Transmission method and apparatus, first node, second node, and network management node

Abstract

The present application relates to the technical field of communications, and discloses a transmission method and apparatus, a first node, a second node, and a network management node. The transmission method according to an embodiment of the present application comprises: a first node sends a first request message to a second node, wherein the first request message comprises information related to a data service protocol, the data service protocol is a protocol based on a data service model, the information related to the data service protocol comprises information about at least one data service model, and the data service model is used to describe a group of data parameters.

Description

Transmission method, apparatus, first node, second node, and network management node

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411954520.6, filed in China on December 27, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a transmission method, apparatus, first node, second node, and network management node. Background Technology

[0004] The convergence of communication and sensing technologies, along with scenarios involving artificial intelligence (AI) and communications, enables mobile networks to provide sensing, AI, and computing services. These services generate substantial amounts of data, which can be transmitted to core network functions, radio access network nodes, user equipment (UE), or external network functions for use—a process termed data service. However, current technologies often define different data service protocols for different combinations of data sending and receiving nodes. Examples include data service protocols between the UE and the radio access network (RAN), between the UE and the core network (CN), between the RAN and CN, within the CN, and within the RAN. This can easily lead to an excessive number of data service protocols. Summary of the Invention

[0005] This application provides a transmission method, apparatus, first node, second node, and network management node. Since the data service protocol is defined based on the data service model, the data service protocol can support the data service model between different nodes, thereby reducing the number of data service protocols.

[0006] Firstly, a transmission method is provided, the method comprising:

[0007] The first node sends a first request message to the second node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information on at least one data service model, the data service model being used to describe a set of data parameters.

[0008] Secondly, a transmission method is provided, the method comprising:

[0009] The second node receives a first request message from the first node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information about at least one data service model, the data service model being used to describe a set of data parameters.

[0010] Thirdly, a transmission method is provided, the method comprising:

[0011] The network management node performs the first operation;

[0012] The first operation includes at least one of the following:

[0013] Receive data service capability information from the second node;

[0014] Receive a capability request message from the first node, the capability request message being used to request data service capability information of at least one second node;

[0015] The data service capability information includes at least one of the following:

[0016] The first capability indicator is used to indicate whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model;

[0017] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0018] Information on supported data service models.

[0019] Fourthly, a transmission device is provided, the device comprising:

[0020] The sending module is used to send a first request message to the second node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information on at least one data service model, the data service model being used to describe a set of data parameters.

[0021] Fifthly, a transmission device is provided, the device comprising:

[0022] A receiving module is configured to receive a first request message from a first node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information on at least one data service model, the data service model being used to describe a set of data parameters.

[0023] Sixthly, a transmission device is provided, the device comprising:

[0024] The processing module is used to perform the first operation;

[0025] The first operation includes at least one of the following:

[0026] Receive data service capability information from the second node;

[0027] Receive a capability request message from the first node, the capability request message being used to request data service capability information of at least one second node;

[0028] The data service capability information includes at least one of the following:

[0029] The first capability indicator is used to indicate whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model;

[0030] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0031] Information on supported data service models.

[0032] In a seventh aspect, a transmission apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect.

[0033] In an eighth aspect, a first node is provided, the first node including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0034] In a ninth aspect, a first node is provided, including a processor and a communication interface, wherein the communication interface is used to send a first request message to a second node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information of at least one data service model, the data service model being used to describe a set of data parameters.

[0035] In a tenth aspect, a second node is provided, the second node including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0036] Eleventhly, a second node is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first request message from a first node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information of at least one data service model, the data service model being used to describe a set of data parameters.

[0037] In a twelfth aspect, a network management node is provided, the network management node including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third aspect.

[0038] In a thirteenth aspect, a network management node is provided, including a processor and a communication interface, wherein the processor is configured to perform a first operation; wherein the first operation includes at least one of the following:

[0039] Receive data service capability information from the second node;

[0040] Receive a capability request message from the first node, the capability request message being used to request data service capability information of at least one second node;

[0041] The data service capability information includes at least one of the following:

[0042] The first capability indicator is used to indicate whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model;

[0043] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0044] Information on supported data service models.

[0045] In a fourteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0046] In a fifteenth aspect, a wireless communication system is provided, comprising: a first node and a second node, wherein the first node is configured to perform the steps of the method described in the first aspect, and the second node is configured to perform the steps of the method described in the second aspect. Optionally, the wireless communication system further comprises a network management node configured to perform the steps of the method described in the third aspect.

[0047] In a sixteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect.

[0048] In a seventeenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect.

[0049] In this embodiment, the first node sends a first request message to the second node. This first request message includes information related to a data service protocol, which is a data service model-based protocol. The information related to the data service protocol includes information about at least one data service model, which describes a set of data parameters. Because the data service protocol is defined based on a data service model, the same data service protocol can support data service models between different nodes, thereby reducing the number of data service protocols. The first node and the second node exchange information about the data service model, which supports the implementation of data transmission based on the aforementioned data service protocol. Attached Figure Description

[0050] Figure 1a is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0051] Figure 1b is a schematic diagram of the data plane protocol stack between the UE and the RAN in an embodiment of this application;

[0052] Figure 2 is a flowchart of a transmission method provided in an embodiment of this application;

[0053] Figure 3 is a schematic diagram of RTT positioning provided in an embodiment of this application;

[0054] Figure 4 is a flowchart of another transmission method provided in an embodiment of this application;

[0055] Figure 5 is a flowchart of another transmission method provided in an embodiment of this application;

[0056] Figure 6 is a flowchart of another transmission method provided in an embodiment of this application;

[0057] Figure 7 is a flowchart of another transmission method provided in an embodiment of this application;

[0058] Figure 8 is a flowchart of another transmission method provided in an embodiment of this application;

[0059] Figure 9 is a flowchart of another transmission method provided in an embodiment of this application;

[0060] Figure 10 is a structural diagram of a transmission device provided in an embodiment of this application;

[0061] Figure 11 is a structural diagram of another transmission device provided in an embodiment of this application;

[0062] Figure 12 is a structural diagram of another transmission device provided in an embodiment of this application;

[0063] Figure 13 is a structural diagram of the communication device provided in an embodiment of this application;

[0064] Figure 14 is a structural diagram of the terminal provided in an embodiment of this application;

[0065] Figure 15 is a structural diagram of a network-side device provided in an embodiment of this application;

[0066] Figure 16 is a structural diagram of another network-side device provided in an embodiment of this application. Detailed Implementation

[0067] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0068] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0069] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0070] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0071] Figure 1a shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0072] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0073] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0074] For ease of understanding, the following describes some aspects of the embodiments of this application:

[0075] I. Data Services

[0076] The convergence of communication and sensing, along with 6G applications such as Artificial Intelligence (AI) and communication, enables 6G networks to possess capabilities such as sensing services, AI services, and computing services. These services can be further categorized into external services and service networks based on their target audience. Taking sensing as an example, sensing services provided by 6G to external network functions such as application functions are called external sensing services; sensing services provided by 6G to core network functions, radio access network nodes, or UEs are called service networks.

[0077] The aforementioned services will generate a large amount of internal network data. This internal network data is typically transmitted not to external network functions, but rather to core network functions, radio access network nodes, or UEs for use. Therefore, this type of data service is called a service network data service, also known as an internal data service. Regarding network exposure, data generated by 6G networks may also be sent to external network functions such as application functions; this is called an external data service.

[0078] II. Data Surface

[0079] Because sensing / AI data is characterized by large volume, flexible endpoints, and flexible priorities, and because multi-UE data and UE-base station data can have their volume reduced or quality improved through preprocessing at the base station, a data plane can be introduced in 6G networks to collect, transmit, and process the aforementioned internal network data. The data plane is a protocol stack used for data collection and transmission within the mobile network. This data plane protocol stack supports the session / radio bearers required for any data service, potentially including data service protocol stacks between UE and RAN, between UE and Core Network (CN), between RAN and CN, within CN, and within RAN. According to the definition of relevant peers, a protocol stack needs to be defined between each of these pairs of peers. For example, in positioning, when the UE or base station acts as a positioning measurement node, the positioning protocol stack between the UE and LMF is used, as well as the positioning protocol stack between the base station and LMF. Different sending and receiving nodes have different underlying transport protocols depending on whether they involve air interface transmission. For example, the data service protocol stack between the UE and the network (e.g., the radio access network or core network) involves air interface transmission, so its underlying transport protocol in 5G is Radio Resource Control (RRC) / Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) / Media Access Control (MAC) / Physical Layer (PHY) or Service Data Adaptation Protocol (SDAP) / PDCP / RLC / MAC / PHY. On the other hand, the data service protocol stack between the RAN and CN does not involve air interface transmission, so its underlying transport protocol in 5G is Stream Control Transmission Protocol (SCTP) / Internet Protocol (IP) or GPRS Tunneling Protocol User Plane (GTP-U) / User Datagram Protocol (UDP) / IP.

[0080] An example of a data plane protocol stack between a UE and a RAN can be shown in Figure 1b. The data plane consists of core network data plane functions, radio access network data plane functions, and UE data plane functions, providing end-to-end connectivity. The data plane is responsible for data control, including data collection coordination, data collection configuration, and data transmission configuration. The data plane is also responsible for functions such as data acquisition, data transmission, data preprocessing, data privacy and security, data analysis, data storage, and data services.

[0081] III. Perceived Data

[0082] Sensing data is generated by the UE or base station and can also be called sensing measurement data or sensing result. One possible classification method for sensing measurement data is to divide the sensing measurements into the following four categories (this description focuses on the measurement quantities; it can also be divided into three categories or no classification, etc.; the four categories are for illustrative purposes only). Based on the relationship between sensing measurements and sensing services, the third and fourth level measurements below are often also referred to as sensing results. The measurement results of the second level measurements and / or the first level measurements are also referred to as sensing measurement data.

[0083] The first level of measurement (received signal / raw channel information) includes: the complex result of the received signal / channel response, amplitude / phase, I-channel / Q-channel and its operation results (operations include addition, subtraction, multiplication, division, matrix addition, subtraction, multiplication, matrix transpose, trigonometric operations, square root operations, and power operations, as well as threshold detection results and maximum / minimum value extraction results of the above operation results; operations also include Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT), Discrete Fourier Transform (DFT) / Inverse Discrete Fourier Transform (IDFT), Two-Dimensional Fast Fourier Transform (2D-FFT), Three-Dimensional Fast Fourier Transform (3D-FFT), matched filtering, autocorrelation operation, wavelet transform and digital filtering, as well as threshold detection results and maximum / minimum value extraction results of the above operation results).

[0084] The second level of measurement (basic measurement) includes: time delay, Doppler, angle, signal strength, and their multidimensional combination representation;

[0085] The third level of measurement (basic attributes / states) includes: distance, velocity, angle / orientation, radar cross section (RCS), and acceleration;

[0086] The fourth level of measurement (advanced attributes / states) includes: spatial location, target presence, trajectory, action, expression, vital signs, quantity, imaging results, weather, air quality, shape, material, and composition.

[0087] IV. Data Service Nodes

[0088] The aforementioned data service nodes may include data function nodes and data nodes.

[0089] The main services and functions of a data function node may include data service control and / or data processing, etc. For example, the main services and functions of a data function node may include at least one of the following:

[0090] (1) Data privacy and security features: used to support authentication and authorization mechanisms for data access, or data privacy and security processes such as privacy computing.

[0091] (2) Data control function: Used to support data collection coordination, data service configuration (such as data packet size and / or interval for data transmission), data transmission configuration (such as establishing / modifying / releasing data plane transmission channels), or data processing configuration (such as data preprocessing or data analysis configuration). Among these, the core network function or radio access network coordinates data collection according to different data requirements to avoid duplicate data collection by the base station or UE.

[0092] (3) Data transmission function: Used to support the forwarding and transmission of data plane data according to the configuration of data control function. Depending on the peer of the data transmission, data plane transmission includes various data transmission protocols such as UE and RAN, RAN and CN, UE and CN, RAN internal function inter-function or CN internal function inter-function.

[0093] (4) Data Processing Functions: Sensing-related data processing includes sensing data analysis and multimodal data fusion. Data analysis preprocesses and aggregates data, reducing the need for collecting raw data across network nodes. For example, raw data can be collected from data producers based on the needs of data consumers, then summarized, organized, and correlated to output data with specified granularity and time-period requirements. Data fusion allows the base station to fuse sensing measurement data from multiple UEs with its own sensing measurement data to generate multidimensional spectral information.

[0094] (5) Data storage function: Much data in 5G networks is short-term, real-time data that is not persistently stored, such as measurement information reported by terminals assisting in scheduling. However, communication and sensing fusion may require the storage and processing of large amounts of data. For example, for sensing needs such as drone intrusion detection, environmental perception, traffic flow, and weather conditions, base stations or UEs will generate a large amount of sensing data through measurements. In order to support the reuse of sensing measurement data for different sensing use cases, as well as the training of AI models for AI-based sensing processing algorithms, 6G needs to provide a persistent data storage mechanism.

[0095] For example, the aforementioned data function nodes may include radio access network data function nodes, and / or core network data function nodes, etc.

[0096] The primary service and function of a data node is to provide or acquire data. A data node can be a UE, a radio access network, a core network function, or an application function. When a data node is used to provide data, it can also be called a data provider node or data supplier; when a data node is used to acquire data, it can also be called a data consumer node or data consumer.

[0097] The transmission method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0098] Please refer to Figure 2, which is a flowchart of a transmission method provided in an embodiment of this application. The method can be executed by a first node, as shown in Figure 2, and includes the following steps:

[0099] Step 201: The first node sends a first request message to the second node, wherein the first request message includes information related to the data service protocol, the data service protocol is a protocol based on a data service model, and the information related to the data service protocol includes information on at least one data service model, the data service model being used to describe a set of data parameters.

[0100] In this embodiment, the first node can be a core network function, a radio access network, a UE, or an application function, etc. Similarly, the second node can also be a core network function, a radio access network, a UE, or an application function, etc.

[0101] The aforementioned first request message can be any request message related to data services. For example, the aforementioned first request message includes, but is not limited to, data service interface establishment request messages, data collection request messages, or data subscription request messages.

[0102] The aforementioned data service protocol can be used for interaction between data service nodes, which may include data function nodes and data nodes. For example, data function nodes and data nodes can transmit data service-related messages through this data service protocol, or data nodes can transmit data through this data service protocol. It should be noted that the first node and the second node can be either a data function node or a data node, or both the first node and the second node can be data nodes. For example, one of the first node and the second node can be a data provider node and the other a data consumer node.

[0103] The aforementioned data service protocol is based on a Data Service Model (DSM). This can be understood as a data service protocol defined by a DSM, upon which information units of different DSM models can be transmitted. A DSM can describe a set of data parameters, and different DSM models can describe different data parameters. Furthermore, a DSM can be applied to data services between at least one first node and one second node, or it can be applied to data services between one first node and at least one second node, or it can be used for data services between at least one first node and at least one second node. The aforementioned data service model can also be referred to as a service model or a data model, etc.

[0104] For example, taking location data service as an example, related technologies define the LTE Positioning Protocol (LPP) and NR Positioning Protocol A (NRPPa). In this embodiment, a Common Positioning Data Service Model (Positioning_Common_DSM) and a Location Data Service Model (Positioning_DSM) can be defined, both of which are based on the same data service protocol for transmission.

[0105] The general location data service model is applicable to both location data collection between the LMF and the UE, and location data collection between the LMF and the base station. For example, the general location data service model may include at least one of the following:

[0106] Time Difference of Arrival (TDOA): LPP and NRPPa support downlink time difference of arrival (DL-TDOA) and uplink time difference of arrival (UL-TDOA), respectively. The data reported by both is essentially time difference of arrival; the main difference is that downlink data is the time difference of arrival of the UE from multiple TRPs' downlink positioning reference signals (PRS), while uplink data is the time difference of arrival of the UE's uplink positioning reference signals (e.g., sounding reference signals (SRS) used for positioning) measured at different TRPs. Therefore, if the UE or base station is considered as the first node, the data parameter is a universal time difference of arrival.

[0107] Round-trip Time (RTT): In LTE, the Enhanced Cell-ID (E-CID) technology uses RTT for positioning to estimate the distance between the base station and the UE. NR extends this from a single RTT to the RTT of multiple cells and the UE, resulting in Multi-cell Round-trip Time (Multi-cell RTT). The UE's location is estimated by jointly using the RTT measurements between multiple base stations and the UE. As shown in Figure 3, RTT = (t3 - t0) + (t1 - t2). The data reported by both base stations and UEs essentially calculates t0, t1, t2, and t3 in the RTT. Therefore, if the UE or base station is considered as the first node, the data parameter is the common RTT.

[0108] Angle: LPP and NRPPa support downlink angle-of-departure (DL-AOD) and uplink angle-of-departure (UL-AOA) data, respectively. Both are angle-based positioning methods. The principle of angle-based positioning technology is to estimate the UE position using at least two measured angles. The UE or base station can obtain the angle of departure or angle of arrival by measuring the uplink or downlink channel. Therefore, if the UE or base station is taken as the first node, the data parameter is a general angle.

[0109] The location data service model is applicable to data collection between the LMF and the UE. For example, the location data service model may include the UE's location information, wherein the UE's location may be obtained based on the aforementioned time difference of arrival, round-trip time or angle, or the UE's location may be obtained based on the Global Navigation Satellite System (GNSS).

[0110] The information of the aforementioned data service model may include, but is not limited to, at least one of the following: the identification information of the data service model, the version of the data service model, the indication information of the nodes to which the data service model is applicable, and the indication information of the data collection mode of the data service model.

[0111] It is understood that, since the data service protocol in this embodiment is based on the data service model definition, the first node and the second node can exchange information about the data service model, and thus determine the data service model used for the current data service based on the information about the data service model, so as to realize the data transmission of the current data service based on the above data service protocol.

[0112] In this embodiment, the first node sends a first request message to the second node. This first request message includes information related to a data service protocol, which is a data service model-based protocol. The information related to the data service protocol includes information about at least one data service model, which describes a set of data parameters. Because the data service protocol is defined based on a data service model, the same data service protocol can support data service models between different nodes, thereby reducing the number of data service protocols. The first node and the second node exchange information about the data service model, which supports the implementation of data transmission based on the aforementioned data service protocol.

[0113] Optionally, the method further includes:

[0114] The first node receives a first response message from the second node;

[0115] The first response message includes at least one of the following:

[0116] A first instruction is used to indicate whether to accept or reject the first request message;

[0117] Information about the accepted data service model;

[0118] Information regarding the rejected data service model;

[0119] The first reason indicator is used to indicate the reason for rejecting the data service model.

[0120] The aforementioned first response message is a response message to the first request message. For example, if the first request message is a data service interface establishment request message, then the aforementioned first response message can be a data service interface establishment response message; if the first request message is a data collection request message, then the aforementioned first response message can be a data collection response message; if the first request message is a data subscription request message, then the aforementioned first response message can be a data subscription response message.

[0121] The aforementioned first instruction is used to indicate whether to accept or reject the first request message. It can be understood that the aforementioned first instruction is used to indicate whether to accept or reject the content requested by the first request message. For example, if the first request message is a data service interface establishment request message, the aforementioned first instruction is used to indicate whether to accept or reject the data service interface establishment request. If the first request message is a data collection request message, the aforementioned first instruction is used to indicate whether to accept or reject the data collection request.

[0122] The accepted data service model may include at least one data service model. For example, the accepted data service model may be in the form of a list of accepted data service models. Exemplarily, the accepted data service model may include at least a portion of the data service models included in the first request message. For example, if the first request message includes data service model a1, data service model a2, data service model a3, and data service model a4, then the accepted data service model may include at least one of data service models a1, a2, a3, and a4. For instance, the accepted data service model may include data service model a1 and data service model a3.

[0123] The aforementioned rejected data service model may include at least one data service model. For example, the rejected data service model may also be in the form of a list of rejected data service models. For instance, the rejected data service model may include at least a portion of the data service models included in the first request message. For example, if the first request message includes data service model a1, data service model a2, data service model a3, and data service model a4, then the aforementioned rejected data service model may include at least one of data service models a1, a2, a3, and a4, such that the aforementioned rejected data service model may include data service model a2 and data service model a4.

[0124] For example, when there is only one version of a data service model, the list of accepted and rejected data service models can also be indicated by M bits. For instance, each bit from the least significant bit to the most significant bit represents a data service model in the first request message. If a bit is 1, it indicates that the data service model indicated by that bit is accepted; if the bit is 0, it indicates that the data service model indicated by that bit is rejected. M can represent the number of data service models indicated by the first request message. When there are multiple versions of a data service model in the first request message, an optional implementation is to allocate multiple bits from the least significant version to the most significant version. For example, if the first request message contains data service model 1, data service model 2, and data service model 3, and the data service model has versions 1.0 and 2.0, then 4 bits can be used, from the least significant bit to the most significant bit, to correspond to data service model 1, data service model 1.0, data service model 2.0, and data service model 3, respectively.

[0125] It is understandable that the rejected data service model and the accepted data service model are different data service models.

[0126] The first reason mentioned above is used to indicate the reason for rejecting the data service model, such as privacy reasons, lack of support for the data service model, etc.

[0127] For example, if the second node rejects the first request message, the first response message may include at least one of the following: a first indication for indicating rejection of the first request message; and a first reason indication for indicating the reason for rejecting the data service model. If the second node accepts the first request message, the first response message may include at least one of the following: a first indication for indicating acceptance of the first request message; information about the accepted data service model; information about the rejected data service model; and a first reason indication for indicating the reason for rejecting the data service model.

[0128] In this embodiment, the first node receives the first response message from the second node. This allows the first node to know whether the second node accepts the first request message, and if the second node accepts the first request message, to know the rejected data service model and / or accepted data service model, ensuring consistency in understanding between the first node and the second node.

[0129] Optionally, the information of the data service model includes at least one of the following:

[0130] The identification information of the data service model;

[0131] The version of the data service model;

[0132] Node identification information, used to indicate the nodes to which the data service model applies;

[0133] Data collection mode indicator, used to indicate the data collection mode.

[0134] In this embodiment, the identification information of the data service model is used to identify the data service model.

[0135] Optionally, the identification information of the data service model includes at least one of the following: the identifier (ID) of the data service model, and the name of the data service model.

[0136] One optional implementation is to define a data service model ID supported by all data service nodes, which can uniquely identify a data service model. Another optional implementation is that the data service model ID is unique within at least one data service node, and for a data service model ID unique within that data service node, the data service model indicated by that data service model ID can be specified through the data service model definition.

[0137] The data service model definition can be represented by characters, which can also be called the name of the data service model. One example is DSM-Sensing, representing a data service model for sensed data. Alternatively, DSM-SensingforNET and NETforSenging represent data service models for sensed data when using a sense-assisted network and a communication network-assisted sense, respectively. Another example is DSM-AIforNET and DSM-NETforAI, representing data service models when using an AI-assisted network and a network-assisted AI, respectively. Data regarding data service models for AI-assisted networks can be found in the Channel State Information (CSI) feedback, beam management, or location use cases in the relevant protocol TR 38.843, or in relevant protocols TS23.288 and TS28.552. Another example is using DSM-AI-model to interact with AI model data, such as parameters of a known model structure, or a new model and its parameters. Alternatively, another example is defining the data service model based on perception use cases or AI use cases. For instance, using DSM-Sensing-T (where T is short for trajectoryory) to interact with the perception data needed for trajectory tracking perception use cases, or using DSM-AI-CSI to interact with the data needed for AI-based CSI feedback use cases. Another example is defining the data service model based on the data providing node or interface, such as DSM-UE-level-measurement, or DSM-N2 (where N2 represents the interface between the RAN and CN).

[0138] As data service model versions become more diverse, different versions of the same data service model may exist. Therefore, when multiple versions exist, the version of the data service model can be used to indicate this.

[0139] The aforementioned node identification information is used to indicate the nodes to which the data service model applies. For example, the aforementioned node identification information can be used to indicate nodes to which the data service model applies in addition to the first node and the second node. For instance, when the first node is a UE and the second node is a core network data function, if the data service model also applies to other nodes, an optional implementation is that the aforementioned node identification information can be used to indicate base stations (such as 5G base stations (gNB), centralized units (CU), distributed units (DU), etc.) or network management functions or AF, etc.

[0140] In some alternative embodiments, the information of the data service model may include a reuse indication to indicate that the data service model is also applicable to nodes other than the first node and the second node.

[0141] The aforementioned data collection mode indication is used to indicate a data collection mode. For example, the data collection mode indication can be used to indicate the data collection mode applicable to the data service model, i.e., each data service model corresponds to one data collection mode; or, the data collection mode indication can be used to indicate the data collection mode applicable to all data service models included in the first request message, i.e., all data service models included in the first request message correspond to the same data collection mode. When the first request message contains at least two data service models, the data collection mode indication is used to indicate the data collection mode applicable to the at least two data service models. Compared to having one data collection mode indication for each data service model, this can save indication overhead.

[0142] For example, the data collection mode indication in the data service model information of the first request message is used to indicate the data collection mode applicable to the data service model. A data service model can be applicable to one or more data collection modes. For example, N bits can be used, with each bit from the least significant bit to the most significant bit corresponding to a data collection mode. If the bit is 1, it indicates that the data service model is applicable to that data collection mode, where N is a positive integer. The data collection mode indication in the information of the accepted data service model is used to indicate the accepted data collection mode. For example, if data service model 1 in the first request message is applicable to single-end mode, double-end mode, shared mode, and data exchange mode, the second node accepts the data service model for shared mode. The data collection mode indication in the information of the rejected data service model is used to indicate the rejected data collection mode. For example, if data service model 1 in the first request message is applicable to single-end mode, double-end mode, shared mode, and data exchange mode, the second node rejects the data service model for double-end mode, shared mode, and data exchange mode.

[0143] For example, the data collection mode includes at least one of the following: a first mode, a second mode, a third mode, a fourth mode, and a fifth mode. Wherein:

[0144] The first mode can also be called single-end mode, which means that either the network or the UE obtains the required data.

[0145] The second mode can also be called the dual-end mode, which means that both the network and the UE obtain the required content. The required content may be data, QoS guarantee times, priority upgrade times, traffic quota, voice quota, or points, etc.

[0146] The third mode can also be called the sharing mode. In the sharing mode, during a data collection process, the network requests the data collected by the UE from the UE, and the UE also requests the data collected by the network from the network. Finally, during the data collection process, the network sends the data it collects to the UE, and the UE sends the data it collects to the network.

[0147] The fourth mode can also be called the exchange mode, which refers to the network or UE requesting the required data by exchanging its existing data during a data collection process.

[0148] The fifth mode, also known as the reward mode, refers to a data collection process where the network or UE requests required data in exchange for valuable rewards. These rewards can include Quality of Service (QoS) guarantees, priority upgrades, data traffic, voice calls, call charges, or points. A key feature of the fifth mode is that the reward information needs to be maintained after the data collection to ensure that the recipient can use the rewards and realize their value.

[0149] It should be noted that the above data collection modes can be combined into multiple modes, which will not be listed here. For example, the third and fourth modes can be combined into the sixth mode, which is characterized by the network and UE cooperating during a single data collection process without the need for subsequent information maintenance. In addition, the third, fourth, and fifth modes can also serve as sub-modes of the second mode.

[0150] Optionally, the first request message is a data service interface establishment request message, which is used to request the establishment of a data service interface between the first node and the second node;

[0151] The at least one data service model is at least one data service model supported or requested by the first node.

[0152] The aforementioned data service interface can be used to transmit data packets of the aforementioned data service protocol based on the data service model between the first node and the second node.

[0153] The aforementioned at least one data service model is at least one data service model supported or requested by the first node. For example, if the first node is a data node, the aforementioned at least one data service model can be at least one data service model supported by the first node; if the first node is a data function node, the aforementioned at least one data service model can be at least one data service model requested by the first node.

[0154] Optionally, the data service interface establishment request message may further include the identification information of the first node. For example, the identification information of the first node may reuse the control plane ID; for instance, the Cell Radio Network Temporary Identity (C-RNTI) may be used between the UE and the RAN, and the Subscription Permanent Identifier (SUPI) or gNB ID may be used between the UE and the CN. Alternatively, the identification information of the first node may be a newly defined ID for purposes such as data collection.

[0155] Accordingly, the aforementioned first response message can be a data service interface establishment response message. Optionally, when the first node is a data node, the data service interface establishment response message may further include configuration information related to the data service of the first node, which may include at least one of the following: the data collection identifier of the first node, a key used for data collection, etc.

[0156] In this embodiment, the first node triggers the establishment of the data service interface. During the establishment of the data service interface, information about the data service model is exchanged. This can provide support for the implementation of data service models between different nodes through a data service protocol. In turn, it can reduce the binding relationship between the data service protocol and the sending or receiving node, reduce the number of data service protocols, and avoid the duplication of similar content in the protocol.

[0157] Optionally, the first node is a data function node.

[0158] The following describes the scenario where the first node is a data function node.

[0159] Optionally, the method further includes:

[0160] The first node sends a capability request message to the network management node, the capability request message being used to request data service capability information of at least one second node;

[0161] The first node receives a capability response message from the network management node, the capability response message being used to indicate whether to accept or reject the capability request message.

[0162] In this embodiment, the first node can obtain the data service capability information of at least one second node before sending the first request message. This makes it easier for the first node to select a suitable second node to send the first request message based on the data service capability information of at least one second node.

[0163] Optionally, the capability request message includes at least one of the following:

[0164] Identification information of at least one second node;

[0165] Capability information indicator, used to indicate the data service capability information requested;

[0166] A data consumer indicator is used to indicate the data consumer node or data consumer node type to which the data provided by at least one second node is applicable.

[0167] The data consumption node types mentioned above can be reasonably configured according to requirements, such as internal network functions or external network functions (e.g., AF); or core network functions, radio access network, UE, or AF, etc. For example, one bit can be used to indicate whether it is an internal network function or an external network function.

[0168] It should be noted that the at least one second node included in the above capability request message can be at least a portion of the second nodes included in the above capability request message. For example, if the above capability request message includes second node b1, second node b2 and second node b3, then the above capability request message can include at least one of second node b1, second node b2 and second node b3, such as the above capability request message can include second node b1, second node b2 and second node b3, or the above capability request message can include second node b1 and second node b3, etc.

[0169] In this embodiment, the first node sends at least one of the identification information, capability information indication, and data consumer indication of at least one second node to the network management node, which facilitates the network management node to more accurately provide feedback on the information required by the first node.

[0170] Optionally, the capability response message includes data service capability information of at least one second node;

[0171] or,

[0172] The capability response message includes at least one of the following:

[0173] Denial indication is used to indicate a refusal to provide information on the ability to provide data services;

[0174] The second reason indication is used to indicate the reason for refusing to provide data service capability information.

[0175] It should be noted that the at least one second node indicated by the aforementioned capability response message may include part or all of the at least one second node indicated by the aforementioned capability request message.

[0176] In this embodiment, the network management function can feed back data service capability information of at least one second node to the first node, which makes it easier for the first node to select a suitable second node to send a first request message based on the data service capability information of at least one second node. Alternatively, the network management function can feed back at least one of a rejection indication and a second reason indication to the first node, which makes it easier for the first node to make decisions on subsequent actions.

[0177] Optionally, the data service capability information includes at least one of the following:

[0178] A first capability indicator is used to indicate whether the data service protocol is supported;

[0179] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0180] Information on supported data service models.

[0181] The aforementioned first capability indicator is used to indicate whether the data service protocol is supported, that is, to indicate whether the second node supports or does not support the data service protocol.

[0182] The aforementioned first protocol indication is used to indicate the underlying transport protocols supported when the data service protocol is used for transmission, that is, to indicate which underlying transport protocols the second node supports for data service protocol transmission.

[0183] The information on the data service models supported above is also the information on the data service models supported by the second node.

[0184] Optionally, the first request message is a data collection request message;

[0185] The at least one data service model is a data service model requested by the first node to be used between the second node and the third node, wherein the third node is a data consumption node, and the data consumption node is the node that consumes the data parameters to be collected.

[0186] It should be noted that if the consumer node of the requested data parameters is the first node, that is, the second node reports the collected data parameters to the first node, then the third node can be the first node.

[0187] In this embodiment, the first node sends a data collection request message and interacts with the data service model information in the data collection request message. This allows the data service model used for data collection to be determined based on the data service model information, so that the corresponding data service model can be used to complete the data collection. This provides support for the implementation of data service models between different nodes in a data service protocol, thereby reducing the binding relationship between the data service protocol and the sending or receiving node, reducing the number of data service protocols, and avoiding the duplication of similar content in the protocol.

[0188] Optionally, the data collection request message may further include at least one of the following:

[0189] The message type indicates that the message is a data collection message; optionally, it can be further indicated that the message is a data collection request message.

[0190] Data collection type, used to indicate the type of data collection;

[0191] A data collection ID is used to identify data collection. Optionally, this data collection ID can also be used to associate data provided by different second nodes.

[0192] At least one data collection target, which may include cell, UE, sensing target or service type, etc.

[0193] At least one data acquisition method.

[0194] For example, the above data collection types may include at least one of the following:

[0195] Immediate data collection involves collecting data according to the data collection configuration information and reporting it immediately.

[0196] Logged data collection involves collecting and storing data according to data collection configuration information and reporting it when appropriate.

[0197] Raw data collection involves collecting data according to the data collection configuration information and then reporting the raw data.

[0198] Processed data collection involves collecting data according to configuration information, processing the collected data, and then reporting it. One possible processing method includes inputting the collected data into an AI model to obtain inference results before reporting; or performing calculations such as averaging or variance on the collected data before reporting; or removing redundancy or identifiers from the collected data before reporting; or classifying or quantifying the collected data before reporting, for example, mapping the collected physical resource block (PRB) utilization or throughput values ​​related to service load to high, low, or no service before reporting.

[0199] For example, the above-mentioned data collection methods may include at least one of the following:

[0200] Triggered by the first node request, optionally, the triggering based on the first node request can be an explicit indication or an implicit indication. For example, if the first node does not indicate any collection method (such as periodic triggering and event triggering), it means that the collection method is triggered by the first node request, which is a one-shot collection method. In other words, the first node requests data collection once, and the second node sends data to the first node once.

[0201] Periodic triggering includes the following parameters: time interval, the unit of which can be any one of hour, minute, second, millisecond, microsecond, frame, subframe, symbol, and time slot;

[0202] Event triggering includes the following parameters: triggering event, which includes at least one of the following:

[0203] The amount of data meets the first condition, for example, the amount of data is greater than the first threshold value;

[0204] The data quality meets the second condition, for example, the channel ratio of the sensed data is greater than the second threshold value;

[0205] The location of the second node satisfies the third condition, for example, the second node is located in a specified area;

[0206] The second node's environment meets the fourth condition, for example, the second node is located in an environment such as a tunnel, elevator, high-speed rail, or subway.

[0207] The second node's business type meets the fifth condition, such as the second node conducting voice-related services.

[0208] Accordingly, the aforementioned first response message can be a data collection response message, which may also include a message type to indicate that the message is a data collection type message. Optionally, it may further indicate that the message is a data collection response message.

[0209] Optionally, the first request message may further include a first parameter indication, used to indicate the data parameters to be collected;

[0210] And / or,

[0211] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0212] For example, the aforementioned data parameters may include, but are not limited to, time delay, Doppler, angle, signal strength, etc. Optionally, the aforementioned signal strength may include at least one of the following: Reference Signal Receiving Power (RSRP), Reference Signal Received Quality (RSRQ), etc.

[0213] For example, the information of the accepted data parameters may include a fourth parameter indication for indicating the accepted data parameters, such as a list of accepted data parameters; the information of the rejected data parameters may include a third parameter indication for indicating the rejected data parameters, such as a list of rejected data parameters.

[0214] Optionally, the first request message is a data subscription request message, used to request subscription data parameters;

[0215] The at least one data service model is a data service model requested by the first node to be used between the first node and the fourth node, wherein the fourth node is a data providing node, and the data providing node is the node that provides the data parameters to be subscribed.

[0216] It should be noted that when the second node provides the data parameters for the requested subscription to the first node, the fourth node can be the second node; when the data parameters for the requested subscription are provided to the first node by a node other than the second node, the aforementioned fourth node and the second node are different nodes.

[0217] In this embodiment, the first node sends a data subscription request message and interacts with the data service model information in the data subscription request message. This allows the data service model used for data subscription to be determined based on the data service model information, so that the data consumer can use the corresponding data service model to complete the data acquisition. This provides support for the implementation of data service models between different nodes in a data service protocol, thereby reducing the binding relationship between the data service protocol and the sending or receiving node, reducing the number of data service protocols, and avoiding the duplication of similar content in the protocol.

[0218] Optionally, the data subscription request message may also include a message type to indicate that the message is a data subscription message; optionally, it may further indicate that the message is a data subscription request message.

[0219] Accordingly, the aforementioned first response message can be a data subscription response message. Optionally, the data subscription response message may further include a data type to indicate that the message is a data subscription message; optionally, it may further indicate that the message is a data subscription response message.

[0220] Optionally, the first request message further includes a second parameter indication for indicating the data parameters to be subscribed;

[0221] And / or,

[0222] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0223] For example, the information of the accepted data parameters may include a fourth parameter indication for indicating the accepted data parameters, such as a list of accepted data parameters; the information of the rejected data parameters may include a third parameter indication for indicating the rejected data parameters, such as a list of rejected data parameters.

[0224] Optionally, the information in the rejected data parameters includes at least one of the following:

[0225] The third parameter indicates the data parameters rejected by the second node;

[0226] The third reason indicator is used to indicate the reason for rejecting the data parameter.

[0227] The third reason indicated above is used to indicate the reason for rejecting the data parameter, such as privacy reasons, not supporting the collection of the data parameter, etc.

[0228] Optionally, the method further includes:

[0229] The first node receives a data notification message from the second node;

[0230] The data notification message includes at least one of the following:

[0231] The second instruction is used to indicate that the data parameters for the requested subscription have been collected;

[0232] The requested subscription data parameters or the identification information of the fifth node, wherein the fifth node is the node that provides the requested subscription data parameters.

[0233] The identification information of the fifth node mentioned above may include the cell ID or IP address, etc.

[0234] In this embodiment, when the second node provides the data parameters to be subscribed to to the first node, the second node can directly send the collected data parameters to the first node; when the data parameters to be subscribed to to the first node are provided by a node other than the second node (i.e., the fifth node), the second node can send the identification information of the fifth node to the first node, and then the first node can obtain the data parameters to be subscribed to from the fifth node according to the identification information of the fifth node.

[0235] In this embodiment, the second node sends a data notification message to the first node, so that the first node can obtain the requested data parameters in a timely manner.

[0236] Optionally, the first request message may further include first information; or,

[0237] The method further includes: the first node sending first information to the second node;

[0238] The first information includes at least one of the following:

[0239] Protocol mapping rules are used to indicate the rules for mapping data packets of the data service protocol to the underlying transport protocol;

[0240] The second protocol indication is used to indicate the underlying transport protocol used to send the data packets of the data service protocol;

[0241] A reflection indication is used to indicate that the data packets sending the data service protocol and the data packets receiving the data service protocol use the same underlying transport protocol.

[0242] The above protocol mapping rules are used to indicate the rules for mapping data packets of the data service protocol to the underlying transport protocol. For example, a data provider node can use the protocol mapping rules to encapsulate the collected data parameters into data packets of the data service protocol and then map them to the appropriate underlying transport protocol.

[0243] The aforementioned second protocol indication is used to indicate the underlying transport protocol used to send the data packets of the data service protocol. For example, if the aforementioned second protocol indication is used to indicate that the data packets of the data service protocol use a user plane transport protocol, then the data packets of the data service protocol can be mapped to the user plane transport protocol for transmission. Exemplarily, when the first information includes the second protocol indication, the first node may not indicate the aforementioned protocol mapping rule, or the first node's indication of the aforementioned protocol mapping rule may not be effective, or the second node may not use the aforementioned protocol mapping rule.

[0244] The aforementioned reflection indication is used to indicate that the data packets sending the data service protocol and the data packets receiving the data service protocol use the same underlying transport protocol, so that the underlying transport protocol of the data packets receiving the data service protocol can be known based on the underlying transport protocol used to send the data packets.

[0245] It is understood that the data packets of the aforementioned data service protocol include information units of the data service model.

[0246] In this embodiment, the first node indicates information related to the lower-layer transport protocol (i.e., the first information) to the second node, which facilitates the second node in determining the lower-layer transport protocol of the data packets of the data service protocol. Furthermore, this method reduces the binding relationship between the data service protocol and the underlying transport protocol, thereby further reducing the number of data service protocols and avoiding the duplication of similar content in the protocols.

[0247] In some optional embodiments, the aforementioned first information may also be carried in a first response message, a data notification message, etc.

[0248] Optionally, the underlying transport protocol mapping rule includes at least one of the following:

[0249] The underlying transport protocol of the data packets of the data service protocol is determined based on at least one of the following: the total data volume of the data packets of the data service protocol, the length of the data packets of the data service protocol, and the endpoint of the data packets of the data service protocol.

[0250] The underlying transport protocol of the data packets of the data service protocol is determined based on the mapping relationship between the data service model and the underlying transport protocol.

[0251] The underlying transport protocol of the data packets in the aforementioned data service protocol can be understood as the underlying transport protocol used to map the data packets of the aforementioned data service protocol; that is, the data packets of the aforementioned data service protocol are mapped to this underlying transport protocol for transmission. The endpoint of the data packets of the aforementioned data service protocol can be understood as the consumer node of the data packets of the aforementioned data service protocol or the final receiving node of the data packets of the aforementioned data service protocol, etc. The transmission of the data packets of the aforementioned data service protocol ends after reaching the endpoint.

[0252] In some implementations, the underlying transport protocol of the data service protocol data packets can be determined based on at least one of the total data volume of the data service protocol data packets, the length of the data service protocol data packets, and the endpoint of the data service protocol data packets. This can make the determined underlying transport protocol more suitable for the transmission of the data service protocol data packets.

[0253] For example, a mapping relationship can be established between the total data volume of the data packets of the data service protocol, the length of the data packets of the data service protocol, and the endpoint of the data packets of the data service protocol and the lower-level transport protocol, as shown in Table 1.

[0254] Table 1. Example of a mapping rule for a low-level transport protocol.

[0255] In other implementations, the underlying transport protocol of the data packets of the data service protocol can be determined based on the mapping relationship between the data service model and the underlying transport protocol. For example, the underlying transport protocol corresponding to the data service model used by the data packets of the data service protocol can be determined based on the mapping relationship between the data service model and the underlying transport protocol, which facilitates the rapid determination of the underlying transport protocol of the data packets of the data service protocol. For example, the mapping relationship between the data service model and the underlying transport protocol can be shown in Table 2.

[0256] Table 2. Example of a mapping rule for a low-level transport protocol.

[0257] In other embodiments, the underlying transport protocol of the data service protocol's data packets is determined based on at least one of the total data volume of the data service protocol's data packets, the length of the data service protocol's data packets, and the endpoint of the data service protocol's data packets, as well as the mapping relationship between the data service model and the underlying transport protocol. For example, a first underlying transport protocol can be determined based on at least one of the total data volume of the data service protocol's data packets, the length of the data service protocol's data packets, and the endpoint of the data service protocol's data packets, and a second underlying transport protocol can be determined based on the mapping relationship between the data service model and the underlying transport protocol. If the first underlying transport protocol and the second underlying transport protocol are different, one underlying transport protocol can be selected from the first underlying transport protocol and the second underlying transport protocol as the underlying transport protocol of the data service protocol's data packets. This can improve the flexibility of determining the underlying transport protocol of the data service protocol's data packets.

[0258] In some optional embodiments, before the first node sends the first request message, the method further includes:

[0259] The first node establishes a low-level connection with the second node;

[0260] Where one of the first node and the second node is a terminal and the other is a network-side device, the underlying connection includes the following: control plane connection, user plane connection, and data plane connection.

[0261] When both the first node and the second node are network-side devices, the underlying connection includes the following: Stream Control Protocol (SCTP) connection, Transmission Control Protocol (TCP) connection, Hypertext Transfer Protocol (HTTP) connection, and Quick UDP Internet Connections (QUIC) connection.

[0262] The aforementioned control plane (CP) connections include, for example, the RRC connection between the UE and the radio access network, or the NAS connection between the UE and the core network.

[0263] The aforementioned User Plane (UP) connection, for example, the GTP connection between the UE and the core network.

[0264] The aforementioned data plane connections include, for example, the data plane connection between the UE and the radio access network, or the data plane connection between the UE and the core network.

[0265] For example, the first node can establish a low-level connection based on the pre-configured address of the second node (such as an IP address, cell ID, gNBID, AMF ID, etc.). Alternatively, either the first or second node can obtain low-level connection configuration information from other nodes (such as network management nodes) and establish the connection.

[0266] Please refer to Figure 4, which is a flowchart of a transmission method provided in an embodiment of this application. This method can be executed by a second node, and as shown in Figure 4, it includes the following steps:

[0267] Step 401: The second node receives a first request message from the first node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information about at least one data service model, the data service model being used to describe a set of data parameters.

[0268] Optionally, the method further includes:

[0269] The second node sends a first response message to the first node;

[0270] The first response message includes at least one of the following:

[0271] A first instruction is used to indicate whether to accept or reject the first request message;

[0272] Information about the accepted data service model;

[0273] Information regarding the rejected data service model;

[0274] The first reason indicator is used to indicate the reason for rejecting the data service model.

[0275] Optionally, the information of the data service model includes at least one of the following:

[0276] The identification information of the data service model;

[0277] The version of the data service model;

[0278] Node identification information, used to indicate the nodes to which the data service model applies;

[0279] Data collection mode indicator, used to indicate the data collection mode.

[0280] Optionally, the first request message is a data service interface establishment request message, which is used to request the establishment of a data service interface between the first node and the second node;

[0281] The at least one data service model is at least one data service model supported or requested by the first node.

[0282] Optionally, the second node is a data node.

[0283] Optionally, the method further includes:

[0284] The second node sends its data service capability information to the network management node.

[0285] In this embodiment, the second node can report its data service capability information to the network management node. After receiving the data service capability information, the network management node can store it. The network management node can be a base station or an AMF (Active Data Function) node, etc. In some optional embodiments, the network management node can be a data function node; for example, if the first node is a data function node, then the network management node can be the first node.

[0286] In this embodiment, the second node reports its data service capability information to the network management node, so that the first node can obtain the data service capability information of the second node and select a suitable second node for interaction.

[0287] Optionally, the data service capability information includes at least one of the following:

[0288] A first capability indicator is used to indicate whether the data service protocol is supported;

[0289] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0290] Information on supported data service models.

[0291] Optionally, the first request message is a data collection request message;

[0292] The at least one data service model is a data service model requested by the first node to be used between the second node and the third node, wherein the third node is a data consumption node, and the data consumption node is the node that consumes the data parameters to be collected.

[0293] Optionally, the first request message may further include a first parameter indication, used to indicate the data parameters to be collected;

[0294] And / or,

[0295] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0296] Optionally, the first request message is a data subscription request message, used to request subscription data parameters;

[0297] The at least one data service model is a data service model requested by the first node to be used between the first node and the fourth node, wherein the fourth node is a data providing node, and the data providing node is the node that provides the data parameters to be subscribed.

[0298] Optionally, the first request message further includes a second parameter indication for indicating the data parameters to be subscribed;

[0299] And / or,

[0300] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0301] Optionally, the information in the rejected data parameters includes at least one of the following:

[0302] The third parameter indicates the data parameters rejected by the second node;

[0303] The third reason indicator is used to indicate the reason for rejecting the data parameter.

[0304] Optionally, the method further includes:

[0305] The second node sends a data notification message to the first node;

[0306] The data notification message includes at least one of the following:

[0307] The second instruction is used to indicate that the data parameters for the requested subscription have been collected;

[0308] The requested subscription data parameters or the identification information of the fifth node, wherein the fifth node is the node that provides the requested subscription data parameters.

[0309] Optionally, the first request message may further include first information; or,

[0310] The method further includes: the second node receiving first information from the first node;

[0311] The first information includes at least one of the following:

[0312] Protocol mapping rules are used to indicate the rules for mapping data packets of the data service protocol to the underlying transport protocol;

[0313] The second protocol indication is used to indicate the underlying transport protocol used to send the data packets of the data service protocol;

[0314] A reflection indication is used to indicate that the data packets sending the data service protocol and the data packets receiving the data service protocol use the same underlying transport protocol.

[0315] Optionally, the protocol mapping rule includes at least one of the following:

[0316] The underlying transport protocol of the data packets of the data service protocol is determined based on at least one of the following: the total data volume of the data packets of the data service protocol, the length of the data packets of the data service protocol, and the endpoint of the data packets of the data service protocol.

[0317] The underlying transport protocol of the data packets of the data service protocol is determined based on the mapping relationship between the data service model and the underlying transport protocol.

[0318] It should be noted that the implementation method of this method can be found in the relevant description of the embodiment shown in Figure 2, and will not be repeated here.

[0319] Please refer to Figure 5, which is a flowchart of a transmission method provided in an embodiment of this application. This method can be executed by a network management node, and as shown in Figure 5, it includes the following steps:

[0320] Step 501: The network management node performs the first operation;

[0321] The first operation includes at least one of the following:

[0322] Receive data service capability information from the second node;

[0323] Receive a capability request message from the first node, the capability request message being used to request data service capability information of at least one second node;

[0324] The data service capability information includes at least one of the following:

[0325] The first capability indicator is used to indicate whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model;

[0326] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0327] Information on supported data service models.

[0328] Optionally, the information of the data service model includes at least one of the following:

[0329] The identification information of the data service model;

[0330] The version of the data service model;

[0331] Node identification information, used to indicate the nodes to which the data service model applies;

[0332] Data collection mode indicator, used to indicate the data collection mode.

[0333] It should be noted that the implementation method of this method can be found in the relevant descriptions of the embodiments shown in Figures 2 and 4, and will not be repeated here.

[0334] The embodiments of this application are illustrated below with examples:

[0335] Example 1: Method for establishing a data service interface.

[0336] The main idea of ​​this example is: the first node triggers the establishment of a data service interface, and during the establishment process, sends a data service model, thereby implementing a data service protocol that supports data service models between different nodes. This method can reduce the binding relationship between the data service protocol and the sending or receiving node, thus reducing the number of data service protocols and avoiding the duplication of similar content in the protocol.

[0337] In this example, the first node is a data node, and the second node is a data function node or a data node. For example, referring to Figure 6, the transmission method provided in this embodiment includes the following steps:

[0338] Step a1: Establish the underlying connection between the first node and the second node.

[0339] For details regarding lower-level connections, please refer to the relevant descriptions in the foregoing embodiments, which will not be repeated here.

[0340] It should be noted that step a1 above can be an optional step.

[0341] Step a2: The first node sends a data service interface establishment request message, which includes information about the data service models supported by the first node, such as a list of data service models supported by the first node.

[0342] The information in the aforementioned data service model may include at least one of the following:

[0343] Identification information for the data service model;

[0344] Version of the data service model;

[0345] The reuse instruction is used to indicate whether the data service model is also applicable between the first node and other nodes, in addition to the first node and the second node;

[0346] The list of other nodes indicates the nodes that, in addition to the second node, are applicable to this data service model;

[0347] Data collection mode indication, used to indicate the data collection mode applicable to the data service model; or used to indicate the data collection mode applicable to all data service models included in the data service interface establishment request message;

[0348] Step a3: The second node receives the data service interface establishment request message and sends the data service interface establishment response message to the first node.

[0349] For example, the data service interface establishment response message mentioned above may include at least one of the following:

[0350] The identifier of the second node, which is used to uniquely identify the second node;

[0351] Accept or reject instruction (i.e., the first instruction) is used to indicate whether to accept the data service interface establishment request;

[0352] The list of accepted data service models is used to indicate the data service models accepted by the second node;

[0353] The list of rejected data service models indicates the data service models rejected by the second node.

[0354] For example, the list of accepted data service models may include at least one of the following:

[0355] The data service model ID is used to indicate the data service model accepted by the second node. This data service model ID is the data service model ID that is already included in the data service model list in the first request message.

[0356] Data service model version, used to indicate the version of the data service model accepted by the second node;

[0357] The data collection mode is used to indicate the data collection mode accepted by the second node. For example, the data service model 1 in the first request message is applicable to single-end mode, dual-end mode, sharing mode and data exchange mode. The second node accepts this data service model for sharing mode.

[0358] For example, the list of rejected data service models may include at least one of the following:

[0359] The data service model ID is used to indicate the data service model rejected by the second node. This data service model ID is a data service model ID that is already included in the data service model list in the first request message.

[0360] Data service model version, used to indicate the version of the data service model rejected by the second node;

[0361] Data collection mode, used to indicate the data collection mode rejected by the second node. For example, if data service model 1 in the first request message is applicable to single-end mode, dual-end mode, sharing mode and data exchange mode, the second node rejects the data service model for dual-end mode, sharing mode and data exchange mode.

[0362] Reasons for rejection, such as the second node not being supported.

[0363] Example 2: Data service method based on capability reporting.

[0364] The main idea of ​​this example is that the second node provides its data service capability information through capability reporting, and the first node requests this information from the node maintaining its own capability information based on its needs. This allows different first and second nodes to use the same data service protocol without requiring multiple different protocols. Furthermore, the first and second nodes can use different data service models to meet specific data service requirements.

[0365] In this example, the first node is a data function node, and the second node is a data node. For example, referring to Figure 7, the transmission method provided in this embodiment includes the following steps:

[0366] Step b1: The second node sends the above data service capability information to the network management node.

[0367] The information regarding the aforementioned data service capabilities can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0368] The network management node can store data service capability information reported by the second node. Furthermore, the network management node may or may not be the first node. When the network management node is not the first node, proceed to steps b2 and b3; when the network node is the first node (e.g., core network data function or base station), steps b2 and b3 can be skipped, meaning steps b2 and b3 are not executed.

[0369] Step b2: The first node sends a capability request message to the network management node that maintains the capabilities of the second node as needed. The capability request message can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0370] Step b3: The network management node that maintains the capability information of the second node sends a capability response message to the first node. The capability response message can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0371] Step b4: The first node selects a suitable second node based on data collection or internal network data transmission needs, and sends a data service interface establishment request message to the selected second node. The details of the data service interface establishment request message can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0372] Step b5: The second node receives the data service interface establishment response message and sends a data service interface response message. The data service interface establishment response message can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0373] Example 3: A data collection method.

[0374] The main idea of ​​this example is to use a corresponding data service model to complete data collection through the data service protocol process, thereby implementing a data service protocol that supports data service models between different nodes. This includes data services between the same first node and different second nodes, or between different first nodes and the same second node, or between different first nodes and second nodes. This method can reduce the binding relationship between the data service protocol and the sending or receiving node, thereby reducing the number of data service protocols and avoiding the duplication of similar content in the protocol.

[0375] In this example, the first node is a data function node, and the second node is a data node. For example, referring to Figure 8, the transmission method provided in this embodiment includes the following steps:

[0376] Step c1: The first node selects one or more second nodes based on its data requirements and sends a data collection request message to the selected second nodes.

[0377] For example, the data collection request message may include at least one of the following:

[0378] The message type indicates that the message is a data collection message;

[0379] Data collection type, used to indicate the type of data collection;

[0380] Data collection ID, used to identify the data collection;

[0381] Data parameter information, used to indicate the data parameters requested to be collected, for example, the aforementioned data parameter information may include at least one of data service model information and data parameter indication;

[0382] At least one data acquisition target;

[0383] At least one data acquisition method.

[0384] Step c2: The second node receives the data collection request message and sends a data collection response message to the first node.

[0385] For example, the data collection response message may include at least one of the following:

[0386] Message type: Indicates that the message is a data collection message;

[0387] Accept or reject instructions are used to indicate whether to accept the data collection request;

[0388] The list of accepted data parameters indicates the data parameters accepted by the second node;

[0389] The list of rejected data parameters indicates the data parameters that the second node rejects.

[0390] Step c3: The second node reports the collected data according to the data service configuration information and sends the data report to the third node. The third node can be the first node (such as the core network data function) or other nodes responsible for receiving data (such as the core network perception function).

[0391] Example 4: A method for acquiring or opening up data.

[0392] The main idea of ​​this example is to use a data service protocol process and corresponding data service model to enable data consumers to obtain data. This achieves a data service protocol that supports data service models between different nodes, including data services between the same first node and different second nodes, or between different first nodes and the same second node, or between different first nodes and second nodes. This method can reduce the binding relationship between the data service protocol and the sending or receiving node, thereby reducing the number of data service protocols and avoiding the duplication of similar content in the protocol.

[0393] In this example, the first node is a data node, and the second node is a data function node. For example, referring to Figure 9, the transmission method provided in this embodiment includes the following steps:

[0394] Step d1: The first node requests the required data from the appropriate second node according to its data needs, that is, the first node sends a data subscription request message to the second node.

[0395] For example, the data subscription request message may include at least one of the following:

[0396] The message type indicates whether the message is a data subscription message;

[0397] Data parameter information, used to indicate the data parameters requested for subscription, may include at least one of data service model information and data parameter indication;

[0398] At least one data acquisition target;

[0399] At least one data acquisition method.

[0400] Step d2: The second node receives the data subscription request message and sends a data subscription response message.

[0401] For example, the data subscription response includes at least one of the following:

[0402] Message type: Indicates that the message is a data subscription message;

[0403] Accept or reject instructions are used to indicate whether to accept the data collection request;

[0404] The list of accepted data parameters indicates the data parameters accepted by the second node;

[0405] The list of rejected data parameters indicates the data parameters that the second node rejects.

[0406] Step d3: The second node determines whether the collected data satisfies the aforementioned data subscription requests based on one or more received data subscription requests. If the collected data satisfies the aforementioned data subscription requests, it sends a data notification message to the first node; if the collected data does not satisfy the aforementioned data subscription requests, the second node selects a suitable node to collect data, and after obtaining data that satisfies the data subscription requests, it sends a data notification message to the first node.

[0407] The data notification messages can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0408] Step d4: When the data parameters that satisfy the subscription are provided by a node other than the second node (i.e., the fifth node), the first node obtains the required subscription data based on the identification information of the fifth node when it needs the subscribed data.

[0409] In summary, the embodiments of this application employ a data service model to define the data service protocol. This data service protocol can support data service models between different nodes, including data services between the same first node and different second nodes, or between different first nodes and the same second node, or between different first nodes and second nodes. This reduces the binding relationship between the data service protocol and the sending or receiving node, thereby reducing the number of data service protocols and avoiding the duplication of similar content in the protocol. Furthermore, using a data service model to define the data service protocol facilitates data expansion according to needs, allowing for the addition of new data through new data service models or new versions of existing models. Additionally, the first or second node can flexibly define and use the data service model from dimensions such as data provider node and data consumer node. Different nodes can also share the data service model; for example, a UE or base station can use the perceived data service model. Moreover, this data service protocol has a weak binding relationship with the underlying transmission protocol, making it suitable for both air interface transmission protocols between the UE and the network, and wired transmission protocols between network functions.

[0410] It should be noted that the transmission method provided in this application embodiment can be executed by a transmission device. This application embodiment uses the execution of the transmission method by a transmission device as an example to illustrate the transmission device provided in this application embodiment.

[0411] This application provides a transmission device. As an example, the transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0412] The transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0413] Specifically, referring to Figure 10, when the transmission device is a network-side device or a component or terminal within a network-side device, the transmission device 1000 includes a sending module 1001, used to send a first request message to the second node. The first request message includes information related to a data service protocol, wherein the data service protocol is a protocol based on a data service model, and the information related to the data service protocol includes information about at least one data service model, wherein the data service model is used to describe a set of data parameters.

[0414] Optionally, the device further includes:

[0415] The receiving module is used to receive the first response message from the second node;

[0416] The first response message includes at least one of the following:

[0417] A first instruction is used to indicate whether to accept or reject the first request message;

[0418] Information about the accepted data service model;

[0419] Information regarding the rejected data service model;

[0420] The first reason indicator is used to indicate the reason for rejecting the data service model.

[0421] Optionally, the information of the data service model includes at least one of the following:

[0422] The identification information of the data service model;

[0423] The version of the data service model;

[0424] Node identification information, used to indicate the nodes to which the data service model applies;

[0425] Data collection mode indicator, used to indicate the data collection mode.

[0426] Optionally, the identification information of the data service model includes at least one of the following: the identifier ID of the data service model, and the name of the data service model.

[0427] Optionally, the first request message is a data service interface establishment request message, which is used to request the establishment of a data service interface between the first node and the second node;

[0428] The at least one data service model is at least one data service model supported or requested by the first node.

[0429] Optionally, the first node is a data function node.

[0430] Optionally, the sending module is further configured to send a capability request message to the network management node, the capability request message being used to request the acquisition of data service capability information of at least one second node;

[0431] The apparatus further includes a receiving module for receiving a capability response message from the network management node, the capability response message being used to indicate whether to accept or reject the capability request message.

[0432] Optionally, the capability request message includes at least one of the following:

[0433] Identification information of at least one second node;

[0434] Capability information indicator, used to indicate the data service capability information requested;

[0435] A data consumer indicator is used to indicate the data consumer node or data consumer node type to which the data provided by at least one second node is applicable.

[0436] Optionally, the capability response message includes data service capability information of at least one second node;

[0437] or,

[0438] The capability response message includes at least one of the following:

[0439] Denial indication is used to indicate a refusal to provide information on the ability to provide data services;

[0440] The second reason indication is used to indicate the reason for refusing to provide data service capability information.

[0441] Optionally, the data service capability information includes at least one of the following:

[0442] A first capability indicator is used to indicate whether the data service protocol is supported;

[0443] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0444] Information on supported data service models.

[0445] Optionally, the first request message is a data collection request message;

[0446] The at least one data service model is a data service model requested by the first node to be used between the second node and the third node, wherein the third node is a data consumption node, and the data consumption node is the node that consumes the data parameters to be collected.

[0447] Optionally, the first request message may further include a first parameter indication, used to indicate the data parameters to be collected;

[0448] And / or,

[0449] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0450] Optionally, the first request message is a data subscription request message, used to request subscription data parameters;

[0451] The at least one data service model is a data service model requested by the first node to be used between the first node and the fourth node, wherein the fourth node is a data providing node, and the data providing node is the node that provides the data parameters to be subscribed.

[0452] Optionally, the first request message further includes a second parameter indication for indicating the data parameters to be subscribed;

[0453] And / or,

[0454] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0455] Optionally, the information in the rejected data parameters includes at least one of the following:

[0456] The third parameter indicates the data parameters rejected by the second node;

[0457] The third reason indicator is used to indicate the reason for rejecting the data parameter.

[0458] Optionally, the sending module is further configured to send a data notification message to the second node;

[0459] The data notification message includes at least one of the following:

[0460] The second instruction is used to indicate that the data parameters for the requested subscription have been collected;

[0461] The requested subscription data parameters or the identification information of the fifth node, wherein the fifth node is the node that provides the requested subscription data parameters.

[0462] Optionally, the first request message may further include first information; or,

[0463] The sending module is also used to send first information from the first node to the second node;

[0464] The first information includes at least one of the following:

[0465] Protocol mapping rules are used to indicate the rules for mapping data packets of the data service protocol to the underlying transport protocol;

[0466] The second protocol indication is used to indicate the underlying transport protocol used to send the data packets of the data service protocol;

[0467] A reflection indication is used to indicate that the data packets sending the data service protocol and the data packets receiving the data service protocol use the same underlying transport protocol.

[0468] Optionally, the underlying transport protocol mapping rule includes at least one of the following:

[0469] The underlying transport protocol of the data packets of the data service protocol is determined based on at least one of the following: the total data volume of the data packets of the data service protocol, the length of the data packets of the data service protocol, and the endpoint of the data packets of the data service protocol.

[0470] The underlying transport protocol of the data packets of the data service protocol is determined based on the mapping relationship between the data service model and the underlying transport protocol.

[0471] The transmission device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG2 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0472] Referring to Figure 11, when the transmission device is a network-side device or a component of a network-side device or a terminal or a component of a terminal, the transmission device 1100 includes a receiving module 1101, which is used to receive a first request message from a first node. The first request message includes information related to a data service protocol. The data service protocol is a protocol based on a data service model. The information related to the data service protocol includes information about at least one data service model, which is used to describe a set of data parameters.

[0473] Optionally, the device further includes a sending module for sending a first response message to the first node;

[0474] The first response message includes at least one of the following:

[0475] A first instruction is used to indicate whether to accept or reject the first request message;

[0476] Information about the accepted data service model;

[0477] Information regarding the rejected data service model;

[0478] The first reason indicator is used to indicate the reason for rejecting the data service model.

[0479] Optionally, the information of the data service model includes at least one of the following:

[0480] The identification information of the data service model;

[0481] The version of the data service model;

[0482] Node identification information, used to indicate the nodes to which the data service model applies;

[0483] Data collection mode indicator, used to indicate the data collection mode.

[0484] Optionally, the first request message is a data service interface establishment request message, which is used to request the establishment of a data service interface between the first node and the second node;

[0485] The at least one data service model is at least one data service model supported or requested by the first node.

[0486] Optionally, the second node is a data node.

[0487] Optionally, the device further includes a sending module for sending data service capability information of the second node to the network management node.

[0488] Optionally, the data service capability information includes at least one of the following:

[0489] A first capability indicator is used to indicate whether the data service protocol is supported;

[0490] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0491] Information on supported data service models.

[0492] Optionally, the first request message is a data collection request message;

[0493] The at least one data service model is a data service model requested by the first node to be used between the second node and the third node, wherein the third node is a data consumption node, and the data consumption node is the node that consumes the data parameters to be collected.

[0494] Optionally, the first request message may further include a first parameter indication, used to indicate the data parameters to be collected;

[0495] And / or,

[0496] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0497] Optionally, the first request message is a data subscription request message, used to request subscription data parameters;

[0498] The at least one data service model is a data service model requested by the first node to be used between the first node and the fourth node, wherein the fourth node is a data providing node, and the data providing node is the node that provides the data parameters to be subscribed.

[0499] Optionally, the first request message further includes a second parameter indication for indicating the data parameters to be subscribed;

[0500] And / or,

[0501] The first response message also includes at least one of the following: information on accepted data parameters, and information on rejected data parameters.

[0502] Optionally, the information in the rejected data parameters includes at least one of the following:

[0503] The third parameter indicates the data parameters rejected by the second node;

[0504] The third reason indicator is used to indicate the reason for rejecting the data parameter.

[0505] Optionally, the receiving module is further configured to receive a data notification message from the first node;

[0506] The data notification message includes at least one of the following:

[0507] The second instruction is used to indicate that the data parameters for the requested subscription have been collected;

[0508] The requested subscription data parameters or the identification information of the fifth node, wherein the fifth node is the node that provides the requested subscription data parameters.

[0509] Optionally, the first request message may further include first information; or,

[0510] The receiving module is further configured to receive first information from the first node;

[0511] The first information includes at least one of the following:

[0512] Protocol mapping rules are used to indicate the rules for mapping data packets of the data service protocol to the underlying transport protocol;

[0513] The second protocol indication is used to indicate the underlying transport protocol used to send the data packets of the data service protocol;

[0514] A reflection indication is used to indicate that the data packets sending the data service protocol and the data packets receiving the data service protocol use the same underlying transport protocol.

[0515] Optionally, the protocol mapping rule includes at least one of the following:

[0516] The underlying transport protocol of the data packets of the data service protocol is determined based on at least one of the following: the total data volume of the data packets of the data service protocol, the length of the data packets of the data service protocol, and the endpoint of the data packets of the data service protocol.

[0517] The underlying transport protocol of the data packets of the data service protocol is determined based on the mapping relationship between the data service model and the underlying transport protocol.

[0518] The transmission device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG4 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0519] Referring to Figure 12, when the transmission device is a network-side device or a component of a network-side device, the transmission device 1200 includes a processing module 1201 for performing a first operation;

[0520] The first operation includes at least one of the following:

[0521] Receive data service capability information from the second node;

[0522] Receive a capability request message from the first node, the capability request message being used to request data service capability information of at least one second node;

[0523] The data service capability information includes at least one of the following:

[0524] The first capability indicator is used to indicate whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model;

[0525] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0526] Information on supported data service models.

[0527] Optionally, the information of the data service model includes at least one of the following:

[0528] The identification information of the data service model;

[0529] The version of the data service model;

[0530] Node identification information, used to indicate the nodes to which the data service model applies;

[0531] Data collection mode indicator, used to indicate the data collection mode.

[0532] The transmission device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG5 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0533] As shown in Figure 13, this application embodiment also provides a communication device 1300, including a processor 1301 and a memory 1302. The memory 1302 stores programs or instructions that can run on the processor 1301. For example, when the communication device 1300 is a first node, when the program or instructions are executed by the processor 1301, they implement the various steps of the above-described first node-side transmission method embodiment and achieve the same technical effect. When the communication device 1300 is a second node, when the program or instructions are executed by the processor 1301, they implement the various steps of the above-described second node-side transmission method embodiment and achieve the same technical effect. When the communication device 1300 is a network management node, when the program or instructions are executed by the processor 1301, they implement the various steps of the above-described network management node-side transmission method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0534] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiments shown in FIG2 or FIG4. This terminal embodiment corresponds to the above-described terminal-side method embodiments, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the transmission device shown in FIG10 or FIG11. Specifically, FIG14 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0535] The terminal 1400 includes, but is not limited to, at least some of the following components: radio frequency unit 1401, network module 1402, audio output unit 1403, input unit 1404, sensor 1405, display unit 1406, user input unit 1407, interface unit 1408, memory 1409, and processor 1410.

[0536] Those skilled in the art will understand that the terminal 1400 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1410 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 14 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0537] It should be understood that, in this embodiment, the input unit 1404 may include a graphics processor 14041 and a microphone 14042. The graphics processor 14041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1406 may include a display panel 14061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1407 includes at least one of a touch panel 14071 and other input devices 14072. The touch panel 14071 is also called a touch screen. The touch panel 14071 may include a touch detection device and a touch controller. Other input devices 14072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0538] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1401 can transmit it to the processor 1410 for processing; in addition, the radio frequency unit 1401 can send uplink data to the network-side device. Typically, the radio frequency unit 1401 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0539] The memory 1409 can be used to store software programs or instructions, as well as various data. The memory 1409 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1409 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1409 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0540] Processor 1410 may include one or more processing units; optionally, processor 1410 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1410.

[0541] The radio frequency unit 1401 is used to send a first request message to the second node. The first request message includes information related to a data service protocol. The data service protocol is a protocol based on a data service model. The information related to the data service protocol includes information about at least one data service model. The data service model is used to describe a set of data parameters.

[0542] or,

[0543] Radio frequency unit 1401 is used to receive a first request message from a first node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information of at least one data service model, the data service model being used to describe a set of data parameters.

[0544] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the transmission method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0545] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG2, FIG4, or FIG5. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0546] Specifically, this application embodiment also provides a network-side device, which can be the transmission device shown in FIG10, FIG11, or FIG12. As shown in FIG15, the network-side device 1500 includes: an antenna 1501, a radio frequency device 1502, a baseband device 1503, a processor 1504, and a memory 1505. The antenna 1501 is connected to the radio frequency device 1502. In the uplink direction, the radio frequency device 1502 receives information through the antenna 1501 and sends the received information to the baseband device 1503 for processing. In the downlink direction, the baseband device 1503 processes the information to be transmitted and sends it to the radio frequency device 1502, which processes the received information and then transmits it through the antenna 1501.

[0547] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1503, which includes a baseband processor.

[0548] The baseband device 1503 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG15. One of the chips is, for example, a baseband processor, which is connected to the memory 1505 via a bus interface to call the program or instructions in the memory 1505 to execute the network-side device operation shown in the above method embodiment.

[0549] The network-side device may also include a network interface 1506, such as a Common Public Radio Interface (CPRI).

[0550] The radio frequency device 1502 is used to send a first request message to the second node. The first request message includes information related to a data service protocol. The data service protocol is a protocol based on a data service model. The information related to the data service protocol includes information about at least one data service model. The data service model is used to describe a set of data parameters.

[0551] or,

[0552] Radio frequency device 1502 is configured to receive a first request message from a first node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information of at least one data service model, the data service model being used to describe a set of data parameters.

[0553] or,

[0554] Processor 1504 is used to perform the first operation;

[0555] The first operation includes at least one of the following:

[0556] Receive data service capability information from the second node;

[0557] Receive a capability request message from the first node, the capability request message being used to request data service capability information of at least one second node;

[0558] The data service capability information includes at least one of the following:

[0559] The first capability indicator is used to indicate whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model;

[0560] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0561] Information on supported data service models.

[0562] In addition, the network-side device 1500 of this application embodiment also includes: a program or instructions stored in the memory 1505 and executable on the processor 1504. The processor 1504 calls the program or instructions in the memory 1505 to execute the methods executed by the modules shown in FIG10, FIG11 or FIG12 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0563] Specifically, this application also provides a network-side device. As shown in FIG16, the network-side device 1600 includes a processor 1601, a network interface 1602, and a memory 1603. The network-side device may be the transmission device shown in FIG10, FIG11, or FIG12. The network interface 1602 is, for example, a Common Public Radio Interface (CPRI).

[0564] The network interface 1602 is used to send a first request message to the second node. The first request message includes information related to a data service protocol. The data service protocol is a protocol based on a data service model. The information related to the data service protocol includes information about at least one data service model. The data service model is used to describe a set of data parameters.

[0565] or,

[0566] Network interface 1602 is used to receive a first request message from a first node, wherein the first request message includes information related to a data service protocol, the data service protocol being a protocol based on a data service model, and the information related to the data service protocol including information of at least one data service model, the data service model being used to describe a set of data parameters;

[0567] or,

[0568] Processor 1601 is used to perform the first operation;

[0569] The first operation includes at least one of the following:

[0570] Receive data service capability information from the second node;

[0571] Receive a capability request message from the first node, the capability request message being used to request data service capability information of at least one second node;

[0572] The data service capability information includes at least one of the following:

[0573] The first capability indicator is used to indicate whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model;

[0574] The first protocol indication is used to indicate the underlying transport protocol supported when transmitting using the data service protocol.

[0575] Information on supported data service models.

[0576] In addition, the network-side device 1600 of this application embodiment also includes: a program or instructions stored in the memory 1603 and executable on the processor 1601. The processor 1601 calls the program or instructions in the memory 1603 to execute the methods executed by the modules shown in FIG10, FIG11 or FIG12 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0577] This application also provides a readable storage medium storing a program or instructions. When executed by a processor, the program or instructions implement the various processes of the above-described transmission method embodiments and achieve the same technical effects. To avoid repetition, these will not be described again here. The processor is the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0578] This application also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-described transmission method embodiments, achieving the same technical effect. To avoid repetition, it will not be described again here. It should be understood that the chip mentioned in this application embodiment can also be called a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0579] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0580] This application also provides a transmission system, including a first node and a second node. The first node can be used to perform the steps of the transmission method described above, and the second node can be used to perform the steps of the transmission method described above. Optionally, the transmission system further includes a network management node, which can be used to perform the steps of the transmission method described above.

[0581] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, for example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples. Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.). The computer software product includes several instructions to cause a terminal or network-side device to execute the methods described in the various embodiments of this application. The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art, under the guidance of this application, can make many other implementations without departing from the spirit and scope of the claims, and all such implementations fall within the protection scope of this application.

Claims

A transmission method, comprising: sending, by a first node, a first request message to a second node, wherein the first request message comprises data service protocol related information, the data service protocol is a protocol based on a data service model, and the data service protocol related information comprises information of at least one data service model used for describing a set of data parameters. The method according to claim 1, further comprising: receiving, by the first node, a first response message from the second node; wherein the first response message comprises at least one of: a first indication indicating acceptance or rejection of the first request message; information of an accepted data service model; information of a rejected data service model; a first reason indication indicating a reason for rejecting a data service model. The method according to claim 1 or 2, wherein The information of the data service model comprises at least one of: identification information of the data service model; a version of the data service model; node identification information indicating a node to which the data service model is applicable; a data collection mode indication indicating a data collection mode. The method of claim 3, wherein, The identification information of the data service model comprises at least one of: an identification ID of the data service model and a name of the data service model. The method of any one of claims 1 to 4, wherein, The first request message is a data service interface establishment request message used for requesting establishment of a data service interface between the first node and the second node. The at least one data service model is at least one data service model supported by or requested to be used by the first node. The method of any one of claims 1 to 4, wherein, The first node is a data function node. The method according to claim 6, further comprising: sending, by the first node, a capability request message to a network management node, the capability request message being used for requesting acquisition of data service capability information of at least one second node; receiving, by the first node, a capability response message from the network management node, the capability response message being used for indicating acceptance or rejection of the capability request message. The method of claim 7, wherein, The capability request message comprises at least one of: identification information of the at least one second node; a capability information indication indicating requested data service capability information; a data consumer indication indicating a data consumer node or a data consumer node type to which data provided by the at least one second node is applicable. The method according to claim 7 or 8, wherein: the capability response message comprises data service capability information of the at least one second node; or the capability response message comprises at least one of: a rejection indication indicating rejection of providing data service capability information; a second reason indication indicating a reason for rejecting providing data service capability information. The data service capability information comprises at least one of: The method according to claim 8 or 9, wherein a first capability indication indicating whether the data service protocol is supported; a first protocol indication indicating a supported underlying transmission protocol when the data service protocol is used for transmission; information of a supported data service model. The first request message is a data collection request message; The method of any one of claims 6 to 10, wherein, ​ The at least one data service model is a data service model requested by the first node to be used between the second node and a third node, the third node being a data consumption node, the data consumption node being a consumption node of the requested collected data parameter. The method of claim 11, wherein, The first request message further comprises a first parameter indication, used to indicate a requested collected data parameter. And / or, The first response message further comprises at least one of the following: information of an accepted data parameter, information of a rejected data parameter. The method of any one of claims 1 to 4, wherein, The first request message is a data subscription request message, used to request to subscribe to a data parameter. The at least one data service model is a data service model requested by the first node to be used between the first node and a fourth node, the fourth node being a data provision node, the data provision node being a provision node of the requested subscribed data parameter. The method of claim 13, wherein, The first request message further comprises a second parameter indication, used to indicate a requested subscribed data parameter. And / or, The first response message further comprises at least one of the following: information of an accepted data parameter, information of a rejected data parameter. The method according to claim 12 or 14, wherein The information of the rejected data parameter comprises at least one of the following: A third parameter indication, used to indicate a data parameter rejected by the second node; A third reason indication, used to indicate a reason for rejecting the data parameter. The method according to any one of claims 13 to 15, further comprising: The first node receives a data notification message from the second node; The data notification message comprises at least one of the following: A second indication, used to indicate that the requested subscribed data parameter has been collected; The requested subscribed data parameter or identification information of a fifth node, the fifth node being a node that provides the requested subscribed data parameter. The method of any one of claims 1 to 16, wherein, The first request message further comprises first information; or The method further comprises: the first node sends first information to the second node; The first information comprises at least one of the following: A protocol mapping rule, used to indicate a rule of mapping a data packet of the data service protocol to an underlying transmission protocol; A second protocol indication, used to indicate an underlying transmission protocol used to send a data packet of the data service protocol; A reflection indication, used to indicate that a same underlying transmission protocol is used to send a data packet of the data service protocol and to receive a data packet of the data service protocol. The method of claim 17, wherein, The underlying transmission protocol mapping rule comprises at least one of the following: Determining an underlying transmission protocol of a data packet of the data service protocol according to at least one of a total amount of data of the data packet of the data service protocol, a length of the data packet of the data service protocol and a terminal node of the data packet of the data service protocol; Determining an underlying transmission protocol of a data packet of the data service protocol according to a mapping relationship between a data service model and an underlying transmission protocol. A transmission method, comprising: The second node receives a first request message from the first node, wherein the first request message comprises data service protocol related information, the data service protocol is a protocol based on a data service model, and the data service protocol related information comprises information of at least one data service model used for describing a set of data parameters. The method of claim 19, further comprising: The second node sends a first response message to the first node; The first response message comprises at least one of the following: a first indication indicating acceptance or rejection of the first request message; information of an accepted data service model; information of a rejected data service model; and a first cause indication indicating a cause of rejection of a data service model. The method according to claim 19 or 20, wherein The information of the data service model comprises at least one of the following: identification information of the data service model; a version of the data service model; node identification information indicating a node to which the data service model is applicable; a data collection mode indication indicating a data collection mode. The method of any one of claims 19-21, wherein The first request message is a data service interface establishment request message used for requesting establishment of a data service interface between the first node and the second node. The at least one data service model is at least one data service model supported by or requested to be used by the first node. The method of any one of claims 19 to 22, wherein, The second node is a data node. The method of claim 23, further comprising: The second node sends data service capability information of the second node to a network management node. The method of claim 24, wherein, The data service capability information comprises at least one of the following: a first capability indication indicating whether the data service protocol is supported; a first protocol indication indicating a supported underlying transmission protocol when the data service protocol is used for transmission; information of a supported data service model. The method of any one of claims 23 to 25, wherein, The first request message is a data collection request message. The at least one data service model is a data service model requested by the first node to be used between the second node and a third node, and the third node is a data consumption node which is a consumption node of requested collected data parameters. The method of claim 26, wherein, The first request message further comprises a first parameter indication indicating requested collected data parameters. and / or, The first response message further comprises at least one of the following: information of accepted data parameters and information of rejected data parameters. The method of any one of claims 19 to 22, wherein, The first request message is a data subscription request message used for requesting subscription of data parameters. The at least one data service model is a data service model requested by the first node to use between the first node and a fourth node, and the fourth node is a data provision node which is a provision node of requested subscribed data parameters. The method of claim 28, wherein, The first request message further comprises a second parameter indication indicating requested subscribed data parameters. and / or, The first response message further comprises at least one of the following: accepted data parameters and rejected data parameters. The method of claim 27 or 29, wherein, The information of the rejected data parameters comprises at least one of the following: A third parameter indication is configured to indicate a data parameter rejected by the second node. A third reason indication is configured to indicate a reason for rejecting the data parameter. The method of any one of claims 28-30, further comprising: sending, by the second node, a data notification message to the first node; wherein the data notification message comprises at least one of: a second indication configured to indicate that the requested subscribed data parameter has been collected; an identity of a fifth node that provides the requested subscribed data parameter. The method of any one of claims 19-31, wherein The first request message further comprises first information; or The method further comprises receiving, by the second node, the first information from the first node; wherein the first information comprises at least one of: a protocol mapping rule configured to indicate a rule of mapping a data packet of the data service protocol to an underlying transport protocol; a second protocol indication configured to indicate an underlying transport protocol used for sending the data packet of the data service protocol; a reflection indication configured to indicate that a same underlying transport protocol is used for sending the data packet of the data service protocol and receiving the data packet of the data service protocol. The method of claim 32, wherein, The protocol mapping rule comprises at least one of: determining the underlying transport protocol of the data packet of the data service protocol according to at least one of a total amount of data of the data packet of the data service protocol, a length of the data packet of the data service protocol, and a terminal node of the data packet of the data service protocol; determining the underlying transport protocol of the data packet of the data service protocol according to a mapping relationship between a data service model and an underlying transport protocol. A transmission method, comprising: performing, by a network management node, a first operation; wherein the first operation comprises at least one of: receiving, from a second node, data service capability information of the second node; receiving, from a first node, a capability request message, the capability request message being configured to request to obtain data service capability information of at least one second node; the data service capability information comprises at least one of: a first capability indication configured to indicate whether a data service protocol is supported, the data service protocol being a protocol based on a data service model; a first protocol indication configured to indicate an underlying transport protocol supported when the data packet of the data service protocol is transmitted; information of a data service model supported. The method of claim 34, wherein, The information of the data service model comprises at least one of: identity information of the data service model; a version of the data service model; node identity information configured to indicate a node to which the data service model is applicable; a data collection mode indication configured to indicate a data collection mode. A transmission apparatus, comprising: a sending module configured to send a first request message to a second node, wherein the first request message comprises data service protocol related information, the data service protocol being a protocol based on a data service model, and the data service protocol related information comprises information of at least one data service model, the data service model being configured to describe a group of data parameters. A transmission apparatus, comprising: The receiving module is configured to receive a first request message from a first node, wherein the first request message comprises data service protocol related information, the data service protocol is a protocol based on a data service model, and the data service protocol related information comprises information of at least one data service model used for describing a set of data parameters. A transmission apparatus comprises: The processing module is configured to perform a first operation. The first operation comprises at least one of the following: receiving data service capability information of the second node from the second node; receiving a capability request message from the first node, wherein the capability request message is used for requesting to obtain data service capability information of at least one second node; The data service capability information comprises at least one of the following: a first capability indication used for indicating whether a data service protocol is supported, wherein the data service protocol is a protocol based on a data service model; a first protocol indication used for indicating a supported underlying transmission protocol when the data service protocol is used for transmission; information of a supported data service model. A first node comprises a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement steps of the transmission method according to any one of claims 1 to 18. A second node comprises a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement steps of the transmission method according to any one of claims 19 to 33. A network management node comprises a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement steps of the transmission method according to any one of claims 34 to 35. A readable storage medium stores programs or instructions, and the programs or instructions are executed by a processor to implement the transmission method according to any one of claims 1 to 18, or to implement steps of the transmission method according to any one of claims 19 to 33, or to implement steps of the transmission method according to any one of claims 34 to 35. A computer program product is executed by at least one processor to implement steps of the transmission method according to any one of claims 1 to 18, or to implement steps according to any one of claims 19 to 33, or to implement steps according to any one of claims 34 to 35.

Images