CN116601929A

CN116601929A - Edge computation to 5GC function connection

Info

Publication number: CN116601929A
Application number: CN202280008142.5A
Authority: CN
Inventors: 乔伊·周; 姚羿志
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2021-01-13
Filing date: 2022-01-12
Publication date: 2023-08-15
Also published as: WO2022155200A1

Abstract

An apparatus and system for providing support for connection of edge computation functionality to 5GC functionality is described. An Edge Computing Service Provider (ECSP) management system collects connection information of 5GC functions including a Policy Control Function (PCF), a service capability disclosure function (SCEF), and a network disclosure function (NEF) to connect an Edge Application Server (EAS), an Edge Enablement Server (EES), and an Edge Configuration Server (ECS). The request for information by the 3GPP management system is based on the consumption of provisioning MnS by the ECSP management system through the queryUpfInfoReq operation Consumer lifecycle management (LCM) management service (MnS) or through the upfSelection Information Object Class (IOC).

Description

Edge computation to 5GC function connection

Priority statement

The present application claims the priority of U.S. provisional patent application serial No. 63/136,736 filed on day 2021, month 1, and 13, which application is incorporated herein by reference in its entirety.

Technical Field

Embodiments relate to next generation wireless communications. In particular, some embodiments relate to edge computation in 5G networks.

Background

The use and complexity of wireless systems, including 5 th generation (5G) networks and beginning to include 6 th generation (6G) networks, etc., has increased due to the increase in device types of User Equipment (UEs) that use network resources and the increase in the amount of data and bandwidth used by various applications (e.g., video streaming) operating on these UEs. With the substantial increase in the number and diversity of communication devices, the corresponding network environments (including routers, switches, bridges, gateways, firewalls, and load balancers) have become increasingly complex. Without this, the advent of any new technology presents a number of problems.

Drawings

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The accompanying drawings generally illustrate by way of example, and not by way of limitation, the various embodiments discussed in the present document.

Fig. 1A illustrates an architecture of a network in accordance with some aspects.

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

Fig. 3 illustrates a 5G edge computing network, according to some embodiments.

Fig. 4 illustrates a peer-to-peer (P2P) edge computing management deployment in accordance with some embodiments.

Fig. 5 illustrates an architecture for enabling edge applications according to some embodiments.

Fig. 6 illustrates an inter-edge detection network (inter-EDN) in accordance with some embodiments.

Fig. 7 illustrates an intra-edge detection network (intra-EDN) according to some embodiments.

FIG. 8 illustrates service provider relationships in an edge computing network deployment according to some embodiments.

Fig. 9 illustrates an edge computing network in accordance with some embodiments.

Fig. 10 illustrates User Plane Function (UPF) selection via lifecycle management (LCM) management service (MnS), according to some embodiments.

Fig. 11 illustrates UPF selection via provisioning MnS, according to some aspects.

Fig. 12 illustrates querying a 5 th generation core (5 GC) Internet Protocol (IP) address via provisioning MnS, according to some aspects.

Detailed Description

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may involve structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of others. The embodiments set forth in the claims include all available equivalents of those claims.

Fig. 1A illustrates an architecture of a network in accordance with some aspects. Network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Thus, while reference will be made to 5G, it should be understood that this can be extended to 6G structures, systems and functions. The network functions may be implemented as discrete network elements on dedicated hardware, as software instances running on dedicated hardware, and/or as virtualized functions instantiated on an appropriate platform (e.g., dedicated hardware or cloud infrastructure).

Network 140A is shown to include User Equipment (UE) 101 and UE 102. The UEs 101 and 102 are shown as smartphones (e.g., handheld touch screen mobile computing devices connectable 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 handset, a drone, or any other computing device including wired and/or wireless communication interfaces. The UEs 101 and 102 may be collectively referred to herein as UE 101, and the UE 101 may be configured to perform one or more of the techniques disclosed herein.

Any of the radio links described herein (e.g., as used in network 140A or any other illustrated network) may operate according to any of the example radio communication techniques and/or standards. Any spectrum management scheme includes, for example, private licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., licensed Shared Access (LSA) in 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz, and other frequencies, and Spectrum Access System (SAS) in 3.55-3.7GHz and other frequencies). Different single carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multi-carrier (FBMC), OFDMA, etc.), in particular 3GPP NR, may be used by allocating OFDM carrier data bit vectors to the corresponding symbol resources.

In some aspects, either of the UEs 101 and 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 that utilize short-lived UE connections. In some aspects, either of the UEs 101 and 102 may include Narrowband (NB) IoT UEs (e.g., enhanced NB-IoT (eNB-IoT) UEs and further enhanced (FeNB-IoT) UEs). IoT UEs may utilize technologies such as machine-to-machine (M2M) or Machine Type Communication (MTC) for exchanging data with MTC servers or devices through Public Land Mobile Networks (PLMNs), proximity-based services (ProSe) or device-to-device (D2D) communications, sensor networks, or IoT networks. The M2M or MTC data exchange may be a machine initiated data exchange. The IoT network includes interconnected IoT UEs that may include uniquely identifiable embedded computing devices (within the internet infrastructure) with short-lived connections. The IoT UE may execute a background application (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network. In some aspects, either of the UEs 101 and 102 may include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

The UEs 101 and 102 may be configured to connect (e.g., communicatively couple) with a Radio Access Network (RAN) 110. RAN 110 may be, for example, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or other type of RAN.

The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces that enable communicative coupling, and may conform to cellular communication protocols, such as global system for mobile communications (GSM) protocols, code Division Multiple Access (CDMA) network protocols, push-to-talk (PTT) protocols, PTT Over Cellular (POC) protocols, universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, 6G protocols, and so forth.

In one aspect, the UEs 101 and 102 may further exchange communication data directly through the ProSe interface 105. ProSe interface 105 may also be referred to as a Side Link (SL) interface that includes one or more logical channels including, but not limited to, a physical side link control channel (PSCCH), a physical side link shared channel (PSSCH), a physical side link discovery channel (PSDCH), a physical side link broadcast channel (PSBCH), and a physical side link feedback channel (PSFCH).

UE 102 is shown configured to access an Access Point (AP) 106 via a connection 107. Connection 107 may comprise a local wireless connection, e.g., a connection conforming to any IEEE 802.11 protocol, according to which AP 106 may comprise wireless fidelityAnd a router. In this example, the AP 106 is shown connected to the internet and not to the core network of the wireless system (described in further detail below).

RAN 110 may include one or more access nodes that enable connections 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., cell). In some aspects, communication nodes 111 and 112 may be transmission/reception points (TRP). In the case where the 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 femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacities, or higher bandwidths than macro cells).

Either of the RAN nodes 111 and 112 may terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, either of RAN nodes 111 and 112 may 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 data packet scheduling, and mobility management. In an example, any of nodes 111 and/or 112 may be a gNB, eNB, or other type of RAN node.

RAN 110 is shown communicatively coupled to a Core Network (CN) 120 through an S1 interface 113. In various aspects, the 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., as shown with reference to fig. 1B-1C). In this aspect, the S1 interface 113 is divided into two parts: an S1-U interface 114 that carries traffic data between RAN nodes 111 and 112 and serving gateway (S-GW) 122; and an S1 Mobility Management Entity (MME) interface 115, which is a signaling interface between RAN nodes 111 and 112 and MME 121.

In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124.MME 121 may be similar in function to the control plane of a conventional serving General Packet Radio Service (GPRS) support node (SGSN). MME 121 may manage mobility aspects in the access such as gateway selection and tracking area list management. HSS 124 may include a database of network users including subscription-related information used to support network entity handling communication sessions. The CN 120 may include one or several HSS 124 depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc. For example, the HSS 124 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like.

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

The P-GW 123 may terminate the SGi interface towards the PDN. The P-GW 123 may route data packets between the CN 120 and external networks, e.g., networks including an application server 184 (or referred to as an Application Function (AF)), through an Internet Protocol (IP) interface 125. The P-GW 123 may also transmit data to other external networks 131A, which other external networks 131A may include the internet, an IP multimedia Subsystem (IPs) network, and other networks. In general, the application server 184 may be an element that provides an application that uses IP bearer resources with a 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 through IP interface 125. The application server 184 may 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 the UEs 101 and 102 through the CN 120.

The P-GW 123 may also be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with an internet protocol connectivity access network (IP-CAN) session of the UE. In a roaming scenario with local traffic disruption, there may be two PCRFs associated with the IP-CAN session of the UE: a home PCRF (H-PCRF) within the HPLMN, and a visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). PCRF 126 may be communicatively coupled to application server 184 through P-GW 123.

In some aspects, the communication network 140A may be an IoT network or a 5G or 6G network, including a 5G new radio network that uses communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current IoT implementations is the narrowband IoT (NB-IoT). Operations in the unlicensed spectrum may include Dual Connectivity (DC) operations and independent LTE systems in the unlicensed spectrum according to which LTE-based techniques operate only in the unlicensed spectrum without using "anchors" in the licensed spectrum, known as multewire. In future releases and 5G systems, it is desirable to further enhance the operation of LTE systems in licensed and unlicensed spectrum. Such enhanced operations may include techniques for side link resource allocation and UE processing behavior for NR side link V2X communications.

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

In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, or the like. In some aspects, in a 5G architecture, the gNB may be a Master Node (MN) and the NG-eNB may be a Slave Node (SN).

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, fig. 1B shows a 5G system architecture 140B, represented by a reference point, which can be extended to a 6G system architecture. More specifically, UE 102 may communicate with RAN 110 and one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of Network Functions (NF), 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)/Home Subscriber Server (HSS) 146.

The UPF 134 may provide a connection to a Data Network (DN) 152, which may include, for example, operator services, internet access, or third party services. The AMF 132 may be used to manage access control and mobility and may also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. The SMF 136 may be configured to set up and manage various sessions according to network policies. Thus, the SMF 136 may be responsible for session management and assignment of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transmission. The SMF 136 may be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. Each session may be assigned a different SMF. Using different SMFs may allow each session to be managed separately. Thus, the functionality of each session may be independent of the other.

The UPF 134 can be deployed in one or more configurations depending on the type of service desired and can be connected to a data network. PCF 148 may be configured to provide a policy framework (similar to PCRF in 4G communication systems) that uses network slicing, mobility management, and roaming. The UDM may be configured to store subscriber profiles and data (similar to HSS in a 4G communication system).

AF 150 may provide information about the packet flow to PCF 148 responsible for policy control to support the desired QoS. PCF 148 may set mobility and session management policies for UE 101. To this end, PCF 148 may use the packet flow information to determine an appropriate policy for the appropriate operation of AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

In some aspects, the 5G system architecture 140B includes an IP Multimedia Subsystem (IMS) 168B and a plurality of IP multimedia core network subsystem entities, such as Call Session Control Functions (CSCFs). More specifically, the IMS 168B includes CSCFs that may act as proxy CSCF (P-CSCF) 162B, serving CSCF (S-CSCF) 164B, emergency CSCF (E-CSCF) (not shown in FIG. 1B), or interrogating CSCF (I-CSCF) 166B. P-CSCF 162B may be configured to be the first point of contact for UE 102 within IM Subsystem (IMs) 168B. S-CSCF 164B may be configured to handle session states in the network and E-CSCF may be configured to handle certain aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. I-CSCF 166B may be configured to act as a point of contact for all IMS connections within the operator's network that are destined for subscribers of the network operator or roaming subscribers currently located within the service area of the network operator. In some aspects, I-CSCF 166B may be connected to another IP multimedia network 170E, e.g., an IMS operated by a different network operator.

In some aspects, the UDM/HSS 146 may be coupled to an application server 160E, which application server 160E may include a Telephony Application Server (TAS) or other Application Server (AS). AS 160B may be coupled to IMS 168B through S-CSCF 164B or I-CSCF 166B.

The reference point representation shows that there may be interactions between the corresponding NF services. For example, fig. 1B shows the following reference points: 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 two UPF 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between PCF 148 and AMF 132 in the case of a non-roaming scenario, or between PCF 148 and AMF 132, not shown), N16 (between AMF 142 and nsf 132, not shown), N11 (between AMF 132 and nsf 132, not shown). Other reference point representations not shown in fig. 1B may also be used.

Fig. 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in fig. 1B, the system architecture 140C may also include a Network Exposure Function (NEF) 154 and a Network Repository Function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and interactions between network functions may be represented by respective point-to-point reference points Ni, or as service-based interfaces.

In some aspects, as shown in fig. 1C, the service-based representation may be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this aspect, 5G system architecture 140C may include the following service-based interfaces: namf 158H (service-based interface presented by AMF 132), nsmf 158I (service-based interface presented by SMF 136), nnef 158B (service-based interface presented by NEF 154), npcf 158D (service-based interface presented by PCF 148), nudm 158E (service-based interface presented by UDM 146), naf 158F (service-based interface presented by AF 150), nnrf 158C (service-based interface presented by NRF 156), nnssf 158A (service-based interface presented by NSSF 142), nausf 158G (service-based interface presented by AUSF 144). Other service-based interfaces not shown in fig. 1C (e.g., nudr, N5g-eir, and Nudsf) may also be used.

The NR-V2X architecture may support high reliability low latency side link communications with multiple traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein may be used to support high reliability in distributed communication systems with dynamic topologies, including side link NR V2X communication systems.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE (e.g., a dedicated computer, a personal or laptop computer (PC), a tablet PC, or a smart phone), a dedicated network device (e.g., an eNB), server running software configuring a server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequentially or otherwise) specifying actions to be taken by the machine. For example, the communication device 200 may be implemented as one or more of the devices shown in fig. 1A-1C. Note that the communications described herein may be encoded prior to transmission by a transmitting entity (e.g., UE, gNB) for receipt by a receiving entity (e.g., gNB, UE) and decoded after receipt by the receiving entity.

Examples as described herein may include or may operate on logic or several components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) that are capable of performing specified operations and that may be configured or arranged in a manner. In an example, the circuits may be arranged as modules in a specified manner (e.g., internally or to an external entity, such as other circuits). In an example, all or part of one or more computer systems (e.g., stand-alone, 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) as modules that operate to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

Thus, the term "module" (and "component") is understood to encompass a tangible entity, be it physically constructed, a specially configured (e.g., hardwired), or a temporarily (e.g., transient) configured (e.g., programmed) entity to operate in a specified manner or to perform some or all of any of the operations described herein. Considering the example where modules are temporarily configured, it is not necessary to instantiate each module at any one time. For example, where a module includes a general-purpose hardware processor configured with software, the general-purpose hardware processor may be configured as each of the different modules at different times. The software may accordingly configure the hardware processor to constitute one particular module at one time and another module at another time, for example.

The communication device 200 may include a hardware processor (or equivalent processing circuit) 202 (e.g., a Central Processing Unit (CPU), GPU, hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an interconnect (e.g., bus) 208. Main memory 204 may include any or all of removable storage and non-removable storage, volatile memory, or nonvolatile 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 an example, display unit 210, input device 212, and UI navigation device 214 may be touch screen displays. 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, compass, accelerometer, or other sensor. The communication device 200 may also include an output controller, such as a 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.).

The storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter machine-readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within the static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine-readable medium 222 is shown to be a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.

The term "machine-readable medium" can include any medium that can store, encode, or carry instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of this disclosure, or that can store, encode, or carry data structures used by or associated with such instructions. Non-limiting examples of machine readable media may include solid state memory, as well as optical and magnetic media. Specific examples of machine-readable media may include: nonvolatile 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 disk; random Access Memory (RAM); CD-ROM and DVD-ROM discs.

The instructions 224 may also be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 using any of a number of Wireless Local Area Network (WLAN) transmission 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 a Local Area Network (LAN), a Wide Area Network (WAN), a packet data network (e.g., the internet), a mobile telephone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, and a wireless data network. Communications over the network may include one or more different protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards (referred to as Wi-Fi), the IEEE 802.16 family of standards (referred to as WiMax), the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, point-to-point (P2P) networks, the Next Generation (NG)/fifth generation (5G) standards, and so forth. In an example, the network interface device 220 may include one or more physical jacks (e.g., ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the transmission medium 226.

Note that the term "circuitry" as used herein refers to, is part of, or includes, hardware components configured to provide the described functionality, such as electronic circuitry, logic circuitry, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a Field Programmable Device (FPD) (e.g., a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a Complex PLD (CPLD), a high-capacity PLD (hcpll), a structured ASIC, or a programmable SoC), a Digital Signal Processor (DSP), or the like. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for performing the functions of the program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

Thus, the term "processor circuit" or "processor" as used herein refers to, is part of, or includes the following circuitry: the circuit is 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 refer to one or more application processors, one or more baseband processors, a physical Central Processing Unit (CPU), a single 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).

Any of the radio links described herein may operate in accordance with 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 communications technology, general Packet Radio Service (GPRS) radio communications technology, enhanced data rates for GSM evolution (EDGE) radio communications technology, and/or third generation partnership project (3 GPP) radio communications 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 (CDMA 2000), cellular Digital Packet Data (CDPD), mobitex, third generation (3G), circuit Switched Data (CSD), high Speed Circuit Switched Data (HSCSD), universal mobile telecommunications system (third generation) (UMTS (3G)), wideband code division multiple access (universal mobile telecommunications system) (W-CDMA (UMTS)), high Speed Packet Access (HSPA), high Speed Downlink Packet Access (HSDPA), high Speed Uplink Packet Access (HSUPA), high speed packet access+ (a+), universal mobile telecommunications system time division duplex (UMTS-TDD), time division multiple access (HSPA-CDMA), time division multiple access (TD-synchronization (TD), third generation partnership project (TD-4) (3G), release 4 (release 4, release 4 (release 9.3G)), wideband code division multiple access (3 partnership project 4 (3G), 3GPP release 4 (release 9, release 4, 3.3G) 3GPP rel.11 (3 rd generation partnership project release 11), 3GPP rel.12 (3 rd generation partnership project release 12), 3GPP rel.13 (3 rd generation partnership project release 13), 3GPP rel.14 (3 rd generation partnership project release 14), 3GPP rel.15 (3 rd generation partnership project release 15), 3GPP rel.16 (3 rd generation partnership project release 16), 3GPP rel.17 (3 rd generation partnership project release 17) and subsequent releases (e.g., rel.18, rel.19, etc.), 3GPP 5G, 5G new radio (5G NR), 3GPP 5G new radio, 3GPP LTE extension, LTE advanced specialty, LTE Licensed Assisted Access (LAA), muLTEfire, UMTS Terrestrial Radio Access (UTRA), evolved UMTS terrestrial radio access (E-UTRA), long term evolution advanced (fourth generation) (LTE advanced (4G)), cdmaOne (2G), code division multiple access 2000 (third generation) (CDMA 2000 (3G)), optimized evolution data or evolution-only data (EV-DO), advanced mobile phone system (first generation) (AMPS (1G)), full access communication system/extended full access communication system (TACS/ETACS), digital AMPS (second generation) (D-AMPS (2G)), push-to-talk (PTT), mobile phone system (MTS), improved mobile phone system (IMTS), advanced mobile phone system (AMTS), norway (Offentlig Landmobil Telefoni, public land mobile phone) MTD (abbreviation of Swedish Mobiltelefonisystem D, or mobile phone system D), public automated land Mobile (Autotel/PALM), ARP (Autoloadiopuhin, "automotive radiotelephone"), NMT (Nordic Mobile telephone), a high capacity version of NTT (Japanese telecom telephone) (Hicap), cellular Digital Packet Data (CDPD), mobitex, dataTAC, integrated Digital Enhanced Network (iDEN), personal Digital Cellular (PDC), circuit Switched Data (CSD), personal handhelds phone 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 systems operating at 10-300GHz and above, such as Wigig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating at 300GHz and THz bands, (reporting to other systems (e.g., systems operating in accordance with the 3GPP/LTE, IEEE 802.11, IEEE 11 or other short range communication systems (35) or other vehicles (usually by the public transport infrastructure) in accordance with the standard of 3GPP universal access network or GAN), zigbee, bluetooth (r), wireless gigabit (Wigig., IEEE 802.11ad, IEEE 802.11ay, and IEEE 2 MHz, and other vehicles (usually reporting (35) systems, 3 MHz and other communication infrastructure (35) systems, 3 MHz, 4 to the vehicle infrastructure (35) and other vehicles are usually the communication infrastructure (35) and (35) systems and the communication infrastructure (35) are generally, and the infrastructure (35I and 2 systems are generally the system and the infrastructure (2), the European style of IEEE 802.11 p-based DSRC includes ITS-G5A (i.e., ITS-G5 operated in the European ITS band dedicated to safety-related applications in the frequency range 5875GHz to 5905 GHz), ITS-G5B (i.e., operated in the European ITS band dedicated to ITS non-safety applications in the frequency range 5855GHz to 5875 GHz), ITS-G5C (i.e., ITS application operated in the frequency range 5470GHz to 5725 GHz)), DSRC in Japan in the 700MHz band (including 715MHz to 725 MHz), IEEE 802.11 bd-based systems, and so forth.

The various aspects described herein may be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, licensed exempt spectrum, (licensed) shared spectrum (e.g., licensed Shared Access (LSA) in frequencies 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz and above, and Spectrum Access System (SAS)/Citizen Broadband Radio System (CBRS) in frequencies 3.55-3.7GHz and above). Suitable spectral bands include IMT (international mobile communications) spectrum and other types of spectrum/bands such as bands with national allocations (including 450-470MHz, 902-928MHz (note: e.g., allocated in US (FCC part 15)), 863-868.6MHz (note: e.g., allocated in the european union (ETSI EN 300 220)), 915.9-929.7MHz (note: e.g., allocated in japan), 917-923.5MHz (note: e.g., allocated in 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: which is an ISM band with global availability), and which is used by the-Fi technology series (11 b/g/n/ax) and bluetooth), 2500-2690MHz, 698-790MHz, 610-790.7 MHz, 0-3600MHz, 0-3 MHz, and 3.7 MHz (note: e.g., allocated in china), and 3-2025 MHz (note: e.25.g., allocated in EU), and 775.725 (note: e.g., allocated in EU 5 i.25-5 GHz), total, and 60.725 (note: e.g., allocated in EU 25-5.g., EU 5 MHz), and 60-5.725 (see e.g., normal bands such as those in EU 25.25.25.25.25.725, 25.725, which are allocated in the whole, and 60.725 radio bands (e.g., the internet bands). The next generation Wi-Fi system is expected to include the 6GHz spectrum as the operating band, but notably, by 12 months in 2017, wi-Fi systems have not been allowed to be used in that band. The regulations are expected to be completed in 2019-2020, IMT advanced spectrum, IMT-2020 spectrum (which is expected to include 3600-3800MHz, 3800-4200MHz, 3.5GHz band, 700MHz band, 24.25-86GHz band, etc.), spectrum available under the FCC "front of spectrum" 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, 92-94GHz, etc.), ITS (intelligent transportation system) band currently allocated to WiGig (e.g., wiGig band 1 (57.24-59.40 GHz), wiGig band 2 (59.40-61.56 GHz), and wig 3GHz (61.56-63.72 GHz), and wig band (78-96 GHz), and a total of which is allocated to the radio spectrum (e.g., 35-96 GHz) and 35GHz band (which is allocated to the future radio system) of 35.85-5.85-5.925 GHz and 63-64GHz, and the other bands (e.g., 35-64 GHz), and the other bands (which are allocated to the future radio bands (e.g., 35-96 GHz) of the future radio system) are allocated to the future radio bands (35-71 GHz and 35 GHz-96 GHz) and 35GHz (which are allocated to the future-allocated portions of the radio bands (e.g.g.g.35-71-35 GHz and 35-71 and 35 GHz-71, and 35-71-15) and the future-allocated to the future-allocated bands). Furthermore, the scheme may be used on the basis of assistance of frequency bands such as the TV white space band (typically below 790 MHz), with 400MHz and 700MHz frequency bands being promising candidate frequency bands. In addition to cellular applications, specific applications in the vertical market may also be addressed, such as PMSE (programming and special events), medical, health, surgical, automotive, low latency, drone, etc. applications.

Various aspects described herein can also enable hierarchical application of an aspect, such as by introducing hierarchical usage priorities for different types of users (e.g., low/medium/high priority, etc.) based on priority access to spectrum, such as a level 1 user having the highest priority, followed by a level 2 user, followed by a level 3 user, etc.

Various aspects described herein may also be applied to different single carriers or OFDM types (CP-OFDM, SC-FDMA, SC-OFDM, filter group based multi-carrier (FBMC), OFDMA, etc.), by allocating OFDM carrier data bit vectors to corresponding symbol resources (in particular, 3GPP NR (new radio)).

Some features in this document are defined for the network side, e.g. AP, eNB, NR, or gNB, noting that this term is commonly used in the context of 3gpp 5G and 6G communication systems, etc. Nonetheless, the UE may also play this role and act as an AP, eNB or gNB; that is, some or all of the features defined for the network device may be implemented by the UE.

As described above, 5G networks surpass traditional mobile broadband services to provide a variety of new services, such as internet of things (IoT), industrial control, autopilot, mission critical communications, etc., that may have ultra-low latency, ultra-high reliability, and high data capacity requirements for security and performance considerations. Edge computing has been added as a feature to 5G core (5 GC) system architecture to support such services by hosting some applications closer in the local data network in order to reduce end-to-end latency and load on the transport network. Fig. 3 illustrates a 5G edge computing network, according to some embodiments.

Fig. 4 illustrates a P2P edge computing management deployment in accordance with some embodiments. In the deployment shown in fig. 4, edge computation in a 3GPP network involves communication between a 3GPP management system, a non-3 GPP management system, including an edge computation management system, and ETSI Network Function Virtualization (NFV) management and orchestration (MANO).

Deployment of edge computation in 3GPP networks utilizes cooperation with other Standard Development Organizations (SDOs) because Application Functions (AFs) and Application Servers (AS) are not 3 GPP-defined nodes. Deploying network functions supporting edge computation in 3GPP networks and non-3 GPP networks involves communication between 3GPP management systems and non-3 GPP management systems.

In the example of fig. 4, the 3GPP management system may initiate edge computing deployment by: the edge computing management system is requested to deploy a local data network and a network function virtualization coordinator (NFVO) is requested to connect the UPF and the local data network, wherein a connection (e.g., a virtual link) between the UPF and the local data network has a quality of service (QoS) required for N6. The edge computing management system may initiate edge computing deployment by: the 3GPP management system is requested to deploy UPF and NFVO to connect the UPF and the local data network, wherein QoS requirements are imposed on the connection between the UPF and the local data network.

FIG. 5 illustrates an architecture for enabling deployment of edge applications. In this architecture, the application client is an application residing in the UE that performs the client function(s), and the Edge Application Server (EAS) is an application server residing in an edge data network that is a local data network that performs the server function. The application client connects to an edge application server to take advantage of (or obtain) the services of applications with edge computing advantages.

Fig. 5 illustrates an application architecture for enabling edge applications. The edge data network is a local data network. Edge application server(s) and Edge Enabled Server (EES) are contained in the EDN. An Edge Configuration Server (ECS) provides configuration related to EES, including details of the edge data network hosting the EES. The UE includes application client(s) and edge-enabled clients. The edge application server(s), edge enablement server, and edge configuration server may interact with the 3GPP core network.

EDGE-1 reference points support interactions between EDGE-enabled servers and EDGE-enabled clients that are related to enabling EDGE computing. EDGE-1 reference point support: registering and deregistering an edge-enabled client to an edge-enabled server; retrieving and provisioning configuration information for the UE; and discovery of available edge application servers in the edge data network.

EDGE-2 reference points support EDGE-enabled layer related interactions between EDGE-enabled servers and 3GPP networks. EDGE-2 reference point support: the 3GPP network functions and Application Programming Interfaces (APIs) are accessed to retrieve network capability information, e.g., via service capability disclosure functions (SCEF) and network disclosure functions (NEF) APIs, and wherein EES acts as a trusted AF in the 5 GC. EDGE-2 reference point reuse SA2 defined 3GPP reference point, N33, or EPS or 5GS interfaces that consider different deployment models.

EDGE-3 reference points support interactions between EDGE-enabled servers and EDGE application servers that are related to the EDGE-enabled layer. EDGE-3 reference point support: registering an edge application server with availability information (e.g., time limit, location limit); logging off an edge application server from an edge enabling server; and providing access to network capability information (e.g., location information). The following radix rules apply to EDGE-3 (between EAS and EES): a) An EAS may communicate with only one EES; b) One EES may communicate with one or more EAS simultaneously.

EDGE-4 reference points support EDGE-enabled layer-related interactions between EDGE data network configuration servers and EDGE-enabled clients. EDGE-4 reference point support: edge data network configuration information is provisioned to edge-enabled clients in the UE.

The EDGE-5 reference point supports interactions between application client(s) in the UE and EDGE-enabled clients. EDGE-5 reference point support: obtaining information about an application client for connecting to an edge application server; notification of events related to a connection between an application client and its corresponding edge application server, such as: when an application client needs to be reconnected to a different edge application server; providing application client information (e.g., a profile thereof) for various tasks (e.g., identifying an appropriate edge application server instance to connect to); and providing the identity of the desired edge application server to the edge enabled client to enable it to use the identity as a filter when requesting information about the edge application server.

EDGE-6 reference points support EDGE-enabled layer-related interactions between EDGE data network configuration servers and EDGE-enabled servers. EDGE-6 reference point support: the edge enabled server information is registered with an edge enabled network configuration server.

EDGE-2 (or EDGE-7) reference points support EDGE-enabled layer related interactions between EDGE-enabled servers and 3GPP networks. EDGE-7 reference point support: the 3GPP network functions and APIs are accessed to retrieve network capability information, e.g., via SCEF and NEF APIs, and wherein EAS acts as a trusted AF in 5 GC. EDGE-7 reference point reuse SA2 defined 3GPP reference point, N6 or EPS or 5GS interfaces considering different deployment models.

The EDGE-8 reference point supports interactions between EDGE data network configuration servers and 3GPP networks. EDGE-8 reference point support: and carrying out edge data network configuration on the 3GPP network by utilizing the network public service.

EDGE-9 reference point enables interaction between two EDGE-enabled servers. EDGE-9 reference points may be provided between EES within different EDNs and within the same EDN.

An Edge Enabled Server (EES) provides support functions for edge application servers and edge enabled clients. The edge-enabled server functions are: a) Configuration information is configured to the edge enabling client so that application data traffic can be exchanged with the edge application server; b) Supporting functions of an API caller and an API disclosure function; c) 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); and d) a function of supporting application context transfer.

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

EAS is an application server residing in an edge data network that performs server functions. The application client connects to an edge application server to take advantage of the services of the application and edge computing. The server functionality of the application may be available only as an edge application server. However, if the server functions of the application 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 not be the same. In addition, if the functions of the edge application server and the application server are different, the application data traffic may also be different.

The edge application server may consume the 3GPP core network capabilities in different ways, for example: a) If it is an entity trusted by the 3GPP core network, it can directly invoke the 3GPP core network function API; b) It may invoke 3GPP core network capabilities through an edge-enabled server; and C) it can invoke 3GPP core network capabilities through capability disclosure functions (e.g., SCEF or NEF).

The following cardinality rules apply to the edge application server: a) One or more EAS may be located in the EDN. EAS(s) belonging to the same EAS ID may be provided by multiple ECSPs in the EDN.

The Edge Enabled Server IDs (EESIDs) are Fully Qualified Domain Names (FQDNs) of the edge enabled servers, and each edge enabled server ID is unique within the PLMN domain.

The Edge Application Server ID (EASID) identifies a particular application, e.g., 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 IE.

Table E28.2.4-1: edge application server profile

The edge application server service Key Performance Indicator (KPI) provides information about the characteristics of the service provided by the edge application server (see, e.g., table E28.2.5-1).

Table E28.2.5-1: edge application server service KPI

The edge enabled server profile includes information about EES and the services it provides (see, e.g., table E28.2.6-1).

Table E28.2.6-1: edge enabled server profile

The disclosure of network capabilities to the edge application server(s) depends on the deployment scenario and the business relationship of the ASP/ECSP with the PLMN operator. The following mechanisms are supported: direct network capability disclosure and/or network capability disclosure via an edge-enabled server.

In some implementations, the disclosure of network capability to EAS(s) depends on deployment scenario and the business relationship of ASP/ECSP to PLMN operators. The following mechanisms are supported: direct network capability disclosure and/or network capability disclosure via an edge-enabled server. In some implementations, charging functions with different deployment options are beyond the scope of the present disclosure (SA 5 study) depending on the business relationships between the edge application service provider, the edge computing service provider, and the SFC service provider.

FIG. 6 illustrates an inter-EDN according to some embodiments. FIG. 7 illustrates an intra-EDN according to some embodiments. EDGE-9 reference point enables interaction between two EDGE-enabled servers. EDGE-9 reference points may be provided between EES within different EDNs (as shown in fig. 6) and between EES within the same EDN (as shown in fig. 7).

FIG. 8 illustrates service provider relationships in an edge computing network deployment according to some embodiments. FIG. 8 illustrates roles and relationships of service providers involved in the deployment of edge computing services. An Application Service Provider (ASP) is responsible for creating EAS and Application Clients (AC). The ECSP is responsible for deploying an EDN containing EAS and EES that provide configuration information to the EEC to enable the AC to exchange application data traffic with the EAS. PLMN operators are responsible for deploying 5G network functions, such as 5GC and 5G NR.

The end user is a consumer of the applications/services provided by the ASP and may sign up for an ASP service agreement with a single application service provider or multiple application service providers. The end user enters into a PLMN subscription agreement with the PLMN operator. The UE used by the end user is allowed to register with the PLMN operator network. The ASP consumes edge services (e.g., infrastructure, platform, etc.) provided by the ECSPs and may sign up for ECSP service agreement(s) with a single ECSP or multiple ECSPs. The ECSP may be a mobile network operator or a 3 rd party service provider that provides edge computing services. A single PLMN operator may sign up for a PLMN operator service agreement with a single computing service provider or multiple edge computing service providers. A single ECSP may sign up for a PLMN operator service agreement with a single PLMN operator or multiple PLMN operators providing edge computing support. The ECSP and PLMN operators may be part of the same organization or different organizations.

As described above, the 3GPP management system manages 3GPP defined network functions (e.g., UPF, PCF, EES, ECS, EAS … …) and services. To support edge computation management, the 3GPP management system includes both PLMN management systems responsible for orchestration and management of mobile networks and ECSP management systems responsible for orchestration and management of EDNs. The ECSP and PLMN operators may be part of the same organization.

Mechanisms for deploying edge application servers, edge enablement servers, edge configuration servers, and 5G mobile networks to support edge computation for 3gpp TR 28.814 are disclosed herein. Embodiments herein also include business level and specification level use cases and requirements, including various deployments. The deployment comprises the following steps: the PLMN/EC service provider deploys the EAS on the EDN; ECSP deploys EAS on EDN; the PLMN/EC service provider deploys the EES on the EDN; ECSP deploys EES on EDN; an ECS deployed by PLMN/EC service provider; and ECSP deployed ECS, wherein the PLMN/EC service provider instructs the operator to own both the PLMN and EDN.

Fig. 9 illustrates an edge computing network in accordance with some embodiments. Fig. 9 shows a deeper view of the 5GC in terms of interaction with the EDN. As shown in fig. 9, the mobile network is connected to two EDNs, each containing EAS. In EDN #1, EAS and EES are trusted by the mobile operator, and therefore the EAS and EES are connected to the PCF in the mobile network via Edge-7 and Edge-2 interfaces, respectively. In EDN #2, EAS and EES are trusted by the mobile operator, so EAS and EES are connected to the NEF via Edge-7 and Edge-2 interfaces, respectively. The ECS connects to the NEF via the Edge-8 interface.

3GPP TS 23.558 states that EAS, EES, ECS interacts with 5GC functions such as PCF, NEF, SCEF to provide edge computing services. For example, EES interacts with the 3GPP core network to access the capabilities of network functions directly (e.g., via PCF) or indirectly (e.g., via SCEF/NEF/scef+nef), see sub-clause 6.3.2 in TS 23.558. The ECS interacts with the 3GPP core network to access the capabilities of the network functions either directly (e.g., via PCF) or indirectly (e.g., via SCEF/NEF/scef+nef), see sub-clause 6.3.4 in TS 23.558. EAS can invoke 3GPP core network capabilities through a capability disclosure function (i.e., SCEF or NEF), see sub-clause 6.3.6 in TS 23.558. Thus, the ECSP management system collects connection information of 5GC functions such as PCF, NEF, SCEF, and thus the ECSP management system can connect EAS, EES, ECS. Accordingly, the ECSP management system gathers connection information for 5GC functions such as PCF, NEF, SCEF, and thus, the ECSP management system can connect EAS, EES, ECS to PCF, NEF, SCEF.

UPF selection for supporting EAS deployment

Target of 2.x.1

The goal is to enable the ECSP management system to query the 3GPP management system to select a UPF from the UPF(s) being deployed based on service area and QoS requirements, or to instantiate a new UPF if there are no available UPFs. The selected UPF connects to the EAS via an N6 interface to support edge computing applications.

Description of the preferred embodiments

The ecsp management system queries the 3GPP management system for information about the UPF to be connected to the EAS by providing a UPF selection requirement comprising a list of service area requirements (e.g., topology service area, geographical service area, (see sub-clause 7.3.3 in TS 28.558)) and N6 traffic routing requirements (see table 8.2.4.1 in TS 23.558).

The 3GPP management system finds UPF(s) that meet the EAS service area and QoS requirements among the UPF(s) being deployed.

3. If the UPF is not found, the 3GPP management system deploys a new UPF.

The 3GPP management system provides UPF information to the ECSP management system.

Requirements of 2.x.3

REQ-UPF-FUN-1 3gpp management service producers should have the ability to allow authorized consumers to query the information of the UPF to be connected to the EAS based on UPF selection requirements (e.g., service area and QoS requirements).

REQ-UPF-FUN-2 3gpp management service producers should have the ability to provide UPF information to consumers.

UPF selection for assisting EAS deployment

Summary of x.1

This sub-clause provides a potential solution for use cases for UPF selection to support EAS deployments (see sub-clause 6.2. X). Assume that EAS has been deployed based on the solution described in sub-clause 7.1.

The solution is applicable to scenarios where PLMN operators deploy UPF(s) in 5GC, and ECSP management system is used to query 3GPP management system to select UPF in 5GC, which will connect to EAS via N6 interface to support edge computing applications.

Solution # 1-UPF selection Using LCM MnS

FIG. 10 illustrates UPF selection via LCM MnS according to some embodiments. Specifically, fig. 10 shows that the ECSP management system requests the 3GPP management system to identify the UPF via the provisioning MnS.

The ECSP management system consumes LCM MnS by the queryupfifnforeq operation to request the 3GPP management system to identify a UPF that can connect to EAS via the N6 interface, the UPF having the following attributes:

EAS topology service area: the topology service area is defined according to the relationship with the UE's connection point to the network, for example: a set of cell IDs, tracking area identities, or PLMN IDs (see sub-clause 7.3.3.2 in TS 23.558).

EAS geographic service area: the geographic service area is an area specified by a geographic unit such as a geographic coordinate ID (see sub-clause 7.3.3.3 in TS 23.558).

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

EAS connectivity information: the attribute contains an EAS connection including an EAS identifier and EAS endpoint information.

The 3GPP management system sends the queryUpfInfoResp to inform the consumer that the request is in progress.

The 3GPP management system finds a UPF among the UPF(s) being deployed based on the EAS topology service area, the EAS geographical service area (see sub-clause 7.3.3 in TS 28.558) and QoS requirements, and if no UPF is found, can deploy a new UPF.

The 3GPP management system sends the queryUpfInfoResp to inform the ECSP management system of the UPF identifier and the UPF endpoint attributes containing endpoint information for the selected UPF.

Solution # 2-UPF selection Using Equipped MnS

Fig. 11 illustrates UPF selection via provisioning MnS, according to some aspects. Specifically, fig. 11 shows that the ECSP management system requests the 3GPP management system to identify the UPF via the provisioning MnS.

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

List of N6 traffic routing requirements: n6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI (see table 8.2.4.1 in TS 23.558).

UPF connection information: the attribute contains a UPF connection, including a UPF identifier, a Domain Name (DN) of the upfEndpoint IOC containing UPF endpoint information.

EAS connectivity information: the attribute contains an EAS connection including an EAS identifier, DN of an easEndpoint IOC containing EAS endpoint information.

UPF selection: the attribute contains a value select (select). If select = TRUE, it is a request to select UPF.

The ECSP management system obtains UPF information in the IOC. Thus, an upfEndpoint IOC should be defined to contain the endpoint information for UPF:

UPF endpoint: the attribute contains the DN of the upfEndpoint IOC that contains endpoint information for the selected UPF.

If the upfSelect MOI does not exist:

the ECSP management system consumes provisioning MnS by operating createMOI for the upfselect IOC with EAS topology service area, EAS geographical service area, list of N6 traffic routing requirements, EAS connection information, UPF select = TRUE (TRUE) to query the 3GPP management system for UPF information.

The 3GPP management system finds a UPF among the deployed UPF(s) based on the service area requirements (e.g., topology service area, geographical service area (see sub-clause 7.3.3 in TS 28.558)) and QoS requirements contained in the upfselect IOC, and if no UPF is found, a new UPF may be deployed.

The 3GPP management system creates an upfSelect MOI and sends a notify MOICation with an attribute list (attributeList) that includes the DN of the upfEndpoint IOC containing UPF connection information (see sub-clause 11.1.1.7 in TS 28.532).

The ECSP management system consumes provisioning MnS by operating getMOIAttributes to get UPF endpoint information properties in the upfEndpoint IOC.

The 3GPP management system returns output parameters with UPF endpoint information attributes in the upfEndpoint IOC.

If the upfSelect MOI already exists:

the ECSP management system consumes the provisioning MnS by operating the modifymoittributes to modify the upfselect MOI with EAS topology service area, EAS geographic service area, list of N6 traffic routing requirements, EAS connectivity information, UPF selection = TRUE to query the 3GPP management system for information about the UPF.

The 3GPP management system sends the notfyMOIAttributeValueChanges with an attributeList that includes the DN of the upfEndpoint IOC containing UPF connection information (see sub-clause 11.1.1.7 in TS 28.532).

X access 5GC functionality

Target of 2.x.1

The goal is to enable the ECSP management system to request the 3GPP management system to provide PCF, NEF, SCEF connection information to allow EAS, EES and ECS access to the capability of 5GC functions, e.g. PCF, NEF, SCEF (see sub-clauses 6.3.2, 6.3.4, 6.4.6 in TS 23.558).

Description of the preferred embodiments

The ecsp management system requests the 3GPP management system to provide connection information of 5GC functions, such as an IP address of PCF, NEF, SCEF.

The 3GPP management system returns PCF, NEF, SCEF connection information to the ECSP management system.

Requirements of 2.x.3

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

REQ-ACC-5GC-FUN-2 3gpp management service producers should have the ability to return 5 GC-functional connectivity information to consumers.

Information x for enabling access to 5GC functions

Summary of x.1

The sub-clause provides a potential solution for accessing use cases of 5GC functionality (see sub-clause 6.2. X).

X.2 solution

Fig. 12 illustrates querying a 5GC IP address via provisioning MnS, according to some aspects. Specifically, fig. 12 shows that the ECSP management system requests the 3GPP management system to provide the connection information of PCF, NEF, SCEF via the provisioning MnS.

A 5GCAccessInfo IOC should be defined to enable access to the 5GC functions. The 5GCAccessInfo IOC should contain the following attributes:

list of PCF connection information: the attribute contains the connection information of the PCF, including the PCF identifier, and PCF endpoint (e.g., IP address, DN).

List of NEF connection information: the attribute contains connection information for the NEF, including a NEF identifier, and a NEF endpoint (e.g., IP address, DN).

List of SCEF connection information: the attribute contains connection information for the SCEF, including a SCEF identifier, and a SCEF endpoint (e.g., IP address, DN).

If 5 GCAcess info MOI does not exist:

the ECSP management system consumes the provisioning MnS through an operation createMOI for the 5GCAccessInfo IOC to request the 3GPP management system to create a 5GCAccessInfo Management Object Instance (MOI).

The 3GPP management system creates a 5GCAccess info MOI and sends a notfyMOICation with an attributeList that includes all available connection information for PCF, NEF, SCEF (see sub-clause 11.1.1.7 in TS 28.532).

If a 5GCAccessInfo MOI already exists:

the ECSP management system consumes provisioning MnS by operating getMOIAttributes to get connection information for the 5GC function(s) (e.g., PCF, NEF, SCEF) in the 5GCAccessInfo IOC.

The 3GPP management system returns the output parameters of the connection information with the 5GC function(s).

MnS consumers thus consume or use the management services produced by MnS manufacturers. Each management service consists of various operations. For example, the management service for MnS arrangement is as follows:

accordingly, the consumer consumes the management service (e.g., provisioning MnS) by invoking an operation (e.g., createMOI operation).

TS 23.558 sub-clause 6.3.2 (EES): EES provides support functions for EAS and EECs. The EES functions are: a) Configuration information is configured to the EEC to realize the exchange of application data traffic with the EAS; b) Providing an API caller and API disclosure functions 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) Disclosing events related to the ACT; e) EEC context transfer between EES; f) External disclosure of 3GPP network and service capabilities supporting through EDGE-3 to EAS(s); g) The registration function (i.e., register, update, and de-register) of EEC(s) and EAS(s); and h) triggering EAS instantiation on demand.

TS 23.558 sub-clause 6.3.4 (ECS): the ECS provides support functions for EEC to EES connections. The functions of the ECS are: a) Edge configuration information is provided to the EECs. The edge configuration information includes the following: 1) Information for the EECs to distinguish EES (e.g., EDN service areas); and 2) information (e.g., URI) for establishing a connection with the EES; the ECS may be deployed in an MNO domain or may be deployed by a service provider in a 3 rd party domain; b) Support functions for registration (i.e., registration, update, and deregistration) of EES(s); c) Functions supporting the API invoker and API disclosure functions specified in 3gpp TS 23.222; and d) the ability to interact with the 3GPP core network to access network functions directly (e.g., via PCF) or indirectly (i.e., SCEF/NEF/SCEF+NEF).

TS 23.558 sub-clause 6.3.6 (EAS): EAS is an application server residing in the EDN that performs server functions. AC connects to EAS to take advantage of the service and edge computation of the application. The server function of the application may be available only as EAS. However, some server functionality may also be available both at the edge and in the cloud, as EAS and application servers residing in the cloud, respectively. The server functions provided by the EAS and its cloud application server counterparts may be the same or may be different; if they are different, the application data traffic exchanged with the AC may also be different. EAS may consume 3GPP core network capabilities by: a) Invoking 3GPP core network capabilities via an edge enablement layer by the EES; b) If it is an entity trusted by the 3GPP core network, directly invoking a 3GPP core network function (e.g., PCF) API; and c) invoking the 3GPP core network capabilities by a capability disclosure function (i.e., SCEF/NEF/SCEF+NEF).

In some examples, the means of managing the system comprises processing circuitry configured to operate as a 3GPP management system to: consuming LCM MnS by a queryupfifnforeq operation, receiving a request from an ECSP management system to identify a UPF that can connect to EAS via an N6 interface; and sending the queryUpfInfoResp to inform the ECSP management system and the consumer that the request is in progress; and finding a UPF among the UPF(s) being deployed based on the UPF selection requirement, or instantiating a new UPF if a UPF meeting the UPF selection requirement is not found; and sending a notification queryupinfofresp to notify the ECSP management system of the UPF identifier and UPF endpoint attributes containing endpoint information for the selected UPF.

The UPF selection requirements include: EAS topology service area: the topology service area is defined according to the relationship with the UE's connection point to the network, for example: a set of cell IDs, tracking area identities, or PLMN IDs; EAS geographic service area: a geographic service area is an area specified by a geographic unit such as a geographic coordinate ID; and a list of N6 traffic routing requirements: n6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI; EAS connectivity information: the attribute contains an EAS connection including an EAS identifier and EAS endpoint information.

In some examples, the means of managing the system comprises processing circuitry configured to operate as a 3GPP management system to: consuming provisioning MnS by an operational createMOI for the upfselect IOC, receiving a request from the ECSP management system to identify a UPF that can be connected to EAS via an N6 interface; and the upfSelection IOC contains a UPF selection requirement based on which UPF is found in the UPF(s) being deployed; or instantiating a new UPF if a UPF that meets the UPF selection requirement is not found; creating an upfselect MOI; and sends a notification notify moicontrol to notify the ECSP management system that the upfSelection MOI has been created.

The upfSelect IOC contains: EAS topology service area: the topology service area is defined according to the relationship with the UE's connection point to the network, for example: a set of cell IDs, tracking area identities, or PLMN IDs; EAS geographic service area: a geographic service area is an area specified by a geographic unit such as a geographic coordinate ID; and a list of N6 traffic routing requirements: n6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI; UPF connection information: the attribute is a placeholder for the 3GPP management system to provide UPF connection information; EAS connectivity information: the attribute contains an EAS connection including an EAS identifier, DN of an easEndpoint IOC containing EAS endpoint information; and (3) UPF selection: this attribute pertains to the UPF selection.

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

The UPF connection information attribute contains the UPF connection, including the UPF identifier, the DN of the upfEndpoint IOC containing UPF endpoint information.

Upon receiving notification notify moicontrol, the ECSP management system is configured to: consuming provisioning MnS by manipulating getMOIAttributes to obtain UPF endpoint information attributes in an UPF endpoint IOC; and receives output parameters with UPF endpoint information attributes in the upfEndpoint IOC.

In some examples, the means of managing the system comprises processing circuitry configured to operate as a 3GPP management system to: receiving a request from the ECSP management system via the provisioning MnS by modifying the operation modification moiattributes of the upfselect MOI; and the upfSelection IOC contains a UPF selection requirement based on which UPF is found in the UPF(s) being deployed; or instantiating a new UPF if a UPF that meets the UPF selection requirement is not found; and sending a notification notify MOIAttributeValueChanges with an attributeList to the ECSP management system, the attributeList including the DN of the upfEndpoint IOC containing UPF connection information.

Upon receiving notification of notify moiattributevaluechanges, the ECSP management system is configured to: consuming provisioning MnS by manipulating getMOIAttributes to obtain UPF endpoint information attributes in an UPF endpoint IOC; and receives output parameters with UPF endpoint information attributes in the upfEndpoint IOC.

In some examples, the means of managing the system comprises processing circuitry configured to operate as a 3GPP management system to: consuming provisioning MnS by an operation createMOI for a 5GCAccessInfo IOC, receiving a request from an ECSP management system to create the 5GCAccessInfo IOC; and creating a 5 GCAcess info MOI; and sending a notification notify mol registration with an attributeList to the ECSP management system, the attributeList including all available connection information for PCF, NEF, SCEF.

The 5 GCAcess info IOC includes: list of PCF connection information: the attribute contains connection information for the PCF, including the PCF identifier, and PCF endpoints (e.g., IP address, DN); list of NEF connection information: the attribute contains connection information for the NEF, including a NEF identifier, and a NEF endpoint (e.g., IP address, DN); list of SCEF connection information: the attribute contains connection information for the SCEF, including a SCEF identifier, and a SCEF endpoint (e.g., IP address, DN).

In some examples, the means of managing the system comprises processing circuitry configured to operate as a 3GPP management system to: consuming provisioning MnS by operating getMOIAttributes, receiving a request from an ECSP management system to obtain connection information of a 5GC function; and returns the output parameters of the connection information with 5GC function.

Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the disclosure. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This detailed description is, therefore, not to be taken in a limiting sense, and the scope of the various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

The subject matter may be referred to herein, individually and/or collectively, by the term "embodiment" merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, 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 no B", "B, but no a" and "a and B", unless otherwise indicated. In this document, the terms "comprise" and "wherein" are used as plain english equivalents of the respective terms "comprising" and "wherein. In addition, in the appended claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes other elements in addition to those listed after such term in a claim is still considered to fall within the scope of that claim. In addition, 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.

The abstract of the disclosure is provided to conform to 37c.f.r.1.72 (b), which requires an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. The abstract was submitted under the following cleavage: it is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing detailed description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

1. An apparatus for managing a system, the apparatus comprising:

processing circuitry configured to:

decoding a request from an Edge Computing Service Provider (ECSP) management system to identify a User Plane Function (UPF) to connect to an Edge Application Server (EAS) via an N6 interface;

determining whether a UPF of the deployed UPFs meets the request based on a UPF selection attribute and a quality of service (QoS) attribute in the request;

Instantiating a UPF that satisfies the request in response to determining that none of the deployed UPFs satisfies the request, otherwise selecting a UPF that satisfies the request among the deployed UPFs; and

encoding a notification containing UPF information for the UPF that satisfies the request for transmission to the ECSP management system; and

and a memory configured to store the UPF information.

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

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

4. The apparatus of claim 1, wherein:

the request is based on operating a Consumer lifecycle management (LCM) management service (MnS) through the queryUpfInfoReq, and

the notification includes a queryupinfofresp operation.

5. The apparatus of claim 4, wherein the processing circuit is further configured to: in response to receipt of the request, an additional notification is encoded for transmission to the ECSP management system, the additional notification being used to notify that the request is in progress, the notification including a queryUpfInfoResp operation.

6. The apparatus of claim 1, wherein the UPF information comprises a UPF identifier and a UPF endpoint attribute comprising endpoint information for the UPF.

7. The apparatus of claim 1, wherein:

the request is based on consuming a provisioning management service (MnS) by the ECSP management system through a createMOI operation for an upfselect Information Object Class (IOC).

8. The apparatus of claim 7, wherein:

the upfSelection IOC includes: topology service area, geographical service area, list of N6 traffic routing attributes, UPF connection information, EAS connection information, and UPF select value, which is set to true to indicate that the request will select the UPF,

the N6 traffic routing attribute includes at least one of a routing profile Identifier (ID) or N6 traffic routing information corresponding to a Data Network Access Identifier (DNAI) of the EAS,

the UPF connection information includes a UPF identifier and a Domain Name (DN) of an upEndpoint IOC that includes UPF endpoint information, and

the EAS connectivity information includes an EAS identifier and a DN of an easEndpoint IOC including EAS endpoint information.

9. The apparatus of claim 7, wherein the processing circuitry is configured to create an upfselect Management Object Instance (MOI) and encode notifyMOICreation MOI with an attributeList for transmission to the ECSP management system, the attributeList comprising a Domain Name (DN) of an UPF endpoint IOC containing the UPF connection information.

10. The apparatus of claim 1, wherein:

the request is based on an upfSelect Management Object Instance (MOI) operated by the ECSP management system through a modified MOIAttributes operation Consumer configuration management service (MnS) to modify an upfSelect Information Object Class (IOC), and

the upfSelection IOC includes: topology service area, geographic service area, and the QoS attributes.

11. The apparatus of claim 10, wherein the processing circuit is configured to: notifyMOImodifyMOIAttributes MOI having an attributeList including a Domain Name (DN) of an UPF endpoint IOC containing the UPF connection information is encoded for transmission to the ECSP management system.

12. The apparatus of claim 10, wherein the processing circuit is configured to:

decoding a request from the ECSP management system for a connection of the EAS to a mobile network function including mobile network connection information for the EAS for a Policy Control Function (PCF), a service capability disclosure function (SCEF), and a network disclosure function (NEF), and

in response to a request for the mobile network function, the mobile network connection information is encoded for transmission to the ECSP management system.

13. The apparatus of claim 1, wherein:

decoding provisioning management service (MnS) for 5GCAccessInfo Information Object Class (IOC) from the ECSP management system to enable access to a 5 th generation core network (5 GC) function, the 5GC function including connection information for the EAS for Policy Control Function (PCF), service capability disclosure function (SCEF), and network disclosure function (NEF), and

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.

14. The apparatus of claim 13, wherein the connection information comprises:

PCF connection information, including PCF identifiers and PCF endpoint information,

NEF connection information including NEF identifier and NEF endpoint, and

SCEF connection information including a SCEF identifier and a SCEF endpoint.

15. The apparatus of claim 1, wherein the processing circuit is configured to:

in response to the ECSP management system consuming provisioning MnS through an operation createMOI for a 5GCAccess info Information Object Class (IOC) to request creation of a 5GCAccess info Management Object Instance (MOI), creation of a 5GCAccess info MOI, and

a notify mobility notification with an attributeList including available connection information for Policy Control Function (PCF), service capability disclosure function (SCEF), and network disclosure function (NEF) is encoded for transmission to the ECSP management system.

16. The apparatus of claim 1, wherein the processing circuit is configured to: in response to consuming provisioning MnS by the ECSP management system to request connection information for a 5 th generation core network (5 GC) function through operation getmoiatittributes for a 5GCAccessInfo Information Object Class (IOC), connection information for a Policy Control Function (PCF), a service capability disclosure function (SCEF), and a network disclosure function (NEF) is provided to the ECSP management system.

17. An apparatus of an Edge Computing Service Provider (ECSP), the apparatus comprising:

processing circuitry configured to:

encoding a request for User Plane Function (UPF) information for a UPF to be connected to an Edge Application Server (EAS) via an N6 interface for transmission to a 3GPP management system, the encoding being independent of whether the UPF is present in a plurality of existing UPFs or whether a new UPF is to be deployed based on the request, the request including a service area attribute, an N6 traffic routing attribute, and a quality of service (QoS) attribute; and

decoding a notification from the 3GPP management system containing the UPF information; and a memory configured to store the UPF information.

18. The apparatus of claim 17, wherein the processing circuit is configured to generate the request by one of: lifecycle management (LCM) management service (MnS) is consumed by the queryupfifnforeq operation, or provisioning MnS is consumed by the upfSelection Information Object Class (IOC).

19. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a 3GPP management system, the one or more processors configured to, when executed, configure the 3GPP management system to:

a notification including UPF information for the UPF that satisfies the request is encoded for transmission to the ECSP management system.

20. The non-transitory computer readable storage medium of claim 19, wherein the request is based on consumption by an ECSP management system of one of: lifecycle management (LCM) management service (MnS) is consumed by the queryupfifnforeq operation, or provisioning MnS is consumed by the upfSelection Information Object Class (IOC).