[go: up one dir, main page]

WO2025214283A1 - Procédé et appareil de détermination d'un nœud de réseau - Google Patents

Procédé et appareil de détermination d'un nœud de réseau

Info

Publication number
WO2025214283A1
WO2025214283A1 PCT/CN2025/087460 CN2025087460W WO2025214283A1 WO 2025214283 A1 WO2025214283 A1 WO 2025214283A1 CN 2025087460 W CN2025087460 W CN 2025087460W WO 2025214283 A1 WO2025214283 A1 WO 2025214283A1
Authority
WO
WIPO (PCT)
Prior art keywords
tunnel
node
network node
eas
tunnel information
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/CN2025/087460
Other languages
English (en)
Inventor
Wenliang Xu
Attila MIHÁLY
Thorsten Lohmar
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025214283A1 publication Critical patent/WO2025214283A1/fr
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
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for determining a network node.
  • Tunneling may work by wrapping data in encapsulated packets that look like normal traffic on a network. Upon arriving at their destination, the packets are de-capsulated.
  • VPNs virtual private networks
  • GRE Generic Routing Encapsulation
  • VXLAN Virtual Extensible Local Area Network
  • OpenVPN Generic Network Virtualization Encapsulation
  • Geneve Generic Network Virtualization Encapsulation
  • IP Point-to-Point Tunneling Protocol
  • L2TP Layer 2 Tunneling Protocol
  • IPsec Internet Protocol Security
  • SSL Secure Sockets Layer
  • TLS Transport Layer Security
  • the current discovery mechanism for a network node does not consider the tunnel information.
  • Edge computing may be supported.
  • Edge computing may enable operator and 3rd party services to be hosted close to a terminal device's access point of attachment, so as to achieve an efficient service delivery through a reduced end-to-end latency and load on a transport network.
  • the current discovery mechanism for an edge network node such as Edge Enabler Server (EES) or Edge Application Server (EAS) does not consider the tunnel use case such as VPN, software-defined networking in a wide area network (SD-WAN) , N6 tunnel (e.g. L2TP as described in 3GPP TS 23.501 V18.4.0 and TS 23.502 V18.4.0) in protocol data unit (PDU) Session Anchor (PSA) user plane function (UPF) .
  • PDU protocol data unit
  • PSA Session Anchor
  • UPF user plane function
  • the terminal device location may not be accurate information to determine a network node such as EES/EAS in a network such as edge network because using terminal device location in network node (such as EES/EAS) determination may create a tromboning for application traffic. For example, even though a determined network node (such as EES/EAS) is close to a terminal device location, the traffic tromboning may happen if using terminal device location as criteria to determine the network node.
  • a network node such as EES/EAS
  • an improved solution for tunnel service may be desirable.
  • a method performed by a first network node may comprise obtaining tunnel information of a tunnel and determining a second network node based on the tunnel information.
  • obtaining the tunnel information may comprise at least one of receiving the tunnel information from a terminal device, or receiving the tunnel information from a third network node.
  • the first network node may comprise at least one of an edge configuration node or an edge enabler node
  • the second network node may comprise at least one of an edge enabler node or an edge application node.
  • determining a second network node based on the tunnel information may comprise determining the second network node which is topologically close to a tunnel server of the tunnel.
  • the third network node may comprise at least one of a user plane node, a session management node, a network exposure node, an edge application node, or an edge enabler node.
  • the terminal device may comprise an edge enabler client.
  • a method performed by a terminal device may comprise obtaining tunnel information of a tunnel and sending the tunnel information to a first network node.
  • the tunnel information may be used to determine a second network node.
  • the first network node may comprise at least one of an edge configuration node or an edge enabler node.
  • the second network node may comprise at least one of an edge enabler node or an edge application node.
  • a first network node may comprise a processor and a memory coupled to the processor. Said memory may contain instructions executable by said processor. The first network node is operative to obtain tunnel information of a tunnel and determine a second network node based on the tunnel information.
  • the first network node may be operative to receive the tunnel information from a terminal device, or from a third network node when obtaining the tunnel information.
  • the first network node may be operative to perform any of the methods according to the first aspect of the disclosure.
  • a terminal device may comprise a processor and a memory coupled to the processor. Said memory may contain instructions executable by said processor. The terminal device may be operative to obtain tunnel information of a tunnel and send the tunnel information to a first network node. The tunnel information is used to determine a second network node.
  • the terminal device may be operative to perform any of the methods according to the second aspect of the disclosure.
  • a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform any of the methods according to any one of the first or second aspect.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform any of the methods according to any one of the first or second aspect.
  • Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows.
  • the proposed solution can solve the traffic tromboning problem for application traffic by considering tunnel information.
  • the network node discovery procedure (such as EES discovery procedure and EAS discovery procedure) may be enhanced with considering tunnel information, e.g. determining or discovering a network node which is topologically close to a tunnel server.
  • it can improve the service continuity scenarios as described in clause 8.8.2 of 3GPP TS 23.558 V19.1.0.
  • it can provide edge computing support when tunnel service is used between the terminal device and a data network.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG. 1a illustrates the reference point representation of the architecture for edge enabling applications
  • FIG. 1b schematically shows a high level architecture in a 5G network according to an embodiment of the present disclosure
  • FIG. 1c schematically shows system architecture in a 4G network according to an embodiment of the present disclosure
  • FIG. 2a shows a flowchart of service provisioning procedure based on request/response model
  • FIG. 2b shows a flowchart of EAS discovery procedure
  • FIGs. 3a, 3b, 4, 5, 6a, 6b and 6c shows flowcharts of methods according to embodiments of the present disclosure
  • FIG. 7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • FIG. 8 shows an example of traffic tromboning
  • FIG. 9 shows an example of E2E tunnel
  • FIG. 10 shows an example of N6 tunnel.
  • the term “network” refers to a network following any suitable communication standards such as new radio (NR) , long term evolution (LTE) , LTE-Advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , Code Division Multiple Access (CDMA) , Time Division Multiple Address (TDMA) , Frequency Division Multiple Access (FDMA) , Orthogonal Frequency-Division Multiple Access (OFDMA) , Single carrier frequency division multiple access (SC-FDMA) and other wireless networks.
  • NR new radio
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Address
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single carrier frequency division multiple access
  • a CDMA network may implement a radio
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • Ad-hoc network wireless sensor network
  • the terms “network” and “system” can be used interchangeably.
  • the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP.
  • the communication protocols may comprise the first generation (1G) , 2G
  • network node or “network node” refers to any suitable network function (NF) which can be implemented in a network element (physical or virtual) of a communication network.
  • NF network function
  • the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the 5G system may comprise a plurality of NFs such as AMF (Access and mobility Function) , SMF (Session Management Function) , AUSF (Authentication Service Function) , UDM (Unified Data Management) , PCF (Policy Control Function) , AF (Application Function) , NEF (Network Exposure Function) , UPF (User plane Function) and NRF (Network Repository Function) , RAN (radio access network) , SCP (service communication proxy) , NWDAF (network data analytics function) , NSSF (Network Slice Selection Function) , NSSAAF (Network Slice-Specific Authentication and Authorization Function) , etc.
  • AMF Access and mobility Function
  • SMF Session Management Function
  • AUSF Authentication Service Function
  • UDM Unified Data Management
  • PCF Policy Control Function
  • AF Application Function
  • NEF Network Exposure Function
  • UPF User plane Function
  • NRF Network Repository Function
  • RAN radio access network
  • the 4G system may include MME (Mobile Management Entity) , HSS (home subscriber server) , Policy and Charging Rules Function (PCRF) , Packet Data Network Gateway (PGW) , PGW control plane (PGW-C) , Serving gateway (SGW) , SGW control plane (SGW-C) , E-UTRAN Node B (eNB) , etc.
  • MME Mobile Management Entity
  • HSS home subscriber server
  • PCRF Policy and Charging Rules Function
  • PGW Packet Data Network Gateway
  • PGW-C PGW control plane
  • SGW Serving gateway
  • SGW-C SGW control plane
  • the network function may comprise different types of NFs for example depending on a specific network.
  • terminal device refers to any end device that can access a communication network and receive services therefrom.
  • the terminal device refers to a mobile terminal, user equipment (UE) , or other suitable devices.
  • the UE may be, for example, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA) , a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like.
  • a portable computer an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance
  • a mobile phone a cellular phone, a smart phone, a voice over IP (VoIP) phone
  • a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP (3rd Generation Partnership Project) , such as 3GPP’ LTE standard or NR standard.
  • 3GPP 3rd Generation Partnership Project
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • references in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the phrase “at least one of A and B” or “at least one of A or B” should be understood to mean “only A, only B, or both A and B. ”
  • the phrase “A and/or B” should be understood to mean “only A, only B, or both A and B” .
  • a plurality of followed by a conjunctive list of enumerated items (e.g., “A and B” , “A, B, and C” ) is intended to mean “multiple items, with each item selected from the list consisting of” the enumerated items.
  • “a plurality of A and B” is intended to mean any of the following: more than one A; more than one B; or at least one A and at least one B.
  • Edge computing is a concept that enables services to be hosted close to the service consumers and provides benefits such as efficient service delivery with significant reduction in end-to-end latency and decreased load on the transport network.
  • the benefits of edge computing will strengthen the promise of 5G (fifth generation) and expand the prospects for several new and enhanced use cases, including virtual and augmented reality, Internet of Things (IoT) , Industrial IoT, autonomous driving, real-time multiplayer gaming, etc.
  • IoT Internet of Things
  • Industrial IoT autonomous driving
  • real-time multiplayer gaming etc.
  • SA 3GPP Technical Specification Group Service and System Aspects
  • EDGEAPP 3GPP Technical Specification Group Service and System Aspects
  • the objective of the work may be to define an enabling layer to facilitate communication between the Application Clients (AC) running on the UE and the Edge Application Servers (EAS) deployed on the Edge Data Network (EDN) .
  • This may include aspects of service provisioning and EAS discovery.
  • the work aims to provide support services such as application context transfer between EASs for service continuity, service enablement and capability exposure Application Programming Interfaces (APIs) towards the EAS.
  • APIs Application Programming Interfaces
  • the normative specification for EDGEAPP is written in e.g. 3GPP TS 23.558 V19.1.0. In 3GPP release 18, more functions are added, e.g., application roaming, edge computing federation, service continuity between edge and cloud.
  • 3GPP TS 23.558 V19.1.0 specifies application layer architecture, procedures and information flows necessary for enabling edge applications over 3GPP networks. It includes architectural requirements for enabling edge applications, application layer architecture fulfilling the architecture requirements and procedures to enable the deployment of edge applications.
  • a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device.
  • the communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and/or use of the services provided by, or via, the communication system.
  • FIG. 1a illustrates the reference point representation of the architecture for edge enabling applications.
  • FIG. 1a is same as Figure 6.2-4 of 3GPP TS 23.558 V19.1.0.
  • the Edge Data Network is a local data network.
  • EAS EAS
  • EES EES
  • the Edge Configuration Server provides configurations related to the EES, including details of the EDN hosting the EES.
  • the UE contains Application Client (s) (ACs) and the Edge Enabler Client (EEC) .
  • the EAS (s) , the EES (s) and the ECS may interact with the 3GPP core network.
  • SEAL Service Enabler Architecture Layer for Verticals
  • EDGE-1 enables interactions between the EES and the EEC. It supports:
  • EDGE-4 reference point enables interactions between the ECS and the EEC. It supports:
  • FIG. 1b schematically shows a high level architecture in a 5G network according to an embodiment of the present disclosure.
  • the architecture of FIG. 1b may be similar to Figure 4.2.3-1 of 3GPP TS 23.501 V18.4.0, the disclosure of which is incorporated by reference herein in its entirety.
  • the system architecture of FIG. 1b may be similar to Figure 4.2.3-1 of 3GPP TS 23.501 V18.4.0, the disclosure of which is incorporated by reference herein in its entirety.
  • NFs network functions
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Service Function
  • UDM Unified Data Management
  • PCF Policy Control Function
  • AF Application Function
  • NEF Network Exposure Function
  • UPF User plane Function
  • NRF Network Repository Function
  • RCF service communication proxy
  • SCP Service communication proxy
  • NSSF Network Slice Selection Function
  • NSSAAF Network Slice Selection Function
  • EASDF Edge Application Server Discovery Function
  • NSACF network slice Admission Control Function
  • the exemplary system architecture also contains the service-based interfaces such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf, Neasdf, Nnssf, Nnwdaf and Nsmf exhibited by NFs such as the NRF, the NEF, the AUSF, the UDM, the PCF, the AMF, the NSACF, the EASDF, the NSSF, the NWDAF and the SMF.
  • FIG. 1b also shows some reference points such as N1, N2, N3, N4, N6 and N9, which can support the interactions between NF services in the NFs. For example, these reference points may be realized through corresponding NF service-based interfaces and by specifying some NF service consumers and providers as well as their interactions in order to perform a particular system procedure.
  • Various NFs shown in FIG. 1b may be responsible for functions such as session management, mobility management, authentication, security, etc.
  • the AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R) AN, SCP, NSACF, NSSAAF, EASDF may include the functionality for example as defined in clause 6.2 of 3GPP TS 23.501 V18.4.0.
  • FIG. 1c schematically shows system architecture in a 4G network according to an embodiment of the present disclosure, which is the same as Figure 4.2-1a of 3GPP TS 23.682 V18.0.0, the disclosure of which is incorporated by reference herein in its entirety.
  • the system architecture of FIG. 1c schematically shows system architecture in a 4G network according to an embodiment of the present disclosure, which is the same as Figure 4.2-1a of 3GPP TS 23.682 V18.0.0, the disclosure of which is incorporated by reference herein in its entirety.
  • SCS Services Capability Server
  • AS Application Server
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber System
  • UE User Equipment
  • RAN Radio Access Network
  • SGSN Serving GPRS (General Packet Radio Service) Support Node)
  • MME Mobile Switching Centre
  • S-GW Serving Gateway
  • GGSN/P-GW Gateway GPRS Support Node/PDN (Packet Data Network) Gateway
  • MTC-IWF Machine Type Communications-InterWorking Function
  • CDF/CGF Charging Data Function/Charging Gateway Function
  • MTC-AAA Mobileachine Type Communications-authentication, authorization and accounting
  • SMS-SC/GMSC/IWMSC Short Message Service-Service Centre/Gateway MSC/InterWorking MSC
  • IP-SM-GW Internet protocol Short Message Gateway
  • the exemplary system architecture also contains various reference points, such as Tsms, Tsp, T4, T6a, T6b, T8, S6m, S6n, S6t, SGs, Gi/SGi, Rf/Ga, Gd, SGd, E, etc.
  • the network elements and reference points as shown in FIG. 1c may be same as the corresponding network elements and reference points as described in 3GPP TS 23.682 V18.0.0.
  • FIG. 2a shows a flowchart of service provisioning procedure based on request/response model.
  • FIG. 2a is same as Figure 8.3.3.2.2-1 of 3GPP TS 23.558 V19.1.0.
  • Step 1 The EEC may send a service provisioning request to the ECS.
  • Step 2 Upon receiving the request, the ECS may process the request.
  • Step 3 The ECS may respond to the EEC's request with a service provisioning response.
  • steps 1-3 of FIG. 2a can be found in clause 8.3.3.2.2 of 3GPP TS 23.558 V19.1.0, the detailed description is omitted here for brevity.
  • EEC can also be notified with service provisioning information change in the subscribe-notify model as described in clause 8.3.3.2.3 of 3GPP TS 23.558 V19.1.0.
  • the EEC does not send the tunnel information to ECS.
  • ECS cannot obtain the tunnel information.
  • the EES discovery mechanism does not consider the tunnel use case. Therefore it may create a tromboning for application traffic.
  • FIG. 2b shows a flowchart of EAS discovery procedure.
  • FIG. 2b is same as Figure 8.5.2.2-1 of 3GPP TS 23.558 V19.1.0.
  • Step 1 The EEC may send an EAS discovery request to the EES.
  • Step 2 Upon receiving the request from the EEC, the EES checks if the EEC is authorized to discover the requested EAS (s) .
  • Step 3 The EES sends an EAS discovery response to the EEC.
  • steps 1-3 of FIG. 2b can be found in clause 8.5.2.2 of 3GPP TS 23.558 V19.1.0, the detailed description is omitted here for brevity.
  • EEC can also be notified with EAS information change in the subscribe-notify model as described in clause 8.5.2.3 of 3GPP TS 23.558 V19.1.0.
  • the EEC does not send the tunnel information to EES.
  • EES cannot obtain the tunnel information.
  • the EAS discovery mechanism does not consider the tunnel use case. Therefore it may create a tromboning for application traffic.
  • FIG. 3a shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules or circuits for accomplishing various parts of the method 300 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.
  • the first network node may obtain tunnel information of a tunnel.
  • the first network node may communicate with any suitable network.
  • the first network node may communicate with the underlying 3GPP networks using the respective 3GPP interfaces specified by the 3GPP network.
  • the first network node may communicate with Evolved Packet System (EPS) , a 5GS, or a sixth generation system (6GS) as defined by 3GPP.
  • EPS Evolved Packet System
  • 5GS 5GS
  • 6GS sixth generation system
  • the first network node may be any suitable node, device, function, or entity that can implement any suitable function.
  • the first network node may be any suitable network node as defined in the 3GPP network such as EPS, 5GS or 6GS.
  • the first network node may comprise an edge network node as defined in 3GPP TS 23.558 V19.1.0, such as EES, ECS, EAS, etc.
  • the tunnel may be any suitable tunnel and the present disclosure has no limit on it.
  • the tunnel may be any suitable tunnel as defined in the 3GPP network such as EPS, 5GS or 6GS.
  • the tunnel may be any suitable tunnel as described in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0 and 3GPP TS 23.502 V18.4.0.
  • the tunnel may comprise at least one of a tunnel between a terminal device and a tunnel server or a tunnel between a network node and a tunnel server.
  • the tunnel server may be a network node or a server running any tunneling protocol such as VPN, GRE, VXLAN, OpenVPN, Geneve, PPTP, IP-in-IP, L2TP, IPsec, SSL, TLS, etc.
  • tunneling protocol such as VPN, GRE, VXLAN, OpenVPN, Geneve, PPTP, IP-in-IP, L2TP, IPsec, SSL, TLS, etc.
  • the network node may be any suitable node, device, function, or entity that can implement any suitable function.
  • the network node may be any suitable network node as defined in the 3GPP network such as EPS, 5GS or 6GS.
  • the network node may comprise the network node as described in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0, 3GPP TS 23.502 V18.4.0, or 3GPP TS 23.682 V18.0.0.
  • the tunnel may be used in terminal device communication with a network such as EDN.
  • a network such as EDN.
  • the tunnel may be used in any suitable part of a path between the terminal device and the application server or the network node.
  • the tunnel server may be located in any suitable location of the path between the terminal device and the application server or the network node.
  • the tunnel may be an end to end (E2E) tunnel.
  • E2E end to end
  • an E2E tunnel can be established from a terminal device to a tunnel server.
  • the application traffic may be carried in the tunnel.
  • the tunnel between the network node and the tunnel server may comprise at least one of a N6 tunnel or a SGi tunnel.
  • N6 tunnel may be established (for instance, see 3GPP TS 23.502 V18.4.0, clause 4.3.2.4 for L2TP support) .
  • N6 is a reference point between the UPF and a Data Network.
  • EPC Evolved Packet Core
  • SGi tunnel may be used in PGW user plane (PGW-U) , e.g., see 3GPP TS 29.061 V18.1.0, clause. 11.2.1.7 for Support L2TP for Control and User Plane Separation (CUPS) across SGi.
  • PGW-U PGW user plane
  • CUPS Control and User Plane Separation
  • SGi is a reference point between the EPC based Public Land Mobile Network (PLMN) and the packet data network.
  • PLMN Public Land Mobile Network
  • the tunnel information may comprise any suitable information related to the tunnel.
  • the tunnel information may comprise information which can be used to determine or discover a network node (such as EES or EAS) which may be topologically close to a tunnel server of the tunnel.
  • the tunnel information may comprise location information of the tunnel server.
  • the tunnel information may comprise information which can be used to determine the location information of the tunnel server.
  • the tunnel information may comprise at least one of a service provider identifier (ID) , a tunnel identifier, or an endpoint address of a tunnel server.
  • ID service provider identifier
  • tunnel identifier an endpoint address of a tunnel server.
  • the service provider ID may identify a tunnel service provider.
  • the tunnel ID may identify a tunnel.
  • the endpoint address of the tunnel server may be any suitable endpoint address such as an IP address or a Fully Qualified Domain Name (FQDN) for the tunnel server.
  • the tunnel information may be used to determine a location of the tunnel server.
  • the first network node may obtain the tunnel information of the tunnel in various ways and the present disclosure has no limit on it.
  • the first network node may send a request to a network node or a terminal device or the tunnel server and receive a response comprising the tunnel information of the tunnel.
  • the network node or the terminal device or the tunnel server may send a message comprising the tunnel information of the tunnel to the first network node.
  • the first network node may send a subscription request to the network node or the terminal device or the tunnel server to subscribe a notification of the tunnel information of the tunnel.
  • the first network node may receive the tunnel information from a terminal device. For example, if the terminal device knows the tunnel information, it may send the tunnel information to the first network node.
  • the terminal device may comprise an edge enabler client.
  • the edge enabler client may be similar to the EEC as defined in 3GPP TS 23.558 V19.1.0.
  • the first network node may receive the tunnel information from the edge enabler client.
  • the first network node may receive the tunnel information from a third network node. For example, if the third network node knows the tunnel information, it may send the tunnel information to the first network node.
  • the third network node may be any suitable node, device, function, or entity that can implement any suitable function.
  • the third network node may be any suitable network node as defined in the 3GPP network such as EPS, 5GS or 6GS.
  • the third network node may comprise any suitable network node as defined in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0, 3GPP TS 23.502 V18.4.0, or 3GPP TS 23.682 V18.0.0.
  • the third network node may comprise any suitable edge network node as defined in various 3GPP specifications such as 3GPP TS 23.558 V19.1.0.
  • the third network node may comprise at least one of a user plane node, a session management node, a network exposure node, an edge application node, or an edge enabler node.
  • the user plane node may be similar to the UPF or PGW-U as defined in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0, 3GPP TS 23.502 V18.4.0, or 3GPP TS 23.682 V18.0.0.
  • the session management node may be similar to the SMF or PGW-C as defined in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0, 3GPP TS 23.502 V18.4.0, or 3GPP TS 23.682 V18.0.0.
  • the network exposure node may be similar to the NEF or SCEF as defined in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0, 3GPP TS 23.502 V18.4.0, or 3GPP TS 23.682 V18.0.0.
  • the edge enabler node may be similar to the EES as defined in 3GPP TS 23.558 V19.1.0.
  • the edge application node may be similar to the EAS as defined in 3GPP TS 23.558 V19.1.0.
  • an edge network node such as ECS or EES or EAS may receive the tunnel information from 3GPP core network such as UPF, SMF, NEF, SCEF, PGW-U, PGW-C, etc.
  • the S-EES may receive the tunnel information from S-EAS.
  • the ECS may receive the tunnel information from EES.
  • the T-EES may receive the tunnel information from S-EES.
  • the S-EES or T-EES may receive the tunnel information from EEC.
  • the tunnel information may be received in at least one of a service provisioning request, an application context relocation request, or an edge application node discovery request.
  • the tunnel information may be received in any other suitable message sent from the terminal device to the first network node.
  • the service provisioning request may be similar to the service provisioning request as defined in 3GPP TS 23.558 V19.1.0.
  • the service provisioning request may be sent from EEC to ECS.
  • the application context relocation request may be similar to the ACR request as defined in 3GPP TS 23.558 V19.1.0.
  • the ACR request may be sent from the EEC to the S-EES or T-EES.
  • the edge application node discovery request may be similar to the EAS discovery request as defined in 3GPP TS 23.558 V19.1.0.
  • the EAS discovery request may be sent from EEC to EES.
  • the tunnel information may be received in at least one of a traffic influence notify message, an event exposure notify message, an edge application node discovery request, or an application context relocation request, a retrieve edge enabler node request.
  • the tunnel information may be received in any other suitable message sent from the third network node to the first network node.
  • the traffic influence notify message may be similar to the Nnef_TrafficInfluence_Notify message as defined in 3GPP TS 23.502 V18.4.0.
  • the Nnef_TrafficInfluence_Notify message may be sent by NEF to EES or ECS.
  • the event exposure notify message may be similar to the Nsmf_EventExposure_Notify as defined in 3GPP TS 23.502 V18.4.0.
  • the Nsmf_EventExposure_Notify may be sent by SMF to EES or ECS.
  • the edge application node discovery request may be similar to the EAS discovery request as defined in 3GPP TS 23.558 V19.1.0.
  • the EAS discovery request may be sent by S-EAS to S-EES.
  • the EAS discovery request may be sent by S-EES to T-EES.
  • the application context relocation request may be similar to the ACR request as defined in 3GPP TS 23.558 V19.1.0.
  • the ACR request may be sent by the S-EAS to the S-EES.
  • the retrieve edge enabler node request may be similar to the Retrieve EES request as defined in 3GPP TS 23.558 V19.1.0.
  • the source EES may send the Retrieve EES request to ECS.
  • the first network node may determine the second network node based on the tunnel information in various ways. In addition, the first network node may determine the second network node further based on any other information such as terminal device location, etc.
  • the S-EES provides also the tunnel information to the ECS. If tunnel information is received, the ECS additionally takes the tunnel information into consideration in identifying EES (s) . For instance, the IP address (es) of identified EES (s) needs to be topologically close to the IP address of the tunnel server.
  • FIG. 4 shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules or circuits for accomplishing various parts of the method 400 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the first network node may obtain tunnel information of a tunnel.
  • the tunnel information may be obtained according to embodiments of the present disclosure such as block 302 of FIG. 3a or any other ways described below.
  • the first network node may send the tunnel information to a fourth network node.
  • the fourth network node may communicate with any suitable network.
  • the fourth network node may communicate with the underlying 3GPP networks using the respective 3GPP interfaces specified by the 3GPP network.
  • the fourth network node may communicate with EPS, a 5GS, or a 6GS as defined by 3GPP.
  • the fourth network node may be any suitable node, device, function, or entity that can implement any suitable function.
  • the fourth network node may be any suitable network node as defined in the 3GPP network such as EPS, 5GS or 6GS.
  • the fourth network node may comprise an edge network node as defined in 3GPP TS 23.558 V19.1.0, such as EAS, etc.
  • the first network node may comprise an edge enabler node.
  • the edge enabler node may be similar to the EES as defined in 3GPP TS 23.558 V19.1.0.
  • the EES may be an EES or a source EES.
  • the fourth network node may comprise an edge application node.
  • the edge application node may be similar to the EAS as defined in 3GPP TS 23.558 V19.1.0.
  • the EAS may be an EAS or a source EAS.
  • the tunnel information may be sent to the fourth network node in any suitable message.
  • the tunnel information may be sent to the fourth network node in an application context relocation management event notification.
  • the application context relocation management event notification may be similar to the ACR management event notification as defined in 3GPP TS 23.558 V19.1.0.
  • the EES sends ACR management event notification to the EAS.
  • the first network node may receive the tunnel information from a fifth network node.
  • the fifth network node may be any suitable node, device, function, or entity that can implement any suitable function.
  • the fifth network node may be any suitable network node as defined in the 3GPP network such as EPS, 5GS or 6GS.
  • the fifth network node may comprise a network node as defined in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0, 3GPP TS 23.502 V18.4.0, or 3GPP TS 23.682 V18.0.0.
  • the fifth network node may comprise at least one of a user plane node, a session management node or a network exposure node.
  • the user plane node may be similar to the UPF or PGW-U.
  • the session management node may be similar to the SMF or PGW-C.
  • the network exposure node may be similar to the NEF or SCEF.
  • the tunnel information may be received in at least one of a traffic influence notify message, or an event exposure notify message.
  • the traffic influence notify message may be similar to the Nnef_TrafficInfluence_Notify message.
  • the Nnef_TrafficInfluence_Notify message may be sent by NEF to EES.
  • the event exposure notify message may be similar to the Nsmf_EventExposure_Notify.
  • the Nsmf_EventExposure_Notify may be sent by SMF to EES.
  • the first network node may comprise an edge application node (such as EAS) or an edge enabler node (such as EES) .
  • EAS edge application node
  • EES edge enabler node
  • the fourth network node may comprise an edge enabler node (such as EES) or an edge configuration node (such as ECS) .
  • EES edge enabler node
  • ECS edge configuration node
  • the tunnel information may be sent to the fourth network node in at least one of an edge application node discovery request (e.g. EAS discovery request) , a retrieve edge enabler node request (e.g. retrieve EES request) , or an application context relocation request (e.g. ACR request) .
  • EAS discovery request e.g. EAS discovery request
  • retrieve edge enabler node request e.g. retrieve EES request
  • application context relocation request e.g. ACR request
  • S-EAS may send the edge application node discovery request comprising the tunnel information to the S-EES.
  • S-EES may send the edge application node discovery request comprising the tunnel information to the T-EES.
  • the S-EES may send the retrieve edge enabler node request comprising the tunnel information to the ECS.
  • the S-EAS may send the application context relocation request comprising the tunnel information to the S-EES.
  • the first network node may receive the tunnel information from a sixth network node.
  • the sixth network node may be any suitable node, device, function, or entity that can implement any suitable function.
  • the sixth network node may be any suitable network node as defined in the 3GPP network such as EPS, 5GS or 6GS.
  • the sixth network node may comprise a network node as defined in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0, 3GPP TS 23.502 V18.4.0, or 3GPP TS 23.682 V18.0.0.
  • the sixth network node may comprise an edge network node as defined in 3GPP TS 23.558 V19.1.0, such as EAS, etc.
  • the sixth network node may comprise at least one of a user plane node (e.g. UPF, PGW-U) , a session management node (e.g. SMF, PGW-C) , a network exposure node (e.g., NEF or SCEF) , an edge enabler node (e.g. EES) or an edge application node (e.g. EAS) .
  • a user plane node e.g. UPF, PGW-U
  • a session management node e.g. SMF, PGW-C
  • a network exposure node e.g., NEF or SCEF
  • an edge enabler node e.g. EES
  • EAS edge application node
  • the EAS or EES may receive the tunnel information from 3GPP core network node such as UPF, PGW-U, SMF, PGW-C, NEF, SCEF, etc.
  • the source EAS may receive the tunnel information from the source EES.
  • the tunnel information may be received from the sixth network node in at least one of a traffic influence notify message (e.g. Nnef_TrafficInfluence_Notify message) , an event exposure notify message (e.g. Nsmf_EventExposure_Notify) , an application context relocation management event notification or an edge application node discovery request (e.g. ACR request) .
  • a traffic influence notify message e.g. Nnef_TrafficInfluence_Notify message
  • an event exposure notify message e.g. Nsmf_EventExposure_Notify
  • an application context relocation management event notification e.g. ACR request
  • the EAS or EES may receive a traffic influence notify message comprising the tunnel information from SMF.
  • the EAS or EES may receive an event exposure notify message comprising the tunnel information from NEF.
  • the source EAS may receive an application context relocation management event notification comprising the tunnel information from the source EES.
  • the source EES may receive an edge application node discovery request comprising the tunnel information from the source EAS.
  • FIG. 5 shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules or circuits for accomplishing various parts of the method 500 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the first network node may obtain tunnel information of a tunnel.
  • the tunnel information may be obtained according to embodiments of the present disclosure.
  • the first network node may detect that that a tunnel server of the tunnel is changed or the tunnel is used.
  • the first network node may detect that that the tunnel server of the tunnel is changed or the tunnel is used.
  • the first network node may determine that application context relocation is required.
  • the first network node may send an application context relocation request to another network node.
  • the ACR request may be sent either from the S-EAS to the S-EES.
  • the first network node may be any suitable network node performing ACR detection as described in the ACR scenarios in clause 8.8.2 of 3GPP TS 23.558 V19.1.0.
  • FIG. 6a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a terminal device or communicatively coupled to the terminal device.
  • the apparatus may provide means or modules or circuits for accomplishing various parts of the method 600 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the terminal device may obtain tunnel information of a tunnel.
  • the terminal device may obtain the tunnel information of the tunnel in various ways. For example, if the tunnel is established between the terminal device and the tunnel server, the terminal device may obtain the tunnel information of the tunnel. Alternatively the terminal device may obtain the tunnel information of the tunnel (such as N6/SGi tunnel) from a network node such as 3GPP core network node such as SMF, UPF, NEF, SCEF, etc.
  • a network node such as 3GPP core network node such as SMF, UPF, NEF, SCEF, etc.
  • the tunnel information may be used to determine a second network node.
  • the second network node may comprise at least one of an edge enabler node or an edge application node.
  • the terminal device may obtain the tunnel information of the tunnel between the terminal device and the tunnel server.
  • the terminal device may comprise an edge enabler client.
  • the edge enabler client may perform any of the operations of the terminal device according to embodiments of the present disclosure.
  • the tunnel information may comprise at least one of a service provider identifier, a tunnel identifier, or an endpoint address of a tunnel server.
  • the tunnel may comprise a tunnel between the terminal device and a tunnel server.
  • FIG. 6b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a terminal device or communicatively coupled to the terminal device.
  • the apparatus may provide means or modules or circuits for accomplishing various parts of the method 610 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the terminal device may obtain tunnel information of a tunnel.
  • the tunnel information may be obtained according to embodiments of the present disclosure such as block 602 of FIG. 6a.
  • the terminal device may send the tunnel information to a first network node.
  • the first network node may comprise at least one of an edge configuration node or an edge enabler node.
  • the tunnel information may be sent in at least one of a service provisioning request, an application context relocation request, or an edge application node discovery request.
  • FIG. 6c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a terminal device or communicatively coupled to the terminal device.
  • the apparatus may provide means or modules or circuits for accomplishing various parts of the method 620 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the terminal device may obtain tunnel information of a tunnel.
  • the tunnel information may be obtained according to embodiments of the present disclosure such as block 602 of FIG. 6a.
  • the terminal device may detect that that a tunnel server of the tunnel is changed or the tunnel is used.
  • the first network node may detect that that the tunnel server of the tunnel is changed or the tunnel is used.
  • the terminal device may determine that application context relocation is required.
  • the terminal device may send an application context relocation request to an network node.
  • the ACR request may be sent either from the EEC to the S-EES or T-EES.
  • the terminal device may be EEC performing ACR detection as described in the ACR scenarios in clause 8.8.2 of 3GPP TS 23.558 V19.1.0.
  • the proposed solution may consider the tunnel endpoint as a factor in network node (e.g. EES/EAS) determination.
  • the tunnel endpoint may be considered by ECS and EES, correspondingly.
  • the tunnel endpoint may be offered by EEC or obtained from 3GPP core network.
  • the tunnel endpoint may be considered by ECS and EES, correspondingly.
  • Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows.
  • the proposed solution can solve the traffic tromboning problem for application traffic by considering tunnel information.
  • the network node discovery procedure (such as EES discovery procedure and EAS discovery procedure) may be enhanced with considering tunnel information, e.g. determining or discovering a network node which is topologically close to a tunnel server.
  • it can improve the service continuity scenarios as described in clause 8.8.2 of 3GPP TS 23.558 V19.1.0.
  • it can provide edge computing support when tunnel service is used between the terminal device and a data network.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG. 7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • the first network node or the terminal device described above may be implemented as or through the apparatus 700.
  • the apparatus 700 comprises at least one processor 721, such as a digital processor (DP) , and at least one memory (MEM) 722 coupled to the processor 721.
  • the apparatus 700 may further comprise a transmitter Tx and receiver Rx 723 coupled to the processor 721.
  • the MEM 722 stores a program (PROG) 724.
  • the PROG 724 may include instructions that, when executed on the associated processor 721, enable the apparatus 700 to operate in accordance with the embodiments of the present disclosure.
  • a combination of the at least one processor 721 and the at least one MEM 722 may form processing means 725 adapted to implement various embodiments of the present disclosure.
  • Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 721, software, firmware, hardware or in a combination thereof.
  • the MEM 722 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories, as non-limiting examples.
  • the processor 721 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • general purpose computers special purpose computers
  • microprocessors microprocessors
  • DSPs digital signal processors
  • processors based on multicore processor architecture, as non-limiting examples.
  • the memory 722 contains instructions executable by the processor 721, whereby the first network node operates according to any of the methods performed by the first network node as described above.
  • the memory 722 contains instructions executable by the processor 721, whereby the terminal device operates according to any of the methods performed by the terminal device as described above.
  • a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • the computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory) , a ROM (read only memory) , Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.
  • an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses) , firmware (one or more apparatuses) , software (one or more modules) , or combinations thereof.
  • firmware or software implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.
  • 3GPP TS 23.558 V19.1.0 may be amended as following. To be noted that , some parts remain unchanged are omitted and the parts changed are underlined. 3GPP TSG-SA WG6 Meeting #60 S6-24xxxx (revision of S6-24xxxx) For HELP on using this form: comprehensive instructions can be found at http: //www. 3gpp. org/Change-Requests. Proposed change affects: UICC apps ME Radio Access Network Core Network Additional discussions: In EDGEAPP, UE location is one factor being considered in EDN server discovery. When tunnel service is used in UE communication with DN, UE location is not accurate/sufficient information to determine EAS/EES in EDN. FIG. 8 shows an example of traffic tromboning.
  • FIG. 9 shows an example of E2E tunnel.
  • E2E tunnel Once a PDU session is established, an E2E tunnel can be established from UE to a tunnel server. The application traffic will be carried in the tunnel.
  • UE is assumed to have tunnel endpoint available, which may be configured by user.
  • L2/L3 tunnel e.g. L2TP, IPSec
  • the tunnel endpoint should be considered by ECS and EES, correspondingly.
  • L7 tunnel e.g. SEALDD
  • the tunnel server can be considered as an application service and existing function in cl.
  • N6 tunnel shows an example of N6 tunnel.
  • N6 tunnel may be established (for instance, see TS 23.502, cl.4.3.2.4 for L2TP support) .
  • the 5GC can expose the tunnel endpoint (e.g. L2TP server IP address or host name) to the AF, so that the EEL entities (EES, ECS) can take the obtained tunnel endpoint from core network into consideration in determining corresponding servers in service provisioning and EAS disovery procedure.
  • SGi tunnel may be used in PGW-U, e.g., see TS 29.061, cl. 11.2.1.7 for L2TP support over SGi.
  • change of the tunnel server should be considered when determining target EES/EAS. 8.3.3.2.2 Request-response model (Preconditions and Figure 8.3.3.2.2-1 are not changed, which are omitted here. ) 1.
  • the EEC sends a service provisioning request to the ECS.
  • the service provisioning request includes the security credentials of the EEC received during EEC authorization procedure and may include the UE identifier such as GPSI, connectivity information, UE location, EEC service continuity support and AC profile (s) information.
  • EEC may provide its desired ECSP identifier (s) in the service provisioning request based on EEC preference. If an e2e tunnel is used in the UE for the application, then the EEC provides also the tunnel information to the ECS. 2. Upon receiving the request, the ECS performs an authorization check to verify whether the EEC has authorization to perform the operation.
  • the ECS may utilize the capabilities (e.g. UE location) of the 3GPP core network as specified in clause 8.10.2.
  • the ECS may invoke the NEF monitoring event API as described in 3GPP TS 23.502 [43] and 3GPP TS 23.682 [17] to obtain the UE roaming status and serving PLMN identifier. If the UE is roaming, the ECS may use the serving PLMN identifier to determine the roaming partner ECS (i.e. V-ECS) information to be provided to the EEC in the service provisioning response. If the Prediction expiration time is provided then the ECS may determine whether to identify EES with the instantiable but not instantiated EAS based on the Prediction expiration time and predicted EAS deployment time information obtained from ADAES.
  • V-ECS roaming partner ECS
  • the ECS identifies the EES(s) based on the provided AC profile (s) and the UE location.
  • Whether and how the ECS can obtain the EAS deployment time is FFS (ECS’s operations in step 2 when Application group profile is provided in the request, and neither Application group profile nor AC profiles (s) are provided are not changed, which are omitted here. ) (ECS’s operations in step 2 when ECSP identifier (s) provided by the EEC are not changed, which are omitted here. )
  • the ECS also determines other information that needs to be provisioned, e.g.
  • ECS ECS identification of the EDN, EDN service area, EES endpoints. For the roaming and federation case, if ECS does not identify any suitable EES (s) based on EDN configuration available at the ECS and UE's location, the ECS determines a partner ECS that may satisfy the requirements. Based on ECSP policy, the ECS may use preconfigured or OAM configured information about the partner ECSs or ECS discovery via ECS-ER as specified in clause 8.17.2.3 or both. (ECS’s operations in step 2 related to ECSP policies are not changed, which are omitted here.
  • the ECS identifies all the EES(s) providing the same EAS bundle identifier. - If bundle EAS information includes a list of EASIDs, the ECS identifies the one or more EES which support all of the EASs within the same EDN based on the EDN information obtained in the EES profile. If the tunnel information is received, the ECS additionally takes the tunnel information into consideration in identifying EES (s) . If no tunnel information is received, the ECS checks whether N6/SGi tunnel is used. If N6/SGi tunnel (e.g.
  • the ECS additionally takes the obtained tunnel information from 3GPP core network into consideration in identifying EES (s) . For instance, the IP address (es) of identified EES (s) needs to be topologically close to the IP address of the tunnel server. 8.3.3.2.3.2 Subscribe (Preconditions, Figure 8.3.3.2.3.2-1 and operations in step 1 are not changed, which are omitted here) 2.
  • the ECS performs an authorization check to verify whether the EEC has authorization to perform the operation. If required, the ECS may utilize the capabilities (e.g. UE location or user plane management event notification service if available) of the 3GPP core network as specified in clause 8.10.2.
  • the ECS If the request is authorized, the ECS creates and stores the subscription for provisioning.
  • NOTE 3 The ECS can monitor the user plane path change for EDGE-1 traffic toward EES (s) by utilizing the user plane management event notification service specified in 3GPP TS 23.501 [2] . Based on target DNAI and/or target tunnel information reported from 5GC the ECS can notify more suitable EES (s) to the EEC.
  • 8.3.3.3.2 Service provisioning request Table 8.3.3.3.2-1 describes the information elements for service provisioning request from the EEC to the ECS.
  • Table 8.3.3.3.2-1 Service provisioning request 8.5.2.2 Request-response model (Preconditions and Figure 8.5.2.2-1are not changed, which are omitted here. ) 1.
  • the EEC sends an EAS discovery request to the EES.
  • the EAS discovery request includes the requestor identifier [EECID] along with the security credentials and may include EAS discovery filters, EEC service continuity support, and may also include UE location to retrieve information about particular EAS (s) or a category of EASs, e.g. gaming applications, or Edge Applications Server (s) available in certain service areas, e.g. available on a UE's predicted or expected route.
  • the request may include an EAS selection request indicator. If an e2e tunnel is used in the UE for the application, then the EEC provides also the tunnel information to the EES. 2.
  • the EES Upon receiving the request from the EEC, the EES checks if the EEC is authorized to discover the requested EAS (s) .
  • the authorization check may apply to an individual EAS, a category of EASs or to the EDN, i.e. to all the EASs. If UE's location information is not already available, the EES obtains the UE location by utilizing the capabilities of the 3GPP core network as specified in clause 8.10.3. If EAS discovery filters are provided by the EEC, but it does not contain Application group profile, the EES identifies the EAS (s) based on the provided EAS discovery filters and the UE location.
  • EES additionally takes the obtained tunnel information from 3GPP core network into consideration in identifying EAS (s) .
  • the IP address (es) of identified EAS (s) needs to be topologically close to the IP address of the tunnel server.
  • Table 8.5.3.2-1 describes information elements for the EAS discovery request.
  • Table 8.5.3.2-2 provides further detail about the EAS Discovery Filter information element.
  • the EEC may determine if the ACR is required by detecting that the UE moved or is predicted or expected to move outside the service area (see clause 7.3.3) .
  • the service area can be provided to the EEC by either the ECS during Service Provisioning or EES during EAS Discovery.
  • the EEC may determine that the ACR is required.
  • the EEC may determine that ACR is required if the UE is notified of the existence and availability of a new IPv6 prefix as specified in clause 4.3.5.3 of 3GPP TS 23.502 [3] .
  • the EEC may determine if the ACR is required by detecting that the e2e tunnel server used for application traffic is changed. 8.8.2.2 Initiation by EEC using regular EAS Discovery (the preconditions and Figure 8.8.2.2-1 are not changed, which are omitted here. ) Phase I: ACR Detection 1.
  • the EEC detects the UE location update as a result of a UE mobility event and is provided with the UE's new location as described in clause 8.8.1.1.
  • the EEC can also detect an expected or predicted UE location in the future as described in clause 8.8.1.1 . If a e2e tunnel is used in the UE for application, the EEC can also detect the tunnel server update as described in clause 8.8.1.1 .
  • NOTE 2 If the EEC is triggered by an external entity such as by a notification from the ECS, a list of new EESs (to be used as T-EESs) is provided by that notification and step 3 below is skipped.
  • Phase II ACR Decision (description on Phase II is not changed, which are omitted here.
  • Phase III ACR Execution 3.
  • the EEC performs Service Provisioning (as specified in clause 8.3) for all active applications that require ACR.
  • Service Provisioning procedure results in a list of T-EESs that are relevant to the supplied applications and the new location of the UE and/or new tunnel server used by the UE .
  • the Connectivity information and UE Location in the Service Provisioning procedure contains the expected Connectivity information and expected UE Location. If Service Provisioning results in no T-EES, and if ACR to CAS is supported, then the procedure for ACR with CAS applies as specified in clause 8.8.2A. 2.
  • step 4 to 11 are not changed, which are omitted here
  • 8.8.2.3 EEC executed ACR via S-EES (preconditions and Figure 8.8.2.3-1 are not changed, which are omitted here. )
  • Phase I ACR Detection 1.
  • the EEC detects that ACR may be required as described in clause 8.8.1.1.
  • the EEC may detect that ACR may be required for an expected or predicted UE location in the future as described in clause 8.8.1.1.
  • the EEC may also detect that ACR may be required for the tunnel server update as described in clause 8.8.1.1 . (description on Phase II, III and IV are not changed, which are omitted here.
  • the EEC or S-EAS may inform S-EES with ACID, and predicted/expected UE location or Expected AC Geographical Service Area in the ACR launching procedure.
  • the EEC may also detect a tunnel server update and inform the S-EES with the new tunnel information.
  • 8.8.2.6 EEC executed ACR via T-EES (Preconditions and Figure 8.8.2.6-1 are not changed, which are omitted here. ) Phase I: ACR Detection 1.
  • the EEC detects that ACR may be required as described in clause 8.8.1.1.
  • the EEC may detect that ACR may be required for an expected or predicted UE location in the future as described in clause 8.8.1.1.
  • the EEC may also detect that ACR may be required for the tunnel server update as described in clause 8.8.1.1. (Phase II to Phase IV are not changed, which are omitted here) 8.8.4.4
  • ACR request Table 8.8.4.4-1 describes information elements for the ACR request sent either from the EEC to the S-EES or T-EES, or by the S-EAS to the S-EES.
  • Table 8.8.4.4-1 ACR request 8.6.3.1
  • the EES exposes ACR management event notifications of one or more UEs to an EAS. EES also uses ACR management event notifications to inform the EAS of the need to start an ACT or cancel a previously started ACT.
  • ACR management event notifications exposed by the EES may rely on the NEF northbound API for monitoring event of user plane path management event.
  • This capability exposed by the EES supports: - "User plane path change” .
  • This event supports to detect user plane path change for the application traffic and report the corresponding notification with user plane path change to the EAS.
  • - "ACR monitoring” This event supports to detect user plane path change for the application traffic, discover the T-EAS (s) , and report the corresponding notification with the discovered T-EAS (s) .
  • -"ACR facilitation .
  • This event supports to detect user plane path change for the application traffic, make the decision for ACR, discover the T-EAS (s) , influence the traffic for the selected T-EAS and report the corresponding notification with the selected T-EAS.
  • the EES provided ACR management events related to user plane path change also support N6/SGi tunnel server change. Editor's Note: Coordination with SA2 is needed about how AF can obtain SGi tunnel server change information. - "ACT start/stop” . This event informs the EAS the need to start or stop an ACT towards or from another EAS for a particular UE. The "ACT start” can also inform the EAS of the ACR parameters. - "ACR Selection” .
  • This event informs the EAS about the selected ACR scenario list for each AC using the EAS.
  • 8.6.3.2.3 Notify Figure 8.6.3.2.3-1illustrates the notify operation between the EES and the EAS for continuous ACR management event notifications, the figure is not changed which is omitted here. 1.
  • the EES detects the ACR management event of a UE (e.g. receiving User plane path management event notification for a UE from the 3GPP core network) , or receiving ACR request from the EEC, or when the selected ACR scenario list for a particular AC changes. a.
  • the EES may cache the detected User plane path management event notification locally with timestamp as the latest information of the UE (s) and start the notification aggregation for a group of UEs.
  • the EES decides whether to aggregate and the aggregation period based on the analytics result received from the 3GPP Core Network, local policy and User Plane path management subscription information received from the EAS.
  • the EES determines to notify the user plane path management event notification information (e.g., DNAI, tunnel information) to the EASs which has subscribed for the "user plane path management" event.
  • the user plane path management event notification information e.g., DNAI, tunnel information
  • the EES checks whether any T-EAS is available as described in steps 2-4 of clause 8.8.3.2. If a T-EAS is available, the EES notifies the EAS with T-EAS endpoint; otherwise this event notification will not be sent. Also, when the EES receives the ACR request from the EEC, the EES decides to send the notification to the EAS. c. If "ACR facilitation" Event is subscribed, based on the detected user plane path change report sent from the 3GPP core network, the EES checks whether any T-EAS is available as described in steps 2-4 of clause 8.8.3.2.
  • the EES selects the T-EAS from the discovered EAS list and applies the AF traffic influence with the N6 routing information of the selected T-EAS in the 3GPP Core Network.
  • the EES also notifies the S-EAS with the selected T-EAS endpoint. d. If "ACT start/stop" event is subscribed, during the ACR launch if the EEC indicates the need to notify the EAS in the ACR request as described in clause 8.8.3.4, the EES shall send notification to the EAS to inform it about the need to start or stop the ACT to or from another EAS.
  • the EES may include a service continuity planning indication so that the EES will monitor UE location.
  • the notification message includes ACR identity (ACID, UE ID, S-EAS endpoint and T-EAS endpoint) .
  • ACR identity ACID, UE ID, S-EAS endpoint and T-EAS endpoint
  • the EES shall send notification to the EAS to update the selected ACR scenario list applicable for a particular AC (ACID, UE ID) if an update was received as described in clause 8.15.2.2. (steps 2 and 3 are not changed, which are omitted here. ) 8.8.3.2 Discover T-EAS
  • FIG. 27 illustrates the procedure for fetching T-EAS information. This procedure may be utilized by a S-EAS, which undertakes the transfer of application context information to a T-EAS directly, or can be invoked by the S-EES itself on deciding to execute ACR.
  • T-EAS discovery procedure also supports EAS retrieval which enables a S-EAS to obtain T-EAS (s) serving the application group so that the S-EAS can start communication with obtained EAS (s) for EAS synchronization.
  • the S-EAS sends the EAS discovery request to the S-EES or the S-EES decides to execute the ACR.
  • the EAS discovery request from the S-EAS includes the requestor identifier [EASID] along with the security credentials and includes EAS discovery filter matching its EAS profile.
  • the S-EAS provides the S-EES with the target DNAI .
  • target tunnel information is available at the S-EAS via User Plane Path change event, the S-EAS provides the S-EES with the target tunnel information .
  • the S-EAS also includes an EAS service continuity support indicator indicating that the S-EAS decided ACR according to clause 8.8.2.4 is to be used for the ACR.
  • the S-EAS includes the bundle ID and bundle type indicating the proxy bundle case to which the S-EAS belongs to.
  • the request may include prediction expiration time.
  • the EAS may send EAS discovery request with EAS ID, Application Group ID and EAS synchronization support, which indicates the request to obtain EAS (s) currently serving the Application Group ID with the requested EAS ID in order to perform EAS synchronization.
  • EAS EAS discovery request
  • Application Group ID EAS synchronization support
  • the trigger condition to invoke the Discover T-EAS API is up to application service logic, which is out of scope of this specification.
  • the S-EES either receive the target DNAI and/or target tunnel information for T-EES discovery from the step 1a or by the user plane management event notification from the core network. 2. If the request is received from the S-EAS, the S-EES checks whether the requesting EAS is authorized to perform the discovery operation.
  • the S-EES checks with the ECS-ER with the received EAS ID and Application Group ID and obtains a list of EAS (s) supporting EAS synchronization and serving the application group for the desired application service identified by the EAS ID as described in clause 8.20. Step 2 to step 4 are skipped. If the UE location is not known to the S-EES or provided by the S-EAS request, then the S-EES may interact with 3GPP core network to retrieve the UE location.
  • the S-EES checks if there exists a T-EAS information (registered or cached) that can satisfy the requesting EAS information, target DNAI, target tunnel information , additional query filters and the Expected AC Service KPIs and the Minimum required AC Service KPIs if received from the EEC during the EAS discovery or from the S-EAS in step 1.
  • the S-EES may collect Edge load performances from ADAES or OAM to find T-EAS (s) that satisfies the Expected AC service KPIs or the Minimum required AC Service KPIs.
  • the S-EES may determine the use of statistics or prediction for evaluating KPIs based on the situation of the T-EAS discovery. If target tunnel information is received, the S-EES additionally takes the target tunnel information into consideration in identifying T-EAS (s) . For instance, the IP address (es) of identified T-EAS (s) needs to be topologically close to the IP address of the target tunnel server . If the S-EES finds the T-EAS (s) in the cached or registered information, the flow either continues with step 5 for the S-EAS triggered discovery or stops for the S-EES decided ACR execution, else the S-EES retrieves the T-EES address from the ECS as specified in clause 8.8.3.3 and continues with step 3.
  • the EES may determine whether to identify the instantiable but not instantiated EAS as T-EAS based on Prediction expiration time and the predicted EAS deployment time information obtained from ADAES. Editor's Note: Whether and how the EES can obtain the EAS deployment time (e.g., from ADAES) is FFS. 3.
  • the S-EES invokes the EAS discovery request on the T-EES retrieved from the ECS.
  • the EAS discovery request includes the requestor identifier [EESID] along with the security credentials and includes EAS discovery filter.
  • the S-EES may include prediction expiration time, the Expected AC Service KPIs and the Minimum required AC Service KPIs if received from the EEC during the EAS discovery or from the S-EAS in step 1. If target tunnel information is available at the S-EES (e.g. received from S-EAS in step 1a or by the user plane management event notification from the core network) , the S-EES provides the T-EES with the target tunnel information. The S-EES also includes the EEC service continuity support indicator received from the EEC during EAS discovery.
  • step 1 the S-EES received an EAS service continuity support indicator from the S-EAS, then the S-EES includes this EAS service continuity support indicator and its own EES service continuity support indicator indicating the ACR scenarios supported by the EES. If in step 1 the S-EES decided to execute the ACR, the S-EES includes the EAS service continuity support indicator received from the S-EAS during EAS registration and includes an EES service continuity support indicator indicating that the S-EES executed ACR according to clause 8.8.2.5 is to be used for the ACR.
  • the T-EES may trigger the ECSP management system to instantiate the T-EAS that matches with EAS discovery filter IEs (e.g. ACID) as in clause 8.12. 4.
  • EAS discovery filter IEs e.g. ACID
  • the T-EES discovers the T-EAS (s) and responds with the discovered T-EAS information to the S-EES.
  • the T-EES utilizes the discovery filters (e.g. Expected AC Service KPIs and the Minimum required AC Service KPIs) and the indications which ACR scenarios are supported by the AC, the EEC, the T-EES and the S-EAS.
  • the T-EES may collect edge load analytics from ADAES (as specified in clause 8.8.2 of TS 23.436 [28] ) or performance data from OAM to find T-EAS (s) that satisfies the Expected AC service KPIs or the Minimum required AC Service KPIs.
  • ADAES as specified in clause 8.8.2 of TS 23.436 [28]
  • performance data from OAM to find T-EAS (s) that satisfies the Expected AC service KPIs or the Minimum required AC Service KPIs.
  • the T-EES may determine the use of statistics or prediction for evaluating KPIs based on the situation of the T-EAS discovery.
  • the S-EES may cache the T-EAS information. When the bundle EAS information (i.e.
  • the request message contains direct bundle EAS (s) information (i.e. list of EASID and direct bundle type) .
  • the S-EES receives the direct bundle T-EAS (s) information from each associated T-EES (s) .
  • T-EES (s) may belongs to same EDN.
  • the edge load analytics from ADAES can be either statistics or predictions on the T-EAS.
  • the statistical KPI value can be used for both normal ACR and service continuity planning.
  • the T-EES additionally takes the target tunnel information into consideration in identifying T-EAS (s) . For instance, the IP address (es) of identified T-EAS (s) needs to be topologically close to the IP address of the target tunnel server. 5.
  • the S-EES responds to the S-EAS with the discovered T-EAS Information. For responding S-EAS requesting EAS serving the application group, only EAS endpoint and EAS ID are included in EAS profile of Discovered EAS list. 8.8.3.3 Retrieve T-EES procedure (Preconditions and Figure 8.8.3.3.
  • the S-EES sends the Retrieve EES request (UE location information or UE identity, EASID of the S-EAS, bundle ID, bundle type (i.e. proxy bundle case) , target DNAI and UE connectivity information) to the ECS in order to identify the T-EES which has an EAS available to serve the given AC in the UE.
  • the Retrieve EES request includes application group id.
  • the request message may also contain the AC, EEC service continuity support information. If target tunnel information is available at the S-EES, then the S-EES provides also the tunnel information to the ECS. 2. If the request contains the UE identity (e.g.
  • the ECS interacts with 3GPP core network to retrieve the UE location.
  • the ECS determines T-EES (s) as per the parameters (e.g. EASID, target DNAI) in the request and the UE location information. If the request message contains the AC, EEC service continuity support information, then the ECS may identify the T-EES taking the AC, EEC, T-EES service continuity support into consideration. When the bundle ID and is provided and bundle type indicating the proxy bundle case then the ECS can identify the T-EES based on the bundle ID in the EES profile and in the request message to ensure T-EAS is able to invoke the required proxy bundle EAS (s) as the S-EAS does.
  • the ECS may determine whether to identify T-EES with the instantiable but not instantiated EAS based on Prediction expiration time and predicted EAS deployment time information obtained from ADAES. Editor's Note: Whether and how the ECS can obtain the EAS deployment time (e.g., from ADAES) is FFS. If no ECS-ER is available and when the Retrieve EES request includes application group id to the ECS then the request EES list retrieval is for the announcement of common EAS, ECS determines the list of EESs serving the EASs (with same EASID) for the Group ID included in the Retrieve EES request.
  • the ECS determines a partner ECS that may satisfy the requirements. Based on ECSP policy, the ECS may use preconfigured or OAM configured information about the partner ECSs or ECS discovery via ECS-ER as specified in clause 8.17.2.3 or both. If required by the ECSP policies, the ECS may use service provisioning information retrieval procedure as specified in clause 8.17.2.4 to obtain service provisioning information from the partner ECS.
  • the ECS identifies the one or more T-EES associated with the same EDN which support all of the EASs within the same EDN based on the EES EDN information obtained in the EES profile.
  • T-EES (s) may belongs to same EDN.
  • the ECS additionally takes the tunnel information into consideration in identifying EES (s) . For instance, the IP address (es) of identified EES(s) needs to be topologically close to the IP address of the tunnel server. 8.8.4.6 Retrieve EES request Table 8.8.4.6-1 describes the information elements to retrieve T-EES information from the ECS. Table 8.8.4.6-1: retrieve EES request

Landscapes

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

Abstract

Les modes de réalisation de la présente divulgation concernent un procédé et un appareil destinés à un service de tunnel. Un procédé exécuté par un premier nœud de réseau peut consister à obtenir des informations sur un tunnel. Le procédé peut consister à déterminer (314) un deuxième nœud de réseau sur la base des informations sur le tunnel ; L'obtention des informations sur le tunnel consiste à recevoir les informations sur le tunnel en provenance d'un dispositif terminal et/ou à recevoir les informations sur le tunnel en provenance d'un troisième nœud de réseau.
PCT/CN2025/087460 2024-04-07 2025-04-07 Procédé et appareil de détermination d'un nœud de réseau Pending WO2025214283A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2024/086428 2024-04-07
CN2024086428 2024-04-07

Publications (1)

Publication Number Publication Date
WO2025214283A1 true WO2025214283A1 (fr) 2025-10-16

Family

ID=95517039

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/087460 Pending WO2025214283A1 (fr) 2024-04-07 2025-04-07 Procédé et appareil de détermination d'un nœud de réseau

Country Status (1)

Country Link
WO (1) WO2025214283A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022179218A1 (fr) * 2021-02-24 2022-09-01 华为技术有限公司 Procédé et appareil de communication
US20230388395A1 (en) * 2020-09-29 2023-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Application function influence in application context relocation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230388395A1 (en) * 2020-09-29 2023-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Application function influence in application context relocation
WO2022179218A1 (fr) * 2021-02-24 2022-09-01 华为技术有限公司 Procédé et appareil de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3 Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture for enabling Edge Applications; (Release 19)", no. V19.1.0, 3 April 2024 (2024-04-03), pages 1 - 298, XP052598205, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/23_series/23.558/23558-j10.zip 23558-j10.docx> [retrieved on 20240403] *

Similar Documents

Publication Publication Date Title
US12003592B2 (en) Method and apparatus for service discovery
WO2020098245A1 (fr) Procédé et appareil de gestion de session
JP7589841B2 (ja) ネットワークノードの方法およびネットワークノード
US20240276300A1 (en) Method and apparatus for setting up session with required quality of service
CN112205015A (zh) 用于策略分发的方法、装置和计算机可读介质
CN116761134A (zh) 用于位置服务的方法和装置
US20240056906A1 (en) Method and apparatus for service continuity
KR20230048408A (ko) 사용자 평면 경로 관리를 위한 방법 및 장치
US20230370431A1 (en) Method and apparatus for security communication
WO2022199530A1 (fr) Procédé et appareil pour exposer des informations d&#39;adresse d&#39;équipement utilisateur
WO2022218343A1 (fr) Procédé et appareil de resélection de fonction de gestion de session
WO2022161276A1 (fr) Procédé et appareil de gestion de services de session
WO2025214283A1 (fr) Procédé et appareil de détermination d&#39;un nœud de réseau
WO2023145527A1 (fr) Procédé d&#39;appareil de communication, procédé d&#39;équipement utilisateur (ue), appareil de communication et ue
WO2023016400A1 (fr) Procédé et appareil de restauration de session
KR20250097890A (ko) 네트워크 기능 발견을 위한 방법 및 장치
WO2025214285A1 (fr) Procédé et appareil pour une continuité de service
WO2025092804A1 (fr) Procédé et appareil de vérification de disponibilité de tranche de réseau
WO2025092806A1 (fr) Procédé et appareil de vérification d&#39;état de ressource de tranche de réseau
US20250175925A1 (en) Method and apparatus for session management
US20250374174A1 (en) Method of communication apparatus and communication apparatus
WO2025173532A1 (fr) Procédé, serveur d&#39;application et fonction de plan utilisateur
WO2025066509A1 (fr) Procédé et appareil de facturation
WO2024230495A1 (fr) Procédé et appareil de rapport de règles de session
WO2025168065A1 (fr) Procédé et appareil de surveillance de qualité de service

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: 25720954

Country of ref document: EP

Kind code of ref document: A1