WO2022232132A1 - Charging for obtaining ue location, acr management event and ac information notification - Google Patents

Abstract

An apparatus and system are described to charging for edge computing functions related to 5GC network services. An Edge Enabler Server (EES) generates charging data related to an event, sends a charging data request to a charging function to process the charging data for Charging Data Record (CDR) generation and receive a charging data response in response to the charging data request indicating creation of a CDR. The event is based on a message from a edge computing or network function related to services provided to an Edge Application Server (EAS) for a UE. The message is a UE location request or UE location/ Application Context Relocation (ACR) management event/ Application Client (AC) information subscribe request from the EAS, a request from the 5GC to report UE location or an ACR event of the UE, or a request for AC updates from an edge enabler client (EEC).

Description

CHARGING FOR OBTAINING UE LOCATION, ACR MANAGEMENT EVENT AND AC INFORMATION NOTIFICATION

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States

Provisional Patent Application Serial No. 63/180,442, filed April 27, 2021, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to next generation wireless communications. In particular, some embodiments relate to charging in edge computing and 5^th generation (5G) networks.

BACKGROUND

[0003] The use and complexity of wireless systems, which include 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 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 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 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.

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

[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 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.

[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 Immediate Event Charging (IEC) charging for a one-time UE location request in accordance with some embodiments.

[0016] FIG. 10 illustrates Post Event Charging (PEC) charging for a one time UE location request in accordance with some embodiments. [0017] FIG. 11 illustrates IEC charging for UE location subscription in accordance with some embodiments.

[0018] FIG. 12 illustrates PEC charging for UE location subscription in accordance with some embodiments.

[0019] FIG. 13 illustrates PEC charging for UE location notification in accordance with some embodiments.

[0020] FIG. 14 illustrates Application Context Relocation (ACR) management event subscription charging in accordance with some embodiments. [0021] FIG. 15 illustrates PEC ACR management event subscription charging in accordance with some embodiments.

[0022] FIG. 16 illustrates PEC ACR management event notification charging in accordance with some embodiments. [0023] FIG. 17 illustrates IEC Application Client (AC) information subscription charging in accordance with some embodiments.

[0024] FIG. 18 illustrates PEC AC information subscription charging in accordance with some embodiments.

[0025] FIG. 19 illustrates PEC AC information notification charging in accordance with some embodiments.

DETAILED DESCRIPTION

[0026] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other 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.

[0027] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140 A includes 3 GPP 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 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.

[0028] The network 140 A is shown to include user equipment (UE) 101 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 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.

[0029] 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 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). 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.

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

Internet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short lived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An IoT 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) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep alive messages, status updates, etc.) to facilitate the connections of the IoT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0031] The UEs 101 and 102 may be configured to connect, e.g., 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), aNextGen RAN (NG RAN), or some other type of RAN.

[0032] The UEs 101 and 102 utilize connections 103 and 104, 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 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.

[0033] In an aspect, the UEs 101 and 102 may further directly exchange 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 (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0034] 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 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).

[0035] 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 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., 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. [0036] 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, 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 eNB, or another type of RAN node.

[0037] 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 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, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121

[0038] 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 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 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, location dependencies, etc.

[0039] 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 responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0040] 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 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 Internet, 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., 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 Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0041] 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 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 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. [0042] In some aspects, the communication network 140 A can be an IoT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5G R) and the unlicensed (5G R-U) spectrum. One of the current enablers of IoT 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 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.

[0043] 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 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. [0044] 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) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0045] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 can be in communication 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 unified data management (UDM)/home subscriber server (HSS) 146.

[0046] 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 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 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 other.

[0047] 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 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).

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

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. [0049] In some aspects, the 5G system architecture 140B 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 (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 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 170B, e.g. an IMS operated by a different network operator.

[0050] In some aspects, the UDM/HSS 146 can be coupled to an application server 184, 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.

[0051] 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 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), Nil (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 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. IB can also be used.

[0052] FIG. 1C illustrates a 5G system architecture 140C and a service- 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 service-based interfaces.

[0053] 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- 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 service- based interface exhibited by the UDM 146), Naf 158F (a service-based interface 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 service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0054] NR-V2X architectures may 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 for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0055] FIG. 2 illustrates a block diagram of a communication device in 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 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. 1 A-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 the receiving entity.

[0056] 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 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 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.

[0057] 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 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 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.

[0058] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an 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 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 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 communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0059] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is 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 more instructions 224. [0060] 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 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 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.

[0061] The instructions 224 may further be transmitted or received over 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 a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), 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 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, 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 phone jacks) or one or more antennas to connect to the transmission medium 226.

[0062] Note that the term “circuitry” as used herein refers to, is part of, 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 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 (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 circuitry.

[0063] The term “processor circuitry” or “processor” as used herein thus 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 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.

[0064] 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 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 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 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- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP 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 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. 19, etc ), 3 GPP 5G, 5G, 5G New Radio (5G R), 3 GPP 5G New Radio, 3 GPP 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 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 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 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), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy- phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. llad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 lp or IEEE 802.1 lbd and other) Vehi cl e-to- Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to- Vehicle (12 V) communication 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 lp based DSRC, including ITS-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 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 lbd based systems, etc.

[0065] Aspects described herein can be used in the context of any 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 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 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 lb/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 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 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 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 (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 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) 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 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.

[0066] Aspects described herein can also implement a hierarchical 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.

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

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

[0068] Some of the features in this document are defined for the network 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.

[0069] 5G networks extend beyond the traditional mobile broadband services to provide various new services such as internet of things (IoT), industrial control, autonomous driving, mission critical communications, etc. that may have ultra-low latency, ultra-high reliability, and high data capacity 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. [0070] FIG. 4 illustrates P2P edge computing management deployment in accordance with some embodiments. In the deployment shown in FIG. 4, edge computing in 3 GPP networks involves communication among a 3 GPP management system, a non-3GPP management system, including an edge computing management system, and ETSI network function virtualization (NFV) management and orchestration (MANO).

[0071] The deployment of edge computing in 3 GPP 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 3 GPP networks and non-3GPP networks to support edge computing involves communication between 3 GPP management system and non-3GPP management systems.

[0072] 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 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 NFVO to connect the UPF and local data network with the QoS requirements for the connection between UPF and local data network.

[0073] FIG. 5 shows an architecture to enable the deployment of edge applications. In the architecture, the Application Client is an application resident 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 application with the benefits of Edge Computing.

[0074] FIG. 5 shows an application architecture for enabling Edge

Applications. The Edge Data Network is a local Data Network. Edge Application Server(s) and the Edge Enabler Server (EES) are contained within 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 contains Application Client(s) and the Edge Enabler Client. The Edge Application Server(s), the Edge Enabler Server, and the Edge Configuration Server may interact with the 3 GPP Core Network.

[0075] The interactions related to enabling Edge Computing, between 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. [0076] The interactions related to Edge Enabler Layer, between the Edge

Enabler Server and the 3 GPP 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 (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.

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

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 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.

[0078] 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.

[0079] 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 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 Client to enable it to use that identity as a filter when requesting information about Edge Application Servers.

[0080] 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 supports: Registration of Edge Enabler Server information to the Edge Enabler Network Configuration Server.

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

Edge Enabler Server and the 3 GPP Network are supported by the EDGE-2 (or EDGE-7) reference point. The EDGE-7reference point supports: Access to 3 GPP 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 reference points, N6, or interfaces of the EPS or 5GS considering different deployment models.

[0082] The interactions between the Edge Data Network Configuration

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

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

[0083] 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.

[0084] 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 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.

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

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).

[0086] The EAS is the application server resident in the Edge Data

Network, performing the server functions. The Application Client connects to 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 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.

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

Network capabilities in different ways, such as: a) it may invoke 3 GPP Core Network function APIs directly, if it is an entity trusted by the 3GPP Core Network; b) it may invoke 3 GPP Core Network capabilities through the Edge Enabler Server; and c) it may invoke the 3 GPP Core Network capability through the capability exposure functions (e.g., SCEF or NEF).

[0088] 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. [0089] 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. [0090] The Edge Application Server ID (EASID) identifies a particular application for e.g., SA6 Video, SA6Game etc. For example, all Edge SA6 Video Servers share the same Edge Application Server ID. The format for the EAS ID is out of scope of this specification. Table E28.2.4-1 shows Edge Application Server Profile IEs.

[0091] Edge Application Server Service 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- : Edge Application Server Service KPIs

[0092] The Edge Enabler Server profile includes information about the

EES and the services it provides (see e.g., table E28.2.6-1). Table E28.2.6-1: Edge Enabler Server Profile

[0093] The network capability exposure to Edge Application Server(s) 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 exposure and/or Network capability exposure via Edge Enabler Server.

[0094] 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: 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 (SA5 study).

[0095] 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 shown by FIG. 7.

[0096] 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 responsible for the creation of EAS and application clients (AC). The ECSP is responsible for the deployment of EDNs that contain the EAS and EES that provides the configuration information to the edge enabler client (EEC), enabling the AC to exchange application data traffic with the EAS. The PLMN operator is responsible for the deployment of 5G network functions, such as the 5GC and 5GNR.

[0097] 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 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 agreement(s) with a single 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 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.

[0098] As above, the 3 GPP management system manages the 3 GPP defined network functions (e.g., UPF, PCF, EES, ECS, EAS, ...), and services. 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 organization.

[0099] The ECSP provides edge enabling services to the ASP to enable the EAS to be running in the EDN. Some edge enabling services may be provided by the ECSP or directly via 3GPP Core network capabilities. The edge enabling services include following EES capabilities exposed to the EAS as described in TS 23.558 (which is herein incorporated by reference in its entirety): EAS registration; EAS discovery; Support to Service Continuity; Obtaining LIE location; ACR management event subscription/ notification; Application Client information subscription/notification; Session with QoS. The UC and potential requirement on charging for obtaining UE location by the EAS from the EES, user plane path management event subscription/notification (under ACR management event subscription/ notification), and Application Client information subscription and notification have been captured in TR 28.815. Solutions for charging for services are described herein.

[00100] In particular, charging is specified for the usage of edge enabling infrastructure resources in the EDN of an ECSP to run the virtualized EAS (i.e., EAS is implemented as VNF) provided by an ASP. The charging for edge enabling infrastructure resources usage, is based on the MnS(s) for performance assurance of Edge Computing including following resources usage for EAS: mean virtual CPU usage; mean virtual memory usage; mean virtual disk usage; and data volumes. The time window during which the charging for edge enabling infrastructure resource usage is to be enabled, and the criteria (e.g., thresholds) for triggering the charging may be locally configured to the Charging Enablement Function (CEF) and may not be controlled by the charging function (CHF). The CHF Address(es) selection by the CEF is done during the EAS deployment process based on the following options: NRF based discovery and CEF locally provisioned charging characteristics. Once selected, these CHF Address(es) are used as long as the EAS is deployed in the EDN.

[00101] Charging information for edge enabling infrastructure resources usage charging is collected for each EAS by the CEF from the MnS, with the information identifying the EDN where the edge enabling infrastructure resources are allocated and the information indicating the collection period of the measurements related to the edge enabling infrastructure resources usage

[00102] Solutions on charging for obtaining UE location by EAS from

EES

[00103] One-time UE location request

[00104] FIG. 9 illustrates IEC charging for a one-time UE location request in accordance with some embodiments. As shown, at operation 1, a UE location request is transmitted from the EAS to the EES.

[00105] Operation lch-a) Charging Data Request [Event]: the EES generates charging data related to the UE location request and sends the charging data request for the charging function (CHF) to process the related charging data for Charging Data Record (CDR) generation purposes. Operation lch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation lch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request (which, as other results of the requests described herein, may be stored in a memory associated with the EES).

[00106] At operation 2, the EES checks the UE location with the 3GPP network (see TS 23.558). In some embodiments, location information of the UE is obtained from an application programming interface (API) exposed by the 3GPP core network, e.g., SCEF/NEF/SCEF+NEF or LCS (Location Service).

At operation 3, the EES sends the LIE location response (see TS 23.558) to the EAS. The charging thus occurs prior to the event occurring.

[00107] FIG. 10 illustrates PEC charging for a one-time UE location request in accordance with some embodiments. As shown in FIG. 10, at operation 1, a UE location request is transmitted from the EAS to the EES. At operation 2, the EES checks the UE location with the 3 GPP network. At operation 3, the EES sends the UE location response to the EAS.

[00108] Operation 3ch-a) Charging Data Request [Event]: the EES generates charging data related to the UE location request and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation 3ch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation 3ch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request. The charging thus occurs after the event occurs.

[00109] FIG. 11 illustrates IEC charging for UE location subscription in accordance with some embodiments. At operation 1 in FIG. 11, the EAS sends the UE location subscribe request to the EES. Operation lch-a) Charging Data Request [Event]: the EES generates charging data related to the UE location subscription request and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation lch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation lch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request.

[00110] At operation 2, the EES subscribes to the UE location from the 3GPP Core Network. At operation 3, the EES may subscribe to UE expected behavior analytics (UE mobility) from the 3 GPP Core Network. At operation 4, the EES sends the UE location subscribe response to the EAS.

[00111] FIG. 12 illustrates PEC charging for UE location subscription in accordance with some embodiments. At operation 1 in FIG. 12, the EAS sends the UE location subscribe request to the EES. At operation 2, the EES subscribes to the UE location from the 3GPP Core Network. At operation 3, the EES may subscribe to UE expected behavior analytics (UE mobility) from the 3GPP Core Network. At operation 4, the EES sends the UE location subscribe response to the EAS. Operation 4ch-a) Charging Data Request [Event]: the EES generates charging data related to the UE location subscription and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation 4ch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation 4ch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request.

[00112] FIG. 13 illustrates PEC charging for UE location notification in accordance with some embodiments. At operation 1 in FIG. 13, the EES detects the UE location. At operation 2, the EES sends the UE location notification to the EAS. Operation 2ch-a) Charging Data Request [Event]: the EES generates charging data related to the UE location notification and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation 2ch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation 2ch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request.

[00113] Solutions on charging for ACR management events subscription and notification

[00114] FIG. 14 illustrates Application Context Relocation (ACR) management event subscription charging in accordance with some embodiments. At operation 1, the EAS sends an ACR management event subscribe request to the EES. Operation lch-a) Charging Data Request [Event]: the EES generates charging data related to the ACR management event subscribe request and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation lch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation lch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request. At operation 2, the EES checks the user plane path management event of the requesting UE with the 3 GPP Core Network. At operation 3, the EES may subscribe to UE expected behavior analytics (UE mobility) from the 3 GPP Core Network. At operation 4, the EES sends the UE ACR management event subscribe response to the EAS.

[00115] FIG. 15 illustrates PEC ACR management event subscription charging in accordance with some embodiments. At operation 1, the EAS sends an ACR management event subscribe request to the EES. At operation 2, the EES checks the user plane path management event of the requesting UE with the 3GPP Core Network. At operation 3, the EES may subscribe to UE expected behavior analytics (UE mobility) from the 3 GPP Core Network. At operation 4, the EES sends the UE ACR management event subscribe response to the EAS. Operation 4ch-a) Charging Data Request [Event]: the EES generates charging data related to an ACR management event subscribe request and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation 4ch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation 4ch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request.

[00116] FIG. 16 illustrates PEC ACR management event notification charging in accordance with some embodiments. At operation 1, the EES detects the ACR event of the UE. At operation 2, the EES sends the ACR management event notification to the EAS. Operation 2ch-a) Charging Data Request [Event]: the EES generates charging data related to an ACR management event notification and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation 2ch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation 2ch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request. At operation 3, the EAS may send an acknowledgement for the ACR management event notification to the EES.

[00117] Solutions on charging for Application Client information subscription and notification

[00118] FIG. 17 illustrates IEC AC information subscription charging in accordance with some embodiments. At operation 1, the EAS sends an AC information subscription request to the EES. Operation lch-a) Charging Data Request [Event]: the EES generates charging data related to the AC information subscription request and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation lch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation lch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request. At operation 2, the EES processes the request. At operation 3, the EES sends the AC information subscription response to the EAS.

[00119] FIG. 18 illustrates PEC AC information subscription charging in accordance with some embodiments. At operation 1, the EAS sends an AC information subscription request to the EES. At operation 2, the EES processes the request. At operation 3, the EES sends the AC information subscription response to the EAS. Operation 3ch-a) Charging Data Request [Event]: the EES generates charging data related to the AC information subscription request and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation 3ch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation 3ch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request.

[00120] FIG. 19 illustrates PEC AC information notification charging in accordance with some embodiments. At operation 1, the EEC triggers for AC updates with EES. At operation 2, the EES sends the AC information notification to the EAS. Operation 2ch-a) Charging Data Request [Event]: the EES generates charging data related to the AC information notification and sends the charging data request for the CHF to process the related charging data for CDR generation purposes. Operation 2ch-b) Create CDR: the CHF stores received information and creates a CDR related to the event. Operation 2ch-c) is a Charging Data Response [Event]: The CHF informs the EES of the result of the request.

[00121] 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 to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is 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 range of equivalents to which such claims are entitled.

[00122] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [00123] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other 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 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 terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00124] 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 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 interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus of a management system, the apparatus comprising: processing circuitry configured to operate as an Edge Enabler Server

(EES) to: generate charging data related to an event; encode, for transmission to a charging function (CHF), a charging data request to process the charging data for Charging Data Record (CDR) generation; and decode, from the CHF, a charging data response in response to the charging data request, the charging data response indicating creation of a CDR related to the charging data request; and memory configured to store the charging data response.

2. The apparatus of claim 1, wherein the processing circuitry is further configured to use Immediate Event Charging (IEC), in which the charging data request is sent to the CHF prior to responding to the event.

3. The apparatus of claim 1, wherein the processing circuitry is further configured to use Post Event Charging (PEC), in which the charging data request is sent to the CHF after responding to the event.

4. The apparatus of claim 1, wherein: the event is obtaining a user equipment (UE) location, and the processing circuitry is further configured to: decode, from an Edge Application Server (EAS), a UE location request, obtain, in response to reception of the UE location request, the UE location from a Third Generation Partnership Project (3 GPP) network, and encode, for transmission to the EAS, a UE location response that contains the UE location.

5. The apparatus of claim 1, wherein: the event is a user equipment (UE) location subscription, and the processing circuitry is further configured to: decode, from an Edge Application Server (EAS), a EE location subscribe request, subscribe, in response to reception of the EE location subscribe request, to a EE location from a Third Generation Partnership Project (3 GPP) core network, and encode, for transmission to the EAS, a EE location subscribe response that indicates subscription to the EE location.

6. The apparatus of claim 5, wherein the processing circuitry is further configured to subscribe, in response to reception of the EE location subscribe request, to EE expected behavior analysis from the 3GPP core network prior to transmission of the EE location subscribe response.

7. The apparatus of claim 1, wherein: the event is a user equipment (EE) location notification, and the processing circuitry is further configured to: detect a EE location, and encode, for transmission to an Edge Application Server (EAS) in response to detection of the EE location, the EE location notification via an application programming interface (API).

8. The apparatus of claim 1, wherein: the event is an Application Context Relocation (ACR) management event subscription, and the processing circuitry is further configured to: decode, from an Edge Application Server (EAS), an ACR management event subscribe request for a requesting user equipment (UE), determine, in response to reception of the ACR management event subscribe request, a user plane path management event of the requesting UE from a Third Generation Partnership Project (3 GPP) core network, and encode, for transmission to the EAS, an ACR management event subscribe response that indicates subscription to an ACR management event.

9. The apparatus of claim 8, wherein the processing circuitry is further configured to subscribe, in response to reception of the ACR management event subscribe request, to EE expected behavior analysis from the 3GPP core network prior to transmission of the ACR management event subscribe response.

10. The apparatus of claim 1, wherein: the event is an Application Context Relocation (ACR) event, and the processing circuitry is further configured to: detect an ACR event of a user equipment (EE), and encode, for transmission to an Edge Application Server (EAS) in response to detection of the ACR event, an ACR management event notification.

11. The apparatus of claim 10, wherein the processing circuitry is further configured to decode, from the EAS, an acknowledgement in response to the ACR management event notification.

12. The apparatus of claim 1, wherein: the event is an Application Client (AC) information subscription, and the processing circuitry is further configured to: decode, from an Edge Application Server (EAS), an AC information subscription request, process the AC information subscription request, and encode, for transmission to the EAS, an AC information subscription response.

13. The apparatus of claim 1, wherein: the event is an Application Client (AC) update, and the processing circuitry is further configured to: trigger an AC update, and encode, for transmission to an Edge Application Server (EAS), an AC information notification that contains the AC update.

14. An apparatus of an Edge Enabler Server (EES), the apparatus comprising: processing circuitry configured to: decode, from a network function, a message related to services provided to an Edge Application Server (EAS) for a user equipment (UE); trigger charging for the message; encode, for transmission to a charging function (CHF), a charging data request to report usage of infrastructure resources of the services; decode, from the CHF in response to the charging data request, a charging data response; and encode, for transmission to the network function, a charging data response in response to the charging data request; and memory configured to store the charging data response.

15. The apparatus of claim 14, wherein the processing circuitry is further configured to encode the charging data request for transmission prior to transmission of the charging data response.

16. The apparatus of claim 14, wherein the processing circuitry is further configured to encode the charging data request for transmission after transmission of the charging data response.

17. The apparatus of claim 14, wherein the message is one of: a UE location request from the EAS, a UE location subscribe request from the EAS, a request from a Third Generation Partnership Project (3 GPP) core network to report UE location, an Application Context Relocation (ACR) management event subscribe request from the EAS, a request from the 3 GPP core network to report an ACR event of the UE, an Application Client (AC) information subscription request from the EAS, or a request for AC updates from an edge enabler client (EEC).

18. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of an Edge Enabler Server (EES), the one or more processors to configure the EES to, when the instructions are executed: generate charging data related to an event; encode, for transmission to a charging function (CHF) as part of one of a Post Event Charging (PEC) or Immediate Event Charging (IEC) process, a charging data request to process the charging data for Charging Data Record (CDR) generation; and decode, from the CHF, a charging data response in response to the charging data request, the charging data response indicating creation of a CDR related to the charging data request.

19. The non-transitory computer-readable storage medium of claim 18, wherein the event is dependent on a message from a network function related to services provided to an Edge Application Server (EAS) for a user equipment (UE).

20. The non-transitory computer-readable storage medium of claim 19, wherein the message is one of: a UE location request from the EAS, a UE location subscribe request from the EAS, a request from a Third Generation Partnership Project (3 GPP) core network to report UE location, an Application Context Relocation (ACR) management event subscribe request from the EAS, a request from the 3 GPP core network to report an ACR event of the UE, an Application Client (AC) information subscription request from the EAS, or a request for AC updates from an edge enabler client (EEC).