Sensing method and sensing device
By introducing the interactive mechanism of the first management node and the second management node in the perception system, the perception time and goals are managed, and the shortcomings of perception task management in the prior art are solved, and efficient and accurate perception task execution is achieved.
Patent Information
- Application Number
- PCT/CN2024/133589
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-11-30
- Filing Date
- 2024-11-21
- Publication Date
- 2025-06-05
AI Technical Summary
The prior art lacks relevant solutions for managing perceived goals and perceived time, making it difficult to effectively manage perceived tasks.
A perceived method and device are provided to manage perceived time and perceived targets through interactions between the first management node and the second management node. The specific steps include the first management node receiving a perception request from the second management node, including perception time information or identification of a perception target, and sending a perception report to the second management node.
It realizes effective management of perceived time and perceived goals, supports appointment-based perception and tracking perception, and improves the efficiency and accuracy of perceived tasks.
Smart Images

Figure CN2024133589_05062025_PF_FP_ABST
Abstract
Description
Sensing method and sensing device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 30, 2023, with application number 202311637605.7 and application name “Perception Method and Perception Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The embodiments of the present application relate to the field of perception, and more specifically, to a perception method and a perception device. Background Art
[0003] The 3rd Generation Partnership Project (3GPP) has proposed the functions and requirements for sensing communication services. The purpose of wireless sensing technology is to obtain characteristic information about remote objects or environments without physical contact with them. Wireless sensing refers to the ability to use radio frequency signals to obtain information about the characteristics of the environment and / or objects in it (such as shape, size, direction, speed, position, distance, or relative motion between objects). Sensing data is derived from wireless signals affected by target objects or environmental influences (such as reflection, refraction, and diffraction). Wireless sensing can be applied to applications such as intruder / interrupter detection (on roads, railways, drone-restricted areas, yards, and homes), monitoring applications (for rainfall, tourism, flooding, breathing, and movement), navigation assistance applications, real-time map generation applications, and collision avoidance applications. For example, a drone-restricted area monitoring application can use a sensing base station with wireless sensing characteristics to enable sensing within the restricted area. By analyzing sensing data such as reflection, refraction, and diffraction of radio frequency signals, it can detect whether a drone has intruded.
[0004] Currently, there is no relevant solution to manage perception targets and perception time, so how to manage perception targets and perception time is an urgent problem to be solved. Summary of the Invention
[0005] The embodiments of the present application provide a perception method and a perception device, which can manage perception time and / or perception targets.
[0006] To achieve the above objectives, this application adopts the following technical solutions:
[0007] In a first aspect, a perception method is provided. The method can be executed by a first management node, or by a component of the first management node, such as a processor, chip, or chip system of the first management node. It can also be implemented by a logic module or software that can implement all or part of the functions of the first management node. Taking the method as an example of being executed by the first management node, the method includes: the first management node receiving a perception request from a second management node, the perception request including at least one of the following: perception time information, or an identifier of a perception target; wherein the perception time information includes at least one of the following: a start time and an end time for perceiving a first service, or a perception period for the first service; and the first management node sending a perception report to the second management node.
[0008] In the perception method provided in the embodiment of the present application, the second management node carries at least one of the perception time information and the identification of the perception target in the perception request, so that the first management node manages the perception time (for example, the time for perceiving the first service can be reserved), or the first management node manages the perception target corresponding to the identification of the perception target (for example, the perception target corresponding to the identification of the perception target can be tracked and perceived), and then sends a perception report to the second management node.
[0009] In an embodiment of the present application, the perception report includes at least one of the following: the type of the perception target, the location of the perception target, the trajectory of the perception target, the speed of the perception target, the moving direction of the perception target, or the identification of the perception target. In this solution, the perception report includes the type of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to determine the type of the target perceived by the access network device; the perception report includes at least one of the location of the perception target, the trajectory of the perception target, the speed of the perception target, and the moving direction of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to determine the moving state of the target perceived by the access network device; the perception report includes the identification of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to use the identification of the perception target to identify the unique target in the entire domain or area, and further, to achieve tracking of the perception target.
[0010] In an embodiment of the present application, the first management node sends a perception report to the second management node, including: the first management node sends the perception report to the second management node in response to the perception request. This solution enables the first management node to send the perception report to the second management node based on the perception request.
[0011] In an embodiment of the present application, the method further includes: the first management node sending first information to the second management node, where the first information is used to represent the sensing capability information of the first management node. This solution can enable the first management node to register the sensing capability information of the first management node with the second management node, so that the second management node learns the sensing capability of the first management node, and further enable the second management node to send a sensing request within the sensing capability to the second management node.
[0012] The perception capability information may include at least one of the following: perception coverage level, perception positioning accuracy, or perception management range.
[0013] In a second aspect, a perception method is provided. The method can be executed by a second management node, or by a component of the second management node, such as a processor, chip, or chip system of the second management node. It can also be implemented by a logic module or software that can implement all or part of the functions of the second management node. Taking the method as an example where the method can be executed by the second management node, the method includes: the second management node sending a perception request to the first management node, the perception request including at least one of the following: perception time information, or an identifier of a perception target; wherein the perception time information includes at least one of the following: a start time and an end time for perceiving a first service, or a perception period for the first service; and the second management node receiving a perception report from the first management node.
[0014] In the perception method provided in an embodiment of the present application, the second management node carries at least one of the perception time information and the identification of the perception target in the perception request, so that the first management node manages the perception time, or manages the perception target corresponding to the identification of the perception target (for example, tracks the perception target corresponding to the identification of the perception target), and then sends a perception report to the second management node.
[0015] In an embodiment of the present application, the perception report includes at least one of the following: the type of the perception target, the location of the perception target, the trajectory of the perception target, the speed of the perception target, the moving direction of the perception target, or the identification of the perception target. In this solution, the perception report includes the type of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to determine the type of the target perceived by the access network device; the perception report includes at least one of the location of the perception target, the trajectory of the perception target, the speed of the perception target, and the moving direction of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to determine the moving state of the target perceived by the access network device; the perception report includes the identification of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to use the identification of the perception target to identify the unique target in the entire domain or area, and further, to achieve tracking of the perception target.
[0016] In an embodiment of the present application, the method further includes: the second management node receiving first information from the first management node, where the first information is used to represent the sensing capability information of the first management node. The method can cause the first management node to register the sensing capability information of the first management node with the second management node, so that the second management node learns the sensing capability of the first management node, and further cause the second management node to send a sensing request within the sensing capability to the second management node.
[0017] The perception capability information includes at least one of the following: perception coverage level, perception positioning accuracy, or perception management range.
[0018] In a third aspect, a perception method is provided, which includes: a first management node executes the method described in the first aspect, and a second management node executes the method described in the second aspect.
[0019] In a fourth aspect, a communication device is provided for implementing the various methods described above. The communication device may be the first management node described in the first aspect, or a device included in the first management node, such as a chip; or the communication device may be the second management node described in the second aspect, or a device included in the second management node, such as a chip.
[0020] The communication device includes modules, units, or means corresponding to the above-mentioned method, which can be implemented by hardware, software, or hardware executing corresponding software implementation. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions.
[0021] In some possible designs, the communication device may include a processing module and a communication module. The communication module may include an output module (or a sending module) and an input module (or a receiving module), respectively configured to implement the output (or sending) and input (or receiving) functions of any of the above aspects and any possible designs thereof. The processing module may be configured to implement the processing functions of any of the above aspects and any possible designs thereof.
[0022] Optionally, the communication device further includes a storage module for storing program instructions and data.
[0023] In a fifth aspect, a communication device is provided, comprising: at least one processor configured to execute a computer program or instruction, or to cause the communication device to execute the method described in any of the above aspects through logic circuitry. The communication device may be the first management node described in the first aspect, or a device included in the first management node, such as a chip; or the communication device may be the second management node described in the second aspect, or a device included in the second management node, such as a chip.
[0024] In some possible designs, the communication device further includes a memory for storing computer instructions and / or configuration files of logic circuits. Optionally, the memory is integrated with the processor, or the memory is independent of the processor.
[0025] In one possible design, the communication device further includes a communication interface for inputting and / or outputting signals.
[0026] In some possible designs, the communication interface is an interface circuit for reading and writing computer instructions. For example, the interface circuit is used to receive computer execution instructions (computer execution instructions are stored in a memory, may be read directly from the memory, or may pass through other devices) and transmit them to the processor.
[0027] In some possible designs, the communication interface is used to communicate with modules outside the communication device.
[0028] In some possible designs, the communication device may be a chip system. When the communication device is a chip system, the chip system may include a chip or may include a chip and other discrete devices.
[0029] In a sixth aspect, a communication device is provided, comprising: a logic circuit and an interface circuit; the interface circuit is configured to input and / or output information; and the logic circuit is configured to execute the method described in any of the above aspects, processing the input information and / or generating output information. The communication device may be the first management node described in the first aspect, or a device included in the first management node, such as a chip; or the communication device may be the second management node described in the second aspect, or a device included in the second management node, such as a chip.
[0030] In a seventh aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the method described in any one of the above aspects is executed.
[0031] In an eighth aspect, a computer program product is provided, which, when executed by a processor, enables the method described in any one of the above aspects to be executed.
[0032] It can be understood that when the communication device provided in any one of the fourth to sixth aspects is a chip, the above-mentioned sending action / function can be understood as output information, and the above-mentioned receiving action / function can be understood as input information.
[0033] Among them, the technical effects brought about by any design method in the fourth to sixth aspects can refer to the technical effects brought about by the different design methods in the above-mentioned first and second aspects, and will not be repeated here.
[0034] In a ninth aspect, a communication system is provided, which includes the first management node described in the first aspect and the second management node described in the second aspect.
[0035] Optionally, the communication system further includes an access network device, configured to send a perception report to the first management node. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] FIG1 is a schematic diagram of a 5G network architecture;
[0037] FIG2 is a schematic diagram of a service-oriented management architecture provided in an embodiment of the present application;
[0038] FIG3 is a schematic diagram of a system architecture according to an embodiment of the present application;
[0039] FIG4 is a schematic diagram of a system architecture in which the perception method provided in an embodiment of the present application is applied to a service-oriented management architecture;
[0040] FIG5 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0041] FIG6 is a schematic diagram of an example of a sensing method provided in an embodiment of the present application;
[0042] FIG7 is a schematic diagram of a perception method corresponding to scenario three provided in an embodiment of the present application;
[0043] FIG8 is a schematic diagram of another example of a sensing method provided in an embodiment of the present application;
[0044] FIG9 is a schematic diagram of another example of a sensing method provided in an embodiment of the present application;
[0045] FIG10 is a schematic diagram of a specific embodiment of the sensing method provided in an embodiment of the present application;
[0046] FIG11 is a schematic diagram of a specific embodiment of the sensing method provided in an embodiment of the present application;
[0047] FIG12 is a schematic diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0048] In the description of this application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
[0049] In the description of this application, unless otherwise specified, "plurality" means two or more than two. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and / or c can be represented by: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or plural.
[0050] In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.
[0051] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.
[0052] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, throughout the specification, the various embodiments do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
[0053] It is understood that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in certain scenarios as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.
[0054] In this application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In the various embodiments of this application, unless otherwise specified and there is no logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following description of the embodiments of this application does not constitute a limitation on the scope of protection of this application.
[0055] For ease of understanding, the relevant technologies of the embodiments of this application are briefly introduced.
[0056] 1. Fifth generation (5G) network architecture:
[0057] The 5G network architecture defined in the 3GPP standard is mainly divided into two parts: the access network (AN) and the core network. As shown in Figure 1, terminal devices access the core network through the access network.
[0058] The access network mainly includes radio access network (RAN) equipment, which is used to implement functions related to wireless access.
[0059] The core network mainly includes the following key logical network elements: access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, unified data management function (UDM) network element. In addition, it can also include authentication server function (AUSF) network element, network slice selection function (NSSF) network element, application function (AF) network element, etc. Please refer to the 5G standard for the network elements of related functions and will not be repeated here.
[0060] In addition, referring to FIG1 , Nx represents a logical interface or a service-oriented interface between two network elements, which is used for communication between the network elements. For example, N1 is the interface between the terminal device and the AMF network element; N2 is the interface between the access network device and the AMF network element; N3 is the interface between the access network device and the UPF network element; N9 is the interface between different UPF network elements; N6 is the interface between the UPF network element and the destination network (DN); N4 is the interface between the UPF network element and the SMF network element; N11 is the interface between the AMF network element and the SMF network element; N7 is the interface between the SMF network element and the PCF network element; N5 is the interface between the PCF network element and the AF network element; N14 is the interface between different AMF network elements; N15 is the interface between the AMF network element and the PCF network element; N22 is the interface between the NSSF network element and the AMF network element; N12 is the interface between the AUSF network element and the AMF network element; N8 is the interface between the UDM network element and the AMF network element; N13 is the interface between the AUSF network element and the UDM network element.
[0061] Optionally, the terminal device in the embodiment of the present application can be a user equipment (UE), access terminal, terminal unit, user station, terminal station, mobile station, mobile station, remote station, remote terminal, user terminal terminal equipment, TE), mobile device, wireless communication device, terminal agent, tablet computer (pad), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, vehicle-mounted communication module, wearable device, or terminal device in a 5G network or a public land mobile network (PLMN) evolved after 5G. The access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a drone, a robot, a smart point of sale (POS) machine, a customer-premises equipment (CPE) or a wearable device, virtual reality (VR) reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical (remote medical), wireless terminals in smart grid (smart grid), wireless terminals in transportation safety (transportation safety), wireless terminals in smart city (smart city), wireless terminals in smart home (smart home), etc. Alternatively, the terminal can be a terminal with communication function in the Internet of Things (IoT), such as a terminal in V2X (such as a vehicle networking device), a terminal in D2D communication, or a terminal in M2M communication, etc. The terminal can be mobile or fixed. In addition, the embodiment of the present application does not limit the device form of the terminal. The device for realizing the function of the terminal device can be a terminal device; it can also be a device that can support the terminal device to realize the function, such as a chip system. The device can be installed in the terminal device or used in combination with the terminal device. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.
[0062] 2. Service-oriented management architecture:
[0063] Figure 2 is a schematic diagram of a service-oriented management architecture. As shown in Figure 2, the service-oriented management architecture includes: a business support system (BSS), a cross domain management function (CD-MnF), a domain management function (Domain-MnF), and a domain management function, and / or, a network element managed by the cross domain management function. The domain management function, and / or, the network element managed by the cross domain management function includes a core network element or an access network device. The core network element includes, for example, an access and mobility management function network element, a session management function network element, or a policy control network element.
[0064] The management modes of the service-oriented management architecture include the following:
[0065] Management model 1: The cross-domain management functional unit provides management services and is the producer of management services; the business support system is the consumer of management services.
[0066] Management mode 2: The domain management functional unit provides management services and is the producer of management services; the cross-domain management functional unit is the consumer of management services.
[0067] Management mode three: The domain management functional unit, and / or the network elements managed by the cross-domain management functional unit, provide management services and are producers of management services; the domain management functional unit is a consumer of management services.
[0068] Business support systems, oriented towards communications services, provide functions and management services such as billing, settlement, accounting, customer service, sales operations, network monitoring, communications service lifecycle management, and business intent translation. These systems can be either the operator's operating system or a vertical industry's operating system.
[0069] The cross-domain management function unit, also called the network management function unit (NMF), can be a network management entity such as a network management system (NMS) or a network function management service consumer (NFMS_C). The cross-domain management function unit provides one or more of the following management functions or services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization, and translation of service producer network intents (Intent-CSPs).
[0070] Among them, the network referred to in the above management function or management service may include one or more network elements, or subnetworks, or network slices. That is, the network management function unit may be a network slice management function unit (NSMF), or a cross-domain management data analytical function unit (MDAF), or a cross-domain self-organization network function (SON Function), or a cross-domain intent driven management service (MnS).
[0071] Optionally, in certain deployment scenarios, the cross-domain management functional unit may also provide sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization functions, network intent of sub-network service producers, or translation of network intent of sub-network service consumers (intent from communication service consumer, Intent-CSC), etc. Wherein, the sub-network is composed of multiple small sub-networks and can be a network slice sub-network.
[0072] The domain management function unit, also called the sub-network management function unit (NMF) or the network element management function unit, can be, for example, a radio automation engine (MBB automation engine, MAE), an element management system (EMS), a network function management service provider (NFMS_P), or other network element management entities.
[0073] The domain management functional unit provides one or more of the following functions or management services: lifecycle management of sub-networks or network elements, deployment of sub-networks or network elements, fault management of sub-networks or network elements, performance management of sub-networks or network elements, assurance of sub-networks or network elements, optimization of sub-networks or network elements, and translation of intents from network operators (Intent-NOPs) for sub-networks or network elements. A sub-network here includes one or more network elements, and a sub-network may also include sub-networks, i.e., one or more sub-networks form a larger sub-network.
[0074] Optionally, the subnetwork here can also be a network slice subnetwork. The domain management function unit can be a network slice subnet management function unit (NSSMF), a domain management data analytical function unit (Domain MDAF), a domain self-organization network function (SON Function), a domain intent management function unit Intent Driven MnS, etc.
[0075] The domain management functional units can be classified as follows:
[0076] By network type, they can be divided into: radio access network domain management function (RAN-Domain-MnF), core network domain management function (CN-Domain-MnF), transport network domain management function (TN-Domain-MnF), etc. It should be noted that the domain management function unit can also be a domain network management system that can manage one or more of the access network, core network, or transport network. By administrative region, they can be divided into: domain management function units for a specific region, such as the domain management function unit of City A and the domain management function unit of City B.
[0077] The network elements managed by the domain management functional unit and / or the cross-domain management functional unit are entities that provide network services, including core network elements or access network devices. Specifically, the domain management functional unit and / or the cross-domain management functional unit may provide one or more of the following management functions or services: network element lifecycle management, network element deployment, network element fault management, network element performance management, network element assurance, network element optimization, and network element intent translation.
[0078] FIG3 is a schematic diagram of a system architecture of an embodiment of the present application. As shown in FIG3 , the system includes a first management node and a second management node. The first management node is configured to receive a perception request from the second management node and send a perception report to the second management node; the second management node is configured to send a perception request to the first management node and receive a perception report from the first management node. Optionally, the system architecture further includes an access network device configured to send a perception report corresponding to the first service, or perception data corresponding to the first service, wherein the perception report is determined by analyzing and calculating the perception data.
[0079] The technical solutions of the embodiments of the present application can be applied to the 5G communication system as shown in Figure 1, or the service-oriented management system as shown in Figure 2, or the technical solutions of the embodiments of the present application can also be applied to other communication systems, which is not limited by the embodiments of the present application.
[0080] In one possible implementation, the system architecture shown in FIG3 can be applied to the 5G communication system shown in FIG1 . The second management node can be a network exposure function (NEF) network element or a component of the NEF network element (e.g., a processor, chip, or chip system of the NEF, or a logical module or software of all or part of the functions of the NEF) used to connect the core network internal network element and the core network external application server in the 5G communication system (wherein the core network network element shown in FIG1 is a core network internal network element, and FIG1 does not show the NEF). The first management node can be a network element within the core network, or a component of a network element within the core network (e.g., a processor, chip, or chip system of a network element within the core network), or a logical module or software of all or part of the functions of the network element within the core network. The access network device is configured to send sensing data corresponding to the first service to the first management node, i.e., the network element within the core network. Optionally, although not shown, the first management node can be a sensing function (SF) node deployed within the core network, such as an SF network element. Of course, the SF node can also be deployed on the existing network elements of the 5G communication system, and the embodiments of the present application do not make specific limitations on this.
[0081] In another possible implementation, the system architecture shown in FIG3 can be applied to the service-oriented management architecture shown in FIG2 , wherein the first management node can be a domain management functional unit, or can be a processor, chip, or chip system in the domain management functional unit, or can be a logic module or software of all or part of the functions of the domain management functional unit, and the second management node can be a cross-domain management functional unit, or can be a processor, chip, or chip system in the cross-domain management functional unit, or can be a logic module or software of all or part of the functions of the cross-domain management functional unit. Among them, the access network device is used to perceive the first service to obtain perception data, analyze and calculate the perception data to determine the perception report and send the perception report to the first management node. Among them, the domain management functional unit is deployed with an SF node, or the domain management functional unit manages the SF node.
[0082] For example, FIG4 is a schematic diagram of a system architecture in which the perception method provided in an embodiment of the present application is applied to the service-oriented management architecture shown in FIG2 . As shown in FIG4 , the system architecture includes a domain management functional unit and a cross-domain management functional unit. The domain management functional unit is configured to receive a perception request from the cross-domain management functional unit and send a perception report to the cross-domain management functional unit. The cross-domain management functional unit is configured to send a perception request to the domain management functional unit and receive a perception report from the domain management functional unit. The domain management functional unit includes an SF node, or manages an SF node.
[0083] Optionally, as shown in FIG4 , the cross-domain management function unit is further configured to receive a perception request from a first device and send a perception report to the first device, wherein the first device is a consumer of the perception function.
[0084] Optionally, as shown in FIG4 , the domain management function unit is further configured to send first information to the cross-domain management function unit, where the first information is used to represent the perception capability information of the domain management function unit.
[0085] Optionally, as shown in FIG4 , the domain management function unit is used to configure an access network device that executes the first service.
[0086] Optionally, as shown in FIG4 , the domain management function unit is configured to receive a perception report from an access network device.
[0087] For the above two possible applications, the access network equipment can also send a signal for sensing the first service, receive an echo signal of the signal for sensing the first service, generate sensing data, and detect whether there is a sensing target, etc.
[0088] In the embodiment of the present application, SF can be executed by an SF node, or by a processor, chip, or chip system of the SF node, or by all or part of the logic modules or software of the SF node, and the embodiment of the present application does not specifically limit this.
[0089] Optionally, in the embodiment of the present application, SF may include one or more of the following:
[0090] Manage transmission gateways and encrypt transmissions;
[0091] Air interface SF management, including: supporting the testing, verification, and evaluation of sensing coverage levels and sensing capabilities; supporting the upward registration of sensing coverage levels and sensing positioning accuracy; supporting the reporting of changes in sensing coverage levels and sensing positioning accuracy due to equipment failures, external interference changes, new obstructions, etc.
[0092] Perception authentication, including: verifying whether the perception coverage and perception positioning accuracy requirements exceed the allowable range;
[0093] Dynamic allocation of sensing resources, including: on-demand conversion of sensing area requirements corresponding to sensing requests into resource allocation strategies for access network devices (determining which time domain resources are used for sensing), ensuring that the resources used for sensing are minimized, and minimizing interference between neighboring areas and the impact of external interference;
[0094] Perception data reporting, including: supporting the merging and reporting of perception data from multiple access network devices.
[0095] Optionally, the access network device involved in the present application may be an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in a long term evolution (LTE) system or an enhanced LTE (LTE-advanced, LTE-A) system, such as a traditional macro base station eNB and a micro base station eNB in a heterogeneous network scenario. Alternatively, it may include a next generation node B (gNB) in a new radio (NR) system. Alternatively, it may include a transmission reception point (TRP), a home base station (for example, a home evolved NodeB, or a home Node B, HNB), a base band unit (BBU), a base band pool (BBU pool), or a wireless fidelity (WiFi) access point (AP), etc. Alternatively, it may include a base station in a non-terrestrial network (NTN), which can be deployed on an aircraft or satellite. In an NTN, the access network device can function as a Layer 1 (L1) relay, a base station, or an integrated access and backhaul (IAB) node. Alternatively, the access network device can be a device that implements base station functions in the IoT, such as drone communications, V2X, D2D, or machine-to-machine (M2M) devices.
[0096] In some possible scenarios, the access network device may also be a module or unit that can implement some of the functions of the base station. For example, the first network device may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be set separately, or may be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).
[0097] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, the access network device may be a network device or a module of a network device in an open radio access network (open RAN, ORAN) system. In the ORAN system, CU may also be referred to as open (open, O)-CU, DU may also be referred to as O-DU, CU-CP may also be referred to as O-CU-CP, CU-UP may also be referred to as O-CU-UP, and RU may also be referred to as O-RU. Any of the CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0098] Optionally, the base station in the embodiment of the present application may include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, access points, home base stations, TRPs, transmitting points (TPs), mobile switching centers, etc., and the embodiments of the present application do not make specific limitations on this.
[0099] The functions of the first management node and the second management node involved in this application can be implemented by the communication device 500 in Figure 5. Figure 5 is a schematic diagram of the structure of the communication device 500 provided in an embodiment of the present application. The communication device 500 includes one or more processors 501, a communication line 502, and at least one communication interface (Figure 5 is merely an example of including a communication interface 504 and a processor 501 for illustration), and optionally may also include a memory 503.
[0100] The processor 501 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.
[0101] The communication line 502 may include a path for connecting different components.
[0102] The communication interface 504 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, and wireless local area networks (WLAN). For example, the transceiver module can be a device such as a transceiver or a transceiver. Alternatively, the communication interface 504 can be a transceiver circuit located within the processor 501 to implement signal input and output to the processor.
[0103] The memory 503 may be a device having a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or 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 compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a communication line 502. The memory may also be integrated with the processor.
[0104] The memory 503 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 501. The processor 501 is used to execute the computer-executable instructions stored in the memory 503, thereby implementing the perception method provided in the embodiment of the present application.
[0105] Alternatively, optionally, in an embodiment of the present application, the processor 501 may also perform processing-related functions in the perception method provided in the following embodiments of the present application, and the communication interface 504 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiments of the present application.
[0106] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.
[0107] In a specific implementation, as an embodiment, the processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5 .
[0108] In a specific implementation, as an embodiment, the communication device 400 may include multiple processors, such as the processor 507 and the processor 501 in FIG5 . 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: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, and other types of computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.
[0109] In a specific implementation, as an embodiment, the communication device 500 may further include an output device 505 and an input device 506. The output device 505 communicates with the processor 501 and can display information in a variety of ways. For example, the output device 505 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 506 communicates with the processor 501 and can receive user input in a variety of ways. For example, the input device 506 can be a mouse, a keyboard, a touch screen device, or a sensor device.
[0110] The communication device 500 described above may also sometimes be referred to as a communication device, and may be a general-purpose device or a dedicated device. For example, the communication device 500 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device having a structure similar to that shown in FIG4 . The embodiments of the present application do not limit the type of the communication device 500.
[0111] In addition, the composition structure shown in FIG5 does not constitute a limitation on the communication device. In addition to the components shown in FIG5, the communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0112] The following describes the perception method provided in the embodiment of the present application in conjunction with the communication system shown in Figure 3.
[0113] It should be noted that in the following embodiments of the present application, the message names, parameter names, or information names between network elements are only examples. In other embodiments, they may also be other names. The communication method provided in this application does not make specific limitations on this.
[0114] It is understood that in the embodiments of the present application, each network element may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of various operations. In addition, the steps may be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.
[0115] Figure 6 is an example of a perception method provided by an embodiment of the present application. The method is illustrated by taking the interaction between the first management node and the second management node as an example. Of course, the subject that executes the action of the first management node in the method can also be a device / module in the first management node, such as a chip, processor, processing unit, etc. in the first management node; the subject that executes the action of the second management node in the method can also be a device / module in the second management node, such as a chip, processor, processing unit, etc. in the second management node, and the embodiment of the present application does not make specific limitations on this. The processing performed by a single execution subject (for example, the first management node or the second management node) in the embodiment of the present application can also be divided into executions by multiple execution subjects, and these execution subjects can be logically and / or physically separated. Exemplarily, as shown in Figure 6, method 600 includes:
[0116] S610: The second management node sends a sensing request to the first management node. Correspondingly, the first management node receives the sensing request from the second management node.
[0117] Optionally, in an embodiment of the present application, the first management node configures an access network device that perceives the first service based on the perception request, wherein the access network device that perceives the first service includes at least one access network device.
[0118] Exemplarily, the first service is used to configure access network equipment within a specific area to perform perception, or the first service is used to configure access network equipment to perform perception on a specific perception target, or the first service is other services, which is not limited in the embodiments of the present application.
[0119] In an embodiment of the present application, the perception request includes at least one of the following: perception time information, or an identifier of the perception target.
[0120] The perception time information includes at least one of the following: a start time and an end time for perceiving the first service, or a perception period for the first service. By including the perception time information in the perception request, the first management node can manage the perception period of the first service, or support scheduled perception of the first service.
[0121] Exemplarily, the time when the second management node sends the perception request to the first management node is 10:30, and the start time and end time for perceiving the first service included in the perception request are 11:30 and 11:45 respectively, then the access network device will perceive the first service from 11:30 to 11:45. In other words, the access network device starts perceiving the first service at 11:30 and ends perceiving the first service at 11:45. Alternatively, exemplarily, the perception request includes a perception period of 30 minutes for the first service, then the access network device performs perception of the first service every 30 minutes, for example, the access network device perceives the first service in the first 15 minutes of every 30 minutes.
[0122] Optionally, the identification of the perception target in the embodiment of the present application is the identification of one perception target; or, the identification of the perception target in the embodiment of the present application is the identification of each of multiple perception targets, that is, the identification of each perception target in the multiple perception targets, for example, the identification of multiple perception targets is a list of identifications of perception targets, or a set of identifications of perception targets, which is not limited in the embodiment of the present application.
[0123] Optionally, the identification of the perceived target is a unique identification registered with the perceived target. For example, if the perceived target is an unmanned aerial vehicle (UVA), the identification of the perceived target is the unique identification registered with the UVA. Optionally, if the perceived target is a pedestrian or an animal, the identification of the perceived target is used to identify the pedestrian or animal. Optionally, if the perceived target is another object, the identification of the perceived target is used to identify the other object.
[0124] Optionally, the identifier of the sensing target is a unique identifier of the sensing target allocated by the second management node.
[0125] Optionally, the identifier of the perception target is the identifier of the perception target assigned by the first management node, that is, the identifier of the perception target under the first management node. Optionally, the second management node determines the unique identifier of the perception target based on the identifier assigned by the first management node to the perception target. In one possible implementation, the second management node adds the identifier prefix of the first management node to the identifier assigned by the first management node to the perception target to determine the unique identifier of the perception target; in another possible implementation, the second management node maps the identifier assigned by the first management node to the perception target to the unique identifier of the perception target under the second management node.
[0126] Optionally, the identifier of the perception target is the identifier assigned by the access network device to the perception target, which is the identifier of the perception target under the access network device. Optionally, the first management node determines the identifier of the perception target under the first management node based on the identifier assigned by the access network device to the perception target. In one possible implementation, the first management node adds the identifier prefix of the access network device to the identifier assigned by the access network device to the perception target, and determines the identifier of the perception target at the first management node; in another possible implementation, the first management node maps the identifier assigned by the access network device to the perception target to the identifier of the perception target under the first management node. Further, optionally, the second management node determines the unique identifier of the perception target based on the identifier of the perception target determined by the first management node at the first management node. For details, please refer to the description in the above embodiment and will not be repeated here.
[0127] For example, the identification of the perception target in the access network device may be #1, the identification in the first management node may be &1 or, and the identification in the second management node may be *1 or *, which is not limited in the embodiment of the present application.
[0128] It should be noted that, in a possible implementation, the identifier of the perception target is allocated by the access network device to the perception target, and the first management node obtains the identifier of the perception target allocated by the access network device by obtaining a perception report.
[0129] Optionally, in an embodiment of the present application, the first management node configures an access network device for sensing the first service based on the perception request, wherein the access network device is at least one access network device.
[0130] S620: The first management node sends a perception report to the second management node. Correspondingly, the second management node receives the perception report from the first management node.
[0131] In an embodiment of the present application, the perception report includes at least one of the following: perception target type information, perception target location information, perception target trajectory information, perception target speed information, perception target moving direction information, and perception target identification. In an embodiment of the present application, the perception report includes the type of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to determine the type of the target perceived by the access network device; the perception report includes at least one of the position of the perception target, the trajectory of the perception target, the speed of the perception target, and the moving direction of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to determine the moving state of the target perceived by the access network device; the perception report includes the identification of the perception target, which can enable the receiver of the perception report (for example, the first management node, the second management node) to use the identification of the perception target to identify the unique target in the entire domain or area, and further, to achieve tracking of the perception target.
[0132] Exemplarily, the perception target type information is used to indicate the type of the perception target, and the type of the perception target may include, for example, pedestrians, animals, UAVs, etc.
[0133] Exemplarily, the perception target location information includes an identifier of the cell where the perception target is located, an identifier of the access network device corresponding to the perception target, an identifier of the tracking area corresponding to the perception target, and / or one or more of the geographical longitude, latitude, and altitude corresponding to the perception target.
[0134] Exemplarily, the perception target trajectory information includes the motion trajectory of the perception target. Exemplarily, the motion trajectory of the perception target includes the identifier of the cell where the perception target is located, the identifier of the access network device corresponding to the perception target, the tracking area identifier corresponding to the perception target, and / or one or more of the geographical longitude, latitude, and altitude corresponding to the perception target. For example, the perception target is a UAV, and the perception target trajectory is the flight path of the UAV; for another example, the perception target is a pedestrian or an animal, and the perception target trajectory is the movement path of the pedestrian or animal. Exemplarily, the perception target speed information includes one or more of the X-axis speed, Y-axis speed, and Z-axis speed corresponding to the perception target, wherein the X-axis, Y-axis, and Z-axis are three-dimensional coordinates in the geodetic coordinate system.
[0135] Exemplarily, the perceived target movement direction information includes the perceived target movement direction, and the perceived target movement direction may include the direction in which the perceived target moves east, south, west, or north. For example, the perceived target moves 30m south, or the perceived target moves 30m north, or the perceived target moves 30m northeast, etc. The embodiments of the present application do not limit this.
[0136] In one possible implementation, the first management node sending the perception report to the second management node includes: the first management node sending the perception report to the second management node in response to the perception request. In other words, after receiving the perception request, the first management node triggers the sending of the perception report to the second management node.
[0137] The following describes the sensing method provided in the embodiment of the present application in detail in three scenarios:
[0138] Scenario 1: Perception of a specific area.
[0139] In this scenario, exemplarily, the perception request in step S610 is perception request one, and perception request one includes perception time information. Exemplarily, perception request one is a regional perception request, that is, perception request one is used to request perception of a specific area (for example, the first area) within the perception time corresponding to the perception time information, and the first service is used to configure the access network equipment in the first area to perform perception at the perception time corresponding to the perception time information. It should be noted that the first management node configures at least one access network device for perceiving the first area according to perception request one, and the at least one access network device perceives the first area within the perception time corresponding to the perception time information. For example, the access network devices covering the first area (or the service scope of the access network device is the first area) are base stations 1 to base stations 10, then base stations 1 to base stations 10 perceive the first area within the perception time corresponding to the perception time information, and obtain perception data corresponding to the first area.
[0140] Correspondingly, perception request one also includes at least one of the following: first area information, first area type information, perception target type information, perception number information, or service level agreement (SLA) indicator information.
[0141] Exemplarily, the first area information is used to indicate the area information to be sensed, which may be a cell identifier list (such as a physical cell identifier (PCI), a cell identifier (ID), etc.), a base station identifier list (gNB ID), a tracking area identity list (TAI), and / or geographical latitude and longitude area information.
[0142] Exemplarily, the first area type information is used to indicate the type corresponding to the first area, and the area type may include, for example, ground, low altitude, water area, etc.
[0143] Exemplarily, the perception target type information is used to indicate the type of the perception target, and the perception target type may include, for example, pedestrians, animals, UAVs, etc.
[0144] Exemplarily, the perception number information is used to indicate the maximum or minimum number of targets to be perceived, including the number of perception targets perceived by performing one perception on the first area.
[0145] Exemplarily, the SLA indicator information is used to indicate that the perception report carries an SLA indicator obtained after perceiving the first area, or the SLA indicator information is used to indicate a threshold value of the SLA indicator for perceiving the first area. The SLA indicator includes one or more of the following: confidence level, positioning estimation accuracy, velocity estimation accuracy, perception resolution, maximum perception service latency, refresh rate, missed detection rate, and false detection rate. The following describes the parameters in the SLA indicator information.
[0146] The confidence level describes the degree of authenticity of the sensing data measured by the access network equipment used for sensing, expressed as a percentage. For example, the confidence level can be set to 95% in the sensing request, and the credibility of the sensing data is 95%.
[0147] Positioning estimation accuracy describes the degree of closeness between the position of the sensing target obtained by the access network device used for sensing by executing the sensing request and its actual position value.
[0148] The speed estimation accuracy describes how close the speed of the perceived target, obtained by the access network device through the sensing request, is to its actual speed. The speed estimation accuracy can be calculated based on the change in the perceived position of the object.
[0149] Perception resolution describes the minimum difference between the measured value and the true value of different types of perception targets that can be detected. For example, the perception resolution for detecting the presence of a drone can be 10 meters at range and 10 meters / second at speed. The perception resolution for tracking a flying drone can be 1 meter at range and 1 meter / second at speed.
[0150] The maximum perception service latency describes the maximum delay from the second management node sending a perception request to the first management node reporting a perception report. Alternatively, it describes the maximum delay from the first management node configuring an access network device for perception to the access network device reporting a perception report. This is not limited in the present embodiments.
[0151] The refresh rate describes the rate at which the access network device used for perception generates perception data. For example, if perception data is generated once every second, the resolution is the inverse of the time interval, that is, 0.1.
[0152] The missed detection rate describes the ratio of unperceived sensing targets or events to all sensing targets or events in any predetermined period during which the access network device used for sensing attempts to obtain sensing data.
[0153] The false detection rate describes the ratio of non-sensing targets or events to all sensing targets or events sensed during any predetermined period when the access network equipment used for sensing attempts to obtain sensing data.
[0154] Accordingly, in this scenario, the perception report in step S620 is, illustratively, perception report 1, which includes at least one of the following: perception target type information, perception target location information, perception target trajectory information, perception target speed information, and perception target movement direction information. For examples of perception target type information, perception target location information, perception target trajectory information, perception target speed information, and perception target movement direction information, refer to the description of the above embodiment and are not repeated here.
[0155] In scenario one, perception report one is obtained by perceiving the first area, that is, a perception report for regional perception. For example, if perception request one includes perception target type information, and the type of the perception target included in the perception target type information is UVA, then perception report one is a perception report corresponding to one or more UVAs perceived by the access network device for perceiving and discovering the first area. Optionally, the perception report includes an identifier of the perception target, which is used to determine one or more of the type information, location information, trajectory information, speed information, and movement direction information corresponding to the perception target perceived and discovered in the first area.
[0156] Scenario 2: Perceiving a specific perception target.
[0157] In this scenario, exemplarily, the perception request in step S610 is perception request 2, and perception request 2 includes the identifier of the perception target. Exemplarily, perception request 2 is a tracking perception request, that is, perception request 2 is used to request perception of the perception target corresponding to the identifier of the perception target. For example, if the perception target is moving, the perception target is tracked and perceived. It should be noted that the first management node configures at least one access network device to perceive the perception target corresponding to the identifier of the perception target according to perception request 2, and the at least one access network device perceives the perception target corresponding to the identifier of the perception target. For example, the first management node estimates the second area to the tenth area (i.e., the route of the perception target) to which the perception target may move based on the movement trajectory of the perception target. The access network devices covering the second area to the tenth area are base stations 6 to base stations 14, respectively. Base stations 6 to base stations 14 perceive the perception targets corresponding to the identifiers of the perception targets in turn, and obtain the perception data of each base station perceiving the perception targets corresponding to the identifiers of the perception targets, that is, the perception target corresponding to the identifier of the perception target moves to the second area, and base station 6 perceives the perception target corresponding to the identifier of the perception target and obtains the perception data. The perception target corresponding to the identifier of the perception target moves to the third area, and base station 7 perceives the perception target corresponding to the identifier of the perception target and obtains the perception data. This is deduced from the above and will not be repeated here.
[0158] Accordingly, in this scenario, the perception report in step S620 is, illustratively, perception report 2, which includes at least one of the following: perception target type information, perception target location information, perception target trajectory information, perception target speed information, and perception target movement direction information. For examples of perception target type information, perception target location information, perception target trajectory information, perception target speed information, and perception target movement direction information, please refer to the description of the above embodiment and will not be repeated here.
[0159] In scenario 2, perception report 2 is obtained by perceiving the perception target corresponding to the perception target identifier, i.e., a perception report of tracking perception. The aforementioned perception target type information, perception target position information, perception target trajectory information, perception target speed information, and perception target movement direction information are the perception target type information, position information, trajectory information, speed information, and movement direction information corresponding to the corresponding perception target identifier.
[0160] For example, the identification of the perception target included in perception request 2 is identification list 1 of the perception target, identification list 1 of the perception target is shown in Table 1, and perception report 2 is shown in Table 2, where #1 represents the identification of perception target 1, #2 represents the identification of perception target 2, and #3 represents the identification of perception target 3.
[0161] Table 1
[0162] Table 2 takes perception report 2 including perception target type information, perception target position information, perception target trajectory information, perception target speed information, and perception target moving direction information as an example. Perception report 2 includes the perception report of the perception target corresponding to the identifier of each perception target in perception target identification list 1.
[0163] Table 2
[0164] Optionally, the second management node filters the perception targets from the perception targets corresponding to the identifiers of the perception targets included in the perception request 2 according to the perception report 2. For example, the second management node determines to further perceive the perception targets 1 and 2 based on the perception reports corresponding to the perception targets 1, 2, and 3 shown in Table 2. The second management node then sends a perception request to the first management node again, and the perception request includes #1 and #2.
[0165] Scenario 3: includes two perceptions. The first perception: perception of a specific area, and the perception report 3 includes the identification of the perception target; the second perception: perception of a specific perception target.
[0166] This scenario includes the process of sensing a specific area in the above scenario 1 and the process of sensing a specific sensing target in the above scenario 2. In other words, this scenario includes the sending and receiving processes of the sensing request in step S610 and the sensing report in step S620 twice. For example, as shown in FIG7 , the method 700 includes:
[0167] S710: The second management node sends a first perception request to the first management node. Correspondingly, the first management node receives the first perception request from the second management node.
[0168] In the embodiment of the present application, the description of perception request one can refer to the description in scenario one and will not be repeated here.
[0169] S720: The first management node sends a third perception report to the second management node. Correspondingly, the first management node receives the third perception report from the second management node.
[0170] Optionally, in an embodiment of the present application, Perception Report 3 includes the information included in Perception Report 1 corresponding to Scenario 1 (i.e., at least one of perception target type information, perception target location information, perception target trajectory information, perception target speed information, and perception target movement direction information); the difference from Perception Report 1 corresponding to Scenario 1 is that, due to the need for a second perception, Perception Report 3 must include the identification of the perception target. The identification of the perception target is an identification assigned by the access network device to the perception target discovered in the first area after the access network device perceives the first area based on Perception Request 1.
[0171] For example, Table 3 takes perception report three including perception target identification list two and perception report three including perception target type information, perception target position information, perception target trajectory information, perception target speed information, and perception target moving direction information as an example, where #1 represents the identification of perception target 1, #2 represents the identification of perception target 2, and #3 represents the identification of perception target 3.
[0172] Table 3
[0173] S730: The second management node sends a third perception request to the first management node. Correspondingly, the first management node sends a fourth perception report to the second management node.
[0174] In an embodiment of the present application, the third perception request includes an identifier of a perception target. The identifier of the perception target included in the third perception request is part or all of the identifiers of the perception target included in the third perception report. That is, the first management node and / or the second management node determines one or more perception targets to be tracked based on the identifier of the perception data included in the third perception report. The third perception request includes the identifier of the one or more perception targets to be tracked.
[0175] In one possible implementation, the first management node sends perception report three to the second management node. The first management node does not determine the perception target to be tracked. The second management node determines one or more perception targets to be tracked based on the identifier of the perception target included in the received perception report three, and then the second management node sends perception request three including the identifier of the perception target to be tracked to the first management node.
[0176] In another possible implementation, the first management node determines one or more perception targets to be tracked based on the third perception report. The first management node sends the identifiers of the one or more perception targets to be tracked determined by the first management node and the corresponding partial perception report to the second management node. The second management node further determines one or more perception targets to be tracked based on the received partial perception report, and then the second management node sends a third perception request including the identifiers of the perception targets to be tracked to the first management node. For example, the first management node determines that the perception targets to be tracked are #1, #2, #3, and #4, and the second management node determines that the perception targets to be tracked are #1 and #2. The third perception request includes #1 and #2.
[0177] In another possible implementation, the third management node determines the perception target to be tracked. The third management node can be, for example, the first device described below, or other devices, which is not limited in the embodiments of the present application. In this implementation, after the first management node sends perception report three to the second management node, the second management node sends perception report three to the third management node. Further, the third management node determines the perception target to be tracked, and sends the identifier of the perception target to be tracked to the second management node, and then the second management node sends perception request three including the identifier of the perception target to be tracked to the first management node. It should be noted that the table of the above example is explained by taking the identifier of the perception target included in the perception request and the perception report as the identifier assigned by the access network device to the perception target as an example. The identifier of the perception target included in the perception request three can be the identifier assigned by the access network device to the perception target, or the identifier assigned by the first management node to the perception target, or the identifier assigned by the second management node to the perception target. Please refer to the description in S610 and will not be repeated here.
[0178] As described above, in an embodiment of the present application, the identification of the perception target included in the perception report three includes the identification of the perception target included in the perception request three. Exemplarily, the perception target is UVA, and the identification of the perception target included in the perception request three is part or all of the identifications of the UVA in the identification of the perception target included in the perception report three.
[0179] For example, perception request three includes perception target identification list three, wherein perception target identification list three (#1; #2) is the identification of some perception targets in perception target representation list two (#1; #2; #3). Perception target identification list three is shown in Table 4, wherein #1 identifies the identification of perception target 1, and #2 identifies the identification of perception target 2.
[0180] Table 4
[0181] S740: The first management node sends a fourth perception report to the second management node. Correspondingly, the second management node receives the fourth perception report from the first management node.
[0182] In an embodiment of the present application, perception report four is obtained by perceiving the perception target corresponding to the identification of the perception target, and perception report four includes at least one of the following items corresponding to the identification of the corresponding perception target: perception target type information, perception target position information, perception target trajectory information, perception target speed information, and perception target moving direction information.
[0183] For example, Table 5 takes perception report four including perception target type information, perception target position information, perception target trajectory information, perception target speed information, and perception target moving direction information as an example. Perception report four includes the perception report of the perception target corresponding to the identifier of each perception target in perception target identifier list three.
[0184] Table 5
[0185] In the perception method provided in the embodiment of the present application, the second management node carries at least one of the perception time information and the identification of the perception target in the perception request, so that the first management node manages the perception time (for example, it can reserve the time for perceiving the first service), or enables the first management node to manage the perception target corresponding to the identification of the perception target (for example, it can track and perceive the perception target corresponding to the identification of the perception target), and then sends a corresponding perception report to the second management node.
[0186] Figure 7 above describes the two-step perception process for scenario three. For ease of understanding, Figures 8 and 9 use a single perception as an example to further describe the perception method 600 shown in Figure 6. It should be noted that S610 and S620 are applicable to both the service-oriented management architecture and the 5G communication architecture. The perception method shown in Figure 8 is applicable to the service-oriented management architecture, while the method shown in Figure 9 is applicable to the 5G communication architecture.
[0187] When the perception method in the embodiment of the present application is applied to a service-oriented management architecture, further, optionally, as shown in FIG8 , the method 600 further includes:
[0188] S830: The first management node sends first information to the second management node. Correspondingly, the second management node receives the first information from the first management node.
[0189] In an embodiment of the present application, the first information is used to represent the sensing capability information of the first management node. This solution can enable the first management node to register the sensing capability information of the first management node with the second management node, so that the second management node can learn the sensing capability of the first management node, and further enable the second management node to send a sensing request within the sensing capability to the second management node.
[0190] The perception capability information includes at least one of the following: perception coverage level, perception positioning accuracy, or perception management range.
[0191] In one possible implementation, the perception capability information includes a perception coverage level and / or a perception positioning accuracy, and the first information is information about registering the perception coverage level and / or the perception positioning accuracy. The first information sent by the first management node to the second management node is: a perception function node deployed by the first management node registers the perception coverage level and / or the perception positioning accuracy with the second management node.
[0192] Exemplarily, the perception coverage levels include: Level 1, for example, Level 1: 10m level, used for perception of daily low-altitude areas; Level 2, for example, Level 2: 1-10m level, used for perception of commercial routes and their associated spaces; Level 3, for example, Level 3: m level, used for, for example, UAV trajectory tracking, collision avoidance, etc.
[0193] Of course, the perceived coverage level may also include other coverage levels, which is not limited in the embodiments of the present application.
[0194] In the embodiment of the present application, the perceived positioning accuracy indicates the highest accuracy that can be achieved by the access network device used for perception. Exemplarily, the perceived positioning accuracy includes: m level, 1-10m level, and 10-20m level.
[0195] Of course, the perceived positioning accuracy may also include other accuracies, which are not limited in the embodiments of the present application.
[0196] In another possible implementation, the perception capability information includes the perception management scope, and the first information is the information of the access network device within the perception management scope registered by the first management node to the second management node, or the first information is the information of the networking information of the access network device registered by the first management node to the second management node.
[0197] In an embodiment of the present application, the perception management scope is used to indicate the scope of access network devices that can be managed by the first management node.
[0198] The perception method provided in the embodiment of the present application enables the first management node to actively report the first information to the second management node under the service-oriented management architecture.
[0199] Optionally, as shown in FIG8 , before step S610, the method 600 further includes:
[0200] S840: The first device sends a sensing request to the second management node. Correspondingly, the second management node receives the sensing request from the first device.
[0201] Optionally, in an embodiment of the present application, the first device is a consumer of the sensing service. For example, the sensing target is a UAV, and the first device is an unmanned aerial system (UAS) service provider (USS) device, or the first device is an unmanned traffic management (UTM) device; or, the sensing target is another type of target, and the first device is a corresponding device, which is not limited in the embodiment of the present application.
[0202] Optionally, as shown in FIG8 , after step S620, the method 600 further includes:
[0203] S850: The second management node sends a perception report to the first device. Correspondingly, the first device receives the perception report from the second management node.
[0204] In the embodiment of the present application, the second management node is to send a perception report to the consumer of the perception service.
[0205] The perception method provided in the embodiment of the present application is that, under the service-oriented management architecture, the consumer of the perception service (such as the first device) can send a perception request to the second management node and obtain a perception report.
[0206] Optionally, as shown in FIG8 , before step S620, the method 600 further includes:
[0207] S860: The access network device sends a perception report to the first management node. Correspondingly, the first management node receives the perception report from the access network device.
[0208] In the perception method provided in the embodiments of the present application, a perception report is obtained by analyzing and calculating perception data on the access network device. This solution can implement the perception function on the management plane, reducing the complexity of the first management node's external interface. Specifically, the entire process is as follows: first, the second management node sends a perception request to the first management node. Then, the first management node configures the access network device to perform perception based on the perception request. After performing perception, the access network device analyzes and calculates the obtained perception data to obtain a perception report. After sending the perception report to the first management node, the first management node sends the perception report to the second management node. The entire process is closed-loop from the management plane to the access network device.
[0209] When the perception method is applied to a 5G communication architecture, further, optionally, as shown in FIG9 , before step S610, the method 600 further includes:
[0210] S930: The first device sends a sensing request to the second management node. Correspondingly, the second management node receives the sensing request from the first device.
[0211] In the embodiment of the present application, the description of the first device can be found in the relevant description in S840 and will not be repeated here.
[0212] Optionally, as shown in FIG9 , after step S620, the method further includes:
[0213] S940: The second management node sends a perception report to the first device. Correspondingly, the first device receives the perception report from the second management node.
[0214] In the embodiment of the present application, the relevant description of S940 can refer to the relevant description of S850, which will not be repeated here.
[0215] In the perception method provided by the embodiment of the present application, under the 5G communication architecture, the consumer of the perception service (e.g., the first device) can send a perception request to the second management node and obtain a perception report. Optionally, as shown in FIG9 , before step S620, the method further includes:
[0216] S950: The access network device sends the sensing data of the first service to the first management node. Correspondingly, the first management node receives the sensing data of the first service from the access network device.
[0217] Optionally, in an embodiment of the present application, the first management node analyzes and calculates the perception data from the access network device to obtain a perception report.
[0218] In the perception method provided in the embodiment of the present application, the access network device sends the perception data to the first management node, so that the first management node can analyze and calculate the perception data and determine a perception report.
[0219] For example, Figures 10 and 11 are schematic diagrams of specific embodiments of the perception method provided in the embodiments of the present application. The specific embodiment shown in Figure 10 is a specific embodiment of the perception method 600 shown in Figure 6 applied to the 5G network architecture shown in Figure 1, and the specific embodiment shown in Figure 11 is a specific embodiment of the method 600 applied to the service-oriented management architecture shown in Figure 2.
[0220] It should be noted that the specific embodiments shown in Figures 10 and 11 are specific embodiments of scenario three, that is, a regional perception request is first sent, and based on the identification of the perception target in the perception report of regional perception, a tracking perception request is sent to obtain a perception report of tracking perception. For the specific embodiments of scenario one and scenario two, please refer to the specific embodiment of scenario three, and the embodiments of this application will not be repeated here.
[0221] As shown in FIG10 , taking the first management node as a core network internal network element, the second management node as an NEF network element, and the first device as a USS or UTM as an example, this specific embodiment includes the following steps:
[0222] S1001: USS or UTM sends a zone awareness request to an NEF network element. Correspondingly, the NEF network element receives the zone awareness request from the USS or UTM.
[0223] In the embodiment of the present application, for the relevant description of the area awareness request sent by the USS or UTM to the NEF network element, please refer to the description of the awareness request 1 in method 600, which will not be repeated here.
[0224] S1002: The NEF network element sends a zone awareness request to a network element within the core network. Correspondingly, the network element within the core network receives the zone awareness request from the NEF network element.
[0225] In the embodiment of the present application, the relevant description of the area awareness request sent by the NEF network element to the network element within the core network can refer to the description of awareness request 1 in method 600, which will not be repeated here.
[0226] S1003: The network elements within the core network configure area-aware access network devices.
[0227] In the embodiment of the present application, the relevant description about the configuration of area-aware access network devices by network elements within the core network can refer to the description of the configuration of area-aware access network devices by the first management node in scenario 1 in method 600, which will not be repeated here.
[0228] S1004: The access network device sends the area-aware sensing data to the network element inside the core network. Correspondingly, the network element inside the core network receives the area-aware sensing data from the access network device.
[0229] In the embodiment of the present application, regarding the access network device sending the area-aware perception data to the internal network element of the core network, reference can be made to the description of S950 in method 600, which will not be repeated here.
[0230] S1005: The network element inside the core network sends a zone awareness report to the NEF network element. Correspondingly, the NEF receives the zone awareness report from the network element inside the core network.
[0231] In the embodiment of the present application, for the relevant description on the core network internal network element sending the area perception perception report to the NEF network element, please refer to the description of perception report three in method 600, which will not be repeated here.
[0232] In the embodiment of the present application, the regional perception report is determined by the network elements within the core network based on the analysis and calculation of the perception data.
[0233] S1006: The NEF network element sends a zone awareness report to the USS or UTM. Correspondingly, the USS or UTM receives the zone awareness report from the NEF network element.
[0234] In the embodiment of the present application, for the relevant description of the perception report of the area perception sent by the NEF network element to the USS or UTM, reference can be made to the description of the perception report three in method 600, which will not be repeated here.
[0235] S1007: The NEF network element sends a trace perception request to the network element inside the core network. Correspondingly, the network element inside the core network receives the trace perception request from the NEF network element.
[0236] In the embodiment of the present application, the description of the tracking perception request sent by the NEF network element to the network element within the core network can refer to the description of perception request three in method 600, which will not be repeated here.
[0237] S1008, the core network internal network element configuration tracks the access network device perceived.
[0238] In the embodiment of the present application, for the relevant description of the access network device configured by the network element within the core network and tracked and perceived, reference can be made to the description of the access network device configured by the first management node and tracked and perceived in scenario 2 of method 600, which will not be repeated here.
[0239] S1009: The access network device sends the tracking and sensing data to the network element inside the core network. Correspondingly, the network element inside the core network receives the tracking and sensing data from the access network device.
[0240] In the embodiment of the present application, the relevant description about the access network device sending the tracking perception data to the internal network element of the core network can refer to the description of S950 in method 600, which will not be repeated here.
[0241] S1010: A network element within the core network sends a tracking and sensing perception report to a network element in the NEF. Correspondingly, the NEF receives the tracking and sensing perception report from the network element within the core network.
[0242] In the embodiment of the present application, for the relevant description on the core network internal network element sending the tracking perception perception report to the NEF network element, reference can be made to the description of perception report four in method 600, which will not be repeated here.
[0243] S1011: The NEF network element sends a tracking and sensing perception report to the USS or UTM. Correspondingly, the USS or UTM receives the tracking and sensing perception report from the NEF network element.
[0244] In the embodiment of the present application, for the relevant description of the tracking perception report sent by the NEF network element to the USS or UTM, reference can be made to the description of the perception report four in method 600, which will not be repeated here.
[0245] As shown in FIG11 , taking the first management node as a domain management functional unit, the second management node as a cross-domain management functional unit, and the first device as a USS or a UTM as an example, this specific embodiment includes the following steps:
[0246] S1101: The domain management function unit sends first information to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the first information from the domain management function unit.
[0247] In the embodiment of the present application, the description of the first information sent by the domain management function unit to the cross-domain management function unit can refer to the description of the first information in method 600, which will not be repeated here.
[0248] S1102: The USS or UTM sends a zone awareness request to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the zone awareness request from the USS or UTM.
[0249] In the embodiment of the present application, the relevant description of the regional awareness request sent by the USS or UTM to the cross-domain management functional unit can refer to the description of awareness request 1 in method 600, which will not be repeated here.
[0250] S1103: The cross-domain management function unit sends a zone awareness request to the domain management function unit. Correspondingly, the domain management function unit receives the zone awareness request from the cross-domain management function unit.
[0251] In the embodiment of the present application, the relevant description of the regional awareness request sent by the cross-domain management function unit to the domain management function unit can refer to the description of awareness request 1 in method 600, which will not be repeated here.
[0252] S1104: The domain management function unit configures a region-aware access network device.
[0253] In the embodiment of the present application, for the relevant description of the domain management function unit configuring the access network device with area awareness, please refer to the description of the first management node configuring the access network device with area awareness in scenario 1 in method 600, which will not be repeated here.
[0254] S1105: The access network device sends a zone awareness report to the domain management function unit. Correspondingly, the domain management function unit receives the zone awareness report from the access network device.
[0255] In the embodiment of the present application, regarding the access network device sending the area awareness report to the domain management functional unit, reference may be made to the description of S860 in method 600, which will not be repeated here.
[0256] S1106: The domain management function unit sends a perception report of area awareness to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the perception report of area awareness from the domain management function unit.
[0257] In the embodiment of the present application, for the relevant description of the domain management function unit sending the regional perception perception report to the cross-domain management function unit, please refer to the description of perception report three in method 600, which will not be repeated here.
[0258] S1107: The cross-domain management function unit sends a zone awareness report to the USS or UTM. Correspondingly, the USS or UTM receives the zone awareness report from the cross-domain management function unit.
[0259] In the embodiment of the present application, for the relevant description on the cross-domain management function unit sending the regional awareness report to the USS or UTM, reference can be made to the description of the awareness report three in method 600, which will not be repeated here.
[0260] S1108: The cross-domain management function unit sends a tracking awareness request to the domain management function unit. Correspondingly, the domain management function unit receives the tracking awareness request from the cross-domain management function unit.
[0261] In the embodiment of the present application, the description of the tracking perception request sent by the cross-domain management function unit to the domain management function unit can refer to the description of perception request three in method 600, which will not be repeated here.
[0262] S1109, the domain management function unit configures the access network device to be tracked and sensed.
[0263] In the embodiment of the present application, for the relevant description of the domain management function unit configuring the access network device for tracking and perception, reference can be made to the description of the first management node configuring the access network device for tracking and perception in scenario 2 in method 600, which will not be repeated here.
[0264] S1110: The access network device sends a tracking and sensing perception report to the domain management function unit. Correspondingly, the domain management function unit receives the tracking and sensing perception report from the access network device.
[0265] In the embodiment of the present application, the description of the access network device sending the tracking perception report to the domain management function unit can be referred to the description of S860 in method 600, which will not be repeated here.
[0266] S1111: The domain management function unit sends a tracking perception report to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the tracking perception report from the domain management function unit.
[0267] In the embodiment of the present application, for the relevant description on the domain management function unit sending the tracking perception perception report to the cross-domain management function unit, reference can be made to the description of perception report four in method 600, which will not be repeated here.
[0268] S1112: The cross-domain management function unit sends a tracking and sensing perception report to the USS or UTM. Correspondingly, the USS or UTM receives the tracking and sensing perception report from the domain management function unit.
[0269] In the embodiment of the present application, for the relevant description of the tracking perception report sent by the cross-domain management function unit to the USS or UTM, reference can be made to the description of perception report four in method 600, which will not be repeated here.
[0270] The above mainly introduces the solutions provided by the embodiments of the present application from the perspective of the interaction between the first management node and the second management node. Accordingly, the embodiments of the present application also provide a communication device, which is used to implement the various methods described above. The communication device can be the first management node in the above method embodiments, or a device including the above first management node, or a component that can be used for the first management node; or the communication device can be the second management node in the above method embodiments, or a device including the above second management node, or a component that can be used for the second management node. It can be understood that in order to implement the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily appreciated by those skilled in the art that, in combination with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Professionals and technicians 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.
[0271] In the embodiment of the present application, the communication device can be divided into functional modules according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be understood that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.
[0272] For example, Figure 12 is a schematic diagram of a communication device provided in an embodiment of the present application. Taking the communication device as the first management node in the above method embodiment as an example, the communication device 1200 includes a transceiver module 1210 and a processing module 1220. The transceiver module 1210, which may also be referred to as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver, a transceiver, or a communication interface.
[0273] In an embodiment of the present application, the transceiver module 1210 is configured to receive a sensing request from the second management node. The sensing request includes at least one of the following: sensing time information, or an identifier of a sensing target; the sensing time information includes at least one of the following: a start time and an end time for sensing the first service, or a sensing period for the first service;
[0274] The transceiver module 1210 is further configured to send a perception report to the second management node.
[0275] All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here. Optionally, the communication device 1200 may further include a storage module 1230, which can be used to store instructions and / or data, and the processing module 1220 can read the instructions and / or data in the storage module 1230.
[0276] In the embodiments of the present application, the communication device is presented in the form of various functional modules divided in an integrated manner. The "module" here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device can take the form of the communication device 500 shown in Figure 5.
[0277] For example, the processor 501 in the communication device 500 shown in FIG5 can call the computer execution instructions stored in the memory 503 so that the communication device 500 executes the perception method in the above method embodiment.
[0278] Specifically, the functions / implementation processes of the transceiver module 1210 and the processing module 1220 in FIG12 can be implemented by the processor 501 in the communication device 500 shown in FIG5 calling computer-executable instructions stored in the memory 503. Alternatively, the functions / implementation processes of the processing module 1220 in FIG12 can be implemented by the processor 501 in the communication device 500 shown in FIG5 calling computer-executable instructions stored in the memory 503, and the functions / implementation processes of the transceiver module 1210 in FIG12 can be implemented by the communication interface 504 in the communication device 500 shown in FIG5.
[0279] Since the communication device provided in the embodiment of the present application can execute the above-mentioned perception method, the technical effects that can be obtained can be referred to the above-mentioned method embodiment and will not be repeated here.
[0280] Alternatively, taking the communication device as the second management node in the above method embodiment as an example, the communication device includes a transceiver module 120 and a processing module 1220. The transceiver module 1210, which may also be referred to as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver, a transceiver, or a communication interface.
[0281] In this embodiment of the present application, the transceiver module 1210 is configured to send a sensing request to the first management node. The sensing request includes at least one of the following: sensing time information or an identifier of a sensing target; the sensing time information includes at least one of the following: a start time and an end time for sensing the first service, or a sensing period for the first service.
[0282] The transceiver module 1210 is further configured to receive a perception report from the first management node.
[0283] All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here. Optionally, the communication device 1200 may further include a storage module 1230, which can be used to store instructions and / or data, and the processing module 1220 can read the instructions and / or data in the storage module 1230.
[0284] In the embodiments of the present application, the communication device is presented in the form of various functional modules divided in an integrated manner. The "module" here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device can take the form of the communication device 500 shown in Figure 5.
[0285] For example, the processor 501 in the communication device 500 shown in FIG5 can call the computer execution instructions stored in the memory 503 so that the communication device 500 executes the perception method in the above method embodiment.
[0286] Specifically, the functions / implementation processes of the transceiver module 1210 and the processing module 1220 in FIG12 can be implemented by the processor 501 in the communication device 500 shown in FIG5 calling computer-executable instructions stored in the memory 503. Alternatively, the functions / implementation processes of the processing module 1220 in FIG12 can be implemented by the processor 501 in the communication device 500 shown in FIG5 calling computer-executable instructions stored in the memory 503, and the functions / implementation processes of the transceiver module 1210 in FIG12 can be implemented by the communication interface 504 in the communication device 500 shown in FIG5.
[0287] Since the communication device provided in the embodiment of the present application can execute the above-mentioned perception method, the technical effects that can be obtained can be referred to the above-mentioned method embodiment and will not be repeated here.
[0288] It should be understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of the two. When any of the above modules or units is implemented in software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow. The processor can be built into an SoC (system on a chip) or an ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions to perform calculations or processing within the processor, it can further include necessary hardware accelerators, such as field programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.
[0289] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.
[0290] Optionally, an embodiment of the present application further provides a communication device (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the method in any of the above method embodiments. In one possible design, the communication device also 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 method in any of the above method embodiments. Of course, the memory may not be in the communication device. When the communication device is a chip system, it may be composed of a chip, or it may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.
[0291] Optionally, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is run on a communication device, the communication device can execute the method described in any of the above method embodiments or any of its implementation methods.
[0292] Optionally, an embodiment of the present application further provides a communication system, which includes the first management node described in the above method embodiment and the second management node described in the above method embodiment.
[0293] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0294] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.
[0295] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.
Claims
1. A sensing method, characterized in that: Applied to a first management node, the method includes: Receive a sensing request from the second management node, where the sensing request includes at least one of the following: Perceive time information, or, the identification of the perceived target; The perceived time information includes at least one of the following: The start time and end time for sensing the first service, Or, the sensing period of the first service; Send a perception report to the second management node.
2. The method according to claim 1, characterized in that: The perception report includes at least one of the following: The type of the perceived target, the position of the perceived target, the trajectory of the perceived target, the speed of the perceived target, the moving direction of the perceived target, or the identification of the perceived target.
3. The method according to claim 1 or 2, characterized in that: The sending the perception report to the second management node includes: In response to the perception request, sending the perception report to the second management node.
4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Sending first information to the second management node, where the first information is used to represent perception capability information of the first management node.
5. The method according to claim 4, characterized in that The sensory capability information includes at least one of the following: Perceived coverage level, perceived positioning accuracy, or perceived management scope.
6. A sensing method, characterized in that: Applied to the second management node, including: Sending a sensing request to the first management node, where the sensing request includes at least one of the following: Perceive time information, or, the identification of the perceived target; The perceived time information includes at least one of the following: The start time and end time for sensing the first service, Or, the sensing period of the first service; Receive a perception report from the first management node.
7. The method according to claim 6, characterized in that The perception report includes at least one of the following: The type of the perceived target, the position of the perceived target, the trajectory of the perceived target, the speed of the perceived target, the moving direction of the perceived target, or the identification of the perceived target.
8. The method according to claim 6 or 7, characterized in that: The method further comprises: Receive first information from the first management node, where the first information is used to represent perception capability information of the first management node.
9. The method according to claim 8, characterized in that The sensory capability information includes at least one of the following: Perceived coverage level, perceived positioning accuracy, or perceived management scope.
10. A sensing method, characterized in that: The method comprises: The first management node executes the method according to any one of claims 1 to 5; The second management node executes the method according to any one of claims 6 to 9.
11. A communication device, characterized in that: include: The transceiver module is configured to receive a sensing request from the second management node, wherein the sensing request includes at least one of the following: Perceive time information, or, the identification of the perceived target; The perceived time information includes at least one of the following: The start time and end time for sensing the first service, Or, the sensing period of the first service; The transceiver module is further used to send a perception report to the second management node.
12. The device according to claim 11, characterized in that The perception report includes at least one of the following: The type of the perceived target, the position of the perceived target, the trajectory of the perceived target, the speed of the perceived target, the moving direction of the perceived target, or the identification of the perceived target.
13. The device according to claim 11 or 12, characterized in that The transceiver module is further used to send a perception report to the second management node, including: In response to the perception request, the transceiver module is further used to send the perception report to the second management node.
14. The device according to any one of claims 11 to 13, characterized in that The transceiver module is further used to send first information to the second management node, where the first information is used to represent the perception capability information of the first management node.
15. The device according to claim 14, characterized in that The sensory capability information includes at least one of the following: Perceived coverage level, perceived positioning accuracy, or perceived management scope.
16. A communication device, characterized in that: include: The transceiver module is configured to send a sensing request to the first management node, where the sensing request includes at least one of the following: Perceive time information, or, the identification of the perceived target; The perceived time information includes at least one of the following: The start time and end time for sensing the first service, Or, the sensing period of the first service; The transceiver module is further configured to receive a perception report from the first management node.
17. The device according to claim 16, characterized in that The perception report includes at least one of the following: The type of the perceived target, the position of the perceived target, the trajectory of the perceived target, the speed of the perceived target, the moving direction of the perceived target, or the identification of the perceived target.
18. The device according to claim 16 or 17, characterized in that The transceiver module is further used to receive first information from the first management node, where the first information is used to represent perception capability information of the first management node.
19. The device according to claim 18, characterized in that The sensory capability information includes at least one of the following: Perceived coverage level, perceived positioning accuracy, or perceived management scope.
20. A communication device, characterized in that: The communication device comprises a module for executing the method according to any one of claims 1 to 5, or comprises a module for executing the method according to any one of claims 6 to 9.
21. A communication device, characterized in that: The communication device comprises a processor; the processor is configured to execute the method according to any one of claims 1 to 5, or to cause the communication device to execute the method according to any one of claims 6 to 9.
22. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises instructions, which, when executed, enable the method according to any one of claims 1 to 5 to be implemented, or enable the method according to any one of claims 6 to 9 to be implemented.
23. A computer program product, characterized in that The computer program product comprises instructions, which, when executed, enable the method according to any one of claims 1 to 5 to be implemented, or enable the method according to any one of claims 6 to 9 to be implemented.
24. A communication system, characterized in that: The communication system comprises a first management node executing the method according to any one of claims 1 to 5 and a second management node executing the method according to any one of claims 6 to 9.
25. The communication system according to claim 24, characterized in that The communication system further comprises: An access network device, wherein the access network device is used to send a perception report to the first management node.
Citation Information
Patent Citations
Communication method and device
CN115802399A
Perception service processing method, terminal and network side equipment
CN115866635A
Sharing classified objects perceived by autonomous vehicles
US20200104289A1