[go: up one dir, main page]

WO2025173532A1 - Procédé, serveur d'application et fonction de plan utilisateur - Google Patents

Procédé, serveur d'application et fonction de plan utilisateur

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
English (en)
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/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
    • 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

Un aspect de la présente divulgation comprend un réseau central qui sélectionne une UPF proche de l'UE et transmet un trafic pour permettre l'accès local à un réseau de données et entre des réseaux de données par l'intermédiaire d'interfaces N6 selon les règles de direction de trafic fournies à l'UPF.
PCT/JP2025/002647 2024-02-15 2025-01-28 Procédé, serveur d'application et fonction de plan utilisateur Pending WO2025173532A1 (fr)

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 (fr) 2025-08-21

Family

ID=96772944

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2025/002647 Pending WO2025173532A1 (fr) 2024-02-15 2025-01-28 Procédé, serveur d'application et fonction de plan utilisateur

Country Status (1)

Country Link
WO (1) WO2025173532A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022170593A1 (fr) * 2021-02-10 2022-08-18 Lenovo (Beijing) Limited Fourniture de configuration dns
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 (fr) * 2021-02-10 2022-08-18 Lenovo (Beijing) Limited Fourniture de configuration dns
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 (fr) Procédé d'appareil de communication, procédé de gnb-cu-cp, procédé d'appareil amf, procédé d'appareil smf, procédé d'appareil gnb-du, procédé d'appareil upf, appareil de communication, appareil gnb-cu-cp, appareil amf, appareil smf, appareil gnb du et appareil upf
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 (ja) ネットワークノードの方法およびネットワークノード
WO2023286779A1 (fr) Procédé exécuté par un terminal radio, et terminal radio
WO2022270386A1 (fr) Procédé de premier appareil à fonction de gestion d'accès et de mobilité (amf), procédé d'équipement utilisateur (ue), premier appareil à fonction de gestion d'accès et de mobilité (amf) et équipement utilisateur (ue)
US20240298248A1 (en) Core network node, network node, method for core network node and method for network node
WO2023182198A1 (fr) Procédé pour fonction de plan utilisateur (upf) et upf
WO2023182199A1 (fr) Procédé d'équipement utilisateur (eu), procédé d'appareil de communication et appareil de communication
US20250063336A1 (en) Method of user equipment (ue), method of communication apparatus, ue and communication apparatus
WO2024248116A1 (fr) Procédé d'un premier appareil de communication, premier appareil de communication, procédé de nœud périphérique, procédé d'un premier nœud de réseau central, procédé d'un premier nœud périphérique, nœud périphérique, premier nœud de réseau central et premier nœud périphérique
WO2024162428A1 (fr) Procédé d'appareil de communication, procédé d'équipement utilisateur (ue), appareil de communication et ue
WO2023145527A1 (fr) Procédé d'appareil de communication, procédé d'équipement utilisateur (ue), appareil de communication et ue
WO2023002991A1 (fr) Dispositif à fonction de gestion d'accès et de mobilité (amf), équipement utilisateur (ue), procédé de dispositif amf et procédé d'ue
WO2025173532A1 (fr) Procédé, serveur d'application et fonction de plan utilisateur
WO2023182200A1 (fr) Procédé d'appareil de communication, procédé d'équipement utilisateur (ue), appareil de communication et ue
WO2024185489A1 (fr) Équipement utilisateur, première fonction de gestion d'accès et de mobilité, gestion de données unifiée et procédé associé
WO2023238806A1 (fr) Appareil de communication et procédé associé, premier appareil de communication et procédé associé
WO2025018238A1 (fr) Procédé de premier appareil de communication, procédé d'équipement utilisateur (ue), premier appareil de communication et ue
WO2024225050A1 (fr) Procédé d'équipement utilisateur (ue) distant, procédé de premier appareil de communication, ue distant et premier appareil de communication
WO2024117117A1 (fr) Procédé exécuté par un premier nœud de réseau central, procédé d'équipement utilisateur, premier nœud de réseau central et équipement utilisateur
WO2025069793A1 (fr) Procédé d'équipement utilisateur (ue), procédé de fonction de gestion d'accès et de mobilité (amf), ue et amf
WO2025069797A1 (fr) Procédé d'équipement utilisateur (ue), procédé de fonction de gestion d'accès et de mobilité (amf), ue et 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