Edge computing connected to 5gc functions

Abstract

Apparatuses and systems are described for providing support for connectivity of edge computing functions to 5GC functions. An edge computing service provider (ECSP) management system collects connectivity information of 5GC functions to connect edge application servers (EAS), edge enabling servers (EES), and edge configuration servers (ECS), including policy control functions (PCF), service capability exposure functions (SCEF), and network exposure functions (NEF). The 3GPP management system request for information is based on consuming a lifecycle management (LCM) management service (MnS) by the ECSP management system through a queryUpfInfoReq operation or a provisioning MnS through an upfSelection information object class (IOC).

Description

[0001] Priority Statement

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 136,736, filed January 13, 2021, which is incorporated herein by reference in its entirety. Technical Field

[0003] The embodiments relate to next-generation wireless communications. Specifically, some embodiments relate to edge computing in 5G networks. Background Technology

[0004] The use and complexity of wireless systems (including 5G networks and beginning to include 6G networks, etc.) have increased due to the increasing types of user equipment (UEs) using network resources and the increasing data volume and bandwidth used by various applications operating on these UEs (e.g., video streaming). With the massive increase in the number and diversity of communication devices, the corresponding network environment (including routers, switches, bridges, gateways, firewalls, and load balancers) has become increasingly complex. Unsurprisingly, the emergence of any new technology brings many problems. Attached Figure Description

[0005] In accompanying drawings that are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. Similar reference numerals with different letter suffixes may indicate different instances of similar components. The accompanying drawings illustrate, by way of example and not limitation, the various embodiments discussed in this document.

[0006] Figure 1A The architecture of the network is shown based on some aspects.

[0007] Figure 1B The non-roaming 5G system architecture is shown based on some aspects.

[0008] Figure 1C The non-roaming 5G system architecture is shown based on some aspects.

[0009] Figure 2 A block diagram of a communication device according to some embodiments is shown.

[0010] Figure 3 A 5G edge computing network according to some embodiments is shown.

[0011] Figure 4 A peer-to-peer (P2P) edge computing management deployment is illustrated according to some embodiments.

[0012] Figure 5 An architecture for enabling edge applications is shown according to some embodiments.

[0013] Figure 6 An inter-edge detection network (inter-EDN) according to some embodiments is shown.

[0014] Figure 7 An intra-EDN (Intra-Edge Detection Network) according to some embodiments is shown.

[0015] Figure 8 Service provider relationships in an edge computing network deployment according to some embodiments are illustrated.

[0016] Figure 9 An edge computing network according to some embodiments is shown.

[0017] Figure 10 The User Plane Function (UPF) selection via the Lifecycle Management (LCM) Management Service (MnS) is illustrated according to some embodiments.

[0018] Figure 11 The UPF selection via the configuration of MnS is shown based on several aspects.

[0019] Figure 12 The diagram illustrates how to query the 5th generation core (5GC) Internet Protocol (IP) address via MnS configuration based on several aspects. Detailed Implementation

[0020] The following description and accompanying drawings fully illustrate specific embodiments to enable those skilled in the art to implement them. Other embodiments may include structural, logical, electrical, procedural, and other variations. Parts and features of some embodiments may be included in, or replace, parts and features of other embodiments. The embodiments set forth in the claims include all available equivalents of these claims.

[0021] Figure 1A The network architecture is illustrated based on several aspects. Network 140A includes 3GPP LTE / 4G and NG network functions, which can be extended to 6G capabilities. Therefore, while 5G will be mentioned, it should be understood that this can be extended to 6G architectures, systems, and functions. Network functions can be implemented as discrete network elements on dedicated hardware, software instances running on dedicated hardware, and / or virtualized functions instantiated on appropriate platforms (e.g., dedicated hardware or cloud infrastructure).

[0022] Network 140A is shown as including user equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a portable (laptop) or desktop computer, a wireless phone, a drone, or any other computing device including wired and / or wireless communication interfaces. UE 101 and 102 may be collectively referred to herein as UE 101, and UE 101 may be used to perform one or more of the techniques disclosed herein.

[0023] Any radio link described herein (e.g., used in Network 140A or any other illustrated network) may operate according to any exemplary radio communication technology and / or standard. Any spectrum management scheme includes, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., Licensed Shared Access (LSA) in 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz and other frequencies, and Spectrum Access System (SAS) in 3.55–3.7 GHz and other frequencies). Different single-carrier or orthogonal frequency domain multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank-Based Multicarrier (FBMC), OFDMA, etc.) (particularly 3GPP NR) can be used by allocating OFDM carrier data bit vectors to appropriate symbol resources.

[0024] In some aspects, either UE 101 or 102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connectivity. In some aspects, either UE 101 or 102 may include a Narrowband (NB) IoT UE (e.g., an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) for exchanging data with an MTC server or device over a Public Land Mobile Network (PLMN), Proximity-Based Service (ProSe) or Device-to-Device (D2D) communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated. The IoT network includes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connectivity. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network. In some respects, either UE 101 or 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0025] UEs 101 and 102 can be configured to connect (e.g., communicatively coupled) to a radio access network (RAN) 110. RAN 110 can be, for example, an evolved universal mobile communications system (UMTS) terrestrial radio access network (E-UTRAN), a next-generation RAN (NG RAN), or other types of RAN.

[0026] UEs 101 and 102 utilize connections 103 and 104 respectively, each connection including a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces enabling communication coupling and can conform to cellular communication protocols such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) network protocols, PTT, PTT on Cellular (POC), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE) protocols, 5G protocols, 6G protocols, etc.

[0027] In one aspect, UEs 101 and 102 can further exchange communication data directly through the ProSe interface 105. The ProSe interface 105 may also be referred to as a sidelink (SL) interface, which includes one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Broadcast Channel (PSBCH), and Physical Sidelink Feedback Channel (PSFCH).

[0028] UE 102 is shown configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, according to which AP 106 may include Wi-Fi. Router. In this example, AP 106 is shown as a core network connected to the Internet but not to the wireless system (described in further detail below).

[0029] RAN 110 may include one or more access nodes that enable connections to 103 and 104. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some aspects, communication nodes 111 and 112 may be transmit / receive points (TRPs). When communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells, and one or more RAN nodes (e.g., low-power (LP) RAN node 112) for providing femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells).

[0030] Either RAN node 111 or 112 can terminate the air interface protocol and can be the first point of contact for UEs 101 and 102. In some aspects, either RAN node 111 or 112 can implement various logical functions of RAN 110, including but not limited to Radio Network Controller (RNC) functions, such as radio bearer management, uplink and downlink dynamic radio resource management and packet scheduling, and mobility management. In the example, either node 111 or 112 can be a gNB, eNB, or other type of RAN node.

[0031] RAN 110 is shown communicatively coupled to core network (CN) 120 via S1 interface 113. In various aspects, CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN (e.g., see reference 113). Figures 1B to 1C (As shown). In this aspect, the S1 interface 113 is divided into two parts: the S1-U interface 114, which carries traffic data between RAN nodes 111 and 112 and the serving gateway (S-GW) 122; and the S1 mobility management entity (MME) interface 115, which is the signaling interface between RAN nodes 111 and 112 and the MME 121.

[0032] In this respect, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123, and Home Subscriber Server (HSS) 124. MME 121 can functionally resemble the control plane of a traditional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 124 can include a database of network users, including subscription-related information used to support network entities in handling communication sessions. CN 120 can include one or more HSS 124s, depending on the number of mobile subscribers, equipment capacity, network organization, etc. For example, HSS 124 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0033] The S-GW 122 can terminate the S1 interface 113 facing RAN 110 and route data packets between RAN 110 and CN 120. Furthermore, the S-GW 122 can serve as a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0034] P-GW 123 can terminate an SGi interface toward the PDN. P-GW 123 can route data packets between CN 120 and external networks (e.g., networks including application server 184 (or application function (AF))) via Internet Protocol (IP) interface 125. P-GW 123 can also transmit data to other external networks 131A, which may include the Internet, IP Multimedia Subsystem (IPS) networks, and other networks. Generally, application server 184 can be an element that provides IP bearer resources for use with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this aspect, P-GW 123 is shown communicatively coupled to application server 184 via IP interface 125. Application server 184 can also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UEs 101 and 102 via CN 120.

[0035] P-GW 123 can also be a node for policy enforcement and charging data collection. The Policy and Charging Rule Function (PCRF) 126 is the policy and charging control element of CN 120. In non-roaming scenarios, in some aspects, a single PCRF may exist in the home public land mobile network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local traffic disruptions, two PCRFs may exist associated with the UE's IP-CAN session: the home PCRF (H-PCRF) within the HPLMN and the visited PCRF (V-PCRF) within the visited public land mobile network (VPLMN). PCRF 126 can be communicatively coupled to application server 184 via P-GW 123.

[0036] In some aspects, the communication network 140A can be an IoT network or a 5G or 6G network, including 5G new radio networks using licensed (5G NR) and unlicensed (5G NR-U) spectrum for communication. Currently, one IoT implementation is narrowband IoT (NB-IoT). Operation in the unlicensed spectrum can include dual connectivity (DC) operation and a standalone LTE system in the unlicensed spectrum, under which LTE-based technologies operate only in the unlicensed spectrum without using the "anchor" in the licensed spectrum, called MulteFire. In future versions and 5G systems, it is expected that the operation of the LTE system in both licensed and unlicensed spectrum will be further enhanced. This enhanced operation can include technologies for sidelink resource allocation and UE processing behavior for NR sidelink V2X communication.

[0037] The NG system architecture (or 6G system architecture) may include a RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 may include multiple nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., the 5G core network / 5GC) may include Access and Mobility Functions (AMF) and / or User Plane Functions (UPF). The AMF and UPF can be communicatively coupled to the gNB and NG-eNB via NG interfaces. More specifically, in some aspects, the gNB and NG-eNB can connect to the AMF via an NG-C interface and to the UPF via an NG-U interface. The gNB and NG-eNB can be coupled to each other via an Xn interface.

[0038] In some aspects, the NG system architecture can use reference points across various nodes. In some aspects, each gNB and NG-eNB can be implemented as a base station, mobile edge server, small cell, home eNB, etc. In some aspects, in the 5G architecture, the gNB can be the master node (MN), and the NG-eNB can be the slave node (SN).

[0039] Figure 1B The non-roaming 5G system architecture is illustrated based on several aspects. Specifically, Figure 1B The 5G system architecture 140B, shown as a reference point, can be extended to a 6G system architecture. More specifically, UE 102 can communicate with RAN 110 and one or more other 5GC network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as AMF 132, Session Management Function (SMF) 136, Policy Control Function (PCF) 148, Application Function (AF) 150, UPF 134, Network Slice Selection Function (NSSF) 142, Authentication Server Function (AUSF) 144, and Unified Data Management (UDM) / Household Subscriber Server (HSS) 146.

[0040] UPF 134 can provide connectivity to the data network (DN) 152, which may include, for example, carrier services, internet access, or third-party services. AMF 132 can be used to manage access control and mobility, and may also include network slice selection functionality. AMF 132 can provide UE-based authentication, authorization, mobility management, etc., and can be independent of the access technology. SMF 136 can be configured to set up and manage various sessions according to network policies. Therefore, SMF 136 can be responsible for session management and IP address allocation to the UE. SMF 136 can also select and control UPF 134 for data transmission. SMF 136 can be associated with a single session of UE 101 or multiple sessions of UE 101. That is, UE 101 can have multiple 5G sessions. Different SMFs can be assigned to each session. Using different SMFs allows for individual management of each session. Therefore, the functionality of each session can be independent of each other.

[0041] UPF 134 can be deployed in one or more configurations based on the desired service type and can connect to a data network. PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in 4G communication systems). UDM can be configured to store subscriber profiles and data (similar to HSS in 4G communication systems).

[0042] AF 150 can provide information about packet flows to PCF 148, which is responsible for policy control, to support desired QoS. PCF 148 can set mobility and session management policies for UE 101. For this purpose, PCF 148 can use packet flow information to determine appropriate policies for appropriate operations against AMF 132 and SMF 136. AUSF 144 can store data used for UE authentication.

[0043] In some aspects, the 5G system architecture 140B includes an IP Multimedia Subsystem (IMS) 168B and multiple IP Multimedia Core Network Subsystem entities, such as the Call Session Control Function (CSCF). More specifically, the IMS 168B includes a CSCF, which can function as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, and an emergency CSCF (E-CSCF) (in... Figure 1B(Not shown in the image), or query the CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured as the first contact point for UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. The I-CSCF 166B can be configured to act as the contact point for all IMS connections within the operator's network, where the destination of these IMS connections is a subscriber of that network operator or a roaming subscriber currently within the service area of ​​that network operator. In some aspects, the I-CSCF 166B can connect to another IP multimedia network 170E, for example, an IMS operated by a different network operator.

[0044] In some respects, the UDM / HSS 146 can be coupled to an application server 160E, which may include a Telephone Application Server (TAS) or other application servers (AS). The AS 160B can be coupled to the IMS 168B via an S-CSCF 164B or an I-CSCF 166B.

[0045] Reference points indicate that interactions can exist between corresponding NF services. For example, Figure 1B The following reference points are shown: N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UDM 146 and AMF 132, not shown), N9 (between the two UPF 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136, not shown), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and AMF 132, not shown). N14 (between PCF 144 and UDM 146, not shown), N14 (between the two AMF 132s, not shown), N15 (between PCF 148 and AMF 132 in non-roaming scenarios, or between PCF 148 and the visited network and AMF 132 in roaming scenarios, not shown), N16 (between the two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Also available are... Figure 1BOther reference points not shown in the text are indicated.

[0046] Figure 1C The 5G system architecture 140C and its service-based representation are shown. In addition... Figure 1B In addition to the network entities shown, system architecture 140C may also include network exposure function (NEF) 154 and network repository function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and the interaction between network functions may be represented by corresponding point-to-point reference points Ni, or represented as service-based interfaces.

[0047] In some aspects, such as Figure 1C As shown, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (service-based interface presented by AMF 132), Nsmf158I (service-based interface presented by SMF 136), Nnef 158B (service-based interface presented by NEF 154), Npcf158D (service-based interface presented by PCF 148), Nudm 158E (service-based interface presented by UDM 146), Naf158F (service-based interface presented by AF 150), Nnrf 158C (service-based interface presented by NRF 156), Nnssf158A (service-based interface presented by NSSF 142), and Nausf 158G (service-based interface presented by AUSF 144). It is also possible to use... Figure 1C Other service-based interfaces not shown (e.g., Nudr, N5g-eir, and Nudsf).

[0048] The NR-V2X architecture can support highly reliable, low-latency sidelink communication with various traffic patterns, including periodic and aperiodic communication with random packet arrival times and sizes. The techniques disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0049] Figure 2 A block diagram of a communication device according to some embodiments is shown. Communication device 200 may be a UE (e.g., a dedicated computer, personal or laptop computer (PC), tablet PC, or smartphone), a dedicated network device (e.g., an eNB), server-running software configured to operate as a network device, a virtual device, or any machine capable of (sequentially or otherwise) executing instructions for actions to be taken by a specified machine. For example, communication device 200 may be implemented as... Figures 1A to 1C One or more devices are shown. Note that the communications described herein may be encoded before being transmitted by a sending entity (e.g., UE, gNB) for reception by a receiving entity (e.g., gNB, UE) and decoded after being received by the receiving entity.

[0050] The examples described herein may include logic or components, modules, or mechanisms, or may operate on logic or components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and which can be configured or arranged in a particular manner. In the examples, circuitry may be arranged as modules in a specified manner (e.g., internally or to external entities, such as other circuitry). In the examples, all or part of one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) to operate to perform specified operations. In the examples, the software may reside on a machine-readable medium. In the examples, the software, when executed by the underlying hardware of the module, causes that hardware to perform the specified operations.

[0051] Therefore, the terms "module" (and "component") are understood to encompass tangible entities that are physically constructed, specially configured (e.g., hardwired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate or perform any of the operations described herein in a specified manner. Consider the example of modules being temporarily configured, where it is not necessary to instantiate each module at any given time. For example, in the case where a module comprises a general-purpose hardware processor configured using software, this general-purpose hardware processor can be configured as various different modules at different times. The software can accordingly configure the hardware processor to constitute a particular module at one time and another module at another time.

[0052] The communication device 200 may include a hardware processor (or equivalent processing circuitry) 202 (e.g., a central processing unit (CPU), GPU, hardware processor core, or any combination thereof), main memory 204, and static memory 206, some or all of which may communicate with each other via an interconnect (e.g., a bus) 208. The main memory 204 may include any or all of removable and non-removable storage devices, volatile or non-volatile memory. The communication device 200 may also include a display unit 210, such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In this example, the display unit 210, input device 212, and UI navigation device 214 may be a touchscreen display. The communication device 200 may also include a storage device (e.g., a drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The communication device 200 may also include an output controller, such as serial (e.g., Universal Serial Bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC) etc.) connection, to communicate with or control one or more peripheral devices (e.g., printer, card reader, etc.).

[0053] Storage device 216 may include non-transitory machine-readable medium 222 (hereinafter referred to as machine-readable medium) storing one or more sets of data structures or instructions 224 (e.g., software) that embody or are utilized by any one or more technologies or functions described herein. During execution of instructions 224 by communication device 200, instructions 224 may also reside wholly or at least partially in main memory 204, in static memory 206, and / or in hardware processor 202. Although machine-readable medium 222 is shown as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., centralized or distributed databases, and / or associated caches and servers) configured to store one or more instructions 224.

[0054] The term "machine-readable medium" can include any medium capable of storing, encoding, or carrying instructions that are executed by the communication device 200 and cause the communication device 200 to perform any one or more of the technologies of this disclosure, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Examples of non-limiting machine-readable media can include solid-state memory, as well as optical and magnetic media. Specific examples of machine-readable media can include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)), and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks.

[0055] Commands 224 can also be sent or received via a communication network through network interface device 220 using transmission medium 226, utilizing any of several wireless local area network (WLAN) transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Example communication networks may include local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), simple old-style telephone (POTS) networks, and wireless data networks. Communication on the network may include one or more different protocols, such as the IEEE 802.11 standard series (referred to as Wi-Fi), the IEEE 802.16 standard series (referred to as WiMax), the IEEE 802.15.4 standard series, the Long Term Evolution (LTE) standard series, the Universal Mobile Telecommunications System (UMTS) standard series, peer-to-peer (P2P) networks, next-generation (NG) / fifth-generation (5G) standards, etc. In the example, network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas for connecting to transmission medium 226.

[0056] Note that the term "circuit" as used herein refers to, is part of, or includes hardware components configured to provide the described functions, such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), and so on. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements (or combinations of circuits used in electrical or electronic systems) and program code for performing the functions of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0057] Therefore, as used herein, the term "processor circuit" or "processor" refers to, is part of, or includes the following circuits: circuits capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transmitting digital data. The term "processor circuit" or "processor" may also refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core or multi-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and / or functional processes).

[0058] Any radio link described herein may operate according to any one or more of the following radio communication technologies and / or standards, including but not limited to: Global System for Mobile Communications (GSM) radio communication technology, General Packet Radio Service (GPRS) radio communication technology, Enhanced Data Rate GSM Evolution (EDGE) radio communication technology, and / or 3rd Generation Partnership Project (3GPP) radio communication technology, such as Universal Mobile Telecommunications System (UMTS), Free Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code Division Multiple Access 2000 (CDMA2000), and Cellular Digital Packet Data Interchange (CDMA2000). (CDPD), Mobitex, 3G, Circuit Switched Data (CSD), High-Speed ​​Circuit Switched Data (HSCSD), Universal Mobile Telecommunications System (3G) (UMTS(3G)), Wideband Code Division Multiple Access (W-CDMA(UMTS)), High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), High-Speed ​​Packet Access+ (HSPA+), Universal Mobile Telecommunications System Time Division Duplex (UMTS-TDD), Time Division Code Division Multiple Access (TD-CDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), 3G Partnership Version 8 (Prior to 4G) (3GPP) Rel.8 (pre-4G), 3GPP Rel.9 (3rd Generation Partnership Project version 9), 3GPP Rel.10 (3rd Generation Partnership Project version 10), 3GPP Rel.11 (3rd Generation Partnership Project version 11), 3GPP Rel.12 (3rd Generation Partnership Project version 12), 3GPP Rel.13 (3rd Generation Partnership Project version 13), 3GPP Rel.14 (3rd Generation Partnership Project version 14), 3GPP Rel.15 (3rd Generation Partnership Project version 15), 3GPP Rel.16 (3rd Generation Partnership Project version 16), 3GPP Rel.17 (3rd Generation Partnership Project version 17), and subsequent versions (e.g., Rel.18, Rel.17).19 etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extensions, LTE Advanced Professional, LTE Licensed Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), LTE Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code Division Multiple Access 2000 (3rd Generation) (CDMA2000 (3G)), Optimized Evolved Data or Evolved Data Only (EV-DO), Advanced Mobile Phone Systems (1st Generation) (AMPS (1G)), Total Access Communication System / Extended Total Access Communication System (TACS / ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-Talk (PTT), Mobile Phone Systems (MTS), Improved Mobile Phone Systems (IMTS), Advanced Mobile Phone Systems (AMTS), OLT (Norwegian: Offentlig) LandmobilTelefoni (public land mobile phone), MTD (abbreviation of Swedish Mobiltelefonisystem D, or mobile phone system D), public automated land mobile (Autotel / PALM), ARP (Finnish Autoradiopuhelin, "car radio phone"), NMT (Nordic mobile phone), NTT (Japan Telecom) high-capacity version (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handheld Telephone System (PHS), Broadband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA, also known as 3GPP Universal Access Network or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, Universal Millimeter Wave Standard (wireless systems operating at 10-300 GHz and above, such as WiGig, IEEE 802.11ad, IEEE Technologies operating in the 300 GHz and THz bands and above (based on 3GPP / LTE, or IEEE 802.11p, or IEEE 802.11).11bd and others) vehicle-to-vehicle (V2V) and vehicle-to-X (V2X) and vehicle-to-infrastructure (V2I) and infrastructure-to-vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems (e.g., smart transport systems and others (typically operating at 5850MHz to 5925MHz or above (typically up to 5935MHz, following the change recommendations in CEPT Report 71)), European ITS-G5 system (i.e., based on IEEE) The European style of 802.11p DSRC includes ITS-G5A (i.e., ITS-G5 operating in the following European ITS band, dedicated to security-related applications in the frequency range of 5875GHz to 5905GHz), ITS-G5B (i.e., operating in the following European ITS band, dedicated to non-security applications in the frequency range of 5855GHz to 5875GHz), ITS-G5C (i.e., operating ITS applications in the frequency range of 5470GHz to 5725GHz), DSRC in Japan in the 700MHz band (including 715MHz to 725MHz), systems based on IEEE 802.11bd, etc.

[0059] The various aspects described herein can be applied to any spectrum management scheme context, including dedicated licensed spectrum, unlicensed spectrum, license-exempt spectrum, and (licensed) shared spectrum (e.g., Licensed Shared Access (LSA) in frequencies of 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz and above, and Spectrum Access Systems (SAS) / Citizens Broadband Radio Systems (CBRS) in frequencies of 3.55–3.7 GHz and above). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum and other types of spectrum / bands, such as nationally allocated bands (including 450–470 MHz, 902–928 MHz (e.g., allocated in the US (FCC Part 15)), 863–868.6 MHz (e.g., allocated in the EU (ETSI EN300)). 220), 915.9-929.7MHz (Note: e.g., allocated in Japan), 917-923.5MHz (Note: e.g., allocated in South Korea), 755-779MHz and 779-787MHz (Note: e.g., allocated in China), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (Note: This is the globally available ISM band, and it is used by the Wi-Fi technology family (11b / g / n / ax) and Bluetooth), 2500-2690MHz, 698 -790MHz, 610-790MHz, 3400-3600MHz, 3400-3800MHz, 3800-4200MHz, 3.55-3.7GHz (Note: e.g., allocated to citizen broadband radio services in the US), 5.15-5.25GHz and 5.25-5.35GHz and 5.47-5.725GHz and 5.725-5.85GHz bands (Note: e.g., allocated in the US (FCC Part 15), including four U-NII bands in a total of 500MHz of spectrum), 5.725-5.875GHz (Note: e.g., allocated in the EU (ETSI EN 301 893)), 5.47-5.65GHz (Note: e.g., allocated in South Korea), 5925-7125MHz and 5925-6425MHz bands (Note: under consideration by the US and EU respectively)). The next generation of Wi-Fi systems is expected to include the 6 GHz spectrum as an operating band, but it is worth noting that as of December 2017, Wi-Fi systems were not yet permitted to use this band.Regulatory oversight is expected to be completed in 2019-2020, covering IMT advanced spectrum, IMT-2020 spectrum (expected to include the 3600-3800MHz, 3800-4200MHz, 3.5GHz band, 700MHz band, and 24.25-86GHz band), spectrum available under the FCC's "Spectrum Frontier" 5G initiative (including 27.5-28.35GHz, 29.1-29.25GHz, 31-31.3GHz, 37-38.6GHz, 38.6-40GHz, 42-42.5GHz, 57-64GHz, 71-76GHz, 81-86GHz, and 92-94GHz), and 5.9GHz (commonly used in 5G). The spectrum typically ranges from 5.85-5.925 GHz to 63-64 GHz for ITS (Intelligent Transportation Systems), and currently allocated to WiGig (e.g., WiGig band 1 (57.24-59.40 GHz), WiGig band 2 (59.40-61.56 GHz), WiGig band 3 (61.56-63.72 GHz), and WiGig band 4 (63.72-65.88 GHz)). It also includes the 57-64 / 66 GHz band (note: this band has close proximity to the globally designated Multi-Gigabit Wireless Systems (MGWS) / WiGig, with a total of 14 GHz of spectrum allocated in the US (FCC Section 15), and the EU (ETSIEN for Fixed P2P). The standard allocates a total of 9 GHz of spectrum (302 567 and ETSI EN 301 217-2), the 70.2 GHz-71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated for automotive radar applications (e.g., 76-81 GHz), and future bands (including 94-300 GHz and above). Furthermore, this scheme can be used in conjunction with bands such as TV blank bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being promising candidates. In addition to cellular applications, specific applications in vertical markets can also be addressed, such as PMSE (Programming and Special Events), medical, health, surgical, automotive, low-latency, and drone applications.

[0060] The various aspects described in this article can also enable the tiered application of the scheme, for example, by introducing tiered usage priorities for different types of users (e.g., low / medium / high priority, etc.) based on priority access to the spectrum, such as Level 1 users having the highest priority, followed by Level 2 users, then Level 3 users, and so on.

[0061] The various aspects described in this article can also be applied to different single-carrier or OFDM types (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) by assigning OFDM carrier data bit vectors to corresponding symbol resources (especially 3GPP NR (New Radio)).

[0062] Some features in this document are defined for the network side, such as AP, eNB, NR, or gNB. Note that these terms are typically used in the context of 3GPP 5G and 6G communication systems. Nevertheless, the UE can also play this role and act as an AP, eNB, or gNB; that is, some or all of the features defined for network devices can be implemented by the UE.

[0063] As mentioned above, 5G networks go beyond traditional mobile broadband services to provide a variety of new services that may have ultra-low latency, ultra-high reliability, and high data capacity requirements for security and performance reasons, such as the Internet of Things (IoT), industrial control, autonomous driving, and mission-critical communications. Edge computing has been added as a feature to the 5G Core (5GC) system architecture to support such services by hosting some applications closer to the local data network, thereby reducing end-to-end latency and load on the transport network. Figure 3 A 5G edge computing network according to some embodiments is shown.

[0064] Figure 4 A P2P edge computing management deployment is illustrated according to some embodiments. Figure 4 In the deployment shown, edge computing in the 3GPP network involves communication between the 3GPP management system and non-3GPP management systems. The non-3GPP management system includes the edge computing management system and the ETSI Network Functions Virtualization (NFV) Management and Orchestration (MANO).

[0065] The deployment of edge computing in 3GPP networks leverages collaboration with other standards development organizations (SDOs) because Application Functions (AFs) and Application Servers (ASs) are not 3GPP-defined nodes. Deploying edge computing-enabled network functions in both 3GPP and non-3GPP networks involves communication between the 3GPP management system and the non-3GPP management system.

[0066] exist Figure 4In the example, the 3GPP management system can initiate edge computing deployment by requesting the edge computing management system to deploy a local data network and requesting the Network Functions Virtualization Coordinator (NFVO) to connect the UPF and the local data network, where the connection between the UPF and the local data network (e.g., a virtual link) has Quality of Service (QoS) requirements for N6. The edge computing management system can also initiate edge computing deployment by requesting the 3GPP management system to deploy both the UPF and NFVO to connect the UPF and the local data network, where the connection between the UPF and the local data network has QoS requirements.

[0067] Figure 5 An architecture for enabling edge applications is illustrated. In this architecture, the application client is an application residing in the UE that performs one or more client functions, and the edge application server (EAS) is an application server residing in an edge data network that performs server functions, acting as a local data network. The application client connects to the edge application server to utilize (or obtain) the services of applications that offer the advantages of edge computing.

[0068] Figure 5 The application architecture for enabling edge applications is illustrated. The edge data network is a local data network. One or more edge application servers and edge enablement servers (EES) are included in the EDN. The edge configuration server (ECS) provides configuration related to the EES, including details of the edge data network hosting the EES. The UE includes one or more application clients and edge enablement clients. One or more edge application servers, edge enablement servers, and edge configuration servers can interact with the 3GPP core network.

[0069] The EDGE-1 reference point supports interactions between edge-enabled servers and edge-enabled clients related to enabling edge computing. The EDGE-1 reference point supports: registration and deregistration of edge-enabled clients to edge-enabled servers; retrieval and configuration of UE configuration information; and discovery of available edge application servers in the edge data network.

[0070] The EDGE-2 reference point supports edge enablement layer-related interactions between the edge enablement server and the 3GPP network. The EDGE-2 reference point supports access to 3GPP network functions and application programming interfaces (APIs) to retrieve network capability information, for example, via the Service Capability Exposure Function (SCEF) and Network Exposure Function (NEF) APIs, where the EES acts as a trusted AF in the 5GC. The EDGE-2 reference point reuses interfaces from 3GPP reference points defined in SA2, N33, or EPS or 5GS considering different deployment models.

[0071] EDGE-3 reference points support edge enablement layer-related interactions between edge enablement servers and edge application servers. EDGE-3 reference points support: registering edge application servers using availability information (e.g., time restrictions, location restrictions); deregistering edge application servers from edge enablement servers; and providing access to network capability information (e.g., location information). The following cardinality rules apply to EDGE-3 (between EAS and EES): a) an EAS can communicate with only one EES; b) an EES can communicate with one or more EAS simultaneously.

[0072] The EDGE-4 reference point supports edge data network configuration between the edge data network configuration server and the edge-enabled client, related to the edge enable layer. The EDGE-4 reference point supports configuring edge data network configuration information for the edge-enabled client in the UE.

[0073] The EDGE-5 reference point supports interaction between application clients (one or more) and edge-enabled clients in the UE. The EDGE-5 reference point supports: obtaining information about the application client's connection to the edge application server; notification of events related to the connection between the application client and its corresponding edge application server, such as when the application client needs to reconnect to a different edge application server; providing application client information (e.g., its profile) for various tasks (e.g., identifying the appropriate edge application server instance to connect to); and providing the edge-enabled client with the identity of the required edge application server so that it can use that identity as a filter when requesting information about the edge application server.

[0074] The EDGE-6 reference point supports interaction between the edge data network configuration server and the edge enable server related to the edge enable layer. The EDGE-6 reference point supports registering edge enable server information with the edge enable network configuration server.

[0075] The EDGE-2 (or EDGE-7) reference point supports edge enablement layer-related interactions between the edge enablement server and the 3GPP network. The EDGE-7 reference point supports accessing 3GPP network functions and APIs to retrieve network capability information, for example, via the SCEF and NEF APIs, where the EAS acts as a trusted AF in the 5GC. The EDGE-7 reference point reuses interfaces from the 3GPP reference point defined in SA2, N6, or EPS or 5GS considering different deployment models.

[0076] The EDGE-8 reference point supports interaction between the edge data network configuration server and the 3GPP network. The EDGE-8 reference point supports: configuring and setting up edge data networks with the 3GPP network using publicly available network services.

[0077] EDGE-9 reference points enable interaction between two edge-enabled servers. EDGE-9 reference points can be provided between EES servers within different EDNs and within the same EDN.

[0078] The Edge Enabled Server (EES) provides support for both edge application servers and edge enabled clients. The functions of the Edge Enabled Server include: a) configuring edge enabled clients with configuration information to exchange application data traffic with the edge application server; b) supporting API callers and API exposure functions; c) interacting with the 3GPP core network to access network functions directly (e.g., via PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF); and d) supporting application context transport.

[0079] The following cardinality rules apply to edge-enabled servers: a) one or more EES can be located in an EDN; b) one or more EES can be located in the EDN of each Edge Computing Service Provider (ECSP).

[0080] EAS is an application server that resides in an edge data network and performs server functions. Application clients connect to the edge application server to leverage the application's services and the advantages of edge computing. The application's server functions may only be available as an edge application server. However, if the application's server functions are available as both an edge application server and an application server residing in the cloud, the functions of the edge application server and the application server may differ. Furthermore, if the edge application server and the application server have different functions, the application data traffic may also differ.

[0081] Edge application servers can consume 3GPP core network capabilities in different ways, such as: a) if it is a 3GPP core network trusted entity, it can directly call the 3GPP core network function API; b) it can call 3GPP core network capabilities through the edge enabled server; and c) it can call 3GPP core network capabilities through capability exposure functions (e.g., SCEF or NEF).

[0082] The following cardinality rules apply to edge application servers: a) One or more EASs can reside in the EDN. One or more EASs belonging to the same EAS ID can be provided by multiple ECSPs in the EDN.

[0083] An Edge Enabled Server ID (EESID) is a fully qualified domain name (FQDN) for an Edge Enabled Server, and each Edge Enabled Server ID is unique within the PLMN domain.

[0084] The Edge Application Server ID (EASID) identifies a specific application, such as SA6Video, SA6Game, etc. For example, all edge SA6Video servers share the same Edge Application Server ID. The format of the EAS ID is beyond the scope of this specification. Table E28.2.4-1 shows the Edge Application Server profile.

[0085] Table E28.2.4-1: Edge Application Server Profile

[0086]

[0087]

[0088] Edge application server service key performance indicators (KPIs) provide information about the service characteristics provided by the edge application server (see, for example, Table E28.2.5-1).

[0089] Table E28.2.5-1: Edge Application Server Service KPIs

[0090]

[0091]

[0092] The Edge Enabled Server profile includes information about EES and the services it provides (see, for example, Table E28.2.6-1).

[0093] Table E28.2.6-1: Edge-Enabled Server Profile

[0094]

[0095] The exposure of network capabilities to one or more edge application servers depends on the deployment scenario and the business relationship between the ASP / ECSP and the PLMN operator. The following mechanisms are supported: direct network capability exposure and / or network capability exposure via an edge-enabled server.

[0096] In some implementations, the network capability exposure to one or more EASs depends on the deployment scenario and the business relationship between the ASP / ECSP and the PLMN operator. The following mechanisms are supported: direct network capability exposure and / or network capability exposure via an edge enablement server. In some implementations, the availability of chargeable features with different deployment options, depending on the business relationship between the edge application service provider, the edge computing service provider, and the SFC service provider, is beyond the scope of this disclosure (SA5 study).

[0097] Figure 6 An inter-EDN according to some embodiments is shown. Figure 7An intra-EDN according to some embodiments is illustrated. An EDGE-9 reference point enables interaction between two edge-enabled servers. EDGE-9 reference points can be provided between EES within different EDNs (e.g., Figure 6 (as shown) and provides (e.g., between EES within the same EDN) Figure 7 (As shown).

[0098] Figure 8 Service provider relationships in an edge computing network deployment according to some embodiments are illustrated. Figure 8 This illustrates the roles and relationships of service providers involved in the deployment of edge computing services. Application Service Providers (ASPs) are responsible for creating the EAS and Application Clients (ACs). ECSPs are responsible for deploying the EDN that includes the EAS and EES; the EES provides configuration information to the EEC, enabling the ACs to exchange application data traffic with the EAS. PLMN operators are responsible for deploying 5G network functions such as 5GC and 5G NR.

[0099] End users are consumers of applications / services provided by ASPs and can enter into ASP service agreements with a single application service provider or multiple application service providers. End users enter into PLMN subscription agreements with PLMN operators. UEs (User Equipments) used by end users are allowed to register to the PLMN operator's network. ASPs consume edge services (e.g., infrastructure, platform, etc.) provided by ECSPs and can enter into ECSP service agreements with a single ECSP or multiple ECSPs. ECSPs can be mobile network operators or third-party service providers offering edge computing services. A single PLMN operator can enter into PLMN operator service agreements with a single computing service provider or multiple edge computing service providers. A single ECSP can enter into PLMN operator service agreements with a single PLMN operator or multiple PLMN operators providing edge computing support. ECSPs and PLMN operators can be part of the same organization or different organizations.

[0100] As mentioned above, the 3GPP management system manages network functions (e.g., UPF, PCF, EES, ECS, EAS, etc.) and services defined by 3GPP. To support edge computing management, the 3GPP management system includes both the PLMN management system, which is responsible for the orchestration and management of mobile networks, and the ECSP management system, which is responsible for the orchestration and management of EDN. ECSP and PLMN operators can be part of the same organization.

[0101] This document discloses mechanisms for deploying edge application servers, edge enable servers, edge configuration servers, and 5G mobile networks to support edge computing for 3GPP TR 28.814. The embodiments described herein also include service-level and specification-level use cases and requirements, encompassing various deployments. Deployments include: PLMN / EC service providers deploying EAS on EDN; ECSPs deploying EAS on EDN; PLMN / EC service providers deploying EES on EDN; ECSPs deploying EES on EDN; PLMN / EC service providers deploying ECS; and ECSPs deploying ECS, where the PLMN / EC service provider instructs the operator to own both the PLMN and the EDN.

[0102] Figure 9 An edge computing network according to some embodiments is shown. Figure 9 This shows a more in-depth view of 5GC's interaction with EDN. For example... Figure 9 As shown, the mobile network connects to two EDNs, each containing an EAS. In EDN#1, the EAS and EES are trusted by the mobile operator, and therefore connect to the PCF in the mobile network via the Edge-7 and Edge-2 interfaces, respectively. In EDN#2, the EAS and EES are trusted by the mobile operator, and therefore connect to the NEF via the Edge-7 and Edge-2 interfaces, respectively. The ECS connects to the NEF via the Edge-8 interface.

[0103] 3GPP TS 23.558 specifies that EAS, EES, and ECS interact with 5GC functions such as PCF, NEF, and SCEF to provide edge computing services. For example, EES has the ability to interact with the 3GPP core network to access network functions directly (e.g., via PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF), see sub-clause 6.3.2 of TS 23.558. ECS has the ability to interact with the 3GPP core network to access network functions directly (e.g., via PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF), see sub-clause 6.3.4 of TS 23.558. EAS can invoke 3GPP core network capabilities through capability-exposed functions (i.e., SCEF or NEF), see sub-clause 6.3.6 of TS 23.558. Therefore, the ECSP management system collects connection information for 5GC functions such as PCF, NEF, and SCEF, thus enabling the ECSP management system to connect EAS, EES, and ECS. Accordingly, the ECSP management system collects connection information for 5GC functions such as PCF, NEF, and SCEF. Therefore, the ECSP management system can connect EAS, EES, and ECS to PCF, NEF, and SCEF.

[0104] Version 6.2.x UPF selection for supporting EAS deployment

[0105] 6.2.x.1 Objective

[0106] The goal is to enable the ECSP management system to query the 3GPP management system to select a UPF from one or more deployed UPFs based on service area and QoS requirements, or to instantiate a new UPF if none is available. The selected UPF connects to the EAS via the N6 interface to support edge computing applications.

[0107] 6.2.x.2 Description

[0108] 1. The ECSP management system queries the 3GPP management system for information about the UPFs that will be connected to EAS by providing UPF selection requirements. The UPF selection requirements include a list of service area requirements (e.g., topology service area, geographic service area (see subclause 7.3.3 in TS 28.558)) and N6 traffic routing requirements (see Table 8.2.4.1 in TS 23.558).

[0109] 2.3 The GPP management system identifies one or more UPFs that meet the EAS service area and QoS requirements among the deployed UPFs.

[0110] 3. If the UPF cannot be found, the 3GPP management system will deploy a new UPF.

[0111] 4.3 The GPP management system provides UPF information to the ECSP management system.

[0112] 6.2.x.3 Requirements

[0113] REQ-UPF-FUN-1 3GPP management service producers should have the ability to allow authorized consumers to query information about the UPFs that will be connected to the EAS based on UPF selection requirements (e.g., service area and QoS requirements).

[0114] REQ-UPF-FUN-2 3GPP managed service providers should have the ability to provide UPF information to consumers.

[0115] 7.x UPF Selection for Assisting EAS Deployment

[0116] 7.x.1 Overview

[0117] This sub-clause provides potential solutions for the use cases of selecting UPF to support EAS deployment (see sub-clause 6.2.x). It is assumed that EAS has been deployed based on the solution described in sub-clause 7.1.

[0118] This solution is suitable for PLMN operators deploying one or more UPFs in the 5GC, and the ECSP management system is used to query the 3GPP management system to select the UPF in the 5GC, which will be connected to the EAS via the N6 interface to support edge computing applications.

[0119] 7.x.2 Solution #1 – UPF Selection Using LCM MnS

[0120] Figure 10 UPF selection via LCM MnS is illustrated according to some embodiments. Specifically, Figure 10 The ECSP management system is shown to request the 3GPP management system to identify the UPF via the configured MnS.

[0121] The ECSP management system consumes LCM MnS via the queryUpfInfoReq operation to request the 3GPP management system to identify a UPF that can be connected to EAS via the N6 interface, and that the UPF has the following attributes:

[0122] EAS Topology Service Area: The topology service area is defined based on the relationship between the UE and the connection point to the network, such as a set of cell IDs, tracking area identifiers, or PLMN IDs (see sub-clause 7.3.3.2 in TS 23.558).

[0123] EAS Geographic Service Area: A geographic service area is a region specified by a geographic unit such as a geographic coordinate ID (see sub-clause 7.3.3.3 in TS 23.558).

[0124] List of N6 traffic routing requirements: N6 traffic routing information and / or routing profile ID corresponding to each EAS Data Network Access Identifier (DNAI).

[0125] EAS Connection Information: This attribute contains EAS connection information, including the EAS identifier and EAS endpoint information.

[0126] The 3GPP management system sends queryUpfInfoResp to notify the consumer that the request is in progress.

[0127] The 3GPP management system locates a UPF (one or more) that is being deployed based on the EAS topology service area, the EAS geographic service area (see subclause 7.3.3 in TS 28.558), and QoS requirements, and can deploy a new UPF if no UPF is found.

[0128] The 3GPP management system sends queryUpfInfoResp to notify the ECSP management system of the UPF identifier and the UPF endpoint attribute containing the endpoint information of the selected UPF.

[0129] 7.x.3 Solution #2 – Using UPF Selection with Configuration MnS

[0130] Figure 11 The UPF selection via MnS configuration is shown based on several aspects. Specifically, Figure 11 The ECSP management system is shown to request the 3GPP management system to identify the UPF via the configured MnS.

[0131] The ECSP management system sends UPF selection requests in the Information Object Class (IOC). Therefore, an upfSelection IOC should be defined to support the UPF selection solution. The upfSelection IOC should include, but is not limited to, the following attributes:

[0132] EAS Topology Service Area: The topology service area is defined based on the relationship between the UE and the connection point to the network, such as a set of cell IDs, tracking area identifiers, or PLMN IDs (see sub-clause 7.3.3.2 in TS 23.558).

[0133] EAS Geographic Service Area: A geographic service area is a region specified by a geographic unit such as a geographic coordinate ID (see sub-clause 7.3.3.3 in TS 23.558).

[0134] List of N6 traffic routing requirements: N6 traffic routing information and / or route profile ID corresponding to each EAS DNAI (see Table 8.2.4.1 in TS 23.558).

[0135] UPF Connection Information: This property contains the UPF connection, including the UPF identifier and the domain name (DN) of the upfEndpoint IOC containing UPF endpoint information.

[0136] EAS Connection Information: This attribute contains the EAS connection, including the EAS identifier and the DN of the easEndpoint IOC containing EAS endpoint information.

[0137] UPF Select: This property contains a value select. If select = TRUE, it is a request to select a UPF.

[0138] The ECSP management system obtains UPF information from the IOC. Therefore, the upfEndpoint IOC should be defined to include the endpoint information of the UPF.

[0139] UPF Endpoint: This property contains the DN of the upfEndpoint IOC, which contains endpoint information for the selected UPF.

[0140] If upfSelection MOI does not exist:

[0141] The ECSP management system consumes the configuration MnS through the createMOI operation on the upfSelection IOC to query UPF information from the 3GPP management system. The upfSelection IOC contains the EAS topology service area, the EAS geographic service area, the list of N6 traffic routing requirements, the EAS connection information, and the UPF selection = TRUE.

[0142] The 3GPP management system finds a UPF among the deployed UPFs based on the service area requirements (e.g., topology service area, geographic service area (see subclause 7.3.3 in TS 28.558)) and QoS requirements contained in the upfSelection IOC, and can deploy a new UPF if no UPF is found.

[0143] The 3GPP management system creates an upfSelection MOI and sends a notifyMOICreation with an attribute list, which includes the DN of the upfEndpoint IOC containing UPF connection information (see subclause 11.1.1.7 in TS 28.532).

[0144] The ECSP management system consumes the configuration MnS through the getMOIAttributes operation to obtain the UPF endpoint information attributes in upfEndpointIOC.

[0145] The 3GPP management system returns output parameters with the UPF endpoint information attribute from the upfEndpoint IOC.

[0146] If upfSelection MOI already exists:

[0147] The ECSP management system consumes configuration MnS to modify the upfSelection MOI by operating modifyMOIAttributes, in order to query the 3GPP management system for information about the UPF. The upfSelection MOI contains the EAS topology service area, the EAS geographic service area, a list of N6 traffic routing requirements, EAS connection information, and UPF selection = TRUE.

[0148] The 3GPP management system finds a UPF among the deployed UPFs based on the service area requirements (e.g., topology service area, geographic service area (see subclause 7.3.3 in TS 28.558)) and QoS requirements contained in the upfSelection IOC, and can deploy a new UPF if no UPF is found.

[0149] The 3GPP management system sends a notifyMOIAttributeValueChanges with an attributeList, which includes the DN of the upfEndpoint IOC containing UPF connection information (see subclause 11.1.1.7 in TS 28.532).

[0150] The ECSP management system consumes the configuration MnS through the getMOIAttributes operation to obtain the UPF endpoint information attributes in upfEndpointIOC.

[0151] The 3GPP management system returns output parameters with the UPF endpoint information attribute from the upfEndpoint IOC.

[0152] Accessing 5GC functionality in version 6.2.x

[0153] 6.2.x.1 Objective

[0154] The goal is to enable the ECSP management system to request the 3GPP management system to provide PCF, NEF, and SCEF connectivity information to allow EAS, EES, and ECS to access 5GC functions, such as PCF, NEF, and SCEF (see subclauses 6.3.2, 6.3.4, and 6.4.6 in TS 23.558).

[0155] 6.2.x.2 Description

[0156] 1. The ECSP management system requests the 3GPP management system to provide connection information for 5GC functions, such as the IP addresses of PCF, NEF, and SCEF.

[0157] 2.3 The GPP management system returns connection information for PCF, NEF, and SCEF to the ECSP management system.

[0158] 6.2.x.3 Requirements

[0159] REQ-ACC-5GC-FUN-1 3GPP management service producers should have the ability to allow authorized consumers to query connection information for 5GC functions such as PCF, NEF, and SCEF.

[0160] REQ-ACC-5GC-FUN-2 3GPP management service producers should have the ability to return 5GC functionality connectivity information to consumers.

[0161] 7.x Information for enabling access to 5GC features

[0162] 7.x.1 Overview

[0163] This sub-clause provides potential solutions for use cases that access 5GC functionality (see sub-clause 6.2.x).

[0164] 7.x.2 Solution

[0165] Figure 12 This demonstrates how to query the 5GC IP address via MnS configuration based on several factors. Specifically, Figure 12 The diagram illustrates how the ECSP management system requests connection information for PCF, NEF, and SCEF from the 3GPP management system via the configured MnS.

[0166] A 5GCAccessInfo IOC should be defined to enable access to 5GC features. The 5GCAccessInfo IOC should include the following properties:

[0167] A list of PCF connection information: This attribute contains PCF connection information, including the PCF identifier and PCF endpoints (e.g., IP address, DN, ...).

[0168] A list of NEF connection information: This attribute contains NEF connection information, including the NEF identifier and NEF endpoints (e.g., IP address, DN, ...).

[0169] List of SCEF connection information: This attribute contains the SCEF connection information, including the SCEF identifier and the SCEF endpoints (e.g., IP address, DN, ...).

[0170] If 5GCAccessInfo MOI does not exist:

[0171] The ECSP management system consumes the configuration MnS through the createMOI operation targeting the 5GCAccessInfo IOC to request the 3GPP management system to create a 5GCAccessInfo management object instance (MOI).

[0172] The 3GPP management system creates a 5GCAccessInfo MOI and sends a notifyMOICreation with an attribute list that includes all available connection information for PCF, NEF, and SCEF (see sub-clause 11.1.1.7 in TS28.532).

[0173] If 5GCAccessInfo MOI already exists:

[0174] The ECSP management system consumes configuration MnS by operating getMOIAttributes to obtain connection information for one or more 5GC functions (e.g., PCF, NEF, SCEF) in 5GCAccessInfoIOC.

[0175] The 3GPP management system returns output parameters for connection information with one or more 5GC functions.

[0176] MnS consumers therefore consume or use management services produced by MnS manufacturers. Each management service consists of various operations. For example, the management services configured for MnS are as follows:

[0177]

[0178]

[0179] Therefore, consumers consume management services (e.g., configure MnS) by invoking operations (e.g., createMOI operation).

[0180] TS 23.558 Sub-clause 6.3.2 (EES): The EES provides support functions for the EAS and EEC. The EES functions are: a) configuring the EEC with configuration information to enable the exchange of application data traffic with the EAS; b) providing API callers and API exposure functions as specified in 3GPP TS 23.222; c) the ability to interact with the 3GPP core network to access network functions directly (e.g., via PCF) or indirectly (i.e., via SCEF / NEF / SCEF+NEF); d) exposing events related to ACT; e) EEC context transfer between EESs; f) supporting the external exposure of 3GPP network and service capabilities to (one or more) EAS via EDGE-3; g) registration functions (i.e., registration, update, and deregistration) of (one or more) EECs and (one or more) EAS; and h) triggering EAS instantiation on demand.

[0181] TS 23.558 Subclause 6.3.4 (ECS): The ECS provides support functions for EEC-EES connectivity. The functions of the ECS are: a) to configure edge configuration information to the EEC. The edge configuration information includes the following: 1) information for the EEC to distinguish the EES (e.g., EDN service area); and 2) information for establishing a connection with the EES (e.g., URI); the ECS may be deployed in an MNO domain or may be deployed by a service provider in a third-party domain; b) to support the function of registration (i.e., registration, update, and deregistration) for one or more EES; c) to support the function of API callers and API exposure functions specified in 3GPP TS 23.222; and d) to interact with the 3GPP core network to access network functions directly (e.g., via PCF) or indirectly (i.e., SCEF / NEF / SCEF+NEF).

[0182] TS 23.558 Sub-clause 6.3.6 (EAS): An EAS is an application server residing in the EDN that performs server functions. An AC connects to an EAS to leverage the services of an application and the advantages of edge computing. The server functions of an application may be available only as an EAS. However, some server functions may also be available both at the edge and in the cloud, as an EAS and an application server residing in the cloud, respectively. The server functions provided by the EAS and its cloud application server counterparts may be the same or different; if they are different, the application data traffic exchanged with the AC may also be different. An EAS may consume 3GPP core network capabilities, all of which are optionally supported: a) by invoking 3GPP core network capabilities via the edge enablement layer through the EES; b) by directly invoking 3GPP core network function (e.g., PCF) APIs if it is a 3GPP core network trusted entity; and c) by invoking 3GPP core network capabilities through capability exposure functions (i.e., SCEF / NEF / SCEF+NEF).

[0183] In some examples, the management system's apparatus includes processing circuitry configured to operate as a 3GPP management system to: consume LCM MnS via a queryUpfInfoReq operation; receive a request from the ECSP management system to identify a UPF that can be connected to the EAS via the N6 interface; and send a queryUpfInfoResp to notify the ECSP management system and the consumer that the request is in progress; and find a UPF among the deployed UPF(s) based on the UPF selection requirements, or instantiate a new UPF if no UPF that meets the UPF selection requirements is found; and send a notification queryUpfInfoResp to inform the ECSP management system of the UPF identifier and UPF endpoint attributes, the UPF endpoint attributes containing endpoint information for the selected UPF.

[0184] UPF selection requirements include: EAS topology service area: The topology service area is defined based on the relationship between the UE and the network connection point, such as a set of cell IDs, tracking area identifiers, or PLMN IDs; and EAS geographic service area: The geographic service area is an area specified by geographic units such as geographic coordinate IDs; and a list of N6 traffic routing requirements: N6 traffic routing information and / or routing profile ID corresponding to each EAS DNAI; and EAS connection information: This attribute contains EAS connections, including EAS identifiers and EAS endpoint information.

[0185] In some examples, the management system's apparatus includes processing circuitry configured to operate as a 3GPP management system to: consume the configuration MnS via the operation createMOI for upfSelection IOC; receive requests from the ECSP management system to identify UPFs that can be connected to the EAS via the N6 interface; and the upfSelection IOC contains UPF selection requirements, finds a UPF among the deployed UPF(s)(s) based on the UPF selection requirements; or instantiates a new UPF if no UPF that meets the UPF selection requirements is found; and creates an upfSelection MOI; and sends a notification notifyMOICreation to notify the ECSP management system that the upfSelection MOI has been created.

[0186] The upfSelection IOC includes: EAS Topology Service Area: The topology service area is defined based on the relationship between the UE and the network connection point, such as a set of cell IDs, tracking area identifiers, or PLMN IDs; and EAS Geographic Service Area: The geographic service area is an area specified by geographic units such as geographic coordinate IDs; and a list of N6 traffic routing requirements: N6 traffic routing information and / or routing profile IDs corresponding to each EAS DNAI; and UPF Connection Information: This attribute is a placeholder for UPF connection information provided by the 3GPP management system; EAS Connection Information: This attribute contains EAS connections, including the EAS identifier and the DN of the easEndpoint IOC containing EAS endpoint information; and UPF Selection: This attribute relates to UPF selection.

[0187] If the USF selection is set to true, the list of EAS topology service area, EAS geographic service area, and N6 traffic routing requirements is the requirement for the 3GPP management system to select a UPF connected to EAS via the N6 interface.

[0188] The UPF connection information property contains the UPF connection, including the UPF identifier and the DN of upfEndpointIOC containing UPF endpoint information.

[0189] Upon receiving the notification MOICreation, the ECSP management system is configured to: consume configuration MnS through the getMOIAttributes operation to obtain UPF endpoint information attributes in upfEndpoint IOC; and receive output parameters containing UPF endpoint information attributes in upfEndpoint IOC.

[0190] In some examples, the management system's apparatus includes processing circuitry configured to operate as a 3GPP management system to: receive requests from the ECSP management system via the configuration MnS by modifying MOIAttributes through the upfSelection MOI operation; and the upfSelection IOC contains UPF selection requirements, finding a UPF among the deployed (one or more) UPFs based on the UPF selection requirements; or, if no UPF meeting the UPF selection requirements is found, instantiating a new UPF; and sending a notification MOIAttributeValueChanges with an attributeList including the DN of the upfEndpoint IOC containing UPF connection information to the ECSP management system.

[0191] Upon receiving the notification MOIAttributeValueChanges, the ECSP management system is configured to: consume configuration MnS through the getMOIAttributes operation to obtain UPF endpoint information attributes in the upfEndpoint IOC; and receive output parameters containing UPF endpoint information attributes in the upfEndpoint IOC.

[0192] In some examples, the management system's apparatus includes processing circuitry configured to operate as a 3GPP management system to: consume configuration MnS via an operation createMOI for a 5GCAccessInfo IOC; receive a request from the ECSP management system to create a 5GCAccessInfo IOC; create a 5GCAccessInfo MOI; and send a notification notificationMOICreation with an attribute list to the ECSP management system, the attribute list including all available connection information for PCF, NEF, and SCEF.

[0193] The 5GCAccessInfo IOC contains: a list of PCF connection information: this property contains PCF connection information, including the PCF identifier and PCF endpoints (e.g., IP address, DN, ...); a list of NEF connection information: this property contains NEF connection information, including the NEF identifier and NEF endpoints (e.g., IP address, DN, ...); and a list of SCEF connection information: this property contains SCEF connection information, including the SCEF identifier and SCEF endpoints (e.g., IP address, DN, ...).

[0194] In some examples, the management system's apparatus includes processing circuitry configured to operate as a 3GPP management system to: consume configuration MnS via the getMOIAttributes operation, receive requests from the ECSP management system to obtain 5GC functionality connection information, and return output parameters with 5GC functionality connection information.

[0195] While embodiments have been described with reference to specific exemplary examples, it will be understood that various modifications and changes can be made to these embodiments without departing from the broader scope of this disclosure. Therefore, the specification and drawings should be considered illustrative rather than restrictive. The accompanying drawings, which form a part of this document, illustrate specific embodiments that can implement the subject matter in an illustrative and not limiting manner. The illustrated embodiments have been described in sufficient detail to enable those skilled in the art to implement the teachings disclosed herein. Other embodiments can be utilized and derived from them, thereby allowing structural and logical substitutions and changes to be made without departing from the scope of this disclosure. This detailed description section should therefore not be construed in a limiting sense, and the scope of the various embodiments is defined only by the appended claims and the full scope of their equivalents.

[0196] The subject matter may be referred to herein individually and / or generally by the term "embodiment," for convenience only, and is not intended to actively limit the scope of this application to any single inventive concept if more than one is actually disclosed. Thus, while specific embodiments have been illustrated and described herein, it should be understood that any arrangement intended to achieve the same purpose may substitute for the specific embodiments shown. This disclosure is intended to cover any and all adaptive changes or variations of the various embodiments. Those skilled in the art will readily derive combinations of the above embodiments and other embodiments not specifically described herein upon reading the foregoing description.

[0197] In this document, as is common in patent documents, the terms “a” or “an” are used to include one or more, independent of any other instance or use of “at least one” or “one or more.” In this document, the term “or” is used to refer to a non-exclusive “or,” such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In this document, the terms “comprising” and “in which” are used as concise English equivalents to the corresponding terms “including” and “wherein.” Furthermore, in the appended claims, the terms “comprising” and “including” are open-ended, meaning that a system, UE, article, composition, formulation, or process that includes other elements besides those listed after such terms in the claims is still considered to fall within the scope of the claims. Additionally, in the appended claims, the terms “first,” “second,” and “third,” etc., are used merely as labels and are not intended to impose numerical requirements on their objects.

[0198] The abstract of this disclosure is provided to comply with 37C.FR1.72(b), which requires an abstract that allows the reader to quickly determine the nature of the technical disclosure. The abstract is submitted under the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, as can be seen in the foregoing Detailed Description section, various features are grouped together in a single embodiment for the purpose of simplification. This approach to disclosure should not be construed as reflecting a desire to claim embodiments that require more features than expressly recited in each claim. Rather, as reflected in the appended claims, the inventive subject matter is present in fewer than all the features of a single disclosed embodiment. Therefore, the appended claims are incorporated into the Detailed Description section, wherein each claim stands alone as a separate embodiment.

Claims

1. An apparatus for managing a system, the apparatus comprising: The processing circuit is configured as follows: Decode the request from the Edge Computing Service Provider (ECSP) management system to identify the User Plane Function (UPF) to connect to the Edge Application Server (EAS) via the N6 interface. Based on the UPF selection attribute and Quality of Service (QoS) attribute in the request, determine whether the UPF in the deployed UPF meets the request; In response to determining that no UPF in the deployed UPFs satisfies the request, an instantiated UPF that satisfies the request is created; otherwise, a UPF that satisfies the request is selected from the deployed UPFs. as well as The encoding includes a notification of UPF information for the UPF that satisfies the request, for transmission to the ECSP management system; as well as The memory is configured to store the UPF information. The request is based on one of the following: via queryUpfInfoReq Operational Consumer Lifecycle Management (LCM) Management Service (MnS), provided by the ECSP management system through targeted... upfSelection Information Object Class (IOC) createMOI The operation is used to consume the configured MnS, or by the ECSP management system through... modifyMOIAttributes Operation consumption configuration MnS to modify upfSelection IOC upfSelection Manage Object Instances (MOIs).

2. The apparatus of claim 1, wherein, The UPF selection attributes include a list of N6 traffic routing attributes and service area elements, wherein the service area elements include topology service areas and geographic service areas.

3. The apparatus of claim 2, wherein, The N6 traffic routing attributes include at least one of a routing profile identifier (ID) corresponding to the EAS's Data Network Access Identifier (DNAI) or N6 traffic routing information.

4. The apparatus of claim 1, wherein: The notification includes queryUpfInfoResp operate.

5. The apparatus of claim 4, wherein, The processing circuitry is further configured to: in response to receiving the request, encode an additional notification for transmission to the ECSP management system, the additional notification indicating that the request is in progress, the notification including... queryUpfInfoResp operate.

6. The apparatus of claim 1, wherein, The UPF information includes a UPF identifier and UPF endpoint attributes containing endpoint information of the UPF.

7. The apparatus of claim 1, wherein: The upfSelection The IOC includes: a topology service area, a geographic service area, a list of N6 traffic routing attributes, UPF connection information, EAS connection information, and a UPF selection value, which is set to "true" to indicate that the request will select the UPF. The N6 traffic routing attributes include at least one of a routing profile identifier (ID) corresponding to the EAS Data Network Access Identifier (DNAI) or N6 traffic routing information. The UPF connection information includes a UPF identifier and upfEndpoint The domain name (DN) of the IOC, upfEndpoint The IOC contains UPF endpoint information, and The EAS connection information includes the EAS identifier and easEndpoint The DN of IOC, easEndpoint The IOC contains EAS endpoint information.

8. The apparatus of claim 1, wherein, The processing circuit is configured to create upfSelection Manage object instances (MOIs) and encode those with attributeLists. notifyMOICreation MOI is used for transmission to the ECSP management system, and the attributeList includes upfEndpoint The domain name (DN) of the IOC, upfEndpoint The IOC contains the UPF connection information.

9. The apparatus of claim 1, wherein: The upfSelection The IOC includes: topology service area, geographic service area, and the QoS attribute.

10. The apparatus of claim 9, wherein, The processing circuit is configured to encode an attributeList. notifyMOImodifyMOIAttributes MOI is used for transmission to the ECSP management system, and the attributeList includes upfEndpoint The domain name (DN) of the IOC, upfEndpoint The IOC contains the UPF connection information.

11. The apparatus of claim 9, wherein, The processing circuit is configured as follows: Decode the connection request from the ECSP management system for the EAS to the mobile network function, which includes mobile network connection information for the EAS for the Policy Control Function (PCF), Service Capability Exposure Function (SCEF), and Network Exposure Function (NEF). In response to a request for the mobile network function, the mobile network connection information is encoded for transmission to the ECSP management system.

12. The apparatus of claim 1, wherein: Decoding the data from the ECSP management system 5GCAccessInfo The Configuration Management Service (MnS) for Information Object Classes (IOCs) enables access to 5th Generation Core Network (5GC) functions, including connection information for the EAS for Policy Control Function (PCF), Service Capability Exposure Function (SCEF), and Network Exposure Function (NEF). In response to a request for connection information for the EAS, the connection information for the EAS is encoded for transmission to the ECSP management system.

13. The apparatus of claim 12, wherein, The connection information includes: PCF connection information, including PCF identifier and PCF endpoint information. NEF connection information, including the NEF identifier and NEF endpoint, and SCEF connection information, including the SCEF identifier and SCEF endpoint.

14. The apparatus of claim 1, wherein, The processing circuit is configured as follows: In response to the ECSP management system via targeting 5GCAccessInfo Operations of Information Object Class (IOC) createMOI Consumer configuration MnS to request creation 5GCAccessInfo Manage Object Instances (MOIs), Create 5GCAccessInfo MOI, and Encoding has attributeList of notifyMOICreation The notification is for transmission to the ECSP management system, the attributeList This includes available connectivity information for the Policy Control Function (PCF), Service Capability Exposure Function (SCEF), and Network Exposure Function (NEF).

15. The apparatus of claim 1, wherein, The processing circuit is configured to: respond to the ECSP management system via a specific... 5GCAccessInfo Operations of Information Object Class (IOC) getMOIAttributes The consumer configures MnS to request connection information for 5th generation core network (5GC) functions, and provides the ECSP management system with connection information for Policy Control Function (PCF), Service Capability Exposure Function (SCEF), and Network Exposure Function (NEF).

16. An apparatus for an edge computing service provider (ECSP), the apparatus comprising: The processing circuit is configured as follows: The encoding is for a request for UPF information to be connected to the User Plane Function (UPF) of the Edge Application Server (EAS) via the N6 interface for transmission to the 3GPP management system. The encoding is independent of whether the UPF exists among multiple existing UPFs or whether a new UPF will be deployed based on the request. The request includes service area attributes, N6 traffic routing attributes and quality of service (QoS) attributes. as well as Decode the notification containing the UPF information from the 3GPP management system; as well as The memory is configured to store the UPF information. The request is based on one of the following: via queryUpfInfoReq Operational Consumer Lifecycle Management (LCM) Management Service (MnS), provided by the ECSP management system through targeted... upfSelection Information Object Class (IOC) createMOI The operation is used to consume the configured MnS, or by the ECSP management system through... modifyMOIAttributes Operation consumption configuration MnS to modify upfSelection IOC upfSelection Manage Object Instances (MOIs).

17. A computer-readable storage medium storing instructions for execution by one or more processors of a 3GPP management system, wherein, when the instructions are executed, the one or more processors are configured to configure the 3GPP management system to: Decode the request from the Edge Computing Service Provider (ECSP) management system to identify the User Plane Function (UPF) to connect to the Edge Application Server (EAS) via the N6 interface. Based on the UPF selection attribute and Quality of Service (QoS) attribute in the request, determine whether the UPF in the deployed UPF meets the request; In response to determining that no UPF in the deployed UPFs satisfies the request, an instantiated UPF that satisfies the request is created; otherwise, a UPF that satisfies the request is selected from the deployed UPFs. as well as The encoding includes a notification of UPF information for the UPF that satisfies the request, for transmission to the ECSP management system. The request is based on one of the following: via queryUpfInfoReq Operational Consumer Lifecycle Management (LCM) Management Service (MnS), provided by the ECSP management system through targeted... upfSelection Information Object Class (IOC) createMOI The operation is used to consume the configured MnS, or by the ECSP management system through... modifyMOIAttributes Operation consumption configuration MnS to modify upfSelection IOC upfSelection Manage Object Instances (MOIs).

Images