[go: up one dir, main page]

WO2025173532A1 - Method, application server and user plane function - Google Patents

Method, application server and user plane function

Info

Publication number
WO2025173532A1
WO2025173532A1 PCT/JP2025/002647 JP2025002647W WO2025173532A1 WO 2025173532 A1 WO2025173532 A1 WO 2025173532A1 JP 2025002647 W JP2025002647 W JP 2025002647W WO 2025173532 A1 WO2025173532 A1 WO 2025173532A1
Authority
WO
WIPO (PCT)
Prior art keywords
application server
upf
network
traffic
dnai
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/JP2025/002647
Other languages
French (fr)
Inventor
Hiroshi Dempo
Hassan Al-Kanani
Iskren Ianev
Kundan Tiwari
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Publication of WO2025173532A1 publication Critical patent/WO2025173532A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the present disclosure relates to a core network node and a method of a core network node and so on.
  • the central part of the DN supports application servers.
  • the central part of DN may resides in a cloud environment.
  • the application servers in the central part of the DN is specifically named as Central Application Servers (CAS) in this disclosure.
  • CAS Central Application Servers
  • the local part of the DN attached to another local PSA (L-PSA) UPF in 5GC via the N6 reference point is located at a location closer to UEs.
  • the local part of the DN can be deployed in a distributed way.
  • the local part of the DN hosts Edge Hosting Environment (EHE) which also supports application servers.
  • EHE Edge Hosting Environment
  • the application servers in the local part of the DN is specifically named as Edge Application Servers (EAS) in this disclosure.
  • - AF is an Application Function
  • AF_EAS is a type of an AF and the application server resident in an Edge Hosting Environment (EHE) of a local part of DN, performing the server functions.
  • EHE Edge Hosting Environment
  • - AF_EES is another type of an AF and has functionalities, for example, enabling exchange of application data traffic with the EAS; providing API invoker and API exposing functions; interacting with 3GPP Core Network (e.g., NEF); supporting external exposure of 3GPP network and service capabilities to the EAS(s)
  • NEF 3GPP Core Network
  • each of Aspects and elements included in the each Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.
  • An example object of this disclosure is to provide a method and apparatus that can solve the above problem.
  • Fig. 1 5GS providing access to EAS with UL CL/BP for non-roaming scenario, TS23.548 [5]
  • Fig. 2 Transit gateway and traffic steering service in 5GS
  • Fig. 3 Transit gateway on UPF in distributed anchor point model
  • Fig. 4 Transit gateway on UPF in session breakout model
  • Fig. 5 Transit gateway on UPF in Multiple PDU sessions model
  • Fig. 6 Operations to connect with transit gateway
  • Fig. 7 AF Traffic Influence for traffic routing
  • Fig. 8 System overview
  • Fig. 9 User equipment
  • Fig. 10 (R)AN node
  • Fig. 11 System overview of (R)AN node 5 based on O-RAN architecture
  • Fig. 12 Radio Unit (RU)
  • Fig. 13 Distributed Unit (DU) Fig.
  • Fig. 14 Centralized Unit (CU) Fig. 15: AMF Fig. 16: SMF Fig. 17: UPF Fig. 18: PCF Fig. 19: NEF Fig. 20: UDM Fig. 21: NSSF Fig. 22: General block diagram for AF Fig. 23: PDU Session Establishment Procedure
  • Second aspect Transit gateway service in 5GS
  • An aspect of this disclosure focuses on how to interconnect local parts of the DN with either central or another local part of DN as described in the 1 st problem, i.e., how to interconnect the central and/or local parts of the DN and activate the communication link to transfer traffic satisfying edge computing requirements.
  • the disclosure includes a 5G system that supports edge computing environment.
  • the 5G system supports edge computing environment by one or a combination of the enablers introduced in TS23.501 [2] as well as a new enabler in this solution 1 that supports transit gateway service to route traffic between local parts Data Network and either a central or another local part of DN.
  • Fig. 2 shows an example of a transit gateway service connecting to edge computing environments in a 5G system.
  • the 5GC is a core network system owned by a PLMN operator and another network system identified by DNN-A is owned by the same PLMN operator or external organization such as enterprise companies, cloud service operators/providers.
  • the DNN-A consists of DN1 and DN2 network infrastructures.
  • DN1 is deployed in a local site located closer to UEs in the PLMN.
  • DN2 is also deployed in a local site located closer to UEs in the PLMN.
  • DN2 can be deployed in a central site located closer to or co-located with, for example, an enterprise system or cloud data centers.
  • DN1 is connected with 5GC over DNAI#11 and DNAI#12.
  • DNAI#11 is used to route traffic from/to UE and DNAI#12 is used to route traffic from/to DN2.
  • DN2 is connected with 5GC over DNAI#21 and DNAI#22.
  • DNAI#21 is used to route traffic from/to UE, and DNAI#22 is used to route traffic from/to DN2 through the transit gateway.
  • Traffic from UE is processed at DN1 and then routed back to 5GC over DNAI#12 if the traffic needs to be processed at DN2.
  • Transit gateway service in 5GC is to route traffic from DN1 over DNAI#12 to DN2 over DNAI#22 vice versa.
  • the DNN-A consists of DN1 and DN2.
  • Traffic from UE is processed at EAS1 in DN1 and then forwarded to UPF3 over DNAI#12 if the traffic needs to be processed at EAS2.
  • TGW in UPF3 receives the traffic from EAS1 over DNAI#12 and then route the traffic to EAS2 over DNAI#22.
  • the 5GC is a core network system owned by a PLMN operator and another network system identified by DNN-A is owned by the same PLMN operator or external organization such as enterprise companies, cloud service operators.
  • DN1 is deployed in a local site located at closer to UEs in the PLMN.
  • DN2 is also deployed in a central site connecting to 5GC in the PLMN.
  • DN1 is connected with the 5GC over DNAI#12 that is used to forward traffic from/to UPF2.
  • DN2 is connected with 5GC over DNAI#21 is used to forward traffic from/to PSA-UPF2.
  • the PDU session is split on the PSA-UPF1 and connected with DN1 to access EAS1.
  • EAS1 may forwards the edge application traffic to DNAI#12 if the edge application traffic processed by EAS1 needs to be further processed by CAS2.
  • TGW in the PSA-UPF2 receives the edge application traffic over DNAI#12 and routes the edge application traffic to CAS2 over DNAI#21.
  • Variant 3 of Solution 1 Transit gateway on UPF in Multiple PDU sessions
  • An aspect of Variant 3 of Solution 1 includes a User Plane Function (UPF) that enables a transit gateway service (TGW) disclosed in the solution 1 in multiple PDU sessions model.
  • UPF User Plane Function
  • TGW transit gateway service
  • the 5GC is a core network system owned by a PLMN operator and another network system identified by DNN-A is owned by the same PLMN operator or external organization such as enterprise companies, cloud service operators.
  • EAS1 may forwards the edge application traffic to DNAI#12 if the edge application traffic processed by EAS1 needs to be further processed by CAS2.
  • OAM_ECSP asks to OAM in the PLMN to connect EAS1 and EAS2 to the targeted UPF.
  • Step 2-10 OAM_ECSP responds EAS1 with output.
  • the output includes PSA-UPF2 information.
  • Step 2-11 EAS1 executes Solution 3 to add information for traffic detections and traffic routings.
  • Step 3-1 AF invokes Nnef_TrafficInfluence_Create service operation in TS23.502 [3].
  • the parameter includes information about Traffic Descriptions and N6 Traffic Routing requirements.
  • Traffic Description in the AF Request as specified in TS23.501 [2] includes, for example, 5 IP tuples to detect an IP data flow.
  • the Traffic Description may further be prepared for individual DNAI while indicating DNAI information.
  • Step 3-2 The NEF stores the AF request information in the UDR.
  • Step 3-3 NEF responds to the request in the Step 3-1.
  • Step 3-4 UDR invokes Nudr_DM_Notify to notify PCF when the stored information, that is relevant to AF traffic influence for traffic routing, is modified.
  • Step 3-5 By referring to the received AF Request in the step 3-4, PCF determines if there is any impacts about service data flow detection information and Application Function influence on traffic routing Enforcement Control in PCC rule described in TS23.503 [4].
  • the service data flow detection information containing service data flow filters, is used to detect incoming service data flows.
  • the service data flow filters are prepared while indicating incoming DNAI(s) that enables traffic detection coming from a DN to another DN.
  • the Application Function influence on traffic routing Enforcement Control specified in TS23.503 [4], is used to route the incoming traffic to outgoing network.
  • service data flow template in service data flow detection information is, for example, prepared for N6 traffic between EAS1 and EAS2, or between EAS1 and CAS2.
  • the service data flow filter, prepared for each incoming DNAI contains: -- information for matching user plane packets for IP PDU traffic, as described in TS23.503 [4], derived from the traffic description in the received AF Request. -- DNAI#12 to specify the target DNAI as an enhancement to the current specificaiton.
  • Application Function influence on traffic routing Enforcement Control contains outgoing DNAI, traffic steering policy identifier and N6 traffic routing information.
  • Appropriate information is set for the opposite direction for traffic from DN2 to DN1.
  • Step 3-8 NRF determines a set of UPF instance(s) matching with the Nnrf_NFDiscovery_Request.
  • Step 3-10 SMF maps the service data flow template in the policy information received in the step3-6 into Packet Detection Rules used in UPF.
  • the PDR prepared indicating incoming DNAI in this solution enables traffic detection coming from DN1 to DN2 while isolating different IP domains.
  • Variant 1 of Solution 1 user plane traffic comes from EAS1 in DN1 to EAS2 in DN2, then the incoming traffic on DNAI#12 is detected by the new packet filter in the UPF3 and then forwarded to outgoing DNAI#22.
  • Variant 2 or Variant 3 of Solution1 For Variant 2 or Variant 3 of Solution1, user plane traffic comes from EAS1 in DN1 to CAS2 in DN2, then the incoming traffic on DNAI#12 is detected by the new packet filter in the PSA-UPF2 in this disclosure and then routed to outgoing DNAI#21.
  • Solution 4 focuses on how to do Solutions1-3 during a PDU Session Establishment procedure.
  • the PDU Session Establishment procedure is specified in TS23.502[3].
  • Step 4-1 As described in TS23.502 [3], UE sends PDU Session Establishment Request message to the AMF, and the AMF forwards a N1 SM container comprising the PDU Session Establishment Request message to the SMF.
  • SMF may perform an SM Policy Association Establishment procedure to have a policy that is relevant to traffic steering requested by AF Request.
  • Step 4-2 SMF determine application servers and selects UPF connecting the application server during EAS discovery described in TS23.548 [5].
  • Step 4-3 and Step 4-4 N4 session management procedure is done in Step 4-3 and Step 4-4.
  • N4 session management procedure is used to control the functionality of the UPF and specified in TS 23.501[2] and TS23.502[3].
  • the SMF sends N4 Session Establishment Request to the UPF to provide Packet Detection Rule (PDR) to be installed on the UPF for this PDU session.
  • PDR Packet Detection Rule
  • the SMF maps the service data flow template in the policy information received in the step3-6 of Solution 3 into Packet Detection Rules (PDRs) used in the UPF.
  • PDRs Packet Detection Rules
  • the PDR indicates incoming DNAI that enables traffic detection coming from a DN to another DN.
  • the UPF acknowledges by sending an N4 Session Establishment Response.
  • the (R)AN node 5 can also support a communication using satellite access.
  • the (R)AN node 5 may support a satellite access and a terrestrial access.
  • the core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1.
  • the core network 7 may be a 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions.
  • 5GC 5G Core Network
  • Each function in a logical node can be considered as a network function.
  • the network function may be provided to another node by adapting the Service Based Architecture (SBA).
  • SBA Service Based Architecture
  • the core network 7 may support the Non-Public Network (NPN).
  • NPN Non-Public Network
  • the NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the User plane of the Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5.
  • the User plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection.
  • the Control plane of the Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5.
  • the Control plane of the Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.
  • - RRC Setup Request message This message is sent from the UE 3 to the (R)AN node 5.
  • any of the following parameters may be included together in the RRC Setup Request message. -- establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue.
  • - RRC Setup message This message is sent from the (R)AN node 5 to the UE 3.
  • any of the following parameters may be included together in the RRC Setup message.
  • RRC Setup Complete message This message is sent from the UE 3 to the (R)AN node 5.
  • RRC Setup Complete message This message is sent from the UE 3 to the (R)AN node 5.
  • any of the following parameters may be included together in the RRC Setup Complete message. -- guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity
  • - Registration Accept message This message is sent from the AMF 70 to the UE 3.
  • any of the following parameters may be included together in the Registration Accept message.
  • any of the following parameters may be populated together in the Service Accept message. -- PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value.
  • - Service Reject message This message is sent from the AMF 70 to the UE 3.
  • any of the following parameters may be populated together in the Service Reject message. -- 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list.
  • - Configuration Update Command message This message is sent from the AMF 70 to the UE 3.
  • the UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).
  • transport equipment for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.
  • the UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and/or wireless communication technologies.
  • IoT Internet of things
  • the controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
  • FIG. 15 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G).
  • the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622.
  • a controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g.
  • the CU 62 may support the Non-Public Network (NPN).
  • NPN Non-Public Network
  • the NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the CU 62 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated/combined unit above.
  • Session Management Function Fig. 17 is a block diagram illustrating the main components of the SMF 71.
  • the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712.
  • a controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714.
  • Software may be pre-installed in the memory 714 and/or may be downloaded via the telecommunication network or from a removable memory device (RMD), for example.
  • the software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421.
  • the SMF 71 may support the Non-Public Network (NPN).
  • NPN Non-Public Network
  • the NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • FIG. 18 is a block diagram illustrating the main components of the UPF 72.
  • the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722.
  • a controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724.
  • Software may be pre-installed in the memory 724 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example.
  • the software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421.
  • radio access radio access
  • any other radio communications technology e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.
  • other fix line communications technology e.g. BBF Access, Cable Access, optical access, etc.
  • Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop/tablet computers, web browsers, e-book readers and/or the like.
  • Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network.
  • IoT Internet of Things
  • MTC machine-type communication
  • the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and/or generally stationary) that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
  • a method performed by a first user plane function (UPF) related to a first data network connecting with a first application server comprising: receiving, from a Session Management Function (SMF), a second message comprising second information indicating packet detection rule for a traffic between the first application server and a second application server connecting with a second data network related to a second UPF; and transmitting, based on the second information, a first data to the second UPF.
  • UPF user plane function

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

An aspect of this disclosure includes a core network that selects a UPF close to the UE and forwards traffic to enable the local access to Data Network and between Data Networks via N6 interfaces according to the provided traffic steering rules to the UPF.

Description

METHOD, APPLICATION SERVER AND USER PLANE FUNCTION
　　The present disclosure relates to a core network node and a method of a core network node and so on.
　　Edge Computing enables network operators and 3rd party service providers to host application servers close to the UE's access point of attachment, so as to achieve a service delivery through reduced end-to-end latency and load on the transport network.
　　Fig. 1 shows an architectural view of an edge computing system specified in TS 23.548 [5]. In the context of the present edge computing system, a Data Network (DN) can be categorized as a central or a local part of a DN.
　　The central part of the DN attached to a central PDU Session Anchor (C-PSA) User Plane Function (UPF) in a 5G core (5GC) via an N6 reference point is located at a far side of the 5G system relative to UEs.
　　The central part of the DN supports application servers.
　　For example, the central part of DN may resides in a cloud environment.
　　The application servers in the central part of the DN is specifically named as Central Application Servers (CAS) in this disclosure.
　　On the other hand, the local part of the DN attached to another local PSA (L-PSA) UPF in 5GC via the N6 reference point is located at a location closer to UEs. The local part of the DN can be deployed in a distributed way.
　　The local part of the DN hosts Edge Hosting Environment (EHE) which also supports application servers.
　　The application servers in the local part of the DN is specifically named as Edge Application Servers (EAS) in this disclosure.
　　The Local part of the DN in which EHE is deployed may have user plane connectivity with both a centrally deployed PSA and locally deployed PSA of same DNN.
　　As described in TS23.558 [6], EAS acts as Application Function (AF) for consuming network services from the 3GPP 5G Core Network entities over the Service Based Architecture specified in 3GPP TS 23.501 [2].
NPL 1: [1] 3GPP TR 21.905 V17.1.0: "Vocabulary for 3GPP Specifications"
NPL 2: [2] 3GPP TS 23.501 V18.3.0 (2023-09) System architecture for the 5G System (5GS); Stage 2 (Release 18)
NPL 3: [3] 3GPP TS 23.502 V18.3.0 (2023-09) Procedures for the 5G System (5GS); Stage 2 (Release 18)
NPL 4: [4] 3GPP TS 23.503 V18.3.0 (2023-09) Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 18)
NPL 5: [5] 3GPP TS 23.548 V18.3.0 (2023-09) 5G System Enhancements for Edge Computing; Stage 2 (Release 18)
NPL 6: [6] 3GPP TS 23.558 V18.4.0 (2023-09) Architecture for enabling Edge Applications; (Release 18)
NPL 7: [7] 3GPP TS 28.538 V18.4.0 (2023-09) Edge Computing Management (ECM) (Release 18)
　　For some applications, there may be a case where the traffic is steered to any local part of DN first, then be further processed by EASs. After the processing, the application traffic may still need to be forwarded to the central part of DN for further processing. For example, application that handles raw data such as facial recognition data is processed by the EASs to remove privacy aspects, and then the processed data is transferred to the central part of DN to classify a congestion of the area.
　　Application traffics, however, may not be routed between central and local parts of the DN if there is no communication link between the PSA-UPF and Edge Hosting Environment, or there is no information about how to route the traffic between the central and local parts of the DN in the 5GS [2], [3].
　　The present disclosure aims to address and resolve the following problems:
- how to interconnect the central and/or local parts of the DN and activate the communication link to transfer traffic satisfying edge computing requirements,
- how to detect target traffic to be handled
Abbreviations
　　For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
4G-GUTI　　4G Globally Unique Temporary UE Identity
5GC　　5G Core Network
5GLAN　　5G Local Area Network
5GS　　5G System
5G-AN　　5G Access Network
5G-AN PDB　　5G Access Network Packet Delay Budget
5G-EIR　　5G-Equipment Identity Register
5G-GUTI　　5G Globally Unique Temporary Identifier
5G-BRG　　5G Broadband Residential Gateway
5G-CRG　　5G Cable Residential Gateway
5G GM　　5G Grand Master
5G-RG　　5G Residential Gateway
5G-S-TMSI　　5G S-Temporary Mobile Subscription Identifier
5G VN　　5G Virtual Network
5QI　　5G QoS Identifier
ABBA　　Anti-Bidding-down Between Architectures
AF　　Application Function
AMF　　Access and Mobility Management Function
API　　Application Programming Interface
AS　　Access Stratum
ATSSS　　Access Traffic Steering, Switching, Splitting
ATSSS-LL　　ATSSS Low-Layer
AUSF　　Authentication Server Function
AUTN　　Authentication token
BBF　　Broadband Forum
BMCA　　Best Master Clock Algorithm
BSF　　Binding Support Function
CAG　　Closed Access Group
CAPIF　　Common API Framework for 3GPP northbound APIs
CHF　　Charging Function
CL/BP　　Classifier/Branching Point
CN PDB　　Core Network Packet Delay Budget
CP　　Control Plane
C-PSA UPF　　Central PSA UPF
CU　　Centralized Unit
DAPS　　Dual Active Protocol Stacks
DL　　Downlink
DN　　Data Network
DNAI　　DN Access Identifier
DNN　　Data Network Name
DRX　　Discontinuous Reception
DS-TT　　Device-side TSN translator
DU　　Distributed Unit
ePDG　　evolved Packet Data Gateway
EAP　　Extensible Authentication Protocol
EAS　　Edge Application Server
EBI　　EPS Bearer Identity
EES　　Edge Enabler Server
EHE　　Edge Hosting Environment
EPS　　Evolved Packet System
EUI　　Extended Unique Identifier
FAR　　Forwarding Action Rule
FN-BRG　　Fixed Network Broadband RG
FN-CRG　　Fixed Network Cable RG
FN-RG　　Fixed Network RG
FQDN　　Fully Qualified Domain Name
GFBR　　Guaranteed Flow Bit Rate
GMLC　　Gateway Mobile Location Centre
GPSI　　Generic Public Subscription Identifier
GUAMI　　Globally Unique AMF Identifier
GUTI　　Globally Unique Temporary UE Identity
HR　　Home Routed (roaming)
IAB　　Integrated access and backhaul
IMEI　　International Mobile Equipment Identity
IMEI/TAC　　IMEI Type Allocation Code
IMS　　IP Multimedia Subsystem
IOWN　　Innovative Optical and Wireless Network
IPUPS　　Inter PLMN UP Security
I-SMF　　Intermediate SMF
I-UPF　　Intermediate UPF
LADN　　Local Area Data Network
LBO　　Local Break Out (roaming)
LMF　　Location Management Function
LoA　　Level of Automation
LPP　　LTE Positioning Protocol
L-PSA UPF　　Local PSA UPF
LRF　　Location Retrieval Function
LTE　　Long Term Evolution
MAC　　Medium Access Control
MCC　　Mobile country code
MCX　　Mission Critical Service
MDBV　　Maximum Data Burst Volume
MFBR　　Maximum Flow Bit Rate
MICO　　Mobile Initiated Connection Only
MNC　　Mobile Network Code
MO　　Mobile Originated
MPS　　Multimedia Priority Service
MPTCP　　Multi-Path TCP Protocol
MT　　Mobile Terminated
MT　　Mobile Termination
N3IWF　　Non-3GPP InterWorking Function
N5CW　　Non-5G-Capable over WLAN
NAI　　Network Access Identifier
NAS　　Non-Access Stratum
NEF　　Network Exposure Function
NF　　Network Function
NGAP　　Next Generation Application Protocol
ngKSI　　Next Generation Key Set Identifier
NID　　Network identifier
NPN　　Non-Public Network
NR　　New Radio
NRF　　Network Repository Function
NSI ID　　Network Slice Instance Identifier
NSSAA　　Network Slice-Specific Authentication and Authorization
NSSAAF　　Network Slice-Specific Authentication and Authorization Function
NSSAI　　Network Slice Selection Assistance Information
NSSF　　Network Slice Selection Function
NSSP　　Network Slice Selection Policy
NW-TT　　Network-side TSN translator
NWDAF　　Network Data Analytics Function
O-RAN　　Open RAN Alliance
O-DU　　O-RAN Distributed Unit
O-CU　　O-RAN Centralized Unit
O-RU　　O-RAN Radio Unit
PCF　　Policy Control Function
PDB　　Packet Delay Budget
PDCP　　Packet Data Convergence Protocol
PDR　　Packet Detection Rule
PDU　　Protocol Data Unit
PEI　　Permanent Equipment Identifier
PER　　Packet Error Rate
PFD　　Packet Flow Description
PLMN　　Public Land Mobile Network
PNI-NPN　　Public Network Integrated Non-Public Network
PPD　　Paging Policy Differentiation
PPF　　Paging Proceed Flag
PPI　　Paging Policy Indicator
PSA　　PDU Session Anchor
PTP　　Precision Time Protocol
QFI　　QoS Flow Identifier
QoE　　Quality of Experience
QoS　　Quality of Service
RACS　　Radio Capabilities Signalling optimisation
(R)AN　　(Radio) Access Network
RG　　Residential Gateway
RU　　Radio Unit
RIM　　Remote Interference Management
RLC　　Radio Link Control
RQA　　Reflective QoS Attribute
RQI　　Reflective QoS Indication
RRC　　Radio Resource Control
RSN　　Redundancy Sequence Number
SA NR　　Standalone New Radio
SBA　　Service Based Architecture
SBI　　Service Based Interface
SCP　　Service Communication Proxy
SD　　Slice Differentiator
SDAP　　Service Data Adaptation Protocol
SEAF　　Security Anchor Functionality
SEPP　　Security Edge Protection Proxy
SMF　　Session Management Function
SMS　　Short Message Service
SMSF　　Short Message Service Function
SN　　Sequence Number
SN name　　Serving Network Name.
SNPN　　Stand-alone Non-Public Network
S-NSSAI　　Single Network Slice Selection Assistance Information
SOR　　Steering Of Roaming
SSC　　Session and Service Continuity
SSCMSP　　Session and Service Continuity Mode Selection Policy
SST　　Slice/Service Type
SUCI　　Subscription Concealed Identifier
SUPI　　Subscription Permanent Identifier
SV　　Software Version
TAI　　Tracking Area Identity
TCP　　Transmission Control Protocol
TNAN　　Trusted Non-3GPP Access Network
TNAP　　Trusted Non-3GPP Access Point
TNGF　　Trusted Non-3GPP Gateway Function
TNL　　Transport Network Layer
TNLA　　Transport Network Layer Association
TSC　　Time Sensitive Communication
TSCAI　　TSC Assistance Information
TSN　　Time Sensitive Networking
TSN GM　　TSN Grand Master
TSP　　Traffic Steering Policy
TT　　TSN Translator
TWIF　　Trusted WLAN Interworking Function
UCMF　　UE radio Capability Management Function
UDM　　Unified Data Management
UDR　　Unified Data Repository
UDSF　　Unstructured Data Storage Function
UE　　User Equipment
UL　　Uplink
UL CL　　Uplink Classifier
UP　　User Plane
UPF　　User Plane Function
URLLC　　Ultra Reliable Low Latency Communication
URRP-AMF　　UE Reachability Request Parameter for AMF
URSP　　UE Route Selection Policy
UU　　Interface between User Equipment and Radio Access Network
VID　　VLAN Identifier
VLAN　　Virtual Local Area Network
W-5GAN　　Wireline 5G Access Network
W-5GBAN　　Wireline BBF Access Network
W-5GCAN　　Wireline 5G Cable Access Network
W-AGF　　Wireline Access Gateway Function
WLAN　　Wireless Local Area Network
WUS　　Wake Up Signal
Definitions
　　For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
General
　　Quoting TS 23.558 [6] in relation to the Application Function categories,
- AF is an Application Function
- AF_EAS is a type of an AF and the application server resident in an Edge Hosting Environment (EHE) of a local part of DN, performing the server functions.
- AF_EES is another type of an AF and has functionalities, for example, enabling exchange of application data traffic with the EAS; providing API invoker and API exposing functions; interacting with 3GPP Core Network (e.g., NEF); supporting external exposure of 3GPP network and service capabilities to the EAS(s)
　　The section for system overview describes NEF, UDM, PCF and SMF.
　　Those skilled in the art will appreciate that elements in the figures in this document are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the Aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.
　　For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the Aspects illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.
　　The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or entities or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an Aspect", "in another Aspect" and similar language throughout this specification may, but not necessarily do, all refer to the same Aspect.
　　Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.
　　In the following specification and the claims, reference will be made to a number of terms, which may be defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.
　　As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.
　　Each of Aspects and elements included in the each Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.
　　Any lists described in following aspects include at least one parameter or multiple parameters.
　　An example object of this disclosure is to provide a method and apparatus that can solve the above problem.
Fig. 1 5GS providing access to EAS with UL CL/BP for non-roaming scenario, TS23.548 [5] Fig. 2 Transit gateway and traffic steering service in 5GS Fig. 3 Transit gateway on UPF in distributed anchor point model Fig. 4 Transit gateway on UPF in session breakout model Fig. 5 Transit gateway on UPF in Multiple PDU sessions model Fig. 6 Operations to connect with transit gateway Fig. 7 AF Traffic Influence for traffic routing Fig. 8: System overview Fig. 9: User equipment (UE) Fig. 10: (R)AN node Fig. 11: System overview of (R)AN node 5 based on O-RAN architecture Fig. 12: Radio Unit (RU) Fig. 13: Distributed Unit (DU) Fig. 14: Centralized Unit (CU) Fig. 15: AMF Fig. 16: SMF Fig. 17: UPF Fig. 18: PCF Fig. 19: NEF Fig. 20: UDM Fig. 21: NSSF Fig. 22: General block diagram for AF Fig. 23: PDU Session Establishment Procedure
First aspect (Solution 1): Transit gateway service in 5GS
　　An aspect of this disclosure focuses on how to interconnect local parts of the DN with either central or another local part of DN as described in the 1st problem, i.e., how to interconnect the central and/or local parts of the DN and activate the communication link to transfer traffic satisfying edge computing requirements.
　　The disclosure includes a 5G system that supports edge computing environment.
　　The 5G system supports edge computing environment by one or a combination of the enablers introduced in TS23.501 [2] as well as a new enabler in this solution 1 that supports transit gateway service to route traffic between local parts Data Network and either a central or another local part of DN.
　　Fig. 2 shows an example of a transit gateway service connecting to edge computing environments in a 5G system.
　　In the context, the 5GC is a core network system owned by a PLMN operator and another network system identified by DNN-A is owned by the same PLMN operator or external organization such as enterprise companies, cloud service operators/providers.
　　In Fig. 2 , the DNN-A consists of DN1 and DN2 network infrastructures.
　　DN1 is deployed in a local site located closer to UEs in the PLMN.
　　DN2 is also deployed in a local site located closer to UEs in the PLMN.
　　DN2 can be deployed in a central site located closer to or co-located with, for example, an enterprise system or cloud data centers.
　　DN1 is connected with 5GC over DNAI#11 and DNAI#12.
　　DNAI#11 is used to route traffic from/to UE and DNAI#12 is used to route traffic from/to DN2.
　　DN2 is connected with 5GC over DNAI#21 and DNAI#22.
　　DNAI#21 is used to route traffic from/to UE, and DNAI#22 is used to route traffic from/to DN2 through the transit gateway.
　　Traffic from UE is processed at DN1 and then routed back to 5GC over DNAI#12 if the traffic needs to be processed at DN2.
　　Transit gateway service in 5GC is to route traffic from DN1 over DNAI#12 to DN2 over DNAI#22 vice versa.
Variant 1 of Solution 1: Transit gateway on UPF in distributed anchor point
　　An aspect of Variant 1 of Solution 1 includes a User Plane Function (UPF) that enables a transit gateway service (TGW) disclosed in the solution 1 in distributed anchor point model.
　　As described in TS23.548 [5], distributed anchor point is a connectivity model where the PSA-UPFs are distributed and connected with each corresponding local part of DN.
　　There is no central site in the distributed anchor point model.
　　As shown in Fig. 3 , the 5GC is a core network system owned by a PLMN operator and another network system identified by DNN-A is owned by the same PLMN operator or external organization such as enterprise companies or cloud service operators.
　　It is assumed in this disclosure that interaction with externally provided DNN-A is conducted through the 5G core exposure function NEF.
　　The interactions are introduced in the solution 2 and solution 3.
　　In Fig. 3, the DNN-A consists of DN1 and DN2.
　　DN1 is deployed in a local site located closer to UEs in the PLMN.
　　DN2 is also deployed in a local site located closer to UEs in the PLMN.
　　DN1 is connected with the 5GC over DNAI#11 and DNAI#12.
　　DNAI#11 is used to forward traffic from/to PSA-UPF1 and DNAI#12 is used to forward traffic from/to UPF3.
　　DN2 is connected with 5GC over DNAI#21 and DNAI#22.
　　DNAI#21 is used to forward traffic from/to PSA-UPF2 and DNAI#22 is used to forward traffic from/to UPF3.
　　Traffic from UE is processed at EAS1 in DN1 and then forwarded to UPF3 over DNAI#12 if the traffic needs to be processed at EAS2.
　　TGW in UPF3 receives the traffic from EAS1 over DNAI#12 and then route the traffic to EAS2 over DNAI#22.
　　EAS2 may also have traffic from another UE and then EAS2 routes the traffic to UPF3 over DNAI#22 if the traffic needs to be processed at EAS1.
　　TGW in UPF3 may receive the traffic from EAS2 over DNAI#22 and then route the traffic to EAS1 over DNAI#12.
Variant 2 of Solution 1: Transit gateway on UPF in Session Breakout
　　An aspect of Variant 2 of Solution 1 includes a User Plane Function (UPF) that enables a transit gateway service (TGW) disclosed in the solution1 in session breakout model.
　　As shown in Fig. 4 , the 5GC is a core network system owned by a PLMN operator and another network system identified by DNN-A is owned by the same PLMN operator or external organization such as enterprise companies, cloud service operators.
　　It is assumed in this disclosure that interaction with externally provided DNN-A is conducted through the 5G core exposure function NEF.
　　The interactions are introduced in the solution 2 and solution 3.
　　In Fig. 4, the DNN-A consists of DN1 and DN2.
　　DN1 is deployed in a local site located at closer to UEs in the PLMN.
　　DN2 is also deployed in a central site connecting to 5GC in the PLMN.
　　DN1 is connected with the 5GC over DNAI#12 that is used to forward traffic from/to UPF2.
　　DN2 is connected with 5GC over DNAI#21 is used to forward traffic from/to PSA-UPF2.
　　In session breakout model, a UE has a PDU session to connect DN2 over PSA-UPF2 following PSA-UPF1.
　　The PDU session is split on the PSA-UPF1 and connected with DN1 to access EAS1.
　　Edge application traffic is selectively diverted to EAS1 over PSA-UPF1 and the rest of application traffic is routed to CAS2 over PSA-UPF2.
　　EAS1 may forwards the edge application traffic to DNAI#12 if the edge application traffic processed by EAS1 needs to be further processed by CAS2.
　　TGW in the PSA-UPF2 receives the edge application traffic over DNAI#12 and routes the edge application traffic to CAS2 over DNAI#21.
Variant 3 of Solution 1: Transit gateway on UPF in Multiple PDU sessions
　　An aspect of Variant 3 of Solution 1 includes a User Plane Function (UPF) that enables a transit gateway service (TGW) disclosed in the solution 1 in multiple PDU sessions model.
　　As shown in Fig. 5, the 5GC is a core network system owned by a PLMN operator and another network system identified by DNN-A is owned by the same PLMN operator or external organization such as enterprise companies, cloud service operators.
　　In Fig. 5, the DNN-A consists of DN1 and DN2.
　　DN1 is deployed in a local site located at closer to UEs in the PLMN.
　　DN2 is also deployed in a central site connecting to 5GC in the PLMN.
　　DN1 is connected with the 5GC over DNAI#12 that is used to forward traffic from/to PSA-UPF2.
　　DN2 is connected with 5GC over DNAI#21 is used to forward traffic from/to PSA-UPF2.
　　In session breakout model, a UE has multiple PDU sessions to connect DN1 over PSA-UPF1 and DN2 over PSA-UPF2.
　　Edge computing applications use some of the PDU session(s) connecting to DN1 and use other PDU session(s) connecting to DN2.
　　EAS1 may forwards the edge application traffic to DNAI#12 if the edge application traffic processed by EAS1 needs to be further processed by CAS2.
　　TGW running in the PSA-UPF2 receives the edge application traffic over DNAI#12 and routes the edge application traffic to CAS2 over DNAI#21.
Second aspect (Solution 2): Provisioning for DNAIs for transit gateway
　　An aspect of this disclosure, Solution 2, focuses on how to activate the communication link to transfer traffic in the 1st problem.
　　The following architectural assumptions are considered in this disclosure.
- The following steps are, for example, introduced in the context of Variants of solution 1.
- The steps are initiated when EAS1 needs to transfer edge application traffic to EAS2 or CAS2.
- EAS1 and EAS2 or CAS2 can discover their address with the procedure specified in TS 23.548 [5].
- UPF3 is not running in the beginning.
　　For Solution 2 the relevant operational steps to connect with transit gateway are highlighted in Fig. 6 and described in more details below:
Step 2-1
　　UPF as a NF service consumer invokes Nnrf_NFManagement_NFRegister Request to register NRF of its UPF profile when UPF becomes operative for the first time.
　　The request includes DNAI(s) hosted by the UPF and supported functionalities.
　　The supported functionality in this solution 2 is Transit Ggateway (TGW) functionalities.
　　The TGW enables routing between N6 reference points.
　　NRF responds UPF with an acceptance to Nnrf_NFManagement_NFRegister Request when the UPF profile is successfully stored.
Step 2-2
　　Following an operation for Nnef_DNAIMapping_Subscribe service in TS23.502 [3], EAS1 gives specific information of AF such as IP address and then receives List of DNAI(s) the targeted AS.
　　For Variant 1 of Solution 1, the target application is EAS2.
　　For Variant 2 or Variant 3 of Solution 1, the target application is CAS2.
Step 2-3
　　EAS1 invokes Nnrf_NFDiscovery_Request to find UPF(s) connecting to the targeted application servers.
　　For Variant 1 of Solution 1, the request includes parameters for:
- transit gateway functionalities, and
- Hosting DNAI(s) for EAS2.
　　For Variant 2 or Variant 3 of Solution 1, the request includes parameters for:
- transit gateway functionalities, and
- Hosting DNAI(s) for CAS2.
Step 2-4
　　NRF discovers a set of PSA-UPF instance(s) matching the Nnrf_NFDiscovery_Request.
　　For Variant 1 of Solution 1,
- NRF cannot discover any UPFs because there is no UPF supporting transit gateway.
　　For Variant 2 or Variant 3 of Solution 1,
- NRF discovers PSA-UPF2 supporting transit gateway as well as hosting DNAI#21 connecting to CAS2.
Step 2-5
　　NRF responds EAS1 with UPF profiles of the discovered UPF(s).
　　For Variant 1 of Solution 1,
- NRF responds EAS1 with output that describes there is no UPF(s) supporting transit gateway.
　　For Variant 2 or Variant 3 of Solution 1,
- NRF responds EAS1 with information about PSA-UPF2 supporting transit gateway as well as hosting DNAI#21 connecting to CAS2.
Step 2-6
　　EAS1 checks if the EAS1 is connected to the discovered UPF.
　　For Variant 1 of Solution 1,
- EAS1 determines that there is no UPF(s) supporting transit gateway.
　　For Variant 2 or Variant 3 of Solution 1,
- EAS1 determines that EAS1 is not connected to the PSA-UPF2 supporting transit gateway as well as hosting DNAI#21 connecting to CAS2.
Step 2-7
　　If no UPF or not connected to the discovered PSA-UPF, EAS1 creates N6 routing requirements.
　　For Variant 1 of Solution 1,
- EAS1 creates N6 traffic routing list that includes DNAI(s) associated with the EAS1 and N6 traffic routing information corresponding to each EAS1/ EAS2 DNAI
　　For Variant 2 or Variant 3 of Solution 1,
- EAS1 creates N6 traffic routing list that includes DNAI(s) associated with the EAS1 and N6 traffic routing information corresponding to each EAS1 DNAI
Step 2-8
　　EAS1 requests OAM_ECSP to connect EAS1 to the targeted UPF.
　　For Variant 1 of Solution 1,
- the request includes EAS1 and N6 traffic routing requirements corresponding to each EAS DNAI for DNAI#12.
- the request includes EAS2 and N6 traffic routing requirements corresponding to each EAS DNAI for DNAI#12.
　　For Variant 2 or Variant3 of Solution 1,
- the request includes EAS1 and N6 traffic routing requirements to be routed to EAS1.
Step 2-9
　　OAM_ECSP execute an operation for EAS to connect UPF specified in TS28.538 [7].
　　In the operation, OAM_ECSP asks to OAM in the PLMN to connect EAS1 and EAS2 to the targeted UPF.
　　For Variant 1 of Solution 1,
- UPF3 is newly created because OAM in the PLMN cannot find any UPFs to route traffic between EAS1 and EAS2.
　　For Variant 2 or Variant 3 of Solution 1,
- OAM in the PLMN finds PSA-UPF2 with transit gateway that route traffic between EAS1 and CAS2.
Step 2-10
　　OAM_ECSP responds EAS1 with output.
　　For Variant 1 of Solution 1,
- the output includes UPF3 information.
　　For Variant 2 or Variant 3 of Solution 1,
- the output includes PSA-UPF2 information.
Step 2-11
　　EAS1 executes Solution 3 to add information for traffic detections and traffic routings.
Third aspect (Solution 3): Traffic steering
　　An aspect of this disclosure, Solution 3, focuses on how to detect target traffic described in the 2nd problem.
　　The following architectural assumptions are considered in this disclosure.
- One of the cases described in Solution 1 is somehow achieved.
- Solution 2 or any other solutions have been executed to achieve one of the cases in Solution1
- For simplicity, the following solution focuses on the traffic from EAS1 to EAS2 or CAS2.
　　For Solution 3 the relevant operational steps to AF Traffic Influence for traffic routing are highlighted in Fig. 7 and described in more details below:
Step 3-1
　　AF invokes Nnef_TrafficInfluence_Create service operation in TS23.502 [3].
　　The parameter includes information about Traffic Descriptions and N6 Traffic Routing requirements.
　　Traffic Description in the AF Request as specified in TS23.501 [2] includes, for example, 5 IP tuples to detect an IP data flow.
　　In order to identify traffic on individual DNAI(s), the Traffic Description may further be prepared for individual DNAI while indicating DNAI information.
　　For Variant 1, Variant 2 or Variant3 of Solution 1
- A traffic description is prepared for DNAI#12
- An N6 Traffic Routing requirements is prepared for DNAI#12
Step 3-2
　　The NEF stores the AF request information in the UDR.
Step 3-3
　　NEF responds to the request in the Step 3-1.
Step 3-4
　　UDR invokes Nudr_DM_Notify to notify PCF when the stored information, that is relevant to AF traffic influence for traffic routing, is modified.
　　The notification includes the received AF Request in the step 3-2.
Step 3-5
　　By referring to the received AF Request in the step 3-4, PCF determines if there is any impacts about service data flow detection information and Application Function influence on traffic routing Enforcement Control in PCC rule described in TS23.503 [4].
　　The service data flow detection information, containing service data flow filters, is used to detect incoming service data flows.
　　An enhancement in the aspect of service data flow detection information, the service data flow filters are prepared while indicating incoming DNAI(s) that enables traffic detection coming from a DN to another DN.
　　The Application Function influence on traffic routing Enforcement Control specified in TS23.503 [4], is used to route the incoming traffic to outgoing network.
　　Any impacts can be found by checking the service data flow filters and Application Function influence on traffic routing Enforcement Control information with Traffic Description and N6 Traffic Routing requirements in AF Request in the step 3-4.
　　For Variant 1, Variant 2 or Variant 3 of Solution 1,
- service data flow template in service data flow detection information is, for example, prepared for N6 traffic between EAS1 and EAS2, or between EAS1 and CAS2.
- The service data flow filter, prepared for each incoming DNAI, contains:
-- information for matching user plane packets for IP PDU traffic, as described in TS23.503 [4], derived from the traffic description in the received AF Request.
-- DNAI#12 to specify the target DNAI as an enhancement to the current specificaiton.
　　Application Function influence on traffic routing Enforcement Control contains outgoing DNAI, traffic steering policy identifier and N6 traffic routing information.
　　For traffic from DN1 to DN2 in Variant 1 of Solution 1,
- Application Function influence on traffic routing Enforcement Control is prepared for outgoing DNAI#22.
- For the outgoing DNAI#22, N6 traffic routing information is prepared.
- The N6 traffic routing information contains IP address of EAS2 or network address hosting EAS2.
　　For traffic from DN1 to DN2 in Variant 2 or Variant 3 of Solution 1,
- Application Function influence on traffic routing Enforcement Control is prepared for outgoing DNAI#21.
- For the outgoing DNAI#21 N6 traffic routing information is prepared.
- The N6 traffic routing information contains IP address of CAS2 or network address hosting CAS2.
　　Appropriate information is set for the opposite direction for traffic from DN2 to DN1.
Step 3-6
　　SMF invokes Npcf_SMPolicyControle_UpdateNotify to give SMF the policy information.
Step 3-7
　　SMF receives the policy information on traffic routing in the step3-6.
　　If SMF does not have any information about the target UPF, SMF invokes Nnrf_NFDiscovery_Request to discover UPF supporting transit gateway and hosting incoming and outgoing DNAIs to apply the updated policy in the step3-5.
Step 3-8
　　NRF determines a set of UPF instance(s) matching with the Nnrf_NFDiscovery_Request.
Step 3-9
　　NRF responds SMF with UPF profiles matching with the Nnrf_NFDiscovery_Request in the step3-8.
Step 3-10
　　SMF maps the service data flow template in the policy information received in the step3-6 into Packet Detection Rules used in UPF.
　　The PDR is prepared while indicating incoming DNAI that enables traffic detection coming from a DN to another DN.
　　For Variant 1 of Solution 1, SMF updates
- the packet detection rules for traffic between EAS1 and EAS2
- Packet Detection Rules for DNAI#12 and DNAI#22
- routing information from DNAI#12 to DNAI#22 and from DNAI#22 to DNAI#12
　　For Variant 2 or Variant 3 of Solution 1, SMF updates
- the packet detection rules for traffic between EAS1 and CAS2
- Packet Detection Rules for DNAI#12 and DNAI#21
- routing information from DNAI#12 to DNAI#21 and from DNAI#21 to DNAI#12
　　As described in TS23.501 [2], Packet Detection Rule (PDR) contains information required to classify a packet arriving at the UPF.
　　The PDR prepared indicating incoming DNAI in this solution enables traffic detection coming from DN1 to DN2 while isolating different IP domains.
　　For Variant 1 of Solution 1, user plane traffic comes from EAS1 in DN1 to EAS2 in DN2, then the incoming traffic on DNAI#12 is detected by the new packet filter in the UPF3 and then forwarded to outgoing DNAI#22.
　　For Variant 2 or Variant 3 of Solution1, user plane traffic comes from EAS1 in DN1 to CAS2 in DN2, then the incoming traffic on DNAI#12 is detected by the new packet filter in the PSA-UPF2 in this disclosure and then routed to outgoing DNAI#21.
　　For both cases, the packet filter is derived from the parameters in AF Request source by EAS1.
　　The enhanced parameters specify the incoming DNAI to describe where traffic detection should be executed.
Fourth aspect (Solution 4): PDU Session Establishment Procedure
　　An aspect of this disclosure, Solution 4, focuses on how to do Solutions1-3 during a PDU Session Establishment procedure. The PDU Session Establishment procedure is specified in TS23.502[3].
　　The following architectural assumptions are considered in this disclosure.
- AF Request has been given 5GC by application servers (e.g. EAS, CAS).
- Then a new PDU Session Establishment is executed.
　　Following steps describe how to use the results of Solutions 2-3 having been executed to achieve one of the cases in Solution 1 during a PDU Session Establishment.
Step 4-1
　　As described in TS23.502 [3], UE sends PDU Session Establishment Request message to the AMF, and the AMF forwards a N1 SM container comprising the PDU Session Establishment Request message to the SMF.
　　SMF may perform an SM Policy Association Establishment procedure to have a policy that is relevant to traffic steering requested by AF Request.
Step 4-2
　　SMF determine application servers and selects UPF connecting the application server during EAS discovery described in TS23.548 [5].
　　In the UPF selection during the EAS discovery, the policy for traffic steering in the step4-1 is considered and following UPF(s) are selected.
　　For Variant 1 of Solution 1,
- UPF hosting DNAI#12 and DNAI#22
　　For Variant 2 or Variant 3 of Solution 1,
- UPF hosting DNAI#12
Step 4-3 and Step 4-4
　　N4 session management procedure is done in Step 4-3 and Step 4-4.
　　N4 session management procedure is used to control the functionality of the UPF and specified in TS 23.501[2] and TS23.502[3].
　　The SMF sends N4 Session Establishment Request to the UPF to provide Packet Detection Rule (PDR) to be installed on the UPF for this PDU session.
　　The SMF maps the service data flow template in the policy information received in the step3-6 of Solution 3 into Packet Detection Rules (PDRs) used in the UPF.
　　The PDR indicates incoming DNAI that enables traffic detection coming from a DN to another DN.
　　For Variant 1 of Solution 1, SMF updates
-　　the packet detection rules for traffic between EAS1 and EAS2
-　　Packet Detection Rules for DNAI#12 and DNAI#22
-　　routing information from DNAI#12 to DNAI#22 and from DNAI#22 to DNAI#12
　　For Variant 2 or Variant 3 of Solution 1, SMF updates
-　　the packet detection rules for traffic between EAS1 and CAS2
-　　Packet Detection Rules for DNAI#12 and DNAI#21
-　　routing information from DNAI#12 to DNAI#21 and from DNAI#21 to DNAI#12
　　The UPF acknowledges by sending an N4 Session Establishment Response.
Step 4-5
　　The SMF sends N1 SM container comprising a PDU Session Establishment Accept message to the AMF, and the AMF sends the PDU Session Establishment Accept message to the UE.
Step 4-6
　　The UE sends uplink data to the UPF, and the UPF process the uplink data based on the PDR.
　　Solution 4, focuses on how to do Solutions1-3 during the PDU Session Establishment procedure.
　　N4 session management procedure is done during other procedures specified in TS23.502[3], for example UE Triggered Service Request procedure, PDU Session Modification procedure.
System overview
　　Fig. 9 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) device (known as a user equipment (UE)) to which the above aspects are applicable.
　　The telecommunication system 1 represents a system overview in which an end-to-end communication is possible. For example, UE 3 (or user equipment, 'mobile device' 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7.
　　The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RATs including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).
　　The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively.
　　The (R)AN node 5 may be split into one or more control plane (CP) functions and one or more user plane (UP) functions. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane function is aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called 'dual connectivity' or 'Multi connectivity'.
　　The (R)AN node 5 can also support a communication using satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access.
　　In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN) Global Forum.
　　The core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in a logical node can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA).
　　A Network Function can be deployed as distributed, redundant, stateless, and scalable, and provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).
　　The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　As is well known, a UE 3 may enter and leave areas (i.e. radio cells) served by the (R)AN node 5 as the UE 3 is moving around in the geographical area covered by the telecommunication system 1. In order to keep track of the UE 3 and to facilitate movement between the different (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 is in communication with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.
　　The core network 7 also includes, amongst others, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Exposure Function (NEF) 74, a Unified Data Management (UDM) 75, and a Network Slice Selection Function (NSSF) 76. When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, and PCF 73 for the roaming-out UE 3.
　　The UE 3 and a respective serving (R)AN node 5 are connected via an appropriate air interface (for example the so-called "Uu" interface and/or the like). Neighboring (R)AN nodes 5 are connected to each other via an appropriate (R)AN node 5 to (R)AN node interface (such as the so-called "Xn" interface and/or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "N2"/ "N3" interface(s) and/or the like). From the core network 7, connection to a data network 20 is also provided. The data network 20 can be an internet, a public network, an external network, a private network or an internal network of the PLMN. In the case where the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the IP Multimedia Subsystem (IMS) service may be provided by that data network 20. The UE 3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet or unstructured data type.
　　The "Uu" interface may include a Control plane and User plane.
　　The User plane of the Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection.
　　The Control plane of the Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of the Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.
　　For example, the following messages are communicated over the RRC layer to support AS signaling.
- RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the RRC Setup Request message.
-- establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue.
- RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the RRC Setup message.
-- masterCellGroup and radioBearerConfig
- RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the RRC Setup Complete message.
-- guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity
　　The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and/or the like). The N1 interface is responsible for providing a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface.
- Registration Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the Registration Request message.
-- 5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication and Requested NB-N1 mode DRX parameters.
- Registration Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the Registration Accept message.
-- 5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters and Extended rejected NSSAI.
- Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, the following parameter may be included together in the Registration Complete message.
-- SOR transparent container.
- Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the Authentication Request message.
-- ngKSI,ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge) and EAP message.
- Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Authentication Response message.
-- Authentication response message identity, Authentication response parameter and EAP message.
- Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Authentication Result message.
-- ngKSI, EAP message and ABBA.
- Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Authentication Failure message.
-- Authentication failure message identity, 5GMM cause and Authentication failure parameter.
- Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, the following parameter may be populated together in the Authentication Reject message.
-- EAP message.
- Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Service Request message.
-- ngKSI,Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container.
- Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Service Accept message.
-- PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value.
- Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Service Reject message.
-- 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list.
- Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Configuration Update Command message.
-- Configuration update indication,5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication and Extended rejected NSSAI.
- Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, the following parameter may be populated together in the Configuration Update Complete message.
-- Configuration update complete message identity.
User equipment (UE)
　　Fig. 10 is a block diagram illustrating the main components of the UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32. Further, the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside. Although not necessarily shown in the Figure, the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. A controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating/sending/receiving) signalling and uplink/downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 10. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.
　　The UE 3 may, for example, support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　The UE 3 may, for example, be an item of equipment for production or manufacture and/or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and/or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and/or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and/or related machinery; paper converting machinery; chemical machinery; mining and/or construction machinery and/or related equipment; machinery and/or implements for agriculture, forestry and/or fisheries; safety and/or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and/or application systems for any of the previously mentioned equipment or machinery etc.).
　　The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).
　　The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).
　　The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and/or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).
　　The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).
　　The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and/or system, a weapon, an item of cutlery, a hand tool, or the like.
　　The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).
　　The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and/or wireless communication technologies.
　　Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and/or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and/or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored/tracked.
　　It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
　　It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.
　　The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device).
　　The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).
(R)AN node
　　Fig. 11 is a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. an RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.
　　The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case.
　　The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimation and/or moving trajectory estimation.
　　The (R)AN node 5 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
System overview of (R)AN node 5 based on O-RAN architecture
　　Fig. 12 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.
　　The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit, the DU 61 can be integrated/combined with the CU 62 as another integrated/combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated/combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and/or the like).
　　The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and/or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and/or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and/or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2"/ "N3" interface(s) and/or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes 7 via an appropriate interface (such as the so-called "N3" interface(s) and/or the like).
　　Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide a functionality to communicate with a UE 3 over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.
Radio Unit (RU)
　　Fig. 13 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.
　　The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3), and in particular, relating to MAC layer and RLC layer.
　　The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
　　The RU 60 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　As described above, the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated/combined unit above.
Distributed Unit (DU)
　　Fig. 14 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421 is responsible for handling (generating/sending/receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.
　　The DU 61 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　As described above, the DU 61 can be integrated/combined with the RU 60 or CU 62 as an integrated/combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated/combined unit above.
Centralized Unit (CU)
　　Fig. 15 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421 is responsible for handling (generating/sending/receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.
　　The CU 62 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　As described above, the CU 62 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated/combined unit above.
Access Management Function (AMF)
　　Fig. 16 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421 is responsible for handling (generating/sending/receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g. via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3).
　　The AMF 70 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
Session Management Function (SMF)
　　Fig. 17 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714. Software may be pre-installed in the memory 714 and/or may be downloaded via the telecommunication network or from a removable memory device (RMD), for example. The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421 is responsible for handling (generating/sending/receiving) signalling between the SMF 71 and other nodes, such as the UPF 72 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a Hypertext Transfer Protocol (HTTP) restful methods based on the service based interfaces) relating to session management procedures (for the UE 3).
　　The SMF 71 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
User Plane Function (UPF)
　　Fig. 18 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724. Software may be pre-installed in the memory 724 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421 is responsible for handling (generating/sending/receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a GPRS Tunneling Protocol (GTP) for User plane) relating to User data handling (for the UE 3).
　　The UPF 72 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
Policy Control Function (PCF)
　　Fig. 19 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421 is responsible for handling (generating/sending/receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
　　The PCF 73 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
Network Exposure Function (NEF)
　　Fig. 20 is a block diagram illustrating the main components of the NEF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the NEF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421 is responsible for handling (generating/sending/receiving) signalling between the NEF 74 and other nodes, such as the UDM 75 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network exposure function procedures (for the UE 3).
　　The NEF 74 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
Unified Data Management (UDM)
　　Fig. 21 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421 is responsible for handling (generating/sending/receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).
　　The UDM 75 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
Network Data Analytics Function (NWDAF)
　　Fig. 22 is a block diagram illustrating the main components of the NSSF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NSSF 76 in accordance with the software stored in a memory 764. The Software may be pre-installed in the memory 764 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421 is responsible for handling (generating/sending/receiving) signalling between the NSSF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).
　　The NSSF 76 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
Application Function (AF)
　　Fig. 23 is a block diagram illustrating the main components of the AF 201. As shown, the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014. Software may be pre-installed in the memory 2014 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421 is responsible for handling (generating/sending/receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). For example, the AF_EES and the AF_EAS may have same components to the AF 201.
　　The AF 201 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
Modifications and Alternatives
　　Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.
　　In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.
　　Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input/output (IO) circuits; internal memories / caches (program and/or data); processing registers; communication buses (e.g. control, data and/or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and/or timers; and/or the like.
　　In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities.
　　In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.
　　Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop/tablet computers, web browsers, e-book readers and/or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and/or generally stationary) that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
　　Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.
　　As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.
　　It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.
　　The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.
　　The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
　　While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).
Supplementary notes
　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes.
　　(Supplementary note 1)
　　　　A method performed by a first application server connecting with a first data network related to a first user plane function (UPF), the method comprising:
　　transmitting, to a first core network, a first request to discover a second application server connecting with a second data network related to a second UPF; and
　　receiving, from the first core network, a first response message comprising first information.
　　(Supplementary note 2)
　　The method according to Supplementary note 1, wherein
　　the method comprises connecting with the second application server based on the first information.
　　(Supplementary note 3)
　　The method according to Supplementary note 2, wherein
　　the method comprising transmitting a first data to the connected second application server.
　　(Supplementary note 4)
　　The method according to Supplementary note 2, the connecting with the second application server comprises:
　　for a first type mode, connecting with the second application server via a third UPF, and
　　for a second type mode, connecting with the second application server via the second UPF.
　　(Supplementary note 5)
　　A first application server connecting with a first data network related to a first user plane function (UPF), the first application server comprising:
　　one or more memories storing instructions; and
　　one or more processors configured to process the instructions to control the first application server to:
　　transmit, to a first core network, a first request to discover a second application server connecting with a second data network related to a second UPF; and
　　receive, from the first core network, a first response message comprising first information.
　　(Supplementary note 6)
　　The first application server according to Supplementary note 5, wherein
　　the one or more processors are configured to process the instructions to control the first application server to:
　　connect with the second application server based on the first information.
　　(Supplementary note 7)
　　The first application server according to Supplementary note 6, wherein
　　the one or more processors are configured to process the instructions to control the first application server to:
　　transmit a first data to the connected second application server.
　　(Supplementary note 8)
　　The first application server according to Supplementary note 6, wherein
　　the one or more processors are configured to process the instructions to control the first application server to:
　　for a first type mode, connect with the second application server via a third UPF, and
　　for a second type mode, connect with the second application server via the second UPF.
　　(Supplementary note 9)
　　A method performed by a first user plane function (UPF) related to a first data network connecting with a first application server, the method comprising:
　　receiving, from a Session Management Function (SMF), a second message comprising second information indicating packet detection rule for a traffic between the first application server and a second application server connecting with a second data network related to a second UPF; and
　　transmitting, based on the second information, a first data to the second UPF.
　　(Supplementary note 10)
　　　　The method according to Supplementary note 9, wherein
　　for a first type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via a third UPF, and
　　for a second type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via the second UPF.
　　(Supplementary note 11)
　　A first user plane function (UPF) related to a first data network connecting with a first application server, the first UPF comprising:
　　one or more memories storing instructions; and
　　one or more processors configured to process the instructions to control the first UPF to:
　　receive, from a Session Management Function (SMF), a second message comprising second information indicating packet detection rule for a traffic between the first application server and a second application server connecting with a second data network related to a second UPF; and
　　transmit, based on the second information, a first data to the second UPF.
　　(Supplementary note 12)
　　The first UPF according to Supplementary note 11, wherein
　　for a first type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via a third UPF, and
　　for a second type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via the second UPF.
　　This application is based upon and claims the benefit of priority from India Patent Application No. 202411010542, filed on February 15, 2024, the disclosure of which is incorporated herein in its entirety by reference.
20　　DATA NETWORK
201　　APPLICATION FUNCTION(AF)
2011　　TRANSCEIVER CIRCUIT
2012　　NETWORK INTERFACE
2013　　CONTROLLER
2014　　MEMORY
20141　　OPERATING SYSTEM
20142　　COMMUNICATIONS CONTROL MODULE
201421　　TRANSCEIVER CONTROL MODULE
3　　USER EQUIPMENT(UE)
31　　TRANSCEIVER CIRCUIT
32　　ANTENNA
33　　CONTROLLER
34　　USER INTERFACE
35　　USIM
36　　MEMORY
361　　OPERATING SYSTEM
362　　COMMUNICATIONS CONTROL MODULE
3621　　TRANSCEIVER CONTROL MODULE
5　　gNB
51　　TRANSCEIVER CIRCUIT
52　　ANTENNA
53　　NETWORK INTERFACE
54　　CONTROLLER
55　　MEMORY
551　　OPERATING SYSTEM
552　　COMMUNICATIONS CONTROL MODULE
5521　　TRANSCEIVER CONTROL MODULE
60　　RADIO UNIT(RU)
601　　TRANSCEIVER CIRCUIT
602　　ANTENNA
603　　NETWORK INTERFACE
604　　CONTROLLER
605　　MEMORY
6051　　OPERATING SYSTEM
6052　　COMMUNICATIONS CONTROL MODULE
60521　　TRANSCEIVER CONTROL MODULE
61　　DISTRIBUTED UNIT(DU)
611　　TRANSCEIVER CIRCUIT
612　　NETWORK INTERFACE
613　　CONTROLLER
614　　MEMORY
6141　　OPERATING SYSTEM
6142　　COMMUNICATIONS CONTROL MODULE
61421　　TRANSCEIVER CONTROL MODULE
62　　CENTRALIZED UNIT(CU)
621　　TRANSCEIVER CIRCUIT
622　　NETWORK INTERFACE
623　　CONTROLLER
624　　MEMORY
6241　　OPERATING SYSTEM
6242　　COMMUNICATIONS CONTROL MODULE
62421　　TRANSCEIVER CONTROL MODULE
7　　CORE NETWORK
70　　ACCESS AND MOBILITY FUNCTION(AMF)
701　　TRANSCEIVER CIRCUIT
702　　NETWORK INTERFACE
703　　CONTROLLER
704　　MEMORY
7041　　OPERATING SYSTEM
7042　　COMMUNICATIONS CONTROL MODULE
70421　　TRANSCEIVER CONTROL MODULE
71　　SESSION MANAGEMENT FUNCTION(SMF)
711　　TRANSCEIVER CIRCUIT
712　　NETWORK INTERFACE
713　　CONTROLLER
714　　MEMORY
7141　　OPERATING SYSTEM
7142　　COMMUNICATIONS CONTROL MODULE
71421　　TRANSCEIVER CONTROL MODULE
72　　USER PLANE FUNCTION(UPF)
721　　TRANSCEIVER CIRCUIT
722　　NETWORK INTERFACE
723　　CONTROLLER
724　　MEMORY
7241　　OPERATING SYSTEM
7242　　COMMUNICATIONS CONTROL MODULE
72421　　TRANSCEIVER CONTROL MODULE
73　　POLICY CONTROL FUNCTION(PCF)
731　　TRANSCEIVER CIRCUIT
732　　NETWORK INTERFACE
733　　CONTROLLER
734　　MEMORY
7341　　OPERATING SYSTEM
7342　　COMMUNICATIONS CONTROL MODULE
73421　　TRANSCEIVER CONTROL MODULE
74　　NETWORK EXPOSURE FUNCTION (NEF)
741　　TRANSCEIVER CIRCUIT
742　　NETWORK INTERFACE
743　　CONTROLLER
744　　MEMORY
7441　　OPERATING SYSTEM
7442　　COMMUNICATIONS CONTROL MODULE
74421　　TRANSCEIVER CONTROL MODULE
75　　UNIFIED DATA MANAGEMENT FUNCTION(UDM)
751　　TRANSCEIVER CIRCUIT
752　　NETWORK INTERFACE
753　　CONTROLLER
754　　MEMORY
7541　　OPERATING SYSTEM
7542　　COMMUNICATIONS CONTROL MODULE
75421　　TRANSCEIVER CONTROL MODULE
76　　NETWORK SLICE SELECTION FUNCTION (NSSF)
761　　TRANSCEIVER CIRCUIT
762　　NETWORK INTERFACE
763　　CONTROLLER
764　　MEMORY
7641　　OPERATING SYSTEM
7642　　COMMUNICATIONS CONTROL MODULE
76421　　TRANSCEIVER CONTROL MODULE

Claims (12)

  1. 　　A method performed by a first application server connecting with a first data network related to a first user plane function (UPF), the method comprising:
    　　transmitting, to a first core network, a first request to discover a second application server connecting with a second data network related to a second UPF; and
    　　receiving, from the first core network, a first response message comprising first information.
  2. 　　The method according to claim 1, wherein
    　　the method comprises connecting with the second application server based on the first information.
  3. 　　The method according to claim 2, wherein
    　　the method comprising transmitting a first data to the connected second application server.
  4. 　　The method according to claim 2, the connecting with the second application server comprises:
    　　for a first type mode, connecting with the second application server via a third UPF, and
    　　for a second type mode, connecting with the second application server via the second UPF.
  5. 　　A first application server connecting with a first data network related to a first user plane function (UPF), the first application server comprising:
    　　one or more memories storing instructions; and
    　　one or more processors configured to process the instructions to control the first application server to:
    　　transmit, to a first core network, a first request to discover a second application server connecting with a second data network related to a second UPF; and
    　　receive, from the first core network, a first response message comprising first information.
  6. 　　The first application server according to claim 5, wherein
    　　the one or more processors are configured to process the instructions to control the first application server to:
    　　connect with the second application server based on the first information.
  7. 　　The first application server according to claim 6, wherein
    　　the one or more processors are configured to process the instructions to control the first application server to:
    　　transmit a first data to the connected second application server.
  8. 　　The first application server according to claim 6, wherein
    　　the one or more processors are configured to process the instructions to control the first application server to:
    　　for a first type mode, connect with the second application server via a third UPF, and
    　　for a second type mode, connect with the second application server via the second UPF.
  9. 　　A method performed by a first user plane function (UPF) related to a first data network connecting with a first application server, the method comprising:
    　　receiving, from a Session Management Function (SMF), a second message comprising second information indicating packet detection rule for a traffic between the first application server and a second application server connecting with a second data network related to a second UPF; and
    　　transmitting, based on the second information, a first data to the second UPF.
  10. 　　The method according to claim 9, wherein
    　　for a first type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via a third UPF, and
    　　for a second type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via the second UPF.
  11. 　　A first user plane function (UPF) related to a first data network connecting with a first application server, the first UPF comprising:
    　　one or more memories storing instructions; and
    　　one or more processors configured to process the instructions to control the first UPF to:
    　　receive, from a Session Management Function (SMF), a second message comprising second information indicating packet detection rule for a traffic between the first application server and a second application server connecting with a second data network related to a second UPF; and
    　　transmit, based on the second information, a first data to the second UPF.
  12. 　　The first UPF according to claim 11, wherein
    　　for a first type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via a third UPF, and
    　　for a second type mode, the packet detection rule for the traffic between the first application server and a second application server indicates that the first application server connects with the second application server via the second UPF.
PCT/JP2025/002647 2024-02-15 2025-01-28 Method, application server and user plane function Pending WO2025173532A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202411010542 2024-02-15
IN202411010542 2024-02-15

Publications (1)

Publication Number Publication Date
WO2025173532A1 true WO2025173532A1 (en) 2025-08-21

Family

ID=96772944

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2025/002647 Pending WO2025173532A1 (en) 2024-02-15 2025-01-28 Method, application server and user plane function

Country Status (1)

Country Link
WO (1) WO2025173532A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022170593A1 (en) * 2021-02-10 2022-08-18 Lenovo (Beijing) Limited Dns configuration provisioning
US20230308951A1 (en) * 2021-07-23 2023-09-28 Tencent Technology (Shenzhen) Company Limited Data processing method, network element device, and readable storage medium

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022170593A1 (en) * 2021-02-10 2022-08-18 Lenovo (Beijing) Limited Dns configuration provisioning
US20230308951A1 (en) * 2021-07-23 2023-09-28 Tencent Technology (Shenzhen) Company Limited Data processing method, network element device, and readable storage medium

Similar Documents

Publication Publication Date Title
WO2023032529A1 (en) METHOD OF COMMUNICATION APPARATUS, METHOD OF gNB-CU-CP APPARATUS, METHOD OF AMF APPARATUS, METHOD OF SMF APPARATUS, METHOD OF gNB-DU APPARATUS, METHOD OF UPF APPARATUS, COMMUNICATION APPARATUS, gNB-CU-CP APPARATUS, AMF APPARATUS, SMF APPARATUS, gNB-DU APPARATUS AND UPF APPARATUS
US20240323828A1 (en) Method of af apparatus, method of nef apparatus, method of udm apparatus, method of amf apparatus, method of ue, method of pcf apparatus, method of ran node, af apparatus, nef apparatus, udm apparatus, amf apparatus, ue, pcf apparatus and ran node
US20250016711A1 (en) Method of ue, method of geographically selected amf apparatus, ue, geographically selected amf apparatus, and method of communication terminal
JP7589841B2 (en) Method for network node and network node - Patents.com
WO2023286779A1 (en) Method performed by radio terminal and radio terminal
WO2022270386A1 (en) Method of first access and mobility management function (amf) apparatus, method of user equipment (ue), first access and mobility management function (amf) apparatus, and user equipment (ue)
US20240298248A1 (en) Core network node, network node, method for core network node and method for network node
WO2023182198A1 (en) Method for user plane function (upf) and upf
WO2023182199A1 (en) Method of user equipment (ue), ue, method of communication apparatus and communication apparatus
US20250063336A1 (en) Method of user equipment (ue), method of communication apparatus, ue and communication apparatus
WO2024248116A1 (en) Method of first communication apparatus, first communication apparatus, method of edge node, method of first core network node, method of first edge node, edge node, first core network node and first edge node
WO2024162428A1 (en) Method of communication apparatus, method of user equipment (ue), communication apparatus and ue
WO2023145527A1 (en) Method of communication apparatus, method of user equipment (ue), communication apparatus, and ue
WO2023002991A1 (en) Access and mobility management function (amf) device, user equipment (ue), method of amf device and method of ue
WO2025173532A1 (en) Method, application server and user plane function
WO2023182200A1 (en) Method of communication apparatus, method of user equipment (ue), communication apparatus and ue
WO2024185489A1 (en) User equipment, first access and mobility management function, unified data management, and method thereof
WO2023238806A1 (en) Method of first communication apparatus, method of communication apparatus, first communication apparatus and communication apparatus
WO2025018238A1 (en) Method of first communication apparatus, method of user equipment (ue), first communication apparatus and ue
WO2024225050A1 (en) Method of remote user equipment (ue), method of first communication apparatus, remote ue and first communication apparatus
WO2024117117A1 (en) Method performed by first core network node, method of user equipment, first core network node, and user equipment
WO2025069793A1 (en) Method of user equipment (ue), method of access and mobility management function (amf), ue, and amf
WO2025069797A1 (en) Method of user equipment (ue), method of access and mobility management function (amf), ue, and amf

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25754858

Country of ref document: EP

Kind code of ref document: A1