Communication method and apparatus, and chip

Abstract

The present application is applied to the technical field of communications. Provided are a communication method and apparatus, and a chip. The communication method provided in the present application can identify and schedule a certain type of device in a communication network. The communication method comprises: a first network element acquiring first information and second information, wherein the first information comprises a sensing identifier of a first-type device in a first area and first location information corresponding to the sensing identifier, and the second information comprises a communication identifier of the first-type device in the first area and at least one of the following: second location information or third location information corresponding to the communication identifier; and the first network element associating the sensing identifier of the first-type device with the communication identifier of the first-type device on the basis of the first location information and at least one of the following: the second location information or the third location information.

Description

Communication methods, devices and chips

[0001] This application claims priority to Chinese Patent Application No. 202411220197.X, filed with the State Intellectual Property Office of China on August 30, 2024, entitled "Communication Method, Apparatus and Chip", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to communication methods, devices and chips. Background Technology

[0003] In communication networks, devices with communication needs different from typical human-computer interaction terminals may be introduced, such as drones and unmanned delivery vehicles. Therefore, how to identify and schedule these types of devices within the communication network and meet their communication requirements is an urgent problem to be solved. Summary of the Invention

[0004] This application provides a communication method, apparatus, and chip that can identify and schedule a certain type of device in a communication network.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a communication method is provided. This method can be executed by a first network element, or by a module (e.g., a processor, chip, or chip system) applied to the first network element. The following description uses the execution of this communication method by the first network element as an example. The method includes: the first network element acquiring (or alternatively, determining / obtaining, etc.) first information and second information; wherein the first information includes a sensing identifier of a first type of device within a first area (or alternatively, the first area) and first location information corresponding to the sensing identifier; the second information includes a communication identifier of the first type of device within the first area and at least one of the following: second location information or third location information corresponding to the communication identifier. The first network element associates the sensing identifier and the communication identifier of the first type of device based on the first location information and at least one of the following: second location information or third location information.

[0007] In this application embodiment, the first type of device can also be replaced by descriptions such as first device, first target, first object, first object, first type of target, first type of object, or first type of object.

[0008] In this embodiment of the application, "associating the perception identifier and communication identifier of the first type of device" can also be called determining the association relationship between the perception identifier and the communication identifier of the first type of device. It can be understood as determining that the object / device / target / object corresponding to a certain perception identifier and the object / device / target / object corresponding to a certain communication identifier are the same object / device / target / object.

[0009] In this embodiment of the application, one way to obtain the first information and the second information is that the first network element receives the first information and the second information.

[0010] Based on the communication method provided in the embodiments of this application, the first network element can associate the perception identifier and communication identifier of the first type of device in the first area with the location information corresponding to the two types of identification information obtained. In other words, the first type of device can be screened out from the perception targets in the first area and associated with its communication identity. Thus, the first type of device can be coordinated and scheduled from a global perspective through the communication network, such as global scheduling of drones.

[0011] In conjunction with the first aspect described above, in one possible design, the method further includes: a first network element sending a first message to a second network element, the first message requesting information about a first type of device within a first area, the information of the first type of device including the sensing identifier and location information of the first type of device. The first network element obtaining second information includes: the first network element receiving second information from the second network element.

[0012] Based on this scheme, the first network element can request information about the first type of device from another network element (i.e., the second network element). The second network element can sense the first type of device in the first area based on the request from the first network element, obtain the sensing identifier and location information of the first type of device, and feed it back to the first network element.

[0013] In conjunction with the first aspect described above, in one possible design, the method further includes: the first network element receiving information from the second network element regarding the number of first-type devices within the first area, and / or the type of the first-type devices.

[0014] Based on this scheme, the second network element can also report the number of first-class devices and / or the type of first-class devices to the first network element.

[0015] In conjunction with the first aspect above, in one possible design, the method further includes: a first network element sending a second message to a third network element, the second message being used to request a communication identifier of a first type of device in a first area; the first network element receiving at least one communication identifier from the third network element, the at least one communication identifier being used by the first network element to obtain second information.

[0016] Based on this scheme, the first network element can request the communication identifier of the first type of device in the first area from the third network element, and obtain the second location information based on the communication identifier fed back by the third network element.

[0017] In conjunction with the first aspect above, in one possible design, the second message is used to request the context of a first type of device within a first area; the first network element receives at least one communication identifier from a third network element, including: the first network element receives the context of at least one first type of device from the third network element, the context of the first type of device includes the communication identifier of the first type of device and at least one of the following: a third-party identifier of the first type of device or a correspondence between the third-party identifier of the first type of device and the communication identifier.

[0018] It should be understood that the third-party identifier in this application can be understood as any identifier other than the perception identifier and the communication identifier, which can be used to identify an object / device / target / object.

[0019] Based on this scheme, the first network element can obtain the communication identifier of the first type of device by requesting the context of the first type of device from the third network element. It may also obtain the third-party identifier of the first type of device and / or the correspondence between the third-party identifier and the communication identifier.

[0020] In conjunction with the first aspect mentioned above, in one possible design, the first network element sends a third message to the fourth network element, the third message being used to request the communication identifier of the terminal device in the first area; the first network element receives at least one communication identifier from the fourth network element, the at least one communication identifier being used by the first network element to obtain second information.

[0021] Based on this scheme, the first network element can request the communication identifier of the terminal device in the first area from the fourth network element, and based on the communication identifier fed back by the fourth network element, determine the communication identifier of the first type of device in the terminal device, and obtain the second location information.

[0022] In conjunction with the first aspect mentioned above, in one possible design, the first network element can determine the first type of equipment within the first area based on information fed back by the third network element and / or the fourth network element. Here, "determining the first type of equipment within the first area" can also be replaced by: determining the communication identifier of the first type of equipment within the first area, determining the number of first type of equipment within the first area, or determining the identification information of the first type of equipment.

[0023] In one possible implementation, the first network element can determine the first type of device in the first area by taking the intersection / union of the information fed back by the third network element and the communication identifier fed back by the fourth network element (or, alternatively, by determining the communication identifier / quantity / identification information of the first type of device).

[0024] In another possible implementation, the first network element can determine the first type of device in the first area based solely on the communication identifier fed back by the third or fourth network element (or, alternatively, determine the communication identifier / quantity / identification information of the first type of device).

[0025] In this article, the feedback information can also be replaced with: the information sent / replied.

[0026] In conjunction with the first aspect above, in one possible design, the method further includes: a first network element receiving a fourth message from a fifth network element, the fourth message being used to request the association between the sensing identifier and the communication identifier of a first type of device within a first area; the first network element sending to the fifth network element at least one of the following information for at least one first type of device within the first area: sensing identifier, communication identifier, first location information, or second location information.

[0027] Based on this scheme, the first network element can acquire the first information and the second information and determine the association between the perception identifier and the communication identifier of the first type of device when triggered by the fifth network element. The first network element can also feed back the determined information to the fifth network element so that the second network element can provide services to the first type of device based on the acquired information.

[0028] In conjunction with the first aspect mentioned above, in one possible design, the third location information is obtained based on satellite positioning.

[0029] It should be understood that "based on satellite positioning" can be understood as positioning / location information obtained using satellite positioning technology. This application does not limit the satellite positioning technology. For example, satellite positioning technology may include Global Positioning System (GPS), Real-time Kinematic (RTK), Global Navigation Satellite System (GNSS), etc.

[0030] Based on this scheme, satellite positioning information can also be combined to associate the communication identity and perception identity of the first type of device, further enhancing the accuracy of the association.

[0031] In a second aspect, a communication device is provided for implementing the method implemented by the first network element in the first aspect described above.

[0032] The communication device includes modules, units, or means that implement the above methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0033] In conjunction with the second aspect above, in one possible design, the communication device includes a transceiver module and a processing module: wherein the transceiver module is used to acquire first information and second information; wherein the first information includes a sensing identifier of a first type of device within a first area and first location information corresponding to the sensing identifier, and the second information includes a communication identifier of the first type of device within the first area and at least one of the following: second location information or third location information corresponding to the communication identifier. The processing module is used to associate the sensing identifier and the communication identifier of the first type of device based on at least one of the following: second location information or third location information.

[0034] In conjunction with the second aspect described above, in one possible design, the transceiver module is further configured to send a first message to the second network element. The first message requests information about a first type of device within the first area. This information includes the sensing identifier and location information of the first type of device. The transceiver module acquires the second information by receiving information from the second network element.

[0035] In conjunction with the second aspect above, in one possible design, the transceiver module is further configured to receive information from the second network element indicating the number of first-type devices in the first area, and / or information indicating the type of first-type devices.

[0036] In conjunction with the second aspect above, in one possible design, the transceiver module is further configured to send a second message to the third network element, the second message being used to request the communication identifier of the first type of device in the first area; the transceiver module is further configured to receive at least one communication identifier from the third network element, the at least one communication identifier being used to obtain second information.

[0037] In conjunction with the second aspect above, in one possible design, the second message is used to request the context of a first type of device within the first area; the transceiver module receives at least one communication identifier from a third network element, including: receiving the context of at least one first type of device from the third network element, wherein the context of the first type of device includes the communication identifier of the first type of device and at least one of the following: a third-party identifier of the first type of device or a correspondence between the third-party identifier of the first type of device and the communication identifier.

[0038] In conjunction with the second aspect above, in one possible design, the transceiver module is further configured to send a third message to the fourth network element, the third message being used to request the communication identifier of the terminal device in the first area; the transceiver module is further configured to receive at least one communication identifier from the fourth network element, the at least one communication identifier being used to obtain second information.

[0039] In conjunction with the second aspect described above, in one possible design, the processing module is further configured to determine the first type of device within the first area based on information fed back by the third network element and / or the fourth network element. Here, "determining the first type of device within the first area" can also be replaced by: determining the communication identifier of the first type of device within the first area, determining the number of first type devices within the first area, or determining the identification information of the first type of device.

[0040] In conjunction with the second aspect above, in one possible design, the transceiver module is further configured to receive a fourth message from the fifth network element, the fourth message being used to request the association between the sensing identifier and the communication identifier of the first type of device within the first area; the transceiver module is further configured to send to the fifth network element at least one of the following information of at least one first type of device within the first area: sensing identifier, communication identifier, first location information or second location information.

[0041] In conjunction with the second aspect mentioned above, in one possible design, the third location information is obtained based on satellite positioning.

[0042] Thirdly, a communication device is provided, comprising: a processor configured to execute instructions stored in a memory, wherein when the processor executes the instructions, the communication device performs the method described in any of the preceding aspects. The communication device may be a first network element in the first aspect or any possible design of the first aspect, or a module (e.g., a chip) applied to a first network element.

[0043] In one possible design, the communication device also includes a memory for storing computer instructions. Optionally, the processor and memory are integrated together, or they are separate.

[0044] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0045] Fourthly, a communication device is provided, comprising: a processor and an interface circuit, the interface circuit being used to communicate with a module outside the communication device; the processor being used to execute the method described in any of the preceding aspects via logic circuitry or by running a computer program or instructions. The communication device may be a first network element in the first aspect or any possible design of the first aspect, or a module (e.g., a chip) applied to a first network element.

[0046] Alternatively, the interface circuit can be a code / data read / write interface circuit, which receives computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmits them to the processor so that the processor runs the computer execution instructions to perform the methods described in any of the above aspects.

[0047] In one possible design, the communication device also includes a memory for storing computer programs or instructions. Optionally, the processor and memory are integrated together, or the processor and memory are separate.

[0048] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0049] In some possible designs, the communication device can be a chip or a chip system.

[0050] Fifthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the methods described in the first aspect above, or any possible design of the first aspect.

[0051] In a sixth aspect, this application provides a computer program product containing instructions that, when executed on a computer, enable the computer to perform the methods described in the first aspect above, or any possible design of the first aspect.

[0052] In a seventh aspect, a communication device (e.g., a chip or a chip system) is provided, comprising a processor for implementing the functions described in the first aspect or any possible design of the first aspect. In one possible design, the communication device further comprises a memory for storing necessary program instructions and data. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0053] Eighthly, a communication system is provided. In one possible design, the communication system includes a first network element and at least one other network element, such as the second, third, fourth, or fifth network element involved in the possible designs of the first aspect described above, wherein the first network element is used to perform the methods of the first aspect described above, or any possible design of the first aspect.

[0054] The technical effects of any of the design methods in aspects two through eight can be found in the technical effects of the different design methods in aspect one above, and will not be repeated here. Attached Figure Description

[0055] Figure 1 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0056] Figure 2 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0057] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0058] Figure 4 is a schematic flowchart of a process for processing sensing data provided in an embodiment of this application;

[0059] Figure 5 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0060] Figure 6 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0061] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0062] Figure 8 is a schematic diagram of another communication device provided in an embodiment of this application;

[0063] Figure 9 is a schematic diagram of the structure of a chip system provided in an embodiment of this application. Detailed Implementation

[0064] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of this application are first introduced as follows.

[0065] 1. Perception:

[0066] In communication networks incorporating sensing technologies, radio signals transmitted and / or received by network elements in the environment can be used to determine the characteristics of targets (or sensed targets, such as objects, animals, or people). These characteristics include the target's distance, orientation, speed, motion, and behavior. Based on this sensed target characteristic information, the network can provide services such as high-precision positioning, gesture capture and activity recognition, passive object detection and tracking, imaging, and environmental reconstruction. Furthermore, the introduction of sensing also helps improve communication performance and efficiency.

[0067] In this application embodiment, a network element that has sensing capability (or sensing function) and can acquire and process sensing data to sense a target can be called a sensing network element.

[0068] In the embodiments of this application, "acquiring sensing data" can also be replaced with descriptions such as "collecting sensing data", "determining sensing data", or "obtaining sensing data".

[0069] In this embodiment, the sensing network element can acquire sensing data based on radio signals it transmits and / or receives in the environment, or it can receive sensing data from other network elements. For example, a terminal device or an access network (AN) device can send the measured sensing data to the sensing network element.

[0070] 2. Low-altitude network:

[0071] Low-altitude networks are a new network standard for communication systems to face the future network evolution. They refer to communication networks targeting low-altitude airspace (low-altitude airspace generally refers to airspace with a vertical height of less than 1,000 meters) and can also be called low-altitude infrastructure networks. The embodiments of this application do not limit the name of the network.

[0072] In low-altitude networks, the introduction of unmanned aerial vehicles (UAVs) with communication modules, enabling them to function as terminal devices and collaborate with network elements such as base stations to provide services, such as drone logistics delivery, represents a promising application prospect. UAVs can also be referred to as unmanned aerial vehicles.

[0073] If drones can serve as terminal devices in a communication network, to meet the needs of operators, users, or low-altitude enterprises—such as the network dynamically planning routes for drones and assisting them in obstacle avoidance—the communication network needs to possess the ability to locate and coordinate drones. For drone scheduling, after a drone connects to the network, the network can assign it identification information, such as a user equipment identity (UE ID), allowing for drone scheduling based on this identity. For drone positioning, we consider introducing sensing features into the low-altitude network to obtain the location information of drones within the sensing area. However, even with the introduction of sensing features, since there are still many human-connected terminals (such as mobile phones and other user-owned terminal devices) in the current communication network, there is currently a lack of an effective solution to distinguish between human-connected terminals and network-connected drone terminals within the target area, enabling global coordinated scheduling of drones.

[0074] Based on the above problems, embodiments of this application provide a communication method, device, and chip that can filter out a certain type of device (e.g., a drone) from the perceived targets in the target area and establish the association between the communication identity and the perception identity of this type of device in the target area. This enables the combined use of the perception network and the communication network to coordinate the scheduling of this type of device, thereby better assisting this type of device in fulfilling its related needs.

[0075] In this embodiment, the UE ID can be any identification information that can identify the terminal device, such as the Subscription Permanent Identifier (SUPI), the Generic Public Subscription Identifier (GPSI), the Terminal Equipment Identifier (TEI), the International Mobile Subscriber Identity (IMSI), the Temporary Mobile Subscriber Identity (TMSI), etc. This embodiment does not limit the UE ID.

[0076] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0077] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is merely a description of the relationship between the related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., are not necessarily different. Furthermore, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0078] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0079] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the sending device by sending configuration information to the receiving device.

[0080] In the embodiments of this application, "predefined," "pre-defined," "pre-configured," "pre-configured," or "locally configured" can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device. For example, it can be burned into the device when it leaves the factory, or configured when it first connects to the network. The embodiments of this application do not limit the specific implementation method. "Saving" can refer to saving in one or more memories. The one or more memories can be separate settings or integrated into the encoder or decoder, processor, or communication device. The one or more memories can also be partially separate settings and partially integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and the embodiments of this application do not limit this.

[0081] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0082] In this embodiment, "sending information to... (taking the first network element as an example)" can be understood as the destination of the information being the first network element. This can include sending information directly or indirectly to the first network element. "Receiving information from... (taking the first network element as an example)" can be understood as the source of the information being the first network element, and can include receiving information directly or indirectly from the first network element. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this embodiment can be understood in a similar way, and will not be elaborated further here.

[0083] The communication method provided in this application embodiment can be used in any communication system, such as a third-generation partnership project (3GPP) communication system, for example, a long-term evolution (LTE) system; a fifth-generation (5G) mobile communication system; a hybrid LTE and 5G network system; a new radio (NR) system; a vehicle-to-everything (V2X) system; a device-to-device (D2D) communication system; a machine-to-machine (M2M) communication system; an internet of things (IoT) system; a narrow band internet of things (NB-IoT) system; enhanced mobile broadband (eMBB); ultra-reliable and low-latency communication (URLLC); enhanced machine-type communication (eMTC); a vehicular short-range wireless communication system; and various types of future communication systems. It can also be used in non-terrestrial communication networks. Network (NTN) systems (such as satellite communication systems) and non-3GPP communication systems are not restricted. Furthermore, the term "system" and "network" are interchangeable.

[0084] It should be noted that the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0085] Figure 1 is a schematic diagram of a possible, non-limiting communication system provided in an embodiment of this application. As shown in Figure 1, the communication system includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal device (120a-120j in Figure 1, collectively referred to as 120). The RAN may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network device in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0086] Optionally, the communication system 10 may also include an Internet 300. The Internet 300 may be connected to the core network 200 or the RAN 100.

[0087] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, NTN (non-terrestrial network) systems, or future-oriented evolution systems. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system that integrates two or more of the above systems.

[0088] Terminal devices can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminals can be widely used in various scenarios, such as D2D, V2X communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the form of the terminal device.

[0089] RAN node 110, sometimes referred to as access network equipment, network equipment, RAN entity, or access node, constitutes part of the communication system. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal equipment 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal equipment 120j accessing RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal equipment 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0090] In one possible scenario, RAN nodes can assist terminals in achieving wireless access. For example, an RAN node can be a base station, a Node B (also called a base station), an evolved Node B (eNodeB) in an LTE system, a next-generation Node B (gNB) in a 5G system, an access point (AP), a transmission reception point (TRP), a base station in a future mobile communication system, or an access node in a WiFi system. An RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, an RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software that can implement all or part of the functions of the RAN node.

[0091] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0092] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0093] Figure 2 is a schematic diagram of a possible, non-limiting network architecture provided by an embodiment of this application. As shown in Figure 2, the communication architecture mainly includes the following network elements: UE, AN (or RAN, illustrated as (R)AN in Figure 2), access and mobility management function (AMF) network element, unified data management (UDM) network element, network data analytics function (NWDAF) network element, location management function (LMF) network element, policy control function (PCF) network element, sensing function (SF) network element, and network exposure function (NEF) network element.

[0094] Among them, the AMF network element is mainly responsible for receiving non-access stratum (NAS) signaling (including mobility management (MM) signaling and session management (SM) signaling) from terminal equipment and related signaling from access network equipment (e.g., base station-level N2 signaling that interacts with the AMF), completing the user registration process, forwarding SM signaling, and mobility management.

[0095] SMF is responsible for session management functions, completing processes related to PDU session establishment, release, and update.

[0096] The PCF network element is mainly responsible for user policy management, including both mobility-related policies and protocol data unit (PDU) session-related policies, such as quality of service (QoS) policies and charging policies.

[0097] UDM network elements are primarily responsible for storing users' subscription data.

[0098] The AUSF network element is primarily responsible for authenticating and authorizing the access of terminal devices.

[0099] The NWDAF network element is primarily responsible for providing network analysis services based on network service request data.

[0100] LMF network elements are primarily responsible for providing location services.

[0101] The NEF network element is primarily responsible for managing publicly accessible network data.

[0102] SF network elements have sensing capabilities and are primarily responsible for sensing targets in the environment.

[0103] Optionally, the network architecture may also include some network elements not shown, such as session management function (SMF) network elements, authentication server function (AUSF) network elements, etc.

[0104] The functions of other network elements mentioned in this article can be found in existing communication protocols and will not be elaborated upon here.

[0105] Optionally, in this network architecture, the sensing data acquired by (R)AN / UE can be transmitted to the SF network element via the control plane or the user plane. If the sensing data plane is transmitted via the user plane, the sensing data can be forwarded by the user plane function (UPF) network element or directly transmitted to the SF network element.

[0106] Optionally, control signaling between the SF network element and the (R)AN / UE can be transmitted through the AMF network element.

[0107] Optionally, the UE may have a sensing function. (R)AN may support sensing billing in sensing scenarios.

[0108] As shown in Figure 2, the SF network element can set up interfaces and interact with network elements such as AMF, NEF, UDM, NWDAF, PCF, LMF, and UPF. The specific definitions are as follows:

[0109] NS1: A new NS1 interface has been added between SF network elements and AMF network elements. This interface can transmit control signaling. For scenarios where sensing data is transmitted through the control plane, this interface can also transmit sensing data.

[0110] NS2: A new NS2 interface is added between SF network elements and NEF network elements. This interface can transmit signaling messages between SF network elements and service-side AF (application function) relayed through NEF. In addition, this interface can expose the perception results to the AF.

[0111] NS3: A new NS3 interface is added between SF network elements and UDM network elements. Through this interface, authentication or authorization can be performed, and UE-related subscription information or other information can be obtained.

[0112] NS4: A new NS4 interface has been added between SF network elements and NWDAF network elements. Through this interface, SF network elements can work with NWDAF network elements to complete AI (Artificial Intelligence) processing related to perception services.

[0113] NS5: A new NS5 interface is added between SF network elements and PCF network elements. Through this interface, SF network elements can transmit information such as sensing requirements, quality of service (QoS) requirements, or sensing results of sensing services to PCF network elements. PCF can then make decisions to generate policies and charging control (PCC) policies related to sensing services.

[0114] NS6: A new NS6 interface is added between SF network elements and LMF network elements. Through this interface, SF network elements can obtain location-related information, such as the sensing area, the RAN information of the sensing target (referring to the information of the RAN nodes that sense the sensing target), and the location information of the sensing target.

[0115] NS7: A new NS7 interface is added between the SF network element and the UPF network element. Through this interface, sensing data transmitted via the user plane can be forwarded from the UPF network element to the SF network element. Optionally, in scenarios where the sensing data comes from (R)AN, if the data is forwarded by the UPF network element, the UPF network element can support data transmission at the (R)AN granularity.

[0116] Additionally, as shown in Figure 2, the UE can access the network via (R)AN, and the terminal device can communicate with the AMF network element via the next generation (NG)1 interface (N1). The (R)AN can communicate with the AMF network element via the N2 interface (N2). The AMF network element can communicate with the UDM network element via the N8 interface (N8). The PCF network element can communicate with the NEF network element via the N5 interface (N5). The AF network element can communicate with the NEF network element via the N33 interface (N33).

[0117] Optionally, if the network architecture also includes a UPF network element, (R)AN can communicate with the UPF network element through the N3 interface (N3 for short).

[0118] Optionally, in the sensing scenario, in addition to the interfaces set up between the SF network element and other network elements, existing interfaces (such as N1, N2, N5, N8, N33, etc.) can support the transmission of sensing service-related information, such as authentication information, sensing service type, sensing service quality requirements, sensing measurement data, sensing results, etc.

[0119] Optionally, if the LMF network element supports sensing functionality, an interface can be added between the LMF network element and the gateway mobile location center (GMLC) to transmit sensing service-related information.

[0120] It should be noted that the names of each network element, the interfaces between each network element, the messages between each network element, or the names of the parameters in the messages in this application embodiment are just examples. In the specific implementation, they can also be other names, and this application embodiment does not make specific limitations on them.

[0121] The communication method provided in the embodiments of this application will be described below with reference to Figure 1 or Figure 2.

[0122] Figure 3 is a flowchart of a communication method provided in an embodiment of this application. Figure 3 illustrates the method by taking a first network element as the execution subject of the flowchart, but this application does not limit the execution subject of the flowchart. For example, the first network element in Figure 3 can also be a module applied to the first network element, such as a chip, chip system, or processor, or it can be a logical node, logical module, or software that can implement all or part of the functions of the first network element.

[0123] As shown in Figure 3, the method includes:

[0124] S301, the first network element acquires first information and second information. The first information includes a sensing identifier of a first type of device within a first area and first location information corresponding to the sensing identifier; the second information includes a communication identifier of a first type of device within the first area and second location information corresponding to the communication identifier.

[0125] S302. The first network element associates the sensing identifier and communication identifier of the first type of device with the first location information and the second location information. Associating the sensing identifier and communication identifier of the first type of device can also be understood as: determining the correspondence (or association) between the sensing identifier and communication identifier of the first type of device; or, for the same first type of device, determining the correspondence between the sensing identifier and communication identifier of that device, or determining the sensing identifier and communication identifier of that device.

[0126] Based on the communication method provided in this application embodiment, the first network element can associate the perception identifier and communication identifier of the first type of device in the first area with the location information corresponding to the two types of identification information. In other words, the first type of device can be screened out from the perception targets in the first area and associated with its communication identity. Thus, the first type of device can be coordinated and scheduled through the communication network to assist the first type of device and provide services to it. For example, information can be transmitted to the first device through the communication network to assist the first device in navigation and obstacle avoidance, motion planning, detection and collision avoidance (DAA), etc.

[0127] The embodiments of this application do not limit the first network element. For example, the first network element may be an NWDAF network element, or, for another example, an SF network element.

[0128] The following is a detailed introduction to S301.

[0129] This application does not limit the first type of device. For example, the first type of device may be a drone.

[0130] In S301, the first network element can receive first information from the second network element. The second network element has sensing capabilities and can also be called a sensing network element. For example, the second network element can be an SF network element or a sensing server.

[0131] Before the first network element receives the first information, it can send a first message to the second network element. This first message triggers the second network element to acquire the sensing identifiers and location information of the first type of devices within the first area, and then feeds back these same information to the first network element. For example, the first message can be a request message, requesting the sensing identifiers and location information of the first type of devices within the first area. Alternatively, the first message can be a subscription message, subscribing to the sensing identifiers and location information of the first type of devices within the first area.

[0132] The first region can be a geographical area, such as a circular area centered on a specific geographical location with a certain radius, or a specific urban area. The first region can also be a communication area / 3GPP area, such as the signal coverage area of ​​an access network device (e.g., the coverage area of ​​a base station), cell coverage area, tracking area (TA) coverage area, public land mobile network (PLMN) coverage area, etc.

[0133] In this embodiment, the perception identifier is identification information used to identify the perception target, which can be understood as the identifier when an object, person, animal, or other object is used as a perception target. That is, the second network element can generate an identifier for the perceived target (i.e., the perception target) through an identification mechanism (or, the identifier assigned by the second network element to the perception target), which can be called the perception identifier. For example, the perception identifier can be the target ID.

[0134] It is understood that the perception identifier in the embodiments of this application may have other names, such as perception target identifier, but its function is to identify the perception target. The embodiments of this application do not limit its name.

[0135] In this embodiment of the application, the location information obtained by sensing the first type of device and corresponding to the sensing identifier of the first type of device can be referred to as the first location information.

[0136] In this embodiment, location information can be represented in the form of coordinate points, such as latitude and longitude. Location information can also be represented in the form of spatial coordinate points, such as spatial location points in a Cartesian coordinate system or a polar coordinate system. This embodiment does not limit the form of location information.

[0137] Optionally, if for a certain sensing target, multiple coordinate points at different times are sensed, the positional information formed by these multiple coordinate points can be called trajectory information.

[0138] This application does not limit the specific meaning of the first message in its embodiments. In one possible implementation, the first message may instruct the second network element to obtain the sensing identifier and location information of a first type of device within the first area. For example, the first message may be a message requesting the sensing identifier and location information of a first type of device within the first area. In another possible implementation, the first message may instruct the second network element to obtain information about a sensing target within the first area, and carry information indicating that the type of the sensing target is first type, as well as information indicating that the location information of the sensing target needs to be obtained. For example, a field in the first message is used to indicate the type of the sensing target; setting the value of this field can indicate that the type of the sensing target is first type. Another field in the first message is used to indicate the specific information of the sensing target that needs to be obtained; setting the value of this field can indicate that the location information of the sensing target needs to be obtained.

[0139] The specific name of the first message is not limited in the embodiments of this application. For example, the name of the first message can be Nsf_XXXX_Request / Response or other names.

[0140] In this embodiment of the application, a message provides an indication, which can also be referred to as the message carrying indication information. For example, a first message carrying information indicating that the type of the perceived target is a first type can also be referred to as the first message indicating that the type of the perceived target is a first type.

[0141] Optionally, the first message indicates obtaining location information, or it can be replaced with indicating obtaining trajectory information.

[0142] Optionally, the type of the perceived target indicated by the first message can be understood as perceiving "who you are," or in other words, the first network element needs the second network element to perceive "who" information. For example, the type of perceived target could be a drone, a vehicle, a person, a bird, etc. Taking a low-altitude scenario as an example, assuming the first type of device is a drone, the first message can indicate that the type of perceived target is "drone." After receiving the first message, the second network element can determine, based on the type of perceived target, that the first network element needs to perceive a drone. The second network element can then identify the perceived target and obtain its information based on the processing of the perceived data. For example, by distinguishing the drone's trajectory from the trajectory of similar objects (such as birds), the drone can be identified and its location obtained.

[0143] Optionally, the first message may also carry information indicating the first area. For example, assuming the first area is the signal coverage area of ​​an access network device, the first message may carry the identification information of that access network device. Assuming the first area is a cell / tracking area coverage area, the first message may carry the identification information of the cell / tracking area. Yet another example, assuming the first area is a city, the first message may carry the city's identification number. Alternatively, the information indicating the first area may be sent separately from the first message.

[0144] Optionally, the first message may also indicate other information. For example, the first message may also indicate the number of first-type devices that need to be sensed (or, the first message may also indicate the number of sensed targets). Another example is that the first message may also indicate the number of first-type devices that need to be fed back by the second network element (or, the first message may indicate the number of sensed targets that need to be fed back by the second network element). Yet another example is that the first message may also indicate the time at which the second network element feeds back the first information.

[0145] The following section introduces how the second network element determines the first information.

[0146] The second network element can acquire sensing data obtained by sensing objects within the first area. Specifically, the second network element can collect sensing data based on signals transmitted and / or received by other network elements (e.g., a base station). Alternatively, the second network element can receive sensing data from other network elements. After obtaining the sensing data, the second network element processes the data, filters out the location information of the first type of devices, and assigns sensing identifiers to the first type of devices.

[0147] In one possible implementation, processing the sensing data may specifically include the following steps: spatially clustering the sensing data (e.g., point cloud) reported at each time unit (e.g., a wireless frame / sensing frame) to obtain clusters / sensing targets and their spatial locations, and then assigning IDs to the clusters and targets. Next, in the time dimension, i.e., based on multiple consecutive wireless frames / sensing frames, location stitching is performed to generate a trajectory. Then, a neural network model can be trained based on the trajectory information to perform target recognition and identify a first type of device. For example, assuming the first type of device can be a drone, the model can be trained using 10,000 drone trajectories to distinguish drones from birds.

[0148] In one possible implementation, the process of the second network element processing the sensed data may include a data signal processing section and a communication data processing section. The digital signal processing section includes: the second network element sampling the analog signal and converting it into a digital signal using an analog-to-digital converter (ADC); inverting the sense channel; performing symbol-dimensional Fast Fourier Transform (FFT) and Inverse Fast Fourier Transform (IFFT) to obtain the range spectrum; performing inter-symbol FFT to obtain the velocity spectrum; performing constant false alarm rate (CFAR) detection; and calculating the angle spectrum. The general data processing section includes: single-wireless frame clustering, multi-wireless frame data association, and target recognition.

[0149] For example, as shown in Figure 4, a specific process for the second network element to process sensing data may include: sampling the analog signal and performing analog-to-digital (AD) conversion on the sampled signal to obtain in-phase and quadrature (IQ) component data; performing CP removal and FFT on the IQ data; estimating the range spectrum (R-spectrum) and velocity spectrum (V-spectrum) to obtain the radar spectrum; performing CFAR; measuring the angle to obtain the angle spectrum; performing positioning estimation; processing by the building baseband unit (BBU) to obtain point cloud data; clustering the point cloud data; performing tracking filtering to obtain target data; and performing target recognition. The R-spectrum estimation process includes: channel estimation using least squares (LS), windowing, and IFFT transformation to the time domain. The V-spectrum estimation process includes: decimation along the range dimension, windowing, and FFT transformation to the frequency domain.

[0150] Optionally, the first information may also include other information about the sensed target. For example, the second network element may also determine the number of sensed targets (i.e., the first type of device) and feed it back to the first network element. As another example, the first information may also include the type of sensed target (i.e., the first type of device); for instance, the first information may include information indicating the type of drone.

[0151] This application does not limit the message carrying the first information in its embodiments. For example, if the first message is a subscription message, the first information fed back by the second network element to the first network element can be carried in a notification message for the subscription message. As another example, if the first message is a request message, the first information fed back by the second network element to the first network element can be carried in a reply message (or response message) for the request message.

[0152] In S301, before the first network element receives the second information, the first network element can send a second message to the third network element. The second message can trigger the third network element to obtain the communication identifier of the first type of device in the first area and feed back the communication identifier of the first type of device in the first area to the first network element. For example, the second message can be a request message, requesting the communication identifier of the first type of device in the first area. Another example is that the second message can be a subscription message, subscribing to the communication identifier of the first type of device in the first area.

[0153] The communication identifier of the first type of device is the identifier used when the first type of device performs communication functions. It can also be understood as an identifier used to identify the communication identity of the first type of device within the communication network. Optionally, the communication identifier of the first type of device can be the identification information assigned to it by the communication network after the first type of device joins the network (or, after the communication network authenticates and authorizes the first type of device to access the network). For example, the communication identifier of the first type of device can be its ID in the 3GPP communication system, such as its UE ID, generic public subscription identifier (GPSI), or user permanent identifier (SUPI).

[0154] The third network element can be a network element that stores information about the first type of device. For example, if the first type of device is an unmanned aircraft system (UAS), the third network element can be the network functions (NF) of the UAS.

[0155] This application does not limit the specific meaning of the second message in its embodiments. In one possible implementation, the second message may instruct a third network element to provide the context of a first-type device that is certified and authorized within the first area. For example, if the first-type device is a drone, the second message may instruct the third network element to provide the USS UAV authorization / authentication (UUAA) context within the first area. After receiving the second message, the third network element sends the context of the first-type device certified and authorized within the first area to the first network element. The context of the first-type device includes the communication identifier of the first-type device. Optionally, the context of the first-type device may also include a third-party identifier of the first-type device, such as the factory identifier of the first-type device: the Civil Aviation Administration (CAA) drone identifier (CAAlevel UAV ID). Optionally, the context of the first-type device may also include the correspondence between the communication identifier of the first-type device and the third-party identifier. In another possible implementation, the second message may instruct the third network element to provide information about the first-type device certified and authorized within the first area. After receiving the second message, the third network element sends information about the first type of authenticated and authorized devices within the first area to the first network element. This information includes the communication identifier of the first type of device. Optionally, the information may also include the context of the first type of device as described above.

[0156] This application does not limit the specific name of the second message in its embodiments. For example, the name of the second message can be Nuasnf_XXXX_Request / Response or other names.

[0157] Optionally, the second message may also carry information indicating the first region. Please refer to the above description of information indicating the first region for details. Alternatively, the information indicating the first region may be sent separately from the second message.

[0158] Optionally, the first network element may also send a message to the fourth network element (the fourth network element may be a network element different from the third network element, such as a UPF or SMF network element; this application embodiment does not limit the fourth network element) to trigger the fourth network element to feed back the communication identifier of the first type of device in the first area to the first network element, for example, triggering the fourth network element to feed back the UE ID list of the first type of device in the first area to the first network element.

[0159] In one possible implementation, the first network element can determine the actual communication identifier of the first type of device (or, the communication identifier of the first type of device in the second information) as the intersection of the communication identifier of the first type of device fed back by the fourth network element and the communication identifier of the first type of device fed back by the third network element (i.e., the communication identifier fed back by the fourth network element and the communication identifier fed back by the third network element that are the same).

[0160] In another possible implementation, the first network element can determine the actual communication identifier of the first type of device by the union of the communication identifier of the first type of device fed back by the fourth network element and the communication identifier of the first type of device fed back by the third network element.

[0161] In this embodiment of the application, the intersection of information fed back by different network elements can be understood as the same information in the information fed back by different network elements being placed in the result set, and the union of information fed back by different network elements can be understood as the information fed back by different network elements being placed in the result set.

[0162] For example, assuming that the communication identifiers fed back by the fourth network element include UE ID1, UE ID2 and UE ID3, and the communication identifiers fed back by the third network element include UE ID2, UE ID3 and UE ID4, the first network element can determine the actual communication identifier of the first type of device by the intersection of the information fed back by the two: UE ID2 and UE ID3.

[0163] For example, suppose the communication identifiers fed back by the fourth network element include UE ID1, UE ID2 and UE ID3, and the communication identifiers fed back by the third network element include UE ID2, UE ID3 and UE ID4. The first network element can determine the actual communication identifier of the first type of device by the union of the information fed back by the two: UE ID1, UE ID2, UE ID3 and UE ID4.

[0164] In another possible implementation, the first network element can determine the actual communication identifier of the first type of device based solely on the communication identifier of the first type of device fed back by the fourth network element. In yet another possible implementation, the first network element can determine the actual communication identifier of the first type of device based solely on the communication identifier of the first type of device fed back by the third network element.

[0165] Optionally, the message sent by the first network element to the fourth network element may carry information indicating the first area. Please refer to the above description of information indicating the first area for details. Alternatively, the message sent by the first network element to the fourth network element may be sent separately from the information indicating the first area.

[0166] This application embodiment does not limit the message sent by the first network element to the fourth network element. Optionally, the message may instruct the fourth network element to distinguish between human-network terminals and first-type devices through the data plane / user plane. Optionally, the message sent by the first network element to the fourth network element may include information for distinguishing between first-type devices and human-network terminals. After receiving the message sent by the first network element, the fourth network element can perform user behavior analysis based on the information carried in the message, filter out first-type devices in the first area from the terminal devices in the first area, and thus determine the communication identifier of the first-type devices.

[0167] For example, information used to distinguish between the first type of device and the human-network terminal may include the UAS service provider's (USS) internet protocol (IP) address, data network name (DNN), and filtering templates for data interaction with the USS (e.g., IP 5-tuples or service content filters). For instance, assuming the first type of device is a drone, based on the fact that drones typically report collected radar / video / Global Navigation Satellite System (GNSS) data, the content filter may include the content fields corresponding to the radar / video / GNSS data. The fourth network element can filter out data that may be interacting between the terminal device and the USS based on the content filter, thereby determining that the communication terminal type is a drone rather than a regular human-network terminal, and further determining the drone's communication identifier.

[0168] Optionally, the first network element can also send a message to the fifth network element (the fifth network element is a different network element from the third network element, such as an AMF network element; this embodiment does not limit the fifth network element) to trigger the fifth network element to feed back the communication identifiers of the terminal devices in the first area to the first network element, for example, triggering the fifth network element to feed back the UE ID list of the terminal devices in the first area to the first network element. After receiving the communication identifiers of the terminal devices in the first area, the first network element can determine the actual communication identifier of the first type of device (or, in other words, determine it as the communication identifier of the first type of device in the second information) by the intersection of the communication identifier of the terminal device fed back by the fifth network element and the communication identifier of the first type of device fed back by the third network element. Optionally, if the first network element also receives the communication identifier of the first type of device in the first area from the fourth network element, the first network element can also refer to the communication identifier fed back by the fourth network element to determine the actual communication identifier of the first type of device in the first area.

[0169] In one possible implementation, the first network element can determine the intersection of the communication identifier of the terminal device fed back by the fifth network element and the communication identifier of the first type of device fed back by the third network element, and determine the communication identifier of the first type of device in the actual first area as the union of the communication identifier in the intersection and the communication identifier fed back by the fourth network element.

[0170] For example, assuming the communication identifiers fed back by the fifth network element include UE ID1, UE ID2, UE ID3, UE ID4, UE ID5, and UE ID6, the communication identifiers fed back by the fourth network element include UE ID1, UE ID2, and UE ID3, and the communication identifiers fed back by the third network element include UE ID2, UE ID3, and UE ID4, the first network element can determine the intersection of the information fed back by the fifth and third network elements: UE ID2, UE ID3, and UE ID4, and determine the union of this intersection with the information fed back by the fourth network element: UE ID1, UE ID2, UE ID3, and UE ID4. Then, it can be determined that the communication identifiers of the first type of equipment in the actual first area include UE ID1, UE ID2, UE ID3, and UE ID4.

[0171] In one possible implementation, the first network element can determine the intersection of the communication identifier of the terminal device fed back by the fifth network element and the communication identifier of the first type of device fed back by the third network element, and determine the intersection of the communication identifier in the intersection with the communication identifier fed back by the fourth network element as the actual communication identifier of the first type of device in the first area.

[0172] For example, assuming the communication identifiers fed back by the fifth network element include UE ID1, UE ID2, UE ID3, UE ID4, UE ID5, and UE ID6, the communication identifiers fed back by the fourth network element include UE ID1, UE ID2, and UE ID3, and the communication identifiers fed back by the third network element include UE ID2, UE ID3, and UE ID4, the first network element can determine the intersection of the information fed back by the fifth and third network elements: UE ID2, UE ID3, and UE ID4, and determine the intersection of this intersection with the information fed back by the fourth network element: UE ID2 and UE ID3. Then, it can be determined that the communication identifiers of the first type of equipment in the actual first area include UE ID2 and UE ID3.

[0173] Optionally, the message sent by the first network element to the fifth network element may carry information indicating the first area. Please refer to the above description of information indicating the first area for details. Alternatively, the message sent by the first network element to the fifth network element may be sent separately from the information indicating the first area.

[0174] This application embodiment does not limit the message sent by the first network element to the fifth network element. Optionally, the message can be an event exposure subscription / notification message (Namf_EventExposure_Subscribe / Notify). After receiving the message, the fifth network element can send the communication identifier of the terminal device in the first area to the first network element in a response message / notification message / reply message. Optionally, the fifth network element can periodically send the communication identifier of the terminal device in the first area back to the first network element.

[0175] After the first network element determines the communication identifier of the first type of device in the first area, it can send a third message to the sixth network element. The third message carries the communication identifier of the first type of device in the first area, such as a list of UE IDs of the first type of device in the first area. The third message can trigger the sixth network element to locate the first type of device in the first area based on the communication identifier of the first type of device, obtain the location information of the first type of device, and report the location information of the first type of device back to the first network element.

[0176] The sixth network element has a positioning function, which can locate the device based on its communication identifier. For example, the sixth network element can be a gateway mobile location center (GMLC) network element or an LMF network element in a location service (LCS) system.

[0177] In this embodiment of the application, the location information corresponding to the communication identifier of the first type of device obtained by locating the first type of device can be referred to as the second location information.

[0178] Optionally, if for a certain device, the location information formed by the multiple coordinate points at different times can be called trajectory information.

[0179] The embodiments of this application do not limit the specific meaning of the third message. In one possible implementation, the third message can be a request message, requesting the sixth network element to locate the device corresponding to the communication identifier included in the third message. In another possible implementation, the third message can be a subscription message, subscribing to the location information corresponding to the communication identifier included in the third message.

[0180] The name of the third message is not limited in this application embodiment. For example, the third message can be Ngmlc_Location Provide Location / Notify.

[0181] Optionally, prior to S301, the seventh network element can send third information to the first network element, which can trigger the first network element to retrieve the first and second information. For example, the third information can trigger the first network element to send a first message to the second network element. Alternatively, the third information can trigger the first network element to send a second message to the third network element. Another example is that the third information can trigger the first network element to send a message to the fourth and / or fifth network element, or even to the sixth network element.

[0182] The seventh network element can be a network element that requests services from the first type of device, or a network element related to the first type of device. This application embodiment does not limit the seventh network element. For example, the seventh network element can be an application server (AS), an AF network element, an application platform, or a third-party platform. As another example, if the first type of device is a drone, the seventh network element can be a USS (Unmanned Aerial Vehicle).

[0183] This application does not limit the specific meaning of the third information in its embodiments. In one possible implementation, the third information may indicate / request the determination of the association between the identity (which can be simply referred to as the perception identity) of a first type of device in the first area as a sensing target and its communication identity; or, the third information may indicate / request the determination of the communication and sensing association of a first device in the first area; or, the third information may indicate / request the association between the communication identity and the perception identity of a first device in the first area. After receiving the third information, the first network element obtains the first information and the second information according to the indication / request of the third information. In another possible implementation, the third information may indicate a first service. After receiving the third information, the first network element determines that if it wants to provide the first service, it needs to determine the association between the perception identity and the communication identity of a first type of device in the first area (or, determine the perception and communication association of a first type of device in the first area, or, associate the perception identity and the communication identity of a first type of device in the first area), and then obtains the first information and the second information. For example, the first service can be obstacle avoidance, navigation, path planning request, detection and avoidance request, etc. After receiving the third information, the first network element determines that it is necessary to establish the association between the perception identity and communication identity of the UAV in the first area in order to provide the first service for the UAV.

[0184] In this embodiment, the third information can be carried in a newly defined message, and its function can be found in the above description of the specific meaning of the third information. Alternatively, the third information can be a newly added information element, and its function can be found in the above description of the specific meaning of the third information. In this case, the third information can be carried in an existing message, such as an analysis subscription message (Nnwdaf_AnalyticsSubscription_Subscribe) or an analysis information request message (Nnwdaf_AnalyticsInfo_Request).

[0185] For example, the third information can be a new analytics ID. When the seventh network element sends an analytics subscription message or an analytics information request message to the first network element, if the message carries the new analytics ID, it can trigger the first network element to obtain the first information and the second information.

[0186] Optionally, the seventh network element can also send information indicating the first area to the first network element. For details, please refer to the above description of information indicating the first area. This information indicating the first area can be carried in the same message as the third information, or it can be sent separately from the third information.

[0187] Optionally, the seventh network element can also send fourth information to the first network element, which is used to request the first network element to provide the address information of the eighth network element. The eighth network element can be a user plane / data plane network element in the sensing scenario. Optionally, the eighth network element can split sensing data from the first type of device and sensing data from other devices (e.g., access network devices, other terminal devices). The eighth network element can also obtain auxiliary information based on the split sensing data, which can help the seventh network element provide services to the first type of device. This application embodiment does not limit the eighth network element; for example, the eighth network element can be a sensing process function (SPF) network element. It should be understood that in this application embodiment, splitting can refer to data splitting.

[0188] Optionally, the third information can be carried in the same message as the fourth information, or the third information can be sent separately from the fourth information.

[0189] Optionally, the seventh network element can send the third information to the first network element directly. Alternatively, the seventh network element can send the third information to the first network element through an intermediate network element, i.e., the seventh network element sends the third information to the intermediate network element, which then forwards the third information to the first network element. Similarly, the seventh network element can send the fourth information directly to the first network element, or it can send the fourth information to the first network element through an intermediate network element.

[0190] Optionally, prior to S301, the first network element can select at least one of the following network elements: a second network element, a third network element, a fourth network element, a fifth network element, or a sixth network element. For example, the first network element can select a network element near the first region based on the first region.

[0191] The following is a detailed introduction to S302.

[0192] In S302, the first network element can determine (or establish / obtain / get) the association (or relationship / correspondence) between the sensing identifier and the communication identifier of the first type of device based on the first location information and the second location information. Wherein, if the sensing identifier and the communication identifier are associated, then the first type of device corresponding to the sensing identifier and the first type of device corresponding to the communication identifier can be considered to be the same device.

[0193] In one possible implementation, the first network element can determine the similarity between the first location information and the second location information, and based on whether the similarity reaches a preset threshold, determine whether the sensing identifier corresponding to the first location information and the communication identifier corresponding to the second location information can be associated. If the similarity reaches the threshold, they are considered associated; if the similarity does not reach the preset threshold, they are considered not associated. This application embodiment does not limit the preset threshold; for example, it can be 90%.

[0194] If the first and second location information are trajectory information, i.e., including multiple coordinate point positions, one possible implementation for determining the similarity between the first and second location information is as follows: the first network element can determine whether a coordinate point in the first location information coincides with a coordinate point in the second location information, and determine the number of coinciding coordinate points in the first location information. If the proportion of the number of coinciding coordinate points in the total number of coordinate points included in the first location information reaches a preset threshold, the first network element can consider the first and second location information similar and can establish an association between the communication identifier and the sensing identifier. If the preset threshold is not reached, the first network element can consider the first and second location information dissimilar, and the communication identifier and the sensing identifier are not associated. Similarly, the first network element can also determine whether the first and second location information are similar and whether the communication identifier and the sensing identifier are associated based on whether the proportion of the number of coinciding coordinate points in the second location information in the total number of coordinate points included in the second location information reaches a preset threshold.

[0195] In another possible implementation, the first network element can determine whether the similarity between a coordinate point in the first location information and a coordinate point in the second location information reaches a first preset threshold, and further determine the number of coordinate points in the first location information whose similarity reaches the first preset threshold (which can be simply referred to as similar coordinate points). If the proportion of the number of similar coordinate points in the total number of coordinate points included in the first location information reaches a second preset threshold, the first network element can consider the first location information and the second location information to be similar, and can establish an association between the communication identifier and the sensing identifier. If the second preset threshold is not reached, the first network element can consider the first location information and the second location information to be dissimilar, and the communication identifier and the sensing identifier are not associated. Similarly, the first network element can also determine whether the first location information and the second location information are similar, and whether the communication identifier and the sensing identifier are associated, based on whether the proportion of the number of similar coordinate points in the second location information in the total number of coordinate points included in the second location information reaches a second preset threshold.

[0196] In another possible implementation, the first network element can determine whether the error / difference between a coordinate point in the first location information and a coordinate point in the second location information is less than a third preset threshold (or, it can determine whether the error / difference is not greater than the third preset threshold), and further determine the number of coordinate points in the first location information whose error / difference is less than the third preset threshold. If the proportion of the number of coordinate points whose error / difference is less than the third preset threshold in the total number of coordinate points included in the first location information reaches a fourth preset threshold, the first network element can consider the first location information and the second location information to be similar, and can establish an association between the communication identifier and the sensing identifier. If the fourth preset threshold is not reached, the first network element can consider the first location information and the second location information to be dissimilar, and the communication identifier and the sensing identifier are not associated. Similarly, the first network element can also determine whether the first location information and the second location information are similar, and whether the communication identifier and the sensing identifier are associated, based on whether the proportion of the number of coordinate points in the second location information whose error / difference is less than the third preset threshold in the total number of coordinate points included in the second location information reaches a fourth preset threshold.

[0197] It should be noted that the embodiments of this application do not limit the values ​​of each preset threshold, nor the size relationship between each preset threshold.

[0198] Optionally, if the first location information and the second location information are trajectory information, in the above implementation of judging the similarity between the first location information and the second location information, the similarity between the first location information and the second location information can be judged based on the proportion of the number of consecutive overlapping coordinate points, the number of consecutive similar coordinate points, and the number of consecutive coordinate points with errors / differences less than a third preset threshold in the total number of coordinate points included in the first location information (or the second location information), and whether the communication identifier and the perception identifier are associated. For details, please refer to the above description.

[0199] Optionally, the first network element can also obtain third location information corresponding to the communication identifier of the first type of device within the first area, and determine whether the communication identifier and the sensing identifier are associated based on the third location information. The method of obtaining the third location information can be different from the method of obtaining the second location information.

[0200] In one possible implementation, the third location information can be location information obtained based on satellite positioning, such as location information obtained based on the Global Positioning System (GPS). Another example is location information obtained based on the BeiDou Navigation Satellite System. Yet another example is location information obtained based on real-time kinematic (RTK) positioning.

[0201] Optionally, the third location information can also be trajectory information, including the positions of multiple coordinate points corresponding to different times.

[0202] In one possible implementation for obtaining third location information, the first network element can send a message to the ninth network element. This message carries the communication identifier of the first type of device in the first area. This message can trigger the ninth network element to obtain the third location information corresponding to the communication identifier and feed back the third location information to the first network element.

[0203] For example, the ninth network element can be a UPF, SMF, USS, UAS NF, or AF network element.

[0204] This application embodiment does not limit the messages sent by the first network element to the ninth network element. For example, the first network element may send a request message to the ninth network element, requesting feedback on the third location information corresponding to the communication identifier. As another example, the first network element may send a subscription message to the ninth network element, subscribing to the third location information corresponding to the communication identifier.

[0205] After acquiring the third location information, the first network element can, based on the premise that the similarity between the first and second location information reaches a preset threshold, further determine whether the similarity between the third and first location information reaches a preset threshold. If the similarity between the third and first location information reaches the preset threshold, the first network element can consider the communication identifier and the sensing identifier to be associated. If the similarity between the third and first location information does not reach the preset threshold, the first network element can consider the communication identifier and the sensing identifier to be unassociated.

[0206] Alternatively, the first network element may determine whether the communication identifier and the perception identifier are associated solely based on whether the similarity between the third location information and the first location information reaches a preset threshold.

[0207] Alternatively, the first network element can first determine the similarity between the first location information and the third location information. If the similarity between the first location information and the third location information reaches a preset threshold, it can further determine the similarity between the first location information and the second location information. Based on whether the similarity between the first location information and the second location information reaches a preset threshold, it can determine whether the communication identifier and the sensing identifier are associated.

[0208] Alternatively, the first network element can simultaneously determine the similarity of the first location information, the second location information, and the third location information (i.e., the first location information, the second location information, and the third location information are all input information for determining similarity), and based on the similarity, determine whether the communication identifier and the perception identifier are associated.

[0209] Optionally, the first information acquired by the first network element may contain sensing identifiers without associated communication identifiers. Similarly, the second information acquired by the first network element may contain communication identifiers without associated sensing identifiers.

[0210] Optionally, after S302, the first network element can send the target device information to the seventh network element. Here, the target device refers to a first-class device with associated communication identifier and perception identifier. For example, assuming the first-class device is a drone, with communication identifier: UE ID1, associated with perception identifier: perception target ID1, then the drone corresponding to UE ID1 and perception target ID1 can be called the target drone.

[0211] The information of the target device may include at least one of the following: communication identifier, sensing identifier, first location information, and second location information.

[0212] This application does not limit the message carrying the target device's information in its embodiments. For example, the target device's information may be carried in an analytics subscription notification message (e.g., Nnwdaf_AnalyticsSubscription_Notify) or an analytics response message (e.g., Nnwdaf_AnalyticsInfo_Response).

[0213] Optionally, if the seventh network element sends the fourth information to the first network element before S301, the first network element can also send the address information of the eighth network element, such as the IP address of the eighth network element, to the seventh network element. The fourth information and the target device information can be carried in the same message, or they can be sent separately.

[0214] Optionally, the seventh network element can schedule the target device based on the target device's information. For example, the seventh network element can determine auxiliary information based on the target device's information and send the auxiliary information to the target device. The auxiliary information can assist the target device in performing corresponding actions; for example, the target device can adjust its trajectory / flight path based on the auxiliary information.

[0215] For example, assuming the first network element is an NWDAF network element and the first type of device is a drone, Figure 5 is a possible flowchart illustrating the process by which the first network element acquires first information and second information. As shown in Figure 5, this process includes the following steps:

[0216] S501 and USS / AF send an analytics subscription message (Nnwdaf_AnalyticsSubscription_Subscribe) or an analytics information request message (Nnwdaf_AnalyticsInfo_Request) to the NWDAF network element. This message includes the following information: a new analytics ID and information about the first area. The new analytics ID is used to instruct the NWDAF network element to determine / associate the perception and communication identities of the UAVs in the first area.

[0217] Optionally, the message may also include a fourth piece of information, which is used to indicate the NWDAF network element and provide feedback on the IP address of the SPF network element.

[0218] For details on S501, please refer to the above description of the seventh network element sending third information to the first network element.

[0219] After receiving the analysis subscription message or analysis information request message, the S502 and NWDAF network elements select the SF network element based on the information of the first region carried in the message.

[0220] Optionally, if the process also includes S503, in S502, the NWDAF network element can also select the AMF network element based on the information of the first area.

[0221] S503 (Optional Step): The NWDAF network element sends an event open subscription / notification message (Namf_EventExposure_Subscribe / Notify) to the AMF network element, which carries information about the first region to request the identification information of terminal devices within the first region. After receiving this message, the AMF network element can send a list of UE IDs within the first region to the NWDAF network element.

[0222] For details on S503, please refer to the above description of S301, where the first network element sends a message to the fifth network element, triggering the fifth network element to send back the communication identifier of the terminal device in the first area to the first network element.

[0223] S504, the NWDAF network element sends a first message to the SF network element. The first message requests information about the sensed target within a first area. The first message includes information about the first area and information indicating the type of the sensed target (e.g., UAV type). Optionally, the first message may also include information instructing the NWDAF network element to request the trajectory / location information of the sensed target and information indicating the number of sensed targets.

[0224] After receiving the first message, the S505 and SF network elements acquire the sensing data corresponding to the sensing target ID within the first area. The SF network element processes the sensing data to determine the location information corresponding to the sensing target type (UAV) indicated by the first message.

[0225] The S506 and SF network elements send the UAV's perceived target ID and the corresponding location information to the NWDAF network element.

[0226] For details on S504-S506, please refer to the above description of how the first network element obtains the first information in S301.

[0227] The S507 and NWDAF network elements send a second message to the UAS NF network element. The second message is used to request the UUAA context within the first area. The second message may carry information about the first area.

[0228] The S508 and UAS NF network elements send the UUAA context within the first area to the NWDAF network element. The UUAA context includes the communication identifier of the UAV within the first area (e.g., UE ID such as GPSI, SUPI, etc.). Optionally, the UUAA context may also include the third-party identifier of the UAV within the first area and the correspondence between the third-party identifier and the communication identifier of the UAV.

[0229] For details on S507-S508, please refer to the above description of S301, where the first network element sends a second message to the third network element, and the second message triggers the third network element to feed back the communication identifier of the first type of device in the first area.

[0230] S509 (Optional Step): The NWDAF network element sends a request message to the UPF / SMF network element. This request message requests the UPF / SMF network element to distinguish between drones and human-computer terminals. This request message may carry information about the first area, as well as information used to distinguish between drones and human-computer terminals. After the UPF / SMF network element distinguishes between drones and human-computer terminals in the first area, it sends the filtered list of drone identifiers (UE ID list) to the NWDAF network element.

[0231] For details on S509, please refer to the above description of S301, where the first network element sends a message to the fourth network element, triggering the fourth network element to send back the communication identifier of the first type of device in the first area to the first network element.

[0232] In S510, the NWDAF network element determines the communication identifier (UE ID list) of the UAV within the first area. Specifically, the NWDAF network element can determine the UE ID list of the UAV within the first area based on the UUAA context received in S508. If this process also includes S503 and / or S509, the NWDAF network element can further determine the UE ID list of the UAV within the first area based on the UE ID list received in S503, and / or, the UE ID list received in S509.

[0233] For details on S510, please refer to the above description of the communication identifier included in the second information determined by the first network element in S301.

[0234] In S511, the NWDAF network element sends a location request message (Ngmlc_LocationProvideLocation / Notify) to the GMLC network element. This request message includes the communication identifiers (UE ID list) of the UAVs in the first area, as determined in S510.

[0235] S512 and GMLC locate the UAV corresponding to the UE ID based on the UE ID list, obtain the location information corresponding to the UE ID, and send the location information corresponding to the UE ID to NWDAF.

[0236] For details on S511-S512, please refer to the above introduction on how the first network element obtains the second information in S301.

[0237] S513 and NWDAF network elements associate the sensing identity (sensing target ID) with the communication identity (UE ID) based on the location information corresponding to the sensing target ID obtained in S506 and the location information corresponding to the UE ID obtained in S512. Specifically, the NWDAF network element can associate the sensing target ID with the UE ID based on the similarity between the location information.

[0238] Optionally, the NWDAF network element can further combine the satellite positioning information corresponding to the UE ID to associate the target ID with the UE ID.

[0239] S514. The NWDAF network element sends an analysis subscription notification message or analysis response message (Nnwdaf_AnalyticsSubscription_Notify / Nnwdaf_AnalyticsInfo_Response) to the USS / AF. This message can carry the following information: the sensing target ID, the UE ID associated with the sensing target ID, the location information corresponding to the sensing target ID, and the location information corresponding to the UE ID.

[0240] Optionally, if the message sent by the USS / AF in S501 also includes a fourth piece of information, the NWDAF network element can also send the IP address of the SPF network element to the USS / AF network element in S514.

[0241] Optionally, the method embodiment shown in Figure 3 can be applied to the detection and avoid (DAA) process.

[0242] In the DAA (Direct Access Assist) process, the association between the communication identifier and the sensing identifier of the first type of device established by the first network element can be used to determine DAA information. DAA information can be used to assist the first type of device. For example, DAA information can help the first type of device adjust its trajectory / flight path.

[0243] Optionally, in the DAA process, if the seventh network element sends the fourth information to the first network element before S301, then after S302, when the seventh network element receives the address information of the eighth network element, the seventh network element can initiate the AF influence on traffic routing and service function chaining process based on the address of the eighth network element to insert an uplink classifier (ULCL). For example, the ULCL can be configured on the anchor UPF, or the ULCL can be deployed independently (an independently deployed ULCL can also be called an intermediate UPF (I-UPF) network element). The ULCL network element can divert data reported by the first type of device (e.g., at least one of the following: communication data, radar data, RTK data, GNSS or satellite positioning data) to the eighth network element. Optionally, when inserting a ULCL, the path AF-PCF-SMF-UPF can be dynamically configured.

[0244] In this application, the method of ULCL offloading of radar and RTK data is not limited. ULCL can be a Layer 5 offloading method, that is, offloading data through IP 5-tuples, or a Layer 7 offloading method, for example, filtering based on service content to offload data.

[0245] For example, assuming the first network element is an NWDAF network element and the first type of device is a drone, Figure 6 is a possible flowchart illustrating the process by which the first network element obtains first and second information in the DAA process. As shown in Figure 6, the process includes the following steps:

[0246] S601. The UAV establishes a Protocol Data Unit (PDU) session for communication with the USS. During the session establishment process, the UUAA procedure can be triggered to complete the UAV authentication and authorization.

[0247] S602. Triggering the DAA process can be triggered by a drone. The drone sends a DAA service request to the USS via a PDU session. The request can carry a third-party identifier of the drone, such as a CAA-level UAV ID.

[0248] S603, USS receives DAA service requests. Based on the DAA service requests, USS determines that it needs to obtain the UAV's perception identity and communication identity.

[0249] S604, USS sends an analytics subscription message (Nnwdaf_AnalyticsSubscription_Subscribe) or an analytics information request message (Nnwdaf_AnalyticsInfo_Request) to the NWDAF network element. This message includes the following information: a new analytics ID and information about the first region. The new analytics ID is used to instruct the NWDAF network element to associate the perception and communication identities of the UAVs in the first region.

[0250] Optionally, the message may also include a fourth piece of information, which is used to indicate the NWDAF network element and provide feedback on the IP address of the SPF network element.

[0251] S605 and NWDAF acquire the first and second information, establish the association between the UAV's communication identity and perception identity, and send an analysis subscription notification message or analysis response message (Nnwdaf_AnalyticsSubscription_Notify / Nnwdaf_AnalyticsInfo_Response) to the USS. This message can carry the following information: perception target ID, UE ID associated with perception target ID, location information corresponding to perception target ID, and location information corresponding to UE ID.

[0252] Optionally, the NWDAF network element can also send the IP address of the SPF network element to the USS.

[0253] For details on S605, please refer to the above descriptions of S301-S302 or S502-S514.

[0254] S606 (Optional Step): If in S605, the NWDAF network element also sent the IP address of the SPF network element to the USS, the USS can initiate the AF influence on traffic routing and service function chaining procedure to insert the ULCL network element.

[0255] S607 (optional step): The UAV reports communication data, such as radar data, video data, and GNSS / RTK data. The ULCL network element distributes the communication data reported by the UAV to the SPF network element.

[0256] Based on the acquired target ID, the associated UE ID, the location information corresponding to the target ID, and the location information corresponding to the UE ID, the S608 and USS network elements obtain the airspace status and determine the DAA information. For example, the USS can adjust the trajectory / flight path of a relevant UAV according to the airspace status, and the DAA information can indicate the adjusted trajectory / flight path information.

[0257] The S609 and USS network elements send DAA (Direct Adaptive Action) information to the relevant drones. The drones can then perform corresponding actions based on the DAA information.

[0258] It is understood that the flowcharts shown in the embodiments of this application, such as the flowchart shown in Figure 5, are only logically illustrative flowcharts provided for the purpose of understanding the embodiments of this application, and do not represent the actual timing of the embodiments of this application. The embodiments of this application do not limit the timing between different steps in the flowchart. For example, in Figure 5, the timing between S503, S504, S507, and S509 is not necessarily the sequential timing shown in Figure 5.

[0259] The above-described method embodiments can be applied independently or in combination.

[0260] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various network elements. Accordingly, the embodiments of this application also provide a communication device for implementing the various methods described above. The communication device can be various network elements (such as the first network element, the second network element, the third network element, etc.) in the above method embodiments, or a device containing the various network elements, or a component that can be used for the various network elements.

[0261] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in 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 and design constraints of the technical solution. Those skilled in the art can 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.

[0262] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0263] Figure 7 shows a schematic diagram of a communication device 700. The communication device 700 includes a transceiver module 701 and a processing module 702. The transceiver module 701, also called a transceiver unit 701, is used to implement receiving and / or transmitting functions. The processing module 702, also called a processing unit 702, is used to implement processing functions.

[0264] Optionally, the communication device 700 may also include a storage module 703.

[0265] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0266] Alternatively, in the communication device shown in Figure 7, the names of the modules may not be the same as those shown in the figure. For example, the transceiver module may also be called a communication module or a communication unit.

[0267] If the units in Figure 7 are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. Storage media for storing computer software products include: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0268] In this embodiment, the communication device 700 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above-mentioned functions.

[0269] In a simple embodiment, those skilled in the art will realize that the communication device 700 can take the form of the communication device 800 shown in FIG8.

[0270] As shown in Figure 8, the communication device 800 includes one or more processors 801, a communication line 802, and at least one communication interface (Figure 8 is only an example illustrating the inclusion of a communication interface 804 and a processor 801), and optionally may also include a memory 803.

[0271] The processor 801 may be a general-purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of the program of the present application.

[0272] Communication line 802 may include a path for connecting different components.

[0273] The communication interface 804 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, RAN, terminals, and wireless local area networks (WLAN). For example, the transceiver module can be a transceiver or similar device. Optionally, the communication interface 804 can also be a transceiver circuit or input / output interface located within the processor 801, used to implement signal input and signal output for the processor.

[0274] The memory 803 can be a device with storage functionality. For example, it can be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions; random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory can exist independently and be connected to the processor via communication line 802. The memory can also be integrated with the processor.

[0275] The memory 803 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 801. The processor 801 executes the computer execution instructions stored in the memory 803, thereby implementing the communication method provided in the embodiments of this application.

[0276] Alternatively, in this embodiment, the processor 801 may execute the processing-related functions in the communication method provided in the above embodiments of this application, and the communication interface 804 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0277] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0278] In a specific implementation, as one example, processor 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG8.

[0279] In a specific implementation, as one embodiment, the communication device 800 may include multiple processors, such as processor 801 and processor 807 in FIG. 8. Each of these processors may be a single-core processor or a multi-core processor. The processors here may include, but are not limited to, at least one of the following: CPU, microprocessor, digital signal processing (DSP) processor, microcontroller unit (MCU), or artificial intelligence processor, etc., various computing devices that run software, and each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0280] In a specific implementation, as one embodiment, the communication device 800 may further include an output device 805 and an input device 806. The output device 805 communicates with the processor 801 and can display information in various ways. For example, the output device 805 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 806 communicates with the processor 801 and can receive user input in various ways. For example, the input device 806 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0281] The aforementioned communication device 800 may sometimes be referred to as a communication equipment, which can be a general-purpose device or a special-purpose device. For example, the communication device 800 may be the first access network device, second access network device, third access network device, fourth access network device mentioned above, or a device with a similar structure to that in Figure 8. The embodiments of this application do not limit the type of communication device 800.

[0282] Furthermore, the composition shown in FIG8 does not constitute a limitation on the communication device. In addition to the components shown in FIG8, the communication device 800 may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0283] Optionally, the functions / implementation processes of the transceiver module 701 and processing module 702 in FIG. 7 can be implemented by the processor 801 in the communication device 800 shown in FIG. 8 calling computer execution instructions stored in the memory 803. Alternatively, the functions / implementation processes of the processing module 702 in FIG. 7 can be implemented by the processor 801 in the communication device 800 shown in FIG. 8 calling computer execution instructions stored in the memory 803, and the functions / implementation processes of the transceiver module 701 in FIG. 7 can be implemented by the communication interface 804 in the communication device 800 shown in FIG. 8.

[0284] It should be understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes the software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as FPGAs, programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0285] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, DSP chip, MCU, artificial intelligence processor, ASIC, SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0286] Optionally, embodiments of this application also provide a communication device (e.g., the communication device may be a chip or a chip system), which includes a processor for implementing the methods in any of the above method embodiments. In one possible design, the communication device further includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the methods in any of the above method embodiments. Of course, the memory may not be included in the communication device. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0287] For example, Figure 9 shows a schematic diagram of a chip system. As shown in Figure 9, the chip system includes a processor module, a storage module, a power supply module, and an RF / antenna module.

[0288] The processor module is used for various calculations. The CPU is responsible for executing various instructions, including those for applications, operating systems, and other software. The graphics processing unit (GPU) is mainly responsible for graphics processing, but the CPU can also handle some graphics tasks, such as rendering application interfaces. The modem is used to modulate or demodulate signals so that digital signals can be transmitted in space.

[0289] In the storage module, RAM is temporary storage space used to temporarily store data that is currently in use. For example, if the chip system is located in the phone, RAM can store open web pages, messages from chat applications, game status, etc. ROM is read-only storage space. For example, if the chip system is located in the phone, ROM can store system files, pre-installed applications, and firmware.

[0290] The power module is used to provide voltage and current to other modules to maintain the normal operation of the chip.

[0291] Radio frequency / antenna modules are used to amplify signals and radiate them into space, or to receive wireless signals in space.

[0292] Optionally, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0293] Optionally, embodiments of this application also provide a computer program product storing a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0294] Optionally, embodiments of this application also provide a communication system, which includes the first network element described in the above method embodiments and at least one other network element, such as a second network element, a seventh network element, etc.

[0295] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is 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. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0296] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0297] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

A communication method, characterized in that, The method includes: The first network element acquires first information and second information; wherein, the first information includes a sensing identifier of a first type of device in a first area and first location information corresponding to the sensing identifier, and the second information includes a communication identifier of the first type of device in the first area and at least one of the following: second location information or third location information corresponding to the communication identifier; The first network element associates the sensing identifier and communication identifier of the first type of device with the first location information and at least one of the following: the second location information or the third location information. The method according to claim 1, characterized in that, The method further includes: The first network element sends a first message to the second network element. The first message is used to request information about the first type of device in the first area. The information about the first type of device includes the sensing identifier of the first type of device and the location information of the first type of device. The first network element obtains the second information, including: The first network element receives the second information from the second network element. The method according to claim 2, characterized in that, The method further includes: The first network element receives from the second network element the number of the first type of devices in the first area, and / or the type of the first type of devices. The method according to any one of claims 1-3, characterized in that, The method further includes: The first network element sends a second message to the third network element, the second message being used to request the communication identifier of the first type of device in the first area; The first network element receives at least one communication identifier from the third network element, and the at least one communication identifier is used by the first network element to obtain the second information. The method according to claim 4, characterized in that, The second message is used to request the context of the first type of device within the first area; The first network element receives at least one communication identifier from the third network element, including: The first network element receives context from at least one first type of device from the third network element. The context of the first type of device includes the communication identifier of the first type of device and at least one of the following: the third-party identifier of the first type of device or the correspondence between the third-party identifier and the communication identifier of the first type of device. The method according to claim 4 or 5, characterized in that, The method further includes: The first network element sends a third message to the fourth network element, the third message being used to request the communication identifier of the terminal device in the first area; The first network element receives at least one communication identifier from the fourth network element; The first network element determines the first type of device in the first area based on at least one communication identifier from the third network element and at least one communication identifier from the fourth network element. The method according to any one of claims 1-6, characterized in that, The method further includes: The first network element receives a fourth message from the fifth network element, the fourth message being used to request the association between the sensing identifier and the communication identifier of the first type of device within the first area; The first network element sends to the fifth network element at least one of the following information for at least one of the first type of devices within the first area: the sensing identifier, the communication identifier, the first location information, or the second location information. The method according to any one of claims 1-7, characterized in that, The third location information is obtained based on satellite positioning. A communication device, characterized in that, The communication device includes modules or units for implementing the method of any one of claims 1-8. A chip characterized in that, The chip includes a processor for running a computer program that causes a device including the chip to perform the method as described in any one of claims 1-8. A communication device, characterized in that, The communication device includes: a processor and an interface circuit, the interface circuit being used to communicate with a device other than the communication device, and the processor being used to execute instructions stored in the memory; when the instructions are executed by the processor, the communication device is caused to perform the method of any one of claims 1-8. The apparatus according to claim 11 is characterized in that, The communication device is a chip or chip system. A computer-readable storage medium, characterized in that, It stores instructions that, when executed by a computer, cause the method of any one of claims 1-8 to be performed. A computer program product, characterized in that, The computer program product includes instructions that, when executed by a computer, cause the method of any one of claims 1-8 to be performed.

Images