Communication methods and related products for UWB

Abstract

The present invention discloses a communication method and related products for UWB. The present application may be applicable to UWB-based wireless personal area network systems, sensing systems, positioning systems, ranging systems, or communication systems, and may further be applicable to wireless local area network systems supporting 802.11 series protocols such as the next-generation Wi-Fi protocol of IEEE 802.11ax, e.g., 802.11be or Wi-Fi 7, and the next-generation protocol of 802.11be, e.g., Wi-Fi 8. The method includes the steps of: generating instruction information, the instruction information indicating that a frame counter (FC) is to be constructed based on a first field in a first message, the first field indicating the type of the first message; and transmitting the instruction information. The method in the embodiments of the present application is capable of reducing signaling overhead.

Description

Technical Field

[0001] This application claims priority to Chinese Patent Application No. 202310493176.4, titled "Communication Method and Related Products for UWB", filed with the China National Intellectual Property Administration on April 28, 2023, the entire content of which is incorporated herein by reference.

[0002] Technical Field This application relates to the field of communications, and in particular, to a communication method and related products for UWB.

Background Art

[0003] Ultra-wideband (UWB) technology is a wireless communication and sensing / ranging technology in which non-sinusoidal narrow impulses at the nanosecond level are used for signal transmission. Therefore, ultra-wideband occupies a wide spectral range. Due to the narrow impulses and extremely low radiation spectral density of ultra-wideband, UWB systems have advantages such as strong multipath resolution, low power consumption, and high confidentiality, and have attracted wide attention in the industry. The Institute of Electrical and Electronics Engineers (IEEE) has incorporated UWB technology into the IEEE 802 series of wireless standards and released the wireless personal area network (WPAN) standard IEEE 802.15.4a based on UWB technology and its evolved version IEEE 802.15.4z. Currently, the formulation of the next-generation UWB WPAN standard IEEE 802.15.4ab is under discussion. UWB is planned to be comprehensively upgraded in the IEEE 802.15.4ab standard.

[0004] Due to the large bandwidth of ultra-wideband systems, UWB devices require ultra-high-speed data reception and transmission capabilities, but the spectral efficiency of impulse radio ultra-wideband (IR-UWB) systems based on impulse transmission is low. When transmitting the same information, IR-UWB systems require much higher power consumption overhead than other narrowband short-range protocols (such as Bluetooth and Zigbee protocols). In ranging or sensing scenarios, the accuracy of measurement or sensing is closely related to the signal bandwidth. The larger the signal bandwidth, the higher the sensing or ranging accuracy. Therefore, people consider receiving and transmitting ranging or sensing reference signals via UWB systems and transmitting all other data by using narrowband (NB) protocols, thereby ensuring ranging and sensing accuracy while reducing power consumption. A UWB technical solution that combines narrow-band-assisted UWB with multi-millisecond transmission is also called narrow-band-assisted multi-millisecond ultra-wideband (NBA-MMS UWB).

[0005] In NBA-MMS UWB measurement scenarios, to reduce the duty cycle of NB signals, messages transmitted using the NB protocol, such as start-of-ranging (SOR) messages, may be messages in a compressed physical layer service data unit (PHY) format. However, the signaling overhead of messages in the compressed PSDU format is high. [Overview of the project]

[0006] Embodiments of this application disclose a communication method and related products for UWB that solve the problem of FC construction of messages in a compressed PSDU format and reduce signaling overhead.

[0007] According to the first aspect, the embodiment of the present application provides a communication method for ultra-wideband UWB, wherein the method: Steps include: generating instruction information, which indicates that a frame counter (FC) is constructed based on a first field in a first message, where the first field indicates the type of the first message; and This includes the step of sending instruction information.

[0008] In this embodiment of the present application, instructional information is transmitted indicating that an FC is to be constructed based on a first field in a first message, thereby preventing the first message from carrying a packet number (PN) field, and thereby reducing signaling overhead.

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

[0010] In this implementation, the second field indicates the timeout for receiving SOR messages, which in turn reduces the duration of waiting for SOR messages and thereby reduces power consumption.

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

[0012] In this implementation, the second message further includes a field indicating whether the second field exists, and as a result, the receiving end knows whether the second field exists.

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

[0014] In this implementation, the second message is an ADV-CONF message, and existing ADV-CONF messages may be reused, resulting in minimal impact on existing protocols.

[0015] In a possible implementation of the first embodiment, the step of transmitting instruction information is: The process includes the step of sending a first message, the first message containing instructional information.

[0016] In this implementation, the first message contains instruction information, and no additional messages are required to carry this information. Therefore, the signaling overhead is low.

[0017] According to a second aspect, the embodiment of the present application provides another communication method for ultra-wideband UWB, the method being: Steps include: receiving instruction information, which indicates constructing an FC based on a first field in a first message, where the first field indicates the type of the first message; and This includes the step of building an FC based on the instruction information.

[0018] In this embodiment of the present application, the FC is constructed based on instruction information, and the first message does not need to carry the PN field, thereby reducing signaling overhead.

[0019] In a possible implementation of the second embodiment, the step of constructing the FC based on the instruction information is: The process includes the step of constructing a Field Correction (FC) based on a first field, a measurement round identifier corresponding to a first message, and a measurement block identifier corresponding to a first message, in accordance with the instruction information.

[0020] In this implementation, the FC is constructed based on a first field, a measurement round identifier corresponding to the first message, and a measurement block identifier corresponding to the first message. The first message does not need to carry the PN field, and as a result, signaling overhead can be reduced.

[0021] In a possible implementation of the second embodiment, the step of receiving instruction information is: The step includes receiving a first message, the first message containing instructional information.

[0022] In this implementation, the first message contains instruction information, and no additional messages are required to carry this information. Therefore, the signaling overhead is low.

[0023] In a possible implementation of the first or second embodiment, indicating that the instruction information constructs an FC based on a first field in the first message means that the instruction information constructs an FC based on the order information and the first field in the message list for the list element corresponding to the first message in the message list.

[0024] In this implementation, the instruction information indicates that the FC is constructed based on the sequence information in the message list and the first field for the list element corresponding to the first message in the message list. The first message does not need to carry the PN field and the measured round index, and as a result, signaling overhead can be reduced.

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

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

[0027] In a possible implementation of the first or second aspect, the message list is included in a third message that was sent before the first message was sent.

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

[0029] In a possible implementation of the first or second aspect, the indication information further indicates whether the first message includes a measurement round identifier.

[0030] In this implementation, the indication information further indicates whether the first message includes a measurement round identifier, and as a result, the receiving end knows whether the first message includes a measurement round identifier based on the indication information.

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

[0032] In this implementation, the indication information further indicates whether the first message includes a measurement block identifier, and as a result, the receiving end knows whether the first message includes a measurement block identifier based on the indication information.

[0033] According to a third aspect, an embodiment of the present application provides another communication method for ultra-wideband UWB, and this method includes: Receiving a first message; and A step of constructing a FC based on a first field in a first message, wherein the first field indicates the type of the first message.

[0034] In this embodiment of the present application, the FC is constructed based on a first field in a first message, and the first message does not need to carry the PN field, thus reducing signaling overhead.

[0035] In a possible implementation of the third aspect, the step of constructing a frame count FC based on a first field in the first message is: The process includes the step of constructing a FC based on a first field, a measurement round identifier corresponding to a first message, and a measurement block identifier corresponding to a first message.

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

[0037] In possible implementations of the first, second, or third aspect, the first message is a message in a compressed PSDU format.

[0038] In possible implementations of the first, second, or third embodiment, the first message is a control message in the NBA-MMS UWB measurement process.

[0039] In possible implementations of the first, second, or third aspect, the first message is one of the following: a start-of-ranging SOR message, a polling / initiating POLL message, a reporting message, or a response message.

[0040] According to a fourth aspect, the embodiment of the present application provides another communication method for ultra-wideband UWB, the method being: Steps include: generating instruction information, which indicates that the instruction information constructs an FC based on the order information in the message list for the list element corresponding to the first message in the message list; and This includes the step of sending instruction information.

[0041] In this implementation of the present application, the instruction information is: This demonstrates how to construct a FC (Functional Character) based on the ordering information within the message list for the list element corresponding to the first message in the message list, thereby avoiding the explicit transport of round indices and reducing signaling overhead.

[0042] According to a fifth aspect, the embodiment of the present application provides another communication method for ultra-wideband UWB, the method being: This is a step in which instruction information is received, and the instruction information is Steps showing how to construct an FC based on the order information in the message list for the list element corresponding to the first message in the message list; and This includes the step of building an FC based on the instruction information.

[0043] In this implementation of the present application, the FC is constructed based on instruction information, thereby avoiding the explicit transport of the measuring round index and reducing signaling overhead.

[0044] In a possible implementation of the fifth aspect, the step of constructing the FC based on the instruction information is: The process includes the step of constructing a FC based on instruction information, a measurement slot identifier corresponding to the first message, sequence information, and a measurement block identifier corresponding to the first message.

[0045] In this implementation, the FC is constructed based on a measurement slot identifier corresponding to the first message, sequence information, and a measurement block identifier corresponding to the first message. As a result, explicit transport of the measurement round index can be avoided, and signaling overhead can be reduced.

[0046] According to the sixth aspect, the embodiment of the present application provides another communication method for ultra-wideband UWB, the method being: The step of receiving a first message; and The step includes constructing a message cluster (FC) based on the order information within the message list for the list element corresponding to the first message in the message list.

[0047] In this embodiment of the present application, the FC is constructed based on the ordering information in the message list for the list element corresponding to the first message in the message list, thereby avoiding the explicit transport of the measured round index and reducing signaling overhead.

[0048] In a possible implementation of the sixth aspect, the step of constructing a frame count FC based on the order information in the message list for a list element corresponding to a first message in the message list is: The process includes the step of constructing a measurement block identifier based on a measurement slot identifier corresponding to a first message, sequence information, and a measurement block identifier corresponding to a first message.

[0049] In a possible implementation of the sixth aspect, The steps for constructing a frame count FC based on the order information within the message list for the list element corresponding to the first message in the message list are: The process includes the step of constructing an FC based on a first field in the first message, sequence information, and a measurement block identifier corresponding to the first message.

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

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

[0052] In possible implementations of the fourth, fifth, or sixth aspect, the message list is included in a third message sent before the first message is sent.

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

[0054] In possible implementations of the fourth, fifth, or sixth aspect, the instruction information further indicates whether the first message includes a measurement round identifier.

[0055] In this implementation, the instruction information further indicates whether the first message contains a measurement round identifier, and as a result, the receiving end knows whether the first message contains a measurement round identifier based on the instruction information.

[0056] In possible implementations of the fourth, fifth, or sixth embodiment, the instruction information further indicates whether the first message includes a measurement block identifier.

[0057] In this implementation, the instruction information further indicates whether the first message contains a measurement block identifier, and as a result, the receiving end knows whether the first message contains a measurement block identifier based on the instruction information.

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

[0059] In possible implementations of the fourth, fifth, or sixth aspect, the first message is a message in a compressed PSDU format.

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

[0061] In possible implementations of the fourth, fifth, or sixth aspect, the first message is one of the following: a SOR message, a polling / initiating POLL message, a reporting message, or a response message.

[0062] According to the seventh aspect, an embodiment of the present application provides a communication device. The communication device has functions that perform the behavior of an embodiment of the method of the first aspect. The communication device may be a communication device, or a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of performing all or part of the functions of a communication device. The functions of the communication device may be performed by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The processing module is configured to generate instruction information, which indicates constructing an FC based on a first field in a first message, where the first field indicates the type of the first message. The transceiver module is configured to transmit the instruction information.

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

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

[0065] For the technical effects resulting from possible implementations of the seventh aspect, please refer to the description of the technical effects of the first aspect or possible implementations of the first aspect.

[0066] According to the eighth aspect, an embodiment of the present application provides a communication device. The communication device has functions that perform the behavior of an embodiment of the method of the second aspect. The communication device may be a communication device, or a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of performing all or part of the functions of the communication device. The functions of the communication device may be performed by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive instruction information, which indicates to construct a FC based on a first field in a first message, where the first field indicates the type of the first message. The processing module is configured to construct a FC based on the instruction information.

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

[0068] In a possible implementation of the eighth aspect, the transceiver module is configured to receive a first message, the first message containing instructional information.

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

[0070] For the technical effects resulting from possible implementations of the eighth aspect, please refer to the description of the technical effects of the second aspect or possible implementations of the second aspect.

[0071] According to the ninth aspect, an embodiment of the present application provides a communication device. The communication device has functions that perform the behavior of an embodiment of the method of the third aspect. The communication device may be a communication device, or a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of performing all or part of the functions of the communication device. The functions of the communication device may be performed by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a first message. The processing module is configured to construct a FC based on a first field in the first message, where the first field indicates the type of the first message.

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

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

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

[0075] For the technical effects resulting from a possible implementation of the ninth aspect, please refer to the description of the technical effects of the third aspect or a possible implementation of the third aspect.

[0076] According to the tenth aspect, an embodiment of the present application provides a communication device. The communication device has functions that perform the actions of the embodiment of the method of the fourth aspect. The communication device may be a communication device, or a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of performing all or part of the functions of a communication device. The functions of the communication device may be performed by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to generate instruction information, which is This demonstrates constructing a Message Card (FC) based on the ordering information within the message list for the list element corresponding to the first message in the message list. The transceiver module is configured to transmit instruction information.

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

[0078] For the technical effects resulting from possible implementations of the tenth aspect, please refer to the description of the technical effects of the fourth aspect or possible implementations of the fourth aspect.

[0079] According to the eleventh aspect, an embodiment of the present application provides a communication device. The communication device has functions that perform the behavior of an embodiment of the method of the fifth aspect. The communication device may be a communication device, or a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of performing all or part of the functions of a communication device. The functions of the communication device may be performed by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive instruction information, which indicates that a FC is constructed based on sequence information in the message list for a list element corresponding to a first message in the message list. The processing module is configured to construct the FC based on the instruction information.

[0080] In a possible implementation of the eleventh embodiment, the processing module is configured to construct the FC based on instruction information, a measurement slot identifier corresponding to a first message, sequence information, and a measurement block identifier corresponding to a first message.

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

[0082] For the technical effects resulting from possible implementations of the eleventh aspect, please refer to the description of the technical effects of the fifth aspect or possible implementations of the fifth aspect.

[0083] According to the twelfth aspect, an embodiment of the present application provides a communication device. The communication device has functions that perform the actions of an embodiment of the method of the sixth aspect. The communication device may be a communication device, or a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of performing all or part of the functions of the communication device. The functions of the communication device may be performed by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a first message. The processing module is configured to construct a FC based on sequence information in a message list for list elements corresponding to the first message in the message list.

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

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

[0086] For possible implementations of the communication device in the twelfth aspect, please refer to the possible implementations in the sixth aspect.

[0087] For the technical effects resulting from possible implementations of the twelfth aspect, please refer to the description of the technical effects of the sixth aspect or possible implementations of the sixth aspect.

[0088] According to the 13th aspect, an embodiment of the present application provides another communication device. The communication device includes a processor, the processor is coupled to a memory, the memory is configured to store a program or instruction, and when the program or instruction is executed by the processor, the communication device is capable of performing a method according to any one of the first to sixth aspects.

[0089] In this embodiment of the present application, the process of transmitting information (or signals) in the method can be understood as the process of outputting information based on instructions from a processor. When information is output, the processor sends the information to a transceiver, causing the transceiver to transmit the information. After the information has been output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver receives that information and inputs it to the processor. Furthermore, after the transceiver receives the information, it may require further processing of that information before it is input to the processor.

[0090] Operations involving the processor, such as sending and / or receiving, may generally be understood as instructions output by the processor unless otherwise specified, or unless such operations are inconsistent with the actual function or internal logic of the operations in the relevant description.

[0091] In the implementation process, the processor may be a processor specifically configured to perform these methods, or it may be a processor, such as a general-purpose processor, that executes computer instructions in memory to perform these methods. For example, the processor may be further configured to execute a program stored in memory. Once the program is executed, the communication device becomes capable of performing the methods shown in the first embodiment or any possible implementation of the first embodiment.

[0092] In possible implementations, memory is located outside the communication device. In possible implementations, memory is located inside the communication device.

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

[0094] In possible implementations, the communication device further includes a transceiver, which is configured to receive signals, transmit signals, or do the same.

[0095] According to the fourteenth aspect, an embodiment of the present application provides another communication device, the communication device comprising a processing circuit and an interface circuit, the interface circuit being configured to acquire or output data, and the processing circuit being configured to perform a method according to any one of the first to sixth aspects.

[0096] According to the fifteenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer is able to perform a method according to any one of the first through sixth aspects.

[0097] According to the sixteenth aspect, the embodiment of the present application provides a computer program product. The computer program product includes a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer is able to perform a method according to any one of the first through sixth aspects.

[0098] According to the 17th aspect, the embodiment of the present application provides a communication system including a communication device according to the 7th aspect or any one of the possible implementations of the 7th aspect, and a communication device according to the 8th aspect or any one of the possible implementations of the 8th aspect.

[0099] According to the 18th aspect, the embodiment of the present application provides a communication system including a communication device according to the 10th aspect or any one of the possible implementations of the 10th aspect, and a communication device according to the 11th aspect or any one of the possible implementations of the 11th aspect.

[0100] According to the 19th aspect, an embodiment of the present application provides a chip including a processor and a communication interface. The processor reads instructions stored in memory via the communication interface and executes a method according to any one of the first to sixth aspects. [Brief explanation of the drawing]

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

[0102] [Figure 1] Figure 1 shows the phases of a distance measurement round in the conventional technology.

[0103] [Figure 2] Figure 2 shows a distance measuring block in the conventional technology.

[0104] [Figure 3] Figure 3 shows the initialization process for NBA-MMS UWB ranging.

[0105] [Figure 4A] Figure 4A shows a diagram of one-to-many NBA-MMS UWB ranging.

[0106] [Figure 4B]Figure 4B shows a diagram of one-to-many NBA-MMS UWB ranging in interlaced mode.

[0107] [Figure 5] Figure 5 shows an example of a star topology structure.

[0108] [Figure 6] Figure 6 shows an example of a point-to-point topology structure or a mesh topology structure.

[0109] [Figure 7] Figure 7 shows an example of a UWB system to which the technical solution according to the embodiment of this application can be applied.

[0110] [Figure 8] Figure 8 is a flowchart of the communication method for UWB according to the embodiment of the present application.

[0111] [Figure 9] Figure 9 shows the NBA-MMS UWB ranging process according to an embodiment of the present application.

[0112] [Figure 10] Figure 10 shows an interaction procedure for another communication method for UWB according to an embodiment of the present application.

[0113] [Figure 11] Figure 11 shows an interaction procedure for another communication method for UWB according to an embodiment of the present application.

[0114] [Figure 12] Figure 12 shows an interaction procedure for another communication method for UWB according to an embodiment of the present application.

[0115] [Figure 13]Figure 13 shows the initialization process for pre-configuring one-to-many NBA-MMS UWB ranging.

[0116] [Figure 14] Figure 14 shows an interaction procedure for another communication method for UWB according to an embodiment of the present application.

[0117] [Figure 15] Figure 15 shows an interaction procedure for another communication method for UWB according to an embodiment of the present application.

[0118] [Figure 16] Figure 16 is a diagram showing the structure of a communication device 1600 according to an embodiment of the present application.

[0119] [Figure 17] Figure 17 shows the structure of another communication device 170 according to an embodiment of the present application.

[0120] [Figure 18] Figure 18 is a diagram showing the structure of another communication device 180 according to an embodiment of the present application. [Modes for carrying out the invention]

[0121] In the specification, claims, or accompanying drawings of this application, terms such as “First,” “Second,” and similar terms are intended solely to distinguish different subjects and do not indicate a specific order. It will be understood that the various numbers in the embodiments of this application are used merely for distinction to facilitate explanation and are not used to limit the scope of the embodiments of this application. The sequence numbers of the aforementioned processes do not imply execution order, and the execution order of processes should be determined based on the function and internal logic of the processes. Furthermore, terms such as “includes” and “have,” and any other variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device including a series of steps or units is not limited to the listed steps or units, but rather optionally includes further steps or units not listed, or optionally includes other steps or units specific to these processes, methods, products, or devices.

[0122] The “embodiments” referred to in the specification indicate that certain features, structures, or characteristics described with reference to these embodiments may be included in at least one embodiment of the present application. The wording found in various parts of the specification does not necessarily refer to the same embodiment, nor are they necessarily independent or optional embodiments exclusive to another embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in the specification may be combined with other embodiments.

[0123] The terms used in the following embodiments of this application are intended solely to describe specific embodiments and are not intended to limit this application. The individual terms “one,” “a,” “an,” “the,” and “this” used in this specification and the appended claims of this application are also intended to include plural forms unless explicitly specified otherwise in the context. It should also be understood that the terms “and / or” used in this application mean and include any or all possible combinations of one or more enumerated items. For example, “A and / or B” could represent three cases: only A exists, only B exists, and both A and B exist, where A and B may be singular or plural. The term “plural” used in this application means two or more. In the textual description of this application, the character “ / ” generally indicates an “or” relationship between related subjects.

[0124] In the embodiments of this application, "B corresponding to A" would be understood to indicate that there is a correspondence between A and B, and that B may be determined based on A. However, it should also be noted that determining (or generating) B based on A does not mean that B is determined (or generated) based solely on A, and that B may alternatively be determined (or generated) based on A and / or other information.

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

[0126] Rangefinding round, positioning round, sensing round, and measurement period

[0127] The IEEE 802.15.4z standard defines a single ranging process as a ranging round. The IEEE 802.15.4z standard defines a ranging round as follows: A ranging round is a period of time sufficient to complete a complete ranging task, and that period is related to a group of ERDEVs participating in ranging message exchange (a ranging round is a period of sufficient duration to complete one entire ranging-measurement cycle, including the set of ERDEVs participating in ranging message exchange). The minimum processing time unit of each ranging round is a ranging slot. A ranging round can be divided into three phases: a ranging control phase, a ranging phase, and a measurement report phase. Figure 1 shows the phases of a ranging round in the prior art. Details are shown in Figure 1. The IEEE 802.15.4z standard defines the ranging control phase as containing one ranging slot. However, the IEEE 802.15.4ab standard, currently under discussion and development, may include two or more distance measurement slots in the distance measurement control phase.

[0128] In the first slot of the ranging round shown in Figure 1, the controller sends a ranging control message (RCM). The RCM can carry update messages regarding the round structure of the ranging round, such as updates to the round duration.

[0129] Current and previous ranging rounds (hereinafter referred to as "rounds") may or may not be temporally adjacent. The duration values ​​of different rounds may or may not be the same. For the purposes of the default explanation, the example below uses the same duration values ​​for different rounds.

[0130] Figure 2 shows a case where the current and previous ranging rounds (hereinafter abbreviated as "rounds") are not adjacent in time. Figure 2 is a diagram of a ranging block in the prior art. As shown in Figure 2, a ranging block may be a time structure containing multiple ranging rounds. Optionally, ranging blocks may appear periodically and repeatedly. Optionally, the duration of all ranging rounds within a ranging block may be equal. As shown in Figure 2, for a particular ranging process, the initiator and responder perform the ranging process in a ranging round within a ranging block, for example, round 1 shown in Figure 2. In this application, the initiator may also be called the initiator, i.e., the UWB device that initiates the ranging / sensing / communication procedure. In the ranging / sensing / communication process, the initiator may be the transmitting end or the receiving end. In this application, the initiator, which may also be called the responder, is a UWB device that responds to a ranging / sensing / communication process initiated by a UWB initiator device. In the ranging / sensing / communication process, the responder may be the transmitting end or the receiving end. After a ranging round is completed, a specific ranging process is performed in round 1 of the next ranging block. As can be seen from Figure 2, two adjacent rounds 1 are not adjacent in time; that is, there is a time interval between the two adjacent rounds 1. During the interval slot between two adjacent rounds 1, the device may turn off the receiver and put it to sleep to conserve power. The duration values ​​of adjacent ranging blocks may be the same or different. For example, adjacent ranging blocks with different duration values ​​may be located within a hyper-block. Hereafter, an example where the duration values ​​of adjacent ranging blocks are the same will be used for the default explanation.

[0131] Before NBA-MMS UWB ranging can be performed (or enabled), initialization and establishment processes must be performed (or implemented) between the relevant devices. For example, the initiator is the controller. The initiator must first broadcast an announcement message to all responders to inform them that NBA-MMS UWB ranging now needs to be performed. The broadcast announcement message may be carried in an advertisement poll message / advertisement poll (ADV-POLL) message. After receiving the ADV-POLL message, the responders return an advertisement response message / advertisement response (ADV-RESP) message to the initiator if they need ranging to be performed. In the ADV-RESP message, the responder carries the parameter setting information required by the responder. After receiving an ADV-RESP message, the initiator may decide whether to accept the parameter settings proposed by the responder, or may notify the responder of the final parameter setting result via a start-of-ranging (SOR) message. The SOR message may carry a parameter delivery confirmation message for the responder's ADV-RESP message, or it may carry a parameter change / update message in the responder's ADV-RESP message. After the responder receives a SOR message during a certain time period, the initiator and the responder can start the NBA-MMS UWB ranging process. The length of the time period may be determined by a time offset relative to the MMS POLL information in the SOR message. The NBA-MMS UWB ranging initialization process described above is shown in Figure 3. Figure 3 is a diagram of the NBA-MMS UWB ranging initialization process.

[0132] The application scenario for NBA-MMS UWB ranging may be a one-to-one scenario, meaning one initiator corresponds to one responder, or it may be a one-to-many scenario, as shown in Figure 4A, meaning one initiator corresponds to multiple responders. Figure 4A is a diagram of a one-to-many NBA-MMS UWB ranging scenario.

[0133] In the one-to-many NBA-MMS UWB ranging shown in Figure 4A, the initiator and each responder perform one NBA-MMS UWB ranging operation each. In other words, the initiator and each responder complete the interaction process of polling / start (POLL) and response (RESP) messages, multi-millisecond (MMS) block division interaction, ranging, and ranging result reporting (carried in a report message). In this specification, response messages may be referred to as RESP messages, response messages, or RESPONSE messages. The ranging result reporting includes a report message sent by the responder to the initiator and a report message sent by the initiator to the responders. The ranging process shown in Figure 4A may be referred to as one-to-many NBA-MMS UWB ranging in concatenate mode. It should be noted that this application is also applicable to one-to-many ranging processes in other modes, such as one-to-many NBA-MMS UWB ranging in interlacing mode, as shown in Figure 4B. Figure 4B is a diagram of one-to-many NBA-MMS UWB ranging in interlacing mode. As shown in Figure 4B, in one-to-many NBA-MMS UWB ranging in interlacing mode, each responder transmits MMS subblocks sequentially, and the next responder transmits all MMS subblocks without waiting for the previous responder to complete the transmission of all MMS subblocks. In embodiments of this application, one-to-many NBA-MMS UWB in concatenated mode will be used below as an example for illustrative purposes. The methods in the relevant embodiments are also applicable to one-to-many NBA-MMS UWB processes in interlacing mode, which will not be described in detail.

[0134] In this embodiment of the present application, a single positioning process, i.e., the process of completing a positioning task, is defined as a positioning round. A positioning round may have a different name, which is not limited to the present application. A positioning round may be a period of time (or time cycle) sufficient to complete a complete positioning task. The meaning of a positioning round is the same as that of a ranging round, the difference being that a ranging round is a period of time corresponding to ranging, while a positioning round is a period of time corresponding to positioning. The minimum processing time unit of each positioning round is a positioning slot. A positioning round can be divided into three phases: a positioning control phase, a positioning phase, and a positioning report phase.

[0135] In this embodiment of the present application, a single sensing process, i.e., a process for completing a sensing task, is defined as a sensing round. A sensing round may have a different name, which is not limited to the present application. A sensing round may be a period of time (or time cycle) sufficient to complete a complete sensing task. The meaning of a sensing round is the same as that of a distance-measuring round, the difference being that a distance-measuring round is a period of time corresponding to distance measurement, while a sensing round is a period of time corresponding to sensing. The minimum processing time unit of each sensing round is a sensing slot. A sensing round can be divided into three phases: a sensing control phase, a sensing phase, and a sensing report phase.

[0136] The measurement period is the time frame in which one or more UWB devices complete one or more measurement tasks. These measurement tasks may be ranging tasks, positioning tasks, sensing tasks, or similar. The measurement period may also consist of ranging rounds, positioning rounds, or sensing rounds. It should be noted that the ranging rounds described below may be replaced by sensing rounds, positioning rounds, or measurement periods (which may also be called measurement rounds). Accordingly, ranging tasks may be replaced by sensing tasks, positioning tasks, or measurement tasks.

[0137] Furthermore, it should be noted that the names of different phases within a single measurement round (e.g., ranging round, sensing round, or positioning round) are merely examples and do not constitute any limitation on the scope of protection of this application. For example, the aforementioned measurement control phase may be understood as the phase used to set the parameters required in the measurement round. In another example, the measurement phase may be understood as the phase used to perform the measurement. In yet another example, the measurement result reporting phase may be understood as the phase used to report the measurement results, and may alternatively be called the end of the measurement phase. Furthermore, it should be noted that in embodiments of this application, the size of each field indicates the number of bits occupied by each field.

[0138] Compression header information element message format

[0139] To reduce the duty cycle of NB signals, ADV-POLL messages, ADV-RESP messages, SOR messages, and Report messages may be carried based on compressed header information element (compressed header IE) messages, as shown in Table 1-1 below. Table 1-1 shows an example of the format of a compressed header information element message. Table 1-1 [Table 1]

[0140] SHR (synchronization header) represents the synchronization header, PHR represents the PHY header, PSDU (PHY service data) represents the physical layer service data unit, and PHY (physical layer) represents the physical layer. Table 1-2 shows an exemplary format of a compressed PSDU. Table 1-2 [Table 2]

[0141] The Frame Control field is used to control the format of the header information element (header IE). The Frame Control field occupies 1 byte (octet / byte).

[0142] The address field indicates the device address of the device receiving the message shown in Table 1-1. The address field occupies 2 bytes.

[0143] The Message ID field (sometimes called the Message Identifier field) indicates the type of message shown in Table 1-1. In other words, the Message ID field indicates the type of message corresponding to the current compressed PSDU field. For example, the Message ID field indicates the size and type of data content carried in the Content field in Table 1-2. In the example shown in Table 1-2, the Message ID field occupies 1 byte. The Content field indicates the data content carried by the compressed PSDU. The value of the field is a variable value and is determined by the message content corresponding to the Message ID field.

[0144] The CRC field, sometimes called the cyclic redundancy check (CRC), is used to detect errors in the compressed PSDU in Table 1-2. The CRC field occupies 2 bytes.

[0145] Tables 1-1 and 1-2 show that messages (or data packets) in the compressed PSDU format do not contain a separate frame counter (FC) field. Since messages in the compressed PSDU format do not have an FC field, this also means that a nonce (a random number used only once) cannot be constructed by directly using the FC. In authentication protocols, a nonce is a random or pseudo-random number used to avoid replay attacks. The nonce is used to encrypt and authenticate messages. In this specification, authentication and verification have the same meaning.

[0146] To address the problem that nonces cannot be constructed using FC directly in compressed PSDU format messages, existing technical solutions (which may also be called prior art) are as follows: Based on the different timing structure characteristics of NBA-MMS ranging in the initialization phase and the measurement period phase (measurement cycle), nonces are constructed in different ways for compressed PSDU format messages transmitted in the corresponding phases.

[0147] In conventional technology, the solution for constructing a nonce for a compressed PSDU format message during the initialization phase of NBA-MMS ranging is as follows: 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., unencrypted payload) portion of these messages. The PN field is used to construct the nonce. In other words, the PN field is used to solve the aforementioned problem of constructing a nonce for a message in the compressed PSDU format. Table 2 uses an SOR message as an example. The SOR message includes a PN field. Table 2 is a schematic table of the PSDU format for a SOR message. Table 2 [Table 3]

[0148] The meaning of the message ID field in Table 2 is the same as that of the message ID field in Table 1-2. The message ID field in Table 2 occupies 7 bits. The meaning of the address field in Table 2 is the same as that of the address field in Table 1-2.

[0149] The Security Enable field indicates whether security encryption means (e.g., encryption / authentication) are used for the current message (i.e., the SOR message in Table 2). For example, if the value of the Security Enable field is 0, it indicates that security encryption means are not used for the current message; or, if the value of the Security Enable field is 1, it indicates that security encryption means are used for the current message.

[0150] The PN field is used by the receiving end to construct a nonce, which is used to authenticate the current message. The receiving end is the device that receives the SOR message in Table 2. The PN field occupies 4 bits.

[0151] The secure payload field indicates encrypted content. It contains the encrypted content within the current message. The length of the secure payload field is variable.

[0152] The MIC (message integrity code) field is used to verify whether a frame is authentic and whether an error occurred. The MIC field occupies 2 bits.

[0153] The nonce format based on the PN field shown in Table 2 is shown in Table 3. Table 3 [Table 4]

[0154] The source address field indicates the extended address of the device (i.e., the sender) that sends the frame to be validated.

[0155] The PN field is used by the receiving end to construct the nonce. In the compressed PSDU, the PN field is used as the missing FC field.

[0156] The Non-Security Level field indicates the security measures taken for the messages shown in Table 2.

[0157] Table 2 shows that by introducing the PN field into the SOR message, it is possible to construct the FC used in the nonce shown in Table 3, thereby enabling subsequent encryption / authentication of the frame (i.e., the SOR message shown in Table 2).

[0158] In conventional technology, the solution for constructing nonce for compressed PSDU format messages during the measurement period phase of NBA-MMS ranging is as follows: For ranging control messages such as POLL messages, response messages, and report messages, the nonce is constructed based on pre-known time-series information such as slot indexes / round indexes / block indexes of the ranging process. In other words, for ranging control messages such as POLL messages, response messages, and report messages, there is no need to add an explicit PN field for constructing a nonce to the open payload portion of these messages. For example, before sending ranging control messages such as POLL messages, response messages, and report messages, an SOR message carrying time-series information such as slot indexes / round indexes / block indexes is sent and used for FC construction and scheduling management of POLL messages / response messages / report messages during the measurement period phase (described later). After receiving the SOR message, the receiving end can learn the time-series information such as slot indexes / round indexes / block indexes related to the ranging process based on the received SOR message. The report message shown in Table 4 is used as an example. The format of the nonce constructed for the reporting message is shown in Table 5. Table 4 [Table 5]

[0159] In Table 4, the Message ID field, Security Enable field, and Address field correspond to the fields in Table 2, and further details are not provided here. Table 5 [Table 6]

[0160] In Table 5, the Source Address field indicates the extended address of the device sending the frame to be validated, the Slot Index field indicates the slot index (e.g., measured slot index) corresponding to the frame to be validated, the Round Index field indicates the round index (e.g., measured round index) corresponding to the frame to be validated, and the Block Index field indicates the block index (e.g., measured block index) corresponding to the frame to be validated. From Table 5, it can be seen that the nonce constructed for a reporting message is determined by the transmission time sequence corresponding to the reporting message, i.e., by the slot index / round index / block index. The method for generating the FC of the nonce is: FC = Slot Index || Round Index || Block Index The symbol "||" indicates concatenation. For example, suppose the slot index value is 0x03, the round index value is 0x10, and the block index value is 0x07. In this case, after concatenation, FC=0000001100000000000100000000000000000111 (binary) This is generated. All slot index fields, round index fields, and block index fields in Table 5 are included in the FC. In other words, slot index fields, round index fields, and block index fields in Table 5 are linked to the FC. This shows that the nonce is built on the FC.

[0161] As explained above, in existing solutions where nonce is constructed in relation to compressed PSDU format messages during the initialization phase, compressed PSDU format messages (e.g., SOR messages) must explicitly carry the PN field, which results in extra signaling overhead. In existing solutions where nonce is constructed in relation to compressed PSDU format messages during the measurement period phase, SOR messages and other messages must explicitly carry time-series information such as slot indexes / round indexes / block indexes, which also results in extra signaling overhead. Since the design philosophy of compressed PSDU is to minimize its inherent signaling overhead, the prior art is somewhat inconsistent with the design philosophy of compressed PSDU. This application provides a solution that makes it possible to construct nonce for compressed PSDU format messages without increasing signaling overhead. Below, we will first describe the scenarios to which the communication solution for UWB provided in this application is applicable.

[0162] The communication solutions for UWB provided in the embodiments of this application may operate in star topology, point-to-point topology, or mesh topology structures. The communication solutions for UWB provided in the embodiments of this application may also operate in other topology structures, this is not limited to this application. Figure 5 is a diagram of an example of a star topology structure. As shown in Figure 5, a star topology includes a central control node, for example, a personal area network (PAN) or coordinator as shown in Figure 5. The communication solutions for UWB provided in the embodiments of this application are applicable to data communication / sensing / distancing / positioning between a central control node and one or more other devices in a star topology. Figure 6 is a diagram of an example of a point-to-point topology structure or mesh topology structure. The communication solutions for UWB provided in the embodiments of this application are also applicable to communication / sensing / distancing / positioning between different devices in a point-to-point topology or mesh topology structure (Figure 6). In Figures 5 and 6, black nodes are full-function devices (FFDs), and white nodes are reduced-function devices (RFDs). FFDs can function as PAN coordinators or coordinators, while RFDs cannot function as PAN coordinators or coordinators. FFD devices can communicate with each other, and FFD devices and RFD devices can communicate with each other. RFD devices cannot communicate directly with each other; they can only communicate with FFD devices or transfer data externally through one FFD device. In a UWB system, an FFD may be an anchor device or a tag device with powerful computing capabilities (e.g., a UWB tag mounted on a smartphone), while an RFD is a tag device and possesses only a portion of the computing capabilities.

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

[0164] Figure 7 shows an example of a UWB system to which the technical solutions provided in embodiments of this application can be applied. The UWB system includes an anchor (only one anchor is shown) and one or more tags (only tags 1 and 2 are shown). The protocols supported by the anchor and tags may include protocols such as IEEE 802.15.4a, IEEE 802.15.4z, and IEEE 802.15.4ab. Indeed, with the continued evolution and development of communication technology, the WLAN protocol may further include next-generation protocols such as IEEE 802.15.4ab. The anchor may be an access point, and the tags may be stations (STAs). Both access points and STAs support the WLAN protocol, which may include IEEE 802.11be (or Wi-Fi 7, also known as the EHT protocol).

[0165] An access point is a device with wireless communication capabilities that supports communication according to the WLAN protocol and has the ability to communicate with other devices (e.g., stations or other access points) within a WLAN network. Naturally, an access point may have further capabilities to communicate with other devices. A UWB system includes one or more access point (AP) stations and one or more non-access point stations (non-AP STAs). For ease of explanation, in this specification, access point stations are referred to as access points (APs) and non-access point stations are referred to as stations (STAs).

[0166] An access point may be an entire device, or a chip, processing system, etc., installed within the entire device. A device on which a chip or processing system is installed can implement the methods and functions of the embodiments of this application under the control of the chip or processing system (i.e., AP). The AP in the embodiments of this application is a device that provides services to a Station (STA) and may support, for example, IEEE 802.15.4a, IEEE 802.15.4z, IEEE 802.15.4ab, or a successor to IEEE 802.15.4ab. For example, the AP may be a communications entity such as a communications server, router, switch, bridge, computer, mobile phone, or similar. AP may include anchors, macro base stations, micro base stations (also called small cells), pico base stations, femto base stations, 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 B or home node B, HNB), baseband units (BBUs), Wi-Fi access points (APs), integrated access and backhaul (IABs), or similar. Of course, AP may alternatively be chips and processing systems in various forms within devices for implementing the methods and functions in the embodiments of this application.

[0167] A station is a device having wireless communication capabilities, supporting communication according to the WLAN protocol, and having the ability to communicate with other stations or access points within a WLAN network. For example, an STA is any communication device that enables a user to communicate with an AP and further with the WLAN. The communication device may be an entire device, or it may be a chip, processing system, etc., installed within the entire device. A device in which a chip or processing system is 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). STA may include tag devices / smart tag devices, mobile phones, mobile stations (MS), tablet computers (pads), computers with wireless transceiver functionality (e.g., notebook computers), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-drive, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, subscriber units, cellular phones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, laptop computers, machine type communication (MTC) terminals, or similar devices. The station may include various handheld devices, in-vehicle devices, wearable devices, or computing devices with wireless communication capabilities, or other processing devices connected to a wireless modem.For example, the station may be a handheld device (handset), an in-vehicle device, a wearable device, a terminal in the Internet of Things or a vehicle-to-everything network, any form of terminal in 5G and post-5G communication systems, or similar devices having wireless communication capabilities. This is not limited to the present application. The station may support IEEE 802.15.4 series protocols such as IEEE 802.15a, IEEE 802.15.4z, and IEEE 802.15.4ab.

[0168] Unless otherwise specified, for the purposes of the default explanation below, we will use an example where the initiator is the controller. Accordingly, the methods provided in this application are applicable when the responder is the controller, or when the controller is a third-party device. Furthermore, unless otherwise specified, for the purposes of the default explanation below, we will use the one-to-many case, i.e., the case where one initiator corresponds to multiple responders. Accordingly, the methods provided in this application are applicable when multiple initiators correspond to multiple responders. Furthermore, unless otherwise specified, for the purposes of the default explanation below, we will use an example where, before each measurement round begins, the initiator broadcasts a setting update message for the measurement round (e.g., a ranging round) to all responders based on a measurement start message (e.g., a SOR message). Accordingly, after receiving the measurement round configuration update message, the responder completes the parameter update configuration and, based on the new parameters, starts measurements in this round and in subsequent measurement rounds (up to the next parameter update configuration). Accordingly, the method provided in the present application is applicable when the initiator broadcasts a measurement start message at a different time, for example, when the initiator broadcasts a measurement round configuration update message based on the measurement start message in the measurement reporting phase of each measurement round.

[0169] Furthermore, unless otherwise specified, for the purposes of the default description below, we will use the example in which the measurement start message is used to carry the setting update message for the measurement round to be transmitted. The corresponding description is also applicable when a different message is used to carry the setting update message for the measurement round to be transmitted. For example, in NBA-MMS UWB ranging, the method provided in this application is applicable when the initiator sends a POLL message to the responder that carries the setting update message for the measurement round. For example, in one-to-many NBA-MMS UWB ranging, the initiator sends a POLL message to the first responder that carries the setting update message for the ranging round. The first responder is the responder among several responders that performs the ranging with the initiator first in the time series. In this case, the POLL message is sent in a broadcast manner. In another example, in NBA-MMS UWB ranging, the responder sends a response message to the initiator that carries the setting update message for the measurement round. In another example, in NBA-MMS UWB ranging, the initiator (responder) sends a report message to the responder (initiator) that carries a message updating the setting of the measurement round. The method provided in this application is applicable to all the examples described above. Furthermore, for the sake of clarity, and as a default explanation, the following example assumes that in the first measurement start message, the sequence of list elements matches the sequence of device subscripts, i.e., list elements #0, #1, ..., and #N correspond to devices 0, 1, ..., and N, respectively. The corresponding explanation is also applicable to other cases. For example, the method provided in this application is applicable when list elements #0, #1, ..., and #N correspond to devices 2, 4, ..., and N, respectively. Furthermore, unless otherwise specified, the ranging process will be used as an example by default. Accordingly, the method provided in this application is applicable to other measurement processes such as sensing and positioning. In other words, for the sake of explanation, the following example will use the ranging process as the measurement process.Furthermore, unless otherwise specified, the following assumes that the current round and the previous round are not temporally adjacent by default. Accordingly, the method provided in this application is applicable to cases where the rounds are temporally adjacent.

[0170] Furthermore, unless otherwise specified, the following explanations will use NBA-MMS UWB ranging as the default example. The corresponding explanations are also applicable to other measurement applications such as ranging, sensing, and positioning. Other ranging methods include, but are not limited to, non-NBA-MMS ranging (without NBA or MMS ranging) and MMS ranging (without NBA ranging but including MMS ranging).

[0171] Figure 8 is a flowchart of the communication method for UWB according to an embodiment of the present application. The method shown in Figure 8 may be applicable to scenarios such as ranging, sensing, positioning, and communication, for example, scenarios such as NBA-MMS based ranging, NBA-MMS based sensing, and NBA-MMS based positioning. As shown in Figure 8, the method includes the following steps:

[0172] 801: The sender generates the first message.

[0173] The transmitting end may be a UWB device that supports the UWB standard. The transmitting end may be an AP or a station. The transmitting end may be an FFD or an RFD. The transmitting end may be a ranging, sensing, positioning, or communication initiator, i.e., a ranging initiator, sensing initiator, positioning initiator, or communication initiator; or a ranging, sensing, positioning, or communication responder, i.e., a ranging responder, sensing responder, positioning responder, or communication responder; or a third-party device (sometimes called a controller device), i.e., not a ranging, sensing, positioning, or communication initiator or responder. For a relevant description of the transmitting end below, see Step 801.

[0174] The first message contains instruction information, which indicates that a FC should be constructed based on a first field in the first message, where the first field indicates the type of the first message. The FC constructed based on the first field in the first message may be used to construct a nonce used to encrypt or authenticate the first message. The first message may be a message in compressed PSDU format. For example, the first message may be a control message in the NBA-MMS UWB measurement process, e.g., an ADV-POLL message, ADV-RESP message, ADV-CONF message, SOR message, POLL message, response message, or report message (sometimes called a Report message). In this application, NBA-MMS UWB measurement includes at least one of NBA-MMS UWB ranging, NBA-MMS UWB sensing, NBA-MMS UWB positioning, and the like. The first field may be a message ID field. For example, the first message may be a SOR message as shown in Table 2, where the first field is a message ID field. In another example, the first message is the reporting message shown in Table 4, and the first field is the message ID field. A POLL message may alternatively be called a query message. The name of a POLL message is not limited in this application. Indication information may occupy one or more bits in the first message. If the value represented by one or more bits is 1, the indication information indicates to construct the FC based on the first field in the first message; or, if the value represented by one or more bits is 0, the indication information indicates to construct the FC in another way, for example, based on a slot index, round index, and block index corresponding to the first message, or to construct the FC based on the PN field in the first message.Alternatively, if the value of the instruction information (i.e., the value represented by one or more bits occupied by the instruction information) is 0, the instruction information indicates that the FC is constructed based on the first field in the first message; or, if the value of the instruction information is 1, the instruction information indicates that the FC is constructed in a different manner.

[0175] The number of bits occupied by the instruction information may be less than 4, i.e., less than the number of bits occupied by the PN field (see Tables 2 and 3). For example, the instruction information may occupy 1 or 2 bits. Therefore, the signaling overhead of a solution in which the first message includes instruction information is smaller compared to existing solutions in which the PN field is explicitly carried. The possible formats of the first message are described below by using an example in which the first message is a POLL message. Table 6 shows an example of a PSDU format for a POLL message. Table 6 [Table 7]

[0176] In Table 6, the Message ID field, Security Enablement field, Address field, Secure Payload field, and MIC field are the same as the fields in Table 2, and further details are not provided here. The Block Index field indicates the distance measurement block corresponding to the POLL message, and the Round Index field indicates the distance measurement round corresponding to the POLL message. In this specification, 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 a Block Index field (occupying 2 bits). Table 6 may or may not include a Round Index field (occupying 2 bits). The Presence Control field contains indication information. The Presence Control field may occupy 1 bit, 3 bits, or 1 byte. The location and size of the Presence Control field are not limited in this application, nor is the name of the Presence Control field. In this specification, the size of a field is the number of bits occupied by the field. Furthermore, the presence control field may be a new field or may be included in an existing field. It should be understood that Table 6 merely shows an example of the PSDU format for a POLL message, and the position and size of each field in Table 6 are not limited. Tables 7-1, 7-2, and 7-3 show three examples of presence control fields. Table 7-1 [Table 8]

[0177] See Table 7-1. The presence control field occupies 1 bit. The presence control field indicates whether to construct a Full Form Conversion (FC) based on a first field in the first message. For example, if the value of the presence control field is 1, the presence control field indicates to construct a Full Form Conversion (FC) based on a first field in the first message; or, if the value of the presence control field is 0, the presence control field indicates to construct a Full Form Conversion (FC) based on a slot index, round index, or block index corresponding to the first message, or to construct a Full Form Conversion (FC) based on a PN field in the first message. Table 7-2 [Table 9]

[0178] Refer to Table 7-2. The presence control fields include the block index presence field (occupying 1 bit), the round index presence field (occupying 1 bit), and the imSI enable field (occupying 1 bit). Note 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. Note that the first message shown in Table 6 may not include a block index field, and / or the first message shown in Table 6 may not include a round index field. If the first message does not include a block index field, the value of the block index field corresponding to the first message defaults to 0. If the first message does not include a round index field, the value of the round index field corresponding to the first message defaults to 0. The imSI Activate field indicates whether to construct a FC based on a first field in the first message. For example, if the value of the imSI Activate field is 1, the imSI Activate field indicates to construct a FC based on a first field in the first message; or, if the value of the imSI Activate field is 0, the imSI Activate field indicates to construct a FC based on a slot index, round index, or block index corresponding to the first message, or to construct a FC based on a PN field in the first message. The imSI Activate field in Table 7-2 may be considered indicator information. Table 7-3 [Table 10]

[0179] In Table 7-3, the meanings of the block index presence field (occupying 1 bit), round index presence field (occupying 1 bit), and imSI enable field (occupying 1 bit) are the same as in Table 7-2, and further details are not provided here. The RFU (reserved for future use, reserved for future use, equivalent to reserved) field is a reserved field, i.e., a field reserved for future use, and occupies 5 bits. The presence control fields shown in Table 7-3 occupy 1 byte. The imSI enable field in Table 7-3 may be considered indicator information. It should be noted that the size and position of each field in Table 7-3 are not limited.

[0180] 802: The sender sends the first message.

[0181] Accordingly, the receiving end receives the first message. The receiving end may be a UWB device that supports the UWP standard. The receiving end may be an AP or a station. The receiving end may be an FFD or an RFD. The receiving end may be a ranging, sensing, positioning, or communication initiator, i.e., a ranging initiator, sensing initiator, positioning initiator, or communication initiator; or a ranging, sensing, positioning, or communication responder, i.e., a ranging responder, sensing responder, positioning responder, or communication responder; or a third-party device (sometimes called a controller device), i.e., not a ranging, sensing, positioning, or communication initiator or responder. For example, the transmitting end is both an initiator and a controller, and the receiving end is a responder. In another example, the transmitting end is the controller and the receiving end is the responder. For a relevant explanation of the receiving end below, see step 802.

[0182] In a possible implementation, the transmitting end further performs the following actions: transmits a second message, which includes a second field indicating a timeout for receiving the SOR message. Correspondingly, the receiving end receives the second message. The receiving end can stop monitoring for the SOR message after the timeout indicated by the second field for receiving the SOR message, thereby avoiding the increased energy consumption caused by waiting for a long time to monitor for the SOR message. The second message further includes a field indicating whether the second field exists. The second message is a message transmitted by the transmitting end before the transmitting end transmits the SOR message (e.g., the first message). The second message may be an ADV-CONF message or another message; this is not limited in this application. Herein, an example where the second message is an ADV-CONF message is used for illustrative purposes. Table 8 shows an example of the PSDU format of an ADV-CONF message including the second field. Table 8 [Table 11]

[0183] In Table 8, the SOR transmission timeout field (i.e., the second field) indicates the timeout for 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 may be ranging scheduling time unit (RSTU) or slot. The unit of the SOR transmission timeout is not limited in this application. For example, if 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; or, if 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 SOR message management field is a field used to carry and manage the SOR message list. The SOR Message Management (SMM) presence field (hereinafter referred to as the SMM presence field) indicates whether the second message contains the SOR Message Management field. For example, if the value of the SMM presence field is 1, the second message contains the SOR Message Management field; or, if the value of the SMM presence field is 0, the second message does not contain the SOR Message Management field. The RFU field is a reserved field, i.e., a field reserved for future use, and may occupy 6 bits. It should be understood that Table 8 merely shows an example of a PSDU in the second message, and the size and position of each field in the second message are not limited.

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

[0185] A possible implementation of step 803 is as follows: Construct the FC based on the instruction information in the first message, the first field, the measurement round identifier corresponding to the first message, and the measurement block identifier corresponding to the first message. For example, the receiving end obtains the FC by concatenating the first field, the measurement round identifier (e.g., round index) corresponding to the first message, and the measurement block identifier (e.g., block index) corresponding to the first message. In this example, the method for constructing the FC is: FC = Message ID || Round Index || Block Index Here, "||" indicates concatenation. After constructing the FC, the receiving end can construct a 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 examples of nonces. Table 9-1 [Table 12]

[0186] In Table 9-1, the message ID field, the round index field, and the block index field form a FC. It should be noted that the methods for constructing an FC are not limited in this application, and the methods for constructing an FC provided in this specification are merely examples.

[0187] In another example, an alternative method for building FC is, FC = Block Index || Round Index || Message ID This is also acceptable. In other words, the order of connections used in FC construction is not limited in this application.

[0188] In another example, an alternative method for building FC is, FC=prePN||Block Index||Round Index||Message ID It may also be the case that, in another example, the method for constructing FC is alternatively, FC=prePN||Message ID This may also be the case. prePN (pre-determined Packet Number) is a value agreed upon and stored in advance by the receiving and transmitting ends, and represents a value that can be used to construct the FC. The value of prePN may be updated according to specific rules. For example, after a certain number of time blocks, the value of prePN is incremented by 1. The rules for updating the value of prePN are not limited in this application. Furthermore, other values ​​that may be involved in FC construction are not limited in this application, and prePN is merely an example. Any case in which the FC is constructed based on the message ID falls within the scope of protection of this application.

[0189] Another possible implementation of step 803 is as follows: construct the FC based on the instruction information in the first message, the first field, the order information in the message list of the list element corresponding to the first message in the message list, and the measurement block identifier corresponding to the first message. In this application, if the first message is not a SOR message, the order information in the message list of the list element corresponding to the first message in the message list may be: the order information in the message list of the list element corresponding to the SOR message corresponding to the first message in the message list. The first message and the SOR message corresponding to the first message correspond to the same device. The instruction information indicates that the FC is constructed based on the first field, the order information in the message list of the list element corresponding to the first message in the message list. See the relevant contents of Table 11-4 below. The contents related to the order information in the message list of the list element corresponding to the first message in the message list are described in detail later and are not described here. Different list elements in the message list correspond to different devices. Each list element in the message list contains a device identifier, e.g., a device address. The device address is the address of the device. The message list may be contained in a third message sent before the first message is sent. For example, the third message is an ADV-CONF message in the NBA-MMS UWB measurement process. The third message may, alternatively, be another message. This is not limited to the present application. An example of a possible implementation is as follows: The receiving end obtains the FC by concatenating the first field, the sequence information (e.g., the CODA value below), and the measurement block identifier (e.g., the block index) corresponding to the first message. In this example, the method for constructing the FC is: FC = Message ID || CODA value || Block index The "||" indicates concatenation. The CODA value is a value that indicates the order within the message list of the list element corresponding to the first message in the message list, for example, #1, #2, and #3. After constructing the FC, the receiving end can construct a 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. Table 9-2 shows examples of nonces. Table 9-2 [Table 13]

[0190] In Table 9-2, the Message ID field, the CODA value field, and the Block Index field form a Block Cluster (FC).

[0191] In another example, alternative methods for building FC include: FC = Block Index || CODA Value || Message ID This is also acceptable. In other words, the linking sequence used to construct the FC is not limited in this application.

[0192] In another example, alternative methods for building FC include: FC=prePN||Block Index||CODA Value||Message ID Alternatively, another method for building an FC is: FC = prePN || CODA value This may also be the case. prePN is a value that has been agreed upon and stored in advance by the receiving and transmitting ends and that can be used to construct the FC. The value of prePN may be updated according to certain rules. For example, after a certain number of time blocks, the value of prePN is increased by 1. The rules for updating the value of prePN are not limited in this application. Also, other values ​​that can be involved in FC construction are not limited in this application, and prePN is merely an example. Any case in which the FC is constructed based on the CODA value falls within the scope of protection of this application.

[0193] It should be noted that the format of the nonce is not limited in this application, and Table 9-2 is merely an example.

[0194] The method procedure in Figure 8 may be understood as constructing a Field Control (FC) corresponding to a control message based on the first field (message ID) of the control message (i.e., the first message), the measurement round identifier corresponding to the control message, and the measurement block identifier corresponding to the control message. The method procedure in Figure 8 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 round (e.g., ranging round) have different message IDs. In other words, any two control messages have different message IDs. Therefore, different FCs can be constructed for different control messages based on the method procedure in Figure 8. Figure 9 is a diagram of the NBA-MMS UWB ranging process according to an embodiment of the present application. As shown in Figure 9, the message ID of a POLL message is 0x00, the message ID of a response message is 0x01, the message ID of a reporting message sent by a Responder is 0x02, and the message ID of a reporting message sent by an Initiator is 0x03. Figure 9 shows that different control messages within a ranging round have different message IDs. When the method procedure in Figure 8 is applied to an NBA-MMS UWB ranging scenario, the method procedure in Figure 8 may be understood as: constructing the required FC based on the unique transmission sequence of each control message in the NBA-MMS UWB ranging process, where the message ID of each control message may be considered as the unique transmission sequence of each control message.

[0195] In this embodiment of the present application, the instruction information indicates that the FC is constructed based on a first field in the first message. When the instruction information is included in the first message, the signaling overhead is small because the instruction information occupies fewer bits than the PN field.

[0196] Figure 10 illustrates the steps of an exchange of another communication method for UWB according to an embodiment of the present application. The method shown in Figure 10 may be applicable to scenarios such as ranging, sensing, positioning, and communication, e.g., NBA-MMS based ranging, NBA-MMS based sensing, and NBA-MMS based positioning. Compared with the method steps in Figure 8, the method steps in Figure 10 do not require the first message to carry instruction information, and the receiving end constructs the FC by default based on a first field in the first message. As shown in Figure 10, the method includes the following steps:

[0197] 1001: The transmitting end generates the first message.

[0198] For step 1001, see step 801. Compared to the first message in the method procedure of Figure 8, the first message in the method procedure of Figure 10 does not contain instruction information. The first message may be a message in compressed PSDU format. For example, the first message may be 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 (sometimes called a Report message). In this application, NBA-MMS UWB measurement includes at least one of NBA-MMS UWB ranging, NBA-MMS UWB sensing, NBA-MMS UWB positioning, and the like. The first message includes a first field. The first field may be a message ID field. For example, the first message is a SOR message shown in Table 2, and the first field is a message ID field. In another example, the first message is the report message shown in Table 4, and the first field is the message ID field.

[0199] 1002: The transmitting end sends the first message.

[0200] Accordingly, the receiving end receives the first message. For step 1002, please refer to step 802.

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

[0202] A possible implementation of step 1003 is to construct a FC based on a first field, a measurement round identifier corresponding to the first message, and a measurement block identifier corresponding to the first message. For example, the receiving end obtains the FC by concatenating the first field, the measurement round identifier (e.g., round index) corresponding to the first message, and the measurement block identifier (e.g., block index) corresponding to the first message. After constructing the FC, the receiving end can construct a nonce corresponding to the first message based on the FC. See Table 9. It will be understood that an FC constructed based on a first field in the first message can be used to construct a nonce used to encrypt or authenticate the first message.

[0203] Another possible implementation of step 1003 is to construct the FC based on the first field, the order information in the message list of the list element corresponding to the first message in the message list, and the measurement block identifier corresponding to the first message. The details related to the order information in the message list of the list element corresponding to the first message in the message list are explained in detail later and are not explained here. For example, the receiving end obtains the FC by concatenating the first field, the order information (e.g., the CODA value below), and the measurement block identifier (e.g., the block index) corresponding to the first message. In this example, the method for constructing the FC is: FC = Message ID || CODA value || Block index That is the case.

[0204] The main principles of the method procedure in Figure 10 are the same as those of the method procedure in Figure 8, and the details will not be explained again here.

[0205] In this embodiment of the present application, the FC is constructed based on a first field in a first message. The first message does not require the carrying of a PN field, resulting in low signaling overhead.

[0206] Figure 11 illustrates the steps of an exchange of another communication method for UWB according to an embodiment of the present application. The method shown in Figure 11 may be applicable to scenarios such as ranging, sensing, positioning, and communication, e.g., NBA-MMS based ranging, NBA-MMS based sensing, and NBA-MMS based positioning. Compared with the method steps in Figure 8, in the method steps in Figure 11, the first message does not contain instructional information, and a fourth message sent before the first message contains instructional information. As shown in Figure 11, the method includes the following steps:

[0207] 1101: The sender sends a fourth message.

[0208] Accordingly, the receiving end receives a fourth message. The fourth message contains instruction information, which indicates that the FC should be constructed based on a first field in the first message, and the first field indicates the type of the first message. The instruction information may occupy one or more bits. For example, if the value represented by one or more bits occupied by the instruction information is 1, the instruction information indicates that the FC should be constructed based on a first field in the first message; or, if the value represented by one or more bits is 0, the instruction information indicates that the FC should be constructed in another way, for example, based on the PN field in the first message. The fourth message may contain a presence control field shown in any one of Table 7-1, Table 7-2, or Table 7-3, and the presence control field contains instruction information. This is not described again here.

[0209] The first message may be any message sent by the transmitting or receiving end after the transmitting end has sent the fourth message. In possible implementations, for any control messages sent by the transmitting and receiving ends after the transmitting end has sent the fourth message, the FC is constructed based on the first field in the control message. For example, the fourth message may be one of the ADV-POLL message, ADV-RESP message, ADV-CONF message, and SOR message, and the first message may be one of the POLL message, response message, or reporting message. In another example, the fourth message may be an ADV-POLL message, and the first message may be one of the ADV-RESP message, ADV-CONF message, and SOR message. The fourth message may be any message sent by the transmitting or receiving end before the transmitting end has sent the first message. This is not limited to the present application. It will be understood that the instruction information indicates how to construct the FC corresponding to a control message based on a first field in each control message (e.g., the first message) sent by the transmitting or receiving end after the transmitting end has sent the fourth message. In other words, the fourth message can indicate how to construct the FC corresponding to each control message sent by the transmitting or receiving end after the transmitting end has sent the fourth message. It will be understood that each message sent by the transmitting or receiving end after the transmitting end has sent the fourth message does not need to carry the instruction information. The bits occupied by the instruction information may be fewer than the bits occupied by the slot index field (e.g., the field indicating the slot index in a SOR message). Compared to the slot index field carried in the fourth message, the instruction information carried in the fourth message occupies fewer bits and has less signaling overhead.Furthermore, the instruction information is included in the fourth message, and each message sent by the transmitting end after the transmitting end has sent the fourth message does not need to carry the instruction information, thereby further reducing signaling overhead.

[0210] 1102: The sender sends the first message.

[0211] Accordingly, the receiving end receives a first message. The first message includes a first field, for example, a message ID field.

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

[0213] The FC constructed in step 1103 can be used to construct a nonce used to encrypt or authenticate the first message. A possible implementation of step 1103 is that the receiving end constructs the FC based on the instruction information in the fourth message, the first field, the measurement round 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 round 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 instruction information. After constructing the FC, the receiving end can construct a nonce corresponding to the first message based on the FC.

[0214] The main principles of the method procedure in Figure 11 are the same as those of the method procedure in Figure 8, and the details will not be explained again here.

[0215] In this embodiment of the present application, the instruction information in the fourth message indicates that the FC is constructed based on the first field in the first message. Compared to the slot index field carried in the fourth message or another message, the instruction information in the fourth message occupies fewer bits and has lower signaling overhead. Furthermore, after the transmitting end sends the fourth message, each message sent by the transmitting end does not need to carry the instruction information, and as a result, the signaling overhead can be further reduced.

[0216] Figure 12 illustrates the steps of an exchange of another communication method for UWB according to an embodiment of the present application. The method shown in Figure 12 may be applicable to scenarios such as ranging, sensing, positioning, and communication, e.g., NBA-MMS based ranging, NBA-MMS based sensing, and NBA-MMS based positioning. Compared with the method steps in Figure 8, the method steps in Figure 12 show that instruction information in the first message constructs an FC based on the order information in the message list of list elements corresponding to the first message in the message list. As shown in Figure 12, the method includes the following steps:

[0217] 1201: The sender sends a third message.

[0218] Accordingly, the receiving end receives the third message. The transmitting end sending the third message may also be done by the transmitting end broadcasting the third message. The third message may be an ADV-CONF message or another message containing a SOR message list.

[0219] 1202: The sender generates the first message.

[0220] The first message contains instructional information, which indicates that the list element corresponding to the first message in the message list is used to construct a FC based on the order information 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 a message may be understood as the receiving end that receives the message. For example, the first message is a unicast message, the sender sends the first message to the receiving end, and the receiving end is the receiving end of the first message. The receiving end can use a list element in the message list that contains the receiving end's device identifier as the list element corresponding to the message to be received and / or sent by the receiving end in the message list (e.g., the first message). Different list elements in the message list correspond to different devices. In other words, different list elements in the message list correspond to different device identifiers. Each list element in the message list may contain a device identifier. The message list may be included in a third message that is sent before the first message is sent. For example, the third message is the ADV-CONF message in the NBA-MMS UWB measurement process. The first message may be a message in compressed PSDU format. For example, the first message may be one of the following: a SOR message, a POLL message, a response message, or a reporting message.

[0221] The sequential information within a message list for a list element corresponding to a first message in the message list may be the sequential information within a list element in the message list that contains the device identifier (e.g., device address) of the receiving end of the first message. The receiving end may use the list element in the message list that contains the receiving end's device identifier as the list element corresponding to the message to be received and / or sent by the receiving end in the message list (e.g., the first message). The format of the device identifier is not limited in this application, and the device address is merely an example.

[0222] The following describes an example of the order information within a message list for the list element corresponding to the first message in the message list, referring to the attached diagram. A one-to-many NBA-MMS UWB ranging process is formed by multiple one-to-one NBA-MMS UWB ranging processes based on the order of execution time. In other words, all one-to-one NBA-MMS UWB ranging processes have the same initiator. A typical one-to-many NBA-MMS UWB ranging process is shown in Figure 4A. Figure 13 shows the initialization process for pre-configuring a one-to-many NBA-MMS UWB ranging process. As shown in Figure 13, in the case of one-to-many NBA-MMS UWB ranging, the initiator must first broadcast an ADV-POLL message to notify all responders that require NBA-MMS UWB ranging to be performed, and each responder sends its own ADV-RESP message to the initiator using a competition-based access method. After successfully receiving the ADV-RESP messages using the competition-based access method, the initiator broadcasts an ADV-CONF message to all responders. In Figure 13, SOR0 represents the SOR message sent by the initiator to responder 0. SOR1 represents the SOR message sent by the initiator to responder 1. SOR2 represents the SOR message sent by the initiator to responder 2. The time offset for SOR0 (the time offset until the SOR0 message is sent) indicates the transmission time of SOR0. The time offset for SOR1 (the time offset until the SOR1 message is sent) indicates the transmission time of SOR1. The time offset for SOR2 (the time offset until the SOR2 message is sent) indicates the transmission time of SOR2. For the responder's MMS UWB measurement process, please refer to the distance measurement process shown in Figure 9. The time offset for POLL0 (the time offset until the POLL0 message is sent) indicates the transmission time of the POLL message in the MMS UWB measurement process of responder 0. The time offset for POLL1 (the time offset until the POLL1 message is sent) indicates the transmission time of the POLL message in the MMS UWB measurement process of responder 1. The time offset for POLL2 (the time offset until the POLL2 message is sent) indicates the transmission time of the POLL message in the MMS UWB measurement process of responder 2.

[0223] The ADV-CONF message carries a SOR message list containing multiple SOR messages. The SOR message list is an example of a message list. Each list element in the SOR message list contains the device address and transmission time (time offset relative to SOR#X) of the corresponding SOR message. In other words, each responder can determine whether its ADV-RESP message was successfully received by the initiator by querying whether its device address is included in the SOR message list, and thus whether the responder will participate in the subsequent NBA-MMS UWB ranging process. Only devices whose ADV-RESP message was successfully received by the initiator can start the subsequent NBA-MMS UWB ranging process. The chronological order of the responder device address appearance (CODA) in the message list of an ADV-CONF message may be used as sequential information within the message list for list elements corresponding to control messages (e.g., the first message) that the responder should receive and / or send in the message list. For example, after receiving an ADV-CONF message, the responder queries whether its device address is included in the SOR message list of the ADV-CONF message; if the responder's device address is included in the SOR message list, it uses the order of the device address in the SOR message list as sequential information within the message list for list elements corresponding to control messages (e.g., the first message) that the responder should send and / or receive in the message list.

[0224] Examples of the PSDU format for ADV-CONF messages, including the SOR message list, are shown in Tables 10 through 14 below. The position and size of each field in Tables 10 through 14 are not limited. Table 10 [Table 14]

[0225] Table 10 shows a diagram of the PSDU format for ADV-CONF messages. The meaning of the fields in Table 10 is the same as the meaning of the fields in Tables 1 and 2, and the details will not be explained again here. The Content field is the field that contains the SOR message list, as shown in Table 11. Table 11 shows a diagram of the SOR message list format. Table 11 [Table 15]

[0226] The SOR Message Management (SMM) presence field is used to indicate whether a SOR Message Management field exists. For example, a value of 0 in the SMM presence field indicates that the SOR message list does not contain a SOR Message Management field; or a value of 1 in the SMM presence field indicates that the SOR message list contains a 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. Possible formats for the SOR Message Management field are shown in Table 12. Table 12 [Table 16]

[0227] The Address Type field indicates the type of device address contained in each list element within the SOR message list. For example, a value of 0 in the Address Type field indicates that the device is using a short address (2 bytes); or a value of 1 indicates that the device is using an extended address / long address (8 bytes). The SOR Message List Length field indicates the length of the SOR message list. The SOR Message List field is a SOR message list field. The SOR Message List field contains multiple SOR message scheduling list elements (sometimes abbreviated as list elements). The SOR Message List field is shown in Table 13 below. Table 13 [Table 17]

[0228] Each list element in Table 13 corresponds to a different device. For example, SOR message scheduling list element #0 in Table 13 corresponds to device #0. The example in Table 13 shows that devices #0 through #2 appear in the SOR message list in the order 0, 1, and 2. In other words, the CODA values ​​for the devices are 0, 1, and 2. Table 14 shows a diagram illustrating an exemplary format of the SOR message list elements. Table 14 [Table 18]

[0229] Table 14 shows that each SOR message list element includes a time offset field relative to the SOR and a device address field. The device address in the device address field is the device address of the device, and the time offset field relative to the SOR field indicates the transmission time of the SOR message that the device should receive. For example, after receiving an ADV-CONF message, the receiving end queries whether its 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 relative to SOR" field in the list element containing the device address indicates the transmission time of the SOR message that the receiving end should receive.

[0230] It should be noted that the message carrying a SOR message list containing multiple SOR messages is not limited in this application and may be a different message. The ADV-CONF message is merely an example.

[0231] The first message may be a message in the compressed PSDU format. For example, the first message is a SOR message. The indication information in the first message may occupy one or more bits. For example, if the value represented by one or more bits occupied by the indication information is 1, the indication information indicates constructing the FC based on the order information in the message list for the list element corresponding to the first message in the message list; or if the value represented by one or more bits is 0, the indication information indicates constructing the FC in another way, for example, based on the slot index, round index, and block index carried in the first message. If the first message does not carry the slot index, round index, or block index, the index is 0 by default. Alternatively, if the value of the indication information (i.e., the value represented by one or more bits occupied by the indication information) is 0, the indication information instructs constructing the FC based on the order information in the message list for the list element corresponding to the first message in the message list; or if the value of the indication information is 1, the indication information indicates constructing the FC in another way. Hereinafter, the possible format of the first message will be described by using an example where the first message is a SOR message. Table 15 shows an example of the PSDU format of the SOR message. Table 15

Table 19

[0232] In Table 15, the message ID field, security activation field, address field, secure payload field, and MIC field are the same as the fields in Table 3 and will not be described again here. Table 15 may include a block index field (occupying 2 bits), or may not include a block index field. Table 15 may include a round index field (occupying 2 bits), or may not include a round index field. The presence control field contains indication information. The presence control field may occupy 1 bit, 3 bits, or 1 byte. The position and size of the presence control field are not limited in this application, nor is the name of the presence control field limited. Also, the presence control field may be a new field or may be included in an existing field. It should be understood that Table 15 merely shows 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, Tables 16-2, Tables 16-3, and Tables 16-4 show four examples of the presence control field. Table 16-1 [Table 20]

[0233] See Table 16-1. The presence control field occupies 1 bit. The presence control field indicates whether to construct a FC based on the order information in the message list for the list element corresponding to the first message in the message list. For example, if the value of the presence control field is 1, the presence control field indicates that the FC will be constructed based on the order information in the message list for the list element corresponding to the first message in the message list; or, if the value of the presence control field is 0, the presence control field indicates that the FC will be constructed based on the slot index, round index, and block index carried in the first message. Table 16-2 [Table 21]

[0234] Refer to Table 16-2. The presence control fields include the block index presence field (occupying 1 bit), the round index presence field (occupying 1 bit), and the imRI enable field (occupying 1 bit). Note 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. If the first message does not contain a block index field, the value of the block index field corresponding to the first message defaults to 0. If the first message does not contain a round index field, the value of the round index field corresponding to the first message defaults to 0. The imRI Activate field indicates whether to construct a FC based on the order information within the message list of the list elements corresponding to the first message in the message list. For example, if the value of the imRI Activate field is 1, the imRI Activate field indicates that the FC will be constructed based on the first field in the first message; or, if the value of the imRI Activate field is 0, the imRI Activate field indicates that the FC will be constructed based on the slot index, round index, and block index corresponding to the first message. The imRI Activate field in Table 16-2 may be considered indicator information. Table 16-3 [Table 22]

[0235] In Table 16-3, the meanings of the block index presence field (occupying 1 bit), the round index presence field (occupying 1 bit), and the imRI enable field (occupying 1 bit) are the same as in Table 16-2, and further details are not provided here. The RFU field is a reserved field, i.e., a field reserved for future use, and occupies 5 bits. The presence control fields shown in Table 16-3 occupy 1 byte. The imRI enable field in Table 16-3 may be considered indicator information. It should be noted that the size and position of each field in Table 16-3 are not limited. Table 16-4 [Table 23]

[0236] In Table 16-4, the meanings of the Block Index Presence field (occupying 1 bit), the Round Index Presence field (occupying 1 bit), and the imRI Enable field (occupying 1 bit) are the same as in Table 16-2, and further details are not provided here. The imSI Enable field (occupying 1 bit) indicates whether to construct a Full Form Constraint (FC) based on a first field in the first message. For example, if the value of the imSI Enable field is 1, the imSI Enable field indicates that the FC will be constructed based on a first field in the first message; or, if the value of the imSI Enable field is 0, the imSI Enable field indicates that the FC will be constructed based on a slot index, round index, or block index corresponding to the first message, or based on a PN field in the first message. The imRI Enable field and the imSI Enable field in Table 16-4 may be considered together as instructional information. Alternatively, the instructional information includes the imRI Enable field and the imSI Enable field in Table 16-4. For example, if the imRI Activation field indicates that the FC is constructed based on the order information within the message list of the list element corresponding to the first message in the message list, and imSI Activation indicates that the FC is constructed based on the first field in the first message, then the instruction information indicates that the FC is constructed based on the first field in the first message and the order information within the message list of the list element corresponding to the first message in the message list. It should be noted that the size and position of each field in Table 16-4 are not limited.

[0237] 1203: The sender sends the first message.

[0238] Accordingly, the receiving end receives the first message.

[0239] In a possible implementation, the transmitting end further performs the following action: sending a second message, the second message including a second field indicating a timeout for receiving the SOR message. Accordingly, the receiving end receives the second message. The receiving end can stop monitoring for the SOR message after the timeout indicated by the second field for receiving the SOR message, thereby avoiding the increased energy consumption caused by waiting for a long time to monitor for the SOR message. The second message further includes a field indicating whether the second field is present. The second message is a message sent by the transmitting end before the transmitting end sends the SOR message (e.g., the first message). The second message may be an ADV-CONF message or another message; this is not limited to the present application.

[0240] 1204: The receiving end obtains the order information within the message list for the third message of the list element corresponding to the first message in the message list.

[0241] In possible implementations, after receiving a third message, the receiving end queries whether its 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, it uses the sequence information of the device address in the message list (e.g., the CODA value) as the sequence information in the message list for the list element corresponding to the receiving end's message to be sent and / or received (including the first message). The sequence information of the device address in the message list may also be the order of the list elements containing the device address in the message list. The receiving end's message to be sent and / or received may include a SOR message, a POLL message, a reply message, or a report message. The receiving end can store the sequence information of its device address in the message list and use that sequence information as the sequence information in the message list for the list element corresponding to the receiving end's message to be sent and / or received (including the first message). After receiving the first message, the receiving end can retrieve the sequence information stored on the receiving end and use this sequence information as the sequence information within the message list for the list element corresponding to the first message in the message list. The receiving end retrieving the sequence information within the message list for the list element corresponding to the first message in the message list may be understood as the receiving end retrieving the sequence information currently stored by the receiving end. After the receiving end has stored the sequence information for its device address in the message list, if the receiving end receives a new third message (a new ADV-CONF message), the receiving end can update the stored sequence information.

[0242] 1205: The receiving end constructs the FC based on the instruction information in the first message and the order information in the message list of the list element corresponding to the first message in the message list.

[0243] A possible implementation of step 1205 is to construct the FC based on the instruction information in the first message, the measurement slot identifier corresponding to the first message, the order 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 order information, and the measurement block identifier (e.g., block index) corresponding to the first message to obtain the FC. In this example, the method of constructing the FC is FC = slot index || CODA value || block index where "||" indicates the concatenation process. The CODA value (i.e., the order information) may be a value indicating the order of the list element corresponding to the first message in the message list, such as #1, #2, and #3. After constructing the FC, the receiving end can construct the nonce based on the FC. The nonce is used for encrypting or authenticating the first message. Tables 17 and 18 show examples of two types of nonces. Table 17

Table 24

[0244] The CODA value field of Table 17 contains the order information. For the meanings of the other fields in Table 17, refer to the meanings of the fields in Table 5. The slot index field, the CODA value field, and the block index field form the FC. Table 18

Table 25

[0245] The CODA value field of Table 18 contains the order information. For the meanings of the other fields in Table 18, refer to the meanings of the fields in Table 3.

[0246] The method procedure in Figure 12 may be understood as constructing an FC corresponding to a control message based on a measurement slot identifier corresponding to a control message (i.e., the first message), the sequential information in the message list of the list elements corresponding to the control message in the message list, and the measurement block identifier corresponding to the control message. The sequential information in the message list of the list elements corresponding to the control message in each subprocedure in a one-to-many NBA-MMS UWB ranging process (i.e., a one-to-one NBA-MMS UWB ranging process) reflects the execution order of each subprocedure in a one-to-many NBA-MMS UWB ranging process. Please refer to Figure 13. The one-to-one MMS UWB ranging process in which responder 0 participates precedes the one-to-one MMS UWB ranging process in which responder 1 participates, and the one-to-one MMS UWB ranging process in which responder 1 participates precedes the MMS UWB ranging process in which responder 2 participates. In the message list, the order information for the list element corresponding to a control message (such as a POLL message, response message, and reporting message) in a one-to-one MMS UWB ranging process in which responder 0 participates is #0. In the message list, the order information in the message list for the list element corresponding to the control message in the one-to-one MMS UWB ranging process in which responder 1 participates is #1. In the message list, the order information for the list element corresponding to the control message in the one-to-one MMS UWB ranging process in which responder 2 participates is #2. Therefore, the method procedure in Figure 12 may be alternatively understood as constructing the FC based on the execution sequence of each subprocedure in a one-to-many NBA-MMS UWB ranging process.

[0247] In this embodiment of the present application, the FC is constructed based on the order information in the message list of the list elements corresponding to the first message in the message list, thereby avoiding the explicit transport of round indices and reducing signaling overhead.

[0248] Figure 14 illustrates the procedure of an exchange of another communication method for UWB according to an embodiment of the present application. The method shown in Figure 14 may be applicable to scenarios such as ranging, sensing, positioning, and communication, e.g., NBA-MMS based ranging, NBA-MMS based sensing, and NBA-MMS based positioning. Compared with the method procedure in Figure 12, in the method procedure in Figure 14, the first message does not contain instruction information, and the receiving end constructs the FC by default based on the order information in the message list of the list elements corresponding to the first message in the message list. As shown in Figure 14, the method includes the following steps:

[0249] 1401: The sender sends a third message.

[0250] Accordingly, the receiving end receives the third message.

[0251] 1402: The sender sends the first message.

[0252] Accordingly, the receiving end receives the first message. The first message may be any one of the following: a SOR message, a POLL message, a response message, or a report message.

[0253] 1403: The receiving end obtains the order information within the message list for the list element corresponding to the first message in the message list.

[0254] For step 1403, please refer to step 1204.

[0255] 1404: The receiving end constructs the FC based on the order information in the message list of the list element corresponding to the first message in the message list.

[0256] A possible implementation of step 1404 is to construct the FC based on the measurement slot identifier corresponding to the first message, the sequence information, and the measurement block identifier corresponding to the first message. For example, the receiving end obtains the FC by concatenating the measurement slot identifier (e.g., slot index) corresponding to the first message, the sequence information, and the measurement block identifier (e.g., block index) corresponding to the first message. After the receiving end receives the third message, the sequence information in the message list is the same for list elements in the message list corresponding to messages sent or received by receiving ends (belonging to the same one-to-one NBA-MMS UWB ranging process). Messages in the same one-to-one NBA-MMS UWB ranging process correspond to different measurement slot identifiers, and therefore the messages correspond to different FCs.

[0257] In this embodiment of the present application, the FC is constructed based on the order information within the message list of the list elements corresponding to the first message in the message list, thereby avoiding the explicit transport of round indices and reducing signaling overhead. Furthermore, since the first message does not contain directional information, the signaling overhead in the solution of Figure 14 is less than that in the solution of Figure 12.

[0258] Figure 15 shows the steps of an exchange of another communication method for UWB according to an embodiment of the present application. Compared with the method steps in Figure 12, in the method steps in Figure 15, the first message does not contain instruction information indicating that the FC is constructed based on the order information in the message list of the list elements corresponding to the first message in the message list, while a fourth message sent before the first message contains instruction information. As shown in Figure 15, the method includes the following steps:

[0259] 1501: The sender sends a fourth message.

[0260] Accordingly, the receiving end receives a fourth message. The fourth message contains instructional information indicating that the receiving end should construct a FC based on the order information in the message list of the list elements corresponding to the first message in the message list. The fourth message may be an ADV-POLL message, an ADV-RESP message, upper-layer signaling, or another message, but is not limited to these. The first message may be any one of a SOR message, a POLL message, a response message, or a reporting message. Alternatively, the instructional information instructs the receiving end to construct a FC based on the order information in the message list of the list elements corresponding to each control message received and / or transmitted by the receiving end in the message list after the transmitting end has sent the third message. The constructed FC is used for encryption and authentication of each control message. The third message may be an ADV-CONF message. After the transmitting end has sent the third message, the control messages received and / or transmitted by the receiving end include SOR messages, POLL messages, response messages, and reporting messages.

[0261] 1502: The sender sends a third message.

[0262] Accordingly, the receiving end receives the third message. For step 1502, please refer to step 1201.

[0263] 1503: The receiving end determines the sequence information of the receiving end's device address in the message list of the third message based on the instruction information in the fourth message.

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

[0265] 1504: The sender sends the first message.

[0266] Accordingly, the receiving end receives the first message.

[0267] 1505: The receiving end obtains the order information within the message list for the third message of the list element corresponding to the first message in the message list.

[0268] A possible implementation of step 1505 is as follows: The receiving end retrieves the sequence information of the device addresses stored in the message list of the third message, and uses that sequence information as the sequence information of the third message in the message list for the list element corresponding to the first message in the message list. In other words, the sequence information stored by the receiving end is the sequence information of the third message in the message list for the list element corresponding to the first message in the message list.

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

[0270] A possible implementation of step 1506 is to construct the FC based on the instruction information in the fourth message, and based on the measurement slot identifier, sequence information, and measurement block identifier corresponding to the first message.

[0271] In this embodiment of the present application, the FC is constructed based on the order information in the message list of the list elements corresponding to the first message in the message list, thereby avoiding the explicit transport of round indices and reducing signaling overhead.

[0272] The structure of a communication device capable of implementing the communication method for UWB provided in the embodiments of this application will be described below with reference to the attached drawings.

[0273] Figure 16 shows the structure of a communication device 1600 according to an embodiment of the present application. The communication device 1600 may perform functions or steps performed by the transmitting end in the embodiments of the method described above, or functions or steps performed by the receiving end in the embodiments of the method described above. The communication device may include a processing module 1610 and a transceiver module 1620. In possible implementations, the device may further include a storage unit. The storage unit may be configured to store instructions (code or program) and / or data. The processing module 1610 and the transceiver module 1620 may be coupled to the storage unit. For example, the processing module 1610 can read instructions (code or program) and / or data from the storage unit and perform the corresponding method. The aforementioned units may be arranged independently or may be partially or fully integrated. For example, the transceiver module 1620 may include a transmitting module and a receiving module. The transmitting module may be a transmitter, and the receiving module may be a receiver. The entity corresponding to the transceiver module 1620 may be a transceiver or a communication interface.

[0274] In some possible implementations, the communication device 1600 can perform the behavior and functions of the transmitting end in the embodiments of the method described above. For example, the communication device 1600 may be the transmitting end, or it may be a component (e.g., a chip or circuit) applied to the transmitting end. For example, the transceiver module 1620 may be configured to perform all the receiving or transmitting operations performed by the transmitting end in the embodiments of Figures 8, 10, 11, 12, 14, and 15. The processing module 1610 is configured to perform all operations performed by the transmitting end other than the receiving and transmitting operations in the embodiments of Figures 8, 10, 11, 12, 14, and 15, for example, step 801 in the embodiment shown in Figure 8.

[0275] In some possible implementations, the communication device 1600 can appropriately implement the behavior and functions of the receiving end in the embodiments of the method described above. For example, the communication device 1600 may be the receiving end, or it may be a component (e.g., a chip or circuit) applied to the receiving end. For example, the transceiver module 1620 may be configured to perform all the receiving or transmitting operations performed by the receiving end in the embodiments of Figures 8, 10, 11, 12, 14, and 15. The processing module 1610 is configured to perform all operations performed by the receiving end other than the receiving and transmitting operations in the embodiments of Figures 8, 10, 11, 12, 14, and 15.

[0276] Figure 17 shows the structure of another communication device 170 according to an embodiment of the present application. The communication device in Figure 17 may be the transmitting terminal or the receiving terminal as described above.

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

[0278] In some embodiments of this application, the processor 1710 and the transceiver 1720 may be configured to perform functions, operations, or similar actions performed by the transmitting end. For example, the transceiver 1720 is configured to perform all receiving or transmitting operations performed by the transmitting end in the embodiments of Figures 8, 10, 11, 12, 14, and 15. For example, the processor 1710 is configured to perform all operations performed by the transmitting end other than the receiving and transmitting operations in the embodiments of Figures 8, 10, 11, 12, 14, and 15.

[0279] In some embodiments of this application, the processor 1710 and the transceiver 1720 may be configured to perform functions, operations, or similar actions performed by the receiving end. For example, the transceiver 1720 is configured to perform all receiving or transmitting operations performed by the receiving end in the embodiments of Figures 8, 10, 11, 12, 14, and 15. For example, the processor 1710 is configured to perform all operations performed by the receiving end other than the receiving and transmitting operations in the embodiments of Figures 8, 10, 11, 12, 14, and 15.

[0280] The transceiver 1720 is configured to communicate with another device / device through a transmission medium. The processor 1710 is configured to receive or transmit data and / or signaling via the transceiver 1720 and to carry out the method in the embodiment of the method described above. The processor 1710 is capable of carrying out the functions of the processing module 1610, and the transceiver 1720 is capable of carrying out the functions of the transceiver module 1620.

[0281] Optionally, the transceiver 1720 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily configured to perform conversions between baseband signals and radio frequency signals and to process radio frequency signals. The antenna is primarily configured to receive and transmit radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, or keyboards, are primarily configured to receive data entered by the user and output data to the user.

[0282] Optionally, the communication device 170 may further include at least one memory 1730 configured to store program instructions and / or data. The memory 1730 is coupled to the processor 1710. The coupling in this embodiment of the present application may be an indirect coupling or communication connection between devices, units, or modules in an electrical, mechanical, or other form, used for information exchange between devices, units, or modules. The processor 1710 is capable of operating in cooperation with the memory 1730. The processor 1710 is capable of executing program instructions stored in the memory 1730. At least one of the at least one memory may be included in the processor.

[0283] The processor 1710 can read software programs in memory 1730, interpret and execute instructions for the software programs, and process data within the software programs. If the data needs to be transmitted wirelessly, the processor 1710 performs baseband processing on the data to be transmitted and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves via the antenna. When data is to be transmitted to a communication device, the radio frequency circuit receives the radio frequency signal via the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1710. The processor 1710 converts the baseband signal into data and processes the data.

[0284] In alternative implementations, the radio frequency circuitry and antennas may be located independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antennas may be located remotely, independently of the communication equipment.

[0285] The specific connecting medium between the transceiver 1720, the processor 1710, and the memory 1730 is not limited to this embodiment of the present application. In this embodiment of the present application, the memory 1730, the processor 1710, and the transceiver 1720 are connected via a bus 1740 in Figure 17. The bus is represented by a thick line in Figure 17. The methods of connection between other components are merely illustrative examples and are not limited to them. Buses may be classified as address buses, data buses, control buses, and similar. For ease of representation, only one thick line is used to represent buses in Figure 17, but this does not mean that there is only one bus or only one type of bus.

[0286] In embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component capable of carrying out or executing the methods, steps, and logic block diagrams disclosed in embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor or similar. The steps of the methods disclosed with reference to embodiments of the present application may be carried out directly by the hardware processor or by using a combination of hardware and software modules within the processor.

[0287] Figure 18 is a diagram illustrating the structure of another communication device 180 according to an embodiment of the present application. As shown in Figure 18, the communication device shown in Figure 18 includes a logic circuit 1801 and an interface 1802. The processing module 1610 in Figure 16 may be implemented via the logic circuit 1801, and the transceiver module 1620 in Figure 16 may be implemented via the interface 1802. The logic circuit 1801 may be a chip, processing circuit, integrated circuit, system-on-chip (SoC) chip, or the like. The interface 1802 may be a communication interface, input / output interface, or the like. In this embodiment of the present application, the logic circuit and the interface may be coupled to each other. The specific method of connection between the logic circuit and the interface is not limited to this embodiment of the present application.

[0288] In some embodiments of this application, logic circuits and interfaces may be configured to perform functions, operations, or similar actions performed by the transmitting end.

[0289] In some embodiments of this application, logic circuits and interfaces may be configured to perform functions, operations, or similar actions performed by the receiving end.

[0290] This application further provides a computer-readable storage medium for storing computer programs or instructions. When the computer programs or instructions are executed on a computer, the computer becomes capable of performing the methods described in the embodiments described above.

[0291] This application further provides a computer program product, which includes instructions or a computer program. When the instructions or computer program are executed on a computer, the method described in the above-described embodiment is performed.

[0292] This application further provides a communication system including a transmitting end and a receiving end.

[0293] This application further provides a chip comprising a communication interface and a processor. The communication interface is configured to receive and transmit signals of the chip. The processor is configured to execute computer program instructions, so that a communication device comprising the chip performs the method of the embodiments described above.

[0294] All or part of the embodiments described above may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When a computer program or instruction is loaded onto a computer and executed, all or part of the procedures or functions in the embodiments of this application are executed. The computer may be a general-purpose computer, a dedicated computer, a computer network, a network device, a user device, or another programmable device. The computer program or instruction may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instruction may be transmitted by wire or wirelessly from one website, computer, server, or data center to another website, computer, server, or data center. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device that integrates one or more available mediums, such as a server or data center. The usable media may be magnetic media, such as floppy disks, hard disks, or magnetic tapes; optical media, such as digital video discs; or semiconductor media, such as solid-state drives. Computer-readable storage media may be volatile or non-volatile storage media, or may include both volatile and non-volatile storage media.

[0295] In the embodiments of this application, unless otherwise stated or unless there is a logical inconsistency, the terminology and / or descriptions in different embodiments are consistent and may be referenced to one another, and the technical features in different embodiments may be combined based on their internal logical relationships to form new embodiments.

Claims

1. A communication method for ultra-wideband (UWB): Steps include: generating instruction information, which indicates constructing a frame count FC based on a first field in a first message, where the first field indicates the type of the first message; and The step of transmitting the aforementioned instruction information; A method that includes this.

2. The method according to claim 1, further: A step of sending a second message, the second message including a second field indicating the timeout of the start of ranging SOR message; A method that includes this.

3. The method according to claim 2, wherein the second message further includes a field indicating whether the second field exists.

4. The method according to claim 1 or 2, wherein the second message is an Advertisement Confirmation ADV-CONF message.

5. In the method according to any one of claims 1 to 4, the step of transmitting the instruction information is: A step of sending the first message, wherein the first message includes the instruction information; Methods that include...

6. A communication method for ultra-wideband (UWB): Steps include: receiving instruction information, which indicates constructing a frame count FC based on a first field in a first message, where the first field indicates the type of the first message; and Steps of constructing the FC based on the aforementioned instruction information; A method that includes this.

7. In the method according to claim 6, the step of constructing the FC based on the instruction information is: Steps to construct the FC based on the instruction information, the first field, the measurement round identifier corresponding to the first message, and the measurement block identifier corresponding to the first message; Methods that include...

8. In the method according to claim 6 or 7, the step of receiving the instruction information is: A step of receiving the first message, wherein the first message includes the instruction information; Methods that include...

9. A method according to any one of claims 1 to 8, wherein the instruction information indicates that a frame count FC is constructed based on a first field in a first message: a method in which the instruction information indicates that the FC is constructed based on the order information in the message list and the first field for a list element in the message list corresponding to the first message in the message list.

10. The method according to claim 9, wherein different list elements in the message list correspond to different devices.

11. The method according to claim 10, wherein each list element in the message list includes a device identifier.

12. The method according to claim 10 or 11, wherein the message list is included in a third message transmitted before the first message is transmitted.

13. The method according to claim 12, wherein the third message is an Advertisement Confirmation ADV-CONF message in a Narrowband Auxiliary Multi-Millisecond Ultra-Wideband NBA-MMS UWB Measurement Process.

14. A method according to any one of claims 1 to 13, wherein the instruction information further indicates whether the first message includes a measurement round identifier.

15. A method according to any one of claims 1 to 4, wherein the instruction information further indicates whether the first message includes the measurement block identifier.

16. A communication method for ultra-wideband (UWB): The step of receiving a first message; and A step of constructing a frame count FC based on a first field in the first message, wherein the first field indicates the type of the first message; A method that includes this.

17. The method according to claim 16, the step of constructing a frame count FC based on a first field in the first message is: Steps of constructing the FC based on the first field, the measurement round identifier corresponding to the first message, and the measurement block identifier corresponding to the first message; Methods that include...

18. The method according to claim 16, the step of constructing a frame count FC based on a first field in the first message is: A step of constructing the FC based on the order information in the message list and the first field for the list element corresponding to the first message in the message list; Methods that include...

19. A method according to any one of claims 1 to 18, wherein the first message is a message in a compressed physical layer service data unit (PSDU) format.

20. The method according to claim 19, wherein the first message is a control message in a narrowband-assisted multi-millisecond ultrawideband NBA-MMS UWB measurement process.

21. The method according to claim 20, wherein the first message is one of a start-of-ranging SOR message, a polling / initiating POLL message, a reporting message, or a response message. A method that includes this.

22. A communication method for ultra-wideband (UWB): A step of generating instruction information, the instruction information indicating that a frame count FC is constructed based on the order information in the message list for the list element corresponding to the first message in the message list; and The step of transmitting the aforementioned instruction information; A method that includes this.

23. A communication method for ultra-wideband (UWB): Steps include: receiving instruction information, the instruction information indicating that a frame count FC is constructed based on the order information in the message list for the list element corresponding to the first message in the message list; and Steps of constructing the FC based on the aforementioned instruction information; A method that includes this.

24. In the method according to claim 23, the step of constructing the FC based on the instruction information is: Steps to construct the FC based on the instruction information, the measurement slot identifier corresponding to the first message, the sequence information, and the measurement block identifier corresponding to the first message; Methods that include...

25. A communication method for ultra-wideband (UWB): The step of receiving a first message; and A step of constructing a frame count FC based on the order information in the message list for the list element corresponding to the first message in the message list; A method that includes this.

26. The method according to claim 25, the step of constructing a frame count FC based on the order information in the message list for a list element corresponding to the first message in the message list is: Steps of constructing the FC based on the measurement slot identifier corresponding to the first message, the sequence information, and the measurement block identifier corresponding to the first message; Methods that include...

27. The method according to claim 25, the step of constructing a frame count FC based on the order information in the message list for a list element corresponding to the first message in the message list is: Steps of constructing the FC based on the first field in the first message, the sequence information, and the measurement block identifier corresponding to the first message; Methods that include...

28. A method according to any one of claims 22 to 27, wherein different list elements in the message list correspond to different devices.

29. The method according to claim 28, wherein each list element in the message list includes a device identifier.

30. A method according to any one of claims 22 to 29, wherein the message list is included in a third message transmitted before the first message is transmitted.

31. The method according to claim 30, wherein the third message is an Advertisement Confirmation ADV-CONF message in a Narrowband Auxiliary Multi-Millisecond Ultra-Wideband NBA-MMS UWB Measurement Process.

32. A method according to any one of claims 22 to 24, wherein the instruction information further indicates whether the first message includes a measurement round identifier.

33. A method according to any one of claims 22 to 24, wherein the instruction information further indicates whether the first message includes the measurement block identifier.

34. A method according to any one of claims 22 to 24, wherein the instruction information is included in the first message.

35. A method according to any one of claims 22 to 34, wherein the first message is a message in a compressed physical layer service data unit (PSDU) format.

36. The method according to claim 35, wherein the first message is a control message in a narrowband-assisted multi-millisecond ultrawideband NBA-MMS UWB measurement process.

37. The method according to claim 36, wherein the first message is one of a start-of-ranging SOR message, a polling / initiating POLL message, a reporting message, or a response message. A method that includes this.

38. A communication device comprising a module or unit configured to perform the method described in any one of claims 1 to 21.

39. A communication device comprising a module or unit configured to perform the method described in any one of claims 22 to 37.

40. A communication device including a processor, wherein the processor is coupled to a memory, the memory stores program instructions, and the processor is configured to execute the computer program instructions so that the communication device can perform the method according to any one of claims 1 to 37.

41. It's a tip: A communication interface configured to receive / transmit signals from the aforementioned chip; and A processor configured to execute computer program instructions so that a communication device including the chip can perform the method described in any one of claims 1 to 37; A chip that includes this.

42. A computer-readable storage medium for storing a computer program, wherein the computer program includes program instructions, and when the program instructions are executed, the computer can perform the method according to any one of claims 1 to 37.

43. A computer program product wherein, when the computer program product is executed on a computer, the computer is able to perform the method described in any one of claims 1 to 37.

44. A communication method for ultra-wideband (UWB): Steps include generating an Advertise Confirmation ADV-CONF message, the ADV-CONF message including a time offset relative to a SOR list and instructional information indicating the number of responders, the time offset relative to the SOR list including the address of a first responder and a time offset relative to the start of ranging SOR corresponding to the first responder, the time offset relative to the SOR corresponding to the first responder being a time offset relative to the time when the initiator sent a first SOR message to the first responder; and The step of sending the aforementioned ADV-CONF message; A method that includes this.

45. In the method of claim 44, further: A step of sending the first SOR message to the first responder, wherein the first SOR message includes a time offset between the time the first responder receives the first SOR message and the time the first responder sends a polling / initiating POLL message; A method that includes this.

46. A communication method for ultra-wideband (UWB): Steps include: receiving an Advertise Confirmation ADV-CONF message, the ADV-CONF message including a time offset relative to a SOR list and instructional information indicating the number of responders, the time offset relative to the SOR list including the address of a first responder and a time offset relative to the start of ranging SOR corresponding to the first responder, the time offset relative to the SOR corresponding to the first responder being a time offset relative to the time when the initiator sent a first SOR message to the first responder; and A step of obtaining a time offset for the SOR corresponding to the first responder based on the ADV-CONF message; A method that includes this.

47. The method according to claim 46, further: A step of receiving the first SOR message, wherein the first SOR message includes a time offset between the time the first responder receives the first SOR message and the time the first responder sends a polling / initiating POLL message; and Based on the first SOR message, the step of obtaining a time offset between the time the first SOR message was received and the time the first responder sent a polling / initiating POLL message; A method that includes this.

48. A communication device comprising a module or unit configured to perform the method described in any one of claims 44 to 47.

49. A communication device including a processor, wherein the processor is coupled to a memory, the memory stores computer program instructions, and the processor is configured to execute the computer program instructions so that the communication device can perform the method according to any one of claims 44 to 47.

50. It's a tip: A communication interface configured to receive / transmit signals from the aforementioned chip; and A processor configured to execute computer program instructions so that a communication device including the chip can perform the method described in any one of claims 44 to 47; A chip that includes this.

51. A computer-readable storage medium for storing a computer program, wherein the computer program includes program instructions, and when the program instructions are executed, the computer can perform the method according to any one of claims 44 to 47.

52. A computer program product wherein, when the computer program product is executed on a computer, the computer is able to perform the method described in any one of claims 44 to 47.

Images