Communication methods and related products

Abstract

This invention provides a communication method and related products. The method is applied to ultra-wideband sensing and includes: a response end acquiring multiple measurement report frames based on a measurement report, wherein the measurement report is used to provide the measurement results of the response end, the measurement results are distributed in the multiple measurement report frames, and the length of the corresponding measurement report frame in the multiple measurement report frames is not greater than a preset threshold.

Description

[0001] This application is a divisional application. The original application has the application number 202380103383.2 and the original application date is October 24, 2023. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This invention relates to the field of communication technology, and in particular to a communication method and related products. Background Technology

[0003] Ultra-wideband (UWB) technology is increasingly being used for indoor positioning and other positioning services, such as access control and asset location. In addition to dedicated equipment and tags, UWB radios are becoming increasingly common in high-end smartphones.

[0004] Beyond traditional ranging use cases, other use cases such as device-free sensing, downlink time difference of arrival (DL-TDOA), and long-distance ranging are under active investigation. UWB devices that support sensing are called sensing devices (SDEVs). Sensing involves using UWB transmissions to acquire measurements to estimate features such as distance, velocity, and motion of objects in a region of interest. Sensing measurements can enable various applications, such as presence detection and environment mapping.

[0005] The purpose of the background information is to illustrate information that the applicant believes may be relevant to this invention. It is neither necessary nor appropriate to acknowledge that any of the above information constitutes prior art in relation to this invention. Summary of the Invention

[0006] According to a first aspect, embodiments of the present invention provide a communication method applied to ultra-wideband sensing, and the method includes: The response end obtains multiple measurement report frames based on the measurement report. The measurement report is used to provide the measurement results of the response end. The measurement results are carried in a distributed manner in the multiple measurement report frames. The length of the corresponding measurement report frame in the multiple measurement report frames is not greater than a preset threshold.

[0007] Since the measurement results are carried in a distributed manner across multiple measurement report frames, and the length of the corresponding measurement report frame in the multiple measurement report frames is no greater than a preset threshold, this distribution of measurement reports across multiple measurement report frames can meet the length requirements of measurement report frames, thereby enabling the responding end to report the measurement results.

[0008] In one possible implementation of the first aspect, the method further includes: The responding end receives at least one sensing data packet from the initiating end; The responding end measures at least one sensing data packet to obtain a measurement report.

[0009] In one possible implementation of the first aspect, the method further includes: The responding end sends multiple measurement report frames to the initiating end.

[0010] In one possible implementation of the first aspect, the responding end obtains multiple measurement report frames based on the measurement report, including: The response end retrieves multiple parts of the measurement report based on the measurement report; For the first part of a multi-part report, the responding end performs fragmentation on the first part of the report to obtain a first number of fragments; The responding end acquires multiple measurement report frames based on the first number of fragments in the first part of the report.

[0011] By performing fragmentation at the partial report level, taking into account the boundaries of the partial report, more flexibility will be provided in the format design of the report IE used to implement this process.

[0012] In one possible implementation of the first aspect, the measurement report includes multiple partial reports, and a first partial report in the multiple partial reports is fragmented into a first number of fragments, each of the first number of fragments corresponding to: a first fragment field for indicating whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which the fragments are obtained; a remaining fragment field for indicating the number of remaining fragments in the report from which the fragments are obtained; and a fragment report length field for indicating the length associated with the fragment.

[0013] In one possible implementation of the first aspect, fragments from different parts of the report are carried in a single measurement report frame.

[0014] In one possible implementation of the first aspect, the method further includes: The response end compresses the second part of the report from the multiple part reports.

[0015] By compressing some or all of the reports, the overall signaling overhead is reduced.

[0016] In one possible implementation of the first aspect, a first measurement report frame corresponding to the first part report indicates a first parameter specific to the first part report. The first measurement report frame carries a first fragment of the first part report, and the indication of the first parameter is omitted in the remaining measurement report frames corresponding to the first part report other than the first measurement report frame.

[0017] In one possible implementation of the first aspect, the first measurement report frame includes a first parameter field for indicating a first parameter.

[0018] Since the first parameter specific to this part of the report is common to all acquired fragments, it can be carried only in the first measurement report frame corresponding to the first part of the report, and the indication of the first parameter can be omitted in other measurement report frames corresponding to the first part of the report, in order to reduce signaling overhead.

[0019] In one possible implementation of the first aspect, the responding end obtains multiple measurement report frames based on the measurement report, including: The responding end performs fragmentation on the measurement report to obtain a second number of fragments; The response end acquires multiple measurement report frames based on the second number of fragments.

[0020] By directly fragmenting the measurement report, the operation is simplified, and more flexibility will be provided for the format design of the report IE used to implement this process.

[0021] In one possible implementation of the first aspect, the measurement report is directly fragmented into a second number of fragments, each of which is carried in a measurement report frame. This measurement report frame includes: a first fragment field indicating whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which the fragments are obtained; a remaining fragment field indicating the number of remaining fragments in the report from which the fragments are obtained; and a fragment report length field indicating the length associated with the fragment.

[0022] In one possible implementation of the first aspect, the method further includes: The response end compresses the measurement report; The response end performs fragmentation on the measurement report, including: The response end performs fragmentation on the compressed measurement report.

[0023] In one possible implementation of the first aspect, the CIR bitmap field in the report parameter control field can also be compressed along with the measurement report.

[0024] In one possible implementation of the first aspect, a second measurement report frame among a plurality of measurement report frames indicates a second parameter reported in all parts of the measurement report, the second measurement report frame being the first measurement report frame among the plurality of measurement report frames, with the indication of the second parameter omitted in the remaining measurement report frames other than the second measurement report frame.

[0025] In one possible implementation of the first aspect, the second measurement report frame includes a second parameter field for indicating the second parameter.

[0026] In one possible implementation of the first aspect, the second measurement report frame also includes a parameter indication field for indicating whether the second parameter field exists.

[0027] The measurement report may include multiple partial reports. The second parameter may be a parameter common to all partial reports of the measurement report. That is, the second parameter is shared by multiple measurement report frames that carry all partial reports. Therefore, the second parameter may be carried only in the first measurement report frame among the multiple measurement report frames, and the indication of the second parameter may be omitted in other measurement report frames to reduce signaling overhead.

[0028] In one possible implementation of the first aspect, the corresponding measurement report frame indicates the number of taps carried in the corresponding measurement report frame, and the indicated number of taps is less than the total number of taps to be reported.

[0029] In one possible implementation of the first aspect, the corresponding measurement report frame includes a tap bitmap field, which indicates the number of taps carried in the corresponding measurement report frame. The bitmap indicated by the tap bitmap field is smaller than the bitmap required to indicate the total number of taps to be reported.

[0030] In one possible implementation of the first aspect, the corresponding measurement report frame indicates whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which fragments are obtained, the number of remaining fragments in the report from which fragments are obtained, and the length associated with the fragment.

[0031] In one possible implementation of the first aspect, the corresponding measurement report frame includes: a first fragment field for indicating whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which the fragments are obtained; a remaining fragment field for indicating the number of remaining fragments in the report from which the fragments are obtained; and a fragment report length field for indicating the length associated with the fragment.

[0032] When fragmenting at the partial report level considering the boundaries of partial reports, since the CIR taps included in a partial report can be distributed across multiple fragments, and it is possible that a measurement report frame corresponds to more than one fragment, each fragment included in the measurement report frame can be indicated by a first fragment field, a remaining fragment field, and a fragment report length field. This allows the initiator to identify fragments and arrange multiple fragments of the same partial report in the correct order. When fragmenting the measurement report directly without considering boundaries, each measurement report frame can include a first fragment field, a remaining fragment field, and a fragment report length field to indicate the fragments it carries.

[0033] In one possible implementation of the first aspect, the corresponding measurement report frame further includes: a fragmentation indication field for indicating the presence of a first fragmentation field, remaining fragmentation fields, and a fragmentation report length field.

[0034] Introducing an existence field allows for quick determination of the existence of the sharding indication field, the remaining sharding fields, and the sharding report length field, without needing to decode the values ​​carried in these actual fields.

[0035] In one possible implementation of the first aspect, the corresponding measurement report frame in the plurality of measurement report frames indicates the identifier and measurement of the corresponding measurement report frame.

[0036] In one possible implementation of the first aspect, the corresponding measurement report frame includes a report number for indicating the identifier of the measurement report frame and a measurement number for identifying the measurement.

[0037] Because the measurement report frame carries a report number and a measurement number to identify a partial report, it is possible to accurately identify the partial report corresponding to a specific receiving antenna and segment pair on a specific channel.

[0038] In one possible implementation of the first aspect, the corresponding measurement report frame also indicates: the segment to which the fragment of the measurement report carried by the corresponding measurement report frame belongs, the antenna for receiving the segment, and the channel on which the segment is received.

[0039] In one possible implementation of the first aspect, the corresponding measurement report frame includes: a fragment field for identifying the fragment to which the segment of the measurement report carried by the corresponding measurement report frame belongs; an antenna field for identifying the antenna of the responding end for receiving the fragment; and a channel field for identifying the channel on which the fragment is received.

[0040] Since the first measurement report frame can be divided into two or more partial reports, each carrying all CIR taps corresponding to the receive antenna and segment pairs on a specific channel, partial reports support dividing the measurement report into smaller components, each carrying a complete set of CIR taps for the receive antenna and segment pairs. Even if some components are not received, the remaining received components can still be parsed, thus supporting the acquisition of partial sensing measurements.

[0041] According to a second aspect, embodiments of the present invention provide a communication method applied to ultra-wideband sensing, and the method includes: The initiating end receives multiple measurement report frames from the responding end. These multiple measurement report frames are obtained based on measurement reports, which are used to provide the results of measurements performed by the responding end. The measurement results are distributed across the multiple measurement report frames, and the length of the corresponding measurement report frame in the multiple measurement report frames does not exceed a preset threshold.

[0042] In a third aspect, embodiments of the present invention provide a communication apparatus comprising various modules for performing communication methods according to the first aspect or any possible implementation thereof.

[0043] In a fourth aspect, embodiments of the present invention provide a communication apparatus comprising various modules for performing communication methods according to the second aspect or any possible implementation thereof.

[0044] In a fifth aspect, embodiments of the present invention provide a response terminal including processing circuitry for performing a communication method according to the first aspect or any possible implementation thereof.

[0045] In a sixth aspect, embodiments of the present invention provide an initiator that includes processing circuitry for performing a communication method according to the second aspect or any possible implementation thereof.

[0046] In a seventh aspect, embodiments of the present invention provide a communication system comprising a responding end according to the fifth aspect and an initiating end according to the sixth aspect.

[0047] In an eighth aspect, embodiments of the present invention provide a computer-readable medium storing computer-executable instructions, which, when executed by a processor, cause the processor to perform a communication method according to the first aspect or any possible implementation thereof, or according to the second aspect or any possible implementation thereof.

[0048] In a ninth aspect, embodiments of the present invention provide a computer program product including computer-executable instructions, which, when executed by a processor, cause the processor to perform a communication method according to the first aspect or any possible implementation thereof, or according to the second aspect or any possible implementation thereof.

[0049] According to the communication method provided in this application, the responding end obtains multiple measurement report frames based on the measurement report. The measurement report is used to provide the measurement results performed by the responding end. The measurement results are distributed across multiple measurement report frames, and the length of each corresponding measurement report frame in the multiple measurement report frames does not exceed a preset threshold. This distribution of the measurement report across multiple measurement report frames satisfies the length requirement of the measurement report frames, thereby enabling the responding end to report the measurement results. Attached Figure Description

[0050] The following figures illustrate exemplary embodiments of the present invention by way of example.

[0051] Figure 1 This is a simplified schematic diagram of a communication system according to one or more embodiments of the present invention.

[0052] Figure 2 This is a schematic diagram of an exemplary communication system according to one or more embodiments of the present invention.

[0053] Figure 3 This is a schematic diagram of the basic component structure of a communication system according to one or more embodiments of the present invention.

[0054] Figure 4 A block diagram of a device in a communication system according to one or more embodiments of the present invention is shown.

[0055] Figure 5 This is an interaction flowchart between the responding end and the initiating end according to one or more embodiments of the present invention.

[0056] Figure 6 This is a schematic diagram of a received report field according to one or more embodiments of the present invention.

[0057] Figure 7 This is a schematic flowchart of a communication method according to one or more embodiments of the present invention.

[0058] Figure 8 This is a schematic flowchart of a communication method according to one or more embodiments of the present invention.

[0059] Figure 9 This is a schematic flowchart of a communication method according to one or more embodiments of the present invention.

[0060] Figure 10 This is a schematic flowchart of a communication method according to one or more embodiments of the present invention.

[0061] Figure 11 This is a schematic flowchart of a communication method according to one or more embodiments of the present invention.

[0062] Figure 12 It is the format of a perception measurement report frame carrying a CIR report IE according to one or more embodiments of the present invention.

[0063] Figure 13 This is an exemplary format of the CIR report IE according to one or more embodiments of the present invention.

[0064] Figure 14This is an example of a segment of a received report according to one or more embodiments of the present invention.

[0065] Figures 15A to 15C This is an example of a segment of a received report according to one or more embodiments of the present invention.

[0066] Figure 16 This is an example of a segment of a received report according to one or more embodiments of the present invention.

[0067] Figure 17A and Figure 17B This is an example of a segment of a received report according to one or more embodiments of the present invention.

[0068] Figure 18 This is an example of a segment of a received report according to one or more embodiments of the present invention.

[0069] Figure 19 This is an example of a segment of a received report according to one or more embodiments of the present invention.

[0070] Figure 20 This is an exemplary format of the CIR report IE according to one or more embodiments of the present invention.

[0071] Figure 21 This is an example of a transmission-aware data packet according to one or more embodiments of the present invention.

[0072] Figure 22A and Figure 22B This is an example of a measurement report according to one or more embodiments of the present invention.

[0073] Figure 23A and Figure 23B This is an example of a measurement report according to one or more embodiments of the present invention.

[0074] Figure 24 This is an example of a transmission-aware data packet according to one or more embodiments of the present invention.

[0075] Figure 25 This is an example of an aggregated measurement report according to one or more embodiments of the present invention.

[0076] Figure 26 This is an exemplary format of the processed target feature IE according to one or more embodiments of the present invention.

[0077] Figure 27 This is an exemplary format of the CIR report IE according to one or more embodiments of the present invention.

[0078] Figure 28 This is an example of a segment of a received report according to one or more embodiments of the present invention.

[0079] Figure 29 A schematic structural diagram of a communication device according to one or more embodiments of the present invention is shown.

[0080] Figure 30 A schematic structural diagram of a communication device according to one or more embodiments of the present invention is shown. Detailed Implementation

[0081] To more clearly describe the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings required in the description of the embodiments or the prior art will be briefly introduced below.

[0082] In the following description, reference is made to the accompanying drawings, which form part of this invention, illustrating by way of description specific aspects of embodiments of the invention or aspects in which embodiments of the invention may be used. It will be understood that embodiments of the invention can be used in other aspects and include structural or logical variations not shown in the drawings. Therefore, the following detailed description is not intended to be limiting, and the scope of the invention is defined by the appended claims.

[0083] To aid in understanding the present invention, examples of wireless communication systems and devices are described below.

[0084] Exemplary communication systems and devices refer to Figure 1 A simplified schematic diagram of a communication system is provided as an illustrative example and not a limitation. Communication system 100 includes a radio access network 120. Radio access network 120 may be a next-generation (e.g., sixth-generation, 6G, or later) radio access network, or a traditional (e.g., 5G, 4G, 3G, or 2G) radio access network, or a WLAN (e.g., based on 802.11). In radio access network 120, one or more communication electronic devices (EDs) 110a to 110j (generally referred to as 110) may be interconnected with each other or connected to one or more network nodes (170a, 170b, generally referred to as 170). One or more EDs 110a to 110j also include a UWB module and are capable of performing ambient awareness using UWB signals. Core network 130 may be part of the communication system and may depend on or be independent of the radio access technology used in communication system 100. In addition, the communication system 100 includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0085] Figure 2An exemplary communication system 100 is illustrated. Typically, communication system 100 enables multiple wireless or wired components to transmit data and other content. The purpose of communication system 100 may be to provide content, such as voice, data, video, and / or text, via broadcast, multicast, and unicast. Communication system 100 can operate by sharing resources (e.g., carrier spectrum bandwidth) among its constituent components. Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery, and mobility). Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can enable heterogeneous networks comprising multiple layers. Compared to traditional communication networks, heterogeneous networks can achieve better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks. In its simplest form, the communication system 100 may even be a single ED capable of performing single static sensing of the surrounding environment, or a pair of EDs capable of participating in dual static sensing of the surrounding environment, or three or more EDs capable of participating in multi-static sensing of the surrounding environment.

[0086] Terrestrial and non-terrestrial communication systems can be considered subsystems of a communication system. In the example shown, communication system 100 includes electronic devices (EDs) 110a to 110d (typically referred to as ED 110), radio access networks (RANs) 120a and 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RANs 120a and 120b include corresponding base stations (BSs) 170a and 170b, which are typically referred to as terrestrial transmit and receive points (T-TRPs) 170a and 170b. The non-terrestrial communication network 120c includes access nodes 120c, which are typically referred to as non-terrestrial transmit and receive points (NT-TRPs) 172.

[0087] Alternatively or additionally, any ED 110 can be used to access, connect to, or communicate with any other T-TRP 170a and 170b and NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can perform uplink and / or downlink transmissions with T-TRP 170a via interface 190a. In some examples, ED 110a, 110b, and 110d can also communicate directly with each other via one or more sidelink air interfaces 190b. In some examples, ED 110d can perform uplink and / or downlink transmissions with NT-TRP 172 via interface 190c.

[0088] Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA). Air interfaces 190a and 190b can use other higher-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0089] The 190c air interface enables communication between the ED 110d and one or more NT-TRP172s via a wireless link (or simply a link). In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs and one or more NT-TRPs for multicast transmission.

[0090] Air interface 190a, 190b and 190c can also use UWB technology to perform ambient perception using UWB signals.

[0091] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b and / or core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may (or may not) be directly served by core network 130 and may (or may not) employ the same radio access technology as RANs 120a, RAN 120b, or both. Core network 130 may also serve as a gateway access between (i) RANs 120a and 120b, or EDs 110a, 110b, and 110c, or both, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Furthermore, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or other than wireless communication), ED 110a, 110b, and 110c can also communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include computer networks and / or subnets (internal networks) and include protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating according to various wireless access technologies and include multiple transceivers required to support these technologies.

[0092] Basic component structure Figure 3Another example of an ED 110 and base stations 170a, 170b, and / or 170c is shown. The ED 110 is used to connect people, things, machines, etc. The ED 110 can be widely used in various scenarios, such as cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility.

[0093] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include (or be referred to as) devices such as: user equipment (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics device, smartbook, vehicle, automobile, truck, bus, train, or IoT device, industrial equipment, or devices within the aforementioned equipment (e.g., communication modules, modems, or chips). Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs and are referred to hereinafter as T-TRP 170. Also... Figure 3 As shown, NT-TRP is referred to as NT-TRP 172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically enabled (i.e., established, activated, or enabled), disabled (i.e., released, deactivated, or disabled), and / or configured in response to one or more of the following: connectivity availability and connectivity necessity.

[0094] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown. Alternatively, one, some, or all of the antennas may be panels. For example, the transmitter 201 and receiver 203 may be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals.

[0095] ED 110 includes at least one memory 208. Memory 208 stores instructions and data used, generated, or acquired by ED 110. For example, memory 208 may store software instructions or modules executed by one or more processing units 210, which are used to implement some or all of the functions and / or embodiments described herein. Each memory 208 includes one or more of any suitable volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, processor cache, etc.

[0096] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g. Figure 1 (Wired interface of Internet 150 in the network). Input / output devices can interact with users or other devices on the network. Each input / output device includes any suitable structure for providing or receiving information from the user, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communication.

[0097] ED 110 also includes a processor 210 for performing operations including: operations related to preparing uplink transmissions to NT-TRP 172 and / or T-TRP 170; operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170; and operations related to processing sidelink transmissions to and from another ED 110. Processing operations related to preparing uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. According to an embodiment, receiver 203 may receive downlink transmissions (possibly using receive beamforming), and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction indications (e.g., beam angle information (BAI)) received from T-TRP 170. In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and acquiring system information. In some embodiments, processor 210 may perform channel estimation using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0098] Although not shown, processor 210 may form part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may form part of processor 210.

[0099] Processor 210, as well as the processing components of transmitter 201 and receiver 203, may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 208). Alternatively, some or all of the processing components of processor 210, as well as transmitter 201 and receiver 203, may be implemented using dedicated circuitry, such as a programmable field-programmable gate array (FPGA), a graphics processing unit (GPU), or an application-specific integrated circuit (ASIC).

[0100] In some implementations, the T-TRP 170 can be called by other names, such as base station, base-transceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, Node B, evolved NodeB (eNodeB or eNB), home eNodeB, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, remote radio head, ground node, ground network device, ground base station, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The T-TRP 170 can be a macro BS, micro BS, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned equipment or a device within the aforementioned equipment (e.g., a communication module, modem, or chip).

[0101] In some embodiments, portions of T-TRP 170 may be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna of T-TRP 170 and may be coupled to the device housing the antenna via a communication link (not shown), sometimes referred to as the fronthaul, such as the Common Public Radio Interface (CPRI). Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding, and are not necessarily part of the device housing the antenna of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs that work together, for example, through coordinated multicast transmissions, to serve ED 110.

[0102] T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown. Alternatively, one, some, or all of the antennas may be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. T-TRP 170 also includes a processor 260 for performing operations, including operations related to: preparing transmissions for downlink transmission to ED 110; processing uplink transmissions received from ED 110; preparing transmissions for backhaul transmission to NT-TRP 172; and processing transmissions received from NT-TRP 172 via backhaul. Processing operations related to preparing transmissions for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via backhaul may include operations such as receive beamforming, demodulation, and decoding received symbols. Processor 260 can also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB), generating system information, etc. In some embodiments, processor 260 also generates beam direction indications, such as a BAI, which can be scheduled by scheduler 253 for transmission. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining where to deploy NT-TRP 172, etc. In some embodiments, processor 260 can generate signaling, for example, to configure one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252. It should be noted that the term "signaling" as used herein may alternatively be referred to as control signaling. Dynamic signaling can be transmitted in the control channel (e.g., the physical downlink control channel, PDCCH), while static or semi-static higher-layer signaling can be included in data packets transmitted in the data channel (e.g., the physical downlink shared channel, PDSCH).

[0103] Scheduler 253 may be coupled to processor 260. Scheduler 253 may be included within or operate separately from T-TRP 170, and may schedule uplink, downlink, and / or backhaul transmissions, including issuing scheduling authorizations and / or configuring schedule-free (“configured authorizations”) resources. T-TRP 170 also includes memory 258 for storing information and data. Memory 258 stores instructions and data used, generated, or acquired by T-TRP 170. For example, memory 258 may store software instructions or modules executed by processor 260 for implementing some or all of the functions and / or embodiments described herein.

[0104] Although not shown, processor 260 may form part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may form part of processor 260.

[0105] The processor 260, scheduler 253, and processing components of transmitter 252 and receiver 254 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processor 260, scheduler 253, and processing components of transmitter 252 and receiver 254 may be implemented using dedicated circuitry (e.g., FPGA, GPU, or ASIC).

[0106] Although the NT-TRP 172 is shown as an example of a drone only, it can be implemented in any suitable non-terrestrial form. Furthermore, the NT-TRP 172 may be referred to by other names in some implementations, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown. Alternatively, one, some, or all of the antennas may be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 also includes a processor 276 for performing operations, including operations related to: preparing transmissions for downlink transmissions to ED 110; processing uplink transmissions received from ED 110; preparing transmissions for backhaul transmissions to T-TRP 170; and processing transmissions received from T-TRP 170 via backhaul. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or received via backhaul may include operations such as receive beamforming, demodulation, and decoding of received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-level functions such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is only an example, more generally, NT-TRP 172 may implement higher-level functions in addition to physical layer processing.

[0107] The NT-TRP 172 also includes a memory 278 for storing information and data. Although not shown, a processor 276 may form part of the transmitter 272 and / or receiver 274. Although not shown, the memory 278 may form part of the processor 276.

[0108] Processor 276, and the processing components of transmitter 272 and receiver 274, may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processing components of processor 276, transmitter 272, and receiver 274 may be implemented using dedicated circuitry (e.g., a programmable FPGA, GPU, or ASIC). In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs that work together, for example, through coordinated multicast transmissions, to serve ED 110.

[0109] T-TRP 170, NT-TRP 172 and / or ED 110 may include other components, but for clarity these components are omitted.

[0110] Basic module structure according to Figure 4 One or more steps of the methods in the various embodiments provided herein can be performed by the corresponding units or modules. Figure 4 The diagram illustrates units or modules within a device, such as those in ED 110, T-TRP 170, or NT-TRP 172. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by artificial intelligence (AI) or machine learning (ML) modules. The respective units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of the units or modules may be integrated circuits, such as a programmable FPGA, GPU, or ASIC. It should be understood that if the aforementioned modules are implemented using software executed by a processor, etc., these modules may be retrieved by the processor, wholly or partially, individually or collectively, for processing, or in one or more instances as needed, and these modules themselves may include instructions for further deployment and instantiation.

[0111] Additional details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, for clarity, these details are omitted herein.

[0112] empty An air interface typically includes multiple components and associated parameters that collectively specify how transmissions are sent and / or received over a wireless communication link between two or more communication devices. For example, an air interface may include one or more waveforms, one or more frame structures, one or more multiple access schemes, one or more protocols, one or more coding schemes, and / or one or more modulation schemes defining the transmission of information (e.g., data) over the wireless communication link. The wireless communication link may support links between a radio access network and user equipment (e.g., a "Uu" link), and / or wireless communication links may support links between devices, such as links between two user equipment (e.g., a "sidelink"), and / or wireless communication links may support links between a non-terrestrial (NT) communication network and user equipment (UE). The air interface may also utilize UWB technology to perform ambient awareness using UWB signals.

[0113] Below are some examples of the components mentioned above: Waveform components can specify the shape and form of the signal being transmitted. Waveform options can include orthogonal multiple access (OFDM) and non-orthogonal multiple access (NOA) waveforms. Non-limiting examples of such waveform options include orthogonal frequency division multiplexing (OFDM), filtered OFDM (f-OFDM), time-windowed OFDM, filter bank multicarrier (FBMC), universal filtered multicarrier (UFMC), generalized frequency division multiplexing (GFDM), wavelet packet modulation (WPM), faster than Nyquist (FTN) waveforms, high-rate pulse repetition frequency (HRP) UWB waveforms, low-rate pulse repetition frequency (LRP) UWB waveforms, and low peak-to-average power ratio (PAPR) waveforms (low PAPR WF).

[0114] The frame structure component can specify the configuration of a frame or frame group. The frame structure component can indicate one or more of the following parameters: time, frequency, pilot signature, code, or other parameters for a frame or frame group. Further details about the frame structure will be discussed below.

[0115] Multiple access scheme components can specify multiple access technology options, including technologies that define how communication devices share the common physical channel, such as: time division multiple access (TDMA), frequency division multiple access (FDMA), code division multiple access (CDMA), single carrier frequency division multiple access (SC-FDMA), low density signature multicarrier code division multiple access (LDS-MC-CDMA), non-orthogonal multiple access (NOMA), pattern division multiple access (PDMA), lattice partition multiple access (LPMA), resource spread multiple access (RSMA), and sparse code multiple access (SCMA). In addition, multiple access technology options may include: scheduled access and unscheduled access, also known as unlicensed access; non-orthogonal multiple access and orthogonal multiple access, for example, through dedicated channel resources (e.g., not shared between multiple communication devices); contention-based shared channel resources and non-contention-based shared channel resources; and cognitive radio-based access.

[0116] The Hybrid Automatic Repeat Request (HARQ) protocol component can specify how transmissions and / or retransmissions are performed. Non-limiting examples of transmission and / or retransmission mechanism options include specifying the scheduled data pipeline size, the signaling mechanisms used for transmission and / or retransmission, and the specific mechanism options for the retransmission mechanism.

[0117] The coding and modulation components specify how the transmitted information can be encoded / decoded and modulated / demodulated for transmission / reception. Encoding can refer to methods of error detection and forward error correction. Non-limiting examples of coding options include turbine trellis codes, turbine product codes, fountain codes, low-density parity-check codes, and polar codes. Modulation can simply refer to constellations (including, for example, modulation techniques and orders), or more specifically to various types of advanced modulation methods, such as layered modulation and low PAPR modulation.

[0118] In some embodiments, the air interface can be a "one-size-fits-all" concept. For example, once the air interface is defined, the components within it cannot be changed or adapted. In some implementations, only a limited number of parameters or modes of the air interface can be configured, such as cyclic prefix (CP) length or multiple input multiple output (MIMO) mode. In some embodiments, the air interface design can provide a uniform or flexible framework to support frequency bands below and above 6 GHz (e.g., millimeter wave) for both licensed and unlicensed access. For example, the flexibility of a configurable air interface provided by scalable system parameters and symbol duration can support optimized transmission parameters for different spectrum bands and different services / devices. As another example, a uniform air interface can be self-contained in the frequency domain, and a frequency-domain self-contained design can support more flexible radio access network (RAN) slicing by sharing channel resources between different services in both frequency and time.

[0119] Terminal type The data processing method provided in this invention can be applied to various communication scenarios, such as one or more of the following: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine-type communication (MTC), Internet of Things (IoT), narrowband Internet of Things (NB-IoT), customer front-end equipment (CPE), augmented reality (AR), virtual reality (VR), mass machine-type communications (mMTC), device-to-device (D2D), vehicle-to-everything (V2X), and vehicle-to-vehicle (V2V).

[0120] It should be noted that, in this embodiment of the invention, the Internet of Things (IoT) may include one or more of NB-IoT, MTC, mMTC, etc. This is not a limitation.

[0121] eMBB can be a high-bandwidth mobile broadband service, such as three-dimensional (3D) or ultra-high-definition video. Specifically, eMBB can also improve network speed, user experience, and other performance aspects based on mobile broadband services. For example, when a user watches 4K HD video, the peak network speed can reach 10 Gbit / s.

[0122] URLLC can refer to services with high reliability, low latency, and extremely high availability. Specifically, URLLC can include the following communication scenarios and applications: industrial applications and control, traffic safety and control, remote manufacturing, remote training, remote surgery, autonomous driving, industrial automation, and the security industry.

[0123] MTC can refer to low-cost, enhanced-coverage services, also known as M2M, while mMTC refers to large-scale IoT services.

[0124] NB-IoT can be a service characterized by wide coverage, massive connectivity, low data rate, low cost, low power consumption, and excellent architecture. Specifically, NB-IoT can include smart water meters, smart parking, smart pet tracking, smart bicycles, smart smoke detectors, smart toilets, smart vending machines, and more.

[0125] CPE can refer to a mobile signal access device that receives mobile signals and forwards them via Wireless Fidelity (WiFi) signals, or it can refer to a device that converts high-speed 4G or 5G signals into WiFi signals, and can simultaneously support a relatively large number of mobile terminals accessing the Internet. CPEs can be widely used in rural areas, towns, hospitals, workplaces, factories, and residential communities for wireless network access, reducing the cost of wired network deployment.

[0126] V2X enables communication between vehicles, between vehicles and network devices, and between network devices to obtain a range of traffic information, such as real-time traffic conditions, road information, and pedestrian information, and to provide in-vehicle entertainment information, thereby improving driving safety, reducing congestion, and increasing traffic efficiency.

[0127] For example, terminal types include eMBB devices, URLLC devices, NB-IoT devices, and CPE devices. eMBB devices are primarily used for transmitting large data packets, but can also be used for small data packets, and are typically in a mobile state. The requirements for transmission latency and reliability are universal, and both uplink and downlink communication are present. The channel environment is relatively complex and variable, allowing for both indoor and outdoor communication. For example, an eMBB device could be a mobile phone. URLLC devices are primarily used for transmitting small data packets, but can also transmit medium-sized data packets. Typically, URLLC devices are stationary, but can also move along fixed routes. URLLC devices have high requirements for transmission latency and reliability, meaning they require low latency, high reliability, and both uplink and downlink communication. The channel environment is stable. For example, a URLLC device could be factory equipment. NB-IoT devices are primarily used for transmitting small data. NB-IoT devices are typically stationary, their location is known, their transmission latency and reliability requirements are moderate, their uplink traffic is relatively large, and the channel environment is relatively stable. For example, an NB-IoT device could be a smart water meter or a sensor. CPE devices are primarily used for transmitting large data packets. They are typically in a stationary state or can move over very short distances. They have moderate requirements for transmission latency and reliability, and support both uplink and downlink communication in a relatively stable channel environment. Examples of CPE devices include smart home terminal devices, AR / VR devices, etc. When determining the terminal type, factors such as the device's service type, mobility, transmission latency requirements, reliability requirements, channel environment, and communication scenario can be considered. The terminal type corresponding to the device can be eMBB, URLLC, NB-IoT, or CPE.

[0128] As described in related technologies, ultra-wideband (UWB) technology is increasingly being used for indoor positioning and other location services, such as access control and asset location. In addition to dedicated equipment and tags, UWB radios are becoming increasingly common in high-end smartphones.

[0129] Beyond traditional ranging use cases, other use cases such as device-free sensing, downlink time difference of arrival (DL-TDOA), and long-distance ranging are under active investigation. UWB devices that support sensing are called sensing devices (SDEVs). Sensing involves using UWB transmissions to acquire measurements to estimate features such as distance, velocity, and motion of objects in a region of interest. Sensing measurements can enable various applications, such as presence detection and environment mapping.

[0130] Based on the role of the SDEV during perception measurement, the SDEV can assume any one or more of the following roles: Aware Initiator: The SDEV that initiates a awareness session with other SDEVs, also known as the initiator. The awareness session can start from the time the initiator sends a session establishment request message and end when it receives reports from all measurement instances from the responder. The awareness session can include one or more awareness measurement instances. A measurement instance is represented by one or more measurements performed for a purpose. For example, in order to measure the channel conditions of one or more channels, the initiator will send one or more channel probe PHY protocol data units (PPDUs) to the responder, and the responder can measure one or more PPDUs (e.g., measure one or more fragments of each PPDU) and report the results of one or more measurements. Such one or more measurements will be regarded as a measurement instance. Controller: The SDEV that controls the perception session and defines the perception parameters.

[0131] Subject: SDEV using perception parameters received from the controller.

[0132] Perception Response End: The SDEV that participates in the perception session initiated by the initiator, also known as the response end; Sensing sender: The SDEV that sends the channel sounding PHY PPDU used to perform sensing measurements, also known as the sender, is the channel sounding PPDU that can also be called a sensing PPDU or sensing data packet, which includes one or more segments; Sensing Receiver: The SDEV that receives the Channel Probe PPDU and performs sensing measurements is also called the receiver; Perception Request Device: An SDEV that requests another SDEV to perform perception measurements in a proxy application.

[0133] The initiating end can be either the sender or the receiver. When the initiating end is the sender, the responding end is the receiver, and vice versa. In the following description, the technical solution of this application will be illustrated using the example of the initiating end being the sender and the responding end being the receiver. However, it should be understood that the solution of this application is also applicable to the case where the initiating end is the receiver and the responding end is the sender.

[0134] In most sensing scenarios, the sensing application runs on the initiating end. When the initiating end is the sensing sender and sends sensing data packets (e.g., PPDUs) to the responding end, the responding end (sensing receiver) can send an over-the-air (OTA) sensing measurement report to the initiating end, including one or more (sensing) measurement report frames carrying the sensing measurement results. Two types of sensing measurement reports are supported, as follows.

[0135] (1) Windows-based channel impulse response (CIR) report The perception measurement report includes CIR taps measured within a specific time window.

[0136] (2) Processed target feature report The perception measurement report carries process reports used for perception, such as angle of arrival (AoA), distance, velocity, radar cross section (RCS), etc.

[0137] For sensing applications, using a wider channel bandwidth is beneficial for improving the sensing link budget and the accuracy of sensing measurements. Channel aggregation schemes (called frequency stitching) support combining multiple carrier frequencies, thereby enabling sensing measurements to be performed on a wider channel bandwidth than the default operating channel bandwidth of SDEV. Frequency stitching can be performed using overlapping or non-overlapping channel frequencies, with the carrier frequency grid configuration parameters determining the percentage of overlap. Carrier frequency grids 0, 1, 2, and 3 represent no overlap, 25% overlap, 50% overlap, and 75% overlap, respectively. The frequency stitching type refers to the method used to transmit channel sounding PPDUs (sensing PPDUs), which can be one of the following: Intra-packet frequency splicing: Different segments of the same sensing PPDU are transmitted on different channels; this segment can also be called a sensing segment. Inter-packet frequency splicing: Multiple sensing PPDUs are transmitted on different channels, and different segments of the same sensing PPDU are transmitted on the same channel; Intra-packet frequency splicing and inter-packet frequency splicing: a combination of the two transmission methods mentioned above.

[0138] Other terms related to frequency splicing: The basic channel refers to the initial channel for performing UWB sensing when starting frequency splicing. The initial channel is the channel in which fields such as the synchronization (SYNC) field and the start of frame delimiter (SFD) field are transmitted first. The number of transmissions refers to the total number of transmissions performed at different channel center frequencies for a given measurement instance. In other words, the number of transmissions refers to the number of carrier frequencies used for frequency stitching.

[0139] The following will combine Figure 5 Describes the process of a sensing measurement instance between the initiating and responding ends. For example... Figure 5 As shown, during the session establishment phase, the SDEV can be viewed as the controller, assuming itself as the initiator, and identifying another SDEV (such as...). Figure 5 The controlled party (shown as the "controlled party") is the responder, meaning the controller assumes the role of the initiator and assigns the role of the responder to the controlled party. The initiator first sends a sensing session establishment request message to the responder to initiate a sensing session. This message includes the initiator's sensing capabilities and an AC information element (IE) carrying parameters related to sensing and frequency stitching. The responder responds with a sensing session establishment response message carrying its sensing capabilities and operating parameters. This session establishment phase is essentially a handshake between the controller and the controlled party, allowing both parties to understand each other's capabilities and enabling subsequent sensing. Subsequently, in the sensing round (one sensing data packet transmission and measurement), the initiator sends a sensing data packet with four segments, each segment transmitted on one of four different carrier frequencies specified by the frequency stitching carrier frequency grid parameters (which can be notified by the initiator as one of the frequency stitching parameters). Upon receiving the sensing data packet, the responder performs CIR tap measurements on each bit set to 1 in the CIR bitmap field of the AC IE. For each pair consisting of segments of sensing data packets from the receiving antenna of the responding end and each frequency splicing channel, a partial CIR report is generated. In this example, the feedback control field of the AC IE is set to a value of 1, indicating all reports transmitted since the last transmission, and four sensing measurement report frames are sent, each carrying a partial CIR report corresponding to a segment. The responding end then sends four measurement report frames corresponding to the fourth sensing data packet, respectively. It should be noted that the number of segments shown in the figure is only exemplary; in actual applications, there may be more or fewer segments.

[0140] As described above, the response end typically uses two types of reports to implement the perception report frame, such as... Figure 5 As shown below, the relevant frame structure can be described using the CIR report as an example. It is recommended to include the CIR taps corresponding to the sensing measurements in the CIR report IE, and the CIR report IE in the measurement report frame. The CIR taps are measured for each pair of segments transmitted by the receiving antenna at the responding end and the segment at the initiating end, and are placed in the receive report field of the CIR report IE in a fixed order (e.g., antenna ID first, segment index last). For example, when there are two Rx antennas and two segments, the format of the measurement report frame is as follows: Figure 6 As shown.

[0141] The CIR report format described above may work well when carrying all CIR taps corresponding to a single sensing measurement within the same CIR report IE. However, it's possible that CIR taps are split across multiple CIR report IEs and multiple frames, making it difficult for the initiator to assemble the CIR taps in the correct order. A typical frame may only carry a payload of less than 1000 octets; therefore, when the size of the CIR report exceeds the frame capacity, it is necessary to employ a CIR report format that supports splitting the CIR report across multiple CIR report IEs and multiple frames.

[0142] The proposed solution is to introduce a fragmentation scheme for the sensing measurement report to support: allocating partial reports corresponding to the same sensing measurement instance across multiple CIR report IEs and / or frames; and fragmenting the report when the frame carrying the sensing measurement report is insufficient to carry the entire sensing measurement report (CIR tap). Here, in this embodiment of the invention, a partial report (or CIR partial report) refers to a report carrying all CIR taps corresponding to the receive antenna and segment pairs or the receive antenna and segment pairs on a specific channel. Typically, partial reports are carried in the receive report field of the CIR report IE.

[0143] In one possible implementation of the invention, a partial report corresponds to a first reporting set of fragments of the at least one sensing data packet sent from the initiating end to the responding end (as described with reference to step S701, for the purpose of channel measurement) and the antenna at the responding end for receiving the fragments. This first reporting set can also be referred to as a combination, pair, or group of fragments of at least one sensing data packet and the antenna at the responding end for receiving the fragments. That is, each partial report carries all CIR taps corresponding to the receiving antenna and fragment pair. For example, when at least one sensing data packet includes one sensing data packet, and that sensing data packet includes two fragments (SEG1 and SEG2), and the responding end has two receiving antennas (ANT1 and ANT2), then there will be four partial reports (PR1, PR2, PR3, and PR4), each partial report corresponding to a segment and antenna pair, wherein PR1 corresponds to the set of SEG1 and ANT1, PR2 corresponds to the set of SEG2 and ANT1, PR3 corresponds to the set of SEG1 and ANT2, and PR4 corresponds to the set of SEG2 and ANT2.

[0144] In one possible implementation of the invention, a partial report corresponds to a second reporting set of at least one segment of a sense data packet, an antenna at the responding end for receiving the segment, and a first channel on which the initiating end transmits the segment. This second reporting set may also be referred to as a combination, pair, or group of at least one segment of a sense data packet, an antenna at the responding end for receiving the segment (or a corresponding receive (RX) chain), and a first channel on which the initiating end transmits the segment. That is, each partial report carries all CIR taps corresponding to the receive antenna and segment pair on a specific channel. For example, when at least one sensing data packet includes a sensing data packet comprising two segments (SEG1 and SEG2) and transmitted on a channel (CH1), and the responding end has two receiving antennas (ANT1 and ANT2), then there will be four part reports (PR1', PR2', PR3', and PR4'), each part reporting the corresponding segment and antenna pair, where PR1' corresponds to the set of SEG1, ANT1, and CH1, PR2 corresponds to the set of SEG2, ANT1, and CH1, PR3 corresponds to the set of SEG1, ANT2, and CH1, and PR4 corresponds to the set of SEG2, ANT2, and CH1.

[0145] At the first level, fragmentation of received reports can be performed at the partial report level. That is, all CIR reports (CIR taps) corresponding to a single sensing measurement (measurement instance) can be divided into two or more partial CIR reports, each carrying all CIR taps corresponding to the received antenna and segment pairs (on a specific channel).

[0146] At the second level, further fragmentation can be performed on the partial report. That is, a partial CIR report can be divided into two or more CIR report fragments, each fragment carrying a limited number of CIR taps corresponding to the receive antenna and segment pair (on a specific channel).

[0147] Fragmentation can also be performed in other ways, such as directly fragmenting the measurement report without first dividing the measurement report into partial reports.

[0148] To reduce the size of the received report carrying all CIR reports (CIR taps) corresponding to a single sensing measurement (measurement instance), a portion of the CIR report can be compressed before fragmentation, with each fragment carrying a portion of the compressed CIR report.

[0149] The solution proposed in this invention can be applied to any UWB sensing application that uses (sensing) measurement report frames. Furthermore, the solution can be implemented in tags, smartphones, laptops, remote keys, vehicles, door locks, etc. That is, the initiating and responding ends can be devices such as tags, smartphones, laptops, remote keys, vehicles, and door locks.

[0150] Embodiments of the present invention will be described in detail with reference to the accompanying drawings. The present invention provides a communication method applied to ultra-wideband sensing. (Refer to...) Figure 7 The communication method may include the following steps.

[0151] S701: The response end obtains multiple measurement report frames based on the measurement report. The measurement report is used to provide the measurement results performed by the response end. The measurement results are carried in a distributed manner in the multiple measurement report frames. The length of the corresponding measurement report frame in the multiple measurement report frames is not greater than a preset threshold.

[0152] Here, "measurement" refers to the measurement instance mentioned above, and "measurement result" refers to all measurement results obtained in the measurement, such as all received reports of a measurement instance.

[0153] The responding end can perform measurements to complete a sensing task, such as measuring the conditions of some channels. In one possible implementation, measurements can be performed by measuring one or more sensing data packets received from the initiating end. In this case, after receiving one or more sensing data packets (at least one sensing data packet) from the initiating end, the responding end can obtain multiple measurement report frames based on one or more sensing data packets. For example, the responding end can use one or more of its receiving antennas to measure the CIR tap of each segment of one or more sensing data packets to obtain a measurement report carrying all measurement results for a measurement instance, such as the results obtained by measuring all or more sensing data packets received from the initiating end for completing the same sensing task, or all reception reports carried in the aforementioned "reception report" field. In this case, the measurement can include the transmission and measurement of one or more sensing data packets. This will be described in detail later with specific examples. Each sensing data packet in at least one sensing data packet can include one or more segments. The sensing data packets will be segmented using relevant techniques in the prior art. The embodiments of the present invention do not limit the number of segments of the sensing data packets or the method of segmenting the sensing data packets. For example, a segment can be the SENS field of an HRP-SDEV PPDU.

[0154] It should be noted that the aforementioned sensing data packet can be any data packet that can be exchanged between the initiating end and the responding end to measure channel conditions. In a possible implementation of the present invention, the sensing data packet can be a sensing PPDU (e.g., an HRP-SDEV PPDU), which is sent from the initiating end to the responding end through one or more channels. It should also be noted that the number of sensing data packets can be one or more, and the embodiments of the present invention do not limit this. The number of sensing data packets can be determined based on actual needs. For example, when multiple channels need to be measured, this requirement can be achieved by having one sensing data packet include multiple segments or multiple sensing data packets (each first sensing data packet may include one or more segments).

[0155] After performing the measurement, the responding end can obtain a measurement report. To provide this report to the initiating end, the responding end can use multiple measurement report frames. That is, the obtained measurement report can be fragmented to ensure that each measurement report frame carrying one or more fragments meets the length requirement; that is, the length of each measurement report frame does not exceed a preset threshold. The number of multiple measurement report frames can be determined based on the sensing task; if the size of the obtained measurement report is large, more measurement report frames may be needed. This fragmentation can be performed in various ways, at the partial report level or at a finer granularity. For example, as mentioned above, the measurement result can include multiple partial reports, so fragmentation can be performed at the partial report level; that is, all received reports can be divided according to partial reports. Furthermore, fragmentation can be performed on the partial reports further. Specific examples will be provided later in detail.

[0156] In one possible implementation, the preset threshold can be 1000 octets, representing the payload limit of the measurement report frame. In another implementation, the preset threshold may not be a fixed number, but can be determined based on the number of payload octets that the report frame can carry (after taking into account the overhead of MAC frame header, IE frame header, FCS field, etc.).

[0157] In one possible implementation of the present invention, after the responding end acquires multiple measurement report frames, the method further includes: the responding end sending multiple measurement report frames to the initiating end.

[0158] According to the communication method provided in this application, the responding end obtains multiple measurement report frames based on the measurement report. The measurement report is used to provide the measurement results performed by the responding end. The measurement results are distributed across multiple measurement report frames, and the length of each corresponding measurement report frame in the multiple measurement report frames does not exceed a preset threshold. This distribution of the measurement report across multiple measurement report frames satisfies the length requirement of the measurement report frames, thereby enabling the responding end to report the measurement results.

[0159] Fragmentation can be performed in two different ways: one is to obtain a portion of the measurement report and then fragment it considering the boundaries of that portion; the other is to directly fragment the measurement report without considering the boundaries of the portion. When fragmenting a portion of the report, the CIR report IE will also have different formats. These will be explained in detail below with relevant diagrams.

[0160] One approach is to fragment the measurement report into portions. Figure 7 Based on the communication method shown, Figure 8 This is a schematic flowchart of a communication method according to another embodiment of the present invention. Figure 8 As shown, the method includes: S801: The response end obtains multiple parts of the measurement report based on the measurement report; S802: For the first part of a report in multiple partial reports, the responding end performs fragmentation on the first part of the report to obtain a first number of fragments; S803: The responding end acquires multiple measurement report frames based on the first number of fragments in the first part of the report.

[0161] As mentioned above, multiple measurement report frames can be obtained by performing fragmentation at a partial report level, such as... Figure 8 As shown, the first part of the report can be one or more, and this embodiment of the application does not limit this. That is, by considering the boundaries of the partial reports, some or all of the partial reports included in the measurement report (carried in the received report field shown in the following example) can be fragmented.

[0162] It should be noted that although the examples in this invention are given by performing fragmentation on all partial reports, this approach is also applicable to cases where fragmentation is performed on one or some of the partial reports.

[0163] Furthermore, the specific value of the first quantity here can be determined based on actual needs, and this application embodiment does not limit it in this regard. When multiple partial reports are fragmented, that is, when multiple partial reports are all the aforementioned "first partial reports", the first quantity of each partial report in the multiple partial reports can be the same or different, and this application embodiment does not limit it in this regard.

[0164] In one possible implementation of the first aspect, the measurement report includes multiple partial reports. A first partial report among the multiple partial reports is fragmented into a first number of fragments. Each fragment in the first number of fragments corresponds to: a first fragment field, indicating whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which fragments are obtained; a remaining fragment field, indicating the number of remaining fragments in the report from which fragments are obtained; and a fragment report length field, indicating the length associated with the fragment. Here, the first fragment field can be implemented as a first report fragment field in the following examples, the remaining fragment field can be implemented as a remaining report fragment field in the following examples, and the fragment report length field can be implemented as a partial report length field in the following examples.

[0165] In one possible implementation of the invention, fragments from different partial reports are carried in a single measurement report frame. For fragmented partial reports, each partial report can be divided into multiple fragments, and fragments from different partial reports can be merged and carried into a single measurement report frame, thereby reducing the number of measurement report frames and thus reducing overall signaling overhead.

[0166] By performing fragmentation at the partial report level, taking into account the boundaries of the partial report, more flexibility will be provided in the format design of the report IE used to implement this process.

[0167] exist Figure 8 Based on the communication method shown, Figure 9 This is a schematic flowchart of a communication method according to another embodiment of the present invention, wherein a portion of the report is compressed. Figure 9 As shown, the method includes: S901: The response end obtains multiple parts of the measurement report based on the measurement report; S902: The responding end performs compression on the second part of the report in the multiple part reports; S903: For the first part of a report in a multi-part report, the responding end performs fragmentation on the first part of the report to obtain a first number of fragments; S904: The response end acquires multiple measurement report frames.

[0168] In the above embodiments, the second part report may be the same as or different from the first part report, and the execution order of steps 902 and 903 is not limited herein. That is, in multiple part reports, some or all of the multiple part reports can be used as one or more first part reports to be fragmented, and some or all of the multiple part reports can be used as one or more second part reports to be compressed. Fragmentation and compression operations can be independent of each other. It should be noted that although the example in this invention is given by performing compression on all part reports, this scheme is also applicable to the case of performing compression on one or some part reports. Furthermore, in S904, if all part reports are compressed, the responding end obtains multiple measurement report frames based on the compressed multiple part reports; if some reports are compressed, the responding end obtains multiple measurement report frames based on one or more uncompressed remaining part reports from one or more compressed part reports.

[0169] By compressing some or all of the reports, the overall signaling overhead is reduced.

[0170] In one possible implementation, a first measurement report frame corresponding to the first partial report indicates a first parameter specific to the first partial report. The first measurement report frame carries a first fragment of the first partial report, and the indication of the first parameter is omitted in the remaining measurement report frames corresponding to the first partial report, excluding the first measurement report frame. The first partial report can be fragmented into several fragments, each of which can be carried in a measurement report frame. Since the first parameter specific to this partial report is common to all acquired fragments, it can be carried only in the first measurement report frame corresponding to the first partial report, and the indication of the first parameter can be omitted in the other measurement report frames corresponding to the first partial report, thereby reducing signaling overhead. For example, if the first partial report is fragmented into two segments, each segment carried in a measurement report frame, then there are two measurement report frames corresponding to the first partial report (MRF1 and MRF2). The first parameter can be carried only in the first measurement report frame (MRF1), and since the second measurement report frame is one of the remaining measurement report frames corresponding to the first partial report, the indication of the first parameter is not carried in MRF2.

[0171] In one possible implementation, the first measurement report frame includes a first parameter field for indicating a first parameter.

[0172] Here, the first parameter can be one of the following: the timing offset between the reference tap and the CIR report timing grid, the normalization factor applied to the CIR tap reported in the CIR tap field, and the received signal strength at the antenna used to generate the received sequence for this receive report field. The first parameter can be carried in the independent report descriptor field (corresponding to the first parameter field mentioned above), which will be explained later for specific frame formats.

[0173] In one possible implementation of the invention, a second measurement report frame among multiple measurement report frames indicates a second parameter in all parts of the measurement report. The second measurement report frame is the first measurement report frame among the multiple measurement report frames, and the indication of the second parameter is omitted in the remaining measurement report frames. The measurement report can include multiple parts of the report, and the second parameter can be a parameter common to all parts of the report. That is, the multiple measurement report frames carrying all parts of the report share the second parameter. Therefore, the second parameter can be carried only in the first measurement report frame among the multiple measurement report frames, and the indication of the second parameter can be omitted in the other measurement report frames to reduce signaling overhead.

[0174] In one possible implementation of the invention, the second measurement report frame includes a second parameter field for indicating a second parameter.

[0175] The second parameter here can be parameters such as the number of Rx antennas, the number of segments, or the CIR bitmap. The first parameter can be carried in the report parameter control field (corresponding to the second parameter field mentioned above), which will be explained in detail later for specific frame formats.

[0176] In one possible implementation of the invention, the second measurement report frame further includes a parameter indication field for indicating whether the second parameter field exists.

[0177] In one possible implementation of the invention, the corresponding measurement report frame indicates whether the fragment carried in the corresponding measurement report frame is the first fragment from which a fragment is obtained, the number of remaining fragments in the report from which a fragment is obtained, and the length associated with the fragment. As mentioned above, the measurement results can be distributed across multiple measurement report frames; therefore, for each of the multiple measurement report frames, it is necessary to indicate the fragments carried therein. Each measurement report frame can carry one or more fragments; if it carries more than one fragment, each fragment must be indicated. Therefore, for each fragment carried in the measurement report frame, it indicates whether the fragment is the first fragment from which a partial report of that fragment is obtained, the number of remaining fragments in the partial report from which that fragment is obtained, and the length associated with the fragment. It should be noted that the length associated with the fragment may be longer than the length of the fragment itself, because other information, such as an independent report descriptor field, may be required to carry the fragment.

[0178] In one possible implementation of the present invention, the corresponding measurement report frame includes: a first fragment field, used to indicate whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which fragments are obtained; a remaining fragment field, used to indicate the number of remaining fragments in the report from which fragments are obtained; and a fragment report length field, used to indicate the length associated with the fragment. Here, the first fragment field can be implemented as a first report fragment field in the following examples, the remaining fragment field can be implemented as a remaining report fragment field in the following examples, and the fragment report length field can be implemented as a partial report length field in the following examples.

[0179] In one possible implementation of the present invention, the corresponding measurement report frame further includes a fragmentation indicator field, used to indicate the presence of a first fragmentation field, remaining fragmentation fields, and a fragmentation report length field. The fragmentation indicator field can be implemented as a fragmentation indicator field in the following example.

[0180] In one possible implementation of the invention, corresponding measurement report frames among multiple measurement report frames indicate the identifier of the corresponding measurement report frame and the measurement. In another possible implementation, the corresponding measurement report frame includes a report number indicating the identifier of the measurement report frame and a measurement number identifying the measurement. To enable the initiating end to correctly distinguish each measurement report frame, the corresponding measurement report frame indicates the identifier of the corresponding measurement report frame and the measurement (measurement instance). Thus, when the measurement instances implemented by the initiating end and the responding end are different, and when the result of a measurement instance (measurement) is carried in different measurement report frames, the initiating end can determine which measurement instance each measurement report frame belongs to, and can also distinguish measurement report frames belonging to the same measurement instance. Here, the report number can be carried in the report SN field in the following examples, and the measurement number can be carried in the measurement ID field in the following examples.

[0181] In one possible implementation of the invention, the corresponding measurement report frame further indicates: the segment to which the fragment of the measurement report carried by the corresponding measurement report frame belongs, the antenna of the responding end for receiving the fragment, and the channel on which the fragment is received. In another possible implementation of the invention, the corresponding measurement report frame includes: a fragment field for identifying the segment to which the fragment of the measurement report carried by the corresponding measurement report frame belongs; an antenna field for identifying the antenna of the responding end for receiving the fragment; and a channel field for identifying the channel on which the fragment is received. Here, the fragment field can be implemented as a fragment ID or a fragment ID bitmap field in the following examples; the antenna field can be implemented as an Rx antenna ID or an Rx antenna ID bitmap field in the following examples; and the fragment field can be implemented as a channel ID or a channel ID bitmap field in the following examples.

[0182] Another approach is to directly fragment the measurement report, without considering the boundaries of the received report carried in the received report field. Figure 10 This is a schematic flowchart of a communication method according to another embodiment of the present invention. Figure 10 As shown, the method includes: S1001: The response end performs fragmentation on the measurement report to obtain a second number of fragments; S1002: The response end acquires multiple measurement report frames based on the second number of fragments.

[0183] exist Figure 10 Based on the communication method shown, Figure 11 This is a schematic flowchart of a communication method according to another embodiment of the present invention, wherein measurement reports are compressed. Figure 11 As shown, the method includes: S1101: The response end compresses the measurement report; S1102: The response end performs fragmentation on the compressed measurement report to obtain a second number of fragments; S1103: The response end acquires multiple measurement report frames based on the second number of fragments.

[0184] The compression here can be used to reduce the size of the measurement report, and will help reduce the number of fragments, and further reduce the number of measurement report frames carrying fragments. In addition, when compressing the measurement report, some larger fields, such as CIR bitmap fields, can also be compressed. By directly performing fragmentation on the measurement report, the operation is simplified, and more flexibility is provided in the format design of the report IE used to implement this process.

[0185] Furthermore, the specific value of the second quantity here can be determined based on actual needs, and this application embodiment does not limit it in this regard.

[0186] In one possible implementation of the invention, the measurement report is directly fragmented into a second number of fragments, and each of these second number of fragments is carried in a single measurement report frame. This single measurement report frame includes: a first fragment field indicating whether the fragment carried in the corresponding measurement report frame is the first fragment from which the fragments were obtained; a remaining fragment field indicating the number of remaining fragments in the report from which the fragments were obtained; and a fragment report length field indicating the length associated with the fragment. Here, the first fragment field can be implemented as a first report fragment field in the following examples, the remaining fragment field can be implemented as a remaining report fragment field in the following examples, and the fragment report length field can be implemented as a partial report length field in the following examples.

[0187] In one possible implementation of the first aspect, the CIR bitmap field in the report parameter control field can also be compressed along with the measurement report.

[0188] In one possible implementation of the invention, a second measurement report frame among multiple measurement report frames indicates a second parameter in all parts of the measurement report. The second measurement report frame is the first measurement report frame among the multiple measurement report frames, and the indication of the second parameter is omitted in the remaining measurement report frames. The measurement report can include multiple parts of the report, and the second parameter can be a parameter common to all parts of the report. That is, the multiple measurement report frames carrying all parts of the report share the second parameter. Therefore, the second parameter can be carried only in the first measurement report frame among the multiple measurement report frames, and the indication of the second parameter can be omitted in the other measurement report frames to reduce signaling overhead.

[0189] In one possible implementation of the invention, the second measurement report frame includes a second parameter field for indicating a second parameter.

[0190] The second parameter here can be parameters such as the number of Rx antennas, the number of segments, or the CIR bitmap. The first parameter can be carried in the report parameter control field (corresponding to the second parameter field mentioned above), which will be explained in detail later for specific frame formats.

[0191] In one possible implementation of the invention, the second measurement report frame further includes a parameter indication field for indicating whether the second parameter field exists.

[0192] In one possible implementation of the invention, the corresponding measurement report frame indicates whether the fragment carried in the corresponding measurement report frame is the first fragment from which the fragment is obtained, the number of remaining fragments in the report from which the fragment is obtained, and the length associated with the fragment. As mentioned above, the measurement results can be distributed across multiple measurement report frames; therefore, for each of the multiple measurement report frames, it is necessary to indicate the fragment carried therein. Each measurement report frame can carry one or more fragments; if it carries more than one fragment, each fragment must be indicated. Therefore, for each fragment carried in the measurement report frame, it indicates whether the fragment is the first fragment from which the measurement report from which the fragment is obtained, the number of remaining fragments in the partial report from which the fragment is obtained, and the length associated with the fragment. It should be noted that the length associated with the fragment may be longer than the length of the fragment itself, because other information, such as an independent report descriptor field, may be required to carry the fragment.

[0193] In one possible implementation of the present invention, the corresponding measurement report frame includes: a first fragment field, used to indicate whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which fragments are obtained; a remaining fragment field, used to indicate the number of remaining fragments in the report from which fragments are obtained; and a fragment report length field, used to indicate the length associated with the fragment. Here, the first fragment field can be implemented as a first report fragment field in the following examples, the remaining fragment field can be implemented as a remaining report fragment field in the following examples, and the fragment report length field can be implemented as a partial report length field in the following examples.

[0194] In one possible implementation of the present invention, the corresponding measurement report frame further includes a fragmentation indicator field, used to indicate the presence of a first fragmentation field, remaining fragmentation fields, and a fragmentation report length field. The fragmentation indicator field can be implemented as a fragmentation indicator field in the following example.

[0195] In one possible implementation of the invention, corresponding measurement report frames among multiple measurement report frames indicate the identifier of the corresponding measurement report frame and the measurement. In another possible implementation, the corresponding measurement report frame includes a report number indicating the identifier of the measurement report frame and a measurement number identifying the measurement. To enable the initiating end to correctly distinguish each measurement report frame, the corresponding measurement report frame indicates the identifier of the corresponding measurement report frame and the measurement (measurement instance). Thus, when the measurement instances implemented by the initiating end and the responding end are different, and when the result of a measurement instance (measurement) is carried in different measurement report frames, the initiating end can determine which measurement instance each measurement report frame belongs to, and can also distinguish measurement report frames belonging to the same measurement instance. Here, the report number can be carried in the report SN field in the following examples, and the measurement number can be carried in the measurement ID field in the following examples.

[0196] In one possible implementation of the invention, the corresponding measurement report frame further indicates: the segment to which the fragment of the measurement report carried by the corresponding measurement report frame belongs, the antenna of the responding end for receiving the fragment, and the channel on which the fragment is received. In another possible implementation of the invention, the corresponding measurement report frame includes: a fragment field for identifying the segment to which the fragment of the measurement report carried by the corresponding measurement report frame belongs; an antenna field for identifying the antenna of the responding end for receiving the fragment; and a channel field for identifying the channel on which the fragment is received. Here, the fragment field can be implemented as a fragment ID or a fragment ID bitmap field in the following examples; the antenna field can be implemented as an Rx antenna ID or an Rx antenna ID bitmap field in the following examples; and the fragment field can be implemented as a channel ID or a channel ID bitmap field in the following examples.

[0197] When fragmenting at the partial report level considering the boundaries of partial reports, since the CIR taps included in a partial report can be distributed across multiple fragments, and it is possible that a measurement report frame corresponds to more than one fragment, each fragment included in the measurement report frame can be indicated by a first fragment field, a remaining fragment field, and a fragment report length field. This allows the initiator to identify fragments and arrange multiple fragments of the same partial report in the correct order. When fragmenting the measurement report directly without considering boundaries, each measurement report frame can include a first fragment field, a remaining fragment field, and a fragment report length field to indicate the fragments it carries.

[0198] As described above, there are two types of reports, and the formats (or structures) of these two reports will be explained in detail below. For the first type of report, namely the window-based CIR report, the CIR report IE can have two formats. For the second type of report, namely the processed target feature report, an exemplary processed target feature IE is presented.

[0199] To implement the above fragmentation, a CIR report IE format needs to be designed to notify the initiating end of the fragmentation. The following will first introduce the CIR report IE format, and then describe the corresponding fragmentation and compression in conjunction with the CIR report IE format.

[0200] First, we will introduce the structure of the measurement report frame carrying the CIR report (IE). The measurement report frame is transmitted on the Media Access Control (MAC) sublayer. For example... Figure 12 As shown, the MAC sublayer consists of a MAC frame header, a MAC payload, and a MAC footer (MFR). The MAC payload (i.e., MLME IE) consists of the MLME IE frame header field and a nested IE (i.e., CIR report IE) (consisting of the CIR report IE frame header field and the CIR report IE content field). The CIR report IE content corresponds to the measurement report frame.

[0201] Combining Figure 13 The following is a specific example format for the CIR report IE content fields corresponding to the measurement report frame. Fields of interest are as follows: • Report Identification Control: Carries information that can be used to identify a measurement report frame and is present in all CIR report IEs. This section provides parameters used by the initiator to identify a particular measurement report frame and may therefore include the following fields: • Response Address Pattern: Indicates the presence and size of the "Response Address" field, for example: b00: Indicates that the response address field does not exist.

[0202] b01: Reserved b10: Indicates that the response address field includes a short address (16 bits).

[0203] b11: Indicates that the response address field includes an extended address (64 bits).

[0204] • Presence bit: Indicates whether an optional field exists in the report.

[0205] • Report SN: A unique sequence number that identifies a specific measurement report frame. The report SN can be used for selective retransmission in case of transmission failure. The report SN is generated locally by the responding end.

[0206] • Measurement ID (MID): A unique ID that identifies a specific measurement instance (such as the measurement performed by the responder as described above). The initiating end can use the MID to identify the report corresponding to a specific measurement instance. The MID is generated locally by the responder.

[0207] • Response End Address: Identifies the SDEV (Response End) that generated the Measurement Report Frame. It may exist in the case of SBP and is optional for non-SBP devices. It can be a short 2-byte address assigned to the Response End or an extended 8-byte address for the Response End. If the Response End uses a short 2-byte address in its CIR report, the initiating device can replace it with the extended 8-byte address of the Response End when forwarding the CIR report to the sensing requesting device.

[0208] • Fragmentation Indication: Indicates that the CIR report is fragmented and that a fragmentation control field exists.

[0209] • Report Parameter Control: Carries common parameters for all partial reports with the same MID, such as the number of Rx antennas, the number of segments, and the CIR bitmap. When partial reports corresponding to the same measurement instance are carried on multiple frames, this field may only exist in the first measurement report frame corresponding to that measurement instance, and not in the remaining measurement report frames. This field can be the second parameter field mentioned above, which only exists in the first measurement report frame among multiple measurement report frames of the same measurement report, and is omitted in the remaining measurement report frames.

[0210] • One or more received reports: Carry one or more partial reports and are present in all measurement report frames.

[0211] • Report ID: Identifies a partial report and exists when the received report of the same measurement is carried in different CIR reports or frames. If the Report ID field is not present, it means that the entire report (all partial reports) is carried in the IE. The Report ID may include the following fields: • Rx Antenna ID: The ID of the receiving antenna corresponding to the partial report carrying the CIR tap.

[0212] • Fragment ID: The ID of the segment of the sensing data packet corresponding to the partial report carrying the CIR tap.

[0213] • Channel ID: For frequency splicing packets, this indicates the channel of the measured CIR tap. The channel ID can be a relative index (rather than an actual physical channel index), for example, CH 0 is the primary channel, CH 1 is the next channel closest to the primary channel, etc. This field is reserved for normal sensing packets. If more bits are available (e.g., 7 bits), the channel ID can also represent the actual logical ID of the channel used.

[0214] • Segmentation control (exists if the measurement report is segmented): • First report fragment: Indicates whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which that fragment was obtained. For example, it can be set to 1 for the first fragment of a partial report, and 0 otherwise. This embodiment of the invention does not limit the specific value of this field.

[0215] • Remaining Report Fragments: Indicates the number of remaining fragments (the number of remaining fragments in the report from which fragments are derived). For example, for the last fragment, it can be set to 0. For fragments that are not the last fragment, it is set to a value between 1 and (2n–1). Here, n is the number of bits used for the Remaining Report Fragments field. This embodiment of the invention does not limit the specific value of this field.

[0216] • Partial Report Length: Indicates the length of the partial report field when it is fragmented (e.g., in octet). The number of bits required for the partial report length field can be reduced, for example, by expressing it as a percentage of the total report length (e.g., 7 bits are sufficient to indicate 100%).

[0217] • Partial Report: When compression is performed, a compressed CIR report is carried; otherwise, each partial CIR report carries: • Independent Report Descriptor: Carries report parameters specific to the partial report, such as the timing offset between the reference tap and the CIR report timing grid, the normalization factor applied to the CIR tap reported in the CIR tap field, and the received signal strength at the antenna used to generate the received sequence for this receive report field. When a partial report is fragmented, this field exists only in the first fragment (first report fragment = 1) and not in the remaining fragments because the report parameters are the same for all fragments of the same partial report. The field always exists in unfragmented partial reports. This field can be a first parameter field specific to the first measurement report frame among multiple measurement report frames as described above.

[0218] • CIR Taps: These include CIR tap values ​​corresponding to fragmented or unfragmented partial reports. Each bit in the CIR bitmap has one value, set to 1. Each CIR tap consists of a signed in-phase (I) value and a signed quadrature (Q) value. When a partial report is fragmented, the CIR taps are distributed across the fragments in the same order shown in the CIR bitmap.

[0219] It should be noted that the specific values, lengths, and names of the above fields are for illustrative purposes only and can be other values, as long as the function of each field is achieved.

[0220] Now, we can refer to the above format to explain fragmentation. When the CIR report corresponding to a single sensing measurement (also called a measurement instance) (the aforementioned measurement report includes all received reports acquired for a measurement instance, including CIR taps) is too large to fit in a single frame, the received report can be divided into two or more partial reports, each carrying all CIR taps corresponding to the received antenna and segment pairs on a specific channel. Based on the capacity of the sensing measurement report frame (also called a measurement report frame), two or more measurement report frames are used to carry the measurement report, each carrying one or more partial reports. However, in some cases, it may occur that even a single partial report is too large to fit in a single frame. In these cases, such as... Figure 14 As shown, each partial report can be further divided into two or more CIR report segments (also called fragments), each fragment carrying a limited number of CIR taps corresponding to the receive antenna and segment pair, and each fragment is carried in a separate measurement report frame. The report identifier control field is present in all four measurement report frames, while the report parameter control field is present only in the first measurement report frame. Similarly, the independent report descriptor field is present only in the first fragment of each partial report (first report fragment = 1), and not in the remaining fragments of the partial report, i.e., only in the first and third measurement report frames. Fragments for which compression is not applicable are... Figure 8 A specific example of the process shown.

[0221] The following is combined with Figure 14 , combined Figures 15A to 15C This section provides a concrete example to illustrate sharding.

[0222] Figure 15AA specific example without compression is shown. The initiating end sends a sensing data packet with a single sensing segment. The responding end has two receive antennas, so a total of two partial reports are required, one for each receive antenna and sensing segment. In this example, the AC IE indicates a 32-byte CIR bitmap, with both I and Q values ​​being 16 bits, so each partial report is 1024 bytes in size. Assuming a preset threshold of 1000 bytes for a measurement report frame, since partial reports cannot be contained in a single measurement report frame, each partial report needs to be divided into two segments, resulting in a total of four measurement report frames (and four CIR report IEs, or four CR IEs as shown in the figure) requiring feedback of the measurement's CIR taps. It should also be noted that the report parameter control (RPC) field is only present in the CIR report IE carrying the first segment of the first partial report (in the first measurement report frame mentioned above), and not in the remaining measurement report frames (the remaining measurement report frames mentioned above). The independent report descriptor field is only present in the CIR report IE carrying the first segment of each partial report (in the first measurement report frame mentioned above), and not in the remaining measurement report frames. Figure 15A The CIR Report IE (CR IE) for the first segment (corresponding to the first and third CR IEs) in the figure exists in the receive report field, but not in the receive report field of the CIR Report IE carrying the remaining segments. The independent report descriptor field is not shown in the figure. It should be noted that in the text, specific examples of the CIR Report IE format show fields of interest; fields not shown may also exist in the CIR Report IE. The report parameter control field may exist only in the first of the four measurement report frames corresponding to the same measurement instance, and may be omitted in the remaining measurement report frames.

[0223] You can also Figure 15A The second and third measurement report frames are merged into one measurement report frame to reduce overall signaling overhead. Because... Figure 15A The second measurement report frame (and the corresponding CIR report IE) carries only 64 octets of the CIR taps. Assuming each measurement report frame can carry a maximum of 960 CIR taps, by intelligently fragmenting the second part of the report (e.g., making the first fragment carry 880 octets of the CIR taps), the second fragment of the first part of the report and the first fragment of the second part of the report can be carried in the same measurement report frame, making three measurement report frames sufficient to carry the entire CIR report. This is in... Figure 15BThe details are shown below. The Independent Report Descriptor field exists in the Receive Report field of the first CR IE because it carries the first fragment of the first part of the report, and it exists in the second Receive Report field of the second CR IE because it carries the first fragment of the second part of the report, but it does not exist in the other Receive Report fields. The Report Parameter Control field may only exist in the first measurement report frame of the three measurement report frames in the same measurement instance, and may be omitted in the remaining measurement report frames. Figure 15C Detailed illustration Figure 15B The structure of the second measurement report frame in the example is shown. Fields are displayed using abbreviations, where FRF refers to the first report fragment, RRF refers to the remaining report fragments, PRL refers to the partial report length, and IRD refers to the aforementioned independent report descriptor.

[0224] It should be noted that since the second measurement report frame shown is for the same measurement instance, it does not contain a report parameter control field. The CIR report IE content field carries two receive report fields: the first receive report field carries the second fragment of the first part of the report, and the second receive report field carries the first fragment of the second CIR report. The independent report descriptor field exists in the second receive report field (FRF = 1) but not in the first receive report field. The report parameter control field can be omitted in the second measurement report frame.

[0225] As mentioned above, compression can also be performed during fragmentation. A specific example of the format described above is as follows: Figure 16 As shown. The process is similar to Figure 14 The process differs in that each partial report is first compressed (e.g., using DEFLATE). If the compressed CIR report (compressed partial report) is small enough, one or more measurement report frames are used to carry the compressed CIR report, with each frame carrying one or more compressed reports. However, if even a single compressed CIR report is too large to fit in a single frame, each compressed CIR report can be further divided into two or more fragments, and each fragment is carried in a separate frame. Using compressed fragments is... Figure 9 A specific example of the process shown.

[0226] The following is combined with Figure 16 , combined Figures 17A to 17B This section provides a concrete example to illustrate sharding.

[0227] Figure 17AA specific example of compression is shown. The initiating end sends a sensing data packet with a single sensing segment. The responding end has four receive antennas, so a total of four partial reports are required, one for each receive antenna and sensing segment. In this example, the AC IE indicates a 32-byte CIR bitmap with 16-bit I and Q values, so each partial report is 1024 bytes in size. The AC IE also indicates compression to be performed. In this example, the compression efficiency is 50%, meaning each partial report is 512 bytes in size after compression. While four measurement report frames can be used to transmit four compressed partial reports (as shown in the compressed CIR report), fragmentation can be used on the second compressed partial report, making only three measurement report frames sufficient to transmit the entire CIR report. The first measurement report frame carries the first fragment of the first and second compressed partial reports; the second measurement report frame carries the second fragment of the second compressed partial report and the third compressed partial report, while the third measurement report frame carries the fourth compressed partial report. It should also be noted that the report parameter control field exists only in the CIR report IE carrying the first part of the report (in the first measurement report frame), and not in the remaining measurement report frames. The independent report descriptor field may also exist only in the receive report field of the CIR IE carrying the first fragment corresponding to each part of the report. Figure 17A Not shown in the diagram. The report parameter control field may exist only in the first of the three measurement report frames for the same measurement instance, and may be omitted in the remaining measurement report frames.

[0228] Figure 17B Detailed illustration Figure 17A The example shown illustrates the structure of the second measurement report frame. Since the illustrated second measurement report frame is for the same measurement instance, the report parameter control field is absent. The CIR report IE content field carries two receive report fields: the first receive report field carries the second fragment of the second compressed partial report, and the second receive report field carries the entire third compressed CIR report. The independent report descriptor field is present in the second receive report field (FRF = 1) but not in the first receive report field. The report parameter control field can be omitted in the second measurement report frame.

[0229] While supporting flexible sizes for each shard allows for greater flexibility in adapting to different environments, it's also possible to achieve simplicity by limiting the size of each shard except for the last one. Figure 14 and Figure 16 The size of the slices other than M and N in the M and N values ​​is fixed at a certain size, for example, 960 octets.

[0230] As referenced above Figure 10 and Figure 11Alternatively, fragmentation can be performed directly on measurement reports that include all received reports corresponding to the same measurement instance. Unlike fragmentation at the partial report level considering the boundaries of partial reports, fragmentation can be performed directly on measurement reports, allowing partial reports to be separated.

[0231] Figure 18 and Figure 19 Specific examples of using or not using compression are shown. Figure 18 The process shown does not perform compression. When the CIR report (CIR tap) corresponding to a single sensing measurement is too large to fit in a single frame, the CIR report is divided into two or more CIR report fragments (regardless of partial CIR report boundaries). Each fragment carries a limited number of CIR taps, and each fragment is carried in a separate frame. Alternatively, the CIR report can be divided into two or more partial CIR reports first, and then fragmentation can be applied to the independent partial CIR reports. Figure 19 The compression process is illustrated. For example... Figure 19 As shown, on the sending side (responding end), the CIR report is first compressed (e.g., using DEFLATE). If the compressed report (CIR tap) is too large to fit in a single frame, the compressed measurement report is fragmented into two or more fragments. In one possible implementation, other large fields, such as the CIR bitmap field, may also be compressed along with the CIR tap. Each fragment is carried in a CIR report IE (measurement report frame). On the receiving side (initiating end), the received fragments are first assembled in the correct order. The assembled report is then decompressed to recover the original measurement report (along with other fields compressed together, such as the CIR bitmap). Report parameter control fields may only exist in the first of the three measurement report frames for the same measurement instance, and may be omitted in the remaining measurement report frames. Throughout the text, the terms "perceived measurement report frame" and "measurement report frame" are used interchangeably.

[0232] Combining Figure 20 describe Figure 18 and Figure 19 The specific exemplary format of the CIR report IE content fields corresponding to the measurement report frame described herein, and the fields of interest are as follows: • Report Identification Control: Carries information that can be used to identify measurement reports and is present in all CIR report IEs. This section provides parameters used by the initiator to identify a particular measurement report frame, and therefore may include the following fields: • Response Address Pattern: Indicates the presence and size of the "Response Address" field, for example: b00: Indicates that the response address field does not exist.

[0233] b01: Reserved b10: Indicates that the response address field includes a short address (16 bits).

[0234] b11: Indicates that the response address field includes an extended address (64 bits).

[0235] • Partial Bitmap Length: Identifies the length and valid values ​​of a partial report bitmap field, for example: • b00: 0th bit, meaning that some bitmap fields in the report do not exist. • b01: 8 bits (only Rx antenna ID bitmap and segment ID bitmap exist) b10: 24 bits (all 3 bitmaps exist) b11: Reserved.

[0236] • First report fragment: Set to 1 for the first report fragment or for unfragmented reports, otherwise set to 0.

[0237] • Number of Remaining Report Shards: Indicates the number of remaining report shards. Set to 0 for the last report shard or for reports that are not sharded. Set to a value between 1 and (2n–1) for report shards that are not the last shard. Here, n is the number of bits used for the Remaining Report Shards field.

[0238] • Report SN: A unique sequence number that identifies a specific measurement report frame. The report SN can be used for selective retransmission in case of transmission failure. The report SN is generated locally by the responding end.

[0239] • Measurement ID (MID): A unique ID that identifies a specific measurement instance (such as the measurement performed by the responder as described above). The initiating end can use the MID to identify the report corresponding to a specific measurement instance. The MID is generated locally by the responder.

[0240] • Response End Address: Identifies the SDEV (Response End) that generated the measurement report. It may exist in the case of SBP and is optional for non-SBP devices. It can be a short 2-byte address assigned to the Response End or an extended 8-byte address for the Response End. If the Response End uses a short 2-byte address in the CIR report IE sent by the Response End, the initiating device can replace it with the extended 8-byte address of the Response End when forwarding the CIR report to the sensing requesting device.

[0241] • Partial report bitmap (exists when the received report of the same measurement is carried in different measurement frames). If the bitmap does not exist, the entire report will be carried in the IE. The partial report bitmap may include the following fields: • Rx Antenna ID Bitmap: Identifies the existence of the ID of the receiving antenna corresponding to the CIR tap.

[0242] • Fragment ID Bitmap: Identifies the existence of the ID of the segment of the sensing data packet corresponding to the CIR tap.

[0243] • Channel ID bitmap: For frequency splicing PPDUs, this indicates the channel of the measurement CIR tap. Reserved for normal sensing data packets.

[0244] • Report Parameter Control: Carries common report parameters for all reports with the same MID, such as the number of Rx antennas, the number of segments, and the CIR bitmap. When a measurement report (or part of a CIR report) corresponding to the same measurement instance is carried across multiple frames, this field only exists in the first measurement report frame corresponding to that measurement instance (the first report fragment field is set to 1), and not in the remaining measurement report frames. When compression is performed, some large fields, such as the CIR bitmap, can also be compressed along with the received report. This field can be the second parameter field mentioned above, existing only in the first measurement report frame among multiple measurement report frames of the same measurement report, and omitted in the remaining measurement report frames.

[0245] • One or more receive reports: Carry one or more partial reports, or fragments thereof, corresponding to the receive antenna, segment, and channel indicated in the partial report bitmap. When a partial report bitmap exists, fragmentation will be based on the partial reports.

[0246] • Independent report descriptor: Carries some report-specific reporting parameters, such as the timing offset between the reference tap and the CIR report timing grid, the normalization factor applied to the CIR taps reported in the CIR tap field, and the received signal strength at the antenna used to generate the received sequence for this receive report field.

[0247] • CIR Taps: Includes CIR tap values, one value per bit in the CIR bitmap, set to 1. Each CIR tap consists of a signed in-phase (I) value and a signed quadrature (Q) value. When reports are fragmented, the CIR taps will be distributed across the fragments in the same order shown in the CIR bitmap.

[0248] In a communication method according to one possible implementation of the present invention, the sensing data packet sent by the initiating end may include one or more sensing data packets, and each sensing data packet in the plurality of sensing data packets includes one or more fragments; the measurement report obtained based on the sensing data packet may be one or more. The obtained measurement report can be fragmented according to the scheme of the present invention. The following is in conjunction with... Figure 20 The format shown is as follows: Figure 21 , Figure 22A and Figure 22B as well as Figure 23A and Figure 23B The fragmented communication method will be explained with a specific example.

[0249] like Figure 21 As shown, Figure 21 For the out-of-order inter-packet frequency splicing type, the initiating end sends two sensing data packets to the responding end on different channels CH0 and CH1. Each sensing data packet consists of two segments, SEG 1 and SEG 2. The responding end sends two measurement report frames to the initiating end based on these two sensing data packets. The carrier frequency grid parameter is set to 2 (50% overlap), and the number of transmissions (N) = 2. The channel sequence order field in the AC IE is set to 0, and the channels used are selected sequentially starting from the basic channel (CH0). The frequency splicing type field in the AC IE is set to 1 (inter-packet frequency splicing). Each sensing data packet consists of two segments. The first sensing data packet is sent on the basic channel (CH0) (by the initiating end), while the second sensing data packet is sent on the second channel (CH1), for example, from the basic channel with a carrier frequency increment of 499.2 MHz. Here, the transmission interval between the two sensing data packets is at least 1 ms to maximize the transmission power of each transmission. This can also be indicated by signaling in the MMS mode field in the AC IE. The responder uses all four of its receive antennas to measure the CIR tap for each segment (at each carrier frequency). In this example, the Report Channel field of the Frequency Stitching Parameter field in the AC IE's Sensing Control field is set to 1 (last channel). The Feedback Control field of the Frequency Stitching Parameter field in the AC IE's Sensing Control field is set to 1 (reports all transmissions since the last transmission). Two CIR reports are generated, one for each channel.

[0250] The aforementioned AC IE (not shown) may include the following fields: Carrier frequency grid: Used to indicate carrier frequency grid configuration parameters (also known as carrier frequency grid parameters), which indicate whether the carrier frequencies of the channel overlap; for example, carrier frequency grid parameters 0, 1, 2, and 3 represent no overlap, 25% overlap, 50% overlap, and 75% overlap, respectively.

[0251] Transmission count: This indicates the total number of transmissions performed at different channel center frequencies. In other words, the transmission count refers to the number of carrier frequencies used for frequency splicing.

[0252] Channel sequence order: This indicates whether segments are transmitted sequentially or out of order. For example, a channel sequence order field of 0 indicates sequential transmission, while a field of 1 indicates out-of-order transmission. Sequential transmission refers to the method by which adjacent segments of the same sensing data packet are transmitted sequentially on the channel (whose carrier frequencies follow certain rules or are regularly distributed). Out-of-order transmission refers to a method where overlapping segments of the same sensing data packet or overlapping segments of overlapping sensing data packets can be separated in another dimension (different from the dimension in which the overlap occurs). For example, overlap can occur in the frequency domain, meaning channels carrying two adjacent segments can overlap, and these two segments can be separated in the time domain, for example, the time interval between the transmission of these two segments can be greater than 1 ms.

[0253] Frequency splicing type (not shown in the figure): This indicates the frequency splicing type with different values. For example, when the value is 0, the frequency splicing type is intra-packet frequency splicing; when the value is 1, the frequency splicing type is inter-packet frequency splicing; and when the value is 2, the frequency splicing type is a combination of intra-packet frequency splicing and inter-packet frequency splicing.

[0254] Report Channel Field: This field indicates the channel used to transmit measurement report frames. For example, a value of 0 indicates that the basic channel is used to transmit measurement report frames, and a value of 1 indicates that the last sensing data packet is used to transmit measurement report frames. Here, the basic channel, as described above, refers to the starting channel for performing UWB sensing when frequency splicing is performed, and the last channel refers to the channel on which the last fragment of the last sensing data packet is transmitted.

[0255] MMS Mode: Used to indicate the interval between any two overlapping transmissions of a sense packet or a fragment of the same packet. For example, when the value of the MMS Mode field is 0 (corresponding to sequential mode), the interval can be less than 1 ms; when the value of the MMS Mode field is 1 (corresponding to out-of-order mode), the interval between any two overlapping transmissions of a sense packet or the same packet can be at least 1 ms. There can be two transmission modes, sequential or out-of-order, so this can also be indicated using MMS Mode.

[0256] Feedback control: Used to indicate different reporting formats. For example, when its value is 1, the report is for all transmissions since the last transmission; when its value is 2, the report is for aggregated channels since the last transmission.

[0257] CIR Bitmap: Used to instruct the responder to perform CIR tap measurements on each bit set to 1 in the CIR Bitmap field.

[0258] Figure 22A and Figure 22B use Figure 20The format of the CIR report IE content field shown illustrates the format in an uncompressed scenario. Figure 21 The example shows a possible content of a measurement report frame. Since there are four partial reports corresponding to one segment (one segment per receive antenna) and two segments, each report frame is expected to carry a total of eight partial reports (assuming no size limit). The MID field in both reports is set to the same value (e.g., 1), while the report SNs are set to 1 and 2 respectively. The Rx antenna ID bitmap is set to b1111 to indicate the presence of partial reports corresponding to all four receive antennas. The segment ID bitmap is set to b0011 to indicate the presence of partial reports corresponding to the first two segments. The least significant bit of the channel ID bitmap is set to 1, indicating the presence of a partial CIR report corresponding to the first channel (CH 0) in the first report, while the second least significant bit of the channel ID bitmap is set to 1, indicating the presence of a partial report corresponding to the second channel (CH 1) in the second report. Within each CIR report IE, multiple receive reports included in one or more receive report fields can be arranged in a fixed order, for example, according to the order of antenna ID first and segment index last. In this example, even after the report is divided into two parts, the report is not in a single report frame. Therefore, the receive report field of each report is divided into three fragments, each fragment carrying a portion of the receive report field, and carried in a separate CIR report IE (and a separate report frame). A total of six CIR report IEs are carried in six report frames.

[0259] Figure 23A and Figure 23B use Figure 20 The format of the CIR report IE content field shown illustrates the compression scenario. Figure 21 The example in the diagram shows a possible content of a measurement report frame. The process is similar to that without compression, but the receive report field of each part of the CIR report is compressed first. Some adjacent large fields (such as the CIR bitmap) can also be compressed together. If the compressed CIR report is still too large to fit in a single report frame, the report is further fragmented as described above and transmitted via separate report frames.

[0260] Figure 20 The example is as follows, but assumes that the feedback control field of the frequency splicing parameter field in the AC IE's perception control field is set to 2 (reporting from the aggregated channel after the last transmission), such as... Figure 24 As shown. Here, a single CIR report for the aggregated channel (CH 0 + CH 2) is generated by the response end.

[0261] Figure 25 use Figure 20 The format of the CIR report IE content field shown is illustrated. Figure 24The example shows a possible content of a measurement report frame. The process is similar to... Figure 23A and Figure 23B The process described in [the previous section] differs in that, in this case, the entire CIR report is compressed (rather than separate partial reports), therefore the partial report bitmap field is absent (equal to 0) in the report identifier control field. Although in [the previous section]... Figure 13 , Figure 20 , Figure 26 , Figure 27 or Figure 25 Not shown in the text, but when the measurement report is for the aggregated channel, Figure 13 , Figure 20 , Figure 26 , Figure 27 or Figure 25 In the report IE, the bit in the report (e.g., the aggregate channel bit in the report parameter control field) is set to 1 to remind the initiator that the measurement report is for the aggregate channel.

[0262] As can be seen from the example above, the Report SN will be different for the Report Identifier Control Field reported before sharding and the Report Identifier Control Field reported after sharding, because this number is used to distinguish shards, but the Measurement ID will be the same because they correspond to the same measurement instance.

[0263] It should be noted that in all the examples shown above, the specific values ​​of the fields (e.g., MID, report SN) are for illustrative purposes only, and there are no restrictions on these values.

[0264] In one possible implementation, the responder may not report the original CIR taps, but instead process the measured CIR taps and only report the processed target features, such as angle of arrival (AoA), range, velocity, and radar cross section (RCS). Figure 26 This illustrates one possible format for reporting processed target features (IE) that support fragmentation. The fields of interest in the processed target feature IE content fields are as follows: • Report identification control: Carry information that can be used to identify measurement reports.

[0265] • Response Address Pattern: Indicates the presence and size of the "Response Address" field, for example: b00: Indicates that the response address field does not exist.

[0266] b01: Reserved b10: Indicates that the response address field includes a short address (16 bits).

[0267] b11: Indicates that the response address field includes an extended address (64 bits).

[0268] • First report fragment: Set to 1 for the first report fragment or for unfragmented reports, otherwise set to 0.

[0269] • Number of Remaining Report Shards: Indicates the number of remaining report shards. Set to 0 for the last report shard or for reports that are not sharded. Set to a value between 1 and (2n–1) for report shards that are not the last shard. Here, n is the number of bits used for the Remaining Report Shards field.

[0270] • Report SN: A unique sequence number that identifies a specific report frame. The report SN can be used for selective retransmission in case of transmission failure. The report SN is generated locally by the responding end.

[0271] • Measurement ID (MID): A unique ID that identifies a specific measurement instance. The initiating end can use the MID to identify the report corresponding to a specific measurement instance (such as the measurement performed by the responding end as described above). The MID is generated locally by the responding end. When reporting a CIR report and processing a target feature for the same measurement instance, the same MID can be used in both the CIR report IE and the processed target feature IE to help the initiating end map these two IEs.

[0272] • Response End Address: Identifies the SDEV (response end) that generates the processed target feature. It may exist in the case of SBP and is optional for non-SBP. It can be a short 2-byte address assigned to the sensing response end, or an extended 8-byte address for the response end. If the processed target feature IE sent by the response end uses a short 2-byte address, the initiating device can replace it with the extended 8-byte address of the response end when forwarding the processed target feature IE to the sensing requesting device.

[0273] • Report parameter control: Carries common reporting parameters for all reports with the same MID, such as the number of targets, the total number of targets, the number of sparse targets, etc.

[0274] • Complete target list: Carries the complete processed features, for example: • Azimuth: The azimuth angle of the target • Angle of elevation: The target's angle of elevation • Scope: The scope of the target • Speed: The target's speed • Radar cross section (RCS): The radar cross-section of the target. • Sparse target list: Carries some processed features, for example: • Scope: The scope of the target • Speed: The target's speed If the target feature report IE is too large to fit in a single report frame, the target list is fragmented as described above and transmitted via separate report frames.

[0275] When fragmenting partial reports, the length of each measurement report frame can be guaranteed by considering the taps (e.g., CIR taps) carried in each frame. In this case, different measurement report frame formats can be used.

[0276] Specifically, the corresponding measurement report frame indicates the number of taps carried in the frame, and the indicated number of taps is less than the total number of taps to be reported. In one possible implementation, the corresponding measurement report frame includes a tap bitmap field, which indicates the number of taps carried in the frame, and the bitmap indicated by the tap bitmap field is smaller than the bitmap required to indicate the total number of taps to be reported. In the following example, the tap bitmap field can be implemented as a partial bitmap field within the report parameter control field.

[0277] In one possible implementation of the invention, the corresponding measurement report frame indicates whether the fragment carried in the corresponding measurement report frame is the first fragment from which a fragment is obtained, the number of remaining fragments in the report from which a fragment is obtained, and the length associated with the fragment. As mentioned above, the measurement results can be distributed across multiple measurement report frames; therefore, for each of the multiple measurement report frames, it is necessary to indicate the fragments carried therein. Each measurement report frame can carry one or more fragments; if it carries more than one fragment, each fragment must be indicated. Therefore, for each fragment carried in the measurement report frame, it indicates whether the fragment is the first fragment from which a partial report of that fragment is obtained, the number of remaining fragments in the partial report from which that fragment is obtained, and the length associated with the fragment. It should be noted that the length associated with the fragment may be longer than the length of the fragment itself, because other information, such as an independent report descriptor field, may be required to carry the fragment.

[0278] In one possible implementation of the present invention, the corresponding measurement report frame includes: a first fragment field, used to indicate whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which fragments are obtained; a remaining fragment field, used to indicate the number of remaining fragments in the report from which fragments are obtained; and a fragment report length field, used to indicate the length associated with the fragment. Here, the first fragment field can be implemented as a first report fragment field in the following examples, the remaining fragment field can be implemented as a remaining report fragment field in the following examples, and the fragment report length field can be implemented as a partial report length field in the following examples.

[0279] In one possible implementation of the present invention, the corresponding measurement report frame further includes a fragmentation indicator field, used to indicate the presence of a first fragmentation field, remaining fragmentation fields, and a fragmentation report length field. The fragmentation indicator field can be implemented as a fragmentation indicator field in the following example.

[0280] In one possible implementation of the invention, corresponding measurement report frames among multiple measurement report frames indicate the identifier of the corresponding measurement report frame and the measurement. In another possible implementation, the corresponding measurement report frame includes a report number indicating the identifier of the measurement report frame and a measurement number identifying the measurement. To enable the initiating end to correctly distinguish each measurement report frame, the corresponding measurement report frame indicates the identifier of the corresponding measurement report frame and the measurement (measurement instance). Thus, when the measurement instances implemented by the initiating end and the responding end are different, and when the result of a measurement instance (measurement) is carried in different measurement report frames, the initiating end can determine which measurement instance each measurement report frame belongs to, and can also distinguish measurement report frames belonging to the same measurement instance. Here, the report number can be carried in the report SN field in the following examples, and the measurement number can be carried in the measurement ID field in the following examples.

[0281] In one possible implementation of the invention, the corresponding measurement report frame further indicates: the segment to which the fragment of the measurement report carried by the corresponding measurement report frame belongs, the antenna of the responding end for receiving the fragment, and the channel on which the fragment is received. In another possible implementation of the invention, the corresponding measurement report frame includes: a fragment field for identifying the segment to which the fragment of the measurement report carried by the corresponding measurement report frame belongs; an antenna field for identifying the antenna of the responding end for receiving the fragment; and a channel field for identifying the channel on which the fragment is received. Here, the fragment field can be implemented as a fragment ID or a fragment ID bitmap field in the following examples; the antenna field can be implemented as an Rx antenna ID or an Rx antenna ID bitmap field in the following examples; and the fragment field can be implemented as a channel ID or a channel ID bitmap field in the following examples.

[0282] Figure 27The possible content of a measurement report frame according to the above implementation is shown. Here, the CIR bitmap field in the report parameter control field is used to fragment the measurement report (or a portion of the CIR report). When the CIR report (CIR tap) corresponding to a single sensing measurement is too large to fit in a single frame, the CIR report is divided into two or more CIR report fragments, each carrying a limited number of CIR taps, and each fragment is carried in a separate frame. Alternatively, the measurement report can be divided into two or more partial reports first, and then fragmentation can be applied to the independent partial reports. When fragmenting the measurement report (or a portion of the CIR report), the entire CIR tap window is not indicated in the CIR bitmap field; instead, only a portion of the CIR tap window is carried in each fragment, and the bitmap offset field and CIR bitmap field are set accordingly.

[0283] The fields of interest in the CIR report IE content fields corresponding to the measurement report frame are as follows: • Report Identification Control: Carries information that can be used to identify measurement reports and is present in all CIR report IEs. This section provides parameters used by the initiator to identify a particular measurement report frame, and therefore may include the following fields: • Response Address Pattern: Indicates the presence and size of the "Response Address" field, for example: b00: Indicates that the response address field does not exist.

[0284] b01: Reserved b10: Indicates that the response address field includes a short address (16 bits).

[0285] b11: Indicates that the response address field includes an extended address (64 bits).

[0286] • The presence bit is used to indicate whether an optional field exists in the report.

[0287] • First report fragment: Set to 1 for the first report fragment or for unfragmented reports, otherwise set to 0.

[0288] • Number of Remaining Report Shards: Indicates the number of remaining report shards. Set to 0 for the last report shard or for reports that are not sharded. Set to a value between 1 and (2n–1) for report shards that are not the last shard. Here, n is the number of bits used for the Remaining Report Shards field.

[0289] • Report SN: A unique sequence number that identifies a specific report frame. The report SN can be used for selective retransmission in case of transmission failure. The report SN is generated locally by the sensing and responding end.

[0290] • Measurement ID (MID): A unique ID that identifies a specific measurement instance (such as the measurement performed by the responder as described above). The initiating end can use the MID to identify the report corresponding to a specific measurement instance. The MID is generated locally by the responder.

[0291] • Response End Address: Identifies the SDEV (response end) that generated the CIR report. It may exist in the case of SBP and is optional for non-SBP devices. It can be a short 2-byte address assigned to the response end or an extended 8-byte address for the response end. If the CIR report IE sent by the sensing response end uses a short 2-byte address, the sensing initiating end can replace it with the extended 8-byte address of the response end when forwarding the CIR report IE to the sensing requesting device.

[0292] • Reporting Parameter Control: Carries common reporting parameters for all reports with the same MID, such as the number of Rx antennas, the number of segments, partial bitmap, CIR bitmap, etc. Select the CIR bitmap size so that the corresponding CIR taps can be accommodated in the frame. In these cases, the partial bitmap field is set to 1 to indicate that the CIR bitmap is partially set.

[0293] • One or more receive reports: Carry one or more partial reports, or fragments thereof, corresponding to the receive antenna, segment, and channel indicated in the partial report bitmap. When a partial report bitmap exists, fragmentation will be based on the partial reports.

[0294] • Independent report descriptor: Carries some report-specific reporting parameters, such as the timing offset between the reference tap and the CIR report timing grid, the normalization factor applied to the CIR taps reported in the CIR tap field, and the received signal strength at the antenna used to generate the received sequence for this receive report field.

[0295] • CIR taps: Includes CIR tap values, one value per bit in the CIR bitmap, which is set to 1. Each CIR tap consists of a signed in-phase (I) value and a signed quadrature (Q) value.

[0296] The following is based on Figure 28 For specific examples, combined with Figure 27 Explain the fragmented communication method. For example... Figure 28As shown, the initiating end sends a sensing data packet with a single fragment. The responding end has two receive antennas, so a total of two partial reports are required, one for each receive antenna and one for each SENS fragment. In this example, the AC IE indicates a 32-byte CIR bitmap, with both I and Q values ​​being 16 bits, so each partial report is 1024 bytes in size. Since a partial report cannot fit in a single frame, each partial report needs to be divided into two fragments, so a total of four sensing report frames (and four CIR report IEs) are needed to feed back the CIR taps used for sensing measurements. In the first fragment of the first partial report, the bitmap offset field is set to 0 to indicate the start of the CIR tap window, while signaling a 16-byte CIR bitmap (instead of 32 bytes), indicating only the CIR taps in the first half of the CIR tap window and also carried in the receive report field. Then, in the second fragment of the first report, the bitmap offset field is set to 128 to indicate the center of the CIR tap window, while signaling a 16-byte (instead of 32-byte) CIR bitmap that only indicates the CIR taps in the latter half of the CIR tap window and is also carried in the receive report field. To remind the initiator that the CIR bitmap field is only partially set, the partial bitmap field in the report parameter control is set to 1. The first report fragment and the remaining report fragments are also set as described above to track different fragments of the same CIR report. The second report is fragmented similarly. In this method, since all fragments require the CIR bitmap field, a report parameter control field is present in all CIR report IEs.

[0297] It should be noted that in all the examples shown above, the specific values ​​of the fields (e.g., MID, report SN) are for illustrative purposes only, and there are no restrictions on these values.

[0298] As can be seen from the description above, the number of CIR taps carried in each CIR IE is less than the total number of CIR taps, thus achieving partial report fragmentation.

[0299] According to embodiments of the present invention, a CIR report (CIR tap) corresponding to a single sensing measurement can be divided into two or more partial CIR reports, each partial CIR report carrying all CIR taps corresponding to the receive antenna and segment pairs on a specific channel. Partial CIR reports support the division of the CIR report into smaller components, each component carrying a complete set of CIR taps for the receive antenna and segment pairs. Furthermore, a partial CIR report can also be divided into two or more CIR report fragments, each fragment carrying a finite number of CIR taps corresponding to the receive antenna and segment pairs. When fragmentation is based on a partial CIR report, even if some fragments are lost, the remaining receive fragments can still be used to recover the partial CIR report, thereby obtaining partial sensing measurements. Additionally, the partial CIR report can be compressed before fragmentation, with each fragment carrying a portion of the compressed CIR report, thus reducing overall signaling overhead.

[0300] The following will describe embodiments of products related to wireless communication methods.

[0301] Figure 29 A schematic structural diagram of a wireless communication device according to one or more embodiments of the present invention is shown. Figure 29 As shown, the communication device 2900 may include: The acquisition module 2901 is used to acquire multiple measurement report frames based on the measurement report. The measurement report is used to provide the measurement results of the response end. The measurement results are distributed in multiple measurement report frames, and the length of the corresponding measurement report frame in the multiple measurement report frames is not greater than a preset threshold.

[0302] It should be noted that the acquisition module can also be called the generation module, and the acquisition step performed by the response end in the above method embodiment can also be a generation step.

[0303] In one possible implementation of the first aspect, the acquisition module 2901 is specifically used for: Receive at least one sensing data packet from the initiator; Measure at least one sensing data packet to obtain a measurement report.

[0304] In one possible implementation, module 2901 is specifically used for: Obtain multiple parts of the measurement report based on the measurement report; For the first part of a multi-part report, perform fragmentation on the first part of the report to obtain a first number of fragments; Multiple measurement report frames are obtained based on the first number of slices in the first part of the report.

[0305] In one possible implementation, the acquisition module 2901 is also used for: Compress the second part of the report in the multi-part report.

[0306] In one possible implementation, a first measurement report frame corresponding to the first part report indicates a first parameter specific to the first part report. The first measurement report frame carries a first fragment of the first part report, and the indication of the first parameter is omitted in the other measurement report frames corresponding to the first part report, excluding the first measurement report frame.

[0307] In one possible implementation, the first measurement report frame includes a first parameter field for indicating a first parameter.

[0308] In one possible implementation, module 2901 is specifically used for: Fragment the measurement report to obtain a second number of fragments; Multiple measurement report frames are obtained based on the second number of slices.

[0309] In one possible implementation, the acquisition module 2901 is also used for: Compress the measurement report; Fragment the compressed measurement report.

[0310] In one possible implementation, a second measurement report frame among a plurality of measurement report frames indicates a second parameter reported in all parts of the measurement report, the second measurement report frame being the first measurement report frame among the plurality of measurement report frames, with the indication of the second parameter omitted in the remaining measurement report frames other than the second measurement report frame.

[0311] In one possible implementation, the second measurement report frame includes a second parameter field for indicating the second parameter.

[0312] In one possible implementation, the second measurement report frame also includes a parameter indication field for indicating whether the second parameter field exists.

[0313] In one possible implementation, the corresponding measurement report frame indicates the number of taps carried in the corresponding measurement report frame, and the indicated number of taps is less than the total number of taps to be reported.

[0314] In one possible implementation, the corresponding measurement report frame includes a tap bitmap field, which indicates the number of taps carried in the corresponding measurement report frame. The bitmap indicated by the tap bitmap field is smaller than the bitmap required to indicate the total number of taps to be reported.

[0315] In one possible implementation, the corresponding measurement report frame indicates whether the fragment carried in the corresponding measurement report frame is the first fragment from which the fragment is obtained, the number of the remaining fragments in the report from which the fragment is obtained, and the length associated with the fragment.

[0316] In one possible implementation, the corresponding measurement report frame includes: a first fragment field, used to indicate whether the fragment carried in the corresponding measurement report frame is the first fragment of the report from which the fragments are obtained; a remaining fragment field, used to indicate the number of remaining fragments in the report from which the fragments are obtained; and a fragment report length field, used to indicate the length associated with the fragment.

[0317] In one possible implementation, the corresponding measurement report frame also includes: a fragmentation indication field, used to indicate whether a first fragmentation field, remaining fragmentation fields, and fragmentation report length field exist.

[0318] In one possible implementation, the corresponding measurement report frame in a plurality of measurement report frames indicates the identifier and measurement of the corresponding measurement report frame.

[0319] In one possible implementation, the corresponding measurement report frame includes a report number for indicating the identifier of the measurement report frame and a measurement number for identifying the measurement.

[0320] In one possible implementation, the corresponding measurement report frame also indicates: the segment to which the segment of the measurement report carried by the corresponding measurement report frame belongs, the antenna for receiving the segment, and the channel on which the segment is received.

[0321] In one possible implementation, the corresponding measurement report frame includes: a fragment field for identifying the fragment to which the segment of the measurement report carried by the corresponding measurement report frame belongs; an antenna field for identifying the antenna of the response end for receiving the fragment; and a channel field for identifying the channel on which the fragment is received.

[0322] In one possible implementation, the apparatus further includes a transmitting module for: Send multiple measurement report frames to the initiating end.

[0323] The communication device can be applied to the response terminal described in the above method embodiments, or it can be the response terminal described in the above method embodiments. Those skilled in the art should understand that the relevant descriptions of the above modules in the embodiments of the present invention can be understood in conjunction with the relevant descriptions of the communication methods in the embodiments of the present invention.

[0324] Figure 30 A schematic structural diagram of a wireless communication device according to one or more embodiments of the present invention is shown. Figure 30 As shown, the communication device 3000 may include: The receiving module 3001 is used to receive multiple measurement report frames from the responding end. The multiple measurement report frames are obtained based on measurement reports. The measurement reports are used to provide the results of the measurements performed by the responding end. The measurement results are distributed in the multiple measurement report frames, and the length of the corresponding measurement report frame in the multiple measurement report frames is not greater than a preset threshold.

[0325] The communication device can be applied to the initiating end described in the above method embodiments, or it can be the initiating end described in the above method embodiments. Those skilled in the art should understand that the relevant descriptions of the above modules in the embodiments of the present invention can be understood in conjunction with the relevant descriptions of the communication methods in the embodiments of the present invention.

[0326] This invention provides a response terminal, including processing circuitry for executing any of the above-described communication methods. It should be understood that the response terminal can execute the steps performed by the response terminal in the above method embodiments, which will not be repeated here.

[0327] This invention provides an initiator, including processing circuitry for executing any of the above-described communication methods. It should be understood that the initiator can execute the steps described in the method embodiments above, which will not be repeated here.

[0328] This invention provides a communication device, including a processor and a memory. The memory stores instructions that cause the processor to execute any of the communication methods described above.

[0329] This invention provides a communication system including a responding end and an initiating end. The responding end is used to execute the steps performed by the responding end in any of the above-described communication methods, and the initiating end is used to execute the steps performed by the initiating end in any of the above-described communication methods.

[0330] This invention provides a computer-readable medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform any of the above-described communication methods.

[0331] This invention provides a computer program product including computer execution instructions, which, when executed by a processor, cause the processor to perform any of the above-described communication methods.

[0332] Although the present invention describes methods and processes by means of steps in a certain order, one or more steps in the methods and processes may be omitted or modified as appropriate. Where appropriate, one or more steps may be performed in an order other than that described.

[0333] It should be noted that the expression "at least one of A or B" as used in this document is interchangeable with the expression "A and / or B". It refers to a list in which A, or B, or both A and B can be selected. Similarly, "at least one of A, B, or C" as used in this document is interchangeable with "A and / or B and / or C" or "A, B, and / or C". It refers to a list in which: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B, and C can be selected. The same principle applies to longer lists with the same format.

[0334] Although the invention has been described at least partially in terms of method, those skilled in the art will understand that the invention is also directed to various components, whether by hardware components, software, or any combination thereof, for performing at least some aspects and features of the described methods. Accordingly, the technical solutions of the invention can be implemented in the form of a software product. Suitable software products can be stored in pre-recorded storage devices or other similar non-volatile or non-transitory computer-readable media, including DVDs, CD-ROMs, USB flash drives, removable hard drives, or other storage media. The software product includes instructions tangibly stored therein that enable a processing device (e.g., a personal computer, server, or network device) to perform the method examples disclosed herein. Machine-executable instructions can be in the form of code sequences, configuration information, or other data, which, when executed, cause a machine (e.g., a processor or other processing device) to perform the steps of the method according to the examples of the invention.

[0335] The invention may be practiced in other specific forms without departing from the subject matter of the claims. The exemplary embodiments described are to be regarded in all respects as illustrative rather than restrictive. Features selected from one or more of the above embodiments may be combined to create alternative embodiments not explicitly described, and features suitable for such combinations will be understood within the scope of the invention.

[0336] Furthermore, all values ​​and sub-ranges within the scope of the disclosure are disclosed. Additionally, although the systems, devices, and processes disclosed and shown herein may include a specific number of elements / components, systems, devices, and assemblies may be modified to include more or fewer of such elements / components. For example, although any element / component disclosed may be referenced as a single quantity, embodiments disclosed herein may be modified to include multiple such elements / components. The subject matter described herein is intended to cover and include all suitable technical variations.

[0337] Although embodiments have been described above with reference to the accompanying drawings, those skilled in the art will understand that variations and modifications may be made without departing from the scope defined by the appended claims.

Claims

1. A communication method, characterized in that, The method is applied to ultra-wideband sensing and includes: The initiating end receives multiple measurement report frames from the responding end, wherein the multiple measurement report frames are obtained based on a measurement report, wherein the measurement report is used to provide the result of the measurement performed by the responding end, the multiple measurement report frames carry the result of the measurement, and the length of the corresponding measurement report frame in the multiple measurement report frames is not greater than the payload limit of the measurement report frame. The initiating end obtains the measurement report.

2. The method according to claim 1, characterized in that, The method further includes: The initiating end assembles the multiple measurement report frames.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The initiating end decompresses the multiple measurement report frames.

4. The method according to any one of claims 1 to 3, characterized in that, The corresponding measurement report frame includes a first fragment field, which indicates whether the fragment carried in the corresponding measurement report frame is the first fragment of the measurement report.

5. The method according to any one of claims 1 to 4, characterized in that, The corresponding measurement report frame includes a remaining fragment field indicating the number of remaining fragments in the measurement report.

6. The method according to any one of claims 1 to 5, characterized in that, The corresponding measurement report frame includes a measurement number used to identify the measurement.

7. The method according to any one of claims 1 to 6, characterized in that, The corresponding measurement report frame includes: a fragment field for identifying the fragment to which the segment of the measurement report carried by the corresponding measurement report frame belongs; an antenna field for identifying the antenna of the response end for receiving the fragment; and a channel field for identifying the channel on which the fragment is received.

8. The method according to any one of claims 1 to 7, characterized in that, The corresponding measurement report frame includes a CIR bitmap field and a CIR tap field. The CIR tap field includes CIR tap values, and each CIR tap value corresponds to a bit in the CIR bitmap that is 1.

9. A communication device, characterized in that, The communication device is used in ultra-wideband sensing and includes: A receiving module is configured to receive multiple measurement report frames from a response end, wherein the multiple measurement report frames are obtained based on a measurement report, wherein the measurement report is used to provide the result of a measurement performed by the response end, the multiple measurement report frames carry the result of the measurement, and the length of a corresponding measurement report frame in the multiple measurement report frames is not greater than the payload limit of the measurement report frame. The acquisition module is used to acquire the measurement report.

10. The communication device according to claim 9, characterized in that, The communication device further includes: The acquisition module is used to assemble the plurality of measurement report frames.

11. The communication device according to claim 9 or 10, characterized in that, The communication device further includes: The acquisition module is used to decompress the plurality of measurement report frames.

12. The communication device according to any one of claims 9 to 11, characterized in that, The corresponding measurement report frame includes a first fragment field, which indicates whether the fragment carried in the corresponding measurement report frame is the first fragment of the measurement report.

13. The communication device according to any one of claims 9 to 12, characterized in that, The corresponding measurement report frame includes a remaining fragment field indicating the number of remaining fragments in the measurement report.

14. The communication device according to any one of claims 9 to 13, characterized in that, The corresponding measurement report frame includes a measurement number used to identify the measurement.

15. The communication device according to any one of claims 9 to 14, characterized in that, The corresponding measurement report frame includes: a fragment field for identifying the fragment to which the segment of the measurement report carried by the corresponding measurement report frame belongs; an antenna field for identifying the antenna of the response end for receiving the fragment; and a channel field for identifying the channel on which the fragment is received.

16. The communication device according to any one of claims 9 to 15, characterized in that, The corresponding measurement report frame includes a CIR bitmap field and a CIR tap field. The CIR tap field includes CIR tap values, and each CIR tap value corresponds to a bit in the CIR bitmap that is 1.

17. An initiator, characterized in that, Includes a module for performing the method according to any one of claims 1 to 8.

18. A communication device, characterized in that, It includes a processor and memory. The memory stores instructions that enable the processor to execute the method according to any one of claims 1 to 8.

19. A computer-readable medium storing computer-executable instructions, characterized in that, When the computer execution instructions are executed by the processor, the processor performs the method according to any one of claims 1 to 8.

20. A technical computing program product, comprising computer-executable instructions, characterized in that, When the computer execution instructions are executed by the processor, the processor performs the method according to any one of claims 1 to 8.

Images