Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first network element sends first information to a second network element, the first information being associated with a service requirement of a first service to be transmitted in a data pipeline. In embodiments of the present application, a first network element may send, to a second network element, first information associated with a service requirement of a first service to be transmitted in a data pipeline, so that the second network element establishes, on the basis of the first information, a data pipeline that meets the service requirement of the first service.

Description

Wireless communication methods and communication equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method and device for wireless communication. Background Technology

[0002] Data pipelines are a crucial function supported by the data plane, providing end-to-end services for data from acquisition to final processing, enabling data processing along the way and thus supporting diverse business needs. However, how to establish data pipelines is a pressing issue that urgently needs to be addressed.

[0003] Summary of the Invention

[0004] This application provides a method and apparatus for wireless communication. The various aspects covered in this application are described below.

[0005] In a first aspect, a wireless communication method is provided, comprising: a first network element sending first information to a second network element, wherein the first information is associated with the service requirements of a first service to be transmitted in a data pipeline.

[0006] In a second aspect, a wireless communication method includes: a second network element receiving first information sent by a first network element, wherein the first information is associated with the service requirements of a first service to be transmitted in a data pipeline.

[0007] Thirdly, a wireless communication method includes: a third network element sending a first request to a first network element, the first request being used to request the establishment of a data pipeline for transmitting the first service.

[0008] Fourthly, a communication device is provided, the communication device being a first network element, comprising: a transmitting unit for transmitting first information to a second network element, the first information being associated with the service requirements of a first service to be transmitted in a data pipeline.

[0009] Fifthly, a communication device is provided, the communication device being a second network element, comprising: a receiving unit for receiving first information sent by a first network element, the first information being associated with the service requirements of a first service to be transmitted in a data pipeline.

[0010] In a sixth aspect, a communication device is provided, the communication device being a third network element, comprising: a sending unit, configured to send a first request to a first network element, the first request being configured to request the establishment of a data pipeline for transmitting the first service.

[0011] In a seventh aspect, a communication device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the communication device to perform some or all of the steps of the methods described in the preceding aspects.

[0012] Eighthly, embodiments of this application provide a communication system including the aforementioned communication device. In another possible design, the system may further include other devices that interact with the communication device as described in the embodiments of this application.

[0013] Ninthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.

[0014] In a tenth aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0015] In one aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0016] In this embodiment of the application, the first network element can send first information associated with the service requirements of the first service to be transmitted in the data pipeline to the second network element, so that the second network element can establish a data pipeline that meets the service requirements of the first service based on the first information. Attached Figure Description

[0017] Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.

[0018] Figure 2 is a flowchart illustrating the protocol data unit (PDU) session establishment process applicable to the embodiments of this application.

[0019] Figure 3 is a schematic diagram of a communication system architecture including a data plane provided in an embodiment of this application.

[0020] Figure 4 is a schematic diagram of the data pipeline provided in an embodiment of this application.

[0021] Figure 5 is a schematic diagram of the data pipeline architecture based on the data plane in an embodiment of this application.

[0022] Figure 6 is a schematic flowchart of a wireless communication method according to an embodiment of this application.

[0023] Figure 7 is a schematic flowchart of the data pipeline transmission strategy configured in an embodiment of this application.

[0024] Figure 8 is a schematic flowchart of the data plane access controller (DPAC) obtaining the initial network element capability information in an embodiment of this application.

[0025] Figure 9 is a schematic diagram of path switching in the data pipeline implemented in this application.

[0026] Figure 10 is a flowchart of the scheme for transmitting sensing services through a data pipeline in an embodiment of this application.

[0027] Figure 11 is a schematic diagram of a communication device according to an embodiment of this application.

[0028] Figure 12 is a schematic diagram of a communication device according to an embodiment of this application.

[0029] Figure 13 is a schematic diagram of a communication device according to an embodiment of this application.

[0030] Figure 14 is a schematic structural diagram of a communication device according to an embodiment of this application. Detailed Implementation

[0031] Communication system architecture

[0032] Figure 1 is a system architecture example diagram of a wireless communication system 100 to which embodiments of this application can be applied. The system architecture shown in Figure 1 may include terminal equipment, access network (AN) equipment, and network elements in the core network.

[0033] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, satellite communication systems, and so on.

[0034] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), MT, remote station, remote terminal, mobile device, user terminal, terminal, wireless terminal, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communications. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0035] Access network equipment refers to devices that allow terminal devices to wirelessly access the network architecture. They are primarily responsible for air interface-side radio resource management, QoS management, data compression, and encryption. Access network equipment can also be called radio access network (RAN) equipment, such as base stations. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.

[0036] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0037] In some deployments, the access network device in this application embodiment may refer to a CU or a DU, or the access network device may include both a CU and a DU. The gNB may also include an AAU.

[0038] The types of network elements in the core network can include user plane function (UPF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), network exposure function (NEF), network repository function (NRF), and network slice-specific authentication and authorization function (NSSAAF). Among these, UPF network elements are primarily responsible for user data transmission. The other network elements, which can be referred to as control plane function network elements, are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control to ensure reliable and stable transmission of user data.

[0039] UPF network elements can be used to forward and receive data from terminal devices. For example, a UPF network element can receive service data from the data network and transmit it to the terminal device through the access network equipment; a UPF network element can also receive user data from the terminal device through the access network equipment and forward it to the data network. The transmission resources allocated and scheduled by the UPF network element for the terminal device are managed and controlled by the SMF network element. The bearer between the terminal device and the UPF network element can include: the user plane connection between the UPF network element and the access network equipment, and the channel established between the access network equipment and the terminal device. The user plane connection is a QoS flow that can be established between the UPF network element and the access network equipment for transmitting data.

[0040] AMF network elements can be used to manage terminal device access to the core network, such as: terminal device location updates, network registration, access control, terminal device mobility management, and terminal device attachment and detachment. When providing services for a terminal device's session, AMF network elements can also provide control plane storage resources for that session to store session identifiers and the associated SMF network element identifiers.

[0041] SMF network elements can be used to select user plane network elements for terminal devices, redirect user plane network elements for terminal devices, assign Internet Protocol (IP) addresses to terminal devices, establish bearers (also known as sessions) between terminal devices and UPF network elements, modify and release sessions, and perform QoS control.

[0042] PCF network elements are used to provide policies to AMF and SMF network elements, such as QoS policies and slice selection policies.

[0043] DN (Network Node) can provide data services to users for networks such as IP Multimedia Service (IMS) and the Internet. Within a DN, there can be various application servers (AS) providing different application services, such as carrier services, Internet access, or third-party services. AS can implement application functions (AFs). AF elements are used to interact with network elements in the 3GPP core network to support application-affected data routing, access network exposure functions, and interact with PCF (Policy Control Function) elements for policy control, etc.

[0044] NSSF is used for network slice selection and supports the following functions: selecting a set of network slice instance examples to serve the end device; determining allowed network slice selection assistance information (NSSAI), and, when necessary, determining the mapping to the subscribed single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI, and, when necessary, determining the mapping to the subscribed S-NSSAI; determining the set of AMFs that may be used to query the end device, or determining a list of candidate AMFs based on the configuration.

[0045] AUSF is used to receive AMF requests for authentication of terminal devices. It requests a key from UDM and then forwards the issued key to AMF for authentication processing.

[0046] UDM includes functions such as generating and storing user subscription data and managing authentication data, and supports interaction with external third-party servers.

[0047] NEF is used for capability exposure, meaning that based on NEF, network capabilities can be exported to external networks. Untrusted external applications can access core network data through NEF to ensure network security. NEF can provide functions such as QoS capability exposure for external applications, event subscription, and AF request distribution.

[0048] The Network Request Forwarder (NRF) is used for the registration, management, and status detection of network elements in the core network, thereby achieving automated management of these elements. When a network element in the core network starts up, it must register with the NRF before it can provide services. Registration information may include, for example, the network element's type, address, and service list.

[0049] In addition, some networks (such as 5G networks) have added network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various network elements and network management systems in the core network, and big data statistics, analysis or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control terminal device access based on the data analysis results.

[0050] In some communication systems (such as 5G and 6G systems), network elements in the core network can also be called network functions (NFs).

[0051] The most important feature of the system architecture shown in Figure 1 is that these system architectures include a service-oriented architecture, that is, service providers (such as network elements in the core network) can provide specific services and make them available to other network elements (consumers) through predefined API interfaces.

[0052] It should be noted that each network element in Figure 1 can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function implemented on a platform (e.g., a cloud platform). It should also be noted that the network architecture shown in Figure 1 is merely an illustrative representation of the network elements included in the overall network architecture. In this embodiment, the network elements included in the overall network architecture are not limited.

[0053] Those skilled in the art will understand that the network architecture shown in Figure 1 does not constitute a limitation on the network architecture. In specific implementations, the network architecture may include more or fewer network elements than shown in the figure, or combine certain network elements, etc. It should be understood that AN or RAN is represented in Figure 1 as (R)AN.

[0054] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenarios in which the network devices and terminal devices are located.

[0055] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

[0056] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0057] PDU Session Establishment Process

[0058] In the traditional mechanism, a terminal device can create a new PDU session by triggering a PDU session establishment process. Figure 2 is a flowchart illustrating the PDU session establishment process applicable to the embodiments of this application. As shown in Figure 2, the PDU session establishment process may include steps S210 to S290.

[0059] In step S210, the terminal device sends a session establishment request message to the AMF. This message may include parameters such as a session identifier, session type (e.g., initial session establishment, Evolved Packet System (EPS) to 5G System (5GS) handover, Non-3GPP to 3GPP handover, request for urgent services, etc.), session and service continuity mode (SSC mode), data network name (DNN), and single-network slice selection assistance information (S-NSSAI).

[0060] In step S220, the AMF selects a suitable SMF based on the DNN, S-NSSAI, and contracted data.

[0061] In step S230, the AMF invokes the session service of the selected SMF to trigger session establishment.

[0062] In step S240, the SMF obtains session subscription data from the UDM, such as the SSC mode allowed by the user, the session type, and the Session-AMBR of the session.

[0063] In step S250, the SMF selects a PCF for the session.

[0064] In step S260, SMF establishes a policy connection with PCF and obtains PCC rules.

[0065] In step S370, the SMF establishes a user plane connection between the terminal device, the AN, and the UPF. This mainly involves the allocation of core network tunnel information (CN tunnel info) and the acquisition of access network tunnel information (AN tunnel info). Furthermore, the SMF can also send a session establishment acceptance message to the terminal device through the AMF and AN.

[0066] In step S280, the SMF registers with the UDM, and the UDM records the SMF identifier (SMF ID) corresponding to this session.

[0067] In step S290, the SMF allocates an IPv6 prefix to the terminal device and sends it to the terminal device via the user plane.

[0068] Data plane (DP)

[0069] In some scenarios (e.g., practical experience with 5G network intelligence), data acquisition is extremely difficult, and data quality is hard to guarantee. On the one hand, data collection based on network management suffers from limited data types, long collection cycles (15 minutes), and inconsistent data formats, naming conventions, and calculation methods across different vendors, making it difficult to make network management data publicly available. On the other hand, collecting data from terminal devices is even more difficult because it may lead to privacy leaks and reduced data security. Therefore, ensuring that data collected from terminal devices can be processed by trusted nodes to avoid leaking user privacy, or tracking the collected data throughout its entire lifecycle to ensure that every piece of data used by any data consumer is recorded, are currently unsolvable problems.

[0070] To address the aforementioned issues, some network architectures (e.g., 6G network architecture) have proposed adding a "data plane." In some implementations, the data elements in the data plane will encompass both internal and external network data, including service data, user data, network data, sensing data, and other external data.

[0071] In some implementations, basic data services include one or more of the following: data collection, data preprocessing, data storage, data access, and data sharing and collaboration. These basic data services may possess the following characteristics: support for trusted authentication, authorization, and access; efficient data storage and management; on-demand data collection and preprocessing; and external data accessibility. In other words, the data plane may include one or more network elements that provide basic data services for the aforementioned data elements. Alternatively, the data plane may include one or more functions (or network elements) to support one or more of the following data services: trusted and flexible data collection between data sources and data consumers; data accessibility; data preprocessing; data storage; and data tracking. The data source and / or data consumer can be any node; for example, the data source can be any node with data storage requirements, and the data consumer can be any node with data access requirements.

[0072] In some networks (e.g., 6G networks), "trustworthiness" will become a crucial requirement for users of data services. Data services primarily manifest in the stages of data collection, data storage, data access, and data sharing. How to provide trusted storage and traceability of data during the data service delivery process is a key issue that needs to be addressed in the data plane.

[0073] To address the aforementioned issues, embodiments of this application introduce a data plane. The following description, in conjunction with Figure 3, illustrates a schematic diagram of the data plane-based communication system architecture provided by embodiments of this application.

[0074] In some implementations, the data plane can be used to support one or more of the following functions: trusted data collection, trusted data storage, trusted data access, and trusted data sharing. It should be understood that the name "data plane" is not limited in this application embodiment. For example, the data plane can also be called a "data surface," "data network element set," or "data service plane," etc. In future communication architectures, this name can be replaced with a name in future communication systems that has the same or similar functions as the data plane. For ease of description, this application embodiment uses the data plane as an example for introduction.

[0075] Referring to Figure 3, the data plane may include network element 1 and / or network element 2. In some implementations, network element 1 is used to provide data operation functions for the data plane, or in other words, network element 1 is used to operate on data on the data plane. This application embodiment does not specifically limit the data operation functions provided by network element 1. For example, network element 1 may provide one or more of the following operations: data storage function, data retrieval (calling) function, data sharing function, data collection function, data processing function, data opening function, and data verification function, etc.

[0076] This application does not limit the name of network element 1. Exemplarily, the name of network element 1 may include one or more of the following: data plane operation network element, data plane repository (DPR) network element, data plane operation infrastructure, data plane repository infrastructure, etc. Of course, network element 1 can also be other names, such as the names of network elements with the same or similar functions in future communication systems.

[0077] In some implementations, network element 1 can be a blockchain node located in the blockchain, which helps to leverage the characteristics of the blockchain to achieve functions such as trusted data storage in the communication system architecture.

[0078] It should be noted that network element 1 can correspond to one or more physical devices (e.g., a server). If network element 1 corresponds to multiple physical devices, then the network element can be understood as distributed. Some or all of these physical devices can reside in a blockchain. For example, multiple physical devices can correspond to multiple blockchain nodes.

[0079] In some implementations, if network element 1 is distributed and the multiple physical devices corresponding to network element 1 belong to the same blockchain node, then the multiple physical devices will store the same data, thereby ensuring that the data is immutable.

[0080] The above describes network element 1 in the data plane provided in the embodiments of this application. The following describes network element 2 in the data plane provided in the embodiments of this application.

[0081] In some implementations, network element 2 is used for access authentication and / or access control of data services. In other words, network element 2 is used to manage or control data plane access; that is, network element 2 can serve as an interface between data in the communication system and data operation network elements (such as network element 1) in the data plane. Therefore, network element 2 can also be called DPAC. Of course, in the embodiments of this application, network element 2 can also be called one or more of the following: data plane management network element, data plane interface, data plane control network element; this application embodiment does not limit this.

[0082] In some implementations, network element 2 can be located in the core network, that is to say, network element 2 can be a network element in the core network.

[0083] In some implementations, the aforementioned management or control of data plane access may include one or more of the following: collecting data to be stored on the data plane; performing security verification on the data to be stored on the data plane; managing or verifying the identification information of the data source of the data to be stored on the data plane; managing or verifying the identification information of the data consumer of the data to be stored on the data plane; managing access permissions for the data stored in the data plane; processing the data on the data plane; format conversion; data tracking of the data stored in the data plane; and interacting with the data plane operation network element (network element 1).

[0084] In some embodiments, the function corresponding to network element 2 can be implemented by enhancing the data collection coordination function (DCCF). That is, network element 2 can be a single network element with the DCCF. Of course, in the embodiments of this application, network element 2 can also be an independent network element in the core network, and the embodiments of this application are not limited in this respect.

[0085] For ease of understanding, the following example uses the data plane collecting data from a terminal device to introduce network element 1 and network element 2 in this application embodiment. Assume the terminal device is the data source, network element 1 is DPR, and network element 2 is DPAC. During the transaction between the terminal device and the data plane, the terminal device can send a transaction request to the DPAC. This transaction request carries one or more of the following: data source ID (i.e., terminal device ID), the data itself, and data description information. Accordingly, the DPAC verifies the data source ID based on the transaction request sent by the terminal device. If the verification is successful, the DPAC can send the data source ID, the data itself, and the data description information to the DPR for storage. The data description information describes the function of the data, or in other words, it describes the attributes or content of the data. For example, for the terminal device's sensing data, the data description information can indicate that the data is the terminal device's sensing data. Similarly, for the terminal device's location data, the data description information can indicate that the data is the terminal device's location data. Furthermore, for the terminal device's QoS data or session data, the data description information can indicate that the data is the terminal device's QoS data or session data, etc.

[0086] In some embodiments, network element 2 can communicate with the control plane (CP) through a service-oriented interface. Taking network element 2 as a DPAC as an example, this service-oriented interface can be represented as Ndpac.

[0087] In some scenarios, the data plane is a distributed architecture, which helps support flexible and efficient data management. That is, a distributed data plane can include multiple network elements 1, and correspondingly, different network elements 1 can be associated with different or the same network elements 2. In this case, the data source can choose to access the nearest data plane (or network element 2), thereby reducing data transmission latency.

[0088] Data pipeline

[0089] In some communication systems (such as 6G systems), considering the diverse needs of services, different nodes may need to operate on data separately. For example, different nodes may need to perform operations such as data collection, processing, and reception (or aggregation). Based on the above needs, the communication system provided in this application embodiment introduces a data pipeline, which allows data to be processed while being transmitted in the data pipeline (also known as "processing in-path"). The data transmitted in the data pipeline can be, for example, the data in the data plane mentioned above. The data pipeline of this application embodiment is described below with reference to Figure 4.

[0090] Referring to Figure 4, a data pipeline can include one or more nodes. After data is transmitted from the data source in the data pipeline to the next-hop node, that node can process the data and then send the processed data to the next-hop node in the data pipeline, and so on, until the data is transmitted through the data pipeline to the data receiver. Therefore, a data pipeline can be understood as a collection of data processing steps.

[0091] In some embodiments, nodes in a data pipeline can also be referred to as "data pipeline participants" or "data pipeline contributors." Referring again to Figure 4, data pipeline participants can be functionally categorized into data sources, intermediate nodes (hereinafter referred to as intermediate nodes), and data receivers. The data source can be understood as the origin of the data, providing the raw data collection; the data source can be understood as the starting point of the data pipeline. Intermediate nodes are used to process the data and transmit the processed data to the next hop node. The data receiver is used to receive the final processed data; typically, the data receiver does not need to process the data further. That is to say, the data receiver can be understood as the end point of the data pipeline.

[0092] It should be noted that a data pipeline can include one or more data sources to provide diverse data services. For example, as shown in Figure 4, a data source can include data pipeline participant A and data pipeline participant C. Data pipeline participant A and data pipeline participant C can provide different data.

[0093] This application does not limit the data source. In some implementations, the data source may include one or more of the following: terminal device, access network device, network element in core network, network management device, and application device. In some embodiments, the network management device may include, for example, operations, administration, and maintenance (OAM) device. In some embodiments, the application device may include one or more of the following: application server, application server (AF), third-party application, third-party server, etc.

[0094] It should also be noted that the data processing types performed by different intermediate nodes in the data pipeline can be the same or different. This application embodiment does not limit this. The data processing (also known as data processing method) performed by intermediate nodes can include one or more of the following: compression processing, normalization processing, data processing based on artificial intelligence (AI) models, anonymization processing, data filtering, data analysis, and data computation. Of course, in this application embodiment, data processing can also include other types of data processing.

[0095] For example, referring to Figure 4, intermediate nodes can include data pipeline participant X and data pipeline participant Y. Data pipeline participant X and data pipeline participant Y can provide the same data processing, such as compressing the data, although the specific compression method or the values ​​of the compressed data may differ. Alternatively, data pipeline participant X and data pipeline participant Y can provide different data processing; for example, data pipeline participant X compresses the data, while data pipeline participant Y normalizes the data.

[0096] In some embodiments, an intermediate node may perform one or more processing operations on the data in the data pipeline, which is not limited in this application embodiment. For example, referring to Figure 4, data pipeline participant X may only perform compression processing on the data. Alternatively, data pipeline participant X may perform compression processing and normalization processing on the data, etc.

[0097] This application does not limit the intermediate nodes. In some implementations, the intermediate nodes may include one or more of the following: terminal devices, access network devices, network elements in the core network, network management devices, and application devices.

[0098] It should also be noted that a data pipeline may include one or more data receivers. For example, in the example of Figure 4, the data receiver may include data pipeline participant B. This application embodiment does not limit the data receiver. In some implementations, the data receiver may include one or more of the following: terminal equipment, access network equipment, network elements in the core network, network management equipment, and application equipment.

[0099] As discussed above, data pipelines can be used to provide data services. For example, a data pipeline can provide end-to-end services from data collection to processing and final reception.

[0100] In some embodiments, a data pipeline operates similarly to an assembly line in a manufacturing process. In this way, the output of data processing at one node can become the input for subsequent nodes, enabling a smooth and automated workflow for data within the pipeline. This simplifies data management processes and improves data processing efficiency. Furthermore, the introduction of a data pipeline ensures data integrity.

[0101] This application does not limit the name of the data pipeline. For example, a data pipeline can also be called a "data channel," "data processing set," or "data pool." It should be noted that in future communication systems, this name can be replaced with a name in the future communication system that has the same or similar function as the data pipeline. For ease of description, this application uses a data pipeline as an example for illustration.

[0102] This application does not limit the data types that the data pipeline can handle; in other words, the data pipeline can handle any type of data. For example, the data pipeline can handle one or more of the following data types: continuous data, intermittent data, and batch data. Of course, this application is not limited to these. For instance, if the data types are divided according to other methods, the data pipeline can handle any type of data under those other methods. As an example, the data pipeline can handle one or more of the following data types: perception-type data, location-type data, AI-type data, etc.

[0103] This application does not limit the form in which data is transmitted in the data pipeline. For example, data can be transmitted in the data pipeline in the form of data packets.

[0104] The preceding text introduced the data pipeline provided in the embodiments of this application. The following text describes the relationship between the data pipeline and the data plane in the embodiments of this application. In some embodiments, the data pipeline can be used to provide data services on the data plane, or in other words, the data pipeline can be used to provide data services on the data plane. In this way, the data pipeline can be an important function supported by the data plane, capable of providing end-to-end data services from collection to final reception. The embodiments of this application do not specifically limit the data services provided by the data pipeline. Exemplarily, the data pipeline can be used to provide one or more of the following data services: data collection, data processing, and data reception (or data aggregation). The following text, in conjunction with Figure 5, describes the data pipeline architecture based on the data plane in the embodiments of this application.

[0105] Referring to Figure 5, network elements in a data pipeline architecture based on the data plane can be functionally divided into a control section and an execution section. In some implementations, network elements in the control section are used to control and / or manage the data pipeline. For example, network elements in the control section are used for one or more of the following: selecting nodes in the data pipeline, establishing the data pipeline, assigning data pipeline identifiers, assigning data processing strategies corresponding to the data pipeline, establishing the data routing topology in the data pipeline, and monitoring the performance of nodes in the data pipeline.

[0106] This application does not limit the network elements in the control section. For example, the network element in the control section can be network element 2 mentioned above (such as DPAC). Another example is that the network element in the control section can be PCF. Of course, in this application embodiment, the network element in the control section can be a new network element introduced in future communication systems, as long as it is used for managing and / or controlling the data pipeline.

[0107] It should be noted that the network elements in the control section mentioned above may belong to the network elements in the data pipeline, or the network elements in the control section mentioned above may not belong to the network elements in the data pipeline. This application embodiment does not limit this.

[0108] In some implementations, network elements in the execution section are used to transmit and / or process data. For example, network elements in the execution section may include various nodes in the data pipeline, as described above.

[0109] It should be noted that the control and execution parts of the data pipeline can belong to different domains. Referring to Figure 5, assuming the terminal device is the data source of the data pipeline, it can be located in region A. AF is the data receiver of the data pipeline and can be located in region D. The two control network elements of the data pipeline (e.g., DPAC) can be located in regions B and C respectively. Region B can correspond to the region where the access network equipment is located, and region C can correspond to the region where the core network equipment is located.

[0110] As discussed above, the data pipeline is a crucial function supported by the data plane, providing end-to-end services from data acquisition to final processing, enabling data processing along the way, and thus supporting diverse services (such as 6G services). However, how to establish a data pipeline is an urgent problem to be solved.

[0111] Therefore, to address the above problems, this application provides a wireless communication method. In this method, a first network element can send first information associated with the service requirements of a first service to be transmitted in a data pipeline to a second network element, so that the second network element can establish a data pipeline that meets the service requirements of the first service based on the first information. The wireless communication method of this application embodiment is described below with reference to FIG6. The method shown in FIG6 includes step S610.

[0112] In step S610, the first network element sends first information to the second network element, and the first information is associated with the service requirements of the first service to be transmitted in the data pipeline.

[0113] In some implementations, the first network element is used to manage and / or control the data pipeline. For example, the first network element can be network element 2 (e.g., DPAC) or PCF as described above. For details, please refer to the relevant introduction of network elements in the control section of the data pipeline above.

[0114] In some implementations, the second network element can be used to select data pipeline participants in the data pipeline; in other words, data pipeline participants can be selected from the second network element. For details, please refer to the method shown in Figure 8. Of course, in this embodiment, the second network element can be a data pipeline participant. For a more detailed description of data pipeline participants, please refer to the above.

[0115] It should be noted that in some scenarios, the second network element may include one or more network elements. In this case, the first network element may send the first information to one of the network elements, or the first network element may send the first information to multiple network elements. This application embodiment does not limit this.

[0116] In some implementations, the second network element includes one or more of the following: terminal equipment, access network equipment, network elements in the core network, and third-party servers.

[0117] In this application embodiment, the first service transmitted through the data pipeline is not limited. In some implementations, the first service transmitted through the data pipeline can be a specific service. For example, the first service can be a sensing service. Another example is that the first service can be a service related to an intrinsic intelligence use case. In other implementations, the first service transmitted through the data pipeline can be services with similar business requirements. For example, the first service may include sensing service 1 and sensing service 2, which have similar business requirements.

[0118] In some implementations, the business requirements of the first service may include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, storage requirements of the first service, model requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, location requirements of the first service, etc.

[0119] In some implementations, the first information is used to configure a transmission strategy for transmitting the first service in the data pipeline. That is, the transmission strategy is associated with the service requirements of the first service; for example, the transmission strategy is determined based on the service requirements of the first service. Alternatively, the transmission strategy is matched to the service requirements of the first service. Or, the transmission strategy ensures that the process of transmitting the first service in the data pipeline meets the service requirements of the first service.

[0120] In some scenarios, the above transmission strategy can be referred to as a data pipeline strategy or data pipeline rule. This application does not limit this to specific examples.

[0121] In some implementations, the transmission strategy includes one or more of the following: information indicating the data pipeline for transmitting the first service; a first strategy; a second strategy; a third strategy; a fourth strategy; a fifth strategy; and a sixth strategy.

[0122] Taking the transmission strategy including information indicating the data pipeline for transmitting the first service as an example, in some implementations, the information indicating the data pipeline for transmitting the first service may include a data pipeline identifier (ID).

[0123] In some implementations, the data pipeline can correspond to a transmission strategy for a primary service. In this case, the data pipeline identifier can be understood as an identifier for the transmission strategy of the primary service. Correspondingly, in some scenarios, the data pipeline identifier can be understood as an identifier for the service transmission strategy of the primary service.

[0124] In some implementations, data pipeline participants belonging to the same data pipeline share the same data pipeline identifier. That is, the data pipeline identifier is used to identify the transmission strategy of the first service that the data pipeline participant needs to execute.

[0125] Taking the transmission strategy including the first strategy as an example, in some implementations, the first strategy is used to indicate the data processing requirements corresponding to the data pipeline, or in other words, the first strategy is used to indicate the data processing requirements corresponding to the business data of the first service transmitted in the data pipeline. Therefore, the first strategy is also called the "data processing strategy".

[0126] In some implementations, the first strategy is used to indicate one or more of the following: the role of the second network element in the data pipeline; the latency of the second network element in the data pipeline in processing data; the input data format corresponding to the second network element in the data pipeline; the output data format corresponding to the second network element in the data pipeline; the data volume of the input data corresponding to the second network element in the data pipeline; the data volume of the output data corresponding to the second network element in the data pipeline; and the latency of the second network element in the data pipeline transmitting the output data to the next-hop network element.

[0127] In some implementations, the first strategy is used to indicate the role of the second network element in the data pipeline, or in other words, the first strategy is used to indicate the role of the second network element in the data pipeline. The role of the second network element in the data pipeline can include one or more of the following: an intermediate node in the data pipeline, a data source in the data pipeline, and a data receiver in the data pipeline. A detailed description of each role can be found above.

[0128] In some implementations, the first strategy is used to indicate the latency of data processing by the second network element in the data pipeline, or in other words, the first strategy is used to indicate the duration of data processing by the second network element in the data pipeline, or the first strategy is used to indicate the latency of local data processing by the second network element in the data pipeline. In some scenarios, latency can also be referred to as "data processing latency".

[0129] In this application embodiment, the representation method of data processing latency is not limited. In some implementations, data processing latency can be represented by a maximum latency threshold. In other implementations, data processing latency can be represented by a latency interval, which is used to indicate one or more latency requirements for satisfying the first service.

[0130] In some implementations, the latency of data processing by the second network element in the data pipeline indicated by the first strategy can be determined based on the end-to-end latency requirements of the first service. In the embodiments of this application, the first strategy can indicate the latency of data processing by the second network element in the data pipeline, which helps to meet the end-to-end latency requirements of the first service.

[0131] In some implementations, the first strategy is used to indicate the input data format corresponding to the second network element in the data pipeline. That is, the first strategy indicates the input data format of the input data that the second network element needs to process. For example, after receiving data, the second network element needs to preprocess the received data to ensure that the received data meets the input data format requirements supported by the second network element before performing local processing. Here, the input data format can be understood as the input data format corresponding to the preprocessing performed by the second network element. Of course, in this embodiment, the input data format can be the input data format corresponding to the local data processing performed by the second network element.

[0132] The input data format is not limited in the embodiments of this application. In some implementations, the input data format may be used to indicate one or more of the following: model file format, data serialization format, data encoding method, and data structure.

[0133] In some implementations, the first strategy is used to indicate the output data format corresponding to the second network element in the data pipeline; that is, the first strategy is used to indicate the output data format that the second network element needs to output. For example, the output data generated after the second network element performs local data processing needs to meet a specific output data format.

[0134] The output data format is not limited in the embodiments of this application. In some implementations, the output data format may be used to indicate one or more of the following: model file format, data serialization format, data encoding method, and data structure.

[0135] In some implementations, the first strategy is used to indicate the amount of input data corresponding to the second network element in the data pipeline; that is, the first strategy is used to indicate the amount of input data that the second network element needs to process. In some scenarios, the amount of input data that the second network element needs to process can be understood as the amount of received data that the second network element needs to support.

[0136] In some implementations, the first strategy is used to indicate the amount of output data corresponding to the second network element in the data pipeline; that is, the first strategy is used to indicate the amount of output data that the second network element needs to output. In some scenarios, the amount of output data that the second network element needs to output can be understood as the amount of data that the second network element needs to support for transmission.

[0137] In some implementations, the first strategy is used to indicate the delay in which the second network element in the data pipeline transmits its output data to the next-hop network element. That is, the first strategy indicates the transmission delay in which the second network element in the data pipeline transmits its output data to the next-hop network element, where the next-hop network element can be understood as the network element immediately following the second network element in the data pipeline. Therefore, in some scenarios, this delay is also called the "data transmission delay."

[0138] In this application embodiment, the representation method of data transmission delay is not limited. In some implementations, data transmission delay can be represented by a maximum delay threshold. In other implementations, data transmission delay can be represented by a delay interval, which is used to indicate one or more delays that satisfy the service requirements of the first service.

[0139] In some implementations, the data transmission latency indicated by the first strategy can be determined based on the end-to-end latency requirements of the first service. In the embodiments of this application, the first strategy can indicate the latency for the second network element in the data pipeline to transmit the output data to the next-hop network element, which helps to meet the end-to-end latency requirements of the first service.

[0140] Taking a transmission strategy that includes a second strategy as an example, in some implementations, the second strategy is used to indicate the computing power requirements corresponding to the data pipeline, or in other words, the second strategy is used to indicate the computing power requirements required to transmit the service data of the first service in the data pipeline. Therefore, the second strategy is also called a "computing power strategy".

[0141] In some implementations, the second strategy is used to indicate one or more of the following: the computing power consumed by the second network element in the data pipeline; and the computing power type corresponding to the second network element in the data pipeline.

[0142] In some implementations, the second strategy is used to indicate the computing power consumed by the second network element in the data pipeline, or in other words, the second strategy is used to indicate the computing power required by the second network element in the data pipeline to provide services for the first service.

[0143] In this application embodiment, the representation of computing power is not limited. In some implementations, computing power can be represented by a maximum computing power threshold. In other implementations, computing power can be represented by a computing power range, which indicates one or more computing power requirements for meeting the business needs of the first service. The unit of computing power can be floating point operations per second (FLOPS) / TOPS (tera operations per second).

[0144] In some implementations, the computing power indicated by the second strategy can be determined based on the computing power requirements of the first service. In the embodiments of this application, the second strategy can help meet the computing power requirements of the first service by indicating the aforementioned computing power.

[0145] In some implementations, the second strategy is used to indicate the computing power type corresponding to the second network element in the data pipeline, or in other words, the second strategy is used to indicate the computing power type required by the second network element in the data pipeline to provide services for the first service.

[0146] In this application embodiment, the type of computing power is not limited. In some implementations, the type of computing power includes one or more of the following: computing power provided by a central processing unit (CPU), computing power provided by a graphics processing unit (GPU), and computing power provided by a tensor processing unit (TPU).

[0147] Taking the transmission strategy including the third strategy as an example, in some implementations, the third strategy is used to indicate the model requirements corresponding to the data pipeline, or in other words, the third strategy is used to indicate the model requirements corresponding to the service data of the first service transmitted in the data pipeline. Therefore, the third strategy is also called the "model strategy".

[0148] In some implementations, the third strategy is used to indicate one or more of the following: the model adopted by the second network element in the data pipeline; and the model interoperability information corresponding to the second network element in the data pipeline.

[0149] In some implementations, the third strategy is used to indicate the model adopted by the second network element in the data pipeline, or in other words, the third strategy is used to indicate the model required by the second network element in the data pipeline to provide services for the first service. This model may include an AI / machine learning (ML) model.

[0150] In the embodiments of this application, the method by which the third strategy indicates the model is not limited. In some implementations, the third strategy can indicate the model by carrying a model identifier. In other implementations, the third strategy can indicate the model by carrying a function identifier corresponding to the model.

[0151] In some implementations, the third strategy is used to indicate the model interoperability information corresponding to the second network element in the data pipeline; or, in other words, the third strategy is used to indicate the model interoperability information of the model required by the second network element in the data pipeline to provide services for the first service. The aforementioned model may include AI / ML models.

[0152] In some scenarios, considering that data pipeline participants may come from different vendors, and these vendors may not support model interoperability, meaning some data pipeline participants may not be able to resolve models provided by other vendors. Therefore, the third strategy can indicate the compatibility and collaboration capabilities between different models and frameworks by specifying model interoperability information, which helps improve the rationality of deploying models in the second network element. For example, in some distributed AI model training tasks, if the second network element needs to pass the model to the next-hop network element, the model interoperability information indicates that the second network element needs to transmit a model in an open-source format (i.e., a format with open-source interoperability between model interoperability vendors), ensuring that the next-hop network element can resolve and use the model.

[0153] Of course, in the embodiments of this application, model interoperability information can be used to indicate which network elements' models the model corresponding to the second network element needs to support interoperability with.

[0154] Taking the transmission strategy including the fourth strategy as an example, in some implementations, the fourth strategy is used to indicate the energy consumption requirements corresponding to the data pipeline, or in other words, the fourth strategy is used to indicate the energy consumption requirements that the data pipeline needs to meet when transmitting the first service. Therefore, the fourth strategy is also called the "energy consumption strategy".

[0155] In some implementations, the fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline, or in other words, the fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline to provide services for the first service. Of course, in the embodiments of this application, the fourth strategy can be used to indicate the total energy consumption requirement corresponding to all second network elements in the data pipeline. The unit of energy can be kWh or J.

[0156] In this application embodiment, the method of representing the energy consumed by the second network element is not limited. In some implementations, the energy consumed by the second network element can be represented by a maximum energy threshold. In other implementations, the energy consumed by the second network element can be represented by an energy range, which indicates one or more energy values ​​that meet the service requirements of the first service.

[0157] Taking the fifth strategy as an example of a transmission strategy, in some implementations, the fifth strategy is used to indicate the storage requirements corresponding to the data pipeline, or in other words, the fifth strategy is used to indicate the storage requirements that the data pipeline needs to meet when transmitting the first service. Therefore, the fifth strategy is also called the "storage strategy".

[0158] In some implementations, the fifth strategy is used to indicate whether the second network element in the data pipeline needs to support storing the data corresponding to the second network element and / or the data processing method corresponding to the second network element. As mentioned above, the DPR can provide data storage services. Therefore, the fifth strategy can be used to indicate whether the second network element needs to support storing the data corresponding to the second network element to the DPR, and / or whether the second network element needs to support storing the data processing method corresponding to the second network element to the DPR, which helps to meet the security requirements of the first service for data traceability and interpretability. Of course, in the embodiments of this application, the network element storing data is not limited.

[0159] In some implementations, the data corresponding to the second network element may include one or more of the following: the input data of the second network element, the intermediate data generated during the data processing of the input data by the second network element, and the output data of the second network element.

[0160] In other implementations, the data processing method corresponding to the second network element may include one or more data processing methods used by the second network element in the process of processing the input data to obtain the output data. For an introduction to the data processing methods, please refer to the above.

[0161] Taking the sixth strategy as an example, in some implementations, the sixth strategy is used to indicate the data routing requirements corresponding to the data pipeline, or in other words, the sixth strategy is used to indicate the data routing requirements that the data pipeline needs to meet when transmitting the first service. Therefore, the sixth strategy is also called the "data routing strategy".

[0162] In some implementations, the sixth strategy is used to indicate one or more of the following: the upstream network element of the second network element in the data pipeline; the next-hop network element of the second network element in the data pipeline; whether there is a candidate path in the data pipeline for transmitting service data of the first service; multiple candidate upstream network elements and / or candidate next-hop network elements corresponding to the second network element in the data pipeline; the priority of multiple candidate upstream network elements corresponding to the second network element in the data pipeline; the priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline; the conditions for path switching of the second network element in the data pipeline; whether synchronization is required between the upstream network element of the second network element and the upstream candidate network element corresponding to the second network element; and whether synchronization is required between the next-hop network element of the second network element and the next candidate network element corresponding to the second network element.

[0163] In some implementations, the sixth strategy is used to indicate the upstream network element of the second network element in the data pipeline; that is, the sixth strategy indicates from which network element the second network element in the data pipeline receives the service data of the first service. For example, the sixth strategy can carry the identification information of the upstream network element.

[0164] In some implementations, the upstream network element of the second network element can be understood as the network element that the service data of the first service passes through before it reaches the second network element when the service data of the first service is transmitted through the data pipeline. Alternatively, the upstream network element of the second network element can be understood as the network element in the data pipeline that sends the service data of the first service to the second network element. Or, the upstream network element of the second network element can be understood as the network element in the data pipeline that sends the input data of the second network element to the second network element.

[0165] In some implementations, the upstream network element of the second network element includes one or more of the following: a terminal device, an access network device, a network element in the core network, or a third-party server. For example, when the upstream network element of the second network element is a terminal device, the second network element is a mobility management network element. Another example is when the upstream network element of the second network element is a terminal device, the second network element is another terminal device. This application does not limit this.

[0166] In some implementations, the sixth strategy is used to indicate the next-hop network element of the second network element in the data pipeline; that is, the sixth strategy indicates which network element the second network element in the data pipeline can send the service data of the first service to. For example, the sixth strategy can carry the identification information of the next-hop network element.

[0167] In some implementations, the next-hop network element of the second network element can be understood as the network element that the service data of the first service will reach after passing through the second network element when the service data of the first service is transmitted through the data pipeline. Alternatively, the next-hop network element of the second network element can be understood as the network element in the data pipeline that receives the service data of the first service sent by the second network element. Or, the next-hop network element of the second network element can be understood as the network element in the data pipeline that takes the data sent by the second network element as input data.

[0168] In some implementations, the next-hop network element of the second network element includes one or more of the following: a terminal device, an access network device, a network element in the core network, or a third-party server. For example, when the second network element is a terminal device, its next-hop network element is a mobility management network element. Another example is when the second network element is a terminal device, its next-hop network element is another terminal device. This application does not limit this.

[0169] In some implementations, the sixth strategy is used to indicate whether there are candidate paths in the data pipeline for transmitting service data for the first service. These candidate paths can have one or more candidate data pipeline participants (see Figure 5 for example). For a data pipeline containing candidate paths, this helps meet the high reliability and / or high real-time service requirements of the first service.

[0170] It should be noted that the network elements on the candidate paths of the data pipeline can correspond to the data pipeline identifier of the data pipeline used to transmit the first service. Furthermore, in this embodiment, the number of candidate paths corresponding to the data pipeline is not limited. For example, the candidate paths corresponding to the data pipeline may include one or more.

[0171] In some implementations, the sixth strategy is used to indicate the candidate previous hop network element and / or candidate next hop network element corresponding to the second network element in the data pipeline. The candidate previous hop network element and / or candidate next hop network element can be understood as the previous hop network element and / or next hop network element of the second network element on the candidate path of the data pipeline.

[0172] It should be noted that the candidate previous-hop network element corresponding to the second network element may include one or more network elements. Correspondingly, the candidate next-hop network element corresponding to the second network element may include one or more network elements, and this application embodiment does not limit this.

[0173] In some implementations, the sixth strategy is used to indicate the priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline. The priority determines the order in which these candidate next-hop network elements become the next-hop network element of the second network element. Typically, a higher-priority candidate next-hop network element is used before a lower-priority candidate next-hop network element.

[0174] For example, if the second network element determines that the next-hop network element in the data pipeline is abnormal (e.g., the link between the second network element and the next-hop network element is interrupted, or the next-hop network element is overloaded), the second network element can determine the target next-hop network element based on the priorities of multiple candidate next-hop network elements. The target next-hop network element is a normally functioning network element among the candidate next-hop network elements (e.g., the link between the second network element and the target next-hop network element is normal, or the target next-hop network element is under normal load), and the priority of the target next-hop network element is higher than or equal to the priority of the normally functioning network element among the candidate next-hop network elements. Afterwards, the second network element can send the output data to the target next-hop network element.

[0175] In some implementations, the sixth strategy is used to instruct the second network element in the data pipeline to perform path switching, wherein path switching may include switching from the original path in the data pipeline (or the path currently in use in the data pipeline) to a candidate path in the data pipeline.

[0176] In some implementations, a path switching strategy can be used to indicate the conditions for a second network element to perform a path switch. Accordingly, if the path switching strategy is met, the second network element can switch the next-hop network element in the original path to the next-hop network element in the candidate path.

[0177] In this embodiment, the path switching conditions are not limited. For example, a path switching condition may include a link interruption between the second network element and the next-hop network element in the original path. Another example is that the load on the next-hop network element of the second network element in the original path is too high. Yet another example is that the performance of the second network element in the original path cannot meet the service requirements of the first service.

[0178] In some implementations, the path switching strategy can be used to indicate whether the path switching result of the second network element needs to be sent to the first network element (e.g., the control network element of the data pipeline). The path switching result may include information indicating whether the second network element should perform a path switch and / or information of the next-hop network element of the second network element after the path switch.

[0179] In some implementations, the sixth strategy is used to indicate whether synchronization is needed between the next-hop network element of the second network element and the candidate next-hop network element corresponding to the second network element in the data pipeline. Synchronization can be understood as synchronizing information related to the service data of the first service between the next-hop network element and the candidate next-hop network element corresponding to the second network element. For example, this information may include one or more of the following: model information of the next-hop network element, input data corresponding to the next-hop network element, and transmission strategy corresponding to the next-hop network element. Therefore, this synchronization is also called data context synchronization, where the data context may include, for example, the information related to the service data of the first service.

[0180] In this embodiment, the synchronization method between the next-hop network element and the candidate next-hop network element is not limited. In some implementations, the next-hop network element can directly synchronize with the candidate next-hop network element. In this embodiment, this synchronization method is applicable to scenarios where a connection can be established or exists between the next-hop network element and the candidate next-hop network element, which helps to reduce the time required for synchronization.

[0181] In other implementations, the next-hop network element and the candidate next-hop network element can be synchronized through the first network element. For example, the next-hop network element can send the aforementioned synchronization information to the first network element, and correspondingly, the first network element can forward the received information to the candidate next-hop network element. In the embodiments of this application, this synchronization method can be applied to scenarios where a connection cannot be established between the next-hop network element and the candidate next-hop network element, which helps to expand the scenarios applicable to synchronization.

[0182] The transmission strategy in the embodiments of this application has been introduced above. The communication process based on the first information in the embodiments of this application is described below.

[0183] In some implementations, the above method includes: the second network element sending a first response message to the first network element, the first response message indicating whether to accept or reject the transmission policy. In some scenarios, the first response message may also be called a "policy acceptance response," so that the first network element can identify the participants in the data pipeline.

[0184] In some implementations, if the first response message indicates an accept transmission policy, the second network element can act as a data pipeline participant in the data pipeline. Conversely, if the first response message indicates a reject transmission policy, the second network element does not act as a data pipeline participant in the data pipeline.

[0185] In some implementations, the first response message includes one or more of the following capability information of the second network element: computing power information supported by the second network element; data processing latency information supported by the second network element; energy consumption information supported by the second network element; and model information supported by the second network element. For details regarding computing power information, data processing latency, energy consumption information, and model information, please refer to the above text.

[0186] In this embodiment, if the first response message is used to indicate acceptance of the transmission policy, the capability information of the second network element carried in the first response message helps the first network element manage the second network element, for example, modifying the transmission policy based on the capability information of the second network element. Correspondingly, if the first response message is used to indicate rejection of the transmission policy, the capability information of the second network element carried in the first response message helps the first network element understand the capabilities of the second network element, so as to select data pipeline participants when establishing other data pipelines subsequently. Additionally, the service requester can also obtain the aforementioned capability information of the second network element from the first network element, so that the service requester can determine whether to adjust the service requirements of the first service.

[0187] In some implementations, if the first response message is used to indicate a transmission rejection policy, then the first response message carries the reason for the transmission rejection policy, which helps improve the accuracy of the first network element in re-identifying the data pipeline participants. Additionally, the service requester can also obtain the reason for the aforementioned transmission rejection policy from the first network element, so that the service requester can determine whether to adjust the service requirements of the first service.

[0188] In some scenarios, establishing a data pipeline for the first service can be requested by a third network element. That is to say, the above method also includes: the third network element sending a first request to the first network element, the first request being used to request the establishment of a data pipeline for transmitting the first service.

[0189] In some implementations, the third network element can be a service requester. For example, the third network element can be a terminal device, an access network device, a core network element (e.g., AF), or a third-party server. Correspondingly, the first request can also be called a "service request".

[0190] In some implementations, the first request carries one or more of the following: service requirement information for the first service; and information for determining one or more candidate network elements (also known as initial network elements) for the second network elements. The service requirement information for the first service can be found above. The information for determining one or more candidate network elements for the second network elements may include, for example, the identifier of the candidate network element. Of course, in this embodiment, the first request may also carry service description information for the first service (e.g., the Internet Protocol (IP) quintuple of the first service).

[0191] In some implementations, if the data pipeline is successfully established, the first network element can send a response message to the third network element in response to the first request. The response message to the first request is used to indicate acceptance of the first service, or in other words, the response message to the first request is used to indicate that the data pipeline for transmitting the first service has been successfully established.

[0192] In some other implementations, if the data pipeline fails to be established, the first network element can send a response message to the third network element in response to the first request. The response message to the first request is used to indicate that the first service is rejected, or in other words, the response message to the first request is used to indicate that the data pipeline for transmitting the first service has failed to be established.

[0193] In this application embodiment, the method for determining whether the data pipeline establishment is successful or not is not limited. In some implementations, if all candidate network elements of the second network element accept the transmission strategy of the first service, the data pipeline is successfully established. In other implementations, if some or all of the candidate network elements of the second network element reject the transmission strategy of the first service, the data pipeline establishment fails.

[0194] As mentioned above, the third network element may store information about the candidate network elements of the second network element. In this case, the third network element can (e.g., through a first request) send this information to the first network element so that the first network element can select the second network element of the data pipeline from the candidate network elements of the second network element.

[0195] In other scenarios, the third network element may not store information about candidate network elements for the second network element. In this case, the first network element can determine candidate network elements associated with the first service for selecting the second network element based on the association between the service and network elements. That is to say, the above method also includes: the first network element determining candidate network elements associated with the first service for selecting the second network element based on the first service and the pre-stored association between the service and network elements.

[0196] In other scenarios, the candidate network elements for the second network element may include terminal devices. In this case, the first network element can obtain a terminal device matching the first service from the mobility management network element. The mobility management network element may, for example, include AMF or a network element with similar functions in a 6G communication system. That is, the above method further includes: the first network element sending a second request to the mobility management network element to request a terminal device matching the first service. For example, the second request is used to request a terminal device located within the location information corresponding to the first service.

[0197] In some implementations, the first network element may obtain one or more terminal devices from the mobility management network element as candidate network elements for determining the second network element.

[0198] In some implementations, the mobility management network element can feed back terminal devices that meet the service requirements of the first service to the first network element, serving as candidate network elements for the second network element. This helps improve the accuracy of indicating candidate network elements for the second network element. In the embodiments of this application, the method by which the mobility management network element obtains the service requirements of the first service is not limited. For example, the service requirements of the first service can be sent from the first network element to the mobility management network element.

[0199] The foregoing section described the method for determining candidate network elements of the second network element in the embodiments of this application. The following section describes the scheme for obtaining capability information of the second network element in the embodiments of this application. In the embodiments of this application, after the first network element obtains the capability information of the second network element, it can configure a transmission strategy based on the capability information of the second network element. Of course, the scheme described below in the embodiments of this application can also be applied to obtaining the capability information of candidate network elements of the second network element; simply replace "second network element" with "candidate network element" in the following text. For simplicity, this will not be elaborated further below.

[0200] In some implementations, the capability information of the second network element may include one or more of the following: the computing power information of the second network element and / or the model information of the second network element. The following sections will describe implementation methods 1 and 2 respectively.

[0201] Implementation Method 1: The above method further includes: the first network element sending a third request to the fourth network element, the third request being used to request the acquisition of computing power information of one or more second network elements; and / or the fourth network element sending a second response message to the first network element in response to the third request, the second response message being used to indicate the computing power information of one or more second network elements.

[0202] In some implementations, the fourth network element is used to collect computing power from each node; therefore, it is also called a computing power management network element or a computing power collection network element. For example, the computing power management network element can collect computing power at the granularity of network nodes (NFs). Another example is that the computing power management network element can collect computing power at the granularity of network slices.

[0203] In some implementations, computing power information is used to indicate computing power, which can represent the computing capabilities that each node can provide for computing power services. In other scenarios, computing power can be replaced by computing resources, which, correspondingly, represent the computing resources that each node can provide for computing power services.

[0204] In some implementations, computing power can be measured as computing strength, which can be measured using FLOPS or TOPS. For example, computing strength can be quantified at the terminal device level. Another example is that computing strength can be quantified at the service level. Yet another example is that computing strength can be quantified at the application level.

[0205] In some implementations, the fourth network element can be a network element in the core network, or the fourth network element can be a third-party server located outside the core network that can communicate with the core network.

[0206] In some implementations, the third request carries one or more of the following: identification information of one or more second network elements; and computing power requirement information corresponding to the first service. The method by which the first network element obtains the identification information of one or more second network elements can be found in the description above.

[0207] In some implementations, the computing power requirement information corresponding to the first service includes the computing power size information and / or the computing power type information corresponding to the first service. The computing power size can be measured using FLOPS or TOPS. The computing power type information includes one or more of the following: computing power provided by CPU, computing power provided by GPU, and computing power provided by TPU.

[0208] In some implementations, the second response message carries identification information of some or all of the second network elements, and / or computing power information associated with the identification information of the second network elements. For example, the identification information of the second network elements and the associated computing power information in the second response message can be represented as: {second network element 1, available computing power x FLOPS}, {second network element 2, available computing power y FLOPS}, {second network element 3, available computing power z FLOPS}.

[0209] As described above, the third request can indicate the computing power requirements corresponding to the first service. Correspondingly, the second response message can include one or more groups of second network elements, wherein the computing power of each group of second network elements in the one or more groups of second network elements meets the computing power requirements corresponding to the first service.

[0210] In some implementations, the computing power of each group of second network elements in one or more groups of second network elements meets the computing power requirements of the first service, which may include the minimum value of the computing power of one or more groups of second network elements meeting the computing power requirements of the first service.

[0211] For example, the second response message carries combination 1 and combination 2. In combination 1, the second network element and its corresponding computing power information are identified as {second network element 1, available computing power x FLOPS}, {second network element 2, available computing power y FLOPS}, {second network element 3, available computing power z FLOPS}, where x, y, and z are all positive integers greater than 0, and the sum of the computing power of x, y, and z is greater than or equal to the minimum computing power requirement of the first service. In combination 2, the second network element and its corresponding computing power information are identified as {second network element 4, available computing power m FLOPS}, {second network element 5, available computing power n FLOPS}, {second network element 6, available computing power p FLOPS}, where m, n, and p are all positive integers greater than 0, and the sum of the computing power of m, n, and p is greater than or equal to the minimum computing power requirement of the first service.

[0212] It should be noted that, in this embodiment, one or more groups of second network elements can correspond to one or more candidate paths of the data pipeline. Accordingly, the order of each group of second network elements in the second response message is used to indicate the order of the second network elements in the candidate paths. Of course, in this embodiment, the order of the second network elements in the candidate paths can be indicated by dedicated information.

[0213] Furthermore, as described above, the fourth network element can directly feed back the candidate paths of the data pipeline (i.e., the combination method of the second network element), which helps to simplify the complexity of the first network element in selecting a path from the candidate paths of the data pipeline. Of course, in this embodiment, the fourth network element can only feed back the computing power information of the second network element, without feeding back the combination method of the second network element described above, and the first network element determines the combination method of the second network element, which helps to simplify the workload of the fourth network element.

[0214] Implementation Method 2: The above method further includes: the first network element sending a fourth request to the fifth network element, the fourth request being used to request the acquisition of model information of one or more second network elements; and / or the fifth network element sending a third response message to the first network element in response to the fourth request, the third response message being used to indicate the model information of one or more second network elements.

[0215] In some implementations, the fifth network element is used to manage the model information of various network elements. For example, model information can be managed at one or more of the following granularities: terminal device, vendor, scenario, service, type, and registration process. In some scenarios, the fifth network element is also called the model management network element.

[0216] In some implementations, the model management network element can support the discovery of network elements deploying specific models. For example, the model management network element can support the discovery of network elements deploying a specific model based on the location of that specific model. Another example is that the model management network element can support the discovery of network elements deploying a specific model based on the vendor of that specific model. Yet another example is that the model management network element can support the discovery of network elements deploying a specific model based on the service of that specific model.

[0217] In some implementations, the fifth network element can be a network element in the core network, or it can be a third-party server located outside the core network that can communicate with the core network.

[0218] In some implementations, the fourth request may carry one or more of the following: the service type of the first service, the end-to-end latency requirement of the first service, the accuracy requirement of the first service, and the identification information of one or more second network elements. The method for the first network element to obtain the identification information of one or more second network elements can be found in the above description. Furthermore, the service type of the first service, the end-to-end latency requirement of the first service, and the accuracy requirement of the first service can be used by the fifth network element to provide feedback on second network elements that match the service requirements of the first service.

[0219] In some implementations, the third response message includes one or more of the following: identification information of one or more second network elements; model identifiers supported by one or more second network elements; and interoperability information of models supported by one or more second network elements. For details on model interoperability information, please refer to the above text.

[0220] As described above, the fourth request may carry one or more of the following: the service type of the first service, the end-to-end latency requirements of the first service, and the accuracy requirements of the first service. Accordingly, the third response message may include one or more sets of second network elements that match the service requirements of the first service indicated by the fourth request.

[0221] In some implementations, one or more groups of second network elements are matched with the service requirements of the first service indicated by the fourth request, including each group of second network elements in the group of one or more groups of second network elements satisfying the service type of the first service, the end-to-end latency requirements of the first service, and the accuracy requirements of the first service.

[0222] For example, the third response message carries combination 1 and combination 2. In combination 1, the second network element and its corresponding model information can be represented as: {second network element 1, model ID of the model used by second network element 1, model interoperability information}, {second network element 2, model ID of second network element 2, model interoperability information}, {second network element 3, model ID of second network element 3, model interoperability information}. In combination 2, the second network element and its corresponding model information can be represented as: {second network element 4, model ID of second network element 4, model interoperability information}, {second network element 5, model ID of second network element 5, model interoperability information}, {second network element 6, model ID of second network element 6, model interoperability information}.

[0223] It should be noted that, in this embodiment, the aforementioned group or multiple groups of second network elements can correspond to one or more candidate paths of the data pipeline. Accordingly, the order of each group of second network elements in the third response message is used to indicate the order of the second network elements in the candidate paths. Of course, in this embodiment, the order of the second network elements in the candidate paths can be indicated by dedicated information.

[0224] Furthermore, as described above, the fifth network element can directly feed back the candidate paths of the data pipeline (i.e., the combination method of the second network element), which helps to simplify the complexity of the first network element in selecting a path from the candidate paths of the data pipeline. Of course, in this embodiment, the fifth network element can only feed back the model information of the second network element, without feeding back the combination method of the second network element described above, and the first network element determines the combination method of the second network element, which helps to simplify the workload of the fifth network element.

[0225] In this embodiment of the application, the first network element can communicate with the network element used for energy management to obtain the energy consumption information of the second network element. The communication process is similar to the process of obtaining computing power information in implementation method 1 or the process of obtaining model information in implementation method 2. For the sake of simplicity, it will not be described in detail here.

[0226] The foregoing section introduced the scheme for the first network element to obtain the capability information of the second network element in the embodiments of this application. The following section describes the scheme for transmitting service data of the first service in the data pipeline in the embodiments of this application. It should be noted that the second network element mentioned below can be understood as a data pipeline participant; for example, the second network element accepts the transmission strategy of the first service.

[0227] In some implementations, the above method further includes: in the data pipeline, the second network element sends the service data of the first service to the next-hop network element of the second network element.

[0228] In some implementations, the second network element can send the service data of the first service to the next-hop network element in the form of a data packet. In this case, the header of the data packet can carry a data pipeline identifier, so that the next-hop network element can obtain the data pipeline identifier from the header after receiving the data packet and determine the corresponding transmission strategy based on the data pipeline identifier.

[0229] It should be noted that, in the embodiments of this application, a certain network element (the second network element or the next-hop network element of the second network element) may be located in multiple different data pipelines, that is, a certain network element may be deployed with transmission strategies for transmitting different services. Of course, in the embodiments of this application, a certain network element (the second network element or the next-hop network element of the second network element) may be located in only one data pipeline, that is, the network element may be deployed with a transmission strategy for transmitting one service.

[0230] In some scenarios, the scheme of the second network element transmitting the service data of the first service can be used in combination with the scheme of configuring the transmission strategy described above. For example, after accepting the transmission strategy of the first service, the second network element, as a data pipeline participant, can send the processed service data of the first service to the next-hop network element. Of course, in the embodiments of this application, the scheme of the second network element transmitting the service data of the first service and the scheme of configuring the transmission strategy described above can be used independently.

[0231] In some implementations, it is assumed that the next-hop network element of the second network element in the data pipeline is the sixth network element. The first network element can monitor the performance of the data pipeline between the second network element and the sixth network element, and inform the second network element when it is detected that the performance of the data pipeline cannot meet the business requirements of the first service, so that the second network element can switch paths in a timely manner.

[0232] In other words, the above method also includes: in response to the fact that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service, the first network element sends a first indication information to the second network element, the first indication information being used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service.

[0233] In some other implementations, assuming that the next-hop network element of the second network element in the data pipeline is the sixth network element, the sixth network element can autonomously monitor the performance of the data pipeline between the second network element and the sixth network element, and inform the second network element when it is detected that the performance of the data pipeline cannot meet the business requirements of the first service, so that the second network element can switch paths in a timely manner.

[0234] In other words, the above method also includes: the sixth network element sending a fourth indication message to the second network element, the fourth indication message being used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service.

[0235] It should be noted that the embodiments of this application do not limit the performance of the data pipeline between the second network element and the sixth network element. In some implementations, the performance of the data pipeline between the second network element and the sixth network element may include the transmission delay of the data pipeline between the second network element and the sixth network element, and / or the load of the data pipeline between the second network element and the sixth network element.

[0236] In some scenarios, the second network element can autonomously select candidate network elements of the sixth network element for path switching, which helps reduce the time required for path switching. That is to say, the above method also includes: the second network element determining the candidate network elements of the sixth network element based on the pre-configured candidate network element information of the sixth network element; in the data pipeline, the second network element sends the service data of the first service to the candidate network elements of the sixth network element.

[0237] In this embodiment of the application, the synchronization between the sixth network element and the candidate network element of the sixth network element is indicated by the second network element. This can be applied to the scenario where the first network element performs performance monitoring on the data pipeline between the second network element and the sixth network element. This helps the first network element to control the data pipeline between the second network element and the sixth network element based on the performance monitoring results.

[0238] In some implementations, the pre-configured information of the candidate network elements of the sixth network element may include the identifier of the candidate network element and / or the priority of the candidate network element. The priority of the candidate network element can be, for example, the preference level of the candidate next-hop network element described above, which can be referred to above for further information. Of course, in this embodiment, the priority of the candidate network element of the sixth network element can also be obtained through other pre-configured information.

[0239] It should be noted that, in the embodiments of this application, the sixth network element and / or the candidate network element of the sixth network element can be a data pipeline participant in the data pipeline.

[0240] In some scenarios, if the second network element switches the path from the sixth network element to a candidate network element of the sixth network element, the sixth network element and its candidate network element can synchronize. This helps the candidate network element of the sixth network element to receive the service data of the first service from the second network element in the data pipeline, and process and / or transmit it. For a detailed explanation of synchronization, please refer to the above text.

[0241] In some implementations, the first network element can instruct the sixth network element to synchronize between the sixth network element and its candidate network elements. That is, the above method also includes: the first network element sending second instruction information to the sixth network element, the second instruction information being used to instruct synchronization between the sixth network element and its candidate network elements.

[0242] In this embodiment of the application, the synchronization between the sixth network element and the candidate network element of the sixth network element is indicated by the first network element. This can be applied to the scenario where the first network element performs performance monitoring on the data pipeline between the second network element and the sixth network element. This helps the first network element to control the data pipeline between the second network element and the sixth network element based on the performance monitoring results.

[0243] In other implementations, the first network element can instruct the candidate network elements of the sixth network element to synchronize between the sixth network element and its candidate network elements. That is, the above method also includes: the first network element sending third indication information to the candidate network elements of the sixth network element, the third indication information being used to synchronize between the sixth network element and its candidate network elements.

[0244] For ease of understanding, the following description, in conjunction with Figure 5, introduces the scheme of this application embodiment from the perspective of the functions implemented by the first and second network elements. It should be noted that the following description is only from the perspective of network element functions; the solutions related to network element functions have been described in detail above, and can be found above for details.

[0245] In some implementations, the first network element can be considered as a network element in the control section of the data pipeline. In the data pipeline architecture, the functions of the first network element include one or more of the following: receiving a first request sent by a service requester (as an example of a third network element); interacting with other network elements based on the service requirements of the first service in the first request, collecting information from the network elements, and determining suitable data pipeline participants, wherein other network elements include a fifth network element (e.g., a model management network element) and / or a fourth network element (computing power management network element); determining the data pipeline transmission strategy; allocating data pipeline IDs; and establishing and / or maintaining the data pipeline.

[0246] In some implementations, establishing and / or maintaining a data pipeline may include one or more of the following: monitoring the performance of the data pipeline; indicating whether to perform a path switch for the data pipeline; and identifying candidate network elements for path switching.

[0247] In some implementations, the second network element can be considered as a network element in the execution part of the data pipeline, where the execution part is the data pipeline used to transmit the service data of the first service. In the architecture of the data pipeline, the functions of the second network element include one or more of the following: processing and / or transmitting the received service data of the first service; determining whether to perform path switching of the data pipeline; and identifying candidate network elements for path switching.

[0248] For ease of understanding, the method flow related to the data pipeline in the embodiments of this application is described below with reference to Figures 7 to 10. Assume the first network element is DPAC and the third network element is the service requester. Figure 7 is a schematic flowchart illustrating the transmission strategy for configuring the data pipeline in an embodiment of this application. In the scheme shown in Figure 7, the second network element includes a data source, intermediate node 1, intermediate node 2, and a data receiver. The method shown in Figure 7 includes steps S710 to S760.

[0249] In step S710, the service requester sends a service request to the DPAC.

[0250] In some implementations, when a service requester (e.g., UE, AF, NF) wants to perform a first service (e.g., perception service, AI service), the service requester sends a service request to the DPAC.

[0251] In some implementations, the service request carries one or more of the following: service description information of the first service, service requirements of the first service, and identifiers of the initially determined network elements.

[0252] In some implementations, the service description information includes the service's IP quintuple.

[0253] In some implementations, the business requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, model requirements of the first service, storage requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, and location requirements of the first service.

[0254] In some implementations, the initial network element can be matched with the service requirements of the first service. For example, if the first service is to sense objects in a target area, the initial network element can be multiple network elements located in the target area. These initial network elements can include one or more of the following: terminal equipment, access network equipment, and sensing network elements (SF) with sensing capabilities.

[0255] In step S720, DPAC determines a second network element that meets the conditions from the initial network elements as a data pipeline participant based on the service requirements of the first service.

[0256] It should be understood that the relevant introduction to DPAC's determination of the second network element that meets the conditions from the initial network elements can be found in the above text or the method described in Figure 8.

[0257] In step S730, the DPAC sends first information to multiple second network elements respectively. The first information is used to configure the transmission strategy for transmitting the first service in the data pipeline. The multiple second network elements include a data source, intermediate node 1, intermediate node 2, and a data receiver.

[0258] In some implementations, the transmission strategy may include one or more of the following: data pipeline strategy; data processing strategy; computing power strategy; energy consumption strategy; data routing strategy; path switching strategy; data context synchronization. The function of each strategy can be described in Table 1 and the above introduction to transmission strategies.

[0259] Table 1

[0260] In step S740, multiple second network elements send a first response message to the DPAC respectively. The first response message is used to indicate the acceptance or rejection of the transmission policy.

[0261] In step S750, if the data pipeline is established, the DPAC sends a service request response to the service requester. The service request response message includes the service description information of the first service and / or the service acceptance indication of the first service. The service acceptance indication is used to indicate acceptance of the transmission of the first service through the data pipeline.

[0262] In step S760, the service data of the first service is transmitted through the data pipeline.

[0263] In some implementations, the business data for the first service is collected from a data source and processed according to a data pipeline processing strategy. The data source sends the processed data in a data packet to intermediate node 1, where the packet header carries the data pipeline ID. Accordingly, intermediate node 1 determines the data pipeline strategy based on the data pipeline ID and sends the processed data to the data receiver based on the data pipeline strategy.

[0264] In some scenarios, if the data source detects a performance degradation in the data pipeline between the data source and intermediate node 1, which cannot meet the business requirements of the first service, the data source selects intermediate node 2, a candidate network element of intermediate node 1, as the next-hop network element according to the data pipeline strategy, and sends the processed data to intermediate node 2. Accordingly, intermediate node 2 processes the received data and sends the processed data to the data receiver.

[0265] Figure 8 is a schematic flowchart illustrating the process of DPAC acquiring initial network element capability information in an embodiment of this application. The method shown in Figure 8 includes steps S810 to S870.

[0266] In step S810, the service requester sends a service request to the DPAC.

[0267] In some implementations, when a service requester (e.g., UE, AF, NF) wants to perform a first service (e.g., perception service, AI service), the service requester sends a service request to the DPAC.

[0268] In some implementations, the service request carries one or more of the following: service description information of the first service, service requirements of the first service, and identifiers of the initially determined network elements.

[0269] In some implementations, the service description information includes the service's IP quintuple.

[0270] In some implementations, the business requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, storage requirements of the first service, model requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, and location requirements of the first service.

[0271] In some implementations, the initial network element can be matched with the service requirements of the first service. For example, if the first service is to sense objects in a target area, the initial network element can be multiple network elements located in the target area. These initial network elements can include one or more of the following: terminal equipment, access network equipment, and sensing network elements (SF) with sensing capabilities.

[0272] In step S815, DPAC sends a third request to the computing power management network element. The third request is used to request the acquisition of computing power information of one or more initial network elements.

[0273] In some implementations, the computing power management network element stores the computing power type of each network element and / or the maximum computing power supported by the network element.

[0274] In some implementations, the third request carries one or more of the following: the initial network element ID and / or the computing power requirement of the first service, the computing power requirement of the first service being used to indicate the maximum or minimum total computing power required to complete the first service, and / or the computing power type, etc.

[0275] The method for DPAC to obtain initial network elements is not limited in the embodiments of this application. The following description is based on methods 1 to 3.

[0276] Method 1: The service request message can carry the initial network element ID.

[0277] Method 2: If the service request does not include an initial network element ID, the DPAC can determine the initial network element based on local configuration. For example, if the DPAC stores the initial network elements corresponding to different services, the DPAC can determine the initial network element corresponding to the first service based on the initial network elements corresponding to the first service and the services.

[0278] Method 3: If the initial network element includes terminal devices, the DPAC can interact with the AMF based on the service type of the first service and / or the area information corresponding to the first service to determine one or more terminal devices that are in the area corresponding to the first service and support the first service as the initial network element.

[0279] In step S820, the computing power management network element sends a second response message to the DPAC. The second response message is used to indicate the computing power information of one or more initial network elements.

[0280] For example, the second response message carries combination 1 and combination 2. In combination 1, the initial network element and its corresponding computing power information are identified as {initial network element 1, available computing power x FLOPS}, {initial network element 2, available computing power y FLOPS}, {initial network element 3, available computing power z FLOPS}, where x, y, and z are all positive integers greater than 0, and the sum of the computing power of x, y, and z is greater than or equal to the minimum computing power requirement of the first service. In combination 2, the initial network element and its corresponding computing power information are identified as {initial network element 4, available computing power m FLOPS}, {initial network element 5, available computing power n FLOPS}, {initial network element 6, available computing power p FLOPS}, where m, n, and p are all positive integers greater than 0, and the sum of the computing power of m, n, and p is greater than or equal to the minimum computing power requirement of the first service.

[0281] In step S825, DPAC sends a fourth request to the model management network element. The fourth request is used to request the model information of the initial network element.

[0282] In some implementations, the model management network element is used to manage the model information of various network elements. For example, model information can be managed at one or more of the following granularities: terminal device, vendor, scenario, service, type, and registration process.

[0283] In some implementations, the fourth request may carry one or more of the following: the service type of the first service, the end-to-end latency requirement of the first service, the accuracy requirement of the first service, and the identification information of one or more initial network elements.

[0284] The method for DPAC to obtain initial network elements is not limited in the embodiments of this application. For the method of obtaining the initial network elements, please refer to methods 1 to 3 described above.

[0285] In step S830, the model management network element sends a third response message to the DPAC, which is used to indicate one or more second initial model information.

[0286] For example, the third response message carries combination 1 and combination 2. In combination 1, the initial network element and the corresponding model information can be represented as: {initial network element 1, model ID of the model used by initial network element 1, model interoperability information}, {initial network element 2, model ID of initial network element 2, model interoperability information}, {initial network element 3, model ID of initial network element 3, model interoperability information}. In combination 2, the initial network element and the corresponding model information can be represented as: {initial network element 4, model ID of initial network element 4, model interoperability information}, {initial network element 5, model ID of initial network element 5, model interoperability information}, {initial network element 6, model ID of initial network element 6, model interoperability information}.

[0287] In step S835, DPAC determines multiple second network elements based on the computing power information and / or model information of the initial network elements.

[0288] In step S840, the DPAC sends first information to the second network element. The first information is used to configure the transmission strategy for transmitting the first service in the data pipeline. The transmission strategy can be found in the previous description.

[0289] In step S845, multiple second network elements send a first response message to the DPAC respectively. The first response message is used to indicate the acceptance or rejection of the transmission policy.

[0290] In some implementations, multiple second network elements can determine whether the requirements indicated in the transmission strategy can be met based on their own circumstances. If the requirements indicated in the transmission strategy can be met, the first response message is used to indicate acceptance of the transmission strategy. Conversely, if the requirements indicated in the transmission strategy cannot be met, the first response message is used to indicate rejection of the transmission strategy.

[0291] In some implementations, the first response message includes one or more of the following capability information of the second network element: computing power information supported by the second network element; data processing latency information supported by the second network element; energy consumption information supported by the second network element; and model information supported by the second network element. For details regarding computing power information, data processing latency, energy consumption information, and model information, please refer to the above text.

[0292] In some implementations, if the first response message is used to indicate a rejection policy, the reason for the rejection policy carried in the first response message helps improve the accuracy of the first network element in re-identifying the data pipeline participants.

[0293] It should be noted that if multiple second network elements accept the transmission policy, the data pipeline is successfully established. In this case, the DPAC can send a service request response to the service requester (step S850), instructing the data pipeline to be used for transmitting the first service. Conversely, if multiple second network elements partially or completely reject the transmission policy, the data pipeline establishment fails, and step S850 is executed.

[0294] In step S855, DPAC determines the data pipeline participants and candidate nodes of the data pipeline participants, as well as the transmission strategy of each data pipeline participant, based on the first response messages sent by multiple second network elements.

[0295] In some implementations, since the DPAC determines the end-to-end latency (including processing latency and communication latency) for each data pipeline participant, the DPAC subtracts the processing latency of all nodes from the end-to-end latency requirement to obtain the communication latency requirement for the data pipeline. Accordingly, the DPAC sends the communication latency requirement to the PCF. The PCF then uses the communication latency as a QoS parameter for the service flow according to known mechanisms, which helps guarantee the communication latency of the service data for the first service.

[0296] In some implementations, the transmission strategy of the data pipeline participants may be the same as or different from the transmission strategy in step S840.

[0297] In step S860, DPAC sends first information to multiple data pipeline participants respectively. The first information is used to configure the transmission strategy of the data pipeline participants. The transmission strategy can be referred to in the previous description.

[0298] In step S865, multiple data pipeline participants send a first response message to DPAC, which is used to indicate the acceptance or rejection of the transmission policy.

[0299] In step S870, if all data pipeline participants accept the transmission strategy, the data pipeline is successfully established. At this time, DPAC can send a service request response to the service requester, instructing the data pipeline to be used to transmit the first service.

[0300] Figure 9 is a schematic diagram of path switching in a data pipeline according to the present application. Assuming the data pipeline is successfully established (e.g., via the methods shown in Figures 7 and 8), each data pipeline participant is configured with a transmission strategy for transmitting the first service. Additionally, the data pipeline supports candidate paths.

[0301] Referring to Figure 9, in the data pipeline, the data source is data pipeline participant A1, the next-hop network element of data pipeline participant A1 is data pipeline participant B1, the next-hop network element of data pipeline participant B1 is data pipeline participant C, and the next-hop network element of data pipeline participant C is data pipeline participant D. Furthermore, in the candidate paths of the data pipeline, candidate data pipeline participants for data pipeline participant B1 include data pipeline participant B2 and data pipeline participant B3, wherein data pipeline participant B2 has a higher priority than data pipeline participant B3. The path switching method of this application embodiment is described below in conjunction with methods 1 and 2.

[0302] Method 1: Path switching scheme based on DPAC. Assuming DPAC supports performance monitoring of the data pipeline, DPAC, based on the performance monitoring results, determines whether the performance of data pipeline participant A1-data pipeline participant B1 cannot meet the business requirements of the first service, or whether the local processing latency of data pipeline participant B1 cannot meet the business requirements of the first service. In this case, DPAC notifies data pipeline participant A1 that the performance of data pipeline participant B1 cannot meet the requirements.

[0303] In some implementations, data pipeline participant A1 can select candidate data pipeline participant B2 as the next-hop node on the candidate path based on the routing strategy in the transmission policy. Then, data pipeline participant A1 can send subsequent data packets to data pipeline participant B2.

[0304] Method 2: Path switching scheme not based on DPAC. When data pipeline participant A1 or data pipeline participant B1 detects that the performance of the link between data pipeline participant A1 and data pipeline participant B1 cannot meet the business requirements of the first service, or that the local processing latency of data pipeline participant B1 cannot meet the business requirements of the first service, then data pipeline participant B1 notifies data pipeline participant A1 that the performance of the link between data pipeline participant A1 and data pipeline participant B1 cannot meet the business requirements of the first service.

[0305] In some implementations, data pipeline participant A1 can select candidate data pipeline participant B2 as the next-hop node on the candidate path based on the routing strategy in the transmission policy. Then, data pipeline participant A1 can send subsequent data packets to data pipeline participant B2.

[0306] In some implementations, data pipeline participant A1 can notify DPAC of the path switching result, depending on the configuration of the transmission strategy.

[0307] It should be noted that in methods 1 and 2 above, in order to achieve real-time path switching and ensure the reliability of data packet transmission, the link between data pipeline participant A1 and data pipeline participant B2 can be established when the data pipeline is established. Although the transmission resources between data pipeline participant A1 and data pipeline participant B2 have been allocated, no data transmission will occur if the performance of the link between data pipeline participant A1 and data pipeline participant B1 meets the service requirements of the first service.

[0308] Furthermore, if a path switch is required, the DPAC can notify data pipeline participant B1 to synchronize relevant information (e.g., transmission policy) of data pipeline participant B1 with data pipeline participant B2. If a connection exists between data pipeline participant B1 and data pipeline participant B2, data pipeline participant B1 directly sends the relevant information of the first service to data pipeline participant B2. If no connection exists between data pipeline participant B1 and data pipeline participant B2, data pipeline participant B1 sends the relevant information of the first service to the DPAC, which then forwards it to data pipeline participant B2.

[0309] Figure 10 is a flowchart of a scheme for transmitting sensing services through a data pipeline in an embodiment of this application. Assuming the third network element is a sensing network element, and the sensing network element wants to train a sensing model to achieve perception of traffic conditions at a certain location, the service requirement of the first service is the requirement for training the sensing model. The method shown in Figure 10 includes steps S1010 to S1055.

[0310] In step S1010, SF sends a sensing service request to DPAC.

[0311] In some implementations, the perception business requirements include one or more of the following: the model accuracy of the perception model to be trained, the perception results used to train the perception model, the model training completion time of the perception model, and the computing power required to train the perception model. The perception results may include the target vehicle's outline, the target vehicle's location, and a road map showing the target vehicle's location. The model training completion time indicates the time after which a trained perception model is required.

[0312] In step S1015, DPAC identifies the data pipeline participants that provide services to the sensing service.

[0313] In some implementations, data pipeline participants include multiple terminal devices, access network devices, NWDAF, and SF. It should be noted that the method by which DPAC determines data pipeline participants is not limited in the embodiments of this application. For example, DPAC can determine data pipeline participants based on the method shown in Figure 8.

[0314] In step S1020, the DPAC sends first information to the terminal device, access network device, NWDAF and SF respectively. The first information is used to configure the data pipeline for transmission sensing services.

[0315] In some implementations, for the terminal device, the transmission strategy is used to indicate one or more of the following: the type of sensing data collected, whether the terminal device needs to anonymize the sensing data, whether the terminal device needs to compress the sensing data, and which access network device is the next-hop network element for the terminal device. Specifically, the transmission strategy is used to indicate the collection of sensing measurement data based on sensing signals.

[0316] In some implementations, for access network devices, the transmission strategy is used to indicate one or more of the following: the data processing performed by the access network device, and which network element the access network device's next-hop element is (e.g., NWDAF). The data processing performed by the access network device may include the access network device aggregating sensing results generated by multiple terminal devices and generating point cloud information.

[0317] It should be understood that the access network device itself can also collect sensing data, generate traffic information, and send it to NWDAF as labels for training the sensing model. In this case, the access network device can serve as another data source.

[0318] In some implementations, for NWDAF, the transmission strategy is used to indicate one or more of the following: which model NWDAF uses for training, the latency of model training, the computing power required to train the model, and which network element (e.g., SF) is the next hop network element for NWDAF.

[0319] In some implementations, for the SF, the transmission strategy is used to instruct the SF, as a data receiver, to receive the trained model sent by NWDAF.

[0320] In step S1025, the data pipeline participants send a first response message to the DPAC. The first response message is used to indicate the transmission strategy for accepting sensing services. At this time, the data pipeline is successfully established.

[0321] In step S1030, DPAC sends a service acceptance response to SF.

[0322] In step S1035, multiple terminal devices act as data sources and send service data (i.e., sensing measurement data) of sensing services to the access network device through data pipelines.

[0323] In some implementations, to achieve complete perception of target vehicles in a certain area, multiple terminal devices need to be selected as data sources to perceive information about all angles of the target vehicles in that area. Therefore, each terminal device sends its perceived measurement data to the access network device through a data pipeline.

[0324] In step S1040, the access network device aggregates the sensing measurement data sent by different terminal devices to generate three-dimensional point cloud information of the target vehicle.

[0325] In step S1045, the access network device sends the 3D point cloud information of the target vehicle and the perception information of the target vehicle generated by itself to the NWDAF through the data pipeline.

[0326] In step S1050, NWDAF trains a perception model based on the received 3D point cloud information of the target vehicle and the perception information of the target vehicle.

[0327] In step S1055, NWDAF sends the perception model to SF through the data pipeline. This perception model is used for inference of subsequent perception results.

[0328] The method embodiments of this application have been described in detail above with reference to Figures 1 to 10. The apparatus embodiments of this application will be described in detail below with reference to Figures 11 to 14. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0329] Figure 11 is a schematic diagram of a communication device according to an embodiment of this application. The communication device 1100 shown in Figure 11 is a first network element, and the communication device 1100 includes a transmitting unit 1110.

[0330] The sending unit 1110 is used to send first information to the second network element, wherein the first information is associated with the service requirements of the first service to be transmitted in the data pipeline.

[0331] In some implementations, the first information is used to configure a transmission strategy for transmitting the first service in the data pipeline.

[0332] In some implementations, the transmission strategy includes one or more of the following: information indicating the data pipeline for transmitting the first service; a first strategy for indicating the data processing requirements corresponding to the data pipeline; a second strategy for indicating the computing power requirements corresponding to the data pipeline; a third strategy for indicating the model requirements corresponding to the data pipeline; a fourth strategy for indicating the energy consumption requirements corresponding to the data pipeline; a fifth strategy for indicating the storage requirements corresponding to the data pipeline; and a sixth strategy for indicating the data routing requirements corresponding to the data pipeline.

[0333] In some implementations, the first strategy is used to indicate one or more of the following: the role of the second network element in the data pipeline; the latency of the second network element in the data pipeline in performing data processing; the input data format corresponding to the second network element in the data pipeline; the output data format corresponding to the second network element in the data pipeline; the data volume of the input data corresponding to the second network element in the data pipeline; the data volume of the output data corresponding to the second network element in the data pipeline; and the latency of the second network element in the data pipeline transmitting the output data to the next-hop network element.

[0334] In some implementations, the second strategy is used to indicate one or more of the following: the computing power consumed by the second network element in the data pipeline; and the computing power type corresponding to the second network element in the data pipeline.

[0335] In some implementations, the third strategy is used to indicate one or more of the following: the model adopted by the second network element in the data pipeline; and model interoperability information corresponding to the second network element in the data pipeline.

[0336] In some implementations, the fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline.

[0337] In some implementations, the fifth strategy is used to indicate whether the second network element in the data pipeline needs to support storing the data corresponding to the second network element and / or the data processing method corresponding to the second network element.

[0338] In some implementations, the sixth strategy is used to indicate one or more of the following: the upstream network element of the second network element in the data pipeline; the next-hop network element of the second network element in the data pipeline; whether there is a candidate path in the data pipeline for transmitting service data of the first service; the candidate upstream network element and / or candidate next-hop network element corresponding to the second network element in the data pipeline; the priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline; the strategy for path switching of the second network element in the data pipeline; and whether synchronization is required between the next-hop network element of the second network element in the data pipeline and the candidate next-hop network element corresponding to the second network element.

[0339] In some implementations, the communication device includes: a first receiving unit, configured to receive a first response message sent by the second network element, the first response message being used to indicate acceptance or rejection of the transmission strategy.

[0340] In some implementations, the first response message includes one or more of the following: computing power information supported by the second network element; data processing latency information supported by the second network element; energy consumption information supported by the second network element; and model information supported by the second network element.

[0341] In some implementations, the first response message is used to indicate rejection of the transmission policy, and the first response message carries the reason for rejecting the transmission policy.

[0342] In some implementations, the communication device further includes: a second receiving unit, configured to receive a first request sent by a third network element, the first request being used to request the establishment of a data pipeline for transmitting the first service.

[0343] In some implementations, the first request carries one or more of the following: service requirement information of the first service; and information for determining one or more candidate network elements of the second network element.

[0344] In some implementations, the service requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, storage requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, and location requirements of the first service.

[0345] In some implementations, the communication device further includes a processing unit, configured to determine, based on the first service and pre-stored associations between services and network elements, candidate network elements associated with the first service for selecting the second network element.

[0346] In some implementations, the second network element includes a terminal device, and the sending unit is further configured to send a second request to the mobility management network element to request a terminal device located within the location information corresponding to the first service.

[0347] In some implementations, the sending unit is further configured to send a third request to the fourth network element, the third request being used to request the acquisition of computing power information of one or more of the second network elements; and / or the third receiving unit is configured to receive a second response message sent by the fourth network element in response to the third request, the second response message being used to indicate the computing power information of one or more of the second network elements.

[0348] In some implementations, the third request carries one or more of the following: identification information of one or more of the second network elements; computing power requirement information corresponding to the first service.

[0349] In some implementations, the computing power requirement information corresponding to the first service includes the computing power size information and / or the computing power type information corresponding to the first service.

[0350] In some implementations, the second response message carries identification information of some or all of the second network elements.

[0351] In some implementations, the sending unit is further configured to send a fourth request to the fifth network element, the fourth request being used to request the acquisition of model information of one or more of the second network elements; and / or the fourth receiving unit is further configured to receive a third response message sent by the fifth network element in response to the fourth request, the third response message being used to indicate the model information of one or more of the second network elements.

[0352] In some implementations, the fourth request carries one or more of the following: identification information of one or more of the second network elements; model requirement information corresponding to the first service; end-to-end latency information corresponding to the first service; and accuracy requirements of the first service.

[0353] In some implementations, the third response message includes one or more of the following: identification information of one or more of the second network elements; model identifiers supported by one or more of the second network elements; and interoperability information of the models supported by one or more of the second network elements.

[0354] In some implementations, the next-hop network element of the second network element in the data pipeline is the sixth network element. The sending unit is further configured to send a first indication information to the second network element in response to the fact that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The first indication information is used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service.

[0355] In some implementations, the sending unit is further configured to send second indication information to the sixth network element, the second indication information being used to indicate synchronization between the sixth network element and its candidate network elements.

[0356] In some implementations, the sending unit is further configured to send third indication information to the candidate network elements of the sixth network element, the third indication information being used to synchronize the sixth network element and the candidate network elements of the sixth network element.

[0357] In some implementations, the second network element includes one or more of the following: terminal equipment, access network equipment, network elements in the core network, and third-party servers.

[0358] Figure 12 is a schematic diagram of a communication device according to an embodiment of this application. The communication device 1200 shown in Figure 12 is a second network element, and the communication device 1200 includes: a receiving unit 1210.

[0359] The receiving unit 1210 is used to receive first information sent by the first network element, wherein the first information is associated with the service requirements of the first service to be transmitted in the data pipeline.

[0360] In some implementations, the first information is used to configure a transmission strategy for transmitting the first service in the data pipeline.

[0361] In some implementations, the transmission strategy includes one or more of the following: information indicating the data pipeline for transmitting the first service; a first strategy for indicating the data processing requirements corresponding to the data pipeline; a second strategy for indicating the computing power requirements corresponding to the data pipeline; a third strategy for indicating the model requirements corresponding to the data pipeline; a fourth strategy for indicating the energy consumption requirements corresponding to the data pipeline; a fifth strategy for indicating the storage requirements corresponding to the data pipeline; and a sixth strategy for indicating the data routing requirements corresponding to the data pipeline.

[0362] In some implementations, the first strategy is used to indicate one or more of the following: the role of the second network element in the data pipeline; the latency of the second network element in the data pipeline in performing data processing; the input data format corresponding to the second network element in the data pipeline; the output data format corresponding to the second network element in the data pipeline; the data volume of the input data corresponding to the second network element in the data pipeline; the data volume of the output data corresponding to the second network element in the data pipeline; and the latency of the second network element in the data pipeline transmitting the output data to the next-hop network element.

[0363] In some implementations, the second strategy is used to indicate one or more of the following: the computing power consumed by the second network element in the data pipeline; and the computing power type corresponding to the second network element in the data pipeline.

[0364] In some implementations, the third strategy is used to indicate one or more of the following: the model adopted by the second network element in the data pipeline; and model interoperability information corresponding to the second network element in the data pipeline.

[0365] In some implementations, the fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline.

[0366] In some implementations, the fifth strategy is used to indicate whether the second network element in the data pipeline needs to support storing the data corresponding to the second network element and / or the data processing method corresponding to the second network element.

[0367] In some implementations, the sixth strategy is used to indicate one or more of the following: the upstream network element of the second network element in the data pipeline; the next-hop network element of the second network element in the data pipeline; whether there is a candidate path in the data pipeline for transmitting service data of the first service; the candidate upstream network element and / or candidate next-hop network element corresponding to the second network element in the data pipeline; the priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline; the strategy for path switching of the second network element in the data pipeline; and whether synchronization is required between the next-hop network element of the second network element in the data pipeline and the candidate next-hop network element corresponding to the second network element.

[0368] In some implementations, the communication device includes: a first sending unit, configured to send a first response message to the first network element, the first response message being used to indicate acceptance or rejection of the transmission strategy.

[0369] In some implementations, the first response message includes one or more of the following: computing power information supported by the second network element; data processing latency information supported by the second network element; energy consumption information supported by the second network element; and model information supported by the second network element.

[0370] In some implementations, the first response message is used to indicate rejection of the transmission policy, and the first response message carries the reason for rejecting the transmission policy.

[0371] In some implementations, the communication device further includes: a second sending unit in the data pipeline, used to send the service data of the first service to the next-hop network element of the second network element.

[0372] In some implementations, the next-hop network element of the second network element in the data pipeline is the sixth network element. The receiving unit is further configured to receive a first indication information sent by the first network element in response to the fact that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The first indication information is used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service.

[0373] In some implementations, the next-hop network element of the second network element in the data pipeline is the sixth network element. The receiving unit is further configured to receive fourth indication information sent by the sixth network element, which indicates that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service.

[0374] In some implementations, the communication device further includes: a processing unit, configured to determine a candidate network element of the sixth network element based on pre-configured candidate network element information of the sixth network element; and a third sending unit, configured to send the service data of the first service to the candidate network element of the sixth network element in the data pipeline.

[0375] Figure 13 is a schematic diagram of a communication device according to an embodiment of this application. The communication device 1300 shown in Figure 13 is a third network element, and the communication device 1300 includes a transmitting unit 1310.

[0376] The sending unit 1310 is used to send a first request to the first network element, the first request being used to request the establishment of a data pipeline for transmitting the first service.

[0377] In some implementations, the data pipeline includes one or more second network elements, and the first request carries one or more of the following: service requirement information of the first service; and information for determining candidate network elements for one or more second network elements.

[0378] In some implementations, the service requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, storage requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, and location requirements of the first service.

[0379] In some implementations, the third network element includes terminal equipment and / or network elements in the core network.

[0380] In an optional embodiment, the transmitting unit 1110 may be a transceiver 1430. The communication device 1100 may also include a processor 1410 and a memory 1420, as shown in FIG14.

[0381] In an optional embodiment, the receiving unit 1210 may be a transceiver 1430. The communication device 1200 may also include a processor 1410 and a memory 1420, as shown in FIG14.

[0382] In an optional embodiment, the transmitting unit 1310 may be a transceiver 1430. The communication device 1300 may also include a processor 1410 and a memory 1420, as shown in FIG14.

[0383] Figure 14 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 14 indicate that the unit or module is optional. This device 1400 can be used to implement the methods described in the above method embodiments. Device 1400 can be a chip, a terminal device, or a network device.

[0384] Apparatus 1400 may include one or more processors 1410. The processor 1410 may support apparatus 1400 in implementing the methods described in the preceding method embodiments. The processor 1410 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0385] The apparatus 1400 may further include one or more memories 1420. The memories 1420 store a program that can be executed by the processor 1410, causing the processor 1410 to perform the methods described in the preceding method embodiments. The memories 1420 may be independent of the processor 1410 or integrated within the processor 1410.

[0386] The device 1400 may also include a transceiver 1430. The processor 1410 can communicate with other devices or chips via the transceiver 1430. For example, the processor 1410 can send and receive data with other devices or chips via the transceiver 1430.

[0387] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0388] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0389] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0390] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0391] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0392] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0393] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0394] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0395] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0396] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0397] In the various embodiments of this application, the order of the above-mentioned processes 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.

[0398] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0400] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0402] The above description is merely a specific embodiment 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 scope of the technology 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

A method for wireless communication, characterized in that, include: The first network element sends first information to the second network element, and the first information is associated with the service requirements of the first service to be transmitted in the data pipeline. The method as described in claim 1, characterized in that, The first information is used to configure the transmission strategy for transmitting the first service in the data pipeline. The method as described in claim 2, characterized in that, The transmission strategy includes one or more of the following: Information indicating the data pipeline for transmitting the first service; A first strategy used to indicate the data processing requirements corresponding to the data pipeline; A second strategy for indicating the computing power requirements corresponding to the data pipeline; A third strategy used to indicate the model requirements corresponding to the data pipeline; A fourth strategy for indicating the energy consumption requirements corresponding to the data pipeline; A fifth strategy used to indicate the storage requirements corresponding to the data pipeline; A sixth strategy used to indicate the data routing requirements corresponding to the data pipeline. The method as described in claim 3, characterized in that, The first strategy is used to indicate one or more of the following: The role of the second network element in the data pipeline; The delay in data processing by the second network element in the data pipeline; The input data format corresponding to the second network element in the data pipeline; The output data format corresponding to the second network element in the data pipeline; The amount of input data corresponding to the second network element in the data pipeline; The amount of output data corresponding to the second network element in the data pipeline; In the data pipeline, the second network element will output the delay of data transmission to the next hop network element. The method as described in claim 3 or 4, characterized in that, The second strategy is used to indicate one or more of the following: The computing power consumed by the second network element in the data pipeline; The computing power type corresponding to the second network element in the data pipeline. The method as described in any one of claims 3-5, characterized in that, The third strategy is used to indicate one or more of the following: The model used by the second network element in the data pipeline; The model interoperability information corresponding to the second network element in the data pipeline. The method as described in any one of claims 3-6, characterized in that, The fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline. The method as described in any one of claims 3-7, characterized in that, The fifth strategy is used to indicate whether the second network element in the data pipeline needs to support storing the data corresponding to the second network element and / or the data processing method corresponding to the second network element. The method as described in any one of claims 3-8, characterized in that, The sixth strategy is used to indicate one or more of the following: The upstream network element of the second network element in the data pipeline; The next-hop network element of the second network element in the data pipeline; Does the data pipeline contain a candidate path for transmitting the service data of the first service? The candidate previous hop network element and / or candidate next hop network element corresponding to the second network element in the data pipeline; The priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline; The strategy for path switching of the second network element in the data pipeline; Does the next-hop network element of the second network element in the data pipeline need to be synchronized with the candidate next-hop network element corresponding to the second network element? The method as described in any one of claims 2-9, characterized in that, The method includes: The first network element receives a first response message sent by the second network element, the first response message being used to indicate whether to accept or reject the transmission strategy. The method as described in claim 10, characterized in that, The first response message includes one or more of the following: The computing power information supported by the second network element; The second network element supports data processing latency information; The energy consumption information supported by the second network element; The model information supported by the second network element. The method as described in claim 10 or 11, characterized in that, The first response message is used to indicate that the transmission policy is rejected, and the first response message carries the reason for rejecting the transmission policy. The method as described in any one of claims 1-12, characterized in that, The method further includes: The first network element receives a first request sent by the third network element, the first request being used to request the establishment of a data pipeline for transmitting the first service. The method as described in claim 13, characterized in that, The first request carries one or more of the following: The business requirements information for the first service; Information used to determine one or more candidate network elements for the second network element. The method as described in claim 14, characterized in that, The service requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, storage requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, and location requirements of the first service. The method as described in any one of claims 1-15, characterized in that, The method further includes: The first network element determines candidate network elements associated with the first service for selecting the second network element based on the first service and the pre-stored association relationships between services and network elements. The method as described in any one of claims 1-16, characterized in that, The second network element includes a terminal device, and the method further includes: The first network element sends a second request to the mobility management network element to request a terminal device located within the location information corresponding to the first service. The method as described in any one of claims 1-17, characterized in that, The method further includes: The first network element sends a third request to the fourth network element, the third request being used to request the acquisition of computing power information of one or more of the second network elements; and / or The first network element receives a second response message from the fourth network element in response to the third request. The second response message is used to indicate the computing power information of one or more of the second network elements. The method as described in claim 18, characterized in that, The third request carries one or more of the following: Identification information of one or more second network elements; The computing power requirement information corresponding to the first service. The method as described in claim 19, characterized in that, The computing power requirement information corresponding to the first service includes the computing power size information and / or the computing power type information corresponding to the first service. The method as described in any one of claims 18-20, characterized in that, The second response message carries identification information of some or all of the second network elements. The method as described in any one of claims 1-21, characterized in that, The method further includes: The first network element sends a fourth request to the fifth network element, the fourth request being used to request the acquisition of model information from one or more of the second network elements; and / or The first network element receives a third response message sent by the fifth network element in response to the fourth request. The third response message is used to indicate model information of one or more of the second network elements. The method as described in claim 22, characterized in that, The fourth request carries one or more of the following: Identification information of one or more second network elements; The model requirement information corresponding to the first service; End-to-end latency information corresponding to the first service; The accuracy requirements of the first service. The method as described in claim 22 or 23, characterized in that, The third response message includes one or more of the following: Identification information of one or more second network elements; One or more model identifiers supported by the second network element; Interoperability information of one or more models supported by the second network element. The method according to any one of claims 1-24, characterized in that, In the data pipeline, the next-hop network element of the second network element is the sixth network element, and the method further includes: In response to the fact that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service, the first network element sends a first indication message to the second network element. The first indication message is used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The method as described in claim 25, characterized in that, The method further includes: The first network element sends a second indication message to the sixth network element, the second indication message being used to indicate synchronization between the sixth network element and its candidate network elements. The method as described in claim 25, characterized in that, The method further includes: The first network element sends a third indication information to the candidate network element of the sixth network element, the third indication information being used in the sixth network element... The sixth network element is synchronized with the candidate network elements of the sixth network element. The method as described in any one of claims 1-27, characterized in that, The second network element includes one or more of the following: terminal equipment, access network equipment, network elements in the core network, and third-party servers. A method for wireless communication, characterized in that, include: The second network element receives the first information sent by the first network element, and the first information is associated with the service requirements of the first service to be transmitted in the data pipeline. The method as described in claim 29, characterized in that, The first information is used to configure the transmission strategy for transmitting the first service in the data pipeline. The method as described in claim 30, characterized in that, The transmission strategy includes one or more of the following: Information indicating the data pipeline for transmitting the first service; A first strategy used to indicate the data processing requirements corresponding to the data pipeline; A second strategy for indicating the computing power requirements corresponding to the data pipeline; A third strategy used to indicate the model requirements corresponding to the data pipeline; A fourth strategy for indicating the energy consumption requirements corresponding to the data pipeline; A fifth strategy used to indicate the storage requirements corresponding to the data pipeline; A sixth strategy used to indicate the data routing requirements corresponding to the data pipeline. The method as described in claim 31, characterized in that, The first strategy is used to indicate one or more of the following: The role of the second network element in the data pipeline; The delay in data processing by the second network element in the data pipeline; The input data format corresponding to the second network element in the data pipeline; The output data format corresponding to the second network element in the data pipeline; The amount of input data corresponding to the second network element in the data pipeline; The amount of output data corresponding to the second network element in the data pipeline; In the data pipeline, the second network element will output the delay of data transmission to the next hop network element. The method as described in claim 31 or 32, characterized in that, The second strategy is used to indicate one or more of the following: The computing power consumed by the second network element in the data pipeline; The computing power type corresponding to the second network element in the data pipeline. The method as described in any one of claims 31-33, characterized in that, The third strategy is used to indicate one or more of the following: The model used by the second network element in the data pipeline; The model interoperability information corresponding to the second network element in the data pipeline. The method as described in any one of claims 31-34, characterized in that, The fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline. The method as described in any one of claims 31-35, characterized in that, The fifth strategy is used to indicate whether the second network element in the data pipeline needs to support storing the data corresponding to the second network element and / or the data processing method corresponding to the second network element. The method as described in any one of claims 31-36, characterized in that, The sixth strategy is used to indicate one or more of the following: The upstream network element of the second network element in the data pipeline; The next-hop network element of the second network element in the data pipeline; Does the data pipeline contain a candidate path for transmitting the service data of the first service? The candidate previous hop network element and / or candidate next hop network element corresponding to the second network element in the data pipeline; The priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline; The strategy for path switching of the second network element in the data pipeline; Does the next-hop network element of the second network element in the data pipeline need to be synchronized with the candidate next-hop network element corresponding to the second network element? The method as described in any one of claims 30-37, characterized in that, The method includes: The second network element sends a first response message to the first network element, the first response message being used to indicate whether to accept or reject the transmission strategy. The method as described in claim 38, characterized in that, The first response message includes one or more of the following: The computing power information supported by the second network element; The second network element supports data processing latency information; The energy consumption information supported by the second network element; The model information supported by the second network element. The method as described in claim 38, characterized in that, The first response message is used to indicate rejection of the transmission policy. The first response message describes the reason for rejecting the transmission policy. The method as described in any one of claims 29-40, characterized in that, The method further includes: In the data pipeline, the second network element sends the service data of the first service to the next-hop network element of the second network element. The method as described in any one of claims 29-41, characterized in that, In the data pipeline, the next-hop network element of the second network element is the sixth network element, and the method further includes: In response to the fact that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service, the second network element receives a first indication information sent by the first network element. The first indication information is used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The method as described in any one of claims 29-41, characterized in that, In the data pipeline, the next-hop network element of the second network element is the sixth network element, and the method further includes: The second network element receives a fourth indication message sent by the sixth network element, the fourth indication message being used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The method as described in claim 42 or 43, characterized in that, The method further includes: The second network element determines the candidate network element of the sixth network element based on the pre-configured candidate network element information of the sixth network element; In the data pipeline, the second network element sends the service data of the first service to the candidate network element of the sixth network element. A method for wireless communication, characterized in that, include: The third network element sends a first request to the first network element, the first request being used to request the establishment of a data pipeline for transmitting the first service. The method as described in claim 45, characterized in that, The data pipeline includes one or more second network elements, and the first request carries one or more of the following: The business requirements information for the first service; Information used to identify candidate network elements for one or more second network elements. The method as described in claim 46, characterized in that, The service requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, storage requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, and location requirements of the first service. The method as described in any one of claims 45-47, characterized in that, The third network element includes terminal equipment and / or network elements in the core network. A communication device, characterized in that, The communication device is a first network element, including: The sending unit is used to send first information to the second network element, wherein the first information is associated with the service requirements of the first service to be transmitted in the data pipeline. The communication device as described in claim 49, characterized in that, The first information is used to configure the transmission strategy for transmitting the first service in the data pipeline. The communication device as described in claim 50, characterized in that, The transmission strategy includes one or more of the following: Information indicating the data pipeline for transmitting the first service; A first strategy used to indicate the data processing requirements corresponding to the data pipeline; A second strategy for indicating the computing power requirements corresponding to the data pipeline; A third strategy used to indicate the model requirements corresponding to the data pipeline; A fourth strategy for indicating the energy consumption requirements corresponding to the data pipeline; A fifth strategy used to indicate the storage requirements corresponding to the data pipeline; A sixth strategy used to indicate the data routing requirements corresponding to the data pipeline. The communication device as described in claim 51, characterized in that, The first strategy is used to indicate one or more of the following: The role of the second network element in the data pipeline; The delay in data processing by the second network element in the data pipeline; The input data format corresponding to the second network element in the data pipeline; The output data format corresponding to the second network element in the data pipeline; The amount of input data corresponding to the second network element in the data pipeline; The amount of output data corresponding to the second network element in the data pipeline; In the data pipeline, the second network element will output the delay of data transmission to the next hop network element. The communication device as described in claim 51 or 52 is characterized in that, The second strategy is used to indicate one or more of the following: The computing power consumed by the second network element in the data pipeline; The computing power type corresponding to the second network element in the data pipeline. The communication device as described in any one of claims 51-53, characterized in that, The third strategy is used to indicate one or more of the following Multiple: The model used by the second network element in the data pipeline; The model interoperability information corresponding to the second network element in the data pipeline. The communication device as described in any one of claims 51-54, characterized in that, The fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline. The communication device as described in any one of claims 51-55, characterized in that, The fifth strategy is used to indicate whether the second network element in the data pipeline needs to support storing the data corresponding to the second network element and / or the data processing method corresponding to the second network element. The communication device as described in any one of claims 51-56, characterized in that, The sixth strategy is used to indicate one or more of the following: The upstream network element of the second network element in the data pipeline; The next-hop network element of the second network element in the data pipeline; Does the data pipeline contain a candidate path for transmitting the service data of the first service? The candidate previous hop network element and / or candidate next hop network element corresponding to the second network element in the data pipeline; The priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline; The strategy for path switching of the second network element in the data pipeline; Does the next-hop network element of the second network element in the data pipeline need to be synchronized with the candidate next-hop network element corresponding to the second network element? The communication device as described in any one of claims 50-57, characterized in that, The communication device includes: The first receiving unit is configured to receive a first response message sent by the second network element, wherein the first response message is used to indicate whether to accept or reject the transmission strategy. The communication device as described in claim 58, characterized in that, The first response message includes one or more of the following: The computing power information supported by the second network element; The second network element supports data processing latency information; The energy consumption information supported by the second network element; The model information supported by the second network element. The communication device as described in claim 58 or 59 is characterized in that, The first response message is used to indicate that the transmission policy is rejected, and the first response message carries the reason for rejecting the transmission policy. The communication device as described in any one of claims 49-60, characterized in that, The communication device also includes: The second receiving unit is used to receive a first request sent by a third network element, wherein the first request is used to request the establishment of a data pipeline for transmitting the first service. The communication device as described in claim 61, characterized in that, The first request carries one or more of the following: The business requirements information for the first service; Information used to determine one or more candidate network elements for the second network element. The communication device as described in claim 62, characterized in that, The service requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, computing power requirements of the first service, storage requirements of the first service, energy consumption requirements of the first service, security requirements of the first service, and location requirements of the first service. The communication device as described in any one of claims 49-63, characterized in that, The communication device also includes: The processing unit is used to determine, based on the first service and the pre-stored association relationship between the service and the network element, a candidate network element associated with the first service for selecting the second network element. The communication device as described in any one of claims 49-64, characterized in that, The second network element includes terminal equipment. The sending unit is further configured to send a second request to the mobility management network element to request a terminal device located within the location information corresponding to the first service. The communication device as described in any one of claims 49-65, characterized in that, The sending unit is further configured to send a third request to the fourth network element, the third request being used to request to obtain computing power information of one or more of the second network elements; and / or The third receiving unit is used to receive a second response message sent by the fourth network element in response to the third request. The second response message is used to indicate the computing power information of one or more of the second network elements. The communication device as described in claim 66, characterized in that, The third request carries one or more of the following: Identification information of one or more second network elements; The computing power requirement information corresponding to the first service. The communication device as described in claim 67, characterized in that, The computing power requirement information corresponding to the first service includes the computing power size information and / or the computing power type information corresponding to the first service. The communication device as described in any one of claims 66-68, characterized in that, The second response message carries identification information of some or all of the second network elements. The communication device as described in any one of claims 49-69, characterized in that, The sending unit is further configured to send a fourth request to the fifth network element, the fourth request being used to request the acquisition of model information of one or more of the second network elements; and / or The fourth receiving unit is further configured to receive a third response message sent by the fifth network element in response to the fourth request, the third response message being used to indicate model information of one or more of the second network elements. The communication device as described in claim 70, characterized in that, The fourth request carries one or more of the following: Identification information of one or more second network elements; The model requirement information corresponding to the first service; End-to-end latency information corresponding to the first service; The accuracy requirements of the first service. The communication device as described in claim 70 or 71 is characterized in that, The third response message includes one or more of the following: Identification information of one or more second network elements; One or more model identifiers supported by the second network element; Interoperability information of one or more models supported by the second network element. The communication device as described in any one of claims 49-72, characterized in that, In the data pipeline, the next-hop network element of the second network element is the sixth network element. The sending unit is further configured to, in response to the fact that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service, send a first indication information to the second network element, wherein the first indication information is used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The communication device as described in claim 73, characterized in that, The sending unit is further configured to send second indication information to the sixth network element, the second indication information being used to indicate synchronization between the sixth network element and the candidate network element of the sixth network element. The communication device as described in claim 73, characterized in that, The sending unit is further configured to send third indication information to the candidate network elements of the sixth network element, the third indication information being used to synchronize the sixth network element and the candidate network elements of the sixth network element. The communication device as described in any one of claims 49-75, characterized in that, The second network element includes one or more of the following: terminal equipment, access network equipment, network elements in the core network, and third-party servers. A communication device, characterized in that, The communication device is a second network element, including: The receiving unit is used to receive first information sent by the first network element, wherein the first information is associated with the service requirements of the first service to be transmitted in the data pipeline. The communication device as described in claim 77, characterized in that, The first information is used to configure the transmission strategy for transmitting the first service in the data pipeline. The communication device as described in claim 78, characterized in that, The transmission strategy includes one or more of the following: Information indicating the data pipeline for transmitting the first service; A first strategy used to indicate the data processing requirements corresponding to the data pipeline; A second strategy for indicating the computing power requirements corresponding to the data pipeline; A third strategy used to indicate the model requirements corresponding to the data pipeline; A fourth strategy for indicating the energy consumption requirements corresponding to the data pipeline; A fifth strategy used to indicate the storage requirements corresponding to the data pipeline; A sixth strategy used to indicate the data routing requirements corresponding to the data pipeline. The communication device as described in claim 79, characterized in that, The first strategy is used to indicate one or more of the following: The role of the second network element in the data pipeline; The delay in data processing by the second network element in the data pipeline; The input data format corresponding to the second network element in the data pipeline; The output data format corresponding to the second network element in the data pipeline; The amount of input data corresponding to the second network element in the data pipeline; The amount of output data corresponding to the second network element in the data pipeline; In the data pipeline, the second network element will output the delay of data transmission to the next hop network element. The communication device as described in claim 79 or 80 is characterized in that, The second strategy is used to indicate one or more of the following: The computing power consumed by the second network element in the data pipeline; The computing power type corresponding to the second network element in the data pipeline. The communication device as described in any one of claims 79-81, characterized in that, The third strategy is used to indicate one or more of the following Multiple: The model used by the second network element in the data pipeline; The model interoperability information corresponding to the second network element in the data pipeline. The communication device as described in any one of claims 79-82, characterized in that, The fourth strategy is used to indicate the energy consumed by the second network element in the data pipeline. The communication device as described in any one of claims 79-83, characterized in that, The fifth strategy is used to indicate whether the second network element in the data pipeline needs to support storing the data corresponding to the second network element and / or the data processing method corresponding to the second network element. The communication device as described in any one of claims 79-84, characterized in that, The sixth strategy is used to indicate one or more of the following: The upstream network element of the second network element in the data pipeline; The next-hop network element of the second network element in the data pipeline; Does the data pipeline contain a candidate path for transmitting the service data of the first service? The candidate previous hop network element and / or candidate next hop network element corresponding to the second network element in the data pipeline; The priority of multiple candidate next-hop network elements corresponding to the second network element in the data pipeline; The strategy for path switching of the second network element in the data pipeline; Does the next-hop network element of the second network element in the data pipeline need to be synchronized with the candidate next-hop network element corresponding to the second network element? The communication device as described in any one of claims 78-85, characterized in that, The communication device includes: The first sending unit is configured to send a first response message to the first network element, wherein the first response message is used to indicate whether the transmission strategy is accepted or rejected. The communication device as described in claim 86, characterized in that, The first response message includes one or more of the following: The computing power information supported by the second network element; The second network element supports data processing latency information; The energy consumption information supported by the second network element; The model information supported by the second network element. The communication device as described in claim 86, characterized in that, The first response message is used to indicate that the transmission policy is rejected, and the first response message carries the reason for rejecting the transmission policy. The communication device as described in any one of claims 77-88, characterized in that, The communication device also includes: In the data pipeline, the second sending unit is used to send the service data of the first service to the next-hop network element of the second network element. The communication device as described in any one of claims 77-89, characterized in that, In the data pipeline, the next-hop network element of the second network element is the sixth network element. The receiving unit is further configured to receive a first indication information sent by the first network element in response to the fact that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The first indication information is used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The communication device as described in any one of claims 77-89, characterized in that, In the data pipeline, the next-hop network element of the second network element is the sixth network element. The receiving unit is further configured to receive a fourth indication information sent by the sixth network element, the fourth indication information being used to indicate that the performance of the data pipeline between the second network element and the sixth network element cannot meet the service requirements of the first service. The communication device as described in claim 90 or 91, characterized in that, The communication device also includes: The processing unit is used to determine the candidate network elements of the sixth network element based on the pre-configured candidate network element information of the sixth network element. The third sending unit is used to send the service data of the first service to the candidate network element of the sixth network element in the data pipeline. A communication device, characterized in that, The communication equipment is a third network element, including: The sending unit is used to send a first request to the first network element, the first request being used to request the establishment of a data pipeline for transmitting the first service. The communication device as described in claim 93 is characterized in that, The data pipeline includes one or more second network elements, and the first request carries one or more of the following: The business requirements information for the first service; Information used to identify candidate network elements for one or more second network elements. The communication device as described in claim 94, characterized in that, The service requirements of the first service include one or more of the following: end-to-end latency requirements of the first service, accuracy requirements of the first service, reliability requirements of the first service, and so on. The computing power requirements of the first service, the storage requirements of the first service, the energy consumption requirements of the first service, the security requirements of the first service, and the location requirements of the first service. The communication device as described in any one of claims 93-95, characterized in that, The third network element includes terminal equipment and / or network elements in the core network. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs one of the following: the method as described in any one of claims 1-28, the method as described in any one of claims 29-40, or the method as described in any one of claims 45-48. An apparatus characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform one of the following: the method of any one of claims 1-28, the method of any one of claims 29-40, or the method of any one of claims 45-48. A chip characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform one of the following: the method of any one of claims 1-28, the method of any one of claims 29-40, or the method of any one of claims 45-48. A computer-readable storage medium, characterized in that, It stores a program that causes a computer to perform one of the following: the method as claimed in any one of claims 1-28, the method as claimed in any one of claims 29-40, or the method as claimed in any one of claims 45-48. A computer program product, characterized in that, The program includes a method that causes a computer to perform one of the following: the method of any one of claims 1-28, the method of any one of claims 29-40, or the method of any one of claims 45-48. A computer program, characterized in that, The computer program causes the computer to perform one of the following: the method as claimed in any one of claims 1-28, the method as claimed in any one of claims 29-40, or the method as claimed in any one of claims 45-48.

Images