Target radio access network node, source radio access network node, and methods thereof
The method addresses the lack of direct inter-base station handover signaling in 5G and LTE Systems by using slice and flow information for network transitions, ensuring efficient resource allocation and seamless communication.
Patent Information
- Application Number
- JP2023119539
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2016-08-10
- Filing Date
- 2023-07-24
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2037-05-15
AI Technical Summary
Existing handover procedures between 5G (NG System) and LTE Systems do not adequately address the transfer of handover signaling messages on a direct inter-base station interface, lacking necessary information for seamless network transitions.
Implementing a method and apparatus that facilitate the transfer of handover signaling messages on a direct inter-base station interface, utilizing slice and flow information to manage network handovers, including radio resource configuration and network slicing support.
Enables seamless handover between different Radio Access Technologies (RATs) by providing necessary information for network resource allocation and slice selection, ensuring continuous communication during transitions.
Smart Images

Figure 0007593447000001 
Figure 0007593447000002 
Figure 0007593447000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to wireless communication systems, and more particularly to handover of wireless terminals between different Radio Access Technologies (RATs). [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) started standardization work on the fifth generation mobile communication system (5G) for the introduction of the transition in 2020 as 3GPP Release 14 in 2016 (see Non-Patent Document 1). 5G is expected to be realized by a combination of continuous enhancement / evolution of LTE and LTE-Advanced and innovative enhancement / evolution by introducing a new 5G air interface (new Radio Access Technology (RAT)). The new RAT supports, for example, a higher frequency band than the frequency band (e.g., 6 GHz or less) targeted by the continuous evolution of LTE / LTE-Advanced, for example, a centimeter wave band of 10 GHz or more and a millimeter wave band of 30 GHz or more.
[0003] In this specification, the fifth generation mobile communication system is also referred to as the Next Generation (NextGen) System (NG System). The new RAT for the NG System is referred to as the New Radio (NR), 5G RAT, or NG RAT. The new radio access network (Radio Access Network (RAN)) and core network for the NG System are referred to as the NextGen RAN (NG RAN) and NextGen Core (NG Core), respectively. The wireless terminal (User Equipment (UE)) connecting to the NG System is referred to as the NextGen UE (NG UE). The formal names of the RAT, UE, radio access network, core network, network entities (nodes), and protocol layers for the NG System will be determined in the future as standardization work progresses.
[0004] In addition, the term "LTE" used in this specification includes improvements and developments of LTE and LTE-Advanced to enable interworking with the NG System, unless otherwise specified. Improvements and developments of LTE and LTE-Advanced to enable interworking with the NG System are also called LTE-Advanced Pro, LTE+, or enhanced LTE (eLTE). Furthermore, terms related to LTE networks or logical entities, such as "Evolved Packet Core (EPC)", "Mobility Management Entity (MME)", "Serving Gateway (S-GW)", and "Packet Data Network (PDN) Gateway (P-GW)", used in this specification include these improvements and developments to enable interworking with the NG System, unless otherwise specified. The improved EPC, MME, S-GW, and P-GW may also be referred to as, for example, enhanced EPC (eEPC), enhanced MME (eMME), enhanced S-GW (eS-GW), and enhanced P-GW (eP-GW).
[0005] In LTE and LTE-Advanced, for Quality of Service (QoS) and packet routing, a bearer per QoS class and per PDN connection is used in both RAN (i.e., Evolved Universal Terrestrial RAN) and core network (i.e., Evolved Packet core (EPC)). In other words, in the Bearer-based QoS (or per-bearer QoS) concept, one or more Evolved Packet System (EPS) bearers are set between the UE and the P-GW in the EPC, and multiple Service Data Flows (SDFs) with the same QoS class are forwarded through one EPS bearer that satisfies these QoS. An SDF is one or more packet flows that match an SDF template (i.e., packet filters) based on Policy and Charging Control (PCC) rules. For packet routing, each packet sent through an EPS bearer contains information to identify which bearer (i.e., General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel) this packet is associated with.
[0006] On the other hand, in the NG System, it is considered that a radio bearer may be used in the NG RAN, but a bearer is not used in the NG Core and the interface between the NG Core and the NG RAN (see Non-Patent Document 1). Specifically, PDU flows are defined instead of the EPS bearer, and one or more SDFs are mapped to one or more PDU flows. The PDU flow between the NG UE and the user plane termination entity in the NG Core (i.e., an entity equivalent to the P-GW in the EPC) corresponds to the EPS bearer in the EPS Bearer-based QoS concept. That is, the NG System adopts the Flow-based QoS (or per-flow QoS) concept instead of the Bearer-based QoS concept. In the Flow-based QoS concept, QoS is handled in units of PDU flows. Note that the association between the UE and the data network is called a PDU session. The PDU session is a term equivalent to the PDN connection in LTE and LTE-Advanced. Multiple PDU flows can be configured within one PDU session.
[0007] In this specification, a system that sets an end-to-end bearer (e.g., EPS bearer) between a UE and an edge node (e.g., P-GW) in a core network and adopts a bearer-based QoS concept, such as the LTE and LTE-Advanced systems, is called a "bearer-based system" or a "bearer-based network". On the other hand, a system that does not use a bearer in the core network and the interface between the core network and the RAN and adopts a flow-based QoS concept, such as the NG System, is called a "bearer-less system" or a "bearer-less network". As in the above-mentioned NG System, a radio bearer may be used in the RAN of a bearer-less network. The term "bearer-less" may be rephrased as, for example, GTP-less, (PDN) connection-less, tunnel-less, (IP) flow-based, SDF-based, stream-based, or (PDU) session-based. However, in this specification, the NG System may function as a bearer-based system and may support both flow-based and bearer-based transfer of user data.
[0008] Furthermore, it is also being considered that the NG System will support network slicing (see Non-Patent Document 1). Network slicing uses Network Function Virtualization (NFV) technology and software-defined networking (SDN) technology to enable the creation of multiple virtualized logical networks on a physical network. Each virtualized logical network is called a network slice or a network slice instance, includes logical nodes and functions, and is used for specific traffic and signaling. The NG RAN or the NG Core, or both, have a Slice Selection Function (SSF). The SSF selects one or more network slices suitable for the NG UE based on information provided by at least one of the NG UE and the NG Core.
[0009] Patent Document 1 includes disclosures regarding handover from a bearer-less network (e.g., 5G) to a bearer-based network (e.g., LTE) and handover from a bearer-based network (e.g., LTE) to a bearer-less network (e.g., 5G). In the handover from 5G to LTE shown in Patent Document 1, a source control node (i.e., Access Control Server (ACS) / eMME) of the 5G core (NG Core) maps QoS parameters of the service flows of the bearer-less network (5G) to EPS-bearer-level QoS of the bearer-based network (LTE). The QoS parameters of the service flows of 5G are, for example, DiffServ code point (DSCP) values. The EPS-bearer-level QoS of LTE is, for example, QoS class identifier (QCI) and allocation and retention priority (ARP). The mapping of DSCP values to EPS bearers may be performed one-to-one or n-to-one. The source ACS / eMME sends APN information including EPS-bearer-level QoS information to the target MME. The target MME sets up GTP tunnels for the UE according to the received APN information.
[0010] In addition, in the handover from LTE to 5G shown in Patent Document 1, the source MME of the LTE core (i.e., EPC) sends a forward relocation request including necessary bearer context information to the target ACS / eMME of the 5G core (NG Core). The target ACS / eMME maps the QCI values acquired from the LTE (i.e., source MME) to 5G QoS parameters (i.e., DSCP values) and provides them to a forwarding node (i.e., Mobility Gateway Access Router (M-GW / AR) or Mobility Gateway Edge Router (M-GW / ER)) of the 5G core (NG Core). As a result, the Target ACS / eMME sets up at least one Generic Routing Encapsulation (GRE) tunnel for transmitting service flows (i.e., IP packets) of the UE. [Prior art documents] [Patent documents]
[0011] [Patent Document 1] International Publication No. 2015 / 160329 [Non-patent literature]
[0012] [Non-Patent Document 1] 3GPP TR 23.799 V0.6.0 (2016-07) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14)”, July 2016 Summary of the Invention [Problem to be solved by the invention]
[0013] The present inventors have studied handover between the NG System (5G) and the LTE System and found several problems. For example, Fig. 4 of Patent Document 1 describes that the handover procedure from the NG System (5G) to the LTE System is realized by modifications of the LTE S1-based handover. However, Patent Document 1 does not describe that the handover procedure between the NG System (5G) and the LTE System includes the transfer of a handover signaling message on the direct inter-base station interface.
[0014] Therefore, one of the objectives to be achieved by the embodiments disclosed in this specification is to provide an apparatus, a method, and a program that contribute to providing an Inter-RAT handover procedure involving the transfer of a handover signaling message on a direct inter-base station interface. It should be noted that this objective is only one of the objectives to be achieved by the embodiments disclosed in this specification. Other objectives or problems and novel features will become apparent from the description of this specification or the accompanying drawings. [Means for solving the problem]
[0015] In one aspect, a target Radio Access Network (RAN) node associated with a second network includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive a handover request message from a source RAN node in the first network on a direct interface requesting a handover of a wireless terminal from a first network to the second network, receive at least one of slice information and flow information from a core network in response to receiving the handover request message, and control communication of the wireless terminal based on at least one of the slice information and the flow information, the slice information relating to a network slice in the second network to which the wireless terminal is attached, and the flow information relating to at least one session established in the second network as a bearerless network for transporting at least one packet flow of the wireless terminal.
[0016] In one aspect, a source Radio Access Network (RAN) node associated with a first network includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to determine a handover of a wireless terminal from the first network to a second network, and in response to the handover determination, to transmit a handover request message to a target RAN node in the second network over a direct interface, requesting a handover of the wireless terminal to the second network. The at least one processor is further configured to receive a handover request acknowledge message from the target RAN node over the direct interface, the handover request acknowledge message including a transparent container, and to transmit a mobility command message to the wireless terminal, the mobility command message including the transparent container and indicating a handover to the second network. The transparent container includes radio resource configuration information required for the wireless terminal to establish a radio connection associated with the second network. The radio resource configuration information includes at least one of (a) first radio resource configuration information generated based on slice information regarding a network slice in the second network to which the wireless terminal connects, and (b) second radio resource configuration information generated based on flow information regarding at least one session established in the second network as a bearerless network to transfer at least one packet flow of the wireless terminal.
[0017] In one aspect, a wireless terminal includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive, in a handover from a first network to which the wireless terminal is connected to a second network, a handover-related message including at least one of slice information regarding a network slice in the second network and radio resource configuration information based on the network slice in the second network from a Radio Access Network (RAN) node of the first network.
[0018] In one aspect, a core network node includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to, upon handover of a wireless terminal from a first network to a second network, send slice information regarding a network slice in the second network to which the wireless terminal is connected to a target Radio Access Network (RAN) node associated with the second network.
[0019] In one aspect, a method in a target Radio Access Network (RAN) node associated with a second network includes: receiving a handover request message from a source RAN node in the first network over a direct interface, the handover request message requesting a handover of the wireless terminal from a first network to the second network; receiving at least one of slice information and flow information from a core network in response to receiving the handover request message; and Controlling communication of the wireless terminal based on at least one of the slice information and the flow information; The slice information relates to a network slice in the second network to which the wireless terminal is connected, and the flow information relates to at least one session established in the second network as a bearerless network for transporting at least one packet flow of the wireless terminal.
[0020] In one aspect, a method in a source Radio Access Network (RAN) node associated with a first network includes: determining a handover of the wireless terminal from the first network to a second network; transmitting, in response to the handover decision, a handover request message over a direct interface to a target RAN node in the second network requesting handover of the wireless terminal to the second network; receiving a handover request acknowledge message from the target RAN node over the direct interface, the handover request acknowledge message including a transparent container; and sending a mobility command message to the wireless terminal, the mobility command message including the transparent container and indicating a handover to the second network; The transparent container includes radio resource configuration information required for the wireless terminal to establish a wireless connection associated with the second network. The radio resource configuration information includes at least one of (a) first radio resource configuration information generated based on slice information regarding a network slice in the second network to which the wireless terminal connects, and (b) second radio resource configuration information generated based on flow information regarding at least one session established in the second network as a bearerless network to transfer at least one packet flow of the wireless terminal.
[0021] In one aspect, the program comprises instructions (software code) for causing the computer to carry out the method according to the above aspect when the program is loaded into the computer. Effect of the Invention
[0022] According to the above-mentioned aspects, it is possible to provide an apparatus, a method, and a program that contribute to providing an Inter-RAT handover procedure involving the transfer of a handover signaling message on a direct inter-base station interface. [Brief description of the drawings]
[0023] [Figure 1] FIG. 1 illustrates an example of a wireless communication network according to some embodiments. [Figure 2A] FIG. 2 is a sequence diagram showing an example of an inter-RAT handover procedure from an LTE system to an NG system according to the first embodiment. [Figure 2B] FIG. 2 is a sequence diagram showing an example of an inter-RAT handover procedure from an LTE system to an NG system according to the first embodiment. [Figure 3A] FIG. 2 is a sequence diagram showing an example of an inter-RAT handover procedure from an LTE system to an NG system according to the first embodiment. [Figure 3B] FIG. 2 is a sequence diagram showing an example of an inter-RAT handover procedure from an LTE system to an NG system according to the first embodiment. [Figure 4] 1 is a flowchart illustrating an example of a method performed by a target NR NodeB (NR NB) according to a first embodiment. [Diagram 5] 5 is a flowchart showing an example of a method performed by a source LTE eNB according to the first embodiment. [Figure 6] 5 is a flowchart showing an example of a method performed by a core network according to the first embodiment. [Figure 7]5 is a flowchart showing an example of a method performed by a wireless terminal according to the first embodiment. [Figure 8] FIG. 11 is a sequence diagram showing an example of an inter-RAT handover procedure from an LTE system to an NG system according to the second embodiment. [Figure 9A] FIG. 11 is a sequence diagram showing an example of an inter-RAT handover procedure from an LTE system to an NG system according to the second embodiment. [Figure 9B] FIG. 11 is a sequence diagram showing an example of an inter-RAT handover procedure from an LTE system to an NG system according to the second embodiment. [Figure 10A] FIG. 13 is a sequence diagram showing an example of an inter-RAT handover procedure from an NG system to an LTE system according to the third embodiment. [Figure 10B] FIG. 13 is a sequence diagram showing an example of an inter-RAT handover procedure from an NG system to an LTE system according to the third embodiment. [Figure 11A] FIG. 13 is a sequence diagram showing an example of an inter-RAT handover procedure from an NG system to an LTE system according to the third embodiment. [Figure 11B] FIG. 13 is a sequence diagram showing an example of an inter-RAT handover procedure from an NG system to an LTE system according to the third embodiment. [Figure 12] FIG. 13 is a diagram illustrating an example of the configuration of a wireless communication network according to a fourth embodiment. [Figure 13] A sequence diagram showing an example of an intra-NR handover procedure according to the fourth embodiment. [Figure 14] A sequence diagram showing an example of an intra-NR handover procedure according to the fourth embodiment. [Figure 15] A sequence diagram showing an example of an intra-NR handover procedure according to the fourth embodiment. [Figure 16]A sequence diagram showing an example of an intra-NR handover procedure according to the fourth embodiment. [Figure 17] A sequence diagram showing an example of an intra-NR handover procedure according to the fourth embodiment. [Figure 18] A sequence diagram showing an example of an intra-NR handover procedure according to the fourth embodiment. [Figure 19] FIG. 2 is a block diagram illustrating an example configuration of a wireless terminal according to some embodiments. [Figure 20] FIG. 2 is a block diagram illustrating an example configuration of a base station according to some embodiments. [Figure 21] FIG. 2 is a block diagram illustrating an example configuration of a base station according to some embodiments. [Figure 22] FIG. 2 is a block diagram illustrating an example configuration of a core network node according to some embodiments. [Figure 23A] A figure showing an example of the format of a Mobility from EUTRA command message. [Figure 23B] A figure showing an example of the format of a Mobility from EUTRA command message. [Figure 24] A figure showing an example of the format of an NR Handover Request message. [Diagram 25] A figure showing an example of the format of UE Context Information. [Figure 26] A figure showing an example of the format of an NR Handover Request Acknowledge message. [Figure 27] A figure showing an example of the format of an NR Handover Request Acknowledge message. [Figure 28] FIG. 13 is a diagram showing an example of the format of an NG Core Context. [Figure 29] FIG. 13 is a diagram illustrating an example of a format of Slice Information. [Diagram 30] FIG. 13 is a diagram illustrating an example of a format of Flow Information. [Diagram 31] FIG. 13 is a diagram illustrating an example of a format of a Session Endpoint ID. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0024] In the following, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and duplicated descriptions will be omitted as necessary for clarity of explanation.
[0025] The multiple embodiments described below can be implemented independently or in appropriate combination. These multiple embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different objects or problems and provide different effects.
[0026] <First embodiment> FIG. 1 illustrates an example of the configuration of a wireless communication network according to some embodiments including the present embodiment. In the example of FIG. 1, the wireless communication network includes a wireless terminal (UE) 1, an LTE base station (i.e., eNB) 2, a New Radio (NR) base station (i.e., NR NodeB (NR NB)) 3, and a NextGen (NG) Core 5. The LTE eNB2 is connected to the NG Core 5. That is, the LTE eNB2 is connected to an MME or a control node (i.e., Control Plane Function (CPF) node) having at least a part of the function of an MME in the NG Core 5 via a control plane interface (e.g., NG2 interface), and is connected to a Serving Gateway (S-GW) or a data node (i.e., User Plane Function (UPF) node) having at least a part of the function of an S-GW in the NG Core 5 via a user plane interface (e.g., NG3 interface). In this way, the LTE eNB2 is enhanced to be connected to the NG Core 5, and may be referred to as an eLTE eNB.
[0027] Similarly, the NR NB3 may be connected to one or more CPF nodes in the NG Core5 via a control plane interface (e.g., NG2 interface). The NR NB3 may also be connected to one or more UPF nodes in the NG Core5 via a user plane interface (e.g., NG3 interface). Furthermore, the UE1 may be connected to one or more CPF nodes in the NG Core5 via a control plane interface (e.g., NG1 interface). Here, the NG1 interface is defined as a logical interface for transferring NAS layer information, and the transmission of the NAS layer information may be performed via the NG2 interface and the radio interface (NG Uu) between the NR NB3 and the UE1.
[0028] In some implementations, the NG Core5 may set up a virtualized network slice that provides logical EPC nodes and EPC functions. In some implementations, the E-UTRAN including the LTE eNB2 and the NG RAN including the NR NB3 may be connected to the same network slice. Alternatively, the E-UTRAN including the LTE eNB2 and the NG RAN including the NR NB3 may be connected to different network slices. UE1 has the capability of connecting to the LTE system provided by the LTE eNB2 and the NG Core5, and has the capability of connecting to the NextGen (NG) system provided by the NR NB3 and the NG Core5.
[0029] The LTE eNB2 is connected to the NR NB3 by a direct inter-base station interface 101. The direct inter-base station interface 101 is, for example, called an X3 interface. The direct inter-base station interface 101 is used for the transfer of at least signaling messages between the LTE eNB2 and the NR NB3. The direct inter-base station interface 101 may further be used for user packet transfer between the LTE eNB2 and the NR NB3. The control plane protocol structure and the user plane protocol structure of the direct inter-base station interface 101 may be similar to those of, for example, an X2 interface between LTE eNBs.
[0030] The NG System may include other interfaces in addition to the above-mentioned NG1, NG2, and NG3 interfaces. The interfaces are also called reference points. NG RANs (different NR NBs) may be connected via an NX2 interface. A CPF node having either or both a Mobility Management Function (MMF) and a Session Management Function (SMF) may be connected to a UPF node via a control plane interface (e.g., NG4 interface). Different UPF nodes may be connected via a user plane interface (e.g., NG9 interface). CPF nodes having different functions may be connected via a control plane interface. For example, a CPF node having an MMF and an SMF may be connected to a CPF node having a Policy Control Function (PCF) via a control plane interface (e.g., NG7 interface). A CPF node having an MMF and an SMF may be connected to a node having a Subscriber Data Management (SDM) function via a control plane interface (e.g., NG8 interface). A CPF node may be connected to a node having an Application Function (AF) function via a control plane interface (e.g., NG5 interface). A UPF node may be connected to an external or local Data Network (DN) via a user plane interface (e.g., NG6 interface). The SMF may include functions for authentication of users or terminals, and authorization of services or network slicing.Each of the above network nodes is also referred to as a network function (NF(s)), either individually or collectively.
[0031] In some implementations, the NG System, including the NR NB3 and NG Core5, supports data forwarding based on the flow-based QoS (or per-flow QoS) concept described above. The NG System, including the NR NB3 and NG Core5, may be further configured to support bearer-based forwarding using a bearer per QoS class and per PDU session. The NG System bearer may be established between a pair of Network Functions (NFs), for example, between the NR NB3 and a user plane function in the NG Core5, or between two user plane functions in the NG Core5. Alternatively, the NG System bearer may be established between UE1 and a user plane function in the NG Core5 via the NR NB3. The NG System bearer may be referred to as an NG-EPS-bearer, and the NG System radio access bearer may be referred to as an NG-RAB. The NG System bearer may be used to forward multiple packet flows (PDU flows).
[0032] The NG-RAB may be composed of a radio bearer set between UE1 (NG UE) and NR NB3, and a bearer (eg, NG3 bearer) set between NR NB3 and a user plane function in NG Core5 (eg, Edge Gateway (Edge GW)). The NG-EPS-bearer may be composed of a core network bearer (eg, NG9 bearer) set between the NG-RAB and the user plane function in NG Core5 (eg, between Edge GW and Data Network Gateway (DN GW)). The Edge GW is a gateway to the radio access network and corresponds to the user plane function of the S-GW in LTE. However, unlike the S-GW in LTE, in the NG System, UE1 may be connected to multiple Edge GWs. The DN GW is a gateway to an external network (ie, Data Network) and corresponds to the user plane function of the P-GW in LTE. Note that, like the P-GW in LTE, in the NG System, UE1 may be connected to multiple DN GWs.
[0033] More specifically, the NG-EPS-bearer may be configured between UE1 (NG UE) and a slice specific user plane function (Slice specific User plane NF (SUNF)) in NG Core5. The NG-RAB may be configured between UE1 (NG UE) and a common user plane function (Common User plane NF (CUNF)) in NG Core5. In this case, the CUNF provides the function of the Edge GW, and the SUNF provides the function of the DN GW. The CUNF may associate between the NG-RAB and a core network bearer (e.g., NG9 bearer). That is, the NG-EPS-bearer may be composed of the NG-RAB between UE1 (NG UE) and the CUNF, and the core network bearer (e.g., NG9 bearer) between the CUNF and the SUNF.
[0034] An NG System supporting bearer-based forwarding may further be configured to identify data flows (PDU flows) within a bearer for per-data-flow (PDU flow) QoS handling (e.g., packet discarding). For example, the NR NB3 may associate a bearer (e.g., NG3 bearer) established between the NR NB3 and the user plane function in the NG Core5 with a radio bearer, forward packets between the bearer (e.g., NG3 bearer) and the radio bearer, and further perform per-data-flow (PDU flow) QoS handling (e.g., packet discarding) within the bearer.
[0035] In addition, when (e) LTE eNB2 is connected to NG Core5 via the NG2 interface, a radio access bearer equivalent to an LTE EPS Radio Access Bearer (E-RAB) may be defined as an NG EPS Radio Access Bearer (NE-RAB), and a bearer equivalent to an LTE EPS bearer may be defined as an NG EPS bearer (NEPS bearer). The NE-RAB may be composed of a radio bearer established between UE1 and LTE eNB2, and a bearer (e.g., NG3 bearer) established between the LTE eNB2 and a user plane function (e.g., Edge GW or CUNF) in NG Core5. The NEPS bearer may be composed of a core network bearer (e.g., NG9 bearer) established between the NE-RAB and a user plane function (e.g., between an Edge GW and a DN GW, or between a CUNF and a SUNF) in NG Core5.
[0036] The LTE eNB2 connected to the NG System may be configured to identify a data flow (PDU flow) in the NE-RAB for QoS handling (e.g., packet discarding) per data flow (PDU flow). For example, the LTE eNB2 may associate a bearer (e.g., NG3 bearer) established between the LTE eNB2 and a user plane function in the NG Core5 with a radio bearer, perform packet forwarding between the bearer (e.g., NG3 bearer) and the radio bearer, and further perform QoS handling (e.g., packet discarding) per data flow (PDU flow) in the bearer.
[0037] This embodiment provides a method for handing over UE1 from an LTE system that does not support network slicing to an NG system that supports network slicing. Figures 2A and 2B show an example of a handover procedure of UE1 from the LTE system to the NG system in the example configuration of the wireless communication network shown in Figure 1. Figure 2A shows a preparation phase and an execution phase of the handover, and Figure 2B shows a completion phase of the handover.
[0038] The procedure shown in Figures 2A and 2B is similar to the LTE "X2-based handover" in that it involves the transfer of handover signaling messages over the direct base station interface 101 during the handover preparation phase (i.e., steps 202 and 203). However, if only the transfer of handover signaling messages over the direct base station interface 101 were performed, the NG RAN would lack the information required for the relocation of UE1 from the LTE system to the NG system. Therefore, in the procedure shown in Figures 2A and 2B, the handover completion phase is enhanced to include signaling between the NR NB3 and the NG Core5 (i.e., steps 207, 209, and 210) to obtain the information required for the relocation of UE1 from the LTE system to the NG system.
[0039] In step 201, UE1 is connected to LTE eNB2 and is in a connected state (ie, RRC_Connected). UE1 receives a measurement configuration from LTE eNB2, performs neighbor cell measurements including E-UTRAN (LTE) cells and NG-RAN cells and inter-RAT measurements according to the measurement configuration, and sends a measurement report to LTE eNB2. The measurement configuration is included in, for example, an RRC Connection Reconfiguration message transmitted from E-UTRAN to the UE.
[0040] In step 202, the LTE eNB2 determines an inter-RAT handover to a cell of the NR NB3. In response to the determination of the inter-RAT handover, the LTE eNB2 sends an NR Handover Request message to the target NR NB3 over the direct inter-base station interface 101 (eg, X3 interface).
[0041] The NR Handover Request message in step 202 may include a Handover Type Information Element (IE) indicating that the handover is from LTE to NR. The Handover Type IE is set to, for example, “LTEtoNR”.
[0042] Furthermore, the NR Handover Request message in step 202 may include a "NG EPS Radio Access Bearers (NE-RABs) To Be Setup List" information element (IE). The "NE-RABs To Be Setup List" IE indicates an identifier (i.e., NE-RAB ID) of each NE-RAB for UE1 and QoS parameters (e.g., QoS class identifier (QCI), Allocation and retention priority (ARP), Guaranteed Bit Rate (GBR) QoS information). The NextGen E-RAB (NE-RAB) is an E-RAB set up between UE1 and a User plane Function (e.g., Common User plane NF (CUNF)) in the NG Core 5 via an eLTE eNB extended to support an interface with the NG Core.
[0043] Furthermore, the NR Handover Request message of step 202 may include a “Handover Preparation Information to NR” information element (IE). For example, the “Handover Preparation Information to NR” IE may include assistance information to facilitate mapping of EPS bearers and packet flows (e.g., PDU flows or SDFs) for UE1. The assistance information may indicate identifiers of one or more SDFs or packet filters (e.g., SDF templates or TFTs) to be mapped to each EPS bearer. The assistance information may be sent from UE1 to LTE eNB2 in an RRC message. Furthermore, the assistance information may be transmitted as an information element (IE) including RRC layer parameters or as an RRC layer IE including NAS layer information (e.g., NAS Info IE).
[0044] Additionally or alternatively, the "Handover Preparation Information to NR" IE may include security-related information, including security parameters used by the target NR NB3 for the derivation of Access Stratum (AS) security keys. The security parameters include base keys (i.e., K-keys in LTE) for the derivation of security keys (temporary keys) used by the AS layer. eNBThe security parameters may further include UE security capabilities related to the NG RAT or the NG System. The UE security capabilities indicate the ciphering and integrity protection algorithms implemented in the UE1.
[0045] For example, similar to the existing X2 handover procedure, the source LTE eNB2 receives K eNB * is derived, {K eNB *, NCC} pair to the target NR NB3. The Next Hop parameter (NH) and the Next Hop Chaining Counter parameter (NCC) follow the vertical key derivation algorithm for the next hop K eNB Alternatively, the source LTE eNB2 derives the current K according to a horizontal key derivation algorithm. eNB From K eNB * is derived, {K eNB *, NCC} pair to target NR NB3.
[0046] Alternatively, the source LTE eNB2 may send the unused {NH, NCC} pair to the target NR NB3. In this case, the target NR NB3 derives a base key (i.e., K eNB ) and AS keys.
[0047] Furthermore, the NR Handover Request message in step 202 may include assistance data for network slicing. The "Assistance Data for Network Slicing" IE includes network slice assistance information, which is assistance information for facilitating network slicing. The network slice assistance information may indicate, for example, the type of UE1, a service desired by UE1, or an acceptable latency of UE1, or any combination thereof. Alternatively, some or all of the network slice assistance information may be included in the handover preparation information (or other information element) of the RRC container (RRC Context IE). Here, the network slice assistance information () may be generated by UE1, LTE eNB2, or an EPC network slice instance in NG Core5. For example, UE1 may send the network slice assistance information to LTE eNB2 in step 201. The network slice assistance information may be an information element (IE) or NAS information IE indicating parameters of the RRC layer, which may be included in a measurement report sent from UE1 to LTE eNB2.
[0048] In step 203, the target NR NB3 creates a UE context and allocates resources based on the NR Handover Request message. The target NR NB3 may determine admitted E-RABs based on the received “E-RABs To Be Setup List” IE. The target NR NB3 may determine a flow identifier (e.g., PDU flow ID) corresponding to each admitted E-RAB, endpoint information of the target NR NB3 for delivery of uplink (UL) PDUs, and endpoint information of the target NR NB3 for delivery of downlink (DL) PDUs. The endpoint information of the target NR NB3 for delivery of UL PDUs may be, for example, a UL GTP Tunnel Endpoint Identifier (TEID), or a UL endpoint ID or an Internet Protocol (IP) address, or both. Similarly, the endpoint information of the target NR NB3 for delivery of DL PDUs may be a DL GTP TEID, or a DL endpoint ID or an IP address, or both. The endpoint information for delivery of UL PDUs and DL PDUs is used for forwarding UL data and forwarding DL data, respectively.
[0049] Furthermore, if the NR Handover Request message of step 203 includes security related information, the target NR NB3 may operate as follows. As described above, the security related information includes security parameters for AS security. The target NR NB3 may select an AS security algorithm based on the UE security capabilities included in the security parameters. The AS security algorithm includes ciphering algorithms for Radio Resource Control (RRC) and User Plane (UP), and an integrity protection algorithm for RRC. Furthermore, the target NR NB3 derives temporary keys for RRC ciphering (encryption), UP ciphering (encryption), and RRC integrity protection using the selected security algorithm, based on a base key (i.e., K for LTE) derived from the security parameters. eNB The key may be derived from the
[0050] The target NR NB3 generates a Target To Source Transparent Container to be sent to the UE1. The Target To Source Transparent Container includes, for example, an RRC: Handover Command message (Handover Command To NR) including an RRC Connection Reconfiguration message and other RRC messages. The target NR NB3 then generates an acknowledgement (Handover Request Acknowledge) message to the handover request including the Target To Source Transparent Container. The target NR NB3 sends the NR Handover Request Acknowledge message to the source LTE eNB2 over the direct base station interface 101 (eg, X3 interface). The Target To Source Transparent Container includes, for example, radio resource configuration information (eg, radio parameters) set up by the target NR NB3, identifiers of the AS security algorithm selected by the target NR NB3, and an NCC value. The NR Handover Request Acknowledge message may further include the above-mentioned "NE-RABs Admitted list" information element (IE). The source LTE eNB2 starts data forwarding for the bearers or flows (PDU flow(s)) specified by the “NE-RABs Admitted list” IE.
[0051] In step 204, the source LTE eNB2 sends a Radio Resource Control (RRC) message containing a Handover Command message including the transparent container generated by the target NR NB3 to the UE1. The RRC message may be, for example, a Mobility from EUTRA command message or an RRC Connection Reconfiguration message.
[0052] In step 205, in response to receiving the RRC message containing the Handover Command message, UE1 moves to the target RAN (i.e., NG RAN) and performs handover according to the transparent container (e.g., radio resource configuration information, AS security algorithm, and NCC value) provided in the Handover Command message. That is, UE1 establishes a radio connection with the target NR NB3 associated with a bearer-less network (i.e., NG System). In step 206, UE1 sends a Handover Confirm for NR message to the target NR NB3 after successfully synchronizing to the target cell. The message in step 206 may be an NR RRC Connection Reconfiguration Complete message.
[0053] In step 207, when UE1 successfully accesses the target NR NB3, the target NR NB3 sends an NR Path Switch Request message to the NG Core 5 to inform that UE1 has changed cells and to request a path switch. The NR Path Switch Request message may include a Path Switch Type IE indicating that the path switch is from LTE to NR. The Path Switch Type IE is set to, for example, "LTEtoNR". Furthermore, the NR Path Switch Request message may include a list of EPS bearers of UE1 that have been switched to the cell of the target NR NB3.
[0054] In step 208, a control node (eg, CPF) in the NG Core 5 performs a bearerless session creation procedure. Specifically, the control node determines that a packet forwarding node (gateway) for UE1 needs to be relocated, and selects a target forwarding node (gateway) for the NG System in the NG Core 5. The target forwarding node (gateway) for the NG System is a node corresponding to the S-GW of LTE. The control node sends a Create Session Request message to the target forwarding node (gateway). The Create Session Request message may include information (eg, SDF templates, or Traffic Flow Templates (TFTs)) for identifying one or more service data flows associated with each EPS bearer context. For example, the information for identifying the one or more service data flows may be derived from a message (eg, Forward Relocation Request message) sent from an MME in a network slice instance corresponding to an EPC to which an LTE eNB2 is connected to a control node in a network slice instance corresponding to a pure NG Core to which an NR NB3 is connected. The target forwarding node (gateway) allocates its local resources and returns a Create Session Response message to the control node.
[0055] In addition, if the NG System supports bearer-based forwarding using a bearer per QoS class and per PDU session and relocation of the forwarding node is not required, the control node in the NG Core 5 may perform a bearer modification procedure instead of a session creation procedure in step 208.
[0056] Further, in step 208, a control node (e.g., CPF) in the NG Core 5 may select (reselect) a network slice to be connected to the UE 1 after the handover. The control node in the NG Core 5 may perform creation of the selected network slice instance. In one example, the control node in the NG Core 5 may select a network slice for the UE 1 based on the QoS required for the EPS bearer(s) or SDF(s) of the UE 1. Additionally or alternatively, the NG Core 5 may take into account network slice assistance information. The network slice assistance information assists the control node (e.g., CPF) in the NG Core 5 in selecting, configuring, or approving the network slice. The network slice assistance information may be generated by the UE 1, the LTE eNB 2, or an EPC network slice instance in the NG Core 5. For example, the NR Handover Confirm for NR message sent from UE1 to the target NR NB3 (step 206) may include network slice assistance information, and the target NR NB3 may include the received network slice assistance information in an NR Path Switch Request message (step 207).
[0057] The network slice support information may indicate, for example, the type of UE1 (eg, Device Type, UE Category), the access usage of UE1 (eg, UE Usage Type), the service type desired by UE1 (eg, Requested / Preferred Service Type, Multi-Dimensional Descriptor (MDD)), slice information selected by UE1 (eg, Selected Slice Type, Selected Slice Identity (ID), Selected Network Function (NF) ID), slice information previously approved by UE1 (eg, Authorized Slice Type, Authorized Slice ID, Authorized NF ID), and the tolerable latency of UE1 (eg, Allowed Latency, Tolerable Latency) or any combination thereof. The Service Type may indicate, for example, the type of Use Case (eg, enhanced Mobile Broad Band (eMBB), Ultra Reliable and Low Latency Communication (URLLC), or massive Machine Type Communication (mMTC), or equivalent). The Slice ID may indicate, for example, any one or any combination of slice instance information (Network Slice Instance (NSI) ID), dedicated network information (Dedicated Core Network (DCN) ID), and network domain name information (Domain Network Name (DNN) ID).The NF ID may indicate, for example, the identity (ID) of any one or any combination of a Common Network Function (CNF), a Common Control plane Function (CCNF), a Common User plane Function (CUNF), and a Data Network Gateway (DN GW).
[0058] In step 209, the control node in NG Core5 sends an NR Path Switch Request Acknowledge message to the target NR NB3. The NR Path Switch Request Acknowledge message may include NG Core Information. The NG Core Information may include Flow Information or Slice Information or both. The Flow Information is related to at least one session (i.e., PDU session(s)) established in the bearer-less network (i.e., NG system) for forwarding at least one packet flow (i.e., PDU flow(s)) of UE1. The Flow Information includes a Flow Identifier (e.g., PDU flow ID), an address (Transport Layer Address) of a forwarding node in NG Core5 and a Session Endpoint Identifier (SEID) of the uplink (UL), and flow QoS parameters. The Session Endpoint Identifier (SEID) may be, for example, a Tunnel Endpoint Identifier (TEID) or a Network Function (Node) Identifier (NF ID). The TEID may be, for example, a GTP-TEID or a GRE-TEID.
[0059] The flow information may further indicate mapping of EPS bearers and PDU flows for UE1. For example, the flow information may indicate one or more SDFs mapped to each EPS bearer of UE1 and a flow identifier (e.g., PDU flow ID) assigned to each of the one or more SDFs. Furthermore, the flow information may include priority indicator, flow type indicator, or flow class. The priority information may indicate, for example, a relative priority among multiple flows, or an absolute priority of each flow. The flow type information may indicate, for example, which Use Case or service the flow corresponds to. Furthermore, the flow class may indicate, for example, one of predefined flow types (e.g., loss-less, delay tolerant, delay sensitive, mission critical).
[0060] The slice information includes at least one of information regarding the network slice of NG Core 5 to which UE1 will connect (be connected) after handover, information regarding the network slice of NG Core 5 to which UE1 is allowed to connect, and information regarding the network slice of NG Core 5 to which UE1 can connect.
[0061] The slice information may include identification information of a slice (Network Slice: NS) determined (selected) for UE1, identification information of a network node (NF), or type information of a slice, or any combination thereof. The slice identification information may be, for example, any one or any combination of a Slice ID, an NSI ID, an MDD, a DCN ID, and a DNN. The network node identification information may include, for example, any one or any combination of an NF ID, a CNF ID, a CCNF ID, a Slice specific Control plane NF (SCNF) ID, a CUNF ID, a Slice specific User plane NF (SUNF) ID, a UPF ID, and a DN GW ID. The slice type information may include, for example, a Slice Type indicating any one or any combination of a Service Type, a Service Category, and a Use Case. Additionally or alternatively, the slice type information may include a Tenant ID indicating a Use Case or a contract type (Subscription Group, e.g., home UE or roaming UE). The slice type information may include an MDD including a Slice Type and a Tenant ID as elements. In addition, the content of the above-mentioned slice information may be specified for each network slice. Therefore, when UE1 is connected to multiple network slices at the same time, the slice information may include multiple sets of information corresponding to the number of network slices to which UE1 is connected.
[0062] The slice information may further include a mobility class or a session class, or both. The mobility class may indicate one of predefined mobility levels (e.g., high mobility, low mobility, no mobility). For example, high mobility means that the geographical area in which the network slice supports mobility for UE1 (allows mobility for UE1) is wider than that of low mobility, and the requirement for continuity of service (PDU session) during handover is high. No mobility means that the network slice supports mobility for UE1 only within a very limited geographical area. The mobility class may be specified per UE or per network slice. The session class may indicate one of predefined session types (e.g., Session pre-setup, Session post-setup, No PDU session). For example, Session pre-setup may indicate that a PDU session is required to be established before the UE completes moving to a target (cell, beam, or other area) in order to maintain a service (PDU Session) according to mobility like an existing handover. In contrast, Session post-setup may indicate that a PDU session may be established after the UE moves to the target. A Session Class may be specified for each PDU session. Mobility Class and Session Class may be included in Slice Type. In other words, Slice Type may include multiple attributes including Mobility Class and Session Class. Note that the above-mentioned flow information may include Mobility Class, Session Class, or both.
[0063] In step 210, the target NR NB3 sends an NR DL Information Transfer message to UE1 carrying NAS information (eg, slice information, and flow information) received from the NG Core5.
[0064] After the handover is completed according to the procedure shown in Figures 2A and 2B, the following paths may be used for data forwarding of UE1. If the NG System including the NR NB3 and NG Core5 supports bearer-based forwarding in the NG Core5 and a bearer (e.g., NG-EPS-bearer) is used for UE1 after handover, for example, the uplink path and the downlink path may include a path (e.g., GTP tunnel or GRE tunnel) between the (source or old) S / P-GW and the (target or new) User plane Function (e.g., CUNF) in the NG Core5. That is, the S / P-GW may forward downlink data to the User plane Function (e.g., CUNF) in the NG Core5, and the User plane Function (e.g., CUNF) in the NG Core5 may forward uplink data to the S / P-GW.
[0065] On the other hand, if a bearer (e.g., NG-EPS-bearer) is not used for UE1 after handover, for example, a CUNF may mediate between a (source or old) S / P-GW and a (target or new) User plane Function (e.g., SUNF with NW Slicing functionality). That is, the S / P-GW may forward downlink data to a CUNF in NG Core5, and the CUNF may forward the downlink data to another UNF with per-flow control functionality. Alternatively, data may be forwarded directly between the S / P-GW and the SUNF without going through the CUNF. The data forwarding path after handover described here may also be used in other handover procedures described below.
[0066] 3A and 3B show another example of a handover procedure of UE1 from the LTE System to the NG System in the configuration example of the wireless communication network shown in FIG. 1. FIG. 3A shows a handover preparation phase and an execution phase, and FIG. 3B shows a handover completion phase. In the procedure of FIG. 2A and FIG. 2B already described, the target NR NB3 receives core network information (e.g., flow information or slice information or both) from the NG Core5 in the handover completion phase (step 209) after UE1 connects to the target NR NB3. In contrast, in the procedure shown in FIG. 3A and FIG. 3B, the target NR NB3 receives core network information (e.g., flow information or slice information or both) from the NG Core5 in the handover preparation phase (step 304) before the source LTE eNB2 issues a handover instruction to UE1. The following mainly describes this difference.
[0067] The processes of steps 301 and 302 are similar to the processes of steps 201 and 202 in Fig. 2A. In step 303, the target NR NB3 sends a Handover Preparation Request message to the NG Core5 in response to receiving the NR Handover Request message (step 302).
[0068] The Handover Preparation Request message of step 303 may include a Handover Type IE indicating that the handover is from LTE to NR. The Handover Type IE is set to, for example, "LTEtoNR". Furthermore, the Handover Preparation Request message may include a list of NG EPS bearers of UE1 to be switched to the cell of the target NR NB3.
[0069] In step 304, the NG Core 5 determines that the type of handover is an Inter-RAT handover to an NR (or NG System) based on the received Handover Preparation Request message. In addition, the NG Core 5 sends a Handover Preparation Request Acknowledge message to the target NR NB3, which includes core network information or security-related information or both. The core network information and security-related information are used by the target NR NB3 and UE1 to implement radio resource configuration and security-related configuration for communicating with UE1 in the NG system. Some specific examples of core network information are described below.
[0070] In one example, the core network information may include slice information. The slice information may include at least one of information on a network slice of the NG Core5 to which the UE1 is connected after the handover, information on a network slice of the NG Core5 to which the UE1 is allowed to connect, and information on a network slice of the NG Core5 to which the UE1 can connect. A control node (e.g., CPF) in the NG Core5 determines (selects) a network slice to which the UE1 is to be connected after the handover. In one example, the control node (CPF) in the NG Core5 may select a network slice for the UE1 based on the QoS required for the EPS bearer(s) or SDF(s) of the UE1. Additionally or alternatively, the NG Core5 may consider network slice assistance information. The network slice assistance information assists the control node (e.g., CPF) in the NG Core5 in selecting, configuring, or approving the network slice. The network slice assistance information may be generated by the UE1, the LTE eNB2, or an EPC network slice instance in the NG Core5. For example, UE1 may send network slice assistance information to LTE eNB2 in step 301. The network slice assistance information may be NAS information and may be included in a measurement report sent from UE1 to LTE eNB2. In step 302, the source LTE eNB2 may send the network slice assistance information received from UE1 to the target NR NB3.
[0071] In another example, the core network information may include flow information. The flow information is related to at least one session (i.e., PDU session(s)) established in the bearer-less network (i.e., NG system) for forwarding at least one packet flow (i.e., PDU flow(s)) of UE1. For each packet flow (i.e., PDU flow) of UE1, the flow information includes a flow identifier (e.g., PDU flow ID), an address of a forwarding node in NG Core5 and an uplink (UL) Session Endpoint Identifier (SEID), and flow QoS parameters. The Session Endpoint Identifier (SEID) may be, for example, a Tunnel Endpoint Identifier (TEID), or a Network Function (Node) Identifier (NF ID). The TEID may be, for example, a GTP-TEID or a GRE-TEID.
[0072] The flow information may further indicate a mapping of EPS bearers and PDU flows for UE1. For example, the flow information may indicate one or more SDFs mapped to each EPS bearer of UE1 and a flow identifier (e.g., PDU flow ID) assigned to each of the one or more SDFs. Furthermore, the flow information may include a priority indicator, a flow type indicator, or a flow class.
[0073] The security-related information may also include Non-Access Stratum (NAS) security configuration information used between the NG Core 5 and the UE 1 in the NG System. The NAS security configuration information includes, for example, NAS security algorithms including ciphering and integrity protection. The NAS security configuration information may be a NAS Security Transparent Container IE. That is, the NAS security configuration information is transparently sent from the target NR NB 3 to the UE 1 via the source LTE eNB 2.
[0074] The security related information further includes security parameters used by the target NR NB3 for the derivation of Access Stratum (AS) security keys. The security parameters include base keys (i.e., K eNB The base key includes a set of parameters (e.g., {NH,NCC} pair) for deriving the base key, where the Next Hop parameter (NH) and the Next Hop Chaining Counter parameter (NCC) are derived according to the vertical key derivation algorithm. eNB The security parameters may further include UE security capabilities related to the NG RAT or the NG System. The UE security capabilities indicate the ciphering and integrity protection algorithms implemented in the UE1.
[0075] The core network information included in the Handover Preparation Request Acknowledge message in step 304 may include either one or both of the two examples mentioned above (ie, slice information and flow information).
[0076] In step 305, the target NR NB3 creates a UE context and allocates resources in response to receiving the Handover Preparation Request Acknowledge message containing core network information or security related information or both.
[0077] When the core network information included in the Handover Preparation Request Acknowledge message includes slice information, the target NR NB3 may operate as follows. The target NR NB3 may perform admission control based on the core network information including the slice information. For example, the target NR NB3 may determine whether to accept a bearer or a flow for each bearer or flow. Additionally or alternatively, the target NR NB3 may perform admission control for each network slice to which UE1 connects based on the slice information. At this time, the NR NB3 may determine whether it is possible to accept each network slice. If there is a network slice that is not possible (or not acceptable), the NR NB3 may map the network slice to a specific network slice (e.g., a default network slice) or connect the network slice to a specific NF (e.g., a CUPF). Alternatively, the NR NB3 may determine failure to accept the network slice.
[0078] Additionally or alternatively, the target NR NB3 may generate radio resource configuration information (e.g., radio parameters) required for UE1 to establish a radio connection (e.g., RRC connection, radio bearer) associated with an NG System supporting network slicing based on the slice information (or may derive from the slice information). The radio resource configuration information may include at least one parameter included in the slice information.
[0079] The radio resource configuration information derived from the slice information may include per-network slice (or per-use case) radio (or RAN) parameters. The use cases include, for example, enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC). The per-network slice (or per-use case) radio parameters may be basic physical channel parameters or basic Layer 2 / Layer 3 (L2 / L3) configuration. The basic physical channel parameters may include, for example, a frame / subframe structure, a Transmission Time. Interval (TTI) length, a subcarrier spacing, and a Physical Random Access Channel (PRACH) resource. The PRACH resource may be a preamble index or time / frequency resources, or both. The basic L2 / L3 configuration may include, for example, a frame / subframe pattern, and an L2 protocol sublayer configuration (e.g., PDCP config, RLC config, or MAC config).
[0080] Additionally or alternatively, in RRC layer signaling that specifies (indicates) radio resource configuration information derived from slice information, at least any of the message structure, the format of information elements (IEs), parameter values, and the targets of encoding and decoding of ASN.1 (Abstract Syntax Notation One), which indicates the structural definition of information, may be different for each slice.
[0081] If the core network information included in the Handover Preparation Request Acknowledge message includes flow information, the target NR NB3 may operate as follows. The target NR NB3 may take the flow information into consideration for generating a UE context and radio resource configuration information. Specifically, the target NR NB3 may create a UE context including information on packet flows (i.e., PDU flow(s)) and a security context based on the flow information. Furthermore, the target NR NB3 may generate (or derive from) radio resource configuration information required for UE1 to establish a radio connection (e.g., RRC connection, radio bearer) associated with a bearer-less network (i.e., NG System) based on the flow information. The radio resource configuration information may include at least one parameter included in the flow information. The radio resource configuration information may include system information (System Information Block: SIB) in a cell (or mobility area, beam coverage area) of the target NR NB3, a radio resource configuration common between UEs (Common Resource Configuration), or a radio resource configuration dedicated to a UE (Dedicated Resource Configuration). Furthermore, the radio resource configuration information may include information indicating mapping between a bearer (e.g., EPS bearer, Data Radio Bearer (DRB)) in the cell of the source LTE eNB2 and a flow (e.g., PDU flow) established in the cell of the target NR NB3.
[0082] As previously described, the NG System, including the NR NB3 and NG Core5, may be configured to support bearer-based forwarding using bearers per QoS class and per PDU session, and may be configured to identify data flows (PDU flows) within a bearer for per-data-flow (PDU flow) QoS handling (e.g., packet discarding). For example, the NR NB3 may associate a bearer (e.g., NG3 bearer) established between the NR NB3 and a user plane function in the NG Core5 with a radio bearer, forward packets between the bearer (e.g., NG3 bearer) and the radio bearer, and further perform QoS handling (e.g., packet discarding) for each data flow (PDU flow) within the bearer.
[0083] In this case, the above-mentioned flow information may indicate an association between a bearer (e.g., NG-RAB or NG3 bearer) for UE1 and one or more packet flows (i.e., PDU flow(s)) of UE1 transferred via the bearer. In other words, a control node (e.g., CPF) in the NG Core5 may send flow information to the NR NB3 to inform the NR NB3 of an association between a bearer (e.g., NG-RAB or NG3 bearer) for UE1 and one or more packet flows (i.e., PDU flow(s)) of UE1 transferred via the bearer. The NR NB3 may receive the flow information from the control node in the NG Core5 and perform QoS handling (e.g., packet discarding) for each data flow (PDU flow) in a bearer (e.g., NG3 bearer) established between the NR NB3 and the user plane function in the NG Core5 according to the flow information.
[0084] If the Handover Preparation Request Acknowledge message includes security related information, the target NR NB3 may operate as follows. As described above, the security related information includes NAS security configuration information (NAS Security Transparent Container IE) and security parameters for AS security. The target NR NB3 may include the NAS security configuration information (NAS Security Transparent Container IE) in a transparent container sent to UE1. Additionally or alternatively, the target NR NB3 may select an AS security algorithm based on the UE security capabilities included in the security parameters. The AS security algorithm includes ciphering algorithms for Radio Resource Control (RRC) and User Plane (UP), and an integrity protection algorithm for RRC. Furthermore, the target NR NB3 may generate temporary keys for RRC ciphering (encryption), UP ciphering (encryption), and RRC integrity protection using the selected security algorithm, based on the base key (i.e., K for LTE) derived from the security parameters. eNB The key may be derived from the
[0085] The target NR NB3 generates a Target To Source Transparent Container (RRC Connection Reconfiguration) to be sent to UE1. The Target To Source Transparent Container includes, for example, a Handover Command message including an RRC Connection Reconfiguration message and other RRC messages. The target NR NB3 then generates an acknowledgment (NR Handover Request Acknowledge) message to the handover request including the Target To Source Transparent Container and core network context information (NG Core Context IE) including core network information. The target NR NB3 sends the NR Handover Request Acknowledge message to the source LTE eNB2 over the direct base station interface 101 (e.g., X3 interface). The Target To Source Transparent Container includes, for example, radio resource configuration information (e.g., radio parameters) set up by the target NR NB3, identifiers of the AS security algorithm selected by the target NR NB3, and NAS security configuration information. Note that the core network context information (NG Core Context) may be transmitted to UE1 transparently to the source LTE eNB2. Additionally or alternatively, some or all of the core network context information may be encapsulated in a Target To Source Transparent Container. The NR Handover Request Acknowledge message may further include the above-mentioned "NE-RABs Admitted list" information element (IE). The source LTE eNB2 starts data forwarding for the bearers or flows (PDU flow(s)) specified by the "NE-RABs Admitted list" IE.
[0086] The process of step 306 is the same as the process of step 204 in Fig. 2A. In step 307, in response to receiving the RRC message containing the Handover Command message, UE1 moves to the target RAN (i.e., NG RAN) and performs handover according to the transparent container (e.g., radio resource configuration information, AS security algorithm, and NAS security configuration information) provided in the Handover Command message. The process of step 308 is the same as the process of step 206 in Fig. 2A.
[0087] In step 309, the NG Core 5 performs a bearerless session creation procedure or a bearer modification procedure. In other words, the control node in the NG Core 5 initiates a bearerless session creation procedure or a bearer modification procedure for the UE 1 in response to receiving the Handover Preparation Request message in step 303. That is, the control node in the NG Core 5 initiates a bearerless session creation procedure or a bearer modification procedure for the UE 1 prior to a path switch request from the target NR NB 3 (step 310). The creation or bearer modification of the bearerless session in step 309 may be performed in the same manner as that in step 208 of FIG. 2B.
[0088] In step 310, the target NR NB3 sends an NR Path Switch Request message to the NG Core5. In step 311, the control node in the NG Core5 completes the Inter-RAT handover procedure by performing a flow modification procedure. For example, the control node in the NG Core5 may send a Modify Flow Request message per session (ie, PDU session) to the forwarding node in the NG Core5. The Modify Flow Request message may include a flow identifier (eg, PDU flow ID), as well as the address of the target NR NB3 and a downlink (DL) Session Endpoint Identifier (SEID). The Session Endpoint Identifier (SEID) may be, for example, a Tunnel Endpoint Identifier (TEID). The forwarding node in the NG Core5 may return a Modify Flow Response message to the control node in the NG Core5. In step 312, the control node in the NG Core5 sends an NR Path Switch Request Acknowledge message to the target NR NB3.
[0089] 4 is a flow chart illustrating an example of a method (process 400) performed by a target NR NB3. In step 401, the target NR NB3 receives a Handover Request message from a source LTE eNB2 over the direct base station interface 101. The Handover Request message is related to a handover of UE1 from the LTE system to the NG system. Step 401 corresponds, for example, to step 202 of FIG. 2A or step 302 of FIG. 3A.
[0090] In step 402, the target NR NB3 receives slice information or flow information or both from the core network (ie, NG Core5). Step 402 corresponds, for example, to step 209 in Fig. 2B or step 304 in Fig. 3A.
[0091] In step 403, the target NR NB3 controls the communication of UE1 based on at least one of slice information and flow information. For example, the target NR NB3 may generate radio resource configuration information based on at least one of slice information and flow information, and send the radio resource configuration information to UE1. For example, the target NR NB3 may select a network slice to send a control plane message related to UE1 based on the slice information. For example, the target NR NB3 may forward UL user data (PDU flows) of UE1 to NG Core5 based on endpoint information included in the flow information. For example, the target NR NB3 may perform resource scheduling for UE1 based on flow QoS parameters included in the flow information.
[0092] 5 is a flow chart showing an example of a method (process 500) performed by a source LTE eNB2. In step 501, the source LTE eNB2 sends a Handover Request message to a target NR NB3 over the direct inter-base station interface 101. The Handover Request message is related to a handover of UE1 from the LTE system to the NG system. Step 501 corresponds, for example, to step 202 in FIG. 2A or step 302 in FIG. 3A.
[0093] In step 502, the source LTE eNB2 receives a Handover Request Acknowledge message carrying a transparent container (RRCConnectionReconfiguration) from the target NR NB3 over the direct base station interface 101. Step 502 corresponds, for example, to step 203 in Fig. 2A or step 305 in Fig. 3A. The transparent container carries, for example, radio resource configuration information set up by the target NR NB3, identifiers of the AS security algorithm selected by the target NR NB3, and an NCC value or NAS security configuration information.
[0094] In step 503, the source LTE eNB2 sends a mobility command message (e.g., Handover Command message) including the transparent container received from the target NR NB3 and indicating handover to the bearerless network to the UE1. Step 503 corresponds to step 204 in FIG. 2A or step 306 in FIG. 3A.
[0095] FIG. 6 is a flow chart showing an example of a method (process 600) performed by a core network (i.e., NG Core 5). The process of FIG. 6 may be performed by one control node in the NG Core 5, or may be performed by two control nodes (i.e., source MME and target control node) in the NG Core. In step 601, the NG Core 5 receives a message (e.g., Handover Preparation Request message or NR Path Switch Request message) indicating a handover or path switch from the LTE system to the NG system from the target NR NB 3. Step 601 corresponds to step 207 in FIG. 2B or step 303 in FIG. 3A.
[0096] In step 602, the NG Core 5 sends slice information or flow information or both to the target NR NB 3. Step 602 corresponds, for example, to step 209 in Fig. 2B or step 304 in Fig. 3A.
[0097] FIG. 7 is a flow chart showing an example of a method (process 700) performed by UE1. In step 701, UE1 receives a mobility command message (e.g., Handover Command message) from a source LTE eNB2. The mobility command message includes a transparent container (RRCConnectionReconfiguration) from a target NR NB3. The transparent container includes, for example, radio resource configuration information, AS security algorithm, and NCC value or NAS security configuration information. Step 701 corresponds, for example, to step 204 in FIG. 2A or step 306 in FIG. 3A.
[0098] In step 702, UE1 establishes a wireless connection with a target NR NB3 associated with the NG System according to information included in the received transparent container. Step 702 corresponds to, for example, steps 205 and 206 in FIG. 2A or steps 307 and 308 in FIG. 3A.
[0099] In this embodiment, the network may allow UE1 to know in advance whether the handover target cell (NR cell) supports network slicing. For example, the NR NB3 may broadcast network slicing support information that explicitly or implicitly indicates that network slicing is supported in the NR cell (or that a connection to an NG core capable of network slicing is possible) as system information (e.g., System Information Block Type-x: SIBx. Eg, x = 1). The explicitly transmitted network slicing support information may further include a supported service type (e.g., Supported Service Type) or a supported slice type (e.g., Supported Slice Type) to indicate a supported network slice. On the other hand, the implicitly transmitted network slicing support information may include information on a radio resource configuration that differs for each network slice. UE1 may understand that network slicing is supported in the cell by recognizing that at least a part of the received radio resource configuration is specified for each network slice. The information on the radio resource configuration may include physical resource configuration information or system configuration information, or both. The physical resource configuration information may include at least one of code, time, frequency, and RACH preamble sequence (group). The system configuration information may include at least one of subcarrier spacing, sampling rate, TTI, and subframe / frame format type. The network slicing support information may be transmitted as NAS layer information or AS layer information. In the former case, UE1 forwards the information received at the AS layer (RRC) to the NAS layer.
[0100] The detailed handover procedure from the LTE system to the NG system according to the present embodiment may be, for example, the specific example described above, but is not limited thereto. For example, the message names shown in the above-described handover procedure examples are merely examples. The above-described handover procedure examples may have different message orders, may omit some messages, or may include additional messages.
[0101] As can be understood from the above description, some of the handover procedures from the LTE System to the NG System described in this embodiment are Inter-RAT handover procedures involving the transfer of handover signaling messages on a direct inter-base station interface. In these handover procedures, the target NR NB3 is configured to receive slice information and / or flow information from the core network (i.e., NG Core5) and use the information to control the communication of UE1, so that the target NR NB3 can contribute to continuing the communication of UE1 in a connected state that has been handed over from the LTE System to the NG System.
[0102] <Second embodiment> This embodiment provides a modified example of the handover method of UE1 from the LTE System to the NG System according to the first embodiment. Figure 8 shows an example of a handover procedure of UE1 from the LTE System to the NG System in the configuration example of the wireless communication network shown in Figure 1. Note that the handover procedure shown in Figure 8 is a detailed and modified version of the handover procedure shown in Figures 2A and 2B, and specifically describes the configuration in the NG Core 5 and the network slice selection by the NG Core 5.
[0103] The NG Core 5 shown in Figure 8 includes common network functions (NFs) 51, network functions for network slice A (NFs for slice A) 52, network functions for network slice B (NFs for slice B) 53, and a Home Subscriber Server (HSS) 54.
[0104] Each network element (NF) is a component of a network slice. Each network slice is composed of the network functions (NFs) necessary to provide the required telecommunication services and network capabilities. Each network element (NF) is a processing function in the network and defines its functional behaviour and interfaces. Each network element may be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, or a virtualized function instantiated on a suitable platform.
[0105] Each network slice may be identified by a Network Slice specific Instance ID (NSI-ID). Each network function (NF) may be identified by a Network Function ID (NF ID). If there are common control plane network functions (Common CP NFs) (used), the NSI-ID may be a combination of Common CP NF IDs and Slice specific IDs (i.e., NF IDs for selected slice).
[0106] The Common NFs 51 shown in FIG. 8 include control plane network functions (CP NFs). The Common NFs 51 may further include user plane network functions (UP NFs). The NFs for slice A 52 may include UP NFs and CP NFs. Similarly, the NFs for slice B 53 may include UP NFs and CP NFs.
[0107] FIG. 8 shows an example in which a Slice Selection Function (SSF) is co-located with Common NFs 51. However, the SSF may be located away from Common NFs 51. In this case, Common NFs 51 exchanges messages with the SSF. The SSF selects a network slice to be associated with UE1. For example, the SSF may associate UE1 with a default network slice, or may additionally or alternatively associate UE1 with a network slice (slice type) specified by UE1. The SSF may further perform a NAS Node Selection Function (NNSF) to select CP NFs (or CP NFIDs) corresponding to the selected slice. Here, the default network slice may be set per Public Land Mobile Network (PLMN), per RAT, per UE usage type, per Service type, or per Slice type.
[0108] The allocation of one or more packet flows of UE1 to a network slice may be performed according to any of the following three examples. In the first example, the NG System including the NR NB3 and the NG Core5 supports bearer-based forwarding using a bearer per QoS class and per PDU session. The bearer of the NG System may be called an NG-EPS-bearer, and the radio access bearer of the NG System may be called an NG-RAB. In the first example, each bearer is assigned to a network slice. In some implementations, the Common NFs 51 communicates with the Slice specific User plane NF(s) (SUNF(s)) of the network slice selected for UE1 and configures the bearer of UE1 in the SUNF(s).
[0109] In the second example, similar to the first example, the NG System including NR NB3 and NG Core5 supports bearer-based transport using a bearer per QoS class and per PDU session. The NG System bearer can be used to transport multiple packet flows (PDU flows). In the second example, the NG System is configured to identify data flows (PDU flows) within the bearer for per-PDU-flow QoS handling (e.g., packet discard). In the second example, each packet flow (e.g., PDU flow) of UE1 is assigned to one of the network slices on a per-PDU-flow basis.
[0110] In a third example, an NG system including an NR NB3 and an NG Core5 supports flow-based forwarding of user data. In the third example, network slicing is configured for each PDU session of UE1. In other words, a set of multiple packet flows (PDU flows) included in one PDU session is assigned to any one network slice.
[0111] In step 801, UE1 is handed over from source LTE eNB2 to target NR NB3 and is in a connected state (ie, RRC_Connected) in a cell of target NR NB3. UE1 sends network slice assistance information to target NR NB3. As already described, the network slice assistance information may indicate, for example, the type of UE1, the service desired by UE1, or the tolerable latency of UE1, or any combination thereof. The network slice assistance information may be NAS information and may be included in a measurement report sent from UE1 to LTE eNB2. UE1 may use an RRC Connection Reconfiguration Complete message (eg, step 206 in FIG. 2A), a UL Information Transfer message, or other RRC messages to transmit the network slice assistance information. Note that the transmission of the network slice assistance information by UE1 may be omitted.
[0112] Step 802 corresponds to step 207 in FIG. 2B. That is, the target NR NB3 sends an NR Path Switch Request message to the NG Core5. The NR Path Switch Request message includes an EPS Radio Access Bearer (E-RAB) QoS information element (IE). The E-RAB QoS IE indicates the QoS (e.g., QoS class identifier (QCI), Allocation and retention priority (ARP)) of the E-RAB of UE1. The NR Path Switch Request message may further include network slice assistance information (step 801) sent from the NAS layer of UE1.
[0113] In step 803, the Common NFs 51 performs authentication of the UE 1, if necessary. The authentication includes confirmation of slices authorized for the UE 1. In slice authorization, the Common NFs 51 may determine / judge whether the UE 1 is authorized for each slice.
[0114] In step 804, the Common NFs 51 performs slice selection. That is, the Common NFs 51 selects a network slice to be associated with the UE1. In the example of FIG. 8, the Common NFs 51 selects slice A for the UE1. The slice selection in step 804 may be performed per service (e.g., EPS bearer / E-RAB, IP flow) ongoing or requested by the UE1. As already mentioned, the slice selection in step 804 may be performed by an SSF located remotely from the Common NFs 51.
[0115] Step 805 corresponds to step 208 in Fig. 2B. The Common NFs 51 communicates with the UP NFs (NFs for slice A 52) of the selected slice to create a bearerless session in the selected slice (here, slice A) for the UE 1. Note that if the NG System supports bearer-based transfer of user data and relocation of a transfer node is not required, the Common NFs 51 may perform a bearer modification procedure instead of the session creation procedure.
[0116] Step 806 corresponds to step 209 in Fig. 2B. The Common NFs 51 sends an NR Path Switch Request Acknowledge message to the target NR NB3. Instead of the Common NFs 51, the CP NFs for the selected slice (NFs for slice A52) may send the NR Path Switch Request Acknowledge message to the target NR NB3.
[0117] The NR Path Switch Request Acknowledge message of step 806 includes information (ie, slice information information element (IE)) about the network slice selected by the Common NFs 51 (or SSF). The slice information IE may include, for example, NSI-IDs indicating the selected network slice, NF IDs indicating the selected network functions (NFs), or a multi-dimensional descriptor (MDD), or any combination thereof. The MDD can be provided by the UE in the RRC signaling layer and the NAS signaling layer. The MDD represents a Tenant ID and a Service Descriptor / slice type. The Service Descriptor / slice type indicates a service or use case (eg, eMBB, mMTC, URLLC, critical communications (CriC)) associated with the UE 1 or the selected network slice.
[0118] Step 807 corresponds to step 210 in Figure 2B. The target NR NB3 sends an NR DL Information Transfer message to UE1, carrying the slice information IE received from the NG Core5.
[0119] Figures 9A and 9B show another example of a handover procedure of UE1 from the LTE System to the NG System in the configuration example of the wireless communication network shown in Figure 1. The handover procedure shown in Figures 9A and 9B is a detailed and modified version of the handover procedure shown in Figures 3A and 3B, and specifically describes the configuration in the NG Core 5 and the network slice selection by the NG Core 5. The following mainly describes the differences between the procedure in Figure 8 and the procedures in Figures 9A and 9B.
[0120] In step 901, UE1 is connected to LTE eNB2 and is in a connected state (ie, RRC_Connected). UE1 sends network slice assistance information to LTE eNB2. UE1 may use an RRC Connection Reconfiguration Complete message, a UL Information Transfer message, or other RRC messages to transmit the network slice assistance information.
[0121] Step 902 corresponds to step 302 in Fig. 3A. That is, the source LTE eNB3 sends an NR Handover Request message to the target NR NB3. The NR Handover Request message includes an E-RAB QoS IE. The E-RAB QoS IE indicates the QoS (e.g., QoS class identifier (QCI), Allocation and retention priority (ARP)) of the E-RAB of UE1. The NR Handover Request message may further include network slice assistance information (step 901) sent from the NAS layer of UE1.
[0122] Step 903 corresponds to step 303 in Fig. 3A. That is, the target NR NB3 sends a Handover Preparation Request message to the NG Core5. The Handover Preparation Request message includes the E-RAB QoS IE received from the source LTE eNB2. The Handover Preparation Request message may further include the network slice support information (step 801) received from the source LTE eNB2.
[0123] The processes of steps 904 and 905 are similar to those of steps 803 and 804 in Fig. 8. Step 906 corresponds to step 304 in Fig. 3A. That is, the Common NFs 51 sends a Handover Preparation Request Acknowledge message to the target NR NB3. The Handover Preparation Request Acknowledge message includes information (i.e., slice information IE) about the network slice selected by the Common NFs 51 (or SSF).
[0124] Step 907 corresponds to step 305 in Fig. 3A. That is, the target NR NB3 sends an NR Handover Request Acknowledge message to the source LTE eNB2. The transparent container included in the NR Handover Request Acknowledge message may include the slice information IE sent from the Common NFs51.
[0125] Step 908 corresponds to step 306 in Fig. 3A. That is, the source LTE eNB3 sends a Radio Resource Control (RRC) message including a Handover Command message including a transparent container generated by the target NR NB3 to the UE1. The RRC message may be, for example, a Mobility from EUTRA command message or an RRC Connection Reconfiguration message. As described above, the transparent container sent to the UE1 may include a slice information IE.
[0126] Steps 909 and 910 correspond to steps 307 and 308 in FIG. 3A. That is, UE1 performs handover to the target NR NB3 (step 309) and sends an NR Handover Confirm for NR message to the target NR NB3 (step 910). The message of step 910 may be an NR RRC Connection Reconfiguration Complete message. The message of step 910 may include a slice information IE. The slice information IE includes an identifier (e.g., NSI-ID, NF IDs, or MDD) for identifying the network slice selected for UE1. The slice information IE may be NAS information or RRC information.
[0127] In the handover completion phase, either option 1 (ie, steps 911A, 912A, and 913A) or option 2 (ie, steps 911B, 912B, and 913B) shown in FIG. 9B is executed.
[0128] In option 1, the target NR NB3 sends an NR Path Switch Request message to the Common NFs 51 (step 911A). The NR Path Switch Request message may include a slice information IE. Step 911A corresponds to step 310 in FIG. 3B.
[0129] Step 912A corresponds to step 311 in Fig. 3B. The Common NFs 51 communicates with the UP NFs (NFs for slice A 52) of the selected slice to create a bearerless session in the selected slice (here, slice A) for the UE 1. If the NG System supports bearer-based transfer of user data and no relocation of the transfer node is required, the Common NFs 51 may perform a bearer modification procedure instead of the session creation procedure.
[0130] Step 913A corresponds to step 312 in Fig. 3B. The Common NFs 51 sends an NR Path Switch Request Acknowledge message to the target NR NB3. Instead of the Common NFs 51, the CP NFs for the selected slice (NFs for slice A52) may send the NR Path Switch Request Acknowledge message to the target NR NB3.
[0131] In contrast, in option 2, the target NR NB3 determines the network slice (i.e., slice A) selected for UE1 and sends an NR Path Switch Request Acknowledge message to the CP NFs of NFs for slice A52 corresponding to slice A (step 911B). In some implementations, the target NR NB3 may use the slice information IE received from UE1 in step 910 to determine the network slice selected for UE1. Alternatively, the target NR NB3 may store the slice information IE received from NG Core5 in step 907 in association with the context of UE1, and use the stored slice information IE for the determination in step 911B.
[0132] Step 912B corresponds to step 311 in FIG. 3B. The CP NFs of the NFs for slice A52 communicate with the UP NFs of the NFs for slice A52 to create a bearerless session. If the NG System supports bearer-based transfer of user data and no relocation of the transfer node is required, the NFs for slice A52 may perform a bearer modification procedure instead of the session creation procedure. The NFs for slice A52 may communicate with the Common NFs51 as necessary.
[0133] Step 913B corresponds to step 312 in Figure 3B. The CP NFs for slice A52 send an NR Path Switch Request Acknowledge message to the target NR NB3.
[0134] According to the handover procedure from the LTE System to the NG System of this embodiment, information of the network slice selected by the Common NFs 51 for UE1 (e.g., NSI-ID, MDD, NFIDs) can be provided from the NG Core 5 to the target NR NB3. Thus, for example, the target NR NB3 can know the network slice selected for UE1. Additionally or alternatively, the target NR NB3 can use the information of the network slice selected by the Common NFs 51 for UE1 to generate or derive information or parameters to be sent to UE1 in, for example, a Handover Command (i.e., a transparent container (RRCConnectionReconfiguration)).
[0135] <Third embodiment> This embodiment provides a method for handing over UE1 from an NG system to an LTE system. Figures 10A and 10B show an example of a handover procedure for UE1 from an NG system to an LTE system in the example of the wireless communication network configuration shown in Figure 1. Figure 10A shows a preparation phase and an execution phase of the handover, and Figure 10B shows a completion phase of the handover.
[0136] The procedure shown in Figures 10A and 10B is similar to the "X2-based handover" of LTE in that it involves the transfer of handover signaling messages (i.e., steps 1002 and 1003) over the direct base station interface 101 (e.g., X3 interface) during the handover preparation phase. However, if only the transfer of handover signaling messages over the direct base station interface 101 were performed, the information required for the relocation of UE1 from the LTE system to the NG system would be missing. Therefore, in the procedure shown in Figures 12A and 12B, the handover completion phase is enhanced to include signaling between the LTE eNB2 and the NG Core5 (i.e., steps 1007 and 1008) to obtain the information required for the relocation of UE1 from the NG system to the LTE system.
[0137] In step 1001, UE1 is connected to NR NB3 and is in a connected state (e.g., RRC_Connected). UE1 receives a measurement configuration from NR NB3, performs neighbor cell measurements including NG-RAN cells and E-UTRAN (LTE) cells and inter-RAT measurements according to the measurement configuration, and sends a measurement report to NR NB3.
[0138] In step 1002, the NR NB3 decides to perform an inter-RAT handover to a cell of the LTE eNB2. In response to the decision to perform an inter-RAT handover, the NR NB3 sends a Handover Request message over the direct inter-base station interface 101 to the target LTE eNB2.
[0139] The Handover Request message in step 1002 may include a Handover Type Information Element (IE) indicating a handover from NR to LTE. The Handover Type IE is set to, for example, “NRtoLTE”.
[0140] Additionally, the Handover Request message of step 1002 may indicate identifiers of the PDU flow(s) or bearer(s) of UE 1 to be handed over and QoS parameters (eg, QCI, ARP).
[0141] Furthermore, the Handover Request message of step 1002 may include a "Handover Preparation Information to EUTRA" information element (IE). The "Handover Preparation Information to EUTRA" IE may include security-related information. The security-related information includes security parameters used by the target LTE eNB2 for the derivation of Access Stratum (AS) security keys. The security parameters include base keys (i.e., K eNB ), or parameters (e.g., {NH, NCC} pair) for deriving the base key. The security parameters may further include UE security capabilities for the LTE RAT or LTE System. The UE security capabilities indicate ciphering and integrity protection algorithms implemented in UE1.
[0142] For example, similar to the existing X2 handover procedure, the source NR NB3 derives K eNB * is derived, {K eNB *, NCC} pair to the target LTE eNB2. Alternatively, the source LTE eNB2 may send the current K eNB From K eNB * is derived, {K eNB *, NCC} pair to target NR NB3.
[0143] In step 1003, the target LTE eNB2 creates a UE context and allocates resources based on the Handover Request message. If the NR Handover Request message in step 1003 includes security-related information, the target NR NB3 may operate as follows. As described above, the security-related information includes security parameters for AS security. The target NR NB3 may select an AS security algorithm based on the UE security capabilities included in the security parameters. The AS security algorithm includes ciphering algorithms for Radio Resource Control (RRC) and User Plane (UP), and an integrity protection algorithm for RRC. Furthermore, the target NR NB3 derives temporary keys for RRC ciphering (encryption), UP ciphering (encryption), and RRC integrity protection using the selected security algorithms, based on the base keys (i.e., K for LTE) derived from the security parameters. eNB ) may be derived.
[0144] Then, the target LTE eNB2 generates a Target To Source Transparent Container (RRC Connection Reconfiguration) to be sent to UE1. The Target To Source Transparent Container includes, for example, a Handover Command message (Handover Command To EUTRA) including an RRC Connection Reconfiguration message and other RRC messages. The target LTE eNB2 then generates an acknowledgement (NR Handover Request Acknowledge) message to the handover request including the Target To Source Transparent Container. The target LTE eNB2 sends the NR Handover Request Acknowledge message to the source NR NB3 over the direct inter-base station interface 101. The Target To Source Transparent Container includes, for example, radio resource configuration information (e.g., radio parameters) set up by the target LTE eNB2, identifiers of the AS security algorithm selected by the target NR NB3, and an NCC value.
[0145] The Handover Request Acknowledge message may further include a list of bearers subject to downlink data forwarding. The “Bearers Subject to Data forwarding list” IE contains, for example, the address(es) and TEID(s) for user traffic data forwarding as well as identifiers of the flows (PDU flow(s)) subject to data forwarding. The address(es) and TEID(s) for user traffic data forwarding may be the address and TEID of the target NR NB3 on the direct-to-base station interface 101. The source NR NB3 starts data forwarding for the bearers or flows (PDU flow(s)) specified by the “Bearers Subject to Data forwarding list” IE.
[0146] In step 1004, the source NR NB3 sends a Radio Resource Control (RRC) message including a Handover Command message including the transparent container generated by the target LTE eNB2 to the UE1. The RRC message may be, for example, a Mobility from NR command message or an RRC Connection Reconfiguration message.
[0147] In step 1005, in response to receiving the RRC message containing the Handover Command message, UE1 moves to the target RAN (i.e., E-UTRAN) and performs handover according to the transparent container (e.g., radio resource configuration information, AS security algorithm, and NCC value) provided in the Handover Command message. That is, UE1 establishes a radio connection with the target LTE eNB2 associated with the LTE System. In step 1006, UE1 sends a Handover Confirm for EUTRA message to the target LTE eNB2 after successfully synchronizing with the target cell. The message in step 1006 may be an RRC Connection Reconfiguration Complete message.
[0148] In step 1008, when UE1 successfully accesses the target NR NB3, the target LTE eNB2 sends a Path Switch Request message to the NG Core 5 to inform that UE1 has changed cells and to request a path switch. The Path Switch Request message may include a list of EPS bearers (or PDU flows) of UE1 that have been switched to the cell of the target LTE eNB2.
[0149] In step 1008, a control node (e.g., MME) in the NG Core 5 performs a bearer-based session creation procedure. Specifically, the control node determines that a packet forwarding node (gateway) for UE1 needs to be relocated, and selects a target forwarding node (i.e., S-GW) in the NG Core 5. The control node sends a Create Session Request message to the target S-GW. The Create Session Request message includes information (e.g., SDF templates, or Traffic Flow Templates (TFTs)) for identifying one or more service data flows associated with each PDU flow context. The target S-GW allocates its local resources and returns a Create Session Response message to the control node.
[0150] In step 1009, the NG Core 5 sends a Path Switch Request Acknowledge message to the target LTE eNB 2. The Path Switch Request Acknowledge message includes bearer configuration information. The bearer configuration information includes the address of the forwarding node (after relocation) in the NG Core 5 and the uplink (UL) tunnel endpoint identifier (TEID).
[0151] In addition, if the NG System supports bearer-based transfer of user data and relocation of the transfer node is not required, the control node in the NG Core 5 may perform a bearer modification procedure instead of a session creation procedure in step 1008.
[0152] 11A and 11B show an example of a handover procedure of UE1 from the NG System to the LTE System in the configuration example of the wireless communication network shown in FIG. 1. FIG. 11A shows a handover preparation phase and an execution phase, and FIG. 11B shows a handover completion phase. In the procedure of FIG. 10A and FIG. 10B already described, the target LTE eNB2 receives bearer setting information from the NG Core5 in the handover completion phase (step 100) after UE1 connects to the target LTE eNB2. In contrast, in the procedure shown in FIG. 11A and FIG. 11B, the target LTE eNB2 receives bearer setting information from the NG Core5 in the handover preparation phase (step 1104) before the source NR NB3 issues a handover instruction to UE1. The following mainly describes this difference.
[0153] The processes of steps 1101 and 1102 are similar to the processes of steps 1001 and 1002 in Fig. 10A. In step 1103, the target LTE eNB2 sends a Handover Preparation Request message to the NG Core 5 in response to receiving the Handover Request message (step 1102).
[0154] The Handover Preparation Request message of step 1103 may include a handover type information element (Handover Type IE) indicating that the handover is from NR to LTE. The Handover Type IE is set to, for example, "NRtoLTE". Furthermore, the Handover Preparation Request message may include a list of PDU flows of UE1 to be switched to the cell of the target LTE eNB2.
[0155] In step 1104, the NG Core 5 determines that the type of the handover is an Inter-RAT handover to an LTE system based on the received Handover Preparation Request message. Furthermore, the NG Core 5 sends a Handover Preparation Request Acknowledge message to the target LTE eNB 2, which includes core network information or security-related information or both. The core network information and security-related information are used by the target NR NB 3 to implement resource and security-related settings for communicating with the UE 1 in the NG system.
[0156] In one example, the core network information may include bearer configuration information (Bearer Config). The bearer configuration information relates to at least one EPS bearer configured for UE1. The bearer configuration information includes bearer identifiers (e.g., EPS Bearer Identity and E-RAB ID), addresses of forwarding nodes in NG Core5 and UL TEID, and bearer QoS parameters (e.g., QCI, ARP). The bearer configuration information may indicate mapping of EPS bearers and PDU flows for UE1.
[0157] The security-related information also includes NAS security configuration information of the LTE system. The NAS security configuration information includes, for example, NAS security algorithms including ciphering and integrity protection. The NAS security configuration information may be a NAS Security Transparent Container IE. That is, the NAS security configuration information (NAS Security Transparent Container IE) is transparently sent from the target LTE eNB2 to the UE1 via the source NR NB3.
[0158] The security related information further includes security parameters used by the target LTE eNB2 for the derivation of AS security keys, such as base keys (i.e., K eNB ), or parameters (e.g., {NH, NCC} pair) for deriving the base key. The security parameters may further include UE security capabilities for the LTE RAT or LTE System. The UE security capabilities indicate ciphering and integrity protection algorithms implemented in UE1.
[0159] In step 1105, the target LTE eNB2 creates a UE context and allocates resources based on the Handover Preparation Request Acknowledge message including core network information or security-related information or both. If the Handover Preparation Request Acknowledge message includes security-related information, the target LTE eNB2 may operate as follows. As described above, the security-related information includes NAS security configuration information (NAS Security Transparent Container IE) and security parameters for AS security. The target LTE eNB2 may include the NAS security configuration information (NAS Security Transparent Container IE) in a transparent container sent to UE1. Additionally or alternatively, the target LTE eNB2 may select an AS security algorithm (i.e., ciphering algorithms for RRC and UP, and integrity protection algorithm for RRC) based on the UE security capabilities included in the security parameters. In addition, the target LTE eNB2 generates temporary keys for RRC ciphering (encryption), UP ciphering (encryption), and RRC integrity protection using the selected security algorithms and a base key (i.e., K eNB ) may be derived.
[0160] Then, the target LTE eNB2 generates a transparent container (RRCConnectionReconfiguration) to be sent to the UE1, and generates a Handover Command message (Handover Command to EUTRA message) including the transparent container. The transparent container includes, for example, radio resource configuration information set up by the target LTE eNB2, identifiers of the AS security algorithm selected by the target LTE eNB2, and NAS security configuration information. The target LTE eNB2 sends the Handover Command message to the source NR NB3 over the direct inter-base station interface 101.
[0161] The processing of steps 1106 to 1108 is similar to the processing of steps 1004 to 1006 in FIG. 10. In step 1109, the NG Core 5 performs a bearer session creation procedure. In other words, the control node in the NG Core 5 initiates a bearer session creation procedure for the UE 1 in response to receiving the Handover Preparation Request message in step 1103. That is, the control node in the NG Core 5 initiates an EPS bearer creation procedure for the UE 1 prior to a path switch request from the target LTE eNB 2 (step 1110). The bearer creation in step 1109 may be performed similarly to that in step 1008 in FIG. 10.
[0162] In step 1110, the target LTE eNB2 sends a Path Switch Request message to the NG Core5. In step 1111, the control node in the NG Core5 completes the Inter-RAT handover procedure by performing a bearer modification procedure. For example, the control node in the NG Core5 may send a Modify Bearer Request message per session (ie, PDN connection) to the S-GW. The Modify Bearer Request message may include a bearer identifier (eg, EPS Bearer ID), as well as the address and downlink (DL) TEID of the target LTE eNB2. The S-GW may return a Modify Bearer Response message to the control node in the NG Core5. In step 1112, the control node in the NG Core5 sends a Path Switch Request Acknowledge message to the target LTE eNB2.
[0163] The detailed handover procedure from the NG system to the LTE system according to the present embodiment may be, for example, the specific example described above, but is not limited thereto. For example, the message names shown in the above-described handover procedure examples are merely examples. The above-described handover procedure examples may have different message orders, may omit some messages, or may include additional messages.
[0164] <Fourth embodiment> This embodiment provides a method for handing over UE1 from a source NR NB to a target NE NB in an NG system. In the following, handover in the NG system is referred to as intra-NR handover.
[0165] FIG. 12 shows a configuration example of a wireless communication network according to this embodiment. In the example of FIG. 12, the wireless communication network includes UE1, NR NBs 6 and 7, and NG Core 5. NR NB6 may be, for example, a macro base station or a pico base station. Similarly, NR NB7 may be a macro base station or a pico base station. In the example of FIG. 12, NR NBs 6 and 7 have the same coverage, and the two cells of NR NBs 6 and 7 partially overlap. However, the wireless communication network according to this embodiment may have a Heterogeneous Network (HetNet) structure. For example, NR NB6 may be a macro base station, NR NB7 may be a pico base station, and the macro cell of NR NB6 may completely cover the pico cell of NR NB7. Conversely, NR NB6 may be a pico base station, and NR NB7 may be a macro base station.
[0166] The NR NB6 and the NR NB7 are connected by a direct inter-base station interface 1201. The direct inter-base station interface 1201 is used for the transfer of signaling messages at least between the NR NB6 and the NR NB7. The direct inter-base station interface 1201 may further be used for user packet transfer between the NR NB6 and the NR NB7. The control plane protocol structure and the user plane protocol structure of the direct inter-base station interface 1201 may be similar to those of the X2 interface between the LTE eNBs, for example. The direct inter-base station interface 1201 may be referred to as an NG X2 interface, for example.
[0167] In the following, several examples of intra-NR handover procedures are described. The several examples described below relate to UE mobility in which UE1 in a connected state is handed over from a source NR NB6 to a target NR NB7.
[0168] An example of an intra-NR handover procedure is shown in Figure 13. Figure 13 illustrates the case where network slicing is applied to UE1 at both source cell / source NR NB6 and target cell / target NR NB7. The procedure shown in Figure 13 is similar to the LTE "X2-based handover" in that it involves the transfer of handover signaling messages over the direct base station-to-base station interface 101 during the handover preparation phase (i.e., steps 1303 and 1304).
[0169] In step 1301, UE1 is connected to source NR NB6 and is in a connected state (ie, RRC_Connected). Network slicing is applied to UE1 in the source cell / source NR NB6. In step 1302, UE1 receives a measurement configuration from NR NB6, performs neighbor cell measurements according to the measurement configuration, and sends a measurement report to NR NB6.
[0170] In step 1303, NR NB6 decides on an intra-NR handover to the cell of NR NB7. In response to the decision on an intra-NR handover, source NR NB6 sends an NR Handover Request message over the direct inter-base station interface 1201 to target NR NB7.
[0171] The NR Handover Request message of step 1303 may contain a list (e.g., PDU-Flows To Be Setup List) of UE1's packet flows (i.e., PDU flow(s)) or bearers (i.e., radio access bearer(s)) to be set up at the target NR NB7. The list indicates Flow Information for each packet flow. The Flow Information includes a flow identifier (e.g., PDU flow ID), the address of the forwarding node in the NG Core5 and the uplink (UL) Session Endpoint Identifier (SEID), and flow QoS parameters.
[0172] The NR Handover Request message of step 1303 may include slice information. The slice information relates to one or more network slices to which UE1 is connected (utilized) in the source cell / source NR NB6. The slice information enables the target NR NB7 to recognize one or more network slices to which UE1 is connected. For example, the slice information may indicate identifiers (e.g., NSI-ID, NF IDs, MDD) of each network slice to which UE1 is connected. Additionally or alternatively, the slice information may indicate a UE identifier assigned to UE1 by CP NFs (or a control node equivalent to MME) associated with each network slice. The UE identifier may be an identifier equivalent to the MME UE S1AP ID in LTE. When UE1 is connected to multiple network slices, multiple UE identifiers corresponding to multiple network slices, respectively, may be assigned to UE1.
[0173] In step 1304, the target NR NB7 creates a UE context and allocates resources based on the NR Handover Request message. The target NR NB7 may determine admitted PDU flows based on the received flow information (e.g., PDU-Flows To Be Setup List). The target NR NB7 may recognize one or more network slices to which UE1 is connected based on the received slice information, and may recognize CP NFs (or control nodes equivalent to MMEs) of each network slice.
[0174] The target NR NB7 then generates a transparent container (RRCConnectionReconfiguration) to be sent to UE1, and generates an NR Handover Request Acknowledge message (Handover Command to NR message) containing the transparent container. The target NR NB7 sends the NR Handover Request Acknowledge message to the source NR NB6 over the direct base station interface 1201. The transparent container includes, for example, radio resource configuration information set up by the target NR NB7. The NR Handover Request Acknowledge message may further include the above-mentioned "PDU-flows Admitted list" information element (IE). The source LTE eNB2 starts data forwarding for the flows (PDU flow(s)) specified by the "PDU-flows Admitted list" IE.
[0175] In step 1305, source NR NB6 sends an NR RRC Connection Reconfiguration message to UE1. The RRC Connection Reconfiguration message includes a "MobilityControlInfoNR" IE, which is generated by target NR NB7 and informs UE1 of the settings and information required to access the target cell / target NR NB7.
[0176] In step 1306, UE1 moves from the source cell / source NR NB6 to the target cell / target NR NB7 in response to receiving the NR RRC Connection Reconfiguration message. In step 1307, after successfully synchronizing to the target cell, UE1 sends an NR RRC Connection Reconfiguration Complete message to the target NR NB7, carrying a Handover Confirm for NR message. The Handover Confirm for NR message or the NR RRC Connection Reconfiguration Complete message may carry network slice assistance information or slice configuration.
[0177] In step 1308, when UE1 successfully accesses the target NR NB7, the target NR NB7 sends an NR Path Switch Request message to the NG Core5 to inform that UE1 has changed cells and to request a path switch. The NR Path Switch Request message may include a list of bearers (i.e., E-RABs) or packet flows (i.e., PDU flow(s)) of UE1 that have been switched to the cell of the target NR NB7. More specifically, the NR Path Switch Request message may include an "E-RAB / Flow to be switched in Downlink (DL) List" IE. The NR Path Switch Request message of step 1308 may include slice information. The slice information indicates one or more network slices that UE1 wishes to connect to (use) in the target cell / target NR NB7.
[0178] In step 1309, the NG Core 5 performs a flow modification procedure. For example, the control node in the NG Core 5 may send a Modify Flow Request message per session (ie, PDU session) to the forwarding node in the NG Core 5. The Modify Flow Request message may include a flow identifier (eg, PDU flow ID), as well as the address of the target NR NB3 and a Session Endpoint Identifier (SEID) for downlink (DL). The Session Endpoint Identifier (SEID) may be, for example, a Tunnel Endpoint Identifier (TEID). The forwarding node in the NG Core 5 may return a Modify Flow Response message to the control node in the NG Core 5.
[0179] In step 1310, the control node in the NG Core 5 sends an NR Path Switch Request Acknowledge message to the target NR NB 3. If the NG Core 5 changes the uplink forwarding points of the tunnels, the NR Path Switch Request Acknowledge message may include an “E-RAB / Flow to be switched in Uplink (UL) List” IE. The “E-RAB / Flow to be switched in UL List” IE indicates the new uplink transport layer address and endpoint identifier for each bearer (i.e., E-RAB) or flow (i.e., PDU flow). If the NG System supports bearer-based forwarding of user data, the control node in the NG Core 5 may perform a bearer modification procedure instead of a session creation procedure in step 1310.
[0180] In response to receiving the NR Path Switch Request message in step 1308, the control node of the NG Core 5 may decide to change the network slice for the UE 1 or may determine that no network slice is permitted for the UE 1. In response to this, the NR Path Switch Request Acknowledge message in step 1310 may include a Slice information IE indicating the changed network slice for the UE 1. Alternatively, the NR Path Switch Request Acknowledge message in step 1310 may indicate that no network slice is permitted for the UE 1.
[0181] In step 1311, the target NR NB3 may send an NR DL Information Transfer message to UE1 carrying NAS information (eg, Slice information IE) received from the NG Core5.
[0182] Figure 14 shows an example of an intra-NR handover procedure. The handover procedure shown in Figure 14 is a detailed and modified version of the handover procedure shown in Figure 13, and specifically describes the configuration within the NG Core 5 and the signaling within the NG Core 5. The specific configuration of the NG Core 5 shown in Figure 14 is the same as that shown in Figure 8. That is, the NG Core 5 includes Common NFs 51, NFs for slice A 52, NFs for slice B 53, and HSS 54.
[0183] Step 1401 corresponds to step 1301 in Fig. 13. Here, as an example, slice A and slice B are selected for UE1. Step 1402 corresponds to steps 1302 to 1307 in Fig. 13, and includes a handover preparation phase and a handover execution phase.
[0184] FIG. 14 shows case A (steps 1403 to 1406) and case B (steps 1407 to 1410). Either case A or case B is executed. In case A, the CP NFs (e.g., Session Management Function (SMF) or Mobility Management Function (MMF)) in Common NFs 51 triggers flow modification (or bearer modification) for slices for all UEs 1. In contrast, in case B, the CP NFs (e.g., SMF or MMF) of each slice triggers flow modification (or bearer modification) for that slice.
[0185] First, case A will be described. Step 1403 corresponds to step 1308 in FIG. 13. In step 1403, the target NR NB7 sends an NR Path Switch Request message to the Common NFs51. As already described, the NR Path Switch Request message may include an "E-RAB / Flow to be switched in Downlink (DL) List" IE. Furthermore, the NR Path Switch Request message may include slice information. The slice information indicates one or more network slices that UE1 wishes to connect to (use) in the target cell / target NR NB7.
[0186] Steps 1404 and 1405 correspond to step 1309 in Fig. 13. In steps 1404 and 1405, the CP NFs of the Common NFs 51 trigger flow modification (or bearer modification) to the NFs for slice A 52 and the NFs for slice B 53.
[0187] Step 1406 corresponds to step 1310 in Figure 13. In step 1406, the Common NFs 51 sends an NR Path Switch Request Acknowledge message to the target NR NB 7. As already described, the NR Path Switch Request Acknowledge message may include an "E-RAB / Flow to be switched in UL List" IE.
[0188] Next, case B will be described. Step 1407 corresponds to step 1308 in FIG. 13. In step 1407, the NR NB3 sends an NR Path Switch Request message to each of the CP NFs (i.e., the CP NFs of NFs for slice A52 and the CP NFs of NFs for slice B53) of one or more network slices to which UE1 wishes to connect (use) in the target cell / target NR NB7. The target NR NB7 may determine (select) one or more network slices to which the NR Handover Request message should be sent based on slice information included in the NR Handover Request message (steps 1402, 1303) received from the source NR NB6. Alternatively, the target NR NB7 may determine (select) one or more network slices to which the NR Handover Request message should be sent based on network slice support information or slice information included in the NR RRC Connection Reconfiguration Complete message (or Handover Confirm for NR message) received from UE1.
[0189] Steps 1408 and 1409 correspond to step 1309 in Figure 13. In step 1408, NFs for slice A 52 performs flow modification (or bearer modification) in slice A. In step 1409, NFs for slice B 53 performs flow modification (or bearer modification) in slice B.
[0190] Step 1410 corresponds to step 1310 in Figure 13. In step 1410, each of the CP NFs of NFs for slice A52 and the CP NFs of NFs for slice B53 sends an NR Path Switch Request Acknowledge message to the target NR NB7.
[0191] An example of an intra-NR handover procedure is shown in Figure 15. Figure 15 shows a case where network slicing is not applied to UE1 in source cell / source NR NB6, but network slicing is applied to UE1 in target cell / target NR NB7.
[0192] In step 1501, UE1 is connected to source NR NB6 and is in a connected state (ie, RRC_Connected). UE1 is not applied with network slicing in the source cell / source NR NB6.
[0193] Steps 1502 to 1507 are basically the same as steps 1302 to 1507 in Fig. 13. However, the NR Handover Request message in step 1503 may not include slice information. On the other hand, the NR RRC Connection Reconfiguration Complete message (or Handover Confirm for NR message) in step 1507 may include network slice support information. The network slice support information may be NAS information or RRC information.
[0194] Steps 1508 to 1510 are a handover completion phase, which are basically similar to steps 1308 to 1510 in FIG. 13. However, in step 1509, the NG Core 5 further performs slice selection for the UE 1. To assist the slice selection by the NG Core 5, the NR Path Switch Request message in step 1508 may include network slice assistance information sent from the UE 1. The NR Path Switch Request Acknowledge message in step 1510 may include slice information. The slice information relates to one or more network slices selected for the UE 1 by the NG Core 5.
[0195] Step 1511 corresponds to step 1311 in Figure 13. The NR DL Information Transfer message in step 1511 may carry slice information sent from the NG Core 5.
[0196] Figure 16 shows an example of an intra-NR handover procedure. The handover procedure shown in Figure 16 is a detailed and modified version of the handover procedure shown in Figure 15, and specifically describes the configuration within the NG Core 5 and the signaling within the NG Core 5. The specific configuration of the NG Core 5 shown in Figure 16 is the same as that shown in Figure 8.
[0197] Step 1601 corresponds to step 1501 in Figure 15. Step 1602 corresponds to steps 1502 to 1507 in Figure 15, and includes a handover preparation phase and a handover execution phase. Note that UE1 may send network slice support information to target NR NB7 during step 1602 or before step 1602. For example, UE1 may send network slice support information using an NR RRC Connection Reconfiguration Complete message (or a Handover Confirm for NR message).
[0198] Step 1603 corresponds to step 1308 in Figure 13. In step 1603, the target NR NB7 sends an NR Path Switch Request message to the Common NFs51. As already described, the NR Path Switch Request message may include an "E-RAB / Flow to be switched in Downlink (DL) List" IE. Furthermore, the NR Path Switch Request message may include network slice support information.
[0199] In step 1604, the Common NFs 51 performs authentication of the UE 1, if necessary. The authentication includes confirmation of slices authorized for the UE 1. In slice authorization, the Common NFs 51 may determine / judge whether the UE 1 is authorized for each slice.
[0200] FIG. 16 illustrates the case where at least one network slice is granted to UE1 or is applicable to the services(s) ongoing or requested by UE1. Thus, in step 1605, Common NFs 51 performs slice selection. In the example of FIG. 16, Common NFs 51 selects slice A for UE1. The slice selection in step 1605 may be performed per service(s) ongoing or requested by UE1 (e.g., EPS bearer / E-RAB, IP flow). The slice selection in step 1605 may be performed by an SSF located remotely from Common NFs 51.
[0201] Step 1606 corresponds to step 1509 in Figure 15. Common NFs 51 communicates with NFs for Slice A 52 of the slice (here, slice A) selected for UE1 to perform flow modification (or bearer modification), whereby Common NFs 51 and NFs for Slice A 52 switch the uplink and downlink forwarding points of the packet flow (i.e., PDU flow(s)) or bearer of UE1 from the common network slice (i.e., Common NFs 51) to slice A (i.e., NFs for slice A 52).
[0202] Step 1607 corresponds to step 1510 in Figure 15. The Common NFs 51 sends an NR Path Switch Request Acknowledge message to the target NR NB 7. Instead of the Common NFs 51, the CP NFs for the selected slice (NFs for slice A 52) may send the NR Path Switch Request Acknowledge message to the target NR NB 7. As already described, the NR Path Switch Request Acknowledge message of step 1607 may include an "E-RAB / Flow to be switched in UL List" IE.
[0203] Furthermore, the NR Path Switch Request Acknowledge message in step 1607 may include slice information. The slice information enables the target NR NB7 to recognize one or more network slices selected by the NG Core5 for UE1. For example, the slice information may indicate identifiers (e.g., NSI-ID, NF IDs, MDD) of each network slice. Additionally or alternatively, the slice information may indicate a UE identifier assigned to UE1 by CP NFs (or a control node equivalent to MME) associated with each network slice. The UE identifier may be an identifier equivalent to the MME UE S1AP ID in LTE. When UE1 is connected to multiple network slices, multiple UE identifiers corresponding to multiple network slices, respectively, may be assigned to UE1.
[0204] Step 1608 corresponds to step 1511 in Figure 15. The NR DL Information Transfer message may carry all or part of the slice information sent from the NG Core 5.
[0205] An example of an intra-NR handover procedure is shown in Figure 17. Figure 17 shows a case where network slicing is applied to UE1 in the source cell / source NR NB6, but network slicing is not applied to UE1 in the target cell / target NR NB7.
[0206] In step 1701, similar to step 1301 in FIG. 13, network slicing is applied to UE1 in source cell / source NR NB6. The processes in steps 1702 to 1711 are also similar to the processes in steps 1302 to 1311 in FIG. 13. However, in step 1709, NG Core5 determines that network slicing is not applied to UE1 in target cell / target NR NB7, and switches uplink and downlink forwarding points of packet flows or bearers of UE1 from slices A and B (i.e., NFs for slice A52 and NFs for slice B53) to a common network slice (i.e., Common NFs51). Thus, the NR Path Switch Request Acknowledge message in step 1710 may include information that explicitly or implicitly indicates that network slicing is not applied to UE1. The NR DL Information Transfer message in step 1711 may also include information that explicitly or implicitly indicates that network slicing is not applied to UE1.
[0207] Figure 18 shows an example of an intra-NR handover procedure. The handover procedure shown in Figure 18 is a detailed version and modification of the handover procedure shown in Figure 17, and specifically describes the configuration within the NG Core 5 and the signaling within the NG Core 5. The specific configuration of the NG Core 5 shown in Figure 18 is the same as that shown in Figure 8.
[0208] The processes in steps 1801 to 1803 are the same as those in steps 1401 to 1403 in FIG. 14. In step 1404, the Common NFs 51 performs authentication of the UE1 as necessary. The authentication includes confirmation of slices authorized for the UE1 (slice authorization). In slice authorization, the Common NFs 51 may determine / judge whether the UE1 is authorized for each slice. The Common NFs 51 determines that none of the network slices are authorized for the UE1, or none of the network slices are applicable to the services(s) ongoing or requested by the UE1.
[0209] Steps 1805 and 1806 correspond to step 1709 in Figure 17. In steps 1805 and 1806, the CP NFs of Common NFs51 trigger flow modification (or bearer modification) to NFs for slice A52 and NFs for slice B53 to switch the uplink and downlink forwarding points of UE1's packet flow or bearer from slices A and B (i.e., NFs for slice A52 and NFs for slice B53) to the common network slice (i.e., Common NFs51).
[0210] Steps 1807 and 1808 correspond to steps 1710 and 1711 in Figure 17. In step 1807, Common NFs 51 sends an NR Path Switch Request Acknowledge message to target NR NB7. In step 1808, target NR NB7 sends an NR DL Information Transfer message to UE1. The NR Path Switch Request Acknowledge message and the NR DL Information Transfer message may include information that explicitly or implicitly indicates that network slicing does not apply to UE1.
[0211] As can be understood from the above description, some Intra-NR handover procedures described in this embodiment enable handover of UE1 in a wireless communication network that supports network slicing. In particular, some Intra-NR handover procedures described with reference to Figures 15 to 18 enable handover of UE1 in a case where network slicing is not applied to one of the source cell / source NR NB6 and the target cell / target NR NB7.
[0212] Next, the following describes configuration examples of UE1, LTE eNB2, NR NB3, NR NB6, NR NB7, and core network nodes according to the above-mentioned embodiments. FIG. 19 is a block diagram showing a configuration example of UE1. The LTE transceiver 1901 performs analog RF signal processing related to the PHY layer of the LTE RAT to communicate with the LTE eNB2. The analog RF signal processing performed by the LTE transceiver 1901 includes frequency up-conversion, frequency down-conversion, and amplification. The LTE transceiver 1901 is coupled to the antenna 1902 and the baseband processor 1905. That is, the LTE transceiver 1901 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1905, generates a transmission RF signal, and provides the transmission RF signal to the antenna 1902. The LTE transceiver 1901 also generates a baseband reception signal based on the reception RF signal received by the antenna 1902, and provides the baseband reception signal to the baseband processor 1905.
[0213] The New Radio (NR) transceiver 1903 performs analog RF signal processing for the PHY layer of the NG RAT to communicate with the NR NB3. The New 5G transceiver 1903 is coupled to an antenna 1904 and a baseband processor 1905.
[0214] The baseband processor 1905 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of transmission format (transmission frame), (d) transmission line coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Meanwhile, control plane processing includes communication management of layer 1 (e.g., transmission power control), layer 2 (e.g., radio link control, and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., signaling related to attachment, mobility, and packet communication).
[0215] For example, in the case of LTE and LTE-Advanced, the digital baseband signal processing by the baseband processor 1905 may include signal processing of a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a MAC layer, and a PHY layer. Also, the control plane processing by the baseband processor 1905 may include processing of a Non-Access Stratum (NAS) protocol, an RRC protocol, and a MAC CE.
[0216] The baseband processor 1905 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1906 described later.
[0217] The application processor 1906 is also called a CPU, an MPU, a microprocessor, or a processor core. The application processor 1906 may include multiple processors (multiple processor cores). The application processor 1906 executes a system software program (operating system (OS)) and various application programs (e.g., a communication application for acquiring metering data or sensing data) read from the memory 1908 or a memory not shown in the figure, thereby implementing various functions of the UE1.
[0218] In some implementations, the baseband processor 1905 and the application processor 1906 may be integrated on a single chip, as shown by the dashed line (1907) in Figure 19. In other words, the baseband processor 1905 and the application processor 1906 may be implemented as a single System on Chip (SoC) device 1907. An SoC device may also be referred to as a system Large Scale Integration (LSI) or a chipset.
[0219] The memory 1908 is a volatile memory or a non-volatile memory, or a combination thereof. The memory 1908 may include a plurality of physically independent memory devices. The volatile memory is, for example, a Static Random Access Memory (SRAM) or a Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is a Mask Read Only Memory (MROM), an Electrically Erasable Programmable ROM (EEPROM), a flash memory, or a hard disk drive, or any combination thereof. For example, the memory 1908 may include an external memory device accessible from the baseband processor 1905, the application processor 1906, and the SoC 1907. The memory 1908 may include an internal memory device integrated in the baseband processor 1905, the application processor 1906, or the SoC 1907. Furthermore, the memory 1908 may include a memory in a Universal Integrated Circuit Card (UICC).
[0220] The memory 1908 may store one or more software modules (computer programs) 1909 including instructions and data for performing the processing by the UE 1 described in the above-mentioned embodiments. In some implementations, the baseband processor 1905 or the application processor 1906 may be configured to read the software module 1909 from the memory 1908 and execute it to perform the processing by the UE 1 described in the above-mentioned embodiments.
[0221] FIG. 20 is a block diagram showing a configuration example of an LTE eNB2 according to the above embodiment. Referring to FIG. 20, the LTE eNB2 includes an LTE transceiver 2001, a network interface 2003, a processor 2004, and a memory 2005. The LTE transceiver 2001 performs analog RF signal processing to communicate with UEs supporting the LTE RAT including UE1. The LTE transceiver 2001 may include multiple transceivers. The LTE transceiver 2001 is coupled to an antenna 2002 and a processor 2004. The LTE transceiver 2001 receives modulation symbol data (or OFDM symbol data) from the processor 2004, generates a transmission RF signal, and provides the transmission RF signal to the antenna 2002. The LTE transceiver 2001 also generates a baseband reception signal based on the reception RF signal received by the antenna 2002, and provides the baseband reception signal to the processor 2004.
[0222] The network interface 2003 is used to communicate with network nodes (eg, control nodes and forwarding nodes). The network interface 2003 may include, for example, a network interface card (NIC) that complies with the IEEE 802.3 series.
[0223] The processor 2004 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. For example, in the case of LTE and LTE-Advanced, the digital baseband signal processing by the processor 2004 may include signal processing of a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. In addition, the control plane processing by the processor 2004 may include processing of an S1 protocol, an RRC protocol, and a MAC CE.
[0224] The processor 2004 may include multiple processors. For example, the processor 2004 may include a modem processor (e.g., DSP) that performs digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) that performs control plane processing.
[0225] The memory 2005 is configured by a combination of volatile memory and non-volatile memory. The volatile memory is, for example, SRAM or DRAM, or a combination thereof. The non-volatile memory is, for example, MROM, PROM, flash memory, or a hard disk drive, or a combination thereof. The memory 2005 may include storage located remotely from the processor 2004. In this case, the processor 2004 may access the memory 2005 via the network interface 2003 or an I / O interface not shown.
[0226] The memory 2005 may store one or more software modules (computer programs) 2006 including instructions and data for performing the processes of the LTE eNB2 described in the above embodiments. In some implementations, the processor 2004 may be configured to read the one or more software modules 2006 from the memory 2005 and execute them to perform the processes of the LTE eNB2 described in the above embodiments.
[0227] FIG. 21 is a block diagram showing an example of the configuration of the NR NB3 according to the above embodiment. The NR NBs 6 and 7 may also have the configuration of FIG. 21. Referring to FIG. 21, the NR NB3 includes a New Radio (NR) transceiver 2101, a network interface 2103, a processor 2104, and a memory 2105. The NR transceiver 2101 performs analog RF signal processing to communicate with UEs supporting the NG RAT, including UE1. The NR transceiver 2101 may include multiple transceivers. The NR transceiver 2101 is coupled to an antenna 2102 and a processor 2104. The NR transceiver 2101 receives modulation symbol data from the processor 2104, generates a transmit RF signal, and provides the transmit RF signal to the antenna 2102. The NR transceiver 2101 also generates a baseband receive signal based on the receive RF signal received by the antenna 2102, and provides the baseband receive signal to the processor 2104.
[0228] The network interface 2103 is used to communicate with network nodes (eg, a control node and a forwarding node in the NG Core 5). The network interface 2103 may include, for example, a network interface card (NIC) that complies with the IEEE 802.3 series.
[0229] The processor 2104 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The processor 2104 may include multiple processors. For example, the processor 2104 may include a modem processor (e.g., DSP) that performs digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) that performs control plane processing.
[0230] The memory 2105 is configured by a combination of volatile memory and non-volatile memory. The volatile memory is, for example, SRAM or DRAM, or a combination thereof. The non-volatile memory is, for example, MROM, PROM, flash memory, or a hard disk drive, or a combination thereof. The memory 2105 may include storage located remotely from the processor 2104. In this case, the processor 2104 may access the memory 2105 via the network interface 2103 or an I / O interface not shown.
[0231] The memory 2105 may store one or more software modules (computer programs) 2106 including instructions and data for performing the processing by the NR NB3 described in the above-mentioned embodiments. In some implementations, the processor 2104 may be configured to read the one or more software modules 2106 from the memory 2105 and execute them to perform the processing by the NR NB3 described in the above-mentioned embodiments.
[0232] Fig. 22 is a block diagram showing a configuration example of a core network node 2200 according to the above embodiment. The core network node 2200 is, for example, a control node (eg, Common NFs51) in NG Core5. Referring to Fig. 22, the core network node 2200 includes a network interface 2201, a processor 2202, and a memory 2203. The network interface 2201 is used to communicate with network nodes (eg, RAN nodes, other core network nodes). The network interface 2201 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series.
[0233] The processor 2202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 2202 may include multiple processors.
[0234] The memory 2203 is configured by a combination of volatile memory and nonvolatile memory. The volatile memory is, for example, SRAM or DRAM, or a combination thereof. The nonvolatile memory is, for example, MROM, PROM, flash memory, or a hard disk drive, or a combination thereof. The memory 2203 may include storage located remotely from the processor 2202. In this case, the processor 2202 may access the memory 2203 via the network interface 2201 or an I / O interface not shown.
[0235] The memory 2203 may store one or more software modules (computer programs) 2204 including instructions and data for performing processing by a core network node (e.g., a control node in the NG Core 5) described in the above embodiments. In some implementations, the processor 2202 may be configured to read the one or more software modules 2204 from the memory 2203 and execute them to perform processing by the core network node described in the above embodiments.
[0236] As described with reference to FIG. 19 to FIG. 22, each of the processors included in the UE1, LTE eNB2, NR NB3, and core network node according to the above-described embodiment executes one or more programs including instructions for causing a computer to perform the algorithm described with reference to the drawings. The program can be stored and provided to a computer using various types of non-transitory computer readable medium. The non-transitory computer readable medium includes various types of tangible storage medium. Examples of the non-transitory computer readable medium include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, programmable ROM (PROM), erasable PROM (EPROM), flash ROM, random access memory (RAM)). The program may also be provided to a computer by various types of transitory computer readable medium. Examples of the temporary computer-readable medium include an electric signal, an optical signal, and an electromagnetic wave. The temporary computer-readable medium can provide the program to the computer via a wired communication path such as an electric wire or an optical fiber, or a wireless communication path.
[0237] <Fifth embodiment> In this embodiment, specific examples of the RRC messages described in the above embodiments, the control messages between the RAN and the core network (i.e., NG2 messages), and the control messages between the source base station and the target base station (i.e., X3 messages) are described.
[0238] 23A and 23B show an example of the format of the Mobility from EUTRA command message. In case of handover from LTE System to NG System, the MobilityFromEUTRACommand message includes purpose set to "handover" and targetRAT-Type set to "ngutra" corresponding to NG RAN. Furthermore, the MobilityFromEUTRACommand message includes targetRAT-MessageContainer. The targetRAT-MessageContainer includes the RRCConnectionReconfigurationNR message generated by the target NR NB3. Furthermore, when the targetRAT-Type is "OTHERRAN", i.e., "utra", "geran", or "ngutra", the MobilityFromEUTRACommand message includes nas-SecurityParamFromEUTRA.
[0239] Figure 24 shows an example of the format of an X3AP: NR Handover Request message sent from a source LTE eNB2 to a target NR NB3 on a direct inter-base station interface 101 (X3 interface) in step 202 of Figure 2A and step 302 of Figure 3A. This NR Handover Request message includes an identifier (i.e., Globally Unique CNF ID (GUCNFI)) of a control node (Common NF (CNF)) in NG Core5. Furthermore, this NR Handover Request message includes UE Context Information.
[0240] Figure 25 shows an example of the format of the UE Context Information. In the example of Figure 25, the UE Context Information includes a NE-RABs To Be Setup List. The NE-RABs To Be Setup List indicates a list of radio access bearers (NE-RABs) to be set up in the target NR NB3. The format shown in Figure 25 may be used when the NG System including the NR NB3 and NG Core5 is configured to support bearer-based transfer using a bearer per QoS class and per PDU session.
[0241] The UE Context Information shown in Figure 25 further includes an RRC Context. The RRC Context includes an RRC Handover Preparation Information message. The RRC Handover Preparation Information message is used by the target NR NB3 to implement resource and security related settings for communicating with UE1 in the NG system.
[0242] Furthermore, the UE Context Information shown in FIG. 35 may include assistance information for network slicing (Assistance Data for Network Slicing). The source LTE eNB2 may include the Assistance Data for Network Slicing received from the UE1 or the NG Core5 in the E Context Information.
[0243] FIG. 26 shows an example of the format of an X3AP: NR Handover Request Acknowledge message sent from the target NR NB3 to the source LTE eNB on the direct inter-base station interface 101 (X3 interface) in step 203 of FIG. 2A. This NR Handover Command message includes a Target to Source Transparent Container. The Target to Source Transparent Container includes radio resource configuration information (e.g., radio parameters) generated by the target NR NB3. The Target to Source Transparent Container may include an RRC Container that includes an RRC NG-UTRA Handover Command message. Furthermore, in the example of FIG. 26, the NR Handover Request Acknowledge message includes a NE-RABs Admitted List. The NE-RABs Admitted List indicates a list of radio access bearers (NE-RABs) for which resources are prepared in the target cell.
[0244] FIG. 27 shows an example of a format of an X3AP: NR Handover Request Acknowledge message sent from the target NR NB3 to the source LTE eNB on the direct inter-base station interface 101 (X3 interface) in step 305 of FIG. 3A. The format shown in FIG. 27 differs from the format shown in FIG. 26 in that it includes core network context information (NG Core Context). The NG Core Context may be transmitted to the UE1 transparently to the source LTE eNB2. Additionally or alternatively, a part or all of the NG Core Context may be included in the Target To Source Transparent Container. FIG. 28 shows an example of a format of the NG Core Context. As described in the first embodiment, the NG Core Information includes, for example, slice information and flow information (or PDU session information).
[0245] FIG. 29 shows an example of the format of the slice information. As described in detail in the first embodiment, the slice information includes an identifier (i.e., Network Slice Instance ID) of a network slice determined (selected) for the UE1, and an identifier (i.e., Network Function ID) of a network function or node associated with the network slice. The slice information may include type information (i.e., Multi-Dimensional Descriptor) of the network slice. Furthermore, the slice information may include a mobility class or a session class, or both.
[0246] Fig. 30 shows an example of the format of Flow Information. As described in detail in the first embodiment, Flow Information includes information (PDU session information list) on at least one session (i.e., PDU session(s)) established in the NG system to transfer at least one packet flow (i.e., PDU flow(s)) of UE1. Flow Information includes a session identifier (e.g., PDU Session ID), as well as an address (Transport Layer Address) of a forwarding node in the NG Core5 and a Session Endpoint ID (SIED) of the uplink (UL).
[0247] 31 shows an example of the format of the Session Endpoint ID. As described in detail in the first embodiment, the Session Endpoint ID may be a GTP-TEID, a GRE-TEID, or a network function or node identifier (NF ID).
[0248] <Other embodiments> The above-described embodiments may be implemented independently of each other, or the whole or part of the embodiments may be implemented in appropriate combination.
[0249] The above-described embodiment has been described based on an example of a network configuration in which both the LTE eNB2 and the NR NB3 are connected to the NG Core 5. Alternatively, the LTE eNB2 may be connected to an enhanced EPC (eEPC) that is enhanced to interwork with the NG System. An (e)MME in the eEPC may be connected to a control node (i.e., CPF node) in the NG Core 5 via a control plane interface. Furthermore, one or more nodes in the eEPC may be connected to one or more data nodes (i.e., UPF node) in the NG Core 5 via a user plane interface.
[0250] The E-URAN and NG RAN described in the above embodiments may be implemented based on a Cloud Radio Access Network (C-RAN) concept. The C-RAN may also be called a Centralized RAN. Therefore, the processes and operations performed by each of the LTE eNB2 and NR NB3 described in the above embodiments may be provided by a Digital Unit (DU) included in the C-RAN architecture or a combination of a DU and a Radio Unit (RU). The DU is called a Baseband Unit (BBU) or a Central Unit (CU). The RU is also called a Remote Radio Head (RRH), a Remote Radio Equipment (RRE), or a Distributed Unit (DU). The DU and the RU may provide functions of the AS layer provided throughout the RAN by separating them between the DU and the RU. For example, the DU and the RU may be provided in a configuration in which a part of the AS layer (layer 2 / layer 3 or their sublayers, or some functions of the layers) is arranged in the DU and the remaining layers (or some functions of the layers) are arranged in the RU. That is, the processes and operations performed by each of the LTE eNB2 and NR NB3 described in the above embodiments may be provided by any one or more radio stations (or RAN nodes).
[0251] The NR NB 3 may be configured to dynamically change the allocation of AS layers or functions to the DU and RU. In other words, the NR NB 3 may be configured to dynamically change the AS layers or function split point between the DU and the RU. For example, the NR NB 3 may be configured to dynamically select one from a plurality of different functional split options. In this case, in the LTE to NR HO procedure of some of the above-mentioned embodiments, the NG Core 5 may determine the allocation of the AS layers or functions to the DU and RU of the NR NB 3 in response to receiving a Handover Preparation Required message or an NR Path Switch Request message. Alternatively, the NR NB 3 may determine the allocation of the AS sublayers or functions to the DU and RU of the NR NB 3. The NG Core 5 or the NR NB 3 may select one functional split option to be applied to the NR NB 3 from a plurality of predefined functional split options.
[0252] In one example, the function separation option applied to the NR NB 3 may be determined (selected) based on the E-RAB QoS information IE, e.g. QCI, ARP, or flow information, etc., included in the Handover Preparation Required message or the NR Path Switch Request message. Additionally or alternatively, the function separation option applied to the NR NB 3 may be determined based on slices or information on slices (slice information) generated by the NG Core 5 or the NR NB 3. Additionally or alternatively, the function separation option applied to the NR NB 3 may be determined based on network slice support information included in the NAS information transmitted from the UE 1.
[0253] In addition, in some of the above-mentioned embodiments, a UE identifier may be included in messages transmitted between each node, and the UE identifier is used to identify the handed-over UE 1 in the handover procedure.
[0254] More specifically, the UE identifier may be a UE identifier used on an interface (e.g., Sn interface or NG2 interface, n is an integer) between the NR NB 3 and a control node corresponding to the MME of the NG Core 5. This UE identifier may be expressed as NR NB UE SnAP ID (NR NB UE Sn Application Protocol Identifier) or NR NB UE NG2AP ID.
[0255] Alternatively, the UE identifier may be a UE identifier used on an interface between an NR NB3 and an LTE eNB2 (eg, an Xn interface, where n is an integer). This UE identifier may be expressed as an NR NB UE XnAP ID.
[0256] Alternatively, the UE identifier may be a UE identifier used on an interface (e.g., Sm interface, m is an integer) between a control node corresponding to the MME of the NG Core 5 and the MME in the EPC 4. This UE identifier may be expressed as, for example, eMME UE SmAP ID.
[0257] Alternatively, the UE identifier may be a UE identifier used on an interface (e.g., S1 interface, where l is an integer) between a control node corresponding to the MME of the NG Core 5 and the LTE eNB 2 and assigned by the control node. The UE identifier may be expressed as, for example, eMME UE S1AP ID.
[0258] Furthermore, these UE identifiers may be transferred between each node in the handover procedure. Note that Sn, NG2, Sm, Sl, and Xn for identifying each interface described above are merely examples, and other notations may be used.
[0259] Furthermore, the above-described embodiment is merely an example of application of the technical idea obtained by the inventor of the present invention. In other words, the technical idea is not limited to the above-described embodiment, and various modifications are possible.
[0260] For example, some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes.
[0261] (Appendix 1) a target Radio Access Network (RAN) node associated with a second network, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: receiving, on a direct interface, from a source RAN node in the first network, a handover request message requesting a handover of a wireless terminal from a first network to the second network; In response to receiving the handover request message, the method is configured to receive at least one of slice information and flow information from a core network; and configured to control communication of the wireless terminal based on at least one of the slice information and the flow information; The slice information relates to a network slice in the second network to which the wireless terminal is connected, The flow information relates to at least one session established in the second network as a bearerless network for transporting at least one packet flow of the wireless terminal; Target RAN node.
[0262] (Appendix 2) The slice information includes: (a) identification information of a network slice selected for the wireless terminal; (b) type information of a network slice selected for the wireless terminal; or (c) identification information of a network node or network function associated with the network slice selected for the wireless terminal, or any combination thereof. A target RAN node as described in Appendix 1.
[0263] (Appendix 3) 3. The target RAN node of claim 1 or 2, wherein the slice information includes a mobility class or a session class, or both, supported by the network slice selected for the wireless terminal.
[0264] (Appendix 4) the flow information including, for each packet flow of the wireless terminal, a flow identifier and a flow QoS parameter; 4. The target RAN node according to any one of claims 1 to 3.
[0265] (Appendix 5) the at least one processor is configured to receive at least one of the slice information and the flow information from the core network during a handover completion phase after the wireless terminal connects to the target RAN node. 5. The target RAN node according to any one of Supplementary Note 1 to 4.
[0266] (Appendix 6) the handover request message includes security parameters derived by the source RAN node; the at least one processor is configured to derive an Access Stratum (AS) security key from the security parameters. 5. The target RAN node as described in Supplementary Note 5.
[0267] (Appendix 7) The at least one processor is configured to send a path switch request message to the core network during the handover completion phase; The path switch request message triggers the core network to select or generate a network slice for the wireless terminal. 7. The target RAN node according to claim 5 or 6.
[0268] (Appendix 8) The at least one processor is configured to send a path switch request message to the core network during the handover completion phase; the path switch request message triggers the core network to create a bearerless session for the wireless terminal. 7. The target RAN node according to claim 5 or 6.
[0269] (Appendix 9) the at least one processor is configured to transmit at least one of the slice information and the flow information to the wireless terminal. 9. The target RAN node according to any one of Supplementary Note 5 to 8.
[0270] (Appendix 10) the at least one processor is configured to receive at least one of the slice information and the flow information from the core network during a handover preparation phase prior to a handover instruction by the source RAN node to the wireless terminal. 5. The target RAN node according to any one of Supplementary Note 1 to 4.
[0271] (Appendix 11) the at least one processor is configured to determine, for each bearer or flow of the wireless terminal, whether to accept the bearer or flow based on the slice information. 13. The target RAN node as defined in claim 10.
[0272] (Appendix 12) The at least one processor is configured to determine whether each network slice can be accommodated based on the slice information. 12. The target RAN node of claim 10 or 11.
[0273] (Appendix 13) The at least one processor is further configured to receive from the core network, during the handover preparation phase, Non-Access Stratum (NAS) security configuration information and security parameters used by the target RAN node for deriving Access Stratum (AS) security keys. 13. The target RAN node according to any one of Supplementary Notes 10 to 12.
[0274] (Appendix 14) the at least one processor is configured to send a handover request acknowledge message to the source RAN node over the direct interface, the handover request acknowledge message including a transparent container; The transparent container includes a predetermined parameter included in at least one of the slice information and the flow information, or radio resource configuration information generated based on at least one of the slice information and the flow information, or both, and is forwarded by the source RAN node to the radio terminal. 14. The target RAN node according to any one of Supplementary Notes 10 to 13.
[0275] (Appendix 15) The at least one processor is configured to transmit, in the handover preparation phase, a request message to the core network requesting transmission of at least one of the slice information and the flow information; the request message triggers the core network to select or generate a network slice for the wireless terminal. 15. The target RAN node according to any one of Supplementary Notes 10 to 14.
[0276] (Appendix 16) The at least one processor is configured to transmit, in the handover preparation phase, a request message to the core network requesting transmission of at least one of the slice information and the flow information; the request message triggers the core network to create a bearerless session for the wireless terminal. 15. The target RAN node according to any one of Supplementary Notes 10 to 14.
[0277] (Appendix 17) a source Radio Access Network (RAN) node associated with a first network, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: configured to determine a handover of the wireless terminal from the first network to a second network; and configured to transmit, in response to the handover decision, a handover request message on a direct interface to a target RAN node in the second network, requesting a handover of the wireless terminal to the second network; and configured to receive a handover request acknowledge message from the target RAN node over the direct interface, the handover request acknowledge message including a transparent container; transmitting a mobility command message to the wireless terminal, the mobility command message including the transparent container and indicating a handover to the second network; the transparent container includes radio resource configuration information required for the wireless terminal to establish a wireless connection associated with the second network, The radio resource configuration information includes at least one of: (a) first radio resource configuration information generated based on slice information regarding a network slice in the second network to which the wireless terminal is connected; and (b) second radio resource configuration information generated based on flow information regarding at least one session established in the second network as a bearerless network to transfer at least one packet flow of the wireless terminal. Source RAN node.
[0278] (Appendix 18) the at least one processor is configured to derive second security parameters used in the second network from first security parameters used in the first network, and include the second security parameters in the handover request message; the second security parameters are used by the target RAN node for the derivation of an Access Stratum (AS) security key in the second network. 17. The source RAN node as described in Supplementary Note 17.
[0279] (Appendix 19) 1. A method in a target Radio Access Network (RAN) node associated with a second network, comprising: receiving a handover request message from a source RAN node in the first network over a direct interface, the handover request message requesting a handover of the wireless terminal from a first network to the second network; receiving at least one of slice information and flow information from a core network in response to receiving the handover request message; and Controlling communication of the wireless terminal based on at least one of the slice information and the flow information; Equipped with The slice information relates to a network slice in the second network to which the wireless terminal is connected, The flow information relates to at least one session established in the second network as a bearerless network for transporting at least one packet flow of the wireless terminal; method.
[0280] (Appendix 20) 1. A method in a source Radio Access Network (RAN) node associated with a first network, comprising: determining a handover of the wireless terminal from the first network to a second network; transmitting, in response to the handover decision, a handover request message over a direct interface to a target RAN node in the second network requesting handover of the wireless terminal to the second network; receiving a handover request acknowledge message from the target RAN node over the direct interface, the handover request acknowledge message including a transparent container; and sending a mobility command message to the wireless terminal, the mobility command message including the transparent container and indicating a handover to the second network; Equipped with the transparent container includes radio resource configuration information required for the wireless terminal to establish a wireless connection associated with the second network, The radio resource configuration information includes at least one of: (a) first radio resource configuration information generated based on slice information regarding a network slice in the second network to which the wireless terminal is connected; and (b) second radio resource configuration information generated based on flow information regarding at least one session established in the second network as a bearerless network to transfer at least one packet flow of the wireless terminal. method.
[0281] (Appendix 21) 1. A program for causing a computer to perform a method in a target Radio Access Network (RAN) node associated with a second network, the program comprising: The method comprises: receiving a handover request message from a source RAN node in the first network over a direct interface, the handover request message requesting a handover of the wireless terminal from a first network to the second network; receiving at least one of slice information and flow information from a core network in response to receiving the handover request message; and Controlling communication of the wireless terminal based on at least one of the slice information and the flow information; Equipped with The slice information relates to a network slice in the second network to which the wireless terminal is connected, The flow information relates to at least one session established in the second network as a bearerless network for transporting at least one packet flow of the wireless terminal; program.
[0282] (Appendix 22) 1. A program for causing a computer to perform a method in a source Radio Access Network (RAN) node associated with a first network, the method comprising: The method comprises: determining a handover of the wireless terminal from the first network to a second network; transmitting, in response to the handover decision, a handover request message over a direct interface to a target RAN node in the second network requesting handover of the wireless terminal to the second network; receiving a handover request acknowledge message from the target RAN node over the direct interface, the handover request acknowledge message including a transparent container; and sending a mobility command message to the wireless terminal, the mobility command message including the transparent container and indicating a handover to the second network; Equipped with the transparent container includes radio resource configuration information required for the wireless terminal to establish a wireless connection associated with the second network, The radio resource configuration information includes at least one of: (a) first radio resource configuration information generated based on slice information regarding a network slice in the second network to which the wireless terminal is connected; and (b) second radio resource configuration information generated based on flow information regarding at least one session established in the second network as a bearerless network to transfer at least one packet flow of the wireless terminal. program.
[0283] (Appendix 23) A wireless terminal, At least one memory; at least one processor coupled to the at least one memory; Equipped with A wireless terminal, wherein the at least one processor is configured to receive, during a handover from a first network to which the wireless terminal connects to a second network, a handover-related message including at least one of slice information regarding a network slice in the second network and radio resource setting information based on a network slice in the second network from a radio access network (RAN) node of the first network.
[0284] (Appendix 24) The at least one processor: configured to receive from the RAN node a mobility command message indicating a handover from the first network to the second network, the mobility command message being generated by a target RAN node associated with the second network and containing radio resource configuration information required for the wireless terminal to establish a radio connection associated with a network slice in the second network to which the wireless terminal is connected; and configured to establish the radio connection with the target RAN node associated with the second network using the radio resource configuration information. 24. The wireless terminal of claim 23.
[0285] (Appendix 25) The handover-related message further includes flow information relating to at least one session established in the second network for transferring at least one packet flow of the wireless terminal, and radio resource configuration information derived from the flow information. At least one of the following: 25. The wireless terminal of claim 23 or 24.
[0286] (Appendix 26) A core network node, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor is configured to, upon handover of a wireless terminal from a first network to a second network, send slice information regarding a network slice in the second network to which the wireless terminal is connected to a target Radio Access Network (RAN) node associated with the second network. Core network node.
[0287] (Appendix 27) The at least one processor is further configured to send to the target RAN node flow information regarding at least one session established in the second network for transferring at least one packet flow of the wireless terminal upon handover of the wireless terminal from the first network to the second network. 27. A core network node according to claim 26.
[0288] (Appendix 28) the at least one processor is configured to send the slice information to the target RAN node during a handover preparation phase prior to a handover instruction by a source RAN node to the wireless terminal; 28. A core network node according to claim 26 or 27.
[0289] (Appendix 29) the at least one processor is configured to send the slice information to the target RAN node during a handover completion phase after the wireless terminal connects to the target RAN node. 28. A core network node according to claim 26 or 27.
[0290] This application claims priority based on Japanese Patent Application No. 2016-158282, filed on August 10, 2016, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]
[0291] 1 User Equipment (UE) 2 LTE eNodeB (eNB) 3 New Radio (NR) NodeB (NB) 5 NextGen (NG) Core 6 New Radio (NR) NodeB (NB) 7 New Radio (NR) NodeB (NB) 1905 Baseband Processor 1906 Application Processor 1908 Memory 2004 Processor 2005 Memory 2104 Processor 2105 Memory 2202 Processor 2203 Memory
Claims
1. A target Radio Access Network (RAN) node connected to a Fifth Generation (5G) core network, comprising: means for receiving a Handover Request message from a source RAN node connected to the 5G core network at an interface between the target RAN node and the source RAN node; means for transmitting a Handover Request Acknowledge message to the source RAN node, the Handover Request Acknowledge message including a transparent container; The transparent container includes radio resource configuration information to be transferred to a radio terminal via the source RAN node, The Handover Request message includes slice information and flow list information indicating at least one flow to be set up; the slice information identifies a network slice, the network slice being a logical network; At least one flow indicated in the flow list information is configured within a PDU session; The flow list information includes a flow identifier that identifies a flow within the PDU session, and a flow Quality of Service (QoS) parameter corresponding to the flow identified by the flow identifier. Target RAN node.
2. the source RAN node and the target RAN node are both 5G base stations; The target RAN node of claim 1.
3. The radio resource configuration information is generated based on the Handover Request message. A target RAN node according to claim 1 or 2.
4. The radio resource configuration information is generated based on at least one of the flow list information and the slice information. A target RAN node according to any one of claims 1 to 3.
5. A source Radio Access Network (RAN) node connected to a Fifth Generation (5G) core network, comprising: means for sending a Handover Request message to a target RAN node connected to the 5G core network at an interface between the target RAN node and the source RAN node; means for receiving, from the target RAN node, a Handover Request Acknowledge message including a transparent container including radio resource configuration information, at the interface between the target RAN node and the source RAN node; means for transmitting the radio resource setting information to a radio terminal; The Handover Request message includes slice information and flow list information indicating at least one flow to be set up; the slice information identifies a network slice, the network slice being a logical network; At least one flow indicated in the flow list information is configured within a PDU session; The flow list information includes a flow identifier that identifies a flow within the PDU session, and a flow Quality of Service (QoS) parameter corresponding to the flow identified by the flow identifier. Source RAN node.
6. the source RAN node and the target RAN node are both 5G base stations; The source RAN node of claim 5.
7. The radio resource configuration information is generated based on the Handover Request message. A source RAN node according to claim 5 or 6.
8. The radio resource configuration information is generated based on at least one of the flow list information and the slice information. A source RAN node according to any one of claims 5 to 7.
9. 1. A method for a target Radio Access Network (RAN) node connected to a Fifth Generation (5G) core network, comprising: receiving a Handover Request message at an interface between the target RAN node and the source RAN node from a source RAN node connected to the 5G core network; and sending a Handover Request Acknowledge message to the source RAN node, the Handover Request Acknowledge message including a transparent container; The transparent container includes radio resource configuration information to be transferred to a radio terminal via the source RAN node, The Handover Request message includes slice information and flow list information indicating at least one flow to be set up; the slice information identifies a network slice, the network slice being a logical network; At least one flow indicated in the flow list information is configured within a PDU session; The flow list information includes a flow identifier that identifies a flow within the PDU session, and a flow Quality of Service (QoS) parameter corresponding to the flow identified by the flow identifier. method.
10. the source RAN node and the target RAN node are both 5G base stations; 10. The method of claim 9.
11. The radio resource configuration information is generated based on the Handover Request message.
11. The method according to claim 9 or 10.
12. The radio resource configuration information is generated based on at least one of the flow list information and the slice information. The method according to any one of claims 9 to 11.
13. 1. A method for a source Radio Access Network (RAN) node connected to a Fifth Generation (5G) core network, comprising: sending a Handover Request message to a target RAN node connected to the 5G core network at an interface between the target RAN node and the source RAN node; receiving a Handover Request Acknowledge message from the target RAN node at the interface between the target RAN node and the source RAN node, the Handover Request Acknowledge message including a transparent container containing radio resource configuration information; and transmitting the radio resource setting information to a radio terminal; The Handover Request message includes slice information and flow list information indicating at least one flow to be set up; the slice information identifies a network slice, the network slice being a logical network; At least one flow indicated in the flow list information is configured within a PDU session; The flow list information includes a flow identifier that identifies a flow within the PDU session, and a flow Quality of Service (QoS) parameter corresponding to the flow identified by the flow identifier. method.
14. the source RAN node and the target RAN node are both 5G base stations; The method of claim 13.
15. The radio resource configuration information is generated based on the Handover Request message.
15. The method according to claim 13 or 14.
16. The radio resource configuration information is generated based on at least one of the flow list information and the slice information. The method according to any one of claims 13 to 15.
Citation Information
Patent Citations
Method and apparatus for managing handovers
US20150264609A1
Interworking with bearer-based system
WO2015160329A1
