WO2019166837A1 - Procédé et appareil pour rediriger un équipement utilisateur vers un autre nœud de commande de mobilité - Google Patents

Procédé et appareil pour rediriger un équipement utilisateur vers un autre nœud de commande de mobilité Download PDF

Info

Publication number
WO2019166837A1
WO2019166837A1 PCT/GR2018/000018 GR2018000018W WO2019166837A1 WO 2019166837 A1 WO2019166837 A1 WO 2019166837A1 GR 2018000018 W GR2018000018 W GR 2018000018W WO 2019166837 A1 WO2019166837 A1 WO 2019166837A1
Authority
WO
WIPO (PCT)
Prior art keywords
control node
user equipment
identifier
different
globally unique
Prior art date
Application number
PCT/GR2018/000018
Other languages
English (en)
Inventor
Georgios GKELLAS
Devaki Chandramouli
Thierry Van De Velde
Original Assignee
Nokia Technologies, OY
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies, OY filed Critical Nokia Technologies, OY
Publication of WO2019166837A1 publication Critical patent/WO2019166837A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node

Definitions

  • An example embodiment relates generally to a method, apparatus and computer program product for the attachment of user equipment to a core network and, more particularly, for redirecting the user equipment during the attachment process.
  • a user equipment commonly attaches to a packet core network. More specifically, the user equipment attaches to a mobility management entity (MME) of an evolved packet core (EPC) in order to obtain second generation (2G), third generation (3G), fourth generation (4G) and fifth generation (5G) services.
  • MME mobility management entity
  • EPC evolved packet core
  • the UE may alternatively attach to an access and mobility management function (AMF) or a 5G core (5GC) to obtain 4G, 5G and non-3 rd generation partnership project (3GPP) services.
  • AMF access and mobility management function
  • 5GC 5G core
  • the term mobility control node will be used to include both an MME and AMF.
  • the term core network will be used to denote both an EPC and a 5GC. In some instances, it is required to redirect the UE to a different control node than the control to which the UE originally attempted to attach.
  • the public land mobile network may include a new EPC (supporting enhancements for 5G as specified by 3 GPP) overlay to a legacy EPC, with the new EPC intended to serve 5G-capable UEs and the legacy EPC limited to serving legacy, non-5G UEs.
  • a legacy UE may attempt to attach to the EPC overlay and may be redirected to the legacy EPC.
  • the PLMN network may include mobility management functions provided by different vendors supporting specialized services provided by the different vendors. In this situation, a UE may attempt to attach to an MME of a first vendor and, as a result, may be redirected to the MME of a second vendor.
  • multiple virtualized packet core network instances are deployed in the same PLMN, and the mobile network operator (MNO) wishes to dedicate certain instances to groups of UEs.
  • MNO mobile network operator
  • the EPC instances may be operated by different organizations. Even within a single EPC instance, load rebalancing may be required between the various MMEs of the core network and, as a result, may redirect UEs from the MME to the other MMEs in the PLMN.
  • the 3 GPP has provided techniques, such as a multiple operator core network (MOCN) to provide for redirection to a core network serving a different PLMN identifier (ID).
  • MOCN requires multiple PLMN IDs to be supported by the radio access network (RAN) and specific subscription data to be provisioned in the HSS (for UEs to access the different core networks).
  • RAN radio access network
  • 3 GPP dedicated core networks DECOR and evolved DECOR (eDECOR) are techniques that provide redirection to a different EPC instance within a single PLMN. However, they require specific subscription information to be provisioned in the home subscription server (HSS) or 5G unified data management function (UDM) and to be interpreted by the RAN to select the appropriate core network. Additionally, although DECOR is transparent to the UE, eDECOR requires UE support.
  • a method, apparatus and computer program product are provided in accordance with an example embodiment in order to redirect a user equipment (UE) in a manner that is transparent to the radio access network (RAN) and that does not require that any subscription information be provisioned in the home subscription service (HSS) nor the unified data management (UDM).
  • UE user equipment
  • the method, apparatus and computer program product of an example embodiment may be readily implemented in order to redirect the UE in any of a variety of different situations.
  • the method, apparatus and computer program product of an example embodiment permit redirection of the UE from an evolved packet core (EPC) supporting enhancements for 5G to a legacy EPC, such as in an instance in which the UE does not support 5G service.
  • EPC evolved packet core
  • the method, apparatus and computer program product of another example embodiment are configured to redirect a UE that is attempting to attach to an MME of a first vendor to the MME of a second vendor that supports specialized services sought by the UE.
  • the method, apparatus and computer program product of an example embodiment may redirect a UE to the virtualized packet core network instance dedicated by the mobile network operator (MNO) to a group of UEs that includes the UE in question.
  • the method, apparatus and computer program product may redirect a UE to an EPC instance operated by a different organization.
  • the method, apparatus and computer program product of an example embodiment are configured to redirect the UE in order to rebalance the load imposed upon the plurality of MMEs of the core network.
  • the method, apparatus and computer program product of an example embodiment are configured to provide for the desired redirection of the UE a manner that is transparent to and requires no reconfiguration of the RAN and that does not require provisioning of any specific subscription information in the HSS or the UDM.
  • a method includes receiving a first global identifier of a user equipment during an attachment process to a mobility control node of a core network.
  • the first global identifier includes a globally unique identifier of the mobility control node and a local identifier field for the user equipment within the mobility control node.
  • the method determines that the user equipment has been redirected from a different control node.
  • the method causes a reallocation command to be transmitted to the user equipment.
  • the reallocation command comprises a second global identifier of the user equipment including the globally unique identifier of the mobility control node and the local identifier field having a first locally unique user equipment identifier, different than the ' predefined flag value.
  • the method of an example embodiment may also include receiving a third global identifier of the user equipment during the attachment process.
  • the third global identifier comprises a globally unique identifier of the different control node and the local identifier field having a second locally unique user equipment identifier.
  • the method of this example embodiment also includes determining, based upon the first and second globally unique identifiers of the mobility control node, whether the mobility control node and the different control node are members of a common control node group. In a case in which the mobility control node and a different control node are members of the common control node group, the method obtains context information relating to the user equipment from the different control node.
  • the second and third global identifiers of the user equipment include different global unique temporary identities of the user equipment.
  • the mobility control node of the core network includes a mobility management entity (MME)
  • the globally unique identifiers of the mobility control node and the different control node are different globally unique MME identifiers (GEiMMEIs) and the first and second locally unique user equipment identifiers includes different MME temporary mobile subscriber identities (M-TMSIs).
  • the globally unique identifiers of the mobility control node and the different control node are different globally unique AMF identifiers (GEiAMIs) and the first and second locally unique user equipment identifiers include different fifth generation temporary mobile subscriber identities (5G-TMSIs).
  • GEiAMIs globally unique AMF identifiers
  • 5G-TMSIs fifth generation temporary mobile subscriber identities
  • an apparatus in another example embodiment, includes means for receiving a first global identifier of a user equipment during an attachment process to the apparatus.
  • the first global identifier includes a globally unique identifier of the apparatus and a local identifier field for the user equipment within the apparatus.
  • the apparatus also includes the means for determining, in a case in which the local identifier field has a predefined flag value, such as a null value or a specifically reserved value, that the user equipment has been redirected from a different control node.
  • the apparatus further includes means for causing a reallocation command to be transmitted to the user equipment in a case in which the user equipment has been redirected from the different control node.
  • the reallocation command comprises a second global identifier of the user equipment including the globally unique identifier of the apparatus and the local identifier field having a first locally unique user equipment identifier, different than the predefined flag value.
  • the apparatus of an example embodiment also includes means for receiving a third global identifier of the user equipment during the attachment process.
  • the third global identifier comprises a globally unique identifier of the different control node and the local identifier field has a second locally unique user equipment identifier.
  • the embodiment also includes means for determining, based upon the first and second globally unique identifiers of the mobility control node, whether the apparatus and the different control node are members of a common control node group.
  • the apparatus of this example embodiment also includes means for obtaining context information relating to the user equipment from the different control node in a case in which the apparatus and the different control node are members of the common control node group.
  • the second and third global identifiers of the user equipment include different globally unique temporary identities of the user equipment.
  • the apparatus comprises a mobility management entity (MME)
  • MME mobility management entity
  • GUMMEIs globally unique MME identifiers
  • M- TMSIs MME temporary mobile subscriber identities
  • the apparatus comprises an access and mobility management function (AMF)
  • the globally unique identifiers of the mobility control node and the different control node are different globally unique AMF identifiers (GUAMIs) and the first and second locally unique user equipment identifiers include different fifth generation temporary mobile subscriber identities (5G-TMSIs).
  • GUIAMIs globally unique AMF identifiers
  • 5G-TMSIs fifth generation temporary mobile subscriber identities
  • an apparatus in a further example embodiment, includes at least one processor and at least one memory including computer program code for one or more programs with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to receive a first global identifier of a user equipment during an attachment process to the apparatus.
  • the first global identifier includes a globally unique identifier of the apparatus and a local identifier field for the user equipment within the apparatus.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to determine that the user equipment has been redirected from a different control node.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apprantus to cause a reallocation command to be transmitted to the user equipment.
  • the reallocation command comprises a second global identifier of the user equipment including the globally unique identifier of the apparatus and the local identifier field having a first locally unique user equipment identifier, different than the predefined flag value.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus of an example embodiment to receive a third global identifier of the user equipment during the attachment process.
  • the third global identifier comprises a globally unique identifier of the different control node and the local identifier field has a second locally unique user equipment identifier.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus of this example embodiment to determine whether the apparatus and the different control node are members of a common node group and, in a case in which the apparatus and the different control node are members of a common control node group, to obtain context information relating to the user equipment from the different control node.
  • the second and third global identifiers of the user equipment include different globally unique temporary identities of the user equipment.
  • the apparatus comprises a mobility management entity (MME)
  • MME mobility management entity
  • GUMMEIs MME temporary mobile subscriber identities
  • M-TMSIs MME temporary mobile subscriber identities
  • the apparatus comprises an access and mobility management function (AMF)
  • the globally unique identifiers of the mobility control node and the different control node are different globally unique AMF identifiers (GUAMIs) and the first and second locally unique user equipment identifiers include different fifth generation temporary mobile subscriber identities (5G-TMSIs).
  • a computer program product includes at least one non-transitory computer-readable storage medium having computer executable program code instructions stored therein with the computer executable program code instructions including program code instructions configured, upon execution, to receive a first global identifier of a user equipment during an attachment process to a mobility control node of a core network.
  • the first global identifier includes a globally unique identifier of the mobility control node and a local identifier field for the user equipment within the mobility control node.
  • a computer-executable program code instructions also include program code instructions configured, upon execution, to determine, in a case in which the local identifier field has a predefined flag value, such as a null value or a specifically reserved value, that the user equipment has been redirected from a different control node.
  • the computer-executable program code instructions also include program code instructions configured, upon execution, to cause a reallocation command to be transmitted to the user equipment in a case in which the user equipment has been redirected from the different control node.
  • the reallocation command comprises a second global identifier of the user equipment including the globally unique identifier of the mobility control node and the local identifier field having a first locally unique user equipment identifier, different than the predefined flag value.
  • the computer-executable program code instructions of an example embodiment also include program code instructions configured, upon execution, to receive a third global identifier of the user equipment during the attachment process.
  • the third global identifier comprises a globally unique identifier of the different control node and the local identifier field having a second locally unique user equipment identifier.
  • the computer-executable program code instructions of this example embodiment also include program code instructions configured, upon execution, to determine, based upon the first and second globally unique identifiers of the mobility control node whether the mobility control node and the different control node are members of a common control node group and, in a case in which the mobility control node and the different control node are members of the common control node group, to obtain context information relating to the user equipment from the different control node.
  • the second and third global identifiers of the user equipment include different globally unique temporary identities of the user equipment.
  • the mobility control node of the core network includes a mobility management entity (MME)
  • MME mobility management entity
  • GUMMEIs globally unique MME identifiers
  • M- TMSIs MME temporary mobile subscriber identities
  • the mobility control node of the core network includes an access and mobility management function (AMF)
  • AMF access and mobility management function
  • GUIAMIs globally unique AMF identifiers
  • the first and second locally unique user equipment identifiers include different fifth generation temporary mobile subscriber identities (5G-TMSIs).
  • a method includes receiving, at a user equipment, a non-access stratum reject message.
  • the non-access stratum reject message comprises a target tracking area identifier.
  • the non-access stratum reject message also comprises either an attach reject message or a tracking area update reject message.
  • the non- access stratum reject message of an example embodiment indicates to the user equipment that the use equipment is being redirected.
  • the method also includes creating a non-access stratum request message.
  • the non-access stratum request message includes the target tracking area identifier.
  • the non-access stratum request message also comprises either an attach request message or a tracking area update message.
  • the method further includes causing the non-access stratum request message to be sent toward a mobility control node of a core network. In one example embodiment, causing the non-access stratum request message to be sent toward the mobility control node of the core network provides for cell re-selection within the same public land mobile network based on the target tracking area identifier.
  • an apparatus in another example embodiment, includes means for receiving, at a user equipment, a non-access stratum reject message.
  • the non-access stratum reject message comprises a target tracking area identifier.
  • the non-access stratum reject message also comprises either an attach reject message or a tracking area update reject message.
  • the non-access stratum reject message of an example embodiment indicates to the user equipment that the use equipment is being redirected.
  • the apapratus also includes means for creating a non-access stratum request message.
  • the non-access stratum request message includes the target tracking area identifier.
  • the non-access stratum request message also comprises either an attach request message or a tracking area update message.
  • the apparatus further includes means for causing the non-access stratum request message to be sent toward a mobility control node of a core network.
  • causing the non-access stratum request message to be sent toward the mobility control node of the core network provides for cell re-selection within the same public land mobile network based on the target tracking area identifier.
  • an apparatus in a further example embodiment, includes at least one processor and at least one memory including computer program code for one or more programs with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to receive, at a user equipment, a non-access stratum reject message.
  • the non-access stratum reject message comprises a target tracking area identifier.
  • the non-access stratum reject message also comprises either an attach reject message or a tracking area update reject message.
  • the non-access stratum reject message of an example embodiment indicates to the user equipment that the use equipment is being redirected.
  • the at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus to create a non-access stratum request message.
  • the non-access stratum request message includes the target tracking area identifier.
  • the non-access stratum request message also comprises either an attach request message or a tracking area update message.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to cause the non-access stratum request message to be sent toward a mobility control node of a core network.
  • causing the non- access stratum request message to be sent toward the mobility control node of the core network provides for cell re-selection within the same public land mobile network based on the target tracking area identifier.
  • a computer program product includes at least one non-transitory computer-readable storage medium having computer executable program code instructions stored therein with the computer executable program code instructions including program code instructions configured, upon execution, to receive, at a user equipment, a non-access stratum reject message.
  • the non-access stratum reject message comprises a target tracking area identifier.
  • the non-access stratum reject message also comprises either an attach reject message or a tracking area update reject message.
  • the non- access stratum reject message of an example embodiment indicates to the user equipment that the use equipment is being redirected.
  • the computer executable program code instructions also include program code instructions configured, upon execution, to create a non-access stratum request message.
  • the non-access stratum request message includes the target tracking area identifier.
  • the non-access stratum request message also comprises either an attach request message or a tracking area update message.
  • the computer executable program code instructions further include program code instructions configured, upon execution, to cause the non-access stratum request message to be sent toward a mobility control node of a core network.
  • causing the non-access stratum request message to be sent toward the mobility control node of the core network provides for cell re-selection within the same public land mobile network based on the target tracking area identifier.
  • Figure 1 depicts a network configuration that may be configured to redirect a UE in accordance with an example embodiment of the present disclosure
  • Figure 2 is a block diagram of an apparatus configured in accordance with an example embodiment in order to redirect a UE to a mobility control node of a core network;
  • Figure 3 illustrates operations performed, such as by the apparatus of Figure 2, in order to redirect the UE to a mobility control node of a core network in accordance with a example embodiment of the present disclosure
  • Figure 4 is a signal flow diagram including the operations depicted in the flowchart of Figure 3 in order to redirect a UE to a mobility control node of the core network in accordance with an example embodiment of the present disclosure
  • Figure 5 illustrates operations performed, such as by the apparatus of Figure 2, in order to redirect the UE to a mobility control node of a core network in accordance with another example embodiment of the present disclosure
  • Figure 6 is a signal flow diagram including the operations depicted in the flowchart of Figure 5 in which a UE is redirected to a mobility control node of a core network in accordance with a different example embodiment of the present disclosure.
  • circuitry refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present.
  • This definition of‘circuitry’ applies to all uses of this term herein, including in any claims.
  • the term‘circuitry’ also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware.
  • the term‘circuitry’ as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, field
  • programmable gate array and/or other computing device.
  • a method, apparatus and computer program product are provided in order to provide for redirection of a user equipment (UE) attempting to attach to a core node of a particular instance of a core network to a different control node, such as the control node of a different instance of the core network.
  • the redirection of the UE may be performed for various purposes.
  • one or more of the core network instances may be configured to service legacy, non-5G UEs, such as UEs configured to operate in accordance with fourth generation (4G) networks or the like, while one or more core network instances, such as a new EPC overlay, supporting enhancements for 5G as specified by 3GPP, to the legacy EPC, may be configured to service 5G-capable UEs, that is, UEs configured to communicate via 5G networks.
  • legacy, non-5G UE such as a UE configured to be served by 4G network
  • the legacy non-5G UE may be redirected to the legacy EPC.
  • the public land mobile network may include mobility management entity functions provided by different vendors supporting specialized services provided by the different vendors.
  • a UE attempting to attach to the mobility management entity (MME) of a first vendor may be redirected to the MME of a second vendor that provides the specialized service sought by the UE.
  • MME mobility management entity
  • multiple virtualized packet core network instances are deployed in the same PLMN and the mobile network operator (MNO) may dedicate certain instances to groups of UEs and/or certain EPC instances may be operated by different organizations.
  • a UE of a group of UEs may be redirected to the packet core network instance dedicated to the group of UEs of which the UE is a member, such as by being redirected to the packet core network instance operated by the organization with which the UE is affiliated.
  • redirection of a UE between the various MMEs of the core network may be performed in order to re-balance the load supported by the plurality of MMEs, such as from more heavily loaded MMEs to more lightly loaded MMEs in order to balance the load and to provide more uniform and consistent service to the UEs. While several example scenarios that may lead to redirection are provided, these scenarios are provided by way of illustration and not of limitation, as a UE may also be redirected in any of a number of other scenarios.
  • the network includes a plurality of core network instances of the same PLMN including a source core network instance 10 and a target core network instance 12.
  • the source and target core network instances may be identical or may otherwise be configured to support the same generation of UEs, such as 5G-capable UEs.
  • the redirection between the core network instances may be performed for load management, e.g., load re balancing.
  • the core network instances may be provided by different vendors or operated by different organizations such that redirection of the UEs between the core network instances may be performed to redirect the UE from the source core network instance of a first vendor or a first organization to the target core network instance of a different vendor or different organization with which the UE is configured to be serviced.
  • the core network instances may be configured to support different generations of UEs configured to operate in accordance with different cellular communications standards.
  • one or more of the core network instances may be a legacy core network instance, such as a legacy EPC configured to service, for example, legacy, non-5G UEs, while another core network instance, such as the target core network instance, may be a new EPC overlay to the legacy, EPC configured to service 5G-capable UEs.
  • the UE may be redirected in accordance with an example embodiment so as to be serviced by a core network instance configured to support the particular UE, such as a legacy non-5G UE supported by the legacy EPC or a 5G-capable UE supported by the new EPC overlay.
  • redirection may also occur in accordance with an example embodiment within a single core network instance, such as from one MME to a different MME, for load re-balancing purposes.
  • each core network instance may include one or more mobility control nodes, such as an MME or an access control and mobility management function (AMF) in a 5G core network instance, such as a 5GC overlay.
  • MME mobility control nodes
  • AMF access control and mobility management function
  • 5G core network instance such as a 5GC overlay
  • an MME will be discussed hereinafter, although the control node may alternatively be an AMF in other embodiments.
  • the source core network instance 10 may include a source control node 14 and the target core network instance 12 may include a target control node 16.
  • the network In order to facilitate communication between the user equipment 18, such as a mobile telephone, a smartphone, a laptop computer or other communication device, and the core network instances, the network also generally includes a radio access network 20, such as an evolved universal terrestrial radio access network (E-UTRAN) or the like. While the network of Figure 1 depicts a single radio access network connecting the user equipment to each of the core network instances, the network may include multiple radio access networks interconnecting the user equipment to one of the core network instances or to different ones of the core network instances.
  • E-UTRAN evolved universal terrestrial radio access network
  • an apparatus 30 is provided and as shown, for example, in Figure 2.
  • the apparatus may be embodied by any of a variety of different components and, in one embodiment, is embodied by the mobility control node of a core network instance, such as the target control node 16 of the target core network instance 12, e.g., an MME of an EPC overlay supporting enhancements for 5G.
  • the apparatus of an example embodiment includes, is associated with or is otherwise in
  • a processor 32 In communication with a processor 32, an associated memory 34 and a communication interface 36.
  • the processor 32 (and/or co-processors or any other circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 34 via a bus for passing information among components of the apparatus 30.
  • the memory device may be non-transitory and may include, for example, one or more volatile and/or non-volatile memories.
  • the memory device may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor).
  • the memory device may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present disclosure.
  • the memory device could be configured to buffer input data for processing by the processor.
  • the memory device could be configured to store instructions for execution by the processor.
  • the apparatus 30 may, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single“system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • the processor 32 may be embodied in a number of different ways.
  • the processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special- purpose computer chip, or the like.
  • the processor may include one or more processing cores configured to perform independently.
  • a multi-core processor may enable multiprocessing within a single physical package.
  • the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
  • the processor 32 may be configured to execute instructions stored in the memory device 34 or otherwise accessible to the processor.
  • the processor may be configured to execute hard coded functionality.
  • the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly.
  • the processor when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein.
  • the processor when the processor is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed.
  • the processor may be a processor of a specific device (e.g., an image processing system) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein.
  • the processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.
  • ALU arithmetic logic unit
  • the communication interface 36 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network.
  • the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network.
  • the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s).
  • the communication interface may alternatively or also support wired communication.
  • the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.
  • the operations performed by the apparatus 30 in order to redirect the UE 18 between control nodes, such as from the control node of a source core network instance 10 to a mobility control node of a target core network instance 12 or between control nodes of the same core network instance, are depicted in a flowchart of Figure 3 and more particularly in conjunction with redirection between a source MME 14 and a target MME 16 in the signal flow diagram of Figure 4.
  • the user equipment attempts to attach to a core network instance, such as the source core network instance, such as by transmitting an attach request or a tracking area update (TAU) request to the source core network instance and, more particularly, to the source control node 14, e.g., the source MME.
  • a core network instance such as the source core network instance
  • TAU tracking area update
  • the source control node transmits a response, such as a reject message, to the UE as shown by signal flow 52 of Figure 4.
  • the source control node may decline to serve the UE and may, in turn, generate the reject message for various reasons including, as described above, an attempt by a legacy non-5G UE to attach to an EPC overlay supporting enhancements for 5G, an attempt by the UE to attach to a control node of a different vendor or a different organization than that which services the UE or an attempt to attach to a control node which is overloaded relative to other control nodes with the attachment request being redirected for load management, e.g., load re-balancing, purposes.
  • load management e.g., load re-balancing
  • the reject message issued by the source core network instance 10, such as the source control node 14, includes a first global identifier of the UE 18 that has been allocated by the source core network instance for the UE.
  • the first global identifier of the UE may be a globally unique temporary identity (GUTI) of the UE.
  • GUI globally unique temporary identity
  • the first global identifier of the UE generally includes a globally unique identifier of the mobility control node to which the UE is being redirected.
  • the global identifier of the control node may be a globally unique MME identity (GUMMEI) of the MME.
  • the first global identifier of the UE also includes a local identifier field for the UE within the mobility control node to which the UE is being redirected.
  • the local identifier field has a predefined flag value indicative of the redirection.
  • the predefined flag value may have various predefined values indicative of a redirection, one example of a predefined flag value indicative of redirection is 0x00000000.
  • the UE 18 upon receipt of the reject message, the UE 18 is configured to transmit an attach request or a TAU request to the target core network instance 12 that is identified by the global identifier of the target control node 16, e.g., the GUMMEI provided by the source core network instance 10 in conjunction with the reject message. Accordingly, as shown in block 40 of Figure 3, the target core network instance, such as the target control node, receives the attach request or the TAU request including the first global identifier of the UE.
  • the target core network instance such as the target control node
  • the first global identifier may be in the form of a new GUTI assigned by the source core network instance that has the globally unique identifier of the target core network instance, e.g., the mobility control node, and a local identifier field for the UE within the mobility control node.
  • the local identifier field will have a predefined flag value, such as a null value or a specifically reserved value, in a case in which the UE is redirected to the mobility control node from a different control node, e.g., the source control node.
  • the apparatus 30 includes means, such as the processor 32, the communication interface 36 or the like, configured to receive the first global identifier of the UE 18 during the attachment process.
  • the target core network instance 12, such as the target control node 16, that is, the mobility control node, is configured in accordance with an example embodiment to determine whether the attach or TAU request is provided in conjunction with the redirection of the UE.
  • the apparatus 30 embodied by the target control node, such as a target MME includes means, such as the processor 32 or the like, configured to determine whether the local identifier field for the UE 18 has a predefined flag value.
  • the apparatus embodied by the target control node, such as the target MME includes means, such as the processor or the like, for determining that the user equipment has been redirected from a different control node.
  • the apparatus includes means, such as the processor, the communication interface 36 or the like, for causing a reallocation command to be transmitted to the UE 18. See, block 44 of Figure 3 as well as signal flow 56 of Figure 4.
  • the reallocation command is associated with and generally includes a second global identifier of the UE 18.
  • the second global identifier of the user equipment includes the globally unique identifier of the target control node 16 of the target control network instance 12 and the identifier field includes a first locally unique user equipment identifier within the target control node of the target core network instance.
  • the globally unique identifier of the target control node is the same globally unique identifier of the target control node as provided by the source control node in the reject message.
  • the first locally unique user equipment identifier is different than the predefined flag value that is utilized to indicate the redirection of the UE.
  • the target core network instance is an EPC overlay supporting
  • the first locally unique user equipment identifier that is provided by the second global identifier includes an MME temporary mobile subscriber identity (M-TMSI) or a 5G-TMSI, respectively, although the a first globally unique temporary identity in the form of an M-TMSI will be referenced below for purposes of illustration but not limitation.
  • M-TMSI MME temporary mobile subscriber identity
  • 5G-TMSI 5G-TMSI
  • the apparatus 30 includes means, such as the proessor 32 or the like, configured to determine whether a third global identifier of the UE 18 is received during the attachment process. See block 46 of Figure 3.
  • the third global identifier includes a globally unique identifier of the different control node from which the UE is redirected, that is, the source control node, and the local identifier field having a second locally unique user equipment identifier.
  • the third global identifier of the UE may have been provided in conjunction with the attach or TAU request to the source control node and may now also be provided to the mobility control node following redirection of the UE.
  • the globally unique identifier of the different control node from which the UE is redirected may be the GUMMEI of the source MME and the second locally unique user equipment identifier may be an M-TMSI value that temporarily identifies the UE to the source core network instance.
  • the apparatus 30 is configured to obtain and utilize context information relating to the context of the UE 18 and its service from the source core network instance 10, such as the source control node 14.
  • the apparatus includes means, such as the processor 32 or the like, configured to determine whether the target control node 16 and the source control node 14 are members of a common control node group.
  • the apparatus of an example embodiment includes means, such as the processor, the communication interface 36 or the like, configured to determine whether a third global identifier of the UE, such as a third GUTI, different than the second GUTI, is received during the attachment process. See block 48.
  • the apparatus 30 is capable of distinguishing multiple UEs being redirected to the mobility control node with a local identifier field having the same predefined flag value.
  • the apparatus 30 is configured to determine whether the mobility control node and the different control node, that is, the target and source control nodes, respectively, are members of the common control node group. Although this analysis may be performed in various manners, the apparatus, such as the processor, of an example embodiment is configured to analyze the second and third GUTIs to determine if both the second and third GUTIs have the same MME group identifier (MMEGI).
  • MMEGI MME group identifier
  • the apparatus such as the processor, is configured to determine that the source control node and target control node are in the same pool and, as a result, are members of a common control node group.
  • the apparatus includes means, such as the processor, the communication interface 36 or the like, configured to obtain context information for the UE from the source control node, such as unused
  • the target core network instance proceeds with servicing the UE, albeit without the benefit of context information from other core network instances.
  • PDN packet data network gateway
  • the apparatus 30 is unable to obtain and utilize context information relating to the context of the UE 18 and its service from the source core network instance 10, such as the source control node 14.
  • the UE does not provide, during the attachment process, a third global identifier of the UE, such as the third GUTI that comprises a globally unique identifier of the different control node and the local identifier field with a second locally unique user equipment identifier.
  • the apparatus includes means, such as the processor 32 or the like, configured to, cause a detach request to be sent toward the UE.
  • the detach request includes a detach type value which, in turn, is set to a re-attach value.
  • the globally unique identifiers of the mobility control node and the different control node, that is, the source control node are different globally unique MME identifiers
  • GUMMEIs MME temporary mobile subscriber identities
  • M-TMSIs MME temporary mobile subscriber identities
  • the mobility control node may be an access and mobility management function (AMF).
  • AMF access and mobility management function
  • the globally unique identifers of the mobility control node and the different control node are different globally unique AMF identifiers (GUAMIs) and the first and second locally unique user equipment identifiers comprise different fifth generation temporary mobile subscriber identities (5G-TMSIs).
  • GUIAMIs globally unique AMF identifiers
  • 5G-TMSIs fifth generation temporary mobile subscriber identities
  • the UE may be redirected in a manner that is transparent to the radio access network (RAN) 20.
  • the UE may be redirected without provisioning any subscription information in the HSS or the 5G unified data management function (UDF) that is requied to be interpreted by the RAN to select the appropriate control node.
  • the method, apparatus 30 and computer program product of an example may be readily adopted since the performance of the radio access network need not be modified.
  • the target control node 16 need not reserve a plurality of M-TMSI or 5G-TMSI values to be utilized during redirection of the UE as required by other redirection techniques and, instead, utilizes a local identifier field having a predefined flag value to signal the redirection and then a single M-TMSI or 5G-TMSI value that uniquely identifies the UE to the target control node.
  • the redirection of the UE 18 may be performed in other manners. As shown in the flow chart of Figure 5 and the signal flow diagram of Figure 6, for example, the UE may issue an attach or TAU request to a source core network instance 10, such as a source control node 14, as shown in signal flow 70 of Figure 6.
  • a source core network instance 10 such as a source control node 14, as shown in signal flow 70 of Figure 6.
  • the source core network instance is configured to direct a reject message, such as a non-access stratum (NAS) reject message as shown in signal flow 72, e.g., an attach reject message or a TAU reject message, to the UE indicating that the UE is being redirected so as to be serviced by a different core network instance, such as the target core network instance 12.
  • NAS non-access stratum
  • the reject message includes the target tracking area identifier (TAI).
  • TAI target tracking area identifier
  • the UE therefore receives the NAS reject message, such as an attach reject message or a TAU reject message, that includes the target TAI and that indicates to the UE that the UE is being redirected. See block 60 of Figure 5.
  • TAI target tracking area identifier
  • the UE Utilizing the target TAI and as shown in signal flow 74 of Figure 6, the UE then creates a NAS request message, such as an attach request message or a TAU message, that includes the target TAI. See block 62.
  • the UE then causes the NAS request message to be sent toward a mobility control node of a core network, such as the target control node 16 of the target core network instance 12, as identified by the target TAI in order to attach to the target control node and to be serviced thereby. See block 64.
  • the NAS request message provides for cell re-selection to the target control node of the target core network instance that is within the same PLMN as the source core network instance and its soruce control node.
  • the UE 18 is redirected to a different core network instance utilizing a target TAI
  • the UE is impacted, but the redirection is performed in a manner that is transparent to the radio access network 20.
  • the UE may be redirected without provisioning any subscription information in the HSS.
  • the use of the target TAI avoids the target control node 16 needing to reserve a plurality of M-TMSI values to be utilized during redirection of the UE as required by other redirection techniques.
  • Figure 3 is a flowchart of an apparatus 30, method, and computer program product according to example embodiments of the invention. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device 34 of an apparatus employing an
  • any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks.
  • These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture, the execution of which implements the function specified in the flowchart blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.
  • a computer program product is therefore defined in those instances in which the computer program instructions, such as computer-readable program code portions, are stored by at least one non-transitory computer-readable storage medium with the computer program instructions, such as the computer-readable program code portions, being configured, upon execution, to perform the functions described above, such as in conjunction with the flowchart of Figure 3.
  • the computer program instructions, such as the computer- readable program code portions need not be stored or otherwise embodied by a non-transitory computer-readable storage medium, but may, instead, be embodied by a transitory medium with the computer program instructions, such as the computer-readable program code portions, still being configured, upon execution, to perform the functions described above.
  • blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.
  • certain ones of the operations above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations may be included. Modifications, additions, or amplifications to the operations above may be performed in any order and in any combination.

Landscapes

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

Abstract

Procédé, appareil et produit de type programme informatique redirigeant un équipement utilisateur (UE) d'une manière qui est transparente pour le réseau d'accès radio et l'UE. Un premier identifiant global de l'UE est reçu pendant un processus de rattachement à un nœud de commande de mobilité. Le premier identifiant global comprend un identifiant universel unique du nœud de commande de mobilité et un champ d'identifiant local pour l'UE au sein du nœud de commande de mobilité. Si le champ d'identifiant local présente une valeur d'indication prédéfinie, il est déterminé que l'UE a été redirigé depuis un nœud de commande différent. Si l'UE a été redirigé depuis le nœud de commande différent, une instruction de réattribution est transmise à l'UE. La commande de réattribution comprend un second identifiant universel de l'UE comprenant l'identifiant universel unique du nœud de commande de mobilité et le champ d'identifiant local ayant un premier identifiant d'UE localement unique.
PCT/GR2018/000018 2018-03-01 2018-03-30 Procédé et appareil pour rediriger un équipement utilisateur vers un autre nœud de commande de mobilité WO2019166837A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR2018000011 2018-03-01
GRPCT/GR2018/000011 2018-03-01

Publications (1)

Publication Number Publication Date
WO2019166837A1 true WO2019166837A1 (fr) 2019-09-06

Family

ID=67805252

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GR2018/000018 WO2019166837A1 (fr) 2018-03-01 2018-03-30 Procédé et appareil pour rediriger un équipement utilisateur vers un autre nœud de commande de mobilité

Country Status (1)

Country Link
WO (1) WO2019166837A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4132138A1 (fr) * 2021-08-05 2023-02-08 Vodafone Group Services Limited Traitement de demandes d'inscription dans un réseau cellulaire
WO2023238743A1 (fr) * 2022-06-09 2023-12-14 日本電気株式会社 Noeud de réseau central, noeud de réseau d'accès, terminal sans fil, procédé de communication et support lisible par ordinateur

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030040313A1 (en) * 2001-08-21 2003-02-27 Hogan William Damian Method and apparatus for location area updating in cellular communications
US20110111771A1 (en) * 2009-11-06 2011-05-12 Futurewei Technologies, Inc. Method and System for Location Update in Mobile Network
US20140133464A1 (en) * 2006-08-15 2014-05-15 Huawei Technologies Co., Ltd. Method and system for transferring user equipment in mobile communication system
US20160066219A1 (en) * 2013-04-16 2016-03-03 Nokia Solutions And Networks Oy Mobility management entity (mme) triggered detach and re-attach to a specific target mme

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030040313A1 (en) * 2001-08-21 2003-02-27 Hogan William Damian Method and apparatus for location area updating in cellular communications
US20140133464A1 (en) * 2006-08-15 2014-05-15 Huawei Technologies Co., Ltd. Method and system for transferring user equipment in mobile communication system
US20110111771A1 (en) * 2009-11-06 2011-05-12 Futurewei Technologies, Inc. Method and System for Location Update in Mobile Network
US20160066219A1 (en) * 2013-04-16 2016-03-03 Nokia Solutions And Networks Oy Mobility management entity (mme) triggered detach and re-attach to a specific target mme

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.401, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V15.2.0, 22 December 2017 (2017-12-22), pages 1 - 404, XP051392097 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4132138A1 (fr) * 2021-08-05 2023-02-08 Vodafone Group Services Limited Traitement de demandes d'inscription dans un réseau cellulaire
GB2609487B (en) * 2021-08-05 2023-11-22 Vodafone Group Services Ltd Registration request handling in a cellular network
WO2023238743A1 (fr) * 2022-06-09 2023-12-14 日本電気株式会社 Noeud de réseau central, noeud de réseau d'accès, terminal sans fil, procédé de communication et support lisible par ordinateur

Similar Documents

Publication Publication Date Title
US11611912B2 (en) Cell reselection method and related device
US10791431B2 (en) Methods and apparatus for establishing a group session in a mobile network for subscribers associated with a group
EP3528466B1 (fr) Procédé d'envoi d'informations, unité, et système
TWI831454B (zh) 網路系統中的網路切片選擇之技術
CN111279731B (zh) 过载情况下对5g amf节点的改变
EP3621352B1 (fr) Procédé et dispositif de traitement de session d'unité pdu
CN109548175B (zh) 一种会话处理方法及装置
US10715404B2 (en) Slice changing method and slice changing device
US20190191367A1 (en) Network slice selection method and apparatus
WO2018134483A1 (fr) Procédé et appareil pour un déploiement de tranche de réseau complémentaire et équivalente dans un environnement de réseau
WO2019007345A1 (fr) Procédé, appareil et système de sélection de tranche de réseau, et support d'informations
KR20180134685A (ko) 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
ES2956842T3 (es) Selección de una red central dedicada basada en un tipo de servicio
US11363102B2 (en) Communication method and apparatus for network accessible only in specific area
EP3413537B1 (fr) Procédé de transmission d'informations et appareil d'accès à un réseau central
KR102639093B1 (ko) 무선 시스템들을 위한 액세스 제어 방법들 및 장치
CN109155994B (zh) 一种用户面资源管理方法、用户面网元及控制面网元
WO2017075757A1 (fr) Procédé, dispositif et système permettant de sélectionner un service de fonction de réseau
US20200022076A1 (en) Network Element Selection Method and Apparatus
WO2017161484A1 (fr) Procédé, dispositif et système d'interaction de message
US20210345066A1 (en) Information transmission method and apparatus
EP3687259B1 (fr) Procédé et dispositif de communication
CN109196889B (zh) 用户信息获取方法、标识对应关系保存方法及装置与设备
EP3955600B1 (fr) Procédé de traitement de sms dans l'internet des objets, élément de réseau de gestion de la mobilité et dispositif terminal
WO2019166837A1 (fr) Procédé et appareil pour rediriger un équipement utilisateur vers un autre nœud de commande de mobilité

Legal Events

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

Ref document number: 18722714

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18722714

Country of ref document: EP

Kind code of ref document: A1