Communication method, and apparatus

Abstract

The embodiments of the present application relate to the field of communications. Provided are a communication method and an apparatus, which can provide corresponding task allocation and corresponding data transmission configurations for different computing service requests of a terminal device. The method comprises: a first network element associates a first identifier corresponding to one first request message amongst at least one first request message sent by a first terminal device with a second identifier corresponding to a first task related to a first service requested by said one first request message, and notifies the first terminal device of same, such that the first terminal device may determine, on the basis of the second identifier associated with the first identifier corresponding to said one first request message, the first service requested by which first request message a transmission configuration of the first task related to the first service is configured for.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on December 15, 2023, with application number 202311734404.9 and application name “Communication Method and Device,” the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to communication methods and devices. Background Art

[0003] As industries like healthcare, factories, ports, coal mines, and government and enterprises accelerate their digital transformation, computing and communications are becoming core foundational capabilities that empower these industries' digital transformations. To this end, operators have proposed the concept of a computing network and are organizing standardization discussions within the 3rd Generation Partnership Project (3GPP). A computing network uses network-aware ubiquitous computing and services to dispatch computing tasks to appropriate computing nodes for processing, improving the utilization efficiency of network and computing resources while providing users with low-latency and highly reliable services to ensure a positive user experience.

[0004] When providing computing services to terminal devices over a network, the network needs to schedule computing nodes to perform the computing tasks offloaded by the terminal devices and establish data transmission channels between the computing nodes and the terminal devices. However, how the network provides corresponding task allocation and data transmission configuration based on the different computing service requests of the terminal devices is currently unclear. Summary of the Invention

[0005] The embodiments of the present application provide a communication method and apparatus that can provide corresponding task allocation and corresponding data transmission configuration for different computing service requests of terminal devices.

[0006] To achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, a communication method is provided. The method can be executed by a first network element, or by a component of the first network element, such as a processor, chip, or chip system of the first network element. It can also be implemented by a logic module or software that implements all or part of the first network element. The method includes: receiving at least one first request message from a first terminal device, wherein one of the at least one first request message is for requesting a first service, and the first request message includes a first identifier and a quality of service (QoS) requirement of the first service, and the first identifier corresponds to the first request message; sending a second request message to a first computing node based on the first request message, wherein the second request message is for requesting the first computing node to perform a first task related to the first service, and the second request message includes a second identifier, the second identifier corresponding to the first task, and the second identifier is associated with the first identifier; receiving a second response message from the first computing node, wherein the second response message indicates that the first computing node accepts to perform the first task; and sending a first response message to the first terminal device based on the second response message, wherein the first response message indicates that the first service is provided, and the first response message includes the first identifier and the second identifier.

[0008] Based on this communication method, in a scenario where the first terminal device sends at least one first request message, the first network element associates the first identifier corresponding to one of the at least one first request messages sent by the first terminal device with the second identifier corresponding to the first task related to the first service requested by the first request message, and informs the first terminal device, so that the first terminal device can determine, based on the second identifier associated with the first identifier corresponding to the first request message, which first service configuration the transmission configuration of the first task related to the first service is for. Thus, the first network element can provide corresponding task allocation and data transmission configuration for each service request initiated by the first terminal device to ensure the reliability of the service.

[0009] In a possible design scheme, the method provided by the embodiment of the present application may further include: sending a third request message to the user plane network element. And, sending a fourth request message to the access network device. The third request message is used to request the user plane network element to establish a tunnel for transmitting data of the first task between the user plane network element and the access network device, and the third request message includes a first QoS configuration for establishing a tunnel; the fourth request message is used to request the access network device to establish a wireless bearer for transmitting data of the first task between the user plane network element and the access network device, and the fourth request message includes a second QoS configuration and a second identifier for establishing a wireless bearer, and the first QoS configuration and the second QoS configuration are determined according to the QoS requirements of the first service. For example, in the case where the first computing node is an application server or a computing platform located at the edge network, the data transmission between the first terminal device and the first computing node needs to be implemented through the data plane, so that the first network element can trigger the access network device and the user plane network element to establish a channel for transmitting task data.

[0010] In one possible design, the third request message may further include first information, where the first information is used to indicate filtering and mapping rules for transmitting data of the first task. Thus, the first network element may configure the first information for the user plane network element while configuring the user plane network element to establish a tunnel, thereby indicating filtering and mapping rules for user plane data transmission. This can reduce signaling overhead while ensuring the reliability of user plane network element data transmission.

[0011] In a possible design scheme, the first information may include at least one of the following: application port information, a first parameter group, or a QoS flow template; wherein the application port information includes the application port number of the first terminal device and the application port number of the first computing node, the first parameter group includes the Internet Protocol IP address of the first terminal device, the application port number of the first terminal device, the data transmission protocol type corresponding to the first service, the IP address of the first computing node and the application port number of the first computing node, the QoS flow template includes filtering and mapping rules corresponding to multiple different parameter groups, and the multiple different parameter groups include the first parameter group. In an embodiment of the present application, the data transmission protocol type corresponding to the first service may also be predefined or preconfigured, and the QoS flow template may also be obtained by the user plane network element from the session management network element.

[0012] In one possible design, the first request message may also include second information, which may include at least one of the following: an IP address of the first terminal device, an application port number of the first terminal device, or a data transmission protocol type corresponding to the first service. The method provided in this embodiment of the application may further include: sending the second information to the first computing node. Thus, the first network element may also send the second information to the first computing node to ensure that the first computing node can accurately send the task data to the first terminal device.

[0013] In one possible design, the first response message may also include information about the first computing node and / or a QoS flow template. The information about the first computing node includes the IP address of the first computing node and / or the application port number of the first computing node. The information about the first computing node and / or the QoS flow template are used to filter and map the data of the first task. Thus, the first network element may also carry information in the first response message for instructing the first terminal device to filter and map the data of the first task to ensure the reliability of data transmission.

[0014] In one possible design scheme, the QoS flow template is specifically used to filter and map the IP data flow of the first task into a first QoS flow, or the QoS flow template is used to filter the IP data flow of the first task into a service data flow SDF and map the SDF into the first QoS flow.

[0015] Through the computing service and data transmission process given by this method, the network can dispatch the computing tasks requested by the terminal device to the appropriate computing node to provide corresponding computing resources for execution and corresponding communication resources for transmission, so that the execution of computing tasks and the transmission of data are both reliable.

[0016] According to a second aspect, a communication method is provided, which can be executed by a first terminal device, or by a component of the first terminal device, such as a processor, chip, or chip system of the first terminal device, or by a logic module or software that can implement all or part of the first terminal device. The method comprises: sending at least one first request message to a first network element. Among the at least one first request message, one first request message is used to request a first service, one first request message includes a first identifier and a quality of service (QoS) requirement for the first service, and the first identifier corresponds to one first request message. A first response message is received from the first network element, the first response message is used to indicate the provision of the first service, the first response message includes a first identifier and a second identifier, the second identifier is associated with the first identifier, and the second identifier corresponds to a first task related to the first service.

[0017] In one possible design scheme, the method provided in an embodiment of the present application may further include: receiving first configuration information from a second device, the first configuration information including a second identifier, the first configuration information being used to configure the first terminal device to establish a radio bearer for transmitting data of the first task with the second device; wherein the second device includes a second terminal device or an access network device to which the first terminal device belongs. Determining, based on the second identifier, that the first configuration information is configuration information associated with the first identifier. Transmitting the data of the first task using the radio bearer configured with the first configuration information.

[0018] In one possible design, transmitting data of the first task using a wireless bearer configured with first configuration information may include: mapping the IP data flow of the first task into a first QoS flow according to a first parameter group and / or a QoS flow template, wherein the first parameter group includes the IP address of the first terminal device, the application port number of the first terminal device, the data transmission protocol type corresponding to the first service, the IP address of the first computing node, and the application port number of the first computing node, and the first computing node is a computing node that executes the first task. Transmitting the first QoS flow using a wireless bearer configured with the first configuration information.

[0019] In one possible design, using the first configuration information to transmit data of the first task may include: mapping the IP data stream of the first task to a first QoS stream based on the second identifier, and transmitting the first QoS stream using a radio bearer configured with the first configuration information; or, transmitting the IP data stream of the first task using the radio bearer configured with the first configuration information, where the IP data stream of the first task includes the second identifier.

[0020] In one possible design scheme, the first request message may further include second information, and the second information may include at least one of the following: the IP address of the first terminal device, the application port number of the first terminal device, or the data transmission protocol type corresponding to the first service.

[0021] In one possible design scheme, the first response message may also include information of the first computing node and / or a QoS flow template. The information of the first computing node includes the IP address of the first computing node and / or the application port number of the first computing node. The information of the first computing node and / or the QoS flow template are used to filter and map the data of the first task.

[0022] In one possible design scheme, the QoS flow template is specifically used to filter and map the IP data flow of the first task into a first QoS flow, or the QoS flow template is used to filter the IP data flow of the first task into a service data flow SDF and map the SDF into the first QoS flow.

[0023] The computing service and data transmission process provided by this method enables the computing tasks requested by the terminal device to be offloaded to the computing node for execution, and the execution of the computing tasks and the transmission of data are both reliable and guaranteed.

[0024] In a third aspect, a communication method is provided. The method can be executed by a first computing node, or by a component of the first computing node, such as a processor, chip, or chip system of the first computing node, or by a logic module or software that can implement all or part of the first computing node. The method includes: receiving a second request message from a first network element, the second request message is used to request the first computing node to perform a first task related to a first service, the second request includes a second identifier, and the second identifier corresponds to the first task. A second response message is sent to the first network element based on the second request message, and the second response message is used to indicate that the first computing node accepts to perform the first task.

[0025] In one possible design, the method provided in an embodiment of the present application may further include: sending second configuration information to the first terminal device, the second configuration information including a second identifier, the second configuration information being used to configure the first terminal device to establish a wireless bearer for transmitting data of the first task with the first computing node. The wireless bearer configured with the second configuration information is used to send the data of the first task to the first terminal device.

[0026] In a possible design scheme, the method provided in an embodiment of the present application may also include: sending an IP data flow or a first QoS flow of a first task to a user-side network element, the IP data flow or the first QoS flow of the first task including a second identifier, and the first QoS flow is obtained by mapping the IP data flow of the first task according to the second identifier.

[0027] In a possible design solution, the second request message may further include a QoS requirement of the first task, where the QoS requirement of the first task is determined according to a QoS requirement of the first service.

[0028] In one possible design scheme, the second response message may also include information of the first computing node, the information of the first computing node includes the IP address of the first computing node and / or the application port number of the first computing node, and the information of the first computing node is used to filter and map the data of the first task.

[0029] In one possible design solution, the second response message may further include a QoS flow template, where the QoS flow template is used to filter and map the data of the first task.

[0030] In one possible design scheme, the QoS flow template is specifically used to filter and map the IP data flow of the first task into a first QoS flow, or the QoS flow template is used to filter the IP data flow of the first task into a service data flow SDF and map the SDF into the first QoS flow.

[0031] Among them, the technical effects of the method described in the second or third aspect can refer to the relevant description of the technical effects of the method described in the first aspect, and will not be repeated here.

[0032] In a fourth aspect, a communication method is provided. The method can be executed by a second device, or by a component of the second device, such as a processor, chip, or chip system of the second device, or by a logic module or software that can implement all or part of the second device. The method includes: sending second configuration information to a first terminal device, the second configuration information including a second identifier, and the second configuration information is used to configure the first terminal device to establish a wireless bearer for transmitting data of a first task with the second device. The wireless bearer configured using the second configuration information is used to send data of the first task to the first terminal device, and the second identifier corresponds to the first task.

[0033] In the embodiment of the present application, the second device may be an access network device to which the first terminal device belongs, or may be a second terminal device different from the first terminal device, and there is no limitation on this.

[0034] In one possible design, the second device is an access network device to which the first terminal device belongs, and sending the second configuration information to the first terminal device may include: receiving a fourth request message from the first network element, the fourth request message being used to request the access network device to establish a wireless bearer with the first terminal device for transmitting data of the first task, the fourth request including a second QoS configuration and a second identifier for establishing the wireless bearer. Sending the second configuration information to the first terminal device in accordance with the fourth request message.

[0035] In a possible design scheme, the method provided in the embodiment of the present application may also include: receiving an IP data flow or a first QoS flow of a first task from a user-plane network element, where the IP data flow or the first QoS flow of the first task includes a second identifier.

[0036] In one possible design scheme, using the wireless bearer configured with the second configuration information to send data of the first task to the first terminal device may include: using the wireless bearer configured with the second configuration information to send the IP data stream or the first QoS stream of the first task to the first terminal device, the IP data stream or the first QoS stream of the first task including the second identifier.

[0037] Through the computing service and data transmission process given by this method, the access network device can provide corresponding transmission configuration for the computing task requested by the terminal device, so that the execution of the computing task and the transmission of data are both reliable.

[0038] In a fifth aspect, a communication method is provided. The method can be executed by a user-plane network element, or by a component of the user-plane network element, such as a processor, chip, or chip system of the user-plane network element. The method can also be implemented by a logic module or software that can implement all or part of the user-plane network element. The method includes: receiving a third request message from a first network element, the third request message being used to request the user-plane network element to establish a tunnel with an access network device for transmitting data of a first task, the third request message including a first QoS configuration for establishing the tunnel. The data of the first task is transmitted using the tunnel.

[0039] In a possible design solution, the third request message may further include first information, where the first information is used to indicate filtering and mapping rules for transmitting data of the first task.

[0040] In one possible design scheme, the first information may include at least one of the following: application port information, a first parameter group, or a QoS flow template; wherein the application port information includes the application port number of the first terminal device and the application port number of the first computing node, the first parameter group includes the Internet Protocol IP address of the first terminal device, the application port number of the first terminal device, the data transmission protocol type corresponding to the first service, the IP address of the first computing node and the application port number of the first computing node, the QoS flow template includes filtering and mapping rules corresponding to multiple different parameter groups, and the multiple different parameter groups include the first parameter group.

[0041] In one possible design, using a tunnel to transmit data of a first task may include: mapping the IP data stream of the first task into a first QoS stream based on a first parameter group and / or a QoS stream template, where the first parameter group includes the IP address of a first terminal device, the application port number of the first terminal device, the data transmission protocol type corresponding to the first service, the IP address of a first computing node, and the application port number of the first computing node, the first computing node being a computing node executing the first task, and the first service being related to the first task. Using a tunnel to transmit the first QoS stream.

[0042] In one possible design, transmitting data of the first task using a tunnel may include: receiving an IP data stream of the first task from a first computing node, the IP data stream of the first task including a second identifier, the second identifier corresponding to the first task, the first computing node being a computing node executing the first task, and transmitting the IP data stream of the first task using the tunnel.

[0043] Through the computing service and data transmission process given by this method, a data transmission tunnel for computing tasks requested by terminal devices can be provided between the user-plane network element and the access network device, and the data stream can be filtered and mapped, so that the execution of computing tasks and the transmission of data are both reliable.

[0044] In the sixth aspect, a communication device is provided for implementing the various methods described above. The communication device may be the first network element in the first aspect or the first terminal device in the second aspect or the first computing node in the third aspect or the second device in the fourth aspect or the user plane network element in the fifth aspect, or a device including the first network element or the first terminal device or the first computing node or the second device or the user plane network element, or a device included in the first network element or the first terminal device or the first computing node or the second device or the user plane network element, such as a chip. The communication device includes corresponding modules, units, or means for implementing any of the methods described in the first to fifth aspects, and the modules, units, or means may be implemented by hardware, software, or by executing corresponding software implementations through hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0045] In some possible designs, the communication device includes: a transceiver module and a processing module. The transceiver module is used to perform the transceiver function of the communication device described in the sixth aspect. The processing module is used to perform functions of the communication device described in the sixth aspect other than the transceiver function.

[0046] In one possible design solution, the transceiver module may include a receiving module and a sending module, wherein the sending module is used to implement the sending function of the communication device described in the sixth aspect, and the receiving module is used to implement the receiving function of the communication device described in the sixth aspect.

[0047] In one possible design, the communication device described in aspect 6 may further include a storage module storing a program or instruction. When the processing module executes the program or instruction, the communication device described in aspect 6 may execute the method described in any one of aspects 1 to 5.

[0048] In a seventh aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided. The communication device includes: a processor configured to implement the functions involved in any of the above aspects.

[0049] In one possible design, the communication device may further include a memory for storing necessary program instructions and data. A processor is coupled to the memory, and the processor is configured to execute the computer program or instructions stored in the memory, causing the communication device to perform the method described in any possible implementation of aspects 1 to 5.

[0050] In one possible design solution, the communication device described in the seventh aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the seventh aspect to communicate with other communication devices.

[0051] In one possible design, the processor can be integrated with the memory.

[0052] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0053] In an eighth aspect, a communication device is provided, which includes a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, and the processor being used to implement the method described in any possible implementation method of the first to fifth aspects through a logic circuit or executing code instructions.

[0054] It can be understood that when the communication device provided in either the seventh aspect or the eighth aspect is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0055] In the ninth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the first to fifth aspects above.

[0056] In a tenth aspect, a computer program product comprising instructions is provided, including computer program code, which, when the computer program code is run on a communication device, enables the communication device to execute the method described in any one of the first to fifth aspects above.

[0057] In the eleventh aspect, a communication system is provided, comprising: a first network element for implementing the method described in the first aspect above, a first terminal device for implementing the method described in the second aspect above, and a first computing node for implementing the method described in the third aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] FIG1 is a schematic diagram of the architecture of an XaaS system;

[0059] Figure 2 is a diagram of a computing power network architecture that can be used to schedule computing tasks;

[0060] FIG3 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0061] FIG4 is a flow chart of a communication method provided in an embodiment of the present application;

[0062] FIG5 is a flow chart of another communication method provided in an embodiment of the present application;

[0063] FIG6 is a flow chart of another communication method provided in an embodiment of the present application;

[0064] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0065] FIG8 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The embodiments of the present application will present various aspects, embodiments, or features around a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these solutions may also be used.

[0067] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless fidelity (Wi-Fi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) communication systems, Internet of Vehicles communication systems, world-wide interoperability for microwave access (WiMAX) communication systems, 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, world-wide interoperability for microwave access (WiMAX) communication systems, fifth generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as sixth generation (6G) mobile communication systems.

[0068] As industries like healthcare, factories, ports, coal mines, and government and enterprises accelerate their digital transformation, computing and communications are becoming core foundational capabilities that empower these industries' digital transformations. Consequently, operators have proposed the concept of a computing network and are conducting standardization discussions within the 3GPP. The concept of a computing network aims to enable ubiquitous computing and services through network awareness, dispatching computing tasks to appropriate computing nodes for processing. This improves the utilization efficiency of network and computing resources, while providing users with low-latency and highly reliable services to ensure a positive user experience.

[0069] The IMT-2030 (6G) Promotion Group believes that 6G services will be immersive and intelligent, driven by the low latency demands of immersive services like extended reality (XR) and holographic displays, as well as the real-time processing of massive amounts of data required by intelligent services like robotics, intelligent agents, and large AI-generated content (AIGC) models. The IMT-2030 (6G) Promotion Group believes that 6G services will be immersive and intelligent. 6G networks will need to support the scheduling of AI resources and the processing of extremely large amounts of data to reduce the computational load and energy consumption of terminal devices, thereby meeting the requirements for lighter, more immersive, and more intelligent devices. Therefore, the IMT-2030 (6G) Promotion Group proposes the XaaS architecture, shown in Figure 1. Within this architecture, communication equipment features exposed capabilities, collaborative control, orchestration management, and security, transforming the 6G network architecture from a "connection-centric" to a "task-centric" one.

[0070] Traditional "connection-centric" network architectures are designed to provide the connection channels required for data communication between terminal devices and between terminal devices and application servers, as well as corresponding lifecycle management mechanisms (such as the creation, modification, deletion, and anchor migration of end-to-end communication tunnels) and communication quality of service (QoS) guarantees. For example, the connection establishment method of the 5G network, namely the protocol data unit (PDU) session establishment process, is to provide a transmission channel for data transmission between terminal devices and application servers located in the data network (DN). This includes establishing a data radio bearer (DRB) between the terminal device and the radio access network (RAN) and the NG interface user plane channel (NG-U Tunnel) between the RAN and the user plane function (UPF) of the core network, and providing corresponding QoS guarantees.

[0071] A mission-centric network architecture requires not only connectivity but also coordination and deployment of the computing power, connections, algorithms, and data resources of network nodes to achieve a specific goal. 6G networks provide computing services by introducing computing power, storage resources, and mechanisms for multi-node coordination of computing power, algorithms, and data.

[0072] As shown in Figure 2, a computing power network architecture that can be used to schedule computing tasks is shown. It utilizes the connectivity capabilities of wireless networks and the widespread computing power within the network to provide high-performance computing power, low-latency transmission, and intelligent business assurance services for diverse computing services. In the architecture shown in Figure 2, terminal devices or third-party applications can send computing service requests to the computing management function (CMF) deployed on the RAN side. The CMF can perform computing power perception, computing business perception, network status perception, and computing task scheduling based on the computing service request. The CMF can dispatch services initiated by network elements, external networks, or third-party applications to computing nodes such as terminal devices, mobile edge computing (MEC) platforms, cloud servers, and RAN equipment for execution.

[0073] In this process, the network needs to schedule computing nodes to perform the computing tasks offloaded by the terminal devices and establish data transmission channels between the computing nodes and the terminal devices. However, it is currently unclear how the network provides corresponding task allocation and data transmission configuration based on the different computing service requests of the terminal devices.

[0074] To this end, an embodiment of the present application provides a communication method that can provide corresponding task allocation and corresponding data transmission configuration for different computing service requests of terminal devices.

[0075] In order to better understand the embodiments of the present application, the following explanations are made before introducing the embodiments of the present application.

[0076] First, in the embodiments of the present application, "used to indicate" can include being used for direct indication and being used for indirect indication. When describing a certain "indication information" as being used to indicate A, it can include the indication information directly indicating A or indirectly indicating A, and does not necessarily mean that the indication information carries A.

[0077] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, it is also possible to use the arrangement order of each piece of information agreed in advance (such as specified in the protocol) to achieve the indication of specific information, thereby reducing the indication overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and indicate them uniformly to reduce the indication overhead caused by indicating the same information separately.

[0078] In addition, the specific indication method can also be various existing indication methods, such as but not limited to the above-mentioned indication methods and various combinations thereof. The specific details of the various indication methods can be referred to the prior art and will not be repeated herein. As can be seen from the above, for example, when it is necessary to indicate multiple information of the same type, there may be a situation where the indication methods for different information are different. In the specific implementation process, the required indication method can be selected according to specific needs. The embodiment of the present application does not limit the selected indication method. In this way, the indication method involved in the embodiment of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the information to be indicated.

[0079] The information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in this application. Among them, the sending period and / or sending time of these sub-information can be predefined, for example, predefined according to the protocol, or configured by the transmitting device by sending configuration information to the receiving device. Among them, the configuration information can, for example, but not limited to, include one or a combination of at least two of radio resource control (RRC) signaling, MAC layer signaling and physical layer signaling. Among them, MAC layer signaling, for example, includes MAC-CE; physical (PHY) layer signaling, for example, includes downlink control information (DCI).

[0080] Second, in the embodiments of the present application, the first, second, and various numerical numbers are merely distinctions for ease of description and are not intended to limit the scope of the embodiments of the present application. For example, different indication information is distinguished. For another example, the first indication information and the second indication information are merely for distinguishing different indication information and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different.

[0081] Third, in the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that the device (such as a terminal device or an access network device) will make corresponding processing under certain objective circumstances. It does not limit the time, and does not require the device (such as a terminal device or an access network device) to have a judgment action when implementing it, nor does it mean that there are other limitations.

[0082] At the same time, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0083] Finally, the network architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0084] Please refer to Figure 3, which is a schematic diagram of the architecture of the communication system used in the embodiment of the present application. As an example, as shown in Figure 3, the communication system includes a first terminal device, a first network element and a first computing node, and the first terminal device, the first network element and the first computing node can communicate with each other. Figure 3 exemplarily shows a terminal device and a computing node. The embodiment of the present application does not limit the number of terminal devices and computing nodes. Terminal devices can communicate with each other, and computing nodes can also communicate with each other.

[0085] In the embodiment of the present application, the first service may be a computing service, a data service, etc., without limitation. The first computing node may be a communication device or equipment with computing capabilities in the communication system, such as a terminal device, an access network device, a core network device, an MEC platform deployed at the edge of the network, and an application server deployed in a data network (DN), etc., without limitation.

[0086] Exemplarily, a first terminal device sends a first request to a first network element, and the first network element receives the first request from the first terminal device. The first request requests provision of a first service and includes a first identifier and the QoS requirements of the first service. The first identifier is used to distinguish multiple first requests, each corresponding to a different first identifier. Consequently, the first network element sends a second request to a first computing node based on the first request. The first computing node receives the second request from the first network element and sends a second response to the first network element based on the second request. The second request requests the first computing node to perform a first task associated with the first service and includes a second identifier that identifies the first task. The second response indicates that the first computing node has accepted the first task. Furthermore, the first network element sends a first response to the first terminal device based on the second response, and the first terminal device receives the first response from the first network element. The first response indicates acceptance of the first service and includes the first identifier and a second identifier associated with the first identifier. The specific implementation process can be found in the description of the following method embodiment, and is not described in detail here.

[0087] It should be understood that in the embodiments of the present application, the computing nodes scheduled by the first network element to perform the first task may be one or more. In the following embodiments, the scheduled computing node is taken as the first computing node as an example for explanation. The first computing node may be any one of the at least one computing node scheduled by the first network element.

[0088] The communication equipment and network elements involved in the embodiments of the present application are described below.

[0089] 1. Terminal equipment

[0090] The terminal device may be one or more, such as a first terminal device, a second terminal device, a third terminal device, etc. The terminal device may be a terminal device with transceiver functions, or may be a chip or chip system provided in the terminal device. The terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit (subscriber unit), subscriber station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application can be a mobile phone, a cellular phone, a smart phone, a tablet computer, a wireless data card, a personal digital assistant (PDA), a wireless modem, a handheld device (handset), a laptop computer, a machine type communication (MTC) terminal, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a smart home device (for example, a refrigerator, a television, an air conditioner, an electric meter, etc.), an intelligent robot, a robotic arm, a workshop equipment, a wireless terminal in unmanned driving, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a vehicle-mounted terminal, a roadside unit with terminal function, a roadside control unit (ROU), ... The terminal device of the present application may also be an onboard module, onboard module, onboard component, onboard chip or onboard unit built into a vehicle as one or more components or units. The terminal device may also be other devices with terminal functions, for example, a terminal device may also be a device that functions as a terminal in D2D communication.

[0091] The embodiments of this application do not limit the device form factor of the terminal. The device used to implement the functions of the terminal device can be the terminal device; it can also be a device that supports the terminal device to implement the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or include chips and other discrete devices.

[0092] 2. Access network equipment

[0093] There may be multiple access network devices, such as a first access network device, a second access network device, a third access network device, etc. The access network device may also be referred to as an access network node, a RAN node, a RAN entity or an access node, etc., which is located on the network side of the above-mentioned communication system to help the terminal device achieve wireless access, and has a device with wireless transceiver function or a chip or chip system that can be set in the device. The access network device includes but is not limited to: a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP or transmission point, TP), a next generation NodeB (gNB), a next generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a Wi-Fi system, etc. The access network device may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, an open radio access network (ORAN) or a wireless controller in a centralized radio access network (CRAN) scenario. The access network device may also be one or a group of antenna panels (including multiple antenna panels) of a base station in 5G, or it may also be a network node constituting a gNB, TRP or TP or transmission measurement function (TMF), such as a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), a road side unit (RSU) with base station functions. Optionally, the access network device may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in V2X technology may be an RSU. All or part of the functions of the network device in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The access network device in this application may also be a logical node, a logical module or software that can implement all or part of the functions of the access network device.

[0094] Among them, the CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, for example, a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH). It can be understood that the access network device can be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into a network device in the access network RAN, or the CU can be divided into a network device in the CN, which is not limited here.

[0095] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0096] The embodiments of this application do not limit the form of the access network device. The device used to implement the functions of the access network device can be the access network device; it can also be a device that supports the access network device to implement the functions, such as a chip system. The device can be installed in the access network device or used in conjunction with the access network device.

[0097] 3. First Network Element

[0098] The first network element is responsible for accepting computing service requests and executing computing task scheduling. It can have one or more of the following functions: computing power perception, computing business perception, network status perception or computing task scheduling, and can realize the orchestration and management of computing power resources. In the implementation of this application, the first network element can be deployed in the access network, can be deployed independently from the access network equipment, can be embedded in the access network equipment, such as embedded in the CU or DU of the access network equipment, or can be deployed in the core network, without limitation. For example, the first network element can be a task management function (TMF) or the CMF in Figure 2 above.

[0099] It should be understood that the communication system shown in Figure 3 may also include other core network elements, other terminal devices or other access network devices, such as user plane network elements, access and mobility management network elements, session management network elements, data management network elements, policy control network elements, network data analysis network elements, etc., without limitation. Among them, the user plane network element may be the UPF in 5G communication, the access and mobility management network element may be the access and mobility management function (AMF) in the 5G system, the session management network element may be the session management function (SMF) in the 5G system, the data management network element may be the unified data management (UDM) in the 5G system, the policy control network element may be the policy control function (PCF) in the 5G system, and the network data analysis network element may be the network data analysis function (NWDAF) in the 5G system.

[0100] It should be understood that the names of nodes, modules, devices or network elements in different scenarios or architectures or systems, as well as the names of communication interfaces between nodes, modules, devices or network elements are given as examples in the embodiments of the present application, and the possibility of name changes in future communication systems, scenarios or architectures is not excluded.

[0101] The communication method provided in the embodiment of the present application will be described in detail below with reference to Figures 4 to 6.

[0102] For example, Figure 4 is a flow chart of a communication method provided in an embodiment of the present application. The communication method is illustrated by taking the communication between the first terminal device, the first network element and the first computing node shown in Figure 3 as an example. Of course, the subject that executes the action of the first terminal device in the method can also be a device / module in the first terminal device, such as a chip, processor, processing unit, etc. in the first terminal device; the subject that executes the action of the first network element in the method can also be a device / module in the first network element, such as a chip, processor, processing unit, etc. in the first network element; the subject that executes the action of the first computing node in the method can also be a device / module in the first computing node, such as a chip, processor, processing unit, etc. in the first computing node; the embodiment of the present application does not make specific limitations on this.

[0103] Exemplarily, as shown in FIG4 , the communication method includes:

[0104] S401: A first terminal device sends at least one first request message to a first network element. Correspondingly, the first network element receives at least one first request message from the first terminal device.

[0105] The first request message is a service request initiated by the first terminal device. For example, one of the at least one first request message is used to request the first service, or each or any one of the at least one first request message is used to request the first service. In other words, the first terminal device can send one or more first request messages to the first network element to request the first network element to provide it with a service.

[0106] It should be noted that, in the embodiment of the present application, the first terminal device sending at least one first request message mainly refers to the first terminal device sending one first request message at a time, and the number of first request messages sent is also the number of times the first request message is sent. In some possible scenarios, the first terminal device sending at least one first request message may mean that the first terminal device sends one or more first request messages at a time.

[0107] Exemplarily, first services may include two main types. One type is computing services, such as AI inference services, AI training services, and AR rendering services. For this type of first service, the scheduled computing nodes primarily have computing power and transmission requirements. The service provision process may include: the first network element assigns a computing task related to the first service to the scheduled computing node; the computing node executes the computing task related to the first service and transmits the results of the computing task to the first terminal device. For example, if the first service is an AI inference service, the computing task may be an AI inference task. The other type is data services, such as perception services, positioning services, and AI model provision services. For this type of first service, the scheduled computing nodes primarily have transmission requirements. The service provision process may include: the first network element assigns a data task related to the first service to the scheduled computing node; the computing node obtains data or AI models related to the data task and transmits the data or AI model to the first terminal device. The data task may include, for example, perception measurements or positioning measurements.

[0108] It should be understood that in addition to the above two types of services, the first service can also be other types of first services, and there is no limitation on this. In addition, the first services corresponding to the multiple first request messages initiated by the first terminal device can be the same or different, or partially the same and partially different, and there is no limitation on this. For example, for the first request message 1 and the first request message 2 initiated by the first terminal device, the first services requested by the first request message 1 and the first request message 2 can both be AR rendering services, or the first service requested by the first request message 1 is AR rendering service, and the first service requested by the first request message 2 is AI model training service.

[0109] For at least one first request message initiated by the first terminal device, a first request message includes a first identifier and a QoS requirement of the first service (which may be referred to as a service QoS requirement). The first identifier corresponds to a first request message. In an embodiment of the present application, the first identifier may be an identifier (identity, ID) assigned by the first terminal device (or the client application on the first terminal device) for each first request message initiated. Each or any first request message in the at least one first request message initiated by the first terminal device corresponds to a first identifier, and the first identifier may be used to uniquely identify a first request message initiated by the first terminal device each time. In other words, multiple first request messages correspond to multiple different first identifiers, and the first identifier may be used to distinguish between multiple first request messages. It should be understood that different first identifiers may refer to different values ​​of the first identifier.

[0110] In one possible design, the first identifier can be represented by a special digital number, and the digital length, arrangement order, and digital size can be pre-configured or pre-defined by the protocol, or can be network configured, and there is no limitation on this.

[0111] Exemplarily, the first terminal device uses the precise moment of each initiation of the first request message as the first identifier of the first request message initiated this time. For example, if the first terminal device initiates a first request message at 09:21:13 on October 19, 2023, such as the first request message 1 in the above example, and initiates a first request message at 23:24:25 on October 19, 2023, such as the first request message 2 in the above example, then the first identifier corresponding to the first request message 1 can be expressed as 20231019092113, and the first identifier corresponding to the first request message 2 can be expressed as 20231019232425. Thus, the first identifier can be used to identify or distinguish first request messages sent by the first terminal device at different times, or to identify or distinguish multiple first request messages sent by the first terminal device.

[0112] The QoS requirement of the first service is used to indicate the service quality requirement of the first terminal device for completing the first service, or to ensure the service quality of the first service, and serves as a basis for the first network element scheduling computing node. Different first services correspond to different QoS requirements. The QoS requirement can refer to the QoS requirement for a single service or a class of services, without limitation.

[0113] In an embodiment of the present application, the QoS requirement of the first service may be generated by the first terminal device, or may be obtained by the first terminal device from a core network element (such as a policy control network element), which is not limited to this. The QoS requirement of the first service may include a communication QoS requirement and / or a computing QoS requirement. Among them, the communication QoS requirement may include a transmission delay requirement, a transmission reliability requirement, etc. The transmission delay requirement may include a time requirement for completing data transmission related to the first service, and the transmission reliability requirement may include requirements for the bit error rate, jitter, packet loss rate, etc. of the transmission. For example, the communication QoS requirement may be represented by a 5G QoS indicator (5G QoS identifier, 5QI) communication parameter defined by 5G NR, such as a communication QoS requirement may include an uplink / downlink packet delay budget (packet delay budget uplink / downlink, UL / DL PDB), a guaranteed bit rate (guarantee bit rate, GBR), a maximum data burst volume (maximum data burst volume, MDBV), a packet error rate (packet error rate, PER), etc., to indicate the demand for communication.

[0114] Computing QoS requirements are mainly used to characterize the computing power QoS requirements for computing nodes. Computing QoS requirements can include requirements such as computing load (or load, payload), computing latency, computing energy consumption, and computing accuracy.

[0115] The computational load requirement may indicate (or reflect, or represent) the computational capability requirement for the computing node, and may be expressed as the computational capability requirement for the processor. The computational capability of the processor may include the number of operations per second (OPS) or floating-point operations per second (FLOPS) that the processor can perform per second (s), the processor model, memory capacity, input / output (I / O) speed, or main frequency, etc. For example, the computational load requirement may include the required main frequency in hertz (Hz) or gigahertz (GHz), the required number of read / write operations per second (IOPS) in gigabits per second (Gbits / s), and the required memory capacity in bytes.

[0116] The computational latency requirement may indicate (or reflect, or express) the time requirement for completing a computational task, such as how long it takes to complete the computational task.

[0117] The demand for computing energy consumption may also indicate (or reflect, or represent) computing power consumption demand, which may refer to the requirement for the power or energy consumed by the device that performs the computing task. For example, the computing task may be performed by an access network device, and the demand for computing power consumption may include the computing power consumption requirement for the access network device. The computing power consumption requirement for the access network device may be the requirement for the average computing power consumption of the access network device to perform tasks within a period of time, and the duration for calculating the average computing power consumption may be predefined or preconfigured. Alternatively, the computing power consumption requirement may also be the requirement for the computing power consumption of the access network device after completing a processing or within a short period of time (such as processing a video frame or a task). The computing power consumption may also be converted into a corresponding computing energy consumption indicator, and the unit may be a convertible unit such as watts or joules.

[0118] Computational accuracy requirements can indicate (or reflect, or express) the required error between the calculated result and the actual result, such as a maximum error of 5%. Alternatively, computational accuracy requirements can refer to the accuracy requirements for inference / training results obtained through inference or training using AI models / algorithms.

[0119] It should be understood that the first request message may also include an identifier of the first service for the first network element to identify which first service the first terminal device is requesting, as well as information indicating the request for the first service.

[0120] In one possible implementation, the first request message may further include information for implementing data transmission related to the first service. For example, the first request message may further include second information, which may include at least one of the following: an Internet Protocol (IP) address of the first terminal device, an application port number of the first terminal device, or a data transmission protocol type corresponding to the first service.

[0121] Among them, the IP address of the first terminal device is used to determine the location of the first terminal device, the application port number of the first terminal device is the application port number corresponding to the application related to the first service on the first terminal device, and the IP address of the first terminal device and the application port number of the first terminal device can be used for the computing node scheduled by the first network element (such as the first computing node described below) to accurately locate the first terminal device and transmit data related to the first service to the first terminal device.

[0122] The data transmission protocol type corresponding to the first service is used to indicate the protocol used when transmitting data related to the first service. The data transmission protocol type may include a Transmission Control Protocol (TCP) type or a User Datagram Protocol (UDP) type. In some possible scenarios, the data transmission protocol type corresponding to the first service may be predefined or preconfigured. In this case, the first request message may not carry the data transmission protocol type corresponding to the first service.

[0123] In this implementation, after completing the computing node selection, the first network element may send the second information to the selected computing node. Exemplarily, the first network element sends the second information to the first computing node, and correspondingly, the first computing node receives the second information from the first network element.

[0124] It should be understood that the first request message can reuse messages defined in existing protocols or existing implementations. The type of the first request message is related to the deployment of the first network element. For example, if the first network element is deployed on the access network device to which the first terminal device belongs, the first request message can be an RRC message or a MAC message, etc. For another example, if the first network element is deployed on the session management network element in the core network, the first request message can be a PDU session establishment request message, etc., and there is no limitation on this; the first request message can also be a newly defined message, such as a computing service request message, a service request message, etc., and there is no limitation on this.

[0125] S402: The first network element sends a second request message to the first computing node according to the first request message. Correspondingly, the first computing node receives the second request message from the first network element.

[0126] After receiving a first request message, the first network element will initiate a corresponding second request message based on the first request message. The number of second request messages is related to the number of computing nodes scheduled by the first network element. In the embodiment of the present application, taking the first computing node as an example, the second request message is used to request the first computing node to perform a first task related to the first service.

[0127] Among them, the first task can be any one of one or more tasks associated with the first service, which can be understood as the implementation of the first service is based on the implementation of one or more associated tasks. For multiple different first tasks associated with the first service, each first task corresponds to a QoS requirement, and the QoS requirement of the first task can be determined based on the QoS requirement of the first service. The first network element can schedule the computing node to execute the corresponding first task based on the QoS requirement of each first task.

[0128] Exemplarily, for the first request message 1 in the above example, the first service is an AR rendering service, and the first task associated with the AR rendering service may include task 1, task 2, and task 3. The first network element may combine the computing power status of each computing node in the perceived network, the network status between each computing node and the first terminal device, and the network status between computing nodes, etc., to select a computing node that meets the QoS requirements of the first task to execute the corresponding first task, and send corresponding second request messages to the selected three computing nodes (including the first computing node) respectively.

[0129] In one possible implementation, the one or more first tasks associated with the first service may be obtained by the first network element performing task division for the implementation of the first service. In this implementation, the QoS requirement of each first task may be determined by the first network element based on the QoS requirement of the first service.

[0130] In another possible implementation, the one or more first tasks associated with the first service may also be obtained by dividing the implementation of the first service by the first terminal device. In this implementation, the QoS requirements of the first service may include the QoS requirements corresponding to the one or more first tasks, the second identifier of each first task may be assigned by the first terminal device, and the first request message may include the second identifier of each second task.

[0131] In response to a first request message, the first network element sends a second request message to the first computing node, including a second identifier. The second identifier corresponds to the first task, and the second identifier is associated with the first identifier corresponding to the first request message. There are two designs for how the second identifier corresponds to the first task:

[0132] Design 1: The second identifier is used to identify a first task, and different first tasks correspond to different second identifiers. In other words, the first network element assigns a second identifier to each different first task. In this Design 1, if the first tasks in multiple second request messages sent by the first network element are the same, then the second identifiers in the multiple second request messages are the same.

[0133] In one possible scenario, the first service requested by the two first request messages received by the first network element is the same, then the first task divided by the first network element for the first service requested by the two first request messages can be the same, then for the two first request messages, the second identifiers in the two second request messages sent by the first network element to the first computing node respectively can be the same, or, the second identifiers in the second request messages sent by the first network element to two different computing nodes (such as the first computing node and the second computing node) respectively can be the same.

[0134] In a specific example, referring to the above example, the first service requested by the first request message 1 is associated with tasks 1 to 3, then the first network element can assign a second identifier to tasks 1 to 3 respectively, such as the second identifier of task 1 is Task1 ID, the second identifier of task 2 is Task2 ID, and the second identifier of task 3 is Task3 ID, then Task1 ID to Task3 ID are associated with the first identifier of the first request message 1 (such as 20231019092113 in the above example), and the first network element can send corresponding second request messages to the three computing nodes (including the first computing node) for the first request message 1. Taking the second request message corresponding to the first computing node as an example, which is used to request the first computing node to execute task 1, the second request message includes Task1 ID.

[0135] For the above-mentioned design 1, in one possible implementation method, the QoS requirement of the first task has a corresponding relationship with the second identifier (referred to as a first corresponding relationship), and the first corresponding relationship can be pre-configured in the first network element in the form of a table. Exemplarily, the first corresponding relationship is shown in Table 1 below. The first service is associated with three first tasks (task 1 to task 3), and the QoS requirement of each first task corresponds to a second identifier, that is, the first corresponding relationship includes the corresponding relationship of the second identifiers corresponding to multiple first tasks. Therefore, the first network element can determine the second identifier corresponding to the first task from the first corresponding relationship based on the obtained QoS requirement of the first task.

[0136] Table 1

[0137] It should be understood that for different first services, the first network element may store a plurality of correspondences between the QoS requirements of the first tasks associated with the first services and the second identifiers.

[0138] Design 2: The second identifier is used to identify the first task in a second request message. In this Design 2, the second identifier is used to identify which second request message the first task corresponds to. The second identifier simultaneously identifies a second request message and a first task. The second identifier is used to uniquely identify the first task in a second request message. In other words, the first network element will assign a second identifier to the second request message corresponding to the first task related to the first service requested by a received first request message. It can be understood that the second identifier is used to identify a second request message. Therefore, whether the first network element is sending a first request service, multiple first request messages requesting the same first service, or multiple first request messages requesting different first services, the second identifiers in the multiple second request messages sent by the first network element are different.

[0139] In a specific example, referring to the above example, the first service requested by the first request message 1 is associated with tasks 1 to 3. For tasks 1 to 3, the first network element sends corresponding second request messages 1 to 3 to the three computing nodes respectively. For example, computing node 1 corresponds to second request message 1, which is used to request computing node 1 to perform task 1, and second request message 1 includes Msg-Task1 ID for identifying the second request message 1 and task 1; computing node 2 corresponds to second request message 2, which is used to request computing node 2 to perform task 2, and second request message 2 includes Msg-Task2 ID for identifying the second request message 2 and task 2; computing node 3 corresponds to second request message 2, which is used to request computing node 3 to perform task 3, and second request message 3 includes Msg-Task3 ID for identifying the second request message 3 and task 3. Therefore, Msg-Task1 ID to Msg-Task3 ID are associated with the first identifier of the first request message 1 (such as 20231019092113 in the above example). Taking the second request message corresponding to the first computing node as the second request message 1 as an example, the second request message includes Msg-Task1 ID, which is used to identify the first task in the second request message 1.

[0140] Optionally, the second request message may also include the QoS requirements of the first task, so that the first computing node can determine whether it can accommodate or accept the execution of the first task based on the QoS requirements of the first task, and after determining that it can accept or accept the execution of the first task, the first computing node can transmit data related to the first task according to the QoS requirements of the first task to ensure the QoS of the first service. The specific implementation process can be found in the relevant description in S403 below, which will not be repeated here.

[0141] In some possible scenarios, the first computing node is also pre-configured with the above-mentioned first correspondence. In this case, the second request message may not carry the QoS requirements of the first task. The first computing node can determine the QoS requirements of the first task based on the second identifier and the first correspondence for executing the first task.

[0142] S403: The first computing node sends a second response message to the first network element according to the second request message. Correspondingly, the first network element receives the second response message from the first computing node.

[0143] The second response message may be a response message to the second request message in S402 above. In an embodiment of the present application, after receiving the second request message, the first computing node may determine whether it is acceptable to execute the first task based on the QoS requirement of the first task in the second request message, and send a second response message to the first network element, where the second response message is used to indicate whether the first computing node accepts to execute the first task.

[0144] If the first computing node accepts to execute the first task, the second response is used to indicate that the first computing node accepts to execute the first task; if the first computing node does not accept to execute the first task, the second response is used to indicate that the first computing node does not accept to execute the first task.

[0145] In one possible implementation, the second response carries first indication information, which is used to indicate whether the first computing node accepts to execute the first task. The first indication information can be indicated by 1 bit, and the bit value is 1 to indicate acceptance of the execution of the first task, and the bit value is 0 to indicate rejection of the execution of the first task. Alternatively, the bit value is 0 to indicate acceptance of the execution of the first task, and the bit value is 1 to indicate rejection of the execution of the first task. There is no limitation on this.

[0146] Exemplarily, the first computing node can determine whether it can accept the first task currently received in the first request based on the QoS requirements of the first task, the current network status, computing resource usage, and the estimated computing resource usage in the future. If the first computing node determines that there are sufficient computing resources available currently and in the future, it accepts the first task and reserves sufficient computing resources for executing the first task. Among them, the computing resource usage may include the usage of various processors, memory, disk, network bandwidth, power supply, etc., for example, the resource usage ratio, total resource utilization or the current number of processes. Various processors include central processing unit (CPU), graphics processing unit (GPU), neural network processing unit (NPU), tensor processing unit (TPU), etc.

[0147] If the first computing node does not accept to execute the first task, the first network element may reselect another computing node to send a second request message until a computing node that can accept to execute the first task is found. In the embodiment of the present application, the first computing node accepting to execute the first task is used as an example for description.

[0148] In one possible implementation, the second response message may also include information about the first computing node. The information about the first computing node may include the IP address of the first computing node and / or the application port number of the first computing node. The information about the first computing node is used to filter and map the data of the first task. In this implementation, the information about the first computing node can be used by the node or device that transmits the data of the first task to locate the position of the first computing node, and to filter and map the transmitted data of the first task. For example, the first network element may carry the acquired information about the first computing node in the first response message in the following S404 and send it to the first terminal device, or may send it to the first terminal device through other messages, so that the first terminal device can obtain the IP address and application port number of the first computing node, so as to filter out the data of the first task from the first computing node, and accurately send the data of the first task to the first computing node.

[0149] Optionally, the second response message may also include a QoS flow template (QoS flow template), which is used to filter and map the data of the first task. The QoS flow template includes filtering and mapping rules corresponding to multiple different parameter groups, and the filtering and mapping rules corresponding to the same parameter group may include filtering and mapping rules for uplink data, filtering and mapping rules for downlink data, and filtering and mapping rules applied to bidirectional data transmission. In addition, the multiple different parameter groups include a first parameter group, and the filtering and mapping rules corresponding to the first parameter group are used for filtering and mapping the data of the first task between the first terminal device and the first computing node. The first parameter group includes the IP address of the first terminal device, the application port number of the first terminal device, the IP address of the first computing node, the application port number of the first computing node, and the data transmission protocol type corresponding to the first service.

[0150] Exemplarily, the QoS flow template is specifically used to filter and map the IP data flow of the first task into a first QoS flow, or the QoS flow template is used to filter the IP data flow of the first task into a service data flow (SDF) and then map the SDF into the first QoS flow. The first QoS flow is the QoS flow corresponding to the first task.

[0151] In other words, each parameter group in the QoS flow template includes the IP address of the sending device, the application port number of the sending device, the IP address of the receiving device, the application port number of the receiving device, and the data transmission protocol type between the sending device and the receiving device. This is a five-tuple parameter group, and different parameter groups correspond to different filtering and mapping rules. It should be understood that during uplink transmission, the first terminal device acts as the sending device and the first computing node acts as the receiving device; during downlink transmission, the first terminal device acts as the receiving device and the first computing node acts as the sending device.

[0152] Thus, the QoS flow template can be generated by the first computing node and sent to the first network element. After the first network element obtains the QoS flow template, it can send the QoS flow template to the transmission node used to complete the data transmission of the first task between the first terminal device and the first computing node. The transmission node includes the first terminal device, and based on the type of the selected first computing node, the transmission node may also include an access network device to which the first terminal device belongs, a user plane network element, etc., which is not limited to this. For specific implementation, please refer to the relevant descriptions in the following scenarios 1 and 2, which are not limited to this.

[0153] S404: The first network element sends a first response message to the first terminal device according to the second response message. Correspondingly, the first terminal device receives the first response message from the first network element.

[0154] The first response message may be a response message to a first request message in the above S401. In an embodiment of the present application, the first response message is used to indicate the provision of the first service, and the first response message includes a first identifier and a second identifier. That is, for a first service requested by a first request message initiated by the first terminal device at a certain time, the first network element notifies the first terminal device of the second identifier allocated to the first service requested this time through the first response message, so that the first terminal device can obtain the second identifier associated with the first identifier corresponding to the first request message, so as to distinguish which first service the subsequently received transmission configuration information and the subsequently received data are for which first request message requesting the first service.

[0155] Exemplarily, after receiving the second response message, the first network element can determine based on the second response message that the first computing node is capable of performing the first task. If the first network element schedules multiple computing nodes to perform multiple first tasks related to the first service, then after the first network element receives the second response messages corresponding to all scheduled computing nodes, it can determine that there are computing nodes capable of performing the first tasks related to the first service. The first network element can then send a first response message to the first terminal device to inform the first terminal device of which first request message initiated by it has provided the first service.

[0156] Optionally, the first response message may further include information about the first computing node and / or a QoS flow template. The information about the first computing node includes the IP address of the first computing node and / or the application port number of the first computing node. The information about the first computing node and / or the QoS flow template are used to filter and map the data for the first task. Thus, the first terminal device may filter and map the data for the first task based on the information about the first computing node and / or the QoS flow template.

[0157] In some possible scenarios, the QoS flow template may be obtained by the first terminal device from the session management network element, or the QoS flow template may be generated by the first terminal device for uplink data based on the received downlink data, without limitation. In this case, the first response message may not carry the QoS flow template.

[0158] Thus, based on the above process, the first terminal device can obtain the second identifier associated with each first request message in at least one first request message initiated. For example, the first terminal device obtains the second identifiers associated with two first request messages from the first network element, such as the second identifiers associated with the first identifier corresponding to the first request message 1 are Task1 ID, Task2 ID and Task3 ID, and the second identifiers associated with the first identifier corresponding to the second request message 2 are Task4 ID and Task5 ID. Thus, the first terminal device can determine, based on the second identifier associated with each first identifier, which first service requested by the first request message for which the subsequently received transmission configuration information and transmission data are intended.

[0159] For the first service requested by the first request message, there are two scenarios for the data transmission configuration and data transmission process between the first terminal device and the first computing node:

[0160] In one possible scenario, the first computing node transmits the data for the first task to the first terminal device via a radio bearer, without requiring a user interface to transmit the data for the first task to the first terminal device. For example, the first computing node may be a second terminal device or an access network device to which the first terminal device belongs, and the second terminal device is different from the first terminal device.

[0161] In this scenario 1, after the first computing node determines to accept the execution of the first task, the first computing node can establish a transmission configuration with the first terminal device. In one possible design, the first computing node can send first configuration information to the first terminal device, and accordingly, the first terminal device receives the first configuration information from the first computing node. The first configuration information is used to configure the first terminal device to establish a wireless bearer for transmitting data of the first task with the first computing node, and the first configuration information includes a second identifier, which can be used to identify the wireless bearer corresponding to the first service requested by the first request message initiated by the first terminal device for which the first configuration information is sent.

[0162] It should be understood that when the first computing node is the second terminal device, the first computing node and the first terminal device communicate through the wireless bearer of the side link; when the first computing node is an access network device, the first computing node and the first terminal device communicate through the wireless bearer between the Uu interface.

[0163] In one possible implementation, the first configuration information may be carried in an RRC message or MAC signaling. For example, the first computing node may send an RRC reconfiguration message to the first terminal device, and the drb-ToAddModList field in the RRC reconfiguration message carries the first configuration information, and the first configuration information may be used to establish a corresponding packet data convergence protocol (PDCP) entity and configure relevant security parameters, establish and configure a radio link control (RLC) entity, establish and configure a dedicated traffic channel (DTCH) logical channel, etc. Furthermore, after the first terminal device completes the establishment of the radio bearer according to the first configuration information, it may send an RRC reconfiguration completion message to the first computing node to indicate that the radio bearer establishment is complete. In an embodiment of the present application, the first configuration information may include an uplink radio bearer configuration and a downlink radio bearer configuration, and the radio bearer mainly refers to a DRB.

[0164] After receiving the first configuration information, the first terminal device can determine which first identifier the second identifier in the first configuration information is associated with based on the second identifier in the first configuration information and the second identifier associated with the first identifier corresponding to at least one first request message obtained by the first network element based on the above S404, thereby determining which first service corresponding to which first request message sent the first configuration information corresponds to.

[0165] Referring to the above example, the first terminal device learns from the first network element that the second identifiers associated with the first identifier corresponding to the first request message 1 are Task1 ID, Task2 ID and Task3 ID, and the second identifiers associated with the first identifier corresponding to the second request message 2 are Task4 ID and Task5 ID. The second identifier in the first configuration information is Task1 ID. The first terminal device can determine that the first configuration information is the second identifier associated with the first identifier corresponding to the first request message 1 based on the second identifier in the first configuration information and the stored second identifiers associated with different first identifiers, that is, the first configuration information is the configuration information associated with the first identifier corresponding to the first request message 1, which is used to realize the transmission of data of the first task related to the first service requested by the first request message 1.

[0166] Thus, the first computing node and the first terminal device can use the radio bearer configured by the first configuration information to transmit data of the first task, which is described below for uplink transmission and downlink transmission respectively:

[0167] For upstream transmission:

[0168] In a possible implementation 1, the first terminal device may map the IP data stream of the first task into a first QoS stream based on the first parameter group and / or the QoS stream template, thereby transmitting the first QoS stream using the radio bearer configured with the first configuration information. For a detailed description of the first parameter group and the QoS stream template, please refer to the relevant description in S403 above and will not be repeated here.

[0169] Exemplarily, the first terminal device can determine the corresponding filtering and mapping rules from the QoS flow template based on the first parameter group, and filter and map the IP data flow of the first task generated by the application (APP) on the first terminal device to the first QoS flow according to the corresponding filtering and mapping rules, so that the first terminal device transmits the first QoS flow to the first computing node through the wireless bearer configured by the first configuration information (the first QoS flow has a mapping relationship with the wireless bearer configured by the first configuration information). Alternatively, the IP data flow generated by the APP on the first terminal device carries the first parameter group, and the first terminal device can determine the corresponding filtering and mapping rules from the QoS flow template based on the first parameter group in the IP data flow, and map the IP data flow to the first QoS transmitted through the wireless bearer configured by the first configuration information (the first QoS flow has a mapping relationship with the wireless bearer configured by the first configuration information).

[0170] In a possible implementation 2, the first terminal device may map the IP data stream of the first task to a first QoS stream based on the second identifier, and transmit the first QoS stream using the radio bearer configured with the first configuration information; or the first terminal device may transmit the IP data stream of the first task using the radio bearer configured with the first configuration information. The IP data stream of the first task includes the second identifier.

[0171] That is to say, the first terminal device can carry a second identifier in the IP data stream of the first task generated (such as generated by APP), and map the IP data stream to a first QoS stream transmitted by a wireless bearer configured by the first configuration information according to the second identifier (the first QoS stream has a mapping relationship with the wireless bearer configured by the first configuration information), or the first terminal device directly uses the second identifier in the IP data stream to transmit the IP data stream using the wireless bearer configured by the first configuration information associated with the second identifier to send data for executing the first task to the first computing node.

[0172] For downlink transmission:

[0173] In one possible implementation, the first computing node may generate an IP data flow or a first QoS flow of the first task carrying the second identifier, and transmit the IP data flow or the first QoS flow of the first task via a wireless bearer of the first configuration information associated with the second identifier. Alternatively, the first configuration information and the first QoS have a mapping relationship, and the first computing node may also map the IP data flow of the first task to the first QoS flow transmitted via the wireless bearer configured using the first configuration information.

[0174] In a possible scenario 2, the first computing node needs to transmit data of the first task to the first terminal device through the user. For example, the first computing node can be an application server or an MEC platform.

[0175] In this scenario, the first network element needs to trigger the user plane network element and the access network device to which the first terminal device belongs to establish a channel for transmitting data for the first task. In one possible design, the first network element sends a third request message to the user plane network element, and the user plane network element receives the third request message from the first network element. The third request message is used to request the user plane network element to establish a tunnel with the access network device for transmitting data for the first task. The third request message includes a first QoS configuration for establishing the tunnel, and the first QoS configuration is determined based on the QoS requirements of the first service.

[0176] Thus, after receiving the third request message, the user plane network element can establish a tunnel with the access network device according to the first QoS configuration in the third request message, for example, a general packet radio service (GPRS) tunneling protocol user plane part protocol (user plane part of GPRS tunneling protocol, GTP-U) tunnel, or referred to as an N3 tunnel. Exemplarily, the user plane network element can determine configuration information for tunnel establishment based on the first QoS configuration, and send the configuration information for tunnel establishment to the access network device. The configuration information for tunnel establishment may include relevant configuration information such as routing priority, congestion avoidance, packet filtering, and uplink or downlink rate control.

[0177] Optionally, the third request message may also include first information, and the first information is used to indicate filtering and mapping rules for transmitting data of the first task. Exemplarily, the first information may include at least one of the following: application port information, a first parameter group, or a QoS flow template; wherein the application port information includes the application port number of the first terminal device and the application port number of the first computing node. The specific description of the first parameter group and the QoS flow template can be found in the relevant description in S403 above, which will not be repeated here. It should be understood that the first information may also not be carried in the third request message, but may be sent by the first network element using other messages.

[0178] Thus, the user plane network element can filter and screen the data of the first task from the first computing node according to the first information, so as to accurately locate the first terminal device to send the data of the first task to it.

[0179] In some possible scenarios, the user plane network element may also obtain the QoS flow template from the session management network element, without obtaining it from the first network element. In addition, the application port information and the first parameter group may not be included in the third request message, but may be sent by the first network element through other messages, or pre-configured in the user plane network element.

[0180] Furthermore, the first network element sends a fourth request message to the access network device, and the access network device receives the fourth request message from the first network element. The fourth request message is used to request the access network device to establish a radio bearer with the first terminal device for transmitting data of the first task, and the fourth request message includes a second QoS configuration and a second identifier for establishing the radio bearer, where the second QoS configuration is determined based on the QoS requirement of the first service.

[0181] Furthermore, the access network device may send second configuration information to the first terminal device based on the second QoS configuration in the fourth request message, and accordingly, the first terminal device receives the second configuration information from the access network device. The second configuration information is used to configure the first terminal device to establish a wireless bearer for transmitting data of the first task between the first terminal device and the access network device. The second configuration information includes a second identifier. The specific description of the second configuration information can be found in the relevant description of the above-mentioned first configuration information, which will not be repeated here. In some scenarios, the second configuration information is the above-mentioned first configuration information.

[0182] After the data transmission channel between the user plane network element and the access network device and the data transmission channel between the access network device and the first terminal device are established based on the above process, the first computing node and the first terminal device implement data transmission of the first task based on the established data transmission channel.

[0183] In this scenario 2, there are still uplink transmission and downlink transmission. The following describes uplink transmission and downlink transmission respectively:

[0184] For upstream transmission:

[0185] The specific process of the first terminal device using the wireless bearer configured by the second configuration information to send the data of the first task to the access network device is similar to the process of the first terminal device using the wireless bearer configured by the first configuration information to send the data of the first task to the first computing node in the above scenario 1, and will not be repeated here. Furthermore, after the access network device receives the IP data stream or the first QoS stream of the first task, it can transmit the IP data stream or the first QoS stream of the first task to the user plane network element through the tunnel between the access network device and the user plane network element, and then the user plane network element sends it to the first computing node.

[0186] For downlink transmission:

[0187] In a possible implementation 1, the first computing node can send the IP data stream of the first task to the user plane network element. Accordingly, after the user plane receives the IP data stream, the user plane network element can map the IP data stream of the first task to a first QoS stream according to the first parameter group and / or the QoS flow template, and transmit the first QoS stream to the access network device using a tunnel. The access network device then transmits the first QoS stream to the first terminal device using the wireless bearer configured by the second configuration information.

[0188] Optionally, the IP data flow of the first task includes a first parameter group. In this case, the user-side network element can determine the corresponding filtering and mapping rules from the QoS flow template based on the first parameter group in the IP data flow, and map the IP data flow of the first task to the first QoS flow.

[0189] In a possible implementation 2, the first computing node can send an IP data stream of a first task carrying a second identifier to the user plane network element. Accordingly, after the user plane network element receives the IP data stream of the first task, it can map the IP data stream to a first QoS stream based on the second identifier in the IP data stream of the first task (the second identifier has a mapping relationship with the first QoS stream), and transmit the first QoS stream to the access network device using a tunnel, and then the access network device uses the wireless bearer configured by the second configuration information to transmit the first QoS stream to the first terminal device.

[0190] Mapping the IP data stream of the first task to the first QoS stream may include mapping the IP data stream of the first task to an SDF, and then mapping the SDF to the first QoS stream. In this embodiment of the present application, the data of the first task sent by the first terminal device may be input data for the first computing node to execute the first task, and the data of the first task sent by the first computing node may be an execution result obtained by the first computing node after completing the first task.

[0191] It can be seen from the above two scenarios that the first terminal device needs to receive the wireless bearer configuration to complete data transmission, but due to the difference in the first computing node, the device sending the wireless bearer configuration may be the first computing node or may not be the first computing node. Therefore, the above devices that send the wireless bearer configuration (such as the first configuration information and the second configuration information) can be collectively referred to as the second device.

[0192] In some possible situations, the above-mentioned wireless bearer configuration information may also include a first identifier. In this case, the first terminal device may determine the wireless bearer configuration information for which first request message corresponds to the wireless bearer configuration information based on the first identifier and the second identifier. When transmitting an IP data stream or a first QoS stream, the IP data stream or the first QoS stream may also carry the first identifier and the second identifier at the same time.

[0193] Based on the communication method shown in FIG4 above, in a scenario where the first terminal device sends multiple first request messages, the first network element associates the first identifier corresponding to any one of the multiple first request messages sent by the first terminal device with the second identifier corresponding to the first task related to the first service requested by the first request message, and notifies the first terminal device, so that the first terminal device can determine which first service requested by the first request message the transmission configuration of the first task related to the first service is for based on the second identifier associated with the first identifiers corresponding to different first request messages. In this way, the first network element can provide corresponding task allocation and data transmission configuration for each service request initiated by the first terminal device.

[0194] The communication method shown in FIG4 is described below in conjunction with a specific application scenario. For example, taking the first computing node as a gNB, the first terminal device as a UE, the first network element as a TMF, the first service as an AI training service, the first request message as a computing service request message, the first response message as a computing service response message, the second request message as a computing task request message, and the second response message as a computing task response message as an example, a computing service request initiated by the UE is described. As shown in FIG5, the communication method includes:

[0195] S501: UE sends a computing service request message to TMF. Correspondingly, TMF receives the computing service request from UE.

[0196] Among them, the computing service request message is used to request AI training service, and the computing service request message includes a first identifier and the QoS requirement of the AI ​​training service. The first identifier corresponds to the computing service request message, that is, the first identifier is used to identify the computing service request message.

[0197] For example, the UE sends the computing service request message at 09:21:13 on October 19, 2023 to request the AI ​​training service. The first identifier corresponding to the computing service request can be expressed as 20231019092113. The QoS requirements of the AI ​​training service can include communication QoS requirements, such as PDB and GFBR requirements, and computing QoS requirements, such as computing energy consumption and computing accuracy requirements.

[0198] It should be understood that the computing service request message may further include the IP address of the UE and the application port number corresponding to the first service, etc., for subsequent data transmission.

[0199] S502: The TMF sends a computing task request message to the gNB. In response, the gNB receives the computing task request message from the TMF.

[0200] The computing task request message is used to request the gNB to perform an AI training task related to the AI ​​training service. The computing task request includes a second identifier, which corresponds to the AI ​​training task and is associated with the first identifier.

[0201] Exemplarily, after receiving the computing service request message, the TMF may select the gNB as the computing node for executing the AI ​​training task associated with the AI ​​training service based on the QoS requirements of the AI ​​training service, the perceived computing power status of each computing node in the network, the network status between each computing node and the UE, and the network status between computing nodes, etc., and assign a corresponding second identifier to the AI ​​training task. The TMF associates the second identifier with the first identifier corresponding to the computing service request message in S501, thereby sending the computing task request message to the gNB. In this case, the QoS requirements of the AI ​​training service can be used as the QoS requirements of the AI ​​training task. The specific description of the second identifier can be found in the relevant description of S402 above and is not repeated here.

[0202] Optionally, the computing task request message may also include the QoS requirements of the AI ​​training task.

[0203] S503: The gNB sends a computing task response message to the TMF. In response, the TMF receives the computing task response message from the gNB.

[0204] The Computing Task Response message is used to instruct the gNB to accept and execute the AI ​​training task.

[0205] For example, after receiving the computing task request message, the gNB may make an acceptance decision and reserve resources for the AI ​​training task. For example, the gNB may determine whether to accept the currently received computing task request message based on its current computing resource usage and estimated computing resource usage over a period of time. If the computing task request message is accepted, the gNB may send a computing task response message to the TMF to indicate that the gNB accepts the execution of the AI ​​training task.

[0206] If the computing task request message is not accepted, the gNB may not send any information or message to the TMF. If the TMF does not receive a response from the gNB within a period of time, it may be considered that the gNB does not accept the execution of the AI ​​training task. Alternatively, the gNB may also send a computing task response message to the TMF. In this case, the computing task response message is used to indicate that the gNB does not accept the execution of the AI ​​training task. There is no limitation on this.

[0207] S504: The TMF sends a computing service response message to the UE. Correspondingly, the UE receives the computing service response message from the TMF.

[0208] The computing service response message is used to indicate the provision of AI training services, and the computing service response message includes a first identifier and a second identifier.

[0209] Exemplarily, after the TMF determines that the gNB accepts the AI ​​training task based on the computing task response message, it can send a computing service response message to the UE to indicate that the AI ​​training service requested by the corresponding computing service request message can be provided to the UE, and carry the second identifier associated with the first identifier of the corresponding computing service request message in the computing service response message.

[0210] S505. The gNB sends an RRC reconfiguration message to the UE. Accordingly, the UE receives the RRC reconfiguration message from the gNB.

[0211] The RRC reconfiguration message carries first configuration information, which includes a second identifier. The first configuration information is used to configure the UE to establish data transmission for AI training with the gNB.

[0212] For example, after the UE obtains the second identifier associated with a computing service request message initiated, the UE can determine whether the identifier carried by the first configuration information in the received RRC reconfiguration message is the second identifier associated with the first identifier of a computing service request message recently initiated. If it is an associated second identifier, it can be determined that the first configuration information is the configuration information associated with the corresponding computing service request message. Thus, the UE can establish a wireless bearer based on the first configuration information.

[0213] Furthermore, after completing the radio bearer configuration, the UE may send an RRC reconfiguration complete message to the gNB to indicate that the configuration is complete.

[0214] S506. The UE sends data for AI training to the gNB via the radio bearer configured with the first configuration information. Correspondingly, the gNB receives data for AI training from the UE via the radio bearer configured with the first configuration information.

[0215] Exemplarily, after determining that the first configuration information is the configuration information associated with the corresponding first identifier, the UE can use the radio bearer configured by the first configuration information to send data for AI training to the gNB as input data for the gNB to perform the AI ​​training task, thereby completing the AI ​​training and obtaining an AI training result (such as an AI inference model).

[0216] S507: The gNB sends the AI ​​training results to the UE via the radio bearer configured with the first configuration information. Correspondingly, the UE receives the AI ​​training results from the gNB via the radio bearer configured with the first configuration information.

[0217] Similarly, after completing the AI ​​training task, the gNB may also use the radio bearer configured by the first configuration information to send the AI ​​training results to the UE, thereby providing the first service to the UE.

[0218] In the scenario shown in Figure 5, the TMF offloads the UE's tasks to the gNB based on the UE's computing service request message. Data transmission needs to be implemented by the gNB. By allocating a corresponding second identifier to the corresponding computing service request, the TMF can provide the UE with corresponding task allocation and data transmission configuration for the specific computing service request.

[0219] For example, the first computing node is an MEC platform, the first terminal device is a UE, the first network element is a TMF, the user plane network element is a UPF, the access network device is a gNB, and the first service is an AI training service. As shown in FIG6 , the communication method includes:

[0220] S601: UE sends a computing service request message to TMF. Correspondingly, TMF receives the computing service request message from UE.

[0221] Among them, the computing service request includes the first identifier and the QoS requirement of the AI ​​training service. The specific description of the computing service request message can be found in the relevant description in the above S501, which will not be repeated here.

[0222] S602: TMF sends a computing task request message to the MEC platform. Correspondingly, the MEC platform receives the computing task request message from TMF.

[0223] Among them, the computing task request message is used to request the MEC platform to perform AI training tasks related to the AI ​​training service, and the computing task request message includes a second identifier corresponding to the AI ​​training task.

[0224] S603: The MEC platform sends a computing task response message to the TMF. Correspondingly, the TMF receives the computing task response message from the MEC platform.

[0225] The computing task response message is used to instruct the MEC platform to accept and execute the AI ​​training task.

[0226] Since the computing node that performs the AI ​​training task is the MEC platform, the MEC platform and the UE need to communicate through the data plane. Therefore, the TMF needs to trigger the UPF and gNB to establish a data plane channel, such as executing S605 and S606 below.

[0227] S604: The TMF sends a computing service response message to the UE. Correspondingly, the UE receives the computing service response message from the TMF.

[0228] The computing service response message is used to indicate the provision of AI training services, and the computing service response message includes a first identifier and a second identifier.

[0229] The specific implementation process of S602 to S604 can refer to the implementation process of S502 to S504 above, which will not be described in detail.

[0230] S605: The TMF sends a first data plane channel establishment request message to the UPF. Correspondingly, the UPF receives the first data plane channel establishment request message from the TMF.

[0231] Among them, the first data plane channel establishment request message is used to request the UPF to establish a tunnel between the gNB, and the first data plane channel establishment request message includes a first QoS configuration, and the first QoS configuration is configured according to the QoS requirements of the AI ​​training service.

[0232] Exemplarily, the UPF can send relevant configuration information for tunnel establishment determined according to the first QoS configuration to the gNB based on the first data plane channel establishment request message to complete the establishment of the N3 tunnel for data transmission for AI training tasks between the gNB and the UPF.

[0233] S606. The TMF sends a second data plane channel establishment request message to the gNB. In response, the gNB receives the second data plane channel establishment request message from the TMF.

[0234] Among them, the second data plane channel establishment request message is used to request the gNB to establish a radio bearer between the gNB and the UE, and the second data plane channel establishment request message includes the second QoS configuration and the second identifier.

[0235] Exemplarily, the gNB may send a radio bearer establishment configuration for transmitting data of the AI ​​training task to the UE according to the second data plane channel establishment request message and the second QoS configuration and the second identifier, such as executing S607 below.

[0236] The embodiment of the present application does not limit the execution order of the above S605 and S606. S605 and S606 can be executed simultaneously, or S605 can be executed first and then S606, or S606 can be executed first and then S605. In addition, S605 and S606 can also be executed before S604 or after S604, and this is not limited.

[0237] S607. The gNB sends an RRC reconfiguration message to the UE. Accordingly, the UE receives the RRC reconfiguration message from the gNB.

[0238] The RRC reconfiguration message carries first configuration information, which includes a second identifier. The first configuration information is used to configure the UE to establish data transmission for the AI ​​training task with the gNB. The specific implementation process of S607 can be found in the relevant description of S505 above and is not repeated here.

[0239] S608: The UE sends data for AI training to the MEC platform. Correspondingly, the MEC platform receives data for AI training from the UE.

[0240] Exemplarily, the UE first sends data for AI training to the gNB via the radio bearer configured with the first configuration information. Correspondingly, the gNB receives data for AI training from the UE via the radio bearer configured with the first configuration information.

[0241] In one possible implementation, the UE generates data for AI training in the form of an IP data stream, and uses IP five-tuple information or QoS flow to filter and map the IP data stream into a first QoS flow. The first QoS flow is then mapped to a radio bearer configured with the first configuration information and transmitted to the gNB. The IP five-tuple information is the above-mentioned first parameter group, which may include the UE's IP address, the UE's application port number, the MEC platform's IP address, the MEC platform's application port number, and the data transmission protocol type. The MEC platform's IP address and the MEC platform's application port number may be sent to the UE by the TMF, and the data transmission protocol type may be pre-configured or selected by the UE, without limitation. The QoS flow template may also be sent to the UE by the TMF, obtained in advance by the UE from the SMF, or generated by the UE for uplink data based on received downlink data, without limitation.

[0242] In another possible implementation, the UE generates data for AI training in the form of an IP data stream, carries the second identifier in the IP data stream, maps the IP data stream into a first QoS stream based on the second identifier, and then maps the first QoS stream to the radio bearer configured with the first configuration information for transmission to the gNB, or directly transmits the IP data stream carrying the second identifier to the gNB through the radio bearer configured with the first configuration information.

[0243] Furthermore, after the gNB receives the IP data flow or the first QoS flow carrying data for AI training, it can send it to the UPF through the N3 tunnel between it and the UPF, and then the UPF sends it to the MEC platform, so that the MEC platform can perform AI training tasks based on the data for AI training.

[0244] S609: The MEC platform sends the AI ​​training results to the UE. Correspondingly, the UE receives the AI ​​training results from the MEC platform.

[0245] For example, the MEC platform first sends the AI ​​training results to the UPF.

[0246] In one possible implementation, the MEC platform can send the AI ​​training results to the UPF in the form of an IP data stream, and carry a second identifier in the IP data stream. Thus, the UPF can map the IP data stream into a first QoS stream according to the second identifier, and send it to the gNB using the N3 tunnel, or directly send the IP data stream carrying the second identifier to the gNB through the N3 tunnel.

[0247] In another possible implementation, the MEC platform can send the AI ​​training results to the UPF in the form of an IP data stream, and the IP data stream carries IP five-tuple information. As a result, the UPF can determine the corresponding filtering and mapping rules from the QoS flow template based on the IP five-tuple information, and use the corresponding filtering and mapping rules to map the IP data stream into the first QoS flow, and send it to the gNB using the N3 tunnel. Among them, the MEC platform can obtain the UE's IP address, UE's application port number, and data transmission protocol type from the TMF to form the IP five-tuple information. The QoS flow template can be obtained by the UPF from the TMF or obtained in advance from the SMF, and there is no limitation on this.

[0248] Furthermore, the gNB can send the first QoS flow or IP data flow carrying the AI ​​training result to the UE through the radio bearer configured by the first configuration information to provide the first service.

[0249] In the scenario shown in Figure 6, the TMF offloads the UE's task to the MEC platform based on the UE's computing service request message. Data transmission needs to be implemented through the UPF and gNB. By allocating a corresponding second identifier to the corresponding computing service request, the UE can be provided with corresponding task allocation and data transmission configuration for a specific computing service request.

[0250] In each of the above embodiments, the method and / or step implemented by the first network element may also be implemented by a component that can be used for the first network element (e.g., a processor, chip, chip system, circuit, logic module, or software); the method and / or step implemented by the user plane network element may also be implemented by a component that can be used for the user plane network element (e.g., a processor, chip, chip system, circuit, logic module, or software); the method and / or step implemented by the access network device may also be implemented by a component that can be used for the access network device (e.g., a processor, chip, chip system, circuit, logic module, DU or software). Exemplarily, when the above When the executing entity of each embodiment is the DU in the access network device, the sending or receiving steps performed by the access network device can be replaced by the sending or receiving of the DU, and further can be the sending of the DU to the RU or the receiving of the DU from the RU; the methods and / or steps implemented by the first computing node can also be implemented by components that can be used for the first computing node (such as a processor, chip, chip system, circuit, logic module, or software); the methods and / or steps implemented by the first terminal device can also be implemented by components that can be used for the first terminal device (such as a processor, chip, chip system, circuit, logic module, or software).

[0251] The above mainly introduces the solutions provided by this application. Accordingly, this application also provides a communication device, which is used to implement the various methods in the above-mentioned method embodiments. The communication device can be the first network element in the above-mentioned method embodiments, or a device including the first network element, or a component that can be used for the first network element, such as a chip or chip system. Alternatively, the communication device can be the user plane network element in the above-mentioned method embodiments, or a device including the user plane network element, or a component that can be used for the user plane network element, such as a chip or chip system. Alternatively, the communication device can be the access network device in the above-mentioned method embodiments, or a device including the access network device, or a component that can be used for the access network device, such as a chip or chip system. Alternatively, the communication device can be the first computing node in the above-mentioned method embodiments, or a device including the first computing node, or a component that can be used for the first computing node, such as a chip or chip system. Alternatively, the communication device can be the first terminal device in the above-mentioned method embodiments, or a device including the first terminal device, or a component that can be used for the first terminal device, such as a chip or chip system.

[0252] In some embodiments, in order to implement the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware 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 this application.

[0253] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0254] Taking the communication device as the first network element or the first computing node or the first terminal device or the access network device in the above-mentioned method embodiment as an example, Figure 7 is a structural diagram of a communication device provided in an embodiment of the present application. As shown in Figure 7, the communication device 700 includes: a processing module 701 and a transceiver module 702. Among them, the processing module 701 is used to perform the processing function of the first network element or the first computing node or the first terminal device or the access network device in the above-mentioned method embodiment. The transceiver module 702 is used to perform the transceiver function of the first network element or the first computing node or the first terminal device or the access network device in the above-mentioned method embodiment.

[0255] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0256] Since the communication device 700 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0257] In one possible design solution, in the embodiment of the present application, the transceiver module 702 may include a receiving module and a sending module (not shown in FIG7 ), wherein the sending module and the receiving module are used to implement the sending function and the receiving function of the communication device 700 , respectively.

[0258] In one possible design, the communication device 700 may further include a storage module (not shown in FIG. 7 ) storing a program or instruction. When the processing module 701 executes the program or instruction, the communication device 700 may perform the functions of the first network element, the first computing node, the first terminal device, or the access network device in the method shown in FIG. 4 .

[0259] In some embodiments, the processing module 701 involved in the communication device 700 can be implemented by a processor or a processor-related circuit component, which can be a processor or a processing unit; the transceiver module 702 can be implemented by a transceiver or a transceiver-related circuit component, which can be a transceiver or a transceiver unit.

[0260] For example, FIG8 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device can be the first network element or the first computing node or the first terminal device or the access network device in the above-mentioned method embodiment, or it can be a chip (system) or other parts or components that can be set in the first network element or the first computing node or the first terminal device or the access network device. As shown in FIG8 , the communication device 800 may include a processor 801. In one possible design scheme, the communication device 800 may further include a memory 802 and / or a transceiver 803. The processor 801 is coupled to the memory 802 and the transceiver 803, such as by being connected via a communication bus.

[0261] The following is a detailed introduction to the various components of the communication device 800 in conjunction with FIG8 :

[0262] The processor 801 is the control center of the communication device 800 and can be a single processor or a collective term for multiple processing elements. For example, the processor 801 includes one or more central processing units (CPUs), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more microprocessors (digital signal processors, DSPs) or one or more field programmable gate arrays (FPGAs).

[0263] In one possible design, the processor 801 may execute various functions of the communication device 800 by running or executing software programs stored in the memory 802 and calling data stored in the memory 802 .

[0264] In a specific implementation, as an embodiment, the processor 801 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG8 .

[0265] In a specific implementation, as an embodiment, the communication device 800 may also include multiple processors, such as the processor 801 and the processor 804 shown in Figure 8. Each of these processors may be a single-core processor or a multi-core processor. The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0266] The memory 802 is used to store the software program for executing the solution of the present application, and the execution is controlled by the processor 801. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0267] In one possible design, the memory 802 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 802 can be integrated with the processor 801 or exist independently and be coupled to the processor 801 through an interface circuit (not shown in FIG8 ) of the communication device 800. This embodiment of the present application does not specifically limit this.

[0268] Transceiver 803 is used for communication with other communication devices. For example, if communication device 800 is a terminal device, transceiver 803 can be used to communicate with an access network device or another terminal device. For another example, if communication device 800 is a network device, transceiver 803 can be used to communicate with a terminal device or another network device.

[0269] In one possible design, transceiver 803 may include a receiver and a transmitter (not separately shown in FIG8 ), wherein the receiver is used to implement a receiving function, and the transmitter is used to implement a sending function.

[0270] In one possible design scheme, the transceiver 803 can be integrated with the processor 801, or it can exist independently and be coupled to the processor 801 through the interface circuit of the communication device 800 (not shown in Figure 8). This embodiment of the present application does not specifically limit this.

[0271] It should be noted that the structure of the communication device 800 shown in FIG8 does not constitute a limitation on the communication device. An actual communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0272] In addition, the technical effects of the communication device 800 can refer to the technical effects of the methods described in the above method embodiments, and will not be repeated here.

[0273] An embodiment of the present application further provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, the functions of the above-mentioned method embodiment are realized.

[0274] The embodiments of the present application also provide a computer program product, which implements the functions of the above method embodiments when executed by a computer.

[0275] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0276] 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 beyond the scope of this application.

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

[0278] In the several embodiments provided in this 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 merely a logical function division. In actual implementation, there may be other division methods, 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.

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

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

[0281] 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 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. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or an access 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 ROM, a random access memory RAM, a magnetic disk, or an optical disk.

[0282] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0283] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: The method comprises: Receiving at least one first request message from a first terminal device, wherein one first request message among the at least one first request message is used to request a first service, and the one first request message includes a first identifier and a quality of service QoS requirement of the first service, and the first identifier corresponds to the one first request message; Sending a second request message to the first computing node according to the first request message, where the second request message is used to request the first computing node to perform a first task related to the first service, and the second request message includes a second identifier, where the second identifier corresponds to the first task and is associated with the first identifier; receiving a second response message from the first computing node, where the second response message is used to indicate that the first computing node accepts to execute the first task; A first response message is sent to the first terminal device according to the second response message, where the first response message is used to indicate the provision of the first service, and the first response message includes the first identifier and the second identifier.

2. The method according to claim 1, characterized in that The method further comprises: Sending a third request message to a user plane network element, the third request message being used to request the user plane network element to establish a tunnel for transmitting data of the first task between the user plane network element and the access network device, the third request message including a first QoS configuration for establishing the tunnel; And, a fourth request message is sent to the access network device, the fourth request message is used to request the access network device to establish a wireless bearer for transmitting data of the first task between the access network device and the first terminal device, the fourth request message includes a second QoS configuration and the second identifier for establishing the wireless bearer, and the first QoS configuration and the second QoS configuration are determined according to the QoS requirements of the first service.

3. The method according to claim 2, characterized in that The third request message also includes first information, where the first information is used to indicate filtering and mapping rules for transmitting data of the first task.

4. The method according to claim 3, characterized in that The first information includes at least one of the following: application port information, a first parameter group, or a QoS flow template; wherein the application port information includes the application port number of the first terminal device and the application port number of the first computing node, the first parameter group includes the Internet Protocol IP address of the first terminal device, the application port number of the first terminal device, the data transmission protocol type corresponding to the first service, the IP address of the first computing node and the application port number of the first computing node, and the QoS flow template includes filtering and mapping rules corresponding to multiple different parameter groups, and the multiple different parameter groups include the first parameter group.

5. The method according to any one of claims 1 to 4, characterized in that The first request message further includes second information, and the second information includes at least one of the following: an IP address of the first terminal device, an application port number of the first terminal device, or a data transmission protocol type corresponding to the first service; the method further includes: The second information is sent to the first computing node.

6. A communication method, characterized in that: The method comprises: Sending at least one first request message to a first network element, where one first request message among the at least one first request message is used to request a first service, where the one first request message includes a first identifier and a quality of service QoS requirement of the first service, where the first identifier corresponds to the one first request message; Receive a first response message from the first network element, the first response message is used to indicate the provision of the first service, the first response message includes the first identifier and a second identifier, the second identifier is associated with the first identifier, and the second identifier corresponds to a first task related to the first service.

7. The method according to claim 6, characterized in that The method further comprises: Receiving first configuration information from a second device, the first configuration information including the second identifier, the first configuration information being used to configure the first terminal device to establish a wireless bearer for transmitting data of the first task between the first terminal device and the second device; wherein the second device includes the second terminal device or an access network device to which the first terminal device belongs; Determining, according to the second identifier, that the first configuration information is configuration information associated with the first identifier; The data of the first task is transmitted using the radio bearer configured by the first configuration information.

8. The method according to claim 7, characterized in that The transmitting the data of the first task by using the radio bearer configured by the first configuration information includes: Mapping the IP data flow of the first task into a first QoS flow according to a first parameter group and / or the QoS flow template, the first parameter group including the IP address of the first terminal device, the application port number of the first terminal device, the data transmission protocol type corresponding to the first service, the IP address of the first computing node and the application port number of the first computing node, the first computing node being a computing node that executes the first task; The first QoS flow is transmitted using a radio bearer configured using the first configuration information.

9. The method according to claim 7, characterized in that: The using the first configuration information to transmit the data of the first task includes: Mapping the IP data flow of the first task to a first QoS flow according to the second identifier, and transmitting the first QoS flow using the radio bearer configured by the first configuration information; or, Transmitting the IP data stream of the first task using the radio bearer configured by the first configuration information; The IP data stream of the first task includes the second identifier.

10. The method according to any one of claims 6 to 9, characterized in that: The first request message also includes second information, and the second information includes at least one of the following: an IP address of the first terminal device, an application port number of the first terminal device, or a data transmission protocol type corresponding to the first service.

11. The method according to any one of claims 1 to 10, characterized in that The first response message also includes information of the first computing node and / or a QoS flow template. The information of the first computing node includes the IP address of the first computing node and / or the application port number of the first computing node. The information of the first computing node and / or the QoS flow template are used to filter and map data of the first task.

12. A communication method, characterized in that: The method comprises: receiving a second request message from the first network element, where the second request message is used to request the first computing node to perform a first task related to the first service, where the second request includes a second identifier, and the second identifier corresponds to the first task; A second response message is sent to the first network element according to the second request message, where the second response message is used to indicate that the first computing node accepts to execute the first task.

13. The method according to claim 12, characterized in that The method further comprises: Sending second configuration information to the first terminal device, where the second configuration information includes the second identifier, and the second configuration information is used to configure the first terminal device to establish a wireless bearer for transmitting data of the first task with the first computing node; The wireless bearer configured using the second configuration information sends data of the first task to the first terminal device.

14. The method according to claim 12 or 13, characterized in that The method further comprises: The IP data flow or the first QoS flow of the first task is sent to the user plane network element, the IP data flow of the first task or the first QoS flow includes the second identifier, and the first QoS flow is obtained by mapping the IP data flow of the first task according to the second identifier.

15. The method according to any one of claims 1 to 5 or 12 to 14, characterized in that: The second request message also includes a QoS requirement of the first task, and the QoS requirement of the first task is determined according to a QoS requirement of the first service.

16. The method according to any one of claims 1 to 5 or 12 to 15, characterized in that: The second response message also includes information about the first computing node, including the IP address of the first computing node and / or the application port number of the first computing node, and the information about the first computing node is used to filter and map data of the first task.

17. The method according to claim 16, characterized in that The second response message also includes a QoS flow template, and the QoS flow template is used to filter and map the data of the first task.

18. The method according to any one of claims 4, 8, 11 or 17, characterized in that The QoS flow template is specifically used to filter and map the IP data flow of the first task into a first QoS flow, or the QoS flow template is used to filter the IP data flow of the first task into a service data flow SDF and map the SDF into the first QoS flow.

19. A communication method, characterized in that: The method comprises: Sending second configuration information to the first terminal device, where the second configuration information includes a second identifier, where the second configuration information is used to configure the first terminal device to establish a radio bearer for transmitting data of the first task with the second device, and the second identifier corresponds to the first task; The wireless bearer configured using the second configuration information sends data of the first task to the first terminal device.

20. The method according to claim 19, characterized in that The second device is an access network device to which the first terminal device belongs, and the sending the second configuration information to the first terminal device includes: receiving a fourth request message from the first network element, the fourth request message being used to request the access network device to establish a radio bearer for transmitting data of the first task between the access network device and the first terminal device, the fourth request including a second QoS configuration and the second identifier for establishing the radio bearer; The second configuration information is sent to the first terminal device according to the fourth request message.

21. The method according to claim 19 or 20, characterized in that The method further comprises: Receive the IP data flow or the first QoS flow of the first task from the user plane network element, where the IP data flow or the first QoS flow of the first task includes the second identifier.

22. The method according to claim 19 or 20, characterized in that The sending the data of the first task to the first terminal device using the radio bearer configured by the second configuration information includes: The wireless bearer configured using the second configuration information sends the IP data flow or the first QoS flow of the first task to the first terminal device, where the IP data flow or the first QoS flow of the first task includes the second identifier.

23. A communication device, characterized in that: Comprising modules for executing the method as claimed in any one of claims 1 to 22.

24. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1-22 through a logic circuit or executing code instructions.

25. A communication device, characterized in that: include: processor; The processor is configured to execute a computer program or instruction so that the method according to any one of claims 1 to 22 is implemented.

26. A communication chip, characterized in that: Instructions are stored therein, and when the chip runs on a communication device, the method according to any one of claims 1 to 22 is implemented.

27. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instruction, and when the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 22 is implemented.

28. A computer program product, characterized in that The device comprises a computer program code, and when the computer program code is executed on a communication device, the communication device implements the method according to any one of claims 1 to 22.

Images