CN114946231A - Techniques to manage access and mobility management function (AMF) relocation - Google Patents

Techniques to manage access and mobility management function (AMF) relocation Download PDF

Info

Publication number
CN114946231A
CN114946231A CN202080093124.2A CN202080093124A CN114946231A CN 114946231 A CN114946231 A CN 114946231A CN 202080093124 A CN202080093124 A CN 202080093124A CN 114946231 A CN114946231 A CN 114946231A
Authority
CN
China
Prior art keywords
message
network element
core network
amf
node
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.)
Pending
Application number
CN202080093124.2A
Other languages
Chinese (zh)
Inventor
卢飞
游世林
朱进国
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of CN114946231A publication Critical patent/CN114946231A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Landscapes

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

Abstract

Techniques to manage access and mobility management function (AMF) relocation are described. Example techniques include: receiving, by a network node, a first message indicating completion of a Radio Resource Control (RRC) connection establishment, wherein the first message is received in response to a first registration rejection by a first core network element of a communication node; and after receiving the first message, sending a second message to the second core network element that the communication node requests a second registration from the second core network element, wherein the first message and the second message comprise an identifier of the second core network element.

Description

Techniques to manage access and mobility management function (AMF) relocation
Technical Field
The present disclosure relates generally to digital wireless communications.
Background
Mobile telecommunications technology is driving the world towards increasingly interconnected and networked societies. Next generation systems and wireless communication technologies will need to support a wider range of use case characteristics and provide a more complex and sophisticated range of access requirements and flexibility than existing wireless networks.
Long Term Evolution (LTE) is a standard developed by the third generation partnership project (3GPP) for wireless communication of mobile devices and data terminals. LTE-Advanced (LTE-a) is a wireless communication standard that enhances the LTE standard. The fifth generation wireless system, referred to as 5G, improves the LTE and LTE-a wireless standards and addresses the need to support higher data rates, large numbers of connections, ultra-low latency, high reliability, and other emerging services.
Disclosure of Invention
Techniques for managing relocation of Access and Mobility Management functions (AMFs) are disclosed.
In a first example embodiment, a method of wireless communication includes: receiving, by a network node, a first message indicating Radio Resource Control (RRC) connection setup complete, wherein the first message is received in response to a first core network element rejecting a first registration of a communication node; and after receiving the first message, sending a second message to a second core network element that the communication node requests a second registration from the second core network element, wherein the first message and the second message comprise an identifier of the second core network element.
In a second example embodiment, a method of wireless communication includes: the communication node receiving a first message indicating that the first core network element rejects the first registration of the communication node; and after receiving the first message, transmitting a second message indicating Radio Resource Control (RRC) connection setup complete to the network node, wherein the first message and the second message comprise an identifier of the second core network element, and wherein transmitting the second message triggers a second registration of the communication node with the second core network element.
In a third example embodiment, a wireless communication method includes: the network node receiving a first message from the communication node indicating a Radio Resource Control (RRC) connection setup complete; and after receiving the first message, sending a second message to the first core network element that the correspondent node requests registration from the first core network element, wherein the first message and the second message include an identifier of the first core network element.
In a fourth example embodiment, a wireless communication method includes: the communication node receiving a first message indicating a Radio Resource Control (RRC) release from the network node; and after receiving the first message, sending a second message to the network node indicating that RRC connection establishment is complete, wherein the first message and the second message include an identifier of the first core network element, and wherein sending the second message triggers registration of the communication node with the first core network element.
In yet another exemplary aspect, the above-described method is embodied in the form of processor executable code and stored in a non-transitory computer readable storage medium. The code included in the computer readable storage medium, when executed by a processor, causes the processor to implement the methods described in this patent document.
In yet another exemplary embodiment, an apparatus configured or operable to perform the above method is disclosed.
The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, the description and the claims.
Drawings
Fig. 1 shows the structure of a 5G mobile communication system.
Fig. 2 illustrates a conventional technique for performing a registration procedure with access and mobility management function (AMF) relocation in 5 GS.
Fig. 3 illustrates an example flow diagram of an initial AMF sending a registration reject message including information about a target AMF to a User Equipment (UE).
Fig. 4 shows an example flow diagram of a NG-RAN node sending a Radio Resource Control (RRC) release message to a UE including information about a target AMF.
Fig. 5A illustrates a first exemplary flow chart for a network node facilitating AMF relocation.
Fig. 5B illustrates a first exemplary flow chart of a communications node facilitating AMF relocation.
Fig. 6A illustrates a second exemplary flow chart for a network node facilitating AMF relocation.
Fig. 6B illustrates a second exemplary flow chart for a correspondent node facilitating AMF relocation.
Fig. 7 shows an exemplary block diagram of a hardware platform that may be part of a network node or a communication node.
Detailed Description
This patent document describes techniques for performing access and mobility management function (AMF) relocation. An overview of the 5G system architecture is described first, followed by a discussion of technical issues associated with conventional techniques for performing registration procedures with AMFs. Next, this patent document describes at least two example embodiments in which AMF relocation may be performed and at least some of the technical problems associated with conventional techniques may be overcome.
The exemplary headings for the following sections are intended to facilitate an understanding of the disclosed subject matter and are not intended to limit the scope of the claimed subject matter in any way. Thus, one or more features of one exemplary section may be combined with one or more features of another exemplary section. Also, for clarity of explanation, 5G terminology is used, but the technology disclosed in this document is not limited to 5G technology and may be used in wireless systems implementing other protocols.
Overview of the I.5GS architecture
Fig. 1 shows an architecture of a 5G mobile communication system. A User Equipment (UE) is connected to a 5G network.
The architecture shown in fig. 1 includes the following means and/or related functions:
UE-user equipment.
5G RAN (or NG RAN) -5G radio Access network or base station.
Access and mobility management function (AMF) -AMF may include at least the following functions: registration management, connection management, reachability management, and mobility management. The function also performs access authentication and access authorization. The AMF is a non-access stratum (NAS) security termination, and relays an SM (Session management) NAS and the like between the UE and the SMF.
Session Management Function (SMF) -SMF may include at least the following functions: session management (e.g., session establishment, modification, and release), UE IP address assignment and management (including optional grants), selection and control of UP functions, downlink data notification, and the like.
User Plane Function (UPF) -UPF may include at least the following functions: anchor point for intra-Radio Access Technology (RAT) mobility/inter-Radio Access Technology mobility, packet routing and forwarding, traffic usage reporting, QoS (quality of service) handling of the user plane, downlink packet buffering, and downlink data notification triggering, etc.
Unified Data Management (UDM) -UDM may include at least the following functions: authentication credentials for generating Authentication and Key Agreement (AKA) of 3GPP, user identification processing (e.g., storage and management of subscription permanent identifiers (SUPI) for each user in a 5G system), subscription management, and the like.
Authentication Server Function (AUSF) -AUSF may include at least the following functions: authentication of 3GPP access is supported.
Conventional techniques for performing AMF relocation registration procedure
Fig. 2 shows a conventional technique for performing a registration procedure with AMF relocation in 5 GS. The set of operations indicated in fig. 2 are associated with numbers further explained below using the same numbering scheme:
the UE sends a registration request message to the NG-RAN, the registration request message including a clear text information element (e.g., registration type, SUbscription hidden Identifier (SUCI) of the UE, or 5G Globally Unique Temporary Identifier (5G-global Unique Identifier,5G-GUTI) of the UE), security parameters).
NG-RAN forwards a Registration Request (RR) message to the initial AMF.
3. The initial AMF performs an authentication process to generate a partial native 5G security context.
4. The AMF integrity protects the secure mode command message initially, and then sends the secure mode command message to employ the partial native 5G security context. In the security mode command message, it contains the next generation key set identifier (ngKSI), the key (Kamf), and the retransmission of the indicia needed for the RR message.
And 5, the UE sends a safety mode completion message to the AMF. This message will include the entire registration request message. The entire registration request will contain the plaintext IE and the non-plaintext IE. non-plaintext IE as in step 1 including the requested Network Slice Selection Assistance Information (NSSAI) and the UE Network capabilities.
6. The initial AMF sends an NSSF _ NSSelect _ Get message to a Network Slice Selection Function (NSSF). The nssf _ NSSelect _ Get message includes the requested NSSAI, a Tracking Area Identifier (TAI), and a public land mobile network Identifier (PLMN ID) of a SUbscription Permanent Identifier (SUPI).
NSSF sends a response to NSSF _ NSSelection _ Get to the initial AMF, which includes the AMF set and the allowed NSSAI.
8. If the initial AMF decides to forward the NAS message to the target AMF via the (R) AN based on the local policy and subscription information, the initial AMF sends a rerouted NAS message to the (R) AN. The reroute NAS message includes information about the target AMF and the registration request message.
The RAN selects a target AMF based on the reroute NAS message and sends an initial UE message to the target AMF.
10. Since the target AMF does not have the UE context, the target AMF determines to perform the authentication procedure, and the AMF transmits a Nausf _ UE authentication _ authentication request message to the AUSF. The message will include SUPI.
The AUSF will return a Nausf UEAuthentication authentication response message. The message will include an authentication key or token (AUTN) and an authentication sequence number (SQN).
12. The target AMF sends an unprotected authentication request message to the UE and starts a timer to monitor for an authentication response message.
13. Since a secure connection has been established between the UE and the initial AMF, the UE will discard the unprotected authentication request message.
14. Upon expiration of the timer started in step 12, the AMF will send a registration reject message to the UE.
The conventional flow chart shown in fig. 2 has at least the following technical problems. If the initial AMF and the UE have established a secure connection and AMF relocation via the RAN has been performed, when the target AMF sends an unprotected authentication request message to the UE, the UE will discard the unprotected authentication request message because the UE is in a secure connection with the initial AMF. In this case, the UE will not respond to the target AMF, and the target AMF will reject the registration procedure when the timer expires, so that the UE may not be able to obtain service from the NG-RAN node.
Exemplary embodiment #1
In a first example embodiment, the initial AMF sends a registration reject message including information on the target AMF to the UE. The UE sends target AMF information to the NG-RAN for target AMF selection. And, the target AMF performs an authentication procedure.
Fig. 3 illustrates an example flow diagram of an initial AMF sending a registration reject message to a UE including information about a target AMF. The registration reject message indicates that the initial AMF rejects registration of the UE with the initial AMF. The set of operations indicated in fig. 3 are associated with the following numbering further explained using the same numbering scheme:
the UE sends a registration request message to the NG-RAN, the registration request message including a plaintext IE (e.g., registration type, SUCI or 5G-GUTI, security parameters). The registration request message enables the UE to register with the AMF.
The NG-RAN forwards the registration request message to the initial AMF.
3. The initial AMF performs an authentication process to generate a partial native 5G security context.
4. The AMF integrity protects the secure mode command message initially and then sends the secure mode command message to use the partial native 5G security context. The security mode command message contains the retransmission of the flags required for ngKSI, Kamf and RR messages.
And 5, the UE sends a safety mode completion message to the AMF. The entire registration request message will be included in the message. The entire registration request will contain a plaintext IE and a non-plaintext IE as in step 1. The non-clear IE includes the requested NSSAI and UE network capabilities.
6. The initial AMF sends an NSSF _ NSSelect _ Get message to the NSSF. The nssf _ NSSelect _ Get message includes the PLMN ID of the requested NSSAI, TAI and SUPI.
NSSF sends a response to NSSF _ NSSelection _ Get to the initial AMF, which includes the AMF set and allowed NSSAI.
8. If the initial AMF decides to forward the NAS message to the target AMF based on the local policy and subscription information, the initial AMF sends a registration reject message to the UE. The registration reject message includes information about the target AMF, wherein the target AMF information may include a Globally Unique AMF Identifier (GUAMI) of the target AMF. After receiving the registration reject message, the UE will release the existing NAS signaling connection. The secure connection between the UE and the initial AMF is terminated.
The UE sends RRC setup complete (msg5) to the NG-RAN. The registration request message may also be carried therein as a NAS Protocol Data Unit (PDU) in msg 5. Accordingly, the RRC setup complete message may include a registration request message. msg5 may also include the GUAMI of the target AMF.
The NG-RAN forwards the registration request message to the target AMF as part of the initial UE message.
11. Since the target AMF does not have the UE context, the target AMF determines to perform the authentication procedure, and the target AMF transmits a Nausf _ UE authentication _ authentication request message to the AUSF. The message will include SUPI.
The AUSF returns a Nausf UEAuthentication authentication response message to the target AMF. The message will include AUTN and SQN.
13. The target AMF sends an unprotected authentication request message to the UE and starts a timer to monitor for an authentication response message.
14. At least because the UE did not have a secure connection setup with the initial AMF when it received the registration reject message from the initial AMF (at step 8), the UE will send an authentication response message to the target AMF. The authentication response message may comprise an authentication code RES (or an authentication code result value).
15. The target AMF will send a registration accept message to the UE. The 5G-GUTI of the UE may be included in the registration accept message.
The UE will send a registration complete message to the target AMF to acknowledge the reception of the 5G-GUTI.
Exemplary embodiment #2
In a second example embodiment, the NG-RAN node sends a Radio Resource Control (RRC) release message to the UE including information about the target AMF. The UE sends target AMF information to the NG-RAN for target AMF selection. And, the target AMF performs an authentication procedure.
Fig. 4 shows an example flow diagram of a NG-RAN node sending an RRC release message to a UE, the RRC release message including information about a target AMF. The set of operations indicated in FIG. 4 are associated with the following numbering further explained using the same numbering scheme:
the UE sends a registration request message to the NG-RAN. The registration request message includes a plaintext IE (e.g., registration type, SUCI or 5G-GUTI, security parameters). The registration request message enables the UE to register with the AMF.
The NG-RAN forwards the registration request message to the initial AMF.
3. The initial AMF performs an authentication process to generate a partial native 5G security context.
4. The AMF integrity protects the secure mode command message initially and then sends the secure mode command message to use the partial native 5G security context. The security mode command message contains the retransmission of the flags required for ngKSI, Kamf and RR messages.
And 5, the UE sends a safety mode completion message to the AMF. The entire registration request message will be included in the message. The entire registration request will contain a plaintext IE and a non-plaintext IE as in step 1. The non-clear IE includes the requested NSSAI and UE network capabilities.
6. The initial AMF sends an NSSF _ NSSelect _ Get message to the NSSF, which includes the PLMN IDs of the requested NSSAI, TAI, and SUPI.
NSSF sends a response to NSSF _ NSSelection _ Get to the initial AMF, which includes the AMF set and allowed NSSAI.
8. If the initial AMF decides to forward the NAS message to the target AMF via the (R) AN based on the local policy and subscription information, the initial AMF sends a rerouted NAS message to the (R) AN. The re-routing NAS message enables the NG-RAN node to generate and/or send a registration request message as described in step 10. The reroute NAS message includes information about the target AMF (e.g., the GUAMI of the target AMF, which is shown as "target GUAMI" in fig. 4) and the registration request message.
The RAN performs the RRC release procedure. The RAN sends an RRC release message to the UE, where the RRC release message may include the GUAMI of the target AMF. After receiving the RRC release message, the UE will release the RRC connection and release the existing NAS signaling connection. The secure connection between the UE and the initial AMF is terminated
The UE sends RRC setup complete (msg5) to the NG-RAN. The registration request message may also be carried therein as a NAS PDU in msg 5. Accordingly, the RRC setup complete message may include a registration request message. msg5 may also include the GUAMI of the target AMF.
The NG-RAN forwards the registration request message to the target AMF as part of the initial UE message.
12. Since the target AMF does not have the UE context, the target AMF determines to perform the authentication procedure, and the target AMF transmits a Nausf _ UE authentication _ authentication request message to the AUSF. The message will include SUPI.
The AUSF will return a Nausf UEAuthentication authentication response message. The message will include AUTN and SQN.
14. The target AMF sends an unprotected authentication request message to the UE and starts a timer to monitor for an authentication response message.
15. At least because the UE does not have a secure connection setup with the initial AMF when it receives the RRC release message from the initial AMF (at step 9), the UE will send an authentication response message to the target AMF. The authentication response message may comprise an authentication code RES.
The AMF will send a registration accept message to the UE. The 5G-GUTI of the UE may be included in the registration accept message.
The UE will send a registration complete message to the AMF to acknowledge the reception of the 5G-GUTI.
Fig. 5A illustrates a first exemplary flow diagram for a network node that facilitates AMF relocation. In operation 502, the network node receives a first message indicating Radio Resource Control (RRC) connection setup complete (e.g., an RRC setup complete message), wherein the first message is received in response to a rejection of the first registration of the communication node by the first core network element. The rejection of the first registration may indicate a termination of the connection between the first core network element and the correspondent node. At operation 504, the network node sends, to the second core network element, a second message (e.g., a registration request message) that the communication node requests a second registration from the second core network element after receiving the first message, wherein the first message and the second message include an identifier of the second core network element.
In some embodiments, the identifier of the second core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the second core network element. In some embodiments, the first message comprises the second message in a non-access stratum (NAS) Protocol Data Unit (PDU). In some embodiments, sending the second message comprises sending an initial User Equipment (UE) message with the second message. In some embodiments, the network node comprises a base station, the communication node comprises a User Equipment (UE), the first core network element comprises a first access and mobility management function (AMF), and the second core network element comprises a second AMF. In some embodiments, the authentication process is triggered by the second core network element after sending the second message.
Fig. 5B illustrates a first exemplary flow chart for a correspondent node facilitating AMF relocation. At operation 522, the correspondent node receives a first message (e.g., a registration reject message) indicating that the first core network element rejects the correspondent node's first registration. The rejection of the first registration may indicate a termination of a connection between the first core network element and the correspondent node. At operation 524, the communication node, after receiving the first message, sends a second message (e.g., an RRC setup complete message) to the network node, the second message indicating Radio Resource Control (RRC) connection setup complete, wherein the first message and the second message include an identifier of the second core network element, and wherein sending the second message triggers a second registration of the communication node with the second core network element.
In some embodiments, the identifier of the second core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the second core network element. In some embodiments, the network node comprises a base station, the communication node comprises a User Equipment (UE), the first core network element comprises a first access and mobility management function (AMF), and the second core network element comprises a second AMF.
Fig. 6A illustrates a second exemplary flow chart for a network node facilitating AMF relocation. At operation 602, the network node receives a first message (e.g., an RRC setup complete message) from the communication node indicating that a Radio Resource Control (RRC) connection setup is complete. At operation 604, the network node, upon receiving the first message, sends a second message (e.g., a registration request message) to the first core network element, the second message requesting the correspondent node to register with the first core network element, wherein the first message and the second message include an identifier of the first core network element.
In some embodiments, the identifier of the first core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the first core network element. In some embodiments, the first message comprises a second message in a non-access stratum (NAS) Protocol Data Unit (PDU). In some embodiments, sending the second message comprises sending an initial User Equipment (UE) message with the second message. In some embodiments, the first message is received in response to the network node sending a third message (e.g., an RRC release message) to the communication node indicating an RRC release, and wherein the third message includes an identifier of the first core network element.
In some embodiments, the third message is sent in response to the network node receiving a non-access stratum (NAS) reroute request message from the second core network element that facilitates generation or sending of the second message, and the NAS reroute request message includes an identifier of the first core network element. In some embodiments, the network node comprises a base station, the communication node comprises a User Equipment (UE), the first core network element comprises a first access and mobility management function (AMF), and the second core network element comprises a second AMF.
Fig. 6B illustrates a second exemplary flow chart for a communication node facilitating AMF relocation. At operation 622, the communication node receives a first message (e.g., an RRC release message) from the network node indicating a release of Radio Resource Control (RRC). At operation 624, the communication node, after receiving the first message, sends a second message (e.g., an RRC setup complete message) to the network node indicating completion of the RRC connection setup, wherein the first message and the second message include an identifier of the first core network element, and wherein sending the second message triggers the communication node to register with the first core network element.
In some embodiments, the identifier of the first core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the first core network element. In some embodiments, the first message is received in response to sending a non-access stratum (NAS) reroute request message by the second core network element, and the NAS reroute request message includes an identifier of the first core network element. In some embodiments, the network node comprises a base station, the communication node comprises a User Equipment (UE), the first core network element comprises a first access and mobility management function (AMF), and the second core network element comprises a second AMF.
Fig. 7 illustrates an exemplary block diagram of a hardware platform 700, which may be part of a network node (e.g., a base station or RAN node) or a communication node (e.g., a UE). Hardware platform 700 includes at least one processor 710 and memory 705 having instructions stored thereon. The instructions, when executed by the processor 710, configure the hardware platform 700 to perform the operations described in the various embodiments described in fig. 3-6B and in this patent document. The transmitter 715 sends or transmits information or data to another node. For example, the network node transmitter may send a message to the communication node. The receiver 720 receives information or data sent or transmitted by another node. For example, the communication node may receive a message from a network node.
The term "exemplary" is used herein to mean an "… … example," and does not imply an ideal or preferred embodiment unless otherwise stated.
Some embodiments described herein are described in the general context of methods or processes, which may be implemented in one embodiment by a computer program product, embodied in a computer-readable medium, including computer-executable instructions (such as program code) executed by computers in networked environments. The computer readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), Compact Discs (CDs), Digital Versatile Discs (DVDs), and the like. Thus, a computer-readable medium may include a non-transitory storage medium. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-or processor-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.
Some disclosed embodiments may be implemented as a device or module using hardware circuitry, software, or a combination thereof. For example, a hardware circuit implementation may include discrete analog and/or digital components (e.g., integrated as part of a printed circuit board). Alternatively or additionally, the disclosed components or modules may be implemented as Application Specific Integrated Circuits (ASICs) and/or Field Programmable Gate Array (FPGA) devices. Some implementations may additionally or alternatively include a Digital Signal Processor (DSP), which is a special-purpose microprocessor, having an architecture optimized for the operational needs of the digital signal processing associated with the functions disclosed herein. Similarly, the various components or sub-components within each module may be implemented in software, hardware, or firmware. Connectivity between modules and/or components within modules may be provided using any of the connectivity methods and media known in the art, including but not limited to communication over the internet, wired or wireless networks using appropriate protocols.
Although this document contains many specifics, these should not be construed as limitations on the scope of the claimed invention or of what may be claimed, but rather as descriptions of features of particular embodiments. Certain features that are described herein in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination. Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results.
Only a few embodiments and examples are described and other embodiments, enhancements and variations can be made based on what is described and illustrated in this disclosure.

Claims (22)

1.A method of wireless communication, comprising:
receiving, by a network node, a first message indicating completion of a Radio Resource Control (RRC) connection setup,
wherein the first message is received in response to the first core network element rejecting the first registration of the correspondent node; and
after receiving the first message, sending a second message to a second core network element that the communication node requests a second registration from the second core network element,
wherein the first message and the second message comprise an identifier of the second core network element.
2. The method of claim 1, wherein the identifier of the second core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the second core network element.
3. The method of claim 1, wherein the first message comprises a second message in a non-access stratum (NAS) Protocol Data Unit (PDU).
4. The method of claim 1, wherein sending the second message comprises sending an initial User Equipment (UE) message with the second message.
5. The method of claim 1, wherein the network node comprises a base station, wherein the communication node comprises a User Equipment (UE), wherein the first core network element comprises a first access and mobility management function (AMF), and wherein the second core network element comprises a second AMF.
6. The method according to claim 1, characterized in that after sending the second message, an authentication procedure is triggered by the second core network element.
7. A method of wireless communication, comprising:
receiving, by a communication node, a first message indicating that a first core network element rejects a first registration of the communication node; and
transmitting, after receiving the first message, a second message indicating Radio Resource Control (RRC) connection setup completion to a network node,
wherein the first message and the second message comprise an identifier of a second core network element, an
Wherein sending the second message triggers a second registration of the communication node with the second core network element.
8. The method of claim 1, wherein the identifier of the second core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the second core network element.
9. The method of claim 7, wherein the network node comprises a base station, wherein the communication node comprises a User Equipment (UE), wherein the first core network element comprises a first access and mobility management function (AMF), and wherein the second core network element comprises a second AMF.
10. A method of wireless communication, comprising:
the network node receiving a first message from the communication node indicating a Radio Resource Control (RRC) connection setup complete; and
after receiving the second message, sending a second message to a first core network element that the communication node requests registration from the first core network element,
wherein the first message and the second message comprise an identifier of the first core network element.
11. The method of claim 10, wherein the identifier of the first core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the first core network element.
12. The method of claim 10, wherein the first message comprises a second message in a non-access stratum (NAS) Protocol Data Unit (PDU).
13. The method of claim 10, wherein sending the second message comprises sending an initial User Equipment (UE) message with the second message.
14. The method of claim 10,
receiving the first message in response to the network node sending a third message to the communication node indicating an RRC release, an
The third message includes an identifier of the first core network element.
15. The method of claim 14,
sending the third message in response to the network node receiving a non-access stratum (NAS) reroute request message from a second core network element that facilitates generation of the second message, an
The NAS reroute request message includes an identifier of the first core network element.
16. The method of claim 15, wherein the network node comprises a base station, wherein the communication node comprises a User Equipment (UE), wherein the first core network element comprises a first access and mobility management function (AMF), and wherein the second core network element comprises a second AMF.
17. A method of wireless communication, comprising:
the communication node receiving a first message indicating a release of Radio Resource Control (RRC) from the network node; and
after receiving the first message, sending a second message to the network node indicating that RRC connection establishment is complete,
wherein the first message and the second message comprise an identifier of a first core network element, an
Wherein sending the second message triggers registration of the communication node with the first core network element.
18. The method of claim 17, wherein the identifier of the first core network element comprises a globally unique access and mobility management function (AMF) identification (GUAMI) of the first core network element.
19. The method of claim 17,
receiving a non-access stratum (NAS) rerouting request message sent by a second core network element, and
the NAS reroute request message includes an identifier of the first core network element.
20. The method of claim 19, wherein the network node comprises a base station, wherein the communication node comprises a User Equipment (UE), wherein the first core network element comprises a first access and mobility management function (AMF), and wherein the second core network element comprises a second AMF.
21. An apparatus for wireless communication, comprising a processor configured to implement the method of one or more of claims 1-20.
22. A computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to implement a method according to one or more of claims 1 to 20.
CN202080093124.2A 2020-01-22 2020-01-22 Techniques to manage access and mobility management function (AMF) relocation Pending CN114946231A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/073816 WO2021093182A1 (en) 2020-01-22 2020-01-22 Techniques to manage access and mobility management function (amf) relocation

Publications (1)

Publication Number Publication Date
CN114946231A true CN114946231A (en) 2022-08-26

Family

ID=75911743

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080093124.2A Pending CN114946231A (en) 2020-01-22 2020-01-22 Techniques to manage access and mobility management function (AMF) relocation

Country Status (2)

Country Link
CN (1) CN114946231A (en)
WO (1) WO2021093182A1 (en)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108924926B (en) * 2017-03-29 2022-02-25 华为技术有限公司 Communication method and communication device
EP3972347A1 (en) * 2017-12-08 2022-03-23 Comcast Cable Communications LLC User plane function selection for isolated network slice
CN109936861B (en) * 2017-12-18 2021-08-03 华为技术有限公司 Communication method, access network equipment, terminal equipment and core network equipment
US10506543B1 (en) * 2018-06-25 2019-12-10 Qualcomm Incorporated Low power periodic and triggered location of a mobile device using early data transmission

Also Published As

Publication number Publication date
WO2021093182A1 (en) 2021-05-20

Similar Documents

Publication Publication Date Title
US10945177B2 (en) Method and apparatus for session release in wireless communication
US9843910B2 (en) Method and system for reporting a short message capability via an IP multimedia subsystem
CN113661696B (en) System and method for handling scalable FQDN
WO2019091489A1 (en) Improvement for initial ims registration
US10757645B2 (en) Access control in communications network comprising slices
EP2991440B1 (en) Method and device for connecting to network
CN112369077B (en) UE behavior for emergency services attachment device
US9877346B2 (en) Method and nodes for handling ESM information
JP7156486B2 (en) Method and user equipment
CN114051745A (en) System and method for dual SIM UE operation in 5G networks
CN111480353A (en) Method and apparatus for establishing a signaling connection between a remote User Equipment (UE) and a telecommunications network via a relay-capable UE
US11877351B2 (en) Provision GPSI pertaining to PDU session(s)
JP2022501864A (en) Security key generation technology
WO2020229409A1 (en) Smf set support over n4 interface
CN114501683A (en) Call processing method, device and storage medium
CN107438290B (en) Connection establishment method for small data transmission, SCEF entity and MME
US8817778B2 (en) Session processing method, device, and communication system
WO2016174512A1 (en) Resource control for wireless device detach
US20160249249A1 (en) Method and apparatus for obtaining authentication information
CN111615848A (en) Method for controlling access to network in wireless communication system and apparatus therefor
CN112584332A (en) Short message transmission method, device and system, and registration method and device
WO2021093182A1 (en) Techniques to manage access and mobility management function (amf) relocation
CN105578539A (en) Optimal switching method supporting multiple PDN connections and corresponding network node
JP2014027550A (en) Mobile communication system, mobile station, network device, and mobile communication method
CN117204039A (en) Network relay security

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination