[go: up one dir, main page]

WO2025118197A1 - Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées - Google Patents

Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées Download PDF

Info

Publication number
WO2025118197A1
WO2025118197A1 PCT/CN2023/136879 CN2023136879W WO2025118197A1 WO 2025118197 A1 WO2025118197 A1 WO 2025118197A1 CN 2023136879 W CN2023136879 W CN 2023136879W WO 2025118197 A1 WO2025118197 A1 WO 2025118197A1
Authority
WO
WIPO (PCT)
Prior art keywords
sensing
terminal device
request
mac
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/136879
Other languages
English (en)
Inventor
Jin Yang
Gang Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Priority to PCT/CN2023/136879 priority Critical patent/WO2025118197A1/fr
Publication of WO2025118197A1 publication Critical patent/WO2025118197A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to device, method and computer readable medium for Integrated Sensing And Communication (ISAC) .
  • IIC Integrated Sensing And Communication
  • ISAC is considered as a promising topic for future wireless network extension.
  • 3GPP third generation partnership project
  • it may aim to build communication based sensing system.
  • RRC radio resource control
  • a random access procedure may be needed to start a sensing procedure.
  • example embodiments of the present disclosure provide a device, method and computer readable medium for ISAC.
  • a terminal device comprising a processor.
  • the processor is configured to cause the terminal device to: transmit a random access (RA) request for a sensing service, the RA request comprising an RA preamble and first type of information related to the sensing service; and receive responding information for the RA request.
  • RA random access
  • a network device comprising a processor.
  • the processor is configured to cause the network device to: receive an RA request for a sensing service, the RA request comprising an RA preamble and first type of information related to the sensing service; determine responding information for the RA request; and transmit the responding information for the RA request.
  • a method for ISAC comprises: transmitting an RA request for a sensing service, the RA request comprising an RA preamble and first type of information related to the sensing service; and receiving responding information for the RA request.
  • a method for ISAC comprises: receiving an RA request for a sensing service, the RA request comprising an RA preamble and first type of information related to the sensing service; determining responding information for the RA request; and transmitting the responding information for the RA request.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor of a device, cause the device to perform the method according to the third aspect or the fourth aspect.
  • FIGs. 1A and 1B illustrate an example communication network in which embodiments of the present disclosure can be implemented, respectively;
  • Fig. 2 illustrates a signaling chart illustrating a contention-based random access (CBRA) procedure with 4-step RA type in accordance with some embodiments of the present disclosure
  • Fig. 3 illustrates a signaling chart illustrating a CBRA procedure with 2-step RA type in accordance with some embodiments of the present disclosure
  • Fig. 4 illustrates a signaling chart illustrating a fallback procedure for a CBRA with 2-step RA type in accordance with some embodiments of the present disclosure
  • Fig. 5 illustrates a signaling chart illustrating a contention-free random access (CFRA) procedure with 4-step RA type in accordance with some embodiments of the present disclosure
  • Fig. 6 illustrates a signaling chart illustrating a CFRA procedure with 2-step RA type in accordance with some embodiments of the present disclosure
  • Figs. 7, 8, 9 and 10A illustrate a signaling chart illustrating an example process for ISAC in accordance with some embodiments of the present disclosure, respectively;
  • Fig. 10B illustrates an example of a MAC subheader in accordance with some embodiments of the present disclosure
  • Fig. 11 illustrates an example of a MAC PDU in accordance with some embodiments of the present disclosure
  • Fig. 12A illustrates an example of a MAC PDU in accordance with some embodiments of the present disclosure
  • Fig. 12B illustrates an example of a MAC subheader in accordance with some embodiments of the present disclosure
  • Figs. 12C and 12D illustrate an example of the MAC SDU in accordance with some embodiments of the present disclosure, respectively;
  • Fig. 13A illustrates an example of a MAC PDU in accordance with some embodiments of the present disclosure
  • Figs. 13B and 13C illustrate an example of a MAC subheader in accordance with some embodiments of the present disclosure, respectively;
  • Fig. 13D illustrates an example of the MAC SDU in Fig. 13A in accordance with some embodiments of the present disclosure
  • Fig. 14 illustrates a signaling chart illustrating an example process for ISAC in accordance with some embodiments of the present disclosure
  • Fig. 15 illustrates an example of determining the responding information for the sensing request in accordance with some embodiments of the present disclosure
  • Fig. 16 illustrates an example of an ISAC system in accordance with some embodiments of the present disclosure
  • Fig. 17 illustrates a signaling chart illustrating an example process for ISAC in accordance with some embodiments of the present disclosure
  • Fig. 18 illustrates a flowchart of an example method in accordance with some embodiments of the present disclosure
  • Fig. 19 illustrates a flowchart of an example method in accordance with some embodiments of the present disclosure.
  • Fig. 20 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eX
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the network device may have the function of network energy saving, Self-Organizing Networks (SON) /Minimization of Drive Tests (MDT) .
  • the terminal may have the function of power saving.
  • test equipment e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘some embodiments’ and ‘an embodiment’ are to be read as ‘at least some embodiments. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • Fig. 1A illustrates a schematic diagram of an example communication network 100A in which embodiments of the present disclosure can be implemented.
  • the communication network 100A may include a terminal device 110, a terminal device 120, a control node 130, an Access and Mobility management Function (AMF) 140 and a Sensing Function (SF) 150.
  • AMF Access and Mobility management Function
  • SF Sensing Function
  • the communication network 100A may include any suitable number of devices adapted for implementing embodiments of the present disclosure.
  • the terminal device 110 may comprise at least one of a sensing module and a communication module.
  • the terminal device 110 comprises a sensing module 110-1 and a communication module 110-2.
  • the sensing module 110-1 in the terminal device 110 may comprise at least one of a Uu sensing module 110-11 or a sidelink sensing module 110-12.
  • the Uu sensing module 110-11 may be configured to perform a Uu sensing function based on the network assistance or control, and the Uu sensing function may comprise at least one of a downlink sensing function and an uplink sensing function.
  • the sidelink sensing module 110-12 may be configured to perform a sidelink sensing function.
  • the terminal device 120 may comprise at least one of a sensing module and a communication module.
  • the terminal device 120 comprises a sensing module 120-1 and a communication module 120-2.
  • control node 130 may comprise at least one of a sensing module and a communication module.
  • the control node 130 comprises a sensing module 130-1 and a communication module 130-2.
  • control node 130 may be implemented as a network device (such as a gNB in NR) . In such embodiments, the control node 130 may be referred to as a network device 130.
  • control node 130 may be implemented as a Road Side Unit (RSU) .
  • RSU Road Side Unit
  • the control node 130 may be referred to as RSU 130.
  • control node 130 may be implemented as a sensing Transmission-Reception Point (TRP) .
  • TRP 130 Transmission-Reception Point 130.
  • the terminal device 120 may be implemented as a sensing TRP.
  • the terminal device 120 may be referred to as TRP 120.
  • the AMF 140 may be a node in a core network.
  • the AMF 140 may provide matching information about the control node 130 or the terminal device 110 according to sensing requirement.
  • the communications in the communication network 100A may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (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) and the like.
  • GSM Global System for Mobile Communications
  • LTE LTE
  • LTE-Evolution LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • the communications may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , the sixth generation (6G) communication protocols.
  • the communications in the communication network 100A may comprise ISAC.
  • the communication network with ISAC may structure sharing hardware architectures, channel characteristics and signal processing, and integrate types of sensing information, such as sensory data from the environment and radar based sensing information, and communication information to achieve higher resource efficiency and provide more intelligent and integrated network solutions.
  • the ISAC network can be applied to more extensive scenarios, including smart home, smart manufacturing, environmental monitoring, and so on.
  • control node 130 may comprise at least one of the following:
  • ⁇ a third interface between the control node 130 and the SF 150.
  • the terminal device 110 may comprise at least one of the following:
  • ⁇ a fifth interface between the terminal device 110 and the terminal device 120.
  • the first interface between the control node 130 and the terminal device 110 may be a Uu interface.
  • sidelink sensing related information may be exchanged on the Uu interface.
  • Uu sensing procedure may be performed between the control node 130 and the terminal device 110, and Uu sensing function related information may be exchanged, e.g., between the sensing module 130-1 of the control node 130 and the sensing module 110-1 of the terminal device 110.
  • the fifth interface between the terminal device 110 and the terminal device 120 may be a Unified Air Interface, such as PC5 interface.
  • a sidelink sensing procedure may be performed and sidelink sensing function related information may be exchanged on the PC5 interface, i.e., between the sensing module 110-1 the terminal device 110 and the sensing module 120-1 of the terminal device 120.
  • the SF 150 comprises no interface with the control node 130.
  • the SF 150 indirectly exchanges information with the control node 130 through the AMF 140.
  • the terminal device 110 comprises the fourth interface between the terminal device 110 and the AMF 140.
  • the AMF 140 may transmit the sensing related information about the terminal device 110 to the terminal device 110 via the fourth interface.
  • Fig. 1B illustrates a schematic diagram of another example communication network 100B in which embodiments of the present disclosure can be implemented.
  • the example communication network 100B is similar to the example communication network 100A.
  • the example communication network 100B is different from the example communication network 100A in that in the example communication network 100B, the control node 130 comprises the third interface between the control node 130 and the SF 150.
  • the SF 150 may exchange sensing related information with the sensing module 130-1 in the control node 130 via the third interface.
  • the terminal device 110 does not comprise the fourth interface between the terminal device 110 and the AMF 140.
  • the terminal device 110 may exchange information with the AMF 140 through the control node 130.
  • a sensing terminal device When a sensing service is required, a sensing terminal device may not be in radio resource control (RRC) connected status, and it may require relevant procedure to change a status of the terminal device in radio access network (RAN) for further operation.
  • RRC radio resource control
  • a random access procedure may be needed to start a sensing procedure.
  • RRC radio resource control
  • a terminal device may perform a sensing procedure without communication requirement. Thus, there may be no need to set up RRC connection in communication system.
  • a terminal device transmits an RA request for a sensing service.
  • the RA request comprises at least one of the following: an RA preamble or first type of information related to the sensing service.
  • the terminal device receives responding information for the RA request.
  • This solution provides mechanism to start a sensing procedure for a terminal device in RRC_IDLE or RRC_INACTIVE status.
  • the terminal device may reuse RA mechanism in communication system to set up connection with a control node, and then start sensing related procedure.
  • This solution needs less complexity to start sensing service in ISAC system for the terminal device in RRC_IDLE or RRC_INACTIVE status.
  • this solution may reduce latency for sensing service, and reduce overhead and power consumption for triggering sensing service.
  • Fig. 2 illustrates a signaling chart illustrating a contention-based random access (CBRA) procedure 200 with 4-step RA type in accordance with some embodiments of the present disclosure.
  • a CBRA procedure with 4-step RA type is also referred to as 4-step CBRA procedure.
  • the CBRA procedure 200 will be described with reference to Fig. 1A or 1B.
  • the CBRA procedure 200 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the terminal device 110 transmits 210, to the network device 130, an RA request comprising an RA preamble on physical random access channel (PRACH) .
  • PRACH physical random access channel
  • the RA request in an RA procedure with 4-step RA type is also referred to as a message 1 (MSG1) .
  • the terminal device 110 monitors for a random access response (RAR) from the network device 130 within a configured window.
  • RAR random access response
  • the random access response in an RA procedure with 4-step RA type is also referred to as a message 2 (MSG2) .
  • the terminal device 110 upon receiving 220 the random access response, the terminal device 110 performs 230 a scheduled transmission using uplink (UL) grant scheduled in the random access response and monitors contention resolution.
  • the scheduled transmission using UL grant scheduled in the MSG2 is also referred to as a message 3 (MSG3) .
  • the MSG3 comprises an ID of the terminal device 110.
  • the network device 130 transmits 240 a contention resolution message.
  • the contention resolution message comprises an identity (ID) of a terminal device.
  • the contention resolution message in an RA procedure with 4-step RA type is also referred to as a message 4 (MSG4) .
  • the terminal device 110 may declare the RA procedure successful.
  • Fig. 3 illustrates a signaling chart illustrating a CBRA procedure 300 with 2-step RA type in accordance with some embodiments of the present disclosure.
  • a CBRA procedure with 2-step RA type is also referred to as 2-step CBRA procedure.
  • the CBRA procedure 300 will be described with reference to Fig. 1A or 1B.
  • the CBRA procedure 300 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the terminal device 110 transmits 310, to the network device 130, an RA request comprising an RA preamble on PRACH and a payload on physical uplink control channel (PUSCH) .
  • the RA request in an RA procedure with 2-step RA type is also referred to as a message A (MSGA) .
  • the payload on PUSCH comprises an ID of the terminal device 110.
  • the terminal device 110 monitors for a response from the network device 130 within a configured window.
  • the network device 130 transmits 320 a contention resolution message.
  • the contention resolution message comprises an ID of a terminal device.
  • the contention resolution message in an RA procedure with 2-step RA type is also referred to as a message B (MSGB) .
  • the terminal device 110 may declare the RA procedure successful.
  • the terminal device 110 ends the random access procedure.
  • the terminal device 110 performs MSG3 transmission using UL grant scheduled in the fallback indication and monitors contention resolution as shown in Fig. 4.
  • Fig. 4 illustrates a signaling chart illustrating a fallback procedure 400 for a CBRA with 2-step RA type in accordance with some embodiments of the present disclosure.
  • the fallback procedure 400 will be described with reference to Fig. 1A or 1B.
  • the fallback procedure 400 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the terminal device 110 transmits 410, to the network device 130, an RA request comprising an RA preamble on PRACH and a payload on PUSCH.
  • the payload on PUSCH comprises an ID of the terminal device 110.
  • the terminal device 110 monitors for a response from the network device 130 within a configured window.
  • the terminal device 110 receives 420 MSGB comprising a fallback indication. In turn, the terminal device 110 performs 430 MSG3 transmission using UL grant scheduled in the fallback indication and monitors contention resolution.
  • the action 440 in Fig. 4 is similar to the action 240 in Fig. 2. Details of the action 440 is omitted for brevity.
  • Fig. 5 illustrates a signaling chart illustrating a contention-free random access (CFRA) procedure 500 with 4-step RA type in accordance with some embodiments of the present disclosure.
  • a CFRA procedure with 4-step RA type is also referred to as 4-step CFRA procedure.
  • the CFRA procedure 500 will be described with reference to Fig. 1A or 1B.
  • the CFRA procedure 500 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the network device 130 assigns 505 a dedicated RA preamble for MSG1 transmission.
  • the message for assigning the dedicated RA preamble is also referred to as a message 0 (MSG0) .
  • the terminal device 110 transmits 510, to the network device 130, an RA request (i.e., MSG1) comprising the dedicated RA preamble on PRACH.
  • an RA request i.e., MSG1
  • the terminal device 110 monitors for an RAR (i.e., MSG2) from the network device 130 within a configured window.
  • RAR i.e., MSG2
  • the terminal device 110 upon receiving 520 the RAR from the network device 130, the terminal device 110 ends the RA procedure.
  • Fig. 6 illustrates a signaling chart illustrating a CFRA procedure 600 with 2-step RA type in accordance with some embodiments of the present disclosure.
  • a CFRA procedure with 2-step RA type is also referred to as 2-step CFRA procedure.
  • the CFRA procedure 600 will be described with reference to Fig. 1A or 1B.
  • the CFRA procedure 600 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the network device 130 assigns 605 a dedicated RA preamble and PUSCH resource for MSGA transmission.
  • the terminal device 110 transmits 610, to the network device 130, an RA request (i.e., MSGA) comprising the dedicated RA preamble on PRACH and a payload on PUSCH resource assigned by the network device 130.
  • an RA request i.e., MSGA
  • the terminal device 110 monitors for an RAR (i.e., MSGB) from the network device 130 within a configured window.
  • RAR i.e., MSGB
  • the terminal device 110 upon receiving 620 the RAR from the network device 130, the terminal device 110 ends the RA procedure.
  • any of the RA procedures 200, 300, 500 and 600 may be triggered by a sensing request.
  • the sensing request may be indicated from the network device 130 or the SF 150.
  • the sensing request may be indicated from higher layer of the terminal device 110 itself.
  • the terminal device 110 starts an RA procedure triggered by the sensing request.
  • the terminal device 110 may reuse any of the RA procedures 200, 300, 500 and 600 to initiate RRC connection to the network device 130.
  • the terminal device 110 and the network device 130 cannot identify this RA procedure is triggered by the sensing request, i.e., sensing relevant information and request should be exchanged between the terminal device 110 and the network device 130 after the RA procedure is completed.
  • sensing request can be used interchangeably with “sensing service request” .
  • the terminal device 110 may perform at least one of the following:
  • the network device 130 may perform at least one of the following:
  • the terminal device 110 may obtain sensing configuration information or sensing resource allocation from the network device 130 through the sensing triggered RA procedure directly without needing to set up RRC connection with the network device 130.
  • the terminal device 110 can perform a sensing procedure in RRC_IDLE or RRC_INACTIVE status.
  • the terminal device 110 may start a sensing procedure in RRC_IDLE or RRC_INACTIVE status.
  • latency for sensing service may be reduced, and overhead and power consumption for triggering sensing service may be reduced.
  • the sensing triggered RA procedure may be indicated by a physical downlink control channel (PDCCH) , by a MAC entity of the terminal device 110 itself, or by a radio resource control (RRC) message for sensing request.
  • PDCCH physical downlink control channel
  • RRC radio resource control
  • Fig. 7 illustrates a signaling chart illustrating an example process 700 for ISAC in accordance with some embodiments of the present disclosure.
  • the process 700 will be described with reference to Fig. 1A or 1B.
  • the process 700 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the terminal device 110 transmits 710 an RA request for a sensing service to the network device 130.
  • the RA request comprises at least one of the following: an RA preamble, or first type of information related to the sensing service.
  • the first type of information related to the sensing service comprises at least one of following: a sensing request of the terminal device110; or a sensing result report.
  • the network device 130 Upon receiving the RA request for the sensing service, the network device 130 determines 720 responding information for the RA request.
  • the network device 130 transmits 730 the responding information for the RA request to the terminal device 110.
  • the process 700 provides mechanism to start a sensing procedure for the terminal device 110 in RRC_IDLE or RRC_INACTIVE status.
  • the terminal device 110 may reuse RA mechanism in communication system to set up connection with a control node, and then start sensing related procedure.
  • the process 700 needs less complexity to start sensing service in ISAC system for the terminal device in RRC_IDLE or RRC_INACTIVE status.
  • the process 700 may reduce latency for sensing service, and reduce overhead and power consumption for triggering sensing service.
  • an RA configuration for the sensing service may be configured, pre-configured, or predefined.
  • the terminal device 110 may transmit the RA request for the sensing service based on the RA configuration for the sensing service.
  • the RA configuration for the sensing service may comprise at least one RA preamble for the sensing service.
  • the at least one RA preamble for the sensing service may comprise at least one of the following: a first RA preamble for initiating a 4-step RA procedure triggered by the sensing service, or a second RA preamble for initiating the 2-step RA procedure triggered by the sensing service.
  • Fig. 8 illustrates a signaling chart illustrating an example process 800 for ISAC in accordance with some embodiments of the present disclosure.
  • the process 800 may be considered as an example implementation of the process 700 or the procedure 300.
  • the process 800 will be described with reference to Fig. 1A or 1B.
  • the process 800 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the terminal device 110 uses 2-step CBRA to initiate RRC connection to the network device 130.
  • the first type of information related to the sensing service comprises a sensing request of the terminal device 110.
  • the terminal device 110 transmits an RA preamble for the sensing service 810 and a sensing request 820 in the assigned PUSCH resource for MSGA.
  • the network device 130 detects the RA preamble for the sensing service 810 and the sensing request 820 in MSGA, and further transmits MSGB (i.e., contention resolution message) to the terminal device 110.
  • MSGB i.e., contention resolution message
  • the RA configuration for the sensing service may comprise at least one RA preamble for a request for sensing configuration information. This will be described with reference to Fig. 9.
  • Fig. 9 illustrates a signaling chart illustrating an example process 900 for ISAC in accordance with some embodiments of the present disclosure.
  • the process 900 may be considered as an example implementation of the process 700 or the procedure 500.
  • the process 900 will be described with reference to Fig. 1A or 1B.
  • the process 900 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • a dedicated RA preamble is configured for a request for sensing configuration information.
  • a request for sensing configuration information is also referred to as a sensing configuration information request for brevity.
  • the terminal device 110 may need to obtain the sensing configuration information from network device 130. Then, the terminal device 110 triggers a 2-step CFRA procedure with the dedicated preamble for the sensing configuration information request.
  • the network device 130 assigns 905 the dedicated RA preamble for the sensing configuration information request.
  • the terminal device 110 transmits 910, to the network device 130, an RA request (i.e., MSG1) comprising the dedicated RA preamble for the sensing configuration information request on PRACH.
  • an RA request i.e., MSG1
  • the network device 130 detects the dedicated preamble for the sensing configuration information request, and transmits 920 confirmation in an RAR (i.e., MSG2) to the terminal device 110.
  • RAR i.e., MSG2
  • the RA configuration for the sensing service may comprise a dedicated PRACH resource set for the sensing service.
  • the dedicated PRACH resource set for the sensing service comprises at least one PRACH resource for the sensing service.
  • the at least one PRACH resource for the sensing service may be within communication resources. In other words, the at least one PRACH resource for the sensing service may be distinguished from PRACH resources for communication purpose.
  • the at least one PRACH resource for the sensing service may be within a sensing resource set.
  • the terminal device 110 when the terminal device 110 starts an RA procedure triggered by a sensing request, the terminal device 110 transmits an RA preamble using a PRACH resource for the sensing service in the dedicated PRACH resource set to identify the RA procedure is for sensing. Then, the network device 130 detects the RA preamble on a PRACH resource for the sensing service. Then, the network device 130 identifies the RA procedure is for sensing, and determines an RAR accordingly.
  • the RA configuration for the sensing service may comprise a dedicated PRACH resource set for sensing configuration information.
  • the dedicated PRACH resource set for the sensing configuration information comprises at least one PRACH resource for the sensing configuration information.
  • the dedicated PRACH resource set for the sensing configuration information may be configured or pre-configured.
  • the terminal device 110 may trigger a 4-step CFRA procedure, and transmit MSG1 on a PRACH resource for the sensing configuration information.
  • the network device 130 detects an RA preamble on the PRACH resource for the sensing configuration information, and transmits confirmation in MSG2.
  • the RA configuration for the sensing service may comprise a reference signal for determining a type of the RA procedure triggered by the sensing service.
  • the reference signal for determining a type of the RA procedure triggered by the sensing service may be configured, pre-configured or pre-defined.
  • the terminal device 110 may select 4-step RA or 2-step RA based on measurement of the reference signal to perform an RA procedure triggered by a sensing request.
  • the reference signal may be synchronization signal block (SSB) , channel state information reference signal (CSI-RS) , or a sensing signal transmitted by a network node, such as gNB or TRP.
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • a sensing signal transmitted by a network node such as gNB or TRP.
  • the RA configuration for the sensing service may comprise a threshold for receiving power level of the reference signal. Based on the measurement of the reference signal, the terminal device 110 may determine whether to use 2-step RA or 4-step RA for a sensing service. For example, when the measurement of received reference signal exceeds the threshold, 2-step RA is used.
  • the threshold for receiving power level of the reference signal may be configured, pre-configured or pre-defined.
  • the receiving power level of the reference signal comprises at least one of the following: reference signal received power (RSRP) of the reference signal, reference signal received quality (RSRQ) of the reference signal, or received signal strength indication (RSSI) of the reference signal.
  • RSRP reference signal received power
  • RSSI received signal strength indication
  • the reference signal for determining a type of a sensing triggered RA procedure.
  • the reference signal comprises an SSB, and a dedicated threshold of RSRP for determining a type of a sensing triggered RA procedure is pre-configured.
  • the threshold may be indicated through parameter: msgA-RSRP-Threshold-Sensing.
  • the terminal device 110 measures the RSRP of SSB. If the RSRP exceeds the threshold, the terminal device 110 determines to use 2-step RA procedure for a sensing request.
  • the threshold may be indicated through parameter: rsrp-ThresholdSSB-Sensing.
  • the terminal device 110 measures the RSRP of SSB. If the RSRP exceeds the threshold, the terminal device 110 determines to switch from 2-step RA procedure to 4-step RA procedure.
  • the RA configuration for the sensing service may comprise a PUSCH resource for initiating a 2-step CFRA procedure triggered by the sensing service.
  • a dedicated medium access control (MAC) protocol data unit may be defined according to sensing requirement.
  • the terminal device 110 may receive the responding information for the RA request by receiving a MAC PDU which comprises at least one MAC subPDU.
  • Each of the at least one MAC subPDU comprises at least one of the following: a MAC subheader and a MAC service data unit (SDU) .
  • SDU MAC service data unit
  • the at least one MAC subPDU may comprise a first MAC subPDU.
  • the first MAC subPDU may comprises a first MAC subheader with a random access preamble identity (RAPID) only which indicates acknowledgment for a request for sensing configuration information.
  • RAPID random access preamble identity
  • the RAPID is associated with the RA preamble for the sensing service. This will be described with reference to Figs. 10A and 10B.
  • Fig. 10A illustrates a signaling chart illustrating an example process 1000 for ISAC in accordance with some embodiments of the present disclosure.
  • the process 1000 may be considered as an example implementation of the process 700.
  • the process 1000 will be described with reference to Fig. 1A or 1B.
  • the process 1000 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the network device 130 assigns 1005 a dedicated RA preamble for a sensing configuration information request.
  • the sensing configuration information may be a type of system information block (SIB) , or a system information (SI) message.
  • SIB system information block
  • SI system information
  • the sensing configuration information may not be broadcast by the network device 130 periodically. Then, the terminal device 110 needs to transmit a request to obtain the SIB or SI for sensing.
  • the terminal device 110 transmits 1010, to the network device 130, an RA request (i.e., MSG1) comprising the dedicated RA preamble for the sensing configuration information request on PRACH.
  • an RA request i.e., MSG1
  • the dedicated RA preamble for the sensing configuration information request indicates to request the sensing configuration information.
  • the network device 130 detects the RA request with the dedicated preamble, and transmits 1020 an RAR (i.e., MGS2) to the terminal device 110.
  • the RAR comprises a MAC PDU which comprises a first MAC subPDU.
  • the first MAC subPDU comprises a first MAC subheader 1040 with an RAPID only which indicates acknowledgment for the sensing configuration information request. Details of the first MAC subheader 1040 will be described with reference to Fig. 10B later.
  • the network device 130 After the RA procedure succeeds, the network device 130 further broadcasts 1030 the sensing configuration information on physical downlink shared channel (PDSCH) .
  • PDSCH physical downlink shared channel
  • Fig. 10B illustrates an example of a MAC subheader in accordance with some embodiments of the present disclosure.
  • the first MAC subheader 1040 may comprise an Extension field (represented by E) , a Type field (represented by T) and RAPID.
  • the Extension field is a flag indicating whether the MAC subPDU including this MAC subheader is the last MAC subPDU or not in the MAC PDU.
  • the Type field is a flag indicating whether the MAC subheader contains an RAPID or a Backoff Indicator (BI) .
  • the RAPID indicates acknowledgment for the sensing configuration information request.
  • the RAPID is associated with the dedicated RA preamble for the sensing configuration information request.
  • the RAPID may be derived from the dedicated preamble for the sensing configuration information request.
  • the at least one MAC subPDU may comprise a second MAC subPDU.
  • the second MAC subPDU may comprise a second MAC subheader with an RAPID and a second MAC service data unit (SDU) comprising the sensing configuration information. This will be described with reference to Figs. 11, 12A, 12B, 12C and 12D.
  • Fig. 11 illustrates an example of a MAC PDU in accordance with some embodiments of the present disclosure.
  • a dedicated PRACH resource set for the sensing configuration information may be configured or pre-configured.
  • the terminal device 110 may trigger a 4-step CFRA procedure, and transmit an RA preamble on a PRACH resource for the sensing configuration information in the dedicated PRACH resource set.
  • the network device 130 detects the RA preamble on the PRACH resource for the sensing configuration information, and transmits MSG2 to the terminal device 110.
  • the MSG2 comprises a MAC PDU 1100.
  • the MAC PDU 1100 comprises one or more MAC subPDUs and optionally padding.
  • the MAC PDU 1100 may comprise a MAC subPDU 1110, a MAC subPDU 1120, and so on.
  • Each of the one or more MAC subPDUs in the MAC PDU 1100 may be referred to as a second MAC subPDU.
  • the MAC subPDU 1110 comprises a MAC subheader 1112 with Backoff Indicator (BI) only.
  • the BI field identifies the overload condition in the cell.
  • the size of the BI field is 4 bits.
  • the MAC subPDU 1120 comprises a MAC subheader 1122 and a MAC SDU 1124.
  • the MAC subheader 1122 may comprise an Extension field (represented by E) , a Type field (represented by T) and RAPID.
  • the Extension field is a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU or not in the MAC PDU.
  • the Type field is a flag indicating whether the MAC subheader contains an RAPID or a BI.
  • the RAPID field identifies the transmitted RA preamble.
  • the MAC SDU 1124 comprises the sensing configuration information (represented by “SenInfo” in Fig. 11) .
  • the sensing configuration information may comprise at least one of the following: a configuration for sensing resources, allocation of a sensing mode, or a configuration for a sensing TRP.
  • an RA preamble for the sensing configuration information request may be configured or pre-configured.
  • the terminal device 110 may trigger a 2-step CFRA procedure, and transmit MSGA comprising the RA preamble for the sensing configuration information request.
  • the RA preamble for the sensing configuration information request may indicate to request the sensing configuration information.
  • the terminal device 110 may determine that the second MAC subPDU in MSGB is associated with the sensing configuration information based on the RA preamble for the sensing configuration information request.
  • Fig. 12A illustrates an example of a MAC PDU in accordance with some embodiments of the present disclosure.
  • the terminal device 110 may trigger a 2-step RA procedure.
  • the terminal device 110 transmits, to the network device 130, MSGA comprising an RA preamble on PRACH and a payload on PUSCH. Then, the network device 130 transmits MSGB based on the detection of MSGA.
  • the MSGB comprises a MAC PDU 1200.
  • the MAC PDU 1200 comprises one or more MAC subPDUs and optionally padding.
  • the MAC PDU 1200 may comprise a MAC subPDU 1210, a MAC subPDU 1220, and so on.
  • Each of the MAC subPDU 1210 and the MAC subPDU 1220 may be referred to as a second MAC subPDU.
  • the MAC subPDU 1210 comprises a MAC subheader 1212 and a MAC SDU 1214.
  • the MAC subPDU 1220 comprises a MAC subheader 1222 and a MAC SDU 1224.
  • Fig. 12B illustrates an example of the MAC subheader 1212 and the MAC subheader 1222 in accordance with some embodiments of the present disclosure.
  • each of the MAC subheader 1212 and the MAC subheader 1222 may comprise an Extension field (represented by E) , a T1 field (represented by T1) and RAPID.
  • the Extension field is a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU (other than MAC subPDU for MAC SDU) or not in the MAC PDU.
  • the T1 field is a flag indicating whether the MAC subheader contains an RAPID or T2.
  • the RAPID field identifies the transmitted RA preamble.
  • the RAPID is derived from the RA preamble.
  • the size of the RAPID field is 6 bits.
  • Each of the MAC SDU 1214 and the MAC SDU 1224 comprises a first indicator (represented by F) .
  • the first indicator indicates whether a respective one of the MAC SDU 1214 and the MAC SDU 1224 is for fallback RAR or the sensing configuration information.
  • a reserved bit in a legacy MAC SDU may be used as the first indicator.
  • Fig. 12C illustrates an example of the MAC SDU 1214 in accordance with some embodiments of the present disclosure.
  • the MAC SDU 1214 comprises an F filed 1216.
  • the F filed 1216 set to “0” indicates that the MAC SDU 1214 is for fallback RAR.
  • Fig. 12D illustrates an example of the MAC SDU 1224 in accordance with some embodiments of the present disclosure.
  • the MAC SDU 1224 comprises an F filed 1226.
  • the F filed 1226 set to “1” indicates that the MAC SDU 1224 is for the sensing configuration information (represented by “SenInfo” in Fig. 12A) .
  • the terminal device 110 may determine that the MAC SDU 1224 in MSGB is associated with the sensing configuration information based on the F filed 1226.
  • the sensing configuration information may comprise at least one of the following: a configuration for sensing resources, allocation of a sensing mode, or a configuration for a sensing TRP.
  • the size of the sensing configuration information is 55 bits.
  • the terminal device 110 may determine that the second MAC subPDU is associated with the sensing configuration information based on a radio network temporary identifier (RNTI) which is associated with a PRACH resource used for the sensing configuration information request.
  • RNTI radio network temporary identifier
  • each PRACH resource is associated with an RNTI respectively.
  • an associated RNTI is used for identifying DCI which indicates a PDSCH transmission comprising the MAC PDU with the sensing configuration information.
  • the at least one MAC subPDU may comprise a third MAC subPDU.
  • the third MAC subPDU may comprise a third MAC subheader with an RAPID and a success RAR for the sensing service. This will be described with reference to Figs. 13A, 13B, 13C and 13D.
  • Fig. 13A illustrates an example of a MAC PDU in accordance with some embodiments of the present disclosure.
  • the terminal device 110 may trigger a 2-step RA procedure.
  • the terminal device 110 transmits MSGA to the network device 130.
  • the network device 130 transmits MSGB based on the detection of MSGA.
  • the MSGB comprises a MAC PDU 1300.
  • the MAC PDU 1300 comprises one or more MAC subPDUs and optionally padding.
  • the MAC PDU 1300 may comprise a MAC subPDU 1310, a MAC subPDU 1320, a MAC subPDU 1330, and so on.
  • Each of the MAC subPDU 1320 and the MAC subPDU 1330 may be referred to as a third MAC subPDU.
  • the MAC subPDU 1310 comprises a MAC subheader 1312 with BI only.
  • the BI field identifies the overload condition in the cell.
  • the size of the BI field is 4 bits.
  • the MAC subPDU 1320 comprises a MAC subheader 1322 and a MAC SDU 1324.
  • the MAC subPDU 1330 comprises a MAC subheader 1332 and a MAC SDU 1334.
  • Fig. 13B illustrates an example of the MAC subheader 1312 in accordance with some embodiments of the present disclosure.
  • the MAC subheader 1312 may comprise an Extension 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.
  • the Extension field is a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU (other than MAC subPDU for MAC SDU) or not in the MAC PDU.
  • the T1 field is a flag indicating whether the MAC subheader contains an RAPID or T2.
  • the Reserved bit is set to 0.
  • the T2 field is a flag indicating whether the MAC subheader contains a BI or a MAC SDU indicator (represented by S) .
  • the BI field identifies the overload condition in the cell.
  • the size of the BI field is 4 bits.
  • Fig. 13C illustrates an example of the MAC subheader 1322 and the MAC subheader 1332 in accordance with some embodiments of the present disclosure.
  • each of the MAC subheader 1322 and the MAC subheader 1332 may comprise an Extension 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 bit (represented by R) .
  • each of the MAC subheader 1322 and the MAC subheader 1332 comprises a second indicator 1340 (represented by C) .
  • the second indicator 1340 indicates whether the success RAR for the sensing service follows a respective one of the MAC subheader 1322 and the MAC subheader 1332 or not.
  • a reserved bit in a legacy MAC SDU may be used as the second indicator 1340.
  • the C filed in the MAC subheader 1322 may be set to “0” indicates that the success RAR for the sensing service does not follow the MAC subheader 1322, while the C filed in the MAC subheader 1332 may be set to “1” indicates that the success RAR for the sensing service follows the MAC subheader 1332.
  • the MAC SDU 1334 is also referred to as the success RAR for the sensing service 1334.
  • Fig. 13D illustrates an example of the MAC SDU 1334 in Fig. 13A in accordance with some embodiments of the present disclosure.
  • the MAC SDU 1334 i.e., the success RAR for the sensing service 1334) comprises UE contention resolution identity, sensing resource allocation and cell radio network temporary identifier (C-RNTI) .
  • C-RNTI cell radio network temporary identifier
  • the sensing resource allocation indicates sensing resources assigned for the terminal device 110.
  • the size of the sensing resource allocation is 23 bits.
  • the first type of information related to the sensing service may comprise at least one of following: a sensing request of the terminal device 110, or a sensing result report.
  • the terminal device 110 may trigger a 4-step RA procedure.
  • the terminal device 110 may receive MSG2 which assigns a PUSCH resource for MSG3. Then, the terminal device 110 may transmit the sensing result report and/or the sensing request on the assigned PUSCH resource in MSG3 to the network device 130. After that, the network device 130 may transmit MSG4 to the terminal device 110 to acknowledge a successfully receiving of the sensing result report and/or the sensing request carried in MSG3.
  • the terminal device 110 may trigger a 2-step RA procedure.
  • a PUSCH resource is assigned for MSGA transmission.
  • the terminal device 110 may transmit the sensing result report and/or the sensing request on the assigned PUSCH resource in MSGA to the network device 130.
  • the network device 130 may transmit MSGB to the terminal device 110 to acknowledge a successfully receiving of the sensing result report and/or the sensing request carried in MSGA.
  • the sensing request of the terminal device 110 may comprise at least one of the following:
  • the sensing result report may comprise at least one of the following:
  • ⁇ a list of detected sensing signals, each of the detected sensing signals being identified by an ID of a sensing TRP, or
  • the sensing capability of the terminal device 110 may comprise at least one of following:
  • sensing modes may be defined based on transmission (Tx) /reception (Rx) node of sensing signal.
  • the sensing modes may comprise at least one of the following:
  • a sensing signal is transmitted by a network node, e.g., gNB (such as the network device 130) , and received/measured by the network node itself;
  • a network node e.g., gNB (such as the network device 130)
  • ⁇ sensing mode 2 a sensing signal is transmitted by a network node (such as the network device 130) , and received/measured by a UE (such as the terminal device 110 or 120) ;
  • a sensing signal is transmitted by a network node A (such as the network device 130) , and received/measured by a network node B (such as a network device which is not shown in Fig. 1A or 1B) ;
  • ⁇ sensing mode 4 a sensing signal is transmitted by a UE (such as the terminal device 110 or 120) , and received/measured by the UE itself;
  • ⁇ sensing mode 5 a sensing signal is transmitted by a UE (such as the terminal device 110 or 120) , and received/measured by a network node (such as the network device 130) ; or
  • ⁇ sensing mode 6 a sensing signal is transmitted by a UE A (such as the terminal device 110) , and received/measured by a UE B (such as the terminal device 120) .
  • the at least one sensing mode supported by the terminal device 110 may comprise at least one of the following: sensing mode 2, sensing mode 4, sensing mode 5, or sensing mode 6.
  • the type of sensing signals supported by the terminal device 110 may comprise at least one of the following: sensing reference signals (RS) , positioning reference signals (PRS) , sounding reference signals (SRS) , or channel state information reference signals (CSI-RS) .
  • RS sensing reference signals
  • PRS positioning reference signals
  • SRS sounding reference signals
  • CSI-RS channel state information reference signals
  • the type of the sensing result report supported by the terminal device 110 may comprise at least one of the following: position, velocity, or point cloud.
  • the network device 130 may determine, based on the sensing request, responding information for the sensing request.
  • the responding information for the sensing request may comprise information indicating at least one of the following: a sensing mode, or at least one sensing resource. Then, the network device 130 may transmit, to the terminal device 110, the responding information for the sensing request in MSG4 or MSGB. This will be described with reference to Fig. 14.
  • Fig. 14 illustrates a signaling chart illustrating an example process 1400 for ISAC in accordance with some embodiments of the present disclosure.
  • the process 1400 may be considered as an example implementation of the process 700.
  • the process 1400 will be described with reference to Fig. 1A or 1B.
  • the process 1400 may involve the terminal device 110 and the network device 130 in Fig. 1A or 1B.
  • the terminal device 110 initiates a 4-step CBRA procedure.
  • the first type of information related to the sensing service comprises a sensing request of the terminal device 110.
  • the responding information for the sensing request comprises information indicating at least one of the following: a sensing mode assigned for the terminal device 110, or at least one sensing resource.
  • the terminal device 110 transmits 1410 MSG1 comprising an RA preamble on PRACH. Then, the terminal device 110 receives 1420, from the network device 130, MSG2 which assigns a PUSCH resource for MSG3.
  • the terminal device 110 transmits 1430 a sensing request on the assigned PUSCH resource as MSG3 to the network device 130.
  • the sensing request of the terminal device 110 may comprise at least one of the following:
  • the sensing service requirement may comprise surroundings detection.
  • the sensing capability of the terminal device 110 may comprise: at least one sensing mode supported by the terminal device 110, and a type of sensing signals supported by the terminal device 110.
  • the at least one sensing mode supported by the terminal device 110 may comprise at least one of the following: sensing mode 4, or sensing mode 5.
  • sensing mode 4 a sensing signal is transmitted by the terminal device 110 and received/measured by the terminal device 110 itself.
  • sensing mode 5 a sensing signal is transmitted by the terminal device 110 and received/measured by the network device 130.
  • the type of sensing signals supported by the terminal device 110 may comprise sensing RS.
  • the network device 130 determines the responding information for the sensing request.
  • the responding information for the sensing request comprises information indicating a sensing mode and at least one sensing resource.
  • the responding information for the sensing request comprises information indicating the sensing mode 4 is assigned for the terminal device 110, i.e., the terminal device 110 should use the sensing mode 4 for a sensing service.
  • the responding information for the sensing request further comprises at least one sensing resource.
  • the at least one sensing resource may comprise at least one of the following: a first sensing resource assigned for the terminal device 110, or a second sensing resource used by a sensing target.
  • the network device 130 transmits 1440 the responding information for the sensing request in PDSCH associated with MSG4.
  • the terminal device 110 transmits sensing RS on the at least one assigned sensing resource for the terminal device 110 and measures the echo signal to obtain a sensing result.
  • Fig. 15 illustrates an example 1500 of determining the responding information for the sensing request in accordance with some embodiments of the present disclosure.
  • the terminal device 110 initiates a 2-step RA procedure.
  • the terminal device 110 transmits MSGA comprising an RA preamble on PRACH and a sensing request on the assigned PUSCH resource.
  • the sensing request of the terminal device 110 may comprise at least one of the following:
  • the sensing capability of the terminal device 110 may comprise at least one sensing mode supported by the terminal device 110.
  • the at least one sensing mode supported by the terminal device 110 may comprise at least one of the following: sensing mode 4, or sensing mode 6.
  • sensing mode 4 a sensing signal is transmitted by the terminal device 110 and received/measured by the terminal device 110 itself.
  • sensing mode 6 a sensing signal is transmitted by the terminal device 120, and received/measured by the terminal device 110.
  • the network device 130 determines the responding information for the sensing request.
  • the responding information for the sensing request comprises information indicating a sensing mode and at least one sensing resource.
  • the responding information for the sensing request comprises information indicating the sensing mode 6 assigned for the terminal device 110.
  • the responding information for the sensing request further comprises at least one sensing resource.
  • the at least one sensing resource may comprise a second sensing resource used by a sensing target (i.e., the terminal device 120) .
  • the network device 130 transmits the responding information for the sensing request in PDSCH associated with MSGB.
  • the terminal device 110 detects and measures a sensing signal transmitted by the sensing target (i.e., the terminal device 120) , and determines a sensing result, i.e., relevant position and relevant velocity between the terminal device 110 and the terminal device 120.
  • a sensing signal transmitted by the sensing target i.e., the terminal device 120
  • a sensing result i.e., relevant position and relevant velocity between the terminal device 110 and the terminal device 120.
  • the network device 130 may determine, based on the sensing result report, responding information for the sensing result report.
  • the responding information for the sensing result report may comprise information indicating at least one of the following: an ID of the at least one sensing TRP, or at least one sensing resource assigned for the terminal device 110. Then, the network device 130 may transmit, to the terminal device 110, the responding information for the sensing result report in MSG4 or MSGB. This will be described with reference to Figs. 16 and 17.
  • Fig. 16 illustrates an example of an ISAC system 1600 in accordance with some embodiments of the present disclosure.
  • the ISAC system 1600 comprises the network device 130, the terminal device 110, a TRP 1610, a TRP 1620 and a TRP 1630.
  • the terminal device 120 in Fig. 1A or 1B may act as one of TRPs 1610, 1620 and 1630.
  • Fig. 17 illustrates a signaling chart illustrating an example process 1700 for ISAC in accordance with some embodiments of the present disclosure.
  • the process 1700 may be considered as an example implementation of the process 700.
  • the process 1700 will be described with reference to Fig. 16.
  • the process 1700 may involve the terminal device 110, the network device 130 and the TRP 1630 in Fig. 16.
  • the terminal device 110 transmits 1710 MSGA.
  • MSA comprises an RA preamble on PRACH as well as a sensing request of the terminal device 110 and a sensing result report on the assigned PUSCH resource for MSGA.
  • the sensing request of the terminal device 110 comprises sensing service requirement and position information of the terminal device 110.
  • the sensing result report comprises a list of detected sensing signals. Each of the detected sensing signals is identified by an ID of a sensing TRP.
  • the sensing result report also comprises a sensing result for each of the detected sensing signals.
  • the network device 130 determines 1720 at least one suitable sensing TRP for the terminal device 110. For example, the network device 130 determines the TRP 1630 as a suitable sensing TRP for the terminal device 110.
  • the network device 130 Based on the sensing result report, the network device 130 also determines at least one sensing resource assigned for the terminal device 110 (i.e., sensing resource allocation for the terminal device 110) .
  • the network device 130 transmits 1730 MSGB to the terminal device 110.
  • MSGB comprises an ID of the TRP 1630 and the sensing resource allocation for the terminal device 110.
  • the terminal device 110 transmits 1750 a sensing signal on the assigned sensing resource.
  • the network device 130 transmits 1740 the sensing resource allocation for the terminal device 110 to the TRP 1630.
  • the TRP 1630 detects the sensing signal from the terminal device 110 based on the sensing resource allocation, and determines 1760 a sensing result.
  • the TRP 1630 transmits 1770 a sensing result report to the network device 130.
  • Fig. 18 illustrates a flowchart of an example method 1800 in accordance with some embodiments of the present disclosure.
  • the method 1800 can be implemented at a terminal device, such as the terminal device 110 or the terminal device 120, as shown in Fig. 1A or 1B.
  • the method 1800 will be described with reference to Fig. 1A or 1B.
  • the terminal device 110 transmits an RA request for a sensing service.
  • the RA request comprises at least one of the following: an RA preamble or first type of information related to the sensing service.
  • the terminal device 110 receives responding information for the RA request.
  • transmitting the RA request for a sensing service comprises transmit the RA request based on an RA configuration for the sensing service.
  • the RA configuration for the sensing service comprises at least one of the following: at least one RA preamble for the sensing service, at least one RA preamble for a request for sensing configuration information, at least one physical random access channel (PRACH) resource for the sensing service, at least one PRACH resource for the sensing configuration information, a reference signal for determining a type of an RA procedure triggered by the sensing service, a threshold for receiving power level of the reference signal, or a physical uplink shared channel (PUSCH) resource for initiating a 2-step contention free random access (CFRA) procedure triggered by the sensing service.
  • PRACH physical random access channel
  • PUSCH physical uplink shared channel
  • the at least one RA preamble for the sensing service comprises at least one of the following: a first RA preamble for initiating a 4-step CFRA procedure triggered by the sensing service, or a second RA preamble for initiating the 2-step CFRA procedure triggered by the sensing service.
  • the receiving power level of the reference signal comprises at least one of the following: reference signal received power (RSRP) of the reference signal, reference signal received quality (RSRQ) of the reference signal, or received signal strength indication (RSSI) of the reference signal.
  • RSRP reference signal received power
  • RSSI received signal strength indication
  • receiving the responding information for the RA request comprises: receiving a medium access control (MAC) protocol data unit (PDU) which comprises at least one MAC subPDU.
  • PDU medium access control protocol data unit
  • each of the at least one MAC subPDU comprises at least one of the following: a MAC subheader and a MAC service data unit (SDU) .
  • the at least one MAC subPDU comprises a first MAC subPDU
  • the first MAC subPDU comprises: a first MAC subheader with a random access preamble identity (RAPID) only which indicates acknowledgment for a request for sensing configuration information, the RAPID being associated with the RA preamble for the request for sensing configuration information.
  • RAPID random access preamble identity
  • the at least one MAC subPDU comprises a second MAC subPDU
  • the second MAC subPDU comprises: a second MAC subheader with a random access preamble identity (RAPID) and a second MAC service data unit (SDU) comprising the sensing configuration information.
  • RAPID random access preamble identity
  • SDU second MAC service data unit
  • the sensing configuration information comprises at least one of the following: a configuration for sensing resources, allocation of a sensing mode, or a configuration for a sensing transmission-reception point (TRP) .
  • the method 1800 further comprises: determining that the second MAC subPDU is associated with the sensing configuration information based on at least one of following: the RA preamble which is for a request for the sensing configuration information; a radio network temporary identifier (RNTI) which is associated with a physical random access channel (PRACH) resource used for a request for the sensing configuration information; or a first indicator which is comprised in the second MAC SDU and indicates whether the second MAC SDU is for fallback random access response (RAR) or the sensing configuration information.
  • RNTI radio network temporary identifier
  • PRACH physical random access channel
  • RAR fallback random access response
  • the at least one MAC subPDU comprises a third MAC subPDU
  • the third MAC subPDU comprises: a third MAC subheader with a random access preamble identity (RAPID) and a success random access response (RAR) for the sensing service.
  • RAPID random access preamble identity
  • RAR success random access response
  • the third MAC subheader comprises a second indicator indicating whether the success RAR for the sensing service follows the third MAC subheader or not.
  • the first type of information related to the sensing service comprises at least one of following: a sensing request of the terminal device; or a sensing result report.
  • the sensing request of the terminal device comprises at least one of the following: sensing service requirement, an identity (ID) of at least one sensing target, a sensing resource request, sensing capability of the terminal device, position information of the terminal device, or velocity information of the terminal device.
  • the sensing result report comprises at least one of the following: an identity (ID) of at least one sensing target, an ID of at least one sensing signal, an ID of at least one sensing transmission-reception point (TRP) , measurement result of the at least one sensing signal, position information of the at least one sensing target, velocity information of the at least one sensing target, point cloud data of the at least one sensing target, a list of detected sensing signals, each of the detected sensing signals being identified by an ID of a sensing TRP, or a sensing result for each of the detected sensing signals.
  • ID identity
  • TRP transmission-reception point
  • the sensing capability of the terminal device comprises at least one of following: at least one sensing mode supported by the terminal device; a type of sensing signals supported by the terminal device; or a type of a sensing result report supported by the terminal device.
  • the responding information for the RA request comprises responding information for the sensing request.
  • the responding information for the sensing request comprises information indicating at least one of the following: a sensing mode, or at least one sensing resource.
  • the at least one sensing resource comprises at least one of the following: a first sensing resource assigned for the terminal device, or a second sensing resource used by a sensing target.
  • the responding information for the RA request comprises responding information for the sensing result report.
  • the responding information for the sensing result report comprises information indicating at least one of the following: an identity of the at least one sensing TRP, or at least one sensing resource assigned for the terminal device.
  • Fig. 19 illustrates a flowchart of an example method 1900 in accordance with some embodiments of the present disclosure.
  • the method 1900 can be implemented at a network device, such as the network device 130 as shown in Fig. 1A or 1B.
  • a network device such as the network device 130 as shown in Fig. 1A or 1B.
  • the method 1900 will be described with reference to Fig. 1A or 1B.
  • the network device 130 receives an RA request for a sensing service.
  • the RA request comprises at least one of the following: an RA preamble or first type of information related to the sensing service.
  • the network device 130 determines responding information for the RA request.
  • the network device 130 transmits the responding information for the RA request.
  • receiving the RA request comprises receiving the RA request based on an RA configuration for the sensing service.
  • the RA configuration for the sensing service comprises at least one of the following: at least one RA preamble for the sensing service, at least one RA preamble for a request for sensing configuration information, at least one physical random access channel (PRACH) resource for the sensing service, at least one PRACH resource for the sensing configuration information, a reference signal for determining a type of an RA procedure triggered by the sensing service, a threshold for receiving power level of the reference signal, or a physical uplink shared channel (PUSCH) resource for initiating a 2-step contention free random access (CFRA) procedure triggered by the sensing service.
  • PRACH physical random access channel
  • PUSCH physical uplink shared channel
  • the at least one RA preamble for the sensing service comprises at least one of the following: a first RA preamble for initiating a 4-step CFRA procedure triggered by the sensing service, or a second RA preamble for initiating the 2-step CFRA procedure triggered by the sensing service.
  • the receiving power level of the reference signal comprises at least one of the following: reference signal received power (RSRP) of the reference signal, reference signal received quality (RSRQ) of the reference signal, or received signal strength indication (RSSI) of the reference signal.
  • RSRP reference signal received power
  • RSSI received signal strength indication
  • the network device is caused to transmit the responding information for the RA request by: transmitting a medium access control (MAC) protocol data unit (PDU) which comprises at least one MAC subPDU.
  • MAC medium access control
  • PDU protocol data unit
  • each of the at least one MAC subPDU comprises at least one of the following: a MAC subheader and a MAC service data unit (SDU) .
  • the at least one MAC subPDU comprises a first MAC subPDU
  • the first MAC subPDU comprises: a first MAC subheader with a random access preamble identity (RAPID) only which indicates acknowledgment for a request for sensing configuration information, the RAPID being associated with the RA preamble for the sensing service.
  • RAPID random access preamble identity
  • the at least one MAC subPDU comprises a second MAC subPDU
  • the second MAC subPDU comprises: a second MAC subheader with a random access preamble identity (RAPID) and a second MAC service data unit (SDU) comprising the sensing configuration information.
  • RAPID random access preamble identity
  • SDU second MAC service data unit
  • the sensing configuration information comprises at least one of the following: a configuration for sensing resources, allocation of a sensing mode, or a configuration for a sensing transmission-reception point (TRP) .
  • the second MAC subPDU is associated with the sensing configuration information based on at least one of following: the RA preamble which is for a request for the sensing configuration information; a radio network temporary identifier (RNTI) which is associated with a physical random access channel (PRACH) resource used for a request for the sensing configuration information; or a first indicator which is comprised in the second MAC SDU and indicates whether the second MAC SDU is for fallback random access response (RAR) or the sensing configuration information.
  • RNTI radio network temporary identifier
  • PRACH physical random access channel
  • RAR fallback random access response
  • the at least one MAC subPDU comprises a third MAC subPDU
  • the third MAC subPDU comprises: a third MAC subheader with a random access preamble identity (RAPID) and a success random access response (RAR) for the sensing service.
  • RAPID random access preamble identity
  • RAR success random access response
  • the third MAC subheader comprises a second indicator indicating whether the success RAR for the sensing service follows the third MAC subheader or not.
  • the first type of information related to the sensing service comprises at least one of following: a sensing request of the terminal device; or a sensing result report.
  • the sensing request of the terminal device comprises at least one of the following: sensing service requirement, an identity (ID) of at least one sensing target, a sensing resource request, sensing capability of the terminal device, position information of the terminal device, or velocity information of the terminal device.
  • the sensing result report comprises at least one of the following: an identity (ID) of at least one sensing target, an ID of at least one sensing signal, an ID of at least one sensing transmission-reception point (TRP) , measurement result of the at least one sensing signal, position information of the at least one sensing target, velocity information of the at least one sensing target, point cloud data of the at least one sensing target, a list of detected sensing signals, each of the detected sensing signals being identified by an ID of a sensing TRP, or a sensing result for each of the detected sensing signals.
  • ID identity
  • TRP transmission-reception point
  • the sensing capability of the terminal device comprises at least one of following: at least one sensing mode supported by the terminal device; a type of sensing signals supported by the terminal device; or a type of a sensing result report supported by the terminal device.
  • the responding information for the RA request comprises responding information for the sensing request.
  • the responding information for the sensing request comprises information indicating at least one of the following: a sensing mode, or at least one sensing resource.
  • the at least one sensing resource comprises at least one of the following: a first sensing resource assigned for the terminal device, or a second sensing resource used by a sensing target.
  • the responding information for the RA request comprises responding information for the sensing result report.
  • the responding information for the sensing result report comprises information indicating at least one of the following: an identity of the at least one sensing TRP, or at least one sensing resource assigned for the terminal device.
  • Fig. 20 is a simplified block diagram of a device 2000 that is suitable for implementing embodiments of the present disclosure.
  • the device 2000 can be considered as a further example embodiment of the terminal device 110, the terminal device 120, or the control node 130 as shown in Fig. 1A or 1B. Accordingly, the device 2000 can be implemented at or as at least a part of the terminal device 110, the terminal device 120, or the control node 130.
  • the 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 part of a program 2030.
  • the transceiver 2040 may be for bidirectional communications or a unidirectional communication based on requirements.
  • the transceiver 2040 may include at least one of a transmitter 2042 and a receiver 2044.
  • the transmitter 2042 and the receiver 2044 may be functional modules or physical entities.
  • the transceiver 2040 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the components included in the apparatuses and/or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof.
  • one or more units may be implemented using software and/or firmware, for example, machine-executable instructions stored on the storage medium.
  • parts or all of the units in the apparatuses and/or devices may be implemented, at least in part, by one or more hardware logic components.
  • FPGAs Field-programmable Gate Arrays
  • ASICs Application-specific Integrated Circuits
  • ASSPs Application-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent un dispositif, un procédé et un support lisible par ordinateur pour ISAC. Un dispositif terminal transmet une demande d'accès aléatoire (RA) pour un service de détection. La demande de RA comprend un préambule de RA et un premier type d'informations relatives au service de détection. Le dispositif terminal reçoit des informations de réponse pour la demande de RA.
PCT/CN2023/136879 2023-12-06 2023-12-06 Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées Pending WO2025118197A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/136879 WO2025118197A1 (fr) 2023-12-06 2023-12-06 Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/136879 WO2025118197A1 (fr) 2023-12-06 2023-12-06 Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées

Publications (1)

Publication Number Publication Date
WO2025118197A1 true WO2025118197A1 (fr) 2025-06-12

Family

ID=95981376

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/136879 Pending WO2025118197A1 (fr) 2023-12-06 2023-12-06 Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées

Country Status (1)

Country Link
WO (1) WO2025118197A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887930A (zh) * 2021-01-25 2021-06-01 温州职业技术学院 一种基于物联网的传感器感测信息高速上传方法及系统
CN113727436A (zh) * 2021-07-16 2021-11-30 中国信息通信研究院 一种终端非激活状态通信感知方法和设备
US20220191819A1 (en) * 2020-12-10 2022-06-16 Nokia Technologies Oy Associating sensing information with a user
US20230276500A1 (en) * 2020-08-06 2023-08-31 Beijing Xiaomi Mobile Software Co., Ltd. Method for random access, communication device, and storage medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230276500A1 (en) * 2020-08-06 2023-08-31 Beijing Xiaomi Mobile Software Co., Ltd. Method for random access, communication device, and storage medium
US20220191819A1 (en) * 2020-12-10 2022-06-16 Nokia Technologies Oy Associating sensing information with a user
CN112887930A (zh) * 2021-01-25 2021-06-01 温州职业技术学院 一种基于物联网的传感器感测信息高速上传方法及系统
CN113727436A (zh) * 2021-07-16 2021-11-30 中国信息通信研究院 一种终端非激活状态通信感知方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
XIAOMI: "Sensing channel model in LLS and SLS", 3GPP TSG RAN MEETING #99 RP-230065, 23 March 2023 (2023-03-23) *

Similar Documents

Publication Publication Date Title
US12063558B2 (en) Early data transmission for dual connectivity or carrier aggregation
US20250142425A1 (en) Method, device and computer storage medium of communication
WO2023060413A1 (fr) Procédé, dispositif et support de stockage informatique pour les communications
US20240397556A1 (en) Method for initial access to support redcap ue using restricted prach occasions shared with nr ue
WO2024148575A1 (fr) Dispositif et procédé de communication
WO2024000601A1 (fr) Procédés, dispositifs, ainsi que support de communication
WO2025118197A1 (fr) Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées
WO2024007176A1 (fr) Procédés, dispositifs et support de communication
WO2024197742A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications de liaison latérale
WO2025199695A1 (fr) Dispositifs et procédés de communication
WO2025227338A1 (fr) Nœuds de détection, procédé et support lisible par ordinateur pour une détection et une communication intégrées
WO2024212074A1 (fr) Dispositifs, procédés et supports lisibles par ordinateur pour détection et communication intégrées
WO2025145430A1 (fr) Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées
WO2025081313A1 (fr) Dispositifs et procédés de communication
WO2025086214A1 (fr) Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées
WO2024192769A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications de liaison latérale
WO2025217816A1 (fr) Nœud de réseau, dispositif terminal, procédés et supports lisibles par ordinateur permettant une détection et une communication intégrées (isac)
WO2025175584A1 (fr) Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées
WO2025194392A1 (fr) Nœud de commande de détection, procédé et support lisible par ordinateur pour une détection et une communication intégrées
WO2024168511A1 (fr) Dispositif, procédé et support lisible par ordinateur pour détection et communication intégrées
WO2024040449A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés aux communications de liaison latérale
WO2025081414A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications de liaison latérale
WO2025030505A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications de liaison latérale
WO2024187475A1 (fr) Dispositifs et procédés de communication
WO2025217887A1 (fr) Dispositif, procédé et support lisible par ordinateur pour communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23960509

Country of ref document: EP

Kind code of ref document: A1