Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. The method comprises: determining a first identifier, the first identifier being associated with a first computing task; receiving first data from a terminal device by means of a first air interface bearer indicated by the first identifier, the first data being data associated with the first computing task; and sending the first data to a target instance, the target instance being used for processing the data associated with the first computing task. In the technical solution of the present application, a network device (such as an access communication-computation node) can implement data transmission with a terminal device by means of the first air interface bearer indicated by the first identifier, so that a first computing task can be tightly coupled to the first air interface bearer, and communication resources and computing resources are fully and efficiently utilized, thereby realizing efficient transmission of computing task-based and user plane-based data.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application with application number 202410409060.2 filed with the State Intellectual Property Office of China on April 3, 2024, and priority to the Chinese patent application with the invention name “Communication Method and Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a communication method and device. Background Art

[0003] When an application client on a terminal device calls software code on a cloud server to execute computing services, this can be achieved by developing its own services over the operator's broadband network (over the top, or OTT) approach. In this scenario, the network device only provides the Internet Protocol (IP) packet forwarding required for the software code call process and does not manage and / or schedule the computing resources of the compute nodes.

[0004] With the standardization of hardware computing devices and algorithm models, and the maturation of software technologies such as artificial intelligence and cloud computing, data volumes have exploded, and the demand for computing power has also increased. This has also led to the problem of uneven distribution of computing resources. To address this uneven distribution of computing resources, utilizing networks to schedule and allocate computing resources has become a current development trend. In the current technological context, computing-first networking (CFN) can be used to schedule and / or allocate computing resources. Through computing power routing, computing services requested by terminal devices are routed to the most suitable computing power location (or computing node).

[0005] However, when selecting computing nodes for computing services requested by terminal devices, routing devices in CFNs typically only consider whether each computing node has the software program corresponding to the computing function required by the terminal device, as well as the single-hop network transmission performance from the current node to the next hop node in the routing network. As a result, the routing devices fail to consider the overall communication performance from the terminal device to different computing nodes when selecting computing nodes. For example, if the communication delay between the terminal and each computing node is too long, the delay in the terminal receiving the output of the computing service will not meet the service requirements.

[0006] In view of this, in order to fully and efficiently utilize communication resources and computing resources, an efficient transmission solution for user-plane data based on computing power services is urgently needed to be developed. Summary of the Invention

[0007] The present application provides a communication method and apparatus to achieve efficient transmission of user plane data based on computing tasks.

[0008] In a first aspect, a communication method is provided. The method can be executed by a network device with computing capabilities or a component (such as a chip or module) of a network device with computing capabilities. For example, the network device can be an access network device, or an access computing node (or a first node). Alternatively, the method can be executed by a computing device with communication capabilities or a component (such as a chip or module) of a computing device with communication capabilities. The following description uses the execution subject of this method as the first node as an example. In actual implementation, the execution subject of this method can be other names.

[0009] The method includes: determining a first identifier, which is associated with a first computing task; receiving first data from a terminal device through a first air interface bearer indicated by the first identifier, wherein the first data is data associated with the first computing task; and sending the first data to a target instance, which is used to process the data associated with the first computing task.

[0010] In some implementations, the first identifier is used to identify a bearer or resource associated with the first computing task, and the bearer or resource can be used to carry data required to be transmitted for the current invocation of the first computing task. Exemplarily, the bearer or resource may include a data radio bearer (DRB), or a data radio bearer may include multiple bearers associated with the first computing task, or may also include other bearers or resources for carrying data.

[0011] Based on the above scheme, by associating the first identifier with the first computing task, the first data of the first computing task can be determined according to the first identifier, and then the target instance of the first data can be selected, and then the data transmission between the terminal device and the first node can be realized through the first air interface bearer indicated by the first identifier. In this way, the first computing task can be tightly coupled with the first air interface bearer, and communication resources and computing resources can be fully and efficiently utilized, thereby realizing efficient transmission of computing task-based and user-plane-based data.

[0012] In combination with the first aspect, in certain implementations of the first aspect, determining the first identifier includes: receiving a first request message from the terminal device, the first request message including the identifier of the first computing task, and the first request message is used to request scheduling of the first computing task; determining the first identifier based on the first request message.

[0013] Based on the above scheme, the first node starts scheduling the first computing task according to the first request information, and allocates the air interface bearer required for transmitting data for the current scheduling of the computing task according to the first request information and the identifier of the first computing task, which helps to improve resource utilization and avoid waste caused by reserved resources. By associating the first computing task with the first identifier, it is also possible to send the first data of the computing task to the appropriate computing instance based on the first identifier.

[0014] In combination with the first aspect, in certain implementations of the first aspect, determining the first identifier includes: receiving second request information from the core network, the second request information including the identifier of the first computing task; and determining the first identifier based on the second request information.

[0015] Based on the above scheme, the first node can allocate the air interface bearer required for data transmission for the current scheduling of the computing task according to the identifier of the first computing task in the second request information, which helps to improve resource utilization and avoid waste caused by reserved resources, and realizes high-performance and guaranteed transmission of the first data between the terminal device and the first node according to the first air interface bearer indicated by the first identifier.

[0016] In combination with the first aspect, in certain implementations of the first aspect, determining the first identifier includes: receiving a first data packet through a second air interface, the first data packet carrying second data and an identifier of the first computing task, the identifier of the first computing task indicating that the second data is data associated with the first computing task; and determining the first identifier based on the identifier of the first computing task.

[0017] In some implementations, the second air interface bearer may be a DRB, or a signaling radio bearer (SRB), or other bearers.

[0018] For example, the second air interface bearer may be a bearer allocated in the past when the first computing task is called, or the second air interface bearer may be determined by the terminal device itself. The second air interface bearer may be the same as or different from the first air interface bearer.

[0019] Based on the above scheme, when the terminal device provides a first data packet, the second data associated with the first computing task can be determined through the identifier of the first computing task in the first data packet, and the second data can be sent to the first node through the second air interface bearer. This can allocate the air interface bearer required for data transmission for the current scheduling of the computing task, help improve resource utilization, avoid waste caused by reserved resources, and also achieve high-performance and guaranteed transmission of the second data between the terminal device and the first node.

[0020] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending the second data to the target instance according to the identifier of the first computing task, where the target instance is associated with the first node.

[0021] Based on the above scheme, according to the identifier of the first computing task, it can be determined to forward the second data to the local target instance of the first node, so that the second data of the first computing task of the terminal can be sent to a suitable target instance for further processing, thereby ensuring the end-to-end performance of the first computing task.

[0022] In combination with the first aspect, in certain implementations of the first aspect, the second data is sent to the second node based on the relationship between the identifier of the first computing task and the second identifier, and the target instance is associated with the second node; or, the second data is sent to the second node based on the relationship between the identifier of the first computing task, the second identifier, and the identifier of the terminal device, and the target instance is associated with the second node; wherein the second identifier includes a first address and a second address, the first address is the address of a node of a first transmission path, the second address is the address of another node of the first transmission path, the first transmission path is used to transmit third data, and the third data is determined based on the second data.

[0023] Based on the above scheme, the first node can determine to forward the second data to the target instance associated with the second node based on the relationship between the first identifier, the identifier of the first computing task and the identifier of the terminal device. This can realize data transmission between the first node and the second node, thereby making full and efficient use of communication resources and computing resources, realizing the transmission of user-side data between the first node and the second node, and further ensuring the end-to-end performance of the first computing task.

[0024] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending the first identifier to the terminal device.

[0025] Based on the above solution, the terminal device can determine the first air interface bearer for transmitting data according to the first identifier, so that the data is transmitted on the indicated resources. This can make full use of communication resources and achieve high-performance and guaranteed data transmission between the terminal device and the computing node.

[0026] In combination with the first aspect, in certain implementations of the first aspect, the sending of the first data to the target instance includes: sending the first data to the target embodiment based on the first identifier, and the target instance is associated with the first node; or, sending the first data to the target embodiment based on the first identifier and the identifier of the first computing task, and the target instance is associated with the second node; or, sending the first data to the target embodiment based on the first identifier and the identifier of the first quality of service QoS flow, and the target instance is associated with the second node, wherein the identifier of the first QoS flow is the identifier of the QoS flow associated with the first computing task.

[0027] Based on the above scheme, the first node can determine to forward the first data to the target instance associated with itself based on its own stored information, such as the first identifier; or the first identifier and the identifier of the first computing task. In this way, when the first node can provide the resources required for the computing task, data transmission can be achieved through the local target instance of the first node. The first data is sent to the target instance according to the first identifier, and the same forwarding action is performed on the data received on an air interface bearer without parsing the protocol header of each data packet before forwarding. This can simplify the data forwarding complexity and resource consumption of the first node and ensure the end-to-end performance of the first computing task.

[0028] In combination with the first aspect, in certain implementations of the first aspect, the sending of the first data to the target instance includes: sending the first data to the second node based on the relationship between the first identifier and the second identifier, and the target instance is associated with the second node, wherein the second identifier includes a first address and a second address, the first address is the address of a node of a first transmission path, the second address is the address of another node of the first transmission path, the first transmission path is used to transmit third data, and the third data is determined based on the first data; or, sending the first data to the second node based on the relationship between the first identifier, the identifier of the first computing task, and the second identifier, and the target instance is associated with the second node; or, sending the first data to the second node based on the relationship between the first identifier, the identifier of the first quality of service QoS flow, and the second identifier, and the target instance is associated with the second node, wherein the identifier of the first QoS flow is the identifier of the QoS flow associated with the first computing task.

[0029] Based on the above scheme, the first node determines to forward the first data to the target instance associated with the second node based on the relationship between the first identifier stored in the first node and the identifier of the first computing task or the second identifier, so that the first data can be accurately transmitted to the target instance associated with the second node that provides computing resources. By sending the first data to the target instance based on the first identifier, the same forwarding action is performed on the data received on an air interface bearer without parsing the protocol header of each data packet before forwarding. This can simplify the data forwarding complexity and resource consumption of the first node, thereby achieving efficient data transmission and ensuring the end-to-end performance of the first computing task.

[0030] In combination with the first aspect, in certain implementations of the first aspect, sending the first data to the second node includes: sending a second data packet to the second node, the second data packet including a first protocol header and a first payload, the destination address of the first protocol header being the first address, the source address of the first protocol header being the second address, and the first payload being determined based on the first data.

[0031] Based on the above solution, the second data can be encapsulated and transmitted to the target instance associated with the second node through the first address and the second address, ensuring that the first data can be accurately transmitted to the target instance and guaranteeing the end-to-end performance of the first computing task.

[0032] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending fifth data to the terminal device on the first air interface bearer, where the fifth data comes from the target instance.

[0033] Based on the above scheme, the air interface bearer identifier indicated by the first identifier is used to realize the downlink data sent by the target instance, further realize the data transmission between the terminal device and the first node, and realize the tight coupling of the computing task data transmission and the air interface bearer resources, thereby ensuring the end-to-end performance of the first computing task.

[0034] In combination with the first aspect, in certain implementations of the first aspect, sending fifth data to the terminal device on the first air interface bearer includes: receiving sixth data from the target instance, which is associated with the first node; or, receiving a third data packet from the second node, the third data packet including a second protocol header and a second payload, the destination address of the second protocol header being the second address, the source address of the second protocol header being the first address, the second payload including seventh data, the seventh data being determined based on the data sent by the target instance, which is associated with the second node.

[0035] Based on the above scheme, the data from the target instance can be encapsulated and transmitted to the first node through the first address and the second address, ensuring that when the second node sends the downlink data associated with the first computing task, it can be accurately delivered to the terminal device via the first node, thereby ensuring the end-to-end performance of the first computing task.

[0036] In conjunction with the first aspect, in some implementations of the first aspect, the first protocol header or the second protocol header further includes at least one of the following:

[0037] The identifier of the first computing task; the identifier of the terminal device.

[0038] Based on the above scheme, the data to be transmitted can be determined according to the identifier of the first computing task or the identifier of the terminal device, and the data from the target instance can be encapsulated and transmitted to the first node through the first address and the second address, thereby ensuring accurate data transmission. Even if the connection between the first node and the second node is based on service granularity, different terminal devices can be distinguished based on the identifier of the terminal device.

[0039] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending a third request message to the second node and receiving a third response message, wherein the third request message is used to request the second node to allocate the first address to the first computing task, and the second response message is used to indicate the first address.

[0040] Based on the above scheme, the second node can assign the corresponding first address to the first computing task, so that the data associated with the first computing task can be transmitted through the designated tunnel. This can make full use of communication resources and realize data transmission between the terminal device and the computing node, thereby ensuring the end-to-end performance of the first computing task.

[0041] In combination with the first aspect, in certain implementations of the first aspect, the identifier of the first computing task includes a unicast address, and the method further includes: allocating the unicast address to the first computing task based on the first request information, or requesting the unicast address from the second node based on the first request information, and receiving the unicast address from the second node; and sending information about the unicast address to the terminal device.

[0042] Exemplarily, the second node may be a neighboring node of the current node, such as a collaborative node. Requesting a unicast address from the second node according to the first request information may include: sending a request information to the second node to request the second node to allocate a unicast address for the first computing task; and receiving the unicast address from the second node.

[0043] Based on the above solution, the first node can obtain the unicast address of the first computing task, allowing the terminal to obtain the address associated with the first computing task and then use this unicast address as the destination address when transmitting user-plane data. Furthermore, the first node can also determine and select the target instance of the first computing task based on the unicast address, allowing the data to be processed by the designated resources. This effectively utilizes communication and computing resources and achieves efficient data transmission on the user plane.

[0044] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving first indication information on the first air interface bearer, where the first indication information is used to indicate the end of the first computing task.

[0045] In combination with the first aspect, in some implementations of the first aspect, the first indication information further includes an identifier of the first computing task.

[0046] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving fourth request information, where the fourth request information is used to indicate the end of scheduling of the first computing task.

[0047] Based on the above scheme, through the first indication information, the first node can know when the first computing task ends, thereby realizing the same forwarding of one or more data based on the granularity of the computing task, flexibly allocating and releasing different computing resources and transmission resources, and improving the efficiency of data transmission.

[0048] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving fifth request information from a third node, where the fifth request information is used to instruct the first computing task to switch from the third node to the first node.

[0049] Based on the above technical solution, the fifth request information can be used to switch between the first node and the third node, so that when the computing resources and communication resources of the third node are insufficient, the first computing task can be switched to the first node, and different computing resources and transmission resources can be flexibly allocated and released to realize the transmission of data of the first computing task.

[0050] In combination with the first aspect, in certain implementations of the first aspect, the first identifier is also associated with at least one set of computing power quality of service QoS parameters, and the set of computing power QoS parameters is the QoS parameters associated with the first computing task.

[0051] In combination with the first aspect, in certain implementations of the first aspect, each set of computing power QoS parameters includes transmission QoS parameters and / or computing QoS parameters.

[0052] Based on the above solution, by associating the first identifier with the QoS, while ensuring that the computing task data is transmitted through the corresponding first air interface bearer, the performance of the first computing task can also be guaranteed.

[0053] In a second aspect, a communication method is provided, which can be executed by a terminal device or by a component (such as a chip or module) of the terminal device, and this application does not limit this. For ease of description, the following description is based on an example of execution by a terminal device.

[0054] The method includes: receiving a first identifier from a first node, the first identifier is used to indicate a first air interface bearer, and the first identifier is associated with a first computing task; sending first data to the first node via the first air interface bearer, the first data being data associated with the first computing task.

[0055] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending a first request message to the first node, the first request message including an identifier of the first computing task, and the first request message is used to request scheduling of the first computing task.

[0056] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: sending a first data packet through a second air interface, the first data packet carrying second data and an identifier of a first computing task, the identifier of the first computing task indicating that the second data is data associated with the first computing task.

[0057] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: receiving fifth data on the first air interface bearer, the fifth data coming from a target instance, and the target instance being used to process data associated with the first computing task.

[0058] In combination with the second aspect, in some implementations of the second aspect, first indication information is sent on the first air interface bearer, where the first indication information is used to indicate the end of the first computing task.

[0059] In combination with the second aspect, in some implementations of the second aspect, the first indication information further includes an identifier of the first computing task.

[0060] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending fourth request information, where the fourth request information is used to indicate the end of scheduling of the first computing task.

[0061] In combination with the second aspect, in certain implementations of the second aspect, the first identifier is also associated with at least one set of computing power quality of service QoS parameters, and the set of computing power QoS parameters is the QoS parameters associated with the first computing task.

[0062] In combination with the second aspect, in certain implementations of the second aspect, each set of computing power QoS parameters includes transmission QoS parameters and / or computing QoS parameters.

[0063] In a third aspect, a communication method is provided, which can be executed by a network device having computing task control capabilities, or by a component of a network device having computing task control capabilities. For example, the network device can be a core network.

[0064] The method includes: receiving a sixth request message from a terminal device, the sixth request message being used to request scheduling of a first computing task, and the sixth request message including an identifier of the first computing task; selecting a target instance, the target instance being used to process data associated with the first computing task, and the target instance being associated with a first node or a second node.

[0065] Based on the above technical solution, it is possible to select a target instance for a specific computing task (for example, when an access node or a collaborative node can provide multiple instances for a computing task, a target instance can be selected from the multiple instances and assigned to the computing task). When the computing task ends, the corresponding air interface bearer and / or target instance can be released, which helps improve resource utilization. In addition, the first node can directly send (or route) relevant data to the target instance determined based on the communication resources used for the first computing task, avoiding the situation where the communication resources of the node providing the target instance cannot meet the performance of the first computing task, thereby helping to ensure the performance of the first computing resources.

[0066] In conjunction with the third aspect, in certain implementations of the third aspect, when the target instance is associated with the first node, the method further includes:

[0067] A seventh request message is sent to the first node, where the seventh request message is used to request allocation of resources for the terminal device to process the first computing task, and the seventh request message includes an identifier of the first computing task; a first address is received from the first node, where the first address is an address of a node on a first transmission path, where the first transmission path is used to transmit fourth data, where the fourth data is determined based on the first data, and the first data is data associated with the first computing task.

[0068] In combination with the third aspect, in certain implementations of the third aspect, the seventh request information is used to request that resources for processing the first computing task be allocated to the terminal device, including: the seventh request information is used to request the first node to allocate a first air interface bearer and the target instance, the first air interface bearer is used to transmit first data, and the first data is data associated with the first computing task.

[0069] In combination with the third aspect, in certain implementations of the third aspect, when the target instance is associated with the second node, the method also includes: sending an eighth request message to the second node, the eighth request message being used to request allocation of resources for the terminal device to process the first computing task, and the eighth request message including an identifier of the first computing task; receiving a second address from the second node, the second address being the address of another node of the first transmission path, the first transmission path being used to transmit fourth data, the fourth data being determined based on the first data, the first data being data associated with the first computing task.

[0070] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: determining a third identifier based on the sixth request information, the third identifier being used to indicate data associated with the first computing task; and sending the third identifier to the terminal device.

[0071] In combination with the third aspect, in certain implementations of the third aspect, the identifier of the first computing task includes a unicast address, and the method further includes: receiving the unicast address from the first node or the second node; and sending the unicast address to the terminal device.

[0072] In a fourth aspect, a communication method is provided, which can be executed by a network device having computing task control capabilities, or by a component of a network device having computing task control capabilities. For example, the network device can be a core network.

[0073] The method includes: receiving a sixth request message from a terminal device, the sixth request message is used to request scheduling of a first computing task, and the sixth request message includes an identifier of the first computing task; sending a seventh request message to a first node, the seventh request message is used to request allocation of resources for processing the first computing task to the terminal device, and the seventh request message includes an identifier of the first computing task.

[0074] Based on the above solution, resources can be allocated to specific computing tasks. When the computing task is completed, the corresponding air interface bearer can be released, which helps to improve resource utilization.

[0075] In combination with the fourth aspect, in certain implementations of the fourth aspect, a first address is received from the first node, where the first address is the address of a node on a first transmission path, and the first transmission path is used to transmit fourth data, where the fourth data is determined based on the first data, and the first data is data associated with the first computing task.

[0076] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method also includes: sending an eighth request message to the second node, the eighth request message being used to request allocation of resources for the terminal device to process the first computing task, and the eighth request message including an identifier of the first computing task; receiving a second address from the second node, the second address being the address of another node of the first transmission path, the first transmission path being used to transmit fourth data, the fourth data being determined based on the first data, the first data being data associated with the first computing task.

[0077] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method further includes: selecting a target instance, which is used to process data associated with the first computing task, and the target instance is associated with the first node or the second node.

[0078] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the target instance is associated with the first node, the seventh request information is used to request that resources for processing the first computing task be allocated to the terminal device, including: the seventh request information is used to request the first node to allocate a first air interface bearer and the target instance, the first air interface bearer is used to transmit first data, and the first data is data associated with the first computing task.

[0079] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method further includes: determining a third identifier based on the sixth request information, the third identifier being used to indicate data associated with the first computing task; and sending the third identifier to the terminal device.

[0080] In combination with the fourth aspect, in certain implementations of the fourth aspect, the identifier of the first computing task includes a unicast address, and the method further includes: receiving the unicast address from the first node or the second node; and sending the unicast address to the terminal device.

[0081] In the fifth aspect, a communication method is provided, which can be executed by a network device with computing capabilities, or a component (such as a chip or module) of a network device with computing capabilities. For example, the network device can be a network device adjacent to the network device that executes the method in any implementation of the first aspect, such as a neighboring node of an access node (for example, a collaborative node (or called a second node)). Alternatively, the method can also be executed by a computing device with communication capabilities or a component (such as a chip or module) of a computing device with communication capabilities. The following is an example in which the execution subject of this method is the second node. In actual implementation, the execution subject of this method can be other names.

[0082] The method includes: receiving a third request message from a first node, the third request message being used to request a second node to allocate a first address for a first computing task, the first address being associated with the first computing task; and allocating a target instance to the first computing task according to the third request message, the target instance being used to process data associated with the first computing task, and the target instance being associated with the second node.

[0083] In combination with the fifth aspect, in certain implementations of the fifth aspect, first response information is sent to the first node, where the first response message is used to indicate the first address.

[0084] In combination with the fifth aspect, in certain implementations of the fifth aspect, a second data packet is received from a first node, the second data packet including a first protocol header and a first payload, the destination address of the first protocol header is a first address, the source address of the first protocol header is a second address, the first address is the address of a node of a first transmission path, the second address is the address of another node of the first transmission path, the first transmission path is used to transmit fourth data, the fourth data is determined based on the first data, the first data is data associated with the first computing task, and the first payload is determined based on the first data.

[0085] In combination with the fifth aspect, in certain implementations of the fifth aspect, a third data packet is sent to the first node, the third data packet including a second protocol header and a second payload, the destination address of the second protocol header is the second address, the source address of the second protocol header is the first address, and the second payload includes seventh data, which is determined based on the data sent by the target instance.

[0086] In combination with the fifth aspect, in certain implementations of the fifth aspect, the second node allocates the unicast address to the first computing task according to the third request information, and sends the unicast address to the first node.

[0087] For the non-exhaustive beneficial effects and possible designs of the second to fifth aspects, please refer to the relevant description in the first aspect and will not be repeated here.

[0088] In the sixth aspect, an embodiment of the present application provides a communication device. The communication device may be a device or apparatus with a chip, or a device or apparatus integrated with a circuit, or a chip, chip system, module or control unit in the aforementioned device or apparatus, and this application does not limit it. It should be noted that, in this application, when referring to a communication device, it may refer to the communication device itself, or to a chip, functional module or integrated circuit in the communication device that completes the method provided in this application, and this application does not limit it. The device is used to execute the method provided in any one of the first to fifth aspects above. Specifically, the device may include units and / or modules for executing the method provided in any one of the implementation modes of the first to fifth aspects.

[0089] When the device is used to execute the method provided in any one of the implementations of the first to fifth aspects, the device may include a transceiver unit and a processing unit.

[0090] In some implementations, the processing unit may be at least one processor. The transceiver unit may be a transceiver or an input / output interface. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0091] In some implementations, the communication device is a chip, chip system, or circuit in a terminal device or network device (such as a first node, a core network, or a second node). The transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit. The processing unit can be at least one processor, processing circuit, or logic circuit.

[0092] In a seventh aspect, embodiments of the present application provide a processor for executing the methods provided in the above aspects. For operations such as sending and receiving involved in the processor, unless otherwise specified, or unless otherwise inconsistent with its actual function or inherent logic in the relevant description, it can be understood as operations such as processor output, reception, and input, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna, and this application does not limit this.

[0093] In combination with the seventh aspect, in certain implementations of the sixth aspect, the processor is set in a communication device, and the communication device is any one of the first node, the terminal equipment, the core network and the second node.

[0094] In an eighth aspect, an embodiment of the present application provides a communication system, which includes a first node and a terminal device. The first node can execute the method provided by any one of the implementation modes in the above-mentioned first aspect; the terminal device can execute the method provided by any one of the implementation modes in the above-mentioned second aspect.

[0095] In combination with the eighth aspect, in certain implementations of the eighth aspect, the communication system also includes a core network, which can execute the method provided by any implementation of the third aspect or the method provided by any implementation of the fourth aspect.

[0096] In combination with the eighth aspect, in certain implementations of the eighth aspect, the communication system further includes a second node, which can execute the method provided by any one of the implementations of the fifth aspect.

[0097] In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores instructions or program codes, which, when executed by a processor, can implement the method provided in any one of the implementations of the first to fifth aspects above.

[0098] In a tenth aspect, an embodiment of the present application provides a computer program product comprising instructions. When the computer program product is run on a computer, the computer is caused to execute the method provided in any one of the implementations of the first to fifth aspects above.

[0099] In an eleventh aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method provided in any one of the implementation modes of the first to fifth aspects above.

[0100] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any one of the implementation methods of the first to fifth aspects above.

[0101] The beneficial effects brought about by the above-mentioned sixth to eleventh aspects can be specifically referred to the description of the beneficial effects in the first to fifth aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] FIG1 is a schematic diagram of a communication system used in an embodiment of the present application.

[0103] FIG2 is a schematic diagram of another communication system applied in an embodiment of the present application.

[0104] FIG3 is a schematic block diagram of a general computing node and an end-to-end protocol stack provided in an embodiment of the present application.

[0105] FIG4 is a schematic block diagram of a communication method provided in an embodiment of the present application.

[0106] FIG5 is another schematic block diagram of the communication method provided in an embodiment of the present application.

[0107] FIG6 is another schematic block diagram of the communication method provided in an embodiment of the present application.

[0108] FIG7 is an exemplary flowchart of a communication method provided in an embodiment of the present application.

[0109] FIG8 is another exemplary flowchart of the communication method provided in an embodiment of the present application.

[0110] FIG9 is another exemplary flowchart of the communication method provided in an embodiment of the present application.

[0111] FIG10 is another exemplary flowchart of the communication method provided in an embodiment of the present application.

[0112] FIG11 is a schematic diagram of a communication device provided in an embodiment of the present application.

[0113] FIG12 is another schematic diagram of a communication system provided in an embodiment of the present application.

[0114] FIG13 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0116] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0117] 1. Unless otherwise specified, “plurality” means two or more.

[0118] 2. Unless otherwise specified or there is no logical conflict, the terms and / or descriptions between different embodiments of this application are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their internal logical relationships.

[0119] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of protection of this application. The size of the serial numbers involved in this application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0120] At the same time, any embodiment or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0121] 4. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0122] 5. In this application, "used to indicate" can be understood as "enabling," and "enabling" can include direct enabling and indirect enabling. When describing that certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, and does not necessarily mean that the information contains A.

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

[0124] 6. In this application, "pre-configuration" may include pre-definition, such as protocol definition. "Pre-definition" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including each network element). This application does not limit the specific implementation method.

[0125] 7. "Storage" or "saving" as used in this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, processor, or communication device. The type of memory may be any form of storage medium and is not limited thereto.

[0126] 8. The “protocol” referred to in this application may refer to a standard protocol in the field of communications, such as the fourth generation (4G) th generation, 4G) network, fifth generation (5 th This application does not limit the present invention to 5G (5G generation) network protocols, new radio (NR) protocols, 5.5G network protocols, future network protocols, and related protocols used in future communication systems.

[0127] 9. The arrows or boxes indicated by dotted lines in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0128] 10. Unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can mean A or B. “And / or” in this application is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

[0129] For ease of understanding, the communication system shown in FIG1 is used as an example to describe the communication system applicable to various embodiments of the present application.

[0130] As shown in Figure 1 , the communications system includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (e.g., 110a and 110b in Figure 1 , collectively referred to as 110) and at least one terminal device (e.g., 120a-120j in Figure 1 , collectively referred to as 120). The RAN may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1 ). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wiredly connected to core network 200. The core network devices in core network 200 and RAN node 110 in RAN 100 may be separate physical devices, or they may be a single physical device that integrates core network logical functions and radio access network logical functions.

[0131] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as 4G, 5G, future mobile communication systems, non-terrestrial network (NTN) systems, or future evolution systems. The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (Wi-Fi) system, or a communication system that integrates two or more of the above systems.

[0132] In a communication system, a device can send signals to or receive signals from another device. Signals can include information, signaling, or data. Devices can also be replaced by entities, network entities, communication devices, communication modules, nodes, communication nodes, etc. The embodiments of this application are described using devices as an example.

[0133] In an embodiment of the present application, the terminal device 120 is a device with wireless transceiver functions, which may refer to user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device.

[0134] In the embodiment of the present application, the terminal device 120 may also be a satellite phone, a cellular phone, a smart phone, a wireless data card, a wireless modem, a machine type communication device, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a customer-premises equipment (CPE), a smart point of sale (POS) machine, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an on-board device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a terminal in device-to-device (D2D) communication, a terminal in vehicle-to-everything (V2X), a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a remote medical device, or a similar device. In the embodiments of the present application, the device for realizing the function of the terminal device may be a terminal device, or a device capable of supporting the terminal device to realize the function, such as a chip system or a chip, which may be installed in the terminal device. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

[0135] In the embodiment of the present application, the terminal device 120 may also be a device with communication functions in a future communication system, and the form or type of the terminal device in other future communication systems is not limited.

[0136] In the embodiments of the present application, the RAN node 110 may also be referred to as an access network device, an access node, or a RAN entity, and is used to help terminal devices achieve wireless access. Multiple RAN nodes 110 may be nodes of the same type or different types. In some scenarios, the roles of the RAN node 110 and the terminal device 120 are relative. For example, the network element 120i in Figure 1 may be a helicopter or a drone, which may be configured as a mobile base station. For terminal devices 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal device. The RAN node 110 and the terminal device 120 are sometimes referred to as communication devices. For example, 110a and 110b in Figure 1 may be understood as communication devices with base station functions, and the network elements 120a-120j may be understood as communication devices with terminal functions.

[0137] In one possible scenario, the RAN node 110 may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a future mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node may be a macro base station (such as 110a in FIG1 ), a micro base station or an indoor station (such as 110b in FIG1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node may also be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in vehicle to everything (V2X) technology may be a road side unit (RSU).

[0138] In another possible scenario, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes implementing portions of the base station's functionality. For example, a RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be separate or included in the same network element, such as the baseband unit (BBU). The CU and DU nodes split the gNB's protocol layers, centrally controlling some protocol layer functions within the CU and distributing some or all of the remaining protocol layer functions within the DU, which is then centrally controlled by the CU. As an implementation method, the CU is deployed with the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, and the service data adaptation protocol (SDAP) layer in the protocol stack; the DU is deployed with the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical layer (PHY) in the protocol stack. Thus, the CU has the processing capabilities of RRC, PDCP, and SDAP. The DU has the processing capabilities of RLC, MAC, and PHY. It will be understood that the above functional division is only an example and does not constitute a limitation on the CU and DU. The RU may be included in a radio frequency device or a radio frequency unit, for example, in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

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

[0140] In the embodiment of the present application, the core network 200 refers to the equipment in the core network (CN) that provides service support for the terminal device 120. At present, some examples of core network equipment are: access and mobility management function (AMF) entity, session management function (SMF) entity, user plane function (UPF) entity, etc., which are not listed here one by one. Among them, the AMF entity can be responsible for access management and mobility management of terminal devices; the SMF entity can be responsible for session management, such as user session establishment, etc.; the UPF entity can be a functional entity of the user plane, mainly responsible for connecting to the external network. It should be noted that the entities in this application can also be referred to as network elements or functional entities. For example, the AMF entity can also be referred to as AMF network element or AMF functional entity. For another example, the SMF entity can also be referred to as SMF network element or SMF functional entity, etc.

[0141] In the embodiments of the present application, the device for implementing the functions of the network device can be a network device; it can also be a device that can support the network device to implement the functions, such as a chip system, a hardware circuit, a software module, or a hardware circuit and a software module. The device can be installed in the network device or used in conjunction with the network device. In the embodiments of the present application, only the device for implementing the functions of the network device is used as an example to illustrate, and does not constitute a limitation on the solutions of the embodiments of the present application.

[0142] It should be noted that the embodiments of the present application do not limit the scenarios in which the network device is located. In addition, the network device can be a hardware device, or a software function running on dedicated hardware, or a software function running on general-purpose hardware, for example, an entity including dedicated or general-purpose hardware devices and software functions. The present application does not limit the specific form of the network device.

[0143] In order to facilitate understanding of the technical solution of this application, the relevant terms involved in this application are introduced below.

[0144] 1. Communication computing node: hereinafter referred to as a communication computing node, is a network device that has computing capabilities and can provide communication functions.

[0145] 2. Computing power function: Software program code written to support computing and processing specified data according to a specified algorithm. For example, such computing and processing may include: video stream transcoding, image rendering, image detection, artificial intelligence (AI) calculations, etc.

[0146] 3. Computing Service: Also known as a computing service, this is an independent application process that implements a set or a specific computing function to solve a specific problem. Computing services use a lightweight application programming interface (API) to communicate through a well-defined interface. Generally, a computing service corresponds to one or more computing functions that provide the same functionality. This means that multiple different computing functions implementing the same functionality can provide the same computing service. Generally, the functionality implemented by a computing function can be encapsulated as a service and made available to external entities through an API.

[0147] 4. Computing Function Instance: This is an application created by installing the computing function code onto a general computing node, hereafter referred to as a function instance. A function instance can be understood as an entity that can run a computing function. For example, it can be hosted by a container that provides the computing function's runtime environment, processes the function's input, executes the code logic, and produces output results. A computing function instance can also be referred to as a computing service instance.

[0148] 5. Computing function scheduling: This involves using a function instance to perform computations on specified data. This is referred to as function scheduling. The same computing function can be scheduled multiple times, with the inputs for each scheduling being the same or different. Consequently, the outputs for each scheduling can be the same or different. Computing function scheduling can also be understood as computing task scheduling.

[0149] 6. Computing Task: Also known as a computing task, this involves executing a computing function call (invoke) or computing service to obtain a result in order to complete a business logic transaction. For example, to perform video transcoding on specified data, a computing function call / computing service can be executed for a video clip or video code segment. This process uses the video clip or video code segment as input for the computing function / computing service until the computing function / computing service executes and obtains the complete transcoded clip or code segment. This is called a computing task. To process the next different video clip or video code segment, a new computing task must be executed, i.e., the computing function / computing service is called again or executed. In other words, different calls / executions of the computing function / computing service are called different computing tasks.

[0150] 7. Scheduling Compute Tasks: Prepare transmission resources for the compute task, or prepare both compute and transmission resources for the compute task, and begin executing the compute service call until the compute function / computing service runs and obtains the data processing results. It should be noted that if the compute resources required for the compute task are already prepared, only transmission resources are prepared for the compute task; if the compute resources required for the compute task are not already prepared, both transmission and compute resources are prepared for the compute task.

[0151] 8. Computing network: abbreviated as computing network, is a new type of information infrastructure that connects multiple computing nodes based on mobile communication networks, IP networks, and other networks, thereby scheduling computing tasks to computing nodes that can execute the computing tasks based on the resources required by the tasks.

[0152] 9. Computing power function identifier: A global identifier that uniquely identifies a computing power function. The identifier of the computing power function can be in any of the following formats: a globally unique identifier, for example, composed of one or more combinations of letters, numbers, and special characters; an identifier in the format of a uniform resource locator (URL); a fully qualified domain name (FQDN); an Internet Protocol (IP) address, for example, an IP unicast address, an IP anycast address, or a virtual IP address. In an embodiment of the present application, the computing power function identifier can also be a network identifier of the computing power function (for example, an identifier assigned by a mobile communication network, or an identifier that can be recognized by a mobile communication network negotiated between a third party and the mobile communication network). In this application, except where explicitly stated, computing power service and computing power function can be used interchangeably, and computing power function identifier and computing power service identifier can be used interchangeably.

[0153] 10. Computing power session: also known as computing session, computing network session, the computing nodes in the computing network can complete the authorization of computing tasks through computing power sessions, determine the nodes that provide computing resources for the computing tasks, and prepare computing power function instances for the computing tasks. Among them, authorizing the computing task can be understood as: the computing node subsequently provides computing resources and / or communication resources for the computing task. Preparing a computing power function instance for the computing task may include: triggering the instantiation of the computing power function and / or activating the computing processing function of the computing power function instance, so that when the computing power function instance receives the data to be processed of the computing task, it can process the data to be processed in a timely manner. Triggering the instantiation of the computing power function can be understood as: when the computing node does not have an available computing power function instance, downloading or obtaining the code of the computing power function required for the computing task, initiating a suitable container, and installing the computing power function code on the computing node.

[0154] 11. Computing Quality of Service (QoS): also known as computing network QoS, includes transmission QoS and computing QoS. It is a parameter used to ensure communication (or information transmission) and computing characteristics. It may include at least one of the following: transmission resource type, priority, packet delay budget, packet error rate, packet loss rate, default maximum data burst size, default averaging window, etc. It may also include computing resource types, such as central processing unit (CPU) resources, graphics processing unit (GPU) resources, neural network processing unit (NPU) resources, tensor processing unit (TPU) resources, deep learning processing unit (DPU) resources, field programmable gate array (FPGA) resources, memory resources, storage resources, etc. It may also include resource consumption granularity and computing power requirements, such as at least one of the following: floating point operations per second (FLOPS) and operations per second (OPS).

[0155] 12. Computing QoS Flow: This is used to transmit computing task data and meet the computing QoS requirements. The computing task data includes the data to be processed by the computing task and / or the processing results of the computing task.

[0156] 13. Computing Power QoS Class Identifier (QCI): This identifier is used to identify a set of computing power QoS characteristic parameters. Different computing power QoS characteristic parameters use different computing power QCIs, which identify different levels or grades of computing power QoS requirements and guarantees. Optionally, the transmission QCI and the calculation QCI can be two independent parameters. In this case, a set of computing power QoS characteristic parameters can be identified by the combination of the transmission QCI and the calculation QCI.

[0157] 14. Nc interface address: includes addresses at both ends, and each end address includes: IP address and user datagram protocol (UDP) port number. One end address can be called Nc uplink address (that is, NcUL address), and the other end address can be called Nc downlink address (that is, Nc DL address). Generally, the end close to the terminal device is called Nc uplink address, and the end far away from the terminal device is called Nc downlink address. Optionally, the Nc interface address also includes a tunnel identifier. The tunnel identifier can be associated with a terminal device, or it can be associated with a computing task of a terminal device. The Nc interface can also be understood as an Nc connection, and the Nc tunnel can also be referred to as Nc.

[0158] 15. Nodes associated with function instances: The function instance and the node associated with the function instance are co-deployed, or the function instance and the node associated with the function instance have a direct communication connection, or the function instance and the node associated with the function instance share hardware and / or software resources. For example, a collaboration node is a node that can be associated with a function instance. In this case, the function instance and the collaboration node are co-deployed, or the function instance and the collaboration node have a direct communication connection, or the function instance and the collaboration node share hardware and / or software resources. For another example, an access computing node is a node that can be associated with a function instance. In this case, the function instance and the access computing node are co-deployed, or the function instance and the access computing node have a direct communication connection, or the function instance and the access computing node share hardware and / or software resources.

[0159] As mentioned above, when selecting computing nodes, the routing devices in the CFN only consider the balance of the network load or the distance of the communication path, and fail to consider the overall communication performance from the terminal device to different computing nodes, so that the selected computing node may not be the node with better computing resources, resulting in a large delay in scheduling computing services. In response to the above problems, a network device (hereinafter referred to as an access computing node) or core network with computing functions that can provide access services to terminal devices has been developed. The above-mentioned access computing node or core network can determine whether the access computing node or the neighboring node of the access computing node can provide computing resources for the execution of the computing service based on the performance requirements of the computing service requested by the terminal device and the wireless communication resources that the access computing node can provide for the execution of the computing service. Furthermore, selecting a node whose available computing resources can support the performance requirements of the computing service to provide computing resources for the execution of the computing service can ensure the performance of the computing service.

[0160] However, the above scheme focuses on the allocation of computing nodes that execute computing services based on the control plane, and does not fully consider how data associated with computing services (such as data to be processed or processed data) is transmitted between terminal devices and computing nodes. For example, how to allocate communication resources between terminal devices and computing nodes for data associated with computing services, and how to release communication resources allocated for data associated with computing services. In view of this, the present application provides a communication method and device that can realize the transmission of data associated with computing tasks between terminal devices and computing nodes, thereby realizing efficient transmission of user-side data based on the granularity of computing tasks.

[0161] Figure 2 shows another schematic block diagram of a communication system provided by an embodiment of the present application. As shown in Figure 2, the communication system may include a terminal device 10, a service access computing node 20, and a core network 30. Optionally, the communication system may further include at least one collaborative access computing node (such as collaborative access computing nodes 21 to 2n, where n is a positive integer); the communication system may further include at least one collaborative core computing node (such as collaborative core computing nodes 31 to 3n, where n is a positive integer). The terminal device 10 may include any of the terminal devices 120 shown in FIG1 . If the terminal device 10 includes any of the terminal devices 120a, 120b, 120c, and 120i shown in FIG1 , the service access computing node 20 may include the RAN node 110 shown in FIG1 , and the at least one collaborative access computing node may also include the RAN node 110b shown in FIG1 . Alternatively, if the terminal device 10 includes any of the terminal devices 120f, 120g, and 120h shown in FIG1 , the service access computing node 20 may include the RAN node 110b shown in FIG1 , and the at least one collaborative access computing node may also include the RAN node 110a shown in FIG1 . In some implementations, the at least one collaborative access computing node may also include a UPF entity adjacent to the service access computing node 20. The at least one collaborative core computing node may include the core network 200 shown in FIG1 . The core network 30 may communicate with each computing node via a control plane, and the control plane may include one or more control plane function entities in the core network 200.

[0162] In actual implementation, the above-mentioned inter-computing nodes (such as service access inter-computing nodes, collaborative access inter-computing nodes, and collaborative core inter-computing nodes) may have, in addition to the communication function, some or all of the following functions:

[0163] 1) Computing task decision-making function, that is, determining whether its own computing resources are sufficient to perform local computing tasks. The above local computing tasks can be computing tasks requested by terminal devices or other general computing nodes, or they can also be computing tasks assigned by the core network.

[0164] 2) Control functions of function instances, including deploying function instances to virtualized hardware platforms and / or managing virtualized resources.

[0165] 3) Provide the virtualized resources required to run the computing function. These virtualized resources include communication resources, computing resources, and storage resources. More specifically, computing resources include virtualized CPU resources, GPU resources, NPU resources, TPU resources, FPGA resources, DPU resources, memory resources, and storage resources.

[0166] In particular, the service access computing node 20 is further configured to establish a communication connection with the terminal device 10 according to a computing task call request from the terminal device 10. The communication connection is used to carry function calls or computing task data.

[0167] The core network 30 is used to perform one or more of the following: processing computing task call requests from the terminal device 10 to implement identity authentication and authorization; deploying overall management and control strategies on each computing node for computing tasks; determining collaborative nodes based on computing tasks, for example, selecting one or more collaborative nodes from at least one collaborative access computing node and / or at least one collaborative core computing node.

[0168] It should be noted that the communication delay between at least one collaborative access computing node and at least one collaborative core node and the service access computing node 20 meets the delay requirement. For example, the communication delay between at least one collaborative access computing node or at least one collaborative core computing node and the service access computing node 20 is less than or equal to the delay threshold. The delay threshold can be 1 millisecond, 2 milliseconds, 5 milliseconds, or other values.

[0169] It should also be noted that the functions of each of the above computing nodes can be implemented or completed by a logical network element or a group of co-deployed logical network elements. For example, a service access computing node or a collaborative access computing node can be composed of a traditional base station plus a group of edge computing servers. The embodiment of the present application does not impose specific restrictions on the functional division of traditional base stations and edge computing servers. For another example, as shown in Figure 3 (a), the computing nodes in the embodiment of the present application (such as service access computing nodes, collaborative access computing nodes, collaborative core computing nodes) can also be implemented by a computing platform and a virtualized hardware platform independent of the computing platform (such as virtual machines, containers, etc.). Among them, the computing platform provides communication functions and function instance management functions. The communication function is used to realize communication with terminal devices and / or other computing nodes, and the function instance management function is used to realize dynamic management of function instances in computing nodes, such as computing power function instantiation, function instance activation, function instance release, etc., thereby realizing dynamic expansion or contraction of virtualized resources in the virtualized hardware platform. In addition, when the inter-computing node is a service access inter-computing node, the computing platform may also include a centralized control unit for determining the computing resources allocated for the computing task, or determining the collaborative node that provides computing resources for the computing task. The virtualized hardware platform is used to provide the virtualized resources required for the function instance to run, or the virtualized hardware platform also provides resources for implementing the user plane functions of the inter-computing node (such as user plane data transmission).

[0170] (b) and (c) in Figure 3 show a schematic diagram of the end-to-end protocol stack in the computing power service scheduling process provided by an embodiment of the present application. Among them, the data to be processed by the computing power service of the terminal device is encapsulated via the application layer, transmission control protocol (TCP) / user datagram protocol (UDP) / quick UDP Internet connections (QUIC) layer, IP layer, and computing power layer to obtain a computing power layer data packet, and then add layer 2 (layer 2 such as SDAP layer, PDCP layer, MAC layer) header to obtain an air interface data packet, which is transmitted to the access computing node through the air interface bearer. The access computing node parses the air interface data packet to obtain a computing power layer data packet, as shown in (b) in Figure 3. When the access computing node provides a function instance corresponding to the computing power service, the access computing node sends the computing power layer data packet to the function instance through computing power routing; as shown in (c) in Figure 3, when the collaborative node provides a function instance, the access computing node sends the computing power layer data packet to the collaborative node through computing power routing, and the collaborative node sends the computing power layer data packet to the function instance through computing power routing. Furthermore, the function instance parses the computing layer data packet to obtain the data to be processed by the computing service, and processes the data. Optionally, data packets can be transmitted between the access node and the function instance, or between the collaboration node and the function instance through other transmission protocols, for example, through L2 or L2 through other transmission protocols. The communication method provided by the embodiment of the present application is described in detail below in conjunction with the accompanying drawings. The embodiment provided by the present application can be applied to the communication system shown in Figures 1 and 2 above.

[0171] First, three scenarios applicable to the embodiments of the present application are described with reference to the schematic block diagrams of the communication method in Figures 4 to 6.

[0172] Figure 4 shows a schematic block diagram of a communication method provided by an embodiment of the present application. As shown in Figure 4(a), the UE is connected to the access computing node via a Uu interface. For example, there are three Uu interfaces between the UE and the access computing node, wherein each Uu interface corresponds to an air interface DRB, and each air interface DRB is associated with a computing function, such as air interface DRB1 is associated with computing function 1, air interface DRB 2 is associated with computing function 2, and air interface DRB3 is associated with computing function 3. For another example, when the computing function instance is provided by a collaborative node, the computing function can also correspond one-to-one (or called an association) with the reference point (or interface) tunnel (or tunnel identifier) ​​between the access computing node and the collaborative node. For example, tunnel (Nc) 1 is associated with computing function 1, Nc 2 is associated with computing function 2, and Nc 3 is associated with computing function 3. Among them, the air interface DRB is also called the air interface bearer, which can be indicated by the computing power bearer identifier. That is, computing power bearer identifier 1 indicates air interface bearer 1, computing power bearer identifier 2 indicates air interface bearer 2, and computing power bearer identifier 3 indicates air interface bearer 3; computing power function can also be called computing task. In addition, when the computing power function instance is executed on the collaborative node, multiple computing power functions can also be associated with a tunnel between the access node and the collaborative node. For example, tunnel (Nc) 1 is associated with computing power function 1, computing power function 2, and computing power function 3 respectively, that is, multiple computing power functions are associated with one Nc. As shown in Figure 4(b).

[0173] Figure 5 shows another schematic block diagram of the communication method provided by an embodiment of the present application. As shown in Figure 5, the UE is connected to the access computing node through a Uu interface. For example, there is a Uu interface between the UE and the access computing node, and the Uu interface corresponds to an air interface DRB1. The air interface DRB1 is associated with multiple computing functions, for example, air interface DRB1 is associated with computing function 1, computing function 1 and computing function 3. For another example, when the computing function instance is executed on the collaborative node, the computing function can also correspond one-to-one to the reference point tunnel between the access computing node and the collaborative node (or called an association). For example, Nc1 is associated with computing function 1, Nc 2 is associated with computing function 2, and Nc 3 is associated with computing function 3. Among them, the air interface DRB is also called an air interface bearer, which can be indicated by a computing power bearer identifier, that is, computing power bearer identifier 1 indicates air interface bearer 1, computing power bearer identifier 2 indicates air interface bearer 2, and computing power bearer identifier 3 indicates air interface bearer 3; computing power function can also be called a computing task.

[0174] Figure 6 shows another schematic block diagram of the communication method provided by an embodiment of the present application. As shown in Figure 6, the UE and the access computing node are connected through a Uu interface. For example, there is a Uu interface between the UE and the access computing node, and the Uu interface corresponds to an air interface DRB1, and the air interface DRB1 is associated with multiple computing functions. For example, air interface DRB1 is associated with computing function 1, computing function 1 and computing function 3. For another example, when the computing function instance is executed on the collaborative node, multiple computing functions can also be associated with a tunnel between the access computing node and the collaborative node. For example, Nc 1 is associated with computing function 1, computing function 2, and computing function 3, respectively, that is, multiple computing functions are associated with one Nc. Among them, the air interface DRB is also called an air interface bearer, which can be indicated by a computing power bearer identifier, that is, computing power bearer identifier 1 indicates air interface bearer 1, computing power bearer identifier 2 indicates air interface bearer 2, and computing power bearer identifier 3 indicates air interface bearer 3; computing power function can also be called a computing task. It should be noted that the above-mentioned computing power function can also be regarded as a computing task. For the convenience of description, the following description takes the computing task as an example.

[0175] The following describes in detail the communication method performed by the communication system described in Figure 2 in conjunction with Figures 7 to 11. Among them, Figures 7 to 9 are illustrated by taking the terminal device requesting to schedule computing task 1 as an example. The methods shown in Figures 7 to 9 can be performed by the terminal device and the access computing node. In some scenarios, the methods shown in Figures 7 to 9 also require the participation of collaborative nodes and core networks. Among them, the terminal device may include the terminal device 10 in Figure 2, the access computing node may include the service access computing node 20 in Figure 2, the core network may include the core network 30 in Figure 2, and the collaborative node may include at least one collaborative access computing node and / or at least one collaborative core computing node in Figure 2.

[0176] Figure 7 is an exemplary flow chart of a communication method provided in an embodiment of the present application. In this embodiment of the present application, each scheduling of a computing task is associated with an air interface bearer indicated by a computing power bearer identifier. The computing power bearer identifiers and the air interface bearers indicated by them corresponding to the scheduling of different computing tasks may be the same or different. Specifically, method 300 may include some or all of the following steps.

[0177] S301: The terminal device sends a scheduling request for computing task 1 to the access computing node. Correspondingly, the access computing node receives the scheduling request for computing task 1 from the terminal device.

[0178] Among them, the scheduling request carries the computing power service identifier of computing task 1. The specific form of the computing power service identifier can be referred to the description in the above embodiment and will not be repeated here. As mentioned above, computing task 1 can be understood as a scheduling of a computing power service (such as computing power service 1) or a computing power function (such as computing power function 1). The computing power service identifier of computing task 1 can be understood as: the identifier of computing power service 1 or computing power function 1 corresponding to computing task 1.

[0179] Exemplarily, the scheduling request may be air interface control signaling, such as access stratum (AS) signaling. More specifically, the scheduling request may be RRC layer signaling, or MAC layer signaling.

[0180] In some implementations, before the access intermediary computing node receives the scheduling request for computing task 1, no node providing computing resources has been assigned to computing task 1. In this case, the scheduling request further requests the access intermediary computing node to assign a node providing computing resources to computing task 1. Furthermore, the access intermediary computing node may determine whether to provide all computing resources for computing task 1 itself or by a cooperating node. For details, see step S302 below.

[0181] S302: The access general computing node determines whether it can provide all computing resources for computing task 1.

[0182] For example, the access intermediary computing node determines the computing resource 1 required for computing task 1 based on its own communication capabilities (e.g., the communication resources that can be provided for computing task 1). For another example, the access intermediary computing node determines whether to provide all computing resources for computing task 1 based on its own available communication resources and computing resource 1.

[0183] For example, if the available computing resources of the access computing node cannot meet the computing resources 1 required by computing task 1, the access computing node can determine not to provide all computing resources for computing task 1; otherwise, the access computing node can determine to provide all computing resources for computing task 1 by itself.

[0184] As an implementation method, the access computing node can also request the core network to identify the node that provides all computing resources for computing task 1. In other words, the core network can determine the node that provides all computing resources for computing task 1. Specifically, the core network sends a request to the identified node, requesting the corresponding node to provide a function instance for computing task 1. For example, when the access computing node receives the request from the core network, it determines that it will provide all computing resources for computing task 1. Optionally, the core network can assign a unicast IP address for access to computing task 1.

[0185] Based on the decision result of the access node, the subsequent execution steps can be divided into the following two cases:

[0186] Case 1:

[0187] The access general computing node determines that it will provide all computing resources (ie, function instance 1) for computing task 1. Specifically, step S303 may be included.

[0188] S303 , access the general computing node to provide function instance 1 for computing task 1 .

[0189] For example, when the access computing node provides all computing resources for computing task 1, if the access computing node does not have a function instance required by a computing task locally, the access computing node first dynamically triggers the instantiation of computing power function 1 corresponding to computing task 1 to obtain function instance 1, thereby activating the computing processing function of function instance 1 corresponding to computing task 1. The access computing node dynamically triggering the instantiation of computing power function 1 corresponding to computing task 1 to obtain function instance 1 may include at least one of the following:

[0190] Scheduling of computing power function 1 container resources;

[0191] Operation of computing power function 1 container resources;

[0192] Loading of computing power function 1;

[0193] The operation of computing power function 1.

[0194] Optionally, the access computing node can also determine the access unicast IP address for computing task 1 based on the above-mentioned scheduling request, wherein determining the access unicast IP address includes allocating the access unicast IP address for access by the access computing node itself or obtaining the access unicast IP address for access from function instance 1. When the computing power service identifier of computing task 1 carried by the access computing node in the scheduling request is a globally unique identifier or an identifier in URL format or an FQDN or an IP anycast address or a virtual IP address, the access unicast IP address is allocated to computing task 1. The access unicast IP address is used for terminal devices to access function instance 1 that provides computing task 1, and can be the unicast IP address of the access computing node, or the unicast IP address of function instance 1, or a virtual IP address (the virtual IP address is associated with multiple function instances of computing power services corresponding to computing task 1). Exemplarily, when the scheduling request carries the computing service identifier of computing task 1 as a globally unique identifier or an identifier in URL format or an FQDN, the determined IP unicast address to be accessed may be the unicast IP address of the access node, or the unicast IP address of function instance 1, or a virtual IP address; or when the scheduling request carries the computing service identifier of computing task 1 as an IP anycast address or a virtual IP address, the determined IP unicast address to be accessed may be the unicast IP address of the access node, or the unicast IP address of function instance 1. The unicast IP address of the access node and the unicast IP address of function instance 1 may belong to the same IP network segment.

[0195] Exemplarily, the accessed unicast IP address may also be a public IP address, or may also be a private IP address.

[0196] Case 2:

[0197] The access intermediary computing node determines that other intermediary computing nodes provide all computing resources for computing task 1 (ie, function instance 1).

[0198] For example, if it is determined that the collaborative node provides all computing resources for computing task 1, there are two ways to request the collaborative node to provide computing resources for computing task 1: method 1 and method 2. They are introduced below:

[0199] Method 1 (S304a to S304d):

[0200] S304a: The access computing node sends a request message 1 to the core network. Correspondingly, the core network receives the request message 1 from the access computing node.

[0201] Among them, the request information 1 is used to obtain the Nc uplink address 1 (that is, NcUL address 1). The request information 1 carries the Nc downlink address 1 (that is, Nc DL address 1) allocated by the access computing node to the computing task 1, wherein the Nc DL address 1 is associated with the computing task 1. The above-mentioned Nc DL address 1 and NcUL address 1 are respectively the two end addresses of the Nc 1 interface address, for example, Nc DL address 1 is the first end address of the Nc 1 interface address, and Nc UL address 1 is the second end address of the Nc 1 interface address; for another example, Nc UL address 1 is the first end address of the Nc 1 interface address, and Nc DL address 1 is the second end address of the Nc 1 interface address. Among them, the Nc 1 interface address includes Nc DL address 1 and NcUL address 1, NcUL address 1 may include IP address 1, UDP port number 1 and tunnel identifier 1, and Nc DL address 1 may include IP address 2, UDP port number 2 and tunnel identifier 1.

[0202] It should be noted that NcUL address 1 may include IP address 1, UDP port number 1, and tunnel identifier 1, and NcDL address 1 may include IP address 2, UDP port number 2, and tunnel identifier 1. This is only an example. When the association between the Nc interface address and the computing task, terminal device, or node is different, the content included in NcDL address 1 and NcUL address 1 is also different. See step S305b for details.

[0203] Optionally, the request information 1 is also used to request the cooperation node to allocate an access unicast IP address for the computing task 1 .

[0204] S304b: The core network sends request information 2 to the coordination node. Correspondingly, the coordination node receives the request information 2 from the core network.

[0205] The request information 2 is used to obtain Nc UL address 1 from the coordination node. The request information 2 carries the Nc DL address 1. The coordination node is a node associated with providing function instance 1 for computing task 1. The coordination node allocates Nc UL address 1 to computing task 1.

[0206] Optionally, after receiving the above-mentioned request information 2, the collaborative node also allocates an access unicast IP address for computing task 1. The access unicast IP address is associated with computing task 1. The access unicast IP address 1 can be the unicast IP address of the collaborative node, the unicast IP address of function instance 1, or a virtual IP address (the virtual IP address is associated with multiple function instances of computing power services corresponding to computing tasks 1). The unicast IP address of the collaborative node and the unicast IP address of function instance 1 can belong to the same IP network segment.

[0207] S304c: The coordination node sends response information 2 to the core network. Correspondingly, the core network receives the response information 2 from the coordination node.

[0208] The response message 2 carries the Nc UL address 1. Optionally, it also carries the unicast IP address accessed by the computing task 1. The response message 2 is the response message to the request message 2.

[0209] S304d: The core network sends a response message 1 to the access computing node. Correspondingly, the access computing node receives the response message 1 from the core network.

[0210] The response message 1 carries Nc UL address 1. Optionally, the response message 1 also carries the unicast IP address accessed by computing task 1. The response message 1 is the response message to the request message 1.

[0211] Steps S304a to S304d illustrate one implementation in which, when the collaborative node provides all computing resources for computing task 1, the collaborative node allocates Nc UL address 1 and, optionally, also allocates a unicast IP address accessible by computing task 1. In summary, the collaborative node notifies the core network of Nc UL address 1 via response message 2. Optionally, response message 2 also notifies the core network of the unicast IP address accessed by computing task 1. Furthermore, the core network notifies the access general computing node of Nc UL address 1 via response message 1. Optionally, response message 1 also notifies the access general computing node of the unicast IP address accessed by computing task 1.

[0212] It should be noted that the protocol between the access computing node and the core network may be based on a non-access stratum (NAS) protocol, or may be based on a hypertext transfer protocol (HTTP) or HTTPS protocol.

[0213] Method 2 (S305a to S305b):

[0214] S305a: The access computing node sends a request message 3 to the coordination node. Correspondingly, the coordination node receives the request message 3 from the access computing node.

[0215] The request information 3 is used to request the cooperative node to allocate Nc UL address 1. The request information 1 carries the Nc DL address 1 allocated by the access computing node to computing task 1. The allocation of Nc DL address 1 by the access computing node to computing task 1 can also be understood as associating the Nc DL address 1 with computing task 1.

[0216] Optionally, after receiving the request information 3 , the collaboration node further allocates an access unicast IP address for the computing task 1 .

[0217] S305b: The coordination node sends a response message 3 to the access computing node. Correspondingly, the access computing node receives the response message 3 from the coordination node.

[0218] The response information 3 carries the Nc UL address 1 of the computing task 1. Optionally, the response information 3 also carries the unicast IP address accessed by the computing task 1.

[0219] In steps S305a and S305b, when the coordinating node provides computing resources for computing task 1, the coordinating node allocates Nc UL address 1. Optionally, the coordinating node also allocates a unicast IP address accessed by computing task 1. In summary, the coordinating node notifies the access node of Nc UL address 1 via response message 3. Optionally, response message 3 also notifies the access node of the unicast IP address accessed by computing task 1.

[0220] The Nc interface address in steps S304a to S304d, and S305a to S305b above can be associated with a computing task of a terminal device, multiple computing tasks, a terminal device, or a node. In this case, the computing task, terminal device, or node can be identified by one or more of the IP address, port number, and tunnel identifier in the Nc interface address. Specifically, as follows:

[0221] (1) When each Nc interface address is associated with one or more computing tasks of a computing service of a terminal device, the above-mentioned request information 1 to request information 3 may also carry the computing service identifier of computing task 1. Optionally, any request information from request information 1 to request information 3 also carries the identifier of the terminal device associated with the computing task 1 or carries a session identifier, wherein the identifier of the terminal device is used to identify the terminal device that uses the Nc to transmit the data of the computing task. The Nc interface address corresponds to a computing task of a computing service, and the computing task corresponds to a terminal device; or the Nc interface address corresponds to multiple computing tasks of this computing service, and the multiple computing tasks are associated with the same terminal device.

[0222] For example, terminal device 1 and terminal device 2 each have two computing tasks (e.g., computing task 1 and computing task 2), and computing task 1 and computing task 2 belong to different computing power services / computing power functions. For example, Nc 1 corresponds to computing task 1 of terminal device 1 (the computing task 1 belongs to computing power service 1), Nc 2 corresponds to computing task 2 of terminal device 1 (the computing task 2 belongs to computing power service 2), Nc 3 corresponds to computing task 1 of terminal device 2 (the computing task 1 belongs to computing power service 1), and Nc 4 corresponds to computing task 2 of terminal device 2 (the computing task 2 belongs to computing power service 2). Among them, the first end address of the Nc interface address is the Nc DL address, and the second end address is the Nc UL address. For example, the first end address of the Nc 1 interface address is Nc DL address 1, and the second end address is Nc UL address 1.

[0223] At this time, a computing task of a terminal device can be identified by one or more of the IP address, port number, and tunnel identifier in the Nc interface address.

[0224] For example, the tunnel identifier is used to identify different computing tasks of the same terminal device; or the tunnel identifier is used to identify computing tasks of different computing power services of different terminal devices.

[0225] Optionally, the tunnel identifier is used to identify a computing task on a terminal device. That is, different tunnel identifiers are associated with different computing tasks on the same terminal device. In this case, the first end address of the Nc1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#2, and tunnel identifier 1; the first end address of the Nc2 interface address includes IP#1, port#1, tunnel identifier 2, and the second end address includes IP#2, port#2, and tunnel identifier 2; the first end address of the Nc3 interface address includes IP#1, port#1, and tunnel identifier 3, and the second end address includes IP#2, port#2, and tunnel identifier 3; and the first end address of the Nc4 interface address includes IP#1, port#1, and tunnel identifier 4, and the second end address includes IP#2, port#2, and tunnel identifier 4.

[0226] Tunnel ID 1 is used to identify computing task 1 of terminal device 1, tunnel ID 2 is used to identify computing task 2 of terminal device 1, tunnel ID 3 is used to identify computing task 1 of terminal device 2, and tunnel ID 4 is used to identify computing task 2 of terminal device 2. In other words, the two computing tasks of terminal device 1 correspond to tunnel ID 1 and tunnel ID 2, respectively, and the two computing tasks of terminal device 2 correspond to tunnel ID 3 and tunnel ID 4, respectively; in other words, different tunnel IDs correspond one-to-one to different computing tasks of the same (and / or different) terminal devices.

[0227] Optionally, a tunnel identifier pair is used to identify a computing task on a terminal device. That is, different tunnel identifier pairs are associated with different computing tasks on the same terminal device. In this case, the first end address of the Nc1 interface address includes IP#1, port#1, and tunnel identifier 11, and the second end address includes IP#2, port#2, and tunnel identifier 12; the first end address of the Nc2 interface address includes IP#1, port#1, and tunnel identifier 21, and the second end address includes IP#2, port#2, and tunnel identifier 22; the first end address of the Nc3 interface address includes IP#1, port#1, and tunnel identifier 31, and the second end address includes IP#2, port#2, and tunnel identifier 32; and the first end address of the Nc4 interface address includes IP#1, port#1, and tunnel identifier 41, and the second end address includes IP#2, port#2, and tunnel identifier 42.

[0228] Tunnel identifiers 11 and 12 are used to identify computing task 1 of terminal device 1, tunnel identifiers 21 and 22 are used to identify computing task 2 of terminal device 1, tunnel identifiers 31 and 32 are used to identify computing task 1 of terminal device 2, and tunnel identifiers 41 and 42 are used to identify computing task 2 of terminal device 2. Tunnel identifiers 11 and 12 constitute tunnel identifier pair 1, tunnel identifiers 21 and 22 constitute tunnel identifier pair 2, tunnel identifiers 31 and 32 constitute tunnel identifier pair 3, and tunnel identifiers 41 and 42 constitute tunnel identifier pair 4. In other words, the two computing tasks of terminal device 1 correspond to tunnel identifier pair 1 and tunnel identifier pair 2, respectively, and the two computing tasks of terminal device 2 correspond to tunnel identifier pair 3 and tunnel identifier pair 4, respectively. In other words, different tunnel identifier pairs correspond one-to-one to different computing tasks of the same (and / or different) terminal devices.

[0229] Optionally, the tunnel identifier is used to identify computing tasks of different computing power services of the same terminal device, and different IP addresses identify different terminal devices. That is, different tunnel identifiers are associated with computing tasks of different computing power services of the same terminal device, and different IPs are associated with different terminal devices. In this case, the first end address of the Nc 1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#1, and tunnel identifier 1; the first end address of the Nc 2 interface address includes IP#1, port#1, and tunnel identifier 2, and the second end address includes IP#2, port#1, and tunnel identifier 2; the first end address of the Nc 3 interface address includes IP#3, port#1, and tunnel identifier 3, and the second end address includes IP#4, port#1, and tunnel identifier 3; the first end address of the Nc 4 interface address includes IP#3, port#1, and tunnel identifier 4, and the second end address includes IP#4, port#1, and tunnel identifier 4.

[0230] Among them, tunnel identifier 1 is used to identify computing task 1 of computing service 1, and tunnel identifier 2 is used to identify computing task 2 of computing service 2. In other words, the two computing tasks of different computing services correspond to tunnel identifier 1 and tunnel identifier 2 respectively; in other words, different tunnel identifiers correspond one-to-one to the computing tasks of different computing services of the same terminal device. In addition, different IP addresses can identify different terminal devices. For example, IP#1 and IP#2 are used to identify terminal device 1, and IP#3 and IP#4 are used to identify terminal device 2, where IP#1 and IP#2 constitute IP address 1, and IP#3 and IP#4 constitute IP address 2. In other words, IP address 1 identifies terminal device 1, and IP address 2 identifies terminal device 2.

[0231] Optionally, the tunnel identifier is used to identify computing tasks of different computing power services of the same terminal device, and different port numbers identify different terminal devices. That is, different tunnel identifiers are associated with computing tasks of different computing power services of the same terminal device, and different port numbers are associated with different terminal devices. In this case, the first end address of the Nc 1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#1, and tunnel identifier 1; the first end address of the Nc 2 interface address includes IP#1, port#1, and tunnel identifier 2, and the second end address includes IP#2, port#1, and tunnel identifier 2; the first end address of the Nc 3 interface address includes IP#1, port#2, and tunnel identifier 1, and the second end address includes IP#2, port#2, and tunnel identifier 1; the first end address of the Nc 4 interface address includes IP#1, port#2, and tunnel identifier 2, and the second end address includes IP#2, port#2, and tunnel identifier 2.

[0232] Tunnel ID 1 identifies computing task 1 for computing service 1, and tunnel ID 2 identifies computing task 2 for computing service 2. In other words, two computing tasks for different computing services correspond to tunnel ID 1 and tunnel ID 2, respectively; in other words, different tunnel IDs correspond one-to-one to computing tasks for different computing services on the same terminal device. Furthermore, different port numbers can identify different terminal devices. For example, port #1 identifies terminal device 1, and port #2 identifies terminal device 2.

[0233] Optionally, the tunnel identifier is used to identify different terminal devices, and different port numbers identify different computing tasks for the same terminal device. That is, different tunnel identifiers are associated with different terminal devices, and different port numbers are associated with different computing tasks for the same terminal device. In this case, the first end address of the Nc1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#1, and tunnel identifier 1; the first end address of the Nc2 interface address includes IP#1, port#2, and tunnel identifier 1, and the second end address includes IP#2, port#2, and tunnel identifier 1; the first end address of the Nc3 interface address includes IP#1, port#1, and tunnel identifier 2, and the second end address includes IP#2, port#1, and tunnel identifier 2; and the first end address of the Nc4 interface address includes IP#1, port#2, and tunnel identifier 2, and the second end address includes IP#2, port#2, and tunnel identifier 2.

[0234] Tunnel ID 1 identifies terminal device 1, and tunnel ID 2 identifies terminal device 2. In other words, different terminal devices correspond to tunnel ID 1 and tunnel ID 2, respectively; in other words, different tunnel IDs correspond one-to-one with different terminal devices. Furthermore, different port numbers can identify different computing tasks on the same terminal device. For example, port #1 identifies computing task 1, and port #2 identifies computing task 2.

[0235] It should also be noted that the description in (1) above is only an example of a tunnel identifier used to identify different computing tasks of the same terminal device or computing tasks of different computing services. Tunnel identifiers, IP addresses and port numbers can also have other combinations to identify different forms of computing tasks, and this application does not limit this.

[0236] (2) When the Nc interface address is associated with one or more computing tasks of a computing service, the above-mentioned request information 1 to request information 3 may also carry the identifier of the terminal device. The Nc corresponds to one computing task of a computing service, and the one computing task corresponds to one terminal device; or the Nc corresponds to multiple computing tasks of the computing service, and the multiple computing tasks are associated with different terminal devices; or the Nc corresponds to multiple computing tasks of the computing service, and the multiple computing tasks are associated with the same terminal device.

[0237] Exemplarily, a tunnel identifier, IP address, or port number is used to identify different computing tasks. Specifically, the NC interface address identifies different computing tasks by using different tunnel identifiers, IP addresses, or port numbers. For example, tunnel identifier 1 identifies computing task 1, and tunnel identifier 2 identifies computing task 2. Computing task 1 and computing task 2 belong to the same computing power service / computing power function, and different calls to the computing power service can use the same NC interface address.

[0238] For example, Nc 1 corresponds to computing task 1, and Nc 2 corresponds to computing task 2. Computing task 1 and computing task 2 belong to different computing power services.

[0239] Optionally, the tunnel identifier is used to identify different computing tasks for different computing services. That is, different tunnel identifiers are associated with different computing tasks for different computing services. In this case, the first end address of the Nc 1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#2, and tunnel identifier 1; the first end address of the Nc 2 interface address includes IP#1, port#1, and tunnel identifier 2, and the second end address includes IP#2, port#2, and tunnel identifier 2.

[0240] Tunnel ID 1 is used to identify computing task 1, and tunnel ID 2 is used to identify computing task 2. In other words, different computing tasks of different computing services correspond to tunnel ID 1 and tunnel ID 2 respectively; in other words, different tunnel IDs correspond one-to-one to different computing tasks of different computing services.

[0241] Optionally, IP addresses are used to identify different computing tasks for different computing services. That is, different IP addresses are associated with different computing tasks for different computing services. In this case, the first end address of the Nc 1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#1, and tunnel identifier 1. The first end address of the Nc 2 interface address includes IP#3, port#1, and tunnel identifier 2, and the second end address includes IP#4, port#1, and tunnel identifier 2.

[0242] Among them, IP#1 and IP#2 are used to identify computing task 1, and IP#3 and IP#4 are used to identify computing task 2. Among them, IP#1 and IP#2 constitute IP address 1, and IP#3 and IP#4 constitute IP address 2. In other words, different computing tasks of different computing services correspond to IP address 1 and IP address 2 respectively; in other words, different IP addresses correspond one-to-one to different computing tasks of different computing services. Optionally, when using IP addresses to identify different computing tasks of different computing services, the Nc interface address may not include a tunnel identifier. For example, the Nc 1 interface address does not include tunnel identifier 1, and the Nc 2 interface address does not include tunnel identifier 2.

[0243] Optionally, the port number is used to identify different computing tasks for different computing services. That is, different port numbers are associated with different computing tasks for different computing services. In this case, the first end address of the Nc1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#1, and tunnel identifier 1; the first end address of the Nc2 interface address includes IP#1, port#2, and tunnel identifier 2, and the second end address includes IP#2, port#2, and tunnel identifier 2.

[0244] Among them, port#1 is used to identify computing task 1, and port#2 is used to identify computing task 2. In other words, different computing tasks of different computing services correspond to port number 1 and port number 2, respectively; in other words, different port numbers correspond one-to-one with different computing tasks of different computing services. Optionally, when using port numbers to identify different computing tasks of different computing services, the Nc interface address can include no tunnel identifier. For example, the Nc 1 interface address does not include tunnel identifier 1, and the Nc 2 interface address does not include tunnel identifier 2.

[0245] Optionally, port number pairs are used to identify different computing tasks for different computing services. That is, different port number pairs are associated with different computing tasks for different computing services. In this case, the first end address of the Nc 1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#3, and tunnel identifier 1; the first end address of the Nc 2 interface address includes IP#1, port#2, and tunnel identifier 2, and the second end address includes IP#2, port#4, and tunnel identifier 2.

[0246] Among them, port#1 and port#3 are used to identify computing task 1, and port#2 and port#4 are used to identify computing task 2. Port#1 and port#3 constitute port number pair 1, and port#2 and port#4 constitute port number pair 2. In other words, different computing tasks of different computing power services correspond to port number pair 1 and port number pair 2, respectively; or, different port number pairs correspond one-to-one to different computing tasks of different computing power services. Optionally, when using port number pairs to identify different computing tasks of different computing power services, the Nc interface address may not include a tunnel identifier. For example, the Nc 1 interface address does not include tunnel identifier 1, and the Nc 2 interface address does not include tunnel identifier 2.

[0247] It should be noted that the description in (2) above is only an example of using the information in the Nc interface address to identify different computing tasks. Tunnel identifiers, IP addresses, and port numbers can also have other combinations to identify different forms of computing tasks, and this application does not limit this.

[0248] (3) When the Nc interface address is associated with a terminal device, the above request information 1 to request information 3 may also carry the computing power service identifier of computing task 1.

[0249] For example, Nc 1 corresponds to terminal device 1, and Nc 2 corresponds to terminal device 2.

[0250] Exemplarily, a tunnel identifier, IP address, or port number is used to identify different terminal devices. Specifically, the Nc interface address identifies different terminal devices by using different tunnel identifiers, IP addresses, or port numbers. For example, tunnel identifier 1 identifies terminal device 1, and tunnel identifier 2 identifies terminal device 2.

[0251] Optionally, the tunnel identifier is used to identify different terminal devices. That is, different tunnel identifiers are associated with different terminal devices. In this case, the first end address of the Nc1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#1, and tunnel identifier 1. The first end address of the Nc2 interface address includes IP#1, port#1, and tunnel identifier 2, and the second end address includes IP#2, port#1, and tunnel identifier 2.

[0252] Tunnel ID 1 is used to identify terminal device 1, and tunnel ID 2 is used to identify terminal device 2. In other words, different tunnel IDs correspond to different terminal devices on a one-to-one basis.

[0253] Optionally, IP addresses are used to identify different terminal devices; that is, different IP addresses are associated with different terminal devices. In this case, the first-end address of the NC1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second-end address includes IP#2, port#1, and tunnel identifier 1. The first-end address of the NC2 interface address includes IP#3, port#1, and tunnel identifier 2, and the second-end address includes IP#4, port#1, and tunnel identifier 2.

[0254] IP#1 and IP#2 are used to identify terminal device 1, and IP#3 and IP#4 are used to identify terminal device 2. IP#1 and IP#2 constitute IP address 1, and IP#3 and IP#4 constitute IP address 2. In other words, different IP addresses correspond one-to-one to different terminal devices. Optionally, when using IP addresses to identify different terminal devices, the Nc interface address may not include a tunnel identifier. For example, the Nc 1 interface address does not include tunnel identifier 1, and the Nc 2 interface address does not include tunnel identifier 2.

[0255] Optionally, the port number is used to identify different terminal devices. That is, different port numbers are associated with different terminal devices. In this case, the first end address of the NC1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#1, and tunnel identifier 1. The first end address of the NC2 interface address includes IP#1, port#2, and tunnel identifier 2, and the second end address includes IP#2, port#2, and tunnel identifier 2.

[0256] Port#1 is used to identify terminal device 1, and port#2 is used to identify terminal device 2. That is, different port numbers correspond one-to-one to different terminal devices. Optionally, when using port numbers to identify different terminal devices, the NC interface address may not include a tunnel identifier. For example, the NC1 interface address does not include tunnel identifier 1, and the NC2 interface address does not include tunnel identifier 2.

[0257] It should be noted that the description in (3) above is only an example of using the information in the Nc interface address to identify different terminal devices. Tunnel identifiers, IP addresses, and port numbers can also be used in other combinations to identify terminal devices, and this application does not limit this.

[0258] (4) When Nc UL address 1 is associated with a node or a pair of nodes, the above request information 1 to request information 3 may also carry the computing power service identifier of computing task 1.

[0259] Exemplarily, a tunnel identifier, IP address, or port number is used to identify a node-level NC. Specifically, the NC interface address identifies different NCs by using different tunnel identifiers, IP addresses, or port numbers. For example, tunnel identifier 1 identifies NC 1, and tunnel identifier 2 identifies NC 2.

[0260] Optionally, tunnel identifiers are used to identify different nodes. That is, different tunnel identifiers are associated with different nodes. For example, the first end address of the Nc1 interface address includes IP#1, port#1, and tunnel identifier 1, and the second end address includes IP#2, port#2, and tunnel identifier 1. The first end address of the Nc2 interface address includes IP#1, port#1, and tunnel identifier 2, and the second end address includes IP#2, port#2, and tunnel identifier 2.

[0261] Tunnel ID 1 is used to identify Nc 1, and tunnel ID 2 is used to identify Nc 2. That is, different tunnel IDs correspond to different Nc nodes on a one-to-one basis.

[0262] It should be noted that the description in (4) above is only an example of using the information in the Nc interface address to identify different nodes. Tunnel identifiers, IP addresses, and port numbers can also be used in other combinations to identify nodes, and this application does not limit this.

[0263] S306 . The collaboration node provides function instance 1 for computing task 1 .

[0264] Exemplarily, when the collaborative node provides computing resources for computing task 1, the access computing node sends a request message (for example, request message 3) to the collaborative node, and the request message 3 carries the computing power service identifier of computing task 1 to trigger the collaborative node to prepare function instance 1. Alternatively, the access computing node sends a request message (for example, request message 1) to the collaborative node through the core network to request the collaborative node to prepare function instance 1. After the collaborative node receives the request message (for example, request message 2 or request message 3), if the collaborative node does not have the function instance required by a certain computing task locally, the collaborative node first dynamically triggers the instantiation of the computing power function 1 corresponding to computing task 1 to obtain function instance 1, so as to activate the computing processing function of the function instance 1 corresponding to computing task 1. Among them, the collaborative node dynamically triggers the instantiation of the computing power function 1 corresponding to computing task 1 to obtain function instance 1, which may include at least one of the following:

[0265] Scheduling of computing power function 1 container resources;

[0266] Operation of computing power function 1 container resources;

[0267] Loading of computing power function 1;

[0268] The operation of computing power function 1.

[0269] It should be noted that in steps S304a to S304d and S305a to S305b, the operation in which the coordinating node allocates a unicast IP address for access to computing task 1 after receiving the request information (e.g., request information 2 or request information 3) can also be implemented in step S306. In other words, when the coordinating node provides function instance 1 to computing task 1, it can also allocate a unicast IP address for access to computing task 1.

[0270] Furthermore, the collaboration node stores forwarding rule information of data associated with the computing task 1 of the terminal device.

[0271] The forwarding rule instructs the collaborative node to forward the received uplink data on the Nc tunnel to the function instance 1 corresponding to the accessed unicast IP address. Furthermore, the function instance 1 corresponding to the accessed unicast IP address receives downlink data and sends it to the access node on the Nc tunnel.

[0272] The forwarding rule includes an upstream rule and a downstream rule, and the forwarding rule information includes any of the following:

[0273] 1) When each Nc interface address is associated with one or more computing tasks of a computing power service of a terminal device, for example, Nc UL address 1 in the Nc1 interface address is associated with computing task 1 of terminal device 1 (the computing task 1 belongs to computing power service 1), Nc UL address 2 in the Nc2 interface address is associated with computing task 2 of terminal device 1 (the computing task 2 belongs to computing power service 2), and Nc UL address 3 in the Nc3 interface address is associated with computing task 1 of terminal device 2 (the computing task 1 belongs to computing power service 1). At this time, the forwarding rule information includes: the Nc interface address and the unicast IP address accessed by the computing task. Optionally, it can also be understood that the Nc interface address is associated with all computing tasks of a computing power service of a terminal device, that is, different computing tasks of the computing power service of a terminal device at different times can be associated with the same Nc.

[0274] More specifically, as shown in the three Nc tunnels in Figure 4(a) and Figure 5, the uplink rule information includes: Nc UL address 1 and the unicast IP address of function instance 1 accessed by computing task 1; Nc UL address 2 and the unicast IP address of function instance 2 accessed by computing task 2; Nc UL address 3 and the unicast IP address of function instance 3 accessed by computing task 3.

[0275] Exemplarily, as shown in the three Nc tunnels in Fig. 4(a) and Fig. 5, Nc 1 corresponds to computing task 1, Nc 2 corresponds to computing task 2, and Nc 3 corresponds to computing task 3. At this time, the uplink forwarding rule information includes: Nc DL address 1, Nc UL address 1, and the unicast IP address accessed by computing task 1; Nc DL address 2, Nc UL address 2, and the unicast IP address accessed by computing task 2; Nc DL address 3, Nc UL address 3, and the unicast IP address accessed by computing task 3.

[0276] For example, the uplink forwarding rule information includes:

[0277] <IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1; the unicast IP address accessed by computing task 1>;

[0278] <IP#1, port#1, tunnel identifier 2; IP#2, port#1, tunnel identifier 2; the unicast IP address accessed by computing task 2>;

[0279] <IP#1, port#1, tunnel identifier 3, IP#2, port#1, tunnel identifier 3; the unicast IP address accessed by computing task 3>.

[0280] The downlink rule information includes: the identifier of terminal device 1, Nc DL address 1, and Nc UL address 1; the identifier of terminal device 2, Nc DL address 2, and Nc UL address 2; the identifier of terminal device 3, Nc DL address 3, and Nc UL address 3. Hereinafter, the terminal device is described by taking UE as an example.

[0281] For example, the downlink forwarding rule information includes:

[0282] <Five-tuple {UE 1 IP, UE 1 side port number (optional), function instance IP 1 (optional), port number 1, protocol (optional)}; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>;

[0283] <Five-tuple {UE2 IP, UE 2 side port number (optional), function instance IP 2 (optional), port number 2, protocol (optional)}; IP#1, port#1, tunnel identifier 2; IP#2, port#1, tunnel identifier 2>;

[0284] <Five-tuple {UE2 IP, UE 2 side port number (optional), function instance IP 1 (optional), port number 1, protocol (optional)}; IP#1, port#1, tunnel identifier 3; IP#2, port#1, tunnel identifier 3>.

[0285] Among them, the five-tuple in the downlink can also be other identifiers for identifying transmission channels or transmission streams or transmission connections at the UE granularity between the collaborative nodes and the application instances.

[0286] Among them, the Nc interface address includes the Nc DL address and the Nc UL address. This Nc interface is used to transmit data of the computing task corresponding to the terminal device. For example, the Nc 1 interface address includes the Nc DL address 1 and the Nc UL address 1, and at this time, the Nc 1 interface is used to transmit data of the computing task 1 corresponding to the terminal device 1.

[0287] 2) When each Nc interface address is associated with one or more computing tasks of a computing power service, and each computing task in the multiple computing tasks of a computing power service is associated with a terminal device, that is, when the Nc interface address is associated with multiple terminal devices corresponding to multiple computing tasks of a computing power service, for example, the Nc UL address 1 in the Nc 1 interface address is associated with the computing power service 1, and this computing service 1 corresponds to multiple terminal devices. At this time, the forwarding rule information includes: the Nc interface address, the unicast IP address accessed by the computing task. Optionally, the forwarding rule information further includes the computing power service identifier of the computing task (for example, the computing power service identifier of the computing task 1).

[0288] More specifically, as shown in the three Nc tunnels in Figure 4(a) and Figure 5, the uplink rule information includes: the Nc DL address 1, the Nc UL address 1, and the unicast IP address accessed by the computing task 1; the Nc DL address 2, the Nc UL address 2, and the unicast IP address accessed by the computing task 2; the Nc DL address 3, the Nc UL address 3, and the unicast IP address accessed by the computing task 3.

[0289] For example, the uplink forwarding rule information includes:

[0290] <IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1; the unicast IP address accessed by the computing task 1>;

[0291] <IP#1, port#1, tunnel identifier 2; IP#2, port#1, tunnel identifier 2; the unicast IP address accessed by the computing task 2>;

[0292] <IP#1, port#1, tunnel identifier 3; IP#2, port#1, tunnel identifier 3; the unicast IP address accessed by the computing task 3>;

[0293] Among them, the tunnel identifier is used to identify different computing tasks, and different computing tasks belong to different computing power services.

[0294] The downlink rule information includes: computing service identifier, Nc DL address 1, and Nc UL address 1 of computing task 1; computing service identifier, Nc DL address 2, and Nc UL address 2 of computing task 2; and computing service identifier, Nc DL address 3, and Nc UL address 3 of computing task 3. The multiple terminal devices associated with a computing task all transmit data through an Nc interface, and downlink data from different UEs in the same function instance are mapped to the same Nc interface.

[0295] For example, the downlink forwarding rule information includes:

[0296] <quintuple {UE 1's IP, UE 1's port number (optional), function example IP 1 (optional), port number 1, protocol (optional)}; IP#1, port#1, tunnel ID 1; IP#2, port#1, tunnel ID 1>;

[0297] <quintuple {UE2IP, UE2 side port number (optional), function instance IP 1 (optional), port number 1, protocol (optional)}; IP#1, port#1, tunnel ID 1; IP#2, port#1, tunnel ID 1>;

[0298] <quintuple {UE3IP, UE 3 side port number (optional), function instance IP 1 (optional), port number 1, protocol (optional)}; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>.

[0299] 3) When each Nc interface address is associated with a terminal device, that is, when there is a one-to-one correspondence between Nc interface addresses and terminal devices, for example, Nc UL address 1 in the Nc1 interface address is associated with terminal device 1, the forwarding rule information includes: the Nc interface address, the unicast IP address accessed by the computing task, and the computing power service identifier of the computing task. Optionally, the forwarding rule information also includes the identifier of the terminal device (for example, the identifier of terminal device 1 associated with computing task 1).

[0300] More specifically, the uplink rule information includes: Nc UL address 1, the destination IP address 1 of the uplink data of computing task 1, and the unicast IP address accessed by computing task 1; Nc UL address 2, the destination IP address 2 of the uplink data of computing task 2, and the unicast IP address accessed by computing task 2; Nc UL address 3, the destination IP address 3 of the uplink data of computing task 3, and the unicast IP address accessed by computing task 3.

[0301] For example, the uplink forwarding rule information includes:

[0302] <IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1; computing power service identifier for computing task 1; unicast IP address accessed by computing task 1>; At this time, the corresponding Nc1 interface address of terminal device 1, and terminal device 1 corresponds to computing task 1.

[0303] <IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1; computing power service identifier for computing task 2; unicast IP address accessed by computing task 2>; At this time, the corresponding Nc1 interface address of terminal device 1, and terminal device 1 corresponds to computing task 2.

[0304] <IP#1, port#1, tunnel identifier 2; IP#2, port#1, tunnel identifier 2; computing power service identifier for computing task 3; unicast IP address accessed by computing task 1>; At this time, the corresponding Nc2 interface address of terminal device 2.

[0305] Among them, different tunnel identifiers are used to identify different terminal devices.

[0306] The downlink rule information includes: identifier of terminal device 1, Nc DL address 1 and Nc UL address 1; identifier of terminal device 2, Nc DL address 2 and Nc UL address 2; identifier of terminal device 3, Nc DL address 3 and Nc UL address 3.

[0307] For example, the downlink forwarding rule information includes:

[0308] <Five-tuple {IP of UE 1, port number on the UE 1 side (optional), function example IP 1 (optional), port number 1, protocol (optional)}; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>;

[0309] <Five-tuple {IP of UE 1, port number on the UE 1 side (optional), function example IP 2 (optional), port number 2, protocol (optional)}; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>;

[0310] <Five-tuple {IP of UE2, port number on the UE 2 side (optional), function instance IP 1 (optional), port number 3, protocol (optional)}; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>.

[0311] <Five-tuple {UE2IP, UE 2-side port number (optional), Function Instance IP 2 (optional), port number 3, protocol (optional)}; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>.

[0312] 4) When an Nc interface address is associated with a node or a pair of nodes, for example, the Nc 1 interface address is associated with the first node (or called the access computing node). At this time, the forwarding rule information includes: NcDL address, Nc UL address, the unicast IP address accessed by the computing task, and the computing power service identifier of the computing task. Optionally, the forwarding rule information further includes the identifier of the terminal device (for example, the identifier of terminal device 1 associated with computing task 1).

[0313] More specifically, for an Nc tunnel in Figure 6, the upstream rule information includes: Nc DL address 1, Nc UL address 1, the destination IP address 1 of the upstream data of computing task 1, and the unicast IP address accessed by computing task 1; Nc DL address 2, Nc UL address 2, the destination IP address 2 of the upstream data of computing task 2, and the unicast IP address accessed by computing task 2; Nc DL address 3, Nc UL address 3, the destination IP address 3 of the upstream data of computing task 3, and the unicast IP address of computing task 3.

[0314] An example of the specific upstream forwarding rule information is as follows: The tunnel identifier indicates different UEs

[0315] <IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1; the computing power service identifier of computing task 1; the unicast IP address accessed by computing task 1>; At this time, the Nc interface address is associated with access computing node 1.

[0316] <IP#3, port#1, tunnel identifier 2; IP#4, port#1, tunnel identifier 2; the computing power service identifier of computing task 2; the unicast IP address accessed by computing task 2>; At this time, the Nc interface address is associated with access computing node 2.

[0317] The downstream rule information includes: Nc DL address 1 and Nc UL address 1; Nc DL address 2 and Nc UL address 2; Nc DL address 3 and Nc UL address 3.

[0318] An example of the downstream forwarding rule information is as follows:

[0319] <quintuple {UE 1 IP, UE 1 side port number (optional), function example IP 1 (optional), port number 1, protocol (optional)}; IP#1, port#1, tunnel ID 1; IP#2, port#1, tunnel ID 1>;

[0320] <quintuple {UE 1 IP, UE 2 side port number (optional), function example IP 2 (optional), port number 2, protocol (optional)}; IP#1, port#1, tunnel ID 1; IP#2, port#1, tunnel ID 1>;

[0321] <quintuple {UE1IP, UE2 side port number (optional), function instance IP 2 (optional), port number 3, protocol) (optional)}; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>.

[0322] S307. The access computing node allocates air interface bearer 1 and computing power bearer identifier 1 to function instance 1.

[0323] Among them, computing task 1 is associated with computing power bearer identifier 1, and computing power bearer identifier 1 can be called Uu computing power bearer identifier 1 (i.e., Uu ID#1); or computing power bearer identifier 1 can be a DRB identifier; or an air interface bearer identifier. In other words, computing power bearer identifier 1 is used to indicate air interface bearer 1, which can transmit data associated with computing task 1 scheduled by the scheduling request. It can be understood that computing power bearer is an air interface data bearer. In other words, air interface bearer 1 indicates the communication resources used for data transmission between the terminal device and the access computing node.

[0324] Optionally, the computing power bearer identifier 1 is also associated with a set of computing power QoS parameters, which include transmission QoS parameters and calculation QoS parameters. The set of computing power QoS parameters can be identified by computing power QCI, where different computing power QoS parameters use different computing power QCIs, and different computing power QCIs identify different grades or levels of computing power QoS requirements and guarantees. Optionally, the set of computing power QoS parameters can also be identified by QoS flow, or the set of computing power QoS parameters can be identified by QCI. When the transmission QCI and the calculation QCI are two independent parameters, a set of computing power QoS parameters can be identified by a combination of the transmission QCI and the calculation QCI.

[0325] Exemplarily, the access computing node determines the computing power bearer identifier 1 based on the scheduling request of the above-mentioned computing task 1. After the access computing node allocates air interface resources and the computing power bearer identifier 1 to the function instance 1, the access computing node stores the computing power bearer identifier 1, or stores the computing power bearer identifier 1 and the computing power service identifier of the computing task 1; optionally, the access computing node may also store the computing power bearer identifier 1 and the identifier 1 of the QoS flow, or the access computing node may also store the computing power bearer identifier 1 and the QCI identifier 1.

[0326] Optionally, the computing power service identifier of computing task 1 may include the unicast IP address accessed by the computing task 1.

[0327] It should be noted that the computing power carrying identifier 1 allocated by the access node to function instance 1 can be associated with computing task 1 or multiple computing tasks. In other words, the computing power carrying identifiers corresponding to the scheduling of multiple computing tasks are the same.

[0328] It should also be noted that, when collaborative nodes are involved, the association between computing tasks and computing power bearer identifiers, as well as the association between computing tasks and Nc interface addresses, can be combined. Specifically, there are the following:

[0329] Each computing task is uniquely associated with a computing power bearer identifier, and the computing power bearer identifier is uniquely associated with the computing task. Multiple computing tasks are associated with multiple NC interface addresses (as shown in Figure 4(a)), where each of the multiple computing tasks belongs to a different computing power service; or each computing power service is uniquely associated with a computing power bearer identifier, and the computing power bearer identifier is uniquely associated with the computing power service. Multiple computing tasks of a computing power service are associated with the same NC interface address at different times (as shown in Figure 4(a)).

[0330] Each computing task is uniquely associated with a computing power bearer identifier, and the computing power bearer identifier is uniquely associated with the computing task, and multiple computing tasks are associated with one Nc interface address (as shown in Figure 4(b)), where each of the multiple computing tasks belongs to a different computing power service; or

[0331] Each computing power service is uniquely associated with a computing power bearer identifier, and the computing power bearer identifier is uniquely associated with the computing task. Multiple computing tasks are associated with one Nc interface address (as shown in Figure 4(b)), where each of the multiple computing tasks belongs to a different computing power service; or

[0332] Multiple computing tasks (the multiple computing tasks belong to the same computing power service or different computing power services) are associated with one computing power bearer identifier, and each computing task is uniquely associated with one Nc interface address, that is, one Nc interface address is uniquely associated with the computing task (as shown in FIG5 ), wherein each computing task belongs to one computing power service, that is, each computing task of the multiple computing tasks belongs to a different computing power service; or

[0333] Multiple computing tasks (these multiple computing tasks belong to the same computing power service or different computing power services) are associated with a computing power bearer identifier, and multiple computing tasks are associated with an Nc interface address (as shown in Figure 6), where each of the multiple computing tasks belongs to a different computing power service.

[0334] Furthermore, the access computing node stores the forwarding context of computing task 1 corresponding to the terminal device. The forwarding context is used to indicate whether the access computing node forwards the uplink data of computing task 1 to the local function instance of the access computing node or to the collaborative node.

[0335] As an example, when the access computing node provides all computing resources for computing task 1, the forwarding context stored by the access computing node includes: computing power bearer identifier 1. Optionally, the forwarding context may also include the computing power service identifier of computing task 1 and / or QoS flow identifier 1, where QoS flow identifier 1 is used to identify the QoS of computing task 1. At this time, the access computing node forwards the uplink data to the local function instance of the access computing node.

[0336] More specifically, the forwarding context stored in the access computing node may be any of the following:

[0337] 1) When each computing power bearer identifier is associated with one or more computing tasks of a computing power service, the forwarding context includes the computing power bearer identifier. For example, the forwarding context includes computing power bearer identifier 1, and computing power bearer identifier 1 is associated with computing task 1.

[0338] 2) When a computing power bearer identifier is associated with multiple computing tasks, and each of the multiple computing tasks belongs to a different computing power service, the forwarding context includes the computing power bearer identifier and the computing power service identifier of the computing task. For example, the forwarding context includes the computing power bearer identifier 1 and the computing power service identifier of computing task 1.

[0339] Optionally, when a computing power bearer identifier is associated with multiple computing tasks, the forwarding context may include the computing power bearer identifier and the QoS flow identifier, for example, the forwarding context includes the computing power bearer identifier 1 and the QoS flow identifier 1.

[0340] As another example, when the collaborative node provides all the computing resources for computing task 1, the forwarding context stored in the access general computing node includes: the relationship between computing power bearing identifier 1 and the Nc 1 interface address. Optionally, the forwarding context may include the relationship between computing power bearing identifier 1, the Nc1 interface address, and the computing power service identifier of computing task 1, or the relationship between computing power bearing identifier 1, the Nc 1 interface address, and the identifier 1 of the QoS flow. At this time, the access general computing node forwards the uplink data to the collaborative node.

[0341] More specifically, the forwarding context stored in the access general computing node can be specifically divided into any one of the following:

[0342] 1) When one computing task or multiple computing tasks or all computing tasks of a computing power service are uniquely associated with one computing power bearing identifier, and this computing power bearing identifier is uniquely associated with one computing task or multiple computing tasks or all computing tasks of this computing power service, each computing task of multiple computing tasks is associated with one Nc interface address, or multiple computing tasks belonging to the same computing power service are associated with one Nc, the Nc interface address forwarding context includes the relationship between the computing power bearing identifier and the Nc interface address. For example, the forwarding context includes the relationship between computing power bearing identifier 1 and the Nc 1 interface address.

[0343] Among them, the context in the uplink direction includes:

[0344] <Computing power bearing identifier 1; IP#1, port#1, tunnel identifier 1; IP#2, port#1, tunnel identifier 1>;

[0345] <Computing power bearing identifier 2; IP#1, port#1, tunnel identifier 2; IP#2, port#1, tunnel identifier 2>;

[0346] <Computing power bearing identifier 3; IP#1, port#1, tunnel identifier 3; IP#2, port#1, tunnel identifier 3>.

[0347] The context in the downlink direction includes:

[0348] <IP#2, port#1, tunnel identifier 1; IP#1, port#1, tunnel identifier 1; Computing power bearing identifier 1>;

[0349] <IP#2, port#1, tunnel identifier 2; IP#1, port#1, tunnel identifier 2; Computing power bearing identifier 2>;

[0350] <IP#2, port#1, tunnel identifier 3; IP#1, port#1, tunnel identifier 3; Computing power bearing identifier 3>.

[0351] 2) When one computing task, multiple computing tasks, or all computing tasks of a computing power service are uniquely associated with a computing power bearer identifier, and the computing power bearer identifier is uniquely associated with one computing task, multiple computing tasks, or all computing tasks of the computing power service, and multiple computing power services are associated with an Nc interface address, wherein each of the multiple computing power services includes one or more computing tasks, and the Nc interface address forwarding context includes the relationship between the computing power bearer identifier, the Nc interface address, and the computing power service identifier of the computing task, for example, the forwarding context includes the relationship between the computing power bearer identifier 1, the Nc 1 interface address, and the computing power service identifier of computing task 1.

[0352] Optionally, when multiple computing tasks are associated with multiple QoS flow identifiers, the forwarding context may include the relationship between the computing power bearer identifier, the Nc interface address and the QoS flow identifier. For example, the forwarding context includes the relationship between the computing power bearer identifier 1, the Nc 1 interface address and the QoS flow identifier 1.

[0353] The uplink context includes:

[0354] <computing power bearer ID 1; IP#1, port#1, tunnel ID 1; IP#2, port#1, tunnel ID 1; computing power service ID of computing task 1>;

[0355] <computing power bearer ID 2; IP#1, port#1, tunnel ID 2; IP#2, port#1, tunnel ID 2; computing power service ID of computing task 2>;

[0356] <computing power bearer ID 3; IP#1, port#1, tunnel ID 3; IP#2, port#1, tunnel ID 3; computing power service ID of computing task 3>;

[0357] The context in the downstream direction includes:

[0358] <Computing power service ID of computing task 1; IP#2, port#1, tunnel ID 1; IP#1, port#1, tunnel ID 1; computing power carrying ID 1>;

[0359] <Computing power service identifier of computing task 2; IP#2, port#1, tunnel identifier 2; IP#1, port#1, tunnel identifier 2; computing power carrying identifier 2>;

[0360] <Computing power service identifier of computing task 3; IP#2, port#1, tunnel identifier 3; IP#1, port#1, tunnel identifier 3; computing power carrying identifier 3>.

[0361] 3) When multiple computing services are associated with a computing power bearer identifier, each of which includes one or more computing tasks, and a computing service is associated with an Nc interface address, each of which includes one or more computing tasks, the forwarding context includes the relationship between the computing power bearer identifier, the Nc interface address, and the computing power service identifier of the computing task. For example, the forwarding context includes the relationship between computing power bearer identifier 1, the Nc 1 interface address, and the computing power service identifier of computing task 1.

[0362] The uplink context includes:

[0363] <computing power bearer ID 1; IP#1, port#1, tunnel ID 1; IP#2, port#1, tunnel ID 1; computing power service ID of computing task 1>;

[0364] <computing power bearer ID 2; IP#1, port#1, tunnel ID 2; IP#2, port#1, tunnel ID 2; computing power service ID of computing task 2>;

[0365] <computing power bearer ID 3; IP#1, port#1, tunnel ID 3; IP#2, port#1, tunnel ID 3; computing power service ID of computing task 3>;

[0366] The context in the downstream direction includes:

[0367] <Computing power service ID of computing task 1; IP#2, port#1, tunnel ID 1; IP#1, port#1, tunnel ID 1; computing power carrying ID 1>;

[0368] <Computing power service identifier of computing task 2; IP#2, port#1, tunnel identifier 2; IP#1, port#1, tunnel identifier 2; computing power carrying identifier 2>;

[0369] <Computing power service identifier of computing task 3; IP#2, port#1, tunnel identifier 3; IP#1, port#1, tunnel identifier 3; computing power carrying identifier 3>.

[0370] 4) When each of multiple computing tasks is associated with an Nc interface address, or when multiple computing tasks belonging to the same computing power service are associated with an Nc, and multiple computing power services are associated with an Nc interface address, wherein each of the multiple computing power services includes one or more computing tasks, the forwarding context includes: the relationship between the computing power bearer identifier, the Nc interface address, and the computing power service identifier of the computing task. For example, the forwarding context includes the relationship between the computing power bearer identifier 1, the Nc 1 interface address, and the computing power service identifier of computing task 1. The context in the uplink direction includes:

[0371] <computing power bearer ID 1; IP#1, port#1, tunnel ID 1; IP#2, port#1, tunnel ID 1; computing power service ID of computing task 1>;

[0372] <computing power bearer ID 2; IP#1, port#1, tunnel ID 2; IP#2, port#1, tunnel ID 2; computing power service ID of computing task 2>;

[0373] <computing power bearer ID 3; IP#1, port#1, tunnel ID 3; IP#2, port#1, tunnel ID 3; computing power service ID of computing task 3>;

[0374] The context in the downstream direction includes:

[0375] <Computing power service ID of computing task 1; IP#2, port#1, tunnel ID 1; IP#1, port#1, tunnel ID 1; computing power carrying ID 1>;

[0376] <Computing power service identifier of computing task 2; IP#2, port#1, tunnel identifier 2; IP#1, port#1, tunnel identifier 2; computing power carrying identifier 2>;

[0377] <Computing power service identifier of computing task 3; IP#2, port#1, tunnel identifier 3; IP#1, port#1, tunnel identifier 3; computing power carrying identifier 3>.

[0378] S308: The access computing node sends a response message to the terminal device regarding the scheduling request for computing task 1. Correspondingly, the terminal device receives the response message regarding the scheduling request for computing task 1 from the access computing node.

[0379] Among them, the response information of the scheduling request carries the computing power carrying identifier 1.

[0380] Exemplarily, the scheduling response may be air interface control signaling, such as AS signaling. More specifically, the scheduling response may be RRC layer signaling, or MAC layer signaling, etc.

[0381] Optionally, the response information of the scheduling request also includes the unicast IP address accessed by computing task 1. When all computing resources of computing task 1 are provided by the access general computing node, the unicast IP address accessed by computing task 1 may be the unicast IP address allocated by the access general computing node for computing task 1; when all computing resources of computing task 1 are provided by the collaborative node, the unicast IP address accessed by computing task 1 may be the unicast IP address allocated by the collaborative node for computing task 1.

[0382] Optionally, when a computing power carrying identifier is associated with multiple computing tasks, the response information of the scheduling request carries the computing power service identifier of computing task 1.

[0383] S309: The terminal device sends first uplink data to the access communication node. Correspondingly, the access communication node receives the first uplink data from the terminal device.

[0384] The terminal device sends the first uplink data on the air interface bearer 1 indicated by the computing power bearer identifier 1, where the first uplink data is data associated with computing task 1. Exemplarily, the terminal device fills the destination IP address of the IP layer of the first uplink data with the access unicast IP address of computing task 1.

[0385] As an implementation method, the terminal device can carry the computing power bearer identifier 1 in the protocol header of the computing power routing layer, where the computing power routing layer can be the service data adaptation protocol (SDAP) layer, and then the terminal device sends the first uplink data on the air interface bearer indicated by the above computing power bearer identifier 1.

[0386] As another implementation, computing power bearer identifier 1 indicates air interface bearer 1, where air interface bearer 1 includes a resource indication and coding and modulation scheme information for the physical uplink shared channel (PUSCH). In this case, the terminal device does not explicitly carry computing power bearer identifier 1 in the computing power layer, but instead transmits data on air interface bearer 1 indicated by computing power bearer identifier 1. In other words, the first uplink data is sent on air interface bearer 1.

[0387] In an embodiment of the present application, the terminal device can directly send a first uplink data packet to the access computing node through the air interface bearer 2, and the first uplink data packet carries the second uplink data and the computing power service identifier of the computing task 1. The access computing node allocates a computing power bearer identifier 1 to the computing task 1 according to the computing power service identifier of the computing task 1. For example, the access computing node sends the second uplink data to the function instance 1 according to the computing power service identifier of the computing task 1. At this time, the function instance 1 is a local function instance of the access computing node. For another example, the access computing node sends the second data to the collaborative node based on the relationship between the computing power service identifier of the computing task 1 and the Nc 1 interface address, or the relationship between the computing power service identifier of the computing task 1, the Nc 1 interface address, and the identifier of the terminal device.

[0388] S310: The access computing node forwards the first uplink data.

[0389] The access computing node determines, according to the stored forwarding context, whether to forward the first uplink data to the local function instance of the access computing node or to the collaboration node.

[0390] As an example, when the forwarding context stored in the access computing node includes computing power bearer identifier 1; or when the forwarding context stored in the access computing node includes computing power bearer identifier 1 and computing power service identifier of computing task 1; or when the forwarding context stored in the access computing node includes computing power bearer identifier 1 and QoS flow identifier 1, the first uplink data is forwarded to the local function instance of the access computing node. The local function instance may be function instance 1 in step S303a above.

[0391] As another example, when the forwarding context stored in the access computing node includes the relationship between the computing power bearer identifier 1 and the Nc 1 interface address; or when the forwarding context stored in the access computing node includes the relationship between the computing power bearer identifier 1, the Nc 1 interface address and the computing power service identifier of the computing task 1; or when the forwarding context stored in the access computing node includes the relationship between the computing power bearer identifier 1, the Nc 1 interface address and the identifier 1 of the QoS flow, the first uplink data is sent to the collaboration node. At this time, the collaboration node is a node associated with function instance 1. When the access computing node forwards the first uplink data to the local function instance, method 300 also includes the steps of:

[0392] S310a: The access common computing node sends first uplink data to the function instance. Correspondingly, the function instance receives the first uplink data from the access common computing node.

[0393] The access computing node can send the first uplink data to the function instance based on the stored forwarding context. In this case, the function instance is the local function instance of the access computing node, that is, function instance 1 associated with the access computing node. A detailed description of the forwarding context is provided in step S307 and is not repeated here.

[0394] As an example, when the destination address of an uplink data packet is an anycast address, a virtual IP address, or the IP address of an access computing node, the access computing node selects function instance 1 (in this case, the access computing node can select function instance 1 from multiple function instances, and the multiple function instances serve computing task 1). The access computing node obtains the communication address of function instance 1 (e.g., an IP unicast address) and sends the first uplink data to function instance 1 according to the communication address. The uplink data packet carries the first uplink data.

[0395] As another example, when the destination address in the uplink data packet is the unicast IP address of function instance 1, it is directly forwarded to function instance 1.

[0396] S310b: The function instance sends the first downlink data of the terminal device to the access computing node. Correspondingly, the access computing node receives the first downlink data from the function instance.

[0397] Among them, the function instance is function instance 1 associated with the access computing node, the first downlink data is carried in the downlink data packet #1, and when function instance 1 sends the first downlink data to the collaborative node, the source address of the downlink data packet #1 can be the IP address of function instance 1, or it can be an anycast address, or a virtual IP address.

[0398] The first downlink data is the data after the function instance 1 processes the data to be processed.

[0399] When the access communication node forwards the first uplink data to the cooperation node, the method 300 includes the following steps:

[0400] S311a: The access communication node sends a second uplink data packet to the coordination node. Correspondingly, the coordination node receives the second uplink data packet from the access communication node.

[0401] The access computing node encapsulates the first uplink data according to the stored forwarding context to obtain a second uplink data packet. This second uplink data packet includes protocol header 1 and payload 1. The destination address of protocol header 1 is the Nc UL address, the source address of protocol header 1 is the Nc DL address 1, and payload 1 is determined by the first uplink data. Therefore, it can be understood that the first uplink data serves as payload 1 of the second uplink data packet. In other words, the second data packet is an Nc-encapsulated data packet. A detailed description of the forwarding context is provided in step S307 and will not be repeated here.

[0402] Exemplarily, when the Nc interface address is associated with one or more computing tasks of a computing power service, the protocol header 1 also carries the terminal device identifier or session identifier. When an Nc interface address is associated with a computing power service (i.e., Nc is the computing power service granularity), the protocol header 1 carries the terminal device identifier. When an Nc interface address is associated with a terminal device (i.e., Nc is at the terminal device granularity), the protocol header 1 carries the computing power service identifier of computing task 1. When an Nc interface address is associated with a node (i.e., Nc is at the node granularity), the protocol header 1 carries the computing power service identifier of computing task 1 and the terminal device identifier.

[0403] S311b: The coordination node sends the third uplink data to the function instance, wherein the third uplink data is the data after removing the protocol header 1 of the second uplink data packet.

[0404] When the destination address in the uplink data packet is an anycast address, a virtual IP address, or the IP address of the collaborative node, the collaborative node selects function instance 1 (at this time, the collaborative node can select function instance 1 from multiple function instances, and the multiple function instances serve computing task 1), the collaborative computing node obtains the communication address of function instance 1 (for example, a unicast IP address), and sends the third uplink data to function instance 1 according to the communication address.

[0405] When the destination address in the uplink data packet is the unicast IP address of function instance 1, it is forwarded directly to function instance 1.

[0406] S311c: The function instance sends the second downlink data to the collaboration node. Correspondingly, the collaboration node receives the second downlink data from the function instance.

[0407] Among them, the function instance is function instance 1 associated with the collaborative node, and the second downlink data is carried in downlink data packet #2. When the function instance sends the second downlink data to the collaborative node, the source address of downlink data packet #2 can be the IP address of the function instance, or it can be an anycast address, or a virtual IP address.

[0408] The second downstream data may be understood as data after function instance 1 processes the data to be processed.

[0409] It should be noted that the function instance in steps S311b and S311c is function instance 1 associated with the collaboration node.

[0410] S311d: The coordination node sends the first downlink data packet of the terminal device to the access communication node. Correspondingly, the access communication node receives the first downlink data packet from the coordination node.

[0411] The first downlink data packet includes a protocol header 2 and a payload 2. The destination address of the protocol header 2 is the aforementioned Nc DL address, the source address of the protocol header 2 is the aforementioned Nc UL address, and the payload 2 includes the second downlink data. In other words, the first downlink data packet is an Nc-encapsulated data packet. Specifically, the coordinating node performs Nc encapsulation on the second downlink data based on the stored forwarding rule information. The forwarding rule information is described in step S306 above and is not further described here.

[0412] Exemplarily, when the Nc interface address is associated with one or more computing tasks of a computing service, the protocol header 2 also carries the terminal device identifier or session identifier.

[0413] When an Nc interface address is associated with a terminal device, protocol header 2 carries the computing power service identifier of computing task 1. When an Nc interface address is associated with a terminal device, protocol header 1 carries the computing power service identifier of computing task 1. When an Nc interface address is associated with a node, protocol header 2 carries the computing power service identifier of computing task 1 and the terminal device identifier.

[0414] S312: The access communication node sends the third downlink data to the terminal device. Correspondingly, the terminal device receives the third downlink data from the access communication node.

[0415] Among them, the third downlink data is data associated with computing task 1. The access computing node determines the computing power bearer identifier 1 according to the Nc 1 interface address, and the access computing node sends the third downlink data to the terminal device through the air interface bearer 1 indicated by the computing power bearer identifier 1. The third downlink data is determined based on the above-mentioned first downlink data, or based on the above-mentioned second downlink data. Specifically, when the access computing node forwards the first uplink data to the local function instance of the access computing node, the third downlink data is determined based on the above-mentioned first downlink data; when the access computing node forwards the first uplink data to the collaborative node, the third downlink data is determined based on the above-mentioned second downlink data.

[0416] When the access computing node receives data from the collaborative node, that is, the second downlink data, the corresponding computing power bearer identifier 1 is determined according to the protocol header 2, wherein the corresponding computing power bearer identifier determined according to the protocol header 2 includes: the protocol header 2 is directly mapped to the computing power bearer identifier 1; or, the protocol header 2 carries the computing power service identifier of the computing task 1, and is mapped to the computing power bearer identifier 1 according to the computing power service identifier of the computing task 1. Next, the access computing node removes the protocol header 2 of the first downlink data packet according to the stored forwarding context to obtain the third downlink data, and then the access computing node sends the third downlink data to the terminal device through the air interface bearer 1 indicated by the computing power bearer identifier 1. Among them, the introduction of the forwarding context refers to the description in the above step S307 and will not be repeated here.

[0417] It should be noted that Nc can be based on the user plane part of the GPRS tunneling protocol (GTP-U) protocol, or it can be based on other transmission protocols to transmit remote direct memory access (RDMA), which is not limited in the embodiment of the present application.

[0418] S313: The terminal device sends a scheduling end indication of computing task 1 to the access computing node. Correspondingly, the access computing node receives the scheduling end indication of computing task 1 from the terminal device.

[0419] The scheduling end indication of computing task 1 is used to indicate the end of scheduling of computing task 1. The access computing node releases air interface bearer 1 according to the scheduling end indication.

[0420] When the access computing node provides computing resources for computing task 1, it releases the local air interface bearer and the resources required to execute computing task 1 according to the scheduling end indication. When the collaborative node executes computing task 1, the access computing node sends a request to the core network requesting the collaborative node to release the communication resources and the resources required to execute computing task 1. For example, the core network sends a resource release request to the collaborative node, requesting the collaborative node to release the resources related to the computing function call. For example, upon receiving the resource release request, the collaborative node deletes the stored relationship and releases the communication resources and the resources required for the computing task.

[0421] Exemplarily, the scheduling end request may be an air interface control signaling, such as access stratum (AS) signaling. More specifically, the scheduling end request may be an RRC layer signaling, or a MAC layer signaling.

[0422] In some implementations, the terminal device may also send an indication message 1 to the access computing node, and the indication message 1 is used to indicate the end of computing task 1. For example, the indication message 1 may include an end maker data packet, and the access computing node releases communication resources and computing task resources based on the data packet. The endmarker data packet is received from the air interface bearer 2 of the terminal device. When the next computing task of the same computing power service arrives, another computing node can be selected to serve another computing task, such as selecting collaborative node 2 to perform computing task 2. The collaborative node in the above steps may include collaborative node 1, and a new Nc tunnel will be formed between the access computing node and the collaborative node 2. The access computing node saves the new Nc interface address, such as the Nc 2 interface address, and the data related to computing task 2 is transmitted between the access computing node and the collaborative node through the Nc interface address 2.

[0423] In the communication method provided in the embodiment of the present application, by associating the first identifier with the first computing task, the first data of the first computing task can be determined according to the first identifier, and then the target instance of the first data can be selected, and then the data transmission between the terminal device and the first node can be realized through the first air interface bearer indicated by the first identifier. In this way, the first computing task can be tightly coupled with the first air interface bearer, and communication resources and computing resources can be fully and efficiently utilized, thereby realizing efficient transmission of computing task-based and user-side-based data.

[0424] Figure 8 is an exemplary flow chart of a communication method provided in an embodiment of the present application. In this embodiment of the present application, the scheduling of multiple computing tasks corresponds to a computing power carrying identifier. The computing power carrying identifier corresponding to the scheduling of different computing tasks is the same. Method 400 may include some or all of the following steps.

[0425] S401: The terminal device sends a scheduling request for computing task 1 to the core network. Correspondingly, the core network receives the invocation request for computing task 1 from the terminal device.

[0426] The scheduling request is used to request the scheduling of computing task 1, and the scheduling request carries the computing power service identifier of computing task 1. The computing power service identifier of computing task 1 facilitates the core network to identify the computing task requested by the terminal device. The specific form of the computing power service identifier of computing task 1 can be referred to the description in the above embodiment and will not be repeated here.

[0427] Exemplarily, the scheduling request may be non-access stratum (NAS) signaling.

[0428] Optionally, the scheduling request also carries the network identifier of computing task 1, which may be an identifier assigned by the network to computing task 1, and is used by the terminal device to carry the information element when encapsulating a data packet to indicate that the data packet is associated with computing task 1.

[0429] S402. The core network determines a general computing node that provides all computing resources for computing task 1.

[0430] Among them, the core network determines the general computing node that provides all computing resources for computing task 1 based on the above scheduling request.

[0431] It should be noted that when the call request for computing task 1 in step 1 above does not carry the network identifier of computing task 1, the core network can also allocate the network identifier of computing task 1. In the subsequent sending and receiving process of computing task 1 data, the data of computing task 1 needs to carry the network identifier of computing task 1.

[0432] Optionally, the core network may further allocate QoS parameters to the computing task 1, where the QoS parameters include a quality of service flow identifier (QoS flow identifier, QFI) and a QoS level corresponding to the QFI.

[0433] Based on the decision of the core network, the subsequent execution steps can be divided into the following two cases.

[0434] Case 1:

[0435] Determine that the cooperative node provides all computing resources for computing task 1. Specifically, steps S403a to S403f are included.

[0436] S403a: The core network sends request information 4 to the coordination node. Correspondingly, the coordination node receives the request information 4 from the core network.

[0437] Request message 4 is used to request the collaborative node to allocate resources to the terminal device for processing computing task 1, and request message 4 includes the computing service identifier of computing task 1. The resources for processing computing task 1 may include function as a service (FaaS). Optionally, request message 4 also carries the network identifier of computing task 1.

[0438] Optionally, the core network allocates an IP address for access by the computing task 1, and the access IP address may be an anycast address or a virtual IP address.

[0439] S403b: The coordination node sends response information 4 to the core network. Correspondingly, the core network receives the response information 4 from the coordination node.

[0440] The coordinating node allocates Nc UL address 1 to computing task 1 based on request information 4. Optionally, the coordinating node allocates a unicast IP address for access to computing task 1. This unicast IP address can be the unicast IP address of the coordinating node, a virtual IP address, or the unicast IP address of a function instance. The unicast IP address for access is described in steps S304b and S305a above and is not repeated here.

[0441] Furthermore, the collaboration node provides function instance 1 for computing task 1. After receiving request information 4, if the collaboration node does not have the function instance required by a computing task locally, the collaboration node first dynamically triggers the instantiation of computing function 1 corresponding to computing task 1 to obtain function instance 1, thereby activating the computing processing function of function instance 1 corresponding to computing task 1. The collaboration node dynamically triggering the instantiation of computing function 1 corresponding to computing task 1 to obtain function instance 1 may include at least one of the following:

[0442] Scheduling of computing power function 1 container resources;

[0443] Operation of computing power function 1 container resources;

[0444] Loading of computing power function 1;

[0445] The operation of computing power function 1.

[0446] The response message 4 carries the Nc UL address 1, and the coordination node notifies the core network of the Nc UL address through the response message 4. Optionally, the response message 4 also carries the unicast IP address or virtual IP address accessed by the computing task 1.

[0447] S403c: The core network sends a request message 5 to the access and communication node. Correspondingly, the access and communication node receives the request message 5 from the core network.

[0448] Request message 5 is used to request the access computing node to allocate Nc DL address 1 to computing task 1. Optionally, request message 5 also carries the computing service identifier of computing task 1 or the network identifier of computing task 1. Nc DL address 1 is associated with computing task 1.

[0449] S403d: The access computing node sends a response message 5 to the core network. Correspondingly, the core network receives the response message 5 from the access computing node.

[0450] The response information 5 carries the Nc DL address 1. Optionally, the response information 5 also includes at least one of the terminal device identifier, the computing service identifier of the computing task 1, and the port number. The port number can be used to distinguish different terminal devices or the computing service identifier of the computing task 1.

[0451] S403e: The core network sends the Nc DL address 1 to the coordination node. Correspondingly, the coordination node receives the Nc DL address 1 from the core network.

[0452] It should be noted that the above steps S403a to S403e can be replaced by the following steps S403a' to S403d', specifically:

[0453] S403a': The core network sends request information 4 to the coordination node. Correspondingly, the coordination node receives the request information 4 from the core network.

[0454] Optionally, the core network allocates an IP anycast address or a virtual IP address for access by the computing task 1.

[0455] S403b': The core network sends a request message 5 to the access and communication node. Correspondingly, the access and communication node receives the request message 5 from the core network.

[0456] S403c': The access communication node sends a response message 5 to the core network. Correspondingly, the core network receives the corresponding message 5 from the access communication node.

[0457] S403c', the access computing node sends a request message 5' to the collaboration node, where the request message 5' includes the NcDL address;

[0458] S403d′: The cooperative computing node allocates an NcUL address and sends a response message to the access computing node, where the response message includes the NcDL address.

[0459] It should be noted that the above steps S403a' to S403d' are not shown in FIG. 8 .

[0460] S403f. The collaboration node provides function instance 1 for computing task 1.

[0461] The specific implementation of step S403f is as described in step S306 above, which will not be described in detail here. Step S403f can also be performed after step S403a.

[0462] Furthermore, the collaboration node stores forwarding rule information of data associated with computing task 1. The access general computing node stores the relationship between the network identifier of computing task 1 and the Nc 1 interface address.

[0463] The forwarding rule and the information about the forwarding rule may refer to the above step S306 and will not be described in detail here.

[0464] Optionally, the access node can also store the relationship between the computing power bearer identifier 1, the network identifier of computing task 1, and the Nc 1 interface address. The core network stores the relationship between the computing power service identifier of computing task 1, the network identifier of computing task 1, and the unicast IP address accessed by computing task 1.

[0465] Case 2:

[0466] Determine the access intermediary computing node to provide all computing resources for computing task 1. Specifically, steps S404a to S404b may be included.

[0467] S404a: The core network sends a request message 6 to the access and communication node. Correspondingly, the access and communication node receives the request message 6 from the core network.

[0468] The request information 6 is used to request the access computing node to allocate resources for processing computing task 1 to the terminal device, and the request information 5 includes the computing service identifier of computing task 1. The resources for processing computing task 1 may include FaaS.

[0469] Furthermore, the access node allocates an access unicast IP address to computing task 1 according to request information 6. The access unicast IP address can be the unicast IP address of the access node, a virtual IP address, or the unicast IP address of function instance 1.

[0470] S404b: The access communication node sends a response message 6 to the core network. Correspondingly, the core network receives the response message 6 from the access communication node.

[0471] The response information 6 carries the unicast IP address or virtual IP address accessed by the computing task 1 .

[0472] Furthermore, the access general computing node provides function instance 1 for computing task 1. For a detailed introduction, please refer to the above step S303 and will not be repeated here.

[0473] The introduction of the accessed unicast IP address in S404a and S404b is referred to the above step S303 and will not be repeated here.

[0474] S405 . The access computing node allocates air interface bearer 1 and computing power bearer identifier 1 to function instance 1.

[0475] The detailed description of step S405 refers to the above step S307 and will not be repeated here.

[0476] S406: The access computing node sends a response message to the terminal device regarding the scheduling request for computing task 1. Correspondingly, the terminal device receives the response message regarding the scheduling request for computing task 1 from the access computing node.

[0477] The response information of the scheduling request carries the network identifier of computing task 1. Optionally, the response information of the scheduling request also carries computing power bearer identifier 1. For a detailed introduction to computing power bearer identifier 1, please refer to the above step S301 and will not be repeated here.

[0478] Exemplarily, the response information to the scheduling request is encapsulated in a NAS container. The core network sends the scheduling request response information to the access computing node via the NAS container. The access computing node then sends the scheduling request response information to the terminal device. The access computing node sends the scheduling request response information via AS signaling. The AS signaling includes the air interface bearer configuration corresponding to computing capacity bearer identifier 1, such as a DRB identifier. Optionally, the NAS container also includes QoS parameters assigned by the core network.

[0479] S407: The terminal device sends first uplink data to the access communication node. Correspondingly, the access communication node receives the first uplink data from the terminal device.

[0480] Exemplarily, the terminal device sends the first uplink data on air interface bearer 1 indicated by computing power bearer identifier 1. The terminal device can carry the network identifier in the header of the computing power routing layer. The computing power routing layer can be an enhancement layer to the SDAP layer. That is, the SDAP header carries the computing task network identifier. Optionally, the SDAP layer also includes QoS parameters.

[0481] S408: The access computing node forwards the first uplink data.

[0482] The access computing node determines whether to forward the first uplink data to the local function instance of the access computing node or to the local function instance of the collaboration node according to the stored forwarding context.

[0483] When the access computing node forwards the first uplink data to the local function instance, method 400 further includes steps S408a and S408b.

[0484] When the access communication node forwards the first uplink data to the cooperation node, the method 400 further includes steps S409a to S409d.

[0485] Among them, the detailed description of steps S408a and S408b, and steps S409a to S409d refers to the above steps S310a and S310b, and steps S311a to S311d, which will not be repeated here.

[0486] S410: The access communication node sends third downlink data to the terminal device. Correspondingly, the terminal device receives the third downlink data from the access communication node.

[0487] S411: The terminal device sends a scheduling end indication of computing task 1 to the access computing node. Correspondingly, the access computing node receives the scheduling end indication of computing task 1 from the terminal device.

[0488] The detailed description of steps S410 and S411 refers to the above steps S312 and S313, which will not be repeated here.

[0489] In one implementation, in method 400, when a collaborative node executes a computing task, multiple computing tasks can be associated with a single Nc tunnel. Steps S401 to S405 described above can also be replaced with steps S301 to S308 in method 300 described above, with the difference being that the access intermediary computing node or the collaborative node also assigns a network identifier for computing task 1. For example, the access intermediary computing node assigns a network identifier for computing task 1 via request information 1 and request information 2 in steps S304a and S304b, and then sends the network identifier to the access intermediary computing node via response information 2 and response information 1.

[0490] Furthermore, the response information of the call request of computing task 1 carries the network identifier of computing task 1, and the access computing node sends the network identifier of computing task 1 to the terminal device.

[0491] It should be noted that the Nc tunnel in this case is a node-level tunnel, and the endpoint addresses of Nc UL and Nc DL can be preconfigured. At this point, the coordinating node does not need to be assigned Nc UL address 1, and the access computing node does not need to be assigned Nc DL address 1. The access computing node and the coordinating node only need to exchange corresponding communication addresses. Alternatively, it can be understood that: if the core network has obtained the Nc addresses of the coordinating node and the access computing node, then request information 4 can carry the Nc address of the access computing node, and request information 5 can carry the Nc address of the coordinating node. At this point, the core network no longer sends Nc DL address 1 to the coordinating node, that is, step S403e is no longer executed.

[0492] It should also be noted that when the Nc tunnel is a node-level tunnel, the protocol header 1 in the second uplink data packet in step S409a also carries the terminal device identifier (for example, UE ID, or carries a UE session identifier, which is used to identify the UE session) and the network identifier of the computing task 1.

[0493] In the communication method provided in the embodiment of the present application, the access computing node can allocate an air interface bearer (such as DRB resources) for data transmission in the scheduling process of computing task 1 in response to the request of the terminal device. The air interface bearer can be associated with multiple computing tasks, so that the data in the scheduling process of multiple computing tasks are transmitted on the same air interface bearer, thereby improving the utilization rate of air interface resources.

[0494] Figure 9 is an exemplary flow chart of a communication method provided in an embodiment of the present application. The method 500 shown in Figure 13 can be executed by the current access computing node and the target access computing node. Among them, the current access computing node and the target access computing node may include the service access computing node 20 in Figure 2. In some implementations, method 500 may be executed before method 300 and method 400, or may be executed after method 300 and method 400. When method 500 is executed before method 300 and method 400, the target access computing node is the access computing node in method 300 and method 400; when method 500 is executed after method 300 and method 400, the current access computing node is the access computing node in method 300 and method 400. The method 500 may include some or all of the following steps.

[0495] S501: The currently connected computing node detects that a switching event occurs.

[0496] Exemplarily, when the access computing node of the terminal device needs to be switched from the current access computing node to the target access computing node, subsequent steps are executed.

[0497] Exemplarily, the conditions for triggering the handover include one or more of the following:

[0498] 1) The terminal device moves from the serving cell of the current access node to the serving cell of the target access node;

[0499] 2) Preventive switching, that is, the target access node can provide a better quality communication link;

[0500] 3) Rescue switching: For example, if the quality of the communication link of the current access computing node is lower than the threshold value, switching to the target access computing node is performed to improve communication quality. For another example, if the receiving level of the target access computing node is higher than the receiving level of the current access computing node by a certain value (for example, the certain value is the rescue level switching tolerance), switching to the target access computing node is performed to avoid frequent switching. For another example, if the timing advance (TA) of the current access computing node is greater than the threshold value, switching to the target access computing node is performed to control the coverage range of network equipment and reduce system interference.

[0501] It should be understood that the above conditions for triggering switching are only exemplary. In actual implementation, switching may also be performed when situations other than the above conditions occur.

[0502] S502: The current access computing node sends handover information to the target access computing node. Correspondingly, the target access computing node receives the handover information from the current access computing node.

[0503] Exemplarily, the switching information indicates that the terminal device has been served by a computing task currently accessed by the computing node, where the served computing task includes a computing task currently being executed by the currently accessed computing node and requested by the terminal device. The switching information may carry the computing power service identifier of computing task 1 and Nc UL address 1.

[0504] Optionally, the current access computing node sending the switching information to the target access computing node may include: the current access computing node sending the switching information to the core network, and then the core network sending the switching information to the target access computing node.

[0505] S503: The target access computing node sends a handover information response to the current access computing node. Correspondingly, the current access computing node receives the handover information response from the target access computing node.

[0506] Exemplarily, the switching information response is used to indicate that the target access computing node is ready to receive a computing task 1 request from the terminal device.

[0507] Optionally, the switching message response carries computing power bearer identifier 2 (ie, Uu ID#2), or the target access computing node reuses computing power bearer identifier 1 (ie, Uu ID#1).

[0508] Optionally, the target access computing node sends a handover information response to the current access computing node, which may include: the target access computing node sends a handover information response to the core network, and then the core network sends a handover information response to the current access computing node.

[0509] S504: The currently connected computing node sends a handover command to the terminal device. Correspondingly, the terminal device receives the handover command from the currently connected computing node.

[0510] Exemplarily, the switching command is used to instruct the terminal device to send subsequent computing task call requests to the target access computing node.

[0511] In some implementations, the switching command may include air interface bearer configuration, or DRB identifier 1 corresponding to computing task 1.

[0512] S505: The target access computing node sends a first message to the coordination node. Correspondingly, the coordination node receives the first message from the target access computing node.

[0513] Exemplarily, the first message carries the computing power service identifier of computing task 1 and Nc DL address 1.

[0514] S506. The target access computing node saves the relationship between the computing power service identifier, computing power bearer identifier (which can be Uu ID#1 or Uu ID#2) and Nc interface address 1 of computing task 1.

[0515] S507: The coordinating node updates the local Nc address.

[0516] S508: The terminal device sends first uplink data to the target access communication node. Correspondingly, the target access communication node receives the first uplink data from the terminal device.

[0517] In one implementation, the terminal device may carry the computing power bearer identifier 2 in the header of the computing power routing layer, wherein the computing power routing layer may be a service data adaptation protocol (SDAP) layer.

[0518] As another implementation, if the terminal device does not carry computing power bearer identifier 2 at the computing power routing layer, computing power bearer identifier 1 is used to identify air interface bearer 1, and the terminal device transmits data on air interface bearer 1 indicated by computing power bearer identifier 1. In other words, the first uplink data is transmitted on air interface bearer 1.

[0519] Furthermore, the target access computing node forwards the first uplink data, that is, the subsequent execution steps are the same as the above steps S310 to S313 or steps S407 to S411, which will not be repeated here.

[0520] It should be noted that in the above step S313 or step S411, the scheduling end indication of the computing task 1 can also carry the computing power bearer identifier 2. Furthermore, the resources of the air interface bearer 1 and the computing task 1 are released. Among them, the resources of the air interface bearer 1 and the computing task 1 can be released by the current access computing node or the target access computing node. After the access computing node releases the air interface bearer, UuID#1 or UuID#2 or the air interface bearer identified by them can no longer be used. In the scenario where the collaborative node participates, the collaborative node can release the communication resources and the resources of the computing task 1.

[0521] It should be noted that in the communication methods of Figures 7 to 10 above, the terminal device initiates a single computing task call. In actual implementation, the terminal device can also initiate multiple computing task calls. Specifically, the terminal device sends an end marker to the access computing node. After receiving the end marker, the access computing node selects another computing node to schedule one of the remaining computing tasks in the multiple computing tasks based on the real-time computing power resources. For example, the first access computing node schedules computing task 1, the second access computing node schedules computing task 2, or the first collaborative node schedules computing task 2. Since another computing task, such as computing task 2, is scheduled at this time, a new Nc path is generated, that is, a new Nc tunnel. The Nc tunnel corresponds to a new computing task, and the access computing node saves the relationship between the new Nc tunnel and the new computing task. If the function instance serving the scheduling of this computing task changes, for example, it becomes a different function instance on the same computing node, or the computing node where it is located becomes another computing node, then the access computing node triggers the release of the original computing task resources.

[0522] The end tag is used to identify the invocation of multiple computing tasks initiated by a terminal device. This end tag belongs to the computing power routing layer and causes the data packet to terminate at the common computing node and not be forwarded to the original function instance. In one implementation, the end tag includes the computing power bearer identifier; in another implementation, the end tag includes the network identifier of the computing task.

[0523] In an embodiment of the present application, when the access computing node needs to be replaced due to reasons such as a change in the location of the terminal device, the target access computing node can transmit data on the tunnel indicated by the Nc UL identifier based on the computing power service identifier and Nc UL address of the computing task carried in the switching message, or transmit data through a new tunnel path to ensure that the data is transmitted through the path corresponding to the computing task.

[0524] Figure 10 is an exemplary flow chart of a communication method provided by an embodiment of the present application. The method 600 shown in Figure 10 can be performed by a terminal device and a first node. The terminal device may include the terminal device in any of the methods 300 to 500 or a component (such as a chip or module) in the terminal device, and the first node may include the access computing node in any of the methods 300 to 500 or a component (such as a chip or module) in the access computing node. In some scenarios, method 600 also requires the participation of a collaborative node (such as a second node), a core network, and a target function instance. The collaborative node may include the collaborative node in any of the methods 300 to 500 or a component (such as a chip or module) in the collaborative node, and the target instance may include the function instance in any of the methods 300 to 500 or a component (such as a chip or module) in the function instance. The method may include S610 to S630, specifically:

[0525] S610: The first node determines a first identifier.

[0526] The first identifier is associated with the first computing task, and the first identifier is used to indicate a first air interface bearer, which is used to transmit data associated with the first computing task.

[0527] Illustratively, the data associated with the first computing task may include the first uplink data in the above embodiment; the first computing task may include computing task 1 in the above embodiment; the first identifier may include computing power bearer identifier 1 in the above embodiment; and the first air interface bearer may include the above air interface bearer 1. The description of computing power bearer identifier 1 refers to step S307 and is not repeated here.

[0528] Optionally, the first identifier is also associated with at least one set of computing power QoS parameters, wherein the set of computing power QoS parameters is the QoS parameters associated with the above-mentioned first computing task, and each set of computing power QoS parameters includes transmission QoS parameters and / or computing QoS parameters.

[0529] The first node may determine the first identifier in one of the following ways:

[0530] Method 1 includes:

[0531] S611a: The terminal device sends a first request message to the first node. Correspondingly, the first node receives the first request message from the terminal device.

[0532] The first request information includes an identifier of the first computing task, and the first request information is used to request scheduling of the first computing task.

[0533] S611b: The first node determines a first identifier according to the first request information.

[0534] Illustratively, the first node determines the first computing task corresponding to the identifier of the first computing task included in the first request information, and further determines the first identifier.

[0535] Among them, the first computing task can take computing task 1 in the above embodiment as an example, and the identifier of the first computing task can include the computing power service identifier of computing task 1 in the above embodiment (such as the anycast address, unicast address, globally unique identifier, URL identifier, FQDN, etc. of computing task 1).

[0536] Method 2 includes:

[0537] S612a: The core network sends second request information to the second node. Correspondingly, the second node receives the second request information from the core network.

[0538] The second request information includes an identifier of the first computing task.

[0539] S612b: The second node determines the first identifier according to the second request information.

[0540] Exemplarily, the first node determines the first computing task corresponding to the identifier of the first computing task included in the second request information, and further determines the first identifier.

[0541] Method 3 includes:

[0542] S613a: The terminal device sends a first data packet to the first node, where the first data packet carries the second data and an identifier of the first computing task. Correspondingly, the first node receives the first data packet from the terminal device.

[0543] Illustratively, the first node receives the first data packet via a second air interface bearer, the identifier of the first computing task indicates that the second data packet is data associated with the first computing task, and the second air interface bearer and the first air interface bearer may be the same bearer or different bearers. The second air interface bearer may be air interface bearer 2 in the above embodiment.

[0544] S613b: The second node determines the first identifier according to the identifier of the first computing task.

[0545] Exemplarily, the first node determines the first computing task corresponding to the identifier of the first computing task based on the identifier of the first computing task, and then determines the first identifier. Further, the method 600 further includes step S614.

[0546] S614: The first node sends a first identifier to the terminal device. Correspondingly, the terminal device receives the first identifier from the first node.

[0547] Optionally, after executing steps S613a and S613b, the first node may send the second data to the target instance.

[0548] As an example, the first node sends the second data to the target instance according to the identifier of the first computing task. At this time, the target instance is associated with the first node. That is, at this time, the first node determines to send the second data to the locally associated target instance; or, in other words, at this time, the first node provides resources for the first computing task.

[0549] As another example, the first node sends the second data to the second node based on the relationship between the identifier of the first computing task and the second identifier; or the first node sends the second data to the second node based on the relationship between the identifier of the first computing task, the second identifier, and the identifier of the terminal device. In this case, the target instance is associated with the second node, that is, the first node determines to send the second data to the second node; or in other words, the second node provides resources for the first computing task.

[0550] It should be noted that the above-mentioned second identifier includes a first address and a second address, the first address is the address of a node on the first transmission path, the second address is the address of another node on the first transmission path, the first transmission path is used to transmit third data, and the third data is determined based on the second data.

[0551] Exemplarily, the second identifier may include the Nc 1 interface address in the above embodiment, the first address may include the Nc UL address 1 in the above embodiment, and the second address may include the Nc DL address 1 in the above embodiment.

[0552] S620: The terminal device sends first data to the first node. Correspondingly, the first node receives the first data from the terminal device.

[0553] The first node receives first data from the terminal device through the first air interface bearer indicated by the first identifier, and the first data is data associated with the first computing task.

[0554] Illustratively, the first data may be the first uplink data in the above embodiment.

[0555] S630: The first node sends first data to the target instance.

[0556] The target instance is used to process data associated with the first computing task, and the data associated with the first computing task may include first data.

[0557] Exemplarily, when a first node sends first data to a target instance, it determines whether to send the first data to the target instance associated with the first node or to the second node based on the stored forwarding context. Specific implementations include the following two methods:

[0558] In one implementation, the first node storage and forwarding context may include: a first identifier; or the first identifier and an identifier of a first computing task; or the first identifier and an identifier of a first QoS flow. The identifier of the first QoS flow is the identifier of the QoS flow associated with the first computing task.

[0559] Furthermore, the first node sends the first data to the target instance, including: the first node sends the first data to the target instance based on the first identifier; or, sends the first data to the target embodiment based on the first identifier and the identifier of the first computing task, and the target instance is associated with the first node; or, sends the first data to the target embodiment based on the first identifier and the identifier of the first QoS flow, and the target instance is associated with the first node.

[0560] Exemplarily, the identifier of the first QoS flow includes the identifier 1 of the QoS flow in the above embodiment.

[0561] In another implementation, the forwarding context stored by the first node includes: a relationship between a first identifier and a second identifier; or a relationship between the first identifier, an identifier of a first computing task, and the second identifier; or the first identifier, an identifier of a first quality of service (QoS) flow, and the second identifier. The second identifier includes a first address and a second address, the first address being the address of a node on a first transmission path, the second address being the address of another node on the first transmission path, the first transmission path being used to transmit fourth data, the fourth data being determined based on the first data.

[0562] Furthermore, the first node sends the first data to the target instance, including: sending the first data to the second node based on the relationship between the first identifier and the second identifier, and the target instance is associated with the second node; or, sending the first data to the second node based on the relationship between the first identifier, the identifier of the first computing task, and the second identifier, and the target instance is associated with the second node; or, sending the first data to the second node based on the relationship between the first identifier, the identifier of the first quality of service QoS flow, and the second identifier, and the target instance is associated with the second node.

[0563] Optionally, the first node sends fifth data to the terminal device over the first air interface bearer, wherein the fifth data comes from the target instance. Specifically, the fifth data comes from the target instance local to the first node, or the fifth data comes from a second node associated with the target instance.

[0564] Exemplarily, the forwarding context stored by the first node may refer to the description in step S307 , and the specific implementation method of the first node sending the first data to the target instance may also refer to the above-mentioned step S310 , which will not be repeated here.

[0565] Furthermore, the first node sending the first data to the target instance may be one of Case 1 and Case 2. Specifically:

[0566] Case 1: The first node sends first data to the target instance, specifically including:

[0567] S631a: The first node sends first data to the target instance. Correspondingly, the target instance receives the first data from the first node.

[0568] S631b: The first node receives sixth data from the target instance.

[0569] The sixth data may include the first downlink data in the above embodiment. In this case, the fifth data is determined based on the sixth data.

[0570] It should be noted that S631a and S631b are steps performed in the embodiment of the present application when the target instance is associated with the first node.

[0571] Case 2: The first node sends first data to the second node, specifically including:

[0572] It should be noted that after receiving the first data, the second node forwards the relevant data according to the forwarding rule information stored in the second node. The specific description of the forwarding rule information can be found in the above step S306 and will not be repeated here.

[0573] S632a: The first node sends a second data packet to the second node. Correspondingly, the second node receives the second data packet from the first node.

[0574] The second data packet includes a first protocol header and a first payload, the destination address of the first protocol header is the above-mentioned first address, the source address of the first protocol header is the above-mentioned second address, and the first payload is determined according to the first data.

[0575] Exemplarily, the first protocol header may be protocol header 1 in the above embodiment, the first payload may be payload 1 determined according to the first uplink data in the above embodiment; the second data packet may be the data packet after Nc encapsulation of the first uplink data in the above embodiment.

[0576] Furthermore, the second node sends the data of the second data packet after removing the protocol header 1 to the target instance, which is associated with the second node and processes the data sent by the second node after removing the protocol header 1, wherein the data after removing the protocol header 1 can be the third uplink data in the above embodiment.

[0577] S632b: The target instance sends the seventh data to the second node. Correspondingly, the second node receives the seventh data from the target instance.

[0578] The seventh data may include the second downlink data in the above embodiment.

[0579] S632c: The second node sends a third data packet to the first node. Correspondingly, the first node receives the third data packet from the second node.

[0580] The third data packet includes a second protocol header and a second payload, the destination address of the second protocol header is the second address, the source address of the second protocol header is the first address, and the second payload includes seventh data. In this case, the fifth data is determined based on the seventh data.

[0581] Exemplarily, the second protocol header may be protocol header 2 in the above embodiment, and the second payload may be payload 2 in the above embodiment; the third data packet may be the data packet after Nc encapsulation of the second downlink data in the above embodiment, that is, it may be the first downlink data packet in the above embodiment.

[0582] It should be noted that S632a to S631c are steps performed in an embodiment of the present application when the target instance is associated with the second node.

[0583] Optionally, the first protocol header and the second protocol header in S632a and S632c further include at least one of the following:

[0584] The identifier of the first computing task; the identifier of the terminal device. The description of protocol header 1 and protocol header 2 is as described in steps S311a and S311d above, which will not be repeated here.

[0585] Optionally, before the above step S632a, the method further includes step S632a' and step S632a". Specifically:

[0586] S632a': The first node sends the third request information to the second node. Correspondingly, the second node receives the third request information from the first node.

[0587] The third request information is used to request the second node to allocate the first address to the first computing task.

[0588] Optionally, the third request information carries the identifier of the first computing task; or the third request information carries the second address.

[0589] Exemplarily, the third request information includes request information 1 and request information 2 in steps S304a and S304b, and may also include request information 3 in step S305a. The third request information may be sent directly by the first node to the second node, or may be forwarded to the second node via the core network.

[0590] S632a”: The first node sends first response information to the second node. Correspondingly, the second node receives the first response information from the first node.

[0591] The first response message indicates the aforementioned first address. This means that after the second node assigns the first address to the first computing task based on the third request information, the second node indicates the first address to the first node via the first response message. At this point, the first node encapsulates the data based on the first and second addresses. For example, the first response message may include response information 2 and response information 1 in steps S304c and S304d, or response information 3 in step S305b.

[0592] For example, the implementation steps in the above-mentioned Case 1 and Case 2 may also refer to the descriptions in S310a to S310b and S311a to S311d, which will not be repeated here.

[0593] Optionally, the identifier of the first computing task includes a unicast address. Specifically, the first node allocates a unicast address to the first computing task according to the above-mentioned first request information; or requests the unicast address from the second node according to the first request information, and the first node receives the unicast address from the second node. Specifically, when it is determined that the second node provides computing resources (for example, a target instance) for the first computing task, the first node sends a request message to the second node to request the second node to allocate a unicast address for the first computing task; and receives the unicast address from the second node. Alternatively, the first node requests the second node to allocate the unicast address via the core network, and after the second node allocates the unicast address, it sends it to the first node, that is, the first node receives the unicast address from the second node. Further, the first node sends information about the unicast address to the terminal device.

[0594] Exemplarily, the unicast address includes the unicast IP address accessed by computing task 1 in the above embodiment. For the description of allocating the unicast IP address accessed by computing task 1, refer to the above steps S304b to S305b and will not be repeated here.

[0595] Optionally, the first node may receive first indication information on the first air interface bearer, where the first indication information is used to indicate the end of the first computing task. Exemplarily, the first indication information may be the end maker data packet in the above embodiment, which instructs the first node or the second node to end execution of the first computing task according to the end maker data packet. The first indication information also includes an identifier of the first computing task. For a description of the end maker data packet, please refer to step S313 and will not be repeated here.

[0596] In some implementations, the method further includes: the terminal device sending a fourth request message to the first node, the fourth request message being used to indicate the end of scheduling of the first computing task. Accordingly, the first node receives the fourth request message from the terminal device. Exemplarily, the fourth request message may include the scheduling end indication for computing task 1 in steps S313 and S411 above.

[0597] Optionally, the first node releases the first air interface bearer resources and the resources for executing the first computing task based on the fourth request information. Specifically, when the first node executes the first computing task, the first node locally releases the first air interface bearer resources and the resources for executing the first computing task; when the second node executes the first computing task, the first node sends a first message to the second node via the core network, where the first message is used to instruct the second node to release the first air interface bearer resources and the resources for executing the first computing task.

[0598] Optionally, the method further includes: the third node sending a fifth request message to the first node. Accordingly, the first node receives the fifth request message from the third node. The fifth request message is used to instruct the first computing task to be switched from the third node to the first node. Exemplarily, the fifth request message includes the switching message in step S502 above.

[0599] In some implementations, prior to executing S610 to S630, the terminal device may reside in the service cell of the third node, i.e., the third node provides support for the terminal device's computing tasks with air interface bearer resources and computing resources. Subsequently, due to the occurrence of a handover event, the first node provides support for the terminal device with air interface bearer resources and computing resources. The method further includes: the third node sends a fifth request message to the first node. Accordingly, the first node receives the fifth request message from the third node. The fifth request message is used to instruct the first computing task to be handed over from the third node to the first node.

[0600] In some implementations, before executing S610 to S630, the method further includes:

[0601] S610': The terminal device sends sixth request information to the core network. Correspondingly, the core network receives the sixth request information from the terminal device.

[0602] The sixth request information is used to request scheduling of the first computing task, and the sixth request information includes an identifier of the first computing task.

[0603] Exemplarily, the sixth request information includes the scheduling request for computing task 1 in step S401 above.

[0604] S620': Select a target instance.

[0605] The target instance is used to process data associated with the first computing task, and the target instance is associated with the first node or the second node.

[0606] Optionally, when the target instance is associated with the first node, the method further includes: sending a seventh request message to the first node, the seventh request message being used to request allocation of resources for processing the first computing task to the terminal device, and the seventh request message including an identifier of the first computing task. Exemplarily, the seventh request message includes request message 6 in step S404a above.

[0607] Furthermore, the core network receives the first address from the first node. That is, according to the seventh request information, the first node allocates the first address to the first computing task 1.

[0608] Specifically, the seventh request information is used to request allocation of resources for processing the first computing task to the terminal device, including: the seventh request information is used to request the first node to allocate the above-mentioned first air interface bearer and target instance.

[0609] Optionally, when the target instance is associated with the second node, the method further includes: the core network sending an eighth request message to the second node, the eighth request message being used to request allocation of resources for processing the first computing task to the terminal device, and the eighth request message including an identifier of the first computing task. Exemplarily, the eighth request message includes request message 4 in step S403a above.

[0610] Furthermore, the core network receives the second address from the second node. That is, according to the seventh request information, the second node allocates the second address to the first computing task 1.

[0611] In some implementations, the core network determines a third identifier based on the sixth request information, where the third identifier is used to indicate data associated with the first computing task; illustratively, the third identifier can be the network identifier of computing task 1 in step S401 or S403a above.

[0612] Furthermore, the second node sends the third identifier to the terminal device.

[0613] It should be noted that the identifier of the first computing task may include a unicast address, and the core network may receive the unicast address from the first node or the second node and send the unicast address to the terminal device. For a detailed description of the unicast address, please refer to the above step S404b.

[0614] Based on the above scheme, a first identifier can be assigned to a specific computing task, thereby allocating the air interface bearer required for transmitting data for the current scheduling of the computing task. By associating the first identifier with the first computing task, the first data of the first computing task can be determined according to the first identifier, and then the target instance of the first data can be selected, and then the data transmission between the terminal device and the first node can be realized through the first air interface bearer indicated by the first identifier. In this way, the first computing task can be tightly coupled with the first air interface bearer, and communication resources and computing resources can be fully and efficiently utilized, thereby realizing efficient transmission of computing task-based and user-plane-based data.

[0615] The above, in combination with Figures 7 to 10, illustrates the communication method provided in the embodiments of the present application. In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0616] The communication device provided in the embodiment of the present application is described in detail below with reference to Figures 11 to 13. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so that the contents not described in detail can be referred to the method embodiment above, and for the sake of brevity, they are not repeated here.

[0617] Figure 11 is a schematic block diagram of a communication device 2000 provided in an embodiment of the present application. Communication device 2000 can be an access computing node, terminal device, core network, or collaborative node, or a component (such as a chip or module) in an access computing node, terminal device, core network, or collaborative node, used to implement the methods involved in the embodiments shown in Figures 7 to 10. For details, please refer to the relevant descriptions in the above method embodiments. Among them, the chip can be, for example, a system on chip (SoC).

[0618] As shown in Figure 11, the device 2000 may include a transceiver unit 2010 and a processing unit 2020. The transceiver unit 2010 can communicate with the outside world, and the processing unit 2020 is used to process data. The transceiver unit 2010 can also be called a communication interface or a transceiver unit. The processing unit 2020 can be used to perform processing.

[0619] It should be noted that the communication device 2000 may include a sending unit but not a receiving unit. Alternatively, the communication device 2000 may include a receiving unit but not a sending unit. The specific implementation depends on whether the above solution executed by the communication device 2000 includes a sending action and a receiving action.

[0620] Optionally, the device 2000 may further include a storage unit, which may be used to store instructions and / or data. The processing unit 2020 may read the instructions and / or data in the storage unit so that the device implements the aforementioned method embodiment.

[0621] Exemplarily, the communication device 2000 can be an access computing node (or called a first node), or it can be a communication device applied to an access computing node or used in combination with an access computing node and capable of implementing the method executed by the access computing node, such as a chip, a chip system or a circuit. For details, please refer to the relevant description of the chip system shown in the figure below.

[0622] Exemplarily, the communication device 2000 can be a terminal device, or a communication device applied to a terminal device or used in combination with a terminal device and capable of implementing a method executed by the terminal device, such as a chip, a chip system or a circuit. For details, please refer to the relevant description of the chip system shown in the figure below.

[0623] Exemplarily, the communication device 2000 can be a core network, or a communication device applied to the core network or used in conjunction with the core network and capable of implementing the method executed by the core network, such as a chip, a chip system or a circuit. For details, please refer to the relevant description of the chip system shown in the figure below.

[0624] Exemplarily, the communication device 2000 can be a collaborative node (or called a second node), or it can be a communication device applied to a collaborative node or used in combination with a collaborative node and capable of implementing the method executed by the collaborative node, such as a chip, a chip system or a circuit. For details, please refer to the relevant description of the chip system shown in the figure below.

[0625] In one possible design, the device 2000 can implement steps or processes corresponding to those executed by the first node in the above method embodiment, wherein the transceiver unit 2010 is used to perform transceiver-related operations of the first node in the above method embodiment, and the processing unit 2020 is used to perform processing-related operations of the first node in the above method embodiment.

[0626] As an example, the transceiver unit 2010 is used to receive first data from a terminal device through a first air interface bearer indicated by a first identifier, and the first data is data associated with the first computing task; the transceiver unit 2010 is also used to send the first data to a target instance, and the target instance is used to process the data associated with the first computing task; the processing unit 2020 is used to determine the first identifier, and the first identifier is associated with the first computing task.

[0627] In another possible design, the device 2000 can implement steps or processes corresponding to those executed by the terminal device in the above method embodiment, wherein the transceiver unit 2010 is used to execute the transceiver-related operations of the terminal device in the above method embodiment, and the processing unit 2020 is used to execute the processing-related operations of the terminal device in the above method embodiment.

[0628] As an example, the transceiver unit 2010 is used to receive a first identifier from a first node, where the first identifier is used to indicate a first air interface bearer, and the first identifier is associated with a first computing task; the transceiver unit 2010 is also used to send first data to the first node via the first air interface bearer, where the first data is data associated with the first computing task.

[0629] In another possible design, the device 2000 can implement steps or processes corresponding to those performed by the core network in the above method embodiments, wherein the transceiver unit 2010 is used to perform operations related to transceiver transmission of the core network in the above method embodiments, and the processing unit 2020 is used to perform operations related to processing of the core network in the above method embodiments.

[0630] As an example, the transceiver unit 2010 is used to receive a sixth request information from a terminal device, where the sixth request information is used to request scheduling of a first computing task, and the sixth request information includes an identifier of the first computing task; the processing unit 2020 is used to select a target instance, where the target instance is used to process data associated with the first computing task, and the target instance is associated with the first node or the second node.

[0631] In another possible design, the device 2000 can implement steps or processes corresponding to those executed by the second node in the above method embodiment, wherein the transceiver unit 2010 is used to perform transceiver-related operations of the second node in the above method embodiment, and the processing unit 2020 is used to perform processing-related operations of the second node in the above method embodiment.

[0632] As an example, the transceiver unit 2010 is configured to receive third request information from the first node, where the third request information is used to request the second node to allocate a first address to the first computing task, where the first address corresponds to the first computing task;

[0633] Processing unit 2020 is configured to allocate a target instance to the first computing task based on the third request information. The target instance is configured to process data associated with the first computing task, and the target instance is associated with the second node. It should be understood that the specific process of each unit executing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiment and will not be repeated here for the sake of brevity.

[0634] It should also be understood that the above-mentioned device 2000 is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 2000 can be specifically the communication device in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the communication device in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

[0635] The device 2000 of the above-mentioned solution has the function of implementing the corresponding steps performed by the communication device (such as an access node, terminal equipment, core network or collaborative node) in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0636] In addition, the above-mentioned transceiver unit may also be a transceiver circuit (for example, may include a transmitting circuit, or may also include a receiving circuit), and the processing unit may be a processing circuit.

[0637] FIG12 is a schematic diagram of another communication device 2100 provided in an embodiment of the present application. The device 2100 includes a processor 2110, which is coupled to a memory 2120. The memory 2120 is configured to store computer programs or instructions and / or data. The processor 2110 is configured to execute the computer programs or instructions stored in the memory 2120, or read data stored in the memory 2120, to perform the methods described in the above method embodiments.

[0638] Optionally, there are one or more processors 2110 .

[0639] Optionally, the memory 2120 is one or more.

[0640] Optionally, the memory 2120 may also be referred to as a storage medium or a storage device. The memory 2120 may be integrated with the processor 2110 or may be separately provided.

[0641] Optionally, as shown in Figure 12, the apparatus 2100 further includes a transceiver 2130, which is configured to receive and / or transmit signals. For example, the processor 2110 is configured to control the transceiver 2130 to receive and / or transmit signals.

[0642] As an example, the processor 2110 may have the processing unit 2020 shown in FIG. 12 , the memory 2120 may have the function of a storage unit, and the transceiver 2130 may have the transceiver unit (or acquisition unit 2010 ) shown in FIG. 12 .

[0643] As a solution, the device 2100 is used to implement the operations performed by the communication device (such as an access node, terminal equipment, core network or collaborative node) in the above various method embodiments.

[0644] For example, the processor 2110 is configured to execute computer programs or instructions stored in the memory 2120 to implement relevant operations of the communication device in the above various method embodiments.

[0645] In some implementations, when apparatus 2100 is a terminal device, transceiver 2130 may include a transmitter, a receiver, a radio frequency circuit, an antenna, and input / output devices. Processor 2110 is primarily used to process communication protocols and communication data, control the terminal device, execute software programs, and process software program data. Memory 2120 is primarily used to store software programs and data. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals.

[0646] Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves.

[0647] Input and output devices (eg, touch screen, display screen, keyboard, etc.) are mainly used to receive data input by the user and output data to the user.

[0648] It should be noted that some types of terminal devices may not have input and output devices.

[0649] When data needs to be sent, the processor performs baseband processing on the data to be transmitted and outputs the baseband signal to the RF circuit. The RF circuit then performs RF processing on the baseband signal and transmits it via the antenna in the form of electromagnetic waves. When data is sent to a terminal device, the RF circuit receives the RF signal via the antenna, converts it into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes it.

[0650] In other implementations, when the apparatus 2100 is a network device (such as a first node (or access node), a core network, or a second node (or collaborative node)), the processor 2110 is mainly used for baseband processing, controlling the network device, etc.; the processor 2110 is usually the control center of the network device, used to control the network device to perform the processing operations on the network device side in the above method embodiment, such as determining the computing resources required for the computing task, determining the node that provides computing resources for the computing task, etc. The memory 2120 is mainly used to store computer program code and data. The transceiver 2130 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals; the transceiver 2130 may include an antenna and a radio frequency circuit (not shown in the figure), wherein the radio frequency circuit is mainly used for radio frequency processing.

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

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

[0653] In some implementations, the processor 2110 may also be referred to as a processing unit, a processing board, a processing module, a processing device, etc. The transceiver 2130 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc.

[0654] When the device 2100 is a chip, the chip includes a processor, memory, and a transceiver. The transceiver can be an input / output circuit or a communication interface; the processor can be a processing module, microprocessor, or integrated circuit integrated on the chip. The sending operation of the terminal device in the above method embodiment can be understood as the chip's output, and the receiving operation of the terminal device in the above method embodiment can be understood as the chip's input.

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

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

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

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

[0659] 13 is a schematic diagram of a chip system 2200 provided in an embodiment of the present application. The chip system 2200 (or also referred to as a processing system) includes a logic circuit 2210 and an input / output interface 2220 .

[0660] Logic circuit 2210 may be a processing circuit within chip system 2200. Logic circuit 2210 may be coupled to a storage unit and invoke instructions within the storage unit, enabling chip system 2200 to implement the methods and functions of various embodiments of the present application. Input / output interface 2220 may be an input / output circuit within chip system 2200, outputting information processed by chip system 2200 or inputting data or signaling information to be processed into chip system 2200 for processing.

[0661] As a solution, the chip system 2200 is used to implement the operations performed by the communication device (such as access node, terminal equipment, core network or collaboration node) in the above various method embodiments.

[0662] For example, the logic circuit 2210 is used to implement the processing-related operations performed by the communication device (such as an access computing node, terminal equipment, core network or collaborative node) in the above method embodiments; the input / output interface 2220 is used to implement the sending and / or receiving-related operations performed by the communication device (such as an access computing node, terminal equipment, core network or collaborative node) in the above method embodiments.

[0663] The present application also provides a processor for coupling with a memory, and for executing the methods and functions involving access to a common computing node, a terminal device, a core network or a collaborative node in any of the above embodiments.

[0664] In another embodiment of the present application, a computer program product including a computer program or instructions is provided. When the computer program product is run on a computer, the method of the aforementioned embodiment is implemented.

[0665] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by a communication device (such as an access node, terminal equipment, core network or collaborative node) in the above-mentioned method embodiments.

[0666] For example, when the computer program is executed by a computer, the computer can implement the methods performed by a communication device (such as an access node, terminal equipment, core network or collaborative node) in each embodiment of the above method.

[0667] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by a communication device (such as an access node, terminal equipment, core network or collaborative node) in the above-mentioned method embodiments.

[0668] An embodiment of the present application also provides a communication system, which includes the access communication node (or called the first node), terminal equipment, core network or collaborative node (or called the second node) in the above embodiment for executing the method in any one of the embodiments shown in Figures 7 to 10.

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

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

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

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

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

[0674] 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 a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

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

Claims

1. A communication method, characterized in that: include: Determining a first identifier, where the first identifier is associated with a first computing task; receiving first data from a terminal device through a first air interface bearer indicated by the first identifier, where the first data is data associated with the first computing task; The first data is sent to a target instance, where the target instance is used to process the data associated with the first computing task.

2. The method according to claim 1, characterized in that The determining of the first identifier includes: receiving first request information from the terminal device, where the first request information includes an identifier of the first computing task, and the first request information is used to request scheduling of the first computing task; The first identifier is determined according to the first request information.

3. The method according to claim 1, characterized in that The determining of the first identifier includes: receiving a second request message from a core network, where the second request message includes an identifier of the first computing task; The first identifier is determined according to the second request information.

4. The method according to claim 1, wherein The determining of the first identifier includes: receiving a first data packet through a second air interface bearer, where the first data packet carries second data and an identifier of the first computing task, where the identifier of the first computing task indicates that the second data is data associated with the first computing task; The first identifier is determined according to the identifier of the first computing task.

5. The method according to claim 4, characterized in that The method further comprises: The second data is sent to the target instance according to the identifier of the first computing task, where the target instance is associated with the first node.

6. The method according to claim 4, characterized in that The method further comprises: sending the second data to the second node according to the relationship between the identifier of the first computing task and the second identifier, and associating the target instance with the second node; or Sending the second data to a second node according to a relationship between the identifier of the first computing task, the second identifier, and the identifier of the terminal device, and associating the target instance with the second node; The second identifier includes a first address and a second address, the first address is the address of a node on the first transmission path, the second address is the address of another node on the first transmission path, the first transmission path is used to transmit third data, and the third data is determined based on the second data.

7. The method according to any one of claims 1 to 6, characterized in that The method further includes: sending the first identifier to the terminal device.

8. The method according to any one of claims 1 to 4, characterized in that The sending the first data to the target instance includes: sending the first data to the target instance according to the first identifier, the target instance being associated with the first node; or sending the first data to the target instance according to the first identifier and the identifier of the first computing task, wherein the target instance is associated with the first node; or According to the first identifier and the identifier of the first quality of service QoS flow, the first data is sent to the target embodiment, and the target instance is associated with the first node, wherein the identifier of the first QoS flow is the identifier of the QoS flow associated with the first computing task.

9. The method according to any one of claims 1 to 4, characterized in that The sending the first data to the target instance includes: sending the first data to a second node based on a relationship between the first identifier and the second identifier, and associating the target instance with the second node, wherein the second identifier includes a first address and a second address, the first address is an address of a node on a first transmission path, and the second address is an address of another node on the first transmission path, the first transmission path is used to transmit fourth data, and the fourth data is determined based on the first data; or Sending the first data to a second node according to the relationship between the first identifier, the identifier of the first computing task, and the second identifier, and associating the target instance with the second node; or Based on the relationship between the first identifier, the identifier of the first quality of service QoS flow, and the second identifier, the first data is sent to the second node, and the target instance is associated with the second node, wherein the identifier of the first QoS flow is the identifier of the QoS flow associated with the first computing task.

10. The method according to claim 9, characterized in that The sending the first data to the second node includes: A second data packet is sent to the second node, where the second data packet includes a first protocol header and a first payload, the destination address of the first protocol header is the first address, the source address of the first protocol header is the second address, and the first payload is determined based on the first data.

11. The method according to any one of claims 8 to 10, characterized in that The method further includes: sending fifth data to the terminal device over the first air interface bearer, where the fifth data comes from the target instance.

12. The method according to claim 11, characterized in that The sending fifth data to the terminal device over the first air interface bearer includes: receiving sixth data from the target instance, the target instance being associated with the first node, the fifth data being determined based on the sixth data; or, A third data packet is received from the second node, the third data packet including a second protocol header and a second payload, the destination address of the second protocol header being the second address, the source address of the second protocol header being the first address, the second payload including seventh data, the seventh data being determined based on data sent by the target instance, the target instance being associated with the second node, and the fifth data being determined based on the seventh data.

13. The method according to claim 10 or 12, characterized in that The first protocol header or the second protocol header further includes at least one of the following: an identifier of the first computing task; The identifier of the terminal device.

14. The method according to any one of claims 9 to 13, characterized in that The method further comprises: A third request message is sent to the second node, and a first response message is received from the second node, wherein the third request message is used to request the second node to allocate the first address to the first computing task, and the first response message is used to indicate the first address.

15. The method according to any one of claims 2 to 14, characterized in that The identifier of the first computing task includes a unicast address, and the method further includes: Allocating the unicast address to the first computing task according to the first request information, or requesting the unicast address from a second node according to the first request information, and receiving the unicast address from the second node; Send the unicast address information to the terminal device.

16. The method according to any one of claims 1 to 15, characterized in that The method further includes: receiving first indication information on the first air interface bearer, where the first indication information is used to indicate that the first computing task is finished.

17. The method according to claim 16, characterized in that The first indication information also includes an identifier of the first computing task.

18. The method according to any one of claims 1 to 15, characterized in that The method further comprises: Fourth request information is received, where the fourth request information is used to indicate the end of scheduling of the first computing task.

19. The method according to any one of claims 1 to 18, characterized in that The first identifier is also associated with at least one set of computing power quality of service QoS parameters, where the set of computing power QoS parameters are QoS parameters associated with the first computing task.

20. The method according to claim 19, wherein Each set of computing power QoS parameters includes transmission QoS parameters and / or computing QoS parameters.

21. A communication method, characterized in that: include: receiving a first identifier from a first node, where the first identifier is used to indicate a first air interface bearer and the first identifier is associated with a first computing task; First data is sent to the first node through the first air interface bearer, where the first data is data associated with the first computing task.

22. The method according to claim 21, characterized in that The method further comprises: A first request message is sent to the first node, where the first request message includes an identifier of the first computing task, and the first request message is used to request scheduling of the first computing task.

23. The method according to claim 21 or 22, characterized in that The method further comprises: A first data packet is sent via the second air interface, where the first data packet carries second data and an identifier of a first computing task, and the identifier of the first computing task indicates that the second data is data associated with the first computing task.

24. The method according to claim 21 or 22, characterized in that The method further includes: receiving fifth data on the first air interface bearer, where the fifth data comes from a target instance, and the target instance is used to process data associated with the first computing task.

25. The method according to any one of claims 21 to 24, characterized in that The method further includes: sending first indication information on the first air interface bearer, where the first indication information is used to indicate that the first computing task is finished.

26. The method according to claim 25, characterized in that The first indication information also includes an identifier of the first computing task.

27. The method according to any one of claims 21 to 26, characterized in that The method further comprises: Send a fourth request message, where the fourth request message is used to indicate the end of scheduling of the first computing task.

28. The method according to any one of claims 21 to 27, characterized in that The first identifier is also associated with at least one set of computing power quality of service QoS parameters, where the set of computing power QoS parameters are QoS parameters associated with the first computing task.

29. The method according to claim 28, characterized in that Each set of computing power QoS parameters includes transmission QoS parameters and / or computing QoS parameters.

30. A communication device, characterized in that: The method comprises a method for performing the method according to any one of claims 1 to 20, or a method for performing the method according to any one of claims 21 to 29.

Images