WO2023083138A1

WO2023083138A1 - Electronic device and method for communication system and storage medium

Info

Publication number: WO2023083138A1
Application number: PCT/CN2022/130328
Authority: WO
Inventors: 李岚涛; 孙晨
Original assignee: 索尼集团公司; 李岚涛
Priority date: 2021-11-12
Filing date: 2022-11-07
Publication date: 2023-05-19
Also published as: CN116133059A; CN118202702A

Abstract

The present disclosure relates to an electronic device and method for a communication system and a storage medium. Described are embodiments in which the Quality of Service (QoS) of a communication service is configured and coordinated. In the embodiments, an electronic device for a network node comprises a processing circuit, the processing circuit being configured to receive a first request message from a terminal device, wherein the first request message corresponds to a PDU session establishment request or PDU session modification request message, and the first request message at least comprises computing QoS configuration information of a communication service; and provide a computing requirement of the communication service to a computing function (CF) to instantiate a corresponding computing resource.

Description

Electronic device, method and storage medium for communication system

technical field

The present disclosure relates generally to communication devices and communication methods, including techniques for configuring and coordinating quality of service (QoS) for communication services, such as communication computing converged services.

Background technique

In wireless communication systems, the quality of service framework is an important mechanism to guarantee the end-to-end service performance of communication services. In the fifth generation (5G) mobile communication system, a 5G QoS model based on QoS flow (QoS flow) is proposed. The 5G QoS model takes the QoS flow as the granularity, and provides appropriate quality of service for various communication services including communication computing fusion services in terms of communication transmission performance based on the corresponding QoS configuration information (Profile).

There are a variety of computing power resources in the current network system in order to support various services that involve computing to a certain extent (such as communication and computing fusion services). Generally speaking, computing power resources can be deployed on computing power resource platforms such as edge clouds and data centers, and can be deployed together with wireless network devices or network functions, and can even be deployed when terminal devices have sufficient computing power (for example, there is idle computing power). Next, computing power resources are provided by terminal equipment. A variety of computing resources can meet the needs of various service scenarios.

For various communication services, it is desirable to rationally utilize computing power resources and communication transmission resources in order to provide appropriate and satisfactory end-to-end service quality.

Contents of the invention

A first aspect of the present disclosure relates to an electronic device for a network node. The electronic device includes processing circuitry configured to receive a first request message from a terminal device, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least a communication service computing QoS configuration information, the computing QoS configuration information includes at least one of computing QoS parameters or computing QoS characteristics; and providing the computing function CF with computing requirements of the communication service to instantiate corresponding computing power resources, wherein the computing requirements are It is generated when the computing QoS configuration information of the communication service complies with the policy of the terminal device. In some embodiments, the network node may be configured to implement an Access and Mobility Management Function AMF and/or a Session Management Function SMF.

A second aspect of the present disclosure relates to an electronic device for a network node configured to implement a computing function CF. The electronic device comprises a processing circuit configured to receive a computing requirement of a communication service from a session management function (SMF); and provide the SMF with information of instantiated computing power resources.

A third aspect of the present disclosure relates to an electronic device for a terminal device, comprising a processing circuit. The processing circuit is configured to send a first request message to the network, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least operational QoS configuration information of the communication service, the operational QoS The configuration information includes at least one of operational QoS parameters or operational QoS characteristics.

A fourth aspect of the present disclosure relates to an electronic device for a network node configured to implement an Application Function AF. The electronic device includes a processing circuit configured to send an AF requirement to a policy control function PCF, wherein the AF requirement is based on at least one of subscription information of the communication service or a business scenario, and the AF requirement includes an AF requirement of the communication service Calculate QoS configuration information.

A fifth aspect of the present disclosure relates to an electronic device for a network node configured to implement a policy control function PCF. The electronic device includes a processing circuit configured to receive an AF requirement from an application function AF, wherein the AF requirement includes operational QoS configuration information for a communication service; generate a PCC rule based on the AF requirement; and provide a session management function SMF with The PCC rules.

A sixth aspect of the present disclosure relates to various methods for communication including operations or any combination of operations performed by, for example, the various electronic devices described above.

A seventh aspect of the present disclosure relates to a computer-readable storage medium having stored thereon executable instructions that, when executed by one or more processors, implement methods according to various embodiments of the present disclosure. operate.

An eighth aspect of the present disclosure relates to a computer program product comprising instructions which, when executed by a computer, cause methods according to various embodiments of the present disclosure to be implemented.

The foregoing summary is provided to summarize some exemplary embodiments in order to provide a basic understanding of aspects of the subject matter described herein. Accordingly, the above-described features are examples only and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description described in conjunction with the accompanying drawings.

Description of drawings

A better understanding of the present disclosure may be gained when considering the following detailed description of the embodiments when considered in conjunction with the accompanying drawings. The same or similar reference numerals are used in the drawings to denote the same or similar components. The accompanying drawings, together with the following detailed description, are incorporated in and form a part of this specification, and serve to illustrate embodiments of the disclosure and explain principles and advantages of the disclosure. in:

Fig. 1 shows an example block diagram of a communication system according to an embodiment of the present disclosure.

FIG. 2 shows an example structure of a communication system according to an embodiment of the present disclosure.

FIG. 3 shows an example architecture of 5G NR (New Radio) QoS according to an embodiment of the present disclosure.

Fig. 4 illustrates an example electronic device in which a network node according to an embodiment of the disclosure may be implemented.

FIG. 5 shows an example electronic device that can implement a terminal device according to an embodiment of the present disclosure.

FIG. 6 shows an example process flow for configuring QoS of a communication service according to an embodiment of the present disclosure.

FIG. 7 illustrates an example process flow for configuring and coordinating computing and communication QoS parameters of communication services according to an embodiment of the disclosure.

FIG. 8 shows an example processing flow for instantiating computing power resources according to an embodiment of the present disclosure.

9-12B illustrate example methods for communicating according to embodiments of the disclosure.

Fig. 13 shows an example block diagram of a computer that can be implemented as a terminal device or a network node according to an embodiment of the present disclosure.

Fig. 14 shows an example of dividing operation requirements.

15-16 illustrate example signaling flows for communication according to embodiments of the present disclosure.

While the embodiments described in this disclosure may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the embodiments to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and modifications falling within the spirit and scope of the claims. Alternatives.

Detailed ways

Representative applications of aspects such as devices and methods according to the present disclosure are described below. These examples are described only to add context and to assist in understanding the described embodiments. Thus it will be apparent to one skilled in the art that the embodiments described below may be practiced without some or all of the specific details. In other instances, well known process steps have not been described in detail to avoid unnecessarily obscuring the described embodiments. Other applications are possible and the aspects of the present disclosure are not limited to these examples.

Generally, all terms used herein will be interpreted according to their ordinary meanings in the relevant technical field, unless different meanings and/or hints are clearly given in the usage context. References to elements, means, components, units and operations, etc. are intended to be openly interpreted as at least one instance of the elements, means, components, units and operations, unless clearly stated otherwise. The operations of any method disclosed herein do not have to be performed in the exact order disclosed, unless an operation is explicitly or implicitly described as preceding or preceding another operation. Any feature of any embodiment disclosed herein can be applied to any suitable other embodiment. Likewise, any advantage of any embodiment can be applied to any other embodiment, and vice versa. Other objects, features and advantages of the embodiments will become apparent from the following description.

Example of a communication system

Fig. 1 shows an example block diagram of a communication system according to an embodiment of the present disclosure. It should be understood that Figure 1 shows only one of many types and possible arrangements of communication systems; the features of the present disclosure may be implemented in any of a variety of systems, as desired.

As shown in FIG. 1 , a communication system 100 includes base stations 120A, 120B and

terminals

110A, 110B to 110N. The base station and the terminal can be configured to perform uplink and downlink communication through the Uu interface. The base stations 120A, 120B may be configured to communicate with a network 130 (eg, a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and/or the Internet). Accordingly, base stations 120A, 120B may facilitate communication between terminals 110A- 110N and/or between terminals 110A- 110N and network 130 . Further, the terminal devices 110A to 110N can perform direct link communication within an effective communication range through the PC5 interface.

In FIG. 1, the coverage area of base stations 120A, 120B may be referred to as a cell. A base station operating in accordance with one or more cellular communication technologies can provide continuous or nearly continuous communication signal coverage to terminals 110A through 110N over a wide geographic area.

As shown in FIG. 1 , the communication system 100 includes a cloud 150 and a mobile edge computing node (Mobile Edge Computing, MEC) 140. The cloud 150 can provide services, such as IaaS, PaaS, and SaaS, for terminal devices through a connection with the network 130. In the cloud 150 and the MEC 140, computing power resources can be deployed to provide support for meeting the computing needs of communication services (such as communication computing fusion services).

In this disclosure, the base station may be a 5G NR base station, such as gNB and ng-eNB. gNB can provide NR user plane and control plane protocol for terminal equipment termination; ng-eNB is a node defined for compatibility with 4G LTE communication system, which can be an evolved node B (eNB) of LTE radio access network Upgrade to provide Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocols for UE termination. In addition, examples of base stations may include, but are not limited to, the following: at least one of a base transceiver station (BTS) and a base station controller (BSC) in a GSM system; a radio network controller (RNC) and a Node B in a WCDMA system At least one of them; an access point (AP) in a WLAN or a WiMAX system; and a corresponding network node in a communication system to be or being developed. Part of the functions of the base station in this paper can also be implemented as an entity that has a control function for communication in the D2D, M2M, and V2X communication scenarios, or as an entity that plays a role in spectrum coordination in the cognitive radio communication scenario.

In the present disclosure, a terminal device may have its full range of common meanings, for example, a terminal device may be a mobile station (Mobile Station, MS), a user equipment (User Equipment, UE) and the like. An end device may be implemented as a mobile phone, handheld device, media player, computer, laptop, tablet, vehicle-mounted unit or vehicle or virtually any type of wireless device. In some cases, end devices may communicate using multiple wireless communication technologies. For example, a terminal device may be configured to communicate using one or more of GSM, UMTS, CDMA2000, WiMAX, LTE, LTE-A, WLAN, NR, Bluetooth, and the like. Embodiments of the present disclosure will be described more in conjunction with a UE below, however, it should be understood that these embodiments are applicable to any type of terminal equipment.

FIG. 2 shows an example structure of a communication system according to an embodiment of the present disclosure. As an example, system 200 is shown as having 3GPP 5G core network (5GC) functionality. Network functions may be implemented as discrete network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on an appropriate platform (e.g., dedicated hardware or cloud infrastructure) . It should be understood that various processes, functions and characteristics according to the present disclosure may be applicable to other (including those that have been and will be studied) core networks other than 5G. The following describes various network functions (Network Function, NF) by taking the system 200 as an example.

The UPF can act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection with DNs, and a branch point to support multi-homed PDU sessions. UPF can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets, perform traffic usage reporting, perform QoS processing on the user plane (e.g., packet filtering, gating, UL/DL rate execution), perform uplink traffic validation (eg, SDF to QoS flow mapping), transport-level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF may include an uplink classifier to support routing of traffic flows to the data network. A DN can represent various network operator services, Internet access or third-party services. The UPF can interact with the SMF via the N4 reference point between the SMF and the UPF.

The AUSF may store data for authentication of the UE and handle authentication-related functions. AUSF can facilitate a common authentication framework for various access types. AUSF can communicate with AMF via N12 reference point between AMF and AUSF; and can communicate with UDM via N13 reference point between UDM and AUSF. In addition, AUSF can present an interface based on Nausf services.

The AMF may be responsible for registration management (eg responsible for registering UEs, etc.), connection management, reachability management, mobility management and lawful interception of AMF related events, and access authentication and authorization. AMF may be the termination point of the N11 reference point between AMF and SMF. AMF may be the termination point of RAN CP interface, which may include or be the N2 reference point between (R)AN and AMF; and AMF may be the termination point of NAS(N1) signaling and perform NAS encryption and integrity protection .

The AMF can also support NAS signaling with the UE through the N3IWF interface. N3IWF can be used to provide access to untrusted entities. The N3IWF may be the termination point of the N2 interface between the (R)AN of the control plane and the AMF, and may be the termination point of the N3 reference point between the (R)AN of the user plane and the UPF. Thus, the AMF can handle N2 signaling from the SMF and AMF for PDU sessions and QoS, encapsulate/decapsulate packets for IPSec and N3 tunneling, mark N3 user plane packets in the uplink, and perform the corresponding QoS of N3 packet marking, which takes into account the QoS requirements associated with such marking received via N2. N3IWF can also relay uplink and downlink control plane NAS signaling between UE and AMF via the N1 reference point between UE and AMF, and relay uplink and downlink between UE and UPF User plane grouping. N3IWF also provides mechanisms for establishing IPsec tunnels with UEs. AMF can present an interface based on Namf services.

SMF may be responsible for SM (e.g., session establishment, modification and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of UPF traffic Steering to route traffic to the correct destination; terminate interface towards policy control functions; control portion of policy enforcement and QoS; lawful intercept (for SM events and interface to LI systems); terminate SM portion of NAS messages; downlink Initiate AN-specific SM information sent to the AN via N2 via the AMF; and determine the SSC mode for the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables PDU exchange between a UE identified by a Data Network Name (DNN) and a Data Network (DN). A PDU session can be established at UE request, modified at UE and 5GC request, and released at UE and 5GC request using NAS SM signaling exchanged between UE and SMF over the N1 reference point. The 5GC can trigger specific applications in the UE upon request from the application server. In response to receiving the trigger message, the UE may communicate the trigger message (or relevant portion/information of the trigger message) to one or more identified applications in the UE. An identified application in the UE may establish a PDU session to a specific DNN. The SMF may check whether the UE request complies with the user subscription information associated with the UE. In this regard, the SMF may retrieve and/or request to receive update notifications from the UDM regarding SMF-level subscription data.

SMF may include the following roaming functions: processing local execution to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (in VPLMN for SM events and interfaces with LI systems); and support Interaction with external DN to transport signaling for PDU session authorization/authentication via external DN. In a roaming scenario, an N16 reference point between two SMFs can be included in the system 700, which can be located between another SMF in the visited network and an SMF in the home network. In addition, SMF can present an interface based on Nsmf services.

The NEF may provide means for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure/re-exposure, application functions (eg, AF), edge computing or fog computing systems, etc. In such embodiments, the NEF may authenticate, authorize and/or restrict the AF. The NEF can also transform information exchanged with the AF as well as information exchanged with internal network functions. For example, NEF can convert between AF Service Identifier and internal 5GC information. The NEF may also receive information from other network functions (NFs) based on the exposed capabilities of the other network functions. This information can be stored at the NEF as structured data, or at the data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF to other NFs and AFs, and/or used for other purposes such as analysis. In addition, NEF may present an interface based on Nnef services.

NRF may support a service discovery function, receive NF discovery requests from NF instances, and provide NF instances with information of discovered NF instances. NRF also maintains information of available NF instances and the services they support. In addition, NRF may present an interface based on Nnrf services.

PCF may provide policy rules for control plane functions to enforce them, and may also support a unified policy framework for managing network behavior. The PCF may also implement the FE to access subscription information related to policy decisions in the UDM's UDR. The PCF may communicate with the AMF via the N15 reference point between the PCF and AMF, which may include the PCF in the visited network and the AMF in case of roaming scenarios. The PCF may communicate with the AF via the N5 reference point between the PCF and the AF; and communicate with the SMF via the N7 reference point between the PCF and the SMF. The system 200 and/or CN may also include a N24 reference point between the PCF (in the home network) and the PCF in the visited network. In addition, PCF may present an interface based on Npcf services.

The UDM may process subscription-related information to support handling of communication sessions by network entities, and may store UE's subscription data. For example, subscription data may be transferred between UDM and AMF via the N8 reference point between UDM and AMF. UDM may consist of two parts: Application FE and UDR. UDR can store subscription data and policy data of UDM and PCF, and/or structured data for exposure and application data of NEF (including PFD for application detection, application request information of multiple UEs). A Nudr-based service interface may be exposed by the UDR to allow the UDM, PCF, and NEF to access specific sets of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends can serve the same user in different transactions. UDM-FE accesses subscription information stored in UDR, and performs authentication credential processing, user identification processing, access authorization, registration/mobility management, and subscription management. The UDR can interact with the SMF via the N10 reference point between the UDM and the SMF. UDM can also support SMS management, where the SMS-FE implements similar application logic as discussed previously. In addition, UDM can present an interface based on Nudm services.

AF provides application influence on traffic routing, provides access to NCE, and interacts with policy frameworks for policy control. NCE can be the mechanism that allows 5GC and AF to provide information to each other via NEF, which can be used for edge computing implementation. In such implementations, network operator and third party services can be hosted near the accessory's UE access point to enable efficient service delivery with reduced end-to-end delay and load on the transport network. For edge computing specific implementations, the 5GC can select a UPF near the UE and perform traffic diversion from the UPF to the DN via the N6 interface. This may be based on UE subscription data, UE location and information provided by the AF. In this way, AF can influence UPF (re)selection and traffic routing. Based on the operator's deployment, when the AF is considered as a trusted entity, the network operator can allow the AF to directly interact with the relevant NF. In addition, AF can present an interface based on Naf services.

The NSSF may select a set of network slice instances to serve the UE. The NSSF may also determine allowed NSSAIs and mappings to subscribed S-NSSAIs, if required. The NSSF may also determine the set of AMFs to serve the UE, or a list of candidate AMFs, based on appropriate configuration and possibly by querying the NRF. The selection of a set of network slice instances for a UE may be triggered by the AMF, where the UE registers by interacting with the NSSF, which may cause the AMF to change. The NSSF may interact with the AMF via the N22 reference point between the AMF and the NSSF; and may communicate with another NSSF in the visited network via the N31 reference point. In addition, NSSF may present an interface based on Nnssf services.

According to an embodiment of the present disclosure, the system 200 may have a computing function CF (Computing/Computation Function). Computing functions may include sub-functions such as computing resource management, computing resource deployment/allocation, and budget interface adaptation. According to different contexts, computing functions may also be called computing sensing functions, computing management functions, and the like. CF can be used to instantiate computing power resources according to computing requirements from terminal devices or AFs, or coordinate computing power resources with other functional entities based on the deployment of computing power resources. CF may present an interface based on Ncf services.

Figure 3 shows an example architecture of 5G NR QoS according to an embodiment of the present disclosure. The 5G QoS model is based on QoS flows, and supports QoS flows that require guaranteed flow bit rates (GBR QoS flows) and QoS flows that do not require guaranteed flow bit rates (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the smallest granularity for QoS differentiation within a PDU session. In a PDU session, the QoS flow is identified by the QoS Flow ID (QFI) carried in the encapsulation header on the NG-U.

As shown in Figure 3, in the QoS architecture of NG-RAN (such as NR for connection to 5GC and E-UTRA for connection to 5GC), for each UE, 5GC can establish one or more PDU sessions. Together with the PDU session, the NG-RAN may establish at least one data radio bearer (DRB), and then may configure an additional DRB for the QoS flow of the PDU session (when configured may depend on the NG-RAN). NG-RAN can map packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in UE and 5GC can associate UL and DL packets with QoS flows, and AS-level mapping rules in UE and NG-RAN associate UL and DL QoS flows with DRBs.

NG-RAN and 5GC ensure service quality (such as reliability and target latency) by mapping data packets to appropriate QoS flows and DRBs. Therefore, there is a two-step mapping of IP flows to QoS flows (NAS) and QoS flows to DRBs (AS).

At the NAS level, a QoS flow can be characterized by QoS configuration information (Profile) and QoS rules (Rule). The QoS configuration may be provided by the 5GC to the NG-RAN, and the QoS rules may be provided by the 5GC to the UE.

The NG-RAN can determine the handling on the radio interface using the QoS configuration information, and the QoS rules can indicate to the UE the mapping between UL user plane traffic and QoS flows. Depending on its configuration, a QoS flow can be GBR or non-GBR. The QoS Configuration Information for a QoS Flow may contain QoS parameters such as the following (see eg 3GPP TS 23.501).

For each QoS flow:

-5G QoS Identifier (5QI);

- Assignment and Reservation Priority (ARP).

Only in case of GBR QoS flows:

- Guaranteed Stream Bit Rate (GFBR) for UL and DL;

- Maximum Stream Bit Rate (MFBR) for UL and DL;

- For UL and DL, the maximum packet loss rate;

- delay key resource types;

- Notification control.

Only in case of non-GBR QoS flows:

- Reflective QoS Attribute (RQA): RQA, when included, indicates that some (not necessarily all) traffic carried on a QoS flow is subject to Reflective Quality of Service (RQoS) at the NAS;

- Additional QoS flow information.

The 5QI is associated with QoS characteristics and can provide guidelines for setting node-specific parameters for each QoS flow. Standardized or pre-configured 5G QoS characteristics are derived from 5QI values and are not signaled through explicit signaling. Correspondingly, the QoS characteristics that need to be notified by signaling can be used as part of the QoS configuration information. The QoS characteristics of a QoS Flow may include things such as the following (see eg 3GPP TS 23.501).

-priority;

- packet delay budget;

-False alarm rate;

- averaging window;

- Maximum data burst size.

At the AS level, the DRB can define packet handling on the radio interface (Uu). DRB can serve packets with the same packet forwarding process. NG-RAN can perform mapping of QoS flows to DRBs based on QFI and related QoS configuration information (eg including QoS parameters and QoS characteristics). Separate DRBs can be established for QoS flows that require different packet forwarding processing, or multiple QoS flows belonging to the same PDU session can be multiplexed in the same DRB.

In the uplink, the mapping of QoS flows to DRBs can be controlled by mapping rules. Mapping rules can be signaled in two different ways, reflective mapping and explicit configuration (eg via RRC signaling). Regardless of the way in which the mapping rules are notified, the UE always applies the latest updated mapping rules.

The above 5G QoS configuration information and corresponding parameters and characteristics are related to transmission, so as to provide appropriate end-to-end communication or transmission performance. According to the embodiments of the present disclosure, computing QoS configuration information and corresponding parameters and characteristics are defined opposite to the above-mentioned communication QoS, aiming to provide a mechanism to provide appropriate computing performance for communication services. This is more beneficial for communication and computing fusion services such as AR/VR and V2X. Some examples of computing QoS parameters are shown below.

-Computation Power Requirements, including, for example, the universal value/average value of the computing power of the computing power platform (for example, the unit is flops/tflops), the maximum value of the computing power of the computing power platform (for example, the unit is flops/tflops), Haha Rate (H/s), codec capability (such as frame rate, resolution, codec format (such as H.264/H.265)), etc.;

- Computation Priority/Precedence, indicating the processing priority of the computing service;

- Computation Characteristics, including, for example, the computing framework required for computing (such as CUDA), hardware tendencies or requirements (such as CPU, GPU, NPU, FPGA, etc.), system configuration of computing platforms (such as win, linux, etc.), The network communication capability (such as bandwidth) and computing granularity of the computing platform (such as the amount of data that needs to be transmitted for three data packets for one computation);

- Service Identifier (Service Identifier), marking the type of service or indicating the application scenario;

- Computation Deployment, including container deployment, virtual machine deployment, general-purpose servers (such as AF open API supporting computing), etc.;

- Computation Buffer Requirements, including buffer size, buffer read and write speed, distributed cache system type (such as redis, MemCache, SSDB) or hardware specifications (SRAM), etc.;

- The slice number of the computing power slice (Computation S-NSSAI), which is used to indicate the corresponding slice resource selected by the core network for the UE.

In some embodiments, when sending a PDU session establishment or modification request message, the UE may carry the standardized operational QoS parameters or characteristics of each QoS flow at the granularity of the QoS flow, and send it to the core network functional entity. According to some embodiments, the computing resources can be instantiated based on the computing QoS parameters of the communication service (for example, the communication computing fusion service), so as to guarantee the computing performance of the communication service. The communication transmission resources may be configured based on the communication QoS parameters of the communication service, so as to guarantee the communication or transmission performance of the communication service. According to some embodiments, it is possible to coordinate between the operational QoS parameters and the communication QoS parameters of the communication service, so as to achieve the best possible overall quality of service for the communication service under the currently available computing power and communication resources.

example electronics

Fig. 4 illustrates an example electronic device in which a network node according to an embodiment of the disclosure may be implemented. The electronic device 400 may include various units to implement various embodiments for controlling and coordinating communication service QoS according to the present disclosure. In the example of FIG. 4 , the electronic device 400 includes a control unit 402 and a transceiver unit 404 . The control unit 402 may be configured to control or perform operations related to configuration and coordination of communication service QoS, and the transceiving unit 404 may be configured to control or perform operations related to signaling or messaging. Various operations described below in conjunction with network nodes or network functions may be implemented by the units 402 to 404 of the electronic device 400 or other possible units.

In some embodiments, the electronic device 400 may be implemented at a chip level, or may also be implemented at a device level by including other external components such as wired or wireless links. The electronic device 400 can work as a communication device as a complete machine, for example, a network node such as AMF, SMF, or CF.

FIG. 5 shows an example electronic device that can implement a terminal device according to an embodiment of the present disclosure. The electronic device 500 may include various units to implement various embodiments for controlling and coordinating communication service QoS according to the present disclosure. In the example of FIG. 5 , an electronic device 500 includes a control unit 502 and a transceiver unit 504 . The control unit 502 may be configured to control or perform operations related to configuration and coordination of communication service QoS, and the transceiving unit 504 may be configured to control or perform operations related to signaling or messaging. Various operations described below in connection with the terminal device may be implemented by the units 502 to 504 of the electronic device 500 or other possible units.

In some embodiments, electronic device 500 may be implemented at a chip level, or may also be implemented at a device level by including other external components (eg, radio links, antennas, etc.). The electronic device 500 can function as a communication device as a whole, such as a UE, a vehicle-mounted unit, or a vehicle equipped with communication capabilities.

It should be noted that the above-mentioned units are only logical modules divided according to the specific functions they implement, and are not used to limit specific implementation methods, for example, they can be implemented in software, hardware, or a combination of software and hardware. In actual implementation, each of the above units may be implemented as an independent physical entity, or may also be implemented by a single entity (for example, a processor (CPU or DSP, etc.), an integrated circuit, etc.). Herein, processing circuitry may refer to various implementations of digital circuitry, analog circuitry, or mixed-signal (combination of analog and digital) circuitry that performs a function in a computing system. Processing circuitry may include, for example, circuits such as integrated circuits (ICs), application specific integrated circuits (ASICs), portions or circuits of individual processor cores, entire processor cores, individual processors, such as field programmable gate arrays (FPGAs) programmable hardware devices, and/or systems including multiple processors.

Computing performance guarantee based on computing QoS parameters

FIG. 6 shows an example process flow for configuring QoS of a communication service according to an embodiment of the present disclosure. As shown in FIG. 6 , at operation 0, computing policy configuration is performed between the NFs of the core network. The computing policy configuration can be based on AF requirements and PCC rules, etc. Specifically, in some embodiments, the AF may send an AF requirement to the PCF. The AF requirement may be generated based on at least one of communication service or user subscription information or business scenarios. The AF requirement may at least include computing QoS configuration information of the communication service. Additionally, the AF requirement also includes communication QoS configuration information of the communication service.

Correspondingly, the PCF can receive the AF request from the AF. The PCF further generates a PCC rule based on the AF requirement, and provides the PCC rule to the SMF. The PCC rule may include at least operational QoS configuration information for the communication service. Additionally, the PCC rule also includes communication QoS configuration information of the communication service.

Correspondingly, AMF/SMF can receive PCC rules from PCF. The PCC rule may include operational QoS configuration information of the communication service or additional communication QoS configuration information. Further, the AMF/SMF can generate a policy for each UE based on the PCC rule. The AMF/SMF can apply the policy to the PDU session establishment process and PDU session modification process initiated by the corresponding UE and to the corresponding QoS flow.

As shown in Fig. 6, at operation 2, the UE may send a first request message to the core network (eg AMF/SMF). For example, the first request message may correspond to a PDU session establishment request or a PDU session modification request message. Generally, the first request message may be received by the AMF, which in turn forwards session-related information to the SMF. The first request message may at least include computing QoS configuration information of the communication service, and the computing QoS configuration information includes, for example, at least one of computing QoS parameters or computing QoS characteristics. Additionally, the first request message may include communication QoS configuration information of the communication service, where the communication QoS configuration information includes, for example, at least one of communication QoS parameters or communication QoS characteristics. Generally speaking, the operation QoS configuration information and the communication QoS configuration information take the QoS flow as the granularity, and carry the standardized QoS parameters or characteristics corresponding to each QoS flow. For example, computing QoS parameters or characteristics may include at least one of the following, namely, computing power requirements, computing priorities, computing characteristics, service identifiers, computing deployment methods, computing cache requirements, or slice numbers of computing power slices.

It should be understood that the computing QoS configuration information and communication QoS configuration information of the communication service may be determined by the UE based on service characteristics from higher layers (eg application layer, service layer). For example, at operation 1, the UE may obtain the computing requirements of the communication service by parsing data packets (such as application-specific data packet headers) or AT (attention) commands at the NAS level. Further, the UE may map the computing requirement to computing QoS configuration information (for example, including standardized computing QoS parameters and/or characteristics) based on the computing policy. Similarly, the UE can obtain the communication requirements of the communication service, and map the communication requirements into communication QoS configuration information based on the transmission strategy.

As shown in FIG. 6 , at operation 4, the AMF/SMF may provide the computing requirements of the communication service to the CF to instantiate corresponding computing power resources. The computing requirement may be generated when the computing QoS configuration information of the communication service complies with the policy of the terminal device. For example, at operation 3, upon obtaining the operational QoS configuration information of the communication service forwarded by the AMF, the SMF may verify whether it complies with the policy of the terminal device. In the case that the computing QoS configuration information conforms to the policy of the terminal device, the SMF can determine the computing requirements of the communication service based on the computing QoS configuration information.

At operation 3, the SMF may additionally verify whether the communication QoS configuration information of the communication service complies with the policy of the terminal device. In the case that the communication QoS configuration information conforms to the policy of the terminal device, the SMF can determine the communication requirements of the communication service based on the communication QoS configuration information. Further, the SMF can coordinate between computing and communication QoS parameters or characteristics, so as to determine and meet the computing requirements and communication requirements of communication services in a complementary or mutually matching manner, as described in detail later. Furthermore, AMF/SMF can negotiate or coordinate with CF and other network functional entities on the QoS parameters or characteristics of operation and communication, and it is really necessary to establish/modify the initial operation and communication QoS parameters in the QoS flow (such as QoS rules and the packet filter, etc.).

As shown in FIG. 6 , at operation 5 , the CF may provide the SMF with information about the instantiated computing resources. In some embodiments, upon receiving the computing requirement of the communication service from the SMF, the CF may determine the computing resource to be instantiated based on the computing requirement and the available computing resource. For example, the computing power resource may come from at least one of the following, that is, a core network computing power resource entity, a base station or a base station side module, a UPF, a UE, or a third-party computing power resource platform. According to some embodiments, the information of the instantiated computing resource may include configuration information of the computing resource, or further include interface information for accessing the computing resource.

As shown in FIG. 6 , at operation 6, upon receiving the instantiated computing power resource information from the CF, the AMF/SMF may provide a first response message to the UE. The first response message may correspond to a PDU session establishment accept or a PDU session modification accept message. After that, a data plane connection can be established between the UE and the UPF.

Through the processing flow 600, for the established/modified QoS flow, computing resources can be allocated and instantiated based on computing QoS parameters or characteristics, so as to provide appropriate computing performance for communication services. For the established/modified QoS flow, a data plane is established based on communication QoS parameters or characteristics, so as to provide appropriate transmission performance for communication services.

Coordination of Computing and Communication QoS Parameters

In some embodiments, based on the coordinated operational QoS parameters or characteristics, the computational requirements of the communication service may be determined. In some embodiments, the communication needs of the communication service are determined based on the coordinated communication QoS parameters or characteristics. Further, the AMF/SMF may coordinate QoS parameters or characteristics for computation and communication based on both computation QoS configuration information and communication QoS configuration information. By coordinating between computing and communication QoS parameters or characteristics, the communication service can achieve matching computing and communication performance, or the overall performance of the communication service including computing and communication can be improved. Some examples of harmonizing QoS parameters or characteristics for computation and communication are described below.

In some embodiments, QoS parameters or characteristics for computation and communication may be coordinated in a complementary manner. For example, the transmission delay may be determined relative to the operational delay of the communication service, or determined relative to the transmission delay of the communication service such that the sum of the operational delay and the transmission delay is lower than or equal to a threshold level. For communication services carried by QoS flows, the overall delay perceived by users can be composed of two parts: computing delay and transmission delay. It is easy to understand that as long as the sum of the computation delay and the transmission delay is kept below a threshold level, an expected quality of experience (QoE) can be provided in terms of delay. This enables the communication system to have certain flexibility in guaranteeing service delay performance.

For example, when the delay performance provided by the transmission resources is relatively unsatisfactory (that is, the transmission delay is large), computing resources can be configured to make the calculation delay small so as to complement the large transmission delay. As an example, configuring computing power resources may include increasing computing power, increasing the priority of computing tasks, etc.). The opposite holds true as well. For another example, when the delay performance provided by computing power resources is relatively unsatisfactory (that is, the calculation delay is relatively large), transmission resources can be configured to make the transmission delay small so as to complement the large calculation delay. The opposite holds true as well.

It should be understood that AMF/SMF can collect network status, radio resource conditions, and QoS performance data from RAN, UPF, and CF, so as to provide a basis for determining transmission delay parameters and operation delay parameters. For example, transmission delay parameters may include packet delay budget (PDB). The data packet delay budget can correspond to the end-to-end transmission delay, or can be composed of one of the following delays: uplink air interface delay, downlink air interface delay, core network transmission delay, and external network/DN transmission delay. The operation delay parameter can be understood as the time required for a processed data entity to be completely received and processed to form an output result. Specifically, the operation delay parameter may include the waiting time in memory such as cache, PIPE, FIFO or computer priority system, as well as the time spent in the actual operation process.

In some embodiments, QoS parameters or characteristics for computation and communication may be coordinated in a mutually matching or consistent manner. For example, one of arithmetic processing capability and communication bandwidth is determined to match the other of the two based on the relative priorities of communication and arithmetic processing of the communication service. The bandwidth that RAN can provide on the air interface (such as the highest data rate UL/DL GFBR and MFBR corresponding to each QoS flow) needs to be related to the data processing capacity per unit time provided by the computing resources for the QoS flow (that is, data processing capability) match; and vice versa. For example, the data processing capability may include guaranteed data processing capability (Guaranteed Data Processing Capability) and maximum data processing capability (Maximum Data Processing Capability), which correspond to or match the GFBR and MFBR of the QoS flow data transmission rate respectively.

According to some embodiments, when the priority of communication transmission is higher than the priority of operation, communication and computing power resources can be allocated so that the data throughput per unit time of communication is greater than or equal to the data throughput per unit time of operation, so as to ensure timely processing All the processed data are transmitted. For example, for communication and computing fusion services such as AR/VR, game screen rendering, Internet of Vehicles fusion perception, vehicle route decision-making, high-speed fleet travel, pedestrian collision warning, etc., the service can be set to smooth priority/real-time synchronization/high frame rate priority, Then the priority of operation processing can be lower than that of communication transmission. Correspondingly, the communication bandwidth can be set to be superior to the data processing amount per unit time of the operation (that is, when the operation resource is limited, the requirement for the operation processing capacity is reduced), so as to meet the real-time requirement.

According to some embodiments, when the priority of operation processing is higher than that of communication transmission, communication and computing resources can be allocated so that the data throughput per unit time of operation is greater than or equal to the data throughput per unit time of communication, so as to ensure that Perform calculations on all transmitted data in a timely manner. For example, in the case of relatively high requirements for information density/quality/details of processing results (such as movies, remote control, shopping live broadcast, sensor data capture), the communication computing fusion service can be set to give priority to image quality, and the communication The priority can be lower than that of the operation. Correspondingly, the amount of data processed per unit time of calculation needs to be better than the communication bandwidth, so as to meet the requirements for picture quality/information density of processing results.

In the case where the priority of operation processing is equivalent or consistent with that of communication transmission, communication and computing resources can be allocated so that the data throughput per unit time of operation is approximately equal to the data throughput per unit time of communication.

In some embodiments, a priority comparison identifier (Priority Comparison Identifier) may be used to indicate which one needs to be prioritized in operation processing and communication transmission. The identifier may be carried in the PDU session establishment or modification request message, for example. Through the comparison of the above priorities, when any of the computing and communication resources is limited, the priority (computing or communication) corresponding to the limited resources can be set to be high, so as to give priority to guaranteeing higher priority (computing or communication) needs. Correspondingly, there will be redundancy in unconstrained resources. In addition, in actual deployment, a single instantiated computing resource may need to support multiple QoS flows with computing requirements in a PDU session. Correspondingly, the network bandwidth corresponding to the computing resource instance needs to match the data bandwidth of all QoS flows that need to be supported (that is, the data throughput per unit time of computing). In some embodiments, the computing granularity can be used as the QoS guarantee granularity (QoS guarantee granularity) to monitor the real-time QoS performance of the computing and communication of the communication computing fusion service. The QoS guarantee granularity of the communication computing fusion service should be aimed at the complete amount of data that needs to be processed (for example, from the application point of view, it is a complete data unit that needs to be processed), rather than for a single data packet transmitted over the air interface. Therefore, when a single data packet transmitted over the air interface cannot carry the complete amount of data to be processed by the instantiated computing resource at one time, the RAN needs to monitor the real-time QoS performance with the computing granularity of the instantiated computing resource, and adjust the allocation of air interface resources accordingly to meet the requirements of computing resources. Granular QoS requirements.

In one embodiment, multiple data packets may carry the same serial number in the header, so as to identify that the multiple data packets belong to the same data processing sequence/batch. This sequence number can be identified in the packet filter. Correspondingly, the RAN (such as the base station) can be configured to identify multiple data packets as belonging to the same data processing sequence through the sequence number in the data packet header, and monitor the actual communication QoS performance of the multiple data packets.

In an embodiment, the UE or the AF may provide a fixed computing granularity, for example, specifying the computing granularity as N data packets or a time window of X ms. Correspondingly, the RAN (eg base station) may be configured to identify a specific number of data packets or multiple data packets within a specific time window as belonging to the same data processing sequence, and monitor the actual communication QoS performance of these multiple data packets. FIG. 7 illustrates an example process flow for configuring and coordinating computing and communication QoS parameters of communication services according to an embodiment of the disclosure. Through the processing flow 700, the CF, the RAN, and the UPF can provide the AMF/SMF with reference information for computing or communication resource allocation.

In the case that the operation QoS configuration information of the session requested by the UE complies with the policy of the UE, at operation 1a, the AMF/SMF may send an operation request to the CF. Operation requests can include negotiable QoS parameters, such as operation delay, data processing capability/computing power, QoS guarantee granularity (or operation granularity), deployment mode and other parameters; operation requirements can include non-negotiable QoS parameters, such as computing framework requirements, application scenarios, etc. At operation 1b, based on the callable computing resources, the CF can feed back the parameters that can be satisfied to the AMF/SMF, such as the currently guaranteed optimal computing QoS parameters, or the requested computing QoS parameters. CF can also feed back a series of parameter sets of a series of operation instances that can be provided at present. Based on this feedback information, the AMF/SMF may control or adjust operational QoS parameters or requirements, or may coordinate between operational and communication QoS parameters or requirements, as described above. Afterwards, the AMF/SMF can form the computing requirements of the communication service based on the adjusted computing QoS parameters or requirements, and further request the CF to instantiate corresponding computing power resources.

In some embodiments, the computing requirements of a single communication service or QoS flow may require multiple instantiated computing resources to satisfy. For example, in a distributed processing scenario, parallel computing requirements (such as image processing requirements) may be divided into multiple sub-computing requirements, and distributed computing is performed on the computing requirements under time synchronization conditions. For another example, in the scenario of heterogeneous computing requirements, the overall computing requirements (such as data fusion based on image processing) can be divided into sub-computing requirements (such as image processing requirements and data fusion requirements) for different computing architectures/computing instances. According to some embodiments, based on whether there is a dependency relationship among the multiple sub-computing requirements, the divided sub-computing requirements may correspond to serial, parallel or mixed instantiated computing power resources. The division of computing requirements can be understood with reference to the example in FIG. 14 . Correspondingly, CF can allocate/pre-allocate computing resources for sub-computing needs based on managed computing resources and third-party computing resources that can be coordinated. In the allocation of computing power resources, it is also possible to allocate computing power resources with relatively close distances (such as Euclidean distance) or small network transmission delays for UE communication services according to the geographic location of instantiable computing resources and the UE's geographic location instance.

Additionally, at operation 2a, the AMF/SMF may send a network status report request to the UPF, which carries the application identifier of the PDU session and the UE address/ID (such as SUPI (Subscription Permanent Identifier), SUCI (Subscriber Concealed Identifier), GUTI (Global Unique Temporary Identity), etc.), to obtain the QoS data of the external network/DN. At operation 2b, the UPF may provide a network status report to the AMF/SMF. For example, UPF can provide the external network QoS data for the existing PDU session of the UE (that is, the UE has other similar PDU sessions, and the PDU session and the session to be established/modified belong to the same application service); or there are currently other For the data flow of the same application service of the UE, the UPF can provide its external network QoS data without exposing the privacy of other UEs. For example, UPF can form a statistical table for each application service to record the QoS of the external network data flow of different application services.

Additionally, at operation 3a, the AMF/SMF may send a radio resource report request to the RAN to obtain wireless air interface QoS data. At operation 3b, the RAN base station may provide a radio resource report to the AMF/SMF, including the radio air interface QoS data of the UE. If the UE has established an air interface data link, and the RAN has statistical data on the QoS flow granularity/DRB data plane, the wireless air interface QoS data to be reported can be easily obtained. Alternatively, even if the current UE does not have data plane communication, the RAN can find data plane communication with the UE in a similar air interface communication environment based on machine learning/artificial intelligence/pattern matching/location technology, and provide corresponding QoS analysis data. Based on the wireless air interface QoS data, AMF/SMF can determine the QoS parameters that can be satisfied or added.

Replaceable QoS parameters and configuration switching

For communication and computing converged services, there may be room for adjustment of computing and communication QoS parameters. Therefore, by configuring and coordinating QoS parameters, a list of computing or communication QoS parameters arranged or identified by priority can be obtained. The QoS parameter table may include alternative sets of operational QoS parameters or communication QoS parameters. Taking computing QoS parameters as an example, each set of computing QoS parameters can correspond to an instantiable configuration of computing power resources. The AF can provide alternative (computing or communication) QoS requirements to the PCF, and then the PCF generates corresponding PCC rules and indicates them to the SMF, and the SMF generates alternative QoS configurations arranged by priority. Alternative QoS configurations can be understood as hierarchical QoS rules, and these hierarchical QoS rules correspond to different QoS levels acceptable to the application layer. In this way, when the computing power resources or air interface resources change, the computing power resources or air interface resources allocated to the UE can be dynamically adjusted, thereby providing different levels of QoS guarantees.

It should be understood that at least one of the operational QoS configuration information and the communication QoS configuration information may be selected from alternative sets of QoS parameters. Alternative sets of QoS parameters are prioritized or identified as multiple sets of complete QoS parameters, and one set of QoS parameters can be selected based on available or allocated communication resources and/or computing power resources. Example situations in which switching of operational QoS configurations may be triggered are described below.

In some embodiments, when the currently instantiated computing power resources may not be able to continue to meet the computing QoS requirements or there are computing power resources available for instantiation to provide better computing QoS performance, it can be adjusted by SMF to improve Calculate the priority of QoS. The adjustment may include adjusting some or all of the calculated QoS parameters. On the contrary, when it is necessary to reduce the use of computing power resources, it can be adjusted by the SMF, for example, to reduce the priority of computing QoS.

According to some embodiments, the adjustment of the operational QoS parameters may trigger the adjustment of the communication QoS parameters (so that the two match or complement each other). For example, the adjustment may include complementary adjustment of communication delay, matching adjustment of bandwidth, adjustment of QoS guarantee granularity, and so on.

In some embodiments, in the case that the currently allocated transmission resources may not be able to continue to meet the communication QoS requirements or there are allocated transmission resources to provide better communication QoS performance, it can be adjusted, for example, by the SMF to increase the priority of the communication QoS . The adjustment may include adjusting some or all of the communication QoS parameters. On the contrary, in the case that the use of transmission resources needs to be reduced, the priority of communication QoS can be lowered, for example, adjusted by the SMF.

Similarly, adjustments to communication QoS parameters may trigger adjustments to operational QoS parameters (so that the two match or complement each other), according to some embodiments. For example, the adjustment may include complementary adjustment of operation delay, matching adjustment of operation processing capability, and so on.

Of course, the calculation QoS and communication QoS parameters can be adjusted separately, and there is not necessarily a mutual influence relationship. In addition to the alternative QoS configurations arranged by priority generated by the SMF, in some embodiments, the switching of computing and communication QoS configurations can also be implemented through the PDU session modification process or the AF Influence process.

Computing resources deployment method and instantiation

In the embodiments of the present disclosure, computing resources may be deployed in different ways. The computing power resource may come from at least one of the following, that is, a core network computing power resource entity, a base station or a base station side module, UPF, UE, or a third-party computing power resource platform. Different computing resource deployment methods can correspond to different data plane structures.

In some embodiments, the computing resource can be implemented as a single core network functional entity, which can be called a computing instance CI (Computing Instance). Correspondingly, a tunnel interface Ni may be set between the RAN and the CI, and a tunnel interface Nii may be set between the UPF and the CI. FIG. 8 shows an example processing flow for instantiating computing power resources according to an embodiment of the present disclosure.

As shown in FIG. 8, at operation 1a, the AMF/SMF may (for example, request through a computing resource or a computing instance) indicate the Ni Tunnel information of the RAN and the Ni i Tunnel information of the UPF to the CF, and further indicate to the CI. Once the instantiation of computing power resources is completed, CF can allocate Ni Tunnel information and Nii Tunnel information to the obtained CI to receive uplink and downlink data. At operation 1b, the CF will indicate the Ni Tunnel information and Nii Tunnel information allocated to the CI to the AMF/SMF. Through operations 2a and 2b, the SMF can indicate the Nii Tunnel information to the corresponding UPF, thereby completing the establishment of the data plane channel on the network side.

Corresponding to various service scenarios, one or more of the following may be established for communication services. In some embodiments, the uplink data from the terminal device needs to be processed, and the result of the data processing needs to be transmitted to the DN/external network. In some embodiments, the downlink data from the DN/external network needs to be processed, and the result of the data processing needs to be transmitted to the terminal device. In some embodiments, data from an end device needs to be processed and the results of the data processing need to be returned to the end device. Correspondingly, in order to distinguish the above-mentioned different data processing requirements, the following schemes may exist. For example, corresponding QoS flows are respectively established to serve different data processing requirements, even if these data processing requirements belong to the same service request or the same PDU session. Through the configuration of different QoS flows, you can set the corresponding data processing and output result forwarding rules. Another example is mixing multiple data processing requirements on a single QoS flow. Correspondingly, data packet headers corresponding to different data processing requirements may carry corresponding specific identifiers to indicate data processing and output result forwarding rules (for example, whether to process, output result to UE or DN).

In some embodiments, computing resources can also be deployed on the base station side, such as the base station itself or an integrated computing module (such as a server with computing functions), etc. The deployment of computing resources can be controlled by the base station. This framework is conducive to the coordination between computing QoS and communication QoS, at least because the control unit of air interface resources and the control unit of computing resources are more tightly coupled. In these embodiments, no allocation and delivery of tunnel information is required. A finer QoS guarantee granularity (for example, compared with the calculation granularity) can be adopted. For example, the calculation delay requirement of the data transmitted by the data packet can be determined based on the actual air interface transmission delay of each data packet.

In some embodiments, computing power resources can be deployed on the UPF side, for example, as a computing function characteristic of the UPF. Accordingly, the functionality of the CF can be incorporated into the UPF.

In some embodiments, computing power resources can be used as third-party computing resources without being fully controlled by the core network. The third-party computing resources may only coordinate with the core network between computing QoS and communication QoS. Correspondingly, the data plane architecture does not need any modification, only QoS coordination with third-party computing resources through CF is required.

According to some embodiments, a plurality of terminal devices with highly overlapped or even completely consistent computing and communication fusion services can be formed into a group. For example, for services such as marshalling, path planning, and perception fusion in V2X scenarios, or services such as AR/VR/multi-player interactive games involving multimedia, live broadcasting, etc., the data computing and communication requirements that multiple terminal devices need to perform may highly overlap. For example, these multiple terminal devices may all need to render the same picture, and all need to perform path planning/environment perception on the same traffic scene. Correspondingly, in the PDU session establishment/modification process (or in the registration process), multiple terminal devices in the same group can carry the same group ID (such as the group ID of the application layer, the group ID of layer 2) or the group The computing service identifier (Computation Service Identifier) shared by the group terminal equipment assists AMF/SMF and CF to deploy the common computing service of the group to the same instantiated computing resources when allocating computing resources.

example method

FIG. 9 illustrates an example method for communicating according to an embodiment of the disclosure. The method may be executed by the electronic device 400 or a corresponding network function (such as AMF/SMF). As shown in FIG. 9, the method 900 may include receiving a first request message from a terminal device, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least an operation of the communication service Computational QoS configuration information, the computational QoS configuration information including at least one of computational QoS parameters or computational QoS characteristics (block 902). The method may also include providing computing requirements of the communication service to the CF to instantiate corresponding computing power resources, wherein the computing requirements are generated when the computing QoS configuration information of the communication service complies with the policy of the terminal device (block 904). Further details of the method can be understood with reference to the above description of the corresponding network functions.

In one embodiment, the method 900 may include receiving a PCC rule from the PCF, wherein the PCC rule includes operational QoS configuration information of the communication service, wherein the policy of the terminal device is generated based on the PCC rule.

In one embodiment, the computing QoS configuration information includes one or more of the following: computing power requirements, computing priorities, computing characteristics, service identifiers, computing deployment methods, computing cache requirements, or slice numbers of computing power slices.

In one embodiment, the first request message further includes communication QoS configuration information for the communication service, and the method 900 may include coordinating QoS parameters or characteristics for computing and communication based on both the computing QoS configuration information and the communication QoS configuration information; and determining the computational requirements of the communication service based on the coordinated operational QoS parameters or characteristics, and/or determining the communication requirements of the communication service based on the coordinated communication QoS parameters or characteristics.

In one embodiment, coordinating QoS parameters or characteristics for computing and communication includes at least one of: The other one, so that the sum of the operation delay and the transmission delay is lower than or equal to the threshold level; based on the relative priority of the communication and operation processing of the communication service, one of the operation processing capability and the communication bandwidth is determined to be the same as this The other of the two is matched; the real-time QoS performance of the computation and communication of the communication service is monitored based on the computation granularity.

In one embodiment, at least one of the operational QoS configuration information and the communication QoS configuration information is selected from alternative sets of QoS parameters, wherein the alternative sets of QoS parameters are prioritized or identify multiple sets of complete QoS parameters, and select a set of QoS parameters based on available or allocated communication resources and/or computing power resources.

In one embodiment, the method 900 may include receiving information of instantiated computing resources from the CF; and providing a first response message to the UE, wherein the first response message corresponds to a PDU session establishment accept or a PDU session modification accept message .

In one embodiment, one or more of the following is established for the communication service: the uplink data from the terminal device needs to be processed, and the result of the data processing needs to be transmitted to the DN/external network; the downlink data from the DN/extranet The link data needs to be processed, and the result of data processing needs to be transmitted to the terminal device; the data from the terminal device needs to be processed, and the result of data processing needs to be returned to the terminal device.

Figure 15 shows an example signaling flow for communication according to an embodiment of the disclosure. The signaling process 1500 can be performed between a terminal device (such as a UE) and a core network. As shown in Figure 14, at operation 1, the UE may send a computing resource registration request message to the core network (for example, composed of network functions such as AMF, SMF, and CF), which includes information about the computing resources that the UE can provide, including For example, computing resource characteristics or parameters, computing resources available period (computation resources available period), computing resource contract (such as charging policy), air interface path (D2D or Uu interface) and other information elements. Upon receiving the computing resource registration request message, the core network can confirm whether the information elements therein comply with the policy of the UE. If so, the core network (such as AMF, SMF, CF) can record the computing resource information of the UE. The computing resource information can be stored locally in the CF or in the UDM. Next, at operation 2, the core network may send a computing resource registration accept message to the UE. In some embodiments, the above-mentioned operations may be implemented by carrying the above-mentioned information elements in signaling of a registration procedure (registration procedure), a service request procedure (service request procedure), etc., or may be implemented through a dedicated signaling procedure. Through the computing resource registration process, the computing resources of the UE can become computing power resources that can be managed by the core network.

Figure 16 shows an example signaling flow for communication according to an embodiment of the disclosure. The signaling process 1600 may be performed between a terminal device (such as a UE) and a core network. As shown in Figure 15, when computing resources need to be instantiated, CF can search for matching computing resources based on computing requirements. At operation 1, after confirming that the computing resources available to a specific UE can match the computing requirements (including computing characteristic parameters, computing resource availability time period, air interface path and other information elements), the core network can send computing instances to the UE A request message is deployed to wake up the UE. Upon receiving the computing instance deployment message, at operation 2, the UE returns a computing instance deployment acknowledgment (ACK) message to the core network if the computing resources to be deployed match those previously registered with the core network or are available. In some embodiments, the above operations may be implemented by carrying the above information elements in the signaling of the paging process, the service request process triggered by the network, etc., or may be implemented through a dedicated signaling process. Through the computing resource deployment process, the core network can call the idle computing resources of a specific UE to provide computing power support for communication services of other terminal devices or users.

Figure 10 illustrates an example method for communicating according to an embodiment of the disclosure. The method can be executed by the electronic device 400 or a corresponding network function (eg CF). As shown in FIG. 10, the method 1000 can include receiving a computing requirement for a communication service from an SMF (block 1002). The method may also include providing information of the instantiated computing resource to the SMF (block 1004). Further details of the method can be understood with reference to the above description of the corresponding network functions.

In one embodiment, the computing power resource is instantiated based on the computing requirements of the communication service, and the computing power resource comes from at least one of the following: a core network computing power resource entity; a base station or a base station side module, a UPF, a UE, or a second Three-party computing resource platform.

FIG. 11 illustrates an example method for communicating according to an embodiment of the disclosure. The method can be executed by the electronic device 500 or any terminal device. As shown in FIG. 11 , the method 1100 may include sending a first request message to the network, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least the operation QoS configuration of the communication service information, the computed QoS configuration information includes at least one of computed QoS parameters or computed QoS characteristics (block 1102). Optionally, the method may also include receiving a response message from the network, such as a PDU session establishment response or a PDU session modification response message (block 1104). Further details of the method can be understood with reference to the above description about the terminal device.

In one embodiment, the method 1100 may further include obtaining computing requirements of the communication service, and mapping the computing requirements to computing QoS parameters and/or characteristics based on computing policies.

Figure 12A illustrates an example method for communicating according to an embodiment of the disclosure. The method can be executed by the electronic device 400 or corresponding network functions (such as PCF and AF). As shown in FIG. 12A , the method 1200 may include sending an AF requirement from the AF to the PCF, wherein the AF requirement is based on at least one of communication service subscription information or business scenarios, and the AF requirement includes computing QoS configuration information of the communication service; Accordingly, an AF request is received from the AF by the PCF (block 1202). The method may also include generating, by the PCF, PCC rules based on the AF requirements (block 1204). The method may also include providing, by the PCF, the PCC rules to the SMF (block 1206). Further details of the method can be understood with reference to the above description of the corresponding network functions.

Figure 12B illustrates an example method for communicating according to an embodiment of the disclosure. The method may be executed by the electronic device 400 or a corresponding network function (such as a RAN or its base station). As shown in FIG. 12B, the method 1250 may include identifying multiple data packets as belonging to the same data processing sequence through sequence numbers in the data packet headers, and monitoring actual communication QoS performance of the multiple data packets (block 1252). Alternatively, the method may include identifying a certain number of data packets or multiple data packets within a certain time window as belonging to the same data processing sequence, and monitoring the actual communication QoS performance of the multiple data packets (block 1254). Further details of the method can be understood with reference to the above description of the corresponding network functions.

Exemplary electronic devices and methods according to the embodiments of the present disclosure have been respectively described above. It should be understood that the operations or functions of these electronic devices may be combined with each other to realize more or less operations or functions than described. Operational steps of the various methods may also be combined with each other in any suitable order to similarly achieve more or fewer operations than described.

It should be understood that the machine-readable storage medium or the machine-executable instructions in the program product according to the embodiments of the present disclosure may be configured to perform operations corresponding to the above-mentioned device and method embodiments. When referring to the above-mentioned device and method embodiments, the embodiments of the machine-readable storage medium or the program product will be obvious to those skilled in the art, so the description will not be repeated. Machine-readable storage media and program products for carrying or including the above-mentioned machine-executable instructions also fall within the scope of the present disclosure. Such storage media may include, but are not limited to, floppy disks, optical disks, magneto-optical disks, memory cards, memory sticks, and the like. In addition, it should be understood that the series of processes and devices described above may also be implemented by software and/or firmware.

In addition, it should be understood that the series of processes and devices described above may also be implemented by software and/or firmware. In the case of realization by software and/or firmware, the program constituting the software is installed from a storage medium or a network to a computer having a dedicated hardware configuration, such as a general-purpose computer 1300 shown in FIG. , capable of performing various functions and more. Fig. 13 shows an example block diagram of a computer that can be implemented as a terminal device or a network node according to an embodiment of the present disclosure.

In FIG. 13 , a central processing unit (CPU) 1301 executes various processes according to programs stored in a read only memory (ROM) 1302 or loaded from a storage section 1308 to a random access memory (RAM) 1303 . In the RAM 1303, data required when the CPU 1301 executes various processing and the like is also stored as necessary.

The CPU 1301, ROM 1302, and RAM 1303 are connected to each other via a bus 1304. The input/output interface 1305 is also connected to the bus 1304 .

The following components are connected to the input/output interface 1305: an input section 1306 including a keyboard, a mouse, etc.; an output section 1307 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 1308 , including a hard disk, etc.; and the communication part 1309, including a network interface card such as a LAN card, a modem, and the like. The communication section 1309 performs communication processing via a network such as the Internet.

A driver 1310 is also connected to the input/output interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1310 as necessary, so that a computer program read therefrom is installed into the storage section 1308 as necessary.

In the case of realizing the above-described series of processes by software, the programs constituting the software are installed from a network such as the Internet or a storage medium such as the removable medium 1311 .

Those skilled in the art should understand that such a storage medium is not limited to the removable medium 1311 shown in FIG. 13 in which the program is stored and distributed separately from the device to provide the program to the user. Examples of the removable media 1311 include magnetic disks (including floppy disks (registered trademark)), optical disks (including compact disk read only memory (CD-ROM) and digital versatile disks (DVD)), magneto-optical disks (including )) and semiconductor memory. Alternatively, the storage medium may be a ROM 1302, a hard disk contained in the storage section 1308, or the like, in which programs are stored and distributed to users together with devices containing them.

It should be understood that the technical solutions of the present disclosure may be implemented through the following exemplary implementation manners.

1. An electronic device for a network node, the electronic device comprising processing circuitry configured to:

Receiving a first request message from a terminal device, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least computing QoS configuration information of the communication service, and the computing QoS configuration information includes calculating at least one of QoS parameters or calculating QoS characteristics; and

The computing requirement of the communication service is provided to the computing function CF to instantiate corresponding computing resources, wherein the computing requirement is generated when the computing QoS configuration information of the communication service complies with the policy of the terminal device.

2. The electronic device of clause 1, wherein the processing circuit is further configured to:

receiving a PCC rule from a Policy Control Function PCF, wherein the PCC rule contains operational QoS configuration information for the communication service,

Wherein, the policy of the terminal device is generated based on the PCC rule.

3. The electronic device according to clause 1, wherein the operational QoS configuration information includes one or more of the following:

Computing power requirements, computing priority, computing characteristics, service identifiers, computing deployment methods, computing cache requirements, or slice numbers of computing power slices.

4. The electronic device according to clause 1, wherein the first request message further includes communication QoS configuration information of the communication service, and the processing circuit is further configured to:

coordinating QoS parameters or characteristics for computation and communications based on both computation QoS configuration information and communications QoS configuration information; and

Computational requirements of the communication service are determined based on coordinated operational QoS parameters or characteristics, and/or communication requirements of the communication service are determined based on coordinated communication QoS parameters or characteristics.

5. The electronic device of clause 4, wherein coordinating QoS parameters or characteristics for computation and communication includes at least one of the following:

determining the other of the computational latency and the transmission latency relative to the other of the computational latency and the transmission latency of the communication service such that the sum of the computational latency and the transmission latency is less than or equal to a threshold level;

determining one of arithmetic processing capability and communication bandwidth to match the other of the two based on the relative priority of communication and arithmetic processing of the communication service;

The real-time QoS performance of the operation and communication of the communication service is monitored based on the operation granularity.

6. An electronic device according to clause 4, wherein at least one of the operational QoS configuration information and the communication QoS configuration information is selected from alternative sets of QoS parameters,

Wherein, the replaceable sets of QoS parameters are prioritized or identified as multiple sets of complete QoS parameters, and one set of QoS parameters is selected based on available or allocated communication resources and/or computing power resources.

7. The electronic device of clause 1, wherein the processing circuit is further configured to:

receiving instantiated computing resource information from CF; and

A first response message is provided to the UE, wherein the first response message corresponds to a PDU session establishment accept or a PDU session modification accept message.

8. The electronic device of clause 1, wherein for the communication service, one or more of the following holds true:

The uplink data from the terminal device needs to be processed, and the result of the data processing needs to be transmitted to the DN/external network;

The downlink data from the DN/external network needs to be processed, and the result of the data processing needs to be transmitted to the terminal device;

The data from the terminal device needs to be processed, and the result of the data processing needs to be returned to the terminal device.

9. The electronic device according to clause 1, wherein the processing circuit is further configured to: receive a second request message from a terminal device, the second request message including information on computing power resources to be registered by the terminal device; and Sending a second response message to the terminal device to indicate acceptance of the computing resource registration of the terminal device.

10. The electronic device according to clause 9, wherein the processing circuit is further configured to: send a third request message to the terminal device, the third request message indicating to the terminal device the number of computing power resources to be instantiated information; and receiving a third response message from the terminal device, where the third response message includes an acknowledgment by the terminal device of the instantiated computing resources.

11. An electronic device for a network node, wherein said network node is configured to implement a computing function CF, said electronic device comprising a processing circuit configured to:

receive operational requirements for communication services from the Session Management Function SMF; and

Provide the information of the instantiated computing resources to the SMF.

12. The electronic device of clause 11, wherein the computing power resource is instantiated based on computing requirements of the communication service, and the computing power resource is derived from at least one of:

Core network computing resource entity;

Base station or base station side module;

User Plane Function UPF;

UE; or

Third-party computing resource platform.

13. An electronic device for a terminal device, comprising processing circuitry configured to:

Sending a first request message to the network, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least computing QoS configuration information of the communication service, and the computing QoS configuration information includes computing QoS At least one of parametric or operational QoS characteristics.

14. The electronic device of clause 13, wherein the processing circuit is further configured to:

Computational requirements to obtain said communication service; and

Based on the computing policy, the computing requirements are mapped to computing QoS parameters and/or characteristics.

15. The electronic device according to clause 14, wherein the processing circuit is further configured to: send a second request message to the network, the second request message includes information about the computing resource to be registered by the terminal device; and receive information from A second response message from the network, where the second response message indicates that the computing resource registration is accepted.

16. The electronic device of clause 15, wherein the processing circuit is further configured to: receive a third request message from a network, the third request message indicating information on a computing power resource to be instantiated; Sending a third response message, where the third response message includes the terminal device's confirmation of the instantiated computing resources.

17. An electronic device for a network node, wherein the network node is configured to implement an application function AF, the electronic device comprising processing circuitry configured to:

Sending an AF requirement to a policy control function PCF, wherein the AF requirement is based on at least one of subscription information of the communication service or a business scenario, and the AF requirement includes computing QoS configuration information of the communication service.

18. An electronic device for a network node, wherein the network node is configured to implement a policy control function PCF, the electronic device comprising processing circuitry configured to:

receiving an AF requirement from an application function AF, wherein the AF requirement includes computing QoS configuration information of a communication service;

generating PCC rules based on the AF requirements; and

Said PCC rules are provided to a Session Management Function SMF.

19. An electronic device for use in a radio access network, comprising processing circuitry configured to:

Identifying multiple data packets as belonging to the same data processing sequence through the sequence number in the data packet header, and monitoring the actual communication QoS performance of the multiple data packets; or

A specific number of data packets or a plurality of data packets within a specific time window are identified as belonging to the same data processing sequence, and actual communication QoS performance of the plurality of data packets is monitored.

20. A method of wireless communication for a session management function (SMF) and comprising:

receiving a first request message from a terminal device, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least operational QoS configuration information for the communication service, the operational QoS configuration information including calculating at least one of QoS parameters or calculating QoS characteristics; and

21. The method of clause 20, further comprising:

Wherein, the policy of the terminal device is generated based on the PCC rule.

22. The method of clause 20, wherein the first request message further includes communication QoS configuration information for the communication service, and the method further comprises:

23. A computer readable storage medium having stored thereon executable instructions which, when executed by one or more processors, carry out the operations of the method according to any one of clauses 20 to 22 .

24. A computer program product comprising instructions which, when executed by a computer, cause the method according to any one of clauses 20 to 22 to be carried out.

The exemplary embodiments of the present disclosure are described above with reference to the accompanying drawings, but the present disclosure is of course not limited to the above examples. A person skilled in the art may find various alterations and modifications within the scope of the appended claims, and it should be understood that they will naturally come under the technical scope of the present disclosure.

For example, a plurality of functions included in one unit in the above embodiments may be realized by separate devices. Alternatively, a plurality of functions implemented by a plurality of units in the above embodiments may be respectively implemented by separate devices. In addition, one of the above functions may be realized by a plurality of units. Needless to say, such a configuration is included in the technical scope of the present disclosure.

In this specification, the steps described in the flowcharts include not only processing performed in time series in the stated order but also processing performed in parallel or individually and not necessarily in time series. Furthermore, even in the steps of time-series processing, needless to say, the order can be appropriately changed.

Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made hereto without departing from the spirit and scope of the disclosure as defined by the appended claims. Moreover, the terms "comprising", "comprising" or any other variation thereof in the embodiments of the present disclosure are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a series of elements includes not only those elements, but also Include other elements not expressly listed, or also include elements inherent in the process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Claims

An electronic device for a network node, the electronic device comprising processing circuitry configured to:

Receiving a first request message from a terminal device, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least computing QoS configuration information of the communication service, and the computing QoS configuration information includes calculating at least one of QoS parameters or calculating QoS characteristics; and

The computing requirement of the communication service is provided to the computing function CF to instantiate corresponding computing resources, wherein the computing requirement is generated when the computing QoS configuration information of the communication service complies with the policy of the terminal device.
The electronic device of claim 1, wherein the processing circuit is further configured to:

receiving a PCC rule from a Policy Control Function PCF, wherein the PCC rule contains operational QoS configuration information for the communication service,

Wherein, the policy of the terminal device is generated based on the PCC rule.
The electronic device according to claim 1, wherein the operational QoS configuration information includes one or more of the following:

Computing power requirements, computing priority, computing characteristics, service identifiers, computing deployment methods, computing cache requirements, or slice numbers of computing power slices.
The electronic device according to claim 1, wherein the first request message further includes communication QoS configuration information of the communication service, and the processing circuit is further configured to:

coordinating QoS parameters or characteristics for computation and communications based on both computation QoS configuration information and communications QoS configuration information; and

Computational requirements of the communication service are determined based on coordinated operational QoS parameters or characteristics, and/or communication requirements of the communication service are determined based on coordinated communication QoS parameters or characteristics.
The electronic device of claim 4, wherein coordinating QoS parameters or characteristics for computing and communication includes at least one of the following:

determining the other of the computational latency and the transmission latency relative to the other of the computational latency and the transmission latency of the communication service such that the sum of the computational latency and the transmission latency is less than or equal to a threshold level;

determining one of arithmetic processing capability and communication bandwidth to match the other of the two based on the relative priority of communication and arithmetic processing of the communication service;

The real-time QoS performance of the operation and communication of the communication service is monitored based on the operation granularity.
The electronic device according to claim 4, wherein at least one of the operational QoS configuration information and the communication QoS configuration information is selected from alternative sets of QoS parameters,

Wherein, the replaceable sets of QoS parameters are prioritized or identified as multiple sets of complete QoS parameters, and one set of QoS parameters is selected based on available or allocated communication resources and/or computing power resources.
The electronic device of claim 1, wherein the processing circuit is further configured to:

receiving instantiated computing resource information from CF; and

A first response message is provided to the UE, wherein the first response message corresponds to a PDU session establishment accept or a PDU session modification accept message.
The electronic device according to claim 1, wherein for the communication service, one or more of the following holds true:

The uplink data from the terminal device needs to be processed, and the result of the data processing needs to be transmitted to the DN/external network;

The downlink data from the DN/external network needs to be processed, and the result of the data processing needs to be transmitted to the terminal device;

The data from the terminal device needs to be processed, and the result of the data processing needs to be returned to the terminal device.
The electronic device according to claim 1, wherein the processing circuit is further configured to: receive a second request message from the terminal device, the second request message including information on the computing resources to be registered by the terminal device; The terminal device sends a second response message to indicate acceptance of the computing power resource registration of the terminal device.
The electronic device according to claim 9, wherein the processing circuit is further configured to: send a third request message to the terminal device, and the third request message indicates to the terminal device information about computing power resources to be instantiated and receiving a third response message from the terminal device, where the third response message includes an acknowledgment by the terminal device of instantiating computing power resources.
An electronic device for a network node, wherein the network node is configured to implement a computing function CF, the electronic device comprising a processing circuit configured to:

receive operational requirements for communication services from the Session Management Function SMF; and

Provide the information of the instantiated computing resources to the SMF.
The electronic device according to claim 11, wherein the computing power resource is instantiated based on computing requirements of the communication service, and the computing power resource is from at least one of the following:

Core network computing resource entity;

Base station or base station side module;

User Plane Function UPF;

UE; or

Third-party computing resource platform.
An electronic device for a terminal device, comprising processing circuitry configured to:

Sending a first request message to the network, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least computing QoS configuration information of the communication service, and the computing QoS configuration information includes computing QoS At least one of parametric or operational QoS characteristics.
The electronic device of claim 13, wherein the processing circuit is further configured to:

Computational requirements to obtain said communication service; and

Based on the computing policy, the computing requirements are mapped to computing QoS parameters and/or characteristics.
The electronic device according to claim 14, wherein the processing circuit is further configured to: send a second request message to the network, the second request message includes information about computing power resources to be registered by the terminal device; and receive information from the network The second response message of the second response message indicates that the computing resource registration is accepted.
The electronic device according to claim 15, wherein the processing circuit is further configured to: receive a third request message from the network, the third request message indicating the information of the computing resources to be instantiated; and send to the network A third response message, where the third response message includes the terminal device's confirmation of the instantiated computing resources.
An electronic device for a network node, wherein the network node is configured to implement an application function AF, the electronic device comprising a processing circuit configured to:

Sending an AF requirement to a policy control function PCF, wherein the AF requirement is based on at least one of subscription information or business scenarios of the communication service, and the AF requirement includes operational QoS configuration information of the communication service.
An electronic device for a network node, wherein the network node is configured to implement a Policy Control Function PCF, the electronic device comprising processing circuitry configured to:

receiving an AF requirement from an application function AF, wherein the AF requirement includes computing QoS configuration information of a communication service;

generating PCC rules based on the AF requirements; and

Said PCC rules are provided to a Session Management Function SMF.
An electronic device for a radio access network comprising processing circuitry configured to:

Identifying multiple data packets as belonging to the same data processing sequence through the sequence number in the data packet header, and monitoring the actual communication QoS performance of the multiple data packets; or

A specific number of data packets or a plurality of data packets within a specific time window are identified as belonging to the same data processing sequence, and actual communication QoS performance of the plurality of data packets is monitored.
A wireless communication method for a session management function SMF and comprising:

receiving a first request message from a terminal device, wherein the first request message corresponds to a PDU session establishment request or a PDU session modification request message, and the first request message includes at least operational QoS configuration information for the communication service, the operational QoS configuration information including calculating at least one of QoS parameters or calculating QoS characteristics; and

The computing requirement of the communication service is provided to the computing function CF to instantiate corresponding computing power resources, wherein the computing requirement is generated when the computing QoS configuration information of the communication service complies with the policy of the terminal device.
The method of claim 20, further comprising:

receiving a PCC rule from a Policy Control Function PCF, wherein the PCC rule contains operational QoS configuration information for the communication service,

Wherein, the policy of the terminal device is generated based on the PCC rule.
The method according to claim 20, wherein the first request message further includes communication QoS configuration information of the communication service, and the method further comprises:

coordinating QoS parameters or characteristics for computation and communications based on both computation QoS configuration information and communications QoS configuration information; and

Computational requirements of the communication service are determined based on coordinated operational QoS parameters or characteristics, and/or communication requirements of the communication service are determined based on coordinated communication QoS parameters or characteristics.
A computer readable storage medium having stored thereon executable instructions which, when executed by one or more processors, effectuate operations according to the method of any one of claims 20 to 22.
A computer program product comprising instructions which, when executed by a computer, cause the method of any one of claims 20 to 22 to be carried out.