Communication method for uwb and related products

Abstract

The application discloses a communication method for UWB and related products. The application can be applied to a UWB-based wireless personal area network system, a sensing system, a positioning system, a ranging system, or a communication system, and can also be applied to a wireless local area network system supporting a next-generation Wi-Fi protocol of IEEE 802.11ax, such as 802.11be, Wi-Fi7, 802.11be next generation, Wi-Fi8, and other 802.11 series protocols. The method comprises the following steps: generating indication information, wherein the indication information is used to indicate that a frame counter (FC) is constructed based on a first field in a first message, and the first field is used to indicate the type of the first message; and sending the indication information. The method provided in the application embodiment can save signaling overhead.

Description

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

[0002] This application relates to the field of communications, and more particularly to communication methods and related products for UWB. Background Technology

[0003] Ultra-wideband (UWB) technology is a wireless communication and sensing ranging technology that uses nanosecond-level non-sinusoidal narrow pulses to transmit signals, thus occupying a very wide frequency spectrum. Due to its narrow pulse width and extremely low radiation spectral density, UWB systems possess advantages such as strong multipath resolution, low power consumption, and strong security, attracting widespread attention in the industry. The Institute of Electrical and Electronics Engineers (IEEE) has incorporated UWB technology into its IEEE 802 series of wireless standards, releasing the UWB-based wireless personal area network (WPAN) standard IEEE 802.15.4a, and its evolved version IEEE 802.15.4z. Currently, the development of the next-generation UWB WPAN standard, IEEE 802.15.4ab, is also on the agenda. The IEEE 802.15.4ab standard plans to comprehensively upgrade UWB.

[0004] Because of the large bandwidth of ultra-wideband (UWB) systems, UWB devices require ultra-high-speed data transmission and reception capabilities. However, impulse radio ultra-wideband (IR-UWB) systems based on pulse transmission have low spectral efficiency. When transmitting the same information, IR-UWB systems require significantly higher power consumption compared to other narrowband short-range protocols (such as Bluetooth or Zifeng protocols). For ranging or sensing scenarios, the accuracy of measurement or sensing is highly dependent on the signal bandwidth; the larger the bandwidth, the higher the accuracy of sensing or ranging. Therefore, it is considered to transmit and receive the reference signal for ranging or sensing through a UWB system, while transmitting all other data through narrowband (NB) protocols. This approach ensures both the accuracy of ranging and sensing and saves power. The aforementioned UWB technology solution combining narrowband-assisted multi-millisecond ultra-wideband (NBA-MMS UWB) is also known as narrowband-assisted multi-millisecond ultra-wideband (NBA-MMS UWB).

[0005] In NBA-MMS UWB measurement scenarios, to reduce the duty cycle of the NB signal, messages transmitted via the NB protocol, such as start-of-ranging (SOR) messages, can be based on compressed physical layer service data unit (PSDU) format. However, messages based on compressed PSDU format have significant signaling overhead. Summary of the Invention

[0006] This application discloses a communication method and related products for UWB, which can solve the problem of FC construction based on compressed PSDU format messages and has less signaling overhead.

[0007] In a first aspect, embodiments of this application provide a communication method for Ultra Wideband (UWB), the method comprising: generating indication information, the indication information being used to indicate the construction of a frame counter (FC) based on a first field in a first message, the first field being used to indicate the type of the first message; and sending the indication information.

[0008] In this embodiment of the application, sending indication information for instructing the construction of an FC based on the first field in the first message can avoid carrying the packet number (PN) field in the first message, thereby saving signaling overhead.

[0009] In one possible implementation of the first aspect, the method further includes: sending a second message, the second message including a second field for indicating a deadline for receiving a start-of-ranging (SOR) message.

[0010] In this implementation, the second field is used to indicate the deadline for receiving the SOR message, which can save the waiting time for the SOR message and thus save power consumption.

[0011] In one possible implementation of the first aspect, the second message further includes a field for indicating whether the second field exists.

[0012] In this implementation, the second message also includes a field indicating whether the second field exists, so that the receiving end knows whether the second field exists.

[0013] In one possible implementation of the first aspect, the second message is an advertising confirmation (ADV-CONF) message.

[0014] In this implementation, the second message is an ADV-CONF message, which can reuse existing ADV-CONF messages and has little impact on the existing protocol.

[0015] In one possible implementation of the first aspect, sending the indication information includes: sending the first message, wherein the first message includes the indication information.

[0016] In this implementation, the first message includes indication information, eliminating the need for additional messages to carry the indication information and reducing signaling overhead.

[0017] Secondly, embodiments of this application provide another communication method for Ultra Wideband (UWB), the method comprising: receiving indication information, the indication information being used to indicate the construction of a Functional Communication Unit (FC) based on a first field in a first message, the first field being used to indicate the type of the first message; and constructing the FC according to the indication information.

[0018] In this embodiment of the application, the FC is constructed according to the instruction information. The first message does not need to carry the PN field, which can save signaling overhead.

[0019] In one possible implementation of the second aspect, constructing the FC according to the indication information includes: constructing the FC based on the first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message, according to the indication information.

[0020] In this implementation, the FC is constructed based on the first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message. The first message does not need to carry the PN field, which can save signaling overhead.

[0021] In one possible implementation of the second aspect, receiving the indication information includes: receiving the first message, wherein the first message includes the indication information.

[0022] In this implementation, the first message includes indication information, eliminating the need for additional messages to carry the indication information and reducing signaling overhead.

[0023] In one possible implementation of the first or second aspect, the indication information is used to indicate the construction of an FC based on a first field in a first message, including: the indication information is used to indicate the construction of an FC based on the first field and the sorting information of the list element corresponding to the first message in the message list.

[0024] In this implementation, the indication information is used to indicate the sorting information of the list element corresponding to the first message in the message list, based on the first field and the first message in the message list, to construct the FC; the first message does not need to carry the PN field and the measurement wheel index, which can save signaling overhead.

[0025] In one possible implementation of the first or second aspect, different list elements in the message list correspond to different devices.

[0026] In one possible implementation of the first or second aspect, each list element in the message list includes a device identifier.

[0027] In one possible implementation of the first or second aspect, the message list includes a third message sent before the first message is sent.

[0028] In one possible implementation of the first or second aspect, the third message is the ADV-CONF message during the NBA-MMS UWB measurement process.

[0029] In one possible implementation of the first or second aspect, the indication information is further used to indicate whether the first message includes a measuring wheel identifier.

[0030] In this implementation, the indication information is also used to indicate whether the first message includes a measuring wheel identifier, so that the receiving end can know whether the first message includes a measuring wheel identifier based on the indication information.

[0031] In one possible implementation of the first or second aspect, the indication information is further used to indicate whether the first message includes a measurement block identifier.

[0032] In this implementation, the indication information is also used to indicate whether the first message includes a measurement block identifier, so that the receiving end can know whether the first message includes a measurement block identifier based on the indication information.

[0033] Thirdly, embodiments of this application provide another communication method for Ultra Wideband (UWB), the method comprising: receiving a first message; constructing an FC based on a first field in the first message, wherein the first field is used to indicate the type of the first message.

[0034] In this embodiment of the application, an FC is constructed based on the first field in the first message. The first message does not need to carry the PN field, which can save signaling overhead.

[0035] In one possible implementation of the third aspect, constructing the frame count FC based on the first field in the first message includes: constructing the FC based on the first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message.

[0036] In one possible implementation of the third aspect, constructing a frame count FC based on a first field in the first message includes: constructing the FC based on the first field and the sorting information of the list element corresponding to the first message in the message list.

[0037] In one possible implementation of the first, second, or third aspect, the first message is a message based on a compressed PSDU format.

[0038] In one possible implementation of the first, second, or third aspect, the first message is a control message during the NBA-MMS UWB measurement process.

[0039] In one possible implementation of the first, second, or third aspect, the first message is any one of a ranging initiation SOR message, a polling / initiation POLL message, a report message, or a response message.

[0040] Fourthly, embodiments of this application provide another communication method for Ultra Wideband (UWB), the method comprising: generating indication information, the indication information being used to indicate the sorting information of a list element corresponding to a first message in a message list in the message list, constructing a Functional Joint (FC); and sending the indication information.

[0041] In this embodiment of the application, the indication information is used to indicate the sorting information of the list element corresponding to the first message in the message list in the message list, and to construct FC, thereby avoiding the explicit carrying of the Round Index and saving signaling overhead.

[0042] Fifthly, embodiments of this application provide another communication method for Ultra Wideband (UWB), the method comprising: receiving indication information, the indication information being used to indicate the sorting information of a list element corresponding to a first message in a message list in the message list, constructing a Functional Collective (FC); and constructing the FC according to the indication information.

[0043] In this embodiment, the FC is constructed according to the instruction information, avoiding the need to explicitly carry the measurement wheel index, thus saving signaling overhead.

[0044] In one possible implementation of the fifth aspect, constructing the FC according to the indication information includes: constructing the FC based on the measurement slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message, according to the indication information.

[0045] In this implementation, an FC is constructed based on the measurement slot identifier, sorting information, and measurement block identifier corresponding to the first message; this avoids explicitly carrying the measurement round index, thus saving signaling overhead.

[0046] In a sixth aspect, embodiments of this application provide another communication method for Ultra Wideband (UWB), the method comprising: receiving a first message; and constructing an FC based on the sorting information of the list element corresponding to the first message in the message list.

[0047] In this embodiment, the FC is constructed based on the sorting information of the list element corresponding to the first message in the message list; this avoids explicitly carrying the measurement round index, thus saving signaling overhead.

[0048] In one possible implementation of the sixth aspect, constructing a frame count FC based on the sorting information of the list element corresponding to the first message in the message list includes: constructing the FC based on the measurement slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message.

[0049] In one possible implementation of the sixth aspect, constructing a frame count FC based on the sorting information of the list element corresponding to the first message in the message list includes: constructing the FC based on a first field in the first message, the sorting information, and the measurement block identifier corresponding to the first message.

[0050] In one possible implementation of the fourth, fifth, or sixth aspect, different list elements in the message list correspond to different devices.

[0051] In one possible implementation of the fourth, fifth, or sixth aspect, each list element in the message list includes a device identifier.

[0052] In one possible implementation of the fourth, fifth, or sixth aspect, the message list includes a third message sent prior to the first message.

[0053] In one possible implementation of the fourth, fifth, or sixth aspect, the third message is the ADV-CONF message during the NBA-MMS UWB measurement process.

[0054] In one possible implementation of the fourth, fifth, or sixth aspect, the indication information is further used to indicate whether the first message includes a measuring wheel identifier.

[0055] In this implementation, the indication information is also used to indicate whether the first message includes a measuring wheel identifier, so that the receiving end can know whether the first message includes a measuring wheel identifier based on the indication information.

[0056] In one possible implementation of the fourth, fifth, or sixth aspect, the indication information is further used to indicate whether the first message includes a measurement block identifier.

[0057] In this implementation, the indication information is also used to indicate whether the first message includes a measurement block identifier, so that the receiving end can know whether the first message includes a measurement block identifier based on the indication information.

[0058] In one possible implementation of the fourth, fifth, or sixth aspect, the indication information is included in the first message.

[0059] In one possible implementation of the fourth, fifth, or sixth aspect, the first message is a message based on a compressed PSDU format.

[0060] In one possible implementation of the fourth, fifth, or sixth aspect, the first message is a control message during the NBA-MMS UWB measurement process.

[0061] In one possible implementation of the fourth, fifth, or sixth aspect, the first message is any one of an SOR message, a polling / initiating POLL message, a report message, or a response message.

[0062] In a seventh aspect, embodiments of this application provide a communication device that has the function of implementing the behavior described in the first aspect method embodiment. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate indication information, the indication information being used to indicate the construction of an FC based on a first field in a first message, the first field being used to indicate the type of the first message; the transceiver module is used to send the indication information.

[0063] In one possible implementation of the seventh aspect, the transceiver module is further configured to send a second message, the second message including a second field indicating a deadline for receiving the SOR message.

[0064] For possible implementations of the communication device in the seventh aspect, please refer to the various possible implementations in the first aspect.

[0065] For the technical effects of the various possible implementations of the seventh aspect, please refer to the introduction of the technical effects of the first aspect or the various possible implementations of the first aspect.

[0066] Eighthly, embodiments of this application provide a communication device that has the function of implementing the behavior described in the second aspect of the method embodiments. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive indication information, the indication information being used to instruct the construction of an FC based on a first field in a first message, the first field being used to indicate the type of the first message; the processing module is used to construct the FC according to the indication information.

[0067] In one possible implementation of the eighth aspect, the processing module is specifically configured to construct an FC based on the indication information, the first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message.

[0068] In one possible implementation of the eighth aspect, the transceiver module is specifically configured to receive the first message, the first message including the indication information.

[0069] For possible implementations of the communication device in the eighth aspect, please refer to the various possible implementations in the second aspect.

[0070] For the technical effects of the various possible implementations of the eighth aspect, please refer to the introduction of the technical effects of the second aspect or the various possible implementations of the second aspect.

[0071] Ninthly, embodiments of this application provide a communication device that has the function of implementing the behavior described in the third aspect of the method embodiments. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first message; the processing module is used to construct an FC based on a first field in the first message, the first field indicating the type of the first message.

[0072] In one possible implementation of the ninth aspect, the processing module is specifically configured to construct an FC based on the first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message.

[0073] In one possible implementation of the ninth aspect, the processing module is specifically configured to construct an FC based on the first field and the sorting information of the list element corresponding to the first message in the message list.

[0074] For possible implementations of the communication device in the ninth aspect, please refer to the various possible implementations in the third aspect.

[0075] For the technical effects of the various possible implementations of the ninth aspect, please refer to the introduction of the technical effects of the third aspect or the various possible implementations of the third aspect.

[0076] Tenthly, embodiments of this application provide a communication device that has the function of implementing the behavior described in the fourth aspect of the method embodiments. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate indication information, the indication information being used to indicate the sorting information of the list element corresponding to the first message in the message list, and to construct an FC; the transceiver module is used to send the indication information.

[0077] For possible implementations of the communication device in the tenth aspect, please refer to the various possible implementations in the fourth aspect.

[0078] For the technical effects of the various possible implementations of the tenth aspect, please refer to the introduction of the technical effects of the fourth aspect or the various possible implementations of the fourth aspect.

[0079] Eleventhly, embodiments of this application provide a communication device that has the function of implementing the behavior described in the fifth aspect of the method embodiments. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The function of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive indication information, the indication information being used to indicate the sorting information of the list element corresponding to the first message in the message list, and to construct an FC (Focus Function). The processing module is used to construct an FC according to the indication information.

[0080] In one possible implementation of the eleventh aspect, the processing module is specifically configured to construct an FC based on the indication information, the measurement slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message.

[0081] For possible implementations of the communication device in the eleventh aspect, please refer to the various possible implementations in the fifth aspect.

[0082] For the technical effects of the various possible implementations of the eleventh aspect, please refer to the introduction of the technical effects of the fifth aspect or the various possible implementations of the fifth aspect.

[0083] In a twelfth aspect, embodiments of this application provide a communication device that has the function of implementing the behavior described in the sixth aspect method embodiment. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first message; the processing module is used to construct an FC (Focus Function) based on the sorting information of the list element corresponding to the first message in the message list.

[0084] In one possible implementation of the twelfth aspect, the processing module is specifically configured to construct an FC based on the measurement slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message.

[0085] In one possible implementation of the twelfth aspect, the processing module is specifically configured to construct an FC based on the first field in the first message, the sorting information, and the measurement block identifier corresponding to the first message.

[0086] For possible implementations of the communication device in aspect 12, please refer to the various possible implementations in aspect 6.

[0087] For the technical effects of the various possible implementations of the twelfth aspect, please refer to the introduction of the technical effects of the sixth aspect or the various possible implementations of the sixth aspect.

[0088] In a thirteenth aspect, embodiments of this application provide another communication device, the communication device including a processor coupled to a memory for storing a program or instructions, which, when executed by the processor, cause the communication device to perform the methods shown in any one of the first to sixth aspects above.

[0089] In this embodiment of the application, during the execution of the above method, the process of sending information (or signals) can be understood as a process of outputting information based on processor instructions. When outputting information, the processor sends the information to the transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, it may require further processing before being input into the processor.

[0090] Unless otherwise specified, or unless their actual function or internal logic in the relevant description is contradicted, the sending and / or receiving operations involved by the processor can generally be understood as processor instruction output.

[0091] In implementation, the processor described above can be a processor specifically designed to execute these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. For example, the processor can also be used to execute a program stored in memory, which, when executed, causes the communication device to perform the methods as shown in the first aspect or any possible implementation thereof.

[0092] In one possible implementation, the memory is located outside the aforementioned communication device. In another possible implementation, the memory is located inside the aforementioned communication device.

[0093] In one possible implementation, the processor and memory may be integrated into a single device; that is, the processor and memory may be integrated together.

[0094] In one possible implementation, the communication device further includes a transceiver for receiving or transmitting signals, etc.

[0095] In a fourteenth aspect, embodiments of this application provide another communication device, which includes a processing circuit and an interface circuit. The interface circuit is used to acquire data or output data; the processing circuit is used to perform the methods shown in any one of the first to sixth aspects above.

[0096] In a fifteenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed, cause a computer to perform the method as described in any one of the first to sixth aspects above.

[0097] In a sixteenth aspect, embodiments of this application provide a computer program product comprising a computer program, the computer program including program instructions that, when executed, cause a computer to perform the method as described in any one of the first to sixth aspects above.

[0098] In a seventeenth aspect, embodiments of this application provide a communication system including the communication device described in the seventh aspect or any possible implementation thereof, and the communication device described in the eighth aspect or any possible implementation thereof.

[0099] In an eighteenth aspect, embodiments of this application provide a communication system including the communication device described in the tenth aspect or any possible implementation thereof, and the communication device described in the eleventh aspect or any possible implementation thereof.

[0100] In a nineteenth aspect, embodiments of this application provide a chip including a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method as shown in any one of the first to sixth aspects above. Attached Figure Description

[0101] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0102] Figure 1 This is a schematic diagram of the various stages of a distance measuring wheel in the prior art;

[0103] Figure 2 This is a schematic diagram of a distance measuring block in the prior art;

[0104] Figure 3 This is a schematic diagram of the initialization process for NBA-MMS UWB ranging.

[0105] Figure 4A This is a schematic diagram of a one-to-many NBA-MMS UWB ranging method;

[0106] Figure 4B This is a schematic diagram of a one-to-many NBA-MMS UWB ranging method based on an interleaved pattern.

[0107] Figure 5 A schematic diagram illustrating an example of a star topology;

[0108] Figure 6 A schematic diagram illustrating an example of a point-to-point topology or a mesh topology;

[0109] Figure 7 An example of a UWB system to which the technical solutions provided in the embodiments of this application are applicable;

[0110] Figure 8 A flowchart illustrating the communication method interaction for UWB provided in this application embodiment;

[0111] Figure 9 A schematic diagram of an NBA-MMS UWB ranging process provided in this application embodiment;

[0112] Figure 10 Another communication method interaction flow for UWB provided in the embodiments of this application;

[0113] Figure 11 Another communication method interaction flow for UWB provided in the embodiments of this application;

[0114] Figure 12 Another communication method interaction flow for UWB provided in the embodiments of this application;

[0115] Figure 13 A schematic diagram of the initialization process for pre-configuring one-to-many NBA-MMS UWB ranging;

[0116] Figure 14 Another communication method interaction flow for UWB provided in the embodiments of this application;

[0117] Figure 15 Another communication method interaction flow for UWB provided in the embodiments of this application;

[0118] Figure 16 This is a schematic diagram of the structure of a communication device 1600 provided in an embodiment of this application;

[0119] Figure 17 A schematic diagram of another communication device 170 provided in the embodiments of this application;

[0120] Figure 18 This is a schematic diagram of another communication device 180 provided in an embodiment of this application. Detailed Implementation

[0121] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are only used to distinguish different objects and not to describe a specific order. It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and inherent logic. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0122] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0123] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to and includes any or all possible combinations of one or more of the listed items. For example, “A and / or B” can mean: the presence of only A, the presence of only B, and the presence of both A and B, where A and B can be singular or plural. The term “multiple” as used in this application refers to two or more. In the textual description of this application, the character “ / ” generally indicates that the preceding and following objects are in an “or” relationship.

[0124] It is understood that in the various embodiments of this application, "B corresponding to A" means that there is a correspondence between A and B, and B can be determined based on A. However, it should also be understood that determining (or generating) B based on (or on) A does not mean that B is determined (or generated) solely based on (or on) A; B can also be determined (or generated) based on (or on) A and / or other information.

[0125] To facilitate understanding of the solutions in this application, the terminology and technical solutions involved in the embodiments of this application will be introduced first below.

[0126] Ranging round, positioning round, sensing round, measurement cycle.

[0127] In the IEEE 802.15.4z standard, a single ranging process is defined as a ranging round. A ranging round is defined as a period of sufficient duration to complete one entire range-measurement cycle involving the set of ERDEVs participating in the ranging exchange. The smallest processing unit for each ranging round is a ranging slot. A ranging round consists of three phases: the ranging control phase, the ranging phase, and the measurement report phase. Figure 1 This is a schematic diagram of the various stages of a distance measuring wheel in the prior art. For example... Figure 1 As shown. In the IEEE 802.15.4z standard, the ranging control phase includes one ranging time slot, while in the currently discussed IEEE 802.15.4ab standard, the ranging control phase can include more than one ranging time slot.

[0128] exist Figure 1 In the first time slot of the ranging wheel shown, the controller sends a ranging control message (RCM). The RCM may carry updates about the wheel structure of this ranging wheel, such as updates to the wheel's round duration.

[0129] The new and old ranging rounds (hereinafter referred to as "rounds") can be adjacent in time or not. The duration of different rounds can be the same or different. The following explanation assumes that different rounds have the same duration.

[0130] Among them, the cases where the new and old ranging rounds (hereinafter referred to as rounds) are not adjacent in time are determined by... Figure 2 As shown. Figure 2 This is a schematic diagram of a distance measuring block in the prior art. (Example) Figure 2As shown, the ranging block can be a time structure containing multiple ranging wheels. Optionally, the ranging block may repeat periodically. Optionally, the duration of each ranging wheel in the ranging block may be equal. Figure 2 As shown, for a specific ranging process, the initiator and responder will operate within a ranging wheel of a ranging block, for example... Figure 2 The example shown is round 1. In this application, the initiator can be called the initiating end, i.e., the UWB device that initiates the ranging / sensing / communication process. During the ranging / sensing / communication process, the initiating end can be either a transmitter or a receiver. In this application, the initiator can also be called the responding end, the UWB device that responds to the ranging / sensing / communication process initiated by the UWB initiating end device. During the ranging / sensing / communication process, the responding end can be either a transmitter or a receiver. After this ranging round is completed, the specific ranging process will be carried out in round 1 of the next ranging block. Figure 2 As can be seen, two consecutive round 1 operations are not contiguous in time; that is, there is a time interval between two consecutive round 1 operations. During the time slot between two consecutive round 1 operations, the device can turn off the receiver and enter sleep mode to save power. The duration of adjacent ranging blocks can be the same or different. For example, ranging blocks with different durations can be located in a hyperblock. The following explanation assumes that adjacent ranging blocks have the same duration.

[0131] Before initiating (or activating) NBA-MMS UWB ranging, the relevant devices need to undergo an initialization and setup process. Taking the initiator as the controller, the initiator first needs to broadcast an announcement message to inform all responders that NBA-MMS UWB ranging needs to be initiated. This broadcast announcement message can be carried by an advertisement poll (ADV-POLL) message. After receiving the ADV-POLL message, if a responder needs to initiate ranging, it will send an advertisement response (ADV-RESP) message back to the initiator. In this ADV-RESP message, the responder will carry the required parameter configuration information. After receiving the ADV-RESP message, the initiator can decide whether to accept the parameter configuration proposed by the responder and can inform the responder of the final parameter configuration result through a start-of-ranging (SOR) message. The SOR message can carry either a parameter acknowledgment message to the responder's ADV-RESP message, or a parameter modification / update message to the responder's ADV-RESP message. After receiving the SOR message, the initiator and responder can initiate the NBA-MMS UWB ranging process after a certain interval. The length of this interval is determined by the Time offset to MMS POLL information in the SOR message. The NBA-MMS UWB ranging initialization process described above is as follows: Figure 3 As shown. Figure 3 This is a schematic diagram of the initialization process for NBA-MMS UWB ranging.

[0132] The application scenarios for NBA-MMS UWB ranging can be either one-to-one, where one initiator corresponds to one responder, or one-to-many, where one initiator corresponds to multiple responders, as follows: Figure 4A As shown. Figure 4A This is a schematic diagram of a one-to-many NBA-MMS UWB ranging method.

[0133] Figure 4AIn the one-to-many NBA-MMS UWB ranging scenario, the initiator and each responder sequentially conduct NBA-MMS UWB ranging. That is, the initiator and each responder will complete the following processes: POLL (Initiation by Request) and RESP (Response by Request) message exchanges, multi-millisecond (MMS) block exchanges, ranging, and ranging result reporting (carried in Report messages). In this paper, the response message can be referred to as a RESP message, a Response message, or a RESPONSE message. Ranging result reporting includes both the responder's Report message to the initiator and the initiator's Report message to the responder. Figure 4A The distance measurement process shown can be referred to as one-to-many NBA-MMS UWB distance measurement based on concatenation. It should be noted that this application is also applicable to other one-to-many distance measurement processes, such as one-to-many NBA-MMS UWB distance measurement based on interlacing. See [reference needed]. Figure 4B . Figure 4B This is a schematic diagram of a one-to-many NBA-MMS UWB ranging method based on an interleaved pattern. Figure 4B As shown, in one-to-many NBA-MMS UWB ranging based on interleaved mode, each responder sends MMS blocks sequentially, instead of waiting for the previous responder to send all MMS blocks before the next responder sends them. This is illustrated in various embodiments of this application. The following description uses one-to-many NBA-MMS UWB based on splicing mode as an example. The methods in related embodiments are also applicable to one-to-many NBA-MMS UWB processes based on interleaved mode, and will not be repeated here.

[0134] In this embodiment, a single positioning process, i.e., the process of completing a positioning task, is defined as a positioning wheel. The positioning wheel can have other names, and this application does not limit its usage. A positioning wheel can be a time period (or time cycle) sufficient to complete a full positioning task. The meaning of a positioning wheel is similar to that of a ranging wheel, the difference being that one corresponds to a time cycle for ranging, and the other to a time cycle for positioning. The minimum processing time unit for each positioning wheel is a positioning slot. A positioning wheel can be divided into three phases: a positioning control phase, a positioning phase, and a positioning report phase.

[0135] In this embodiment, a single sensing process, i.e., the process of completing a sensing task, is defined as a sensing wheel. The sensing wheel can have other names, and this application does not limit its usage. A sensing wheel can be a time period (or time cycle) sufficient to complete a full sensing task. The meaning of a sensing wheel is similar to that of a ranging wheel, the difference being that one corresponds to a time cycle for ranging, and the other to a time cycle for sensing. The minimum processing time unit for each sensing wheel is a sensing slot. A sensing wheel can be divided into three phases: a sensing control phase, a sensing phase, and a sensing report phase.

[0136] The measurement cycle refers to the time period during which one or more UWB devices complete one or more measurement tasks. These measurement tasks can be ranging, positioning, sensing, etc. The measurement cycle can be a ranging wheel, a positioning wheel, or a sensing wheel. Note that in the following text, the ranging wheel can be replaced with the sensing wheel, the positioning wheel, or the measurement cycle (which can be called the measurement wheel); correspondingly, the ranging task can be replaced with the sensing task, the positioning task, or the measurement task.

[0137] Furthermore, it should be noted that the names of different stages within a single measuring wheel (e.g., ranging wheel, sensing wheel, positioning wheel, etc.) are merely examples and do not constitute any limitation on the scope of protection of this application. For example, the aforementioned measurement control stage can be understood as the stage used to configure the required parameters in the measuring wheel. As another example, the aforementioned measurement stage can be understood as the stage used to perform the measurement. Yet another example, the aforementioned measurement result reporting stage can be understood as the stage used to report the measurement results, and can also be referred to as the end of the measurement stage. Additionally, it should be noted that in the various embodiments of this application, the size of each field represents the number of bits occupied by each field.

[0138] The compressed header cell message format.

[0139] To reduce the duty cycle of the NB signal, ADV-POLL, ADV-RESP, SOR, and Report messages can be carried using compressed header information element (IE) messages, as shown in Table 1-1. Table 1-1 is an example of a compressed header information element message format.

[0140] Table 1-1

[0141] SHR PHR Compressed PSDU

[0142] In this context, SHR (synchronization header) represents the synchronization header, PHR is the PHY header, PSDU (PHY service data unit) represents the physical layer service data unit, and PHY (physical layer) is the physical layer. An example format for compressed PSDU is shown in Table 1-2 below.

[0143] Table 1-2

[0144] Octets:1 Octets:2 Octets:1 Variable Octets:2 Frame Control Address Message ID Content CRC

[0145] The Frame Control field is used to control the format of the header elements. The Frame Control field occupies one byte.

[0146] The Address field represents the device address of the device that receives the messages shown in Table 1-1. The Address field occupies two bytes.

[0147] Message ID field (also known as message identification field): Represents the message type shown in Table 1-1. In other words, the MessageID field indicates the message type corresponding to the current compressed PSDU field. For example, the Message ID field indicates the type and size of the data content carried by the Content field in Table 1-2. In the example shown in Table 1-2, the Message ID field occupies one byte. Content field: The data content carried by the compressed PSDU. The size of this field is variable, determined by the message content corresponding to the Message ID field.

[0148] The CRC field, also known as the cyclic redundancy check field, is used to check for errors in the compressed PSDU in Table 1-2. The CRC field occupies two bytes.

[0149] As shown in Tables 1-1 and 1-2, messages (or data packets) based on compressed PSDU format do not contain a separate frame counter (FC) field. The absence of the FC field in compressed PSDU format messages means that the FC cannot be directly used to construct a nonce (a once-in-a-lifetime random number). In authentication protocols, the nonce is a random or pseudo-random number to prevent replay attacks. The nonce is used to implement message encryption / authentication. In this paper, authentication and verification have the same meaning.

[0150] To address the issue that messages based on compressed PSDU format cannot be directly constructed using FC, an existing technical solution (hereinafter referred to as the prior art) is as follows: Based on the different timing structure characteristics of NBA-MMS ranging in the initialization phase and the measurement cycle phase, different methods are used to construct nonces for messages based on compressed PSDU format transmitted in the corresponding phases.

[0151] In existing technologies, NBA-MMS ranging employs the following scheme for constructing nonces for messages based on compressed PSDU format during the initialization phase: For messages transmitted during the initialization phase, such as SOR messages, ADV-POLL messages, ADV-RESP messages, and ADV-CONF messages, an explicit packet number (PN) field is added to the open payload (i.e., the unencrypted payload). The PN field is used to construct the nonce, thus solving the nonce construction problem for the aforementioned compressed PSDU format messages. Taking the SOR message in Table 2 as an example, the SOR message contains the PN field. Table 2 is a schematic table of the PSDU format for the SOR message.

[0152] Table 2

[0153]

[0154] The Message ID field in Table 2 has the same meaning as the Message ID field in Table 1-2. The Message ID field in Table 2 occupies 7 bits. The Address field in Table 2 has the same meaning as the Address field in Table 1-2.

[0155] The Security Enable field indicates whether the current message (i.e., the SOR message in Table 2) uses security encryption measures (such as encryption / authentication). For example, when the value of the Security Enable field is 0, the Security Enable field indicates that the current message does not use security encryption measures; when the value of the Security Enable field is 1, the Security Enable field indicates that the current message uses security encryption measures.

[0156] The PN field is used by the receiver to construct the Nonce, which is used for authentication / authorization of the current message. The receiver is the device that receives the SOR message in Table 2. The PN field occupies 4 bits.

[0157] Secured Payload field: The encrypted content. The Secured Payload field contains the encrypted content of the current message. The length of the Secured Payload field is variable.

[0158] The MIC (message integrity code) field is used to verify the authenticity of a frame and whether there are any errors. The MIC field occupies 2 bits.

[0159] One format for the Nonce based on the PN field shown in Table 2 is shown in Table 3.

[0160] Table 3

[0161] Octets:8 4 1 Source Address PN Nonce Security Level

[0162] Source Address field: Used to indicate the extended address of the device (i.e., the sender) that sent the frame to be verified.

[0163] PN field: Used by the receiver to construct the Nonce. The PN field serves the function of the missing FC field in the compressed PSDU.

[0164] The Nonce Security Level field indicates the security measures taken for the messages shown in Table 2.

[0165] As shown in Table 2, by introducing the PN field into the SOR message, the FC used in the Nonce shown in Table 3 can be constructed, thereby enabling subsequent encryption / authentication of the frame (i.e., the SOR message shown in Table 2).

[0166] The existing NBA-MMS ranging technology constructs nonces for messages based on compressed PSDU format during the measurement cycle as follows: For ranging control messages such as POLL, Response, and Report messages, the nonce is constructed based on prior knowledge of timing information such as slot index, round index, and block index related to the ranging process. In other words, for ranging control messages such as POLL, Response, and Report messages, there is no need to add an explicit PN field for nonce construction in the public payload of these messages. For example, before sending ranging control messages such as POLL, Response, and Report messages, a SOR message carrying timing information such as slot index, round index, and block index is sent for scheduling management and FC construction of POLL / Response / Report messages during the measurement cycle (described below). After receiving the SOR message, the receiving end can obtain the timing information such as slot index, round index, and block index related to the ranging process based on the received SOR message. Taking the Report message shown in Table 4 as an example, the format of the nonce constructed for this Report message is shown in Table 5.

[0167] Table 4

[0168]

[0169] In Table 4, the fields such as Message ID, Security Enable, and Address are the same as those in Table 2 above, and will not be repeated here.

[0170] Table 5

[0171] Octets:8 Bits: 0-7 8-23 24-39 Source Address Slot Index Round Index Block Index

[0172] In Table 5, the Source Address field represents the extended address of the device sending the frame to be verified, the SlotIndex field represents the Slot Index (e.g., measurement slot index) corresponding to the frame to be verified, the Round Index field represents the Round Index (e.g., measurement round index) corresponding to the frame to be verified, and the Block Index field represents the Block Index (e.g., measurement block index) corresponding to the frame to be verified. As shown in Table 5, the Nonce constructed for a Report message is determined by the transmission timing of that Report message, that is, by the slot index / round index / block index. One method for generating the Nonce's FC is: FC = slot index || round index || block index. Here, the symbol "||" represents a concatenation operation. For example, assuming the Slot index value is 0x03, the round index value is 0x10, and the block index value is 0x07, then the concatenated FC is 000000110000000000010000000000000000111 (binary representation). The Slot Index, Round Index, and Block Index fields in Table 5 are all contained within the FC. In other words, the Slot Index, Round Index, and Block Index fields in Table 5, when concatenated, form the FC. Therefore, the Nonce is constructed based on the FC.

[0173] As described above, existing schemes for constructing nonces for messages based on compressed PSDU format during the initialization phase require the compressed PSDU-based messages (such as SOR messages) to explicitly carry the PN field, which incurs additional signaling overhead. Existing schemes for constructing nonces for messages based on compressed PSDU format during the measurement period require SOR messages and other messages to explicitly carry timing information such as slot index / round index / block index, which also incurs additional signaling overhead. Since the design philosophy of compressed PSDU is to minimize inherent signaling overhead, existing technologies contradict this design philosophy to some extent. This application provides a scheme for constructing nonces for messages based on compressed PSDU format without increasing signaling overhead. The following section introduces the applicable scenarios for the UWB communication scheme provided in this application.

[0174] The communication scheme for UWB provided in this application can operate in star topology, point-to-point topology, or mesh topology. The communication scheme for UWB provided in this application can also operate in other topologies, and this application does not impose any limitations on it. Figure 5 This is a schematic diagram illustrating an example of a star topology. Figure 5 As shown, a star topology involves a central control node, for example... Figure 5 The personal area network (PAN) or coordinator shown is described. The communication scheme for UWB provided in this application embodiment is applicable to data communication / sensing / ranging / positioning between the central control node and one or more other devices in a star topology. Figure 6 This is a schematic diagram illustrating an example of a point-to-point topology or a mesh topology. The communication scheme for UWB provided in this application embodiment is also applicable to point-to-point or mesh topologies. Figure 6 ( ), communication / sensing / ranging / positioning between different devices. Figure 5 and Figure 6 In the diagram, black nodes represent full-function devices (FFDs), and white nodes represent reduced-function devices (RFDs). FFDs can act as PAN coordinators or coordinators, while RFDs cannot. FFDs can communicate with each other, and with each other. RFDs cannot communicate directly with each other; they can only communicate with FFDs or forward data through an FFD. In a UWB system, an FFD can be an anchor device or a tag device with strong computing capabilities (e.g., a UWB tag mounted on a smartphone); while an RFD is a tag device with only partial computing capabilities.

[0175] The technical solutions of this application are primarily applicable to UWB systems, such as UWB systems supporting IEEE 802.15.4a, IEEE 802.15.4z, IEEE 802.15.4ab, or next-generation standards of IEEE 802.15.4ab. Those skilled in the art will readily understand that the various aspects of this application can be extended to other networks employing various standards or protocols, such as BLUETOOTH, high-performance radio LAN (HIPERLAN) (a wireless standard similar to IEEE 802.11, primarily used in Europe), and wide area networks (WANs), personal area networks (PANs), or other networks now known or to be developed in the future. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in the embodiments of this application can be applied to any suitable wireless network.

[0176] See Figure 7 , Figure 7 This application provides an example of a UWB system to which the technical solution provided in the embodiments of this application applies. The UWB system includes an anchor (only one anchor is shown) and one or more tags (only tag 1 and tag 2 are shown). The anchor and tags support protocols such as IEEE 802.15.4a, IEEE 802.15.4z, and IEEE 802.15.4ab. Of course, with the continuous evolution and development of communication technologies, the WLAN protocol can also include next-generation protocols such as IEEE 802.15.4ab. The anchor can be an access point, and the tag can be a station (STA). Both the access point and the STA support WLAN protocols, which may include IEEE 802.11be (or Wi-Fi 7, EHT protocol).

[0177] An access point is a device with wireless communication capabilities, supporting communication using the WLAN protocol and enabling communication with other devices (such as stations or other access points) within a WLAN network. It can also communicate with other devices. In a UWB system, there are one or more access point (AP) type stations and one or more non-access point stations (non-AP STAs). For ease of description, this paper refers to access point type stations as access points (APs) and non-access point type stations as stations (STAs).

[0178] An access point can be a complete device, or it can be a chip or processing system installed within a complete device. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of the chip or processing system (i.e., the AP). The AP in the embodiments of this application is a device that provides services to a station (STA), and can support, for example, IEEE 802.15.4a, IEEE 802.15.4z, IEEE 802.15.4ab, or their next generation. For example, an AP can be a communication server, router, switch, bridge, computer, mobile phone, or other communication entity. An access point (AP) can include anchors, macro base stations, micro base stations (also known as small stations), pico base stations, femtocells, relay stations, access points, gNBs, transmission reception points (TRPs), evolved Node Bs (eNBs), radio network controllers (RNCs), home base stations (e.g., home evolved Node Bs, or home Node Bs, HNBs), base band units (BBUs), WiFi access points (APs), integrated access and backhaul (IABs), etc. Of course, the AP can also be the chip and processing system within these various types of devices to implement the methods and functions of the embodiments of this application.

[0179] A station is a device with wireless communication capabilities, supporting communication using the WLAN protocol and having the ability to communicate with other stations or access points in a WLAN network. For example, a STA is any communication device that allows a user to communicate with an AP and thus with the WLAN. This communication device can be a complete device or a chip or processing system installed in a complete device. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of the chip or processing system (i.e., the station). STAs can include tag devices / smart tag devices, mobile phones, mobile stations (MS), tablets, computers with wireless transceiver capabilities (e.g., laptops), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical, smart grid, transportation safety, smart city, and smart home applications, subscriber units, cellular phones, wireless data cards, personal digital assistant (PDA) computers, tablets, laptop computers, and machine-type communication (MTC) terminals. Stations can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. For example, the station can be a handset with wireless communication capabilities, an in-vehicle device, a wearable device, or a terminal in the Internet of Things or the Internet of Vehicles, or any form of terminal in 5G and subsequent communication systems; this application is not limited to this. The station can support the IEEE 802.15 series protocols, such as IEEE 802.15.4a, IEEE 802.15.4z, and IEEE 802.15.4ab.

[0180] It should be noted that, unless otherwise specified, the following description assumes the initiator is the controller. The corresponding description applies to cases where the responder is the controller, or where the controller is a third-party device. Furthermore, unless otherwise specified, the following description assumes a one-to-many scenario, i.e., one initiator corresponding to multiple responders. The corresponding description applies to cases where multiple initiators correspond to multiple responders. Furthermore, unless otherwise specified, the following description assumes the initiator broadcasts a configuration update message for the measurement wheel (e.g., the ranging wheel) to all responders before the start of each measurement wheel via a measurement initiation message (e.g., a SOR message). Accordingly, upon receiving the configuration update message for the measurement wheel, the responder completes the parameter update configuration and starts the current measurement wheel and subsequent measurement wheels with the new parameters (until the next parameter update configuration). The corresponding description applies to situations where the initiator broadcasts measurement initiation messages at other times, such as when the measurement round configuration update message is broadcast via the measurement initiation message during the measurement reporting phase of each measurement round. The method proposed in this application is applicable to all such situations.

[0181] Furthermore, unless otherwise specified, the following description assumes that the measurement wheel configuration update message is carried by a measurement initiation message. The corresponding description also applies to cases where other messages are used to carry the measurement wheel configuration update message. For example, in NBA-MMS UWB ranging, the method proposed in this application applies when the initiator sends a POLL message to the responder to piggyback on the measurement wheel configuration update message. For instance, in one-to-many NBA-MMS UWB ranging, the initiator piggybacks the ranging wheel configuration update message by sending a POLL message to the first responder. Here, the first responder refers to the first responder among multiple responders to initiate ranging with the initiator in chronological order; in this case, the POLL message is sent via broadcast. As another example, in NBA-MMS UWB ranging, the responder piggybacks the measurement wheel configuration update message by sending a Response message to the initiator. For example, in NBA-MMS UWB ranging, the initiator (responder) sends a Report message to the responder (initiator) that carries the configuration update message for the measuring wheel. The method proposed in this application applies to all the above-mentioned examples. Furthermore, for ease of description, it is assumed below that in the initial measurement initiation message, the order of the list elements corresponds to the device index order, i.e., list elements #0, #1, ..., ~#N correspond to device 0, device 1, ..., device N, respectively. The corresponding description applies to other cases as well. For example, if list elements #0, #1, ..., ~#N correspond to device 2, device 4, ..., device N, the method proposed in this application applies. Furthermore, unless otherwise specified, the following description assumes that the ranging process is being performed. The corresponding description applies to other measurement processes, such as sensing and positioning. In other words, the following description uses ranging as an example of the measurement process. Furthermore, unless otherwise specified, the following description assumes that the time between the old and new rounds is not adjacent. The corresponding description applies to rounds that are time-adjacent. The method proposed in this application is applicable to all rounds.

[0182] Furthermore, unless otherwise specified, the following descriptions will use NBA-MMS UWB ranging as an example. The corresponding descriptions also apply to other ranging, sensing, positioning, and other measurement applications. Other ranging methods include, but are not limited to: non-NBA-MMS ranging (ranging that does not include NBA or MMS) and MMS ranging (ranging that does not include NBA but includes MMS).

[0183] Figure 8This application provides an interactive flow for a communication method for UWB. Figure 8 The method shown can be applied to scenarios such as ranging, sensing, positioning, and communication, for example: ranging based on NBA-MMS, sensing based on NBA-MMS, and positioning based on NBA-MMS. Figure 8 As shown, the method includes:

[0184] 801. The sending end generates the first message.

[0185] The transmitter can be a UWB device that supports the UWB standard. The transmitter can be an access point (AP) or a site. The transmitter can be an FFD or an RFD. The transmitter can be an initiator of ranging, sensing, positioning, or communication (i.e., a ranging initiator, sensing initiator, positioning initiator, or communication initiator); it can also be a responder of ranging, sensing, positioning, or communication (i.e., a ranging responder, sensing responder, positioning responder, or communication responder); or it can be a third-party device (which can be called a controller device), i.e., not an initiator or responder of ranging, sensing, positioning, or communication. For a more detailed description of the transmitter below, please refer to step 801.

[0186] The first message includes instruction information, which instructs the construction of an FC (Functional Control Message) based on a first field in the first message. The first field indicates the type of the first message. The FC constructed based on the first field can be used to construct a Nonce for encrypting or authenticating the first message. The first message can be a message based on a compressed PSDU format. For example, the first message is a control message in the NBA-MMS UWB measurement process, such as an ADV-POLL message, ADV-RESP message, ADV-CONF message, SOR message, POLL message, Response message, or Report message (which may be called a report message). In this application, NBA-MMS UWB measurement includes at least one of NBA-MMS UWB ranging, NBA-MMS UWB sensing, and NBA-MMS UWB positioning. The first field can be a Message ID field. For example, the first message is the SOR message shown in Table 2, where the first field is the Message ID field. Another example is the Report message shown in Table 4, where the first field is the Message ID field. The POLL message can also be called an inquiry message; this application does not limit the name of the POLL message. The indication information may occupy one or more bits in the first message. When the value represented by the one or more bits is 1, the indication information is used to indicate the construction of an FC based on the first field in the first message; when the value represented by the one or more bits is 0, the indication information is used to indicate the construction of an FC by other means, such as constructing an FC based on the slot index, round index, and block index corresponding to the first message, or to indicate the construction of an FC based on the PN field in the first message. Alternatively, when the value of the indication information (i.e., the value represented by the one or more bits occupied by the indication information) is 0, the indication information is used to indicate the construction of an FC based on the first field in the first message; when the value of the indication information is 1, the indication information is used to indicate the construction of an FC by other means.

[0187] The indication information can occupy fewer than 4 bits, which is less than the number of bits occupied by the PN field (see Tables 2 and 3). For example, the indication information occupies 1 or 2 bits. Therefore, the scheme in which the first message includes indication information has less signaling overhead compared to the existing scheme that explicitly carries the PN field. The following describes one possible format of the first message, taking a POLL message as an example. Table 6 shows an example of the PSDU format of a POLL message.

[0188] Table 6

[0189]

[0190] In Table 6, the fields Message ID, Security Enable, Address, Secure Payload, and MIC are the same as those in Table 2 above, and will not be repeated here. The Block Index field indicates the ranging block corresponding to the POLL message, and the Round Index field indicates the ranging round corresponding to the POLL message. In this paper, the Block Index is an example of a measurement block identifier, and the Round Index is an example of a measurement round identifier. Table 6 may or may not include the Block Index field (occupying 2 bits). Table 6 may or may not include the Round Index field (occupying 2 bits). The Presence Control field includes the above-mentioned indication information. The Presence Control field may occupy 1 bit, 3 bits, or one byte. This application does not limit the position and size of the Presence Control field, nor does it limit the name of the Presence Control field. In this paper, the size of the field refers to the number of bits occupied by the field. In addition, the Presence Control field can be a new field or it can be included in an existing field. It should be understood that Table 6 is merely an example of the PSDU format for POLL messages, and the position and size of the fields in Table 6 are not limited.

[0191] Tables 7-1, 7-2, and 7-3 show three examples of the Presence Control field.

[0192] Table 7-1

[0193] 1 Presence Control

[0194] Referring to Table 7-1, the Presence Control field occupies one bit. The Presence Control field is used to indicate whether to construct an FC based on the first field in the first message. For example, when the value of the Presence Control field is 1, it indicates that an FC should be constructed based on the first field in the first message; when the value of the Presence Control field is 0, it indicates that an FC should be constructed based on the slot index, round index, and block index corresponding to the first message, or it indicates that an FC should be constructed based on the PN field in the first message.

[0195] Table 7-2

[0196] Bits:0 1 2 Block Index Presence Round Index Presence imSI enabled

[0197] Referring to Table 7-2, the Presence Control field includes the Block Index Presence field (occupying 1 bit), the Round Index Presence field (occupying 1 bit), and the imSI enabled field (occupying 1 bit). It should be noted that the size and position of each field in Table 7-2 are not limited. The Block Index Presence field indicates whether the Block Index field in Table 6 exists. The Round Index Presence field indicates whether the Round Index field in Table 6 exists. It should be noted that the first message shown in Table 6 may not contain a Block Index field, and / or, the first message shown in Table 6 may not contain a Round Index field. When the first message does not contain a Block Index field, the default value of the BlockIndex field corresponding to the first message is 0. When the first message does not contain a Round Index field, the default value of the RoundIndex field corresponding to the first message is 0. The imSI enabled field is used to indicate whether an FC is constructed based on the first field in the first message. For example, when the value of the imSI enabled field is 1, the imSI enabled field is used to indicate the construction of an FC based on the first field in the first message; when the value of the imSI enabled field is 0, the imSI enabled field is used to indicate the construction of an FC based on the slot index, round index, and block index corresponding to the first message, or to indicate the construction of an FC based on the PN field in the first message. The imSI enabled field in Table 7-2 can be regarded as the above indication information.

[0198] Table 7-3

[0199]

[0200]

[0201] The meanings of the Block Index Presence (1 bit), Round Index Presence (1 bit), and imSI enabled (1 bit) fields in Table 7-3 are the same as those in Table 7-2, and will not be repeated here. The RFU (reserved for future use, equivalent to reserved) field is a reserved field, occupying 5 bits, and is reserved for future use. The Presence Control field shown in Table 7-3 occupies one byte. The imSI enabled field in Table 7-3 can be considered as the aforementioned indication information. It should be noted that the size and position of the fields in Table 7-3 are not limited.

[0202] 802. The sending end sends the first message.

[0203] Accordingly, the receiving end receives the first message. The receiving end can be a UWB device that supports the UWB standard. The receiving end can be an AP or a site. The receiving end can be an FFD or an RFD. The receiving end can be an initiator of ranging, sensing, positioning, or communication, i.e., a ranging initiator, sensing initiator, positioning initiator, or communication initiator; it can also be a responder of ranging, sensing, positioning, or communication, i.e., a ranging responder, sensing responder, positioning responder, or communication responder; it can also be a third-party device (which can be called a controller device), i.e., not an initiator or responder of ranging, sensing, positioning, or communication. For example, the sending end is both the initiator and the controller, and the receiving end is the responder. Another example is that the sending end is the controller, and the receiving end is the responder. The relevant description of the receiving end in the following text can be found in step 802.

[0204] In one possible implementation, the sending end further performs the following operation: sending a second message, which includes a second field indicating a deadline for receiving SOR messages. Correspondingly, the receiving end receives the second message. The receiving end can stop listening for SOR messages after the deadline indicated by the second field, thereby avoiding increased energy consumption caused by prolonged waiting for SOR messages. The second message also includes a field indicating the presence of the second field. The second message is a message sent by the sending end before sending the SOR message (e.g., the first message). The second message can be an ADV-CONF message or other messages; this application does not limit this. Here, the ADV-CONF message is used as an example to describe the second message. Table 8 shows an example of the PSDU format of an ADV-CONF message containing a second field.

[0205] Table 8

[0206]

[0207] In Table 8, the SOR transmission timeout field (i.e., the second field) indicates the deadline of the SOR message, and the SOR transmission timeout Presence field indicates whether the second message contains the SOR transmission timeout field, i.e., whether the second message contains the SOR transmission timeout field. The unit of the SOR transmission timeout field can be a ranging scheduling time unit (RSTU) or a slot; this application does not impose any limitation on the unit of the SOR transmission timeout. For example, when the value of the SOR transmission timeout Presence field is 1, the second message contains the SOR transmission timeout field, i.e., the second message contains the SOR transmission timeout field; when the value of the SOR transmission timeout Presence field is 0, the second message does not contain the SOR transmission timeout field, i.e., the second message does not contain the SOR transmission timeout field. The SORMessage Management field is used to carry and manage the SOR message list. The SOR MessageManagement (SMM) Presence field (hereinafter referred to as the SMM Presence field) indicates whether the second message contains the SOR Message Management field. For example, when the SMM Presence field value is 1, the second message includes the SOR Message Management field; when the SMM Presence field value is 0, the second message does not include the SOR Message Management field. The RFU field is a reserved field, i.e., a field reserved for future use, and can occupy 6 bits. It is understood that Table 8 is only an example of a PSDU in the second message, and the size and position of each field in the second message are not limited.

[0208] 803. The receiving end constructs an FC based on the instruction information in the first message and the first field in the first message.

[0209] One possible implementation of step 803 is as follows: Based on the indication information in the first message, an FC is constructed using the first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message. For example, the receiving end concatenates the first field, the measurement wheel identifier (e.g., round index) corresponding to the first message, and the measurement block identifier (e.g., block index) corresponding to the first message to obtain the FC. In this example, the FC is constructed as: FC = message ID || round index || block index. "||" indicates a concatenation operation. After constructing the FC, the receiving end can construct the Nonce corresponding to the first message based on the FC. The Nonce corresponding to the first message is used for encryption or authentication of the first message. The Nonce corresponding to the first message may include the source address and the FC. Table 9-1 shows an example of a Nonce.

[0210] Table 9-1

[0211]

[0212] In Table 9-1, the Message ID field, Round Index field, and Block Index field constitute the FC (Frame Controller). It should be noted that this application does not impose any restrictions on the construction method of the FC; the FC construction methods given throughout are merely examples.

[0213] In another example, the FC constructor can also be: FC = block index || round index || message ID. In other words, this application does not impose any restrictions on the concatenation order used in the FC constructor.

[0214] In another example, the FC construction method can also be: FC = prePN || block index || round index || message ID. Alternatively, it can be FC = prePN || message ID. Here, prePN (pre-determined Packet Number) represents a value pre-agreed upon and stored by the sender and receiver that can be used to construct the FC. prePN can be updated according to a specific rule, such as incrementing the prePN value by 1 after a certain number of block times. This application does not impose any restrictions on the update rule of prePN. Furthermore, this application does not impose any restrictions on other values ​​that can participate in FC construction; the aforementioned prePN is merely an example. Any situation where FC construction is based on the message ID is within the scope of protection of this application.

[0215] Another possible implementation of step 803 is as follows: Based on the indication information in the first message, and based on the first field, the sorting information of the list element corresponding to the first message in the message list, and the measurement block identifier corresponding to the first message, an FC is constructed. In this application, when the first message is not a SOR message, the sorting information of the list element corresponding to the first message in the message list can be: the sorting information of the list element corresponding to the SOR message corresponding to the first message in the message list. The first message and its corresponding SOR message correspond to the same device. The indication information is used to indicate the construction of an FC based on the first field and the sorting information of the list element corresponding to the first message in the message list, see Table 11-4 below. The relevant content of the sorting information of the list element corresponding to the first message in the message list will be described in detail later, and will not be described here. Different list elements in the message list correspond to different devices. Each list element in the message list includes a device identifier, such as a device address. A device address refers to the address of a device. The message list may be included in a third message sent before sending the first message. For example, the third message is the ADV-CONF message in the NBA-MMS UWB measurement process. The third message can also be other messages, and this application does not impose any limitations on this. An example of a possible implementation is as follows: The receiving end concatenates the first field, the aforementioned sorting information (e.g., CODA values ​​below), and the measurement block identifier (e.g., blockindex) corresponding to the first message to obtain the FC. In this example, the FC is constructed as: FC = message ID || CODA values ​​|| blockindex. "||" indicates a concatenation operation. CODA values ​​can be a numerical value representing the sorting of the list element corresponding to the first message in the message list, such as #1, #2, #3, etc. After constructing the FC, the receiving end can construct the Nonce corresponding to the first message based on this FC. The Nonce corresponding to the first message is used for encryption or authentication of the first message. Table 9-2 shows an example of a Nonce.

[0216] Table 9-2

[0217]

[0218] In Table 9-2, the Message ID field, the CODAvalues ​​field, and the Block Index field constitute the FC.

[0219] In another example, the FC constructor can also be: FC = block index || CODAvalues ​​|| message ID. In other words, this application does not impose any restrictions on the concatenation order used in the FC constructor.

[0220] In another example, the FC construction method can also be: FC = prePN || block index || CODA values ​​|| message ID. Alternatively, it can be FC = prePN || CODA values. Here, prePN represents a value pre-agreed upon and stored by the sender and receiver that can be used to construct the FC. prePN can be updated according to a specific rule, for example, incrementing the prePN value by 1 after a certain number of block times. This invention does not impose any limitations on the update rule of prePN. Furthermore, this application does not impose any limitations on other values ​​that can participate in FC construction; the aforementioned prePN is merely an example. Any situation where FC construction is based on CODA values ​​is within the scope of protection of this application.

[0221] It should be noted that this application does not impose any restrictions on the format of the Nonce; Table 9-2 is merely an example.

[0222] Figure 8 The method flow can be understood as follows: Based on the first field (message ID) of the control message (i.e., the first message), the measurement wheel identifier corresponding to the control message, and the measurement block identifier corresponding to the control message, construct the FC corresponding to the control message. Figure 8 The methodology is applicable to scenarios such as NBA-MMS-based ranging, NBA-MMS-based sensing, and NBA-MMS-based positioning. In these scenarios, different control messages within the same measurement wheel (e.g., the ranging wheel) have different message IDs; that is, any two control messages have different message IDs. Therefore, by… Figure 8 The method flow in the document can construct different control functions (FCs) for different control messages. Figure 9 This is a schematic diagram of an NBA-MMS UWB ranging process provided for an embodiment of this application. Figure 9 As shown, the message ID of the POLL message is 0x00, the message ID of the Response message is 0x01, the message ID of the Report message sent by the Responder is 0x02, and the message ID of the Report message sent by the Initiator is 0x03. Figure 9 It can be seen that different control messages have different message IDs within a single ranging wheel. When Figure 8When the methodology is applied to the NBA-MMS UWB ranging scenario, Figure 8 The method can be understood as follows: construct the required FC by the inherent sending order of each control message in the NBA-MMS UWB ranging process, where the message ID of each control message can be regarded as the inherent sending order of each control message.

[0223] In this embodiment, the indication information is used to indicate the construction of an FC based on the first field in the first message. When the indication information is included in the first message, the signaling overhead is less because the indication information occupies fewer bits than the PN field.

[0224] Figure 10 This application provides another communication method interaction flow for UWB. Figure 10 The method shown can be applied to scenarios such as ranging, sensing, positioning, and communication, for example: ranging based on NBA-MMS, sensing based on NBA-MMS, and positioning based on NBA-MMS. Figure 10 The methods and processes in Figure 8 Compared to the previous method flow, the first message does not need to carry indication information; the receiving end constructs the FC (Functional Opening) based on the first field in the first message by default. For example... Figure 10 As shown, the method includes:

[0225] 1001. The sending end generates the first message.

[0226] Step 1001 can be found in step 801. Figure 10 The first message in the method flow and Figure 8 Compared to the first message in the method flow, this one does not include the aforementioned instruction information. The first message can be a message based on a compressed PSDU format. For example, the first message is a control message in the NBA-MMS UWB measurement process, such as an ADV-POLL message, ADV-RESP message, ADV-CONF message, SOR message, POLL message, Response message, or Report message (which may be called a report message). In this application, NBA-MMS UWB measurement includes at least one of NBA-MMS UWB ranging, NBA-MMS UWB sensing, and NBA-MMS UWB positioning. The first message includes a first field. The first field can be a Message ID field. For example, the first message is the SOR message shown in Table 2, where the first field is a Message ID field. Another example is the Report message shown in Table 4, where the first field is a Message ID field.

[0227] 1002. The sending end sends the first message.

[0228] Accordingly, the receiving end receives the first message. Step 1002 can be referred to step 802.

[0229] 1003. The receiving end constructs an FC based on the first field in the first message.

[0230] One possible implementation of step 1003 is as follows: Construct an FC based on the first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message. For example, the receiving end concatenates the first field, the measurement wheel identifier (e.g., round index) corresponding to the first message, and the measurement block identifier (e.g., block index) corresponding to the first message to obtain the FC. After constructing the FC, the receiving end can construct the Nonce corresponding to the first message based on the FC, as shown in Table 9. It can be understood that the FC constructed based on the first field in the first message can be used to construct a Nonce for encrypting or authenticating the first message.

[0231] Another possible implementation of step 1003 is as follows: Construct an FC based on the first field, the sorting information of the list element corresponding to the first message in the message list, and the measurement block identifier corresponding to the first message. The sorting information of the list element corresponding to the first message in the message list will be described in detail later; it will not be described here. For example, the receiving end concatenates the first field, the aforementioned sorting information (e.g., CODA values ​​below), and the measurement block identifier corresponding to the first message (e.g., block index) to obtain the FC. In this example, the FC is constructed as: FC = message ID || CODA values ​​|| block index.

[0232] Figure 10 The main principles of the method and process Figure 8 The main principles of the method flow are similar, so they will not be repeated here.

[0233] In this embodiment of the application, the FC is constructed based on the first field in the first message. The first message does not need to carry the PN field, resulting in less signaling overhead.

[0234] Figure 11 This application provides another communication method interaction flow for UWB. Figure 11 The method shown can be applied to scenarios such as ranging, sensing, positioning, and communication, for example: ranging based on NBA-MMS, sensing based on NBA-MMS, and positioning based on NBA-MMS. Figure 11 Methods and procedures Figure 8 Compared to the previous method flow, the first message does not contain instruction information, while the fourth message sent before the first message contains the aforementioned instruction information. For example... Figure 11As shown, the method includes:

[0235] 1101. The sending end sends the fourth message.

[0236] Correspondingly, the receiving end receives a fourth message. The fourth message includes indication information, which instructs the construction of an FC based on a first field in the first message. The first field indicates the type of the first message. The indication information may occupy one or more bits. For example, when one or more bits in the indication information represent a value of 1, the indication information instructs the construction of an FC based on the first field in the first message; when the one or more bits represent a value of 0, the indication information instructs the construction of an FC in another manner, such as based on the PN field in the first message. The fourth message may contain a Presence Control field as shown in any of Tables 7-1, 7-2, or 7-3, which contains the aforementioned indication information; details are omitted here.

[0237] The first message can be any message sent by the sending end or the receiving end after the sending end sends the fourth message. In one possible implementation, after the sending end sends the fourth message, any control message sent by the sending end and the receiving end constructs an FC based on the first field in that control message. For example, the fourth message can be any of the following: ADV-POLL message, ADV-RESP message, ADV-CONF message, or SOR message; and the first message can be any of the following: POLL message, Response message, or Report message. Another example is that the fourth message is an ADV-POLL message, and the first message can be any of the following: ADV-RESP message, ADV-CONF message, or SOR message. The fourth message can be any message sent by the sending end or the receiving end before the sending end sends the first message; this application does not limit this. The indication information can be understood as indicating that the FC corresponding to each control message (e.g., the first message) sent by the sending end or the receiving end after the sending end sends the fourth message is constructed based on the first field in that control message. In other words, the fourth message can indicate the construction method of the FC (Functional Control) corresponding to each control message sent by the sender or receiver after the fourth message. It is understood that each message sent by the sender or receiver after the fourth message does not need to carry indication information. The number of bits occupied by the indication information can be less than that occupied by the slot index field (e.g., the field indicating the slot index in an SOR message). The fourth message carrying indication information occupies fewer bits than the fourth message carrying a slot index field, resulting in less signaling overhead. Furthermore, since the indication information is included in the fourth message, each message sent by the sender after the fourth message does not need to carry the indication information, further saving signaling overhead.

[0238] 1102. The sending end sends the first message.

[0239] Accordingly, the receiving end receives the first message. The first message includes a first field, such as the message ID field.

[0240] 1103. The receiving end constructs an FC based on the instruction information in the fourth message.

[0241] The FC constructed in step 1103 can be used to construct a Nonce for encrypting or authenticating the first message. One possible implementation of step 1103 is as follows: The receiving end constructs the FC based on the indication information in the fourth message, the aforementioned first field, the measurement wheel identifier corresponding to the first message, and the measurement block identifier corresponding to the first message. For example, the receiving end constructs the FC by concatenating the first field, the measurement wheel identifier (e.g., round index) corresponding to the first message, and the measurement block identifier (e.g., block index) corresponding to the first message, based on the indication information. After constructing the FC, the receiving end can construct the Nonce corresponding to the first message based on this FC.

[0242] Figure 11 The main principles of the method and process Figure 8 The main principles of the method flow are similar, so they will not be repeated here.

[0243] In this embodiment, the indication information in the fourth message is used to indicate the construction of an FC based on the first field in the first message. Compared to the fourth message or other messages carrying a slot index field, this method uses fewer bits and has less signaling overhead. Furthermore, each message sent by the sender after the fourth message does not need to carry the indication information, further saving signaling overhead.

[0244] Figure 12 This application provides another communication method interaction flow for UWB. Figure 12 The method shown can be applied to scenarios such as ranging, sensing, positioning, and communication, for example: ranging based on NBA-MMS, sensing based on NBA-MMS, and positioning based on NBA-MMS. Figure 12 The methods and processes in Figure 8 Compared to the previous method flow, the indication information in the first message is used to indicate the sorting information of the list element corresponding to the first message in the message list within the message list, and to construct the FC (Open Function). For example... Figure 12 As shown, the method includes:

[0245] 1201. The sending end sends a third message.

[0246] Correspondingly, the receiving end receives the third message. The sending end can send the third message by broadcasting it. The third message can be an ADV-CONF message or other messages containing a list of SOR messages.

[0247] 1202. The sending end generates the first message.

[0248] The first message includes indication information used to construct an FC (Focus Function) based on the ordering information of the list element corresponding to the first message in the message list. The list element corresponding to the first message in the message list contains the device identifier (e.g., device address) of the receiving end of the first message. The receiving end of the message can be understood as the end that receives the message. For example, if the first message is a unicast message, the sender sends the first message to a receiving end, and that receiving end is the recipient of the first message. The receiving end can use the list element in the message list containing its device identifier as the list element corresponding to its message to be received and / or sent (e.g., the first message) in the message list. Different list elements in the above message list correspond to different devices. Or, different list elements in the above message list correspond to different device identifiers. Each list element in the above message list may include a device identifier. The above message list may be included in a third message sent before sending the above first message. For example, the third message is an ADV-CONF message in the NBA-MMS UWB measurement process. The above first message may be a message based on a compressed PSDU format. For example, the first message is any one of the following: SOR message, POLL message, Response message, or Report message.

[0249] The sorting information of the list elements corresponding to the first message in the message list can be: the sorting information of the list elements in the message list containing the device identifier (e.g., device address) of the receiving end of the first message in the message list. The receiving end can use the list elements in the message list containing its device identifier as the list elements corresponding to its message to be received and / or sent (e.g., the first message) in the message list. This application does not impose any limitations on the form of the device identifier; the device address is merely an example.

[0250] The following example, with reference to the accompanying diagram, illustrates the sorting information of the list elements corresponding to the first message in the message list. A one-to-many NBA-MMS UWB ranging process consists of multiple one-to-one NBA-MMS UWB ranging processes executed in chronological order; that is, the initiator of each one-to-one NBA-MMS UWB ranging process is the same. A typical one-to-many NBA-MMS UWB ranging process is as described above. Figure 4AAs shown. The initialization process for pre-configuring one-to-many NBA-MMS UWB ranging is as follows: Figure 13 As shown. Figure 13 This diagram illustrates the initialization process for pre-configuring one-to-many NBA-MMS UWB ranging. (Example:) Figure 13 As shown, for one-to-many NBA-MMS UWB ranging, the Initiator first needs to broadcast an ADV-POLL message to inform all responders that NBA-MMSUWB ranging needs to be performed. Each responder sends its ADV-RESP message to the Initiator using a contention-based access method. After successfully receiving all successfully contention-based ADV-RESP messages, the Initiator broadcasts an ADV-CONF message to all responders. Figure 13 In this context, SOR 0 represents the SOR message sent by the Initiator to responder 0, SOR 1 represents the SOR message sent by the Initiator to responder 1, and SOR 2 represents the SOR message sent by the Initiator to responder 2. Time offset to SOR 0 indicates the time SOR 0 was sent, Time offset to SOR 1 indicates the time SOR 1 was sent, and Time offset to SOR 2 indicates the time SOR 2 was sent. For the responder's MMS UWB measurement process, please refer to [link to relevant documentation]. Figure 9 The distance measurement process shown is as follows: Time offset to POLL 0 indicates the time when the POLL 0 message is sent during the MMS UWB measurement process of responder 0; Time offset to POLL 1 indicates the time when the POLL 1 message is sent during the MMS UWB measurement process of responder 1; and Time offset to POLL 2 indicates the time when the POLL 2 message is sent during the MMS UWB measurement process of responder 2.

[0251] The ADV-CONF message carries a SOR message list containing multiple SOR messages. The SOR message list is an example of the message list described above. Each element in the SOR message list contains a device address and the corresponding SOR message's sending time (time offset to SOR#X). In other words, each responder can determine whether its ADV-RESP message has been successfully received by the initiator by checking if its own device address is included in this SOR message list, thus determining whether it will participate in the subsequent NBA-MMS UWB ranging process. Only devices whose ADV-RESP messages are successfully received by the initiator will initiate the subsequent NBA-MMS UWB ranging process. The chronological order of the responder device address appearance (CODA) in the ADV-CONF message's message list serves as the sorting information for the corresponding list elements of the control messages (e.g., the first message) to be sent and / or received by the receiver in the message list. For example, after receiving an ADV-CONF message, the receiving end checks whether its own device address is included in the SOR message list in the ADV-CONF message. If the receiving end's device address is included in the SOR message list, the order of the device address in the SOR message list is used as the order information of the list element corresponding to the control message (e.g., the first message) to be sent and / or received by the receiving end in the message list.

[0252] An example of a PSDU format for an ADV-CONF message containing a list of SOR messages is shown in Tables 10 to 14 below. The position and size of each field in Tables 10 to 14 are not limited.

[0253] Table 10

[0254]

[0255] Table 10 is a schematic diagram of the PSDU format of the ADV-CONF message. The meanings of the fields in Table 10 are similar to those in Tables 1-2, and will not be repeated here. The Content field contains the SOR message list, as shown in Table 11. Table 11 is a schematic diagram of the SOR message list format.

[0256] Table 11

[0257]

[0258] The SOR Message Management (SMM) Presence field controls the presence of the SOR Message Management field. For example, a value of 0 indicates that the SOR message list does not contain the SOR Message Management field; a value of 1 indicates that the SOR message list contains the SOR Message Management field. The RFU field is a reserved field. The SOR Message Management field is used to carry and manage the SOR message list. One possible format for the SOR Message Management field is shown in Table 12:

[0259] Table 12

[0260] Bits:0 1-7 Octets:Variable Address Type SOR Messages List Length SOR Messages List

[0261] The Address Type field indicates the type of device address contained in each list element of the SOR Messages List. For example, when the Address Type field value is 0, it indicates that the device uses a short address (2 bytes); when the Address Type field value is 1, it indicates that the device uses an extended address / long address (8 bytes). The SOR Messages List Length field indicates the length of the SOR Messages List. The SOR Messages List field is the SOR message list field. The SOR Messages List field includes multiple SOR message dispatch list elements (which can be simply referred to as list elements). The SOR message list fields are shown in Table 13 below.

[0262] Table 13

[0263]

[0264] In Table 13, each list element corresponds to a different device. For example, SOR messagesscheduling list element #0 in Table 13 corresponds to device #0. As shown in the example in Table 13, devices #0 to #2 appear in the SOR message list in the order of 0, 1, and 2, respectively, meaning their CODA values ​​are 0, 1, and 2. Table 14 shows a schematic diagram of an example format for SOR message list elements.

[0265] Table 14

[0266] Octets: TBD (to be determined) Octets:2 Time offset to SOR Device address

[0267] As shown in Table 14, each SOR message list element includes a Time offset to SOR field and a Device address field. The Device address field contains the device address of a device, and the Time offset to SOR field indicates the transmission time of the SOR message that the device is expected to receive. For example, after receiving an ADV-CONF message, the receiving end checks whether its own device address is included in the SOR message list of the ADV-CONF message. If the receiving end's device address is included in the SOR message list, the Time offset to SOR field in the list element containing the device address indicates the transmission time of the SOR message that the receiving end is expected to receive.

[0268] It should be noted that this application does not impose any limitations on the message carrying the aforementioned list of SOR messages containing multiple SOR messages; other messages may also be included, and the aforementioned ADV-CONF message is merely an example.

[0269] The first message mentioned above can be a message based on compressed PSDU format. For example, the first message is an SOR message. The indication information in the first message may occupy one or more bits. For example, when the value of one or more bits representing the indication information is 1, the indication information is used to indicate the sorting information of the list element corresponding to the first message in the message list within the message list, constructing an FC (Final Message). When the value of the one or more bits representing the indication information is 0, the indication information is used to indicate the construction of an FC in other ways, such as based on the slot index, round index, and block index carried by the first message. When the first message does not carry any of the slot index, round index, and block index, the default index is 0. Alternatively, when the value of the indication information (i.e., the value represented by one or more bits representing the indication information) is 0, the indication information is used to indicate the construction of an FC based on the sorting information of the list element corresponding to the first message in the message list within the message list; when the value of the indication information is 1, the indication information is used to indicate the construction of an FC in other ways. The following uses an SOR message as an example to illustrate one possible format of the first message. Table 15 shows an example of the PSDU format of a SOR message.

[0270] Table 15

[0271]

[0272]

[0273] In Table 15, the fields Message ID, Security Enable, Address, Secure Payload, and MIC are the same as those in Table 3 above, and will not be repeated here. Table 15 may or may not include a Block Index field (occupying 2 bits). Table 15 may or may not include a Round Index field (occupying 2 bits). The Presence Control field includes the aforementioned indication information. The Presence Control field may occupy 1 bit, 3 bits, or one byte. This application does not limit the position or size of the Presence Control field, nor does it limit the name of the Presence Control field. In addition, the Presence Control field can be a new field or it can be included in an existing field. It should be understood that Table 15 is only an example of the PSDU format of the SOR message, and the position and size of each field in Table 15 are not limited. Tables 16-1, 16-2, 16-3, and 16-4 show four examples of the Presence Control field.

[0274] Table 16-1

[0275] 1 Presence Control

[0276] Referring to Table 16-1, the Presence Control field occupies one bit. The Presence Control field is used to indicate whether to construct an FC (Focus Control) based on the ordering information of the list element corresponding to the first message in the message list. For example, when the value of the Presence Control field is 1, the Presence Control field is used to indicate that the FC is constructed based on the ordering information of the list element corresponding to the first message in the message list; when the value of the Presence Control field is 0, the Presence Control field is used to indicate that the FC is constructed based on the slot index, round index, and block index carried by the first message.

[0277] Table 16-2

[0278] Bits:0 1 2 Block Index Presence Round Index Presence imRI enabled

[0279] Referring to Table 16-2, the Presence Control field includes the Block Index Presence field (occupying 1 bit), the Round Index Presence field (occupying 1 bit), and the imRI enabled field (occupying 1 bit). It should be noted that the size and position of each field in Table 16-2 are not limited. The Block Index Presence field indicates whether the Block Index field in Table 15 exists. The Round Index Presence field indicates whether the Round Index field in Table 15 exists. The first message shown in Table 15 may not contain a Block Index field, and / or, the first message shown in Table 15 may not contain a Round Index field. When the first message does not contain a Block Index field, the default value of the BlockIndex field corresponding to the first message is 0. When the first message does not contain a Round Index field, the default value of the RoundIndex field corresponding to the first message is 0. The imRI enabled field is used to indicate whether an FC is constructed based on the sorting information of the list element corresponding to the first message in the message list. For example, when the value of the imRI enabled field is 1, the imRI enabled field is used to indicate the construction of an FC based on the first field in the first message; when the value of the imRI enabled field is 0, the imRI enabled field is used to indicate the construction of an FC based on the slot index, round index, and block index corresponding to the first message. The imRI enabled field in Table 16-2 can be regarded as the above indication information.

[0280] Table 16-3

[0281] Bits:0 1 2 3-7 Block Index Presence Round Index Presence imRI enabled RFU

[0282] The meanings of the Block Index Presence (1 bit), Round Index Presence (1 bit), and imRI enabled (1 bit) fields in Table 16-3 are the same as those in Table 16-2, and will not be repeated here. The RFU field is a reserved field, i.e., a field reserved for future use, occupying 5 bits. The PresenceControl field shown in Table 16-3 occupies one byte. The imRI enabled field in Table 16-3 can be regarded as the above-mentioned indication information. It should be noted that the size and position of each field in Table 16-3 are not limited.

[0283] Table 16-4

[0284]

[0285]

[0286] The meanings of the Block Index Presence (1 bit), Round Index Presence (1 bit), and imRI enabled (1 bit) fields in Table 16-4 are the same as those in Table 16-2, and will not be repeated here. imSI enabled (1 bit) indicates whether an FC (Functional Control Unit) is constructed based on the first field in the first message. For example, when the value of the imSI enabled field is 1, it indicates that an FC is constructed based on the first field in the first message; when the value of the imSI enabled field is 0, it indicates that an FC is constructed based on the slot index, round index, and block index corresponding to the first message, or it indicates that an FC is constructed based on the PN field in the first message. The imRI enabled and imSI enabled fields in Table 16-4 can be considered as the above-mentioned indication information. In other words, the above-mentioned indication information includes the imRI enabled and imSI enabled fields in Table 16-4. For example, when the `imRIenabled` field is used to indicate the construction of an FC (Final Function) based on the sorting information of the list element corresponding to the first message in the message list, and when `imSI enabled` is used to indicate the construction of an FC based on the first field in the first message, the indication information is used to indicate the construction of an FC based on the first field in the first message and the sorting information of the list element corresponding to the first message in the message list. It should be noted that the size and position of the fields in Table 16-4 are not limited.

[0287] 1203. The sending end sends the first message.

[0288] Correspondingly, the receiving end receives the first message.

[0289] In one possible implementation, the sending end further performs the following operation: sending a second message, which includes a second field indicating a deadline for receiving SOR messages. Correspondingly, the receiving end receives the second message. The receiving end can stop listening for SOR messages after the deadline indicated by the second field, thereby avoiding increased energy consumption caused by prolonged waiting for SOR message listening. The second message also includes a field indicating the presence of the second field. The second message is a message sent by the sending end before sending the SOR message (e.g., the first message). The second message can be an ADV-CONF message or other messages; this application does not limit the specific message type.

[0290] 1204. The receiving end obtains the sorting information of the list element corresponding to the first message in the message list of the third message.

[0291] In one possible implementation, after receiving a third message, the receiving end checks whether its own device address is included in the message list of the third message. If the receiving end's device address is included in the message list, the sorting information of the device address in the message list (e.g., CODA values) is used as the sorting information of the list element corresponding to the message to be sent and / or received (including the first message) in the message list. The sorting information of the device address in the message list can be the sorting of list elements containing the device address in the message list. The messages to be sent and / or received by the receiving end may include: SOR messages, POLL messages, Response messages, or Report messages. The receiving end may store the sorting information of its device address in the message list so as to use this sorting information as the sorting information of the list element corresponding to the message to be sent and / or received (including the first message) in the message list. After receiving the first message, the receiving end can retrieve its stored sorting information and use it as the sorting information of the list element corresponding to the first message in the message list. The receiver obtaining the sorting information of the list element corresponding to the first message in the message list can be understood as the receiver obtaining its currently stored sorting information. After storing the sorting information of its device address in the message list, if the receiver receives a new third message (a new ADV-CONF message), it can update its stored order information.

[0292] 1205. The receiving end constructs an FC based on the instruction information in the first message and the sorting information of the list element corresponding to the first message in the message list in the message list.

[0293] One possible implementation of step 1205 is as follows: Based on the indication information in the first message, construct the FC (Focus Controller) according to the measurement slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message. For example, the receiving end concatenates the measurement slot identifier (e.g., slot index), the sorting information, and the measurement block identifier (e.g., block index) corresponding to the first message to obtain the FC. In this example, the FC is constructed as: FC = slot index || CODA values ​​|| block index. "||" indicates a concatenation operation. CODA values ​​(i.e., sorting information) can be a value representing the sorting of the list element corresponding to the first message in the message list, such as #1, #2, #3, etc. After constructing the FC, the receiving end can construct a Nonce based on the FC. This Nonce is used for encryption or authentication of the first message. Tables 17 and 18 show examples of two types of Nonces.

[0294] Table 17

[0295]

[0296] The CODAvalues ​​field in Table 17 contains the sorting information mentioned above. For the meaning of the other fields in Table 17, please refer to the meaning of the fields in Table 5. The Slot Index field, CODAvalues ​​field, and Block Index field together form the FC.

[0297] Table 18

[0298] Octets:8 4 1 Source Address CODA values Nonce Security Level

[0299] The CODAvalues ​​field in Table 18 contains the sorting information mentioned above. For the meanings of the other fields in Table 18, please refer to the field meanings in Table 3.

[0300] Figure 12 The method flow can be understood as follows: Based on the measurement slot identifier corresponding to the control message (i.e., the first message), the sorting information of the list element corresponding to the control message in the message list, and the measurement block identifier corresponding to the control message, the FC corresponding to the control message is constructed. In the one-to-many NBA-MMS UWB ranging process, the sorting information of the list element corresponding to the control message in the message list of each sub-process (i.e., the one-to-one NBA-MMS UWB ranging process) reflects the execution order of each sub-process in the one-to-many NBA-MMS UWB ranging process. See also... Figure 13The one-to-one MMS UWB ranging process involving responder 0 precedes the one-to-one MMS UWB ranging process involving responder 1. The one-to-one MMS UWB ranging process involving responder 1 precedes the one-to-one MMS UWB ranging process involving responder 2. In the one-to-one MMS UWB ranging process involving responder 0, the list element corresponding to the control message (e.g., POLL message, Response message, Report message) is sorted as #0 in the message list. In the one-to-one MMS UWB ranging process involving responder 1, the list element corresponding to the control message is sorted as #1 in the message list. In the one-to-one MMS UWB ranging process involving responder 2, the list element corresponding to the control message is sorted as #2 in the message list. Therefore, Figure 12 The method flow can also be understood as: constructing FC by utilizing the execution order of each subprocess in the one-to-many NBA-MMS UWB ranging process.

[0301] In this embodiment of the application, an FC is constructed based on the sorting information of the list element corresponding to the first message in the message list, which avoids explicitly carrying the Round Index and can save signaling overhead.

[0302] Figure 14 This application provides another communication method interaction flow for UWB. Figure 14 The method shown can be applied to scenarios such as ranging, sensing, positioning, and communication, for example: ranging based on NBA-MMS, sensing based on NBA-MMS, and positioning based on NBA-MMS. Figure 14 Methods and procedures Figure 12 Compared to the previous method, the first message does not contain indication information. The receiving end defaults to the sorting information of the list element corresponding to the first message in the message list, and constructs an FC (Open Function). Figure 14 As shown, the method includes:

[0303] 1401. The sending end sends a third message.

[0304] Correspondingly, the receiving end receives the third message.

[0305] 1402. The sending end sends the first message.

[0306] Accordingly, the receiving end receives the first message. The first message can be any one of the following: SOR message, POLL message, Response message, or Report message.

[0307] 1403. The receiving end obtains the sorting information of the list element corresponding to the first message in the message list.

[0308] Step 1403 can be found in step 1204.

[0309] 1404. The receiving end constructs an FC based on the sorting information of the list element corresponding to the first message in the message list.

[0310] One possible implementation of step 1404 is as follows: Construct an FC (Focus Function) based on the measurement slot identifier corresponding to the first message, the aforementioned sorting information, and the measurement block identifier corresponding to the first message. For example, the receiving end concatenates the measurement slot identifier (e.g., slot index) corresponding to the first message, the aforementioned sorting information, and the measurement block identifier (e.g., block index) corresponding to the first message to obtain the FC. After receiving the third message, the receiving end ensures that the sorting information of the list elements corresponding to the sent or received messages (belonging to the same one-to-one NBA-MMS UWB ranging process) in the message list is the same. Since the measurement slot identifiers corresponding to the messages belonging to the same one-to-one NBA-MMS UWB ranging process are different, the FCs corresponding to the messages are different.

[0311] In this embodiment, an FC (Functional Opening) is constructed based on the sorting information of the list element corresponding to the first message in the message list, thus avoiding explicitly carrying the Round Index and saving signaling overhead. Furthermore, since the first message does not contain indication information, Figure 14 The scheme and Figure 12 Compared to the previous solution, it has less signaling overhead.

[0312] Figure 15 This application provides another communication method interaction flow for UWB. Figure 15 Methods and procedures Figure 12 Compared to the previous method flow, the first message does not contain indication information for constructing an FC based on the sorting information of the list element corresponding to the first message in the message list within that message list. The fourth message, sent before the first message, contains this indication information. For example... Figure 15 As shown, the method includes:

[0313] 1501. The sending end sends the fourth message.

[0314] Correspondingly, the receiving end receives a fourth message. The fourth message includes indication information, which instructs the construction of an FC (Focus Control Message) based on the ordering information of the list element corresponding to the first message in the message list within that message list. The fourth message can be an ADV-POLL message, an ADV-RESP message, higher-layer signaling, or other message, without limitation. The first message can be any one of an SOR message, a POLL message, a Response message, or a Report message. Alternatively, the indication information instructs the receiving end to construct an FC based on the ordering information of the list elements corresponding to the received and / or sent control messages in the message list within the message list after the sending end sends the third message. The constructed FC is used for encryption or authentication of each control message. The third message can be an ADV-CONF message. After the sending end sends the third message, the receiving end receives and / or sends control messages including SOR messages, POLL messages, Response messages, and Report messages.

[0315] 1502. The sending end sends a third message.

[0316] Correspondingly, the receiving end receives the third message. Step 1502 can be referred to step 1201.

[0317] 1503. The receiving end determines the sorting information of its device address in the message list in the third message based on the indication information in the fourth message.

[0318] The receiving end can store the sorting information of its device address in the message list in the third message.

[0319] 1504. The sending end sends the first message.

[0320] Correspondingly, the receiving end receives the first message.

[0321] 1505. The receiving end obtains the sorting information of the list element corresponding to the first message in the message list of the third message.

[0322] One possible implementation of step 1505 is as follows: The receiving end obtains the sorting information of its stored device address in the message list of the third message, and uses this sorting information as the sorting information of the list element corresponding to the first message in the message list of the third message. In other words, the sorting information stored by the receiving end is the sorting information of the list element corresponding to the first message in the message list of the third message.

[0323] 1506. The receiving end constructs an FC based on the instruction information in the fourth message and the sorting information of the list element corresponding to the first message in the message list in the message list.

[0324] One possible implementation of step 1506 is as follows: Based on the indication information in the fourth message, and based on the measurement slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message, construct an FC.

[0325] In this embodiment of the application, an FC is constructed based on the sorting information of the list element corresponding to the first message in the message list, which avoids explicitly carrying the Round Index and can save signaling overhead.

[0326] The structure of a communication device for implementing the UWB communication method provided in the embodiments of this application is described below with reference to the accompanying drawings.

[0327] Figure 16 This is a schematic diagram of a communication device 1600 provided in an embodiment of this application. The communication device 1600 can correspondingly implement the functions or steps implemented by the transmitting end in the above-described method embodiments, and can also correspondingly implement the functions or steps implemented by the receiving end in the above-described method embodiments. The communication device may include a processing module 1610 and a transceiver module 1620. In one possible implementation, a storage unit may also be included, which can be used to store instructions (code or program) and / or data. The processing module 1610 and the transceiver module 1620 can be coupled to the storage unit. For example, the processing module 1610 can read the instructions (code or program) and / or data in the storage unit to implement the corresponding method. The above-described units can be set independently, or partially or completely integrated. For example, the transceiver module 1620 may include a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The entity corresponding to the transceiver module 1620 can be a transceiver or a communication interface.

[0328] In some possible implementations, the communication device 1600 can correspondingly implement the behavior and functions of the transmitting end in the above method embodiments. For example, the communication device 1600 can be a transmitting end, or a component (e.g., a chip or circuit) applied in the transmitting end. The transceiver module 1620 can, for example, be used to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 14 , Figure 15 In this embodiment, all receive or send operations are performed by the sending end. The processing module 1610 is used to execute... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 14 , Figure 15 In the embodiments, all operations performed by the sending end other than the sending and receiving operations are included, for example... Figure 8Step 801 in the illustrated embodiment.

[0329] In some possible implementations, the communication device 1600 can correspondingly implement the behavior and functions of the receiving end in the above method embodiments. For example, the communication device 1600 can be a receiving end, or it can be a component (e.g., a chip or circuit) applied in the receiving end. The transceiver module 1620 can, for example, be used to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 14 , Figure 15 In this embodiment, all receiving or transmitting operations are performed by the receiving end. The processing module 1610 is used to execute... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 14 , Figure 15 In the embodiments, all operations performed by the receiving end other than the sending and receiving operations are included.

[0330] Figure 17 This is a schematic diagram of another communication device 170 provided in an embodiment of this application. Figure 17 The communication device mentioned above can be either the sending end or the receiving end.

[0331] like Figure 17 As shown, the communication device 170 includes at least one processor 1710 and a transceiver 1720.

[0332] In some embodiments of this application, the processor 1710 and transceiver 1720 can be used to perform functions or operations performed by the transmitting end. For example, the transceiver 1720 is used to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 14 , Figure 15 In this embodiment, all receive or transmit operations are performed by the transmitting end. The processor 1710 is used, for example, to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 14 , Figure 15 In the embodiments, all operations performed by the sending end except for sending and receiving operations are performed.

[0333] In some embodiments of this application, the processor 1710 and transceiver 1720 can be used to perform functions or operations performed by the receiving end. For example, the transceiver 1720 is used to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12, Figure 14 , Figure 15 In this embodiment, all receive or transmit operations are performed by the receiving end. The processor 1710 is used, for example, to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 14 , Figure 15 In the embodiments, all operations performed by the receiving end other than the sending and receiving operations are included.

[0334] Transceiver 1720 is used to communicate with other devices / appliances via a transmission medium. Processor 1710 uses transceiver 1720 to send and receive data and / or signaling, and to implement the methods in the above-described method embodiments. Processor 1710 can implement the functions of processing module 1610, and transceiver 1720 can implement the functions of transceiver module 1620.

[0335] Optionally, transceiver 1720 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is primarily used for converting baseband signals to RF signals and processing RF signals. The antenna is primarily used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

[0336] Optionally, the communication device 170 may further include at least one memory 1730 for storing program instructions and / or data. The memory 1730 is coupled to the processor 1710. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 1710 may operate in conjunction with the memory 1730. The processor 1710 may execute program instructions stored in the memory 1730. At least one of the at least one memory may be included in the processor.

[0337] Processor 1710 can read software programs from memory 1730, interpret and execute the instructions of the software programs, and process the data of the software programs. When data needs to be transmitted wirelessly, processor 1710 performs baseband processing on the data to be transmitted and outputs a baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to processor 1710. Processor 1710 converts the baseband signal into data and processes the data.

[0338] In another implementation, the aforementioned radio frequency circuits and antennas can be set up independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuits and antennas can be arranged in a remote manner, independent of the communication device.

[0339] This application embodiment does not limit the specific connection medium between the transceiver 1720, processor 1710, and memory 1730. This application embodiment... Figure 17 The memory 1730, processor 1710, and transceiver 1720 are connected via a bus 1740, and the bus is in... Figure 17 The connections between other components are shown in thick lines only and are not intended to be limiting. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 17 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0340] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0341] Figure 18 This is a schematic diagram of another communication device 180 provided in an embodiment of this application. (See attached diagram.) Figure 18 As shown, Figure 18 The communication device shown includes logic circuit 1801 and interface 1802. Figure 16 The processing module 1610 can be implemented using logic circuit 1801. Figure 16 The transceiver module 1620 can be implemented using interface 1802. The logic circuit 1801 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 1802 can be a communication interface, input / output interface, etc. In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment.

[0342] In some embodiments of this application, the logic circuit and interface can be used to perform the functions or operations performed by the sending end as described above.

[0343] In some embodiments of this application, the logic circuit and interface can be used to perform the functions or operations performed by the receiving end described above.

[0344] This application also provides a computer-readable storage medium storing a computer program or instructions that, when run on a computer, cause the computer to perform the methods of the above embodiments.

[0345] This application also provides a computer program product, which includes instructions or a computer program that, when run on a computer, causes the methods in the above embodiments to be executed.

[0346] This application also provides a communication system, including the aforementioned transmitting end and the aforementioned receiving end.

[0347] This application also provides a chip, which includes: a communication interface and a processor; the communication interface is used for signal transmission and reception of the chip; the processor is used to execute computer program instructions, causing a communication device including the chip to perform the methods as described in the above embodiments.

[0348] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The aforementioned computer program product includes one or more computer programs or instructions. When the aforementioned computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The aforementioned computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The aforementioned computer program or instructions can be stored in a computer-readable storage medium, or transferred from one computer-readable storage medium to another. For example, the aforementioned computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The aforementioned computer-readable storage medium can be any available medium accessible to a computer, or a data storage device such as a server or data center integrating one or more available media. The aforementioned available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

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

Claims

1. A communication method for ultra-wideband (UWB), characterized by, The method comprises: generating a confirmation announcement ADV-CONF message, the ADV-CONF message comprising a ranging initiation SOR message list, each SOR message list element comprising an address of a receiving end and a corresponding SOR time offset of the receiving end, the corresponding SOR time offset of the receiving end being used to indicate a transmission time of a SOR message to be received by the receiving end; transmitting the ADV-CONF message.

2. The method of claim 1, wherein, The method further comprises: transmitting the SOR message to the receiving end, the SOR message indicating a time offset of the receiving end for transmitting a poll POLL message.

3. A communication device, characterized by The communication device comprises a processor coupled with a memory, the memory storing computer program instructions, the processor being configured to execute the computer program instructions to cause the communication device to perform the method of claim 1 or 2.

4. A chip, characterized by The method comprises: a communication interface for signal transceiving of the chip; and a processor configured to execute computer program instructions to cause a communication device comprising the chip to perform the method of claim 1 or 2. The computer readable storage medium stores a computer program, the computer program comprising program instructions which, when executed, cause a computer to perform the method of claim 1 or 2.

5. A computer readable storage medium, characterized in that, ​

Images