Identifier mapping method, and device

Abstract

The present application relates to an identifier mapping method, and a device. The method comprises: a first data control node receiving identifier mapping information of a first data pipeline from a second data control node, wherein the first data control node belongs to a first domain, the second data control node belongs to a second domain, and the identifier mapping information of the first data pipeline comprises a mapping relationship between an identifier of the first data pipeline in the first domain and an identifier of the first data pipeline in the second domain; and the first data control node sending the identifier mapping information of the first data pipeline to one or a plurality of first participant nodes of the first data pipeline in the first domain.

Description

Identification mapping methods and devices Technical Field

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

[0002] With technological advancements, increasingly sophisticated demands for data processing and acquisition have emerged. Under existing network architectures, data acquisition remains challenging, and data quality is difficult to guarantee. This has led to the concept of data pipelines, where multiple devices or nodes can collaborate to complete the same data processing task. However, as technology evolves, future nodes in a data pipeline may not belong to the same domain. In such scenarios, ensuring collaborative work between nodes from different domains within the same data pipeline while maintaining policy security and privacy for each node in each domain becomes a critical challenge. Summary of the Invention

[0003] This application provides an identifier mapping method and device.

[0004] This application provides an identifier mapping method, including:

[0005] The first data control node receives the identifier mapping information of the first data pipeline from the second data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0006] The first data control node sends the identification mapping information of the first data pipeline to one or more first participating nodes in the first domain.

[0007] This application provides an identifier mapping method, including:

[0008] The first participating node receives the identifier mapping information of the first data pipeline from the first data control node. The identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. The first participating node is a participating node of the first data pipeline in the first domain, and the first data control node belongs to the first domain.

[0009] This application provides an identifier mapping method, including:

[0010] The second data control node sends the identifier mapping information of the first data pipeline to the first data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0011] The second data control node sends the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain.

[0012] This application provides an identifier mapping method, including:

[0013] The terminal sends the identifier of the first data pipeline in the first domain to the second data control node, wherein the second data control node belongs to the second domain and the terminal belongs to the first domain;

[0014] The terminal receives identification mapping information of the first data pipeline from the second data control node, wherein the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0015] This application provides an identifier mapping method, including:

[0016] The terminal receives the identifier of the first data pipeline in the first domain from the first data control node, wherein the terminal belongs to the second domain and the first data plane control point belongs to the first domain;

[0017] The terminal sends the identifier mapping information of the first data pipeline to the first data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0018] This application provides a first data control node, including:

[0019] The first communication unit is configured to receive identification mapping information of a first data pipe from a second data control node, wherein the first data control node belongs to a first domain and the second data control node belongs to a second domain, and the identification mapping information of the first data pipe includes the mapping relationship between the identifier of the first data pipe in the first domain and the identifier of the first data pipe in the second domain; and to send the identification mapping information of the first data pipe to one or more first participating nodes of the first data pipe in the first domain.

[0020] This application provides a first participating node, including:

[0021] The second communication unit is used to receive the identification mapping information of the first data pipeline from the first data control node, wherein the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain, the first participating node is the participating node of the first data pipeline in the first domain, and the first data control node belongs to the first domain.

[0022] This application provides a second data control node, including:

[0023] The third communication unit is used to send the identification mapping information of the first data pipeline to the first data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain; and to send the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain.

[0024] This application provides a terminal, including:

[0025] The fourth communication unit is configured to send the identifier of the first data pipeline in the first domain to the second data control node, wherein the second data control node belongs to the second domain and the terminal belongs to the first domain; and to receive the identifier mapping information of the first data pipeline from the second data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0026] This application provides a terminal, including:

[0027] The fourth communication unit is configured to receive the identifier of the first data pipeline in the first domain from the first data control node, wherein the terminal belongs to the second domain and the first data plane control point belongs to the first domain; and to send the identifier mapping information of the first data pipeline to the first data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0028] This application provides a first data control 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 data control node to perform the methods described above.

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

[0030] This application provides a second data control 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 second data control node to perform the methods described above.

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

[0032] This application provides a chip for implementing the above-described method. Specifically, the chip includes a processor for retrieving and running a computer program from a memory, causing a device equipped with the chip to perform the above-described method.

[0033] By adopting the above scheme, when the first data pipeline spans different domains, the data control node of the first domain receives the identifier mapping information of the first data pipeline from the data control node of the second domain. This identifier mapping information includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. Then, the data control node of the first domain can send the identifier mapping information of the first data pipeline to the participating nodes within the first domain. In this way, in the scenario where the first data pipeline spans multiple domains, the uniqueness of the identifier of the first data pipeline within each domain can be guaranteed, thereby avoiding the problem of participating nodes from other domains obtaining relevant policies of their own domain. This ensures inter-domain isolation and guarantees the security and privacy of the policies of participating nodes in different domains. Furthermore, since participating nodes in different domains can know the mapping relationship of the identifier of the same data pipeline in different domains, it can be guaranteed that participating nodes in different domains of the same data pipeline can work collaboratively. Attached Figure Description

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

[0035] Figure 2 is a schematic flowchart of an identifier mapping method according to an embodiment of this application.

[0036] Figure 3 is a schematic flowchart of an identifier mapping method according to another embodiment of this application.

[0037] Figure 4 is a schematic flowchart of an identifier mapping method according to another embodiment of this application.

[0038] Figure 5 is a schematic diagram of a network architecture including a data plane according to an embodiment of this application.

[0039] Figure 6 is a schematic diagram of a data pipeline according to an embodiment of this application.

[0040] Figure 7 is a schematic diagram of the composition of the DPID of the first data pipeline in the first domain according to an embodiment of the present application.

[0041] Figure 8 is a schematic diagram of a scene of a QUIC frame according to an embodiment of this application.

[0042] Figure 9 is a schematic diagram of the DPID field carried in the stream identifier field of a QUIC frame according to an embodiment of this application.

[0043] Figure 10 is a schematic flowchart of an identifier mapping method according to an embodiment of this application.

[0044] Figure 11 is another schematic flowchart of an identifier mapping method according to an embodiment of this application.

[0045] Figures 12 and 13 are schematic flowcharts illustrating two methods for performing identification mapping processing on the previous hop participating node and the next hop participating node of adjacent domains in a first data pipeline, according to an embodiment of this application.

[0046] Figure 14 is a schematic flowchart of an identifier mapping method according to another embodiment of this application.

[0047] Figure 15 is a schematic block diagram of a first data control node according to an embodiment of the present application.

[0048] Figure 16 is a schematic block diagram of a first participating node according to an embodiment of this application.

[0049] Figure 17 is a schematic block diagram of a second data control node according to an embodiment of the present application.

[0050] Figure 18 is a schematic block diagram of an end view according to an embodiment of the present application.

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

[0052] Figure 20 is a schematic block diagram of a chip according to an embodiment of this application. Detailed Implementation

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

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

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

[0056] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies and basic concepts involved in the embodiments of this application are described below. The following related 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.

[0057] 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 first core network devices. 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.

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

[0059] S210, The first data control node receives the identifier mapping information of the first data pipe from the second data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identifier mapping information of the first data pipe includes the mapping relationship between the identifier of the first data pipe in the first domain and the identifier of the first data pipe in the second domain.

[0060] S220, the first data control node sends the identification mapping information of the first data pipeline to one or more first participating nodes in the first domain.

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

[0062] S310, The first participating node receives the identifier mapping information of the first data pipeline from the first data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain, the first participating node is the participating node of the first data pipeline in the first domain, and the first data control node belongs to the first domain.

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

[0064] S410, the second data control node sends the identifier mapping information of the first data pipeline to the first data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0065] S420, the second data control node sends the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain.

[0066] In this embodiment, the data control node can serve as an interface between network data and the DP (Data Plane) infrastructure. The data control node can also be referred to as any one of the following: DPAC (Data Plane Access Controller), data plane control node, data plane management network element, data plane interface, data plane control network element, data plane function, or data plane management function.

[0067] The data plane can be the core network's data plane. The data plane supports trusted data collection, data storage, data access, and data sharing. Data elements within the data plane will encompass both internal and external network data, specifically including business data, user data, network data, sensing data, and external data. The basic data services provided by the data plane include data acquisition, data preprocessing, data storage, data access, data sharing, and collaboration. These basic data services have the following technical characteristics: support for trusted authentication, authorization, and access; efficient data storage and management; on-demand data acquisition and preprocessing; and external data accessibility.

[0068] The main functions of a data control node may include at least one of the following: data collection; management and verification of data source and data consumer IDs (identifiers); data processing and data sharing; interaction with data plane storage facilities to store data in or retrieve data from the data plane storage facilities; data services provided between the data source or data consumer and the data control node, such as data storage, data retrieval, and data collection; and support for data tracking. For example, the processing of a data transaction or data service between a UE (User Equipment) as a data source and the core network's data plane may include: the UE sending a data transaction request to the data control node, the data transaction request carrying the data source ID, the source data itself, and data description information; after receiving the data transaction request from the UE, the data control node verifies the data source ID in the data transaction request, and if the verification is successful, sends the data source ID, the source data itself, and the data description information to the data plane storage facility.

[0069] The functions supported by the data control node can be implemented by enhancing the existing DCCF (Data Collection Coordination Function) or by adding a new network element or node; this application does not limit them.

[0070] Referring to Figure 5, an exemplary network architecture including a data plane is illustrated. This network architecture comprises three parts: the user plane, the control plane, and the data plane. The data plane includes DPAC, Data Plane Repository Infrastructure, etc.; the user plane may include UE, (R)AN (access network), UPF (User Plane Function), DN (data network), etc.; the control plane may include multiple control plane functions or multiple control plane network elements, such as AMF (Access and Mobility Management Function), SMF (Session Management Function), PCF (Policy Control Function), NRF (Network Repository Function), NEF (Network Exposure Function), AF (Application Function), UDM (Unified Data Management), NSSF (Network Slice Selection Function), NWDAF (Network Data Analytics Function), and AUSF (Authentication Server), as shown in Figure 5. Functions such as authentication server functions, etc., are required. It should be noted that, to support flexible and efficient data management, the data plane is a distributed architecture; therefore, data sources can reduce data transmission latency by selecting a data plane that is closer to them for access.

[0071] A data pipeline consists of multiple participating nodes that collaborate to complete a data-related processing task or business process. Any participating node can be referred to as a participant, contributor, or contributing node, etc. The data output of one participating node becomes the input of subsequent participating nodes, allowing for a smooth and automated workflow throughout the pipeline. The operation of a data pipeline is similar to an assembly line in manufacturing; it simplifies data management processes, improves data processing efficiency, and ensures data integrity.

[0072] Referring to Figure 6, the establishment of the data pipeline, the selection of participating nodes (or participants or contributors) within the entire data pipeline, the data processing strategies corresponding to each participating node, and the data routing topology are all managed by the data control node. The multiple participating nodes in the data pipeline can be categorized into the following types: data source, general pipeline participant, and data receiver. A participating node acting as a data source can be the starting point of the data pipeline, capable of collecting raw data. A data pipeline can include one or more data sources to achieve diverse data services. For example, in Figure 6, contributor #A and contributor #C are two data sources for the data pipeline. Participating nodes acting as general pipeline participants (such as contributor #X and contributor #Y in Figure 6) can receive data from the previous participating node, process the data, and then send the processed results to the next participating node. When the previous participating node is a data source, its data is the raw data; when the previous participating node is a general pipeline participant, its data is the data processed by the previous participating node. The participating node acting as a data receiver (such as contributor #B in the data pipeline in Figure 6) is the endpoint of the data pipeline. This node receives the final processed data and does not perform any further processing. Data pipelines can handle different types of data, such as continuous, intermittent, and batch data. In general, a data pipeline is a combination of the following series of data processing steps: data is collected from the data source, sent by the data source to the next participating node, processed by that node, and forwarded to the next participating node, and so on, thus achieving data processing along the way.

[0073] Each participating node in the data pipeline can determine the processing method to be used when participating in the execution of the data-related processing tasks corresponding to that data pipeline, based on a data policy. The data policy for each participating node can be pre-configured, for example, by the data control node. The data policy can include at least one of the following: data pipeline policy, routing information, etc. The data pipeline policy of each participating node can be used to determine the data processing method to be used when participating in the execution of the data-related processing tasks corresponding to that data pipeline. The data processing method can include at least one of the following: compression, normalization, AI model-based data processing, etc. For example, this data pipeline policy can also be called a data processing policy or a data operation policy, etc., which will not be explained again below. The routing information of each participating node can be used to determine the previous hop participating node and / or the next hop participating node when participating in the execution of the data-related processing tasks corresponding to that data pipeline. For example, this routing information can also be called a routing policy.

[0074] A data pipeline identifier can uniquely identify or identify a data pipeline and is associated with that data pipeline's data policy. The data pipeline identifier is used by each participating node in the data pipeline to determine the data policy to be used when participating in the execution of the data-related processing tasks corresponding to that data pipeline.

[0075] The architecture of a data pipeline can be divided into the control part and the execution part.

[0076] The control part of the data pipeline is mainly based on the data control node. The main functions of the data control node in the data pipeline architecture are as follows: receiving business requests sent by the business requester, interacting with other network elements and collecting information based on the business requirements in the request, and determining the appropriate participants in the data pipeline; determining the data pipeline configuration strategy / rules, which may include at least one of the data processing strategy, routing strategy, etc. of each node; assigning the data pipeline identifier (ID), and establishing and maintaining the data pipeline.

[0077] The execution portion of a data pipeline is the data pipeline itself, and the data is transmitted within the data pipeline (the participating nodes). Data pipelines support the following functions: participating nodes within the same data pipeline are configured with the same data pipeline ID; each participating node in the data pipeline parses and processes the data, enabling data processing along the path and flexible routing. It should be noted that there can be multiple data execution paths within a single data pipeline. That is, to support the high reliability and real-time requirements of certain business operations, multiple candidate paths can be established for data execution. Thus, for each participating node, multiple candidate nodes can be identified. When a node cannot meet business requirements due to load, link quality, or other reasons, it can be switched to another path in a timely manner, ensuring the real-time performance and reliability of the data.

[0078] A data pipeline may exist across domains, meaning it can consist of one or more participating nodes within each of multiple domains, and the participating nodes differ across domains. Each of the multiple domains may include one or more devices (or nodes), and different domains may include different devices or nodes. A participating node in any domain can be at least a portion of the devices or nodes included in that domain.

[0079] There are multiple ways to divide a domain.

[0080] For example, domains can be divided based on devices or device types. For instance, nodes or devices of different device types can be divided into different domains. This means that UE, RAN (Radio Access Network) (or RAN access network devices), CN (Core Network) (or core network devices within the CN), OAM (Operation, Administration and Maintenance), and Application (or AF (Application Function)) can be divided into different domains. For example, one or more terminals can be divided into the same domain, multiple access network devices on the access network side can be divided into the same domain, multiple core network devices on the core network side can be divided into the same domain, and so on. Here, one or more terminals may be divided into the same domain, or a single terminal may be divided into a single domain (i.e., different terminals may be divided into different domains). This is not a limitation or an exhaustive list.

[0081] For example, domain partitioning based on location involves dividing nodes or devices located in different locations into different domains. This location can be a logical location and / or a geographical location. For instance, location-based domain partitioning can create Edge domains and Cloud domains. Edge domains can include devices (or nodes) located at the network edge, which are at the front end of the network and typically close to the data source. Cloud domains can be provided by cloud service providers and can include at least one of cloud servers, cloud storage, etc. Devices or nodes in cloud domains are at the back end of the network and typically relatively far from the data source. For example, location can also be used to partition different domains located in different geographical regions. For example, for two different geographical regions, Region-1 and Region-2, devices or nodes in Region-1 are assigned to the same domain, devices or nodes in Region-2 are assigned to the same domain, and so on.

[0082] For example, domain partitioning can be based on network type, that is, dividing nodes or devices of different network types into different domains. Network types can include at least one of the following: TN (Terrestrial Network), NTN (Non-Terrestrial Network), PLMN (Public Land Mobile Network), and NPN (Non-public network). For instance, devices or nodes under a TN network can be grouped into the same domain, and devices or nodes under an NTN network can be grouped into the same domain. Similarly, devices or nodes under PLMN-1 can be grouped into the same domain, devices or nodes under PLMN-2 can be grouped into the same domain, and devices or nodes under an NPN network can be grouped into the same domain.

[0083] For example, domain partitioning can be based on system type, that is, dividing nodes or devices of different system types into different domains. System types can include at least one of the following: 6GS (6th Generation System), 5GS (5th Generation System), and EPS (Evolved Packet System). For instance, devices or nodes under 6GS can be divided into the same domain, devices or nodes under 5GS can be divided into the same domain, and devices or nodes under EPS can be divided into the same domain.

[0084] It should be understood that the above is only an illustrative description of the domain division methods. In actual processing, the above division methods may be combined. For example, different domains may be divided based on at least two of the following: device, device type, location, system type, and network type. In actual processing, other methods may also be used to divide different domains. This article does not limit or exhaust all possible domain division methods.

[0085] The following example illustrates the concept of a cross-domain data pipeline. This first data pipeline can consist of one or more participating nodes within each of multiple domains. These participating nodes can collaboratively complete processing tasks related to the first data service, which can be any type of data service. There is no limitation on the number of domains the first data pipeline crosses. The device type of any participating node in the first data pipeline can be any one of the following: terminal, access network device, core network device, AF, server, etc.

[0086] The first data pipeline can have different identifiers in different domains of multiple domains. The identifier of the first data pipeline in a certain domain can be replaced by the domain DPID (Data Pipeline ID) of the first data pipeline, or the DPID of the first data pipeline in a certain domain, etc., which will not be repeated below.

[0087] The domain data pipeline ID of the first data pipeline in any domain can consist of the following two parts: the domain identifier and the domain identifier of the first data pipeline in that domain.

[0088] The domain identifier is used to identify a specific domain. This domain identifier can be represented as a domain ID, which will not be repeated below.

[0089] The domain identifier of the first data pipeline in this domain can be determined and assigned by the data control node or identifier allocation node of this domain. The domain identifier of the first data pipeline in this domain is unique within the domain, thus ensuring the uniqueness of the identifier of the first data pipeline in this domain. The domain identifier of the first data pipeline in this domain can be replaced by the domain-specific data pipeline ID (domain-specific DPID) of the first data pipeline in this domain, which will not be repeated below.

[0090] The length of the identifiers for different domains can be the same, and the length of the identifiers for the first data pipeline within the corresponding domains of different domains can also be the same. The length of the identifier for the first data pipeline within any corresponding domain is greater than the length of the domain identifier. This embodiment does not limit the specific length of the domain identifiers or the identifiers for the first data pipeline within any corresponding domain.

[0091] Taking the example of a first data pipeline spanning multiple domains, including adjacent first and second domains, the identifier of the first data pipeline in the first domain is different from that in the second domain. Furthermore, the identifier of the first data pipeline in the first domain is unique within that domain, and the identifier in the second domain is also unique within that domain. Here, the first and second domains may be different domains derived from at least one of the following partitioning methods: device, device type, location, system type, network type, etc. For example, the first and second domains may be different domains derived from device type, where they may each contain different device types, such as the first domain including one or more terminals and the second domain including one or more access network devices, or vice versa. Alternatively, the first and second domains may be derived from location, where the first domain may be an edge domain (e.g., including one or more edge devices or edge nodes) and the second domain may be a cloud domain (e.g., including cloud hosts and / or cloud storage, etc.), or vice versa. Finally, the first and second domains may be derived from device type and network type, where the first domain may include one or more core network devices under PLMN-1 and the second domain may include one or more access network devices under PLMN-2, or vice versa. It should be understood that this is only an exemplary illustration of the division method of the first domain and the second domain, and only an exemplary illustration of the devices or nodes that the first domain and the second domain may contain. In actual processing, any one or more of the above division methods or other division methods may be used to divide different first domains and second domains. The devices or nodes that the first domain and the second domain may contain are not limited to the possibilities in the above examples. The embodiments of this application do not limit or exhaustively describe them, and will not be repeated below.

[0092] The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain and the identifier of the first data pipeline within the domain corresponding to the first domain; the identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline within the domain corresponding to the second domain. Referring to Figure 7, the composition of the DPID of the first data pipeline in the first domain is illustrated by way of example. The first domain data pipeline ID of the first data pipeline can consist of the following two parts: the first domain ID and the domain-specific data pipeline ID of the first data pipeline within the first domain.

[0093] In some possible implementations, the first data control node needs to send a first service request to the second data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain, so that the second data control node obtains the identifier of the first data pipeline in the first domain, and then generates the identifier mapping information of the first data pipeline.

[0094] Before the first data control node sends the first service request to the second data control node, the method further includes: the first data control node receiving a second service request from a service request node, wherein the second service request carries relevant information about the first data service; and the first data control node determining one or more participating nodes of the first data pipeline corresponding to the first data service within the first domain based on the relevant information of the first data service, wherein the one or more participating nodes of the first data pipeline within the first domain include the one or more first participating nodes.

[0095] In this embodiment, the service request node belongs to the first domain. The device type of the service request node is not limited in this embodiment. For example, the device type of the service request node can be any of the following: terminal, access network device, core network device, AF, etc. The device types of the first data control node and the second data control node are also not limited in this embodiment. For example, the device type of the first data control node or the second data control node may be any of the following: terminal, access network device, core network device, AF, etc. The device type of the second data control node may be the same as or different from that of the first data control node; this will not be explained again below.

[0096] This embodiment does not limit the reason why the service request node sends the second service request. The second service request may carry relevant information about the first data service. This relevant information may include at least one of the following: description information, identifier (ID), description identifier, etc.

[0097] The first data control node determines one or more participating nodes of the first data pipeline corresponding to the first data service within the first domain based on the relevant information of the first data service. This may include: the first data control node determining the description information of the first data service corresponding to or associated with the relevant information of the first data service based on the relevant information of the first data service; and determining one or more participating nodes of the first data pipeline corresponding to the first data service within the first domain based on the description information of the first data service.

[0098] Specifically, on both the business request node and the first data control node, the following information can be pre-configured: relevant information for each data service in one or more data services, and data service description information corresponding to or associated with the relevant information for each data service. The data service description information may include the requirements for executing the data service or data business. For example, the requirements for executing any data service may include at least one of the following: end-to-end latency requirements, accuracy requirements, reliability requirements, computing power requirements, storage requirements, energy consumption requirements, security requirements, location requirements, etc. The various aspects of the requirements for executing a data service will not be elaborated or exhaustively listed here.

[0099] It should be understood that, since the first data control node belongs to the first domain, the first data control node only needs to determine one or more participating nodes in the first domain that participate in the first data pipeline. This embodiment does not limit the specific processing method for the first data control node to determine one or more participating nodes in the first domain corresponding to the first data service.

[0100] In one embodiment, after determining one or more participating nodes of the first data pipeline corresponding to the first data service within the first domain, and before the first data control node receives the identifier mapping information from the second data control node, the first data control node may further include: the first data control node sending a first identifier allocation request to the first identifier allocation node; the first data control node receiving a first identifier allocation response from the first identifier allocation node, wherein the first identifier allocation response carries one of the following: the identifier of the first data pipeline in the first domain, or the identifier of the first data pipeline within the domain corresponding to the first domain.

[0101] The first identifier allocation node can be an identifier allocation node within the first domain. Here, the identifier allocation node can be a newly added network element dedicated to allocating identifiers for data pipelines; or, the identifier allocation node can be an existing network element that has been given the function of allocating identifiers for data pipelines, such as the existing network element being a UDM in the core network, etc., without limitation or exhaustive list. For example, the identifier allocation node can also be referred to as a data pipeline identifier (ID) pool.

[0102] The content carried by the first identifier allocation request is not limited in this embodiment. For example, it may carry at least one of the following: the identifier of the first data control node, information related to the first data service, etc.

[0103] Optionally, the first identifier allocation response may carry the identifier of the first data pipeline in the first domain.

[0104] On the first identifier allocation node side, all possible or candidate identifiers (or identifier values) within the first domain can be pre-generated or pre-stored. For simplicity, the following text will refer to all possible or candidate identifiers (or identifier values) within the first domain as all candidate identifiers within the first domain. Any one of these candidate identifiers within the first domain can be assigned as the domain identifier (or simply domain-specific DPID) for any data pipeline in the first domain. The value range of all candidate identifiers within the first domain can be related to the length of the data pipeline's domain identifier in each domain. For example, if the length of the data pipeline's domain identifier in each domain is 2 bytes (16 bits), then the value range of all candidate identifiers within the first domain can be 1 to 65536. This is only an example; in actual processing, the value range of all candidate identifiers within the first domain will vary depending on the length of the data pipeline's domain identifier in each domain. We will not limit or exhaust all possible cases here.

[0105] After receiving the first identifier allocation request, the first identifier allocation node can perform the following processing: The first identifier allocation node selects one from the unused candidate identifiers as the domain identifier of the first data pipeline in the first domain; the first identifier allocation node marks the candidate identifier selected as the domain identifier of the first data pipeline in the first domain as used; the first identifier allocation node combines the identifier of the first domain and the domain identifier of the first data pipeline in the first domain to obtain the identifier of the first data pipeline in the first domain.

[0106] The first identifier allocation node can mark the status of each candidate identifier in the first domain that it stores. For example, if a candidate identifier is selected as the identifier of a data pipeline in the first domain, the candidate identifier can be marked as used or in use, or the status of the candidate identifier is marked as used; if a candidate identifier is not selected as the identifier of any data pipeline in the first domain, the candidate identifier can be marked as valid or not used, etc.

[0107] Unused candidate identifiers may include all candidate identifiers that are not marked as used, or all candidate identifiers that are marked as valid or unused.

[0108] The first identifier allocation node selects one from the unused candidate identifiers as the domain identifier of the first data pipeline corresponding to the first domain. This can be done in three ways: the first identifier allocation node randomly selects one from the unused candidate identifiers as the domain identifier of the first data pipeline corresponding to the first domain; or the first identifier allocation node selects the first one from the unused candidate identifiers as the domain identifier of the first data pipeline corresponding to the first domain; or the first identifier allocation node selects the value at a specified sorting position from the unused candidate identifiers as the domain identifier of the first data pipeline corresponding to the first domain. The specified sorting position can be indicated according to the actual situation, and its indication method or content is not limited here.

[0109] The first identifier allocation node combines the identifier of the first field and the identifier of the first data pipeline within the corresponding field in the first field to obtain the identifier of the first data pipeline in the first field. Specifically, the first identifier allocation node combines the identifier of the first field and the identifier of the first data pipeline within the corresponding field in the first field according to a specified combination method. The identifier of the first field can be pre-configured by the first identifier allocation node; its configuration method is not limited here. The specified combination method can be default, pre-configured, or protocol-defined. For example, the specified combination method could default to placing the identifier of the first field in the low bit position (or on the right) and the identifier of the first data pipeline within the corresponding field in the first field in the high bit position (or on the left), or vice versa. Not all possible combination methods are limited here.

[0110] Optionally, the first identifier allocation response may carry the identifier of the first data pipeline within the domain corresponding to the first domain.

[0111] After receiving the first identifier allocation request, the first identifier allocation node can perform the following processing: the first identifier allocation node selects one from the unused candidate identifiers as the domain identifier of the first data pipeline in the first domain; the first identifier allocation node marks the candidate identifier selected as the domain identifier of the first data pipeline in the first domain as used.

[0112] The processing after the first data control node receives the first identifier allocation response may further include: combining the identifier of the first domain and the domain identifier of the first data pipeline corresponding to the first domain to obtain the identifier of the first data pipeline in the first domain. The relevant explanation of the first data control node combining the identifier of the first data pipeline in the first domain is the same as the previous example and will not be repeated. The identifier of the first domain may be pre-configured on the first data control node side or pre-generated by the first data control node, and there is no limitation on it here.

[0113] In one embodiment, after the first data control node receives a first identifier allocation response from the first identifier allocation node, the method further includes: the first data control node sending a first service request to the second data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain. Correspondingly, before the second data control node sends a second identifier allocation request to the second identifier allocation node, the method further includes: the second data control node receiving a first service request from the first data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain.

[0114] The first data control node sending a first service request to the second data control node may include: the first data control node determining, based on the first data service description information, whether the first data pipeline requires the participation of other domains; if it is determined that the participation of a second domain is required, the first data control node sends the first service request to the second data control node. Here, the requirement for the participation of a second domain in the first data pipeline may mean that the first data pipeline needs to be jointly composed of participating nodes from the second domain to collaboratively complete the processing tasks related to the first data service. This embodiment does not limit the specific processing method by which the first data control node determines whether the first data pipeline requires the participation of other domains.

[0115] The first data control node's determination of whether the first data pipeline requires the participation of other domains can be performed simultaneously with the first data control node's determination of one or more participating nodes in the first domain corresponding to the first data service, or after the first data control node's determination of one or more participating nodes in the first domain corresponding to the first data service, without limitation.

[0116] The second domain is a neighboring domain of the first domain. The number of neighboring domains of the first domain can be one or more, and the second domain can refer to any one of the one or more neighboring domains of the first domain. Since the relevant processing for each neighboring domain of the first domain is the same as that for the second domain, the following explanation mainly uses the second domain as an example and does not elaborate on the relevant processing for each neighboring domain of the first domain.

[0117] Optionally, the first data control node sending a first service request to the second data control node may include: the first data control node sending the first service request to the second data control node through a first data orchestration node in a first domain. Correspondingly, the processing of the first data orchestration node may include: receiving the first service request from the first data control node and sending the first service request to a second data orchestration node in a second domain. The processing of the second data orchestration node may include: receiving the first service request from the first data orchestration node and sending the first service request to the second data control node. The second data control node receiving the first service request from the first data control node includes: the second data control node receiving the first service request from the first data control node through a second data orchestration node in a second domain.

[0118] The functions of the first data orchestration node can include at least one of the following: cross-domain authorization, authentication and configuration transmission, ensuring isolation between domains, etc. The first data orchestration node can be a logical function, connected to the first data control node and equipment in the first domain; alternatively, the first data orchestration node can be an independent network element. The second data orchestration node has the same function as the first data orchestration node, but belongs to a different domain, and will not be described again. A data orchestration node within any domain can also be called a DPOC (Data Plane Orchestration Controller), a domain isolation node, or a data orchestration function, etc.

[0119] Optionally, the first data control node can directly send the first service request to the second data control node. The second data control node directly receives the first service request from the first data control node. In this case, it can also be understood that the function provided by the data orchestration node is the function of the data control node itself.

[0120] In addition to carrying the identifier of the first data pipeline in the first domain, the first service request may also carry at least one of the following: information related to the first data service, which is used by the second data control node to determine one or more participating nodes of the first data pipeline corresponding to the first data service within the second domain; and the addresses of one or more first participating nodes. Specifically, for each of the one or more first participating nodes, the previous hop participating node in the first data pipeline belongs to the second domain, and / or the next hop participating node in the first data pipeline belongs to the second domain. For example, for any given first participating node, the previous hop participating node in the first data pipeline belongs to the second domain, and / or the next hop participating node in the first data pipeline belongs to the second domain.

[0121] The address of the first participating node can refer to its network address and / or network identifier. The network address can include at least one of the following: IP (Internet Protocol) address, MAC (Media Access Control) address, etc., and the network identifier can include at least one of the following: number, entity identifier, etc. By carrying the address of the first participating node located at the edge of the first domain in the first service request, the second data control node can determine the routing information corresponding to the participating nodes at the edge locations adjacent to the first and second domains. This first participating node can also be referred to as an edge node of the first domain, or an edge participating node in the first domain located at an edge location adjacent to the second domain.

[0122] Optionally, the first service request may carry the identifier of the first data pipeline in the first domain, relevant information about the first data service, and the addresses of one or more first participating nodes.

[0123] It should be noted that the processing by the first data control node after determining whether the first data pipeline requires the participation of other domains based on the first data service description information may also include: determining that the first data pipeline does not require the participation of other domains. In this case, since the first data control node determines that the first data pipeline does not require the participation of other domains, the first data control node can, after obtaining the identifier of the first data pipeline in the first domain, directly send the identifier of the first data pipeline in the first domain, the routing information corresponding to each participating node, the data pipeline policy corresponding to each participating node, etc., to each participating node in the first domain, which will not be elaborated here.

[0124] In some possible implementations, after the second data control node receives the first service request sent by the first data control node, it further includes: the second data control node determining one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain based on the relevant information of the first data service, wherein the one or more participating nodes of the first data pipeline in the second domain include the one or more second participating nodes.

[0125] The second data control node determines the processing method of one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain based on the relevant information of the first data service. This is similar to the processing method of the first data control node determining one or more participating nodes of the first data pipeline corresponding to the first data service in the first domain based on the relevant information of the first data service in the previous embodiment, so it will not be described again.

[0126] The preceding hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the second participating nodes in the first data pipeline belongs to the first domain. This second participating node may also be referred to as an edge node of the second domain, or an edge participating node located at an edge position adjacent to the first domain within the second domain.

[0127] In one embodiment, after the second data control node determines one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain based on the relevant information of the first data service, and before the second data control node sends the identifier mapping information of the first data pipeline to the first data control node, the method further includes: the second data control node sending a second identifier allocation request to a second identifier allocation node; the second data control node receiving a second identifier allocation response from the second identifier allocation node, wherein the second identifier allocation response carries one of the following: the identifier of the first data pipeline in the second domain, or the identifier of the first data pipeline in the domain corresponding to the second domain.

[0128] Here, the second identifier allocation node can be an identifier allocation node within the second domain. The content carried in the second identifier allocation request is not limited in this embodiment.

[0129] The description of the second identifier allocation node allocating the identifier of the first data pipeline in the second domain or the identifier of the first data pipeline in the domain corresponding to the second domain is similar to the description of the first identifier allocation node allocating the identifier of the first data pipeline in the first domain or the identifier of the first data pipeline in the domain corresponding to the first domain in the previous embodiment, and therefore will not be repeated. It should be noted that if the second identifier allocation response carries the identifier of the first data pipeline in the domain corresponding to the second domain, the second data control node can combine the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain to obtain the identifier of the first data pipeline in the second domain. The method by which the second data control node combines the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain is similar to the method by which the first data control node combines the identifier of the first domain and the identifier of the first data pipeline in the domain corresponding to the first domain in the previous embodiment, and will not be repeated.

[0130] After the second data control node receives the second identifier allocation response from the second identifier allocation node, the second data control node can generate and save the identifier mapping information of the first data pipeline. The identifier mapping information of the first data pipeline can be the identifier mapping information of the first data pipeline in a first domain and a second domain. Specifically, the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0131] After the second data control node generates the identification mapping information of the first data pipeline, the second data control node sends the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain.

[0132] Optionally, the second data control node sends the identification mapping information of the first data pipeline to each of the one or more second participating nodes within the second domain. Correspondingly, taking any one of the second participating nodes as an example, after receiving the identification mapping information of the first data pipeline, the second participating node can send a configuration receive response to the second data control node. The configuration receive response sent by the second participating node can be used to indicate that the second participating node has received the identification mapping information of the first data pipeline.

[0133] Optionally, the second data control node sends the identification mapping information of the first data pipeline to each of the one or more participating nodes of the first data pipeline within the second domain, wherein the one or more participating nodes within the second domain include one or more second participating nodes. Accordingly, taking any participating node within the second domain as an example, after receiving the identification mapping information of the first data pipeline, the participating node can send a configuration receive response to the second data control node.

[0134] After receiving the second identifier allocation response from the second identifier allocation node, the second data control node further includes at least one of the following: the second data control node sends the identifier of the first data pipeline in the second domain to one or more participating nodes of the first data pipeline in the second domain; the second data control node sends routing information corresponding to each of the one or more second participating nodes to each of the first or second participating nodes, wherein the routing information corresponding to each of the second participating nodes includes at least one of the following: the address of the previous hop participating node in the first data pipeline belonging to the first domain corresponding to each of the second participating nodes, and the address of the next hop participating node in the first data pipeline belonging to the first domain corresponding to each of the second participating nodes.

[0135] The second data control node sending routing information corresponding to each of the one or more second participating nodes to each of the first or second participating nodes may include: the second data control node sending the routing information corresponding to each of the one or more participating nodes in the second domain to each of the first or second participating nodes, wherein the one or more participating nodes in the second domain include one or more second participating nodes. The routing information corresponding to each participating node in the second domain can be used by each participating node to determine its previous hop participating node and / or next hop participating node in the first data pipeline. This embodiment does not limit the specific method by which the second data control node determines the routing information corresponding to each participating node in the second domain.

[0136] Specifically, all participating nodes in the second domain include the second participating node and / or other participating nodes besides the second participating node (or non-edge participating nodes in the second domain).

[0137] Taking any other participating node in the second domain besides the second participating node as an example, the routing information corresponding to any other participating node in the second domain includes: the address of the previous hop participating node in the first data pipeline that belongs to the second domain, and the address of the next hop participating node in the first data pipeline that belongs to the second domain.

[0138] Taking any second participating node as an example, the routing information corresponding to the second participating node includes at least one of the following: the address of the previous participating node in the first data pipeline that belongs to the first domain, and the address of the next participating node in the first data pipeline that belongs to the first domain.

[0139] Optionally, if the previous hop participating node of the second participating node belongs to the second domain and the next hop participating node belongs to the first domain, the routing information corresponding to the second participating node may include: the address of the previous hop participating node of the second participating node that belongs to the second domain in the first data pipeline, and the address of the next hop participating node of the second participating node that belongs to the first domain in the first data pipeline.

[0140] Optionally, if the next-hop participating node of the second participating node belongs to the second domain and the previous-hop participating node belongs to the first domain, the routing information corresponding to the second participating node may include: the address of the previous-hop participating node of the second participating node that belongs to the first domain in the first data pipeline, and the address of the next-hop participating node of the second participating node that belongs to the second domain in the first data pipeline.

[0141] Optionally, if both the next-hop participating node and the previous-hop participating node of the second participating node belong to the first domain, the routing information corresponding to the second participating node may include: the address of the previous-hop participating node of the second participating node that belongs to the first domain in the first data pipeline, and the address of the next-hop participating node of the second participating node that belongs to the first domain in the first data pipeline.

[0142] It should be noted that the second data control node can also send other information to each participating node in the second domain. For example, the second data control node can also send the data pipeline policy corresponding to each participating node in the first data pipeline to each participating node in the second domain. The data pipeline policies corresponding to different participating nodes in the second domain in the first data pipeline may be the same or different. The relevant description of the data pipeline policy is the same as that in the aforementioned embodiments, so it will not be repeated.

[0143] For example, the second data control node can send a first configuration message to each second participating node. The first configuration message for each second participating node can carry at least one of the following: the identifier mapping information of the first data pipeline, the identifier of the first data pipeline in the second domain, the routing information corresponding to the second participating node, and the data pipeline policy corresponding to the second participating node in the first data pipeline. Correspondingly, after receiving its corresponding first configuration message, any second participating node can also send a configuration reception response to the second data control node. This configuration reception response can indicate that the second participating node has received the first configuration message. Then, the second participating node can associate its data pipeline policy corresponding to the first data pipeline with the identifier of the first data pipeline in the second domain and save it locally. It can also associate its routing information with the identifier of the first data pipeline in the second domain and save it locally. Furthermore, the second participating node will also save the identifier mapping information of the first data pipeline.

[0144] For example, the second data control node sends a first configuration message corresponding to each of the other participating nodes in the second domain, excluding the second participating node. Each first configuration message may carry the identifier of the first data pipeline in the second domain, and may also carry at least one of the following: routing information corresponding to the other participating node, and the data pipeline policy corresponding to the other participating node in the first data pipeline. Correspondingly, after receiving its corresponding first configuration message, any other participating node in the second domain can also send a configuration reception response corresponding to the first configuration message back to the second data control node. Then, the other participating node can associate and save the data pipeline policy corresponding to the other participating node in the first data pipeline with the identifier of the first data pipeline in the second domain locally, and also associate and save the routing information corresponding to the other participating node with the identifier of the first data pipeline in the second domain locally.

[0145] It is also important to understand that after determining each participating node in the second domain, the second data control node may further include: if the second data control node determines, based on the first data service description information, that the first data pipeline also requires the participation of the third domain, then the second data control node sends a third service request to the third data control node in the third domain, wherein the third domain is adjacent to the second domain and not adjacent to the first domain. In this case, the relevant processing of the third data control node is similar to that of the second data control node, and the third data control node can send the identification mapping information of the first data pipeline in the second and third domains to the second data control node. The relevant processing between the third data control node and the second data control node can be similar to the relevant processing between the second data control node and the first data control node, and will not be elaborated further. In addition, the number of domains spanned by the first data pipeline may be even greater. The relevant processing of the data control nodes in every two adjacent domains is similar to that of the first and second data control nodes, and therefore will not be elaborated further.

[0146] In one embodiment, after the second data control node generates the identification mapping information of the first data pipeline, it can send the identification mapping information of the first data pipeline to the first data control node. Correspondingly, the first data control node can receive the identification mapping information of the first data pipeline from the second data control node.

[0147] In one embodiment, on the second data control node side, the method further includes: the second data control node sending the addresses of the one or more second participating nodes to the first data control node. On the first data control node side, the method further includes: the first data control node receiving the addresses of one or more second participating nodes in the second domain from the second data control node in the first data pipeline, wherein the previous hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain. The relevant description of the address of the second participating node is the same as that of the address of the first participating node in the foregoing embodiments, and will not be repeated.

[0148] The process of the second data control node sending the addresses of one or more second participating nodes to the first data control node can be performed simultaneously with the second data control node sending the identification mapping information of the first data pipeline to the first data control node. For example, the second data control node can send a second configuration message to the first data control node, which carries the identification mapping information of the first data pipeline and the addresses of one or more second participating nodes.

[0149] In some possible implementations, after the first data control node receives the identification mapping information of the first data pipeline from the second data control node, the first data control node may also create a mapping table locally. The mapping table may include: the identifier of the first data pipeline in the first domain, and the identifier of the first data pipeline in the second domain that has a mapping relationship with the identifier of the first data pipeline in the first domain.

[0150] It should also be understood that if there are one or more other adjacent domains besides the second domain in the first domain, the first data control node can also interact with other adjacent domains to receive the identifier mapping information of the first data pipeline from each other data control node in each other adjacent domain and jointly generate a mapping relationship table; here, the identifier mapping information of the first data pipeline from each other data control node can be referred to as the identifier mapping information of the first data pipeline in the first domain and each other adjacent domain, wherein the identifier mapping information of the first data pipeline in the first domain and each other adjacent domain may include: the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in each other adjacent domain. For example, one of the other adjacent domains of the first domain is called the fourth domain. The identifier mapping information of the first data pipeline from the data control node of the fourth domain may include the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the fourth domain. In this case, after the first data control node receives the identifier mapping information of the first data pipeline from the second data control node and the identifier mapping information of the first data pipeline from the data control node of the fourth domain, it creates a mapping relationship table locally. The mapping relationship table may include: the identifier of the first data pipeline in the first domain, the identifier of the first data pipeline in the second domain that has a mapping relationship with the identifier of the first data pipeline in the first domain, and the identifier of the first data pipeline in the fourth domain that has a mapping relationship with the identifier of the first data pipeline in the first domain.

[0151] In one embodiment, after the first data control node receives the identification mapping information of the first data pipeline from the second data control node, the first data control node sends the identification mapping information of the first data pipeline to one or more first participating nodes of the first data pipeline in the first domain.

[0152] Optionally, the first data control node sends the identification mapping information of the first data pipeline to each of the one or more first participating nodes within the first domain. Accordingly, taking any one of the one or more first participating nodes as an example, the processing of that first participating node may include: the first participating node receiving the identification mapping information of the first data pipeline from the first data control node. After receiving the identification mapping information of the first data pipeline, the first participating node may send a configuration receive response to the first data control node. The configuration receive response sent by the first participating node can be used to indicate that the first participating node has received the identification mapping information of the first data pipeline.

[0153] Optionally, the first data control node sends the identification mapping information of the first data pipeline to each of the one or more participating nodes in the first domain, wherein the one or more participating nodes in the first domain include one or more first participating nodes. Correspondingly, taking any participating node in the first domain as an example, after receiving the identification mapping information of the first data pipeline, the participating node can send a configuration receive response to the first data control node.

[0154] In one embodiment, after receiving a first identifier allocation response from the first identifier allocation node, the method further includes: the first data control node sending the identifier of the first data pipeline in the first domain to one or more participating nodes of the first data pipeline within the first domain. Specifically, the first data control node may send the identifier of the first data pipeline in the first domain to one or more participating nodes of the first data pipeline within the first domain after receiving the first identifier allocation response from the first identifier allocation node and after receiving identifier mapping information of the first data pipeline from the second data control node.

[0155] Accordingly, taking any first participating node as an example, the method further includes: the first participating node receiving the identifier of the first data pipeline in the first domain from the first data control node. For any other participating node in the first domain besides the respective first participating nodes, its processing may include: receiving the identifier of the first data pipeline in the first domain from the first data control node.

[0156] After the first data control node receives the addresses of one or more second participating nodes in the second domain of the first data pipeline from the second data control node, the method further includes: the first data control node sending routing information corresponding to each of the one or more first participating nodes to each of the first participating nodes, wherein the routing information corresponding to each first participating node includes at least one of the following: the address of the previous hop participating node in the first data pipeline belonging to the second domain corresponding to each first participating node, and the address of the next hop participating node in the first data pipeline belonging to the second domain corresponding to each first participating node.

[0157] Here, the first data control node sending routing information corresponding to each of the one or more first participating nodes to each of the first participating nodes may include: the first data control node sending routing information corresponding to each of the one or more participating nodes in the first domain to each of the one or more participating nodes, wherein the one or more participating nodes in the first domain include one or more first participating nodes. This embodiment does not limit the specific method by which the first data control node determines the routing information corresponding to each participating node in the first domain.

[0158] Specifically, all participating nodes in the first domain include the first participating node and / or other participating nodes besides the first participating node (or non-edge participating nodes in the first domain).

[0159] For any other participating node within the first domain besides the respective first participating nodes, its processing may include: receiving routing information corresponding to other participating nodes within the first domain from the first data control node. The routing information corresponding to any other participating node within the first domain includes: the address of the previous-hop participating node belonging to the first domain in the first data pipeline, and the address of the next-hop participating node belonging to the first domain in the first data pipeline.

[0160] Taking any first participating node within the first domain as an example, the method further includes: the first participating node receiving routing information corresponding to the first participating node from the first data control node, wherein the routing information corresponding to the first participating node includes at least one of the following: the address of the previous hop participating node in the first data pipeline belonging to the second domain, and the address of the next hop participating node in the first data pipeline belonging to the second domain.

[0161] Optionally, if the previous hop participating node of the first participating node belongs to the first domain and the next hop participating node belongs to the second domain, the routing information corresponding to the first participating node may include: the address of the previous hop participating node of the first participating node that belongs to the first domain in the first data pipeline, and the address of the next hop participating node of the first participating node that belongs to the second domain in the first data pipeline.

[0162] Optionally, if the next-hop participating node of the first participating node belongs to the first domain and the previous-hop participating node belongs to the second domain, the routing information corresponding to the first participating node may include: the address of the previous-hop participating node of the first participating node that belongs to the second domain in the first data pipeline, and the address of the next-hop participating node of the first participating node that belongs to the first domain in the first data pipeline.

[0163] Optionally, if both the next-hop participating node and the previous-hop participating node of the first participating node belong to the second domain, the routing information corresponding to the first participating node may include: the address of the previous-hop participating node of the first participating node that belongs to the second domain in the first data pipeline, and the address of the next-hop participating node of the first participating node that belongs to the second domain in the first data pipeline.

[0164] It should be noted that the first data control node can also send other information to each participating node in the first domain. For example, the first data control node can also send the data pipeline policy corresponding to each participating node in the first data pipeline to each participating node in the first domain. The data pipeline policies corresponding to different participating nodes in the first domain may be the same or different. The relevant description of the data pipeline policy is the same as that in the aforementioned embodiments, so it will not be repeated.

[0165] For example, the first data control node can send a third configuration message to each first participating node. Each first participating node's first configuration message can carry at least one of the following: the identifier mapping information of the first data pipeline, the identifier of the first data pipeline in the first domain, the routing information corresponding to the first participating node, and the data pipeline policy corresponding to the first participating node in the first data pipeline. Correspondingly, after receiving its corresponding third configuration message, any first participating node can also send a configuration reception response to the first data control node. This configuration reception response can indicate that the first participating node has received the third configuration message. Then, the first participating node can associate its data pipeline policy corresponding to the first data pipeline with the identifier of the first data pipeline in the first domain and save it locally. It can also associate its routing information with the identifier of the first data pipeline in the first domain and save it locally. Furthermore, the first participating node will also save the identifier mapping information of the first data pipeline.

[0166] For example, the first data control node sends a third configuration message corresponding to each of the other participating nodes in the first domain, excluding the first participating node. Each third configuration message may carry the identifier of the first data pipeline in the first domain, and may also carry at least one of the following: routing information corresponding to the other participating node, and the data pipeline policy corresponding to the other participating node in the first data pipeline. Correspondingly, after receiving its corresponding third configuration message, any other participating node in the first domain can also send a configuration reception response corresponding to the third configuration message back to the first data control node. Then, the other participating node can associate and save the data pipeline policy corresponding to the other participating node in the first data pipeline with the identifier of the first data pipeline in the first domain locally, and also associate and save the routing information corresponding to the other participating node with the identifier of the first data pipeline in the first domain locally.

[0167] In some possible implementations, taking any first participating node in the first domain as an example, after receiving the identifier mapping information of the first data pipeline, the identifier of the first data pipeline in the first domain, the routing information corresponding to the first participating node, and the data pipeline policy corresponding to the first participating node from the first data control node, the first participating node will perform identifier mapping and related data processing when executing task processing within the first data pipeline. The following explanation will use any one of the first participating nodes as an example. It should be noted that the processing performed by each first participating node in the first domain is the same, therefore, it will not be described in detail below.

[0168] In one embodiment, the identifier mapping process is performed by an upstream node located at an edge position adjacent to the first domain and the second domain.

[0169] After the first participating node receives the identifier mapping information of the first data pipeline from the first data control node, the method further includes: if, based on the routing information corresponding to the first participating node, it is determined that the next-hop participating node in the first data pipeline belongs to the second domain, the first participating node determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline; the first participating node sends a first data frame to the next-hop participating node, wherein the first data frame carries the identifier of the first data pipeline in the second domain.

[0170] The identifier of the first data pipeline in the second field is carried by the identifier field in the first data frame or by the reserved field in the first data frame.

[0171] The first data frame can be encapsulated based on a preset transmission protocol. The specific encapsulation method or position of the first data pipeline's identifier in the second field within the first data frame is related to the preset transmission protocol. This preset transmission protocol can be configured according to actual conditions, and this embodiment does not limit it. As long as all participating nodes in each field of the first data pipeline can support the transmission protocol, it is within the protection scope of this embodiment.

[0172] For example, the identifier of the first data pipeline in the second field is carried by the identifier field in the first data frame. The preset transport protocol can be the QUIC (Quick UDP Internet Connection) protocol.

[0173] Referring to Figure 8, when the QUIC protocol is used to support data transmission in a data pipeline, the data itself is carried as stream data within QUIC frames (such as frames 1, 2 to N in Figure 8). Any QUIC frame (e.g., frame 2) may include the following fields: Frame Type, indicating a specific QUIC protocol frame type, such as PADDING, PING, ACK, etc.; Stream ID, identifying the data stream transmitted in this QUIC 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, carrying the frame payload. Additionally, a QUIC frame header can be encapsulated when transmitting data using the QUIC protocol; the content of this QUIC frame header is not limited in this embodiment.

[0174] In the QUIC frame, the two least significant bits in the stream identifier field are used to identify the initiator of the stream (least significant bit) and to identify whether the stream is unidirectional or bidirectional (second significant bit). For example, when the two least significant bits are "00", it indicates client-initial and bidirectional; when the two least significant bits are "01", it indicates server-initial and bidirectional; when the two least significant bits are "10", it indicates client-initial and unidirectional; and when the two least significant bits are "11", it indicates server-initiated and unidirectional. Therefore, the lowest two bits of the stream identifier field in the QUIC frame cannot be modified, and the maximum length of the stream identifier field in the QUIC frame is 62 bits.

[0175] However, in the stream identifier field of the QUIC frame, apart from the lowest two bits, at least some of the remaining bits can be modified to encapsulate or carry the identifier of the first data pipeline in a certain field. The specific number of bits or bytes in the stream identifier field of the QUIC frame used to encapsulate or carry the identifier of the first data pipeline in a certain field is related to the length of the identifier of the first data pipeline in each field.

[0176] Referring to Figure 9, assuming the length of the domain identifier in the identifier of the first data pipeline in each domain is less than or equal to 14 bits, and the length of the domain-specific identifier in the identifier of the first data pipeline in each domain is less than or equal to 16 bits, then the lowest 4 bytes of the stream identifier field in the QUIC frame can be modified to encapsulate or carry the identifier of the first data pipeline in a certain domain. Specifically, the two lowest bytes (14 bits remaining after subtracting the lowest two bits from 16 bits) of the stream identifier field in the QUIC frame are used to encapsulate or carry the domain identifier (or represented as Domain ID); the lowest 3rd to 4th bytes of the stream identifier field in the QUIC frame are used to encapsulate or carry the domain-specific DPID; and the remaining 5th to 8th bytes of the stream identifier field in the QUIC frame can be used to encapsulate or carry the stream ID (or data plane stream ID), which represents any data stream related to the data plane. Taking any QUIC frame as the first data frame as an example, the identifier of the first data pipeline in the second field of the identifier of the second field can be encapsulated in the remaining 14 bits of the two lowest bytes of the stream identifier field of the first data frame, excluding the last two bits. The identifier of the first data pipeline in the second field of the identifier of the first data pipeline in the corresponding field of the second field can be encapsulated in the lowest 3rd to 4th bytes of the stream identifier field of the first data frame.

[0177] The above is merely an illustrative example. There may be many other ways to modify at least some bytes in the stream identifier field of a QUIC frame to encapsulate or carry the identifier of the first data pipeline in a certain field. For example, assuming the length of the field identifier in the identifier of the first data pipeline in a certain field is less than or equal to 6 bits, and the length of the field-specific identifier in the identifier of the first data pipeline in a certain field is less than or equal to 16 bits, a lowest byte (6 bits remaining after subtracting the lowest 2 bits from 8 bits) in the stream identifier field of the QUIC frame is used to encapsulate or carry the field identifier, and the lowest 2nd to 4th bytes in the stream identifier field of the QUIC frame are used to encapsulate or carry the field-specific DPID; or, a lowest byte (6 bits remaining after subtracting the lowest 2 bits from 8 bits) in the stream identifier field of the QUIC frame can be used to encapsulate or carry the field identifier, and the lowest 2nd to 3rd bytes in the stream identifier field of the QUIC frame can be used to encapsulate or carry the field-specific DPID. This embodiment does not limit or exhaust all possible methods. Any method that can modify at least some bytes in the stream identifier field of the QUIC frame to encapsulate or carry the identifier of the first data pipeline in a certain field is within the scope of protection of this embodiment.

[0178] It should also be noted that in actual processing, the QUIC protocol can be replaced by any other protocol used for data transmission. Under any other protocol used for data transmission, the first data frame can be a data frame under that protocol, and the identifier of the first data pipeline in the second field can be carried by at least some bits in the identifier field of the first data frame under that protocol. This is not limited or exhaustive.

[0179] For example, the identifier of the first data pipeline in the second field is carried by a reserved field in the first data frame. The preset transmission protocol can be any protocol used for data transmission, that is, the first data frame can be any data frame in any protocol used for data transmission. The number of bits or bytes in the reserved field of the data frame used for data transmission that can be used to encapsulate or carry the identifier of the first data pipeline in a certain field is related to the length of the identifier of the first data pipeline in each field, and is not limited or exhaustively listed here.

[0180] The first data frame also carries the processed data corresponding to the first participating node. For example, the processed data corresponding to the first participating node may be encapsulated or carried in the fields of the first data frame used to carry the frame payload or data. Which fields of the first data frame are used to carry the frame payload or data may be related to the preset transmission protocol, and is not limited here.

[0181] The first participating node obtains its corresponding processed data in the following ways: the first participating node determines the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; the first participating node processes the data to be processed based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the first participating node.

[0182] The data to be processed may originate from the previous participating node in the first data pipeline. This means the data to be processed can be the data processed by the previous participating node. The previous participating node may belong to either the first domain or the second domain; this is not limited here. The data pipeline strategy of the first participating node in the first data pipeline may include the data processing method required by the first participating node for the data to be processed; this embodiment does not impose any limitations. Alternatively, the data to be processed may be the raw data collected by the first participating node. In this case, it is not necessary to process the raw data; the raw data can be directly carried in the first data frame and sent. Or, in this case, after collecting the raw data, the first participating node can also perform corresponding data processing (such as preprocessing) on ​​the raw data according to the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the first participating node.

[0183] In one embodiment, the identifier mapping process is performed by downstream nodes located at the edge positions adjacent to the first and second domains.

[0184] After the first participating node receives the identifier mapping information of the first data pipeline from the first data control node, the method further includes: the first participating node receiving a second data frame from the previous hop participating node of the first data pipeline belonging to the second domain, wherein the second data frame carries the identifier of the first data pipeline in the second domain; the first participating node determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline.

[0185] The identifier of the first data pipeline in the second field is carried by an identifier field in the second data frame or by a reserved field in the second data frame. The second data frame can also be encapsulated based on a preset transmission protocol. The encapsulation method or location for specifically encapsulating the identifier of the first data pipeline in the second field within the second data frame is similar to the method used in the aforementioned embodiments for specifically encapsulating the identifier of the first data pipeline in the second field within the first data frame, and therefore will not be elaborated upon further.

[0186] The second data frame also carries the processed data corresponding to the previous hop participating node. For example, the second data frame may carry the processed data corresponding to the previous hop participating node in a field used to carry frame payload or data, which is not limited here.

[0187] After the first participating node determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline, the process further includes: the first participating node determining the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; and the first participating node processing the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the first participating node. The specific processing method of the first participating node processing the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the first participating node is similar to the processing method in the previous embodiment where the first participating node processes the data to be processed based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the first participating node. The only difference is that the data to be processed in the previous embodiment is replaced with the processed data corresponding to the previous hop participating node belonging to the second domain, and therefore will not be elaborated further.

[0188] In one embodiment, the processing of the first participating node may further include: the first participating node sending an operation completion message to the first data control node. This operation completion message allows the first data control node to know that the first participating node has completed its task. The timing of the first participating node sending the operation completion message to the first data control node may be after the first participating node has completed the processing task related to the first data service corresponding to the first data pipeline it needs to participate in executing, and has sent out its processed data.

[0189] After the first participating node sends an operation end message to the first data control node, it may further include at least one of the following: the first participating node releases the identifier of the first data pipeline in the first domain; the first participating node releases the data pipeline policy corresponding to the first data pipeline; the first participating node deletes the identifier mapping information of the first data pipeline.

[0190] Preferably, after the first participating node sends an operation completion message to the first data control node, the first participating node releases the identifier of the first data pipeline in the first domain, releases the data pipeline policy corresponding to the first data pipeline, and deletes the identifier mapping information of the first data pipeline. In other words, after completing all its tasks within the first data pipeline, the first participating node may no longer save the identifier of the first data pipeline in the first domain, the data pipeline policy corresponding to the first data pipeline, or the identifier mapping information.

[0191] The above is an illustrative example using any one of the first participating nodes in the first domain. In actual processing, the processing of each first participating node in the first domain is the same, so it will not be described in detail. Other participating nodes in the first domain besides the first participating nodes can perform various processes other than the above-mentioned identifier mapping, which will also not be described again.

[0192] The processing of any second participating node is similar to that of the first participating node. The only difference is that when the identifier mapping is performed by the upstream node, the second participating node needs to determine, based on the corresponding routing information, whether the next-hop participating node belongs to the first domain before performing the identifier mapping, obtaining the identifier of the first data pipeline in the first domain, and sending a data frame carrying the identifier of the first data pipeline in the first domain and its processed data. In the scenario where the identifier mapping is performed by the downstream node, the second participating node determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline carried in the received data frame, and then performs data processing. In addition, the data pipeline strategy corresponding to the first data pipeline of the second participating node may be different from that of the first participating node in the first data pipeline, so the specific processing of each second participating node will not be repeated here.

[0193] In some possible implementations, after the first data control node sends the identifier mapping information of the first data pipeline to one or more first participating nodes in the first domain, the method further includes: upon receiving an operation end message from the one or more first participating nodes, the first data control node performs at least one of the following: sending a first identifier release request to the first identifier allocation node, wherein the first identifier release request is used to instruct the first identifier allocation node to release the identifier of the first data pipeline in the first domain; deleting the identifier mapping information of the first data pipeline.

[0194] After the second data control node sends the identifier mapping information of the first data pipeline to one or more second participating nodes in the second domain, the method further includes: upon receiving an operation end message from the one or more second participating nodes, the second data control node performs at least one of the following: sending an identifier release request to the second identifier allocation node, wherein the identifier release request is used to instruct the second identifier allocation node to release the identifier of the first data pipeline in the second domain; or deleting the identifier mapping information of the first data pipeline.

[0195] For example, when the first data control node receives an operation end message from each of the one or more first participating nodes, the first data control node sends a first identifier release request to the first identifier allocation node and deletes the identifier mapping information of the first data pipeline.

[0196] For example, the processing of the first data control node can be as follows: when the first data control node receives an operation end message from each of the one or more participating nodes in the first data pipeline within the first domain, the first data control node sends a first identifier release request to the first identifier allocation node and deletes the identifier mapping information of the first data pipeline, wherein the one or more participating nodes in the first domain include one or more first participating nodes.

[0197] In other words, when the first data control node determines that each participating node in the first domain or each first participating node has completed its respective task, it can notify the first identifier allocation node in the first domain to release the identifier allocated to the first data pipeline, and the first data control node will no longer store any identifier mapping information of the first data pipeline locally.

[0198] Optionally, the first identifier release request may carry the identifier of the first data pipeline in the first domain, and information indicating release. This information indicating release may be descriptive, such as including a "release ID" or "deletion identifier".

[0199] Accordingly, the processing performed by the first identifier allocation node after receiving the first identifier release request from the first data control node may include: determining the domain identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the first domain; and remarking the candidate identifier corresponding to the domain identifier of the first data pipeline in the first domain as valid or unused.

[0200] Optionally, the first identifier release request may carry information indicating the release of the first data pipeline within the domain corresponding to the first domain, as well as the identifier of the first data pipeline in the identifier of the first domain. Accordingly, the processing performed by the first identifier allocation node after receiving the first identifier release request from the first data control node may include: re-marking the candidate identifier corresponding to the domain identifier of the first data pipeline in the domain corresponding to the first domain as valid or unused.

[0201] After the first data control node completes the execution of sending a first identifier release request to the first identifier allocation node and / or deleting the identifier mapping information of the first data pipeline, the process may further include: the first data control node sending an operation completion response to the service request node. The content that this operation completion response may carry is not limited in this embodiment.

[0202] The processing of the second data control node can be as follows: Upon receiving an operation completion message from each of the participating nodes in one or more of the first data pipeline within the second domain, the second data control node sends a second identifier release request to the second identifier allocation node and deletes the identifier mapping information of the first data pipeline; or, upon receiving an operation completion message from each of the second participating nodes, the second data control node sends a second identifier release request to the second identifier allocation node and deletes the identifier mapping information of the first data pipeline. In other words, when the second data control node determines that all participating nodes or all second participating nodes of the first data pipeline within the second domain have completed their respective tasks, it can notify the second identifier allocation node within the second domain to release the identifier allocated to the first data pipeline, and the second data control node will no longer locally store any identifier mapping information of the first data pipeline. The description of the related processing of the second data control node and the second identifier allocation node is similar to the description of the related processing of the first data control node and the first identifier allocation node, and therefore will not be repeated.

[0203] The identifier mapping method provided in this application embodiment will be described below with reference to Figure 10, specifically including:

[0204] Step 1001: When a service requester (i.e., the service request node in the aforementioned embodiments) wants to execute a data-related service, the service requester sends a service request (i.e., the second service request in the aforementioned embodiments) to the DPAC-A (i.e., the first data control node) within its own domain (e.g., the first domain). This service request may include a data service description ID (i.e., information related to the first data service in the aforementioned embodiments). The data service description ID can be a standardized ID, corresponding to data service description information (i.e., the first data service description information in the aforementioned embodiments). This data service description ID and its corresponding data service description information can be pre-configured in the service requester and the DPAC-A. The content of the data service description information is the same as in the aforementioned embodiments and will not be repeated here.

[0205] Step 1002: DPAC-A determines the data pipeline participants (i.e., one or more participating nodes of the first data pipeline in the first domain) who need to participate in the data service based on the data service description ID and data service description information.

[0206] Step 1003: DPAC-A sends a domain identifier allocation request (i.e., the first identifier allocation request) to the data pipeline ID pool-A (i.e., the first identifier allocation node).

[0207] Step 1004: Assign domain DPID-A (i.e., the identifier of the first data pipeline in the first domain) to the data pipeline ID pool-A, and mark the ID as being in use and unable to be assigned again.

[0208] Step 1005: Data pipeline ID pool-A sends an allocation request response (i.e., first identifier allocation response) to DPAC-A, which may include the allocated domain DPID-A.

[0209] Step 1006: Based on the data service description ID and data service description information, DPAC-A determines that a participant in domain B (such as the second domain) is required to support the data pipeline established for this service. Therefore, DPAC-A interacts with DPOC-B (i.e., the second data orchestration node) through DPOC-A (i.e., the first data orchestration node).

[0210] Step 1007: DPAC-A sends a service request (i.e., the first service request) to DPOC-B via DPOC-A, which includes the Data Service Description ID and the domain DPID-A. DPOC-B can then send the Data Service Description ID and the domain DPID-A to DPAC-B (i.e., the second data control node of the second domain).

[0211] Optionally, the content sent by DPAC-A when interacting with DPOC-B through DPOC-A may include, in addition to the data service description ID and the domain DPID-A, the address of the edge node (i.e., the address of the first participating node of the first domain).

[0212] Step 1008: DPAC-B determines the data pipeline participants (i.e., one or more participating nodes of the first data pipeline in the second domain) within this domain based on the data service description ID.

[0213] Step 1009: DPAC-B sends a domain identifier allocation request (i.e., the second identifier allocation request) to the data pipeline ID pool-B (i.e., the second identifier allocation node).

[0214] Step 1010: Assign domain DPID-B (i.e., the identifier of the first data pipeline in the second domain) to the data pipeline ID pool-B, and mark the ID as being in use and unable to be assigned again.

[0215] Step 1011: Data pipeline ID pool-B sends an allocation request response (i.e., second identifier allocation response) to DPAC-B, including the allocated domain DPID-B.

[0216] Step 1012: DPAC-B establishes the DPID mapping relationship between domain A and domain B (i.e., the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain).

[0217] Step 1013: DPAC-B sends a service response to DPAC-A via DPOC-B, which carries the DPID mapping relationship between domain A and domain B. Optionally, DPAC-B can also send the address of the edge node (the address of the second participating node of the second domain) to DPAC-A via DPOC-B.

[0218] Step 1014: DPAC-A collects mapping relationships and creates a mapping relationship table.

[0219] Optionally, if DPAC-A has multiple neighborhoods, DPAC-A can collect the mapping relationships of multiple neighborhoods and create a mapping relationship table, for example:

[0220] In step 1015A, if participant X is at the edge of domain A (i.e., participant X is the first participating node in the first domain), then DPAC-A sends the mapping table to participant X. Optionally, DPAC-A may also send the mapping table to all participants in the same domain (i.e., all participating nodes in the first domain).

[0221] Step 1016A: Participant X returns a mapping configuration acceptance response to DPAC-A.

[0222] In step 1015B, if participant Y is at the edge of domain B (i.e., participant Y is the second participating node in the second domain), then DPAC-B sends the mapping table to participant Y. Optionally, DPAC-B may also send the mapping table to all participants within the same domain (i.e., all participating nodes in the second domain).

[0223] Step 1016B: Participant Y returns the mapping configuration acceptance response to DPAC-B.

[0224] Step 1017: After the data operation of the data pipeline (i.e., the first data pipeline) is completed, participants X and Y return an operation completion message to DPAC-A and DPAC-B, respectively. Participants X and Y then release the domain DPID locally and release the data policy and resource configuration allocated for establishing the data pipeline.

[0225] Step 1018: DPAC-A sends a release request for domain DPID-A to data pipeline ID pool-A. Data pipeline ID pool-A remarks the ID as valid and it can be allocated again. DPAC-B sends a release request for domain DPID-B to data pipeline ID pool-B. Data pipeline ID pool-B remarks the ID as valid and it can be allocated again.

[0226] Step 1019: DPAC-A sends a data operation completion response to the service requester.

[0227] Referring to Figure 10, the three stages of the domain DPID lifecycle are illustrated below:

[0228] Preparation Phase: Based on the business requirement description provided by the business requester, DPAC-A discovers and selects suitable data pipeline participants and formulates a data pipeline strategy. Then, DPAC-A requests the allocation of an unused domain DPID-A from the data pipeline ID pool-A within the same domain. The data pipeline ID pool-A can be a UDM or a new network element. DPAC-A interacts with neighboring domains through DPOC-A to create domain DPID mapping relationships between its own domain and neighboring domains. DPAC-A sends its own domain DPID-A and the domain-neighboring domain DPID mapping relationships to the participants in its own domain. DPAC-A can send the domain-neighboring domain DPID mapping relationships only to participants at the domain edge, i.e., those whose previous or next-hop nodes are in different domains, or send the mapping rules to all participants in domain A. The relevant explanations for DPOC are the same as in the previous embodiments and will not be repeated. Furthermore, for data pipelines operating only within a single domain, only the domain's DPID needs to be sent to the participants; DPID mapping is not required.

[0229] Execution Phase: When participants in domains A and B of the data pipeline need to send data to the next node, they encapsulate the data into a QUIC stream and generate a QUIC stream ID (or QUIC stream ID field). The first four bytes of the QUIC stream ID are used to encapsulate the domain DPID, which is pre-allocated and configured by DPAC-A and DPAC-B to each participant in their respective domains. After a participant receives a data frame from the previous participant, it knows which data pipeline strategy to match based on the domain DPID in the QUIC stream ID, and thus performs the corresponding data operation. If two adjacent participants belong to different domains, the previous participant can map its own domain DPID to the neighboring domain's DPID according to its locally configured mapping information, add the mapped ID to the QUIC stream's ID field, and send it to the next participant; alternatively, the previous node still uses its own domain's DPID for data stream transmission, and the next participant, based on its locally configured mapping information, maps the DPID of another domain carried in the QUIC stream's ID field to its own domain's DPID, and then matches the corresponding data strategy.

[0230] Release Phase: Once the data pipeline operation is complete, each participant in the data pipeline releases its locally stored DPIDs and bindings to mapping rules, data pipeline resources, and policy configurations, etc. DPAC-A and DPAC-B release their respective domain DPIDs to their respective data pipeline ID pools.

[0231] The solution provided in this application embodiment, when the first data pipeline spans different domains, involves the data control node of the first domain obtaining the identifier mapping information of the first data pipeline from the data control node of the second domain. This identifier mapping information includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. The data control node of the first domain can then send this identifier mapping information to participating nodes within the first domain. This ensures the uniqueness of the identifier of the first data pipeline within each domain in scenarios where the first data pipeline spans multiple domains, thereby avoiding the problem of participating nodes from other domains obtaining relevant policies of this domain. It guarantees inter-domain isolation and thus ensures the security and privacy of the policies of participating nodes in different domains. Furthermore, since participating nodes in different domains can know the mapping relationship of the identifiers of the same data pipeline in different domains, it ensures that participating nodes in different domains working together on the same data pipeline can achieve collaborative operation.

[0232] Figure 11 is a schematic flowchart of an identifier mapping method according to an embodiment of this application. The method includes at least a portion of the following.

[0233] S1110. The terminal sends the identifier of the first data pipeline in the first domain to the second data control node, wherein the second data control node belongs to the second domain and the terminal belongs to the first domain;

[0234] S1120, The terminal receives the identifier mapping information of the first data pipe from the second data control node, wherein the identifier mapping information of the first data pipe includes the mapping relationship between the identifier of the first data pipe in the first domain and the identifier of the first data pipe in the second domain.

[0235] The descriptions of the identifiers of the first data pipeline in the first domain and the identifiers of the first data pipeline in the second domain are the same as those in the aforementioned embodiments and will not be repeated here.

[0236] In some possible implementations, before the terminal sends the identifier of the first data pipeline to the second data control node, the method further includes: the terminal receiving a second service request from a service request node, wherein the second service request carries information related to the first data service. The descriptions of the service request node and the second service request are the same as in the previous embodiments and will not be repeated. The difference from the previous embodiments is that the terminal may no longer need to determine other participating nodes within the first domain.

[0237] In one embodiment, after the terminal receives a second service request from a service request node and before the terminal sends the identifier of the first data pipeline in the first domain to the second data control node, the method further includes one of the following: the terminal generates an identifier of the first data pipeline in the first domain; the terminal sends an identifier allocation request to the identifier allocation node corresponding to the terminal, and the terminal receives an identifier allocation response from the identifier allocation node corresponding to the terminal, wherein the identifier allocation response carries one of the following: the identifier of the first data pipeline in the first domain, and the identifier of the first data pipeline in the domain corresponding to the first domain.

[0238] The process of generating an identifier for the first data pipeline in the first domain by the terminal may include: selecting one from unused candidate identifiers stored or managed by the terminal as the domain identifier for the first data pipeline in the first domain; and combining the identifier of the first domain and the domain identifier for the first data pipeline in the first domain to obtain the identifier for the first data pipeline in the first domain. The identifier of the first domain may be pre-generated by the terminal, pre-configured by the terminal, or pre-stored by the terminal; this embodiment does not limit this. The relevant descriptions of the candidate identifiers are the same as in the previous embodiments and will not be repeated. After selecting one from unused candidate identifiers stored or managed by the terminal as the domain identifier for the first data pipeline in the first domain, the process may further include marking the selected candidate identifier as the domain identifier for the first data pipeline in the first domain as in use.

[0239] The identifier allocation node corresponding to the terminal can be the identifier allocation node within the first domain responsible for allocating the data pipeline identifier for that terminal. For example, the identifier allocation node corresponding to the terminal can be the data pipeline ID pool corresponding to the terminal within the first domain; or, for example, the identifier allocation node corresponding to the terminal can be the application server corresponding to the terminal within the first domain. The specific possible devices for the identifier allocation node corresponding to the terminal are not limited or exhaustively listed here. The content that the identifier allocation request issued by the terminal may carry is not limited in this embodiment; for example, it may carry at least one of the following: the terminal's identifier, information related to the first data service, etc.

[0240] The specific processing of the identifier allocation node corresponding to the terminal, which allocates one of the identifiers of the first data pipeline in the first domain and the identifiers of the first data pipeline in the domain corresponding to the first domain, is similar to the relevant description of the first identifier allocation node in the previous embodiment, and will not be repeated here.

[0241] It should be noted that if the identifier allocation response received by the terminal carries the identifier of the first data pipeline within the domain corresponding to the first domain, the terminal can combine the identifier of the first domain and the identifier of the first data pipeline within the domain corresponding to the first domain to obtain the identifier of the first data pipeline in the first domain. The method by which the terminal combines the identifier of the first domain and the identifier of the first data pipeline within the domain corresponding to the first domain is similar to the method by which the first data control node combines the identifier of the first domain and the identifier of the first data pipeline within the domain corresponding to the first domain in the aforementioned embodiments, and will not be elaborated upon further.

[0242] In general, when a terminal is a participating node in the first domain of the first data pipeline, the domain DPID (i.e., the identifier of the first data pipeline in the first domain) on the terminal side can be allocated by the terminal itself, or by the application server corresponding to the terminal, or by a dedicated data pipeline ID pool (such as the data pipeline ID pool-UE) on the core network side.

[0243] In one embodiment, the terminal sending the identifier of the first data pipeline in the first domain to the second data control node includes: the terminal sending a first service request to the second data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain.

[0244] The first service request also carries at least one of the following: information related to the first data service, which is used by the second data control node to determine one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain; and the identifier of the terminal.

[0245] The description of the relevant information for the first data service is the same as in the aforementioned embodiments and will not be repeated. The purpose of carrying the terminal identifier in the first service request may be to help the second data control node determine the routing information corresponding to the second participating node located at the edge position adjacent to the first domain.

[0246] The processing after the second data control node receives the first service request from the terminal is the same as the processing after the second data control node receives the first service request from the first data control node in the previous embodiment. For example, the second data control node determines one or more participating nodes of the first data pipeline in the second domain, obtains the identifier of the first data pipeline in the second domain, determines the routing information and data pipeline policy corresponding to each participating node in the second domain and sends them to each participating node in the second domain, generates the identifier mapping information of the first data pipeline and sends it to the second participating node, etc. Therefore, it will not be described again.

[0247] The difference from the previous embodiments is that, after the second data control node generates the identification mapping information of the first data pipeline, it can send the identification mapping information of the first data pipeline to the terminal. Correspondingly, the terminal can receive the identification mapping information of the first data pipeline from the second data control node.

[0248] In some possible implementations, after the terminal receives the identification mapping information of the first data pipe from the second data control node, it can also create a mapping table locally. The mapping table may include: the identifier of the first data pipe in the first domain, and the identifier of the first data pipe in the second domain that has a mapping relationship with the identifier of the first data pipe in the first domain.

[0249] It should also be understood that the second domain can be any one of one or more adjacent domains of the first domain. If there are one or more other adjacent domains besides the second domain in the first domain, the terminal can also interact with other adjacent domains to receive the identification mapping information of the first data pipeline from each other data control node of each other adjacent domain. The identification mapping information of the first data pipeline from each other data control node can be the identification mapping information of the first data pipeline in the first domain and each other adjacent domain, and together generate a mapping relationship table.

[0250] In one embodiment, the method further includes: the terminal receiving addresses of one or more second participating nodes in the second domain of the first data pipeline from the second data control node, wherein the previous hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the second participating nodes in the first data pipeline belongs to the first domain; the terminal determining routing information, wherein the routing information includes at least one of the following: the address of the previous hop participating node of the terminal in the first data pipeline belonging to the second domain, and the address of the next hop participating node of the terminal in the first data pipeline belonging to the second domain.

[0251] Here, the terminal receiving the addresses of one or more second participating nodes in the second domain of the first data pipeline from the second data control node can be performed simultaneously with the terminal receiving the identification mapping information of the first data pipeline from the second data control node. For example, the second data control node can send a second configuration message to the terminal, which carries the identification mapping information of the first data pipeline and the addresses of one or more second participating nodes. The relevant descriptions of the second participating nodes are the same as in the previous embodiments and will not be repeated.

[0252] The specific method by which the terminal determines the routing information is not limited in this embodiment. After determining the routing information, the terminal can also associate or correspond the routing information with the identifier of the first data pipeline in the first domain and save it locally.

[0253] It should be noted that the terminal can also obtain the data pipeline policy corresponding to the first data pipeline, associate or correspond the data pipeline policy corresponding to the first data pipeline with the identifier of the first data pipeline in the first domain and save it locally. The terminal may generate the data pipeline policy corresponding to the first data pipeline based on the first data service description information, or obtain the data pipeline policy corresponding to the first data pipeline from other devices. This embodiment does not limit it.

[0254] In some possible implementations, after receiving the identification mapping information from the first data pipeline of the second data control node, the terminal performs identification mapping and related data processing when executing task processing within the first data pipeline. The relevant processing of the terminal will be described below.

[0255] In one embodiment, the identifier mapping process is performed by an upstream node located at an edge position adjacent to the first domain and the second domain.

[0256] After the terminal receives the identifier mapping information of the first data pipeline from the second data control node, the method further includes: if the terminal determines, based on the routing information, that the next-hop participating node in the first data pipeline belongs to the second domain, the terminal determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline; the terminal sends a third data frame to the next-hop participating node, wherein the third data frame carries the identifier of the first data pipeline in the second domain.

[0257] The identifier of the first data pipeline in the second field is carried by an identifier field in the third data frame or by a reserved field in the third data frame. This third data frame can also be encapsulated based on a preset transmission protocol. The encapsulation method or location for specifically encapsulating the identifier of the first data pipeline in the second field in the third data frame is similar to the method used in the previous embodiments for specifically encapsulating the identifier of the first data pipeline in the second field in the first data frame, and therefore will not be repeated. The description of the field in the third data frame carrying the identifier of the first data pipeline in the second field is also similar to the description of the field in the previous embodiments for carrying the identifier of the first data pipeline in the second field in the first data frame, and therefore will not be repeated.

[0258] The third data frame also carries the processed data corresponding to the terminal; the method further includes: the terminal determining the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; the terminal performing data processing on the data to be processed based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal.

[0259] The data to be processed may originate from the previous participating node in the first data pipeline, meaning it can be data processed by that previous participating node. This previous participating node may belong to the second domain, which is not limited here. The terminal's data pipeline strategy corresponding to the first data pipeline may include the data processing method required by the terminal for the data to be processed, which is not limited in this embodiment. Alternatively, the data to be processed may be raw data collected by the terminal. The terminal may not process the raw data and may directly carry and send it in the third data frame; or, after collecting the raw data, the terminal may perform corresponding data processing (such as preprocessing) on ​​the raw data according to the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal.

[0260] For a next-hop participating node belonging to the second domain, this next-hop participating node can be any second participating node. After receiving the third data frame, this second participating node can determine the data pipeline policy corresponding to the first data pipeline based on the identifier of the first data pipeline in the second domain, and process the received data based on the data pipeline policy corresponding to the second participating node in the first data pipeline. Additionally, it may include: if the second participating node is the final recipient of the data, it can also return a data pipeline operation completion notification to the second data control node of the second domain; or, if the second participating node is not the final recipient of the data, it can also send its processed data to the next participating node of the first data pipeline.

[0261] Figure 12 illustrates the identification mapping process for the previous hop participating node in the adjacent domain within the first data pipeline. Taking the example of data transmission between the UE (the terminal in the first domain) and participating node X (a second participating node in the second domain), the specific steps include:

[0262] In step 1201, the UE performs data acquisition and preprocessing according to the pre-configured data pipeline policy (such as the data pipeline policy corresponding to the first data pipeline). It should be noted that before executing step 1201, both the UE and the participating node X have configured the domain DPID mapping table (i.e., the identifier mapping table).

[0263] Step 1202: According to the routing policy, the UE determines the next hop node as the participating node X in the second domain. The UE encapsulates the data into a QUIC stream data frame (i.e., the third data frame), performs domain DPID mapping to obtain the DPID of the first data pipeline in the second domain, and sets the domain DPID in the QUIC stream ID field as the identifier of the first data pipeline in the second domain.

[0264] Step 1203: The UE sends the preprocessed data to the participating node X via a QUIC stream (carrying the DPID of the first data pipeline in the second domain). For example, the UE may send the data to the participating node X via the third data frame of the QUIC stream, carrying the identifier of the first data pipeline in the second domain.

[0265] Step 1204: Participating node X determines the local data operation strategy based on the DPID of the first data pipeline in the second domain in the QUIC stream ID and processes the data.

[0266] Step 1205: If participating node X is the final recipient of the data, then participating node X returns a data pipeline operation completion notification to the second data control node of the second domain. Alternatively, if participating node X is not the final recipient of the data, it can also send its processed data to the next participating node in the first data pipeline; this is not limited here.

[0267] In one embodiment, the identifier mapping process is performed by downstream nodes located at the edge positions adjacent to the first and second domains.

[0268] After the terminal receives the identifier mapping information of the first data pipeline from the second data control node, the method further includes: the terminal receiving a fourth data frame from the previous hop participating node of the first data pipeline belonging to the second domain, wherein the fourth data frame carries the identifier of the first data pipeline in the second domain; the terminal determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline.

[0269] The identifier of the first data pipeline in the second field is carried by the identifier field in the fourth data frame or by the reserved field in the fourth data frame. This fourth data frame can also be encapsulated based on a preset transmission protocol. The encapsulation method or location for specifically encapsulating the identifier of the first data pipeline in the second field in the fourth data frame is similar to the method used in the aforementioned embodiments for specifically encapsulating the identifier of the first data pipeline in the second field in the first data frame, and therefore will not be elaborated upon further.

[0270] The fourth data frame also carries the processed data corresponding to the previous hop participating node. After the terminal determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline, the process further includes: the terminal determining the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; and the terminal processing the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal. The fourth data frame may carry the processed data corresponding to the previous hop participating node in a field used to carry frame payload or data, which is not limited here.

[0271] The terminal processes the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline, and obtains the specific processing method of the processed data corresponding to the terminal. It is similar to the processing of the first participating node in the previous embodiment. The only difference is that in this embodiment, the terminal executes the process and the data to be processed in the previous embodiment is replaced with the processed data corresponding to the previous hop participating node belonging to the second domain. Therefore, it will not be described in detail.

[0272] In some possible examples, if the identifier mapping process is performed by a downstream node located at an edge position adjacent to the first and second domains, and the terminal is the previous hop node or an upstream node, then the processing can be carried out in the manner illustrated in Figure 13. Taking the example of the UE (the terminal in the first domain) and participating node X (a second participating node in the second domain) needing to directly transmit data, the specific steps include:

[0273] Step 1301 is the same as step 1201, and will not be described again.

[0274] Step 1302: According to the routing policy, the UE determines the next hop node as the participating node X in the second domain. The UE sends the preprocessed data, which can be encapsulated as a QUIC stream. The domain DPID in the QUIC stream ID field is set to the DPID of the first data pipeline in the first domain.

[0275] Step 1303: Participating node X performs domain DPID mapping to obtain the DPID of the first data pipeline in the second domain.

[0276] Steps 1304 to 1305 are the same as steps 1204 to 1205, and will not be described again.

[0277] In one embodiment, the terminal's processing may further include: when the terminal completes the data processing operation, performing at least one of the following: releasing the identifier of the first data pipeline in the first domain; releasing the data pipeline policy corresponding to the first data pipeline; deleting the identifier mapping information of the first data pipeline; sending an identifier release request to the identifier allocation node corresponding to the terminal, wherein the identifier release request is used to instruct the identifier allocation node corresponding to the terminal to release the identifier of the first data pipeline in the first domain.

[0278] Optionally, if the terminal itself generates the identifier of the first data pipeline in the first domain, then when the terminal completes the data processing operation, it performs the following processing: releases the identifier of the first data pipeline in the first domain; releases the data pipeline policy corresponding to the first data pipeline; and deletes the identifier mapping information of the first data pipeline.

[0279] Optionally, if the identifier of the terminal's first data pipeline in the first domain is determined or assigned by the identifier allocation node corresponding to the terminal, then upon completion of the data processing operation, the following processing is performed: sending an identifier release request to the identifier allocation node corresponding to the terminal; releasing the data pipeline policy corresponding to the first data pipeline; and deleting the identifier mapping information of the first data pipeline. The description of the identifier release request is similar to that of the first identifier release request in the aforementioned embodiments. The processing by the identifier allocation node corresponding to the terminal after receiving the identifier release request is also similar to that of the first identifier allocation node in the aforementioned embodiments, and will not be repeated.

[0280] The solution provided in this application embodiment enables a terminal in the first domain to send the identifier of the first data pipeline in the first domain to the data control node in the second domain when the first data pipeline spans different domains. The terminal then receives the identifier mapping information of the first data pipeline from the second data control node. This identifier mapping information includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. This ensures the uniqueness of the identifier of the first data pipeline within each domain in scenarios where the first data pipeline spans multiple domains. This avoids the problem of participating nodes from other domains obtaining the terminal's relevant policies, ensuring inter-domain isolation and thus guaranteeing security and privacy. Furthermore, since participating nodes and terminals in different domains can know the mapping relationship of the identifier of the same data pipeline in different domains, collaborative work can be ensured among participating nodes and terminals in different domains using the same data pipeline.

[0281] Figure 14 is a schematic flowchart of an identifier mapping method according to an embodiment of this application. The method includes at least a portion of the following.

[0282] S1410, The terminal receives the identifier of the first data pipeline in the first domain from the first data control node, wherein the terminal belongs to the second domain and the first data plane control point belongs to the first domain;

[0283] S1420, The terminal sends the identifier mapping information of the first data pipeline to the first data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0284] The identification of the first data pipeline in the first domain and the related descriptions of the identification of the first data pipeline in the second domain are the same as in the previous embodiments and will not be repeated. The difference from the previous embodiments is that the terminal belongs to the second domain.

[0285] In some possible implementations, the terminal receiving the identifier of the first data pipeline in the first domain from the first data control node includes: the terminal receiving a first service request from the first data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain. The first service request also carries at least one of the following: information related to a first data service; addresses of one or more first participating nodes, wherein the previous hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain, and / or the next hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain. The description of the first service request is the same as in the previous embodiments and will not be repeated. The processing by the first data control node before sending the first service request is the same as in the previous embodiments and will not be repeated.

[0286] In one embodiment, after the terminal receives a second service request from a service request node and before the terminal sends the identifier mapping information of the first data pipeline to the first data control node, the method further includes one of the following: the terminal generates an identifier of the first data pipeline in the second domain; the terminal sends an identifier allocation request to the identifier allocation node corresponding to the terminal, and the terminal receives an identifier allocation response from the identifier allocation node corresponding to the terminal, wherein the identifier allocation response carries one of the following: the identifier of the first data pipeline in the second domain, and the identifier of the first data pipeline in the domain corresponding to the second domain.

[0287] The description of how the terminal generates the identifier of the first data pipeline in the second domain is similar to the description of how the terminal generates the identifier of the first data pipeline in the first domain in the previous embodiment. The only difference is that the terminal belongs to the second domain in this embodiment, so it will not be described again.

[0288] The description of the identifier allocation node corresponding to the terminal is similar to that in the previous embodiment, except that in this embodiment, the terminal and its corresponding identifier allocation node both belong to the second domain, so it will not be described again.

[0289] The identifier allocation request issued by the terminal is the same as that in the previous embodiment, and will not be described again.

[0290] The specific processing by which the identifier allocation node corresponding to the terminal allocates one of the identifier of the first data pipeline in the second domain and the domain-specific identifier of the first data pipeline in the second domain is similar to the processing by the second identifier allocation node in the aforementioned embodiments, and therefore will not be described in detail. Furthermore, if the identifier allocation response received by the terminal carries the domain-specific identifier of the first data pipeline in the second domain, the terminal can combine the identifier of the second domain and the domain-specific identifier of the first data pipeline in the second domain to obtain the identifier of the first data pipeline in the second domain. The processing by which the terminal combines these identifiers to obtain the identifier of the first data pipeline in the second domain is similar to the processing method of the second data control node in the aforementioned embodiments, and will not be described in detail either.

[0291] In one embodiment, after the terminal receives a first service request from a first data control node, the method further includes: the terminal determining routing information, wherein the routing information includes at least one of the following: the address of the previous hop participating node corresponding to the terminal in the first data pipeline and belonging to the first domain, and the address of the next hop participating node corresponding to the terminal in the first data pipeline and belonging to the first domain. The method by which the terminal determines the routing information can be the same as the method by which the first data control node determines the routing information corresponding to any first participating node in the first domain in the aforementioned embodiments, and therefore will not be elaborated upon. The specific method by which the terminal determines the routing information is not limited in this embodiment. After determining the routing information, the terminal can also associate or correspond the routing information with the identifier of the first data pipeline in the second domain and store it locally.

[0292] It should be noted that the terminal can also obtain the data pipeline policy corresponding to the first data pipeline, associate or correspond the data pipeline policy corresponding to the first data pipeline with the identifier of the first data pipeline in the second domain and save it locally. This embodiment will not elaborate on this.

[0293] This embodiment does not limit the processing related to the terminal generating the identifier mapping information of the first data pipeline. After generating the identifier mapping information of the first data pipeline, the terminal sends the identifier mapping information of the first data pipeline to the first data control node. In addition, when sending the identifier mapping information of the first data pipeline to the first data control node, the terminal can also send its own identifier to the first data control node, so that the first data control node can generate corresponding routing information. Accordingly, the processing of the first data control node after receiving the identifier mapping information of the first data pipeline can be the same as in the previous embodiment, and will not be described again.

[0294] In some possible implementations, after the terminal sends out the identification mapping information of the first data pipeline, the terminal will perform identification mapping and related data processing when performing task processing in the first data pipeline. The relevant processing of the terminal will be described below.

[0295] In one embodiment, the identifier mapping process is performed by an upstream node located at an edge position adjacent to the first domain and the second domain.

[0296] After the terminal sends the identifier mapping information of the first data pipeline to the first data control node, the method further includes: if the terminal determines, based on the routing information, that the next-hop participating node in the first data pipeline belongs to the first domain, the terminal determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline; the terminal sends a fifth data frame to the next-hop participating node, wherein the fifth data frame carries the identifier of the first data pipeline in the first domain.

[0297] The identifier of the first data pipeline in the first field is carried by the identifier field in the fifth data frame or by the reserved field in the fifth data frame. This fifth data frame can also be encapsulated based on a preset transmission protocol, which will not be elaborated upon here.

[0298] The fifth data frame also carries the processed data corresponding to the terminal; the method further includes: the terminal determining the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the second domain; the terminal processing the data to be processed based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal. The description of the data to be processed is similar to that in the previous embodiment, the only difference being that the previous participating node may be in the first domain, so it will not be repeated. For the next-hop participating node belonging to the first domain, this next-hop participating node can be any first participating node within the first domain. The processing of this first participating node after receiving the fifth data frame is similar to the processing of the second participating node after receiving the third data frame in the previous embodiment, and will not be repeated.

[0299] In one embodiment, the identifier mapping process is performed by downstream nodes located at the edge positions adjacent to the first and second domains.

[0300] After the terminal sends the identifier mapping information of the first data pipeline to the first data control node, the method further includes: the terminal receiving a sixth data frame from the previous hop participating node of the first data pipeline belonging to the first domain, wherein the sixth data frame carries the identifier of the first data pipeline in the first domain; the terminal determining the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline.

[0301] The identifier of the first data pipeline in the first field is carried by the identifier field in the sixth data frame or by the reserved field in the sixth data frame. This sixth data frame can also be encapsulated based on a preset transmission protocol, which will not be elaborated further.

[0302] The sixth data frame also carries the processed data corresponding to the previous hop participating node. After the terminal determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline, the method further includes: the terminal determining the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the second domain; and the terminal processing the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal. The specific processing method of the terminal processing the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal is similar to that in the previous embodiment and will not be described in detail.

[0303] The terminal's processing may further include: when the terminal completes the data processing operation, performing at least one of the following: releasing the identifier of the first data pipeline in the second domain; releasing the data pipeline policy corresponding to the first data pipeline; deleting the identifier mapping information of the first data pipeline; sending an identifier release request to the identifier allocation node corresponding to the terminal, wherein the identifier release request is used to instruct the identifier allocation node corresponding to the terminal to release the identifier of the first data pipeline in the second domain.

[0304] Optionally, if the identifier of the first data pipeline generated by the terminal itself is in the second domain, then upon completion of the data processing operation, the terminal performs the following steps: releases the identifier of the first data pipeline in the second domain; releases the data pipeline policy corresponding to the first data pipeline; and deletes the identifier mapping information of the first data pipeline. Optionally, if the identifier of the terminal's first data pipeline in the second domain is determined or allocated by the identifier allocation node corresponding to the terminal, then upon completion of the data processing operation, the terminal performs the following steps: sends an identifier release request to the identifier allocation node corresponding to the terminal; releases the data pipeline policy corresponding to the first data pipeline; and deletes the identifier mapping information of the first data pipeline. The explanation regarding the identifier release request is similar to that of the second identifier release request in the aforementioned embodiment and will not be repeated.

[0305] The solution provided in this application embodiment enables a second-domain terminal to receive the identifier of the first data pipeline in the first domain from the data control node of the first domain when the first data pipeline spans different domains. The terminal then generates identifier mapping information for the first data pipeline, which includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. This ensures the uniqueness of the identifier of the first data pipeline within each domain in scenarios where the first data pipeline spans multiple domains, thereby avoiding the problem of participating nodes from other domains obtaining the terminal's relevant policies. It guarantees inter-domain isolation, thus ensuring security and privacy. Furthermore, since participating nodes and terminals in different domains can know the mapping relationship of the identifier of the same data pipeline in different domains, it ensures that participating nodes and terminals in different domains working together on the same data pipeline can achieve collaborative operation.

[0306] Figure 15 is a schematic diagram of the composition structure of a first data control node according to an embodiment of this application, including:

[0307] The first communication unit 1501 is configured to receive identification mapping information of a first data pipe from a second data control node, wherein the first data control node belongs to a first domain and the second data control node belongs to a second domain, and the identification mapping information of the first data pipe includes the mapping relationship between the identifier of the first data pipe in the first domain and the identifier of the first data pipe in the second domain; and to send the identification mapping information of the first data pipe to one or more first participating nodes of the first data pipe in the first domain.

[0308] The preceding hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain, and / or the next hop participating node of each of the first participating nodes in the first data pipeline belongs to the second domain.

[0309] The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain and the identifier of the first data pipeline in the domain corresponding to the first domain; the identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain.

[0310] The first communication unit is configured to send a first identifier allocation request to the first identifier allocation node; and receive a first identifier allocation response from the first identifier allocation node, wherein the first identifier allocation response carries one of the following: the identifier of the first data pipeline in the first domain, or the identifier of the first data pipeline in the domain corresponding to the first domain.

[0311] The first communication unit is configured to send a first service request to the second data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain.

[0312] The first service request also carries at least one of the following: information related to the first data service, which is used by the second data control node to determine one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain; and the address of the one or more first participating nodes.

[0313] As shown in Figure 15, it also includes: a first processing unit 1502, used to determine one or more participating nodes of the first data pipeline corresponding to the first data service in the first domain based on the relevant information of the first data service, wherein the one or more participating nodes of the first data pipeline in the first domain include the one or more first participating nodes.

[0314] The first communication unit is configured to receive a second service request from a service request node, wherein the second service request carries information related to the first data service.

[0315] The first communication unit is configured to send the identifier of the first data pipeline in the first domain to one or more participating nodes of the first data pipeline in the first domain.

[0316] The first communication unit is configured to receive the addresses of one or more second participating nodes in the second domain of the first data pipeline from the second data control node, wherein the previous hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain.

[0317] The first communication unit is configured to send routing information corresponding to each of the one or more first participating nodes to each of the first participating nodes, wherein the routing information corresponding to each of the first participating nodes includes at least one of the following: the address of the previous participating node in the first data pipeline belonging to the second domain, and the address of the next participating node in the first data pipeline belonging to the second domain.

[0318] Upon receiving an operation end message from one or more first participating nodes, the first communication unit is configured to send a first identifier release request to the first identifier allocation node, wherein the first identifier release request is configured to instruct the first identifier allocation node to release the identifier of the first data pipeline in the first domain; and / or, the first processing unit is configured to delete the identifier mapping information of the first data pipeline.

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

[0320] The second communication unit 1601 is used to receive the identification mapping information of the first data pipeline from the first data control node, wherein the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain, the first participating node is the participating node of the first data pipeline in the first domain, and the first data control node belongs to the first domain.

[0321] The preceding participating node of the first participating node in the first data pipeline belongs to the second domain, and / or the next participating node of the first participating node in the first data pipeline belongs to the second domain.

[0322] The second communication unit is used to receive the identifier of the first data pipeline in the first domain from the first data control node.

[0323] The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain and the identifier of the first data pipeline in the domain corresponding to the first domain; the identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain.

[0324] As shown in Figure 16, it further includes: a second processing unit 1602, used to determine the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline when the routing information corresponding to the first participating node determines that the next-hop participating node in the first data pipeline belongs to the second domain.

[0325] The second communication unit is used to send a first data frame to the next-hop participating node, wherein the first data frame carries the identifier of the first data pipeline in the second domain.

[0326] The identifier of the first data pipeline in the second field is carried by the identifier field in the first data frame or by the reserved field in the first data frame.

[0327] The first data frame also carries the processed data corresponding to the first participating node.

[0328] The second processing unit is configured to determine the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; and to process the data to be processed based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the first participating node.

[0329] The second communication unit is configured to receive a second data frame from the previous hop participating node of the first data pipeline belonging to the second domain, wherein the second data frame carries the identifier of the first data pipeline in the second domain;

[0330] The second processing unit is configured to determine the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline.

[0331] The identifier of the first data pipeline in the second field is carried by the identifier field in the second data frame or by the reserved field in the second data frame.

[0332] The second data frame also carries the processed data corresponding to the previous hop participating node.

[0333] The second processing unit is configured to determine the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; and to process the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the first participating node.

[0334] The second communication unit is configured to receive routing information corresponding to the first participating node from the first data control node, wherein the routing information corresponding to the first participating node includes at least one of the following: the address of the previous hop participating node corresponding to the first participating node in the first data pipeline that belongs to the second domain, and the address of the next hop participating node corresponding to the first participating node in the first data pipeline that belongs to the second domain.

[0335] The second communication unit is used to send an operation end message to the first data control node.

[0336] The second processing unit is configured to perform at least one of the following: release the identifier of the first data pipeline in the first domain; release the data pipeline policy corresponding to the first data pipeline; delete the identifier mapping information of the first data pipeline.

[0337] Figure 17 is a schematic diagram of the composition structure of a second data control node according to an embodiment of this application, including:

[0338] The third communication unit 1701 is used to send the identification mapping information of the first data pipeline to the first data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain; and to send the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain.

[0339] The preceding hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the second participating nodes in the first data pipeline belongs to the first domain.

[0340] The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain and the identifier of the first data pipeline in the domain corresponding to the first domain; the identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain.

[0341] The third communication unit is configured to send a second identifier allocation request to the second identifier allocation node; and receive a second identifier allocation response from the second identifier allocation node, wherein the second identifier allocation response carries one of the following: the identifier of the first data pipeline in the second domain, or the identifier of the first data pipeline in the domain corresponding to the second domain.

[0342] The third communication unit is configured to receive a first service request from the first data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain.

[0343] The first service request also carries at least one of the following: information related to the first data service; the address of one or more first participating nodes, wherein the previous hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain, and / or the next hop participating node of each of the first participating nodes in the first data pipeline belongs to the second domain.

[0344] As shown in Figure 17, it further includes: a third processing unit 1702, used to determine one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain based on the relevant information of the first data service, wherein the one or more participating nodes of the first data pipeline in the second domain include the one or more second participating nodes.

[0345] The third communication unit is configured to perform at least one of the following: send the identifier of the first data pipeline in the second domain to one or more participating nodes of the first data pipeline in the second domain; send routing information corresponding to each of the one or more second participating nodes to each of the second participating nodes, wherein the routing information corresponding to each of the second participating nodes includes at least one of the following: the address of the previous hop participating node in the first data pipeline belonging to the first domain corresponding to each of the second participating nodes, and the address of the next hop participating node in the first data pipeline belonging to the first domain corresponding to each of the second participating nodes.

[0346] The third communication unit is used to send the addresses of the one or more second participating nodes to the first data control node.

[0347] Upon receiving an operation end message from one or more second participating nodes, the third communication unit is configured to send a second identifier release request to the second identifier allocation node, wherein the second identifier release request is configured to instruct the second identifier allocation node to release the identifier of the first data pipeline in the second domain; and / or, the third processing unit is configured to delete the identifier mapping information of the first data pipeline.

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

[0349] The fourth communication unit 1801 is used to send the identifier of the first data pipeline in the first domain to the second data control node, wherein the second data control node belongs to the second domain and the terminal belongs to the first domain; and to receive the identifier mapping information of the first data pipeline from the second data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0350] The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain and the identifier of the first data pipeline in the domain corresponding to the first domain; the identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain.

[0351] As shown in Figure 18, the terminal further includes: a fourth processing unit 1802, used to generate an identifier for the first data pipeline in the first domain; or, the fourth communication unit, used to send an identifier allocation request to the identifier allocation node corresponding to the terminal and receive an identifier allocation response from the identifier allocation node corresponding to the terminal, wherein the identifier allocation response carries one of the following: the identifier of the first data pipeline in the first domain, or the identifier of the first data pipeline in the domain corresponding to the first domain.

[0352] The fourth communication unit is used to send a first service request to the second data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain.

[0353] The first service request also carries at least one of the following: information related to the first data service, which is used by the second data control node to determine one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain; and the identifier of the terminal.

[0354] The fourth communication unit is used to receive a second service request from a service request node, wherein the second service request carries information related to the first data service.

[0355] The fourth communication unit is configured to receive the addresses of one or more second participating nodes in the second domain from the second data control node in the first data pipeline, wherein the previous hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain; the fourth processing unit is configured to determine routing information, wherein the routing information includes at least one of the following: the address of the previous hop participating node corresponding to the terminal in the first data pipeline that belongs to the second domain, and the address of the next hop participating node corresponding to the terminal in the first data pipeline that belongs to the second domain.

[0356] The fourth processing unit is configured to determine the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline, when the next-hop participating node in the first data pipeline belongs to the second domain based on the routing information; the fourth communication unit is configured to send a third data frame to the next-hop participating node, wherein the third data frame carries the identifier of the first data pipeline in the second domain.

[0357] The identifier of the first data pipeline in the second field is carried by the identifier field in the third data frame or by the reserved field in the third data frame.

[0358] The fourth processing unit is used to determine the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; and to process the data to be processed based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal.

[0359] The fourth communication unit is configured to receive a fourth data frame from the previous hop participating node of the first data pipeline belonging to the second domain, wherein the fourth data frame carries the identifier of the first data pipeline in the second domain.

[0360] The fourth processing unit is used to determine the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline.

[0361] The identifier of the first data pipeline in the second field is carried by the identifier field in the fourth data frame or by the reserved field in the fourth data frame.

[0362] The fourth data frame also carries the processed data corresponding to the previous hop participating node; after determining the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline, the fourth processing unit performs the following: determining the data pipeline policy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; and processing the processed data corresponding to the previous hop participating node based on the data pipeline policy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal.

[0363] When the fourth processing unit completes the data processing operation, it performs at least one of the following: releasing the identifier of the first data pipeline in the first domain; releasing the data pipeline policy corresponding to the first data pipeline; deleting the identifier mapping information of the first data pipeline; sending an identifier release request to the identifier allocation node corresponding to the terminal, wherein the identifier release request is used to instruct the identifier allocation node corresponding to the terminal to release the identifier of the first data pipeline in the first domain.

[0364] In one embodiment, a terminal includes:

[0365] The fourth communication unit is configured to receive the identifier of the first data pipeline in the first domain from the first data control node, wherein the terminal belongs to the second domain and the first data plane control point belongs to the first domain; and to send the identifier mapping information of the first data pipeline to the first data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain.

[0366] The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain and the identifier of the first data pipeline in the domain corresponding to the first domain; the identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain.

[0367] The terminal further includes a fourth processing unit, which is configured to generate an identifier for the first data pipeline in the second domain; or, the fourth communication unit is configured to send an identifier allocation request to the identifier allocation node corresponding to the terminal and receive an identifier allocation response from the identifier allocation node corresponding to the terminal, wherein the identifier allocation response carries one of the following: the identifier of the first data pipeline in the second domain, or the identifier of the first data pipeline in the domain corresponding to the second domain.

[0368] The fourth communication unit is configured to receive a first service request from the first data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain.

[0369] The first service request also carries at least one of the following: information related to the first data service; the address of one or more first participating nodes, wherein the previous hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain, and / or the next hop participating node of each of the first participating nodes in the first data pipeline belongs to the second domain.

[0370] The fourth processing unit is used to determine routing information, wherein the routing information includes at least one of the following: the address of the previous hop participating node corresponding to the terminal in the first data pipeline that belongs to the first domain, and the address of the next hop participating node corresponding to the terminal in the first data pipeline that belongs to the first domain.

[0371] The fourth processing unit determines the identifier of the first data pipeline in the first domain based on the routing information, when the next-hop participating node in the first data pipeline belongs to the first domain. Based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline, the fourth processing unit determines the identifier of the first data pipeline in the first domain.

[0372] The fourth communication unit is used to send a fifth data frame to the next-hop participating node, wherein the fifth data frame carries the identifier of the first data pipeline in the first domain.

[0373] The identifier of the first data pipeline in the first domain is carried by the identifier field in the fifth data frame or by the reserved field in the fifth data frame.

[0374] The fourth processing unit is used to determine the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the second domain; and to process the data to be processed based on the data pipeline strategy corresponding to the first data pipeline to obtain the processed data corresponding to the terminal.

[0375] The fourth communication unit is configured to receive a sixth data frame from the previous hop participating node of the first data pipeline belonging to the first domain, wherein the sixth data frame carries the identifier of the first data pipeline in the first domain.

[0376] The fourth processing unit is used to determine the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline.

[0377] The identifier of the first data pipeline in the first domain is carried by the identifier field in the sixth data frame or by the reserved field in the sixth data frame.

[0378] The sixth data frame also carries the processed data corresponding to the previous hop participating node; after the fourth processing unit determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline, it performs the following: based on the identifier of the first data pipeline in the second domain, it determines the data pipeline policy corresponding to the first data pipeline; based on the data pipeline policy corresponding to the first data pipeline, it processes the processed data corresponding to the previous hop participating node to obtain the processed data corresponding to the terminal.

[0379] When the fourth processing unit completes the data processing operation, it performs at least one of the following: releasing the identifier of the first data pipeline in the second domain; releasing the data pipeline policy corresponding to the first data pipeline; deleting the identifier mapping information of the first data pipeline; sending an identifier release request to the identifier allocation node corresponding to the terminal, wherein the identifier release request is used to instruct the identifier allocation node corresponding to the terminal to release the identifier of the first data pipeline in the second domain.

[0380] The device in this application embodiment can realize the corresponding functions of the devices in the foregoing configuration 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.).

[0381] Figure 19 is a schematic structural diagram of a communication device 1900 according to an embodiment of this application. The communication device 1900 includes a processor 1910, which can call and run computer programs from a memory to enable the communication device 1900 to implement the methods in the embodiments of this application. In one possible implementation, the communication device 1900 may further include a memory 1920. The processor 1910 can call and run computer programs from the memory 1920 to enable the communication device 1900 to implement the methods in the embodiments of this application. The memory 1920 may be a separate device independent of the processor 1910, or it may be integrated into the processor 1910. In one possible implementation, the communication device 1900 may further include a transceiver 1930, which the processor 1910 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 1930 may include a transmitter and a receiver. The transceiver 1930 may further include antennas, and the number of antennas may be one or more.

[0382] In one possible implementation, the communication device 1900 may be the first data control node, the first participating node, the second data control node, or the terminal in the embodiments of this application. The communication device 1900 may implement the corresponding processes implemented by the first data control node, the first participating node, the second data control node, or the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0383] Figure 20 is a schematic structural diagram of a chip 2000 according to an embodiment of this application. The chip 2000 includes a processor 2010, 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 2000 may further include a memory 2020. The processor 2010 can call and run computer programs from the memory 2020 to implement the methods executed by a first data control node, a first participating node, a second data control node, or a terminal in the embodiments of this application. The memory 2020 may be a separate device independent of the processor 2010, or it may be integrated into the processor 2010. In one possible implementation, the chip 2000 may further include an input interface 2030. The processor 2010 can control the input interface 2030 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 2000 may further include an output interface 2040. The processor 2010 can control the output interface 2040 to communicate with other devices or chips, specifically, it can output information or data to other devices or chips.

[0384] In one possible implementation, the chip can be applied to the first data control node, or the first participating node, or the second data control node, or the terminal in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first data control node, or the first participating node, or the second data control node, or the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0385] 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

An identifier mapping method, comprising: The first data control node receives the identifier mapping information of the first data pipeline from the second data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. The first data control node sends the identification mapping information of the first data pipeline to one or more first participating nodes in the first domain. According to the method of claim 1, wherein, The preceding hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain, and / or the next hop participating node of each of the first participating nodes in the first data pipeline belongs to the second domain. The method according to claim 1 or 2, wherein, The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain, and the identifier of the first data pipeline in the domain corresponding to the first domain; The identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain. The method according to claim 3, wherein, Before the first data control node receives the identifier mapping information from the second data control node, it also includes: The first data control node sends a first identifier allocation request to the first identifier allocation node; The first data control node receives a first identifier allocation response from the first identifier allocation node, wherein the first identifier allocation response carries one of the following: the identifier of the first data pipeline in the first domain, or the identifier of the first data pipeline in the domain corresponding to the first domain. The method according to claim 4, wherein, After receiving the first identifier allocation response from the first identifier allocation node, the first data control node further includes: The first data control node sends a first service request to the second data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain. The method according to claim 5, wherein, The first service request also carries at least one of the following: The relevant information of the first data service is used by the second data control node to determine one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain. The addresses of the one or more first participating nodes. The method according to claim 5 or 6, wherein, Before the first data control node sends the first service request to the second data control node, it also includes: The first data control node receives a second service request from the service request node, wherein the second service request carries information related to the first data service; Based on the relevant information of the first data service, the first data control node determines one or more participating nodes of the first data pipeline corresponding to the first data service within the first domain, wherein the one or more participating nodes of the first data pipeline within the first domain include the one or more first participating nodes. The method according to any one of claims 4-7, wherein, After receiving the first identifier allocation response from the first identifier allocation node, the first data control node further includes: The first data control node sends the identifier of the first data pipeline in the first domain to one or more participating nodes of the first data pipeline in the first domain. The method according to any one of claims 1-8, wherein, The method further includes: The first data control node receives the addresses of one or more second participating nodes in the second domain of the first data pipeline from the second data control node, wherein the previous hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain. The method according to claim 9, wherein, After the first data control node receives the addresses of one or more second participating nodes in the second domain of the first data pipeline from the second data control node, it further includes: The first data control node sends routing information corresponding to each of the one or more first participating nodes to each of the first participating nodes, wherein the routing information corresponding to each first participating node includes at least one of the following: the address of the previous participating node in the first data pipeline that belongs to the second domain, and the address of the next participating node in the first data pipeline that belongs to the second domain. The method according to any one of claims 1-10, wherein, After the first data control node sends the identification mapping information of the first data pipeline to one or more first participating nodes in the first domain, the method further includes: Upon receiving an operation completion message from one or more first participating nodes, the first data control node performs at least one of the following: Send a first identifier release request to the first identifier allocation node, wherein the first identifier release request is used to instruct the first identifier allocation node to release the identifier of the first data pipeline in the first domain; Delete the identifier mapping information of the first data pipeline. An identifier mapping method, comprising: The first participating node receives the identifier mapping information of the first data pipeline from the first data control node. The identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. The first participating node is a participating node of the first data pipeline in the first domain, and the first data control node belongs to the first domain. The method according to claim 12, wherein, The preceding participating node of the first participating node in the first data pipeline belongs to the second domain, and / or the next participating node of the first participating node in the first data pipeline belongs to the second domain. The method according to any one of claims 12 or 13, wherein, The method further includes: The first participating node receives the identifier of the first data pipeline in the first domain from the first data control node. The method according to any one of claims 12-14, wherein, The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain, and the identifier of the first data pipeline in the domain corresponding to the first domain; The identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain. The method according to any one of claims 12-15, wherein, After the first participating node receives the identifier mapping information of the first data pipeline from the first data control node, it further includes: If, based on the routing information corresponding to the first participating node, it is determined that the next-hop participating node in the first data pipeline belongs to the second domain, the first participating node determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline. The first participating node sends a first data frame to the next-hop participating node, wherein the first data frame carries the identifier of the first data pipeline in the second field. The method according to claim 16, wherein, The identifier of the first data pipeline in the second field is carried by the identifier field in the first data frame or by the reserved field in the first data frame. The method according to claim 16 or 17, wherein, The first data frame also carries the processed data corresponding to the first participating node. The method according to claim 18, wherein, The method further includes: The first participating node determines the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; The first participating node processes the data to be processed based on the data pipeline strategy corresponding to the first data pipeline, and obtains the processed data corresponding to the first participating node. The method according to any one of claims 12-15, wherein, After the first participating node receives the identifier mapping information of the first data pipeline from the first data control node, it further includes: The first participating node receives a second data frame from the previous participating node of the first data pipeline that belongs to the second domain, wherein the second data frame carries the identifier of the first data pipeline in the second domain; The first participating node determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline. The method according to claim 20, wherein, The identifier of the first data pipeline in the second field is carried by the identifier field in the second data frame or by the reserved field in the second data frame. The method according to claim 20 or 21, wherein, The second data frame also carries the processed data corresponding to the previous hop participating node. The method according to claim 22, wherein, After the first participating node determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline, it further includes: The first participating node determines the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain; The first participating node processes the processed data corresponding to the previous participating node based on the data pipeline strategy corresponding to the first data pipeline, and obtains the processed data corresponding to the first participating node. The method according to any one of claims 12-23, wherein, The method further includes: The first participating node receives routing information corresponding to the first participating node from the first data control node, wherein the routing information corresponding to the first participating node includes at least one of the following: the address of the previous participating node corresponding to the first participating node in the first data pipeline that belongs to the second domain, and the address of the next participating node corresponding to the first participating node that belongs to the second domain in the first data pipeline. The method according to any one of claims 16-23, wherein, Also includes: The first participating node sends an operation completion message to the first data control node. The method according to claim 25, wherein, After the first participating node sends an operation completion message to the first data control node, it further includes at least one of the following: The first participating node releases the identifier of the first data pipeline in the first domain; The first participating node releases the data pipeline strategy corresponding to the first data pipeline. The first participating node deletes the identifier mapping information of the first data pipeline. An identifier mapping method, comprising: The second data control node sends the identifier mapping information of the first data pipeline to the first data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. The second data control node sends the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain. The method according to claim 27, wherein, The preceding hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the second participating nodes in the first data pipeline belongs to the first domain. The method according to claim 27 or 28, wherein, The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain, and the identifier of the first data pipeline in the domain corresponding to the first domain; The identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain. The method according to claim 29, wherein, Before the second data control node sends the identifier mapping information of the first data pipeline to the first data control node, it also includes: The second data control node sends a second identifier allocation request to the second identifier allocation node; The second data control node receives a second identifier allocation response from the second identifier allocation node, wherein the second identifier allocation response carries one of the following: the identifier of the first data pipeline in the second domain, or the identifier of the first data pipeline in the domain corresponding to the second domain. The method according to claim 30, wherein, Before the second data control node sends the second identifier allocation request to the second identifier allocation node, it also includes: The second data control node receives a first service request from the first data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain. The method according to claim 31, wherein, The first service request also carries at least one of the following: Information related to First Data Services; The addresses of one or more first participating nodes, wherein the previous hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain, and / or the next hop participating node of each of the first participating nodes in the first data pipeline belongs to the second domain. The method according to claim 32, wherein, After receiving the first service request from the first data control node, the second data control node further includes: Based on the relevant information of the first data service, the second data control node determines one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain, wherein the one or more participating nodes of the first data pipeline in the second domain include the one or more second participating nodes. The method according to claim 32 or 33, wherein, After receiving the second identifier allocation response from the second identifier allocation node, the second data control node further includes at least one of the following: The second data control node sends the identifier of the first data pipeline in the second domain to one or more participating nodes of the first data pipeline in the second domain; The second data control node sends routing information corresponding to each of the one or more second participating nodes to each of the second participating nodes, wherein the routing information corresponding to each second participating node includes at least one of the following: the address of the previous participating node in the first data pipeline belonging to the first domain, and the address of the next participating node in the first data pipeline belonging to the first domain. The method according to any one of claims 25-34, wherein, The method further includes: The second data control node sends the addresses of the one or more second participating nodes to the first data control node. The method according to any one of claims 25-35, wherein, After the second data control node sends the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain, the method further includes: Upon receiving an operation completion message from one or more of the second participating nodes, the second data control node performs at least one of the following: Send a second identifier release request to the second identifier allocation node, wherein the second identifier release request is used to instruct the second identifier allocation node to release the identifier of the first data pipeline in the second domain; Delete the identifier mapping information of the first data pipeline. An identifier mapping method, comprising: The terminal sends the identifier of the first data pipeline in the first domain to the second data control node, wherein the second data control node belongs to the second domain and the terminal belongs to the first domain; The terminal receives identification mapping information of the first data pipeline from the second data control node, wherein the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. The method according to claim 37, wherein, The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain, and the identifier of the first data pipeline in the domain corresponding to the first domain; The identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain. The method according to claim 37 or 38, wherein, Before the terminal sends the first data pipeline to the second data control node and the identifier of the first field, it also includes one of the following: The terminal generates the identifier of the first data pipeline in the first domain; The terminal sends an identifier allocation request to the identifier allocation node corresponding to the terminal, and the terminal receives an identifier allocation response from the identifier allocation node corresponding to the terminal, wherein the identifier allocation response carries one of the following: the identifier of the first data pipeline in the first domain, or the identifier of the first data pipeline in the domain corresponding to the first domain. The method according to any one of claims 37-39, wherein, The terminal sends the identifier of the first data pipeline in the first domain to the second data control node, including: The terminal sends a first service request to the second data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain. The method according to claim 40, wherein, The first service request also carries at least one of the following: information related to the first data service, which is used by the second data control node to determine one or more participating nodes of the first data pipeline corresponding to the first data service in the second domain; and the identifier of the terminal. The method according to any one of claims 37-41, wherein, Before the terminal sends the first data pipeline to the second data control node and the identifier of the first field, it also includes: The terminal receives a second service request from a service request node, wherein the second service request carries information related to the first data service. The method according to any one of claims 37-42, wherein, The method further includes: The terminal receives the addresses of one or more second participating nodes in the second domain of the first data pipeline from the second data control node, wherein the previous hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain, and / or the next hop participating node of each of the one or more second participating nodes in the first data pipeline belongs to the first domain. The terminal determines routing information, wherein the routing information includes at least one of the following: the address of the previous hop participating node corresponding to the terminal in the first data pipeline that belongs to the second domain, and the address of the next hop participating node corresponding to the terminal in the first data pipeline that belongs to the second domain. The method according to any one of claims 37-43, wherein, After receiving the identification mapping information of the first data pipeline from the second data control node, the terminal further includes: When the terminal determines, based on routing information, that the next-hop participating node in the first data pipeline belongs to the second domain, the terminal determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline. The terminal sends a third data frame to the next-hop participating node, wherein the third data frame carries the identifier of the first data pipeline in the second domain. The method according to claim 44, wherein, The identifier of the first data pipeline in the second field is carried by the identifier field in the third data frame or by the reserved field in the third data frame. The method according to claim 44 or 45, wherein, The third data frame also carries processed data corresponding to the terminal; the method further includes: The terminal determines the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain. The terminal processes the data to be processed based on the data pipeline strategy corresponding to the first data pipeline, and obtains the processed data corresponding to the terminal. The method according to any one of claims 37-43, wherein, After receiving the identification mapping information of the first data pipeline from the second data control node, the terminal further includes: The terminal receives a fourth data frame from the previous participating node of the first data pipeline that belongs to the second domain, wherein the fourth data frame carries the identifier of the first data pipeline in the second domain; The terminal determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline. The method according to claim 47, wherein, The identifier of the first data pipeline in the second field is carried by the identifier field in the fourth data frame or by the reserved field in the fourth data frame. The method according to claim 47 or 48, wherein, The fourth data frame also carries the processed data corresponding to the previous hop participating node; after the terminal determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline, it further includes: The terminal determines the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the first domain. The terminal processes the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline, and obtains the processed data corresponding to the terminal. The method according to any one of claims 37-49, wherein, The method further includes: When the terminal completes the data processing operation, it performs at least one of the following: releasing the identifier of the first data pipeline in the first domain; releasing the data pipeline policy corresponding to the first data pipeline; deleting the identifier mapping information of the first data pipeline; sending an identifier release request to the identifier allocation node corresponding to the terminal, wherein the identifier release request is used to instruct the identifier allocation node corresponding to the terminal to release the identifier of the first data pipeline in the first domain. An identifier mapping method, comprising: The terminal receives the identifier of the first data pipeline in the first domain from the first data control node, wherein the terminal belongs to the second domain and the first data plane control point belongs to the first domain; The terminal sends the identifier mapping information of the first data pipeline to the first data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. The method according to claim 51, wherein, The identifier of the first data pipeline in the first domain consists of the following parts: the identifier of the first domain, and the identifier of the first data pipeline in the domain corresponding to the first domain; The identifier of the first data pipeline in the second domain consists of the following parts: the identifier of the second domain and the identifier of the first data pipeline in the domain corresponding to the second domain. The method according to claim 51 or 52, wherein, Before the terminal sends the identifier mapping information of the first data pipeline to the first data control node, it also includes one of the following: The terminal generates the identifier of the first data pipeline in the second domain; The terminal sends an identifier allocation request to the identifier allocation node corresponding to the terminal, and the terminal receives an identifier allocation response from the identifier allocation node corresponding to the terminal, wherein the identifier allocation response carries one of the following: the identifier of the first data pipeline in the second domain, or the identifier of the first data pipeline in the domain corresponding to the second domain. The method according to any one of claims 51-53, wherein, The terminal receives the identifier of the first data pipeline in the first domain from the first data control node, including: The terminal receives a first service request from a first data control node, wherein the first service request carries the identifier of the first data pipeline in the first domain. The method according to claim 54, wherein, The first service request also carries at least one of the following: information related to the first data service; the address of one or more first participating nodes, wherein the previous hop participating node of each of the one or more first participating nodes in the first data pipeline belongs to the second domain, and / or the next hop participating node of each of the first participating nodes in the first data pipeline belongs to the second domain. The method according to claim 54, wherein, After receiving the first service request from the first data control node, the terminal further includes: The terminal determines routing information, wherein the routing information includes at least one of the following: the address of the previous hop participating node corresponding to the terminal in the first data pipeline and belonging to the first domain, and the address of the next hop participating node corresponding to the terminal in the first data pipeline and belonging to the first domain. The method according to any one of claims 51-56, wherein, After the terminal sends the identifier mapping information of the first data pipeline to the first data control node, it further includes: When the terminal determines, based on routing information, that the next-hop participating node in the first data pipeline belongs to the first domain, the terminal determines the identifier of the first data pipeline in the first domain based on the identifier of the first data pipeline in the second domain and the identifier mapping information of the first data pipeline. The terminal sends a fifth data frame to the next-hop participating node, wherein the fifth data frame carries the identifier of the first data pipeline in the first domain. The method according to claim 57, wherein, The identifier of the first data pipeline in the first domain is carried by the identifier field in the fifth data frame or by the reserved field in the fifth data frame. The method according to claim 57 or 58, wherein, The fifth data frame also carries processed data corresponding to the terminal; the method further includes: The terminal determines the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the second domain. The terminal processes the data to be processed based on the data pipeline strategy corresponding to the first data pipeline, and obtains the processed data corresponding to the terminal. The method according to any one of claims 51-56, wherein, After the terminal sends the identifier mapping information of the first data pipeline to the first data control node, it further includes: The terminal receives a sixth data frame from the previous participating node of the first data pipeline that belongs to the first domain, wherein the sixth data frame carries the identifier of the first data pipeline in the first domain. The terminal determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline. The method according to claim 60, wherein, The identifier of the first data pipeline in the first domain is carried by the identifier field in the sixth data frame or by the reserved field in the sixth data frame. The method according to claim 60 or 61, wherein, The sixth data frame also carries the processed data corresponding to the previous hop participating node; after the terminal determines the identifier of the first data pipeline in the second domain based on the identifier of the first data pipeline in the first domain and the identifier mapping information of the first data pipeline, it further includes: The terminal determines the data pipeline strategy corresponding to the first data pipeline based on the identifier of the first data pipeline in the second domain. The terminal processes the processed data corresponding to the previous hop participating node based on the data pipeline strategy corresponding to the first data pipeline, and obtains the processed data corresponding to the terminal. The method according to any one of claims 51-62, wherein, The method further includes: When the terminal completes the data processing operation, it performs at least one of the following: releasing the identifier of the first data pipeline in the second domain; releasing the data pipeline policy corresponding to the first data pipeline; deleting the identifier mapping information of the first data pipeline; sending an identifier release request to the identifier allocation node corresponding to the terminal, wherein the identifier release request is used to instruct the identifier allocation node corresponding to the terminal to release the identifier of the first data pipeline in the second domain. A first data control node includes: The first communication unit is configured to receive identification mapping information of a first data pipe from a second data control node, wherein the first data control node belongs to a first domain and the second data control node belongs to a second domain, and the identification mapping information of the first data pipe includes the mapping relationship between the identifier of the first data pipe in the first domain and the identifier of the first data pipe in the second domain; and to send the identification mapping information of the first data pipe to one or more first participating nodes of the first data pipe in the first domain. A first participating node includes: The second communication unit is used to receive the identification mapping information of the first data pipeline from the first data control node, wherein the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain, the first participating node is the participating node of the first data pipeline in the first domain, and the first data control node belongs to the first domain. A second data control node, comprising: The third communication unit is used to send the identification mapping information of the first data pipeline to the first data control node, wherein the first data control node belongs to the first domain and the second data control node belongs to the second domain, and the identification mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain; and to send the identification mapping information of the first data pipeline to one or more second participating nodes in the second domain. A terminal, comprising: The fourth communication unit is configured to send the identifier of the first data pipeline in the first domain to the second data control node, wherein the second data control node belongs to the second domain and the terminal belongs to the first domain; and to receive the identifier mapping information of the first data pipeline from the second data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. A terminal, comprising: The fourth communication unit is configured to receive the identifier of the first data pipeline in the first domain from the first data control node, wherein the terminal belongs to the second domain and the first data plane control point belongs to the first domain; and to send the identifier mapping information of the first data pipeline to the first data control node, wherein the identifier mapping information of the first data pipeline includes the mapping relationship between the identifier of the first data pipeline in the first domain and the identifier of the first data pipeline in the second domain. A first data control node includes: 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 data control node to perform the method as described in any one of claims 1 to 11. A first participating node includes: 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 participating node to perform the method as described in any one of claims 12 to 26. A second data control 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 second data control node to perform the method as described in any one of claims 27 to 36. 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 claimed in any one of claims 37 to 50, or claims 51 to 63. 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 11, or claims 12 to 26, or claims 27 to 36, or claims 37 to 50, or claims 51 to 63.

Images