Communication method and device

Abstract

A communication method and device are used for improving data transmission efficiency. A data communication agent in the 3GPP network can support multiple transport protocols, the data communication agent receives a first subscription message from a first network element in the 3GPP network, and the first subscription message is used for subscribing 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; the first data is packaged by a first transmission protocol in a plurality of transmission protocols; and sending the first data to the first network element. Data transmission is directly carried out based on the data communication agent, and the data transmission efficiency is improved. Meanwhile, the data communication agent supports multiple transmission protocols, and different service scenes can be met.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a communication method and apparatus. Background Art

[0002] With the development of technologies, communication systems are evolving towards higher frequencies, larger bandwidths, and denser distributions of large-scale antenna arrays. As a result, a single system can integrate sensing and communication capabilities, enabling performance improvement among various systems.

[0003] Both wireless communication and wireless sensing are based on the electromagnetic wave theory. At the transmitting end, electromagnetic wave signals are modulated so that the electromagnetic waves carry source information. During propagation, the electromagnetic wave signals are affected by the wireless environment, that is, the electromagnetic wave signals are environmentally modulated and thus carry environmental information. At the receiving end, by analyzing the electromagnetic wave signals, not only can the carried source information be obtained, but also the sensing information reflecting the characteristics of the propagation environment can be extracted. This makes integrated sensing and communication (ISAC) possible. Compared with a system where sensing and communication are separated, an ISAC system can bring many advantages, such as cost savings, reduced device size, lower power consumption, improved spectral efficiency, and reduced mutual interference between communication and sensing.

[0004] A communication system may have a large amount of sensing data, and the current transmission methods for signaling and data in the communication system are not suitable for transmitting a large amount of sensing data. Therefore, how to transmit sensing data is an urgent problem to be solved. Summary of the Invention

[0005] Embodiments of this application provide a communication method and apparatus to improve data transmission efficiency.

[0006] In a first aspect, this application provides a communication method. This method can be applied to a data communication proxy, or a component (such as a processor, a chip, a chip system, a circuit, or others) configured in the data communication proxy, or a software module. The data communication proxy is deployed in a 3rd generation partnership project (3GPP) network, and the data communication proxy supports multiple transmission protocols. The method may include: receiving 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; receiving 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 by a first transmission protocol among the multiple transmission protocols; and sending the first data to the first network element.

[0007] Through the above method, data transmission can be directly performed based on the data communication proxy, improving the data transmission efficiency. At the same time, the data communication proxy supports multiple transmission protocols, which can meet different service scenarios.

[0008] In a possible design, the multiple transmission protocols include multiple of the following transmission protocols: Transmission Control Protocol (TCP), User Datagram Protocol (UDP), or Quick UDP Internet Connection (QUIC) protocol.

[0009] In a possible design, the first transmission protocol is indicated by the sensing service control function network element. This can clarify the encapsulation form of the first data.

[0010] In a possible design, the first network element is the first access network device, and the second network element is the second access network device; or, the first network element is the first core network device, and the second network element is the 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. That is to say, both the access network device and the core network device can act as data producers to publish data and also act as data consumers to subscribe to data.

[0011] In a possible design, the first network element is the sensing data processing function network element, the second network element is the access network device, and the first information type is indicated by the sensing service control function network element; or, the first network element is the sensing data processing function network element, the second network element is the user plane function network element, and the first information type is indicated by the sensing service control function network element; or, the first network element is the network openness function network element, the second network element is the sensing data processing function network element, and the first information type is indicated by the sensing service control function network element. For example, when the first network element is the sensing data processing function network element, the sensing data processing function network element acts as a data consumer to subscribe to data, and when the second network element is the sensing data processing function network element, the sensing data processing function network element acts as a data producer to publish data. Among them, 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 sensing service control function network element.

[0012] In a possible design, before sending the first data to the first network element, a data request message can also be received from the first network element. In this way, after the first network element initiates a data request, the data communication proxy can then send the first data to the first network element.

[0013] In a possible design, a first message is received, and the first message is used to create a data producer. Subsequently, the data producer can publish data.

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

[0015] In a possible design, a second message is received, and the second message is used to delete a data producer. Deleting the data producer after the service stops can save resources.

[0016] In a possible design, the second message includes an identifier of the data producer. This can accurately delete the data producer.

[0017] In a possible design, a third message is received, and the third message is used to create a data consumer. Subsequently, the data consumer can subscribe to data.

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

[0019] In a possible design, a fourth message is received, and the fourth message is used to delete a data consumer. Deleting the data consumer after the service stops can save resources.

[0020] In a possible design, the fourth message includes an identifier of the data consumer. This can accurately delete the data consumer.

[0021] In a second aspect, the present application provides a communication method. This method can be applied to a first network element, or a component (such as a processor, a chip, a chip system, a circuit, or others) configured in the first network element, 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 sensing service control function network element in the 3GPP network, where the first control message is used to indicate receiving data of a first information type; sending a first subscription message to a data communication proxy in the 3GPP network, where the first subscription message is used to subscribe to data of the first information type; the data communication proxy supports multiple transport protocols; receiving first data from the data communication proxy, where the first data is data of the first information type; and the first data is encapsulated by a first transport protocol among the multiple transport protocols.

[0022] Through the above method, the data consumer can directly subscribe to the required data from the data communication proxy without interacting with the data producer, which can improve the data transmission efficiency. At the same time, the data communication proxy supports multiple transport protocols, which can meet different service scenarios.

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

[0024] In a possible design, the first transport protocol is indicated by the sensing service control function network element. This can clarify the encapsulation form of the first data.

[0025] In a possible design, before receiving the first data from the data communication proxy, a data request message may also be sent to the data communication proxy. In this way, when the first network element has a data requirement, it can request data from the data communication proxy.

[0026] In a possible design, a third message is sent to the data communication proxy, where the third message is used to create a data consumer. In this way, subsequent data consumers can perform data subscriptions.

[0027] In a possible design, the third message may include one or more of the following: data consumer name, adopted transport protocol, data consumer group identifier, QoS, or supported data compression algorithm. This can clarify the data consumer subscribing to the data, the transport protocol adopted when subscribing to the data, and the supported data compression form, so that the data consumer can accurately subscribe to the data.

[0028] In a possible design, a first service stop message is received from the sensing service control function network element; a fourth message is sent to the data communication proxy, where the fourth message is used to delete the data consumer. In this way, deleting the data consumer after the service stops can save resources.

[0029] In a possible design, the fourth message includes the identifier of the data consumer. This can accurately delete the data consumer.

[0030] 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, a chip, a chip system, a circuit, or others) 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, where the second control message is used to indicate sending data of a first information type; sending first data to a data communication agent in the 3GPP network; the first data is data of the first information type; the data communication agent supports multiple transmission protocols; the first data is encapsulated by a first transmission protocol among the multiple transmission protocols.

[0031] Through the above method, the data producer can directly publish data to the data communication agent without interacting with the data consumer, which can improve the data transmission efficiency. At the same time, the data communication agent supports multiple transmission protocols, which can meet different service scenarios.

[0032] In a possible design, the multiple transmission protocols include multiple of the following transmission protocols: TCP, UDP, or QUIC protocol.

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

[0034] In a possible design, sending a first message to the data communication agent, where the first message is used to create a data producer. In this way, the subsequent data producer can publish data.

[0035] In a possible design, the first message may include one or more of the following: data producer name, adopted transmission protocol, quality of service level QoS, or supported data compression algorithm. This can clarify the data producer that publishes data, the transmission protocol adopted when publishing data, and the supported data compression form, so that the data producer can accurately publish data.

[0036] In a possible design, 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 the data producer. In this way, deleting the data producer after the service stops can save resources.

[0037] In a possible design, the second message includes the identifier of the data producer. This can accurately delete the data producer.

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

[0039] In a possible design, the structure of 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 the relevant information of the data producer and the data consumer. These modules can execute the corresponding functions in the above first aspect or each possible design example of the first aspect. For specific details, refer to the detailed description in the method examples and will not be elaborated here.

[0040] In a 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 the relevant information of the data producer and the data consumer. Optionally, a memory is further 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 to execute the corresponding functions in the above 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 of the communication device.

[0041] In a fifth aspect, the present application further 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.). This communication device has the functions implemented in the above second aspect or each possible design example of the second aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0042] In a possible design, the structure of the communication device includes an interface module and a processing module. These modules can execute the corresponding functions in the above second aspect or each possible design example of the second aspect. For specific details, refer to the detailed description in the method examples and will not be elaborated here.

[0043] In a possible design, the structure of the communication device includes a communication interface and a processor, and optionally also includes a memory. The communication interface is used for sending and receiving information and for communicating and interacting with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions in the above-mentioned second aspect or each possible design example of the second aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0044] 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 functions implemented in the above-mentioned third aspect or each possible design example of the third aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0045] In a possible design, the structure of the communication device includes an interface module and a processing module, and these modules can perform the corresponding functions in the above-mentioned third aspect or each possible design example of the third aspect. For specific details, refer to the detailed description in the method examples and will not be elaborated here.

[0046] In a possible design, the structure of the communication device includes a communication interface and a processor, and optionally also includes a memory. The communication interface is used for sending and receiving information and for communicating and interacting with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions in the above-mentioned third aspect or each possible design example of the third aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

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

[0048] In an eighth aspect, a computer-readable storage medium provided by an embodiment of the present application stores a computer program or computer-executable instructions. When the computer program or computer-executable instructions are called by a computer, the computer is caused to execute the methods described in the first aspect and any possible design thereof, or the methods described in the second aspect and any possible design thereof, or the methods described in the third aspect and any possible design thereof in the embodiments of the present application. Exemplarily, the computer-readable storage medium may be any available medium that can be accessed by a computer. By way of example but not limited to: the computer-readable medium may include a non-transitory computer-readable medium, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc 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.

[0049] In a 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 run on a computer, the methods described in the first aspect or any possible design of the first aspect, or the methods described in the second aspect or any possible design of the second aspect, or the methods described in the third aspect or any possible design of the third aspect are executed.

[0050] In a tenth aspect, the present application further provides a chip, including a processor, where the processor is used to execute the methods described in the first aspect or any possible design of the first aspect, or the methods described in the second aspect or any possible design of the second aspect, or the methods described in the third aspect or any possible design of the third aspect.

[0051] For the various aspects from the fourth aspect to the tenth aspect above and the possible technical effects that each aspect may achieve, please refer to the description of the technical effects that can be achieved by the first aspect or various possible solutions in the first aspect above, and details will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 It is a schematic diagram of a perception scenario provided by the present application;

[0053] Figure 2 It is a schematic diagram of data transmission based on DCP provided by the present application;

[0054] Figure 3 It is a schematic diagram of a possible perception architecture with DCP introduced in a 3GPP network provided by the present application;

[0055] Figure 4 Schematic diagram of a protocol stack for sensing data provided by this application;

[0056] Figure 5 Schematic diagram of another possible sensing architecture with DCP introduced in the 3GPP network provided by this application;

[0057] Figure 6 Schematic diagram of another protocol stack for sensing data provided by this application;

[0058] Figure 7 Schematic diagram of another protocol stack for sensing data provided by this application;

[0059] Figure 8 Flowchart of a communication method provided by this application;

[0060] Figure 9 Flowchart of an example of a communication method provided by this application;

[0061] Figure 10 Flowchart of an example of another communication method provided by this application;

[0062] Figure 11 Flowchart of an example of another communication method provided by this application;

[0063] Figure 12 Flowchart of an example of another communication method provided by this application;

[0064] Figure 13 Schematic diagram of the structure of a communication device provided by this application;

[0065] Figure 14 Structure diagram of a communication device provided by this application. Detailed implementation manners

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

[0067] The embodiments of the present application provide a communication method and device to improve data transmission efficiency. Among them, the method and device described in the present application are based on the same technical concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repeated parts will not be elaborated.

[0068] For the convenience of those skilled in the art to understand, some terms involved in the present application will be explained below.

[0069] 1) Wireless sensing (or simply sensing)

[0070] Wireless sensing uses wireless signals for sensing. Sensing is the process of collecting, processing the collected data, and generating sensing results. For example, by collecting data to determine the distance, shape, type, etc. of surrounding obstacles, or by collecting data to determine the breathing frequency, heart rate, etc. of the monitored object. Among them, the collected data can be data collected by sensors or data collected by wireless signals.

[0071] Both wireless sensing and wireless communication are based on the electromagnetic wave theory. At the transmitting end, the electromagnetic wave signal is modulated so that the electromagnetic wave signal carries the source information. And the electromagnetic wave signal will be affected by the wireless environment during propagation, that is, the electromagnetic wave signal is affected by the environment and can also carry environmental information; at the receiving end, by analyzing the electromagnetic wave signal, not only the carried source information can be obtained, but also the sensing information reflecting the characteristics of the propagation environment can be extracted. That is to say, the electromagnetic wave signal has the inherent dual capabilities of communication and sensing, which makes integrated sensing and communication (ISAC) possible. Integrated sensing and communication can also be called joint communications and sensing (JCAS). Integrated sensing and communication can also be abbreviated as integrated communication and sensing for short. Compared with the system where sensing and communication are separated, ISAC has a series of advantages, such as cost savings, reduced device size, lower power consumption, improved frequency efficiency, reduced mutual interference between communication and sensing, etc.

[0072] 2) Sensing scenarios

[0073] Sensing scenarios can be divided into sensing scenarios based on access network devices, sensing scenarios based on access network devices and terminal devices, and sensing scenarios based on terminal devices. Exemplarily, the sensing scenarios can be seen in the sensing scenarios shown in (1) to (6) of Figure 1 as shown.

[0074] Figure 1 The sensing scenario shown in (1) of is a sensing scenario based on access network devices, and the access network device serves as the transmitting (TX) and receiving (RX) ends of the sensing signal. For example, the sensing signal 1 sent by the access network device reaches the target object (such as a person), and after the sensing signal 1 is reflected by the target object, the access network device can receive the sensing signal 2, and then the sensing signal 2 can be processed to obtain the sensing result.

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

[0076] Figure 1 The sensing scenario shown in (3) is a sensing scenario based on access network devices and terminal devices. The access network device serves as the transmitter of the sensing signal, and the terminal device serves as the receiver of the sensing signal. For example, the sensing signal 1 sent by the access network device reaches the target object. After the sensing signal 1 is reflected by the target object, the terminal device can receive the sensing signal 2. Then, the terminal device can process the sensing signal 2 to obtain a sensing result.

[0077] Figure 1 The sensing scenario shown in (4) is also a sensing scenario based on access network devices and terminal devices. The terminal device serves as the transmitter of the sensing signal, and the access network device serves as the receiver of the sensing signal. For example, the sensing signal 1 sent by the terminal device reaches the target object. After the sensing signal 1 is reflected by the target object, the access network device can receive the sensing signal 2. Then, the access network device can process the sensing signal 2 to obtain a sensing result.

[0078] Figure 1 The sensing scenario shown in (5) is a sensing scenario based on terminal devices. The terminal device serves as both the transmitter and receiver of the sensing signal. For example, the sensing signal 1 sent by the terminal device reaches the target object. After the sensing signal 1 is reflected by the target object, the terminal device can receive the sensing signal 2. Then, it can process the sensing signal 2 to obtain a sensing result.

[0079] Figure 1 The sensing scenario shown in (6) is also a sensing scenario based on terminal devices. One terminal device serves as the transmitter of the sensing signal, and another terminal device serves as the receiver of the sensing signal. For example, the sensing signal 1 sent by the terminal device acting as TX reaches the target object. After the sensing signal 1 is reflected by the target object, the terminal device acting as RX can receive the sensing signal 2. Then, the terminal device acting as RX can process the sensing signal 2 to obtain a sensing result.

[0080] The above sensing signal 2 can be understood as the reflected signal of the above sensing signal 1. The information carried by the sensing signal 2 is more than that carried by the sensing signal 1. For example, the sensing signal 2 can carry source information and environmental information.

[0081] 3) Access network device

[0082] An access network device is a device that provides access for terminal devices. The access network device can also be referred to as a network device, an access node (AN), a radio access network (RAN) node, etc. The access network device can be a base station, an evolved Node B in a long term evolution (LTE) system or a long term evolution-advanced (LTE-A) system, which can be abbreviated as eNB or e-NodeB, a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a next generation NodeB in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc. It can also be an access network device in an open radio access network (openRAN, ORAN) system. Optionally, the access network device can also be a module or unit that completes some functions of the base station. For example, the access network device can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. Here, the CU completes the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete some or all of the functions of the physical layer. Among them, in different systems, the 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, the CU can also be called O-CU, the DU can also be called open (O)-DU, the CU-CP can also be called O-CU-CP, the CU-UP can also be called O-CUP-UP, and the RU can also be called O-RU.

[0083] Exemplarily, the access network device may be a macro base station, a micro base station (also known as a small station) or an indoor station, and may also be a relay node or 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 (for example, a home evolved NodeB, or a home Node B, HNB), a base band unit (BBU) or a remote radio unit (RRU), or a wireless fidelity (Wifi) access point (AP), or a base band pool (BBU pool) and an RRU in a cloud radio access network (CRAN), etc.

[0084] 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 disposed within the access network device.

[0085] The embodiments of this application do not limit the specific technologies and specific device forms adopted by the access network device.

[0086] 4) Terminal device

[0087] A terminal device, also known as a user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that provides voice and / or data connectivity to users. For example, terminal devices can include handheld devices with wireless connection capabilities, in-vehicle devices, etc. Currently, terminal devices can be: mobile phones, tablets, laptops, palmtop computers, 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, etc.

[0088] The terminal device can also be a device-to-device (D2D) terminal device, a vehicle-to-everything (V2X) communication terminal device, a smart vehicle, a telematics box (or vehicle networking system), a machine-to-machine / machine-type communications (M2M / MTC) terminal device, an Internet of Things (IoT) terminal device. For example, the terminal device can be a vehicle, a ship, an aircraft or other vehicles or terminal-type roadside units, or a communication module or chip built into a vehicle or roadside unit. For example, the terminal device can be an in-vehicle module. The terminal device can also be a roadside unit (RSU).

[0089] In this application, the terminal device can also be a functional module, a chip, or a chip system. Optionally, the functional module, the chip, or the chip system can be disposed within the terminal device.

[0090] Embodiments of the present application do not limit the specific technologies and specific device forms adopted by the terminal device.

[0091] 5) In the description of the present application, terms such as "first" and "second" are only used for the purpose of distinguishing descriptions, and cannot be construed as indicating or implying relative importance, nor can they be construed as indicating or implying an order.

[0092] 6) In the description of the present application, "at least one (kind)" means one (kind) or more (kinds), and more (kinds) means two (kinds) or more than two (kinds). "At least one of the following" or its similar expressions refer 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 represent: 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 multiple.

[0093] 7) In the description of the present application, "and / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. " / " represents "or", for example, a / b represents a or b.

[0094] With the diversified development of data transmission (such as perception data transmission and artificial intelligence (AI) data transmission, etc.), the current existing signaling or data transmission methods can no longer meet the future data transmission requirements. Based on this, in order to improve data transmission efficiency, the present 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 function as DCP can be regarded as DCP, and the present application does not limit this. Among them, DCP can be deployed as an independent network element in the 3GPP network, or can be co-located with network elements or devices in the 3GPP network, and the present application does not limit this. Optionally, DCP can be deployed in the access network or in the core network, and the present application does not limit this.

[0095] Exemplarily, Figure 2 shows a possible schematic diagram of data transmission based on DCP. Among them, a data producer sends data to DCP, for example Figure 2The topic publish shown. A data consumer can subscribe to data from the DCP and perform data pull. In some embodiments, each data consumer in a group of data consumers can subscribe to data from the DCP, as Figure 2 shown in the topic subscribe.

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

[0097] In some embodiments, the DCP can communicate 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 transmitting messages with the data producer through the first interface to create the data producer. Among them, when creating a data producer, the DCP can receive the data producer name and the transmission protocol adopted (such as TCP, UDP, or QUIC) through the first interface. Optionally, the DCP can also receive the quality of service (QoS) and / or the supported data compression algorithm 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, QoS, and the data compression algorithm supported by the data producer together or separately. Optionally, the DCP can send the ID of the data producer and / or the selected data compression algorithm of the data producer together or separately.

[0098] For another example, the DCP can delete a data producer through the second interface, which can also be understood as the DCP transmitting messages with the data producer through the second interface to delete the data producer. Among them, when deleting a data producer, the DCP can receive the ID of the data producer through the second interface.

[0099] For another example, the DCP can create a data consumer through the third interface, which can also be understood as the DCP transmitting messages with the data consumer through the third interface to create the data consumer. Among them, when creating a data consumer, the DCP can receive one or more of the data consumer name, the transmission protocol adopted (such as TCP, UDP, or QUIC), and the data consumer group identity (ID) through the third interface. Optionally, the DCP can also receive the QoS and / or the supported data compression algorithm through the third interface. When creating a data consumer, the DCP can also send the ID of the data consumer through the third interface. Optionally, the DCP can also send the selected data compression algorithm through the third interface. Optionally, the DCP can 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 can send the ID of the data consumer and / or the selected data compression algorithm of the data consumer together or separately.

[0100] For another example, the DCP can delete a data consumer through the fourth interface. It can also be understood that the DCP deletes a data producer by transmitting a message between the fourth interface and the data consumer. When deleting the data consumer, the DCP can receive the ID of the data consumer through the fourth interface.

[0101] For another example, the DCP can implement data subscription through the fifth interface. It can also be understood that the DCP realizes the data subscription of the data consumer by transmitting a message between the fifth interface and the data consumer. When subscribing to data, the DCP can receive the ID of the data consumer and a list of information types through the fifth interface. It should be understood that the list of information types is only a form. The list of information types can include at least one information type, and at least one information type can also be carried in the message in other forms. This application does not make any limitations in this regard. Exemplarily, the list of information types can include a topic list. Optionally, the DCP can receive the subscription duration through the fifth interface. Optionally, the DCP can receive the ID of the data consumer, the list of information types, and the subscription duration together, or it can receive the ID of the data consumer and the list of information types in the first message, and receive the subscription duration in the second message.

[0102] For another example, the DCP can implement data unsubscription through the sixth interface. It can also be understood that the DCP realizes the data unsubscription of the data consumer by transmitting a message between the sixth interface and the data consumer. When unsubscribing from data, the DCP can receive the ID of the data consumer and the list of information types through the sixth interface. Optionally, the DCP can receive the ID of the data consumer and the list of information types together or separately.

[0103] For another example, the DCP can implement data publishing through the seventh interface. It can also be understood that the DCP realizes the data publishing of the data producer by transmitting a message between the seventh interface and the data producer. When publishing data, the DCP can receive the ID of the data producer, the list of information types, and the data through the seventh interface. Optionally, the DCP can receive one or more of the ID of the data producer, the list of information types, and the data together or separately.

[0104] For another example, the DCP can implement data consumption through the eighth interface. It can also be understood that the DCP realizes the data consumption of the data consumer by transmitting a message between the eighth interface and the data consumer, and it can also be understood as the data extraction process of the data consumer. When consuming data, the DCP can receive the ID of the data consumer and the list of information types through the eighth interface. When consuming data, the DCP can send the data required by the consumer through the eighth interface. Optionally, the DCP can receive the ID of the data producer and the list of information types together or separately.

[0105] It should be noted that the foregoing first interface to the eighth interface are only exemplary names of the interfaces, and other names can be used for replacement. This application does not limit this. Optionally, the first interface to the eighth interface can be the same interface, or some of them can be the same interface. This application does not limit this.

[0106] In an optional manner, the QoS carried in the foregoing message can be reflected by the following values in the message: The value of QoS in the message is the first value, such as 0, indicating that the data is distributed at most once; The value of QoS in the message is the second value, such as 1, indicating that the data is distributed at least once; The value of QoS in the message is the third value, such as 2, indicating that the data is distributed only once. It should be understood that the above values and meanings of QoS are only for illustrative purposes and do not limit this application.

[0107] In an example, the foregoing 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.

[0108] DCP supports the transport layer security protocol (TLS) for data encryption integrity protection in scenarios where data is transmitted based on TCP or QUIC. DCP also supports the datagram transport layer security protocol (DTLS) for data encryption integrity protection in scenarios where data is transmitted based on UDP.

[0109] Exemplarily, in this application, the data producer and the data consumer can be different network elements in the 3GPP network, where the different network elements can be the same type of network element or different types of network elements. For example, the data producer is the first access network device and the data consumer is the second access network device. Another example is that the data producer is the first core network device and the data consumer is the second core network device. Another example is that the data producer is an access network device and the data consumer is a core network device. Another example is that the data producer is a core network device and the data consumer is an access network device.

[0110] Optionally, the same network element in the 3GPP network can be a data consumer in one scenario and a data producer in another scenario. This application does not limit this.

[0111] Exemplarily, the transmission mechanism for transmitting data through DCP can be called a data spine, or it can also be called other names. This application does not limit this.

[0112] In this application, the data can be sensing data, AI data, etc. In the following embodiments, sensing data is taken as an example for illustration.

[0113] Based on the above, Figure 3 The figure shows a schematic diagram of a possible sensing architecture in which DCP is introduced in a 3GPP network. In this sensing architecture, the access network device can be directly connected to the DCP. Among them, the access network device 1, as the sensing source, directly transmits the sensing data to the DCP. After obtaining the sensing data from the terminal device, the access network device 2 transmits the sensing data to the DCP.

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

[0115] The sensing data process function (SDPF) network element can be used to implement the data plane function of the sensing service. For example, the SDPF is used to process the sensing data of the sensing service to obtain the sensing result of the sensing service. The SDPF can be mounted on the SBI bus through the SBI to communicate with other core network elements, or can communicate through a separate interface. For example, it can communicate with other SDPFs through a separate interface, or communicate with the SSCF through a separate interface.

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

[0117] Among them, the core network elements in the sensing 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), and the sensing service subscriber management (SSSM) network element, etc., can act as data consumers to subscribe to data from the DCP, or act as data producers to send data to the DCP.

[0118] It should be understood that Figure 3 The devices included in the illustrated sensing architecture are only examples. The sensing architecture may also include other devices, or may not include Figure 3 Some of the illustrated devices. This application does not make any limitations in this regard.

[0119] Based on Figure 3 the illustrated sensing architecture, taking the example that the sensing data comes from the terminal device, the protocol stack of the sensing data can be as Figure 4 shown. Among them, the data forwarding protocol (DFP-S) belongs to the data processing protocol. The main functions of the DFP-S layer include data acquisition, data processing, data storage, data analysis, parsing and recombination of data headers, reporting of statistical information, data compression or privacy protection, etc. The data spine adaptor (DSA) layer is a newly introduced protocol layer. The main function of the DSA layer is message queue adaptation (such as creating a data consumer, creating a data producer, data publishing, data subscribing, data unsubscribing, data consuming, etc., one or more of them). Optionally, the DSA can also be replaced by the message queue adaptor (MQA), or it may have other names. This application does not make any limitations in this regard.

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

[0121] Figure 5The figure shows a schematic diagram of another possible sensing architecture with DCP introduced in a 3GPP network. In this sensing architecture, sensing data can be transmitted to the DCP through a user plane function (UPF) network element. For example, the access network device 1, as a sensing source, transmits the sensing data to the UPF, and the UPF then transmits the sensing data to the DCP. After obtaining the sensing data from the terminal device, the access network device 2 transmits the sensing data to the UPF, and the UPF then transmits the sensing data to the DCP.

[0122] Among them, in this sensing architecture, the functions of the SSCF network element, the SDPF network element, and the DSF network element can be referred to Figure 3 the relevant descriptions involved in the shown sensing architecture, and will not be elaborated here.

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

[0124] It should be understood that Figure 5 the devices included in the shown sensing architecture are only examples, and the sensing architecture may also include other devices, or may not include Figure 5 the partially shown devices, and this application does not make any limitations in this regard.

[0125] Based on Figure 5 the shown sensing architecture, taking the case where the sensing data comes from the terminal device as an example, in one possible way, the access network device can transparently transmit the sensing data of the terminal device to the UPF without processing the sensing data. In this case, the protocol stack of the sensing data can be as Figure 6 shown, and the access network device (such as a RAN node) may not include the DSA layer, while the UPF and the DCP include the DSA layer to process the received sensing data.

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

[0127] In another possible way, after receiving the sensing data of the terminal device, the access network device needs to process the sensing data. In this case, the protocol stack of the sensing data can be as Figure 7 shown.

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

[0129] It should be understood that the access network device can also be used as a sensing data source, that is, the access network device collects sensing data. In this case, the protocol stack corresponding to the sensing data can be Figure 7 the protocol stack obtained by removing the protocol layer of the UE and the protocol layer in the left column of the RAN node from the protocol stack shown, which is not shown by a diagram here.

[0130] 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 wireless communication systems such as short-range communications. Among them, 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), and massive machine-type communications (mMTC), long range (LoRa) systems or vehicle-to-everything (V2X) systems. The embodiments of the present application can also be applied to ORAN systems and the like.

[0131] Based on the above description, the communication method provided by the embodiments of the present application will be 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, etc. The present application only takes a certain device (or network element) as an example for illustration, but does not limit the present application.

[0132] Exemplarily, Figure 8 A schematic flowchart of a communication method provided by an embodiment of the present application is shown. Among them, the process of the method can include the following steps:

[0133] S801: The sensing service control function (SSCF) network element in the 3GPP network sends a first control message to a first network element in the 3GPP network. The first control message is used to indicate 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.

[0134] In this application, the data can be perception data, AI data, etc. In the illustrative description of this application, perception data is taken as an example for illustration. It should be understood that the illustrative description is not a limitation to this application.

[0135] In some embodiments, after receiving a perception service request message from a third-party entity, the perception service control function (SSCF) network element can determine the perception entity associated with the perception service. For example, the SSCF network element can select a second network element as the perception entity associated with the perception service.

[0136] Among them, the third-party entity can be an entity that requests the perception service.

[0137] In one implementation, the third-party entity can directly send a perception service request message to the SSCF network element. In another implementation, the third-party entity can send a perception service request message to the SSCF network element through the network exposure function (NEF) network element.

[0138] Optionally, the first control message can be a first perception control message.

[0139] In one example, the information type can refer to a topic or others. Correspondingly, the data of the first information type refers to the data of a certain topic.

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

[0141] In an optional embodiment, the first subscription message can include the ID of the data consumer and a list of information types. For example, the list of information types can include a topic list.

[0142] Optionally, the first subscription message can also include the subscription duration.

[0143] S803: The SSCF network element sends a second control message to a second network element in the 3GPP network. The second control message is used to instruct the sending of the data of the first information type. Correspondingly, the second network element receives the second control message from the SSCF network element.

[0144] Optionally, the second control message can be a second perception control message.

[0145] S804: The second network element sends the first data to the Data Communication Proxy (DCP). Correspondingly, the DCP receives the first data from the second network element. The first data is of the first information type; the first data is encapsulated by the first transport protocol among multiple transport protocols supported by the DCP.

[0146] Exemplarily, the multiple transport protocols supported by the DCP may include multiple of the following transport protocols: TCP, UDP, or QUIC protocol, etc.

[0147] Optionally, the first transport protocol may be indicated by the Sensing Service Control Function (SSCF) network element. For example, the SSCF network element may indicate the first transport protocol through a second control message, or the SSCF network element may also indicate the first transport protocol through other messages, which is not limited in this application.

[0148] In an optional implementation manner, when the second network element sends the first data to the DCP, it may also send the identifier of the second network element and the first information type to the DCP. It should be understood that the first data, the identifier of the second network element, and the first information type may be sent through the same message or through different messages, which is not limited in this application.

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

[0150] In an optional implementation manner, the first network element may be a data consumer, and the second network element may be a data producer. For example, specifically, the first network element and the second network element may be the following devices: the first network element is the first access network device, and the second network element is the second access network device; or, the first network element is the first core network device, and the second network element is the 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.

[0151] Exemplarily, in a scenario a1, the first network element may be the Sensing Data Processing Function (SDPF) network element, and the second network element may be an access network device.

[0152] In this scenario a1, the SDPF network element subscribes to the data of the first information type from the DCP, and the access network device sends the first data of the first information type to the DCP.

[0153] In this scenario a1, in one implementation, the terminal device is the sensing data source. After the access network device obtains the sensing 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 sensing data source. After the access network device collects the sensing data, it sends the first data to the Data Communication Proxy (DCP).

[0154] In one scenario a2, the first network element is the Sensing Data Processing Function (SDPF) network element, and the second network element is the User Plane Function (UPF) network element.

[0155] In this scenario a2, the Sensing Data Processing Function (SDPF) network element subscribes to data of the first information type from the Data Communication Proxy (DCP), and the User Plane Function (UPF) network element sends the first data of the first information type to the Data Communication Proxy (DCP).

[0156] In this scenario a2, in one implementation, the terminal device is the sensing data source. After the access network device obtains the sensing data from the terminal device, it forwards the sensing 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 sensing data source. After the access network device obtains the sensing data from the terminal device, it processes the sensing data and sends the processed sensing 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 sensing data source. After the access network device collects the sensing data, it sends the sensing 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).

[0157] In one scenario a3, the first network element is the Network Exposure Function (NEF) network element, and the second network element is the Sensing Data Processing Function (SDPF) network element.

[0158] In this scenario a3, the Network Exposure Function (NEF) network element subscribes to data of the first information type from the Data Communication Proxy (DCP), and the Sensing Data Processing Function (SDPF) network element sends the first data of the first information type to the Data Communication Proxy (DCP).

[0159] In this scenario a3, the Sensing Data Processing Function (SDPF) network element can first subscribe to data of other information types from the Data Communication Proxy (DCP), process the obtained data of other information types to obtain the first data of the first information type, and then send the first data to the Data Communication Proxy (DCP).

[0160] Among them, in each of the foregoing scenarios, the first information type may be indicated by the Sensing Service Control Function (SSCF) network element. For example, as mentioned above, the SSCF network element indicates to the first network element through a first control message and to the second network element through a second control message.

[0161] In an alternative embodiment, in addition to the manner in which the Data Communication Proxy (DCP) directly sends the first data to the first network element in S805, in a possible manner, before the DCP directly sends the first data to the first network element, it receives a data request message from the first network element. That is to say, when the first network element needs data, it can send a data request message to the DCP, and the DCP can send the first data to the first network element after receiving the data request message from the first network element.

[0162] Optionally, the data request message may include the ID of the data consumer and the first information type.

[0163] In some embodiments, the second network element may send a first message to the DCP, and the first message is used to create a data producer. Accordingly, the DCP may receive the first message from the second network element.

[0164] Exemplarily, the first message may include one or more of the following: data producer name, adopted transport protocol, QoS, or supported data compression algorithm. For specific descriptions, reference may be made to the relevant introductions mentioned above, and details are not elaborated here.

[0165] Optionally, the second network element may send the first message to the DCP when the system starts; or, the second network element may also send the first message to the DCP when the sensing task starts. For example, the second network element may send the first message to the DCP after receiving the second control message.

[0166] The DCP may also send a response message to the first message of the second network element, and the response message to the first message may include the identifier of the data producer. Optionally, the response message to the first message may further include the selected data compression algorithm.

[0167] In some embodiments, after the second network element receives a second service stop message from the SSCF network element, it may send a second message to the DCP, and the second message is used to delete the data producer. Accordingly, the DCP receives the second message from the second network element.

[0168] Exemplarily, the second message may include the identifier of the data producer.

[0169] In some embodiments, the first network element may send a third message to the Data Communication Proxy (DCP), and the third message is used to create a data consumer. Accordingly, the DCP may receive the third message from the first network element.

[0170] Exemplarily, the third message may include one or more of the following: data consumer name, adopted transport protocol, data consumer group identifier, QoS, or supported data compression algorithm. For specific descriptions, reference may be made to the relevant introductions mentioned above, which will not be elaborated here.

[0171] Optionally, the first network element may send the third message to the DCP when the system starts; or, the first network element may also send the third message to the DCP when the sensing task starts. For example, the first network element may send the third message to the DCP after receiving the first control message.

[0172] The DCP may also send a response message to the third message to the first network element, and the response message to the third message may include the identifier of the data consumer. Optionally, the response message to the third message may further include the selected data compression algorithm.

[0173] In some implementations, after the first network element receives the first service stop message from the Sensing Service Control Function (SSCF) network element, it may send a fourth message to the DCP, and the fourth message is used to delete the data consumer. Accordingly, the DCP receives the fourth message from the first network element.

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

[0175] The above Figure 8 The communication method shown can directly perform data transmission based on the DCP, improving data transmission efficiency. At the same time, the DCP supports multiple transport protocols, which can meet different service scenarios. In addition, by adopting the communication method of the present application, based on the data transmission of the DCP, there is no need for a binding relationship between the data producer and the data consumer, and the two can be decoupled, making the data transmission more flexible.

[0176] Based on the above embodiments, the following Figures 9 - 12 shows an example of the communication method provided by the present application. In the following example, the data is taken as the sensing data for illustration, and the information type is taken as the theme for illustration.

[0177] Exemplarily, Figure 9 shows an example of a communication method. In this example, the UE is the sensing data source. This example corresponds to Figure 3 the shown sensing architecture, and the RAN node can be directly connected to the DCP. For example,Figure 9 The example shown may include the following steps:

[0178] S901: A third-party entity sends a sensing service request to the SSCF.

[0179] Optionally, the third-party entity may send a sensing service request to the SSCF through the NEF, and S901 is taken as an example in Figure 9 to illustrate. It should be understood that the third-party entity may directly send a sensing service request to the SSCF.

[0180] In some embodiments, one or more of a sensing service type, a sensing data type of the sensing service, or a sensing service identifier may be carried in the sensing service request. Optionally, the sensing 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 environmental temperature, environmental humidity, air quality, weather conditions, crowd density, traffic flow density, air pressure, etc. The monitoring type may include, but is not limited to, one or more of mobile monitoring, intrusion monitoring, fall monitoring, health monitoring, etc. Mobile monitoring may include, but is not limited to, one or more of distance monitoring, location monitoring, moving speed monitoring, moving path monitoring, etc. Health monitoring may include, but is not limited to, one or more of information such as breathing frequency 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.

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

[0182] Exemplarily, the third-party entity may be any entity that requests a sensing service, and the present application does not limit the third-party entity.

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

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

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

[0186] In some embodiments, one or more of a sensing service type, a sensing data type of the sensing service, a sensing service identifier, regional information of the sensing service, or sensing requirement information of the sensing service may be carried in the sensing control message 1, and the specific sensing service type may refer to the description in S901.

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

[0188] S904: The SSCF sends a sensing control message 2 to the SDPF. The sensing control message 2 is used to instruct the 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.

[0189] In this case, the SDPF can be both a data consumer and a data producer. When the SDPF is a data consumer, the SDPF can subscribe to the data of topic 1, and at this time the SDPF can correspond to the aforementioned first network element; when the SDPF is a data producer, the SDPF can publish the data of topic 2, and at this time the SDPF can correspond to the aforementioned second network element.

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

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

[0192] S906: The SSCF sends a sensing control message 4 to the NEF. The sensing control message 4 is used to instruct the NEF to subscribe to the data of topic 2.

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

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

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

[0196] The message 1 may include one or more of the following: data producer name, adopted transport protocol, QoS, or supported data compression algorithm.

[0197] Exemplarily, the data producer name in the message 1 may be a name defined by the RAN node, for example, it may be the RAN node name, or it may also be in other string forms, or in other arbitrary forms, which is not limited in this application.

[0198] S907 is optional.

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

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

[0201] Exemplarily, the name of the data producer in the message 2 may be the name defined by SDPF, such as the SDPF name, or may also be in other string forms, or may also be in other arbitrary forms, and the present application does not make any limitation thereto.

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

[0203] Exemplarily, the name of the data consumer in the message 3 may be the name defined by SDPF, such as the SDPF name, or may also be in other string forms, or may also be in other arbitrary forms, and the present application does not make any limitation thereto.

[0204] S908 is optional.

[0205] The present application does not make any limitation on the sequence order of S907 and S908.

[0206] S909: SDPF sends a subscription message 1 to DCP, and the subscription message 1 is for the data of topic 1.

[0207] Exemplarily, the subscription message 1 may include the ID of the data consumer and the topic list.

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

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

[0210] S910: NEF sends a message 4 to DCP, and the message 4 is for creating a data consumer.

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

[0212] Exemplarily, the name of the data consumer in the message 4 may be the name defined by NEF, such as the NEF name, or may also be in other string forms, or may also be in other arbitrary forms, and the present application does not make any limitation thereto.

[0213] S910 is optional.

[0214] S911: The NEF sends Subscription Message 2 to the DCP. Subscription Message 2 is used to subscribe to the data of Topic 2.

[0215] Exemplarily, Subscription Message 2 may include the ID of the data consumer and the topic list.

[0216] Exemplarily, the ID of the data consumer included in Subscription Message 2 is the ID of the data consumer returned by the DCP to the NEF after the NEF sends Message 4 to the DCP to create a data consumer.

[0217] Optionally, Subscription Message 2 may also include the subscription duration.

[0218] S912: The UE collects Sensing Data 1 and sends Sensing Data 1 to the RAN node.

[0219] Among them, Sensing Data 1 is the data of Topic 1.

[0220] S913: The RAN node sends Sensing Data 1 to the DCP.

[0221] It should be understood that S912 is described by taking the example that after the UE collects the sensing data of Topic 1, the RAN node directly forwards it to the DCP. It should be understood that in another possible way, after the UE collects the sensing data and sends it to the RAN node, the RAN node processes the sensing data obtained from the UE to obtain the sensing data 1 of Topic 1, and then sends the sensing data 1 to the DCP.

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

[0223] Among them, 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 a data producer.

[0224] S914: The SDPF sends Data Request Message 1 to the DCP.

[0225] This Data Request Message 1 may include the ID of the data consumer corresponding to the SDPF and Topic 1.

[0226] Exemplarily, the ID of the data consumer included in this Data Request Message 1 is the ID of the data consumer returned by the DCP to the SDPF after the SDPF sends Message 3 to the DCP to create a data consumer.

[0227] S914 is optional.

[0228] S915: The DCP sends Sensing Data 1 to the SDPF.

[0229] S916: The SDPF processes the sensed data 1 to obtain the sensed data 2.

[0230] The sensed data 2 is the data of the subject 2.

[0231] S917: The SDPF sends the sensed data 2 to the DCP.

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

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

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

[0235] S918 is optional.

[0236] S919: The DCP sends the sensed data 2 to the NEF.

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

[0238] S921: The SSCF sends the sensing service stop message 1 to the UE.

[0239] S922: The SSCF sends the sensing service stop message 2 to the RAN node.

[0240] S923: The SSCF sends the sensing service stop message 3 to the SDPF.

[0241] S924: The SSCF sends the sensing service stop message 4 to the NEF.

[0242] This application does not limit the sequence of S921 - S924 above.

[0243] The above S921 - S924 are optional.

[0244] S925: The RAN node sends the message 5 to the DCP, and the message 5 is used to delete the data producer.

[0245] The message 5 may include the identifier of the data producer.

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

[0247] The message 6 may include the identifier of the data producer.

[0248] The message 7 may include the identifier of the data consumer.

[0249] S927: The NEF sends Message 8 to the DCP, and Message 8 is used to delete the data consumer.

[0250] Message 8 may include the identifier of the data consumer.

[0251] Among them, the present application does not limit the sequence of S925 - S927.

[0252] The above S925 - S927 are optional.

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

[0254] Via Figure 9 In the example shown, the RAN node is directly connected to the DCP. Based on the DCP, the publication and subscription of sensing data can be directly performed without binding between the data producer and the data consumer, which can improve the data transmission efficiency.

[0255] Exemplarily, Figure 10 shows an example of another communication method. In this example, the UE is the sensing data source, and the RAN node can transparently transmit the sensing data of the UE. This example corresponds to Figure 5 the shown sensing architecture, and the RAN node is connected to the DCP through the UPF. For example, Figure 10 the example shown may include the following steps:

[0256] S1001: The third - party entity sends a sensing service request to the SSCF.

[0257] Optionally, the third - party entity may send a sensing service request to the SSCF through the NEF, and S1001 is shown by taking this as an example in Figure 10 . It should be understood that the third - party entity may directly send a sensing service request to the SSCF.

[0258] Optionally, for the relevant description of the sensing service request, reference may be made to the description involved in the foregoing S901, and details are not elaborated here.

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

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

[0261] S1003: The SSCF sends Sensing Control Message 1 to the UE. Sensing Control Message 1 is used to instruct the UE to collect sensing data.

[0262] Optionally, for the relevant description of the sensing control message 1, reference can be made to the description involved in the foregoing S903, which will not be elaborated here.

[0263] S1004: The SSCF sends a sensing control message 2 to the SDPF. The sensing control message 2 is used to instruct the 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.

[0264] In this case, the SDPF can be both a data consumer and a data producer. When the SDPF is a data consumer, the SDPF can subscribe to the data of topic 1, and at this time, the SDPF can correspond to the foregoing first network element; when the SDPF is a data producer, the SDPF can send the data of topic 2, and at this time, the SDPF can correspond to the foregoing second network element.

[0265] S1005: The SSCF sends a sensing control message 3 to the UPF. The sensing control message 3 is used to instruct the UPF to send the data of topic 1.

[0266] Exemplarily, the UPF is a data producer, and the UPF can correspond to the foregoing second network element.

[0267] S1006: The SSCF sends a sensing control message 4 to the NEF. The sensing control message 4 is used to instruct the NEF to subscribe to the data of topic 2.

[0268] Exemplarily, the NEF is a data consumer, and the NEF can correspond to the foregoing first network element.

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

[0270] S1007: The UPF sends a message 1 to the DCP. The message 1 is used to create a data producer.

[0271] The message 1 may include one or more of the following: data producer name, adopted transport protocol, QoS, or supported data compression algorithm.

[0272] Exemplarily, the data producer name in the message 1 can be a name defined by the UPF. For example, it can be the UPF name, or it can also be in the form of other strings, or it can also be in any other form, and this application does not limit this.

[0273] S1007 is optional.

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

[0275] The message 2 may include one or more of the following: data producer name, adopted transport protocol, QoS, or supported data compression algorithm.

[0276] The message 3 may include one or more of the following: data consumer name, adopted transport protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0277] Similarly, the data producer name in the message 2 and the data consumer name in the message 3 may refer to the relevant descriptions involved in the Figure 9 illustrated example, which will not be elaborated here.

[0278] S1008 is optional.

[0279] This application does not limit the sequence of S1007 and S1008.

[0280] S1009: The SDPF sends a subscription message 1 to the DCP, and the subscription message 1 is for the data of topic 1.

[0281] Exemplarily, the subscription message 1 may include the ID of the data consumer and the topic list.

[0282] Similarly, the ID of the data consumer in the subscription message 1 may refer to the Figure 9 relevant descriptions involved in the illustrated example, which will not be elaborated here.

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

[0284] S1010: The NEF sends a message 4 to the DCP, and the message 4 is for creating a data consumer.

[0285] The message 4 may include one or more of the following: data consumer name (which may refer to the Figure 9 relevant descriptions involved in the illustrated example), adopted transport protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0286] S1010 is optional.

[0287] S1011: The NEF sends a subscription message 2 to the DCP, and the subscription message 2 is for subscribing to the data of topic 2.

[0288] Exemplarily, the subscription message 2 may include the ID of the data consumer (which may refer to the Figure 9 relevant descriptions involved in the illustrated example) and the topic list.

[0289] Optionally, the subscription message 2 may further include the subscription duration.

[0290] S1012: The UE collects sensing data 1 and sends the sensing data 1 to the UPF via the RAN node.

[0291] Among them, the sensing data 1 is the data of theme 1.

[0292] S1013: The UPF sends the sensing data 1 to the DCP.

[0293] It should be understood that S1012 is described by taking the example that after the UE collects the sensing data 1 of theme 1, it is directly forwarded to the DCP through the RAN node and the UPF. It should be understood that in another possible way, after the UE collects the sensing data and sends it to the UPF through the RAN node, the UPF processes the obtained sensing data to obtain the sensing data 1 of theme 1, and then sends the sensing data 1 to the DCP.

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

[0295] Among them, the ID of the data producer corresponding to the UPF may 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 a data producer.

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

[0297] This data request message 1 may include the ID of the data consumer corresponding to the SDPF (see the relevant descriptions involved in the example shown in Figure 9 ) and theme 1.

[0298] S1014 is optional.

[0299] S1015: The DCP sends the sensing data 1 to the SDPF.

[0300] S1016: The SDPF processes the sensing data 1 to obtain sensing data 2.

[0301] The sensing data 2 is the data of theme 2.

[0302] S1017: The SDPF sends the sensing data 2 to the DCP.

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

[0304] This data request message 2 may include the ID of the data consumer corresponding to the NEF (see the relevant descriptions involved in the example shown in Figure 9 ) and theme 2.

[0305] S1018 is optional.

[0306] S1019: The DCP sends the sensing data 2 to the NEF.

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

[0308] S1021: The SSCF sends the sensing service stop message 1 to the UE.

[0309] S1022: The SSCF sends the sensing service stop message 2 to the UPF.

[0310] S1023: The SSCF sends the sensing service stop message 3 to the SDPF.

[0311] S1024: The SSCF sends the sensing service stop message 4 to the NEF.

[0312] This application does not limit the sequence of S1021 - S1024 above.

[0313] The above S1021 - S1024 are optional.

[0314] S1025: The UPF sends message 5 to the DCP, and message 5 is used to delete the data producer.

[0315] Message 5 may include the identifier of the data producer.

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

[0317] Message 6 may include the identifier of the data producer.

[0318] Message 7 may include the identifier of the data consumer.

[0319] S1027: The NEF sends message 8 to the DCP, and message 8 is used to delete the data consumer.

[0320] Message 8 may include the identifier of the data consumer.

[0321] Among them, this application does not limit the sequence of S1025 - S1027.

[0322] The above S1025 - S1027 are optional.

[0323] It should be understood that the steps for creating the data producer and the steps for creating the data consumer in this application can also be executed when the system starts, or the steps for creating the data producer and the steps for creating the data consumer may not be executed. This application does not limit this.

[0324] Via Figure 10In the example shown, the perception data can be directly published and subscribed based on the DCP without the need for binding between the data producer and the data consumer, which can improve the data transmission efficiency.

[0325] Exemplarily, Figure 11 an example of another communication method is shown. In this example, the UE is the perception data source, and after the RAN node obtains the perception data of the UE, it processes the perception data. This example corresponds to Figure 5 the perception architecture shown, and the RAN node is connected to the DCP through the UPF. For example, Figure 11 the example shown may include the following steps:

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

[0327] Optionally, the third-party entity may send a perception service request to the SSCF through the NEF, and S1101 is shown by taking this as an example in Figure 11 . It should be understood that the third-party entity may directly send a perception service request to the SSCF.

[0328] Optionally, the relevant description of the perception service request may refer to the description involved in the foregoing S901 and will not be elaborated here.

[0329] S1102: The SSCF determines the perception entity associated with the perception service.

[0330] For example, the SSCF may select the transmission entity of the perception data, such as the UE, RAN node, UPF, SDPF, etc.

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

[0332] Optionally, the relevant description of the perception control message 1 may refer to the description involved in the foregoing S903 and will not be elaborated here.

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

[0334] S1105: The SSCF sends a perception control message 3 to the SDPF. The perception control message 3 is used to instruct the SDPF to subscribe to the data of topic 1 and publish the data through topic 2 after analyzing and processing the data of topic 1.

[0335] In this case, the SDPF can be either a data consumer or a data producer. When the SDPF is a data consumer, the SDPF can subscribe to the data of Topic 1, and at this time, the SDPF can correspond to the aforementioned first network element; when the SDPF is a data producer, the SDPF can send the data of Topic 2, and at this time, the SDPF can correspond to the aforementioned second network element.

[0336] S1106: The SSCF sends a sensing control message 4 to the UPF, and the sensing control message 4 is used to instruct the UPF to send the data of Topic 1.

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

[0338] S1107: The SSCF sends a sensing control message 5 to the NEF, and the sensing control message 5 is used to instruct the NEF to subscribe to the data of Topic 2.

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

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

[0341] S1108: The UPF sends a message 1 to the DCP, and the message 1 is used to create a data producer.

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

[0343] S1108 is optional.

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

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

[0346] The 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.

[0347] S1109 is optional.

[0348] This application does not limit the sequence of S1108 and S1109.

[0349] S1110: The SDPF sends Subscription Message 1 to the DCP. Subscription Message 1 is for the data of Topic 1.

[0350] Exemplarily, Subscription Message 1 may include the ID of the data consumer and the topic list.

[0351] Optionally, Subscription Message 1 may also include the subscription duration.

[0352] S1111: The NEF sends Message 4 to the DCP. Message 4 is for creating a data consumer.

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

[0354] S1111 is optional.

[0355] S1112: The NEF sends Subscription Message 2 to the DCP. Subscription Message 2 is for subscribing to the data of Topic 2.

[0356] Exemplarily, Subscription Message 2 may include the ID of the data consumer and the topic list.

[0357] Optionally, Subscription Message 2 may also include the subscription duration.

[0358] S1113: The UE collects Sensing Data 1 and sends Sensing Data 1 to the RAN node.

[0359] S1114: The RAN node processes Sensing Data 1 to obtain Sensing Data 2.

[0360] Among them, the processing of Sensing Data 1 by the RAN node may be point cloud data processing, etc., which is not limited in this application.

[0361] S1115: The RAN node sends Sensing Data 2 to the UPF.

[0362] S1116: The UPF sends Sensing Data 3 to the DCP.

[0363] Among them, Sensing Data 3 is the data of Topic 1.

[0364] Optionally, Sensing Data 3 and Sensing Data 2 may be the same data, that is, the UPF does not process the data. Sensing Data 3 may also be the sensing data obtained by the UPF processing Sensing Data 2. This application does not limit this.

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

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

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

[0368] S1117 is optional.

[0369] S1118: The DCP sends sensed data 3 to the SDPF.

[0370] S1119: The SDPF processes the sensed data 3 to obtain sensed data 4.

[0371] The sensed data 4 is the data of topic 2.

[0372] S1120: The SDPF sends the sensed data 4 to the DCP.

[0373] S1121: The NEF sends data request message 2 to the DCP.

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

[0375] S1121 is optional.

[0376] S1122: The DCP sends the sensed data 4 to the NEF.

[0377] S1123: The NEF sends the sensed data 4 to a third-party entity.

[0378] Optionally, after step 1123, similar operations as in the foregoing S1021 - S1027 may also be performed in this example. For details, refer to the foregoing description and will not be elaborated here. Figure 11 shown.

[0379] It should be understood that the steps for creating a data producer and the steps for creating a data consumer in this application may also be executed when the system starts, or the steps for creating a data producer and the steps for creating a data consumer may not be executed. This application does not make any limitations in this regard.

[0380] Figure 11 In the shown example, for the relevant descriptions of the data producer name, data consumer name, the ID of the data producer, and the ID of the data consumer, reference may be made to Figure 10 the similar descriptions involved in the shown example, which will not be elaborated in this example.

[0381] Through Figure 11 the shown example, based on the DCP, the publication and subscription of sensed data can be directly performed without the need for binding between the data producer and the data consumer, which can improve the data transmission efficiency.

[0382] Exemplarily, Figure 12 an example of another communication method is shown. In this example, the RAN node is the sensing data source. This example corresponds to Figure 5 the shown sensing architecture, and the RAN node is connected to the DCP through the UPF. For example, Figure 12 the shown example may include the following steps:

[0383] S1201: A third-party entity sends a sensing service request to the SSCF.

[0384] Optionally, the third-party entity may send the sensing service request to the SSCF through the NEF, and S1201 takes this as an example in Figure 12 this case. It should be understood that the third-party entity may directly send the sensing service request to the SSCF.

[0385] Optionally, for the relevant description of the sensing service request, reference may be made to the description involved in the foregoing S901, which will not be elaborated here.

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

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

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

[0389] Optionally, the relevant description of the sensing control message 1 is similar to the content of the sensing control message 1 involved in the foregoing S903, and reference may be made to each other, which will not be elaborated here.

[0390] S1204: The SSCF sends a sensing control message 2 to the SDPF. The sensing control message 2 is used to instruct the SDPF to subscribe to the data of topic 1 and publish the data through topic 2 after analyzing and processing the data of topic 1.

[0391] In this case, the SDPF can be both a data consumer and a data producer. When the SDPF is a data consumer, the SDPF can subscribe to the data of topic 1, and at this time, the SDPF can correspond to the foregoing first network element; when the SDPF is a data producer, the SDPF can send the data of topic 2, and at this time, the SDPF can correspond to the foregoing second network element.

[0392] S1205: The SSCF sends a sensing control message 3 to the UPF. The sensing control message 3 is used to instruct the UPF to publish the data of topic 1.

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

[0394] S1206: The SSCF sends a sensing control message 4 to the NEF, and the sensing control message 4 is used to instruct the NEF to subscribe to the data of topic 2.

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

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

[0397] S1207: The UPF sends a message 1 to the DCP, and the message 1 is used to create a data producer.

[0398] The message 1 may include one or more of the following: data producer name, adopted transport protocol, QoS, or supported data compression algorithm.

[0399] S1207 is optional.

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

[0401] The message 2 may include one or more of the following: data producer name, adopted transport protocol, QoS, or supported data compression algorithm.

[0402] The message 3 may include one or more of the following: data consumer name, adopted transport protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0403] S1208 is optional.

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

[0405] S1209: The SDPF sends a subscription message 1 to the DCP, and the subscription message 1 is for the data of topic 1.

[0406] Exemplarily, the subscription message 1 may include the ID of the data consumer and the topic list.

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

[0408] S1210: The NEF sends a message 4 to the DCP, and the message 4 is used to create a data consumer.

[0409] The following one or more items may be included in Message 4: data consumer name, adopted transport protocol, data consumer group identifier, QoS, or supported data compression algorithm.

[0410] S1210 is optional.

[0411] S1211: The NEF sends Subscription Message 2 to the DCP, and Subscription Message 2 is used to subscribe to the data of Topic 2.

[0412] Exemplarily, the data consumer's ID and the topic list may be included in Subscription Message 2.

[0413] Optionally, the subscription duration may also be included in Subscription Message 2.

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

[0415] Among them, the sensed data 1 is the data of Topic 1.

[0416] S1213: The UPF sends the sensed data 1 to the DCP.

[0417] It should be understood that S1212 is described by taking the example that after the RAN node collects the sensed data of Topic 1 and forwards it to the DCP through the UPF. It should be understood that in another possible way, after the RAN node collects the sensed data and sends it to the UPF, the UPF processes the obtained sensed data to obtain the sensed data 1 of Topic 1, and then sends the sensed data 1 to the DCP.

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

[0419] S1214: The SDPF sends Data Request Message 1 to the DCP.

[0420] The Data Request Message 1 may include the ID of the data consumer corresponding to the SDPF and Topic 1.

[0421] S1214 is optional.

[0422] S1215: The DCP sends the sensed data 1 to the SDPF.

[0423] S1216: The SDPF processes the sensed data 1 to obtain the sensed data 2.

[0424] The sensed data 2 is the data of Topic 2.

[0425] S1217: The SDPF sends the sensed data 2 to the DCP.

[0426] S1218: The NEF sends Data Request Message 2 to the DCP.

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

[0428] S1218 is optional.

[0429] S1219: The DCP sends the sensing data 2 to the NEF.

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

[0431] Optionally, after S1220, similar operations as in the foregoing S1021 - S1027 may also be performed in this example. For details, refer to the foregoing description and will not be elaborated here. Figure 11 shown.

[0432] It should be understood that the steps for creating the data producer and the steps for creating the data consumer in this application may also be executed when the system is started, or the steps for creating the data producer and the steps for creating the data consumer may not be executed. This application does not make any limitation in this regard.

[0433] Figure 12 In the example shown, for the relevant descriptions of the data producer name, data consumer name, ID of the data producer, and ID of the data consumer, reference may be made to Figure 10 the similar descriptions involved in the example shown. Details will not be elaborated in this example.

[0434] Through Figure 12 In the example shown, based on the DCP, the publication and subscription of sensing data can be directly performed without binding between the data producer and the data consumer, which can improve the data transmission efficiency.

[0435] Based on the above embodiments, the embodiments of this application further provide a communication device. Referring to Figure 13 shown, the communication device 1300 may include an interface module 1301 and a processing module 1302. Among them, the interface module 1301 may be used to send and receive information, etc. The processing module 1302 may implement the control and management of the actions of the communication device 1300. The processing module 1302 may also control the operations performed by the interface module 1301.

[0436] Exemplarily, the communication device 1300 may be the data communication proxy in the above embodiments (such as Figures 9 - 12 the DCP in Figures 9 - 12the network element as a data consumer), the 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 embodiments (such as Figures 9 - 12 the network element as a data producer) in the second network element, the processor of the second network element, or a chip, or a chip system, or a functional module, etc.

[0437] In one embodiment, when the communication device 1300 is used to implement the function of the data communication proxy in the above embodiments, the interface module 1301 supports multiple transmission protocols, and the processing module 1302 is used to process the relevant information of the data producer and the data consumer. Specifically, it may include: the interface module 1301 may be used to receive a first subscription message from the 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 the second network element in the 3GPP network, where the first data is data of the first information type; the first data is encapsulated by 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 transceiver operations of the interface module 1301.

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

[0439] In a possible way, the first transmission protocol is indicated by the sensing service control function network element.

[0440] In an alternative 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.

[0441] For example, 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 the 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 the 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.

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

[0443] In one example, the interface module 1301 can also be used to receive a first message for creating a data producer.

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

[0445] In some embodiments, the interface module 1301 can also be used to receive a second message for deleting a data producer.

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

[0447] In some embodiments, the interface module 1301 can also be used to receive a third message for creating a data consumer.

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

[0449] In some embodiments, the interface module 1301 can also be used to receive a fourth message for deleting a data consumer.

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

[0451] In yet another embodiment, when the communication device 1300 is used to implement the functions of the first network element in the above embodiments, it may include: the interface module 1301 can be used to receive a first control message from a perception service control function network element in the 3GPP network, the first control message is used to indicate receiving data of a first information type; send a first subscription message to a data communication proxy in the 3GPP network, the first subscription message is used to subscribe to data of the first information type; the data communication proxy supports multiple transmission protocols; and receive first data from the data communication proxy, the first data is data of the first information type; the first data is encapsulated by a first transmission protocol among the multiple transmission protocols. The processing module 1302 can be used to control the sending and receiving operations of the interface module 1301.

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

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

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

[0455] In one example, the interface module 1301 can also be used to send a third message to the data communication agent, and the third message is used to create a data consumer.

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

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

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

[0459] In yet another embodiment, when the communication device 1300 is used to implement the function of the second network element in the above embodiment, it may include: the interface module 1301 can be used to receive a second control message from the sensing service control function network element in the 3GPP network, and the second control message is used to indicate sending data of the first information type; send the 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 the first transport protocol among the multiple transport protocols. The processing module 1302 can be used to control the transceiver operations of the interface module 1301.

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

[0461] Optionally, the first transport protocol is indicated by the sensing service control function network element.

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

[0463] Exemplarily, the first message includes one or more of the following: data producer name, adopted transport protocol, quality of service level QoS, or supported data compression algorithm.

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

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

[0466] It should be noted that the division of units in the embodiments of the present application is illustrative. It is only a logical function division, and there may be other division methods in actual implementation. In the embodiments of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0467] 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 such an understanding, the technical solution of the present application, in essence, or the part that makes a contribution, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: various media 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 disc that can store program codes.

[0468] Based on the above embodiments, the embodiments of the present application also provide a communication device. Refer to Figure 14 As shown, the communication device 1400 can include a communication interface 1401 and a processor 1402. Optionally, the communication device 1400 can also include a memory 1403. Among them, the memory 1403 can be arranged inside the communication device 1400 or outside the communication device 1400. Among them, the processor 1402 can control the communication interface 1401 to receive and send signals, messages, information, or data, etc.

[0469] 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, data, etc. The receiver is used to receive signals, messages, information, data, etc. Exemplarily, the transmitter transmits signals, messages, information, data, etc. under the control of the processor 1402. The receiver receives signals, messages, information, data, etc. under the control of the processor 1402.

[0470] 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 above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0471] Among them, the communication interface 1401, the processor 1402, and the memory 1403 are interconnected with each other. Optionally, the communication interface 1401, the processor 1402, and the memory 1403 are interconnected through a bus 1404; the bus 1404 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 14 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0472] In an alternative embodiment, the memory 1403 is used to store programs and the like. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory 1403 may include a RAM, and may also include a non-volatile memory, such as one or more disk memories. The processor 1402 executes the application program stored in the memory 1403 to implement the above functions, thereby implementing the functions of the communication device 1400.

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

[0474] In one embodiment, when the communication device 1400 implements the functions of the data communication agent in the above embodiment, the communication interface 1401 may implement the transceiver operations performed by the data communication agent in the above embodiment; the processor 1402 may implement other operations performed by the data communication agent in the above embodiment except for the transceiver operations. For specific related descriptions, reference may be made to the relevant descriptions in the above embodiment, and details are not described herein again.

[0475] 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; the processor 1402 may implement other operations performed by the first network element in the above embodiment except for the transceiver operations. For specific related descriptions, reference may be made to the relevant descriptions in the above embodiment, and details are not described herein again.

[0476] In yet 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; the processor 1402 may implement other operations performed by the second network element in the above embodiment except for the transceiver operations. For specific related descriptions, reference may be made to the relevant descriptions in the above embodiment, and details are not described herein again.

[0477] 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, the second network element, etc. involved in the above embodiments.

[0478] An embodiment of the present application further 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 may implement a communication method provided in the above method embodiment.

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

[0480] An embodiment of the present application further provides a chip, including a processor, and the processor is used to enable the chip to implement a communication method provided in the above method embodiment.

[0481] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. 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 disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0482] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0483] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0484] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Therefore, the instructions executed on the computer or other programmable device provide for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1Steps of functions specified in one or more boxes.

[0485] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these changes and modifications.

Claims

1. A communication method, characterized in that, Applied to a data communication agent, the data communication agent is deployed in a 3GPP (Third Generation Partnership Project) 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, where the first subscription message is used to subscribe to data of a first information type; Receiving 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 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 to 4, characterized in that, The method further includes: Receiving a first message, where the first message is 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, where the second message is 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, where the third message is used to create a data consumer.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Receiving a fourth message, where the fourth message is 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 (Third Generation Partnership Project) network, and includes: Receiving a first control message from a sensing service control function network element in the 3GPP network, where the first control message is used to indicate receiving data of a first information type; Sending a first subscription message to a data communication agent in the 3GPP network, where the first subscription message is 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, where the first data is 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, where the third message is used to create a data consumer.

12. The method according to any one of claims 9-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 to 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-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