Communication sensing method, communication sensing apparatus, storage medium, and program product

Abstract

Provided are a communication sensing method, a communication sensing apparatus, a storage medium, and a program product. The method is applied to a first node and comprises: receiving sensing configuration information sent by a second node; and performing configuration on the basis of the sensing configuration information.

Description

Communication sensing methods, communication sensing devices, storage media and software products

[0001] This disclosure claims priority to Chinese patent application No. 202411589091.7, filed on November 7, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a communication sensing method, a communication sensing device, a storage medium, and a program product. Background Technology

[0003] The future 6G mobile communication technology network will incorporate new scenarios such as communication sensing and artificial intelligence (AI) on top of traditional user service data transmission. Communication sensing and AI will generate massive amounts of data, which can originate from terminals, base stations, edge servers, and the core network. This means that all network element nodes in the 6G network will have a need for data collection, analysis, and processing, and data transmission may occur between any network element nodes within the 6G network. Taking sensing as an example, sensing can include communication sensing measurement data and environmental or target object sensing data. Summary of the Invention

[0004] This disclosure provides a communication sensing method, a communication sensing device, a storage medium, and a program product.

[0005] On one hand, this disclosure provides a communication sensing method applied to a first node, comprising: receiving sensing configuration information sent by a second node; and configuring the node according to the sensing configuration information.

[0006] On the other hand, embodiments of this disclosure provide a communication sensing method, which is applied to a second node and includes: sending sensing configuration information to a first node.

[0007] In another aspect, embodiments of this disclosure provide a communication sensing method applied to a second node, comprising: receiving sensing authorization information from a first node sent by a third node; and determining whether the first node authorizes the execution of sensing based on the sensing authorization information from the first node.

[0008] In another aspect, embodiments of this disclosure provide a communication sensing method applied to a third node, comprising: sending sensing request information to one or more second nodes; and receiving sensing response information sent by one or more second nodes.

[0009] In another aspect, embodiments of this disclosure provide a communication sensing device applied to a first node, the device comprising: a receiving module and a processing module.

[0010] The receiving module receives the perception configuration information sent by the second node. The processing module performs configuration based on the perception configuration information.

[0011] In another aspect, embodiments of this disclosure provide a communication sensing device applied to a second node, the device comprising: a transmitting module.

[0012] The sending module is used to send perception configuration information to the first node.

[0013] In another aspect, embodiments of this disclosure provide a communication sensing device applied to a second node, the device comprising: a receiving module and a processing module.

[0014] The receiving module receives the perception authorization information from the first node sent by the third node. The processing module determines whether the first node authorizes the execution of perception based on the first node's perception authorization information.

[0015] In another aspect, embodiments of this disclosure provide a communication sensing device applied to a third node, the device comprising: a transmitting module and a receiving module.

[0016] The sending module is used to send perception request information to one or more second nodes. The receiving module is used to receive perception response information sent by one or more second nodes.

[0017] In another aspect, embodiments of this disclosure provide a communication sensing device, including a memory and a processor. The memory and the processor are coupled. The memory is used to store a computer program. When the processor executes the computer program, it implements the communication sensing method of any of the above aspects.

[0018] In another aspect, embodiments of this disclosure provide a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the communication sensing method described above.

[0019] In another aspect, embodiments of this disclosure provide a computer program product including computer program instructions that, when executed, implement the communication sensing method described above. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0021] Figure 1 is a schematic diagram of a 5G user plane data transmission architecture according to some embodiments;

[0022] Figure 2 is a schematic diagram of a UE-side perceived data transmission scenario according to some embodiments;

[0023] Figure 3 is a schematic diagram of a RAN-side sensing data transmission scenario according to some embodiments;

[0024] Figure 4 is a data plane architecture diagram between a base station and a core network according to some embodiments;

[0025] Figure 5 is a schematic diagram of a communication system according to some embodiments;

[0026] Figure 6 is a flowchart of a communication sensing method according to some embodiments;

[0027] Figure 7 is a flowchart of another communication sensing method according to some embodiments;

[0028] Figure 8 is a flowchart of yet another communication sensing method according to some embodiments;

[0029] Figure 9 is a flowchart of yet another communication sensing method according to some embodiments;

[0030] Figure 10 is a signaling flowchart of a base station configuration for a connected UE to perform sensing and report sensing data according to some embodiments;

[0031] Figure 11 is a flowchart of an idle or inactive UE sending sensing data to a base station according to some embodiments;

[0032] Figure 12 is a flowchart of a core network sending UE awareness authorization information to the RAN according to some embodiments;

[0033] Figure 13 is a signaling flowchart of a core network sending a perception request to the RAN according to some embodiments;

[0034] Figure 14 is a signaling flowchart of a core network configuration for UE to perform sensing and report sensing data via NAS signaling, according to some embodiments.

[0035] Figure 15 is a signaling flowchart of a core network configuration for UE to perform sensing and report sensing data through DP-RB and data tunnel according to some embodiments.

[0036] Figure 16 is a schematic diagram of a communication connection between network nodes according to some embodiments;

[0037] Figure 17 is a flowchart of a sensing task configuration and sensing data reporting between a RAN and a RAN or CN according to some embodiments;

[0038] Figure 18 is a flowchart of a core network initiating a sensing task and reporting sensing data via a CU to allow a RU or DU to perform a sensing task according to some embodiments.

[0039] Figure 19 is a flowchart of an AF initiating a RU, DU, or xNB to perform a sensing task and report sensing data according to some embodiments;

[0040] Figure 20 is a block diagram of a communication sensing device according to some embodiments;

[0041] Figure 21 is a block diagram of another communication sensing device according to some embodiments;

[0042] Figure 22 is a block diagram of another communication sensing device according to some embodiments;

[0043] Figure 23 is a block diagram of another communication sensing device according to some embodiments;

[0044] Figure 24 is a block diagram of another communication sensing device according to some embodiments. Detailed Implementation

[0045] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0046] It should be noted that in this disclosure, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts by way of example.

[0047] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0048] In the description of this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "more than one" means two or more.

[0049] As the number of digital data applications and services continues to surge, the demands and challenges on network resources and operators will continue to increase. Delivering the diverse network performance characteristics required for future services is one of the major technical challenges facing service providers today. Network performance requirements primarily include connection data rates, latency, quality of service (QoS), security, and availability, all of which vary from service to service. Therefore, future networks must support flexible resource allocation, providing customized connectivity for each different type of service, and enhancing the network's ability to meet future demands.

[0050] On the other hand, with the introduction of new scenarios such as communication sensing and AI, future 6G communication networks will incorporate a large amount of data generated and acquired by the 6G system on top of traditional user service data transmission. This data can come from terminals, base stations, edge servers, core networks, etc. Compared to 5G, 6G data exhibits more massive, polymorphic, temporal, and correlated characteristics. Furthermore, the industry generally proposes introducing a data plane into 6G networks to build a unified, reliable, complete, and universal data service framework at the architecture level, thereby improving network and application performance and maximizing data value.

[0051] In 5G networks, user equipment (UE) service data can be mapped to different protocol data unit sessions (PDU sessions) based on its associated data network (DN) and single-network slice selection assistance information (S-NSSAI). A PDU session can contain various data types, which can be mapped to individual service data flows according to service data flow (SDF) or traffic flow template (TFT) templates. In some embodiments, during downlink or uplink processes, the user plane function (UPF) or the UE maps these service data to different QoS flows according to the session management function (SMF) configuration. Between the base station and the UPF, a next-generation tunnel (NG tunnel) is established at the PDU session level for corresponding data transmission. Between the UE and the base station, uplink and downlink QoS flows are associated with the data radio bearer (DRB) according to the base station's access service level (AS) mapping rules. The base station can establish one or more DRBs for each QoS flow within a PDU session. At the network access service level (NAS level), QoS flow is the smallest granularity for QoS differentiation within a PDU session. Each QoS flow within a PDU session is identified by a QoS flow identifier (QFI) and is packaged, encapsulated, and transmitted by the next-generation-user-plane tunnel (NG-U tunnel). At the AS level, QoS guarantees are implemented between the UE and the base station at the DRB granularity. Once the mappings from the PDU session, NG-U tunnel, DRB, service data to QoS flow, and QoS flow to DRB are configured, the UE can transmit uplink and downlink service data with the DN.

[0052] In some embodiments, Figure 1 illustrates a 5G user plane data transmission architecture. As shown in Figure 1, the next-generation radio access network (NG-RAN) includes the UE and new radio (NR) nodes, the next-generation core network (NG-CN) includes the next-generation user plane (NG-UP), and the internet side includes peers (typically referring to another entity participating in communication at the same protocol layer). There are two end-to-end (E2E) services between the UE, NR node, NG-UP, and peers. Furthermore, multiple SDFs on the peer side (such as SDF_1, ..., SDF_m, SDF_m+1, ..., SDF_x, SDF_x+1, ..., SDF_n) can interact with user plane data through a PDU session between the UE, NR node, and NG-UP. In addition, the PDU session includes two radio bearers and an NG3 tunnel. The first radio bearer includes two QoS flows, and the second radio bearer includes one QoS flow.

[0053] Thus, future 6G communication networks will incorporate new scenarios such as communication sensing and AI into traditional user service data transmission. Communication sensing and AI will generate massive amounts of data, which can originate from terminals, base stations, edge servers, and the core network. This means that all network element nodes in the 6G network will have a need for data collection, analysis, and processing, and data transmission may occur between any network element nodes within the 6G network. Taking sensing as an example, sensing can include communication sensing measurement data and environmental or target object sensing data:

[0054] (1) Communication-aware measurement data: Communication-aware measurement data can be generated by the UE or the radio access network (RAN), or processed on the UE or RAN side. Communication-aware data generated on the UE side can be transmitted to the RAN for further processing, and vice versa.

[0055] (2) Environment or target object perception data: Environment or target object perception data can be generated by the UE or RAN. This perception data can be processed directly by the UE or RAN, or the UE can send the perception data to the RAN for processing. Alternatively, the UE or RAN can send the generated perception data to the core network for processing. In some embodiments, the UE or RAN can send the generated perception data to the application function (AF) for processing.

[0056] Therefore, the transmission of sensing data is no longer a simple end-to-end user plane data transmission between the UE and UPF. Instead, it needs to support distributed data transmission between any network elements and between any network element and a terminal. Furthermore, 6G networks need to process data based on its inherent connections, transforming and optimizing it to achieve the desired state for data analysis and intelligent applications. It's important to note that sensing encompasses various types. Taking the UE as an example, it can include sensing in various scenarios such as smartphone environmental sensing, vehicle-mounted sensors, industrial internet sensors, medical wearable devices, virtual reality (VR) and augmented reality (AR) devices, and agricultural sensor networks. From the base station's perspective, it can also include wireless signal sensing (e.g., RFID fingerprint recognition), environmental sensing (e.g., temperature, humidity, air pressure), pedestrian flow and mobility analysis, drone detection and tracking, vehicle traffic monitoring, weather and air quality detection, and various other sensing scenarios and tasks. These different sensing scenarios correspond to significantly different amounts of sensing data, and the latency and reliability requirements for sensing data transmission vary considerably.

[0057] To support the acquisition and processing of sensing data in future wireless communication networks, UEs, base stations (xNBs), core networks, or AFs or application servers (ASs) can all support sensing functions (SF) to perform sensing data acquisition, storage, and processing. Figures 2 and 3 illustrate the sensing data transmission scenarios on the UE side and the RAN side, respectively. As shown in Figures 2 and 3, for base stations, they can be divided into radio units (RUs), distributed units (DUs), and centralized units (CUs). Here, RUs, DUs, and / or CUs can all support SF functions. RUs and DUs can be co-located or deployed separately. UEs, RUs, DUs, and xNBs themselves can possess sensing functions, perform sensing operations, and acquire raw sensing data. AFs or ASs can acquire sensing data from third-party sensors. From the UE's perspective, the UE's sensing data can be processed directly on the UE side to obtain sensing results. Furthermore, the UE's sensing data can also be sent to xNBs, core network elements, or AFs or ASs for further processing. Similarly, sensing data from RU, DU, and / or xNB can also be processed at the base station to obtain sensing results. Furthermore, sensing data from RU, DU, and / or xNB can also be sent to core network elements or AF or AS for further processing.

[0058] In traditional wireless communication networks, control plane signaling between base stations and core network elements' access and mobility management functions (AMFs) is exchanged via next-generation application protocol (NGAP) signaling. Control signaling between base stations and other core network elements is also first sent to the AMF and then forwarded by the AMF to other core network elements. User plane data between base stations and the core network is transmitted between the base station and the UPF via an NG-U tunnel, and then sent by the UPF to the data network.

[0059] For sensing data transmission between the base station and the core network, a data plane function (DPF) can be introduced. This means that sensing data transmission between the base station and the core network can be uniformly sent from the base station to the DPF, which then forwards the corresponding data to the SF and / or other data plane-related core network elements such as the data analytics function (DAF). Figure 4 shows the data plane architecture between the base station and the core network, which is divided into the user plane, control plane, and data plane. Subsequently, the SF can perform sensing data analysis and obtain sensing results or intermediate results. The SF may need to send the sensing data to the DAF for AI or machine learning (ML)-based sensing model training and data analysis or model training. Besides the architecture shown in Figure 4 for sensing data transmission between the base station and core network elements, direct sensing data transmission between the base station and the SF can also be considered, or a scenario where the DPF and UPF are co-located, with the base station transmitting sensing data to the UPF, which then transmits it to the SF.

[0060] In summary, in order to support the acquisition and processing of sensing data in future wireless communication networks, how to flexibly configure network nodes to perform communication sensing and realize the efficient collection and transmission of sensing data on demand has become an urgent technical problem to be solved.

[0061] To address the aforementioned technical problems, this disclosure provides a communication sensing method applicable to communication sensing scenarios. The sensing node receives sensing configurations from upstream nodes and performs local configuration to achieve communication sensing. This allows for flexible configuration of network nodes to perform communication sensing, enabling efficient on-demand collection and transmission of sensing data.

[0062] In this embodiment of the disclosure, the network architecture of the mobile communication network (including but not limited to 2G, 3G, 4G, 5G and future mobile communication networks (such as the evolution of the fifth generation mobile communication technology (5G-A) and the sixth generation mobile communication technology (6G))) may include at least a first communication node and a second communication node, which may be referred to as the first node and the second node, respectively.

[0063] In some embodiments, FIG5 is a schematic diagram of a communication system according to some embodiments. As shown in FIG5, the communication system may include: a first node 501 and a second node 502.

[0064] Here, the second node 502 can send sensing configuration information to the first node 501 based on sensing requirements. Then, the first node 501 can receive the sensing configuration information sent by the second node 502, configure itself based on the sensing configuration information, and perform subsequent communication sensing.

[0065] It should be noted that, in this embodiment of the disclosure, the first node 501 and the second node 502 satisfy any one of the following:

[0066] When the first node 501 is a terminal (such as a UE), the second node 502 can be any one of the following: base station, CU, DU, SF network element, and AMF network element;

[0067] When the first node 501 is a base station, the second node 502 can be any one of the following: an adjacent base station, an SF network element, an AMF network element, or an AF network element.

[0068] When the first node 501 is an RU, the second node 502 can be any one of CU, DU, adjacent base station, SF network element, AMF network element, or AF network element;

[0069] When the first node 501 is DU, the second node 502 can be any one of CU, adjacent base station, SF network element, AMF network element, or AF network element.

[0070] In some embodiments, the second node 502 may initiate a query request for sensing capabilities to the first node 501 based on sensing requirements. Then, the first node 501 may respond to the query request by providing feedback on its own sensing capabilities to the second node 502. Subsequently, the second node 502 may send sensing configuration information to the first node 501 based on the sensing requirements and the first node 501's sensing capabilities. The first node 501 may then receive the sensing configuration information sent by the second node 502, configure itself based on the sensing configuration information, and perform subsequent communication sensing.

[0071] In some embodiments, when the first node 501 is a UE and the second node is a base station, the communication system may further include a third node 503, which is any one of an AMF network element, an AF network element, or an SF network element.

[0072] Here, the second node 502 can receive the perception authorization information from the first node 501 provided by the third node 503. Then, based on the perception requirements and the perception authorization information from the first node 501, the second node 502 can send perception configuration information to the first node 501. The first node 501 can then receive the perception configuration information sent by the second node 502, configure itself based on the perception configuration information, and perform subsequent communication perception.

[0073] It should be noted that, in the embodiments disclosed herein, the base station (BS) can be a base station or evolved Node B (eNB or eNodeB) in LTE, Long Term Evolution Advanced (LTEA), a base station device (gNB) in a 5G network, or a base station in a future communication system, etc. The base station can include various network-side devices such as macro base stations, micro base stations, femtocell base stations, wireless remote extensions, reconfigurable intelligent surfaces (RISS), routers, relay stations, transmission and reception points (TRPs), receivers, access points, and wireless fidelity (WIFI) devices. A base station can sometimes also be referred to as a reader / writer used for communication with terminals.

[0074] A terminal can be a device with wireless transceiver capabilities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on. This disclosure does not limit the application scenarios. A terminal may also be referred to as a user, user equipment (UE), artificial intelligence and internet of things (A-IoT) device, access terminal, UE unit, UE station, mobile station, mobile station, remote station, transmitter, remote terminal, mobile device, UE terminal, wireless communication device, UE agent, or UE device, etc., and this disclosure does not limit these terms.

[0075] It should be noted that Figure 5 is only an exemplary framework diagram. The number of devices included in Figure 5 and the names of each device are not limited. In addition to the devices shown in Figure 5, the communication system may also include other devices, such as core network devices.

[0076] This disclosure does not limit the application scenarios. The system architecture and business scenarios described in the embodiments of this disclosure are for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of this disclosure. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this disclosure are also applicable to similar technical problems.

[0077] Figure 6 is a flowchart of a communication sensing method according to some embodiments. As shown in Figure 6, the communication sensing method is applied to a first node, including S601.

[0078] In S601, the sensing configuration information sent by the second node is received.

[0079] Here, the perception configuration information may include at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

[0080] The following sections will introduce the configuration of the sensing task, the configuration of the sensing data reporting, and the configuration of the sensing data transmission, respectively, using numbers (I), (II), and (III).

[0081] (i) The perception task configuration may include at least one of the following (1)-(12):

[0082] (1) Perceptual identification;

[0083] (2) Segmentation identification;

[0084] (3) Perception type;

[0085] (4) Perceiving the target;

[0086] (5) Sensory area;

[0087] (6) Sensor type;

[0088] (7) Sensing trigger conditions;

[0089] (8) Perceiving frequency;

[0090] (9) Perceived duration;

[0091] (10) Public Land Mobile Network (PLMN) identifier;

[0092] (11) Perceive data processing needs;

[0093] (12) Perception data processing type.

[0094] For (3) above, the perception type may include at least one of the following: communication perception, environment perception, and target object perception.

[0095] For (4) above, the perception target includes the perception object or the perception event.

[0096] For (5) above, the sensing area is used to indicate the scope of sensing application, and the sensing area can be indicated by any of the following: the identifier of the tracking area (TA), the list of cell identifiers, the geographical location range, one or more RU identifiers, or one or more DU identifiers.

[0097] For (11) above, the sensing data processing requirement is used to indicate whether the sensing data is to be analyzed locally.

[0098] For (7) above, the perception triggering condition may include at least one of the following: entering a specified geographical area, leaving a specified geographical area, the perception time range, or the target network or environmental conditions.

[0099] It should be noted that the target network or environmental conditions may include at least one of the following:

[0100] Movement conditions;

[0101] Energy consumption conditions;

[0102] Air interface link quality;

[0103] Temperature conditions;

[0104] Humidity conditions;

[0105] Lighting conditions;

[0106] Noise conditions.

[0107] (ii) The configuration for reporting sensing data may include at least one of the following 1-6:

[0108] 1. Perceptual identification;

[0109] 2. Sensing data identification;

[0110] 3. Perceive data types;

[0111] 4. Triggering conditions for sensing data reporting;

[0112] 5. Perceive data format;

[0113] 6. Sensing data reporting address.

[0114] For the above 3, the perceptual data type may include at least one of the following:

[0115] Raw data;

[0116] Sensing preprocessed data;

[0117] Perceive and analyze data;

[0118] Perceive and predict information;

[0119] Prediction reliability;

[0120] Timestamp.

[0121] It should be noted that the raw data may include at least one of the following:

[0122] Signal strength;

[0123] Signal quality;

[0124] Time difference of arrival;

[0125] Angle of arrival;

[0126] Video stream.

[0127] Furthermore, the perception preprocessing data may include at least one of the following:

[0128] De-identified data;

[0129] Estimate distance;

[0130] Relative position;

[0131] Movement speed;

[0132] Direction of movement;

[0133] Position relative to a reference point;

[0134] Temperature, humidity, pressure, noise, or light.

[0135] In addition, the perception analysis data may include at least one of the following:

[0136] Detected target type;

[0137] Target quantity;

[0138] Target characteristics;

[0139] Abnormal changes in the environment.

[0140] For the above 4, the triggering condition for sensing data reporting may include at least one of the following:

[0141] Periodic reporting;

[0142] Event trigger reporting;

[0143] Real-time reporting;

[0144] Batch reporting;

[0145] Report all at once.

[0146] For the above 5, the perceptual data format may include at least one of the following:

[0147] Compression required;

[0148] Compression algorithm;

[0149] Is it encrypted?

[0150] Encryption algorithm;

[0151] Whether integrity protection is in place;

[0152] Integrity protection algorithm;

[0153] Internet Protocol (IP) indication or non-internet protocol (non-IP) indication;

[0154] Protocol identifier or protocol type.

[0155] For the above 6, the sensing data reporting address may include at least one of the following: target node address (i.e., the address of the destination node for data transmission), target node identifier (i.e., the identifier of the destination node for data transmission), and target port number (i.e., the port number of the destination port for data transmission).

[0156] (III) The configuration for sensing data transmission may include any of the following:

[0157] Signaling radio bearers (SRB) configuration;

[0158] Data plane radio bearers (DP-RB) configuration.

[0159] When the sensing data transmission configuration includes an SRB configuration, the sensing data transmission configuration may include SRB identification information.

[0160] Furthermore, when the sensing data transmission configuration includes a DP-RB configuration, the sensing data transmission configuration may include at least one of DP-RB addition, modification, or release; that is, the sensing data transmission configuration may include at least one of the following:

[0161] DP-RB identifier;

[0162] DP-RB associated sensing data identifiers;

[0163] Segmentation identification;

[0164] Configuration information for the packet data convergence protocol (PDCP) layer;

[0165] Should PDCP be rebuilt?

[0166] Should PDCP be restored?

[0167] Configuration information for the radio link control (RLC) layer;

[0168] The relevant configuration of logical channels;

[0169] Configuration information for the medium access control (MAC) layer.

[0170] In S602, configuration is performed based on the perception configuration information.

[0171] It should be noted that the process of configuring the first node based on the perception configuration information can be found in the relevant technical descriptions on configuration based on configuration information, and will not be elaborated here.

[0172] Understandably, sensing nodes receive sensing configurations from upstream nodes and perform local configurations to achieve communication sensing. In this way, communication sensing can be performed by flexibly configuring network nodes, enabling efficient on-demand collection and transmission of sensing data.

[0173] It should be noted that, in order to better adapt to the sensing requirements, the upstream node also needs to refer to the actual sensing capabilities of the sensing node when issuing sensing configurations to the sensing node, so as to allocate sensing configurations corresponding to its sensing capabilities.

[0174] In some embodiments, before the first node receives the perception configuration information sent by the second node (i.e., S601), the first node may send its own perception capability information to the second node, and then receive the perception configuration information sent by the second node based on the first node's perception capability information.

[0175] The perception capability information of the first node may include at least one of the following:

[0176] The types of sensors supported by the first node;

[0177] The first node's perception and processing capabilities;

[0178] The perception type of the first node;

[0179] The sensing area of ​​the first node;

[0180] The available time for sensing at the first node;

[0181] The first node's perception indication information.

[0182] It should be noted that the sensing indication information may include at least one of the following: sensing capability used to indicate whether a sensing task can be performed, and sensing function used to indicate whether sensing task organization and / or sensing data acquisition, forwarding, and processing are supported.

[0183] In some embodiments, after the first node configures itself according to the perception configuration information (i.e., S602), the first node may also send perception configuration completion information to the second node based on its actual configuration (such as the compatibility between its own perception capability and perception configuration).

[0184] The perception configuration completion message may include at least one of the following:

[0185] Acceptable perceptual identifiers;

[0186] Acceptable sensor data reporting identifier;

[0187] Acceptable encryption algorithms;

[0188] Acceptable integrity protection algorithms;

[0189] Acceptable compression algorithms;

[0190] Acceptable protocol types;

[0191] Perceive the data source address.

[0192] It should be noted that the source data address can include at least one of the following: source node address (i.e., the address of the originating node of the data transmission), source node identifier (i.e., the identifier of the originating node of the data transmission), and source port number (i.e., the port number of the originating port of the data transmission).

[0193] In other words, after the sensing node receives the sensing configuration sent by the upstream node, the sensing node can also determine whether it supports the sensing task indicated by the sensing configuration, determine the compatibility between its own sensing capabilities and the sensing configuration, and then feed back the compatibility result to the upstream node through the configuration response message, so as to inform the upstream node of its own configuration status for the sensing configuration, so that the upstream node can understand the completion status of the sensing requirements, and flexibly update the sensing configuration of the sensing node based on the actual configuration status of the sensing node in the subsequent process.

[0194] In some embodiments, the first node and the second node may satisfy any one of the following (a)-(d):

[0195] (a) When the first node is a UE, the second node can be any one of the following: base station, CU, DU, SF network element, AMF network element;

[0196] (b) If the first node is a base station, the second node can be any one of the following: an adjacent base station, an SF network element, an AMF network element, or an AF network element;

[0197] (c) When the first node is RU, the second node can be any one of CU, DU, adjacent base station, SF network element, AMF network element, or AF network element;

[0198] (d) When the first node is DU, the second node can be any one of CU, adjacent base station, SF network element, AMF network element, or AF network element.

[0199] In other words, in different communication scenarios, the system can adapt the initiating and executing nodes of the communication sensing required by the scenario to meet the collection and interaction of different combinations of sensing data and synchronize the changes in the communication scenario.

[0200] In this embodiment of the disclosure, when the first node is a UE, the aforementioned perception configuration information can be carried in a radio resource control (RRC) reconfiguration message, or the perception configuration information can be carried in system information (i.e., the perception configuration information is sent to the first node by the second node via broadcast).

[0201] In one implementation, if the first node is an idle or inactive (i.e., disconnected) UE, during the process of the first node receiving the sensing configuration information sent by the second node (i.e., S601), the first node can first receive the sensing task configuration sent by the second node and determine whether it can execute the sensing task corresponding to the sensing task configuration. Then, if the first node can execute the sensing task corresponding to the sensing task configuration, it can enter a connected state and send RRC signaling to the second node.

[0202] RRC signaling may include at least one of the following: perception identifier, fragmentation identifier, perception intention indication.

[0203] In other words, the UE can receive the perception task configuration sent by the upstream node in the non-connected state, determine whether its own perception capability can support the execution of the perception task, and switch from the non-connected state to the connected state if the perception task can be executed, and report its own intention to execute the perception task to the upstream node.

[0204] In some embodiments, the second node may receive RRC signaling sent by the connected UE and determine whether the connected UE needs to participate in the required communication awareness.

[0205] If the second node determines that the connected UE does not need to participate in communication awareness, then no further awareness configuration needs to be performed.

[0206] If the second node determines that the connected UE needs to participate in communication sensing, the second node can then send the sensing data reporting configuration and sensing data transmission configuration to the first node in sequence, and then send the completed sensing configuration to the first node.

[0207] This provides more references for the upstream nodes in the process of configuring perception to perception nodes, thereby improving the accuracy of perception configuration.

[0208] In another implementation, if the first node is an idle or inactive (i.e., disconnected) UE, during the process of the first node receiving the sensing configuration information sent by the second node (i.e., S601), the first node can first receive the sensing task configuration sent by the second node and determine whether its own sensing capabilities can support the execution of the sensing task. Then, if the first node can execute the sensing task corresponding to the sensing task configuration, it can configure itself according to the sensing task configuration in the disconnected state and determine whether the sensing data corresponding to the sensing task has been collected. Next, if the first node has collected the sensing data corresponding to the sensing task, it can enter the connected state and send RRC signaling to the second node.

[0209] RRC signaling may include at least one of the following: sensing data indication, sensing identifier, sensing data identifier, fragment identifier.

[0210] In other words, the first node can enter the connected state and send RRC signaling to the second node when it has configured the corresponding sensing task for the sensing task and collected the sensing data corresponding to the sensing task.

[0211] It should be noted that in the above embodiments, the sensing data is collected after the first node enters the connected state, and the incentive condition for the first node to trigger RRC signaling reporting is only whether its own sensing capabilities are suitable for the needs of the sensing task. However, in this embodiment, the first node can collect sensing data based on the non-connected state before entering the connected state, and the incentive condition for the first node to trigger RRC signaling reporting not only considers whether its own sensing capabilities are suitable for the needs of the sensing task, but also whether sensing data corresponding to the sensing task has been collected.

[0212] In this way, compared with the above embodiments, the UE can report its own adaptation to the sensing task and the relevant information of the collected sensing data (such as sensing data identifier) ​​to the upstream node. This allows the upstream node to verify the UE's ability to participate in communication sensing and also to verify the UE's collection effect of sensing data, so as to make subsequent configuration arrangements for the communication sensing of all UEs for sensing needs.

[0213] In another implementation, if the first node is an idle or inactive (i.e., disconnected) UE, during the process of the first node receiving the sensing configuration information sent by the second node (i.e., S601), the first node can first receive the sensing task configuration and sensing data reporting configuration sent by the second node, and determine whether its own sensing capability can support the execution of the sensing task. Then, if the first node can execute the sensing task corresponding to the sensing task configuration, it can configure itself according to the sensing task configuration in the disconnected state, and determine whether the sensing data corresponding to the sensing task has been collected. Next, if the first node has collected the sensing data corresponding to the sensing task, it can enter the connected state and send RRC signaling to the second node.

[0214] RRC signaling may include at least one of the following: sensing data indication, sensing identifier, sensing data identifier, fragment identifier.

[0215] In some embodiments, the first node can also report the perception data corresponding to the perception task it has collected to the second node based on the perception data reporting configuration.

[0216] In other words, when the UE reports its adaptation to the sensing task and the relevant information of the collected sensing data to the upstream node, the UE can simultaneously report the collected sensing data to the upstream node based on the reporting configuration. This ensures that the upstream node will also receive the sensing data corresponding to the sensing task during the signaling interaction period if the upstream node subsequently determines to allow the UE to participate in communication sensing.

[0217] It should be noted that in the above embodiments, the RRC signaling can be any of the following: RRC connection establishment request message, RRC connection establishment completion message, or new RRC signaling.

[0218] This disclosure also provides a communication sensing method applied to a second node, as shown in FIG7. The communication sensing method may include S701.

[0219] In S701, perception configuration information is sent to the first node.

[0220] The perception configuration information may include at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

[0221] It should be noted that for the description of the perception task configuration, perception data reporting configuration, and perception data transmission configuration, please refer to the description of the perception task configuration, perception data reporting configuration, and perception data transmission configuration in the embodiment of S601 above, which will not be repeated here.

[0222] In this embodiment of the disclosure, the second node can send perception configuration information to the first node based on perception requirements.

[0223] In one implementation, when the second node is an AF network element, during the process of the second node sending sensing configuration information to the first node (i.e., S701), the second node can send sensing configuration information to the first node through the first network element.

[0224] Here, the first network element may include a network exposure function (NEF) network element or a radio access network exposure function (RAN exposure function (REF) network element.

[0225] It should be noted that as the demand for communication sensing increases, the need for sensing data at different network node locations also increases, enabling each network node to acquire its own communication sensing capabilities. For example, some base stations in wireless access networks possess communication sensing capabilities.

[0226] In some embodiments, when the first node is a UE and the second node is a base station, while the second node sends sensing configuration information to the first node (i.e., S701), the second node can determine whether it has sensing capabilities. After determining that it has sensing capabilities, it can determine whether it can execute the sensing task configuration corresponding to the sensing task (i.e., whether its sensing capabilities meet the sensing requirements). Subsequently, if the second node determines that it can execute the sensing task configuration corresponding to the sensing task, the second node can configure it according to the sensing configuration information.

[0227] In other words, if an upstream node possesses the sensing capabilities to meet sensing requirements, it can not only organize sensing nodes to conduct communication sensing, but also act as a sensing node itself for communication sensing. This enriches the data sources for sensing data.

[0228] In some embodiments, before the second node sends the perception configuration information to the first node (i.e., S701), the second node may receive the first node's perception capability information sent by the first node. Subsequently, during the process of the second node sending the perception configuration information to the first node, the second node may send the perception configuration information to the first node based on the perception requirements and the first node's perception capability information.

[0229] In other words, during the process of upstream nodes issuing sensing configurations to sensing nodes, it is necessary to consider not only the sensing requirements but also the actual sensing capabilities of the sensing nodes to ensure that the issued sensing configurations are compatible with the sensing nodes.

[0230] In other embodiments, during the process of the second node sending perception configuration information to the first node (i.e., S701), the second node may receive perception request information sent by the third node and send perception configuration information to the first node according to the perception request information.

[0231] Here, the perception request information may include at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

[0232] In other words, upstream nodes can send perception configurations to intermediate nodes, which in turn can organize and arrange perception nodes based on these configurations.

[0233] In one implementation, after the second node receives the perception request information sent by the third node, the second node can send perception response information to the third node.

[0234] Here, the perception response information may include at least one of the following: acceptable perception identifier, unacceptable perception identifier, and cause value.

[0235] In other words, after the upstream node sends the sensing configuration to the intermediate node, the intermediate node can report its own adaptation to communication sensing and / or the organization and arrangement of sensing nodes to the upstream node, so that the upstream node can understand the execution of communication sensing.

[0236] It should be noted that in the above embodiments, when the first node is a UE and the second node is a base station, the third node can be any one of the following: an adjacent base station, an SF network element, an AMF network element, or an AF network element.

[0237] In some embodiments, when the first node is a UE, the second node is a base station, and the third node is an adjacent base station, the second node can query whether the third node is a historical access node of the first node when the first node accesses the second node. If the third node is a historical access node of the first node, the second node can receive a handover preparation message sent by the third node. The handover preparation message includes the perception authorization information of the first node, thereby obtaining the perception authorization information of the first node.

[0238] In other words, when a sensing node undergoes an access switch due to movement, the sensing authorization information of the sensing node is synchronized from the historical access point to the new access point.

[0239] This disclosure also provides a communication sensing method applied to a second node, as shown in FIG8. The communication sensing method may include S801 and S802.

[0240] In S801, the perception authorization information of the first node is received by the third node.

[0241] In S802, based on the perception authorization information of the first node, it is determined whether the first node is authorized to perform perception.

[0242] Here, the perceived authorization information may include at least one of the following:

[0243] First node address or identifier;

[0244] Group identifier;

[0245] Perception type;

[0246] Perceptual identifiers;

[0247] Perceive the target;

[0248] Authorization instructions;

[0249] Sensing area;

[0250] Available time;

[0251] Segmentation identification;

[0252] PLMN information.

[0253] In one implementation, the second node can send perception configuration information to the first node based on perception requirements and the first node's perception authorization information, provided that the first node has authorized the execution of perception.

[0254] In some embodiments, if the perception authorization information (such as authorization indication) of the first node changes, the second node may send perception configuration update indication information to the first node.

[0255] Here, the awareness configuration update indication information may include at least one of the following: release indication, suspend indication, and resume indication.

[0256] It should be noted that the release instruction is used to release the corresponding perception configuration, the suspend instruction is used to pause the corresponding perception and / or perception reporting, and the resume instruction is used to resume the corresponding perception and / or perception reporting.

[0257] In other words, when upstream nodes distribute sensing configurations to sensing nodes, they need to consider not only the sensing requirements but also the sensing capabilities authorized for the sensing nodes to ensure that the distributed sensing configurations are compatible with the sensing nodes. Furthermore, if the sensing authorization of a sensing node changes, the upstream node can promptly update the sensing configuration within the sensing node.

[0258] In some embodiments, during the process of the second node sending perception configuration information to the first node, the second node may receive its own perception capability information reported by the first node, and receive perception authorization information for the first node issued by the third node. Then, the second node may issue perception configuration information to the first node based on perception requirements, the first node's perception capability information, and the first node's perception authorization information.

[0259] In other words, during the process of upstream nodes issuing sensing configurations to sensing nodes, not only sensing requirements can be referenced, but also the actual sensing capabilities of the sensing nodes and the sensing capabilities authorized to the sensing nodes can be referenced to ensure that the issued sensing configurations are compatible with the sensing nodes.

[0260] This disclosure also provides a communication sensing method applied to a third node, as shown in FIG9. The communication sensing method may include S901 to S902.

[0261] In S901, a perception request message is sent to one or more second nodes.

[0262] In one implementation, the third node can determine the sensing range based on sensing needs and send sensing request information to one or more second nodes within the sensing range.

[0263] Here, the third node can receive perception needs from users or customers and determine the perception range based on the content information described by the perception needs.

[0264] It should be noted that the perception request information may include at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

[0265] In S902, sensing response information sent by one or more second nodes is received.

[0266] Here, the perception response information may include at least one of the following: acceptable perception identifier, unacceptable perception identifier, and cause value.

[0267] In some embodiments, when the second node is a base station and the third node is an SF network element, during the process of the third node sending perception request information to one or more second nodes (i.e., S901), the third node may send a data tunnel establishment / modification request information between the DPF network element and the second node to the data plane function (DPF) network element.

[0268] Here, the data tunnel establishment or modification request information may include at least one of the following: perception identifier, fragment identifier, perception data identifier, UE IP address, UE perception data port number, data flow service quality (QoS) information, and the data tunnel establishment or modification request information is used to indicate the configuration of the data tunnel between the second node and the DPF network element.

[0269] Subsequently, the third node can receive data tunnel establishment or modification response information sent by the DPF network element. The data tunnel establishment or modification response information may include at least one of the following: perception identifier, fragment identifier, perception data identifier, IP address of the DPF network element, and tunnel endpoint identifier (TEID) of the DPF network element.

[0270] It should be noted that, in the above embodiments, the perception request information may also include: fragment identifier, perception data identifier, IP address of DPF network element, and TEID of DPF network element.

[0271] The sensing response information may also include: fragment identifier, sensing data identifier, IP address of the second node, and TEID of the second node.

[0272] In the above embodiments, the DPF network element can be co-located with the UPF network element, or the function of the DPF network element can be included in the function of the UPF network element, that is, the UPF network element can have the function of the DPF network element.

[0273] The communication sensing method provided in this disclosure will be described below with reference to the embodiments.

[0274] Example 1: This embodiment of the disclosure provides a signaling flow for configuring a connected UE to perform sensing and report sensing data, as shown in Figure 10, including:

[0275] Step 1: A UE with sensing capability can send sensing capability information (i.e., sensing capability) to the base station.

[0276] The perception capability information includes at least one of the following: supported sensor types (such as global positioning system (GPS), accelerometer, camera, radar, etc.), perception processing capabilities, perception type, perception area, available time, etc.

[0277] Step 2: The base station selects candidate UEs to participate in the sensing task based on the UE's capabilities and current sensing requirements (i.e., selects the candidate UEs for the sensing task).

[0278] Step 3: If the UE is selected to participate in a sensing task, the base station sends sensing configuration information (i.e., sensing configuration) to the UE. Sensing configuration information can be sent via RRC Reconfiguration messages. The sensing configuration information may include sensing task information.

[0279] Here, the sensing task information includes at least one of the following: sensing identifier, segment identifier, sensing type, sensing target, sensing area, sensor type, sensing trigger condition, sensing frequency, sensing duration, whether data processing is performed, and sensing data processing type.

[0280] The perception type includes at least one of the following: communication perception, environmental perception, target object perception, etc.

[0281] Perception targets include specific types of perceived objects or perceived events.

[0282] The sensing area refers to the scope of sensing application, which can be indicated by the tracking area (TA), cell list, or geographical location range.

[0283] Whether data processing is required refers to whether preliminary analysis needs to be performed on the UE.

[0284] The triggering conditions for sensing include at least one of the following: entering a designated geographical area, leaving a designated geographical area, a sensing time period (such as a specific date, peak time period, or evening time period), or specific network or environmental conditions. The geographical area can be indicated by geographic location information or by a list of cell identifiers. Specific network or environmental conditions can include one of the following: UE mobility conditions, UE energy conditions, air interface link quality, temperature conditions, humidity conditions, lighting conditions, noise conditions, etc. For various network or environmental conditions, the network can configure corresponding thresholds for the UE to determine whether the corresponding conditions are met, thereby initiating sensing.

[0285] In addition, the perception configuration information may also include perception data reporting information.

[0286] The information reported by the sensor data includes at least one of the following: sensor identifier, sensor data identifier, sensor data type, sensor data reporting trigger condition, sensor data format, and sensor data address.

[0287] The data type of perception includes at least one of the following: raw data, perception preprocessed data, perception analysis data, perception prediction information, prediction confidence, and timestamp.

[0288] Raw data may also include: signal strength, signal quality, time difference of arrival, angle of arrival, or video stream, etc.

[0289] Sensing preprocessing data may include the following information: desensitized data, estimated distance, relative position, movement speed, movement direction, position relative to a reference point, and / or temperature / humidity / pressure / noise / light, etc.

[0290] Perception analysis data may also include the following information: the type of target detected, the number of targets, the characteristics of the targets, and abnormal changes in the environment.

[0291] A timestamp indicates the precise time of perception or detection.

[0292] The triggering conditions for sensing data reporting can include at least one of the following: periodic reporting, event-triggered reporting, real-time reporting, batch reporting, and one-time reporting.

[0293] For periodic reporting, the information reported by the sensing data can also include the sensing data reporting cycle.

[0294] For event-triggered reporting, the information reported by the perception data can also include the reporting trigger event and the corresponding judgment threshold.

[0295] Real-time reporting refers to the UE continuously reporting perceived data in the form of a data stream.

[0296] Batch reporting refers to reporting a certain amount of data all at once after it has been accumulated. Corresponding to batch reporting, the data reporting information can also include a data volume threshold.

[0297] For one-time reporting, the UE reports the sensed data to the base station all at once. In this case, the UE can send the sensed data to the base station again after the base station sends another one-time reporting instruction.

[0298] The perceived data format includes at least one of the following: whether it is compressed, compression algorithm, whether it is encrypted, encryption algorithm, whether it is integrity protected, integrity protection algorithm, IP or non-IP indication, protocol identifier or protocol type.

[0299] The sensing data address may include at least one of the following: target node, target port number. The target node may be a target IP address or a target node identifier. In the embodiments of this disclosure, the target node may be the IP address of a base station or a base station identifier.

[0300] In some embodiments, the perception configuration information may also include a perception data reporting transmission channel configuration. This transmission channel can be used for RRC signaling or DP-RB transmission. If RRC signaling is used, the base station can configure the corresponding SRBx (x = 2, 3, 4, 5...n) for the UE. The perception configuration information may include the SRB identifier information corresponding to the perception data reporting. If DP-RB transmission is used, the perception configuration information may include DP-RB configuration information.

[0301] DP-RB configuration information may include at least one of the following: DP-RB addition, DP-RB modification, DP-RB release. DP-RB addition or modification information may include at least one of the following: DP-RB identifier, associated sensing data identifier, fragment identifier, PDCP-related configuration, whether to rebuild PDCP, whether to restore PDCP, RLC-related configuration, logical channel-related configuration, and MAC-related configuration. PDCP-related configurations may include at least one of the following: whether out-of-order delivery is allowed, discard timer, PDCP sequence number (SN) size, t-reordering timer, whether header compression is allowed, and whether integrity is guaranteed. RLC-related configurations may include at least one of the following: acknowledged mode (AM), unacknowledged mode (UM), sequence number length (SN length), t-reassembly, maximum retransmission threshold (maxRetxThreshold), and T-poll retransmit. Logical channel configurations may include: priority, prioritized bit rate (PBR), bucket size duration (BSD), logical channel group identifier (LCGID), service request identifier (SRID), allowed subcarrier spacing (allowed SCS), and allowed configured grant. The DP-RB release information includes one or more DP-RB identifiers that need to be released.

[0302] Step 4: After receiving the sensing configuration information from the base station, the UE can send a sensing configuration complete message (i.e., sensing configuration complete) to the base station. The sensing configuration complete message may contain at least one of the following: accepted sensing identifier, accepted sensing data reporting identifier, accepted encryption algorithm, accepted integrity algorithm, accepted compression algorithm, accepted protocol type, and sensing data source address. The sensing data source address includes at least one of the following: source node and source port number. The source node can be a source IP address or a source node identifier.

[0303] Step 5: After receiving the sensing configuration information from the base station, the UE performs the sensing-related configuration (i.e., performs sensing).

[0304] In some embodiments, the UE's perception-related configuration includes the following operations:

[0305] (1) If the perception configuration information contains DP-RB configuration, the UE performs the corresponding DP-RB addition, modification or release operation;

[0306] (2) If the perception configuration information contains perception task information, the UE performs the corresponding perception operation according to the perception configuration and obtains perception data;

[0307] (3) If the perception configuration information includes perception data reporting information, then when the perception data reporting condition is triggered, the perception data is assembled according to the perception data format requirements and transmitted through DP-RB or SRBx.

[0308] Step 6: For the transmission of sensing data, if the sensing configuration information contains the SRBx associated with the sensing data, the UE can encapsulate the sensing data corresponding to the sensing task into an IP packet or non-IP packet and send it to the base station (i.e., sensing report) through the sensing container in the SRBx.

[0309] If the UE receives the DP-RB configuration sent by the base station, and the DP-RB configuration contains the corresponding sensing data identifier, the UE can transmit the sensing data corresponding to the matched sensing data identifier through the DP-RB.

[0310] In some embodiments, the UE can encapsulate the sensing data into corresponding application protocol data. If it is an IP packet, the source or destination IP address and source or destination port number of the IP packet can be set according to the corresponding sensing data reporting address and sensing data source address information exchanged between the UE and the base station. In addition, the UE can perform compression, encryption, and / or integrity protection processing at the application layer or data plane adaptation protocol (DPAP) sublayer according to the format requirements of the sensing data reporting.

[0311] In some embodiments, the UE may encapsulate a DPAP sub-header, which may carry at least one of the following fields: QoS indication, data type indication, data identifier, source node identifier, one or more target node identifiers, source port number, target port number, protocol identifier, and timestamp. The QoS indication may be at least one of the following: data quality index (DQI) and data identifier. For non-IP data plane data, the target node of the data plane data can identify the corresponding application based on the target port number, thereby delivering the data to the appropriate application. Similarly, the source port number of the data's source node identifies the application at the source. For non-IP data plane data, considering that the application layer may have different protocol types, the protocol identifier in the DPAP subheader can be used to indicate the protocol type. For example, the protocol identifier can indicate at least one of the following protocols: Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), gRPC (a type of remote procedure call), Web Real-Time Communication (WebRTC), Message Queuing Telemetry Transport (MQTT), WebSocket (a full-duplex communication protocol), and Constrained Application Protocol (CoAP). The timestamp can be used to indicate at least one of the following information: data generation time, data latency budget, etc. After the UE encapsulates the DPAP subheader, it delivers the DPAP protocol data unit (PDU) to the PDCP and RLC entities of the DP-RB for subsequent processing, data PDCP / RLC / MAC encapsulation, and finally sends it to the base station through the air interface.

[0312] Example 2: This example describes the process by which an idle or inactive UE sends sensing data to the base station, as shown in Figure 11, including:

[0313] Step 1: The base station can send sensing task-related information via broadcast (i.e., broadcast sensing task).

[0314] In some embodiments, the base station can send sensing task information through system information.

[0315] In some embodiments, the sensing task includes at least one of the following information: sensing identifier, segment identifier, sensing type, sensing target, sensor type, sensing area, sensing trigger condition, sensing frequency, sensing duration, segment identifier, PLMN identifier, whether data processing is performed, sensing data processing type, etc.

[0316] Step 2: After receiving the sensing task information, the UE in the RRC_IDLE or RRC_INACTIVE state determines whether it has the capability and / or willingness to perform the sensing task. If the UE decides to perform the sensing task, it performs the corresponding sensing operation according to the sensing task information and obtains sensing data (i.e., performs sensing).

[0317] Step 3: When the UE has reportable sensing data, the UE initiates entry into the connected state (i.e., Radio Resource Control (RRC) connection setup). The UE may carry at least one of the following information in the RRC connection establishment request message and / or RRC connection establishment completion message: sensing data indication, sensing identifier, sensing data identifier, fragment identifier, etc.

[0318] Step 4: After completing the RRC connection establishment, the UE can also send a sensing data indication, sensing identifier and / or sensing data identifier information to the base station through new RRC signaling, as shown in Figure 11.

[0319] Step 5: After receiving the sensing data indication from the UE, the base station can send sensing configuration information to the UE. The sensing configuration information may include sensing report configuration and / or sensing data reporting transmission channel configuration. The information included in the sensing data reporting configuration and sensing data reporting transmission channel configuration can be found in Example 1.

[0320] After receiving the sensing configuration information from the base station, the UE performs sensing-related configuration. In some embodiments, the UE's sensing-related configuration includes the following operations: 1) If the sensing-related configuration information contains DP-RB configuration, the UE performs DP-RB addition, modification, or release operations accordingly; 2) If the sensing-related configuration information contains sensing data reporting information, when the sensing data reporting condition is triggered, the UE assembles the sensing data according to the sensing data format requirements and transmits the sensing data through DP-RB or SRBx.

[0321] Step Six: After receiving the sensing configuration information from the base station, the UE may optionally send a sensing configuration completion message (i.e., sensing report configuration complete) to the base station. The sensing configuration completion message may contain at least one of the following: accepted sensing identifier, accepted sensing data reporting identifier, accepted encryption algorithm, accepted integrity algorithm, accepted compression algorithm, accepted protocol type, and sensing data source address. The sensing data source address includes at least one of the following: source node and source port number. The source node may be a source IP address or a source node identifier.

[0322] Step 7: For the transmission of sensing data, if the transmission channel configuration information reported by the sensing data includes an SRBx associated with the sensing data, the UE can encapsulate the sensing data corresponding to the sensing task into an IP packet or non-IP packet and send it to the base station through the sensing container in the SRBx. If the UE receives the DP-RB configuration sent by the base station, and the DP-RB configuration contains the corresponding sensing data identifier, the UE can transmit the sensing data corresponding to the matched sensing data identifier through the DP-RB.

[0323] In addition to the process shown in Figure 11, the base station can also send sensing data reporting information via system information broadcast. In this case, the UE can organize the sensing data to be reported while in RRC_IDLE or RRC_INACTIVE state and determine whether the triggering conditions for sensing data reporting are met. When the triggering conditions for sensing data reporting are met, the UE initiates entry into the connected state.

[0324] Furthermore, a UE in the RRC_IDLE or RRC_INACTIVE state can determine whether it has the capability and / or willingness to perform the sensing task after receiving sensing task-related information broadcast by the base station. If the UE determines that it can perform the sensing task, it initiates entry into the connected state. In some embodiments, the UE may carry at least one of the following information in the RRC connection establishment request message and / or RRC connection establishment completion message: sensing identifier, sensing task intention indication, etc. Additionally, after completing the RRC connection establishment, the UE may also send the sensing task intention indication and / or sensing identifier information to the base station via new RRC signaling.

[0325] After receiving this information, the base station can send sensing data reporting information and / or sensing data reporting transmission channel configuration to the UE. Upon receiving this information, the UE performs sensing tasks, prepares sensing data, and sends the sensing data to the base station using the sensing data reporting transmission channel.

[0326] Example 3: This example describes the process by which the core network sends UE awareness authorization information to the RAN, as shown in Figure 12, including:

[0327] Step 1: For some sensing tasks, only specific UEs or user groups are eligible to perform them. To enable the base station to better control the UE's sensing behavior, core network elements (such as the AMF) can send sensing authorized information to the base station. Sensing authorized information can be sent via UE-specific signaling or non-UE-specific signaling.

[0328] The perception authorization information may include at least one of the following: UE identifier, group identifier, perception type, perception identifier, perception target, authorization instruction, perception area, perception time, fragmentation information, and PLMN information.

[0329] The perception type includes at least one of the following: communication perception, environmental perception, target object perception, etc.

[0330] Perception targets include specific types of perceived objects or perceived events.

[0331] The sensing area refers to the scope of application of the sensing task, which can be indicated by TA, a list of cells, or a geographical location range.

[0332] The sensing time includes at least one of the following: the time range during which the UE can sense, and the time range during which the UE cannot sense.

[0333] The authorization instruction may include at least one of the following: perception can be performed, perception cannot be performed.

[0334] After receiving the perception authorization information from the core network, the base station will consider the perception authorization information when selecting a UE to perform a specific perception task. For example, it will select a UE or user group that is authorized to perform the corresponding perception task and configure the corresponding UE to perform the perception task.

[0335] It is important to note that the UE's perception authorization information and / or user group's perception authorization information may change. In this case, the AMF can send updated perception authorization information to the RAN. If the base station receives a change in the UE's perception authorization information from "permission to perform perception" to "permission to perform perception," the base station can send perception configuration information to the UE, including information on the release, modification, suspension, or resumption of perception-related configurations.

[0336] The release, suspension, or resumption information for perception-related configurations may include at least one of the following: release indication, suspension indication, resumption indication, perception identifier, etc. If the UE receives perception-related configuration release information, the UE releases the corresponding perception-related configuration. If the UE receives a perception-related configuration suspension indication, the UE suspends the corresponding perception and / or perception data reporting. If the UE receives a perception-related configuration resumption indication, the UE resumes the corresponding perception and / or perception data reporting.

[0337] Furthermore, when a UE hands over, the source base station sends perception authorization information to the target base station. In some embodiments, the source base station can send the UE's perception authorization information to the target base station via a handover preparation message. Upon receiving this information, the target base station will consider the perception authorization information when selecting a UE to perform a specific perception task.

[0338] Example 4: This example describes the signaling process for the core network to send a sensing request to the RAN.

[0339] Besides sensing tasks initiated by base stations, sensing tasks may also be initiated by the core network (such as AMF / SF / AF). For example, when the SF in the core network receives a sensing request from a user or customer, the SF can initiate a sensing request to the base station. Alternatively, the SF in the core network can send sensing request information to the AMF, which then determines the relevant base stations based on the sensing area information and sends sensing request information to the relevant base stations. As shown in Figure 13, this includes:

[0340] Step 1: The base station can send sensing indication information (i.e., sensing capability) to the core network.

[0341] The sensing indication information includes at least one of the following: the sensing capability of the base station, and the base station supports sensing functions.

[0342] The sensing capabilities of a base station are used to indicate whether the base station can perform sensing tasks. In this case, the base station's sensing capabilities may include at least one of the following: supported sensor types (e.g., GPS, accelerometer, camera, radar, etc.), sensing processing capabilities, sensing type, sensing area, and sensing availability time. In some embodiments, the sensing type includes at least one of the following: communication sensing, environmental sensing, target object sensing, etc. The sensing target includes a specific type of sensing object or sensing event. The sensing area refers to the applicable sensing range, which can be indicated by a TA (Transmission Area), a cell list, or a geographic coordinate range. The sensing availability time includes at least one of the following: the time range during which the base station can perform sensing, and the time range during which the base station cannot perform sensing.

[0343] The base station supports sensing functions to indicate that the base station supports functions such as sensing task organization and / or sensing data collection, forwarding and processing, but the base station may not be able to perform sensing on its own.

[0344] Step 2: The core network can determine the base stations in the relevant sensing areas based on the sensing needs of users or customers and the sensing indication information of the base stations, and send sensing requests to these base stations.

[0345] A sensing request may include sensing task information, which includes at least one of the following: sensing identifier, segment identifier, sensing type, sensing target, sensing area, sensor type, sensing trigger condition, sensing frequency, sensing duration, whether data processing is performed, and sensing data processing type. The content of information such as sensing type, sensing target, sensing area, sensor type, sensing trigger condition, sensing frequency, sensing duration, whether data processing is performed, and sensing data processing type is similar to the relevant description in Embodiment 1.

[0346] Furthermore, the perception request information may also include perception data reporting information, which includes at least one of the following: perception identifier, perception data identifier, perception data type, perception data reporting trigger condition, perception data format, and perception data address. The content of the perception data type, perception data reporting trigger condition, and perception data format is similar to that described in Embodiment 1. The perception data address may also include at least one of the following: target node and target port number. The target node is either the IP address of the SF or DPF or the identifier of the SF or DPF node.

[0347] Step 3: After receiving the sensing request from the AMF or SF, the base station determines whether it can accept the sensing task and sends a sensing response to the AMF or SF. The sensing response may contain at least one of the following information: an acceptable sensing identifier, an unacceptable sensing identifier, and a reason value.

[0348] The base station can determine whether the sensing task is performed by the base station itself, the UE, or a combination of both. If the sensing task involves the UE, the base station can initiate the procedure corresponding to Implementation Example 1, select one or more UEs to participate in the sensing task, and send sensing configuration information to the UEs.

[0349] Example 5: This example describes the signaling flow for configuring the UE in the core network to perform sensing and reporting sensing data through network access service (NAS) signaling, as shown in Figure 14, including:

[0350] Step 1: The UE with sensing capability sends sensing capability information (i.e., sensing capability) to the SF in the core network. Alternatively, the UE can also send sensing capability information to the AMF in the core network, which then forwards the UE's sensing capability information to the SF. The sensing capability information includes at least one of the following: supported sensor types (e.g., GPS, accelerometer, camera, radar, etc.), sensing processing capabilities, sensing type, sensing area, and available time.

[0351] Step 2: The SF of the core network receives the sensing request from the user or customer. The SF can decide which candidate UEs to participate in the sensing task based on the UE's capabilities and sensing requirements (i.e., select the candidate UEs for sensing task).

[0352] Step 3: The SF can initiate a sensing request to the UE. Alternatively, the SF in the core network can send sensing request information to the UE through the AMF.

[0353] In some embodiments, the perception request information sent by the AMF or SF to the UE can be transmitted via NAS signaling. The perception request information includes perception task information. The perception task information includes at least one of the following: perception identifier, segment identifier, perception type, perception target, perception area, sensor type, perception trigger condition, perception frequency, perception duration, whether data processing is performed, and perception data processing type. The perception target, perception area, sensor type, perception trigger condition, perception frequency, perception duration, whether data processing is performed, and perception data processing type are described similarly to those in Embodiment 1.

[0354] Furthermore, the perception request information may also include perception data reporting information, which includes at least one of the following: perception identifier, perception data identifier, perception data type, perception data reporting trigger condition, perception data format, and perception data address. The content of the perception data type, perception data reporting trigger condition, perception data format, and perception data address is similar to that described in Embodiment 1. The perception data address may also include at least one of the following: target node and target port number. The target node is either the IP address of the SF or the node identifier of the SF.

[0355] Step 4: After receiving the sensing request from the core network (such as AMF or SF), the UE determines whether it can accept the sensing task and sends a sensing response to the AMF or SF. The sensing response may contain at least one of the following information: an acceptable sensing identifier, an unacceptable sensing identifier, and a reason value. Additionally, the sensing response may include an accepted sensing identifier, an accepted sensing data reporting identifier, an accepted encryption algorithm, an accepted integrity protection algorithm, an accepted compression algorithm, an accepted protocol type, and the sensing data source address. The sensing data source address includes at least one of the following information: a source node and a source port number. The source node can be a source node identifier or a source node identifier.

[0356] Step 5: After receiving the sensing request information from the base station, the UE performs sensing-related configuration (i.e., performs sensing). In some embodiments, the UE's sensing-related configuration includes the following operations:

[0357] (1) If the perception request information contains perception task information, the UE performs the corresponding perception operation according to the perception-related configuration and obtains perception data;

[0358] (2) If the sensing request information contains sensing data reporting information, when the sensing data reporting condition is triggered, the sensing data is assembled according to the sensing data format requirements and the sensing data is transmitted to the AMF and / or SF (i.e., sensing report) via NAS signaling.

[0359] Example 6: This example provides the signaling flow for configuring the UE in the core network to perform sensing and reporting sensing data through DP-RB and data tunnel, as shown in Figure 15, including:

[0360] Step 1: A UE with sensing capability can send sensing capability information (i.e., sensing capability) to the SF. Additionally, the UE can send sensing capability information to the AMF, which then forwards the UE's sensing capability information to the SF.

[0361] Step 2: The SF in the core network receives a sensing request from a user or customer. The SF can decide which candidate UEs to participate in the sensing task (i.e., select the candidate UEs for the sensing task) based on the UE's capabilities and sensing requirements. The SF can initiate sensing requests to these UEs, or the SF can send sensing request information to the relevant UEs through the AMF.

[0362] Step 3: The SF can send a sensing request to the RAN via the AMF, and the RAN then sends sensing-related configuration information to the corresponding UE. Assuming that the sensing data reported by the UE to the SF is reported in the form of Internet Protocol flow (IP flow), then DP-AB and data tunnels carrying these sensing data (data) IP flows need to be established between the DPF and the RAN, and between the RAN and the UE, respectively, as shown in Figure 16.

[0363] Taking the data tunnel establishment or modification process as an example, after step two above, the SF can send a data tunnel establishment or modification request to the DPF. The data tunnel establishment / modification request may contain at least one of the following information: awareness identifier, fragment identifier, awareness data identifier, data port number, data IP address, and data flow QoS information.

[0364] The data IP address and data port number correspond to the UE's IP address and the UE's perceived data port number. After receiving the data tunnel establishment / modification request, the DPF configures the data tunnel between the xNB and the DPF, for example, the DPF establishes different data tunnels for different fragments. In addition, the DPF stores the mapping information of data IP address and data port corresponding to the data tunnel.

[0365] The data tunnel establishment or modification response sent by the DPF to the SF may contain at least one of the following information: awareness identifier, fragment identifier, awareness data identifier, and data tunnel transport layer information. The data tunnel transport layer information includes the DPF-side IP address and TEID information.

[0366] On the other hand, the SF sends a sensing request message to the RAN. Alternatively, the SF can also send a sensing request message to the RAN via the AMF. The sensing request message contains sensing task information. This sensing task information includes at least one of the following: sensing identifier, segment identifier, sensing type, sensing target, sensing area, sensor type, sensing trigger condition, sensing frequency, sensing duration, whether data processing is performed, and sensing data processing type. Furthermore, the sensing request message may also contain sensing data reporting information, which includes at least one of the following: sensing identifier, sensing data identifier, sensing data type, sensing data reporting trigger condition, sensing data format, and sensing data address. The sensing data address may also include at least one of the following: the SF's IP address or the SF's node identifier. In addition, the sensing request message may also contain data tunnel configuration information, which includes at least one of the following: segment information, sensing data identifier, DPF-side IP address, and DPF-side TEID.

[0367] After receiving the sensing request, the RAN initiates a sensing configuration process to the UE (including sending sensing configuration and receiving sensing configuration complete). The signaling interaction can be found in Example 1. It should be noted that the address of the sensing data included in the sensing configuration information sent by the RAN to the UE may also include at least one of the following: the IP address of the SF or the node identifier of the SF.

[0368] The RAN sends sensing response information (i.e., sensing response) to the SF. Additionally, the RAN can send sensing response information to the SF via the AMF. The sensing response information may contain at least one of the following: acceptable sensing identifiers, unacceptable sensing identifiers, and their cause values. Furthermore, the sensing response information may contain data tunnel configuration information, which includes at least one of the following: fragmentation information, sensing data identifiers, RAN-side IP address, and RAN-side TEID.

[0369] After receiving the data tunnel configuration information from the RAN side, the SF can initiate a data tunnel establishment / modification process to the DPF, informing the DPF of the corresponding RAN side data tunnel configuration information.

[0370] After receiving the sensing configuration from the base station, the UE executes the sensing-related configuration (i.e., performs sensing). In some embodiments, the UE performs corresponding sensing operations according to the sensing-related configuration to obtain sensing data. When the sensing data reporting condition is triggered, the UE assembles the sensing data according to the sensing data format requirements. In some embodiments, the UE assembles the sensing data into IP packets, where the destination address and destination port number of the IP packet are the IP address and port number of the SF. Then, the UE delivers the sensing IP data packet to the DPAP sublayer for processing, and the DPAP sublayer maps the sensing IP data packet to the corresponding DP-RB for transmission. When the RAN receives the data sent by the UE through the DP-RB, it maps the DP-RB data packet to the corresponding data tunnel, encapsulates the data tunnel header, which may contain the RAN-side IP address, RAN-side TEID information, DPF-side IP address, DPF-side TEID information, and / or sensing data identifier. Then, it delivers the data packet to the DPF. After receiving the data packet, the DPF removes the data tunnel header and routes the sensing IP data packet inside to the SF via IP routing (i.e., sensing report with data plane).

[0371] It should be noted that a data tunnel can be a GTP tunnel, a DPAP tunnel, or a QUIC tunnel.

[0372] Example 7: This example provides the configuration of sensing tasks and the process of reporting sensing data between RAN and RAN / CN.

[0373] Future base stations will also have sensing capabilities and be able to perform sensing tasks. For example, the process of NE1 requesting the base station to perform a sensing task and report sensing data could include the following possibilities:

[0374] The core network SF (NE2) initiates the base station (NE1) to perform sensing tasks and report sensing data.

[0375] 1) Base station (NE2) initiates a joint sensing task with neighboring base station (NE1);

[0376] 2) CU(NE2) initiates DU(NE1) to perform a perception task;

[0377] 3) CU(NE2) initiates RU(NE1) to perform a perception task;

[0378] 4) The core network SF (NE2) initiates the RU (NE1) to perform the sensing task;

[0379] 5) The core network SF (NE2) initiates the DU (NE1) to perform the perception task.

[0380] It should be noted that the situation where the core network SF (NE2) initiates the execution of sensing tasks by base stations, RUs, or DUs can be further divided into two sub-scenarios:

[0381] (1) SF directly initiates the base station, RU, or DU to perform sensing tasks;

[0382] (2) SF initiates the base station, RU, or DU to perform sensing tasks through AMF.

[0383] As shown in Figure 17, NE1, which has sensing capabilities, can send sensing capability information to NE2. The sensing capability information includes at least one of the following: supported sensor types (such as GPS, accelerometer, camera, radar, etc.), sensing processing capabilities, sensing type, sensing area, and available time.

[0384] Upon receiving a perception request, NE2 can decide which candidate NEs to participate in the perception task based on NE1's capabilities and the perception request. Then, NE2 initiates the perception task to these candidate NEs.

[0385] In some embodiments, NE2 sends a sensing request message to NE1. The sensing request message includes sensing task information. The sensing task information includes at least one of the following: sensing identifier, segment identifier, sensing type, sensing target, sensing area, sensor type, sensing trigger condition, sensing frequency, sensing duration, whether data processing is performed, and sensing data processing type. The sensing target, sensing area, sensor type, sensing trigger condition, sensing frequency, sensing duration, whether data processing is performed, and sensing data processing type are described similarly to those in Embodiment 1.

[0386] Furthermore, the perception request information may also include perception data reporting information, which includes at least one of the following: perception identifier, perception data identifier, perception data type, perception data reporting trigger condition, perception data format, and perception data address. The content of the perception data type, perception data reporting trigger condition, perception data format, and perception data address is similar to that described in Embodiment 1. The perception data address may also include at least one of the following: target node and target port number. The target node is either the IP address of NE2 or the node identifier of NE2.

[0387] After receiving a sensing request from NE2, NE1 determines whether it can accept the sensing task and sends a sensing response to NE2. The sensing response may contain at least one of the following: an acceptable sensing identifier, an unacceptable sensing identifier, and a reason value. Additionally, the sensing task response may include an accepted sensing identifier, an accepted sensing data reporting identifier, an accepted encryption algorithm, an accepted integrity protection algorithm, an accepted compression algorithm, an accepted protocol type, and the sensing data source address. The sensing data source address includes at least one of the following: a source node and a source port number. The source node can be NE1's IP address or a dot identifier.

[0388] After receiving the perception request from NE2, NE1 executes the perception task. In some embodiments, the UE performs perception operations according to the perception-related configuration, obtains perception data, and if the perception-related configuration information includes perception data reporting information, then when the perception data reporting condition is triggered, the perception data is processed according to the perception data format requirements and assembled. Assuming NE2 is configured to use non-IP format perception data, NE1 can assemble a DPAP subheading from the non-IP data. The DPAP subheading may contain at least one of the following fields: QoS indication, data type indication, data identifier, source node identifier, one or more target node identifiers, source port number, target port number, protocol identifier, and timestamp. After encapsulating the DPAP subheading, NE1 encapsulates a UDP / IP subheading, where the source and destination IP addresses of the IP subheading correspond to the IP addresses of NE2 and NE1, respectively. Finally, NE1 transmits the IP packet to NE2.

[0389] Example 8: This example describes the process by which the core network initiates a sensing task through the CU, allowing the RU or DU to perform sensing tasks and report sensing data.

[0390] As shown in Figure 18, an RU or DU with sensing capabilities can send sensing capability information to a CU. The sensing capability information includes at least one of the following: supported sensor types (e.g., GPS, accelerometer, camera, radar, etc.), sensing processing capabilities, sensing type, sensing area, and available time. In some embodiments, the CU can send sensing capability information to an AMF or SF, and this sensing capability information includes at least one of the following: DU identifier, RU identifier, supported sensor types (e.g., GPS, accelerometer, camera, radar, etc.), sensing processing capabilities, sensing type, sensing area, and available time.

[0391] When the SF (Sensing Provider) in the core network receives a sensing request from a user or customer, it can initiate a sensing request to a CU (Center Unit) with sensing capabilities. Alternatively, the SF in the core network can send a sensing request to the AMF (Awareness Management Provider). The AMF determines the relevant base stations and / or RUs (Real-Time Base Stations) and / or DUs (Dedicated Units) based on the sensing area information, and then sends the sensing request to the relevant CUs.

[0392] The perception request may include perception task information, which includes at least one of the following: perception identifier, segment identifier, perception type, perception target, perception area, sensor type, perception trigger condition, perception frequency, perception duration, whether data processing is performed, and perception data processing type. The content of the perception type, perception target, perception area, sensor type, perception trigger condition, perception frequency, perception duration, whether data processing is performed, and perception data processing type is similar to the description in Embodiment 1. For the perception area, it may also include at least one of the following: one or more RU identifiers, and one or more DU identifiers. Furthermore, the perception request information may also include perception data reporting information, which includes at least one of the following: perception identifier, perception data identifier, perception data type, perception data reporting trigger condition, perception data format, and perception data address. The content of the perception data type, perception data reporting trigger condition, and perception data format is similar to the description in Embodiment 1. The perception data address may also include at least one of the following: target node and target port number. The target node is the IP address of the SF or DPF, or the SF or DPF node identifier.

[0393] After receiving a sensing request from the AMF or SF, the CU determines the RU or DU corresponding to the sensing area and then sends sensing request information to these RUs or DUs. Upon receiving a sensing request from the CU, the RU or DU sends sensing response information to the CU. In some embodiments, the CU may send sensing response information to the AMF or SF after receiving sensing response information from multiple RUs or DUs. The sensing response information may include at least one of the following: acceptable RU identifiers, acceptable DU identifiers, acceptable sensing identifiers, unacceptable sensing identifiers, and a reason value.

[0394] After receiving a sensing request from the CU, the RU or DU executes a sensing task. In some embodiments, the RU or DU performs sensing operations according to sensing-related configurations to acquire sensing data. When the sensing data reporting condition is triggered, the sensing data is processed according to the sensing data format requirements and then assembled. Assuming the SF or AMF is configured to use IP-formatted sensing data, the source IP address in the IP header is the RU / DU's IP address, and the destination IP address corresponds to the SF's IP address. Finally, the RU or DU transmits the IP packet to the SF, indicating that the sensing data did not pass through the CU.

[0395] Example 9: This example provides a process for AF to initiate RU, DU, or xNB to perform a sensing task and report sensing data.

[0396] As shown in Figure 19, an AF with sensing needs can send a sensing request message to the NEF or REF. The NEF or REF then sends the sensing request message to the RU / DU / xNB.

[0397] After receiving a sensing request from NEF or REF, the RU / DU / xNB sends a sensing response message to NEF or REF. The sensing response message may contain at least one of the following: acceptable RU identifier, acceptable DU identifier, acceptable xNB identifier, acceptable sensing identifier, unacceptable sensing identifier, and reason value.

[0398] After receiving a sensing request from NEF or REF, the RU, DU, or xNB executes a sensing task. In some embodiments, the RU, DU, or xNB performs sensing operations according to sensing-related configurations, acquires sensing data, and when the sensing data reporting conditions are triggered, processes the sensing data according to the sensing data format requirements, assembles the sensing data, and sends it directly to the AF / AS.

[0399] In summary, the embodiments of this disclosure design the signaling process for performing perception and transmitting perception data on the UE side and the base station side, including perception capability interaction, perception task issuance, perception data reporting configuration, perception data channel establishment, perception data transmission, etc., to achieve efficient on-demand transmission of perception data.

[0400] It is understood that, in order to achieve the above-mentioned functions, the communication sensing device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the algorithmic steps of the examples described in conjunction with the embodiments of this disclosure, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0401] This disclosure embodiment can divide the communication sensing device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each functional module according to each function.

[0402] Figure 20 is a block diagram of a communication sensing device according to some embodiments. The communication sensing device can be applied to a first node and execute the communication sensing method shown in Figure 6 above. As shown in Figure 20, the communication sensing device 2000 includes a receiving module 2001 and a processing module 2002.

[0403] The receiving module 2001 is used to receive the perception configuration information sent by the second node; the processing module 2002 is used to perform configuration based on the perception configuration information.

[0404] In some embodiments, the communication sensing device 2000 further includes a transmitting module 2003. The transmitting module 2003 is used to transmit the sensing capability information of the first node to the second node.

[0405] In some embodiments, the perception capability information of the first node includes at least one of the following:

[0406] The types of sensors supported by the first node;

[0407] The first node's perception and processing capabilities;

[0408] The perception type of the first node;

[0409] The sensing area of ​​the first node;

[0410] The available time for sensing at the first node;

[0411] The first node's perception indication information.

[0412] In some embodiments, the perception configuration information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

[0413] In some embodiments, the perception task configuration includes at least one of the following:

[0414] Perceptual identifiers;

[0415] Segmentation identification;

[0416] Perception type;

[0417] Perceive the target;

[0418] Sensing area;

[0419] Sensor type;

[0420] Perceive trigger conditions;

[0421] Perceived frequency;

[0422] Perceived duration;

[0423] Public Land Mobile Network (PLMN) identifier;

[0424] Perceive data processing needs;

[0425] Perception data processing type.

[0426] In some embodiments, the perception type includes at least one of the following: communication perception, environment perception, and target object perception.

[0427] In some embodiments, the sensing target includes a sensing object or a sensing event.

[0428] In some embodiments, the sensing region is used to indicate the scope of sensing application, and the sensing region is indicated by any of the following:

[0429] The tracking area is identified;

[0430] List of community signs;

[0431] Geographical location range;

[0432] One or more radio frequency unit (RU) identifiers;

[0433] One or more distribution unit (DU) identifiers.

[0434] In some embodiments, the sensing data processing requirement is used to indicate whether the sensing data is to be analyzed locally.

[0435] In some embodiments, the perception triggering condition includes at least one of the following:

[0436] Enter the designated geographical area;

[0437] Leave the designated geographical area;

[0438] Perceived time range;

[0439] Target network or environmental conditions.

[0440] In some embodiments, the target network or environmental conditions include at least one of the following:

[0441] Movement conditions;

[0442] Energy consumption conditions;

[0443] Air interface link quality;

[0444] Temperature conditions;

[0445] Humidity conditions;

[0446] Lighting conditions;

[0447] Noise conditions.

[0448] In some embodiments, the perception data reporting configuration includes at least one of the following:

[0449] Perceptual identifiers;

[0450] Sensing data identification;

[0451] Perceive data types;

[0452] Triggering conditions for sensing data reporting;

[0453] Perceive data format;

[0454] Address for reporting sensor data.

[0455] In some embodiments, the sensed data type includes at least one of the following:

[0456] Raw data;

[0457] Sensing preprocessed data;

[0458] Perceive and analyze data;

[0459] Perceive and predict information;

[0460] Prediction reliability;

[0461] Timestamp.

[0462] In some embodiments, the raw data includes at least one of the following:

[0463] Signal strength;

[0464] Signal quality;

[0465] Time difference of arrival;

[0466] Angle of arrival;

[0467] Video stream.

[0468] In some embodiments, the perception preprocessing data includes at least one of the following:

[0469] De-identified data;

[0470] Estimate distance;

[0471] Relative position;

[0472] Movement speed;

[0473] Direction of movement;

[0474] Position relative to a reference point;

[0475] Temperature, humidity, pressure, noise, or light.

[0476] In some embodiments, the perception analysis data includes at least one of the following:

[0477] Detected target type;

[0478] Target quantity;

[0479] Target characteristics;

[0480] Abnormal changes in the environment.

[0481] In some embodiments, the triggering condition for sensing data reporting includes at least one of the following:

[0482] Periodic reporting;

[0483] Event trigger reporting;

[0484] Real-time reporting;

[0485] Batch reporting;

[0486] Report all at once.

[0487] In some embodiments, the sensed data format includes at least one of the following:

[0488] Compression required;

[0489] Compression algorithm;

[0490] Is it encrypted?

[0491] Encryption algorithm;

[0492] Whether integrity protection is in place;

[0493] Integrity protection algorithm;

[0494] Internet Protocol (IP) indication or non-IP (non-Internet Protocol) indication;

[0495] Protocol identifier or protocol type.

[0496] In some embodiments, the sensing data reporting address includes at least one of the following: target node address, target node identifier, and target port number.

[0497] In some embodiments, the sense data transmission configuration includes any of the following:

[0498] Signaling Radio Bearer (SRB) configuration;

[0499] Data plane wireless bearer DP-RB configuration.

[0500] In some embodiments, when the sensing data transmission configuration includes an SRB configuration, the sensing data transmission configuration includes SRB identification information.

[0501] In some embodiments, when the sensing data transmission configuration includes a DP-RB configuration, the sensing data transmission configuration includes at least one of DP-RB addition, modification, or release.

[0502] In some embodiments, the sense data transmission configuration includes at least one of the following:

[0503] DP-RB identifier;

[0504] DP-RB associated sensing data identifiers;

[0505] Segmentation identification;

[0506] Configuration information for the Packet Data Convergence Protocol (PDCP) layer;

[0507] Should PDCP be rebuilt?

[0508] Should PDCP be restored?

[0509] Configuration information for the Radio Link Control (RLC) layer;

[0510] The relevant configuration of logical channels;

[0511] Configuration information for the Media Access Control (MAC) layer.

[0512] In some embodiments, the sending module 2003 is further configured to send a perception configuration completion message to the second node.

[0513] In some embodiments, the awareness configuration completion information includes at least one of the following:

[0514] Acceptable perceptual identifiers;

[0515] Acceptable sensor data reporting identifier;

[0516] Acceptable encryption algorithms;

[0517] Acceptable integrity protection algorithms;

[0518] Acceptable compression algorithms;

[0519] Acceptable protocol types;

[0520] Perceive the data source address.

[0521] In some embodiments, the perceived data source address includes at least one of the following: source node address, source node identifier, and source port number.

[0522] In some embodiments, the first node and the second node satisfy any one of the following:

[0523] When the first node is a user equipment (UE), the second node can be any one of the following: base station, centralized unit (CU), DU, sensing function (SF) network element, or access and mobility management function (AMF) network element;

[0524] When the first node is a base station, the second node can be any one of the following: an adjacent base station, an SF network element, an AMF network element, or an application function AF network element.

[0525] When the first node is RU, the second node can be any one of CU, DU, adjacent base station, SF network element, AMF network element, or AF network element;

[0526] When the first node is DU, the second node can be any one of CU, adjacent base station, SF network element, AMF network element, or AF network element.

[0527] In some embodiments, the first node is a UE, and the sensing configuration information is carried in a Radio Resource Control (RRC) reconfiguration message, or the sensing configuration information is carried in system information.

[0528] In some embodiments, the first node is an idle or inactive UE. The receiving module 2001 is specifically configured to receive the perception task configuration sent by the second node; the processing module 2002 is further configured to enter a connected state when the first node is capable of executing the perception task corresponding to the perception task configuration. The sending module 2003 is further configured to send RRC signaling to the second node, the RRC signaling including at least one of the following: perception identifier, fragment identifier, and perception intention indication.

[0529] In some embodiments, the first node is an idle or inactive UE. The receiving module 2001 is configured to receive the sensing task configuration sent by the second node; the processing module 2002 is further configured to enter a connected state when the first node is capable of executing the sensing task corresponding to the sensing task configuration and the first node has collected the sensing data corresponding to the sensing task. The sending module 2003 is further configured to send RRC signaling to the second node, the RRC signaling including at least one of the following: sensing data indication, sensing identifier, sensing data identifier, and fragment identifier.

[0530] In some embodiments, the first node is an idle or inactive UE. The receiving module 2001 is configured to receive the perception task configuration and perception data reporting configuration sent by the second node; the processing module 2002 is further configured to enter a connected state when the first node is capable of executing the perception task corresponding to the perception task configuration and meets the perception data reporting triggering condition corresponding to the perception data reporting configuration. The sending module 2003 is further configured to send RRC signaling to the second node, the RRC signaling including at least one of the following: perception data indication, perception identifier, perception data identifier, and fragment identifier.

[0531] In some embodiments, RRC signaling is any of the following: RRC connection establishment request message, RRC connection establishment completion message, or new RRC signaling.

[0532] Figure 21 is a block diagram of another communication sensing device according to some embodiments. The communication sensing device can be applied to a second node and execute the communication sensing method shown in Figure 7 above. As shown in Figure 21, the communication sensing device 2100 includes: a transmitting module 2101.

[0533] The sending module 2101 is used to send perception configuration information to the first node.

[0534] In some embodiments, the perception configuration information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

[0535] In some embodiments, the first node is a UE and the second node is a base station. The communication sensing device 2100 further includes a processing module. The processing module is configured to perform a sensing task based on sensing configuration information when the second node is capable of executing a sensing task configuration corresponding to the sensing task.

[0536] In some embodiments, the second node is an AF network element, and the sending module 2101 is used to send perception configuration information to the first node through the first network element. The first network element includes a Network Open Function (NEF) network element or a Radio Access Network Open Function (REF) network element.

[0537] In some embodiments, the communication sensing device 2100 further includes a receiving module 2102. The receiving module 2102 is configured to receive sensing capability information of the first node sent by the first node.

[0538] In some embodiments, the receiving module 2102 is further configured to receive perception request information sent by the third node; the sending module 2101 is configured to send perception configuration information to the first node according to the perception request information.

[0539] In some embodiments, the perception request information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

[0540] In some embodiments, the sending module 2101 is further configured to send perception response information to the third node, the perception response information including at least one of the following: an acceptable perception identifier, an unacceptable perception identifier, and a cause value.

[0541] In some embodiments, when the first node is a UE and the second node is a base station, the third node is any one of an adjacent base station, an SF network element, an AMF network element, or an AF network element.

[0542] Figure 22 is a block diagram of another communication sensing device according to some embodiments. The communication sensing device can be applied to a second node and execute the communication sensing method shown in Figure 8 above. As shown in Figure 22, the communication sensing device 2200 includes a receiving module 2201 and a processing module 2202.

[0543] The receiving module 2201 is used to receive the perception authorization information of the first node sent by the third node; the processing module 2202 is used to determine whether the first node authorizes the execution of perception based on the perception authorization information of the first node.

[0544] In some embodiments, the communication sensing device 2200 further includes a sending module 2203. The sending module 2203 is configured to send sensing configuration information to the first node when the first node authorizes the execution of sensing.

[0545] In some embodiments, the perceived authorization information includes at least one of the following:

[0546] First node address or identifier;

[0547] Group identifier;

[0548] Perception type;

[0549] Perceptual identifiers;

[0550] Perceive the target;

[0551] Authorization instructions;

[0552] Sensing area

[0553] Available time;

[0554] Segmentation identification;

[0555] PLMN information.

[0556] In some embodiments, the sending module 2203 is further configured to send a perception configuration update indication information to the first node when the perception authorization information of the first node changes; the perception configuration update indication information includes at least one of the following: release indication, suspension indication, and recovery indication, wherein the release indication is used to release the corresponding perception configuration, the suspension indication is used to suspend the corresponding perception and / or perception reporting, and the recovery indication is used to recover the corresponding perception and / or perception reporting.

[0557] Figure 23 is a block diagram of another communication sensing device according to some embodiments. The communication sensing device can be applied to a third node and execute the communication sensing method shown in Figure 9 above. As shown in Figure 23, the communication sensing device 2300 includes a transmitting module 2301 and a receiving module 2302.

[0558] The sending module 2301 is used to send perception request information to one or more second nodes; the receiving module 2302 is used to receive perception response information sent by one or more second nodes.

[0559] In some embodiments, the communication sensing device 2300 further includes a processing module 2303. The processing module 2303 is used to determine the sensing range according to the sensing requirements; the sending module 2301 is also used to send sensing request information to one or more second nodes within the sensing range.

[0560] In some embodiments, the perception request information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration; or, the perception response information includes at least one of the following: an acceptable perception identifier, an unacceptable perception identifier, and a reason value.

[0561] In some embodiments, the second node is a base station, the third node is an SF network element, and the sending module 2301 is used to send a data tunnel establishment or modification request information between the DPF network element and the second node to the DPF network element. The data tunnel establishment / modification request information includes at least one of the following: perception identifier, fragment identifier, perception data identifier, UE IP address, UE perception data port number, and data flow quality of service (QoS) information. The data tunnel establishment or modification request information is used to indicate the configuration of the data tunnel between the second node and the DPF network element.

[0562] In some embodiments, the receiving module 2302 is further configured to receive data tunnel establishment or modification response information sent by the DPF network element; the data tunnel establishment or modification response information includes at least one of the following: sensing identifier, fragment identifier, sensing data identifier, IP address of the DPF network element, and tunnel endpoint identifier (TEID) of the DPF network element.

[0563] In some embodiments, the sensing request information includes: fragment identifier, sensing data identifier, IP address of DPF network element, and TEID of DPF network element.

[0564] In some embodiments, the sensing response information includes: fragment identifier, sensing data identifier, IP address of the second node, and TEID of the second node.

[0565] In the case of implementing the functions of the integrated modules described above in hardware, this disclosure provides another possible block diagram of the communication sensing device involved in the above embodiments. As shown in FIG24, the communication sensing device 2400 includes: a processor 2402 and a bus 2404. In some embodiments, the communication sensing device may further include a memory 2401; in some embodiments, the communication sensing device may further include a communication interface 2403.

[0566] Processor 2402 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 2402 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 2402 may also be a combination of computing functions, such as a combination of one or more microprocessors, a digital signal processor (DSP), and a microprocessor, etc.

[0567] The communication interface 2403 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0568] The memory 2401 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0569] In one implementation, the memory 2401 can exist independently of the processor 2402. The memory 2401 can be connected to the processor 2402 via a bus 2404 and is used to store instructions or program code. When the processor 2402 calls and executes the instructions or program code stored in the memory 2401, it can implement the communication sensing method provided in the embodiments of this disclosure.

[0570] In another implementation, the memory 2401 can also be integrated with the processor 2402.

[0571] Bus 2404 can be an extended industry standard architecture (EISA) bus, etc. Bus 2404 can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in Figure 24, but this does not mean that there is only one bus or one type of bus.

[0572] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a computer, cause the computer to perform the communication sensing method as described in any of the above embodiments.

[0573] In some embodiments, the computer-readable storage media described above may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices for storing information and / or other machine-readable storage media. The term "machine-readable storage media" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0574] This disclosure provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the communication sensing method described in any of the above embodiments.

[0575] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication sensing method, wherein, Applied to the first node, the method includes: Receive the perception configuration information sent by the second node; Configure according to the perception configuration information.

2. The method according to claim 1, wherein, Before receiving the perception configuration information sent by the second node, the method further includes: Send the perception capability information of the first node to the second node.

3. The method according to claim 2, wherein, The perception capability information of the first node includes at least one of the following: The types of sensors supported by the first node; The sensing and processing capabilities of the first node; The perception type of the first node; The sensing area of ​​the first node; The sensing availability time of the first node; The perception indication information of the first node.

4. The method according to any one of claims 1-3, wherein, The perception configuration information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

5. The method according to claim 4, wherein, The perception task configuration includes at least one of the following: Perceptual identifiers; Segmentation identification; Perception type; Perceive the target; Sensing area; Sensor type; Perceive trigger conditions; Perceived frequency; Perceived duration; Public Land Mobile Network (PLMN) identifier; Perceive data processing needs; Perception data processing type.

6. The method according to claim 5, wherein, The perception type includes at least one of the following: communication perception, environment perception, and target object perception.

7. The method according to claim 5, wherein, The perception target includes the perception object or the perception event.

8. The method according to claim 5, wherein, The sensing area is used to indicate the scope of sensing application, and the sensing area is indicated by any of the following: The tracking area is identified; List of community signs; Geographical location range; One or more radio frequency unit (RU) identifiers; One or more distribution unit (DU) identifiers.

9. The method according to claim 5, wherein, The sensing data processing requirement is used to indicate whether the sensing data should be analyzed locally.

10. The method according to claim 5, wherein, The perception triggering condition includes at least one of the following: Enter the designated geographical area; Leave the designated geographical area; Perceived time range; Target network or environmental conditions.

11. The method according to claim 10, wherein, The target network or environmental conditions include at least one of the following: Movement conditions; Energy consumption conditions; Air interface link quality; Temperature conditions; Humidity conditions; Lighting conditions; Noise conditions.

12. The method according to claim 4, wherein, The sensing data reporting configuration includes at least one of the following: Perceptual identifiers; Sensing data identification; Perceive data types; Triggering conditions for sensing data reporting; Perceive data format; Address for reporting sensor data.

13. The method according to claim 12, wherein, The sensed data type includes at least one of the following: Raw data; Sensing preprocessed data; Perceive and analyze data; Perceive and predict information; Prediction reliability; Timestamp.

14. The method according to claim 13, wherein, The raw data includes at least one of the following: Signal strength; Signal quality; Time difference of arrival; Angle of arrival; Video stream.

15. The method according to claim 13, wherein, The sensing preprocessing data includes at least one of the following: De-identified data; Estimate distance; Relative position; Movement speed; Direction of movement; Position relative to a reference point; Temperature, humidity, pressure, noise, or light.

16. The method according to claim 13, wherein, The perception analysis data includes at least one of the following: Detected target type; Target quantity; Target characteristics; Abnormal changes in the environment.

17. The method according to claim 12, wherein, The triggering conditions for the reporting of the sensing data include at least one of the following: Periodic reporting; Event trigger reporting; Real-time reporting; Batch reporting; Report all at once.

18. The method according to claim 12, wherein, Perceptual data formats include at least one of the following: Compression required; Compression algorithm; Is it encrypted? Encryption algorithm; Whether integrity protection is in place; Integrity protection algorithm; Internet Protocol (IP) indication or non-IP (non-Internet Protocol) indication; Protocol identifier or protocol type.

19. The method according to claim 12, wherein, The address for reporting sensing data includes at least one of the following: target node address, target node identifier, and target port number.

20. The method according to claim 4, wherein, The sensing data transmission configuration includes any one of the following: Signaling Radio Bearer (SRB) configuration; Data plane wireless bearer DP-RB configuration.

21. The method according to claim 20, wherein, When the sensing data transmission configuration includes the SRB configuration, the sensing data transmission configuration includes SRB identification information.

22. The method according to claim 20, wherein, When the sensing data transmission configuration includes the DP-RB configuration, the sensing data transmission configuration includes at least one of DP-RB addition, modification, or release.

23. The method according to claim 22, wherein, The sensing data transmission configuration includes at least one of the following: DP-RB identifier; DP-RB associated sensing data identifiers; Segmentation identification; Configuration information for the Packet Data Convergence Protocol (PDCP) layer; Should PDCP be rebuilt? Should PDCP be restored? Configuration information for the Radio Link Control (RLC) layer; The relevant configuration of logical channels; Configuration information for the Media Access Control (MAC) layer.

24. The method according to claim 1, wherein, After configuring according to the perception configuration information, the method further includes: Send a perception configuration completion message to the second node.

25. The method according to claim 24, wherein, The perception configuration completion information includes at least one of the following: Acceptable perceptual identifiers; Acceptable sensor data reporting identifier; Acceptable encryption algorithms; Acceptable integrity protection algorithms; Acceptable compression algorithms; Acceptable protocol types; Perceive the data source address.

26. The method of claim 25, wherein, The source data address includes at least one of the following: source node address, source node identifier, and source port number.

27. The method according to claim 1, wherein, The first node and the second node satisfy any one of the following: When the first node is a user equipment (UE), the second node is any one of a base station, a central unit (CU), a DU, a sensing function (SF) network element, or an access and mobility management function (AMF) network element. When the first node is a base station, the second node can be any one of the following: an adjacent base station, an SF network element, an AMF network element, or an application function AF network element. When the first node is RU, the second node can be any one of CU, DU, adjacent base station, SF network element, AMF network element, or AF network element; When the first node is DU, the second node is any one of CU, adjacent base station, SF network element, AMF network element, and AF network element.

28. The method according to claim 1, wherein, The first node is a UE, and the perception configuration information is carried in a Radio Resource Control (RRC) reconfiguration message, or the perception configuration information is carried in system information.

29. The method according to claim 28, wherein, The first node is an idle or inactive UE, and the receipt of the perception configuration information sent by the second node includes: Receive the perception task configuration sent by the second node; When the first node can execute the perception task configuration corresponding to the perception task, it enters the connection state and sends RRC signaling to the second node. The RRC signaling includes at least one of the following: perception identifier, fragment identifier, and perception intention indication.

30. The method according to claim 28, wherein, The first node is an idle or inactive UE, and the receipt of the perception configuration information sent by the second node includes: Receive the perception task configuration sent by the second node; When the first node can execute the perception task corresponding to the perception task configuration and the first node collects the perception data corresponding to the perception task, it enters the connection state and sends RRC signaling to the second node. The RRC signaling includes at least one of the following: perception data indication, perception identifier, perception data identifier, and fragment identifier.

31. The method according to claim 28, wherein, The first node is an idle or inactive UE, and the receipt of the perception configuration information sent by the second node includes: Receive the perception task configuration and perception data reporting configuration sent by the second node; When the first node can execute the perception task corresponding to the perception task configuration and meets the perception data reporting triggering condition corresponding to the perception data reporting configuration, it enters the connection state and sends RRC signaling to the second node. The RRC signaling includes at least one of the following: perception data indication, perception identifier, perception data identifier, and fragment identifier.

32. The method according to any one of claims 29-31, wherein, The RRC signaling is any one of the following: RRC connection establishment request message, RRC connection establishment completion message, or new RRC signaling.

33. A communication sensing method, wherein, Applied to the second node, the method includes: Send the perception configuration information to the first node.

34. The method according to claim 33, wherein, The perception configuration information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

35. The method according to claim 34, wherein, The first node is a UE, and the second node is a base station; the method further includes: If the second node can execute the perception task corresponding to the perception task configuration, the configuration is performed according to the perception configuration information.

36. The method according to claim 33, wherein, The second node is an AF network element, and the step of sending sensing configuration information to the first node includes: The sensing configuration information is sent to the first node through a first network element, wherein the first network element includes a Network Open Function (NEF) network element or a Radio Access Network Open Function (REF) network element.

37. The method according to claim 33, wherein, Before sending the perception configuration information to the first node, the method further includes: Receive the perception capability information of the first node sent by the first node.

38. The method according to claim 33, wherein, Sending the perception configuration information to the first node includes: Receive perception request information sent by the third node; Based on the perception request information, the perception configuration information is sent to the first node.

39. The method according to claim 38, wherein, The perception request information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration.

40. The method of claim 38, wherein, After receiving the perception request information sent by the third node, the method further includes: Send perception response information to the third node, the perception response information including at least one of the following: acceptable perception identifier, unacceptable perception identifier, and cause value.

41. The method according to any one of claims 38-40, wherein, When the first node is a UE and the second node is a base station, the third node can be any one of the following: an adjacent base station, an SF network element, an AMF network element, or an AF network element.

42. A communication sensing method, wherein, Applied to the second node, the method includes: Receive the perception authorization information sent by the third node from the first node; Based on the perception authorization information of the first node, determine whether the first node authorizes the execution of perception.

43. The method of claim 42, further comprising: If the first node authorizes the execution of perception, perception configuration information is sent to the first node.

44. The method according to claim 42, wherein, The perceived authorization information includes at least one of the following: The address or identifier of the first node; Group identifier; Perception type; Perceptual identifiers; Perceive the target; Authorization instructions; Sensing area Available time; Segmentation identification; PLMN information.

45. The method of claim 43, further comprising: If the perception authorization information of the first node changes, a perception configuration update instruction message is sent to the first node; The perception configuration update indication information includes at least one of the following: release indication, suspension indication, and recovery indication. The release indication is used to release the corresponding perception configuration, the suspension indication is used to pause the corresponding perception and / or perception reporting, and the recovery indication is used to restore the corresponding perception and / or perception reporting.

46. ​​A communication sensing method, wherein, Applied to a third node, the method includes: Send perception request information to one or more second nodes; Receive sensing response information sent by one or more second nodes.

47. The method according to claim 46, wherein, Sending perception request information to one or more second nodes includes: Determine the sensing range based on sensing needs; The sensing request information is sent to one or more second nodes within the sensing range.

48. The method according to claim 46, wherein, The perception request information includes at least one of the following: perception task configuration, perception data reporting configuration, and perception data transmission configuration; or... The perception response information includes at least one of the following: an acceptable perception identifier, an unacceptable perception identifier, and a cause value.

49. The method according to claim 46, wherein, The second node is a base station, and the third node is an SF network element. Sending sensing request information to one or more second nodes includes: Send a data tunnel establishment or modification request to the Data Plane Function (DPF) network element between the DPF network element and the second node; The data tunnel establishment or modification request information includes at least one of the following: perception identifier, fragment identifier, perception data identifier, UE IP address, UE perception data port number, and data flow service quality (QoS) information. The data tunnel establishment or modification request information is used to indicate the configuration of the data tunnel between the second node and the DPF network element.

50. The method of claim 49, further comprising: Receive data tunnel establishment or modification response information sent by the DPF network element; The data tunnel establishment or modification response information includes at least one of the following: perception identifier, fragment identifier, perception data identifier, IP address of the DPF network element, and tunnel endpoint identifier (TEID) of the DPF network element.

51. The method according to claim 49, wherein, The perception request information includes: fragment identifier, perception data identifier, IP address of the DPF network element, and TEID of the DPF network element.

52. The method according to claim 49, wherein, The sensing response information includes: fragment identifier, sensing data identifier, IP address of the second node, and TEID of the second node.

53. A communication sensing device, comprising: Memory and processor; The memory and the processor are coupled; The memory is used to store instructions that can be executed by the processor; When the processor executes the instructions, it performs the method according to any one of claims 1-52.

54. A computer-readable storage medium, wherein, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method according to any one of claims 1-52.

55. A computer program product, wherein, The computer program product includes computer program instructions that, when executed, implement the method according to any one of claims 1-52.

Images