Handling UE in CM-CONNECTED state and RRC inactive state
By receiving and processing UE's context requests on 5G network nodes, the data forwarding problem when UE moves from 5GS to EPS in the RRC_INACTIVE state is solved, and the continuity and accuracy of data forwarding are achieved, improving the user experience.
Patent Information
- Application Number
- CN202080042746.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-06-12
- Filing Date
- 2020-06-12
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-06-12
AI Technical Summary
In the RRC_INACTIVE state, when the UE moves from 5GS to EPS, the lack of a mechanism to manage user plane resources, resulting in data forwarding problems. Especially when the UE is configured with RAN notification areas of LTE/EPC and NR cells, it is impossible to forward effectively. data.
By receiving the UE's context request at the 5G network node, the data forwarding information is determined, and the context response, including data forwarding information is sent to the EPS network node, to ensure that the data is not lost during the mobility transfer process, and the necessary user plane resources are established. The specific steps include retrieving data forwarding information from NG-RAN, sending requests to SMF and UPF to obtain the bearer context, and forwarding the buffered data in a timely manner.
Effectively reduces packet loss, improves end-user performance, and ensures the continuity and accuracy of data during the mobility transfer process.
Smart Images

Figure CN113994763B_ABST
Abstract
Description
[0001] Related Applications
[0002] This application claims the benefit of provisional patent application serial number 62 / 860,603, filed on June 12, 2019, the disclosure of which is hereby incorporated by reference in its entirety. Technical Field
[0003] The present disclosure relates to operation of a wireless device in an inactive state. Background Art
[0004] The 3rd Generation Partnership Project (3GPP) has decided to introduce both a new fifth generation (5G) core network (5GC) and a new radio access technology (RAT) called New Radio (NR) in the 5G System (5GS). However, the core network 5GC will also support other RATs besides NR, namely Evolved Universal Terrestrial Radio Access (E-UTRA).
[0005] Figure 1 The network architecture of the evolved packet system (EPS) and 5GS is shown, showing the evolved universal terrestrial radio access network (E-UTRAN) including long term evolution (LTE) nodes, i.e. enhanced or evolved Node Bs (eNBs), connected to the evolved packet core (EPC), and the next generation (NG) radio access network (RAN) NG-RAN including LTE nodes (e.g. NG-eNBs) and NR nodes (e.g. new radio base stations (gNBs)) connected to the 5GC.
[0006] LTE nodes connected to the EPC (LTE / EPC) can interconnect with the X2 interface, while NG-RAN nodes (NR and LTE / 5GC) can interconnect with the Xn interface. 3GPP has also introduced an interface called N26 between the Mobility Management Entity (MME) in the EPC and the Access and Mobility Management Function (AMF) in the 5GC, which enables interworking between the EPC and 5GC.
[0007] Figure 2 The diagram illustrates the state transitions currently supported in LTE (E-UTRA) and NR connected to EPC or 5GC. It can be seen that it is possible to move an ongoing user equipment (UE) connection (UE is in RRC_CONNECTED) between two RATs using a handover procedure. In addition, (not shown) it is possible for the network to move the UE to another RAT by sending a release message with redirection information. When the UE is in the radio resource control (RRC) idle or RRC inactive state, a cell reselection procedure will be used when switching between RATs.
[0008] also, Figure 2 The new RRC state RRC_INACTIVE introduced in Release (Rel-) 15 for both NR and LTE / 5GC is shown. In RRC_INACTIVE, the UE stores certain configurations, such as data radio bearer (DRB) configurations and physical layer parameters. When the UE needs to resume the connection, it transmits an RRCConnectionResumeRequest or RRCResumeRequest in LTE and NR, respectively. The UE can then reuse the stored settings and reduce the time and signaling required for correct operation in RRC_CONNECTED (e.g., in the RRC_INACTIVE state, security and core network (CN) connections are restored upon resumption).
[0009] NOTE: In NR, there is an equivalent message for the case of a 40-bit long RRC_INACTIVE mode Radio Network Temporary Identifier (I-RNTI) used as the UE identifier RRCResumeRequest1, which is associated with a different logical channel compared to the short I-RNTI used in the RRCResumeRequest message.
[0010] In Rel-15 (first release) of the NG-RAN standard, it has been agreed that direct transition between RRC_INACTIVE in LTE / 5GC and RRC_INACTIVE in NR is not supported. Therefore, a Rel-15 UE in RRC_INACTIVE state in one RAT performing cell reselection to another RAT will trigger the UE to release its AS context, enter RRC_IDLE and perform a mobility registration update / tracking area update.
[0011] Inter-system RAN Notification Area: It has been proposed to configure a UE with a RAN Notification Area (RNA) that includes both LTE / EPC cells and NR cells, so that the UE can freely reselect between cells without signaling anything to the network. If the UE reselects an LTE / EPC cell within a UE-specific RNA, the UE will remain in the RRC_INACTIVE state. If the UE needs to connect to the network while camping on an LTE / EPC cell, it enters RRC_IDLE and triggers a Tracking Area Update (TAU) in the EPC.
[0012] To ensure reachability of the UE even when the UE is camping in LTE / EPC, it is proposed to introduce RAN paging for X2 so that if the UE is paged in a LTE / EPC cell while in RRC_INACTIVE state, it will enter RRC_IDLE state and trigger a TAU in EPC.
[0013] Even in the case where the RNA includes only NR cells, the UE can enter the LTE / EPC cell and trigger a TAU toward the EPC.
[0014] Tracking Area Update (TAU): When a UE enters a cell that does not belong to its configured Tracking Area Identity (TAI) list and the UE is connected to the EPC, this will trigger a non-access stratum (NAS) TAU by transmitting a Tracking Area Update Request (TRACKING AREA UPDATEREQUEST) to the target MME (shown below from 3GPP Technical Specification (TS) 24.301 Version 15.5.0), and the target MME can respond with a Tracking Area Update (TRACKING AREA UPDATE) Accept. In NR, a similar procedure is defined, called Mobility Registration Update, where the UE sends a Registration Update Request (REGISTRATION UPDATEREQUEST) instead.
[0015] There are some challenges. In the RRC_INACTIVE state, at least one PDU session has user plane resources, namely the N3 General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnel between the UPF terminating N6 and the NG-RAN terminating N3 and the associated DRB established. This means that any Mobile Terminated (MT) data is buffered or forwarded in or to the NG-RAN and the AMF is not aware of this.
[0016] The NAS entities in the AMF and in the UE are in the Configuration Management (CM)-CONNECTED state. If a UE in RRC_INACTIVE state moves from 5GS to EPS, the UE shall perform a Tracking Area Update procedure to move the UE context from the old AMF to the new MME. However, there is no mechanism describing how to manage user plane resources. For example, in a scenario where the UE is configured with an RNA that includes both LTE / EPC cells and NR cells, there is no means to forward data that triggers RAN paging in the old NG-RAN to the UE connected to the eNB in EPS. Summary of the invention
[0017] Systems and methods for handling wireless devices in a CM-Connected state and an RRC inactive state are provided. In some embodiments, a method for performing a mobility transfer from a fifth generation (5G) network to an evolved packet system (EPS) network includes a 5G network node: receiving a context request for a context associated with a user equipment (UE) from an EPS network node; determining data forwarding information associated with the UE; and sending a context response including context information associated with the UE and data forwarding information associated with the UE to the EPS network node. In this way, packet loss will be minimized, resulting in improved end-user performance.
[0018] In some embodiments, upon UE context transfer from old AMF to new MME triggered by TAU request in EPS, and if the UE state in AMF is CM-CONNECTED state, the AMF provides the MME with information about the need to establish an EPS bearer that can serve the PDU session subject to the transfer of EPS based on the information retrieved from NG-RAN and SMF. The AMF and MME also communicate data forwarding tunnel information for possible data forwarding between NG-RAN and E-UTRAN. The MME implements the need for user plane resource establishment based on the indication from AMF in the GTPv2 context response.
[0019] In some embodiments, the 5G network node includes an access and mobility management function (AMF). In some embodiments, the EPS network node includes a mobility management entity (MME).
[0020] In some embodiments, the context request includes current UE location information. In some embodiments, the current UE location information includes at least one of: a current Tracking Area Identity (TAI); and an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Cell Global Identifier (eCGI).
[0021] In some embodiments, determining NG data forwarding information associated with the UE includes receiving an indication of data forwarding information associated with the UE from a session management function (SMF).
[0022] In some embodiments, determining data forwarding information includes: sending a first request for data forwarding information associated with the UE to a 5G Node B (gNB) within the NG-RAN; receiving a first response from the gNB including the data forwarding information associated with the UE; sending a second request for bearer context information associated with the UE to an SMF and / or a user plane function (UPF), the second request including the data forwarding information associated with the UE; and receiving a second response from the SMF and / or UPF, the second response including the bearer context information associated with the UE, a buffered download data waiting indication associated with the UE, and a direct or indirect forwarding indication associated with the UE; and wherein sending the data forwarding information includes sending the buffered download data waiting indication and the direct or indirect forwarding indication.
[0023] In some embodiments, the first request comprises an N2 data forwarding information request message, and the first response comprises an N2 data forwarding information response message. In some embodiments, the data forwarding information associated with the UE comprises at least one of: a protocol data unit (PDU) session identifier (ID) with buffered data; a direct or indirect forwarding indication; and information identifying a forwarding container.
[0024] In some embodiments, the second request includes a Nsmf_PDUSessionContext request message, and the second response includes a Nsmf_PDUSessionContext response message.
[0025] In some embodiments, direct forwarding is indicated by the presence of a direct forwarding indicator in the second response, and wherein indirect forwarding is indicated by the absence of a direct forwarding indicator in the second response.
[0026] In some embodiments, the method further comprises: receiving a context acknowledgement including a general packet radio service (GPRS) tunneling protocol (GTP) user plane (GTP-U) tunnel information from an EPS node; and sending the GTP-U tunnel information to a NG-RAN. In some embodiments, receiving the GTP-U tunnel information comprises receiving a fully-qualified tunnel endpoint identifier (F-TEID). In some embodiments, sending the GTP-U tunnel information to the NG-RAN comprises sending an N2 forwarding information request message including the GTP-U tunnel information.
[0027] In some embodiments, a method for performing a mobility transfer from a 5G network to an EPS network includes an EPS network node: sending a context request for a context associated with a user equipment (UE) to a 5G network node; receiving a context response from the 5G network node, the context response including context information associated with the UE and also data forwarding information associated with the UE; and when it is determined that data forwarding is required for the UE, providing the 5G network node with GTP-U tunnel information for forwarding data from the 5G network to the EPS network.
[0028] In some embodiments, a method for performing a mobility transfer from a 5G network to an EPS network includes an NG RAN node: receiving a request for data forwarding information associated with a UE from a 5G network node; and sending a response to the 5G network node including the data forwarding information associated with the UE.
[0029] In some embodiments, a method for performing a mobility transfer from a 5G network to an EPS network includes a first 5G network node: receiving a request for bearer context information associated with a UE from a second 5G network node; and sending a response to the second 5G network node including the bearer context information associated with the UE and a buffered download data waiting indication associated with the UE.
[0030] Certain embodiments may provide one or more of the following technical advantages. When a UE performs a TAU request towards EPS in idle mode mobility and there is data available at the source system, the solution enables EPS bearer establishment required for downlink data forwarding. In this way, packet loss will be minimized, resulting in improved end-user performance. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure and together with the description serve to explain the principles of the disclosure.
[0032] Figure 1 The network architecture of the evolved packet system (EPS) and 5GS is shown, showing the evolved universal terrestrial radio access network (E-UTRAN) including long term evolution (LTE) nodes, i.e. enhanced or evolved Node Bs (eNBs), connected to the evolved packet core (EPC), and the next generation (NG) radio access network (RAN) NG-RAN including LTE nodes (e.g. NG-eNBs) and NR nodes (e.g. new radio base stations (gNBs)) connected to the 5GC;
[0033] Figure 2Diagram showing the state transitions currently supported in LTE (E-UTRA) and NR connected to EPC or 5GC;
[0034] Figure 3 An example of a cellular communication system 300 is illustrated in which embodiments of the present disclosure may be implemented;
[0035] Figure 4 A wireless communication system represented as a 5G network architecture consisting of core network functions (NFs) is illustrated, where the interaction between any two NFs is represented by point-to-point reference points / interfaces;
[0036] Figure 5 Diagram showing the use of service-based interfaces between NFs in the control plane instead of Figure 4 5G network architecture of point-to-point reference points / interfaces used in the 5G network architecture;
[0037] Figure 6 A method for performing a mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure is illustrated;
[0038] Figure 7 is a flow chart illustrating an exemplary method for performing a mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure;
[0039] Figure 8 is a flow chart illustrating an exemplary method for performing a mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure;
[0040] Fig. 9 is a flow chart illustrating an exemplary method for performing a mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure;
[0041] Fig.10 is a flow chart illustrating an exemplary method for performing a mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure;
[0042] Fig.11 illustrates one embodiment of a user equipment (UE) according to some embodiments of the present disclosure;
[0043] Fig.12 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized according to some embodiments of the present disclosure;
[0044] Fig.13 illustrates an exemplary communication system according to some embodiments of the present disclosure;
[0045] Fig.14The present invention illustrates some embodiments of the present invention. Fig.13 An example implementation of a UE, a base station and a host computer according to an embodiment;
[0046] Figures 15 to 18 is a flow chart illustrating a method implemented in a communication system according to some embodiments of the present disclosure; and
[0047] Figures 19 to 21 Depicted are flow charts illustrating some methods implemented in a communication system according to some embodiments of the present disclosure. DETAILED DESCRIPTION
[0048] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments, and illustrate the best mode for practicing the embodiments. When reading the following description according to the attached drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize the application of these concepts that are not particularly proposed herein. It should be understood that these concepts and applications belong to the scope of the present disclosure.
[0049] Radio node: As used herein, a "radio node" is a radio access node or a wireless device.
[0050] Radio access node: As used herein, a "radio access node" or "radio network node" is any node in a radio access network of a cellular communication network that operates to transmit and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to: base stations (e.g., NR base stations (gNBs) in a 3rd Generation Partnership Project (3GPP) fifth generation (5G) new radio (NR) network or enhanced or evolved Node Bs (eNBs) in a 3GPP Long Term Evolution (LTE) network), high power or macro base stations, low power base stations (e.g., micro base stations, pico base stations, home eNBs or the like), and relay nodes.
[0051] Core network node: As used herein, a "core network node" is any type of node in a core network that implements core network functions, including a server or data center. Some examples of 4G (EPC) core network functions implemented on a node include, for example, a mobility management entity (MME), a packet data network gateway (PGW), a service capability exposure function (SCEF), a home subscriber server (HSS), or the like. Examples of 5G core network functions are access and mobility functions (AMF), UPF, session management functions (SMF), authentication server functions (AUSF), network slice selection functions (NSSF), network exposure functions (NEF), network functions (NF) repository functions (NRF), policy control functions (PCF), unified data management (UDM), or the like. Core network functions can be virtualized / containerized on a node, or implemented locally (on-premise) using dedicated physical nodes (computing, storage, and network).
[0052] Wireless Device: As used herein, a "wireless device" is any type of device that has access to (i.e., is served by) a cellular communication network by wirelessly transmitting and / or receiving signals to (one or more) radio access nodes. Some examples of wireless devices include, but are not limited to, user equipment devices (UEs) and machine type communication (MTC) devices in 3GPP networks.
[0053] Network node: As used herein, a "network node" is any node that is either part of the core network or the radio access network of a cellular communication network / system.
[0054] Note that the description given herein focuses on a 3GPP cellular communication system, and therefore, 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to a 3GPP system.
[0055] Note that in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells, and therefore, it is important to note that the concepts described herein apply equally to both cells and beams.
[0056] Figure 3An example of a cellular communication system 300 in which embodiments of the present disclosure may be implemented is illustrated. In the embodiments described herein, the cellular communication system 300 may be a 5G system (5GS) including an NR RAN, an evolved packet system (EPS) including an LTE RAN, or a RAN including both 5GS and EPS components. In this example, the RAN includes base stations 302-1 and 302-2, which are referred to as eNBs in LTE and gNBs in 5G NR, controlling corresponding (macro) cells 304-1 and 304-2. The base stations 302-1 to 302-2 are generally referred to herein as base stations 302, and are individually referred to as base stations 302. Similarly, the (macro) cells 304-1 and 304-2 are generally referred to herein as (macro) cells 304, and are individually referred to as (macro) cells 304. The RAN may also include a plurality of low power nodes 306-1 to 306-4 that control corresponding small cells 308-1 to 308-4. The low power nodes 306-1 to 306-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs) or the like. It is noteworthy that, although not shown, one or more of the small cells 308-1 to 308-4 may alternatively be provided by the base station 302. The low power nodes 306-1 to 306-4 are generally collectively referred to as low power nodes 306 herein, and are individually referred to as low power nodes 306. Similarly, the small cells 308-1 to 308-4 are generally collectively referred to as small cells 308 herein, and are individually referred to as small cells 308. The cellular communication system 300 also includes a core network 310, which is referred to as a 5G core (5GC) in 5GS. The base station 302 (and the optional low power node 306) are connected to the core network 310.
[0057] Base station 302 and low power node 306 provide services to wireless devices 312-1 through 312-5 in corresponding cells 304 and 308. Wireless devices 312-1 through 312-5 are generally referred to herein collectively as wireless devices 312, and individually as wireless devices 312. Wireless devices 312 are also sometimes referred to herein as UEs.
[0058] Figure 4 The figure illustrates a wireless communication system represented as a 5G network architecture consisting of core network functions (NFs), where the interaction between any two NFs is represented by point-to-point reference points / interfaces. Figure 4 can be regarded as Figure 3 A specific implementation of system 300.
[0059] From the access side, Figure 4The 5G network architecture shown in the figure includes multiple user equipment (UE) connected to the radio access network (RAN) or access network (AN) and access and mobility management function (AMF). Typically, the R (AN) includes a base station, such as an evolved Node B (eNB) or a 5G base station (gNB) or similar. From the core network side, Figure 4 The 5G core NFs shown in the figure include network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), AMF, session management function (SMF), policy control function (PCF) and application function (AF).
[0060] The reference point representation of the 5G network architecture is used to develop detailed call flows in the standardization of the specification. The N1 reference point is defined to carry signaling between the UE and the AMF. The reference points for connecting between the AN and the AMF and between the AN and the UPF are defined as N2 and N3, respectively. There is a reference point N11 between the AMF and the SMF, which means that the SMF is at least partially controlled by the AMF. N4 is used by the SMF and the UPF so that the UPF can be set using control signals generated by the SMF, and the UPF can report its status to the SMF. Respectively, N9 is a reference point for connection between different UPFs, and N14 is a reference point for connection between different AMFs. Since the PCF applies policies to the AMF and SMF respectively, N15 and N7 are defined. N12 is required for the AMF to perform authentication of the UE. Because the subscription data of the UE is required for the AMF and the SMF, N8 and N10 are defined.
[0061] The 5G core network is designed to separate the user plane and the control plane. The user plane carries user services, while the control plane carries signaling in the network. Figure 4 In the NF, UPF is in the user plane, while all other NFs, namely AMF, SMF, PCF, AF, AUSF and UDM, are in the control plane. Separating the user plane and the control plane ensures that the resources of each plane are scaled independently. It also allows the UPF to be deployed separately from the control plane functions in a distributed manner. In this architecture, for some applications that require low latency, the UPF can be deployed very close to the UE to shorten the round-trip time (RTT) between the UE and the data network.
[0062] The core 5G network architecture consists of modular functions. For example, AMF and SMF are independent functions in the control plane. Separating AMF and SMF allows independent evolution and scaling. Other control plane functions like PCF and AUSF can be Figure 4 The modular functional design enables the 5G core network to flexibly support various services.
[0063] Each NF interacts directly with another NF. It is possible to use an intermediate function to route messages from one NF to another. In the control plane, a set of interactions between two NFs is defined as a service so that its reuse is possible. The service enables support for modularization. The user plane supports interactions such as forwarding operations between different UPFs.
[0064] Figure 5 Diagram showing the use of service-based interfaces between NFs in the control plane instead of Figure 4 The 5G network architecture uses point-to-point reference points / interfaces in the 5G network architecture. However, the above reference Figure 4 The NF described corresponds to Figure 5 The NF shown in FIG. The service (s) provided by the NF to other authorized NFs can be opened to the authorized NFs through the service-based interface. Figure 5 In the NF, the service-based interface is indicated by the letter "N" followed by the NF name, such as Namf for the service-based interface of AMF and Nsmf for the service-based interface of SMF, etc. Figure 5 The Network Open Function (NEF) and Network Function (NF) Repository Function (NRF) in the above discussion Figure 4 However, it should be clarified that although Figure 4 There is no clear indication, but Figure 4 All NFs depicted in the Figure 5 The NEF and NRF interact.
[0065] It can be described in the following way Figure 4 and 5 Some characteristics of the NF shown in . AMF provides UE-based authentication, authorization, mobility management, etc. Even UEs using multiple access technologies are basically connected to a single AMF because the AMF is independent of the access technology. SMF is responsible for session management and assigns Internet Protocol (IP) addresses to UEs. It also selects and controls UPF for data transfer. If the UE has multiple sessions, a different SMF may be assigned to each session to manage them individually, and possibly each session provides different functionality. AF provides information about packet flows to the PCF responsible for policy control in order to support Quality of Service (QoS). Based on this information, the PCF determines policies on mobility and session management so that the AMF and SMF operate correctly. AUSF supports the authentication function of the UE or the like, and thereby stores data for authentication of the UE or the like, while the UDM stores subscription data for the UE. The data network (DN), which is not part of the 5G core network, provides Internet access or operator services and similar services.
[0066] NFs may be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on a suitable platform (e.g., cloud infrastructure).
[0067] When a UE enters a cell that is not in its configured Tracking Area Identity (TAI) list and the UE is connected to the EPC, this will trigger a Non-Access Stratum (NAS) TAU by transmitting a Tracking Area Update Request (shown below from 3GPP Technical Specification (TS) 24.301 Version 15.5.0) to the target MME, which can respond with a Tracking Area Update Accept. In NR, a similar procedure is defined, called Mobility Registration Update, where the UE sends a Registration Update Request instead.
[0068] There are certain challenges currently. In the RRC_INACTIVE state, at least one PDU session has user plane resources, namely, the N3 General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnel between the UPF terminating N6 and the Next Generation (NG) Radio Access Network (RAN) terminating N3 and the associated DRBs established. This means that any mobile terminated (MT) data is buffered or forwarded in or to the NG-RAN and the AMF is not aware of this.
[0069] The NAS entities in the AMF and in the UE are in the Configuration Management (CM)-CONNECTED state. If a UE in RRC_INACTIVE state moves from 5GS to EPS, the UE will perform a Tracking Area Update procedure to move the UE context from the old AMF to the new MME. However, there is no mechanism described on how to manage user plane resources. For example, in a scenario where the UE is configured with a RAN Notification Area (RNA) that includes both LTE / EPC cells and NR cells, there is no means to forward data that triggers RAN paging in the old NG-RAN to the UE connected to the eNB in EPS.
[0070] In some embodiments, when a UE in CM-CONNECTED state with RRC inactive in 5GS moves to EPS, the UE enters CM-IDLE mode. However, the current interworking idle mode mobility procedures from 5GS to EPS do not cover the case of CM-CONNECTED with RRC inactive, where there may be buffered data in the NG-RAN due to enhanced DRX (eDRX) in RRC inactive state.
[0071] Systems and methods for handling wireless devices in a CM-Connected state and an RRC inactive state are provided. In some embodiments, a method for performing a mobility transfer from a fifth generation (5G) network to an evolved packet system (EPS) network includes a 5G network node: receiving a context request for a context associated with a user equipment (UE) from an EPS network node; determining data forwarding information associated with the UE; and sending a context response including context information associated with the UE and data forwarding information associated with the UE to the EPS network node. In this way, packet loss will be minimized, resulting in improved end-user performance.
[0072] In some embodiments, following the data forwarding principles present in EPS (TS 23.401 clause 5.3.3.1A), a new 5GS to EPS idle mode mobility procedure is introduced using the N26 interface for RRC inactivity and data forwarding.
[0073] Trigger for data forwarding: In some embodiments, the methods described herein are applicable when a UE in CM-CONNECTED state in 5GS and in RRC_INACTIVE state in NG-RAN enters CM-IDLE state in LTE / EPC and triggers a NAS TAU in the EPS network in at least the following scenarios:
[0074] (a) If a UE in RRC_INACTIVE state is configured with a RAN Notification Area (RNA) with both LTE / EPC cells and NR cells, and if mobile terminated (MT) data arrives at the source gNB while the UE is camped on the LTE / EPC cell, the network shall initiate RAN paging over the Xn and X2 interfaces. When the UE receives RAN paging via the LTE / EPC cell, the UE shall transition to RRC_IDLE state and perform NAS TAU in the EPS network; and
[0075] (b) If the UE is in RRC_INACTIVE state with discontinuous reception (DRX) or enhanced DRX (eDRX) activated (in this case, the gNB may be buffering data for the UE to deliver the data to the UE when it wakes up during a DRX / eDRX active period) and if the UE reselects an LTE / EPC cell, the UE shall transition to RRC_IDLE state and perform a NAS TAU in the EPS network.
[0076] Once the MME receives the TAU Request, the MME will request the UE context from the old AMF by sending a Context Request message. Typically, the AMF knows that the UE is in CM-CONNECTED state, and when the AMF receives the Context Request message from the MME, the AMF then becomes aware that the UE is in RRC_INACTIVE state.
[0077] In some embodiments according to the present disclosure, the AMF then requests the gNB to report the state transition of the UE and the need for data forwarding information, and thereby retrieves the buffered data information from the gNB. In some embodiments, the AMF then retrieves the bearer context information from the SMF and / or UPF and forwards the information to the MME in a context response message.
[0078] With this information, the MME then sets up the required user plane resources on the EPS side and also the forwarding tunnel. In some embodiments, the MME then provides this information back to the AMF in a context confirm message. After receiving the context confirm message from the MME, the AMF and / or SMF can use this information to establish a forwarding channel between the 5GS network and the EPS network (e.g. between the 5GS gNB and / or UPF and the EPS Serving Gateway (SGW) and / or eNB). In some embodiments, the AMF and / or SMF provides the gNB with the forwarding address of the involved entity (e.g., eNB or UPF), and the gNB forwards the buffered data directly to the target eNB, or indirectly to the target eNB via the 5G UPF and / or EPS SGW.
[0079] TAU procedure and data forwarding in RRC inactivity: Figure 6 A method for performing mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure is illustrated. Figure 6 is being proposed as a diagram to be included in 3GPP TS 23.502; the diagram is tentatively named " Figure 4 .11.1.3.x-1: 5GS to EPS idle mode mobility and data forwarding using N26 interface in case of RRC inactivity". The proposed changes / improvements to the prior art are as follows: Figure 6 In bold font.
[0080] Below is a corresponding example procedure proposed for TS 23.502 for data forwarding for 5GS to EPS idle mode mobility in RRC_INACTIVE case according to some embodiments of the present disclosure.
[0081] 4.11.1.3.x 5GS to EPS idle mode mobility and data forwarding using N26 interface in RRC inactive state.
[0082] In case of network sharing, the UE selects the target Public Land Mobile Network (PLMN) ID according to clause 5.18.3 of TS 23.501 [2].
[0083] Clause 4.11.1.3.x covers the case of idle mode mobility from 5GC to EPC. The UE performs the Tracking Area Update procedure in E-UTRA / EPS when it moves from NG-RAN / 5GS in CM-CONNECTED state with RRC Inactive to E-UTRA / EPS coverage area.
[0084] The procedure involves tracking area update to the EPC and setup of default EPS bearers and dedicated bearers in the EPC in steps 1-11, and reactivation if required.
[0085] 1-4. Steps 1-4 from clause 4.11.1.3.2 with the following enhancements:
[0086] In the context request message of step 4, the MME may provide the current UE location information (i.e. the current TAI and eCGI from the eNB in step 3).
[0087] 5. If the UE is in CM-CONNECTED state, the AMF retrieves data forwarding information from the NG-RAN by sending an N2 DATA FORWARDING REQUEST message. If it is received, the AMF indicates that the data forwarding target is the E-UTRAN / EPC, and the UE location information received in step 4.
[0088] If there is data buffered for the UE, the NG-RAN provides data forwarding information (PDU session ID with buffered data, direct forwarding availability, forwarding container). Furthermore, the source NG-RAN includes information to assist the target eNB management of this UE in a transparent manner. The NG-RAN uses the UE location information to decide whether direct or indirect forwarding should be used.
[0089] NOTE: RAN3 determines the N2 message between NG-RAN and AMF, which can be a new message or an enhancement of the existing message.
[0090] 6a. Step 5a from clause 4.11.1.3.2 with the following enhancements:
[0091] The AMF also includes in step 5 the data forwarding information from the NG-RAN to the SMF for the PDU session indicated in step 4a.
[0092] 6b. Step 5b from Clause 4.11.1.3.2.
[0093] 6c. Step 5c from clause 4.11.1.3.2 with the following enhancements:
[0094] Based on the data forwarding information from NG-RAN in step 6a, the SMF includes a buffered DL data waiting indication and a direct forwarding indication in the response.
[0095] 7. Step 6 from clause 4.11.1.3.2 with the following enhancements:
[0096] The AMF includes the indication received from the above SMF.
[0097] 8-18. Steps 7-18 from clause 4.11.1.3.2.
[0098] 19-22. If the "Buffered DL Data Pending Indication" is set in step 6, the MME triggers steps 11-14 in clause 5.3.3.1A of TS 23.401 with the following enhancements:
[0099] If "Direct Forwarding Indication" is also set in step 8, the MME may skip step 21 and provide the eNB GTP-U tunnel information as the forwarding F-TEID to the AMF in step 22. Otherwise, the MME provides the SGW GTP-U tunnel information received in step 21 to the AMF as the forwarding F-TEID.
[0100] 23-25. Steps 10a, 10b, 10c in clause 4.11.1.2.1 with the following enhancements:
[0101] If the SMF receives the eNB GTP-U tunnel information in the forwarding F-TEID, the SMF and UPF may skip the allocation of the CN tunnel for data forwarding, and if direct data forwarding is supported, directly provide the eNB GTP-U tunnel as the tunnel information for data forwarding.
[0102] 26. The AMF sends the tunnel information for data forwarding to the NG-RAN in the N2 Forwarding Information message.
[0103] NOTE: RAN3 determines the N2 message between NG-RAN and AMF, which can be a new message or an enhancement of the existing message.
[0104] 27. After the timer started in step 7 expires, the AMF initiates the N2 UE context release procedure.
[0105] Figure 7 is a flow chart illustrating an exemplary method for performing mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure. Figure 7The method performed at a 5G network node such as an AMF is illustrated. Figure 7 In the embodiment shown in , the method includes the following steps. Step 700: Receive a context request for a context associated with a UE from an EPS network node. Step 702: Determine data forwarding information associated with the UE. In some embodiments, the information is received from an SMF. In some embodiments, the information is received from a RAN node. Step 704: Send a context response including context information associated with the UE and data forwarding information associated with the UE to the EPS network node.
[0106] Figure 8 is a flow chart illustrating an exemplary method for performing mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure. Figure 8 The method is illustrated as being performed at an EPS network node such as an MME. Figure 8 In the embodiment shown in , the method includes the following steps. Step 800: Send a context request for a context associated with the UE to a 5G network node. Step 802: Receive a context response including context information associated with the UE and also data forwarding information associated with the UE from the 5G network node. Step 804: When determining that data forwarding is required for the UE, provide the 5G network node with GTP-U tunnel information for forwarding data from the 5G network to the EPS network.
[0107] Fig. 9 is a flow chart illustrating an exemplary method for performing mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure. Fig. 9 The method is illustrated as being performed at a NG-RAN network node such as a gNB. Fig. 9 In the embodiment shown in , the method comprises the following steps: Step 900: Receive a request for data forwarding information associated with the UE from a 5G network node. Step 902: Send a response including the data forwarding information associated with the UE to the 5G network node.
[0108] Fig.10 is a flow chart illustrating an exemplary method for performing mobility transfer from a 5G network to an EPS network according to some embodiments of the present disclosure. Fig. 9 The method is illustrated as being performed at a 5G network node such as an SMF. Fig.10In the embodiment shown in , the method includes the following steps. Step 1000: Receive a request for bearer context information associated with the UE from a second 5G network node such as an AMF, the request including data forwarding information associated with the UE. Step 1002: Send a response to the second 5G network node, the response including the bearer context information associated with the UE, a buffered download data waiting indication associated with the UE, and a direct or indirect forwarding indication associated with the UE.
[0109] Fig.11 1 is a schematic block diagram of a radio access node 1100 according to some embodiments of the present disclosure. The radio access node 1100 may be, for example, a base station 302 or 306. As shown, the radio access node 1100 includes a control system 1102, which includes one or more processors 1104 (e.g., a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or the like), a memory 1106, and a network interface 1108. The one or more processors 1104 are also referred to herein as processing circuits. In addition, the radio access node 1100 includes one or more radio units 1110, each of which includes one or more transmitters 1112 and one or more receivers 1114 coupled to one or more antennas 1116. The radio unit 1110 may be referred to as a radio interface circuit, or may be part of a radio interface circuit. In some embodiments, the radio unit(s) 1110 is external to the control system 1102 and is connected to the control system 1102 via, for example, a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 1110 and potentially the antenna(s) 1116 are integrated with the control system 1102. The one or more processors 1104 operate to provide one or more functions of the radio access node 1100 as described herein. In some embodiments, the function(s) are implemented in software stored, for example, in the memory 1106 and executed by the one or more processors 1104.
[0110] Fig.12 1 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1100 according to some embodiments of the present disclosure. The discussion is equally applicable to other types of network nodes. In addition, other types of network nodes may have similar virtualized architectures.
[0111] As used herein, a "virtualized" radio access node is an implementation of a radio access node 1100 in which at least a portion of the functionality of the radio access node 1100 is implemented as (one or more) virtual components (e.g., via (one or more) virtual machines executed on (one or more) physical processing nodes in (one or more) networks). As shown, in this example, the radio access node 1100 includes: a control system 1102, the control system 1102 including one or more processors 1104 (e.g., CPU, ASIC, FPGA and / or the like), a memory 1106 and a network interface 1108; and one or more radio units 1110, each of which includes one or more transmitters 1112 and one or more receivers 1114 coupled to one or more antennas 1116, as described above. The control system 1102 is connected to the (one or more) radio units 1110 via, for example, optical cables or the like. Control system 1102 is connected via network interface 1108 to one or more processing nodes 1200, which are coupled to or included as part of network(s) 1202. Each processing node 1200 includes one or more processors 1204 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1206, and network interface 1208.
[0112] In this example, the functions 1210 of the radio access node 1100 described herein are implemented at one or more processing nodes 1200 or distributed across the control system 1102 and one or more processing nodes 1200 in any desired manner. In some specific embodiments, some or all of the functions 1210 of the radio access node 1100 described herein are implemented as virtual components that are executed by one or more virtual machines that are implemented in (one or more) virtual environments hosted by (one or more) processing nodes 1200. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the (one or more) processing nodes 1200 and the control system 1102 is used in order to implement at least some of the desired functions 1210. It is worth noting that in some embodiments, the control system 1102 may not be included, in which case the (one or more) radio units 1110 communicate directly with the (one or more) processing nodes 1200 via (one or more) appropriate network interfaces.
[0113] In some embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to implement a node (e.g., processing node 1200) or functionality of the radio access node 1100 that implements one or more of the functions 1210 of the radio access node 1100 in a virtual environment according to any of the embodiments described herein. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).
[0114] Fig.13 is a schematic block diagram of a radio access node 1100 according to some other embodiments of the present disclosure. The radio access node 1100 includes one or more modules 1300, each of which is implemented in software. The module(s) 1300 provide the functionality of the radio access node 1100 described herein. The discussion also applies to Fig.12 1200 , where module 1300 may be implemented at one of processing nodes 1200 and / or distributed across multiple processing nodes 1200 and / or distributed across (one or more) processing nodes 1200 and control system 1102 .
[0115] Fig.14 1400 is a schematic block diagram of a UE 1400 according to some embodiments of the present disclosure. As shown, the UE 1400 includes one or more processors 1402 (e.g., CPU, ASIC, FPGA and / or the like), a memory 1404, and one or more transceivers 1406, each of which includes one or more transmitters 1408 and one or more receivers 1410 coupled to one or more antennas 1412. The (one or more) transceivers 1406 include radio front-end circuitry connected to the (one or more) antennas 1412, which is configured to condition signals transmitted between the (one or more) antennas 1412 and the (one or more) processors 1402, as will be appreciated by one of ordinary skill in the art. The processor 1402 is also referred to herein as a processing circuit. The transceiver 1406 is also referred to herein as a radio circuit. In some embodiments, the functionality of the UE 1400 described above may be implemented in whole or in part using software stored in the memory 1404 and executed by the (one or more) processors 1402, for example. Note that the UE 1400 may include Fig.14Additional components not shown, such as, for example, one or more user interface components (e.g., input / output interfaces including displays, buttons, touch screens, microphones, (one or more) speakers, and / or the like, and / or any other components for allowing information to be input into and / or output from UE 1400), a power source (e.g., a battery and associated power circuitry), etc.
[0116] In some embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to implement the functionality of the UE 1400 according to any of the embodiments described herein. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).
[0117] Fig.15 1400 according to some other embodiments of the present disclosure. The UE 1400 includes one or more modules 1500, each of which is implemented in software. The module(s) 1500 provide the functionality of the UE 1400 described herein.
[0118] Fig.16 A communication system according to some embodiments of the present disclosure is illustrated. Fig.16 According to an embodiment, a communication system includes a telecommunications network 1600, such as a 3GPP type cellular network, which includes an access network 1602 such as a RAN and a core network 1604. The access network 1602 includes a plurality of base stations 1606A, 1606B, 1606C, such as NBs, eNBs, gNBs or other types of wireless access points (APs), each of which defines a corresponding coverage area 1608A, 1608B, 1608C. Each base station 1606A, 1606B, 1606C is connectable to the core network 1604 via a wired or wireless connection 1610. A first UE 1612 located in the coverage area 1608C is configured to be wirelessly connected to or paged by the corresponding base station 1606C. A second UE 1614 in the coverage area 1608A is wirelessly connectable to the corresponding base station 1606A. Although multiple UEs 1612 , 1614 are illustrated in this example, the disclosed embodiments are equally applicable to scenarios where a single UE is in the coverage area or where a single UE is connecting to the corresponding base station 1606 .
[0119] The telecommunications network 1600 itself is connected to a host computer 1616, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 1616 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections 1618 and 1620 between the telecommunications network 1600 and the host computer 1616 may extend directly from the core network 1604 to the host computer 1616, or may be made via an optional intermediate network 1622. The intermediate network 1622 may be one or a combination of more than one of a public, private, or managed network; the intermediate network 1622, if any, may be a backbone network or the Internet; in particular, the intermediate network 1622 may include two or more sub-networks (not shown).
[0120] Fig.16 The communication system as a whole enables connectivity between connected UEs 1612, 1614 and a host computer 1616. This connectivity can be described as an over-the-top (OTT) connection 1624. The host computer 1616 and the connected UEs 1612, 1614 are configured to use the access network 1602, the core network 1604, any intermediate networks 1622, and possible additional infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection 1624. The OTT connection 1624 can be transparent in the sense that the participating communication devices through which the OTT connection 1624 passes are unaware of the routing of uplink and downlink communications. For example, the base station 1606 may not or need not be informed of the past routing of incoming downlink communications, which have data originating from the host computer 1616 to be forwarded (e.g., handed over) to the connected UE 1612. Similarly, the base station 1606 need not be aware of the future routing of outbound uplink communications originating from the UE 1612 to the host computer 1616 .
[0121] Fig.17 A communication system according to some embodiments of the present disclosure is illustrated. Fig.17An example implementation of the UE, base station, and host computer discussed in the previous paragraphs according to one embodiment is described. In the communication system 1700, the host computer 1702 includes hardware 1704, which includes a communication interface 1706 configured to establish and maintain a wired or wireless connection to the interface of different communication devices of the communication system 1700. The host computer 1702 further includes a processing circuit 1708 that may have storage and / or processing capabilities. In particular, the processing circuit 1708 may include one or more programmable processors, ASICs, FPGAs, or a combination of these (not shown) suitable for executing instructions. The host computer 1702 further includes software 1710, which is stored in the host computer 1702 or accessible by the host computer 1702 and executable by the processing circuit 1708. The software 1710 includes a host application 1712. The host application 1712 may be operable to provide services to a remote user, such as a UE 1714 connected via an OTT connection 1716 terminating between the UE 1714 and the host computer 1702. In providing services to the remote user, the host application 1712 may provide user data transmitted using the OTT connection 1716.
[0122] The communication system 1700 further includes a base station 1718, which is arranged in the telecommunication system and includes hardware 1720 that enables it to communicate with the host computer 1702 and with the UE 1714. The hardware 1720 may include a communication interface 1722 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 1700, and for establishing and maintaining a connection with at least a network located in a coverage area ( Fig.17 The communication interface 1722 may be configured to facilitate a connection 1728 to the host computer 1702. The connection 1728 may be direct, or it may pass through a core network (eg, a wireless network) of the telecommunications system. Fig.17 1718) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1720 of the base station 1718 further includes processing circuitry 1730, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these (not shown) adapted to execute instructions. The base station 1718 further has software 1732 stored internally or accessible via an external connection.
[0123] The communication system 1700 further includes the UE 1714 already mentioned. The hardware 1734 of the UE 1714 may include a radio interface 1736, which is configured to establish and maintain a wireless connection 1726 with a base station serving a coverage area in which the UE 1714 is currently located. The hardware 1734 of the UE 1714 further includes a processing circuit 1738, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these (not shown) suitable for executing instructions. The UE 1714 further includes software 1740, which is stored in or accessible by the UE 1714 and executable by the processing circuit 1738. The software 1740 includes a client application 1742. The client application 1742 may be operable to provide services to human or non-human users via the UE 1714 with the support of the host computer 1702. In the host computer 1702, the executing host application 1712 can communicate with the executing client application 1742 via an OTT connection 1716 terminated at the UE 1714 and the host computer 1702. When providing services to users, the client application 1742 can receive request data from the host application 1712 and provide user data in response to the request data. The OTT connection 1716 can transmit both the request data and the user data. The client application 1742 can interact with the user to generate the user data it provides.
[0124] Notice, Fig.17 The host computer 1702, base station 1718 and UE 1714 shown in the figure can be respectively Fig.16 The host computer 1616, one of the base stations 1606A, 1606B, 1606C, and one of the UEs 1612, 1614 may be similar or identical. That is, the internal workings of these entities may be similar to Fig.17 As shown in , and independently, the surrounding network topology can be Fig.16 network topology.
[0125] exist Fig.17 17, OTT connection 1716 has been abstractly drawn to illustrate communication between host computer 1702 and UE 1714 via base station 1718, without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from UE 1714 or the service provider operating host computer 1702, or both. When OTT connection 1716 is active, the network infrastructure can further make decisions by which it dynamically changes the routing (e.g., based on network reconfiguration or load balancing considerations).
[0126] The wireless connection 1726 between the UE 1714 and the base station 1718 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of OTT services provided to the UE 1714 using the OTT connection 1716, wherein the wireless connection 1726 forms the last segment. More specifically, when the UE performs a TAU request towards the EPS with idle mode mobility and there is data available at the source system, the teachings of these embodiments enable the EPS bearer setup required for downlink data forwarding, and thereby provide benefits such as minimizing packet loss, which results in improved end-user performance.
[0127] For the purpose of monitoring the data rate, latency, and other factors improved by one or more embodiments, a measurement process may be provided. There may further be optional network functionality for reconfiguring the OTT connection 1716 between the host computer 1702 and the UE 1714 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 1716 may be implemented with the software 1710 and hardware 1704 of the host computer 1702, or with the software 1740 and hardware 1734 of the UE 1714, or with both. In some embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1716 passes; the sensor may participate in the measurement process by supplying the values of the monitored quantities exemplified above, or supplying the values of other physical quantities according to which the software 1710, 1740 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1716 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration need not affect the base station 1718, and it may be unknown or imperceptible to the base station 1718. Such processes and functionality may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 1702 to measure throughput, propagation time, latency, and the like. The measurements may be achieved because the software 1710 and 1740 uses the OTT connection 1716 to cause messages (particularly empty or "dummy" messages) to be transmitted while it monitors propagation time, errors, etc.
[0128] Fig.18 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.16 and 17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig.18In step 1800, the host computer provides user data. In sub-step 1802 of step 1800 (which may be optional), the host computer provides the user data by executing a host application. In step 1804, the host computer initiates a transmission to the UE carrying the user data. In step 1806 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 1808 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
[0129] Fig.19 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.16 and 17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig.19 Reference is made to the accompanying drawings of . In step 1900 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1902, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout this disclosure, the transmission may be delivered via a base station. In step 1904 (which may be optional), the UE receives the user data carried in the transmission.
[0130] Fig. 20 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.16 and 17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig. 20. In step 2000 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2002, the UE provides user data. In sub-step 2004 of step 2000 (which may be optional), the UE provides the user data by executing a client application. In sub-step 2006 of step 2002 (which may be optional), the UE executes a client application that provides the user data as a reaction to the received input data provided by the host computer. When providing the user data, the executed client application may further consider the user input received from the user. Regardless of the specific manner in which the user data is provided, in sub-step 2008 (which may be optional), the UE initiates the transmission of the user data to the host computer. In step 2010 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives the user data transmitted from the UE.
[0131] Fig.21 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.16 and 17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig.21 In step 2100 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 2102 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2104 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.
[0132] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple of these functional units. These functional units may be implemented via processing circuits and other digital hardware, the processing circuits may include one or more microprocessors or microcontrollers, and the other digital hardware may include digital signal processors (DSPs), dedicated digital logic and the like. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for implementing one or more of the technologies described herein. In some implementations, a processing circuit may be used to cause the corresponding functional unit to perform the corresponding functions according to one or more embodiments of the present disclosure.
[0133] Although the processes in the figures may illustrate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.). Example
[0134] Group A Example - 5G AMF
[0135] Embodiment 1: A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system EPS network, the method comprising: at a 5G network node: receiving a context request for a context associated with a user equipment UE from an EPS network node; determining data forwarding information associated with the UE from a next generation NG radio access network RAN NG-RAN; and sending a context response including the context information associated with the UE and also the data forwarding information associated with the UE to the EPS network node.
[0136] Embodiment 2: The method of embodiment 1, wherein the 5G network node includes an access and mobility management function AMF.
[0137] Embodiment 3: The method of embodiment 1 or 2, wherein the EPS network node includes a mobility management entity MME.
[0138] Embodiment 4: The method of any of embodiments 1-3, wherein the context request includes current UE location information.
[0139] Embodiment 5: The method of embodiment 4, wherein the current UE location information includes at least one of the following: a current tracking area identity TAI; and an evolved universal terrestrial radio access network E-UTRAN cell global identifier eCGI.
[0140] Embodiment 6: The method of any embodiment of Embodiments 1-5, wherein determining data forwarding information comprises: sending a first request for data forwarding information associated with the UE to a 5G Node B gNB within the NG-RAN; receiving a first response including the data forwarding information associated with the UE from the gNB; sending a second request for bearer context information associated with the UE to a session management function SMF and / or a user plane function UPF, the second request including the data forwarding information associated with the UE; and receiving a second response from the SMF and / or UPF, the second response including the bearer context information associated with the UE, a buffered download data waiting indication associated with the UE, and a direct or indirect forwarding indication associated with the UE; and wherein sending the data forwarding information comprises sending the buffered download data waiting indication and the direct or indirect forwarding indication.
[0141] Embodiment 7: The method of embodiment 6, wherein the first request includes an N2 data forwarding information request message, and the first response includes an N2 data forwarding information response message.
[0142] Embodiment 8: The method of embodiment 6 or 7, wherein the data forwarding information associated with the UE includes at least one of the following: a protocol data unit PDU session identifier ID having buffered data; a direct or indirect forwarding indication; and information identifying a forwarding container.
[0143] Embodiment 9: The method of Embodiment 8, wherein the second request includes an Nsmf_PDUSessionContext request message, and the second response includes an Nsmf_PDUSessionContext response message.
[0144] Embodiment 10: The method of Embodiment 6 or 9, wherein direct forwarding is indicated by the presence of a direct forwarding indicator in the second response, and wherein indirect forwarding is indicated by the absence of a direct forwarding indicator in the second response.
[0145] Embodiment 11: The method of any embodiment in Embodiments 1-10 further comprises: receiving a context confirmation including General Packet Radio Service GPRS Tunneling Protocol GTP User Plane GTP-U tunnel information from an EPS node; and sending the GTP-U tunnel information to NG-RAN.
[0146] Embodiment 12: The method of embodiment 11, wherein receiving the GTP-U tunnel information comprises receiving a forwarding-complete tunnel endpoint identifier F-TEID.
[0147] Embodiment 13: The method of Embodiment 11 or 12, wherein sending the GTP-U tunnel information to the NG-RAN includes sending an N2 forwarding information request message including the GTP-U tunnel information.
[0148] Group B Example - EPS MME
[0149] Embodiment 14: A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system EPS network, the method comprising: at an EPS network node: sending a context request for a context associated with a user equipment UE to a 5G network node; receiving a context response from the 5G network node, the context response comprising context information associated with the UE and also data forwarding information associated with the UE; and when it is determined that data forwarding is required for the UE, providing the 5G network node with General Packet Radio Service GPRS Tunneling Protocol GTP User Plane GTP-U tunnel information for forwarding data from the 5G network to the EPS network.
[0150] Embodiment 15: The method of embodiment 14, wherein the EPS network node includes a mobility management entity MME.
[0151] Embodiment 16: The method of embodiment 14 or 15, wherein the 5G network node includes an access and mobility management function AMF.
[0152] Embodiment 17: The method of any of embodiments 14-16, wherein the context request includes current UE location information.
[0153] Embodiment 18: The method of embodiment 17, wherein the current UE location information comprises at least one of: a current tracking area identity TAI; and an evolved universal terrestrial radio access network E-UTRAN cell global identifier eCGI.
[0154] Embodiment 19: The method of any of embodiments 14-18, wherein the data forwarding information comprises at least one of: a buffered download data waiting indication associated with the UE; and a direct or indirect forwarding indication.
[0155] Embodiment 20: The method of Embodiment 19, wherein direct forwarding is indicated by the presence of a direct forwarding indicator, and wherein indirect forwarding is indicated by the absence of a direct forwarding indicator.
[0156] Embodiment 21: The method of any embodiment of Embodiments 14-20, wherein providing the GTP-U tunnel information for forwarding data from the 5G network to the EPS network includes providing a forwarding-complete tunnel endpoint identifier F-TEID.
[0157] Embodiment 22: The method of any embodiment of Embodiments 14-21, wherein providing the GTP-U tunnel information for forwarding data from the 5G network to the EPS network includes: sending an N2 forwarding information request message including the GTP-U tunnel information.
[0158] Group C Example - N5 NG-RAN
[0159] Embodiment 23: A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system EPS network, the method comprising: at a next generation NG radio access network RAN node: receiving a request for data forwarding information associated with a user equipment UE from a 5G network node; and sending a response including the data forwarding information associated with the UE to the 5G network node.
[0160] Embodiment 24: The method of Embodiment 23, wherein the request for data forwarding information associated with the UE includes current UE location information.
[0161] Embodiment 25: The method of embodiment 24, wherein the current UE location information comprises at least one of: a current tracking area identity TAI; and an evolved universal terrestrial radio access network E-UTRAN cell global identifier eCGI.
[0162] Embodiment 26: The method of any of embodiments 23-25, wherein the request comprises an N2 data forwarding information request message, and the response comprises an N2 data forwarding information response message.
[0163] Embodiment 27: The method of any embodiment of Embodiments 23-27, wherein the data forwarding information associated with the UE includes at least one of the following: a protocol data unit PDU session identifier ID having buffered data; a direct or indirect forwarding indication; and information identifying a forwarding container.
[0164] Group D Example - 5G SMF
[0165] Embodiment 28: A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system EPS network, the method comprising: at a first 5G network node: receiving a request for bearer context information associated with a UE from a second 5G network node, the request comprising data forwarding information associated with the UE; and sending a response to the second 5G network node, the response comprising the bearer context information associated with the UE, a buffered download data waiting indication associated with the UE, and a direct or indirect forwarding indication associated with the UE.
[0166] Embodiment 29: The method of embodiment 28, wherein the first 5G network node includes a session management function SMF.
[0167] Embodiment 30: The method of Embodiment 28 or 29, wherein the second 5G network node includes an access and mobility management function AMF.
[0168] Embodiment 31: The method of any of Embodiments 28-30, wherein the request comprises a Nsmf_PDUSessionContext request message, and the response comprises a Nsmf_PDUSessionContext response message.
[0169] Embodiment 32: The method of any of Embodiments 28-31, wherein direct forwarding is indicated by the presence of a direct forwarding indicator in the response, and wherein indirect forwarding is indicated by the absence of a direct forwarding indicator in the response.
[0170] Group E Examples - Equipment
[0171] Embodiment 33: A fifth generation 5G network node, which is used to perform mobility transfer from a 5G network to an evolved packet system EPS network, the 5G network node comprising: a processing circuit, which is configured to perform any steps of any of the steps of any embodiment of Group A, Group C or Group D; and a power supply circuit, which is configured to supply power to the 5G network node.
[0172] Embodiment 34: The 5G network node of Embodiment 33, the 5G network node includes an access and mobility management function AMF node.
[0173] Example 35: The 5G network node of Example 33, the 5G network node includes a session management function SMF node.
[0174] Example 36: The 5G network node of Example 33, the 5G network node includes a user plane function UPF node.
[0175] Embodiment 37: The 5G network node of Embodiment 33, the 5G network node comprising a next generation NG radio access network RAN node.
[0176] Embodiment 38: The NG-RAN node of Embodiment 37, the NG-RAN node includes a new radio interface NR node B gNB.
[0177] Embodiment 39: An evolved packet system EPS network node, which is used to perform mobility transfer from a fifth generation 5G network to an EPS network, the EPS network node comprising: a processing circuit, which is configured to perform any steps of any of the steps of any embodiment in Group B embodiments; and a power supply circuit, which is configured to supply power to the EPS network node.
[0178] Embodiment 40: The EPS network node of Embodiment 39, wherein the EPS network node includes a mobility management entity MME.
[0179] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, how it is used above shall take precedence. If listed multiple times below, the first listing shall take precedence over any subsequent listing(s).
[0180] 3GPP Third Generation Partnership Project
[0181] 5G fifth generation
[0182] 5GC Fifth Generation Core Network
[0183] 5GS Fifth Generation System
[0184] AF application function
[0185] AMF access and mobility management function
[0186] AN Access Network
[0187] AP Access Point
[0188] ASIC Application-Specific Integrated Circuit
[0189] AUSF authentication server function
[0190] CGI Cell Global Identifier
[0191] CM Configuration Management
[0192] CN Core Network
[0193] CPU Central Processing Unit
[0194] DL Downlink
[0195] DN Data Network
[0196] DRB Data Radio Bearer
[0197] DRX Discontinuous Reception
[0198] DSP Digital Signal Processor
[0199] eCGI Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Cell Global Identifier
[0200] eDRX Enhanced Discontinuous Reception
[0201] eNB Enhanced or evolved Node B
[0202] EPC Evolved Packet Core
[0203] EPS Evolved Packet System
[0204] E-UTRAN Evolved Universal Terrestrial Radio Access
[0205] E-UTRAN Evolved Universal Terrestrial Radio Access Network
[0206] FPGA Field Programmable Gate Array
[0207] F-TEID Full Tunnel Endpoint Identifier
[0208] gNB new air interface base station
[0209] GPRS General Packet Radio Service
[0210] GTP General Packet Radio Service Tunneling Protocol
[0211] · GTP-U General Packet Radio Service Tunneling Protocol, User Data
[0212] HSS Home Subscriber Server
[0213] ID Identifier / Identity
[0214] IP Internet Protocol
[0215] I-RNTI Inactive Mode Radio Network Temporary Identifier
[0216] LTE Long Term Evolution
[0217] MME Mobility Management Entity
[0218] MT Mobile Terminated
[0219] MTC Machine Type Communication
[0220] NAS Non-Access Stratum
[0221] NEF Network Open Function
[0222] NF Network Function
[0223] NG Next Generation (e.g. 5G)
[0224] NR New Radio
[0225] NRF Network Function Repository capabilities
[0226] NSSF network slice selection function
[0227] OTT Over the Top
[0228] PCF policy control function
[0229] PDU Protocol Data Unit
[0230] PGW Packet Gateway
[0231] PLMN Public Land Mobile Network
[0232] QoS Quality of Service
[0233] RAM Random Access Memory
[0234] RAN Radio Access Network
[0235] RAT Radio Access Technology
[0236] RNA Radio Access Network Notification Area
[0237] RNTI Radio Network Temporary Identifier
[0238] ROM Read Only Memory
[0239] RRC Radio Resource Control
[0240] RRH Remote Radio Head
[0241] RTT Round Trip Time
[0242] SCEF service capability exposure function
[0243] SGW Service Gateway
[0244] SMF session management functions
[0245] TAI Tracking Area Identity
[0246] TAU Tracking Area Updates
[0247] TEID Tunnel Endpoint Identifier
[0248] TS Technical Specification
[0249] UDM unified data management
[0250] UE User Equipment
[0251] UPF User Plane Function
[0252] UTRA Universal Terrestrial Radio Access
[0253] UTRAN Universal Terrestrial Radio Access Network
[0254] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.
Claims
1. A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system (EPS) network, performed by a fifth generation 5G network entity, wherein: The 5G network entity includes an access and mobility management function AMF implemented on a node, and the method is performed by the AMF, and the method includes: receiving (700) a context request including current UE location information associated with a user equipment UE from an EPS network entity; sending (5) a first request for data forwarding information to a 5G Node B gNB within a next generation radio area network NG-RAN indicating the current UE location information, and receiving (5) a first response including the data forwarding information associated with the UE from the 5G Node B gNB; determining (702) the data forwarding information associated with the UE; starting a timer and sending (704) a context response including bearer context information associated with the UE and the data forwarding information associated with the UE to the EPS network entity, and the EPS determines whether the UE requires data forwarding; After determining that the UE requires data forwarding, receiving (22) a context acknowledgement including General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnel information from the EPS network entity; sending (26) an N2 forwarding information request message including the GTP-U tunnel information to the NG-RAN and receiving (26) an N2 forwarding information response; and After the timer expires, initiating (27) an N2 UE context release procedure, wherein determining (702) data forwarding information associated with the UE further comprises: - sending (6a) a second request for bearer context information associated with the UE to a session management function, SMF, and / or a user plane function, UPF, the second request comprising 5G Node B gNB data forwarding information associated with the UE obtained from a 5G Node B gNB within a next generation radio area network, NG-RAN; and - Receive (6c) a second response from the SMF and / or the UPF, the second response including the bearer context information associated with the UE, the buffered download data waiting indication associated with the UE, and the direct or indirect forwarding indication associated with the UE, wherein the data forwarding information associated with the UE includes the buffered download data waiting indication and the direct or indirect forwarding indication.
2. The method of claim 1, wherein: The 5G network entity includes an access and mobility management function AMF implemented on the node.
3. The method according to any one of claims 1 to 2, wherein: The EPS network entity includes a mobility management entity MME implemented on the node.
4. The method of claim 1, wherein: The current UE location information includes at least one of the following: The current Tracking Area Identity TAI; and Evolved Universal Terrestrial Radio Access Network E-UTRAN Cell Global Identifier eCGI.
5. The method of claim 1, wherein: Determining the data forwarding information associated with the UE includes: An indication of the data forwarding information associated with the UE is received from a session management function, SMF.
6. The method of claim 1, wherein: The first request includes an N2 data forwarding information request message, and the first response includes an N2 data forwarding information response message.
7. The method of claim 1, wherein: The data forwarding information associated with the UE includes at least one of the following: The protocol data unit PDU session identifier ID with the buffered data; The direct or indirect forwarding instruction; and Identifies information about the forwarding container.
8. The method of claim 7, wherein: The second request includes a Nsmf_PDUSessionContext request message, and the second response includes a Nsmf_PDUSessionContext response message.
9. The method of claim 1, wherein: Direct forwarding is indicated by the presence of a direct forwarding indicator in the second response, and wherein indirect forwarding is indicated by the absence of a direct forwarding indicator in the second response.
10. The method of claim 1, wherein: Receiving the GTP-U tunnel information includes receiving a forward-complete tunnel endpoint identifier F-TEID.
11. A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system EPS network, wherein: The method is performed by an EPS network entity including a mobility management entity MME implemented on a node, the method is performed by the MME, and the method includes: sending (800) a context request including current UE location information associated with a user equipment UE to a 5G network entity; receiving (5) a first request for data forwarding information associated with a user equipment UE from a 5G network node including an access and mobility management function AMF implemented on the node indicating the current US location information, and sending (5) to the 5G network node including the data forwarding information associated with the UE; Starting a timer by the AMF and receiving (802) a context response including bearer context information associated with the UE and data forwarding information associated with the UE from the 5G network entity; The data forwarding information includes a buffered download data waiting indication associated with the UE and a direct or indirect forwarding indication, wherein the data forwarding information associated with the UE is determined by the AMF communicating with the MME, and wherein determining the data forwarding information further includes: - sending (6a) a second request for bearer context information associated with the UE to a session management function, SMF, and / or a user plane function, UPF, the second request comprising 5G Node B gNB data forwarding information associated with the UE obtained from a 5G Node B gNB within a next generation radio area network, NG-RAN; and - receiving (6c) a second response from the SMF and / or the UPF, the second response comprising the bearer context information associated with the UE, a buffered download data waiting indication associated with the UE, and a direct or indirect forwarding indication associated with the UE, wherein the data forwarding information associated with the UE comprises the buffered download data waiting indication and the direct or indirect forwarding indication; Upon determining that data forwarding is required for the UE, providing (804) general packet radio service GPRS tunneling protocol GTP user plane GTP-U tunnel information for forwarding data from the 5G network to the EPS network to the 5G network entity, wherein the AMF in communication with the MME is configured to perform the following steps: sending (26) an N2 forwarding information request message including the GTP-U tunnel information to the NG-RAN and receiving (26) an N2 forwarding information response; and After the timer expires, an N2 UE context release procedure is initiated (27).
12. The method of claim 11, wherein: The EPS network entity includes a mobility management entity MME implemented on a node.
13. The method according to claim 11 or 12, wherein: The 5G network entity includes an access and mobility management function AMF implemented on the node.
14. The method of claim 11, wherein: The current UE location information includes at least one of the following: The current Tracking Area Identity TAI; and Evolved Universal Terrestrial Radio Access Network E-UTRAN Cell Global Identifier eCGI.
15. The method of claim 11, wherein: Direct forwarding is indicated by the presence of a direct forwarding indicator, and wherein indirect forwarding is indicated by the absence of a direct forwarding indicator.
16. The method of claim 11, wherein: Providing the GTP-U tunnel information for forwarding data from the 5G network to the EPS network includes providing a forwarding-complete tunnel endpoint identifier F-TEID.
17. A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system EPS network, wherein: The method is performed by a next generation NG radio access network RAN node, and the method comprises: receiving (900) a first request for data forwarding information associated with a user equipment UE from a 5G network node including an access and mobility management function AMF implemented on the node indicating current US location information; and sending (902) a first response including the data forwarding information associated with the UE to the 5G network node, wherein the AMF in communication with the Next Generation NG Radio Access Network RAN node is configured to perform the following steps: Determine the data forwarding information associated with the UE, wherein the determining further comprises: - sending (6a) a second request for bearer context information associated with the UE to a session management function, SMF, and / or a user plane function, UPF, the second request comprising 5G Node B gNB data forwarding information associated with the UE obtained from a 5G Node B gNB within a next generation radio area network, NG-RAN; and - receiving (6c) a second response from the SMF and / or the UPF, the second response comprising the bearer context information associated with the UE, a buffered download data waiting indication associated with the UE, and a direct or indirect forwarding indication associated with the UE, wherein the data forwarding information associated with the UE comprises the buffered download data waiting indication and the direct or indirect forwarding indication; starting a timer and sending (704) a context response including bearer context information associated with the UE and the data forwarding information associated with the UE to the EPS network entity, and the EPS determines whether the UE requires data forwarding; After determining that the UE requires data forwarding, receiving (22) a context acknowledgement including General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnel information from the EPS network entity; receiving (26) an N2 forwarding information request message including said GTP-U tunnel information and sending (26) an N2 forwarding information response; and After the timer expires, an N2 UE context release procedure is initiated (27).
18. The method of claim 17, wherein: The request for the data forwarding information associated with the UE includes current UE location information.
19. The method of claim 18, wherein: The current UE location information includes at least one of the following: The current Tracking Area Identity TAI; and Evolved Universal Terrestrial Radio Access Network E-UTRAN Cell Global Identifier eCGI.
20. The method of claim 17, wherein: The request includes an N2 data forwarding information request message, and the response includes an N2 data forwarding information response message.
21. The method of claim 17, wherein: The data forwarding information associated with the UE includes at least one of the following: The protocol data unit PDU session identifier ID with the buffered data; forwarding instructions directly or indirectly; and Identifies information about the forwarding container.
22. A method for performing mobility transfer from a fifth generation 5G network to an evolved packet system EPS network, wherein: The method is performed by a first 5G network entity including a session management function SMF implemented on a node, and the method includes: Determine data forwarding information associated with the UE, including: receiving, from a second 5G network entity including an access and mobility management function AMF implemented on the node, a second request for bearer context information associated with the user equipment UE; and sending a second response including the bearer context information associated with the UE and a buffered download data waiting indication associated with the UE to the second 5G network entity, wherein the AMF communicating with the SMF is configured to perform the following steps: receiving (4) from the EPS network entity a context request including current UE location information associated with a user equipment UE; sending (5) a first request for data forwarding information associated with the UE to a 5G Node B gNB in a next generation wireless regional area network NG-RAN indicating the current UE location information, and receiving (5) a first response including the data forwarding information associated with the UE from the 5G Node B gNB; The AMF starts a timer and sends (7, 704) a context response including bearer context information associated with the UE and the data forwarding information associated with the UE to the EPS network entity, and the EPS determines whether the UE requires data forwarding; After determining that the UE requires data forwarding, receiving (22) a context acknowledgement including General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnel information from the EPS network entity; sending (26) an N2 forwarding information request message including the GTP-U tunnel information to the NG-RAN and receiving (26) an N2 forwarding information response; and After the timer expires, an N2 UE context release procedure is initiated (27).
23. The method of claim 22, wherein: The first 5G network entity includes a session management function SMF implemented on a node.
24. The method of claim 22, wherein: The second 5G network entity includes an access and mobility management function AMF implemented on the node.
25. The method of claim 22, wherein: The request includes a Nsmf_PDUSessionContext request message, and the response includes a Nsmf_PDUSessionContext response message.
26. The method of claim 22, wherein: Direct forwarding is indicated by the presence of a direct forwarding indicator in the response, and wherein indirect forwarding is indicated by the absence of a direct forwarding indicator in the response.
Citation Information
Patent Citations
Always-on bearer for small data transfers in LTE systems
CN104737619A
Interworking with bearer-based system
CN106465080A
Systems, apparatuses, and methods for lightweight over-the-air signaling mechanisms in data communications
CN106717105A
Method for UE context management and device for supporting same
CN108713337A
Reliable data delivery over non-access stratum
CN109804661A
