Communication method and apparatus

Abstract

The present application relates to the field of mobile communications, and provides a communication method and apparatus. The method comprises: a sensing network element can acquire capability information of a device supporting the N3GPP sensing capability, and selects a first device in response to the capability information and sensing demand information from a requesting device; the sensing network element sends a first message to the selected first device, the first message being used for requesting sensing data of N3GPP sensing; and the sensing network element receives first sensing data from the first device, wherein the first sensing data includes the sensing data of N3GPP sensing. The sensing performance can be improved on the basis of sensing data of N3GPP sensing.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

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

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

[0004] The continuous advancement of mobile communication technology and the continuous enhancement of air interface capabilities are enabling mobile networks to achieve a qualitative leap from simply providing voice, SMS, and data services to realizing the interconnection of everything. Furthermore, the continuous innovation of information technology is driving new demands and services such as artificial intelligence, immersive experiences, and digital twins, while also placing higher requirements on communication networks for information exchange. In addition to improving traditional communication capabilities, computing, perception, artificial intelligence, and security capabilities will also be provided. Among these, perception will become a key capability and characteristic of future mobile communication networks.

[0005] In order to support perception capabilities, the 3rd Generation Partnership Project (3GPP) has described the use cases and potential requirements of perception services. For example, perception application scenarios involve highways, railways, home intrusion scenarios, drone intrusion scenarios, smart parking scenarios, drone collision perception, drone route tracking, and pedestrian and vehicle flow perception. Currently, 3GPP supports the perception of target objects through 3GPP access technology. At present, based on 3GPP perception, the core network in the fifth generation (5th generation, 5G) mobile communication system can obtain perception data based on the perception of terminal devices and / or access network devices. Limited by the coverage range of perception devices, device capabilities, and the upper limit of the accuracy that can be achieved by the technology, the perception accuracy based on 3GPP perception, a single perception technology, may not meet the requirements of applications and services.

[0006] Summary of the Invention

[0007] The present application provides a communication method and apparatus for enhancing perception performance through non-3GPP (non-3GPP, N3GPP) perception technology.

[0008] In a first aspect, a communication method is provided. The method can be implemented by a perception network element. The perception network element can be an SF or a component of an SF, such as an SF-C or SF-U, or a perception server. The component in the present application can include, for example, at least one of a chip, a chip system, a processor, a transceiver, a processing unit, or a transceiver unit. Taking the execution subject as an example, the method can be implemented by the following steps: the perception network element obtains capability information of a device that supports N3GPP perception capability; the perception network element receives a perception request message from a requesting device, the perception request message being used to request perception data; the perception network element responds to the perception request message and determines a first device according to the capability information, the first device being one or more devices that support N3GPP perception capability; the perception network element sends a first message to the first device, the first message being used to request perception data perceived by N3GPP; the perception network element receives first perception data from the first device, the first perception data including perception data perceived by N3GPP.

[0009] Based on the method shown in the first aspect, the perception network element can obtain the capability information of the device that supports N3GPP perception capability, and select the first device based on the capability information and the perception requirement information from the requesting device, thereby obtaining the perception data of N3GPP perception through the selected first device. The perception performance can be improved based on the perception data of N3GPP perception.

[0010] In one possible implementation, the perception network element may select the first device based on the first perception requirement information and the capability information, so that the selected first device meets the perception requirement. As a possible embodiment, the first perception requirement information may be the same as the fourth perception requirement information carried in the perception request message, or may be obtained based on the fourth perception requirement information.

[0011] In one possible implementation, the first message includes second perception requirement information. Therefore, the first device can perform N3GPP perception based on the second perception requirement information to provide N3GPP perception data that meets the requirements. As a possible embodiment, the second perception requirement information can be the same as the fourth perception requirement information carried in the perception request message, or can be obtained based on the fourth perception requirement information.

[0012] In one possible implementation, the perception network element may obtain the capability information from the device supporting N3GPP perception capabilities, an application function, a normalized data warehouse network element, a normalized data management network element, an N3GPP perception capability storage function network element, or an access and mobility management network element. The N3GPP perception capability storage function network element may be a dedicated N3GPP perception-related storage network element. The access and mobility management network element may be an AMF corresponding to the area of ​​the device supporting 3GPP perception capabilities.

[0013] In one possible implementation, the perception network element sends a device request message and / or a device subscription message to the device, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element that supports N3GPP perception capability; wherein the device request message and / or the device subscription message includes third perception requirement information, and the third perception requirement information is used to discover devices that support N3GPP perception capability. Therefore, the perception network element can request capability information of devices that support N3GPP perception capability and meet the perception requirements through the third perception requirement information. As a possible embodiment, the third perception requirement information can be the same as the fourth perception requirement information carried in the perception request message, or can be obtained based on the fourth perception requirement information.

[0014] In one possible implementation, the perception network element may further send second perception data to the requesting device. The second perception data may be further perception data obtained based on the first perception data. For example, the second perception data may be used to determine a perception result. In addition, the second perception data may also include the perception result.

[0015] In one possible implementation, the perception network element receives 3GPP-perceived perception data from a second device, where the second device supports 3GPP perception capabilities. The perception network element generates the second perception data based on the first perception data and the 3GPP-perceived perception data. Based on this implementation, when the perception network element is a SF, the perception network element can obtain 3GPP perception data from a temporary device that supports 3GPP perception (i.e., the second device), and perform processing such as fusing and / or analyzing the 3GPP perception data with the first perception data to obtain the second perception data.

[0016] In a possible implementation, in the above implementation, the first message is also used by the first device to obtain the 3GPP-perceived perception data. At this time, the second device and the first device are the same device, or in other words, the second device may include but is not limited to the first device.

[0017] In one possible implementation, the perception network element may receive 3GPP-perceived perception data from a perception function network element. The perception network element generates the second perception data based on the first perception data and the 3GPP-perceived perception data. Based on this implementation, when the perception network element is a perception server, the perception network element may obtain 3GPP perception data from the SF, and perform processing such as fusing and / or analyzing the 3GPP perception data with the first perception data to obtain the second perception data. This application does not make specific requirements on the way in which the SF obtains the 3GPP perception data.

[0018] In a possible implementation manner, the perception network element sends a second message to the perception function network element, where the second message is used to request 3GPP perception data.

[0019] In a possible implementation, the first perception data is generated based on the N3GPP perception data and the 3GPP perception data. That is, the first perception device may fuse the 3GPP perception data and the N3GPP perception data.

[0020] In a possible implementation, the awareness request message includes fourth awareness requirement information. The fourth awareness requirement information represents the awareness requirement of the requesting device.

[0021] In one possible implementation, the perception network element may further send an address and / or data tag information for receiving the first perception data to the first device; the perception network element receives the first perception data from the first device with the destination address being the address; and / or the perception network element receives the first perception data from the first device including the data tag information. The address and / or tag may be used by the perception network element to identify that the received perception data includes N3GPP-perceived perception data.

[0022] In a second aspect, a communication method is provided. The method can be implemented by a first device. The first device may include a terminal or a base station, or may be a component of a terminal or a base station. The component in the present application may include, for example, at least one of a chip, a chip system, a processor, a transceiver, a processing unit, or a transceiver unit. Taking the execution subject as the first device as an example, the method can be implemented by the following steps: the first device receives a first message from a perception network element, the first message is used to request perception data perceived by N3GPP, and the first device is a device that supports N3GPP perception; the first device obtains first perception data in response to the first message, the first perception data includes perception data perceived by N3GPP; the first device sends the first perception data to the perception network element.

[0023] In one possible implementation, the first device may also send the capability information of the first device to the perception network element, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element, and the capability information is used by the perception network element to determine the first device.

[0024] In one possible implementation, the first device may also receive a device request message and / or a device subscription message from the perception network element; wherein the device request message and / or the device subscription message includes third perception requirement information, and the third perception requirement information is used to discover devices that support N3GPP perception capabilities.

[0025] In one possible implementation, the first message is also used to request 3GPP-perceived perception data, and the first device may also send 3GPP-perceived perception data to the perception network element; or; the first device may also generate the first perception data based on the 3GPP-perceived perception data and N3GPP-perceived perception data.

[0026] In one possible implementation, the first device may also receive the address and / or data tag information for receiving the first perception data from the perception network element; in addition, the first device may also send the first perception data with the destination address being the address to the perception network element; and / or, the first device may also send the first perception data containing the data tag information to the perception network element.

[0027] In any possible implementation of the first aspect and / or the second aspect, the device supporting N3GPP awareness capability includes: a device with N3GPP awareness capability, and / or a device connected to a device with N3GPP awareness capability.

[0028] In any possible implementation of the first aspect and / or the second aspect, the capability information of the device supporting N3GPP perception capability includes one or more of the following: supported perception area; location; indication of support for N3GPP perception capability; supported perception type; device identification; supported perception capability indicators; supported perception data fusion capability information, used to indicate support for fusion of N3GPP-perceived perception data and 3GPP-perceived perception data, and / or, used to indicate a fusion indicator of supported N3GPP-perceived perception data and 3GPP-perceived perception data.

[0029] In any possible implementation of the first aspect and / or the second aspect, one or more of the first perception demand information, the second perception demand information, the third perception demand information and the fourth perception demand information include one or more of the following information: the perception area of ​​the demand; the perception capability index of the demand; fusion demand information, used to indicate the fusion of the N3GPP-perceived perception data and the 3GPP-perceived perception data, and / or, used to indicate the fusion index of the N3GPP-perceived perception data and the 3GPP-perceived perception data of the demand; the perception type of the demand; perception service information, the perception service information is used to determine one or more of the perception area of ​​the demand, the perception capability index of the demand, the fusion demand and the perception type of the demand.

[0030] The beneficial effects of the above second aspect and its various possible implementations can be found in the description of the beneficial effects of the first aspect and its corresponding implementations, and the repeated parts will be omitted.

[0031] In a third aspect, a communication method is provided. The method can be implemented by a perception network element or a component in the perception network element, and by a perception server or a component of the perception server, wherein the perception network element is an SF. The method can be implemented by the following steps: obtaining capability information of a device supporting N3GPP perception capability; receiving a perception request message from a requesting device, wherein the perception request message is used to request perception data; in response to the perception request message, determining a first device according to the capability information, wherein the first device is one or more devices supporting N3GPP perception capability; sending a first message to the first device, wherein the first message is used to request perception data perceived by N3GPP; and receiving first perception data from the first device, wherein the first perception data includes perception data perceived by N3GPP.

[0032] The difference from the first aspect is that in the method shown in the third aspect, the perception network element can receive the perception request message from the requesting device, and the perception server can send a first message to the first device to request the first device to perform N3GPP perception. Optionally, the perception network element and / or the perception server can select the first device, and the method for selecting the first device can refer to the first aspect.

[0033] In a possible implementation manner, the device supporting N3GPP awareness capability includes: a device having N3GPP awareness capability, and / or a device connected to a device having N3GPP awareness capability.

[0034] In a possible implementation, the receiving the first perception data from the first device includes: a perception server receiving the first perception data from the first device; and the perception server sending the first perception data to a perception network element.

[0035] In one possible implementation, the obtaining of capability information of a device supporting N3GPP perception capability includes: a perception server obtaining capability information of a device supporting N3GPP perception capability; the receiving of a perception request message from a requesting device includes: the perception network element receiving the perception request message; the determining of a first device according to the capability information in response to the perception request message includes: the perception network element sending a third message to the perception server in response to the perception request message, the third message being used to request perception data perceived by N3GPP; the perception server determining the first device according to the capability information in response to the third message.

[0036] In a possible implementation, determining the first device according to the capability information includes: selecting the first device according to first perception requirement information and the capability information.

[0037] In a possible implementation, the third message includes second perception requirement information.

[0038] In one possible implementation, the obtaining of capability information of a device supporting N3GPP perception capability includes: the perception server obtaining the capability information from the device supporting N3GPP perception capability, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element.

[0039] In one possible implementation, the perception server sends a device request message and / or a device subscription message to the device, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element that supports N3GPP perception capability; wherein the device request message and / or the device subscription message includes third perception requirement information, and the third perception requirement information is used to discover devices that support N3GPP perception capability.

[0040] In one possible implementation, the capability information includes one or more of the following: supported perception areas; locations; indications of supported N3GPP perception capabilities; device identification; supported perception types; supported perception capability indicators; supported perception data fusion capability information, used to indicate support for fusion of N3GPP-perceived perception data and 3GPP-perceived perception data, and / or, used to indicate supported fusion indicators of N3GPP-perceived perception data and 3GPP-perceived perception data.

[0041] In one possible implementation, the perception network element receives a perception request message from a requesting device, where the perception request message is used to request a perception result, and the perception request message includes fourth perception requirement information; the method further includes: the perception network element sending second perception data to the requesting device.

[0042] In a possible implementation manner, the perception network element may further generate the second perception data according to the first perception data and the 3GPP-perceived perception data.

[0043] In one possible implementation, the perception network element generates second perception data based on the first perception data and the 3GPP-perceived perception data, including: the perception network element receives the 3GPP-perceived perception data from the second device, and receives the first perception data from the perception server; the perception network element generates the second perception data based on the first perception data and the 3GPP-perceived perception data.

[0044] In a possible implementation, the first message is also used by the first device to obtain the 3GPP-perceived perception data, and the second device is the same device as the first device.

[0045] In a possible implementation manner, the first perception data is generated according to the N3GPP-perceived perception data and the 3GPP-perceived perception data.

[0046] In one possible implementation, the perception network element generates the second perception data based on the first perception data and the 3GPP-perceived perception data, including: the perception network element processes the first perception data and the 3GPP-perceived perception data according to the fourth perception requirement information to generate the second perception data.

[0047] In a possible implementation, the perception request message includes fourth perception requirement information.

[0048] In one possible implementation, one or more of the first perception demand information, the second perception demand information, the third perception demand information and the fourth perception demand information include one or more of the following information: the perception area of ​​the demand; the perception capability index of the demand; fusion demand information, used to indicate the fusion of the N3GPP-perceived perception data and the 3GPP-perceived perception data, and / or, used to indicate the fusion index of the N3GPP-perceived perception data and the 3GPP-perceived perception data of the demand; the perception type of the demand; perception service information, the perception service information is used to determine one or more of the perception area of ​​the demand, the perception capability index of the demand, the fusion demand and the perception type of the demand.

[0049] In one possible implementation, the perception server may also send an address and / or data tag information for receiving the first perception data to the first device; the reception of the first perception data from the first device includes: the perception server receives the first perception data from the first device with the destination address being the address; or, the perception server receives the first perception data from the first device containing the data tag information.

[0050] The beneficial effects of the third aspect and its various possible implementations can be found in the description of the beneficial effects of the first aspect and its corresponding implementations, and the repeated parts will be omitted.

[0051] In a fourth aspect, a communication device is provided. The device can implement the method described in any aspect of the first to third aspects and any possible implementation thereof. The device has the functions of the above-mentioned perception network element, first device or perception server. For example, when implementing the method shown in the first aspect, the device is, for example, a perception network element or a functional module of a perception network element, or can be a processor in a perception network element. For another example, when implementing the method shown in the second aspect and any possible implementation thereof, the device is, for example, a first device, a perception module in the first device or a processor. For another example, when implementing the method shown in the third aspect and any possible direction thereof, the device is, for example, a perception network element or a perception server, or can be a functional module of a perception network element or a functional module of a perception server, or a component such as a processor of a perception network element or a perception server.

[0052] In an optional implementation, the device may include a module that performs the methods / operations / steps / actions described in any of the first to third aspects and any possible implementation thereof. The module may be a hardware circuit, software, or a combination of a hardware circuit and software. In an optional implementation, the device includes a processing unit (sometimes also referred to as a processing module) and a communication unit (sometimes also referred to as a transceiver module, a communication module, etc.). The transceiver unit is capable of implementing a sending function and a receiving function. When the transceiver unit implements the sending function, it may be referred to as a sending unit (sometimes also referred to as a sending module). When the transceiver unit implements the receiving function, it may be referred to as a receiving unit (sometimes also referred to as a receiving module). The sending unit and the receiving unit may be the same functional module, which is called a transceiver unit, and the functional module is capable of implementing a sending function and a receiving function; or, the sending unit and the receiving unit may be different functional modules, and the transceiver unit is a general term for these functional modules.

[0053] Exemplarily, when the apparatus is used to execute the method described in any aspect of the first to third aspects and any possible implementation thereof, the apparatus may include a communication unit and a processing unit.

[0054] In the fifth aspect, an embodiment of the present application also provides a communication device, including a processor for executing a computer program (or computer executable instructions) stored in a memory. When the computer program (or computer executable instructions) is executed, the device executes a method performed by a perception network element, a first device or a perception server in any aspect of the first to third aspects and any possible implementation thereof.

[0055] In one possible implementation, the processor and memory are integrated;

[0056] In another possible implementation, the memory is located outside the communication device.

[0057] The communication device also includes a communication interface, which is used for the communication device to communicate with other devices, such as sending or receiving data and / or signals. Exemplarily, the communication interface can be a transceiver, circuit, bus, module or other type of communication interface.

[0058] In a sixth aspect, a computer-readable storage medium is provided, which is used to store computer programs or instructions, and when the computer-readable storage medium is executed, the method shown in any aspect from the first to the third aspect and any possible implementation thereof is implemented.

[0059] In a seventh aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the method shown in any aspect from the first to the third aspect and any possible implementation thereof to be implemented.

[0060] In an eighth aspect, an embodiment of the present application further provides a communication device for executing the method in any aspect of the above-mentioned first to third aspects and any possible implementation thereof.

[0061] In the ninth aspect, a chip system is provided, which includes a logic circuit (or it can be understood that the chip system includes a processor, and the processor may include a logic circuit, etc.), and may also include an input and output interface. The input and output interface can be used to input messages and also to output messages. The input and output interfaces can be the same interface, that is, the same interface can implement both the sending function and the receiving function; or, the input and output interfaces include an input interface and an output interface, the input interface is used to implement the receiving function, that is, for receiving messages; the output interface is used to implement the sending function, that is, for sending messages. The logic circuit can be used to perform operations other than the sending and receiving functions in the methods shown in any of the first to third aspects above and any possible implementation thereof; the logic circuit can also be used to transmit messages to the input and output interface, or receive messages from other communication devices from the input and output interface. The chip system can be used to implement the methods shown in any of the first to third aspects above and any possible implementation thereof. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0062] Optionally, the chip system may further include a memory, which may be used to store instructions, and the logic circuit may call the instructions stored in the memory to implement corresponding functions.

[0063] In a tenth aspect, a communication system is provided, which may include a perception network element and a first device, wherein the perception network element may be used to perform the method of the first aspect and any possible implementation thereof, and the first device may be used to perform the method of the second aspect and any possible implementation thereof. Alternatively, the communication system may include a perception network element, a perception server, and a first device, wherein the perception network element and the perception server may be used to perform the method of the third aspect and any possible implementation thereof, and the first device may be used to perform the method of the second aspect and any possible implementation thereof.

[0064] The technical effects brought about by the above fourth to tenth aspects can be found in the description of the above first aspect and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0066] FIG2 is a schematic diagram of the architecture of another wireless communication system provided in an embodiment of the present application;

[0067] FIG3 is a schematic diagram of the architecture of another wireless communication system provided in an embodiment of the present application;

[0068] FIG4 is a schematic diagram of the architecture of another wireless communication system provided in an embodiment of the present application;

[0069] FIG5 is a flow chart of a communication method provided in an embodiment of the present application;

[0070] FIG6 is a flow chart of another communication method provided in an embodiment of the present application;

[0071] FIG7 is a flow chart of another communication method provided in an embodiment of the present application;

[0072] FIG8 is a flow chart of another communication method provided in an embodiment of the present application;

[0073] FIG9 is a flow chart of another communication method provided in an embodiment of the present application;

[0074] FIG10 is a flow chart of another communication method provided in an embodiment of the present application;

[0075] FIG11 is a flow chart of another communication method provided in an embodiment of the present application;

[0076] FIG12 is a flow chart of another communication method provided in an embodiment of the present application;

[0077] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0078] FIG14 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0079] FIG15 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0080] The technical solutions provided in the embodiments of this application can be applied to various communication systems. For example, they can be applied to LTE systems or 5G systems, as well as other future-oriented new systems. This embodiment of the application does not specifically limit this. In addition, the term "system" and "network" can be used interchangeably. The following description will only use the 5G communication system architecture as an example.

[0081] As shown in Figure 1, the 5G communication system, as standardized by the 3rd Generation Partnership Project (3GPP), includes terminal devices (e.g., user equipment (UE)), access networks (e.g., radio access networks (RAN)), and core networks (CN). Logically, the core network elements of the data network (DN) can be divided into two parts: the user plane and the control plane. The control plane is responsible for mobile network management, while the user plane is responsible for service data transmission.

[0082] Among them, terminal devices are the entry point for mobile users to interact with the network. They can provide basic computing and storage capabilities, display service windows to users, and receive user input. Next-generation terminal devices (NextGen UE) can use new air interface technologies to establish signal and data connections with the RAN, thereby transmitting control signals and service data to the mobile network. Terminal devices can include various handheld devices with wireless communication capabilities, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to wireless modems, as well as various forms of terminals, including mobile stations (MS), terminals, and soft terminals, such as water meters, electricity meters, and sensors.

[0083] RAN: Deployed close to terminal devices, it provides network access for authorized users in a specific area and determines transmission tunnels of varying quality to transmit user data based on user level and service requirements. The RAN manages its own resources, utilizing them effectively and providing access services to terminal devices on demand. It also forwards control signals and user data between terminal devices and the core network.

[0084] Core Network: Responsible for maintaining mobile network subscription data, managing mobile network elements, and providing terminal devices with session management, mobility management, policy management, and security authentication. It provides network authentication for terminal devices when they attach; allocates network resources when they request services; updates network resources when they move; provides fast recovery mechanisms when they are idle; and releases network resources when they detach. When they have service data, it provides data routing, such as forwarding uplink data to the data network; or receiving downlink data from terminal devices from the data network and forwarding it to the RAN, which then sends it to the terminal device.

[0085] Data network (DN): A data network that provides business services to users. Typically, the client is located on a terminal device, and the server is located on the data network. A data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the internet, or a proprietary network jointly deployed by operators, such as the network that provides Internet Protocol (IP) Multimedia Core Network Subsystem (IMS) services.

[0086] Among them, the core network user plane includes the user plane function (UPF), the core network control plane includes the access and mobility management function (AMF), the session management function (SMF), the network exposure function (NEF), the network function repository function (NRF), the unified data repository (UDR) network element, the unified data management (UDM) network element, the policy control function (PCF), the application function (AF), the authentication server function (AUSF), the network slice selection function (NSSF), the location management function (LMF) network slice selection authentication and authorization function (NSSAAF), etc.

[0087] The core network control plane adopts a service-oriented architecture. Interactions between control plane network elements are based on service calls, replacing the traditional point-to-point communication. In a service-oriented architecture, control plane network elements expose services to other control plane network elements for invocation. In point-to-point communication, the communication interface between control plane network elements stores a set of specific messages that can only be used by the control plane network elements at both ends of the interface.

[0088] The following describes the functions of the functional entities in the core network:

[0089] 1. Session Management Network Element: This element is primarily used for session management, IP address allocation and management of terminal devices, selection of endpoints for manageable user equipment plane functions, policy control, or charging function interfaces, and downlink data notification. In 5G communications, the session management network element may be an SMF network element. In future communications such as 6G communications, the session management function network element may still be an SMF network element or have other names, which are not limited in this application. Nsmf is a service-based interface provided by SMF, through which SMF can communicate with other network functions.

[0090] 2. Access management network element, or access and mobility management network element: mainly used for mobility management and access management, etc. For example, it can be the mobility management entity (MME) function in the 4G communication network or the AMF network element in the 5G network. In future communications such as 6G communications, the access management network element can still be an AMF network element, or have other names, which is not limited in this application. Namf is a service-based interface provided by AMF, and AMF can communicate with other network functions through Namf.

[0091] 3. Network Open Element: This element is used to securely expose services and capabilities provided by 3GPP network functions to the outside world. In 5G communications, the Network Open Element may be an NEF element. In future communications, such as 6G communications, the Network Open Function Element may still be an NEF element, or have other names, which are not limited in this application. Nnef is the service-based interface provided by the NEF, through which the NEF can communicate with other network functions.

[0092] 4. Network storage network element: used to provide service registration, discovery and authorization, and maintain available network function (NF) instance information, which can realize on-demand configuration of network functions and services and interconnection between NFs. In 5G communications, the network storage network element can be an NRF network element. In future communications such as 6G communications, the network storage function network element can still be an NRF network element, or have other names, which is not limited in this application. Nnrf is a service-based interface provided by NRF. NRF can communicate with other network functions through Nnrf.

[0093] 5. Policy Control Element: A unified policy framework for guiding network behavior, providing policy rule information for control plane function elements (such as AMF, SMF, etc.). In 5G communications, the policy control element can be a PCF element. In future communications such as 6G communications, the policy control element can still be a PCF element, or have other names, which are not limited in this application. Among them, Npcf is a service-based interface provided by PCF, and PCF can communicate with other network functions through Npcf.

[0094] 6. Data Management NE: This element is used to handle user identification, subscription, access authentication, registration, or mobility management. In 5G communications, the data management NE may be a UDM NE. In future communications, such as 6G communications, the data management NE may still be a UDM NE or have other names, which are not limited in this application. Nudm is a service-based interface provided by the UDM, through which the UDM can communicate with other network functions.

[0095] 7. Application Function Network Element: This element is used for routing application-affected data, accessing network open functions, or interacting with the policy framework for policy control. In 5G communications, the application function network element may be an AF network element. In future communications such as 6G communications, the application function network element may still be an AF network element or have other names, which are not limited in this application. Naf is a service-based interface provided by the AF, through which the AF can communicate with other network functions. The AF can be a third-party functional entity or an application server deployed by the operator.

[0096] 8. User plane network element: used for packet routing and forwarding, or quality of service (QoS) processing of user plane data. In 5G communications, the user plane network element may be a user plane function (UPF) network element. In future communications such as 6G communications, the user plane network element may still be a UPF network element or have other names, which is not limited in this application.

[0097] 9. Authentication Service Element: This is primarily used for user authentication. In 5G communications, the authentication service element may be an AUSF element. In future communications, such as 6G communications, the authentication service element may still be an AUSF element, or have other names, which are not limited in this application. Nausf is a service-based interface provided by AUSF, through which AUSF can communicate with other network functions.

[0098] 10. Network slice selection function network element: used to select network slices for terminal devices. In 5G communications, the network slice selection function network element can be an NSSF network element. In future communications such as 6G communications, the network slice selection function network element can still be an NSSF network element, or have other names. This application does not limit this.

[0099] It is understandable that the core network may also include other network elements, and this application does not limit this.

[0100] It should be noted that the names of the network elements and the interfaces between them in Figure 1 are only examples. In specific implementations, the names of the network elements and the interfaces between them may be other, and the embodiments of this application do not specifically limit this.

[0101] As shown in Figure 1, the terminal device can access the 5G system through access network equipment such as RAN. The terminal device can communicate with the AMF network element through the next generation network (NG) 1 interface (referred to as N1), the access network device communicates with the AMF network element through the N2 interface (referred to as N2), the access network device communicates with the UPF network element through the N3 interface (referred to as N3), the AMF network element communicates with the SMF network element through the N11 interface (referred to as N11), the AMF network element communicates with the UDM network element through the N8 interface (referred to as N8), the AMF network element communicates with the AUSF network element through the N12 interface (referred to as N12), the AMF network element communicates with the PCF network element through the N15 interface (referred to as N15), the SMF network element communicates with the PCF network element through the N7 interface (referred to as N7), the SMF network element communicates with the UPF network element through the N4 interface (referred to as N4), the NEF network element communicates with the SMF network element through the N29 interface (referred to as N29), and the UPF network element accesses the data network through the N6 interface (referred to as N6). network, DN).

[0102] It should be noted that the names of the network elements and the interfaces between them in Figure 1 are only examples. In specific implementations, the names of the network elements and the interfaces between them may be other, and the embodiments of this application do not specifically limit this.

[0103] Access network equipment can be wirelessly connected to a communication system, providing wireless access to terminal devices. It can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in fifth-generation (5G) mobile communication systems, a next-generation base station in sixth-generation (6G) mobile communication systems, a base station in future mobile communication systems, a Wi-Fi system, a long-range radio (LoRa) system, or an access node in an Internet of Vehicles system. Access network equipment can also be a module or unit that performs some of the functions of a base station.

[0104] In some deployments, the access network equipment may include a centralized unit (CU) and a distributed unit (DU), or a remote radio unit (RRU) and an active antenna unit (AAU). The access network equipment may also include a radio unit (RU). The CU implements some of the functions of the access network equipment, while the DU implements some of the functions of the access network equipment. For example, the CU implements the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, while the DU implements the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. Since RRC layer information will eventually become PHY layer information, or be converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling or PHCP layer signaling, can also be considered to be sent by the DU, or by the DU+RU. It is understood that the network device may be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU may be classified as a network device in the access network RAN, or may be classified as a network device in the core network CN, without limitation herein.

[0105] The access network device may also include an active antenna unit (AAU) and / or a baseband unit (BBU). Among them, the BBU is mainly responsible for baseband signal processing. The AAU implements some physical layer processing functions, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this architecture, high-level signaling such as RRC layer signaling can also be considered to be sent by the DU, or, sent by the DU+AAU. It can be understood that the access network device can be a device including one or more of the CU node, DU node, and AAU node.

[0106] In addition, the core network elements may also include sensing function (SF) network elements, referred to as SF. The SF can utilize access network equipment and / or terminal equipment for sensing. It is understood that the sensing in this application includes 3GPP sensing and N3GPP sensing, and the current SF mainly involves 3GPP sensing.

[0107] Optionally, the SF may be co-located with other network elements, or the functions of the SF may be specifically implemented by other network elements, or the SF may be independently configured, which is not limited in this embodiment of the present application. The SF may also be referred to as a sensing control function (SCF) or other possible names. Optionally, the SF may also be deployed in a non-core network, which is not limited in this embodiment of the present application.

[0108] As shown in Figure 2, the perception control signaling between SF and access network equipment and / or terminal equipment is transmitted through AMF. The perception measurement data obtained by the access network equipment / terminal equipment can be transmitted to SF via the control plane or user plane. The user plane can be forwarded via UPF or directly transmitted to SF. In addition, it is necessary to support perception charging in the terminal device execution and access network device execution perception scenarios.

[0109] Optionally, as shown in Figure 2, SF sets interfaces and interacts with core network elements such as AMF, NEF, UDM, NWDAF, PCF, and UPF. The specific definitions are as follows:

[0110] NS1: An NS1 interface is set up between the SF and the AMF, which can transmit perception control signaling. For scenarios where the control plane uploads perception measurement data, this interface can also transmit perception measurement data.

[0111] NS2: An NS2 interface is set up between the SF and the NEF. This interface can transmit signaling messages between the SF and the service-side AF via the NEF, and at the same time open the perception information to the AF.

[0112] NS3: An NS3 interface is set up between SF and UDM, through which authentication or authorization can be achieved, and terminal device perception contract information, service AMF information or other information can be obtained.

[0113] NS4: An NS4 interface is set up between the SF and the NWDAF. Through this interface, the SF and the NWDAF can jointly complete artificial intelligence (AI) processing related to perception services.

[0114] NS5: An NS5 interface is set up between the SF and the PCF. Through this interface, the SF can transmit messages or signaling such as the perception requirements, QoS requirements or perception information of the perception service to the PCF. The PCF decides and generates the policy and charging control (PCC) policy related to the perception service.

[0115] NS6: SF sets up NS6 interface with user plane function. Perception measurement data can be directly transmitted from access network equipment to SF via user plane function, or indirectly forwarded to SF via UPF. If the access network equipment performs perception and forwards the data via UPF, UPF needs to be modified to support data transmission at the granularity of access network equipment.

[0116] In addition to the interfaces set above, existing communication interfaces (such as N1, N2, N5, N8, N33, etc.) can also support the transmission of perception service related information, such as authentication information, perception service type, perception service quality requirements, perception measurement data or perception information, etc.

[0117] In addition, SF can also be connected to LMF through an interface. In addition, SF can also be installed together with LMF.

[0118] In addition, as shown in Figure 3, when the SF adopts a control plane-user plane separation architecture, the SF control plane (SF-control plain, SF-C) network element and the SF user plane (SF-user plain, SF-U) network element, where the SF-C network element can be simply referred to as SF-C, and the SF-U network element can be simply referred to as SF-U. It can be understood that when the SF adopts a control plane-user plane separation architecture, the SF-U can be used to perform perception data processing, for example, generating or obtaining perception information based on perception data provided by access network equipment; and the SF-C can be used to perform other control plane signaling processing, such as obtaining perception requests, or for signaling and data exchange and transmission between the SF and other network elements.

[0119] As shown in FIG4 , the SF may also be connected to the access network device via the NS1 interface.

[0120] SF can obtain the perception requirements from the requesting device (or demander, requestor) of the perception service. The requesting device of the perception service can be an AF network element, an external application server (AS), an access network device, or a terminal device. After obtaining the perception requirements, SF can control the execution object of the perception service to detect and / or collect perception data. The execution object of the perception service may include one or more access network devices and / or one or more terminal devices. The perception requirements of AF or AS can be sent to SF via NEF.

[0121] Taking the access network device as an example, the access network device can perform 3GPP sensing operations to obtain sensing data. The sensing operations may include, for example, sending sensing signals and receiving echo signals. A sensing signal is a signal used to sense (or detect) a sensed target (or target object). The sensing signal is also called a detection signal, a linear frequency modulation signal, an optical frequency division multiplexing (OFDM) wave, a frequency-modulated continuous wave (FMCW), etc. An echo signal refers to a signal reflected by the target object from the sensing signal. For example, the access network device may perform certain processing based on the echo signal to generate (or replace it with determining or obtaining, etc.) sensing data. After obtaining sensing data through detection, the access network device may send the sensing data to the SF, which processes the sensing data to obtain sensing information and provides the sensing information to the device requesting the sensing service. The sensing information may also be called a sensing result. For example, the SF may process the sensing data based on the sensing requirements of the device requesting the sensing service to obtain sensing information.

[0122] Perception data, for example, includes point cloud data collected / collected / acquired by access network devices and / or terminal devices. Perception data may include at least one of the following information: speed, distance, angle, coordinates, time, energy, etc. In other words, the perception data provided by the access network device to the SF may specifically be point cloud data, or the aforementioned speed, distance, and other information obtained after processing the point cloud data by the access network device and / or terminal device. Coordinates in this application may include longitude and latitude and / or geographic coordinates. Time in this application may include the timestamp of each sampling point data. Energy in this application may include the echo energy contained in each sampling point data. Perception information can be obtained based on point cloud information through data processing methods such as cluster analysis. Perception information may include the presence or absence of targets, target type, number of targets, target characteristics (such as shape), trajectory, location, speed, direction / angle, environmental reconstruction or environmental imaging, positional relationships among multiple targets, whether a target has intruded into a specific area, whether a target has deviated from a predetermined trajectory, whether the distance between targets is less than a specific threshold, and whether there is a collision risk among multiple targets.

[0123] There are various ways in which the access network device can provide the SF with sensory data. As one possible implementation, the SF can establish a sensory data transmission channel for the access network device, which can then send the sensory data to the SF via the channel. Furthermore, the SF processes the sensory data based on sensory requirements to obtain sensory information, and then sends the sensory information to the device requesting the sensory service. For example, the sensory data transmission channel can include: a channel between the access network device and the UPF network element, a channel between the UPF network element and the SF, and a channel between the SF and the device requesting the sensory service. In other words, the sensory data transmission path can be: the access network device sends the sensory data to the UPF network element, the SF obtains sensory information based on the sensory data, and then sends the sensory information to the device requesting the sensory service. In the above transmission path, the data in brackets represents data transmission or processing. For example, in the above example transmission path, other network elements may be included between the network elements. For example, the path between the SF and the device requesting the sensory service may also include other possible network elements, such as the NEF, but the specific implementation is not limited. In the embodiments of this application, the specific implementation of establishing the sensory data transmission channel is not limited, and "channel" can be replaced by "tunnel" or other possible names.

[0124] It is understandable that the SF in the above transmission path can be replaced by a perception data processing function network element or a perception function network element. That is, the perception data processing function network element can convert the perception data into perception information that can be sent to the device requesting the perception service. Specifically, the SF can establish a perception data transmission channel for the access network device, and then the access network device can send the perception data to the SF. Further, the SF processes the perception data according to the perception requirements to obtain perception information and sends the perception information to the device requesting the perception service. In other words, the transmission path of the perception data can be: the access network device collects the perception data and sends the perception data to the UPF, the UPF sends the perception data to the SF, the SF obtains the perception information based on the perception data, and then sends the perception information to the device requesting the perception service.

[0125] Furthermore, as sensing scenarios continue to expand, the accuracy of 3GPP sensing alone may not meet application and service requirements due to limitations in the coverage, capabilities, and accuracy limits of sensing devices. Therefore, combining N3GPP sensing with 3GPP sensing is being considered to improve sensing performance.

[0126] In this application, N3GPP perception may include perception performed by devices such as cameras, radars, wireless fidelity (WIFI), Bluetooth, ZigBee, near field communication (NFC), temperature sensors, and humidity sensors. In N3GPP perception, the perception device can be used to perform N3GPP perception measurements to obtain perception data. For example, in a scenario where a radar performs N3GPP perception measurements, the radar is an N3GPP perception device, and the radar can be used to send radar signals and perform perception measurements based on the echo signals of the radar signals. This application does not require the specific method of performing N3GPP perception measurements and obtaining N3GPP perception.

[0127] In order to improve the perception performance, the present application provides a communication method for acquiring perception data of N3GPP perception, so as to improve the performance of 3GPP perception through the perception data of N3GPP perception.

[0128] The communication method described herein may include a perception network element and a device supporting N3GPP perception capabilities. The perception network element may be used to request, instruct, or control the device supporting N3GPP perception capabilities to perform N3GPP perception. The device supporting N3GPP perception capabilities may perform N3GPP perception and provide N3GPP perception data to the perception network element.

[0129] In this application, the perception network element can be a SF, a perception server, or the functions of the perception network element can be implemented by two entities, the SF and the perception server. The perception server can be a server for supporting or providing perception services, such as an AS, AF, cloud platform, or edge platform for supporting or providing perception services.

[0130] In addition, the device supporting N3GPP perception capability may include a device with N3GPP perception capability and / or a device connected to a device with / equipped with N3GPP perception capability. The device with N3GPP perception capability refers to a device that supports performing N3GPP perception measurements and obtaining N3GPP perception data.

[0131] Exemplarily, a device supporting N3GPP perception capabilities may be a 3GPP device, or may include a 3GPP device and an N3GPP device. The 3GPP device supports accessing the network via a 3GPP method and thereby connecting to a perception network element. The 3GPP device may be, for example, a terminal device or an access network device.

[0132] N3GPP devices may have N3GPP perception capabilities, and the N3GPP devices themselves may not support network access via 3GPP, but may only connect to perception network elements or the network where the perception network elements are located through 3GPP devices connected to the N3GPP devices. For example, N3GPP devices may connect to 3GPP devices via 3GPP and / or N3GPP, for example, via wired or Bluetooth connections. N3GPP devices may perform N3GPP perception through cameras, radars, Wi-Fi, Bluetooth, ZigBee, NFC, temperature sensors, humidity sensors, and the like, and provide the perception data to the 3GPP devices, which then provide the N3GPP-perceived perception data to the perception network elements.

[0133] In one possible scenario, the 3GPP device itself may have N3GPP awareness capabilities, so when not connected to an N3GPP device, the 3GPP device with N3GPP awareness capabilities may function as a device with N3GPP awareness capabilities. In another possible scenario, the 3GPP device with N3GPP awareness capabilities may also be connected to an N3GPP device, i.e., the N3GPP device may function as a device with N3GPP awareness capabilities, and the 3GPP device may also function as a device connected to a device with N3GPP awareness capabilities (i.e., an N3GPP device), in which case the devices supporting N3GPP awareness capabilities are the 3GPP device and the N3GPP device. In another possible scenario, when the 3GPP device itself does not have N3GPP awareness capabilities and the 3GPP device is connected to an N3GPP device, the 3GPP device may function as a device connected to a device with N3GPP awareness capabilities, in which case the device supporting N3GPP awareness capabilities may be the 3GPP device.

[0134] As shown in FIG5 , taking the sensing network element as an SF as an example, a communication method provided in this application may include the following steps:

[0135] S101: SF obtains capability information of a device supporting N3GPP perception capability.

[0136] Hereinafter, the capability information of a device supporting N3GPP perception capability will be referred to as capability information.

[0137] It is understood that the capability information in this application may include capability information of devices with N3GPP awareness capabilities. Therefore, when a 3GPP device has N3GPP awareness capabilities, the capability information reported by the 3GPP device may include the capability information of the 3GPP device; and / or, when a 3GPP device is connected to an N3GPP device, the capability information reported by the 3GPP device is the capability information of the N3GPP device. In other words, when the device supporting N3GPP awareness capabilities is a 3GPP device, the capability information may include the capability information of the 3GPP device; when the device supporting N3GPP awareness capabilities is a 3GPP device and an N3GPP device, the capability information may include the capability information of the 3GPP device and the capability information of the N3GPP device, respectively. It is understood that 3GPP devices and N3GPP devices may be collectively referred to as devices.

[0138] Optionally, capability information may include one or more of the following:

[0139] (1) An indication of whether the N3GPP perception capability is supported, which can be used to indicate whether the 3GPP device and / or the N3GPP device supports the N3GPP perception capability. For example, when the 3GPP device is not connected to the N3GPP device, if the 3GPP device supports the N3GPP perception capability, the capability information reported by the 3GPP device may carry an indication indicating support for the N3GPP perception capability; when the 3GPP device does not support the N3GPP perception capability, the capability information may carry an indication indicating that the N3GPP perception capability is not supported. For another example, when the 3GPP device is connected to one or more N3GPP devices, since the N3GPP device supports the N3GPP perception capability, the capability information may carry an indication indicating support for the N3GPP perception capability.

[0140] For example, the capability information may include a field indicating whether the N3GPP awareness capability is supported. For example, the field may include 1 bit, and a value of 0 indicates that the N3GPP awareness capability is not supported; a value of 1 indicates that the N3GPP awareness capability is supported.

[0141] The indication of whether the N3GPP perception capability is supported may be mandatory content of capability information reported by a 3GPP device.

[0142] (2) Location information, or simply referred to as location, can be used to indicate the location of the 3GPP device and / or N3GPP device. The location information may include geographic coordinate information or area information. For example, the geographic coordinate information may be the location of the 3GPP device and / or N3GPP device represented by latitude and longitude information and / or distance information. For another example, the area information is the 3GPP area information or identifier (e.g., cell identifier, tracking area ID (TAI), access network device identifier) ​​where the 3GPP device and / or N3GPP device is located.

[0143] (3) Supported perception areas may indicate areas that the 3GPP device and / or N3GPP device supports for perception, for example, the area includes the 3GPP perception area and / or N3GPP perception area that the 3GPP device supports for perception, and / or, includes the N3GPP perception area that the N3GPP device supports for perception. The perception area may be represented by geographic range information and / or area information. For example, the geographic range information may be an area range represented by latitude and longitude information and / or distance information. The area information may be information or identification of the 3GPP area where the perception range of the 3GPP device and / or N3GPP device is located, for example, the area information may be a cell identification list, a TRP identification list, a CU identification list, a DU identification list, an RRU identification list, an AAU identification list, an access network device identification or a TAI list and other information. In the present application, the list may include one or more items of information, for example, the cell identification list may include one or more cell identifications.

[0144] It is understood that there is a certain correlation between location information and supported perception areas, so the perception areas supported by a device can be inferred based on the device's location information. In addition, when the capability information includes area information, the area information can represent both location information and supported perception areas.

[0145] (4) Supported perception types, which can be used to indicate what type of perception the 3GPP device and / or N3GPP device supports. For example, it can be used to indicate support for 3GPP perception and / or support for N3GPP perception.

[0146] Furthermore, if N3GPP sensing is supported, the sensing type may be used to indicate which N3GPP sensing types are supported by the 3GPP device and / or N3GPP device. For example, the supported N3GPP sensing type may be used to indicate support for N3GPP sensing via a camera, support for N3GPP sensing via radar, or support for other types of N3GPP sensing. In this case, the supported sensing type may not explicitly indicate support for N3GPP sensing, but rather may indicate support for N3GPP sensing by indicating the specific supported N3GPP sensing type.

[0147] The supported perception types may include fields or information corresponding to the perception types, implicitly indicating the supported perception types. For example, field 00 indicates support for 3GPP perception, field 01 indicates support for N3GPP perception, and field 10 indicates support for both 3GPP perception and N3GPP perception. Furthermore, when N3GPP perception is supported, additional fields may be used to indicate the supported N3GPP perception types, for example, by using a bitmap to indicate supported or unsupported types among multiple N3GPP perception types.

[0148] (5) Supported perception capability indicators, which may also be referred to as perception capability key performance indicators (KPIs). Supported perception capability indicators may be used to indicate the 3GPP perception performance and / or N3GPP perception performance supported by the 3GPP device. And / or, the supported perception capability indicators may also indicate the N3GPP perception performance supported by the N3GPP device. The supported perception performance may be a performance parameter indicating supported perception accuracy. For example, if the 3GPP device and / or the N3GPP device supports N3GPP perception, the perception capability indicator may include parameters such as camera pixels, resolution, or rotation angle, or may include performance parameters such as radar accuracy.

[0149] (6) Supported perception data fusion capability information can be used to indicate whether the 3GPP device and / or N3GPP device supports the fusion of N3GPP perception data and 3GPP perception data; on the other hand, when data fusion is supported, it can be used to indicate the data fusion indicators supported by the 3GPP device and / or N3GPP device.

[0150] The data fusion indicator can indicate the level of data fusion, that is, it can be used to indicate which levels of perception data are supported for fusion. The level can also be replaced by protocol layer, level, or level. For example, the data fusion indicator can be used to indicate support for data fusion at the point cloud data level, that is, deduplication and noise reduction operations are performed on the original N3GPP perception data and 3GPP perception data to obtain point cloud data in the form of three-dimensional coordinates, and the point cloud data in the form of three-dimensional coordinates are fused. For example, the point cloud data in the form of N3GPP three-dimensional coordinates is merged with the point cloud data in the form of 3GPP three-dimensional coordinates. For another example, the data fusion indicator can be used to indicate support for fusion at the perception object rendering level (e.g., two-dimensional or three-dimensional image display layer), for example, cluster analysis is performed on the N3GPP point cloud data to obtain object-level analysis results, and cluster analysis is performed on the 3GPP point cloud data to obtain object-level analysis results or perception results, and then the analysis results are merged to obtain, for example, two-dimensional or three-dimensional image layer data. It can be understood that the perception object (object) rendering layer can be perception information or data obtained through processing such as cluster analysis based on point cloud data.

[0151] As an example, the data fusion at the point cloud data level is performed on the point cloud data in the form of three-dimensional coordinates. As shown in Table 1, the point cloud data in the form of three-dimensional coordinates may include the information elements (IEs) or information groups shown in Table 1.

[0152] Table 1

[0153] When fusing point cloud data in the form of three-dimensional coordinates, point cloud data in the form of three-dimensional coordinates can be obtained respectively based on the perception data perceived by 3GPP and the perception data perceived by N3GPP, and then the point cloud data in the form of three-dimensional coordinates can be fused.

[0154] As another example, the fusion of point cloud data at the object mapping level can be, for example, the fusion of measurement results such as the presence or absence of a target, target type, number of targets, target characteristics, trajectory, position, speed, direction / angle, environmental reconstruction, or environmental imaging, the position relationship of multiple targets, whether the target invades a specific area, whether the target deviates from the predetermined trajectory, whether the distance between targets is less than a specific threshold, and whether there is a risk of collision between multiple targets.

[0155] Taking the trajectory as an example, the fusion of point cloud data at the object drawing level can be the fusion of one or more of the information shown in Table 2.

[0156] Table 2

[0157] In addition, the data fusion indicator may also indicate which types of data are supported for fusion. For example, if only the fusion of point cloud data collected by the camera and the perception data of 3GPP perception is supported, the data fusion indicator may indicate that only the fusion of the perception data collected by the camera is supported.

[0158] (7) Supported perception service information. The supported perception service information is used to indicate or determine the perception services supported by the 3GPP device and / or N3GPP device. The perception service may correspond to, be used to indicate or determine one or more of the perception areas, supported perception types, supported perception capability indicators, and supported data fusion capability information supported by the 3GPP device and / or N3GPP device. For example, the perception service information is associated with one or more of the perception areas, supported perception types, supported perception capability indicators, and supported data fusion capability information supported by the 3GPP device and / or N3GPP device. Therefore, the supported perception service information may be used to deduce or determine one or more of the perception areas, supported perception types, supported perception capability indicators, and supported data fusion capability information supported by the required 3GPP device and / or N3GPP device. The association relationship may be predefined, or may be indicated by a network element such as an SF or a server, or may be indicated by a device supporting N3GPP perception capability. This application does not make specific requirements. Optionally, the perception service information may include an identifier of the perception service, device information, information of an N3GPP device, or type information of the perception service.

[0159] (8) Device identification, which can be used to identify 3GPP devices and / or N3GPP devices. The device identification may include the identification of the 3GPP device and / or the identification of the N3GPP device. For example, when the 3GPP device is a terminal device, the device identification may be the UE identification of the terminal device, such as the generic public subscription identifier (GPSI); or, when the 3GPP device is an access network device, it may be the access network device identification, IP address, control plane protocol address, user plane tunnel protocol address, etc. of the 3GPP device. Optionally, the device identification may also include the identification of the N3GPP device to distinguish different N3GPP devices, such as the device MAC address, the data link layer, i.e., layer 2 (L2) address, the device SN number, etc.

[0160] Optionally, when a 3GPP device is connected to an N3GPP device, the capability information may carry an identifier of the 3GPP device and an identifier of the N3GPP device, which are used to mark the capability information of the 3GPP device and the capability information of the N3GPP device, respectively. For example, when the capability information includes a capability information set of the 3GPP device (such as an indication of whether the 3GPP device supports N3GPP perception capabilities, location information, supported perception areas, supported perception types, supported perception data fusion capability information, supported perception capability indicators, or supported perception service information) and a capability information set of the N3GPP device (such as an indication of whether the N3GPP device supports N3GPP perception capabilities, location information, supported perception areas, supported perception types, supported perception data fusion capability information, supported perception capability indicators, or supported perception service information), the capability information set of the 3GPP device may further include the identifier of the 3GPP device, and the capability information set of the N3GPP device may further include the identifier of the N3GPP device.

[0161] As an example in this application, regardless of whether N3GPP perception is supported, a 3GPP device may send capability information after going online or after a change in perception capabilities. Going online may refer to turning on the 3GPP device and accessing the network via a 3GPP method. Furthermore, a change in perception capabilities may be caused by a change in the N3GPP device to which the 3GPP device is connected, or by a change in perception capability information such as the registered perception area, location, supported perception capability indicators, or supported converged capabilities of the 3GPP device and / or N3GPP device.

[0162] It is understood that, in one possible scenario, devices supporting N3GPP awareness capabilities may include 3GPP devices and N3GPP devices, wherein the 3GPP device itself may not have N3GPP awareness capabilities, but one or more N3GPP devices connected to it may have N3GPP awareness capabilities. In this case, the capability information reported by the 3GPP device includes capability information of the N3GPP devices. In addition, the capability information may also include an identifier or information (such as a MAC address, etc.) of each N3GPP device and / or an identifier of the 3GPP device supporting N3GPP awareness capabilities.

[0163] Optionally, a device supporting N3GPP sensing capabilities can connect to multiple N3GPP devices. These N3GPP devices can support the same type of N3GPP sensing, such as radar sensing. Furthermore, the sensing capabilities of these N3GPP devices can be the same or different. Furthermore, a device supporting N3GPP sensing capabilities can also connect to multiple N3GPP devices supporting different types of N3GPP sensing. The type of N3GPP device here refers to the N3GPP sensing method or type supported by the N3GPP device.

[0164] In another possible scenario, the 3GPP device itself may have N3GPP perception capability, and the device supporting N3GPP perception capability is the 3GPP device. In this case, the capability information reported by the device supporting N3GPP perception capability may be the N3GPP perception capability information of the device supporting N3GPP perception capability itself.

[0165] Another possible scenario can be understood as a combination of the above two scenarios, that is, devices supporting N3GPP-aware capabilities may include 3GPP devices and N3GPP devices, where the 3GPP device supports both N3GPP-aware types and is connected to one or more N3GPP devices. In this case, the capability information reported by the 3GPP device includes its own N3GPP-aware capability information and the N3GPP-aware capability information of one or more connected N3GPP devices. Optionally, the capability information in this case may also include 3GPP-aware capability information of the 3GPP device.

[0166] In one possible implementation of S101, the SF may obtain capability information from a 3GPP device and / or a capability information storage device. The capability information storage device may be a network element or device for collecting and storing capability information. For example, the capability information storage device may be an application function, a UDM, a UDR, an N3GPP-aware capability storage function network element, or an AMF.

[0167] The N3GPP Perception Capability Storage Functional Network Element, also known as the N3GPP Perception Repository or N3GPP-NRF, can be independent of existing core network elements such as the AMF, UDR, UDM, NRF, or AF, or can be integrated with existing core network elements such as the NRF, without specific limitations. 3GPP devices can be predefined or preconfigured to report capability information to the N3GPP Perception Capability Storage Functional Network Element.

[0168] Optionally, the SF may send a device request message, or a perception device request message, to the 3GPP device and / or the capability information storage device. The perception device request message is used to request a device that supports N3GPP perception capabilities. This request triggers the 3GPP device and / or the capability information storage device to send information about the device that supports N3GPP perception capabilities to the SF. For example, the device information includes a device identifier and device capability information, where the device identifier is used to distinguish different devices. In this case, the capability information may include at least one of an indication of whether N3GPP perception capabilities are supported, location information, supported perception areas, supported perception types, supported perception capability indicators, supported perception data fusion capability information, and supported perception service information. Alternatively, the device information may include capability information, in which case the capability information includes a device identifier to distinguish different devices. In addition, the capability information may also include an indication of whether N3GPP perception capabilities are supported, location information, supported perception areas, supported perception types, supported perception capability indicators, supported perception data fusion capability information, and at least one of supported perception service information, so that after receiving a perception device request message from the SF, the collected capability information or device identifier and capability information can be sent to the SF.

[0169] In addition, the SF may send a device subscription message, also known as a perception device subscription message, to the 3GPP device and / or capability information storage device. The perception device subscription message may be used to subscribe to devices that support N3GPP perception capabilities. For example, for a 3GPP device, if capability information has already been provided to the SF, then upon receiving the perception device subscription message, the 3GPP device may provide the changed capability information to the SF when the perception capability changes. For another example, for a capability information storage device, upon receiving a perception device subscription message, the capability information collected within a period of time after receiving the perception device subscription message may be sent to the SF.

[0170] In addition, in the scenario where an interface exists between the SF and an access network device, the SF can obtain the capability information of the 3GPP device through the interface between the SF and the access network device. The 3GPP device can be the access network device or a terminal device connected to the access network device.

[0171] Taking the capability information storage device as AMF as an example, the terminal device and / or access network device, as a 3GPP device, can provide capability information to the AMF during the registration process with the AMF. As an example of SF obtaining capability information from AMF, SF can send a perception device request message to AMF, and AMF can provide the capability information obtained from the terminal device and / or access network device to SF. As another example of SF obtaining capability information from AMF, SF can send a subscription message to AMF, and after accepting the subscription, AMF can provide SF with the capability information of 3GPP devices that are newly online or whose perception capabilities have changed.

[0172] Optionally, the above perception device request message and / or perception device subscription message may carry perception requirement information of N3GPP perception (for the convenience of distinguishing multiple perception requirement information in this application, the perception requirement information here may be referred to as third perception requirement information), which is used to indicate the discovery of devices that support N3GPP perception capabilities. Accordingly, the 3GPP device and / or capability information storage device may provide the SF with capability information of devices that meet the requirements based on the third perception requirement information. For example, the capability information provided to the SF by the 3GPP device and / or capability information storage device is capability information that meets the third perception requirement information, so that the SF can obtain capability information that meets the requirements and improve perception reliability.

[0173] It can be understood that the first perception demand information, the second perception demand information, the third perception demand information and the fourth perception demand information involved in this application may be the same or different.

[0174] The third perception requirement information can be determined based on the fourth perception requirement information. For example, the third perception requirement information can be the same as the fourth perception requirement information, or can be obtained based on the fourth perception requirement information. The fourth perception requirement information can optionally be included in the perception request message shown in S102, that is, the fourth perception requirement information can represent the perception requirement of the requesting device. The third perception requirement information can also be independent of the fourth perception requirement information, for example, generated by the SF based on its own decision and / or configuration information, without specific limitation.

[0175] Taking the third perception demand information as an example, the perception demand information in this application may include one or more of the following information:

[0176] (1) The required sensing area, which may be referred to as a target area, may be used to indicate the area, location, or range where sensing is required. For example, the required sensing area may include geographic coordinate information or regional information for the required sensing. For example, the geographic coordinate information may be latitude and longitude information. For another example, the regional information may be 3GPP regional information or identifier, such as a cell identifier, a TRP identifier, a CU identifier, a DU identifier, an RRU identifier, an AAU identifier, an access network device identifier, or a TAI.

[0177] (2) The required perception type, which may be referred to as the target perception type, may be used to indicate the required perception type and / or type of perception data. For example, the required perception type may be used to indicate that 3GPP perception and / or N3GPP perception is required, or the required perception type may be used to indicate that the required perception data is 3GPP-perceived perception data and / or N3GPP-perceived perception data. In addition, 3GPP perception and / or N3GPP perception may be performed by default. For example, when the requirement for 3GPP perception or N3GPP perception is not explicitly indicated, 3GPP perception and / or N3GPP perception may be used by default to obtain perception data that meets other perception requirements.

[0178] Optionally, the required perception type may further indicate the type of N3GPP perception that needs to be performed, such as indicating that radar perception is required. For example, a bitmap may be used to indicate supported or unsupported types among multiple N3GPP perception types.

[0179] (3) Required perception capability indicator, which may be referred to as a target KPI, may be used to indicate the required 3GPP perception performance and / or N3GPP perception performance. For example, the required perception capability indicator may indicate the required perception accuracy.

[0180] (4) Fusion requirement information, used to indicate whether it is necessary to fuse the perception data perceived by N3GPP and the perception data perceived by 3GPP, and / or used to indicate the required fusion index of the N3GPP perception data and the 3GPP perception data.

[0181] Among them, the data fusion index can indicate the level at which data fusion is required.

[0182] In addition, the data fusion indicator can also indicate which types of data need to be fused. For example, when only the point cloud data collected by the camera and the perception data of 3GPP perception need to be fused, the data fusion indicator can indicate that only the perception data collected by the camera needs to be fused.

[0183] (5) Perception service information, or called perception service information of demand, the perception service information is used to indicate or determine the perception service requested by the requesting device, and the perception service may correspond to, be used to indicate or determine one or more of the perception area of ​​demand, the perception type of demand, the perception capability index of demand, the fusion demand and the perception type of demand. For example, the perception service is associated with one or more of the perception area of ​​demand, the perception type of demand, the perception capability index of demand, the fusion demand and the perception type of demand, so the perception service information may represent one or more of the perception area of ​​demand, the perception type of demand, the perception capability index of demand, the fusion demand and the perception type of demand. The association may be predefined, or may be indicated by a network element such as a SF or a server, or may be indicated by a perception requesting device such as a terminal device, an access network device or a server, and this application does not make specific requirements. Optionally, the perception service information may include an identifier of the perception service, information of the requesting device, or information on the type of the perception service.

[0184] (6) Device identification, which can be used to indicate the device that needs to be perceived. Referring to the description of the device identification in the capability information, the device identification here can include the 3GPP device identification and / or the N3GPP device identification, which are used to indicate the 3GPP device and / or N3GPP device that needs to be perceived, respectively.

[0185] It can be understood that one or more of the above required device identification, selected perception area, fusion requirement information and required perception service information can also be independent of the perception requirement information, that is, as perception requirements parallel to the perception requirement information.

[0186] In addition, optionally, if the third perception requirement information is not carried in the perception device request message and / or the perception device subscription message, then in this application, it can be required by default that any device that supports N3GPP perception capabilities provide N3GPP perception. In addition, default perception requirement information can also be used. Among them, the default perception requirement information can be predefined, such as defined by a protocol or defined in the factory configuration of the device; the default perception requirement information can also be pre-configured, for example, the default perception requirement information can be obtained by the device based on the configuration information sent by network elements such as SF and server, or it can be obtained in the previous perception process or configuration process.

[0187] S102: The SF receives a perception request message from a requesting device, requesting to obtain perception data.

[0188] Alternatively, the perception request message may be used to request a perception result.

[0189] The requesting device may be a terminal device, access network device, AF, or AS, etc., requesting a perception service. In this case, the requesting device may send the perception request message based on the perception-related service. Furthermore, it is not excluded that perception is performed based on network optimization needs. In this case, the requesting device may be a core network element such as an SMF. It is understood that the SF may send perception data or perception results to the requesting device based on the perception request message.

[0190] Optionally, the perception request message may include perception requirement information (for the sake of convenience, the perception requirement information may be referred to as fourth perception requirement information). The fourth perception requirement information may include one or more of the required perception area, required perception capability indicators, fusion requirement information, required perception type, and perception service information.

[0191] S103: The SF determines the first device according to the capability information of the device supporting the N3GPP perception capability in response to the perception request message.

[0192] The first device may be a 3GPP device. For example, in S103, the SF may select a 3GPP device that meets the requirements as the first device based on the capability information of the 3GPP device. Alternatively, the SF may select an N3GPP device that meets the requirements based on the capability information of the N3GPP device and use the 3GPP device connected to the N3GPP device as the first device.

[0193] In one possible embodiment, the SF can determine the first device based on the first perception requirement information and capability information, thereby reasonably determining the first node to obtain perception data that meets the requirements. The first perception requirement information may include one or more of the required perception area, required perception capability indicator, fusion requirement information, required perception type, and perception service information. For a description of each of these information, refer to the description of the third perception requirement information.

[0194] Among them, the first perceived demand information may be the same as or different from the fourth perceived demand information. If the first perceived demand information is the same as the fourth perceived demand information, the SF may select the first device based on the perceived demand. If the first perceived demand information is different from the fourth perceived demand information, the SF may perform certain processing based on the fourth perceived demand information provided by the requesting device, and select the first device based on the first perceived demand information obtained from the processing. Optionally, the first perceived demand information may be the same as or different from the third perceived demand information, which is not specifically limited in this application.

[0195] As an example, the processing of the fourth perception requirement information by the SF may include: determining whether N3GPP perception is required based on the fourth perception requirement information, and determining whether to indicate the perception type and other requirement information of N3GPP perception in the first perception information based on the result, for example, determining whether it is necessary to improve the perception performance through N3GPP perception based on the required perception performance indicators. Optionally, if the SF decides that N3GPP perception is required, and the fourth perception requirement information does not explicitly indicate that N3GPP perception is required, the first perception requirement information can and indicates that N3GPP perception is required, that is, the first perception requirement information may carry perception type information for indicating the need for N3GPP perception. Similarly, the SF may also determine the required performance indicators of N3GPP perception when deciding to perform N3GPP perception based on the fourth perception information, and carry the performance indicators of N3GPP perception in the first perception requirement information.

[0196] Optionally, in S103, the manner in which the SF determines the first device according to the first sensing requirement information and the capability information of the device supporting the N3GPP sensing capability may include any one or more of the following:

[0197] A. The SF selects a first device based on the required perception area included in the first perception requirement information and the supported perception area indicated by the capability information of the device supporting the N3GPP perception capability. For example, the SF may select a device supporting the N3GPP perception capability whose supported perception area falls within the required perception area as the first device.

[0198] B. The SF selects the first device according to the required N3GPP perception data type contained in the first perception requirement information and the supported N3GPP perception type indicated by the capability information of the device supporting the N3GPP perception capability, so that the first device supports the requested type of N3GPP perception.

[0199] C. The SF selects a first device based on the fusion requirement information indicating whether data fusion is required, included in the first perception requirement information, and the capability information of the device supporting the N3GPP perception capability indicating whether data fusion is supported. If the first perception requirement information indicates that data fusion is required, and the device supporting the N3GPP perception capability supports data fusion, the device may be selected as the first device.

[0200] D. The SF selects a first device based on the required data fusion indicator included in the first sensing requirement information and the supported data fusion indicator indicated by the capability information of the device supporting N3GPP sensing capabilities. For example, if the required fusion indicator requires data fusion at the point cloud data level, the selected first device at least supports data fusion at the point cloud data level.

[0201] E. SF selects the first device based on the perception service information contained in the first perception requirement information and the capability information of the device supporting the N3GPP perception capability. For example, the device whose supported perception service information includes the perception service information contained in the first perception requirement information is selected as the first device. For another example, SF can determine the area to be perceived, the required perception type, the required perception capability indicators and the required data fusion indicators based on the perception service information, and then match them with the capability information of the device supporting the N3GPP perception capability, and select the device that matches the above parameters as the first device. Among them, when there are multiple parameters that need to be matched, a device that matches all multiple parameters, at least one parameter, or at least a specific parameter (such as perception area information) can be selected as the first device.

[0202] It can be understood that the perception area of ​​the demand, the N3GPP perception data type of the demand, the fusion requirement information for indicating whether data fusion is required, and the fusion index of the data of the demand contained in the above-mentioned first perception requirement information can also be replaced by the perception area of ​​the demand, the N3GPP perception data type of the demand, the fusion requirement information for indicating whether data fusion is required, and the fusion index of the data of the demand indicated by the perception service information in the first perception requirement information. Alternatively, the SF can determine one or more of the perception area of ​​the cell, the perception type of the demand, the perception capability index of the demand, the fusion requirement and the perception type of the demand based on the perception service information contained in the first perception requirement information, and select a device that supports the one or more perception requirement information as the first device based on the perception requirement information and the capability information of the device that supports the N3GPP perception capability. Among them, when there are multiple parameters that need to be matched, a device that matches all multiple parameters, at least one parameter, or at least a specific parameter (such as perception area information) can be selected as the first device.

[0203] S104: The SF sends a first message to the first device, where the first message may be used to request perception data perceived by N3GPP.

[0204] Optionally, the first message may include second perception requirement information.

[0205] The second perception demand information may include one or more of the perception area of ​​the demand, the perception capability index of the demand, the fusion demand information, the perception type of the demand, and the perception business information. The description of each information can be found in the description of the third perception demand information.

[0206] It can be understood that the second perceived demand information may be the same as any one or more of the first perceived demand information, the third perceived demand information and the fourth perceived demand information, or may be different from the first perceived demand information, the third perceived demand information and the fourth perceived demand information.

[0207] For example, the perception area of ​​the requirement contained in the second perception requirement information may be a perception area associated with the first device (generally equal to or slightly larger than the perception area supported by the first device), which is used to request the first device to perceive the area, while the perception area contained in the first perception requirement information may not be associated with a specific device that supports N3GPP perception capabilities, for example, it may be an area corresponding to the perception range representing the requirement; in addition, the perception area contained in the second perception requirement information may be determined based on the perception area contained in the first perception requirement information, for example, the perception area contained in the second perception requirement information may be a smaller range of perception area determined from the perception area contained in the first perception requirement information based on the perception area supported by the first device.

[0208] For another example, the second perception requirement information may also include information about the selected N3GPP device, such as an identifier of the N3GPP device, indicating that N3GPP perception is to be performed by the corresponding N3GPP device, or identifying that perception data of the corresponding N3GPP device is required. The identifier of the N3GPP device may not be included in the first perception requirement information and / or the fourth perception requirement information, but is determined by the SF after selecting the first device based on the N3GPP device connected to the first device and the perception requirement for N3GPP perception. Therefore, if the SF explicitly requests the N3GPP device to perform N3GPP perception through the second perception requirement information, the first device may request, instruct, or control the N3GPP device to perform N3GPP perception.

[0209] In addition, when the SF does not explicitly request the N3GPP device to perform N3GPP perception through the second perception requirement information, the first device may also determine whether the N3GPP device needs to perform N3GPP perception based on the second perception requirement information. For example, when the perception area of ​​the requirement indicated by the second perception requirement information is the perception range of the N3GPP device, and / or the perception capability indicator of the requirement indicated by the second perception requirement information requires the N3GPP device to provide N3GPP perception to be realized, the first device may decide to have the N3GPP device perform N3GPP perception. For another example, when the first device does not support N3GPP perception and the second perception requirement information indicates that N3GPP perception is required, the first device may decide to have the N3GPP device perform N3GPP perception. In the case where the N3GPP device performs N3GPP perception, the first device may perform 3GPP perception and / or N3GPP perception, or may not perform perception.

[0210] In some cases, the first device may also decide to perform 3GPP sensing and / or N3GPP sensing by itself without requiring the N3GPP device to provide sensing data for N3GPP sensing. For example, when the sensing capability of the first device itself can meet the sensing capability required by the second sensing requirement information, the first device may perform 3GPP sensing and / or N3GPP sensing.

[0211] It can be understood that if the first message contains information of the selected N3GPP device, or the first device determines that N3GPP perception needs to be performed by the N3GPP device based on the second perception requirement information, the first device can request, instruct or control the N3GPP device to perform N3GPP perception based on the first message, and obtain the perception data of N3GPP perception from the N3GPP device through the connection between the first device and the N3GPP device.

[0212] Optionally, the first message may also carry an address and / or label for the SF to receive N3GPP-perceived perception data. Further optionally, the address and / or label may be carried in the first message, i.e., the SF carries the address and / or label for receiving N3GPP-perceived perception data when requesting N3GPP-perceived perception data from the first device. Furthermore, the SF may also carry the address and / or label for receiving N3GPP-perceived perception data when sending a device request message and / or a device subscription message to the first device.

[0213] The address may include the SF's device address and port. Specifically, the device address may be a User Plane Tunneling Protocol IP address. The tag may be an SF-assigned or default identifier representing N3GPP-perceived perception data. Accordingly, when the SF receives perception data with the destination address being the tag, it may identify the perception data as N3GPP-perceived perception data. Alternatively, when the SF receives perception data carrying the tag or sent along with the tag, it may identify the perception data as N3GPP-perceived perception data.

[0214] S105: The SF receives first perception data from the first device, where the first perception data includes N3GPP-perceived perception data.

[0215] Based on S105, SF can obtain the first perception data.

[0216] The N3GPP-perceived perception data may be obtained by the first device or an N3GPP device connected to the first device through N3GPP perception measurement. If the N3GPP-perceived perception data is obtained by the N3GPP device, the first device may obtain the N3GPP-perceived perception data from the N3GPP device and then send the first perception data to the SF, thereby reporting the N3GPP-perceived perception data to the SF.

[0217] Optionally, the SF may further process the first perception data to obtain second perception data. The second perception data may be perception data obtained based on cluster analysis or other processing of the first perception data, and the perception data may be used to further determine the perception result; in addition, the second perception data may also include the perception result.

[0218] As an example, the first device may include multiple 3GPP devices, and the SF processing may include fusing the perception data from the multiple 3GPP devices, and the fused second perception data may include N3GPP perception data of the multiple 3GPP devices.

[0219] As another example, the SF may also receive 3GPP-aware perception data from a second device, where the second device may include one or more first devices supporting 3GPP perception; or the second device may be a device other than the first device supporting 3GPP perception, such as a terminal device and / or an access network device. In this case, the SF's processing of the first perception data may include fusing the N3GPP-aware perception data with the 3GPP-aware perception data to obtain the second perception data. This combination of 3GPP and N3GPP perception can improve performance such as perception accuracy.

[0220] Among them, if the second device includes one or more first devices, that is, the second device includes one or more 3GPP devices for providing N3GPP-perceived perception data to the SF, then the first message sent by the SF to these first devices can also be used by the first device to obtain 3GPP-perceived perception data. For example, the first message can carry 3GPP-perceived perception type indication information to instruct the first device to perform 3GPP perception, or the first device can decide whether to perform 3GPP perception based on the perception requirement information in the first message; for example, when the first device only performs N3GPP perception and cannot meet the perception area, perception capability indicator or fusion requirement information required by the perception requirement information, the first device can decide to perform 3GPP perception.

[0221] In addition, in the combination of the above two examples, SF can also fuse the perception data from multiple 3GPP devices, wherein at least one 3GPP device or the corresponding N3GPP device among the multiple 3GPP devices supports N3GPP perception, and at least one 3GPP device supports 3GPP perception. Therefore, the fusion of perception data includes the fusion of perception data from multiple 3GPP devices, and the fusion of perception data of N3GPP perception and perception data of 3GPP perception.

[0222] Optionally, the SF may send the second perception data to the requesting device, so that the requesting device analyzes and / or processes the second perception data to obtain a final perception result. Furthermore, the second perception data may also be understood as the final perception result, or as perception data used to determine the perception result. Accordingly, the SF may send the perception result to the requesting device.

[0223] It can be understood that SF can fuse perception data according to perception requirement information (such as the fourth perception requirement information or the first perception requirement information), for example, process the first perception data and 3GPP perception data according to the fourth perception requirement information to obtain the second perception data. The fusion here can be the fusion of perception data from multiple 3GPP devices, or the fusion of 3GPP-perceived perception data and N3GPP-perceived perception data, for example, so that the fused perception data or perception results meet one or more of the perception area, required perception capability indicators, fusion requirement information and perception type required by the perception requirement information. Therefore, SF can obtain perception data or perception results that meet the requirements of the requesting device by fusing the perception data, and can improve the perception accuracy.

[0224] Optionally, the first perception data in S105 may be perception data generated based on N3GPP-perceived perception data and 3GPP-perceived data. For example, the first perception data is perception data fused by N3GPP perception and 3GPP perception. The first device supporting data fusion may fuse N3GPP-perceived perception data and 3GPP-perceived data to generate perception data. Therefore, in the present application, the first device may fuse N3GPP-perceived perception data and 3GPP-perceived data, the SF may fuse N3GPP-perceived perception data and 3GPP-perceived data, the first device may align the obtainable N3GPP-perceived perception data and 3GPP-perceived data to fuse them, and the SF may fuse the fused data, N3GPP-perceived perception data and 3GPP-perceived data provided by one or more first devices.

[0225] For example, when the first message carries perception requirement information, the first device may fuse the perception data according to the perception requirement information. Specifically, when the perception requirement information contains fusion requirement information indicating that data fusion is required, and / or when the perception requirement information contains fusion indicators, the first device may fuse the perception data perceived by N3GPP and the data perceived by 3GPP to obtain the first perception data. The first device may fuse the data according to the fusion indicator carried in the perception requirement information or the default fusion indicator. The default fusion indicator may be predefined or preconfigured. In addition, the first device may also perform data fusion and provide the fused first perception data to the SF by default when obtaining the N3GPP perception data and the 3GPP perception data. At this time, the data fusion may be performed according to the default fusion indicator.

[0226] In addition, if the perception requirement information carried in the first message does not include fusion requirement information, that is, if the first device is not explicitly instructed, requested, or required to perform fusion of N3GPP-perceived perception data and 3GPP-perceived data, the first device may default to not performing fusion of N3GPP-perceived perception data and 3GPP-perceived data. In this case, the SF may perform fusion of N3GPP-perceived perception data and 3GPP-perceived data.

[0227] When SF adopts a control plane-user plane separation architecture, S101-104 can be understood as being executed by SF-C, and S105 and the action of sending the second perception data can be understood as being executed by SF-U.

[0228] It can be understood that in the present application, the first device itself can support both N3GPP perception capabilities and support the fusion of 3GPP-perceived perception data and N3GPP-perceived perception data; or, the first device itself can also support N3GPP perception capabilities but does not support the fusion of 3GPP-perceived perception data and N3GPP-perceived perception data; or, the first device itself may not support N3GPP perception capabilities, but is connected to one or more N3GPP devices. At this time, the first device can optionally support the fusion of 3GPP-perceived perception data and N3GPP-perceived perception data, or it can only support reporting of N3GPP-perceived perception data provided by the N3GPP device to the SF.

[0229] Based on the process shown in Figure 5, the SF can obtain capability information of devices supporting N3GPP awareness capabilities and select one or more first devices supporting N3GPP awareness capabilities based on the capability information. The SF can also send a first message to the first device to request, control, or instruct the first device to provide N3GPP-aware awareness data.

[0230] For example, the process shown in Figure 5 can be applied to the various embodiments shown in Figures 6 to 9 below. The various embodiments shown in Figures 6 to 9 are introduced below.

[0231] As shown in Figure 6, in Example 1, the perception network element is SF, and the capability information of devices supporting N3GPP perception is collected and / or stored by SF. SF can collect capability information by receiving capability information reported by 3GPP devices through network elements such as AMF or AF, or by receiving capability information from access network devices through an interface between SF and access network devices (NS1 interface as shown in Figure 4).

[0232] As shown in FIG6 , the embodiment 1 may include the following steps:

[0233] S201: The 3GPP device reports capability information to the SF.

[0234] Accordingly, SF stores capability information.

[0235] For example, the 3GPP device is a terminal device or an access network device.

[0236] As described in this application, when a 3GPP device supports N3GPP perception, the 3GPP device itself may be a device supporting N3GPP perception, in which case the capability information includes the N3GPP perception capability information of the 3GPP device; and / or, the N3GPP device to which the 3GPP device is connected may support N3GPP perception, in which case the capability information includes the N3GPP perception capability information of the N3GPP device.

[0237] In addition, the capability information may include one or more of the following: supported perception areas, locations, indications of supported N3GPP perception capabilities, device identifiers, supported perception types, supported perception capability indicators, and supported perception data fusion capability information for the 3GPP device and / or N3GPP device. For an explanation of the capability information, please refer to the introduction to the process in FIG. 5 of this application, and any repetitions will not be repeated.

[0238] Optionally, in S201, the 3GPP device may report the capability information to the SF through the AMF, AF, or through the interface between the access network device and the SF.

[0239] For example, 3GPP devices can report N3GPP device information to SF via AMF via non-access-stratum (NAS) protocols. In addition, 3GPP devices can also report capability information to SF via user plane paths, such as using application layer protocols such as Hypertext Transfer Protocol (HTTP) or Session Initiation Protocol (SIP).

[0240] In addition, in S201, the AF may also report capability information to the SF. For example, the AF may be installed in the terminal device, so the AF may obtain the capability information of the terminal device and / or the capability information of the N3GPP device connected to the terminal device, and provide the capability information to the SF.

[0241] It can be understood that S201 can be used as an exemplary implementation of S101 in the process shown in FIG5 .

[0242] S202: The device requesting the perception service sends a perception request message.

[0243] Correspondingly, the SF receives the perception request message.

[0244] The requesting device may be a terminal device, access network device, AF or AS, etc., which is used to request the sensing service. In FIG6 , a terminal device is used as an example of the requesting device.

[0245] If the AS or terminal device acts as the requesting device, the NEF and / or AF can receive the perception request message from the requesting device and forward the perception request message to the SF accordingly. In one example, the NEF and / or AF acts as a forwarding node to forward (e.g., transparently transmit) the perception request message sent by the AS. In another example, the AF can be installed in the terminal device, and the AF can receive the perception request message from the terminal device and then send the perception request message to the SF, or the AF can send the perception request message to the SF through the NEF.

[0246] In addition, if the terminal device or access network device acts as the requesting device, the requesting device can also send a perception request message to the SF through the AMF, or the perception request message can be sent through the interface between the access network device and the SF.

[0247] In S202, the perception request message may include fourth perception requirement information, such as one or more of the perception area of ​​the requirement, the perception capability index of the requirement, the fusion requirement information, the perception type of the requirement, and the perception service information. For the above-mentioned various perception requirement information, please refer to the introduction of the perception requirement information in S101. Among them, the perception requirement information can be indicated by the perception service information. For example, the perception service information can also be independent of the perception requirement information, and there can be a corresponding relationship or an association relationship between the perception service information and the perception requirement information. Therefore, the perception requirement information can also be implicitly indicated by indicating the perception service information.

[0248] S203: Optionally, the SF obtains the security-aware privacy requirements from the UDM / UDR.

[0249] For example, privacy requirements are used to indicate or express that devices and perceived objects that support N3GPP perception are based on privacy security regulations, that is, SF ensures through S203 that perception cannot be performed privately to avoid leakage of sensitive information.

[0250] S204: The SF selects one or more first devices for N3GPP sensing based on the capability information and sensing requirement information of the devices supporting N3GPP sensing, wherein the sensing requirement information is, for example, the first sensing requirement information mentioned above.

[0251] Referring to the description of S103, the SF may select one or more first devices from at least one device according to the first perception requirement information and capability information of at least one device, and the first device or an N3GPP device connected to the first device may perform N3GPP perception.

[0252] In addition, optionally, the SF may select one or more N3GPP devices connected to the first device, and indicate information of the N3GPP devices, so that the first device requests, instructs or controls the N3GPP devices to perform N3GPP perception.

[0253] It can be understood that S204 can be used as an exemplary implementation of S103 in the process shown in FIG. 5 .

[0254] S205: The SF sends a first message to the first device.

[0255] The first message may be a perception control message, used to trigger the first device to provide first perception data to the SF, that is, to provide N3GPP-perceived perception data.

[0256] The first message may include second perception requirement information, which may at least be used to indicate N3GPP perception requirements.

[0257] In addition, the SF may also determine whether the first device is required to fuse the 3GPP perception data and the N3GPP perception data. If the first device is required to perform data fusion, the SF may also determine fusion requirement information, which may be understood as fusion requirement information contained in the second requirement information. As described in this application, the second perception requirement information may be perception requirement information sent by the SF to the first device. The second perception requirement information may be different from the first perception requirement information. For example, the second perception requirement information may be obtained based on the first perception requirement information, and the first perception requirement information and / or the second perception requirement information may be obtained based on the fourth perception requirement information.

[0258] The first message or the second perception requirement information may also include an identifier of the N3GPP device, which is used to indicate that the N3GPP perception is performed by the N3GPP device.

[0259] Optionally, the first message may also include an address and / or identifier of the SF for receiving the first perception data. Accordingly, when sending the first perception data to the SF, the first device may send the data through the address, or send the identifier together with the data, so that the SF can identify the first perception data based on the address and / or identifier.

[0260] S206: The first device performs perception measurement according to the first message to obtain first perception data, which includes N3GPP perception data.

[0261] Among them, when the first device itself supports N3GPP perception, the perception device can perform N3GPP perception and obtain perception data of N3GPP perception.

[0262] In addition, when the first device itself does not support N3GPP perception but is connected to an N3GPP device, the perception device may obtain perception data of N3GPP perception from the N3GPP device.

[0263] If the first device supports N3GPP perception and is connected to one or more N3GPP devices, the N3GPP perception data may include N3GPP perception data obtained by the first device performing N3GPP perception, and may also include N3GPP perception data obtained by the N3GPP devices performing N3GPP perception. Optionally, the first device may fuse the N3GPP perception data obtained by performing N3GPP perception with the N3GPP perception data obtained by performing N3GPP perception on the N3GPP devices to obtain the first perception data.

[0264] Optionally, the first perception data may be data obtained by the first device by fusing the 3GPP-perceived perception data and the N3GPP-perceived perception data. The 3GPP-perceived perception data may be obtained by the first device through 3GPP perception. The N3GPP-perceived perception data may be obtained by the first device through N3GPP perception, and / or may be obtained by the N3GPP device through N3GPP perception.

[0265] As a possible implementation, if the perception requirement information in the first message includes data fusion requirement information, the first device may default to requiring fusion of 3GPP-perceived perception data and N3GPP-perceived perception data. Therefore, if the first device obtains both 3GPP perception data and N3GPP perception data, data fusion is required. In addition, if the perception requirement information in the first message does not include data fusion requirement information, the first device may default to not requiring data fusion. Therefore, if the first device obtains both 3GPP perception data and N3GPP perception data, the first device may send the 3GPP perception data and the N3GPP perception data to the SF without performing data fusion.

[0266] S207: The first device sends first perception data to the SF.

[0267] Optionally, if in S205, the first message includes an address for receiving the first perception data, then in S207, the first device may use the address as the destination address of the first perception data. Accordingly, the SF may recognize that the perception data received through the address includes N3GPP perception data, i.e., the first perception data.

[0268] For example, the SF may send a channel establishment request to the first device through the AMF to request establishment of a channel, where the channel can be used to transmit the first perception data. The channel establishment request may include an address for receiving the first perception data. Accordingly, the first perception data can be transmitted through the established channel, and the SF can be informed that the data transmitted through the channel is the first perception data.

[0269] In addition, if in S205, the first message includes an identifier for receiving the first perception data, then in S207, the first device may send the first perception data and the identifier. Accordingly, the SF may recognize that the perception data sent together with the identifier includes N3GPP perception data, i.e., the first perception data.

[0270] Optionally, the first perception data may also include 3GPP-perceived perception data.

[0271] S208: Optionally, SF performs data fusion.

[0272] Among them, the data fusion in S208 includes the fusion of perception data provided by SF to multiple devices (such as the first device and other devices), and / or, includes the fusion of SF to 3GPP perception data and N3GPP perception data (such as the first perception data).

[0273] It can be understood that in S208, data fusion can be performed based on the fusion requirement information required by the fourth perception requirement information, so that the fusion result meets the requirements of the requesting device.

[0274] S209: SF sends the sensing result to the requesting device.

[0275] The perception result may be obtained by the SF processing the perception data including the first perception data according to the fourth perception requirement information. For example, in addition to obtaining the first perception data from the first device, the SF may also obtain 3GPP-perceived perception data and / or N3GPP-perceived perception data from other perception devices, and obtain the perception result by performing cluster analysis or other processing on all the perception data.

[0276] Based on the process shown in Figure 6, the SF can collect and / or store capability information of devices that support N3GPP awareness, select a first device, and obtain first awareness data including N3GPP-aware awareness data from the first device, thereby obtaining a awareness result based on the first awareness data. Because the SF can collect capability information, it does not need to request capability information from other devices when selecting the first device, thereby improving the efficiency of selecting N3GPP-aware devices.

[0277] In embodiment 2, the perception network element is SF, and the capability information is collected and / or stored by the N3GPP perception capability storage functional network element.

[0278] As shown in FIG7 , the process of Example 2 is similar to that of FIG6 , so step S30x in FIG7 can be implemented with reference to step S20x in FIG6 .

[0279] The difference between Figure 7 and Figure 6 is that the 3GPP device in S301 reports the capability information to the N3GPP perception capability storage function network element instead of reporting the capability information to the SF. In Figure 7, N3GPP-NRF is taken as an example to represent the N3GPP perception capability storage function network element. Among them, when the 3GPP device reports the perception capability to the N3GPP perception capability storage function network element, the 3GPP device can use application layer protocols such as HTTP or SIP through the user plane path to report the capability information to the N3GPP perception capability storage function network element. Alternatively, the 3GPP device can send the capability information to the SF, and then the SF sends the capability information to the N3GPP perception capability storage function network element. Alternatively, the 3GPP device can send the capability information to the AMF, and then the AMF sends the capability information to the N3GPP perception capability storage function network element.

[0280] In addition, in the process of FIG. 7 , S304 - a and S304 - b may be executed before S304 .

[0281] In S304-a, the SF sends a device awareness request message to the N3GPP awareness capability storage functional network element. Optionally, the device awareness request message may include third awareness requirement information for discovering devices that support N3GPP awareness capabilities. The N3GPP awareness capability storage functional network element can filter the capability information of eligible devices based on the third awareness requirement information and provide feedback to the SF on the capability information of eligible devices. The N3GPP awareness capability storage functional network element can also provide capability information for all devices upon receiving the device awareness request message.

[0282] In S304-b, SF may receive capability information of devices supporting N3GPP perception from the N3GPP perception capability storage functional network element. Optionally, the N3GPP perception capability storage functional network element may determine capability information that meets the perception requirements based on the third perception requirement information, and provide the capability information that meets the perception requirements to SF. For example, the N3GPP perception capability storage functional network element may select capability information of a device whose location matches the perception area required in the third perception request information, whose supported N3GPP perception type matches the required N3GPP perception type in the third perception request information in the request, and / or whose supported perception data fusion capability matches the required data fusion capability in the third perception request information.

[0283] In one possible example, the N3GPP awareness capability storage function network element only includes capability information of the N3GPP device. In another possible example, the N3GPP awareness capability storage function network element only includes capability information of the 3GPP device and capability information of the N3GPP device.

[0284] Based on the process shown in Figure 7, the N3GPP perception capability storage functional network element can collect and / or store capability information of devices that support N3GPP perception, and the N3GPP perception capability storage functional network element can provide capability information to the SF based on the perception device request message. In addition, in S304, the SF can also make a secondary selection based on the capability information and perception requirement information to more reasonably determine the first device, and obtain first perception data containing N3GPP perception perception data from the first device, thereby obtaining a perception result based on the first perception data. In this embodiment, the N3GPP perception capability storage functional network element can be an independent functional network element, which can avoid occupying the processing overhead and communication overhead of the SF or other network elements.

[0285] In embodiment 3, the sensing network element is SF, and the UDR / UDM collects and / or stores the capability information.

[0286] As shown in Figure 8, the process of Example 3 is similar to that of Figure 7, so step S40x in Figure 8 can be implemented by referring to step S30x in Figure 7. The difference is that in the process of Figure 8, the UDR / UDM executes the actions of the N3GPP perception capability storage functional network element in the process shown in Figure 7.

[0287] Based on the process shown in Figure 8, the UDR / UDM can collect and / or store the capability information of devices that support N3GPP perception, and the UDR / UDM can provide the capability information to the SF based on the perception device request message. In addition, in S404, the SF can also make a secondary selection based on the capability information and the perception requirement information to more reasonably determine the first device, and obtain the first perception data containing the perception data of N3GPP perception from the first device, so as to obtain the perception result based on the first perception data. In this embodiment, the UDR / UDM collects and / or stores the capability information of devices that support N3GPP perception, which can avoid occupying the processing overhead and communication overhead of network elements such as SF or AMF.

[0288] In embodiment 4, the perception network element is SF, and the AMF collects and / or stores the capability information reported by the 3GPP device.

[0289] As shown in Figure 9, the process of Example 4 is similar to that of Figure 6. Therefore, step S50x in Figure 9 can be implemented with reference to step S20x in Figure 6. The difference is that in S501, the 3GPP device reports capability information to the AMF. Therefore, the capability information stored by the AMF is the capability information of the 3GPP devices within the area it manages.

[0290] In addition, in the process shown in Figure 9, before S504, S504-a to S504-c may be performed: the SF determines the AMF based on the required perception area. Therefore, the SF can request the capability information of the 3GPP device from the AMF only based on the required perception area, avoiding requesting capability information from the AMF corresponding to the area where perception is not required, thereby reducing the processing and communication overhead of the AMF in the non-required area.

[0291] In addition, S504-b and S504-c can refer to the description of S304-a and S304-b in Figure 7 respectively. The difference is that the N3GPP perception capability storage function network element in S304-a and S304-b is replaced by AMF.

[0292] Based on the process shown in Figure 9, the AMF can collect and / or store the capability information of the devices supporting N3GPP perception within the area it manages, and the AMF can provide the capability information of the devices within the area it manages to the SF based on the perception device request message. In addition, in S504, the SF can also make a secondary selection based on the capability information and the perception requirement information to more reasonably determine the first device, and obtain the first perception data containing the perception data of N3GPP perception from the first device, so as to obtain the perception result based on the first perception data. In this embodiment, 3GPP devices such as terminal devices or access network devices can register the capability information with the AMF corresponding to the area where they are located, and the AMF can use the capability information as the registration information of the 3GPP devices in the unmanaged area for unified management, thereby improving the storage and management efficiency of the capability information.

[0293] In embodiment 5, the perception network element subscribes to capability information from the AMF, for example, it can provide perception requirement information. If a 3GPP device that meets the N3GPP perception requirement information is accessed, the AMF can provide capability information to the perception network element.

[0294] As shown in FIG10 , the process of Example 5 is similar to that of FIG9 , so the step S50x in FIG10 can be implemented by referring to the step S50x in FIG9 . The difference is:

[0295] (1) Delete or cancel S504-a in FIG9.

[0296] (2) Replace S504-b in Figure 9 with S501-a: The SF sends a device subscription message to the AMF. The device subscription message can be used to subscribe to the capability information of devices that support N3GPP awareness capabilities. The AMF may send a response message to the SF to indicate receipt of the subscription.

[0297] Optionally, the device subscription message may include third-party perception requirement information.

[0298] (3) Optionally, in the specific implementation of S501 in FIG10 , the N3GPP-aware device, including the first device, may send a setup request via the NG interface between the base station and the AMF, and report the capability information of the N3GPP-aware device to the AMF in the setup request message. Optionally, the message may be repeatedly sent when the capability information of the N3GPP-aware device changes.

[0299] (4) S504-c in FIG9 can be replaced by S501-b: AMF can send the capability information to SF after receiving it.

[0300] In addition, optionally, if the device subscription message contains third perception requirement information, then in S501-b, the AMF can provide the SF with capability information of devices supporting N3GPP perception that meet the perception requirements based on the third perception requirement information.

[0301] In embodiment 6, the access network device provides capability information to the SF via the interface between the access network device and the SF. The 3GPP device may be an access network device, a terminal device connected to the access network device, or other device.

[0302] The process of Example 6 is similar to that of Figure 6, and therefore may be implemented with reference to the steps in Figure 8. The difference is that when executing step S201, in Example 6, the first device (or other device supporting N3GPP awareness capabilities) may send capability information to the SF via the interface between the base station and the SF. The first device may be the base station or a device such as a UE connected to the base station. Taking the scenario shown in Figure 4 as an example, the interface between the base station and the SF may be the NS1 interface.

[0303] In another embodiment of the present application, in the process shown in Figure 5, S101 can be replaced by being executed by a network element such as AMF or NRF that stores capability information. After executing S102, SF can send a perception device request message to the network element that stores capability information (see S304-a, S404-a for details). The selection of the first device is performed by the network element that stores capability information, that is, S103 is replaced by being executed by the network element that stores capability information. The network element that stores capability information sends the information of the selected first device to SF, so that SF executes S104-105 and sends the second perception data.

[0304] In another embodiment of the present application, the actions performed by the SF in the process shown in Figure 5 can also be replaced by actions performed by the perception server. In other words, the perception server can be used to obtain capability information and select the first device according to the capability information.

[0305] The manner in which the perception server acquires capability information may refer to the manner in which the SF acquires capability information in S101, for example, the manner in which the SF acquires capability information in any of the possible manners shown in Figures 6 to 10. For example, in S201 shown in Figure 6, the 3GPP device may register capability information with the perception server. Alternatively, the SF may acquire capability information in the manner in which the SF acquires capability information in S101, and the perception server may obtain capability information from the SF.

[0306] In a possible embodiment, the action of the perception server selecting the first device may be performed in response to a perception request message from the requesting device, and the perception request message may be used to request perception data or perception results. That is, in this embodiment, the requesting device may send a perception request message to the perception server instead of sending a perception request message to the SF. In this embodiment, the perception server may feed back the second perception data or perception result to the requesting device. Optionally, in this embodiment, the perception server may also send a second message to the SF, and the second message may be used to request the SF to perform 3GPP perception, obtain 3GPP-perceived perception data from the SF, and obtain the second perception data or perception result by combining the 3GPP-perceived perception data and the N3GPP-perceived perception data (such as the first perception data).

[0307] In another possible embodiment, the perception server's action of selecting the first device may be performed in response to an N3GPP perception request from the SF. The SF may receive a perception request message from the requesting device and, if N3GPP perception is required, send a third message to the perception server requesting N3GPP perception and / or N3GPP-perceived perception data. The SF may also independently decide to instruct the perception server to perform N3GPP perception for other reasons, such as network optimization needs. In this case, the SF may optionally not perform N3GPP perception based on the perception request message (i.e., in this case, the SF does not need to receive the perception request message). The perception server may also, after obtaining N3GPP-perceived perception data (such as the first perception data), send the N3GPP-perceived perception data to the SF. Therefore, in this embodiment, the SF may provide feedback of second perception data or a perception result to the perception server. The second perception data may be obtained based on at least the N3GPP-perceived perception data, and the perception result may be obtained based on at least the N3GPP-perceived perception data. For example, the SF may request the 3GPP-perceived perception device to obtain 3GPP-perceived perception data, and the SF may combine the 3GPP-perceived perception data and the N3GPP-perceived perception data to obtain the second perception data or perception result.

[0308] The two possible embodiments are described below in conjunction with the embodiments shown in FIG. 11 and FIG. 12 .

[0309] As shown in Figure 11, in Example 7, the perception network element is a perception server, and the perception server collects and / or stores the capability information reported by the 3GPP device. In Example 7, the requesting device may send a perception request message to the perception server through S602, and the perception server may provide the perception data or perception results to the requesting device through S609. When 3GPP perception is required, the perception server may send a second message to the SF through S607-a, and the second message may be used to request the perception data of 3GPP perception. Correspondingly, in S607-b, the SF may send the perception data of 3GPP perception to the perception server, and the server may perform perception data fusion and obtain the perception data or perception results. In Example 7, the perception server may send the perception data or perception results to the requesting device through S609.

[0310] It is understood that in Figure 11, the way the perception server selects the first device through S604 can refer to the way the SF selects the first device in S204. S603 can be implemented with reference to S203, so the perception server can obtain the privacy requirements for perception security from the UFM / UDR. In addition, this application does not limit the execution sequence of S603 and S604. Furthermore, the way the perception server performs data fusion in S608 can refer to S708. The perception server can perform data fusion based on the fourth perception requirement information carried in the perception request message.

[0311] As shown in Figure 12, in Example 8, the perception network element is a perception server, and the perception server collects and / or stores capability information. After the SF receives the perception request message from the requesting device through S702, if the SF determines that N3GPP perception is required based on the perception request message, it sends a third message to the perception server through the step shown in S702-a, so that the perception network element selects the first device based on the capability information, and the first device performs N3GPP perception. After obtaining the N3GPP perception data, the perception server can provide the N3GPP perception data to the SF through the step shown in S707-a, and then the SF provides the perception result to the requesting device. Optionally, the SF can also obtain 3GPP perception data based on the perception requirement information, and obtain perception data or perception results after fusing the 3GPP perception data and the N3GPP perception data. The SF can also provide the perception data or perception results to the requesting device through S709.

[0312] It is understood that in Figure 12 , the way the perception server selects the first device in S704 can be similar to the way the SF selects the first device in S204. S703 can be implemented similarly to S203, and this application does not limit the execution sequence of S703 and S704. Alternatively, the perception server can obtain the privacy requirements for perception security from the UFM / UDR. The way the SF performs data fusion in S708 can be similar to S208.

[0313] It can also be understood that the implementation methods of the steps not specifically described in Figures 11 and 12 can be found in the introduction of the corresponding steps in other embodiments of the present application and will not be repeated here.

[0314] The actions of the 3GPP device shown in the various embodiments of the present application may be executed by a chip on the 3GPP device, a processing module of an operating system (OS), or a middleware client on the OS (for example, in the form of a software development kit (SDK)).

[0315] Based on the same concept, an embodiment of the present application also provides a communication device. The communication device may include hardware structures and / or software modules corresponding to the functions shown in the above method. Those skilled in the art should easily appreciate that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0316] Figures 13 to 15 are schematic diagrams of the structures of possible communication devices provided in embodiments of the present application. This communication device can be used to implement the functions of the SF, perception server, device supporting N3GPP perception, or first device in the above-mentioned method embodiments, thereby also achieving the beneficial effects of the above-mentioned method embodiments. In one possible implementation, the communication device can be a component in the SF, perception server, or first device involved in the above-mentioned method, or a component in a third network element. For relevant details and effects, please refer to the description of the above-mentioned embodiments.

[0317] As shown in Figure 13, the communication device 1300 includes a processing unit 1310 and a communication unit 1320. The communication unit 1320 can implement corresponding communication functions, and the processing unit 1310 is used to perform data processing, such as parsing / reading policy information and other data or information received by the communication unit 1320, or triggering the communication unit 1320 to send data or information, or generating data or information to be sent, etc. The communication unit 1320 can also be a transceiver unit or an input and output interface, etc., for the communication device 1300 to perform receiving and / or sending actions. The communication device 1300 can be used to implement the functions of the SF, the perception server, the device supporting N3GPP perception, or the first device in any of the method embodiments shown in Figures 5 to 12 above. The actions that the communication device can perform can be found in the description of the aforementioned method embodiments and will not be repeated here.

[0318] It is understood that the division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of the present application may be integrated into a single processor, or may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules.

[0319] As shown in Figure 14, a communication device 1400 provided in an embodiment of the present application is used to implement the communication method provided in this application. The communication device 1400 can be a communication device that applies the communication method, a component of a communication device, or a device that can be used in conjunction with the communication device. The communication device 1400 can be a first network element, a second network element, or a fourth network element. Specifically, the communication device 1400 can be a system-on-chip (SoC) or a chip. In the embodiment of the present application, the SoC can be composed of a chip or can include a chip and other discrete components. The communication device 1400 includes at least one processor 1420 for implementing the communication method provided in the embodiment of the present application. The communication device 1400 can also include an input / output interface 1410, which can include an input interface and / or an output interface. In the embodiment of the present application, the input / output interface 1410 can be used to communicate with other devices via a transmission medium, and its functions can include sending and / or receiving. For example, when the communication device 1400 is a chip, transmission is performed with other chips or devices via the input / output interface 1410. The processor 1420 can be used to implement the method described in the above method embodiment.

[0320] Exemplarily, the processor 1420 may be used to execute actions executed by the processing unit 1310 , and the input / output interface 1410 may be used to execute actions executed by the communication unit 1320 , which will not be described in detail.

[0321] Optionally, the communication device 1400 may further include at least one memory 1430 for storing program instructions and / or data. The memory 1430 is coupled to the processor 1420. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 1420 may operate in conjunction with the memory 1430. The processor 1420 may execute program instructions stored in the memory 1430. At least one of the at least one memory may be integrated with the processor.

[0322] In an embodiment of the present application, the memory 1430 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or may be a volatile memory (volatile memory), such as a random-access memory (RAM). A memory is 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, but is not limited thereto. The memory in the embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.

[0323] In the embodiments of the present application, the processor 1420 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0324] As shown in Figure 15, a communication device 1500 provided in an embodiment of the present application is used to implement the communication method provided in the present application. The communication device 1500 can be a communication device that applies the communication method shown in the embodiment of the present application, or it can be a component in a communication device, or it can be a device that can be used in combination with a communication device. The communication device 1500 can be a first network element or a third network element. Among them, the communication device 1500 can be a chip system or a chip. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. Part or all of the communication methods provided in the above embodiments can be implemented by hardware or by software. When implemented by hardware, the communication device 1500 may include: an input interface circuit 1501, a logic circuit 1502 and an output interface circuit 1503.

[0325] Optionally, taking the device being used to implement the function of the receiving end as an example, the input interface circuit 1501 can be used to execute the above-mentioned receiving action performed by the communication unit 1320, the output interface circuit 1503 can be used to execute the above-mentioned sending action performed by the communication unit 1320, and the logic circuit 1502 can be used to execute the above-mentioned action performed by the processing unit 1310, which will not be repeated.

[0326] Optionally, the communication device 1500 may be a chip or an integrated circuit in a specific implementation.

[0327] Part or all of the operations and functions performed by the communication device described in the above method embodiments of the present application can be completed using a chip or an integrated circuit.

[0328] An embodiment of the present application provides a computer-readable storage medium storing a computer program, wherein the computer program includes instructions for executing the above method embodiment.

[0329] An embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the above method embodiment.

[0330] An embodiment of the present application provides a communication system, which includes a first network element and a second network element. The communication system can be used to execute any one or more processes in Figures 5 to 12.

[0331] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0332] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, an SSD).

[0333] Note: A portion of this patent application contains material which is subject to copyright protection. The copyright owner reserves all rights reserved except for copies of the materials in the patent file or patent record in the Patent Office.

[0334] The SF, the perception server, the device supporting N3GPP perception, or the first device in each of the above-mentioned apparatus embodiments respectively correspond to the SF, the perception server, the device supporting N3GPP perception, or the first device in the method embodiments, and the corresponding steps are performed by the corresponding modules or units. For example, the communication unit (transceiver) performs the receiving or sending steps in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can refer to the corresponding method embodiments. Among them, there can be one or more processors.

[0335] As used in this specification, the terms "component," "module," "system," and the like are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and a computing device can be a component. One or more components can reside in a process and / or an execution thread, and a component can be located on one computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component across a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0336] Those skilled in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0337] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0338] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0340] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. If the functions are implemented in the form of software functional units and sold or used as independent products, they may be stored in a computer-readable storage medium.

[0341] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0342] In the description of this application, words such as "first" and "second" are used solely for descriptive purposes and should not be construed as indicating or implying relative importance or order. It should be noted that this application does not limit the order of appearance of "first," "second," etc. For example, "second" may appear before "first," and this is not a limitation in this application.

[0343] In the description of this application, "at least one (kind)" refers to one (kind) or more (kinds), and more (kinds) refers to two (kinds) or more than two (kinds). "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple. In the description of this application, " / " means "or", for example, a / b means a or b.

Claims

1. A communication method, characterized in that: include: The perception network element obtains capability information of devices supporting non-3rd Generation Partnership Project N3GPP perception capabilities; The perception network element receives a perception request message from a requesting device, where the perception request message is used to request perception data; The perception network element determines, in response to the perception request message, a first device according to the capability information, where the first device is one or more devices supporting N3GPP perception capability; The perception network element sends a first message to the first device, where the first message is used to request perception data perceived by N3GPP; The perception network element receives first perception data from the first device, where the first perception data includes perception data perceived by N3GPP.

2. The method according to claim 1, characterized in that The device supporting N3GPP perception capability includes: A device having N3GPP awareness capability, and / or a device connected to a device having N3GPP awareness capability.

3. The method according to claim 1 or 2, characterized in that The sensing network element determines the first device according to the capability information, including: The perception network element selects the first device according to the first perception requirement information and the capability information.

4. The method according to any one of claims 1 to 3, characterized in that: The first message includes second perception requirement information.

5. The method according to any one of claims 1 to 4, characterized in that: The perception network element obtains capability information of a device supporting N3GPP perception capability, including: The perception network element obtains the capability information from the device, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element that supports N3GPP perception capability.

6. The method according to claim 5, characterized in that The method further comprises: The perception network element sends a device request message and / or a device subscription message to the device, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element supporting the N3GPP perception capability; The device request message and / or the device subscription message includes third perception requirement information, and the third perception requirement information is used to discover devices that support N3GPP perception capabilities.

7. The method according to any one of claims 1 to 6, characterized in that: The capability information includes one or more of the following: Supported perception areas; Location; Indication of support for N3GPP awareness capabilities; The type of perception supported; Equipment identification; Supported perceived capability indicators; The supported perception data fusion capability information is used to indicate support for fusion of N3GPP-perceived perception data and 3GPP-perceived perception data, and / or to indicate supported fusion indicators of N3GPP-perceived perception data and 3GPP-perceived perception data.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: The perception network element sends second perception data to the requesting device.

9. The method according to claim 8, characterized in that The method further comprises: The perception network element receives 3GPP perception data from a second device, where the second device is a device supporting 3GPP perception capability; The perception network element generates the second perception data according to the first perception data and the perception data perceived by the 3GPP.

10. The method according to claim 9, characterized in that The first message is also used by the first device to obtain the 3GPP-perceived perception data, and the second device is the same device as the first device.

11. The method according to claim 8, characterized in that The method further comprises: The perception network element receives the perception data perceived by 3GPP from the perception function network element; The perception network element generates the second perception data according to the first perception data and the perception data perceived by the 3GPP.

12. The method according to claim 11, characterized in that The method further comprises: The perception network element sends a second message to the perception function network element, where the second message is used to request perception data perceived by 3GPP.

13. The method according to any one of claims 1 to 12, characterized in that: The first perception data is generated according to the perception data perceived by the N3GPP and the perception data perceived by the 3GPP.

14. The method according to any one of claims 1 to 13, characterized in that: The perception request message includes fourth perception requirement information.

15. The method according to any one of claims 1 to 14, characterized in that: One or more of the first perceived demand information, the second perceived demand information, the third perceived demand information, and the fourth perceived demand information include one or more of the following information: The perceived area of ​​demand; The perceived ability index of demand; Fusion requirement information, used to indicate the fusion of the perception data perceived by N3GPP and the perception data perceived by 3GPP, and / or used to indicate the fusion index of the required perception data perceived by N3GPP and the perception data perceived by 3GPP; the perceived type of need; Perception service information, where the perception service information is used to determine one or more of a perception area of ​​the demand, a perception capability index of the demand, the fusion demand, and a perception type of the demand.

16. The method according to any one of claims 1 to 15, characterized in that: The method further comprises: The perception network element sends, to the first device, address and / or data tag information for receiving the first perception data; The sensing network element receives first sensing data from the first device, including: The perception network element receives the first perception data with the destination address being the address from the first device; and / or, The perception network element receives the first perception data including the data tag information from the first device.

17. A method of communication, characterized in that: include: A first device receives a first message from a perception network element, where the first message is used to request perception data perceived by N3GPP, and the first device is a device supporting N3GPP perception; The first device obtains first perception data in response to the first message, where the first perception data includes perception data perceived by N3GPP; The first device sends the first perception data to the perception network element.

18. The method according to claim 17, characterized in that The first device comprises: A device having N3GPP awareness capability, and / or a device connected to a device having N3GPP awareness capability.

19. The method according to claim 17 or 18, characterized in that The method further comprises: The first device sends the capability information of the first device to the perception network element, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element, and the capability information is used to determine the first device.

20. The method of claim 19, wherein: The method further comprises: Receiving a device request message and / or a device subscription message from the perception network element; The device request message and / or the device subscription message includes third perception requirement information, and the third perception requirement information is used to discover devices that support N3GPP perception capabilities.

21. The method according to claim 19 or 20, characterized in that The capability information includes one or more of the following: Supported perception areas; Location; Indication of support for N3GPP awareness capabilities; The type of perception supported; Equipment identification; Supported perceived capability indicators; The supported perception data fusion capability information is used to indicate support for fusion of N3GPP-perceived perception data and 3GPP-perceived perception data, and / or to indicate supported fusion indicators of N3GPP-perceived perception data and 3GPP-perceived perception data.

22. The method according to any one of claims 17 to 21, characterized in that: The first message includes second perception requirement information.

23. The method according to any one of claims 17 to 22, characterized in that: The first message is also used to request 3GPP-perceived perception data, and the method further includes: The first device sends 3GPP-perceived perception data to the perception network element; or; The first device generates the first perception data according to the 3GPP-perceived perception data and the N3GPP-perceived perception data.

24. The method according to any one of claims 17 to 23, characterized in that: One or more of the second perceived demand information and the third perceived demand information include one or more of the following information: The perceived area of ​​demand; The perceived ability index of demand; Fusion requirement information, used to indicate the fusion of the perception data perceived by N3GPP and the perception data perceived by 3GPP, and / or used to indicate the fusion index of the required perception data perceived by N3GPP and the perception data perceived by 3GPP; the perceived type of need; Perception service information, where the perception service information is used to determine one or more of a perception area of ​​the demand, a perception capability index of the demand, the fusion demand, and a perception type of the demand.

25. The method according to any one of claims 17 to 24, characterized in that: The method further comprises: The first device receives, from the perception network element, address and / or data tag information for receiving the first perception data; The first device sending the first perception data to the perception network element includes: The first device sends the first perception data with the destination address being the address to the perception network element; and / or, The first device sends the first perception data including the data tag information to the perception network element.

26. A communication method, characterized in that: include: Get the capability information of devices that support N3GPP perception capabilities; receiving a sensing request message from a requesting device, wherein the sensing request message is used to request sensing data; In response to the perception request message, determining a first device according to the capability information, where the first device is one or more devices supporting N3GPP perception capability; Sending a first message to the first device, where the first message is used to request perception data perceived by N3GPP; Receive first perception data from the first device, where the first perception data includes perception data perceived by N3GPP.

27. The method of claim 26, wherein: The device supporting N3GPP perception capability includes: A device having N3GPP awareness capability, and / or a device connected to a device having N3GPP awareness capability.

28. The method according to claim 26 or 27, characterized in that The receiving first perception data from the first device includes: The perception server receives the first perception data from the first device; The perception server sends the first perception data to the perception network element.

29. The method according to any one of claims 26 to 28, characterized in that: The obtaining of capability information of a device supporting N3GPP perception capability includes: The perception server obtains capability information of devices supporting N3GPP perception capability; The receiving a sensing request message from a requesting device includes: The perception network element receives the perception request message; The step of determining, in response to the sensing request message, the first device according to the capability information comprises: The perception network element sends a third message to the perception server in response to the perception request message, where the third message is used to request perception data perceived by N3GPP; The perception server determines the first device according to the capability information in response to the third message.

30. The method according to any one of claims 26 to 29, characterized in that: The determining the first device according to the capability information includes: The first device is selected according to the first perceived demand information and the capability information.

31. The method of claim 29, wherein: The third message includes second perception requirement information.

32. The method according to any one of claims 26 to 31, characterized in that: The obtaining of capability information of a device supporting N3GPP perception capability includes: The perception server obtains the capability information from the device, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element that supports N3GPP perception capability.

33. The method of claim 32, wherein: The perception server sends a device request message and / or a device subscription message to the device, application function, normalized data warehouse network element, normalized data management network element, N3GPP perception capability storage function network element or access and mobility management network element that supports N3GPP perception capability; wherein the device request message and / or the device subscription message includes third perception requirement information, and the third perception requirement information is used to discover devices that support N3GPP perception capability.

34. The method according to any one of claims 26 to 33, characterized in that: The capability information includes one or more of the following: supported sensing areas; locations; indication of supported N3GPP sensing capabilities; device identification; supported sensing types; Supported perception capability indicators; supported perception data fusion capability information, used to indicate support for fusion of N3GPP-perceived perception data and 3GPP-perceived perception data, and / or, used to indicate supported fusion indicators of N3GPP-perceived perception data and 3GPP-perceived perception data.

35. The method according to any one of claims 26 to 34, characterized in that: The perception request message includes fourth perception requirement information; The method further comprises: The perception network element sends second perception data to the requesting device.

36. The method of claim 35, wherein: The method further comprises: The perception network element generates the second perception data according to the first perception data and the perception data perceived by 3GPP.

37. The method of claim 36, wherein: The sensing network element generates second sensing data according to the first sensing data and the sensing data sensed by 3GPP, including: The perception network element receives the 3GPP-perceived perception data from the second device, and receives the first perception data from the perception server; The perception network element generates the second perception data according to the first perception data and the perception data perceived by the 3GPP.

38. The method of claim 37, wherein: The first message is also used by the first device to obtain the 3GPP-perceived perception data, and the second device is the same device as the first device.

39. The method according to any one of claims 36 to 38, characterized in that: The sensing network element generates the second sensing data according to the first sensing data and the sensing data sensed by the 3GPP, including: The perception network element processes the first perception data and the perception data perceived by 3GPP according to the fourth perception requirement information to generate the second perception data.

40. The method according to any one of claims 26 to 39, characterized in that: The first perception data is generated according to the perception data perceived by the N3GPP and the perception data perceived by the 3GPP.

41. The method according to any one of claims 26 to 40, characterized in that: The perception request message includes fourth perception requirement information.

42. The method according to any one of claims 26 to 41, characterized in that: One or more of the first perception demand information, the second perception demand information, the third perception demand information and the fourth perception demand information include one or more of the following information: a perception area of ​​the demand; a perception capability indicator of the demand; fusion demand information, used to indicate the fusion of N3GPP-perceived perception data and 3GPP-perceived perception data, and / or, used to indicate a fusion indicator of the N3GPP-perceived perception data and the 3GPP-perceived perception data of the demand; the perception type of the demand; perception service information, the perception service information is used to determine one or more of the perception area of ​​the demand, the perception capability indicator of the demand, the fusion demand and the perception type of the demand.

43. The method according to any one of claims 26 to 42, characterized in that: The perception server may also send, to the first device, address and / or data tag information for receiving the first perception data; The receiving first perception data from the first device includes: The perception server receives the first perception data whose destination address is the address from the first device; Alternatively, the perception server receives the first perception data including the data tag information from the first device.

44. A communication device, characterized in that: The method comprises a processor configured to execute a computer program or instructions to implement the method according to any one of claims 1 to 43.

45. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instructions. When the computer program or instructions are executed by the communication device, the method according to any one of claims 1 to 43 is implemented.

46. ​​A computer program product, characterized in that When the computer program product is executed by a computer, the computer is caused to execute the method according to any one of claims 1 to 43.

47. A chip, characterized in that: comprising a processor configured to execute the method as claimed in any one of claims 1 to 43.

48. A communication system, characterized in that: The invention comprises a communication device for executing the method as claimed in any one of claims 1 to 16 and a communication device for executing the method as claimed in any one of claims 17 to 25.

49. A communication system, characterized in that: A communication device comprising the method according to any one of claims 17 to 25 and a communication device for executing the method according to any one of claims 26 to 43.

Images