Communication method and device

Abstract

The invention discloses a communication method and device. The method comprises the steps that a first device receives perception data of at least one terminal; and processing the sensing data of the at least one terminal according to whether the position of the at least one terminal is obtained or not. In the method, a first device can process sensing data of at least one terminal according to whether the position of the at least one terminal is obtained or not. In one case, a first device can acquire a location of at least one terminal, so that perception data of the at least one terminal can be processed according to the location of the at least one terminal. In this case, the location of the at least one terminal may be a reference location of the at least one terminal, rather than an actual location of the at least one terminal. The position of the terminal is the privacy of the terminal, so that the method can improve the perceptual processing performance under the condition of ensuring the privacy of the terminal.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Integrated sensing and communication (ISAC) is one of the important application scenarios in mobile communication systems. ISAC possesses diverse capabilities such as high-precision positioning, environment reconstruction, imaging, and recognition, which can greatly facilitate applications requiring ultra-high resolution and accuracy. Furthermore, ISAC also helps improve communication performance and efficiency.

[0003] Currently, in the ISAC system, the terminal can provide sensing data. How to process the terminal's sensing data requires further research. Summary of the Invention

[0004] This application provides a communication method and apparatus for processing sensor data from a terminal.

[0005] In a first aspect, embodiments of this application provide a communication method that can be applied to a first device on the access network side. The first device may be a first logic unit in the access network or a device within the first logic unit (e.g., a module, communication module, circuit, chip (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor); or, the first device may be a first access network device or a device within the first access network device (e.g., a module, communication module, circuit, chip (such as a modem chip, or an SoC chip or SIP chip containing a modem core), a chip system, or a processor). The first logic unit can be used for sensing. Optionally, the first access network device may include the first logic unit.

[0006] The method includes: a first device receiving sensing data from at least one terminal; and processing the sensing data from at least one terminal based on whether the location of at least one terminal has been obtained.

[0007] In this method, the first device can process the sensing data of at least one terminal based on whether the location of at least one terminal is acquired. In one case, the first device can acquire the location of at least one terminal, and thus process the sensing data of at least one terminal based on the location of at least one terminal. In this case, the location of at least one terminal can be a reference location of at least one terminal, rather than the actual location of at least one terminal. Since the location of a terminal is a matter of terminal privacy, this method can improve the performance of sensing processing while ensuring the privacy of the terminal.

[0008] Furthermore, in this method, the first device can be used for sensing, and the first device can be independent of the device used for communication on the access network side, thereby improving the scalability of the first device, and thus meeting higher sensing requirements by upgrading the first device.

[0009] In one possible design, upon obtaining the location of at least one terminal, the first device processes the sensing data of at least one terminal based on that location. This design enables the access network side to process the terminal's sensing data. Compared to processing the terminal's sensing data through core network equipment or a third-party server, this design reduces the processing latency of the terminal's sensing data. Furthermore, in this design, the location of the at least one terminal obtained by the first device can be a reference location for the at least one terminal, rather than its actual location. The actual location of the terminal is a matter of terminal privacy. Therefore, this design reduces the processing latency of the terminal's sensing data and improves the performance of sensing processing while ensuring the privacy of at least one terminal.

[0010] And / or, in the absence of obtaining the location of at least one terminal, the first device sends sensing data of at least one terminal and receives first sensing data, which is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal. Through this design, the first device on the access network side can obtain the first sensing data, which is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal. In this design, the access network side may not need to obtain the location of at least one terminal. The actual location of the terminal is a matter of terminal privacy. Therefore, this method can achieve the processing of sensing data of at least one terminal while ensuring the privacy of at least one terminal.

[0011] In one possible design, the first device may also receive first indication information, which indicates whether a terminal is involved in sensing. With this design, the first device can accurately determine whether a terminal is involved in sensing based on the first indication information. Furthermore, in this design, the presence or absence of a terminal is indicated by the first indication information, and the first device does not need to perform calculations to determine whether a terminal is involved, thereby reducing the computational complexity and power consumption of the first device.

[0012] In one possible design, upon receiving a first indication that a terminal is involved in sensing, the first device sends a first request to request the location of at least one terminal. This design allows the first device to request the location of at least one terminal on demand, avoiding unnecessary transmission of information indicating the location of at least one terminal and thus saving transmission resources.

[0013] And / or, if the first indication information indicates that a terminal is involved in sensing, and the location of at least one terminal has not been obtained, the first device sends a second request. The second request is used to request first sensing data, which is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal. Through this design, the first device can request first sensing data on demand, avoiding unnecessary transmission of first sensing data, thereby saving transmission resources.

[0014] In one possible design, the first device also acquires second sensing data. Wherein, if the location of at least one terminal is acquired, the second sensing data is obtained by fusing sensing data from at least one terminal with third sensing data sensed by the access network side; and / or, if the location of at least one terminal is not acquired, the second sensing data is obtained by fusing first sensing data with third sensing data sensed by the access network side, wherein the first sensing data is obtained by processing the sensing data of at least one terminal based on its location. In this design, the first device can obtain the second sensing data based on sensing data from multiple devices, thereby enabling sensing processing based on more comprehensive sensing data and improving sensing performance.

[0015] In one possible design, the sensing data and third-party sensing data from at least one terminal are transmitted on different interfaces, or on different logical links on the same interface, or contained in different data packets. This design allows each device to accurately determine whether the received sensing data is sensing data from at least one terminal or third-party sensing data sensed by the access network side.

[0016] In one possible design, the first device also transmits second sensing data, which corresponds to sensing data from at least one terminal. For example, the first device may transmit the second sensing data to a sensing management network element, allowing the network element to accurately acquire the second sensing data and thus perform more effective sensing management. Alternatively, the first device may transmit the second sensing data to a second device, enabling the second device to communicate based on the second sensing data, or the second sensing data may be used to assist in communication.

[0017] In one possible design, the first device further receives first information indicating a first sensing requirement. The first device then sends second information. The second information is used to determine first sensing resources; the first sensing resources are used by at least one terminal to send and / or receive sensing signals, and the sending and / or receiving of sensing signals corresponds to a second sensing requirement, which is determined based on the first sensing requirement.

[0018] Through this design, after receiving first information indicating a first sensing requirement, the first device on the access network side can send second information for determining the first sensing resource. Thus, the first sensing resource can be determined on the access network side. Since the device on the access network side can easily obtain information about the resources on the access network side, it can determine sensing resources that are appropriate for the access network side's conditions, thereby meeting the sensing requirement, improving sensing performance, and increasing the efficiency of sensing management.

[0019] In addition, since the devices on the access network side can quickly obtain information about the resources on the access network side, the latency of determining the sensing resources can be reduced, thereby improving sensing performance and the efficiency of sensing management.

[0020] In one possible design, the second information indicates the first sensing resource. With this design, the first device can accurately indicate the first sensing resource via the second information. Furthermore, in this approach, the sensing resource can be determined by the first device on the access network side, thereby improving the flexibility of the first device in sensing management and thus improving the efficiency of sensing management. Alternatively, the second information indicates a second sensing requirement, which is used to determine the first sensing resource. In this way, the second device can determine the first sensing resource matching the second sensing requirement based on the second sensing requirement indicated by the second information. Furthermore, in this approach, the sensing resource can be determined by the second device on the access network side, thereby improving the flexibility of the second device in sensing management and thus improving the efficiency of sensing management.

[0021] In one possible design, when the second information indicates the first sensing resource, the first device also receives third information indicating recommended and / or unrecommended sensing resources. This third information is used to determine the first sensing resource. With this design, the first device can learn about the recommended and / or unrecommended sensing resources, thereby selecting appropriate sensing resources to better meet sensing needs and improve the efficiency of sensing management.

[0022] In one possible design, when the second information indicates the first sensing resource, the first device also receives first response information, which indicates whether to accept or reject using the first sensing resource to fulfill the second sensing requirement. Thus, the first device can accurately determine whether the second device accepts or rejects using the first sensing resource to fulfill the second sensing requirement based on the first response information.

[0023] In one possible design, if the first response information indicates that the first sensing resource is rejected from fulfilling the second sensing requirement, the first response information also indicates at least one of the following: the reason for rejection; or, recommended and / or not recommended sensing resources. Thus, the first device can know the reason for rejecting the first sensing resource from fulfilling the second sensing requirement, and / or, the recommended and / or not recommended sensing resources, and can adjust the second information accordingly. For example, it can adjust the sensing requirements for the second device and / or the sensing resources configured for at least one terminal, so that the adjusted second information (or the sensing resources determined based on the adjusted second information) is adapted to the resource situation on the terminal side, thereby satisfying the sensing requirements, improving sensing performance, and improving the efficiency of sensing management.

[0024] In one possible design, when the second information indicates the first sensing resource, the second information also indicates at least one of the following: the transmission and reception mode of at least one terminal performing sensing; or, the area sensed by at least one terminal. With this design, the second device can accurately determine the transmission and reception mode and / or the area sensed based on the second information, thereby improving sensing performance. Furthermore, in this design, the transmission and reception mode and / or the area sensed can be indicated by the first device, thereby increasing the flexibility of the first device in sensing management.

[0025] In one possible design, when the second information indicates a second sensing requirement, the first device receives second response information. The second response information indicates a first sensing resource, allowing the first device to accurately determine the first sensing resource based on the second response information; alternatively, the second response information indicates a refusal to fulfill the second sensing requirement, allowing the first device to accurately determine that the second device has refused to fulfill the second sensing requirement based on the second response information.

[0026] In one possible design, when the second response information indicates the first sensing resource, the second response information also indicates at least one of the following: the transmission and reception mode of at least one terminal performing sensing; or, the area sensed by at least one terminal. With this design, the second response information can accurately indicate the transmission and reception mode of sensing and / or the area sensed, thereby improving the efficiency of sensing management and enhancing sensing performance.

[0027] In one possible design, if the second response information indicates a refusal to fulfill a second sensing requirement, the second response information also indicates at least one of the following: the reason for the refusal; recommended and / or not recommended sensing resources; or, the sensing requirement that can be fulfilled. In this way, the first device can learn one or more of the following: the reason for refusing to fulfill the second sensing requirement, the recommended and / or not recommended sensing resources, or, the achievable sensing requirement. Based on this, it can adjust the sensing requirements for the second device so that the adjusted sensing requirements are adapted to the resource situation on the terminal side served by the second device, thereby satisfying the sensing requirements, improving sensing performance, and increasing the efficiency of sensing management.

[0028] In one possible design, the reasons for rejection include at least one of the following: insufficient time-domain resources; insufficient frequency-domain resources; insufficient spatial-domain resources; insufficient code-domain resources; insufficient power-domain resources; no terminal available for sensing; or, the terminal does not meet the second sensing requirement. This design provides multiple forms of rejection reasons, is relatively flexible, and is easy to implement.

[0029] In one possible design, the first device receives first information from a sensing management network element; alternatively, the first device receives first information from a second logic unit or a second access network device. This design provides multiple ways to obtain first information indicating a first sensing requirement, offering greater flexibility. Furthermore, if the first device can receive first information from the second logic unit or the second access network device, the first device can obtain the first sensing requirement from the second logic unit or the second access network device on the access network side, thereby improving the access network's management efficiency for sensing and reducing the latency of obtaining the first sensing requirement.

[0030] In one possible design, the first sensing requirement includes at least one of the following: the perceived quality of service (QoS) or service level agreement (SLA); the type of perceived data; the time of sensing; or, the area of ​​sensing. This design provides multiple possible ways to define sensing requirements, allowing for flexible configuration of these requirements.

[0031] In one possible design, the type of sensed data includes at least one of the following: in-phase / quadrature (I / Q) signals, range-angle-velocity (RAV) spectrum information, channel frequency response (CFR) information, point cloud information, or sensed target information. This design provides multiple possible ways to configure the types of sensed data.

[0032] Secondly, embodiments of this application provide a communication method, the execution subject of which may include one or more of a first device, a second device, and a sensing management network element. The first device may be a first logical unit in an access network or a device within a first logical unit (e.g., a module, communication module, circuit, chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor); the second device may be a second logical unit in the access network or a device within a second logical unit (e.g., a module, communication module, circuit, chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor). Alternatively, the first device may be a first access network device or a device within a first access network device (e.g., a module, communication module, circuit, chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor); the second device may be a second access network device or a device within a second access network device (e.g., a module, communication module, circuit, chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor).

[0033] The method includes: a first device receiving sensing data from at least one terminal; and the first device processing the sensing data from the at least one terminal based on whether the location of the at least one terminal has been obtained.

[0034] In one possible design, if the location of at least one terminal is obtained, the first device processes the sensing data of at least one terminal based on its location. And / or, if the location of at least one terminal is not obtained, the first device transmits the sensing data of at least one terminal; correspondingly, the sensing management network element receives the sensing data of at least one terminal. The sensing management network element transmits first sensing data; correspondingly, the first device receives the first sensing data. The first sensing data is obtained by processing the sensing data of at least one terminal based on its location.

[0035] In one possible design, the sensing management network element or the second device sends a first indication message; correspondingly, the first device can also receive the first indication message. The first indication message indicates whether a terminal is involved in sensing.

[0036] In one possible design, when the first indication information indicates that a terminal is participating in sensing, the first device sends a first request; correspondingly, the sensing management network element receives the first request. The first request is used to request the location of at least one terminal. And / or, when the first indication information indicates that a terminal is participating in sensing, but the location of at least one terminal has not been obtained, the first device sends a second request; correspondingly, the sensing management network element receives the second request. The second request is used to request first sensing data, which is obtained by processing the sensing data of at least one terminal based on its location.

[0037] In one possible design, the first device further acquires second sensing data. Wherein, if the location of at least one terminal is acquired, the second sensing data is obtained by fusing sensing data from at least one terminal with third sensing data sensed by the access network side; and / or, if the location of at least one terminal is not acquired, the second sensing data is obtained by fusing first sensing data with third sensing data sensed by the access network side, wherein the first sensing data is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal.

[0038] In one possible design, the sensing data and third sensing data of at least one terminal are transmitted on different interfaces, or on different logical links on the same interface, or contained in different data packets.

[0039] In one possible design, the first device also transmits second sensing data; correspondingly, the second device and / or sensing management network element receive the second sensing data. The second sensing data corresponds to sensing data from at least one terminal.

[0040] In one possible design, the first device also receives first information indicating a first sensing requirement. The first device sends second information; correspondingly, the second device receives the second information. The second information is used to determine a first sensing resource; the first sensing resource is used for at least one terminal to send and / or receive sensing signals, the sending and / or receiving of sensing signals corresponding to a second sensing requirement, which is determined based on the first sensing requirement.

[0041] In one possible design, the second information indicates the first sensing resource; or, the second information indicates the second sensing requirement, which is used to determine the first sensing resource.

[0042] In one possible design, if the second information indicates a first sensing resource, the second device also sends a third information; correspondingly, the first device also receives the third information. The third information indicates recommended and / or not recommended sensing resources, and is used to determine the first sensing resource.

[0043] In one possible design, when the second information indicates the first sensing resource, the second device also sends a first response information; correspondingly, the first device also receives the first response information. The first response information indicates whether the first sensing resource is accepted or rejected to fulfill the second sensing requirement.

[0044] In one possible design, if the first response information indicates that the first sensing resource is rejected for fulfilling the second sensing requirement, the first response information also indicates at least one of the following: the reason for rejection; or, the recommended and / or not recommended sensing resources.

[0045] In one possible design, where the second information indicates the first sensing resource, the second information also indicates at least one of the following: a transmission and reception mode for sensing by at least one terminal; or, an area sensed by at least one terminal.

[0046] In one possible design, when the second information indicates a second sensing requirement, the second device sends a second response information; correspondingly, the first device receives the second response information. The second response information may indicate a first sensing resource, or it may indicate a refusal to fulfill the second sensing requirement.

[0047] In one possible design, if the second response information indicates the first sensing resource, the second response information also indicates at least one of the following: a transmission and reception mode for sensing by at least one terminal; or, an area sensed by at least one terminal.

[0048] In one possible design, if the second response information indicates that the second sensing need is refused to be fulfilled, the second response information also indicates at least one of the following: the reason for the refusal; recommended and / or not recommended sensing resources; or, the sensing need that can be fulfilled.

[0049] In one possible design, the reasons for rejection include at least one of the following: insufficient time domain resources; insufficient frequency domain resources; insufficient spatial domain resources; insufficient code domain resources; insufficient power domain resources; no terminal for sensing; or, the terminal does not meet the second sensing requirement.

[0050] In one possible design, the sensing and management network element sends first information; correspondingly, the first device receives the first information from the sensing and management network element. Alternatively, the second device sends first information; correspondingly, the first device receives first information from the second device.

[0051] In one possible design, the first sensing requirement includes at least one of the following: sensing QoS or SLA; the type of sensing data; the time of sensing; or, the area of ​​sensing.

[0052] In one possible design, the type of sensing data includes at least one of the following: I / Q signal, RAV spectrum information, CFR information, point cloud information, or sensing target information.

[0053] Thirdly, this application provides a communication device. In one possible design, the communication device can be a logic unit or a device within a logic unit (e.g., a module, communication module, circuit or chip responsible for communication functions, chip system, or processor), or it can be an access network device or a device within an access network device (e.g., a module, communication module, circuit or chip responsible for communication functions, chip system, or processor). The communication device has the functionality to implement the first aspect described above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or hardware executing corresponding software.

[0054] In one possible design, the communication device includes an interface unit and a processing unit. The interface unit can be used to transmit and receive signals to enable communication between the communication device and other devices; the processing unit can be used to perform some internal operations of the communication device. The functions performed by the processing unit and the interface unit can correspond to the operations described in the first aspect above.

[0055] In one possible design, the communication device includes a processor. The processor is capable of executing computer programs or instructions that, when executed, cause the communication device to implement the methods in any of the possible designs described in the first aspect above.

[0056] In one possible design, the communication device includes a processor and a memory, the memory of which can store the necessary computer programs or instructions for implementing the functions described in the first aspect above. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design of the first aspect above.

[0057] In one possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and to perform the methods in any possible design of the first aspect described above.

[0058] Fourthly, this application provides a communication system that may include at least one of a first device, a second device, and a sensing management network element. Optionally, the communication system may further include a terminal. The first device may execute the communication method provided in the first aspect or may execute the operation of the first device in the second aspect; the second device may execute the operation of the second device in the second aspect; the sensing management network element may execute the operation executed by the sensing management network element in the second aspect; and the terminal may execute the operation of the terminal in the second aspect.

[0059] Fifthly, this application provides a computer-readable storage medium storing a computer program or instructions, wherein when the computer program or instructions are executed, the method in any of the possible designs in the first aspect described above is implemented.

[0060] Sixthly, this application provides a computer program product including computer program code, wherein when the computer program code is run, the method in any of the possible designs in the first aspect described above is implemented.

[0061] In a seventh aspect, this application provides a chip for reading a computer program stored in a memory to execute the method in any of the possible designs in the first aspect described above.

[0062] The technical effects that can be achieved by any of the second to seventh aspects mentioned above can be described with reference to the technical effects that can be achieved by any possible design in the first aspect mentioned above. Repeated parts will not be discussed. Attached Figure Description

[0063] Figure 1A Architecture diagrams of several communication systems provided in the embodiments of this application;

[0064] Figures 1B to 1C Schematic diagrams of several access network devices provided in the embodiments of this application;

[0065] Figure 2 Several schematic diagrams illustrating the interaction between the first device and the sensing management network element provided in the embodiments of this application;

[0066] Figure 3 Several schematic diagrams illustrating the interaction between the first device and the third device provided in the embodiments of this application;

[0067] Figure 4 Several schematic diagrams illustrating the interaction between the second device and the sensing management network element provided in the embodiments of this application;

[0068] Figure 5 Several other schematic diagrams illustrating the interaction between the first device and the sensing management network element provided in the embodiments of this application;

[0069] Figure 6 Several other schematic diagrams illustrating the interaction between the second device and the sensing management network element provided in the embodiments of this application;

[0070] Figure 7 A schematic diagram of an integrated communication and sensing scenario provided in an embodiment of this application;

[0071] Figure 8 Schematic diagrams of several sensing scenarios provided in the embodiments of this application;

[0072] Figure 9 A flowchart illustrating the first communication method provided in this application embodiment;

[0073] Figures 10 to 17 Flowcharts of several communication methods provided in the embodiments of this application;

[0074] Figure 18 A structural diagram of a communication device provided in an embodiment of this application;

[0075] Figure 19 This is a structural diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0076] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. The technical solutions in the embodiments of this application can be applied to various communication systems, such as fourth-generation (4G) mobile communication systems (e.g., Long Term Evolution (LTE) systems), fifth-generation (5G) mobile communication systems (e.g., New Radio (NR) systems), or future communication systems. The methods provided in the embodiments of this application can be applied to terrestrial network communication systems or non-terrestrial network (NTN) communication systems. NTN communication systems can be, for example, satellite communication systems, and may also include unmanned aerial vehicles (UAVs), high altitude platform stations (HAPS), and other aerial access network equipment; this application does not limit these aspects.

[0077] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0078] To facilitate understanding of the embodiments of this application, Figure 1AA possible, non-limiting system schematic diagram is shown. For example... Figure 1A As shown, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 10 may also include an Internet 300.

[0079] RAN 100 includes at least one RAN node (such as...) Figure 1A 110a and 110b, collectively referred to as 110) and at least one terminal (such as Figure 1A RAN 100, denoted as RAN 120a-120j, is collectively referred to as RAN 120. RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 1A (Not shown in the image). Terminal 120 is connected to RAN node 110 wirelessly. RAN node 110 is connected to core network 200 wirelessly or via wired connection. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

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

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

[0082] RAN nodes can also be described in different ways, such as access network equipment. Unless otherwise specified in this application, access network equipment will be used as the term.

[0083] In one possible scenario, access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission point (TP), an access point (AP), a transmission reception point (TRP), a mobile switching center, a next-generation NodeB (gNB), a next-generation base station in a future communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc. Access network equipment can also be a macro base station (such as...). Figure 1A 110a), micro base stations or indoor stations (such as Figure 1A The access network device can be a relay node or donor node (as described in section 110b), or a wireless controller, satellite, drone, balloon, or aircraft in a CRAN scenario. Optionally, the access network device can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the access network device functions.

[0084] In another possible scenario, multiple access network devices collaborate to assist the terminal in achieving wireless access, with each device implementing a portion of the base station's functions. For example, the access network devices can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be separate entities or included in the same network element, such as a baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). For example, Figure 1B As shown, multiple access network devices cooperate to assist the terminal in achieving wireless access. These multiple access network devices may include CU, DU, and RU. The CU may include CU-CP and CU-UP.

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

[0086] Optionally, when multiple access network devices cooperate to assist the terminal in achieving wireless access, each access network device implements a portion of the protocol layer functions in the base station.

[0087] In some examples, such as Figure 1CAs shown in (a), the CU implements the functions of the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, and the service data adaptation protocol (SDAP) layer, while the DU implements the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The CU and DU communicate via the F1 interface.

[0088] In other examples, such as Figure 1C As shown in (b), CU-CP can implement the functions of the RRC layer and the PDCP layer control plane (PDCP-C), CU-UP can implement the functions of the SDAP layer and the PDCP layer user plane (PDCP-U), and DU can implement the functions of the RLC layer, MAC layer, and PHY layer. CU-CP and DU communicate through the F1-C interface, CU-UP and DU communicate through the F1-U interface, and CU-CP and CU-UP communicate through the E1 interface.

[0089] In some other examples, the correspondence between network elements in the ORAN system and their implementable protocol layer functions can be found in Table 1 below.

[0090] Table 1

[0091]

[0092] The PHY-high function may include at least one of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation; the PHY-low function may include at least one of the following: fast Fourier transform (FFT) / inverse fast Fourier transformation (iFFT) transformation, digital beamforming, or extraction and filtering of the physical random access channel (PRACH).

[0093] A terminal can also be referred to as terminal equipment, user equipment (UE), mobile station, mobile terminal, wireless terminal equipment, subscriber unit, subscriber station, mobile station, remote station, user terminal, user agent, or user device. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. Wearable devices, also known as wearable smart devices or smart wearable devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables. Terminals used in vehicles are called in-vehicle terminal devices, which are also known as on-board units (OBUs).

[0094] For example, a terminal may include a mobile phone (or "cellular" phone), a computer with a mobile terminal device, or a portable, pocket-sized, handheld, or computer-embedded mobile device. For instance, a terminal may be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or other similar devices. A terminal may also include restricted devices, such as devices with limited power consumption, limited storage capacity, or limited computing power. For example, a terminal may be an information sensing device such as a barcode scanner, radio frequency identification (RFID), a sensor, a global positioning system (GPS), or a laser scanner. The embodiments of this application do not limit the device form of the terminal.

[0095] In this application, core network equipment refers to equipment in the core network that provides service support to terminals. Examples of core network equipment include: access and mobility management function (AMF) entities, session management function (SMF) entities, and user plane function (UPF) entities, which are not listed here. The AMF entity is responsible for terminal access management and mobility management; the SMF entity is responsible for session management, such as user session establishment; and the UPF entity can be a user plane functional entity, primarily responsible for connecting to external networks. It should be noted that in this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and similarly, an SMF entity can also be called an SMF network element or an SMF functional entity.

[0096] This application may be applied to scenario 1 and / or scenario 2.

[0097] Scenario 1: The communication system in Scenario 1 may include a sensing management network element, a first device on the access network side, and a second device on the access network side. Optionally, the communication system may also include a third device on the access network side. The first device may be a first logical unit in the access network or a device within the first logical unit (e.g., a module, communication module, circuit, chip (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor). The first logical unit may be used for sensing, or it may be used to manage sensing. The second device may be a second logical unit in the access network or a device within the second logical unit (e.g., a module, communication module, circuit, chip (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor). Optionally, the second logical unit may be used for communication, or it may be used to manage communication. The third device may be a third logical unit in the access network or a device within the third logical unit (e.g., a module, communication module, circuit, chip (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor). The third device can be used to receive and / or transmit signals (e.g., communication signals and / or sensing signals).

[0098] For example, the first logical unit may be a sensing unit (SU), which can implement some of the functions of the base station. The second logical unit may include a CU and / or a DU. The third logical unit may be a RU. It should be understood that the SU may also have other names, as long as it has the same function, it is within the scope of protection of this application.

[0099] Optionally, in scenario 1, there can be multiple interaction methods between the first device and the sensing management network element, such as at least one of methods a1 to a8. The interaction method between the first device and the sensing management network element for control plane information and the interaction method for user plane (or data plane) information (e.g., sensing data) can be the same or different. The following explanation uses SU as an example of the first device.

[0100] Method a1: The perception management network element is an independent network element in the core network (e.g., SF). Figure 2 Example (a) shows the SF as an example of the sensing and management network element. Figure 2 As shown in (a), the SU can interact directly with the SF; or, there is a direct connection between the SU and the SF, through which they can interact. Optionally, in this mode, both control plane information and user plane information between the SF and the SU can be transmitted through this direct connection.

[0101] Method a2: The perception management network element is an independent network element in the core network (e.g., SF). Figure 2 Example (b) shows the SF as an example of the sensing and management network element. Figure 2 As shown in (b), SU can access core network equipment other than SF. Figure 2 (b) of the above is illustrated using AMF and / or UPF as examples) and the second device ( Figure 2 (As illustrated in (b) of the diagram, CU and / or DU are used as examples) interact with SF. For example, control plane information between SU ​​and SF can be forwarded via CU and AMF; and / or, user plane information between SU ​​and SF can be forwarded via CU and UPF. Also, for example, control plane information between SU ​​and SF can be forwarded via DU, CU, and AMF; and / or, user plane information between SU ​​and SF can be forwarded via DU, CU, and UPF. Yet another example, control plane information between SU ​​and SF can be forwarded via DU and AMF; and / or, user plane information between SU ​​and SF can be forwarded via DU and UPF.

[0102] Method a3: The perception management network element is an independent network element in the core network (e.g., SF). Figure 2 (c) in the example uses the SF as the sensing and management network element. Figure 2 As shown in (c), the SU can be accessed via the second device ( Figure 2(c) In this example, CU and / or DU are used to illustrate the interaction with SF. For example, there is a direct connection between SU ​​and CU; or, SU can be directly connected to CU. SU can interact with SF through CU. Alternatively, there is a direct connection between SU ​​and DU; or, SU can be directly connected to DU. SU can interact with SF through DU. Yet another example, there is a direct connection between SU ​​and DU; or, SU can be directly connected to DU. SU can interact with SF through DU and CU. Optionally, in this method, the interaction methods for control plane information and user plane information between SU ​​and SF can be the same.

[0103] Method a4: The sensing and management network element is a third-party server ( Figure 2 (d) is referred to as the perception server. For example... Figure 2 As shown in (d), the SU can directly interact with the perception server; or, there is a direct connection between the SU and the perception server, through which they can interact. Optionally, in this mode, both control plane information and user plane information between the SU and the perception server can be transmitted through this direct connection.

[0104] Method a5: The sensing and management network element is a third-party server ( Figure 2 (e) in the text refers to the perception server. For example... Figure 2 As shown in (e), the SU can be accessed through the core network equipment ( Figure 2 (e) is illustrated using AMF and / or UPF as examples) and the second device ( Figure 2 (e) In this example, CU and / or DU are used to illustrate the interaction with the perception server. The core network devices and the perception server can interact via an application programming interface (API). For example, control plane information between the SU and the perception server can be forwarded via CU and AMF; and / or, user plane information between the SU and the perception server can be forwarded via CU and UPF. Alternatively, control plane information between the SU and the perception server can be forwarded via DU, CU, and AMF; and / or, user plane information between the SU and the perception server can be forwarded via DU, CU, and UPF. Again, for example, control plane information between the SU and the perception server can be forwarded via DU and AMF; and / or, user plane information between the SU and the perception server can be forwarded via DU and UPF.

[0105] Method a6: The sensing and management network element is a third-party server ( Figure 2 (in section (f), it is referred to as the perception server). For example... Figure 2 As shown in (f), the SU can be accessed via the second device ( Figure 2(f) In this example, CU and / or DU are used to illustrate the interaction with the perception server. For example, there is a direct connection between SU ​​and CU; or, SU can directly connect to CU. SU can interact with the perception server through CU. Alternatively, there is a direct connection between SU ​​and DU; or, SU can directly connect to DU. SU can interact with the perception server through DU. Yet another example, there is a direct connection between SU ​​and DU; or, SU can directly connect to DU. SU can interact with the perception server through both DU and CU. Optionally, in this method, the interaction methods for control plane information and user plane information between SU ​​and perception server can be the same.

[0106] Method a7: The sensing management network element can be a sensing function device integrated in the core network equipment. Figure 2 Example (g) illustrates a sensing management network element that is a sensing function device integrated into the AMF and / or UPF. Figure 2 As shown in (g), the SU can directly interact with the AMF and / or UPF; or, a direct connection exists between the SU and the AMF and / or UPF, through which the SU and the AMF and / or UPF can interact. For example, perception-related control surface information between the SU and the AMF can be transmitted via the direct connection between the SU and the AMF; and / or, perception-related user surface information (e.g., perception data) between the SU and the UPF can be transmitted via the direct connection between the SU and the UPF.

[0107] Method a8: The sensing management network element can be a sensing function device integrated in the core network equipment. Figure 2 Example (h) illustrates a sensing management network element that is a sensing function device integrated in the AMF and / or UPF. For instance... Figure 2 As shown in (h), SU can be accessed via the second device ( Figure 2 (h) In this example, CU and / or DU are used to illustrate the interaction with AMF and / or UPF. For example, perception-related control plane information between SU ​​and AMF can be forwarded through CU; and / or, perception-related user plane information (e.g., perception data) between SU ​​and UPF can be forwarded through CU. Also, for example, perception-related control plane information between SU ​​and AMF can be forwarded through DU and CU; and / or, perception-related user plane information (e.g., perception data) between SU ​​and UPF can be forwarded through DU and CU. Yet another example, perception-related control plane information between SU ​​and AMF can be forwarded through DU; and / or, perception-related user plane information (e.g., perception data) between SU ​​and UPF can be forwarded through DU.

[0108] Optionally, when the first device and the sensing management network element interact via mode a2, mode a5, or mode a8, the second device and the AMF may include two types of interfaces (e.g., the CU and the AMF may include two interfaces), one type of interface for communication and the other type of interface for sensing; or, the second device and the AMF may include one interface (e.g., the CU and the AMF may include one interface), on which a portion of the logical links are used for communication and another portion of the logical links are used for sensing; or, the second device and the AMF may include one interface (e.g., the CU and the AMF may include one interface), on which data packets transmitted may contain or be associated with information indicating the data type included in the data packet, such as sensing data, communication data, or other data besides sensing data and communication data.

[0109] Optionally, when the first device and the sensing management network element interact via mode a2, mode a5, or mode a8, the second device and the UPF may include two types of interfaces (e.g., the CU and the UPF may include two interfaces), one type of interface for communication and the other type of interface for sensing; or, the second device and the UPF may include one interface (e.g., the CU and the UPF may include one interface), on which a portion of the logical links are used for communication and another portion of the logical links are used for sensing; or, the second device and the UPF may include one interface (e.g., the CU and the UPF may include one interface), on which the data packets transmitted may contain or be associated with information indicating the data type included in the data packet, such as sensing data, communication data, or other data besides sensing data and communication data.

[0110] Optionally, in scenario 1, there can be multiple interaction methods between the first device and the third device, such as at least one of methods b1 to b4. The interaction method between the control plane information and the user plane (or data plane) information (e.g., sensed data) information (the interaction method between the first device and the third device) can be the same or different. The following explanation uses SU as the first device and RU as the third device as an example.

[0111] Method b1: There is a direct connection between SU ​​and CU; or in other words, SU can be directly connected to CU. For example... Figure 3 As shown in (a), the SU can interact with the RU through the CU. Optionally, in this mode, both control plane information and user plane information between the SU and the RU can be forwarded through the CU.

[0112] Method b2: There is a direct connection between SU ​​and CU; or in other words, SU can be directly connected to CU. For example... Figure 3As shown in (b), the SU can interact with the RU through the CU and DU. Optionally, in this mode, both control plane information and user plane information between the SU and RU can be forwarded through the CU and DU.

[0113] Method b3: There is a direct connection between SU ​​and DU; or in other words, SU can be directly connected to DU. For example... Figure 3 As shown in (c), the SU can interact with the RU via the DU. Optionally, in this mode, both control plane information and user plane information between the SU and RU can be forwarded via the DU.

[0114] Method b4: There is a direct connection between SU ​​and RU; or in other words, SU can be directly connected to RU. For example... Figure 3 As shown in (d), the SU can directly interact with the RU; or, there is a direct connection between the SU and the RU, through which they can interact. Optionally, in this mode, both control plane information and user plane information between the SU and the RU can be transmitted through this direct connection.

[0115] Optionally, in scenario 1, there can be multiple interaction methods between the second device and the sensing management network element, such as at least one of methods c1 to c5. The interaction method between the control plane information and the user plane (or data plane) information (e.g., sensing data) between the second device and the sensing management network element can be the same or different.

[0116] Method c1: The perception management network element is an independent network element in the core network (e.g., SF). Figure 4 Example (a) shows the SF as an example of the sensing and management network element. Figure 4 As shown in (a), the second device ( Figure 4 (a) In this example, CU and / or DU can interact directly with SF; or, there is a direct connection between the second device and SF, through which the second device and SF can interact. For example, there is a direct connection between CU and SF, through which CU and SF can interact. Another example is that there is a direct connection between CU and SF, through which DU can interact with SF. Yet another example is that there is a direct connection between DU and SF, through which DU and SF can interact. Optionally, in this method, the interaction methods for control plane information and user plane information between the second device and SF can be the same.

[0117] Method c2: The perception management network element is an independent network element in the core network (e.g., SF). Figure 4 Example (b) shows the SF as an example of the sensing and management network element. Figure 4 As shown in (b) of the diagram, the second device ( Figure 4(b) in the example shows CU and / or DU) can be accessed through core network equipment other than SF. Figure 4 (as illustrated in (b) of the diagram, using AMF and / or UPF as examples) the interaction with SF. For example, control plane information between CU and SF can be forwarded via AMF; and / or, user plane information between CU and SF can be forwarded via UPF. Also, for example, control plane information between DU and SF can be forwarded via CU and AMF; and / or, user plane information between DU and SF can be forwarded via CU and UPF.

[0118] Method c3: The sensing and management network element is a third-party server ( Figure 4 (c) refers to the perception server. Figure 4 As shown in (c), the second device ( Figure 4 (c) In this embodiment, CU and / or DU are shown as examples. The second device can directly interact with the sensing server; or, a direct connection exists between the second device and the sensing server, through which they can interact. For example, a direct connection exists between the CU and the sensing server, through which they can interact. Another example is that a direct connection exists between the CU and the sensing server, and the DU can interact with the sensing server through the CU. Yet another example is that a direct connection exists between the DU and the sensing server, through which they can interact. Optionally, in this method, the interaction methods for control plane information and user plane information between the second device and the sensing server can be the same.

[0119] Method c4: The sensing and management network element is a third-party server ( Figure 4 (d) is referred to as the perception server. For example... Figure 4 As shown in (d) in the diagram, the second device ( Figure 4 (d) in the example shown in section CU and / or DU) can be accessed through core network equipment ( Figure 4 (d) in the example illustrates the interaction with the perception server using AMF and / or UPF. For example, control plane information between the CU and the perception server can be forwarded via AMF; and / or, user plane information between the CU and the perception server can be forwarded via UPF. Also, for example, control plane information between the DU and the perception server can be forwarded via CU and AMF; and / or, user plane information between the DU and the perception server can be forwarded via CU and UPF.

[0120] Method c5: The sensing management network element can be a sensing function device integrated in the core network equipment. Figure 4 Example (e) illustrates a sensing management network element that is a sensing function device integrated into the AMF and / or UPF. Figure 4 As shown in (e), the second device ( Figure 4(e) In this example, CU and / or DU can be directly connected to AMF and / or UPF; or, a direct connection exists between the second device and AMF and / or UPF, through which the second device can interact. For example, perception-related control plane information between CU and AMF can be transmitted via a direct connection between AMFs; and / or, perception-related user plane information (e.g., perception data) between CU and UPF can be transmitted via a direct connection between UPFs. Also, for example, perception-related control plane information between DU and AMF can be transmitted via a direct connection between CU and AMF; and / or, perception-related user plane information (e.g., perception data) between DU and UPF can be transmitted via a direct connection between DU and UPF.

[0121] Scenario 2: The communication system in Scenario 2 may include a sensing management network element, a first device on the access network side, and a second device on the access network side. The first device may be a first access network device or a device within the first access network device (e.g., a module, communication module, circuit, chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor). Optionally, the first access network device may include a first logic unit, which can be used for sensing, or the first logic unit can be used for managing sensing. The second device may be a second access network device or a device within the second access network device (e.g., a module, communication module, circuit, chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor). Optionally, the first access network device may be an access network-side device independent of the second access network device.

[0122] For example, the first access network device is a NodeC, and the second access network device is a base station (e.g., a NodeB). It should be understood that NodeC may also have other names, as long as it has the same function, they are all within the scope of protection of this application.

[0123] Optionally, in scenario 2, there can be multiple interaction methods between the first device and the sensing management network element, such as at least one of methods d1 to c8. The interaction method between the first device and the sensing management network element regarding control plane information and the interaction method regarding user plane (or data plane) information (e.g., sensing data) can be the same or different. The following explanation uses NodeC as an example of the first device.

[0124] Method d1: The perception management network element is an independent network element in the core network (e.g., SF). Figure 5 Example (a) shows the SF as an example of the sensing and management network element. Figure 5As shown in (a), the NodeC can interact directly with the SF; or, a direct connection exists between the NodeC and the SF, through which they can interact. Optionally, in this mode, both control plane information and user plane information between the NodeC and the SF can be transmitted through this direct connection.

[0125] Method d2: The perception management network element is an independent network element in the core network (e.g., SF). Figure 5 Example (b) shows the SF as an example of the sensing and management network element. Figure 5 As shown in (b), NodeC can access core network devices other than SF. Figure 5 (b) of the above is illustrated using AMF and / or UPF as examples) and the second device ( Figure 5 (As illustrated in (b) of this paper, NodeB interacts with SF. For example, control plane information between NodeC and SF can be forwarded through NodeB and AMF; and / or, user plane information between NodeC and SF can be forwarded through NodeB and UPF.)

[0126] Method d3: The perception management network element is an independent network element in the core network (e.g., SF). Figure 5 (c) in the example uses the SF as the sensing and management network element. Figure 5 As shown in (c), NodeC can be accessed via a second device ( Figure 5 (C) In this example, NodeB interacts with SF. Optionally, in this method, the interaction methods for control plane information and user plane information between NodeC and SF can be the same.

[0127] Method d4: The sensing and management network element is a third-party server ( Figure 5 (d) is referred to as the perception server. For example... Figure 5 As shown in (d), the NodeC can interact directly with the perception server; alternatively, a direct connection exists between the NodeC and the perception server, through which they can interact. Optionally, in this mode, both control plane information and user plane information between the NodeC and the perception server can be transmitted via this direct connection.

[0128] Method d5: The sensing and management network element is a third-party server ( Figure 5 (e) in the text refers to the perception server. For example... Figure 5 As shown in (e), NodeC can be accessed through core network devices ( Figure 5 (e) is illustrated using AMF and / or UPF as examples) and the second device ( Figure 5(e) In this example, NodeB interacts with the perception server. For instance, control plane information between NodeC and the perception server can be forwarded via NodeB and AMF; and / or, user plane information between NodeC and the perception server can be forwarded via NodeB and UPF.

[0129] Method d6: The sensing and management network element is a third-party server ( Figure 5 (in section (f), it is referred to as the perception server). For example... Figure 5 As shown in (f), NodeC can be accessed via a second device ( Figure 5 (f) in the example shows NodeB interacting with the perception server. Optionally, in this method, the interaction methods for control plane information and user plane information between NodeC and the perception server can be the same.

[0130] Method d7: The sensing management network element can be a sensing function device integrated in the core network equipment. Figure 5 Example (g) illustrates a sensing management network element that is a sensing function device integrated into the AMF and / or UPF. Figure 5 As shown in (g), the NodeC can interact directly with the AMF and / or UPF; or, a direct connection exists between the NodeC and the AMF and / or UPF, through which the NodeC and the AMF and / or UPF can interact. For example, perception-related control plane information between the NodeC and the AMF can be transmitted via the direct connection between the NodeC and the AMF; and / or, perception-related user plane information (e.g., perception data) between the NodeC and the UPF can be transmitted via the direct connection between the NodeC and the UPF.

[0131] Method d8: The sensing management network element can be a sensing function device integrated in the core network equipment. Figure 5 Example (h) illustrates a sensing management network element that is a sensing function device integrated in the AMF and / or UPF. For instance... Figure 5 As shown in (h), NodeC can be accessed via a second device ( Figure 5 (h) In this example, NodeB interacts with AMF and / or UPF. For example, perception-related control plane information between NodeC and AMF can be forwarded through NodeB; and / or, perception-related user plane information (e.g., perception data) between NodeC and UPF can be forwarded through NodeB.

[0132] Optionally, when the NodeC and the sensing management network element interact via mode d2, mode d5, or mode d8, the second device and the AMF may include two types of interfaces: one type for communication and the other for sensing; or, the second device and the AMF may include one interface, on which a portion of the logical links are for communication and another portion for sensing; or, the second device and the AMF may include one interface on which data packets transmitted may contain or be associated with information indicating the data type included in the data packet, such as sensing data, communication data, or other data besides sensing data and communication data.

[0133] Optionally, when the NodeC and the sensing management network element interact via mode d2, mode d5, or mode d8, the second device and the UPF may include two types of interfaces: one type for communication and the other for sensing; or, the second device and the UPF may include one interface, on which a portion of the logical links are for communication and another portion is for sensing; or, the second device and the UPF may include one interface on which data packets transmitted may contain or be associated with information indicating the data type included in the data packet, such as sensing data, communication data, or other data besides sensing data and communication data.

[0134] Optionally, in scenario 2, there can be multiple interaction methods between the second device and the sensing management network element, such as at least one of methods e1 to e5. The interaction method between the control plane information and the user plane (or data plane) information (e.g., sensing data) between the second device and the sensing management network element can be the same or different.

[0135] Method e1: The perception management network element is an independent network element in the core network (e.g., SF). Figure 6 Example (a) shows the SF as an example of the sensing and management network element. Figure 6 As shown in (a), the second device ( Figure 6 (a) In this example, NodeB can directly interact with SF; or, there is a direct connection between the second device and SF, through which the second device and SF can interact. Optionally, in this method, the interaction methods of control plane information and user plane information between the second device and SF can be the same.

[0136] Method e2: The perception management network element is an independent network element in the core network (e.g., SF). Figure 6 Example (b) shows the SF as an example of the sensing and management network element. Figure 6 As shown in (b) of the diagram, the second device ( Figure 6(b) in the example shows NodeB) can be accessed through core network devices other than SF. Figure 6 (As illustrated in (b) of this paper, using AMF and / or UPF as examples) the interaction with SF. For example, control plane information between NodeB and SF can be forwarded via AMF; and / or, user plane information between NodeB and SF can be forwarded via UPF.

[0137] Method e3: The sensing and management network element is a third-party server ( Figure 6 (c) refers to the perception server. Figure 6 As shown in (c), the second device ( Figure 6 (c) In this example, NodeB can directly interact with the sensing server; or, there is a direct connection between the second device and the sensing server, through which they can interact. Optionally, in this method, the interaction methods for control plane information and user plane information between the second device and the sensing server can be the same.

[0138] Method e4: The sensing and management network element is a third-party server ( Figure 6 (d) is referred to as the perception server. For example... Figure 6 As shown in (d) in the diagram, the second device ( Figure 6 (d) In this example, NodeB can be used via core network equipment. Figure 6 (d) in the example illustrates the interaction between the NodeB and the perception server using AMF and / or UPF. For instance, control plane information between the NodeB and the perception server can be forwarded via AMF; and / or, user plane information between the NodeB and the perception server can be forwarded via UPF.

[0139] Method e5: The sensing management network element can be a sensing function device integrated in the core network equipment. Figure 6 Example (e) illustrates a sensing management network element that is a sensing function device integrated into the AMF and / or UPF. Figure 6 As shown in (e), the second device ( Figure 6 (e) In this example, NodeB can interact directly with AMF and / or UPF; or, a direct connection exists between the second device and AMF and / or UPF, through which the second device can interact with AMF and / or UPF. For example, perception-related control plane information between NodeB and AMF can be transmitted via a direct connection between AMFs; and / or, perception-related user plane information (e.g., perception data) between NodeB and UPF can be transmitted via a direct connection between UPFs.

[0140] The communication systems and service scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0141] The relevant terms used in the embodiments of this application will be explained below. It should be noted that these explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by this application.

[0142] 1. Integrated communication and sensing:

[0143] Integrated communication and sensing technology is considered one of the key technologies for expanding the service capabilities of mobile communication networks. The core idea of ​​this technology is to add sensing capabilities to the mobile communication network, building capabilities such as target detection, tracking, and imaging, thereby integrating communication and sensing capabilities into a single network, achieving harmonious coexistence and mutual benefit. Please see [link to relevant documentation]. Figure 7 This is a schematic diagram of an integrated communication and sensing scenario. Figure 7 In the example, solid lines represent communication, and dashed lines represent sensing. Figure 7 As shown, access network devices can sense other objects by transmitting and receiving data on their own, or they can sense other objects while communicating with terminals. Figure 7 The example uses a smartphone as the terminal and drones, pedestrians, and vehicles as the sensing targets.

[0144] Sensing technology can generally be divided into two modes: single-site sensing and dual-site sensing. Single-site sensing refers to a single device that transmits the sensing signal and receives the echo signal. In other words, in single-site sensing, the transmitting device both transmits the sensing signal and receives the echo signal reflected from the surface of the sensing target. Therefore, this single-site sensing mode can also be called a self-transmitting and self-receiving mode, without limitation. Dual-site sensing refers to two different devices that transmit the sensing signal and receive the echo signal. In other words, sensing station A transmits the sensing signal, and the echo signal reflected from the surface of the sensing target is received by sensing station B. Therefore, this dual-site sensing mode can also be called the A-transmitting and B-receiving mode. The echo signal is obtained after the sensing signal passes through the sensing target (e.g., reflection, diffraction, or scattering). Therefore, this echo signal can still be called the sensing signal; the term "received sensing signal" in the following text can be replaced with "received echo signal."

[0145] Optionally, single-site sensing mode can be combined with dual-site sensing mode. For example, some nodes use single-site sensing mode, while others use dual-site sensing mode. Another example is that a node uses single-site sensing mode for a period of time and dual-site sensing mode for another period. Yet another example is that a node uses both single-site and dual-site sensing modes for a period of time. The combination of single-site and dual-site sensing modes can also be called a hybrid transceiver mode; or, in other words, the combination of automatic transmission / transmission mode and A-to-transmit / B-to-receive mode can also be called a hybrid transceiver mode.

[0146] Figure 8 The diagram illustrates a sensing scenario to which embodiments of this application are applicable. Figure 8 The document provides eight sensing scenarios applicable to the embodiments of this application, namely: the scenario where access network device A transmits and receives signals independently, i.e., the scenario where access network device A sends sensing signals and receives echo signals, such as... Figure 8 As shown in (1); the scenario where terminal A transmits and receives signals independently, that is, the scenario where terminal A sends sensing signals and receives echo signals, as shown in (1); Figure 8 As shown in (2) in the diagram; the scenario where access network device A sends a sensing signal and access network device B receives the echo signal, as follows: Figure 8 As shown in (3) in the diagram; the scenario where terminal A sends a sensing signal and terminal B receives the echo signal, as shown in the diagram. Figure 8 As shown in (4) in the diagram; the scenario where access network device A sends a sensing signal and terminal A receives an echo signal, as shown in the diagram. Figure 8 As shown in (5) in the example; the scenario where terminal A sends a sensing signal and access network device A receives the echo signal, as shown in the example. Figure 8 As shown in (6) in the diagram; under the control of access network device C, access network device A sends sensing signals and access network device B receives echo signals, as in the following scenario. Figure 8 As shown in (7) in the diagram; under the control of access network device A, the scenario in which terminal A sends a sensing signal and terminal B receives the echo signal is as follows: Figure 8 As shown in (8) of the table. Figure 8 The example shown uses a vehicle as the sensing target and a smartphone as the terminal.

[0147] The sensing target can also be referred to as a target, a detected target, a sensed object, a sensed device, etc., without limitation. The sensing target can be any tangible object in the environment capable of reflecting, diffracting, or scattering electromagnetic waves. For example, the sensing target can be a stationary object such as a mountain, forest, or building. Alternatively, the sensing target can be a mobile object such as a vehicle, drone, pedestrian, or terminal. This application does not limit the specific implementation form of the sensing target.

[0148] The sensing result can also be referred to as the detected result, the detected data, or the detected data, etc., without limitation. The sensing result can be the result obtained by the receiving device processing the echo signal. For example, the sensing result may include at least one of the following: the position of the sensed target, the velocity of the sensed target, the distance from the sensed target to the receiving device, the distance from the sensed target to the transmitting device, the direction or angle of the sensed target, or the intensity of the echo signal, etc.

[0149] 2. In this application, the time unit may be an absolute time or a unit of time-domain resources. For example, the time unit may include at least one of the following: a system frame, a subframe, a millisecond (ms), a slot, or a symbol, etc. The symbol may be a time-domain symbol (e.g., an orthogonal frequency division multiplexing (OFDM) symbol), etc.

[0150] A frequency unit can be an absolute frequency or a unit of frequency domain resources. For example, a frequency unit may include at least one of the following: a subcarrier, a resource element (RE), a resource block (RB), or a resource block group (RBG), etc.

[0151] 3. In this application, the sensing data of a certain device may be the original data sensed by the device, or the data after the device processes the original sensed data (e.g., dimension alignment, upsampling, downsampling or one or more), or the features obtained after the original sensed data is processed by a neural network, or the sensing data obtained by the device through fusion operation.

[0152] 4. In this application, "instruction" or "for instruction" can include explicit instruction (or direct instruction) and implicit instruction (or indirect instruction). When describing information for instructing A, it can include whether the information explicitly instructs A or implicitly instructs A, but does not necessarily mean that the information carries A.

[0153] The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different, without limitation.

[0154] In the embodiments of this application, "information" can be an explicit indication, that is, a direct indication through signaling, or obtained by combining other rules or parameters with parameters indicated by signaling, or by deduction. It can also be an implicit indication, that is, obtained based on rules or relationships, or based on other parameters, or by deduction. No limitation is imposed.

[0155] 5. In this application, communication between different devices can refer to direct communication between different devices (i.e., without the need for relaying or forwarding by other devices), or communication between different devices through other devices (i.e., requiring relaying or forwarding by other devices), or communication between a functional unit within a device and other devices through another functional unit. For example, "sending information to…(terminal)" can be understood as the destination of the information being the terminal, and may include sending information directly or indirectly to the terminal. "Receiving information from…(terminal)" can be understood as the source of the information being the terminal, and may include receiving information directly or indirectly from the terminal. Information may undergo necessary processing between the source and destination ends, such as format changes, digital-to-analog conversion, amplification, filtering, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood in a similar way, and will not be elaborated further here.

[0156] 6. In this application, the words “exemplary,” “for example,” “e.g.,” and “example” are used to indicate examples, illustrations, or descriptions, and are not intended to limit the scope of protection of this application. It should be understood that the examples in this application may also be implemented in other ways.

[0157] 7. In this application, any two of the programs, instructions, and code can be substituted for one another.

[0158] 8. In this application, the processing of the perceived data may include, but is not limited to, at least one of the following: fusion processing or perceived data calculation.

[0159] Currently, in the ISAC system, terminal participation in sensing can improve sensing performance. For example, if terminals send and / or receive sensing signals, the sensing range can be expanded. Also, terminals can provide sensing data. By fusing the sensing data from terminals—for example, fusing terminal sensing data with sensing data from the access network side, or fusing sensing data from multiple terminals—sensing accuracy can be improved, thereby better guaranteeing sensing QoS or SLA.

[0160] When terminals are involved in sensing, how to process the sensing data from those terminals requires further research.

[0161] This application provides a communication method. Figure 9 This is a flowchart illustrating the communication method provided in the embodiments of this application.

[0162] Figure 9 The present application uses a sensing management network element, a first device on the access network side, and a second device on the access network side as examples to illustrate the execution subjects of this interaction, but this application does not limit the execution subjects of this interaction. For example, the sensing management network element can be replaced by a device in the sensing management network element (e.g., a module, communication module, circuit, chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor), or it can be replaced by a logical node, logical module, or software that can implement all or part of the functions of the sensing management network element.

[0163] In some examples, the sensing management network element can be a core network device. For example, the sensing management network element can be an independent network element (such as SF) in the core network. The SF can also have other names, such as sensing management function, etc., as long as it has the same function, it is within the scope of protection of this application. For another example, the sensing management network element can be integrated with a core network device in one device. For instance, the sensing management network element can be a sensing function device integrated into the core network device, or the sensing management network element and the core network device can be different devices in one device. The core network device can be, for example, AMF and / or UPF. In other examples, the sensing management network element can be a third-party server. Optionally, the third-party server can be outside the core network, or the third-party server may not be a core network device. It should be understood that the sensing management network element can have other names, such as sensing network element, sensing server, or sensing network element / server, as long as it has the same function, it is within the scope of protection of this application.

[0164] like Figure 9 As shown, the method includes:

[0165] S901: At least one terminal sends sensing data from at least one terminal; correspondingly, the first device receives sensing data from at least one terminal.

[0166] The first terminal can be any of at least one terminal. The following explanation uses the first terminal as an example to illustrate S901.

[0167] In some possible ways, such as in scenario 1 above, the first terminal can send its sensing data to the first device sequentially through the third device and the second device. For example, the third device is RU, the second device includes CU and DU, and the first device is SU. The first terminal can send its sensing data to the SU sequentially through RU, DU, and CU. Another example: the third device is RU, the second device includes CU, and the first device is SU. The first terminal can send its sensing data to the SU sequentially through RU and CU. Yet another example: the third device is RU, the second device includes DU, and the first device is SU. The first terminal can send its sensing data to the SU sequentially through RU and DU.

[0168] In other possible approaches, as described in scenario 1 above, the first terminal can send its sensing data to the first device via a third device. For example, the third device is RU, and the first device is SU. The first terminal can send its sensing data to the SU via RU.

[0169] In another possible approach, as described in scenario 2 above, the first terminal can send its sensing data to the first device via the second device. For example, the second device is a NodeB, and the first device is a NodeC. The first terminal can send its sensing data to the NodeC via the NodeB.

[0170] It should be understood that the timing at which different terminals in at least one terminal send sensing data can be the same or different, without restriction.

[0171] For example, the type of sensed data from at least one terminal may include at least one of the following: I / Q signals, CFR information, RAV spectrum information, or point cloud information. It should be understood that the types of sensed data from different terminals within the at least one terminal may be the same or different.

[0172] S902: The first device can process the sensing data of at least one terminal based on whether the location of at least one terminal has been obtained.

[0173] In some examples, the location of at least one terminal may be the actual location of that at least one terminal.

[0174] In other examples, the location of the at least one terminal may be a reference location of the at least one terminal. The reference location of the at least one terminal differs from, but corresponds to (or is related to) the actual location of the at least one terminal. For example, the distance between the reference location and the actual location of the at least one terminal is a first offset value, or the distance between the reference location and the actual location of the at least one terminal is less than (or less than or equal to) the first offset value. The first offset value may be preset, such as as specified by a protocol; or it may be determined by the first device; or it may be notified to the first device by other devices (e.g., core network equipment). The reference location and / or the first offset value may also have other names, as long as they have the same function, they are all within the scope of protection of this application.

[0175] S902 can be implemented in multiple ways, such as method f1 and / or method f2.

[0176] Method f1: When the location of at least one terminal is obtained, the first device can process the sensing data of at least one terminal based on the location of at least one terminal.

[0177] In some implementations, the first device may perform fusion processing on the sensed data of at least one terminal based on the location of at least one terminal. This fusion processing may include, for example, at least one of the following: fusion processing of I / Q signals, fusion processing of CFR information, fusion processing of RAV spectrum information, or fusion processing of point cloud information.

[0178] For example (hereinafter referred to as Example 1), the sensing data received by the first device from at least one terminal is of type I / Q signal. The first device can perform fusion processing on the sensing data of at least one terminal according to the location of at least one terminal to obtain fused sensing data of type I / Q signal.

[0179] For example (hereinafter referred to as Example 2), the sensing data received by the first device from at least one terminal is of type I / Q signal. The first device can process the sensing data from at least one terminal to obtain sensing data of at least one terminal of type CFR information; then, the first device can perform fusion processing on the sensing data of at least one terminal of type CFR information according to the location of at least one terminal to obtain fused sensing data of type CFR information. Optionally, the CFR information in this example can be replaced with RAV spectrum information.

[0180] For example, the first device receives sensing data from at least one terminal, which is of I / Q signal type. The first device can process the sensing data from at least one terminal to obtain sensing data of at least one terminal of type CFR information, and process the sensing data of at least one terminal of type CFR information to obtain sensing data of at least one terminal of type point cloud information. Then, the first device can perform fusion processing on the sensing data of at least one terminal of type point cloud information according to the location of at least one terminal to obtain fused sensing data of type point cloud information. Optionally, the CFR information in this example can be replaced with RAV spectral information.

[0181] For example, the first device receives sensing data from at least one terminal of type CFR information. The first device can perform fusion processing on the sensing data of at least one terminal based on the location of the terminal to obtain fused sensing data of type CFR information. Optionally, the CFR information in this example can be replaced with RAV spectral information.

[0182] For example, the first device receives sensing data from at least one terminal of type CFR information. The first device can process the sensing data from at least one terminal of type CFR information to obtain sensing data from at least one terminal of type point cloud information; then, the first device can perform fusion processing on the sensing data from at least one terminal of type point cloud information according to the location of at least one terminal to obtain fused sensing data of type point cloud information. Optionally, the CFR information in this example can be replaced with RAV spectral information.

[0183] For example, the first device receives sensing data from at least one terminal that is of the type of point cloud information. The first device can perform fusion processing on the sensing data of at least one terminal that is of the type of point cloud information according to the location of at least one terminal to obtain fused sensing data of the type of point cloud information.

[0184] It should be understood that this implementation is illustrated using the example of fusing sensing data from at least one terminal. In practical applications, the first device may also perform other processing on the sensing data from at least one terminal besides fusing, based on the location of at least one terminal, without limitation.

[0185] In other implementations, the first device may perform fusion processing on the sensing data of at least one terminal and the third sensing data sensed by the access network side based on the location of at least one terminal. For details, please refer to the above description of "the first device may perform fusion processing on the sensing data of at least one terminal based on the location of at least one terminal", except that "sensing data of at least one terminal" is replaced with "sensing data of at least one terminal and the third sensing data sensed by the access network side", which will not be repeated here.

[0186] In some examples, such as Scenario 1 above, the third sensing data perceived by the access network side can be the third sensing data perceived by the third device. The third device can send the third sensing data; correspondingly, the first device can receive the third sensing data from the third device, thereby enabling the fusion of sensing data from at least one terminal and the third sensing data.

[0187] In other examples, such as scenario 2 above, the third sensing data perceived by the access network side can be the third sensing data perceived by the second device. The second device can send the third sensing data; correspondingly, the first device can receive the third sensing data from the second device, thereby enabling the fusion of sensing data and third sensing data from at least one terminal.

[0188] Optionally, the types of sensing data from at least one terminal and the third sensing data received by the first device may be the same or different.

[0189] In some examples, when the types of sensing data and third sensing data received by the first device from at least one terminal are the same, the first device can directly fuse the sensing data and third sensing data of at least one terminal based on the location of at least one terminal. Alternatively, the first device can process the sensing data and third sensing data of at least one terminal of the first type into sensing data of the second type, and then fuse the sensing data and third sensing data of the second type. The first type and the second type may be different. For example (hereinafter referred to as Example 3), the types of sensing data and third sensing data received by the first device from at least one terminal are both I / Q signals. The first device can directly fuse the sensing data and third sensing data of at least one terminal of the I / Q signal type based on the location of at least one terminal to obtain fused sensing data of the I / Q signal type. Another example (hereinafter referred to as Example 4), the types of sensing data and third sensing data received by the first device from at least one terminal are both I / Q signals. The first device can process the sensing data of at least one terminal of type I / Q signal to obtain the sensing data of at least one terminal of type CFR information, and process the third sensing data of type I / Q signal to obtain the third sensing data of type CFR information. Then, the first device can perform fusion processing on the sensing data of at least one terminal of type CFR information and the third sensing data of type CFR information according to the location of at least one terminal to obtain fused data of type CFR information.

[0190] In other examples, when the types of sensing data from at least one terminal and the third sensing data received by the first device are different, the first device may process the sensing data from at least one terminal and / or the third sensing data to make the types of the sensing data from at least one terminal and the third sensing data the same. Then, the first device may perform fusion processing on the sensing data from at least one terminal and the third sensing data based on the location of at least one terminal. For example, the type of sensing data from at least one terminal received by the first device is I / Q signal, and the type of the third sensing data received by the first device is CFR information. The first device may process the sensing data from at least one terminal of type I / Q signal to obtain sensing data from at least one terminal of type CFR information. Then, the first device may perform fusion processing on the sensing data from at least one terminal of type CFR information and the third sensing data of type CFR information based on the location of at least one terminal to obtain fused data of type CFR information. For another example (hereinafter referred to as Example 5), the type of sensing data from at least one terminal received by the first device is I / Q signal, and the type of the third sensing data received by the first device is CFR information. The first device can process sensing data from at least one terminal of type I / Q signal to obtain sensing data of at least one terminal of type point cloud information, and process third sensing data of type CFR information to obtain third sensing data of type point cloud information. Then, the first device can perform fusion processing on the at least one terminal of type point cloud information and the third sensing data of type point cloud information according to the location of at least one terminal to obtain fused data of type point cloud information. For example, the sensing data received by the first device from at least one terminal is of type CFR information, and the third sensing data received by the first device is of type I / Q signal. The first device can process the third sensing data of type I / Q signal to obtain third sensing data of type CFR information. Then, the first device can perform fusion processing on the at least one terminal of type CFR information and the third sensing data of type CFR information according to the location of at least one terminal to obtain fused data of type CFR information.

[0191] It should be understood that this implementation is illustrated using the example of fusing sensing data from at least one terminal and third sensing data. In practical applications, the first device may also perform other processing besides fusing sensing data from at least one terminal and third sensing data based on the location of at least one terminal, without limitation.

[0192] Through method f1, the first device on the access network side can process the sensing data of at least one terminal based on the location of at least one terminal, thereby enabling the access network side to process the terminal's sensing data. Compared with processing the terminal's sensing data through core network equipment or a third-party server, this method can reduce the processing latency of the terminal's sensing data.

[0193] Furthermore, in this method, the location of at least one terminal acquired by the first device can be a reference location for at least one terminal, rather than the actual location of at least one terminal. The actual location of the terminal is a matter of terminal privacy. Therefore, this method can reduce the processing latency of the terminal's sensing data and improve the performance of sensing processing while ensuring the privacy of at least one terminal.

[0194] Method f2:

[0195] Method f2 may include steps A1 to A2:

[0196] Step A1: If the location of at least one terminal is not obtained, the first device may send sensing data of at least one terminal; correspondingly, the sensing management network element may receive the sensing data of the at least one terminal.

[0197] In some implementations, in scenario 1 above, the first device can send sensing data of at least one terminal to the sensing management network element through at least one of the methods a1 to a8.

[0198] In other implementations, in scenario 2 above, the first device can send sensing data of at least one terminal to the sensing management network element through at least one of the methods d1 to d8.

[0199] Optionally, in step A1, the first device may also send information to the sensing management network element indicating the type of sensing data from at least one terminal. In this way, the sensing management network element can accurately determine the type of sensing data from at least one terminal.

[0200] For example, in step A1, the type of the sensing data of at least one terminal may include at least one of the following: RAV spectral information or point cloud information.

[0201] Step A2: The sensing management network element can send the first sensing data; correspondingly, the first device can receive the first sensing data.

[0202] In some implementations, in scenario 1 above, the perception management network element can send the first perception data to the first device through at least one of the methods a1 to a8.

[0203] In other implementations, in scenario 2 above, the perception management network element can send the first perception data to the first device through at least one of the methods d1 to d8.

[0204] The first sensing data is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal. Optionally, the first sensing data may be obtained by a sensing management network element processing the sensing data of at least one terminal based on the location of at least one terminal; or, the sensing management network element may process the sensing data of at least one terminal based on the location of at least one terminal to obtain the first sensing data. For details, please refer to the description of "the first device may process the sensing data of at least one terminal based on the location of at least one terminal" in method f1, except that the first device is replaced by a sensing management network element, which will not be repeated here.

[0205] Optionally, in step A2, the sensing management network element may also send information to the first device indicating the type of the first sensing data. In this way, the first device can accurately determine the type of the first sensing data.

[0206] For example, in step A2, the type of the first sensed data may include at least one of the following: RAV spectral information or point cloud information.

[0207] In method f2, the first device on the access network side can acquire first sensing data, which is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal. In this method, the access network side may not acquire the location of at least one terminal. The actual location of the terminal is a matter of terminal privacy. Therefore, this method can process the sensing data of at least one terminal while ensuring the privacy of at least one terminal.

[0208] Optionally, in method f2, Figure 9 The method shown may also include step A3:

[0209] Step A3: The first device processes the first sensing data.

[0210] In some implementations, the first device can process the first sensing data of a first type to obtain sensing data of a second type. For example (hereinafter referred to as Example Six), the first sensing data received by the first device is of type I / Q signal. The first device processes the first sensing data to obtain sensing data of type CFR information or RAV spectrum information. Another example (hereinafter referred to as Example Seven), the first sensing data received by the first device is of type I / Q signal. The first device processes the first sensing data to obtain sensing data of type CFR information or RAV spectrum information, and processes the sensing data of type CFR information or RAV spectrum information to obtain sensing data of type point cloud information. Yet another example, the first sensing data received by the first device is of type I / Q signal. The first device processes the first sensing data to obtain sensing data of type CFR information or RAV spectrum information, processes the sensing data of type CFR information or RAV spectrum information to obtain sensing data of type point cloud information, and processes the sensing data of type point cloud information to obtain sensing data of type sensing target information. Yet another example, the first sensing data received by the first device is of type CFR information or RAV spectrum information. The first device processes first sensing data of type CFR information or RAV spectrum information to obtain sensing data of type point cloud information. For example, the first sensing data received by the first device is of type CFR information or RAV spectrum information. The first device processes the first sensing data of type CFR information or RAV spectrum information to obtain sensing data of type point cloud information, and processes the sensing data of type point cloud information to obtain sensing data of type sensing target information.

[0211] In other examples, the first device may perform fusion processing on the first sensing data and the third sensing data sensed by the access network side. For details, please refer to the description in method f1 above that "the first device may perform fusion processing on the sensing data of at least one terminal and the third sensing data sensed by the access network side according to the location of at least one terminal". The only difference is that the sensing data of at least one terminal is replaced with the first sensing data and "according to the location of at least one terminal" is deleted. It will not be repeated here.

[0212] Among some possible ways, Figure 9 The method shown may also include S903:

[0213] S903: The first device receives first instruction information, which indicates whether a terminal is involved in sensing.

[0214] In some implementations, the first device may receive first indication information from the sensing management network element, as shown in S903a. Optionally, the first indication information is determined by the sensing management network element based on sensing requirements (e.g., the first sensing requirements in S906 or S908 below). The specific content of the first sensing requirements will be described in S906 below and will not be elaborated here. For example, if the sensing area in the first sensing requirements includes the area where the terminal is located, the sensing management network element may determine that the first indication information indicates that a terminal is participating in sensing; and / or, if the sensing area in the first sensing requirements does not include the area where the terminal is located, the sensing management network element may determine that the first indication information indicates that no terminal is participating in sensing.

[0215] In other implementations, the first device may receive first indication information from the second device, as shown in S903b. In some examples, the first indication information may be determined by the second device based on sensing resources (e.g., the first sensing resources in S907 or S909 below). For example, if the first sensing resources include sensing resources for a terminal, the second device may determine that the first indication information indicates that a terminal is involved in sensing; and / or, if the first sensing resources do not include sensing resources for a terminal, the second device may determine that the first indication information indicates that no terminal is involved in sensing. In other examples, the first indication information is determined by the second device based on sensing requirements (e.g., the first sensing requirements in S906 or S908 below). For example, if the sensing area in the first sensing requirements includes the area where the terminal is located, the second device may determine that the first indication information indicates that a terminal is involved in sensing; and / or, if the sensing area in the first sensing requirements does not include the area where the terminal is located, the second device may determine that the first indication information indicates that no terminal is involved in sensing.

[0216] Optionally, S903 can be performed before S902. This application does not restrict the execution order of S903 and S901.

[0217] In this manner, the first device can accurately determine whether a terminal is involved in sensing based on the first indication information. Furthermore, in this method, whether a terminal is involved in sensing is indicated by the first indication information, and the first device does not need to perform calculations on whether a terminal is involved in sensing, thereby reducing the computational complexity and power consumption of the first device.

[0218] In other possible approaches, the first device can determine independently whether a terminal is involved in sensing. Optionally, the first device can determine whether a terminal is involved in sensing based on sensing requirements (e.g., the first sensing requirement in S906 below). This first sensing requirement can be notified to the first device by a sensing management network element or a second device. For example, if the sensing area in the first sensing requirement includes the area where the terminal is located, the first device can determine that a terminal is involved in sensing; and / or, if the sensing area in the first sensing requirement does not include the area where the terminal is located, the first device can determine that no terminal is involved in sensing. In this approach, the first device can accurately determine whether a terminal is involved in sensing based on the sensing requirements. Furthermore, in this approach, the presence or absence of a terminal is determined by the first device, and no indication information indicating whether a terminal is involved in sensing needs to be transmitted between the first device and other devices, thereby reducing signaling overhead and saving transmission resources.

[0219] In some implementations, when a terminal is involved in sensing, the first device can send a first request; correspondingly, the sensing management network element can receive the first request. The first request can be used to request the location of at least one terminal. For example, when first indication information indicates that a terminal is involved in sensing, the first device can send the first request to the sensing management network element. Or, for example, when the first device determines on its own that a terminal is involved in sensing, the first device can send the first request to the sensing management network element.

[0220] Optionally, after receiving the first request, the sensing management network element may send information indicating the location of at least one terminal; correspondingly, the first device may receive the information indicating the location of at least one terminal. It should be understood that when the at least one terminal includes multiple terminals, the information indicating the location of different terminals among the at least one terminal may be carried in the same message or in different messages, without limitation. In this way, the first device can accurately determine the location of at least one terminal, thereby enabling the execution of the above-described method f1.

[0221] For example, the first request may include indication information of at least one terminal, such as the identifier of at least one terminal. In this way, the sensing management network element can selectively send information indicating the location of at least one terminal based on the indication information of the at least one terminal, thereby avoiding unnecessary transmission of such information and saving transmission resources.

[0222] In other implementations, when a terminal is involved in sensing, the first device can obtain the location of at least one locally stored terminal, thereby enabling the execution of the above-described method f1.

[0223] It should be understood that the above implementations can be independent or combined with each other. For example, when terminals are involved in sensing, the first device can obtain the location of a first portion of the terminals among at least one locally stored terminals, and request the location of the terminals other than the first portion of terminals among the at least one terminal through a first request.

[0224] In some implementations, when a terminal is involved in sensing but the location of at least one terminal has not been obtained, the first device can send a second request; correspondingly, the sensing management network element can receive the second request. The second request can be used to request first sensing data, the specific content of which can be found in the description of the first sensing data in step A2 above, and will not be repeated here. For example, when the first indication information indicates that a terminal is involved in sensing but the location of at least one terminal has not been obtained, the first device can send a second request to the sensing management network element. As another example, when the first device determines on its own that a terminal is involved in sensing but the location of at least one terminal has not been obtained, the first device can send a second request to the sensing management network element.

[0225] The failure to obtain the location of at least one terminal may include, but is not limited to, one or more of the following situations: the first device does not locally store the location of at least one terminal; after the first device sends the first request, the sensing management network element does not send information indicating the location of at least one terminal; after the first device sends the first request, although the sensing management network element sends information indicating the location of at least one terminal, the first device does not receive such information. Reasons for the first device not receiving information indicating the location of at least one terminal include, for example, a link interruption between the first device and the sensing management network element.

[0226] Optionally, after receiving the second request, the sensing management network element may execute step A2 above. In this way, the sensing management network element can send the first sensing data to the first device in a targeted manner based on the request of the first device, thereby avoiding unnecessary transmission of the first sensing data and thus saving transmission resources.

[0227] Among some possible ways, Figure 9 The method shown may also include S904:

[0228] S904: The first device acquires the second sensing data.

[0229] In some implementations, when the location of at least one terminal is obtained, the second sensing data may be the result of processing the sensing data of at least one terminal in method f1; or, the second sensing data may be obtained based on the sensing data of at least one terminal; or, the second sensing data may correspond to (or be related to or associated with) the sensing data of at least one terminal.

[0230] Optionally, the second sensing data may be obtained by fusing sensing data from at least one terminal based on the location of at least one terminal; or, the first device may fusing sensing data from at least one terminal based on the location of at least one terminal to obtain the second sensing data. For details, please refer to the explanation of "the first device may fusing sensing data from at least one terminal based on the location of at least one terminal" in method f1, which will not be repeated here. The type of the sensing data obtained by fusing sensing data from at least one terminal and the type of the second sensing data may be the same or different. For example, in Example 1 of method f1 above, the sensing data obtained by fusing sensing data from at least one terminal is fused sensing data of type I / Q signal; the second sensing data may be fused sensing data of type I / Q signal, or it may be the result of processing the fused sensing data of type I / Q signal (e.g., sensing data of type CFR information or point cloud information). For example, in Example 2 of Method f1 above, the sensing data obtained by fusing the sensing data of at least one terminal is the fused sensing data of type CFR information; the second sensing data may be the fused sensing data of type CFR information, or it may be the result of processing the fused sensing data of type CFR information (for example, sensing data of type point cloud information).

[0231] For example, the second sensing data can be obtained by fusing the sensing data of at least one terminal and the third sensing data sensed by the access network side based on the location of at least one terminal; or, the first device can fusing the sensing data of at least one terminal and the third sensing data sensed by the access network side based on the location of at least one terminal to obtain the second sensing data. For details, please refer to the description of "the first device can fusing the sensing data of at least one terminal and the third sensing data sensed by the access network side based on the location of at least one terminal" in method f1, which will not be repeated here. The type of the sensing data obtained by fusing the sensing data of at least one terminal and the third sensing data and the type of the second sensing data can be the same or different. For example, in Example 3 of method f1 above, the sensing data obtained by fusing the sensing data of at least one terminal and the third sensing data is the fused sensing data of type I / Q signal; the second sensing data can be the fused sensing data of type I / Q signal, or it can be the result of processing the fused sensing data of type I / Q signal (e.g., sensing data of type CFR information or point cloud information). For example, in Example 4 of Method f1 above, the perceived data obtained by fusing the perceived data from at least one terminal and the third perceived data is fused perceived data of type CFR information; the second perceived data can be fused perceived data of type CFR information, or it can be the result of processing the fused perceived data of type CFR information (e.g., perceived data of type point cloud information). As another example, in Example 5 of Method f1 above, the perceived data obtained by fusing the perceived data from at least one terminal and the third perceived data is fused perceived data of type point cloud information; the second perceived data can be fused perceived data of type point cloud information, or it can be the result of processing the fused perceived data of type point cloud information. In this example, the first device can obtain the second perceived data based on perceived data from multiple devices, thereby enabling perception processing based on more comprehensive perceived data and improving perception performance.

[0232] Optionally, in this implementation, the sensing data of at least one terminal and the third sensing data can be transmitted on different interfaces, or on different logical links on the same interface, or contained in different data packets. For example, in scenario 1 above, the third sensing data can be the sensing data of a third device. The third device can send the sensing data of at least one terminal to the first device, and it can also send the third sensing data to the first device. As previously described, the first and third devices may include two types of interfaces: one type for transmitting terminal sensing data and the other for transmitting access network-side sensing data. In this case, at least one terminal's sensing data and third sensing data can be transmitted on different interfaces. Alternatively, the first and third devices may include one interface, where a portion of the logical links can be used to transmit terminal sensing data and another portion can be used to transmit access network-side sensing data. In this case, at least one terminal's sensing data and third sensing data can be transmitted on different logical links of the same interface. Or, the first and third devices may include one interface where the data packets transmitted may contain or be associated with information indicating the data type included in the data packet. In this case, at least one terminal's sensing data and third sensing data may be contained in different data packets. For example, in scenario 2 above, the third sensing data may be the sensing data of the second device. The second device can send both at least one terminal's sensing data to the first device and the third sensing data to the first device. As described above, the first device and the second device may include two types of interfaces: one type for transmitting terminal sensing data and the other for transmitting access network-side sensing data. In this case, at least one terminal's sensing data and third sensing data can be transmitted on different interfaces. Alternatively, the first device and the second device may include one interface, where a portion of the logical link can be used to transmit terminal sensing data and another portion can be used to transmit access network-side sensing data. In this case, at least one terminal's sensing data and third sensing data can be transmitted on different logical links of the same interface. Or, the first device and the second device may include one interface, where the data packets transmitted may contain or be associated with information indicating the data type included in the data packet. In this case, at least one terminal's sensing data and third sensing data can be included in different data packets. In this way, the first device can accurately determine whether the received sensing data is at least one terminal's sensing data or access network-side sensing data.

[0233] In other implementations, the second sensing data can be the first sensing data. Optionally, if the location of at least one terminal is not obtained, the second sensing data can be the first sensing data. The specific content of the first sensing data can be found in the description of the first sensing data in step A2, and will not be repeated here.

[0234] In some implementations, the second sensing data may be the result of processing the first sensing data in step A3 above; or, the second sensing data may be obtained based on the first sensing data; or, the second sensing data may correspond to (or be related to) the first sensing data. The specific content of the first sensing data can be found in the description of the first sensing data in step A2, and will not be repeated here. Optionally, this implementation can be applied to situations where the location of at least one terminal has not been obtained.

[0235] In some examples, the second sensing data can be the second type of sensing data obtained by processing the first type of first sensing data; or, the first device can process the first type of first sensing data to obtain the second type of second sensing data. For details, please refer to the explanation of "the first device can process the first type of first sensing data to obtain the second type of sensing data" in step A3, which will not be repeated here. For example, in Example Six in step A3 above, the second sensing data can be sensing data of type CFR information or RAV spectrum information. As another example, in Example Seven in step A3 above, the second sensing data can be sensing data of type point cloud information.

[0236] In some examples, the second sensing data can be the sensing data obtained by fusing the first sensing data and the third sensing data sensed by the access network side; or, the first device can fusing the first sensing data and the third sensing data sensed by the access network side to obtain the second sensing data. For details, please refer to the explanation of "the first device can fusing the first sensing data and the third sensing data sensed by the access network side" in step A3, which will not be repeated here. The type of the sensing data obtained by fusing the first and third sensing data and the type of the second sensing data can be the same or different. For example, the sensing data obtained by fusing the first and third sensing data is the fused sensing data of type I / Q signal; the second sensing data can be the fused sensing data of type I / Q signal, or it can be the result of processing the fused sensing data of type I / Q signal (e.g., sensing data of type CFR information or point cloud information). For example, the sensing data obtained by fusing the first and third sensing data is fused sensing data of type CFR information; the second sensing data can be fused sensing data of type CFR information, or it can be the result of processing the fused sensing data of type CFR information (e.g., sensing data of type point cloud information). Again, for example, the sensing data obtained by fusing the first and third sensing data is fused sensing data of type point cloud information; the second sensing data can be fused sensing data of type point cloud information, or it can be the result of processing the fused sensing data of type point cloud information. In this example, the first device can obtain the second sensing data based on sensing data from multiple devices, thereby enabling sensing processing based on more comprehensive sensing data and improving sensing performance.

[0237] Among some possible ways, Figure 9 The method shown may also include S905:

[0238] S905: The first device sends second sensing data.

[0239] The second sensing data may correspond to (or be related to or associated with) the sensing data of at least one terminal. The specific content of the second sensing data can be found in the description of the second sensing data in S904, and will not be repeated here.

[0240] In some implementations, the first device can send second sensing data to the sensing management network element; correspondingly, the sensing management network element can receive the second sensing data from the first device, as shown in S905a. For example, in scenario 1 above, the first device can send the second sensing data to the sensing management network element through at least one of methods a1 to a8. As another example, in scenario 2 above, the first device can send sensing data to the sensing management network element through at least one of methods d1 to d8. Through this implementation, the sensing management network element can accurately obtain the second sensing data, thereby enabling more effective sensing management based on the second sensing data.

[0241] Optionally, in this implementation, when the first device sends the second sensing data to the sensing management network element through the second device and the core network equipment (e.g., AMF or UPF), the second sensing data and communication data can be transmitted on different interfaces between the second device and the core network equipment, or on different logical links on the same interface, or contained in different data packets. For example, in scenario 1 above, the second sensing data and communication data can be transmitted on different interfaces between the CU and the UPF, or on different logical links on the same interface between the CU and the UPF, or in different data packets on the same interface between the CU and the UPF. As another example, in scenario 2 above, the second sensing data and communication data can be transmitted on different interfaces between the NodeB and the UPF, or on different logical links on the same interface between the NodeB and the UPF, or in different data packets on the same interface between the NodeB and the UPF.

[0242] In other implementations, the first device can send second sensing data to the second device; correspondingly, the second device can receive the second sensing data from the first device, as shown in S905b. This second sensing data can be used to assist communication. For example, in scenario 1 above, where the first device is a first logic unit and the second device is a second logic unit, the first logic unit can send the second sensing data to the second logic unit, and the second logic unit can communicate based on the second sensing data. As another example, in scenario 2 above, where the first device is a first access network device and the second device is a second access network device, the first access network device can send the second sensing data to the second access network device, and the second access network device can communicate based on the second sensing data.

[0243] Optionally, the first device may also send information to the second device indicating the type of the second sensed data. In this way, the second device can accurately determine the type of the second sensed data. For example, the type of the second sensed data may include at least one of the following: point cloud information or sensed target information.

[0244] In other implementations, the first device can send the second sensing data to a third-party server; correspondingly, the third-party server can receive the second sensing data from the first device. Through this implementation, the third-party server can accurately obtain the second sensing data. This application does not limit the way the third-party server uses the second sensing data; for example, the third-party server can use the second sensing data for artificial intelligence (AI) and / or digital twins.

[0245] It should be understood that the above implementations can be independent or combined. When the above implementations are combined, the first device can send the second sensing data to multiple devices simultaneously, or it can send the second sensing data to multiple devices separately. For example, the timing of sending the second sensing data to different devices can be the same or different; for instance, the timing of sending the second sensing data to the sensing management network element can be the same or different from the timing of sending the second sensing data to the second device. And / or, the second sensing data sent to different devices can be carried in the same message or in different messages; for instance, the second sensing data sent to the sensing management network element and the second sensing data sent to the second device can be carried in the same message or in different messages.

[0246] Among some possible ways, Figure 9 The method shown may also include S906 to S907:

[0247] S906: The first device can receive first information, and the first information can indicate a first sensing need.

[0248] In some possible ways, the sensing management network element can send first information, and correspondingly, the first device can receive the first information from the sensing management network element, as shown in S906a. In this way, the first device can obtain a first sensing requirement from the sensing management network element.

[0249] In other possible approaches, the second device may send the first information; correspondingly, the first device may receive the first information from the second device, as shown in S906b. For example, in scenario 1 above, where the first device is a first logic unit and the second device is a second logic unit, the first logic unit may receive the first information from the second logic unit. As another example, in scenario 2 above, where the first device is a first access network device and the second device is a second access network device, the first access network device may receive the first information from the second access network device. In this way, the first device can obtain the first sensing requirement from the second device on the access network side, thereby improving the access network's management efficiency for sensing and reducing the latency of obtaining the first sensing requirement.

[0250] Optionally, the first sensing requirement includes at least one of the following information, or in other words, the first information indicates at least one of the following: sensing QoS or SLA; sensing data type; sensing time; or, sensing area. Specific details are as follows:

[0251] 1. Sensing QoS or SLA: This can be used to indicate the QoS or SLA required for sensing. For example, a sensing QoS or SLA may include at least one of the following: coverage, accuracy, resolution, detection / false alarm probability, service latency, or refresh rate. Coverage may be a limitation on the detectable distance and / or range; accuracy may be the difference between the sensing result and the actual data, such as one or more of distance difference, angle difference, or velocity difference; resolution may be the minimum difference between different sensing results in one or more dimensions of distance, angle, or velocity; detection / false alarm probability refers to the probability of detecting the presence or absence of a target; service latency refers to the time interval between the occurrence of an event or triggering of sensing and the output of the sensing result; refresh rate may be the rate at which the sensing data (e.g., location data) is refreshed.

[0252] 2. Type of Sensing Data: This can be used to indicate the type of data to be sensed. For example, the type of sensing data may include at least one of the following: I / Q signal, RAV spectrum information, CFR information, point cloud information, or sensing target information. Several possible ways of specifying the type of sensing data are provided here, allowing for flexible configuration of the sensing data type.

[0253] 3. Time of perception: This can be used to indicate the time during which perception is performed. For example, if the perception time included in the first perception requirement is a first time period, it means that perception should be performed within the first time period. The perception time can be an absolute time or a relative time relative to a reference time; there are no restrictions.

[0254] 4. Sensing Area: This can be used to indicate the area to be sensed. For example, if the sensing area indicated by the first information is a first region, it means that sensing will be performed within the first region, or that a target within the first region will be sensed. Optionally, the sensing area can be indicated in several ways. In some examples, the sensing area can be indicated by the coordinates of the region. In other examples, the sensing area can be indicated by an administrative region; for example, if the administrative region is City A, it means that sensing will be performed within City A. In still other examples, the sensing area can be indicated by the identifiers of one or more cells; for example, if the identifiers of one or more cells include the identifiers of cell #1 and cell #2, it means that sensing will be performed within the coverage (or service area) of cell #1 and cell #2. The sensing area can be replaced by at least one of the following: the scope of sensing or the location of sensing.

[0255] This method provides multiple possible ways to address the first sensing requirement, thus allowing for flexible configuration of the first sensing requirement.

[0256] The first information may also have other names, such as perceived business information or perceived demand information, as long as it has the same function, it is within the scope of protection of this application.

[0257] Optionally, S906 precedes S901.

[0258] In some examples, when S906 is S906a and S903 is S903a, the execution order of S906a and S903a is not limited; the first information in S906a and the first indication information in S903a can be carried in the same message or in a new message without restriction. In other examples, when S906 is S906b and S903 is S903b, the execution order of S906b and S903b is not limited; the first information in S906b and the first indication information in S903b can be carried in the same message or in a new message without restriction.

[0259] S907: The first device can send the second information; correspondingly, the second device can receive the second information.

[0260] For example, in scenario 1 above, where the first device is a first logic unit and the second device is a second logic unit, the first logic unit can send second information to the second logic unit. As another example, in scenario 2 above, where the first device is a first access network device and the second device is a second access network device, the first access network device can send second information to the second access network device.

[0261] The second information can be used to determine the first sensing resource. The first sensing resource can be used by at least one terminal to send and / or receive sensing signals; or, the first sensing resource can be the resource for the at least one terminal to send and / or receive sensing signals. The sending and / or receiving of the sensing signal corresponds to (or is related to or associated with) the second sensing requirement; or, the sending and / or receiving of the sensing signal can be used to fulfill the second sensing requirement. The second sensing requirement is determined based on the first sensing requirement.

[0262] In some examples, the second perceptual requirement can be the first perceptual requirement.

[0263] In other examples, the second sensing requirement may include a portion of the first sensing requirement; or, the second sensing requirement may be a sub-requirement of the first sensing requirement; or, the second sensing requirement may be obtained by (the first device) segmenting (or splitting) the first sensing requirement. For example, in the first sensing requirement, the sensing area includes area #1 in cell #1 and area #1 in cell #2. Cell #1 is a cell of CU #1, and cell #2 is a cell of CU #2. The first sensing requirement can be split into second sensing requirement #1 and second sensing requirement #2. In second sensing requirement #1, the sensing area includes area #1 in cell #1; in second sensing requirement #2, the sensing area includes area #2 in cell #2. As another example, in the first sensing requirement, the sensing area includes area #1 in cell #1 and area #1 in cell #2. Cell #1 is a cell of NodeB #1, and cell #2 is a cell of NodeB #2. The first sensing requirement can be split into second sensing requirement #1 and second sensing requirement #2. In the second sensing requirement #1, the sensing area includes area #1 within cell #1; in the second sensing requirement #2, the sensing area includes area #2 within cell #2. For example, in the first sensing requirement, the sensing time includes time period #1 and time period #2. During time period #1, the traffic volume of cell #1 is less than (or less than or equal to) a traffic volume threshold; during time period #2, the traffic volume of cell #2 is less than (or less than or equal to) a traffic volume threshold. The first sensing requirement can be further divided into a second sensing requirement #3 and a second sensing requirement #4. In the second sensing requirement #3, the sensing time includes time period #1, and the sensing area includes the coverage area of ​​cell #1; in the second sensing requirement #4, the sensing time includes time period #2, and the sensing area includes the coverage area of ​​cell #2. The traffic volume threshold can be pre-set, such as as specified in a protocol; or it can be determined by the first device; or it can be notified to the first device by other devices (e.g., core network equipment).

[0264] For details regarding the second sensing requirement, please refer to the description of the first sensing requirement in S901, except that the first sensing requirement is replaced with the second sensing requirement, and will not be repeated here.

[0265] Optionally, the S907 precedes the S901.

[0266] In this manner, after receiving first information indicating a first sensing requirement, the first device on the access network side can send second information for determining the first sensing resource. Thus, the first sensing resource can be determined on the access network side. Since the device on the access network side can easily obtain information about the resources on the access network side, it can determine sensing resources that are appropriate for the access network side's conditions, thereby meeting the sensing requirement, improving sensing performance, and increasing the efficiency of sensing management.

[0267] In addition, since the devices on the access network side can quickly obtain information about the resources on the access network side, the latency of determining the sensing resources can be reduced, thereby improving sensing performance and the efficiency of sensing management.

[0268] As mentioned above, the second information is used to determine the first sensing resource, and there are multiple ways to determine it, such as method g1 or method g2.

[0269] Method g1: The second information indicates the first sensing resource. This application does not limit the specific content of the second information indicating the first sensing resource.

[0270] For example, the first sensing resource may include at least one of the following: time domain resources, frequency domain resources, spatial domain resources, code domain resources, or power domain resources.

[0271] Optionally, in this approach, the first sensing resource may be determined by the first device. For example, the first sensing resource may be determined by the first device based on the second sensing requirement. This application does not limit the specific method by which the first device determines the first sensing resource based on the second sensing requirement.

[0272] The second information may also have other names, such as perceived resource configuration information, etc. As long as it has the same function, it is within the scope of protection of this application.

[0273] In this way, the second device can accurately determine the first sensing resource based on the second information. Furthermore, in this method, the sensing resource can be determined by the first device on the access network side, thereby improving the flexibility of the first device in sensing management and consequently increasing the efficiency of sensing management.

[0274] Optionally, in mode g1, the second information may further include first indication information, which indicates whether a terminal may be involved in sensing. The specific content of the first indication information can be found in the description of the first indication information in S903, and will not be repeated here. In this way, the second device can accurately determine whether a terminal is involved in sensing based on the first indication information.

[0275] In some implementations, in method g1, Figure 9 The method shown may also include step B1:

[0276] Step B1: The second device can send the third information; correspondingly, the first device can receive the third information.

[0277] The third information may indicate preferred and / or non-preferred sensing resources. Optionally, the recommended and / or non-preferred sensing resources may be those recommended and / or non-preferred by the second device. For example, the recommended and / or non-preferred sensing resources may include at least one of the following: time-domain resources, frequency-domain resources, spatial-domain resources, code-domain resources, or power-domain resources.

[0278] Optionally, the third information can be used to determine the first sensing resource; or, the first device can determine the first sensing resource based on the third information.

[0279] In some examples, the third information indicates recommended sensing resources; the first resource may belong to the recommended sensing resources, or the first device may select the first sensing resource from the recommended sensing resources. For example, if the recommended sensing resources indicated by the third information are time-domain resources on time units #1 and #2, then the first sensing resource may include time-domain resources on time units #1 and / or #2. As another example, if the recommended sensing resources indicated by the third information are frequency-domain resources on frequency units #1 and #2, then the first sensing resource may include frequency-domain resources on frequency units #1 and / or #2.

[0280] In other examples, the third resource indicates a deprecated sensing resource; the first sensing resource may be a resource other than the deprecated sensing resource, or the first sensing resource may be a resource supported by the second device other than the deprecated sensing resource, or the first device may select the first sensing resource from resources other than the deprecated sensing resource, or the first device may select the first sensing resource from resources supported by the second device other than the deprecated sensing resource. For example, if the deprecated sensing resource indicated by the third information is a time-domain resource on time unit #1 and time unit #2, then the first sensing resource may include some or all of the time-domain resources other than the time-domain resources on time unit #1 and time unit #2. As another example, if the deprecated sensing resource indicated by the third information is a frequency-domain resource on frequency unit #1 and frequency unit #2, then the first sensing resource may include some or all of the frequency-domain resources other than the frequency-domain resources on frequency unit #1 and frequency unit #2. For example, if the third information indicates that the unrecommended sensing resources are time-domain resources on time units #1 and #2, and the resources supported by the second device include time-domain resources on time units #1 to #4, then the first sensing resource may include time-domain resources on time units #3 and / or #4. For example, if the third information indicates that the unrecommended sensing resources may be frequency-domain resources on frequency units #1 and #2, and the resources supported by the second device include frequency-domain resources on frequency units #1 to #4, then the first sensing resource may include frequency-domain resources on frequency units #3 and / or #4.

[0281] In some other examples, the third information indicates recommended and unrecommended sensing resources. The first sensing resource may be among the recommended sensing resources but not among the unrecommended ones. For example, if the third information indicates that the recommended sensing resources are time-domain resources on time units #1 and #2, and the unrecommended sensing resources are time-domain resources on time units #3 and #4, then the first sensing resource may include time-domain resources on time units #1 and / or #2. As another example, if the third information indicates that the recommended sensing resources are frequency-domain resources on frequency units #1 and #2, and the unrecommended sensing resources are frequency-domain resources on frequency units #3 and #4, then the first sensing resource may include frequency-domain resources on frequency units #1 and / or #2.

[0282] The third information may also have other names, as long as it has the same function, it is within the scope of protection of this application.

[0283] Optionally, step B1 can be performed before S907. This application does not restrict the execution order of steps B1 and S906. In S906, when the first device receives the first information from the second device, the first information and the third information can be carried in the same message or in different messages.

[0284] Through this implementation, the first device can learn about recommended and / or unrecommended sensing resources, and thus select appropriate sensing resources accordingly, thereby better meeting sensing needs and improving the efficiency of sensing management.

[0285] In other implementations, in method g1, Figure 9 The method shown may also include step B2:

[0286] Step B2: The second device can send the first response information; correspondingly, the first device can receive the first response information.

[0287] The first response information may indicate whether to accept or reject the use of the first sensing resource to fulfill the second sensing requirement. Optionally, "the first sensing resource is used to fulfill the second sensing requirement" may be replaced by at least one of the following: configuration (or scheduling or indication) of the first sensing resource; configuration (or scheduling or indication) of the second information; or, the first sensing resource is used for receiving and / or transmitting sensing signals of at least one terminal. "Accept or reject" may be replaced by at least one of the following: whether to accept, whether to agree, or whether to reject. Through this method, the first device can accurately determine whether the second device accepts or rejects the use of the first sensing resource to fulfill the second sensing requirement based on the first response information.

[0288] Optionally, if the first response information indicates that the first sensing resource is rejected from fulfilling the second sensing requirement, the first response information may also indicate at least one of the following: the reason for rejection, or the sensing resources recommended and / or not recommended by the CU. This will be explained in detail below.

[0289] 1. Reason for Rejection: This indicates the reason for rejecting the use of the first sensing resource to fulfill the second sensing requirement. Optionally, this reason can be indicated by a cause value.

[0290] For example, the reason may include at least one of the following reasons a1 to a7:

[0291] Reason a1: Insufficient sensing time domain resources. For example, the available sensing time domain resources of the terminal served by the second device are less than the time domain resources in the first sensing resources.

[0292] Reason a2: Insufficient sensing frequency domain resources. For example, the available sensing frequency domain resources of the terminal served by the second device are less than the frequency domain resources in the first sensing resources.

[0293] Reason a3: Insufficient sensing airspace resources. For example, the available sensing airspace resources of the terminal served by the second device are less than the airspace resources in the first sensing resource.

[0294] Reason a4: Insufficient sensing code domain resources. For example, the available sensing code domain resources of the terminal served by the second device are less than the code domain resources in the first sensing resource.

[0295] Reason a5: Insufficient sensing power domain resources. For example, the available sensing power domain resources of the terminal served by the second device are less than the power domain resources in the first sensing resource.

[0296] Reason a6: No terminal for sensing. For example, among the terminals served by the second device, there is no terminal for sensing; or, among the terminals served by the second device, there is no terminal with sensing capabilities.

[0297] Reason a7: The terminal cannot meet the sensing QoS or SLA in the second sensing requirement. For example, the terminal served by the second device cannot meet the second sensing requirement.

[0298] 2. Recommended and / or not recommended sensory resources: For details, please refer to the explanation of recommended and / or not recommended sensory resources in step B1, which will not be repeated here.

[0299] Through this method, the first device can learn the reasons for rejecting the first sensing resource to fulfill the second sensing requirement, and / or the recommended and / or not recommended sensing resources, thereby adjusting the second information accordingly. For example, the sensing requirement for the second device indicated by the second information and / or the sensing resources configured for at least one terminal can be adjusted so that the adjusted second information (or the sensing resources determined according to the adjusted second information) is adapted to the resource situation on the terminal side, thereby satisfying the sensing requirement, improving sensing performance, and improving the efficiency of sensing management.

[0300] Optionally, if the first response information indicates that the first sensing resource is rejected for fulfilling the second sensing requirement, the first device may re-execute S907.

[0301] In some implementations, the first device can send second information to another second device. For example, the first device is a first logic unit. After sending the second information to CU#1, the first logic unit receives a first response information #1 from CU#1, which indicates that the first sensing resource is rejected from fulfilling the second sensing requirement. The first logic unit can then send the second information to CU#2, allowing the terminal served by CU#2 to fulfill the second sensing requirement. Another example is a first access network device. After sending the second information to NodeB#1, the first access network device receives a first response information #1 from NodeB#1, which indicates that the first sensing resource is rejected from fulfilling the second sensing requirement. The first access network device can then send the second information to NodeB#2, allowing the terminal served by NodeB#2 to fulfill the second sensing requirement.

[0302] In other implementations, the first device may send updated second information to the second device. This updated second information may be determined based on the reason for rejection and / or recommended and / or not recommended sensing resources; or, the updated second information may correspond to (or be related to or associated with) the reason for rejection and / or recommended and / or not recommended sensing resources. The following example illustrates this using the sensing resource indicated by the updated second information as first sensing resource #1 and the sensing resource indicated by the previous second information as first sensing resource #2. For example, if the reason for rejection includes insufficient sensing time-domain resources, the time-domain resources in first sensing resource #1 may be less than the time-domain resources in first sensing resource #2; or, if the reason for rejection includes insufficient sensing time-domain resources, the first device may reduce the time-domain resources in the first sensing resource. Another example is that first sensing resource #2 includes not recommended sensing resources, while first sensing resource #1 does not include not recommended sensing resources. Yet another example is that first sensing resource #2 is not a recommended sensing resource, while first sensing resource #1 is a recommended sensing resource.

[0303] The first response information may have other names, such as first feedback information, sensing resource configuration response message, sensing resource configuration completion / success message (indicating acceptance of the first sensing resource for fulfilling the second sensing requirement), or sensing resource configuration failure / rejection message (indicating rejection of the first sensing resource for fulfilling the second sensing requirement). Any message with the same function is within the scope of protection of this application.

[0304] Optionally, steps B1 and B2 can be independent or combined.

[0305] Optionally, step B1 and / or step B2 may be performed before S901; and / or step B2 may be performed after S907.

[0306] Optionally, in mode g1, the second information may also indicate at least one of the following: the transmission and reception mode for sensing; or, the sensing area. This will be explained in detail below.

[0307] 1. Sensing Transceiver Mode: Optionally, the sensing transceiver mode can be a transceiver mode in which at least one terminal is aware. For example, the transceiver mode can be one of the following: self-transmitting and self-receiving mode, A-transmitting and B-receiving mode, or hybrid transceiver mode. For details, please refer to the explanation of self-transmitting and self-receiving mode, A-transmitting and B-receiving mode, and hybrid transceiver mode in the terminology explanation section above; further details will not be repeated here.

[0308] 2. Sensing Area: Optionally, the sensing area can be an area sensed by at least one terminal. For details, please refer to the description of "sensing area" in the first sensing requirement in S906, which will not be repeated here. In some examples, the sensing area indicated by the second information may be the same as the sensing area in the first sensing requirement. In other examples, the sensing area indicated by the second information may be different from the sensing area in the first sensing requirement. For example, the sensing area indicated by the second information may belong to the sensing area in the first sensing requirement.

[0309] In this manner, the second device can accurately determine the transmission and reception mode and / or the sensing area based on the second information, thereby improving sensing performance. Furthermore, in this method, the transmission and reception mode and / or the sensing area can be indicated by the first device, thereby increasing the flexibility of the first device in sensing management.

[0310] Method g2: The second information indicates the second sensing requirement, which is used to determine the first sensing resource.

[0311] For details regarding the second sensing requirement, please refer to the explanation of the second sensing requirement in S907, which will not be repeated here.

[0312] Optionally, the second sensing requirement can be used to determine the first sensing resource; or, the second device can determine the first sensing resource based on the second sensing requirement; or, the second sensing requirement corresponds to (or is related to or associated with) the first sensing resource.

[0313] In some possible ways, the second information may also indicate the transmission and reception mode for sensing. For details, please refer to the description of the transmission and reception mode for sensing in mode g1, which will not be repeated here.

[0314] In this manner, the second device can determine a first sensing resource that matches the second sensing requirement indicated by the second information. Furthermore, in this method, the sensing resource can be determined by the second device on the access network side, thereby improving the flexibility of the second device in sensing management and consequently increasing the efficiency of sensing management.

[0315] In some implementations, in method g2, Figure 9 The method shown may also include step C1:

[0316] Step C1: The second device can send a second response message; correspondingly, the first device can receive the second response message.

[0317] In some implementations, the second response information may indicate the first sensing resource. For example, the first sensing resource may include at least one of the following: time-domain resources, frequency-domain resources, spatial-domain resources, code-domain resources, or power-domain resources. Thus, the first device can accurately determine the first sensing resource based on the second response information.

[0318] Optionally, in this implementation, the second response information may also indicate at least one of the following: the transmit / receive mode for sensing; or, the sensing location. This will be explained in detail below.

[0319] 1. Sensing Transmit / Receive Mode: Details are provided in section g1 regarding the sensing transmit / receive mode, and will not be repeated here. In some examples, the sensing transmit / receive mode indicated by the second response information may be the same as the sensing transmit / receive mode indicated by the second information. In other examples, the sensing transmit / receive mode indicated by the second response information may be different from the sensing transmit / receive mode indicated by the second information. For example, the sensing transmit / receive mode indicated by the second response information may belong to the sensing transmit / receive mode indicated by the second information. For instance, the sensing transmit / receive mode indicated by the second information includes: spontaneous transmission / reception mode and A transmits, B receives mode; the sensing transmit / receive mode indicated by the second response information may include: spontaneous transmission / reception mode and / or A transmits, B receives mode.

[0320] 2. Perceived Area: For details, please refer to the explanation of "perceived area" in the first perception requirement in S901, which will not be repeated here. In some examples, the perceived area indicated by the second response information may be the same as the perceived area in the second perception requirement. In other examples, the perceived area indicated by the second response information may be different from the perceived area in the second perception requirement. For example, the perceived area indicated by the second response information may belong to the perceived area in the second perception requirement.

[0321] Optionally, step C1 may be performed before S901; and / or step C1 may be performed after S907.

[0322] This method allows the second response information to accurately indicate the transmission and reception mode and / or the area being sensed, thereby improving the efficiency of sense management and enhancing sense performance.

[0323] Optionally, in this implementation, the second device can send both the second response information and the first indication information to the first device; that is, step C1 can be combined with S903b in S903. In this case, the time when the second device sends the second response information may be the same as or different from the time when the second device sends the first indication information; and / or, the first indication information and the second response information may be carried in the same message, or they may be carried in different messages.

[0324] In other implementations, the second response information may indicate refusal (or disagreement or non-acceptance) of fulfilling the second sensing requirement. Through this implementation, the first device can accurately determine, based on the second response information, that the second device refuses to fulfill the second sensing requirement.

[0325] Optionally, in this implementation, the second response information may also indicate at least one of the following: the reason for rejection; recommended and / or not recommended sensory resources; or, the sensory requirements that can be met. This will be explained in detail below.

[0326] 1. Reason for Refusal: This indicates the reason for refusing to fulfill the second perceptual requirement. Optionally, this reason can be indicated by a cause value.

[0327] For example, the reason may include at least one of the following reasons a1 to a7: Reason a1: Insufficient sensing time domain resources; Reason a2: Insufficient sensing frequency domain resources; Reason a3: Insufficient sensing spatial domain resources; Reason a4: Insufficient sensing code domain resources; Reason a5: Insufficient sensing power domain resources; Reason a6: No terminal available for sensing; Reason a7: The terminal does not meet the sensing QoS or SLA in the second sensing requirement. The specific details of reasons a1 to a7 can be found in the explanation of reasons a1 to a7 in step B2, and will not be repeated here.

[0328] 2. Recommended and / or not recommended sensory resources: For details, please refer to the explanation of recommended and / or not recommended sensory resources in step B1, which will not be repeated here.

[0329] 3. Achievable perception requirements: or perception requirements that can be satisfied. Optionally, the achievable perception requirements can be the perception requirements that the terminal serving the second device can achieve, for example, the perceived QoS or SLA that the terminal serving the second device can satisfy.

[0330] Through this method, the first device can learn the reasons for refusing to fulfill the second sensing requirement, the recommended and / or not recommended sensing resources, or one or more of the sensing requirements that can be fulfilled. Based on this, the sensing requirements for the second device can be adjusted so that the adjusted sensing requirements are adapted to the resource situation on the terminal side served by the second device, thereby satisfying the sensing requirements, improving sensing performance, and improving the efficiency of sensing management.

[0331] Optionally, if the second response information indicates that the second sensing requirement is refused, the first device may re-execute S907.

[0332] In some implementations, the first device can send a second message to another second device. For example, the first device is a first logic unit. After sending the second message to CU#1, the first logic unit receives a second response message #1 from CU#1, indicating that the second sensing requirement is refused. The first logic unit can then send the second message to CU#2, allowing the terminal served by CU#2 to fulfill the second sensing requirement. Another example is a first access network device. After sending the second message to NodeB#1, the first access network device receives a second response message #1 from NodeB#1, indicating that the second sensing requirement is refused. The first access network device can then send the second message to NodeB#2, allowing the terminal served by NodeB#2 to fulfill the second sensing requirement.

[0333] In other implementations, the first device may send updated second information to the second device. This updated second information may be determined based on at least one of the following, or may correspond to (or be related to) at least one of the following: the reason for rejection; recommended and / or unrecommended sensing resources; or, the achievable sensing requirements. The following explanation uses the sensing requirement indicated by the updated second information as second sensing requirement #1, and the sensing requirement indicated by the previous second information as second sensing requirement #2. For example, if the reason for rejection includes insufficient sensing temporal resources, the sensing temporal resources required for second sensing requirement #1 may be less than those required for second sensing requirement #2; or, if the reason for rejection includes insufficient sensing temporal resources, the first device may reduce the temporal resources required for the second sensing requirement. For another example, the sensing resources required for second sensing requirement #2 may include unrecommended sensing resources, while the sensing resources required for second sensing requirement #1 may not include unrecommended sensing resources. Yet another example, the sensing resources required for second sensing requirement #2 may not be recommended sensing resources, while the sensing resources required for second sensing requirement #1 may be recommended sensing resources. For example, the second sensing requirement #2 is not a sensing requirement that the terminal served by the second device can fulfill, while the second sensing requirement #1 is a sensing requirement that the terminal served by the second device can fulfill.

[0334] The second response information may have other names, such as second feedback information, sensing resource configuration response message, sensing resource configuration completion / success message (indicating the first sensing resource), or sensing resource configuration failure / rejection message (indicating the refusal to fulfill the second sensing requirement). Any message with the same function is within the scope of protection of this application.

[0335] Optionally, in this method, after determining the first sensing resource, the first device or the second device may notify at least one terminal of the sensing resource. The first terminal may be any one of the at least one terminals. The following description uses the first terminal as an example to illustrate how at least one terminal acquires the sensing resource.

[0336] In some implementations, the first device can send fourth information; correspondingly, the first terminal can receive the fourth information. The fourth information may indicate a second sensing resource, which may be part or all of the first sensing resource. In some examples, in scenario 1 above, the first device can send the fourth information to the first terminal sequentially through the second and third devices. For example, the first device is SU, the second device includes CU and DU, and the third device is RU. SU can send the fourth information to the first terminal sequentially through CU, DU, and RU. Another example: the first device is SU, the second device includes CU, and the third device is RU. SU can send the fourth information to the first terminal sequentially through CU and RU. Yet another example: the first device is SU, the second device includes DU, and the third device is RU. SU can send the fourth information to the first terminal sequentially through DU and RU. In other examples, in scenario 1 above, the first device can send the fourth information to the first terminal through the third device. For example, the first device is SU, and the third device is RU. SU can send the fourth information to the first terminal through RU. In other examples, in scenario 2 above, the first device can send fourth information to the first terminal via the second device. For instance, the first device is NodeC, and the second device is NodeB. NodeC can send the fourth information to the first terminal via NodeB.

[0337] In other implementations, the second device can send a fourth message; correspondingly, the first terminal can receive the fourth message. The fourth message may indicate a second sensing resource, which may be part or all of the first sensing resource. In some examples, in scenario 1 above, the second device can send the fourth message to at least one terminal via a third device. For example, the second device includes a CU, and the third device is an RU. The CU can send the fourth message to the first terminal sequentially via a DU and a RU. As another example, the second device includes a DU, and the third device is an RU. The DU can send the fourth message to the first terminal via the RU. In other examples, in scenario 2 above, the second device can send the fourth message to the first terminal. For example, the second device is a NodeB. The NodeB can send the fourth message to the first terminal.

[0338] In the manner described above, the first terminal can determine the second sensing resource for sensing, and thus can send and / or receive sensing signals according to the second sensing resource, thereby obtaining sensing data corresponding to the sensing signal. Similarly, each of the at least one terminal can send and / or receive sensing signals according to its corresponding sensing resource, thereby obtaining the sensing data of that at least one terminal, and thus executing S901.

[0339] Optionally, the fourth information may also indicate at least one of the following: the transmission and reception mode for sensing; or, the area of ​​sensing. These will be explained in detail below.

[0340] 1. Sensing Transmit / Receive Mode: For details, please refer to the description of sensing transmit / receive modes in method g1; it will not be repeated here. In some examples, the sensing transmit / receive mode indicated by the fourth information may be the same as the sensing transmit / receive mode indicated by the second information. In other examples, the sensing transmit / receive mode indicated by the fourth information may be different from the sensing transmit / receive mode indicated by the second information. For example, the sensing transmit / receive mode indicated by the fourth information may belong to the sensing transmit / receive mode indicated by the second information. For instance, the sensing transmit / receive modes indicated by the second information include: spontaneous transmission / reception mode and A transmits / B receives mode; the sensing transmit / receive modes indicated by the fourth information may include: spontaneous transmission / reception mode and / or A transmits / B receives mode.

[0341] For example, the first terminal can receive and / or send sensing signals according to the sensing transmission and reception mode indicated by the fourth information. For instance, if the transmission and reception mode is a self-transmission and self-reception mode, the first terminal can send and receive sensing signals according to the second sensing resources. As another example, if the transmission and reception mode is an A-transmit B-receive mode, the first terminal can send or receive sensing signals according to the second sensing resources. Yet another example, if the transmission and reception mode is a mixed transmission and reception mode, the first terminal can send and receive sensing signal #1 according to the second sensing resources, and also receive sensing signal #2 sent by other devices (e.g., RU or other terminals).

[0342] 2. Perceived Area: For details, please refer to the explanation of "perceived area" in the first perception requirement in S906, which will not be repeated here. In some examples, the perceived area indicated by the fourth information may be the same as the perceived area in the second perception requirement. In other examples, the perceived area indicated by the fourth information may be different from the perceived area in the second perception requirement. For example, the perceived area indicated by the fourth information may belong to the perceived area in the second perception requirement.

[0343] For example, the first terminal may receive and / or transmit sensing signals according to the sensing area indicated by the fourth information. For instance, the first terminal may receive and / or transmit sensing signals within the sensing area indicated by the fourth information. Also, for example, the first terminal may transmit sensing signals to the sensing area indicated by the fourth information; and / or, the first terminal may receive sensing signals from the sensing area indicated by the fourth information.

[0344] Among other possible approaches, Figure 9 The method shown may also include S908 to S909:

[0345] S908: Perception management network elements acquire primary perception requirements.

[0346] Optionally, the perception management element may obtain the first perception requirement from the AF; or, the perception management element may receive the first perception requirement from the AF.

[0347] The specific details of the first perception requirement can be found in the explanation of the first perception requirement in S906, and will not be repeated here.

[0348] S909: The sensing management network element can send second information; correspondingly, the second device can receive the second information.

[0349] The second information can be used to determine the first sensing resource, which is used by at least one terminal to send and / or receive sensing signals. The sending and / or receiving of these sensing signals corresponds to the second sensing requirement, which is determined based on the first sensing requirement. The specific content of the second information can be found in the description of the second information in S907, except that the first device is replaced by a sensing management network element, and will not be repeated here.

[0350] Optionally, in this method, after determining the first sensing resource, the second device may notify at least one terminal of the sensing resource. The notification method can be referred to the description of "the second device may notify at least one terminal of the sensing resource" in S907 above, and will not be repeated here. In this way, each of the at least one terminal can send and / or receive sensing signals according to its corresponding sensing resource, thereby obtaining the sensing data of the at least one terminal, and then S901 can be executed.

[0351] Optionally, S908 and S909 precede S901.

[0352] In this way, the second device on the access network side can negotiate the first sensing resource with the sensing management network element. Since the second device on the access network side can easily obtain information about the resources on the access network side, it can determine sensing resources that are suitable for the access network side, thereby meeting sensing requirements, improving sensing performance, and increasing the efficiency of sensing management.

[0353] exist Figure 9In the method shown, the first device can process the sensing data of at least one terminal based on whether the location of at least one terminal is acquired. In one case, the first device can acquire the location of at least one terminal, and thus process the sensing data of at least one terminal based on the location of at least one terminal. In this case, the location of at least one terminal can be a reference location of at least one terminal, rather than the actual location of at least one terminal. Since the location of a terminal is a matter of terminal privacy, this method can improve the performance of sensing processing while ensuring the privacy of the terminal.

[0354] Furthermore, in this method, the first device can be used for sensing, and the first device can be independent of the devices used for communication on the access network side (e.g., the second device and / or the third device), thereby improving the scalability of the first device and enabling it to meet higher sensing requirements by upgrading the first device.

[0355] This application provides another communication method. Figure 10 This is a flowchart illustrating the communication method provided in the embodiments of this application. Figure 10 For details regarding the execution entity of the method shown, please refer to the section on... Figure 9 The description of the execution entity of the method shown will not be repeated here. Figure 10 In the method shown, the first device can process the sensing data of at least one terminal based on the location of at least one terminal. For example... Figure 10 As shown, the method includes:

[0356] S1001: At least one terminal sends sensing data of at least one terminal; correspondingly, the first device receives sensing data of at least one terminal.

[0357] For details of S1001, please refer to S901, and will not be repeated here.

[0358] S1002: The first device can process the sensing data of at least one terminal based on the location of at least one terminal.

[0359] For details of S1002, please refer to method f1 in S902, which will not be repeated here.

[0360] Among some possible ways, Figure 10 The method shown may also include:

[0361] S1003: The first device receives the first instruction information, which indicates whether a terminal is involved in sensing.

[0362] For details of S1003, please refer to S903; further details will not be provided here.

[0363] In other possible approaches, the first device can independently determine whether a terminal is involved in sensing; details can be found in [reference needed]. Figure 9 The explanation of "the first device can determine on its own whether there is a terminal involved in sensing" in the method shown will not be repeated here.

[0364] In some implementations, when terminals are involved in sensing, the first device can send a first request; correspondingly, the sensing management network element can receive the first request. The first request can be used to request the location of at least one terminal. For details, please refer to [link / reference]. Figure 9 The explanation of "when a terminal is involved in sensing, the first device may send a first request" in the method shown will not be repeated here.

[0365] Optionally, after receiving the first request, the sensing management network element may send information indicating the location of at least one terminal; correspondingly, the first device may receive the information indicating the location of at least one terminal. For details, please refer to [link / reference]. Figure 9 The description of "the sensing management network element can send information indicating the location of at least one terminal" in the method shown will not be repeated. After receiving the information indicating the location of at least one terminal, the first device can execute S1002.

[0366] In other implementations, when a terminal is involved in sensing, the first device can obtain the location of at least one locally stored terminal, thereby enabling the execution of S1002.

[0367] It should be understood that the above implementations can be independent or combined with each other. For example, when terminals are involved in sensing, the first device can obtain the location of a first portion of the terminals among at least one locally stored terminals, and request the location of the terminals other than the first portion of terminals among the at least one terminal through a first request.

[0368] Among some possible ways, Figure 10 The method shown may also include:

[0369] S1004: The first device acquires the second sensing data.

[0370] The second sensing data may be the result of processing the sensing data of at least one terminal in S1002. The specific content of the second sensing data can be found in the explanation in S904 that "the second sensing data may be the result of processing the sensing data of at least one terminal in mode f1," and will not be repeated here.

[0371] Among some possible ways, Figure 10 The method shown may also include S1005:

[0372] S1005: The first device sends the second sensing data.

[0373] For details of S1005, please refer to S905; further details will not be provided here.

[0374] Among some possible ways, Figure 10 The method shown may also include S1006 to S1007:

[0375] S1006: The first device can receive first information, and the first information can indicate a first sensing need.

[0376] S1007: The first device can send second information; correspondingly, the second device can receive the second information. The second information can be used to determine the first sensing resource.

[0377] For details on S1006 to S1007, please refer to S906 to S907, which will not be repeated here.

[0378] Among other possible approaches, Figure 10 The method shown may also include S1008 to S1009:

[0379] S1008: The perception management network element obtains the first perception requirement.

[0380] S1009: The sensing management network element can send second information; correspondingly, the second device can receive the second information. The second information can be used to determine the first sensing resource.

[0381] For details of S1008 to S1009, please refer to S908 to S909, which will not be repeated here.

[0382] pass Figure 10 The method shown allows the first device on the access network side to process the sensing data of at least one terminal based on the location of at least one terminal, thereby enabling the access network side to process the terminal's sensing data. Compared to processing the terminal's sensing data through core network equipment or a third-party server, this method can reduce the processing latency of the terminal's sensing data.

[0383] Furthermore, in this method, the location of at least one terminal acquired by the first device can be a reference location for at least one terminal, rather than the actual location of at least one terminal. The actual location of the terminal is a matter of terminal privacy. Therefore, this method reduces the processing latency of the terminal's sensing data and improves the performance of sensing processing while ensuring the privacy of at least one terminal.

[0384] Furthermore, in this method, the first device can be used for sensing, and the first device can be independent of the device used for communication on the access network side, thereby improving the scalability of the first device, and thus meeting higher sensing requirements by upgrading the first device.

[0385] This application provides yet another communication method. Figure 11 This is a flowchart illustrating the communication method provided in the embodiments of this application. Figure 11 For details regarding the execution entity of the method shown, please refer to the section on... Figure 9 The description of the execution entity of the method shown will not be repeated here. Figure 11 In the method shown, the first device can receive first sensing data, which is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal. For example... Figure 11 As shown, the method includes:

[0386] S1101: The sensing management network element sends the first sensing data; correspondingly, the first device receives the first sensing data.

[0387] The first sensing data is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal.

[0388] For details of S1101, please refer to step A2. Repeated points will not be repeated here.

[0389] Optionally, before sending the first sensing data, the sensing management network element may acquire sensing data from at least one terminal. The acquisition method may be multiple, such as at least one of method h1 to method h3.

[0390] Method h1: At least one terminal can sequentially send sensing data of at least one terminal to the sensing management network element through the third device and the second device. Optionally, this method h1 can be applied to scenario 1 above.

[0391] The first terminal can be any of at least one terminal. The following explanation uses the first terminal as an example to illustrate method h1.

[0392] For example, the second device includes a CU and a DU, and the third device is a RU. The first terminal can sequentially send its sensing data to the sensing management network element through the RU, DU, and CU.

[0393] For example, the second device includes a CU, and the third device is an RU. The first terminal can send its sensing data to the sensing management network element through the RU and the CU in sequence.

[0394] For example, the second device includes a DU, and the third device is a RU. The first terminal can sequentially send its sensing data to the sensing management network element through the RU and the DU.

[0395] Optionally, in this approach, the sensing data received by the second device can be sensing data from at least one terminal or third sensing data sensed by the access network side (e.g., a third device). If the sensing data received by the second device is sensing data from at least one terminal, the second device can send the sensing data from at least one terminal to the sensing management network element; and / or, if the sensing data received by the second device is third sensing data sensed by the access network side, the second device can send the third sensing data to the first device. In this way, the second device can determine a suitable transmission path for the received sensing data, thereby reducing the transmission latency of the sensing data.

[0396] Optionally, in this method, the sensing data and third sensing data of at least one terminal can be transmitted on different interfaces, or on different logical links on the same interface, or contained in different data packets. For details, please refer to the description in S904 regarding "the sensing data and third sensing data of at least one terminal can be transmitted on different interfaces, or on different logical links on the same interface, or contained in different data packets." In this way, the second device can accurately determine whether the received sensing data is sensing data from at least one terminal or third sensing data sensed by the access network side.

[0397] Method h2: At least one terminal can send sensing data of at least one terminal to the sensing management network element through the second device. Optionally, this method h2 can be applied to scenario 2 above.

[0398] The first terminal can be any of at least one terminal. The following explanation uses the first terminal as an example to illustrate mode h2. For example, the second device includes a NodeB. The first terminal can send its sensing data to the sensing management network element via the NodeB.

[0399] Optionally, in this approach, the sensing data acquired by the second device can be sensing data from at least one terminal or third sensing data sensed by the access network side (e.g., the second device). If the sensing data acquired by the second device is sensing data from at least one terminal, the second device can send the sensing data from at least one terminal to the sensing management network element; and / or, if the sensing data acquired by the second device is third sensing data sensed by the access network side, the second device can send the third sensing data to the first device. In this way, the second device can determine a suitable transmission path for the received sensing data, thereby reducing the transmission latency of the sensing data.

[0400] Method h3: At least one terminal can send sensing data of at least one terminal to the sensing management network element through the first device. Optionally, this method h3 can be applied to scenarios 1 and 2 above.

[0401] Method h3 may include steps D1 to D2:

[0402] Step D1: At least one terminal sends sensing data from at least one terminal; correspondingly, the first device receives sensing data from at least one terminal.

[0403] For details on step D1, please refer to S901, which will not be repeated here.

[0404] Step D2: The first device can send sensing data from at least one terminal; correspondingly, the sensing management network element can receive the sensing data from the at least one terminal.

[0405] The specific details of step D2 can be found in step A1 of S902, which states that "the first device can send sensing data from at least one terminal; correspondingly, the sensing management network element can receive the sensing data from the at least one terminal," and will not be repeated here.

[0406] S1102: The first device communicates based on the second sensing data.

[0407] In some implementations, the second sensing data is the same as the first sensing data.

[0408] In other implementations, the second sensing data corresponds to (or is related to or associated with) the first sensing data; or, the second sensing data is obtained based on the first sensing data; or, the second sensing data is the result of processing the first sensing data.

[0409] In some examples, the specific content of the second sensing data can be found in the description of the second sensing data in S904, which states that "the second sensing data can be the result of processing the first sensing data in step A3 above," and will not be repeated here.

[0410] In other examples, the second sensing data can be obtained by processing the first sensing data based on the location of at least one terminal; or, the first device can process the first sensing data based on the location of at least one terminal to obtain the second sensing data. There are several ways for the first device to obtain the location of at least one terminal. For example, when terminals are involved in sensing, the first device can send a first request; correspondingly, the sensing management network element can receive the first request, which can be used to request the location of at least one terminal. For details, please refer to [reference needed]. Figure 9The description of "when terminals participate in sensing, the first device can send a first request; correspondingly, the sensing management network element can receive the first request" in the illustrated method will not be repeated. After receiving the first request, the sensing management network element can send information indicating the location of at least one terminal; correspondingly, the first device can receive information indicating the location of at least one terminal. For example, when terminals participate in sensing, the first device can obtain the location of at least one terminal stored locally. It should be understood that the above examples can be independent or combined. For example, when terminals participate in sensing, the first device can obtain the location of a first portion of the at least one terminal stored locally, and request the location of the terminals other than the first portion of the at least one terminal through the first request.

[0411] Optionally, S1102 may include step E1:

[0412] Step E1: The first device can send the second sensing data.

[0413] For details on step E1, please refer to S905, which will not be repeated here.

[0414] Among some possible ways, Figure 11 The method shown may also include:

[0415] S1103: The first device receives first instruction information, which indicates whether a terminal is involved in sensing.

[0416] For details of S1103, please refer to S903; further details will not be provided here.

[0417] In other possible approaches, the first device can independently determine whether a terminal is involved in sensing; details can be found in [reference needed]. Figure 9 The explanation of "the first device can determine on its own whether there is a terminal involved in sensing" in the method shown will not be repeated here.

[0418] In some implementations, when a terminal is involved in sensing, the first device can send a second request; correspondingly, the sensing management network element can receive the second request. The second request can be used to request the first sensing data. For details, please refer to [link / reference needed]. Figure 9 The explanation of "the first device can send a second request; correspondingly, the sensing management network element can receive the second request" in the method shown will not be repeated.

[0419] Optionally, after receiving the second request, the sensing management network element may execute S1101. In this way, the sensing management network element can send the first sensing data to the first device in a targeted manner based on the request of the first device, thereby avoiding unnecessary transmission of the first sensing data and thus saving transmission resources.

[0420] Among some possible ways, Figure 11 The method shown may also include S1104 to S1105:

[0421] S1104: The first device can receive first information, and the first information can indicate a first sensing need.

[0422] S1105: The first device can send second information; correspondingly, the second device can receive the second information. The second information can be used to determine the first sensing resource.

[0423] For details on S1104 to S1105, please refer to S906 to S907, which will not be repeated here.

[0424] Among other possible approaches, Figure 11 The method shown may also include S1106 to S1107:

[0425] S1106: Perception management network elements acquire the first perception requirement.

[0426] S1107: The sensing management network element can send second information; correspondingly, the second device can receive the second information. The second information can be used to determine the first sensing resource.

[0427] For details on S1106 to S1107, please refer to S908 to S909, which will not be repeated here.

[0428] pass Figure 11 The method shown allows a first device on the access network side to acquire first sensing data, which is obtained by processing sensing data of at least one terminal based on its location. In this method, the access network side may not acquire the location of at least one terminal, as the actual location of the terminal is considered private information. Therefore, this method can process the sensing data of at least one terminal while ensuring its privacy.

[0429] Furthermore, in this method, the first device can be used for sensing, and the first device can be independent of the device used for communication on the access network side, thereby improving the scalability of the first device, and thus meeting higher sensing requirements by upgrading the first device.

[0430] The following is combined Figures 12 to 17 ,illustrate Figure 9 , Figure 10 and Figure 11 Examples of at least one of the methods shown in [the document]. Figure 12 or Figure 13 The method shown is Figure 9 , Figure 10 and Figure 11 Possible examples of the methods shown. In Figure 12 or Figure 13In the method shown, the first device can process the sensing data of at least one terminal based on whether the location of at least one terminal has been obtained. Figure 14 or Figure 15 The method shown is Figure 9 and Figure 10 Possible examples of the methods shown. In Figure 14 or Figure 15 In the method shown, the first device can process the sensing data of at least one terminal based on the location of at least one terminal. Figure 16 or Figure 17 The method shown is Figure 9 and Figure 11 Possible examples of the methods shown. In Figure 16 or Figure 17 In the method shown, the first device can receive first sensing data, which is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal.

[0431] exist Figure 12 , Figure 14 and Figure 16 In the method shown, the first device is SU, the second device is CU, and the third device is RU, as an example for explanation. Optionally, in Figure 12 , Figure 14 and Figure 16 In the method shown, the CU can communicate directly with the SU, or the CU can communicate with the SU through the DU.

[0432] In some implementations, Figure 12 , Figure 14 and Figure 16 In the method shown, CU can be replaced by DU. Optionally, DU can communicate directly with SU, or DU can communicate with SU through CU.

[0433] exist Figure 13 , Figure 15 and Figure 17 The method shown is illustrated using NodeC as the first device and NodeB as the second device as an example.

[0434] like Figure 12 As shown, the method includes:

[0435] S1201: SU and CU interact to perceive demand.

[0436] For example, the CU sends a first message to the SU, which indicates a first sensing requirement. For details, please refer to S906b, which will not be repeated here.

[0437] Optionally, in S1201, the CU also sends a first indication message to the SU. The first indication message indicates whether a terminal is involved in sensing. For details, please refer to S903b, which will not be repeated here.

[0438] S1202: SU sends a third request to the perception management network element.

[0439] The third request is used to request information about at least one terminal. The information about the at least one terminal may include an identifier for the at least one terminal. Optionally, the information about the at least one terminal may further include information indicating the location of the at least one terminal; or, the information about the at least one terminal may also indicate the location of the at least one terminal.

[0440] It should be understood that the third request may have other names, such as terminal information request, etc., as long as it has the same function, it is within the protection scope of this application.

[0441] S1203: The perception management network element sends the third response information to the SU.

[0442] The third response information may include information from at least one terminal.

[0443] It should be understood that the third response information may have other names, such as third feedback information, terminal request response, or terminal information request response, etc. As long as it has the same function, it is within the protection scope of this application.

[0444] In cases where the third response information includes information indicating the location of at least one terminal. Figure 12 The method shown may include embodiment 1; and / or, in the case where the third response information does not include information indicating the location of at least one terminal, Figure 12 The method shown may include Implementation 2.

[0445] Implementation method 1:

[0446] Implementation method 1 may include S1204 to S1208:

[0447] S1204: The CU and SU negotiate the first sensing resource for perception.

[0448] In some implementations, S1204 may include steps F1 to F3:

[0449] Step F1: SU sends a second message to CU, the second message indicating a second sensing requirement, the second sensing requirement being used to determine the first sensing resource.

[0450] The details of step F1 can be found in method g2 in S907 above, and will not be repeated here.

[0451] Optionally, before sending the second information, the SU may select the terminal for sensing. For example, the SU may select a terminal that supports sensing, based on, for example, the terminal's capabilities. For instance, the terminal may send information indicating its capabilities to the SU via one or more of the RU, DU, and CU; if the information indicating the terminal's capabilities indicates that the terminal supports sensing, the SU may select that terminal.

[0452] Step F2: SU sends a first indication message to CU, which indicates whether a terminal is involved in sensing.

[0453] This application does not restrict the execution order of steps F1 and F2. The first instruction information and the second information may be carried in the same message or in different messages.

[0454] Step F3: The CU sends a second response message to the SU. The second response message may indicate the first sensing resource; or, the second response message may indicate rejection (or disagreement or non-acceptance) of fulfilling the second sensing request.

[0455] The details of step F3 can be found in step C1 of S907 above, and will not be repeated here.

[0456] Optionally, if the second response information indicates that the second sensing request is rejected, SU may re-execute S1204. For details, please refer to the description of the first device being able to re-execute S907 in step C1, which will not be repeated here.

[0457] In other implementations, S1204 may include steps G1 to G3:

[0458] Step G1: SU sends second information to CU, the second information indicating a second sensing requirement, the second sensing requirement being used to determine the first sensing resource.

[0459] The details of step G1 can be found in method g2 above, and will not be repeated here.

[0460] Optionally, before sending the second information, the SU may select the terminal to be used for sensing. The selection method can be referred to the explanation of "the SU may select the terminal to be used for sensing" in step F1 of S1204 above, and will not be repeated here.

[0461] Step G2: The CU sends a second response message to the SU. The second response message may indicate the first sensing resource; or, the second response message may indicate rejection (or disagreement or non-acceptance) of fulfilling the second sensing request.

[0462] Step G3: The CU sends a first indication message to the SU, which indicates whether a terminal is involved in sensing.

[0463] For details on step G3, please refer to S903b, which will not be repeated here.

[0464] This application does not impose any restriction on the execution order of steps G2 and G3. The first instruction information and the second response information may be carried in the same message or in different messages.

[0465] Optionally, if the second response information indicates that the second sensing request is rejected, SU may re-execute S1204. For details, please refer to the description of the first device being able to re-execute S907 in step C1, which will not be repeated here.

[0466] In some implementations, S1204 may include step H1:

[0467] Step H1: The SU can send a second message to the CU, which can instruct the first sensing resource.

[0468] The details of step H1 can be found in method g1 in S907 above, and will not be repeated here.

[0469] Optionally, in this implementation, S1204 may also include step H2:

[0470] Step H2: The CU sends third information to the SU, which may indicate recommended and / or unrecommended sensing resources.

[0471] The details of step H2 can be found in step B1 of S907 above, and will not be repeated here.

[0472] Optionally, in this implementation, S1204 may also include step H3:

[0473] Step H3: The CU sends a first response message to the SU, which can indicate whether to accept or reject the use of the first sensing resource to fulfill the second sensing requirement.

[0474] The details of step H3 can be found in step B2 of S907 above, and will not be repeated here.

[0475] Optionally, if the first response information indicates that the first sensing resource is rejected from being used to fulfill the second sensing requirement, SU may re-execute S1204. For details, please refer to the explanation in step B2 regarding the re-execution of S907 by the first device; it will not be repeated here.

[0476] The first terminal can be any of the at least one terminal. The following explanation uses the first terminal as an example to illustrate how at least one terminal acquires sensing resources.

[0477] S1205: The CU sends fourth information to the first terminal. The fourth information may indicate a second sensing resource, which may be part or all of the first sensing resource.

[0478] For details regarding S1205, please refer to [link / reference]. Figure 9 The description of "the second device can send the fourth information; correspondingly, the first terminal can receive the fourth information" in the method shown will not be repeated.

[0479] Optionally, the fourth information may also indicate at least one of the following: the transmission and reception mode for sensing; or, the area being sensed. See details for further information. Figure 9 The explanation of the fourth piece of information in the method shown will not be repeated here.

[0480] S1206: The first terminal sends the first terminal's sensing data to the RU.

[0481] For example, the type of sensing data of the first terminal may include at least one of the following: I / Q signal, CFR information, RAV spectrum information, or point cloud information.

[0482] As previously stated, the first terminal is any one of at least one terminals. Each of these at least one terminals can perform operations similar to S1205 and S1206, so that the RU can receive sensing data from at least one terminal.

[0483] S1207: The RU sends sensing data from at least one terminal to the CU.

[0484] The transmission times of the sensing data from different terminals in the at least one terminal may be the same or different. For example, the RU may send the sensing data of one terminal to the CU after receiving the sensing data of that terminal. Or, for example, the RU may send the sensing data of the at least one terminal to the CU after receiving the sensing data of all terminals in the at least one terminal.

[0485] Optionally, the RU can send both terminal sensing data to the CU and RU sensing data to the CU. The RU can indicate whether the sensing data sent by the RU is terminal sensing data or RU sensing data. For example, the sensing data of at least one terminal and the sensing data of the RU can be transmitted on different interfaces between the RU and the CU; or, the sensing data of at least one terminal and the sensing data of the RU can be transmitted on different logical links of the same interface between the RU and the CU; or, the sensing data of at least one terminal and the sensing data of the RU can be transmitted in different data packets of the same interface between the RU and the CU.

[0486] S1208: The CU sends sensing data from at least one terminal to the SU.

[0487] Optionally, the CU can send both terminal sensing data and RU sensing data to the SU. The CU can indicate whether the sensing data sent by the CU is terminal sensing data or RU sensing data. The indication can be explicit or implicit. For example, the sensing data of at least one terminal and the sensing data of the RU can be transmitted on different interfaces between the SU and the CU; or, the sensing data of at least one terminal and the sensing data of the RU can be transmitted on different logical links of the same interface between the SU and the CU; or, the sensing data of at least one terminal and the sensing data of the RU can be transmitted in different data packets of the same interface between the SU and the CU.

[0488] Optionally, implementation 1 further includes S1209:

[0489] S1209: SU processes the sensing data of at least one terminal based on the location of at least one terminal to obtain second sensing data.

[0490] For details of S1209, please refer to method f1 in S902, which will not be repeated here.

[0491] Optionally, implementation 1 further includes S1210:

[0492] S1210: SU sends second sensing data to CU.

[0493] For details on S1210, please refer to S905b; further details will not be provided here.

[0494] Implementation Method 2:

[0495] Implementation method 2 may include S1211 to S1218:

[0496] S1211 to S1215: Refer to S1204 to S1208, and will not be repeated here.

[0497] S1216: SU sends sensing data from at least one terminal to the sensing management network element.

[0498] For details of S1216, please refer to step A1 in S902, which will not be repeated here.

[0499] S1217: The perception management network element processes the perception data of at least one terminal to obtain the first perception data.

[0500] Optionally, the sensing management network element can process the sensing data of at least one terminal based on the location of at least one terminal to obtain first sensing data. For details, please refer to the explanation of "the sensing management network element can process the sensing data of at least one terminal based on the location of at least one terminal to obtain first sensing data" in step A2 of S902, which will not be repeated here.

[0501] S1218: The perception management network element sends the first perception data to the SU.

[0502] For details of S1218, please refer to step A2 in S902, which will not be repeated here.

[0503] Optionally, implementation 2 further includes S1219:

[0504] S1219: SU processes the first sensing data to obtain the second sensing data.

[0505] For details of S1209, please refer to step A3 in S902, which will not be repeated here.

[0506] Optionally, implementation 2 further includes S1220:

[0507] S1220: SU sends second sensing data to CU.

[0508] For details on S1210, please refer to S905b; further details will not be provided here.

[0509] pass Figure 12 The method shown allows the SU to request terminal information from the sensing management network element for sensing services triggered by the access network side, and to process the terminal's sensing data based on whether the terminal information includes information indicating the terminal's location.

[0510] In one scenario, the SU can acquire the location of at least one terminal, thereby enabling the processing of the sensing data of that terminal based on its location. In this case, the location of the at least one terminal can be a reference location, rather than its actual location. Since the terminal's location is a matter of terminal privacy, this method can improve the performance of sensing processing while preserving the terminal's privacy.

[0511] In another scenario, the SU (Supply Controller) fails to acquire the location of at least one terminal. The SU can acquire first sensing data, which is obtained by processing the sensing data of at least one terminal based on its location. In this method, the access network side may not acquire the location of at least one terminal. The actual location of a terminal is a matter of terminal privacy. Therefore, this method can process the sensing data of at least one terminal while ensuring the privacy of at least one terminal.

[0512] Furthermore, in this method, the SU can perform fusion processing based on the terminal's sensing data or its processing results, thereby improving sensing QoS or SLA, and thus improving the performance of sensing processing.

[0513] Furthermore, in this method, the SU can be used for sensing, and the SU can be independent of the access network side devices used for communication (e.g., one or more of CU, DU, and RU), thereby improving the scalability of the SU and enabling higher sensing requirements to be met by upgrading the SU.

[0514] like Figure 13 As shown, the method includes:

[0515] S1301: NodeC and NodeB interact to sense requirements.

[0516] For details of S1301, please refer to S1201, except that SU is replaced with NodeC and CU is replaced with NodeB, which will not be repeated here.

[0517] S1302: NodeC sends a third request to the perception management network element. The third request is used to request information from at least one terminal.

[0518] S1303: The perception management network element sends a third response message to the NodeC.

[0519] For details of S1302 to S1303, please refer to S1202 to S1203, except that SU is replaced with NodeC, and will not be repeated here.

[0520] In cases where the third response information includes information indicating the location of at least one terminal. Figure 13 The method shown may include embodiment 3; and / or, in the case that the third response information does not include information indicating the location of at least one terminal, Figure 13 The method shown may include embodiment 4.

[0521] Implementation Method 3:

[0522] Implementation method 3 may include S1304 to S1307:

[0523] S1304: NodeB and NodeC negotiate the first sensing resource for sensing.

[0524] For details of S1304, please refer to S1204, except that SU is replaced with NodeC and CU is replaced with NodeB, which will not be repeated here.

[0525] The first terminal can be any of the at least one terminal. The following explanation uses the first terminal as an example to illustrate how at least one terminal acquires sensing resources.

[0526] S1305: NodeB sends fourth information to the first terminal. The fourth information may indicate a second sensing resource, which may be part or all of the first sensing resource.

[0527] S1306: The first terminal sends its sensing data to the NodeB.

[0528] For details on S1305 to S1306, please refer to S1205 to S1206, except that CU is replaced with NodeB and RU is replaced with NodeB, which will not be repeated here.

[0529] As previously stated, the first terminal is any one of at least one terminals. Each of these at least one terminals can perform operations similar to S1305 and S1306, so that the NodeB can receive sensing data from at least one terminal.

[0530] S1307: NodeB sends sensing data from at least one terminal to NodeC.

[0531] For details of S1307, please refer to S1208, except that SU is replaced with NodeC and CU is replaced with NodeB, which will not be repeated here.

[0532] Optionally, implementation 3 also includes S1308:

[0533] S1308: NodeC processes the sensing data of at least one terminal based on the location of at least one terminal to obtain second sensing data.

[0534] For details of S1308, please refer to method f1 in S902, which will not be repeated here.

[0535] Optionally, implementation 3 also includes S1309:

[0536] S1309: NodeC sends second sensing data to NodeB.

[0537] For details on S1309, please refer to S905b; further details will not be provided here.

[0538] Implementation Method 4:

[0539] Implementation method 4 may include S1310 to S1316:

[0540] S1310 to S1313: Refer to S1304 to S1307, and will not be repeated here.

[0541] S1314: NodeC sends sensing data from at least one terminal to the sensing management network element.

[0542] For details of S1314, please refer to step A1 in S902, which will not be repeated here.

[0543] S1315: The perception management network element processes the perception data of at least one terminal to obtain the first perception data.

[0544] For details of S1315, please refer to S1217, which will not be repeated here.

[0545] S1316: The perception management network element sends the first perception data to the NodeC.

[0546] For details of S1316, please refer to step A2 in S902, which will not be repeated here.

[0547] Optionally, implementation 4 also includes S1317:

[0548] S1317: NodeC processes the first sensing data to obtain the second sensing data.

[0549] For details of S1317, please refer to step A3 in S902, which will not be repeated here.

[0550] Optionally, implementation 4 also includes S1318:

[0551] S1318: NodeC sends second sensing data to NodeB.

[0552] For details of S1318, please refer to S905b, which will not be repeated here.

[0553] Figure 13 The technical effects of the method shown can be referenced. Figure 12 The technical effect of the method shown is simply that SU is replaced with NodeC, and CU, DU and RU are replaced with NodeB, which will not be elaborated further.

[0554] like Figure 14 As shown, the method includes:

[0555] S1401: The SU and the perception management network element interact to meet perception requirements.

[0556] For example, the perception management network element sends the first information to the SU, which indicates the first perception requirement. For details, please refer to S906a, which will not be repeated here.

[0557] Optionally, in S1401, the perception management network element also sends a first indication information to the SU. The first indication information indicates whether a terminal is participating in perception. For details, please refer to S903a, which will not be repeated here.

[0558] S1402 to S1406: Refer to S1204 to S1208, and will not be repeated here.

[0559] S1407: SU sends the second sensing data to the sensing management network element.

[0560] In some implementations, the second sensing data is sensing data from at least one terminal. In this implementation, the specific details of S1407 can be found in S901, and will not be repeated here.

[0561] In other implementations, the second sensing data may be obtained by processing the sensing data of at least one terminal; or, the second sensing data may be obtained by the SU processing the sensing data of at least one terminal. For example, the second sensing data may be obtained by the SU processing the sensing data of at least one terminal based on the location of at least one terminal. For details, please refer to method f1 in S902, which will not be repeated here.

[0562] Optional, Figure 14 The method shown also includes S1408 and / or S1409:

[0563] S1408: SU processes the sensing data of at least one terminal to obtain second sensing data.

[0564] Optionally, the SU processes the sensing data of at least one terminal based on the location of at least one terminal to obtain second sensing data. For details, please refer to method f1 in S902, which will not be elaborated further.

[0565] Optionally, S1408 can precede S1407.

[0566] S1409: SU sends second sensing data to CU.

[0567] For details of S1409, please refer to S905b, which will not be repeated here.

[0568] Optionally, S1408 can precede S1409.

[0569] This application does not restrict the order of S1407 and S1409.

[0570] pass Figure 14 The method shown allows the SU on the access network side to obtain the terminal's sensing data from the CU for sensing services triggered by the sensing management network element. This reduces the transmission latency of the terminal's sensing data, and the SU can process the terminal's sensing data more quickly and in real time, thereby improving sensing performance and enhancing sensing QoS or SLA.

[0571] In some cases, the access network-side device can autonomously determine whether the terminal participates in sensing, thereby acquiring the terminal's sensing data more quickly and in real time, and processing the terminal's sensing data more quickly and in real time, which can improve sensing performance and enhance sensing QoS or SLA.

[0572] Furthermore, in this method, the SU can be used for sensing, and the SU can be independent of the access network side devices used for communication (e.g., one or more of CU, DU, and RU), thereby improving the scalability of the SU and enabling higher sensing requirements to be met by upgrading the SU.

[0573] like Figure 15 As shown, the method includes:

[0574] S1501: NodeC and perception management network elements interact to meet perception requirements.

[0575] For details on S1501, please refer to S1401, except that SU is replaced with NodeC, which will not be repeated here.

[0576] S1502 to S1505: Refer to S1304 to S1307, and will not be repeated here.

[0577] S1506: NodeC sends second sensing data to the sensing management network element.

[0578] For details of S1506, please refer to S1407, except that SU is replaced with NodeC, and will not be repeated here.

[0579] Optional, Figure 15 The method shown also includes S1507 and / or S1508:

[0580] S1507: NodeC processes the sensing data of at least one terminal to obtain second sensing data.

[0581] S1508: NodeC sends second sensing data to NodeB.

[0582] For details of S1507 to S1508, please refer to S1408 to S1409, except that SU is replaced with NodeC and CU is replaced with NodeB, which will not be repeated here.

[0583] Figure 15 The technical effects of the method shown can be referenced. Figure 14 The technical effect of the method shown is simply that SU is replaced with NodeC, and CU, DU and RU are replaced with NodeB, which will not be elaborated further.

[0584] like Figure 16 As shown, the method includes:

[0585] S1601: The sensing management network element sends a first indication message to the SU, which can indicate whether a terminal is participating in sensing.

[0586] For details of S1601, please refer to S903a, which will not be repeated here.

[0587] Optionally, in S1601, the sensing management network element can also send first information to the SU, which indicates the first sensing requirement. For details, please refer to S906a, which will not be repeated here.

[0588] S1601 is an optional step.

[0589] S1602: The CU negotiates the first sensing resource with the sensing management network element.

[0590] In some implementations, S1602 may include step I1:

[0591] Step I1: The sensing management network element sends the second information to the CU, which can instruct the first sensing resource.

[0592] The specific details of step I1 can be found in method g1 of S907, except that the first device is replaced by a sensing management network element, which will not be described in detail here.

[0593] Optionally, before sending the second information, the perception management network element may select the terminal for perception. For example, the perception management network element may select a terminal that supports perception, based on, for example, the terminal's capabilities. For instance, the terminal may send information indicating its capabilities to the perception management network element via one or more of the RU, DU, and CU. If the information indicating the terminal's capabilities indicates that the terminal supports perception, the perception management network element may select that terminal. Alternatively, the terminal may send information indicating its capabilities to the perception management network element via one or more of the RU, DU, and CU, and also via core network equipment (e.g., AMF or UPF). If the information indicating the terminal's capabilities indicates that the terminal supports perception, the perception management network element may select that terminal.

[0594] Optionally, in this implementation, S1602 may also include step I2:

[0595] Step I2: The CU sends third information to the sensing management network element, which may indicate recommended and / or unrecommended sensing resources.

[0596] The details of step I2 can be found in step B1 of S907, except that the first device is replaced by a sensing management network element, which will not be repeated here.

[0597] Optionally, in this implementation, S1602 may also include step I3:

[0598] Step I3: The CU sends a first response message to the sensing management network element. The first response message can indicate whether to accept or reject the use of the first sensing resources to realize the second sensing requirement.

[0599] The details of step I3 can be found in step B2 of S907, except that the first device is replaced by a sensing management network element, which will not be described again.

[0600] Optionally, if the first response information indicates that the first sensing resource is rejected from fulfilling the second sensing requirement, the sensing management network element may re-execute S1602. For details, please refer to the description in step B2 regarding the re-execution of S907 by the first device, except that the first device is replaced by the sensing management network element, and will not be repeated here.

[0601] In other implementations, S1602 may include steps J1 to J2:

[0602] Step J1: The sensing management network element sends second information to the CU. The second information can indicate a second sensing requirement, which is used to determine the first sensing resource.

[0603] The specific details of step J1 can be found in method g2 of S907, except that the first device is replaced by a sensing management network element, which will not be described in detail here.

[0604] Optionally, before sending the second information, the sensing management network element may select the terminal to be used for sensing. The selection method can be referred to the explanation of "the sensing management network element may select the terminal to be used for sensing" in step I1 of S1602 above, and will not be repeated here.

[0605] Step J2: The CU sends a second response message to the sensing management network element. The second response message may indicate the first sensing resource; or, the second response message may indicate rejection (or disagreement or non-acceptance) of fulfilling the second sensing requirement.

[0606] The details of step J2 can be found in step C1 of S907, except that the first device is replaced by a sensing management network element, which will not be described again.

[0607] Optionally, if the second response information indicates that the second sensing request is rejected, the sensing management network element may re-execute S1602. For details, please refer to the description in step C1 regarding the re-execution of S907 by the first device, except that the first device is replaced by the sensing management network element, and will not be repeated here.

[0608] S1603: The CU sends a first indication message to the SU, which can indicate whether a terminal is involved in sensing.

[0609] For details of S1603, please refer to S903b, which will not be repeated here.

[0610] S1603 is an optional step.

[0611] The first terminal can be any of the at least one terminal. The following explanation uses the first terminal as an example to illustrate how at least one terminal acquires sensing resources.

[0612] S1604: The CU sends fourth information to the first terminal. The fourth information may indicate a second sensing resource, which may be part or all of the first sensing resource.

[0613] S1605: The first terminal sends the first terminal's sensing data to the RU.

[0614] For details on S1604 to S1605, please refer to S1205 to S1206, which will not be repeated here.

[0615] As previously stated, the first terminal is any one of at least one terminals. Each of these at least one terminals can perform operations similar to those in S1604 to S1605, so that the RU can receive sensing data from at least one terminal.

[0616] S1606: The RU sends sensing data from at least one terminal to the CU.

[0617] For details of S1606, please refer to S1207, which will not be repeated here.

[0618] S1607: The CU sends sensing data from at least one terminal to the sensing management network element.

[0619] In some implementations, if the sensing data received by the CU from the RU includes the sensing data of the terminal, the CU may execute S1607. Optionally, in S1607, the CU may send only the sensing data of at least one terminal to the sensing management network element, or the CU may send the sensing data of at least one terminal and the sensing data of the RU to the sensing management network element.

[0620] Optionally, when the CU can send terminal sensing data and RU sensing data to the sensing management network element, the CU can indicate whether the sensing data sent by the CU is terminal sensing data or RU sensing data. The indication can be explicit or implicit. For example, the sensing data of at least one terminal and the sensing data of the RU can be transmitted on different interfaces between the sensing management network element and the CU; or, the sensing data of at least one terminal and the sensing data of the RU can be transmitted on different logical links of the same interface between the sensing management network element and the CU; or, the sensing data of at least one terminal and the sensing data of the RU can be transmitted in different data packets of the same interface between the sensing management network element and the CU.

[0621] Optionally, if the sensing data received by the CU from the RU is the RU's sensing data, the CU may send the RU's sensing data to the SU, but S1607 will not be executed.

[0622] S1608: SU can send a second request to the perception management network element. The second request can be used to request the first perception data.

[0623] Optionally, if the first indication information indicates that a terminal is involved in sensing, the SU may send a second request to the sensing management network element. For details, please refer to [link / reference]. Figure 9 The explanation of "the first device can send a second request; correspondingly, the sensing management network element can receive the second request" in the method shown will not be repeated.

[0624] This application does not restrict the execution order of S1608 and S1604 to S1607.

[0625] S1609: The perception management network element sends the first perception data to the SU.

[0626] For details of S1609, please refer to S1101, and will not be repeated here.

[0627] Optionally, in S1609, the sensing management network element may also send at least one of the following to the SU: information indicating the location of at least one terminal, or information indicating the sensing area.

[0628] Optional, Figure 16 The method shown includes S1610:

[0629] S1610: SU sends second sensing data to CU.

[0630] For details regarding the second sensing data, please refer to the description of the second sensing data in S1102, which will not be repeated here.

[0631] Optional, Figure 16 The method shown includes S1611:

[0632] S1611: SU processes the first sensing data to obtain the second sensing data.

[0633] For details of S1611, please refer to step A3 in S902, which will not be repeated here.

[0634] S1611 can precede S1610.

[0635] pass Figure 16 The method shown allows the SU to request first sensing data from the sensing management network element for sensing services triggered by the sensing management network element. The first sensing data is obtained by processing the sensing data of at least one terminal based on the location of at least one terminal, thereby processing the sensing data of the terminal, improving sensing performance, and improving the QoS / SLA of sensing.

[0636] In some cases, the access network-side device can autonomously determine whether the terminal participates in sensing, thereby acquiring the terminal's sensing data more quickly and in real time, and processing the terminal's sensing data more quickly and in real time, which can improve sensing performance and enhance sensing QoS or SLA.

[0637] Furthermore, in this method, the SU can be used for sensing, and the SU can be independent of the access network side devices used for communication (e.g., one or more of CU, DU, and RU), thereby improving the scalability of the SU and enabling higher sensing requirements to be met by upgrading the SU.

[0638] like Figure 17 As shown, the method includes:

[0639] S1701: The perception management network element sends the first indication information to the NodeC. The first indication information can indicate whether there is a terminal participating in perception.

[0640] For details on S1701, please refer to S1601, except that SU is replaced with NodeC, which will not be repeated here.

[0641] S1702: NodeB negotiates the first sensing resource with the sensing management network element.

[0642] For details on S1702, please refer to S1602, except that CU is replaced by NodeB, which will not be repeated here.

[0643] S1703: NodeB sends a first indication message to NodeC, which can indicate whether a terminal is involved in sensing.

[0644] For details of S1703, please refer to S903b, which will not be repeated here.

[0645] S1703 is an optional step.

[0646] The first terminal can be any of the at least one terminal. The following explanation uses the first terminal as an example to illustrate how at least one terminal acquires sensing resources.

[0647] S1704: NodeB sends fourth information to the first terminal. The fourth information may indicate a second sensing resource, which may be part or all of the first sensing resource.

[0648] S1705: The first terminal sends its sensing data to the NodeB.

[0649] For details on S1704 to S1705, please refer to S1305 to S1306, which will not be repeated here.

[0650] As previously stated, the first terminal is any one of at least one terminals. Each of these at least one terminals can perform operations similar to S1704 and S1705, so that the NodeB can receive sensing data from at least one terminal.

[0651] S1706: NodeB sends sensing data from at least one terminal to the sensing management network element.

[0652] For details of S1706, please refer to S1607, except that CU is replaced with NodeB, RU is replaced with NodeB, and SU is replaced with NodeC. Further details will not be repeated here.

[0653] In some implementations, if the sensing data acquired by the NodeB includes the sensing data of the terminal, the NodeB may execute S1706. Optionally, in S1706, the NodeB may send only the sensing data of at least one terminal to the sensing management network element, or the NodeB may send the sensing data of at least one terminal and the NodeB's sensing data to the sensing management network element.

[0654] Optionally, if the sensing data acquired by NodeB is NodeB's own sensing data, NodeB may send NodeB's sensing data to NodeC, but S1706 will not be executed.

[0655] S1707: NodeC can send a second request to the perception management network element. The second request can be used to request the first perception data.

[0656] S1708: The perception management network element sends the first perception data to the NodeC.

[0657] For details of S1707 to S1708, please refer to S1608 to S1609, except that SU is replaced with NodeC, and will not be repeated here.

[0658] Optional, Figure 17 The method shown also includes S1709:

[0659] S1709: NodeC sends second sensing data to NodeB.

[0660] For details regarding the second sensing data, please refer to the description of the second sensing data in S1102, which will not be repeated here.

[0661] Optional, Figure 17 The method shown includes S1710:

[0662] S1710: NodeC processes the first sensing data to obtain the second sensing data.

[0663] For details of S1710, please refer to step A3 in S902, which will not be repeated here.

[0664] S1710 precedes S1709.

[0665] Figure 17 The technical effects of the method shown can be referenced. Figure 16 The technical effect of the method shown is simply that SU is replaced with NodeC, and CU, DU and RU are replaced with NodeB, which will not be elaborated further.

[0666] Based on the same technical concept as the above-described method embodiments, this application provides a corresponding communication device that can be used to perform the functions of the relevant steps in the above-described method embodiments. This function can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. The communication device can be a logic unit on the access network side, or a device (e.g., a circuit or chip) within a logic unit on the access network side, or a logic node, logic module, or software capable of implementing all or part of the functions of the logic unit on the access network side; or the communication device can be an access network device or a device (e.g., a circuit or chip) within an access network device, or a logic node, logic module, or software capable of implementing all or part of the functions of the access network device.

[0667] In one possible implementation, the communication device provided in this application embodiment has the following structure: Figure 18 As shown, the communication device includes a processing unit 1802. Optionally, the communication device may also include an interface unit 1801. The functions of each unit in the communication device 1800 are described below.

[0668] Interface unit 1801 is used for inputting and / or outputting information. Input information can be replaced by received information, and output information can be replaced by transmitted information. When outputting information, interface unit 1801 can output information to other devices outside of communication device 1800, or to other units within communication device 1800. In some embodiments, interface unit 1801 can be implemented through at least one of a physical interface, a communication module, a communication interface, and an input / output interface. In other embodiments, interface unit 1801 can be implemented through interface circuitry, such as a mobile communication module. The mobile communication module may include one or more of at least one antenna, at least one filter, a switch, a power amplifier, a low-noise amplifier (LNA), etc.

[0669] The processing unit 1802 can be used to support the communication device 1800 in performing the processing actions in the above method embodiments. The processing unit 1802 can be implemented by one or more processors. For example, the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0670] In one embodiment, the communication device 1800 is applied to Figure 9 The first device in this embodiment of the application is shown. The specific functions of the processing unit 1802 in this embodiment will be described below.

[0671] The processing unit 1802 is configured to: receive sensing data from at least one terminal through the interface unit 1801; and process the sensing data from at least one terminal based on whether the location of at least one terminal has been obtained.

[0672] In some possible embodiments, the processing unit 1802 is specifically configured to: if the location of at least one terminal is obtained, process the sensing data of at least one terminal based on the location of at least one terminal; and / or, if the location of at least one terminal is not obtained, send the sensing data of at least one terminal through the interface unit 1801, and receive first sensing data through the interface unit 1801, the first sensing data being obtained by processing the sensing data of at least one terminal based on the location of at least one terminal.

[0673] Optionally, the processing unit 1802 is further configured to: receive first indication information through the interface unit 1801, the first indication information indicating whether a terminal is involved in sensing.

[0674] Optionally, the processing unit 1802 is further configured to: send a first request through the interface unit 1801 when the first indication information indicates that a terminal is involved in sensing, the first request being used to request the location of at least one terminal; and / or, when the first indication information indicates that a terminal is involved in sensing and the location of at least one terminal has not been obtained, send a second request through the interface unit 1801, the second request being used to request first sensing data, the first sensing data being obtained by processing the sensing data of at least one terminal based on the location of at least one terminal.

[0675] In some implementations, the processing unit 1802 is further configured to: acquire second sensing data; wherein, if the location of at least one terminal is acquired, the second sensing data is obtained by fusing sensing data of at least one terminal and third sensing data sensed by the access network side; and / or, if the location of at least one terminal is not acquired, the second sensing data is obtained by fusing first sensing data and third sensing data sensed by the access network side, wherein the first sensing data is obtained by processing sensing data of at least one terminal based on the location of at least one terminal.

[0676] Optionally, the processing unit 1802 is further configured to: send second sensing data through the interface unit 1801, the second sensing data corresponding to sensing data of at least one terminal.

[0677] In some possible configurations, the processing unit 1802 is further configured to: receive first information via the interface unit 1801, the first information indicating a first sensing requirement; and send second information via the interface unit 1801, the second information being used to determine a first sensing resource, the first sensing resource being used by at least one terminal to send and / or receive sensing signals, the sent and / or received sensing signals corresponding to a second sensing requirement, the second sensing requirement being determined based on the first sensing requirement.

[0678] In some implementations, the processing unit 1802 is further configured to: receive third information through the interface unit 1801 when the second information indicates the first sensing resource, the third information indicating recommended and / or unrecommended sensing resources, the third information being used to determine the first sensing resource.

[0679] In other implementations, the processing unit 1802 is further configured to: receive first response information through the interface unit 1801 when the second information indicates the first sensing resource, the first response information indicating whether to accept or reject the use of the first sensing resource to fulfill the second sensing requirement.

[0680] In some implementations, the processing unit 1802 is also configured to: receive second response information through the interface unit 1801 when the second information indicates a second sensing requirement, the second response information indicating a first sensing resource, or the second response information indicating a refusal to fulfill the second sensing requirement.

[0681] Optionally, the processing unit 1802 is specifically used to: receive first information from the sensing management network element through the interface unit 1801; or, receive first information from the second logic unit or the second access network device through the interface unit 1801.

[0682] For a more detailed description of the processing unit 1802 and the interface unit 1801 mentioned above, please refer to [link / reference]. Figure 9The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0683] It should be noted that the module division in the above embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical entities, or have two or more units integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

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

[0685] In one possible implementation, the communication device provided in the embodiments of this application is described below. Figure 19 As shown, the communication device 1900 includes a processor 1902. Optionally, the communication device 1900 may also include an interface circuit 1901 and a memory 1903. The interface circuit 1901, the processor 1902, and the memory 1903 are coupled to each other.

[0686] Optionally, the interface circuit 1901, processor 1902, and memory 1903 are coupled to each other via bus 1904. Bus 1904 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 19 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0687] Interface circuit 1901 is used for inputting and / or outputting information. Input information can be replaced by received information, and output information can be replaced by transmitted information. When outputting information, interface circuit 1901 can output information to other devices outside of communication device 1900, or to other units within communication device 1900. For example, interface circuit 1901 can be implemented through at least one of a physical interface, a communication module, a communication interface, an input / output interface, and a mobile communication module. The mobile communication module may include one or more of at least one antenna, at least one filter, a switch, a power amplifier, an LNA, etc.

[0688] Processor 1902 can be used to support communication device 1900 in performing the processing actions in the above method embodiments. When communication device 1900 is used to implement the above method embodiments, processor 1902 can also be used to implement the functions of processing unit 1802. Processor 1902 can be a CPU, or other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. General-purpose processors can be microprocessors or any conventional processor.

[0689] In one embodiment, the communication device 1900 is applied to Figure 9 The first device in this embodiment of the application is shown. The specific functions of the processor 1902 in this embodiment are described below.

[0690] The processor 1902 is configured to: receive sensing data from at least one terminal via interface circuit 1901; and process the sensing data from at least one terminal based on whether the location of at least one terminal has been obtained.

[0691] The specific functions of processor 1902 can be found in the descriptions of the communication methods provided in the embodiments and examples of this application above. Figure 18 The specific functional description of the communication device 1800 shown in the embodiments of this application will not be repeated here.

[0692] Memory 1903 is used to store program instructions and / or data. Specifically, program instructions may include program code, which includes computer operation instructions. Memory 1903 may include RAM and may also include non-volatile memory, such as at least one disk storage device. Processor 1902 executes the program instructions stored in memory 1903 and uses the data stored in memory 1903 to implement the above-mentioned functions, thereby realizing the communication method provided in the embodiments of this application. Memory 1903 may be integrated with processor 1902 or may be a memory outside the communication device.

[0693] It is understood that this application Figure 19 The memory 1903 can be volatile memory or non-volatile memory, or may include both. The non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0694] Based on the above embodiments, this application also provides a computer program product including computer-executable instructions, which, when run, causes the methods provided in the above embodiments to be executed.

[0695] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the methods provided in the above embodiments.

[0696] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0697] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory to implement the method provided in the above embodiments.

[0698] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. The chip system may be composed of chips or may include chips and other discrete components.

[0699] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0700] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0701] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0702] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0703] In this application, "at least one" or "at least one item" refers to one or more, and "more than one" refers to two or more. "And / or" describes 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, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0704] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0705] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method characterized by comprising: A first logical unit or a first access network device applied to an access network, the first access network device comprising the first logical unit, the first logical unit being configured to sense, and the method comprising: receiving sensing data of at least one terminal; processing the sensing data of the at least one terminal according to whether the position of the at least one terminal is acquired.

2. The method of claim 1, wherein, Processing the sensing data of the at least one terminal according to whether the position of the at least one terminal is acquired, comprising: in the case where the position of the at least one terminal is acquired, processing the sensing data of the at least one terminal according to the position of the at least one terminal; and / or in the case where the position of the at least one terminal is not acquired, sending the sensing data of the at least one terminal, receiving first sensing data, the first sensing data being obtained by processing the sensing data of the at least one terminal according to the position of the at least one terminal.

3. The method of claim 1 or 2, wherein, Further comprising: receiving first indication information, the first indication information indicating whether there is a terminal participating in sensing.

4. The method of claim 3, wherein, Further comprising: in the case where the first indication information indicates that there is a terminal participating in sensing, sending a first request, the first request being used to request the position of the at least one terminal; and / or in the case where the first indication information indicates that there is a terminal participating in sensing and the position of the at least one terminal is not acquired, sending a second request, the second request being used to request first sensing data, the first sensing data being obtained by processing the sensing data of the at least one terminal according to the position of the at least one terminal.

5. The method according to any one of claims 1 to 4, characterized in that, Further comprising: acquiring second sensing data; wherein, in the case where the position of the at least one terminal is acquired, the second sensing data is obtained by fusing the sensing data of the at least one terminal and third sensing data sensed by the access network side; and / or, in the case where the position of the at least one terminal is not acquired, the second sensing data is obtained by fusing the first sensing data and the third sensing data sensed by the access network side, the first sensing data being obtained by processing the sensing data of the at least one terminal according to the position of the at least one terminal.

6. The method of claim 5, wherein, The sensing data of the at least one terminal and the third sensing data are transmitted on different interfaces, or on different logical links on the same interface, or are contained in different data packets.

7. The method according to any one of claims 1 to 6, wherein, Further comprising: sending the second sensing data, the second sensing data corresponding to the sensing data of the at least one terminal.

8. The method according to any one of claims 1 to 7, characterized in that, Further comprising: receiving first information, the first information indicating a first sensing requirement; sending second information, the second information being used to determine a first sensing resource, the first sensing resource being used for the at least one terminal to send and / or receive sensing signals, the sending and / or receiving sensing signals corresponding to a second sensing requirement, the second sensing requirement being determined according to the first sensing requirement.

9. The method of claim 8, wherein, The second information being used to determine a first sensing resource, comprising: the second information indicating the first sensing resource; or the second information indicating the second sensing requirement, the second sensing requirement being used to determine the first sensing resource.

10. The method of claim 9, wherein, in case that the second information indicates the first sensing resource, further comprising: receiving third information, the third information indicating recommended and / or non-recommended sensing resource, the third information being used for determining the first sensing resource.

11. The method of claim 9 or 10, wherein, in case that the second information indicates the first sensing resource, further comprising: receiving first response information, the first response information indicating that the first sensing resource is accepted or rejected for fulfilling the second sensing requirement.

12. The method of claim 11, wherein, in case that the first response information indicates that the first sensing resource is rejected for fulfilling the second sensing requirement, the first response information further indicating at least one of: a reason for rejection; or a recommended and / or non-recommended sensing resource.

13. The method according to any one of claims 9 to 12, characterized in that, in case that the second information indicates the first sensing resource, the second information further indicating at least one of: a transceiving mode in which the at least one terminal performs sensing; or an area in which the at least one terminal performs sensing.

14. The method of claim 9, wherein, in case that the second information indicates the second sensing requirement, further comprising: receiving second response information, the second response information indicating the first sensing resource, or the second response information indicating that the second sensing requirement is rejected.

15. The method of claim 14, wherein, in case that the second response information indicates the first sensing resource, the second response information further indicating at least one of: a transceiving mode in which the at least one terminal performs sensing; or an area in which the at least one terminal performs sensing.

16. The method of claim 14, wherein, in case that the second response information indicates that the second sensing requirement is rejected, the second response information further indicating at least one of: a reason for rejection; a recommended and / or non-recommended sensing resource; or a sensing requirement that can be fulfilled.

17. The method of claim 12 or 16, wherein, the reason for rejection comprises at least one of: insufficient time domain resource; insufficient frequency domain resource; insufficient spatial domain resource; insufficient code domain resource; insufficient power domain resource; no terminal available for sensing; or the terminal does not meet the second sensing requirement.

18. The method of any one of claims 8 to 17, wherein, receiving first information, comprising: receiving the first information from a sensing management network element; or receiving the first information from a second logical unit or a second access network device.

19. The method of any one of claims 8 to 18, wherein, the first sensing requirement comprises at least one of the following information: sensing quality of service (QoS) or service level agreement (SLA); type of sensing data; time of sensing; or area of sensing.

20. The method of claim 19, wherein, the type of sensing data comprises at least one of: in-phase and quadrature (I / Q) signal, range-angle-velocity (RAV) spectrum information, channel frequency response (CFR) information, point cloud information, or sensing target information.

21. A communications device, characterized by comprising means for performing the method of any of claims 1-20.

22. A communications device, characterized by comprising a processor configured to execute computer program or instructions, such that the apparatus performs the method of any of claims 1-20.

23. A computer-readable storage medium, characterized in that, the computer readable storage medium has stored therein computer programs or instructions which, when executed, implement the method of any of claims 1-20.

24. A computer program product, characterised in that, the computer program product comprises computer program code which, when executed, implements the method of any of claims 1-20.

Images