EP4275341A1 - Edge application server performance assurance - Google Patents

Abstract

An apparatus and system are described to support the edge application server performance assurance. Use case for Edge Application Server (EAS) performance assurance, as well as measurement collection via performance job control and configurable measurement control are described. A consumer requests the 3 GPP management system to collect EAS measurements, including available resources and connection bandwidth on network interfaces to an application client, which are collected and reported via a data file reporting or streaming service. The measurement jobs are created by the Edge Computing Service Provider (ECSP) management system by a measurement job control management service (MnS) with createMeasurementJob operation or a provisioning MnS with createMOI operation.

Description

EDGE APPLICATION SERVER PERFORMANCE ASSURANCE

5 PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63/135,982, filed January 11, 2021, which is incorporated herein by reference in its entirety.

10 TECHNICAL FIELD

[0002] Embodiments pertain to next generation wireless communications. In particular, some embodiments relate to edge computing in 5G networks.

15 BACKGROUND

[0003] The use and complexity of wireless systems, which include 5^th generation (5G) networks and are starting to include sixth generation (6G) networks among others, has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of

20 data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated. As expected, a number of issues abound with the

25 advent of any new technology.

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals

30 having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.

1 [0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1 C illustrates a non-roaming 5G system architecture in accordance with some aspects.

5 [0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates a 5G edge computing network in accordance with some embodiments.

[0010] FIG. 4 illustrates peer-to-peer (P2P) edge computing management

10 deployment in accordance with some embodiments.

[0011] FIG. 5 illustrates architecture for enabling edge applications in accordance with some embodiments.

[0012] FIG. 6 illustrates an inter-Edge Detection Network (EDN) in accordance with some embodiments.

15 [0013] FIG. 7 illustrates an intra-EDN in accordance with some embodiments.

[0014] FIG. 8 illustrates service provider relationship in an edge computing network deployment in accordance with some embodiments.

[0015] FIG. 9 illustrates a performance Management Service (MnS) in

20 accordance with some embodiments.

DETAILED DESCRIPTION

[0016] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other

25 embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0017] FIG. 1 A illustrates an architecture of a network in accordance

30 with some aspects. The network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions. A network function can be implemented as a discrete

2 network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0018] The network 140A is shown to include user equipment (UE) 101

5 and UE 102. The 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 portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless

10 communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0019] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any

15 exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies).

20 Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3 GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

25 [0020] In some aspects, any of the UEs 101 and 102 can comprise an

Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE

30 and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D)

3 communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Interet infrastructure), with short-lived

5 connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0021] The UEs 101 and 102 may be configured to connect, e.g.,

10 communicatively couple, with a radio access network (RAN) 110. 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 some other type of RAN.

[0022] The UEs 101 and 102 utilize connections 103 and 104,

15 respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple

20 access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0023] In an aspect, the UEs 101 and 102 may further directly exchange

25 communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel

30 (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0024] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11

4 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

5 [0025] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a

10 geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The

RAN 110 may include one or more RAN nodes for providing macrocells, e.g.,

15 macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0026] 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.

20 In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the 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 the nodes 111 and/or 112 can be a gNB, an

25 eNB, or another type of RAN node.

[0027] The RAN 110 is shown to be 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 some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this

30 aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115,

5 which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0028J In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home

5 subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related

10 information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution,

15 location dependencies, etc.

[0029] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other

20 responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0030] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively

25 referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks

131 A, which can include the Interet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g.,

30 UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet

6 Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0031 J The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the

5 policy and charging control element of the 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 a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a

10 Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0032] In some aspects, the communication network 140 A can be an loT network or a 5G or 6G network, including 5G new radio network using

15 communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without

20 the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

25 [0033] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network/5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be

30 communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

7 [0034] In some aspects, the NG system architecture can use reference points between various nodes. 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 forth. In some aspects, a gNB can be a master node (MN)

5 and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0035] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 1406 in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 can be in communication

10 with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an 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

15 unified data management (UDM)/home subscriber server (HSS) 146.

[0036] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF

20 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for

25 data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each

30 other.

[0037] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network

8 slicing, mobility management, and roaming (similar to PCRF 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).

[0038] The AF 150 may provide information on the packet flow to the

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

10 [0039] In some aspects, the 5G system architecture 1406 includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF

15 (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency

20 request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network

25 170E, e.g. an IMS operated by a different network operator.

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

30 [0041 J A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates 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

9 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),

5 N10 (between the UDM 146 and the SMF 136, not shown), Nl 1 (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 case of a non-roaming scenario, or between the PCF 148

10 and a visited network and AMF 132 in 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 not shown in FIG. 1 B can also be used.

[0042] FIG. 1C illustrates a 5G system architecture 140C and a service¬

15 based representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as

20 service-based interfaces.

[0043J In some aspects, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service¬

25 based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a servicebased interface exhibited by the UDM 146), Naf 158F (a service-based interface

30 exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other

10 service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0044J NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and

5 aperiodic communications with random packet arrival time and size.

Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0045] FIG. 2 illustrates a block diagram of a communication device in

10 accordance with 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 smart phone, dedicated network equipment 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 instructions (sequential or

15 otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by

20 the receiving entity.

[0046] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an

25 example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole 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 configured by firmware or software (e.g., instructions, an application portion, or an

30 application) as a module that operates 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.

11 [0047] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform

5 part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different

10 modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0048] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing

15 unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memoiy 204 and a static memoiy 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may

20 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 an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a

25 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 further 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

30 communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0049] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable

12 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 static memory 206,

5 and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as 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

10 more instructions 224.

[0050] 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 cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is

15 capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, 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

20 Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.

[0051] The instructions 224 may further be transmitted or received over

25 a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer 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

30 a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Interet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute

13 of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards,

5 peer-to-peer (P2P) networks, a next generation (NG)/5^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.

[0052] Note that the term “circuitiy” as used herein refers to, is part of,

10 or includes hardware components such as an electronic circuit, a logic circuit, 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 (HCPLD), a

15 structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. 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

20 (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out 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 circuitiy.

[0053] The term “processor circuitry” or “processor” as used herein thus

25 refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. 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

30 multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

14 [0054] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet

5 Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long

10 Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), 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

15 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 Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-

20 Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership

25 Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.

30 19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th

15 Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System/Extended

5 Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for

10 Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN),

15 Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards

20 in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. Had, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 Ip or IEEE 802.1 Ibd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to-Vehicle (12 V) communication

25 technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802.1 Ip based DSRC,

30 including TTS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to

16 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

[0055] Aspects described herein can be used in the context of any

5 spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable

10 spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300220)), 915.9-929.7 MHz (note: allocated for example in

15 Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz,

20 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 - 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for

25 example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is

30 expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative

17 (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as

5 WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi-Gigabit Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P)

10 allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the

15 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0056] Aspects described herein can also implement a hierarchical

20 application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.

[0057] Aspects described herein can also be applied to different Single

25 Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0058] Some of the features in this document are defined for the network

30 side, such as APs, eNBs, NR or gNBs - note that this term is typically used in the context of 3GPP 5G and 6G communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.

18 [0059] As above, 5G networks extend beyond the traditional mobile broadband services to provide various new services such as internet of things (loT), industrial control, autonomous driving, mission critical communications, etc. that may have ultra-low latency, ultra-high reliability, and high data capacity

5 requirements due to safety and performance concerns. Edge computing as a feature has been added in the 5G core (5GC) system architecture to support such services by hosting some applications closer in the local data network in order to reduce the end-to-end latency and the load on the transport network. FIG. 3 illustrates a 5G edge computing network in accordance with some embodiments.

10 [0060] FIG. 4 illustrates P2P edge computing management deployment in accordance with some embodiments. In the deployment shown in FIG. 4, edge computing in 3GPP networks involves communication among a 3GPP management system, a non-3GPP management system, including an edge computing management system, and ETSI network function virtualization

15 (NFV) management and orchestration (MANO).

[0061] The deployment of edge computing in 3GPP networks uses cooperation with other Standards Development Organizations (SDOs), as the application function (AF) and application server (AS) are not 3 GPP defined nodes. The deployment of network functions in 3GPP networks and non-3GPP

20 networks to support edge computing involves communication between 3 GPP management system and non-3GPP management systems.

[0062] In the example of FIG. 4, the 3 GPP management system can initiate the edge computing deployment by requesting the edge computing management system to deploy the local data network, and the Network

25 Functions Virtualization Orchestrator (NFVO) to connect the UPF and local data network with the quality of service (QoS) for N6 requirements for the connection (e.g., a virtual link) between the UPF and local data network. The edge computing management system can initiate the edge computing deployment by requesting the 3 GPP management system to deploy the UPF and

30 NFVO to connect the UPF and local data network with the QoS requirements for the connection between UPF and local data network.

[0063] FIG. 5 shows an architecture to enable the deployment of edge applications. In the architecture, the Application Client is an application resident

19 in a UE performing client function(s), and the Edge Application Server (EAS) is an application server resident in the Edge Data Network that is the local data network, performing server functions. The Application Client connects to the Edge Application Server to avail itself of (or obtain) the services of the

5 application with the benefits of Edge Computing.

[0064] FIG. 5 shows an application architecture for enabling Edge Applications. The Edge Data Network is a local Data Network. Edge Application Servers) and the Edge Enabler Server (EES) are contained within the EDN. The Edge Configuration Server (ECS) provides configurations related

10 to the EES, including details of the Edge Data Network hosting the EES. The UE contains Application Client(s) and the Edge Enabler Client. The Edge Application Servers), the Edge Enabler Server, and the Edge Configuration Server may interact with the 3 GPP Core Network.

[0065] The interactions related to enabling Edge Computing, between

15 the Edge Enabler Server and the Edge Enabler Client are supported by the EDGE-1 reference point. The EDGE-1 reference point supports: Registration and de-registration of the Edge Enabler Client to the Edge Enabler Server; Retrieval and provisioning of configuration information for the UE; and Discovery of Edge Application Servers available in the Edge Data Network.

20 [0066] The interactions related to Edge Enabler Layer, between the Edge Enabler Server and the 3GPP Network are supported by the EDGE-2 reference point. The EDGE-2 reference point supports: Access to 3GPP Network functions and Application Programming Interfaces (APIs) for retrieval of network capability information, e.g., via Service Capability Exposure Function

25 (SCEF) and Network Exposure Function (NEF) APIs, and with the EES acting as a trusted AF in the 5GC. The EDGE-2 reference point reuses SA2 defined 3GPP reference points, N33, or the interfaces of EPS or 5GS considering different deployment models.

[0067] The interactions related to the Edge Enabler Layer, between the

30 Edge Enabler Server and the Edge Application Servers are supported by the EDGE-3 reference point. The EDGE-3 reference point supports: Registration of Edge Application Servers with availability information (e.g., time constraints, location constraints); De-registration of Edge Application Servers from the Edge

20 Enabler Server; and Providing access to network capability information (e.g., location information). The following cardinality rules apply for EDGE-3 (Between EAS and EES): a) One EAS may communicate with only one EES; b) One EES may communicate with one or more EAS(s) concurrently.

5 [0068] The interactions related to the Edge Enabler Layer, between the Edge Data Network Configuration Server and the Edge Enabler Client are supported by the EDGE-4 reference point. The EDGE-4 reference point supports: Provisioning of Edge Data Network configuration information to the Edge Enabler Client in the UE.

10 [0069] The interactions between the Application Client(s) and the Edge Enabler 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; Notifications about events related to the connection between Application Clients and their

15 corresponding Edge Application Servers, such as: when an Application Client needs to reconnect to a different 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 Provide the identity of the desired Edge Application Server to the Edge Enabler

20 Client to enable it to use that identity as a filter when requesting information about Edge Application Servers.

[0070] The interactions related to the Edge Enabler Layer, between the Edge Data Network Configuration Server and the Edge Enabler Server are supported by the EDGE-6 reference point. The EDGE-6 reference point

25 supports: Registration of Edge Enabler Server information to the Edge Enabler Network Configuration Server.

[0071] The interactions related to the Edge Enabler Layer, between the Edge Enabler Server and the 3GPP Network are supported by the EDGE-2 (or EDGE-7) reference point. The EDGE-7reference point supports: Access to

30 3GPP Network functions and APIs for retrieval of network capability information, e.g., via SCEF and NEF APIs, and with the EAS acting as a trusted AF in the 5GC. The EDGE-7 reference point reuses SA2 defined 3GPP

21 reference points, N6, or interfaces of the EPS or 5GS considering different deployment models.

[0072] The interactions between the Edge Data Network Configuration

Server and the 3 GPP Network are supported by the EDGE-8 reference point.

5 The EDGE-8 reference point supports: Edge Data Network configurations provisioning to the 3GPP network utilizing network exposure services.

[0073] The EDGE-9 reference point enables interactions between two Edge Enabler Servers. The EDGE-9 reference point may be provided between the EES within different EDNs and within the same EDN.

10 [0074] The Edge Enabler Server (EES) provides supporting functions for Edge Application Servers and the Edge Enabler Client. Functionalities of the Edge Enabler Server are: a) provisioning of configuration information to the Edge Enabler Client, enabling exchange of application data traffic with the Edge Application Server; b) supporting the functionalities of the API invoker and API

15 exposing function; c) interacting with the 3 GPP Core Network for accessing the capabilities of network functions either directly (e.g., via PCF) or indirectly (e.g., via SCEF/NEF/SCEF+NEF); and d) support the functionalities of application context transfer.

[0075] The following cardinality rules apply for the Edge Enabler

20 Server: a) One or more EES(s) may be located in an EDN; b) One or more EES(s) may be located in an EDN per Edge Computing Service Provider (ECSP).

[0076] The EAS is the application server resident in the Edge Data Network, performing the server functions. The Application Client connects to

25 the Edge Application Server in order to take advantage of the services of the application with the benefits of Edge Computing. It is possible that the server functions of an application are available only as the Edge Application Server. However, if the server functions of the application are available as both an Edge Application Server and an Application Server resident in the cloud, it is possible

30 that the functions of the Edge Application Server and the Application Server are not 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.

22 [0077] The Edge Application Server may consume the 3 GPP Core

Network capabilities in different ways, such as: a) it may invoke 3GPP Core Network function APIs directly, if it is an entity trusted by the 3GPP Core Network; b) it may invoke 3GPP Core Network capabilities through the Edge

5 Enabler Server; and c) it may invoke the 3GPP Core Network capability through the capability exposure functions (e.g., SCEF or NEF).

[0078] The following cardinality rules apply for Edge Application Servers: a) One or more EAS(s) may be located in an EDN. The EAS(s) belonging to the same EAS ID can be provided by multiple ECSP(s) in an EDN.

10 [0079] The Edge Enabler Server ID (EESID) is the Fully Qualified Domain Name (FQDN) of the Edge Enabler Server and each Edge Enabler Server ID is unique within a PLMN domain.

[0080] The Edge Application Server ID (EASID) identifies a particular application for e.g., SA6Video, SA6Game etc. For example, all Edge SA6Video

15 Servers share the same Edge Application Server ID. The format for the EAS ID is out of scope of this specification. Table 1 shows Edge Application Server Profile IBs.

Table 1: EAS Profile

Information Status Description element

EAS ID M The identifier of the EAS _

EAS Endpoint M Endpoint information (e.g., URI, FQDN, IP address) used to communicate with the EAS. This information maybe discovered by EEC and exposed to Application Clients so that application clients can establish contact with the EAS. _

Application o Identifies the Application Client(s) that can be Client ID(s) served by the E AS _

EAS Provider O The identifier of the EAS Provider Identifier

EAS Type o The category or type of EAS (e.g., V2X)

EAS description o Human-readable description of the E AS

EAS Schedule o The availability schedule of the EAS (e.g., time windows)

EAS Service O The geographical service area that the EAS serves Area _

EAS Service O Service characteristics provided by EAS, detailed KPIs in Table 8.2.5-1 _ Service o Indicates if the EAS supports service continuity or continuity not. support

23 EAS O The availability reporting period (e.g., heart beat Availability period) that indicates to the EES how often it Reporting needs to check the EAS's availability after a Period successful registration. _

EAS Required O A list of the Service APIs that are required by the Service APIs EAS _

EAS Status o The status of the EAS (e.g., enabled, disabled, etc.)

[0081] Edge Application Server Service key performance indicators (KPIs) provide information about service characteristics provided by the Edge Application Server (see e.g., Table 2).

5 Table 2: EAS Service KPIs _

Information element Status _ Description _

Maximum Request rate O Maximum request rate from the Application Client supported by the server. _

Maximum Response O The maximum response time time advertised for the Application Client's service requests. _

Availability o Advertised percentage of time the server is available for the Application Client's use. _

Available Compute O The maximum compute resource available for the Application Client.

Available Graphical O The maximum graphical compute Compute resource available for the Application Client. _

Available Memory O The maximum memory resource available for the Application Client.

Available Storage o The maximum storage resource available for the Application Client.

Connection Bandwidth o The connection bandwidth in Kbit/s advertised for the Application Client's use. _

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 required by the server to consume 3 GPP Core Network capabilities, if any.

[0082] The Edge Enabler Server profile includes information about the EES and the services it provides (see e.g., Table 3). io Table 3: EES Profile _

Information Status Description element

24 EES ID M The 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 to connect to the EES.

Edge M List of Edge Application Servers registered with Application the EES. Server Profiles

EES Provider O The identifier of the EES Provider (such as ECSP) Identifier

[0083] The network capability exposure to 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:

5 Direct network capability exposure and/or Network capability exposure via Edge Enabler Server.

[0084] In some implementations, the network capability exposure to EAS(s) depends on the deployment scenarios and the business relationship of the ASP/ECSP with the PLMN operator. The following mechanisms are supported:

10 Direct network capability exposure and/or Network capability exposure via Edge Enabler Server. In some implementations, the charging functionalities with different deployment options depending on business relationships among Edge Application Service Provider, Edge Computing Service Provider, and SFC service provider are out of scope of the present disclosure (SAS study).

15 [0085] FIG. 6 illustrates an inter-EDN in accordance with some embodiments. FIG. 7 illustrates an intra-EDN in accordance with some embodiments. The EDGE-9 reference point enables interactions between two Edge Enabler Servers. The EDGE-9 reference point may be provided between EES within different EDNs as shown by Figure E3 and within the same EDN as

20 shown by FIG. 7.

[0086] FIG. 8 illustrates service provider relationship in an edge computing network deployment in accordance with some embodiments. FIG. 8 shows the roles and relationship of service providers involved in the deployment of edge computing services. The application service provider (ASP) is

25 responsible for the creation of EAS and application clients (AC). The ECSP is responsible for the deployment of EDNs that contain the E AS and EES that provides the configuration information to the EEC, enabling the AC to exchange

25 application data traffic with the EAS. The PLMN operator is responsible for the deployment of 5G network functions, such as the 5GC and 5G NR.

[0087] The end user is the consumer of the applications/services provided by the ASP and can have an ASP service agreement with a single

5 application service provider or multiple application service providers. The end user has a PLMN subscription arrangement with the PLMN operator. The UE used by the end user is allowed to be registered on the PLMN operator network. The ASP consumes the edge services (e.g., infrastructure, platform, etc.) provided by the ECSP and can have an ECSP service agreements) with a single

10 ECSP or multiple ECSPs. The ECSP may be a mobile network operator or a 3rd party service provider offering Edge Computing services. A single PLMN operator can have the PLMN operator service agreement with a single computing service provider or multiple edge computing service providers. A single ECSP can have PLMN operator service agreement with a single PLMN

15 operator or multiple PLMN operators that provide edge computing support. The ECSP and the PLMN operator can be part of the same organization or different organizations.

[0088] As above, the 3GPP management system manages the 3GPP defined network functions (e.g., UPF, PCF, EES, ECS, EAS, ...), and services.

20 To support the edge computing management, the 3GPP management system includes both a PLMN management system that is responsible for the orchestration and management of the mobile networks and an ECSP management system that is responsible for the orchestration and management of the EDN. The ECSP and the PLMN operator can be part of the same

25 organization. The services include performance assurance of the different edge computing network functions, as well as collection of various types of measurements (including EAS measurements, for example) for performance assurance. Use cases and requirements for EAS performance assurance are presented herein, as are measurement collection via performance job control, and

30 measurement collection via configurable measurement control.

[0089] 6.2.x EAS performance assurance

[0090] 6.2.x.1 Goal

26 [0091] The goal is to enable a consumer, such as an Application Service Provider (ASP) (or Management Service Consumer (MnS-C)), to collect EAS KPI or performance measurement to meet the requirement [AR-5.2.10-2-a] (see subclause 5.2.10.2 in TS 23.558).

5 [0092] 6.2.X.2 Description

[0093] A consumer requests the 3 GPP management system to collect EAS measurements, such as available resources (e.g., available compute, available memory, available storage), and connection bandwidth on the network interfaces (see subclause 8.2.5 in TS 23.558 and Table 2, above).

10 [0094] The 3 GPP management system collects and reports the EAS measurements to the consumer.

[0095] 6.2.X.3 Requirements

[0096] REQ-EAS-PA-FUN-1 The 3GPP management service producer should have the capability allowing an authorized consumer to request the

15 collection of EAS measurements, such as available resources (e.g., available compute, available memory, available storage), and connection bandwidth on the network interfaces.

[0097] REQ-EAS-PA-FUN-23 GPP management service producer should have the capability to report the EAS measurements to the consumer.

20

[0098] 7.x EAS performance assurance

[0099] 7.x.1 General

[00100] This subclause provides potential solutions for the use case of the EAS performance assurance (see subclause 6.2.x). It collects the EAS KPI or

25 performance measurements that are defined in Table 2 (see subclause 8.2.5 in TS 23.558). FIG. 9 illustrates a performance assurance MnS in accordance with some embodiments. In particular, FIG. 9 shows the performance assurance MnS used by a consumer, such as an ASP, to collect EAS measurements from the ECSP management system.

30 [00101] 7.x.2 Measurement collection via performance job control

[00102] The MnS-C at the ASP consumes the measurement job control MnS with createMeasurementiob operation (see TS 28.550) to request that a Management Service Producer (MnS-P) in the ECSP management system

27 collect the EAS measurements, such as available resources (e.g., available compute, available memory, available storage), and the connection bandwidth on the network interfaces (see subclause 8.2.5 in TS 23.558 and Table 2).

[00103] The createMeasurewientlob operation indicates a delivery

5 mechanism for the EAS measurements. That is, the createMeasurementJob operation indicates whether the EAS measurement data will be sent via a data file reporting service or data streaming service (see clause 7 in TS 28.550).

[00104] The ASP, as the consumer of the performance data file reporting

MnS, executes the following steps to receive the measurement data via the data

10 file reporting service: the ASP invokes the subscribe operation (see TS 28.532) to subscribe to receive notifications from the ECSP management system; the ASP receives a notification from the MnS producer indicating the performance data file is ready; and the ASP fetches the measurement data from the MnS producer.

15 [00105] The subscribe operation includes:

[00106] 11.6.1 Operations and notifications

[00107] 11.6.1.1 Notification notifyFileReady [00108] 11.6.1.1.1 Definition [00109] A MnS producer sends this notification to subscribed MnS

20 consumers when a new file becomes ready (available) on the MnS producer for upload by MnS consumers. The "filelnfoList" parameter provides information (meta data) about the new file and optionally, in addition to that, information about all other files, which became ready for upload earlier and are still available for upload when the notification is sent.

25 [00110] The "objectClass" and "objectinstance" parameters of the notification header identify the object representing the function (process) making the file available for retrieval, such as the "PerfMetricJob" or the "TraceJob" defined in TS 28.622. When no dedicated object is standardized or instantiated, the "ManagedElement", where the file is processed, shall be used. For the case

30 that the file is processed on a management node, the "ManagementNode", where the file is processed, shall be used instead.

[00111] 11.6.1.1.2 Input parameters

28 Parameter S Information Type Comment Name objectClass M Entity.objectClass See clause 11.6.1.1.1 for the definition of Entity objectinstance M Entity, objectinstance See clause 11.6.1.1.1 for the definition of Entity notificationld M notifi cati onTypejM "notifyFileReady" eventTime M Time when the file, that triggered this notification, was ready for upload. systemDN M

29 Parameter S Information Type Comment Name filelnfoList M List of struct Information (meta data) fileLocation (M), about the fileSize (O), new file, fileReadyTime (O), that became fileExpirationTime (O), ready for fileCompression (M), upload and fileFormat (M), triggered fileDataType (M), this notification, and

Each element is defined as following: information

- "fileLocation": Location of the file. The about files, location may be a directory path or a URL, for which example became

"\\202.112.101. l\D:\user\Files\<xxx>", or ready for

"ftp://nms.telecom_org.com/datastore/<xxx>, upload where <xxx> is the filename. earlier and

- "fileSize" : Size of the file. Its value is a non are still negative integer. The unit is byte. available

- "fileReadyTime": Date and time when the file for upload was closed (the last time) and made available when the on the MnS producer. The file content will not notification be changed anymore. is sent.

- "fileExpirationTime": Date and time after which the file may be deleted. It shall not be empty and shall be later than "fileReadyTime".

- "fileCompression": Name of the algorithm used for compressing the file. An empty or absent "fileCompression" parameter indicates the file is not compressed. The MnS producer selects the compression algorithm. It is encouraged to use popular algorithms such as GZIP.

- "fileFormat": Identifier of the XML or ASN.l schema (incl. its version) used to produce the file content.

- "fileDataType": Type of the management data stored in the file. Allowed values are:

- "PERFORMANCE"

- "TRACE"

- "ANALYTICS"

- "PROPRIETARY"

The value "PERFORMANCE" refers to measurements and KPIs.

30 Parameter S Information Type Comment Name additionalText O Allows a free form text description to be reported as defined in ITU-T Rec. X. 733 [4]

[00112] 11.6.1.3 Operation subscribe

[00113] 11.6.1.3.1 Definition

[00114] This operation allows a MnS consumer to subscribe to the

5 notifications of the file data reporting service producer.

[00115] 11.6.1.3.2 Input parameters

Parameter Name S Information Type Comment which the notifications shall be sent. timeTick producer. This value defines the time window within which the MnS consumer intends to invoke the "subscribe" operation again to confirm its subscription. The value "0" shall indicate infinity. In this case the subscription is not terminated by the MnS producer.

Unit is minutes filter use to filter notifications. The filter can be applied to all parameters of a notification

The filter constraint grammar is solution set dependent

[00116] 11.6.1.3.3 Output parameters

31 Parameter s Matching Information Comment Name subscription Unambiguous identity of this Id subscription. _ status ENUM (OperationSucceeded, If subscription is successfully OperationF ailedExistingSubscri created, status = ption, OperationFailed) OperationSuceeded .

If subscription is not created because it is duplicated or conflict with existing subscription(s), status = OperationFailedExistingSubscr iption

If the operation is failed for any other reason than being duplicated or conflict with existing subscription(s), status = OperationFailed.

[00117] 11.6.1.3.4 Exceptions

Name Definition operation failed existingj duplicated or conflict with existing subscription(s)

Returned Information: The output parameter status operation failed Condition: The operation failed for any other reason than being duplicated or conflict with subscription(s) Returned Information: The output parameter status

[00118] The ECSP management system, as the producer of performance

5 data streaming MnS, executes the following steps to send the measurements to ASP via the data streaming service (see Annex D in TS 28.550): the MnS producer invokes an establishStreamingConnection operation to establish a streaming connection with the ASP for sending the streaming data; and the MnS producer collects the measurement data and invokes a reportStreamData

10 operation to send the streaming data to the ASP. The ASP establishes the streaming connection with the MnS producer in response to invocation of the establishStreamingConnection operation by the MnS producer and receives the streaming data in response to invocation of the reportStreamData operation by the MnS producer.

15 [00119] From Annex D:

32 [00120] 11.. The consumer of MnS for measurement control requests the MnS producer to start the measurement collection by the following two alternatives:

[00121] 1) by the measurement job control service

5 [00122] la. The MnS consumer invokes the createMeasurementJob operation towards the MnS producer;

[00123] 2) by the configurable measurement control service (a.k.a., NRM fragment-based measurement control service).

[00124] lb. The MnS consumer creates a new PerjMetricJob

10 MOI, by invoking the createMOI operation towards the MnS producer; or [00125] 1c. The MnS consumer modifies an existing PerjMetricJob

MOI to add new measurements to be collected, by invoking the modijyMOIAttributes operation towards the MnS producer.

[00126] 22.. The producer of MnS for measurement control configures

15 the NF to collect the measurements. The mechanism of this step is vendor specific. If producer of MnS for measurement control is in the NF, this step can be skipped.

[00127] 33.. The NF triggers the producer of MnS for performance data streaming to set up the streaming information for the new measurements to

20 be collected. The mechanism of this step is vendor specific. If producer of MnS for performance data streaming is in the NF, this step can be skipped.

[00128] 4. The producer of MnS for performance data streaming communicates with the consumer to:

[00129] 4a. establish the streaming (WebSocket) connection containing

25 the stream information if it does not exist yet, by invoking the establishStreamingConnection operation;

[00130] 4b. add the stream information for the new measurements if they will be reported by new streams, by invoking the addStreamlnfo operation;

[00131] 4c. update the stream information for the new measurements if

30 they will be reported by existing streams, by invoking the updateStreamlnfo operation.

[00132] 55.. The NF collects the measurements. This step is the internal behaviour of the NF.

33 [00133] 66.. The NF report the collected measurements to the producer of MnS for performance data streaming. The mechanism of this step is vendor specific. If producer of MnS for performance data streaming is in the NF, this step can be skipped.

5 [00134] 7. The producer of MnS for performance data streaming sends the collected measurements to the consumer via performance data streams, by invoking the reportStreamData operation.

[00135] 7.x.3 Measurement collection via configurable measurement control

10 [00136] The MnS-C of the ASP consumes the provisioning MnS with createMOI operation to create a PerJMetricJob managed object instance (MOI) to request the MnS-P at the ECSP management system to collect EAS measurements, such as available resources (e.g., available compute, available memory, available storage), and connection bandwidth on the network interfaces

15 (see Annex D in TS 28.550 and Table 2).

[00137] The PerJMetricJob Information Object Class (IOC) indicates whether the EAS measurement data will be sent via a data file reporting service or data streaming service (See clause 4.3.31 in TS 28.622).

[00138] The ASP, as the consumer of performance data file reporting

20 MnS, executes the following steps to receive the measurement data via the data file reporting service: the ASP invokes the subscribe operation (see TS 28.532) to subscribe to receive notifications from the ECSP management system; the ASP receives a notification from the MnS producer indicating the performance data file is ready; and the ASP fetches the measurement data from the MnS

25 producer.

[00139] The ECSP management system, as the producer of performance data streaming MnS, executes the following steps to send the measurements to the ASP via the data streaming service (see Annex D in TS 28.550): the MnS producer invokes the establishStreamingConnection operation to establish a

30 streaming connection with the ASP for sending the streaming data; and the MnS producer collects the measurement data and invokes the reportStreamData operation to send the streaming data to the ASP. The ASP establishes the streaming connection with the MnS producer in response to invocation of the

34 establishStreamingConnection operation by the MnS producer and receives the streaming data in response to invocation of the reportStreamData operation by the MnS producer.

[00140] Thus, for example, an apparatus of a management system

5 contains processing circuitry configured to operate as the ASP or MnS-C of the ASP. The processing circuitry is configured to: consume the measurement job control MnS with createMeasurementlob operation or measurement job control MnS with createMOI operation provided by the MnS-P at the ECSP management system to create a measurement job to collect EAS measurements.

10 The measurement job decides that measurement data is to be sent via: a data file reporting service or data streaming service.

[00141] In either case, if the measurement data is sent via data file reporting service, then the ASP is configured to: invoke the subscribe operation to subscribe to receive notifications from the ECSP management system; and

15 receive a notification from the MnS producer indicating the performance data file is ready; and fetch the measurement data from the MnS producer at the ECSP management system.

[00142] Similarly, in either case, if the measurement data is sent via data streaming service, then the ECSP management system is configured to: invoke

20 the establishStreamingConnection operation to establish a streaming connection with the MnS-C at the ASP for sending the streaming data, and collect the measurement data and invoke the reportStreamData operation to send the streaming data to the MnS-C at the ASP.

[00143] The createMOI operation is to create the PerJMetricJob MOI that

25 defines the measurement job to collect the EAS measurements.

[00144] The EAS measurements include available resources (available compute, memory, and storage) measurements and connection bandwidth measurements.

[00145] The EC SP management system creates measurement jobs via the

30 measurement job control MnS with createMeasurementlob operation or the provisioning MnS with createMOI operation. Upon the creation of a measurement job, the ECSP management system is configured to collect the

35 measurements according to the measurement job definition and report the measurement data.

[00146] The MnS-C thus consumes or uses the management services produced by the MnS-P. Each management service consists of various

5 operations. For example, the management services for a provisioning MnS are shown below:

MnS Component Type A _ Note _

Operations and notifications defined in clause It is supported by Provisioning ll.l.lof TS 28.532: MnS for NF, as defined in

- createMOI operation 28.531.

- getMOIAttributes operation modifyMOIAttributes operation deleteMOI operation notifyMOIAttributeValueChanges operation

- notifyMOICreation

- notifyMOIDeletion notifyMOIChanges

Operations defined in clause 11.3.1.1.1 in TS It is supported by Performance 28.532 and clause 6.2.3 of TS 28.550: Assurance MnS for NF s, as

- notifyFileReady operation defined in 28.550.

- reportStreamData operation

[00147] Thus, a consumer consumes a management service (e.g., a

10 provisioning MnS) by invoking an operation (e.g., a createMOI operation). [00148] Although an embodiment has 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 present disclosure. Accordingly, the specification and drawings are

15 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

20 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, therefore, is not to be taken in a

36 limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00149] The subject matter may be referred to herein, individually and/or

5 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

10 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. [00150] In this document, the terms "a" or "an" are used, as is common in

15 patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English

20 equivalents of the respective 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 a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the

25 terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00151] The Abstract of the Disclosure is provided to comply 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

30 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. This method of disclosure is not to be

37 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

5 Detailed Description, with each claim standing on its own as a separate embodiment.

38

Claims

CLAIMS What is claimed is:

1. An apparatus of an application service provider (ASP), the apparatus

5 comprising: processing circuitry configured to: encode, for transmission to a management service producer (MnS-P) at an Edge Computing Service Provider (ECSP) management system, a request to collect Edge Application Server

10 (EAS) service key performance indicators (KPIs) or performance measurements for an application client; and decode, from the MnS-P of the ECSP management system, EAS measurements for the EAS KPIs or performance measurements; and

15 memory configured to store the EAS measurements.

2. The apparatus of claim 1, wherein the E AS measurements include available resources and connection bandwidth on network interfaces to the application client.

20

3. The apparatus of claim 2, wherein the available resources comprise: maximum compute resources available for the application client, maximum memory resources available for the application client, and maximum storage resources available for the application client.

25

4. The apparatus of claim 1, wherein a management service consumer (MnS-C) of the ASP is configured to consume a measurement job control Management Service (MnS) with createMeasuremenUob operation to request that the ECSP management system collect the EAS measurements.

30

5. The apparatus of claim 4, wherein the createMeasuremenUob operation indicates a delivery mechanism for the EAS measurements, the delivery mechanism selected from a set of services that include a data file reporting service and a data streaming service.

39

6. The apparatus of claim 5, wherein in response to the createMeasurementJob operation indicating that the delivery mechanism includes the data file reporting service, the processing circuitry is further

5 configured to: invoke a subscribe operation to subscribe to receive notifications from the ECSP management system; decode, from the MnS-P, a notification indicating a performance data file that contains the EAS measurements is ready; and

10 in response to reception of the notification, fetch from the MnS-P the performance data file that contains the EAS measurements.

7. The apparatus of claim 5, wherein in response to the createMeasurementJob operation indicating that the delivery mechanism

15 includes the data streaming service, the processing circuitry is further configured to: establish a streaming connection between the MnS-C and MnS-P in response to invocation of an estabtishStreamingConnection operation by the MnS producer; and

20 decode, at the MnS-C, streaming data that contains the EAS measurements in response to invocation of a reportStreamData operation by the MnS-P.

8. The apparatus of claim 4, wherein:

25 the EAS measurements include available resources and connection bandwidth on network interfaces to the application client, and the available resources comprise maximum compute resources available for the application client, maximum memory resources available for the application client, and maximum storage resources available for the application

30 client.

9. The apparatus of claim 1, wherein a management service consumer (MnS-C) of the ASP is configured to consume a provisioning Management

40 Service (MnS) with createMOI operation to create a PerfMetricJob managed object instance (MOI) of an PerfMetricJob Information Object Class (IOC) to request that the ECSP management system collect the EAS measurements.

5 10. The apparatus of claim 9, wherein the PerfMetricJob IOC indicates a delivery mechanism for the EAS measurements, the delivery mechanism selected from a set of services that include a data file reporting service and a data streaming service.

10 11. The apparatus of claim 10, wherein in response to the PerfMetricJob IOC indicating that the delivery mechanism includes the data file reporting service, the processing circuitry is further configured to: invoke a subscribe operation to subscribe to receive notifications from the ECSP management system;

15 decode, from the MnS-P, a notification indicating a performance data file that contains the EAS measurements is ready; and in response to reception of the notification, fetch from the MnS-P the performance data file that contains the EAS measurements.

20 12. The apparatus of claim 10, wherein in response to the PerfMetricJob IOC indicating that the delivery mechanism includes the data streaming service, the processing circuitry is further configured to: establish a streaming connection between the MnS-C and MnS-P in response to invocation of an establishStreamingConnection operation by the

25 MnS producer; and decode, at the MnS-C, streaming data that contains the EAS measurements in response to invocation of a reportStreamData operation by the MnS-P.

30 13. The apparatus of claim 9, wherein: the EAS measurements include available resources and connection bandwidth on network interfaces to the application client, and

41 the available resources comprise maximum compute resources available for the application client, maximum memoiy resources available for the application client, and maximum storage resources available for the application client.

5

14. The apparatus of claim 1, wherein measurement jobs to obtain the EAS measurements are created via at least one of: a measurement job control Management Service (MnS) with createMeasurementJob operation, or a provisioning MnS with createMOI operation.

10

15. An apparatus of a Third Generation Partnership Project (3 GPP) management system, the apparatus comprising: processing circuitry configured to: decode, from an application service provider (ASP), a request to

15 collect Edge Application Server (EAS) service key performance indicators (KPIs) or performance measurements for an application client; in response to reception of the request, collect E AS measurements for the EAS KPIs or performance measurements; and

20 encode, for transmission to the ASP, a report that contains the EAS measurements; and memoiy configured to store the EAS measurements.

16. The apparatus of claim 15, wherein the EAS measurements include

25 available resources and connection bandwidth on network interfaces to the application client.

17. The apparatus of claim 16, wherein the available resources comprise: maximum compute resources available for the application client,

30 maximum memory resources available for the application client, and maximum storage resources available for the application client.

42

18. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of an application service provider (ASP), the one or more processors to configure the ASP to, when the instructions are executed:

5 encode, for transmission to a management service producer (MnS-P) at an Edge Computing Service Provider (ECSP) management system, a request to collect Edge Application Server (EAS) service key performance indicators (KPIs) or performance measurements for an application client, measurement jobs to obtain the EAS measurements created via at least one of: a measurement

10 job control Management Service (MnS) with createMeasurementJob operation or a provisioning MnS with createMOI operation; decode, from the MnS-P of the ECSP management system EAS measurements for the EAS KPIs or performance measurements.

15 19. The non-transitory computer-readable storage medium of claim 18, wherein: the EAS measurements include available resources and connection bandwidth on network interfaces to the application client, and the available resources comprising maximum compute resources

20 available for the application client, maximum memory resources available for the application client, and maximum storage resources available for the application client.

20. The non-transitory computer-readable storage medium of claim 18,

25 wherein: a delivery mechanism for the EAS measurements includes at least one of a data file reporting service or a data streaming service, for the data file reporting service, the one or more processors to configure the ASP to:

30 invoke a subscribe operation to subscribe to receive notifications from the ECSP management system; decode, from the MnS-P, a notification indicating a performance data file that contains the EAS measurements is ready; and

43 in response to reception of the notification, fetch from the MnS-P the performance data file that contains the EAS measurements, and for the data streaming service, the one or more processors to configure the ASP to:

5 establish a streaming connection between a management service consumer (MnS-C) of the ASP and MnS-P in response to invocation of an establishStreamingConnection operation by the MnS producer, and decode, at the MnS-C, streaming data that contains the EAS measurements in response to invocation of a reportStreamData operation

10 by the MnS-P.

44