DE112021003901T5 - EDGE COMPUTING APPLICATIONS FOR 5G SYSTEMS - Google Patents

Abstract

A setup and system for an edge server deployment is described. The service provider and management system can deploy Edge Application Server, Edge Activation Server, Edge Configuration Server and the 5G cellular networks to support edge computing for 3GPP. In response to a request to install an Edge Computing (EC) Network Function (NF), a VNF is instantiated and connected to 5th Generation Core (5GC) NFs to send information across edge interfaces. In response to a request to terminate the EC-NF, the EC-NF associated with the EC-NF identifier in the request is terminated and the EC-NF is separated from the 5GC-NFs. An appropriate notification is sent to indicate successful installation or termination of the EC-NF.

Description

PRIORITY CLAIM

This application claims priority from US provisional patent application serial number 63/055,057 , filed July 22, 2020, which is hereby incorporated by reference in its entirety.

TECHNICAL AREA

Embodiments relate to wireless connections in 5G or New Radio (NR) systems. Some embodiments relate to edge computing in 5G systems.

BACKGROUND

The usage and complexity of 3GPP LTE systems (including LTE and LTE-Advanced systems) has increased due to both an increase in the types of user equipment (UE) using network resources and the amount of data and bandwidth used by various applications running on these UEs, such as video streaming. With the tremendous increase in the number and diversity of communication devices, the associated network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated, particularly with the advent of Next Generation (NG) (or New Radio(NR )-/5 ^th Generation(5G) systems). As expected, a number of problems are associated with the advent of any new technology.

character list

• 1A veranschaulicht eine Architektur eines Netzwerks gemäß einigen Aspekten.
• 1B veranschaulicht eine Nicht-Roaming-5G-Systemarchitektur gemäß einigen Aspekten.
• 1C veranschaulicht eine Nicht-Roaming-5G-Systemarchitektur gemäß einigen Aspekten.
• 2 veranschaulicht ein Blockdiagramm einer Kommunikationsvorrichtung gemäß einigen Ausführungsformen.
• 3 veranschaulicht ein 5G-Edge-Computing-Netzwerk gemäß einigen Ausführungsformen.
• 4 veranschaulicht einen Peer-to-Peer(P2P)-Edge-Computing-Verwaltungseinsatz gemäß einigen Ausführungsformen.
• 5 veranschaulicht eine Architektur zum Ermöglichen von Edge-Anwendungen gemäß einigen Ausführungsformen.
• 6 veranschaulicht ein Inter-Edge-Detektionsnetzwerk (EDN) gemäß einigen Ausführungsformen.
• 7 veranschaulicht ein Intra-EDN gemäß einigen Ausführungsformen.
• 8 veranschaulicht eine Dienstanbieterbeziehung in einem Edge-Computing-Netzwerkeinsatz gemäß einigen Ausführungsformen.

In the figures, which are not necessarily drawn to scale, like numerals may describe like components from different views. The same reference numbers with different letter suffixes may represent different instances of similar components. The figures illustrate various embodiments discussed herein, generally by way of example but not limitation.

• 1A Figure 12 illustrates an architecture of a network according to some aspects.
• 1B Figure 12 illustrates a non-roaming 5G system architecture according to some aspects.
• 1C Figure 12 illustrates a non-roaming 5G system architecture according to some aspects.
• 2 12 illustrates a block diagram of a communication device, according to some embodiments.
• 3 12 illustrates a 5G edge computing network, according to some embodiments.
• 4 FIG. 11 illustrates a peer-to-peer (P2P) edge computing management deployment, in accordance with some embodiments.
• 5 1 illustrates an architecture for enabling edge applications, according to some embodiments.
• 6 12 illustrates an inter-edge detection network (EDN) according to some embodiments.
• 7 12 illustrates an intra EDN, according to some embodiments.
• 8th 12 illustrates a service provider relationship in an edge computing network deployment, according to some embodiments.

DETAILED DESCRIPTION

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

1A Figure 12 illustrates an architecture of a network according to some aspects. The network 140A includes 3GPP-LTE/4G and NG network functions. A network function can be implemented as a discrete network element on dedicated hardware, as a software instance running on dedicated hardware and/or as a virtualized function instantiated on a suitable platform, e.g. B. dedicated hardware or a cloud infrastructure.

Network 140A is shown to include user equipment (UE) 101 and UE 102 . UEs 101 and 102 are illustrated as smartphones (e.g., handheld, touchscreen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as wearable ( Laptop) or desktop computer, wireless handset, drone, or any other computing device that incorporates a wired and/or wireless communication interface. UEs 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.

Any of the radio links described herein (e.g., as used in network 140A or any other illustrated network) may operate according to any example radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as LSA (Licensed Shared Access) at 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and other frequencies and SAS (Spectrum Access System) at 3.55-3.7 GHz and other frequencies). Different single carrier or orthogonal frequency domain multiplexing or OFDM modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multicarrier (FBMC), OFDMA etc.), and in particular 3GPP NR, can be used by mapping the OFDM Bearer data bit vectors are used to the corresponding symbol resources.

In some aspects, any one of UEs 101 and 102 may include an Internet of Things (IoT) UE or a mobile IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications is using ephemeral UE connections. In some aspects, any one of UEs 101 and 102 may be a narrowband or NB-IoT UE (e.g., such as an enhanced NB-IoT or eNB-IoT UE and a further enhanced or FeNB-IoT -UE An IoT UE may include technologies such as machine-to-machine (M2M) or other machine-type communications (MTC) for exchanging data with an MTC server or device over a Public Land Mobile Network (PLMN). terrestrial mobile network), proximity-based service (ProSe - environment-based service) or device-to-device (D2D - Device to Device) communication, sensor networks or IoT networks. The M2M or MTC data exchange can be a machine-initiated data exchange An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with ephemeral connections. (e.g. keep-alive messages, status updates, etc.) to facilitate connections to the IoT network. In some aspects, any of the UEs 101 and 102 may include enhanced MTC or EMTC UEs, respectively, or further enhanced MTC or FeMTC UEs, respectively.

The UEs 101 and 102 may be configured to connect to a radio access network (RAN) 110, e.g. B. to couple communicatively. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or another type of RAN.

UEs 101 and 102 utilize links 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in more detail below); In this example, links 103 and 104 are illustrated as an air interface to enable communicative coupling and may be used with cellular communication protocols such as a GSM protocol (GSM - Global System for Mobile Communications), a CDMA network protocol (CDMA - Code-Division Multiple Access), a PTT protocol (PTT - Push-to-Talk), a POC protocol (POC - Universal Mobile Telecommunications System), a UMTS protocol (UMTS - Universal Mobile Telecommunications System), an LTE protocol (LTE - 3GPP Long Term Evolution), a 5G protocol (5G - fifth generation), a NR protocol (NR - New Radio) and the like.

In one aspect, the UEs 101 and 102 can also directly exchange communication data via a ProSe interface 105 . The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a shared physical sidelink channel (PSSCH). sidelink shared channel), a physical sidelink discovery channel (PSDCH), a physical sidelink broadcast channel (PSBCH), and a physical sidelink feedback channel (PSFCH).

UE 102 is shown configured to access an access point (AP) 106 via link 107 . Connection 107 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, for example, according to which AP 106 may include a wireless fidelity or WiFi® router. In this example, the AP 106 is shown as being connected to the Internet without being connected to the core network of the wireless system (described in more 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 (BSs), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, and the like, and may be ground stations (e.g. terrestrial 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). In cases where the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may operate within the NodeBs' communication cell. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g. the macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g. cells with smaller coverage areas, smaller user capacity or higher bandwidth compared to macrocells), e.g. a low-power or LP-RAN node 112.

Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102 . In some aspects, each of RAN nodes 111 and 112 may perform various logical functions for RAN 110, including but not limited to radio network control (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, an eNB, or another type of RAN node.

The RAN 110 is shown communicatively coupled to a core network (CN) 120 via an SI interface 113 . In aspects, the CN 120 may be an Evolved Packet Core (EPC) network, a NextGen Packet Core (NPC) network, or any other type of CN (such as, for example, referring to FIG 1B-1C ) is described. In this aspect, the S1 interface 113 is divided into two parts: the S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the service gateway (S-GW) 122, and the S1 mobility management entity interface or MME interface 115, which is a signaling interface between RAN nodes 111 and 112 and MMEs 121.

In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the packet data network or PDN gateway (P-GW) 123 and a home subscriber server or HSS (Home Subscriber Server) 124. The MMEs 121 can in their Function similar to the control plane of older serving General Packet Radio Service (GPRS) support nodes (SGSN). The MMEs 121 can manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS 124 may include a database of network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may include one or more HSS 124 depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, the HSS 124 may support routing/roaming, authentication, authorization, name/address resolution , location dependencies, etc.

The S-GW 122 may terminate the S1 interface 113 to the RAN 110 and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may and may be a local mobility anchor point for inter-RAN node handovers also provide an anchor for inter-3GPP mobility len. Other duties of the S-GW 122 may include law enforcement, billing, and enforcement of some policies.

The P-GW 123 can terminate an SGi interface to a PDN. The P-GW 123 can route data packets between the EPC network 120 and external networks, such as a network having the application server 184 (alternatively referred to as application function (AF)), via an internet protocol (IP) interface 125 . The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. In general, the application server 184 can be an element offering applications using IP bearer resources with the core network (e.g. UMTS packet service or PS domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown communicatively coupled to an application server 184 via an 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 via the CN 120.

The P-GW 123 may also be a policy enforcement and billing data collection node. A Policy and Charging Rules Function (PCRF) 126 is the policy and charging control of the CN 120. In a non-roaming scenario, there may be a single PCRF in the public land mobile home network ( HPLMN) in connection with a UE's Internet Protocol connectivity access network (IP-CAN) session. In a roaming scenario with a local population of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a home PCRF (H-PCRF) within an HPLMN and a guest PCRF (V-PCRF ) within a public guest land mobile network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123 .

In some aspects, the communication network 140A may be an IoT network or a 5G network, including a 5G New Radio network that uses communications in the licensed (5G-NR) and unlicensed (5G-NR-U) spectrum . One of the current enablers of IoT is Narrowband IoT (NB-IoT). An operation in the unlicensed spectrum may include a dual connectivity or DC operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology only in an unlicensed spectrum without the use of an "anchor" in the licensed spectrum, called MulteFire, works. A further improved operation of LTE systems in the licensed and unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operation may include techniques for sidelink resource allocation and UE processing behavior for NR sidelink V2X communications.

An NG system architecture may include the RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 may include multiple nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core network or 5GC) may include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. In particular, in some aspects, the gNBs and the NG-eNBs may be connected to the AMF through NG-C interfaces and to the UPF through NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

In some aspects, the NG system architecture may use reference points between different nodes as provided by the 3GPP-TS (Technical Specification) 23.501 (e.g. V15.4.0, 2018-12). In some aspects, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so on. In some aspects, a gNB can be a Master Node (MN) and the NG-eNB can be a Secondary Node (SN) in an SG architecture.

1B Figure 12 illustrates a non-roaming 5G system architecture according to some aspects. Specifically illustrated 1B a SG system architecture 140B in a reference point representation. In particular, the UE 102 may be in communication with the RAN 110 as well as one or more other SGC network entities. The SG system architecture 140B includes several network functions (NFs) such as an AMF 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a UPF 134, a network slice selection function ( NSSF) 142, an authentication server function (AUSF) 144, and a 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 carrier services, internet access, or third party services, for example. The AMF 132 can be used to manage admission control and mobility, and can also include network slice selection functionality. The AMF 132 can provide UE-based authentication, authorization, mobility management, etc. and can be independent of the access technologies. The SMF 136 can be configured to establish and manage various sessions according to a network policy. The SMF 136 can thus be responsible for session management and assignment of IP addresses to UEs. The SMF 136 can also select and control the UPF 134 for data transmission. The SMF 136 may be associated with a single UE 101 session or multiple UE 101 sessions. This means that the UE 101 can have multiple SG sessions. Each session can have different SMFs associated with it. Using different SMFs can allow each session to be managed individually. Consequently, the functionalities of each session can be independent of each other.

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

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

In some aspects, the SG system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as multiple IP multimedia core network subsystem entities, such as call session control functions (CSCFs). In particular, the IMS 168B includes a CSCF acting as a Proxy CSCF (P-CSCF) 162BE, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (in 1B not shown) or an interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B may be configured as the first point of contact for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B may be configured to handle session states on the network and the E-CSCF may be configured to handle certain aspects of emergency sessions, such as routing an emergency request to the right emergency center or PSAP. The I-CSCF 166B may be configured to serve as the point of contact within an operator's network for all IMS calls destined for a subscriber of that network operator or a roaming subscriber currently in the service area of that network operator. In some aspects, the I-CSCF 166b may be connected to another IP multimedia network 170E, e.g. B. an IMS operated by another network operator.

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

A reference point representation shows that there can be an interaction between corresponding LF services. For example illustrated 1B the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134 ), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in the case of a non-roaming scenario, or between the PCF 148 and a visited network and the AMF 132 in the case of a roaming scenario, not shown), N16 (between two SMFs, not shown) and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations included in 1B are not shown can also be used.

1C illustrates a SG system architecture 140C and a service-based representation. In addition to the in 1B Illustrated network entities, the system architecture 140C can also a network exposure function (NEF) 154 and a network repository function (NRF) 156 . In some aspects, SG system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

In some aspects, as in 1C As illustrated, service-based representations can be used to represent network functions within the control plane that allow other authorized network functions to access their services. In this regard, the SG system architecture 140C may include the following service-based interfaces: Namf 158H (a service-based interface presented by the AMF 132), Nsmf 1581 (a service-based interface presented by the SMF 136), Nnef 158B ( a service-based interface presented by the NEF 154), Npcf 158D (a service-based interface presented by the PCF 148), a Nudm 158E (a service-based interface presented by the UDM 146), Naf 158F (a service-based interface presented by AF 150), Nnrf 158C (a service-based interface presented by NRF 156), Nnssf 158A (a service-based interface presented by NSSF 142), Nausf 158G (a service-based interface shown by the AUSF 144). Other service-based interfaces (such as Nudr, N5g-eir, and Nudsf) built into 1C are not shown can also be used.

NR-V2X architectures can support high-reliability, low-latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR-V2X communication systems.

2 12 illustrates a block diagram of a communication device, according to some embodiments. The communication device 200 may be: a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC or a smartphone, a dedicated network device such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing commands (sequential or otherwise) that specify actions to be performed by that machine. The communication device 200 can, for example, be one or more of the 1A until 1C be implemented shown devices. It is noted that communications described herein may be encoded prior to transmission by the sending entity (e.g. UE, GNB) for receipt by the receiving entity (e.g. gNB, UE) and decoded after receipt by the receiving entity.

Examples, as described herein, may include or operate on logic or any number of components, modules, or mechanisms. Modules and components are physical entities (e.g., hardware) that are capable of performing specified operations and may be configured or arranged in a particular way. In one example, circuits may be moduled in a specified manner (e.g., internally or with respect to external entities such as other circuits). In one example, all or part of one or more computer systems (e.g., a standalone, client, or server computer system) or one or more hardware processors may be powered by firmware or software (e.g., applications, an application portion, or a Application) configured as a module that operates to perform specified operations. In an example, the software may reside on a machine-readable medium. In one example, the software, when executed by the module's underlying hardware, causes the hardware to perform the specified operations.

Accordingly, the term "module" (and "component") is understood to include a tangible entity, whether an entity that is physically constructed, specifically configured (e.g., hardwired), or transient (e.g., transitory) configured (e.g. programmed) to operate in a predetermined manner or to perform part or all of any operations described herein. Considering examples where modules are configured temporarily, each of the modules need not be instantiated at any given time. For example, where the modules include a general purpose hardware processor configured using software, the general purpose hardware processor may be configured as respective different modules at different times. Software can accordingly configure a hardware processor, for example, to form a particular module at one time and form a different module at another time.

Communications device 200 may include a hardware processor (or equivalent processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), main memory 204, and static memory 206, some or all of which may be can communicate with each other via an interconnect (e.g., a bus) 208 . Main memory 204 may include any or all removable data storage and non-removable data storage, volatile storage, or non-volatile storage. The communication device 200 may further 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 one example, display unit 210, input device 212, and UI navigation device 214 may be a touch screen display. The communication device 200 may also include a data storage device (e.g., a disk drive unit) 216, a signal generating device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor system), a compass, accelerometer, or other sensor. The communication device 200 may also include an output controller, such as a serial (e.g., USB (Universal Serial Bus)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to the communicating with or controlling one or more peripheral devices (e.g., a printer, card reader, etc.).

The data storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter referred to simply as machine-readable medium) on which are stored one or more sets of data structures or instructions 224 (e.g., software) that may be generated by one or more of the techniques described herein or Functions are embodied or used. The instructions 224 may also reside entirely or at least partially within the main memory 204, within the static memory 206, and/or within the hardware processor 202 during their execution by the communication device 200. Although the machine-readable medium 222 is illustrated as a single medium, the term "machine-readable medium" can 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" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that causes the communication device 200 to perform any one or more of the techniques of the present disclosure, or that capable of storing, encoding, or maintaining data structures used by or associated with such instructions. Non-limiting examples of machine-readable media can include solid-state memory, and optical and magnetic media. Specific examples of machine-readable media may 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; radio random access memory (RAM); and 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 utilizing 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), cellular networks (e.g., cellular based networks), plain old telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols such as, among others, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, the IEEE 802.16 family of standards known as WiMax , the IEEE 802.15.4 family of standards, an LTE (Long Term Evolution) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a Next-Generation(NG)/5 ^th Generation (SG) standard. In one example, network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas for connection to transmission medium 226 .

It is noted that the term "circuitry" as used herein refers to, is part of, or includes hardware components, such as electronic circuitry, a Logic circuit, a processor (shared, dedicated or bank) and/or a memory (shared, dedicated or bank), an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g. Field Programmable Gate Array (FPGA), Programmable Logic Device (PLD), Complex PLD (CPLD), Structured ASIC or Programmable SoC), Digital Signal Processors (DSPs) etc. configured to provide the functionality described. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the functionality described. The term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuitry used in an electrical or electronic system) with the program code used to perform the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term "processor circuitry" or "processor" as used herein thus refers to circuitry capable of sequentially and automatically performing a sequence of arithmetic or logical operations, or recording, storing, and/or transmitting digital data thereof or includes the same. The term "processor circuitry" 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 computer-executable Execute or otherwise operate instructions, such as program code, software modules, such as program code, software modules, and/or functional processes.

As above, 5G networks extend beyond traditional mobile broadband services to provide various new services such as Internet of Things (IoT), industrial control, autonomous driving, mission-critical communications, etc., which due to safety and performance concerns require ultra-low latency, ultra-high reliability, and high data capacity requirements. Edge computing as a feature has been added in the SG Core (SGC) system architecture to support such services by hosting some applications closer to the local data network to reduce the end-to-end latency and the load on the reduce transport network. 3 12 illustrates a 5G edge computing network, according to some embodiments.

4 FIG. 11 illustrates a P2P edge computing management deployment, in accordance with some embodiments. In the operation that 4 As shown, edge computing in 3GPP networks involves communication between a 3GPP management system, a non-3GPP management system, including an edge computing management system, and ETSI network function virtualization (NFV) management and orchestration (MANO).

The deployment of edge computing in 3GPP networks uses cooperation with other standards development organizations (SDOs) since the application function (AF) and the application server (AS) are not 3GPP-defined nodes. Deploying network functions in 3GPP networks and non-3GPP networks to support edge computing involves communication between 3GPP management systems and non-3GPP management systems.

In the example of 4 the 3GPP management system can initiate the edge computing deployment by requesting that the edge computing management system deploy the local data network and that the network function virtualization orchestrator (NFVO) update the UPF and the local data network with the Quality of Service (QoS)-for- N6 requests for the connection (e.g. a virtual circuit) between the UPF and the local data network connects. The edge computing management system can initiate the edge computing deployment by requesting that the 3GGP management system deploy the UPF and the NFVO to provide the UPF and the local data network with the QoS requirements for the connection between the UPF and to connect to the local data network.

5 shows an architecture to enable deployment of edge applications. In architecture, the application client is an application residing in a UE that performs one or more client functions, and the edge application server (EAS) is an application server residing in the edge data network that runs the local data network, and which performs server functions. The Application client connects to the edge application server to provide (or receive) the application's services with the benefits of edge computing.

5 shows an application architecture for enabling edge applications. The edge data network is a local data network. The one or more Edge Application Servers and the Edge Enabler Server (EES) are included in the EDN. The Edge Configuration Server (ECS) provides configurations related to the EES, including details of the edge data network hosting the EES. The UE includes one or more application clients and the edge activation client. The one or more edge application servers, edge activation server and edge configuration server can interact with the 3GPP core network.

The interactions related to enabling edge computing between the Edge Activation Server and the Edge Activation Client are supported by the EDGE-1 reference point. The EDGE-1 reference point supports the following: Registration and deregistration of the Edge Activation Client with the Edge Activation Server; retrieving and providing configuration information to the UE; and discovering edge application servers available on the edge data network.

The interactions related to the edge activation layer between the edge activation server and the 3GPP network are supported by the EDGE-2 reference point. The EDGE-2 reference point supports the following: Access to 3GPP network functions and application programming interfaces (APIs) to retrieve network capability information, e.g. via SCEF (Service Capability Exposure Function) and NEF (Network Exposure Function) APIs, and where the EES acts as a trusted AF in the SGC. The EDGE-2 reference point reuses SA2 defined 3GPP reference points, N33 or the interfaces of the EPS or SGS considering different deployment models.

The interactions related to the edge activation layer between the edge activation server and the edge application servers are supported by the EDGE 3 reference point. The EDGE 3 reference point supports the following: registration of edge application servers with availability information (e.g. time restrictions, location restrictions); deregistering Edge Application Servers from the Edge Activation Server; and providing access to network capability information (e.g., location information). For EDGE-3 (between EAS and EES) the following cardinality rules apply: A) an EAS can communicate with only one EES; b) an EES can communicate in parallel with one or more EAS.

The edge activation layer interactions between the edge data network configuration server and the edge activation client are supported by the EDGE 4 reference point. The EDGE 4 reference point supports the following: Providing edge data network configuration information to the edge activation client in the UE.

The interactions between the one or more application client(s) and the edge activation client in the UE are supported by the EDGE 5 reference point. The EDGE 5 reference point supports: obtaining information about edge application servers that the application client uses to connect; Notification of events related to the connection between Application Clients and their respective Edge Application Servers, such as: when an Application Client needs to connect to another Edge Application Server; providing application client information (such as its profile) to be used for various tasks, such as identifying the appropriate edge application server instance to connect to; and providing the identity of the desired Edge Application Server to the Edge Activation Client to enable it to use that identity as a filter when requesting information about Edge Application Servers.

The edge activation layer interactions between the edge data network configuration server and the edge activation server are supported by the EDGE 6 reference point. The EDGE 6 reference point supports the following: Registration of Edge Activation Server information with the Edge Activation Network Configuration Server.

The interactions related to the Edge Activation layer between the Edge Activation Server and the 3GPP network are supported by the EDGE 2 (or EDGE 7) reference point. The EDGE-7 reference point supports the following: Access to 3GPP network functions and APIs to retrieve network capability information, e.g. B. via SCEF and NEF APIs, and where the EAS in the SGC as ver trustworthy AF acts. The EDGE-7 reference point reuses SA2 defined 3GPP reference points, N6 or interfaces of the EPS or SGS considering different deployment models.

The interactions between the data network configuration server and the 3GPP network are supported by the EDGE-8 reference point. The EDGE 8 reference point supports the following: Edge data network configurations deployed to the 3GPP network using network vulnerability discovery services.

The EDGE 9 reference point enables interactions between two edge activation servers. The EDGE-9 reference point can be provided between the EES within different EDNs and within the same EDN.

The Edge Enabler Server (EES) provides supporting functions for Edge Application Server and the Edge Enabler Client. Functionalities of the Edge Activation Server are as follows: A) providing configuration information to the Edge Activation Client, thereby enabling application traffic to be exchanged with the Edge Application Server; b) supporting the functionalities of the API caller and the API detection function; c) interacting with the 3GPP core network to access network function capabilities either directly (e.g. via PCF) or indirectly (e.g. via SCEF/NEF/SCEF+NEF); and d) supporting application context transfer functionalities.

The following cardinality rules apply to Edge Activation Server: A) one or more EES may reside in an EDN; b) one or more EES may reside in an EDN per Edge Computing Service Provider (ECSP).

The EAS is the application server that resides in the data edge network and performs the server functions. The application client connects to the edge application server to use the application's services with the benefits of edge computing. It is possible for an application's server capabilities to be available only as the Edge application server. However, if the application's server capabilities are available both as an edge application server and as an application server located in the cloud, it is possible that the capabilities of the edge application server and the application server are not the same. Additionally, if the capabilities of the edge application server and the application server are different, the application traffic may also be different.

The edge application server can consume the 3GPP core network capabilities in different ways, such as: A) it can call 3GPP core network function APIs directly if it is an entity trusted by the 3GPP core network; b) it can invoke 3GPP core network capabilities through the edge activation server; and c) it can invoke the 3GPP core network capability through the capability discovery functions (e.g. SCEF or NEF).

The following cardinality rules apply to edge application servers: A) One or more EAS can reside in an EDN. The EAS(s) belonging to the same EAS-ID may be provided by one or more ECSPs in an EDN.

The Edge Activation Server ID (EESID) is the Fully Qualified Domain Name (FQDN) of the Edge Activation Server and each Edge Activation Server ID is unique within a PLMN domain.

The Edge Application Server ID (EASID) identifies a specific application for e.g. B. SA6Video, SA6Game, etc. For example, all Edge SA6Video Servers share the same Edge Application Server ID. The format for the EAS ID is outside the scope of this specification. Table E28.2.4-1 shows edge application server profile IDs. Table E28.2.4-1: Edse application serverorofil information element status Description EAS ID M identifier of the EAS EAS endpoint M Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS. This information can be recognized by the EEC and exposed to application clients so that application clients can contact the EAS. Application Client ID(s) O Identifies the application client(s) that can be served by the EAS EAS provider identifier O EAS provider identifier EAS type O Category or type of EAS (e.g. V2X) EAS description O Human-readable description of the EAS EAS planning O Availability plan for the EAS (e.g. time slots) EAS service area O Geographic service area served by the EAS EAS service KPIs O Service features provided by the EAS detailed in Table 8.2.5-1 Service Continuity Support O Indicates whether the EAS supports service continuity or not. EAS Availability Report Period O Availability reporting period (e.g. heartbeat period) that tells the EES how often to check the availability of the EAS after a successful registration. Service APIs required by the EAS O A list of service APIs required by the EAS EAS status O Status of the EAS (e.g. enabled, disabled, etc.)

Edge application server key performance indicators (KPIs) provide information about service characteristics provided by the edge application server (see, e.g., Table E28.2.5-1). Table E28.2.5-1: Edee Application Server Service KPIs information element status Description Maximum request rate O Maximum request rate of the application client supported by the server. Maximum response time O The maximum advertised response time for the application client's service requests. Availability O Advertised percentage of time that the server will be available for use by the application client. Available computing O The maximum computing resource available to the application client. Available graphic computing O The maximum graphical computing resource available to the application client. Available memory O The maximum memory resource available to the application client. Available data storage O The maximum datastore resource available to the application client. connection bandwidth O The connection bandwidth in Kbps advertised for the application client usage. NOTE: The maximum response time includes the round-trip time of the request and response packet, the processing time at the server, and the time it takes for the server to consume 3GPP core network capabilities, if any.

The edge activation server profile includes information about the EES and the services it provides (see for example Table E28.2.6-1). Table E28.2.6-1: Edge activation server profile information element status Description EES ID M identifier of the EES EES endpoint M Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EES. This information is provided to the EEC for connection to the EES. Edge Application Server Profiles M List of Edge Application Servers registered with the EES. EES provider identifier O EES provider identifier (such as ECSP)

The network capability exposure to the one or more edge application servers depends on the deployment scenarios and the business relationship of the ASP/ECSP with the PLMN operator. The following mechanisms are supported: direct network capability discovery and/or network capability discovery via edge activation server.

In some implementations, network capability exposure to one or more EAS depends on the deployment scenarios and the business relationship of the ASP/ECSP with the PLMN operator. The following mechanisms are supported: direct network capability discovery and/or network capability discovery via edge activation server. In some implementations, the charging functionalities with different deployment possibilities depending on business relationships between edge application service provider, edge computing service provider and SFC service provider are outside the scope of the present disclosure (SA5 study).

6 12 illustrates an inter-EDN, according to some embodiments. 7 12 illustrates an intra EDN, according to some embodiments. The EDGE 9 reference point enables interactions between two edge activation servers. The EDGE-9 reference point can be used between EES within different EDNs, as shown in Figure E3, and within the same EDN, as shown in 7 shown to be provided.

8th 12 illustrates a service provider relationship in an edge computing network deployment, according to some embodiments. 8th shows the roles and relationship of service providers involved in deploying edge computing services. The Application Service Provider (ASP) is responsible for creating an EAS and Application Client (AC). The ECSP is responsible for deploying EDNs containing the EAS and the EES that provide configuration information to the EEC, allowing the AC to exchange application traffic with the EAS. The PLMN operator is responsible for deploying 5G network features such as SGC and SG-NR.

The end user is the consumer of the applications/services provided by the ASP and can have an ASP service agreement with a single application service provider or multiple application service providers. The end user has a PLMN subscription agreement with the PLMN operator. The UE used by the end user is allowed to be registered in the PLMN operator network. The ASP consumes the edge services (e.g., infrastructure, platform, etc.) provided by the ECSP and may have one or more ECSP service agreements with a single ECSP or multiple ECSPs. The ECSP can be a mobile network operator or a third party that offers edge computing services. A single PLMN operator may have the PLMN operator service agreement with a single computing service provider or multiple edge computing service providers. A single ECSP can have a PLMN Provider Service Agreement with a single PLMN Provider or with multiple PLMN operators that provide edge computing support. The ECSP and the PLMN operator can be part of the same organization or different organizations.

As above, the 3GPP management system manages the 3GPP defined network functions (e.g. UPF, PCF, EES, ECS, EAS...) and services. To support edge computing management, the 3GPP management system includes both a PLMN management system responsible for orchestrating and managing the cellular networks and an ECSP management system responsible for orchestrating and managing the EDN. The ECSP and the PLMN operator can be part of the same organization.

• 5 Anwendungsfälle
• 5.1 Anwendungsfälle auf Geschäftsebene
• 5.1.x Einsatz von einem oder mehreren Edge-Anwendungsservern
• 5.1.x.1 Einsatz des EAS in dem EDN durch einen PLMN/EC-Dienstanbieter
• 5.1.x.1.1 Ziel

The mechanisms for deploying the Edge Application Servers, Edge Activation Servers, Edge Configuration Servers, and 5G cellular networks to support Edge Computing for 3GPP TR 28.814 are disclosed herein. The embodiments herein also include business-level and specification-level use cases and requirements, including various deployments. The deployments include: the EAS in the EDN by the PLMN/EC service provider; the EAS in the EDN by the ECSP; the EES in the EDN by the PLMN/EC service provider; the EES in the EDN by the ECSP; the ECS by the PLMN/EC service provider; and the ECS through the ECSP, where the PLMN/EC service provider indicates that the operator owns both the PLMN and the EDN.

• 5 use cases
• 5.1 Business Level Use Cases
• 5.1.x Deployment of one or more edge application servers
• 5.1.x.1 Deployment of the EAS in the EDN by a PLMN/EC service provider
• 5.1.x.1.1 Goal

One goal is to allow the ASP to install or uninstall one or more EAS in the EDN. It is assumed that both the PLMN networks and the EDN belong to the same organization, called the PLMN/EC service provider.

5.1.x.1.2 Prerequisites

The ASP has a service agreement with the PLMN/EC service provider.

The PLMN/EC service provider has deployed one or more EDNs.

5.1.x.1.3 Description

5.1.x.1.3.1 EAS installation

• 1. The ASP requests the PLMN/EC service provider to install one or more EAS with deployment requirements.
• 2. The PLMN/EC service provider selects the EDN to host the EAS based on the deployment requirements.
• 3. The PLMN/EC service provider installs the EAS in the EDN that meets the deployment requirements.
• 4. The PLMN/EC service provider notifies the ASP that the EAS was installed successfully.

5.1.x.1.3.2 EAS termination

1. 1. The ASP requests the PLMN/EC service provider to terminate one or more EAS with the EAS identifier(s).
2. 2. The PLMN/EC service provider terminates the EAS based on the identifier in the EDN.
3. 3. The PLMN/EC service provider notifies the ASP that the EAS completed successfully.

5.1.x.2 Deployment of an EAS in an EDN by an ECSP

5.1.x.2.1 Goal

The goal is to allow the ASP to install or terminate one or more EAS in an EDN in the ECSP (Edge Computing Service Provider).

5.1.x.2.2 Prerequisites

The ASP has a service level agreement with the ECSP.

The ECSP provider deployed EDN(s).

5.1.x.2.3 Description

5.1.x.2.3.1 EAS installation

1. 1. The ASP requests the ECSP to install one or more EAS with deployment requirements.
2. 2. The ECSP selects the EDN to host the EAS based on the deployment requirements.
3. 3. The ECSP installs the EAS on the selected edge data network.
4. 4. The ECSP notifies the ASP that the EAS was installed successfully.

5.1.x.2.3.2 EAS termination

1. 1. The ASP requests the ECSP to terminate one or more EAS with EAS identifier(s).
2. 2. The ECSP terminates the EAS based on the identifier in the EDN.
3. 3. The ECSP notifies the ASP that the EAS completed successfully.

5.1.y Deployment of one or more edge activation servers

5.1.y.1 Deployment of the EES in the EDN by a PLMN/EC service provider

5.1.y.1.1 Goal

The goal is to allow installation and termination of one or more EES in the EDN. It is believed that the edge computing service provider and the PLMN operator can be part of the same organization, referred to as the PLMN/EC service provider.

5.1.y.1.2 Prerequisites

The PLMN/EC service provider is operational.

5.1.y.1.3 Description

5.1.y.1.3.1 EES installation

1. 1. The PLMN/EC service provider has received a request to install one or more EES with deployment requirements.
2. 2. The PLMN/EC service provider selects an EDN to host the EES.
3. 3. The PLMN/EC service provider installs the EES.
4. 4. The PLMN/EC service provider sends a notification to indicate that the EES was installed successfully.

5.1.y.1.3.2 EES termination

1. 1. The PLMN/EC service provider received a request to terminate one or more EES with the EES identifier.
2. 2. The PLMN/EC service provider terminates the EES based on the EES identifier.
3. 3. The PLMN/EC service provider sends a notification to indicate that the EES was successfully terminated.

5.1.y.2 Deployment of an EES in the EDN by an ECSP

5.1.y.2.1 Goal

The goal is to allow the installation and termination of one or more EES in the EDN in the ECSP.

5.1.y.2.2 Prerequisites

The ECSP is operational.

5.1.y.2.3 Description

5.1.y.2.3.1 EES installation

1. 1. The ECSP has received a request to install one or more EES with deployment requirements.
2. 2. The ECSP selects the EDN to host the EES.
3. 3. The ECSP installs the EES on the selected edge data network.
4. 4. The ECSP sends a notification to indicate that the EES was installed successfully.

5.1.y.2.3.2 EES termination

1. 1. The ECSP has received a request to terminate one or more EES with the EES identifier.
2. 2. The ECSP terminates the EES based on the EES identifier.
3. 3. The ECSP sends a notification to indicate that the EES has completed successfully.

5.1.z Deployment of one or more edge configuration servers

5.1.z. 1 Deployment of an ECS by a PLMN operator

5.1.z.1.1 Goal

The goal is to allow the installation and termination of one or more ECS in the PLMN operator.

5.1.z.1.2 Prerequisites

The PLMN operator is operational.

5.1.z.1.3 Description

5.1.z.1.3.1 ECS installation

1. 1. The PLMN operator receives a request to install one or more ECS.
2. 2. The PLMN operator installs the ECS.
3. 3. The PLMN operator sends a notification indicating that the ECS was installed successfully.

5.1.z.1.3.2 ECS termination

1. 1. The PLMN operator receives a request to terminate one or more ECS with the ECS identifier.
2. 2. The PLMN operator terminates the ECS based on the ECS identifier.
3. 3. The PLMN operator sends a notification to indicate that the ECS terminated successfully.

5.1.z.2 Use of an ECS by an ECSP

5.1.z.2.1 Goal

The goal is to allow the installation and termination of one or more ECS in the ECSP.

5.1.z.2.2 Prerequisites

The ECSP is operational.

5.1.z.2.3 Description

5.1.z.2.3.1 ECS installation

• 1. The ECSP receives a request to install one or more ECS.
• 2. The ECSP selects the EDN to the ECS.
• 3. The ECSP installs the ECS.
• 3. The ECSP sends a notification to indicate that the ECS was installed successfully.

5.1.z.2.3.2 ECS termination

1. 1. The ECSP receives a request to terminate one or more ECS with the ECS identifiers.
2. 2. The ECSP terminates the one or more ECS based on the ECS identifiers.
3. 3. The ECSP sends a notification indicating that the ECS completed successfully.

5.2 Specification Level Use Cases

5.2.x Deployment of one or more edge application servers

5.2.x.1 Deployment of an EAS in an EDN by a PLMN/EC service provider

5.2.x.1.1 Goal

The goal is to allow the ASP to install or terminate the EAS in the EDN.

5.2.x.1.2 Prerequisites

The ASP has a service agreement with the PLMN/EC service provider.

The EES have been deployed in the EDN.

The SGC networks have been deployed.

5.2.x.1.3 Description

5.2.x.2.3.1 EAS installation

1. 1. A consumer consumes the management service of a PLMN/EC management system to provide the EAS with application packages (e.g. VNF, VNFD, etc.) and deployment requirements (e.g. virtualized resource requirements (e.g. compute, storage, etc.) .), QoS requirements (e.g. latency, bandwidth) and geographic service areas, etc.).
2. 2. The PLMN/EC management system determines in which EDN the EAS is deployed based on the deployment requirements. The selection of the EDN in which the EAS is installed may be determined by, for example, QoS requirements and geographic service area requirements.
3. 3. The PLMN/EC management system consumes the management service of ETSI NFV MANO to perform the following operations: Instantiate the EAS VNF Connecting the EAS to the EES. Connecting the EAS to the SGC network functions to send the information over N6 and Edge 7 interfaces.
4. 4. The PLMN/EC management system notifies the ASP management system that the EAS was installed successfully.

5.2.x.2.3.1 EAS Termination

1. 1. A consumer consumes the management service of the PLMN/EC management system to terminate the EAS with the EAS identifier.
2. 2. The PLMN/EC management system terminates the EAS VNF based on the EAS identifier and disconnects the EAS from the SGC network functions.
3. 3. The PLMN/EC management system notifies the ASP management system that the EAS completed successfully.

5.2.x.2 Deployment of an EAS in an EDN by an ECSP

5.2.x.2.1 Goal

The goal is to allow the ASP to install or terminate the EAS in an EDN in the ECSP.

5.2.x.2.2 Prerequisites

The ASP has a service level agreement with the ECSP.

The EES have been deployed in the EDN.

The SGC networks have been deployed.

5.2.x.2.3 Description

5.2.x.2.3.1 EAS installation

1. 1. A consumer consumes the management service of the ECSP management system to provide the EAS with application packages (e.g. VNF, VNFD...etc.) and deployment requests (e.g. virtualized resource requests (e.g. compute, storage, ...), QoS requirements (e.g. latency, bandwidth) and geographical service areas ... etc.).
2. 2. The ECSP management system determines in which EDN the EAS is deployed based on the deployment requirements. The selection of the EDN in which the EAS is installed may be determined by, for example, QoS requirements and geographic service area requirements.
3. 3. The ECSP management system consumes the management service of ETSI NFV MANO to perform the following operations: Instantiate the EAS VNF Connect the EAS to the EES. Connecting the EAS to the SGC network functions to send the information over N6 and Edge 7 interfaces.
4. 4. The ECSP management system notifies the ASP management system that the EAS was installed successfully.

5.2.x.2.3.2 EAS installation

1. 1. A consumer consumes the management service of the ECSP management system to terminate the EAS with the EAS identifier.
2. 2. The ECSP management system terminates the EAS VNF based on the EAS identifier and separates the EAS from the SGC network functions.
3. 3. The ECSP management system notifies the ASP management system that the EAS completed successfully.

5.2.x Deployment of one or more edge activation servers

5.2.y Deployment of one or more Edge Activation Servers

5.2.y.1 Deployment of the EES in the EDN by a PLMN/EC service provider

5.2.y.1.1 Goal

The goal is to allow installation and termination of one or more EES in the EDN.

5.2.y.1.2 Prerequisites

The PLMN/EC management system in the PLMN/EC service provider is operational.

The SGC networks have been deployed.

5.2.y.1.3 Description

5.2.y.1.3.1 EES installation

1. 1. A consumer consumes the management service of the PLMN/EC management system to provide the EES with EES packets (e.g. VNF, VNF packet...etc.) and deployment requests (e.g. virtualized resource requests (e.g .Calculation, storage...) to install.
2. 2. The PLMN/EC management system determines the EDN where the EES will be installed.
3. 3. The PLMN/EC management system performs the following operations to install the EES: Instantiate the EES VNF Connecting the EES to the SGC network functions to send the information over the Edge 2 interfaces.
4. 4. The PLMN/EC management system sends a notification to indicate that the EES has been installed successfully.

5.2.y.1.3.2 EES termination

1. 1. A consumer consumes the management service of the PLMN/EC management system to terminate the EES with the EES identifier.
2. 2. The PLMN/EC management system terminates the EES VNF based on the EES identifier and separates the EES from the SGC network functions.
3. 3. The PLMN/EC management system sends a notification to indicate that the EES has been completed successfully.

5.2.y.2 Deployment of an EES in an EDN by an ECSP

5.2.y.2.1 Goal

The goal is to allow the installation and termination of one or more EES in the EDN in the ECSP.

5.2.y.2.2 Prerequisites

The ECSP management system in the ECSP is operational.

The EES(s) have been deployed in the EDN.

The SGC networks have been deployed.

5.2.y.2.3 Description

5.2.y.2.3.1 EES installation

1. 1. A consumer consumes the management service of the ECSP management system to install the EES with application packages (e.g. VNF, VNF package...etc.) and deployment requirements.
2. 2. The ECSP management system determines the EDN in which the EES will be deployed.
3. 3. The ECSP management system performs the following operations to install the EES: Instantiate the EES VNF Connecting the EES to the SGC network functions to send the information over the Edge 2 interfaces.
4. 4. The ECSP management system sends a notification to indicate that the EES was installed successfully.

5.2.y.2.3.2 EES termination

1. 1. A consumer consumes the management service of the ECSP management system to terminate the EES with the EES identifier.
2. 2. The ECSP management system determines the EDN in which the EES will be deployed.
3. 3. The ECSP management system terminates the EES VNF based on the EES identifier and disconnects the EES from the SGC network functions.
4. 4. The ECSP management system sends a notification to indicate that the EES has completed successfully.

5.2.z Deployment of one or more edge configuration servers

5.2.z. 1 Deployment of an ECS by a PLMN operator

5.2.z.1.1 Goal

The goal is to allow the installation and termination of one or more ECS in the PLMN operator.

5.2.z.1.2 Prerequisites

The PLMN management system in the PLMN operator is operational.

The SGC networks have been deployed.

5.2.z.1.3 Description

5.1.z.1.3 ECS installation

1. 1. A consumer consumes the management service of the PLMN management system to install the ECS with application packages (e.g. VNF, VNF package...etc.).
2. 2. The PLMN management system performs the following operations to install the ECS: Instantiate the ECS VNF Connecting the ECS to the SGC network functions to send the information over the Edge 8 interfaces.
3. 3. The PLMN management system sends a notification to indicate that the ECS was installed successfully.

5.1.z.1.3 ECS termination

1. 1. A consumer consumes the management service of the PLMN management system to terminate the ECS with the ECS identifier.
2. 2. The PLMN management system terminates the ECS VNF based on the ECS identifier and disconnects the ECS from the SGC network functions.
3. 3. The PLMN management system sends a notification to indicate that the ECS was successfully terminated.

5.2.z. 2 Deployment of an ECS by an ECSP

5.2.z.2.1 Goal

The goal is to allow the installation and termination of one or more ECS in the ECSP.

5.2.z.2.2 Prerequisites

The ECSP management system in the ECSP is operational.

The SGC networks have been deployed.

5.2.z.2.3 Description

5.1.z.2.3.1 ECS installation

1. 1. A consumer consumes the management service of the ECSP management system to install the ECS with application packages (e.g. VNF, VNF package...etc.).
2. 2. The ECSP management system selects the EDN to install the ECS.
3. 3. The ECSP management system performs the following operations to install the EES: Instantiate the ECS VNF Connecting the ECS to the SGC network functions to send the information over the Edge 8 interfaces.
4. 4. The ECSP management system sends a notification to indicate that the ECS has been deployed successfully.

5.1.z.2.3.2 ECS termination

1. 1. A consumer consumes the management service of the ECSP management system to terminate the ECS with the ECS identifier.
2. 2. The ECSP management system terminates the ECS VNF based on the ECS identifier and disconnects the ECS from the SGC network functions.
3. 3. The ECSP management system sends a notification indicating that the ECS has been successfully deployed (here: terminated).

6 Potential Requirements

6.1 Business Level Requirements

6.1.x Edge Application Server

• REQ-EAS-DEPLOY-CON-a The PLMN/EC service provider management system should allow a consumer to request installation of one or more EAS in the EDN with the deployment requirements.
• REQ-EAS-DEPLOY-CON-b The management system of the PLMN/EC service provider should allow a consumer to request the termination of one or more EAS in the EDN with the EAS identifier.
• REQ-EAS-DEPLOY-CON-c The PLMN/EC service provider management system should be able to send the notification indicating the status of the EAS installation and termination.
• REQ-EAS-DEPLOY-CON-d The management system of the ECSP should allow a consumer to request the installation of one or more EAS in the EDN with the deployment requirements.
• REQ-EAS-DEPLOY-CON-e The management system of the ECSP should allow a consumer to request installation and termination of one or more EAS in the EDN with the EAS identifier.
• REQ-EAS-DEPLOY-CON-f The management system of the ECSP should be able to send the notification indicating the status of the EAS installation and termination.

6.1.Y Edge activation server

• REQ-EES-DEPLOY-CON-a The PLMN/EC service provider management system should allow a consumer to request installation of the EES with deployment requirements.
• REQ-EES-DEPLOY-CON-b The management system of the PLMN/EC service provider should allow a consumer to request the termination of the EES with the EES identifier.
• REQ-EES-DEPLOY-CON-c The PLMN/EC service provider management system should be able to send the notification indicating the status of EES installation and termination.
• REQ-EES-DEPLOY-CON-d The ECSP should allow a consumer to request installation of the EES in the EDN with deployment requirements.
• REQ-EES-DEPLOY-CON-c The ECSP should allow a consumer to request termination of the EES in the EDN with the EES identifier.
• REQ-EES-DEPLOY-CON-f The ECSP should be able to send the notification indicating the status of EES installation and termination.

6.1.z Edge Configuration Server

• REQ-ECS-DEPLOY-CON-a The PLMN operator's management system should allow the PLMN provider to request the installation of the ECS.
• REQ-ECS-DEPLOY-CON-b The management system of the PLMN operator should allow the PLMN provider to request the termination of the ECS with the ECS identifier.
• REQ-ECS-DEPLOY-CON-c The PLMN operator management system should be able to send the notification indicating the status of ECS installation and termination.
• REQ-ECS-DEPLOY-CON-d The management system of the ECSP should allow the PLMN provider to request the installation of the ECS.
• REQ-ECS-DEPLOY-CON-e The management system of the ECSP should allow the PLMN provider to request the termination of the ECS with the ECS identifier.
• REQ-ECS-DEPLOY-CON-f The management system of the ECSP should be able to send the notification indicating the status of the ECS installation and termination.

6.2 Specification Level Requirements

6.2.x Edge Application Server

• REQ-EAS-DEPLOY-FUN-a The PLMN/EC management system should provide management services to allow consumers to install EAS with application packages (e.g. VNF, VNFD...etc.) and deployment requirements (e.g. B. virtualized resource requirements (e.g. compute, storage...), QoS requirements (e.g. latency, bandwidth) and geographic service areas...etc.).
• REQ-EAS-DEPLOY-FUN-b The PLMN/EC management system should provide management services to allow consumers to request termination of the EAS with the EAS identifier.
• REQ-EAS-DEPLOY-FUN-c The PLMN/EC management system should be able to instantiate the EAS VNF on the EDN, connect the EAS to the EES and the EAS to the SGC network functions to send the information to connect via N6 and Edge 7 interfaces.
• REQ-EAS-DEPLOY-FUN-d The PLMN/EC management system should be able to terminate the EAS VNF based on the EAS identifier and detach the EAS from the SGC network functions.
• REQ-EAS-DEPLOY-FUN-e The PLMN/EC management system should be able to send the notification indicating the status of EAS installation and termination.
• REQ-EAS-DEPLOY-FUN-f The ECSP management system should provide management services to allow consumers to install an EAS with application packages (e.g. VNF, VNFD...etc.) and deployment requirements (e.g. virtualized resource requirements (e.g. compute, storage...), QoS requirements (e.g. latency, bandwidth) and geographic service areas...etc.).
• REQ-EAS-DEPLOY-FUN-g The ECSP management system should provide management services to allow consumers to request termination of EAS with the EAS identifier.
• REQ-EAS-DEPLOY-FUN-h The ECSP management system should be able to instantiate the EAS VNF in the EDN, connect the EAS to the EES and the EAS to the SGC network functions to send the information over N6 - and Edge 7 interfaces to connect.
• REQ-EAS-DEPLOY-FUN-i The ECSP management system should be able to terminate the EAS VNF based on the EAS identifier and detach the EAS from the SGC network functions.
• REQ-EAS-DEPLOY-FUN-j The ECSP management system should be able to send the notification indicating the status of EAS installation and termination.

6.2.y Edge activation server

• REQ-EES-DEPLOY-FUN-a The PLMN/EC management system should provide management services to allow consumers to install an EES with EES packages (e.g. VNF, VNF package...etc.) and Request deployment requirements (e.g. virtualized resource requirements (e.g. compute, storage...).
• REQ-EES-DEPLOY-FUN-b The PLMN/EC management system should provide management services to allow consumers to request termination of the EES with the EES identifier.
• REQ-EES-DEPLOY-FUN-c The PLMN/EC management system should be able to instantiate the EES-VNF in the EDN and connect the EES to the SGC network functions to send the information over Edge 2 interfaces.
• REQ-EES-DEPLOY-FUN-d The PLMN/EC management system should be able to terminate the EES VNF based on the EES identifier and detach the EES with the SGC network functions.
• REQ-EES-DEPLOY-FUN-e The PLMN/EC management system should be able to send the notification indicating the status of EES installation and termination.
• REQ-EES-DEPLOY-FUN-f The ECSP management system should provide management services to allow consumers to install EES with EES packages (e.g. VNF, VNF package...etc.) and deployment requirements ( e.g., to request virtualized resource requests (e.g., compute, memory...).
• REQ-EES-DEPLOY-FUN-g The ECSP management system should provide management services to allow consumers to request termination of the EES with the EES identifier.
• REQ-EES-DEPLOY-FUN-h The ECSP management system should be able to terminate the EES VNF in the EDN and detach the EES to the 5GC network functions to send the information over the Edge 2 interfaces.
• REQ-EES-DEPLOY-FUN-i The ECSP management system should be able to terminate the EES VNF based on the EES identifier and detach the EES from the SGC network functions.
• REQ-EES-DEPLOY-FUN-j The ECSP management system should be able to send the notification indicating the status of EES installation and termination.

6.2.z Edge Configuration Server

• REQ-ECS-DEPLOY-FUN-a The PLMN management system should provide management services to allow consumers to request installation of the ECS with application packages (e.g. VNF, VNF package...etc.).
• REQ-ECS-DEPLOY-FUN-b The PLMN management system should provide management services to allow consumers to request termination of the ECS with the ECS identifier.
• REQ-ECS-DEPLOY-FUN-c The PLMN management system should be able to instantiate the ECS VNF in the EDN and connect the ECS to the SGC network functions to send the information over Edge-8 interfaces.
• REQ-ECS-DEPLOY-FUN-d The PLMN management system should be able to terminate the ECS VNF based on the ECS identifier and detach the ECS from the SGC network functions.
• REQ-ECS-DEPLOY-FUN-e The PLMN management system should be able to send the notification indicating the status of the EAS installation and termination.
• REQ-ECS-DEPLOY-FUN-f The ECSP management system should provide management services to allow consumers to request installation of ECS application packages (e.g. VNF, VNF package...etc.).
• REQ-ECS-DEPLOY-FUN-g The ECSP management system should provide management services to allow consumers to request the termination of an ECS with the ECS identifier.
• REQ-ECS-DEPLOY-FUN-h The ECSP management system should be able to instantiate the ECS VNF in the EDN and connect the ECS to the SGC network functions to send the information over Edge-8 interfaces.
• REQ-ECS-DEPLOY-FUN-i The PLMN management system should be able to terminate the ECS VNF based on the ECS identifier and detach the ECS from the SGC network functions.
• REQ-ECS-DEPLOY-FUN-j The ECSP management system should be able to send the notification indicating the status of EAS installation and termination.

The EAS is an application server that resides in the data edge network and performs the server functions. This use case concerns the case when the EAS is to be deployed in the operator's EDN managed by the operator's management system. The lifecycle of the EAS (instancing, termination, scaling, etc.) has to be managed and there can be multiple EDNs serving a given edge location. In order to deploy an EDN as a local data network, the serving location and the constituent edge entities (EAS and EES) are defined for each EDN. The ECSP management system is requested to instantiate the entities as 3GPP network functions targeting the specific location server. The instantiated EES can serve one or more EAS.

Although an embodiment has been described with reference to specific example embodiments, it is apparent that various modifications and changes can be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are in an illustrative manner and not to be construed in a limiting sense. The accompanying drawings which form a part hereof show by way of illustration and not limitation specific embodiments in which the subject matter may be embodied. The illustrated embodiments 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 from them 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 various embodiments is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.

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

In this document, the term "a" is used, as is conventional in patent specifications, to include one or more than one, regardless of other cases or usages 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” is both “A but not B” and “B but not A” and “A and B” includes unless otherwise noted. In this document, the terms “comprising” and “in which/in which” are used as equivalents of the corresponding terms “comprising” and “wherein”. Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such term in a claim is still contemplated as falling within the scope of that claim. Also, in the following claims, the terms "first", "second", "third", etc. are used as labels only and are not intended to impose numerical requirements on their objects .

The Summary of Disclosure is in compliance with 37 C.F.R. §1.72(b) requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, 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. However, this type of disclosure should not be construed 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. Accordingly, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• US63/055057 [0001]

Claims (20)

A device configured to operate as a service provider in a New Radio (NR) network, the device comprising: processing circuitry configured to: Receiving, from an application service provider (ASP), a first request to install an edge computing (EC) network function (NF) to support EC, the EC-NF being selected from a set of EC-NFs having an edge Application Server (EAS) includes; or receiving, from another entity, a first request to install an edge computing (EC) network function (NF) to support EC, the EC-NF selected from a set of EC-NFs that includes: an edge - Activation Server (EES) and an Edge Configuration Server (ECS) NF; in response to the first request, installing the EC-NF and sending a first notification to the ASP or other entity to indicate the installation of the EC-NF; receiving, from the ASP or other entity, a second request to terminate the EC-NF after installing the EC-NF, the second request including an identifier of the EC-NF; and in response to the second request, terminating the EC-NF and sending a second notification to the ASP or other entity to indicate termination of the EC-NF; and a memory configured to store the first and second requests. setup after claim 1 wherein the processing circuitry is configured to select one of a plurality of Edge Data Networks (EDNs) to host the EC-NF based on deployment conditions in response to the first request. setup after claim 2 , where the deployment conditions include quality of service (QoS), geographic service area conditions and virtualized resources to be used. setup after claim 1 , where the service provider is an edge computing service provider (ECSP) that includes an ECSP management system. setup after claim 4 , wherein: the first request is a request to install an EAS and the second request is a request to terminate the EAS, in response to receiving the first request the ECSP management system is configured to: instantiate an EAS virtual network function (VNF ) and after instantiating the EAS VNF, connecting the EAS to the EES and connecting the EAS to 5 ^th Generation Core (5GC) NFs to send information over N6 and Edge 7 interfaces, and in response to receipt the second request comprising an EAS identifier of the EAS to be terminated, the ECSP management system is configured to: terminate the EAS VNF with the EAS identifier and disconnect the EAS from the SGC NFs. setup after claim 4 , wherein: the first request is a request to install an EES and the second request is a request to stop the EES, in response to receiving the first request the ECSP management system is configured to: instantiate an EES virtual network function (VNF ) and after instantiating the EES VNF, connecting the EES to 5 ^th Generation Core (5GC) NFs to send information over N6 and Edge 2 interfaces, and in response to receiving the second request, the a EES identifier of the EES to be terminated, the ECSP management system is configured to: terminate the EES-VNF with the EES identifier and disconnect the EES from the SGC-NFs. setup after claim 4 , where: the first request is a request to install an ECS and the second request is a Request to terminate the ECS is, in response to receiving the first request, the ECSP management system is configured to: instantiate an ECS virtual network function (VNF) and after instantiating the ECS VNF, connecting the EES to ^5th Generation Core (5GC) NFs to send information over N6 and Edge 8 interfaces, and in response to receiving the second request, which includes an ECS identifier of the ECS to be terminated, the ECSP management system is configured to: Terminating the ECS VNF with the ECS identifier and detaching the ECS from the SGC NFs. setup after claim 1 wherein the service provider is a Public Land Mobile Network (PLMN) and/or EC service provider, each comprising a PLMN or EC management system. setup after claim 8 wherein: the first request is a request to install an EAS and the second request is a request to terminate the EAS, in response to receiving the first request, the PLMN or EC management system is configured to: instantiate a virtual EAS - Network Function (VNF) and after instantiating the EAS VNF, connecting the EAS to the EES and connecting the EAS to 5 ^th Generation Core(5GC) NFs to send information over N6 and Edge 7 interfaces, and in In response to receiving the second request comprising an EAS identifier of the EAS to be terminated, the PLMN or EC management system is configured to: terminate the EAS VNF with the EAS identifier and disconnect the EAS from the SGC NFs . setup after claim 8 , wherein: the first request is a request to install an EES and the second request is a request to terminate the EES, in response to receiving the first request, the PLMN or EC management system is configured to: instantiate a virtual EES - Network Function (VNF) and after instantiating the EES VNF, connecting the EES to 5 ^th Generation Core (5GC) NFs to send information over N6 and Edge 2 interfaces and in response to receiving the second Request comprising an EES identifier of the EES to be terminated, the PLMN or EC management system is configured to: terminate the EES-VNF with the EES identifier and disconnect the EES from the SGC-NFs. setup after claim 8 , wherein: the first request is a request to install an ECS and the second request is a request to terminate the ECS, in response to receiving the first request, the PLMN or EC management system is configured to: instantiate a virtual ECS - Network Function (VNF) and after instantiating the ECS VNF, connecting the EES to 5 ^th Generation Core (5GC) NFs to send information over N6 and Edge 8 interfaces and in response to receiving the second Request comprising an ECS identifier of the ECS to be terminated, the PLMN or EC management system is configured to: terminate the ECS VNF with the ECS identifier and disconnect the ECS from the SGC NFs. setup after claim 1 , wherein the processing circuitry is configured in response to the first request to: select, based on deployment conditions, one of a plurality of edge data networks (EDNs) to host the EC-NF, and install the EC-NF in the one of the EDNs. setup after claim 1 , wherein the EC-NF is: a first EES in an edge data network (EDN) for providing configuration information to an edge activation client (EEC) and for enabling the exchange of application traffic between a first EAS and an application client (AC) in a user equipment (UE), or a second EES for providing the configuration information to the EEC and for enabling the exchange of application traffic between the first EAS and the AC in the UE. setup after claim 1 , wherein the processing circuitry is further configured to generate: in an edge data network (EDN), an EAS-NF configured to perform server functions, and in a user equipment (UE), an application client (AC) -NF configured to perform client functions. A device configured to operate as a service provider management system, the device comprising: processing circuitry configured to: receive a first request to install an edge computing (EC) network function (NF) to support EC wherein the EC-NF is selected from a set of EC-NFs including: an Edge Application Server (EAS), an Edge Activation Server (EES), and an Edge Configuration Server (ECS); in response to receiving the first request: instantiating a virtual EC network function (VNF) of the EC-NF and after instantiating the EC-VNF, connecting the EC-NF to 5 ^th Generation Core (5GC) NFs to obtain information about Edge - send interfaces and send a first notification to indicate the installation of the EC-NF; receiving a second request to terminate the EC-NF after installing the EC-NF, the second request including an EC-NF identifier of the EC-NF; and in response to receiving the second request: terminating the EC-NF associated with the EC-NF identifier, disconnecting the EC-NF from the 5GC-NFs, and sending a second notification to indicate termination of the EC-NF; and a memory configured to store the first and second requests. setup after claim 15 wherein the service provider is a Public Land Mobile Network (PLMN) and/or EC service provider and the management system comprises a PLMN or EC management system, respectively. setup after claim 15 , wherein the service provider is an edge computing service provider (ECSP) and the management system comprises an ECSP management system. setup after claim 15 , wherein the processing circuitry is configured in response to the first request to: select, based on deployment conditions, one of a plurality of edge data networks (EDNs) to host the EC-NF, and install the EC-NF in the one of the EDNs. Non-transitory computer-readable data storage medium storing instructions for execution by one or more processors of a service provider in a Next Generation (NG) network, wherein the one or more processors, when executing the instructions, configure the service to: receive a first request for installing an Edge Computing (EC) Network Function (NF) to support EC, wherein the EC-NF is selected from a set of EC-NFs including: an Edge Application Server (EAS), an Edge Activation Server (EES) and an Edge Configuration Server (ECS); in response to receiving the first request: instantiating an EC virtual network function (VNF) of the EC-NF and after instantiating the EC-VNF connecting the EC-NF to ^5th Generation Core(5GC) NFs to send information about edge interfaces and sending an initial notification to indicate installation of the EC-NF; receiving a second request to terminate the EC-NF after installing the EC-NF, the second request including an EC-NF identifier of the EC-NF; and in response to receiving the second request: terminating the EC-NF associated with the EC-NF identifier, disconnecting the EC-NF from the 5GC-NFs, and sending a second notification to indicate termination of the EC-NF. medium after claim 19 wherein, in response to the first request, performing: selecting, based on deployment conditions, one of a plurality of Edge Data Networks (EDNs) to host the EC-NF and installing the EC-NF in the one of EDN's.

Images