Communication method for UWB and related product

Abstract

The invention discloses a communication method for a UWB (Ultra Wideband) and a related product, which can be applied to a wireless personal local area network system, a sensing system, a positioning system, a ranging system or a communication system based on the UWB, and can also be applied to a wireless local area network system supporting a next generation Wi-Fi (Wireless Fidelity) protocol of IEEE (Institute of Electrical and Electronic Engineers) 802.11 ax, such as 802.11 series protocols such as 802.11 be, Wi-Fi7, 802.11 be next generation, Wi-Fi8 and the like. The method comprises: generating indication information, the indication information being used for indicating to construct a frame count (FC) based on a first field in a first message, the first field being used for indicating a type of the first message; and sending the indication information. The method provided by the embodiment of the invention can save signaling overhead.

Description

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

[0002] The present 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 that uses nanosecond non-sinusoidal narrow pulses to transmit signals, so it occupies a wide spectrum range. Due to its narrow pulses and extremely low radiation spectrum density, the UWB system has the advantages of strong multipath resolution, low power consumption, and strong confidentiality, and has attracted widespread attention in the industry. The Institute of Electrical and Electronics Engineers (IEEE) has incorporated UWB technology into its IEEE 802 series of wireless standards and released the wireless personal area networks (WPAN) standard IEEE 802.15.4a based on UWB technology, as well as its evolved version IEEE802.15.4z. At present, the formulation of the next generation UWB WPAN standard IEEE 802.15.4ab has also been put on the agenda. The IEEE802.15.4ab standard plans to make a comprehensive upgrade to UWB.

[0004] Due to the large bandwidth of the ultra-wideband system, UWB devices need to have ultra-high-speed data transmission and reception capabilities, while the spectrum efficiency of the impulse radio ultra-wideband (IR-UWB) system based on pulse transmission is low. When transmitting the same information, the power consumption overhead required by the IR-UWB system is much higher than that of other narrowband short-range protocols (such as Bluetooth or Zifeng protocols). For ranging or perception scenarios, the accuracy of its measurement or perception is closely related to the signal bandwidth. The larger the signal bandwidth, the higher the accuracy of its perception or ranging. Therefore, people consider transmitting and receiving the reference signal for ranging or perception through the UWB system, and transmitting all other data through the narrowband (NB) protocol, so as to ensure the accuracy of ranging and perception and save power consumption. The above-mentioned UWB technical solution combining narrowband-assisted UWB and multi-millisecond transmission is also called narrow-band assisted multi-millisecond ultra-wideband (NBA-MMS UWB).

[0005] In the NBA-MMS UWB measurement scenario, in order to reduce the duty cycle of the NB signal, the message transmitted through the NB protocol, such as the start-of-ranging (SOR) message, can be a message based on the compressed physical layer service data unit (PHY service data unit, PSDU) format. However, the message signaling overhead based on the compressed PSDU format is large. Summary of the invention

[0006] The embodiments of the present application disclose a communication method and related products for UWB, which can solve the FC construction problem of messages based on the compressed PSDU format and have less signaling overhead.

[0007] In a first aspect, an embodiment of the present application provides a communication method for ultra-wideband UWB, the method comprising: generating indication information, the indication information being used to indicate construction of a frame count (framecounter, FC) based on a first field in a first message, the first field being used to indicate a type of the first message; and sending the indication information.

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

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

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

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

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

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

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

[0015] In a possible implementation manner of the first aspect, the sending the indication information includes: sending the first message, where the first message includes the indication information.

[0016] In this implementation, the first message includes the indication information, and no additional message is required to carry the indication information, so the signaling overhead is relatively small.

[0017] In a second aspect, an embodiment of the present application provides another communication method for ultra-wideband UWB, the method comprising: receiving indication information, the indication information being used to indicate construction of FC based on a first field in a first message, the first field being used to indicate the type of the first message; and constructing FC according to the indication information.

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

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

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

[0021] In a possible implementation manner of the second aspect, the receiving indication information includes: receiving the first message, where the first message includes the indication information.

[0022] In this implementation, the first message includes the indication information, and no additional message is required to carry the indication information, so the signaling overhead is relatively small.

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

[0024] In this implementation, the indication information is used to indicate the construction of FC based on the first field and the sorting information of 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 measurement round index, which can save signaling overhead.

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

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

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

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

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

[0030] In this implementation, the indication information is further used to indicate whether the first message includes the measurement round identifier, so that the receiving end can learn whether the first message includes the measurement round identifier according to the indication information.

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

[0032] In this implementation, the indication information is further used to indicate whether the first message includes the measurement block identifier, so that the receiving end can learn whether the first message includes the measurement block identifier according to the indication information.

[0033] In a third aspect, an embodiment of the present application provides another communication method for ultra-wideband UWB, the method comprising: receiving a first message; constructing FC according to a first field in the first message, wherein the first field is used to indicate the type of the first message.

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

[0035] In a possible implementation manner of the third aspect, constructing a frame count FC according to the first field in the first message includes: constructing FC according to the first field, a measurement round identifier corresponding to the first message, and a measurement block identifier corresponding to the first message.

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

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

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

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

[0040] In a fourth aspect, an embodiment of the present application provides another communication method for ultra-wideband UWB, the method comprising: generating indication information, the indication information being used to indicate sorting information in the message list based on list elements corresponding to the first message in the message list, constructing FC; and sending the indication information.

[0041] In the embodiment of the present application, the indication information is used to indicate the sorting information of the list element corresponding to the first message in the message list, construct the FC, avoid the display of the Round Index, and save signaling overhead.

[0042] In a fifth aspect, an embodiment of the present application provides another communication method for ultra-wideband UWB, the method comprising: receiving indication information, the indication information being used to indicate sorting information in the message list based on list elements corresponding to the first message in the message list, constructing FC; constructing FC according to the indication information.

[0043] In the embodiment of the present application, FC is constructed according to the indication information, thereby avoiding the need to display and carry the measurement round index (RoundIndex), thereby saving signaling overhead.

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

[0045] In this implementation, FC is constructed based on the measurement time slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message; the explicit carrying of the measurement round index (Round Index) is avoided, and signaling overhead can be saved.

[0046] In a sixth aspect, an embodiment of the present application provides another communication method for ultra-wideband UWB, the method comprising: receiving a first message; constructing FC according to sorting information of list elements corresponding to the first message in the message list.

[0047] In the embodiment of the present application, FC is constructed according to the sorting information of the list element corresponding to the first message in the message list, thereby avoiding the display of the measurement round index (Round Index), and saving signaling overhead.

[0048] In a possible implementation of the sixth aspect, a frame count FC is constructed according to the sorting information of the list element corresponding to the first message in the message list, including: constructing FC according to the measurement time slot identifier corresponding to the first message, the sorting information and the measurement block identifier corresponding to the first message.

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

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

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

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

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

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

[0055] In this implementation, the indication information is further used to indicate whether the first message includes the measurement round identifier, so that the receiving end can learn whether the first message includes the measurement round identifier according to the indication information.

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

[0057] In this implementation, the indication information is further used to indicate whether the first message includes the measurement block identifier, so that the receiving end can learn whether the first message includes the measurement block identifier according to the indication information.

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

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

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

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

[0062] In a seventh aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the method embodiment of the first aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or by hardware executing corresponding software implementations, and the hardware or software includes one or more modules or units corresponding to the above functions. In a possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate indication information, the indication information is used to indicate the construction of FC based on the first field in the first message, and the first field is used to indicate the type of the first message; the transceiver module is used to send the indication information.

[0063] In a possible implementation manner of the seventh aspect, the transceiver module is further used to send a second message, where the second message includes a second field for indicating a deadline for receiving the SOR message.

[0064] Possible implementations of the communication device of the seventh aspect may refer to various possible implementations of the first aspect.

[0065] For the technical effects brought about by various possible implementation methods of the seventh aspect, reference may be made to the introduction to the technical effects of the first aspect or various possible implementation methods of the first aspect.

[0066] In an eighth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the method embodiment of the second aspect above. The communication device may be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive indication information, the indication information is used to indicate the construction of FC based on the first field in the first message, and the first field is used to indicate the type of the first message; the processing module is used to construct FC according to the indication information.

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

[0068] In a possible implementation manner of the eighth aspect, the transceiver module is specifically used to receive the first message, and the first message includes the indication information.

[0069] Possible implementations of the communication device of the eighth aspect may refer to various possible implementations of the second aspect.

[0070] For the technical effects brought about by various possible implementation methods of the eighth aspect, reference may be made to the introduction to the technical effects of the second aspect or various possible implementation methods of the second aspect.

[0071] In the ninth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the method embodiment of the third aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or by hardware executing corresponding software implementations, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first message; the processing module is used to construct an FC according to a first field in the first message, and the first field is used to indicate the type of the first message.

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

[0073] In a possible implementation manner of the ninth aspect, the processing module is specifically used to construct FC according to the first field and sorting information of the list element corresponding to the first message in the message list.

[0074] Possible implementations of the communication device of the ninth aspect may refer to various possible implementations of the third aspect.

[0075] Regarding the technical effects brought about by various possible implementation methods of the ninth aspect, reference may be made to the introduction to the technical effects of the third aspect or various possible implementation methods of the third aspect.

[0076] In the tenth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the method embodiment of the fourth aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or by hardware executing corresponding software implementations, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate indication information, and the indication information is used to indicate the construction of FC based on the sorting information of the list element corresponding to the first message in the message list in the message list; the transceiver module is used to send the indication information.

[0077] Possible implementations of the communication device of the tenth aspect may refer to various possible implementations of the fourth aspect.

[0078] Regarding the technical effects brought about by various possible implementation methods of the tenth aspect, reference may be made to the introduction to the technical effects of the fourth aspect or various possible implementation methods of the fourth aspect.

[0079] In the eleventh aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the method embodiment of the fifth aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive indication information, and the indication information is used to indicate the sorting information of the list element corresponding to the first message in the message list in the message list, and construct FC; the processing module is used to construct FC according to the indication information.

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

[0081] Possible implementations of the communication device of the eleventh aspect may refer to various possible implementations of the fifth aspect.

[0082] Regarding the technical effects brought about by various possible implementation methods of the eleventh aspect, reference may be made to the introduction to the technical effects of the fifth aspect or various possible implementation methods of the fifth aspect.

[0083] In the twelfth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the above-mentioned sixth aspect method embodiment. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or by hardware executing corresponding software implementations, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first message; the processing module is used to construct an FC according to the sorting information of the list element corresponding to the first message in the message list in the message list.

[0084] In a possible implementation manner of the twelfth aspect, the processing module is specifically used to construct an FC according to the measurement time slot identifier corresponding to the first message, the sorting information, and the measurement block identifier corresponding to the first message.

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

[0086] Possible implementations of the communication device of the twelfth aspect may refer to various possible implementations of the sixth aspect.

[0087] Regarding the technical effects brought about by various possible implementation methods of the twelfth aspect, reference may be made to the introduction to the technical effects of the sixth aspect or various possible implementation methods of the sixth aspect.

[0088] In the thirteenth aspect, an embodiment of the present application provides another communication device, which includes a processor, the processor is coupled to a memory, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the communication device executes the method shown in any one of the above-mentioned first aspect to the above-mentioned sixth aspect.

[0089] In the embodiment of the present application, in the process of executing the above method, the process of sending information (or signal) in the above method can be understood as the process of outputting information based on the instructions of the processor. When outputting information, the processor outputs the information to the transceiver so that it can be transmitted by the transceiver. After the information is output by the processor, it may also need to be processed in other ways before it reaches the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to be processed in other ways before it is input into the processor.

[0090] For operations such as sending and / or receiving involved by the processor, unless otherwise specified or unless they conflict with the actual function or internal logic in the relevant description, they can be generally understood as instructions output based on the processor.

[0091] During the implementation process, the processor may be a processor specifically used to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor, etc. For example, the processor may also be used to execute a program stored in the memory, and when the program is executed, the communication device executes the method as shown in the first aspect or any possible implementation of the first aspect.

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

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

[0094] In a possible implementation, the communication device further includes a transceiver, and the transceiver is used to receive a signal or send a signal.

[0095] In the fourteenth aspect, an embodiment of the present application provides another communication device, which includes a processing circuit and an interface circuit, the interface circuit is used to acquire data or output data; the processing circuit is used to execute the method shown in any one of the above-mentioned first aspect to the above-mentioned sixth aspect.

[0096] In the fifteenth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. The computer program includes program instructions, which, when executed, enable the computer to execute the method shown in any one of the above-mentioned first to sixth aspects.

[0097] In the sixteenth aspect, an embodiment of the present application provides a computer program product, which includes a computer program, and the computer program includes program instructions, which, when executed, enable the computer to execute the method shown in any one of the above-mentioned first to sixth aspects.

[0098] In the seventeenth aspect, an embodiment of the present application provides a communication system, comprising the communication device described in the seventh aspect or any possible implementation of the seventh aspect, and the communication device described in the eighth aspect or any possible implementation of the eighth aspect.

[0099] In the eighteenth aspect, an embodiment of the present application provides a communication system, comprising the communication device described in the tenth aspect or any possible implementation of the tenth aspect, and the communication device described in the eleventh aspect or any possible implementation of the eleventh aspect.

[0100] In the nineteenth aspect, an embodiment of the present application provides a chip, including a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes a method as shown in any one of the first to sixth aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

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

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

[0104] Figure 3 A schematic diagram of the initialization process of NBA-MMS UWB ranging;

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

[0106] Figure 4B A schematic diagram of one-to-many NBA-MMS UWB ranging based on an interleaved mode;

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

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

[0109] Figure 7 An example of a UWB system to which the technical solution provided in the embodiments of the present application is applicable;

[0110] Figure 8 An interactive flow chart of a communication method for UWB provided in an embodiment of the present application;

[0111] Fig. 9 A schematic diagram of an NBA-MMS UWB ranging process provided in an embodiment of the present application;

[0112] Fig.10 Another communication method interaction process for UWB provided in an embodiment of the present application;

[0113] Fig.11 Another communication method interaction process for UWB provided in an embodiment of the present application;

[0114] Fig.12 Another communication method interaction process for UWB provided in an embodiment of the present application;

[0115] Fig.13 Schematic diagram of the initialization process for pre-configuring one-to-many NBA-MMS UWB ranging;

[0116] Fig.14 Another communication method interaction process for UWB provided in an embodiment of the present application;

[0117] Fig.15 Another communication method interaction process for UWB provided in an embodiment of the present application;

[0118] Fig.16 A schematic diagram of the structure of a communication device 1600 provided in an embodiment of the present application;

[0119] Fig.17 A schematic diagram of the structure of another communication device 170 provided in an embodiment of the present application;

[0120] Fig.18 A schematic diagram of the structure of another communication device 180 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0121] The terms "first" and "second" in the specification, claims and drawings of the present application are only used to distinguish different objects, rather than to describe a specific order. It is understood that the various digital numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and inherent logic. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or equipment, etc., comprising a series of steps or units, is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, etc., or optionally also includes other steps or units inherent to these processes, methods, products or equipment, etc.

[0122] The "embodiment" mentioned in this article means that the specific features, structures or characteristics described in conjunction with the embodiment can be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It can be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0123] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be used as limitations to the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include plural expressions, unless there is a clear contrary indication in its context. It should also be understood that the term "and / or" used in the present application refers to and includes any or all possible combinations of one or more listed items. For example, "A and / or B" can represent: only A exists, only B exists, and A and B exist at the same time, wherein A, B can be singular or plural. The term "multiple" used in the present application refers to two or more. In the textual description of the present application, the character " / " generally indicates that the front and back associated objects are a kind of "or" relationship.

[0124] It can be understood that in each embodiment of the present application, "A corresponds to B" means that there is a corresponding relationship between A and B, and B can be determined according to A. However, it should also be understood that determining (or generating) B according to (or based on) A does not mean that B is determined (or generated) only according to (or based on) A, and B can also be determined (or generated) according to (or based on) A and / or other information.

[0125] To facilitate understanding of the solutions of the present application, the following first introduces the terms and technical solutions involved in the embodiments of the present application.

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

[0127] In the IEEE 802.15.4z standard, a single ranging process is defined as a ranging round. In the IEEE 802.15.4z standard, a ranging round is defined as: a ranging round is a period of sufficient duration to complete one entire range-measurement cycle involving the set of ERDEVs participating in the ranging exchange. The minimum processing time unit of each ranging round is a ranging slot. In a ranging round, there are three phases: ranging control phase, ranging phase, and measurement report phase. Figure 1 Schematic diagram of various stages of a distance measuring wheel in the prior art. Figure 1 In the IEEE 802.15.4z standard, the ranging control phase includes one ranging time slot, while in the IEEE 802.15.4ab standard currently under discussion, the ranging control phase may include more than one ranging time slot.

[0128] exist Figure 1 In the first time slot of the ranging wheel shown, the controller will send a ranging control message (RCM). The RCM may carry an update message about the wheel structure of the ranging wheel, such as the update of the round duration of the ranging wheel.

[0129] The new and old ranging rounds (hereinafter referred to as rounds) may be adjacent in time or not adjacent in time. The durations of different rounds may be the same or different. The following description assumes that the durations of different rounds are the same.

[0130] Among them, the situation where the time between the new and old ranging rounds (hereinafter referred to as rounds) is not adjacent is determined by Figure 2 shown. Figure 2 FIG. 1 is a schematic diagram of a distance measurement block in the prior art. Figure 2As shown, the distance measurement block can be a time structure including multiple distance measurement wheels. Optionally, the distance measurement block will be repeated in a periodic manner. Optionally, the duration of each distance measurement wheel in the distance measurement block is equal. Figure 2 As shown, for a specific ranging process, its initiator and responder will be carried out in a ranging round in a ranging block, for example Figure 2 Round 1 shown. In the present application, the initiator may be referred to as the initiator, that is, the UWB device that initiates the ranging / perception / communication process. During the ranging / perception / communication process, the initiator may be a transmitter or a receiver. In the present application, the initiator may be referred to as the responder, that is, the UWB device that responds to the ranging / perception / communication process initiated by the UWB initiator device. During the ranging / perception / communication process, the responder may be a transmitter or a receiver. When the ranging round is completed, the specific ranging process will be carried out in round 1 in the next ranging block. By Figure 2 It can be seen that two adjacent round 1s are not adjacent in time, that is, there is a time interval between two adjacent round 1s. In the interval between two adjacent round 1s, the device can turn off the receiver to sleep to save power. Among them, the duration of adjacent ranging blocks can be the same or different. For example, ranging blocks with different durations of adjacent ranging blocks can be located in a hyper-block. The following description assumes that the duration of adjacent ranging blocks is the same as an example.

[0131] Before conducting (or starting) NBA-MMS UWB ranging, the initialization and establishment process needs to be carried out (or executed) between related devices. Taking the initiator as the controller as an example, the initiator needs to first broadcast a notification message to inform all responders that NBA-MMS UWB ranging needs to be carried out. The broadcast notification message can be carried by an advertisement poll (ADV-POLL) message. After receiving the ADV-POLL message, if the responder needs to carry out ranging, it will feedback an advertisement response message / advertisement response message (ADV-RESP) message to the initiator. In the ADV-RESP message, the responder will carry the parameter configuration information it needs. After receiving the ADV-RESP message, the initiator can decide whether to confirm the adoption of the parameter configuration proposed by the responder, and can inform the responder of the final parameter configuration result through the start-of-ranging (SOR) message. The SOR message can carry a parameter confirmation message in the ADV-RESP message to the responder, or a parameter change / update message in the ADV-RESP message to the responder. After a certain interval after the responder receives the SOR message, the initiator and responder can start the NBA-MMS UWB ranging process. The length of the interval can be determined by the Time offset to MMS POLL information in the SOR message. The initialization process of NBA-MMS UWB ranging described above is as follows Figure 3 shown. Figure 3 A schematic diagram of the initialization process of NBA-MMS UWB ranging.

[0132] The application scenario of NBA-MMS UWB ranging can be a one-to-one scenario, that is, one initiator corresponds to one responder, or a one-to-many scenario, that is, one initiator corresponds to multiple responders, as follows Figure 4A shown. Figure 4A A schematic diagram of one-to-many NBA-MMS UWB ranging.

[0133] Figure 4AIn the one-to-many NBA-MMS UWB ranging shown, the initiator and each responder carry out NBA-MMS UWB ranging one by one. That is, the initiator and each responder will complete the interaction of inquiry / initiation (POLL) message and response (response, RESP) message, multi-millisecond (multi-millisecond, MMS) block interaction, ranging, and ranging result reporting (carried on Report message) interaction process. In this article, the response message can be called RESP message, Response message, or RESPONSE message. The ranging result reporting includes both the Report message from the responder to the initiator and the Report message from the initiator to the responder. Figure 4A The ranging process shown can be called one-to-many NBA-MMS UWB ranging based on concatenation mode. It should be noted that the present application is also applicable to one-to-many ranging processes of other modes, such as one-to-many NBA-MMS UWB ranging based on interlacing mode, see Figure 4B . Figure 4B Figure 1 is a schematic diagram of one-to-many NBA-MMS UWB ranging based on an interleaved mode. Figure 4B As shown, in the one-to-many NBA-MMS UWB ranging based on the staggered mode, each responder sends the MMS blocks in sequence, instead of waiting for the previous responder to send all the MMS blocks before the next responder sends all the MMS blocks. In each embodiment of the present application. The following description is based on the one-to-many NBA-MMS UWB based on the splicing mode as an example. The related embodiment method is also applicable to the one-to-many NBA-MMS UWB process based on the staggered mode, and will not be repeated.

[0134] In an embodiment of the present application, a single positioning process, i.e., a process of completing a positioning task, is defined as a positioning wheel. The positioning wheel may be called by other names, which are not limited in the present application. The positioning wheel may be a time period (or time cycle) sufficient to complete a complete positioning task. The meaning of the positioning wheel is similar to that of the ranging wheel, except that one is a time period corresponding to ranging, and the other is a time period corresponding to positioning. The minimum processing time unit of each positioning wheel is a positioning slot. In a positioning wheel, it can be divided into three phases: positioning control phase, positioning phase, and positioning report phase.

[0135] In an embodiment of the present application, a single perception process, that is, a process of completing a perception task, is defined as a perception round. The perception wheel can be other names, which are not limited in this application. A perception wheel can be a time period (or time cycle) sufficient to complete a complete perception task. The meaning of a perception wheel is similar to that of a ranging wheel, the difference being that one is a time period corresponding to ranging, and the other is a time period corresponding to perception. The minimum processing time unit of each perception wheel is a sensing slot. In a perception wheel, it can be divided into three phases: a sensing control phase, a sensing phase, and a sensing report phase.

[0136] A measurement cycle refers to the time period during which one or more UWB devices complete one or more measurement tasks. Here, the measurement tasks may be ranging tasks, positioning tasks, perception tasks, etc. A measurement cycle may be a ranging wheel, a positioning wheel, or a perception wheel. It should be noted that the ranging wheel in the following text may be replaced by a perception wheel, a positioning wheel, or a measurement cycle (which may be referred to as a measurement wheel); correspondingly, the ranging task may be replaced by a perception task, a positioning task, or a measurement task.

[0137] In addition, it should be noted that the names of the different stages in a single measuring wheel (such as a ranging wheel, a sensing wheel, a positioning wheel, etc.) are only examples and do not constitute any limitation on the scope of protection of the present application. For example, the above-mentioned measurement control stage can be understood as a stage for configuring the required parameters in the measuring wheel. For another example, the above-mentioned measurement stage can be understood as a stage for performing measurements. For another example, the above-mentioned measurement result reporting stage can be understood as a stage for reporting measurement results, and can also be called the end of the measurement stage. In addition, it should be noted that in each embodiment of the present application, the size of each field represents the number of bits occupied by each field.

[0138] The compressed header cell message format.

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

[0140] Table 1-1

[0141] SHR PHR Compressed PSDU

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

[0143] Table 1-2

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

[0145] The Frame Control field is used to control the format of the header IE. The Frame Control field occupies one byte (Octets / Bytes).

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

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

[0148] CRC field: also known as cyclic redundancy check field (CRC), is a field for error detection of the compressed PSDU in Table 1-2. The CRC field occupies two bytes.

[0149] As can be seen from Table 1-1 and Table 1-2, messages (or data packets) based on the compressed PSDU format do not contain a separate frame counter (FC) field. Due to the absence of the FC field in messages based on the compressed PSDU format, it also means that the FC cannot be used directly to construct a Nonce (a random number used only once). In the authentication protocol, Nonce is a random number or pseudo-random number to avoid replay attacks. Nonce is used to implement message encryption / authentication. In this article, authentication and verification have the same meaning.

[0150] In order to solve the problem that the message based on the compressed PSDU format cannot directly use FC to construct Nonce, an existing technical solution (hereinafter referred to as the prior art) is as follows: based on the different timing structure characteristics of NBA-MMS ranging in the initialization phase and the measurement cycle phase, different methods are used to construct Nonce for the message based on the compressed PSDU format transmitted in the corresponding phase.

[0151] In the prior art, the scheme for constructing Nonce for messages based on the compressed PSDU format 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 public payload portion (i.e., non-encrypted payload, open payload) of these messages. The PN field is used to construct Nonce, that is, to solve the Nonce construction problem of the aforementioned compressed PSDU format messages. Taking the SOR message in Table 2 as an example, the SOR message contains a PN field. Table 2 is a schematic diagram of the PSDU format of the SOR message.

[0152] Table 2

[0153]

[0154] 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.

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

[0156] PN field: used by the receiving end to construct Nonce, which is used to authenticate / verify the current message. The receiving end is the device that receives the SOR message in Table 2. The PN field occupies 4 bits.

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

[0158] MIC (message integrity code) field: used to verify the authenticity of the frame and whether there is an error. The MIC field occupies 2 bits.

[0159] Among them, a format of Nonce based on the PN field shown in Table 2 is shown in Table 3.

[0160] Table 3

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

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

[0163] PN field: used by the receiving end to construct the Nonce. The PN field acts as the missing FC field in the compressed PSDU.

[0164] Nonce Security Level field: used to indicate the security protection measures taken by the message shown in Table 2.

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

[0166] In the prior art, NBA-MMS ranging constructs Nonce for messages based on the compressed PSDU format during the measurement cycle phase as follows: For messages such as POLL messages, Response messages, and Report messages for ranging control purposes, Nonce is constructed based on the timing information such as slot index / round index / block index of the ranging process known in advance. That is to say, for messages such as POLL messages, Response messages, and Report messages for ranging control purposes, there is no need to add an explicit PN field for Nonce construction in the public payload part of these messages. For example, before sending messages such as POLL messages, Response messages, and Report messages for ranging control purposes, a SOR message carrying timing information such as slotindex / roundindex / blockindex is sent for scheduling management of POLL messages / Response messages / Report messages during the measurement cycle phase and FC construction (described below). After the receiving end receives the SOR message, it can obtain the timing information such as slot index / roundindex / blockindex of the ranging process based on the received SOR message. Taking the Report message shown in Table 4 as an example, the format of the Nonce constructed for the Report message is shown in Table 5.

[0167] Table 4

[0168]

[0169] In Table 4, fields such as Message ID, Security Enable, and Address are consistent with the fields in the aforementioned Table 2 and are not repeated here.

[0170] Table 5

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

[0172] In Table 5, the Source Address field is used to indicate the extended address of the device that sends the frame to be verified, the SlotIndex field indicates the Slot Index (e.g., measurement slot index) corresponding to the frame to be verified, the Round Index field indicates the Round Index (e.g., measurement round index) corresponding to the frame to be verified, and the Block Index field indicates the Block Index (e.g., measurement block index) corresponding to the frame to be verified. As can be seen from Table 5, the Nonce constructed for the Report message is determined by the sending timing corresponding to the Report message, that is, by the slot index / round index / block index. A method for generating the FC of the Nonce is: FC=slot index||round index||block index. Among them, the symbol "||" indicates a splicing operation. For example, assuming that the Slot index value is 0x03, the round index value is 0x10, and the block index value is 0x07, the FC generated after splicing is 0000001100000000000100000000000000000111 (binary representation). The Slot Index field, Round Index field, and Block Index field in Table 5 are all included in FC. In other words, the Slot Index field, Round Index field, and Block Index field in Table 5 are concatenated to form FC. It can be seen that Nonce is constructed based on FC.

[0173] From the foregoing introduction, it can be seen that in the existing scheme for constructing Nonce for messages based on the compressed PSDU format during the initialization phase, messages based on the compressed PSDU format (such as SOR messages) need to explicitly carry the PN field, which will bring additional signaling overhead. In the existing scheme for constructing Nonce for messages based on the compressed PSDU format during the measurement cycle phase, messages such as SOR messages need to explicitly carry timing information such as slot index / round index / block index, which will also bring additional signaling overhead. Since the design concept of compressed PSDU is to reduce the inherent signaling overhead as much as possible, there is a certain degree of contradiction between the prior art and the design concept of compressed PSDU. The present application provides a solution for constructing Nonce for messages based on the compressed PSDU format without increasing signaling overhead. The following first introduces the scenarios to which the communication solution for UWB provided by the application is applicable.

[0174] The communication scheme for UWB provided in the embodiment of the present application can work in a star topology, a point-to-point topology, or a mesh topology. The communication scheme for UWB provided in the embodiment of the present application can also work in other topologies, which are not limited in the present application. Figure 5 A schematic diagram of an example of a star topology is shown in FIG. Figure 5 As shown, the star topology involves a central control node, e.g. Figure 5 The personal area network (PAN) or coordinator shown in the figure. The communication scheme for UWB provided in the embodiment of the present application is applicable to data communication / perception / distance measurement / positioning between a central control node and one or more other devices in a star topology. Figure 6 Schematic diagram of an example of a point-to-point topology or a mesh topology. The communication solution for UWB provided in the embodiment of the present application is also applicable to point-to-point topology or mesh topology ( Figure 6 ), communication / perception / ranging / positioning between different devices. Figure 5 and Figure 6 In the figure, the black nodes are full-function devices (FFD) and the white nodes are reduced function devices (RFD). FFD can act as a PAN coordinator or coordinator, while RFD cannot act as a PAN coordinator or coordinator. FFD devices can communicate with each other and with RFD devices. RFD devices cannot communicate directly with each other, but can only communicate with FFD devices, or forward data outward through an FFD device. In the UWB system, FFD can be an anchor device or a tag device with strong computing power (such as a UWB tag mounted on a smartphone); while RFD is a tag device with only partial computing power.

[0175] The technical solution of the present application is mainly applicable to UWB systems, such as UWB systems that support the next generation standard of IEEE 802.15.4a standard, IEEE802.15.4z standard, IEEE 802.15.4ab standard, or IEEE 802.15.4ab standard. It is easy for those skilled in the art to understand that the various aspects involved in the present application can be extended to other networks using various standards or protocols, such as BLUETOOTH (Bluetooth), high performance wireless LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe) and wide area network (WAN), personal area network (PAN) or other networks known now or developed later. Therefore, regardless of the coverage range and wireless access protocol used, the various aspects provided by the embodiments of the present application can be applied to any suitable wireless network.

[0176] See also Figure 7 , Figure 7 An example of a UWB system to which the technical solution provided in the embodiments of the present application is applicable. The UWB system includes an anchor (anchor, only one anchor is shown), one or more tags (tags, only tag 1 and tag 2 are shown). Among them, the protocols supported by the anchor and the tag may include IEEE 802.15.4a, IEEE 802.15.4z, IEEE802.15.4ab and other protocols. Of course, with the continuous evolution and development of communication technology, the WLAN protocol may also include the next generation protocol of IEEE802.15.4ab, etc. The anchor point may be an access point, and the tag may be a station (Station, STA). Both the access point and the STA support the WLAN protocol, and the WLAN protocol may include IEEE 802.11be (or Wi-Fi 7, EHT protocol).

[0177] An access point is a device with wireless communication function, supports communication using WLAN protocol, and has the function of communicating with other devices in the WLAN network (such as stations or other access points). Of course, it can also have the function of communicating with other devices. In the UWB system, there are one or more access point (AP) type stations and one or more non-access point type stations (none access point station, non-AP STA). For ease of description, this article refers to access point type stations as access points (APs) and non-access point type stations as stations (STAs).

[0178] The access point can be a complete device, or a chip or processing system installed in the complete device. The device installed with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of the chip or processing system (i.e., AP). The AP in the embodiments of the present application is a device that provides services for stations (STAs), and can support, for example, IEEE 802.15.4a, IEEE 802.15.4z, IEEE 802.15.4ab or its next generation. For example, AP can be a communication entity such as a communication server, a router, a switch, a bridge, a computer, a mobile phone, etc. AP may include an anchor, a macro base station, a micro base station (also called a small station), a pico base station, a femto base station, a relay station, an access point, a gNB, a transmission reception point (TRP), an evolved Node B (eNB), a radio network controller (RNC), a home base station (e.g., home evolved NodeB, or homeNode B, HNB), a base band unit (BBU), a WiFi access point (AP), an integrated access and backhaul (IAB), etc. Of course, AP may also be a chip and a processing system in these various forms of devices, so as to realize the methods and functions of the embodiments of the present application.

[0179] A station is a device with wireless communication function, supports communication using WLAN protocol, and has the ability to communicate with other stations or access points in the WLAN network. For example, STA is any communication device that allows a user to communicate with an AP and then communicate with a WLAN. The communication device can be a complete device, or a chip or processing system installed in the complete device. Devices installed with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of the chip or processing system (i.e., station). STA may include tag devices / smart tag devices, mobile phones, mobile stations (MS), tablet computers (pads), computers with wireless transceiver functions (such as laptops), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, 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 assistants (PDA) computers, tablet computers, laptop computers, machine type communication (MTC) terminals, etc. Stations may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems. For example, the station can be a handheld device (handset) with wireless communication function, a vehicle-mounted device, a wearable device or a terminal in the Internet of Things, the Internet of Vehicles, 5G and any form of terminal in the communication system evolved after 5G, etc., which is not limited by this application. The station can support the IEEE 802.15 series of protocols, such as IEEE 802.15.4a, IEEE 802.15.4z, and IEEE 802.15.4ab.

[0180] It should be noted that, unless otherwise specified, the following description assumes that the initiator is the controller. The corresponding description is applicable to the case where the responder is the controller, or the controller is a third-party device. The methods proposed in this application are applicable. In addition, unless otherwise specified, the following description assumes that the one-to-many case is used, that is, one initiator corresponds to multiple responders. The corresponding description assumes that multiple initiators correspond to multiple responders, and the methods proposed in this application are applicable. In addition, unless otherwise specified, the following description assumes that the initiator broadcasts the configuration update message of the measurement round (such as the ranging round) to all responders through the measurement initiation message (such as the SOR message) before the start of each measurement round. Accordingly, after receiving the configuration update message of the measurement round, the responder completes the parameter update configuration and starts the current round of measurement and the subsequent measurement rounds with the new parameters (until the next parameter update configuration). The corresponding description is for the case where the initiator broadcasts the measurement initiation message at other times, for example, the case where the configuration update message of the measurement round is broadcast through the measurement initiation message during the measurement reporting phase of each measurement round, to which the method proposed in the present application is applicable.

[0181] In addition, unless otherwise specified, the following text assumes that the measurement initiation message is used to carry the sending of the configuration update message of the measurement wheel. The corresponding description is also applicable to the case where other messages are used to carry the sending of the configuration update message of the measurement wheel. For example, in NBA-MMS UWB ranging, the initiator sends a POLL message to the responder to carry the configuration update message of the measurement wheel, and the methods proposed in this application are applicable. For example, in one-to-many NBA-MMS UWB ranging, the initiator carries the configuration update message of the ranging wheel by sending a POLL message to the first responder. Among them, the first responder refers to the first responder that conducts ranging with the initiator in chronological order among multiple responders. At this time, the POLL message is sent by broadcasting. For another example, in NBA-MMS UWB ranging, the responder carries the configuration update message of the measurement wheel by sending a Response message to the initiator. For another example, in NBA-MMS UWB ranging, the Report message sent by the initiator (responder) to the responder (initiator) carries the configuration update message of the measurement round. For the above-mentioned examples, the methods proposed in this application are applicable. In addition, for the convenience of expression, the following text assumes by default that in the first measurement initiation message, the order in which the list elements appear is consistent with the subscript order of the device, that is, the list elements #0, #1, ..., ~#N correspond to device 0, device 1, ..., device N, respectively. The corresponding description is also applicable to other situations. For example, the list elements #0, #1, ..., ~#N correspond to devices 2, 4, ..., and N, respectively, and the methods proposed in this application are applicable. In addition, unless otherwise specified, the following text defaults to the ranging process as an example. The corresponding description is applicable to other measurement processes, such as perception, positioning, etc. The methods proposed in this application are applicable. In other words, the following description takes the measurement process as an example of ranging. In addition, unless otherwise specified, the following text defaults to the situation where the new and old rounds are not adjacent in time. The corresponding description is applicable to rounds that are temporally adjacent to each other, and the method proposed in this application is applicable.

[0182] In addition, unless otherwise specified, the following description assumes that NBA-MMS UWB ranging is used as an example. The corresponding description is also applicable to other ranging, sensing, positioning and other measurement applications. Among them, other ranging includes but is not limited to: non-NBA-MMS ranging (ranging that does not include NBA or MMS), MMS ranging (ranging that does not include NBA but includes MMS).

[0183] Figure 8An interactive process of a communication method for UWB provided in an embodiment of the present application. Figure 8 The method shown can be applied to ranging, perception, positioning, communication and other scenarios, for example: ranging based on NBA-MMS, perception based on NBA-MMS, positioning based on NBA-MMS and other scenarios. Figure 8 As shown, the method includes:

[0184] 801. A sender generates a first message.

[0185] The transmitting end may be a UWB device supporting 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 an initiator of ranging, perception, positioning, or communication, i.e., a ranging initiator, a perception initiator, a positioning initiator, or a communication initiator; it may also be a responder of ranging, perception, positioning, or communication, i.e., a ranging responder, a perception responder, a positioning responder, or a communication responder; it may also be a third-party device (which may be referred to as a controller device), i.e., it is not an initiator or responder of ranging, perception, positioning, or communication. In the following, the relevant description of the transmitting end may refer to step 801.

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

[0187] The number of bits occupied by the indication information may be less than 4 bits, that is, less than the number of bits occupied by the PN field (see Table 2 and Table 3). For example, the indication information occupies 1 bit or 2 bits. Therefore, compared with the existing scheme of displaying and carrying the PN field, the scheme in which the first message includes the indication information has less signaling overhead. The following takes the first message being a POLL message as an example to introduce a possible format of the first message. Table 6 is an example of the PSDU format of the POLL message.

[0188] Table 6

[0189]

[0190] In Table 6, the fields such as Message ID, Security Enable, Address, Secured Payload, and MIC are consistent with the fields in the aforementioned Table 2 and are not repeated here. The Block Index field is used to indicate the ranging block corresponding to the POLL message, and the Round Index field is used to indicate the ranging round corresponding to the POLL message. In this article, 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 include a Block Index field (occupying 2 bits), or it may not include a Block Index field. Table 6 may include a RoundIndex field (occupying 2 bits), or it may not include a Round Index field. The Presence Control field includes the above-mentioned indication information. The Presence Control field may occupy 1 bit, 3 bits, or one byte. This application does not limit the position and size of the PresenceControl field, nor does it limit the name of the PresenceControl field. In this article, the size of the field refers to the number of bits occupied by the field. In addition, the Presence Control field may be a new field or may be included in an existing field. It should be understood that Table 6 is only an example of the PSDU format of the POLL message, and the position and size of each field in Table 6 are not limited.

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

[0192] Table 7-1

[0193] 1 Presence Control

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

[0195] Table 7-2

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

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

[0198] Table 7-3

[0199]

[0200]

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

[0202] 802. The sender sends a first message.

[0203] Correspondingly, the receiving end receives the first message. The receiving end may be a UWB device supporting the UWB 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 an initiator of ranging, perception, positioning, or communication, that is, a ranging initiator, a perception initiator, a positioning initiator, or a communication initiator; it may also be a responder of ranging, perception, positioning, or communication, that is, a ranging responder, a perception responder, a positioning responder, or a communication responder; it may also be a third-party device (which may be called a controller device), that is, it is not an initiator and responder of ranging, perception, positioning, or communication. For example, the sending end is an initiator and also a controller, and the receiving end is a responder. For another example, the sending end is a controller and the receiving end is a responder. In the following, the relevant description of the receiving end can be found in step 802.

[0204] In a possible implementation, the transmitting end also performs the following operations: sending a second message, wherein the second message includes a second field for indicating the deadline for receiving the SOR message. Accordingly, the receiving end receives the second message. The receiving end may stop monitoring the SOR message after the deadline for receiving the SOR message indicated by the second field, thereby avoiding the increase in energy consumption caused by waiting for a long time to monitor the SOR message. The second message also includes a field for indicating whether the second field exists. The second message is a message sent by the transmitting end before sending the SOR message (for example, the first message). The second message may be an ADV-CONF message or other message, which is not limited in this application. Here, the second message is introduced by taking the ADV-CONF message as an example. Table 8 shows an example of the PSDU format of the ADV-CONF message containing the second field.

[0205] Table 8

[0206]

[0207] In Table 8, the SOR transmission timeout field (i.e., the second field) is used to indicate the deadline of the SOR message, and the SOR transmission timeout Presence field is used to indicate whether the second message contains the SOR transmission timeout field, i.e., whether the SOR transmission timeout field exists in the second message. The unit of the SOR transmission timeout field can be a ranging scheduling time unit (RSTU) or a time slot. The present application does not impose any limitation on the unit of the SOR transmission timeout. For example, when the value of the SOR transmission timeout Presence field is 1, the second message contains the SOR transmission timeout field, i.e., the SOR transmission timeout field exists in the second message; when the value of the SOR transmission timeout Presence field is 0, the second message does not contain the SOR transmission timeout field, i.e., the SOR transmission timeout field does not exist in the second message. 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) is used to indicate whether the SOR Message Management field is included in the second message. For example, when the value of the SMM Presence field is 1, the second message includes the SOR Message Management field; when the value of the SMM Presence field is 0, the second message does not include the SOR Message Management field. The RFU field is a reserved field, that is, a field reserved for future use, which can occupy 6 bits. It can be understood that Table 8 is only an example of the PSDU in the second message, and the size and position of each field in the second message are not limited.

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

[0209] A possible implementation of step 803 is as follows: According to the indication information in the first message, based on the above-mentioned first field, the measurement round identifier corresponding to the above-mentioned first message, and the measurement block identifier corresponding to the above-mentioned first message, construct FC. For example, the receiving end splices the first field, the measurement round identifier corresponding to the first message (such as round index), and the measurement block identifier corresponding to the first message (such as block index) to obtain FC. In this example, the FC construction method is: FC=message ID||round index||block index. "||" represents a splicing operation. After constructing 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 a source address (Source Address) and the FC. Table 9-1 is an example of a Nonce.

[0210] Table 9-1

[0211]

[0212] In Table 9-1, the Message ID field, the Round Index field, and the Block Index field constitute FC. It should be noted that this application does not impose any limitation on the construction method of FC, and the FC construction method given in the full text is just an example.

[0213] In another example, the FC construction method may also be: FC=block index||round index||message ID. In other words, the present application does not impose any limitation on the splicing order used in the FC construction.

[0214] In another example, the FC construction method can also be: FC=prePN||block index||round index||message ID. For another example, it can also be FC=prePN||message ID. Among them, prePN (pre-determined Packet Number) represents the numerical value that is agreed upon and stored in advance by the sender and receiver and can be used to construct FC. prePN can be updated according to a specific rule. For example, after a specific number of block times, the prePN value is increased by 1. This application does not impose any restrictions on the numerical update rules of prePN. In addition, this application does not impose any restrictions on other numerical values ​​that can participate in the FC construction. The above-mentioned prePN is just an example. As long as there is a situation based on message ID to participate in the construction of FC, it is within the scope of protection of this application.

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

[0216] Table 9-2

[0217]

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

[0219] In another example, the FC construction method may also be: FC=block index||CODA values||message ID. In other words, the present application does not impose any limitation on the splicing order used in the FC construction.

[0220] In another example, the FC construction method can also be: FC=prePN||block index||CODAvalues||message ID. For another example, it can also be FC=prePN||CODA values. Among them, prePN represents the numerical value that can be used to construct FC and is agreed upon and stored in advance by the sender and receiver. prePN can be updated according to a specific rule. For example, after a specific number of block times, the prePN value is increased by 1. The present invention does not impose any limitation on the numerical update rule of prePN. In addition, the present application does not impose any limitation on other numerical values ​​that can participate in the FC construction. The aforementioned prePN is just an example. As long as there is a situation based on CODA values ​​to participate in the construction of FC, it is within the scope of protection of this application.

[0221] It should be noted that this application does not impose any limitation on the format of Nonce, and Table 9-2 is only an example.

[0222] Figure 8 The method flow can be understood as: constructing the FC corresponding to the control message based on the first field (message ID) of the control message (ie, the first message), the measurement round identifier corresponding to the control message, and the measurement block identifier corresponding to the control message. Figure 8 The method flow is applicable to scenarios such as NBA-MMS-based ranging, NBA-MMS-based perception, and NBA-MMS-based positioning. In these scenarios, different control messages in the same measurement round (such as ranging round) have different message IDs, that is, the message IDs of any two control messages are different, so Figure 8 The method flow in can construct different FCs for different control messages. Fig. 9 A schematic diagram of an NBA-MMS UWB ranging process provided in an embodiment of the present application. Fig. 9 As shown in the figure, the message ID of the POLL message is 0x00, the message ID of the Response message is 0x01, the message ID of the Report message sent by the Responder is 0x02, and the message ID of the Report message sent by the Initiator is 0x03. Fig. 9 It can be seen that in a ranging round, different control messages have different message IDs. Figure 8When the method flow is applied to the NBA-MMS UWB ranging scenario, Figure 8 The method flow can be understood as: constructing the required FC through the inherent sending order of each control message in the NBA-MMS UWB ranging process, wherein the message ID of each control message can be regarded as the inherent sending order of each control message.

[0223] In the embodiment of the present application, the indication information is used to indicate that the FC is constructed based on the first field in the first message. When the indication information is included in the first message, since the indication information occupies fewer bits than the PN field, the signaling overhead is less.

[0224] Fig.10 Another communication method interaction process for UWB provided in an embodiment of the present application. Fig.10 The method shown can be applied to scenarios such as ranging, perception, positioning, and communication, for example, ranging based on NBA-MMS, perception based on NBA-MMS, and positioning based on NBA-MMS. Fig.10 The method flow and Figure 8 Compared with the method flow in , the first message does not need to carry the indication information, and the receiving end constructs the FC based on the first field in the first message by default. Fig.10 As shown, the method includes:

[0225] 1001. A sender generates a first message.

[0226] Step 1001 may refer to step 801 . Fig.10 The first message in the method flow is Figure 8 Compared with the first message in the method flow, the above-mentioned indication information is not included. The above-mentioned first message may be a message based on the compressed PSDU format. Exemplarily, the first message is a control message in the NBA-MMS UWB measurement process, such as an ADV-POLL message, an ADV-RESP message, an ADV-CONF message, a SOR message, a POLL message, a Response message, or a Report message (which may be referred to as a report message). In the present application, NBA-MMS UWB measurement includes at least one of NBA-MMS UWB ranging, NBA-MMS UWB perception, NBA-MMS UWB positioning, etc. The above-mentioned first message includes a first field. The first field may be a Message ID field. For example, the first message is the SOR message shown in Table 2, and the first field is the Message ID field. For another example, the first message is the Report message shown in Table 4, and the first field is the Message ID field.

[0227] 1002. The sender sends a first message.

[0228] Correspondingly, the receiving end receives the first message. Step 1002 may refer to step 802.

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

[0230] A possible implementation of step 1003 is as follows: construct FC according to 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 concatenates the first field, the measurement round identifier corresponding to the first message (e.g., round index), and the measurement block identifier corresponding to the first message (e.g., block index) to obtain FC. After constructing FC, the receiving end can construct the Nonce corresponding to the first message based on the FC, see Table 9. It can be understood that the FC constructed based on the first field in the first message can be used to construct a Nonce for encrypting or authenticating the first message.

[0231] Another possible implementation of step 1003 is as follows: construct FC based on the first field, the sorting information of the list element corresponding to the first message in the message list, and the measurement block identifier corresponding to the first message. The relevant content of the sorting information of the list element corresponding to the first message in the message list in the above message list will be described in detail later and will not be described here. For example, the receiving end concatenates the first field, the above sorting information (such as the CODA values ​​below), and the measurement block identifier corresponding to the first message (such as block index) to obtain FC. In this example, the FC construction method is: FC=message ID||CODA values||block index.

[0232] Fig.10 The main principles and procedures of the method Figure 8 The main principles of the method flow are similar and will not be repeated here.

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

[0234] Fig.11 Another communication method interaction process for UWB provided in an embodiment of the present application. Fig.11 The method shown can be applied to scenarios such as ranging, perception, positioning, and communication, for example, ranging based on NBA-MMS, perception based on NBA-MMS, and positioning based on NBA-MMS. Fig.11 The method flow and Figure 8 Compared with the method flow, the first message does not include the indication information, and the fourth message sent before the first message includes the above indication information. Fig.11As shown, the method includes:

[0235] 1101. The sender sends a fourth message.

[0236] Correspondingly, the receiving end receives the fourth message. The fourth message includes indication information, and the indication information is used to indicate that the FC is constructed based on the first field in the first message, and the first field is used to indicate the type of the first message. The indication information may occupy one or more bits. For example, when the value represented by one or more bits occupied by the indication information is 1, the indication information is used to indicate that the FC is constructed based on the first field in the first message; when the value represented by the one or more bits is 0, the indication information is used to indicate that the FC is constructed in other ways, such as constructing the FC based on the PN field in the first message. The fourth message may include the Presence Control field shown in any one of Table 7-1, Table 7-2, or Table 7-3, and the Presence Control field contains the above-mentioned indication information, which will not be repeated here.

[0237] The first message may be any message sent by the sending end or the receiving end after the sending end sends the fourth message. In a possible implementation, after the sending end sends the fourth message, any control message sent by the sending end and the receiving end constructs an FC based on the first field in the control message. For example, the fourth message is any message among ADV-POLL message, ADV-RESP message, ADV-CONF message, and SOR message, and the first message is any message among POLL message, Response message, or Report message. For another example, the fourth message is ADV-POLL message, and the first message is any message among ADV-RESP message, ADV-CONF message, and SOR message. The fourth message may be any message sent by the sending end or the receiving end before the sending end sends the first message, and this application does not limit it. The indication information can be understood as being used to indicate that the FC corresponding to the control message is constructed based on the first field in each control message (e.g., the first message) sent by the sending end or the receiving end after the sending end sends the fourth message. That is to say, the fourth message may indicate the construction method of the FC corresponding to each control message sent by the transmitting end or the receiving end after the transmitting end sends the fourth message. It can be understood that each message sent by the transmitting end or the receiving end after the transmitting end sends the fourth message does not need to carry the indication information. The bits occupied by the indication information may be less than the bits occupied by the slot index field (for example, the field indicating the slot index in the SOR message). Compared with the fourth message carrying the slot index field, the fourth message carries fewer bits of indication information, and the signaling overhead is less. In addition, the indication information is included in the fourth message, and each message sent by the transmitting end after sending the fourth message does not need to carry the indication information, which can further save the signaling overhead.

[0238] 1102. The sender sends a first message.

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

[0240] 1103. The receiving end constructs FC according to the instruction information in the fourth message.

[0241] The FC constructed in step 1103 can be used to construct a Nonce for encrypting or authenticating the first message. A possible implementation of step 1103 is as follows: the receiving end constructs 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 according to the indication information in the fourth message. For example, the receiving end concatenates 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 according to the indication information to construct the FC. After constructing the FC, the receiving end can construct the Nonce corresponding to the first message based on the FC.

[0242] Fig.11 The main principles and procedures of the method Figure 8 The main principles of the method flow are similar and will not be repeated here.

[0243] In the embodiment of the present application, the indication information in the fourth message is used to indicate the construction of the FC based on the first field in the first message, which occupies fewer bits than the fourth message or other messages carrying the slot index field, and reduces the signaling overhead. In addition, each message sent by the sender after sending the fourth message does not need to carry the indication information, which can further save the signaling overhead.

[0244] Fig.12 Another communication method interaction process for UWB provided in an embodiment of the present application. Fig.12 The method shown can be applied to scenarios such as ranging, perception, positioning, and communication, for example, ranging based on NBA-MMS, perception based on NBA-MMS, and positioning based on NBA-MMS. Fig.12 The method flow and Figure 8 Compared with the method flow in , the indication information in the first message is used to indicate the order information of the list element corresponding to the first message in the message list, and construct FC. Fig.12 As shown, the method includes:

[0245] 1201. The sender sends a third message.

[0246] Correspondingly, the receiving end receives the third message. The sending end sending the third message may be: the sending end broadcasts the third message. The third message may be an ADV-CONF message or other message containing a SOR message list.

[0247] 1202. The sender generates a first message.

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

[0249] The sorting information of the list element corresponding to the first message in the message list in the message list may be: the sorting information of the list element in the message list containing 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 containing its device identifier as the list element corresponding to its message to be received and / or to be sent (e.g., the first message) in the message list. This application does not make any limitation on the form of the device identifier, and the device address is only an example.

[0250] The following is an example of the sorting information of the list elements corresponding to the first message in the message list in conjunction with the accompanying drawings. A one-to-many NBA-MMS UWB ranging process is composed of multiple one-to-one NBA-MMSUWB ranging processes in the order of execution time, that is, the initiator of each one-to-one NBA-MMS UWB ranging process is the same. Among them, a typical one-to-many NBA-MMS UWB ranging process is as mentioned above Figure 4AThe initialization process for pre-configuring one-to-many NBA-MMS UWB ranging is shown in FIG. Fig.13 shown. Fig.13 The figure is a schematic diagram of the initialization process of pre-configuring one-to-many NBA-MMS UWB ranging. Fig.13 As shown in the figure, for one-to-many NBA-MMS UWB ranging, the Initiator needs to first broadcast an ADV-POLL message to inform all responders that they need to conduct NBA-MM UWB ranging; each responder sends its ADV-RESP message to the Initiator in a competitive access manner. After successfully receiving the ADV-RESP messages of each successful competitive access, the Initiator broadcasts an ADV-CONF message to all responders. Fig.13 In the above table, SOR 0 indicates the SOR message sent by the Initiator to responder 0, SOR 1 indicates the SOR message sent by the Initiator to responder 1, SOR 2 indicates the SOR message sent by the Initiator to responder 2, Time offset to SOR 0 indicates the time when SOR 0 is sent, Time offset to SOR 1 indicates the time when SOR 1 is sent, and Timeoffset to SOR 2 indicates the time when SOR 2 is sent. For the MMS UWB measurement process of the responder, please refer to Fig. 9 In the ranging process shown, Time offset to POLL 0 (time offset for sending POLL 0 message) indicates the sending time of the POLL message in the MMS UWB measurement process of responder 0, Timeoffset to POLL 1 (time offset for sending POLL 1 message) indicates the sending time of the POLL message in the MMS UWB measurement process of responder 1, and Time offset to POLL 2 (time offset for sending POLL 2 message) indicates the sending time of the POLL message in the MMS UWB measurement process of responder 2.

[0251] The ADV-CONF message carries a SOR message list containing multiple SOR messages. The SOR message list is an example of the above message list. Each list element in the SOR message list contains a device address and the sending time of the corresponding SOR message (time offset to SOR#X). In other words, each responder can determine whether its own ADV-RESP message is successfully received by the initiator by querying whether its own device address is included in the SOR message list, that is, whether it will participate in the subsequent NBA-MMS UWB ranging process. Only the device whose ADV-RESP message is successfully received by the initiator will start the subsequent NBA-MMS UWB ranging process. The order in which the device address of the receiving end appears in the message list of the ADV-CONF message (chronological order of the responder device address appearance, CODA) can be used as the sorting information of the list element corresponding to the control message (e.g., the first message) to be sent and / or received by the receiving end in the message list in the message list. For example, after receiving the ADV-CONF message, the receiving end queries whether its own device address is included in the SOR message list in the ADV-CONF message; when the device address of the receiving end is included in the SOR message list, the ranking of the device address in the SOR message list is used as the ranking information of the list element in the message list corresponding to the control message (for example, the first message) to be sent and / or received by the receiving end.

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

[0253] Table 10

[0254]

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

[0256] Table 11

[0257]

[0258] The SOR Message Management (SMM) Presence field is used to control whether the SOR Message Management field exists. For example, when the value of the SMM Presence field is 0, it means that the SOR message list does not contain the SOR Message Management field; when the value of the SMM Presence field is 1, it means that the SOR message list contains the SOR Message Management field. The RFU field is a reserved field. The SOR Message Management field is a field used to carry and manage the SOR message list. A possible format of the SOR Message Management field is shown in Table 12:

[0259] Table 12

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

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

[0262] Table 13

[0263]

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

[0265] Table 14

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

[0267] As can be seen from Table 14, each SOR message list element includes a Time offset to SOR field and a Device address field. The Device address in the Device address field is the device address of a device, and the Time offset to SOR field indicates the sending time of the SOR message to be received by the device. For example, after the receiving end receives the ADV-CONF message, it queries whether its own device address is included in the SOR message list in the ADV-CONF message; when the device address of the receiving end is included in the SOR message list, the Timeoffset to SOR field in the list element containing the device address indicates the sending time of the SOR message to be received by the receiving end.

[0268] It should be noted that the present application does not impose any limitation on the message carrying the aforementioned SOR message list including multiple SOR messages, and it may also be other messages, and the aforementioned ADV-CONF message is only an example.

[0269] The above-mentioned first message may be a message based on a 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, when the value represented by the one or more bits occupied by the indication information is 1, the indication information is used to indicate that the FC is constructed based on the sorting information of the list element corresponding to the first message in the message list in the message list; when the value represented by the one or more bits is 0, the indication information is used to indicate that the FC is constructed in other ways, for example, the FC is constructed based on the slot index, round index and block index carried by the first message. When the first message does not carry an index among the slot index, round index and block index, the index is 0 by default. Alternatively, when the value of the indication information (i.e., the value represented by the one or more bits occupied by the indication information) is 0, the indication information is used to indicate that the FC is constructed based on the sorting information of the list element corresponding to the first message in the message list in the message list; when the value of the indication information is 1, the indication information is used to indicate that the FC is constructed in other ways. The following takes the first message as an example of a SOR message to introduce a possible format of the first message. Table 15 is an example of the PSDU format of the SOR message.

[0270] Table 15

[0271]

[0272]

[0273] In Table 15, the fields such as Message ID, Security Enable, Address, Secured Payload, MIC, etc. are consistent with the fields in the aforementioned Table 3 and are not repeated 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 includes the above-mentioned indication information. The Presence Control field may occupy 1 bit, 3 bits, or one byte. This application does not limit the position and size of the Presence Control field, nor does it limit the name of the Presence Control field. In addition, the Presence Control field may be a new field or may be included in an existing field. It should be understood that Table 15 is only an example of the PSDU format of the SOR message, and the position and size of each field in Table 15 are not limited. Tables 16-1, 16-2, 16-3 and 16-4 show four examples of the PresenceControl field.

[0274] Table 16-1

[0275] 1 Presence Control

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

[0277] Table 16-2

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

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

[0280] Table 16-3

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

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

[0283] Table 16-4

[0284]

[0285]

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

[0287] 1203. The sender sends a first message.

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

[0289] In a possible implementation, the transmitting end also performs the following operations: sending a second message, the second message including a second field for indicating the deadline for receiving the SOR message. Accordingly, the receiving end receives the second message. The receiving end may stop monitoring the SOR message after the deadline for receiving the SOR message indicated by the second field, thereby avoiding the increase in energy consumption caused by waiting for a long time to monitor the SOR message. The second message also includes a field for indicating whether the second field exists. The second message is a message sent by the transmitting end before sending the SOR message (for example, the first message). The second message can be an ADV-CONF message or other message, which is not limited in this application.

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

[0291] In a possible implementation, after receiving the third message, the receiving end queries whether its own device address is included in the message list in the third message; when the device address of the receiving end is included in the message list, the sorting information (e.g., CODA values) of the device address in the message list is used as the sorting information of the list element corresponding to the message (including the first message) to be sent and / or received by the receiving end in the message list. The sorting information of the device address in the message list may be the sorting of the list element containing the device address in the message list. The message to be sent and / or received by the receiving end may include: a SOR message, a POLL message, a Response message, or a Report message. The receiving end may store the sorting information of its device address in the message list so as to use the sorting information as the sorting information of the list element corresponding to the message (including the first message) to be sent and / or received in the message list. After receiving the first message, the receiving end may obtain the stored sorting information and use it as the sorting information of the list element corresponding to the first message in the message list. The receiving end obtains the sorting information of the list element corresponding to the first message in the message list, which can be understood as: the receiving end obtains the sorting information currently stored. After storing the sorting information of its device address in the message list, if the receiving end receives a new third message (new ADV-CONF message), it can update its stored sequence information.

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

[0293] A possible implementation of step 1205 is as follows: According to the indication information in the first message, based on the measurement time slot identifier corresponding to the above-mentioned first message, the above-mentioned sorting information and the measurement block identifier corresponding to the above-mentioned first message, construct FC. For example, the receiving end splices the measurement time slot identifier corresponding to the first message (such as slot index), the above-mentioned sorting information and the measurement block identifier corresponding to the first message (such as block index) to obtain FC. In this example, the FC construction method is: FC=slot index||CODA values||block index. "||" represents the splicing operation. CODA values ​​(i.e., sorting information) can be a numerical value indicating the sorting of the list element corresponding to the first message in the message list in the above-mentioned message list, such as #1, #2, #3, etc. After constructing FC, the receiving end can construct Nonce based on the FC. The Nonce is used for encryption or authentication of the first message. Table 17 and Table 18 are examples of two types of Nonces.

[0294] Table 17

[0295]

[0296] The CODAvalues ​​field in Table 17 contains the above-mentioned sorting information. The meanings of other fields in Table 17 can refer to the meanings of the fields in Table 5. The Slot Index field, CODAvalues ​​field and Block Index field constitute FC.

[0297] Table 18

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

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

[0300] Fig.12 The method flow can be understood as: based on the measurement time slot identifier corresponding to the control message (i.e., the first message), the sorting information of the list element corresponding to the control message in the message list in the message list, and the measurement block identifier corresponding to the control message, construct the FC corresponding to the control message. The sorting information of the list element corresponding to the control message in the message list in each sub-process (i.e., the one-to-one NBA-MMS UWB ranging process) in the one-to-many NBA-MMS UWB ranging process reflects the execution order of each sub-process in the one-to-many NBA-MMS UWB ranging process. Refer to Fig.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. The ordering information of the list elements corresponding to the control messages (such as POLL messages, Response messages, and Report messages) in the one-to-one MMS UWB ranging process in which responder 0 participates is #0 in the message list, the ordering information of the list elements corresponding to the control messages in the one-to-one MMS UWB ranging process in which responder 1 participates is #1 in the message list, and the ordering information of the list elements corresponding to the control messages in the one-to-one MMS UWB ranging process in which responder 2 participates is #2 in the message list. Therefore, Fig.12 The method flow in can also be understood as: constructing FC by utilizing the execution sequence of each sub-process in the one-to-many NBA-MMS UWB ranging process.

[0301] In the embodiment of the present application, FC is constructed based on the sorting information of the list element corresponding to the first message in the message list, thereby avoiding the explicit carrying of Round Index and saving signaling overhead.

[0302] Fig.14 Another communication method interaction process for UWB provided in an embodiment of the present application. Fig.14 The method shown can be applied to scenarios such as ranging, perception, positioning, and communication, for example, ranging based on NBA-MMS, perception based on NBA-MMS, and positioning based on NBA-MMS. Fig.14 The method flow and Fig.12 Compared with the method flow, the first message does not include the indication information, and the receiving end defaults to the sorting information of the list element corresponding to the first message in the message list in the message list, and constructs FC. Fig.14 As shown, the method includes:

[0303] 1401. The sender sends a third message.

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

[0305] 1402. The sender sends a first message.

[0306] Correspondingly, the receiving end receives the first message. The first message may be any one of a SOR message, a POLL message, a Response message, or a Report message.

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

[0308] Step 1403 may refer to step 1204 .

[0309] 1404. The receiving end constructs FC according to the sorting information of the list elements corresponding to the first message in the message list.

[0310] A possible implementation of step 1404 is as follows: construct FC according to the measurement time slot identifier corresponding to the first message, the above-mentioned sorting information, and the measurement block identifier corresponding to the first message. For example, the receiving end concatenates the measurement time slot identifier corresponding to the first message (e.g., slot index), the above-mentioned sorting information, and the measurement block identifier corresponding to the first message (e.g., block index) to obtain FC. After receiving the third message, the receiving end has the same sorting information in the message list for the list elements corresponding to the messages sent or received (belonging to the same one-to-one NBA-MMS UWB ranging process). Since the measurement time slot identifiers corresponding to the messages belonging to the same one-to-one NBA-MMS UWB ranging process are different, the FCs corresponding to the messages are different.

[0311] In the embodiment of the present application, FC is constructed based on the sorting information of the list elements corresponding to the first message in the message list, thereby avoiding the need to display the Round Index and saving signaling overhead. In addition, since the first message does not contain the indication information, Fig.14 The scheme and Fig.12 Compared with the scheme in , the signaling overhead is less.

[0312] Fig.15 Another communication method interaction process for UWB provided in an embodiment of the present application. Fig.15 The method flow and Fig.12 Compared with the method flow, the first message does not include the instruction information for indicating that the FC is constructed based on the sorting information of the list elements corresponding to the first message in the message list, and the fourth message sent before the first message includes the instruction information. Fig.15 As shown, the method includes:

[0313] 1501. The sender sends a fourth message.

[0314] Correspondingly, the receiving end receives the fourth message. The fourth message includes indication information, and the indication information is used to indicate that the FC is constructed based on the sorting information of the list element corresponding to the first message in the message list in the message list. The fourth message can be an ADV-POLL message, an ADV-RESP message, a high-level signaling or other message, which is not limited here. The first message can be any one of a SOR message, a POLL message, a Response message, or a Report message. Alternatively, the indication information is used to indicate that the receiving end constructs the FC based on the sorting information of the list elements corresponding to the list in the message list in the message list of each control message received and / or sent after the sending end sends the third message. The constructed FC is used for encryption or authentication of each control message. The third message can be an ADV-CONF message. After the sending end sends the third message, the control messages received and / or sent by the receiving end include a SOR message, a POLL message, a Response message, and a Report.

[0315] 1502. The sender sends a third message.

[0316] Correspondingly, the receiving end receives the third message. Step 1502 may refer to step 1201 .

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

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

[0319] 1504. The sender sends a first message.

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

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

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

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

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

[0325] In the embodiment of the present application, FC is constructed based on the sorting information of the list element corresponding to the first message in the message list, thereby avoiding the explicit carrying of Round Index and saving signaling overhead.

[0326] The structure of a communication device that can implement the communication method for UWB provided in the embodiments of the present application is described below in conjunction with the accompanying drawings.

[0327] Fig.16 A schematic diagram of the structure of a communication device 1600 provided in an embodiment of the present application. The communication device 1600 may correspond to the functions or steps implemented by the transmitting end in the above-mentioned various method embodiments, and may also correspond to the functions or steps implemented by the receiving end in the above-mentioned various method embodiments. The communication device may include a processing module 1610 and a transceiver module 1620. In a possible implementation, a storage unit may also be included, which may be used to store instructions (codes or programs) 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 may read the instructions (codes or programs) and / or data in the storage unit to implement the corresponding method. The above-mentioned units may be independently arranged or partially or fully integrated. For example, the transceiver module 1620 may include a sending module and a receiving module. The sending 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.

[0328] In some possible implementations, the communication device 1600 can implement the behaviors and functions of the transmitting end in the above method embodiments. For example, the communication device 1600 can be a transmitting end, or a component (such as a chip or circuit) used in the transmitting end. The transceiver module 1620 can be used to perform Figure 8 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 The processing module 1610 is used to perform all receiving or sending operations performed by the transmitting end in the embodiment of Figure 8 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 In the embodiment of the present invention, all operations performed by the transmitting end except the sending and receiving operations, such as Figure 8Step 801 in the embodiment shown.

[0329] In some possible implementations, the communication device 1600 can implement the behaviors and functions of the receiving end in the above method embodiments. For example, the communication device 1600 can be a receiving end, or a component (such as a chip or circuit) used in the receiving end. The transceiver module 1620 can be used to perform Figure 8 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 The processing module 1610 is used to perform all receiving or sending operations performed by the receiving end in the embodiment of Figure 8 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 All operations except the sending and receiving operations performed by the receiving end in the embodiment.

[0330] Fig.17 A schematic diagram of the structure of another communication device 170 provided in an embodiment of the present application. Fig.17 The communication device in the communication method may be the above-mentioned sending end or the above-mentioned receiving end.

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

[0332] In some embodiments of the present application, the processor 1710 and the transceiver 1720 may be used to execute functions or operations performed by the transmitting end. The transceiver 1720 may be used to execute Figure 8 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 The processor 1710 is used to perform all receiving or sending operations performed by the transmitting end in the embodiment of Figure 8 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 All operations performed by the transmitting end except the sending and receiving operations in the embodiment.

[0333] In some embodiments of the present application, the processor 1710 and the transceiver 1720 may be used to execute the functions or operations executed by the receiving end. The transceiver 1720 is used to execute Figure 8 , Fig.10 , Fig.11 , Fig.12, Fig.14 , Fig.15 The processor 1710 is used to perform all receiving or sending operations performed by the receiving end in the embodiment of Figure 8 , Fig.10 , Fig.11 , Fig.12 , Fig.14 , Fig.15 All operations except the sending and receiving operations performed by the receiving end in the embodiment.

[0334] The transceiver 1720 is used to communicate with other devices / apparatuses via a transmission medium. The processor 1710 uses the transceiver 1720 to send and receive data and / or signaling, and is used to implement the method in the above method embodiment. The processor 1710 can implement the functions of the processing module 1610, and the transceiver 1720 can implement the functions of the transceiver module 1620.

[0335] Optionally, the transceiver 1720 may include a radio frequency circuit and an antenna. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, a display screen, a keyboard, etc., are mainly used to receive data input by a user and output data to the user.

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

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

[0338] In another implementation, the above-mentioned RF circuit and antenna can be arranged independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna can be arranged independently of the communication device in a remote manner.

[0339] The specific connection medium between the transceiver 1720, the processor 1710 and the memory 1730 is not limited in the embodiment of the present application. Fig.17 The memory 1730, the processor 1710 and the transceiver 1720 are connected via a bus 1740. Fig.17 The connection between other components is only for illustration and is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.17 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0340] In the 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, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0341] Fig.18 FIG. 1 is a schematic diagram of the structure of another communication device 180 provided in an embodiment of the present application. Fig.18 As shown, Fig.18 The communication device shown includes a logic circuit 1801 and an interface 1802 . Fig.16 The processing module 1610 in can be implemented by a logic circuit 1801. Fig.16 The transceiver module 1620 in the embodiment can be implemented with an interface 1802. The logic circuit 1801 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 1802 can be a communication interface, an input and output interface, etc. In the embodiment of the present application, the logic circuit and the interface can also be coupled to each other. The embodiment of the present application does not limit the specific connection method of the logic circuit and the interface.

[0342] In some embodiments of the present application, the logic circuit and interface may be used to execute the functions or operations performed by the above-mentioned transmitting end, etc.

[0343] In some embodiments of the present application, the logic circuit and interface may be used to execute the functions or operations performed by the above-mentioned receiving end, etc.

[0344] The present application also provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed on a computer, the computer executes the method of the above embodiment.

[0345] The present application also provides a computer program product, which includes instructions or a computer program. When the instructions or the computer program are run on a computer, the method in the above embodiment is executed.

[0346] The present application also provides a communication system, comprising the above-mentioned transmitting end and the above-mentioned receiving end.

[0347] The present application also provides a chip, which includes: a communication interface and a processor; the communication interface is used for sending and receiving signals of the above-mentioned chip; the processor is used to execute computer program instructions so that a communication device including the above-mentioned chip executes the method in the above-mentioned embodiment.

[0348] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The above computer program product includes one or more computer programs or instructions. When the above computer program or instruction is loaded and executed on a computer, the above process or function of the embodiment of the present application is executed in whole or in part. The above computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The above computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the above computer program or instruction may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means. The above computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The above available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it may also be an optical medium, such as a digital video disc; it may also be a semiconductor medium, such as a solid-state hard disk. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0349] In the various embodiments of the present application, unless otherwise specified or provided in a logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

Claims

1. A communication method for ultra-wideband UWB, characterized in that: include: Generate a confirmation notification ADV-CONF message, wherein the ADV-CONF message includes a ranging initiation SOR message list, each SOR message list element includes an address of a receiving end and a ranging initiation SOR time offset corresponding to the receiving end, and the SOR time offset corresponding to the receiving end is used to indicate a sending time of a SOR message to be received by the receiving end; Send the ADV-CONF message.

2. The method according to claim 1, characterized in that The method further comprises: The SOR message is sent to the receiving end, where the SOR message indicates a time offset for the receiving end to send a polling POLL message.

3. A communication device, characterized in that: The device comprises a processor, 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 performs the method according to claim 1 or 2.

4. A chip, characterized in that: include: A communication interface, used for sending and receiving signals of the chip; as well as A processor, configured to execute computer program instructions so that a communication device including the chip executes the method according to claim 1 or 2.

5. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed, the computer executes the method according to claim 1 or 2.

Images