Sensing request method and device, terminal, network side equipment, medium and product

By including the perception request type in the perception request message, the problem of excessive information interaction in the perception and communication fusion process is solved, and the perception overhead is saved.

CN120711533APending Publication Date: 2025-09-26VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410353075.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-03-26
Publication Date
2025-09-26

AI Technical Summary

Technical Problem

In future wireless communication systems, excessive information interaction in the perception and communication fusion process will lead to high communication overhead and high complexity in network function processing.

Method used

By including the perception request type in the perception request message, the information units carried by the perception request message are reduced, and the perception request process is optimized.

Benefits of technology

This reduces the amount of information that needs to be exchanged in the perception and communication fusion process, saving perception overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120711533A_ABST
    Figure CN120711533A_ABST
Patent Text Reader

Abstract

The invention discloses a perception request method and device, a terminal, network side equipment, a medium and a product, and belongs to the technical field of communication, and the perception request method comprises the steps that a second node receives a first message sent by a first node; wherein the first message is used for sensing a request, and the first message comprises a sensing request type. In the sensing request process, the sensing request type is included in the first message, so that the information units carried by the sensing request message can be reduced, the information needing to be interacted in the communication and sensing fusion process can be reduced, and the sensing overhead is saved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a perception request method, device, terminal, network-side equipment, medium and product. Background Art

[0002] Future beyond 5th Generation Mobile Networks (B5G), 6th Generation Mobile Networks or 6th Generation Wireless Systems (6G), or other future wireless communication systems are expected to provide various high-precision perception services, such as indoor positioning for robot navigation, sensing for smart homes, and radar sensing for self-driving cars.

[0003] With the introduction of sensing services, Integrated Sensing and Communication (ISAC) enables sensing and communication systems to share the same frequency band and hardware, improving frequency efficiency and reducing hardware costs. Faced with a wide range of communication and sensing fusion use cases, the information that needs to be exchanged in the communication and sensing fusion process includes sensing targets, sensing areas, sensing data, nodes sending sensing requests, sensing nodes, nodes receiving the requested sensing data, and response timeliness. This can lead to excessive information exchange in the communication and sensing fusion process, resulting in high sensing-related communication overhead. Summary of the Invention

[0004] The embodiments of the present application provide a perception request method, apparatus, terminal, network-side equipment, medium, and product, which can solve the problem of high complexity in processing perception-related network functions.

[0005] In a first aspect, a perception request method is provided, the method comprising:

[0006] The second node receives the first message sent by the first node;

[0007] The first message is used for a perception request, and the first message includes a perception request type.

[0008] In a second aspect, a perception request method is provided, the method comprising:

[0009] The first node sends a first message to the second node;

[0010] The first message is used for a perception request, and the first message includes a perception request type.

[0011] According to a third aspect, a perception request device is provided, the device comprising:

[0012] A first receiving module, configured to receive a first message sent by a first node;

[0013] The first message is used for a perception request, and the first message includes a perception request type.

[0014] In a fourth aspect, a perception request device is provided, the device comprising:

[0015] a fifth sending module, configured to send the first message to the second node;

[0016] The first message is used for a perception request, and the first message includes a perception request type.

[0017] In a fifth aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented, or when the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0018] In the sixth aspect, a terminal is provided, comprising a communication interface, wherein the communication interface is used to receive a first message sent by a first node or send a first message to a second node; wherein the first message is used for a perception request, and the first message includes a perception request type.

[0019] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented, or when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0020] In an eighth aspect, a network side device is provided, including a communication interface, wherein:

[0021] The communication interface is used to receive a first message sent by a first node or send a first message to a second node; wherein, the first message is used for a perception request, and the first message includes a perception request type.

[0022] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0023] In a tenth aspect, a wireless communication system is provided, comprising a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method according to the first aspect, and the network-side device is configured to perform the steps of the method according to the second aspect;

[0024] Alternatively, the system includes a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method according to the second aspect, and the network-side device can be used to perform the steps of the method according to the first aspect;

[0025] Alternatively, the system includes a first network side device and a second network side device, the first network side device can be used to perform the steps of the method described in the first aspect, and the second network side device can be used to perform the steps of the method described in the second aspect.

[0026] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0027] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium, and is executed by at least one processor to implement the steps of the perception request method as described in the first aspect, or the computer program / program product is executed by at least one processor to implement the steps of the perception request method as described in the second aspect.

[0028] In an embodiment of the present application, a second node receives a first message sent by a first node; wherein the first message is for a perception request and includes a perception request type. During the perception request process, including the perception request type in the first message reduces the number of information elements carried in the perception request message, thereby reducing the information required to be exchanged during the communication and perception fusion processes, thereby saving perception overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0030] Figure 2 is a schematic diagram of a perception method applicable to the embodiments of the present application;

[0031] Figure 3 This is a flowchart of a perception request method provided by an embodiment of the present application;

[0032] Figure 4 This is a flowchart of another perception request method provided by an embodiment of the present application;

[0033] Figure 5 is a schematic diagram of a perception request device provided in an embodiment of the present application;

[0034] Figure 6 is a schematic diagram of another sensing request device provided in an embodiment of the present application;

[0035] Figure 7 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0036] Figure 8 is a schematic diagram of a terminal provided in an embodiment of the present application;

[0037] Figure 9 This is a schematic diagram of a network-side device provided in an embodiment of the present application;

[0038] Figure 10 This is a schematic diagram of another network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0040] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0041] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0042] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0043] Figure 1The block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture, etc.), a game console, a personal computer (PC), a teller machine, or a self-service machine, etc., and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0044] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( Function, AF), Location Management Function (LMF), Gateway Mobile Location Center (GMLC), Network Data Analytics Function (NWDAF), etc. It should be noted that in the embodiment of the present application, only the core network equipment in the NR system is introduced as an example, and the specific type of the core network equipment is not limited.

[0045] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

[0046] Sensing and communication systems are usually designed separately and occupy different frequency bands. ISAC enables sensing and communication systems to share the same frequency band and hardware, improving frequency efficiency and reducing hardware costs. ISAC will become a key technology for future wireless communication systems to support many important application scenarios. Typical applications of ISAC include: navigation and obstacle avoidance for autonomous vehicles, indoor positioning and activity recognition based on Wi-Fi, communication and sensing for unmanned aerial vehicles, extended reality (XR), radar and communication integration, etc. Each application has different requirements, limitations and regulatory issues. ISAC has attracted great research interest and attention from academia and industry.

[0047] ISAC achieves low-cost, integrated communication and perception capabilities through shared hardware and software-defined functions. Its key features include: a unified and simplified architecture; reconfigurable and scalable functions; and improved efficiency and reduced costs. The advantages of integrated communication and perception are threefold: reduced equipment cost and size; improved spectrum utilization; and enhanced system performance.

[0048] In the embodiments of the present application, typical communication perception integration scenarios that are expected to be achieved through technical upgrades of the communication system architecture are exemplified as shown in Table 1 below.

[0049] Table 1 Typical scenarios of communication perception integration

[0050]

[0051] In the embodiment of the present application, regarding the sensing signal, according to the difference between the sensing signal sending node and the receiving node, there are 6 basic sensing modes, such as Figure 2 As shown (taking a base station as an example of an access network node), it specifically includes:

[0052] 1) Base station self-transmitting and self-receiving sensing: In this sensing mode, base station A sends a sensing signal and performs sensing measurement by receiving the echo of the sensing signal;

[0053] 2) Inter-base station air interface sensing: Base station B receives the sensing signal sent by base station A and performs sensing measurements;

[0054] 3) Uplink air interface perception: Base station A receives the perception signal sent by terminal A and performs perception measurement;

[0055] 4) Downlink air interface perception: Terminal B receives the perception signal sent by base station B and performs perception measurement;

[0056] 5) Terminal self-transmitting and self-receiving sensing: Terminal A sends a sensing signal and performs sensing measurement by receiving the echo of the sensing signal;

[0057] 6) Sidelink perception between terminals: Terminal B receives the perception signal sent by terminal A and performs perception measurement.

[0058] It is worth noting that Figure 2 Each perception method in the text takes a perception signal sending node and a perception signal receiving node as an example. In actual systems, one or more different perception methods can be selected according to different perception use cases and perception requirements, and each perception method can have one or more sending nodes and receiving nodes. Figure 2 The perception targets in the example are people and cars, and it is assumed that neither people nor cars carry or install signal receiving / transmitting equipment. However, the perception targets in actual scenes will be richer.

[0059] In the embodiments of the present application, the perception data includes at least one of a perception measurement report and perception assistance data. The perception measurement report primarily comprises measurement results obtained after measuring perception measurement quantities, while the perception assistance data includes the location of a terminal sending or receiving a perception signal, the location of an access network node sending or receiving the perception signal, an environment map, target area information, and the like.

[0060] An optional classification method is to classify the perception measurement quantities into the following four categories (this description focuses on the measurement quantities, and can also be divided into three categories or unclassified, etc., and the four categories are only for illustration). Based on the relationship between the perception measurement quantities and the perception services, the third and fourth level measurement quantities below are generally also referred to as perception results. The measurement results of the second and / or first level measurement quantities are also referred to as perception measurement data.

[0061] a) First-level measurement quantities (received signal / original channel information), including: received signal / channel response complex results, amplitude / phase, I / Q path and operation results thereof (operations include addition, subtraction, multiplication, and division, matrix addition, subtraction, multiplication, and division, matrix transposition, trigonometric operations, square root operations, and power operations, as well as threshold detection results and maximum / minimum value extraction results of the above operation results; operations also include Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT), Discrete Fourier Transform (DFT) / Inverse Discrete Fourier Transform (IDFT), 2D-FFT, 3D-FFT, matched filtering, autocorrelation operation, wavelet transform, and digital filtering, as well as threshold detection results and maximum / minimum value extraction results of the above operation results);

[0062] b) Second-level measurement quantities (basic measurement quantities), including: time delay, Doppler, angle, signal strength, and their multi-dimensional combination representation;

[0063] c) Level 3 measurements (basic attributes / status), including: distance, velocity, angle / direction, radar cross section (RCS), and acceleration;

[0064] d) Level 4 measurements (advanced attributes / states) include: spatial position, target presence, trajectory, movement, expression, vital signs, quantity, imaging results, weather, air quality, shape, material, and composition.

[0065] Optionally, the perception configuration includes at least one of the following:

[0066] Configuration of perception measurement objects, configuration of perception signals, configuration of perception measurement quantities, configuration of perception measurement reports and transmission configuration of perception data.

[0067] In the embodiment of the present application, the perception configuration (or perception configuration information) includes at least one of perception measurement object configuration information, perception signal configuration information, perception measurement quantity configuration, perception (measurement) report configuration, and perception data transmission configuration.

[0068] Wireless sensing is the process of measuring received signals and then processing the measurement results to obtain the desired sensing results. Therefore, the configuration of the sensing signal can also be called the configuration of the sensing measurement object, which includes at least one of the following:

[0069] Waveforms, such as Orthogonal Frequency Division Multiplexing (OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), Orthogonal Time Frequency Space (OTFS), Frequency Modulated Continuous Wave (FMCW), and pulse signals;

[0070] Subcarrier spacing: For example, the subcarrier spacing of an OFDM system is 30 kHz.

[0071] Guard interval: The time interval between the end of a signal transmission and the reception of the latest echo signal of that signal. This parameter is proportional to the maximum sensing distance. For example, it can be calculated as 2dmax / c, where dmax is the maximum sensing distance (a sensing requirement). For example, for a self-transmitting and self-receiving sensing signal, dmax represents the maximum distance between the sensing signal receiving point and the signal transmitting point. In some cases, the cyclic prefix (CP) of the OFDM signal can serve as the minimum guard interval. c is the speed of light.

[0072] Bandwidth: This parameter is inversely proportional to the range resolution and can be obtained by c / 2 / delta_d, where delta_d is the range resolution (a perception requirement).

[0073] Burst duration: This parameter is inversely proportional to the rate resolution (a sensing requirement). It is the time span over which the signal is sensed, primarily for calculating Doppler shift. This parameter can be calculated as c / 2 / delta_v / fc, where delta_v is the rate resolution and fc is the carrier frequency or center frequency of the signal.

[0074] Time interval: This parameter can be calculated as c / 2 / fc / v_range; where v_range is the maximum rate minus the minimum rate (pertaining to the sensing requirement); this parameter is the time interval between two adjacent sensing signals;

[0075] The transmit power of the sensing signal is measured, for example, with a value of 2dBm intervals from -20dBm to 23dBm.

[0076] Information about the sending ports of the sensing signal, including quantity and port number;

[0077] Signal formats, such as the Channel-State-Information Reference Signal (CSI-RS), Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), Positioning Reference Signal (PRS), or other predefined signals, as well as related sequence format information;

[0078] Signal direction; for example, the direction of the perceived signal (e.g., base station transmits and UE receives, base station receives and UE transmits, base station transmits and receives independently, base stations transmit and receive between each other, UE transmits and receives independently, or UEs transmit and receive between each other);

[0079] · Sense the beam information of the signal;

[0080] Time resources, such as the time slot index or symbol index of the time slot where the perception signal is located. There are two types of time resources: one-time time resources, for example, one symbol sends an omnidirectional first signal; and one-time time resources, for example, multiple groups of periodic time resources or discontinuous time resources (which may include a start time and an end time). Each group of periodic time resources sends a perception signal in the same direction, and different groups of periodic time resources have different beam directions.

[0081] Frequency resources, including the center frequency of the sensing signal, bandwidth, resource blocks (RBs) or subcarriers, etc.

[0082] Quasi Co-Location (QCL) relationship, for example, the sensing signal includes multiple resources, each resource is associated with a synchronization signal block (Synchronization Signal / PBCH Block, SSB) QCL, QCL includes Type A, B, C or D.

[0083] The sensing measurement parameters configuration is used to instruct the sensing measurement node to measure at least one of the following sensing measurement parameters (a three-category approach is exemplified below for the sensing measurement parameters):

[0084] a) First-level measurement quantities (received signal or original channel information), including: received signal / channel response complex results, amplitude / phase, I / Q path and operation results thereof (operations include addition, subtraction, multiplication, and division, matrix addition, subtraction, multiplication, and division, matrix transposition, trigonometric operations, square root operations, and power operations, as well as threshold detection results and maximum / minimum value extraction results of the above operation results; operations also include Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT), Discrete Fourier Transform (DFT) / Inverse Discrete Fourier Transform (IDFT), 2D-FFT, 3D-FFT, matched filtering, autocorrelation operation, wavelet transform, and digital filtering, as well as threshold detection results and maximum / minimum value extraction results of the above operation results);

[0085] b) Second-level measurement quantities (basic measurement quantities), including: time delay, Doppler, angle, signal strength, and their multi-dimensional combination representation;

[0086] c) Level 3 measurements (also known as perception results) include: target presence, distance, speed, angle / direction, RCS, acceleration, position, trajectory, movement, expression, breathing rate, heart rate, imaging results, weather, air quality, material and composition, etc.

[0087] The perception measurement report configuration includes at least one of the following:

[0088] The access type used for report transmission can be 3GPP access or non-3GPP access. 3GPP access can be indicated as 4G (LTE), 5G (NR), 6G, etc., and non-3GPP access can be indicated as wireless local area network (WLAN), Bluetooth, and wired network. If there are multiple access types, the priority order can also be reflected in a list. For example, if the access type used for report transmission is indicated as 5G or 4G, it means that 5G will be used to transmit the report first.

[0089] Reporting criteria: The criteria that triggers the sensing measurement node to send measurement reports, which can be periodic, event-triggered, or indicated. Events include but are not limited to the following:

[0090] The perceived signal quality detected by the receiving end meets the threshold requirements, such as at least one of the following: the signal-to-noise ratio (SNR), the reference signal receiving power (RSRP), the received signal strength indication (RSSI), and the signal-to-clutter ratio threshold. If the threshold is met, the perceived measurement quantity in the perception measurement item configuration is measured and reported.

[0091] The perception measurement results obtained by the receiving end meet the perception requirements, that is, the perception performance indicators corresponding to the calculated perception measurement results meet or exceed the preset threshold. For example, the perception SNR (an optional definition is the ratio of the effective signal power of the signal propagation path corresponding to the perception target to the noise power, or the ratio of the effective signal power of the signal propagation path corresponding to the perception target to the sum of the noise power and the signal power of the signal propagation paths corresponding to non-perception targets) is or exceed the preset threshold.

[0092] The receiving end correctly demodulates the data (e.g., passes the cyclic redundancy check (CRC)) and performs perception based on the communication data, using a method of first demodulating and then estimating the perception parameters. If the communication demodulation is incorrect, the perception measurement results will be affected and become unreliable.

[0093] The mandatory sensing measurement items meet the requirements. For example, the delay, Doppler and GPS location information of the sensing signal are mandatory sensing measurement items, while RSRP and Reference Signal Receiving Quality (RSRQ) are optional. In this case, they are reported only when multiple mandatory sensing measurement items are available.

[0094] Report format: The report includes the maximum number of cells under the Radio Access Technology (RAT) supported by the second node, the maximum number of measurement quantities for each cell, etc.

[0095] In the embodiment of the present application, the above-mentioned perception data transmission configuration can be understood as a transmission-related configuration of a type of data.

[0096] In the embodiment of the present application, the perceived service QoS is used to indicate the demand for perceived service quality. It can be defined in at least one of the following ways:

[0097] Perception QoS classes are categorized as Type I: Best Effort. If the perception data fails to meet the QoS requirements, the perception data must still be fed back, but with an indication that the requested QoS was not met. If no perception data is obtained, the reason for the failure is fed back. Type II: Multiple QoS. This includes QoS requirements corresponding to multiple QoS levels. If the perception data fails to meet the most stringent QoS requirements, the Sensing Function (SF) initiates the perception process again, attempting to meet lower QoS requirements until one of the QoS requirements is met. If the most relaxed QoS requirements are still not met, the positioning result is not fed back, only the reason for the failure is fed back. Type III: Assured, the most stringent perception QoS type. If the perception data fails to meet the QoS requirements, the positioning result is not fed back, only the reason for the failure is fed back.

[0098] Positioning accuracy (including horizontal and vertical accuracy) describes how closely the measured perception result (i.e., position) of a target object matches its true position. This can be further divided into horizontal perception accuracy and vertical perception accuracy. The former refers to the perception error on a two-dimensional reference plane or horizontal plane, while the latter refers to the perception error along the vertical axis or height.

[0099] Velocity accuracy (including horizontal accuracy and vertical accuracy): describes how close the measured perception of the target object's velocity (i.e., speed) is to its true velocity.

[0100] Perceptual resolution: describes the minimum difference in the measured magnitude (e.g., distance, velocity) of a target object to allow detection of objects of different magnitudes.

[0101] Refresh rate: describes the rate at which sensory data is generated. It is the inverse of the time interval between two consecutive sensory data.

[0102] Missed detection probability: describes the ratio of missed detection events to all events of obtaining sensing results within any predetermined time period when the system attempts to obtain sensing data. It is mainly applicable to binary judgment sensing data.

[0103] False alarm probability: describes the ratio of events that do not represent target objects or environmental features to all events detected in any predetermined time period when attempting to acquire sensory data. It is mainly applicable to perception data with binary judgments.

[0104] Recognition accuracy: describes the probability of correctly identifying the perceived target category.

[0105] Maximum perception service latency: describes the time from triggering the required perception data to providing the perception data at the perception system interface.

[0106] Optionally, the perceived QoS information includes at least one of the following:

[0107] Perception QoS type, positioning accuracy, speed accuracy, perception resolution, perception refresh rate, perception missed detection probability, perception false alarm probability, perception recognition accuracy, and maximum perception service delay.

[0108] Below, in combination with the accompanying drawings, the perception request method, device, terminal, network-side equipment, medium and product provided in the embodiments of the present application are described in detail through some embodiments and their application scenarios.

[0109] See also Figure 3 , Figure 3 This is a flow chart of a perception request method provided by an embodiment of the present invention, which is used for a second node, such as Figure 3 As shown, the method includes the following steps:

[0110] Step 301: The second node receives a first message sent by the first node; wherein the first message is used for a perception request, and the first message includes a perception request type.

[0111] In an embodiment of the present application, the first node initiates a perception request process by sending a first message to the second node. The above-mentioned perception request process is used to request perception, wherein the first message can also be described as a perception request or a perception request message.

[0112] The first node may be a terminal, a network function node (e.g., a core network function node or a radio access network node), or an application function or a perception service client. The second node may be a terminal, a network function node (e.g., a core network function node or a radio access network node), or an application function or a perception service client.

[0113] In an embodiment of the present application, the first message includes the perception request type, and the first message may carry indication information indicating the perception request type.

[0114] In an embodiment of the present application, the second node receives the first message sent by the first node. During the perception request process, by including the perception request type in the first message, the information units carried by the perception request message can be reduced, thereby saving perception overhead.

[0115] Optionally, the perception request type includes at least one of the following:

[0116] The sensing target is the terminal's sensing request.

[0117] Perception request of the terminal associated with the perception target,

[0118] Perception request of the terminal associated with the perception area,

[0119] The sensing target is a sensing request associated with a non-terminal.

[0120] The sensing area is a sensing request associated with a non-terminal.

[0121] The sensing target is the sensing request of the access network device.

[0122] The perception target is associated with the perception request of the access network device.

[0123] Perception area associated access network device perception request,

[0124] The sensing target is a sensing request associated with a non-access network device.

[0125] The perception area is the perception request associated with non-access network devices.

[0126] The sensing node and the sensing request node are the sensing requests of the same node.

[0127] The sensing node and the sensing request node are sensing requests of different nodes.

[0128] The receiving node of the requested sensing data and the sensing requesting node are the same node's sensing request.

[0129] The receiving node of the requested sensing data and the sensing requesting node are sensing requests of different nodes.

[0130] A perception request to request perception results,

[0131] A perception request to request perception measurement data,

[0132] A perception request to request perception assistance data,

[0133] Perception requests triggered by the core network,

[0134] Perception requests triggered by access network devices,

[0135] Terminal-triggered perception request,

[0136] Application function AF triggers the perception request,

[0137] Perception request triggered by the perception service client,

[0138] Instant perception request,

[0139] Latency-aware requests,

[0140] Periodic awareness request.

[0141] In the embodiment of the present application, the perception request type may be a standard perception request type, a custom perception request type, or a combination of the two. The perception request type may include at least one of the following:

[0142] The perception target is a terminal and / or an access network node. The perception request includes a terminal (e.g., user equipment UE) as the perception target, for example, a request to perceive the speed or position of the target UE; and the perception target is an access network node, for example, a request to perceive the speed or position of a mobile base station (e.g., a base station deployed on a low-orbit satellite).

[0143] The target is a perception request for associated terminals and / or access network nodes: including the association of perception targets or perception areas with the above-mentioned terminals and / or access network nodes. One method can be represented by a terminal / access network node identifier and a corresponding association condition. For example, breathing monitoring of one or more people (for example, 2 people) closest to a UE, obstacle perception within 5 meters near a UE, environmental reconstruction within a range corresponding to a mobile base station (for example, a base station deployed on a low-orbit satellite) (for example, the perceptible range can be determined based on perception accuracy and base station power, etc.), and intrusion monitoring within a range corresponding to multiple cells or base stations in a private network scenario. Usually, this type of perception request needs to be perceived based on the location information of the terminal and / or access network node, especially when the terminal and / or access network node associated with the target is mobile, it is necessary to first obtain the latest location information of the terminal and / or access network node, so the perception process definition can be defined for this type of feature.

[0144] A perception request whose target is not associated with a terminal and / or access network node refers to a perception request whose target (perception target and / or perception area) is not associated with a terminal and / or access network node. For example, a perception request includes a perception target or perception area that is a geographic area and a perception characteristic, such as drone intrusion monitoring within a geographic area represented by longitude, latitude, and altitude, or vehicle perception with a speed characteristic representing a speed greater than a threshold. For general geographic area descriptions, refer to the definition in 3GPP TS 23.032.

[0145] The sensing node and the sensing request node are the same node for the sensing request: the above-mentioned sensing node mainly refers to at least one of the sending node of the sensing signal and the receiving node of the sensing signal. For example, a UE sends a sensing request, and the UE is at least one of the sending node of the sensing signal and the receiving node of the sensing signal. For another example, a base station sends a sensing request, and the base station is at least one of the sending node of the sensing signal and the receiving node of the sensing signal. Usually, this type of sensing request may not require sensing node selection (for example, the node sending the sensing request sends and receives the sensing signal for sensing) or select other sensing nodes or sensing functions SF based on the sensing request node (for example, if the node sending the sensing request is also the sending node of the sensing signal, then it is necessary to determine the receiving node of the sensing signal and the sensing function SF based on the location and capabilities of the node).

[0146] A sensing node and a sensing requesting node are sensing requests from different nodes. A sensing node refers to at least one of a transmitting node and a receiving node of a sensing signal. For example, a UE may send a sensing request but not be willing to serve as a transmitting node or a receiving node for sensing signals. The UE may determine the reason for its refusal, for example, due to battery or privacy concerns.

[0147] The sensing request is a request in which the receiving node and the sensing requesting node are the same node. The requested sensing data (also referred to as sensing information) includes at least one of a sensing result, sensing measurement data, or sensing assistance data. For example, a UE sends a sensing request, and the sensing result generated by the network is sent to the UE.

[0148] The sensing data receiving node and the sensing requesting node are different nodes in the sensing request. The requested sensing data (also referred to as sensing information) includes at least one of a sensing result, sensing measurement data, or sensing assistance data. For example, the UE sends a sensing request, and the sensing result generated by the network side is sent to an application function or a sensing services client.

[0149] Perception request for perception results: Perception results mainly refer to third-level or fourth-level measurement quantities in perception data, such as distance, speed, angle / direction, RCS, acceleration, spatial position, target presence, trajectory, movement, expression, vital signs, quantity, imaging results, weather, air quality, shape, material, composition, etc.

[0150] Perception request for perception measurement data: Perception measurement data mainly refers to the first-level and second-level measurement quantities in the perception data, such as delay, Doppler, angle, signal strength, and their multi-dimensional combination representations; and also includes received signals, channel response results, amplitude / phase, I / Q paths, and their calculation results.

[0151] Perception Request for Perception Assistance Data: One type of perception assistance data is defined as data beyond the aforementioned perception results and perception measurement data that assists in generating the desired perception result. For example, this data may include the location of the UE sending or receiving the perception signal, an environmental map, and so on. Another type of perception assistance data is defined as data beyond the aforementioned perception results that assists in generating the desired perception result. For example, the UE requests network-side perception measurement data or UE location information to assist the UE's camera, etc., in performing user posture perception.

[0152] Core network triggered sensing request (Network Induced Sensing Request): A core network network function node (such as AMF, SMF, PCF in the 5G protocol) initiates a sensing request for emergency calls, service load forecasting, etc. When the sensing target is a UE, the core network network function node may be the UE's service node. When the sensing target is a base station, or a sensing target associated with a base station, the core network network function node is the service node of the base station. The core network triggered sensing request may be a core network device acting as the first node to send the above-mentioned first message.

[0153] Network Induced Sensing Request triggered by a radio access network: A perception request is initiated by a radio access network node (such as a base station, CU or DU in the 5G protocol, etc.) for beamforming optimization and network energy saving. When the perception target is a UE, the radio access network node may be a service node of the UE. Or the perception target is the radio access network node, or a perception target associated with the radio access network node. Or the perception area is the coverage area of ​​the radio access network node or a sub-area in the coverage area. Among them, the perception request triggered by the radio access network may be that the radio access network sends the above-mentioned first message as the first node.

[0154] Terminal-triggered perception request: The terminal sends a perception request to the serving Public Land Mobile Network (PLMN). The perceived target may be the terminal itself, a perception target associated with the terminal, or a perception target unrelated to the UE. The terminal's perception request may be the terminal acting as the first node to send the aforementioned first message.

[0155] Awareness request triggered by an application function or awareness service client: The application function or awareness service client sends a request for awareness to a certain PLMN (such as Home PLMN or Visited PLMN) network, where the application function can be an AF outside the network or an AF inside the network.

[0156] Immediate Location Request: The location requester expects to receive a response containing location information within a short period of time, where the time can be specified using the quality of service parameter Qos.

[0157] Deferred Sensing Request: The sensing requester expects to receive a response containing an indication of event occurrence and / or sensing data at a future time (or multiple times). The event type of the deferred sensing request includes at least one of the following:

[0158] Interesting perception results (also known as pre-defined perception results): For example, in intrusion monitoring, the event type might be "intrusion occurred." Another example is rainfall monitoring, where the event type might be "heavy or light rainfall," and one or more pre-defined rainfall intervals.

[0159] Area (also described as a predefined sensing area): Detects events where a target enters, leaves, or stays within a predefined geographic area.

[0160] Preset perception time: After receiving a perception request, perception may not be performed immediately, but perception may be performed and perception data may be fed back at a preset time. In particular, the preset perception time may be periodic sensing (Periodic Sensing), that is, a predefined periodic timer, and an event of activating a perception report when the timer expires. In an embodiment of the present application, a periodic perception request may be used as a parallel perception request form with a delayed perception request, or may be used as a perception request form in a delayed perception request.

[0161] Interesting change features (also described as preset feature changes): For example, the event that the target moves more than a predefined straight-line distance from its previous location. Another example is the event that the rainfall in the sensing area changes by more than a predefined threshold from the previous time.

[0162] Availability of the terminal and / or network equipment: Any event in which network equipment (including core network nodes and / or radio access network nodes, such as AMFs and / or base stations) establishes contact with the terminal. This can also refer to any event in which the core network establishes contact with a radio access network node. For example, this refers to the core network reestablishing a connection with the UE after the UE enters flight mode or is powered off.

[0163] In the embodiments of the present application, for the convenience of explanation, base stations are used instead of access network nodes in some descriptions. It can be understood that the content of the base station can be replaced by other access network nodes.

[0164] Optionally, in the case where the perception request type includes a delay perception request, the first message further includes delay perception request related parameters, where the delay perception request related parameters include at least one of the following: duration of event reporting, minimum time interval between consecutive event reports, maximum time interval between consecutive event reports, maximum event sampling interval, whether to include the requested perception data in the event report, and the number of perception reports;

[0165] Alternatively, in the case where the perception request type includes a periodic perception request, the first message also includes periodic perception request related parameters, and the periodic perception request related parameters include at least one of the following: the time interval between consecutive perception reports, the number of perception reports, and the preset time for the first perception report.

[0166] In an embodiment of the present application, when the perception request executed by the first message is a delay perception request or a periodic perception request, the first message may also carry parameters related to the delay perception request or the periodic perception request, respectively.

[0167] Among them, for periodic perception requests, the preset time of the above-mentioned first perception report refers to the time for sending the first perception report pre-defined in the perception process corresponding to the periodic perception request, or the time for executing the perception report for the first time pre-defined in the perception process.

[0168] When a periodic awareness request is understood as a special case of a delay awareness request, it can be described as including a periodic awareness report type or a triggered awareness report type. The delay awareness request includes parameters related to the periodic awareness report type or parameters related to the triggered awareness report type.

[0169] Optionally, the response to the delay awareness request is associated with at least one of the following triggering events:

[0170] a first preset perception result, a first preset perception area, a first preset perception time, a first preset characteristic change, the availability of the terminal, and the availability of the network device;

[0171] Alternatively, the response to the periodic sensing request is associated with at least one of the following triggering events:

[0172] A second preset perception result, a second preset perception area, a second preset perception time, a second preset characteristic change, the availability of the terminal and the availability of the network device.

[0173] In the embodiments of the present application, the meanings of the first preset perception result, the first preset perception area, the first preset perception time, and the first preset characteristic change can correspond to the descriptions of the preset perception result, the preset perception area, the preset perception time, and the preset characteristic change in the aforementioned embodiments. The second preset perception result, the second preset perception area, the second preset perception time, and the second preset characteristic change can also correspond to the descriptions of the preset perception result, the preset perception area, the preset perception time, and the preset characteristic change in the aforementioned embodiments.

[0174] Optionally, the method further includes:

[0175] When a preset condition is met, the second node sends the sensing data to the receiving node of the requested sensing data;

[0176] The satisfying of the preset conditions includes at least one of the following:

[0177] Satisfy the parameters related to delay-aware requests;

[0178] Satisfy the parameters related to periodic perception requests;

[0179] a triggering event associated with a response satisfying a latency-aware request;

[0180] Satisfy the response association trigger event of the periodic perception request.

[0181] In an embodiment of the present application, the triggering of the perception response of the delayed perception request or the periodic perception request can be performed based on relevant parameters or relevant triggering events.

[0182] It should be noted that the type of perception request can also be defined based on a combination of the above-mentioned multiple perception request types. For example, the UE and / or base station triggers, and the UE and / or base station is a perception request of the perception node. The above two types of conditions together constitute the definition of a type of perception request, or a combination of multiple perception request types defines a perception request type (the perception method can also be determined accordingly).

[0183] Optionally, a definition of a perception request type is a perception request type indication, which may be a value of an information unit with a preset length longer than a characteristic length representing different perception request types. For example, different values ​​of an information unit with an 8-bit length represent different perception request types, such as 00000001 indicating that the target is a UE perception request, 00000010 indicating that the target is a base station perception request, 00000011 indicating a network trigger point perception request, and 01000000 indicating that the target is a UE-associated and UE-triggered perception request, etc.

[0184] Optionally, the first message further includes at least one of the following:

[0185] Perception service type, perception target information, perception area information, sending node identifier of the perception signal, receiving node identifier of the perception signal, receiving node identifier of the requested perception data, requested perception data type indication, first node identifier, perception response timeliness indication, perception mode indication, perception service quality QoS information, valid duration of the requested perception data, pseudo-identification indication of the perception target, perception integrity requirements, and willingness information of the first node to participate in perception.

[0186] In this embodiment of the present application, in addition to the information indicating the type of the perception request, the first message may also include at least one of the following:

[0187] Perception service type (Service Type), used to indicate the perception service type, such as public safety, entertainment services, etc.;

[0188] Perception target information, such as UE and / or base station IDs, such as UE and / or base station IDs and corresponding association conditions;

[0189] Perception region information (e.g., general geographic region description);

[0190] Perceive QoS information;

[0191] The identification of the sending node of the sensing signal;

[0192] Identification of the receiving node that senses the signal;

[0193] The sending node identifier of the perception request (i.e., the first node identifier);

[0194] The receiving node identifier of the requested sensing information;

[0195] An indication of the timeliness of the perceived response may include at least one of immediate, delayed, or periodic;

[0196] Perceptual style indications, e.g. Figure 2 One or a combination of the 6 basic perception modes shown;

[0197] Pseudo-identifier indication (pseudonymindicator): If the sensing request (first message) contains a pseudo-identifier indication, the network assigns a pseudo-identifier to the sensing target (for example, when the sensing target is a UE or a base station) and then sends it to the receiving node of the sensing data (such as an AF or a sensing service client);

[0198] The requested maximum age of sensing data refers to the maximum effective age of the requested sensing information. The requested maximum age of sensing data can also be called the effective age of the requested sensing data. Sensing information within the maximum age meets the requirements, while information exceeding the maximum age does not meet the requirements. The sensing request receiving node (second node) can determine whether the requirements are met based on the maximum effective age and the timestamp of the obtained sensing information.

[0199] The requested perception data type indicates a classification method for perception data types, as described in the aforementioned embodiments, and can include at least one of perception results, perception measurement data, or perception auxiliary data. Another classification method for perception data types can be further subdivided based on the time the perception data was acquired, including at least one of the following: current perception result, current or most recent perception result, perception result at perception time X, current perception measurement data, current or most recent perception measurement data, perception measurement data at perception time X, current perception auxiliary data, current or most recent perception auxiliary data, and perception auxiliary data at perception time X. One method is to obtain the latest data through a perception process when the requested perception type indicates current perception result / measurement data / auxiliary data. When the requested perception type indicates current or most recent perception result / measurement data / auxiliary data, if already acquired perception result / measurement data / auxiliary data is available, a direct response can be provided without performing a subsequent perception process. Alternatively, it can be combined with the maximum duration of the requested perception information. When the requested perception type indicates current or recent perception results / measurement data / auxiliary data, if there are already acquired perception results / measurement data / auxiliary data, the timestamp of the perception information and the maximum duration of the requested perception information are used to determine if they meet the requirements. A direct response is given without the need for a subsequent perception process.

[0200] The willingness information of the first node to participate in sensing refers to the willingness information of the first node (e.g., UE) to participate in sensing provided by the first message: for example, the UE is willing to serve as a sensing node, the UE is unwilling to serve as a sensing node, or the UE has no preference; if the first node is willing to serve as a sensing node, the second node may preferentially select the first node as the sensing node;

[0201] Integrity requirements include at least one of Time to Alert (TTA), Target Integrity Risk (TIR), and Alert Limit. Alert Time refers to the maximum time allowed from when an error exceeds a limit until an unavailable flag is issued; Target Integrity Risk refers to the probability of an error exceeding the upper limit per unit time, provided the unavailable flag is not issued within the TTA. The Alert Limit refers to the maximum permissible perception error to ensure system integrity. If the perception error exceeds this limit, the perceived integrity result may not meet the integrity requirements.

[0202] Optionally, the perception integrity requirement includes at least one of the following:

[0203] Alert time, target integrity risk, and alert limits.

[0204] It is understandable that when certain information is already included in a perception request type message, the first message may not need to be repeatedly indicated, thereby saving signaling overhead. For example, when the perception request type is a perception request in which the perception target is a terminal, the terminal is triggered, the terminal is a receiving node of a perception signal, the terminal is a receiving node of requested perception data, and the perception result is requested, then the first message may not need to include the perception target information, the receiving node identifier of the perception signal, the receiving node identifier of the requested perception data, the sending node identifier of the perception request, and the requested perception data type indication. In this case, the first message may include one of the sending node identifier of the perception signal and the perception response timeliness indication.

[0205] Optionally, the method further includes:

[0206] The second node determines the perception process corresponding to the perception request based on the first message.

[0207] In the embodiments of the present application, on the one hand, considering that the perception process involves a lot of relevant information, it may result in too much information that needs to be exchanged in the communication and perception fusion process, resulting in a large perception-related communication overhead. Therefore, in the perception request process, the perception request is classified, and the first message includes the perception request type, which reduces the information units carried by the sent message, thereby reducing the communication information overhead. On the other hand, considering that the perception process involves a lot of relevant information, which may increase the complexity of perception-related network function processing, the process definition can also be simplified by perception request classification. In other words, one way to use the perception request type is to reduce the information units carried by the sent message based on the type definition and indication information, and another way is to define the perception process based on the perception request type, which helps to refine the interactive information in the perception process according to the classification. In the embodiments of the present application, it is possible to avoid different types of perception request processes being mixed together, resulting in too many information units contained in the message, so that the single message is too large and the processing of each perception-related node is more complicated.

[0208] In an embodiment of the present application, optionally, when the first node is a terminal, the second node is a network function node (including at least one of a core network function node and a radio access network node); when the first node is a radio access network node, the second node is a core network function node. In an embodiment of the present application, the second node may determine the perception process corresponding to the perception request based on the perception request type in the first message sent by the first node.

[0209] Optionally, the second node determines, according to the first message, a perception process corresponding to the perception request, including:

[0210] The second node determines, according to the first message, a target node corresponding to the perception request;

[0211] The second node sends target awareness configuration information to the target node;

[0212] The target node includes at least one of a perception-related function node, a perception node, and a requested perception data receiving node.

[0213] In an embodiment of the present application, a target node related to the perception request can be selected according to the perception request type, thereby determining the corresponding perception process.

[0214] Optionally, the sensing node includes at least one of a sensing signal sending node and a sensing signal receiving node, and the second node determines, according to the first message, a target node corresponding to the sensing request, including at least one of the following:

[0215] In a case where the perception request type includes at least one of a perception request of a terminal as the perception target, a perception request of a terminal associated with the perception target, and a perception request of a terminal associated with the perception area, the second node uses at least one of a serving access network device of the terminal or a serving core network function of the terminal as a perception-related function node;

[0216] When the sensing request type includes at least one of a sensing request in which the sensing target is a terminal, a sensing request in which the sensing target is associated with a terminal, and a sensing request in which the sensing area is associated with a terminal, the second node uses at least one of the terminal and an access network device whose signal coverage covers the terminal as a sensing node;

[0217] When the perception request type includes at least one of a perception request in which the perception target is an access network device, a perception request in which the perception target is associated with an access network device, and a perception request in which the perception area is associated with an access network device, the second node uses the service access and mobility management function AMF of the access network device as a perception-related function node;

[0218] When the sensing request type includes at least one of a sensing request of an access network device as a sensing target, a sensing request of an access network device associated with a sensing target, and a sensing request of an access network device associated with a sensing area, the second node uses the access network device as a sensing node;

[0219] In a case where the sensing request type includes at least one of a sensing request for a terminal associated with a sensing target and a sensing request for a terminal associated with a sensing area, the second node determines a sensing node according to a location of the terminal;

[0220] In a case where the sensing request type includes at least one of a sensing request for sensing a target-associated access network device and a sensing request for sensing an area-associated access network device, the second node determines a sensing node according to a location of the access network device;

[0221] When the perception request type includes at least one of a perception request in which the perception target is non-terminal associated, a perception request in which the perception area is non-terminal associated, a perception request in which the perception target is non-access network device associated, and a perception request in which the perception area is non-access network device associated, the second node uses, according to the perception area in the first message, at least one of the AMF corresponding to the perception area and the access network device corresponding to the perception area as at least one of the perception-related function node and the perception node;

[0222] In a case where the perception request type includes a core network triggered perception request, the second node determines the core network function as a perception-related function node;

[0223] In a case where the perception request type includes a perception request triggered by an access network device, the second node determines the access network device as a perception-related function node;

[0224] In a case where the perception request type includes at least one of a perception request triggered by an access network device and a perception request triggered by a terminal, the second node determines a perception-related function node through a serving network function corresponding to the access network device;

[0225] In a case where the perception request type includes at least one of a perception request triggered by an application function AF and a perception request triggered by a perception service client, the second node determines a perception-related function node through a network exposure function NEF;

[0226] In a case where the sensing request type includes at least one of a delayed sensing request and a periodic sensing request, the second node determines the network device as at least one of a sensing-related function node and a sensing node.

[0227] In an embodiment of the present application, for example, if the perception target is a perception request of a terminal and / or an access network device, the network can select its serving base station or serving AMF as a perception-related functional node based on the terminal and / or access network device in the perception request, and select the terminal and / or access network device as a perception signal sending node or receiving node.

[0228] If the perception target is a terminal and / or a perception target associated terminal, you can choose a perception method in which the terminal sends and receives from the access network device or the UE receives and receives from the access network device, or a perception method in which the access network device sends and receives by itself. In this case, the above-mentioned access network device can be a service access network device of the perception target terminal and / or the perception target associated terminal, or it can be an access network device whose signal coverage range can cover part or all of the access network devices of the above-mentioned perception target terminal and / or the perception target associated terminal.

[0229] If the target is a terminal and / or access network device associated with the perception request, the network selects its serving access network device or serving AMF as the perception-related functional node based on the terminal and / or access network device in the perception request. If the perception request does not provide the location information of the terminal and / or access network device, the network must first estimate the location of the terminal and / or access network device, and then select the perception method and perception node based on the location estimation information.

[0230] If the target of the perception request is a non-terminal and / or access network device, the network selects the AMF as the perception-related function node, perception mode, and perception node based on the perception area, etc. in the perception request. Alternatively, the AMF corresponding to the perception area may be determined based on the perception area, and the AMF may select the corresponding perception function SF, which in turn determines the specific perception mode.

[0231] If the sensing node and the sensing requesting node are the same node, the network selects the sensing requesting node (e.g., the access network device or terminal that sends the sensing request) as the sensing signal sending node and / or the sensing signal receiving node based on the sensing requesting node in the sensing request. When the sensing requesting node is selected as the sensing signal sending node, the corresponding sensing mode can be that the sensing requesting node sends and other nodes receive. When the sensing requesting node is selected as the sensing signal receiving node, the corresponding sensing mode can be that other nodes send the sensing signal and the sensing requesting node receives. When the sensing requesting node is selected as both the sensing signal sending node and the sensing signal receiving node, the corresponding sensing mode can be that the sensing requesting node sends and receives the signal itself.

[0232] If the sensing node and the sensing requesting node are sensing requests from different nodes, then the network should exclude the sensing requesting node when selecting the sensing node based on the sensing requesting node in the sensing request, and avoid selecting it as the sensing node.

[0233] If the receiving node of the requested sensing data and the sensing requesting node are the same node, the network sends the sensing data to the sensing requesting node.

[0234] If the receiving node of the requested perception data and the perception requesting node are different nodes, the network will send the perception information to the indicated perception data receiving node (for example, determined by the receiving node identifier of the requested perception data in the first message), rather than the perception requesting node.

[0235] If it is a perception request requesting a perception result, the network (or other perception node) processes the perception measurement data to generate a perception result, and then sends the perception result to the perception data receiving node.

[0236] If it is a perception request for requesting perception measurement data, the network (or other perception nodes) does not need to process the perception measurement data and sends the perception measurement data to the perception data receiving node.

[0237] If it is a sensing request for sensing assistance data, the network (or other sensing node) sends the sensing assistance data to the sensing data receiving node.

[0238] If it is a network-triggered sensing request (Network Induced Sensing Request), the node that usually triggers the sensing request is the service network node of the sensing target or sensing area (for example, the access network equipment perceives the environment within its coverage area for auxiliary beam management, etc., for example, the AMF perceives the number of users within its service area for auxiliary network optimization). In this case, the network side does not need to select the sensing-related functional node, because the network functional node that triggers the sensing request is the required sensing-related functional node.

[0239] If the perception request is triggered by the terminal and / or access network equipment, the corresponding service network function (such as AMF, SF) will select other perception-related functional nodes (such as SF, NEF), etc.

[0240] If the terminal and / or access network device requests its own perception information, authentication may be simplified. For example, the second node may not need to authenticate the terminal and / or access network device.

[0241] If the perception request is triggered by an application function or a perception service client, the corresponding network open function (such as NEF) will select other perception-related function nodes (such as SF, AMF, etc.), and a more complete authentication mechanism is required to authenticate the requested perception information.

[0242] If the perception request type includes at least one of a delayed perception request and a periodic perception request, since the perception process usually takes a long time, a network device with relatively stable communication performance (for example, a fixed location) is usually selected as at least one of the perception-related functional nodes and the perception node.

[0243] In an embodiment of the present application, the above-mentioned network can be a second node, or it can be another node other than the second node (which can be described as a third node), and the third node can interact with the second node to perform a perception process.

[0244] Optionally, the second node determines, according to the first message, a perception process corresponding to the perception request, including:

[0245] The second node determines, according to the first message, at least one of a sensing time domain resource and a sensing frequency domain resource corresponding to the sensing process.

[0246] In this embodiment of the present application, the perception time-frequency resources corresponding to the perception process can be selected according to the perception request type.

[0247] For example, if it is an immediate location request, the network allocates air interface sensing time and frequency resources according to the sensing response time requirement during the sensing process, and the air interface sensing time and frequency resources only need to meet the current sensing response.

[0248] If it is a delayed sensing request (Deferred Sensing Request), the network needs to continuously monitor the requested delay event (i.e., the triggering event associated with the response to the delayed sensing request) during the sensing process (for example, monitor whether the delay event occurs), and allocate air interface sensing time-frequency resources for the delayed event. The air interface sensing time-frequency resources may be periodic, etc., to meet the sensing response requirements within the time interval when the delayed sensing request is valid.

[0249] Optionally, the first message includes a receiving node identifier of the requested perception data, and after the second node sends the target perception configuration information to the target node, the method further includes:

[0250] The second node sends the sensing data to the requested receiving node of the sensing data.

[0251] In an embodiment of the present application, after executing the perception process by sending target perception configuration information to the target node, the second node can send the perception data obtained by the perception measurement to the receiving node of the requested perception data.

[0252] Optionally, the third node may send the perception data to the receiving node of the requested perception data based on the instruction of the second node.

[0253] Optionally, the first message further includes information about the first node's willingness to participate in perception, and the second node determines, based on the first message, a target node corresponding to the perception request, including:

[0254] The second node determines the target node according to the perception request type and the willingness information of the first node to participate in perception.

[0255] In this embodiment of the present application, the perception request (first message) may also provide information about the willingness of the first node (e.g., UE) to participate in perception: for example, whether the UE is willing to serve as a perception node, whether the UE is unwilling to serve as a perception node, or whether the UE has no preference. If the first node is willing to serve as a perception node, the second node may preferentially select the first node as the perception node.

[0256] Optionally, the second node determines, according to the first message, a perception process corresponding to the perception request, including:

[0257] When the second node agrees to the perception request, it determines the perception process corresponding to the perception request according to the first message.

[0258] In an embodiment of the present application, before determining the perception process based on the first message, the second node will also judge whether to agree to the perception request. Only when the second node agrees to the perception request will it determine the perception process corresponding to the perception request based on the first message, thereby ensuring the rationality of the perception process.

[0259] Optionally, the method further includes at least one of the following:

[0260] The second node rejects the sensing request if the first message includes the sensing target and the number of the sensing targets is greater than or equal to a first preset threshold;

[0261] The second node rejects the sensing request if the first message includes the sensing areas and the number, area or height of the sensing areas is greater than or equal to a second preset threshold;

[0262] When the second node fails to authenticate the sensing request, rejecting the sensing request;

[0263] When authorization of the perception request fails, the second node rejects the perception request.

[0264] In an embodiment of the present application, specific limitations are made on several situations in which the second node disagrees with the perception request, that is, rejects the perception request. One optional way is to make a judgment based on at least one of the perception target and the perception area. When the number of perception targets exceeds a preset threshold, and / or the perception area exceeds a preset range, it can be considered that the current request cannot be satisfied, that is, the second node determines to reject the perception request. Another optional way is to judge whether to reject the perception request based on the authentication and / or authorization results. If the authentication and authorization are successful, the perception request can be approved, otherwise the perception request is rejected. Among them, authentication includes but is not limited to identity authentication of the first node and at least one of the other relevant nodes in the perception request, and authorization can be based on the relevant configuration file to determine whether to allow the perception request to be executed.

[0265] Optionally, the method further includes:

[0266] When rejecting the perception request, the second node sends a second message to the first node, where the second message is used to reject the perception request.

[0267] In an embodiment of the present application, when a perception request is rejected, the rejection request can be fed back to the initiator of the perception request (the first node). As described in the aforementioned embodiment, when a perception request is approved, a specific perception process can be determined, and the above-mentioned perception process can be related to the first node or unrelated to the first node. That is, when the perception is approved, the second node can send feedback of the approval request to the first node or not.

[0268] Optionally, the method further includes:

[0269] When the second node agrees with the perception request, the second node sends a third message to the first node, where the third message is used to agree with the perception request.

[0270] For ease of understanding, the following is an illustrative description of the execution process of the embodiment of the present application based on several different examples:

[0271] Example 1

[0272] Step 1: The first node sends a perception request (first message), where the perception request includes a perception request type, and the perception request type includes at least one of the following items or a combination of multiple items. One of the definitions of a perception request type is a perception request type indication, where different values ​​of an information unit of a certain (e.g., 8) bit length represent different perception request types (e.g., 00000001 indicates a perception request of a UE as the target, 00000010 indicates a perception request of a base station as the target, 00000011 indicates a network trigger point perception request, and 01000000 indicates a perception request of a UE associated with the target and triggered by the UE, etc.);

[0273] The specific perception request type can be described in the above embodiment, and other information included in the perception request can refer to the description of the above embodiment;

[0274] Step 2: The second node receives the sensing request and performs sensing service authorization and authentication based on the sensing request. If the authentication or authorization fails, the network (the second node or other node) sends a sensing response to reject the sensing request. If the authentication and authorization pass, the network can select a sensing-related function node (e.g., AMF, NEF, SF), a sensing method, and a sensing node (base station and / or UE) based on the specific sensing request type. The sensing method can be used to further determine the target node (at least one of a sensing-related function node, a sensing node, and a node receiving the requested sensing data).

[0275] The specific method of determining the target node corresponding to the sensing request according to the sensing request type in the first message can refer to the description of the above embodiment;

[0276] Step 3: The selected node receives the sensing configuration information (refer to the description of the above embodiment) and executes the sensing process;

[0277] Step 4: Optionally, the network (the second node or another node) sends a perception response to the perception result receiving node indicated by the perception request. When the first node is a UE, and the UE is both the perception measurement node and the perception result receiving node, one method is: in step 3, the UE reports the perception measurement data to the network, and then the network sends the generated perception result to the UE in this step. Another method is: the UE generates a perception result based on the perception measurement data without reporting the perception test data to the network, and then the perception measurement reporting in step 3 and this step are skipped.

[0278] Example 2

[0279] Step 1. The perception request sent by the first node is a delayed perception request, and the delayed perception request includes a periodic sensing report type, or a triggered sensing report type, or parameters related to the periodic sensing report type, or parameters related to the triggered sensing report type.

[0280] The periodic perception report type is an event type in the delayed perception request, and the parameters related to this type include the time interval between consecutive perception reports, the total number of reports, and the predetermined location time of the first perception report;

[0281] The triggering events corresponding to the triggered perception report type (or event-triggered perception report type) include the perception results of interest, area (Area), the change characteristics of interest, or the availability of UE and / or base station, etc. The parameters related to the event-triggered perception report type include the duration of the event report, the minimum time interval between consecutive event reports, the maximum time interval between consecutive event reports, the maximum event sampling interval, whether the requested perception information should be included in the event report, and whether only one perception report or multiple perception reports are required. Optionally, the relevant parameters of the perception result event report of interest also include the perception result of interest; the relevant parameters of the area event report also include detailed information of the target geographical area, an indication of the need for additional inspection, whether the perception target is located in the requested target area, and whether the event to be reported is the perception target being in the target area, entering or leaving the target area; the relevant parameters of the perception feature event report of interest also include threshold perception feature parameters, such as threshold linear distance, threshold rainfall, threshold acceleration, etc.; the relevant parameters of the availability event report of the UE and / or access network device also include UE availability events (such as registration request registration in the 5G protocol, UE RRC state from idle to active or from inactive to active, etc.), access network device availability events (for example, base station or cell from on to off, or from off to on, etc.).

[0282] For other information that may be included in the perception request, please refer to the description of the aforementioned embodiment;

[0283] Step 2: The second node receives the sensing request and, optionally, pre-determines whether the sensing targets and / or sensing areas in the sensing request meet the requirements. For example, if the number of requested sensing targets and / or sensing areas is greater than one, the network verifies whether the number of target terminals in the sensing request is equal to or less than the maximum number of target terminals of the first node (e.g., the sensing service client). If the maximum number of target terminals is exceeded, the network sends a sensing response, rejecting the sensing request. Optionally, a rejection reason may be provided: exceeding the maximum number of target terminals. If the number of requested sensing targets and / or sensing areas is one, or does not exceed the maximum number of target terminals, the network performs service authentication or authorization based on the sensing request. If authentication or authorization fails, the network (the second node or another node) sends a sensing response, rejecting the sensing request. If authentication and authorization succeed, the network selects sensing-related function nodes (e.g., AMF, NEF, SF), sensing modes, and sensing nodes (base station and / or UE).

[0284] Step 3: The selected node receives the perception configuration information (refer to the description of the above embodiment) and executes the perception process.

[0285] Step 4: The network detects whether the periodic perception report type, the triggered perception report type, or the related parameters of each type in the perception request are met. If the report triggering condition is met (for example, the timer expires, the perception result of interest is obtained, the perception feature of interest is obtained, an area event occurs, or a UE / base station availability event occurs), then optionally, the network (the second node or other node) sends a perception response to the perception result receiving node indicated by the perception request. When the first node is a UE, and the UE is a perception measurement node and a perception result receiving node, one method is: in step 3, the UE reports the perception measurement data to the network, and the network sends the generated perception result to the UE in this step; another method is: the UE generates a perception result based on the perception measurement data, and there is no need to report the perception test data to the network, then the perception measurement report in step 3 (refer to the description of the previous embodiment) and this step 4 are skipped.

[0286] Example 3

[0287] Step 1. The UE sends a UE-triggered perception request message. Different types of perception services can be requested: the perception target is the perception result of the UE, the perception target is the perception result of the target associated with the UE, the perception target is the perception result of the target not associated with the UE, and the perception result or perception assistance data sent to the perception service client or AF or wireless access network node (such as a base station). Among them, one use case for sending to the wireless access network node is that the perception result or perception assistance data is used to assist wireless communication, such as beamforming or channel estimation. The perception request can also provide information on the UE's willingness to participate in perception: UE as a perception node, preferably UE as a perception node, UE not as a perception node, and no preference.

[0288] For other information that may be included in the perception request, please refer to the description of the aforementioned embodiment;

[0289] Step 2: The second node receives the sensing request, and the network performs service authentication and / or authorization based on the sensing request. If authentication or authorization fails, the network (the second node or another node) sends a sensing response, rejecting the sensing request. If authentication and authorization succeed, the network selects sensing-related function nodes (e.g., AMF, NEF, SF), sensing methods, and sensing nodes (base station and / or UE). If the sensing request provides information about the UE's willingness to participate in sensing, the network selects the sensing method and sensing node based on the UE's willingness to participate in sensing.

[0290] Step 3: The selected node receives the perception configuration information (refer to the description of the above embodiment) and executes the perception process.

[0291] Step 4: Optionally, the network (the second node or another node) sends a perception response to the perception result receiving node indicated by the perception request. When the first node is a UE, and the UE is both the perception measurement node and the perception result receiving node, one method is: in step 3, the UE reports the perception measurement data to the network, and then the network sends the generated perception result to the UE in this step. Another method is: the UE generates a perception result based on the perception measurement data without reporting the perception test data to the network, and then the perception measurement reporting in step 3 and this step are skipped.

[0292] See also Figure 4 , Figure 4 This is a flowchart of another perception request method provided by an embodiment of the present invention, which is used for a first node, such as Figure 4 As shown, the method includes the following steps:

[0293] Step 401: The first node sends a first message to the second node;

[0294] The first message is used for a perception request, and the first message includes a perception request type.

[0295] Optionally, the perception request type includes at least one of the following:

[0296] The sensing target is the terminal's sensing request.

[0297] Perception request of the terminal associated with the perception target,

[0298] Perception request of the terminal associated with the perception area,

[0299] The sensing target is a sensing request associated with a non-terminal.

[0300] The sensing area is a sensing request associated with a non-terminal.

[0301] The sensing target is the sensing request of the access network device.

[0302] The perception target is associated with the perception request of the access network device.

[0303] Perception area associated access network device perception request,

[0304] The sensing target is a sensing request associated with a non-access network device.

[0305] The perception area is the perception request associated with non-access network devices.

[0306] The sensing node and the sensing request node are the sensing requests of the same node.

[0307] The sensing node and the sensing request node are sensing requests of different nodes.

[0308] The receiving node of the requested sensing data and the sensing requesting node are the same node's sensing request.

[0309] The receiving node of the requested sensing data and the sensing requesting node are sensing requests of different nodes.

[0310] A perception request to request perception results,

[0311] A perception request to request perception measurement data,

[0312] A perception request to request perception assistance data,

[0313] Perception requests triggered by the core network,

[0314] Perception requests triggered by access network devices,

[0315] Terminal-triggered perception request,

[0316] Application function AF triggers the perception request,

[0317] Awareness request triggered by the awareness service client,

[0318] Instant perception request,

[0319] Latency-aware requests,

[0320] Periodic awareness request.

[0321] Optionally, in the case where the perception request type includes a delay perception request, the first message further includes delay perception request related parameters, where the delay perception request related parameters include at least one of the following: duration of event reporting, minimum time interval between consecutive event reports, maximum time interval between consecutive event reports, maximum event sampling interval, whether to include the requested perception data in the event report, and the number of perception reports;

[0322] Alternatively, in the case where the perception request type includes a periodic perception request, the first message also includes periodic perception request related parameters, and the periodic perception request related parameters include at least one of the following: the time interval between consecutive perception reports, the number of perception reports, and the preset time for the first perception report.

[0323] Optionally, the first message further includes at least one of the following:

[0324] Perception service type, perception target information, perception area information, sending node identifier of the perception signal, receiving node identifier of the perception signal, receiving node identifier of the requested perception data, requested perception data type indication, first node identifier, perception response timeliness indication, perception mode indication, perception service quality QoS information, valid duration of the requested perception data, pseudo-identification indication of the perception target, perception integrity requirements, and willingness information of the first node to participate in perception.

[0325] Optionally, the perception integrity requirement includes at least one of the following:

[0326] Alert time, target integrity risk, and alert limits.

[0327] Optionally, the method further includes:

[0328] receiving a second message sent by the second node, where the second message is used to reject the perception request;

[0329] Or, receive a third message sent by the second node, where the second message is used to agree to the perception request.

[0330] It should be noted that this embodiment is as Figure 3 The method embodiment of the first node corresponding to the embodiment shown in the figure can be found in the specific implementation method. Figure 3 To avoid duplication, the relevant descriptions in the embodiment shown in the figure will not be repeated in this embodiment. Figure 3 All implementations in the method embodiment shown are applicable to this embodiment and can achieve the same or similar beneficial effects. To avoid repeated description, this embodiment will not be described in detail.

[0331] The perception request method provided in the embodiment of the present application can be executed by a perception request device. Figure 3 Taking the method of the embodiment shown as an example, Figure 5 As shown, the perception request device 500 provided in an embodiment of the present application is described.

[0332] The apparatus 500 comprises:

[0333] A first receiving module 501 is configured to receive a first message sent by a first node;

[0334] The first message is used for a perception request, and the first message includes a perception request type.

[0335] Optionally, the perception request type includes at least one of the following:

[0336] The sensing target is the terminal's sensing request.

[0337] Perception request of the terminal associated with the perception target,

[0338] Perception request of the terminal associated with the perception area,

[0339] The sensing target is a sensing request associated with a non-terminal.

[0340] The perception area is a perception request associated with a non-terminal. The perception target is a perception request associated with an access network device.

[0341] Perception area associated access network device perception request,

[0342] The sensing target is a sensing request associated with a non-access network device.

[0343] The perception area is the perception request associated with non-access network devices.

[0344] The sensing node and the sensing request node are the sensing requests of the same node.

[0345] The sensing node and the sensing request node are sensing requests of different nodes.

[0346] The receiving node of the requested sensing data and the sensing requesting node are the same node's sensing request.

[0347] The receiving node of the requested sensing data and the sensing requesting node are sensing requests of different nodes.

[0348] A perception request to request perception results,

[0349] A perception request to request perception measurement data,

[0350] A perception request to request perception assistance data,

[0351] Perception requests triggered by the core network,

[0352] Perception requests triggered by access network devices,

[0353] Terminal-triggered perception request,

[0354] Application function AF triggers the perception request,

[0355] Awareness request triggered by the awareness service client,

[0356] Instant perception request,

[0357] Latency-aware requests,

[0358] Periodic awareness request.

[0359] Optionally, in the case where the perception request type includes a delay perception request, the first message further includes delay perception request related parameters, where the delay perception request related parameters include at least one of the following: duration of event reporting, minimum time interval between consecutive event reports, maximum time interval between consecutive event reports, maximum event sampling interval, whether to include the requested perception data in the event report, and the number of perception reports;

[0360] Alternatively, in the case where the perception request type includes a periodic perception request, the first message also includes periodic perception request related parameters, and the periodic perception request related parameters include at least one of the following: the time interval between consecutive perception reports, the number of perception reports, and the preset time for the first perception report.

[0361] Optionally, the response to the delay awareness request is associated with at least one of the following triggering events:

[0362] a first preset perception result, a first preset perception area, a first preset perception time, a first preset characteristic change, the availability of the terminal, and the availability of the network device;

[0363] Alternatively, the response to the periodic sensing request is associated with at least one of the following triggering events:

[0364] A second preset perception result, a second preset perception area, a second preset perception time, a second preset characteristic change, the availability of the terminal and the availability of the network device.

[0365] Optionally, the device further includes:

[0366] A first sending module, configured to send the requested sensing data to a receiving node when a preset condition is met;

[0367] The satisfying of the preset conditions includes at least one of the following:

[0368] Satisfy the parameters related to delay-aware requests;

[0369] Satisfy the parameters related to periodic perception requests;

[0370] a triggering event associated with a response satisfying a latency-aware request;

[0371] Satisfy the response association trigger event of the periodic perception request.

[0372] Optionally, the first message further includes at least one of the following:

[0373] Perception service type, perception target information, perception area information, sending node identifier of the perception signal, receiving node identifier of the perception signal, receiving node identifier of the requested perception data, requested perception data type indication, first node identifier, perception response timeliness indication, perception mode indication, perception service quality QoS information, valid duration of the requested perception data, pseudo-identification indication of the perception target, perception integrity requirements, and willingness information of the first node to participate in perception.

[0374] Optionally, the perception integrity requirement includes at least one of the following:

[0375] Alert time, target integrity risk, and alert limits.

[0376] Optionally, the device further includes:

[0377] A determination module is used to determine the perception process corresponding to the perception request based on the first message.

[0378] Optionally, the determining module includes:

[0379] A first determining submodule, configured to determine a target node corresponding to the perception request according to the first message;

[0380] A second sending module is used to send target perception configuration information to the target node;

[0381] The target node includes at least one of a perception-related function node, a perception node, and a requested perception data receiving node.

[0382] Optionally, the sensing node includes at least one of a sensing signal sending node and a sensing signal receiving node, and the first determining submodule includes:

[0383] a first determining unit, configured to, when the sensing request type includes at least one of a sensing request of a terminal being a sensing target, a sensing request of a terminal associated with a sensing target, and a sensing request of a terminal associated with a sensing area, select at least one of a serving access network device of the terminal or a serving core network function of the terminal as a sensing-related function node;

[0384] a second determining unit, configured to, when the sensing request type includes at least one of a sensing request in which the sensing target is a terminal, a sensing request in which the sensing target is associated with a terminal, and a sensing request in which the sensing area is associated with a terminal, select at least one of the terminal and an access network device whose signal coverage covers the terminal as a sensing node;

[0385] a third determining unit, configured to, when the sensing request type includes at least one of a sensing request where the sensing target is an access network device, a sensing request where the sensing target is associated with an access network device, and a sensing request where the sensing area is associated with an access network device, use the service access and mobility management function AMF of the access network device as a sensing-related function node;

[0386] a fourth determining unit, configured to, when the sensing request type includes at least one of a sensing request in which the sensing target is an access network device, a sensing request in which the sensing target is associated with an access network device, and a sensing request in which the sensing area is associated with an access network device, use the access network device as a sensing node;

[0387] a fifth determining unit, configured to determine a sensing node according to a location of the terminal when the sensing request type includes at least one of a sensing request for a terminal associated with a sensing target and a sensing request for a terminal associated with a sensing area;

[0388] a sixth determining unit, configured to determine a sensing node according to a location of the access network device when the sensing request type includes at least one of a sensing request for sensing a target-associated access network device and a sensing request for sensing an area-associated access network device;

[0389] a seventh determining unit, configured to, when the perception request type includes at least one of a perception request in which the perception target is non-terminal associated, a perception request in which the perception area is non-terminal associated, a perception request in which the perception target is non-access network device associated, and a perception request in which the perception area is non-access network device associated, use, according to the perception area in the first message, at least one of the AMF corresponding to the perception area and the access network device corresponding to the perception area as at least one of the perception-related function node and the perception node;

[0390] an eighth determining unit, configured to, when the perception request type includes a core network triggered perception request, determine the core network function as a perception-related function node;

[0391] a ninth determining unit, configured to, when the perception request type includes a perception request triggered by an access network device, determine the access network device as a perception-related function node;

[0392] a tenth determining unit, configured to determine a perception-related function node by using a serving network function corresponding to the access network device when the perception request type includes at least one of a perception request triggered by an access network device and a perception request triggered by a terminal;

[0393] an eleventh determining unit, configured to determine a perception-related function node through a network exposure function NEF when the perception request type includes at least one of a perception request triggered by an application function AF and a perception request triggered by a perception service client;

[0394] The twelfth determining unit is configured to determine the network device as at least one of a perception-related function node and a perception node when the perception request type includes at least one of a delayed perception request and a periodic perception request.

[0395] Optionally, the first message includes an identifier of a receiving node of the requested sensing data, and the apparatus further includes:

[0396] The third sending module is used to send the perception data to the receiving node of the requested perception data.

[0397] Optionally, the first message further includes information about the first node's willingness to participate in sensing, and the first determining submodule further includes:

[0398] A thirteenth determining unit is configured to determine the target node according to the perception request type and the willingness information of the first node to participate in perception.

[0399] Optionally, the determining module includes:

[0400] The second determining submodule is configured to determine at least one of a sensing time domain resource and a sensing frequency domain resource corresponding to the sensing process according to the first message.

[0401] Optionally, the determining module includes:

[0402] The third determination submodule is used to determine the perception process corresponding to the perception request according to the first message when the perception request is agreed.

[0403] Optionally, the device further includes:

[0404] A first rejecting module, configured to reject the sensing request if the first message includes sensing targets and the number of the sensing targets is greater than or equal to a first preset threshold;

[0405] a second rejecting module, configured to reject the sensing request if the first message includes sensing areas and the number, area, or height of the sensing areas is greater than or equal to a second preset threshold;

[0406] A third rejection module is configured to reject the perception request if the authentication of the perception request fails;

[0407] The fourth rejection module is used to reject the perception request when the authorization for the perception request fails.

[0408] Optionally, the device further includes:

[0409] The fourth sending module is used to send a second message to the first node when the perception request is rejected, and the second message is used to reject the perception request.

[0410] It should be noted that the perception request device provided in the embodiment of the present invention is a device capable of executing the above perception request method. Figure 3 All implementations in the illustrated method embodiment are applicable to the perception request device and can achieve the same or similar beneficial effects. To avoid repetitive description, this embodiment will not be described in detail.

[0411] The perception request method provided in the embodiment of the present application can be executed by a perception request device. Figure 4 Taking the method of the embodiment shown as an example, Figure 6 As shown, the perception request device 600 provided in an embodiment of the present application is described.

[0412] The device comprises:

[0413] A fifth sending module 601 is configured to send a first message to a second node;

[0414] The first message is used for a perception request, and the first message includes a perception request type.

[0415] Optionally, the perception request type includes at least one of the following:

[0416] The sensing target is the terminal's sensing request.

[0417] Perception request of the terminal associated with the perception target,

[0418] Perception request of the terminal associated with the perception area,

[0419] The sensing target is a sensing request associated with a non-terminal.

[0420] The sensing area is a sensing request associated with a non-terminal.

[0421] The sensing target is the sensing request of the access network device.

[0422] The perception target is associated with the perception request of the access network device.

[0423] Perception area associated access network device perception request,

[0424] The sensing target is a sensing request associated with a non-access network device.

[0425] The perception area is the perception request associated with non-access network devices.

[0426] The sensing node and the sensing request node are the sensing requests of the same node.

[0427] The sensing node and the sensing request node are sensing requests of different nodes.

[0428] The receiving node of the requested sensing data and the sensing requesting node are the same node's sensing request.

[0429] The receiving node of the requested sensing data and the sensing requesting node are sensing requests of different nodes.

[0430] A perception request to request perception results,

[0431] A perception request to request perception measurement data,

[0432] A perception request to request perception assistance data,

[0433] Perception requests triggered by the core network,

[0434] Perception requests triggered by access network devices,

[0435] Terminal-triggered perception request,

[0436] Application function AF triggers the perception request,

[0437] Awareness request triggered by the awareness service client,

[0438] Instant perception request,

[0439] Latency-aware requests,

[0440] Periodic awareness request.

[0441] Optionally, in the case where the perception request type includes a delay perception request, the first message further includes delay perception request related parameters, where the delay perception request related parameters include at least one of the following: duration of event reporting, minimum time interval between consecutive event reports, maximum time interval between consecutive event reports, maximum event sampling interval, whether to include the requested perception data in the event report, and the number of perception reports;

[0442] Alternatively, in the case where the perception request type includes a periodic perception request, the first message also includes periodic perception request related parameters, and the periodic perception request related parameters include at least one of the following: the time interval between consecutive perception reports, the number of perception reports, and the preset time for the first perception report.

[0443] Optionally, the first message further includes at least one of the following:

[0444] Perception service type, perception target information, perception area information, sending node identifier of the perception signal, receiving node identifier of the perception signal, receiving node identifier of the requested perception data, requested perception data type indication, first node identifier, perception response timeliness indication, perception mode indication, perception service quality QoS information, valid duration of the requested perception data, pseudo-identification indication of the perception target, perception integrity requirements, and willingness information of the first node to participate in perception.

[0445] Optionally, the perception integrity requirement includes at least one of the following:

[0446] Alert time, target integrity risk, and alert limits.

[0447] Optionally, the apparatus 600 further includes:

[0448] A second receiving module is configured to receive a second message sent by the second node, where the second message is used to reject the sensing request;

[0449] Or, a third receiving module is used to receive a third message sent by the second node, where the second message is used to agree to the perception request.

[0450] It should be noted that the perception request device provided in the embodiment of the present invention is a device capable of executing the above perception request method. Figure 4 All implementations in the illustrated method embodiment are applicable to the perception request device and can achieve the same or similar beneficial effects. To avoid repetitive description, this embodiment will not be described in detail.

[0451] The perception request device 500 or the perception request device 600 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0452] like Figure 7 As shown, the embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702, wherein the memory 702 stores a program or instruction that can be run on the processor 701. For example, when the communication device 700 is a terminal, the program or instruction is executed by the processor 701 to implement the above Figure 3 or Figure 4 When the communication device 700 is a network side device, the program or instruction is executed by the processor 701 to implement the above Figure 3 or Figure 4 The various steps of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0453] The embodiment of the present application further provides a terminal, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the following Figure 3 or Figure 4 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 8 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0454] The terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809 and at least some of the components of the processor 810.

[0455] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) to power each component. The power supply can be logically connected to the processor 810 through a power management system, thereby realizing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0456] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the graphics processor 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0457] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0458] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 809 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0459] Processor 810 may include one or more processing units. Optionally, processor 810 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0460] The radio frequency unit 801 is used to receive a first message sent by a first node or send a first message to a second node; wherein the first message is used for a perception request, and the first message includes a perception request type.

[0461] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the method embodiment Figure 3 or Figure 4 , and achieve the same or corresponding technical effects. To avoid repetition, they will not be described here.

[0462] The embodiment of the present application further provides a network side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 3 or Figure 4 The network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation method of the above method embodiment are applicable to the network side device embodiment and can achieve the same technical effect.

[0463] Specifically, the embodiment of the present application also provides a network side device. Figure 9 As shown, network-side device 900 includes an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. Antenna 91 is connected to radio frequency device 92. In the uplink direction, radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing. In the downlink direction, baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92. Radio frequency device 92 processes the received information and then sends it through antenna 91.

[0464] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 93 , which includes a baseband processor.

[0465] The baseband device 93 may include, for example, at least one baseband board on which a plurality of chips are arranged, such as Figure 9 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 95 via a bus interface to call the program in the memory 95 to execute the network device operations shown in the above method embodiment.

[0466] The network side device may further include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).

[0467] Specifically, the network side device 900 of the embodiment of the present application further includes: instructions or programs stored in the memory 95 and executable on the processor 94, and the processor 94 calls the instructions or programs in the memory 95 to execute. Figure 5 or Figure 6 The methods executed by the modules shown achieve the same technical effects, so they will not be described here to avoid repetition.

[0468] Specifically, the embodiment of the present application also provides a network side device. Figure 10As shown, the network side device 1000 includes: a processor 1001, a network interface 1002 and a memory 1003. The network interface 1002 is, for example, a common public radio interface (CPRI).

[0469] Specifically, the network side device 1000 of the embodiment of the present application further includes: instructions or programs stored in the memory 1003 and executable on the processor 1001, and the processor 1001 calls the instructions or programs in the memory 1003 to execute Figure 5 or Figure 6 The methods executed by the modules shown achieve the same technical effects, so they will not be described here to avoid repetition.

[0470] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored, and when the program or instruction is executed by the processor, the above Figure 3 or Figure 4 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0471] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0472] The embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the above Figure 3 or Figure 4 The various processes of the method embodiment can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0473] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0474] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the above Figure 3 or Figure 4 The various processes of the method embodiments can achieve the same technical effects, and to avoid repetition, they will not be described here.

[0475] The embodiment of the present application also provides a communication system, including: the system includes a terminal and a network side device, the terminal can be used to perform the following Figure 3 The steps of the method described in the figure are as follows: Figure 4 The steps of the method described;

[0476] Alternatively, the system includes a terminal and a network side device, and the terminal can be used to perform the following Figure 4 The steps of the method described in the figure are as follows: Figure 3 The steps of the method described;

[0477] Alternatively, the system includes a first network side device and a second network side device, wherein the first network side device can be used to perform the following steps: Figure 3 The steps of the method described above, the second network side device can be used to perform the following Figure 4 The steps of the method described are shown.

[0478] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0479] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0480] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A perception request method, characterized in that: include: The second node receives the first message sent by the first node; The first message is used for a perception request, and the first message includes a perception request type.

2. The method according to claim 1, characterized in that The perception request type includes at least one of the following: The sensing target is the terminal's sensing request. Perception request of the terminal associated with the perception target, Perception request of the terminal associated with the perception area, The sensing target is a sensing request associated with a non-terminal. The sensing area is a sensing request associated with a non-terminal. The sensing target is the sensing request of the access network device. The perception target is associated with the perception request of the access network device. Perception area associated access network device perception request, The sensing target is a sensing request associated with a non-access network device. The perception area is the perception request associated with non-access network devices. The sensing node and the sensing request node are the sensing requests of the same node. The sensing node and the sensing request node are sensing requests of different nodes. The receiving node of the requested sensing data and the sensing requesting node are the same node's sensing request. The receiving node of the requested sensing data and the sensing requesting node are sensing requests of different nodes. A perception request to request perception results, A perception request to request perception measurement data, A perception request to request perception assistance data, Perception requests triggered by the core network, Perception requests triggered by access network devices, Terminal-triggered perception request, Application function AF triggers the perception request, Awareness request triggered by the awareness service client, Instant perception request, Latency-aware requests, Periodic awareness request.

3. The method according to claim 2, characterized in that In the case where the perception request type includes a delay perception request, the first message further includes delay perception request related parameters, where the delay perception request related parameters include at least one of the following: duration of event reporting, minimum time interval between consecutive event reports, maximum time interval between consecutive event reports, maximum event sampling interval, whether to include the requested perception data in the event report, and the number of perception reports; Alternatively, in the case where the perception request type includes a periodic perception request, the first message also includes periodic perception request related parameters, and the periodic perception request related parameters include at least one of the following: the time interval between consecutive perception reports, the number of perception reports, and the preset time for the first perception report.

4. The method according to claim 3, characterized in that The response to the delay-aware request is associated with at least one of the following triggering events: a first preset perception result, a first preset perception area, a first preset perception time, a first preset characteristic change, the availability of the terminal, and the availability of the network device; Alternatively, the response to the periodic sensing request is associated with at least one of the following triggering events: A second preset perception result, a second preset perception area, a second preset perception time, a second preset characteristic change, the availability of the terminal and the availability of the network device.

5. The method according to claim 4, characterized in that The method further comprises: When a preset condition is met, the second node sends the sensing data to the receiving node of the requested sensing data; The satisfying of the preset conditions includes at least one of the following: Satisfy the parameters related to delay-aware requests; Satisfy the parameters related to periodic perception requests; a triggering event associated with a response satisfying a latency-aware request; Satisfy the response association trigger event of the periodic perception request.

6. The method according to any one of claims 1 to 5, characterized in that The first message further includes at least one of the following: Perception service type, perception target information, perception area information, sending node identifier of the perception signal, receiving node identifier of the perception signal, receiving node identifier of the requested perception data, requested perception data type indication, first node identifier, perception response timeliness indication, perception mode indication, perception service quality QoS information, valid duration of the requested perception data, pseudo-identification indication of the perception target, perception integrity requirements, and willingness information of the first node to participate in perception.

7. The method according to claim 6, characterized in that The perception integrity requirement includes at least one of the following: Alert time, target integrity risk, and alert limits.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The second node determines the perception process corresponding to the perception request based on the first message.

9. The method according to claim 8, characterized in that The second node determines, according to the first message, a perception process corresponding to the perception request, including: The second node determines, according to the first message, a target node corresponding to the perception request; The second node sends target awareness configuration information to the target node; The target node includes at least one of a perception-related function node, a perception node, and a requested perception data receiving node.

10. The method according to claim 9, characterized in that The sensing node includes at least one of a sensing signal sending node and a sensing signal receiving node, and the second node determines, according to the first message, a target node corresponding to the sensing request, including at least one of the following: In a case where the perception request type includes at least one of a perception request of a terminal as the perception target, a perception request of a terminal associated with the perception target, and a perception request of a terminal associated with the perception area, the second node uses at least one of a serving access network device of the terminal or a serving core network function of the terminal as a perception-related function node; When the sensing request type includes at least one of a sensing request in which the sensing target is a terminal, a sensing request in which the sensing target is associated with a terminal, and a sensing request in which the sensing area is associated with a terminal, the second node uses at least one of the terminal and an access network device whose signal coverage covers the terminal as a sensing node; When the perception request type includes at least one of a perception request in which the perception target is an access network device, a perception request in which the perception target is associated with an access network device, and a perception request in which the perception area is associated with an access network device, the second node uses the service access and mobility management function AMF of the access network device as a perception-related function node; When the sensing request type includes at least one of a sensing request of an access network device as a sensing target, a sensing request of an access network device associated with a sensing target, and a sensing request of an access network device associated with a sensing area, the second node uses the access network device as a sensing node; In a case where the sensing request type includes at least one of a sensing request for a terminal associated with a sensing target and a sensing request for a terminal associated with a sensing area, the second node determines a sensing node according to a location of the terminal; In a case where the sensing request type includes at least one of a sensing request for sensing a target-associated access network device and a sensing request for sensing an area-associated access network device, the second node determines a sensing node according to a location of the access network device; When the perception request type includes at least one of a perception request in which the perception target is non-terminal associated, a perception request in which the perception area is non-terminal associated, a perception request in which the perception target is non-access network device associated, and a perception request in which the perception area is non-access network device associated, the second node uses, according to the perception area in the first message, at least one of the AMF corresponding to the perception area and the access network device corresponding to the perception area as at least one of the perception-related function node and the perception node; In a case where the perception request type includes a core network triggered perception request, the second node determines the core network function as a perception-related function node; In a case where the perception request type includes a perception request triggered by an access network device, the second node determines the access network device as a perception-related function node; In a case where the perception request type includes at least one of a perception request triggered by an access network device and a perception request triggered by a terminal, the second node determines a perception-related function node through a serving network function corresponding to the access network device; In a case where the perception request type includes at least one of a perception request triggered by an application function AF and a perception request triggered by a perception service client, the second node determines a perception-related function node through a network exposure function NEF; In a case where the sensing request type includes at least one of a delayed sensing request and a periodic sensing request, the second node determines the network device as at least one of a sensing-related function node and a sensing node.

11. The method according to claim 9 or 10, characterized in that The first message includes a receiving node identifier of the requested sensing data, and after the second node sends target sensing configuration information to the target node, the method further includes: The second node sends the sensing data to the requested receiving node of the sensing data.

12. The method according to any one of claims 9 to 11, characterized in that The first message also includes information about the willingness of the first node to participate in the perception, and the second node determines the target node corresponding to the perception request according to the first message, including: The second node determines the target node according to the perception request type and the willingness information of the first node to participate in perception.

13. The method according to any one of claims 8 to 12, characterized in that The second node determines, according to the first message, a perception process corresponding to the perception request, including: The second node determines, according to the first message, at least one of a sensing time domain resource and a sensing frequency domain resource corresponding to the sensing process.

14. The method according to any one of claims 8 to 13, characterized in that The second node determines, according to the first message, a perception process corresponding to the perception request, including: When the second node agrees to the perception request, it determines the perception process corresponding to the perception request according to the first message.

15. The method according to claim 14, characterized in that The method further comprises at least one of the following: The second node rejects the sensing request if the first message includes the sensing target and the number of the sensing targets is greater than or equal to a first preset threshold; The second node rejects the sensing request if the first message includes the sensing areas and the number, area or height of the sensing areas is greater than or equal to a second preset threshold; When the second node fails to authenticate the sensing request, rejecting the sensing request; When authorization of the perception request fails, the second node rejects the perception request.

16. The method according to claim 14 or 15, characterized in that The method further comprises: When rejecting the perception request, the second node sends a second message to the first node, where the second message is used to reject the perception request.

17. A perception request method, characterized in that: include: The first node sends a first message to the second node; The first message is used for a perception request, and the first message includes a perception request type.

18. The method according to claim 17, characterized in that The perception request type includes at least one of the following: The sensing target is the terminal's sensing request. Perception request of the terminal associated with the perception target, Perception request of the terminal associated with the perception area, The sensing target is a sensing request associated with a non-terminal. The sensing area is a sensing request associated with a non-terminal. The sensing target is the sensing request of the access network device. The perception target is associated with the perception request of the access network device. Perception area associated access network device perception request, The sensing target is a sensing request associated with a non-access network device. The perception area is the perception request associated with non-access network devices. The sensing node and the sensing request node are the sensing requests of the same node. The sensing node and the sensing request node are sensing requests of different nodes. The receiving node of the requested sensing data and the sensing requesting node are the same node's sensing request. The receiving node of the requested sensing data and the sensing requesting node are sensing requests of different nodes. A perception request to request perception results, A perception request to request perception measurement data, A perception request to request perception assistance data, Perception requests triggered by the core network, Perception requests triggered by access network devices, Terminal-triggered perception request, Application function AF triggers the perception request, Awareness request triggered by the awareness service client, Instant perception request, Latency-aware requests, Periodic awareness request.

19. The method according to claim 18, characterized in that In the case where the perception request type includes a delay perception request, the first message further includes delay perception request related parameters, where the delay perception request related parameters include at least one of the following: duration of event reporting, minimum time interval between consecutive event reports, maximum time interval between consecutive event reports, maximum event sampling interval, whether to include the requested perception data in the event report, and the number of perception reports; Alternatively, in the case where the perception request type includes a periodic perception request, the first message also includes periodic perception request related parameters, and the periodic perception request related parameters include at least one of the following: the time interval between consecutive perception reports, the number of perception reports, and the preset time for the first perception report.

20. The method according to any one of claims 17 to 19, characterized in that The first message further includes at least one of the following: Perception service type, perception target information, perception area information, sending node identifier of the perception signal, receiving node identifier of the perception signal, receiving node identifier of the requested perception data, requested perception data type indication, first node identifier, perception response timeliness indication, perception mode indication, perception service quality QoS information, valid duration of the requested perception data, pseudo-identification indication of the perception target, perception integrity requirements, and willingness information of the first node to participate in perception.

21. The method according to claim 20, characterized in that The perception integrity requirement includes at least one of the following: Alert time, target integrity risk, and alert limits.

22. The method according to any one of claims 17 to 21, characterized in that The method further comprises: receiving a second message sent by the second node, where the second message is used to reject the perception request; Or, receive a third message sent by the second node, where the second message is used to agree to the perception request.

23. A perception request device, characterized in that: The device comprises: A first receiving module, configured to receive a first message sent by a first node; The first message is used for a perception request, and the first message includes a perception request type.

24. The device according to claim 23, characterized in that In the case where the perception request type includes a delay perception request, the first message further includes delay perception request related parameters, where the delay perception request related parameters include at least one of the following: duration of event reporting, minimum time interval between consecutive event reports, maximum time interval between consecutive event reports, maximum event sampling interval, whether to include the requested perception data in the event report, and the number of perception reports; Alternatively, in the case where the perception request type includes a periodic perception request, the first message further includes periodic perception request related parameters, and the periodic perception request related parameters include at least one of the following: a time interval between consecutive perception reports, a number of perception reports, and a preset time for the first perception report; The device further comprises: A first sending module, configured to send the requested sensing data to a receiving node when a preset condition is met; The satisfying of the preset conditions includes at least one of the following: Satisfy the parameters related to delay-aware requests; Satisfy the parameters related to periodic perception requests; a triggering event associated with a response satisfying a latency-aware request; Satisfy the response association trigger event of the periodic sensing request; The response to the delay perception request is associated with at least one of the following triggering events: a first preset perception result, a first preset perception area, a first preset perception time, a first preset feature change, the availability of the terminal, and the availability of the network device; The response to the periodic perception request is associated with at least one of the following triggering events: a second preset perception result, a second preset perception area, a second preset perception time, a second preset feature change, the availability of the terminal, and the availability of the network device.

25. The device according to claim 23 or 24, characterized in that The device further comprises: A determination module is used to determine the perception process corresponding to the perception request based on the first message.

26. The device according to claim 25, characterized in that The determining module includes: A first determining submodule, configured to determine a target node corresponding to the perception request according to the first message; A second sending module is used to send target perception configuration information to the target node; The target node includes at least one of a perception-related function node, a perception node, and a requested perception data receiving node.

27. The device according to claim 26, characterized in that The sensing node includes at least one of a sensing signal sending node and a sensing signal receiving node, and the first determining submodule includes: a first determining unit, configured to, when the sensing request type includes at least one of a sensing request of a terminal being a sensing target, a sensing request of a terminal associated with a sensing target, and a sensing request of a terminal associated with a sensing area, select at least one of a serving access network device of the terminal or a serving core network function of the terminal as a sensing-related function node; a second determining unit, configured to, when the sensing request type includes at least one of a sensing request in which the sensing target is a terminal, a sensing request in which the sensing target is associated with a terminal, and a sensing request in which the sensing area is associated with a terminal, select at least one of the terminal and an access network device whose signal coverage covers the terminal as a sensing node; a third determining unit, configured to, when the sensing request type includes at least one of a sensing request where the sensing target is an access network device, a sensing request where the sensing target is associated with an access network device, and a sensing request where the sensing area is associated with an access network device, use the service access and mobility management function AMF of the access network device as a sensing-related function node; a fourth determining unit, configured to, when the sensing request type includes at least one of a sensing request in which the sensing target is an access network device, a sensing request in which the sensing target is associated with an access network device, and a sensing request in which the sensing area is associated with an access network device, use the access network device as a sensing node; a fifth determining unit, configured to determine a sensing node according to a location of the terminal when the sensing request type includes at least one of a sensing request for a terminal associated with a sensing target and a sensing request for a terminal associated with a sensing area; a sixth determining unit, configured to determine a sensing node according to a location of the access network device when the sensing request type includes at least one of a sensing request for sensing a target-associated access network device and a sensing request for sensing an area-associated access network device; a seventh determining unit, configured to, when the perception request type includes at least one of a perception request in which the perception target is non-terminal associated, a perception request in which the perception area is non-terminal associated, a perception request in which the perception target is non-access network device associated, and a perception request in which the perception area is non-access network device associated, use, according to the perception area in the first message, at least one of the AMF corresponding to the perception area and the access network device corresponding to the perception area as at least one of the perception-related function node and the perception node; an eighth determining unit, configured to, when the perception request type includes a core network triggered perception request, determine the core network function as a perception-related function node; a ninth determining unit, configured to, when the perception request type includes a perception request triggered by an access network device, determine the access network device as a perception-related function node; a tenth determining unit, configured to determine a perception-related function node by using a serving network function corresponding to the access network device when the perception request type includes at least one of a perception request triggered by an access network device and a perception request triggered by a terminal; an eleventh determining unit, configured to determine a perception-related function node through a network exposure function NEF when the perception request type includes at least one of a perception request triggered by an application function AF and a perception request triggered by a perception service client; The twelfth determining unit is configured to determine the network device as at least one of a perception-related function node and a perception node when the perception request type includes at least one of a delayed perception request and a periodic perception request.

28. The device according to claim 26 or 27, characterized in that The first message includes a receiving node identifier of the requested sensing data, and the apparatus further includes: The third sending module is used to send the perception data to the receiving node of the requested perception data.

29. The device according to any one of claims 26 to 28, characterized in that The first message also includes information about the willingness of the first node to participate in the sensing. The first determination submodule further includes: A thirteenth determining unit is configured to determine the target node according to the perception request type and the willingness information of the first node to participate in perception.

30. The device according to any one of claims 25 to 29, characterized in that The determining module includes: The second determining submodule is configured to determine at least one of a sensing time domain resource and a sensing frequency domain resource corresponding to the sensing process according to the first message.

31. The device according to any one of claims 25 to 30, characterized in that The determining module includes: The third determination submodule is used to determine the perception process corresponding to the perception request according to the first message when the perception request is agreed.

32. The device according to claim 31, characterized in that The device further comprises: A first rejecting module, configured to reject the sensing request if the first message includes sensing targets and the number of the sensing targets is greater than or equal to a first preset threshold; a second rejecting module, configured to reject the sensing request if the first message includes sensing areas and the number, area, or height of the sensing areas is greater than or equal to a second preset threshold; A third rejection module is configured to reject the perception request if the authentication of the perception request fails; The fourth rejection module is used to reject the perception request when the authorization for the perception request fails.

33. The device according to claim 31 or 32, characterized in that The device further comprises: The fourth sending module is used to send a second message to the first node when the perception request is rejected, and the second message is used to reject the perception request.

34. A perception request device, characterized in that The device comprises: a fifth sending module, configured to send the first message to the second node; The first message is used for a perception request, and the first message includes a perception request type.

35. The device according to claim 34, characterized in that The device further comprises: A second receiving module is configured to receive a second message sent by the second node, where the second message is used to reject the sensing request; Or, a third receiving module is used to receive a third message sent by the second node, where the second message is used to agree to the perception request.

36. A terminal, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the perception request method as described in any one of claims 1 to 16, or when the program or instruction is executed by the processor, it implements the steps of the perception request method as described in any one of claims 17 to 22.

37. A network side device, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the perception request method as described in any one of claims 1 to 16, or when the program or instruction is executed by the processor, it implements the steps of the perception request method as described in any one of claims 17 to 22.

38. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the perception request method as described in any one of claims 1 to 16, or when the program or instruction is executed by the processor, it implements the perception request method as described in any one of claims 17 to 22.

39. A computer program product, characterized in that The method comprises computer instructions, which implement the steps of the method according to any one of claims 1 to 16 when the computer instructions are executed by a processor, or implement the steps of the method according to any one of claims 17 to 22 when the computer instructions are executed by a processor.