Method and device for computing power scheduling

Abstract

The invention provides a computing power scheduling method, which comprises the steps that first equipment acquires a computing power resource request, and the computing power resource request comes from an access stratum (AS), a non-access stratum (NAS) or an application layer of the first equipment; the first equipment generates computing power request information according to the computing power resource request, the computing power request information is used for requesting to allocate computing power resources to the first equipment, and wireless signaling is sent to a network side through UE, so that the network side dispatches the computing power resources to the UE according to the signaling, and computing power sharing and dispatching in the wireless network are achieved.

Description

A method and device for computing power scheduling Technical Field

[0001] The present application relates to the field of communications, and in particular, to a method and apparatus for computing power scheduling. Background Art

[0002] Cloud computing aims to integrate multiple relatively low-cost computing entities into a single, robust system through the network. A core concept of cloud computing is to continuously improve the processing power of the cloud, thereby reducing the processing burden on user terminals. Ultimately, the user terminal is reduced to a simple input and output device, enabling on-demand access to the cloud's powerful computing capabilities. The core concept of cloud computing is to centrally manage and schedule a large number of network-connected computing resources, forming a computing resource pool that provides on-demand services to users. Therefore, how to quickly and efficiently share and schedule network resources is a key issue that cloud computing must address.

[0003] With the emergence of large-scale artificial intelligence (AI) models and computing-intensive services such as extended reality (XR), single-point computing bottlenecks will gradually emerge, whether for network-side devices or terminal devices. Therefore, supporting computing power sharing in wireless networks is a future trend. For example, to address the problem of network computing bottlenecks, with the introduction of user equipment (UE) (for example, for terminals supporting different levels of autonomous driving, with different levels of computing power), UE-side terminals can be shared with the network side to assist network computing; and for XR terminals, if their own computing power is insufficient or the load is high, they can request the network to perform auxiliary computing.

[0004] To support this type of computing power sharing in wireless networks, wireless standards must support computing power sharing and define standard interfaces to support computing power requests and scheduling. Traditional communication systems (2G to 5G) only schedule and utilize connection resources. The scheduling and utilization of computing power resources are considered internal implementation issues and are not discussed in the standards. Cloud computing already supports computing power sharing and scheduling for distributed computing, but these are generally implemented and deployed in cloud networks based on fixed networks. For example, for multiple computing nodes, a unified centralized control node is generally used to centrally manage and schedule each computing node.

[0005] Cloud networks support simple computing power sharing and scheduling, but their fixed network-based methods cannot be reused in wireless networks. In particular, computing power sharing and scheduling for air interfaces require special design, which is not supported by existing technical solutions.

[0006] Summary of the Invention

[0007] The present application provides a method and apparatus for computing power scheduling. For scenarios where a UE has computing power and the network centrally controls and schedules the UE's computing power, or where the network has computing power and the UE requests computing power from the network to assist the UE in performing calculations, the UE sends wireless signaling to the network side, so that the network side schedules computing power resources to be allocated to the UE based on the signaling, thereby realizing computing power sharing and scheduling in a wireless network.

[0008] In a first aspect, a method for computing power scheduling is provided. The method can be executed by an electronic device, or can be executed by a chip or circuit configured in the electronic device, and this application does not limit this.

[0009] The method includes: a first device obtains a computing power resource request, wherein the computing power resource request comes from the access layer AS, non-access layer NAS or application layer of the first device; the first device generates computing power request information according to the computing power resource request, and the computing power request information is used to request the allocation of computing power resources for the first device.

[0010] It should be understood that the electronic device in this application may be a terminal device or a network device.

[0011] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: the first device sends the computing power request information, and the sending method of the computing power request information includes AS signaling or NAS signaling, and the AS signaling includes a scheduling request SR, a random access channel RACH, a cache status report BSR and a radio resource control RRC signaling.

[0012] In one possible implementation, the computing power request information includes first parameter information, which includes one or more of a quality of service QoS parameter, a resource location parameter, and a resource size parameter of the computing power resource requested by the first device.

[0013] In one possible implementation, the method further includes: the first device receives allocation result information, and the allocation result information is used to indicate the allocation result of the computing power resources requested by the computing power request information, and the allocation result includes all allocation success, all allocation failure or partial allocation success.

[0014] In one possible implementation, the method also includes: the first device receives computing power configuration information, the computing power configuration information includes configuration information of computing power resources allocated by the network device to the first device, and the computing power resources allocated by the network device to the first device include computing power resources of the first device and the network device.

[0015] In one possible implementation, the first device generates computing power request information based on the computing power resource request, including: when preset parameters meet corresponding preset conditions, the first device generates the computing power request information based on the computing power resource request, and the preset parameters include at least one of the following parameters: the detection result of periodic detection of whether there is a computing power resource request, the total amount of computing power resources requested by the computing power resource, the number of computing power resource requests, the minimum delay of the computing power resource request, and the minimum value of the remaining delay of the computing power resource request.

[0016] In one possible implementation, when the computing power resource request is canceled, the method further includes: if the computing power request information has not been sent, the first device cancels sending the computing power request information; if the computing power request information has been sent, the first device generates and sends a cancellation request information, and the cancellation request information is used to request the cancellation of the allocation of the first computing power resource, and the first computing power resource is all or part of the computing power resources requested to be allocated by the computing power request information.

[0017] In a possible implementation, the computing power resource request is a computing power resource request from a first business, and the method further includes: determining a sending method of the computing power request information according to an identification ID of the first business.

[0018] In one possible implementation, the method further includes: determining a method for sending the computing power request information based on a QoS requirement of the computing power resources corresponding to the computing power resource request.

[0019] In a possible implementation, the computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device is only allowed to be used by part of the services.

[0020] In a possible implementation, the method further includes: the first device obtaining multiple computing power resource requests; and the first device generating the computing power request information according to the multiple computing power resource requests.

[0021] On the second aspect, a method for computing power scheduling is provided. The method can be executed by a network device, or can also be executed by a chip or circuit configured in the network device, and this application does not limit this.

[0022] The method includes: a network device receives computing power request information, wherein the computing power request information is used to request the allocation of computing power resources to a first device; the network device determines allocation result information, wherein the allocation result information is used to indicate the allocation result of the computing power resources requested to be allocated by the computing power request information, wherein the allocation result includes all allocation success, all allocation failure or partial allocation success; and the network device sends the allocation result information.

[0023] In one possible implementation, the computing power request information includes first parameter information, which includes one or more of a quality of service QoS parameter, a resource location parameter, and a resource size parameter of the computing power resource requested by the first device.

[0024] In one possible implementation, the method further includes: determining computing power configuration information, the computing power configuration information including configuration information of computing power resources allocated by the network device to the first device, the computing power resources allocated by the network device to the first device including computing power resources of the first device and the network device; the network device sends the computing power configuration information.

[0025] In a possible implementation, the computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device is only allowed to be used by part of the services.

[0026] According to a third aspect, a communication device is provided, including: a processing module for obtaining a computing power resource request, wherein the computing power resource request comes from the access layer AS, non-access layer NAS or application layer of a first device; the processing module is also used to generate computing power request information based on the computing power resource request, and the computing power request information is used to request the allocation of computing power resources for the first device.

[0027] In one possible implementation, the device also includes: a sending module for sending the computing power request information, wherein the sending method of the computing power request information includes AS signaling or NAS signaling, and the AS signaling includes a scheduling request SR, a random access channel RACH, a cache status report BSR or a radio resource control RRC signaling.

[0028] In one possible implementation, the device also includes: a receiving module for receiving allocation result information, wherein the allocation result information is used to indicate the allocation result of the computing power resources requested by the computing power request information, and the allocation result includes all allocation success, all allocation failure or partial allocation success.

[0029] In one possible implementation, the receiving module is also used to receive computing power configuration information, wherein the computing power configuration information includes configuration information of computing power resources allocated by the network device to the first device, and the computing power resources allocated by the network device to the first device include computing power resources of the first device and the network device.

[0030] In one possible implementation, the processing module is also used to generate computing power request information based on the computing power resource request, including: when the preset parameters meet the corresponding preset conditions, the processing module is also used to generate the computing power request information based on the computing power resource request, and the preset parameters include at least one of the following parameters: the detection result of periodic detection of whether there is a computing power resource request, the total amount of computing power resources requested by the computing power resource, the number of computing power resource requests, the minimum delay of the computing power resource request, and the minimum value of the remaining delay of the computing power resource request.

[0031] In one possible implementation, when the computing power resource request is canceled, if the computing power request information has not been sent, the sending module cancels the sending of the computing power request information; if the computing power request information has been sent, the processing module is also used to generate a cancellation request information, and the sending module is also used to send the cancellation request information, and the cancellation request information is used to request the cancellation of the allocation of the first computing power resource, which is all or part of the computing power resources requested to be allocated by the computing power request information.

[0032] In a possible implementation, the computing power resource request is a computing power resource request from a first business, and the sending module is further used to determine a sending method of the computing power request information according to an identification ID of the first business.

[0033] In a possible implementation, the sending module is further used to determine a method for sending the computing power request information based on the QoS requirements of the computing power resources corresponding to the computing power resource request.

[0034] In a possible implementation, the computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device is only allowed to be used by part of the services.

[0035] In a possible implementation, the processing module obtains multiple computing power resource requests and generates the computing power request information according to the multiple computing power resource requests.

[0036] In a fourth aspect, a communication device is provided, including: a receiving module for receiving computing power request information, wherein the computing power request information is used to request the allocation of computing power resources to a first device; a processing module for determining allocation result information, wherein the allocation result information is used to indicate the allocation result of the computing power resources requested to be allocated by the computing power request information, wherein the allocation result includes all allocation success, all allocation failure or partial allocation success; and a sending module for sending the allocation result information.

[0037] In one possible implementation, the processing module is also used to determine computing power configuration information, the computing power configuration information includes configuration information of computing power resources allocated by the network device to the first device, and the computing power resources allocated by the network device to the first device include the computing power resources of the first device and the network device; the sending module is also used to send the computing power configuration information.

[0038] In a possible implementation, the computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device is only allowed to be used by part of the services.

[0039] In a fifth aspect, a communication device is provided, comprising modules or units for executing the method in the first aspect or any possible implementation of the first aspect.

[0040] In a sixth aspect, a communication device is provided, comprising modules or units for executing the method in the second aspect or any possible implementation of the second aspect.

[0041] In a seventh aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute instructions in the memory to implement the method of the first aspect and possible implementations thereof. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0042] In one implementation, the communication device is a terminal device or a network device. When the communication device is a terminal device or a network device, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0043] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0044] In an eighth aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute the method of the second aspect and possible implementations thereof. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface. In another possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface.

[0045] In one implementation, the communication device is a network device. When the communication device is a network device, the communication interface may be a transceiver or an input / output interface.

[0046] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0047] In a ninth aspect, a communication device is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, so that the method of any one of the first or second aspects, and any possible implementation of any of the above aspects, is implemented.

[0048] In a specific implementation, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. The input circuit and the output circuit may be different circuits or the same circuit, in which case the circuit functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0049] In a tenth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter to execute the method of any one of the first or second aspects, and any possible implementation of the aforementioned aspects.

[0050] In a possible implementation, there are one or more processors and one or more memories.

[0051] In a possible implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0052] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0053] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, the output data of the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0054] The processor in the above aspects can be a chip, which can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or located outside the processor and exist independently.

[0055] In the eleventh aspect, a processing device is provided, comprising a communication interface and a processing circuit, wherein the communication interface is used to obtain data to be processed, and the processing circuit is used to process the data to be processed according to the method in any possible implementation of the first aspect.

[0056] In the twelfth aspect, a processing device is provided, comprising: a communication interface and a processing circuit, wherein the communication interface is used to send indication information according to the method in any possible implementation of the second aspect, and the processing circuit is used to generate the indication information.

[0057] In the thirteenth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when run, enables a computer to execute any one of the first or second aspects, as well as a method in any possible implementation of the above aspects.

[0058] In the fourteenth aspect, a computer-readable medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute any of the first or second aspects mentioned above, as well as any possible implementation of the above aspects.

[0059] In the fifteenth aspect, a chip system is provided, comprising a memory and a processor, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a communication device equipped with the chip system executes the methods in any of the above-mentioned aspects 1 to 2 and their possible implementation methods.

[0060] Among them, the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0061] In a sixteenth aspect, a communication system is provided, comprising the aforementioned network device and electronic device.

[0062] In one possible design, the communication system may also include other devices that interact with the communication device in the solution provided in the embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] FIG1 is a schematic diagram of an example of a communication system according to the method of the present application.

[0064] FIG2 is a schematic diagram of an example of a communication system architecture of the method of the present application.

[0065] FIG3 is a schematic diagram of a communication method of the present application.

[0066] FIG4 is a schematic flow chart of a communication method of the present application.

[0067] FIG5 is a schematic diagram of a communication model provided in this application.

[0068] FIG6 is a schematic diagram of a request information format provided by this application.

[0069] FIG7 is a schematic diagram of a method for selecting sending resources provided in this application.

[0070] FIG8 is a schematic diagram of a communication model provided in this application.

[0071] FIG9 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0072] FIG10 is a schematic block diagram of another communication device provided in an embodiment of the present application.

[0073] FIG11 is a schematic block diagram of an electronic device provided in an embodiment of the present application.

[0074] FIG12 is a schematic block diagram of a network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] The technical solution in this application will be described below with reference to the accompanying drawings.

[0076] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, machine to machine (M2M) system, non-terrestrial network (NTN) system, the 5th Generation (5G) system or New Radio (NR) system or other future wireless communication systems.

[0077] As shown in Figure 1, the communication system may include at least one network device, such as the network device shown in Figure 1; the communication system may also include at least one terminal device, such as the terminal device shown in Figure 1. The network device and the terminal device may communicate via a wireless link. In the communication system, the network device and the terminal device may wirelessly communicate using air interface resources, which may include at least one of time domain resources, frequency domain resources, code resources, and space resources.

[0078] The terminal device in the embodiments of the present application may refer to a user device, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., and the embodiments of the present application are not limited thereto.

[0079] Wearable devices, also known as wearable smart devices, are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0080] User equipment (UE) is a mobile station that can be vehicle-mounted, portable, or handheld. The physical device and mobile user are completely independent. All user information can be stored on a smart card (SIM card), which can be used on the mobile station. The terminal can directly interact with the base station over the air interface. The terminal can send and / or receive signals.

[0081] Furthermore, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people, machines, and things.

[0082] It should be understood that this application does not limit the specific form of the terminal device.

[0083] The network device in the embodiment of the present application can also be a device for communicating with a terminal device. The network device can be a base station (Base Transceiver Station, BTS) in a Global System of Mobile communication (GSM) system or a Code Division Multiple Access (CDMA), or a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station (Evolved NodeB, eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G network, or a network device in a future evolved PLMN network, etc., and the embodiment of the present application is not limited.

[0084] It should be understood that the network device in the wireless communication system can be any device with wireless transceiver functions. The device includes, but is not limited to, an evolved Node B (eNB), a radio network controller (RNC), a road side unit (RSU), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B, or home node B, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It may also be a gNB or a transmission point (TRP or TP) in a 5G (such as NR) system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DPU). unit, DU), etc. The network device can also be a network-side device in the Internet of Vehicles that provides communication services or communication control for terminal devices.

[0085] The network device provides communication services for the terminal devices in the cell. The terminal devices in the cell communicate with the network device through the transmission resources allocated by the network device (for example, frequency domain resources, time domain resources, etc.). The cell may belong to a macro base station (for example, a macro eNB or a macro gNB, etc.).

[0086] As shown in Figure 2, the communication system architecture to which this application is applicable may include base stations, terminal equipment, core networks, external networks, etc.

[0087] Core Network: As the core component of the mobile communications network, the core network plays a connecting role, primarily responsible for handling end-user mobility management, session management, and data transmission (core functions). The 5G core network has three new enhancements based on the EPC: a service-based architecture, support for network slicing, and separation of the control and user planes. Compared to the 4G core network, the 5G core network further evolves toward a separated architecture. First, the separation of network functions incorporates the design principles of NFV cloud native and builds the network in a software-based, modular, and service-oriented manner. Second, the separation of the control and user planes frees user plane functions from the constraints of "centralization," allowing them to be flexibly deployed in both the core network and the access network.

[0088] The core network's primary functions are providing user connections, user management, and service bearer services. As a bearer network, it provides an interface to external networks. Establishing user connections includes functions such as mobility management (MM), call management (CM), switching / routing, and recorded notifications (integrated with intelligent network services to establish connections to intelligent network peripheral devices). User management includes user profiling, QoS (including descriptions of user service QoS), user communication logging (accounting), VHE (virtual home environment) (interactions with the intelligent network platform provide a virtual home environment), and security (security measures provided by the authentication center include security management of mobile services and security processing for access to external networks). Bearer connections include access to the external PSTN (Public Switched Telephone Network), external circuit and packet data networks, the Internet (Internet), intranets (intranets), and the mobile phone's own SMS (Short Message Service) server. The basic services that the core network can provide include mobile office, e-commerce, communications, entertainment services, travel and location-based services, telemetry services, simple messaging services (monitoring and control), etc.

[0089] Simply put, a mobile network can be divided into three parts: the base station subsystem, the network subsystem, and system support components such as security management. The core network, located within the network subsystem, primarily connects call and data requests received over the air interface to different networks.

[0090] External network: Operators or network management systems, such as the Public Land Mobile Network (PLMN), are networks established and operated by the government or operators approved by it to provide land mobile communications services to the public. Examples include China Mobile, China Unicom, and China Telecom.

[0091] In the embodiments of the present application, the terminal device is wirelessly connected to the radio access network (RAN) equipment, and the RAN network element is wirelessly or wiredly connected to the core network equipment. The core network equipment and the RAN network element can be independent and distinct physical devices, or the functions of the core network device and the logical functions of the RAN network element can be integrated into the same physical device, or a single physical device can integrate some of the functions of the core network device and some of the functions of the RAN network element. The terminal can be fixed or mobile.

[0092] As shown in Figure 3, a terminal may include the physical layer (PHY), the medium access control (MAC) layer, the radio link control (RLC) layer, the packet data convergence protocol (PDCP), the radio resource control (RRC), and the service data adaptation protocol (SDAP). The terminal may also include user plane protocols and control plane protocols. A base station may also include user plane protocols and control plane protocols. The various layers of the terminal and base station may be interconnected to exchange information.

[0093] The present application provides a method and apparatus for computing power scheduling. For scenarios where a UE has computing power and the network centrally controls and schedules the UE computing power, or where the network has computing power and the UE requests computing power from the network to assist the UE in performing calculations, the UE sends wireless signaling to the network side, so that the network side schedules computing power resources to be allocated to the UE based on the signaling, thereby realizing computing power sharing and scheduling in a wireless network.

[0094] It should be understood that the description of the specific scenarios in the embodiments of the present application is only an example. In addition to being applicable to the application scenarios described above, the methods provided in the embodiments of the present application are also applicable to application scenarios with similar problems.

[0095] In the description of the embodiments of the present application, unless otherwise specified, "a plurality of" or "a plurality of" means two or more. In addition, "at least one" can be replaced by "one or more".

[0096] The technical solutions provided in the embodiments of this application can be applied to wireless communications between communication devices. Wireless communications between communication devices may include: wireless communications between network devices and terminals, wireless communications between network devices, and wireless communications between terminals. In the embodiments of this application, the term "wireless communications" may also be referred to as "communication," which may also be described as "data transmission," "information transmission," or "transmission."

[0097] It should be understood that the names of all nodes and messages in this application are merely names set for the convenience of description in this application. The names in the actual network may be different. This application should not be understood as limiting the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as a method or equivalent replacement of this application, and is within the scope of protection of this application. No further details will be given below.

[0098] The following describes in detail various uplink scheduling methods provided by the embodiments of the present application with reference to the accompanying drawings.

[0099] FIG4 shows a method 300 for computing power scheduling provided in the present application. The method in FIG4 includes at least part of the following contents.

[0100] S310, the UE (ie, an example of the first device) obtains a computing power resource request and generates computing power request information according to the computing power resource request.

[0101] S320, the UE sends computing power request information to the network device, where the computing power request information is used to request allocation of computing power resources for the UE.

[0102] S330, the network device determines allocation result information and computing power configuration information, where the allocation result information is used to indicate the allocation status of computing power resources.

[0103] S340, the network device sends allocation result information and computing power configuration information to the UE.

[0104] S310-S340 are described in detail below.

[0105] In S310 , the UE obtains a computing power resource request and generates computing power request information according to the computing power resource request.

[0106] First, the new computing power model provided by this application is introduced.

[0107] In the traditional communication model, the application layer maps the data packets to be sent to different data radio bearers (DRBs). Each DRB is mapped to a logical channel (LCH) (1:N mapping for packet duplication and 1:1 mapping for non-duplication). The UE's MAC layer counts the amount of buffered data in each logical channel group (LCG) and reports it to the network via Buffer Status Report (BSR) signaling in the form of an LCG. (Because each LCH must be reported separately according to the LCH, the signaling overhead is high. Therefore, LCHs with similar quality of service (QoS) requirements are grouped into an LCG. An LCG only reports the size of one buffered data volume, saving signaling overhead.)

[0108] QoS requirements refer to the need for QoS levels. QoS is a network technology used to manage and optimize network traffic to ensure that different applications and services on the network receive appropriate quality of service guarantees, such as bandwidth, latency, and packet loss. QoS levels refer to the priorities of different applications and services. That is, different traffic on the network has different processing priorities and service quality requirements. Therefore, different QoS levels need to be assigned to them to ensure that their transmission and processing within the network receive the appropriate priority and guarantees. QoS levels are generally divided into multiple levels, such as high, medium, and low, or more. The higher the level, the higher the network service quality requirements of the application or service, requiring higher priority and bandwidth guarantees.

[0109] For computing power requests, the existing communication model cannot be directly reused because computing power request messages do not correspond to specific packets, and the MAC layer cannot infer the size of the computing power request by summarizing the cached packet size of the computing power request message. Therefore, a new computing power model needs to be designed. As shown in Figure 5, the new computing power model is divided into two layers. The upper layer corresponds to the application (Application, APP) or 3GPP layer, which is the requester of computing power resources. The 3GPP layer can specifically be the Non-Access Stratum (NAS) layer or the Access Stratum (AS). The lower layer corresponds to the RRC or MAC layer, which is the computing power resource request message layer. This layer aggregates the computing power requests of various services (Services) / tasks (Tasks) and sends the corresponding computing power resource request messages to the network side. The sending methods include RRC / MAC / Scheduling Request (SR) / Random Access Channel (RACH) methods.

[0110] In addition, for multiple computing power requests for the same business (APP / Service / Task, taking APP as an example), or different computing power requests for different APPs, this layer can merge or not merge; merging means summing up multiple computing power requests and sending one message, that is, multiple computing power requests correspond to one total computing power request information, and the total computing power requirement is carried in one computing power request information. Not merging means sending multiple messages for multiple computing power requests, that is, multiple computing power requests correspond to multiple computing power request information, and each computing power request information carries the computing power requirement of each computing power request.

[0111] In traditional communications networks, when multiple UEs transmit data simultaneously within the same network device, different services have varying latency requirements. Some UE services are latency-sensitive (such as URLLC services), while others are latency-insensitive (such as eMBB services). Latency sensitivity refers to UE services that place high demands on network transmission latency, requiring data transmission and processing to be completed in a relatively short period of time. For example, services such as live video streaming and online gaming are latency-sensitive. Excessive network transmission latency can negatively impact the user experience and even disrupt normal service operations.

[0112] Therefore, since different services have different latency requirements, i.e., different services have different QoS priorities, computing resource requests include not only requirements for computing resource size and location, but also QoS requirements.

[0113] In one possible implementation, the UE obtains one or more computing resource requests from one or more services, where the computing resource requests include at least one of computing resource size, computing resource location, and QoS requirement.

[0114] Specifically, when a computing power request information is generated based on a computing power resource request, corresponding to the case where the RRC / MAC layer does not merge the computing power resource requests, the computing power resource request corresponds to one computing power request information.

[0115] When one computing power request information is generated based on multiple computing power resource requests, corresponding to the situation where the RRC / MAC layer merges the computing power resource requests, multiple computing power resource requests correspond to one computing power request information.

[0116] The following uses the Computing Buffer Status Report (C-BSR) as an example to introduce several formats of computing power request information.

[0117] When the RRC / MAC layer does not merge computing resource requests, one computing resource request corresponds to one C-BSR. In this case, it can be reported per service / task, supporting both long and short formats.

[0118] Short format: As shown in Figure 6, only the computing power requirements of one service are reported at a time, that is, one C-BSR corresponds to the computing power requirements of one service. In this case, the C-BSR can carry the following fields: service ID and computing power resource size.

[0119] In a possible implementation, the C-BSR may also carry a "delay requirement," where the delay requirement is a QoS level requirement of the service corresponding to the C-BSR.

[0120] Long format: As shown in Figure 6, the computing power requirements of multiple services can be reported at once, that is, one C-BSR corresponds to the computing power requirements of multiple services. In this case, the C-BSR can carry the following fields: service ID bitmap, the amount of computing power resources requested for each service ID.

[0121] In a possible implementation, the C-BSR may also carry a "delay requirement," where the delay requirement is a QoS level requirement of multiple services corresponding to the C-BSR.

[0122] When "latency requirement" is carried, different latency requirements for requests of different computing resources with the same service ID can be allowed. When "latency requirement" is not carried, different latency requirements for the same service ID cannot be distinguished, or the network defaults to similar latency requirements for computing resource requests with the same service ID.

[0123] When the RRC / MAC layer merges computing power resource requests, multiple computing power resource requests correspond to one computing power request information. In this case, they can be reported according to service groups (service / task groups), and both long / short formats are supported. Each service group includes one or more services.

[0124] Short form: Reports the computing power requirements of only one business group at a time. That is, one C-BSR corresponds to the computing power requirements of one business group. Replace the business ID field with the business group ID field, similar to the case of not merging computing power resource requests.

[0125] In a possible implementation, the C-BSR may also carry a "delay requirement," where the delay requirement is a QoS level requirement of the service corresponding to the C-BSR.

[0126] Long format: Multiple business groups can report their computing power requirements at once, meaning one C-BSR corresponds to the computing power requirements of multiple business groups. In this case, the C-BSR may carry the following fields: a business group ID bitmap and the amount of computing power requested for each business group ID.

[0127] In a possible implementation, the C-BSR may also carry a "delay requirement," where the delay requirement is a QoS level requirement of multiple service groups corresponding to the C-BSR.

[0128] When the "latency requirement" is included, different latency requirements for different computing resources in the same business group ID can be allowed. If the "latency requirement" is not included, different latency requirements for the same business group ID cannot be distinguished, or the network defaults to similar latency requirements for computing resources requested with the same business group ID.

[0129] In a possible implementation, which services the UE groups into a service group needs to be pre-configured by the network. For example, the network configures a mapping relationship between services and service groups for the UE.

[0130] In S320, the UE sends computing power request information to the network device, where the computing power request information is used to request allocation of computing power resources for the UE.

[0131] In an embodiment of the present application, the computing power request information can be RRC layer information (such as RRC signaling, etc.) or MAC layer information (such as BSR, etc.). When both RRC and MAC methods of requesting computing power are supported at the same time, how the UE chooses which method is a problem that needs to be solved in the embodiment of the present application.

[0132] Specifically, the network side may pre-configure application conditions of different request methods for the UE (via broadcast signaling such as a Master Information Block (MIB) / System Information Block (SIB), or RRC dedicated signaling, etc.).

[0133] In one possible implementation, since the transmission delay of the MAC method is smaller than that of the RRC method, the MAC method can be used for emergency services and the RRC method can be used for non-emergency services. Specifically, the following two methods are included.

[0134] Method 1: The method for sending the computing power request information is determined based on the service ID. For example, when the QoS requirements of a service are fixed, the network configures the UE with a mapping between the service ID and the computing power request information reporting method. For example, service 1 corresponds to RRC signaling, service 2 corresponds to MAC CE, and so on.

[0135] Method 2: Determine the method of sending the computing power request information based on the QoS requirement of the computing power resources corresponding to the computing power resource request, including: when the QoS requirement of the computing power resources is higher than the preset value, sending the computing power request information through RRC signaling; when the QoS requirement of the computing power resources is lower than the preset value, sending the computing power request information through MAC signaling.

[0136] When the QoS requirements for different computing resource requests within a service vary significantly, the network configures a latency threshold for the UE. For example, when the latency requirement is less than the latency threshold, the computing request is sent via MAC layer information; otherwise, it is sent via RRC layer information. In this case, when the latency requirements for different computing resource requests within the same service vary significantly, different forms of computing request information can be used for reporting.

[0137] There are two types of computing resources that the UE requests from the network: one-time computing power and periodic computing power. The request message for different types of computing power resources carries the following parameter information (i.e., the first parameter information):

[0138] 1) One-time computing resources

[0139] When the computing power resources requested by the UE from the network are one-time computing power resources, the computing power request information may carry one or more of the following parameters (QoS parameters, resource location parameters, and resource size parameters).

[0140] a) QoS parameters

[0141] QoS parameters include delay requirements (referring to computing delay requirements), reliability requirements (referring to computing QoS requirements), etc.

[0142] It should be understood that both latency requirements and computational latency requirements are related to time, but have different meanings.

[0143] Latency requirements refer to the time required for data to be sent from the sender to the receiver in a communication system. This includes transmission delay, processing delay, and queuing delay. Latency requirements vary across different communication scenarios. For example, VoIP calls require real-time communication within tens of milliseconds, while email latency can be within minutes or even hours.

[0144] Computing latency refers to the time required from receiving a request to returning a response in a computing system, including processing, storage, and transmission time. Different computing application scenarios have different computing latency requirements. For example, high-frequency trading requires computations to be completed within milliseconds or microseconds, while cloud gaming requires computations within tens of milliseconds.

[0145] Therefore, both latency requirements and computational latency requirements are time metrics, but they target different objects and application scenarios. Latency requirements primarily concern communication systems, while computational latency requirements primarily concern computing systems.

[0146] Similarly, QoS requirements and computational QoS requirements are both related to quality of service, but their meanings are different.

[0147] QoS requirements refer to the different processing priorities and service quality requirements of different applications and services on the network. Therefore, different QoS levels need to be assigned to them to ensure that their transmission and processing within the network are prioritized and guaranteed accordingly. QoS requirements vary in different network application scenarios. For example, VoIP calls require high priority and low latency, while file downloads require low priority and high bandwidth.

[0148] Computing QoS requirements refer to the fact that different applications and services within a computing system have different processing priorities and service quality requirements. Therefore, it is necessary to allocate different computing resources and service quality assurance to different applications and services based on their characteristics and user needs to ensure computing system performance and user experience. Computing QoS requirements vary across different computing application scenarios. For example, high-frequency trading requires fast response times and high concurrency, while big data analysis requires high fault tolerance and high-performance computing capabilities.

[0149] Therefore, QoS requirements and computing QoS requirements are both indicators for measuring service quality, but they target different objects and application scenarios. QoS requirements mainly involve network systems, while computing QoS requirements mainly involve computing systems.

[0150] b) Resource location parameters

[0151] The resource location parameter may include one or more of the following parameters: such as start time, CPU ID, CPU type (such as CPU / NPU / GPU, etc.).

[0152] The start time of computing resources refers to the time when the computing resources become available. If the computing resources start time is too late, tasks may not be completed on time, thus affecting the normal operation of the business. On the other hand, if the computing resources start time is earlier, the completion efficiency of computing tasks can be improved, the execution time can be shortened, and the efficiency and profitability of the business can be improved. Therefore, when requesting and allocating computing resources, it is necessary to consider the availability of computing resources to properly plan and allocate computing tasks.

[0153] c) Resource size parameters

[0154] The resource size parameter may be any one of parameters such as the amount of computation and duration. It should be understood that the specific type of the resource size parameter may be flexibly adjusted according to the specific scenario.

[0155] The resource size can be expressed as computing duration (computing duration = computing amount / computing capability), such as xx milliseconds; or the resource size can be expressed as computing amount, such as xx flops.

[0156] Note: flops stands for "floating-point operations per second" or "peak speed per second", which is the abbreviation of "floating-point operations per second".

[0157] 2) Periodic computing resources

[0158] When the computing power resources requested by the UE from the network are periodic computing power resources, the computing power request information may carry one or more of the following parameters (QoS parameters, resource location parameters, and resource size parameters).

[0159] a) QoS parameters

[0160] The same one-time computing resources include latency requirements (referring to computing latency requirements) and reliability requirements (referring to computing QoS requirements).

[0161] b) Resource location parameters

[0162] In addition to the same parameters as the one-time computing power resources, such as the start time, CPU ID, CPU type, etc., additional descriptive parameters of periodic attributes (such as the cycle size, the total number of cycles, etc.) are required.

[0163] c) Resource size parameters

[0164] The resource size parameter of the periodic computing power resource corresponds to the size of each resource in the periodic resource. The resource size parameter can be any one of the parameters such as the computing amount and duration. It should be understood that the specific type of the resource size parameter can be flexibly adjusted according to the specific scenario.

[0165] In an embodiment of the present application, there is a triggering and cancellation mechanism for the UE to send computing power request information. The triggering and cancellation mechanism of C-BSR is introduced below using the computing power request information as C-BSR as an example.

[0166] Trigger mechanism:

[0167] The C-BSR report can be triggered periodically or by events.

[0168] For periodic triggering, the UE periodically checks whether there is a computing power resource request. When there is a computing power resource request, it sends the computing power request information. Specifically, the network can configure the C-BSR trigger period and / or start time for the UE (such as 10ms as a period, starting at 0ms). The UE side will then start the corresponding timer and check every 10ms whether there is a need to send a C-BSR (if there is a computing power request primitive passed down from the upper layer, it is considered that there is a demand; otherwise, there is no demand). If there is no demand, no C-BSR is sent.

[0169] For event triggering, the network can configure the C-BSR triggering conditions for the UE. The UE MAC layer will then detect when the event meets the sending conditions and trigger the sending of the C-BSR when it meets the conditions. Otherwise, it will not be triggered. The event can be any combination of the following conditions:

[0170] 1) The total amount of computing power resource requests is greater than the first value;

[0171] 2) The number of computing resource requests is greater than the second value;

[0172] 3) The minimum latency of computing resource requests is less than the third value;

[0173] 4) The lowest value of the remaining latency of the computing resource request is less than the fourth value.

[0174] It should be understood that the first value, the second value, the third value and the fourth value are preset values ​​pre-configured by the network for the UE.

[0175] Cancellation mechanism:

[0176] Scenario 1: When a UE has previously requested computing power and no longer has this demand, but the previous C-BSR has been generated and sent or has not been sent to the network (this is because sending a C-BSR also requires the network to schedule uplink transmission resources for the UE. If the UE is not scheduled in time, the C-BSR cannot be sent in time), then it is necessary to promptly notify the network that there is no such demand.

[0177] Scenario 2: When the UE has a computing power request and has notified the lower layer and generated a corresponding C-BSR (sent or not), but the network has allocated computing power resources to the UE through pre-judgment or reservation, the generated C-BSR (sent or not) needs to be canceled.

[0178] The following discusses the two cases where the C-BSR has been sent or not:

[0179] 1) C-BSR not sent: For the above-mentioned C-BSR method of not merging computing resource requests (1:1 mapping of computing resource requests and computing request information), directly cancel the C-BSR. For the above-mentioned C-BSR method of merging computing resource requests (N:1 mapping of computing resource requests and computing request information), there are two ways to do this: a) directly update the total demand, generate the latest C-BSR, and delete the previous C-BSR; b) do not directly cancel the old C-BSR, but generate another C-BSR and carry the canceled demand amount (for example, marked by a negative value).

[0180] 2) C-BSR has been sent: At this time, a canceled C-BSR can be generated (for example, a negative value is used to indicate the amount of canceled computing resources).

[0181] In the above embodiment, a solution is provided in which the UE applies for computing power resources from the network through computing power request information in the form of RRC signaling or MAC CE (such as C-BSR).

[0182] When MAC CE is used to request computing power from the network, a C-BSR is required. However, the C-BSR can only be sent if the UE has uplink transmission resources allocated by the network (i.e., a UL grant). Sometimes, the UE does not have a UL grant, so a C-BSR cannot be sent. In this case, a corresponding mechanism is required for the UE to first notify the network that it has uplink data to send. In existing communication networks, this is achieved through the Scheduling Request (SR) mechanism.

[0183] In existing networks, SR is a resource on the Physical Uplink Control Channel (PUCCH) and is pre-configured by the network to the UE (for example, periodically). When the UE has uplink data to send but no UL grant, it first triggers SR to inform the network. The network then allocates a small UL grant to the UE for the transmission of MAC CE (such as BSR) to inform the UE how much data to send. After receiving the BSR sent by the UE, the network allocates the corresponding UL grant based on the specific data volume. The UE then uses the secondary allocated UL grant to send uplink data.

[0184] However, at certain times, there are no SR resources on the UE side (this is because configuring SR resources is optional and the network is not forced to configure them for the UE), or the SR resources on the UE side have expired (for example, the SR resources configured by the network for the UE are time-limited, such as valid within 100ms; or the UE has lost uplink synchronization. At this time, even if there are valid SR resources, they cannot be used). At this time, the UE can only notify the network through random access.

[0185] In view of the above description, in existing communication systems, the UE reports uplink data transmission capacity to the network in three ways: BSR (such as C-BSR), SR, and RACH. The priority order is: BSR takes precedence over SR and RACH, as shown in Figure 7.

[0186] The following describes how the UE requests computing resources from the network through SR.

[0187] For sending computing power request information, existing SR resources used for data transmission can be used, or dedicated SR resources can be allocated for computing power request information.

[0188] In one possible implementation, computing power requests can be made through existing SR resources used for data transmission, that is, computing power requests and data transmission requests share one or more sets of SR resources. When the UE sends computing power request information to the network side through SR, the specific QoS level and / or request type (such as computing power request or UL grant request) can be carried in the SR, so that the network side knows that the request sent by the UE is a computing power request and a specific QoS level.

[0189] In another possible implementation, to facilitate the network's understanding that the request carried by the SR resource is a computing power request rather than a data transmission request, a dedicated set of SR resources can be allocated for computing power request information. These dedicated SR resources are distinct from ordinary data transmission SR resources and are used only for computing power requests and not for any other purpose. When the UE sends computing power request information using these dedicated SR resources, the network can determine from these dedicated SR resources that the request sent by the UE is a computing power request.

[0190] In another possible implementation, different services of the same UE may have different QoS priorities for computing power requests. In the above solution, the network side can learn that the request sent by the UE is a computing power request through a dedicated SR resource, but cannot obtain the QoS priority of the computing power request through the dedicated SR resource. In order to enable the network side to distinguish computing power requests with different QoS requirements, multiple sets of dedicated SR resources can be configured for the UE, and different SR resources can be used to correspond to computing power requests with different QoS requirements.

[0191] For multiple computing power requests for the same business ID, as shown in Figure 8, there are two different modeling methods:

[0192] 1) Model 1: The QoS requirements of different computing power requests for the same service ID are similar / identical;

[0193] In this case, the QoS requirements of multiple computing power requests for the same service ID are not much different, and the QoS requirements of computing power requests from the same service can be considered the same. Therefore, the network can pre-configure the mapping relationship between service ID and SR index for the UE.

[0194] Specifically, the relevant configuration of Model 1 is as follows:

[0195] a) SR resource configuration

[0196] The computing power request information must have a dedicated SR resource. That is, the network side configures different SR resources, such as SR resource 1 and SR resource 2, based on the resource conditions in the system.

[0197] In this model 1, a static SR resource configuration method can be adopted, that is, dedicated SR resources are allocated to the computing power request information of a specific business, and the business is matched with the SR resource. That is, when a specific business requires computing power, the SR resource corresponding to the specific business is used to send the computing power request information corresponding to the business.

[0198] b): Binding relationship

[0199] The SR index is bound to the service ID to differentiate the QoS levels of different services. Since the QoS requirements of computing power requests from the same service can be considered the same, after the SR index is bound to the service ID, it is also bound to the corresponding QoS level of the service.

[0200] Specifically, the network side needs to configure the correspondence between the service ID and the SR resource.

[0201] Optionally, SR resources are mapped one-to-one to services, such as SR resource 1 corresponds to service 1, SR resource 2 corresponds to service 2, and so on.

[0202] Optionally, multiple services with similar QoS requirements can be mapped to the same SR resource, such as SR resource 1 corresponding to service 1, SR resource 2 corresponding to services 2 and 3, and SR resource 3 corresponding to services 4 and 5.

[0203] c) Trigger conditions

[0204] When there are no CPU resources, or when there are CPU resources but the QoS requirements (such as latency, size, etc.) are not met, the sending of SR is triggered.

[0205] In the solution corresponding to Model 1, the UE can trigger SR resources corresponding to different computing power requests based on different services. After receiving the corresponding SR resources, the network can indirectly obtain the computing power resource request (rather than the uplink data transmission resource request) and the corresponding QoS requirement level (different services and their QoS levels correspond to different SR resources).

[0206] 2) Model 2: Different computing power requests for the same service ID have different or significantly different QoS requirements.

[0207] In this case, the QoS requirements of different computing power requests for the same service ID vary significantly. Therefore, the service and SR resource binding method cannot be used as in Model 1. Instead, a more detailed binding of QoS requirement levels and SR resources is required. In other words, the network can pre-configure the mapping between QoS levels and SR indices for the UE.

[0208] Specifically, the relevant configuration of Model 2 is as follows:

[0209] a) SR resource configuration

[0210] The computing power request information must have a dedicated SR resource. That is, the network side configures different SR resources, such as SR resource 1 and SR resource 2, based on the resource conditions in the system.

[0211] Similar to Model 1, in this Model 2, a static SR resource configuration method can also be adopted, that is, dedicated SR resources are allocated for computing power request information of a specific QoS level, and the QoS level of the computing power request and the SR resources are matched. That is, when a request of a specific QoS level requires computing power, the SR resources corresponding to the QoS level are used to send the computing power request information corresponding to the service.

[0212] In another possible implementation, an additional set of default SR resources may be configured, and all computing power requests for which no mapping relationship between QoS levels and SR resources is explicitly configured are sent through this SR resource.

[0213] b): Binding relationship

[0214] The SR index is bound to the QoS level. Different service requests have different QoS levels, and different QoS levels can correspond to different SR resources.

[0215] Specifically, the network side needs to configure the correspondence between QoS levels and SR resources.

[0216] Optionally, SR resources are mapped one-to-one to QoS levels, such as SR resource 1 corresponds to QoS level 1, SR resource 2 corresponds to QoS level 2, and so on.

[0217] Optionally, multiple similar QoS levels can also be mapped to the same SR resource, such as SR resource 1 corresponding to QoS level 1, SR resource 2 corresponding to QoS level 2 and QoS level 3, SR resource 3 corresponding to QoS level 4 and QoS level 5, etc.

[0218] c) Generation of service QoS

[0219] Service QoS is generated by the upper layer of the UE and carried to the lower layer through primitives. Service QoS can be left to the UE to implement, or the network can configure mapping rules for the UE.

[0220] d): Trigger conditions

[0221] When there are no CPU resources, or when there are CPU resources but the QoS requirements (such as latency, size, etc.) are not met, the sending of SR is triggered.

[0222] In the solution corresponding to Model 2, the UE can trigger SR resources corresponding to different computing power requests based on the different QoS requirements of the service. After receiving the corresponding SR resources, the network can indirectly obtain the computing power resource request (rather than the uplink data transmission resource request) and obtain the corresponding QoS level (different QoS levels correspond to different SR resources).

[0223] In addition, whether it is model 1 or model 2, the QoS requirements of computing power requests for different business IDs can be the same or very different.

[0224] When no SR resources are available, the UE needs to request computing resources through RACH. The following describes how the UE requests computing resources from the network through RACH.

[0225] When the UE uses the RACH method to request computing power resources, similarly, computing power request information can be sent through the RACH resources.

[0226] Similar to the SR method, for sending computing power request information, existing RACH resources used for data transmission can be used, or dedicated RACH resources can be allocated for computing power request information.

[0227] In one possible implementation, RACH access and computing power request can be performed through competition through the existing network / cell public RACH resources for data transmission. At this time, the computing power request and the data transmission request share one or more sets of RACH resources. Therefore, when the UE sends computing power request information to the network side through the RACH, the specific QoS level and / or request type (such as computing power request or UL grant request) can be carried in the RACH message, so that the network side knows that the request sent by the UE is a computing power request and a specific QoS level.

[0228] In another possible implementation, to make it easier for the network to know that the request carried by the RACH resource is a computing power request rather than a data transmission request, a dedicated RACH resource can be allocated for the computing power request information. This dedicated RACH resource is separate from ordinary data transmission RACH resources and is used only for computing power requests and not for other purposes. When the UE sends computing power request information using this dedicated RACH resource, the network can know that the request sent by the UE is a computing power request through this dedicated RACH resource.

[0229] In another possible implementation, different services of the same UE may have different QoS priorities for computing power requests. In the above solution, the network side can learn through dedicated RACH resources that the request sent by the UE is a computing power request, but cannot obtain the QoS priority of the computing power request through the dedicated RACH resources. In order to enable the network side to distinguish computing power requests with different QoS requirements, multiple sets of dedicated RACH resources can be configured for the UE, and different RACH resources can be used to correspond to computing power requests with different QoS requirements.

[0230] Multiple computing power requests for the same service ID are modeled in two different ways, similar to sending computing power requests through SR:

[0231] 1) Model 1: The QoS requirements of different computing power requests for the same service ID are similar / identical;

[0232] In this case, the QoS requirements of multiple computing power requests for the same service ID are not much different, and the QoS requirements of computing power requests from the same service can be considered the same. Therefore, the network can pre-configure the mapping relationship between service ID and RACH resource preamble code ID for the UE.

[0233] Specifically, the relevant configuration of Model 1 is as follows:

[0234] a) RACH resource configuration

[0235] The computing power request information must have a dedicated RACH resource. That is, the network side configures different RACH resources, such as RACH resource 1 and RACH resource 2, based on the resource conditions in the system.

[0236] In Model 1, a static RACH resource configuration approach can be used, allocating dedicated RACH resources to specific service computing power requests. In other words, the preamble IDs of services and RACH resources can be mapped. When a specific service requires computing power, the RACH resource corresponding to that service is used to send the computing power request information for that service.

[0237] b): Binding relationship

[0238] The preamble ID is bound to the service ID to differentiate the QoS levels of different services. Since the QoS requirements of computing power requests from the same service can be considered the same, after the preamble ID is bound to the service ID, the preamble ID is also bound to the QoS level corresponding to the service.

[0239] Specifically, the network side needs to configure the correspondence between the service ID and the RACH resource.

[0240] Optionally, RACH resources are mapped one-to-one to services, such as RACH resource 1 corresponds to service 1, RACH resource 2 corresponds to service 2, and so on.

[0241] Optionally, multiple services with similar QoS requirements may be mapped to the same RACH resource, such as RACH resource 1 corresponding to service 1, RACH resource 2 corresponding to services 2 and 3, and RACH resource 3 corresponding to services 4 and 5.

[0242] In the solution corresponding to model 1, the UE can trigger different preamble IDs corresponding to different computing power requests according to different services. After receiving the RACH resource of the corresponding preamble ID, the network can indirectly obtain the computing power resource request (rather than the uplink data transmission resource request) and the corresponding QoS requirement level (different services and their QoS levels correspond to different preamble IDs).

[0243] 2) Model 2: Different computing power requests for the same service ID have different or significantly different QoS requirements.

[0244] In this case, the QoS requirements for different computing power requests for the same service ID vary significantly. Therefore, it is not possible to bind services and RACH resources one by one as in Model 1. Instead, it is necessary to bind QoS requirement levels and RACH resources in a more detailed manner. In other words, the network can pre-configure the mapping between QoS levels and preamble IDs for the UE.

[0245] Specifically, the relevant configuration of Model 2 is as follows:

[0246] a) RACH resource configuration

[0247] The computing power request information must have a dedicated RACH resource. That is, the network side configures different RACH resources, such as RACH resource 1 and RACH resource 2, based on the resource conditions in the system.

[0248] Similar to Model 1, in Model 2, a static RACH resource configuration method can also be used. Specifically, dedicated RACH resources are allocated for computing power requests of specific QoS levels. The QoS level of the computing power request is mapped to the RACH resource. That is, when a request of a specific QoS level requires computing power, the RACH resource corresponding to that QoS level is used to send the computing power request information corresponding to that service.

[0249] In another possible implementation, an additional set of default RACH resources may be configured, and all computing power requests for which no mapping relationship between QoS levels and RACH resources is explicitly configured are sent through the RACH resources.

[0250] b): Binding relationship

[0251] The preamble ID is bound to the QoS level. Different service requests have different QoS levels, so computing power requests of different QoS levels can correspond to different RACH resources.

[0252] Specifically, the network side needs to configure the correspondence between QoS levels and RACH resources.

[0253] Optionally, RACH resources are mapped one-to-one to QoS levels, such as RACH resource 1 corresponds to QoS level 1, RACH resource 2 corresponds to QoS level 2, and so on.

[0254] Optionally, multiple similar QoS levels may be mapped to the same RACH resource, such as RACH resource 1 corresponding to QoS level 1, RACH resource 2 corresponding to QoS level 2 and QoS level 3, RACH resource 3 corresponding to QoS level 4 and QoS level 5, etc.

[0255] In the solution corresponding to Model 2, the UE can trigger RACH resources corresponding to different computing power requests based on the different QoS requirements of the service. After receiving the corresponding RACH resources, the network can indirectly obtain the computing power resource request (rather than the uplink data transmission resource request) and obtain the corresponding QoS level (different QoS levels correspond to different SR resources).

[0256] The following describes the process of requesting computing resources using the RACH method:

[0257] a) RACH trigger

[0258] When a service ID does not have a valid SR (for example, no SR is configured, or SR is configured but does not meet the latency requirement, or SR is prohibited from being sent frequently), RACH is triggered.

[0259] b) RACH process

[0260] The RACH process reuses the RACH process in existing 5G communications, which mainly includes the following steps:

[0261] 1. Random Access Signal Transmission: A mobile device or terminal transmits a random access signal (RAP) containing a preamble on the RACH. The transmission time and preamble are randomly selected. The random access signal typically consists of multiple subcarriers, each with a preamble to distinguish different mobile devices or terminals.

[0262] 2. Access Response Waiting: After receiving the random access signal, the network sends an access response (Random Access Response) to the mobile device or terminal, which contains a random access response preamble and some other information. The mobile device or terminal needs to wait for a period of time to receive the access response, which is usually pre-set by the network.

[0263] 3. Random Access Response Transmission: After receiving the access response, the mobile device or terminal needs to send a random access response signal on the RACH, which contains the access response preamble and some other information. The random access response signal is usually composed of multiple subcarriers, each with a preamble, which is used to confirm that the mobile device or terminal has successfully accessed the network.

[0264] 4. Access confirmation: After receiving the random access response signal, the network will send an access confirmation (Random Access Completion) to the mobile device or terminal to confirm that the mobile device or terminal has successfully accessed the network.

[0265] In general, the RACH process is primarily the process by which a mobile device or terminal initiates an initial access request to the network. This includes the transmission of a random access signal, waiting for an access response, the transmission of a random access response, and the final confirmation of an access confirmation. This process typically relies on specific resources and algorithms, such as the allocation and identification of preambles, and the allocation and scheduling of access responses, to achieve efficient and reliable data transmission and communication connections.

[0266] In S330, the network device determines allocation result information, which is used to indicate the allocation status of computing power resources. In S340, the network device sends the allocation result information and computing power configuration information to the UE.

[0267] In the above solution, the UE sends computing power request information to the network device to request allocation of computing power resources.

[0268] In one possible implementation, the computing power request information includes first parameter information, where the first parameter information is used to indicate at least one of the size, location, and QoS requirement of each computing power resource in the computing power resources.

[0269] After receiving the computing power request, the network device determines allocation result information based on the computing power request. The allocation result information indicates the allocation of the computing power resources requested by the computing power request. Specifically, the allocation result information can indicate the allocation status of the requested computing power resources (e.g., success, failure, partial success and partial failure, etc.).

[0270] In one possible implementation, when part or all of the requested computing resources are successfully allocated, the network device determines computing power configuration information, where the computing power configuration information includes configuration information of part or all of the computing resources.

[0271] In another possible implementation, the allocation result information includes computing power configuration information.

[0272] In one possible implementation, for scenarios where computing power allocation fails, the allocation result information may also carry the reasons for the failure (such as QoS requirements not being met, excessive load, invalid CPU ID, unsupported CPU type, etc.).

[0273] The network device allocates computing resources to the UE through allocation result information or independent computing power configuration information.

[0274] Specifically, allocation can be performed through independent RRC / MAC messages or through a combination of methods (such as RRC configuration + MAC / PHY activation). Regardless of the method used, the information carried is as follows:

[0275] 1) Periodic Resources (Configured Computing Grant, CCG)

[0276] CCG parameters: include one or more of the following parameters: CPU ID, CPU slot ID, start offset, CCG cycle, CCG bitmap.

[0277] CPU slot: In communication systems, a CPU slot is a time slot used to process control signaling. Its primary function is to provide control and management functions for the communication system, such as allocating resources, scheduling data transmission, coordinating user devices, and maintaining system status. The number and allocation of CPU slots are typically determined during system design and deployment, and are adjusted and optimized based on network load and communication requirements to improve system efficiency and performance. A CPU slot request typically refers to the process of a mobile device or terminal initiating a control signaling request from the network. Its primary purpose is to obtain CPU slot resources for control signaling processing and resource management.

[0278] Start offset: Refers to the first position of a periodic resource, typically the first position or starting position of a resource that is periodically allocated and used (such as a time slot or chip). In a communication system, the first position of a periodic resource is typically determined during system design and adjusted and optimized based on different communication requirements and network load. For example, in a TDMA system, a time slot is a periodic resource, and its first position is typically a fixed time point, such as the system startup time or frame synchronization time. The length and position of each time slot are also fixed. In a CDMA system, a chip is a periodic resource, and its first position is typically a fixed chip sequence, such as a Walsh code sequence. The length and position of each chip are also fixed. When allocating and using periodic resources, the system typically needs to consider factors such as resource utilization, latency, and throughput to ensure system efficiency and performance.

[0279] CCG period: This refers to the period size, which refers to the length or capacity of the resource within a complete period. For example, for time slot resources, the period size is usually a complete frame period, that is, multiple time slots are combined into a frame, and the frame length is usually fixed. For chip resources, the period size is usually a complete chip sequence period, that is, multiple chips are combined into a chip sequence, and the chip sequence length is also usually fixed.

[0280] CCG bitmap: refers to the grant location, which can be in the form of a bitmap or duration; its unit is time (ms, SFN is the base value; CPU slot) or frequency (Hz).

[0281] A bitmap is a graphical data structure that represents the allocation of periodic resources. It is usually used to describe the allocation of periodic resources within a complete cycle. A bitmap usually consists of a set of binary bits, each of which represents a position or time slot of a periodic resource, where 0 indicates that the position or time slot is unallocated, and 1 indicates that the position or time slot is allocated. For example, for time slot resources, a bitmap usually consists of a set of binary bits, each of which represents the allocation of a time slot, where 0 indicates that the time slot is unallocated, and 1 indicates that the time slot is allocated. For chip resources, a bitmap usually consists of a set of binary bits, each of which represents the allocation of a chip, where 0 indicates that the chip is unallocated, and 1 indicates that the chip is allocated. Bitmaps can be used to quickly describe and query the allocation of periodic resources.

[0282] 2) One-time resources (Dynamic Computing Grant, DCG)

[0283] Similar to CCG, it includes one or more of the following parameters: CPU ID, CPU slot ID, etc.

[0284] In a possible implementation, the network device further sends resource constraint information to the UE.

[0285] In another possible implementation, the computing power configuration information also includes resource constraint information.

[0286] Resource constraint information: The constraint relationship between resources and services, used to indicate that some computing resources are only allowed to be used by some services, or some computing resources are not allowed to be used by some services. For example, computing resources include computing resource 1, computing resource 2, and other computing resources.

[0287] In one possible implementation, the resource constraint information is used to indicate that computing resource 1 can only be used by business 1, and computing resource 2 can only be used by business 2.

[0288] In another possible implementation, the resource constraint information is used to indicate that computing resource 1 cannot be used by business 1, and computing resource 2 cannot be used by businesses 1 and 2.

[0289] Optionally, resource constraint information includes the binding relationship between the business and computing resources: {business ID / business group ID, computing resource ID}. In other words, different computing resources can correspond to different businesses or business groups, and a specific computing resource can only be used by one or more corresponding businesses or business groups.

[0290] In one possible implementation, the network needs to configure a binding relationship between computing resources and a service ID / service group ID for the UE.

[0291] From the UE side, when there is a certain computing power resource (such as CPU time slice), it is necessary to determine whether there is a pre-configured restriction relationship. If there is a constraint, it can only be scheduled for use by the service ID that is allowed to use it.

[0292] Figure 9 is a schematic block diagram of a communication device 400 provided in an embodiment of the present application. The device 400 includes a transceiver unit 410 and a processing unit 420. The transceiver unit 410 can communicate with the outside world, and the processing unit 420 is used to process data. The transceiver unit 410 can also be referred to as a communication interface or a communication unit.

[0293] In a possible implementation, the apparatus 400 may further include a storage unit, which may be used to store instructions and / or data, and the processing unit 420 may read the instructions and / or data in the storage unit.

[0294] The device 400 can be used to execute the actions performed by the network device in the above method embodiment. In this case, the device 400 can be a network device or a component that can be configured on the network device. The transceiver unit 410 is used to execute the transceiver-related operations on the network device side in the above method embodiment, and the processing unit 420 is used to execute the processing-related operations on the network device side in the above method embodiment.

[0295] Alternatively, the device 400 can be used to execute the actions performed by the terminal device in the above method embodiment. In this case, the device 400 can be a terminal device or a component that can be configured on the terminal device. The transceiver unit 410 is used to execute the transceiver-related operations on the terminal device side in the above method embodiment, and the processing unit 420 is used to execute the processing-related operations on the terminal device side in the above method embodiment.

[0296] As shown in Figure 10, an embodiment of the present application further provides a communication device 500. The communication device 500 includes a processor 510, which is coupled to a memory 520. The memory 520 is used to store computer programs or instructions and / or data. The processor 510 is used to execute the computer programs or instructions and / or data stored in the memory 520, so that the method in the above method embodiment is executed.

[0297] In a possible implementation, the communication device 500 includes one or more processors 510 .

[0298] In a possible implementation, as shown in FIG10 , the communication device 500 may further include a memory 7520 .

[0299] In a possible implementation, the communication device 500 may include one or more memories 520 .

[0300] In a possible implementation, the memory 520 may be integrated with the processor 510 or provided separately.

[0301] In one possible implementation, as shown in Figure 10, the wireless communication device 500 may further include a transceiver 7530, which is used to receive and / or transmit signals. For example, the processor 510 is used to control the transceiver 530 to receive and / or transmit signals.

[0302] As a solution, the communication device 500 is used to implement the operations performed by the network device in the above method embodiment.

[0303] For example, the processor 510 is used to implement the processing-related operations performed by the network device in the above method embodiment, and the transceiver 530 is used to implement the sending and receiving-related operations performed by the network device in the above method embodiment.

[0304] As another solution, the communication device 500 is used to implement the operations performed by the terminal device in the above method embodiment.

[0305] For example, the processor 510 is used to implement the processing-related operations performed by the terminal device in the above method embodiment, and the transceiver 530 is used to implement the sending and receiving-related operations performed by the terminal device in the above method embodiment.

[0306] The present application also provides a communication device 600, which can be a terminal device or a chip. The communication device 600 can be used to perform the operations performed by the terminal device in the above-described method embodiments. When the communication device 600 is a terminal device, FIG11 shows a simplified schematic diagram of the terminal device structure. For ease of understanding and illustration, FIG11 uses a mobile phone as an example of a terminal device. As shown in FIG11, the terminal device includes a processor, memory, radio frequency circuitry, an antenna, and input / output devices. The processor is primarily used to process communication protocols and communication data, control the terminal device, execute software programs, and process software program data. The memory is primarily used to store software programs and data. The radio frequency circuitry is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user. It should be noted that some types of terminal devices may not have input / output devices.

[0307] When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, only one memory and processor are shown in Figure 11. In actual terminal device products, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be set independently of the processor or integrated with the processor, and this is not limited in the embodiments of the present application.

[0308] In the embodiment of the present application, the antenna and radio frequency circuit with transceiver functions can be regarded as the transceiver unit of the terminal device, and the processor with processing function can be regarded as the processing unit of the terminal device.

[0309] As shown in Figure 11, the terminal device includes a transceiver unit 610 and a processing unit 620. The transceiver unit 610 may also be called a transceiver, a transceiver, a transceiver device, etc. The processing unit 620 may also be called a processor, a processing board, a processing module, a processing device, etc.

[0310] In one possible implementation, the device in the transceiver unit 610 that implements the receiving function can be considered a receiving unit, and the device in the transceiver unit 610 that implements the transmitting function can be considered a transmitting unit. That is, the transceiver unit 610 includes a receiving unit and a transmitting unit. The transceiver unit may also be sometimes referred to as a transceiver, a transceiver, or a transceiver circuit. The receiving unit may also be sometimes referred to as a receiver, a receiver, or a receiving circuit. The transmitting unit may also be sometimes referred to as a transmitter, a transmitter, or a transmitting circuit.

[0311] For example, in one implementation, the transceiver unit 610 is used to perform a receiving operation of the terminal device, and the processing unit 620 is used to perform a processing action on the terminal device side.

[0312] It should be understood that FIG11 is merely an example and not a limitation, and the terminal device including the transceiver unit and the processing unit may not rely on the structure shown in FIG11 .

[0313] When the communication device 600 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. The input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be different circuits or the same circuit, in which case the circuit functions as an input circuit and an output circuit respectively at different times.

[0314] The embodiment of the present application further provides a communication device 700, which can be a network device or a chip. The communication device 700 can be used to execute the operations executed by the network device in the above method embodiment.

[0315] When the communication device 700 is a network device. Figure 12 shows a simplified schematic diagram of the network device structure. The network device includes a portion 710 and a portion 720. Portion 710 is primarily used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals; portion 720 is primarily used for baseband processing, controlling the network device, etc. Portion 710 can generally be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver. Portion 720 is generally the control center of the network device, generally referred to as a processing unit, which is used to control the network device to perform the processing operations on the network device side in the above-mentioned method embodiments.

[0316] The transceiver unit in section 710, which may also be referred to as a transceiver or transceiver, includes an antenna and radio frequency circuitry, with the radio frequency circuitry primarily responsible for radio frequency processing. In one possible implementation, the device in section 710 that implements the receiving function can be considered a receiving unit, and the device that implements the transmitting function can be considered a transmitting unit. That is, section 710 includes both a receiving unit and a transmitting unit. The receiving unit can also be referred to as a receiver, receiver, or receiving circuit, and the transmitting unit can be referred to as a transmitter, transmitter, or transmitting circuit.

[0317] Section 720 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control network devices. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an optional embodiment, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0318] For example, in one implementation, the transceiver unit of part 710 is used to execute the transceiver-related steps executed by the network device in the embodiment; and part 720 is used to execute the processing-related steps executed by the network device.

[0319] It should be understood that FIG12 is merely an example and not a limitation, and the network device including the transceiver unit and the processing unit may not rely on the structure shown in FIG12 .

[0320] When the communication device 700 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. The input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be different circuits or the same circuit. In this case, the circuit functions as an input circuit and an output circuit at different times.

[0321] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the method executed by the terminal device or the method executed by the network device in the above method embodiment.

[0322] For example, when the computer program is executed by a computer, the computer can implement the method executed by the terminal device or the method executed by the network device in the above method embodiment.

[0323] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by a terminal device or the method executed by a network device in the above method embodiment.

[0324] An embodiment of the present application further provides a communication system, which includes the network device and terminal device in the above embodiment.

[0325] The explanation and beneficial effects of the relevant contents in any of the wireless communication devices provided above may refer to the corresponding method embodiments provided above, and will not be repeated here.

[0326] In an embodiment of the present application, a terminal device or network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0327] The embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided in the embodiments of the present application; as long as it is capable of communicating according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application, it is sufficient. For example, the execution subject of the method provided in the embodiments of the present application may be a terminal device or a network device, or a functional module in the terminal device or network device that is capable of calling and executing a program.

[0328] Various aspects or features of the embodiments of the present application may be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" may encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, a computer-readable medium may include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.).

[0329] The various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0330] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0331] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0332] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0333] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0334] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of this application.

[0335] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0336] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0337] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0338] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0339] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0340] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the embodiments of the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for computing power scheduling, characterized in that: include: The first device obtains a computing resource request, where the computing resource request comes from an access layer AS, a non-access layer NAS or an application layer of the first device; The first device generates computing power request information according to the computing power resource request, where the computing power request information is used to request allocation of computing power resources to the first device.

2. The method according to claim 1, characterized in that The method further comprises: The first device sends the computing power request information, and the sending method of the computing power request information includes AS signaling or NAS signaling. The AS signaling includes a scheduling request SR, a random access channel RACH, a buffer status report BSR and a radio resource control RRC signaling.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first device receives allocation result information, where the allocation result information is used to indicate an allocation result of the computing power resources requested to be allocated by the computing power request information, where the allocation result includes all allocation success, all allocation failure, or partial allocation success.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The first device receives computing power configuration information, where the computing power configuration information includes configuration information of computing power resources allocated by a network device to the first device, and the computing power resources allocated by the network device to the first device include computing power resources of the first device and the network device.

5. The method according to any one of claims 1 to 4, characterized in that The first device generates computing power request information according to the computing power resource request, including: When the preset parameters meet the corresponding preset conditions, the first device generates the computing power request information according to the computing power resource request, and the preset parameters include at least one of the following parameters: the detection result of periodic detection of whether there is a computing power resource request, the total amount of computing power resources requested for computing power resources, the number of computing power resource requests, the minimum delay of the computing power resource request, and the minimum value of the remaining delay of the computing power resource request.

6. The method according to any one of claims 1 to 5, characterized in that When the computing resource request is cancelled, the method further includes: If the computing power request information has not been sent, the first device cancels sending the computing power request information; If the computing power request information has been sent, the first device generates and sends a cancellation request information, where the cancellation request information is used to request the cancellation of the allocation of the first computing power resource, which is all or part of the computing power resources requested to be allocated by the computing power request information.

7. The method according to any one of claims 2 to 6, characterized in that The computing power resource request is a computing power resource request from a first business, and the method further includes: Determine a method for sending the computing power request information according to the identification ID of the first service.

8. The method according to any one of claims 2 to 7, characterized in that The method further comprises: The method for sending the computing power request information is determined according to the QoS requirements of the computing power resources corresponding to the computing power resource request.

9. The method according to any one of claims 4 to 8, characterized in that The computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device are only allowed to be used by part of the services.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: The first device obtains multiple computing resource requests; The first device generates the computing power request information according to the multiple computing power resource requests.

11. A method for computing power scheduling, characterized in that: include: The network device receives computing power request information, where the computing power request information is used to request allocation of computing power resources to the first device; The network device determines allocation result information, where the allocation result information is used to indicate an allocation result of the computing power resource requested to be allocated by the computing power request information, where the allocation result includes all allocation success, all allocation failure, or partial allocation success; The network device sends the allocation result information.

12. The method according to claim 11, characterized in that The method further comprises: Determine computing power configuration information, where the computing power configuration information includes configuration information of computing power resources allocated by the network device to the first device, and the computing power resources allocated by the network device to the first device include computing power resources of the first device and the network device; The network device sends the computing power configuration information.

13. The method according to claim 11 or 12, characterized in that The computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device are only allowed to be used by part of the services.

14. A computing power scheduling device, characterized in that: include: A processing module, configured to obtain a computing resource request, where the computing resource request comes from an access layer AS, a non-access layer NAS or an application layer of the first device; The processing module is further used to generate computing power request information according to the computing power resource request, and the computing power request information is used to request allocation of computing power resources to the first device.

15. The device according to claim 14, characterized in that The device also includes: A sending module is used to send the computing power request information, where the sending method of the computing power request information includes AS signaling or NAS signaling, and the AS signaling includes a scheduling request SR, a random access channel RACH, a cache status report BSR or a radio resource control RRC signaling.

16. The device according to claim 14 or 15, characterized in that The device also includes: A receiving module is used to receive allocation result information, wherein the allocation result information is used to indicate the allocation result of the computing power resources requested to be allocated by the computing power request information, and the allocation result includes all allocation success, all allocation failure or partial allocation success.

17. The device according to any one of claims 14 to 16, characterized in that The receiving module is also used to receive computing power configuration information, where the computing power configuration information includes configuration information of computing power resources allocated by the network device to the first device, and the computing power resources allocated by the network device to the first device include computing power resources of the first device and the network device.

18. The device according to any one of claims 14 to 17, characterized in that The processing module is further configured to generate computing power request information according to the computing power resource request, including: When the preset parameters meet the corresponding preset conditions, the processing module is also used to generate The computing power request information, the preset parameters include at least one of the following parameters: the detection result of periodic detection of whether there is a computing power resource request, the total amount of computing power resources requested for computing power resources, the number of computing power resource requests, the minimum delay of the computing power resource request, and the minimum value of the remaining delay of the computing power resource request.

19. The device according to any one of claims 14 to 18, characterized in that When the computing resource request is cancelled, If the computing power request information has not been sent, the sending module cancels sending the computing power request information; If the computing power request information has been sent, the processing module is also used to generate cancellation request information, and the sending module is also used to send the cancellation request information, and the cancellation request information is used to request the cancellation of the allocation of the first computing power resource, which is all or part of the computing power resources requested to be allocated by the computing power request information.

20. The device according to any one of claims 15 to 19, characterized in that The computing power resource request is a computing power resource request from a first business, and the sending module is further used to determine a sending method of the computing power request information according to an identification ID of the first business.

21. The device according to any one of claims 15 to 20, characterized in that The sending module is also used to determine the method of sending the computing power request information according to the QoS requirements of the computing power resources corresponding to the computing power resource request.

22. The device according to any one of claims 17 to 21, characterized in that The computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device are only allowed to be used by part of the services.

23. The device according to any one of claims 14 to 22, characterized in that The processing module obtains multiple computing power resource requests and generates the computing power request information according to the multiple computing power resource requests.

24. A computing power scheduling device, characterized in that: include: A receiving module, configured to receive computing power request information, wherein the computing power request information is used to request allocation of computing power resources to the first device; a processing module, configured to determine allocation result information, wherein the allocation result information is used to indicate an allocation result of the computing power resources requested to be allocated by the computing power request information, wherein the allocation result includes all allocation success, all allocation failure, or partial allocation success; A sending module is used to send the allocation result information.

25. The device according to claim 24, characterized in that The processing module is further used to determine computing power configuration information, where the computing power configuration information includes configuration information of computing power resources allocated by the network device to the first device, and the computing power resources allocated by the network device to the first device include computing power resources of the first device and the network device; The sending module is also used to send the computing power configuration information.

26. The device according to claim 24 or 25, characterized in that The computing power configuration information includes resource constraint information, and the resource constraint information is used to indicate that part of the computing power resources allocated by the network device to the first device are only allowed to be used by part of the services.

27. A computer program product, characterized in that The computer program product comprises: a computer program code, when the computer program code is executed, Execute the method according to any one of claims 1 to 10, or Execute the method of any one of claims 11 to 13.

28. A computer-readable storage medium, characterized in that: The computer readable storage medium stores a computer program. When the computer program is executed, The device performs the method according to any one of claims 1 to 10, or The device is caused to perform the method as claimed in any one of claims 11 to 13.

29. A chip system, characterized in that: comprising: a processor for calling and running a computer program from a memory, Enable a communication device equipped with the chip system to perform the method according to any one of claims 1 to 10; or The communication device equipped with the chip system executes the method as claimed in any one of claims 11 to 13.

30. A communication system, characterized in that: The invention comprises an electronic device and a network device, wherein the network device is used to execute the method according to any one of claims 11 to 13, and the electronic device is used to execute the method according to any one of claims 1 to 10.

Images