HK1179089B - Method and apparatuses for receiving a mobility management entity name - Google Patents

Description

Method and apparatus for receiving mobility management entity name

Technical Field

Some embodiments of the present invention relate to communication networks, and more particularly to wireless communication networks, such as Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (UTRAN), Long Term Evolution (LTE) and evolved UTRAN (E-UTRAN).

Background

A Universal Mobile Telecommunications System (UMTS) network includes three interacting domains: core Network (CN), UMTS Terrestrial Radio Access Network (UTRAN) and User Equipment (UE). The main function of the CN is to provide switching, routing and transit for user traffic. The CN may also contain databases and network management functions.

The UTRAN includes base stations, or node bs, (nbs), and Radio Network Controllers (RNCs). The UTRAN considers the connectivity between the UE and the CN. The RNC provides control functionality for one or more node bs. The RNC and its corresponding node b (nb) are referred to as a Radio Network Subsystem (RNS).

Long Term Evolution (LTE) is concerned with improving the UMTS through improved efficiency and service, reduced cost, and the use of new spectrum opportunities. In particular, LTE is a third generation partnership project (3 GPP) standard that provides uplink speeds of up to 50 megabits per second (Mbps) and downlink speeds of up to 100 Mbps. As mentioned above, LTE is also expected to improve spectral efficiency in 3G networks, allowing operators to provide more data and voice services over a given bandwidth. Therefore, LTE is designed to meet future needs for high speed data and media transport in addition to high capacity voice support.

Disclosure of Invention

An embodiment of the invention includes a method. The method includes receiving a terminating request from a user equipment at a network node. The method may further include performing a recovery data procedure or an update location procedure, receiving a Mobility Management Entity (MME) name from another network element, and registering the MME name to subscriber data associated with the user equipment. The method then includes sending the paging request only to the MME indicated by the MME name received from the other network element.

Other embodiments of the present invention are directed to an apparatus comprising: a memory including computer program code; and at least one processor. With the at least one processor, the memory and the computer program code are configured to at least control the apparatus to: the method includes receiving a terminal request from a user equipment, performing a recovery data procedure or an update location procedure, receiving a Mobility Management Entity (MME) name from another network element, and registering the MME name to subscriber data associated with the user equipment. The apparatus further includes means for sending a paging request to only the MME indicated by the MME name received from the other network element.

Another embodiment of the invention includes a computer program embodied on a computer readable medium. The computer program, when executed, is configured to control a processor to perform operations. The operations include receiving a terminating request from a user equipment at a network node. The operations may further include performing a recovery data procedure or an update location procedure, receiving a Mobility Management Entity (MME) name from another network element, and registering the MME name to subscriber data associated with the user equipment. The operations also include sending the paging request only to the MME indicated by the MME name received from the other network element.

Drawings

For a proper understanding of the present invention, reference should be made to the accompanying drawings, in which:

FIG. 1 illustrates an example of a system according to one embodiment of this disclosure;

FIG. 2 illustrates a signaling diagram;

FIG. 3 illustrates a signaling diagram according to one embodiment;

FIG. 4 illustrates a flow diagram of a method according to an embodiment; and

fig. 5 illustrates an apparatus according to an embodiment of the invention.

Detailed Description

Evolved Packet System (EPS) is an architecture designed for LTE and is a successor to General Packet Radio System (GPRS). EPS is described in 3gpp ts23.401 and 3gpp ts23.402, the subject matter of which is incorporated herein by reference in their entirety. EPS provides a new radio interface and new packet core network functionality for broadband wireless data access. Such EPS core network functions include a Mobility Management Entity (MME) 130, a packet data network gateway (PDN-GW) 170, and a serving gateway (S-GW) 150, as shown in fig. 1.

Fig. 1 illustrates an example of an EPS architecture in which certain embodiments of the present invention may be implemented. The MME130 is an entity responsible for mobility management procedures in the EPS. For example, the MME130 is responsible for knowing the location of the subscriber in the E-UTRAN 102. MME130 authenticates the subscriber and supervises the resources granted to the subscriber by the control gateway. The subscriber's UE110 may be camped on the E-UTRAN102, UTRAN100, or GERAN101, but there are no two accesses at the same time. That is, when the UE110 is camped on the E-UTRAN102, it cannot be reached through the UTRAN100 or the GERAN 101.

A Serving GPRS Support Node (SGSN) 120, which may be responsible for packet routing or transport and authentication/charging functions, can be included in the architecture shown in fig. 1. Also, a Policy Charging and Rules Function (PCRF) 160 may be provided as a node for determining policy rules in the network and determining access to the operator's IP services 180.

For the initial period of EPS deployment (when EPS access is available in the spot area), Circuit Switched Fallback (CSFB) has been standardized at 3GPP23.272 for general services such as Unstructured Supplementary Service Data (USSD), positioning, Short Message Service (SMS) and calls available for UEs camped on E-UTRAN 102. The subject matter of 3GPP23.272 is hereby incorporated by reference in its entirety. 3GPP23.272 defines an SGs interface between MME130 and Mobile services switching center (MSC) Server (MSS)/Visitor Location Register (VLR) 190, which will be discussed in more detail below in conjunction with FIGS. 2 and 3.

When UE110 registers in EPS, it may indicate its CSFB capability in the request. If the EPS supports CSFB, the MME130 will perform a location update procedure on the SGs interface to the MSS/VLR190 on behalf of the UE 110. In turn, the MSS/VLR190 utilizes a normal location update procedure to download the CS subscription data from the Home Location Register (HLR)/Home Subscriber Server (HSS) 140 and stores the MMEID in the VLR database. Thus, the UE110 will also be registered with the MSS/VLR 190. Mobile Terminated (MT) CS events (call, SMS, MT-location request) for UE110 will be routed to the MSS 190.

When the MTCS event reaches the MSS190, the MSS190 sends a paging request to the MME130 over the SGs interface to indicate the incoming CS event and search for the location of the UE 110. The UE110 is forced back to the CS network (UTRAN/GERAN) using a CS fallback procedure for the call, USSD, and Location Request (LR) procedures, and the actual MTCS procedures (call, location request, USSD) are performed by the MSS190 when the UE110 is camped on the CS access network as if the UE110 were originally in the CS domain. When the service is performed, the UE110 returns to the EPS.

However, if subscriber data is deleted from the VLR190 for some reason (e.g., system restart, VLR restart) and an MTCS event arrives at the MSS190, the VLR does not know the MME130 address when the MTCS event arrives before the MME130 will re-register itself to the VLR over the SGs interface. The execution of the search procedure for this case is recommended by 3GPP29.118, which is incorporated herein in its entirety by reference, as shown in fig. 2.

As shown in fig. 2, when a VLR re-initiation 200 is present and a terminating request 201 is received, the VLR190 performs MAP recovery data 202 in accordance with 3GPP29.002, which is incorporated herein in its entirety by reference, in order to retrieve subscriber data from the HLR 140. The MSS190 performs a search 203 for the location of the subscriber on the a/Iu but in this case the subscriber is not located. The MSS190 then sends a paging request 204, 205, 206 to each MME130-1, 130-2, 130-3 connected thereto via the SGs interface to search for the location of the subscriber. After receiving the paging request, each MME130-1, 130-2, 130-3 pages its own area for determining the location of the subscriber 207 and returns a paging response 208 to the MSS190 over the SGs interface. When the MME has located the subscriber, the paging response may include an indication of the location of the subscriber.

Thus, as shown in fig. 2, the MSS190 needs to send a paging request to each MME130-1, 130-2, 130-3 connected thereto. This results in heavy operation, especially considering that VLR restart may affect many subscribers, and the MSS190 will need to perform a search procedure for all affected subscribers.

Thus, embodiments of the present invention take advantage of the fact that the MME name has already been delivered to HLR140 when the subscriber registers with the MME 130. More specifically, embodiments of the present invention propose to include the MME name into the Mobile Application Part (MAP) Insert Subscriber Data (ISD) message, as shown in fig. 3. Therefore, when the MTCS event reaches the MSS190 and the MSS/VLR190 performs the recovery data procedure, the MME name will be received from the HLR140 together with other subscriber data. Thus, the MSS/VLR190 will be aware of the current MME of the subscriber and the paging request will only be sent to this MME, thus avoiding the search procedure.

In one embodiment, the MME name is a parameter that contains the Diameter identity of the MME 130. If the subscriber is registered to the EPS, the HLR140 sends the MME name to the VLR190 during the Data recovery procedure if a recovery indicator is set in the MAP _ recovery _ Data (MAP _ Restore _ Data) request. If a resume indicator is set in the MAP Update Location (MAP Update Location) request, the HLR140 sends the MME name to the VLR190 during the Update Location procedure.

The resume indicator according to one embodiment is a parameter that, if present, indicates that the HLR sends the MME name in MAP Insert Subscriber Data (ISD) if the subscriber is registered to EPS, or the SGSN number if available and if the subscriber is registered to GPRS. The VLR may set the resume indicator during a CSFB mobile originated call if the VLR performs an implicit (implicit) location update.

Fig. 3 illustrates an exemplary signaling diagram according to one embodiment of the present invention. Similar to fig. 2, when a VLR re-initiation 300 is present and a terminating request 301 is received, the VLR190 executes MAP recovery data 302 to retrieve subscriber data from the HLR 140. However, rather than paging all MMEs 130-1, 130-2, 130-3 connected thereto, the MSS190 registers the MME name to the subscriber data and receives the MME name from the HLR in response to the recovery data procedure 302. If the HLR for CS mobility data and MME data is not in the same network element, the HLR140 performing the restore data procedure may retrieve the MME name from another HLR/HSS.

In one embodiment, the MME name may be received from HLR140 inserted in a MAP subscriber data service (ISD). Thus, the MSS only needs to send the paging request 303 over the SGs interface to one MME130-1 indicated by the MME name in the ISD received from the HLR 140. After receiving the paging request, the MME pages 304 its own area in order to determine the location of the subscriber and returns a paging response 305 to the MSS190 over the SGs interface. When the MME has located the subscriber, the paging response 305 may include an indication of the location of the subscriber. The call, SMS, USSD, and/or MT-LR may then be delivered as described in 3GPP23.272, which is incorporated herein by reference in its entirety.

Thus, as discussed above, when the HLR receives the resume data request and the MME name is registered to the subscriber data, HLR140 returns the MME name inserted in the subscriber data service (ISD) in the MAP to MSS 190. This avoids the need to perform the search procedure because the paging request would only need to be sent to the MME130-1 indicated by the MME name received in the MAPISD. For example, embodiments of the invention may be implemented in a network that uses an HLR product with an S6a interface towards the MME or HLR and is able to retrieve the identity of the MME by using some other means in order to correctly populate the subscription data.

As will be appreciated by those skilled in the art, the Mobile Application Part (MAP) is the SS7 protocol, which provides an application layer for various nodes in, for example, a UMTS mobile core network to communicate with each other in order to provide services to subscribers. The MAP is an application layer protocol used to access the HLR, VLR, MSC, device identity register, authentication center, SMS center, and serving GPRS support node.

Fig. 4 illustrates a method for mobility management according to an embodiment of the present invention. The method comprises the following steps: at 400, a terminating request is received from a UE at an MSS or VLR. The terminating request may be a mobile terminated CS event and may be received after a VLR restart that deletes subscriber data associated with the UE. In response to receiving the terminating request, the method further comprises: at 410, a recovery data procedure and/or an update location procedure is performed by the MSS or VLR. The method comprises the following steps: at 420, an MME name is received from the HLR during the recovery data procedure and/or the update location procedure. The method then includes: at 430, the MME name is registered to subscriber data associated with the UE. The method comprises the following steps: at 440, the paging request is sent only to the MME indicated by the MME name received from the HLR.

According to some embodiments, the methods described above may be stored as instructions on a computer-readable medium and executed by a processor. The computer readable medium may be a non-transitory medium that may be encoded with information that, when executed in hardware, performs a process corresponding to the process disclosed in fig. 4 or any other process discussed herein. Examples of non-transitory media include computer-readable media, computer distribution media, computer-readable storage media, and computer program products.

Fig. 5 illustrates a device 10 according to one embodiment, which device 10 may be configured to provide mobility management services. In some embodiments, the device 10 is implemented in a network element (such as a computing system, server, register, etc.). Device 10 may include a communication interface 12, such as a bus or other communication mechanism, for communicating information between components of device 10. Alternatively, the components of the device 10 may communicate directly with each other without the use of the communication interface 12.

Device 10 also includes a processor 22 coupled to communication interface 12 for receiving, managing, and/or processing user inputs or information, and for executing instructions or operations. The processor 22 may be any type of general or special purpose processor. In one embodiment, processor 22 may be included within an Application Specific Integrated Circuit (ASIC).

The device 10 further includes a memory 14 for storing information and instructions to be executed by the processor 22. Memory 14 may include any combination of Random Access Memory (RAM), Read Only Memory (ROM), static storage devices such as magnetic or optical disks, or any other type of machine or computer readable medium. Computer readable media can be any available media that can be accessed by processor 22 and may include both volatile and nonvolatile media, removable and non-removable media, and communication media. Communication media may include computer program code or instructions, data structures, program modules or other data, and includes any information delivery media.

The device 10 may further comprise a transceiver 20 for receiving information from and/or transmitting information to other network elements in the network. Transceiver 20 may be a separate component of device 10 or, alternatively, transceiver 20 may be included as a function of processor 22. In one embodiment, the memory 14 stores software modules or applications 16, which software modules or applications 16 provide functionality when executed by the processor 22. The modules may include an operating system 15 that provides operating system functionality for the device 10.

As shown in fig. 5, some embodiments of the present invention are directed to an apparatus 10. The apparatus 10 comprises; at least one processor 22; and at least one memory 14 including computer program code. With the at least one processor 22, the at least one memory 14 and the computer program code are configured to cause the apparatus 10 at least to receive a terminating request from the UE. In some embodiments, the termination request is a mobile terminated CS event, such as a call, USSD, SMS, or MT-LR. The termination request may be received after a VLR restart that deletes subscriber data associated with the UE. With the at least one processor 22, the at least one memory 14 and the computer program code are further configured to cause the apparatus 10 to perform a restore data procedure and/or an update location procedure, and receive an MME name from the HLR during the restore data procedure and/or the update location procedure. With the at least one processor 22, the at least one memory 14 and the computer program code are further configured to cause the apparatus 10 to register an MME name to the subscriber data, and send a paging request only to the MME indicated by the MME name received from the HLR. In some embodiments, the device 10 is an MSS and/or a VLR.

The computer readable media mentioned above may be embodied, at least in part, by a transmission line, a compact disk, a digital video disk, a magnetic tape, a bernoulli drive, a magnetic disk, a holographic disk or tape, flash memory, magnetoresistive memory, integrated circuits, or any other digital processing apparatus storage device.

It should be noted that many of the functional features described in this specification have been presented as modules, applications, and so forth, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be partially implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose.

Indeed, a module of executable code or algorithm may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

The described features, advantages, and characteristics of the invention may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the invention.

One of ordinary skill in the art will readily appreciate that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations different from those disclosed. Thus, while the invention has been described based upon these preferred embodiments, it would be apparent to those skilled in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. For the purpose of determining the metes and bounds of the invention, therefore, reference should be made to the appended claims.

Claims (15)

1. A method for receiving a mobility management entity name, comprising:

receiving a mobile terminated circuit switched event as a termination request from the user equipment at the network node;

performing at least one of a restore data process and an update location process;

receiving the mobility management entity name from a home location register;

registering the mobility management entity name to subscriber data associated with the user equipment; and

the paging request is sent only to the mobility management entity indicated by the received mobility management entity name.

2. The method of claim 1, wherein receiving the mobility management entity name comprises: the mobility management entity name is received during the resume data procedure when a resume indicator is set in a mobile application part resume data request.

3. The method according to claim 1 or 2, wherein receiving the mobility management entity name comprises: the mobility management entity name is received during the update location procedure when a resume indicator is set in a mobile application part update location request.

4. The method according to claim 2, wherein the recovery indicator is configured to indicate that the mobility management entity name is received from the home location register when the user equipment is registered to an evolved packet system, and wherein the recovery indicator is configured to indicate that a serving general packet radio system support node number is received when the recovery indicator is available and when the user equipment is registered to a general packet radio system.

5. The method of any of claims 2 or 4, further comprising setting the recovery indicator by a visitor location register.

6. A method according to any of claims 1, 2 or 4, wherein receiving the terminating request comprises receiving the terminating request after a visitor location register restart deleting subscriber data associated with the user equipment.

7. The method of any of claims 1, 2 or 4, wherein receiving the mobility management entity name comprises receiving a mobility management entity name for a mobile application part insertion into a subscriber data service.

8. An apparatus for receiving a mobility management entity name, comprising:

means for receiving a mobile terminated circuit switched event as a termination request from the user equipment at the network node;

means for performing at least one of a recovery data process and an update location process;

means for receiving the mobility management entity name from a home location register;

means for registering the mobility management entity name with subscriber data associated with the user equipment; and

means for sending the paging request only to the mobility management entity indicated by the received mobility management entity name.

9. The apparatus of claim 8, wherein the means for receiving the mobility management entity name comprises: means for receiving the mobility management entity name during the resume data procedure when a resume indicator is set in a mobile application part resume data request.

10. The apparatus according to claim 8 or 9, wherein the means for receiving the mobility management entity name comprises: means for receiving the mobility management entity name during the update location procedure when the resume indicator is set in the mobile application part update location request.

11. The apparatus according to claim 9, wherein the recovery indicator is configured to indicate that the mobility management entity name is received from the home location register when the user equipment is registered to an evolved packet system, and wherein the recovery indicator is configured to indicate that a serving general packet radio system support node number is received when the recovery indicator is available and when the user equipment is registered to a general packet radio system.

12. The apparatus of any of claims 9 or 11, further comprising means for setting the restoration indicator by a visitor location register.

13. An arrangement according to any of claims 8, 9 or 11, wherein the means for receiving the termination request comprises means for receiving the termination request after a visitor location register restart deleting subscriber data associated with the user equipment.

14. The apparatus according to any of claims 8, 9 or 11, wherein the means for receiving the mobility management entity name comprises means for receiving a mobility management entity name in a mobile application part insertion subscriber data service.

15. An apparatus for receiving a mobility management entity name, comprising:

means for receiving a mobile terminated circuit switched event as a termination request from the user equipment;

means for performing at least one of a recovery data process and an update location process;

means for receiving the mobility management entity name from a home location register;

means for registering the mobility management entity name with subscriber data associated with the user equipment; and

means for sending the paging request only to the mobility management entity indicated by the received mobility management entity name.