Communication method and device

Abstract

A communication method and device, used for improving the data transmission efficiency. A data communication proxy in a 3GPP network may support a plurality of transmission protocols. The method comprises: a data communication proxy receiving a first subscription message from a first network element in a 3GPP network, the first subscription message being used for subscribing to data of a first information type; receiving first data from a second network element in the 3GPP network, wherein the first data is data of the first information type, and the first data is encapsulated by a first transmission protocol among a plurality of transmission protocols; and sending the first data to the first network element. Data transmission is directly carried out by means of a data communication proxy, so that the data transmission efficiency is improved. Moreover, the data communication proxy supports a plurality of transmission protocols, so that different service scenes can be met.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on December 27, 2023, with application number 202311828079.2 and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] With the development of technology, communication systems are moving towards higher frequency bands, larger bandwidths, and more densely distributed large-scale antenna arrays, so that a single system can integrate perception and communication capabilities, allowing each system to improve the performance of each other.

[0005] Wireless communication and wireless sensing are both based on electromagnetic wave theory. At the transmitter, electromagnetic wave signals are modulated, carrying information about the source. However, during propagation, these signals are affected by the wireless environment, meaning they are modulated by the environment and thus carry environmental information. By analyzing the electromagnetic wave signals, the receiver can not only obtain the source information but also extract sensory information reflecting the characteristics of the propagation environment. This makes integrated sensing and communication (ISAC) possible. Compared to systems that separate sensing and communication, these systems offer many advantages, including cost savings, reduced device size, lower power consumption, improved spectrum efficiency, and reduced interference between communication and sensing.

[0006] There may be a large amount of perception data in the communication system, but the signaling and data transmission methods of the current communication system are not suitable for transmitting a large amount of perception data. Therefore, how to transmit perception data is an urgent problem to be solved.

[0007] Summary of the Invention

[0008] The embodiments of the present application provide a communication method and apparatus for improving data transmission efficiency.

[0009] In a first aspect, the present application provides a communication method, which can be applied to a data communication agent, or a component configured in a data communication agent (such as a processor, chip, chip system, circuit or other, etc.), or a software module. The data communication agent is deployed in a 3rd generation partnership project (3GPP) network, and the data communication agent supports multiple transmission protocols. The method may include: receiving a first subscription message from a first network element in the 3GPP network, the first subscription message being used to subscribe to data of a first information type; receiving first data from a second network element in the 3GPP network, the first data being data of the first information type; the first data being encapsulated by a first transmission protocol among the multiple transmission protocols; and sending the first data to the first network element.

[0010] Through the above method, data can be directly transmitted based on the data communication agent, improving data transmission efficiency. At the same time, the data communication agent supports multiple transmission protocols to meet different business scenarios.

[0011] In one possible design, the multiple transport protocols include multiple of the following transport protocols: transmission control protocol (TCP), user datagram protocol (UDP), or quick UDP internet connection (QUIC) protocol.

[0012] In one possible design, the first transmission protocol is indicated by the perception service control function network element, which can clarify the encapsulation form of the first data.

[0013] In one possible design, the first network element is a first access network device, and the second network element is a second access network device; or, the first network element is a first core network device, and the second network element is a second core network device; or, the first network element is an access network device, and the second network element is a core network device; or, the first network element is the core network device, and the second network element is the access network device. In other words, both the access network device and the core network device can act as data producers to publish data, and can also act as data consumers to subscribe to data.

[0014] In one possible design, the first network element is a perception data processing function network element, the second network element is an access network device, and the first information type is indicated by the perception service control function network element; or, the first network element is a perception data processing function network element, the second network element is a user plane function network element, and the first information type is indicated by the perception service control function network element; or, the first network element is a network open function network element, the second network element is a perception data processing function network element, and the first information type is indicated by the perception service control function network element. For example, when the first network element is the perception data processing function network element, the perception data processing function network element subscribes to data as a data consumer, and when the second network element is the perception data processing function network element, the perception data processing function network element publishes data as a data producer. The information type of the data subscribed by the data consumer and the information type of the data published by the data producer can be indicated by the perception service control function network element.

[0015] In one possible design, before sending the first data to the first network element, a data request message may be received from the first network element. In this way, after the first network element initiates the data request, the data communication agent may send the first data to the first network element.

[0016] In one possible design, a first message is received, where the first message is used to create a data producer, so that subsequent data producers can publish data.

[0017] In one possible design, the first message may include one or more of the following: the name of the data producer, the adopted transmission protocol, the quality of service (QoS), or the supported data compression algorithm. This can clearly identify the data producer that publishes the data, the transmission protocol used when publishing the data, and the supported data compression methods, so that the data producer can accurately publish the data.

[0018] In one possible design, a second message is received, wherein the second message is used to delete the data producer. In this way, the data producer can be deleted after the service is stopped, which can save resources.

[0019] In one possible design, the second message includes the identifier of the data producer, so that the data producer can be accurately deleted.

[0020] In one possible design, a third message is received, and the third message is used to create a data consumer, so that subsequent data consumers can subscribe to the data.

[0021] In one possible design, the third message may include one or more of the following: a data consumer name, a transmission protocol used, a data consumer group identifier, QoS, or a supported data compression algorithm. This can clearly identify the data consumer subscribing to the data, the transmission protocol used when subscribing to the data, and the supported data compression methods, so that the data consumer can accurately subscribe to the data.

[0022] In one possible design, a fourth message is received, wherein the fourth message is used to delete the data consumer. In this way, the data consumer can be deleted after the service is stopped, which can save resources.

[0023] In one possible design, the fourth message includes an identifier of the data consumer, so that the data consumer can be accurately deleted.

[0024] In a second aspect, the present application provides a communication method, which can be applied to a first network element, or a component configured in the first network element (such as a processor, chip, chip system, circuit or other, etc.), or a software module. The first network element is deployed in a 3GPP network. The method may include: receiving a first control message from a perception service control function network element in the 3GPP network, the first control message being used to indicate receiving data of a first information type; sending a first subscription message to a data communication agent in the 3GPP network, the first subscription message being used to subscribe to data of the first information type; the data communication agent supporting multiple transmission protocols; receiving first data from the data communication agent, the first data being data of the first information type; the first data being encapsulated by a first transmission protocol among the multiple transmission protocols.

[0025] Through this approach, data consumers can subscribe to the data they need directly from the data communication agent without having to interact with the data producer, which improves data transmission efficiency. Furthermore, the data communication agent supports multiple transmission protocols to meet different business scenarios.

[0026] In one possible design, the multiple transport protocols include multiple of the following transport protocols: TCP, UDP or QUIC protocol.

[0027] In one possible design, the first transmission protocol is indicated by the perception service control function network element, which can clarify the encapsulation form of the first data.

[0028] In one possible design, before receiving the first data from the data communication agent, a data request message may be sent to the data communication agent. In this way, the first network element may request data from the data communication agent when there is a data demand.

[0029] In one possible design, a third message is sent to the data communication agent, and the third message is used to create a data consumer, so that subsequent data consumers can subscribe to data.

[0030] In one possible design, the third message may include one or more of the following: a data consumer name, a transmission protocol used, a data consumer group identifier, QoS, or a supported data compression algorithm. This can clearly identify the data consumer subscribing to the data, the transmission protocol used when subscribing to the data, and the supported data compression methods, so that the data consumer can accurately subscribe to the data.

[0031] In one possible design, a first service stop message is received from the perception service control function network element; and a fourth message is sent to the data communication agent, wherein the fourth message is used to delete the data consumer. In this way, deleting the data consumer after the service is stopped can save resources.

[0032] In one possible design, the fourth message includes an identifier of the data consumer, so that the data consumer can be accurately deleted.

[0033] In a third aspect, the present application provides a communication method, which can be applied to a second network element, or a component (such as a processor, chip, chip system, circuit, or other, etc.) configured in the second network element, or a software module. The first network element is deployed in a 3GPP network. The method may include: receiving a second control message from a perception service control function network element in the 3GPP network, the second control message being used to instruct the sending of data of a first information type; sending first data to a data communication agent in the 3GPP network; the first data being data of the first information type; the data communication agent supporting multiple transmission protocols; and the first data being encapsulated in a first transmission protocol among the multiple transmission protocols.

[0034] Through this method, data producers can publish data directly to the data communication agent without interacting with data consumers, which can improve data transmission efficiency. At the same time, the data communication agent supports multiple transmission protocols to meet different business scenarios.

[0035] In one possible design, the multiple transport protocols include multiple of the following transport protocols: TCP, UDP or QUIC protocol.

[0036] In one possible design, the first transmission protocol is indicated by the perception service control function network element, which can clarify the encapsulation form of the first data.

[0037] In one possible design, a first message is sent to the data communication agent, where the first message is used to create a data producer, so that the subsequent data producer can publish data.

[0038] In one possible design, the first message may include one or more of the following: the name of the data producer, the transmission protocol used, the quality of service (QoS), or the supported data compression algorithms. This can clearly identify the data producer that publishes the data, the transmission protocol used when publishing the data, and the supported data compression methods, so that the data producer can accurately publish the data.

[0039] In one possible design, a second service stop message is received from the perception service control function network element; and a second message is sent to the data communication agent, wherein the second message is used to delete the data producer. In this way, deleting the data producer after the service is stopped can save resources.

[0040] In one possible design, the second message includes the identifier of the data producer, so that the data producer can be accurately deleted.

[0041] In a fourth aspect, the present application further provides a communication device, which can be applied to a data communication agent, or a module in a data communication agent (such as a processor, a chip, or a chip system, etc.). The communication device has the function of implementing the above-mentioned first aspect or each possible design example of the first aspect. The function can be implemented by hardware or by executing the corresponding software implementation by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0042] In one possible design, the communication device includes an interface module and a processing module. The interface module supports multiple transmission protocols, and the processing module is used to process information related to data producers and data consumers. These modules can perform the corresponding functions described in the first aspect or various possible design examples of the first aspect. For details, please refer to the detailed description in the method example and are not repeated here.

[0043] In one possible design, the structure of the communication device includes a communication interface and a processor, the communication interface supports multiple transmission protocols, and the processor is used to process relevant information of data producers and data consumers. A memory is optionally included. Specifically, the communication interface is used to send and receive information, and to communicate and interact with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions in the above-mentioned first aspect or each possible design example of the first aspect. The memory is coupled to the processor and stores the necessary program instructions and data for the communication device.

[0044] In a fifth aspect, the present application also provides a communication device, which can be applied to a first network element, or a module in the first network element (such as a processor, a chip, or a chip system, etc.). The communication device has the function of implementing the above-mentioned second aspect or each possible design example of the second aspect. The function can be implemented by hardware or by executing the corresponding software implementation by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0045] In one possible design, the structure of the communication device includes an interface module and a processing module, which can perform the corresponding functions in the above-mentioned second aspect or each possible design example of the second aspect. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0046] In one possible design, the communication device includes a communication interface and a processor, and optionally a memory. The communication interface is used to send and receive information and to communicate and interact with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions described in the second aspect or various possible design examples of the second aspect. The memory is coupled to the processor and stores program instructions and data necessary for the communication device.

[0047] In a sixth aspect, the present application further provides a communication device, which can be applied to a second network element, or a module in the second network element (such as a processor, a chip, or a chip system, etc.). The communication device has the function of implementing the above-mentioned third aspect or each possible design example of the third aspect. The function can be implemented by hardware or by executing the corresponding software through hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0048] In one possible design, the structure of the communication device includes an interface module and a processing module, which can perform the corresponding functions in the above-mentioned third aspect or each possible design example of the third aspect. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0049] In one possible design, the communication device includes a communication interface and a processor, and optionally a memory. The communication interface is used to send and receive information and to communicate and interact with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions described in the third aspect or various possible design examples of the third aspect. The memory is coupled to the processor and stores program instructions and data necessary for the communication device.

[0050] In a seventh aspect, an embodiment of the present application provides a 3GPP network, which may include the above-mentioned data communication agent, the first network element, and the second network element, etc.

[0051] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program or computer-executable instructions. When the computer program or computer-executable instructions are called by a computer, the computer executes the method described in the first aspect of the embodiment of the present application and any possible design thereof, or the method in the second aspect and any possible design thereof, or the method in the third aspect and any possible design thereof. Exemplarily, the computer-readable storage medium can be any available medium that can be accessed by a computer. Taking this as an example but not limited to: the computer-readable medium can include non-transitory computer-readable media, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0052] In the ninth aspect, an embodiment of the present application provides a computer program product, including a computer program or instructions. When the computer program or instructions are run on a computer, the method described in the first aspect or any possible design of the first aspect, or the method in the second aspect or any possible design of the second aspect, or the method in the third aspect or any possible design of the third aspect is executed.

[0053] In the tenth aspect, the present application also provides a chip, including a processor, which is used to execute the method described in the above-mentioned first aspect or any possible design of the first aspect, or the above-mentioned second aspect or any possible design of the second aspect, or the above-mentioned third aspect or any possible design of the third aspect.

[0054] For each of the above-mentioned aspects 4 to 10 and the technical effects that may be achieved by each of the aspects, please refer to the above-mentioned description of the technical effects that can be achieved by the first aspect or various possible solutions in the first aspect, and no further details will be given here. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] FIG1 is a schematic diagram of a perception scenario provided by this application;

[0056] FIG2 is a schematic diagram of data transmission based on DCP provided by this application;

[0057] FIG3 is a schematic diagram of a possible perception architecture in which DCP is introduced in a 3GPP network provided by this application;

[0058] FIG4 is a schematic diagram of a protocol stack for sensing data provided by this application;

[0059] FIG5 is a schematic diagram of another possible perception architecture in which DCP is introduced in a 3GPP network provided by this application;

[0060] FIG6 is a schematic diagram of another protocol stack for sensing data provided by this application;

[0061] FIG7 is a schematic diagram of another protocol stack for sensing data provided by this application;

[0062] FIG8 is a flow chart of a communication method provided by the present application;

[0063] FIG9 is a flow chart of an example of a communication method provided by the present application;

[0064] FIG10 is a flowchart of an example of another communication method provided by the present application;

[0065] FIG11 is a flowchart of an example of another communication method provided by the present application;

[0066] FIG12 is a flowchart of an example of another communication method provided by the present application;

[0067] FIG13 is a schematic structural diagram of a communication device provided by the present application;

[0068] FIG14 is a structural diagram of a communication device provided in this application. DETAILED DESCRIPTION

[0069] The present application will be described in further detail below with reference to the accompanying drawings.

[0070] The embodiments of the present application provide a communication method and apparatus for improving data transmission efficiency. The method and apparatus described in the present application are based on the same technical concept. Since the method and apparatus solve similar problems, the implementation of the apparatus and method can refer to each other, and the repetitive parts will not be repeated.

[0071] To facilitate understanding by those skilled in the art, some terms involved in this application are explained below.

[0072] 1) Wireless Sensing (or Perception)

[0073] Wireless sensing uses wireless signals for sensing. Perception is the process of collecting, processing, and generating sensing results from collected data. For example, collected data can be used to determine the distance, shape, and type of surrounding obstacles, or to determine the breathing rate and heart rate of the monitored subject. The collected data can be collected by sensors or wireless signals.

[0074] Both wireless sensing and wireless communications are based on electromagnetic wave theory. At the transmitter, electromagnetic wave signals are modulated, allowing them to carry information about the source. During propagation, electromagnetic wave signals are affected by the wireless environment, meaning they can also carry environmental information. By analyzing the electromagnetic wave signals, the receiver can not only obtain the source information but also extract sensory information reflecting the characteristics of the propagation environment. In other words, electromagnetic wave signals inherently possess both communication and perception capabilities, making integrated sensing and communication (ISAC) possible. This is also known as joint communications and sensing (JCAS), or simply as integrated synaesthesia. Compared to systems that separate sensing and communication, ISAC offers a range of advantages, including cost savings, reduced device size, lower power consumption, improved frequency efficiency, and reduced interference between communication and sensing.

[0075] 2) Perception scene

[0076] Perception scenarios can be divided into perception scenarios based on access network devices, perception scenarios based on access network devices and terminal devices, and perception scenarios based on terminal devices. For example, the perception scenarios can refer to the perception scenarios shown in (1) to (6) of Figure 1.

[0077] The perception scenario shown in (1) of Figure 1 is based on an access network device, which acts as both the transmitting (TX) and receiving (RX) ends of the perception signal. For example, perception signal 1 sent by the access network device reaches a target object (e.g., a person). After being reflected by the target object, perception signal 1 is received by the access network device as perception signal 2, which is then processed to obtain a perception result.

[0078] The perception scenario shown in (2) of Figure 1 is also based on access network devices. One access network device acts as the transmitter (TX) of the perception signal, and the other access network device acts as the receiver (RX) of the perception signal. For example, perception signal 1 sent by the access network device acting as the TX reaches the target object. After being reflected by the target object, the access network device acting as the RX can receive perception signal 2. The access network device acting as the RX can then process perception signal 2 to obtain a perception result.

[0079] The perception scenario shown in (3) of Figure 1 is based on an access network device and a terminal device. The access network device acts as the transmitter of the perception signal, and the terminal device acts as the receiver of the perception signal. For example, perception signal 1 sent by the access network device reaches the target object. After being reflected by the target object, perception signal 1 is received by the terminal device. The terminal device then processes perception signal 2 to obtain a perception result.

[0080] The perception scenario shown in (4) of Figure 1 is also based on access network devices and terminal devices. The terminal device acts as the transmitter of the perception signal, and the access network device acts as the receiver of the perception signal. For example, perception signal 1 sent by the terminal device reaches the target object. After being reflected by the target object, perception signal 1 is received by the access network device. The access network device then processes perception signal 2 to obtain the perception result.

[0081] The perception scenario shown in (5) of Figure 1 is based on a terminal device, which acts as both the transmitter and receiver of the perception signal. For example, perception signal 1 sent by the terminal device reaches the target object. After being reflected by the target object, perception signal 1 is received by the terminal device as perception signal 2, which is then processed to obtain a perception result.

[0082] The perception scenario shown in (6) of Figure 1 is also a perception scenario based on terminal devices, with one terminal device acting as the transmitter of the perception signal and the other terminal device acting as the receiver of the perception signal. For example, the perception signal 1 sent by the terminal device acting as the TX reaches the target object. After the perception signal 1 is reflected by the target object, the terminal device acting as the RX can receive the perception signal 2. The terminal device acting as the RX can then process the perception signal 2 to obtain the perception result.

[0083] The above-mentioned perception signal 2 can be understood as a reflection signal of the above-mentioned perception signal 1. The perception signal 2 carries more information than the information carried by the perception signal 1. For example, the perception signal 2 can carry source information and environmental information.

[0084] 3) Access network equipment

[0085] Access network equipment is equipment that provides access to terminal devices. Access network equipment can also be referred to as network equipment, access nodes (ANs), or radio access network (RAN) nodes. Access network equipment can include base stations, evolved Node Bs (eNBs or e-NodeBs) in long-term evolution (LTE) systems or long-term evolution-advanced (LTE-A), transmission reception points (TRPs), next-generation NodeBs (gNBs) in fifth-generation (5G) mobile communication systems, next-generation base stations in sixth-generation (6G) mobile communication systems, base stations in future mobile communication systems, or access nodes in wireless local area networks (WiFi) systems. Access network equipment in open radio access networks (ORAN) systems can also be included. Optionally, the access network device may also be a module or unit that performs some of the functions of the base station. For example, the access network device may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU here performs the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and may also perform the functions of the service data adaptation protocol (SDAP); the DU performs the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and may also perform the functions of part of the physical layer or all of the physical layer. In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU can also be called O-CU, DU can also be called open (open, O)-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CUP-UP, and RU can also be called O-RU.

[0086] Exemplarily, the access network device may be a macro base station, a micro base station (also known as a small station), an indoor station, a relay node, a donor node, etc. The access network device may also be a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or home Node B, HNB), a baseband unit (BBU) or a remote radio unit (RRU), or a wireless fidelity (Wifi) access point (AP), or a baseband pool (BBU pool) and RRU in a cloud radio access network (CRAN), etc.

[0087] In this application, the access network device may also be a functional module, a chip or a chip system. Optionally, the functional module, the chip or the chip system may be provided in the access network device.

[0088] The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.

[0089] 4) Terminal equipment

[0090] A terminal device, also known as user equipment (UE), mobile station (MS), or mobile terminal (MT), is a device that provides voice and / or data connectivity to users. For example, a terminal device may include a handheld device or vehicle-mounted device with wireless connectivity. Currently, terminal devices may include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, extended reality (XR) devices, mixed reality (MR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes.

[0091] The terminal device may also be a device-to-device communication (D2D) terminal device, a vehicle-to-everything (V2X) communication terminal device, an intelligent vehicle, a vehicle-to-machine system (or a telematics box, TBOX), a machine-to-machine / machine-type communication (M2M / MTC) terminal device, or an Internet of Things (IoT) terminal device. For example, the terminal device may be a vehicle, ship, or aircraft, or a terminal-type roadside unit, or a communication module or chip built into a vehicle or roadside unit. For example, the terminal device may be a vehicle-mounted module. The terminal device may also be a roadside unit (RSU).

[0092] In this application, the terminal device may also be a functional module, a chip or a chip system. Optionally, the functional module, the chip or the chip system may be provided in the terminal device.

[0093] The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.

[0094] 5) In the description of this application, words such as "first" and "second" are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance or order.

[0095] 6) In the description of this application, "at least one" means one or more, and "more" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or plural.

[0096] 7) In the description of this application, "and / or" describes the relationship between associated objects and indicates that three relationships can exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural. " / " means "or", for example, a / b means a or b.

[0097] With the diversified development of data transmission (such as perceptual data transmission and artificial intelligence (AI) data transmission, etc.), the current signaling or data transmission methods can no longer meet the future data transmission needs. Based on this, in order to improve the efficiency of data transmission, this application considers introducing new network functions in the 3rd generation partnership project (3GPP) network, such as data communication proxy (DCP). It should be understood that DCP is only an example of a name, and DCP can also be replaced by other names. Devices with the same functions as DCP can be regarded as DCP, and this application does not limit this. Among them, DCP can be deployed as an independent network element in the 3GPP network, or it can be co-installed with network elements or devices in the 3GPP network, and this application does not limit this. Optionally, DCP can be deployed in the access network or in the core network, and this application does not limit this.

[0098] For example, Figure 2 illustrates a possible DCP-based data transmission diagram. A data producer sends data to the DCP, such as the topic publish shown in Figure 2. Data consumers can subscribe to and pull data from the DCP. In some embodiments, each data consumer in a group of data consumers can subscribe to data from the DCP, such as the topic subscribe shown in Figure 2.

[0099] DCP can support multiple transport protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), or the Quick UDP Internet Connection (QUIC) protocol or other transport protocols. DCP can include an adapter layer and a distributed message queue (DMQ) to support efficient data distribution. The adapter layer can complete the adaptation of the client's (such as data producer or data consumer) transport protocol (such as TCP, UDP, QUIC transport protocol, etc.), interact directly with the client, and distribute the client's request to the processing thread. DMQ can complete the message exchange function and distribute the messages published by the data producer to the corresponding data consumer. DCP supports the concept of data consumer groups, that is, the same message can only be consumed by one data consumer belonging to the same data consumer group, but can be consumed by different data consumer groups at the same time.

[0100] In some embodiments, the DCP can implement communication with data producers or data consumers through some interfaces. For example, the DCP can create a data producer through the first interface, which can also be understood as the DCP creating a data producer by transmitting messages between the data producer and the data producer through the first interface. When creating a data producer, the DCP can receive the name of the data producer and the adopted transmission protocol (such as TCP, UDP or QUIC) through the first interface. Optionally, the DCP can also receive the quality of service (QoS) and / or supported data compression algorithms through the first interface. When creating a data producer, the DCP can send the identity (ID) of the data producer through the first interface. Optionally, the DCP can also send the selected data compression algorithm through the first interface. Optionally, the DCP can receive one or more of the data producer name, the transmission protocol adopted by the data producer, the QoS, and the data compression algorithms supported by the data producer together or separately. Optionally, the DCP can send the ID of the data producer and / or the data compression algorithm selected by the data producer together or separately.

[0101] For another example, the DCP may delete the data producer through the second interface, which can also be understood as the DCP deleting the data producer by transmitting a message to the data producer through the second interface. When deleting the data producer, the DCP may receive the data producer's ID through the second interface.

[0102] For another example, the DCP may create a data consumer through a third interface, which can also be understood as the DCP creating a data consumer by transmitting messages between the data consumer and the data consumer through the third interface. When creating a data consumer, the DCP may receive one or more of the data consumer name, the adopted transmission protocol (such as TCP, UDP or QUIC) and the data consumer group identifier (ID) through the third interface. Optionally, the DCP may also receive QoS and / or supported data compression algorithms through the third interface. When creating a data consumer, the DCP may also send the data consumer's ID through the third interface. Optionally, the DCP may also send the selected data compression algorithm through the third interface. Optionally, the DCP may receive one or more of the data consumer name, the transmission protocol adopted by the data consumer, QoS, and the data compression algorithm supported by the data consumer together or separately. Optionally, the DCP may send the data consumer's ID and / or the data compression algorithm selected by the data consumer together or separately.

[0103] For another example, the DCP can delete a data consumer through the fourth interface, which can also be understood as the DCP deleting the data producer by transmitting a message between the DCP and the data consumer through the fourth interface. When deleting a data consumer, the DCP can receive the data consumer's ID through the fourth interface.

[0104] For another example, the DCP can implement data subscription through the fifth interface, which can also be understood as the DCP transmitting messages between the data consumer and the data consumer through the fifth interface to implement the data subscription of the data consumer. Among them, when subscribing to data, the DCP can receive the data consumer's ID and information type list through the fifth interface. It should be understood that the information type list is only one form, and the information type list may include at least one information type, and at least one information type may also be carried in the message in other forms, which is not limited in this application. Exemplarily, the information type list may include a topic list. Optionally, the DCP can receive the subscription duration through the fifth interface. Optionally, the DCP can receive the data consumer's ID, information type list and subscription duration together, or it can receive the data consumer's ID and information type list in the first message, and receive the subscription duration in the second message.

[0105] For another example, the DCP can implement data unsubscription via the sixth interface. This can also be understood as the DCP transmitting messages to the data consumer via the sixth interface to enable the data consumer to unsubscribe from the data. During data unsubscription, the DCP can receive the data consumer's ID and information type list via the sixth interface. Alternatively, the DCP can receive the data consumer's ID and information type list together or separately.

[0106] For another example, the DCP can implement data release via the seventh interface. This can also be understood as the DCP transmitting messages to the data producer via the seventh interface to enable the data producer to release the data. When releasing data, the DCP can receive the data producer's ID, information type list, and data via the seventh interface. Alternatively, the DCP can receive one or more of the data producer's ID, information type list, and data together or separately.

[0107] For another example, the DCP can consume data via the eighth interface. This can also be understood as the DCP transmitting messages to the data consumer via the eighth interface to consume data, or as the data consumer extracting data. During data consumption, the DCP can receive the data producer's ID and information type list via the eighth interface. During data consumption, the DCP can send the data required by the consumer via the eighth interface. Optionally, the DCP can receive the data producer's ID and information type list together or separately.

[0108] It should be noted that the aforementioned first to eighth interfaces are merely examples of interface names and may be replaced with other names, which is not limited in this application. Optionally, the first to eighth interfaces may be the same interface, or some of them may be the same interface, which is not limited in this application.

[0109] In one optional manner, the QoS carried in the aforementioned message may be reflected in the message as follows: the QoS value in the message is a first value, such as 0, indicating that the data is delivered at most once; the QoS value in the message is a second value, such as 1, indicating that the data is delivered at least once; and the QoS value in the message is a third value, such as 2, indicating that the data is delivered only once. It should be understood that the above QoS values ​​and meanings are merely illustrative and do not limit this application.

[0110] In one example, the aforementioned supported data compression algorithms may include but are not limited to at least one of the following: GZIP (gnuzip), Lempel-Ziv, Deflate, Delta, LZ4, zstd (zstandard), PPMD, Crook, ZPAQ, CMIX, Deepzip or NNCP, etc.

[0111] DCP supports transport layer security (TLS) for data integrity protection over TCP or QUIC. It also supports datagram transport layer security (DTLS) for data integrity protection over UDP.

[0112] By way of example, in this application, the data producer and data consumer may be different network elements in a 3GPP network, where the different network elements may be of the same type or different types. For example, the data producer may be a first access network device, and the data consumer may be a second access network device. In another example, the data producer may be a first core network device, and the data consumer may be a second core network device. In another example, the data producer may be an access network device, and the data consumer may be a core network device. In another example, the data producer may be a core network device, and the data consumer may be an access network device.

[0113] Optionally, the same network element in the 3GPP network may act as a data consumer in one scenario and as a data producer in another scenario, and this application does not limit this.

[0114] Exemplarily, the transmission mechanism for transmitting data through DCP can be called a data spine, or can be called other names, which is not limited in this application.

[0115] In this application, the data may be perception data or AI data, etc. The following embodiments are described using perception data as an example.

[0116] Based on the above, Figure 3 shows a schematic diagram of a possible perception architecture for a 3GPP network that incorporates the DCP. In this perception architecture, access network devices can be directly connected to the DCP. Access network device 1 acts as a perception source, transmitting perception data directly to the DCP. Access network device 2, after acquiring the perception data from the terminal device, transmits the perception data to the DCP.

[0117] In this sensing architecture, the sensing service control function (SSCF) can be used to implement the control plane functions of sensing services. For example, the SSCF is used to receive sensing capability information from sensing entities and orchestrate sensing services based on the sensing capability information of the sensing entities (including the selection of sensing signal receiving / sending entities). The SSCF can connect to the SBI bus through the service-based interface (SBI) to communicate with other core network elements.

[0118] The Sensing Data Processing Function (SDPF) network element implements the data plane functions of a sensing service. For example, the SDPF processes the sensing data of the sensing service to obtain the sensing results of the sensing service. The SDPF can communicate with other core network elements by attaching to the SBI bus via the SBI, or through separate interfaces, such as with other SDPFs or with the SSCF.

[0119] The data storage function (DSF) network element can store sensing data.

[0120] Among them, the core network elements in the perception structure, such as the access and mobility management function (AMF) network element, the network exposure function (NEF) network element, the policy control function (PCF) network element, the charging function (CHF) network element, the service communication proxy (SCP), the sensing service subscriber management (SSSM) network element, etc. can subscribe to data from the DCP as data consumers, or send data to the DCP as data producers.

[0121] It should be understood that the devices included in the perception architecture shown in Figure 3 are only examples. The perception architecture may also include other devices, or may not include some of the devices shown in Figure 3. This application does not limit this.

[0122] Based on the perception architecture shown in Figure 3, taking the perception data coming from the terminal device as an example, the protocol stack of the perception data can be shown in Figure 4. Among them, the data forwarding protocol (DFP-S) belongs to the data processing protocol, and the main functions of the DFP-S layer include data collection, data processing, data storage, data analysis, data packet header parsing and reorganization, statistical information reporting, data compression or privacy protection, etc. The data spine adapter (DSA) layer is a newly introduced protocol layer. The main function of the DSA layer is message queue adaptation (such as creating data consumers, creating data producers, data publishing, data subscription, data unsubscription, data consumption, etc.). Optionally, DSA can also be replaced by a message queue adapter (MQA), or it can have other names, which is not limited in this application.

[0123] In some embodiments, based on the protocol stack shown in Figure 4, after the RAN node receives the perception data collected by the UE, the RAN node processes the perception data at the DFP-S layer, processes the perception data into a format corresponding to the DSA layer, and sends the perception data in the format corresponding to the DSA layer to the DCP.

[0124] Figure 5 shows a schematic diagram of another possible sensing architecture incorporating DCP in a 3GPP network. In this sensing architecture, sensing data can be transmitted to the DCP via the user plane function (UPF) network element. For example, access network device 1, acting as the sensing source, transmits sensing data to the UPF, which then transmits the sensing data to the DCP. After receiving sensing data from a terminal device, access network device 2 transmits the sensing data to the UPF, which then transmits the sensing data to the DCP.

[0125] Among them, in this perception structure, the functions of the SSCF network element, SDPF network element and DSF network element can be found in the relevant description in the perception architecture shown in Figure 3, and will not be introduced in detail here.

[0126] Similarly, the core network elements in the perception structure, such as AMF network elements, session management function (SMF) network elements, NEF network elements, PCF network elements, CHF, SCP, SSSM, application function (AF) network elements, etc., can subscribe to data from DCP as data consumers, or send data to DCP as data producers.

[0127] It should be understood that the devices included in the perception architecture shown in Figure 5 are only examples. The perception architecture may also include other devices, or may not include some of the devices shown in Figure 5. This application does not limit this.

[0128] Based on the perception architecture shown in Figure 5, taking the perception data originating from a terminal device as an example, in one possible approach, the access network device can transparently transmit the perception data from the terminal device to the UPF, without processing the perception data. In this case, the protocol stack for the perception data can be as shown in Figure 6. The access network device (e.g., RAN node) may not include the DSA layer, while the UPF and DCP include the DSA layer to process the received perception data.

[0129] In some embodiments, after the UE collects the perception data and sends it to the UPF through the RAN node, the UPF processes the format corresponding to the PDU layer of the perception data of the PDU session into the format corresponding to the DSA layer, and sends the perception data in the format corresponding to the DSA layer to the DCP.

[0130] In another possible approach, after receiving the sensing data from the terminal device, the access network device needs to process the sensing data. In this case, the protocol stack of the sensing data may be as shown in FIG7 .

[0131] In some embodiments, after the RAN node receives the perception data collected by the UE, the RAN node processes the perception data at the DFP-S layer and sends the processed perception data to the UPF. The UPF processes the PDU layer corresponding format of the perception data of the PDU session into the DSA layer corresponding format, and sends the perception data in the DSA layer corresponding format to the DCP.

[0132] It should be understood that the access network device can also serve as a source of perception data, that is, the access network device collects perception data. In this case, the protocol stack corresponding to the perception data can be the protocol stack shown in Figure 7 excluding the UE protocol layer and the protocol stack obtained after removing the protocol layer in the column on the left side of the RAN node. It is no longer shown here in the legend.

[0133] The embodiments of the present application can be applied to communication systems evolved after 5G, such as 5G systems and 6G systems, satellite communications, and short-range wireless communication systems. The wireless communication systems mentioned in the embodiments of the present application include, but are not limited to, the three major application scenarios of 5G / 6G systems: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communications (mMTC), long-range LoRa systems, or vehicle-to-vehicle systems. The embodiments of the present application can also be applied to ORAN systems, etc.

[0134] Based on the above description, the communication method provided in the embodiment of the present application is described in detail below. In the following embodiments, the operations performed by a certain device (or network element) can also be performed by a processor of a certain device (or network element), or a chip or chip system, or a functional module. This application only uses the execution of a certain device (or network element) as an example, but does not limit this application.

[0135] For example, FIG8 shows a flow chart of a communication method provided in an embodiment of the present application. The flow of the method may include the following steps:

[0136] S801: A sensing service control function (SSCF) network element in a 3GPP network sends a first control message to a first network element in the 3GPP network, where the first control message is used to instruct receiving data of a first information type. Correspondingly, the first network element receives the first control message from the sensing service control function (SSCF) network element.

[0137] In this application, the data may be perception data or AI data, etc. In the example description of this application, perception data is used as an example. It should be understood that the example description does not serve as a limitation to this application.

[0138] In some implementations, after receiving the awareness service request message from the third-party entity, the awareness service control function SSCF network element may determine an awareness entity associated with the awareness service. For example, the awareness service control function SSCF network element may select the second network element as the awareness entity associated with the awareness service.

[0139] The third-party entity may be an entity that requests the perception service.

[0140] In one implementation, the third-party entity may send the awareness service request message directly to the awareness service control function SSCF network element. In another implementation, the third-party entity may send the awareness service request message to the awareness service control function SSCF network element via the network open function NEF network element.

[0141] Optionally, the first control message may be a first perception control message.

[0142] In one example, the information type may refer to a topic or other topics. Accordingly, the data of the first information type refers to data of a certain topic.

[0143] S802: The first network element sends a first subscription message to the data communication proxy DCP, where the first subscription message is used to subscribe to data of a first information type. Correspondingly, the data communication proxy DCP receives the first subscription message from the first network element.

[0144] In an optional implementation, the first subscription message may include the data consumer's ID and an information type list. For example, the information type list may include a topic list.

[0145] Optionally, the first subscription message may further include subscription duration.

[0146] S803: The Sensing Service Control Function (SSCF) network element sends a second control message to a second network element in the 3GPP network, where the second control message is used to instruct the second network element to send data of the first information type. Correspondingly, the second network element receives the second control message from the Sensing Service Control Function (SSCF) network element.

[0147] Optionally, the second control message may be a second perception control message.

[0148] S804: The second network element sends first data to the data communication proxy DCP. Correspondingly, the data communication proxy DCP receives the first data from the second network element. The first data is data of a first information type and is encapsulated using a first transmission protocol among multiple transmission protocols supported by the data communication proxy DCP.

[0149] Exemplarily, the multiple transmission protocols supported by the data communication proxy DCP may include multiple of the following transmission protocols: TCP, UDP or QUIC protocol, etc.

[0150] Optionally, the first transmission protocol may be indicated by the SSCF network element. For example, the SSCF network element may indicate the first transmission protocol through a second control message, or the SSCF network element may indicate the first transmission protocol through other messages, which is not limited in this application.

[0151] In an optional embodiment, when the second network element sends the first data to the data communication proxy DCP, it may also send the second network element identifier and the first information type to the data communication proxy DCP. It should be understood that the first data, the second network element identifier, and the first information type may be sent via the same message or via different messages, and this application does not limit this.

[0152] S805: The data communication proxy DCP sends first data to the first network element. Correspondingly, the first network element receives the first data from the data communication proxy DCP.

[0153] In an optional implementation, the first network element may be a data consumer, and the second network element may be a data producer. For example, the first network element and the second network element may be the following devices: the first network element is a first access network device, and the second network element is a second access network device; or the first network element is a first core network device, and the second network element is a second core network device; or the first network element is an access network device, and the second network element is a core network device; or the first network element is a core network device, and the second network element is an access network device.

[0154] For example, in a scenario a1, the first network element may be a perception data processing function (SDPF) network element, and the second network element may be an access network device.

[0155] In this scenario a1, the perception data processing function SDPF network element subscribes to data of the first information type from the data communication proxy DCP, and the access network device sends first data of the first information type to the data communication proxy DCP.

[0156] In scenario a1, in one implementation, the terminal device is the source of the perception data. After the access network device obtains the perception data from the terminal device, it sends the first data to the data communication proxy DCP. In another implementation, the access network device is the source of the perception data. After the access network device collects the perception data, it sends the first data to the data communication proxy DCP.

[0157] In a scenario a2, the first network element is a perception data processing function (SDPF) network element, and the second network element is a user plane function (UPF) network element.

[0158] In the scenario a2, the perception data processing function SDPF network element subscribes to data of the first information type from the data communication agent DCP, and the user plane function UPF network element sends first data of the first information type to the data communication agent DCP.

[0159] In this scenario a2, in one implementation, the terminal device is the source of the perception data. After the access network device obtains the perception data from the terminal device, it forwards the perception data to the user plane function UPF network element, and then the user plane function UPF network element sends the first data to the data communication proxy DCP. In another implementation, the terminal device is the source of the perception data. After the access network device obtains the perception data from the terminal device, it processes the perception data and sends the processed perception data to the user plane function UPF network element, and then the user plane function UPF network element sends the first data to the data communication proxy DCP. In yet another implementation, the access network device is the source of the perception data. After the access network device collects the perception data, it sends the perception data to the user plane function UPF network element, and then the user plane function UPF network element sends the first data to the data communication proxy DCP.

[0160] In a scenario a3, the first network element is a network open function NEF network element, and the second network element is a perception data processing function SDPF network element.

[0161] In the scenario a3, the network openness function NEF network element subscribes to data of the first information type from the data communication proxy DCP, and the perception data processing function SDPF network element sends first data of the first information type to the data communication proxy DCP.

[0162] In this scenario a3, the perception data processing function SDPF network element can first subscribe to data of other information types from the data communication agent DCP, process the obtained data of other information types, obtain first data of the first information type, and then send the first data to the data communication agent DCP.

[0163] In each of the aforementioned scenarios, the first information type may be indicated by the Sensing Service Control Function SSCF network element. For example, as mentioned above, the Sensing Service Control Function SSCF network element indicates to the first network element via a first control message and indicates to the second network element via a second control message.

[0164] In an optional implementation, in addition to the method in which the data communication proxy DCP directly sends the first data to the first network element in S805, in one possible method, the data communication proxy DCP receives a data request message from the first network element before directly sending the first data to the first network element. In other words, when the first network element needs data, it can send a data request message to the data communication proxy DCP, and after receiving the data request message from the first network element, the data communication proxy DCP can send the first data to the first network element.

[0165] Optionally, the data request message may include the data consumer's ID and the first information type.

[0166] In some embodiments, the second network element may send a first message to the data communication proxy DCP, where the first message is used to create a data producer. Correspondingly, the data communication proxy DCP may receive the first message from the second network element.

[0167] For example, the first message may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS, or the supported data compression algorithm. Detailed descriptions thereof may be found in the aforementioned related introductions and will not be repeated here.

[0168] Optionally, the second network element may send a first message to the data communication agent DCP when the system starts; or, the second network element may also send a first message to the data communication agent DCP when the perception task starts. For example, the second network element may send a first message to the data communication agent DCP after receiving the second control message.

[0169] The data communication proxy DCP may also send a response message to the first message to the second network element, wherein the response message to the first message may include the identifier of the data producer. Optionally, the response message to the first message may also include a selected data compression algorithm.

[0170] In some embodiments, after receiving the second service stop message from the SSCF network element, the second network element may send a second message to the data communication proxy DCP, where the second message is used to delete the data producer. Accordingly, the data communication proxy DCP receives the second message from the second network element.

[0171] Exemplarily, the second message may include an identifier of a data producer.

[0172] In some embodiments, the first network element may send a third message to the data communication proxy DCP, where the third message is used to create a data consumer. Correspondingly, the data communication proxy DCP may receive the third message from the first network element.

[0173] Exemplarily, the third message may include one or more of the following: a data consumer name, an adopted transmission protocol, a data consumer group identifier, QoS, or a supported data compression algorithm. For detailed descriptions, please refer to the aforementioned related introductions and will not be repeated here.

[0174] Optionally, the first network element may send a third message to the data communication agent DCP when the system starts; or, the first network element may also send a third message to the data communication agent DCP when the perception task starts. For example, the first network element may send a third message to the data communication agent DCP after receiving the first control message.

[0175] The data communication proxy DCP may also send a response message to the third message to the first network element, wherein the response message to the third message may include the identifier of the data consumer. Optionally, the response message to the third message may also include a selected data compression algorithm.

[0176] In some implementations, after receiving the first service stop message from the sensor service control function SSCF network element, the first network element may send a fourth message to the data communication proxy DCP, where the fourth message is used to delete the data consumer. Correspondingly, the data communication proxy DCP receives the fourth message from the first network element.

[0177] Exemplarily, the fourth message may include an identifier of the data consumer.

[0178] The communication method shown in FIG8 can directly transmit data based on the data communication proxy DCP, improving data transmission efficiency. At the same time, the data communication proxy supports multiple transmission protocols to meet different business scenarios. In addition, using the communication method of the present application, data transmission based on the data communication proxy eliminates the need for a binding relationship between data producers and data consumers. The two can be decoupled, making data transmission more flexible.

[0179] Based on the above embodiments, the communication method provided by the present application is described below by way of examples shown in Figures 9 to 12. In the following examples, the data is described as perception data, and the information type is described as a topic.

[0180] For example, FIG9 shows an example of a communication method. In this example, the UE is the source of the perception data. This example corresponds to the perception architecture shown in FIG3 , where the RAN node can be directly connected to the DCP. For example, the example shown in FIG9 may include the following steps:

[0181] S901: The third-party entity sends a perception service request to the SSCF.

[0182] Optionally, the third-party entity may send the service awareness request to the SSCF via the NEF, which is shown as an example in S901 in Figure 9. It should be understood that the third-party entity may send the service awareness request directly to the SSCF.

[0183] In some embodiments, the perception service request may carry one or more of the perception service type, the perception data type of the perception service, or the perception service identifier. Optionally, the perception service type may include, but is not limited to, one or more of the following types: environmental type, monitoring type, imaging type, positioning type, etc. Among them, the environmental type may include, but is not limited to, one or more of the ambient temperature, ambient humidity, air quality, weather conditions, crowd density, traffic density, air pressure, etc. The monitoring type may include, but is not limited to, one or more of the monitoring such as mobile monitoring, intrusion monitoring, fall monitoring, and health monitoring. Mobile monitoring may include, but is not limited to, one or more of the monitoring such as distance monitoring, position monitoring, mobile speed monitoring, and mobile path monitoring. Health monitoring may include, but is not limited to, one or more of the information such as respiratory rate and heartbeat. The imaging type may include, but is not limited to, one or more of medical imaging, 3D map imaging, 3D map construction, building imaging, body temperature imaging, etc.

[0184] Optionally, the perception service request may also include one or more of the following: an identifier of a third-party entity, regional information of the perception service, or perception requirement information of the perception service.

[0185] Illustratively, the third-party entity may be any entity that requests to perceive the service, and this application does not limit the third-party entity.

[0186] S902: The SSCF determines a sensing entity associated with the sensing service.

[0187] For example, the SSCF may select a transmission entity for the sensing data, such as a UE, a RAN node, or an SDPF.

[0188] S903: The SSCF sends a perception control message 1 to the UE. The perception control message 1 is used to instruct the UE to collect perception data.

[0189] In some embodiments, the perception control message 1 may carry one or more of the perception service type, the perception data type of the perception service, the perception service identifier, the area information of the perception service, or the perception demand information of the perception service. For details on the perception service type, please refer to the description in S901.

[0190] Optionally, the information carried in the perception control message 1 may also be sent to the UE through other messages, or determined by the UE through other methods, which is not limited in this application.

[0191] S904: SSCF sends a perception control message 2 to SDPF. Perception control message 2 is used to instruct SDPF to subscribe to the data of topic 1 and publish the data through topic 2 after performing data analysis and processing on the data of topic 1.

[0192] In this case, the SDPF can be both a data consumer and a data producer. When the SDPF is a data consumer, it can subscribe to data in Topic 1, and in this case, the SDPF can correspond to the aforementioned first network element. When the SDPF is a data producer, the SDPF can publish data in Topic 2, and in this case, the SDPF can correspond to the aforementioned second network element.

[0193] S905: The SSCF sends a perception control message 3 to the RAN node. The perception control message 3 is used to instruct the RAN node to publish data of topic 1.

[0194] Exemplarily, the RAN node is a data producer, and the RAN node may correspond to the aforementioned second network element.

[0195] S906: SSCF sends a perception control message 4 to NEF. Perception control message 4 is used to instruct NEF to subscribe to data of topic 2.

[0196] Exemplarily, NEF is a data consumer, and NEF may correspond to the aforementioned first network element.

[0197] It should be understood that the aforementioned sequence of S903-S906 is only an example, and this application does not limit the sequence of S903-S906.

[0198] S907: The RAN node sends message 1 to the DCP. Message 1 is used to create a data producer.

[0199] Message 1 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0200] Exemplarily, the data producer name in message 1 may be a name defined by a RAN node, such as a RAN node name, or may be in other character string formats, or may be in any other format, which is not limited in this application.

[0201] S907 is optional.

[0202] S908: SDPF sends message 2 and message 3 to DCP. Message 2 is used to create a data producer, and message 3 is used to create a data consumer.

[0203] Message 2 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0204] Exemplarily, the data producer name in message 2 may be a name defined by SDPF, such as an SDPF name, or may be in other character string forms, or may be in any other form, which is not limited in this application.

[0205] Message 3 may include one or more of the following: data consumer name, adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0206] Exemplarily, the data consumer name in message 3 may be a name defined by SDPF, such as an SDPF name, or may be in other character string formats, or may be in any other format, which is not limited in this application.

[0207] S908 is optional.

[0208] This application does not limit the order of S907 and S908.

[0209] S909: SDPF sends a subscription message 1 to DCP. Subscription message 1 is for data of topic 1.

[0210] Exemplarily, the subscription message 1 may include the data consumer's ID and a topic list.

[0211] Exemplarily, the data consumer ID included in the subscription message 1 is the data consumer ID returned by the DCP to the SDPF after the SDPF sends the message 3 to the DCP to create the data consumer.

[0212] Optionally, the subscription message 1 may further include the subscription duration.

[0213] S910: NEF sends message 4 to DCP. Message 4 is used to create a data consumer.

[0214] Message 4 may include one or more of the following: data consumer name, adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0215] Exemplarily, the data consumer name in message 4 may be a name defined by NEF, such as an NEF name, or may be in other character string formats, or may be in any other format, which is not limited in this application.

[0216] S910 is optional.

[0217] S911: NEF sends subscription message 2 to DCP. Subscription message 2 is used to subscribe to data of topic 2.

[0218] Exemplarily, the subscription message 2 may include the data consumer's ID and a topic list.

[0219] Exemplarily, the data consumer ID included in the subscription message 2 is the data consumer ID returned by the DCP to the NEF after the NEF sends the message 4 to the DCP to create the data consumer.

[0220] Optionally, the subscription message 2 may also include the subscription duration.

[0221] S912: The UE collects the perception data 1 and sends the perception data 1 to the RAN node.

[0222] Among them, perception data 1 is the data of subject 1.

[0223] S913: The RAN node sends the sensing data 1 to the DCP.

[0224] It should be understood that S912 is described using the example of the RAN node directly forwarding the UE's collected perception data 1 for Topic 1 to the DCP. It should be understood that in another possible approach, after the UE collects the perception data and sends it to the RAN node, the RAN node processes the perception data obtained from the UE to obtain perception data 1 for Topic 1, and then sends the perception data 1 to the DCP.

[0225] Exemplarily, the RAN node may also send the ID of the data producer corresponding to the RAN node and Topic 1 to the DCP.

[0226] The ID of the data producer corresponding to the RAN node may be the ID of the data producer returned by the DCP to the RAN node after the RAN node sends message 1 to the DCP to create the data producer.

[0227] S914: The SDPF sends a data request message 1 to the DCP.

[0228] The data request message 1 may include the ID of the data consumer corresponding to the SDPF and topic 1.

[0229] Exemplarily, the data consumer ID included in the data request message 1 is the data consumer ID returned by the DCP to the SDPF after the SDPF sends the message 3 to the DCP to create the data consumer.

[0230] S914 is optional.

[0231] S915: The DCP sends the sensing data 1 to the SDPF.

[0232] S916: SDPF processes the perception data 1 to obtain perception data 2.

[0233] Perception data 2 is the data of topic 2.

[0234] S917: SDPF sends perception data 2 to DCP.

[0235] S918: The NEF sends a data request message 2 to the DCP.

[0236] The data request message 2 may include the ID of the data consumer corresponding to the NEF and topic 2.

[0237] Exemplarily, the data consumer ID included in the data request message 2 is the data consumer ID returned by the DCP to the NEF after the NEF sends the message 4 to the DCP to create the data consumer.

[0238] S918 is optional.

[0239] S919: The DCP sends the sensing data 2 to the NEF.

[0240] S920: The NEF sends the sensing data 2 to the third-party entity.

[0241] S921: SSCF sends a perception service stop message 1 to the UE.

[0242] S922: SSCF sends a perception service stop message 2 to the RAN node.

[0243] S923: SSCF sends a perception service stop message 3 to SDPF.

[0244] S924: SSCF sends a perception service stop message 4 to NEF.

[0245] This application does not limit the order of the above S921-S924.

[0246] The above S921-S924 are optional.

[0247] S925: The RAN node sends message 5 to the DCP. Message 5 is used to delete the data producer.

[0248] The message 5 may include an identification of the data producer.

[0249] S926: SDPF sends message 6 and message 7 to DCP. Message 6 is used to delete the data producer, and message 7 is used to delete the consumer.

[0250] The message 6 may include an identification of the data producer.

[0251] The message 7 may include an identification of the data consumer.

[0252] S927: NEF sends message 8 to DCP. Message 8 is used to delete the data consumer.

[0253] The message 8 may include an identification of the data consumer.

[0254] Among them, the order of S925-S927 is not limited in this application.

[0255] The above S925-S927 are optional.

[0256] It should be understood that the steps of data producer creation and data consumer creation in this application may also be executed when the system starts, or the steps of data producer creation and data consumer creation may not be executed, and this application does not limit this.

[0257] In the example shown in FIG9 , the RAN node is directly connected to the DCP. Based on the DCP, the perception data can be directly published and subscribed without the need for binding between the data producer and the data consumer, thereby improving data transmission efficiency.

[0258] For example, Figure 10 illustrates another communication method. In this example, the UE is the source of perception data, and the RAN node can transparently transmit the UE's perception data. This example corresponds to the perception architecture shown in Figure 5, where the RAN node is connected to the DCP via the UPF. For example, the example shown in Figure 10 may include the following steps:

[0259] S1001: A third-party entity sends a perception service request to the SSCF.

[0260] Optionally, the third-party entity may send a service awareness request to the SSCF via the NEF, which is shown as an example in S1001 in Figure 10. It should be understood that the third-party entity may send a service awareness request directly to the SSCF.

[0261] Optionally, the relevant description of the perception service request can be found in the description involved in the aforementioned S901, which will not be repeated here.

[0262] S1002: The SSCF determines a sensing entity associated with the sensing service.

[0263] For example, the SSCF may select a transmission entity for the sensing data, such as UE, UPF, SDPF, etc.

[0264] S1003: The SSCF sends a perception control message 1 to the UE. The perception control message 1 is used to instruct the UE to collect perception data.

[0265] Optionally, for the relevant description of the perception control message 1, please refer to the description involved in the aforementioned S903, which will not be repeated here.

[0266] S1004: SSCF sends a perception control message 2 to SDPF. Perception control message 2 is used to instruct SDPF to subscribe to the data of topic 1, and to publish the data through topic 2 after performing data analysis and processing on the data of topic 1.

[0267] In this case, the SDPF can be both a data consumer and a data producer. When the SDPF is a data consumer, it can subscribe to data in Topic 1, and in this case, the SDPF can correspond to the aforementioned first network element. When the SDPF is a data producer, the SDPF can send data in Topic 2, and in this case, the SDPF can correspond to the aforementioned second network element.

[0268] S1005: SSCF sends perception control message 3 to UPF, where perception control message 3 is used to instruct UPF to send data of topic 1.

[0269] Exemplarily, UPF is a data producer, and UPF may correspond to the aforementioned second network element.

[0270] S1006: SSCF sends a perception control message 4 to NEF. Perception control message 4 is used to instruct NEF to subscribe to data of topic 2.

[0271] Exemplarily, NEF is a data consumer, and NEF may correspond to the aforementioned first network element.

[0272] It should be understood that the aforementioned order of S1003-S1006 is only an example, and this application does not limit the order of S1003-S1006.

[0273] S1007: UPF sends message 1 to DCP. Message 1 is used to create a data producer.

[0274] Message 1 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0275] Exemplarily, the data producer name in message 1 may be a name defined by UPF, such as a UPF name, or may be in other character string forms, or may be in any other form, which is not limited in this application.

[0276] S1007 is optional.

[0277] S1008: SDPF sends message 2 and message 3 to DCP. Message 2 is used to create a data producer, and message 3 is used to create a data consumer.

[0278] Message 2 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0279] Message 3 may include one or more of the following: data consumer name, adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0280] Similarly, the data producer name in message 2 and the data consumer name in message 3 can refer to the relevant description involved in the example shown in Figure 9, and will not be repeated here.

[0281] S1008 is optional.

[0282] This application does not limit the order of S1007 and S1008.

[0283] S1009: SDPF sends a subscription message 1 to DCP. Subscription message 1 is for data of topic 1.

[0284] Exemplarily, the subscription message 1 may include the data consumer's ID and a topic list.

[0285] Similarly, the ID of the data consumer in the subscription message 1 can be found in the relevant description in the example shown in FIG9 , which will not be repeated here.

[0286] Optionally, the subscription message 1 may further include the subscription duration.

[0287] S1010: NEF sends message 4 to DCP. Message 4 is used to create a data consumer.

[0288] Message 4 may include one or more of the following: data consumer name (see the relevant description in the example shown in FIG. 9 ), adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0289] S1010 is optional.

[0290] S1011: NEF sends a subscription message 2 to DCP. Subscription message 2 is used to subscribe to data of topic 2.

[0291] Exemplarily, the subscription message 2 may include the ID of the data consumer (see the relevant description in the example shown in FIG9 ) and a topic list.

[0292] Optionally, the subscription message 2 may also include the subscription duration.

[0293] S1012: The UE collects the perception data 1 and sends the perception data 1 to the UPF through the RAN node.

[0294] Among them, perception data 1 is the data of subject 1.

[0295] S1013: UPF sends perception data 1 to DCP.

[0296] It should be understood that S1012 is described using the example of the UE collecting perception data 1 of Topic 1 and forwarding it directly to the DCP via the RAN node and the UPF. It should be understood that in another possible approach, after the UE collects perception data and sends it to the UPF via the RAN node, the UPF processes the acquired perception data to obtain perception data 1 of Topic 1, and then sends perception data 1 to the DCP.

[0297] Exemplarily, the UPF may also send the ID of the data producer corresponding to the UPF and topic 1 to the DCP.

[0298] Among them, the ID of the data producer corresponding to the UPF can be the ID of the data producer returned by the DCP to the UPF after the UPF sends message 1 to the DCP to create the data producer.

[0299] S1014: The SDPF sends a data request message 1 to the DCP.

[0300] The data request message 1 may include the ID of the data consumer corresponding to the SDPF (see the relevant description in the example shown in FIG9 ) and topic 1 .

[0301] S1014 is optional.

[0302] S1015: DCP sends perception data 1 to SDPF.

[0303] S1016: SDPF processes the perception data 1 to obtain perception data 2.

[0304] Perception data 2 is the data of topic 2.

[0305] S1017: SDPF sends perception data 2 to DCP.

[0306] S1018: The NEF sends a data request message 2 to the DCP.

[0307] The data request message 2 may include the ID of the data consumer corresponding to the NEF (see the relevant description in the example shown in FIG9 ) and topic 2 .

[0308] S1018 is optional.

[0309] S1019: DCP sends perception data 2 to NEF.

[0310] S1020: The NEF sends the sensing data 2 to the third-party entity.

[0311] S1021: SSCF sends a perception service stop message 1 to the UE.

[0312] S1022: SSCF sends a perception service stop message 2 to UPF.

[0313] S1023: SSCF sends a perception service stop message 3 to SDPF.

[0314] S1024: SSCF sends a perception service stop message 4 to NEF.

[0315] This application does not limit the order of the above S1021-S1024.

[0316] The above S1021-S1024 are optional.

[0317] S1025: UPF sends message 5 to DCP. Message 5 is used to delete the data producer.

[0318] The message 5 may include an identification of the data producer.

[0319] S1026: SDPF sends message 6 and message 7 to DCP. Message 6 is used to delete the data producer, and message 7 is used to delete the consumer.

[0320] The message 6 may include an identification of the data producer.

[0321] The message 7 may include an identification of the data consumer.

[0322] S1027: NEF sends message 8 to DCP. Message 8 is used to delete the data consumer.

[0323] The message 8 may include an identification of the data consumer.

[0324] Among them, the order of S1025-S1027 is not limited in this application.

[0325] The above S1025-S1027 are optional.

[0326] It should be understood that the steps of data producer creation and data consumer creation in this application may also be executed when the system starts, or the steps of data producer creation and data consumer creation may not be executed, and this application does not limit this.

[0327] In the example shown in FIG10 , the perception data can be directly published and subscribed based on DCP without the need for binding between data producers and data consumers, thereby improving data transmission efficiency.

[0328] For example, Figure 11 illustrates another communication method. In this example, the UE is the source of perception data. After the RAN node obtains the UE's perception data, it processes the perception data. This example corresponds to the perception architecture shown in Figure 5 , where the RAN node is connected to the DCP via the UPF. For example, the example shown in Figure 11 may include the following steps:

[0329] S1101: A third-party entity sends a perception service request to the SSCF.

[0330] Optionally, the third-party entity may send a service awareness request to the SSCF via the NEF, which is shown as an example in S1101 in Figure 11. It should be understood that the third-party entity may send a service awareness request directly to the SSCF.

[0331] Optionally, the relevant description of the perception service request can be found in the description involved in the aforementioned S901, which will not be repeated here.

[0332] S1102: The SSCF determines a sensing entity associated with the sensing service.

[0333] For example, the SSCF may select a transmission entity for the sensing data, such as a UE, a RAN node, a UPF, or a SDPF.

[0334] S1103: The SSCF sends a perception control message 1 to the UE. The perception control message 1 is used to instruct the UE to collect perception data.

[0335] Optionally, for the relevant description of the perception control message 1, please refer to the description involved in the aforementioned S903, which will not be repeated here.

[0336] S1104: The SSCF sends a perception control message 2 to the RAN node. The perception control message 2 is used to instruct the RAN node to process the perception data.

[0337] S1105: SSCF sends a perception control message 3 to SDPF. Perception control message 3 is used to instruct SDPF to subscribe to the data of topic 1, and to publish the data through topic 2 after performing data analysis and processing on the data of topic 1.

[0338] In this case, the SDPF can be both a data consumer and a data producer. When the SDPF is a data consumer, it can subscribe to data in Topic 1, and in this case, the SDPF can correspond to the aforementioned first network element. When the SDPF is a data producer, the SDPF can send data in Topic 2, and in this case, the SDPF can correspond to the aforementioned second network element.

[0339] S1106: SSCF sends perception control message 4 to UPF. Perception control message 4 is used to instruct UPF to send data of topic 1.

[0340] Exemplarily, UPF is a data producer, and UPF may correspond to the aforementioned second network element.

[0341] S1107: SSCF sends a perception control message 5 to NEF. Perception control message 5 is used to instruct NEF to subscribe to data of topic 2.

[0342] Exemplarily, NEF is a data consumer, and NEF may correspond to the aforementioned first network element.

[0343] It should be understood that the aforementioned order of S1103-S1107 is only an example, and this application does not limit the order of S1103-S1107.

[0344] S1108: UPF sends message 1 to DCP. Message 1 is used to create a data producer.

[0345] Message 1 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0346] S1108 is optional.

[0347] S1109: SDPF sends message 2 and message 3 to DCP. Message 2 is used to create a data producer, and message 3 is used to create a data consumer.

[0348] Message 2 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0349] Message 3 may include one or more of the following: data consumer name, adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0350] S1109 is optional.

[0351] This application does not limit the order of S1108 and S1109.

[0352] S1110: SDPF sends a subscription message 1 to DCP. Subscription message 1 is for data of topic 1.

[0353] Exemplarily, the subscription message 1 may include the data consumer's ID and a topic list.

[0354] Optionally, the subscription message 1 may further include the subscription duration.

[0355] S1111: NEF sends message 4 to DCP. Message 4 is used to create a data consumer.

[0356] Message 4 may include one or more of the following: data consumer name, adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0357] S1111 is optional.

[0358] S1112: NEF sends subscription message 2 to DCP. Subscription message 2 is used to subscribe to data of topic 2.

[0359] Exemplarily, the subscription message 2 may include the data consumer's ID and a topic list.

[0360] Optionally, the subscription message 2 may also include the subscription duration.

[0361] S1113: The UE collects perception data 1 and sends the perception data 1 to the RAN node.

[0362] S1114: The RAN node processes the perception data 1 to obtain perception data 2.

[0363] Among them, the processing of the perception data 1 by the RAN node can be point cloud data processing, etc., which is not limited in this application.

[0364] S1115: The RAN node sends the perception data 2 to the UPF.

[0365] S1116: UPF sends perception data 3 to DCP.

[0366] Among them, perception data 3 is the data of topic 1.

[0367] Optionally, the perception data 3 and the perception data 2 may be the same data, that is, the UPF does not process the data. The perception data 3 may also be the perception data obtained by the UPF performing data processing on the perception data 2. This application does not limit this.

[0368] Exemplarily, the UPF may also send the ID of the data producer corresponding to the UPF and topic 1 to the DCP.

[0369] S1117: The SDPF sends a data request message 1 to the DCP.

[0370] The data request message 1 may include the ID of the data consumer corresponding to the SDPF and topic 1.

[0371] S1117 is optional.

[0372] S1118: DCP sends perception data 3 to SDPF.

[0373] S1119: SDPF processes perception data 3 to obtain perception data 4.

[0374] Perception data 4 is the data of topic 2.

[0375] S1120: SDPF sends perception data 4 to DCP.

[0376] S1121: NEF sends a data request message 2 to DCP.

[0377] The data request message 2 may include the ID of the data consumer corresponding to the NEF and topic 2.

[0378] S1121 is optional.

[0379] S1122: DCP sends perception data 4 to NEF.

[0380] S1123: NEF sends the sensing data 4 to the third-party entity.

[0381] Optionally, after step 1123, similar operations as those in S1021-S1027 mentioned above may also be performed in this example. Please refer to the above description, which will not be repeated here and is not shown in Figure 11.

[0382] It should be understood that the steps of data producer creation and data consumer creation in this application may also be executed when the system starts, or the steps of data producer creation and data consumer creation may not be executed, and this application does not limit this.

[0383] In the example shown in FIG11 , the relevant descriptions of the data producer name, data consumer name, data producer ID, and data consumer ID can refer to the similar descriptions involved in the example shown in FIG10 , and are not repeated in this example.

[0384] In the example shown in FIG11 , the perception data can be directly published and subscribed based on DCP without the need for binding between data producers and data consumers, thereby improving data transmission efficiency.

[0385] For example, Figure 12 shows another example of a communication method. In this example, the RAN node is the source of the perception data. This example corresponds to the perception architecture shown in Figure 5, where the RAN node is connected to the DCP via the UPF. For example, the example shown in Figure 12 may include the following steps:

[0386] S1201: The third-party entity sends a perception service request to the SSCF.

[0387] Optionally, the third-party entity may send a service awareness request to the SSCF via the NEF, which is shown as an example in S1201 in Figure 12. It should be understood that the third-party entity may send a service awareness request directly to the SSCF.

[0388] Optionally, the relevant description of the perception service request can be found in the description involved in the aforementioned S901, which will not be repeated here.

[0389] S1202: The SSCF determines a sensing entity associated with the sensing service.

[0390] For example, the SSCF may select a transmission entity for the sensing data, such as a RAN node, UPF, SDPF, etc.

[0391] S1203: The SSCF sends a perception control message 1 to the RAN node. The perception control message 1 is used to instruct the RAN node to collect perception data.

[0392] Optionally, the description related to the perception control message 1 is similar to the content of the perception control message 1 involved in the aforementioned S903, and they can refer to each other and will not be repeated here.

[0393] S1204: SSCF sends a perception control message 2 to SDPF. Perception control message 2 is used to instruct SDPF to subscribe to the data of topic 1 and publish the data through topic 2 after performing data analysis and processing on the data of topic 1.

[0394] In this case, the SDPF can be both a data consumer and a data producer. When the SDPF is a data consumer, it can subscribe to data in Topic 1, and in this case, the SDPF can correspond to the aforementioned first network element. When the SDPF is a data producer, the SDPF can send data in Topic 2, and in this case, the SDPF can correspond to the aforementioned second network element.

[0395] S1205: SSCF sends perception control message 3 to UPF. Perception control message 3 is used to instruct UPF to publish data of topic 1.

[0396] Exemplarily, UPF is a data producer, and UPF may correspond to the aforementioned second network element.

[0397] S1206: SSCF sends a perception control message 4 to NEF. Perception control message 4 is used to instruct NEF to subscribe to data of topic 2.

[0398] Exemplarily, NEF is a data consumer, and NEF may correspond to the aforementioned first network element.

[0399] It should be understood that the aforementioned order of S1203-S1206 is only an example, and this application does not limit the order of S1203-S1206.

[0400] S1207: UPF sends message 1 to DCP. Message 1 is used to create a data producer.

[0401] Message 1 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0402] S1207 is optional.

[0403] S1208: SDPF sends message 2 and message 3 to DCP. Message 2 is used to create a data producer, and message 3 is used to create a data consumer.

[0404] Message 2 may include one or more of the following: the name of the data producer, the adopted transmission protocol, QoS or supported data compression algorithm.

[0405] Message 3 may include one or more of the following: data consumer name, adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0406] S1208 is optional.

[0407] This application does not limit the order of S1207 and S1208.

[0408] S1209: SDPF sends a subscription message 1 to DCP. Subscription message 1 is for data of topic 1.

[0409] Exemplarily, the subscription message 1 may include the data consumer's ID and a topic list.

[0410] Optionally, the subscription message 1 may further include the subscription duration.

[0411] S1210: NEF sends message 4 to DCP. Message 4 is used to create a data consumer.

[0412] Message 4 may include one or more of the following: data consumer name, adopted transmission protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0413] S1210 is optional.

[0414] S1211: NEF sends subscription message 2 to DCP. Subscription message 2 is used to subscribe to data of topic 2.

[0415] Exemplarily, the subscription message 2 may include the data consumer's ID and a topic list.

[0416] Optionally, the subscription message 2 may also include the subscription duration.

[0417] S1212: The RAN node collects the sensing data 1 and sends the sensing data 1 to the UPF.

[0418] Among them, perception data 1 is the data of subject 1.

[0419] S1213: UPF sends perception data 1 to DCP.

[0420] It should be understood that S1212 is described using the example of a RAN node collecting perception data 1 of Topic 1 and forwarding it to the DCP via the UPF. It should be understood that in another possible approach, after the RAN node collects the perception data and sends it to the UPF, the UPF processes the acquired perception data to obtain perception data 1 of Topic 1, and then sends the perception data 1 to the DCP.

[0421] Exemplarily, the UPF may also send the ID of the data producer corresponding to the UPF and topic 1 to the DCP.

[0422] S1214: The SDPF sends a data request message 1 to the DCP.

[0423] The data request message 1 may include the ID of the data consumer corresponding to the SDPF and topic 1.

[0424] S1214 is optional.

[0425] S1215: DCP sends perception data 1 to SDPF.

[0426] S1216: SDPF processes perception data 1 to obtain perception data 2.

[0427] Perception data 2 is the data of topic 2.

[0428] S1217: SDPF sends perception data 2 to DCP.

[0429] S1218: The NEF sends a data request message 2 to the DCP.

[0430] The data request message 2 may include the ID of the data consumer corresponding to the NEF and topic 2.

[0431] S1218 is optional.

[0432] S1219: DCP sends perception data 2 to NEF.

[0433] S1220: The NEF sends the sensing data 2 to the third-party entity.

[0434] Optionally, after S1220, similar operations as those in S1021-S1027 mentioned above may also be performed in this example. Please refer to the above description, which will not be repeated here and is not shown in Figure 11.

[0435] It should be understood that the steps of data producer creation and data consumer creation in this application may also be executed when the system starts, or the steps of data producer creation and data consumer creation may not be executed, and this application does not limit this.

[0436] In the example shown in FIG12 , the relevant descriptions of the data producer name, data consumer name, data producer ID, and data consumer ID can refer to the similar descriptions involved in the example shown in FIG10 , and are not repeated in this example.

[0437] In the example shown in FIG12 , the perception data can be directly published and subscribed based on DCP without the need for binding between data producers and data consumers, thereby improving data transmission efficiency.

[0438] Based on the above embodiments, embodiments of the present application further provide a communication device. Referring to FIG. 13 , the communication device 1300 may include an interface module 1301 and a processing module 1302. The interface module 1301 may be used to send and receive information, among other things. The processing module 1302 may control and manage the operations of the communication device 1300. The processing module 1302 may also control the operations performed by the interface module 1301.

[0439] Exemplarily, the communication device 1300 may be a data communication agent in the above-mentioned embodiments (such as the DCP in Figures 9 to 12), a processor of the data communication agent, or a chip, or a chip system, or a functional module, etc. Alternatively, the communication device 1300 may also be the first network element in the above-mentioned embodiments (such as the network element as a data consumer in Figures 9 to 12), a processor of the first network element, or a chip, or a chip system, or a functional module, etc. Alternatively, the communication device 1300 may also be the second network element in the above-mentioned embodiments (such as the network element as a data producer in Figures 9 to 12), a processor of the second network element, or a chip, or a chip system, or a functional module, etc.

[0440] In one embodiment, when the communication device 1300 is used to implement the functions of the data communication agent in the above-mentioned embodiment, the interface module 1301 supports multiple transmission protocols, and the processing module 1302 is used to process relevant information of data producers and data consumers. Specifically, the interface module 1301 may be used to receive a first subscription message from a first network element in the 3GPP network, where the first subscription message is used to subscribe to data of a first information type; receive first data from a second network element in the 3GPP network, where the first data is data of the first information type; the first data is encapsulated in a first transmission protocol among the multiple transmission protocols; and send the first data to the first network element. The processing module 1302 may be used to control the sending and receiving operations of the interface module 1301.

[0441] Exemplarily, the multiple transport protocols include multiple of the following transport protocols: TCP, UDP or QUIC protocol.

[0442] In one possible approach, the first transmission protocol is indicated by a perception service control function network element.

[0443] In an optional embodiment, the first network element is a first access network device, and the second network element is a second access network device; or, the first network element is a first core network device, and the second network element is a second core network device; or, the first network element is an access network device, and the second network element is a core network device; or, the first network element is the core network device, and the second network element is the access network device.

[0444] For example, the first network element is a perception data processing function network element, the second network element is an access network device, and the first information type is indicated by the perception service control function network element; or, the first network element is a perception data processing function network element, the second network element is a user plane function network element, and the first information type is indicated by the perception service control function network element; or, the first network element is a network open function network element, the second network element is a perception data processing function network element, and the first information type is indicated by the perception service control function network element.

[0445] Optionally, the interface module 1301 may also be configured to: receive a data request message from the first network element before sending the first data to the first network element.

[0446] In an example, the interface module 1301 may also be used to receive a first message, where the first message is used to create a data producer.

[0447] Exemplarily, the first message may include one or more of the following: a data producer name, an adopted transmission protocol, a quality of service QoS, or a supported data compression algorithm.

[0448] In some embodiments, the interface module 1301 may also be used to receive a second message, where the second message is used to delete the data producer.

[0449] For example, the second message includes the identifier of the data producer.

[0450] In some embodiments, the interface module 1301 may also be configured to receive a third message, where the third message is used to create a data consumer.

[0451] The third message may include one or more of the following: a data consumer name, an adopted transmission protocol, a data consumer group identifier, a quality of service level QoS, or a supported data compression algorithm.

[0452] In some embodiments, the interface module 1301 may also be used to receive a fourth message, where the fourth message is used to delete a data consumer.

[0453] Optionally, the fourth message includes an identifier of the data consumer.

[0454] In another embodiment, when the communication device 1300 is used to implement the functions of the first network element in the above embodiment, it may include: an interface module 1301 may be used to receive a first control message from a perception service control function network element in the 3GPP network, the first control message being used to instruct reception of data of a first information type; send a first subscription message to a data communication agent in the 3GPP network, the first subscription message being used to subscribe to data of the first information type; the data communication agent supporting multiple transmission protocols; and receive first data from the data communication agent, the first data being data of the first information type; the first data being encapsulated in a first transmission protocol among the multiple transmission protocols. A processing module 1302 may be used to control the sending and receiving operations of the interface module 1301.

[0455] Exemplarily, the multiple transport protocols include multiple of the following transport protocols: TCP, UDP or QUIC protocol.

[0456] Optionally, the first transmission protocol is indicated by the perception service control function network element.

[0457] In a possible manner, the interface module 1301 may also be configured to: before receiving the first data from the data communication agent, send a data request message to the data communication agent.

[0458] In an example, the interface module 1301 may also be configured to send a third message to the data communication agent, where the third message is used to create a data consumer.

[0459] Exemplarily, the third message may include one or more of the following: a data consumer name, an adopted transmission protocol, a data consumer group identifier, a quality of service QoS, or a supported data compression algorithm.

[0460] In an example, the interface module 1301 can also be used to receive a first service stop message from the perception service control function network element; and send a fourth message to the data communication agent, where the fourth message is used to delete the data consumer.

[0461] Optionally, the fourth message includes an identifier of the data consumer.

[0462] In another embodiment, when the communication device 1300 is used to implement the functions of the second network element in the above embodiment, it may include: an interface module 1301 may be used to receive a second control message from a perception service control function network element in the 3GPP network, the second control message being used to instruct the transmission of data of a first information type; send first data to a data communication agent in the 3GPP network; the first data being data of the first information type; the data communication agent supporting multiple transmission protocols; and the first data being encapsulated in a first transmission protocol among the multiple transmission protocols. A processing module 1302 may be used to control the transmission and reception operations of the interface module 1301.

[0463] Exemplarily, the multiple transport protocols include multiple of the following transport protocols: TCP, UDP or QUIC protocol.

[0464] Optionally, the first transmission protocol is indicated by the perception service control function network element.

[0465] In a possible manner, the interface module 1301 may also be used to send a first message to the data communication agent, where the first message is used to create a data producer.

[0466] Exemplarily, the first message includes one or more of the following: a data producer name, an adopted transmission protocol, a quality of service QoS, or a supported data compression algorithm.

[0467] In one possible manner, the interface module 1301 may also be used to receive a second service stop message from the perception service control function network element; and send a second message to the data communication agent, where the second message is used to delete the data producer.

[0468] Optionally, the second message includes an identifier of the data producer.

[0469] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. The functional units in the embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0470] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the contributing part or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0471] Based on the above embodiments, the present application also provides a communication device. Referring to FIG14 , the communication device 1400 may include a communication interface 1401 and a processor 1402. Optionally, the communication device 1400 may further include a memory 1403. The memory 1403 may be disposed inside the communication device 1400 or outside the communication device 1400. The processor 1402 may control the communication interface 1401 to receive and send signals, messages, information, or data.

[0472] Optionally, the communication interface 1401 may be a transceiver, which may include a transmitter and / or a receiver. The transmitter is used to transmit signals, messages, information, or data. The receiver is used to receive signals, messages, information, or data. Exemplarily, the transmitter transmits signals, messages, information, or data under the control of the processor 1402. The receiver receives signals, messages, information, or data under the control of the processor 1402.

[0473] Specifically, the processor 1402 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 1402 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0474] The communication interface 1401, the processor 1402, and the memory 1403 are interconnected. Optionally, the communication interface 1401, the processor 1402, and the memory 1403 are interconnected via a bus 1404; the bus 1404 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, FIG14 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0475] In an optional embodiment, the memory 1403 is used to store programs, etc. Specifically, the programs may include program code, which includes computer operating instructions. The memory 1403 may include RAM, or may also include non-volatile memory (non-volatile memory), such as one or more disk storage devices. The processor 1402 executes the application stored in the memory 1403 to implement the above functions, thereby realizing the functions of the communication device 1400.

[0476] Exemplarily, the communication device 1400 may be the data communication agent in the above embodiment, or the first network element, the second network element, etc. Alternatively, the communication device 1400 may be a chip, etc.

[0477] In one embodiment, when the communication device 1400 implements the data communication agent function in the above-described embodiment, the communication interface 1401 may implement the transceiver operations performed by the data communication agent in the above-described embodiment; and the processor 1402 may implement other operations performed by the data communication agent in the above-described embodiment in addition to the transceiver operations. Specific details can be found in the description of the above-described embodiment and will not be detailed here.

[0478] In another embodiment, when the communication device 1400 implements the functions of the first network element in the above embodiment, the communication interface 1401 may implement the transceiver operations performed by the first network element in the above embodiment; and the processor 1402 may implement other operations performed by the first network element in the above embodiment in addition to the transceiver operations. For specific details, please refer to the relevant descriptions in the above embodiment and will not be described in detail here.

[0479] In another embodiment, when the communication device 1400 implements the functions of the second network element in the above embodiment, the communication interface 1401 may implement the transceiver operations performed by the second network element in the above embodiment; and the processor 1402 may implement other operations performed by the second network element in the above embodiment in addition to the transceiver operations. For specific related descriptions, please refer to the relevant descriptions in the above embodiment and will not be described in detail here.

[0480] Based on the above embodiments, an embodiment of the present application provides a 3GPP network, which may include the data communication agent, the first network element, and the second network element involved in the above embodiments.

[0481] An embodiment of the present application also provides a computer-readable storage medium, which is used to store a computer program or computer-executable instructions. When the computer program or computer-executable instructions are executed by a computer, the computer can implement a communication method provided by the above method embodiment.

[0482] An embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a computer, the computer can implement a communication method provided by the above method embodiment.

[0483] An embodiment of the present application also provides a chip, including a processor, wherein the processor is used to enable the chip to implement a communication method provided by the above method embodiment.

[0484] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0485] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0486] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0487] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0488] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A communication method, characterized in that, Applied to a data communication agent, the data communication agent is deployed in a 3rd Generation Partnership Project (3GPP) network, and the data communication agent supports multiple transport protocols, including: Receiving a first subscription message from a first network element in the 3GPP network, the first subscription message being used to subscribe to data of a first information type; Receiving first data from a second network element in the 3GPP network, the first data being data of the first information type; the first data is encapsulated by a first transport protocol among the multiple transport protocols; Sending the first data to the first network element.

2. The method according to claim 1, wherein: The first network element is a first access network device, and the second network element is a second access network device; or The first network element is a first core network device, and the second network element is a second core network device; or The first network element is an access network device, and the second network element is a core network device; or The first network element is the core network device, and the second network element is the access network device.

3. The method according to claim 1 or 2, wherein: The first network element is a sensing data processing function network element, the second network element is an access network device, and the first information type is indicated by a sensing service control function network element; or The first network element is a sensing data processing function network element, the second network element is a user plane function network element, and the first information type is indicated by a sensing service control function network element; or The first network element is a network exposure function network element, the second network element is a sensing data processing function network element, and the first information type is indicated by the sensing service control function network element.

4. The method according to any one of claims 1 to 3, characterized in that, Before sending the first data to the first network element, the method further includes: Receiving a data request message from the first network element.

5. The method according to any one of claims 1-4, characterized in that The method further includes: Receiving a first message, the first message being used to create a data producer.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receiving a second message, the second message being used to delete a data producer.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receiving a third message, the third message being used to create a data consumer.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: Receiving a fourth message, the fourth message being used to delete a data consumer.

9. A communication method, characterized in that, Applied to a first network element, the first network element is deployed in a 3GPP network, and includes: Receiving a first control message from a sensing service control function network element in the 3GPP network, the first control message being used to indicate receiving data of a first information type; Sending a first subscription message to a data communication agent in the 3GPP network, the first subscription message being used to subscribe to data of the first information type; the data communication agent supports multiple transport protocols; Receiving first data from the data communication agent, the first data being data of the first information type; the first data is Encapsulated by a first transport protocol among the multiple transport protocols.

10. The method according to claim 9, wherein Before receiving the first data from the data communication agent, the method further includes: Sending a data request message to the data communication agent.

11. The method according to claim 9 or 10, characterized in that The method further includes: Sending a third message to the data communication agent, the third message being used to create a data consumer.

12. The method according to any one of claims 9 to 11, characterized in that, The method further includes: Receiving a first service stop message from the perception service control function network element; Sending a fourth message to the data communication agent, where the fourth message is used to delete a data consumer.

13. A communication method, characterized in that, Applied to a second network element, the second network element is deployed in a 3rd Generation Partnership Project (3GPP) network, and includes: Receiving a second control message from the perception service control function network element in the 3GPP network, where the second control message is used to indicate sending data of a first information type; Sending first data to the data communication agent in the 3GPP network; the first data is data of the first information type; the data communication agent supports multiple transport protocols; the first data is encapsulated by a first transport protocol among the multiple transport protocols.

14. The method according to claim 13, wherein The method further includes: Sending a first message to the data communication agent, where the first message is used to create a data producer.

15. The method according to claim 13 or 14, characterized in that, The method further includes: Receiving a second service stop message from the perception service control function network element; Sending a second message to the data communication agent, where the second message is used to delete a data producer.

16. The method according to any one of claims 1-15, characterized in that, The multiple transport protocols include multiple of the following transport protocols: Transmission Control Protocol (TCP), User Datagram Protocol (UDP), or Quick UDP Internet Connections (QUIC) protocol.

17. The method according to any one of claims 1 to 16, characterized in that, The first transport protocol is indicated by the perception service control function network element.

18. The method according to claim 5 or 14, characterized in that, The first message includes one or more of the following: data producer name, adopted transport protocol, Quality of Service (QoS) level, or supported data compression algorithm.

19. The method according to claim 6 or 15, characterized in that, The second message includes the identifier of the data producer.

20. The method according to claim 7 or 11, characterized in that The third message includes one or more of the following: data consumer name, adopted transport protocol, data consumer group identifier, Quality of Service (QoS) level, or supported data compression algorithm.

21. The method according to claim 8 or 12, characterized in that, The fourth message includes the identifier of the data consumer.

22. A communication device, characterized in that, Including an interface module and a processing module, the interface module supports multiple transport protocols, and the processing module is used to process information related to data producers and data consumers; wherein: The interface module is specifically used to send and receive messages or data; The processing module is specifically used to execute the method according to any one of claims 1-8, 16-21 through the interface module.

23. A communication device, characterized in that, Including: An interface module for the communication of the communication device; A processing module for executing the method according to any one of claims 9-12, 16-21 through the interface module, or executing the method according to any one of claims 13-21.

24. A communication device, characterized in that, Including a communication interface and a processor, the communication interface supports multiple transport protocols, and the processor is used to process information related to data producers and data consumers; wherein: The communication interface is specifically used to send and receive messages or data; The processor is specifically used to execute the method according to any one of claims 1-8, 16-21 through the communication interface.

25. A communication device, characterized in that, Including: A communication interface for the communication of the communication device; A processor for executing the method according to any one of claims 9-12, 16-21 through the communication interface, or executing the method according to any one of claims 13-21.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or computer-executable instructions, and when the computer program or computer-executable instructions are called by a computer, they are used to execute the method described in any one of claims 1-8, 16-21, or execute the method described in any one of claims 9-12, 16-21, or execute the method described in any one of claims 13-21.

27. A chip, characterized in that, It includes a processor, and the processor is used to execute the method described in any one of claims 1-8, 16-21, or execute the method described in any one of claims 9-12, 16-21, or execute the method described in any one of claims 13-21.

28. A computer program product, characterized in that, The computer program product includes a computer program or instructions, and when the computer program or instructions run on a computer, they cause the computer to execute the method described in any one of claims 1-8, 16-21, or execute the method described in any one of claims 9-12, 16-21, or execute the method described in any one of claims 13-21.

Images