[go: up one dir, main page]

WO2024216823A1 - Systèmes et procédés de transfert - Google Patents

Systèmes et procédés de transfert Download PDF

Info

Publication number
WO2024216823A1
WO2024216823A1 PCT/CN2023/117695 CN2023117695W WO2024216823A1 WO 2024216823 A1 WO2024216823 A1 WO 2024216823A1 CN 2023117695 W CN2023117695 W CN 2023117695W WO 2024216823 A1 WO2024216823 A1 WO 2024216823A1
Authority
WO
WIPO (PCT)
Prior art keywords
smf
wireless communication
request message
pdu session
communication 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
PCT/CN2023/117695
Other languages
English (en)
Inventor
Jinguo Zhu
Shuang Liang
Menghan WANG
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
Priority to PCT/CN2023/117695 priority Critical patent/WO2024216823A1/fr
Publication of WO2024216823A1 publication Critical patent/WO2024216823A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • 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

  • the disclosure relates generally to wireless communications, including but not limited to systems and methods for handover.
  • the standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) .
  • the 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) .
  • 5G-AN 5G Access Network
  • 5GC 5G Core Network
  • UE User Equipment
  • the elements of the 5GC also called Network Functions, have been simplified with some of them being software based, and some being hardware based, so that they could be adapted according to need.
  • example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
  • example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
  • a first wireless communication node may receive a handover request message from a first network entity (e.g., an access and mobility management function (AMF) ) .
  • the handover request message may include a radio access network (RAN) container.
  • the first wireless communication node may determine whether to select a first session management function (SMF) (e.g., a I-SMF) for direct communication with the first wireless communication node according to the RAN container.
  • SMS session management function
  • the RAN container may include at least one of: a packet data unit (PDU) session identity (ID) ; a second SMF (e.g., a source I-SMF) address; radio information of at least one quality of service (QoS) flow; or QoS profile information of a PDU session.
  • PDU packet data unit
  • ID packet data unit
  • second SMF e.g., a source I-SMF
  • QoS quality of service
  • the first wireless communication node may select the first SMF for direct communication with the first wireless communication node.
  • the first wireless communication node may send a packet data unit (PDU) session create request message to the selected first SMF.
  • the PDU session create request message may include the second SMF address of a PDU session.
  • the first wireless communication node may determine at least one radio resource to be allocated for the PDU session.
  • the PDU session create request message may further include N2 session management (SM) information.
  • the N2 SM information may include N3 user plane information of the PDU session.
  • the first wireless communication node may receive a packet data unit (PDU) session establishment request message from a wireless communication device.
  • the PDU session establishment request message may include at least one of: single -network slice selection assistance information (S-NSSAI) ; a data network name (DNN) ; a PDU session identity (ID) ; or a request type.
  • S-NSSAI single -network slice selection assistance information
  • DNN data network name
  • ID PDU session identity
  • the first wireless communication node may select the second SMF for direct communication with the first wireless communication node according to the PDU session establishment request message.
  • the first wireless communication node may transmit the PDU session establishment request message to the selected second SMF.
  • the PDU session establishment request message further includes at least one of: a user equipment (UE) identity (ID) ; UE location information; an access type; a radio access technology (RAT) type; or a third SMF (e.g., an anchor SMF) address selected by the first wireless communication node.
  • the second SMF e.g., a I-SMF
  • the configuration may include single -network slice selection assistance information (S-NSSAI) and a data network name (DNN) .
  • S-NSSAI single -network slice selection assistance information
  • DNN data network name
  • the second SMF may select a third SMF via a network repository function (NRF) according to a configuration.
  • the configuration may include single -network slice selection assistance information (S-NSSAI) and a data network name (DNN) .
  • S-NSSAI single -network slice selection assistance information
  • DNN data network name
  • the first wireless communication node may receive a resource request message to request a radio resource allocation for at least one quality of service (QoS) flow corresponding to the PDU session establishment request message from the selected second SMF.
  • the resource request message may include at least one quality of service (QoS) profile and N3 tunnel information of a user plane function (UPF) .
  • QoS quality of service
  • the first wireless communication node may receive a security mode command message from the first network entity.
  • the security mode command message may include at least one security context to protect communication between a wireless communication device and the first wireless communication node.
  • the first wireless communication node may transmit a registration request message to the first network entity.
  • the registration request message may include at least one of: a registration type; a globally unique temporary identifier (GUTI) ; at least one security parameter; or a user equipment (UE) mobility management (MM) core network capability.
  • the first network entity may perform a UE authentication procedure according to the registration request message.
  • FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure
  • FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure
  • FIG. 3 illustrates an example architecture of a 5G system, in accordance with some embodiments of the present disclosure
  • FIG. 4 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure
  • FIG. 7A illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure
  • FIG. 7B illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure.
  • FIG. 8 illustrates a flow diagram of an example method for handover, in accordance with an embodiment of the present disclosure.
  • FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
  • the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100.
  • NB-IoT narrowband Internet of things
  • Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101.
  • the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
  • Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
  • the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
  • the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
  • Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
  • the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
  • FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution.
  • the system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein.
  • system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.
  • the System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) .
  • the BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220.
  • the UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240.
  • the BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
  • system 200 may further include any number of modules other than the modules shown in FIG. 2.
  • modules other than the modules shown in FIG. 2.
  • the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof.
  • various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
  • the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
  • a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
  • the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
  • a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
  • the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
  • the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
  • the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
  • LTE Long Term Evolution
  • 5G 5G
  • the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
  • eNB evolved node B
  • the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
  • PDA personal digital assistant
  • the processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
  • a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof.
  • the memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively.
  • the memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.
  • the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively.
  • Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
  • the network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202.
  • network communication module 218 may be configured to support internet or WiMAX traffic.
  • network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network.
  • the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
  • MSC Mobile Switching Center
  • the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
  • the model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it.
  • the OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols.
  • the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
  • a first layer may be a physical layer.
  • a second layer may be a Medium Access Control (MAC) layer.
  • MAC Medium Access Control
  • a third layer may be a Radio Link Control (RLC) layer.
  • a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • a fifth layer may be a Radio Resource Control (RRC) layer.
  • a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
  • NAS Non Access Stratum
  • IP Internet Protocol
  • a relay of a session management message between a user equipment (UE) and a session management function (SMF) by an access and mobility management function (AMF) can lead to inefficiency and excessive system complexity due to interactions between the AMF and the SMF.
  • AMF access and mobility management function
  • the present disclosure presents a solution for a PDU session handover that bypasses the direct interaction between the AMF and the SMF.
  • FIG. 3 illustrates an example architecture of a 5G system, in accordance with some embodiments of the present disclosure.
  • this example architecture there can be following functions.
  • UE user equipment.
  • the RAN may manage the radio resource.
  • the RAN may deliver the user data received over N3 to the UE and may deliver the user data from the UE over a N3 interface.
  • the RAN may perform a mapping between dedicated radio bearers (DRBs) and quality of service (QoS) flows in a packet data unit (PDU) session.
  • DRBs dedicated radio bearers
  • QoS quality of service
  • AMF access and mobility management function. This function may include at least one of following functionalities: a registration management, a connection management, or a reachability management and mobility management. This function may also perform the access authentication and access authorization.
  • the AMF can be a non-access stratum (NAS) security termination and may relay a session management (SM) NAS message between the UE and a session management function (SMF) .
  • NAS non-access stratum
  • SM session management
  • SMF session management function
  • SMF session management function. This function may include at least one of following functionalities: a session establishment, a modification and release, a UE IP address allocation and management (including optional authorization functions) , a selection and control of user plane (UP) function, or a downlink data notification.
  • the SMF may control a user plane function (UPF) via N4 association.
  • the SMF may provide a packet detection rule (PDR) to the UPF to instruct how to detect user data traffic, a forwarding action rule (FAR) , a QoS enforcement rule (QER) , a usage reporting rule (URR) to instruct the UPF how to perform the user data traffic forwarding, QoS handling and usage reporting for the user data traffic detected by using the PDR.
  • PDR packet detection rule
  • FAR forwarding action rule
  • QER QoS enforcement rule
  • URR usage reporting rule
  • UPF user plane function. This function may include at least one of following functionalities: serving as an anchor point for intra-/inter-radio access technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, QoS handling for the user plane, or downlink packet buffering and downlink data notification triggering.
  • RAT intra-/inter-radio access technology
  • GTP-U General packet radio services tunnelling protocol user plane
  • the GTP-U tunnel can be per PDU session.
  • the UPF may bind the downlink traffic to QoS flows within the GTP-U tunnel of the PDU session by using the FARs received from the SMF.
  • the RAN may transfer the user plane traffic to QoS flows identified by the UE.
  • PCF policy control function.
  • the PCF may provide QoS policy rules to control plane functions to enforce the rules.
  • the PCF (s) may transform the application function (AF) requests into policy and charging control (PCC) rules that apply to PDU sessions.
  • AF application function
  • PCC policy and charging control
  • UDM unified data management.
  • the UDM may perform the generation of an authentication and key management agreement (AKA) authentication credential, an access authorization based on subscription data, and/or UE's serving network function (NF) registration management (e.g., storing serving AMF for UE, storing serving SMF for UE's PDU Session) and subscription management.
  • AKA authentication and key management agreement
  • NF serving network function
  • the UDM may access the unified data repository (UDR) to retrieve UE subscription data and may store the UE context into the UDR.
  • the UDM and UDR may be deployed together.
  • FIG. 4 illustrates a sequence diagram of an example PDU session establishment procedure, in accordance with some embodiments of the present disclosure.
  • Step 1 A UE may send a non-access stratum (NAS) message (e.g., a PDU session establishment request message) to an AMF.
  • the NAS message may include at least one of: single -network slice selection assistance information (S-NSSAI) , a data network name (DNN) , a PDU session identity (ID) , a request type, or a N1 SM container.
  • S-NSSAI single -network slice selection assistance information
  • DNN data network name
  • ID PDU session identity
  • Step 2 The AMF may select a session management function (SMF) for the PDU session via a network repository function (NRF) or a local configuration.
  • SMF session management function
  • NRF network repository function
  • the AMF may provide the DNN and the S-NSSAI to the NRF, so the NRF can select an SMF to the AMF, together with a service area of the selected SMF.
  • Step 3 The AMF may send a Nsmf_PDUSession_CreateSMContext request message to the selected SMF.
  • the Nsmf_PDUSession_CreateSMContext request message may include at least one of: a PDU session ID, a SM context ID, UE location information, an access type, a radio access technology (RAT) type, or an operation type.
  • RAT radio access technology
  • Step 4 The SMF may send a Nsmf_PDUSession_CreateSMContext Response message to the AMF.
  • Step 5 The SMF may determine that the PCC authorization is required and requests to establish an SM policy association with the PCF by invoking a Npcf_SMPolicyControl_Create operation.
  • Step 6 The PCF may make an authorization and a policy decision.
  • the PCF may answer with a Npcf_SMPolicyControl_Create response message.
  • the PCF may provide PCC rules to the SMF.
  • the SMF may select an user plane function (UPF) and may request the UPF to allocate a N3 tunnel for the uplink data.
  • UPF user plane function
  • Step 7 The SMF may send AMF an Namf_Communication_N1N2MessageTransfer message.
  • the message may include at least one of: parameters (e.g., PDU session ID) , N2 SM information (e.g., PDU session ID, QFI (s) , QoS Profile (s) , N3 tunnel of the UPF) , or a N1 SM container (e.g., PDU session establishment accept) .
  • parameters e.g., PDU session ID
  • N2 SM information e.g., PDU session ID, QFI (s) , QoS Profile (s) , N3 tunnel of the UPF
  • a N1 SM container e.g., PDU session establishment accept
  • Step 8 The AMF may send a N2 PDU session request message to the (R) AN.
  • the N2 PDU session request message may include at least one of: N2 SM information, a NAS message (e.g., PDU session ID, a N1 SM container (e.g., PDU session establishment accept) ) .
  • Step 9 The (R) AN may send a RRC reconfiguration to the UE.
  • the (R) AN may issue an access network (AN) specific signaling exchange with the UE that is related with the information received from the SMF. For example, in case of a NG-RAN, an RRC connection reconfiguration may take place with the UE establishing the NG-RAN resources related to the QoS profile (s) .
  • the (R) AN may also allocate (R) AN tunnel information for the PDU session.
  • the (R) AN may forward the NAS message (e.g., a PDU session ID, a N1 SM container (e.g., PDU session establishment accept) ) to the UE.
  • NAS message e.g., a PDU session ID, a N1 SM container (e.g., PDU session establishment accept)
  • Step 10 The (R) AN may send a N2 PDU session response (e.g., a PDU session ID, cause, N2 SM information) message to the AMF.
  • the (R) AN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.
  • Step 11 The AMF may send a Nsmf_PDUSession_UpdateSMContext request (e.g., a SM context ID, N2 SM information, a request type) message to the SMF.
  • the AMF may forward the N2 SM information received from (R) AN to the SMF.
  • Step 12 The SMF may send a Nsmf_PDUSession_UpdateSMContext response (cause) message to the AMF.
  • both the SM NAS message e.g. PDU session establishment request, PDU session establishment accept
  • N2 SM information can be transferred via the AMF, which may not be efficient.
  • the present disclosure provides a solution to handle the PDU session without involvement of AMF.
  • the present disclosure also provides a solution for N2 based handover procedure, in which there is no interaction between the AMF and the SMF.
  • the RAN can communicate with the SMF directly without AMF involvement. It is possible when the N2 interface is service based so the RAN can discover the SMF via a network repository function (NRF) and communicate with the selected SMF directly.
  • FIG. 5 illustrates a sequence diagram of an example UE registration procedure, in accordance with some embodiments of the present disclosure. In this procedure the AMF provides the security information to the RAN to protect the message between the UE and the RAN.
  • Step 1 A UE may send a NAS registration request message to a RAN.
  • the NAS registration request message may include at least one of: a registration type, a globally unique temporary identifier (GUTI) , at least one security parameter, a UE mobility management (MM) core network capability, or other parameters.
  • GUI globally unique temporary identifier
  • MM UE mobility management
  • Step 2 The RAN may select an AMF and may forward the registration request message to the AMF.
  • Step 3 The AMF may decide to retrieve the UE context including the subscription permanent identifier (SUPI) from the old AMF.
  • the AMF may send a UE context request message to the old AMF identified by the GUTI provided by the UE.
  • SUPI subscription permanent identifier
  • Step 4 The old AMF may return the UE context including the SUPI to the new AMF.
  • Step 5 The AMF may perform a UE authentication procedure.
  • the UE can be authenticated by the network and the network can be also authenticated by the UE.
  • Step 6 After the UE is successfully authenticated, the AMF may send security mode command message towards the RAN node. This message may include security contexts to protect the message between the UE and the RAN.
  • Step 7 The RAN may send a security mode command to the UE to start the security handling.
  • the UE may respond with the NAS message Security Mode Complete to the RAN which is security protected.
  • the security protect may include both the message integrating and message ciphering.
  • Step 8 The RAN may decipher the NAS security Mode Command Complete message and may forward it to the AMF.
  • Step 9 After the success of authentication, the AMF may retrieve a UE subscription from the UDM.
  • the AMF may discover the UDM by using the SUPI.
  • the AMF may send UE subscription data request message towards the UDM. This message may include the SUPI and the AMF address.
  • Step 10 The UDM may store the AMF address and may return the UE subscription data towards the AMF.
  • the AMF may include the NAS Registration Accept message in the N2 message.
  • the NAS Registration message can be sent to the UE.
  • the NAS Registration message may include the Registration Area and the new GUTI and the Mobility Restriction information.
  • the N2 message can be sent to the RAN and may also include the mobility restriction information.
  • Step 12 The RAN may perform the security handling for the NAS message and may send the NAS Registration Accept message over the Uu interface to the UE.
  • Step 13 The UE may decipher the NAS message and may store the registration area, GUTI and the mobility restriction information, and may send a registration complete message to the AMF.
  • the UE is successfully registered in the network.
  • FIG. 6 illustrates a sequence diagram of an example PDU session establishment procedure with I-SMF insertion, in accordance with some embodiments of the present disclosure.
  • the RAN may discover the I-SMF and may communicate with the I-SMF directly without involvement of an AMF.
  • Step 1 A UE may send a NAS message (e.g., a PDU session establishment request message) to a RAN.
  • This message may include at least one of: S-NSSAI (s) , a DNN, a PDU session ID, or a request type.
  • the NAS message may also include a SUPI to uniquely identify the UE.
  • Step 2 The RAN may select an SMF for the PDU session via a NRF or a local configuration.
  • the RAN may provide the DNN and S-NSSAI to the NRF, so the NRF can select an SMF to the RAN.
  • the RAN may determine that it cannot connect to the SMF directly. In this case, the RAN may select an intermediated-SMF (I-SMF) which the RAN can directly communicate with.
  • I-SMF intermediated-SMF
  • Step 3 The RAN may forward the PDU session establishment request to the selected I-SMF, together with at least of a UE ID, UE location information, an access type, a RAT Type, and/or optionally the SMF (e.g., an anchor SMF) address selected by the RAN.
  • the UE ID can be set to SUPI and can be sent to selected I-SMF if the SUPI is not provided in the PDU Session establishment request message.
  • Step 4 The I-SMF may select an I-UPF and may send a N4 session establishment request message to the I-UPF.
  • the I-UPF may allocate and may provide the N3 user plane information and N9 user plane information of the PDU session to I-SMF.
  • the N3 interface can be between the RAN and the I-UPF.
  • the N9 interface can be between the I-UPF and the UPF.
  • Step 5 If the SMF address is not provided by the RAN, the I-SMF may select the SMF of the PDU session via a NRF or a local configuration. In case of via NRF, the I-SMF may provide the DNN and the S-NSSAI to the NRF, so the NRF can select an SMF for the PDU session.
  • Step 6 The I-SMF may send a PDU session create request message towards the selected SMF, including a UE ID, a DNN, and/or S-NSSAI.
  • Step 7 The SMF may retrieve the UE subscription data of the S-NSSAI and DNN from the UDM by using the UE ID, the S-NSSAI, and/or the DNN.
  • Step 8 The SMF may determine at least one QoS flow parameters based on subscription and PCC rule (s) .
  • the SMF may select an UPF to serve the PDU session and may configure the UPF with the detection rules and traffic handling rules for the QoS flows.
  • the UPF may allocate N9 tunnel information for the uplink traffic.
  • Step 9 The SMF may send a PDU session registration request message to the UDM.
  • This message may include a SMF address, a PDU session ID.
  • the UDM may store the PDU session ID.
  • the SMF may address and return the response to the SMF.
  • Step 10 The SMF may send a PDU session create response message towards the RAN.
  • This message may include the QoS profiles of the QoS flows in the PDU session, and/or the N9 tunnel information of the UPF.
  • Step 11 The SMF may send a RAN resource request message to the RAN to request radio resource allocation for the QoS flows of the PDU session.
  • This message may include the QoS profiles of the QoS flows and/or the N3 tunnel information of the I-UPF.
  • the SMF may also send the NAS PDU session establishment accept message towards the RAN.
  • Step 12 The RAN may communicate with the UE to allocate the radio resource for the QoS flows.
  • the RAN may also send a NAS PDU session establishment accept message towards the UE.
  • Step 13 The RAN may allocate RAN N3 tunnel information for the PDU session and may send a radio resource response message to the I-SMF, including the RAN N3 tunnel information for the PDU Session.
  • Step 14 The I-SMF may provide the RAN N3 tunnel information and the UPF N9 tunnel information for the PDU Session to the I-UPF.
  • the PDU session with I-SMF insertion is established and the PDU session information is stored in the UDM.
  • the interaction between the AMF and the SMF can be avoided.
  • FIGS. 7A and 7B illustrate a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure.
  • FIGS. 7A and 7B show how to support direct communicate between a RAN and a SMF in a N2 based handover. This procedure can be used when there is no Xn interface between a source RAN and a target RAN.
  • Step 0 Before a handover, a user plane to transfer uplink data and downlink data can be between the UE and the source RAN, between the source RAN and the source I-UPF, and between the source RAN and the UPF.
  • Step 1 Based on radio measurement, the source RAN may send a handover required message including the target information and RAN container towards the source AMF.
  • the RAN container may include at least one of: a SUPI, a PDU Session ID, an address of the source I-SMF or source SMF (in case no source I-SMF) , radio information of the QoS flows, or QoS profiles of the PDU Session.
  • Step 2 Based on the target information, the source AMF may determine the target AMF and may send a UE context relocation request message towards the target AMF. This message may include the target information and the RAN container received from the source RAN.
  • Step 3 The target AMF may select the target RAN and may send a handover request message towards the target RAN.
  • This message may include the RAN container received from the source AMF.
  • This message may also include the SUPI.
  • Step 4 Based on the received source I-SMF address or SMF address, the target RAN may determine whether to select target I-SMF which can communicate with the target RAN directly.
  • Step 5 The target RAN may send a PDU Session Create request message towards the target I-SMF, including the source I-SMF address or SMF address of the PDU session. If QoS profiles of the PDU session are received in Step 3, the target RAN may allocate radio resource for the PDU session.
  • the PDU session create request message may include the N2 SM information.
  • the N2 SM Information may include target RAN N3 user plane information of the PDU session.
  • the target RAN N3 tunnel can be used between the target RAN and the I-UPF.
  • Step 6 The target I-SMF may send a PDU session context request message towards the source I-SMF or SMF to retrieve session management context.
  • Step 7 The source I-SMF or SMF may return the session management context.
  • the session management context may include the QoS information of the PDU session, the N9 tunnel information of the UPF, and/or the SMF address of the PDU Session.
  • Step 8 The target I-SMF may select I-UPF and may send a N4 session establishment request message to the target I-UPF.
  • Step 9 The target I-UPF may allocate and may provide the target I-UPF N3 user plane information and target I-UPF N9 user plane information of the PDU session to the target I-SMF.
  • Step 10 If the radio information has not been allocated for the QoS flows in the target RAN (e.g. no N2 SM information is received in Step 5) , the target I-SMF may send RAN radio resource allocation request to the target RAN, including the N2 SM information.
  • the N2 SM information may include the QoS profiles of the QoS flows in the PDU session and/or the N3 tunnel information of the target I-UPF.
  • Step 11 The target RAN may allocate the radio resource of the QoS flow and may allocate N3 tunnel information for the PDU session.
  • the Target RAN may send a RAN radio resource allocation response message to the target I-SMF, including the N2 SM information.
  • the N2 SM information may include whether the QoS flows have been accepted and the N3 tunnel information of the target RAN.
  • Step 12 The target I-SMF may send the create PDU session response to the target RAN. If Steps 10 and 11 are not performed, this message may also include N2 SM information.
  • the N2 SM information may include the N3 tunnel information of the target I-UPF.
  • Step 13 The Target RAN may send a handover ACK towards the target AMF, including the RAN container.
  • the RAN container may include the radio resource information of the PDU session in the target RAN.
  • Step 14 The target AMF may send a UE context relocation response message towards the source AMF, including the RAN container as received from the target RAN.
  • Step 15 The source AMF may send a handover response message to the source RAN, including the RAN container as received from the target AMF.
  • Step 16 The source RAN may send a handover command message to the UE.
  • This message may include radio resources received from the target RAN.
  • Step 17 Based on the radio resource received from source RAN, the UE may access to the target RAN and may establish a radio connection towards the target RAN.
  • Step 18 The Target RAN may send a handover notification towards the target I-SMF.
  • Step 19 The target I-SMF may send a N4 Session modification request message to target I-UPF, to update the N3 tunnel information of the target RAN.
  • Step 20 The target I-UPF may send a N4 session modification response message to the target I-SMF.
  • Step 21 The target I-SMF may send a PDU session update request message towards the SMF, including the N9 user plane information of the PDU session received from the I-UPF in Step 9.
  • Step 22 The SMF may send a N4 session modification request message to UPF to update the N9 user plane information of the target I-UPF.
  • Step 23 The UPF may send a N4 session modification response message to the SMF.
  • Step 24 The SMF may send a PDU session update response message towards the target I-SMF.
  • Step 25 The UE may perform a UE registration in the target AMF via the target RAN.
  • the user plane of the PDU session is now between the UE and the target RAN, between the target RAN and the target I-UPF (N3 tunnel) , between the target I-UPF and the UPF (N9 tunnel) .
  • N3 tunnel between the target RAN and the target I-UPF
  • N9 tunnel between the target I-UPF and the UPF
  • FIG. 8 illustrates a flow diagram of a method 800 for handover.
  • the method 800 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGS. 1–6, 7A and 7B.
  • the method 800 may be performed by a wireless communication node (e.g., a target RAN) , in some embodiments. Additional, fewer, or different operations may be performed in the method 800 depending on the embodiment. At least one aspect of the operations is directed to a system, method, apparatus, or a computer-readable medium.
  • a first wireless communication node may receive a handover request message from a first network entity (e.g., an access and mobility management function (AMF) ) .
  • the handover request message may include a radio access network (RAN) container.
  • the first wireless communication node may determine whether to select a first session management function (SMF) (e.g., a I-SMF) for direct communication with the first wireless communication node according to the RAN container.
  • SMS session management function
  • the RAN container may include at least one of: a packet data unit (PDU) session identity (ID) ; a second SMF (e.g., a source I-SMF) address; radio information of at least one quality of service (QoS) flow; or QoS profile information of a PDU session.
  • PDU packet data unit
  • ID packet data unit
  • second SMF e.g., a source I-SMF
  • QoS quality of service
  • the first wireless communication node may select the first SMF for direct communication with the first wireless communication node.
  • the first wireless communication node may send a packet data unit (PDU) session create request message to the selected first SMF.
  • the PDU session create request message may include the second SMF address of a PDU session.
  • the first wireless communication node may determine at least one radio resource to be allocated for the PDU session.
  • the PDU session create request message may further include N2 session management (SM) information.
  • the N2 SM information may include N3 user plane information of the PDU session.
  • the first wireless communication node may receive a packet data unit (PDU) session establishment request message from a wireless communication device.
  • the PDU session establishment request message may include at least one of: single -network slice selection assistance information (S-NSSAI) ; a data network name (DNN) ; a PDU session identity (ID) ; or a request type.
  • S-NSSAI single -network slice selection assistance information
  • DNN data network name
  • ID PDU session identity
  • the first wireless communication node may select the second SMF for direct communication with the first wireless communication node according to the PDU session establishment request message.
  • the first wireless communication node may transmit the PDU session establishment request message to the selected second SMF.
  • the PDU session establishment request message further includes at least one of: a user equipment (UE) identity (ID) ; UE location information; an access type; a radio access technology (RAT) type; or a third SMF (e.g., an anchor SMF) address selected by the first wireless communication node.
  • the second SMF e.g., a I-SMF
  • the configuration may include single -network slice selection assistance information (S-NSSAI) and a data network name (DNN) .
  • S-NSSAI single -network slice selection assistance information
  • DNN data network name
  • the second SMF may select a third SMF via a network repository function (NRF) according to a configuration.
  • the configuration may include single -network slice selection assistance information (S-NSSAI) and a data network name (DNN) .
  • S-NSSAI single -network slice selection assistance information
  • DNN data network name
  • the first wireless communication node may receive a resource request message to request a radio resource allocation for at least one quality of service (QoS) flow corresponding to the PDU session establishment request message from the selected second SMF.
  • the resource request message may include at least one quality of service (QoS) profile and N3 tunnel information of a user plane function (UPF) .
  • QoS quality of service
  • the first wireless communication node may receive a security mode command message from the first network entity.
  • the security mode command message may include at least one security context to protect communication between a wireless communication device and the first wireless communication node.
  • the first wireless communication node may transmit a registration request message to the first network entity.
  • the registration request message may include at least one of: a registration type; a globally unique temporary identifier (GUTI) ; at least one security parameter; or a user equipment (UE) mobility management (MM) core network capability.
  • the first network entity may perform a UE authentication procedure according to the registration request message.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a "software module) , or any combination of these techniques.
  • firmware e.g., a digital implementation, an analog implementation, or a combination of the two
  • firmware various forms of program or design code incorporating instructions
  • software or a “software module”
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

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

Abstract

Sont présentés des systèmes et des procédés de transfert. Un premier nœud de communication sans fil peut recevoir un message de demande de transfert en provenance d'une première entité de réseau. Le message de demande de transfert peut comprendre un conteneur de réseau d'accès radio (RAN). Le premier nœud de communication sans fil peut déterminer s'il faut sélectionner une première fonction de gestion de session (SMF) pour une communication directe avec le premier nœud de communication sans fil en fonction du conteneur RAN.
PCT/CN2023/117695 2023-09-08 2023-09-08 Systèmes et procédés de transfert Pending WO2024216823A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/117695 WO2024216823A1 (fr) 2023-09-08 2023-09-08 Systèmes et procédés de transfert

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/117695 WO2024216823A1 (fr) 2023-09-08 2023-09-08 Systèmes et procédés de transfert

Publications (1)

Publication Number Publication Date
WO2024216823A1 true WO2024216823A1 (fr) 2024-10-24

Family

ID=93151935

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/117695 Pending WO2024216823A1 (fr) 2023-09-08 2023-09-08 Systèmes et procédés de transfert

Country Status (1)

Country Link
WO (1) WO2024216823A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200120570A1 (en) * 2016-12-15 2020-04-16 Lg Electronics Inc. Method for performing handover in wireless communication system and apparatus therefor
WO2021260417A1 (fr) * 2020-06-25 2021-12-30 Telefonaktiebolaget Lm Ericsson (Publ) Procédés assurant une communication flexible entre des réseaux d'accès radio et des réseaux centraux, et nœuds associés
CN115707053A (zh) * 2021-08-12 2023-02-17 大唐移动通信设备有限公司 一种网络切换方法、装置及网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200120570A1 (en) * 2016-12-15 2020-04-16 Lg Electronics Inc. Method for performing handover in wireless communication system and apparatus therefor
WO2021260417A1 (fr) * 2020-06-25 2021-12-30 Telefonaktiebolaget Lm Ericsson (Publ) Procédés assurant une communication flexible entre des réseaux d'accès radio et des réseaux centraux, et nœuds associés
CN115707053A (zh) * 2021-08-12 2023-02-17 大唐移动通信设备有限公司 一种网络切换方法、装置及网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Procedures for Inter-RAT mobility support to and from NB-IoT", 3GPP DRAFT; S2-1900630 TS 23.502 PROCEDURES FOR INTER-RAT MOBILITY SUPPORT TO AND FROM NB-IOT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Kochi, India; 20190121 - 20190125, 15 January 2019 (2019-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051590298 *

Similar Documents

Publication Publication Date Title
CN110999431B (zh) 用于在无线通信系统中注册终端的方法及其设备
US20230015755A1 (en) System and method for sidelink communications in wireless communication networks
US12402069B2 (en) Method for slice information update
US20250106105A1 (en) Configuring for mobile relay nodes with user plane functions
US11611899B2 (en) Method of quality of service control for a specific user equipment in a slice
CN113873520A (zh) 一种通信方法、终端设备和无线接入网设备
US20230284128A1 (en) Method of slice support for vehicle-to-everything service
US20240188157A1 (en) Systems and methods for establishing shared n3 tunnel
WO2024216823A1 (fr) Systèmes et procédés de transfert
WO2024230030A1 (fr) Systèmes et procédés de transfert
WO2024113069A1 (fr) Systèmes et procédés de gestion de qualité de service pour un trafic de réalité étendue
CN113329406A (zh) 用于共享网络中的无线资源控制管理的系统和方法
WO2024230037A1 (fr) Systèmes et procédés de gestion de session
WO2025076714A1 (fr) Systèmes et procédés d'enregistrement d'équipements utilisateurs
WO2024169004A1 (fr) Systèmes et procédés de réactivation d'une session d'unité de données de protocole (pdu) pour remplacement de nom de réseau de données (dnn)
WO2025236499A1 (fr) Systèmes et procédés d'authentification et de gestion de clé pour désactivation de service d'applications
AU2021459631B2 (en) Systems and methods for establishing shared n3 tunnel
WO2024156159A1 (fr) Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs)
WO2024216828A1 (fr) Systèmes et procédés de prise en charge de l'authentification et de la sécurité d'un ue
US12349096B1 (en) Method and user equipment for locally removing S-NSSAI upon expiry of slice deregistration inactivity timer
WO2024156135A1 (fr) Systèmes et procédés de réattribution de fonction de gestion de session (smf)
WO2025035397A1 (fr) Procédé, dispositif et produit-programme d'ordinateur pour des communications sans fil
US20250324380A1 (en) Operation method due to slice deregistration inactivity timer expiry
US20250324381A1 (en) Method for performing a de-mapping of a replaced s-nssai and an alternative s-nssai
WO2025145587A1 (fr) Systèmes et procédés de transfert d'informations pour systèmes de relais

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: 23933694

Country of ref document: EP

Kind code of ref document: A1