CN118202702A - Electronic device, method and storage medium for communication system - Google Patents

Abstract

The present disclosure relates to electronic devices, methods, and storage media for communication systems. Various embodiments of configuring and coordinating the quality of service of a communication service are described. In an embodiment, an electronic device for a network node includes a processing circuit 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 computing QoS configuration information of the communication service; and providing a computing requirement of the communication service to a computing function CF to instantiate corresponding computing resources.

Description

Electronic device, method and storage medium for communication system Technical Field

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

Background technique

In wireless communication systems, the quality of service framework is an important mechanism to ensure 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 is proposed. The 5G QoS model uses QoS flow as the granularity and provides appropriate service quality for various communication services including communication computing convergence services in terms of communication transmission performance based on the corresponding QoS configuration information (Profile).

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

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

Summary of the invention

The first aspect of the present disclosure relates to an electronic device for a network node. The electronic device includes a processing circuit, which is 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 at least includes operation QoS configuration information of a communication service, and the operation QoS configuration information includes at least one of an operation QoS parameter or an operation QoS characteristic; and provide the operation requirement of the communication service to the operation function CF to instantiate the corresponding computing power resources, wherein the operation requirement is generated when the operation QoS configuration information of the communication service complies with the policy of the terminal device. In some embodiments, the network node can 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, the network node being configured to implement a computing function CF. The electronic device comprises a processing circuit configured to receive computing requirements of a communication service from a session management function SMF; and provide information of instantiated computing resources to the SMF.

A third aspect of the present disclosure relates to an electronic device for a terminal device, comprising a processing circuit, wherein the processing circuit is configured to send a first request message to a 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 at least includes operation QoS configuration information of a communication service, and the operation QoS configuration information includes at least one of an operation QoS parameter or an operation QoS characteristic.

A fourth aspect of the present disclosure relates to an electronic device for a network node, the network node being configured to implement an application function AF. The electronic device comprises a processing circuit, the processing circuit being 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 or a service scenario of a communication service, and the AF requirement comprises operation QoS configuration information of the communication service.

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

A sixth aspect of the present disclosure relates to various methods for communication, which include any 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 executable instructions stored thereon, which, when executed by one or more processors, implement the operations of the methods according to various embodiments of the present disclosure.

An eighth aspect of the present disclosure relates to a computer program product, which comprises instructions, which when executed by a computer, enable the implementation of the method according to various embodiments of the present disclosure.

The above summary is provided to summarize some exemplary embodiments to provide a basic understanding of various aspects of the subject matter described herein. Therefore, the above features are merely examples and should not be interpreted as narrowing 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 clear from the specific embodiments described below in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present disclosure may be obtained when the following detailed description of the embodiments is considered in conjunction with the accompanying drawings. The same or similar reference numerals are used in the various drawings to represent the same or similar components. The accompanying drawings, together with the following detailed description, are included in and form a part of this specification and are used to illustrate embodiments of the present disclosure and to explain the principles and advantages of the present disclosure. Among them:

FIG. 1 shows an exemplary 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.

FIG3 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 present disclosure may be implemented.

FIG. 5 shows an example electronic device in which a terminal device according to an embodiment of the present disclosure can be implemented.

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

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

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

9 to 12B illustrate example methods for communication according to embodiments of the present 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 partitioning computation requirements.

15 to 16 show example signaling flows for communication according to an embodiment of the present disclosure.

Although the embodiments described in the present disclosure may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown as examples in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to limit the embodiments to the particular forms disclosed, but on the contrary, the purpose is to cover all modifications, equivalents and alternatives within the spirit and scope of the claims.

Detailed ways

Representative applications of various aspects such as the apparatus and method of the present disclosure are described below. The description of these examples is only to increase the context and help understand the described embodiments. Therefore, it is clear to those skilled in the art that the embodiments described below can be implemented without some or all of the specific details. In other cases, well-known process steps are not described in detail to avoid unnecessarily obscuring the described embodiments. Other applications are also possible, and the solutions of the present disclosure are not limited to these examples.

In general, all terms used herein will be interpreted according to their common meaning in the relevant technical field, unless different meanings and/or implications are clearly given in the context of use. Unless clearly otherwise specified, references to elements, devices, components, units and operations etc. are intended to be openly interpreted as at least one instance in elements, devices, components, units and operations. The operation of any method disclosed herein need not be performed in the precise order disclosed, unless the operation is clearly or implicitly described as after or before another operation. Any feature of any embodiment disclosed herein may be applied to any other appropriate embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. Other purposes, features and advantages of the embodiment will become clear from the following description.

Communication System Example

Figure 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 can be implemented in any of the various systems as desired.

As shown in FIG1 , the communication system 100 includes base stations 120A, 120B and terminals 110A, 110B to 110N. The base stations and the terminals may be configured to perform uplink and downlink communications via a Uu interface. The base stations 120A, 120B may be configured to communicate with a network 130 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and/or the Internet). Therefore, the base stations 120A, 120B may facilitate communications between the terminals 110A to 110N and/or between the terminals 110A to 110N and the network 130. Further, the terminal devices 110A to 110N may perform direct link communications within an effective communication range via a PC5 interface.

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 may provide continuous or nearly continuous communication signal coverage to terminals 110A through 110N over a wide geographic area.

As shown in FIG1 , the communication system 100 includes a cloud 150 and a mobile edge computing node (MEC) 140. The cloud 150 can provide services such as IaaS, PaaS, and SaaS to terminal devices through a connection with a network 130. In the cloud 150 and the MEC 140, computing resources can be deployed to provide support for computing requirements of communication services (e.g., communication computing fusion services).

In the present disclosure, the base station may be a 5G NR base station, such as a gNB and an ng-eNB. The gNB may provide an NR user plane and control plane protocol terminated with a terminal device; the ng-eNB is a node defined for compatibility with a 4G LTE communication system, which may be an upgrade of an evolved Node B (eNB) of an LTE radio access network, providing an Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminated with a UE. 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; at least one of a radio network controller (RNC) and a Node B in a WCDMA system; an access point (AP) in a WLAN, WiMAX system; and corresponding network nodes in a communication system to be or being developed. Some of the functions of the base station herein may also be implemented as an entity having a control function for communication in D2D, M2M, and V2X communication scenarios, or as an entity that plays a role in spectrum coordination in a cognitive radio communication scenario.

In the present disclosure, terminal devices may have the full breadth of their usual meanings, for example, terminal devices may be mobile stations (Mobile Station, MS), user equipment (User Equipment, UE), etc. Terminal devices may be implemented as wireless devices such as mobile phones, handheld devices, media players, computers, laptops, tablet computers, vehicle-mounted units or vehicles, or almost any type of wireless device. In some cases, terminal devices may communicate using a variety of wireless communication technologies. For example, terminal devices may be configured to communicate using one or more of GSM, UMTS, CDMA2000, WiMAX, LTE, LTE-A, WLAN, NR, Bluetooth, etc. Embodiments of the present disclosure will be described more in conjunction with UE below, but it should be understood that these embodiments are applicable to any type of terminal device.

FIG2 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) functions. 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 features according to the present disclosure may be applicable to other (including those already studied and to be studied) core networks other than 5G. Various network functions (NF) are described below using system 200 as an example.

The UPF may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN, and a branch point to support multi-host PDU sessions. The UPF may also perform packet routing and forwarding, perform packet inspection, execute the user plane portion of the policy rules, legally 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 verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF may include an uplink classifier for supporting routing of traffic flows to the data network. The DN may represent various network operator services, Internet access, or third-party services. The UPF may interact with the SMF via the N4 reference point between the SMF and the UPF.

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

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

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

The 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; configuring traffic steering of the UPF to route traffic to the correct destination; terminating the interface towards the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining 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 the exchange of PDUs between a UE and a data network (DN) identified by a data network name (DNN). A PDU session may be established at the request of the UE, modified at the request of the UE and 5GC, and released at the request of the UE and 5GC using NAS SM signaling exchanged between the UE and SMF over the N1 reference point. Upon request from an application server, the 5GC may trigger a specific application in the UE. In response to receiving the trigger message, the UE may deliver the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE. The identified applications 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 about SMF-level subscription data from the UDM.

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

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

NRF can support service discovery functions, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF also maintains information about available NF instances and the services they support. In addition, NRF can present an interface based on Nnrf services.

The PCF may provide for control plane functions to enforce their policy rules and may also support a unified policy framework for managing network behavior. The PCF may also implement a FE to access subscription information related to policy decisions in the UDR of the UDM. The PCF may communicate with the AMF via the N15 reference point between the PCF and the AMF, which may include the PCF in the visited network and the AMF in a roaming scenario. 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 the CN may also include an N24 reference point between the PCF (in the home network) and the PCF in the visited network. In addition, the PCF may present an interface based on Npcf services.

UDM can process subscription-related information to support the network entity's processing of communication sessions, and can store subscription data of UE. For example, subscription data can be transmitted between UDM and AMF via the N8 reference point between UDM and AMF. UDM may include two parts: application FE and UDR. UDR can store subscription data and policy data of UDM and PCF, and/or structured data for exposure of NEF and application data (including PFD for application detection, application request information of multiple UEs). Nudr service-based interfaces can be presented by UDR to allow 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 changes in relevant data in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. UDM-FE accesses subscription information stored in UDR, and performs authentication credential processing, user identification processing, access authorization, registration/mobility management and subscription management. UDR can interact with SMF via the N10 reference point between UDM and SMF. UDM may also support SMS management, where SMS-FE implements similar application logic discussed previously.In addition, UDM may present an interface based on Nudm services.

AF can provide application influence on traffic routing, provide access to NCE, and interact with the policy framework for policy control. NCE can be a 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 operators and third-party services can be hosted near the UE access point of the attachment to achieve efficient service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementations, 5GC can select UPF near the UE and perform traffic steering from UPF to DN via the N6 interface. This can be based on UE subscription data, UE location and information provided by AF. In this way, AF can affect UPF (re)selection and traffic routing. Based on operator deployment, when AF is considered a trusted entity, the network operator can allow AF to interact directly with relevant NFs. 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. If necessary, the NSSF may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. The NSSF may also determine the set of AMFs, or a list of candidate AMFs, to serve the UE based on appropriate configuration and possibly by querying the NRF. The selection of a set of network slice instances for the UE may be triggered by the AMF, where the UE registers by interacting with the NSSF, which may result in a change in the AMF. 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, the NSSF may present an interface based on the Nnssf service.

According to an embodiment of the present disclosure, the system 200 may have a computing function CF (Computing/Computation Function). The computing function may include sub-functions such as computing resource management, computing resource deployment/allocation, and budget interface adaptation. Depending on the context, the computing function may also be referred to as a computing perception function, a computing management function, etc. The CF may be used to instantiate computing resources according to computing requirements from a terminal device or AF, or coordinate computing resources with other functional entities based on the deployment of computing resources. The CF may present an interface based on Ncf services.

FIG3 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, QoS flows are the minimum granularity for QoS differentiation in a PDU session. In a PDU session, a QoS flow is identified by a QoS flow ID (QFI) carried in an encapsulation header on the NG-U.

As shown in Figure 3, in the QoS architecture of NG-RAN (e.g., for NR connected to 5GC and E-UTRA connected to 5GC), for each UE, 5GC can establish one or more PDU sessions. Together with the PDU session, NG-RAN can establish at least one data radio bearer (DRB), and can then configure additional DRBs for the QoS flow of the PDU session (when to configure may depend on NG-RAN). NG-RAN can map packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC can associate UL and DL packets with QoS flows, and AS-level mapping rules in the 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 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, QoS flows can be characterized by QoS configuration information (Profile) and QoS rules (Rule). 5GC can provide QoS configuration to NG-RAN, and 5GC can provide QoS rules to UE.

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

For each QoS flow:

-5G QoS Identifier (5QI);

-Allocation and Reservation Priority (ARP).

In case of GBR QoS flows only:

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

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

- Maximum packet loss rate for UL and DL;

- Delay critical resource types;

-Notification control.

In case of non-GBR QoS flows only:

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

-Additional QoS flow information.

5QI is associated with QoS characteristics and can provide guidance for setting node-specific parameters for each QoS flow. Standardized or pre-configured 5G QoS characteristics are derived from 5QI values and are not notified through explicit signaling. Accordingly, QoS characteristics that require signaling can be included as part of the QoS configuration information. The QoS characteristics of a QoS flow can include the following (see, for example, 3GPP TS 23.501).

-priority;

-Packet delay budget;

-False alarm rate;

- averaging window;

- Maximum data burst size.

At the AS level, DRBs can define packet processing on the radio interface (Uu). DRBs can serve packets with the same packet forwarding processing. NG-RAN can perform mapping of QoS flows to DRBs based on QFI and related QoS configuration information (e.g., 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. The mapping rules can be notified in two different ways, namely reflective mapping and explicit configuration (e.g., via RRC signaling). Regardless of the way the mapping rules are notified, the UE always applies the most recently updated mapping rules.

The above 5G QoS configuration information and corresponding parameters, characteristics, etc. are all related to transmission, so as to provide appropriate end-to-end communication or transmission performance. According to an embodiment of the present disclosure, operation QoS configuration information and corresponding parameters and characteristics are defined relative to the above communication QoS, aiming to provide a mechanism to provide appropriate operation performance for communication services. This is more beneficial for communication operation fusion services such as AR/VR, V2X, etc. Some examples of operation 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 (e.g., in flops/tflops), the maximum value of the computing power of the computing power platform (e.g., in flops/tflops), hash rate (H/s), codec capabilities (e.g., frame rate, resolution, codec format (e.g., 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 the computation (e.g., CUDA), hardware preferences or requirements (e.g., CPU, GPU, NPU, FPGA, etc.), the system configuration of the computing platform (e.g., Windows, Linux, etc.), the network communication capabilities of the computing platform (e.g., bandwidth), and the computational granularity (e.g., the amount of data that needs to be transmitted for one computation to be performed in three packets);

-Service Identifier, which marks the service type or indicates the application scenario;

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

- Computation Buffer Requirements, including, for example, buffer size, buffer read and write speed, distributed cache system type (e.g., redis, MemCache, SSDB) or hardware specifications (SRAM), etc.

-Slice number of the computing 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 standardized computing QoS parameters or characteristics of each QoS flow at the granularity of the QoS flow to send to the core network functional entity. According to some embodiments, computing resources may be instantiated based on the computing QoS parameters of a communication service (e.g., a communication computing fusion service) to provide a guarantee for the computing performance of the communication service. Communication transmission resources may be configured based on the communication QoS parameters of the communication service to provide a guarantee for the communication or transmission performance of the communication service. According to some embodiments, coordination may be made between the computing QoS parameters and the communication QoS parameters of the communication service to achieve the best possible overall service quality for the communication service under the currently available computing power and communication resources.

Example Electronic Devices

FIG4 shows an example electronic device that can implement a network node according to an embodiment of the present disclosure. 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 FIG4, electronic device 400 includes a control unit 402 and a transceiver unit 404. Control unit 402 may be configured to control or perform operations related to configuration and coordination of communication service QoS, and transceiver unit 404 may be configured to control or perform operations related to signaling or message transceiving. Various operations described below in conjunction with network nodes or network functions may be implemented by units 402 to 404 of electronic device 400 or other possible units.

In some embodiments, the electronic device 400 may be implemented at the chip level, or may be implemented at the device level by including other external components (e.g., wired or wireless links). The electronic device 400 may work as a communication device as a whole, such as a network node such as AMF, SMF, CF.

FIG5 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 FIG5 , the 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 the configuration and coordination of the communication service QoS, and the transceiver unit 504 may be configured to control or perform operations related to signaling or message transceiving. The various operations described below in conjunction with the terminal device may be implemented by units 502 to 504 of the electronic device 500 or other possible units.

In some embodiments, the electronic device 500 may be implemented at the chip level, or may be implemented at the device level by including other external components (e.g., radio links, antennas, etc.). The electronic device 500 may work as a communication device as a whole, such as a UE, an onboard 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 implemented by them, rather than being used to limit the specific implementation methods, for example, they can be implemented in software, hardware or a combination of software and hardware. In actual implementation, the above-mentioned units can be implemented as independent physical entities, or can also be implemented by a single entity (for example, a processor (CPU or DSP, etc.), an integrated circuit, etc.). Among them, the processing circuit can refer to various implementations of a digital circuit system, an analog circuit system or a mixed signal (a combination of analog and digital) circuit system that performs functions in a computing system. The processing circuit may include, for example, circuits such as integrated circuits (ICs), application specific integrated circuits (ASICs), parts or circuits of a separate processor core, the entire processor core, a separate processor, a programmable hardware device such as a field programmable gate array (FPGA), and/or a system including multiple processors.

Computing performance guarantee based on computing QoS parameters

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

Accordingly, the PCF may receive the AF requirement 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 at least include the operation QoS configuration information of the communication service. Additionally, the PCC rule also includes the communication QoS configuration information of the communication service.

Accordingly, AMF/SMF may receive PCC rules from PCF. The PCC rules may include operation QoS configuration information of the communication service or additional communication QoS configuration information. Further, AMF/SMF may generate policies for each UE based on PCC rules. AMF/SMF may 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 Figure 6, at operation 2, the UE may send a first request message to the core network (e.g., 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 the session-related information to the SMF. The first request message may include at least the computing QoS configuration information of the communication service, and the computing QoS configuration information may include, for example, at least one of the computing QoS parameters or computing QoS characteristics. Additionally, the first request message may include the communication QoS configuration information of the communication service, and the communication QoS configuration information may include, for example, at least one of the communication QoS parameters or communication QoS characteristics. Generally speaking, the computing QoS configuration information and the communication QoS configuration information are based on the granularity of the QoS flow, and carry the standardized QoS parameters or characteristics corresponding to each QoS flow. For example, the computing QoS parameters or characteristics may include at least one of the following, namely, computing power requirements, computing priority, computing characteristics, service identifiers, computing deployment methods, computing cache requirements, or slice numbers of computing power slices.

It should be understood that the operation QoS configuration information and communication QoS configuration information of the communication service can be determined by the UE based on the service characteristics from the higher layer (e.g., application layer, service layer). For example, at operation 1, the UE can obtain the operation requirements of the communication service by parsing the data packet (e.g., the first packet of the data packet of a specific application) or the AT (attention) command at the NAS level. Further, the UE can map the operation requirements to the operation QoS configuration information (e.g., including standardized operation QoS parameters and/or characteristics) based on the operation strategy. Similarly, the UE can obtain the communication requirements of the communication service and map the communication requirements to the communication QoS configuration information based on the transmission strategy.

As shown in Figure 6, at operation 4, AMF/SMF can provide the computing requirements of the communication service to CF to instantiate the corresponding computing resources. The computing requirements can 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 computing QoS configuration information of the communication service forwarded by AMF, SMF can verify whether it complies with the policy of the terminal device. When the computing QoS configuration information complies with the policy of the terminal device, SMF can determine the computing requirements of the communication service based on the computing QoS configuration information.

At operation 3, additionally, the SMF may verify whether the communication QoS configuration information of the communication service complies with the policy of the terminal device. In the case where the communication QoS configuration information complies with the policy of the terminal device, the SMF may determine the communication requirements of the communication service based on the communication QoS configuration information. Further, the SMF may coordinate between the operation and communication QoS parameters or characteristics, so as to determine and meet the operation requirements and communication requirements of the communication service in a complementary or mutually matching manner, as described in detail later. Furthermore, the AMF/SMF may negotiate or coordinate the operation and communication QoS parameters or characteristics with the CF and other network functional entities, and indeed the initial operation and communication QoS parameters (such as QoS rules and the packet filters contained therein, etc.) in the QoS flow that need to be established/modified.

As shown in Figure 6, at operation 5, the CF may provide the SMF with information about the instantiated computing power resources. In some embodiments, upon receiving the computing requirements of the communication service from the SMF, the CF may determine the computing power resources to be instantiated based on the computing requirements and the available computing power resources. For example, the computing power resources may come from at least one of the following, namely, 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 power resources may include configuration information of the computing power resources, or may also include interface information for accessing the computing power resources.

As shown in Figure 6, at operation 6, upon receiving the information of the instantiated computing resources 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 acceptance or a PDU session modification acceptance message. After that, a data plane connection may be established between the UE and the UPF.

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

Coordination of computing and communication QoS parameters

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

In some embodiments, QoS parameters or characteristics for computing and communication can be coordinated in a complementary manner. For example, the transmission delay can be determined relative to the computing delay of the communication service, or the computing delay can be determined relative to the transmission delay of the communication service, so that the sum of the computing delay and the transmission delay is less than or equal to a threshold level. For the communication service carried by the QoS flow, the overall delay perceived by the user can be composed of two parts: the computing delay and the transmission delay. It is easy to understand that as long as the sum of the computing delay and the transmission delay is kept below the threshold level, the expected quality of experience (QoE) can be provided in terms of delay. This allows the communication system to have a certain degree of flexibility in ensuring service delay performance.

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

It should be understood that AMF/SMF can collect network status, radio resource conditions and QoS performance data from RAN, UPF and CF, etc., so as to provide a basis for determining transmission delay parameters and operation delay parameters. For example, transmission delay parameters may include data packet delay budget (PDB). The data packet delay budget may correspond to end-to-end transmission delay, or may be composed of one of the following delays: uplink air interface delay, downlink air interface delay, core network transmission delay, 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 on a memory such as a cache, PIPE, FIFO or a computer priority system, as well as the time spent in the actual operation processing process.

In some embodiments, QoS parameters or characteristics for computing and communication may be coordinated in a mutually matching or consistent manner. For example, based on the relative priority of communication and computing processing of the communication service, one of the computing processing capability and the communication bandwidth is determined to match the other of the two. The bandwidth that the RAN can provide on the air interface (e.g., the maximum data rate UL/DL GFBR and MFBR corresponding to each QoS flow) needs to match the data processing per unit time (i.e., data processing capability) provided by the computing resources for the QoS flow; and vice versa. For example, the data processing capability may include a guaranteed data processing capability (Guaranteed Data Processing Capability) and a 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 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 that all data processed by operation can be transmitted in time. For example, for communication and operation fusion services such as AR/VR, game screen rendering, vehicle network fusion perception, vehicle route decision-making, fleet high-speed travel, pedestrian collision warning, etc., the service can be set to smooth priority/real-time synchronization/high frame rate priority, and the priority of operation processing can be lower than the priority of communication transmission. Accordingly, the communication bandwidth can be set to be better than the data processing volume per unit time of operation (that is, when the operation resources are limited, the operation processing capacity requirements are reduced) to meet the real-time requirements.

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

When the priority of computing processing is equal to or consistent with the priority of communication transmission, communication and computing resources can be allocated so that the data throughput per unit time of computing is roughly equal to the data throughput per unit time of communication.

In some embodiments, a priority comparison identifier (Priority Comparison Identifier) can be used to indicate which of the computing processing and communication transmission needs to be prioritized. The identifier can be carried, for example, in a PDU session establishment or modification request message. Through the above-mentioned priority comparison, when either of the computing and communication resources is limited, the (computing or communication) priority corresponding to the limited resource can be set to high, so as to give priority to the (computing or communication) requirements of higher priority. Accordingly, there will be redundancy in non-limited 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. Accordingly, the network bandwidth corresponding to the computing resource instance needs to match the data bandwidth of all QoS flows that need to be supported (i.e., the data throughput per unit time of the computing). In some embodiments, the computing granularity can be used as the 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 for the complete amount of data that needs to be processed (for example, a complete data unit that needs to be processed from the application perspective), 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 that the instantiated computing resources need to process at one time, the RAN needs to monitor the real-time QoS performance at the computing granularity of the instantiated computing resources and adjust the allocation of air interface resources accordingly to meet the QoS requirements at the computing granularity.

In one embodiment, multiple data packets may carry the same sequence number in the header to identify that the multiple data packets belong to the same data processing sequence/batch. The sequence number may be identified in the data packet filter. Accordingly, the RAN (e.g., a base station) may be configured to identify the 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 one embodiment, a fixed operation granularity may be provided by the UE or AF, for example, the operation granularity may be specified as N packets or a time window of X ms, etc. Accordingly, the RAN (e.g., a base station) may be configured to identify a specific number of packets or multiple packets within a specific time window as belonging to the same data processing sequence, and monitor the actual communication QoS performance of the multiple packets. FIG7 shows an example processing flow for configuring and coordinating operation and communication QoS parameters for communication services according to an embodiment of the present disclosure. Through the processing flow 700, the CF, RAN, and UPF may provide reference information for operation or communication resource allocation to the AMF/SMF.

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

In some embodiments, the computing requirements of a single communication service or QoS flow may require multiple instantiated computing resources to meet. For example, in a distributed processing scenario, a parallel computing requirement (e.g., an image processing requirement) can be divided into multiple sub-computing requirements, and distributed computing can be performed on the computing requirements under time synchronization conditions. For another example, in a heterogeneous computing requirement scenario, the overall computing requirement (e.g., data fusion based on image processing) can be divided into sub-computing requirements for different computing architectures/computing instances (e.g., image processing requirements and data fusion requirements). According to some embodiments, based on whether there is a dependency relationship between multiple sub-computing requirements, the divided sub-computing requirements can correspond to serial, parallel or mixed instantiated computing resources. The division of computing requirements can be understood with reference to the example in Figure 14. Accordingly, CF can allocate/pre-allocate computing resources for sub-computing requirements based on the managed computing resources and the third-party computing resources that can be coordinated. In the allocation of computing resources, it is also possible to allocate computing resource instances with a relatively close distance (e.g., Euclidean distance) or a smaller network transmission delay to the UE communication service according to the geographical location of the instantiable computing resources and the geographical location of the UE.

Additionally, at operation 2a, AMF/SMF may send a network status report request to UPF, which carries the application identifier of the PDU session and the UE address/ID (e.g., 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, UPF may provide a network status report to AMF/SMF. For example, UPF may provide the external network QoS data for the existing PDU session of the UE (i.e., the UE has other similar PDU sessions, and the PDU session belongs to the same application service as the session to be established/modified); or if there are data flows of the same application service of other UEs, UPF may provide their external network QoS data without exposing the privacy of other UEs. For example, UPF may form a statistical table for each application service to record the QoS of the external network data flows of different application services respectively.

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, which includes the wireless air interface QoS data of the UE. If the UE already has an established 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 has no data plane communication, the RAN can find the data plane communication with a similar air interface communication environment to the UE based on machine learning/artificial intelligence/pattern matching/positioning technology, and provide corresponding QoS analysis data. Based on the wireless air interface QoS data, the AMF/SMF can determine the QoS parameters that can be met 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 respectively. Therefore, by configuring and coordinating QoS parameters, a computing or communication QoS parameter table arranged or identified by priority can be obtained. The QoS parameter table may include multiple groups of replaceable computing QoS parameters or communication QoS parameters. Taking computing QoS parameters as an example, each group of computing QoS parameters may correspond to an instantiable computing resource configuration. AF may provide replaceable (computing or communication) QoS requirements to PCF, and then PCF may generate corresponding PCC rules and indicate them to SMF, and SMF may generate replaceable QoS configurations arranged by priority. Replaceable QoS configurations may be understood as hierarchical QoS rules, which correspond to different QoS levels acceptable to the application layer. In this way, when computing resources or air interface resources change, the computing resources or air interface resources allocated to the UE may be dynamically adjusted to provide different levels of QoS guarantees.

It should be understood that at least one of the computing QoS configuration information and the communication QoS configuration information can be selected from multiple replaceable sets of QoS parameters. Multiple replaceable sets of QoS parameters prioritize or identify multiple complete sets of QoS parameters, and one of the sets of QoS parameters can be selected based on available or allocated communication resources and/or computing resources. The following describes an example situation that can trigger switching of the computing QoS configuration.

In some embodiments, when the currently instantiated computing power resources may not continue to meet the computing QoS requirements or there are computing power resources available for instantiation to provide better computing QoS performance, the SMF may, for example, adjust to increase the priority of computing QoS. The adjustment may include adjusting some or all of the parameters in the computing QoS parameters. Conversely, when it is necessary to reduce the use of computing power resources, the SMF may, for example, adjust to reduce the priority of computing QoS.

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

In some embodiments, when the currently allocated transmission resources may not continue to meet the communication QoS requirements or there are transmission resources that can be allocated to provide better communication QoS performance, the priority of the communication QoS can be increased, for example, by the SMF. The adjustment may include adjusting some or all of the communication QoS parameters. On the contrary, when it is necessary to reduce the use of transmission resources, the priority of the communication QoS can be reduced, for example, by the SMF.

According to some embodiments, similarly, adjustment of communication QoS parameters may trigger adjustment of computing QoS parameters (so that the two are matched or complementary to each other). For example, the adjustment may include complementary adjustment of computing latency, matching adjustment of computing processing capacity, and so on.

Of course, the computing QoS and communication QoS parameters can be adjusted separately, and they do not necessarily affect each other. In addition to the priority-ordered replaceable QoS configurations generated by the SMF, in some embodiments, the switching of computing and communication QoS configurations can also be achieved through the PDU session modification process or the AF Influence process.

Computing resource deployment and instantiation

In the embodiments of the present disclosure, computing resources may have different deployment modes. The computing resources may come from at least one of the following: a core network computing resource entity, a base station or a base station side module, a UPF, a UE, or a third-party computing resource platform. Different computing resource deployment modes may correspond to different data plane structures.

In some embodiments, the computing power resource may be implemented as a single core network functional entity, which may be referred to as a computing instance CI. Accordingly, a tunnel interface Ni may be provided between the RAN and the CI, and a tunnel interface Nii may be provided between the UPF and the CI. FIG8 shows an example processing flow for instantiating computing power resources according to an embodiment of the present disclosure.

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

Corresponding to various business scenarios, one or more of the following may be true for communication services. In some embodiments, uplink data from a 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, downlink data from a 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 a terminal device needs to be processed, and the result of the data processing needs to be returned to the terminal device. Accordingly, in order to distinguish the above-mentioned different data processing requirements, the following schemes may exist. For example, corresponding QoS flows are 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, corresponding data processing and output result forwarding rules can be set. For another example, multiple data processing requirements are mixed on a single QoS flow. Accordingly, the data packet header 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, whether the output result is transmitted to the UE or the 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). 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 the air interface resources is more closely coupled with the control unit of the computing resources. In these embodiments, the allocation and transmission operations of Tunnel information are not required. A finer QoS guarantee granularity (for example, compared to the computing granularity) can be adopted. For example, the computing 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 resources can be deployed on the UPF side, for example, as a computing function feature of the UPF. Accordingly, the functions of the CF can be incorporated into the UPF.

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

According to some embodiments, multiple terminal devices with highly overlapping or even completely identical computing and communication fusion services can be formed into a group. For example, for services such as grouping, path planning, and perception fusion in V2X scenarios, or services such as AR/VR/multi-player interactive games and live broadcasts involving multimedia, the data computing and communication requirements required by multiple terminal devices may be highly overlapping. For example, these multiple terminal devices may all need to render the same picture, and all need to perform path planning/environmental perception on the same traffic scene. Accordingly, multiple terminal devices in the same group can carry the same group ID (such as the application layer group ID, layer 2 group ID) or the computing service identifier (Computation Service Identifier) shared by the group terminal devices in the PDU session establishment/modification process (or in the registration process) to assist AMF/SMF and CF in deploying the group's common computing services to the same instantiated computing resources when allocating computing resources.

Example Method

Figure 9 shows an example method for communication according to an embodiment of the present disclosure. The method can be performed by an electronic device 400 or a corresponding network function (e.g., AMF/SMF). As shown in Figure 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 computing QoS configuration information of a communication service, and the computing QoS configuration information includes at least one of computing QoS parameters or computing QoS characteristics (box 902). The method may also include providing computing requirements of a communication service to a CF to instantiate corresponding computing resources, wherein the computing requirements are generated when the computing QoS configuration information of the communication service complies with a policy of the terminal device (box 904). Further details of the method may be understood with reference to the above description of the corresponding network function.

In one embodiment, method 900 may include receiving a PCC rule from a PCF, wherein the PCC rule contains operational QoS configuration information for a communication service, and wherein a 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 priority, computing characteristics, service identifiers, computing deployment methods, computing cache requirements, or slice numbers of computing power slices.

In one embodiment, the first request message also includes communication QoS configuration information of the communication service, and 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 computing requirements of the communication service based on the coordinated computing 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, coordination of QoS parameters or characteristics for computing and communication includes at least one of the following: determining one of the computing delay and the transmission delay relative to the other of the computing delay and the transmission delay of the communication service so that the sum of the computing delay and the transmission delay is less than or equal to a threshold level; determining one of the computing processing capacity and the communication bandwidth to match the other of the two based on the relative priority of communication and computing processing of the communication service; and monitoring the real-time QoS performance of computing and communication of the communication service based on the computing granularity.

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

In one embodiment, method 900 may include receiving information about 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 true for the communication service: 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; 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; data from the terminal device needs to be processed, and the result of the data processing needs to be returned to the terminal device.

FIG. 15 shows an example signaling process for communication according to an embodiment of the present disclosure. The signaling process 1500 can be executed between a terminal device (e.g., a UE) and a core network. As shown in FIG. 14 , at operation 1, the UE can send a computing resource registration request message to the core network (e.g., 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 resource available time period (computation resources available period), computing resource contract (e.g., charging strategy), 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 (e.g., 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. Then, at operation 2, the core network can send a computing resource registration acceptance message to the UE. In some embodiments, the above operation can be implemented by carrying the above information elements in the signaling of the registration procedure, service request procedure, etc., or can be implemented through a dedicated signaling procedure. Through the computing resource registration procedure, the computing resources of the UE can become computing resources that can be managed by the core network.

FIG. 16 shows an example signaling process for communication according to an embodiment of the present disclosure. The signaling process 1600 can be executed between a terminal device (e.g., a UE) and a core network. As shown in FIG. 15, in the case where computing power resources need to be instantiated, the CF can search for matching computing resources based on computing requirements. At operation 1, upon confirming that the computing resources that can be provided by a specific UE can match the computing requirements (including computing characteristic parameters, computing resource available time period, air interface path and other information elements), the core network can send a computing instance deployment request message to the UE to wake up the UE. Upon receiving the computing instance deployment message, at operation 2, when the computing power resources to be deployed are consistent with the resources previously registered with the core network or the resources are available, the UE returns a computing instance deployment confirmation (ACK) message to the core network. In some embodiments, the above operation can be implemented by carrying the above information elements in the signaling of a paging process, a network-triggered service request process, etc., or can be implemented by 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 the communication services of other terminal devices or users.

FIG10 shows an example method for communication according to an embodiment of the present disclosure. The method may be performed by an electronic device 400 or a corresponding network function (e.g., CF). As shown in FIG10 , the method 1000 may include receiving a computing demand for a communication service from an SMF (block 1002). The method may also include providing information about instantiated computing resources to the SMF (block 1004). Further details of the method may be understood with reference to the description of the corresponding network function above.

In one embodiment, computing power resources are instantiated based on the computing requirements of communication services, and the computing power resources come from at least one of the following: 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.

FIG11 shows an example method for communication according to an embodiment of the present disclosure. The method may be performed by the electronic device 500 or any terminal device. As shown in FIG11 , 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 computing QoS configuration information of the communication service, and the computing QoS configuration information includes at least one of computing QoS parameters or computing QoS characteristics (box 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 (box 1104). Further details of the method may be understood with reference to the description of the terminal device above.

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 the computing policy.

Figure 12A shows an example method for communication according to an embodiment of the present disclosure. The method can be performed by the electronic device 400 or the corresponding network functions (e.g., PCF and AF). As shown in Figure 12A, the method 1200 may include sending an AF requirement by the AF to the PCF, wherein the AF requirement is based on at least one of the subscription information or business scenarios of the communication service, and the AF requirement includes the operation QoS configuration information of the communication service; accordingly, the PCF receives the AF requirement from the AF (box 1202). The method may also include generating PCC rules based on the AF requirement by the PCF (box 1204). The method may also include providing PCC rules to the SMF by the PCF (box 1206). Further details of the method can be understood with reference to the description of the corresponding network functions above.

Figure 12B shows an example method for communication according to an embodiment of the present disclosure. The method can be performed by an electronic device 400 or a corresponding network function (e.g., a RAN or its base station). As shown in Figure 12B, the method 1250 may include identifying multiple data packets as belonging to the same data processing sequence by a sequence number in a data packet header, and monitoring the actual communication QoS performance of the multiple data packets (box 1252). Alternatively, the method may include identifying a specific number of data packets or multiple data packets within a specific time window as belonging to the same data processing sequence, and monitoring the actual communication QoS performance of the multiple data packets (box 1254). Further details of the method can be understood with reference to the description of the corresponding network function above.

The above describes each exemplary electronic device and method according to the embodiments of the present disclosure. It should be understood that the operations or functions of these electronic devices can be combined with each other to achieve more or less operations or functions than described. The operating steps of each method can also be combined with each other in any appropriate order to similarly achieve more or less operations than described.

It should be understood that the machine executable instructions in the machine readable storage medium or program product according to the embodiments of the present disclosure can 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 program product are clear to those skilled in the art, so they are not described repeatedly. 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 above-mentioned series of processes and devices may also be implemented by software and/or firmware.

In addition, it should be understood that the above series of processes and devices can also be implemented by software and/or firmware. In the case of implementation by software and/or firmware, the program constituting the software is installed from a storage medium or a network to a computer with a dedicated hardware structure, such as a general-purpose computer 1300 shown in FIG. 13, and the computer can perform various functions when various programs are installed. 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.

13, a central processing unit (CPU) 1301 executes various processes according to a program stored in a read-only memory (ROM) 1302 or a program 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 processes and the like is also stored as needed.

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

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, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN card, a modem, etc. The communication section 1309 performs communication processing via a network such as the Internet.

A drive 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, etc. is mounted on the drive 1310 as needed so that a computer program read therefrom is installed into the storage section 1308 as needed.

In the case where the above-described series of processing is realized by software, a program constituting the software is installed from a network such as the Internet or a storage medium such as the removable medium 1311 .

Those skilled in the art will appreciate that such storage media are not limited to the removable media 1311 shown in FIG. 13 in which programs are stored and distributed separately from the device to provide the programs to users. 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 minidiscs (MD) (registered trademark)), and semiconductor memories. Alternatively, the storage medium may be a ROM 1302, a hard disk included in the storage portion 1308, or the like, in which programs are stored and distributed to users together with the device containing them.

It should be understood that the technical solution of the present disclosure can be implemented through the following example implementations.

1. An electronic device for a network node, the electronic device comprising a processing circuit, the processing circuit being 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 operation QoS configuration information of a communication service, wherein the operation QoS configuration information includes at least one of an operation QoS parameter or an operation QoS characteristic; and

The computing requirements of the communication service are provided to the computing function CF to instantiate corresponding computing 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.

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

receiving a PCC rule from a policy control function PCF, wherein the PCC rule includes a calculation QoS configuration information of the communication service,

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

3. The electronic device of clause 1, wherein the computing QoS configuration information comprises 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.

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

Coordinating QoS parameters or characteristics for computing and communications based on both the computing QoS configuration information and the communications QoS configuration information; and

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

5. The electronic device of clause 4, wherein coordinating QoS parameters or characteristics for computing and communication comprises at least one of:

determining one of the computation delay and the transmission delay relative to the other of the computation delay and the transmission delay of the communication service so that the sum of the computation delay and the transmission delay is less than or equal to a threshold level;

determining one of the computing processing capability and the communication bandwidth to match the other of the two based on the relative priorities of the communication and computing 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. The electronic device of clause 4, wherein at least one of the operation QoS configuration information and the communication QoS configuration information is selected from a plurality of alternative sets of QoS parameters,

The multiple replaceable groups of QoS parameters are arranged or identified with priority as multiple groups of complete QoS parameters, and one group of QoS parameters is selected based on available or allocated communication resources and/or computing resources.

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

Receiving information about instantiated computing resources from the 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 is 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;

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. An 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 about computing resources that the terminal device wants to register; and send a second response message to the terminal device to indicate acceptance of the computing resource registration of the terminal device.

10. An 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 information of the computing power resources to be instantiated to the terminal device; and receive a third response message from the terminal device, the third response message including confirmation of the instantiated computing power resources by the terminal device.

11. 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, wherein the processing circuit is configured to:

Receiving computing requirements for communication services from a session management function SMF; and

Provide the SMF with information about instantiated computing resources.

12. The electronic device according to clause 11, wherein the computing resources are instantiated based on the computing requirements of the communication service, and the computing resources are 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 power resource platform.

13. An electronic device for a terminal device, comprising a processing circuit, wherein the processing circuit is configured to:

A first request message is sent 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 operation QoS configuration information of the communication service, wherein the operation QoS configuration information includes at least one of an operation QoS parameter or an operation QoS characteristic.

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

Obtaining computing requirements for the communication service; and

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

15. An 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 including information about the computing resources that the terminal device wants to register; and receive a second response message from the network, the second response message indicating that the computing resource registration is accepted.

16. An electronic device according to clause 15, wherein the processing circuit is further configured to: receive a third request message from the network, the third request message indicating information of the computing power resources to be instantiated; and send a third response message to the network, the third response message including confirmation of the instantiated computing power resources by the terminal device.

17. 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, wherein the processing circuit is configured to:

An AF requirement is sent to a policy control function PCF, wherein the AF requirement is based on at least one of subscription information or a service scenario of a communication service, and the AF requirement includes operation 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 a processing circuit, wherein the processing circuit is configured to:

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

Based on the AF requirement, generate PCC rules; and

The PCC rules are provided to the Session Management Function SMF.

19. An electronic device for a radio access network, comprising a processing circuit, the processing circuit being configured to:

Identifying multiple data packets as belonging to the same data processing sequence by using sequence numbers in data packet headers, and monitoring 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 wireless communication method, the method being used 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 computing QoS configuration information of a communication service, wherein the computing QoS configuration information includes at least one of computing QoS parameters or computing QoS characteristics; and

The computing requirements of the communication service are provided to the computing function CF to instantiate corresponding computing 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.

21. The method according to clause 20, further comprising:

receiving a PCC rule from a policy control function PCF, wherein the PCC rule includes a calculation QoS configuration information of the communication service,

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

22. A method according to clause 20, wherein the first request message further comprises communication QoS configuration information of the communication service, and the method further comprises:

Coordinating QoS parameters or characteristics for computing and communications based on both the computing QoS configuration information and the communications QoS configuration information; and

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

23. A computer-readable storage medium having executable instructions stored thereon, which when executed by one or more processors implement 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 implemented.

The exemplary embodiments of the present disclosure are described above with reference to the accompanying drawings, but the present disclosure is certainly not limited to the above examples. Those skilled in the art may obtain various changes and modifications within the scope of the appended claims, and it should be understood that these changes and modifications will naturally fall within the technical scope of the present disclosure.

For example, a plurality of functions included in one unit in the above embodiments may be implemented by separate devices. Alternatively, a plurality of functions implemented by a plurality of units in the above embodiments may be implemented by separate devices, respectively. In addition, one of the above functions may be implemented 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 flowchart include not only the processing performed in time series in the order described, but also the processing performed in parallel or individually rather than necessarily in time series. In addition, even in the steps processed in time series, it goes without saying that 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 transformations can be made without departing from the spirit and scope of the present disclosure as defined by the appended claims. Moreover, the terms "including", "comprising" or any other variants of the embodiments of the present disclosure are intended to cover non-exclusive inclusions, so that the process, method, article or equipment including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of further restrictions, the elements defined by the statement "including one..." do not exclude the presence of other identical elements in the process, method, article or equipment including the elements.

Claims (24)

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 comprises at least operational QoS configuration information of a communication service, the operational QoS configuration information comprising at least one of an operational QoS parameter or an operational QoS characteristic; and

   The computational requirements of the communication service are provided to a computational function CF to instantiate corresponding computational power resources, wherein the computational requirements are generated if the computational QoS configuration information of the communication service complies with the policies of the terminal device.
2. The electronic device of claim 1, wherein the processing circuit is further configured to:

   receiving PCC rules from a policy control function PCF, wherein the PCC rules contain operational QoS configuration information of the communication service,

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

   The power demand, the operation priority, the operation characteristic, the service identifier, the operation deployment mode, the operation cache demand or the slice number of the power slice.
4. The electronic device of claim 1, wherein the first request message further comprises communication QoS configuration information for the communication service, and the processing circuit is further configured to:

   coordinating QoS parameters or characteristics for operation and communication based on both the operation QoS configuration information and the communication QoS configuration information; and

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

   Determining one of an operational delay and a transmission delay relative to the other of the operational delay and the transmission delay of the communication service such that a sum of the operational delay and the transmission delay is less than or equal to a threshold level;

   Determining one of an arithmetic processing capability and a communication bandwidth to be matched with the other of the communication service based on a relative priority of the communication and the arithmetic processing of the communication service;

   and monitoring the operation of the communication service and the real-time QoS performance of the communication based on the operation granularity.
6. The electronic device of claim 4, wherein at least one of the operational QoS configuration information and the communication QoS configuration information is selected from a replaceable plurality of sets of QoS parameters,

   Wherein the alternative sets of QoS parameters prioritize or identify sets of complete QoS parameters and select one of the sets of QoS parameters based upon available or allocated communication resources and/or computational resources.
7. The electronic device of claim 1, wherein the processing circuit is further configured to:

   receiving information from the instantiated computing power resource of the 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 claim 1, wherein for the communication service, one or more of:

   Uplink data from the terminal equipment need to be processed, and the result of data processing needs to be transmitted to a DN/external network;

   Downlink data from the DN/external network need to be processed, and the result of the data processing needs to be transmitted to the terminal equipment;

   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 of claim 1, wherein the processing circuit is further configured to: receiving a second request message from a terminal device, wherein the second request message comprises information of 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 power resource registration of the terminal device.
10. The electronic device of claim 9, wherein the processing circuit is further configured to: sending a third request message to the terminal equipment, wherein the third request message indicates information of computing power resources to be instantiated to the terminal equipment; and receiving a third response message from the terminal device, the third response message including an acknowledgement of the instantiated computing force resource by the terminal device.
11. An electronic device for a network node, wherein the network node is configured to implement an arithmetic function CF, the electronic device comprising processing circuitry configured to:

    receiving an operation requirement of a communication service from a session management function SMF; and

    The SMF is provided with information of the instantiated computing power resource.
12. The electronic device of claim 11, wherein the computing power resource is instantiated based on an operational requirement of the communication service, and the computing power resource is from at least one of:

    a core network computing power resource entity;

    A base station or a base station side module;

    User plane function UPF;

    A UE; or (b)

    And a third party computing power resource platform.
13. An electronic device for a terminal device, comprising processing circuitry configured to:

    A first request message is sent 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 for the communication service, the operational QoS configuration information including at least one of an operational QoS parameter or an operational QoS characteristic.
14. The electronic device defined in claim 13 wherein the processing circuitry is further configured to:

    Obtaining the operation requirement of the communication service; and

    The operational requirements are mapped to operational QoS parameters and/or characteristics based on an operational policy.
15. The electronic device of claim 14, wherein the processing circuit is further configured to: sending a second request message to the network, wherein the second request message comprises information of computing power resources to be registered by the terminal equipment; and receiving a second response message from the network, the second response message indicating that the computing power resource registration is accepted.
16. The electronic device of claim 15, wherein the processing circuit is further configured to: receiving a third request message from the network, the third request message indicating information of the computing power resource to be instantiated; and sending a third response message to the network, the third response message including an acknowledgement of the instantiated computing resource by the terminal device.
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:

    An AF requirement is sent to a policy control function PCF, wherein the AF requirement is based on at least one of subscription information or traffic scenarios of a communication service, and the AF requirement comprises operational 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 comprises operational QoS configuration information of a communication service;

    Generating PCC rules based on the AF requirements; and

    The PCC rules are provided to a session management function SMF.
19. An electronic device for a radio access network, comprising processing circuitry configured to:

    Identifying a plurality of data packets as belonging to the same data processing sequence by sequence numbers in the data packet header, and monitoring the actual communication QoS performance of the plurality of data packets; or alternatively

    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 the actual communication QoS performance of the plurality of data packets is monitored.
20. 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 comprises at least operational QoS configuration information of a communication service, the operational QoS configuration information comprising at least one of an operational QoS parameter or an operational QoS characteristic; and

    The computational requirements of the communication service are provided to a computational function CF to instantiate corresponding computational power resources, wherein the computational requirements are generated if the computational QoS configuration information of the communication service complies with the policies of the terminal device.
21. The method of claim 20, further comprising:

    receiving PCC rules from a policy control function PCF, wherein the PCC rules contain operational QoS configuration information of the communication service,

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

    coordinating QoS parameters or characteristics for operation and communication based on both the operation QoS configuration information and the communication QoS configuration information; and

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