Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The wireless communication method comprises: a first network element sends a first message to a second network element, wherein the first message is used for requesting to monitor a data pipeline, the data pipeline is used for providing a data service, and the first network element is used for access authentication and / or access control of the data service.

Description

Method and communication device for wireless communication TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, and more particularly, to a method and a communication device for wireless communication. BACKGROUND

[0002] A data pipeline can provide a full flow service for data from collection (or collection) to reception, and operating data in the data pipeline can facilitate simplifying the process of data management and improving data processing efficiency. In the scenario of providing data service by using the data pipeline, how to manage and / or control the data pipeline is a problem to be solved.

[0003] SUMMARY

[0004] The present application provides a method and a communication device for wireless communication. The various aspects involved in the present application are introduced below.

[0005] In a first aspect, a method for wireless communication is provided, comprising: a first network element sending a first message to a second network element, the first message being used to request monitoring of a data pipeline; wherein the data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0006] In a second aspect, a method for wireless communication is provided, comprising: a second network element receiving a first message sent by a first network element, the first message being used to request monitoring of a data pipeline; wherein the data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0007] In a third aspect, a method for wireless communication is provided, comprising: a third network element receiving a third message sent by a first network element, the third message being used to request storing first information, the first information being used to indicate a monitoring result corresponding to an operation performed on data in a data pipeline, wherein the data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service, and the third network element is used to provide storage and retrieval functions of data operations.

[0008] In a fourth aspect, a method for wireless communication is provided, comprising: a fourth network element sending a sixth message to a first network element, the sixth message being used to request monitoring of a data pipeline; wherein the data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0009] In a fifth aspect, a communication device is provided, the communication device being a first network element, the communication device comprising: a first sending module, configured to send a first message to a second network element, the first message being used to request monitoring of a data pipe, wherein the data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0010] In a sixth aspect, a communication device is provided, the communication device being a second network element, the communication device comprising: a receiving module, configured to receive a first message sent by a first network element, the first message being used to request monitoring of a data pipe, wherein the data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0011] In a seventh aspect, a communication device is provided, the communication device being a third network element, the communication device comprising: a first receiving module, configured to receive a third message sent by a first network element, the third message being used to request storing of first information, the first information being used to indicate a monitoring result corresponding to an operation performed on data in a data pipe, wherein the data pipe is used to provide a data service, the first network element is used for access authentication and / or access control of the data service, and the third network element is used to provide a storage and retrieval function of the data operation.

[0012] In an eighth aspect, a communication device is provided, the communication device being a fourth network element, the communication device comprising: a sending module, configured to send a sixth message to a first network element, the sixth message being used to request monitoring of a data pipe, wherein the data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0013] In a ninth aspect, a communication device is provided, comprising a processor, a memory and a communication interface, the memory being used to store one or more computer programs, and the processor being used to invoke the computer program in the memory to make the communication device perform some or all of the steps in the methods in the aspects described above.

[0014] In a tenth aspect, an embodiment of the present application provides a communication system, which comprises the communication device described above. In another possible design, the system can further comprise other devices interacting with the communication device in the solutions provided by the embodiments of the present application.

[0015] In an eleventh aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program makes a computer perform some or all of the steps in the methods in the aspects described above.

[0016] In a twelfth aspect, an embodiment of the present application provides a computer program product, which includes a non-transitory computer readable storage medium storing a computer program, the computer program is operable to cause a computer to execute some or all of the steps of the methods in the various aspects described above. In some implementations, the computer program product can be a software installation package.

[0017] In a thirteenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can invoke and run a computer program from the memory to implement some or all of the steps described in the methods of the various aspects described above.

[0018] The embodiments of the present application can monitor the data pipe to achieve management and / or control of the data pipe by monitoring the data pipe, thereby facilitating implementation of diversified service requirements. BRIEF DESCRIPTION OF DRAWINGS

[0019] FIG. 1 is an example diagram of a system architecture of a wireless communication system to which embodiments of the present application can be applied.

[0020] FIG. 2 is a flow diagram of quality of service (QoS) monitoring.

[0021] FIG. 3 is an example diagram of a communication system architecture including a data plane according to an embodiment of the present application.

[0022] FIG. 4 is an example diagram of a data pipe according to an embodiment of the present application.

[0023] FIG. 5 is a flow diagram of a method of wireless communication according to an embodiment of the present application.

[0024] FIG. 6 is a flow diagram of a method of wireless communication according to another embodiment of the present application.

[0025] FIG. 7 is a flow diagram of a method of wireless communication according to yet another embodiment of the present application.

[0026] FIG. 8 is an example diagram of data transmission in a data pipe according to an embodiment of the present application.

[0027] FIG. 9 is a flow diagram of a method of wireless communication according to yet another embodiment of the present application.

[0028] FIG. 10 is a flow diagram of a method of wireless communication according to yet another embodiment of the present application.

[0029] FIG. 11 is a flow diagram of a method of wireless communication according to yet another embodiment of the present application.

[0030] FIG. 12 is a structure diagram of a communication device according to an embodiment of the present application.

[0031] FIG. 13 is a schematic diagram of a structure of a communication device according to another embodiment of the present application.

[0032] FIG. 14 is a schematic diagram of a structure of a communication device according to yet another embodiment of the present application.

[0033] FIG. 15 is a schematic diagram of a structure of a communication device according to yet another embodiment of the present application.

[0034] FIG. 16 is a schematic diagram of a structure of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0035] Communication system architecture

[0036] FIG. 1 is an example of a system architecture of a wireless communication system 100 to which embodiments of the present application can be applied. The system architecture shown in FIG. 1 can include terminal devices, access network (AN) devices, and network elements in a core network.

[0037] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a 5th generation (5G) system or new radio (NR), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), and the like. The technical solutions provided by the present application can also be applied to future communication systems, such as a 6th generation mobile communication system, a satellite communication system, and the like.

[0038] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), an MT, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless terminal, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device providing voice and / or data connectivity for a user, and can be used to connect people, things and machines, such as handheld devices with wireless connection function, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device to device (D2D), etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signals through the base station.

[0039] The access network device can be an access device through which a terminal device accesses the network architecture wirelessly, and is mainly responsible for radio resource management, QoS management, data compression and encryption, etc. on the air interface side. The access network device can also be referred to as a radio access network (RAN) device, for example, the access network device can be a base station. The base station can broadly cover various names in the following or replace the following names, such as: NodeB (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. The base station can be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station can also refer to a communication module, modem or chip used in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs the function of a base station in D2D, V2X, machine-to-machine (M2M) communication, a network side device in a 6G network, a device that performs the function of a base station in a future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.

[0040] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, the helicopter or the drone can be configured to serve as a device that communicates with another base station.

[0041] In some deployments, the access network device in the embodiments of the present application can refer to a CU or a DU, or the access network device includes a CU and a DU. The gNB can also include an AAU.

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

[0043] The UPF network element can be used to forward and receive data of the terminal device. For example, the UPF network element can receive service data from a data network and transmit it to the terminal device through the access network device; the UPF network element can also receive user data from the terminal device through the access network device and forward it to the data network. Among them, 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 a user plane connection between the UPF network element and the access network device, and a channel established between the access network device and the terminal device. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.

[0044] The AMF network element can be used to manage the access of the terminal device to the core network, for example, location update of the terminal device, registration network, access control, mobility management of the terminal device, attachment and detachment of the terminal device, and the like. The AMF network element can also provide storage resources for the control plane of the session for the terminal device in the case of providing services for the session, to store the session identifier, the SMF network element identifier associated with the session identifier, and the like.

[0045] The SMF network element can be used to select a user plane network element for the terminal device, redirect a user plane network element for the terminal device, allocate an internet protocol (IP) address for the terminal device, establish a bearer (also referred to as a session) between the terminal device and the UPF network element, modify, release, and QoS control of the session.

[0046] The PCF network element is used to provide policies such as QoS policies, slice selection policies, and the like to the AMF network element and the SMF network element.

[0047] The DN can provide data services for users, such as IP multi-media service (IMS) networks, the Internet, and the like. There can be various application servers (ASs) in the DN to provide different application services, such as operator services, Internet access, or third-party services, and the like, and the ASs can implement the functions of application functions (AFs). Among them, the AF network element is used to interact with the network elements in the 3GPP core network to support application influence data routing, access network exposure functions, and interact with the PCF network element for policy control, and the like.

[0048] The NSSF is used for network slice selection, and the supported functions include: selecting a set of network slice implementations to serve the terminal device; determining the allowed network slice selection assistance information (NSSAI), and determining the mapping to the single-network slice selection assistance information (S-NSSAI) of the subscription when needed; determining the configured NSSAI, and determining the mapping to the S-NSSAI of the subscription when needed; determining a set of AMFs that can be queried for the terminal device, or determining a list of candidate AMFs based on configuration.

[0049] The AUSF is used to receive a request for authentication of the terminal device from the AMF, request a key from the UDM, and then forward the issued key to the AMF for authentication processing.

[0050] The UDM includes functions such as generation and storage of user subscription data, management of authentication data, and supports interaction with external third-party servers.

[0051] The NEF is used for capability exposure, that is, based on the NEF, the capabilities of the network can be output to external networks. An external untrusted application can access internal data of the core network through the NEF to ensure the security of the network. The NEF can provide functions such as external application QoS capability exposure, event subscription, AF request distribution, and the like.

[0052] The NRF is used for registration, management, and state detection of network elements in the core network, so as to realize automatic management of network elements in the core network. When a network element in the core network starts, it must be registered in the NRF to provide services. The registration information may include, for example, the type, address, and service list of the network element.

[0053] In addition, some networks (for example, a 5G network) also increase a network data analysis function (network data analytics function, NWDAF) in the core network. Based on the NWDAF, data can be collected from various network elements, network management systems, and the like in the core network, and big data statistics, analysis, or intelligent data analysis can be performed, so as to obtain analysis or prediction data on the network side, and then assist various network elements to more effectively control terminal device access according to the data analysis results.

[0054] In some communication systems (for example, a 5G system, a 6G system, and the like), the network elements in the core network can also be referred to as network functions (network function, NF).

[0055] In the system architecture shown in FIG. 1, an important feature is that these system architectures include a service-oriented architecture, that is, a service provider (such as a network element in the core network) can provide specific services, and other network elements (consumers) can call through a defined API interface.

[0056] It should be noted that each network element in FIG. 1 can be a network element in a hardware device, a software function running on a dedicated hardware, or a virtualized function instantiated on a platform (for example, a cloud platform). It should be noted that in the network architecture shown in FIG. 1, only network elements included in the entire network architecture are exemplarily illustrated. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0057] Those skilled in the art can understand that the network architecture shown in FIG. 1 does not constitute a limitation on the network architecture, and the network architecture can include more or fewer network elements than shown, or combine certain network elements, and the like. It should be understood that the AN or RAN is represented in the form of (R)AN in FIG. 1.

[0058] In some scenarios, the network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; and can also be deployed on the aircraft, balloon and satellite in the air. The scenario in which the network device and the terminal device are located is not limited in the embodiments of the present application.

[0059] By way of example and without limitation, in the embodiments of the present application, the network device can have a mobile characteristic, for example, the network device can be a mobile device. In some embodiments of the present application, the network device can be a satellite, a balloon station. For example, the satellite can 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 the present application, the network device can also be a base station arranged at a position on land, water, etc.

[0060] In the embodiments of the present application, the network device can serve a cell, and the terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell. The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cell can include a metro cell, a micro cell, a pico cell, a femto cell, etc., and these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-speed data transmission services.

[0061] QoS monitoring

[0062] There is a method of QoS monitoring in the 5G system to meet the needs of ultra-reliable low latency communication (URLLC) services. QoS monitoring meets the high QoS requirements of URLLC services by real-time monitoring of message delays. The method of QoS monitoring is described below in conjunction with FIG. 2.

[0063] As shown in FIG. 2, the method of QoS monitoring can include steps 1 to 9.

[0064] In step 1, the AF sends a QoS monitoring request to the PCF to request QoS monitoring of a service data flow.

[0065] In step 2, the PCF generates a QoS monitoring policy according to the QoS monitoring request sent by the AF.

[0066] In some embodiments, the QoS monitoring policy is an authorized QoS monitoring policy.

[0067] In some embodiments, the PCF can include the generated QoS monitoring policy in the PCC rule.

[0068] In step 3, the PCF sends the PCC rule to the SMF. The PCC rule includes the QoS monitoring policy described above.

[0069] In some embodiments, the SMF can initiate uplink / downlink packet delay measurement between the terminal device and the UPF based on the QoS monitoring policy in the PCC rule. As an implementation manner, the SMF can initiate the uplink / downlink packet delay measurement between the terminal device and the UPF through a PDU session establishment or modification process.

[0070] In some embodiments, the UPF described above can be a PDU session anchor UPF (PSA UPF).

[0071] In step 4, the SMF sends a QoS monitoring request to the UPF and the RAN respectively.

[0072] In step 5a, the RAN initiates uplink / downlink packet delay measurement of the RAN part according to the QoS monitoring request.

[0073] In some embodiments, the RAN can report the measurement result of the RAN part to the UPF. For example, the RAN can carry the measurement result of the RAN part in an uplink data packet or a dummy uplink data packet to report to the UPF.

[0074] In some embodiments, if the RAN and the UPF are time-synchronized, the RAN and the UPF can support one-way packet delay monitoring. In some embodiments, if the time of the RAN and the UPF is not synchronized, the RAN and the UPF can consider that the uplink and downlink packet delays are the same.

[0075] In step 5b, the UPF sends a downlink monitoring packet to the RAN.

[0076] In some embodiments, the UPF can encapsulate the QoS flow identifier (QFI), the QoS monitoring packet (QMP) indication, and the local time T1 of sending the downlink monitoring packet in a general packet radio service tunneling protocol user plane (GPRS tunneling protocol user plane, GTP-U) header.

[0077] In step 6, the RAN records the local time T1 of receiving the GTP-U header and the local time T2 of receiving the downlink monitoring packet.

[0078] In step 7, the RAN sends a monitoring response packet to the UPF.

[0079] As an implementation manner, the RAN can take an uplink data packet with the same QFI as the downlink monitoring packet from the terminal device as the monitoring response packet. As another implementation manner, in the case of no uplink data packet, the RAN can send a virtual uplink packet to the UPF as the monitoring response packet.

[0080] In some embodiments, the RAN can encapsulate the QMP indication, the uplink / downlink packet delay result of the RAN part, the times T1, T1, and the local time T3 of sending the uplink monitoring response packet in the GTP-U header.

[0081] In step 8, the UPF records the local time T4 of receiving the monitoring response packet.

[0082] In some embodiments, the UPF can calculate the round-trip delay (for example, in the case of time asynchronization between the RAN and the UPF) or calculate the uplink / downlink packet delay from the RAN to the UPF (for example, in the case of time synchronization between the RAN and the UPF).

[0083] As an implementation manner, in the case of time asynchronization between the RAN and the UPF, the UPF can calculate the uplink / downlink delay by (T2-T1+T4-T3) / 2.

[0084] As an implementation manner, in the case of time synchronization between the RAN and the UPF, the UPF can calculate the uplink packet delay and the downlink packet delay by (T4-T3) and (T2-T1) respectively.

[0085] In some embodiments, after the UPF calculates the uplink / downlink packet delay from the RAN to the UPF, the packet uplink / downlink delay of the RAN part can be added to obtain the uplink / downlink packet delay from the terminal device to the UPF.

[0086] At step 9, the UPF reports the measurement result of the packet delay to the SMF. Step S290 is an optional step. For example, the UPF can report the measurement result of the packet delay to the SMF under certain conditions (e.g., reaching a threshold reported to the SMF).

[0087] For ease of understanding, some related technical knowledge related to the embodiments of the present application is introduced first. The following related technologies can be combined with the technical solutions of the embodiments of the present application in any way as optional schemes, which all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0088] Data plane (DP)

[0089] In some scenarios (for example, practical experience of intelligentization of a 5G network), it is very difficult to obtain data, and the quality of the data is difficult to guarantee. On the one hand, data collection based on network management also has the problems of less data types, longer collection period (15 min), non-uniform data format, naming, and calculation method of different manufacturers, which leads to difficulty in opening network management data. On the other hand, it is more difficult to collect data from terminal devices, because collecting data from terminal devices may lead to leakage of private data and reduction of data security. Therefore, how to guarantee that the data collected from terminal devices can be processed by a trusted node so as to not leak the privacy of users, or how to track the collected data in the whole life cycle and guarantee that the use of any data by any data consumer will be recorded, are problems that cannot be solved at present.

[0090] In view of the above problems, in some network architectures (for example, a 6G network architecture), a scheme of adding a “data plane” is proposed. In some implementation modes, the data elements in the data plane will cover internal and external data of the network, and specifically include business data, user data, network data, perception data, and external data.

[0091] In some implementation modes, the basic data service includes data collection, data preprocessing, data storage, data access, data sharing and collaboration, and the like. The basic data service can have the following characteristics: supporting trusted authentication, authorization, and access, efficient data storage and management, on-demand data collection and data preprocessing, and external data opening. That is, the data plane can include one or more network elements that provide basic data services for the above-mentioned data elements, or in other words, the data plane includes one or more functions (or network elements) to support one or more of the following data services: trusted between data sources and data consumers, flexible data collection, data opening, data preprocessing, data storage, and data tracking. The data source and / or the data consumer can be any node, for example, the data source can be any node that has a data storage requirement, and the data consumer can be any node that has a data calling requirement.

[0092] In some networks (e.g., a 6G network), "trust" will become an important requirement for users of data services, where the data services are mainly embodied in data collection, data storage, data access, data sharing, and the like. How to provide trusted storage and traceable features of data in the process of providing data services becomes a key problem that needs to be solved in the data plane.

[0093] To address the above problems, an embodiment of the present application introduces a data plane. The following introduces a schematic diagram of a communication system architecture including a data plane according to an embodiment of the present application.

[0094] 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 in the embodiments of the present application, the name of the data plane is not limited, for example, the data plane can also be referred to as "data plane", "data network element set", or "data service plane", etc. In future communication architectures, this name can be replaced by a name in a future communication system that is the same as or similar to the data plane function. For ease of description, the embodiments of the present application take the data plane as an example for introduction.

[0095] Referring to FIG. 3, the data plane can include a network element 1 and / or a network element 2. In some implementations, the network element 1 is configured to provide data operation functions of the data plane, or in other words, the network element 1 is configured to operate data in the data plane. The embodiments of the present application do not limit the data operation functions of the data plane provided by the network element 1. For example, the network element 1 can provide one or more of the following operations: data storage function of the data plane, data retrieval (invocation) function of the data plane, data sharing function of the data plane, data collection function of the data plane, data processing function of the data plane, data opening function of the data plane, data verification function of the data plane, and the like.

[0096] The embodiments of the present application do not limit the name of the network element 1. For example, the name of the network element 1 can 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, and the like. Of course, the network element 1 can also be other names, such as a name corresponding to a network element with the same or similar function in a future communication system.

[0097] In some implementations, the network element 1 can be a blockchain node (e.g., a blockchain node 210) located in a blockchain, which helps to achieve functions such as trusted data storage in the communication system architecture by virtue of the characteristics of the blockchain.

[0098] It should be noted that the network element 1 can correspond to one or more entity devices (for example, servers). If the network element 1 corresponds to multiple entity devices, it can be understood that the network element is distributed. Among them, part or all of the entity devices in the multiple entity devices can be located in the blockchain. For example, the multiple entity devices can correspond to multiple blockchain nodes in the blockchain.

[0099] In some implementations, if the network element 1 is distributed, and the multiple entity devices corresponding to the network element 1 belong to the same blockchain node, the multiple entity devices will store the same data, thereby ensuring the data unforgeability.

[0100] The above introduces the network element 1 in the data plane provided by the embodiments of the present application, and the following introduces the network element 2 in the data plane provided by the embodiments of the present application.

[0101] In some implementations, the network element 2 is used for access authentication and / or access control of data services, or in other words, the network element 2 is used for managing or controlling data plane access, that is, the 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, the network element 2 can also be called a data plane access controller (DPAC). Of course, in the embodiments of the present application, the 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, and the embodiments of the present application do not limit this.

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

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

[0104] In some embodiments, the function corresponding to the network element 2 can be realized by enhancing the data collection coordination function (DCCF). That is, the network element 2 can be a network element with the DCCF. Of course, in the embodiments of the present application, the network element 2 can also be an independent network element in the core network, and the embodiments of the present application do not limit this.

[0105] For ease of understanding, the following takes data collection by a data plane to a terminal device as an example to introduce the network element 1 and the network element 2 in the embodiments of the present application. It is assumed that the terminal device is a data source, the network element 1 is a DPR, and the network element 2 is a DPAC. In the process of transaction between the terminal device and the data plane, the terminal device can send a transaction request to the DPAC, and the transaction request carries one or more of the following: data source ID (i.e., terminal device ID), data itself, and data description information. Correspondingly, the DPAC verifies the data source ID according to the transaction request sent by the terminal device. If the verification is passed, 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 is used to describe the function of the data, or in other words, the data description information is used to describe the attribute or content of the data. For example, for the sensing data of the terminal device, the data description information of the data can be used to indicate that the data is the sensing data of the terminal device. For example, for the location data of the terminal device, the data description information of the data can be used to indicate that the data is the location data of the terminal device. For example, for the QoS data or session data of the terminal device, the data description information of the data can be used to indicate that the data is the QoS data or session data of the terminal device, and so on.

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

[0107] In some scenarios, the data plane is a distributed architecture, which helps to support flexible and efficient data management. That is, the distributed data plane can include multiple network elements 1, and correspondingly, different network elements 1 can be associated with different or the same network element 2. At this time, the data source can access through the data plane (or network element 2) that is relatively close, thereby reducing the transmission delay of the data.

[0108] Data pipeline

[0109] In some communication systems (such as a 6G system), considering the diversified needs of services, different nodes can need to operate data respectively, for example, different nodes can need to collect, process, receive (or aggregate) data, and so on. Based on the above needs, as a possible implementation manner, data in some communication systems can be operated in a data pipeline to simplify the process of data management and improve the efficiency of data processing. The data pipeline is introduced as follows.

[0110] In some embodiments, the data pipeline can be used to provide data services. For example, the data pipeline can provide a full-process service from data collection to processing and finally to reception.

[0111] In some embodiments, a data pipeline can be used to provide data services in a data plane, or in other words, a data pipeline can be used to provide data services in a data plane. In this way, a data pipeline can be an important function supported by a data plane, and can provide a full flow service for data from collection to final reception in a data plane.

[0112] In some embodiments, a data pipeline can be understood as a collection of a series of data processing steps. For example, in a data pipeline, data can be collected by a data source and sent to the next node for processing, the next node processes the data and then forwards it to the next node, and so on, to achieve on-the-fly processing of data.

[0113] Therefore, in some embodiments, it can be understood that the running mode of a data pipeline is similar to an assembly line in a manufacturing process. In this way, the output of one network entity after processing data can become the input of the subsequent network entity, so that data can achieve smooth and automated workflow in a data pipeline, which is beneficial to simplify data management process and provide data processing efficiency. In addition, the introduction of a data pipeline can also ensure the integrity of data.

[0114] The name of the data pipeline is not limited in the embodiments of the present application. For example, the data pipeline can also be referred to as a "data channel", a "data processing collection" and the like. It should be noted that in future communication systems, the name can be replaced by a name in a future communication system that is the same as or similar to the function of the data pipeline. In order to facilitate understanding, the embodiments of the present application take the data pipeline as an example for introduction.

[0115] The data services provided by the data pipeline are not specifically limited in the embodiments of the present application. Exemplarily, the data pipeline can be used to provide one or more of the following data services: data collection, data processing, data reception (or data aggregation).

[0116] The data processing that can be provided by the data pipeline is not specifically limited in the embodiments of the present application. Exemplarily, the data pipeline can provide one or more of the following data processing: compression processing, normalization processing, data processing based on an artificial intelligence (AI) model, anonymization processing, data filtering, data analysis, data calculation, and the like.

[0117] The embodiments of the present application do not limit the data types that can be processed by the data pipeline, or in other words, the data pipeline can process any type of data. For example, the data pipeline can process one or more of the following data types: continuous data, intermittent data, batch data. Of course, the embodiments of the present application are not limited thereto, for example, in the case of data types divided in other ways, the data pipeline can process any type of data under other division manners. As an example, the data pipeline can process one or more of the following data types: perception type data, positioning type data, AI type data, etc.

[0118] For ease of understanding, the composition of the data pipeline is introduced below in conjunction with FIG. 4. As shown in FIG. 4, the data pipeline can be composed of data pipeline participants (or data pipeline contributors) and / or the processing of data by data pipeline participants.

[0119] The embodiments of the present application do not limit the types of data pipeline participants, and for example, the types of data pipeline participants can include one or more of the following types: a data source (hereinafter referred to as a data source) in the data pipeline, an intermediate node (hereinafter referred to as an intermediate node) in the data pipeline, and a data receiver (hereinafter referred to as a data receiver or a data recipient) in the data pipeline.

[0120] The data source can be understood as the starting point of the data pipeline and can provide data collection services. One or more data sources can be included in a data pipeline to achieve diversified data services. For example, in the example of FIG. 4, the 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.

[0121] In some embodiments, after the data source collects data, it can send the data to the next node (such as an intermediate node). For example, after the data source collects data and processes the collected data, it sends the data to the next node. Alternatively, the data source collects data and directly sends the collected data to the next node, etc. The next node of the data source can be an intermediate node, but the embodiments of the present application are not limited thereto, and the next node of the data source can also be a data receiver.

[0122] In some embodiments, the data source can send data in the form of a data packet. Similarly, the intermediate node can also send data in the form of a data packet, which will not be described again hereinafter.

[0123] The embodiments of the present application do not limit the data source. For example, the data source can include one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device. In some embodiments, the network management device can include an operations, administration, and maintenance (OAM) device, for example. In some embodiments, the application device can include one or more of the following: an application server, an AF, a third-party application, a third-party server, and the like.

[0124] The intermediate node can provide a data processing service. For example, the intermediate node can provide one or more of the following data processing services: compression processing, normalization processing, AI model-based data processing, anonymization processing, data filtering, data analysis, data calculation, and the like.

[0125] One or more intermediate nodes can be included in one data pipeline. Different intermediate nodes can provide the same data processing or different data processing. For example, in the example of FIG. 4, the 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 compression processing on data, except that the specific compression method or the value of the compressed data can be different. Alternatively, data pipeline participant X and data pipeline participant Y can provide different data processing, such as compression processing by data pipeline participant X and normalization processing by data pipeline participant Y.

[0126] One intermediate node can perform one or more processes on the data in the data pipeline, and the embodiments of the present application do not limit this. For example, data pipeline participant X can only perform compression processing on the data. Alternatively, data pipeline participant X can perform compression processing and normalization processing on the data, and the like.

[0127] In some embodiments, after the intermediate node processes the data in the data pipeline, the intermediate node can send the processed data to the next node, such as the next intermediate node or the data recipient. For example, in the example of FIG. 4, data pipeline participant X can send the processed data to data pipeline participant Y. Data pipeline participant Y can send the processed data to the data recipient.

[0128] The embodiments of the present application do not limit the intermediate node. For example, the intermediate node can include one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

[0129] The data receiver can be understood as the end point of the data pipeline. The data receiver can receive the data after final processing and no longer process the data. One or more data receivers can be included in one data pipeline. For example, in the example of FIG. 4, the data receiver can include the data pipeline participant B.

[0130] Embodiments of the present application do not limit the data receiver. For example, the data receiver can include one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

[0131] In some embodiments, the data pipeline can further include a controller of the data pipeline. The controller of the data pipeline can manage and / or control the entire service process of the data pipeline. For example, the controller of the data pipeline can perform one or more of the following operations: determining various nodes (such as data sources, intermediate nodes, data receivers, etc.) of the data pipeline, establishing the data pipeline, allocating data processing strategies in the data pipeline, determining data routing topology, and managing nodes in the data pipeline to perform performance monitoring of the data pipeline.

[0132] Embodiments of the present application do not limit the controller of the data pipeline. For example, the controller of the data pipeline can be the network element 2 (such as DPAC) mentioned above, or the controller of the data pipeline can be a new network element introduced in a future communication system, as long as it is used to manage and / or control the data pipeline.

[0133] It should be noted that, in some embodiments, the controller of the data pipeline can belong to the composition of the data pipeline. In some embodiments, the controller of the data pipeline can not belong to the composition of the data pipeline, and embodiments of the present application do not limit this.

[0134] Continuing to refer to FIG. 4, the other nodes in FIG. 4 are nodes that do not participate in the data pipeline shown in FIG. 4, or in other words, the controller of the data pipeline does not select the other nodes shown in FIG. 4 as nodes in the data pipeline. In some embodiments, the other nodes can be nodes in another data pipeline, or the other nodes can not participate in any data pipeline, and embodiments of the present application do not limit this.

[0135] As can be seen from the above description, the introduction of the data pipeline is beneficial to simplify the data management process and improve data processing efficiency, thereby ensuring that the communication system supports more diversified services. Therefore, in the scenario of providing data services by using the data pipeline, how to manage the data pipeline is a problem to be solved.

[0136] To solve the above problems, the embodiments of the present application provide a method and a communication device for wireless communication, which can monitor a data pipe, so as to realize management and / or control of the data pipe by monitoring the data pipe, such as determining participants of the data pipe, adjusting configuration of the data pipe, etc., thereby realizing diversified service requirements.

[0137] To monitor the data pipe, it is necessary to define an index (hereinafter referred to as an index) of the data pipe to be monitored. The index is introduced as follows.

[0138] In some embodiments, the index can be associated with one or more of the following: pipe performance of the data pipe, quality of data in the data pipe, and operation performed on data in the data pipe.

[0139] In some embodiments, the index can include one or more of the following: latency of the data pipe, throughput of the data pipe, resource consumed by the data pipe, size of data in the data pipe, consistency of data in the data pipe, integrity of data in the data pipe, bias of data in the data pipe, and operation performed on data in the data pipe.

[0140] As an example, the index can include the latency of the data pipe.

[0141] As another example, the index can include the throughput of the data pipe.

[0142] As yet another example, the index can include the latency of the data pipe and the throughput of the data pipe.

[0143] The latency of the data pipe and the throughput of the data pipe are the most basic performances of the data pipe, and need to be accurately monitored. Considering that the data pipe can involve multiple data sources, accurate strategy configuration of the latency of the data pipe and the throughput of the data pipe is beneficial to realize performance monitoring of the data pipe with a flexible topology.

[0144] Of course, the index can also include a combination of one or more of the above indexes, such as the index including one or more of the size of data in the data pipe, the consistency of data in the data pipe, the integrity of data in the data pipe, and the bias of data in the data pipe; or the index including the operation performed on data in the data pipe; or the index including the latency of the data pipe and the operation performed on data in the data pipe, etc., which are not limited in the embodiments of the present application.

[0145] In some embodiments, the latency of the data pipeline is an end-to-end latency. For example, the latency of the data pipeline includes the latency experienced by the data in the data pipeline from being collected to being received by the data recipient, i.e., the latency experienced by the data from being collected by the data source, to being processed by the intermediate nodes, to being received by the data recipient.

[0146] In some embodiments, the latency of the data pipeline includes a transmission latency of the data in the data pipeline and a processing latency of the data in the data pipeline.

[0147] In some embodiments, the latency of the data pipeline is the overall latency of the data pipeline, or in other words, the latency of the data pipeline is a complete latency corresponding to the process of the data from being collected to being received in the data pipeline.

[0148] In some embodiments, considering that some services need multiple iterations (e.g., training data used in AI model training scenarios), the latency of the data pipeline can include one or more of the following: a one-way latency, a latency for completing the entire service.

[0149] The one-way latency described above can refer to the latency experienced by the data from being collected to being received by the data recipient in one run of the service. For example, in one training process in the AI model training scenario, the latency experienced by the data from being collected to being received by the data recipient.

[0150] The latency for completing the entire service described above can refer to the latency experienced by the data from being collected for the first time to being received by the data recipient for the last time in the process of completing the entire service. For example, in the entire AI model training process (including one or more training processes) in the AI model training scenario, the latency experienced by the data from being collected for the first time to being received by the data recipient for the last time.

[0151] In some embodiments, the latency for completing the entire service can include one or more one-way latencies.

[0152] The throughput (i.e., bit rate) of the data pipeline can be used to indicate the throughput of the entire data pipeline, or in other words, to indicate the overall result of the throughput of the data pipeline. Considering that the throughputs of the various nodes in the data pipeline can be different, the indication manner of the throughput of the data pipeline is not limited in the embodiments of the present application. Exemplarily, the throughput of the data pipeline can include one or more of the following: the throughputs of the various nodes in the data pipeline, the throughput of the data recipient in the data pipeline, and the maximum value among the throughputs of the various nodes in the data pipeline.

[0153] As an example, the throughput of the data pipeline can include the throughputs of the various nodes in the data pipeline, i.e., the throughput of the data pipeline can include the throughput of the data source, the throughput of the intermediate nodes, and the throughput of the data recipient.

[0154] As another example, the throughput of the data pipeline can include the throughput of the data sink. That is, the throughput of the data sink can be taken as the throughput of the entire data pipeline.

[0155] As yet another example, the throughput of the data pipeline can include the maximum of the throughputs of the various nodes in the data pipeline. That is, the throughput of the data pipeline can include the maximum of the throughput of the data source, the throughput of the intermediate node, and the throughput of the data sink. For example, when the throughput of the data source is the maximum, the throughput of the data pipeline is the throughput of the data source. Or, when the throughput of the intermediate node is the maximum, the throughput of the data pipeline is the throughput of the intermediate node. Or, when the throughput of the data sink is the maximum, the throughput of the data pipeline is the throughput of the data sink.

[0156] It should be noted that the throughputs of the various nodes in the data pipeline can be different because the data pipeline can include multiple data sources, and the data rates from the different data sources to the intermediate node and from the intermediate node to the data sink can be different.

[0157] The embodiments of the present application do not limit the resources consumed by the data pipeline. For example, the resources consumed by the data pipeline can include one or more of the following: computing resources, energy resources.

[0158] In some embodiments, the computing resources consumed by the data pipeline can include the computing resources consumed by each node for processing data, or in other words, the computing resources consumed by the data pipeline can be the sum of the computing resources consumed by each node. In some embodiments, the computing resources consumed by the data pipeline can be represented by one or more of the following: floating point operations per second (FLOPS), tera operations per second (TOPS), floating point of operations (FLOPs), tera floating point operations per second (TFLOPS). The embodiments of the present application are not limited to the above-listed representation manners, and the computing resources consumed by the data pipeline can be represented by any computing resource representation manner.

[0159] In some embodiments, the energy resource consumed by the data pipeline (hereinafter referred to as the energy consumption of the data pipeline) can include the total energy consumption required by the data pipeline to support the processing and transmission of data, or in other words, the energy consumption of the data pipeline can include the sum of the energy consumption of each node. In some embodiments, the energy consumption of the data pipeline can be expressed in kilowatt hours (kwh).

[0160] In some embodiments, one or more of the latency of the data pipeline, the throughput of the data pipeline, and the resource consumed by the data pipeline can be used to indicate the pipeline performance of the data pipeline. However, the embodiments of the present application are not limited thereto, and the pipeline performance of the data pipeline can also be indicated by other indicators.

[0161] The size of the data in the data pipeline (for example, the size of the data set) can represent the size of the original data collected by the data source, or can represent the size of the data output by each node. In some embodiments, the size of the data in the data pipeline can represent the richness of the data, and generally speaking, the larger the data in the data pipeline, the higher the richness of the data. As an example, in the AI model training process, the larger the data in the data pipeline, the more accurate the model training can be ensured, and the higher the generalization can be ensured.

[0162] The consistency of the data in the data pipeline can be used to indicate the consistency of the format of the data transmission. In some embodiments, the data in the data pipeline can be transmitted in a unified format to ensure that the data has high consistency.

[0163] The integrity of the data in the data pipeline can be used to indicate the data feature dimension possessed by the data, that is, the attributes and features possessed by the data. The higher the integrity of the data, the more rich the data feature dimension contained by the data can be. Taking AI model training as an example, the higher the integrity of the data, the more accurate the trained model can be.

[0164] The embodiments of the present application do not limit the data feature dimension possessed by the data. As an example, in the case that the data in the data pipeline includes the description of the characteristics of a person, the data feature dimension possessed by the data can include one or more of the following: gender, age, height, weight, skin color, etc. As another example, in the case that the data in the data pipeline includes the description of the characteristics of a flower, the data feature dimension possessed by the data can include one or more of the following: color, size, shape, etc.

[0165] The bias condition of the data in the data pipeline can be used to indicate the proportion of each data feature dimension in the data in the data pipeline, so as to prevent some data feature dimensions in the data in the data pipeline from having too high a proportion, thereby causing data bias.

[0166] In some embodiments, one or more of the size of the data in the data pipeline, the consistency of the data in the data pipeline, the integrity of the data in the data pipeline, and the bias of the data in the data pipeline can be used to indicate the quality of the data in the data pipeline. However, embodiments of the present application are not limited thereto, and the quality of the data in the data pipeline can also be indicated by other indicators.

[0167] In some embodiments, the operation performed on the data in the data pipeline can include any operation performed on the data in the data pipeline. For example, the operation performed on the data in the data pipeline can include one or more of the following: data collection, data processing, data reception. In some embodiments, the operation performed on the data in the data pipeline should be recorded to achieve traceability and explainability of the data.

[0168] The indicators for monitoring are introduced above, and the method embodiments of the present application are introduced below.

[0169] FIG. 5 is a flow diagram of a method of wireless communication provided by an embodiment of the present application. The method shown in FIG. 5 is introduced from the perspective of the first network element interacting with the second network element. To facilitate understanding, the first network element and the second network element are introduced first.

[0170] In some embodiments, the first network element can be used for access authentication and / or access control of a data service. For example, the first network element can be used for access authentication and / or access control of a data plane, or in other words, the first network element can be used for access authentication and / or access control of a data service provided by a data plane.

[0171] In some embodiments, the first network element can be a controller of a data pipeline.

[0172] As an example, the first network element can be the network element 2 (such as DPAC) mentioned above. For related introduction of the network element 2, please refer to the foregoing description.

[0173] In some embodiments, the second network element can be a participant of a data pipeline. For example, the second network element can include one or more of the following: a data source, an intermediate node, a data receiver.

[0174] In some embodiments, the second network element can include one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, an application device.

[0175] The method shown in FIG. 5 includes step S510, in which the first network element sends a first message to the second network element. The first message is used to request monitoring of a data pipeline.

[0176] In some embodiments, the first message can be used to indicate the requested monitoring indicator, for example, the first message can include explicit indication information of the requested monitoring indicator, or the first message can implicitly indicate the requested monitoring indicator. In this way, each node in the data pipeline can monitor the data pipeline based on the indicator.

[0177] The embodiments of the present application do not limit the implementation manner of the first message implicitly indicating the requested monitoring indicator. As an implementation manner, the first message can carry a monitoring policy, and the monitoring policy implicitly indicates the requested monitoring indicator. As another implementation manner, the type of the first message can implicitly indicate the requested monitoring indicator, and the second network element can determine the requested monitoring indicator according to the type of the first message after receiving the first message.

[0178] In some embodiments, the requested monitoring indicator of the first message is associated with one or more of the following: pipeline performance of the data pipeline, quality of data in the data pipeline, and operation performed on data in the data pipeline.

[0179] In some embodiments, the requested monitoring indicator of the first message can include one or more of the following: latency of the data pipeline, throughput of the data pipeline, resource consumed by the data pipeline, size of data in the data pipeline, consistency of data in the data pipeline, integrity of data in the data pipeline, bias of data in the data pipeline, and operation performed on data in the data pipeline.

[0180] In some embodiments, the first message can include one or more of the following information: identification of the data pipeline, first indication information, and monitoring policy.

[0181] The identification of the data pipeline can be used to uniquely identify one data pipeline, for example, the identification of each data pipeline is different in all data pipelines managed by the controller of the data pipeline. The embodiments of the present application do not limit the acquisition manner of the identification of the data pipeline, for example, the identification of the data pipeline can be assigned by the controller of the data pipeline when establishing the data pipeline. Alternatively, the identification of the data pipeline can be assigned by the session management network element (such as SMF) in the core network.

[0182] The first indication information can be used to indicate the requested monitoring indicator and / or to indicate monitoring of the indicator. For example, the first indication information can include explicit indication information of the specific requested monitoring indicator (such as latency of the data pipeline, throughput of the data pipeline, etc.). Alternatively, the first indication information can be implicit indication information used to indicate monitoring of the indicator. As an example, the first indication information can be a monitoring policy to indicate the requested monitoring indicator through the monitoring policy. As another example, the first indication information can include the type of the first message, and the type of the first message can implicitly indicate the requested monitoring indicator.

[0183] The monitoring policy can be used to instruct the second network element how to monitor the data pipeline. In some embodiments, the monitoring policy is related to one or more of the following factors: the metric, the data pipeline participant.

[0184] In some embodiments, different monitoring policies correspond to different metrics.

[0185] In some embodiments, different monitoring policies correspond to different data pipeline participants (i.e., different second network elements).

[0186] The monitoring policy will be described in more detail below.

[0187] In some embodiments, when the metric includes a latency of the data pipeline, the monitoring policy can be used to instruct one or more of the following: the second network element to add a timestamp of sending data in the sent data; the second network element to determine a latency of data transmission in the data pipeline to the second network element; the second network element to add a processing latency of data in the sent data; the second network element to determine the latency of the data pipeline; the second network element to add an identification of the data pipeline in the sent data; the second network element to add an iteration round corresponding to the data in the sent data; and the second network element to send a threshold of the latency of the data pipeline to the first network element.

[0188] Taking an example in which data is sent in the form of data packets, the monitoring policy can instruct the second network element to add a timestamp of sending a data packet in a packet header of the sent data packet.

[0189] In some embodiments, the latency of data transmission in the data pipeline to the second network element can refer to a latency of data transmission from a last node of the second network element to the second network element. Taking an example in which the second network element is an intermediate node, if a last node of the second network element is a data source, the latency of data transmission to the second network element can refer to a latency of data transmission from the data source to the second network element; if the last node of the second network element is another intermediate node, the latency of data transmission to the second network element can refer to a latency of data transmission from the other intermediate node to the second network element. Taking an example in which the second network element is a data receiver, if a last node of the second network element is a data source, the latency of data transmission to the second network element can refer to a latency of data transmission from the data source to the second network element; if the last node of the second network element is an intermediate node, the latency of data transmission to the second network element can refer to a latency of data transmission from the intermediate node to the second network element.

[0190] In some embodiments, in case that multiple iterations are needed for the completion of the whole service, the monitoring policy can instruct the second network element to add the iteration round corresponding to the data in the transmitted data. For example, in the scenario of AI model training, if the latency of the data pipeline in the whole training process needs to be monitored, the monitoring policy can instruct the second network element to add the iteration round corresponding to the data in the transmitted data.

[0191] In some embodiments, the second network element can determine whether the monitoring result of the latency of the data pipeline needs to be sent to the first network element according to the threshold of the latency of the data pipeline indicated in the monitoring policy. In some embodiments, when the latency of the data pipeline meets the threshold of the latency of the data pipeline indicated in the monitoring policy, the second network element can send the monitoring result of the latency of the data pipeline to the first network element. However, the embodiments of the present application are not limited thereto, for example, the second network element can periodically send the monitoring result of the latency of the data pipeline to the first network element. Alternatively, the second network element can determine whether to send the monitoring result of the latency of the data pipeline to the first network element based on other conditions.

[0192] As an example, in case that the indicator includes the latency of the data pipeline, if the second network element is a data source, the monitoring policy can be used to instruct one or more of the following: the second network element adds the timestamp of the transmitted data in the transmitted data; the second network element adds the processing latency of the data in the transmitted data; the second network element adds the identification of the data pipeline in the transmitted data; and the second network element adds the iteration round corresponding to the data in the transmitted data.

[0193] As another example, in case that the indicator includes the latency of the data pipeline, if the second network element is an intermediate node, the monitoring policy can be used to instruct one or more of the following: the second network element adds the timestamp of the transmitted data in the transmitted data; the second network element determines the latency of the data transmission in the data pipeline to the second network element; the second network element adds the processing latency of the data in the transmitted data; the second network element adds the identification of the data pipeline in the transmitted data; and the second network element adds the iteration round corresponding to the data in the transmitted data.

[0194] In some embodiments, if there are multiple data sources, the latency of the data transmission to the second network element can refer to the maximum among the latencies of the individual data sources transmitting to the second network element. That is, the second network element can compare the transmission latencies of the data sent by the individual data sources, and select the maximum latency as the latency of the data transmission to the second network element. However, the embodiments of the present application are not limited thereto, for example, considering that the different data sources can not send data packets at the same time, as one possible implementation, the second network element can use the time of the last received data packet minus the time of the earliest timestamp of the sent data packet as the latency of the data transmission to the second network element. That is, the intermediate node can not distinguish which data source the data packet is sent by, and directly use the time of the last received data packet minus the time of the earliest timestamp of the sent data packet as the latency of the data transmission to the second network element.

[0195] In some embodiments, if the second network element is an intermediate node, the processing latency of the data by the second network element can be the time of the second node sending the data packet minus the time of the last received data packet (i.e., receiving the data packets sent by all data sources).

[0196] As yet another example, in the case where the metric includes the latency of the data pipeline, if the second network element is a data receiver, the monitoring policy can be used to indicate one or more of: the second network element determining the latency of the data pipeline; the second network element sending a threshold of the latency of the data pipeline to the first network element.

[0197] In some embodiments, in the case where the metric includes the throughput of the data pipeline, the monitoring policy can be used to indicate one or more of: a time window for monitoring the throughput of the data pipeline; the second network element determining the throughput of the second network element; the second network element determining the throughput of the data pipeline; the second network element adding the throughput of the second network element in the sent data; the second network element adding the identification of the data pipeline in the sent data; the second network element adding the iteration round corresponding to the data in the sent data; the second network element sending a threshold of the throughput of the data pipeline to the first network element.

[0198] The second network element can monitor the throughput of the second network element within the time window for monitoring the throughput of the data pipeline. For example, the data source can monitor the throughput of the data source within the time window. Or, the intermediate node can monitor the throughput of the intermediate node within the time window. Or, the data receiver can monitor the throughput of the data receiver within the time window.

[0199] In some embodiments, the second network element can determine whether to send the monitoring result of the throughput of the data pipe to the first network element according to the threshold of the throughput of the data pipe indicated in the monitoring policy. In some embodiments, when the throughput of the data pipe meets the threshold of the throughput of the data pipe indicated in the monitoring policy, the second network element can send the monitoring result of the throughput of the data pipe to the first network element. However, the embodiments of the present application are not limited thereto, for example, the second network element can periodically send the monitoring result of the throughput of the data pipe to the first network element. Alternatively, the second network element can determine whether to send the monitoring result of the throughput of the data pipe to the first network element based on other conditions.

[0200] As an example, in the case that the index includes the throughput of the data pipe, if the second network element is a data source, the monitoring policy can be used to indicate one or more of the following: a time window for monitoring the throughput of the data pipe; the second network element determines the throughput of the second network element; the second network element adds the throughput of the second network element in the data sent; the second network element adds the identification of the data pipe in the data sent; the second network element adds the iteration round corresponding to the data in the data sent; and the second network element sends the threshold of the throughput of the data pipe to the first network element.

[0201] As another example, in the case that the index includes the throughput of the data pipe, if the second network element is an intermediate node, the monitoring policy can be used to indicate one or more of the following: a time window for monitoring the throughput of the data pipe; the second network element determines the throughput of the second network element; the second network element adds the throughput of the second network element in the data sent; the second network element adds the identification of the data pipe in the data sent; the second network element adds the iteration round corresponding to the data in the data sent; and the second network element sends the threshold of the throughput of the data pipe to the first network element.

[0202] In some embodiments, if there are multiple data sources, the intermediate node can respectively count the size of the data sent by different data sources in the monitoring time window, or count the size of the data sent by all data sources, and calculate the throughput of the second network element.

[0203] As yet another example, in the case that the index includes the throughput of the data pipe, if the second network element is a data receiver, the monitoring policy can be used to indicate one or more of the following: a time window for monitoring the throughput of the data pipe; the second network element determines the throughput of the second network element; the second network element determines the throughput of the data pipe; and the second network element sends the threshold of the throughput of the data pipe to the first network element.

[0204] As an implementation manner, the second network element can count the size of the data received in the monitoring time window, and determine the throughput of the second network element based on the counted data.

[0205] The embodiments of the present application do not limit the way in which the second network element determines the throughput of the second network element. For example, the second network element can calculate the throughput of the second network element based on one or more of the following information: the size of the data received within the monitoring time window, the time length of the monitoring time window. As an example, the second network element can calculate the throughput of the second network element based on the formula: Q=N*S / L, where Q is the throughput of the second network element, N is the number of data packets received by the second network element within the monitoring time window, S is the size of one data packet, and L is the time length of the monitoring time window.

[0206] In some embodiments, in the case where the indicator includes the resource consumed by the data pipeline, the monitoring strategy can be used to indicate one or more of the following: the second network element adds the resource consumption result of the second network element in the data sent by the second network element; the second network element determines the resource consumed by the data pipeline; the second network element adds the identification of the data pipeline in the data sent by the second network element; the second network element adds the iteration round corresponding to the data in the data sent by the second network element; and the second network element sends the threshold of the resource consumption result of the second network element to the first network element.

[0207] In some embodiments, the threshold of the resource consumption result can be configured for each node in the data pipeline. In this case, the second network element can determine whether the resource consumed by the second network element exceeds the threshold, and report the resource consumption result in the case where the threshold is exceeded.

[0208] In some embodiments, the threshold of the resource consumption result can be configured for the entire data pipeline. In this case, the second network element can determine whether the cumulative resource consumed by the data transmitted to the second network element exceeds the threshold, and report the resource consumption result in the case where the threshold is exceeded.

[0209] As an example, in the case where the indicator includes the resource consumed by the data pipeline, if the second network element is a data source, the monitoring strategy can be used to indicate one or more of the following: the second network element adds the resource consumption result of the second network element in the data sent by the second network element; the second network element adds the identification of the data pipeline in the data sent by the second network element; the second network element adds the iteration round corresponding to the data in the data sent by the second network element; and the second network element sends the threshold of the resource consumption result of the second network element to the first network element.

[0210] As another example, in the case where the indicator includes the resource consumed by the data pipeline, if the second network element is an intermediate node, the monitoring strategy can be used to indicate one or more of the following: the second network element adds the resource consumption result of the second network element in the data sent by the second network element; the second network element adds the identification of the data pipeline in the data sent by the second network element; the second network element adds the iteration round corresponding to the data in the data sent by the second network element; and the second network element sends the threshold of the resource consumption result of the second network element to the first network element.

[0211] As another example, in a case where the metric includes resource consumed by the data pipeline, if the second network element is a data receiver, the monitoring policy can be used to instruct one or more of the following: the second network element to determine resource consumed by the data pipeline; the second network element to send a threshold of the resource consumption result of the second network element to the first network element. For example, the second network element can receive resource consumption results carried in data by the data source and the intermediate nodes, and determine resource consumed by the data pipeline based on the resource consumption results of the respective nodes (e.g., the resource consumed by the data pipeline is a sum of the resource consumed by the respective nodes).

[0212] In some embodiments, in a case where the metric includes size of data in the data pipeline, the monitoring policy can be used to configure a first threshold. The first threshold can be used to determine whether the size of data in the data pipeline fails to meet a requirement and needs to be fed back to the first network element. In some embodiments, the size of data in the data pipeline failing to meet the requirement can mean that the data is too large, e.g., exceeds the first threshold. In some embodiments, the size of data in the data pipeline failing to meet the requirement can mean that the data is too small, e.g., is below the first threshold.

[0213] In some embodiments, the first network element can configure the first threshold to the respective nodes in the data pipeline.

[0214] In some embodiments, in a case where the metric includes consistency of data in the data pipeline, the monitoring policy can be used to configure a format of data in the data pipeline. For example, the first network element can configure a uniform data format to the respective nodes in the data pipeline, i.e., the data in the data pipeline is transmitted in the uniform format.

[0215] In some embodiments, if a format of data received by some nodes (e.g., the intermediate nodes, the data receiver) is different from a required format of data, the node can report to the first network element.

[0216] In some embodiments, in a case where the metric includes integrity of data in the data pipeline, the monitoring policy can be used to configure a data feature dimension corresponding to the data in the data pipeline.

[0217] In some embodiments, if data sent or collected by some nodes (e.g., the data source, the intermediate nodes, the data receiver) fails to meet the data feature dimension of the data, the node can report to the first network element.

[0218] In some embodiments, in a case where the metric includes bias of data in the data pipeline, the monitoring policy can be used to configure a second threshold. The second threshold can be used to determine whether the bias of data in the data pipeline needs to be fed back to the first network element.

[0219] In some embodiments, the second threshold can be a proportional value. That is, the first network element can configure the second network element with a proportional threshold of the data bias, and the second network element can perform bias calculation on the received or collected data, and if some data feature dimensions in the data exceed the proportional threshold, the second network element can report to the first network element.

[0220] In some embodiments, in a case where the indicator includes an operation performed on the data in the data pipeline, the monitoring policy can be used to instruct the second network element to send one or more of the following information to the first network element: information associated with the operation performed on the data in the data pipeline, reporting frequency.

[0221] The present application embodiments do not limit the information associated with the operation performed on the data in the data pipeline. Exemplarily, the information associated with the operation performed on the data in the data pipeline can include one or more of the following: type of the operation performed, information of the data before the operation, information of the data after the operation, time when the operation occurs.

[0222] The type of the operation performed can include one or more of the following: data collection, data processing, data reception.

[0223] Taking the operation performed on the data in the data pipeline as data collection as an example, the information associated with the operation performed on the data in the data pipeline can include one or more of the following: type of the operation performed is data collection, size of the collected data, data feature dimension corresponding to the collected data, bias condition of the collected data, time of collecting the data, etc.

[0224] Taking the operation performed on the data in the data pipeline as data processing as an example, the information associated with the operation performed on the data in the data pipeline can include one or more of the following: type of the operation performed is data processing, information of the data before the processing (such as size of the data, data feature dimension, bias condition, etc.), information of the data after the processing, time of processing the data, etc. Taking data processing including data compression as an example, the information associated with the operation performed on the data in the data pipeline can include one or more of the following: type of the operation performed is data compression, information of the data before the compression (such as size before compression), information of the data after the compression (such as size after compression), time of data compression, etc.

[0225] Taking the operation performed on the data in the data pipeline as data reception as an example, the information associated with the operation performed on the data in the data pipeline can include one or more of the following: type of the operation performed is data reception, information of the received data (such as size of the data, data feature dimension, bias condition, etc.), time of receiving the data, etc.

[0226] The embodiments of the present application do not limit the reporting frequency. For example, each node can report once after performing an operation on the data in the data pipeline each time. Alternatively, each node can report once after performing a certain number (e.g., multiple) of operations on the data in the data pipeline, so as to save signaling overhead.

[0227] In some embodiments, the second network element can perform a corresponding operation based on the monitoring policy sent by the first network element.

[0228] For example, in the case where the index includes the latency of the data pipeline, if the second network element is a data source, the second network element can add one or more of the following information in the sent data based on the monitoring policy: a timestamp of sending the data, a processing latency of the data, an identifier of the data pipeline, and an iteration round corresponding to the data.

[0229] For example, in the case where the index includes the latency of the data pipeline, if the second network element is a data source, the second network element can add one or more of the following information in the sent data based on the monitoring policy: a timestamp of sending the data, a processing latency of the data, an identifier of the data pipeline, and an iteration round corresponding to the data.

[0230] For example, in the case where the index includes the latency of the data pipeline, if the second network element is a data source, the second network element can add one or more of the following information in the sent data based on the monitoring policy: a timestamp of sending the data, a processing latency of the data, an identifier of the data pipeline, and an iteration round corresponding to the data.

[0231] For example, in the case where the index includes the throughput of the data pipeline, if the second network element is a data source or an intermediate node, the second network element can perform one or more of the following operations based on the monitoring policy: the second network element adds one or more of the following information in the sent data: a throughput of the second network element, an identifier of the data pipeline, and an iteration round corresponding to the data; and the second network element sends the throughput of the second network element to the first network element.

[0232] For example, in the case that the metric includes the throughput of the data pipeline, if the second network element is a data source, the second network element can collect data and process data based on the monitoring policy. For example, the second network element can compress the data, format the data, etc. based on the monitoring policy. Alternatively, the second network element can determine the size of the data, the consistency of the data, the completeness of the data, the bias of the data, etc. based on the monitoring policy.

[0233] For example, in the case that the metric includes the quality-related metric of the data in the data pipeline (such as one or more of the size of the data in the data pipeline, the consistency of the data in the data pipeline, the completeness of the data in the data pipeline, the bias of the data in the data pipeline), if the second network element is a data source, the second network element can collect data and process data based on the monitoring policy. For example, the second network element can compress the data, format the data, etc. based on the monitoring policy. Alternatively, the second network element can determine the size of the data, the consistency of the data, the completeness of the data, the bias of the data, etc. based on the monitoring policy.

[0234] For example, in the case that the metric includes the quality-related metric of the data in the data pipeline, if the second network element is an intermediate node, the second network element can process data based on the monitoring policy. For example, the second network element can determine the size of the data, the consistency of the data, the completeness of the data, the bias of the data, etc. based on the monitoring policy.

[0235] For example, in the case that the metric includes the quality-related metric of the data in the data pipeline, if the second network element is a data sink, the second network element can determine the quality of the data based on the monitoring policy. For example, the second network element can determine the size of the data, the consistency of the data, the completeness of the data, the bias of the data, etc. based on the monitoring policy.

[0236] With continued reference to FIG. 5, in some embodiments, the method shown in FIG. 5 can further include step S520. At step S520, the second network element sends a second message to the first network element. In some embodiments, the second message is a response message to the first message.

[0237] In some embodiments, the second message can include one or more of the following information: the identity of the data pipeline, the monitoring result, the iteration round to which the data in the data pipeline corresponds, the type of the data pipeline participant to which the second network element corresponds.

[0238] The type of the data pipeline participant corresponding to the second network element can include one or more of the following: data source, intermediate node, data receiver. For example, when the second network element reports the throughput of the data pipeline to the first network element, the second network element can indicate the type of the data pipeline participant corresponding to the second network element. Or, when the second network element reports the operation performed on the data in the data pipeline to the first network element, the second network element can indicate the type of the data pipeline participant corresponding to the second network element. Or, when the second network element reports the quality result of the data in the data pipeline to the first network element, the second network element can indicate the type of the data pipeline participant corresponding to the second network element.

[0239] In some embodiments, the monitoring result can include one or more of the following: the latency of the data pipeline, the throughput of the data pipeline, the resource consumption result of the data pipeline, the quality result of the data in the data pipeline, and the information associated with the operation performed on the data in the data pipeline.

[0240] As an example, the monitoring result can include the latency of the data pipeline.

[0241] As another example, the monitoring result can include the throughput of the data pipeline.

[0242] The latency of the data pipeline and the throughput of the data pipeline, as the most basic performance of the data pipeline, need to be accurately monitored. Accurate reporting of the monitoring result of the latency of the data pipeline and the throughput of the data pipeline is conducive to real-time adjustment of the configuration of the data pipeline based on the monitoring result, so that the performance of the data pipeline is more optimal.

[0243] Of course, the monitoring result can also include a combination of one or more of the other monitoring results described above, such as the monitoring result including the quality result of the data in the data pipeline; or the monitoring result including the information associated with the operation performed on the data in the data pipeline; or the monitoring result including the latency of the data pipeline and the quality result of the data in the data pipeline; or the monitoring result including the throughput of the data pipeline and the information associated with the operation performed on the data in the data pipeline, etc. The embodiments of the present application are not limited thereto.

[0244] In some embodiments, the latency of the data pipeline in the monitoring result can be indicated by the segment latency in the latency of the data pipeline. That is, the second network element can indicate the segment latency between adjacent nodes in the monitoring result, so as to determine the latency of the data pipeline based on the segment latency. However, the embodiments of the present application are not limited thereto, for example, the monitoring result can directly indicate the latency of the data pipeline (i.e. the sum of the segment latencies), or the monitoring result can indicate the latency of the data pipeline and the segment latency in the latency of the data pipeline.

[0245] In some embodiments, the throughput of the data pipeline in the monitoring result can be indicated by one or more of the following: the throughput of each node, the throughput of the data receiver, the maximum value in the throughput of each node.

[0246] In some embodiments, the resource consumption result of the data pipeline can include one or more of the following: the total amount of resources consumed by each node (i.e., the sum of the amount of resources consumed by each node individually), the amount of resources consumed by each node individually (i.e., the amount of resources consumed by each node itself).

[0247] In some embodiments, the quality result of the data in the data pipeline can be used to indicate one or more of the following: whether the size of the data in the data pipeline meets the requirements, whether the consistency of the data in the data pipeline meets the requirements, whether the integrity of the data in the data pipeline meets the requirements, and whether the bias of the data in the data pipeline meets the requirements.

[0248] In some embodiments, the first network element requests the second network element to monitor the data pipeline based on a request from the fourth network element. Continuing to refer to FIG. 5, in some embodiments, the method shown in FIG. 5 can include step S530, in which the fourth network element sends a sixth message to the first network element, and the sixth message can be used to request monitoring of the data pipeline.

[0249] The embodiments of the present application do not limit the fourth network element, which may, for example, include one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

[0250] In some embodiments, the sixth message can include one or more of the following: service description information of the first service, the first identifier, and the requested monitoring indicators.

[0251] The embodiments of the present application do not limit the first service, which can be any one or more services. The embodiments of the present application do not limit the service description information of the first service, which may, for example, include one or more of the following: the type of the first service and service flow information (such as IP quintuple) of the first service.

[0252] The embodiments of the present application do not limit the type of the first service. For example, the type of the first service can include one or more of the following: a sensing service, an AI service, a positioning service, and a session service.

[0253] In some embodiments, the first identifier can be used to indicate the data pipe associated with the first service, thus, the first identifier can also be understood or referred to as a service request associated identifier. In some embodiments, when the fourth network element has requested the first network element to establish the corresponding data pipe for the service, the fourth network element can carry the first identifier in the sixth message.

[0254] In some embodiments, the first network element can determine the data pipe to be monitored according to the information carried in the sixth message.

[0255] In some embodiments, after receiving the sixth message, the first network element can perform the foregoing step S510 and step S520 to monitor the data pipe.

[0256] In some embodiments, after receiving the sixth message, the first network element can perform the following step S630 to retrieve the monitoring result from the third network element. For example, the first network element can autonomously trigger the monitoring of the operation performed on the data in the data pipe, in which case, if the first network element receives the request of the fourth network element to monitor the operation performed on the data in the data pipe, the first network element can directly perform the following step S630.

[0257] In some embodiments, the method shown in FIG. 5 can further include step S540. In step S540, the first network element sends a seventh message to the fourth network element. In some embodiments, the seventh message is a response message of the sixth message.

[0258] In some embodiments, the seventh message can include one or more of the following: service description information of the first service, the first identifier, and the monitoring result corresponding to the data pipe associated with the first service.

[0259] As an example, the seventh message can include the service description information of the first service and the monitoring result corresponding to the data pipe associated with the first service.

[0260] As another example, the seventh message can include the first identifier and the monitoring result corresponding to the data pipe associated with the first service.

[0261] As yet another example, the seventh message can include the service description information of the first service, the first identifier, and the monitoring result corresponding to the data pipe associated with the first service.

[0262] For related introduction of the monitoring result, please refer to the foregoing description, which will not be repeated here for brevity.

[0263] In some embodiments, in a case where the indicator comprises an operation performed on the data in the data pipeline, the first network element can further request storage of a monitoring result corresponding to the operation performed on the data in the data pipeline, so as to store all operations performed on the data in the data pipeline. This is because the operations performed on the data in the data pipeline are frequent, and if the fourth network element is fed back every time, a great signaling overhead will be caused. In addition, monitoring and recording all operations performed on the data in the data pipeline is conducive to meeting the demand for data traceability. Therefore, the embodiment of the present application proposes that the first network element can request storage of the monitoring result corresponding to the operation performed on the data in the data pipeline, so that the fourth network element can request the first network element to view the historical monitoring result. This will be introduced below in combination with FIG. 6.

[0264] FIG. 6 is a flow diagram of a method of wireless communication provided by another embodiment of the present application. The method shown in FIG. 6 is introduced from the perspective of interaction between the first network element and the third network element. The related introduction of the first network element can be referred to the foregoing. The third network element can provide a storage and / or retrieval function of data operation, for example. Exemplarily, the third network element can be the network element 1 mentioned above.

[0265] The method shown in FIG. 6 can comprise step S610. This step will be introduced below.

[0266] In step S610, the first network element sends a third message to the third network element. The third message can be used to request storage of the first information.

[0267] In some embodiments, the first information can be used to indicate a monitoring result corresponding to an operation performed on the data in the data pipeline. Exemplarily, the first information can comprise one or more of the following: an identifier of the data pipeline, information associated with the operation performed on the data in the data pipeline, a type of data pipeline participant corresponding to the second network element.

[0268] The embodiment of the present application does not limit the condition under which the first network element requests storage of the first information. In some embodiments, the first network element can request the third network element to store the first information every time the second network element reports the monitoring result corresponding to the operation performed on the data in the data pipeline. In some embodiments, the first network element can request the third network element to store the first information corresponding to the multiple reports of the second network element after receiving the multiple reports of the second network element. In some embodiments, the first network element can periodically request the third network element to store the first information.

[0269] In some embodiments, after receiving the third message sent by the first network element, the third network element can store the first information. The embodiments of the present application do not limit the format of the first information stored by the third network element, and exemplarily, the first information stored by the third network element can include one or more of the following contents: a storage address, an identifier of the data pipe, a storage time, information associated with the operation performed on the data in the data pipe, and a type of the data pipe participant corresponding to the second network element.

[0270] For the convenience of understanding, one example of the format of the first information stored by the third network element is given below in combination with Table 1.

[0271] Table 1

[0272] In some embodiments, the method shown in FIG. 6 can further include step S620. In step S620, the third network element sends a fourth message to the first network element. In some embodiments, the fourth message is a response message of the third message.

[0273] In some embodiments, the fourth message can include the storage address corresponding to the first information, so as to facilitate the first network element to query or retrieve the first information according to the storage address. For example, the fourth message can include a content identifier (CID) corresponding to the first information, so as to identify the storage address of the first information on the third network element.

[0274] In some embodiments, after receiving the storage address corresponding to the first information, the first network element can store the storage address. Exemplarily, the first network element can store the correspondence between the identifier of the data pipe and the storage address, that is, the operations corresponding to the identifier of the data pipe are all stored in the storage address.

[0275] In some embodiments, the method shown in FIG. 6 can further include step S630. In step S630, the first network element sends a fifth message to the third network element. The fifth message can be used to request to retrieve the first information.

[0276] In some embodiments, the fifth message can include one or more of the following information: an identifier of the data pipe, and a storage address corresponding to the first information.

[0277] In some embodiments, the third network element can return the monitoring result corresponding to all the operations performed on the data in the data pipe corresponding to the identifier of the data pipe according to the fifth message.

[0278] In some embodiments, after receiving the monitoring results corresponding to all operations performed on the data in the data pipeline corresponding to the identifier of the data pipeline, the first network element may send the monitoring results corresponding to all operations performed on the data in the data pipeline corresponding to the first service to the fourth network element.

[0279] In some embodiments, the fifth message is sent based on the first network element receiving a request from the fourth network element. For example, when the fourth network element requests the first network element to monitor the operations performed on the data in the data pipeline, and the first network element is already monitoring the operations performed on the data in the data pipeline, the first network element can request the third network element to retrieve the first information. However, the embodiments of this application are not limited to this. For example, when the fourth network element requests the first network element to monitor the operations performed on the data in the data pipeline, if the first network element is not monitoring the operations performed on the data in the data pipeline, the first network element can monitor using the method shown in Figure 5 and report the monitoring results to the fourth network element and / or request the third network element to store the first information.

[0280] In some embodiments, the method shown in FIG6 can be used in combination with the method shown in FIG5. For example, in step S520 of FIG5, after the second network element sends a second message to the first network element, the first network element can request to store the monitoring results corresponding to the operation performed on the data in the data pipeline based on the method of FIG6.

[0281] For ease of understanding, the following uses different indicators as examples to exemplify the process of the embodiments of this application. It should be noted that the explanations of the terms mentioned in the following embodiments can be found above, and for the sake of brevity, they will not be repeated below.

[0282] Example 1: Monitoring the latency of the data pipeline

[0283] Figure 7 is a schematic flowchart of a wireless communication method according to another embodiment of this application. The method shown in Figure 7 may include steps S701 to S710.

[0284] In step S701, the fourth network element sends a sixth message to the first network element to request monitoring of the performance of the data pipeline corresponding to the first service.

[0285] In some embodiments, the sixth message may include one or more of the following: service description information of the first service, a first identifier, and a metric to be monitored. In Embodiment 1, the metric to be monitored is the latency of the data pipeline.

[0286] In steps S702 to S704, the first network element sends a first message to each node in the data pipeline.

[0287] In some embodiments, the first message comprises one or more of the following information: an identity of the data pipeline, the first indication information, a monitoring strategy.

[0288] In embodiment 1, the first indication information is used to indicate a time delay of requesting monitoring the data pipeline.

[0289] In embodiment 1, the monitoring strategy comprises a monitoring strategy corresponding to the time delay of the data pipeline. For example, the monitoring strategy corresponding to the time delay of the data pipeline can comprise a monitoring strategy corresponding to different nodes (such as a data source, an intermediate node, and a data receiver) in the data pipeline.

[0290] Taking the data source as an example, the monitoring strategy can instruct the data source to add one or more of the following information in the data sent: a timestamp of sending the data, a processing time delay of the data, an identity of the data pipeline, and an iteration round corresponding to the data.

[0291] Taking the intermediate node as an example, the monitoring strategy can instruct one or more of the following: determining a time delay of transmitting the data from the data source to the intermediate node, adding a timestamp of sending the data in the data sent, adding a processing time delay of the data in the data sent, adding an identity of the data pipeline in the data sent, and adding an iteration round corresponding to the data in the data sent.

[0292] Taking the data receiver as an example, the monitoring strategy can instruct one or more of the following: determining a time delay of the data pipeline, and sending a threshold of the time delay of the data pipeline to the first network element.

[0293] In step S705, the data source adds one or more of the following information in the header of the data packet to be sent to the intermediate node: a timestamp of sending the data, a processing time delay of the data, an identity of the data pipeline, and an iteration round corresponding to the data.

[0294] Moreover, the data source can send the data packet with the above information added to the intermediate node.

[0295] In step S706, the intermediate node determines a time delay of transmitting the data to the intermediate node, and processes the data packet. The way in which the intermediate node determines the time delay of transmitting the data to the intermediate node can be referred to the foregoing description.

[0296] In step S707, the intermediate node adds one or more of the following information in the header of the data packet sent: a timestamp of sending the data, a processing time delay (C1) of the data, a time delay (T1) of transmitting the data to the intermediate node, an identity of the data pipeline, and an iteration round corresponding to the data.

[0297] Moreover, the intermediate node can send the data packet with the above information added to the data receiver.

[0298] At step S708, the data receiver determines the latency of the data pipeline.

[0299] As an implementation manner, the data receiver can determine the latency (T2) of the data transmission to the data receiver according to the time of receiving the data packet and the timestamp of the intermediate node sending the data, in which case, the data receiver can determine the latency of the data pipeline as T1+C1+T2.

[0300] In some embodiments, if it is necessary to monitor the latency of multiple rounds of the data pipeline, the data receiver can store the latency of the current round according to the iteration round as Nx: T1+C1+T2, where Nx is the iteration round. When the iteration round that needs to be reported is reached, the data receiver can report the latency of each round respectively, or report the total latency of multiple rounds (i.e., report the sum of the latency of each round).

[0301] At step S709, when the data receiver determines that it is necessary to send the monitoring result to the first network element, the data receiver sends a second message to the first network element.

[0302] In embodiment 1, the second message can include one or more of the following: an identifier of the data pipeline, the monitoring result, and an iteration round corresponding to the data in the data pipeline.

[0303] In embodiment 1, the monitoring result includes the latency of the data pipeline.

[0304] In some embodiments, the data receiver can determine whether it is necessary to send the monitoring result to the first network element according to a threshold configured in the monitoring strategy.

[0305] At step S710, the first network element sends a seventh message to the fourth network element. The seventh message can include one or more of the following: service description information of the first service, the first identifier, and a monitoring result corresponding to the data pipeline associated with the first service.

[0306] The latency of the data pipeline needs to be accurately monitored as the most basic performance of the data pipeline. Considering that the data pipeline can involve multiple data sources, accurate strategy configuration of the latency of the data pipeline is beneficial to realize performance monitoring of the data pipeline with a flexible topology structure.

[0307] For ease of understanding, the processes of steps S705 to S708 are introduced below in combination with FIG. 8. As shown in FIG. 8, after receiving the monitoring policy, the data source 1 and the data source 2 add the sending time stamp, the identification of the data pipe, and the iteration round in the packet header of the data packet to be sent to the intermediate node. For example, the data source 1 adds the sending time stamp t11 in the packet header of the data packet to be sent to the intermediate node; the data source 2 adds the sending time stamp t21 in the packet header of the data packet to be sent to the intermediate node. Then, the intermediate node determines the time delay T1 of the data from the data source to the intermediate node according to the receiving time of the data packet, t11 and t21, and further determines the processing time delay C1 of the data. Then, the intermediate node adds T1, C1 and the time stamp t3 of the sent data packet in the packet header of the data packet to be sent to the data receiver. The data receiver determines the time delay T2 of the data from the intermediate node to the data receiver according to the receiving time t4 of the data packet and the time stamp t3 of the data packet sent by the intermediate node, and can determine the time delay of the data pipe as T1+C1+T2. Of course, if the data source (such as the data source 1 and / or the data source 2) and / or the data receiver also exist the processing of the data, i.e., the processing time delay C2 and / or C3 exist, the processing time delay C2 and / or C3 also need to be considered when determining the time delay of the data pipe.

[0308] It should be noted that the data source 1, the data source 2, and the intermediate node can carry one or more of the identification of the data pipe, the iteration round, and the like in addition to the time-related information (such as the sending time stamp, the processing time delay of the data, and the time delay of the data transmission to the second network element) carried in the packet header, and the embodiments of the present application are not limited thereto.

[0309] Embodiment 2: Monitoring the throughput of the data pipe

[0310] FIG. 9 is a flow diagram of a method of wireless communication provided by another embodiment of the present application. The method shown in FIG. 9 can include steps S901 to S910.

[0311] In step S901, the fourth network element sends a sixth message to the first network element to request monitoring the performance of the data pipe corresponding to the first service.

[0312] In some embodiments, the sixth message can include one or more of the following information: the service description information of the first service, the first identification, and the requested monitoring index. In Embodiment 2, the requested monitoring index is the throughput of the data pipe.

[0313] In steps S902 to S904, the first network element sends a first message to each node in the data pipe.

[0314] In some embodiments, the first message comprises one or more of the following information: an identity of the data pipeline, the first indication information, the monitoring strategy.

[0315] In embodiment 2, the first indication information is used to indicate a request to monitor the throughput of the data pipeline.

[0316] In embodiment 2, the monitoring strategy comprises a monitoring strategy corresponding to the throughput of the data pipeline. For example, the monitoring strategy corresponding to the throughput of the data pipeline can comprise a monitoring strategy corresponding to different nodes (such as a data source, an intermediate node, and a data receiver) in the data pipeline.

[0317] Taking the data source as an example, the monitoring strategy can indicate one or more of the following: a time window for monitoring the throughput of the data pipeline, determining the throughput of the data source, adding the throughput of the data source in the transmitted data, adding the identity of the data pipeline in the transmitted data, adding the iteration round corresponding to the data in the transmitted data, and sending a threshold of the throughput of the data pipeline to the first network element. If the data source sends the monitoring result to the first network element, the type of the participant can be reported as the data source at the same time.

[0318] Taking the intermediate node as an example, the monitoring strategy can indicate one or more of the following: a time window for monitoring the throughput of the data pipeline, determining the throughput of the intermediate node, determining the throughput of the data pipeline, adding the throughput of the intermediate node in the transmitted data, adding the identity of the data pipeline in the transmitted data, adding the iteration round corresponding to the data in the transmitted data, and sending a threshold of the throughput of the data pipeline to the first network element. If the intermediate node sends the monitoring result to the first network element, the type of the participant can be reported as the intermediate node at the same time.

[0319] In some embodiments, the intermediate node can count the size of the data transmitted by different data sources within the monitoring time window and calculate the throughput. That is, the intermediate node can calculate the throughput for different data sources respectively. In some embodiments, the intermediate node can count the size of the data transmitted by all data sources within the monitoring time window and calculate the throughput. That is, the intermediate node can calculate the throughput without distinguishing the data sources.

[0320] Taking the data receiver as an example, the monitoring strategy can indicate one or more of the following: a time window for monitoring the throughput of the data pipeline, determining the throughput of the data receiver, determining the throughput of the data pipeline, and sending a threshold of the latency of the data pipeline to the first network element. The latency of the data pipeline sent by the data receiver to the first network element can comprise one or more of the following: the throughput of each node, the throughput of the data receiver, and the maximum value in the throughput of each node.

[0321] At step S905, the data source adds one or more of the following information in the header of the data packet to be sent to the intermediate node: a time window for monitoring the throughput of the data pipe, the throughput of the data source, the identity of the data pipe, the iteration round to which the data corresponds.

[0322] Also, the data source can send the data packet with the above information added to the intermediate node.

[0323] At step S906, the intermediate node determines the throughput of the intermediate node.

[0324] At step S907, the intermediate node adds one or more of the following information in the header of the data packet to be sent: a time window for monitoring the throughput of the data pipe, the throughput of the intermediate node, the identity of the data pipe, the iteration round to which the data corresponds.

[0325] Also, the intermediate node can send the data packet with the above information added to the data receiver.

[0326] In some embodiments, the intermediate node can report the throughput of the second network element and / or the throughput of the data pipe to the first network element.

[0327] At step S908, the data receiver determines the throughput of the data pipe.

[0328] As an implementation manner, the data receiver can determine the throughput of the data receiver and take the throughput of the data receiver as the throughput of the data pipe.

[0329] As another implementation manner, the data receiver can determine the throughput of the data receiver and take the throughput of each node as the throughput of the data pipe.

[0330] As still another implementation manner, the data receiver can determine the throughput of the data receiver and take the maximum value among the throughput of each node as the throughput of the data pipe.

[0331] At step S909, when the data receiver determines that the monitoring result needs to be sent to the first network element, the data receiver sends a second message to the first network element.

[0332] In embodiment 2, the second message can include one or more of the following: the identity of the data pipe, the monitoring result, the iteration round to which the data in the data pipe corresponds, the type of the data pipe participant.

[0333] In embodiment 2, the monitoring result includes the throughput of the data pipe.

[0334] In some embodiments, the data receiver can determine whether the monitoring result needs to be sent to the first network element according to a threshold configured in the monitoring strategy.

[0335] At step S910, the first network element sends a seventh message to the fourth network element. The seventh message can include one or more of the following: service description information of the first service, the first identifier, and a monitoring result corresponding to the data pipeline associated with the first service.

[0336] The throughput of the data pipeline needs to be accurately monitored as the most basic performance of the data pipeline. Considering that the data pipeline can involve multiple data sources, accurate policy configuration of the throughput of the data pipeline is beneficial to performance monitoring of the data pipeline with a flexible topology.

[0337] Embodiment 3: Monitoring the quality of data in the data pipeline

[0338] FIG. 10 is a flow diagram of a method of wireless communication, according to another embodiment of the present disclosure. The method shown in FIG. 10 can include steps S1001 to S1008.

[0339] At step S1001, the fourth network element sends a sixth message to the first network element to request monitoring of the performance of the data pipeline corresponding to the first service.

[0340] In some embodiments, the sixth message can include one or more of the following information: service description information of the first service, the first identifier, and an index to be monitored. In embodiment 3, the index to be monitored is an index corresponding to the quality of data in the data pipeline, such as one or more of the size of data, the consistency of data, the integrity of data, and the bias of data.

[0341] At steps S1002 to S1004, the first network element sends a first message to each node in the data pipeline.

[0342] In some embodiments, the first message includes one or more of the following information: an identifier of the data pipeline, first indication information, and a monitoring policy.

[0343] In embodiment 3, the first indication information is used to indicate that the quality of data in the data pipeline is requested to be monitored.

[0344] In embodiment 3, the monitoring policy includes a monitoring policy corresponding to the quality of data in the data pipeline. For example, the monitoring policy corresponding to the quality of data in the data pipeline can include a monitoring policy corresponding to different nodes (such as a data source, an intermediate node, and a data receiver) in the data pipeline.

[0345] In embodiment 3, the monitoring policies corresponding to different nodes can be the same.

[0346] In embodiment 3, the monitoring strategy can indicate one or more of the following: the first threshold, a format of the data in the data pipeline, a data feature dimension corresponding to the data in the data pipeline, the second threshold.

[0347] At step S1005a, the data source performs data collection and / or data processing.

[0348] For example, the data source can compress, unify format, etc. the data based on the monitoring strategy. For another example, the data source can determine a size of the data in the data pipeline, a completeness of the data, a bias of the data, etc. so as to report to the first network element when a requirement in the monitoring strategy is not met.

[0349] At step S1005b, the data source sends a second message to the first network element. The second message can include one or more of the following: an identity of the data pipeline, a quality result of the data in the data pipeline, and a type of the data pipeline participant being the data source.

[0350] At step S1006a, the intermediate node performs data reception and / or data processing.

[0351] For example, the intermediate node can determine a size of the data in the data pipeline, a consistency of the data, a completeness of the data, a bias of the data, etc. so as to report to the first network element when a requirement in the monitoring strategy is not met.

[0352] At step S1006b, the intermediate node sends a second message to the first network element. The second message can include one or more of the following: an identity of the data pipeline, a quality result of the data in the data pipeline, and a type of the data pipeline participant being the intermediate node.

[0353] At step S1007a, the data receiver performs data reception and determines a size of the data in the data pipeline, a consistency of the data, a completeness of the data, a bias of the data, etc. so as to report to the first network element when a requirement in the monitoring strategy is not met.

[0354] At step S1007b, the data receiver sends a second message to the first network element. The second message can include one or more of the following: an identity of the data pipeline, a quality result of the data in the data pipeline, and a type of the data pipeline participant being the data receiver.

[0355] At step S1008, the first network element sends a seventh message to the fourth network element. The seventh message can include one or more of the following: service description information of the first service, the first identity, and a monitoring result corresponding to the data pipeline associated with the first service.

[0356] In some embodiments, after receiving the quality result of the data in the data pipe returned by any node, the first network element can send a seventh message to the fourth network element, so as to let the fourth network element determine whether to continue the service.

[0357] The quality of data fundamentally determines the good or bad of a service result. For example, for an AI model training task, the quality of data can fundamentally affect the accuracy, generalization, etc. of the AI model. Therefore, embodiment 3 monitors the quality of data for each node in the data pipe, thereby facilitating guaranteeing that the data has high quality at each link and guaranteeing that the service result is better. If the quality of data is poor at any link, the first network element can feed back to the fourth network element in time, so as to let the fourth network element determine in time whether to continue the service.

[0358] Embodiment 4: Monitoring the operation performed on the data in the data pipe

[0359] Compared with embodiments 1 to 3, the operation performed on the data in the data pipe is more frequent, and therefore, if the operation performed on the data in the data pipe each time is fed back to the fourth network element, it will cause great signaling overhead. In addition, in order to meet the requirement of monitoring and recording all the operations performed on the data in the data pipe, thereby meeting the requirement of data traceability, each operation needs to be stored. In this case, the fourth network element can request the first network element to view the historical operation performed on the data in the data pipe.

[0360] FIG. 11 is a flow diagram of a method of wireless communication provided by another embodiment of the present application. The method shown in FIG. 11 can include steps S1101 to S1114.

[0361] In steps S1101 to S1103, the first network element sends a first message to each node in the data pipe.

[0362] In some embodiments, the first message includes one or more of the following information: an identifier of the data pipe, first indication information, a monitoring strategy.

[0363] In embodiment 4, the first indication information is used to indicate the request for monitoring the operation performed on the data in the data pipe.

[0364] In embodiment 4, the monitoring strategy includes a monitoring strategy corresponding to the operation performed on the data in the data pipe. For example, the monitoring strategy corresponding to the operation performed on the data in the data pipe can include a monitoring strategy corresponding to different nodes (such as a data source, an intermediate node, and a data receiver) in the data pipe.

[0365] In embodiment 4, the monitoring strategies corresponding to different nodes can be the same.

[0366] In embodiment 4, the monitoring strategy can instruct the second network element to send one or more of the following to the first network element: information associated with the operation performed on the data in the data pipe, reporting frequency. The related description of the information associated with the operation performed on the data in the data pipe can be referred to the foregoing.

[0367] In step S1104 to step S1106, each node in the data pipe sends a second message to the first network element. The second message can include one or more of the following: the identifier of the data pipe, the information associated with the operation performed on the data in the data pipe, the type of the data pipe participant.

[0368] In step S1107, the first network element sends a third message to the third network element. The third message is used to request storing the first information.

[0369] As an implementation manner, the first network element can request the third network element to store the corresponding first information after receiving the second message sent by one node each time. As another implementation manner, the first network element can request the third network element to uniformly store the first information after receiving multiple second messages.

[0370] In step S1108 to step S1109, the third network element stores the first information and sends a fourth message to the first network element. The fourth message includes the storage address corresponding to the first information.

[0371] In step S1110, the first network element stores the correspondence between the identifier of the data pipe and the storage address.

[0372] In step S1111, the fourth network element sends a sixth message to the first network element to request monitoring the performance of the data pipe corresponding to the first service.

[0373] In some embodiments, the sixth message can include one or more of the following information: the service description information of the first service, the first identifier, the requested monitoring index. In embodiment 3, the requested monitoring index is the operation performed on the data in the data pipe.

[0374] In step S1112, the first network element sends a fifth message to the third network element. The fifth message is used to request retrieving the first information.

[0375] For example, the first network element can determine the identifier of the data pipe according to the service description information of the first service and / or the first identifier, and determine the storage address corresponding to the first information according to the identifier of the data pipe. Then, the first network element can send the fifth message to the third network element, and the fifth message can carry the identifier of the data pipe and / or the storage address corresponding to the first information.

[0376] At step S1113, the third network element sends, to the first network element, information associated with all operations performed on data in the data pipe corresponding to the identification of the data pipe.

[0377] At step S1114, the first network element sends, to the fourth network element, a seventh message. The seventh message can include information associated with all operations performed on data in the data pipe corresponding to the first service.

[0378] The method embodiments of the present application are described in detail above in combination with FIG. 1 to FIG. 11, and the device embodiments of the present application are described in detail below in combination with FIG. 12 to FIG. 16. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and thus, the parts not described in detail can be referred to the foregoing method embodiments.

[0379] FIG. 12 is a structural schematic diagram of a communication device according to an embodiment of the present application. The communication device 1200 shown in FIG. 12 can be any of the first network elements described above. The communication device 1200 includes a first sending module 1210. The first sending module 1210 can be configured to send, to a second network element, a first message used to request monitoring of a data pipe; wherein the data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0380] In some embodiments, the first message requests monitoring of one or more of the following indexes: pipe performance of the data pipe; quality of data in the data pipe; and operation performed on data in the data pipe.

[0381] In some embodiments, the first message is used to request monitoring of one or more of the following indexes: latency of the data pipe; throughput of the data pipe; resource consumed by the data pipe; size of data in the data pipe; consistency of data in the data pipe; integrity of data in the data pipe; bias of data in the data pipe; and operation performed on data in the data pipe.

[0382] In some embodiments, the latency of the data pipe includes a latency experienced by data in the data pipe from collection to reception by a data receiver.

[0383] In some embodiments, the throughput of the data pipe includes one or more of the following: throughput of each node in the data pipe, throughput of a data receiver in the data pipe, and maximum value of the throughput of each node in the data pipe.

[0384] In some embodiments, the first message comprises one or more of the following information: an identity of the data pipeline; first indication information for indicating a requested monitored indicator and / or for indicating monitoring of the indicator; a monitoring strategy.

[0385] In some embodiments, the first message requests a monitored indicator comprising a latency of the data pipeline, and the monitoring strategy is for indicating one or more of: the second network element adding a time stamp of transmitted data in the transmitted data; the second network element determining a latency of data transmission in the data pipeline to the second network element; the second network element adding a processing latency of data in the transmitted data; the second network element determining the latency of the data pipeline; the second network element adding an identity of the data pipeline in the transmitted data; the second network element adding an iteration round corresponding to data in the transmitted data; and the second network element sending a threshold of the latency of the data pipeline to the first network element.

[0386] In some embodiments, the first message requests a monitored indicator comprising a throughput of the data pipeline, and the monitoring strategy is for indicating one or more of: a time window for monitoring the throughput of the data pipeline; the second network element determining a throughput of the second network element; the second network element determining the throughput of the data pipeline; the second network element adding the throughput of the second network element in the transmitted data; the second network element adding an identity of the data pipeline in the transmitted data; the second network element adding an iteration round corresponding to data in the transmitted data; and the second network element sending a threshold of the throughput of the data pipeline to the first network element.

[0387] In some embodiments, the first message requests a monitored indicator comprising a resource consumed by the data pipeline, and the monitoring strategy is for indicating one or more of: the second network element adding a resource consumption result of the second network element in the transmitted data; the second network element determining the resource consumed by the data pipeline; the second network element adding an identity of the data pipeline in the transmitted data; the second network element adding an iteration round corresponding to data in the transmitted data; and the second network element sending a threshold of the resource consumption result of the second network element to the first network element.

[0388] In some embodiments, the first message requests a monitored indicator comprising a size of data in the data pipeline, and the monitoring strategy is for configuring a first threshold for determining whether the size of data in the data pipeline does not meet a requirement and needs to be fed back to the first network element.

[0389] In some embodiments, the first message requests a monitored indicator comprising a consistency of data in the data pipeline, and the monitoring strategy is for configuring a format of the data in the data pipeline.

[0390] In some embodiments, the first message requests a monitored metric comprising integrity of data in the data pipeline, and the monitoring strategy is configured to configure a data feature dimension corresponding to the data in the data pipeline.

[0391] In some embodiments, the first message requests a monitored metric comprising bias of data in the data pipeline, and the monitoring strategy is configured to configure a second threshold for determining whether the bias of data in the data pipeline needs to be fed back to the first network element.

[0392] In some embodiments, the first message requests a monitored metric comprising an operation performed on data in the data pipeline, and the monitoring strategy is configured to instruct the second network element to send one or more of the following information to the first network element: information associated with the operation performed on data in the data pipeline; reporting frequency.

[0393] In some embodiments, the communication device further comprises a first receiving module 1220 configured to receive a second message sent by the second network element, the second message comprising one or more of the following information: an identifier of the data pipeline; a monitoring result; an iteration round corresponding to data in the data pipeline; a type of a data pipeline participant corresponding to the second network element.

[0394] In some embodiments, the monitoring result comprises one or more of the following: a latency of the data pipeline; a throughput of the data pipeline; a resource consumption result of the data pipeline; a quality result of data in the data pipeline; information associated with an operation performed on data in the data pipeline.

[0395] In some embodiments, the latency of the data pipeline is indicated by a segmented latency in the latency of the data pipeline.

[0396] In some embodiments, the resource consumption result of the data pipeline comprises one or more of the following: a total amount of resources consumed by each node in the data pipeline; an amount of resources consumed by each node in the data pipeline individually.

[0397] In some embodiments, the quality result of data in the data pipeline is configured to indicate one or more of the following: whether a size of data in the data pipeline meets a requirement, whether a consistency of data in the data pipeline meets a requirement, whether an integrity of data in the data pipeline meets a requirement, and whether a bias of data in the data pipeline meets a requirement.

[0398] In some embodiments, the information associated with the operation performed on the data in the data pipeline comprises one or more of: a type of the operation performed, information of the data before the operation, information of the data after the operation, a time when the operation occurs.

[0399] In some embodiments, the first message requests monitoring of an operation performed on the data in the data pipeline, and the communication device further comprises a second sending module configured to send a third message to a third network element, the third message being used to request storage of first information, the first information being used to indicate a monitoring result corresponding to the operation performed on the data in the data pipeline, wherein the third network element is configured to provide storage and retrieval of the data operation.

[0400] In some embodiments, the first information comprises one or more of: an identifier of the data pipeline, information associated with the operation performed on the data in the data pipeline, a type of a data pipeline participant corresponding to the second network element.

[0401] In some embodiments, the communication device further comprises a second receiving module configured to receive a fourth message sent by the third network element, the fourth message comprising a storage address corresponding to the first information.

[0402] In some embodiments, the communication device further comprises a storage module configured to store a correspondence between the identifier of the data pipeline and the storage address.

[0403] In some embodiments, the communication device further comprises a third sending module configured to send a fifth message to the third network element, the fifth message being used to request retrieval of the first information.

[0404] In some embodiments, the fifth message comprises one or more of the following information: the identifier of the data pipeline, the storage address corresponding to the first information.

[0405] In some embodiments, the communication device further comprises a third receiving module configured to receive a sixth message sent by a fourth network element, the sixth message being used to request monitoring of the data pipeline.

[0406] In some embodiments, the sixth message comprises one or more of the following information: service description information of a first service; a first identifier, the first identifier being used to indicate a data pipeline associated with the first service; and an indicator requested to be monitored.

[0407] In some embodiments, the communication device further includes a fourth sending module configured to send a seventh message to the fourth network element, the seventh message including one or more of the following: service description information of the first service, the first identifier, and a monitoring result corresponding to a data pipe associated with the first service.

[0408] In some embodiments, the fourth network element includes one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

[0409] In some embodiments, the second network element includes one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

[0410] In some embodiments, the first sending module 1210 can be a transceiver 1630. The communication device 1200 can further include a processor 1610 and a memory 1620, as shown in FIG. 16.

[0411] FIG. 13 is a structural schematic diagram of a communication device according to another embodiment of the present application. The communication device 1300 shown in FIG. 13 can be any of the second network elements described above. The communication device 1300 can include a receiving module 1310. The receiving module 1310 can be configured to receive a first message sent by a first network element, the first message being used to request monitoring of a data pipe, wherein the data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0412] In some embodiments, the first message requests monitoring of an index associated with one or more of the following: a pipe performance of the data pipe; a quality of data in the data pipe; and an operation performed on data in the data pipe.

[0413] In some embodiments, the first message is used to request monitoring of one or more of the following indexes: a latency of the data pipe; a throughput of the data pipe; a resource consumed by the data pipe; a size of data in the data pipe; a consistency of data in the data pipe; an integrity of data in the data pipe; a bias condition of data in the data pipe; and an operation performed on data in the data pipe.

[0414] In some embodiments, the latency of the data pipe includes a latency experienced by data in the data pipe from being collected to being received by a data receiver.

[0415] In some embodiments, the throughput of the data pipeline comprises one or more of: a throughput of each node in the data pipeline, a throughput of a data receiver in the data pipeline, a maximum value of the throughput of each node in the data pipeline.

[0416] In some embodiments, the first message comprises one or more of: an identification of the data pipeline; first indication information for indicating a requested monitored indicator and / or for indicating monitoring of the indicator; a monitoring strategy.

[0417] In some embodiments, the requested monitored indicator comprises a latency of the data pipeline, and the monitoring strategy is for indicating one or more of: the second network element adding a time stamp of transmitted data in the transmitted data; the second network element determining a latency of data transmission in the data pipeline to the second network element; the second network element adding a processing latency of data in the transmitted data; the second network element determining the latency of the data pipeline; the second network element adding an identification of the data pipeline in the transmitted data; the second network element adding an iteration round corresponding to the data in the transmitted data; and the second network element sending a threshold of the latency of the data pipeline to the first network element.

[0418] In some embodiments, if the second network element is a data source in the data pipeline, the communication device further comprises a first processing module 1320 for adding one or more of the following information in the transmitted data: a time stamp of transmitted data, a processing latency of data, an identification of the data pipeline, and an iteration round corresponding to the data.

[0419] In some embodiments, if the second network element is an intermediate node in the data pipeline, the communication device further comprises a second processing module for: determining a latency of data transmission in the data pipeline to the second network element; and adding one or more of the following information in the transmitted data: the latency of data transmission in the data pipeline from a data source to the second network element, a time stamp of transmitted data, a processing latency of data, an identification of the data pipeline, and an iteration round corresponding to the data.

[0420] In some embodiments, if the second network element is a data receiver in the data pipeline, the communication device further comprises: a determining module for determining a latency of the data pipeline; and / or a first sending module for sending the latency of the data pipeline to the first network element.

[0421] In some embodiments, the first message requests a monitored metric comprising a throughput of the data pipeline, and the monitoring strategy is configured to indicate one or more of: a time window for monitoring the throughput of the data pipeline; the second network element determining the throughput of the second network element; the second network element determining the throughput of the data pipeline; the second network element adding the throughput of the second network element in transmitted data; the second network element adding an identification of the data pipeline in transmitted data; the second network element adding an iteration round corresponding to data in transmitted data; and the second network element sending a threshold of the throughput of the data pipeline to the first network element.

[0422] In some embodiments, if the second network element is a data source or an intermediate node in the data pipeline, the communication device further comprises: a third processing module configured to add one or more of the following information in transmitted data: the throughput of the second network element, an identification of the data pipeline, and an iteration round corresponding to data; and / or a second sending module configured to send the throughput of the second network element to the first network element.

[0423] In some embodiments, if the second network element is a data sink in the data pipeline, the communication device further comprises: a third sending module configured to send the throughput of the data pipeline to the first network element.

[0424] In some embodiments, the first message requests a monitored metric comprising a resource consumed by the data pipeline, and the monitoring strategy is configured to indicate one or more of: the second network element adding a resource consumption result of the second network element in transmitted data; the second network element determining a resource consumed by the data pipeline; the second network element adding an identification of the data pipeline in transmitted data; the second network element adding an iteration round corresponding to data in transmitted data; and the second network element sending a threshold of the resource consumption result of the second network element to the first network element.

[0425] In some embodiments, the first message requests a monitored metric comprising a size of data in the data pipeline, and the monitoring strategy is configured to configure a first threshold for determining whether the size of data in the data pipeline does not meet a requirement and needs to be fed back to the first network element.

[0426] In some embodiments, the first message requests a monitored metric comprising a consistency of data in the data pipeline, and the monitoring strategy is configured to configure a format of data in the data pipeline.

[0427] In some embodiments, the first message requests a monitored metric comprising an integrity of data in the data pipeline, and the monitoring strategy is configured to configure a data feature dimension corresponding to data in the data pipeline.

[0428] In some embodiments, the first message requests a monitored index comprising bias of data in the data pipeline, and the monitoring strategy is configured to configure a second threshold for determining whether the bias of data in the data pipeline needs to be fed back to the first network element.

[0429] In some embodiments, the first message requests a monitored index comprising an operation performed on data in the data pipeline, and the monitoring strategy is configured to instruct the second network element to send one or more of the following information to the first network element: information associated with the operation performed on data in the data pipeline; reporting frequency.

[0430] In some embodiments, the communication device further comprises a fourth sending module configured to send a second message to the first network element, the second message comprising one or more of the following information: an identifier of the data pipeline; a monitoring result; an iteration round corresponding to data in the data pipeline; a type of a data pipeline participant corresponding to the second network element.

[0431] In some embodiments, the monitoring result comprises one or more of the following: latency of the data pipeline; throughput of the data pipeline; resource consumption result of the data pipeline; quality result of data in the data pipeline; information associated with an operation performed on data in the data pipeline.

[0432] In some embodiments, the latency of the data pipeline is indicated by a segmented latency in the latency of the data pipeline.

[0433] In some embodiments, the resource consumption result of the data pipeline comprises one or more of the following: total resource amount consumed by each node in the data pipeline; resource amount consumed by each node in the data pipeline individually.

[0434] In some embodiments, the quality result of data in the data pipeline is configured to indicate one or more of the following: whether a size of data in the data pipeline meets a requirement, whether consistency of data in the data pipeline meets a requirement, whether integrity of data in the data pipeline meets a requirement, whether bias of data in the data pipeline meets a requirement.

[0435] In some embodiments, the information associated with the operation performed on data in the data pipeline comprises one or more of the following: type of the operation performed, information of data before the operation, information of data after the operation, time when the operation occurs.

[0436] In some embodiments, the second network element comprises one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, an application device.

[0437] In some embodiments, the receiving module 1310 can be a transceiver 1630. The communication device 1300 can further include a processor 1610 and a memory 1620, as shown in FIG. 16.

[0438] FIG. 14 is a structural diagram of a communication device according to another embodiment of the present application. The communication device 1400 shown in FIG. 14 can be any of the third network elements described above. The communication device 1400 can include a first receiving module 1410. The first receiving module 1410 can be configured to receive a third message sent by a first network element, the third message being used to request storage of first information, the first information being used to indicate a monitoring result corresponding to an operation performed on data in a data pipe, wherein the data pipe is used to provide a data service, the first network element is used for access authentication and / or access control of the data service, and the third network element is used to provide storage and retrieval functions of the data operation.

[0439] In some embodiments, the first information includes one or more of the following: an identifier of the data pipe, information associated with the operation performed on the data in the data pipe, and a type of a data pipe participant corresponding to the second network element.

[0440] In some embodiments, the communication device further includes a sending module 1420 configured to send a fourth message to the first network element, the fourth message including a storage address corresponding to the first information.

[0441] In some embodiments, the communication device further includes a second receiving module configured to receive a fifth message sent by the first network element, the fifth message being used to request retrieval of the first information.

[0442] In some embodiments, the fifth message includes one or more of the following information: an identifier of the data pipe, and a storage address corresponding to the first information.

[0443] In some embodiments, the information associated with the operation performed on the data in the data pipe includes one or more of the following: a type of the operation performed, information of the data before the operation, information of the data after the operation, and a time when the operation occurred.

[0444] In some embodiments, the first receiving module 1410 can be a transceiver 1630. The communication device 1400 can further include a processor 1610 and a memory 1620, as shown in FIG. 16.

[0445] FIG. 15 is a schematic diagram of a structure of a communication device according to another embodiment of the present application. The communication device 1500 shown in FIG. 15 can be any of the fourth network elements described above. The communication device 1500 can include a sending module 1510. The sending module 1510 can be configured to send a sixth message to a first network element, the sixth message being used to request monitoring of a data pipe, wherein the data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

[0446] In some embodiments, the sixth message includes one or more of the following information: service description information of the first service; a first identifier, the first identifier being used to indicate a data pipe associated with the first service; an indicator of the requested monitoring.

[0447] In some embodiments, the indicator of the requested monitoring is associated with one or more of the following: pipe performance of the data pipe; quality of data in the data pipe; an operation performed on data in the data pipe.

[0448] In some embodiments, the sixth message is used to request monitoring of one or more of the following indicators: latency of the data pipe; throughput of the data pipe; resource consumption of the data pipe; size of data in the data pipe; consistency of data in the data pipe; integrity of data in the data pipe; bias of data in the data pipe; an operation performed on data in the data pipe.

[0449] In some embodiments, the latency of the data pipe includes a latency experienced by data in the data pipe from being collected to being received by a data receiver.

[0450] In some embodiments, the throughput of the data pipe includes one or more of the following: throughput of each node in the data pipe, throughput of a data receiver in the data pipe, a maximum value of the throughput of each node in the data pipe.

[0451] In some embodiments, the communication device further includes a receiving module 1520, configured to receive a seventh message sent by the first network element, the seventh message including one or more of the following: the service description information of the first service, the first identifier, and a monitoring result corresponding to the data pipe associated with the first service.

[0452] In some embodiments, the monitoring result includes one or more of the following: latency of the data pipe; throughput of the data pipe; resource consumption result of the data pipe; quality result of data in the data pipe; information associated with an operation performed on data in the data pipe.

[0453] In some embodiments, the latency of the data pipeline is indicated by a segment latency in the latency of the data pipeline.

[0454] In some embodiments, the resource consumption result of the data pipeline comprises one or more of: a total amount of resources consumed by each node in the data pipeline, an amount of resources consumed by each node in the data pipeline individually.

[0455] In some embodiments, the quality result of the data in the data pipeline is used to indicate one or more of: whether a size of the data in the data pipeline meets a requirement, whether a consistency of the data in the data pipeline meets a requirement, whether an integrity of the data in the data pipeline meets a requirement, whether a bias of the data in the data pipeline meets a requirement.

[0456] In some embodiments, the information associated with the operation performed on the data in the data pipeline comprises one or more of: a type of the operation performed, information of the data before the operation, information of the data after the operation, a time when the operation occurs.

[0457] In some embodiments, the fourth network element comprises one or more of: a terminal device, an access network device, a network element in a core network, a network management device, an application device.

[0458] In some embodiments, the second network element comprises one or more of: a terminal device, an access network device, a network element in a core network, a network management device, an application device.

[0459] In some embodiments, the sending module 1510 can be a transceiver 1630. The communication device 1500 can further include a processor 1610 and a memory 1620, as shown in FIG. 16.

[0460] FIG. 16 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. The dashed line in FIG. 16 indicates that the unit or module is optional. The apparatus 1600 can be used to implement the method described in the above method embodiments. The apparatus 1600 can be a chip, a terminal device or a network device.

[0461] The apparatus 1600 can include one or more processors 1610. The processor 1610 can support the apparatus 1600 to implement the methods described in the foregoing method embodiments. The processor 1610 can be a general processor or a special-purpose processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general processor can be a microprocessor or the processor can also be any conventional processor.

[0462] The apparatus 1600 can also include one or more memories 1620. The memory 1620 stores a program that can be executed by the processor 1610, so that the processor 1610 performs the methods described in the foregoing method embodiments. The memory 1620 can be independent of the processor 1610 or integrated in the processor 1610.

[0463] The apparatus 1600 can also include a transceiver 1630. The processor 1610 can communicate with other devices or chips through the transceiver 1630. For example, the processor 1610 can perform data transceiving with other devices or chips through the transceiver 1630.

[0464] The embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal device or the network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in the various embodiments of the present application.

[0465] The embodiments of the present application also provide a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal device or the network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in the various embodiments of the present application.

[0466] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal device or the network device provided by the embodiments of the present application, and the computer program causes the computer to execute the method performed by the terminal device or the network device in the various embodiments of the present application.

[0467] It should be understood that the terms "system" and "network" can be used interchangeably in this application. In addition, the terms used in this application are only used to explain the specific embodiments of this application, and are not intended to limit this application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of this application and the drawings are used to distinguish different objects, and are not used to describe a specific order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0468] In embodiments of this application, the term "indicate" can be direct indication, or indirect indication, or can represent an associated relationship. For example, A indicates B, which can mean that B can be obtained by A; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have an associated relationship.

[0469] In embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0470] In embodiments of this application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or can represent an associated relationship between the two, or can represent an indication and being indicated, configuration and being configured, etc.

[0471] In embodiments of this application, the term "include" can mean direct inclusion, or indirect inclusion. Alternatively, the term "include" mentioned in embodiments of this application can be replaced by "indicate" or "used to determine". For example, A includes B can be replaced by A indicates B, or A is used to determine B.

[0472] In embodiments of this application, "predefined" or "preconfigured" can be achieved by pre-saving corresponding codes, tables or other means for indicating related information in devices (such as terminal devices and network devices), and this application does not limit the specific implementation manner. For example, predefinition can mean definition in a protocol.

[0473] In embodiments of this application, the "protocol" can refer to a standard protocol in the communication field, which can include LTE protocol, NR protocol and related protocols applied to future communication systems, and this application does not limit this.

[0474] The term "and / or" used in the embodiments of the present application only describes an association relationship of associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this document generally represents an "or" relationship between the front and rear associated objects.

[0475] In various embodiments of the present application, the size of the sequence number of each process described above does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0476] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0477] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiments of the present application.

[0478] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0479] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center and the like integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0480] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising: Comprising: a first network element sending a first message to a second network element, the first message being used to request monitoring of a data pipeline; wherein the data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

2. The method of claim 1, wherein, the indicators requested to be monitored by the first message are associated with one or more of the following: a pipeline performance of the data pipeline; a quality of data in the data pipeline; an operation performed on data in the data pipeline.

3. The method according to claim 1 or 2, characterized in that, the first message is used to request monitoring of one or more of the following indicators: a latency of the data pipeline; a throughput of the data pipeline; a resource consumed by the data pipeline; a size of data in the data pipeline; a consistency of data in the data pipeline; an integrity of data in the data pipeline; a bias of data in the data pipeline; an operation performed on data in the data pipeline.

4. The method of claim 3, wherein, the latency of the data pipeline comprises a latency experienced by data in the data pipeline from being collected to being received by a data receiver.

5. The method according to claim 3 or 4, characterized in that, the throughput of the data pipeline comprises one or more of the following: a throughput of each node in the data pipeline, a throughput of a data receiver in the data pipeline, a maximum value of the throughput of each node in the data pipeline.

6. The method according to any one of claims 1-5, characterized in that, the first message comprises one or more of the following information: an identification of the data pipeline; first indication information used to indicate the indicators requested to be monitored and / or used to indicate monitoring of the indicators; a monitoring strategy.

7. The method of claim 6, wherein, the indicators requested to be monitored by the first message comprise the latency of the data pipeline, and the monitoring strategy is used to indicate one or more of the following: the second network element adding a time stamp of sending data in the sent data; the second network element determining a latency of data transmission in the data pipeline to the second network element; the second network element adding a processing latency of data in the sent data; the second network element determining the latency of the data pipeline; the second network element adding an identification of the data pipeline in the sent data; the second network element adding an iteration round corresponding to data in the sent data; the second network element sending a threshold of the latency of the data pipeline to the first network element.

8. The method according to claim 6 or 7, characterized in that, the indicators requested to be monitored by the first message comprise the throughput of the data pipeline, and the monitoring strategy is used to indicate one or more of the following: a time window for monitoring the throughput of the data pipeline; the second network element determining a throughput of the second network element; the second network element determining the throughput of the data pipeline; the second network element adding the throughput of the second network element in the sent data; the second network element adding an identification of the data pipeline in the sent data; the second network element adding an iteration round corresponding to data in the sent data; the second network element sending a threshold of the throughput of the data pipeline to the first network element.

9. The method according to any one of claims 6-8, characterized in that, the indicators requested to be monitored by the first message comprise a resource consumed by the data pipeline, and the monitoring strategy is used to indicate one or more of the following: the second network element adding a resource consumption result of the second network element in the sent data; the second network element determining a resource consumed by the data pipeline; The second network element adds the identifier of the data pipe into the data sent by the second network element. The second network element adds the iteration round corresponding to the data into the data sent by the second network element. The second network element sends the threshold of the resource consumption result of the second network element to the first network element.

10. The method according to any one of claims 6-9, characterized in that, The first message requests to monitor the size of the data in the data pipe, and the monitoring strategy is used to configure a first threshold, which is used to determine whether the size of the data in the data pipe needs to be fed back to the first network element.

11. The method according to any one of claims 6-10, characterized in that, The first message requests to monitor the consistency of the data in the data pipe, and the monitoring strategy is used to configure the format of the data in the data pipe.

12. The method according to any one of claims 6-11, characterized in that, The first message requests to monitor the integrity of the data in the data pipe, and the monitoring strategy is used to configure the data feature dimension corresponding to the data in the data pipe.

13. The method according to any one of claims 6-12, characterized in that, The first message requests to monitor the bias of the data in the data pipe, and the monitoring strategy is used to configure a second threshold, which is used to determine whether the bias of the data in the data pipe needs to be fed back to the first network element.

14. The method according to any one of claims 6-13, characterized in that, The first message requests to monitor the operation performed on the data in the data pipe, and the monitoring strategy is used to instruct the second network element to send one or more of the following information to the first network element: information associated with the operation performed on the data in the data pipe; reporting frequency.

15. The method of any one of claims 1-14, wherein, The method further comprises: The first network element receives the second message sent by the second network element, and the second message comprises one or more of the following information: the identifier of the data pipe; monitoring result; the iteration round corresponding to the data in the data pipe; the type of the data pipe participant corresponding to the second network element.

16. The method of claim 15, wherein, The monitoring result comprises one or more of the following: the latency of the data pipe; the throughput of the data pipe; the resource consumption result of the data pipe; the quality result of the data in the data pipe; information associated with the operation performed on the data in the data pipe.

17. The method of claim 16, wherein, The latency of the data pipe is indicated by the segment latency in the latency of the data pipe.

18. The method according to claim 16 or 17, characterized in that The resource consumption result of the data pipe comprises one or more of the following: the total resource amount consumed by each node in the data pipe, and the resource amount consumed by each node in the data pipe.

19. The method according to any one of claims 16-18, characterized by, The quality result of the data in the data pipe is used to indicate one or more of the following: whether the size of the data in the data pipe meets the requirement, whether the consistency of the data in the data pipe meets the requirement, whether the integrity of the data in the data pipe meets the requirement, and whether the bias of the data in the data pipe meets the requirement.

20. The method of any one of claims 1-19, wherein, The information associated with the operation performed on the data in the data pipe comprises one or more of the following: the type of the operation, the information of the data before the operation, the information of the data after the operation, and the time when the operation occurs.

21. The method of any one of claims 1-20, wherein, The first message requests to monitor the operation performed on the data in the data pipe, and the method further comprises: The first network element sends a third message to a third network element, the third message being used to request storage of first information, the first information being used to indicate a monitoring result corresponding to an operation performed on data in the data pipeline, wherein the third network element is used to provide storage and retrieval of the data operation.

22. The method of claim 21, wherein, The first information comprises one or more of the following: an identifier of the data pipeline, information associated with the operation performed on data in the data pipeline, a type of data pipeline participant corresponding to the second network element.

23. The method of claim 21 or 22, wherein, The method further comprises: The first network element receives a fourth message sent by the third network element, the fourth message comprising a storage address corresponding to the first information.

24. The method of claim 23, wherein, The method further comprises: The first network element stores a correspondence between the identifier of the data pipeline and the storage address.

25. The method of any one of claims 21-24, wherein, The method further comprises: The first network element sends a fifth message to the third network element, the fifth message being used to request retrieval of the first information.

26. The method of claim 25, wherein, The fifth message comprises one or more of the following information: the identifier of the data pipeline, the storage address corresponding to the first information.

27. The method of any one of claims 1-26, wherein, The method further comprises: The first network element receives a sixth message sent by a fourth network element, the sixth message being used to request monitoring of the data pipeline.

28. The method of claim 27, wherein, The sixth message comprises one or more of the following information: Service description information of a first service; A first identifier, the first identifier being used to indicate a data pipeline associated with the first service; An index requested to be monitored.

29. The method of claim 27 or 28, wherein, The method further comprises: The first network element sends a seventh message to the fourth network element, the seventh message comprising one or more of the following: service description information of the first service, the first identifier, a monitoring result corresponding to the data pipeline associated with the first service.

30. The method of any one of claims 27-29, wherein, The fourth network element comprises one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

31. The method of any one of claims 1-30, wherein, The second network element comprises one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

32. A method of wireless communication, comprising: Comprise: A second network element receives a first message sent by a first network element, the first message being used to request monitoring of a data pipeline; Wherein the data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

33. The method of claim 32, wherein, The index requested to be monitored by the first message is associated with one or more of the following: A pipeline performance of the data pipeline; A quality of data in the data pipeline; An operation performed on data in the data pipeline.

34. The method of claim 32 or 33, wherein, The first message is used to request monitoring of one or more of the following indexes: A latency of the data pipeline; A throughput of the data pipeline; A resource consumed by the data pipeline; A size of data in the data pipeline; A consistency of data in the data pipeline; An integrity of data in the data pipeline; A bias condition of data in the data pipeline; An operation performed on data in the data pipeline.

35. The method of claim 34, wherein, The latency of the data pipeline comprises a latency experienced by data in the data pipeline from being collected to being received by a data receiver.

36. The method of claim 34 or 35, wherein, The throughput of the data pipeline comprises one or more of: a throughput of each node in the data pipeline, a throughput of a data receiver in the data pipeline, a maximum of the throughputs of each node in the data pipeline.

37. The method of any one of claims 32-36, wherein, The first message comprises one or more of the following information: an identity of the data pipeline; first indication information for indicating a monitored indicator and / or for indicating monitoring of the indicator; a monitoring strategy.

38. The method of claim 37, wherein, The monitored indicator comprises a latency of the data pipeline, and the monitoring strategy is used for indicating one or more of: the second network element adding a time stamp of transmitted data in the transmitted data; the second network element determining a latency of data transmission in the data pipeline to the second network element; the second network element adding a processing latency of data in the transmitted data; the second network element determining a latency of the data pipeline; the second network element adding an identity of the data pipeline in the transmitted data; the second network element adding an iteration round corresponding to data in the transmitted data; the second network element sending a threshold of the latency of the data pipeline to the first network element.

39. The method of claim 38, wherein, If the second network element is a data source in the data pipeline, the method further comprises: the second network element adding one or more of the following information in the transmitted data: a time stamp of transmitted data, a processing latency of data, an identity of the data pipeline, an iteration round corresponding to data.

40. The method of claim 38, wherein, If the second network element is an intermediate node in the data pipeline, the method further comprises: the second network element determining a latency of data transmission in the data pipeline to the second network element; the second network element adding one or more of the following information in the transmitted data: a latency of data transmission in the data pipeline from a data source to the second network element, a time stamp of transmitted data, a processing latency of data, an identity of the data pipeline, an iteration round corresponding to data.

41. The method of claim 38, wherein, If the second network element is a data receiver in the data pipeline, the method further comprises: the second network element determining a latency of the data pipeline; and / or the second network element sending the latency of the data pipeline to the first network element.

42. The method of any one of claims 37-41, wherein, The monitored indicator comprises a throughput of the data pipeline, and the monitoring strategy is used for indicating one or more of: a time window for monitoring the throughput of the data pipeline; the second network element determining a throughput of the second network element; the second network element determining a throughput of the data pipeline; the second network element adding the throughput of the second network element in the transmitted data; the second network element adding an identity of the data pipeline in the transmitted data; the second network element adding an iteration round corresponding to data in the transmitted data; the second network element sending a threshold of the throughput of the data pipeline to the first network element.

43. The method of claim 42, wherein, If the second network element is a data source or an intermediate node in the data pipeline, the method further comprises: the second network element adding one or more of the following information in the transmitted data: a throughput of the second network element, an identity of the data pipeline, an iteration round corresponding to data; and / or The second network element sends, to the first network element, a throughput of the second network element.

44. The method of claim 42, wherein, If the second network element is a data receiver in the data pipeline, the method further includes: The second network element sends, to the first network element, a throughput of the data pipeline.

45. The method of any one of claims 37-44, wherein, The first message requests a monitored index including a resource consumed by the data pipeline, and the monitoring strategy is used to indicate one or more of: The second network element adds, in the sent data, a resource consumption result of the second network element; The second network element determines a resource consumed by the data pipeline; The second network element adds, in the sent data, an identification of the data pipeline; The second network element adds, in the sent data, an iteration round corresponding to the data; The second network element sends, to the first network element, a threshold of the resource consumption result of the second network element.

46. The method of any one of claims 37-45, wherein, The first message requests a monitored index including a size of data in the data pipeline, and the monitoring strategy is used to configure a first threshold used to determine whether the size of the data in the data pipeline needs to be fed back to the first network element.

47. The method of any one of claims 37-46, wherein, The first message requests a monitored index including a consistency of data in the data pipeline, and the monitoring strategy is used to configure a format of the data in the data pipeline.

48. The method of any one of claims 37-47, wherein, The first message requests a monitored index including an integrity of data in the data pipeline, and the monitoring strategy is used to configure a data feature dimension corresponding to the data in the data pipeline.

49. The method of any one of claims 37-48, wherein, The first message requests a monitored index including a bias of data in the data pipeline, and the monitoring strategy is used to configure a second threshold used to determine whether the bias of the data in the data pipeline needs to be fed back to the first network element.

50. The method of any one of claims 37-49, wherein, The first message requests a monitored index including an operation performed on data in the data pipeline, and the monitoring strategy is used to indicate that the second network element sends, to the first network element, one or more of: Information associated with the operation performed on the data in the data pipeline; A reporting frequency.

51. The method of any one of claims 32-50, wherein, The method further includes: The second network element sends, to the first network element, a second message including one or more of: An identification of the data pipeline; A monitoring result; An iteration round corresponding to the data in the data pipeline; A type of a data pipeline participant corresponding to the second network element.

52. The method of claim 51, wherein, The monitoring result includes one or more of: A latency of the data pipeline; A throughput of the data pipeline; A resource consumption result of the data pipeline; A quality result of the data in the data pipeline; Information associated with the operation performed on the data in the data pipeline.

53. The method of claim 52, wherein, The latency of the data pipeline is indicated by a segmented latency in the latency of the data pipeline.

54. The method of claim 52 or 53, wherein, The resource consumption result of the data pipeline includes one or more of: a total resource amount consumed by each node in the data pipeline, and a resource amount consumed by each node in the data pipeline individually.

55. The method of any one of claims 52-54, wherein, The quality result of the data in the data pipeline is used to indicate one or more of the following: whether the size of the data in the data pipeline meets the requirements, whether the consistency of the data in the data pipeline meets the requirements, whether the integrity of the data in the data pipeline meets the requirements, and whether the bias of the data in the data pipeline meets the requirements.

56. The method of any one of claims 32-55, wherein, The information associated with the operation performed on the data in the data pipeline includes one or more of the following: the type of the operation performed, the information of the data before the operation, the information of the data after the operation, and the time when the operation occurs.

57. The method of any one of claims 32-56, wherein, The second network element includes one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

58. A method of wireless communication, comprising: The method comprises: The third network element receives a third message sent by the first network element, and the third message is used to request storage of first information, wherein the first information is used to indicate a monitoring result corresponding to an operation performed on data in a data pipeline, the data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

59. The method of claim 58, wherein, The third network element provides a storage and retrieval function of the data operation.

60. The method of claim 58 or 59, wherein, The first information includes one or more of the following: an identifier of the data pipeline, information associated with the operation performed on the data in the data pipeline, and a type of a data pipeline participant corresponding to the second network element. The method further comprises:

61. The method of any one of claims 58-60, wherein, The third network element sends a fourth message to the first network element, and the fourth message includes a storage address corresponding to the first information. The method further comprises:

62. The method of claim 61, wherein, The third network element receives a fifth message sent by the first network element, and the fifth message is used to request retrieval of the first information.

63. The method of any one of claims 58-62, wherein, The fifth message includes one or more of the following information: an identifier of the data pipeline and a storage address corresponding to the first information.

64. A method of wireless communication, comprising: The information associated with the operation performed on the data in the data pipeline includes one or more of the following: the type of the operation performed, the information of the data before the operation, the information of the data after the operation, and the time when the operation occurs. The method comprises: A fourth network element sends a sixth message to a first network element, and the sixth message is used to request monitoring of the data pipeline.

65. The method of claim 64, wherein, The data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service. The sixth message includes one or more of the following information: Service description information of a first service; A first identifier, which is used to indicate a data pipeline associated with the first service; 66. The method of claim 64 or 65, wherein, An index to be monitored. The index to be monitored by the sixth message is associated with one or more of the following: Pipeline performance of the data pipeline; Quality of the data in the data pipeline; 67. The method of any one of claims 64-66, wherein, An operation performed on the data in the data pipeline. The sixth message is used to request monitoring of one or more of the following indexes: Latency of the data pipeline; Throughput of the data pipeline; Resources consumed by the data pipeline; Size of the data in the data pipeline; Consistency of the data in the data pipeline; Integrity of the data in the data pipeline; Bias of the data in the data pipeline; An operation performed on the data in the data pipeline.

68. The method of claim 67, wherein, A latency of the data pipeline includes a latency experienced by the data in the data pipeline from being collected to being received by a data receiver.

69. The method of claim 67 or 68, wherein, A throughput of the data pipeline includes one or more of: a throughput of each node in the data pipeline, a throughput of the data receiver in the data pipeline, a maximum of the throughput of each node in the data pipeline.

70. The method of any one of claims 64-69, wherein, The method further includes: The fourth network element receives a seventh message sent by the first network element, and the seventh message includes one or more of: service description information of the first service, the first identifier, and a monitoring result corresponding to the data pipeline associated with the first service.

71. The method of claim 70, wherein, The monitoring result includes one or more of: A latency of the data pipeline; A throughput of the data pipeline; A resource consumption result of the data pipeline; A quality result of the data in the data pipeline; Information associated with an operation performed on the data in the data pipeline.

72. The method of claim 71, wherein, The latency of the data pipeline is indicated by a segmented latency in the latency of the data pipeline.

73. The method of claim 71 or 72, wherein, The resource consumption result of the data pipeline includes one or more of: a total amount of resources consumed by each node in the data pipeline, and an amount of resource consumed by each node in the data pipeline individually.

74. The method of any one of claims 71-73, wherein, The quality result of the data in the data pipeline is used to indicate one or more of: whether a size of the data in the data pipeline meets a requirement, whether a consistency of the data in the data pipeline meets a requirement, whether an integrity of the data in the data pipeline meets a requirement, and whether a bias condition of the data in the data pipeline meets a requirement.

75. The method of any one of claims 64-74, wherein, The information associated with the operation performed on the data in the data pipeline includes one or more of: a type of the operation, information of the data before the operation, information of the data after the operation, and a time when the operation occurs.

76. The method of any one of claims 64-75, wherein, The fourth network element includes one or more of: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

77. The method of any one of claims 64-76, wherein, The second network element includes one or more of: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

78. A communications device, characterized by The communication device is a first network element, and the communication device includes: A first sending module configured to send a first message to a second network element, the first message being used to request monitoring of a data pipeline; The data pipeline is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

79. The communication device of claim 78, wherein, The first message requests monitoring of one or more of: A pipeline performance of the data pipeline; A quality of the data in the data pipeline; An operation performed on the data in the data pipeline.

80. The communication device of claim 78 or 79, wherein, The first message is used to request monitoring of one or more of: A latency of the data pipeline; A throughput of the data pipeline; A resource consumed by the data pipeline; A size of the data in the data pipeline; A consistency of the data in the data pipeline; An integrity of the data in the data pipeline; A bias condition of the data in the data pipeline; An operation performed on the data in the data pipeline.

81. The communication device of claim 80, wherein, The latency of the data pipeline includes a latency experienced by data in the data pipeline from being collected to being received by a data receiver.

82. The communication device of claim 80 or 81, wherein, The throughput of the data pipeline includes one or more of: a throughput of each node in the data pipeline, a throughput of the data receiver in the data pipeline, a maximum value of the throughput of each node in the data pipeline.

83. The communication device of any of claims 78-82, wherein, The first message includes one or more of: an identity of the data pipeline; first indication information indicating a monitored indicator and / or indicating monitoring of the indicator; a monitoring strategy.

84. The communication device of claim 83, wherein, The monitored indicator requested by the first message includes a latency of the data pipeline, and the monitoring strategy is used to indicate one or more of: the second network element adding a time stamp of sending data in the sent data; the second network element determining a latency of data transmission in the data pipeline to the second network element; the second network element adding a processing latency of data in the sent data; the second network element determining the latency of the data pipeline; the second network element adding an identity of the data pipeline in the sent data; the second network element adding an iteration round corresponding to data in the sent data; the second network element sending a threshold of the latency of the data pipeline to the first network element.

85. The communication device of claim 83 or 84, wherein, The monitored indicator requested by the first message includes a throughput of the data pipeline, and the monitoring strategy is used to indicate one or more of: a time window for monitoring the throughput of the data pipeline; the second network element determining a throughput of the second network element; the second network element determining the throughput of the data pipeline; the second network element adding the throughput of the second network element in the sent data; the second network element adding an identity of the data pipeline in the sent data; the second network element adding an iteration round corresponding to data in the sent data; the second network element sending a threshold of the throughput of the data pipeline to the first network element.

86. The communication device of any of claims 83-85, wherein, The monitored indicator requested by the first message includes a resource consumed by the data pipeline, and the monitoring strategy is used to indicate one or more of: the second network element adding a resource consumption result of the second network element in the sent data; the second network element determining a resource consumed by the data pipeline; the second network element adding an identity of the data pipeline in the sent data; the second network element adding an iteration round corresponding to data in the sent data; the second network element sending a threshold of the resource consumption result of the second network element to the first network element.

87. The communication device of any of claims 83-86, wherein, The monitored indicator requested by the first message includes a size of data in the data pipeline, and the monitoring strategy is used to configure a first threshold used to determine whether the size of data in the data pipeline needs to be fed back to the first network element.

88. The communication device of any of claims 83-87, wherein, The monitored indicator requested by the first message includes a consistency of data in the data pipeline, and the monitoring strategy is used to configure a format of data in the data pipeline.

89. The communication device of any of claims 83-88, wherein, The monitored indicator requested by the first message includes an integrity of data in the data pipeline, and the monitoring strategy is used to configure a data feature dimension corresponding to data in the data pipeline.

90. The communication device of any of claims 83-89, wherein, The first message requests a monitored index including bias of data in the data pipeline, and the monitoring strategy is used to configure a second threshold used to determine whether the bias of data in the data pipeline needs to be fed back to the first network element.

91. The communication device of any of claims 83-90, wherein, The first message requests a monitored index including an operation performed on data in the data pipeline, and the monitoring strategy is used to instruct the second network element to send one or more of the following information to the first network element: information associated with the operation performed on data in the data pipeline; reporting frequency.

92. The communication device of any of claims 78-91, wherein, The communication device further includes: A first receiving module is configured to receive a second message sent by the second network element, and the second message includes one or more of the following information: an identifier of the data pipeline; a monitoring result; an iteration round corresponding to data in the data pipeline; a type of a data pipeline participant corresponding to the second network element.

93. The communication device of claim 92, wherein, The monitoring result includes one or more of the following: a latency of the data pipeline; a throughput of the data pipeline; a resource consumption result of the data pipeline; a quality result of data in the data pipeline; information associated with the operation performed on data in the data pipeline.

94. The communication device of claim 93, wherein, The latency of the data pipeline is indicated by a segmented latency in the latency of the data pipeline.

95. The communication device of claim 93 or 94, wherein, The resource consumption result of the data pipeline includes one or more of the following: a total amount of resources consumed by each node in the data pipeline, and an amount of resources consumed by each node in the data pipeline individually.

96. The communication device of any of claims 93-95, wherein, The quality result of data in the data pipeline is used to indicate one or more of the following: whether a size of data in the data pipeline meets a requirement, whether consistency of data in the data pipeline meets a requirement, whether integrity of data in the data pipeline meets a requirement, and whether bias of data in the data pipeline meets a requirement.

97. The communication device of any of claims 78-96, wherein, The information associated with the operation performed on data in the data pipeline includes one or more of the following: a type of the operation, information of data before the operation, information of data after the operation, and a time when the operation occurs.

98. The communication device of any of claims 78-97, wherein, The first message requests a monitored index including an operation performed on data in the data pipeline, and the communication device further includes: A second sending module is configured to send a third message to a third network element, and the third message is used to request storage of first information used to indicate a monitoring result corresponding to the operation performed on data in the data pipeline, wherein the third network element is used to provide storage and retrieval functions of data operations.

99. The communication device of claim 98, wherein, The first information includes one or more of the following: an identifier of the data pipeline, information associated with the operation performed on data in the data pipeline, and a type of a data pipeline participant corresponding to the second network element.

100. The communication device of claim 98 or 99, wherein, The communication device further includes: A second receiving module is configured to receive a fourth message sent by the third network element, and the fourth message includes a storage address corresponding to the first information.

101. The communication device of claim 100, wherein, The communication device further includes: A storage module is configured to store a correspondence between the identifier of the data pipeline and the storage address.

102. The communication device of any of claims 98-101, wherein, The communication device further includes: The third sending module is configured to send a fifth message to the third network element, where the fifth message is used to request to invoke the first information.

103. The communication device of claim 102, wherein, The fifth message comprises one or more of the following information: an identifier of the data pipe, a storage address corresponding to the first information.

104. The communication device of any of claims 78-103, wherein, The communication device further comprises: The third receiving module is configured to receive a sixth message sent by a fourth network element, where the sixth message is used to request to monitor the data pipe. The sixth message comprises one or more of the following information:

105. The communication device of claim 104, wherein, service description information of a first service; a first identifier, the first identifier being used to indicate a data pipe associated with the first service; an index requested to be monitored. The communication device further comprises:

106. The communication device of claim 104 or 105, wherein, The fourth sending module is configured to send a seventh message to the fourth network element, where the seventh message comprises one or more of the following information: the service description information of the first service, the first identifier, and a monitoring result corresponding to the data pipe associated with the first service. The fourth network element comprises one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

107. The communication device of any of claims 104-106, wherein, The second network element comprises one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

108. The communication device of any of claims 78-107, wherein, The communication device is a second network element, and the communication device comprises:

109. A communications device, characterized by The receiving module is configured to receive a first message sent by a first network element, where the first message is used to request to monitor a data pipe. The data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service. The index requested to be monitored by the first message is associated with one or more of the following:

110. The communication device of claim 109, wherein, pipe performance of the data pipe; quality of data in the data pipe; an operation performed on data in the data pipe. The first message is used to request to monitor one or more of the following indexes:

111. The communication device of claim 109 or 110, wherein, latency of the data pipe; throughput of the data pipe; resources consumed by the data pipe; size of data in the data pipe; consistency of data in the data pipe; integrity of data in the data pipe; bias condition of data in the data pipe; an operation performed on data in the data pipe. The latency of the data pipe comprises a time delay experienced by data in the data pipe from being collected to being received by a data receiver.

112. The communication device of claim 111, wherein, The throughput of the data pipe comprises one or more of the following: throughput of each node in the data pipe, throughput of a data receiver in the data pipe, and a maximum value of the throughput of each node in the data pipe.

113. The communication device of claim 111 or 112, wherein, The first message comprises one or more of the following information:

114. The communication device of any of claims 109-113, wherein, an identifier of the data pipe; first indication information, used to indicate an index requested to be monitored and / or used to indicate monitoring of the index; a monitoring strategy. The index requested to be monitored by the first message comprises the latency of the data pipe, and the monitoring strategy is used to indicate one or more of the following:

115. The communication device of claim 114, wherein, the second network element adds a time stamp of sent data in the sent data; the second network element determines a time delay of data transmission in the data pipe to the second network element; ​ the second network element adds a processing delay of the data in the transmitted data; the second network element determines a delay of the data pipe; the second network element adds an identifier of the data pipe in the transmitted data; the second network element adds an iteration round corresponding to the data in the transmitted data; the second network element sends a threshold of the delay of the data pipe to the first network element.

116. The communication device of claim 115, wherein, If the second network element is a data source in the data pipe, the communication device further comprises: a first processing module, configured to add one or more of the following information in the transmitted data: a timestamp of the transmitted data, a processing delay of the data, an identifier of the data pipe, and an iteration round corresponding to the data.

117. The communication device of claim 115, wherein, If the second network element is an intermediate node in the data pipe, the communication device further comprises a second processing module, configured to: determine a delay of data transmission from a data source to the second network element in the data pipe; add one or more of the following information in the transmitted data: the delay of data transmission from the data source to the second network element in the data pipe, a timestamp of the transmitted data, a processing delay of the data, an identifier of the data pipe, and an iteration round corresponding to the data.

118. The communication device of claim 115, wherein, If the second network element is a data receiver in the data pipe, the communication device further comprises: a determining module, configured to determine a delay of the data pipe; and / or a first sending module, configured to send the delay of the data pipe to the first network element.

119. The communication device of any of claims 114-118, wherein, The first message requests to monitor an index including a throughput of the data pipe, and the monitoring strategy is used to indicate one or more of the following: a time window for monitoring the throughput of the data pipe; the second network element determines a throughput of the second network element; the second network element determines a throughput of the data pipe; the second network element adds the throughput of the second network element in the transmitted data; the second network element adds an identifier of the data pipe in the transmitted data; the second network element adds an iteration round corresponding to the data in the transmitted data; the second network element sends a threshold of the throughput of the data pipe to the first network element.

120. The communication device of claim 119, wherein, If the second network element is a data source or an intermediate node in the data pipe, the communication device further comprises: a third processing module, configured to add one or more of the following information in the transmitted data: the throughput of the second network element, an identifier of the data pipe, and an iteration round corresponding to the data; and / or a second sending module, configured to send the throughput of the second network element to the first network element.

121. The communication device of claim 119, wherein, If the second network element is a data receiver in the data pipe, the communication device further comprises: a third sending module, configured to send the throughput of the data pipe to the first network element.

122. The communication device of any of claims 114-121, wherein, The first message requests to monitor an index including a resource consumed by the data pipe, and the monitoring strategy is used to indicate one or more of the following: the second network element adds a resource consumption result of the second network element in the transmitted data; the second network element determines a resource consumed by the data pipe; the second network element adds an identifier of the data pipe in the transmitted data; the second network element adds an iteration round corresponding to the data in the transmitted data; The second network element sends a threshold of resource consumption result of the second network element to the first network element.

123. The communication device of any of claims 114-122, wherein, The first message requests to monitor an index including a size of data in the data pipeline, and the monitoring strategy is used to configure a first threshold used to determine whether the size of data in the data pipeline needs to be fed back to the first network element.

124. The communication device of any of claims 114-123, wherein, The first message requests to monitor an index including consistency of data in the data pipeline, and the monitoring strategy is used to configure a format of data in the data pipeline.

125. The communication device of any of claims 114-124, wherein, The first message requests to monitor an index including integrity of data in the data pipeline, and the monitoring strategy is used to configure a data feature dimension corresponding to data in the data pipeline.

126. The communication device of any of claims 114-125, wherein, The first message requests to monitor an index including a bias condition of data in the data pipeline, and the monitoring strategy is used to configure a second threshold used to determine whether the bias condition of data in the data pipeline needs to be fed back to the first network element.

127. The communication device of any of claims 114-126, wherein, The first message requests to monitor an index including an operation performed on data in the data pipeline, and the monitoring strategy is used to instruct the second network element to send one or more of the following information to the first network element: information associated with the operation performed on data in the data pipeline; a reporting frequency.

128. The communication device of any of claims 109-127, wherein, The communication device further includes: A fourth sending module is configured to send a second message to the first network element, and the second message includes one or more of the following information: an identifier of the data pipeline; a monitoring result; an iteration round corresponding to data in the data pipeline; a type of a data pipeline participant corresponding to the second network element.

129. The communication device of claim 128, wherein, The monitoring result includes one or more of the following: a latency of the data pipeline; a throughput of the data pipeline; a resource consumption result of the data pipeline; a quality result of data in the data pipeline; information associated with the operation performed on data in the data pipeline.

130. The communication device of claim 129, wherein, The latency of the data pipeline is indicated by a segment latency in the latency of the data pipeline.

131. The communication device of claim 129 or 130, wherein, The resource consumption result of the data pipeline includes one or more of the following: a total resource amount consumed by each node in the data pipeline, and a resource amount consumed by each node in the data pipeline individually.

132. The communication device of any of claims 129-131, wherein, The quality result of data in the data pipeline is used to indicate one or more of the following: whether a size of data in the data pipeline meets a requirement, whether consistency of data in the data pipeline meets a requirement, whether integrity of data in the data pipeline meets a requirement, and whether a bias condition of data in the data pipeline meets a requirement.

133. The communication device of any of claims 109-132, wherein, The information associated with the operation performed on data in the data pipeline includes one or more of the following: a type of the operation, information of data before the operation, information of data after the operation, and a time when the operation occurs.

134. The communication device of any of claims 109-133, wherein, The second network element includes one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

135. A communications device, characterized by The communication device is a third network element, and the communication device includes: The first receiving module is configured to receive a third message sent by a first network element, the third message being used to request storage of first information, the first information being used to indicate a monitoring result corresponding to an operation performed on data in a data pipe, wherein the data pipe is used to provide a data service, the first network element is used for access authentication and / or access control of the data service, and the third network element is used to provide storage and retrieval functions of the data operation.

136. The communication device of claim 135, wherein, The first information includes one or more of the following: an identifier of the data pipe, information associated with the operation performed on the data in the data pipe, and a type of a data pipe participant corresponding to the second network element.

137. The communication device of claim 135 or 136, wherein, The communication device further includes: The sending module is configured to send a fourth message to the first network element, the fourth message including a storage address corresponding to the first information.

138. The communication device of any of claims 135-137, wherein, The communication device further includes: The second receiving module is configured to receive a fifth message sent by the first network element, the fifth message being used to request retrieval of the first information.

139. The communication device of claim 138, wherein, The fifth message includes one or more of the following information: an identifier of the data pipe and a storage address corresponding to the first information.

140. The communication device of any of claims 135-139, wherein, The information associated with the operation performed on the data in the data pipe includes one or more of the following: a type of the operation performed, information of the data before the operation, information of the data after the operation, and a time when the operation occurs.

141. A communications device, characterized by The communication device is a fourth network element, and the communication device includes: The sending module is configured to send a sixth message to a first network element, the sixth message being used to request monitoring of the data pipe. The data pipe is used to provide a data service, and the first network element is used for access authentication and / or access control of the data service.

142. The communication device of claim 141, wherein, The sixth message includes one or more of the following information: Service description information of a first service; A first identifier, the first identifier being used to indicate a data pipe associated with the first service; An index to be monitored.

143. The communication device of claim 141 or 142, wherein, The index to be monitored by the sixth message is associated with one or more of the following: Pipe performance of the data pipe; Quality of data in the data pipe; An operation performed on the data in the data pipe.

144. The communication device of any of claims 141-143, wherein, The sixth message is used to request monitoring of one or more of the following indexes: latency of the data pipe, throughput of the data pipe, resources consumed by the data pipe, size of data in the data pipe, consistency of data in the data pipe, integrity of data in the data pipe, bias condition of data in the data pipe, and the operation performed on the data in the data pipe.

145. The communication device of claim 144, wherein, The latency of the data pipe includes a latency experienced by data in the data pipe from collection to reception by a data receiver.

146. The communication device of claim 144 or 145, wherein, The throughput of the data pipe includes one or more of the following: throughput of each node in the data pipe, throughput of a data receiver in the data pipe, and a maximum value in the throughput of each node in the data pipe.

147. The communication device of any of claims 141-146, wherein, The communication device further includes: The receiving module is configured to receive a seventh message sent by the first network element, the seventh message comprising one or more of the following: service description information of the first service, the first identifier, and monitoring results corresponding to a data pipe associated with the first service.

148. The communication device of claim 147, wherein, The monitoring results comprise one or more of the following: a time delay of the data pipe; a throughput of the data pipe; a resource consumption result of the data pipe; a quality result of data in the data pipe; and information associated with an operation performed on the data in the data pipe.

149. The communication device of claim 148, wherein, The time delay of the data pipe is indicated by a segment time delay in the time delay of the data pipe.

150. The communication device of claim 148 or 149, wherein, The resource consumption result of the data pipe comprises one or more of the following: a total amount of resources consumed by each node in the data pipe and an amount of resources consumed by each node in the data pipe individually.

151. The communication device of any of claims 148-150, wherein, The quality result of data in the data pipe is used to indicate one or more of the following: whether a size of the data in the data pipe meets a requirement, whether a consistency of the data in the data pipe meets a requirement, whether an integrity of the data in the data pipe meets a requirement, and whether a bias of the data in the data pipe meets a requirement.

152. The communication device of any of claims 141-151, wherein, The information associated with the operation performed on the data in the data pipe comprises one or more of the following: a type of the operation, information of the data before the operation, information of the data after the operation, and a time when the operation occurs.

153. The communication device of any of claims 141-152, wherein, The fourth network element comprises one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

154. The communication device of any of claims 141-153, wherein, The second network element comprises one or more of the following: a terminal device, an access network device, a network element in a core network, a network management device, and an application device.

155. A communications device, characterized by A communication device comprising a transceiver, a memory, and a processor, wherein the memory is configured to store a program, and the processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the communication device performs the method in any one of claims 1-31 or 32-57 or 58-63 or 64-77.

156. An apparatus, comprising: A device comprising a processor configured to invoke a program from a memory, so that the device performs the method in any one of claims 1-31 or 32-57 or 58-63 or 64-77.

157. A chip, comprising: A chip comprising a processor configured to invoke a program from a memory, so that a device installed with the chip performs the method in any one of claims 1-31 or 32-57 or 58-63 or 64-77.

158. A computer-readable storage medium, characterized in that, A computer program product comprising a program configured to cause a computer to perform the method in any one of claims 1-31 or 32-57 or 58-63 or 64-77.

159. A computer program product, characterized in that, A computer program product comprising a program configured to cause a computer to perform the method in any one of claims 1-31 or 32-57 or 58-63 or 64-77.

160. A computer program, characterized in that, A computer program product comprising a program configured to cause a computer to perform the method in any one of claims 1-31 or 32-57 or 58-63 or 64-77.

Images