WO2022099453A1 - Procédés, entités et support lisible par ordinateur pour l'insertion ulcl - Google Patents

Procédés, entités et support lisible par ordinateur pour l'insertion ulcl Download PDF

Info

Publication number
WO2022099453A1
WO2022099453A1 PCT/CN2020/127784 CN2020127784W WO2022099453A1 WO 2022099453 A1 WO2022099453 A1 WO 2022099453A1 CN 2020127784 W CN2020127784 W CN 2020127784W WO 2022099453 A1 WO2022099453 A1 WO 2022099453A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
ulcl
plane entity
user plane
address
Prior art date
Application number
PCT/CN2020/127784
Other languages
English (en)
Inventor
Chunbo Wang
Jan Backman
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Chunbo Wang
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ), Chunbo Wang filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/CN2020/127784 priority Critical patent/WO2022099453A1/fr
Publication of WO2022099453A1 publication Critical patent/WO2022099453A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/088—Access security using filters or firewalls
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node

Definitions

  • the present disclosure generally relates to the technical field of communication technologies, and particularly to methods, entities, and computer readable media for Uplink Classifier (ULCL) insertion in Evolved Packet Core (EPC) .
  • ULCL Uplink Classifier
  • EPC Evolved Packet Core
  • 3GPP Releases 15 and 16 specify ULCL for 5G core network.
  • the ULCL function provides multiple Packet Data Unit (PDU) Session anchors (PSAs) in the data path of a PDU session.
  • PDU Packet Data Unit
  • PSAs Packet Data Unit
  • the UL traffic is classified by ULCL and forwarded to different anchor User plane Functions (UPFs) based on the traffic forwarding rules provided by the Session Management Function (SMF) .
  • UPFs User plane Functions
  • Such functions provide edge computing for the terminals, e.g. the vehicles, so as to route the traffic matching the local access through the local Data Network (DN) .
  • DN Local Data Network
  • FIG. 1 (corresponding to Figure 5.6.4.2-1 of 3GPP TS23.501 v16.6.0, and 3GPP TS23.501 v16.6.0 is incorporated herein by reference in its entirety) schematically illustrates a User plane Architecture for the ULCL, in which insertion of an ULCL PSA in a data path of a PDU Session is depicted.
  • the SMF may decide to insert a ULCL PSA in the data path of a PDU Session during or after the PDU Session Establishment, or to remove a ULCL PSA from the data path of a PDU Session (e.g., due to application service termination) .
  • the SMF may include more than one UPF supporting the UL CL functionality in the data path of a PDU Session.
  • the network may need to relocate a UPF acting as ULCL and establish a new PSA for access to the local DN.
  • the source to target ULCL and PSA UPF relocation procedure is schematically illustrated in FIG. 2 (corresponding to Figure 4.3.5.7-1 of 3GPP TS23.502 v16.6.0, and 3GPP TS23.502 v16.6.0 is incorporated herein by reference in its entirety) .
  • the UE has an established PDU Session with a UPF including the PDU Session Anchor (Remote UPF) .
  • the PDU Session user plane involves at least the Source (R) AN, Source Branching Point or Source UL CL, local Source UPF (PSA2) and the Remote UPF (PDU Session Anchor, PSA1) , where Source Branching Point or Source UL CL and PSA2 can be co-located.
  • the SMF decides to change the Branching Point or the ULCL due to UE mobility.
  • the SMF selects a local Target UPF (PSA3) and using N4 establishes the local Target UPF for the PDU Session.
  • PSA3 local Target UPF
  • N4 the local Target UPF for the PDU Session.
  • the SMF also allocates a new IPv6 prefix corresponding to PSA3, and if the PCF has subscribed to the IP allocation/release event, the SMF performs the Session Management Policy Modification procedure as defined in clause 4.16.5 of 3GPP TS23.502 v16.6.0 to provide the new allocated IPv6 prefix to the PCF.
  • the SMF may send an earlier notification to the Application Function (AF) after PSA3 is selected.
  • AF Application Function
  • 5G Core 5G Core
  • AF Application Function
  • the SMF waits for a notification response from the AF before configuring the PSA3. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure.
  • the SMF selects a UPF and using N4 establishes the Target Branching Point or Target ULCL for the PDU Session. SMF provides the necessary uplink forwarding rules towards the PSA3 and PSA1 including the Tunnel Info for each UPF. If session continuity upon ULCL relocation is used, the SMF also uses N4 to establish an N9 forwarding tunnel between the Source ULCL and Target ULCL, including the Tunnel Info for each UPF. In addition, the AN Tunnel Info to target (R) AN is provided for downlink forwarding. In the case of ULCL, the SMF provides traffic filters indicating what traffic shall be forwarded towards PSA3, PSA1 and Source ULCL, respectively.
  • the SMF also provides traffic filters for the IPv6 prefixes corresponding to PSA3 and PSA1 indicating what traffic shall be forwarded towards PSA3 and PSA1 respectively.
  • Target Branching Point or Target ULCL provides the CN Tunnel Info for downlink traffic.
  • the SMF updates the PSA1 via N4. It provides the PDU Session CN Tunnel Info for the downlink traffic.
  • the SMF updates the PSA3. It provides the CN Tunnel Info for downlink traffic.
  • step 5 If the Target Branching Point or the Target ULCL and the PSA3 are co-located in a single UPF then step 5 is not needed.
  • the SMF sends a late notification to the AF and waits for a notification response from the AF. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure and remove the Target Branching Point or Target ULCL and PSA3.
  • the SMF updates (R) AN via N2 SM information over N11. It provides the new CN Tunnel Info corresponding to the Target Branching Point or the Target ULCL. If there is an existing UPF between the Target (R) AN and Target Branching Point or Target ULCL, the SMF updates the existing UPF via N4 instead of updating the (R) AN.
  • IPv6 multi-homing PDU Session if the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF sends a late notification to the AF and waits for a notification response from the AF. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure.
  • the SMF In the case of IPv6 multi-homing, the SMF notifies the UE of the availability of the new IP prefix @PSA3. This is performed using an IPv6 Router Advertisement message. Also, the SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message as described in clause 5.8.2.2.2 of 3GPP TS23.501 v16.6.0.
  • the SMF may re-configure the UE for the original IP prefix @PSA1, i.e. SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message as described in clause 5.8.2.2.2 of 3GPP TS23.501 v16.6.0.
  • the SMF sends a Late Notification to the AF indicating a change of DNAI as described in clause 4.3.6.3 of 3GPP TS23.502 v16.6.0.
  • SMF also sends notification to target AF as described in 4.3.6.3 and cancels any future notification message to source AF as it is no longer involved.
  • the message can include routing information to the application located in the target local DN.
  • the routing information to the application located in the target local DN can be determined by the AF based on the new DNAI, in which case the AF can invoke the AF triggered influence on traffic routing procedure targeting single UE as described in clause 4.3.6.4 of 3GPP TS23.502 v16.6.0, which assists the SMF in generation of the routing rule on the Target ULCL towards PSA3 (i.e. towards the application located in the target local DN) . It is up to network configuration whether the routing information to the application located in the target local DN is configured in the SMF or in the AF.
  • the AF can also trigger mechanisms that are out of the scope of this specification (e.g. IP-level or HTTP-level redirection) by which the traffic is redirected towards the application in the target local DN. Based on this redirection the UE starts using a new destination IP address which leads the Target ULCL to force the traffic towards PSA3.
  • IP-level or HTTP-level redirection e.g. IP-level or HTTP-level redirection
  • detection of no active traffic over the N9 forwarding tunnel is performed during a preconfigured time interval in order to release the N9 forwarding tunnel.
  • the detection can be done by either Source ULCL or Target ULCL, either of which notifies the SMF.
  • the SMF releases the Source Branching Point or the Source ULCL.
  • the 4G network will co-exist with 5G network for a long period.
  • 3GPP standard has defined the interworking between 5G System (5GS) and Evolved Packet System (EPS) (See 3GPP TS23.501 v16.6.0, clause 4.3.1 for 5GS Interworking with the Evolved Packet Core (EPC) in a Non-Roaming architecture) .
  • 5GS 5G System
  • EPS Evolved Packet System
  • EPC Evolved Packet Core
  • the single PGW-U anchor can’ t be changed during the lifetime of a Packet Data Network (PDN) connection (the PDN connection in the EPC (4G) corresponds to the PDU session in the 5GC) .
  • PDN Packet Data Network
  • PDN connection reactivation also called PDN reactivation
  • PDN connection release includes PDN connection release and PDN connection reestablishment, based on e.g. UE location and/or service information after mobility procedure is completed, so that the ULCL PSA is changed after the PDN reactivation
  • a method at a first control plane entity includes: determining that a second control plane entity selected by the first control plane entity supports selection of a first user plane entity and a ULCL function entity; and transmitting, to the second control plane entity, an indication of selecting a first user plane entity and a ULCL function entity.
  • the indication includes a first address, that is to be allocated to a first user plane entity, for a ULCL function entity to transmit Downlink (DL) traffic to the first user plane entity.
  • DL Downlink
  • the method further includes: receiving, from the second control plane entity, a second address, that is allocated to a ULCL function entity and transmitted by the ULCL function entity to the second control plane entity, for a first user plane entity to transmit UL traffic to the ULCL function entity.
  • the method further includes: selecting, based on the received second address, the first user plane entity; and transmitting the second address to the first user plane entity for the first user plane entity to transmit the UL traffic to the ULCL function entity.
  • the method further includes: transmitting the second address to a first mobility management entity.
  • the first user plane entity and the ULCL function entity are collocated.
  • the indication is transmitted in a Create Session Request message
  • the first address is an Internal Full Qualified-Tunnel Endpoint Identifier (F-TEID) that is transmitted in an S5/S8-U SGW F-TEID Information Element (IE) in the Create Session Request message.
  • F-TEID Internal Full Qualified-Tunnel Endpoint Identifier
  • IE F-TEID Information Element
  • the second address is an S5-U ULCL F-TEID that is received in an S5/S8-U PGW F-TEID IE in a Create Session Response message from the second control plane entity, transmitted in an S5/S8-U PGW F-TEID IE in a Create Session Response message to the mobility management entity, and transmitted in a UL remote Forwarding Action Rule (FAR) in a Packet Forwarding Control Protocol (PFCP) Session Establishment Request message to the first user plane entity.
  • FAR UL remote Forwarding Action Rule
  • the first control plane entity includes a Serving Gateway Control plane (SGW-C) entity
  • the second control plane entity includes a combined Packet Data Network Gateway Control plane (PGW-C) and SMF entity
  • the first user plane entity includes a Serving Gateway User plane (SGW-U) entity
  • the ULCL function entity includes a ULCL PSA entity
  • the first mobility management entity includes a Mobility Management Entity (MME) .
  • SGW-C Serving Gateway Control plane
  • PGW-C Packet Data Network Gateway Control plane
  • SGW-U Serving Gateway User plane
  • MME Mobility Management Entity
  • a method at a second control plane entity that supports selection of a first user plane entity and a ULCL function entity.
  • the method includes: performing a process of inserting a ULCL function entity during a connection establishment.
  • said performing the process of inserting the ULCL function entity includes: determining to insert a ULCL function entity; and performing session establishment with the ULCL function entity.
  • the ULCL function entity is determined to be inserted based on at least one of:
  • UE User Equipment
  • the service information includes at least one of:
  • DNAI Data Network Access Identifier
  • the traffic forwarding rule for the ULCL function entity includes routing contexts to local DN for edge breakout by the ULCL function entity.
  • said performing the process of inserting the ULCL function entity further includes: receiving, from a first control plane entity, an indication of selecting a first user plane entity and a ULCL function entity.
  • the indication includes a first address, that is to be allocated to the first user plane entity, for the ULCL function entity to transmit Downlink (DL) traffic to the first user plane entity.
  • DL Downlink
  • said performing the session establishment with the ULCL function entity further includes: triggering session establishment to a second user plane entity; and receiving, from the second user plane entity, a third address, that is allocated to the second user plane entity.
  • said performing the session establishment with the ULCL function entity further includes: transmitting, to the ULCL function entity, a session establishment request message; and receiving, from the ULCL function entity, a session establishment response message,
  • the session establishment request message includes: the first address, that is received from the first control plane entity, for the ULCL function entity to transmit DL traffic to the first user plane entity; the third address, that is received from the second user plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity; and the traffic forwarding rule for the ULCL function entity; and
  • the session establishment response message includes: a second address, that is allocated to the ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity; and a fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • said performing the session establishment with the ULCL function entity further includes: transmitting, to the second user plane entity, the received fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • said performing the session establishment with the ULCL function entity further includes: transmitting, to the first control plane entity, the received second address that is allocated to the ULCL function entity.
  • the first user plane entity and the ULCL function entity are collocated.
  • the indication is received in a Create Session Request message
  • the first address is an Internal F-TEID that is received in an S5/S8-U SGW F-TEID IE of the Create Session Request message.
  • the transmitted session establishment request message includes a PFCP Session Establishment Request message, which includes: a UL remote FAR that is set to an N9 PSA F-TEID as the third address, a DL remote FAR that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • the received session establishment response message includes a PFCP Session Establishment Response message, which includes: an S5-U ULCL F-TEID as the second address, and an N9 ULCL F-TEID as the fourth address.
  • the fourth address is an N9 ULCL F-TEID that is transmitted in a DL remote FAR in a PFCP Session Modification Request message.
  • the second address is an S5-U ULCL F-TEID that is transmitted in an S5/S8-U PGW F-TEID IE in a Create Session Response message.
  • the method further includes: receiving, from another first control plane entity, as a target first control plane entity, a fifth address that is allocated to another first user plane entity, as a target first user plane entity, and transmitted by the target first user plane entity to the target first control plane entity; and transmitting the fifth address to the ULCL function entity for the ULCL function entity to establish a session with the target first user plane entity to switch the DL traffic to the target first user plane entity from the first user plane entity as a source first user plane entity.
  • the fifth address is received in a case where the target first control plane entity receives the second address from a first mobility management entity, and transmits the second address to the target first user plane entity, wherein the second address was received by the first mobility management entity from the second control plane entity via the source first control plane entity.
  • the method further includes: transmitting, to the ULCL function entity, an indication of releasing a session between the ULCL function entity and the target first user plane entity.
  • the method further includes: re-performing the process of inserting a ULCL function entity for a new connection establishment to establish another ULCL function entity.
  • the fifth address is a Target S5/S8-U SGW F-TEID that is received in a Modify Bearer Request message, and is transmitted in a DL remote FAR of a PFCP Session Modification Request message.
  • the method further includes: transmitting, to the ULCL function entity, a session modification request message; and receiving, from the ULCL function entity, a session modification response message, which includes a sixth address that is allocated to the ULCL function entity for an access node to transmit UL traffic to the ULCL function entity.
  • the session modification request message is transmitted in a case where handover from an EPS to a 5GS is required.
  • the method further includes: receiving, from a second mobility management entity, a seventh address that is allocated to the access node; and transmitting the received seventh address to the ULCL function entity for the ULCL function entity to transmit DL traffic to the access node.
  • the method further includes: receiving a handover complete indication from the second mobility management entity; and triggering session modification to the ULCL function entity for the ULCL function entity to switch the DL traffic to the access node based on the received seventh address.
  • the method further includes: re-performing the process of inserting a ULCL function entity for a new connection establishment to establish another ULCL function entity.
  • the transmitted session modification request message includes a PFCP Session Modification Request message
  • the received session modification response message includes a PFCP Session Modification Response message, which includes an N3 ULCL F-TEID as the sixth address.
  • the seventh address is an N3 Next Generation-Radio Access Network (NG-RAN) F-TEID that is received in an Nsmf_PDU Session_Update_SM Context Request message, and is transmitted in a PFCP Session Modification Request message.
  • NG-RAN Next Generation-Radio Access Network
  • the first control plane entity may include an SGW-C entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include an SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity
  • the first mobility management entity includes a Mobility Management Entity (MME)
  • the second mobility management entity includes an Access and Mobility Management Function (AMF) entity.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • a method at a ULCL function entity includes: receiving a session establishment request message from a second control plane entity that supports selection of a first user plane entity and a ULCL function entity; and transmitting, to the second control plane entity, a session establishment response message.
  • the session establishment request message includes: a first address, that is to be allocated by a first control plane entity to the first user plane entity, and is received from the first control plane entity via the second control plane entity, for the ULCL function entity to transmit DL traffic to the first user plane entity; a third address, that is allocated to the second user plane entity, and is received from the second user plane entity via the second control plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity; and a traffic forwarding rule for the ULCL function entity; and the session establishment response message includes: a second address, that is allocated to the ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity; and a fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the traffic forwarding rule for the ULCL function entity includes routing contexts to local DN for edge breakout by the ULCL function entity.
  • the ULCL function entity is collocated with the first user plane entity.
  • the received session establishment request message includes a PFCP Session Establishment Request message, which includes: a UL remote FAR IE that is set to an N9 PSA F-TEID as the third address, a DL remote FAR IE that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • PFCP Session Establishment Request message which includes: a UL remote FAR IE that is set to an N9 PSA F-TEID as the third address, a DL remote FAR IE that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • the transmitted session establishment response message includes a PFCP Session Establishment Response message, which includes: an S5-U ULCL F-TEID as the second address, and a N9 ULCL F-TEID as the fourth address.
  • the method further includes: receiving, from the second control plane entity, a fifth address, that is allocated to another first user plane entity, as a target first user plane entity, for the ULCL function entity to switch the DL traffic to the target first user plane entity from the first user plane entity as a source first user plane entity, wherein the fifth address was received by the target first control plane entity from the target first user plane entity and transmitted to the second control plane entity.
  • the fifth address is received in a case where the target first control plane entity receives the second address from a first mobility management entity, and transmits the second address to the target first user plane entity, wherein the second address was received by the first mobility management entity from the second control plane entity via the source first control plane entity.
  • the method further includes: receiving, from the second control plane entity, an indication of releasing a session between the ULCL function entity and the target first user plane entity; and releasing the session between the ULCL function entity and the target first user plane entity.
  • the fifth address is a Target S5/S8-U SGW F-TEID that is received in a DL remote FAR of a PFCP Session Modification Request message.
  • the method further includes: receiving a session modification request message from the second control plane entity; and transmitting, to the second control plane entity, a session modification response message, which includes a sixth address that is allocated to the ULCL function entity for an access node to transmit UL traffic to the ULCL function entity.
  • the session modification request message is received in a case where handover from an EPS to a 5GS is required.
  • the method further includes: receiving, from the second control plane entity, a seventh address, that is allocated to the access node and transmitted to the second control plane entity from a second mobility management entity, for the ULCL function entity to transmit DL traffic to the access node.
  • the method further includes: switching the DL traffic to the access node based on the received seventh address, in a case where a handover complete indication is received by the second control plane entity from the second mobility management entity.
  • the received session modification request message includes a PFCP Session Modification Request message
  • the transmitted session modification response message includes a PFCP Session Modification Response message, which includes an N3 ULCL F-TEID as the sixth address.
  • the seventh address is an N3 NG-RAN F-TEID that is received in a PFCP Session Modification Request message.
  • the first control plane entity includes a SGW-C entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the first user plane entity includes an SGW-U entity
  • the ULCL function entity includes a ULCL PSA entity
  • the second user plane entity includes a PSA entity
  • the first mobility management entity is an MME
  • the second mobility management entity includes an AMF entity.
  • a method at a first user plane entity includes: receiving, from a first control plane entity, a second address, that is allocated to a ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity, wherein the second address was received by the first control plane entity from the ULCL function entity via a second control plane entity.
  • the second address is an S5-U ULCL F-TEID that is received in a UL remote FAR in a PFCP Session Modification Request message from the first control plane entity.
  • the first control plane entity includes a SGW-C entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the first user plane entity includes a SGW-U entity
  • the ULCL function entity includes a ULCL PSA entity.
  • a method at a second user plane entity includes: transmitting, to a second control plane entity, a third address allocated to the second user plane entity, which is to be used for a ULCL function entity to transmit UL traffic to the second user plane entity; and receiving, from the second control plane entity, a fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the second control plane entity supports selection of a first user plane entity and a ULCL function entity.
  • the first user plane entity and the ULCL function entity are collocated.
  • the third address is an N9 PSA F-TEID that is transmitted in a PFCP Session Establishment Response message
  • the fourth address is an N9 ULCL F-TEID that is transmitted in a DL remote FAR in a PFCP Session Modification Request message.
  • the second user plane entity includes a PSA entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the first user plane entity includes a SGW-U entity
  • the ULCL function entity includes a ULCL PSA entity.
  • a method at a second control plane entity that supports selection of a first user plane entity and a ULCL function entity includes: triggering first session modification to a ULCL function entity; and receiving, from the ULCL function entity, a second address and a fourth address allocated to the ULCL function entity, wherein the second address is used for the first user plane entity to transmit UL traffic to the ULCL function entity, and the fourth address is used for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the method is performed in a case where handover from a 5GS to an EPS is required.
  • the method further includes: triggering second session modification to the second user plane entity; and receiving, from the second user plane entity, a third address, that is allocated to the second user plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity.
  • the method further includes: transmitting the second address to a mobility management entity.
  • the method further includes: receiving, from a first control plane entity, an eighth address that is allocated to the first user plane entity; and transmitting, to the ULCL function entity, the eighth address for the ULCL function entity to transmit DL traffic to the first user plane entity and the third address for the ULCL function entity to transmit UL traffic to the second user plane entity.
  • the method further includes: transmitting, to the second user plane entity, the fourth address for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the second address is an S5-U ULCL F-TEID that is received in a PFCP Session Modification Response message from the ULCL function entity
  • the fourth address is a N9 ULCL F-TEID that is received in the PFCP Session Modification Response message from the ULCL function entity.
  • the third address is an N9 PSA F-TEID that is received in a PFCP Session Modification Response message from the second user plane entity.
  • the third address is an N9 PSA F-TEID that is transmitted in a PFCP Session Modification Request message to the ULCL function entity
  • the eighth address is an S5/S8-U SGW F-TEID that is transmitted in the PFCP Session Modification Request message to the ULCL function entity.
  • the fourth address is the N9 ULCL F-TEID that is transmitted in a PFCP Session Modification Request message to the second user plane entity.
  • the method further includes: transmitting, to the ULCL function entity, an indication of releasing a session between the ULCL function entity and the first user plane entity.
  • the mobility management entity includes an AMF entity
  • the first control plane entity includes a SGW-C entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the first user plane entity includes a SGW-U entity
  • the ULCL function entity includes a ULCL PSA entity
  • the second user plane entity includes a PSA entity.
  • the method further includes: performing the process of inserting a ULCL function entity according to the second aspect of the present disclosure.
  • a method at a ULCL function entity includes: receiving, from a second control plane entity, a trigger of first session modification for the ULCL function entity; and transmitting, to the second control plane entity, a second address and a fourth address allocated to the ULCL function entity, wherein the second address is used for the first user plane entity to transmit UL traffic to the ULCL function entity, and the fourth address is used for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the method is performed in a case where handover from a 5GS to an EPS is required.
  • the method further includes: receiving a third address and an eighth address from the second control plane entity, wherein the third address is allocated to the second user plane entity, and forwarded from the second user plane entity by the second control plane entity for the ULCL function entity to transmit UL traffic to the second user plane entity, and the eighth address is allocated to the first user plane entity, and forwarded from the first control plane entity by the second control plane entity for the ULCL function entity to transmit UL traffic to the first user plane entity.
  • the second address is an S5-U ULCL F-TEID that is transmitted in a PFCP Session Modification Response message to the second control plane entity
  • the fourth address is an N9 ULCL F-TEID that is transmitted in the PFCP Session Modification Response message to the second control plane entity.
  • the third address is an N9 PSA F-TEID that is received in a PFCP Session Modification Request message from the second control plane entity
  • the eighth address is an S5/S8-U SGW F-TEID that is received in the PFCP Session Modification Request message from the second control plane entity.
  • the method further includes: receiving, from the second control plane entity, an indication of releasing a session between the ULCL function entity and the first user plane entity; and releasing the session between the ULCL function entity and the first user plane entity.
  • the first control plane entity may include a SGW-C entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include a SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity
  • the second user plane entity may include a PSA entity.
  • a method at a second user plane entity includes: transmitting, to a second control plane entity, a third address allocated to the second user plane entity, which is to be used for a ULCL function entity to transmit UL traffic to the second user plane entity; and receiving, from the second control plane entity, a fourth address, that is allocated to the ULCL function entity and forwarded from the ULCL function entity by the second control plane entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the third address is an N9 PSA F-TEID that is transmitted in a PFCP Session Modification Response message
  • the fourth address is an N9 ULCL F-TEID that is received in a PFCP Session Modification Request message from the second control plane entity.
  • the second user plane entity includes a PSA entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the ULCL function entity includes a ULCL PSA entity
  • a first control plane entity includes: at least one processor, and at least one memory, storing instructions which, when executed on the at least one processor, cause the first control plane entity to perform any of the methods according to the first aspect of the present disclosure.
  • a second control plane entity that supports selection of a first user plane entity and a ULCL function entity.
  • the second control plane entity includes: at least one processor, and at least one memory, storing instructions which, when executed on the at least one processor, cause the second control plane entity to perform any of the methods according to the second and sixth aspects of the present disclosure.
  • a ULCL function entity includes: at least one processor, and at least one memory, storing instructions which, when executed on the at least one processor, cause the ULCL function entity to perform any of the methods according to the third and seventh aspects of the present disclosure.
  • a first user plane entity includes: at least one processor, and at least one memory, storing instructions which, when executed on the at least one processor, cause the first user plane entity to perform any of the methods according to the fourth aspect of the present disclosure.
  • a second user plane entity includes: at least one processor, and at least one memory, storing instructions which, when executed on the at least one processor, cause the second user plane entity to perform any of the methods according to the fifth and eighth aspects of the present disclosure.
  • a computer readable storage medium has computer program instructions stored thereon, the computer program instructions, when executed by at least one processor, causing the at least one processor to perform the method according to any of the first to eighth aspects of the present disclosure.
  • ⁇ providing solutions to change ULCL function by triggering PDN reactivation according to at least the UE location and the service information after the completion of the UE mobility procedure or the handover between 5GS and EPS.
  • FIG. 1 schematically illustrates a user plane architecture for ULCL function
  • FIG. 2 schematically shows exemplary simultaneous change of Branching Point or ULCL and additional PSAfor a PDU Session in 5GS;
  • FIG. 3 schematically shows an exemplary network architecture for over which the present disclosure can be implemented
  • FIG. 4 schematically shows a method for ULCL insertion at a first control plane entity according to a first exemplary embodiment of the present disclosure
  • FIG. 5 schematically shows a method for ULCL insertion at a second control plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 6 schematically shows a method for ULCL insertion at a ULCL function entity according to the first exemplary embodiment of the present disclosure
  • FIG. 7 schematically shows a method for ULCL insertion at a first user plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 8 schematically shows a method for ULCL insertion at a second user plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 9 schematically shows an exemplary signaling sequence diagram of ULCL insertion at initial PDN connection establishment procedure, in which the methods at various entities according to the first exemplary embodiment of the present disclosure are applied;
  • FIG. 10 schematically shows exemplary user plane traffic routing for collocated SGW-U and ULCL PSA1 according to the first exemplary embodiment of the present disclosure
  • FIG. 11A schematically shows an exemplary signaling sequence diagram of ULCL changing after SGW relocation Type 1, in which methods at various entities according to the first exemplary embodiment of the present disclosure are applied;
  • FIG. 11B schematically shows an exemplary signaling sequence diagram of a ULCL changing after SGW relocation Type 2, in which the methods at various entities according to the first exemplary embodiment of the present disclosure are applied;
  • FIG. 12 schematically shows an exemplary traffic flow between Target SGW-U and ULCL PSA1 before PDN reactivation according to the first exemplary embodiment of the present disclosure
  • FIG. 13 schematically shows an exemplary signaling sequence diagram of ULCL keeping in a scenario of Handover (HO) from EPS to 5GS and ULCL changing after the HO from EPS to 5GS, in which the methods at various entities according to the first exemplary embodiment of the present disclosure are applied;
  • HO Handover
  • FIG. 14 schematically shows a method for ULCL keeping at a second control plane entity according to a second exemplary embodiment of the present disclosure
  • FIG. 15 schematically shows a method for ULCL keeping at a ULCL function entity according to the second exemplary embodiment of the present disclosure
  • FIG. 16 schematically shows a method for ULCL keeping at a second user plane entity according to the second exemplary embodiment of the present disclosure
  • FIG. 17 schematically shows an exemplary signaling sequence diagram of ULCL keeping in a scenario of HO from 5GS to EPS and ULCL changing after the HO from 5GS to EPS, in which the methods at various entities according to the second exemplary embodiment of the present disclosure are applied;
  • FIG. 18 schematically shows an exemplary traffic flow between SGW-U and ULCL PSA1 after handover from 5GS to EPS before PDN reactivation according to the second exemplary embodiment of the present disclosure
  • FIG. 19 schematically shows an exemplary structural block diagram of a first control plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 20 schematically shows another exemplary structural block diagram of a first control plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 21 schematically shows an exemplary structural block diagram of a second control plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 22 schematically shows another exemplary structural block diagram of a second control plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 23 schematically shows an exemplary structural block diagram of a ULCL function entity according to the first exemplary embodiment of the present disclosure
  • FIG. 24 schematically shows another exemplary structural block diagram of a ULCL function entity according to the first exemplary embodiment of the present disclosure
  • FIG. 25 schematically shows an exemplary structural block diagram of a first user plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 26 schematically shows another exemplary structural block diagram of a first user plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 27 schematically shows an exemplary structural block diagram of a second user plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 28 schematically shows another exemplary structural block diagram of a second user plane entity according to the first exemplary embodiment of the present disclosure
  • FIG. 29 schematically shows an exemplary structural block diagram of a second control plane entity according to the second exemplary embodiment of the present disclosure
  • FIG. 30 schematically shows another exemplary structural block diagram of a second control plane entity according to the second exemplary embodiment of the present disclosure
  • FIG. 31 schematically shows an exemplary structural block diagram of a ULCL function entity according to the second exemplary embodiment of the present disclosure
  • FIG. 32 schematically shows another exemplary structural block diagram of a ULCL function entity according to the second exemplary embodiment of the present disclosure
  • FIG. 33 schematically shows an exemplary structural block diagram of a second user plane entity according to the second exemplary embodiment of the present disclosure.
  • FIG. 34 schematically shows another exemplary structural block diagram of a second user plane entity according to the second exemplary embodiment of the present disclosure.
  • exemplary is used herein to mean “illustrative, ” or “serving as an example, ” and is not intended to imply that a particular embodiment is preferred over another or that a particular feature is essential.
  • first and second, ” and similar terms are used simply to distinguish one particular instance of an item or feature from another, and do not indicate a particular order or arrangement, unless the context clearly indicates otherwise.
  • step, ” as used herein is meant to be synonymous with “operation” or “action. ” Any description herein of a sequence of steps does not imply that these operations must be carried out in a particular order, or even that these operations are carried out in any order at all, unless the context or the details of the described operation clearly indicates otherwise.
  • references in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” etc. indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • the term “network” refers to a network following any suitable (wireless or wired) communication standards.
  • the wireless communication standards may comprise new radio (NR) , long term evolution (LTE) , LTE-Advanced, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , Code Division Multiple Access (CDMA) , Time Division Multiple Address (TDMA) , Frequency Division Multiple Access (FDMA) , Orthogonal Frequency-Division Multiple Access (OFDMA) , Single carrier frequency division multiple access (SC-FDMA) and other wireless networks.
  • NR new radio
  • LTE long term evolution
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Address
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single carrier frequency division multiple access
  • a CDMA network may implement a radio technology such as Universal Terre
  • UTRA includes WCDMA and other variants of CDMA.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • Ad-hoc network wireless sensor network
  • the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the wireless communication protocols as defined by a standard organization such as 3GPP or the wired communication protocols.
  • the wireless communication protocols may comprise the first generation (1G) , 2G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • entity refers to a network device or network node or network function in a communication network, and may also refer to a virtualized entity that may be implemented on cloud.
  • a core network device may offer numerous servicesto customers who are interconnected by an access network device. Each access network device is connectable to the core network device over a wired or wireless connection.
  • CN entity refers to any suitable function which can be implemented in a network entity (physical or virtual) of a communication network.
  • a network entity can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the 5G Core Network system may comprise a plurality of functions such as AMF, SMF, UDM (Unified Data Management) , PCF (Policy Control Function) , UPF (User plane Function) , NRF (Network Repository Function) , etc.
  • the 4G Core Network system may include MME, HSS (home subscriber server) , P-GW, BM-SC, etc.
  • the CN entity may comprise different types of functions for example depending on the specific network.
  • FIG. 3 schematically shows an exemplary network architecture over which the present disclosure can be implemented, in which the SGW-U and the ULCL function entity (e.g., ULCL PSA1) are logically separate user plane entities but are collocated physically, and are controlled by the SGW-C and the combined PGW-C+SMF respectively via separate PFCP sessions.
  • the SGW-U and the ULCL function entity e.g., ULCL PSA1
  • the SGW-C and the combined PGW-C+SMF respectively via separate PFCP sessions.
  • combined PGW-C+SMF refers to a control plane entity having functions of both PGW-C and SMF.
  • the combined PGW-C+SMF as proposed in the present disclosure can support selection of the collocated user plane, i.e., the collocated SGW-U and the ULCL function entity, based on system configuration.
  • the collocation of the SGW-U and the ULCL function entity as proposed in the present disclosure may enable to reduce one hop (from RAN to DN) in the user plane, which may reduce the user plane latency, and save user plane resource.
  • the combined PGW-C+SMF establishes the UPF PSA0 and the inserts ULCL PSA1 at the PDN connection establishment.
  • the SGW-C selects and controls the SGW-U which is collocated with the ULCL PSA1.
  • a ULCL function entity e.g., ULCL PSA1 as shown in FIG. 3
  • a ULCL function entity e.g., ULCL PSA1 as shown in FIG. 3
  • ULCL PSA1 ULCL PSA1 as shown in FIG. 3
  • two PSA e.g., ULCL PSA1 and UPF PSA0 as shown in FIG. 3
  • SGW relocation Type 1 (corresponding to FIG. 11A)
  • SGW relocation Type 2 (corresponding to FIG. 11B)
  • HO from EPS to 5GS (corresponding to FIG. 13)
  • HO from 5GS to EPS (corresponding to FIG. 17) , etc.;
  • PDN reactivation including PDN connection release and PDN connection reestablishment, based on e.g. UE location and/or service information after the mobility procedure is completed.
  • the first control plane entity may be any node that can be configured to perform the method 400 as described below, including a virtualized entity that may be implemented on cloud..
  • the first control plane entity may determine that a second control plane entity selected by the first control plane entity can support selection of a first user plane entity and a ULCL function entity that are collocated (e.g., based on system configuration) .
  • the first control plane entity may transmit an indication to the selected second control plane entity, indicating to the second control plane entity that collocated user plane (i.e., a first user plane entity and a ULCL function entity that are collocated) shall be selected.
  • the second control plane entity that collocated user plane i.e., a first user plane entity and a ULCL function entity that are collocated
  • the indication may include a first address, e.g., a reserved Internal F-TEID, which may take an unused IP address, such as 0.0.0.0.
  • the first address may be allocated to a first user plane entity for its collocated ULCL function entity to transmit DL traffic to the first user plane entity.
  • the indication may be transmitted in a Create Session Request message to the second user plane entity, and the first address may be an Internal F-TEID that is transmitted in an S5/S8-U SGW F-TEID IE in the Create Session Request message.
  • the first control plane entity may receive, from the second control plane entity, a second address, that is allocated to a ULCL function entity and transmitted by the ULCL function entity to the second control plane entity, for a first user plane entity to transmit UL traffic to the ULCL function entity.
  • the first control plane entity may select the first user plane entity collocated with the ULCL function entity, based on the received second address. Then, the first control plane entity may transmit the second address to the first user plane entity for the first user plane entity to transmit the UL traffic to the ULCL function entity.
  • the second address may be an S5-U ULCL F-TEID that is received in an S5/S8-U PGW F-TEID IE in a Create Session Response message from the second control plane entity, and may be transmitted in a UL remote FAR in a PFCP Session Establishment Request message to the first user plane entity.
  • the first control plane entity may also transmit the second address to a first mobility management entity.
  • the second address may be an S5-U ULCL F-TEID that is transmitted in an S5/S8-U PGW F-TEID IE in a Create Session Response message to the first mobility management entity.
  • the first control plane entity may include an SGW-C entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include an SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity.
  • the second control plane entity may be any node that can be configured to perform the method 500 as described below, including a virtualized entity that may be implemented on cloud.
  • the method 500 at the second control plane entity at least partly corresponds to the method 400 at the first control plane entity.
  • some description of the method 500 may refer to that of method 400 as previously described, and thus will be omitted here for simplicity.
  • the second control plane entity that supports selection of a first user plane entity and a ULCL function entity may perform a process of inserting a ULCL function entity during a connection establishment.
  • the second control plane entity may receive an indication from the first control plane entity, indicating, to the second control plane entity, of selecting a first user plane entity and a ULCL function entity that are collocated.
  • the indication includes a first address, that is to be allocated to the first user plane entity, for the ULCL function entity to transmit DL traffic to the first user plane entity.
  • the indication may be received in a Create Session Request message from the first user plane entity, and the first address may be an Internal F-TEID that is transmitted in an S5/S8-U SGW F-TEID IE in the Create Session Request message.
  • the second control plane entity may also trigger session establishment to a second user plane entity; and receive, from the second user plane entity, a third address, that is allocated to the second user plane entity.
  • the second control plane entity may determine to insert a ULCL function entity, and perform session establishment with the ULCL function entity.
  • the ULCL function entity may be determined to be inserted based on at least one of: UE location, or service information related to the ULCL function entity.
  • the service information may include at least one of: a DNAI, or a traffic forwarding rule for the ULCL function entity.
  • the service information may be configured locally in the second control plane entity, or based on Policy and Charging Control (PCC) rules received from the PCF.
  • PCC Policy and Charging Control
  • the concept of the service information may refer to 3GPP TS 29.512 V17.0.0, and 3GPP TS 29.512 V17.0.0 is incorporated herein by reference in its entirety.
  • the traffic forwarding rule for the ULCL function entity may include routing contexts, e.g., N6 interface information, to local DN (also called Edge DN) for edge breakout by the ULCL function entity.
  • the routing contexts may be used by the ULCL function entity to forward the UL traffic to the Edge DN via the N6 interface, as shown in FIG. 10.
  • the second control plane entity may transmit a session establishment request message to the ULCL function entity; and receive a session establishment response message from the ULCL function entity.
  • the session establishment request message may include:
  • the first address that is received from the first control plane entity, for the ULCL function entity to transmit DL traffic to the first user plane entity,
  • the third address that is received from the second user plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity
  • the session establishment response message may include:
  • a second address that is allocated to the ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity
  • a fourth address that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the transmitted session establishment request message may include a PFCP Session Establishment Request message, which may include: a UL FAR that is set to a N9 PSA F-TEID as the third address, a DL remote FAR that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • PFCP Session Establishment Request message may include: a UL FAR that is set to a N9 PSA F-TEID as the third address, a DL remote FAR that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • the received session establishment response message may include a PFCP Session Establishment Response message, which may include: an S5-U ULCL F-TEID as the second address, and an N9 ULCL F-TEID as the fourth address.
  • the second control plane entity may transmit, to the second user plane entity, the received fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the fourth address may be an N9 ULCL F-TEID that is transmitted in a DL remote FAR in a PFCP Session Modification Request message.
  • the second control plane entity may transmit, to the first control plane entity, the received second address that is allocated to the ULCL function entity.
  • the second address may be an S5-U ULCL F-TEID that is transmitted in an S5/S8-U PGW F-TEID IE in a Create Session Response message.
  • the first user plane entity may transmit the UL traffic to the ULCL function entity via the S5-U interface between the ULCL function entity and the first user plane entity based on the second address (S5-U ULCL F-TEID) ; and the ULCL function entity may divert the UL traffic in two ways based on the traffic forwarding rules for the ULCL function entity.
  • the UL traffic in one way may be forwarded by the ULCL function entity to the Edge DN via the N6 interface between the ULCL function entity and the Edge DN; and the UL traffic in another way may be forwarded by the ULCL function entity to the second user plane entity based on the received third address (e.g., N9 PSA F-TEID) via the N9 interface between the ULCL function entity and the second user plane entity and in turn forwarded by the second user plane entity to the central DN via the N6 interface between the second user plane entity and the central DN.
  • the received third address e.g., N9 PSA F-TEID
  • the DL traffic for edge computing from the Edge DN may enter the second user plane entity via the N6 interface and may be forwarded to the ULCL function entity via the N9 interface based on the fourth address (N9 ULCL F-TEID) , and the ULCL function entity may transmit the DL traffic to the first user plane entity via the S5-U interface based on the received first address (e.g., Internal F-TEID) .
  • the received first address e.g., Internal F-TEID
  • the second control plane entity places the second address (e.g., S5-U ULCL F-TEID) , that is allocated to the ULCL function entity, in an existing IE (e.g., S5/S8-U PGW F-TEID IE) of the Create Session Response message, and transmits the Create Session Response message to the first control plane entity.
  • S5/S8-U PGW F-TEID IE e.g., S5/S8-U PGW F-TEID IE
  • the first control plane entity e.g., the SGW-C
  • the first mobility management entity e.g., the MME
  • receiving the Create Session Response message would take the IE of the Create Session Response message as a normal one for their normal subsequent operations. That is, those other entities do not know that the S5/S8-U PGW F-TEID IE is filled with a new value (second address) .
  • the first control plane entity e.g., the SGW-C
  • the first control plane entity may select the first user plane entity (e.g., the SGW-U) collocated with the ULCL function entity, and transmit a PFCP Session Establishment Request message to the first user plane entity (e.g., the SGW-U) with the UL remote FAR set to the second address (e.g., S5-U ULCL F-TEID) it receives.
  • the ULCL function entity is transparent to the first user plane entity (e.g., the SGW-U) and the first control plane entity (e.g., the SGW-C) .
  • the first user plane entity (e.g., the SGW-U) and the first control plane entity (e.g., the SGW-C) regard the ULCL function entity as a second user plane entity (e.g., a PGW-U) .
  • the first mobility management entity e.g., the MME
  • the ULCL function entity is also transparent to the first mobility management entity (e.g., the MME) . That is, the first mobility management entity regards the ULCL function entity as a legacy PGW-U.
  • the method 500 may further include the following steps.
  • the second control plane entity may receive a fifth address from another first control plane entity, which is used as a target first control plane entity, wherein the fifth address is allocated to another first user plane entity, which is used as a target first user plane entity.
  • the fifth address may be transmitted by the target first user plane entity to the target first control plane entity, and forwarded by the target first control plane entity to the second control plane entity.
  • the second control plane entity may transmit the received fifth address to the ULCL function entity for the ULCL function entity to establish a session with the target first user plane entity to switch the DL traffic to the target first user plane entity from the first user plane entity, which is used as a source first user plane entity.
  • the fifth address may be a Target S5/S8-U SGW F-TEID that is received in a Modify Bearer Request message, and may be transmitted in a DL remote FAR of a PFCP Session Modification Request message.
  • the fifth address may be received in a case where the target first control plane entity receives the second address from a first mobility management entity, and transmits the second address to the target first user plane entity, wherein the second address was received by the first mobility management entity from the second control plane entity via the source first control plane entity.
  • the ULCL function entity may transmit the DL traffic to the target first user plane entity based on the received fifth address (e.g., Target S5/S8-U SGW F-TEID) , and the target first user plane entity may transmit the UL traffic to the ULCL function entity based on the received second address (e.g., S5-U ULCL F-TEID) .
  • the traffic may be routed between the UE and the original edge Data Network (DN) via the target first user plane entity and the ULCL function entity after the SGW relocation, until PDN reactivation is triggered.
  • DN edge Data Network
  • the second control plane entity may transmit, to the ULCL function entity, an indication of releasing the session between the ULCL function entity and the target first user plane entity.
  • the second control plane entity may then perform step S501 as previously described during PDN reactivation to perform the PDN connection reestablishment to insert another ULCL function entity, in particular, to insert another ULCL function entity collocated with another first user plane entity, e.g., in order to obtain better user experience.
  • the first user plane entity that is collocated with the newly inserted ULCL function entity may be the former target first user plane entity, or may be some other suitable first user plane entity, which depends on at least one of the UE location and the service information.
  • the method 500 may further include the following steps.
  • the second control plane entity may transmit, to the ULCL function entity, a session modification request message; and receive, from the ULCL function entity, a session modification response message, which includes a sixth address that is allocated to the ULCL function entity for the access node to transmit UL traffic to the ULCL function entity.
  • the second control plane entity may receive, from a second mobility management entity, a seventh address that is allocated to the access node; and transmit the received seventh address to the ULCL function entity for the ULCL function entity to transmit DL traffic to the access node.
  • the transmitted session modification request message may include a PFCP Session Modification Request message
  • the received session modification response message may include a PFCP Session Modification Response message, which may include an N3 ULCL F-TEID as the sixth address.
  • the seventh address may be an N3 NG-RAN F-TEID that is received in an Nsmf_PDU Session_Update_SM Context Request message, and is transmitted in a PFCP Session Modification Request message.
  • the second control plane entity may trigger session modification to the ULCL function entity for the ULCL function entity to switch the DL traffic to the access node based on the received seventh address.
  • the second control plane entity may then change the ULCL function entity either by the PDU session reactivation (referring to Clause 4.3.5.1 of 3GPP TS 23.502 v16.6.0, which is thus incorporated herein by reference in its entirety) or ULCL change (referring to Clause 4.3.5.7 of 3GPP TS 23.502 v16.6.0 which is thus incorporated herein by reference in its entirety) in 5GC, e.g., in order to obtain better user experience.
  • the first control plane entity may include an SGW-C entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include an SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity
  • the second user plane entity may include a PSA entity
  • the first mobility management entity is an MME
  • the second mobility management entity may include an AMF entity.
  • the ULCL function entity may be any node that can be configured to perform the method 600 as described below, including a virtualized entity that may be implemented on cloud.
  • the method 600 at the ULCL function entity at least partly corresponds to the method 500 at the second control plane entity.
  • some description of the method 600 may refer to that of method 500 as previously described, and thus will be omitted here for simplicity.
  • the second control plane entity may determine to insert a ULCL function entity based on at least one of: UE location, or service information related to the ULCL function entity.
  • the service information may include at least one of: a DNAI, or a traffic forwarding rule for the ULCL function entity.
  • the ULCL function entity may receive a session establishment request message from the second control plane entity that supports selection of a first user plane entity and a ULCL function entity that are collocated.
  • the ULCL function entity may transmit, to the second control plane entity, a session establishment response message.
  • the session establishment request message may include:
  • a first address that is to be allocated by a first control plane entity to the first user plane entity, and is received from the first control plane entity via the second control plane entity, for the ULCL function entity to transmit DL traffic to the first user plane entity;
  • a third address that is allocated to the second user plane entity, and is received from the second user plane entity via the second control plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity;
  • the traffic forwarding rule for the ULCL function entity may include routing contexts to local DN for edge breakout by the ULCL function entity.
  • the routing contexts may be used by the ULCL function entity to forward the UL traffic to the Edge DN via the N6 interface, as shown in FIG. 10.
  • the session establishment response message may include:
  • a fourth address that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the ULCL function entity is collocated with the first user plane entity.
  • the received session establishment request message may include a PFCP Session Establishment Request message, which may include: a UL remote FAR IE that is set to an N9 PSA F-TEID as the third address, a DL remote FAR IE that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • PFCP Session Establishment Request message may include: a UL remote FAR IE that is set to an N9 PSA F-TEID as the third address, a DL remote FAR IE that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • the transmitted session establishment response message may include a PFCP Session Establishment Response message, which may include: an S5-U ULCL F-TEID as the second address, and a N9 ULCL F-TEID as the fourth address.
  • the ULCL function entity may transmit the DL traffic to the first user plane entity based on the received first address (e.g., Internal F-TEID) , and transmit the UL traffic to the second user plane entity based on the received third address (e.g., N9 PSA F-TEID) .
  • the second user plane entity may transmit the UL traffic to the ULCL function entity based on the received fourth address (N9 ULCL F-TEID) that is transmitted by the ULCL function entity and forwarded by the second control plane entity.
  • the second address (S5-U ULCL F-TEID) forwarded by the second control plane entity from the ULCL function entity will be further forwarded by the first control user plane entity to the mobility management entity for the access node to transmit the UL traffic to the ULCL function entity.
  • the method 600 may further include the following steps.
  • the ULCL function entity may receive, from the second control plane entity, a fifth address, that is allocated to another first user plane entity, which is used as a target first user plane entity, for the ULCL function entity to switch the DL traffic to the target first user plane entity from the first user plane entity which is used as a source first user plane entity, wherein the fifth address was received by the target first control plane entity from the target first user plane entity and transmitted to the second control plane entity.
  • the fifth address may be a Target S5/S8-U SGW F-TEID that is received in a DL remote FAR of a PFCP Session Modification Request message.
  • the fifth address may be received in a case where the target first control plane entity receives the second address from a first mobility management entity, and transmits the second address to the target first user plane entity, wherein the second address was received by the first mobility management entity from the second control plane entity via the source first control plane entity.
  • the ULCL function entity may transmit the DL traffic to the target first user plane entity based on the received fifth address (e.g., Target S5/S8-U SGW F-TEID) , and the target first user plane entity may transmit the UL traffic to the ULCL function entity based on the received second address (e.g., S5-U ULCL F-TEID) .
  • the traffic may be routed between the UE and the original edge Data Network (DN) via the target first user plane entity and the ULCL function entity after the SGW relocation, until PDN reactivation is triggered.
  • DN edge Data Network
  • the ULCL function entity may receive, from the second control plane entity, an indication of releasing a session between the ULCL function entity and the target first user plane entity; and then release the session between the ULCL function entity and the target first user plane entity.
  • the second control plane entity may then perform step S501 as previously described during PDN reactivation to perform the PDN connection reestablishment to insert another ULCL function entity, in particular, to insert another ULCL function entity collocated with another first user plane entity, e.g., in order to obtain better user experience. Accordingly, the newly inserted ULCL function entity may perform the method 600 as previously described.
  • the method 600 may further include the following steps.
  • the ULCL function entity may receive a session modification request message from the second control plane entity; and transmit, to the second control plane entity, a session modification response message, which includes a sixth address that is allocated to the ULCL function entity for an access node to transmit UL traffic to the ULCL function entity.
  • the received session modification request message may include a PFCP Session Modification Request message
  • the transmitted session modification response message may include a PFCP Session Modification Response message, which may include an N3 ULCL F-TEID as the sixth address.
  • the ULCL function entity may receive, from the second control plane entity, a seventh address, that is allocated to the access node and transmitted to the second control plane entity from a second mobility management entity, for the ULCL function entity to transmit DL traffic to the access node.
  • the ULCL function entity may switch the DL traffic to the access node based on the received seventh address.
  • the seventh address may be an N3 NG-RAN F-TEID that is received in a PFCP Session Modification Request message.
  • the second control plane entity may then change the ULCL function entity either by the PDU session reactivation (referring to Clause 4.3.5.1 of 3GPP TS 23.502 v16.6.0, which is thus incorporated herein by reference in its entirety) or ULCL change (referring to Clause 4.3.5.7 of 3GPP TS 23.502 v16.6.0 which is thus incorporated herein by reference in its entirety) in 5GC, e.g., in order to obtain better user experience.
  • the first control plane entity may include a SGW-C entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include an SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity
  • the second user plane entity may include a PSA entity
  • the first mobility management entity is an MME
  • the second mobility management entity may include an AMF entity.
  • the first user plane entity may be any node that can be configured to perform the method 700 as described below, including a virtualized entity that may be implemented on cloud.
  • the method 700 at the first user plane entity at least partly corresponds to the method 400 at the first control plane entity.
  • some description of the method 700 may refer to that of method 400 as previously described, and thus will be omitted here for simplicity.
  • the first user plane entity may receive, from a first control plane entity, a second address, that is allocated to a ULCL function entity that is collocated with the first user plane entity, for the first user plane entity to transmit UL traffic to the ULCL function entity, wherein the second address was received by the first control plane entity from the ULCL function entity via the second control plane entity.
  • the second address may be an S5-U ULCL F-TEID that is received in a UL remote FAR in a PFCP Session Modification Request message from the first control plane entity.
  • the first user plane entity may transmit the UL traffic to the ULCL function entity.
  • the ULCL function entity may transmit DL traffic to the first user plane entity based on the first address it receives, as previously described.
  • the above process may be performed during the PDN connection establishment.
  • the method 700 may further include the following steps.
  • the first user plane entity which is used as a target first user plane entity in this exemplary implementation, may receive a second address from the first control plane entity, which is used as a target first control plane entity in this exemplary implementation.
  • the second address was allocated to the ULCL function entity, for the target first user plane entity to transmit UL traffic to the ULCL function entity. As previously described, the second address was received by the first control plane entity from the ULCL function entity via the second control plane entity.
  • the second address may be an S5-U ULCL F-TEID that is received in a UL remote FAR in a PFCP Session Establishment Request message from the first control plane entity.
  • the target first user plane entity may transmit a fifth address, that is allocated to the tar target first user plane entity, to the target first control plane entity, which is to be used for the ULCL function entity to transmit DL traffic to the target first user plane entity.
  • the fifth address may be transmitted by the target first user plane entity to the target first control plane entity, and forwarded by the target first control plane entity to the ULCL function entity via the second control plane entity.
  • the ULCL function entity may then switch, based on the received fifth address, the DL traffic to the target first user plane entity from the first user plane entity
  • the fifth address may be a Target S5/S8-U SGW F-TEID that is transmitted in a PFCP Session Establishment Response message to the target first control plane entity.
  • the traffic may be routed between the UE and the original edge Data Network (DN) via the target first user plane entity and the ULCL function entity after the SGW relocation, until PDN reactivation is triggered.
  • DN edge Data Network
  • the ULCL function entity may receive, from the second control plane entity, an indication of releasing a session between the ULCL function entity and the target first user plane entity; and then release the session between the ULCL function entity and the target first user plane entity.
  • the second control plane entity may then perform step S501 as previously described during PDN reactivation to perform the PDN connection reestablishment to insert another ULCL function entity, in particular, to insert another ULCL function entity collocated with another first user plane entity, e.g., in order to obtain better user experience.
  • the first user plane entity that is collocated with the newly inserted ULCL function entity may perform the method 700 as previously described.
  • the first control plane entity may include a SGW-C entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include a SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity.
  • the second user plane entity may be any node that can be configured to perform the method 800 as described below, including a virtualized entity that may be implemented on cloud.
  • the method 800 at the second user plane entity at least partly corresponds to the method 500 at the second control plane entity.
  • some description of the method 800 may refer to that of method 500 as previously described, and thus will be omitted here for simplicity.
  • the second user plane entity may transmit, to a second control plane entity, a third address allocated to the second user plane entity, which is to be used for a ULCL function entity to transmit UL traffic to the second user plane entity.
  • the second user plane entity may receive, from the second control plane entity, a fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the second control plane entity may support selection of a first user plane entity and a ULCL function entity that are collocated.
  • the above process may be performed during the PDN connection establishment.
  • the third address may be an N9 PSA F-TEID that is transmitted in a PFCP Session Establishment Response message
  • the fourth address may be an N9 ULCL F-TEID that is transmitted in a DL remote FAR in a PFCP Session Modification Request message.
  • the second user plane entity may include a PSA entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include a SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity.
  • an MME is shown as an example of the first mobility management entity
  • an SGW-C is shown as an example of the first control plane entity
  • a combined PGW-C and SMF is shown as an example of the second control plane entity and may be represented as (combined) PGW-C+SMF
  • an SGW-U is shown an example of the first user plane entity
  • a ULCL PSA1 is shown as an example of the ULCL function entity
  • a UPF (PSA0) is shown as an example of the second user plane entity.
  • the SGW-U and the ULCL PSA1 are collocated, which may be represented as (collocated) ULCL PSA1+SGW-U.
  • the SGW-C when detecting that the selected PGW-C+SMF can support the collocated user plane selection (based on system configuration) , the SGW-C skips SGW-U selection and sends a Create Session Request to the combined PGW-C+SMF, with its S5/S8-U SGW F-TEID set to a reserved Internal F-TEID which is used to indicate to the PGW-C+SMF that the collocated user plane shall be selected.
  • the reserved Internal F-TEID may take an unused IP address, such as 0.0.0.0, as an indication for the collocated user plane selection.
  • the Internal F-TEID may also be used by the SGW-U to receive DL traffic from the collocated user plane entity, see Note (S9_5) as well.
  • the combined PGW-C+SMF triggers PFCP session establishment towards the UPF (PSA0) to establish the PSA0 for the UE.
  • the UPF (PSA0) returns its allocated N9 F-TEID towards the combined PGW-C+SMF.
  • the combined PGW-C+SMF determines to insert a ULCL (PSA1) function, preferably based on at least one of the UE location and the service information.
  • the service information (such as DNAI, traffic forwarding rules) may be configured locally in the combined PGW-C+SMF or based on the PCC rules received from PCF, which may refer to step 5 in Figure 4.3.6.4-1 of 3GPP TS 23.502 v16.6.0, and 3GPP TS 23.502 v16.6.0 is incorporated herein by reference in its entirety.
  • the combined PGW-C+SMF triggers the establishment of ULCL PSA1 and sends a PFCP Session Establishment Request message with the UL remote FAR, the DL remote FAR, and the ULCL traffic forwarding rules (also called ULCL rules) , such as traffic filters, routing contexts to local DN (i.e., Edge DN) for edge breakout, e.g., N6 interface information.
  • ULCL traffic forwarding rules also called ULCL rules
  • the routing contexts may be used by the ULCL PSA1 to forward the UL traffic to the Edge DN via the N6 interface, as shown in FIG. 10.
  • the DL remote FAR (set to the Internal F-TEID, see the above Note (S9_3) indicates to the ULCL PSA1 to send the DL traffic to the internal tunnel end point of the collocated SGW-U.
  • the UL remote FAR (set to the PSA0 N9 F-TEID) is used by the ULCL PSA1 to send the UL traffic to the UPF (PSA0) .
  • the ULCL PSA1 sends towards the PGW-C+SMF its allocated S5-U ULCL F-TEID and N9 F-TEID in a PFCP Session Establishment Response message.
  • the S5-U ULCL F-TEID is used by the SGW-U to send UL traffic to the ULCL PSA1, and the N9 ULCL F-TEID will be used by the UPF (PSA0) to send DL traffic to the ULCL PSA1.
  • the combined PGW-C+SMF sends a PFCP Session Modification Request message towards the UPF (PSA0) with the DL remote FAR updated to the N9 ULCL F-TEID.
  • the combined PGW-C+SMF sends towards the SGW-C a Create Session Response message with the S5/S8-U PGW F-TEID IE which contains the value of the S5-U ULCL F-TEID.
  • the SGW-C may select the SGW-U collocated with the ULCL PSA1 and send a PFCP Session Establishment Request to the SGW-U with the UL remote FAR set to the S5-U ULCL F-TEID.
  • the ULCL logic is transparent to the SGW-C and SGW-U.
  • the SGW-C and SGW-U regards the ULCL PSA1 as a PGW-U.
  • the SGW-U returns its allocated S1-U SGW F-TEID in a PFCP Session Establishment Response towards the SGW-C.
  • the SGW-C sends a Create Session Response message to the MME with the S5/S8-U PGW F-TEID (containing the value of the S5-U ULCL F-TEID) and the S1-U SGW F-TEID.
  • the MME stores the received S5/S8-U PGW F-TEID (containing the value of the S5-U ULCL F-TEID) which will be used in the later SGW relocation scenarios (refer to FIG. 11A and FIG. 11B) .
  • the ULCL logic is transparent to the MME, i.e., the MME regards the ULCL PSA1 as the legacy PGW-U.
  • the collocated SGW-U and ULCL PSA1 are inserted in the data path of the PDN connection after the successful PDN connection establishment.
  • the ULCL function diverts the traffic in two ways based on the ULCL traffic forwarding rules. The traffic in one way is forwarded to the Central DN via the UPF PSA0, and the traffic in another way for edge computing is forwarded to the Edge DN via the N6 interface.
  • the traffic for edge computing from the Edge DN enters the ULCL PSA1 via the N6 interface and is forwarded to SGW-U via the S5-U interface, and the traffic from the Central DN is routed via the UPF PSA0 and forwarded to the ULCL PSA1 via the N9 interface, and then is further forwarded to the SGW-U via the S5-U interface.
  • the S1-U tunnel between the eNB and the SGW-U There is no change for the S1-U tunnel between the eNB and the SGW-U.
  • the ULCL function entity e.g., ULCL PSA1
  • the first user plane entity e.g., SGW-U
  • SGW relocation e.g., Type 1 and Type 2, which are respectively shown in FIGS. 11A and 11B
  • HO from EPS to 5GS shown in FIG. 13
  • FIGS. 11A and 11B exemplary signaling sequence diagrams of ULCL changing after SGW relocation Type 1 and Type 2 will be described respectively with reference to FIGS. 11A and 11B, in which the methods 400 ⁇ 800 at various entities according to the first exemplary embodiment of the present disclosure are applied.
  • an MME is shown as an example of the first mobility management entity
  • a Target SGW-C is shown as an example of the target first control plane entity
  • a Source SGW-C is shown as an example of the source first control plane entity
  • a combined PGW-C and SMF is shown as an example of the second control plane entity and may be represented as (combined) PGW-C+SMF
  • a Target SGW-U is shown an example of the target first user plane entity
  • a Source SGW-U is shown an example of the source first user plane entity
  • a ULCL PSA1 is shown as an example of the ULCL function entity
  • a UPF (PSA0) is shown as an example of the second user plane entity.
  • the source SGW-U and the ULCL PSA1 are collocated, which may be represented as (collocated) ULCL PSA1+Source SGW-U.
  • the exemplary signaling sequence diagram of FIG. 11A is applied to the SGW relocation Type 1 scenario, details of which follows the procedure as per Clause 5.5.1.1.3 of 3GPP TS 23.401 v16.8.0, which is thus incorporated herein by reference in its entirety.
  • FIG. 11A modification on the signaling related to the methods 400 ⁇ 800 is shown in Bold Italics, in which e.g., Signaling S11A_1, S11A_2, S11A_5, S11A_6, S11A_18, and PDN connection reestablishment related signaling (referring to S9_3, S9_5 ⁇ S9_10 and S9_12 in FIG. 9) .
  • the MME sends a Create Session Request message (with the S5/S8-U PGW F-TEID set to S5/S8-U ULCL F-TEID, referring to S9_12 of FIG. 9) to the Target SGW-C.
  • the MME receives and stores the S5/S8-U PGW F-TEID at ULCL insertion in S9_12 of FIG. 9 as described above.
  • the Target SGW-C sends a PFCP Session Establishment Request to the Target SGW-U, and sets the UL remote FAR to the S5/S8-U PGW F-TEID (set to S5/S8-U ULCL F-TEID) received from the MME.
  • the S5/S8-U PGW F-TEID takes the value of the S5/S8-U ULCL F-TEID (referring to S9_4 of FIG. 9 as described above) .
  • the target SGW-U can send UL traffic to the ULCL PSA1 using the UL remote FAR (i.e., S5/S8-U ULCL F-TEID) .
  • the Target SGW-U returns its allocated Target S1-U SGW F-TEID and Target S5/S8-U SGW F-TEID to the Target SGW-C.
  • Target SGW-C sends a Modify Bearer Request (MBReq) message with the Target S5/S8-U SGW F-TEID to the combined PGW-C+SMF.
  • MReq Modify Bearer Request
  • the combined PGW-C+SMF updates the DL remote FAR of the ULCL PSA1 with the Target S5/S8-U SGW F-TEID. Then, the ULCL PSA1 can send DL traffic to the Target SGW-U using the DL remote FAR (i.e., Target S5/S8-U SGW F-TEID) .
  • the combined PGW-C+SMF replies a Modify Bearer Response (MBResp) message to the Target SGW-C.
  • MResp Modify Bearer Response
  • S11A_8 ⁇ S11A_11 the SGW relocation continues as the existing EPC procedure.
  • the edge application traffic is routed between UE and the original edge DN via the Target SGW-U and the ULCL PSA1 as shown in FIG. 12, until PDN reactivation is triggered.
  • the combined PGW-C+SMF determines to trigger PDN reactivation (including PDN connection release and PDN connection reestablishment) based on e.g., UE location and/or service information. For example, if there is edge application server deployed in the current location of the UE, the PGW-C+SMF may trigger the PDN reactivation either immediately or after a delay timer expiry.
  • the combined PGW-C+SMF sends a Delete Bearer Request message to the Target SGW-C to request PDN reactivation.
  • the Target SGW-C sends a Delete Bearer Request message to the MME.
  • the MME triggers a PDN reactivation towards the UE.
  • the MME sends a Delete Bearer Response message to the Target SGW-C.
  • Target SGW-C triggers PFCP session deletion towards the Target SGW-U.
  • Target SGW-C sends a Delete Bearer Response message to the combined PGW-C+SMF.
  • the combined PGW-C+SMF triggers PFCP session deletion towards the ULCL PSA1 by sending, to the ULCL PSA1, an indication of releasing the session between the ULCL PSA1 and the Target SGW-U, and the ULCL PSA1 releases the session accordingly.
  • the combined PGW-C+SMF also triggers PFCP session deletion towards the UPF (PSA0) .
  • a new collocated SGW-U and ULCL may be established in the target site according to the signaling flows in FIG. 9 as previously described to perform the PDN connection reestablishment.
  • the UE After the PDN reactivation, the UE will automatically do a new Domain Name System (DNS) query and connect to the new edge application server located in the edge DN close to the target site. That is, a better user experience than that via the original ULCL PSA1 may be obtained.
  • DNS Domain Name System
  • the SGW-U of the new collocated SGW-U and ULCL may be the former Target SGW-U or some other suitable SGW-U.
  • the setup of Target SGW-U and ULCL PSA1 shown in FIG. 12 is released and replaced with the collocated SGW-U and ULCL PSA1 shown in FIG. 10.
  • the exemplary signaling sequence diagram of FIG. 11B is applied to the SGW relocation Type 2 scenario, details of which follows the procedure as per Clause 5.5.1.2.2 of 3GPP TS 23.401 v16.8.0 (which is thus incorporated herein by reference in its entirety) and the similar logic as the SGW relocation Type 1 scenario as previously described with reference to FIG. 11A.
  • FIG. 11B modification on the signaling related to the methods 400 ⁇ 800 is shown in Bold Italics, in which e.g., Signaling S11B_1, S11 B_2, S11 B_9, S11B_10, signaling related to deleting the session between ULCL PSA1 and Target SGW-U (referring to S11A_18 in FIG. 11A) , and PDN connection reestablishment related signaling (referring to S9_3, S9_5 ⁇ S9_10 and S9_12 in FIG. 9) .
  • Signaling S11B_1, S11 B_2, S11 B_9, S11B_10 signaling related to deleting the session between ULCL PSA1 and Target SGW-U
  • PDN connection reestablishment related signaling referring to S9_3, S9_5 ⁇ S9_10 and S9_12 in FIG. 9 .
  • S11B_1 ⁇ S11B_3 are identical with those of S11A_1 ⁇ S11A_3, description of which is thus omitted herein for simplicity.
  • the Target SGW-C sends a Create Session Response message (with the S1-U SGW F-TEID for the Target SGW-U) to the MME as the existing EPC standard.
  • the MME sends a Modify Bearer Request message to the Target SGW-C with the S1-U eNB F-TEID.
  • the S1-U eNB F-TEID is only available after S11B_5 for SGW relocation Type 2 (referring to Clause 5.5.1.2.2 of 3GPP TS 23.401 v16.8.0) . That is the difference from SGW relocation Type 1.
  • the Target SGW-C triggers PFCP modification with the S1-U eNB F-TEID towards the Target SGW-U, then the Target SGW-U switches the DL traffic towards the eNB on the target side.
  • S11B_8 ⁇ S11B_11 the same procedure as S11A_4 ⁇ S11A_7 related to SGW relocation Type 1 is performed for the ULCL PSA1 to switch the DL traffic to the Target SGW-U.
  • Target SGW-C replies a Modify Bearer Response to the MME as the existing EPC standard.
  • S11B_13 ⁇ S11B_15 the same procedure as S11A_9 ⁇ S11A_11 related to SGW relocation Type 1 is performed to delete the resource on the source SGW-C and SGW-U.
  • the mobility is executed as the legacy EPC procedure (i.e., the ULCL PSA1 is treated as the PGW-U by MME and SGW-C) .
  • the ULCL PSA is kept during the mobility procedure.
  • the PDN reactivation may be triggered by the combined PGW-C+SMF after the mobility procedure is completed.
  • the reactivation may not be triggered for each mobility procedure as long as the latency is acceptable between the target site and the ULCL PSA1.
  • the original ULCL PSA is removed together with the PDN connection release (triggered due to PDN reactivation) , then during the PDN connection re-establishment, a new ULCL PSA can be inserted in the target site as described previously with reference to FIG. 9.
  • an MME is shown as an example of the first mobility management entity
  • an AMF is shown as an example of the second mobility management entity
  • an SGW-C is shown as an example of the first control plane entity
  • a combined PGW-C and SMF is shown as an example of the second control plane entity and may be represented as (combined) PGW-C+SMF
  • an SGW-U is shown an example of the first user plane entity
  • a ULCL PSA1 is shown as an example of the ULCL function entity
  • a UPF (PSA0) is shown as an example of the second user plane entity.
  • the SGW-U and the ULCL PSA1 are collocated, which may be represented as (collocated) ULCL PSA1+SGW-U.
  • the exemplary signaling sequence diagram of FIG. 13 is applied to the HO from EPS to 5GS scenario, details of which follows the procedure as per Clause 4.11.1.2.2 of 3GPP TS23.502 v16.6.0 (which is thus incorporated herein by reference in its entirety) and the following deviation:
  • the combined PGW-C+SMF triggers a PFCP Session Modification Request message to the ULCL PSA1.
  • the ULCL PSA1 returns the allocated N3 tunnel information (e.g., N3 ULCL F-TEID) in the PDCP Session Modification Response message to the combined PGW-C+SMF.
  • the combined PGW-C+SMF receives the NG-RAN N3 Tunnel information (e.g., N3 NG-RAN F-TEID) from the AMF, then triggers PFCP session modification to update the ULCL PSA1 with the NG-RAN N3 tunnel information (e.g., N3 NG-RAN F-TEID) .
  • the NG-RAN N3 Tunnel information e.g., N3 NG-RAN F-TEID
  • the combined PGW-C+SMF when the combined PGW-C+SMF receives the HO Complete Indication from the AMF, the combined PGW-C+SMF triggers PFCP session modification to the ULCL PSA1 which switches the DL traffic to the NG-RAN.
  • the combined PGW-C+SMF determines to change the UPF anchor either by the PDU session reactivation (referring to Clause 4.3.5.1 of 3GPP TS 23.502 v16.6.0, which is thus incorporated herein by reference in its entirety) or ULCL change (referring to Clause 4.3.5.7 of 3GPP TS 23.502 v16.6.0 which is thus incorporated herein by reference in its entirety) in 5GC.
  • the ULCL function is released at the HO from 5GS to EPS, and the edge service through the ULCL is discontinued immediately.
  • the ULCL function may be kept in the data path at the HO from 5GS to EPS, so that the edge service through the ULCL can be continued until PDN reactivation is triggered.
  • the second control plane entity may be any node that can be configured to perform the method 1400 as described below, including a virtualized entity that may be implemented on cloud..
  • the method 1400 may be performed in a case where handover from a 5GS to an EPS is required.
  • the second control plane entity that supports selection of a first user plane entity and a ULCL function entity may trigger first session modification to a ULCL function entity in step S1401, so as to establish a user plane tunnel for each EPS bearer.
  • the second control plane entity may receive, from the ULCL function entity, a second address and a fourth address allocated to the ULCL function entity, wherein the second address may be used for the first user plane entity to transmit UL traffic to the ULCL function entity, and the fourth address may be used for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the second address may be an S5-U ULCL F-TEID that is transmitted in a PFCP Session Modification Response message from the ULCL function entity
  • the fourth address may be a N9 ULCL F-TEID that is transmitted in the PFCP Session Modification Response message from the ULCL function entity.
  • the second control plane entity may also trigger second session modification to a second user plane entity.
  • the second control plane entity may receive, from the second user plane entity, a third address, that is allocated to the second user plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity.
  • the third address may be an N9 PSA F-TEID that is received in a PFCP Session Modification Response message from the second user plane entity.
  • the second control plane entity may transmit the received second address to a mobility management entity.
  • the second control plane entity may receive, from the first control plane entity, an eighth address that is allocated to the first user plane entity.
  • the eighth address may be an S5/S8-U SGW F-TEID that is transmitted in a PFCP Session Modification Request message to the ULCL function entity.
  • the second control plane entity may transmit, to the ULCL function entity, the received eighth address for the ULCL function entity to transmit DL traffic to the first user plane entity and the received third address for the ULCL function entity to transmit UL traffic to the second user plane entity.
  • the third address may be an N9 PSA F-TEID that is transmitted in a PFCP Session Modification Request message to the ULCL function entity
  • the eighth address is an S5/S8-U SGW F-TEID that is transmitted in the PFCP Session Modification Request message to the ULCL function entity.
  • the second control plane entity may transmit, to the second user plane entity, the received fourth address for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the fourth address may be the N9 ULCL F-TEID that is transmitted in a PFCP Session Modification Request message to the second user plane entity.
  • the second control plane entity may transmit, to the ULCL function entity, an indication of releasing the session between the ULCL function entity and the first user plane entity.
  • the second control plane entity may then perform step S501 as previously described during PDN reactivation to perform the PDN connection reestablishment to insert another ULCL function entity, in particular, to insert another ULCL function entity collocated with another first user plane entity, e.g., in order to obtain better user experience.
  • the mobility management entity may include an AMF entity
  • the first control plane entity may include a SGW-C entity
  • the second control plane entity may include a combined PGW-C and SMF entity
  • the first user plane entity may include a SGW-U entity
  • the ULCL function entity may include a ULCL PSA entity
  • the second user plane entity may include a PSA entity.
  • the ULCL function entity may be any node that can be configured to perform the method 1500 as described below, including a virtualized entity that may be implemented on cloud.
  • the method 1500 at the ULCL function entity at least partly corresponds to the method 1400 at the second control plane entity.
  • some description of the method 1500 may refer to that of method 1400 as previously described, and thus will be omitted here for simplicity.
  • the method 1500 may be performed in a case where handover from a 5GS to an EPS is required.
  • the ULCL function entity may receive, from a second control plane entity, a trigger of first session modification for the ULCL function entity.
  • the ULCL function entity may transmit, to the second control plane entity, a second address and a fourth address allocated to the ULCL function entity.
  • the second address may be used for the first user plane entity to transmit UL traffic to the ULCL function entity
  • the fourth address may be used for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the second address may be an S5-U ULCL F-TEID that is transmitted in a PFCP Session Modification Response message to the second control plane entity
  • the fourth address may be an N9 ULCL F-TEID that is transmitted in the PFCP Session Modification Response message to the second control plane entity.
  • the ULCL function entity may receive a third address and an eighth address from the second control plane entity.
  • the third address may be allocated to the second user plane entity, and forwarded from the second user plane entity by the second control plane entity for the ULCL function entity to transmit UL traffic to the second user plane entity.
  • the eighth address may be allocated to the first user plane entity, and forwarded from the first control plane entity by the second control plane entity for the ULCL function entity to transmit UL traffic to the first user plane entity.
  • the third address may be an N9 PSA F-TEID that is received in a PFCP Session Modification Request message from the second control plane entity
  • the eighth address may be an S5/S8-U SGW F-TEID that is received in the PFCP Session Modification Request message from the second control plane entity.
  • the ULCL function entity may receive, from the second control plane entity, an indication of releasing a session between the ULCL function entity and the target first user plane entity; and then release the session between the ULCL function entity and the target first user plane entity.
  • the second control plane entity may then perform step S501 as previously described during PDN reactivation to perform the PDN connection reestablishment to insert another ULCL function entity, in particular, to insert another ULCL function entity collocated with another first user plane entity, e.g., in order to obtain better user experience. Accordingly, the newly inserted ULCL function entity may perform the method 600 as previously described.
  • the second user plane entity may be any node that can be configured to perform the method 1600 as described below, including a virtualized entity that may be implemented on cloud.
  • the method 1600 at the second user plane entity at least partly corresponds to the method 1400 at the second control plane entity.
  • some description of the method 1600 may refer to that of method 1400 as previously described, and thus will be omitted here for simplicity.
  • the method 1600 may be performed in a case where handover from a 5GS to an EPS is required.
  • the second user plane entity may transmit, to a second control plane entity, a third address allocated to the second user plane entity, which is to be used for a ULCL function entity to transmit UL traffic to the second user plane entity.
  • the second user plane entity may receive, from the second control plane entity, a fourth address, that is allocated to the ULCL function entity and forwarded from the ULCL function entity by the second control plane entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the third address may be an N9 PSA F-TEID that is transmitted in a PFCP Session Modification Response message to the second control plane entity.
  • the fourth address may be an N9 ULCL F-TEID that is received in a PFCP Session Modification Request message from the second control plane entity.
  • the second user plane entity includes a PSA entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the ULCL function entity includes a ULCL PSA entity
  • FIG. 17 exemplary signaling sequence diagram of ULCL changing after HO from 5GS to EPS will be described with reference to FIG. 17, in which the methods 400 ⁇ 800 at various entities according to the first exemplary embodiment of the present disclosure are applied.
  • an AMF is shown as an example of the mobility management entity
  • an SGW-C is shown as an example of the first control plane entity
  • a combined PGW-C and SMF is shown as an example of the second control plane entity and may be represented as (combined) PGW-C+SMF
  • an SGW-U is shown an example of the first user plane entity
  • a ULCL PSA1 is shown as an example of the ULCL function entity
  • a UPF (PSA0) is shown as an example of the second user plane entity.
  • the ULCL PSA1 is not required to be collocated with the SGW-U. After the HO from 5GS to EPS is completed, the SGW-U and the ULCL PSA1 are collocated during the PDN connection reestablishment.
  • the exemplary signaling sequence diagram of FIG. 17 is applied to the HO from 5GS to EPS scenario, details of which follows the procedure as per Clause 4.11.1.2.1 of 3GPP TS23.502 v16.6.0 (which is thus incorporated herein by reference in its entirety) and the following deviation:
  • the combined PGW-C+SMF triggers PFCP session modification to the ULCL PSA1 to establish the user plane tunnel for each EPS bearer.
  • the ULCL PSA1 need establish both S5-U and N9 tunnels for each EPS bearer.
  • the S5-U tunnel is used to receive the UL traffic from the SGW-U
  • the N9 tunnel is used to receive the DL traffic from the UPF (PSA0) .
  • the ULCL PSA1 returns the established user plane tunnel (both S5-U and N9) information (e.g., S5-U ULCL F-TEID and N9 ULCL F-TEID) to the combined PGW-C+SMF.
  • the combined PGW-C+SMF only sends PFCP session modification to UPF (PSA0) to establish the user plane tunnel for each EPS bearer.
  • the combined PGW-C+SMF triggers PFCP session modification to the UPF (PSA0) to establish the N9 user plane tunnel for each EPS bearer.
  • the UPF (PSA0) returns the established N9 tunnel information (e.g., N9 PSA0 F-TEID) to the combined PGW-C+SMF.
  • the combined PGW-C+SMF returns to the AMF with the EPS bearer contexts (e.g., S5-U ULCL F-TEID) corresponding to the S5-U tunnel (s) established by the ULCL PSA1.
  • the EPS bearer contexts e.g., S5-U ULCL F-TEID
  • the combined PGW-C+SMF returns to the AMF with the EPS bearer contexts corresponding to the user plane tunnel (s) established by UPF (PSA0) .
  • the combined SMF+PGW sends PFCP session modification to the ULCL PSA1 with the S5/S8-U SGW F-TEID and the N9 PSA0 F-TEID (corresponding to the tunnel established by the UPF (PSA0) at S17_4) , the ULCL PSA1 switches the DL traffic to the SGW-U, and switches the UL traffic to the UPF PSA0.
  • the combined SMF+PGW sends PFCP session modification to the UPF (PSA0) with the N9 ULCL F-TEID (corresponding to the tunnel established by ULCL PSA1 at S17_3) and the UPF (PSA0) switches the DL traffic to the ULCL PSA1.
  • the combined PGW-C+SMF determines to trigger PDN connection reactivation (including PDN connection release and PDN connection reestablishment) based on the UE location and/or the service information as per S11A_12 ⁇ S11A_19 as previously described with reference to FIG. 11A, description of which is thus omitted herein for simplicity.
  • FIG. 18 An exemplary traffic flow between SGW-U and ULCL PSA1 after the HO from 5GS to EPS before PDN reactivation according to the second exemplary embodiment of the present disclosure is shown in FIG. 18.
  • FIG. 19 schematically shows a block diagram of the first control plane entity 1900 according to the first exemplary embodiment of the present disclosure.
  • the first control plane entity 1900 in FIG. 19 may perform the method 400 as described previously with reference to FIG. 4. Accordingly, some detailed description on the first control plane entity 2000 may refer to the corresponding description of the method 400 in FIG. 4 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the first control plane entity 1900 may include a determination unit 1901 and a transmitting unit 1903.
  • the determination unit 1901 may determine that a second control plane entity selected by the first control plane entity supports selection of a first user plane entity and a ULCL function entity.
  • the transmitting unit 1903 may transmit, to the second control plane entity, an indication of selecting a first user plane entity and a ULCL function entity.
  • the indication may include a first address, that is to be allocated to a first user plane entity, for a ULCL function entity to transmit DL traffic to the first user plane entity.
  • the first control plane entity 1900 may further include a receiving unit (not shown) , which may be configured to receive, from the second control plane entity, a second address, that is allocated to a ULCL function entity and transmitted by the ULCL function entity to the second control plane entity, for a first user plane entity to transmit UL traffic to the ULCL function entity.
  • a receiving unit not shown
  • the first control plane entity 1900 may further include a selection unit (not shown) , which may be configured to select, based on the received second address, the first user plane entity; and transmitting the second address to the first user plane entity for the first user plane entity to transmit the UL traffic to the ULCL function entity.
  • a selection unit not shown
  • the transmitting unit 1903 may further be configured to transmit the second address to a first mobility management entity.
  • the first user plane entity and the ULCL function entity are collocated.
  • the indication is transmitted in a Create Session Request message
  • the first address is an Internal F-TEID that is transmitted in an S5/S8-U SGW F-TEID IE in the Create Session Request message.
  • the second address is an S5-U ULCL F-TEID that is received in an S5/S8-U PGW F-TEID IE in a Create Session Response message from the second control plane entity, transmitted in an S5/S8-U PGW F-TEID IE in a Create Session Response message to the mobility management entity, and transmitted in a UL remote FAR in a PFCP Session Establishment Request message to the first user plane entity.
  • FIG. 20 schematically shows a block diagram of the first control plane entity 2000 according to the first exemplary embodiment of the present disclosure.
  • the first control plane entity 2000 in FIG. 20 may perform the method 400 as described previously with reference to FIG. 4. Accordingly, some detailed description on the first control plane entity 2000 may refer to the corresponding description of the method 400 in FIG. 4 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the first control plane entity 2000 includes at least one processor 2001 and at least one memory 2003.
  • the at least one processor 2001 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 2003 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 2003 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 2003 stores instructions executable by the at least one processor 2001.
  • the instructions when loaded from the at least one memory 2003 and executed on the at least one processor 2001, may cause the first control plane entity 2000 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 4 with reference to the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • FIG. 21 schematically shows a block diagram of the second control plane entity 2100 according to the first exemplary embodiment of the present disclosure.
  • the second control plane entity 2100 in FIG. 21 may perform the method 500 as described previously with reference to FIG. 5. Accordingly, some detailed description on the second control plane entity 2200 may refer to the corresponding description of the method 500 in FIG. 5 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the second control plane entity supports selection of a first user plane entity and a ULCL function entity.
  • the second control plane entity 2100 may include an insertion unit 2101, which may be configured to perform a process of inserting a ULCL function entity during a connection establishment.
  • the insertion unit 2101 may include: a determination unit (not shown) and a session establishment unit (not shown) .
  • the determination unit may be configured to determine to insert a ULCL function entity.
  • the session establishment unit may be configured to perform session establishment with the ULCL function entity.
  • the ULCL function entity is determined to be inserted based on at least one of: a location of a UE or service information related to the ULCL function entity.
  • the service information includes at least one of: a DNAI, or a traffic forwarding rule for the ULCL function entity.
  • the traffic forwarding rule for the ULCL function entity includes routing contexts to local DN for edge breakout by the ULCL function entity.
  • the insertion unit 2101 may further include a receiving unit (not shown) , which may be configured to receive, from a first control plane entity, an indication of selecting a first user plane entity and a ULCL function entity.
  • a receiving unit (not shown) , which may be configured to receive, from a first control plane entity, an indication of selecting a first user plane entity and a ULCL function entity.
  • the indication includes a first address, that is to be allocated to the first user plane entity, for the ULCL function entity to transmit Downlink (DL) traffic to the first user plane entity.
  • DL Downlink
  • the insertion unit may further include a trigger unit (not shown) , which may be configured to trigger session establishment to a second user plane entity.
  • the receiving unit may be further configured to receive, from the second user plane entity, a third address, that is allocated to the second user plane entity.
  • the inserting unit 2101 may further include a transmitting unit (not shown) , which may be configured to transmit, to the ULCL function entity, a session establishment request message, and receive, from the ULCL function entity, a session establishment response message,
  • a transmitting unit (not shown) , which may be configured to transmit, to the ULCL function entity, a session establishment request message, and receive, from the ULCL function entity, a session establishment response message,
  • the session establishment request message may include: the first address, that is received from the first control plane entity, for the ULCL function entity to transmit DL traffic to the first user plane entity; the third address, that is received from the second user plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity; and the traffic forwarding rule for the ULCL function entity,
  • the session establishment response message may include: a second address, that is allocated to the ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity; and a fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the session establishment unit may be further configured to transmit, to the second user plane entity, the received fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the session establishment unit may be further configured to transmit, to the first control plane entity, the received second address that is allocated to the ULCL function entity.
  • the first user plane entity and the ULCL function entity are collocated.
  • the first control plane entity includes an SGW-C entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the first user plane entity includes an SGW-U entity
  • the ULCL function entity includes a ULCL PSA entity
  • the second user plane entity includes a PSA entity.
  • the indication is received in a Create Session Request message
  • the first address is an Internal F-TEID that is received in an S5/S8-U SGW F-TEID IE of the Create Session Request message.
  • the transmitted session establishment request message includes a PFCP Session Establishment Request message, which includes: a UL remote FAR that is set to an N9 PSA F-TEID as the third address, a DL remote FAR that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • the received session establishment response message includes a PFCP Session Establishment Response message, which includes: an S5-U ULCL F-TEID as the second address, and an N9 ULCL F-TEID as the fourth address.
  • the fourth address is an N9 ULCL F-TEID that is transmitted in a DL remote FAR in a PFCP Session Modification Request message.
  • the second address is an S5-U ULCL F-TEID that is transmitted in an S5/S8-U PGW F-TEID IE in a Create Session Response message.
  • the receiving unit may be further configured to receive, from another first control plane entity, as a target first control plane entity, a fifth address that is allocated to another first user plane entity, as a target first user plane entity, and transmitted by the target first user plane entity to the target first control plane entity; and transmitting the fifth address to the ULCL function entity for the ULCL function entity to establish a session with the target first user plane entity to switch the DL traffic to the target first user plane entity from the first user plane entity as a source first user plane entity.
  • the fifth address is received in a case where the target first control plane entity receives the second address from a first mobility management entity, and transmits the second address to the target first user plane entity, wherein the second address was received by the first mobility management entity from the second control plane entity via the source first control plane entity.
  • the transmitting unit may be further configured to transmit, to the ULCL function entity, an indication of releasing a session between the ULCL function entity and the target first user plane entity.
  • the insertion unit 2101 may be further configured to re-perform the process of inserting a ULCL function entity for a new connection establishment to establish another ULCL function entity.
  • the fifth address is a Target S5/S8-U SGW F-TEID that is received in a Modify Bearer Request message, and is transmitted in a DL remote FAR of a PFCP Session Modification Request message.
  • the transmitting unit may be further configured to: transmit, to the ULCL function entity, a session modification request message.
  • the receiving unit may be further configured to receive, from the ULCL function entity, a session modification response message, which includes a sixth address that is allocated to the ULCL function entity for an access node to transmit UL traffic to the ULCL function entity.
  • the session modification request message is transmitted in a case where handover from an EPS to a 5GS is required.
  • the receiving unit may be further configured to receive, from a second mobility management entity, a seventh address that is allocated to the access node.
  • the transmitting unit may be further configured to transmit the received seventh address to the ULCL function entity for the ULCL function entity to transmit DL traffic to the access node.
  • the receiving unit may be further configured to receive a handover complete indication from the second mobility management entity.
  • the trigger unit may be further configured to trigger session modification to the ULCL function entity for the ULCL function entity to switch the DL traffic to the access node based on the received seventh address.
  • the insertion unit 2101 may be further configured to re-perform the process of inserting a ULCL function entity for a new connection establishment to establish another ULCL function entity.
  • the transmitted session modification request message includes a PFCP Session Modification Request message
  • the received session modification response message includes a PFCP Session Modification Response message, which includes an N3 ULCL F-TEID as the sixth address.
  • the seventh address is an N3 NG-RAN F-TEID that is received in an Nsmf_PDU Session_Update_SM Context Request message, and is transmitted in a PFCP Session Modification Request message.
  • FIG. 22 schematically shows a block diagram of the second control plane entity 2200 according to the first exemplary embodiment of the present disclosure.
  • the second control plane entity 2200 in FIG. 22 may perform the method 500 as described previously with reference to FIG. 5. Accordingly, some detailed description on the second control plane entity 2200 may refer to the corresponding description of the method 500 in FIG. 5 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the second control plane entity 2200 includes at least one processor 2201 and at least one memory 2203.
  • the at least one processor 2201 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 2203 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 2203 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 2203 stores instructions executable by the at least one processor 2201.
  • the instructions when loaded from the at least one memory 2203 and executed on the at least one processor 2201, may cause the first control plane entity 2200 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 5 with reference to the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • FIG. 23 schematically shows a block diagram of the ULCL function entity 2300 according to the first exemplary embodiment of the present disclosure.
  • the ULCL function entity 2300 in FIG. 23 may perform the method 500 as described previously with reference to FIG. 6. Accordingly, some detailed description on the ULCL function entity 2300 may refer to the corresponding description of the method 600 in FIG. 6 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the ULCL function entity 2300 may include a receiving unit 2301 and a transmitting unit 2303.
  • the receiving unit 2301 may be configured to receive a session establishment request message from a second control plane entity that supports selection of a first user plane entity and a ULCL function entity.
  • the transmitting unit 2303 may be configured to transmit, to the second control plane entity, a session establishment response message.
  • the session establishment request message includes: a first address, that is to be allocated by a first control plane entity to the first user plane entity, and is received from the first control plane entity via the second control plane entity, for the ULCL function entity to transmit DL traffic to the first user plane entity; a third address, that is allocated to the second user plane entity, and is received from the second user plane entity via the second control plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity; and a traffic forwarding rule for the ULCL function entity; and the session establishment response message includes: a second address, that is allocated to the ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity; and a fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the traffic forwarding rule for the ULCL function entity includes routing contexts to local DN for edge breakout by the ULCL function entity.
  • the ULCL function entity is collocated with the first user plane entity.
  • the received session establishment request message includes a PFCP Session Establishment Request message, which includes: a UL remote FAR IE that is set to an N9 PSA F-TEID as the third address, a DL remote FAR IE that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • PFCP Session Establishment Request message which includes: a UL remote FAR IE that is set to an N9 PSA F-TEID as the third address, a DL remote FAR IE that is set to the Internal F-TEID as the first address, and the traffic forwarding rule for the ULCL function entity.
  • the transmitted session establishment response message includes a PFCP Session Establishment Response message, which includes: an S5-U ULCL F-TEID as the second address, and a N9 ULCL F-TEID as the fourth address.
  • the receiving unit 2301 may be further configured to receive, from the second control plane entity, a fifth address, that is allocated to another first user plane entity, as a target first user plane entity, for the ULCL function entity to switch the DL traffic to the target first user plane entity from the first user plane entity as a source first user plane entity, wherein the fifth address was received by the target first control plane entity from the target first user plane entity and transmitted to the second control plane entity.
  • the fifth address is received in a case where the target first control plane entity receives the second address from a first mobility management entity, and transmits the second address to the target first user plane entity, wherein the second address was received by the first mobility management entity from the second control plane entity via the source first control plane entity.
  • the receiving unit 2301 may be further configured to receive, from the second control plane entity, an indication of releasing a session between the ULCL function entity and the target first user plane entity.
  • the ULCL function entity may further include a releasing unit (not shown) , which may be configured to release the session between the ULCL function entity and the target first user plane entity.
  • a releasing unit (not shown) , which may be configured to release the session between the ULCL function entity and the target first user plane entity.
  • the fifth address is a Target S5/S8-U SGW F-TEID that is received in a DL remote FAR of a PFCP Session Modification Request message.
  • the receiving unit 2301 may be further configured to receive a session modification request message from the second control plane entity.
  • the transmitting unit 2303 may be further configured to transmit, to the second control plane entity, a session modification response message, which includes a sixth address that is allocated to the ULCL function entity for an access node to transmit UL traffic to the ULCL function entity.
  • the session modification request message is received in a case where handover from an EPS to a 5GS is required.
  • the receiving unit 2301 may be further configured to receive, from the second control plane entity, a seventh address, that is allocated to the access node and transmitted to the second control plane entity from a second mobility management entity, for the ULCL function entity to transmit DL traffic to the access node.
  • the transmitting unit 2303 may be further configured to: switching the DL traffic to the access node based on the received seventh address, in a case where a handover complete indication is received by the second control plane entity from the second mobility management entity.
  • the received session modification request message includes a PFCP Session Modification Request message
  • the transmitted session modification response message includes a PFCP Session Modification Response message, which includes an N3 ULCL F-TEID as the sixth address.
  • the seventh address is an N3 NG-RAN F-TEID that is received in a PFCP Session Modification Request message.
  • FIG. 24 schematically shows a block diagram of the ULCL function entity 2400 according to the first exemplary embodiment of the present disclosure.
  • the ULCL function entity 2400 in FIG. 24 may perform the method 600 as described previously with reference to FIG. 6. Accordingly, some detailed description on the ULCL function entity 2400 may refer to the corresponding description of the method 600 in FIG. 6 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the ULCL function entity 2400 includes at least one processor 2401 and at least one memory 2403.
  • the at least one processor 2401 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 2403 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 2403 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 2403 stores instructions executable by the at least one processor 2401.
  • the instructions when loaded from the at least one memory 2403 and executed on the at least one processor 2401, may cause the first control plane entity 2400 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 6 with reference to the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • FIG. 25 schematically shows a block diagram of the first user plane entity 2500 according to the first exemplary embodiment of the present disclosure.
  • the first user plane entity 2500 in FIG. 25 may perform the method 700 as described previously with reference to FIG. 7. Accordingly, some detailed description on the first user plane entity 2500 may refer to the corresponding description of the method 700 in FIG. 7 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the first user plane entity 2500 may include a receiving unit 2501, which may be configured to receive, from a first control plane entity, a second address, that is allocated to a ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity, wherein the second address was received by the first control plane entity from the ULCL function entity via the second control plane entity.
  • a receiving unit 2501 may be configured to receive, from a first control plane entity, a second address, that is allocated to a ULCL function entity, for the first user plane entity to transmit UL traffic to the ULCL function entity, wherein the second address was received by the first control plane entity from the ULCL function entity via the second control plane entity.
  • the second address is an S5-U ULCL F-TEID that is received in a UL remote FAR in a PFCP Session Modification Request message from the first control plane entity.
  • the first control plane entity includes a SGW-C entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the first user plane entity includes a SGW-U entity
  • the ULCL function entity includes a ULCL PSA entity.
  • FIG. 26 schematically shows a block diagram of the first user plane entity 2600 according to the first exemplary embodiment of the present disclosure.
  • the first user plane entity 2600 in FIG. 26 may perform the method 700 as described previously with reference to FIG. 7. Accordingly, some detailed description on the first user plane entity 2600 may refer to the corresponding description of the method 700 in FIG. 7 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the first user plane entity 2600 includes at least one processor 2601 and at least one memory 2603.
  • the at least one processor 2601 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 2603 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 2603 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 2603 stores instructions executable by the at least one processor 2601.
  • the instructions when loaded from the at least one memory 2603 and executed on the at least one processor 2601, may cause the first control plane entity 2600 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 7 with reference to the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • FIG. 27 schematically shows a block diagram of the second user plane entity 2700 according to the first exemplary embodiment of the present disclosure.
  • the second user plane entity 2700 in FIG. 27 may perform the method 800 as described previously with reference to FIG. 8. Accordingly, some detailed description on the second user plane entity 2700 may refer to the corresponding description of the method 800 in FIG. 8 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the second user plane entity 2700 may include a transmitting unit 2701 and a receiving unit 2703.
  • the transmitting unit 2701 may be configured to transmit, to a second control plane entity, a third address allocated to the second user plane entity, which is to be used for a ULCL function entity to transmit UL traffic to the second user plane entity.
  • the receiving unit 2703 may be configured to receive, from the second control plane entity, a fourth address, that is allocated to the ULCL function entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the second control plane entity supports selection of a first user plane entity and a ULCL function entity.
  • the first user plane entity and the ULCL function entity are collocated.
  • the third address is an N9 PSA F-TEID that is transmitted in a PFCP Session Establishment Response message
  • the fourth address is an N9 ULCL F-TEID that is transmitted in a DL remote FAR in a PFCP Session Modification Request message.
  • the second user plane entity includes a PSA entity
  • the second control plane entity includes a combined PGW-C and SMF entity
  • the first user plane entity includes a SGW-U entity
  • the ULCL function entity includes a ULCL PSA entity.
  • FIG. 28 schematically shows a block diagram of the second user plane entity 2800 according to the first exemplary embodiment of the present disclosure.
  • the second user plane entity 2800 in FIG. 28 may perform the method 800 as described previously with reference to FIG. 8. Accordingly, some detailed description on the second user plane entity 2800 may refer to the corresponding description of the method 800 in FIG. 8 and the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • the second user plane entity 2800 includes at least one processor 2801 and at least one memory 2803.
  • the at least one processor 2801 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 2803 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 2803 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 2803 stores instructions executable by the at least one processor 2801.
  • the instructions when loaded from the at least one memory 2803 and executed on the at least one processor 2801, may cause the first control plane entity 2800 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 8 with reference to the signaling sequence diagrams of FIGS. 9, 11A ⁇ 11B, and 13 as previously discussed, and thus will be omitted here for simplicity.
  • FIG. 29 schematically shows a block diagram of the second control plane entity 2900 according to the second exemplary embodiment of the present disclosure.
  • the second control plane entity 2900 in FIG. 29 may perform the method 1400 as described previously with reference to FIG. 14. Accordingly, some detailed description on the second control plane entity 2900 may refer to the corresponding description of the method 1400 in FIG. 14 and the signaling sequence diagram of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • the second control plane entity 2900 may include a triggering unit 2901 and a receiving unit 2903.
  • the triggering unit 2901 may be configured to trigger first session modification to a ULCL function entity.
  • the receiving unit 2903 may be configured to receive, from the ULCL function entity, a second address and a fourth address allocated to the ULCL function entity, wherein the second address is used for the first user plane entity to transmit UL traffic to the ULCL function entity, and the fourth address is used for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the triggering unit 2901 may be further configured to trigger second session modification to the second user plane entity.
  • the receiving unit 2903 may be further configured to receive, from the second user plane entity, a third address, that is allocated to the second user plane entity, for the ULCL function entity to transmit UL traffic to the second user plane entity.
  • the second control plane entity 2900 may further include a transmitting unit (not shown) , which may be configured to transmit the second address to a mobility management entity.
  • the receiving unit 2903 may be further configured to receive, from a first control plane entity, an eighth address that is allocated to the first user plane entity.
  • the transmitting unit may be further configured to transmit, to the ULCL function entity, the eighth address for the ULCL function entity to transmit DL traffic to the first user plane entity and the third address for the ULCL function entity to transmit UL traffic to the second user plane entity.
  • the transmitting unit may be further configured to transmit, to the second user plane entity, the fourth address for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the second address is an S5-U ULCL F-TEID that is received in a PFCP Session Modification Response message from the ULCL function entity
  • the fourth address is a N9 ULCL F-TEID that is received in the PFCP Session Modification Response message from the ULCL function entity.
  • the third address is an N9 PSA F-TEID that is received in a PFCP Session Modification Response message from the second user plane entity.
  • the third address is an N9 PSA F-TEID that is transmitted in a PFCP Session Modification Request message to the ULCL function entity
  • the eighth address is an S5/S8-U SGW F-TEID that is transmitted in the PFCP Session Modification Request message to the ULCL function entity.
  • the fourth address is the N9 ULCL F-TEID that is transmitted in a PFCP Session Modification Request message to the second user plane entity.
  • the transmitting unit may be further configured to transmit to the ULCL function entity, an indication of releasing a session between the ULCL function entity and the first user plane entity.
  • the second control plane entity 2900 may further include an insertion unit (not shown) , which may be configured to insert a ULCL function entity as previously described with reference to FIG. 9.
  • FIG. 30 schematically shows a block diagram of the second control plane entity 3000 according to the second exemplary embodiment of the present disclosure.
  • the second control plane entity 3000 in FIG. 30 may perform the method 1400 as described previously with reference to FIG. 14. Accordingly, some detailed description on the second control plane entity 3000 may refer to the corresponding description of the method 1400 in FIG. 14 and the signaling sequence diagram of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • the second control plane entity 3000 includes at least one processor 3001 and at least one memory 3003.
  • the at least one processor 3001 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 3003 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 3003 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 3003 stores instructions executable by the at least one processor 3001.
  • the instructions when loaded from the at least one memory 3003 and executed on the at least one processor 3001, may cause the first control plane entity 3000 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 14 with reference to the signaling sequence diagram of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • FIG. 31 schematically shows a block diagram of the ULCL function entity 3100 according to the second exemplary embodiment of the present disclosure.
  • the ULCL function entity 3100 in FIG. 31 may perform the method 1500 as described previously with reference to FIG. 15. Accordingly, some detailed description on the ULCL function entity 3100 may refer to the corresponding description of the method 1500 in FIG. 15 and the signaling sequence diagrams of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • the ULCL function entity 3100 may include a receiving unit 3101 and a transmitting unit 3103.
  • the receiving unit 3101 may be configured to receive, from a second control plane entity, a trigger of first session modification for the ULCL function entity.
  • the transmitting unit 3103 may be configured to transmit, to the second control plane entity, a second address and a fourth address allocated to the ULCL function entity, wherein the second address is used for the first user plane entity to transmit UL traffic to the ULCL function entity, and the fourth address is used for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the receiving unit 3101 may be further configured to receive a third address and an eighth address from the second control plane entity, wherein the third address is allocated to the second user plane entity, and forwarded from the second user plane entity by the second control plane entity for the ULCL function entity to transmit UL traffic to the second user plane entity, and the eighth address is allocated to the first user plane entity, and forwarded from the first control plane entity by the second control plane entity for the ULCL function entity to transmit UL traffic to the first user plane entity.
  • the second address is an S5-U ULCL F-TEID that is transmitted in a PFCP Session Modification Response message to the second control plane entity
  • the fourth address is an N9 ULCL F-TEID that is transmitted in the PFCP Session Modification Response message to the second control plane entity.
  • the third address is an N9 PSA F-TEID that is received in a PFCP Session Modification Request message from the second control plane entity
  • the eighth address is an S5/S8-U SGW F-TEID that is received in the PFCP Session Modification Request message from the second control plane entity.
  • the receiving unit 3101 may be further configured to receive, from the second control plane entity, an indication of releasing a session between the ULCL function entity and the first user plane entity; and releasing the session between the ULCL function entity and the first user plane entity.
  • FIG. 32 schematically shows a block diagram of the ULCL function entity 3200 according to the second exemplary embodiment of the present disclosure.
  • the ULCL function entity 3200 in FIG. 32 may perform the method 1500 as described previously with reference to FIG. 15. Accordingly, some detailed description on the ULCL function entity 3200 may refer to the corresponding description of the method 1500 in FIG. 15 and the signaling sequence diagrams of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • the ULCL function entity 3200 includes at least one processor 3201 and at least one memory 3203.
  • the at least one processor 3201 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 3203 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 3203 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 3203 stores instructions executable by the at least one processor 3201.
  • the instructions when loaded from the at least one memory 3203 and executed on the at least one processor 3201, may cause the first control plane entity 3200 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 15 with reference to the signaling sequence diagrams of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • FIG. 33 schematically shows a block diagram of the second user plane entity 3300 according to the second exemplary embodiment of the present disclosure.
  • the second user plane entity 3300 in FIG. 33 may perform the method 1600 as described previously with reference to FIG. 16. Accordingly, some detailed description on the ULCL function entity 3300 may refer to the corresponding description of the method 1600 in FIG. 16 and the signaling sequence diagrams of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • the second user plane entity 3300 may include a transmitting unit 3301 and a receiving unit 3303.
  • the transmitting unit 3301 may be configured to transmit, to a second control plane entity, a third address allocated to the second user plane entity, which is to be used for a ULCL function entity to transmit UL traffic to the second user plane entity
  • the receiving unit 3303 may be configured to receive, from the second control plane entity, a fourth address, that is allocated to the ULCL function entity and forwarded from the ULCL function entity by the second control plane entity, for the second user plane entity to transmit DL traffic to the ULCL function entity.
  • the third address is an N9 PSA F-TEID that is transmitted in a PFCP Session Modification Response message
  • the fourth address is an N9 ULCL F-TEID that is received in a PFCP Session Modification Request message from the second control plane entity.
  • FIG. 34 schematically shows a block diagram of the second user plane entity 3400 according to the second exemplary embodiment of the present disclosure.
  • the second user plane entity 3400 in FIG. 34 may perform the method 1600 as described previously with reference to FIG. 16. Accordingly, some detailed description on the ULCL function entity 3400 may refer to the corresponding description of the method 1600 in FIG. 16 and the signaling sequence diagrams of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • the second user plane entity 3400 includes at least one processor 3401 and at least one memory 3403.
  • the at least one processor 3401 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions.
  • the at least one memory 3403 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) .
  • the at least one processor memory 3403 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.
  • the at least one memory 3403 stores instructions executable by the at least one processor 3401.
  • the instructions when loaded from the at least one memory 3403 and executed on the at least one processor 3401, may cause the first control plane entity 3400 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIG. 16 with reference to the signaling sequence diagrams of FIG. 17 as previously discussed, and thus will be omitted here for simplicity.
  • the present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM) , a flash memory and a hard drive.
  • the computer program product includes a computer program.
  • the computer program includes: code/computer readable instructions, which when executed by the at least one processor 2001 causes the first control plane entity 2000 to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 4; or code/computer readable instructions, which when executed by the at least one processor 2201 causes the second control plane entity 2200 to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIG. 5; or code/computer readable instructions, which when executed by the at least one processor 2401 causes the ULCL function entity 2400 to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIG.
  • code/computer readable instructions which when executed by the at least one processor 2601 causes the first user plane entity 2600 to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 7; or code/computer readable instructions, which when executed by the at least one processor 2801 causes the second user plane entity 2800 to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIG. 8; or code/computer readable instructions, which when executed by the at least one processor 3001 causes the second control plane entity 3000 to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIG.
  • code/computer readable instructions which when executed by the at least one processor 3201 causes the ULCL function entity 3200 to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIG. 15; or code/computer readable instructions, which when executed by the at least one processor 3401 causes the second user plane entity 3400 to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIG. 16.
  • the computer program product may be configured as a computer program code structured in computer program modules.
  • the computer program modules could essentially perform the actions of the flow illustrated in any of FIGS. 4 to 8 and 14 to 16.
  • the processor may be a single CPU (Central processing unit) , but could also include two or more processing units.
  • the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuit (ASICs) .
  • the processor may also include board memory for caching purposes.
  • the computer program may be carried by a computer program product connected to the processor.
  • the computer program product may include a non-transitory computer readable storage medium on which the computer program is stored.
  • the computer program product may be a flash memory, a Random-access memory (RAM) , a Read-Only Memory (ROM) , or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories.
  • RAM Random-access memory
  • ROM Read-Only Memory
  • EEPROM Electrically Erasable programmable read-only memory

Landscapes

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

Abstract

Procédés, entités et support lisible par ordinateur pour l'insertion ULCL. Le procédé au niveau d'une seconde entité de plan de contrôle qui prend en charge la sélection d'une première entité de plan utilisateur et d'une entité fonctionnelle ULCL comprend : la réalisation d'un processus d'insertion d'une entité fonctionnelle ULCL pendant un établissement de connexion.
PCT/CN2020/127784 2020-11-10 2020-11-10 Procédés, entités et support lisible par ordinateur pour l'insertion ulcl WO2022099453A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/127784 WO2022099453A1 (fr) 2020-11-10 2020-11-10 Procédés, entités et support lisible par ordinateur pour l'insertion ulcl

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/127784 WO2022099453A1 (fr) 2020-11-10 2020-11-10 Procédés, entités et support lisible par ordinateur pour l'insertion ulcl

Publications (1)

Publication Number Publication Date
WO2022099453A1 true WO2022099453A1 (fr) 2022-05-19

Family

ID=81600738

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/127784 WO2022099453A1 (fr) 2020-11-10 2020-11-10 Procédés, entités et support lisible par ordinateur pour l'insertion ulcl

Country Status (1)

Country Link
WO (1) WO2022099453A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150366000A1 (en) * 2014-06-12 2015-12-17 Nokia Solutions And Networks Oy Architecture for radio access network and evolved packet core
US20160212179A1 (en) * 2013-08-19 2016-07-21 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for establishing a connection in a telecommunications network
US20180097894A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Method and system for user plane path selection
CN109413619A (zh) * 2017-08-14 2019-03-01 中兴通讯股份有限公司 信息发送、操作执行方法及装置、会话管理功能实体
WO2019134464A1 (fr) * 2018-01-08 2019-07-11 电信科学技术研究院有限公司 Procédé et appareil de transmission de données de liaison descendante
CN110636639A (zh) * 2018-06-25 2019-12-31 大唐移动通信设备有限公司 一种会话管理方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160212179A1 (en) * 2013-08-19 2016-07-21 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for establishing a connection in a telecommunications network
US20150366000A1 (en) * 2014-06-12 2015-12-17 Nokia Solutions And Networks Oy Architecture for radio access network and evolved packet core
US20180097894A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Method and system for user plane path selection
CN109413619A (zh) * 2017-08-14 2019-03-01 中兴通讯股份有限公司 信息发送、操作执行方法及装置、会话管理功能实体
WO2019134464A1 (fr) * 2018-01-08 2019-07-11 电信科学技术研究院有限公司 Procédé et appareil de transmission de données de liaison descendante
CN110636639A (zh) * 2018-06-25 2019-12-31 大唐移动通信设备有限公司 一种会话管理方法及装置

Similar Documents

Publication Publication Date Title
US10873886B2 (en) Mobile edge platform switching method, apparatus, and system
US20200366525A1 (en) Method, device, and system for controlling tunnel identifier allocation
US20200413244A1 (en) Method for registering terminal in wireless communication system and apparatus therefor
US11696358B2 (en) Methods and nodes for handling bearers
US20120099561A1 (en) Handover Control Method and Device
KR102293707B1 (ko) 전송 제어 방법, 장치 및 시스템
EP4191951A1 (fr) Procédé, appareil et système de traitement de session
WO2019101292A1 (fr) Fonction et procédé de traitement de trafic pour une application
CN109314909B (zh) 一种锚点网关的切换方法、装置及系统
BR122016004704A2 (pt) Sistema, método e aparelho de comunicação
EP3120654A1 (fr) Rétablissement de double connectivité
JP2019521588A (ja) 通信制御方法および関連するネットワーク要素
CN103703823A (zh) 移动终止呼叫改进
CN109429362B (zh) 会话处理方法及装置
EP3627799A1 (fr) Terminal de communication et procédé permettant d'établir une session de communication
US20160100337A1 (en) Circuit switched fallback method and device
CN105325031B (zh) 一种业务路径变更方法及装置
EP3883332A1 (fr) Dispositif utilisateur, dispositif de commande et procédé de commande de communication
KR20190004220A (ko) 5g 단말 서비스 연속성 관리를 위한 upf 장치 재배치 방법
US11252627B2 (en) Maintaining local offloading of traffic in a handover from a fifth generation system (5GS) to an evolved packet system (EPS)
CN114599065A (zh) 网络切换方法、融合网元、通信系统和存储介质
CN116916402A (zh) 用于在重定位时协调到边缘应用服务器的无缝服务连续性的机制
US20220248370A1 (en) Signaling Delivery in a Wireless Network
WO2022099453A1 (fr) Procédés, entités et support lisible par ordinateur pour l'insertion ulcl
WO2022099647A1 (fr) Procédés, entités et supports lisibles par ordinateur pour activation/modification d'ulcl

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20961012

Country of ref document: EP

Kind code of ref document: A1