Communication method, and device

Abstract

The present application relates to a communication method, and a device. The method comprises: a terminal receiving first configuration information from a control plane network element, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used for determining a first identifier carried in a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and execute related processing.

Description

Communication methods and devices Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0002] With the development of communication technology, there may be a need for network-based computing services in communication systems. For example, various types of nodes may be needed to participate in computation to complete an operation. These nodes can include one or more of the following: terminals, access network equipment, core network equipment, and application servers. However, in communication systems, how to enable the various nodes providing computing power to coordinate and complete an operation becomes a problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and device.

[0004] This application provides a communication method, including:

[0005] The terminal receives first configuration information from a control plane network element, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0006] This application provides a communication method, including:

[0007] The control plane network element sends first configuration information to the terminal, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0008] This application provides a communication method, including:

[0009] The first execution node receives third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0010] This application provides a terminal, including:

[0011] The first communication unit is configured to receive first configuration information from a control plane network element, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0012] This application provides a control plane network element, including:

[0013] The second communication unit is used to send first configuration information to the terminal, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0014] This application provides a first execution node, including:

[0015] The third communication unit is used to receive third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0016] This application provides a terminal, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the terminal to perform the methods described above.

[0017] This application provides a control plane network element, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to cause the control plane network element to perform the methods described above.

[0018] This application provides a first execution node, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to cause the first execution node to perform the above-described method.

[0019] This application provides a chip for implementing the above method.

[0020] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the methods described above.

[0021] This application provides a computer-readable storage medium for storing a computer program, which, when run by a device, causes the device to perform the above-described method.

[0022] This application provides a computer program product, including computer program instructions that cause a computer to perform the above-described method.

[0023] By adopting the above scheme, the terminal obtains first configuration information from the control plane network element. Based on the first binding relationship determined by this first configuration information, the terminal can determine the first identifier that the data packet for the first operation needs to carry. This first identifier is used by each first execution node performing the first operation to identify the relevant data packet and perform related processing. In this way, an identifier can be added to the relevant data or data packet for an operation on the terminal side, enabling each first execution node to correctly perform the corresponding operation on the data packet by recognizing the identifier, ensuring that the relevant data for the same operation can be processed collaboratively by the nodes. Attached Figure Description

[0024] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application.

[0025] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application.

[0026] Figure 3 is a schematic flowchart of a communication method according to another embodiment of this application.

[0027] Figure 4 is a schematic flowchart of a communication method according to another embodiment of this application.

[0028] Figure 5 is a schematic diagram of a scenario in which a first operation of a UE according to an embodiment of the present application is performed collaboratively by a second execution node.

[0029] Figure 6 is a schematic diagram of the QUIC protocol frame format according to an embodiment of this application.

[0030] Figure 7 is a schematic diagram of a system architecture according to an embodiment of this application.

[0031] Figures 8 to 13 are various schematic flowcharts of a communication method according to an embodiment of the present application.

[0032] Figure 14 is a schematic block diagram of a terminal according to an embodiment of this application.

[0033] Figure 15 is a schematic block diagram of a control plane network element according to an embodiment of the present application.

[0034] Figure 16 is a schematic block diagram of a first execution node according to an embodiment of the present application.

[0035] Figure 17 is a schematic block diagram of a communication device according to an embodiment of this application.

[0036] Figure 18 is a schematic block diagram of a chip according to an embodiment of this application.

[0037] Figure 19 is a schematic block diagram of a communication system according to an embodiment of this application. Detailed Implementation

[0038] The technical solutions of this application embodiment can be applied to various communication systems, such as: LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), NR (New Radio), evolution of NR, WLAN (Wireless Local Area Network), WiFi (Wireless Fidelity), or other communication systems.

[0039] This application describes various embodiments in conjunction with network devices and terminals. The terminal can be mobile or fixed, and may also be referred to as a mobile station, user unit, etc. The terminal can be a station in a WLAN, or a smart terminal, wireless modem, laptop, tablet, etc. In this application embodiment, the terminal can be a VR (Virtual Reality) terminal / AR (Augmented Reality) terminal, industrial control terminal, autonomous driving terminal, telemedicine terminal, smart grid terminal, transportation safety terminal, smart city terminal, or smart home wireless terminal, etc. By way of example and not limitation, in this application embodiment, the terminal can also be a wearable device.

[0040] In this embodiment, the network device can be a device for communicating with a terminal. The network device can be an access point in a WLAN, an evolved base station in LTE, a relay station, a vehicle-mounted device, a wearable device, a network device in an NR network (gNB, the next generation Node B), a network device in a future PLMN network, or a network device in a non-terrestrial network, etc. By way of example and not limitation, in this embodiment, the network device can have mobility characteristics; for example, the network device can be a mobile device.

[0041] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0042] Figure 1 exemplarily illustrates a communication system 100. The communication system includes network devices 110 and terminals 120. In one possible implementation, the communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include one or more terminals 120; this embodiment does not limit this. In another possible implementation, the communication system 100 may also include other network entities such as mobility management entities and access and mobility management functions; this embodiment does not limit this. The network devices may further include access network devices and control plane network elements. That is, the communication system may also include multiple core networks for communicating with the access network devices. The access network devices may be base stations of LTE, LTE-A, or NR systems. Taking the communication system shown in Figure 1 as an example, the communication devices may include network devices and terminals with communication functions. The communication devices may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities; this embodiment does not limit this.

[0043] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0044] S210. The terminal receives first configuration information from a control plane network element, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0045] Figure 3 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0046] S310. The control plane network element sends first configuration information to the terminal, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0047] Figure 4 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0048] S410, the first execution node receives third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0049] The first identifier can be used by one or more first execution nodes to identify data packets related to the first operation and / or to perform related processing.

[0050] The relevant processing may include: data processing and / or data transmission.

[0051] Control plane network elements may include at least one of the following from the core network side: SMF (Session Management Function), AMF (Access and Mobility Management Function), PCF (Policy Control Function), etc. This document does not limit or exhaustively list all possible implementations of the control plane network element.

[0052] The device type of any one of the one or more first execution nodes may include: access network equipment, core network side NF (Network Function), server, terminal, etc.

[0053] Among them, the NF on the core network side, which is any first execution node, may be a control plane NF or a user plane NF. The user plane NF may include UPF (User Plane Function), etc.

[0054] When the device type of any first execution node is a terminal, this application refers to the first execution node as another terminal.

[0055] Different first execution nodes may have the same or different device types. This document does not limit or exhaustively list all possible device types for the first execution node.

[0056] In some possible implementations, before the terminal receives the first configuration information from the control plane network element, the method further includes: the terminal receiving second configuration information from the control plane network element, wherein the second configuration information includes a second binding relationship, the second binding relationship being used by the terminal to determine a second identifier carried in the data packet related to the first operation, and the second identifier being used by one or more second execution nodes to identify the data packet related to the first operation and perform related processing. Correspondingly, before the control plane network element sends the first configuration information to the terminal, the method further includes: the control plane network element sending the second configuration information to the terminal, wherein the second configuration information includes a second binding relationship, the second binding relationship being used by the terminal to determine a second identifier carried in the data packet related to the first operation, and the second identifier being used by one or more second execution nodes to identify the data packet related to the first operation and perform related processing.

[0057] Here, the second identifier can be used by one or more second execution nodes to determine the data packets related to the first operation and / or to perform related processing.

[0058] In one embodiment, before the terminal receives the second configuration information from the control plane network element, the terminal's processing may further include: the terminal sending a first indication to the control plane network element, wherein the first indication is used to indicate at least one of the following: the terminal supports or requests the network side to provide computing power services for the terminal, or the terminal has computing capabilities. Before the control plane network element sends the second configuration information to the terminal, the control plane network element's processing may further include: the control plane network element receiving a first indication from the terminal, wherein the first indication is used to indicate at least one of the following: the terminal supports or requests the network side to provide computing power services for the terminal, or the terminal has computing capabilities.

[0059] In this context, computing power services refer to services that provide computing (or computing power) resources to process an operation. The computing power services provided by the 3GPP system can compute or process part or all of an operation. Computing power services can be used for operation-related computations, such as computations related to autonomous driving operations, AI inference or training operations, and positioning-related computations. In providing computing power services, it can also be combined with communication capabilities. By rationally allocating communication resources and computing power resources, the data transmission time and data processing time during the computation or processing of data or data packets related to an operation can be ensured to remain within a certain time range. This time range can be configured or determined according to actual needs and is not limited here.

[0060] It should be noted that the provision of computing power services to the terminal by the network side is not intended to limit the provision of computing power resources and / or communication resources to the terminal to execution nodes within the 3GPP system or network. Rather, it refers to the allocation of computing power resources and / or communication resources to the terminal by the network side to one or more execution nodes, which may include nodes (or devices) belonging to the 3GPP system and / or devices outside the 3GPP system.

[0061] Having computing power in a terminal can mean that the terminal itself has computing power and can provide its own computing power.

[0062] Optionally, the first indication is used to instruct the terminal to support or request the network side to provide computing power services to the terminal. In this case, the terminal can use the first indication to indicate that it needs or requests the network side to provide computing power services.

[0063] Optionally, the first indication is used to indicate that the terminal supports or requests the network side to provide computing power services to the terminal, and that the terminal has computing capabilities. In this case, the terminal can use the first indication to indicate that it needs or requests computing power services, and that it is also capable of providing computing capabilities.

[0064] The first instruction can be carried in a session request, which can be a session establishment request or a session modification request.

[0065] Specifically, a session request can be used to request the establishment or modification of a first session, which can be used to transmit data packets related to a first operation.

[0066] Here, the first operation can be performed collaboratively by one or more execution nodes. These one or more execution nodes may include one or more first execution nodes; or the one or more execution nodes may include one or more second execution nodes, without limitation.

[0067] Furthermore, the data packet related to the first operation can refer to the data packet of the task related to the first operation. Here, the task (or business, service, or application) can be the first computational task, which may be any one of the following: a task in an autonomous driving scenario, or a large model inference task.

[0068] The first operation is one or more execution nodes performing the same first computation task. The first operation can be an operation or related processing performed collaboratively by one or more execution nodes on the data or data packets of the first computation task. That is, during the collaborative execution of the first operation by one or more execution nodes, after the data or data packets belonging to the first computation task (i.e. the data or data packets of the first computation task related to the first operation) are received by one or more execution nodes, one or more execution nodes can perform related processing on the data or data packets they receive.

[0069] Taking any one of one or more execution nodes as an example, when that execution node processes the received data or data packets, the processing can include data processing, which may include one of the following: using the execution node's local data, the received data or data packets for data processing; or processing only the received data. During the data processing process, the execution node utilizes its computing resources.

[0070] In addition, after any execution node completes the processing of the data, if there is a next-hop node after the execution node, the relevant processing of the execution node may also include data transmission, that is, the execution node transmits the processed data or data packet to the next-hop node.

[0071] For example, the first operation can also be referred to as the operation corresponding to the first session, or the first operation corresponding to the first session, etc. In the following text, the terms "first operation," "operation corresponding to the first session," and "first operation corresponding to the first session" have the same meaning and will not be explained again.

[0072] Furthermore, by carrying a first instruction in the session request, the terminal can be used by the control plane network element to know that the terminal needs or requests to obtain computing power services for the first operation corresponding to the first session.

[0073] For example, the terminal may determine, based on at least one of its own needs, its own computing power, or pre-configured strategies, whether the first operation corresponding to the first session to be established or modified requires requesting computing power services from the network side. If it determines that it needs to request computing power services from the network side, it sends a session request carrying a first instruction. The pre-configured strategies may include whether the terminal needs computing power services from the network side, etc. This is merely an illustrative example, and this application does not limit how the terminal determines whether a particular session needs to request or obtain computing power services from the network side.

[0074] Optionally, in addition to carrying the first instruction, the session request may also carry at least one of the following: the computing power requested by the terminal, information related to the first operation, and parameters related to the first session.

[0075] The computing power requested by the terminal can be represented in the following ways: the total number of calculations, operations, or computations required by the terminal, or the number of calculations, operations, or computations per unit time. For example, this computing power can be measured or represented in FLOPs (floating point operations). This unit of time can be configured according to actual needs, such as in seconds. The computing power can also be measured or represented in FLOPS (floating-point operations per second), TOPS (tera operations per second), or TFLOPS (teraFLOPS).

[0076] The computing power requested by the terminal enables the control plane network element to know the computing power required by the terminal. Then, the control plane network element can determine or select one or more first execution nodes from all nodes that can provide computing power to provide computing power for the first operation corresponding to the first session, based on the computing power requested by the terminal.

[0077] The relevant information for the first operation includes at least one of the following: the relevant identifier of the first operation, and the model information for performing the first operation.

[0078] The identifier related to the first operation can be represented by the identifier of the first computing task; the identifier of the first computing task can be pre-configured or pre-defined. The model information can also be pre-configured or pre-defined, and this embodiment does not limit the model information.

[0079] The relevant parameters for the first session may refer to other content or parameters required to be carried in the session establishment request or session modification request as specified in the relevant protocol. Here, we do not limit the possible content or parameters of the relevant parameters for the first session.

[0080] It should be understood that when a terminal carries a first indication in a session request to establish or modify a particular session, it indicates which session is being requested to be established or modified, and this session can be used to transmit data packets related to the corresponding operation. For example, a terminal can initiate a session request to establish or modify a second session according to its own needs, and this session request can also carry a first indication. In this case, the terminal carries a first indication in the session request to establish or modify the second session, which is used to request the establishment or modification of the second session. This second session can be used to transmit data packets related to a second operation, which is different from the first operation. The related processing of the second operation can be similar to that of the first operation, so this application will not elaborate on it.

[0081] In one embodiment, before sending the second configuration information to the terminal, the control plane network element may further include: determining one or more second execution nodes. Here, the timing of the control plane network element determining the execution of one or more second execution nodes may be after receiving the first instruction and before sending the second configuration information.

[0082] The one or more second execution nodes are used to collaboratively execute the first operation.

[0083] The control plane network element may determine the one or more second execution nodes by interacting with the computing power management network element (CMF) to determine the one or more second execution nodes.

[0084] Among them, the computing power management network element can also be called the computing power collection function or the computing power management function.

[0085] A computing power management network element can collect the computing power provided by one or more nodes or execution nodes. Each execution node in one or more execution nodes can be a node capable of providing computing power or computing power resources. Computing power can be measured in FLOPS, TFLOPS, or TOPS. An execution node is a node capable of providing computing power; in the following text, the meanings of execution node and node are the same and will not be explained again.

[0086] Any node or device type that can provide computing power or computing resources can be one of the following: access network equipment, network function (NF) on the core network side, server, terminal, etc.

[0087] The types of NFs on the core network side that can provide computing power or computing resources can be one of the following: user plane network elements, sensing functions, AI functions, NWDAF (Network Data Analytics Function), etc. Among them, user plane network elements may include UPF (User Plane Function), etc. This article does not limit or exhaust all possible types of core network devices that can provide computing power or computing resources.

[0088] Any server capable of providing computing power or computing resources can be one of the following: edge computing server, remote server, etc.

[0089] When a node or device that can provide computing power or computing resources is a terminal, that node can be referred to as another terminal, which will not be explained again below.

[0090] On the computing power management network element side, it can possess or manage the computing power (or computing power resources) status of each node capable of providing computing power globally, and / or possess or manage the information of each node capable of providing computing power. The computing power (or computing power resources) status of any node can include at least one of the following: the node's load status, the node's idle computing power, and the node's chip type; the information of any node can include at least one of the following: the node's name, the node's identifier, the node's IP address, and the node's domain name.

[0091] The interaction between the control plane network element and the computing power management network element to determine the one or more second execution nodes may include: the control plane network element sending a query request to the computing power management network element, wherein the query request carries at least one of the following: the computing power requested by the terminal, information related to the first operation, and relevant parameters of the first session; the control plane network element receiving a query response from the computing power management network element, wherein the query response carries one or more second execution nodes. This embodiment does not limit the method by which the computing power management network element ultimately determines one or more second execution nodes from all the nodes it manages.

[0092] In one embodiment, after the control plane network element determines one or more second execution nodes, it can send second configuration information to the terminal.

[0093] The second configuration information may include a second binding relationship. The second binding relationship includes the binding relationship between the second filter information corresponding to the first operation and the second identifier.

[0094] Filter information may include at least one of the following: IP (Internet Protocol) triplet, IP quintuple, Application ID, DNN (Data Network Name), domain name, etc.

[0095] The second filter information corresponding to the first operation may include at least one of the following: the second IP triplet corresponding to the first operation, the second IP quintuple corresponding to the first operation, the second Application ID corresponding to the first operation, the second DNN corresponding to the first operation, the second domain name corresponding to the first operation, etc. This embodiment does not limit the specific method by which the control plane network element determines the second filter information corresponding to the first operation. For simplicity, the second filter information corresponding to the first operation will be simply referred to as "second filter information" in the following text, and will not be described again.

[0096] The identifier can be a QFI (QoS Flow Identifier), meaning the second identifier can be a second QFI. Alternatively, the identifier can also be a newly defined ID; for example, the second identifier can be represented as a second ID.

[0097] The second binding relationship can be used by the terminal to determine whether the data to be transmitted is related to the first operation based on the second filter information, and by the terminal to carry a second identifier when transmitting a data packet containing the first operation-related data packet if it determines that the data to be transmitted is related to the first operation. When this second identifier is carried in the first operation-related data packet, it enables each of the second execution nodes collaboratively executing the first operation to identify the first operation-related data packet and / or perform related processing on the first operation-related data packet and / or data packet.

[0098] In some examples, the second configuration information further includes an execution policy of the terminal associated with the second identifier, the execution policy of the terminal associated with the second identifier including at least one of the following: a processing policy of the terminal associated with the second identifier, wherein the processing policy of the terminal associated with the second identifier is used by the terminal to determine the data processing to be performed on the data related to the first operation; a routing policy of the terminal associated with the second identifier, wherein the routing policy of the terminal associated with the second identifier is used to indicate at least one of the following: the next-hop node for the terminal to send the data packet related to the first operation, and the previous-hop node for the terminal to receive the data packet related to the first operation.

[0099] The execution policy of the terminal associated with the second identifier can be used by the terminal to determine the relevant processing that needs to be performed on the data or data packets related to the first operation, wherein the relevant processing may include data processing and / or data transmission. The execution policy of the terminal associated with the second identifier can be alternatively referred to as the terminal-side execution policy under the second identifier. In the following text, the terminal-side execution policy under the second identifier and the execution policy of the terminal associated with the second identifier have the same meaning and will not be described again.

[0100] Optionally, the execution strategy of the terminal associated with the second identifier may only include the routing strategy of the terminal associated with the second identifier. In this example, the terminal may not participate in the calculation process of the first operation, but the terminal needs to transmit data packets related to the first operation.

[0101] In one scenario, the routing policy of the terminal associated with the second identifier is used only to instruct the terminal to send the next-hop node for the data packets related to the first operation. That is, the terminal may not participate in the computation of the first operation, but it still needs to send the data packets related to the first operation.

[0102] The routing policy for the terminal associated with the second identifier may include: information about the next-hop node for which the terminal sends data packets related to the first operation. This next-hop node can be any one of the aforementioned one or more second execution nodes. The information about the next-hop node may include at least one of the following: the network address of the next-hop node, and the identifier of the next-hop node. The network address may include at least one of the following: an IP address, a MAC (Media Access Control) address, etc.

[0103] In one scenario, the routing policy associated with the terminal by the second identifier can be used to instruct the terminal on the next-hop node for sending the data packets related to the first operation and the previous-hop node for receiving the data packets related to the first operation. That is, the terminal may not participate in the calculation and processing of the first operation, but it still needs to send and receive data packets related to the first operation.

[0104] The routing policy of the terminal associated with the second identifier may include: information about the next-hop node where the terminal sends the data packet related to the first operation, and information about the previous-hop node where the terminal receives the data packet related to the first operation. The next-hop node can be any one of the aforementioned one or more second execution nodes, and the previous-hop node can be any one of the aforementioned one or more second execution nodes, and the previous-hop node and the next-hop node may be different. The information of the previous-hop node may include at least one of the following: the network address of the previous-hop node, and the identifier of the previous-hop node. The explanation regarding the network address is the same as in the previous example and will not be repeated.

[0105] In this scenario, after the data related to the first operation is processed by the upstream node of the terminal, the upstream node encapsulates the processed data into a data packet related to the first operation and sends it back to the terminal. From the terminal's perspective, this includes both the uplink data or data packet related to the first operation transmitted by the terminal and the downlink data or data packet related to the first operation received by the terminal, thus forming a round-trip or round-trip transmission process.

[0106] Optionally, the execution strategy of the terminal associated with the second identifier may include the processing strategy of the terminal associated with the second identifier and the routing strategy of the terminal associated with the second identifier. In this example, the terminal participates in the data processing of the first operation and also needs to transmit data packets related to the first operation. The relevant description of the routing strategy of the terminal associated with the second identifier is the same as in the previous example, and therefore will not be repeated.

[0107] The processing strategy of the terminal associated with the second identifier may include at least one of the following: the computing resources used by the terminal to process the data related to the first operation, and information related to the model used by the terminal to process the data related to the first operation.

[0108] The information related to the model used by the terminal to process the data related to the first operation may include at least one of the following: the model's identifier (or number or name), the information related to the model's input data, and the information related to the model's output data. The information related to the model's input data may include at least one of the following: the conditions or format that the terminal needs to meet when inputting the data related to the first operation into the model, and other local data that the terminal needs to use. The information related to the model's output data may include the format of the output data.

[0109] The second configuration information can be carried in a session response, which can be a session establishment response or a session modification response. For example, if the first indication is carried in a session establishment request, the second configuration information can be carried in a session establishment response, which can also be used to indicate the completion of establishing the first session; or, if the first indication is carried in a session modification request, the second configuration information can be carried in a session modification response, which can also be used to indicate the completion of modifying the first session.

[0110] Optionally, the control plane network element sends a session reply to the terminal, the session reply carrying the second configuration information.

[0111] Optionally, the control plane network element sends an N2 message to the access network device corresponding to the terminal. The N2 message carries a NAS message, which includes a session reply carrying the second configuration information. The access network device corresponding to the terminal then transparently transmits the NAS message to the terminal.

[0112] This transmission method is particularly suitable for scenarios where the access network device corresponding to the terminal also acts as a second execution node. For example, a control plane network element can send an N2 message to the access network device corresponding to the terminal. This N2 message carries the fourth configuration information and a NAS message corresponding to the access network device. The NAS message includes a session reply carrying the second configuration information. Correspondingly, the access network device corresponding to the terminal can extract its own fourth configuration information from the N2 message and transparently transmit the NAS message to the terminal. The content of the fourth configuration information will be described in detail in the following embodiments.

[0113] It should be understood that this transmission method can also be applied to scenarios where the access network device corresponding to the terminal does not act as any second execution node, and this is not limited here.

[0114] In one embodiment, after the control plane network element determines the second execution node, the executable processing further includes: the control plane network element sending fourth configuration information corresponding to each of the one or more second execution nodes to each of the second execution nodes, wherein the fourth configuration information corresponding to each of the second execution nodes includes the execution strategy of each of the second execution nodes associated with the second identifier, and the execution strategy of each of the second execution nodes associated with the second identifier is used by each of the second execution nodes to determine the relevant processing for coordinating the execution of the first operation.

[0115] The execution strategy of each second execution node associated with the second identifier includes at least one of the following: a processing strategy of each second execution node associated with the second identifier, wherein the processing strategy of each second execution node associated with the second identifier is used by each second execution node to determine the processing to be performed on the data related to the first operation; and a routing strategy of each second execution node associated with the second identifier, wherein the routing strategy of each second execution node associated with the second identifier is used to indicate at least one of the following: the next-hop node for each second execution node to send the data packet related to the first operation, and the previous-hop node for each second execution node to receive the data packet related to the first operation.

[0116] Accordingly, for any second execution node, the second execution node receives fourth configuration information from the control plane network element, wherein the fourth configuration information includes the execution strategy of the second execution node associated with the second identifier, and the execution strategy of the second execution node associated with the second identifier is used by the second execution node to determine the relevant processing for coordinating the execution of the first operation.

[0117] For any given second execution node, the execution strategy of the second execution node associated with the second identifier includes at least one of the following: a processing strategy of the second execution node associated with the second identifier, wherein the processing strategy of the second execution node associated with the second identifier is used by the second execution node to determine the processing to be performed on the data related to the first operation; and a routing strategy of the second execution node associated with the second identifier, wherein the routing strategy of the second execution node associated with the second identifier is used to indicate at least one of the following: the next-hop node for the second execution node to send the data packet related to the first operation, and the previous-hop node for the second execution node to receive the data packet related to the first operation.

[0118] The descriptions of the routing policies for each second execution node are similar to those for the aforementioned terminal, and therefore will not be repeated. Similarly, the descriptions of the processing policies for each second execution node are similar to those for the aforementioned terminal, and will not be repeated.

[0119] Optionally, the fourth configuration information corresponding to each second execution node may also include a second binding relationship.

[0120] In one embodiment, during the process where the terminal performs related processing on the data or data packets related to the first operation based on the second configuration information it receives (i.e., the execution policy of the terminal associated with the second binding relationship and / or the second identifier), and each second execution node performs related processing on the data or data packets related to the first operation based on the fourth configuration information it receives (i.e., the execution policy of the second execution node associated with the second identifier), the control plane network element can further determine whether at least some operations in the first operation need to be migrated. If it is determined that at least some operations in the first operation need to be migrated, the processing of the control plane network element can further include: the control plane network element sending the first configuration information to the terminal. Correspondingly, the processing of the terminal can include: the terminal receiving the first configuration information from the control plane network element.

[0121] Here, "at least some of the operations in the first operation need to be migrated" can mean that at least some of the operations or at least some of the related processes in the first operation need to be migrated from the original execution node to the new execution node.

[0122] The control plane network element may determine whether at least some of the operations in the first operation need to be migrated from the original execution node to the new execution node in the following ways: the control plane network element determines whether at least some of the operations in the first operation need to be migrated from the original execution node to the new execution node based on at least one of the following: terminal mobility, load sharing, etc.

[0123] Among them, the mobility of the terminal can refer to the change in the location of the terminal as the terminal moves.

[0124] Load sharing can represent the load on each node, which can refer to the computing power (or computing resources) of all nodes that can provide computing power.

[0125] For example, the control plane network element can determine whether at least some of the operations in the first operation need to be migrated from the original execution node to the new execution node based on the mobility of the terminal.

[0126] Specifically, the control plane network element can determine whether the location of the terminal has changed. If the location of the terminal has changed, it can determine whether there is an original execution node among one or more second execution nodes that cannot cover the location of the terminal. If there is no original execution node that cannot cover the location of the terminal, it can select a new execution node from the remaining nodes that can provide computing power based on the location of the terminal, and determine that at least part of the operation in the first operation is migrated from the original execution node to the new execution node.

[0127] The method for determining the location change of the terminal can be: the terminal moves from one area to another, which may be at least one of the following: physical cell, tracking area, area divided by latitude and longitude.

[0128] For example, the control plane network element can determine, based on the load sharing situation, whether at least some of the operations in the first operation need to be migrated from the original execution node to the new execution node.

[0129] Specifically, the control plane network element can determine whether there is an original execution node with a load higher than the threshold value among one or more second execution nodes. If not, it is determined that the first operation does not need to be migrated. If there is an original execution node with a load higher than the threshold value, a new execution node with a load not higher than the threshold value is selected from the remaining nodes that can provide computing power, and it is determined that at least part of the operation in the first operation is migrated from the original execution node to the new execution node.

[0130] It should be noted that the above is merely an illustrative example. In actual processing, the mobility of the terminal and the load sharing can also be combined to determine whether at least some operations in the first operation need to be migrated from the original execution node to the new execution node. For example, when the terminal's location changes, if one or more second execution nodes have an original execution node with a load higher than a threshold, and / or one or more second execution nodes have an original execution node that cannot cover the terminal's location, the control plane network element can select a new execution node from the remaining nodes that can provide computing power, which can cover the terminal's location and has a load not higher than the threshold, and determine that at least some operations in the first operation are migrated from the original execution node to the new execution node. Here, we do not limit or exhaust all possible processing methods for the control plane network element to determine how at least some operations in the first operation need to be migrated, or to determine the original and new execution nodes.

[0131] Furthermore, if the control plane network element determines that at least part of the operation in the first operation is migrated from the original execution node to the new execution node, the control plane network element may determine one or more first execution nodes.

[0132] The one or more first execution nodes are used to collaboratively execute the first operation. Specifically, the one or more first execution nodes are used to collaboratively execute the first operation when at least some operations in the first operation are migrated from the original execution node to the new execution node, and the one or more first execution nodes include the new execution node.

[0133] In this process, one or more first execution nodes are at least partially different from one or more second execution nodes. The number of original execution nodes being migrated can be one or more, and the original execution nodes can be at least one of one or more second execution nodes; the number of new execution nodes can also be one or more, and the new execution nodes are included in one or more first execution nodes.

[0134] In other words, the first operation was originally executed collaboratively by one or more second execution nodes, or by a terminal and one or more second execution nodes, where different second execution nodes could handle different parts of the first operation. During the collaborative execution by one or more second execution nodes, or by a terminal and one or more second execution nodes, the control plane network element can determine that some operations or related processes in the first operation, originally executed by one or more second execution nodes, need to be migrated to one or more new execution nodes, i.e., each new execution node replaces one or more second execution nodes to execute at least a portion of the operations in the first operation.

[0135] Referring to Figure 5, the first operation of the UE is processed collaboratively by execution node-1 and execution node-3. Execution node-1 performs a portion of the first operation or some related processing, while execution node-3 performs another portion of the first operation or another portion of related processing. For example, the control plane network element determines that a portion of the first operation originally performed by execution node-1 needs to be migrated to a new execution node-2. That is, the new execution node-2 provides computing resources or computing services to perform a portion of the first operation. In other words, the new execution node-2 and execution node-3 collaboratively perform the first operation, and the new execution node-2 and execution node-3 constitute one or more first execution nodes.

[0136] Figure 5 also illustrates the base station (i.e., the base station corresponding to the UE). This base station may also act as a second execution node. For example, the UE's first operation is processed collaboratively by the base station, execution node-1, and execution node-3 in Figure 5. For instance, the control plane network element determines that some operations in the first operation originally performed by execution node-1 need to be migrated to a new execution node-2. That is, the new execution node-2 provides computing resources or computing services to perform a part of the first operation. In other words, the base station, the new execution node-2, and execution node-3 collaboratively execute the first operation. The base station, the new execution node-2, and execution node-3 constitute one or more first execution nodes.

[0137] The above is merely an illustrative example; it does not limit or exhaustively list all possible scenarios for node migration in at least a portion of the first operation.

[0138] In one embodiment, after determining one or more first execution nodes, the control plane network element may send first configuration information to the terminal. Correspondingly, the terminal receives the first configuration information from the control plane network element.

[0139] The first configuration information can be carried by a downlink NAS message. This first configuration information can be received during the transmission of a data packet related to the first operation by the terminal. For example, the downlink NAS message can be a session modification command.

[0140] The initial configuration information can be used by the terminal to determine the initial binding relationship.

[0141] The first binding relationship includes the binding relationship between the first filter information corresponding to the first operation and the first identifier. The description of the filter information is the same as in the previous embodiments. For example, the first filter information corresponding to the first operation may include at least one of the following: the first IP triplet corresponding to the first operation, the first IP quintuple corresponding to the first operation, the first ApplicationID corresponding to the first operation, the first DNN corresponding to the first operation, the first domain name corresponding to the first operation, etc. For simplicity, the first filter information corresponding to the first operation will be simply referred to as the first filter information in the following text, and will not be described again.

[0142] The first identifier can be the first QFI; or, the first identifier can be a newly defined first ID.

[0143] The first binding relationship can be used by the terminal to determine whether the data to be transmitted is related to the first operation based on the first filter information, and by the terminal to carry a first identifier when transmitting a data packet containing the first operation-related data if it determines that the data to be transmitted is related to the first operation. When the first identifier is carried in the data packet related to the first operation, it enables each first execution node collaboratively executing the first operation to identify the data packet related to the first operation and / or perform related processing on the data packet related to the first operation.

[0144] The second filter information is different from the first filter information, and / or the second identifier is different from the first identifier.

[0145] Optionally, the first configuration information includes the first binding relationship. In this case, the terminal can directly obtain and save the first binding relationship from the first configuration information.

[0146] Optionally, if the second filter information is the same as the first filter information, the first configuration information includes a mapping relationship between the first identifier and the second identifier, wherein the mapping relationship between the first identifier and the second identifier is used by the terminal to determine the first binding relationship.

[0147] The terminal can determine the first binding relationship in the following ways: the terminal searches for the locally stored second binding relationship based on the second identifier, replaces the second identifier in the second binding relationship with the first identifier based on the mapping relationship between the first identifier and the second identifier, and directly uses the second filter information corresponding to the first operation in the second binding relationship as the first filter information corresponding to the first operation; and determines the binding relationship (i.e., the first binding relationship) between the first filter information corresponding to the first operation and the first identifier.

[0148] In other words, if the second filter information is the same as the first filter information and the second identifier is different from the first identifier, the control plane network element can enable the terminal to determine or obtain the first binding relationship by simply indicating the mapping relationship between the first identifier and the second identifier.

[0149] In some examples, the first configuration information further includes an execution policy of the terminal associated with the first identifier, the execution policy of the terminal associated with the first identifier including at least one of the following: a processing policy of the terminal associated with the first identifier, wherein the processing policy of the terminal associated with the first identifier is used for the terminal to determine the data processing to be performed on the data related to the first operation; a routing policy of the terminal associated with the first identifier, wherein the routing policy of the terminal associated with the first identifier is used to indicate at least one of the following: the next-hop node for the terminal to send the data packet related to the first operation, and the previous-hop node for the terminal to receive the data packet related to the first operation.

[0150] The execution policy of the terminal associated with the first identifier can be used by the terminal to determine the relevant processing that needs to be performed on the data or data packet related to the first operation. The execution policy of the terminal associated with the first identifier can be replaced by the terminal-side execution policy under the first identifier. In the following text, the terminal-side execution policy under the first identifier and the execution policy of the terminal associated with the first identifier have the same meaning and will not be explained again.

[0151] Optionally, the execution strategy of the terminal associated with the first identifier may only include the routing strategy of the terminal associated with the first identifier. In this example, the terminal may not participate in the calculation process of the first operation, but the terminal needs to transmit data packets related to the first operation.

[0152] In one scenario, the routing policy of the terminal associated with the first identifier is used only to instruct the terminal to send the next-hop node for the data packets related to the first operation. That is, the terminal may not participate in the computation of the first operation, but it still needs to send the data packets related to the first operation.

[0153] The routing policy of the terminal associated with the first identifier may include information about the next-hop node for which the terminal sends the data packet related to the first operation. This next-hop node can be any one of the aforementioned one or more first execution nodes. The information about the next-hop node for which the terminal sends the data packet related to the first operation, included in the routing policy of the terminal associated with the first identifier, may be the same as or different from the information about the next-hop node for which the terminal sends the data packet related to the first operation, included in the routing policy of the terminal associated with the second identifier; this example does not limit this.

[0154] In one scenario, the routing policy of the terminal associated with the first identifier can be used to instruct the terminal on the next-hop node for sending data packets related to the first operation and the previous-hop node for receiving such data packets. That is, the terminal may not participate in the computation of the first operation, but it still needs to send and receive data packets related to the first operation.

[0155] The routing strategy for the terminal associated with the first identifier may include: information about the next-hop node where the terminal sends the data packet related to the first operation, and information about the previous-hop node where the terminal receives the data packet related to the first operation. The next-hop node may be any one of the aforementioned one or more first execution nodes, and the previous-hop node may be any one of the aforementioned one or more first execution nodes, and the previous-hop node and the next-hop node may be different.

[0156] The information about the next-hop node for the terminal sending the first operation-related data packet, included in the routing policy of the terminal associated with the first identifier, may be the same as or different from the information about the next-hop node for the terminal sending the first operation-related data packet, included in the routing policy of the terminal associated with the second identifier; and / or, the information about the previous-hop node for the terminal sending the first operation-related data packet, included in the routing policy of the terminal associated with the first identifier, may be the same as or different from the information about the previous-hop node for the terminal sending the first operation-related data packet, included in the routing policy of the terminal associated with the second identifier. This example does not impose any limitations.

[0157] In this case, it includes both the uplink data or data packets related to the first operation transmitted by the terminal and the downlink data or data packets related to the first operation received by the terminal, thus forming a Round-Trip.

[0158] Optionally, the execution strategy of the terminal associated with the first identifier may include the processing strategy of the terminal associated with the first identifier and the routing strategy of the terminal associated with the first identifier. In this example, the terminal participates in the calculation and processing of the first operation and also needs to transmit data packets related to the first operation. The relevant description of the routing strategy of the terminal associated with the first identifier is the same as in the previous example, so it will not be repeated.

[0159] The processing strategy of the terminal associated with the first identifier may include at least one of the following: computing resources used by the terminal to process data related to the first operation, and information related to the model used by the terminal to process data related to the first operation. The description of the information related to the model used by the terminal to process data related to the first operation is similar to that in the previous embodiments and will not be repeated.

[0160] The processing strategy of the terminal associated with the first identifier may be the same as or different from the processing strategy of the terminal associated with the second identifier. For example, the computing resources used by the terminal to process data related to the first operation in the processing strategy of the terminal associated with the first identifier may be different from those used by the terminal associated with the second identifier. Similarly, the model-related information used by the terminal to process data related to the first operation in the processing strategy of the terminal associated with the first identifier may be different from that used by the terminal associated with the second identifier. This is merely an illustrative example, and the processing strategy of the terminal associated with the first identifier is not limited or exhaustively described here.

[0161] In some examples, the first configuration information may also include a first condition. This first condition includes at least one of the following: the activation time of the first binding relationship, the activation region of the first binding relationship, and the data transmission requirements corresponding to the first binding relationship.

[0162] Optionally, the first condition includes the activation time of the first binding relationship.

[0163] The activation time of the first binding relationship may include the activation period of the first binding relationship, which may include the activation start time, or the activation start time and the activation end time.

[0164] If the startup time of the first binding relationship includes only the start time of its activation, then the terminal determines that the first condition is met if it determines that the current time has reached the start time of the activation of the first binding relationship; otherwise, it determines that the first condition is not met. If the startup time of the first binding relationship includes both the start time and the end time of its activation, then the terminal determines that the first condition is met if it determines that the current time has reached the start time of the activation of the first binding relationship; the terminal determines that the first condition is not met if it determines that the current time has not reached the start time of the activation of the first binding relationship, or if the current time has reached the end time of the activation of the first binding relationship.

[0165] Optionally, the first condition includes the enabled region of the first binding relationship.

[0166] The number of enabled areas for the first binding relationship can be one or more, and the area can be any one of physical cells, tracking areas, latitude and longitude-based areas, etc. The terminal can determine that the first condition is met if it determines that its current location is within the enabled area of ​​the first binding relationship; otherwise, it can determine that the first condition is not met.

[0167] Optionally, the first condition includes the data transmission requirements corresponding to the first binding relationship.

[0168] The data transmission requirements corresponding to the first binding relationship can be configured according to the actual situation.

[0169] For example, the data transmission requirement corresponding to the first binding relationship may include the terminal's data transmission rate not reaching a specified threshold. This situation can be understood as the terminal using the current second binding relationship for data transmission, but due to factors such as load conditions and / or terminal mobility, the terminal's data transmission rate is low (e.g., below the specified threshold). In this case, the terminal can determine that the first condition is met; otherwise, it can determine that the first condition is not met. It should be noted that this is only an illustrative example, and in actual processing, data transmission requirements may be set to other requirements, which are not limited or exhaustively listed here.

[0170] The above is merely a description of the first condition including any one of the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship. In actual processing, the first condition may include at least two of the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship. For example, the first condition may include the activation area of ​​the first binding relationship and the data transmission requirements corresponding to the first binding relationship. Accordingly, the terminal can determine that the first condition is met if it is determined that its current location is within the activation area of ​​the first binding relationship and the data transmission requirements corresponding to the first binding relationship are met; otherwise, it determines that the first condition is not met.

[0171] It should be noted that in actual processing, the first condition may include other conditions, and we will not limit or exhaustively list the possible contents of the first condition here.

[0172] In one embodiment, after determining one or more first execution nodes, the control plane network element can further perform the following processing: the control plane network element sends third configuration information corresponding to each of the one or more first execution nodes to each of the first execution nodes, wherein the third configuration information corresponding to each first execution node includes the execution strategy of each first execution node associated with the first identifier, and the execution strategy of each first execution node associated with the first identifier is used by each first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0173] The order in which the control plane network element sends the third configuration information corresponding to each first execution node to each first execution node and the order in which the control plane network element sends the first configuration information to the terminal are not limited in this embodiment.

[0174] The execution strategy of each first execution node associated with the first identifier includes at least one of the following: a processing strategy of each first execution node associated with the first identifier, wherein the processing strategy of each first execution node associated with the first identifier is used by each first execution node to determine the data processing to be performed on the data related to the first operation; a routing strategy of each first execution node associated with the first identifier, wherein the routing strategy of each first execution node associated with the first identifier is used to indicate at least one of the following: the next-hop node for each first execution node to send the data packet related to the first operation, and the previous-hop node for each first execution node to receive the data packet related to the first operation.

[0175] Accordingly, for any first execution node, the first execution node receives third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0176] For any first execution node, the execution strategy of the first execution node associated with the first identifier includes at least one of the following: a processing strategy of the first execution node associated with the first identifier, wherein the processing strategy of the first execution node associated with the first identifier is used by the first execution node to determine the processing to be performed on the data related to the first operation; a routing strategy of the first execution node associated with the first identifier, wherein the routing strategy of the first execution node associated with the first identifier is used to indicate at least one of the following: the next-hop node for the first execution node to send the data packet related to the first operation, and the previous-hop node for the first execution node to receive the data packet related to the first operation.

[0177] The descriptions of the routing policies for each first execution node are similar to those for the aforementioned terminal routing policies, and therefore will not be repeated. Similarly, the descriptions of the processing policies for each first execution node are similar to those for the aforementioned terminal processing policies, and will not be repeated.

[0178] In some embodiments, the first configuration information may include a first condition; alternatively, the terminal may generate the first condition locally based on a protocol or using a default method. The description of the first condition is the same as in the foregoing embodiments and will not be repeated. This embodiment does not limit the method by which the terminal generates the first condition.

[0179] In this embodiment, after receiving the first configuration information from the control plane network element, the terminal can determine whether the first condition is met. If the first condition is not met, the execution strategy of the terminal associated with the second binding relationship and the second identifier is still used to perform the relevant processing of the first operation. If the first condition is met, the execution strategy of the terminal associated with the first binding relationship and the first identifier can be used to perform the relevant processing of the first operation. The explanation regarding the terminal's determination of whether the first condition is met is the same as in the previous embodiment and will not be repeated.

[0180] In one embodiment, after the terminal receives the first configuration information from the control plane network element, the method further includes: if the terminal does not meet the first condition and determines that the data to be transmitted corresponds to the second filter information, the terminal determines the second identifier based on the second filter information and the second binding relationship, wherein the first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship; the terminal sends a second data packet, wherein the second data packet is generated based on the data to be transmitted and carries the second identifier.

[0181] In other words, when the terminal receives the first configuration information but does not meet the first condition, the related processing performed on the data or data packets related to the first operation is the same as the operation performed by the terminal after receiving the second configuration information but before receiving the first configuration information.

[0182] Here, the method by which the terminal generates the data to be transmitted is not limited in this embodiment. The method by which the terminal determines whether the data to be transmitted corresponds to the second filter information corresponding to the first operation can be the same as the relevant protocol, or it can adopt other methods, which are not limited here.

[0183] If the terminal does not meet the first condition and determines that the data to be transmitted corresponds to the second filter information, it can determine that the data to be transmitted is data related to the first operation, and then determine the second identifier based on the second filter information and the second binding relationship.

[0184] The process of generating a second data packet by the terminal may include: the terminal determining the data carried by the second data packet; and the terminal encapsulating or carrying a second identifier in the second data packet.

[0185] Optionally, the second data packet is obtained by processing the data to be transmitted based on the processing policy of the terminal associated with the second identifier.

[0186] The terminal's processing may include: if the execution strategy of the terminal associated with the second identifier includes the processing strategy of the terminal associated with the second identifier, the terminal processes the data to be transmitted based on the processing strategy of the terminal associated with the second identifier to obtain processed data; and the processed data is carried as data in the second data packet.

[0187] Optionally, the second data packet is generated based on the data to be transmitted.

[0188] Specifically, the second data packet carries the data to be transmitted. Terminal processing may include: if the execution strategy of the terminal associated with the second identifier does not include the processing strategy of the terminal associated with the second identifier, the terminal uses the data to be transmitted as the data carried in the second data packet.

[0189] Optionally, the second identifier is the second QFI. In this case, the encapsulation method of the second QFI in the second data packet is the same as that of the relevant protocol, and this embodiment does not limit it.

[0190] Optionally, the second identifier is a newly defined second ID. The first protocol layer of the second data packet carries the second identifier, wherein the first protocol layer includes one of the following: SDAP (Service Data Adaptation Protocol) layer, PDCP (Packet Data Convergence Protocol) layer, and a new protocol layer.

[0191] In the case where the second identifier is a newly defined second ID, the QFI as specified in the relevant protocol still retains its existing functions. This embodiment will not elaborate on all the existing functions of QFI in this case.

[0192] In one scenario, the first protocol layer includes one of the following: SDAP layer or PDCP layer. That is, the terminal carries the second identifier at the SDAP layer or PDCP layer of the second data packet.

[0193] Specifically, the terminal carries, encapsulates, or marks a second identifier in the header of the second data packet at the SDAP or PDCP layer.

[0194] The location of the second identifier in the header of the SDAP or PDCP layer can be an existing field, an extended field, or a new field in the header of the SDAP or PDCP layer. Here, a new field in the header of the SDAP or PDCP layer refers to a field newly defined in addition to the fields specified in the header of the SDAP or PDCP layer. This embodiment does not limit the location of this new field in the header of the SDAP or PDCP layer.

[0195] In one scenario, the first protocol layer includes a new protocol layer. That is, the terminal carries the second identifier in the new protocol layer of the second data packet.

[0196] The new protocol layer can be any protocol layer that supports data transmission. In other words, while keeping the original protocol layer architecture on the terminal side unchanged, a new protocol layer can be added, and the ID newly defined in this application, i.e., the first identifier, can be encapsulated in this new protocol layer.

[0197] In some preferred examples, the new protocol layer includes a QUIC (Quick UDP Internet Connection) layer. The second identifier defined in this application embodiment can be encapsulated, identified, or carried in the stream ID field of any one or more QUIC frames. This embodiment does not limit the specific byte or bit position occupied by the second identifier in the stream ID field.

[0198] After completing the above processing to generate the second data packet, the terminal can send the second data packet. Specifically, sending the second data packet includes: the terminal sending the second data packet to the next-hop node, wherein the next-hop node is determined based on the routing policy of the terminal associated with the second identifier, and the next-hop node is one of the one or more second execution nodes. Since the routing policy of the terminal associated with the second identifier includes at least the information of the next-hop node, the terminal can determine the next-hop node that will cooperate in performing the first operation based on the information of the next-hop node after generating the second data packet, and directly send the second data packet to the next-hop node.

[0199] Since the processing received by any one of the one or more second execution nodes from the previous hop node is the same, the following explanation will focus on the processing of any one of the second execution nodes.

[0200] For any second execution node, after receiving the fourth configuration information from the control plane network element, the process further includes: the second execution node receiving a fifth data packet; if the fifth data packet carries the second identifier, the second execution node performs relevant processing on the fifth data packet based on the execution policy of the second execution node associated with the second identifier.

[0201] Optionally, the upstream node of any second execution node is a terminal. The second execution node receives the fifth data packet as follows: the second execution node receives the fifth data packet from the terminal, and the fifth data packet is identical to the second data packet.

[0202] Optionally, the preceding node of any second execution node is not a terminal. The second execution node receives the fifth data packet as follows: the second execution node receives the fifth data packet from the preceding node, and the fifth data packet may be the same as or different from the second data packet.

[0203] When the fifth data packet carries the second identifier, the second execution node performs relevant processing on the fifth data packet based on the execution policy associated with the second identifier. This may include: determining whether the fifth data packet carries the second identifier; if the fifth data packet carries the second identifier, the second execution node determines that the fifth data packet is a data packet related to the first operation, and the second execution node performs relevant processing on the fifth data packet based on the execution policy associated with the second identifier. Alternatively, it may also include: if the fifth data packet does not carry the second identifier, determining that the fifth data packet is not a data packet related to the first operation, and performing other processing on the fifth data packet. Here, the possible processing by the second execution node when the fifth data packet is not a data packet related to the first operation is not limited.

[0204] Optionally, the second identifier is the second QFI. In this case, the encapsulation method of the second QFI in the fifth data packet is the same as that of the relevant protocol, and this embodiment does not limit it.

[0205] Optionally, the second identifier is a newly defined second ID.

[0206] In one scenario, the fifth data packet is identical to the second data packet, meaning the upstream node of the second execution node is a terminal. The first protocol layer of the fifth data packet carries the second identifier. The way the first protocol layer of the fifth data packet carries the second identifier is the same as the way the first protocol layer of the second data packet carries the second identifier in the aforementioned embodiment, and therefore will not be described again.

[0207] In one scenario, the fifth data packet differs from the second data packet, meaning that the previous hop node of the second execution node is not a terminal, and the second execution node is not another terminal. The second protocol layer of the fifth data packet carries the second identifier, wherein the second protocol layer includes one of the following: GTP-U layer, TCP / IP layer, and a new protocol layer.

[0208] For example, the second protocol layer includes one of the following: GTP-U layer or TCP / IP layer. This second identifier is in the header of the GTP-U layer or TCP / IP layer packet.

[0209] The location of this second identifier in the packet header of the GTP-U layer can be an existing field, an extended field, or a new field in the packet header of the GTP-U layer. Among them, a new field in the packet header of the GTP-U layer refers to a newly defined field in addition to the fields in the packet header specified by the GTP-U layer, which is not limited in this embodiment.

[0210] The location of this second identifier in the TCP / IP layer header can be an existing field, an extended field, or a new field in the TCP / IP layer header. Existing fields in the TCP / IP layer header may include fields such as the Type of Service field. New fields in the TCP / IP layer header refer to newly defined fields in addition to those specified in the TCP / IP layer header; this embodiment does not impose such limitations.

[0211] For example, the second protocol layer includes a new protocol layer. In some preferred examples, the new protocol layer includes a QUIC layer. The second identifier defined in the embodiments of this application can be encapsulated, identified, or carried in the stream ID field of any one or more QUCI frames. This embodiment does not limit the specific byte or bit position occupied by the second identifier in the stream ID field.

[0212] In one example, taking any second execution node as an example, if the execution strategy of the second execution node associated with the second identifier includes the processing strategy of the second execution node associated with the second identifier, the second execution node performs related processing on the fifth data packet based on the execution strategy of the second execution node associated with the second identifier. This includes: the second execution node performs data processing on the data in the fifth data packet based on the processing strategy of the second execution node associated with the second identifier to obtain processed data; if the routing strategy of the second execution node associated with the second identifier determines that there is a next-hop node, the second execution node sends a sixth data packet to the next-hop node, wherein the sixth data packet carries the second identifier and the processed data.

[0213] Specifically, if the routing policy of the second execution node associated with the second identifier determines that a next-hop node exists, the second execution node sending a sixth data packet to the next-hop node may include: the second execution node determining whether a next-hop node exists based on the routing policy of the second execution node associated with the second identifier; if the routing policy of the second execution node associated with the second identifier determines that a next-hop node exists, then the second execution node sending a sixth data packet to the next-hop node.

[0214] Optionally, if the second identifier is the second QFI, the encapsulation method of the second QFI in the sixth data packet is the same as that of the relevant protocol, and this embodiment does not limit it.

[0215] Optionally, the second identifier is a newly defined second ID.

[0216] In one scenario, the device type of the second execution node is an access network device, and the next-hop node of the second execution node is a terminal (or other terminal). The first protocol layer of the sixth data packet carries the second identifier, wherein the first protocol layer includes one of the following: SDAP layer, PDCP layer, and new protocol layer. The specific way the first protocol layer carries the second identifier is the same as in the aforementioned embodiments, and therefore will not be described in detail.

[0217] In one scenario, neither the second execution node nor its next-hop node is a terminal or any other terminal. The second protocol layer of the sixth data packet carries the second identifier, wherein the second protocol layer includes one of the following: GTP-U layer, TCP / IP layer, or a new protocol layer. The specific way the second protocol layer carries the second identifier is the same as in the aforementioned embodiments, and therefore will not be described in detail.

[0218] Additionally, it may include: if the routing policy of the second execution node associated with the second identifier determines that there is no next-hop node, then the second execution node may use the processed data as the processing result. This processing result may be stored locally on the second execution node or may be reported to other devices. This embodiment does not limit the processing of the processing result by the first execution node.

[0219] In one example, taking any second execution node as an example, if the execution policy of the second execution node associated with the second identifier does not include the processing policy of the second execution node associated with the second identifier, the second execution node performs related processing on the fifth data packet based on the execution policy of the second execution node associated with the second identifier, including: if it is determined that there is a next-hop node based on the routing policy of the second execution node associated with the second identifier, the second execution node sends a sixth data packet to the next-hop node, wherein the sixth data packet carries the second identifier and the data in the fifth data packet.

[0220] The second execution node can generate the data for the sixth data packet by extracting the data from the fifth data packet and using it directly as the data for the sixth data packet. The possible ways in which the sixth data packet carries the second identifier are the same as in the previous examples, and therefore will not be repeated.

[0221] Additionally, it may include: if the routing policy of the second execution node associated with the second identifier determines that there is no next-hop node, then the second execution node may use the data in the fifth data packet as the processing result. This processing result may be stored locally on the second execution node or may be reported to other devices. This embodiment does not limit the processing of the processing result by the first execution node.

[0222] In one embodiment, after the terminal receives first configuration information from a control plane network element, the method further includes: when the terminal determines that the data to be transmitted corresponds to the first filter information, determining the first identifier based on the first filter information and the first binding relationship; the terminal sends a first data packet, wherein the first data packet is generated based on the data to be transmitted and carries the first identifier. Specifically, determining the first identifier based on the first filter information and the first binding relationship when the terminal determines that the data to be transmitted corresponds to the first filter information includes: when the terminal satisfies a first condition and determines that the data to be transmitted corresponds to the first filter information, determining the first identifier based on the first filter information and the first binding relationship, wherein the first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship.

[0223] The method by which the terminal generates the data to be transmitted is not limited in this embodiment. The method by which the terminal determines whether the data to be transmitted corresponds to the first filter information corresponding to the first operation can be the same as the relevant protocol, or it can adopt other methods, which are not limited here.

[0224] The process of generating the first data packet by the terminal may include: the terminal determining the data carried by the first data packet; the terminal encapsulating or carrying the first identifier in the first data packet.

[0225] Optionally, the first data packet is obtained by processing the data to be transmitted based on the processing policy of the terminal associated with the first identifier. Specifically, the data carried in the first data packet is obtained by processing the data to be transmitted based on the processing policy of the terminal associated with the first identifier. The terminal processing may include: if the execution policy of the terminal associated with the first identifier includes the processing policy of the terminal associated with the first identifier, the terminal processes the data to be transmitted based on the processing policy of the terminal associated with the first identifier to obtain processed data; and uses the processed data as the data carried in the first data packet.

[0226] Optionally, the first data packet is generated based on the data to be transmitted. Specifically, the data carried by the first data packet is the data to be transmitted. Terminal processing may include: if the execution policy of the terminal associated with the first identifier does not include the processing policy of the terminal associated with the first identifier, the terminal uses the data to be transmitted as the data carried by the first data packet.

[0227] Optionally, the first identifier is the first QFI. In this case, the encapsulation method of the first QFI in the first data packet is the same as that of the relevant protocol, and this embodiment does not limit it. When the first identifier is the first QFI (and / or the second identifier is the second QFI), it can be understood that a new function is added to the QFI, that is, the QFI can also be used by each execution node to identify its corresponding operation-related data packets and / or perform related processing.

[0228] Optionally, the first identifier is a newly defined first ID. The first protocol layer of the first data packet carries the first identifier, wherein the first protocol layer includes one of the following: SDAP layer, PDCP layer, and new protocol layer. When the first identifier is a newly defined first ID, the QFI as specified in the relevant protocol still retains its existing functions. This embodiment will not elaborate on all the existing functions of QFI in this case.

[0229] In one scenario, the first protocol layer includes one of the following: SDAP layer or PDCP layer. That is, the terminal carries the first identifier in the SDAP or PDCP layer of the first data packet.

[0230] Specifically, the terminal carries, encapsulates, or identifies the first identifier in the header of the first data packet at the SDAP or PDCP layer.

[0231] The first identifier, located in the header of the SDAP or PDCP layer, can be an existing field, an extended field, or a new field in the header of the SDAP or PDCP layer. The description of new fields in the header of the SDAP or PDCP layer is the same as in the previous embodiments and will not be repeated here.

[0232] In one scenario, the first protocol layer includes a new protocol layer. That is, the terminal carries the first identifier in the new protocol layer of the first data packet.

[0233] The new protocol layer can be any protocol layer that supports data transmission. In other words, while keeping the original protocol layer architecture on the terminal side unchanged, a new protocol layer can be added, and the ID newly defined in this application, i.e., the first identifier, can be encapsulated in this new protocol layer.

[0234] In some preferred examples, the new protocol layer includes a QUIC layer. The first identifier can be encapsulated, identified, or carried in the stream ID field of any one or more QUCI frames. This embodiment does not limit the specific byte or bit position occupied by the first identifier in the stream ID field.

[0235] Referring to Figure 6, when the QUIC protocol is used to support data transmission, the data itself is carried as stream data in QUIC frames (such as frames 1, 2 to N in Figure 6). Any QUIC frame (for example, frame 2) may include the following fields: Frame Type, indicating a specific QUIC protocol frame type, such as PADDING, PING, ACK, etc.; Stream ID, used to carry, transmit, or mark the first identifier; Offset (or frame offset), used for QUIC frame delivery ordering, loss detection, and retransmission to achieve reliable data delivery; each QUIC frame is uniquely identified by the stream ID and offset; Data Length, indicating the size of the data stream; and Stream Data, used to carry the frame payload. Additionally, when transmitting data using the QUIC protocol, a QUIC frame header can also be carried. This embodiment does not limit or exhaustively list all frame formats or frame contents when transmitting data using the QUIC protocol.

[0236] The above is only an illustrative example. In actual processing, the QUIC protocol can be replaced by any other protocol used for data transmission. No limit or exhaustive list is provided here.

[0237] The terminal sending the first data packet includes: the terminal sending the first data packet to a next-hop node, wherein the next-hop node is determined based on the routing policy of the terminal associated with the first identifier, and the next-hop node is one of the one or more first execution nodes. Since the routing policy of the terminal associated with the first identifier includes at least the information of the next-hop node, the terminal can determine the next-hop node to collaboratively execute the first operation based on the information of the next-hop node after generating the first data packet, and directly send the first data packet to the next-hop node.

[0238] Since the processing received by any one of the first execution nodes from the previous hop node is the same, the following explanation will focus on the processing of any one of the first execution nodes.

[0239] For any first execution node, after receiving the third configuration information from the control plane network element, the process further includes: the first execution node receiving a third data packet; and if the third data packet carries the first identifier, the first execution node performing relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier.

[0240] The third data packet received by the first execution node may come from the terminal or from other first execution nodes, so the third data packet may be the same as or different from the first data packet.

[0241] Optionally, the upstream node of the first execution node is the terminal. The first execution node receives the third data packet as follows: the first execution node receives the third data packet from the terminal, and the third data packet is the same as the first data packet.

[0242] Optionally, the upstream node of the first execution node is not a terminal. The first execution node receives the third data packet as follows: the first execution node receives a third data packet from the upstream node. The third data packet may be the same as or different from the first data packet.

[0243] When the third data packet carries the first identifier, the first execution node performs relevant processing on the third data packet based on the execution policy associated with the first execution node of the first identifier. This may include: determining whether the third data packet carries the first identifier; if the third data packet carries the first identifier, the first execution node determines that the third data packet is a data packet related to the first operation, and the first execution node performs relevant processing on the third data packet based on the execution policy associated with the first execution node of the first identifier. Alternatively, it may also include: if the third data packet does not carry the first identifier, determining that the third data packet is not a data packet related to the first operation, and performing other processing on the third data packet. Here, the possible processing by the first execution node when the third data packet is not a data packet related to the first operation is not limited.

[0244] Optionally, the first identifier is the first QFI. In this case, the encapsulation method of the first QFI in the third data packet is the same as that of the relevant protocol, and this embodiment does not limit it.

[0245] Optionally, the first identifier is the newly defined first ID.

[0246] In one scenario, the third data packet is identical to the first data packet. The first protocol layer of the third data packet carries the first identifier, wherein the first protocol layer includes one of the following: SDAP layer, PDCP layer, or a new protocol layer. The specific method by which the first protocol layer carries the first identifier is the same as in the aforementioned embodiments, and therefore will not be repeated.

[0247] In one scenario, the third data packet differs from the first data packet, meaning the third data packet originates from another first execution node, and this other first execution node is not another terminal. The second protocol layer of the third data packet carries the first identifier, wherein the second protocol layer includes one of the following: GTP-U (GPRS Tunneling Protocol-User Plane) layer, TCP / IP (Transmission Control Protocol / Internet Protocol) layer, or a new protocol layer.

[0248] For example, the second protocol layer includes one of the following: GTP-U layer or TCP / IP layer. Specifically, this first identifier is in the header of the GTP-U layer or TCP / IP layer packet.

[0249] The location of this first identifier in the packet header of the GTP-U layer can be an existing field, an extended field, or a new field in the packet header of the GTP-U layer. Among them, the new field in the packet header of the GTP-U layer refers to a newly defined field in addition to the fields in the packet header specified by the GTP-U layer, which is not limited in this embodiment.

[0250] The location of this first identifier in the TCP / IP layer header can be an existing field, an extended field, or a new field in the TCP / IP layer header. Existing fields in the TCP / IP layer header may include fields such as the Type of Service field; new fields in the TCP / IP layer header refer to newly defined fields in addition to the fields specified in the TCP / IP layer header, which are not limited in this embodiment.

[0251] For example, the second protocol layer includes a new protocol layer. In some preferred examples, the new protocol layer includes a QUIC layer. The first identifier defined in the embodiments of this application can be encapsulated, identified, or carried in the stream ID field of any one or more QUCI frames.

[0252] In one example, still taking any first execution node as an example, when the execution strategy of the first execution node associated with the first identifier includes the processing strategy of the first execution node associated with the first identifier, the first execution node performs related processing on the third data packet based on the execution strategy of the first execution node associated with the first identifier, including: the first execution node performs data processing on the data in the third data packet based on the processing strategy of the first execution node associated with the first identifier to obtain processed data; when it is determined that there is a next-hop node based on the routing strategy of the first execution node associated with the first identifier, the first execution node sends a fourth data packet to the next-hop node, wherein the fourth data packet carries the first identifier and the processed data.

[0253] Wherein, if the routing policy of the first execution node associated with the first identifier determines that there is a next-hop node, the first execution node sending a fourth data packet to the next-hop node may include: the first execution node determining whether there is a next-hop node based on the routing policy of the first execution node associated with the first identifier; if the routing policy of the first execution node associated with the first identifier determines that there is a next-hop node, then the first execution node sending a fourth data packet to the next-hop node.

[0254] Optionally, if the first identifier is the first QFI, the encapsulation method of the first QFI in the fourth data packet is the same as that of the relevant protocol, and this embodiment does not limit it.

[0255] Optionally, the first identifier is the newly defined first ID.

[0256] In one scenario, the device type of the first execution node is an access network device, and the next-hop node of the first execution node is a terminal or other terminal. The first protocol layer of the fourth data packet carries the first identifier, wherein the first protocol layer includes one of the following: SDAP layer, PDCP layer, and new protocol layer. The specific way in which the first protocol layer of the fourth data packet carries the first identifier is the same as the specific way in which the first protocol layer of the first data packet carries the first identifier in the aforementioned embodiments, and therefore will not be described in detail.

[0257] In one scenario, neither the first execution node nor its next-hop node is a terminal or any other terminal. The second protocol layer of the fourth data packet carries the first identifier, wherein the second protocol layer includes one of the following: GTP-U layer, TCP / IP layer, or a new protocol layer. The specific way in which the second protocol layer of the fourth data packet carries the first identifier is the same as the way the second protocol layer of the third data packet carries the first identifier in the aforementioned embodiment, and therefore will not be described in detail.

[0258] Additionally, it may include: if the routing policy of the first execution node associated with the first identifier determines that there is no next-hop node, then the first execution node may use the processed data as the processing result. This processing result may be stored locally on the first execution node or may be reported to other devices. This embodiment does not limit the processing of the processing result by the first execution node.

[0259] In one example, still taking any first execution node as an example, if the execution strategy of the first execution node associated with the first identifier does not include the processing strategy of the first execution node associated with the first identifier, the first execution node performs related processing on the third data packet based on the execution strategy of the first execution node associated with the first identifier, including: if it is determined that there is a next-hop node based on the routing strategy of the first execution node associated with the first identifier, the first execution node sends a fourth data packet to the next-hop node, wherein the fourth data packet carries the first identifier and the data in the third data packet.

[0260] The first execution node can generate the fourth data packet by extracting the data from the third data packet and using it directly as the fourth data packet. The possible ways in which the fourth data packet carries the first identifier are the same as in the previous examples, and therefore will not be repeated.

[0261] Additionally, it may include: if the routing policy of the first execution node associated with the first identifier determines that there is no next-hop node, then the first execution node may use the data in the third data packet as the processing result. This processing result may be stored locally on the first execution node or may be reported to other devices. This embodiment does not limit the processing of the processing result by the first execution node.

[0262] As illustrated in the foregoing embodiments, one or more first execution nodes are at least partially different from one or more second execution nodes. That is, one or more first execution nodes may be partially the same as or partially different from one or more second execution nodes; or, one or more first execution nodes may be completely different from one or more second execution nodes.

[0263] In cases where one or more first execution nodes may be partially the same as or partially different from one or more second execution nodes, there may be one or more identical third execution nodes among the one or more first execution nodes and one or more second execution nodes. Taking any one third execution node as an example, the third execution node may first receive the fourth configuration information, and then receive the third configuration information. After the third execution node receives the third configuration information, upon first receiving a data packet carrying the first identifier, the third execution node enables the execution policy associated with the first identifier contained in the third configuration information. That is, the third execution node performs the relevant processing of the data packet as a first execution node. Then, the third execution node can delete the execution policy associated with the second identifier contained in the fourth configuration information. In other words, the third execution node can replace or update the execution policy associated with the second identifier with the execution policy associated with the first identifier.

[0264] In some embodiments, the first configuration information does not include the first condition; and the terminal side does not generate the first condition. On the terminal side, after the terminal receives the first configuration information from the control plane network element, the method further includes: when the terminal determines that the data to be transmitted corresponds to the first filter information, the terminal determines the first identifier based on the first filter information and the first binding relationship; the terminal sends a first data packet, wherein the first data packet is generated based on the data to be transmitted and carries the first identifier.

[0265] Unlike the previous embodiments, after receiving the first configuration information, the terminal side directly begins to perform relevant processing based on the execution strategy of the terminal associated with the first binding relationship and / or the first identifier.

[0266] In this embodiment, the processing of the terminal before receiving the first configuration information may also include: the terminal determining the second identifier based on the second filter information and the second binding relationship when it determines that the data to be transmitted corresponds to the second filter information; the terminal sending a second data packet, wherein the second data packet is generated based on the data to be transmitted and carries the second identifier. The descriptions of the related processing of the terminal generating and sending the second data packet are the same as in the previous embodiments, and therefore will not be repeated.

[0267] Correspondingly, the processing after any second execution node receives the fourth configuration information also includes: the second execution node receiving the fifth data packet; and, if the fifth data packet carries the second identifier, the second execution node performing relevant processing on the fifth data packet based on the execution policy of the second execution node associated with the second identifier. The description of the second execution node performing relevant processing on the fifth data packet based on the execution policy of the second execution node associated with the second identifier is the same as in the foregoing embodiments and will not be repeated here.

[0268] In this embodiment, the processing of the terminal after receiving the first configuration information differs from that in the previous embodiments only in that the terminal does not need to determine whether the first condition is met. It only needs to determine the first identifier based on the first filter information and the first binding relationship, provided that the data to be transmitted corresponds to the first filter information. The terminal then sends the first data packet. The descriptions of the related processing for generating and sending the first data packet are the same as in the previous embodiments and will not be repeated here.

[0269] Correspondingly, the processing after any first execution node receives the third configuration information also includes: the first execution node receiving the third data packet; and, if the third data packet carries the first identifier, the first execution node performing relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier. The description of the first execution node performing relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier is the same as in the foregoing embodiments and will not be repeated here.

[0270] Referring to Figure 7, an exemplary system architecture applicable to the communication method provided in this embodiment is described below:

[0271] Figure 7 illustrates the computing power management network element (CMF), whose function is the same as that in the aforementioned embodiments, and will not be described in detail.

[0272] Figure 7 illustrates the Policy Control Function (PCF), whose functions may include: allocating PCC rules, determining data flow information including filter information, corresponding QoS parameters, and a first identifier.

[0273] Figure 7 also illustrates the model management network element, which can manage the relevant information of the model of each node, such as the identifier (or number) of the model of each node that can provide computing power, the relevant information of the model's input data, the relevant information of the model's output data, and so on, at least one of these.

[0274] As shown in Figure 7, the node capable of providing computing power (such as the first execution node or the second execution node in the aforementioned embodiments) may include at least one of the user plane network elements, base stations, etc., within the 3GPP system; and / or, the node capable of providing computing power (such as the first execution node or the second execution node in the aforementioned embodiments) may include an application server. The application server may include a remote server as shown in Figure 7, and / or an EC server, where the EC server can be an Edge Computing server. The difference between an EC server and a remote server is that an EC server generally refers to an application server geographically close to the terminal (or user), typically serving a smaller area; a remote server generally serves a larger area, but may be geographically far from the terminal (or user).

[0275] Additionally, although not illustrated in Figure 7, the system architecture to which the communication method provided in this embodiment is applicable may also include a Session Management Element (SMF). Its functions may include sending session-related configuration parameters to each node during session establishment or modification. These session-related configuration parameters may include, but are not limited to, QoS rules, PDR (Packet Detection Rule), and QoS (Quality of Service) parameters. The Session Management Element can further configure each first execution node, and / or each second execution node, and / or terminal.

[0276] The aforementioned control plane network elements in the embodiments of this application may include at least one of the above-mentioned SMF, PCF, model management network elements, etc. In addition, control plane network elements may also include AMF, etc. Here, we do not limit or exhaust all the functions or devices that the control plane network elements may include.

[0277] Referring to Figures 8 and 9, an exemplary description of the communication method provided in this application is provided, including:

[0278] Step 801, the UE (i.e. the terminal) sends a session request, which carries a first indication. The first indication is used to indicate that the UE supports or requests the network to provide computing power (or supports or requests the network to provide computing power services or computing resources to the terminal, etc.), and / or that the UE has computing power.

[0279] Specifically, the UE can send a session request carrying a first indication to the control plane network element through the base station. This session request can be a session modification or establishment request. That is, by sending a session request carrying the first indication, the UE requests computing power services or computing resources for its first operation.

[0280] Step 802: The control plane network element determines one or more second execution nodes. The method by which the control plane network element selects or determines one or more second execution nodes is the same as in the previous embodiment, and will not be described again here.

[0281] In the scenario illustrated in Figure 8, one or more second execution nodes include execution plane network elements and base stations. Execution plane network elements can refer to any network-side node or server capable of providing computing power. For example, execution plane network elements may include one or more user plane network elements.

[0282] Step 803: The control plane network element configures session parameters (specifically, PDU session parameters) to the execution plane network element (such as the user plane network element), which carries configuration information (i.e., the fourth configuration information corresponding to the execution plane network element). The configuration information corresponding to the execution plane network element may include the execution policy of the execution plane network element associated with the second QFI.

[0283] The execution strategy of the execution plane network element associated with the second QFI may specifically include at least one of the following:

[0284] The processing strategy of the execution plane network element associated with the second QFI (or the operation corresponding to the execution plane network element under the second QFI) is used by the execution plane network element to determine the relevant processing to be performed on the data related to the first operation, such as the computing resources used, the model, and the input and / or output data.

[0285] The routing strategy of the execution plane network element associated with the second QFI may include at least one of the following: the next-hop node (such as the node's address or node identifier) ​​through which the execution plane network element sends the data packet related to the first operation, and the previous-hop node (such as the node's address or node identifier) ​​through which the execution plane network element receives the data packet related to the first operation.

[0286] The above execution strategy can also be called a task descriptor, task description information, operation descriptor, operation description information, etc. Here, we will not limit or exhaust all possible names.

[0287] Optionally, the configuration information corresponding to the execution plane network element may also include a second binding relationship. The second binding relationship can be the relationship between the second filter information (for example, the filter information may include at least one of the following: IP triplet, quintuple, Application ID, DNN, domain name, etc.) and the second QFI.

[0288] Step 804: The control plane network element sends configuration information (e.g., the fourth configuration information corresponding to the base station) to the base station. The content of the configuration information corresponding to the base station is similar to that of the configuration information corresponding to the execution plane network element, and will not be repeated here.

[0289] Step 805: The control plane network element sends a session reply to the UE, which carries configuration information (i.e., the second configuration information in the aforementioned embodiment). This configuration information includes the second binding relationship. In addition, the configuration information sent to the UE may also include the execution policy of the UE associated with the second QFI. The specific description of this policy is the same as in the aforementioned embodiment and will not be repeated here.

[0290] It should be noted that steps 804 and 805 can be configured using the same message. That is, the control plane network element can send an N2 message containing a NAS message (which may carry a session reply) to the base station. When the base station receives the N2 message, it will pass the NAS message through to the UE.

[0291] Step 806: The UE transmits data in the user plane according to the configuration information, and marks the data packets corresponding to the specific second filter information transmitted in the user plane (i.e., the second data packets in the aforementioned embodiment) with the second QFI mark; correspondingly, for downlink data, the execution plane network element (such as UPF) can also mark the data packets corresponding to the specific second filter information with the second QFI mark according to the configuration information (i.e., the fourth configuration information).

[0292] In addition, the UE sends data to the network (such as one or more second execution nodes), and the network (one or more second execution nodes) processes the data using its computing resources and then sends the processed data back to the UE, forming a "round-trip". In this case, the first operation includes both uplink and downlink data transmission.

[0293] Based on Figure 8, and in conjunction with Figure 9, the migration process in the communication method is illustrated by example, including:

[0294] Step 901: The UE sends data on the user plane. Specifically, the UE binds the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) to the specific second QFI for transmission according to the second binding relationship.

[0295] In the scenario illustrated in Figure 9, one or more second execution nodes participating in the first operation may include: a base station, execution plane network element-1, and execution plane network element-2. That is, after the data or data packets related to the first operation are sent by the UE, they are processed by the base station, execution plane network element-1, and execution plane network element-2 based on their respective processing strategies and / or routing strategies.

[0296] Step 902: When the control plane network element needs to migrate the first operation to another execution plane network element (i.e., the control plane network element needs to migrate at least some of the operations or at least some of the related processes in the first operation from the original execution node to the new execution node), the control plane network element sends a downlink NAS message (such as a session modification command) to the UE, carrying new configuration information (i.e., the first configuration information in the aforementioned embodiment). The new configuration information may include at least one of the following: a first binding relationship (updated binding relationship), an operation descriptor, and condition information corresponding to the execution of the updated first binding relationship (i.e., the first condition in the aforementioned embodiment).

[0297] The updated first binding relationship can be to bind the original filter information to the new QFI. For example, it can be to keep the second filter information unchanged and bind the second filter information as the first filter information to the first QFI, where the first QFI is different from the second QFI.

[0298] Condition information may include at least one of the following: time, location, data transmission rate, etc.

[0299] Step 903: The control plane node sends new configuration information (i.e., the third configuration information in the aforementioned embodiments) to execution plane network elements-1 and-3. The new configuration information corresponding to each execution plane network element may include at least the execution policy (or operation descriptor) of the execution plane network element associated with the first QFI.

[0300] Step 904, Optionally, if condition information is configured for the UE, the UE starts monitoring whether the condition information is met. If the condition information is met, step 905 is executed; otherwise, the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) is continuously bound to the specific second QFI for transmission according to the second binding relationship, and the condition information is continuously monitored.

[0301] Alternatively, if no condition information is configured for the UE, the UE can immediately execute step 905; or, the UE can determine whether to execute step 905 based on its local configuration. For example, the UE may generate condition information locally. If the condition information is met, step 905 is executed. Otherwise, the UE continues to bind the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) to the specific second QFI for transmission according to the second binding relationship, and continuously monitors whether the condition information is met.

[0302] Step 905: The UE marks the data packet corresponding to the specific first filter information transmitted in the user plane (i.e., the first data packet in the aforementioned embodiment) with the first QFI and sends it according to the updated first binding relationship. Similarly, after the network side execution plane element-1 receives the data or data packet corresponding to the first QFI, it sends the data or data packet marked with the first QFI to the execution plane element-3 according to the configuration of the control plane element (i.e., the third configuration information).

[0303] In step 905, the base station can also perform the same processing. For example, after the base station receives the data or data packet corresponding to the new first QFI, it sends the data or data packet of the first QFI to the execution plane network element-1 according to the configuration of the control plane network element (i.e., the third configuration information). Then, after the network side execution plane network element-1 receives the data or data packet corresponding to the new first QFI, it sends the data or data packet of the first QFI to the execution plane network element-3 according to the configuration of the control plane network element (i.e., the third configuration information).

[0304] For execution plane network element-1, before step 903, execution plane network element-1 uses the operation descriptor (i.e., the execution strategy of the execution plane network element associated with the second QFI) contained in the original configuration information (i.e., the fourth configuration information in the aforementioned embodiment) to perform related processing (such as data processing and / or data transmission) on the received data or data packets. After completing step 903, execution plane network element-1 will obtain new configuration information (i.e., the third configuration information in the aforementioned embodiment). After completing step 903 and before executing step 905, since no data or data packets corresponding to the first QFI are received, execution plane network element-1 still uses the operation descriptor (i.e., the execution strategy of the execution plane network element associated with the second QFI) contained in the original configuration information to perform related processing on the received data or data packets. When execution plane network element-1 performs step 905, it will receive data or data packets corresponding to the first QFI. Therefore, it will enable the operation descriptor (i.e., the execution policy of the execution plane network element associated with the first QFI) contained in the new configuration information to process the received data or data packets. At this time, execution plane network element-1 may delete the execution policy of the execution plane network element associated with the second QFI, that is, replace or update the execution policy of the execution plane network element associated with the second QFI with the execution policy of the execution plane network element associated with the first QFI.

[0305] Here, for the UE, base station, and each execution plane network element, if their respective configuration information includes a processing policy, the data will be processed based on their respective processing policies before being sent.

[0306] In the scenarios illustrated in Figures 8 and 9, filter information is bound to QFI, and then data packets are identified through QFI. This enables each execution node to determine the associated processing strategy, thereby reducing the impact on the existing user plane protocol layer and eliminating the need to introduce new parameters into the existing user plane protocol layer.

[0307] Referring to Figures 10 and 11, another exemplary description of the communication method provided in this application is provided, including:

[0308] Steps 1001 to 1002 are the same as steps 801 and 802, and will not be repeated.

[0309] Step 1003: The control plane network element configures session parameters (such as PDU session parameters) to the execution plane network element (such as the user plane network element), which carries configuration information (i.e., the fourth configuration information corresponding to the execution plane network element). The configuration information corresponding to the execution plane network element may include the execution policy of the execution plane network element associated with the second ID.

[0310] The execution strategy of the execution plane element associated with the second ID may specifically include at least one of the following:

[0311] The processing strategy of the execution plane element associated with the second ID (or the operation corresponding to the execution plane element under the second ID) is used by the execution plane element to determine the processing of the data related to the first operation, such as the computing resources used, the model, and the input and / or output data.

[0312] The routing strategy of the execution plane network element associated with the second ID may include at least one of the following: the next-hop node (such as the node's address or node identifier) ​​through which the execution plane network element sends the data packet related to the first operation, and the previous-hop node (such as the node's address or node identifier) ​​through which the execution plane network element receives the data packet related to the first operation.

[0313] Optionally, the configuration information corresponding to the execution plane network element may also include a second binding relationship. The second binding relationship can be the correspondence between the second filter information (such as IP triples, quintuples, Application ID, DNN, domain name, etc.) and the second ID.

[0314] Step 1004: The control plane network element sends configuration information (i.e., the fourth configuration information corresponding to the base station) to the base station. The content of the configuration information corresponding to the base station is similar to that of the configuration information corresponding to the execution plane network element, and will not be repeated.

[0315] Step 1005: The control plane network element sends a session reply to the UE, which carries configuration information (i.e., the second configuration information in the aforementioned embodiment). The configuration information includes the second binding relationship. In addition, the configuration information sent to the UE may also include the execution policy of the UE associated with the second ID. The specific description of this is the same as in the aforementioned embodiment and will not be repeated.

[0316] Step 1006: The UE performs user plane data transmission according to the configuration information. Specifically, the UE marks the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) with a second ID at the existing protocol layer (such as SDAP or PDCP layer) and transmits it. The execution plane network element (such as UPF) can also mark the data packet corresponding to the specific second filter information with a second ID at the existing protocol layer (such as GTP-U or TCP / IP protocol layer) and transmit it according to the configuration information (i.e., the fourth configuration information).

[0317] Specifically, user plane data is tagged with a second ID using the SDAP or PDCP protocol layer at the air interface, and with the second ID using the GTP-U or TCP / IP protocol layer at the core network side. For example:

[0318] - Existing, extended, or new fields in the SDAP or PDCP header are used to identify the second ID;

[0319] - The extended field of the GTP-U header marks the second ID, or the Type of Service field of the TCP / IP header marks the second ID.

[0320] Based on Figure 10, and in conjunction with Figure 11, the migration process in the communication method is illustrated by example, including:

[0321] Step 1101: Send data in the user plane. Specifically, the UE, based on the second binding relationship, adds a second ID to the existing protocol layer of the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) and transmits it through the user plane.

[0322] In the scenario illustrated in Figure 11, one or more second execution nodes participating in the first operation may specifically include: a base station, execution plane network element-1, and execution plane network element-2. That is, after the relevant data or data packets of the first operation are sent by the UE, they are collaboratively processed by the base station, execution plane network element-1, and execution plane network element-2 based on their respective processing strategies and / or routing strategies.

[0323] Step 1102: When the control plane network element needs to migrate the computing services of the terminal to other execution plane network elements (i.e., the control plane network element needs to migrate at least some of the operations or at least some of the related processes in the first operation from the original execution node to the new execution node), the control plane network element sends a downlink NAS message (such as a session modification command) to the UE, carrying new configuration information (i.e., the first configuration information in the aforementioned embodiment). The new configuration information may include at least one of the following: a first binding relationship (updated binding relationship), an operation descriptor, and condition information corresponding to the execution of the updated first binding relationship (i.e., the first condition in the aforementioned embodiment).

[0324] The new configuration information includes a new ID parameter, which may include the mapping relationship between the second ID and the first ID (i.e., the mapping relationship between the old and new IDs). Alternatively, the new configuration information may include a first binding relationship, such as the binding relationship between the first filter information and the first ID.

[0325] Step 1103: The control plane node sends updated configuration information (i.e., the third configuration information in the aforementioned embodiments) to execution plane network elements-1 and-3. The new configuration information corresponding to each execution plane network element may at least include the execution policy (or operation descriptor) of the execution plane network element associated with the first ID.

[0326] Step 1104, Optionally, if condition information is configured for the UE, the UE starts monitoring whether the condition information is met. If the condition information is met, step 1105 is executed; otherwise, according to the second binding relationship, the existing protocol layer of the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) is tagged with the second ID and transmitted through the user plane, and the condition information is continuously monitored.

[0327] The specific description of step 1104 and its alternative descriptions are similar to those of step 904 in the aforementioned embodiments, and will not be repeated here.

[0328] Step 1105: Perform user plane data transmission. Specifically, the UE sends the data (or data packet) corresponding to the first filter information with the first ID marked on the existing protocol layer according to the first binding relationship. Similarly, after receiving the data or data packet corresponding to the first ID, the network side execution plane element-1 sends the data or data packet marked with the first ID to the execution plane element-3 according to the updated configuration information (i.e., the third configuration information).

[0329] In step 1105, the base station can also perform the same processing. For example, after the base station receives the data or data packet corresponding to the new first ID, it sends the data or data packet of the first ID to the execution plane network element-1 according to the configuration of the control plane network element (i.e., the third configuration information). Then, after the network side execution plane network element-1 receives the data or data packet corresponding to the new first QFI, it sends the data or data packet marked with the first ID to the execution plane network element-3 according to the configuration of the control plane network element (i.e., the third configuration information).

[0330] For execution plane element-1, before step 1103, execution plane element-1 uses the operation descriptor (i.e., the execution strategy of the execution plane element associated with the second ID) contained in the original configuration information (i.e., the fourth configuration information in the aforementioned embodiment) to perform related processing (such as data processing and / or data transmission) on the received data or data packets. After completing step 1103, execution plane element-1 will obtain new configuration information (i.e., the third configuration information in the aforementioned embodiment). After completing step 1103 and before executing step 1105, since no data or data packets corresponding to the first ID are received, execution plane element-1 still uses the operation descriptor (i.e., the execution strategy of the execution plane element associated with the second ID) contained in the original configuration information to perform related processing on the received data or data packets. When execution plane network element-1 performs step 1105, it will receive data or data packets corresponding to the first ID. Therefore, it will enable the operation descriptor contained in the new configuration information (i.e., the execution policy of the execution plane network element associated with the first ID) to process the received data or data packets. At this time, execution plane network element-1 may delete the execution policy of the execution plane network element associated with the second ID, that is, replace or update the execution policy of the execution plane network element associated with the second QFI with the execution policy of the execution plane network element associated with the first ID.

[0331] Referring to Figures 12 and 13, another exemplary description of the communication method provided in this application is provided, including:

[0332] Steps 1201 to 1205 are the same as steps 1001 to 1005 in the previous example, and will not be repeated here.

[0333] Step 1206: Data is transmitted in the user plane. Specifically, the UE marks the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) with a second ID at the QUIC protocol layer and transmits it according to the configuration information. The execution plane network element (such as UPF) can also mark the data packet corresponding to the specific second filter information with a second ID at the QUIC protocol layer and transmit it according to the configuration information (i.e., the fourth configuration information).

[0334] Based on Figure 12, and in conjunction with Figure 13, the migration process in the communication method is illustrated by example, including:

[0335] Step 1301: Transmit data in the user plane. Specifically, the UE, based on the second binding relationship, adds a second ID to the QUIC protocol layer of the data packet corresponding to the specific second filter information (i.e., the second data packet in the aforementioned embodiment) and transmits it through the user plane.

[0336] The detailed explanation of step 1301 is similar to that of step 1101 in the previous example. The only difference is that this example marks the second ID on the QUIC protocol layer, so it will not be explained again.

[0337] Steps 1302 to 1304 are the same as steps 1102 to 1104, and will not be repeated here.

[0338] Step 1305: Data is transmitted in the user plane. Specifically, the UE sends the data (or data packet) corresponding to the first filter information with the first ID marked on the QUIC protocol layer according to the first binding relationship. Similarly, after the network side execution plane element-1 receives the data or data packet corresponding to the new first ID, it sends the data or data packet marked with the first ID to the execution plane element-3 according to the configuration of the control plane element (i.e., the third configuration information).

[0339] In step 1305, the base station can also perform similar processing, which will not be elaborated here.

[0340] In some possible implementations, before the terminal receives the first configuration information from the control plane network element, the method further includes: the terminal sending a first indication to the control plane network element, wherein the first indication is used to indicate at least one of the following: the terminal supports or requests the network side to provide computing power services to the terminal, or the terminal has computing capabilities. Correspondingly, before sending the first configuration information, the control plane network element may include: receiving the first indication from the terminal.

[0341] The specific content of the first instruction is the same as in the previous embodiments and will not be repeated. The first instruction can be carried by a session request, and the relevant description of the session request carrying the first instruction is also the same as in the previous embodiments, so it will not be elaborated further.

[0342] Before sending the first configuration information to the terminal, the control plane network element may also include: the control plane network element determining one or more first execution nodes.

[0343] The one or more first execution nodes are used to collaboratively execute the first operation.

[0344] The control plane network element may determine the one or more first execution nodes by interacting with the computing power management network element. The relevant descriptions of the computing power management network element are the same as in the previous embodiments and will not be repeated.

[0345] The interaction between the control plane network element and the computing power management network element to determine the one or more first execution nodes may include: the control plane network element sending a query request to the computing power management network element; and the control plane network element receiving a query response from the computing power management network element, wherein the query response carries one or more first execution nodes. This embodiment does not limit the method by which the computing power management network element ultimately determines one or more first execution nodes from all the nodes it manages.

[0346] In one embodiment, after determining one or more first execution nodes, the control plane network element may send first configuration information to the terminal. Correspondingly, the terminal receives the first configuration information from the control plane network element.

[0347] The first configuration information may include a first binding relationship. The description of the first binding relationship is the same as in the previous embodiments and will not be repeated.

[0348] Optionally, the first configuration information may further include the execution policy of the terminal associated with the first identifier. The specific description of the execution policy of the terminal associated with the first identifier is the same as in the foregoing embodiments and will not be repeated here.

[0349] In this implementation, the first configuration information can be carried in a session response, which can be a session establishment response or a session modification response. For example, if the first indication is carried in a session establishment request, the first configuration information can be carried in a session establishment response, which can also be used to indicate the completion of establishing the first session; or, if the first indication is carried in a session modification request, the first configuration information can be carried in a session modification response, which can also be used to indicate the completion of modifying the first session.

[0350] Optionally, the control plane network element sends a session reply to the terminal, the session reply carrying the first configuration information.

[0351] Optionally, the control plane network element sends an N2 message to the access network device corresponding to the terminal. The N2 message carries a NAS message, which includes a session reply carrying the first configuration information. The access network device corresponding to the terminal then transparently transmits the NAS message to the terminal.

[0352] This transmission method is particularly suitable for scenarios where the access network device corresponding to the terminal also acts as a first execution node. For example, the control plane network element can send an N2 message to the access network device corresponding to the terminal. The N2 message carries the third configuration information and NAS message corresponding to the access network device corresponding to the terminal. The NAS message includes a session reply, which carries the first configuration information. Correspondingly, the access network device corresponding to the terminal can extract its own third configuration information from the N2 message and pass the NAS message through to the terminal.

[0353] It should be understood that this transmission method can also be applied to scenarios where the access network device corresponding to the terminal is not an arbitrary first execution node, and this is not limited here.

[0354] In addition, the session reply may also carry the configuration related to the first session as specified in the relevant protocol. Here, we will not limit the various contents that the session reply may carry.

[0355] In one embodiment, after determining one or more first execution nodes, the control plane network element can further perform the following processing: the control plane network element sends third configuration information corresponding to each of the one or more first execution nodes to each of the first execution nodes, wherein the third configuration information corresponding to each first execution node includes the execution strategy of each first execution node associated with the first identifier, and the execution strategy of each first execution node associated with the first identifier is used by each first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0356] Accordingly, for any first execution node, the first execution node receives third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0357] For any given first execution node, the description of the execution strategy associated with the first identifier is the same as in the foregoing embodiments, and will not be repeated.

[0358] In one embodiment, on the terminal side, after receiving the first configuration information from the control plane network element, the method further includes: the terminal determining the first identifier based on the first filter information and the first binding relationship when it determines that the data to be transmitted corresponds to the first filter information; the terminal sending a first data packet, wherein the first data packet is generated based on the data to be transmitted and carries the first identifier. The specific processing of the terminal side in sending the first data packet is the same as in the aforementioned embodiments and will not be described in detail.

[0359] Correspondingly, the processing after any first execution node receives the third configuration information also includes: the first execution node receiving the third data packet; and, if the third data packet carries the first identifier, the first execution node performing relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier. The description of the first execution node performing relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier is the same as in the foregoing embodiments and will not be repeated here.

[0360] By adopting the above scheme, the terminal obtains first configuration information from the control plane network element. Based on the first binding relationship determined by this first configuration information, the terminal can determine the first identifier that the data packet for the first operation needs to carry. This first identifier is used by each first execution node performing the first operation to identify the relevant data packet and perform related processing. In this way, an identifier can be added to the relevant data or data packet for an operation on the terminal side, enabling each first execution node to correctly perform the corresponding operation on the data packet by recognizing the identifier, ensuring that the relevant data for the same operation can be processed collaboratively by the nodes.

[0361] Furthermore, after receiving the second binding relationship corresponding to the first operation, the terminal may receive the first configuration information again. Based on this first configuration information, the terminal can determine a new first binding relationship. This first binding relationship allows the terminal to determine the first identifier required when at least some operations or related processes in the first operation are migrated to a new execution node. This first identifier may differ from the identifier in the second binding relationship. Thus, because the new first identifier is added to the data or data packets related to the first operation, in scenarios where a specified node is migrated, each first execution node can correctly perform the corresponding operation on the data packet by recognizing this identifier. This ensures that related data for the same operation can be processed collaboratively by the nodes, while also providing migration functionality for at least some operations or related processes within the operation.

[0362] Figure 14 is a schematic diagram of the composition structure of a terminal according to an embodiment of this application, including:

[0363] The first communication unit 1401 is configured to receive first configuration information from a control plane network element, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0364] The related processes include: data processing and / or data transmission.

[0365] The one or more first execution nodes are used to collaboratively execute the first operation.

[0366] The first binding relationship includes the binding relationship between the first filter information corresponding to the first operation and the first identifier.

[0367] The first communication unit is configured to receive second configuration information from the control plane network element, wherein the second configuration information includes a second binding relationship, the second binding relationship is used by the terminal to determine the second identifier carried by the data packet related to the first operation, and the second identifier is used by one or more second execution nodes to identify the data packet related to the first operation and perform related processing.

[0368] The one or more first execution nodes are at least partially different from the one or more second execution nodes.

[0369] The second binding relationship includes the binding relationship between the second filter information corresponding to the first operation and the second identifier.

[0370] The second filter information is different from the first filter information, and / or the second identifier is different from the first identifier.

[0371] When the second filter information is the same as the first filter information, the first configuration information includes a mapping relationship between the first identifier and the second identifier, wherein the mapping relationship between the first identifier and the second identifier is used by the terminal to determine the first binding relationship.

[0372] The first configuration information includes the first binding relationship.

[0373] As shown in Figure 14, the terminal also includes:

[0374] The first processing unit 1402 is configured to determine the first identifier based on the first filter information and the first binding relationship when it is determined that the data to be transmitted corresponds to the first filter information.

[0375] The first communication unit is configured to send a first data packet, wherein the first data packet is generated based on the data to be transmitted and carries the first identifier.

[0376] The first processing unit is configured to determine the first identifier based on the first filter information and the first binding relationship when a first condition is met and it is determined that the data to be transmitted corresponds to the first filter information, wherein the first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship.

[0377] The first configuration information further includes an execution policy of the terminal associated with the first identifier, the execution policy of the terminal associated with the first identifier including at least one of the following: a processing policy of the terminal associated with the first identifier, wherein the processing policy of the terminal associated with the first identifier is used by the terminal to determine the data processing to be performed on the data related to the first operation; a routing policy of the terminal associated with the first identifier, wherein the routing policy of the terminal associated with the first identifier is used to indicate at least one of the following: the next-hop node for the terminal to send the data packet related to the first operation, and the previous-hop node for the terminal to receive the data packet related to the first operation.

[0378] The first data packet is obtained by processing the data to be transmitted based on the processing strategy of the terminal associated with the first identifier.

[0379] The first communication unit is used to send the first data packet to the next-hop node, wherein the next-hop node is determined based on the routing policy of the terminal associated with the first identifier, and the next-hop node is one of the one or more first execution nodes.

[0380] The identifier is the Quality of Service Flow Identifier (QFI).

[0381] The first protocol layer of the first data packet carries the first identifier, wherein the first protocol layer includes one of the following: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and new protocol layer.

[0382] The new protocol layer includes the Fast User Datagram Protocol Internet Connection (QUIC) layer.

[0383] The first processing unit is configured to determine the second identifier based on the second filter information and the second binding relationship when the first condition is not met and it is determined that the data to be transmitted corresponds to the second filter information, wherein the first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship;

[0384] The first communication unit is configured to send a second data packet, wherein the second data packet is generated based on the data to be transmitted and carries the second identifier.

[0385] The first configuration information also includes the first condition.

[0386] The first communication unit is configured to send a first instruction to the control plane network element, wherein the first instruction is configured to indicate at least one of the following: the terminal supports or requests the network side to provide computing power services to the terminal, or the terminal has computing capabilities.

[0387] Figure 15 is a schematic diagram of the composition structure of a control plane network element according to an embodiment of this application, including:

[0388] The second communication unit 1501 is used to send first configuration information to the terminal, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

[0389] The related processes include: data processing and / or data transmission.

[0390] The one or more first execution nodes are used to collaboratively execute the first operation.

[0391] The first binding relationship includes the binding relationship between the first filter information corresponding to the first operation and the first identifier.

[0392] The second communication unit is used to send second configuration information to the terminal, wherein the second configuration information includes a second binding relationship, the second binding relationship is used by the terminal to determine a second identifier carried in the data packet related to the first operation, and the second identifier is used by one or more second execution nodes to determine the execution strategy of the data packet related to the first operation.

[0393] The one or more first execution nodes are at least partially different from the one or more second execution nodes.

[0394] The second binding relationship includes the binding relationship between the second filter information corresponding to the first operation and the second identifier.

[0395] The second filter information is different from the first filter information, and / or the second identifier is different from the first identifier.

[0396] When the second filter information is the same as the first filter information and the first identifier is different from the second identifier, the first configuration information includes a mapping relationship between the first identifier and the second identifier, wherein the mapping relationship between the first identifier and the second identifier is used by the terminal to determine the first binding relationship.

[0397] The first configuration information includes the first binding relationship.

[0398] The first configuration information further includes an execution policy of the terminal associated with the first identifier, the execution policy of the terminal associated with the first identifier including at least one of the following: a processing policy of the terminal associated with the first identifier, wherein the processing policy of the terminal associated with the first identifier is used by the terminal to determine the data processing to be performed on the data related to the first operation; a routing policy of the terminal associated with the first identifier, wherein the routing policy of the terminal associated with the first identifier is used to indicate at least one of the following: the next-hop node for the terminal to send the data packet related to the first operation, and the previous-hop node for the terminal to receive the data packet related to the first operation.

[0399] The first configuration information further includes a first condition, wherein the first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship.

[0400] The second communication unit is configured to receive a first indication from the terminal, wherein the first indication is configured to indicate at least one of the following: the terminal supports or requests the network side to provide computing power services to the terminal, or the terminal has computing capabilities.

[0401] The second communication unit is configured to send third configuration information corresponding to each of the one or more first execution nodes to each of the first execution nodes, wherein the third configuration information corresponding to each of the first execution nodes includes the execution strategy of each of the first execution nodes associated with the first identifier, and the execution strategy of each of the first execution nodes associated with the first identifier is used by each of the first execution nodes to determine the relevant processing for coordinating the execution of the first operation.

[0402] The execution strategy of each first execution node associated with the first identifier includes at least one of the following: a processing strategy of each first execution node associated with the first identifier, wherein the processing strategy of each first execution node associated with the first identifier is used for each first execution node to determine the processing to be performed on the data related to the first operation; a routing strategy of each first execution node associated with the first identifier, wherein the routing strategy of each first execution node associated with the first identifier is used to indicate at least one of the following: the next-hop node for each first execution node to send the data packet related to the first operation, and the previous-hop node for each first execution node to receive the data packet related to the first operation.

[0403] The identifier is the Quality of Service Flow Identifier (QFI).

[0404] Figure 16 is a schematic diagram of the composition structure of a first execution node according to an embodiment of this application, including:

[0405] The third communication unit 1601 is used to receive third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

[0406] The related processes include: data processing and / or data transmission.

[0407] The execution strategy of the first execution node associated with the first identifier includes at least one of the following: a processing strategy of the first execution node associated with the first identifier, wherein the processing strategy of the first execution node associated with the first identifier is used by the first execution node to determine the data processing to be performed on the data related to the first operation; a routing strategy of the first execution node associated with the first identifier, wherein the routing strategy of the first execution node associated with the first identifier is used to indicate at least one of the following: the next-hop node for the first execution node to send the data packet related to the first operation, and the previous-hop node for the first execution node to receive the data packet related to the first operation.

[0408] As shown in Figure 16, the first execution node further includes:

[0409] The third processing unit 1602 is configured to, when the third data packet carries the first identifier, have the first execution node perform relevant processing on the third data packet based on the execution strategy of the first execution node associated with the first identifier;

[0410] The third communication unit is used to receive the third data packet.

[0411] The third processing unit is used to process the data in the third data packet based on the processing strategy of the first execution node associated with the first identifier, so as to obtain the processed data.

[0412] The third communication unit is configured to send a fourth data packet to the next-hop node when the routing policy of the first execution node associated with the first identifier determines that there is a next-hop node, wherein the fourth data packet carries the first identifier and the processed data.

[0413] The third communication unit is configured to send a fourth data packet to the next-hop node when the routing policy of the first execution node associated with the first identifier determines that there is a next-hop node, wherein the fourth data packet carries the first identifier and the data in the third data packet.

[0414] The identifier is QFI.

[0415] The first protocol layer of the third data packet carries the first identifier, wherein the first protocol layer includes one of the following: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and new protocol layer.

[0416] The second protocol layer of the third data packet carries the first identifier, wherein the second protocol layer includes one of the following: General Packet Radio Service-User Plane Tunneling Protocol GTP-U layer, Transmission Control Protocol / Internet Protocol TCP / IP layer, and new protocol layer.

[0417] The new protocol layer includes the Fast User Datagram Protocol Internet Connection (QUIC) layer.

[0418] The device in this application embodiment can realize the corresponding functions of the various devices in the foregoing communication method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in this device can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the device of this application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0419] Figure 17 is a schematic structural diagram of a communication device 1700 according to an embodiment of this application. The communication device 1700 includes a processor 1710, which can call and run computer programs from a memory to enable the communication device 1700 to implement the methods in the embodiments of this application. In one possible implementation, the communication device 1700 may further include a memory 1720. The processor 1710 can call and run computer programs from the memory 1720 to enable the communication device 1700 to implement the methods in the embodiments of this application. The memory 1720 may be a separate device independent of the processor 1710, or it may be integrated into the processor 1710. In one possible implementation, the communication device 1700 may further include a transceiver 1730, which the processor 1710 can control to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices. The transceiver 1730 may include a transmitter and a receiver. The transceiver 1730 may further include antennas, and the number of antennas may be one or more.

[0420] In one possible implementation, the communication device 1700 may be a terminal, a control plane network element, or a first execution node in the embodiments of this application, and the communication device 1700 may implement the corresponding processes implemented by the terminal, the control plane network element, or the first execution node in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0421] Figure 18 is a schematic structural diagram of a chip 1800 according to an embodiment of this application. The chip 1800 includes a processor 1810, which can call and run computer programs from memory to implement the methods in the embodiments of this application. In one possible implementation, the chip 1800 may further include a memory 1820. The processor 1810 can call and run computer programs from the memory 1820 to implement the methods executed by a terminal, control plane network element, or second core network device in the embodiments of this application. The memory 1820 may be a separate device independent of the processor 1810, or it may be integrated into the processor 1810. In one possible implementation, the chip 1800 may further include an input interface 1830. The processor 1810 can control the input interface 1830 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips. In one possible implementation, the chip 1800 may further include an output interface 1840. The processor 1810 can control the output interface 1840 to communicate with other devices or chips, specifically, it can output information or data to other devices or chips.

[0422] In one possible implementation, the chip can be applied to the terminal, control plane network element, or first execution node in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal, control plane network element, or first execution node in the various methods of the embodiments of this application. For simplicity, further details are omitted here. It should be understood that the chip mentioned in the embodiments of this application can also be called a system-on-a-chip, system-on-a-chip, chip system, or system-on-chip, etc. The processor mentioned above can be a general-purpose processor, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or other programmable logic device, transistor logic device, discrete hardware component, etc. Among them, the general-purpose processor mentioned above can be a microprocessor or any conventional processor, etc. The memory mentioned above can be volatile memory or non-volatile memory, or can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM). It should be understood that the above-described memory is exemplary but not limiting. For example, the memory in the embodiments of this application can also be 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 memory bus RAM (DR RAM), etc. In other words, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0423] Figure 19 is a schematic block diagram of a communication system 1900 according to an embodiment of this application. The communication system 1900 includes a terminal 1910, a control plane network element 1920, and a first execution node 1930. The terminal 1910 can be used to implement the corresponding functions implemented by the terminal in the above-described method. The control plane network element 1920 can be used to implement the corresponding functions implemented by the control plane network element in the above-described method. The first execution node 1930 can be used to implement the corresponding functions implemented by the first execution node in the above-described method. For simplicity, further details are omitted here.

[0424] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0425] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. The above descriptions are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, comprising: The terminal receives first configuration information from a control plane network element, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

2. The method of claim 1, wherein, The related processes include: data processing and / or data transmission.

3. The method of claim 1 or 2, wherein, The one or more first execution nodes are used to collaboratively execute the first operation.

4. The method according to any one of claims 1 to 3, wherein, The first binding relationship includes the binding relationship between the first filter information corresponding to the first operation and the first identifier.

5. The method of claim 4, wherein, Before the terminal receives the first configuration information from the control plane network element, it also includes: The terminal receives second configuration information from the control plane network element, wherein the second configuration information includes a second binding relationship. The second binding relationship is used by the terminal to determine the second identifier carried by the data packet related to the first operation. The second identifier is used by one or more second execution nodes to identify the data packet related to the first operation and perform related processing.

6. The method of claim 5, wherein, The one or more first execution nodes are at least partially different from the one or more second execution nodes.

7. The method of claim 5 or 6, wherein, The second binding relationship includes the binding relationship between the second filter information corresponding to the first operation and the second identifier.

8. The method of claim 7, wherein, The second filter information is different from the first filter information, and / or the second identifier is different from the first identifier.

9. The method of claim 7, wherein, When the second filter information is the same as the first filter information, the first configuration information includes a mapping relationship between the first identifier and the second identifier, wherein the mapping relationship between the first identifier and the second identifier is used by the terminal to determine the first binding relationship.

10. The method of any one of claims 1-8, wherein, The first configuration information includes the first binding relationship.

11. The method of any one of claims 1-10, wherein, After receiving the first configuration information from the control plane network element, the terminal further includes: When the terminal determines that the data to be transmitted corresponds to the first filter information, it determines the first identifier based on the first filter information and the first binding relationship. The terminal sends a first data packet, wherein the first data packet is generated based on the data to be transmitted and carries the first identifier.

12. The method of claim 11, wherein, When the terminal determines that the data to be transmitted corresponds to the first filter information, it determines the first identifier based on the first filter information and the first binding relationship, including: When the terminal satisfies the first condition and determines that the data to be transmitted corresponds to the first filter information, it determines the first identifier based on the first filter information and the first binding relationship. The first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship.

13. The method of claim 11 or 12, wherein, The first configuration information also includes the execution policy of the terminal associated with the first identifier, and the execution policy of the terminal associated with the first identifier includes at least one of the following: The processing strategy of the terminal associated with the first identifier, wherein the data processing strategy of the terminal associated with the first identifier is used by the terminal to determine the data processing to be performed on the data related to the first operation; The routing policy of the terminal associated with the first identifier, wherein the routing policy of the terminal associated with the first identifier is used to indicate at least one of the following: the next-hop node where the terminal sends the data packet related to the first operation, and the previous-hop node where the terminal receives the data packet related to the first operation.

14. The method of claim 13, wherein, The first data packet is obtained by processing the data to be transmitted based on the processing strategy of the terminal associated with the first identifier.

15. The method of claim 13 or 14, wherein, The terminal sends a first data packet, including: The terminal sends the first data packet to the next-hop node, wherein the next-hop node is determined based on the routing policy of the terminal associated with the first identifier, and the next-hop node is one of the one or more first execution nodes.

16. The method of any one of claims 1-15, wherein, The identifier is the Quality of Service Flow Identifier (QFI).

17. The method of any one of claims 11-15, wherein, The first protocol layer of the first data packet carries the first identifier, wherein the first protocol layer includes one of the following: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and new protocol layer.

18. The method of claim 17, wherein, The new protocol layer includes the Fast User Datagram Protocol Internet Connection (QUIC) layer.

19. The method of claim 7 or 8, wherein, After receiving the first configuration information from the control plane network element, the terminal further includes: If the terminal does not meet the first condition and determines that the data to be transmitted corresponds to the second filter information, it determines the second identifier based on the second filter information and the second binding relationship. The first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship. The terminal sends a second data packet, wherein the second data packet is generated based on the data to be transmitted and carries the second identifier.

20. The method of claim 12 or 19, wherein, The first configuration information also includes the first condition.

21. The method of any one of claims 1-20, wherein, The method further includes: The terminal sends a first instruction to the control plane network element, wherein the first instruction is used to indicate at least one of the following: the terminal supports or requests the network side to provide computing power services to the terminal, or the terminal has computing capabilities.

22. A communication method, comprising: The control plane network element sends first configuration information to the terminal, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

23. The method of claim 22, wherein, The related processes include: data processing and / or data transmission.

24. The method of claim 22 or 23, wherein, The one or more first execution nodes are used to collaboratively execute the first operation.

25. The method of any one of claims 22-24, wherein, The first binding relationship includes the binding relationship between the first filter information corresponding to the first operation and the first identifier.

26. The method of claim 25, wherein, Before the control plane network element sends the first configuration information to the terminal, it also includes: The control plane network element sends second configuration information to the terminal, wherein the second configuration information includes a second binding relationship. The second binding relationship is used by the terminal to determine the second identifier carried in the data packet related to the first operation. The second identifier is used by one or more second execution nodes to determine the data packet related to the first operation and perform related processing.

27. The method of claim 26, wherein, The one or more first execution nodes are at least partially different from the one or more second execution nodes.

28. The method of claim 26 or 27, wherein, The second binding relationship includes the binding relationship between the second filter information corresponding to the first operation and the second identifier.

29. The method of claim 28, wherein, The second filter information is different from the first filter information, and / or the second identifier is different from the first identifier.

30. The method of claim 28, wherein, When the second filter information is the same as the first filter information, the first configuration information includes a mapping relationship between the first identifier and the second identifier, wherein the mapping relationship between the first identifier and the second identifier is used by the terminal to determine the first binding relationship.

31. The method of any one of claims 22-29, wherein, The first configuration information includes the first binding relationship.

32. The method of any one of claims 22-31, wherein, The first configuration information also includes the execution policy of the terminal associated with the first identifier, and the execution policy of the terminal associated with the first identifier includes at least one of the following: The processing strategy of the terminal associated with the first identifier, wherein the processing strategy of the terminal associated with the first identifier is used by the terminal to determine the data processing to be performed on the data related to the first operation; The routing policy of the terminal associated with the first identifier, wherein the routing policy of the terminal associated with the first identifier is used to indicate at least one of the following: the next-hop node where the terminal sends the data packet related to the first operation, and the previous-hop node where the terminal receives the data packet related to the first operation.

33. The method of any one of claims 22-32, wherein, The first configuration information further includes a first condition, wherein the first condition includes at least one of the following: the activation time of the first binding relationship, the activation area of ​​the first binding relationship, and the data transmission requirements corresponding to the first binding relationship.

34. The method of any one of claims 22-33, wherein, The method further includes: The control plane network element receives a first instruction from the terminal, wherein the first instruction is used to indicate at least one of the following: the terminal supports or requests the network side to provide computing power services to the terminal, or the terminal has computing capabilities.

35. The method of any one of claims 22-34, wherein, The method further includes: The control plane network element sends third configuration information corresponding to each of the one or more first execution nodes to each of the first execution nodes. The third configuration information corresponding to each of the first execution nodes includes the execution strategy of each of the first execution nodes associated with the first identifier. The execution strategy of each of the first execution nodes associated with the first identifier is used by each of the first execution nodes to determine the relevant processing for coordinating the execution of the first operation.

36. The method of claim 35, wherein, The execution strategy of each first execution node associated with the first identifier includes at least one of the following: The processing strategy of each first execution node associated with the first identifier, wherein the processing strategy of each first execution node associated with the first identifier is used by each first execution node to determine the data processing to be performed on the data related to the first operation; The routing policy of each first execution node associated with the first identifier, wherein the routing policy of each first execution node associated with the first identifier is used to indicate at least one of the following: the next-hop node for each first execution node to send the data packet related to the first operation, and the previous-hop node for each first execution node to receive the data packet related to the first operation.

37. The method of any one of claims 22-36, wherein, The identifier is the Quality of Service Flow Identifier (QFI).

38. A communication method, comprising: The first execution node receives third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

39. The method of claim 38, wherein, The related processes include: data processing and / or data transmission.

40. The method of claim 39, wherein, The execution strategy of the first execution node associated with the first identifier includes at least one of the following: The processing strategy of the first execution node associated with the first identifier, wherein the processing strategy of the first execution node associated with the first identifier is used by the first execution node to determine the data processing to be performed on the data related to the first operation; The routing policy of the first execution node associated with the first identifier, wherein the routing policy of the first execution node associated with the first identifier is used to indicate at least one of the following: the next-hop node where the first execution node sends the data packet related to the first operation, and the previous-hop node where the first execution node receives the data packet related to the first operation.

41. The method of claim 40, wherein, After the first execution node receives the third configuration information from the control plane network element, it also includes: The first execution node receives the third data packet; When the third data packet carries the first identifier, the first execution node performs relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier.

42. The method of claim 41, wherein, The first execution node performs relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier, including: The first execution node processes the data in the third data packet based on the processing strategy of the first execution node associated with the first identifier, and obtains the processed data; If the routing policy of the first execution node associated with the first identifier determines that there is a next-hop node, the first execution node sends a fourth data packet to the next-hop node, wherein the fourth data packet carries the first identifier and the processed data.

43. The method of claim 41, wherein, The first execution node performs relevant processing on the third data packet based on the execution policy of the first execution node associated with the first identifier, including: If the routing policy of the first execution node associated with the first identifier determines that there is a next-hop node, the first execution node sends a fourth data packet to the next-hop node, wherein the fourth data packet carries the first identifier and the data in the third data packet.

44. The method of any one of claims 41-43, wherein, The identifier is QFI.

45. The method of any one of claims 41-43, wherein, The first protocol layer of the third data packet carries the first identifier, wherein the first protocol layer includes one of the following: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and new protocol layer.

46. The method of any one of claims 41-43, wherein, The second protocol layer of the third data packet carries the first identifier, wherein the second protocol layer includes one of the following: General Packet Radio Service-User Plane Tunneling Protocol GTP-U layer, Transmission Control Protocol / Internet Protocol TCP / IP layer, and new protocol layer.

47. The method of claim 45 or 46, wherein, The new protocol layer includes the Fast User Datagram Protocol Internet Connection (QUIC) layer.

48. A terminal, comprising: The first communication unit is configured to receive first configuration information from a control plane network element, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

49. A control plane network element, comprising: The second communication unit is used to send first configuration information to the terminal, wherein the first configuration information is used by the terminal to determine a first binding relationship, the first binding relationship is used to determine a first identifier carried by a data packet related to a first operation, and the first identifier is used by one or more first execution nodes to identify the data packet related to the first operation and perform related processing.

50. A first execution node, comprising: The third communication unit is used to receive third configuration information from the control plane network element, wherein the third configuration information includes the execution strategy of the first execution node associated with the first identifier, and the execution strategy of the first execution node associated with the first identifier is used by the first execution node to determine the relevant processing for coordinating the execution of the first operation.

51. A terminal comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the terminal to perform the method as described in any one of claims 1 to 21.

52. A control plane network element comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the control plane network element to perform the method as described in any one of claims 22 to 37.

53. A first execution node, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the first execution node to perform the method as described in any one of claims 38 to 47.

54. A chip comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as described in any one of claims 1 to 21, or claims 22 to 37, or claims 38 to 47.

55. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as claimed in any one of claims 1 to 21, or claims 22 to 37, or claims 38 to 47.

56. A computer program product comprising computer program instructions that cause a computer to perform the method as claimed in any one of claims 1 to 21, or claims 22 to 37, or claims 38 to 47.

57. A computer program that causes a computer to perform the method as claimed in any one of claims 1 to 21, or claims 22 to 37, or claims 38 to 47.

Images