Policy and charging control for computing power networks

Abstract

Aspects of the present disclosure relate to devices and methods for policy and charging control for computing power networks. In one aspect, a first device receives a first request for a policy for management of a computing service from a second device or a third device. The first device generates a policy for management of the computing service based at least on subscription information related to a consumer of the computing service. In turn, the first device sends a policy for management of the computing service to the second device or the third device.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to apparatus and methods for policy and charging control for computing power networks. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] In the future evolution towards 6G networks, 6G networks are envisioned as computing power networks. In this computing power network, the computing capabilities of 6G networks (including the radio access network (RAN), core network (CN), mobile edge computing (MEC), or cloud computing capabilities supported by 6G networks) are expected to be open to support the computing tasks of third-party applications, which is also known as compute-as-a-service. Summary of the Invention

[0004] This disclosure relates to apparatus and methods for policy and charging control for computing power networks. These apparatus and methods can generate policies for the management of computing services by taking into account subscription information related to consumers of the computing services. The NF providing the computing services can ensure that the computing services are provided in accordance with the policies.

[0005] Some implementations of a first device described herein may include: at least one memory; and at least one processor coupled to the at least one memory and configured such that the first device: receives from a second device or a third device a first request for a policy for the management of a computing service; generates a policy for the management of the computing service based at least on subscription information related to consumers of the computing service; and sends the policy for the management of the computing service to the second device or the third device.

[0006] In some implementations, the policies for managing computing services include at least one of the following: a policy identifier, the maximum number of nodes or network functions that the computing service can deploy on, the maximum number or percentage of computing resources that the computing service can occupy, the maximum storage space for the computing service, the maximum memory space for the computing service, the maximum number of floating-point operations per second (FLOPS) for the computing service, the maximum time period for the computing service, or the priority of the computing service.

[0007] In some implementations, the first device is made to generate a strategy for managing the computing service based on subscription information and spending restrictions related to the computing service for consumers.

[0008] In some implementations, the first device is also configured to: generate a UE routing policy (URSP); and send the URSP to the second device.

[0009] In some implementations, the first device is further configured to: receive a second request for a URSP from a second device, the second request including first information received from the UE and second information received from a third device; and the first device is configured to generate a URSP based on the second request.

[0010] In some implementations, the first information received from the UE includes at least one of the following: the UE's identifier, the identifier of the application associated with the computing service, the identifier of the process running under the application, the identifier of the thread running under the application, or the identifier of the task running under the application.

[0011] In some implementations, the second information received from the third device includes at least one of the following: an Internet Protocol (IP) address for the computing service, or a fully qualified domain name (FQDN) for the computing service.

[0012] In some implementations, URSP includes a service descriptor and a routing descriptor. The service descriptor includes at least one of the following: an identifier of the application associated with the computing service, an identifier of the process running under the application, an identifier of the thread running under the application, an identifier of the task running under the application, a destination Internet Protocol (IP) address, a domain description, or a service type; and a routing descriptor associated with at least one of the following: Protocol Data Unit (PDU) session information or network slice information.

[0013] Some implementations of a second device described herein may include: at least one memory; and at least one processor coupled to the at least one memory and configured such that the second device: sends a first request to a first device for a policy for managing computing services; receives the policy for managing computing services from the first device; and sends a third request to a third device for computing services, the third request including at least a portion of the policy for managing computing services.

[0014] In some implementations, the policies for managing computing services include at least one of the following: a policy identifier, the maximum number of nodes or network functions that the computing service can deploy on, the maximum number or percentage of computing resources that the computing service can occupy, the maximum storage space for the computing service, the maximum memory space for the computing service, the maximum number of floating-point operations per second (FLOPS) for the computing service, the maximum time period for the computing service, or the priority of the computing service.

[0015] In some implementations, the second device is also configured to: receive a UE routing policy (URSP) from the first device; and send the URSP to the UE.

[0016] In some implementations, the second device is also configured to send a second request for the URSP to the first device, the second request including first information received from the UE and second information received from the third device.

[0017] In some implementations, the first information received from the UE includes at least one of the following: the UE's identifier, the identifier of the application associated with the computing service, the identifier of the process running under the application, the identifier of the thread running under the application, or the identifier of the task running under the application.

[0018] In some implementations, the second information received from the third device includes at least one of the following: an Internet Protocol (IP) address for the computing service, or a fully qualified domain name (FQDN) for the computing service.

[0019] In some implementations, URSP includes a service descriptor and a routing descriptor. The service descriptor includes at least one of the following: an identifier of the application associated with the computing service, an identifier of the process running under the application, an identifier of the thread running under the application, an identifier of the task running under the application, a destination Internet Protocol (IP) address, a domain description, or a service type; and a routing descriptor associated with at least one of the following: Protocol Data Unit (PDU) session information or network slice information.

[0020] In some implementations, the second device is also configured to: send a fourth request to the third device for a measurement of computing resource consumption for computing services; receive the measured computing resource consumption and the priority of the computing services from the third device; and send a billing data request to the fourth device, the billing data request including at least the measured computing resource consumption.

[0021] In some implementations, the measured computational resource consumption includes at least one of the following: time information related to computational resource consumption, or computational resource consumption itself.

[0022] In some implementations, the time information related to computational resource consumption includes at least one of the following: the start time and stop time of computational resource consumption, or the duration of computational resource consumption.

[0023] In some implementations, computing resource consumption includes at least one of the following: the average number or percentage of computing resources used for computing services per unit of time, the average storage space or percentage of storage space used for computing services per unit of time, the average memory space or percentage of memory space used for computing services per unit of time, or the average number of floating-point operations per second (FLOPS) used for computing services.

[0024] In some implementations, the billing data request may also include at least one of the following: the identifier of the consumer of the computing service, an indication of the billing model, or a triggering event associated with the consumption of computing resources.

[0025] Some implementations of a third device described herein may include: at least one memory; and at least one processor coupled to the at least one memory and configured such that the third device: sends a first request to the first device for a policy for the management of computing services; and receives the policy for the management of computing services from the first device.

[0026] In some implementations, the policies for managing computing services include at least one of the following: a policy identifier, the maximum number of nodes or network functions that the computing service can deploy on, the maximum number or percentage of computing resources that the computing service can occupy, the maximum storage space for the computing service, the maximum memory space for the computing service, the maximum number of floating-point operations per second (FLOPS) for the computing service, the maximum time period for the computing service, or the priority of the computing service.

[0027] In some implementations, the third device is also configured to: receive from the second device a fourth request for a measurement of computing resource consumption for computing services; measure the computing resource consumption; and send the measured computing resource consumption and the priority of the computing services to the second device.

[0028] In some implementations, the measured computational resource consumption includes at least one of the following: time information related to computational resource consumption, or computational resource consumption itself.

[0029] In some implementations, the time information related to computational resource consumption includes at least one of the following: the start time and stop time of computational resource consumption, or the duration of computational resource consumption.

[0030] In some implementations, computing resource consumption includes at least one of the following: the average number or percentage of computing resources used for computing services per unit of time, the average storage space or percentage of storage space used for computing services per unit of time, the average memory space or percentage of memory space used for computing services per unit of time, or the average number of floating-point operations per second (FLOPS) used for computing services.

[0031] In some implementations, the third device is also configured to send a billing data request to the fourth device, the billing data request including at least a measurement of computing resource consumption for the computing service.

[0032] In some implementations, the billing data request may also include at least one of the following: the identifier of the consumer of the computing service, an indication of the billing model, or a triggering event associated with the consumption of computing resources.

[0033] Some implementations of a method described herein may include: receiving, at a first device, a first request for a policy for the management of a computing service from a second or third device; generating, at the first device, a policy for the management of the computing service based at least on subscription information related to consumers of the computing service; and sending the policy for the management of the computing service from the first device to the second or third device.

[0034] Some implementations of a method described herein may include: sending a first request from a second device to a first device for a policy for managing computing services; receiving, at the second device, the policy for managing computing services from the first device; and sending a third request from the second device to a third device for computing services, the third request including at least a portion of the policy for managing computing services.

[0035] Some implementations of a method described herein may include: sending a first request from a third device to a first device for a policy for the management of computing services; and receiving the policy for the management of computing services from the first device.

[0036] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0037] Figure 1A and Figure 1B Examples of wireless communication systems supporting policy and charging controls for computing power networks are illustrated in various aspects of this disclosure.

[0038] Figure 2 The illustration shows an exemplary deployment of computing tasks in a 6G computing network according to various aspects of this disclosure;

[0039] Figures 3 to 7 Signaling diagrams are shown, illustrating example processes supporting policy control for computing power networks according to various aspects of this disclosure;

[0040] Figure 8 and Figure 9 Signaling diagrams are shown, illustrating example processes supporting charging control for computing power networks according to various aspects of this disclosure;

[0041] Figure 10 The illustration shows examples of devices supporting policy and charging controls for computing power networks according to some aspects of this disclosure; and

[0042] Figure 11 The diagram illustrates a flowchart of a method for policy control of computing power networks in accordance with other aspects of this disclosure;

[0043] Figure 12 The diagram illustrates a flowchart of a method for policy and charging control for computing power networks, according to other aspects of this disclosure; and

[0044] Figure 13 The diagram illustrates a flowchart of a method for policy and charging control for computing power networks in accordance with other aspects of this disclosure. Detailed Implementation

[0045] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not impose any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0046] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0047] References to "an embodiment," "example embodiment," "embodiment," and "some embodiments" in this disclosure indicate that the described embodiments may include a particular feature, structure, or characteristic, but not every embodiment is required to include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that implementing such a feature, structure, or characteristic in conjunction with other embodiments (whether explicitly described or not) is within their knowledge.

[0048] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0049] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. It will be further understood that the terms “comprising,” “including,” “having,” “containing,” and / or “containing,” when used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0050] The aspects of this disclosure are described in the context of wireless communication systems.

[0051] Figure 1AAn example of a wireless communication system 100A supporting policy and charging controls for computing power networks according to various aspects of this disclosure is illustrated. The wireless communication system 100A may include one or more network entities 102 (also referred to as network devices (NEs)), one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100A may support various radio access technologies. In some implementations, the wireless communication system 100A may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100A may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100A may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100A may support radio access technologies other than 5G. In addition, the wireless communication system 100A can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0052] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100A. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0053] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0054] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100A. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine-Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100A. In some other implementations, UE 104 may be mobile within the wireless communication system 100A.

[0055] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1 illustrates some examples of UEs 104. UEs 104 are capable of communicating with various types of devices, such as network entities 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device), as shown in Figure 1. Additionally or alternatively, UEs 104 may support communication with other network entities 102 or UEs 104 that can be used as relays in the wireless communication system 100A.

[0056] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0057] Network entity 102 may support communication with core network 106 or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). An ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0058] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: Central Unit (CU), Distributed Unit (DU), Radio Unit (RU), RAN Intelligent Controller (RIC) (e.g., near real-time RIC, non-real-time RIC), Service Management and Orchestration (SMO) system, or any combination thereof.

[0059] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0060] The functional decomposition among CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional decomposition can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU.

[0061] Alternatively, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different items in the CU, DU, or RU).

[0062] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by the corresponding network entity 102 communicating via such communication links.

[0063] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)) and user plane entities that route packets or interconnect with external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)). In some implementations, control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0064] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application (APP) server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0065] In the wireless communication system 100A, network entity 102 and UE 104 can use the resources of the wireless communication system 100A (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more parameter sets.

[0066] In the wireless communication system 100A, one or more parameter sets can be supported, and the parameter sets may include subcarrier spacing and cyclic prefix. The first parameter set (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the regular cyclic prefix. In some implementations, the first set of parameters (e.g., ) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. The second parameter set (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the regular cyclic prefix. The third parameter set (e.g., μ =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the regular cyclic prefix or extended cyclic prefix. The fourth parameter set (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the regular cyclic prefix. The fifth parameter set (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the regular cyclic prefix.

[0067] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0068] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100A. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the parameter set. For a regular cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both regular and extended cyclic prefixes can depend on the parameter set. It should be understood that for a first parameter set (e.g., quantity) associated with a first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0069] In the wireless communication system 100A, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100A can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other equipment or devices, for short-range, high-data-rate capabilities.

[0070] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the first parameter set (e.g., ...). μ =0), which includes a 15 kHz subcarrier spacing; the second parameter set (e.g., μ =1), which includes a 30 kHz subcarrier spacing; the third parameter set (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with a third parameter set (e.g., μ =2), which includes a 60 kHz subcarrier spacing; the fourth parameter set (e.g., μ =3), which includes a subcarrier spacing of 120kHz.

[0071] Figure 1B An example of a wireless communication system 100B supporting policy and charging controls for computing power networks according to various aspects of this disclosure is illustrated.

[0072] on the one hand, Figure 1B The diagram shows... Figure 1A The network entities or network functions (NFs) in the core network 106 shown.

[0073] like Figure 1B As shown, the core network 106 may include an application function (AF) 120, a computing service coordination function (CSCF) 122, an NF 140-1 that provides computing services on the CN 106 side, a billing function (CHF) 124, a policy control function (PCF) 126, and a unified data repository (UDR) 128.

[0074] In some implementations, AF 120 can support interaction with core network 106 to provide services such as influencing data routing decisions, policy control functions, or providing third-party services to the network.

[0075] In some implementations, CSCF 122 may include at least one of the following functions: processing computing service requests from UE 104 or AF 120 to core network 106, monitoring available computing resources within RAN 102 or core network 106, or allocating the requested computing service to other NFs capable of providing computing services. In some implementations, CSCF 122 may be referred to as Computing Resource Coordination Function 122 or Computing Task Coordination Function 122.

[0076] In some implementations, the NF 140-1 that provides computing services on the CN 106 side can be a dedicated core network function for computing services, or a subnet function provided by a Network Data Analysis Function (NWDAF), Artificial Intelligence Machine Learning (AIML) function, data analysis function, or data processing function node.

[0077] In some implementations, CHF 124 may include at least one of the following features: support for offline billing, support for online billing, or support for converged billing.

[0078] In some implementations, PCF 126 may include at least one of the following functions: supporting a unified policy framework to manage network behavior, providing policy rules to at least one control plane function to enforce them, accessing subscription information related to policy decisions in UDR 128, or supporting PDU set processing.

[0079] In some implementations, UDR 128 may support at least one of the following functions: storing and retrieving subscription data by Unified Data Management (UDM), storing and retrieving policy data by PCF 126, storing and retrieving structured data for open access, application data (including Packet Flow Description (PFD) for application detection, AF request information for multiple UEs, and 5G Virtual Network (5G-VN) group information for 5G-VN management), or storing and retrieving NF group identifiers (IDs) corresponding to subscriber identifiers (e.g., Internet Protocol (IP) Multimedia Private Identifier (IMPI), IP Multimedia Public Identifier (IMPU), or Subscription Permanent Identifier (SUPI)).

[0080] on the other hand, Figure 1B The diagram illustrates NF 140-2, which provides computing services on the RAN node 102 side, and NF 140-3, which provides computing services on the MEC node 130 side.

[0081] In some implementations, the NF 140-2 providing compute services on the RAN node 102 side can be a dedicated RAN NF for compute services, or an NF provided by RAN node 102, or, in the case of a split RAN architecture, a service-based RAN Central Unit Control Plane (CU-CP) or a service-based RAN Central Unit Compute Plane. Alternatively, NF 140-2 can be provided as a subnet function of other RAN NFs.

[0082] In some implementations, NF 140-3, which provides computing services on the MEC node 130 side, can be an NF provided by MEC node 130.

[0083] In the following text, for the sake of brevity, NF 140-1, 140-2 and 140-3 will be collectively referred to as NF140, which provides computing services.

[0084] It should be noted that the names of each NF described above are merely exemplary. NFs providing the same functionality or service may be named differently. For example, in some implementations, CSCF 122 may be referred to as Computational Resource Coordination Function 122 or Computational Task Coordination Function 122. In this disclosure, it is assumed that the above-described NFs at least provide the aforementioned related functionality or service.

[0085] As mentioned above, in computing power networks, the computing capabilities of 6G networks (including the computing capabilities of RAN, CN, MEC, or cloud supported by 6G networks) are expected to be open to support computing tasks for third-party applications; this is also known as compute-as-a-service. This will refer to... Figure 2 Describe it.

[0086] Figure 2 The illustration depicts an exemplary deployment 200 of computing tasks in a 6G computing power network according to various aspects of this disclosure. For example... Figure 2 As shown,

[0087] The client and server sides of the application (APP) run on UE 104 and application server 118, respectively. When UE 104 or application server 118 faces computational overload, they can request computing services from the 6G network. If nodes in RAN 102 or CN106 have available spare computing resources, they can create and deploy dedicated containers (which share the same operating system and hardware as the 6G network functions but run in a separate / isolated environment) to support third-party application computing tasks.

[0088] Next, it's necessary to specify how to implement policy control for 6G computing power networks. For example, different computing tasks will have to share the same hardware computing resources, and there will be competition and contention between different computing tasks. Some form of Quality of Service (QoS) control is needed to provide higher priority to certain computing tasks based on subscription information.

[0089] To address the aforementioned and other potential problems, the present disclosure provides a solution supporting policy control for computing power networks. In this solution, a first device receives a first request from a second or third device for a policy to manage computing services. The first device then generates a policy for managing the computing services based on subscription information associated with consumers of the computing services. Subsequently, the first device sends the policy for managing the computing services to the second or third device. In this way, the policy for managing the computing services can be generated by considering the subscription information associated with consumers of the computing services. The NF providing the computing services can ensure that the computing services are provided according to the policy.

[0090] In the following text, reference will be made to Figures 3 to 13 The principles of this disclosure are described.

[0091] Figure 3 A signaling diagram is illustrated, illustrating an example process 300 supporting policy control for a computing capability network according to various aspects of this disclosure. Process 300 may involve a first device, a second device, and a third device. In some implementations, the first device may perform... Figure 1B PCF 126 in the middle. Alternatively, the first device can perform the following: Figure 1B In addition to PCF 126, other network functions are included. In some implementations, the second device can perform... Figure 1B CSCF 122 in the middle. Alternatively, the second device can perform the following: Figure 1B In addition to CSCF 122, other network functions are included. In some implementations, a third device can perform... Figure 1B NF 140 in the middle. Alternatively, the third device can perform the operation of NF 140. Figure 1B Other network functions besides NF 140. For discussion purposes, references will be made to... Figure 1B Describe process 300. Process 300 may involve Figure 1B The UE 104, AF 120, CSCF122, NF 140, PCF 126, CHF 124 and UDR 128 are among them.

[0092] Typically, in process 300, CSCF 122 requests a policy for the management of the computing service from PCF 126, and later instructs NF 140, which provides the computing service, to receive at least a portion of the policy for the management of the computing service.

[0093] Specifically, such as Figure 3As shown, due to computational overload, a consumer of the computational service generates and sends a 310 computational service request message to CSCF 122. For example, the consumer of the computational service may include UE 104 or AF 120. For example, AF 120 may be associated with APP server 118, and APP server 118 may be facing computational overload.

[0094] In some implementations, the compute service request message may also include information related to UE 104 or AF 120 (e.g., UE ID or AF ID) and application-related information associated with the compute service. For example, the UE ID may include one of the following: SUPI, Universal Public Subscription Identifier (GPSI), 5G Globally Unique Temporary UE Identifier (5G-GUTI), or 5G System Architecture Evolution Temporary Mobile Station Identifier (5G-S-TMSI). Application-related information may include OSAppId.

[0095] CSCF 122 sends a 320 first request to PCF 126 for a policy for the management of compute services. For brevity, the policy for the management of compute services will also be referred to below as a compute management (CM) policy or compute session policy.

[0096] In some implementations, CSCF 122 can send a message (e.g., an Npcf_CMPolicyControl_Create message) to PCF 126. This message may include a first request for a compute management policy.

[0097] In some implementations, the message may also include: information related to UE 104 or AF 120 (e.g., UE ID or AF ID), and application-related information associated with computing services. For example, the UE ID may include one of the following: SUPI, GPSI, 5G-GUTI, or 5G-S-TMSI. For example, application-related information may include OSAppId.

[0098] Furthermore, PCF 126 generates a computing management policy 330 based at least on subscription information related to the consumer of the computing service. For example, if the consumer includes UE 104, PCF 126 can generate a computing management policy based at least on subscription information related to UE 104. In another example, if the consumer includes AF 120, PCF 126 can generate a computing management policy based at least on subscription information related to AF 120.

[0099] In some implementations, optionally, if PCF 126 does not yet have subscription information related to the consumer, PCF 126 may trigger one or more procedures to query and subscribe to subscription information from UDR 128. For example, PCF 126 may trigger one or more procedures 322 to query or subscribe to subscription information for UE 104 or AF 120.

[0100] Furthermore, in some implementations, PCF 126 may optionally determine that the decision of the computing management policy depends on the state of the policy counter available at CHF 124. In other words, PCF 126 may determine the computing management policy based on the consumer's subscription information and spending restrictions related to the computing services offered to the consumer.

[0101] Therefore, PCF 126 can trigger another process to subscribe to expenditure limit information for CHF 124. For example, PCF 126 can send a 334 subscription message (e.g., an Nchf_SpendingLimitControl_Subscribe message) to CHF 124. PCF 126 can indicate in the subscription message that the subscription is related to a computing service expenditure limit. Computing service expenditure limits are different from traditional expenditure limits related to data service consumption. The subscription message can also include consumer-related information. For example, if the consumer includes UE 104, the consumer-related information may include the UE ID. For another example, if the consumer includes AF 120, the consumer-related information may include the AF ID.

[0102] Upon receiving a subscription message, CHF 124 can send 336 spending restriction information related to consumer computing services to PCF 126.

[0103] In some implementations, the compute management policy may include an identifier for the compute management policy. This identifier can uniquely identify the compute management policy between CSCF 122 and PCF 126.

[0104] Alternatively or additionally, in some implementations, the compute service may be supported by multiple nodes or NFs. In such implementations, the compute management policy may include the maximum number of nodes or NFs on which the compute service can be deployed.

[0105] Alternatively or additionally, in some implementations, the compute management policy may include the maximum number or percentage of compute resources that a compute service can utilize. For example, the compute management policy may include the maximum number or percentage of central processing units (CPUs) that a compute service can utilize. Alternatively or additionally, the compute management policy may include the maximum number or percentage of graphics processing units (GPUs) that a compute service can utilize. Alternatively or additionally, the compute management policy may include the maximum number or percentage of digital processing units (DPUs) that a compute service can utilize. Alternatively or additionally, the compute management policy may include the maximum number or percentage of field-programmable gate arrays (FPGAs) that a compute service can utilize.

[0106] Alternatively or additionally, in some implementations, the compute management policy may include a maximum storage space for compute services. For example, the compute management policy may include a maximum storage space in gigabytes or gigabytes, or a percentage of the maximum storage space.

[0107] Alternatively or additionally, in some implementations, the compute management policy may include a maximum memory space for compute services. For example, the compute management policy may include a maximum memory space in gigabytes or gigabytes, or a percentage of the maximum memory space.

[0108] Alternatively or additionally, in some implementations, the compute management strategy may include a maximum number of floating-point operations per second (FLOPS) for compute services.

[0109] Alternatively or additionally, in some implementations, the compute management strategy may include a maximum time period for compute services.

[0110] Alternatively or additionally, in some implementations, computing management strategies may include prioritizing computing services.

[0111] In some implementations, the priority of a computation service can be indicated by its priority value. In some implementations, a larger priority value indicates a lower priority. For example, priority values ​​can be in the range of 1 to 10, where 1 represents the highest priority. Alternatively, decreasing priority values ​​indicate a lower priority. For example, priority values ​​can be in the range of 1 to 10, where 10 represents the highest priority.

[0112] Alternatively, the priority of computing services can be indicated by a priority type. For example, a priority type can include one of the following: best-effort, burstable, or guaranteed.

[0113] In some implementations, when computing resources are insufficient, computing resources used for lower-priority or best-effort type computing services can be preempted by another computing service of higher priority or guaranteed type.

[0114] In some implementations, if the NF 140 providing computing services supports computing services of different priorities (e.g., from different consumers), the NF 140 can prioritize computing resources for higher-priority computing services when computing resources are limited.

[0115] In some implementations, "guaranteed" types have higher priority than "burstable" types, and "burstable" types have higher priority than "best-effort" types.

[0116] In some implementations, Quality of Service (QoS) values ​​or QoS identifiers can be used to represent a combination of the above elements. In such implementations, QoS values ​​or QoS identifiers can indicate computational management policies.

[0117] Then, PCF 126 sends the 340 computation management policy to CSCF 122.

[0118] In some implementations, PCF 126 can send messages to CSCF 122 (e.g., the Npcf_CMPolicyControl_Create_Response message). This message can include compute management policies.

[0119] In some implementations, if a QoS value or QoS identifier is used to represent a combination of the above elements, the PCF 126 may send a QoS value or QoS identifier that indicates the calculation of the management policy.

[0120] Upon receiving a compute management policy, CSCF 122 sends at least a portion of the compute management policy 350 to at least one NF 140 providing compute services. For example, in Figure 1B In this context, at least one NF 140 may include at least one of the following: NF140-1, NF 140-2, or NF 140-3.

[0121] In some implementations, CSCF 122 can send a compute service request message to at least one NF 140. The compute service request message may include at least a portion of a compute management policy.

[0122] In some implementations, if at least one NF 140 providing computing services has not yet been selected by CSCF 122, CSCF 122 may select NF 140 first. For example, CSCF 122 may select the NF providing computing services based on configuration or information included in a computing service request received from UE 104 or AF 120. CSCF 122 may then send at least a portion of the computing management policy to at least one NF 140.

[0123] Alternatively, if at least one NF 140 providing computing services has been selected by CSCF 122, CSCF 122 may send at least a portion of the computing management policy to at least one NF 140.

[0124] In some implementations, CSCF 122 can send a compute service request message to at least one NF 140. The compute service request message includes at least a portion of a compute management policy.

[0125] In some implementations, if the computing management policy includes an identifier for the computing management policy as described above, then at least a portion of the computing management policy sent to NF 140 may include the identifier for the computing management policy.

[0126] In some implementations, upon receiving at least a portion of the compute management policy, the NF 140 may send a 360 compute service response message to the CSCF 122.

[0127] Furthermore, CSCF 122 can forward the computing service response message 370 to UE 104 or AF 120.

[0128] Process 300 allows for the generation of computing management policies by considering subscription information related to consumers of the computing service. The NF providing the computing service ensures that the computing service is delivered in accordance with the policy.

[0129] Figure 4 A signaling diagram is illustrated, illustrating an example process 400 supporting policy control for a computing capability network according to various aspects of this disclosure. Process 400 may involve a first device, a second device, and a third device. In some implementations, the first device may perform... Figure 1B PCF 126 in the middle. Alternatively, the first device can perform the following: Figure 1B In addition to PCF 126, other network functions are included. In some implementations, the second device can perform... Figure 1B CSCF 122 in the middle. Alternatively, the second device can perform the following: Figure 1B In addition to CSCF 122, other network functions are included. In some implementations, a third device can perform... Figure 1B NF 140 in the middle. Alternatively, the third device can perform the operation of NF 140. Figure 1B Other network functions besides NF 140. For discussion purposes, references will be made to... Figure 1B Describe process 400. Process 400 may involve... Figure 1B The UE 104, AF 120, CSCF122, NF 140, PCF 126, CHF 124 and UDR 128 are among them.

[0130] Typically, in process 400, the NF 140, which provides computing services, requests and receives computing management policies from the PCF 126.

[0131] Actions 310, 320, 330, 332, 334, 336, 360, and 370 in process 400 are the same as those in process 300. For the sake of brevity, the details of these actions have been omitted.

[0132] The difference between process 400 and process 300 lies in actions 415, 420, and 440.

[0133] Specifically, when a request for computing services is received from UE 104 or AF 120, CSCF 122 sends the request for computing services to NF 140, which provides the computing services.

[0134] Upon receiving a request for computing services from CSCF 122, NF 140, which provides computing services, sends a 420 First Request for Computing Management Policy to PCF 126.

[0135] In some implementations, NF 140 can send a message to PCF 126 (e.g., the Npcf_CMPolicyControl_Create message). This message may include a first request for a compute management policy.

[0136] In some implementations, the message may also include: information related to UE 104 or AF 120 (e.g., UE ID or AF ID), and application-related information associated with computing services. For example, the UE ID may include one of the following: SUPI, GPSI, 5G-GUTI, or 5G-S-TMSI. For example, application-related information may include OSAppId.

[0137] After generating the compute management policy, PCF 126 sends compute management policy 440 to NF 140.

[0138] In some implementations, PCF 126 can send messages to NF 140 (e.g., the Npcf_CMPolicyControl_Create_Response message). This message can include compute management policies.

[0139] In some implementations, if a QoS value or QoS identifier is used to represent a combination of the above elements, the PCF 126 may send a QoS value or QoS identifier that indicates the calculation of the management policy.

[0140] In some implementations, when NF 140 provides computing services to UE 104, data traffic associated with the computing service will be routed to Dedicated Protocol Data Unit (PDU) sessions, dedicated network slices, QoS flows, or dedicated (signaling, data, or computing) radio bearers. The UE Routing Policy (URSP) or QoS rules are created by PCF 126 and provided to UE 104. This will refer to... Figure 5 and Figure 6 Describe it.

[0141] It should be noted that although actions 420 and 440 at NF 140 querying the policy for managing the computing service are shown as following action 415 at NF 140 receiving a request for the computing service, this is not a limitation. When there is no actual request for the computing service, NF 140 can retrieve the policy for managing the computing service through actions 420 and 440 (and other related actions such as actions 332, 334, 336, and 330).

[0142] Figure 5 A signaling diagram is illustrated, which illustrates an example process 500 supporting policy control for computing capability networks according to various aspects of this disclosure. Process 500 may involve a first device, a second device, and a third device. In some implementations, the first device may perform... Figure 1B PCF 126 in the middle. Alternatively, the first device can perform the following: Figure 1B In addition to PCF 126, other network functions are included. In some implementations, the second device can perform... Figure 1B CSCF 122 in the middle. Alternatively, the second device can perform the following: Figure 1B In addition to CSCF 122, other network functions are included. In some implementations, a third device can perform... Figure 1B NF 140 in the middle. Alternatively, the third device can perform the operation of NF 140. Figure 1B Other network functions besides NF 140. For discussion purposes, references will be made to... Figure 1B Describe process 500. Process 500 may involve... Figure 1B UE 104, CSCF 122 and PCF 126 in the example.

[0143] like Figure 5 As shown, PCF 126 generates 510 URSP. Then, PCF 126 sends 520 URSP to CSCF 122.

[0144] Upon receiving the URSP, CSCF 122 sends URSP 530 to UE 104.

[0145] In some implementations, URSP includes the association between compute service-related services and PDU sessions. For example, URSP may include: ○ Business descriptor, which may include: ○ Service type, such as computing service-related services; and ○ A route selection descriptor that is associated with at least one of the following route selection components: ○ PDU session information, such as PDU session type or PDU session pair ID (which indicates an indication shared by redundant PDU sessions), or ○ Network slice information, such as single network slice selection assistance information (S-NSSAI).

[0146] Upon receiving a URSP, UE 104 will initiate 540 service bootstrapping based on the received URSP. Specifically, for data services that satisfy the service descriptor (e.g., if the data service is related to computing services), UE 104 will attempt to identify an existing PDU session that satisfies the routing descriptor and bootstrap the relevant service to the identified existing PDU session.

[0147] If an existing PDU session is not found, UE 104 will trigger another procedure 550 to establish a new PDU session. PCF 126 will generate a session management policy 560 and send the session management policy to the relevant SMF (not shown).

[0148] If an existing PDU session is found, PCF 126 can modify the PCC rules of the existing PDU session (which can be triggered by UE 104) and instruct UE 104 to send computing service-related services to a specific QoS flow.

[0149] In some implementations, PCF 126 can generate and send the URSP before UE 104 initiates the Compute Service Request procedure. In some implementations, procedure 500 can be used in conjunction with either procedure 300 or 400. For example, PCF 126 can generate and send the URSP before UE 104 sends the 310 Compute Service Request message, such as... Figure 3 or Figure 4 As shown in the image.

[0150] Figure 6 A signaling diagram is illustrated, which illustrates an example process 600 for policy control of a network supporting computing capabilities according to various aspects of this disclosure. Process 600 may involve a first device, a second device, and a third device. In some implementations, the first device may perform... Figure 1B PCF 126 in the middle. Alternatively, the first device can perform the following: Figure 1BIn addition to PCF 126, other network functions are included. In some implementations, the second device can perform... Figure 1B CSCF 122 in the middle. Alternatively, the second device can perform the following: Figure 1B In addition to CSCF 122, other network functions are included. In some implementations, a third device can perform... Figure 1B NF 140 in the middle. Alternatively, the third device can perform the operation of NF 140. Figure 1B Other network functions besides NF 140. For discussion purposes, references will be made to... Figure 1B Describe process 600. Process 600 may involve... Figure 1B UE 104, CSCF 122 and PCF126 in the example.

[0151] Typically, in process 600, PCF 126 can generate URSP based on a request received from CSCF 122.

[0152] like Figure 6 As shown, CSCF 122 sends a second request for URSP, 605, to PCF 126.

[0153] In some implementations, CSCF 122 may send a message to PCF 126 (e.g., an Npcf_UEPolicyControl_Update_Request message). This message may include a second request for the URSP.

[0154] The second request includes the first information received from UE 104. For example, CSCF 122 can receive the first information from UE 104 in a compute service request message (action 310), such as... Figure 3 or Figure 4 As shown in the image.

[0155] In some implementations, the first information received from UE 104 may include the ID of UE 104 (i.e., UE ID) or the ID of AF120.

[0156] Alternatively or additionally, the first information received from UE 104 may include information related to the application associated with the computing service.

[0157] For example, application-related information may include the application's ID (i.e., APP ID) and a related description. For instance, the APP ID may include OSAppId.

[0158] Alternatively or additionally, application-related information may include at least one of the following: the ID of the process running under the application (i.e., process ID), the ID of the thread running under the application (i.e., thread ID), the ID of the task running under the application (i.e., task ID), or a related description.

[0159] The second request also includes second information received from NF 140, which provides the computing service. For example, CSCF 122 may receive the second information from NF 140 in the computing service response (Action 360), such as... Figure 3 or Figure 4 As shown in the diagram. Alternatively, CSCF122 can know the second information in advance.

[0160] In some implementations, the second information received from the NF 140 providing computing services may include the Internet Protocol (IP) address used for the computing services. In other words, the second information may include the IP address of the NF 140.

[0161] Alternatively or additionally, in some implementations, the second information received from the NF 140 providing the computing service may include the fully qualified domain name (FQDN) for the computing service. In other words, the second information may include the FQDN of the NF 140.

[0162] In some implementations, a second request for a URSP may include at least one of the following: ○ The IP address or FQDN used to calculate the service ○ UE ID ○ App ID, such as OSAppId and related description ○ Process ID and related description ○ Thread ID and related description ○ Task ID and related description.

[0163] Continue to refer to Figure 6 PCF 126 generates URSP 610 based on the second request. Then, PCF 126 sends URSP 620 to CSCF 122.

[0164] Upon receiving the URSP, CSCF 122 sends URSP 630 to UE 104.

[0165] In some implementations, URSP may include: ○ Business descriptor, which includes at least one of the following: ○ App ID, such as OSAppId, ○ Process ID, ○ Thread ID, ○ Task ID ○ Destination IP address, such as the IP address used for computing services. ○ Domain description, such as the FQDN used for compute services, or ○ Service type, such as computing service-related services; and ○ A routing descriptor associated with at least one of the following: ○ PDU session information, such as PDU session type, PDU session pair ID, or ○ Network slice information, such as S-NSSAI.

[0166] Upon receiving a URSP, UE 104 will initiate 640 service bootstrapping based on the received URSP. Specifically, for data services that satisfy the service descriptor, UE 104 will attempt to identify an existing PDU session that satisfies the routing descriptor and bootstrap the relevant service to the identified existing PDU session.

[0167] For example, if the data service is a data service related to computing services from an APP identified by the APP ID in the service descriptor, then UE 104 will attempt to identify an existing PDU session that satisfies the routing descriptor and redirect the relevant service to the identified existing PDU session.

[0168] For another example, if the data service is a compute-related data service originating from a process identified by the process ID in the service descriptor, UE 104 will attempt to identify an existing PDU session that satisfies the routing descriptor and route the relevant service to the identified existing PDU session. In this way, data services from different processes of the same application can be routed to different PDU sessions or network slices.

[0169] For another example, if the data service is a data service related to the computing service that comes from the thread ID identified in the service descriptor, then UE 104 will attempt to identify an existing PDU session that satisfies the routing descriptor and redirect the relevant service to the identified existing PDU session.

[0170] For another example, if the data service is a data service related to a computing service that comes from a task identified by the task ID in the service descriptor, then UE 104 will attempt to identify an existing PDU session that satisfies the routing descriptor and redirect the relevant service to the identified existing PDU session.

[0171] If an existing PDU session is not found, UE 104 will trigger another procedure 650 to establish a new PDU session. PCF 126 will generate a session management policy 660 and send the session management policy to the relevant SMF (not shown).

[0172] If an existing PDU session is found, PCF 126 can modify the PCC rules of the existing PDU session (which can be triggered by UE 104) and instruct UE 104 to send computing service-related services to a specific QoS flow.

[0173] In some implementations, process 600 can be used in conjunction with either process 300 or 400. For example, as part of a compute service request process, PCF 126 can generate and send URSPs, such as... Figure 3 or Figure 4 As shown.

[0174] Figure 7 A signaling diagram is illustrated, which illustrates an example process 700 for policy control of a network supporting computing capabilities according to various aspects of this disclosure. Process 700 can be considered as a combination of process 600 and process 400.

[0175] Actions 310, 320, 330, 332, 334, 336, 360, 415, 420, and 440 in process 700 are the same as those in process 400. Actions 605, 610, 620, 630, 640, 650, and 660 in process 700 are the same as those in process 600. For the sake of brevity, details of these actions have been omitted.

[0176] In some implementations, UE 104 may have data related to computing services that will be transmitted in the uplink, but the associated PDU session (as shown in the URSP) has not yet been established. UE 104 will initiate the PDU session establishment process and indicate that the PDU session is associated with computing services. The SMF should first check whether UE 104 is authorized to have a PDU session dedicated to computing services based on the subscription information retrieved from the UDM and local policies.

[0177] In some implementations, the billing model for computing power networks will differ from traditional data service-based billing. The use of computing resources should be considered. This will refer to... Figure 8 and Figure 9 Describe it.

[0178] Figure 8 A signaling diagram is illustrated, which illustrates an example process 800 for charging control of a computing-capable network according to various aspects of this disclosure. Process 800 may involve a second, third, and fourth device. In some implementations, the second device may perform... Figure 1B CSCF 122 in the middle. Alternatively, the second device can perform the following: Figure 1B In addition to CSCF 122, other network functions are included. In some implementations, a third device can perform... Figure 1B NF 140 in the middle. Alternatively, the third device can perform the operation of NF 140. Figure 1B In addition to NF 140, other network functions are also included. In some implementations, the fourth device can perform... Figure 1B CHF 124 in the middle. Alternatively, the fourth device can perform the following: Figure 1B Other network functions besides CHF 124. For discussion purposes, references will be made to... Figure 1B Describe process 800. Process 800 may involve... Figure 1B CSCF 122, NF 140 and CHF124.

[0179] Typically, in process 800, CSCF 122 subscribes to computing resource consumption for each NF 140 that provides computing services to UE 104 or AF 120. CSCF 122 collects measured computing resource consumption from one or more NF 140s and further provides the relevant information to CHF 124 to create billing records.

[0180] like Figure 8 As shown, CSCF 122 executes a computing service creation process with at least one NF 140 providing computing services. For example, CSCF 122 can execute the computing service creation process with at least one NF 140 by executing at least one of the processes 300 to 700 described above. At least one NF 140 may include... Figure 1B At least one of NF 140-1, 140-2 and 140-3.

[0181] Then, CSCF 122 sends a fourth request (820) to NF 140, which provides the computing services, for the measurement of computing resource consumption used for the computing services. Hereinafter, computing resource consumption is also referred to as computing resource usage.

[0182] In some implementations, CSCF 122 can subscribe to events related to the computing service by sending an Nnfname_EventExposure_Subscribe message to NF 140. This message includes a fourth request for measurements of computing resource consumption used for the computing service. The message may also include at least one of the following: UE ID, AF ID, APP ID, process ID, thread ID, task ID, expiration time, and related information.

[0183] Upon receiving the fourth request, NF 140 measures the relevant computing resource consumption and sends the measured computing resource consumption and computing service priority to CSCF 122. For example, NF 140 may send an Nnfname_EventExpose_Notify message to CSCF 122. The Nnfname_EventExpose_Notify message may include the measured computing resource consumption.

[0184] In some implementations, the measured computational resource consumption may include at least one of the following: time information related to computational resource consumption, or computational resource consumption itself.

[0185] In some implementations, time information related to computational resource consumption may include the start and stop times of computational resource consumption.

[0186] Alternatively or additionally, in some implementations, time information related to computational resource consumption may include the duration of computational resource consumption.

[0187] In some implementations, computational resource consumption may include the average number or percentage of computational resources used for computational services per unit of time. For example, computational resource consumption may include the average number or percentage of CPUs used for computational services per unit of time. Alternatively or additionally, computational resource consumption may include the average number or percentage of GPUs used for computational services per unit of time. Alternatively or additionally, computational resource consumption may include the average number or percentage of DPUs used for computational services per unit of time. Alternatively or additionally, computational resource consumption may include the average number or percentage of FPGAs used for computational services per unit of time.

[0188] Alternatively or additionally, in some implementations, computing resource consumption may include average storage space or a percentage of storage space used per unit of time for computing services. For example, computing resource consumption may include average storage space, or a percentage of storage space in gigabytes or gigabytes, or a percentage used per unit of time.

[0189] Alternatively or additionally, in some implementations, computing resource consumption may include average memory space or a percentage of memory space used per unit of time for computing services. For example, computing resource consumption may include average memory space, or a percentage of memory space in gigabytes or gigabytes, or a percentage used per unit of time.

[0190] Alternatively or additionally, in some implementations, computational resource consumption may include average FLOPS per unit of time used for computational services.

[0191] In some implementations, the Nnfname_EventExpose_Notify message may also include the priority of the computed service.

[0192] In some implementations, the priority of a computation service can be indicated by a priority value, where an increasing priority value indicates a decreasing priority. For example, the priority value can be in the range of 1 to 10, where 1 represents the highest priority.

[0193] Alternatively, the priority of a computing service can be indicated by a priority type. For example, a priority type can include one of the following: best-effort, burstable, or guaranteed.

[0194] Subsequently, CSCF 122 sends an 840 billing data request to CHF 124. The billing data request includes at least the measured computing resource consumption.

[0195] In some implementations, multiple NF 140s can provide computing services to UE 104 or AF 120. In such an implementation, CSCF 122 can obtain measured computing resource consumption from multiple NF 140s. Billing data requests sent to CHF 124 may include measured computing resource consumption from multiple NF 140s.

[0196] In some implementations, a billing data request sent to CHF 124 may include: first time information related to a first computing resource consumption measured by NF 140-1, and second time information related to a second computing resource consumption measured by NF 140-2. For example, if the first time information includes a first time length of the first computing resource consumption, and the second time information includes a second time length of the second computing resource consumption, then the billing data request may include the sum of the first and second time lengths.

[0197] In some implementations, the billing data request sent to CHF 124 may include the sum of a first computing resource consumption measured by NF 140-1 and a second computing resource consumption measured by NF 140-2.

[0198] In some implementations, the billing data request may also include the ID of the consumer providing the computing service. For example, the billing data request may also include the ID of UE 104 or the ID of AF 120.

[0199] Alternatively or additionally, in some implementations, a billing data request may include an indication of a billing model. This indication may specify billing for the computing service, distinguishing it from billing based on data volume.

[0200] Alternatively or additionally, in some implementations, billing data requests may include triggering events associated with computing resource consumption. For example, a triggering event may include that computing resource consumption has reached a certain limit.

[0201] Then, CHF 124 creates an 850 billing record based on the billing data request and sends an 860 billing data response message to CSCF 122.

[0202] Figure 9 A signaling diagram is illustrated, which illustrates an example process 900 for charging control of a computing-capable network according to various aspects of this disclosure. Process 900 may involve a second, third, and fourth device. In some implementations, the second device may perform... Figure 1B CSCF 122 in the middle. Alternatively, the second device can perform the following: Figure 1B In addition to CSCF 122, other network functions are included. In some implementations, a third device can perform... Figure 1B NF 140 in the middle. Alternatively, the third device can perform the operation of NF 140. Figure 1B In addition to NF 140, other network functions are also included. In some implementations, the fourth device can perform... Figure 1B CHF 124 in the middle. Alternatively, the fourth device can perform the following: Figure 1B Other network functions besides CHF 124. For discussion purposes, references will be made to... Figure 1B Describe process 900. Process 900 may involve... Figure 1B CSCF 122, NF 140 and CHF124.

[0203] Typically, in process 900, NF 140 provides billing data requests to CHF 124.

[0204] like Figure 9 As shown, CSCF 122 performs a computing service creation process with at least one NF 140 providing computing services. For example, CSCF 122 can perform the computing service creation process with at least one NF 140 by executing at least one of the processes 300 to 700 described above. At least one NF 140 may include... Figure 1B At least one of NF 140-1, 140-2 and 140-3.

[0205] NF 140 measures computing resource consumption and sends a 920 billing data request to CHF 124. The billing data request includes the measured computing resource consumption. The measured computing resource consumption is compared with a reference... Figure 8 The computational resource consumption of the measurements described is the same. Therefore, for the sake of brevity, details of the computational resource consumption of the measurements have been omitted.

[0206] In some implementations, the billing data request may also include the ID of the consumer providing the computing service. For example, the billing data request may also include the ID of UE 104 or the ID of AF 120.

[0207] Alternatively or additionally, in some implementations, a billing data request may include an indication of a billing model. This indication may specify billing for the computing service, distinguishing it from billing based on data volume.

[0208] Alternatively or additionally, in some implementations, billing data requests may include triggering events associated with computing resource consumption. For example, a triggering event may include that computing resource consumption has reached a certain limit.

[0209] Alternatively or additionally, in some implementations, billing data requests may include the priority of computing services.

[0210] In some implementations, the priority of a computation service can be indicated by a priority value, where an increasing priority value indicates a decreasing priority. For example, the priority value can be in the range of 1 to 10, where 1 represents the highest priority.

[0211] Alternatively, the priority of a computing service can be indicated by a priority type. For example, a priority type can include one of the following: best-effort, burstable, or guaranteed.

[0212] Then, CHF 124 creates a 930 billing record based on the billing data request and sends a 940 billing data response message to NF 140.

[0213] Figure 10 An example of a device 1000 supporting data transmission in a network supporting wireless sensing according to various aspects of this disclosure is illustrated. Device 1000 may be an example of [base station 102, UE 104, or device 120] as described herein. Device 1000 may support wireless communication with one or more base stations 102, UE 104, or any combination thereof. Device 1000 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 1002, memory 1004, transceiver 1006, and optional I / O controller 1008). These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0214] Processor 1002, memory 1004, transceiver 1006, or various combinations thereof, or various components thereof, may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 1002, memory 1004, transceiver 1006, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0215] In some implementations, processor 1002, memory 1004, transceiver 1006, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 1002 and memory 1004 coupled to processor 1002 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 1004 by processor 1002).

[0216] For example, based on the examples disclosed herein, processor 1002 may support wireless communication at device 1000.

[0217] In some implementations, processor 1002 may be configured to support components for performing the following: receiving, at a first device, a first request from a second or third device for a policy for the management of a computing service; at the first device, generating a policy for the management of a computing service based at least on subscription information related to consumers of the computing service; and sending the policy for the management of the computing service from the first device to the second or third device.

[0218] Alternatively, in some implementations, processor 1002 may be configured to support components for performing: sending a first request from a second device to a first device for a policy for managing computing services; receiving, at the second device, the policy for managing computing services from the first device; and sending a third request from the second device to a third device for computing services, the third request including at least a portion of the policy for managing computing services.

[0219] Alternatively, in some implementations, processor 1002 may be configured to support components for performing: sending a first request from a third device to a first device for a policy for the management of computing services; and receiving a policy for the management of computing services from the first device.

[0220] Processor 1002 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 1002 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 1002. Processor 1002 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1004) to cause device 1000 to perform various functions of this disclosure.

[0221] Memory 1004 may include random access memory (RAM) and read-only memory (ROM). Memory 1004 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1002, cause device 1000 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 1002, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 1004 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0222] I / O controller 1008 can manage the input and output signals of device 1000. I / O controller 1008 can also manage peripheral devices not integrated into device 1000. In some implementations, I / O controller 1008 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 1008 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, Linux®, or other known operating systems. In some implementations, I / O controller 1008 can be implemented as part of a processor, such as processor 1002. In some implementations, a user can interact with device 1000 via I / O controller 1008 or via hardware components controlled by I / O controller 1008.

[0223] In some implementations, device 1000 may include a single antenna 1010. However, in other implementations, device 1000 may have more than one antenna 1010 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1006 may communicate bidirectionally via one or more antennas 1010, wired or wireless links, as described herein. For example, transceiver 1006 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1006 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1010 for transmission, and demodulating packets received from one or more antennas 1010. Transceiver 1006 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0224] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 1010 for transmitting the amplified signal over the air or wireless medium.

[0225] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 1010 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0226] Figure 11A flowchart illustrating a method 1100 for policy control of a network supporting computing capabilities according to various aspects of this disclosure is provided. The operation of method 1100 can be implemented by the device or components thereof described herein. For example, the operation of method 1100 can be performed by a first means described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.

[0227] At 1110, the method may include: at a first device, receiving a first request from a second or third device for a policy for the management of computing services. The operation of 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1110 may be performed by the device described with reference to FIG1.

[0228] At 1120, the method may include: at a first device, generating a policy for managing the computing service, based at least on subscription information related to consumers of the computing service. The operation of 1120 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1120 may be performed by the device described with reference to FIG1.

[0229] At 1130, the method may include sending a policy for the management of computing services from the first device to the second or third device. The operation of 1130 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1130 may be performed by the device described with reference to FIG1.

[0230] Figure 12 A flowchart illustrating a method 1200 supporting policy control for a computing power network according to various aspects of this disclosure is provided. Operation of method 1200 can be implemented by the device or components thereof described herein. For example, operation of method 1200 can be performed by a second means described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.

[0231] At 1210, the method may include sending a first request from the second device to the first device for a policy for the management of computing services. The operation of 1210 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1210 may be performed by the device described with reference to FIG1.

[0232] At 1220, the method may include: at the second device, receiving a policy for managing the computing service from the first device. The operation of 1220 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1220 may be performed by the device described with reference to FIG1.

[0233] At 1230, the method may include: sending a third request from the second device to the third device for a computing service, the third request including at least a portion of a policy for managing the computing service. The operation of 1230 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1230 may be performed by the device described with reference to FIG1.

[0234] Figure 13 A flowchart illustrating a method 1300 supporting policy control for a computing power network according to various aspects of this disclosure is provided. Operation of method 1300 may be implemented by the device or components thereof described herein. For example, operation of method 1300 may be performed by a third means described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the described functions.

[0235] At 1310, the method may include sending a first request from the third device to the first device for a policy for the management of computing services. The operation of 1310 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1310 may be performed by the device described with reference to FIG1.

[0236] At 1320, the method may include receiving a policy for managing the computing service from the first device. The operation of 1320 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1320 may be performed by the device described with reference to FIG1.

[0237] It should be understood, for reference Figures 3 to 9 The described implementation also applies to devices 1000 and methods 1100, 1200, and 1300. For the sake of brevity, details of these implementations have been omitted.

[0238] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0239] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0240] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0241] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0242] As used herein, including in the claims, the article “a” preceding an element is a non-limiting article and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” may include one or more elements.

[0243] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first device: Receive a first request from the second or third device for a policy for the management of computing services; The policy for managing the computing service is generated based at least on subscription information related to consumers of the computing service. as well as The policy for managing the computing service is sent to the second device or the third device.

2. The first apparatus of claim 1, wherein the strategy for managing the computing service includes at least one of the following: The identifier of the strategy, The maximum number of nodes or network functions that can be deployed on the computing service. The maximum number or percentage of computing resources that the computing service can occupy. Maximum storage space for the computing service. Maximum memory space used for the computing service The maximum number of floating-point operations per second (FLOPS) used for the computing service. The maximum time period used for the computing service, or The priority of the computing service.

3. The first apparatus of claim 1, wherein the first apparatus is configured to generate the strategy for managing the computing service based on the subscription information and spending restriction information related to the computing service for the consumer.

4. The first device according to claim 1, wherein the first device is further configured to: Generate UE routing policy (URSP); and The URSP is sent to the second device.

5. The first apparatus according to claim 4, wherein: The first device is also made to: The second device receives a second request for the URSP, the second request including first information received from the UE and second information received from the third device; and The first device is configured to generate the URSP based on the second request.

6. The first apparatus according to claim 5, wherein the first information received from the UE includes at least one of the following: The identifier of the UE, The identifier of the application associated with the computing service. The identifier of the process running under the application. The identifier of the thread running under the application, or The identifier of the task running under the application.

7. A second device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the second device: Send a first request to the first device for a policy for the management of computing services; Receive the policy for managing the computing service from the first device; as well as A third request for the computing service is sent to a third device, the third request including at least a portion of the policy for managing the computing service.

8. The second apparatus of claim 7, wherein the strategy for managing the computing service includes at least one of the following: The identifier of the strategy, The maximum number of nodes or network functions that can be deployed on the computing service. The maximum number or percentage of computing resources that the computing service can occupy. Maximum storage space for the computing service. Maximum memory space used for the computing service The maximum number of floating-point operations per second (FLOPS) used for the computing service. The maximum time period used for the computing service, or The priority of the computing service.

9. The second device according to claim 7, wherein the second device is further configured to: Receive UE routing policy (URSP) from the first device; and Send the URSP to the UE.

10. The second device according to claim 9, wherein the second device is further configured to: A second request for the URSP is sent to the first device, the second request including first information received from the UE and second information received from the third device.

11. The second apparatus of claim 10, wherein the first information received from the UE comprises at least one of the following: The identifier of the UE, The identifier of the application associated with the computing service. The identifier of the process running under the application. The identifier of the thread running under the application, or The identifier of the task running under the application.

12. The second apparatus of claim 10, wherein the second information received from the third apparatus includes at least one of the following: The Internet Protocol (IP) address used for the computing service, or The fully qualified domain name (FQDN) used for the computing service.

13. The second apparatus according to claim 9, wherein the URSP comprises: Business descriptors include at least one of the following: The identifier of the application associated with the computing service. The identifier of the process running under the application. The identifier of the thread running under the application. The identifier of the task running under the application. The destination Internet Protocol (IP) address, Domain description, or Service type; as well as A routing descriptor associated with at least one of the following: Protocol Data Unit (PDU) session information, or Network slice information.

14. The second device according to claim 7, wherein the second device is further configured to: Send a fourth request to the third device for measuring the computing resource consumption used for the computing service; Receive the measured computing resource consumption and the priority of the computing service from the third device; as well as A billing data request is sent to the fourth device, the billing data request including at least the measured consumption of the computing resources.

15. The second apparatus of claim 14, wherein the measured computational resource consumption includes at least one of the following: Time information related to the consumption of the computing resources, or The consumption of computing resources.

16. The second apparatus of claim 15, wherein the time information related to the consumption of the computing resources includes at least one of the following: The start and stop times of the computing resource consumption, or The duration of time consumed by computing resources.

17. The second apparatus of claim 15, wherein the computing resource consumption includes at least one of the following: The average number or percentage of computing resources used per unit of time for the computing service The average storage space or percentage of storage space used per unit of time for the computing service. The average memory space or percentage of memory space used per unit of time for the computing service, or Average floating-point operations per second (FLOPS) used for the computing service.

18. The second apparatus of claim 15, wherein the billing data request further comprises at least one of the following: The identifier of the consumer of the computing service Instructions for the billing model, or Triggering events associated with the consumption of the aforementioned computing resources.

19. A third device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the third device: Send a first request to the first device for a policy for the management of computing services; as well as The policy for managing the computing service is received from the first device.

20. A method for communication, comprising: At the first device, a first request for a policy for the management of computing services is received from the second or third device; At the first device, the policy for managing the computing service is generated based at least on subscription information related to consumers of the computing service; as well as The policy for managing the computing service is sent from the first device to the second device or the third device.

Images