Systems and methods for handover
Patent Information
- Application Number
- PCT/CN2023/117810
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-09-08
- Publication Date
- 2024-11-14
Smart Images

Figure CN2023117810_14112024_PF_FP_ABST
Abstract
Description
SYSTEMS AND METHODS FOR HANDOVERTECHNICAL FIELD
[0001] The disclosure relates generally to wireless communications, including but not limited to systems and methods for handover.BACKGROUND
[0002] 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) . In order to facilitate the enablement of different data services and requirements, 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.SUMMARY
[0003] The 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. In accordance with various embodiments, 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.
[0004] At least one aspect is directed to a system, method, apparatus, or a computer-readable medium of the following. A first wireless communication node (e.g., a target radio access network (RAN) ) may select a first network entity (e.g., a session management function (SMF) or a intermediated SMF (I-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 network entity. The PDU session create request message may include session management (SM) information and a session management function (SMF) address of a PDU session. The SM information may include N2 SM information. The N2 SM information may include N3 user plane information of the PDU session.
[0005] In some embodiments, the first wireless communication node may receive a handover prepare request message from a second wireless communication node (e.g., a source RAN) . The handover prepare request message may include at least one of: a PDU session identity (ID) ; the SMF address of the PDU session; quality of service (QoS) profile information of the PDU session; or radio resource information of the PDU session.
[0006] In some embodiments, the first wireless communication node may determine at least one radio resource to be reserved for a quality of service (QoS) flow of the PDU session. The first wireless communication node may send a handover prepare response message, wherein the handover prepare response message includes information of the determined at least one radio resource to the second wireless communication node.
[0007] In some embodiments, the first wireless communication node may receive a PDU session create response corresponding to the session create request message from the selected first network entity.
[0008] In some embodiments, a wireless communication device may perform a user equipment (UE) registration procedure via the first wireless communication node. The first wireless communication node may receive a PDU session establishment request message from a wireless communication device (e.g., a user equipment (UE) ) . 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. Selecting the first network entity for direct communication with the first wireless communication node may comprise: determining, by the first wireless communication node, the first network entity according to the PDU session establishment request message. The first wireless communication node may transmit the PDU session establishment request message to the selected first network entity.
[0009] In some embodiments, 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 first network entity. The resource request message may include at least one quality of service (QoS) profile and N3 tunnel information of a user plane function (UPF) .
[0010] In some embodiments, the first wireless communication node may receive a security mode command message from a second network entity (e.g., an access and mobility management function (AMF) ) . The security mode command message may include at least one security context to protect communication between a wireless communication device (e.g., a UE) and the first wireless communication node. The first wireless communication node may transmit a registration request message to a second network entity (e.g., an access and mobility management function (AMF) ) . 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 second network entity may perform a UE authentication procedure according to the registration request message.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.
[0012] 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;
[0013] 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;
[0014] FIG. 3 illustrates an example architecture of a 5G system, in accordance with some embodiments of the present disclosure;
[0015] FIG. 4 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure;
[0016] FIG. 5 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure;
[0017] FIG. 6 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure;
[0018] FIG. 7 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure; and
[0019] FIG. 8 illustrates a flow diagram of an example method for handover, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION
[0020] 1. Mobile Communication Technology and Environment
[0021] 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. In the following discussion, 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. ” 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. In FIG. 1, 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.
[0022] For example, 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. In the present disclosure, 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.
[0023] 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. In one illustrative embodiment, 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.
[0024] 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.
[0025] As would be understood by persons of ordinary skill in the art, system 200 may further include any number of modules other than the modules shown in FIG. 2. Those skilled in the art will understand that 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. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, 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.
[0026] In accordance with some embodiments, 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. Similarly, in accordance with some embodiments, 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.
[0027] 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. In some illustrative embodiments, 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.
[0028] In accordance with various embodiments, 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. In some embodiments, 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. 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. In this manner, 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.
[0029] Furthermore, 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. In this regard, 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. In some embodiments, 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.
[0030] 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. For example, network communication module 218 may be configured to support internet or WiMAX traffic. In a typical deployment, without limitation, 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. In this manner, the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) . The terms “configured for, ” “configured to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and / or arranged to perform the specified operation or function.
[0031] 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. In some embodiments, a first layer may be a physical layer. In some embodiments, a second layer may be a Medium Access Control (MAC) layer. In some embodiments, a third layer may be a Radio Link Control (RLC) layer. In some embodiments, a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, a fifth layer may be a Radio Resource Control (RRC) layer. In some embodiments, 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.
[0032] Various example embodiments of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
[0033] 2. Systems and Methods for Handover
[0034] In a 5G system, 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. To simplify the interaction between the AMF and the SMF for a packet data unit (PDU) session management, the present disclosure presents a solution for a PDU session handover that bypasses the direct interaction between the AMF and the SMF.
[0035] FIG. 3 illustrates an example architecture of a 5G system, in accordance with some embodiments of the present disclosure. In this example architecture, there can be following functions.
[0036] (1) UE: user equipment.
[0037] (2) RAN: radio access network. 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.
[0038] (3) 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) .
[0039] (4) 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.
[0040] (5) 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. General packet radio services (GPRS) tunnelling protocol user plane (GTP-U) tunnel can be used over N3 interface between the RAN and the UPF. The GTP-U tunnel can be per PDU session. For downlink traffic, 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. For uplink traffic, the RAN may transfer the user plane traffic to QoS flows identified by the UE.
[0041] (6) 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.
[0042] (7) 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. 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.
[0043] FIG. 4 illustrates a sequence diagram of an example PDU session establishment procedure, in accordance with some embodiments of the present disclosure.
[0044] 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.
[0045] 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. In case of via the NRF, 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.
[0046] 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.
[0047] Step 4: The SMF may send a Nsmf_PDUSession_CreateSMContext Response message to the AMF.
[0048] 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.
[0049] Step 6: The PCF may make an authorization and a policy decision. The PCF may answer with a Npcf_SMPolicyControl_Create response message. In its response, 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.
[0050] 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) .
[0051] 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) ) .
[0052] 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.
[0053] 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.
[0054] 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.
[0055] Step 12: The SMF may send a Nsmf_PDUSession_UpdateSMContext response (cause) message to the AMF.
[0056] In the procedure in FIG. 4, both the SM NAS message (e.g. PDU session establishment request, PDU session establishment accept) and 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 Xn based handover procedure, in which there is no interaction between the AMF and the SMF.
[0057] Implementation Example 1
[0058] In the present disclosure, 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.
[0059] 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.
[0060] Step 2: The RAN may select an AMF and may forward the registration request message to the AMF.
[0061] 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.
[0062] Step 4: The old AMF may return the UE context including the SUPI to the new AMF.
[0063] Step 5: The AMF may perform a UE authentication procedure. In this procedure, the UE can be authenticated by the network and the network can be also authenticated by the UE.
[0064] 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.
[0065] 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.
[0066] Step 8: The RAN may decipher the NAS security Mode Command Complete message and may forward it to the AMF.
[0067] 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.
[0068] Step 10: The UDM may store the AMF address and may return the UE subscription data towards the AMF.
[0069] Step 11: 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.
[0070] 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.
[0071] 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.
[0072] After this procedure, the UE is successfully registered in the network.
[0073] Implementation Example 2
[0074] FIG. 6 illustrates a sequence diagram of an example PDU session establishment procedure, in accordance with some embodiments of the present disclosure. In this procedure the RAN may discover the SMF and may communicate with the SMF directly without involvement of an AMF.
[0075] Step 1: A UE may send a NAS message (e.g., a PDU session establishment request) to a RAN. The NAS message may include at least 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.
[0076] Step 2: The RAN may select an SMF for the PDU session via a NRF or a local configuration. In case of via the NRF, the RAN may provide the DNN and S-NSSAI to the NRF, so the NRF can select an SMF to the RAN. Then RAN may forward the PDU session establishment request to the selected SMF, together with at least of UE location information, an access type, or a RAT type. If the UE does not provide the SUPI in the PDU session establishment request message, the RAN may also send the SUPI to the selected SMF.
[0077] Step 3: The SMF may retrieve the UE subscription data of the S-NSSAI and DNN from a UDM by using the SUPI, S-NSSAI and DNN.
[0078] Step 4: The SMF may determine the 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 N3 tunnel information for the uplink traffic.
[0079] Step 5: 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 UPF.
[0080] Step 6: The RAN may communicate with the UE to allocate the radio resource for the QoS flows. The RAN may also allocate RAN N3 tunnel information for the PDU Session.
[0081] Step 7: The RAN may send a radio resource response message to the SMF, including the RAN N3 tunnel information for the PDU Session.
[0082] Step 8: The SMF may provide the RAN N3 tunnel information for the PDU session to the UPF.
[0083] Step 9: The SMF may send a PDU session registration request message to the UDM. This message may include a SMF address, and / or a PDU Session ID. The UDM may store the PDU Session ID and the SMF address and may return the response to the SMF.
[0084] Step 10: The SMF may send a PDU session establishment accept message to the RAN. This message may include an UE IP address for the PDU session. Alternatively, the SMF may use user plane to allocate the UP IP address to the UE.
[0085] Step 11: The RAN may forward the PDU session establishment accept message to the UE.
[0086] After this procedure, the PDU session is established and the PDU Session information is stored in the UDM. In this procedure, the interaction between the AMF and the SMF can be avoided.
[0087] Implementation Example 3
[0088] FIG. 7 illustrates a sequence diagram of an example handover procedure, in accordance with some embodiments of the present disclosure. FIG. 7 shows how to support direct communicate between the RAN and the SMF in a Xn based handover.
[0089] Step 0: Before a handover, a user plane to transfer the uplink data and downlink data can be between a UE and a source RAN and between a source RAN and a UPF.
[0090] Step 1: Based on a radio measurement, the source RAN may initiate a Xn based handover towards the target RAN by sending a Handover Prepare Request message. This message may include at least one of: a PDU session ID, a SMF address or intermediated SMF (I-SMF) address of the PDU session, QoS profile information of the PDU session, or radio resource information of the PDU session.
[0091] Step 2: The target RAN may determine to reserve the radio resource for the QoS flow of the PDU session received from the source RAN. The target RAN may return the Handover Prepare Response message to the source RAN. This message may include all the radio resource information successfully reserved for the UE in the target RAN.
[0092] Step 3: The source RAN may send a handover command message to the UE. This message may include radio resources received from the target RAN.
[0093] Step 4: Based on the radio resource received from the source RAN, the UE may access to the target RAN and may establish a radio connection towards the target RAN.
[0094] Step 5: Based on the received SMF address (or old I-SMF address) , if the target RAN determines that it cannot connect to the SMF (or old I-SMF) , the target RAN may select an new I-SMF (intermediate-SMF) which can communicate with the target RAN directly.
[0095] Step 6: The target RAN may send a PDU session create request message towards the selected I-SMF, including the N2 SM information and the SMF address (old I-SMF address) of the PDU session. 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.
[0096] Step 7: The I-SMF may send a PDU Session context request message towards the SMF (old I-SMF) to retrieve session management context.
[0097] Step 8: The SMF (old I-SMF) may return the session management context, including the UPF N9 tunnel information of the PDU session. The N9 tunnel can be used between the I-UPF and the UPF.
[0098] Step 9: The I-SMF may select an I-UPF and may send a N4 session establishment request message to the I-UPF, including the target RAN N3 user plane information of the PDU session received from the target RAN, and the UPF N9 tunnel information received from the SMF (old I-SMF) .
[0099] Step 10: The I-UPF may allocate and may provide the I-UPF N3 user plane information and I-UPF N9 user plane information of the PDU session to the I-SMF.
[0100] Step 11: The I-SMF may send a PDU session update request message towards the SMF, including the I-UPF N9 user plane information of the PDU session received from the I-UPF.
[0101] Step 12: The SMF may send a N4 session modification request message to UPF to update the I-UPF N9 user plane information.
[0102] Step 13: The UPF may send a N4 session modification response message to the SMF.
[0103] Step 14: The SMF may send a PDU session update response message towards the I-SMF.
[0104] Step 15: The I-SMF may return a PDU session create response message to the target RAN.
[0105] Step 16: The UE may perform UE registration procedure via the target RAN after the handover.
[0106] After this procedure the user plane of the PDU session is now between the UE and the target RAN, between the target RAN and the I-UPF (N3 tunnel) , between the I-UPF and the UPF (N9 tunnel) . In this procedure, there is no interaction between the AMF and the SMF, simplifying the handover procedure.
[0107] It should be understood that one or more features from the above implementation examples are not exclusive to the specific implementation examples, but can be combined in any manner (e.g., in any priority and / or order, concurrently or otherwise) .
[0108] 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 to 7. In overview, 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.
[0109] A first wireless communication node (e.g., a target radio access network (RAN) ) may select a first network entity (e.g., a session management function (SMF) or a I-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 network entity. The PDU session create request message may include session management (SM) information and a session management function (SMF) address of a PDU session. The SM information may include N2 SM information. The N2 SM information may include N3 user plane information of the PDU session.
[0110] In some embodiments, the first wireless communication node may receive a handover prepare request message from a second wireless communication node (e.g., a source RAN) . The handover prepare request message may include at least one of: a PDU session identity (ID) ; the SMF address of the PDU session; quality of service (QoS) profile information of the PDU session; or radio resource information of the PDU session.
[0111] In some embodiments, the first wireless communication node may determine at least one radio resource to be reserved for a quality of service (QoS) flow of the PDU session. The first wireless communication node may send a handover prepare response message, wherein the handover prepare response message includes information of the determined at least one radio resource to the second wireless communication node.
[0112] In some embodiments, the first wireless communication node may receive a PDU session create response corresponding to the session create request message from the selected first network entity.
[0113] In some embodiments, a wireless communication device may perform a user equipment (UE) registration procedure via the first wireless communication node. The first wireless communication node may receive a PDU session establishment request message from a wireless communication device (e.g., a user equipment (UE) ) . 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. Selecting the first network entity for direct communication with the first wireless communication node may comprise: determining, by the first wireless communication node, the first network entity according to the PDU session establishment request message. The first wireless communication node may transmit the PDU session establishment request message to the selected first network entity.
[0114] In some embodiments, 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 first network entity. The resource request message may include at least one quality of service (QoS) profile and N3 tunnel information of a user plane function (UPF) .
[0115] In some embodiments, the first wireless communication node may receive a security mode command message from a second network entity (e.g., an access and mobility management function (AMF) ) . The security mode command message may include at least one security context to protect communication between a wireless communication device (e.g., a UE) and the first wireless communication node. The first wireless communication node may transmit a registration request message to a second network entity (e.g., an access and mobility management function (AMF) ) . 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 second network entity may perform a UE authentication procedure according to the registration request message.
[0116] While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.
[0117] It is also understood that 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.
[0118] Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0119] A person of ordinary skill in the art would further appreciate that 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. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.
[0120] Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. 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.
[0121] If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. 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. By way of example, and not limitation, 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.
[0122] In this document, the term "module" as used herein, 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.
[0123] Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present solution. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, 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.
[0124] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.
Claims
1.A method comprising:selecting, by a first wireless communication node, a first network entity for direct communication with the first wireless communication node; andsending, by the first wireless communication node to the selected first network entity, a packet data unit (PDU) session create request message, wherein the PDU session create request message includes session management (SM) information and a session management function (SMF) address of a PDU session.2.The method of claim 1, wherein the SM information includes N2 SM information.3.The method of claim 2, wherein the N2 SM information includes N3 user plane information of the PDU session.4.The method of claim 1, comprising:receiving, by the first wireless communication node from a second wireless communication node, a handover prepare request message.5.The method of claim 4, wherein the handover prepare request message includes at least one of:a PDU session identity (ID) ; orthe SMF address of the PDU session; orquality of service (QoS) profile information of the PDU session; orradio resource information of the PDU session.6.The method of claim 4, comprising:determining, by the first wireless communication node, at least one radio resource to be reserved for a quality of service (QoS) flow of the PDU session; andsending, by the first wireless communication node to the second wireless communication node, a handover prepare response message, wherein the handover prepare response message includes information of the determined at least one radio resource.7.The method of claim 1, comprising:receiving, by the first wireless communication node from the selected first network entity, a PDU session create response corresponding to the session create request message.8.The method of claim 1, wherein a wireless communication device performs a user equipment (UE) registration procedure via the first wireless communication node.9.The method of claim 1, comprising:receiving, by the first wireless communication node from a wireless communication device, a PDU session establishment request message.10.The method of claim 9, wherein the PDU session establishment request message includes at least one of:a subscription permanent identifier (SUPI) ; orsingle -network slice selection assistance information (S-NSSAI) ; ora data network name (DNN) ; ora PDU session identity (ID) ; ora request type.11.The method of claim 9, wherein selecting the first network entity for direct communication with the first wireless communication node comprises:determining, by the first wireless communication node, the first network entity according to the PDU session establishment request message.12.The method of claim 11, comprising:transmitting, by the first wireless communication node to the selected first network entity, the PDU session establishment request message.13.The method of claim 12, comprising:receiving, by the first wireless communication node from the selected first network entity, 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, wherein the resource request message includes at least one quality of service (QoS) profile and N3 tunnel information of a user plane function (UPF) .14.The method of claim 1, comprising:receiving, by the first wireless communication node from a second network entity, a security mode command message, wherein the security mode command message includes at least one security context to protect communication between a wireless communication device and the first wireless communication node.15.The method of claim 1, comprising:transmitting, by the first wireless communication node to a second network entity, a registration request message, wherein the registration request message includes at least one of:a subscription permanent identifier (SUPI) ; ora registration type; ora globally unique temporary identifier (GUTI) ; orat least one security parameter; ora user equipment (UE) mobility management (MM) core network capability.16.The method of claim 15, wherein the second network entity performs a UE authentication procedure according to the registration request message.17.A non-transitory computer readable medium storing instructions, which when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1-16.18.An apparatus comprising:at least one processor configured to implement the method of any one of claims 1-16.
Citation Information
Patent Citations
Network slice switching method and device and communication system
CN114679753A
Quality of service support for sidelink relay service
US20210289391A1
Control unit and method for assisting side-link communication
US20220015088A1
Sidelink communication method and apparatus, and storage medium
US20220217575A1
Multiparty session processing method and device
WO2017045536A1
