User plane establishment during 5G system to evolved packet system handover

By pre-allocating user plane resources on the target RAN during the 5G system to the Evolution Packet System (EPS) switch, AMF and MME/SGW solve the problem that user plane resources cannot be maintained, and service continuity and stability of IMS services are achieved. , improves the reliability of the system.

CN118890664APending Publication Date: 2024-11-01TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410993885.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2018-08-14
Filing Date
2019-08-13
Publication Date
2024-11-01

AI Technical Summary

Technical Problem

During the 5G system to the Evolution Packet System (EPS) handover, user plane resources cannot be maintained, resulting in service interruption and IMS service impact. Especially when the UE switches from 5GS to EPS, PDU sessions without user plane PDU sessions are deleted. Impact mobility and service continuity.

Method used

During the 5GS to EPS switching process, AMF and MME/SGW pre-allocate user plane resources on the target RAN and provide the required resource information during the switching, ensuring the maintenance of PDU sessions after HO, using N26 interface and Nsmf_PDU session context Request mechanism to realize resource management and switching of all PDU sessions.

Benefits of technology

It realizes the maintenance of user plane resources during 5GS to EPS handover, ensures service continuity and stability of IMS services, avoids the need for UE to re-establish PDU sessions after handover, and improves the reliability and user experience of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118890664A_ABST
    Figure CN118890664A_ABST
Patent Text Reader

Abstract

The system comprises a mobility management entity MME (103), a first radio access node RAN (102, eNB) providing long term evolution (LTE) access and a second radio access node RAN (108, gNB) providing new radio (NR) access; a User Entity, UE, (101) supports both Long Term Evolution, LTE, and New Radio, NR, Radio Access Technology, RAT.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the PCT international application PCT / CN2019 / 100377, filed on August 13, 2019, with the invention name “User plane establishment during switching from 5G system to evolved packet system”, which entered the Chinese national phase patent application 201980066888.X. Technical Field

[0002] The present invention proposes methods and devices related to Long Term Evolution LTE / Evolved Packet System EPS and New Radio NR radio access / 5G system core network technologies. Background Art

[0003] Figure 1 The well-known SAE-LTE (System Architecture Evolution - Long Term Evolution) architecture is shown in . In the 5G work of 3GPP, a split between mobility management (MM) and session management (SM) has been defined compared to the EPC (Evolved Packet Core), in which the MME (Mobility Management Entity) supports both MM (Mobility Management) and some SM (Session Management) functions. The Access and Mobility Function (AMF) supports the MM functions, and the Session Management Function (SMF) supports the SM functions. The AMF (Access and Mobility Management Function) selects the SMF. Different SMFs can be selected for different PDU (Packet Data Unit) sessions of the UE (User Entity), for example, PDU sessions to different Data Network Names (DNN) / Access Point Names APNs, or the same SMF can be used. Figure 2 The reference architecture is shown in , which corresponds to TS 23.501 V0.5.0 (2017-05), Figure 4 .2.3-3.

[0004] Figure 3 The so-called N26 interface is shown, which is the inter-CN (inter-core network) interface between the MME and the 5GS AMF to enable interworking between the EPC and the NG (next generation) core. Support of the N26 interface in the network is optional for interworking. N26 supports a subset of the functions supported on S10 (essential for interworking). Figure 3 Corresponds to Figure 4 .3.1-1: Non-roaming architecture for interworking between 5GS and EPC / E-UTRAN (Evolved Terrestrial Radio Access Network) for TS23.501 V15.2.0 (2018-06).

[0005] In 5GS, there is support for selective UP (user plane) activation and deactivation as specified in TS 23.501 section 5.6.8, which reads as follows:

[0006] 5.6.8 Selective activation and deactivation of UP connections for existing PDU sessions

[0007] This clause applies to situations where the UE has established multiple PDU (Protocol Data Unit) sessions. Activation of a UP connection for an existing PDU session results in activation of its UE-CN user plane connection (i.e. data radio bearers and N3 tunnel).

[0008] For UEs in CM-IDLE (Connection Management - Idle) state in 3GPP access, the service request procedure triggered by the UE or the network can support independent activation of the UP connection for an existing PDU session. For UEs in CM-IDLE state in non-3GPP access, the service request procedure triggered by the UE allows reactivation of the UP connection for an existing PDU session and can support independent activation of the UP connection for an existing PDU session.

[0009] A UE in the CM-CONNECTED state invokes the Service Request (see TS 23.502 [3] clause 4.2.3.2) procedure to request independent activation of a UP connection for an existing PDU Session.

[0010] Network triggered reactivation of a UP connection for an existing PDU Session is handled as follows:

[0011] - If the UE CM state in the AMF is already CM-CONNECTED on the access (3GPP, non-3GPP) associated with the PDU session in the SMF, the network can reactivate the UP connection for the PDU session using the network initiated service request procedure.

[0012] otherwise:

[0013] - If the UE is registered in both 3GPP and non-3GPP access, and the UE CM state in the AMF in the non-3GPP access is CM-IDLE, the UE may be paged or notified over the 3GPP access for the PDU sessions associated with the non-3GPP access in the SMF (i.e. last routed):

[0014] -If the UE CM state in the AMF is CM-IDLE in 3GPP access, the paging message may include the access type associated with the PDU session in the SMF. Upon receiving the paging message containing the access type, the UE shall reply to the 5GC via the 3GPP access using a NAS Service Request message, which shall contain a list of PDU sessions associated with the received access type and whose UP connections can be reactivated on 3GPP (i.e., the list does not contain the following PDU sessions: their UP connections cannot be reactivated on 3GPP based on UE policy and whether the S-NSSAI of these PDU sessions is within the allowed NSSAI range for 3GPP access). If the PDU session for which the UE has been paged is in the list of PDU sessions provided in the NAS Service Request, the 5GC shall reactivate the UP connection of the PDU session via the 3GPP access;

[0015] - If the UE CM state in the AMF is CM-CONNECTED in 3GPP access, the Notification message shall include the non-3GPP access type. Upon receiving the Notification message, the UE shall reply to the 5GC via 3GPP access using a NAS Service Request message which shall contain a list of allowed PDU Sessions that can be reactivated on 3GPP or an empty list of allowed PDU Sessions (if no PDU Session is allowed to be reactivated via 3GPP access).

[0016] NOTE: It is assumed that a UE that is in range of a non-3GPP access and has a PDU session associated with the non-3GPP access in the UE (ie last routed) attempts to connect to it without being paged.

[0017] - If the UE is registered in both 3GPP and non-3GPP access served by the same AMF, and the UE CM state in the AMF is CM-IDLE in the 3GPP access and CM-CONNECTED in the non-3GPP access, the UE may be notified via non-3GPP for the PDU sessions associated with the 3GPP access in the SMF (i.e. the last routed). The notification message shall include the 3GPP access type. Upon receipt of the notification message, the UE shall reply to the 5GC via the 3GPP access using a NAS Service Request message when the 3GPP access is available.

[0018] End of 5.6.8.

[0019] Deactivation of the UP connection for an existing PDU session results in the corresponding data radio bearer and N3 tunnel being deactivated.When the UE is in CM-CONNECTED state in 3GPP access or non-3GPP access, the UP connections for different PDU sessions can be deactivated independently.

[0020] Since there is no equivalent support in EPS, this requires that a UP should be established for all PDU Sessions in the CM-CONENCTED state. If a PDU Session does not have a UP, the PDU Session shall be completely removed. Summary of the invention

[0021] Due to different requirements / processing in 5GS and EPS as described above, a UE in CM-CONNECTED mode in 5GS has, for example, PDU Sessions 1, 2, and 3, but only PDU Session 1 has UP, and after HO (handover) from 5GS to EPS, it will only have PDU Session 1 left. The other 2 PDU Sessions will be deleted after the move. The UE needs to re-establish the required PDU Sessions from scratch.

[0022] This means that some services, such as IMS (IP Multimedia Subsystem) services, will be significantly affected. Typically, the UE will have to establish an IMS APN (Access Point Name) in the EPS and then re-register with the IMS, resulting in additional signaling in the network. Furthermore, the UE will not be available for any IMS services during the time until the UE successfully re-registers with the IMS.

[0023] The first objective is to propose a method and apparatus for providing a switching process from 5GS to EPS.

[0024] Another object is to provide means for user plane resource establishment during the inter-system handover procedure from 5GS to EPS, and PDU sessions without UP when HO is triggered can be maintained after HO, wherein the selective user plane UP in 5GS will not be affected by EPS.

[0025] The above objectives have been achieved through:

[0026] A method for a Long Term Evolution Radio Access Node (LTE RAN E-UTRAN (eNB) adapted to

[0027] - participate in a handover from a Next Generation RAN (denoted as Source RAN) to said LTE RAN (denoted as Target RAN),

[0028] - receiving a handover request message from a mobility management entity MME,

[0029] - Allocate resources or bearers requested by the mobility management entity MME, even if said resources or said bearers are not included in the transparent container from the source RAN.

[0030] It has also been achieved by a method for a system comprising

[0031] Long Term Evolution Radio Access Node LTE RAN E-UTRAN (eNB),

[0032] Next Generation Radio Access Node NG RAN,

[0033] Access and mobility management function AMF,

[0034] Mobility Management Entity MME,

[0035] Serving Gateway SGW,

[0036] Visitor Session Management Function V-SMF,

[0037] The system is suitable for

[0038] -NG RAN (denoted as source RAN) decides that the UE should be handed over to LTE RAN (denoted as target RAN) and sends a handover required message to AMF,

[0039] - The AMF determines from the "Target eNB Identifier" IE that the handover type is a handover to E-UTRAN. The AMF selects an MME and sends an Nsmf_PDU Session Context Request to the V-SMF for each PDU session associated with the 3GPP access to provide an SM context, which also includes the mapped EPS bearer context.

[0040] -AMF receives Nsmf_PDU Session Context Request Response,

[0041] -AMF sends a relocation request to MME,

[0042] -MME and SGW participate in creating session request and response messages,

[0043] -MME sends a handover request to LTE RAN,

[0044] - The LTE RAN allocates resources or bearers requested by the MME even if the resources or the bearers are not included in the transparent container from the source RAN.

[0045] Other objectives have been achieved through:

[0046] A method for an AMF adapted to perform an Nmsf PDU Session Context Request to an SMF even for PDU sessions for which there is currently no user plane, i.e. also for PDU sessions not included in a Handover Required message from the NG-RAN.

[0047] A method for an AMF adapted to not apply indirect data forwarding to a PDU session that previously did not have a user plane in NG-RAN.

[0048] A method for a Next Generation RAN, NGRAN (gNB), the NGRAN being adapted to accept a handover command from an AMF even when a transparent container from a target RAN such as an eNB includes more user planes for bearers than required by the NG-RAN, the NG-RAN being further adapted to pass the handover command to a UE.

[0049] A method for a UE adapted to accept a handover command when moving to a target RAN such as an eNB and allocate user plane resources as requested in the handover HO command.

[0050] A method for a UE adapted to associate a QoS flow currently without user plane resources with an EPS bearer ID to be established in a HO command.

[0051] The above objects have also been achieved by corresponding devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 Shows the known reference architecture for LTE access and core network systems for non-roaming scenarios, reflecting 3GPP TS 23.401 V15.1.0 (2017-09) Figure 4 .2.1-1: Non-roaming architecture for 3GPP access,

[0053] Figure 2 shows a known reference architecture for 5G access and core network systems for non-roaming scenarios, corresponding to TS 23.501 V15.2.0 (2018-06), Figure 4 .2.3-3: Application of non-roaming 5G system architecture to multiple PDU sessions as reference points,

[0054] Figure 3 shows the known reference architecture for LTE and 5G access and 5G core network systems, corresponding to TS23.501 V15.2.0 (2018-06), Figure 4 .3.1-1: Non-roaming architecture for interworking between 5GS and EPC / E-UTRAN,

[0055] Figure 4 A first embodiment of the present invention is shown.

[0056] Figure 5 yes Figure 4 Continue,

[0057] Figure 6An embodiment of the present invention is shown.

[0058] Figure 7 An additional flow chart showing an embodiment of the present invention corresponds to Figure 4 , ETSI GS NFV 002 V.1.1.1(2013-10),

[0059] Figure 8 and Fig. 9 Other embodiments of the present invention are shown.

[0060] Fig.10 and Fig.11 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment. DETAILED DESCRIPTION

[0061] Solution proposal: During the inter-system handover from 5GS to EPS,

[0062] 1) In addition to the PDU sessions indicated by the RAN (Radio Access Node) for the PDU sessions with UP in the HO required, the source AMF / SMF shall also allocate the CN (Core Network) related tunnel information for the PDU sessions without UP and provide them to the target MME / SGW side through the forward relocation request

[0063] 2) The target MME / SGW establishes UP resources for all received PDU sessions in the core network and indicates this information to the target RAN via a HO request

[0064] 3) The target RAN (e.g., eNB) establishes UP resources for all PDU sessions indicated from the target MME, even those that are not required by the source RAN (e.g., gNB (next generation NodeB)) but are required by the MME. The information is then provided to the MME, and the MME passes the information to the source AMF / SMF in the HO Request Acknowledgement as normal.

[0065] 4) The source AMF / SMF provides the UP resource information from the target RAN to the source RAN in the HO command. Even if the target RAN has allocated more UP resources than it requested, the source RAN still accepts the HO and sends the HO command to the UE, which includes the information provided from the target RAN side.

[0066] 5) The UE will accept the HO command and follow the instructions from the target RAN side to establish UP for all PDU sessions after moving to the 4G side.

[0067] A means is provided for establishing user plane resources during the inter-system handover procedure from 5GS to EPS, and PDU sessions without UP when HO is triggered can be maintained after HO.

[0068] The selective UP in 5GS will not be affected by EPS and will work as expected.

[0069] refer to Figure 4 and Figure 5 , according to an embodiment of the present invention, 3GPP TS 23.502 V15.2.0 (2018-06) is arranged as follows, with modifications underlined:

[0070] 4.11.1.2 Switching process

[0071] 4.11.1.2.1 Switching from 5GS to EPS using N26 interface

[0072] Figure 4 .11.1.2.1-1 describes the handover process from 5GS to EPS when supporting N26.

[0073] In case of handover to a shared EPS network, the source NG-RAN determines the PLMN to be used in the target network as specified in TS 23.501 [2]. The source NG-RAN shall indicate to the AMF the selected PLMN ID to be used in the target network as part of the TAI sent in the HO Required message.

[0074] In case of handover from a shared NG-RAN, the AMF may provide an indication to the MME that the 5GS PLMN is the preferred PLMN when later changing the UE to a 5GS shared network.

[0075] During the handover procedure, as specified in clause 4.9.1.3.1, the source AMF shall reject any PGW-C+SMF initiated N2 request received since the start of the handover procedure and shall include an indication that the request has been temporarily rejected because the handover procedure is in progress.

[0076] Upon receiving a rejection of the N2 request initiated by the PGW-C+SMF, with an indication that the request has been temporarily rejected because a handover procedure is ongoing, the PGW-C+SMF acts as specified in TS 23.401

[13] .

[0077] Figure 4 .11.1.2.1-1: 5GS to EPS handover for single registration mode using N26 interface

[0078] The procedure involves switching to the EPC and establishing the default EPS bearer and dedicated bearers for GBR (guaranteed bit rate) QoS flows in the EPC in steps 1-16, and reactivating (if needed) the dedicated EPS bearers for non-GBR QoS flows in step 17. The procedure may be triggered, for example, due to new radio conditions, load balancing or in the presence of QoS flows for normal voice or IMS emergency voice, and the source NG-RAN node may trigger a handover to the EPC.

[0079] For Ethernet and Unstructured PDU Session Types, PDN Type Non-IP is used in EPS (when supported). Therefore, in these cases, the SMF shall set the PDN type of the EPS bearer context to Non-IP. After handover to EPS, the PDN connection will have PDN type Non-IP but shall be locally associated to PDU Session Type Ethernet or Unstructured in the UE and SMF respectively.

[0080] In case of roaming home routing, PGW (Packet Data Network Gateway)-C+SMF always provides EPS bearer ID and mapped QoS parameters to UE. V-SMF (Visitor SMF) caches EPS bearer ID and mapped QoS parameters obtained from H-SMF for this PDU session. This also applies to the case where HPLMN (Home Public Land Mobile Network) operates the interworking process without N26.

[0081] Note 1: If the PGW-C+SMF in the HPLMN does not provide mapped QoS parameters, IP address reservation cannot be supported.

[0082] 1.NG (Next Generation)-RAN decides that the UE should be handed over to E-UTRAN. If NG-RAN is configured to perform inter-RAT (Radio Access Technology) mobility due to IMS voice fallback triggered by QoS (Quality of Service) flow establishment, and receives a request to establish a QoS flow for IMS voice, the NG-RAN responds via N2 SM information, indicating that the QoS flow establishment is rejected due to mobility due to fallback for IMS voice, and triggers handover to E-UTRAN. NG-RAN sends a Handover Required (Target eNB (eNodeB) ID, Source to Target Transparent Container, Inter-System Handover Indication, Indirect Forwarding Flag) message to AMF. NG-RAN indicates the bearer corresponding to the 5G QoS flow for data forwarding in the source to target transparent container.

[0083] If the handover is triggered due to emergency fallback, the NG-RAN may forward the emergency indication to the target eNB in ​​a source-to-target transparent container, and the target eNB allocates radio bearer resources taking into account the received indication.

[0084] The indirect forwarding flag indicates the applicability of indirect data forwarding.

[0085] 2. In case of HR roaming, the AMF determines the handover type is to E-UTRAN based on the "Target eNB Identifier" IE. The AMF selects the MMF as described in TS 23.401

[13] section 4.3.8.3.

[0086] The AMF requests the V-SMF for each PDU Session associated with the 3GPP access by using an Nsmf_PDU Session_Context request to provide an SM context which also includes the mapped EPS bearer context. The AMF provides the target MME capabilities to the SMF in the request to allow the V-SMF to determine whether to include the EPS bearer context for non-IP PDN types. For PDU Sessions with PDU Session Type Ethernet or Unstructured, the SMF provides the SM context for non-IP PDN types.

[0087] In case of non-roaming or LBO (Local Breakout) roaming, the AMF requests the PGW-C+SMF to provide the SM context by using Nsmf_PDU Session_Context Request. The PGW-C+SMF sends an N4 Session Modification to the PGW-U+UPF to establish a CN tunnel for each EPS bearer and provide the EPS bearer context to the AMF as depicted in step 8 of clause 4.11.1.4.1.

[0088] This step is performed using all PGW-C+SMFs assigned to the UE for each PDU Session of the UE.

[0089] The AMF also performs this step for the following PDU sessions: The SMF holding a PDU Session without a user plane shall allocate a CN user plane for the PDU Session. resources (e.g. CN tunnel information) and provides the SM context in the same way as if the CN user plane was already in place.

[0090] Note 2: The AMF knows whether the MME supports non-IP PDN type capabilities through local configuration.

[0091] Note 3: In home routed roaming scenario, the UE's SMEPS context is obtained from the V-SMF.

[0092] 3. The AMF sends a Forward Relocation Request according to step 2 of clause 5.5.1.2.2 (S1-based handover, normal) of TS 23.401

[13] , with the following modifications and clarifications:

[0093] - The parameter "Preferred Fallback" may be included. Preferred Fallback is an optional indication to the MME that the UE prefers to fall back to the 5GS PLMN when access is later changed to the 5GS shared network. The MME may use this information as specified in TS 23.501 [2].

[0094] - The SGW address and TEID() for both the control plane or EPS bearer in the message enables the target MME to select a new SGW. The AMF includes the indirect forwarding flag received from the source NG-RAN to inform the target MME of the applicability of indirect data forwarding.

[0095] -AMF also includes PDN connection information for SMF to maintain PDU sessions without UP

[0096] NOTE 4: Mapped SMEPSUE contexts are included for PDU Sessions with and without active UP connections.

[0097] 4-5. Step 4 and step 4a in clause 5.5.1.2.2 (S1-based handover, normal) of TS 23.401

[13] respectively.

[0098] 6. Step 5 (Handover Request) in clause 5.5.1.2.2 (S1-based Handover, Normal) of TS 23.401

[13] , with the following modifications:

[0099] - The Handover Request may contain a Handover Restriction List with information about the PLMN ID as specified in clause 5.2a of TS.251

[35] for eNodeB functionality.

[0100] - The eNodeB allocates resources even for the bearer requested by the MME, even if the bearer is not a source-to-target transparent bearer. The eNodeB does not allocate forwarding traffic for bearers that are not part of a source-to-target transparent container. Tunnel. The eNodeB includes the bearers requested by the source RAN and requested by the core network in a target-to-source transparent container.

[0101] 7-9. Steps 5a to 7 in clause 5.5.1.2.2 (S1-based handover, normal) of TS 23.401

[13] .

[0102] 10a. If indirect data forwarding is applicable, the AMF sends a Nsmf_PDU Session_Update SM Context Request (Serving GW address for data forwarding and Serving GW DL TEID (Tunnel Endpoint Identifier)) to the PGW-C+SMF to create an indirect data forwarding tunnel. If multiple PGW-C+SMFs serve the UE, the AMF maps the EPS bearer for data forwarding to the PGW-C+SMF address based on the association between the EPS bearer ID and the PDU Session ID. In case of home route roaming, the AMF requests the V-SMF to create an indirect forwarding tunnel.

[0103] The AMF may not apply indirect data forwarding to PDU sessions that previously did not have a user plane in NG-RAN.

[0104] 10b.PGW-C+SMF may select the intermediate PGW-U+UPF for data forwarding. PGW-C+SMF maps the EPS bearer for data forwarding to the 5G QoS flow based on the association between the EPS bearer ID and QFI of the QoS flow in PGW-C+SMF, and then sends the QFI, service GW address and TEID for data forwarding to PGW-U+UPF. If the CN tunnel information for data forwarding is allocated by PGW-C+SMF, the CN tunnel information for data forwarding is provided to PGW-U+UPF in this step. PGW-U+UPF confirms by sending a response. If the CN tunnel information is allocated by PGW-U+UPF, the CN tunnel information is provided to PGW-C+SMF in the response. In the case of home routing roaming, V-SMF selects V-UPF for data forwarding.

[0105] 10c.PGW-C+SMF returns Nsmf_PDU Session_Update SM Context Response (cause, CN tunnel information for data forwarding, QoS flow for data forwarding) to create indirect data forwarding. Based on the correlation between the QFI for data forwarding and the service GW address and TEID, PGW-U+UPF maps the QoS flow to the data forwarding tunnel in EPC.

[0106] 11.AMF sends a handover command to the source NG-RAN (transparent container (radio parameters that the target eNB has set in the preparation phase), CN tunnel information for data forwarding for each PDU session, QoS flow for data forwarding). NG-RAN The target RAN will be accepted to establish additional user plane resources in the transparent container. The source NG-RAN commands the UE to handover to the target access network by sending a HO command. The UE associates the ongoing QoS flows with the indicated EPS bearer ID to be established in the HO command. The UE shall also associate the QoS flows that currently have no user plane resources with the EPS bearer IDs to be established in the HO command. If the QoS flows associated with the default QoS rule in the PDU session are not assigned an EPS bearer ID, the UE locally deletes the PDU session. If the QoS flows associated with the default QoS rule are assigned an EPS bearer ID, the UE maintains the PDU session (PDN connection) and for the remaining QoS flows that are not assigned an EPS bearer ID, the UE locally deletes the QoS rules and QoS flow level QoS parameters (if associated with those QoS flows). The UE deletes any UE derived QoS rules. The EPS bearer ID assigned for the QoS flow of the default QoS rule in the PDU session becomes the EPS bearer ID of the default bearer in the corresponding PDN connection.

[0107] For the QoS flow indicated in "QoS flow for data forwarding", NG-RAN initiates data forwarding to PGW-U+UPF based on the CN tunnel information for data forwarding of each PDU session. Then, PGW-U+UPF maps the data received from the data forwarding tunnel in 5GS to the data forwarding tunnel in EPS and sends the data to the target eNodeB via the serving GW.

[0108] 12-12c. Steps 13 to 14 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401

[13] .

[0109] 12d.AMF confirms to MME using Relocation Complete Ack message. A timer in AMF starts supervision when resources in NG-RAN and PGW-C+SMF should be released.

[0110] 13. Step 15 from clause 5.5.1.2.2 (S1-based handover, normal) of TS 23.401

[13] .

[0111] 14. Step 16 (Modify Bearer Request) in clause 5.5.1.2.2 (S1-based Handover, Normal) of TS 23.401

[13] , where the following is stated:

[0112] - If the QoS flows associated with the default QoS rule in the PDU session are not assigned an EPS bearer ID, the PGW-C+SMF deletes the PDU session. If the QoS flows associated with the default QoS rule are assigned an EPS bearer ID, the PGW-C+SMF maintains the PDU session (PDN connection) and for the remaining QoS flows that are not assigned an EPS bearer ID, the PGW-C+SMF maintains the PCC (Policy and Charging Control) rules associated with those QoS flows.

[0113] NOTE 5: The PGW-C+SMF initiating dedicated bearer activation for those PCC rules maintained is described in step 18.

[0114] NOTE 6: If a QoS flow is deleted and the default QoS rule contains a packet filter set that allows all UL packets or does not contain a packet filter set, the IP flows of the deleted QoS rule are mapped to the default EPS bearer. If the default QoS rule contains a packet filter, the IP flows in the deleted QoS flow may be interrupted until step 18 of clause 5.5.1.2.2 of TS 23.401

[13] .

[0115] 15.PGW-C+SMF initiates the N4 session modification process to UPF+PGW-U to update the user plane path.PGW-C+SMF releases the CN tunnel resources for the PDU session in UPF+PGW-U.

[0116] 16. Step 16a (Modify Bearer Response) from clause 5.5.1.2.2 (S1 based Handover, Normal) of TS 23.401

[13] . At this stage, the user plane path is established between the UE, the target eNodeB, the Serving GW and the PGW-U+UPF for the default bearer and the dedicated GBR bearer. The PGW-C+SMF uses the EPSQoS parameters as assigned for the dedicated EPS_GBR bearer during QoS flow establishment. The PGW-C+SMF maps all other IP flows to the default EPS bearer.

[0117] 17. Step 17 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401

[13] .

[0118] 18. The UE initiates the Tracking Area Update procedure as specified in clause 5.3.3.1 of TS 23.401

[13] , with modifications as specified in clause 4.11.1.5.3.

[0119] When the old AMF decides not to maintain the UE registration for non-3GPP access any more, the old AMF then unsubscribes from subscription data updates by sending a Nudm_SDM_Unsubscribe service operation to the UDM and releases all AMF and AN resources related to this UE.

[0120] Note 7: The behavior of HSS (Home Subscriber Server) + UDM (Unified Data Management) to cancel the location of another type of CN node (i.e. AMF) is similar to the HSS behavior for MME and Gn / GpSGSN registration (see TS 23.401

[13] ). The target AMF for HSS + UDM to cancel the location is the AMF associated with the 3GPP access.

[0121] 19.PGW-C+SMF initiates the dedicated bearer activation procedure for non-GBR QoS flows by mapping the parameters of the non-GBR flows to the EPC QoS parameters. If PCC is deployed, this setup can be triggered by PCRF+PCF. This procedure is specified in TS 23.401

[13] clause 5.4.1. For Ethernet PDU session types using non-IP PDN types in EPS, this step is not applicable.

[0122] 20. Step 21 from clause 5.5.1.2.2 (S1-based handover, normal) of TS 23.401

[13] .

[0123] 21. If indirect forwarding is used, then expiry of the timer at the AMF started at step 12c triggers the AMF to invoke the Nsmf_PDU Session_Update SM Context Request service operation with an indication to release the forwarding tunnel of the V-SMF in order to release the temporary resources allocated for indirect forwarding at step 10. The V-SMF returns a Nsmf_PDU Session_Update SM Context Response message.

[0124] exist Figure 6 In the figure, a user equipment UE device according to an embodiment of the present invention is shown.

[0125] The UE comprises a processor PCU_UE, an interface IF_UE and a memory MEM_UE in which memory instructions for executing the above method steps are stored. The UE communicates via the interface IF_UE. The IF_UE comprises both an internal interface (not shown) and an external interface for communicating with a transmitter and a receiver.

[0126] Also shown is an AMF, which comprises a processor PCU_A, an interface IF_A and a memory MEM_A. Instructions are stored in the memory for execution by the processor, so that the above method steps are performed and signaling is transmitted on the interface.

[0127] Furthermore, an eNodeB (eNB) is provided, comprising a processor PCU_M, an interface IF_M and a memory MEM_M. Instructions are stored in the memory for execution by the processor, so that the above method steps are performed and signaling is transmitted on the interface.

[0128] exist Figure 6 In the figure, a NG RAN / gNB is also shown, which includes a processor PCU_G, an interface IF_G and a memory MEM_G. Instructions are stored in the memory for execution by the processor, so that the above method steps are performed and signaling is transmitted on the interface.

[0129] An SMF is provided, which comprises a processor PCU_S, an interface IF_S and a memory MEM_S. Instructions are stored in the memory for execution by the processor, so that the above method steps are performed and corresponding signaling is implemented on the interface.

[0130] Finally, a UPF is provided, which comprises a processor PCU_U, an interface IF_U and a memory MEM_U. Instructions are stored in the memory for execution by the processor, so that the above method steps are performed and corresponding signaling is implemented on the interface.

[0131] The above-mentioned devices / entities are adapted to communicate through known external telecommunication interfaces or via an application program interface API where appropriate.

[0132] Note that the features of the methods described above and hereinafter may be implemented in software and may be executed on a data processing device or other processing means resulting from the execution of program code means (such as computer executable instructions). Here and hereinafter, the term processing means includes any circuit and / or device suitably adapted to perform the above functions.

[0133] In particular, the above terms include general or special purpose programmable microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), programmable logic arrays (PLAs), field programmable gate arrays (FPGAs), dedicated electronic circuits, etc., or combinations thereof.

[0134] For example, the program code means may be loaded into a memory such as a RAM (random access memory) from a storage medium such as a read-only memory (ROM) or other non-volatile memory such as a flash memory, or from another device via a suitable data interface, and the described features may be implemented by hard-wired circuitry instead of software or in combination with software.

[0135] A computer program or a computer program product is provided which performs the method steps defined above.

[0136] The methods discussed above may alternatively be implemented with the aid of a system based on network function virtualization. Figure 7 In the present invention, other embodiments are implemented by means of such a network function virtualization system NFVS, which is formed on, for example, a general server, a standard storage device, and a switch. NFVS can be implemented along Figure 4 The line arrangement described in ETSI GS NFV 002 V.1.1.1 (2013-10) and includes the following elements: NFV management and coordination system, including the orchestrator ORCH, the VNF manager VNF_MGR and the virtualization infrastructure manager VIRT_INFRA_MGR. NFVS also includes: an operation / business support system OP / BUSS_SUPP_SYST; a plurality of virtual network function instances VNF (the above method steps are instantiated by a plurality of VNFs); and a virtualization infrastructure VIRT_INFRA. VIRT_INFRA includes virtual computing VIRT_COMP, virtual network VIRT_NETW, virtual memory VIRT_MEM, virtualization layer VIRT_LAYER (e.g., hypervisor) and shared hardware resources SHARED_HARDW_RES, which includes computing devices COMP, network devices NETW (including, for example, standard switches and other network devices) and standard data storage devices MEM.

[0137] According to an embodiment of the present invention, the above method can be Figure 8 or Fig. 9 Implementation in implementation:

[0138] Furthermore, one or more programs for a computer or a computer program product are provided, comprising instructions for performing any of the methods according to the above method steps.

[0139] According to an embodiment of the present invention, a method for Figure 8 + Fig. 9 Alternatively, the system and device can be instantiated as a virtual node in a cloud computing environment, referring to Figure 7 , the cloud environment includes shared hardware resources, which include at least computing devices (COMP), memory devices (MEM) and network devices (NETW).

[0140] Reference Figure 8 According to an embodiment, a communication system includes a telecommunication network 3210 (e.g., a cellular network of the 3GPP type), the telecommunication network 3210 including an access network 3211 (e.g., a radio access network) and a core network 3214. The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c (e.g., NB, eNB, gNB or other types of wireless access points), each base station defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 via a wired or wireless connection 3215. A first user equipment (UE) 3291 located in the coverage area 3213c is configured to be wirelessly connected to the corresponding base station 3212c or to be paged by the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or a only UE is connected to the corresponding base station 3212.

[0141] The telecommunications network 3210 itself is connected to a host computer 3230, which may be implemented in hardware and / or software as a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 3221, 3222 between the telecommunications network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or may be made via an optional intermediate network 3220. The intermediate network 3220 may be a combination of one or more of a public, private, or managed network; the intermediate network 3220 (if present) may be a backbone network or the Internet; specifically, the intermediate network 3220 may include two or more subnetworks (not shown).

[0142] Figure 8 The communication system as a whole implements a connection between one of the connected UEs 3291, 3292 and the host computer 3230. The connection can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to use the access network 3211, the core network 3214, any intermediate networks 3220 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 3250. The OTT connection 3250 can be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are not aware of the routing of uplink and downlink communications. For example, the base station 3212 may not be informed or need not be informed of the past routing of the incoming downlink communication with data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of outgoing uplink communications originating from the UE 3291 to the host computer 3230.

[0143] Now refer to Fig. 9To describe an example implementation of the UE, base station, and host computer discussed in the previous paragraph according to the embodiment. In the communication system 3300, the host computer 3310 includes hardware 3315, and the hardware 3315 includes a communication interface 3316, and the communication interface 3316 is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 3300. The host computer 3310 also includes a processing circuit 3318, which may have storage and / or processing capabilities. Specifically, the processing circuit 3318 may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The host computer 3310 also includes software 3311, which is stored in the host computer 3310 or can be accessed by the host computer 3310 and can be executed by the processing circuit 3318. The software 3311 includes a host application 3312. The host application 3312 is operable to provide services to a remote user (e.g., UE 3330), which is connected via an OTT connection 3350 terminated at the UE 3330 and the host computer 3310. In providing services to the remote user, the host application 3312 may provide user data sent using the OTT connection 3350.

[0144] The communication system 3300 also includes a base station 3320 provided in the telecommunication system, the base station 3320 including hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include: a communication interface 3326 for establishing and maintaining a wired or wireless connection with an interface of different communication devices of the communication system 3300; and a radio interface 3327 for establishing and maintaining at least a connection with a network located in a coverage area ( Fig. 9 The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct, or it may pass through a core network (eg, a wireless network) of the telecommunications system. Fig. 9 3320) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 3320 also has software 3321 stored internally or accessible via an external connection.

[0145] The communication system 3300 also includes the UE 3330 already mentioned. Its hardware 3335 may include a radio interface 3337, which is configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area where the UE 3330 is currently located. The hardware 3335 of the UE 3330 also includes a processing circuit 3338, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The UE 3330 also includes software 3331, which is stored in the UE 3330 or can be accessed by the UE 3330 and can be executed by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332 is operable to provide services to human or non-human users via the UE 3330 with the support of the host computer 3310. In the host computer 3310, the executing host application 3312 can communicate with the executing client application 3332 via the OTT connection 3350 terminated at the UE 3330 and the host computer 3310. When providing services to users, the client application 3332 can receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 can transmit both the request data and the user data. The client application 3332 can interact with the user to generate the user data it provides.

[0146] Notice, Fig. 9 The host computer 3310, base station 3320 and UE 3330 shown can be respectively Figure 8 The host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 are the same. That is, the internal workings of these entities can be as follows Fig. 9 As shown, and independently, the surrounding network topology can be Figure 8 network topology.

[0147] exist Fig. 9 , an OTT connection 3350 has been abstractly drawn to illustrate communications between a host computer 3310 and a user device 3330 via a base station 3320, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 3330 or from the service provider operating the host computer 3310, or from both. The network infrastructure may also make decisions that dynamically change the routing while the OTT connection 3350 is active (e.g., due to load balancing considerations or reconfiguration of the network).

[0148] The wireless connection 3370 between the UE 3330 and the base station 3320 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 3330 using the OTT connection 3350, wherein the wireless connection 3370 forms the last leg in the OTT connection 3350. More precisely, the teachings of these embodiments can improve services for such dual-connected UEs.

[0149] 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 also be an optional network function for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 3350 may be implemented in software 3311 of the host computer 3310 or in software 3331 of the UE 3330 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 3350 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity exemplified above or providing the value of other physical quantities that the software 3311, 3331 can use to calculate or estimate the monitoring quantity. Reconfiguration of the OTT connection 3350 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration does not need to affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such processes and functions may be known and practiced in the art. In a particular embodiment, the measurements may involve proprietary UE signaling that facilitates the host computer 3310 to measure throughput, propagation time, latency, etc. The measurements may be implemented as follows: the software 3311, 3331 enables the use of the OTT connection 3350 to send messages (specifically, empty messages or "fake" messages) while it monitors propagation time, errors, etc.

[0150] Fig.10 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE. For the sake of simplicity of the present disclosure, only the Fig.10In a first step 3410 of the method, a host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission to the UE carrying the user data. In an optional third step 3430, in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0151] Fig.11 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE. For the sake of simplicity of the present disclosure, only the Fig.11 In a first step 3510 of the method, a 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 a second step 3520, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be via a base station. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0152] In other words, it provides:

[0153] A method for a Long Term Evolution Radio Access Node (LTE RAN E-UTRAN) (eNB), wherein the LTE RAN E-UTRAN is adapted to

[0154] - participate in a handover from a Next Generation RAN (denoted as Source RAN) to said LTE RAN (denoted as Target RAN),

[0155] - receiving a handover request message 6 from the mobility management entity MME,

[0156] - Allocate 6 resources or bearers requested by the mobility management entity MME, even if said resources or said bearers are not included in the transparent container from the source RAN.

[0157] A method and a system for use in a system are also provided, the system comprising

[0158] Long Term Evolution Radio Access Node LTE RAN E-UTRAN eNB,

[0159] Next Generation Radio Access Node NG RAN,

[0160] Access and mobility management function AMF,

[0161] Mobility Management Entity MME 103,

[0162] Serving Gateway SGW,

[0163] Visitor Session Management Function V-SMF,

[0164] The system is suitable for

[0165] -NG RAN (denoted as source RAN) decides 1 that the UE should be handed over to LTE RAN (denoted as target RAN) and sends a Handover Required message to AMF,

[0166] - The AMF determines from the “Target eNB Identifier” IE that the type of 2a handover is a handover to E-UTRAN, the AMF selects an MME and sends an Nsmf_PDU Session_Context Request requesting the V-SMF for each PDU Session associated with the 3GPP access to provide an SM context which also includes the mapped EPS bearer context,

[0167] -AMF receives 2c Nsmf_PDU Session_Context Request Response,

[0168] -AMF sends a relocation request to MME,

[0169] -MME and SGW participate in 4 and 5 to create session request and response messages.

[0170] -MME sends a 6 handover request to LTE RAN,

[0171] - The LTE RAN allocates 6 the resources or bearers requested by the MME, even if said resources or said bearers are not included in the transparent container from the source RAN.

[0172] LTE RAN 6 is OK

[0173] -- For bearers that are not part of a source-to-destination transparent container, no forwarding tunnel is allocated.

[0174] -- Include bearers requested by the source RAN and by the core network in the target-to-source transparent container.

[0175] The access and mobility management function AMF may be adapted to perform an Nmsf packet data unit PDU session context request 2a to the SMF even for PDU sessions for which there is currently no user plane, i.e. for PDU sessions not included in the handover required message 1 from the next generation NG radio access node RAN.

[0176] A method is also provided for an access and mobility management function, AMF, which is suitable for executing an Nmsf packet data unit, PDU session context request 2a to the SMF, even for PDU sessions for which there is currently no user plane, i.e., for PDU sessions not included in a handover required message 1 from a next generation NG radio access node RAN.

[0177] A method for an AMF adapted to not apply indirect data forwarding to a PDU session that previously had no user plane in a Next Generation NG-Radio Access Node RAN is provided.

[0178] A method is provided for a Next Generation Radio Access Node, NG RAN gNB, adapted to accept a handover command 11a from an Access and Mobility Management Function, AMF, even when a transparent container from a target RAN, such as an eNB, includes more user planes for bearers than required by the NG-RAN, the NG-RAN being further adapted to pass the handover command 11b to a UE.

[0179] Furthermore, a method for a UE is adapted to associate 11 a QoS flow currently having no user plane resources with an EPS bearer ID to be established in a HO command.

[0180] Furthermore, according to an embodiment, there is provided:

[0181] A long term evolution radio access node LTE RAN E-UTRAN eNB having a radio interface IF_M and a processing circuit PCU_M, the processing circuit of the base station being suitable for

[0182] - participate in a handover from a Next Generation RAN (denoted as Source RAN) to said LTE RAN (denoted as Target RAN),

[0183] - receiving a handover request message 6 from the mobility management entity MME,

[0184] - Allocate 6 resources or bearers requested by the mobility management entity MME, even if said resources or said bearers are not included in the transparent container from the source RAN.

[0185] An access and mobility management function, AMF, adapted to execute an Nmsf packet data unit, PDU session context request 2a to the SMF, even for PDU sessions for which there is currently no user plane, i.e. for PDU sessions not included in a handover required message 1 from a next generation NG radio access node RAN.

[0186] A Next Generation Radio Access Node RAN NG-RAN gNB, adapted to accept a handover command 11a from an AMF even when a transparent container from a target RAN, such as an LTE RAN eNB, includes more user planes for bearers than required by the NG-RAN (1), the NG-RAN being further adapted to pass the handover command 11b to a UE.

[0187] A UE is adapted to associate 11 a QoS flow currently having no user plane resources with an EPS bearer ID to be established in a HO command.

Claims

1. A method for switching one or more protocol data unit (PDU) sessions of a user equipment (UE) from a fifth generation (5G) system (5GS) to an evolved packet system (EPS), wherein the one or more PDU sessions include at least one PDU session without a user plane (UP) connection, the method comprising: At the Next Generation Radio Access Network (NG-RAN) node of 5GS: - Sending a handover required message to the access and mobility function AMF of the 5GS for handing over the UE to the Evolved Universal Terrestrial Radio Access Network E-UTRAN of the EPS, wherein the handover required message includes a source-to-target transparent container for data forwarding, wherein the source-to-target transparent container includes information indicating one or more bearers corresponding to a 5G quality of service QoS flow; At the AMF: - receiving the handover required message from the NG-RAN node; as well as - Send a forward relocation request to the mobility management entity MME of the EPS, wherein the forward relocation request includes packet data network PDN connection information for one or more session management functions SMF to maintain at least one PDU session without UP connection; At the MME: - receiving the forward redirection request from the AMF; as well as - sending a handover request to the E-UTRAN node of the EPS, the handover request including information indicating one or more bearers requested by the MME for handover; as well as At the E-UTRAN node: - receiving the handover request from the MME; as well as - for each of the one or more bearers requested by the MME in the handover request, allocating resources for the bearer even if the bearer is not one of the one or more bearers indicated in the source-to-target transparent container.

2. A method for a Long Term Evolution Radio Access Node LTE RAN of an Evolved Universal Terrestrial Radio Access Network E-UTRAN “eNB” in an Evolved Packet System EPS, for handing over one or more Protocol Data Unit (PDU) sessions of a User Equipment UE from a Fifth Generation 5G System 5GS to the EPS, wherein the one or more PDU sessions include at least one PDU session without a User Plane UP connection, the method comprising: - participate in handover from 5GS RAN to said LTE RAN, - receiving a handover request message from a mobility management entity MME of the EPS, for handing over the one or more PDU sessions of the UE from 5GS to EPS, the handover request including information indicating the one or more bearers requested by the MME for the handover; as well as - for each of the one or more bearers requested by the MME in the handover request, allocating resources requested by the mobility management entity MME, even if the bearer is not one of the one or more bearers included in the transparent container.