WO2018232253A1 - Fonction d'exposition de réseau - Google Patents

Fonction d'exposition de réseau Download PDF

Info

Publication number
WO2018232253A1
WO2018232253A1 PCT/US2018/037775 US2018037775W WO2018232253A1 WO 2018232253 A1 WO2018232253 A1 WO 2018232253A1 US 2018037775 W US2018037775 W US 2018037775W WO 2018232253 A1 WO2018232253 A1 WO 2018232253A1
Authority
WO
WIPO (PCT)
Prior art keywords
nef
network
user equipment
data
identifier
Prior art date
Application number
PCT/US2018/037775
Other languages
English (en)
Inventor
Michael F. Starsinic
Rocco Digirolamo
Mahmoud Watfa
Hongkun Li
Catalina Mihaela MLADIN
Original Assignee
Convida Wireless, Llc
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 Convida Wireless, Llc filed Critical Convida Wireless, Llc
Publication of WO2018232253A1 publication Critical patent/WO2018232253A1/fr

Links

Classifications

    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them

Definitions

  • a server may determine the identity of a network exposure function (NEF) associated with a user equipment (UE).
  • NEF network exposure function
  • UE user equipment
  • Standard registration methods may be enhanced to enable the network to provide the UE with information such as an NEF identifier, a UE external identifier, and a slice identifier.
  • the information may be provided automatically by the server, for example, or upon request from the UE.
  • UE applications and service layers may then use such information, e.g., by providing the NEF identifier or UE identifier, when registering with a server so that the server may identify and communicate with the associated NEF.
  • Figure 8 is a block diagram of an example Hierarchical NEF Architecture.
  • Figure 17 is a system diagram of an example communication network node, such as an M2M/IoT/WoT device, gateway, or server that may be used within the
  • Figure 22 is a system diagram of a second example RAN.
  • Figure 23 is a system diagram of a third example radio access network RAN.
  • 3GPP is defining a 5G mobile core network (MCN).
  • the architecture of the 5G network will rely on network function virtualization (NFV) techniques.
  • NFV network function virtualization
  • the MCN When the MCN is virtualized, the NEF that an Application Function (AF) uses to interface with the MCN may change over time, e.g., depending on what network slice the UE is connected to.
  • the MCN may be designed such that the compute logic and data storage parts of each Network Functions are separate logical entities. This type of design is well suited for allowing NFs to share data storage resources.
  • Figure 2 shows the 5G system architecture from TS 23.501 and shows that the NEF is a service within the 5G system.
  • the service based interface of the NEF is called Nnef Note that in 5G, the SCEF is called the NEF.
  • NEF also has reference points towards the NF's that it interacts with.
  • TS 23.501 has only named one of the NEF reference points; N19 is the name of the reference point between the NEF and SDSF.
  • the SCS/AS may provide the SCEF with configuration information for a UE or a group of UE's. For example, the SCS/AS may provide communication patterns, sleep cycles preferences, etc. The SCS/AS may also request to be notified when a UE becomes reachable, loses connectivity, has a change of IMSI/IMEI association, etc.
  • the configuration information and subscription requests are passed to the HSS and the HSS sends them to the MME. This approach creates a situation where a significant amount of configuration data and subscription requests must be routed through a central point (the HSS) and then to the serving node (MME). In the 5G core network, it would be better if information or requests from the SCS/AS were not all routed through a central repository such as the UDM.
  • UE context/state information can be provided to the Application Function via the NEF, without requiring the compute logic associated with the Network Function to send additional messages.
  • the NEF is part of a network slice, such that the AF does not need to be slice aware.
  • the NEF that is contacted is only part of one slice.
  • the procedure that is used by the UE to connect to a network slice is called the "UE General Registration" procedure as defined in section 4.2.2.2.2 of TS 23.502, Procedures for the 5G System; Stage 2. VO.2.0 and is shown in Figures 4-6.
  • this method may be updated to help the UE and SCS/AS identify the NEF.
  • step 3 of Figure 4 the (R)AN sends an N2 message to the AMF: (N2 parameters, Registration Request (Registration type, Subscriber Permanent Identifier or
  • the AMF may send the Registration Accept message to the UE: Registration Accept (Temporary User ID, Registration area. Mobility restrictions, PDU session status, NSSAI, Periodic registration update timer, NEF Identifiers).
  • the UE may expose the NEF identifier information to applications that use a Slice that is associated with the NEF identifier.
  • the UE OS may expose an API that provides an application with a list of services that can be obtained from a network slice.
  • the list may include one or more NEF identifiers.
  • the list may be provided to the application whenever the application connects to the slice, or by an API that allows an application to browse or check what slice(s) the UE is connected to.
  • a UE application obtains the NEF Identifier, it may provide it to an IoT Server. For example, it may be provided in a Service Layer registration message.
  • Figure 7 shows an example procedure of how a UE application may obtain an NEF identifier and provide it to an IoT Server.
  • the UE application calls an API that is used to obtain, from the UE OS, a list of slices that the UE is connected to, or is able to connect to.
  • the list in the response from the UE OS also includes what services are available in each slice.
  • the list may include an indication that an NEF is associated with a slice and the list may provide an NEF identifier.
  • the IoT Server may then contact the NEF to perform operations related to the UE, such as NIDD, provisioning of Communication Patterns, monitoring, etc.
  • the NEF is shared across network slices. This is different from scenarios in which the NEF is in a single slice, since here the AF needs to provide additional information when requesting services from the NEF. For example, the AF will need to provide the NEF with information about what slice(s) it wants to access services from.
  • the NEF-FE may act as an NEF resolution function and may provide the Application Function with contact information so that the AF can directly contact the proper NEF.
  • the security of the data stored in the DSF should be considered.
  • the network slice may serve multiple UE's but only wish to expose information related to some UE's.
  • a network function stores context data in the DSF.
  • the context data may be context information from the AMF, SMF, PCF, or UPF.
  • the context data may be the UE's IP Address, Reachability Status, Location, Data Usage, available RATs, etc.
  • the context data may be stored such that it can be indexed or retrieved with the UE's Identity (e.g., SUPI).
  • the DSF may respond to the NF with an indication of whether or not the data was stored.
  • the network function may encrypt the context information with a UE Specific Context Key that was provided by the UDM. This may be done so that only authorized network functions may later retrieve or modify the stored context. Note that, for each piece of information that the network function stores in the DSF, it may indicate whether or not the data may be exposed to other network functions and it may indicate what other network functions it may be exposed to.
  • a M2M service layer can provide applications and/or various devices with access to a collection of or a set of the above mentioned capabilities or functionalities, supported by the service layer, which can be referred to as a CSE or SCL.
  • CSE capabilities or functionalities
  • a few examples include but are not limited to security, charging, data management, device management, discovery, provisioning, and connectivity management which can be commonly used by various applications.
  • These capabilities or functionalities are made available to such various applications via APIs which make use of message formats, resource structures and resource representations defined by the M2M service layer.
  • M2M devices 18 and gateways 14 may communicate via various networks including, cellular, WLAN, WPAN (e.g., Zigbee, 6L0WPAN, Bluetooth), direct radio link, and wireline for example.
  • WPAN e.g., Zigbee, 6L0WPAN, Bluetooth
  • the node 30 may include any sub- combination of the foregoing elements while remaining consistent with an embodiment.
  • This node may be a node that implements any of the steps, operations, or functions described herein.
  • the processor 32 may run application-layer programs (e.g., browsers) and/or radio access-layer (RAN) programs and/or other communications programs.
  • the processor 32 may also perform security operations such as authentication, security key agreement, and/or cryptographic operations, such as at the access- layer and/or application layer for example.
  • the transmit/receive element 36 is depicted in Figure 17 as a single element, the node 30 may include any number of transmit/receive elements 36. More specifically, the node 30 may employ MFMO technology. Thus, in an embodiment, the node 30 may include two or more transmit/receive elements 36 (e.g., multiple antennas) for transmitting and receiving wireless signals.
  • the processor 32 may further be coupled to other peripherals 52, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 52 may include various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a sensor, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
  • biometrics e.g., finger print
  • a satellite transceiver e.g., a satellite transceiver
  • a digital camera for photographs or video
  • USB universal serial bus
  • FM frequency modulated
  • the node 30 may be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane.
  • the node 30 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 52.
  • Computing system 90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within a processor 91, to cause computing system 90 to do work.
  • the processor 91 may be a general purpose processor, a special purpose processor, a
  • processor 91 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the computing system 90 to operate in a communications network.
  • Coprocessor 81 is an optional processor, distinct from main processor 91, that may perform additional functions or assist processor 91. Processor 91 and/or coprocessor 81 may receive, generate, and process data related to the methods and apparatuses disclosed herein.
  • computing system 90 may contain peripherals controller 83 responsible for communicating instructions from processor 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.
  • peripherals controller 83 responsible for communicating instructions from processor 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.
  • computing system 90 may contain communication circuitry, such as for example a network adapter 97, that may be used to connect computing system 90 to an external communications network, such as network 12 of Figures 13 and 14, the RAN
  • the communication circuitry may be used to perform the transmitting and receiving steps of certain apparatuses, nodes, or functional entities described herein.
  • the core network 107 may facilitate communications with other networks.
  • the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit- switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the core network 107 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • the SMF 174 may also be connected to the UPF 176, which may provide the WTRUs 102a, 102b, 102c with access to a data network (DN) 190, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the SMF 174 may manage and configure traffic steering rules in the UPF 176 via the N4 interface.
  • the UPF 176 may be responsible for interconnecting a packet data unit (PDU) session with a data network, packet routing and forwarding, policy rule enforcement, quality of service handling for user plane traffic, and downlink packet buffering.
  • PDU packet data unit
  • the PCF 184 may be connected to the SMF 174 via an N7 interface, connected to the AMF 172 via an N15 interface, and connected to an application function (AF) 188 via an N5 interface.
  • the PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and SMF 174, allowing the control plane nodes to enforce these rules.

Abstract

Selon la présente invention, un serveur détermine l'identité d'une fonction d'exposition de réseau (NEF) associée à un équipement utilisateur (UE), et fournit à l'UE des informations telles qu'un identifiant de NEF, un identifiant externe d'UE, et un identifiant de tranche qui peuvent être utilisés pour enregistrer les dispositifs, applications ou fonctions. L'identité de NEF peut être apportée ou fournie automatiquement. L'identité de NEF peut être déterminée de manière dynamique, par exemple, sur la base d'une tranche de réseau utilisée par l'équipement utilisateur. Une fonction de stockage de données peut être utilisée pour recevoir des informations de contexte d'UE, telles que l'accessibilité, l'emplacement, l'utilisation de données et les technologies d'accès radio (RAT) disponibles, et une extrémité avant de fonction de stockage de données (DSF-FE) peut recevoir et traiter une requête provenant d'une NEF pour lire le contexte d'un UE, par exemple, déterminer s'il faut autoriser la requête, et peut en outre fournir le contexte d'UE. La DSF-FE peut être située dans la DSF ou dans la NEF, par exemple.
PCT/US2018/037775 2017-06-15 2018-06-15 Fonction d'exposition de réseau WO2018232253A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762520247P 2017-06-15 2017-06-15
US62/520,247 2017-06-15

Publications (1)

Publication Number Publication Date
WO2018232253A1 true WO2018232253A1 (fr) 2018-12-20

Family

ID=62909599

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/037775 WO2018232253A1 (fr) 2017-06-15 2018-06-15 Fonction d'exposition de réseau

Country Status (1)

Country Link
WO (1) WO2018232253A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111770123A (zh) * 2019-04-02 2020-10-13 华为技术有限公司 通信方法、设备及存储介质
WO2020253627A1 (fr) * 2019-06-18 2020-12-24 ***通信有限公司研究院 Procédé et dispositif d'établissement et de libération de tunnel de réseau local
CN112217653A (zh) * 2019-07-11 2021-01-12 中国电信股份有限公司 策略下发方法、装置和***
WO2021160446A1 (fr) * 2020-02-13 2021-08-19 Telefonaktiebolaget Lm Ericsson (Publ) Récupération d'imei et notification de changement d'imei dans des scénarios d'interfonctionnement de 5gc-epc
TWI759735B (zh) * 2019-05-02 2022-04-01 芬蘭商諾基亞科技公司 用於支援公共陸地行動網路及用戶設備能力標識遷移與共存之方法及設備
US20220124065A1 (en) * 2019-04-12 2022-04-21 Huawei Technologies Co., Ltd. System, apparatus and method to support data server selection
WO2022111311A1 (fr) * 2020-11-24 2022-06-02 中兴通讯股份有限公司 Procédé et appareil de découpage de réseau, dispositif électronique et support de stockage
CN114828204A (zh) * 2019-07-30 2022-07-29 华为技术有限公司 一种通信方法及设备
US11452007B1 (en) 2021-03-16 2022-09-20 Sprint Communications Company L.P. Wireless communication handovers for non-third generation partnership project (non-3GPP) access nodes
US11496357B2 (en) * 2017-07-28 2022-11-08 Beijing Boe Technology Development Co., Ltd. Method for creating resources and corresponding registration method, server, and client device
WO2022245667A1 (fr) * 2021-05-18 2022-11-24 T-Mobile Innovations Llc Service d'équipement utilisateur (ue) sur une fonction d'exposition de réseau (nef) dans un réseau de communication sans fil
US11528660B1 (en) 2021-06-23 2022-12-13 Sprint Communications Company Lp Wireless communication service over a network slice that comprises a network exposure function (NEF)
WO2023012048A1 (fr) * 2021-08-06 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Gestion d'identifications d'équipements utilisateurs
WO2024027893A1 (fr) * 2022-08-01 2024-02-08 Telefonaktiebolaget Lm Ericsson (Publ) Technique permettant à une application d'accéder à une fonction de réseau cible

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016187515A1 (fr) * 2015-05-20 2016-11-24 Convida Wireless, Llc Procédés et appareil pour analyser et regrouper des abonnements de couche service et des notifications pour une efficacité améliorée

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016187515A1 (fr) * 2015-05-20 2016-11-24 Convida Wireless, Llc Procédés et appareil pour analyser et regrouper des abonnements de couche service et des notifications pour une efficacité améliorée

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 23.502, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V0.4.0, 2 June 2017 (2017-06-02), pages 1 - 126, XP051298344 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 23.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V0.5.0, 1 June 2017 (2017-06-01), pages 1 - 145, XP051298314 *
HUAWEI ET AL: "Solution: Consolidated architecture option X", vol. SA WG2, no. Kaohsiung city, Taiwan; 20161017 - 20161021, 16 October 2016 (2016-10-16), XP051155232, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA2/Docs/> [retrieved on 20161016] *
NOKIA ET AL: "23.501 6.3.x: PCF selection", vol. SA WG2, no. Hangzhou, China; 20170529 - 20170602, 9 May 2017 (2017-05-09), XP051268724, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_121_Hangzhou/Docs/> [retrieved on 20170509] *

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11496357B2 (en) * 2017-07-28 2022-11-08 Beijing Boe Technology Development Co., Ltd. Method for creating resources and corresponding registration method, server, and client device
CN111770123B (zh) * 2019-04-02 2022-01-11 华为技术有限公司 通信方法、设备及存储介质
CN111770123A (zh) * 2019-04-02 2020-10-13 华为技术有限公司 通信方法、设备及存储介质
US20220124065A1 (en) * 2019-04-12 2022-04-21 Huawei Technologies Co., Ltd. System, apparatus and method to support data server selection
US11929977B2 (en) * 2019-04-12 2024-03-12 Huawei Technologies Co., Ltd. System, apparatus and method to support data server selection
TWI759735B (zh) * 2019-05-02 2022-04-01 芬蘭商諾基亞科技公司 用於支援公共陸地行動網路及用戶設備能力標識遷移與共存之方法及設備
WO2020253627A1 (fr) * 2019-06-18 2020-12-24 ***通信有限公司研究院 Procédé et dispositif d'établissement et de libération de tunnel de réseau local
CN112217653A (zh) * 2019-07-11 2021-01-12 中国电信股份有限公司 策略下发方法、装置和***
CN112217653B (zh) * 2019-07-11 2023-03-24 中国电信股份有限公司 策略下发方法、装置和***
CN114828204A (zh) * 2019-07-30 2022-07-29 华为技术有限公司 一种通信方法及设备
CN114828204B (zh) * 2019-07-30 2024-04-26 华为技术有限公司 一种通信方法及设备
CN115004663A (zh) * 2020-02-13 2022-09-02 瑞典爱立信有限公司 5gc-epc互通场景下的imei检索和imei更改通知
WO2021160446A1 (fr) * 2020-02-13 2021-08-19 Telefonaktiebolaget Lm Ericsson (Publ) Récupération d'imei et notification de changement d'imei dans des scénarios d'interfonctionnement de 5gc-epc
CN115004663B (zh) * 2020-02-13 2024-02-02 瑞典爱立信有限公司 5gc-epc互通场景下的imei检索和imei更改通知
WO2022111311A1 (fr) * 2020-11-24 2022-06-02 中兴通讯股份有限公司 Procédé et appareil de découpage de réseau, dispositif électronique et support de stockage
US11452007B1 (en) 2021-03-16 2022-09-20 Sprint Communications Company L.P. Wireless communication handovers for non-third generation partnership project (non-3GPP) access nodes
WO2022197467A1 (fr) * 2021-03-16 2022-09-22 T-Mobile Innovations Llc Transferts de communication sans fil pour des nœuds d'accès autres que spécifiques à un projet de partenariat de troisième génération (non 3gpp)
US11671879B2 (en) 2021-03-16 2023-06-06 T-Mobile Innovations Llc Wireless communication handovers for non-third generation partnership project (non-3GPP) access nodes
WO2022245667A1 (fr) * 2021-05-18 2022-11-24 T-Mobile Innovations Llc Service d'équipement utilisateur (ue) sur une fonction d'exposition de réseau (nef) dans un réseau de communication sans fil
US11956702B2 (en) 2021-05-18 2024-04-09 T-Mobile Innovations Llc User equipment (UE) service over a network exposure function (NEF) in a wireless communication network
US11528660B1 (en) 2021-06-23 2022-12-13 Sprint Communications Company Lp Wireless communication service over a network slice that comprises a network exposure function (NEF)
US11864102B2 (en) 2021-06-23 2024-01-02 T-Mobile Innovations Llc Wireless communication service over a network slice that comprises a network exposure function (NEF)
WO2022271558A1 (fr) * 2021-06-23 2022-12-29 T-Mobile Innovations Llc Service de communication sans fil sur une tranche de réseau contenant une fonction d'exposition de réseau (nef)
WO2023012048A1 (fr) * 2021-08-06 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Gestion d'identifications d'équipements utilisateurs
WO2024027893A1 (fr) * 2022-08-01 2024-02-08 Telefonaktiebolaget Lm Ericsson (Publ) Technique permettant à une application d'accéder à une fonction de réseau cible

Similar Documents

Publication Publication Date Title
US11903048B2 (en) Connecting to virtualized mobile core networks
US11696158B2 (en) Network Data Analytics in a communications network
EP3926930B1 (fr) Exposition de service de réseau pour une continuité de service et de session
WO2018232253A1 (fr) Fonction d&#39;exposition de réseau
KR102517014B1 (ko) 서비스 레이어에서의 트래픽 스티어링
US20230328512A1 (en) Core network assisted service discovery
KR102162732B1 (ko) 접속이 pdn 게이트웨이와 로컬 게이트웨이 사이에서 데이터의 라우팅을 가능하게 하는 것을 표시하기 위한 방법 및 장치
CN113678423A (zh) 动态网络能力配置
WO2022026482A1 (fr) Optimisations de plan utilisateur au moyen d&#39;une analyse de données de réseau
CN112042233A (zh) 在5g网络中管理与局域数据网络(ladn)的连接的方法
EP3639612A1 (fr) Transfert de petites données, mise en tampon de données, et gestion de données en tant que service dans un réseau de communications
US20230017009A1 (en) Method and apparatus for indicating that connection enables routing of data between pdn gateway and local gateway

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18740685

Country of ref document: EP

Kind code of ref document: A1