[go: up one dir, main page]

WO2013065264A1 - Dispositif de communication et procédé de migration hors ligne - Google Patents

Dispositif de communication et procédé de migration hors ligne Download PDF

Info

Publication number
WO2013065264A1
WO2013065264A1 PCT/JP2012/006851 JP2012006851W WO2013065264A1 WO 2013065264 A1 WO2013065264 A1 WO 2013065264A1 JP 2012006851 W JP2012006851 W JP 2012006851W WO 2013065264 A1 WO2013065264 A1 WO 2013065264A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
network
communication
detach request
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2012/006851
Other languages
English (en)
Japanese (ja)
Inventor
ヤン スティーブン ジャン
チャン ワー ンー
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Panasonic Corp
Original Assignee
Panasonic Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Panasonic Corp filed Critical Panasonic Corp
Publication of WO2013065264A1 publication Critical patent/WO2013065264A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data

Definitions

  • the disclosed technology relates to a communication technology in a packet-switched data communication network. More specifically, the disclosed technology belongs to a specific group, and offline a communication device (user equipment) that performs communication related to the specific group via a network, and a plurality of communication devices that belong to the specific group It relates to the offline migration method to migrate to.
  • a communication device user equipment
  • GSM Global System for Mobile communications
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • the system is constantly evolving. In the future, the next generation LTE (Long Term Evolution) network will be deployed.
  • LTE Long Term Evolution
  • M2M machine-to-machine
  • MTC machine type communication
  • the following non-patent document 1 defines requirements in a cellular network to support machine type communication (MTC).
  • MTC machine type communication
  • the 3GPP MTC is configured by various communication devices that access the 3GPP cellular network in order to communicate with a server outside the cellular network or to communicate with other communication devices in the cellular network.
  • the cellular network can support MTC more appropriately.
  • MTC includes an MTC device that performs communication using 3GPP wireless network access.
  • MTC devices can be grouped according to the needs of the operator with regard to control, management, billing, and the like.
  • MTC devices belonging to the same group have common characteristics such as, for example, existing in the same area and / or having the same MTC characteristics and / or belonging to the same MTC user. Yes.
  • the MTC user related to the MTC group owns the MTC server.
  • the MTC server is connected to the mobile network operator's packet switched network by an APN (Access Point Name) using the Gi / SGi interface. All MTC devices in the MTC group can communicate with the MTC server on the user plane.
  • APN Access Point Name
  • Optimized to group MTC devices it becomes easy to control, update, and charge MTC devices.
  • redundancy and unnecessary signaling for preventing network congestion can be reduced.
  • the network resources can be used more efficiently by the group-based optimization, and unnecessary signaling can be prevented.
  • FIG. 1 shows an example of a network based on the current architecture of MTC in 3GPP EPC (Evolved Packet Core) described in Non-Patent Document 1 and Non-Patent Document 2 below.
  • the 3GPP network (network) 110 illustrated in FIG. 1 includes a PGW (Packet Data Network Gateway) 120, an MTC-IWF (Inter-Working Function) 122, and an SGW (Serving Gateway). Gateway 130, MME (Mobility Management Entity) 140, PCRF (Policy and Changing Rules) 142, HSS (Home Subscriber Server) 144, multiple base stations ( eNodeB or eNB) 150.
  • PGW Packet Data Network Gateway
  • MTC-IWF Inter-Working Function
  • SGW Serving Gateway
  • Gateway 130 MME (Mobility Management Entity) 140
  • PCRF Policy and Changing Rules
  • HSS Home Subscriber Server
  • eNodeB or eNB multiple base stations
  • a mobile device (sometimes referred to as a user equipment (UE), MTC device, communication device) 100 is attached to a radio access network of a base station (eNB) 150 (shown by an attachment 190).
  • the communication service is acquired from the network 110.
  • the interface 170 between the PGW 120 and the SGW 130 enables packet transfer on the user plane (U-plane) between the PGW 120 and the SGW 130, and the interfaces 174 and 176 between the SGW 130 and the eNB 150 allow Packet transfer between each eNB 150 of the mobile device is possible.
  • one or more EPS bearers via the SGW 130 and the eNB 150 are established between the PGW 120 and the mobile device 100.
  • control plane (C plane) signaling can be executed by the interface 172 between the SGW 130 and the MME 140 and the interfaces 178 and 180 between the MME 140 and each eNB 150.
  • C plane control plane
  • the SGW 130 may notify the downlink via the C-plane interface 172.
  • the MME 140 transmits a paging message and triggers the MTC device 100 to establish a connection via the eNB 150.
  • the interface 145 allows the MME 140 to acquire subscriber information from the HSS 144 in the C plane.
  • the interface 121 enables data transfer between the MTC server 143 and the network 110.
  • the interface 146 enables data transfer between the MTC server 143 and the PGW 120.
  • the MTC device 100 transmits data to the MTC server 143 almost simultaneously and briefly. There is a possibility of going offline in a few seconds (for example, several seconds).
  • Each MTC device 100 in a group needs to initiate a detach request to the MME 140 to request disconnection from the network 110. If there are a large number of MTC devices 100 in the group, a large number of MTC devices 100 to the network 110 almost simultaneously. Will be sent.
  • the network 110 receives these messages, it needs to process each message with communication between network elements (eg, PGW 120, SGW 130, MME 140) in order to reallocate resources.
  • network elements eg, PGW 120, SGW 130, MME 140
  • the network 110 may be overloaded with messages from multiple MTC devices 100 in the same group that occupies a large amount of network resources. As a result, the network 110 may become congested and affect other devices (for example, normal communication related to other devices may be interrupted). Further, when a large number of MTC devices 100 in the same group are attached to the network 110 by wireless communication, a large amount of signaling messages may be transmitted in the wireless communication section (between the MTC device 100 and the eNB 150). There is. In addition, since the MTC device 100 wastes power and battery, which are very important resources for the MTC device, by performing signaling, there is a demand to reduce the amount of signaling as much as possible.
  • FIG. 2 shows a message sequence chart of a detachment procedure started by the MTC device in the prior art. This detaching procedure is described in Non-Patent Document 2, for example.
  • the MME 140 when the MME 140 receives a detach request (Detach Request) 201 started by the UE (MTC device 100), the MME 140 transmits a delete session request (Delete Session Request) message 202 to the SGW 130.
  • the SGW 130 receives the session deletion request message 202 and returns a session deletion response (Delete Session Response) message 203 to the MME 140.
  • the SGW 130 similarly transmits a session deletion request message 204 to the PGW 120, and the PGW 120 returns a session deletion response message 205 to the SGW 130.
  • the MME 140 After receiving the session deletion response message 205 from the SGW 130, the MME 140 performs a confirmation response to the UE 100 by using a detach accept (Detach Accept) message 206. Then, the signaling connection between the UE 100, the eNB 150, and the MME 140 is released (connection release signaling 207, 208), and the detach procedure is completed.
  • a detach accept (Detach Accept) message 206.
  • the network 110 may be congested in the PGW 120, the SGW 130, the MME 140, and the like.
  • the MME 140 needs to reallocate a large amount of resources and needs to process all detach requests 201 received from a number of MTC devices 100.
  • the MTC device 100 may not be able to receive the detach accept message 206.
  • the MTC device 100 retransmits the detach request 201 to the MME 140 five times and then performs an implicit detach. (See Non-Patent Document 3). Such retransmission of messages further exacerbates the network congestion.
  • the congestion can be alleviated by a mobility management back-off timer.
  • the back-off timer is useful for congestion in continuous data transmission, but when there is a transition from no congestion in the core network to a state in which many detach requests are sent in a short time and congestion occurs. Is useless.
  • Patent Document 1 discloses a method for maintaining a connection established with a network node when an accept message is received. However, there is no mention of a method for disconnecting an established connection without receiving an accept message.
  • Patent Document 2 discloses a method in which a device (member) in a group acquires group information from devices belonging to another group in group communication.
  • Patent Document 3 discloses a group communication gateway that supports control signaling and data traffic exchange related to group communication in a cellular network. The group communication gateway relays messages from the group to other nodes, thereby enabling direct mode user terminals to participate in packet-based cellular group communication.
  • 3GPP TS 23.401v10.4.0 “General Packet Radio Service” (GPRS) “enhancements” for “Evolved” Universal “Terrestrial” Radio “Access” network “(E-UTRAN)“ access ”,“ Jun ”2011.
  • 3GPP TS 24.301v10.3.0 “Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3”, Jun 2011.
  • NAS Non-Access-Stratum
  • a technology for shifting a plurality of user devices belonging to the same group to an offline state and a signaling amount between the network and the network that occurs when the offline device is shifted to the offline state are reduced.
  • a communication device and an off-line migration method for realizing the technology to be performed are provided.
  • communication for enabling each communication device to individually determine whether or not to detach from the network is provided.
  • a communication device provided by an aspect of the present disclosure is a communication device that belongs to a specific group and performs communication related to the specific group via a network.
  • a detach request message receiving unit that receives a detach request message that instructs a plurality of communication devices belonging to the specific group to detach from the network;
  • a determination unit that determines whether to respond to the detach request message;
  • the network is detached from the network without performing signaling to the network.
  • the aspect of the disclosed technique may be realized by an off-line migration method or the like other than the communication device described above.
  • One aspect of the disclosed technology is that, for example, a plurality of user devices belonging to a specific group (the same group) are shifted to offline, and the amount of signaling with the network that occurs when shifting to the offline is reduced. Has an effect.
  • each communication device has an effect that it can individually determine whether or not to detach from the network.
  • FIG. 3 is a block diagram illustrating an example of a functional architecture of a user equipment according to the first embodiment of the present disclosure.
  • the figure which shows the 1st example in case MTC server resends a group detach request in 1st Embodiment of this indication technique.
  • the figure which shows the 2nd example in case MTC server resends a group detach request in 1st Embodiment of this indication technique.
  • the figure which shows the 3rd example in case MTC server resends a group detach request in 1st Embodiment of this indication technique.
  • a message requesting a specific device for example, an MTC server
  • detach (disconnect) all user devices for example, MTC devices belonging to the same group.
  • Group Detach Request is transmitted, and each MTC device is detached from the network in response to the group detach request and goes offline. Specifically, for example, the process illustrated in FIG. 3 is executed.
  • FIG. 3 is a sequence chart illustrating an example of basic group offline processing according to the first embodiment of the disclosed technology. Note that the sequence chart shown in FIG. 3 shows an example of processing executed in the network configuration of FIG. Also, the three MTC devices 100A to 100C illustrated in FIG. 3 correspond to the MTC device 100 of FIG. 1, and may be connected to the same or different eNBs 150, respectively.
  • the MTC server 143 transmits a group detach request 240 to the MME 140 via the MTC-IWF 122 or the PGW 120.
  • the MME 140 transmits a group detach request 241 to all the MTC devices 100A to 100C belonging to the corresponding group.
  • the MME 140 transmits a group detach request 241 (hereinafter also referred to as a broadcast group detach request 241) by a broadcast message addressed to a group ID that identifies the corresponding group.
  • the MME 140 may change the format of the group detach request 240 or generate a group detach request 241 having a new format before broadcasting the group detach request 241 to the entire group.
  • the MME 140 may reset a TAU (Tracking Area Update) timer for each MTC device of the related group in the broadcast group detach request 241 when the broadcast group detach request 241 is transferred.
  • the new value to be reset is, for example, a small value defined in advance. If the MME 140 does not receive a further TAU request message from the MTC devices 100A to 100C when the TAU timer expires, the MME 140 performs an implicit detach for each MTC device 100A to 100C in the group associated with the broadcast group detach request 241. May be. In the present specification, the fact that the device disconnects the connection locally without performing signaling in this way is referred to as implicit detach.
  • the MTC devices 100A to 100C accept the broadcast group detach request 241 and detach the connection with the network. At this time, each MTC device 100A to 100C executes implicit detachment 242A to 242C without performing signaling to the network 110 side.
  • the MME 140 performs a process 243 for detaching all the MTC devices 100 A to 100 C of the group related to the broadcast group detach request 241. Specifically, the MME 140 deletes the context of the device (MTC devices 100A to 100C) in the group related to the broadcast group detach request 241.
  • the process 243 performed by the MME 140 may be an implicit detachment (a detach process that does not involve signaling), or may perform signaling for deleting a session in the SGW 130 and the PGW 120. Further, the MME 140 may notify the result of the group detach request 240 by transmitting a response 244 to the group detach request 240 to the MTC server 143.
  • the MTC server 143 transmits a group detach request 240 to all the MTC devices 100A to 100C belonging to the group, and all the MTC devices 100A to 100C transmit signaling messages (for example, By executing the implicit detach locally without transmitting the detach request 201 shown in FIG. 2, the amount of signaling message can be reduced.
  • the MTC server 143 transmits the group detach request 240, but the sender of the group detach request 240 (referred to as a group leader) is the MTC user, the MTC device 100 in the group, or this group. It may be transmitted by any device that does not belong to.
  • the group leader is responsible for initiating a group detach request 240 on behalf of the entire group, and can the group detach request 240 transmitted from the group leader be broadcast to each MTC device 100 in the group? Alternatively, it can be transmitted to each MTC device 100 in the group via the data plane.
  • the group detach request 240 includes a new information element (for example, MTC group ID information).
  • MTC group ID information for example, MTC group ID information.
  • the MTC server 143 first needs to send the group detach request 240 to the MME 140.
  • This group detach request 240 can reach each MTC device 100 via an interface between the MME 140 and the MTC devices 100 in the group.
  • the group leader may be a normal MTC device 100 in the group.
  • the group detach request 240 is started by the MTC device 100 functioning as a group leader, the group detach request 240 is transmitted from the group leader (MTC device 100) to the MME 140, and the MME 140 broadcasts the received group detach request to the entire group. To do.
  • the group leader (for example, the MTC server 143 or the normal MTC device 100) transmits a data packet including the group detach request 240. It is necessary to transmit to each MTC device 100 in the group.
  • the data packet including the group detach request 240 reaches each MTC device 100 via a connection established between the group leader and each MTC device 100. If there is no established connection available between the group leader and each MTC device 100, the MME 140 needs to page each MTC device 100 in order to set up the connection.
  • the MTC device 100 in the group performs implicit detachment based on specific information, or starts a group detach request for all devices in the same group (that is, operates as a group leader). It is possible to determine.
  • the specific information indicating whether to operate as a group leader may be, for example, the unique sequence number received from the MME 140 during the attach procedure and the total number of MTC devices 100 connected in the group, or It may be the number of MTC devices 100 in the group for which data communication has been completed.
  • the information which shows that the MTC device 100 itself is a server or user of an MTC group may be sufficient. These pieces of information may be acquired by the MTC device 100 as the group leader sending a query to the MTC server 143 and a response thereof.
  • the notification regarding the information indicating that it operates as a group leader can be realized by, for example, a group notification to each MTC device 100 in the group.
  • the group notification includes a group property flag (Group Property Flag: GPF) used to store the group property.
  • GPF Group Property Flag
  • the GPF can have various aspects in each group or each application. For example, when the GPF is on, it indicates that the MTC device 100 needs to make a group detach request 240 before going offline. Is off, the MTC device 100 may perform an implicit detach or power off without signaling to the network 110 (eg, MME 140 or SGSN). That is, the MTC device 100 that has received the group notification that the GPF is on operates as a group leader. In the MTC device 100 that is not specified by the group application, the GPF can be ignored.
  • the MTC device 100 compares information received from the network 110 with information stored locally.
  • the MME 140 provides a unique sequence number (for example, Group-aa-bbb) to each MTC device 100, for example, during an attach procedure. This sequence number is incremented every time it is assigned to the MTC device 100. After a certain time elapses, the MME 140 gives the MTC device 100 having the maximum sequence number the right to start a group detach request at the end of data transmission.
  • the MME 140 may grant the right to start a group detach request to the plurality of MTC devices 100, but the MME 140 accepts only a request having the maximum sequence number, for example.
  • the MME 140 gives the MTC device 100 the right to start a group detach request, it is possible to cope with a case where a new MTC device 100 of the same group is attached.
  • the MME provides a unique sequence number to each MTC device 100, for example, during the attach procedure, and further periodically assigns the maximum sequence number from the network 110 to the MTC devices in the group. You may broadcast to 100.
  • the MTC device 100 that has received this broadcast message compares the value included in the broadcast message with a locally stored sequence number, and if the two values match, operates as a group leader, taking the entire group offline.
  • the execution timing of the group detach request 240 for shifting is determined.
  • the execution timing of the group detach request 240 may be a timing at which the MTC device (group leader) 100 completes data transmission.
  • each MTC device 100 can be expanded so that each MTC device 100 can determine whether or not to follow the broadcast group detach request 241.
  • a response 246 TAU message including the ID of another group is transmitted in order to maintain communication in the other group.
  • FIG. 4 is a sequence chart illustrating an example of the extended group offline processing according to the first embodiment of the disclosed technology.
  • the MTC server 143 transmits a group detach request 240 to the MME 140, and the MME 140 transmits a broadcast group detach request 241 to all the MTC devices 100A to 100C in the group.
  • the MTC devices 100A to 100C execute processing 245A to 245C for determining whether to accept the broadcast group detach request 241 or not.
  • the MTC devices that have decided to accept the broadcast group detach request 241 (in FIG. 4, MTC devices 100A and 100B) perform implicit detach and detach from the network.
  • the MTC device that has decided not to accept the broadcast group detach request 241 (in FIG. 4, the MTC device 100C) makes a response 246 for maintaining the attachment to the network 110 to the network 110.
  • the MME 140 receives all devices except for a device (MTC device 100C) that has transmitted a response to the broadcast group detach request 241 after a predetermined time (a time sufficient for receiving a response from each MTC device 100A to 100C) has elapsed. Processing 247 for deleting the context of (MTC devices 100A, 100B) is executed. Note that the MME 140 may change or update the context necessary for maintaining the attachment of the MTC device 100C that has transmitted the response 246 to the broadcast group detach request 241. Further, the MME 140 may notify the result of the group detach request 240 by transmitting a response 248 to the group detach request to the MTC server 143.
  • the MTC devices 100A and 100B that are detached from the network 110 do not transmit a response to the broadcast group detach request 241 and the MTC device 100C that maintains the attachment to the network 110 responds to the broadcast group detach request 241.
  • a response 246 is performed.
  • the MTC device 100 that maintains the attachment to the network 110 does not send a response to the broadcast group detach request 241, and the MTC device 100 that detaches from the network makes a response 246 to the broadcast group detach request 241. It may be.
  • the MTC devices 100A and 100B in FIG. 4 maintain the attachment, and the MTC device 100C in FIG.
  • the MTC device 100 performs a response 246 for disconnecting from the network (in this case, a normal detach process is performed). May be).
  • the MTC device 100 is described to make a decision to select whether to maintain or detach from the network 110. For example, while maintaining the attached state, Other operations such as disconnecting only the PDN connection related to the communication of the group may be selected.
  • the MTC server 143 transmits a group detach request 240 to all the MTC devices 100 belonging to the group, and all the MTC devices 100 respectively send a broadcast group detach request 241.
  • Only the MTC device 100 that decides to accept or accepts the broadcast group detach request 241 (or conversely, the MTC device 100 that does not accept the broadcast group detach request 241) responds 246 to the broadcast group detach request 241 (eg, FIG. 2 detach request 201, TAU message, etc.) to the network 110 to reduce the amount of signaling messages Rukoto can be performed.
  • each of the MTC devices 100A to 100C performs processing 245A to 245C for determining whether or not to accept the broadcast group detach request 241.
  • the devices 100A to 100C perform this processing 245A to 245C, for example, on the mobility management status of the evolved packet system (Evolved Packet System Mobility Management (EMM status)), application status (for example, whether or not there is data to be transmitted), past Can be performed based on whether or not a group trigger request is received and the reception timing.
  • EMM status evolved Packet System Mobility Management
  • application status for example, whether or not there is data to be transmitted
  • past Can be performed based on whether or not a group trigger request is received and the reception timing.
  • the group trigger request is a message transmitted from the MTC server 143 to attach all the MTC devices 100 to the network 110 in order for the MTC server 143 to perform specific communication with all devices in the group.
  • the MTC server 143 transmits a group trigger request 220 to the MME 140 via the MTC-IWF 122 and the PGW 120, and the MME 140 identifies a group ID that identifies the corresponding group.
  • All MTC devices 100A to 100C can be attached by transmitting a group trigger request 221 (hereinafter also referred to as a broadcast group trigger request 221) to all MTC devices 100A to 100C by a broadcast message addressed thereto. It is.
  • the broadcast group trigger request 221 can be embedded in, for example, CBS (Cell Broadcast Service) or SIB (System Information Block) periodically broadcast by each eNB 150.
  • the MTC devices 100A to 100C are considered when performing the process of determining whether to accept the broadcast group detach request 241 (corresponding to the processes 245A to 245C of FIG. 4). An example of the conditions will be described.
  • the relationship between the attachment to the network 110 by the MTC device 100 and the broadcast group trigger request 221 transmitted from the MTC server 143 is as follows.
  • the MTC device 100 attaches and then receives the broadcast group trigger request 221 (Case B)
  • the MTC device 100 attaches itself but receives the broadcast group trigger request 221. If not, it can be divided into three cases (Case C).
  • FIG. 5A shows a case where the MTC device 100 is attached by the broadcast group trigger request 221 (case A).
  • the MTC device 100 receives a broadcast group trigger request 221 from the network 110 in an offline state, attaches 261 to the network 110 in response to the received broadcast group trigger request 221, and then broadcasts.
  • the group detach request 241 has been received.
  • Case A when the MTC device 100 receives the broadcast group detach request 241 from the MME 140, if the current status of the MTC device 100 is in the idle mode, the MTC device 100 executes an implicit detach. If a predetermined period of time elapses without receiving a mobility management message from the MTC device 100, the MME 140 considers that the MTC device 100 has accepted the broadcast group detach request 241, and the MME 140 also disconnects (deletes the context) with respect to the MTC device 100. ).
  • the MTC device 100 executes implicit detachment. After a predetermined period has elapsed without receiving a mobility management message from the MTC device 100, the MME 140 also performs disconnection (context deletion) with respect to the MTC device 100.
  • the MTC device 100 when the MTC device 100 receives the broadcast group detach request 241 from the MME 140, if the MTC device 100 is in the connected mode and has data to be transmitted, the MTC device 100 Initiate a TAU request to maintain the MME 140 context. The MME 140 that has received the TAU request maintains the context regarding the MTC device 100.
  • FIG. 5B shows a case where the MTC device 100 attaches itself and then receives the broadcast group trigger request 221 (Case B).
  • the MTC device 100 attaches to the network 110 for some reason not attributable to the broadcast group trigger request 221, then receives the broadcast group trigger request 221 and further sends the broadcast group detach 241. Receiving.
  • the MTC device 100 transmits a PDN connection disconnection request message to the MME 140, thereby causing a PDN connection related to the broadcast group detach request 241 (PDN used for the group communication). Connection). Further, the MME 140 responds to the disconnection of the PDN connection of the MTC device 100.
  • the MTC device 100 When the MTC device 100 is attached to the network 110 for a reason not caused by the broadcast group trigger request 221 (for example, when other group communication is performed), and is detached according to the broadcast group detach request 241 May affect other group communications, for example. Therefore, in Case B, the MTC device 100 disconnects the PDN connection related to the broadcast group detach request 241, but does not perform detachment according to the broadcast group detach request 241. Note that when only the PDN connection related to the received broadcast group detach request 241 is included, the MTC device 100 may execute the implicit detach instead of starting the PDN connection disconnection request. If the MTC device 100 does not have another PDN connection, it can be considered that there is no reason to attach to the network 110 any more.
  • the MTC device 100 executes the TAU procedure, It is possible to maintain context within the MME 140.
  • FIG. 5C shows a case where the MTC device 100 attaches itself and then receives the broadcast group detach request 241 without receiving the broadcast group trigger request 221 (Case C).
  • Case C illustrated in FIG. 5C the MTC device 100 does not follow the received broadcast group detach request 241 and initiates a TAU request to maintain the context of the network 110.
  • Case C illustrated in FIG. 5C is a case where the MTC device 100 becomes operable after the transmission of the broadcast group trigger request 221 or some situation related to the network 110 (for example, network congestion). For example, a case where the MTC device 100 cannot receive the broadcast group trigger request 221 is assumed.
  • FIG. 6 is a flowchart showing an example of the operation of the MTC device corresponding to cases A to C shown in FIGS. 5A to 5C in the first embodiment of the disclosed technology. 6 is executed by the determination unit 104 of the MTC device 100 shown in FIG. 7 to be described later.
  • step S610 the MTC device 100 checks whether or not a broadcast group trigger request 221 corresponding to the broadcast group detach request 241 has been received in the past.
  • the MTC device 100 determines to start the TAU procedure in step S630.
  • step S620 if it is detected in step S620 that the MTC device 100 has received the broadcast group trigger request 221, the MTC device 100 is attached based on the broadcast group trigger request 221 in step S640. Check whether or not. If it is determined in the check in step S640 that the attachment of the MTC device 100 is caused by the broadcast group trigger request 221 (that is, case A in FIG. 5A), the MTC device 100 sets the EMM status in step S650. Check further.
  • the MTC device 100 determines to perform the implicit detachment in step S660.
  • the MTC device 100 determines whether or not the MTC device 100 has data to be transmitted in step S670. I will investigate further. If the MTC device 100 has data to transmit, the MTC device 100 determines to start the TAU procedure in step S630. Note that the MTC device 100 may specify the value of the TAU timer by a TAU request.
  • the MTC device 100 may calculate, for example, the time required for transmission of the remaining data, and may determine the value of the TAU timer based on the calculation result, and may relate to the value of the TAU timer with the MME 140. You may negotiate. On the other hand, when the MTC device 100 does not have data to be transmitted, the MTC device 100 determines to perform the implicit detachment in step S660.
  • the MTC device 100 In S680, it is determined to delete the PDN connection related to the received broadcast group detach request 241. Although not shown in FIG. 6, in step S680, the MTC device 100 further determines whether or not the MTC device 100 has data to be transmitted in relation to the received broadcast group detach request 241. If the MTC device 100 does not have data to be transmitted, it is determined to delete the PDN connection. If the MTC device 100 has data to be transmitted, the TAU procedure is executed. You may decide.
  • the determination is made based on the broadcast group trigger request 221 received by the MTC device 100 in the past, but the MTC device may use another determination method. For example, when the MTC device 100 receives the broadcast group detach request 241, if the MTC device 100 still has data to be transmitted as the MTC device 100 of the group, the MTC device 100 executes the TAU procedure as the MTC device 100 of the group. When there is no data to be transmitted but communication is performed via another PDN connection (or when it is necessary to do so from now on), the PDN connection related to the group communication is deleted, but detachment is performed. Implicit detach is executed when the online data is maintained without being executed, and there is no data to be transmitted as the MTC device 100 of the group, and communication through another PDN connection is not required. It may be determined as follows.
  • the MTC device 100 determines whether to accept or reject the broadcast group detach request 241, whether or not a PDN connection is established with respect to another APN different from the APN related to this group application. You may check. If the MTC device 100 has a PDN connection established to a different APN (for example, another MTC server), the MTC device 100 executes the TAU request or receives the received broadcast group detach request 241. It decides to disconnect the PDN connection related to, and does not accept the broadcast group detach request 241. On the other hand, if the MTC device 100 does not have another PDN connection established to a different APN (eg, another MTC server) and is not connected to another APN different from the APN associated with the group application. For example, the MTC device 100 can perform implicit detachment.
  • a different APN for example, another MTC server
  • the MTC device 100 when the MTC device 100 receives the broadcast group detach request 241, the mobility management back-off timer is activated, or whether EAB (Enhanced Access Barring) or ACB (Access Class Barring) is active. , Whether to accept the broadcast group detach request 241 may be determined. For example, the MTC device 100 can execute the implicit detachment when the back-off timer is activated or when the EAB / ACB is active.
  • EAB Enhanced Access Barring
  • ACB Access Class Barring
  • FIG. 7 shows an example of the functional architecture of the user equipment in the first embodiment of the disclosed technique.
  • the functional architecture of the user equipment (MTC device 100) illustrated in FIG. 7 includes a wireless interface 101, a NAS (Non Access Stratum) layer 102, a storage unit 103, a determination unit 104, a response unit 105, and an application layer. 106.
  • MTC device 100 The functional architecture of the user equipment (MTC device 100) illustrated in FIG. 7 includes a wireless interface 101, a NAS (Non Access Stratum) layer 102, a storage unit 103, a determination unit 104, a response unit 105, and an application layer. 106.
  • NAS Non Access Stratum
  • the wireless interface 101 is a functional block having hardware and firmware necessary for the MTC device 100 to communicate with the cellular base station (eNB 150), and may include, for example, an antenna, a transmission circuit, and a reception circuit.
  • the radio interface 101 also performs radio access control and signaling to the cellular radio network, and data packet transfer through cellular radio access.
  • the user equipment is an MTC device that performs wireless communication is described as a preferred embodiment, but the user equipment is not limited to the MTC device.
  • the user device may perform wired communication. That is, the wireless interface 101 illustrated in FIG. 7 may be a wired interface for performing wired communication. Further, the wireless interface 101 may be positioned above another layer of the communication protocol stack, for example, above UMA (Unlicensed Mobile Access) or GAN (Generic Access Mobile Network).
  • the NAS layer 102 is a functional block that performs control plane signaling and starts user plane data transfer between the MTC device 100 and the network 110.
  • the wireless interface 101 and the NAS layer 102 can exchange control information and signaling messages through the signal path 701.
  • NAS messages transmitted from the network 110 are processed by the NAS layer 102.
  • the NAS message transmitted from the MTC device 100 to the network 110 is generated by the NAS layer 102.
  • the storage unit 103 has a function of storing information received from the NAS layer 102 through the signal path 702.
  • the storage unit 103 can supply information to the determination unit 104 through the signal path 704.
  • reception history information for example, reception presence / absence and reception timing
  • the broadcast group trigger request 221 can be stored.
  • the determination unit 104 has a function of determining what kind of response is to be made when the NAS layer 102 receives the broadcast group detach request 241.
  • the determination unit 104 can acquire information from the storage unit 103 through the signal path 704. Further, the determination unit 104 can detect reception of the broadcast group detach request 241 based on a notification from the response unit 105, for example. Further, the determination unit 104 may acquire information from the application layer 106 via the signal path 706 as necessary. For example, the determination unit 104 checks whether an application operating in the application layer 106 has data to be transmitted (that is, whether transmission data of the application still remains), or transmission data remains.
  • the remaining data amount may be acquired, or the time required for transmission of the remaining transmission data may be calculated based on the remaining data amount and the transmission speed of the network 110.
  • the value of the TAU timer can be set so that the value of the TAU timer expires after the transmission of the remaining transmission data is completed.
  • the determination unit 104 can instruct the response unit 105 about the determined response method via the signal path 705, and can trigger a signal related to an appropriate response from the response unit 105 to the NAS layer 102. It is.
  • the determination unit 104 can execute the processing of the flowchart shown in FIG.
  • the determination unit 104 functions as a trigger message reception presence / absence determination unit that determines whether or not a broadcast group trigger request has been received, and whether or not the attachment to the current network is caused by the broadcast group trigger request.
  • the response unit 105 has a function of responding to a message received from the NAS layer 102.
  • the response unit 105 generates a signal based on the response method determined by the determination unit 104 and transmits the signal to the NAS layer 102 through the signal path 703.
  • the application layer 106 is an abstraction of an application running on the MTC device 100.
  • the application running on the MTC device 100 requires, for example, communication with an external node (for example, another MTC device 100 or the MTC server 143), and the group application is also included in the application layer 106. included.
  • the first embodiment of the disclosed technology extends the MTC server 143 to request the detachment again for the connected MTC device 100 that has not been detached by the previously transmitted broadcast group detach request. It is possible. For example, after a certain period of time, the MTC server 143 can retransmit a new group detach request to the MTC device 100 that has not accepted the broadcast group detach request.
  • an irrelevant MTC device for example, an already detached MTC device 100 or a device belonging to another group
  • the MTC device 100 having no relation to this may receive this message and perform unnecessary processing.
  • the MTC server 143 uses a unicast message or a multicast cast message instead of a broadcast message so that a new group detach request only reaches the connected MTC device 100 that has not been detached. It may be.
  • FIGS. 8A, 8B, and 8C are diagrams for describing first to third examples when the MTC server retransmits a group detach request in the first embodiment of the disclosed technique. .
  • a unicast message or a multicast cast message for the group detach request.
  • the unicast message (unicast group detach request) is used. The case where is transmitted will be described as an example.
  • the MTC server 143 sends a new unicast group
  • the data packet including the detach request 811 can be unicast.
  • the unicast group detach request 811 can be realized by using, for example, a paging message.
  • the paging message is addressed only to one MTC device 100 (a plurality of specific MTC devices 100 in the case of multicast) instead of all the MTC devices 100 in the group.
  • Unicast or multicast transmission can be specified by an identifier in the paging message. Note that a special information element may be inserted into the paging message so that it can be understood that the destination MTC device 100 is the unicast group detach request 811.
  • the MTC device 100 in the connected mode can receive the unicast group detach request 811 and start the detach procedure (implicit detach) 815 in response to the unicast group detach request 811.
  • the MTC device 100 executes the TAU procedure or performs (or is going to perform) communication related to another PDN connection. May perform a process of disconnecting only the PDN connection of the group communication while maintaining the connection.
  • the MME 140 When the MTC device 100 is in the idle mode, the MME 140 needs to transmit the paging message 812 before transferring the data packet including the detach request 811 to the MTC device 100 as illustrated in FIG. 8B. is there. That is, before receiving a data packet including the unicast group detach request 811 from the MTC server 143, the MTC device 100 needs to receive the paging message 812 and respond to the paging message 812 with the service request 813 to the MME 140. There is.
  • the MTC device 100 can receive the unicast group detach request 814 from the MME 140, and operates according to the unicast group detach request 814 (for example, execution of the implicit detach 815, execution of the TAU procedure, PDN connection Cutting, etc.).
  • the operation shown in FIG. 8B can be extended so as to be realized more efficiently.
  • the MTC device 100 receives the paging message 812, it is executed for the paging message 812 by allowing the MTC server 143 to know that the unicast group detach request 811 is being retransmitted. It is possible to omit a response (specifically, transmission of a service request) from the MTC device 100.
  • the MTC device 100 in the idle mode receives the paging message 812 within a predetermined time after receiving the broadcast group detach request 241, the paging message 812 is transmitted as the unicast group detach request 811.
  • the MTC server 143 is retransmitting the unicast group detach request 811 by making it possible to recognize that the message is a paging message for the purpose of retransmission.
  • the MTC device 100 in the idle mode extended as described above performs an implicit detach 815 (or execution of a TAU procedure, disconnection of a PDN connection, etc.) upon reception of the paging message 812, and a signaling message (eg, FIG. 8B). Service request 813) can be omitted.
  • the MTC server 143 transmits the unicast or multicast group detach request to the connected MTC device 100 that has not been detached. It is possible to request that the connection of the device 100 be detached.
  • a specific device for example, the MTC server 143 is used for all user devices (for example, the MTC device 100) belonging to the same group.
  • a message for requesting detachment (group detach request) is transmitted, and each user device can detach the connection to the network in response to the group detach request. Further, each user device can individually determine the response method when receiving a group detach request.
  • each MTC device 100 needs to transmit a similar message (for example, the detach request 201 in FIG. 2) when detaching from the network 110
  • a particular device becomes a group leader representing all MTC devices 100 in the group and sends a single group message (eg, group detach request) to network 110.
  • group message eg, group detach request
  • each MTC device 100 can suppress power consumption. Specifically, for example, the process illustrated in FIG. 9 is executed.
  • a group leader for example, the MTC device 100C in FIG. 9 that is the sender of the group detach request (the group detach request 264 in FIG. 9) is assigned to all the MTC devices in the group.
  • a query 262 for inquiring the status of 100 is transmitted to the MTC server 143.
  • other MTC devices in the same group for example, the MTC devices 100A and 100B in FIG. 9) can be detached locally (implicit detaches 261A and 261B), respectively.
  • the MTC server 143 transmits a response 263 to the MTC device 100C that is the group leader.
  • the MTC device 100C which is the group leader, determines whether or not to start the group detach request 264 or the start timing based on information in the response 263 from the MTC server 143.
  • the MTC device 100C which is the group leader, transmits a group detach request 264 including group ID information, and the MME 140 receives this group detach request 264, the MME 140 receives the received group detach request as shown in process 265. Detach all MTC devices in the group associated with H.264 locally (eg, delete context).
  • the MTC device 100C which is the group leader, can grasp the status of all the MTC devices 100A and 100B in the group by the query 262 and the response 263.
  • each MTC device 100A and 100B needs to indicate completion of data transmission to the MTC server 143.
  • the MTC server 143 can grasp the status of all the MTC devices 100A, 100B in the MTC group, and the MTC device 100C that is the group leader. Can determine whether or not to make a group detach request 264, or start timing thereof.
  • the MTC device 100C grasps the status of all the MTC devices 100A, 100B by exchanging the query 262 and response 263 with the MTC server 143, but is the group leader.
  • the MTC device 100C may communicate with the MTC devices 100A and 100B in the group via the application layer to grasp the status of the MTC devices 100A and 100B.
  • the MTC device 100C which is a group leader, sets up a connection with each MTC device 100A, 100B, exchanges queries and responses with each MTC device 100A, 100B, and status of each MTC device 100A, 100B By grasping the above, whether or not to start the group detach request or the start timing thereof may be determined.
  • any method can be adopted for the determination of the group leader and the notification within the group.
  • the MTC device 100 that has received the maximum sequence number during the attach procedure can operate as a group leader, similarly to the method described in the first embodiment of the presently disclosed technology.
  • one of the MTC devices in the group (the MTC device 100C) operates as the group leader.
  • the MTC server 143, the MTC user, and any device that does not belong to the same group It may operate as a group leader.
  • each MTC device 100A, 100B performs implicit detachment.
  • the MTC devices 100A, 100B belong to other groups and try to continue communication related to the other groups.
  • the MTC device 100C which is the group leader, may be excluded from the target of the group detach request 264 by notifying the MME 140 of the presence of an MTC device that is not to be detached, or performing the detachment.
  • An MTC device that does not exist may notify the MME 140 of the maintenance of the attached state to the MME 140 itself.
  • the MTC device that does not perform detachment can execute, for example, TAU or perform processing for disconnecting only the PDN connection related to the group communication.
  • the MTC device 100C that is the group leader also executes the implicit detach 261C after transmitting the group detach request 264.
  • the MTC device 100C wants to maintain the attached state without performing the detach. It is done.
  • the MTC device 100C as the group leader may transmit a TAU request including a group detach request having group ID information to the MME 140 so that the attached state of the MTC device 100C itself can be maintained. .
  • a specific device when a large number of all user equipments belonging to the same group detach from the network, a specific device receives a single group message (for example, a group message). (Detach request) can be transmitted to the network.
  • each user device can individually determine whether or not to detach from the network.
  • the MTC server 143 transmits a group trigger request 220 (and a broadcast group trigger request 221) to each MTC device 100A to 100C, and each MTC device 100A to 100C transmits a broadcast group trigger.
  • an MTC device operating as a group leader is determined from among the MTC devices 100A to 100C.
  • the group leader may collectively transmit messages (for example, a TAU request and a PDN connection disconnection request) to be transmitted to the MME 140 by determining individually and not transmitting the broadcast group detach request 241.
  • the communication device receives a trigger message that instructs the plurality of communication devices belonging to the specific group to perform the network hair touch; and A storage unit for storing information on the trigger message; The determination unit may determine whether to respond to the detach request message based on information on the trigger message stored in the storage unit.
  • the determination unit includes a trigger message reception presence / absence determination unit that determines whether the trigger message is received based on information on the trigger message. If the trigger message is not received, it may be determined to maintain the attachment to the network.
  • the determination unit determines whether or not the trigger message is received based on information on the trigger message.
  • An attach factor specifying unit that determines whether or not the current attachment to the network is caused by the trigger message; If the trigger message has not been received, and if the current attachment to the network is not due to the trigger message, it decides to maintain the attachment to the network and You may decide to cut
  • the determination unit determines whether the trigger message is received, a trigger message reception presence / absence determination unit, and a current attachment to the network
  • An attach factor specifying unit that determines whether or not it is caused by a trigger message
  • a status determination unit that determines whether or not the current state of the communication device is an idle mode
  • the determination unit determines whether the trigger message is received, a trigger message reception presence / absence determination unit, and a current attachment to the network Attaching factor specifying unit that determines whether or not it is caused by a trigger message, a status determining unit that determines whether or not the current state of the communication device is in an idle mode, and communication related to the specific group is completed.
  • a group communication completion determination unit that determines whether or not If the trigger message has not been received, if the current attachment to the network is due to the trigger message, and if the current state of the communication device is not in idle mode, and the specified When the communication related to the group is completed, it may be determined to detach from the network.
  • the determination unit determines whether the trigger message is received, a trigger message reception presence / absence determination unit, and a current attachment to the network Attaching factor specifying unit that determines whether or not it is caused by a trigger message, a status determining unit that determines whether or not the current state of the communication device is in an idle mode, and communication related to the specific group is completed.
  • a group communication completion determination unit that determines whether or not If the trigger message has not been received, if the current attachment to the network is due to the trigger message, and if the current state of the communication device is not in idle mode, and the specified If communication related to the group is not completed, it may be determined to maintain the attachment to the network.
  • the determination unit includes a group communication completion determination unit that determines whether communication related to the specific group is completed, When the communication related to the group is not completed, the time until the communication related to the specific group is completed may be calculated and the time may be notified to the network.
  • the determination unit determines to maintain the attachment to the network without responding to the detach request message
  • a timer for measuring elapsed time from the time of receiving the detach request message
  • a paging message receiver for receiving a paging message from the network
  • a detach request message recognition unit that recognizes the paging message received within a predetermined time as a paging message transmitted in accordance with a second detach request message instructing to detach from the network; You may have.
  • the right specifying unit that specifies whether or not the communication device has a transmission right to transmit the detach request message to a plurality of communication devices belonging to the specific group.
  • a detach request message transmitting unit that transmits the detach request message to a plurality of communication devices belonging to the specific group, when having the right to transmit the detach request message; You may have.
  • the plurality of communication devices belonging to the specific group are offline.
  • An offline migration method for migrating to A plurality of communication devices belonging to the specific group receiving a detach request message instructing a plurality of communication devices belonging to the specific group to detach from the network;
  • a plurality of communication devices belonging to the specific group determine whether to respond to the detach request message;
  • detaching from the network in response to the detach request message, detaching from the network without performing signaling to the network.
  • An offline migration method may be included.
  • the offline migration method causes the plurality of communication devices belonging to the specific group to instruct the plurality of communication devices belonging to the specific group to perform the network hair touch.
  • one aspect of the disclosed technology is a method executed by a communication device or a network device, a program for causing a computer to execute the method, and a recording in which the program is recorded It may be realized by a medium or the like.
  • each functional block and each processing unit used in the description of the above embodiment may be realized by hardware, software, or a combination thereof.
  • the functional blocks included in the user equipment shown in FIG. 7 or each processing unit having an equivalent function may be realized by hardware such as a CPU and a memory of an arbitrary computer.
  • each functional block and each processing unit may be realized by causing a computer to execute a program in which operations related to each function are described.
  • the disclosed technology is applied to the MTC technology.
  • the scope of application of the disclosed technology is that of the MTC. It is not limited to technology.
  • the disclosed technology can also be applied to any communication technology capable of grouping communication devices.
  • each functional block used in the description of each embodiment of the presently disclosed technology is typically realized as an LSI (Large Scale Integration) that is an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them.
  • LSI Large Scale Integration
  • IC Integrated Circuit
  • system LSI super LSI
  • ultra LSI ultra LSI depending on the degree of integration.
  • the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible.
  • An FPGA Field Programmable Gate Array
  • a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used.
  • the present disclosure provides an effect of shifting a plurality of user devices belonging to a specific group (the same group) to offline, and reducing the amount of signaling with the network that occurs at the time of shifting to the offline, each communication device Can be individually determined whether or not to detach from the network, and can be applied to communication technologies capable of grouping communication devices, including communication technologies such as MTC.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une technologie qui conduit à la migration hors ligne d'une pluralité d'appareils utilisateurs appartenant à un même groupe, et réduit le volume de signalisation destiné à un réseau apparaissant pendant la migration hors ligne. Au moyen de cette technologie, un serveur MTC (143) transmet une demande de déconnexion de groupe (241) par l'intermédiaire d'une diffusion destinée à des dispositifs MTC (100A-100C) appartenant au même groupe, et chaque dispositif MTC détermine s'il peut ou non accepter la demande de déconnexion du groupe. Les dispositifs MTC qui acceptent la demande de déconnexion du groupe se déconnectent du réseau sans signalisation, tandis que les dispositifs MTC qui n'acceptent pas la demande de déconnexion du groupe répondent (246) à la demande de déconnexion du groupe.
PCT/JP2012/006851 2011-11-01 2012-10-25 Dispositif de communication et procédé de migration hors ligne Ceased WO2013065264A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2011240087 2011-11-01
JP2011-240087 2011-11-01

Publications (1)

Publication Number Publication Date
WO2013065264A1 true WO2013065264A1 (fr) 2013-05-10

Family

ID=48191642

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/006851 Ceased WO2013065264A1 (fr) 2011-11-01 2012-10-25 Dispositif de communication et procédé de migration hors ligne

Country Status (1)

Country Link
WO (1) WO2013065264A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023062878A1 (fr) * 2021-10-13 2023-04-20 株式会社ソラコム Dispositif pour gérer le réglage d'un service de communication sans fil fourni à l'aide d'une infrastructure de communication sans fil possédée par mno, procédé et programme associés

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005217743A (ja) * 2004-01-29 2005-08-11 Hitachi Ltd データ通信方法、並びに、データ通信システムのセンタ局装置及び端末装置
WO2011121921A1 (fr) * 2010-03-29 2011-10-06 パナソニック株式会社 Nœud de communication et nœud de réseau

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005217743A (ja) * 2004-01-29 2005-08-11 Hitachi Ltd データ通信方法、並びに、データ通信システムのセンタ局装置及び端末装置
WO2011121921A1 (fr) * 2010-03-29 2011-10-06 パナソニック株式会社 Nœud de communication et nœud de réseau

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023062878A1 (fr) * 2021-10-13 2023-04-20 株式会社ソラコム Dispositif pour gérer le réglage d'un service de communication sans fil fourni à l'aide d'une infrastructure de communication sans fil possédée par mno, procédé et programme associés

Similar Documents

Publication Publication Date Title
CN115102588B (zh) 5g系统中的寻呼策略区分
JP6835691B2 (ja) マシンタイプ通信のための効率的なシグナリング
JP2020074587A (ja) データスケジューリング方法、基地局およびシステム
EP3346753B1 (fr) Procédé pour transmettre des données dans un système ciot et dispositif associé
US9363658B2 (en) Data transmission method, mobility management entity, and mobile terminal
US20120276913A1 (en) Method and apparatus for transmitting data in a wireless communication network system
US20190021130A1 (en) Method for changing connection mode and mobility management entity
CN107534987B (zh) 一种数据调度方法、基站及系统
WO2013115532A1 (fr) Procédé et appareil de transmission d'un message de compte-rendu de transfert dans un système de communication sans fil
US20150230241A1 (en) Method and apparatus for setting up uplink common bearer in wireless communication network
CN108370498B (zh) 传输方案的确定方法、装置和设备
JP2020503812A (ja) Ｒａｎベースの通知エリアについての情報の通知のための方法およびデバイス
CN102742337A (zh) 数据的传输方法及装置、移动终端
WO2011135790A1 (fr) Dispositif de communication et nœud de réseau
CN111699703B (zh) 在无线电接入网中对数据进行路由的方法、基站、终端
US11140656B2 (en) Paging in a group communications system
WO2013065264A1 (fr) Dispositif de communication et procédé de migration hors ligne
JP2013070319A (ja) 通信システムにおけるアクセスゲートウェイ装置およびルータ広告通信制御方法
CN121040093A (zh) 通信方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12846247

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12846247

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP