EP2472989A1 - Accelerating restoration of communication services upon MME restarting - Google Patents
Accelerating restoration of communication services upon MME restarting Download PDFInfo
- Publication number
- EP2472989A1 EP2472989A1 EP20120159825 EP12159825A EP2472989A1 EP 2472989 A1 EP2472989 A1 EP 2472989A1 EP 20120159825 EP20120159825 EP 20120159825 EP 12159825 A EP12159825 A EP 12159825A EP 2472989 A1 EP2472989 A1 EP 2472989A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- bearer
- mobile station
- management node
- mme
- mobility management
- 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.)
- Granted
Links
- 238000004891 communication Methods 0.000 title description 60
- 230000004044 response Effects 0.000 claims abstract description 9
- 238000010295 mobile communication Methods 0.000 claims abstract 12
- 238000000034 method Methods 0.000 claims description 26
- 101150114331 MME1 gene Proteins 0.000 description 57
- 238000010586 diagram Methods 0.000 description 41
- 238000012545 processing Methods 0.000 description 22
- 230000036541 health Effects 0.000 description 10
- 101150117600 msc1 gene Proteins 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 230000000737 periodic effect Effects 0.000 description 7
- 230000011664 signaling Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 230000005641 tunneling Effects 0.000 description 4
- 101000739172 Homo sapiens Small G protein signaling modulator 1 Proteins 0.000 description 2
- 102100037270 Small G protein signaling modulator 1 Human genes 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 101100398918 Arabidopsis thaliana IPMS2 gene Proteins 0.000 description 1
- 102000018059 CS domains Human genes 0.000 description 1
- 108050007176 CS domains Proteins 0.000 description 1
- 241000760358 Enodes Species 0.000 description 1
- 101100018850 Luffa aegyptiaca IMS1 gene Proteins 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/005—Transmission of information for alerting of incoming communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/25—Maintenance of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
Definitions
- This invention relates to a communication network and, more particularly, to a system and a method as well as an apparatus that may be applied to advantage to the next-generation mobile network system EPC (Evolved Packet Core).
- EPC Evolved Packet Core
- the next-generation mobile network system EPC is a network architecture that accommodates 3G (third generation mobile phone communication system), LTE and so forth in one network.
- 3G third generation mobile phone communication system
- LTE long term evolution
- a MME is a mobility management node.
- the MME takes charge of mobility management (mobility control), such as tracking, of an idle-mode mobile station UE, authentication and setting up a user data forwarding path between an S-GW and a base station eNodeB, in LTE radio access.
- a mobile station is also termed 'a user apparatus', 'a mobile terminal' or simply 'a terminal'.
- the MME is involved in tracking and paging of idle-mode UEs or in bearer activate/deactivate processes.
- the MME selects the S-GW at the time of handover of the UE in LTE and performs user authentication along with HSS.
- a bearer means a logical packet transmission path set up between eNodeB and S-GW/P-GW or the like.
- An SGSN is a mobility management node in the 3G core network. It is a packet switching unit that takes charge of mobility management for mobile stations, such as serving subscriber management, serving subscriber mobility management, originating/incoming call control, tunneling control, charging control, QoS (Quality of Service) control or the like.
- a mobile terminal When a mobile terminal (UE) is in an idle or power-saving state (LTE-idle) in an LTE core network, the mobile station (UE) is identified at the accuracy corresponding to a tracking area list (TA List) composed of a plurality of cells (MME maintains the latest updated TA List).
- TA List tracking area list
- MME maintains the latest updated TA List.
- paging is performed using the latest TA List registered last time.
- the SGSN of the 3G core network performs paging in an RA (Routing Area).
- An S-GW performs routing and forwarding of a user data packet.
- the S-GW is a bearer management node that manages context of a mobile station UE (a parameter of IP bearer service or the like).
- the S-GW sets a path setting request for a P-GW and bearer in the direction of an eNode.
- the S-GW also performs triggering of a paging when the downlink (DL) data to a terminal has arrived.
- a P-GW takes charge of connection of a mobile station (also termed a UE, a user apparatus or a mobile terminal) to a packet data network (a service network: Web browsing service or an external network, such as IMS or the like.
- a mobile station also termed a UE, a user apparatus or a mobile terminal
- a packet data network a service network: Web browsing service or an external network, such as IMS or the like.
- the 'restart' or 'restart of MME/SGSN' means cessation of service due to failure, or intentional cessation of service for maintenance, that leads to initialization setting operation in the MME/SGSN, as a result of which, subscriber information or bearer information that is necessary for the MME/SGSN operation to operate is lost.
- Non-Patent Document 2 (3GPP TS 23.007) provides that, when the S-GW detects that an MME /SGSN has restarted, the S-GW is to release bearer context of a mobile station UE registered in the MME/SGSN that has restarted. That is, According to Non-Patent Document 2, when the MME re-starts after failure, the MME removes the entirety of bearer contexts affected by the restarting. When the S-GW detects that the MME has restarted, the S-GW removes PDN connection table/bearer context corresponding to the MME that has restarted and releases inner resources relevant to the PND connection.
- an S-GW operates in accordance with the above specification of the Non-Patent Document 2, when the MME operation has restarted, the S-GW is unable to effect a packet incoming operation to a mobile station UE until originating a call by the mobile station itself or periodic location registration (e.g., Attach/TAU Request) periodically by performed by the mobile station itself to the MME.
- periodic location registration e.g., Attach/TAU Request
- the network When there is an incoming call to the mobile station UE, the network performs paging all at once to whole cells associated with an area where the mobile station UE has made location registration (tracking area). The so paged mobile station UE accesses a serving cell and establishes a call.
- the entirety of bearer information or resources of the restarted MME has already been removed or released. That is, in the S-GW, radio access bearers in the direction of from the S-GW to the eNodeB and session information between the MME and the S-GW have been removed or released, so that when the incoming packet data to the mobile station UE is received only to no effect.
- TEID or GRE Key as the identification information of a tunnel (GTP-U or P-MIP), a transport protocol between the S-GW and the P-GW, also has been removed.
- GTP-U or P-MIP a transport protocol between the S-GW and the P-GW
- Non-Patent Documents 1 to 3 are incorporated by reference into the present specification. The following is an analysis of the related techniques.
- the S-GW operates in accordance with the above specification of Non-Patent Document 2, as described above, the S-GW which has detected the restarting of the mobility management node MME/SGSN releases entirety of bearers of the mobile station UE registered in the MME/SGSN where restarting occurred.
- the incoming to the mobile station UE after the restarting of the mobility management node MME/SGSN may not be informed to the mobile station UE until such time the attach operation for registration in the network is carried out in the mobile station UE. That is, if, during the time that elapses after restarting of the MME/SGSN until the end of the attachment operation, triggered by the origination by the mobile station UE itself or the periodic location registration by the mobile station UE, the mobile station UE is unable to have a communication service, even if there is an incoming of the communication service. For example, during a time interval of the periodic location registration (e.g., 45 minutes), at the maximum, following the restarting of the MME/SGSN, incoming packet data, addressed to the mobile station UE, may not be delivered to the mobile station UE.
- a time interval of the periodic location registration e.g. 45 minutes
- a bearer management node maintains a specific bearer eligible for restoration of communication services, and removes the other bearers. In case a mobility management node is restarted, the bearer management node maintains at least one bearer.
- a communication method wherein, on restarting of a mobility management node, a circuit switched node sends to the mobility management node a notification message including identification information associated with an mobile station and location registration area information, and the mobility management node starts paging, inclusive of the identification information associated with the mobile station, for an area corresponding to the location registration area information.
- a bearer management node maintains a specific bearer eligible for restoration of communication services, and removes other bearers.
- the mobile network system includes a mobility management node and a bearer management node. When restarting of the mobility management node is performed, the bearer management node maintains at least one of the bearers as set.
- a mobile network system comprising a mobility management node and a circuit switched node.
- the circuit switched node sends to the mobility management node a notification message inclusive of the identification information associated with the mobile station and the location registration area information.
- the management node performs paging including the identification information associated with the mobile station for an area corresponding to the location registration area information.
- a node apparatus that manages a bearer, wherein the node apparatus maintains a specific bearer eligible for restoration of communication services, and removes other bearers. In case restarting of the mobility management node is performed, the node apparatus maintains at least one of the bearers as set.
- a bearer management node S-GW when a mobility management node, such as MME/SGSN, has restarted, a bearer management node S-GW does not release all of bearers relevant to the mobility management node MME/SGSN.
- the bearer management node (S-GW) holds at least part of or entirety of bearers to continue a packet incoming service. That is, when the bearer management node, such as S-GW, detects restarting of the mobility management node (MME/SGSN), the bearer management node confirms that the mobile station UE is accommodated in the mobility management node (MME/SGSN).
- the bearer management node In connection with the mobile station (UE), accommodated in the mobility management node (MME/SGSN), the bearer management node, such as S-GW, retains at least one of bearers set in a direction from the bearer management node (S-GW) towards the external network, such as PDN. By so doing, the mobile station (UE) is able to attach to the network, with packet incoming from the external network (PDN) to the mobile station (UE) as a trigger, thereby accelerating the restoration of a communication service for the mobile station (UE).
- the bearer management node maintains a specific bearer(s) for restoring a communication service, and removes other bearers.
- the bearer management node when maintaining the specific bearer, may start a timer. On timeout of the timer, the bearer management node may remove bearer resources that have been maintained.
- the bearer management node S-GW maintains the location registration area information (TA List/RAI) of the mobile station (UE), informed from the mobility management node (MME/SGSN), and the identification information (IMSI) associated with the mobile station.
- the bearer management node (S-GW) may, on receipt of incoming data to the mobile station (UE), notify the location registration area information (TA list/RAI) and the identification information (IMSI) to the mobility management node (MME/SGSN).
- the mobility management node may then perform paging, using the identification information (IMSI), for only the area corresponding to the location registration area information (TA list/RAI). By so doing, it is possible to selectively reduce an area that is paged by the base station.
- IMSI identification information
- TA list/RAI location registration area information
- Fig.1 is a diagram for illustrating one of modes of the present invention.
- a mobility management node MME/SGSN that manages registration information of a mobile station UE, notifies the location registration information of the mobile station UE to an S-GW at the outset.
- the S-GW maintains the location registration information of the mobile station UE.
- the S-GW also maintains bearers between the S-GW and the P-GW.
- Restarting occurs at the mobility management node MME/SGSN.
- the S-GW When the S-GW detects, by e.g., health check, that the mobility management node MME/SGSN has restarted, the S-GW does not release but maintains bearers that are set between the S-GW and the P-GW. In this case, in view of compatibility of the stable system restoration and availability of communication services, it is possible for the S-GW not to release but continue to maintain those bearers that will provide for high availability services.
- These services may be exemplified by communication that is in need of high reliability in accordance with, e.g., of the operator policy, such as voice services provided by IMS.
- the S-GW may not release but maintain specific S5/S8 bearers between the S-GW and the P-GW, necessary for restoration of services initiated from the network side, and to remove all the other S5/S8 bearers.
- the S-GW when the S-GW detects, by e.g., health check (GTP-echo), that the mobility management node MME/SGSN has restarted, the S-GW releases IMS control bearer services, among bearers set between the S-GW and the P-GW, while maintaining just the bearers used for IMS control.
- GTP-echo health check
- the S-GW releases IMS control bearer services, among bearers set between the S-GW and the P-GW, while maintaining just the bearers used for IMS control.
- Fig.3 is a diagram for illustrating the case of applying the present invention to IMS services.
- the packet incoming is notified, along with the IMSI identifying the UE and the location registration area information, registered beforehand in the S-GW, to the MME/SGSN where the restarting has occurred.
- the MME/SGSN is thus able to cal 1(page) the UE using the IMSI and the location registration area information.
- the mobile station UE that has been paged using the IMSI, performs re-registering (attach) to the MME/SGSN and re-establishes necessary bearers to receive the entirety of packet communication services.
- service arrival may be notified to the mobile station UE to prompt its attachment to the MME to improve availability of communication services.
- a mode of the present invention it is possible to cause the UE to attach to the network, after restarting of the MME/SGSN, with the incoming of the packet to the UE as a trigger.
- Packet communication services may instantaneously be restored to the UE whose services have been started by the arrival of the incoming packet.
- bearers that need high reliability may be taken as bearers to be maintained according to the present invention. It is thus possible to suppress consumption of S-GW resources as well as congestion due to concentration of location registrations.
- This operation is indispensable especially in case a UE where packet communication occurs periodically, as in MTC, is accommodated. The reason is that, in such case, packet communication occurs for many UEs after restarting of the MME/SGSN, and hence the subscriber recovering operations may occur in a burst fashion, with the packet communication as a trigger, thus possibly leading to congestion of the system in its entirety.
- Figs.4 and 5 are diagrams showing an example in which the present invention is applied to CSFB.
- the CSFB function switches voice origination/incoming to 3G to render voice services employing the 3G-CS domain even in case VoIP services are not provided on LTE.
- CSFB function reference is to be made to Non-Patent Document 3 ( Figure 7 .2-1 Mobile Termination Call in idle mode).
- the MME notifies the UE's location registration information to an MSC in advance.
- the MSC detects the restarting of the MME by e.g., health check.
- a call arrived from an originating side G-MSC CS incoming
- the MSC notifies the IMSI and the location registration area to the MME, which MME is able to call (page) the UE using the IMSI and the location registration area information.
- Figs.6 to 9 show networks to which the present invention may be applied.
- Fig.6 is a diagram showing a network configuration of an exemplary embodiment 1 of the present invention. Specifically, Fig.6 shows a packet communication network that accommodates LTE.
- the network includes a mobile station (UE) 101, a base station (eNodeB) 102, a MME 103, an HSS 106, an S-GW 104, a P-GW 105, an external network (PDN) 108 and an IMS 109.
- the IMS 109 is a communication system that integrates packet switched communication services by SIP (Session Initiation Protocol) to implement multi-media services.
- SIP Session Initiation Protocol
- the MME 103 accommodates the eNodeB 102 by an S1-MME interface to perform UE mobility management and authentication as well as setting of a user forwarding path.
- the MME 103 refers to the HSS 106 that is a database for managing subscriber information, through an S6a interface, to perform e.g., authentication.
- the MME 103 transmits/receives a control signal via S1-MME and S11 interfaces to set up or release the user forwarding path on an Sl- U interface between the eNodeB and the S-GW.
- the transport protocol at the S1-U interface between the eNodeB and the S-GW is GTP-U.
- An S5/S8 interface 107 is an interface (user plane) between S-GW and P-GW.
- a transport protocol a tunneling protocol (GTP-U) or a proxy mobile IP protocol (P-MIP), is set.
- GTP-U tunneling protocol
- P-MIP proxy mobile IP protocol
- the S-GW 104 performs user data transmission/reception between it and the eNodeB 102, while setting up or releasing an external PDN based transmission path via P-GW and S5/S8 interface 107.
- the P-GW 105 connects to the external network (PDN) 108 over an SGi interface. The following describes an operation when the MME restarts.
- Fig.10 is a sequence diagram that illustrates, as a first stage, a stage of registering location registration area information of the mobile station UE in the S-GW.
- the base station (eNodeB) 102 of Fig.6 is omitted. It is premised that the mobile station UE1 has set up a radio control link between it and the eNodeB. The respective steps of Fig.10 will now be described.
- the mobile station UE1 transmits a location registration request (Attach Request or TAU Request) to the MME1.
- a location registration request (Attach Request or TAU Request)
- the location of the mobile station UE in an idle (standby) mode is managed per location registration area information (tracking area).
- Each tracking area corresponds to a location area or a routing area in 3G/UMTS, and is composed of one or a plurality of cells. In each of these cells, an identifier of the tracking area to which the cell in question belongs is broadcasted.
- the mobile station in an idle mode has its location registered in the tracking area in which the mobile station UE resides, and stores the identifier of the tracking area in which the UE has its location currently registered.
- the mobile station UE When moving from one cell to another, the mobile station UE receives the identifier of the tracking area which is broadcasted. In case the identifier of the tracking area being broadcasted differs from the identifier of the tracking area, currently registered therein, the UE updates location registration. A request for update of this location registration is termed a 'TAU Request'.
- the MME1 newly assigns the location registration area information (TA List) to the mobile station UE1.
- TA List location registration area information
- the MME1 informs the S-GW1 about the TA List of the mobile station UE1 via S11 interface.
- the S-GW1 stores the TA List, informed from the MME1, in a storage unit (memory) in the S-GW1, as the registration information of the mobile station UE1.
- Fig.11 is a sequence diagram for illustrating, as a second stage, the stage of maintaining a bearer.
- the mobile station UE1 has already attached to the MME1 (an attach request has already been issued).
- a variety of bearers have already been set up using S-GW1 and P-GW1.
- a step 2 of Fig.11 the restarting of the MME1 occurs and in this MME1, the registration information of the UE1, already attached, is erased.
- the S-GW1 detects the restarting of the MME1, from processing such as a health check by GTP Echo processing.
- S-GW1 recognizes all mobile stations UE attached to the MME1 (it is confirmed that the UE1 is accommodated in the MME1).
- the bearer maintaining function according to the present invention is not provided for all services relating to the mobile station UE1, such that bearers (bearers used for IMS control) are maintained for specific services (IMS services providing e.g., voice services).
- the S-GW1 After confirming in the step S4 of Fig.11 that the mobile station UE1 has been accommodated in the MME1, the S-GW1 further confirms, in the step 6 of Fig.11 , whether or not there is a bearer(s) providing the IMS (bearer(s) used for IMS control) among the bearers owned by the mobile station UE1. In verifying the bearers used for IMS control in this manner, a QCI (QoS Class Identifier) value, which is among information elements that each bearer has, may be used.
- QCI QoS Class Identifier
- the bearer may be concluded to be the bearer(s) used for IMS control (IMS Signaling), in accordance with the Table 6.1.7 of Non-Patent Document 1 (3GPP TS23.03). The bearer may then be concluded to be a control bearer used for rendering voice services.
- IMS Signaling IMS Signaling
- the S-GW1 In case of maintaining the bearers used for IMS control (specific bearers), the S-GW1 starts the operation of a timer to release (remove) relevant bearer resources on timeout, in consideration of a case where the mobile station UE1 has already re-attached to another S-GW.
- This timer controls a time of maintaining the above mentioned specific bearer by the S-GW1, and becomes necessary to prevent failing to release the bearers that the S-GW1 maintains. If, in the above timer, the time equivalent to the time of a periodic location registration timer owned by the mobile station UE1 is set, the S-GW1 may wait for incoming of voice services for a necessary minimum time interval corresponding to the time of the next periodic location registration request from the UE1. At this time, the fact that the mobile station UE1 has not been registered in the MME1 is stored in the storage unit (memory) of the S-GW1.
- a step 7 of Fig.11 the mobile station UE1 is not registered in the MME1 and only the IMS control bearer is maintained in the S-GW1 and in the P-GW1. This completes the second stage.
- the S-GW1 removes the entirety of bearers (IMS control bearer resources) that the S-GW1 maintains in connection with the mobile station UE1, on timeout of the timer whose operation was started at the step S6 of Fig.11 .
- Fig.12 is a sequence diagram showing the operation of a third stage in case a signal has arrived in the second stage from the PDN such as IMS. The following describes respective stages.
- a notification from the IMSI indicating the incoming of voice services to the mobile station UE1, arrives at the G-SW1.
- the G-SW1 stores the information that the mobile station UE1 is in an unregistered state due to the restarting of the MME1. Hence, the G-SW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the previously registered TA List, to the MME1, to inform the incoming.
- Downlink Data Notification Downlink Data Notification
- the MME1 performs paging of the mobile station UE1 for the received TA List, using the IMSI.
- the mobile station UE1 has already selected another S-GW and has attached to the MME1.
- the MME1 returns a downlink data notification acknowledge (Downlink Data Notification Acknowledge) response indicating the cause that the UE1 has already attached.
- Downlink Data Notification Acknowledge Downlink Data Notification Acknowledge
- the mobile station UE1 performs the attachment operation on receipt of the paging employing the IMSI.
- the S-GW When the S-GW detects the restarting of the MME, if the tunnel (GTP-U) on the S1-U interface between the eNodeB and the S-GW is active, the S-GW releases the tunnel.
- GTP-U tunnel
- the following describes the operation at the time of SGSN restarting in the network configuration of Fig.7 .
- the operation of the exemplary embodiment 2 is equivalent to the operation at the time of restarting of MME in the exemplary embodiment 1.
- 2G/3G is accommodated.
- the eNodeB 102 and the MME 103 of Fig.6 are replaced by a 2G/3G radio control apparatus (nodeB and RNC) 110 and an SGSN 111.
- An interface between the 2G/3G radio control apparatus (NodeB and RNC) 110 and the SGSN 111 is Iu
- an interface between the 2G/3G radio control apparatus (NodeB and RNC) 110 and the S-GW 104 is S12
- an interface between the SGSN and the S-GW is S4
- an interface between the SGSN 111 and the HSS 106 is an S6d/Gr.
- Fig.13 is a sequence diagram showing a stage of registering the location registration area information of the mobile station UE in the S-GW1, as a first stage. The following describes respective steps.
- the mobile station UE1 sends a location registration request (Attach Request/Routing Area Update Request) to the SGSN1.
- the Routing Area Update Request is a location registration update request to the SGSN.
- the SGSN1 newly assigns the location registration area information (RAI) to the mobile station UE1.
- RAI location registration area information
- the SGSN1 notifies the S-GW1 of the RAI of the mobile station UE1.
- the S-GW1 maintains the RAI notified as the registration information of the mobile station UE1.
- Fig.12 The location registration operation of Fig.12 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, the configuration is not explained in detail.
- Fig.14 is a sequence diagram for the stage of maintaining a bearer, as a second stage. The following describes respective steps.
- a step S1 of Fig.14 the mobile station UE1 has already attached to the SGSN1, and a various types of bearers have been set up using the S-GW1 and P-GW1.
- a step 2 of Fig.14 the processing of restarting occurs in the SGSN1.
- the registration information of the mobile station UE1 attached is erased.
- the S-GW1 detects the restarting at SGSN1 by processing, such as a health check, by GTP Echo processing.
- the S-GW1 recognizes the entirety of the mobile stations UE (it is confirmed that the mobile station UE1 is accommodated in SGSN1).
- bearers are not maintained for the entirety of the services, as is done in the step 5 of Fig.11 . Instead, just a bearer relating to a specific service (IMS service, providing e.g., voice services, in the following example) is maintained.
- IMS service providing e.g., voice services, in the following example
- the S-GW1 confirms, in a step 6 of Fig.14 , whether or not there is the IMS signaling bearer among the bearers held by the mobile station UE1.
- the IMS signaling bearer is a bearer used for IMS control. In determining whether or not a bearer in question is the IMS control bearer, the value of a QCI (QoS Class Identifier), which is one of the control elements owned by each bearer, for example, may be used.
- QCI QoS Class Identifier
- a bearer in question is determined to be the IMS control (IMS signaling) bearer in accordance with Table 6.1.7 of Non-Patent Document 1 (3PP TS23.203).
- the bearer in question may thus be determined to be a control bearer used for providing voice services. If there is such IMS control bearer, the S-GW1 maintains just such bearer, and locally releases (removes) other bearers in accordance with the operation of Non-Patent Document 1 (3GPP TS23.007).
- the operation of a timer which on timeout releases the bearer, is started in order to take account of the case where the mobile station UE1 has already attached to another S-GW 1 .
- This timer is necessary to prevent failing to release bearers that the S-GW1 maintains.
- the S-GW1 may wait for incoming of voice services for a necessary minimum time corresponding to the time of the next periodic location registration request from the UE1. At this time, the fact that the mobile station UE1 has not been registered in the SGSN1 is stored in the S-GW1.
- the SGSN1 is in such a state that the mobile station UE1 has not been registered and that only the IMS control bearer is maintained in the S-GW1 and in the P-GW1.
- the S-GW1 removes the entirety of the bearers maintained in connection with the mobile station UE1 (IMS control bearer resources) at a timeout time point of the timer whose operation started in the step 6 of Fig.14 .
- Fig.15 is a sequence diagram for illustrating the operation of a third stage in case of an incoming from PDN, such as IMS.
- incoming notification of voice services from IMS1 to the mobile station UE1 gets to the S-GW1.
- the S-GW1 sends the IMSI and the downlink data notification (Downlink Data Notification) inclusive of IMSI and RAI that have been registered in advance to the MME to inform the incoming. It is because the S-GW1 stores that the mobile station UE1 is in a non-registered state because of restarting of the SGSN1.
- the downlink data notification Downlink Data Notification
- the SGSN1 in a step S3 in Fig.15 performs paging of the mobile station UE1, for RAI received, using the IMSI.
- the mobile station UE1 has already selected another S-GW and has attached to the SGSN1.
- the SGSN1 sends back to the S-GW1 a downlink data notification acknowledge (Downlink Data Notification Acknowledge) response indicating the cause that the UE1 has already attached.
- Downlink Data Notification Acknowledge Downlink Data Notification Acknowledge
- a step 4 of Fig.15 the mobile station UE1 that has received the paging employing the IMSI performs an attachment operation.
- the attachment operation of the mobile station UE of the step S4 of Fig.15 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, its detailed configuration is omitted.
- the following describes the operation in case of employing an ISR function (LTE/3G location registration omitting function) under the network configuration of Fig.8 .
- ISR the mobile station UE registers its location in both the MME and the SGSN.
- UE location registration is omitted as long as there is no change in the previously registered location registration area in LTE and that in 2G/3G.
- Fig.8 shows a packet communication network configuration accommodating LTE and 2G/3G. This configuration corresponds to the configuration of Fig.1 added by a 2G/3G radio control apparatus 110 and an SGSN 111 to be connected to the mobile station UE 101.
- the MME 103 is connected to the SGSN 111 via an S3 interface, while the MME 103 and the SGSN 111 are connected to the HSS 106 via an S6a interface and an S6d/Gr interface.
- the S-GW 104 is connected to the SGSN 111 and to the MME 103 via an S4 interface and via an S11 interface.
- Fig.13 The processing of location registration for the UE1 from 2G/3G, as a first stage, is shown in Fig.13 .
- Fig.10 may apply as regards the processing of location registration from LTE.
- the S-GW1 maintains RAI and TA List as the location registration area information.
- the processing of location registration during the ISR operation is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, its detailed configuration is omitted.
- Fig.16 is an example of a sequence as an operation in case of restarting of the MME1 of Fig.8 .
- Fig.17 shows an example of a sequence as an operation in case of restarting of the SGSN1 of Fig.8
- the mobile station UE1 has its location registered in the MME1, and a various types of bearers have been established using the S-GW1 and the P-GW1.
- a step 2 of Fig.16 restarting occurs in the MME1, so that the registration information of the mobile station UE1 in the MME1 is erased.
- the S-GW1 detects the restarting of the MME1 from processing, such as a health check by the GTP Echo processing.
- the S-GW1 does not perform releasing of bearers because the S-GW1 knows that the mobile station UE1 attached to the MME1 has been registered using the SGSN1 and the ISR function. At this time, the fact that the mobile station UE1 is not registered in the MME1 is stored in an internal memory of the S-GW1. However, in case the SGSN1 has already been restarted, the processing according to the present invention (processing of maintaining the bearer relevant to the mobile station UE1) is carried out as is the processing of Fig.11 .
- the mobile station UE1 has its location registered in SGSN1, and a various types of bearers have already been set up using the S-GW1 and the P-GW1.
- a step 3 of Fig.17 the processing of restarting, for example, occurs in the SGSN1, and the registration information of the mobile station UE1, which has its location registered, is erased.
- the S-GW1 detects the restarting of the SGSN1 from processing such as a health check by the GTP Echo processing.
- the S-GW1 does not perform bearer releasing because the S-GW1 knows that the mobile station UE1 attached to the MME1 has been registered using the MME1 and the ISR function.
- the non-registration status of the mobile station UE1 in the SGSN1 is stored in the internal memory of the S-GW1.
- the processing according to the present invention processing of maintaining the bearer relevant to the mobile station UE1 is carried out as with the processing of Fig.14 .
- Fig.18 is a diagram showing an example of a sequence of the operation in case there is an incoming from the PDN under a condition that the MME1 of Fig.8 has restarted, as a third stage.
- Fig.19 is a diagram showing an example of a sequence of the operation in case there is an incoming from the PDN under a condition that the SGSN1 of Fig.8 is restarted.
- Fig.20 is a diagram showing an example of a sequence of the operation in case there is an incoming from the PDN under a condition that both the MME1 and the SGSN1 of Fig.8 are restarted.
- the S-GW1 sends a normal downlink data notification (Downlink Data Notification) to the SGSN1 to inform the incoming.
- a normal downlink data notification Downlink Data Notification
- the S-GW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the pre-registered TA List, to the MME1 to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 on account of the restarting of the MME1.
- Downlink Data Notification Downlink Data Notification
- the SGSN1 performs normal paging (paging of the mobile station responsive to the incoming).
- the MME1 performs paging of the mobile station UE1, using the IMSI, by referring to the TA List received.
- paging employing the IMSI is received at LTE, the mobile station UE1 performs an attachment operation.
- incoming notification of communication services from the PDN1 to the mobile station UE1 gets to the S-GW1.
- the S-GW1 sends a normal downlink data notification (Downlink Data Notification) to the MME1 to inform the incoming.
- a normal downlink data notification Downlink Data Notification
- the S-GW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the pre-registered RAI, to the SGSM1, to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 on account of the restarting of the MME1.
- Downlink Data Notification Downlink Data Notification
- the SGSN1 performs normal paging.
- the SGSM1 performs the paging of the mobile station UE1, using the IMSI, by referring to the RAI received.
- a step 6 of Fig.19 in case the paging employing the IMSI is received in 2G/3G, the mobile station UE1 performs an attachment operation.
- incoming notification of communication services from the PDN1 to the mobile station UE1 gets to the S-GW1.
- the S-GW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the pre-registered TA List, to the MME1, to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 on account of the restarting of the MME1.
- Downlink Data Notification Downlink Data Notification
- the S-GW1 sends a downlink data notification, inclusive of the IMSI and the pre-registered TA List, to the SGSN1, to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 which is due to the restarting of the MME1.
- a step 4 of Fig.20 in case the mobile station UE1 having the IMSI according to the notification is not attached, the MME1 performs paging of the mobile station UE1, using the IMSI, by referring to the TA List received.
- a step 5 of Fig.20 in case the mobile station UE1 having the IMSI according to the notification is not attached, the SGSN1 performs paging of the mobile station UE1, using the IMSI, by referring to the RAI received.
- the mobile station UE1 when receiving the paging employing the IMSI, the mobile station UE1 performs an attachment operation.
- Fig.9 is a diagram showing a network configuration according to a fourth exemplary embodiment according to the present invention.
- the network includes a mobile station (UE) 101, a base station (eNodeB) 102, an MME 103, an HSS 106, an MSC/VLR 112, a CS network 113 and a G-MSC (gateway mobile switch center) 114.
- UE mobile station
- eNodeB base station
- MME 103 mobile station
- HSS 106 HSS
- MSC/VLR 112 MSC/VLR 112
- G-MSC gateway mobile switch center
- a signal notifying the incoming is sent from the G-MSC 114 as an originating source to the MSC/VLR 112 via the CS network 113.
- the MSC/VLR 112 identifies the corresponding MME 103 from the incoming information to send a paging request message (Paging-Request-Message) to the MME 103.
- the MME 103 sends a paging signal to the mobile stations that reside in the serving area.
- This paging signal includes information indicating that the paging is for CS services.
- the mobile station UE 101 recognizes this information, that is, the information that the paging is that for CS services, and sends a CS service request signal to the MME 103.
- the MME sends a handover command to the UE1.
- the mobile station (UE) 101 performs handover, while switching to 3G.
- the mobile station UE 101 which has switched to 3G, sends a paging response to the MSC/VLR 112, as a result of which the voice services at the mobile station to the incoming voice are started.
- the following describes the operation when the MME restarts.
- the operation according to the present invention may be summarized to have three separate stages.
- Fig.21 is a sequence diagram showing, as a first stage, the stage of registering location registration area information of the mobile station UE. The following describes respective steps.
- the mobile station UE1 makes a location registration request for CSFB (Attach Request, TAU Request and so forth) to the MME1.
- CSFB Acttach Request, TAU Request and so forth
- the MME1 newly assigns (delivers) the location registration area information (TA List) to the mobile station UE1.
- the MME1 notifies the MSC1 of the TAU List of the mobile station UE1.
- the MSC1 maintains the TAU List, notified from the MME1, as the registration information of the mobile station UE1.
- Fig.21 The location registration operation of Fig.21 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, the detailed configuration is omitted.
- Fig.22 is a sequence diagram showing, as a second stage, the stage of maintaining a bearer. The following describes respective steps.
- a step 1 of Fig.22 the mobile station UE1 has already attached to the MME1.
- restarting occurs in the MME1 and the registration information of the mobile station UE1 is erased.
- the MSC1 detects the restarting of the MME1 from processing such as a health check by the SCTP.
- the MSC1 recognizes the entirety of the mobile stations UE attached to the MME1 (it is recognized that the mobile station UE1 is accommodated in MME1). The above is the second stage.
- Fig.23 depicts an example sequence diagram showing, as a third stage, an operation sequence for the case of incoming (voice incoming or SMS, for example) via a CS domain. The following describes respective steps.
- an incoming notification to the mobile station UE1 arrives at the MSC1 by e.g., the G-MSC.
- the MSC1 sends a paging request message inclusive of IMSI and pre-registered TA List (SGsAP-PAGING-REQUEST message) to the MME1 to notify the MME1 of the incoming. It is because the MSC1 stores the non-registered state of the mobile station UE1 brought about by restarting of the MME1.
- the MME1 performs a paging of the mobile station UE1, using the IMSI, for the TA List received.
- the MME1 sends back to the MSC1 a paging reject message (SGsAP-PAGING-REJECT message) indicating the cause that the UE1 has already attached.
- a paging reject message SGsAP-PAGING-REJECT message
- the mobile station UE1 which has received the paging that uses the IMSI, performs an attachment operation.
- the attachment operation of the mobile station UE in the step 4 of Fig.23 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, the configuration is omitted.
- P-GW1 P-GW1
- P-GW2 P-GW3
- P-GWN P-GWN
- FIG.24 which supplements Fig.10 , for example, and shows subscriber data re-installation by network triggered service request. It is noted that the eNodeB is omitted in Fig.24 .
- the MME sends the latest TA-list to a relevant S-GW. That is, the MME informs the latest TA-list on a per UE basis to one or more S-GWs in every occurrence of mobility events.
- This information (TA list) is important in case of MME failure because paging of the IMSI for the coverage of the MME in its entirety may thereby be avoided. Since larger numbers of eNodeBs are accommodated in one MME, the load in the EPS system may become tremendously severe if paging is to be performed for the entire coverage.
- the relevant S-GW detects MME failure by this GTP echo mechanism.
- the S-GW is able to maintain all or selected bearers, IMSI and the TA list.
- An operator is able to select a bearer based on top-rank services (IMS) (service on top (IMS)), as a result of which the bearer maintained may be selected only for important services.
- IMS top-rank services
- the S-GW starts a timer that controls a time interval for maintaining bearer resources, for example. On timeout of the timer, the bearer resources maintained are removed.
- This alternative is needed for such case in which, when the UE re-attaches to a network, the S-GW in question is not selected. That is, on timeout of the timer of the S-GW in question, the above mentioned bearer resources maintained, for example, S5/S8 bearers, which are specific bearers maintained, are removed on the assumption that the UE has re-attached to the network via a S-GW different from the S-GW in question.
- the S-GW acquires the DL data from the P-GW.
- the S-GW sends a downlink data notification message inclusive of the IMSI and the TA list (DL data notification (IMSI, TA list)) to the MME.
- IMSI DL data notification
- TA list DL data notification
- the MME starts the IMSI page ((Page (IMSI) to TAs specific in TA list) for all of TAs of the TA list received from S-GW.
- the mobile station UE1 On receiving the IMSI page, the mobile station UE1 starts the attach (ATTACH) procedure.
- ATTACH attach
- the MME On receiving the attach (ATTACH) request from the UE, the MME sends a location information update request to the HSS.
- the HSS sends location information update acknowledge to the MME.
- the MME sends the ATTACH acceptance to the mobile station UE via eNodeB.
- the S-GW In case of detecting the restart of the MME, the S-GW maintains the bearer, IMSI or the TA list. In this manner, it is possible to instantaneously recover communication services after restart of the MME and after arrival of the DL data at the UE from the PDN side.
- a mode of the present invention in case only the selected bearer is to be maintained, it is possible to suppress consumption of S-GW resources.
- communication services may instantaneously be restored for services of higher rank of importance, such as voice communication, on arrival of an incoming to the mobile station, after the restarting of the MME.
- the time interval of the maintenance is managed by a timer.
- the bearer, IMSI and the TA list maintained are released.
- UE's communication services may be improved in availability by adding packet incoming as a re-registration trigger of a UE registered in the MME/SGSN in which restarting occurred.
- incoming of the entirety of the packets may be used as a trigger for restoring the UE to the network. It may however be thought that many resources on the S-GW side are used, and that location registration events may become concentrated.
- the S-GW1 is able to maintain the TA list and to perform the Paging processing by using the TA list. However, if it is not possible for the S-GW to receive the TA list from the MME1, the paging may be performed for the whole area supervised by the MME1. In this case, many of the radio network side resources would be consumed.
- the S-GW1 is able to maintain the RAI and to perform Page processing by using the RAI. If it is not possible for the S-GW1 to receive the RAI from the SGSN1, paging may be performed for the total areas supervised by the SGSN. In this case, many of the radio network side resources would be consumed.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Abstract
Description
- The present application asserts priority rights based on
JP Patent Application 2010-102166 filed on April 27, 2010 - This invention relates to a communication network and, more particularly, to a system and a method as well as an apparatus that may be applied to advantage to the next-generation mobile network system EPC (Evolved Packet Core).
- The following recites certain abbreviations used in the present specification.
-
- CS: Circuit Switched
- CSFB: Circuit Switched Fall Back
- eNodeB (eNB): evolved NodeB
- G-MSC: Gateway Mobile Switch Center
- GPRS: General Packet Radio Service
- GTP-C: (GPRS Tunneling Protocol Control Plane)
- GTP-U: (GPRS Tunneling Protocol User Plane)
- P-MIP: Proxy Mobile Internet Protocol
- HSS: Home Subscriber Server
- IMS: IP Multimedia Subsystem
- IMSI: International Mobile-Station Subscription Identifier
- ISR: Idlemode Signaling Reduction
- LTE: Long Term Evolution
- MME: Mobility Management Entity
- MSC: Mobile Switching Center
- MTC: Machine type communication
- P-GW: (PGW or PDN-GW): Packet Data Network Gateway
- PDN: Packet Data Network
- QCI: QoS Class Identifier
- RAI: Routing Area Identity
- RNC: Radio Network Controller
- S-GW (or SGW): Serving Gateway
- SGSN: Serving GPRS Support Node
- SMS: Short Message Service
- SCPT: Stream Control Transmission Protocol
- TA List: Tracking Area List
- TAU: Tracking Area Update
- TEID: Tunnel Endpoint Identifier
- GRE key: Generic Routing Encapsulation Key
- UE: User Equipment
- UMTS: Universal Mobile Telecommunications System
- VLR: Visited Location Register
- 3G: Third Generation
- 3GPP: 3rd Generation Partnership Project
- The next-generation mobile network system EPC is a network architecture that accommodates 3G (third generation mobile phone communication system), LTE and so forth in one network. The following describes several network nodes.
- A MME is a mobility management node. In LTE radio access, the MME takes charge of mobility management (mobility control), such as tracking, of an idle-mode mobile station UE, authentication and setting up a user data forwarding path between an S-GW and a base station eNodeB, in LTE radio access. A mobile station is also termed 'a user apparatus', 'a mobile terminal' or simply 'a terminal'. The MME is involved in tracking and paging of idle-mode UEs or in bearer activate/deactivate processes. The MME selects the S-GW at the time of handover of the UE in LTE and performs user authentication along with HSS. It is noted that a bearer means a logical packet transmission path set up between eNodeB and S-GW/P-GW or the like.
- An SGSN is a mobility management node in the 3G core network. It is a packet switching unit that takes charge of mobility management for mobile stations, such as serving subscriber management, serving subscriber mobility management, originating/incoming call control, tunneling control, charging control, QoS (Quality of Service) control or the like.
- When a mobile terminal (UE) is in an idle or power-saving state (LTE-idle) in an LTE core network, the mobile station (UE) is identified at the accuracy corresponding to a tracking area list (TA List) composed of a plurality of cells (MME maintains the latest updated TA List). At the time of an incoming call to the mobile station, paging is performed using the latest TA List registered last time. The SGSN of the 3G core network performs paging in an RA (Routing Area).
- An S-GW performs routing and forwarding of a user data packet. The S-GW is a bearer management node that manages context of a mobile station UE (a parameter of IP bearer service or the like). In response to a bearer setting request from an MME that has received an attach request from a mobile station UE, The S-GW sets a path setting request for a P-GW and bearer in the direction of an eNode. The S-GW also performs triggering of a paging when the downlink (DL) data to a terminal has arrived.
- A P-GW takes charge of connection of a mobile station (also termed a UE, a user apparatus or a mobile terminal) to a packet data network (a service network: Web browsing service or an external network, such as IMS or the like.
- The following describes restarting of MME/SGSN.
- The 'restart' or 'restart of MME/SGSN' means cessation of service due to failure, or intentional cessation of service for maintenance, that leads to initialization setting operation in the MME/SGSN, as a result of which, subscriber information or bearer information that is necessary for the MME/SGSN operation to operate is lost.
- Non-Patent Document 2 (3GPP TS 23.007) provides that, when the S-GW detects that an MME /SGSN has restarted, the S-GW is to release bearer context of a mobile station UE registered in the MME/SGSN that has restarted. That is, According to Non-Patent
Document 2, when the MME re-starts after failure, the MME removes the entirety of bearer contexts affected by the restarting. When the S-GW detects that the MME has restarted, the S-GW removes PDN connection table/bearer context corresponding to the MME that has restarted and releases inner resources relevant to the PND connection. - Assuming that an S-GW operates in accordance with the above specification of the
Non-Patent Document 2, when the MME operation has restarted, the S-GW is unable to effect a packet incoming operation to a mobile station UE until originating a call by the mobile station itself or periodic location registration (e.g., Attach/TAU Request) periodically by performed by the mobile station itself to the MME. - When there is an incoming call to the mobile station UE, the network performs paging all at once to whole cells associated with an area where the mobile station UE has made location registration (tracking area). The so paged mobile station UE accesses a serving cell and establishes a call. However, according to the specification of
Non-Patent Document 2, the entirety of bearer information or resources of the restarted MME has already been removed or released. That is, in the S-GW, radio access bearers in the direction of from the S-GW to the eNodeB and session information between the MME and the S-GW have been removed or released, so that when the incoming packet data to the mobile station UE is received only to no effect. - In the S-GW in this state, TEID or GRE Key, as the identification information of a tunnel (GTP-U or P-MIP), a transport protocol between the S-GW and the P-GW, also has been removed. Hence, in the S-GW, the incoming data is rejected. The P-GW also removes relevant resources in response to the rejection of the incoming packet data from the S-GW.
-
- Non-Patent Document 1:
- 3GPP TS 23.203 V9.4.0 (2010-03) 3rd Generation Partnership Project: Technical Specification Group Services and System Aspects: Policy and charging control architecture (Release 9), page 31, Table 6.1.7: Standardized QCI characteristics
- Non-Patent Document 2:
- 3GPP TS 23.007 V9.3.0 (2010-03) 3rd Generation Partnership Project: Technical Specification Group Core Network and Terminals; Restoration procedures (Release 9), pages 27-28
- Non-Patent Document 3:
- 3GPP TS 23.272 V9.3.0 (2010-03) 3rd Generation Partnership Project: Technical Specification Group Services and System Aspect; Circuit Switched (CS) fallback In Evolved Packet System (EPS); Stage 2 (Release 9) pages 26-27
- The disclosures of the
Non-Patent Documents 1 to 3 are incorporated by reference into the present specification. The following is an analysis of the related techniques. - In case the S-GW operates in accordance with the above specification of
Non-Patent Document 2, as described above, the S-GW which has detected the restarting of the mobility management node MME/SGSN releases entirety of bearers of the mobile station UE registered in the MME/SGSN where restarting occurred. - Hence, the incoming to the mobile station UE after the restarting of the mobility management node MME/SGSN may not be informed to the mobile station UE until such time the attach operation for registration in the network is carried out in the mobile station UE. That is, if, during the time that elapses after restarting of the MME/SGSN until the end of the attachment operation, triggered by the origination by the mobile station UE itself or the periodic location registration by the mobile station UE, the mobile station UE is unable to have a communication service, even if there is an incoming of the communication service. For example, during a time interval of the periodic location registration (e.g., 45 minutes), at the maximum, following the restarting of the MME/SGSN, incoming packet data, addressed to the mobile station UE, may not be delivered to the mobile station UE.
- That is, a packet communication service is at a standstill. This poses a serious problem since communication services as social infrastructure may not be received for a preset time in case IMS is exploited on an EPS network.
- Accordingly, it is an object of the present invention to provide a system, a method and an apparatus which enable to accelerate restoration of communication services for a mobile station after restarting of a mobility management node.
- In accordance with one aspect of the present invention, there is provided a communication method in which a bearer management node maintains a specific bearer eligible for restoration of communication services, and removes the other bearers. In case a mobility management node is restarted, the bearer management node maintains at least one bearer.
- In accordance with another aspect of the present invention, there is provided a communication method wherein, on restarting of a mobility management node, a circuit switched node sends to the mobility management node a notification message including identification information associated with an mobile station and location registration area information, and the mobility management node starts paging, inclusive of the identification information associated with the mobile station, for an area corresponding to the location registration area information.
- According to the present invention, there is also provided a mobile network system in which a bearer management node maintains a specific bearer eligible for restoration of communication services, and removes other bearers. The mobile network system includes a mobility management node and a bearer management node. When restarting of the mobility management node is performed, the bearer management node maintains at least one of the bearers as set.
- According to the present invention, there is provided a mobile network system comprising a mobility management node and a circuit switched node. In case restarting of the mobility management node is performed, the circuit switched node sends to the mobility management node a notification message inclusive of the identification information associated with the mobile station and the location registration area information. The management node performs paging including the identification information associated with the mobile station for an area corresponding to the location registration area information.
- According to the present invention, there is provided a node apparatus that manages a bearer, wherein the node apparatus maintains a specific bearer eligible for restoration of communication services, and removes other bearers. In case restarting of the mobility management node is performed, the node apparatus maintains at least one of the bearers as set.
- According to the present invention, it is possible to accelerate restoration of a communication service for a mobile station following restarting of a mobility management node.
-
-
Fig.1 is a diagram for illustrating the operation of a mode of the present invention. -
Fig.2 is another diagram for illustrating the operation of the mode of the present invention. -
Fig.3 is yet another diagram for illustrating the operation of the mode of the present invention. -
Fig.4 is yet another diagram for illustrating the operation of the mode of the present invention. -
Fig.5 is yet another diagram for illustrating the operation of the mode of the present invention. -
Fig.6 is a diagram for illustrating a packet communication network that accommodates LTE. -
Fig.7 is a diagram for illustrating a packet communication network that accommodates 2G/3G. -
Fig.8 is a diagram for illustrating a packet communication network that accommodates LTE and 2G/3G. -
Fig.9 is a diagram for illustrating CSFB (Circuit Switch Fall Back). -
Fig.10 is a diagram for illustrating an example sequence of anexemplary embodiment 1 of the present invention. -
Fig.11 is a diagram for illustrating another example sequence of theexemplary embodiment 1 of the present invention. -
Fig.12 is a diagram for illustrating yet another example sequence of theexemplary embodiment 1 of the present invention. -
Fig.13 is a diagram for illustrating an example operating sequence of anexemplary embodiment 2 of the present invention. -
Fig.14 is a diagram for illustrating another example operating sequence of theexemplary embodiment 2 of the present invention. -
Fig.15 is a diagram for illustrating yet another example operating sequence of theexemplary embodiment 2 of the present invention. -
Fig.16 is a diagram for illustrating an example operating sequence of anexemplary embodiment 3 of the present invention. -
Fig.17 is a diagram for illustrating another example operating sequence of theexemplary embodiment 3 of the present invention.Fig.18 is a diagram for illustrating an example operating sequence of anexemplary embodiment 4 of the present invention. -
Fig.19 is a diagram for illustrating another example operating sequence of theexemplary embodiment 4 of the present invention. -
Fig.20 is a diagram for illustrating yet another example operating sequence of theexemplary embodiment 4 of the present invention. -
Fig.21 is a diagram for illustrating an example operating sequence of anexemplary embodiment 5 of the present invention. -
Fig.22 is a diagram for illustrating another example operating sequence of theexemplary embodiment 5 of the present invention. -
Fig.23 is a diagram for illustrating yet another example operating sequence of theexemplary embodiment 5 of the present invention. -
Fig.24 is a diagram for illustrating an example operating sequence of a mode of the present invention. - In one of preferred modes of the present invention, when a mobility management node, such as MME/SGSN, has restarted, a bearer management node S-GW does not release all of bearers relevant to the mobility management node MME/SGSN. The bearer management node (S-GW) holds at least part of or entirety of bearers to continue a packet incoming service. That is, when the bearer management node, such as S-GW, detects restarting of the mobility management node (MME/SGSN), the bearer management node confirms that the mobile station UE is accommodated in the mobility management node (MME/SGSN). In connection with the mobile station (UE), accommodated in the mobility management node (MME/SGSN), the bearer management node, such as S-GW, retains at least one of bearers set in a direction from the bearer management node (S-GW) towards the external network, such as PDN. By so doing, the mobile station (UE) is able to attach to the network, with packet incoming from the external network (PDN) to the mobile station (UE) as a trigger, thereby accelerating the restoration of a communication service for the mobile station (UE). In one of preferred modes of the present invention, the bearer management node maintains a specific bearer(s) for restoring a communication service, and removes other bearers. In one of preferred modes of the present invention, when maintaining the specific bearer, the bearer management node may start a timer. On timeout of the timer, the bearer management node may remove bearer resources that have been maintained.
- In one of preferred modes of the present invention, it is possible to select those bearers that render services of high reliability after restarting of the mobility management node (MME/SGSN). It is thus possible to suppress consumption of resources of the bearer management node (S-GW) as well as to avoid congestion due to concentration of location registrations.
- In one of preferred modes of the present invention, the bearer management node S-GW maintains the location registration area information (TA List/RAI) of the mobile station (UE), informed from the mobility management node (MME/SGSN), and the identification information (IMSI) associated with the mobile station. After restarting of the mobility management node (MME/SGSN), the bearer management node (S-GW) may, on receipt of incoming data to the mobile station (UE), notify the location registration area information (TA list/RAI) and the identification information (IMSI) to the mobility management node (MME/SGSN). The mobility management node (MME/SGSN) may then perform paging, using the identification information (IMSI), for only the area corresponding to the location registration area information (TA list/RAI). By so doing, it is possible to selectively reduce an area that is paged by the base station.
-
Fig.1 is a diagram for illustrating one of modes of the present invention. A mobility management node MME/SGSN that manages registration information of a mobile station UE, notifies the location registration information of the mobile station UE to an S-GW at the outset. The S-GW maintains the location registration information of the mobile station UE. The S-GW also maintains bearers between the S-GW and the P-GW. - Restarting occurs at the mobility management node MME/SGSN.
- When the S-GW detects, by e.g., health check, that the mobility management node MME/SGSN has restarted, the S-GW does not release but maintains bearers that are set between the S-GW and the P-GW. In this case, in view of compatibility of the stable system restoration and availability of communication services, it is possible for the S-GW not to release but continue to maintain those bearers that will provide for high availability services. These services may be exemplified by communication that is in need of high reliability in accordance with, e.g., of the operator policy, such as voice services provided by IMS. For example, the S-GW may not release but maintain specific S5/S8 bearers between the S-GW and the P-GW, necessary for restoration of services initiated from the network side, and to remove all the other S5/S8 bearers.
- In an example shown in
Fig.2 , when the S-GW detects, by e.g., health check (GTP-echo), that the mobility management node MME/SGSN has restarted, the S-GW releases IMS control bearer services, among bearers set between the S-GW and the P-GW, while maintaining just the bearers used for IMS control. By thus applying to just specific services, it is also possible to gradually restore the MME/SGSN while overload on the entire system is avoided. -
Fig.3 is a diagram for illustrating the case of applying the present invention to IMS services. When packet data has arrived, using the bearer held by the S-GW, the packet incoming is notified, along with the IMSI identifying the UE and the location registration area information, registered beforehand in the S-GW, to the MME/SGSN where the restarting has occurred. The MME/SGSN is thus able to cal 1(page) the UE using the IMSI and the location registration area information. The mobile station UE that has been paged using the IMSI, performs re-registering (attach) to the MME/SGSN and re-establishes necessary bearers to receive the entirety of packet communication services. Thus, according to a mode of the present invention, even if the MME/SGSN restarts, service arrival may be notified to the mobile station UE to prompt its attachment to the MME to improve availability of communication services. - According to a mode of the present invention, it is possible to cause the UE to attach to the network, after restarting of the MME/SGSN, with the incoming of the packet to the UE as a trigger. Packet communication services may instantaneously be restored to the UE whose services have been started by the arrival of the incoming packet.
- In a mode of the present invention, just those bearers that need high reliability may be taken as bearers to be maintained according to the present invention. It is thus possible to suppress consumption of S-GW resources as well as congestion due to concentration of location registrations. This operation is indispensable especially in case a UE where packet communication occurs periodically, as in MTC, is accommodated. The reason is that, in such case, packet communication occurs for many UEs after restarting of the MME/SGSN, and hence the subscriber recovering operations may occur in a burst fashion, with the packet communication as a trigger, thus possibly leading to congestion of the system in its entirety.
-
Figs.4 and5 are diagrams showing an example in which the present invention is applied to CSFB. The CSFB function switches voice origination/incoming to 3G to render voice services employing the 3G-CS domain even in case VoIP services are not provided on LTE. As regards the CSFB function, reference is to be made to Non-Patent Document 3 (Figure 7 .2-1 Mobile Termination Call in idle mode). - Referring to
Fig.4 , the MME notifies the UE's location registration information to an MSC in advance. When the MME restarts, the MSC detects the restarting of the MME by e.g., health check. Referring toFig.5 , when a call arrived from an originating side G-MSC (CS incoming), the MSC notifies the IMSI and the location registration area to the MME, which MME is able to call (page) the UE using the IMSI and the location registration area information. - The following describes exemplary embodiments of the present invention.
Figs.6 to 9 show networks to which the present invention may be applied. -
Fig.6 is a diagram showing a network configuration of anexemplary embodiment 1 of the present invention. Specifically,Fig.6 shows a packet communication network that accommodates LTE. Referring toFig.6 , the network includes a mobile station (UE) 101, a base station (eNodeB) 102, aMME 103, anHSS 106, an S-GW 104, a P-GW 105, an external network (PDN) 108 and anIMS 109. TheIMS 109 is a communication system that integrates packet switched communication services by SIP (Session Initiation Protocol) to implement multi-media services. - The
MME 103 accommodates theeNodeB 102 by an S1-MME interface to perform UE mobility management and authentication as well as setting of a user forwarding path. TheMME 103 refers to theHSS 106 that is a database for managing subscriber information, through an S6a interface, to perform e.g., authentication. TheMME 103 transmits/receives a control signal via S1-MME and S11 interfaces to set up or release the user forwarding path on an Sl- U interface between the eNodeB and the S-GW. The transport protocol at the S1-U interface between the eNodeB and the S-GW is GTP-U. - An S5/
S8 interface 107 is an interface (user plane) between S-GW and P-GW. As a transport protocol, a tunneling protocol (GTP-U) or a proxy mobile IP protocol (P-MIP), is set. - The S-
GW 104 performs user data transmission/reception between it and theeNodeB 102, while setting up or releasing an external PDN based transmission path via P-GW and S5/S8 interface 107. The P-GW 105 connects to the external network (PDN) 108 over an SGi interface. The following describes an operation when the MME restarts. -
Fig.10 is a sequence diagram that illustrates, as a first stage, a stage of registering location registration area information of the mobile station UE in the S-GW. InFig.10 , the base station (eNodeB) 102 ofFig.6 is omitted. It is premised that the mobile station UE1 has set up a radio control link between it and the eNodeB. The respective steps ofFig.10 will now be described. - In a
step 1 ofFig.10 , the mobile station UE1 transmits a location registration request (Attach Request or TAU Request) to the MME1. Note that, in LTE, the location of the mobile station UE in an idle (standby) mode is managed per location registration area information (tracking area). Each tracking area corresponds to a location area or a routing area in 3G/UMTS, and is composed of one or a plurality of cells. In each of these cells, an identifier of the tracking area to which the cell in question belongs is broadcasted. The mobile station in an idle mode has its location registered in the tracking area in which the mobile station UE resides, and stores the identifier of the tracking area in which the UE has its location currently registered. When moving from one cell to another, the mobile station UE receives the identifier of the tracking area which is broadcasted. In case the identifier of the tracking area being broadcasted differs from the identifier of the tracking area, currently registered therein, the UE updates location registration. A request for update of this location registration is termed a 'TAU Request'. - In a step S2 of
Fig.10 , the MME1 newly assigns the location registration area information (TA List) to the mobile station UE1. - In a step S3 of
Fig.10 , the MME1 informs the S-GW1 about the TA List of the mobile station UE1 via S11 interface. The S-GW1 stores the TA List, informed from the MME1, in a storage unit (memory) in the S-GW1, as the registration information of the mobile station UE1. - It is noted that the location registration operation in the
steps Fig.10 is known per se and is not directly relevant to the subject-matter of the present invention. Hence, the operation is not explained in detail. -
Fig.11 is a sequence diagram for illustrating, as a second stage, the stage of maintaining a bearer. In astep 1 ofFig.11 , the mobile station UE1 has already attached to the MME1 (an attach request has already been issued). A variety of bearers have already been set up using S-GW1 and P-GW1. - In a
step 2 ofFig.11 , the restarting of the MME1 occurs and in this MME1, the registration information of the UE1, already attached, is erased. - In a
step 3 ofFig.11 , the S-GW1 detects the restarting of the MME1, from processing such as a health check by GTP Echo processing. - In a
step 4 ofFig.11 , S-GW1 recognizes all mobile stations UE attached to the MME1 (it is confirmed that the UE1 is accommodated in the MME1). - In case the present invention is provided for the entirety of the services, all bearers related with the mobile station UE1 from the S-GW1 towards the
external network IMS 1 are maintained in the step S5 ofFig.11 . - In
steps Fig.11 , in distinction from the step S5 ofFig.11 , the bearer maintaining function according to the present invention is not provided for all services relating to the mobile station UE1, such that bearers (bearers used for IMS control) are maintained for specific services (IMS services providing e.g., voice services). - After confirming in the step S4 of
Fig.11 that the mobile station UE1 has been accommodated in the MME1, the S-GW1 further confirms, in thestep 6 ofFig.11 , whether or not there is a bearer(s) providing the IMS (bearer(s) used for IMS control) among the bearers owned by the mobile station UE1. In verifying the bearers used for IMS control in this manner, a QCI (QoS Class Identifier) value, which is among information elements that each bearer has, may be used. If, in using the QCI value, it is '5', for example, the bearer may be concluded to be the bearer(s) used for IMS control (IMS Signaling), in accordance with the Table 6.1.7 of Non-Patent Document 1 (3GPP TS23.03). The bearer may then be concluded to be a control bearer used for rendering voice services. - If there is the bearer(s) used for IMS control among the bearers relating to the mobile station UE1 managed by the S-GW1, only the relevant bearer(s) are maintained. The remaining bearers are locally released in accordance with the operation in accordance with Non-Patent Document 2 (3GPP TS23.007).
- In case of maintaining the bearers used for IMS control (specific bearers), the S-GW1 starts the operation of a timer to release (remove) relevant bearer resources on timeout, in consideration of a case where the mobile station UE1 has already re-attached to another S-GW. This timer controls a time of maintaining the above mentioned specific bearer by the S-GW1, and becomes necessary to prevent failing to release the bearers that the S-GW1 maintains. If, in the above timer, the time equivalent to the time of a periodic location registration timer owned by the mobile station UE1 is set, the S-GW1 may wait for incoming of voice services for a necessary minimum time interval corresponding to the time of the next periodic location registration request from the UE1. At this time, the fact that the mobile station UE1 has not been registered in the MME1 is stored in the storage unit (memory) of the S-GW1.
- In a
step 7 ofFig.11 , the mobile station UE1 is not registered in the MME1 and only the IMS control bearer is maintained in the S-GW1 and in the P-GW1. This completes the second stage. - If the third stage, shown in
Fig.12 , has not been carried out thereafter, the S-GW1 removes the entirety of bearers (IMS control bearer resources) that the S-GW1 maintains in connection with the mobile station UE1, on timeout of the timer whose operation was started at the step S6 ofFig.11 . -
Fig.12 is a sequence diagram showing the operation of a third stage in case a signal has arrived in the second stage from the PDN such as IMS. The following describes respective stages. - In a
step 1 ofFig.12 , a notification from the IMSI, indicating the incoming of voice services to the mobile station UE1, arrives at the G-SW1. - In a step S2 of
Fig.12 , the G-SW1 stores the information that the mobile station UE1 is in an unregistered state due to the restarting of the MME1. Hence, the G-SW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the previously registered TA List, to the MME1, to inform the incoming. - If, in a step S3 of
Fig.12 , the mobile station UE1, having the IMSI that has been notified, is not attached, the MME1 performs paging of the mobile station UE1 for the received TA List, using the IMSI. However, there is such a case wherein, in carrying out the step S3, the mobile station UE1 has already selected another S-GW and has attached to the MME1. In this case, to prompt the S-GW1 to release the entirety of the bearers relevant to the mobile station UE1, the MME1 returns a downlink data notification acknowledge (Downlink Data Notification Acknowledge) response indicating the cause that the UE1 has already attached. - In a
step 4 ofFig.12 , the mobile station UE1 performs the attachment operation on receipt of the paging employing the IMSI. - The attach operation of the mobile station UE in the
step 4 ofFig.12 is well-known to those skilled in the art and, not directly relevant to the present invention. Hence, explanation of the detailed configuration is dispensed with. - When the S-GW detects the restarting of the MME, if the tunnel (GTP-U) on the S1-U interface between the eNodeB and the S-GW is active, the S-GW releases the tunnel.
- As an
exemplary embodiment 2 of the present invention, the following describes the operation at the time of SGSN restarting in the network configuration ofFig.7 . Basically, the operation of theexemplary embodiment 2 is equivalent to the operation at the time of restarting of MME in theexemplary embodiment 1. In the example ofFig.7 , 2G/3G is accommodated. Specifically, theeNodeB 102 and theMME 103 ofFig.6 are replaced by a 2G/3G radio control apparatus (nodeB and RNC) 110 and anSGSN 111. An interface between the 2G/3G radio control apparatus (NodeB and RNC) 110 and theSGSN 111 is Iu, an interface between the 2G/3G radio control apparatus (NodeB and RNC) 110 and the S-GW 104 is S12, an interface between the SGSN and the S-GW is S4 and an interface between theSGSN 111 and theHSS 106 is an S6d/Gr. - The operation of the present exemplary embodiment may be summarized to have three separate stages.
-
Fig.13 is a sequence diagram showing a stage of registering the location registration area information of the mobile station UE in the S-GW1, as a first stage. The following describes respective steps. - In a step S1 of
Fig.13 , the mobile station UE1 sends a location registration request (Attach Request/Routing Area Update Request) to the SGSN1. The Routing Area Update Request is a location registration update request to the SGSN. - In a step S2 of
Fig.13 , the SGSN1 newly assigns the location registration area information (RAI) to the mobile station UE1. - In a
step 3 ofFig.12 , the SGSN1 notifies the S-GW1 of the RAI of the mobile station UE1. The S-GW1 maintains the RAI notified as the registration information of the mobile station UE1. - The location registration operation of
Fig.12 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, the configuration is not explained in detail. -
Fig.14 is a sequence diagram for the stage of maintaining a bearer, as a second stage. The following describes respective steps. - In a step S1 of
Fig.14 , the mobile station UE1 has already attached to the SGSN1, and a various types of bearers have been set up using the S-GW1 and P-GW1. - In a
step 2 ofFig.14 , the processing of restarting occurs in the SGSN1. The registration information of the mobile station UE1 attached is erased. - In a
step 3 ofFig.14 , the S-GW1 detects the restarting at SGSN1 by processing, such as a health check, by GTP Echo processing. - In a step S4 of
Fig.14 , the S-GW1 recognizes the entirety of the mobile stations UE (it is confirmed that the mobile station UE1 is accommodated in SGSN1). - In case the present invention is applied to the entirety of services, all bearers are maintained in a
step 5 ofFig.14 . - In
steps Fig.14 , bearers are not maintained for the entirety of the services, as is done in thestep 5 ofFig.11 . Instead, just a bearer relating to a specific service (IMS service, providing e.g., voice services, in the following example) is maintained. - After step S4 of
Fig.14 of confirming that the mobile station UE1 is accommodated in SGSN1, the S-GW1 confirms, in astep 6 ofFig.14 , whether or not there is the IMS signaling bearer among the bearers held by the mobile station UE1. The IMS signaling bearer is a bearer used for IMS control. In determining whether or not a bearer in question is the IMS control bearer, the value of a QCI (QoS Class Identifier), which is one of the control elements owned by each bearer, for example, may be used. If the QoS value is '5', for example, a bearer in question is determined to be the IMS control (IMS signaling) bearer in accordance with Table 6.1.7 of Non-Patent Document 1 (3PP TS23.203). The bearer in question may thus be determined to be a control bearer used for providing voice services. If there is such IMS control bearer, the S-GW1 maintains just such bearer, and locally releases (removes) other bearers in accordance with the operation of Non-Patent Document 1 (3GPP TS23.007). - In case the IMS control bearer is maintained, the operation of a timer, which on timeout releases the bearer, is started in order to take account of the case where the mobile station UE1 has already attached to another S-
GW 1 . This timer is necessary to prevent failing to release bearers that the S-GW1 maintains. - In case, in the above timer, the time equivalent to the time of a periodic location registration timer included in the mobile station UE1 is set, the S-GW1 may wait for incoming of voice services for a necessary minimum time corresponding to the time of the next periodic location registration request from the UE1. At this time, the fact that the mobile station UE1 has not been registered in the SGSN1 is stored in the S-GW1.
- In a step S7 of
Fig.14 , the SGSN1 is in such a state that the mobile station UE1 has not been registered and that only the IMS control bearer is maintained in the S-GW1 and in the P-GW1. - In case thereafter the third stage shown in
Fig.15 is not executed, the S-GW1 removes the entirety of the bearers maintained in connection with the mobile station UE1 (IMS control bearer resources) at a timeout time point of the timer whose operation started in thestep 6 ofFig.14 . -
Fig.15 is a sequence diagram for illustrating the operation of a third stage in case of an incoming from PDN, such as IMS. - In a step S1 of
Fig.15 , incoming notification of voice services from IMS1 to the mobile station UE1 gets to the S-GW1. - In a step S2 of
Fig.15 , the S-GW1 sends the IMSI and the downlink data notification (Downlink Data Notification) inclusive of IMSI and RAI that have been registered in advance to the MME to inform the incoming. It is because the S-GW1 stores that the mobile station UE1 is in a non-registered state because of restarting of the SGSN1. - In case the mobile station UE1 that has the notified IMSI, has not attached, the SGSN1 in a step S3 in
Fig.15 performs paging of the mobile station UE1, for RAI received, using the IMSI. However, there is such a case wherein, in carrying out the step S3 ofFig.15 , the mobile station UE1 has already selected another S-GW and has attached to the SGSN1. In this case, to prompt the S-GW1 to release the entirety of the bearers relevant to the mobile station UE1, the SGSN1 sends back to the S-GW1 a downlink data notification acknowledge (Downlink Data Notification Acknowledge) response indicating the cause that the UE1 has already attached. - In a
step 4 ofFig.15 , the mobile station UE1 that has received the paging employing the IMSI performs an attachment operation. The attachment operation of the mobile station UE of the step S4 ofFig.15 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, its detailed configuration is omitted. - As an
exemplary embodiment 3 of the present invention, the following describes the operation in case of employing an ISR function (LTE/3G location registration omitting function) under the network configuration ofFig.8 . In ISR, the mobile station UE registers its location in both the MME and the SGSN. In case of switching a radio access system between LTE and 2G/3G, UE location registration is omitted as long as there is no change in the previously registered location registration area in LTE and that in 2G/3G.Fig.8 shows a packet communication network configuration accommodating LTE and 2G/3G. This configuration corresponds to the configuration ofFig.1 added by a 2G/3Gradio control apparatus 110 and anSGSN 111 to be connected to themobile station UE 101. TheMME 103 is connected to theSGSN 111 via an S3 interface, while theMME 103 and theSGSN 111 are connected to theHSS 106 via an S6a interface and an S6d/Gr interface. The S-GW 104 is connected to theSGSN 111 and to theMME 103 via an S4 interface and via an S11 interface. - The processing of location registration for the UE1 from 2G/3G, as a first stage, is shown in
Fig.13 .Fig.10 may apply as regards the processing of location registration from LTE. By these two operations, the S-GW1 maintains RAI and TA List as the location registration area information. The processing of location registration during the ISR operation is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, its detailed configuration is omitted. -
Fig.16 is an example of a sequence as an operation in case of restarting of the MME1 ofFig.8 .Fig.17 shows an example of a sequence as an operation in case of restarting of the SGSN1 ofFig.8 - In a
step 1 ofFig.16 , the mobile station UE1 has its location registered in the MME1, and a various types of bearers have been established using the S-GW1 and the P-GW1. - In a
step 2 ofFig.16 , restarting occurs in the MME1, so that the registration information of the mobile station UE1 in the MME1 is erased. - In a
step 3 ofFig.16 , the S-GW1 detects the restarting of the MME1 from processing, such as a health check by the GTP Echo processing. - In a
step 4 ofFig.16 , the S-GW1 does not perform releasing of bearers because the S-GW1 knows that the mobile station UE1 attached to the MME1 has been registered using the SGSN1 and the ISR function. At this time, the fact that the mobile station UE1 is not registered in the MME1 is stored in an internal memory of the S-GW1. However, in case the SGSN1 has already been restarted, the processing according to the present invention (processing of maintaining the bearer relevant to the mobile station UE1) is carried out as is the processing ofFig.11 . - The following describes the operation in case the SGSN1 of
Fig.8 has restarted. - In a
step 1 ofFig.17 , the mobile station UE1 has its location registered in SGSN1, and a various types of bearers have already been set up using the S-GW1 and the P-GW1. - In a
step 3 ofFig.17 , the processing of restarting, for example, occurs in the SGSN1, and the registration information of the mobile station UE1, which has its location registered, is erased. - In a
step 3 ofFig.17 , the S-GW1 detects the restarting of the SGSN1 from processing such as a health check by the GTP Echo processing. - In a
step 4 ofFig.17 , the S-GW1 does not perform bearer releasing because the S-GW1 knows that the mobile station UE1 attached to the MME1 has been registered using the MME1 and the ISR function. The non-registration status of the mobile station UE1 in the SGSN1 is stored in the internal memory of the S-GW1. However, if the MME1 has already restarted, the processing according to the present invention (processing of maintaining the bearer relevant to the mobile station UE1) is carried out as with the processing ofFig.14 . -
Fig.18 is a diagram showing an example of a sequence of the operation in case there is an incoming from the PDN under a condition that the MME1 ofFig.8 has restarted, as a third stage.Fig.19 is a diagram showing an example of a sequence of the operation in case there is an incoming from the PDN under a condition that the SGSN1 ofFig.8 is restarted.Fig.20 is a diagram showing an example of a sequence of the operation in case there is an incoming from the PDN under a condition that both the MME1 and the SGSN1 ofFig.8 are restarted. - In case there is an incoming from the PDN under a condition the MME1 of
Fig.8 is restarted, incoming notification of communication services from the PDN1 to the mobile station UE1 gets to the S-GW1 in astep 1 ofFig.18 . - In a
step 2 ofFig.18 , the S-GW1 sends a normal downlink data notification (Downlink Data Notification) to the SGSN1 to inform the incoming. - In a
step 3 ofFig.18 , the S-GW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the pre-registered TA List, to the MME1 to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 on account of the restarting of the MME1. - In a
step 4 ofFig.18 , the SGSN1 performs normal paging (paging of the mobile station responsive to the incoming). - In a
step 5 ofFig.18 , in case the mobile station UE1 having the IMSI according to the notification is not attached, the MME1 performs paging of the mobile station UE1, using the IMSI, by referring to the TA List received. - In a
step 6 ofFig.18 , paging employing the IMSI is received at LTE, the mobile station UE1 performs an attachment operation. - The following describes a case wherein an incoming from the PDN is performed under a condition the SGSN has restarted.
- In a
step 1 ofFig.19 , incoming notification of communication services from the PDN1 to the mobile station UE1 gets to the S-GW1. - In a
step 2 ofFig.19 , the S-GW1 sends a normal downlink data notification (Downlink Data Notification) to the MME1 to inform the incoming. - In a
step 3 ofFig.19 , the S-GW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the pre-registered RAI, to the SGSM1, to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 on account of the restarting of the MME1. - In a
step 4 ofFig.18 , the SGSN1 performs normal paging. - In a
step 5 ofFig.18 , in case the mobile station UE1 having the IMSI according to the notification has not attached, the SGSM1 performs the paging of the mobile station UE1, using the IMSI, by referring to the RAI received. - In a
step 6 ofFig.19 , in case the paging employing the IMSI is received in 2G/3G, the mobile station UE1 performs an attachment operation. - The following describes a case wherein an incoming from the PDN is performed under a condition both the MME and the SGSN have restarted.
- In a
step 1 ofFig.20 , incoming notification of communication services from the PDN1 to the mobile station UE1 gets to the S-GW1. - In a
step 2 ofFig.20 , the S-GW1 sends a downlink data notification (Downlink Data Notification), inclusive of the IMSI and the pre-registered TA List, to the MME1, to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 on account of the restarting of the MME1. - In a
step 3 ofFig.20 , the S-GW1 sends a downlink data notification, inclusive of the IMSI and the pre-registered TA List, to the SGSN1, to inform the incoming. It is because the S-GW1 stores the non-registered state of the mobile station UE1 which is due to the restarting of the MME1. - In a
step 4 ofFig.20 , in case the mobile station UE1 having the IMSI according to the notification is not attached, the MME1 performs paging of the mobile station UE1, using the IMSI, by referring to the TA List received. - In a
step 5 ofFig.20 , in case the mobile station UE1 having the IMSI according to the notification is not attached, the SGSN1 performs paging of the mobile station UE1, using the IMSI, by referring to the RAI received. - In a
step 6 ofFig.20 , when receiving the paging employing the IMSI, the mobile station UE1 performs an attachment operation. - The attachment operation of the mobile station UE of the step S6 of
Fig.11 ,12 and13 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, the detail configuration is omitted. -
Fig.9 is a diagram showing a network configuration according to a fourth exemplary embodiment according to the present invention. InFig. 9 , there is shown a CSFB (CS Fallback) architecture. Referring toFig.9 , the network includes a mobile station (UE) 101, a base station (eNodeB) 102, anMME 103, anHSS 106, an MSC/VLR 112, aCS network 113 and a G-MSC (gateway mobile switch center) 114. The following describes the operation of voice incoming from the G-MSC 114 as an originating source to the mobile station (UE) 101 with reference toFig. 9 . - A signal notifying the incoming is sent from the G-
MSC 114 as an originating source to the MSC/VLR 112 via theCS network 113. The MSC/VLR 112 identifies thecorresponding MME 103 from the incoming information to send a paging request message (Paging-Request-Message) to theMME 103. TheMME 103 sends a paging signal to the mobile stations that reside in the serving area. This paging signal includes information indicating that the paging is for CS services. Themobile station UE 101 recognizes this information, that is, the information that the paging is that for CS services, and sends a CS service request signal to theMME 103. The MME sends a handover command to the UE1. The mobile station (UE) 101 performs handover, while switching to 3G. Themobile station UE 101, which has switched to 3G, sends a paging response to the MSC/VLR 112, as a result of which the voice services at the mobile station to the incoming voice are started. The following describes the operation when the MME restarts. - The operation according to the present invention may be summarized to have three separate stages.
-
Fig.21 is a sequence diagram showing, as a first stage, the stage of registering location registration area information of the mobile station UE. The following describes respective steps. - In a
step 1 ofFig.21 , the mobile station UE1 makes a location registration request for CSFB (Attach Request, TAU Request and so forth) to the MME1. - In a
step 2 ofFig.21 , the MME1 newly assigns (delivers) the location registration area information (TA List) to the mobile station UE1. - In a
step 3 ofFig.21 , the MME1 notifies the MSC1 of the TAU List of the mobile station UE1. The MSC1 maintains the TAU List, notified from the MME1, as the registration information of the mobile station UE1. - The location registration operation of
Fig.21 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, the detailed configuration is omitted. -
Fig.22 is a sequence diagram showing, as a second stage, the stage of maintaining a bearer. The following describes respective steps. - In a
step 1 ofFig.22 , the mobile station UE1 has already attached to the MME1. - In a
step 2 ofFig.22 , restarting occurs in the MME1 and the registration information of the mobile station UE1 is erased. - In a
step 3 ofFig.22 , the MSC1 detects the restarting of the MME1 from processing such as a health check by the SCTP. - In a
step 4 ofFig.22 , the MSC1 recognizes the entirety of the mobile stations UE attached to the MME1 (it is recognized that the mobile station UE1 is accommodated in MME1). The above is the second stage. -
Fig.23 depicts an example sequence diagram showing, as a third stage, an operation sequence for the case of incoming (voice incoming or SMS, for example) via a CS domain. The following describes respective steps. - In a
step 1 ofFig.23 , an incoming notification to the mobile station UE1 arrives at the MSC1 by e.g., the G-MSC. - In a
step 2 ofFig.23 , the MSC1 sends a paging request message inclusive of IMSI and pre-registered TA List (SGsAP-PAGING-REQUEST message) to the MME1 to notify the MME1 of the incoming. It is because the MSC1 stores the non-registered state of the mobile station UE1 brought about by restarting of the MME1. - In a
step 3 ofFig.23 , in case the UE1 having the IMSI notified thereto has not attached, the MME1 performs a paging of the mobile station UE1, using the IMSI, for the TA List received. - However, there is such a case wherein, in carrying out the step S3 of
Fig.23 , the mobile station UE1 has already selected another MSC and has attached to the MME1. - In this case, to prompt the MSC1 to release the entirety of the bearers relevant to the mobile station UE1, the MME1 sends back to the MSC1 a paging reject message (SGsAP-PAGING-REJECT message) indicating the cause that the UE1 has already attached.
- In a
step 4 ofFig.23 , the mobile station UE1, which has received the paging that uses the IMSI, performs an attachment operation. The attachment operation of the mobile station UE in thestep 4 ofFig.23 is known per se among those skilled in the art and is not directly relevant to the subject-matter of the present invention. Hence, the configuration is omitted. - In the drawings of the above described exemplary embodiment, only one (P-GW1) is shown as the P-GW for simplicity of explanation. However, a plurality of P-GWs, such as P-GW2, P-GW3 or P-GWN, may be used in a similar manner.
- Another one of modes of the present invention will now be explained with reference to
Fig.24 , which supplementsFig.10 , for example, and shows subscriber data re-installation by network triggered service request. It is noted that the eNodeB is omitted inFig.24 . - S1) The MME sends the latest TA-list to a relevant S-GW. That is, the MME informs the latest TA-list on a per UE basis to one or more S-GWs in every occurrence of mobility events. This information (TA list) is important in case of MME failure because paging of the IMSI for the coverage of the MME in its entirety may thereby be avoided. Since larger numbers of eNodeBs are accommodated in one MME, the load in the EPS system may become tremendously severe if paging is to be performed for the entire coverage.
- S2) The MME performs restarting.
- S3) With a restart counter increased by one, a GTP Echo message (GTP-V2 Echo response message) is sent to the entirety of the relevant S-GWs.
- S4) The relevant S-GW detects MME failure by this GTP echo mechanism. The S-GW is able to maintain all or selected bearers, IMSI and the TA list. An operator is able to select a bearer based on top-rank services (IMS) (service on top (IMS)), as a result of which the bearer maintained may be selected only for important services. For other (selected) bearers, the current MME restarting mechanism is applied. If the S-GW is to maintain bearer resources, IMSI and the TA list, the S-GW starts a timer that controls a time interval for maintaining bearer resources, for example. On timeout of the timer, the bearer resources maintained are removed. This alternative is needed for such case in which, when the UE re-attaches to a network, the S-GW in question is not selected. That is, on timeout of the timer of the S-GW in question, the above mentioned bearer resources maintained, for example, S5/S8 bearers, which are specific bearers maintained, are removed on the assumption that the UE has re-attached to the network via a S-GW different from the S-GW in question.
- S5) DL data arrives at the P-GW from an external network (PDN).
- S6) The S-GW acquires the DL data from the P-GW.
- S7) The S-GW sends a downlink data notification message inclusive of the IMSI and the TA list (DL data notification (IMSI, TA list)) to the MME.
- S8) The MME starts the IMSI page ((Page (IMSI) to TAs specific in TA list) for all of TAs of the TA list received from S-GW.
- S9) On receiving the IMSI page, the mobile station UE1 starts the attach (ATTACH) procedure.
- S10) On receiving the attach (ATTACH) request from the UE, the MME sends a location information update request to the HSS.
- S11) The HSS sends location information update acknowledge to the MME.
- S12) The MME sends the ATTACH acceptance to the mobile station UE via eNodeB.
- In case of detecting the restart of the MME, the S-GW maintains the bearer, IMSI or the TA list. In this manner, it is possible to instantaneously recover communication services after restart of the MME and after arrival of the DL data at the UE from the PDN side.
- In a mode of the present invention, in case only the selected bearer is to be maintained, it is possible to suppress consumption of S-GW resources. In addition, by selecting and maintaining bearers for important services, communication services may instantaneously be restored for services of higher rank of importance, such as voice communication, on arrival of an incoming to the mobile station, after the restarting of the MME.
- In another mode of the present invention, in case a bearer is to be maintained by itself or together with the IMSI and the TA list, the time interval of the maintenance is managed by a timer. On timeout of the timer, the bearer, IMSI and the TA list maintained are released. By so doing, in case, after restart of the MME, the mobile station moves and attaches to a G-SW different from the S-GW that maintains the bearer, it is possible to prevent the S-GW that maintains the bearer from maintaining the bearer longer than is necessary.
- According to the present invention, described above, the following effects may be realized.
- UE's communication services may be improved in availability by adding packet incoming as a re-registration trigger of a UE registered in the MME/SGSN in which restarting occurred.
- In case the present invention is applied to all services, incoming of the entirety of the packets may be used as a trigger for restoring the UE to the network. It may however be thought that many resources on the S-GW side are used, and that location registration events may become concentrated. The S-GW1 is able to maintain the TA list and to perform the Paging processing by using the TA list. However, if it is not possible for the S-GW to receive the TA list from the MME1, the paging may be performed for the whole area supervised by the MME1. In this case, many of the radio network side resources would be consumed.
- According to the present invention, the S-GW1 is able to maintain the RAI and to perform Page processing by using the RAI. If it is not possible for the S-GW1 to receive the RAI from the SGSN1, paging may be performed for the total areas supervised by the SGSN. In this case, many of the radio network side resources would be consumed.
- Further embodiments of the present invention are described by the following items:
- 1. A communication method in which a bearer management node maintains a specific bearer eligible for restoration of communication services, and removes other bearers.
- 2. The communication method according to
item 1, wherein in case the bearer management node maintains the specific bearer, the bearer management node starts a timer, and the bearer management node removes the bearer resource that the bearer management node maintains, on timeout of the timer. - 3. The communication method according to
item - 4. The communication method according to
item 3, wherein the bearer management node maintains
location registration area information of a mobile terminal notified from the mobility management node, and
identification information associated with the mobile terminal. - 5. The communication method according to
item 4, wherein on receipt of an incoming to the mobile terminal after restarting of the mobility management node, the bearer management node notifies the mobility management node of the incoming and of the location registration area information and the identification information the bearer management node maintains, and
the mobility management node performs paging using the identification information for an area corresponding to the location registration area information. - 6. The communication method according to any one of
items 3 to 5, wherein when the bearer management node detects restarting of the mobility management node, the bearer management node confirms that the mobile terminal is accommodated in the mobility management node, and
the bearer management node maintains, in connection with the mobile terminal, the specific bearer that is set in the direction of from the bearer management node to an external network. - 7. The communication method according to
item 3, wherein the mobility management node includes a first mobility management node associated with a first communication system and a second mobility management node associated with a second communication system,
location registration of the mobile terminal is performed for the first and second mobility management nodes,
the bearer management node maintains the location registration area information of the mobile terminal notified from the first and second mobility management nodes and the identification information associated with the mobile terminal,
the bearer management node, in case of detection of restarting of one of the first and second mobility management nodes, maintains the specific bearer,
the bearer management node, when receiving incoming data, sends to the restarted one of the first and second mobility management nodes a notification message inclusive of the identification information associated with the mobile terminal as a destination of the incoming data and the location registration area information, and
the restarted one of the mobility management nodes performs paging including the identification information associated with the mobile terminal for an area corresponding to the location registration area information from the bearer management node. - 8. The communication method according to
item 7, wherein in case restarting occurs in both of the first and second mobility management nodes, the bearer management node maintains all or a selected one of bearers as set in the direction of from the bearer management node to an external network,
the bearer management node on receipt of incoming data sends to the first and second mobility management nodes a notification message inclusive of the identification information associated with the mobile terminal and the location registration area information, and
the first and second mobility management nodes performs paging, inclusive of the identification information associated with the mobile terminal, for an area corresponding to the location registration area information from the bearer management node. - 9. The communication method according to
item 3, wherein the mobility management node informs one or a plurality of bearer management nodes about the latest location registration area information per mobility event of the mobile terminal, and
the bearer management node that detects restarting of the mobility management node by a health check mechanism maintains all bearers or selected bearers and the identification information associated with the mobile terminal along with the location registration area information. - 10. The communication method according to item 9, wherein the bearer management node starts a timer in case of maintaining the bearer, the identification information associated with the mobile terminal and the location registration area information, and
the bearer management node removes the bearer, the identification information associated with the mobile terminal and the location registration area information that the bearer management node maintains, on timeout of the timer. - 11. The communication method according to
item 9 or 10, wherein the bearer management node on acquisition of the incoming data to the mobile terminal, with the bearer, identification information and the location registration area information of the mobile terminal being maintained by the bearer management node, sends to the mobility management node a notification message including the identification information associated with the mobile terminal and the location registration area information, and
the mobility management node starts paging, including the identification information associated with the mobile terminal, for all areas of the location registration area information received from the bearer management node. - 12. The communication method according to
item 11, wherein the mobile terminal starts an attach procedure on receipt of the paging. - 13. A communication method wherein on restarting of a mobility management node, a circuit switched node sends to the mobility management node a notification message including identification information associated with a mobile terminal and location registration area information, and
the mobility management node starts paging, inclusive of the identification information associated with the mobile terminal, for an area corresponding to the location registration area information. - 14. The communication method according to item 13, wherein the circuit switched node maintains the location registration area information of the mobile terminal informed from the mobility management node and the identification information associated with the mobile terminal.
- 15. A mobile network system, wherein a bearer management node maintains a specific bearer eligible for restoration of communication services, and removes other bearers.
- 16. The mobile network system according to item 15, wherein in maintaining the specific bearer, the bearer management node starts a timer, and removes bearer resources that the bearer management node maintains, on timeout of the timer.
- 17. The mobile network system according to item 15 or 16, comprising:
- a mobility management node that manages mobility of the mobile terminal, wherein in case restarting of the mobility management node is performed, the bearer management node maintains the specific bearer and removes other bearers.
- 18. The mobile network system according to item 17, wherein the bearer management node maintains
location registration area information of the mobile terminal notified by the mobility management node, and
identification information associated with the mobile terminal. - 19. The mobile network system according to item 18, wherein when there is an incoming to the mobile terminal after restarting of the mobility management node, the bearer management node informs the mobility management node about the incoming and about the identification information and the location registration area information that the bearer management node maintains, and
the mobility management node performs paging, using the identification information, for an area corresponding to the location registration area information. - 20. The mobile network system according to any one of items 17 to 19, wherein on detecting the restarting of the mobility management node by the bearer management node, the bearer management node confirms that the mobile terminal is accommodated in the mobility management node, and
the bearer management node maintains all bearers or at least one selected bearer as set in the direction of from the bearer management node to an external network in connection with the mobile terminal. - 21. The mobile network system according to item 17, wherein the mobility management node includes:
- a first mobility management node associated with a first communication system; and
- a second mobility management node associated with a second communication system, wherein
- location registration of the mobile terminal is performed for the first and second mobility management nodes,
- the bearer management node maintains the location registration area information notified from the first and second mobility management nodes, and the identification information associated with the mobile terminal,
- the bearer management node, in case of detection of restarting of one of the first and second mobility management nodes does not release but maintains the specific bearer,
- the bearer management node on subsequently receiving incoming data sends to the restarted one of the first and second mobility management nodes a notification message inclusive of the identification information associated with the mobile terminal as a destination of the incoming data and the location registration area information, and
- the restarted one of the mobility management nodes performs paging inclusive of the identification information of the mobile terminal for an area corresponding to the location registration area information from the bearer management node.
- 22. The mobile network system according to item 21, wherein in case both the first and second mobility management nodes are restarted, the bearer management node maintains all bearers or selected one of the bearers set in a direction of from the bearer management node side to an external network,
the bearer management node on receiving the incoming data sends a notification message inclusive of the identification information associated with the mobile terminal and the location registration area information to the first and second mobility management nodes, and
the first and second mobility management nodes perform paging inclusive of the identification information associated with the mobile terminal for an area corresponding to the location registration area information from the bearer management node. - 23. The mobile network system according to item 17, wherein the mobility management node informs the bearer management node about the latest location registration area information per mobility event of the mobile terminal,
the bearer management node that detects restarting of the mobility management node by a health check mechanism maintains all bearers or selected bearers and the identification information associated with the mobile terminal along with the location registration area information. - 24. The mobile network system according to item 23, wherein the bearer management node starts a timer, in case of maintaining the bearers, the identification information associated with the mobile terminal and the location registration area information, and
the bearer management node removes the bearer, the identification information associated with the mobile terminal and the location registration area information, the bearer management node is maintaining, on timeout of the timer. - 25. The mobile network system according to item 23 or 24, wherein when obtaining the incoming data, the bearer management node sends to the mobility management node a notification message inclusive of the identification information associated with the mobile terminal and the location registration area information, and
the mobility management node starts paging, inclusive of the identification information associated with the mobile terminal, for all areas of the location registration area information received from the bearer management node. - 26. The mobile network system according to item 25, wherein on receipt of the paging, the mobile terminal starts an attach procedure.
- 27. A mobile network system comprising:
- a mobility management node; and
- a circuit switched node, wherein in case of restarting of the mobility management node, the circuit switched node sends to the mobility management node a notification message inclusive of identification information associated with the mobile terminal and location registration area information, and
- the management node performs paging inclusive of the identification information associated with the mobile terminal for an area corresponding to the location registration area information.
- 28. The mobile network system according to item 27, wherein the circuit switched node maintains the location registration area information of the mobile terminal, notified from the mobility management node, and the identification information associated with the mobile terminal.
- 29. A node apparatus that manages a bearer, wherein the node apparatus maintains a specific bearer eligible for restoration of communication services, and removes other bearers.
- 30. The node apparatus according to item 29, wherein in case the specific bearer is maintained, the node apparatus starts a timer, and removes the bearer resources maintained, on timeout of the timer.
- 31. The node apparatus according to item 29 or 30, wherein in case restarting of a mobility management node is performed, the node apparatus maintains the specific bearer, and removes other nodes.
- 32. The node apparatus according to item 31, wherein the node apparatus maintains
location registration area information of the mobile terminal notified from the mobility management node, and
identification information associated with the mobile terminal are maintained, wherein
when the incoming to the mobile terminal is received after restarting of the mobility management node, the node apparatus notifies the incoming to the mobility management node, and the node apparatus notifies the location registration area information and the identification information that the node apparatus maintains to the mobility management node. - 33. The node apparatus according to item 31 or 32, wherein when detecting restarting of the mobility management node, the node apparatus maintains all bearers or at least one selected bearer set in the direction of from the node apparatus to an external network.
- 34. The node apparatus according to item 32, wherein in case of maintaining the bearer, the identification information associated with the mobile terminal and the location registration area information, the node apparatus starts a timer, and
the node apparatus removes the bearer maintained, the identification information associated with the mobile terminal maintained and the location registration area information maintained, on timeout of the timer. -
- 101
- UE
- 102
- eNodeB
- 103
- MME
- 104
- S-GW
- 105
- P-GW
- 106
- HSS
- 107
- S5/S8
- 108
- external network
- 109
- IMS.
- 110
- 2G/3G radio control apparatus (NodeB/RNC)
- 111
- SGSN
- 112
- MSC/VLR
- 113
- CS network
- 114
- G-MSC (gate mobile switch center)
Claims (2)
- A mobile terminal (UE) used in a mobile communication network that includes a mobility management entity (MME) and a serving gateway (S-GW), wherein the mobile terminal comprises:means that receives paging from the mobile communication network, upon an arrival of an incoming call destined for the mobile terminal to the mobile communication network with the serving gateway maintaining, upon restarting of the mobility management entity, a specific S5/S8 bearer for a preset time period prescribed by a timer, the serving gateway deleting the specific S5/S8 bearer on timeout of the timer; andmeans that in response to the paging, re-attaches to the mobile communication network.
- A method for registration of a mobile terminal (UE) in a mobile communication network that includes a mobility management entity (MME) and a serving gateway (S-GW), wherein the method comprises:receiving, by the mobile terminal, paging from the mobile communication network, upon an arrival of an incoming call destined for the mobile terminal to the mobile communication network with the serving gateway maintaining, upon restarting of the mobility management entity, a specific S5/S8 bearer for a preset time period prescribed by a timer, the serving gateway deleting the specific S5/S8 bearer on timeout of the timer; andre-attaching to the mobile communication network, by the mobile terminal, in response to the paging.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010102166 | 2010-04-27 | ||
EP11775029.9A EP2448299B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11775029.9 Division | 2011-04-27 |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2472989A1 true EP2472989A1 (en) | 2012-07-04 |
EP2472989B1 EP2472989B1 (en) | 2013-09-04 |
Family
ID=44861546
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP20130190476 Active EP2699048B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon mobility management node restarting |
EP20120159835 Withdrawn EP2466983A3 (en) | 2010-04-27 | 2011-04-27 | Communication method, mobile network system and device |
EP20120159825 Active EP2472989B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP20120159828 Active EP2472990B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP20120159837 Withdrawn EP2472992A1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP20120159821 Active EP2472988B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP20120159830 Active EP2472991B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP11775029.9A Active EP2448299B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP20130190476 Active EP2699048B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon mobility management node restarting |
EP20120159835 Withdrawn EP2466983A3 (en) | 2010-04-27 | 2011-04-27 | Communication method, mobile network system and device |
Family Applications After (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP20120159828 Active EP2472990B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP20120159837 Withdrawn EP2472992A1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP20120159821 Active EP2472988B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP20120159830 Active EP2472991B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
EP11775029.9A Active EP2448299B1 (en) | 2010-04-27 | 2011-04-27 | Accelerating restoration of communication services upon MME restarting |
Country Status (8)
Country | Link |
---|---|
US (8) | US9451583B2 (en) |
EP (8) | EP2699048B1 (en) |
JP (19) | JP4985880B2 (en) |
KR (2) | KR101332971B1 (en) |
CN (3) | CN102860052B (en) |
BR (7) | BR122016006460A2 (en) |
ES (4) | ES2535361T3 (en) |
WO (1) | WO2011136248A1 (en) |
Families Citing this family (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102257851B (en) * | 2008-12-19 | 2014-07-02 | 爱立信电话股份有限公司 | GRE user-plane |
US9060374B2 (en) * | 2010-04-27 | 2015-06-16 | Nec Corporation | Communication method, mobile network system and device |
CN102860052B (en) | 2010-04-27 | 2015-11-25 | 日本电气株式会社 | Communication means, mobile network system and device |
JP5011439B2 (en) * | 2011-01-07 | 2012-08-29 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method, mobility management node, and serving gateway device |
EP2680625B1 (en) * | 2011-05-03 | 2016-09-28 | Huawei Technologies Co., Ltd. | Method and device for transmitting a short message from an evolved packet system to a user equipment |
US9161380B2 (en) * | 2011-07-19 | 2015-10-13 | Qualcomm Incorporated | Silent redial during mobile-originated call |
JP2013150213A (en) * | 2012-01-20 | 2013-08-01 | Sharp Corp | Communication system, gateway device and communication method |
US10085207B2 (en) * | 2012-01-27 | 2018-09-25 | Intel Corporation | Techniques for improved energy-savings management |
WO2013167160A1 (en) * | 2012-05-07 | 2013-11-14 | Nokia Siemens Networks Oy | Speeding up user equipment reachability after network element restart |
US8923880B2 (en) | 2012-09-28 | 2014-12-30 | Intel Corporation | Selective joinder of user equipment with wireless cell |
CN104798391B (en) * | 2012-10-05 | 2018-12-04 | 瑞典爱立信有限公司 | The report of service network, time zone and UCI |
EP2908583B1 (en) * | 2012-10-10 | 2019-02-27 | LG Electronics Inc. | Method for processing paging and method for relaying downlink data |
WO2014091630A1 (en) * | 2012-12-14 | 2014-06-19 | 富士通株式会社 | Wireless communication system, mobile terminal, server, and wireless communication method |
US9807548B2 (en) * | 2013-02-01 | 2017-10-31 | Alcatel Lucent | Method and system for obtaining location information from a wireless network |
JP5525092B1 (en) * | 2013-04-05 | 2014-06-18 | 日本電気株式会社 | Mobility management device, communication system, voice incoming call control method, and program |
JP5606603B1 (en) * | 2013-05-20 | 2014-10-15 | 日本電気通信システム株式会社 | Mobile communication system, SGW, terminal, communication method and control method |
JP6221716B2 (en) | 2013-12-11 | 2017-11-01 | 富士通株式会社 | Communication system and network device |
EP3096573B1 (en) * | 2014-01-13 | 2018-10-24 | LG Electronics Inc. | Downlink data transfer method |
CN104853338A (en) * | 2014-02-14 | 2015-08-19 | 中国移动通信集团广东有限公司 | Business continuing method, device, and mobile switching center / visitor location register |
WO2015123871A1 (en) * | 2014-02-21 | 2015-08-27 | 华为技术有限公司 | Method and device for processing network failure |
CN104883668B (en) * | 2014-02-28 | 2020-02-21 | 北京三星通信技术研究有限公司 | Method for supporting PWS quick recovery |
US9369937B1 (en) | 2014-07-11 | 2016-06-14 | Sprint Communications Company L.P. | Long term evolution (LTE) network hand-over control based on quality-of-service class indicator (QCI) combinations |
CN105744502A (en) * | 2014-12-08 | 2016-07-06 | 中兴通讯股份有限公司 | Intelligent paging method and system, serving gateway and mobile management entity |
KR101838979B1 (en) | 2014-12-22 | 2018-03-15 | 닛본 덴끼 가부시끼가이샤 | Mobile communication system, sgw, terminal, reception method of mobile communication system, reception method of sgw, and reception method of terminal |
KR20170128540A (en) | 2015-03-27 | 2017-11-22 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Data transmission method, access network device, and communication system |
KR101735382B1 (en) * | 2015-10-16 | 2017-05-15 | 주식회사 엘지유플러스 | Method and apparatus for providing incoming call service during MME fault |
JP2018074522A (en) * | 2016-11-02 | 2018-05-10 | 日本電気株式会社 | Gateway device, mobility management device, base station, communication method, control method, paging method, and program |
WO2018089442A2 (en) * | 2016-11-09 | 2018-05-17 | Intel IP Corporation | Ue and devices for detach handling |
CN106972963B (en) * | 2017-03-23 | 2020-01-03 | 数据通信科学技术研究所 | Service module starting control method and starting control method after crash restart |
JP6873943B2 (en) * | 2018-03-26 | 2021-05-19 | Kddi株式会社 | Terminal equipment, base station equipment, control methods, and programs that enable location registration processing during sleep mode. |
JP7258586B2 (en) * | 2019-02-15 | 2023-04-17 | 株式会社Nttドコモ | Mobile station, relay node and communication control method |
US11477828B2 (en) * | 2019-03-15 | 2022-10-18 | Parallel Wireless, Inc. | Multi-UE and multi-message support in tunnel management messages |
US11109344B2 (en) * | 2019-05-01 | 2021-08-31 | Lg Electronics Inc. | Start and stop of reception of downlink transmission based on paging |
CN110312323B (en) * | 2019-05-21 | 2021-01-08 | 展讯半导体(成都)有限公司 | Control method, control device and storage medium |
JP7347053B2 (en) | 2019-09-13 | 2023-09-20 | Agc株式会社 | Composite shoji |
CN114915614B (en) * | 2019-12-20 | 2023-04-11 | 华为技术有限公司 | Method and device for recovering IMS service |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003039186A1 (en) * | 2001-10-12 | 2003-05-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for retaining subscriber data contained in msc/vlr after system restart |
WO2003041435A1 (en) * | 2001-11-03 | 2003-05-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and node for the set-up of a connection in a telecommunication network |
EP1903821A2 (en) * | 2006-09-21 | 2008-03-26 | Innovative Sonic Limited | Method for handling radio link failure in wireless communications system and related apparatus |
US20090239526A1 (en) * | 2008-03-21 | 2009-09-24 | Research In Motion Limited | Evolved Packet System Quality of Service Enforcement Deactivation Handling to Prevent Unexpected User Equipment Detach |
JP2010102166A (en) | 2008-10-24 | 2010-05-06 | Konica Minolta Business Technologies Inc | Electrophotographic photoreceptor, image forming method, and image forming apparatus |
Family Cites Families (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100550804C (en) * | 2006-01-25 | 2009-10-14 | 华为技术有限公司 | A kind of network attached method and network attachment system |
WO2007124685A1 (en) | 2006-04-24 | 2007-11-08 | Huawei Technologies Co., Ltd. | Paging medthod and apparatus in communication network |
CN101064932B (en) * | 2006-04-24 | 2011-02-02 | 华为技术有限公司 | Method for paging a plurality of users |
US9520981B2 (en) | 2007-01-12 | 2016-12-13 | Nokia Technologies Oy | Method and apparatus for providing automatic control channel mapping |
CN101707917A (en) | 2007-06-18 | 2010-05-12 | 诺基亚公司 | Distributed scheduling for multicast in meshed wireless network |
CN101540719B (en) * | 2008-03-19 | 2012-09-19 | 电信科学技术研究院 | Method and equipment for re-locating serving gateway |
WO2009118707A1 (en) | 2008-03-26 | 2009-10-01 | Nokia Corporation | Reporting channel state information |
CN101472256B (en) * | 2008-04-03 | 2011-04-20 | 华为技术有限公司 | Method for hanging up and recovering bearing as well as gateway proxy and communication system |
US8948768B2 (en) | 2008-04-28 | 2015-02-03 | Intel Mobile Communications GmbH | Radio communication device and method for controlling resource allocations |
CN102027798A (en) | 2008-05-13 | 2011-04-20 | 三星电子株式会社 | Method and apparatus for providing voice call in mobile communication system and system thereof |
CN101610576B (en) * | 2008-06-18 | 2013-01-30 | 上海华为技术有限公司 | Information processing method under the condition of limiting signaling and related equipment |
JP5121624B2 (en) * | 2008-08-08 | 2013-01-16 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method and circuit switching center |
KR101029541B1 (en) * | 2008-08-11 | 2011-04-18 | 한국전자통신연구원 | method for processing exceptional case of establishing default bearer in mobile communication system and device therefor |
US8243725B2 (en) | 2008-08-13 | 2012-08-14 | Interdigital Patent Holdings, Inc. | Maintaining circuit switched continuity in an enhanced universal terrestrial radio access network |
US20100080116A1 (en) * | 2008-09-29 | 2010-04-01 | Qualcomm Incorporated | Re-establishing a radio resource control connection with a non-prepared base station |
CN101583192B (en) * | 2008-10-14 | 2012-02-29 | 中兴通讯股份有限公司 | Method for processing bearer reconstruction failure |
US8483149B2 (en) | 2008-12-05 | 2013-07-09 | Nokia Siemens Networks Oy | Resource allocation technique for physical uplink control channel blanking |
WO2010074441A2 (en) | 2008-12-26 | 2010-07-01 | Lg Electronics Inc. | Method of releasing radio bearer in wireless communication system and receiver |
KR101641096B1 (en) * | 2009-02-16 | 2016-07-20 | 삼성전자주식회사 | Apparatus and method for managementing path between nodes in mobile communication system |
KR101528496B1 (en) * | 2009-04-17 | 2015-06-15 | 삼성전자주식회사 | Method and system for supporting emergency call using non-access stratum protocol for emergency call in mobile telecommunication system |
US8831014B2 (en) * | 2009-09-26 | 2014-09-09 | Cisco Technology, Inc. | Providing services at a communication network edge |
EP3125610A1 (en) | 2009-10-30 | 2017-02-01 | Interdigital Patent Holdings, Inc. | Method and apparatus for efficient signaling and usage of resources for wireless communications supporting circuit switched and packet switched sessions |
CN102860052B (en) | 2010-04-27 | 2015-11-25 | 日本电气株式会社 | Communication means, mobile network system and device |
US20120172066A1 (en) | 2010-04-27 | 2012-07-05 | Nec Corporation | Communication method, mobile network system and device |
US20120178479A1 (en) | 2010-04-27 | 2012-07-12 | Nec Corporation | Communication method, mobile network system and device |
JP5342511B2 (en) * | 2010-06-16 | 2013-11-13 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method and call session control server device |
US20110310868A1 (en) * | 2010-06-17 | 2011-12-22 | Telefonaktiebolaget L M Ericsson(Publ) | P-gw/ggsn issued paging requests |
-
2011
- 2011-04-27 CN CN201180021622.7A patent/CN102860052B/en active Active
- 2011-04-27 US US13/381,746 patent/US9451583B2/en active Active
- 2011-04-27 BR BR122016006460-3A patent/BR122016006460A2/en not_active Application Discontinuation
- 2011-04-27 ES ES13190476.5T patent/ES2535361T3/en active Active
- 2011-04-27 EP EP20130190476 patent/EP2699048B1/en active Active
- 2011-04-27 BR BR122016006458-1A patent/BR122016006458A2/en not_active Application Discontinuation
- 2011-04-27 KR KR1020127015597A patent/KR101332971B1/en active IP Right Grant
- 2011-04-27 BR BR122015021035-6A patent/BR122015021035A2/en not_active Application Discontinuation
- 2011-04-27 ES ES12159830.4T patent/ES2477566T3/en active Active
- 2011-04-27 EP EP20120159835 patent/EP2466983A3/en not_active Withdrawn
- 2011-04-27 EP EP20120159825 patent/EP2472989B1/en active Active
- 2011-04-27 ES ES11775029.9T patent/ES2444815T3/en active Active
- 2011-04-27 EP EP20120159828 patent/EP2472990B1/en active Active
- 2011-04-27 BR BR112012019257-4A patent/BR112012019257B1/en active IP Right Grant
- 2011-04-27 ES ES12159821.3T patent/ES2505640T3/en active Active
- 2011-04-27 KR KR1020127033174A patent/KR101293339B1/en active IP Right Grant
- 2011-04-27 EP EP20120159837 patent/EP2472992A1/en not_active Withdrawn
- 2011-04-27 WO PCT/JP2011/060215 patent/WO2011136248A1/en active Application Filing
- 2011-04-27 BR BR122016006464-6A patent/BR122016006464A2/en not_active Application Discontinuation
- 2011-04-27 EP EP20120159821 patent/EP2472988B1/en active Active
- 2011-04-27 EP EP20120159830 patent/EP2472991B1/en active Active
- 2011-04-27 JP JP2011552269A patent/JP4985880B2/en active Active
- 2011-04-27 EP EP11775029.9A patent/EP2448299B1/en active Active
- 2011-04-27 CN CN201510278013.XA patent/CN104936309B/en active Active
- 2011-04-27 CN CN201510280243.XA patent/CN104936310B/en active Active
- 2011-04-27 BR BR122016006463-8A patent/BR122016006463A2/en not_active Application Discontinuation
- 2011-04-27 BR BR122015021034-8A patent/BR122015021034A2/en not_active Application Discontinuation
- 2011-12-15 JP JP2011274455A patent/JP4962644B2/en active Active
- 2011-12-15 JP JP2011274808A patent/JP4968406B2/en active Active
- 2011-12-15 JP JP2011274801A patent/JP4968405B2/en active Active
- 2011-12-15 JP JP2011274774A patent/JP4962653B2/en active Active
- 2011-12-15 JP JP2011274499A patent/JP4962647B2/en active Active
- 2011-12-15 JP JP2011274781A patent/JP4962654B2/en active Active
- 2011-12-15 JP JP2011274747A patent/JP4962649B2/en active Active
- 2011-12-15 JP JP2011274830A patent/JP4968408B2/en active Active
- 2011-12-15 JP JP2011274796A patent/JP4962655B2/en active Active
- 2011-12-15 JP JP2011274483A patent/JP4962646B2/en active Active
- 2011-12-15 JP JP2011274738A patent/JP4962648B2/en active Active
- 2011-12-15 JP JP2011274761A patent/JP4962651B2/en active Active
- 2011-12-15 JP JP2011274464A patent/JP4962645B2/en active Active
- 2011-12-15 JP JP2011274767A patent/JP4962652B2/en active Active
- 2011-12-15 JP JP2011274817A patent/JP4968407B2/en active Active
- 2011-12-15 JP JP2011274757A patent/JP4962650B2/en active Active
-
2012
- 2012-03-15 US US13/421,628 patent/US8514786B2/en active Active
- 2012-03-15 US US13/421,621 patent/US20120202532A1/en not_active Abandoned
- 2012-03-15 US US13/421,575 patent/US8923194B2/en active Active
- 2012-05-02 JP JP2012105246A patent/JP2012151904A/en active Pending
-
2014
- 2014-12-29 US US14/584,710 patent/US20150119089A1/en not_active Abandoned
-
2015
- 2015-04-27 JP JP2015090439A patent/JP5967258B2/en active Active
-
2016
- 2016-06-23 US US15/190,344 patent/US9763281B2/en active Active
- 2016-09-23 US US15/274,088 patent/US10231114B2/en active Active
-
2019
- 2019-01-23 US US16/255,199 patent/US10595189B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003039186A1 (en) * | 2001-10-12 | 2003-05-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for retaining subscriber data contained in msc/vlr after system restart |
WO2003041435A1 (en) * | 2001-11-03 | 2003-05-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and node for the set-up of a connection in a telecommunication network |
EP1903821A2 (en) * | 2006-09-21 | 2008-03-26 | Innovative Sonic Limited | Method for handling radio link failure in wireless communications system and related apparatus |
JP2008079313A (en) * | 2006-09-21 | 2008-04-03 | Asustek Computer Inc | Method and apparatus for handling radio link failure in wireless communication system |
US20090239526A1 (en) * | 2008-03-21 | 2009-09-24 | Research In Motion Limited | Evolved Packet System Quality of Service Enforcement Deactivation Handling to Prevent Unexpected User Equipment Detach |
JP2010102166A (en) | 2008-10-24 | 2010-05-06 | Konica Minolta Business Technologies Inc | Electrophotographic photoreceptor, image forming method, and image forming apparatus |
Non-Patent Citations (5)
Title |
---|
3GPP: "3GPP TR 23.857 - 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study of EPC Nodes Restoration; (Release 10)", 3GPP STANDARD; 3GPP TR 23.857, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.2.0, 7 March 2011 (2011-03-07), pages 1 - 31, XP050476278 * |
3GPP: "TS 23.007 - 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Restoration procedures (Release 9)", 3GPP STANDARD; 3GPP TS 23.007, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V9.3.0, 6 April 2010 (2010-04-06), pages 1 - 39, XP050402405 * |
CATT: "Clarifying the bearers to be deactivated on the S5/S8 interface", 3GPP DRAFT; C4-100955(WAS 100924 CR0544)-CLARIFYING BEARERS TO BE DEACTIVATED, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. San Francisco, US; 20100222, 2 March 2010 (2010-03-02), XP050411498 * |
ERICSSON: "Discussion paper on the handling of hanging PDN connections/bearers Specs: 3GPP TS 23.007, 3GPP TS 29.274", 3GPP DRAFT; C4-100405_DISC_ON_THE_HANDLING_OF_HANGING_PDN_CONNECTIONS _BEARERS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. San Francisco, US; 20100222, 2 March 2010 (2010-03-02), XP050411046 * |
NEC: "EPC node failure", 3GPP DRAFT; C4-101116, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. Kyoto; 20100510, 17 May 2010 (2010-05-17), XP050411725 * |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10595189B2 (en) | Communication method, mobile network system and device | |
US20120172066A1 (en) | Communication method, mobile network system and device | |
US9060374B2 (en) | Communication method, mobile network system and device | |
US20120178479A1 (en) | Communication method, mobile network system and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AC | Divisional application: reference to earlier application |
Ref document number: 2448299 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20121009 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
INTG | Intention to grant announced |
Effective date: 20130709 |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2448299 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 631079 Country of ref document: AT Kind code of ref document: T Effective date: 20130915 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: T3 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602011002927 Country of ref document: DE Effective date: 20131031 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 631079 Country of ref document: AT Kind code of ref document: T Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131204 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131205 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140104 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602011002927 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140106 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20140605 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602011002927 Country of ref document: DE Effective date: 20140605 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: V1 Effective date: 20141101 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: LU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140427 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20141231 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140430 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140430 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140430 Ref country code: NL Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20141101 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140427 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20150427 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150427 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: RS Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20110427 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602011002927 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04W0076040000 Ipc: H04W0076200000 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130904 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240418 Year of fee payment: 14 |