Devices, methods, and computer-readable media for integrating sensing and communication

Abstract

Embodiments of this disclosure relate to an apparatus, method, and computer-readable medium for ISAC. A terminal device sends a random access (RA) request for a sensing service. The RA request includes an RA preamble and a first type of information related to the sensing service. The terminal device receives response information to the RA request.

Description

Technical Field

[0001] The embodiments disclosed herein relate generally to the telecommunications field, and more particularly to an apparatus, method, and computer-readable medium for Integrated Sensing and Communication (ISAC). Background Technology

[0002] ISAC is considered a promising topic for the future expansion of wireless networks. In the early stages of the 3GPP (Third Generation Partnership Project), the discussion of ISAC likely aimed to build communication-based sensing systems. For terminal devices in Radio Resource Control (RRC) idle or RRC inactive states, a random access procedure may be required to initiate the sensing process. Summary of the Invention

[0003] Generally, the exemplary embodiments of this disclosure provide an apparatus, method, and computer-readable medium for ISAC.

[0004] In a first aspect, a terminal device is provided. The terminal device includes a processor. The processor is configured to cause the terminal device to: send a random access (RA) request for a sensing service, the RA request including an RA preamble and first type of information related to the sensing service; and receive response information to the RA request.

[0005] In a second aspect, a network device is provided. The network device includes a processor. The processor is configured to cause the network device to: receive a RA request for a sensing service, the RA request including an RA preamble and first type of information related to the sensing service; determine response information for the RA request; and send the response information for the RA request.

[0006] In a third aspect, a method for ISAC is provided. The method includes: sending a RA request for a sensing service, the RA request including an RA preamble and first type of information related to the sensing service; and receiving response information to the RA request.

[0007] In a fourth aspect, a method for ISAC is provided. The method includes: receiving a RA request for a sensing service, the RA request including an RA preamble and first type of information related to the sensing service; determining response information for the RA request; and sending the response information for the RA request.

[0008] In a fifth aspect, a computer-readable medium is provided that stores instructions. When executed on at least one processor of a device, these instructions cause the device to perform the method according to the third or fourth aspect.

[0009] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other objects, features and advantages of this disclosure will become more apparent from a more detailed description of some embodiments thereof in the accompanying drawings, wherein: Figure 1A and Figure 1B Example communication networks that can implement the embodiments of this disclosure are illustrated respectively; Figure 2 Signaling diagrams illustrating a contention-based random access (CBRA) procedure of type 4 RA according to some embodiments of this disclosure are shown; Figure 3 Signaling diagrams illustrating a CBRA process of type 2 RA according to some embodiments of this disclosure are shown; Figure 4 The following is an example of a signaling diagram illustrating a fallback process for a CBRA with a 2-step RA type, according to some embodiments of this disclosure; Figure 5 Signaling diagrams illustrating a contention-free random access (CFRA) procedure of a 4-step RA type are shown according to some embodiments of this disclosure; Figure 6 Signaling diagrams illustrating a CFRA process of type 2 RA according to some embodiments of this disclosure are shown; Figure 7 , Figure 8 , Figure 9 and Figure 10A Signaling diagrams illustrating example procedures for ISAC according to some embodiments of this disclosure are shown respectively; Figure 10B Examples of MAC subheaders according to some embodiments of this disclosure are shown; Figure 11 Examples of MAC PDUs according to some example embodiments of this disclosure are illustrated; Figure 12AExamples of MAC PDUs according to some embodiments of this disclosure are illustrated; Figure 12B Examples of MAC subheaders according to some embodiments of this disclosure are shown; Figure 12C and Figure 12D Examples of MAC SDUs according to some embodiments of this disclosure are illustrated respectively; Figure 13A Examples of MAC PDUs according to some embodiments of this disclosure are illustrated; Figure 13B and Figure 13C Examples of MAC subheaders according to some embodiments of this disclosure are illustrated respectively; Figure 13D Examples of some embodiments according to this disclosure are illustrated. Figure 13A Example of a MAC SDU; Figure 14 Signaling diagrams illustrating example procedures for ISAC according to some embodiments of this disclosure are shown; Figure 15 Examples of determining response information to a sensing request according to some embodiments of this disclosure are illustrated; Figure 16 Examples of ISAC systems according to some exemplary embodiments of this disclosure are illustrated; Figure 17 Signaling diagrams illustrating example procedures for ISAC according to some embodiments of this disclosure are shown; Figure 18 Flowcharts illustrating example methods according to some embodiments of this disclosure are shown; Figure 19 Flowcharts illustrating example methods according to some embodiments of this disclosure are shown; and Figure 20 This is a simplified block diagram of an apparatus suitable for implementing embodiments of this disclosure.

[0011] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0012] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing this disclosure, and are not intended to limit the scope of this disclosure in any way. The disclosure described herein can be implemented in various ways other than those described below.

[0013] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0014] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE); personal computers; desktop computers; mobile phones; cellular phones; smartphones; personal digital assistants (PDAs); portable computers; tablets; wearable devices; Internet of Things (IoT) devices; Ultra-reliable and Low-Latency Communication (URLLC) devices; Internet of Everything (IoE) devices; machine-type communication (MTC) devices; devices on vehicles for V2X communication, where X refers to pedestrians, vehicles, or infrastructure / networks; devices for Integrated Access and Backhaul (IAB); devices for Small Data Transmission (SDT); mobility devices; devices for Multicast and Broadcast Service (MBS); devices for location services; devices for dynamic / flexible duplexing in commercial networks; RedCap (red-cap) devices; and non-terrestrial networks (NTNs). In the context of a non-terrestrial network, spacecraft or aircraft vehicles are included. These non-terrestrial networks include satellites and high-altitude platforms (HAPs) encompassing unmanned aircraft systems (UAS); extended reality (XR) devices that include different types of reality (such as augmented reality (AR), mixed reality (MR), and virtual reality (VR)); unmanned aerial vehicles (UAVs), often referred to as drones (aircraft without any human pilots); equipment on high-speed trains (HSTs); or image capture devices such as digital cameras and sensors; gaming devices; music storage and playback devices; or internet devices that enable wireless or wired internet access and browsing.The "terminal device" may also have "multicast / broadcast" capabilities to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, wireless software delivery, group communications, and IoT applications. The "terminal device" may also incorporate one or more Subscriber Identity Modules (SIMs), a latter case referred to as multi-SIM. The term "terminal device" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0015] The term "network device" refers to a device that provides or hosts a cell or coverage area for terminal devices to communicate. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), next-generation NodeBs (gNBs), transmission reception points (TRPs), remote radio units (RRUs), radioheads (RHs), remote radio heads (RRHs), IAB nodes, low-power nodes (such as femtonodes and piconodes), reconfigurable intelligent surfaces (RISs), and network-controlled repeaters.

[0016] Terminal devices or network devices may have artificial intelligence (AI) or machine learning capabilities. Terminal devices or network devices typically include models that have been trained on specific functions based on a large amount of collected data and can be used to predict some information.

[0017] Terminal or network devices can operate within several frequency ranges, such as FR1 (410MHz to 7125MHz), FR2 (24.25GHz to 71GHz), bands above 100GHz, and terahertz (THz). They can also operate on licensed / unlicensed / shared spectrum. In Multi-Radio Dual Connectivity (MR-DC) applications, terminal devices can be connected to more than one network device. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-division duplex modes.

[0018] Network devices may feature network energy saving and self-organizing network (SON) / minimization of drive test (MDT) capabilities. Terminals may feature power saving capabilities.

[0019] The embodiments disclosed herein can be implemented in test equipment (e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal equipment, test network equipment, channel simulator).

[0020] The embodiments disclosed herein can be implemented according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, 5G-Advanced Networks, or sixth-generation (6G) networks.

[0021] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “some embodiments” and “one embodiment” should be understood as “at least some embodiments.” The term “another embodiment” should be understood as “at least one other embodiment.” The terms “first,” “second,” etc., may refer to different or the same objects. Other explicit and implicit definitions are given below.

[0022] In some examples, values, processes, or devices are described as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many alternative functionalities used, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0023] Figure 1A A schematic diagram illustrating an example communication network 100A that can implement an embodiment of this disclosure is provided. Figure 1AAs shown, the communication network 100A may include terminal equipment 110, terminal equipment 120, control node 130, access and mobility management function (AMF) 140 and sensing function (SF) 150.

[0024] It should be understood that Figure 1A The number of devices is given for illustrative purposes and does not constitute any limitation on this disclosure. The communication network 100A may include any suitable number of devices suitable for implementing embodiments of this disclosure.

[0025] In some implementations, the terminal device 110 may include at least one of a sensing module and a communication module. For example, such as Figure 1A As shown, the terminal device 110 includes a sensing module 110-1 and a communication module 110-2.

[0026] In some implementations, the sensing module 110-1 in the terminal device 110 may include at least one of the Uu sensing module 110-11 or the sidelink sensing module 110-12.

[0027] In some implementations, Uu sensing modules 110-11 may be configured to perform Uu sensing functions based on network assistance or control, and the Uu sensing functions may include at least one of downlink sensing functions and uplink sensing functions. Sidelink sensing modules 110-12 may be configured to perform sidelink sensing functions.

[0028] Similarly, in some embodiments, the terminal device 120 may include at least one of a sensing module and a communication module. For example, as Figure 1A As shown, the terminal device 120 includes a sensing module 120-1 and a communication module 120-2.

[0029] In some implementations, the control node 130 may include at least one of a sensing module and a communication module. For example, as... Figure 1A As shown, the control node 130 includes a sensing module 130-1 and a communication module 130-2.

[0030] In some implementations, control node 130 may be implemented as a network device (such as a gNB in ​​NR). In such implementations, control node 130 may be referred to as network device 130.

[0031] Alternatively, in some embodiments, control node 130 may be implemented as a roadside unit (RSU). In such embodiments, control node 130 may be referred to as RSU 130.

[0032] Alternatively, in some embodiments, the control node 130 may be implemented as a sense transmit / receive point (TRP). In such embodiments, the control node 130 may be referred to as TRP 130.

[0033] Alternatively, in some embodiments, terminal device 120 may be implemented as a sensing TRP. In such embodiments, terminal device 120 may be referred to as TRP 120.

[0034] In some implementations, AMF 140 may be a node in the core network. AMF 140 may provide matching information about control node 130 or terminal device 110 based on sensing requirements.

[0035] The communications in communication network 100A may conform to any suitable standard, including but not limited to Global System for Mobile Communication (GSM), LTE, LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Furthermore, these communications may be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), and sixth-generation (6G) communication protocols.

[0036] In some implementations, communication in communication network 100A may include ISAC. Communication networks employing ISAC can share hardware architecture, channel characteristics, and signal processing, and integrate various types of sensing information (such as sensing data from the environment and radar-based sensing information) as well as communication information to achieve higher resource efficiency and provide a smarter, more integrated network solution. ISAC networks can be applied in a wider range of scenarios, including smart homes, smart manufacturing, and environmental monitoring.

[0037] In some implementations, control node 130 may include at least one of the following: The first interface between control node 130 and terminal device 110 The second interface between control node 130 and AMF 140, or The third interface between control node 130 and SF 150.

[0038] In some implementations, terminal device 110 may include at least one of the following: The first interface between control node 130 and terminal device 110 The fourth interface between terminal device 110 and AMF 140, or The fifth interface between terminal device 110 and terminal device 120.

[0039] In implementations where control node 130 is a gNB, the first interface between control node 130 and terminal device 110 can be a Uu interface. In some implementations, sidelink sensing information can be exchanged between control node 130 and terminal device 110 on the Uu interface.

[0040] In some implementations, the Uu sensing process can be performed between the control node 130 and the terminal device 110, and Uu sensing function related information can be exchanged, for example, between the sensing module 130-1 of the control node 130 and the sensing module 110-1 of the terminal device 110.

[0041] In some implementations, the fifth interface between terminal device 110 and terminal device 120 may be a unified air interface, such as a PC5 interface. In such implementations, a sidelink sensing process may be performed between terminal device 110 and terminal device 120, and sidelink sensing function-related information may be exchanged on the PC5 interface (i.e., between sensing module 110-1 of terminal device 110 and sensing module 120-1 of terminal device 120).

[0042] In the example communication network 100A, there is no interface between SF 150 and control node 130. Therefore, SF 150 exchanges information indirectly with control node 130 through AMF 140.

[0043] In the example communication network 100A, terminal device 110 includes a fourth interface between terminal device 110 and AMF 140. AMF 140 can send sensing-related information about terminal device 110 to terminal device 110 via the fourth interface.

[0044] Figure 1B A schematic diagram of another example communication network 100B that can implement embodiments of the present disclosure is illustrated. Example communication network 100B is similar to example communication network 100A. The difference between example communication network 100B and example communication network 100A is that, in example communication network 100B, control node 130 includes a third interface between control node 130 and SF 150. SF 150 can exchange sensing-related information with sensing module 130-1 in control node 130 via the third interface.

[0045] In addition, in the example communication network 100B, terminal device 110 does not include a fourth interface between terminal device 110 and AMF 140. Terminal device 110 can exchange information with AMF 140 through control node 130.

[0046] When sensing services are required, the sensing terminal device may not be in a Radio Resource Control (RRC) connected state and may need to go through relevant processes to change the state of the terminal device in the Radio Access Network (RAN) for further operation.

[0047] For terminal devices in a Radio Resource Control (RRC) Idle or RRC Inactive state, a random access procedure may be required to initiate the sensing process.

[0048] Furthermore, the terminal device can perform the sensing process without communication requirements. Therefore, it may not be necessary to establish an RRC connection in the communication system.

[0049] In view of this, the embodiments of this disclosure provide a solution for ISAC. In this solution, the terminal device sends a RA request for a sensing service. The RA request includes at least one of the following: an RA preamble or information of a first type related to the sensing service. The terminal device receives response information to the RA request. This solution provides a mechanism for initiating a sensing process for a terminal device in the RRC_IDLE or RRC_INACTIVE state. The terminal device can reuse the RA mechanism in the communication system to establish a connection with the control node and then begin executing the sensing-related process. This solution enables terminal devices in the RRC_IDLE or RRC_INACTIVE state to initiate sensing services in the ISAC system with lower complexity. Furthermore, this solution reduces the latency of the sensing service and reduces the overhead and power consumption used to trigger the sensing service.

[0050] In the following text, reference will be made to Figures 2 to 6 Describe the implementation plan for the RA process.

[0051] Figure 2 A signaling diagram illustrating a contention-based random access (CBRA) procedure 200 with a 4-step RA type according to some embodiments of this disclosure is shown. A CBRA procedure with a 4-step RA type is also referred to as a 4-step CBRA procedure. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe CBRA process 200. CBRA process 200 may involve Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0052] like Figure 2 As shown, terminal device 110 sends an RA request 210, including an RA preamble, to network device 130 on the physical random access channel (PRACH). The RA request in the RA process with a 4-step RA type is also referred to as message 1 (MSG1).

[0053] After MSG1 is sent, terminal device 110 monitors for random access response (RAR) from network device 130 within a configured window. The random access response in an RA process with a 4-step RA type is also referred to as message 2 (MSG2).

[0054] For CBRA, upon receiving a 220 random access response, terminal device 110 uses the uplink (UL) grant scheduled in the random access response to perform the 230 scheduled transmission and monitors contention resolution. The scheduled transmission using the UL grant scheduled in MSG2 is also referred to as message 3 (MSG3). MSG3 includes the ID of terminal device 110.

[0055] Network device 130 sends a 240 contention resolution message. The contention resolution message includes the identifier (ID) of the end device. The contention resolution message in an RA process with a 4-step RA type is also referred to as message 4 (MSG4).

[0056] If terminal device 110 determines that the ID of terminal device 110 sent in MSG3 matches the ID received in MSG4, then terminal device 110 can declare the RA process successful.

[0057] Figure 3 Signaling diagrams of an illustrative CBRA process 300 with a 2-step RA type according to some embodiments of this disclosure are shown. A CBRA process with a 2-step RA type is also referred to as a 2-step CBRA process. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe CBRA process 300. CBRA process 300 may involve Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0058] like Figure 3 As shown, terminal device 110 sends a 310 RA request to network device 130. This RA request includes an RA preamble on the PRACH and a payload on the physical uplink control channel (PUSCH). RA requests in a 2-step RA process are also referred to as message A (MSGA). The payload on the PUSCH includes the ID of terminal device 110.

[0059] After the MSGA is sent, the terminal device 110 monitors the response from the network device 130 within the configured window.

[0060] Network device 130 sends a 320 contention resolution message. The contention resolution message includes the ID of the end device. Contention resolution messages in RA processes with a 2-step RA type are also referred to as message B (MSGB).

[0061] If terminal device 110 determines that the ID of terminal device 110 transmitted in the payload on PUSCH matches the ID received in MSGB, then terminal device 110 may declare the RA process successful.

[0062] For CBRA, if the contention is successfully resolved upon receiving a response, the terminal device 110 terminates the random access procedure.

[0063] On the other hand, if a fallback instruction is received in the MSGB, the terminal device 110 uses the UL authorization scheduled in the fallback instruction to perform MSG3 transmission and monitors contention resolution, such as... Figure 4 As shown.

[0064] Figure 4 An illustrative signaling diagram for a fallback procedure 400 with a 2-step RA type is shown according to some embodiments of this disclosure. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe rollback process 400. Rollback process 400 may involve Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0065] like Figure 4 As shown, terminal device 110 sends a 410 RA request to network device 130. The RA request includes an RA preamble on PRACH and a payload on PUSCH. The payload on PUSCH includes the ID of terminal device 110.

[0066] After the MSGA is sent, the terminal device 110 monitors the response from the network device 130 within the configured window.

[0067] Terminal device 110 receives MSGB 420 including a fallback instruction. Then, terminal device 110 uses the UL authorization scheduled in the fallback instruction to perform MSG3 transmission 430 and monitors contention resolution.

[0068] Figure 4 Action 440 in the middle is similar to Figure 2 Action 240. For the sake of brevity, details of action 440 have been omitted.

[0069] Figure 5 A signaling diagram illustrating a contention-free random access (CFRA) procedure 500 with a 4-step RA type is shown according to some embodiments of this disclosure. A CFRA procedure with a 4-step RA type is also referred to as a 4-step CFRA procedure. For discussion purposes, reference will be made to... Figure 1A or Figure 1B This describes CFRA process 500. CFRA process 500 may involve... Figure 1Aor Figure 1B Terminal device 110 and network device 130.

[0070] like Figure 5 As shown, network device 130 assigns a dedicated RA preamble (505) for MSG1 transmission. The message used to assign the dedicated RA preamble is also called message 0 (MSG0).

[0071] Terminal device 110 sends a RA request (i.e., MSG1) including a dedicated RA preamble to network device 130 on PRACH.

[0072] After MSG1 is sent, terminal device 110 monitors the RAR (i.e., MSG2) from network device 130 within the configured window.

[0073] For CFRA, after receiving RAR from network device 130 at 520, terminal device 110 ends the RA process.

[0074] Figure 6 Signaling diagrams of an illustrative CFRA process 600 with a 2-step RA type according to some embodiments of this disclosure are shown. A CFRA process with a 2-step RA type is also referred to as a 2-step CFRA process. For discussion purposes, reference will be made to... Figure 1A or Figure 1B This describes CFRA process 600. CFRA process 600 may involve... Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0075] like Figure 6 As shown, network device 130 assigns 605 dedicated RA preamble and PUSCH resources for MSGA transmission.

[0076] Terminal device 110 sends a 610 RA request (i.e., MSGA) to network device 130. The RA request includes a dedicated RA preamble on PRACH and a payload on PUSCH resources assigned by network device 130.

[0077] After the MSGA is sent, terminal device 110 monitors the RAR (i.e., MSGB) from network device 130 within the configured window.

[0078] For CFRA, after receiving RAR from network device 130 at 620, terminal device 110 ends the RA process.

[0079] For terminal device 110 in the RRC_IDLE or RRC_INACTIVE state, any of RA procedures 200, 300, 500, and 600 can be triggered by a sensing request. For example, a sensing request can be indicated from network device 130 or SF 150. Alternatively, a sensing request can be indicated from a higher layer within terminal device 110 itself. When network device 130, SF 150, or a higher layer indicates a sensing request to terminal device 110, terminal device 110 initiates an RA procedure triggered by the sensing request. Terminal device 110 can reuse any of RA procedures 200, 300, 500, and 600 to initiate an RRC connection to network device 130. Without a specific RA configuration for sensing services, terminal device 110 and network device 130 cannot identify that the RA procedure was triggered by a sensing request; that is, sensing-related information and requests should be exchanged between terminal device 110 and network device 130 after the RA procedure is completed.

[0080] In the following text, for the sake of brevity, the RA process triggered by a sensing request will also be referred to as a "sensor-triggered RA process". The term "sensing request" is used interchangeably with "sensing service request".

[0081] Based on the sense-triggered RA process, the terminal device 110 may perform at least one of the following: Establish an RRC connection with the network device, that is, transition to the RRC_CONNECTED state; Request or obtain sensing configuration information from network device 130; Request or obtain sensing resource allocation from network device 130; or Send a sensing result report to network device 130.

[0082] Based on the sense-triggered RA process, network device 130 may perform at least one of the following: Establish an RRC connection with terminal device 110; The sensing requirements of the identification terminal device 110; Notify terminal device 110 of sensing configuration information; Schedule sensing resources for terminal device 110; or Obtain a report of the sensing results.

[0083] It should be noted that terminal device 110 can directly obtain sensing configuration information or sensing resource allocation from network device 130 through a sensing-triggered RA process, without needing to establish an RRC connection with network device 130. In other words, terminal device 110 can execute the sensing process in the RRC_IDLE or RRC_INACTIVE state. Thus, terminal device 110 can initiate the sensing process in the RRC_IDLE or RRC_INACTIVE state. Furthermore, this reduces the latency of the sensing service and lowers the overhead and power consumption used to trigger the sensing service.

[0084] In some implementations, the sense-triggered RA process may be indicated by the physical downlink control channel (PDCCH), by the MAC entity of the terminal device 110 itself, or by the radio resource control (RRC) message used for the sense request.

[0085] Figure 7 Signaling diagrams illustrating example procedure 700 for ISAC according to some embodiments of this disclosure are shown. Reference will be made to these diagrams for discussion purposes. Figure 1A or Figure 1B Let's describe process 700. Process 700 may involve... Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0086] like Figure 7 As shown, terminal device 110 sends a RA request for sensing services to network device 130. The RA request includes at least one of the following: an RA preamble or information of a first type related to the sensing services.

[0087] In some implementations, the first type of information related to the sensing service includes at least one of the following: a sensing request from the terminal device 110; or a sensing result report.

[0088] Upon receiving a RA request for sensing services, network device 130 determines 720's response information to the RA request.

[0089] Subsequently, network device 130 sends 730's response information to the terminal device 110 regarding the RA request.

[0090] Process 700 provides a mechanism for initiating a sensing process for a terminal device 110 in the RRC_IDLE or RRC_INACTIVE state. The terminal device 110 can reuse the RA mechanism in the communication system to establish a connection with the control node and then begin executing sensing-related processes. Process 700 enables terminal devices in the RRC_IDLE or RRC_INACTIVE state to initiate sensing services in the ISAC system with lower complexity. Furthermore, Process 700 reduces the latency of sensing services and lowers the overhead and power consumption used to trigger sensing services.

[0091] In some implementations, for a sensing-triggered RA process, the RA configuration for the sensing service can be configured, pre-configured, or predefined. Terminal device 110 can send an RA request for the sensing service based on the RA configuration used for the sensing service.

[0092] In some implementations, the RA configuration for sensing services may include at least one RA preamble for sensing services. In such implementations, the at least one RA preamble for sensing services may include at least one of the following: a first RA preamble for initiating a four-step RA process triggered by the sensing service, or a second RA preamble for initiating a two-step RA process triggered by the sensing service. When terminal device 110 initiates an RA process triggered by a sensing request, terminal device 110 uses one of the at least one RA preambles for sensing services to identify that the RA is for sensing. This will refer to... Figure 8 Describe it.

[0093] Figure 8 Signaling diagrams illustrating example process 800 for ISAC according to some embodiments of this disclosure are shown. Process 800 can be considered as example implementations of process 700 or process 300. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe process 800. Process 800 may involve Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0094] Typically, in process 800, terminal device 110 uses a two-step CBRA to initiate an RRC connection to network device 130. The first type of information related to the sensing service includes sensing requests from terminal device 110.

[0095] like Figure 8 As shown, in the MSGA, the terminal device 110 sends the RA preamble and sensing request 820 for sensing service 810 in the PUSCH resource assigned to the MSGA.

[0096] Network device 130 detects the RA preamble and sensing request 820 for sensing service 810 in MSGA, and further sends MSGB (i.e., contention resolution message) to terminal device 110.

[0097] Alternatively or in addition, in some embodiments, the RA configuration for sensing services may include at least one RA preamble for requesting sensing configuration information. This will refer to Figure 9 Describe it.

[0098] Figure 9 A signaling diagram illustrating an example process 900 for ISAC according to some embodiments of this disclosure is shown. Process 900 can be considered as an example specific implementation of process 700 or process 500. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe process 900. Process 900 may involve Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0099] Typically, in process 900, a dedicated RA preamble is configured for requesting sensing configuration information. For simplicity, the request for sensing configuration information is also referred to as a sensing configuration information request. When terminal device 110 attempts to initiate a sensing service, terminal device 110 may need to obtain sensing configuration information from network device 130. Then, terminal device 110 uses the dedicated preamble for the sensing configuration information request to trigger a two-step CFRA process.

[0100] like Figure 9 As shown, in MAG0, network device 130 requests a 905 dedicated RA preamble for sensing configuration information.

[0101] Terminal device 110 sends an RA request (i.e., MSG1) to network device 130 on PRACH, including a dedicated RA preamble for sensing configuration information request.

[0102] Network device 130 detects a dedicated preamble for sensing configuration information requests and sends a 920 acknowledgment to terminal device 110 in RAR (i.e., MSG2).

[0103] Alternatively or in addition, in some embodiments, the RA configuration for sensing services may include a dedicated PRACH resource set for sensing services. The dedicated PRACH resource set for sensing services includes at least one PRACH resource for sensing services.

[0104] In some implementations, at least one PRACH resource used for sensing services may be a communication resource. In other words, at least one PRACH resource used for sensing services may be distinguishable from PRACH resources used for communication purposes.

[0105] Alternatively, in some implementations, at least one PRACH resource used for sensing services may belong to a sensing resource set.

[0106] In some implementations, when terminal device 110 initiates a RA procedure triggered by a sensing request, terminal device 110 uses PRACH resources in a dedicated PRACH resource set used for sensing services to send an RA preamble to identify that the RA procedure is for sensing. Network device 130 then detects the RA preamble on the PRACH resources used for sensing services. Network device 130 then identifies that the RA procedure is for sensing and determines the RAR accordingly.

[0107] Alternatively or in addition, in some embodiments, the RA configuration for sensing services may include a dedicated set of PRACH resources for sensing configuration information. The dedicated set of PRACH resources for sensing configuration information includes at least one PRACH resource for sensing configuration information.

[0108] In some implementations, the dedicated PRACH resource set used for sensing configuration information can be configured or pre-configured. When terminal device 110 needs to obtain the sensing configuration information, terminal device 110 can trigger a four-step CFRA procedure and send MSG1 on the PRACH resource used for sensing configuration information. Network device 130 detects the RA preamble on the PRACH resource used for sensing configuration information and sends an acknowledgment in MSG2.

[0109] Alternatively or otherwise, in some implementations, the RA configuration for the sensing service may include a reference signal for determining the type of RA process triggered by the sensing service.

[0110] In some implementations, the reference signal used to determine the type of RA process triggered by the sensing service can be configured, pre-configured, or predefined. Terminal device 110 can select a 4-step RA or a 2-step RA to execute the RA process triggered by the sensing request based on measurements of the reference signal. For example, the reference signal can be a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a sensing signal transmitted by a network node (such as a gNB or TRP).

[0111] Alternatively or in addition, in some embodiments, the RA configuration for sensing services may include a threshold for the received power level of a reference signal. Based on measurements of the reference signal, terminal device 110 may determine whether to use a 2-step RA or a 4-step RA for sensing services. For example, a 2-step RA is used when the measurement of the received reference signal exceeds the threshold.

[0112] In some implementations, the threshold for the received power level of the reference signal can be configured, preconfigured, or predefined.

[0113] In some implementations, the received power level of the reference signal includes at least one of the following: reference signal received power (RSRP), reference signal received quality (RSRQ), and received signal strength indication (RSSI).

[0114] Consider an example of a reference signal used to determine the type of a sense-triggered RA process. In this example, the reference signal includes an SSB, and a dedicated threshold for RSRP used to determine the type of sense-triggered RA process is pre-configured.

[0115] For example, this threshold can be achieved through parameters. msgA-RSRP-Threshold-Sensing This is used as an indication. Based on this configuration, terminal device 110 measures the RSRP of the SSB. If the RSRP exceeds a threshold, terminal device 110 determines to use a two-step RA process for the sensing request.

[0116] Alternatively, this threshold can be determined by parameters. rsrp-ThresholdSSB-Sensing This is used as an indication. Based on this configuration, terminal device 110 measures the RSRP of the SSB. If the RSRP exceeds a threshold, terminal device 110 determines to switch from a 2-step RA process to a 4-step RA process.

[0117] Alternatively or otherwise, in some implementations, the RA configuration for the sensing service may include a PUSCH resource for initiating a two-step CFRA process triggered by the sensing service.

[0118] In some implementations, during a sense-triggered RA process, a dedicated medium access control (MAC) protocol data unit (PDU) can be defined according to the sensed requirements. In such implementations, terminal device 110 can receive response information to the RA request by receiving a MAC PDU that includes at least one MAC sub-PDU. Each of the at least one MAC sub-PDU includes at least one of the following: a MAC sub-header and a MAC Service Data Unit (SDU). Such implementations support the exchange of sensed-related information between terminal device 110 and network device 130 via the RA process.

[0119] In some implementations, the at least one MAC sub-PDU may include a first MAC sub-PDU. The first MAC sub-PDU may include a first MAC sub-header containing only a random access preamble identity (RAPID), which indicates confirmation of a sensing configuration information request. The RAPID is associated with the RA preamble of the sensing service. This will refer to... Figure 10A and Figure 10B Describe it.

[0120] Figure 10A A signaling diagram illustrating an example procedure 1000 for ISAC according to some embodiments of this disclosure is shown. Procedure 1000 can be considered as an example specific implementation of procedure 700. For discussion purposes, reference will be made to... Figure 1A or Figure 1B Let's describe process 1000. Process 1000 may involve... Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0121] like Figure 10A As shown, in MAG0, network device 130 requests a dedicated RA preamble (1005) for sensing configuration information. The sensing configuration information can be a System Information Block (SIB) or a System Information (SI) message. The sensing configuration information may not be periodically broadcast by network device 130. Then, terminal device 110 needs to send a request to obtain the SIB or SI used for sensing.

[0122] Terminal device 110 sends an RA request (i.e., MSG1) to network device 130 on PRACH, including a dedicated RA preamble for requesting sensing configuration information. The dedicated RA preamble for requesting sensing configuration information indicates a request to sense configuration information.

[0123] Network device 130 detects a RA request with a dedicated preamble and sends a 1020 RAR (i.e., MGS2) to terminal device 110. The RAR includes a MAC PDU, which includes a first MAC sub-PDU. The first MAC sub-PDU includes a first MAC sub-header 1040 containing only a RAPID, which indicates acknowledgment of the sensing configuration information request. (See later...) Figure 10B Describe the details of the first MAC subheader 1040.

[0124] After the RA process is successful, network device 130 also broadcasts 1030 sensing configuration information on the physical downlink shared channel (PDSCH).

[0125] Figure 10B Examples of MAC subheaders according to some embodiments of this disclosure are shown. For example... Figure 10B As shown, the first MAC subheader 1040 may include an extension field (represented by E), a type field (represented by T), and a RAPID.

[0126] The extended field is a flag indicating whether the MAC sub-PDU including the MAC sub-header is the last MAC sub-PDU in the MAC PDU.

[0127] The type field is a flag indicating whether the MAC subheader contains a RAPID or a backoff indicator (BI).

[0128] RAPID indicates confirmation of a sensing configuration information request. RAPID is associated with a dedicated RA preamble used for sensing configuration information requests. For example, RAPID can be derived from the dedicated preamble used for sensing configuration information requests.

[0129] In some implementations, the at least one MAC sub-PDU may include a second MAC sub-PDU. The second MAC sub-PDU may include a second MAC sub-header with RAPID and a second MAC service data unit (SDU) including sensing configuration information. This will refer to... Figure 11 , Figure 12A , Figure 12B , Figure 12C and Figure 12D Describe it.

[0130] Figure 11Examples of MAC PDUs according to some example embodiments of this disclosure are illustrated. Figure 11 In the example, the dedicated PRACH resource set used for sensing configuration information can be configured or pre-configured. When terminal device 110 needs to obtain the sensing configuration information, terminal device 110 can trigger a 4-step CFRA procedure and send an RA preamble on the PRACH resource set used for sensing configuration information. Network device 130 detects the RA preamble on the PRACH resource used for sensing configuration information and sends MSG2 to terminal device 110.

[0131] MSG2 includes MAC PDU 1100. MAC PDU 1100 includes one or more MAC sub-PDUs and optional padding. For example, as... Figure 11 As shown, MAC PDU 1100 may include MAC sub-PDU 1110, MAC sub-PDU 1120, etc. Each of the one or more MAC sub-PDUs in MAC PDU 1100 may be referred to as a second MAC sub-PDU.

[0132] MAC sub-PDU 1110 includes a MAC sub-header 1112 containing only a backoff indicator (BI). The BI field identifies the overload condition in the cell. The BI field is 4 bits in size.

[0133] MAC sub-PDU 1120 includes MAC sub-header 1122 and MAC SDU 1124.

[0134] The MAC subheader 1122 may include an extended field (represented by E), a type field (represented by T), and a RAPID.

[0135] The extended field is a flag indicating whether the MAC sub-PDU including the MAC sub-header is the last MAC sub-PDU in the MAC PDU.

[0136] The type field is a flag indicating whether the MAC subheader contains a RAPID or a BI.

[0137] The RAPID field identifies the RA preamble that was sent.

[0138] MAC SDU 1124 includes sensing configuration information (in Figure 11 (represented by "SenInfo" in the original text). For example, sensing configuration information may include at least one of the following: configuration for sensing resources, allocation of sensing modes, and configuration for sensing TRPs.

[0139] Alternatively, in Figure 11In the example, the RA preamble for the sensing configuration information request can be configured or pre-configured. When terminal device 110 needs to obtain sensing configuration information, terminal device 110 can trigger a two-step CFRA process and send an MSGA including the RA preamble for the sensing configuration information request. The RA preamble for the sensing configuration information request indicates a request for sensing configuration information. In such implementations, terminal device 110 can determine that the second MAC sub-PDU in the MSGB is associated with sensing configuration information based on the RA preamble for the sensing configuration information request.

[0140] Figure 12A Examples of MAC PDUs according to some embodiments of this disclosure are illustrated. Figure 12A In the example, when terminal device 110 needs to obtain sensing configuration information, terminal device 110 can trigger a two-step RA process. During the two-step RA process, terminal device 110 sends an MSGA to network device 130, which includes an RA preamble on the PRACH and a payload on the PUSCH. Then, network device 130 sends an MSGB based on the detected MSGA.

[0141] MSGB includes MAC PDU 1200. MAC PDU 1200 includes one or more MAC sub-PDUs and optional padding. For example, as... Figure 12A As shown, MAC PDU 1200 may include MAC sub-PDU 1210, MAC sub-PDU 1220, etc. Each of MAC sub-PDU 1210 and MAC sub-PDU 1220 may be referred to as a second MAC sub-PDU.

[0142] MAC sub-PDU 1210 includes MAC sub-header 1212 and MAC SDU 1214. MAC sub-PDU 1220 includes MAC sub-header 1222 and MAC SDU 1224.

[0143] Figure 12B Examples of MAC subheader 1212 and MAC subheader 1222 according to some embodiments of this disclosure are shown. Figure 12B As shown, each of the MAC subheader 1212 and MAC subheader 1222 may include an extended field (represented by E), a T1 field (represented by T1), and a RAPID.

[0144] The extended field is a flag indicating whether the MAC sub-PDU that includes the MAC sub-header is the last MAC sub-PDU in the MAC PDU (other than the MAC sub-PDU used for the MAC SDU).

[0145] The T1 field is a flag indicating whether the MAC subheader contains RAPID or T2.

[0146] The RAPID field identifies the transmitted RA preamble. The RAPID is derived from the RA preamble. The RAPID field is 6 bits in size.

[0147] Each of MAC SDU 1214 and MAC SDU 1224 includes a first indicator (denoted by F). The first indicator indicates whether the corresponding one of MAC SDU 1214 and MAC SDU 1224 is used for rollback RAR or for sensing configuration information. In some implementations, a reserved bit in a conventional MAC SDU may be used as the first indicator.

[0148] Figure 12C Examples of MAC SDU 1214 according to some embodiments of this disclosure are illustrated. For example... Figure 12B As shown, MAC SDU 1214 includes F field 1216. For example, setting F field 1216 to "0" indicates that MAC SDU 1214 is used for rollback RAR.

[0149] Figure 12D Examples of MAC SDU 1224 according to some embodiments of this disclosure are illustrated. For example... Figure 12B As shown, the MAC SDU 1224 includes an F field 1226. For example, setting the F field 1226 to "1" indicates that the MAC SDU 1224 is used to sense configuration information (in... Figure 12A (represented by "SenInfo" in the text). In this way, the terminal device 110 can determine the association between the MAC SDU 1224 in the MSGB and the sensing configuration information based on the F field 1226.

[0150] In some implementations, the sensing configuration information may include at least one of the following: configuration for sensing resources, allocation of sensing modes, and configuration for sensing TRPs.

[0151] In some implementations, if sensing configuration information is indicated, the size of the sensing configuration information is 55 bits.

[0152] Alternatively, in some embodiments, terminal device 110 may determine that the second MAC sub-PDU is associated with sensing configuration information based on a radio network temporary identifier (RNTI) associated with the PRACH resource used for sensing configuration information requests. In some embodiments, each PRACH resource is associated with a separate RNTI. For a dedicated PRACH resource used for sensing configuration information requests, the associated RNTI is used to identify the DCI, which indicates the PDSCH transmission of a MAC PDU containing sensing configuration information.

[0153] In some implementations, the at least one MAC sub-PDU may include a third MAC sub-PDU. The third MAC sub-PDU may include a third MAC sub-header with RAPID and a successful RAR for sensing services. This will refer to... Figure 13A , Figure 13B , Figure 13C and Figure 13D Describe it.

[0154] Figure 13A Examples of MAC PDUs according to some embodiments of this disclosure are illustrated. Figure 13A In the example, terminal device 110 can trigger a two-step RA procedure. During the two-step RA procedure, terminal device 110 sends an MSGA to network device 130. Then, network device 130 sends an MSGB based on the detected MSGA.

[0155] MSGB includes MAC PDU 1300. MAC PDU 1300 includes one or more MAC sub-PDUs and optional padding. For example, as... Figure 13A As shown, MAC PDU 1300 may include MAC sub-PDU 1310, MAC sub-PDU 1320, MAC sub-PDU 1330, etc. Each of MAC sub-PDU 1320 and MAC sub-PDU 1330 may be referred to as a third MAC sub-PDU.

[0156] MAC sub-PDU 1310 includes a MAC sub-header 1312 containing only the BI field. The BI field identifies the overload status in the cell. The BI field is 4 bits in size.

[0157] MAC sub-PDU 1320 includes MAC sub-header 1322 and MAC SDU 1324. MAC sub-PDU 1330 includes MAC sub-header 1332 and MAC SDU 1334.

[0158] Figure 13B Examples of MAC subheader 1312 according to some embodiments of this disclosure are shown. Figure 13B As shown, the MAC subheader 1312 may include an extended field (represented by E), a T1 field (represented by T1), a T2 field (represented by T2), a reserved bit (represented by R), and a BI field.

[0159] The extended field is a flag indicating whether the MAC sub-PDU that includes the MAC sub-header is the last MAC sub-PDU in the MAC PDU (other than the MAC sub-PDU used for the MAC SDU).

[0160] The T1 field is a flag indicating whether the MAC subheader contains RAPID or T2.

[0161] Reserved bits are set to 0.

[0162] The T2 field is a flag indicating whether the MAC subheader contains a BI or a MAC SDU indicator (represented by S).

[0163] The BI field identifies the overload status within the cell. The BI field is 4 bits in size.

[0164] Figure 13C Examples of MAC subheader 1322 and MAC subheader 1332 according to some embodiments of this disclosure are shown. Figure 13C As shown, each of the MAC subheader 1322 and MAC subheader 1332 may include an extended field (represented by E), a T1 field (represented by T1), a T2 field (represented by T2), a MAC SDU indicator (represented by S), and reserved bits (represented by R).

[0165] Furthermore, each of MAC subheaders 1322 and 1332 includes a second indicator 1340 (denoted by C). The second indicator 1340 indicates whether a successful RAR of the sensing service follows the corresponding one of MAC subheaders 1322 and 1332. In some embodiments, reserved bits in a conventional MAC SDU may be used as the second indicator 1340.

[0166] For example, the C field in MAC subheader 1322 can be set to "0" to indicate that the successful RAR for the sensing service does not follow MAC subheader 1322, while the C field in MAC subheader 1332 can be set to "1" to indicate that the successful RAR for the sensing service follows MAC subheader 1332. In this respect, MAC SDU 1334 is also referred to as the successful RAR 1334 for the sensing service.

[0167] Figure 13D Examples of some embodiments according to this disclosure are illustrated. Figure 13A Example of MAC SDU 1334. For example... Figure 13D As shown, MAC SDU 1334 (i.e., successful RAR of sensing service 1334) includes UE contention resolution identifier, sensing resource allocation, and cell radio network temporary identifier (C-RNTI).

[0168] In some implementations, the sensing resource allocation indicator is the sensing resource assigned by the terminal device 110. For example, the size of the sensing resource allocation is 23 bits.

[0169] As described above, in some embodiments, the first type of information related to the sensing service may include at least one of the following: a sensing request from the terminal device 110, or a sensing result report.

[0170] In some implementations, terminal device 110 may trigger a 4-step RA process. During the 4-step RA process, after sending MSG1 including the RA preamble on PRACH, terminal device 110 may receive MSG2 assigning PUSCH resources for MSG3. Then, terminal device 110 may send a sensing result report and / or sensing request to network device 130 on the assigned PUSCH resources in MSG3. Subsequently, network device 130 may send MSG4 to terminal device 110 to acknowledge successful receipt of the sensing result report and / or sensing request carried in MSG3.

[0171] Alternatively, in some implementations, terminal device 110 may trigger a two-step RA procedure. During the two-step RA procedure, PUSCH resources are assigned for MSGA transmission. Terminal device 110 may then send a sensing result report and / or sensing request to network device 130 in the MSGA on the assigned PUSCH resources. Subsequently, network device 130 may send an MSGB to terminal device 110 to acknowledge successful receipt of the sensing result report and / or sensing request carried in the MSGA.

[0172] In some implementations, the sensing request of terminal device 110 may include at least one of the following: Sensing service requirements At least one identifier (ID) of the sensing target. Sensing resource requests, The sensing capability of terminal device 110 Location information of terminal device 110, or Speed ​​information of terminal device 110.

[0173] In some implementations, the sensing result report may include at least one of the following: At least one ID of the sensing target, At least one sensing signal ID, At least one ID of the sensing TRP, The measurement result of at least one sensing signal, At least one location information of the sensing target, At least one velocity information of the sensing target, Point cloud data of at least one sensing target, A list of detected sensing signals, each identified by the ID of the sensing TRP, or The sensing result for each detected sensing signal.

[0174] In some implementations, the sensing capability of the terminal device 110 may include at least one of the following: The terminal device 110 supports at least one sensing mode. The types of sensing signals supported by terminal device 110, or Types of sensing result reports supported by terminal device 110.

[0175] In some implementations, the sensing mode can be defined based on the transmitting (Tx) / receiving (Rx) node of the sensed signal. For example, the sensing mode may include at least one of the following: Sensing mode 1: The sensing signal is sent by a network node such as a gNB (e.g., network device 130) and received / measured by the network node itself; Sensing mode 2: The sensing signal is sent by a network node (such as network device 130) and received / measured by a UE (such as terminal device 110 or 120); Sensing Mode 3: The sensing signal is sent by network node A (such as network device 130) and by network node B (such as...). Figure 1A or Figure 1B The network device shown in the image receives / measures; Sensing mode 4: The sensing signal is sent by the UE (such as terminal device 110 or 120) and received / measured by the UE itself; Sensing mode 5: The sensing signal is sent by the UE (such as terminal device 110 or 120) and received / measured by the network node (such as network device 130); or Sensing mode 6: The sensing signal is sent by UE A (such as terminal device 110) and received / measured by UE B (such as terminal device 120).

[0176] In some implementations, the terminal device 110 may support at least one of the following sensing modes: sensing mode 2, sensing mode 4, sensing mode 5, and sensing mode 6.

[0177] In some implementations, the types of sensing signals supported by the terminal device 110 may include at least one of the following: a sensing reference signal (RS), a positioning reference signal (PRS), a sounding reference signal (SRS), or a channel state information reference signal (CSI-RS).

[0178] In some implementations, the types of sensing result reports supported by terminal device 110 include at least one of the following: location, velocity, and point cloud.

[0179] In some implementations, if terminal device 110 sends a sensing request in MSG3 or MSGA, network device 130 can determine response information to the sensing request based on the sensing request. The response information to the sensing request may include information indicating at least one of the following: a sensing mode, or at least one sensing resource. Network device 130 can then send the response information to the sensing request to terminal device 110 in MSG4 or MSGB. This will refer to... Figure 14 Describe it.

[0180] Figure 14 A signaling diagram illustrating an example procedure 1400 for ISAC according to some embodiments of this disclosure is shown. Procedure 1400 can be considered as an example specific implementation of procedure 700. For discussion purposes, reference will be made to... Figure 1A or Figure 1B Let's describe process 1400. Process 1400 may involve... Figure 1A or Figure 1B Terminal device 110 and network device 130.

[0181] Typically, in process 1400, terminal device 110 initiates a 4-step CBRA process. The first type of information related to the sensing service includes a sensing request from terminal device 110. The response information to the sensing request includes information indicating at least one of the following: a sensing mode assigned to terminal device 110, or at least one sensing resource.

[0182] like Figure 14 As shown, terminal device 110 sends MSG1, including the RA preamble, on PRACH at 1410. Then, terminal device 110 receives MSG2, which assigns PUSCH resources to MSG3, from network device 130 at 1420.

[0183] Then, terminal device 110 sends a 1430 sensing request as MSG3 to network device 130 on the assigned PUSCH resource.

[0184] The sensing request of terminal device 110 may include at least one of the following: Sensing service requirements Sensing resource requests, The sensing capability of terminal device 110, or Location information of terminal device 110.

[0185] For example, sensing service requirements may include ambient environment detection.

[0186] For example, the sensing capability of terminal device 110 may include: at least one sensing mode supported by terminal device 110, and the type of sensing signal supported by terminal device 110.

[0187] For example, the terminal device 110 may support at least one of the following sensing modes: sensing mode 4 and sensing mode 5. In sensing mode 4, the sensing signal is sent by the terminal device 110 and received / measured by the terminal device 110 itself. In sensing mode 5, the sensing signal is sent by the terminal device 110 and received / measured by the network device 130.

[0188] For example, the types of sensing signals supported by terminal device 110 may include sensing RS.

[0189] Based on the sensing request, network device 130 determines response information to the sensing request. The response information to the sensing request includes information indicating the sensing mode and at least one sensing resource.

[0190] For example, the response information to the sensing request includes information indicating that sensing mode 4 should be assigned to terminal device 110, that is, terminal device 110 should use sensing mode 4 for sensing services.

[0191] For example, the response information to the sensing request may also include at least one sensing resource. The at least one sensing resource may include at least one of the following: a first sensing resource assigned to the terminal device 110, or a second sensing resource used by the sensing target.

[0192] Subsequently, network device 130 sends 1440 response information to the sensing request in the PDSCH associated with MSG4.

[0193] Then, the terminal device 110 transmits a sensing RS on at least one sensing resource assigned to the terminal device 110 and measures the echo signal to obtain the sensing result.

[0194] Figure 15 Example 1500 illustrates the determination of response information to a sensing request according to some embodiments of this disclosure. Typically, in example 1500, terminal device 110 initiates a two-step RA process.

[0195] like Figure 15 As shown, terminal device 110 sends an MSGA including the RA preamble on PRACH and sends a sensing request on the assigned PUSCH resource.

[0196] The sensing request of terminal device 110 may include at least one of the following: The ID of the target being sensed (e.g., the ID of terminal device 120). The sensing capability of terminal device 110, or Location information of terminal device 110.

[0197] For example, the sensing capability of terminal device 110 may include at least one sensing mode supported by terminal device 110.

[0198] For example, the terminal device 110 may support at least one of the following sensing modes: sensing mode 4 and sensing mode 6. In sensing mode 4, the sensing signal is sent by the terminal device 110 and received / measured by the terminal device 110 itself. In sensing mode 6, the sensing signal is sent by the terminal device 120 and received / measured by the terminal device 110.

[0199] Based on the sensing request, network device 130 determines response information to the sensing request. The response information to the sensing request includes information indicating the sensing mode and at least one sensing resource.

[0200] For example, the response information to a sensing request includes information indicating the sensing mode 6 assigned to the terminal device 110.

[0201] For example, the response information to the sensing request may also include at least one sensing resource. The at least one sensing resource may include a second sensing resource used by the sensing target (i.e., terminal device 120).

[0202] Subsequently, network device 130 sends a response to the sensing request in the PDSCH associated with MSGB.

[0203] Then, terminal device 110 detects and measures the sensing signal sent by the sensing target (i.e., terminal device 120) and determines the sensing result, i.e. the relevant position and relevant velocity between terminal device 110 and terminal device 120.

[0204] In some implementations, if terminal device 110 sends a sensing result report in MSG3 or MSGA, network device 130 can determine response information to the sensing result report based on the report. The response information may include information indicating at least one of the following: the ID of at least one sensing TRP, or at least one sensing resource assigned to terminal device 110. Network device 130 can then send the response information to terminal device 110 in MSG4 or MSGB. This will refer to... Figure 16 and Figure 17 To describe.

[0205] Figure 16 Examples of ISAC systems 1600 according to some example implementations of this disclosure are illustrated. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe Figure 16 .like Figure 16 As shown, the ISAC system 1600 includes network device 130, terminal device 110, TRP 1610, TRP 1620, and TRP 1630. For example, Figure 1A or Figure 1B The terminal device 120 can act as one of TRP1610, 1620 and 1630.

[0206] Figure 17 A signaling diagram illustrating an example procedure 1700 for ISAC according to some embodiments of this disclosure is shown. Procedure 1700 can be considered as an example specific implementation of procedure 700. For discussion purposes, reference will be made to... Figure 16 Let's describe process 1700. Process 1700 may involve... Figure 16 The terminal device 110, network device 130, and TRP 1630 are included.

[0207] like Figure 17 As shown, terminal device 110 sends a 1710 MSGA. The MSGA includes the RA preamble on the PRACH, as well as the sensing request from terminal device 110 and the sensing result report on the PUSCH resource assigned to the MSGA.

[0208] The sensing request of terminal device 110 includes a sensing service request and the location information of terminal device 110.

[0209] The sensing results report includes a list of detected sensing signals. Each detected sensing signal is identified by the ID of the sensing TRP. The sensing results report also includes the sensing result for each detected sensing signal.

[0210] Based on the sensing results report, network device 130 determines at least one suitable sensing TRP for terminal device 110. For example, network device 130 determines TRP 1630 as a suitable sensing TRP for terminal device 110.

[0211] Based on the sensing results report, network device 130 also identifies at least one sensing resource assigned to terminal device 110 (i.e., the sensing resource allocation of terminal device 110).

[0212] Subsequently, network device 130 sends 1730 MSGB to terminal device 110. MSGB includes the ID of TRP 1630 and the sensing resource allocation of terminal device 110.

[0213] Then, terminal device 110 sends a 1750 sensing signal on the assigned sensing resources.

[0214] Furthermore, network device 130 sends a 1740 signal to TRP 1630 regarding the allocation of sensing resources to terminal device 110. Therefore, TRP 1630 detects the sensing signal from terminal device 110 based on the sensing resource allocation and determines the 1760 sensing result. Subsequently, TRP 1630 sends a 1770 sensing result report to network device 130.

[0215] Figure 18 A flowchart illustrating example method 1800 according to some embodiments of this disclosure is shown. In some embodiments, method 1800 can be implemented on a terminal device such as... Figure 1A or Figure 1B This is implemented at terminal device 110 or terminal device 120 as shown. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe process 1800.

[0216] At box 1810, terminal device 110 sends an RA request for sensing services. The RA request includes at least one of the following: an RA preamble or information of a first type related to sensing services.

[0217] At box 1820, terminal device 110 receives response information to the RA request.

[0218] In some implementations, sending a RA request for sensing services includes sending the RA request based on the RA configuration used for sensing services.

[0219] In some implementations, the RA configuration for the sensing service includes at least one of the following: at least one RA preamble for the sensing service, at least one RA preamble for a sensing configuration information request, at least one physical random access channel (PRACH) resource for the sensing service, at least one PRACH resource for sensing configuration information, a reference signal for determining the type of RA procedure triggered by the sensing service, a threshold for the received power level of the reference signal, or a physical uplink shared channel (PUSCH) resource for initiating a two-step contention-free random access (CFRA) procedure triggered by the sensing service.

[0220] In some implementations, at least one RA preamble for the sensing service includes at least one of the following: a first RA preamble for initiating a 4-step CFRA process triggered by the sensing service, or a second RA preamble for initiating a 2-step CFRA process triggered by the sensing service.

[0221] In some implementations, the received power level of the reference signal includes at least one of the following: the reference signal received power (RSRP) of the reference signal, the reference signal received quality (RSRQ) of the reference signal, and the received signal strength indication (RSSI) of the reference signal.

[0222] In some implementations, receiving a response to a RA request includes receiving a Media Access Control (MAC) Protocol Data Unit (PDU), which includes at least one MAC sub-PDU. In such implementations, each of the at least one MAC sub-PDU includes at least one of the following: a MAC sub-header and a MAC Service Data Unit (SDU).

[0223] In some implementations, the at least one MAC sub-PDU includes a first MAC sub-PDU, which includes a first MAC sub-header having only a random access preamble identifier (RAPID) indicating an acknowledgment of a sensing configuration information request, the RAPID being associated with an RA preamble used for the sensing configuration information request.

[0224] In some implementations, the at least one MAC sub-PDU includes a second MAC sub-PDU, which includes: a second MAC sub-header having a random access preamble identifier (RAPID), and a second MAC service data unit (SDU) including sensing configuration information.

[0225] In some implementations, the sensing configuration information includes at least one of the following: configuration for sensing resources, allocation of sensing modes, and configuration for sensing transmit / receive points (TRPs).

[0226] In some implementations, method 1800 further includes determining that the second MAC subPDU is associated with sensing configuration information based on at least one of: an RA preamble for sensing configuration information requests; a radio network temporary identifier (RNTI) associated with a physical random access channel (PRACH) resource for sensing configuration information requests; or a first indicator included in the second MAC SDU for indicating whether the second MAC SDU is for fallback random access response (RAR) or sensing configuration information.

[0227] In some implementations, the at least one MAC sub-PDU includes a third MAC sub-PDU, which includes: a third MAC sub-header with a random access preamble identifier (RAPID) and a successful random access response (RAR) for sensing services.

[0228] In some implementations, the third MAC sub-header includes a second indicator that indicates whether a successful RAR of the sensing service follows the third MAC sub-header.

[0229] In some implementations, the first type of information related to the sensing service includes at least one of the following: a sensing request from a terminal device; or a sensing result report.

[0230] In some implementations, the sensing request of the terminal device includes at least one of the following: a sensing service request, an identifier (ID) of at least one sensing target, a sensing resource request, the sensing capability of the terminal device, the location information of the terminal device, or the speed information of the terminal device.

[0231] In some implementations, the sensing result report includes at least one of the following: an identifier (ID) of at least one sensing target, an ID of at least one sensing signal, an ID of at least one sensing transmit / receive point (TRP), a measurement result of at least one sensing signal, location information of at least one sensing target, velocity information of at least one sensing target, point cloud data of at least one sensing target, a list of detected sensing signals, each detected sensing signal being identified by the ID of the sensing TRP, or a sensing result for each detected sensing signal.

[0232] In some implementations, the sensing capabilities of the terminal device include at least one of the following: at least one sensing mode supported by the terminal device; a type of sensing signal supported by the terminal device; and a type of sensing result report supported by the terminal device.

[0233] In some implementations, the response information to a RA request includes response information to a sensing request. In such implementations, the response information to a sensing request includes information indicating at least one of the following: a sensing mode, or at least one sensing resource.

[0234] In some implementations, the at least one sensing resource includes at least one of the following: a first sensing resource assigned to the terminal device, or a second sensing resource used by the sensing target.

[0235] In some implementations, the response information to a RA request includes response information to a sensing result report. In such implementations, the response information to a sensing result report includes information indicating at least one of the following: an identifier of at least one sensing TRP, or at least one sensing resource assigned to the terminal device.

[0236] Figure 19 A flowchart illustrating example method 1900 according to some embodiments of this disclosure is shown. In some embodiments, method 1900 can be implemented in a network device (such as...) Figure 1A or Figure 1B This is implemented at network device 130 shown. For discussion purposes, reference will be made to... Figure 1A or Figure 1B To describe the process 1900.

[0237] At box 1910, network device 130 receives a RA request for sensing services. The RA request includes at least one of the following: an RA preamble or information of a first type related to sensing services.

[0238] At box 1920, network device 130 determines the response information to the RA request.

[0239] At box 1930, network device 130 sends a response to the RA request.

[0240] In some implementations, receiving RA requests includes receiving RA requests based on the RA configuration used for sensing services.

[0241] In some implementations, the RA configuration for the sensing service includes at least one of the following: at least one RA preamble for the sensing service, at least one RA preamble for a sensing configuration information request, at least one physical random access channel (PRACH) resource for the sensing service, at least one PRACH resource for sensing configuration information, a reference signal for determining the type of RA procedure triggered by the sensing service, a threshold for the received power level of the reference signal, or a physical uplink shared channel (PUSCH) resource for initiating a two-step contention-free random access (CFRA) procedure triggered by the sensing service.

[0242] In some implementations, at least one RA preamble for the sensing service includes at least one of the following: a first RA preamble for initiating a 4-step CFRA process triggered by the sensing service, or a second RA preamble for initiating a 2-step CFRA process triggered by the sensing service.

[0243] In some implementations, the received power level of the reference signal includes at least one of the following: the reference signal received power (RSRP) of the reference signal, the reference signal received quality (RSRQ) of the reference signal, and the received signal strength indication (RSSI) of the reference signal.

[0244] In some implementations, the network device sends a response to a RA request by sending a Media Access Control (MAC) Protocol Data Unit (PDU), which includes at least one MAC sub-PDU. In such implementations, each of the at least one MAC sub-PDU includes at least one of the following: a MAC sub-header and a MAC Service Data Unit (SDU).

[0245] In some implementations, the at least one MAC sub-PDU includes a first MAC sub-PDU, which includes a first MAC sub-header having only a Random Access Preamble Identifier (RAPID) indicating an acknowledgment of a sensing configuration information request, the RAPID being associated with an RA preamble used for sensing services.

[0246] In some implementations, the at least one MAC sub-PDU includes a second MAC sub-PDU, which includes: a second MAC sub-header having a random access preamble identifier (RAPID), and a second MAC service data unit (SDU) including sensing configuration information.

[0247] In some implementations, the sensing configuration information includes at least one of the following: configuration for sensing resources, allocation of sensing modes, and configuration for sensing transmit / receive points (TRPs).

[0248] In some implementations, the second MAC sub-PDU is associated with sensing configuration information based on at least one of the following: an RA preamble for sensing configuration information requests; a radio network temporary identifier (RNTI) associated with a physical random access channel (PRACH) resource for sensing configuration information requests; or a first indicator included in the second MAC SDU for indicating whether the second MAC SDU is for fallback random access response (RAR) or sensing configuration information.

[0249] In some implementations, the at least one MAC sub-PDU includes a third MAC sub-PDU, which includes: a third MAC sub-header with a random access preamble identifier (RAPID) and a successful random access response (RAR) for sensing services.

[0250] In some implementations, the third MAC sub-header includes a second indicator that indicates whether a successful RAR of the sensing service follows the third MAC sub-header.

[0251] In some implementations, the first type of information related to the sensing service includes at least one of the following: a sensing request from a terminal device; or a sensing result report.

[0252] In some implementations, the sensing request of the terminal device includes at least one of the following: a sensing service request, an identifier (ID) of at least one sensing target, a sensing resource request, the sensing capability of the terminal device, the location information of the terminal device, or the speed information of the terminal device.

[0253] In some implementations, the sensing result report includes at least one of the following: an identifier (ID) of at least one sensing target, an ID of at least one sensing signal, an ID of at least one sensing transmit / receive point (TRP), a measurement result of at least one sensing signal, location information of at least one sensing target, velocity information of at least one sensing target, point cloud data of at least one sensing target, a list of detected sensing signals, each detected sensing signal being identified by the ID of the sensing TRP, or a sensing result for each detected sensing signal.

[0254] In some implementations, the sensing capabilities of the terminal device include at least one of the following: at least one sensing mode supported by the terminal device; a type of sensing signal supported by the terminal device; and a type of sensing result report supported by the terminal device.

[0255] In some implementations, the response information to a RA request includes response information to a sensing request. In such implementations, the response information to a sensing request includes information indicating at least one of the following: a sensing mode, or at least one sensing resource.

[0256] In some implementations, the at least one sensing resource includes at least one of the following: a first sensing resource assigned to the terminal device, or a second sensing resource used by the sensing target.

[0257] In some implementations, the response information to a RA request includes response information to a sensing result report. In such implementations, the response information to a sensing result report includes information indicating at least one of the following: an identifier of at least one sensing TRP, or at least one sensing resource assigned to the terminal device.

[0258] Figure 20 This is a simplified block diagram of a device 2000 suitable for implementing embodiments of the present disclosure. Device 2000 can be considered as follows: Figure 1A or Figure 1B Another example implementation of the terminal device 110, terminal device 120, or control node 130 shown. Therefore, device 2000 may be implemented as terminal device 110, terminal device 120, or control node 130, or as at least a portion of these devices.

[0259] As shown in the figure, device 2000 includes a processor 2010, a memory 2020 coupled to the processor 2010, a suitable transceiver 2040 coupled to the processor 2010, and a communication interface coupled to the transceiver 2040. The memory 2010 stores at least a portion of a program 2030. Depending on the requirements, the transceiver 2040 can be used for bidirectional or unidirectional communication. The transceiver 2040 may include at least one of a transmitter 2042 and a receiver 2044. The transmitter 2042 and receiver 2044 may be functional modules or physical entities. The transceiver 2040 has at least one antenna to facilitate communication; however, in practice, the access node mentioned in this application may have several antennas. The communication interface can represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and relay nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal equipment.

[0260] The components included in the apparatus and / or device disclosed herein can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In one embodiment, one or more units may be implemented using software and / or firmware (e.g., machine-executable instructions stored on a storage medium). As a supplement to or alternative to the machine-executable instructions, some or all of the units in the apparatus and / or device may be implemented at least partially by one or more hardware logic components. For example, but not limited to, exemplary types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), etc.

Claims

1. A terminal device, the terminal device comprising: Processor, the processor being configured to cause the terminal device to: Send a random access (RA) request to the sensing service, the RA request including an RA preamble and a first type of information related to the sensing service; and Receive response information for the RA request.

2. The terminal device of claim 1, wherein the terminal device sends the RA request based on the RA configuration for the sensing service.

3. The terminal device of claim 2, wherein the RA configuration for the sensing service includes at least one of the following: At least one RA preamble is used for the sensing service. At least one RA preamble is used to sense configuration information requests. At least one physical random access channel (PRACH) resource is used for the sensing service. At least one PRACH resource for the sensing configuration information. Reference signals used to determine the type of RA process triggered by the sensing service. The threshold of the received power level of the reference signal, or Physical uplink shared channel (PUSCH) resources are used to initiate a two-step contention-free random access (CFRA) process triggered by the sensing service.

4. The terminal device according to claim 1, wherein the terminal device receives the response information to the RA request in the following manner: The receiver receives a medium access control (MAC) protocol data unit (PDU), the MAC PDU including at least one MAC sub-PDU, each of the at least one MAC sub-PDU including at least one of the following: a MAC sub-header and a MAC service data unit (SDU).

5. The terminal device according to claim 4, wherein the at least one MAC sub-PDU includes a first MAC sub-PDU, and the first MAC sub-PDU includes: The first MAC subheader contains only a random access preamble identity (RAPID), which indicates confirmation of a sense configuration information request and is associated with the RA preamble used for the sense configuration information request.

6. The terminal device according to claim 4, wherein the at least one MAC sub-PDU includes a second MAC sub-PDU, and the second MAC sub-PDU includes: The second MAC subheader has a random access preamble identifier (RAPID) and a second MAC service data unit (SDU) that includes the sensing configuration information.

7. The terminal device of claim 1, wherein the first type of information related to the sensing service includes at least one of the following: The sensing request from the terminal device; or Sensing results report.

8. The terminal device of claim 7, wherein the sensing request of the terminal device includes at least one of the following: Sensing service requirements At least one identifier (ID) of the sensing target. Sensing resource requests, The sensing capability of the terminal device, The location information of the terminal device, or The speed information of the terminal device.

9. The terminal device according to claim 7, wherein the sensing result report includes at least one of the following: At least one identifier (ID) of the sensing target. At least one sensing signal ID, At least one sensor transmit-reception point (TRP) ID, The measurement result of the at least one sensing signal, The location information of the at least one sensing target, The velocity information of the at least one sensing target, Point cloud data of the at least one sensed target, A list of detected sensing signals, each of which is identified by the ID of the sensing TRP, or The sensing result of each detected sensing signal.

10. The terminal device of claim 7, wherein the response information to the RA request includes response information to the sensing request, wherein the response information to the sensing request includes information indicating at least one of the following: Sensing mode, or At least one sensing resource.

11. A network device, the network device comprising: Processor, the processor being configured to cause the network device to: Receive a random access (RA) request for a sensing service, the RA request including an RA preamble and a first type of information related to the sensing service; Determine the response information to the RA request; and Send the response information to the RA request.

12. The network device of claim 11, wherein the network device receives the RA request based on the RA configuration for the sensing service.

13. The network device of claim 12, wherein the RA configuration for the sensing service comprises at least one of the following: At least one RA preamble is used for the sensing service. At least one RA preamble is used to sense configuration information requests. At least one Physical Random Access Channel (PRACH) resource is used for the sensing service. At least one PRACH resource for the sensing configuration information. Reference signals used to determine the type of RA process triggered by the sensing service. The threshold of the received power level of the reference signal, or Physical uplink shared channel (PUSCH) resources used to initiate a two-step contention-free random access (CFRA) procedure triggered by the sensing service.

14. The network device of claim 11, wherein the network device sends the response information to the RA request in the following manner: Transmit a Media Access Control (MAC) Protocol Data Unit (PDU), the MAC PDU including at least one MAC subPDU, each of the at least one MAC subPDU including at least one of the following: a MAC subheader and a MAC Service Data Unit (SDU).

15. The network device of claim 14, wherein the at least one MAC sub-PDU includes a first MAC sub-PDU, and the first MAC sub-PDU includes: The first MAC subheader contains only a Random Access Preamble Identifier (RAPID), which indicates confirmation of a request for sensing configuration information and is associated with the RA preamble used for the sensing service.

16. The network device of claim 14, wherein the at least one MAC sub-PDU includes a second MAC sub-PDU, and the second MAC sub-PDU includes: The second MAC subheader has a random access preamble identifier (RAPID) and a second MAC service data unit (SDU) that includes the sensing configuration information.

17. The network device of claim 11, wherein the first type of information related to the sensing service includes at least one of the following: The sensing request from the terminal device; or Sensing results report.

18. The network device of claim 17, wherein the sensing request of the terminal device includes at least one of the following: Sensing service requirements At least one identifier (ID) of the sensing target. Sensing resource requests, The sensing capability of the terminal device, The location information of the terminal device, or The speed information of the terminal device.

19. The network device of claim 17, wherein the sensing result report includes at least one of the following: At least one identifier (ID) of the sensing target. At least one sensing signal ID, At least one Sensor Transmitter Point (TRP) ID, The measurement result of the at least one sensing signal, The location information of the at least one sensing target, The velocity information of the at least one sensing target, Point cloud data of the at least one sensed target, A list of detected sensing signals, each of which is identified by the ID of the sensing TRP, or The sensing result of each detected sensing signal.

20. The network device of claim 17, wherein the response information to the RA request includes response information to the sensing request, wherein the response information to the sensing request includes information indicating at least one of the following: Sensing mode, or At least one sensing resource.

Images