UWB communication methods and related products

Abstract

This application discloses a communication method and related products for UWB. This application may be applied to UWB-based wireless personal area network systems, sensing systems, positioning systems, ranging systems, or communication systems, and may be further applied to wireless local area network systems that support 802.11 series protocols such as the next-generation Wi-Fi protocol of IEEE 802.11 ax, e.g., 802.11 be or Wi-Fi 7, and the next-generation protocol of 802.11 be, e.g., Wi-Fi 8. The method includes the steps of: generating a first message, the first message comprising a first bitmap, the i-th bit of the first bitmap corresponding to an i-th UWB device, and if the i-th bit is set to a specified value, the i-th bit indicating the position in a first DPL of parameter configuration information for the i-th UWB device; and transmitting the first message. The first bitmap indicates the location of the UWB device parameter configuration information within the DPL to reduce the signaling overhead for updating list elements.

Description

Technical Field

[0001] This application claims the priority of Chinese Patent Application No. 202310262436.7, titled "COMMUNICATION METHOD FOR UWB AND RELATED PRODUCT", filed with the China National Intellectual Property Administration on March 9, 2023, and Chinese Patent Application No. 202310491082.3, titled "COMMUNICATION METHOD FOR UWB AND RELATED PRODUCT", filed with the China National Intellectual Property Administration on April 28, 2023, both of which are hereby incorporated by reference in their entirety.

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

Background Art

[0003] Ultra-wideband (UWB) technology is a wireless communication and sensing / ranging technology in which non-sinusoidal narrow impulses at the nanosecond level are used for signal transmission. Therefore, ultra-wideband occupies a wide frequency spectrum range. Due to the narrow impulses and extremely low radiation spectrum density, UWB systems have advantages such as strong multipath resolution, low power consumption, and high confidentiality, and have attracted wide attention in the industry.

[0004] Since the Federal Communications Commission approved the entry of UWB technology into the consumer market in 2002, globally renowned corporations, research institutions, and standardization bodies have actively engaged in the research, development, and standardization of ultra-wideband wireless communication technology. The Institute of Electrical and Electronics Engineers (IEEE) incorporated UWB technology into the IEEE 802 series of wireless standards and released the UWB-based wireless personal area network (WPAN) standard IEEE 802.15.4a and its advanced version, IEEE 802.15.4z. Currently, the next-generation UWB WPAN standard, IEEE 802.15.4ab, is being considered. UWB is expected to be comprehensively upgraded in the IEEE 802.15.4ab standard.

[0005] Scheduling information elements (IEs) for UWB applications (such as ranging, sensing, positioning, and communication) are used to schedule one or more UWB devices to implement the UWB application. Currently, existing scheduling information elements for UWB applications typically have high signaling overhead. Therefore, an extended scheduling IE design for UWB applications needs to be provided to reduce the signaling overhead of scheduling information elements for UWB applications. [Overview of the project]

[0006] Embodiments of this application disclose a communication method and related products for UWB to reduce the signaling overhead of scheduling information elements for UWB applications. [Means for solving the problem]

[0007] According to a first aspect, one embodiment of the present application provides a communication method for UWB. The method includes the steps of: generating a first message, the first message comprising a first bitmap, the first bitmap comprising N bits, the i-th bit of the first bitmap corresponding to the i-th UWB device, and if the i-th bit is set to a specified value, the i-th bit indicating the location of the parameter configuration information of the i-th UWB device in a first device parameters list (DPL), where i is between 1 and N, and N is an integer greater than 0, and the first DPL is included in the first message; and transmitting the first message.

[0008] In the embodiments of this application, the first bitmap indicates the location of the parameter configuration information of the UWB device within the DPL, so the device address in the list element can be omitted, and the signaling overhead for updating the list element can be reduced.

[0009] In possible implementations, prior to the step of sending the first message, the method further includes the step of sending a second message. The second message includes a second DPL, which includes one or more sequentially arranged list elements, any list element in the second DPL includes the address of the UWB device corresponding to any list element, and the sequentially arranged i-th list element in the second DPL includes parameter configuration information for the corresponding i-th UWB device.

[0010] In this implementation, a second message is sent, and as a result, the receiver determines, based on the second message, that the i-th list element sequentially placed within the second DPL contains the parameter configuration information for the corresponding i-th UWB device.

[0011] According to a second aspect, one embodiment of the present application provides another communication method for UWB. The method includes the steps of: receiving a first message, the first message comprising a first bitmap, the first bitmap comprising N bits, the i-th bit of the first bitmap corresponding to an i-th UWB device; and determining the location of parameter configuration information for the i-th UWB device in a first device parameter list DPL, where i is between 1 and N, N is an integer greater than 0, and the first DPL is included in the first message.

[0012] In the embodiments of this application, when the i-th bit is set to a specified value, the position of the parameter configuration information for the i-th UWB device in the first DPL is determined, so that the device address of the list element can be omitted, and the signaling overhead for updating the list element can be reduced.

[0013] In possible implementations, the first DPL contains multiple sequentially arranged list elements. The step of determining the location of the parameter configuration information for the i-th UWB device in the first device parameter list DPL, when the i-th bit is set to a specified value, includes determining that the f-th list element in the first DPL contains the parameter configuration information for the i-th UWB device, when the i-th bit is the f-th bit in the first bitmap, which is sequentially arranged and set to a specified value, where F is an integer greater than 0.

[0014] In this implementation, based on the first bitmap, it is determined that the fth list element in the first DPL contains the parameter configuration information for the ith UWB device. As a result, the device address in the list element is omitted, reducing the signaling overhead required to update the list element.

[0015] In a possible implementation, before receiving a first message, the method further includes the steps of: receiving a second message, the second message comprising a second DPL, the second DPL comprising one or more sequentially arranged list elements, any list element in the second DPL comprising the address of a UWB device corresponding to any list element; and determining, based on the second message, that the sequentially arranged i-th list element in the second DPL comprises parameter configuration information for the corresponding i-th UWB device, where i is an integer greater than 0. The step of determining the location of the parameter configuration information for the i-th UWB device in the first device parameter list DPL when the i-th bit is set to a specified value comprises the steps of: determining that the i-th bit in the first bitmap corresponds to the i-th UWB device; and determining the location of the parameter configuration information for the i-th UWB device in the first DPL when the i-th bit is set to a specified value.

[0016] In this implementation, when it is determined that the i-th list element, sequentially placed within the second DPL, contains the parameter configuration information for the corresponding i-th UWB device, it is determined that the i-th bit in the first bitmap corresponds to the i-th UWB device.

[0017] In possible implementations of the first or second embodiment, the first DPL includes one or more sequentially arranged list elements, where the i-th bit is the F-th bit in the first bitmap, which is sequentially arranged and set to a specified value, indicating that the F-th list element of the first DPL contains parameter configuration information for the i-th UWB device, where F is an integer greater than 0.

[0018] In this implementation, based on the first bitmap, it is determined that the fth list element in the first DPL contains the parameter configuration information for the ith UWB device. As a result, the device address in the list element is omitted, reducing the signaling overhead required to update the list element.

[0019] In possible implementations of the first or second embodiment, the first message further includes a first field, the first field indicating that the first bitmap is used to identify the location of the parameter configuration information of the UWB device in the first DPL.

[0020] In this implementation, the first field indicates that the first bitmap is used to identify the location of the UWB device parameter configuration information within the first DPL, and as a result, the receiver knows the location of the UWB device parameter configuration information within the first DPL, identified by the first bitmap, based on the first field.

[0021] In possible implementations of the first or second embodiment, the first message further includes a field indicating the length of the first bitmap.

[0022] In this implementation, the first message further includes a field indicating the length of the first bitmap. Therefore, the receiver knows the length of the first bitmap and parses it correctly.

[0023] In possible implementations of the first or second embodiment, the first message is included in the measurement start message or the polling / start POLL message.

[0024] According to a third aspect, one embodiment of the present application provides another communication method for UWB. The method includes the steps of: generating a first message, the first message comprising a first list element, the first list element comprising parameter configuration information of an i-th UWB device and an identifier of the i-th UWB device, the identifier indicating the order of the list element of the i-th UWB device in a second message within a device parameter list DPL, the second message being information to be sent before the first message is sent, the second message comprising the address of the i-th UWB device, the DPL being included in the second message; and sending the first message. The identifier of the i-th UWB device occupies less than two octets. The identifier of the i-th UWB device is used to identify the i-th UWB device.

[0025] In embodiments of this application, a first message is transmitted. A first list element in the first message includes parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device. The identifier for the i-th UWB device is used such that the device identifier in the list element is changed from a 2-octet or 8-octet device address to an identifier occupying less than 2 octets. This reduces signaling consumption.

[0026] According to a fourth aspect, an embodiment of the present application provides another communication method for UWB. The method includes receiving a first message, where the first message includes a first list element, the first list element includes parameter configuration information of the i-th UWB device and an identifier of the i-th UWB device, the identifier indicates the order of the list element of the i-th UWB device in the second message within the device parameter list DPL, the second message is information transmitted before the first message is transmitted, the second message includes an address of the i-th UWB device, and DPL includes the steps included in the second message, and determining the first list element based on the identifier. The identifier of the i-th UWB device occupies less than 2 octets. The identifier of the i-th UWB device is used to identify the i-th UWB device.

[0027] In an embodiment of the present application, the list element in the first message including the parameter configuration information of the UWB device is determined based on the identifier of the i-th UWB device. The device identifier in the list element is changed from a 2-octet or 8-octet device address to an identifier that occupies less than 2 octets. This reduces signaling consumption.

[0028] In a possible implementation, before receiving the first message, the method further includes receiving a second message, and determining the order of the list element of the i-th UWB device in the second message within DPL, and recording the order as an identifier.

[0029] In this implementation, the identifier of the i-th UWB device is determined and recorded, and then the i-th UWB device is identified using this identifier.

[0030] In a possible implementation of the first aspect or the second aspect, the identifier occupies less than 2 octets.

[0031] In possible implementations of the first or second embodiment, the first message further includes a first field, the first field indicating that an identifier for the i-th UWB device is used to identify the location of the parameter configuration information for the i-th UWB device within the first DPL.

[0032] In this implementation, the first field indicates that the identifier of the i-th UWB device is used to identify the location of the parameter configuration information of the i-th UWB device within the first DPL. Therefore, based on the first field, the receiver knows the location of the parameter configuration information in the first DPL, and the location of the parameter configuration information of the i-th UWB device is identified by the identifier of the i-th UWB device.

[0033] In possible implementations of the first or second embodiment, the first message is included in the measurement start message or the polling / start POLL message. For example, the measurement start message is the start-of-ranging (SOR) message.

[0034] According to a fifth aspect, one embodiment of the present application provides another communication method for UWB. The method includes the step of a first device sending a first message, the first message indicating the expiration of a contention-based access period (CAP), the CAP being the period during which the sending of a response message to the first message is permitted. The first device receives second messages from a plurality of second devices, each of the plurality of second messages including second parameter configuration information for the corresponding second device. The first device sends a third message, the third message including first parameter configuration information for some or all of the plurality of second devices and information indicating when a fourth message is sent, the fourth message being used to update the first parameter configuration information of at least one of the plurality of second devices.

[0035] In embodiments of this application, the first device transmits a first message. The first message indicates the expiration date of the CAP, and as a result, the target second device transmits a second message before the expiration date. This can reduce the duration of waiting to receive the second message in order to reduce energy consumption. The first device transmits a third message. The third message includes information indicating when a fourth message will be transmitted. This can reduce the duration of waiting for the target second device to receive an updated SOR message, in order to reduce energy consumption.

[0036] In possible implementations, the first message includes a first field indicating the expiration date of the CAP.

[0037] In possible implementations, the first message further includes information indicating the start time of CAP.

[0038] In this implementation, the first message further includes information indicating the CAP start time, so the responder knows the CAP start time. This can reduce the responder's power consumption.

[0039] In a possible implementation, the third message includes a second field, which indicates that the third message contains information indicating when the fourth message is sent.

[0040] In this implementation, the target's second device can know that the third message contains information indicating when the fourth message is sent.

[0041] In possible implementations, the third message further includes the addresses of some or all of the second devices.

[0042] In possible implementations, the method further includes the step of sending a fourth message. The fourth message includes a first bitmap, which contains N bits, the i-th bit of the first bitmap corresponding to the i-th UWB device, and if the i-th bit is set to a specified value, the i-th bit indicates the position of the first parameter configuration information of the i-th UWB device in a first device parameter list DPL, where i is between 1 and N, and N is an integer greater than 0, and the first DPL is included in the fourth message.

[0043] In this implementation, the fourth message includes the first bitmap, which indicates the location of the UWB device parameter configuration information within the DPL. Therefore, the device address in the list element can be omitted, reducing the signaling overhead for updating the list element.

[0044] In possible implementations, the first DPL contains multiple sequentially arranged list elements, where the i-th bit is the F-th bit in the first bitmap, which is sequentially arranged and set to a specified value. The i-th bit indicates that the F-th list element of the first DPL contains the first parameter configuration information for the i-th UWB device, where F is an integer greater than 0.

[0045] In this implementation, the first bitmap indicates the location of the UWB device's parameter configuration information within the DPL, thereby omitting the device address in the list elements and reducing the signaling overhead of updating the list elements.

[0046] In possible implementations, the fourth message further includes a third field, which indicates the use of a first bitmap to identify the location of the first parameter configuration information of the UWB device within the first DPL.

[0047] In this implementation, the third field indicates that the first bitmap is used to identify the location of the UWB device parameter configuration information within the first DPL, and as a result, the receiver knows the location of the UWB device parameter configuration information within the first DPL, identified by the first bitmap, based on the third field.

[0048] In possible implementations, the fourth message further includes a field indicating the length of the first bitmap.

[0049] In a possible implementation, the method further includes the step of sending a fourth message. The fourth message includes a first list element, the first list element includes first parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the i-th UWB device list element in the third message within the device parameter list DPL, the DPL being included in the third message, and the i-th UWB device being one of several second devices.

[0050] In this implementation, a fourth message is sent. The first list element in the fourth message contains parameter configuration information for the i-th UWB device and the identifier of the i-th UWB device. The device identifier in the list element is changed from a 2-octet or 8-octet device address to an identifier occupying less than 2 octets. This reduces signaling consumption.

[0051] In possible implementations, identifiers occupy less than two octets.

[0052] In possible implementations, the fourth message further includes a fourth field, which indicates that the identifier of the i-th UWB device is used to identify the location of the i-th UWB device's first parameter configuration information within the first DPL.

[0053] In this implementation, the fourth field indicates that the identifier of the i-th UWB device is used to identify the location of the parameter configuration information of the i-th UWB device within the first DPL. Therefore, based on the fourth field, the receiver knows the location of the parameter configuration information within the first DPL, and the location of the parameter configuration information of the i-th UWB device is identified by the identifier of the i-th UWB device.

[0054] In possible implementations, the fourth message is included in the measurement start message or the polling / start POLL message.

[0055] According to a sixth aspect, one embodiment of the present application provides another communication method for UWB. The method includes the steps of: a target second device receiving a first message, the first message indicating the expiration date of a CAP, where the CAP is a period during which the transmission of a response message to the first message is permitted; transmitting a second message before the expiration date, the second message including second parameter configuration information of the target second device; and receiving a third message, the third message including first parameter configuration information of one or more second devices and information indicating when a fourth message is transmitted, the fourth message being used to update the first parameter configuration information of at least one of the one or more second devices.

[0056] In the embodiments of this application, a third message is received. The third message includes first parameter configuration information of one or more second devices and information indicating when a fourth message is transmitted. This allows the target second device to reduce the duration for which the receiver is able to receive the fourth message, in order to reduce energy consumption.

[0057] In possible implementations, the first message includes a first field indicating the expiration date of the CAP.

[0058] In possible implementations, the first message further includes information indicating the start time of CAP.

[0059] In a possible implementation, the third message includes a second field, which indicates that the third message contains information indicating when the fourth message is sent.

[0060] In possible implementations, the third message further includes the addresses of some or all of the second devices.

[0061] In a possible implementation, the method further includes the steps of: receiving a fourth message, the fourth message comprising a first bitmap, the first bitmap comprising N bits, the i-th bit of the first bitmap corresponding to the i-th UWB device; and determining the location of the first parameter configuration information for the i-th UWB device in a first device parameter list DPL, if the i-th bit is set to a specified value, where i is between 1 and N, N is an integer greater than 0, and the first DPL is included in the fourth message.

[0062] In this implementation, if the i-th bit is set to a specified value, the location of the first parameter configuration information for the i-th UWB device in the first DPL is determined, so the device address of the list element can be omitted, reducing the signaling overhead for updating the list element.

[0063] In possible implementations, the first DPL contains multiple sequentially arranged list elements, where the i-th bit is the F-th bit in the first bitmap, which is sequentially arranged and set to a specified value. The i-th bit indicates that the F-th list element of the first DPL contains the first parameter configuration information for the i-th UWB device, where F is an integer greater than 0.

[0064] In possible implementations, the fourth message further includes a third field, which indicates the use of a first bitmap to identify the location of the first parameter configuration information of the UWB device within the first DPL.

[0065] In possible implementations, the fourth message further includes a field indicating the length of the first bitmap.

[0066] In possible implementations, the first DPL contains multiple sequentially arranged list elements. The step of determining the location of the first parameter configuration information for the i-th UWB device in the first device parameter list (DPL) when the i-th bit is set to a specified value includes determining that the f-th list element in the first DPL contains the first parameter configuration information for the i-th UWB device when the i-th bit is the f-th bit sequentially arranged in the first bitmap and set to a specified value, where F is an integer greater than 0.

[0067] In this implementation, device addresses within list elements are omitted, reducing the signaling overhead required to update list elements.

[0068] In a possible implementation, the third message includes a second DPL, the second DPL includes a number of sequentially arranged list elements, and any list element in the second DPL includes the address of a second device corresponding to any list element. The method further includes determining, based on the third message, that the i-th sequentially arranged list element in the second DPL corresponds to the i-th UWB device, where i is an integer greater than 0. If the i-th bit is set to a specified value, the step of determining the location of the first parameter configuration information for the i-th UWB device in the first device parameter list (DPL) includes determining that the i-th bit of the first bitmap corresponds to the i-th UWB device, and if the i-th bit is set to a specified value, the step of determining the location of the first parameter configuration information for the i-th UWB device in the first DPL.

[0069] In this implementation, when it is determined that the i-th list element, sequentially placed within the second DPL, contains the parameter configuration information for the corresponding i-th UWB device, it is determined that the i-th bit in the first bitmap corresponds to the i-th UWB device.

[0070] In one possible implementation, the method includes the steps of receiving a fourth message, wherein the fourth message contains a first list element, the first list element contains first parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the list element for the i-th UWB device contained in the third message within the device parameter list DPL in the third message, and the i-th UWB device is one of a plurality of second devices; and further the steps of determining the first list element based on the identifier.

[0071] In this implementation, the list element containing the parameter configuration information of the UWB device within the first message is determined based on the identifier of the i-th UWB device. The device identifier in the list element is changed from a 2-octet or 8-octet device address to an identifier occupying less than 2 octets. This reduces signaling consumption.

[0072] In possible implementations, identifiers occupy less than two octets.

[0073] In possible implementations, the fourth message further includes a fourth field, which indicates that the identifier of the i-th UWB device is used to identify the location of the i-th UWB device's first parameter configuration information within the first DPL.

[0074] In possible implementations, the method further includes the step of determining the order in the DPL of the list elements of the i-th UWB device in the third message and recording that order as an identifier.

[0075] In this implementation, the identifier of the i-th UWB device is determined and recorded, and then this identifier is used to identify the i-th UWB device.

[0076] In possible implementations, the fourth message is included in the measurement start message or the polling / start POLL message.

[0077] According to a seventh aspect, one embodiment of the present application provides another communication method for UWB. The method includes: a step of a first device transmitting a first message, the first message indicating the expiration date of a CAP, where CAP is the period during which the transmission of a response message to the first message is permitted; a step of receiving second messages from a plurality of second devices, each of the plurality of second messages including second parameter configuration information of the corresponding second device; and a step of transmitting a third message, the third message carrying information indicating when a fourth message is transmitted, the fourth message being transmitted to some or all of the plurality of second devices.

[0078] In embodiments of this application, the first device transmits a first message. The first message indicates the expiration date of the CAP, and as a result, the target second device transmits a second message before the expiration date. This can reduce the duration for which the second message is received in order to reduce energy consumption. The first device transmits a third message. The third message includes information indicating when a fourth message is transmitted. This can reduce the duration for which the target second device allows the receiver to receive an updated SOR message, in order to reduce energy consumption.

[0079] In a possible implementation, the first message includes a first field, the first field indicating that the first message contains information indicating the expiration date of the CAP.

[0080] In possible implementations, the first message further includes information indicating the start time of CAP.

[0081] In a possible implementation, the third message includes a second field, which indicates that the third message contains information indicating when the fourth message is sent.

[0082] According to the eighth aspect, one embodiment of the present application provides another communication method for UWB. The method includes the steps of: a target second device receiving a first message, the first message indicating an expiration date of a CAP, where the CAP is a period during which the transmission of a response message to the first message is permitted; transmitting a second message to the first device before the expiration date, the second message including second parameter configuration information of the target second device; and receiving a third message from the first device, the third message carrying information indicating when a fourth message will be transmitted, the fourth message being transmitted to some or all of the devices transmitting a response message to the first message to the first device before the expiration date.

[0083] In the embodiments of this application, a third message is received. The third message includes first parameter configuration information of one or more second devices and information indicating when a fourth message is transmitted. This allows the target second device to reduce the duration for which the receiver is able to receive the fourth message, in order to reduce energy consumption.

[0084] In a possible implementation, the first message includes a first field, the first field indicating that the first message contains information indicating the expiration date of the CAP.

[0085] In possible implementations, the first message further includes information indicating the start time of CAP.

[0086] In a possible implementation, the third message includes a second field, which indicates that the third message contains information indicating when the fourth message is sent.

[0087] In possible implementations, the fourth message indicates the end of the measurement for the current round or the next round.

[0088] In possible implementations, the fourth message indicates the termination of measurement for one or more measurement rounds. In other words, the fourth message indicates the termination of measurement for one or more rounds of measurement. For example, the fourth message indicates the termination of measurement for multiple measurement rounds, which may or may not be temporally adjacent. In another example, the fourth message indicates the termination of measurement for multiple measurement rounds, which may be located in the same measurement block or in different measurement blocks. A single measurement block contains one or more measurement rounds. Temporarily adjacent may mean that multiple measurement rounds in the same measurement block are adjacent, or that one or more trailing measurement rounds in a previous measurement block are adjacent to one or more leading measurement rounds in the current measurement block.

[0089] In this implementation, the fourth message indicates that one or more measurement rounds will be terminated to reduce resource overhead and unnecessary measurements. Furthermore, the time resources corresponding to the terminated measurement rounds may be used by another measurement procedure.

[0090] In possible implementations, one or more measurement rounds are multiple consecutive measurement rounds.

[0091] In possible implementations, a fourth message indicating the termination of measurement for one or more measurement rounds includes: The fourth message includes identifiers for one or more measurement rounds (e.g., measurement round indices). In other words, the fourth message includes identifiers for one or more measurement rounds for which measurement needs to be terminated.

[0092] In possible implementations, a fourth message indicates the end of measurement for one or more measurement rounds, where a value F contained in the fourth message indicates the end of measurement for the Fth measurement round, and F is a non-negative integer, and the Fth measurement round is included in one or more measurement rounds. For example, the current measurement round, i.e., round 1, is used as the reference point and indicates the end of measurement for round (measurement round) relative to round 1. For example, a value of 0 indicates that measurement for round 1 has ended, i.e., measurement for the current measurement round has ended, and a value of 1 indicates that measurement for round 2 has ended.

[0093] In possible implementations, a fourth message indicating the completion of measurement for one or more measurement rounds may include: The fourth message indicating the completion of measurement for all remaining measurement rounds. For example, a specific value included in the fourth message indicates that measurement for all remaining rounds has been completed. For example, the specific value is the maximum value of a field occupied by a particular value.

[0094] In possible implementations, a fourth message indicating the end of measurement for one or more measurement rounds includes the following: the fourth message includes a second bitmap, the j-th bit in the second bitmap corresponds to the j-th measurement round, and if the j-th bit is set to a specified value, the j-th bit indicates the end of the j-th measurement round, the j-th measurement round is included in one or more measurement rounds, and j is a non-negative integer.

[0095] In possible implementations, one or more measurement rounds are multiple consecutive measurement rounds. The fourth message indicating the end of measurement for one or more measurement rounds includes the fourth message containing a first value and a second value, where the first value indicates the initial measurement round in multiple consecutive measurement rounds, and the second value indicates the final measurement round in multiple consecutive measurement rounds.

[0096] In possible implementations, the fourth message includes a target field, and when the target field is set to the first value, it indicates that the fourth message has completed the measurement round.

[0097] In possible implementations, the fourth message is a POLL message.

[0098] In possible implementations, the third message indicates the termination of measurement for one or more measurement rounds. In other words, the third message indicates the termination of measurement for one or more rounds of measurement. For example, the third message indicates the termination of measurement for multiple measurement rounds, which may or may not be temporally adjacent. In another example, the third message indicates the termination of measurement for multiple measurement rounds, which may be located in the same measurement block or in different measurement blocks. A single measurement block contains one or more measurement rounds. Temporarily adjacent may mean that multiple measurement rounds in the same measurement block are adjacent, or that one or more trailing measurement rounds in a previous measurement block are adjacent to one or more leading measurement rounds in the current measurement block.

[0099] In this implementation, the third message indicates that one or more measurement rounds will be terminated to reduce resource overhead and unnecessary measurements. Furthermore, the time resources corresponding to the terminated measurement rounds may be used by another measurement procedure.

[0100] In possible implementations, one or more measurement rounds are multiple consecutive measurement rounds.

[0101] In possible implementations, a third message indicating the termination of measurement for one or more measurement rounds means that the third message contains identifiers for one or more measurement rounds (e.g., measurement round indices). In other words, the third message contains identifiers for one or more measurement rounds for which measurement needs to be terminated.

[0102] In possible implementations, a third message indicates the end of measurement for one or more measurement rounds by indicating that a value F contained in the third message indicates the end of measurement for the Fth measurement round, where F is a non-negative integer and the Fth measurement round is included in one or more measurement rounds. For example, the current measurement round, i.e., round 1, is used as the reference point and indicates the end of measurement for round (measurement round) relative to round 1. For example, a value of 0 indicates that measurement for round 1 has ended, i.e., measurement for the current measurement round has ended, and a value of 1 indicates that measurement for round 2 has ended.

[0103] In possible implementations, a third message indicating the completion of measurement for one or more measurement rounds includes indicating the completion of measurement for all remaining measurement rounds. For example, a specific value included in the third message indicates that measurement for all remaining rounds has been completed. For example, the specific value is the maximum value of a field occupied by a particular value.

[0104] In possible implementations, a third message indicating the end of measurement for one or more measurement rounds includes the third message containing a second bitmap, where the j-th bit in the second bitmap corresponds to the j-th measurement round, and if the j-th bit is set to a specified value, the j-th bit indicates the end of the j-th measurement round, where the j-th measurement round is included in one or more measurement rounds, and j is a non-negative integer.

[0105] In possible implementations, one or more measurement rounds are multiple consecutive measurement rounds. A third message indicating the end of measurement for one or more measurement rounds includes the third message containing a first value and a second value, where the first value indicates the initial measurement round in the multiple consecutive measurement rounds, and the second value indicates the final measurement round in the multiple consecutive measurement rounds.

[0106] In a possible implementation, the third message includes a target field, and if the target field is set to the first value, it indicates that the third message indicates the end of the measurement round.

[0107] In possible implementations, the third message is a POLL message.

[0108] According to the ninth aspect, one embodiment of the present application provides a communication device. The communication device has functions to implement the operation in an embodiment of the method of the first aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In possible implementations, the communication device includes a transceiver module and a processing module. The processing module is configured to generate a first message. The first message includes a first bitmap, which contains N bits, the i-th bit of the first bitmap corresponding to the i-th UWB device, and if the i-th bit is set to a specified value, the i-th bit indicates the position of the parameter configuration information of the i-th UWB device in the first DPL, where i is between 1 and N, and N is an integer greater than 0, and the first DPL is included in the first message. The transceiver module is configured to send the first message.

[0109] In possible implementations, the transceiver module is further configured to transmit a second message. The second message includes a second DPL, which includes one or more sequentially arranged list elements, any list element in the second DPL includes the address of the UWB device corresponding to any list element, and the sequentially arranged i-th list element in the second DPL includes parameter configuration information for the corresponding i-th UWB device.

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

[0111] For the technical effects brought about by possible implementations of the ninth aspect, please refer to the description of the technical effects of the first aspect or possible implementations of the first aspect.

[0112] According to a tenth aspect, one embodiment of the present application provides a communication device. The communication device has functions to implement the operation in an embodiment of the method of a second aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a first message. The first message includes a first bitmap, the first bitmap includes N bits, and the i-th bit of the first bitmap corresponds to the i-th UWB device. The processing module is configured such that, if the i-th bit is set to a specified value, it determines the position of the parameter configuration information for the i-th UWB device in the first device parameter list DPL, where i is between 1 and N, N is an integer greater than 0, and the first DPL is included in the first message.

[0113] In possible implementations, the first DPL contains multiple sequentially arranged list elements. The processing module is specifically configured to determine that the fth list element in the first DPL contains parameter configuration information for the i-th UWB device if the i-th bit is the f-th bit in the first bitmap that is sequentially arranged and set to a specified value, where F is an integer greater than 0.

[0114] In possible implementations, the transceiver module is further configured to receive a second message, which includes a second DPL, which includes one or more sequentially arranged list elements, where any list element in the second DPL includes the address of the UWB device corresponding to that list element. The processing module is further configured to determine, based on the second message, that the i-th sequentially arranged list element in the second DPL contains parameter configuration information for the corresponding i-th UWB device, where i is an integer greater than 0. The processing module is also configured to determine that the i-th bit in the first bitmap corresponds to the i-th UWB device, and, if the i-th bit is set to a specified value, to determine the location of the parameter configuration information for the i-th UWB device in the first DPL.

[0115] For possible implementations of the communication device in the tenth embodiment, please refer to the possible implementations in the second embodiment.

[0116] For the technical effects brought about by possible implementations of the tenth embodiment, please refer to the description of the technical effects of the second embodiment or possible implementations of the second embodiment.

[0117] According to the eleventh aspect, one embodiment of the present application provides a communication device. The communication device has functions to implement the operation in an embodiment of the method of the third aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In possible implementations, the communication device includes a transceiver module and a processing module. The processing module is configured to generate a first message. The first message includes a first list element, which includes parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the i-th UWB device's list element in the second message within the device parameter list DPL; the second message is information sent before the first message is sent, which includes the address of the i-th UWB device, and the DPL is included in the second message. The transceiver module is configured to send the first message.

[0118] For possible implementations of the communication device in the eleventh embodiment, please refer to the possible implementations in the third embodiment.

[0119] For the technical effects brought about by possible implementations of the eleventh aspect, please refer to the description of the technical effects of the third aspect or the possible implementations of the third aspect.

[0120] According to a twelfth aspect, one embodiment of the present application provides a communication device. The communication device has functions that implement the behavior of the method embodiment of the fourth aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a first message. The first message contains a first list element, which contains parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the i-th UWB device's list element in the second message within the device parameter list DPL; the second message is information sent before the first message is sent, which contains the address of the i-th UWB device, and the DPL is included in the second message. The processing module is configured to determine the first list element based on the identifier.

[0121] In possible implementations, the transceiver module is further configured to receive a second message. The processing module is further configured to determine the order in the DPL of the i-th UWB device list elements in the second message and record that order as an identifier.

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

[0123] For the technical effects brought about by possible implementations of the twelfth aspect, please refer to the description of the technical effects of the fourth aspect or the possible implementations of the fourth aspect.

[0124] According to a thirteenth aspect, one embodiment of the present application provides a communication device. The communication device has functions to implement the behavior in the method embodiment of the fifth aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In possible implementations, the communication device includes a transceiver module and a processing module. The processing module is configured to generate a first message. The transceiver module is configured to send a first message, the first message indicating the expiration of a CAP, the CAP being the period during which a response message to the first message is permitted; receive a second message from a plurality of second devices, each of which contains the second parameter configuration information of the corresponding second device; send a third message, the third message containing the first parameter configuration information of some or all of the plurality of second devices and information indicating when a fourth message is sent, the fourth message being used to update the first parameter configuration information of at least one of the plurality of second devices.

[0125] In possible implementations, the transceiver module is further configured to transmit a fourth message. The fourth message includes a first bitmap, which contains N bits, the i-th bit of the first bitmap corresponding to the i-th UWB device, and if the i-th bit is set to a specified value, the i-th bit indicates the position of the first parameter configuration information for the i-th UWB device in the first device parameter list DPL, where i is between 1 and N, and N is an integer greater than 0, and the first DPL is included in the fourth message.

[0126] In possible implementations, the transceiver module is further configured to send a fourth message. The fourth message includes a first list element, which includes first parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the i-th UWB device list element in the third message within the device parameter list DPL, which is included in the third message, and the i-th UWB device is one of several second devices.

[0127] For possible implementations of the communication device in the 13th aspect, please refer to the possible implementations in the 5th aspect.

[0128] For the technical effects brought about by possible implementations of the 13th aspect, please refer to the description of the technical effects of the 5th aspect or the possible implementations of the 5th aspect.

[0129] According to a fourteenth aspect, one embodiment of the present application provides a communication device. The communication device has functions that implement the behavior in the method embodiment of the sixth aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a first message. The first message indicates the expiration of a CAP, which is the period during which a response message to the first message is permitted. The transceiver module is configured to generate a second message. The transceiver module is further configured to send a second message before the expiration date, the second message containing second parameter configuration information for a target second device, receive a third message, the third message containing first parameter configuration information for one or more second devices and information indicating when a fourth message is sent, and the fourth message being used to update the first parameter configuration information for at least one of the one or more second devices.

[0130] In possible implementations, the transceiver module is further configured to receive a fourth message. The fourth message contains a first bitmap, which contains N bits, where the i-th bit of the first bitmap corresponds to the i-th UWB device. The processing module is further configured to determine the location of the first parameter configuration information for the i-th UWB device in a first device parameter list (DPL) if the i-th bit is set to a specified value, where i is between 1 and N, and N is an integer greater than 0, and the first DPL is included in the fourth message.

[0131] In possible implementations, the first DPL contains a number of sequentially arranged list elements. The processing module is specifically configured to determine that the fth list element in the first DPL contains first parameter configuration information for the i-th UWB device if the i-th bit is the f-th bit, which is sequentially arranged in the first bitmap and set to a specified value, where F is an integer greater than 0.

[0132] In a possible implementation, the third message contains a second DPL, which contains a number of sequentially arranged list elements, and any list element in the second DPL contains the address of the second device corresponding to any list element. The processing module is further configured to determine, based on the third message, that the i-th sequentially arranged list element in the second DPL corresponds to the i-th UWB device, where i is an integer greater than 0. The processing module is specifically configured to determine the location of the first parameter configuration information of the i-th UWB device in the first DPL if the i-th bit is set to a specified value.

[0133] In a possible implementation, the transceiver module is further configured to receive a fourth message, the fourth message containing a first list element, the first list element containing first parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the i-th UWB device list element in the third message within the Device Parameter List (DPL), the DPL being contained in the third message, and the i-th UWB device being one of several second devices. The processing module is further configured to determine the first list element based on the identifier.

[0134] In possible implementations, the processing module is further configured to determine the order of the list elements of the i-th UWB device in the third message within the DPL and to record that order as an identifier.

[0135] For possible implementations of the communication device in the 14th aspect, please refer to the possible implementations in the 6th aspect.

[0136] For the technical effects brought about by possible implementations of the 14th aspect, please refer to the description of the technical effects of the 6th aspect or the possible implementations of the 6th aspect.

[0137] According to the 15th aspect, one embodiment of the present application provides a communication device. The communication device has functions to implement the behavior in the method embodiment of the 7th aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In possible implementations, the communication device includes a transceiver module and a processing module. The processing unit is configured to generate a first message. The transceiver module is configured to send a first message, the first message indicating the expiration of a CAP, the CAP being the period during which a response message to the first message is permitted; receive second messages from a plurality of second devices, each of which contains second parameter configuration information for the corresponding second device; send a third message, the third message carrying information indicating when a fourth message will be sent; and the fourth message will be sent to some or all of the plurality of second devices.

[0138] For possible implementations of the communication device in the 15th aspect, please refer to the possible implementations in the 7th aspect.

[0139] For the technical effects brought about by possible implementations of the 15th aspect, please refer to the description of the technical effects of the 7th aspect or the possible implementations of the 7th aspect.

[0140] According to the 16th aspect, one embodiment of the present application provides a communication device. The communication device has functions to implement the behavior in the method embodiment of the 8th aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a first message. The first message indicates the expiration of a CAP, which is the period during which a response message to the first message is permitted. The processing unit is configured to generate a second message. The transceiver module is further configured to send a second message to a first device before its expiration date, the second message containing second parameter configuration information for the target second device, receive a third message from the first device, the third message carrying information indicating when a fourth message will be sent, and the fourth message being sent to some or all of the devices that send a response message to the first message to the first device before its expiration date.

[0141] For possible implementations of the communication device in the 16th aspect, please refer to the possible implementations in the 8th aspect.

[0142] For the technical effects brought about by possible implementations of the 16th aspect, please refer to the description of the technical effects of the 8th aspect or the possible implementations of the 8th aspect.

[0143] According to the 17th aspect, one embodiment of the present application provides another communication device. The communication device includes a processor, the processor is coupled to a memory, the memory stores a program or instruction, and when the program or instruction is executed by the processor, the communication device is configured to perform one of the methods of the first to eighth aspects.

[0144] In this embodiment of the present application, in the process of performing the method, the process of transmitting information (or signals) in the method can be understood as the process of outputting information based on instructions from a processor. When outputting information, the processor outputs the information to the transceiver so that the transceiver transmits the information. After the information is output by the processor, further processing of the information may need to be performed on the information before it arrives at the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, further processing of the information may need to be performed on the information before it is input to the processor.

[0145] Unless otherwise specified, or if operations such as sending and / or receiving related to the processor do not contradict the actual function or internal logic of the operation in the relevant description, the operation can generally be understood as an instruction output based on the processor.

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

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

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

[0149] In possible implementations, the communication device further includes a transceiver, which is configured to receive signals, transmit signals, and so on.

[0150] According to the 18th aspect, one embodiment of the present application provides another communication device, the communication device comprising a processing circuit and an interface circuit, the interface circuit being configured to acquire or output data, and the processing circuit being configured to perform a method in any one of the first to eighth aspects.

[0151] According to the 19th aspect, one embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer is able to perform a method in any one of the first to eighth aspects.

[0152] According to the 20th aspect, one embodiment of the present application provides a computer program product. The computer program product includes a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer is able to perform one of the methods of the first through eighth aspects.

[0153] According to the 21st aspect, one embodiment of the present application provides a communication system including a communication device in the 9th aspect or any possible implementation of the 9th aspect, and a communication device in the 10th aspect or any possible implementation of the 10th aspect.

[0154] According to the 22nd aspect, one embodiment of the present application provides a communication system including a communication device in the 11th aspect or any possible implementation of the 11th aspect, and a communication device in the 12th aspect or any possible implementation of the 12th aspect.

[0155] According to the 23rd aspect, one embodiment of the present application provides a communication system including a communication device in the 13th aspect or any possible implementation of the 13th aspect, and a communication device in the 14th aspect or any possible implementation of the 14th aspect.

[0156] According to the 24th aspect, one embodiment of the present application provides a communication system including a communication device in the 15th aspect or any possible implementation of the 15th aspect, and a communication device in the 16th aspect or any possible implementation of the 16th aspect.

[0157] According to the 25th aspect, one embodiment of the present application provides a chip including a processor and a communication interface. The processor reads instructions stored in memory via the communication interface in order to perform a method in any one of the first to eighth aspects.

[0158] According to the 26th aspect, one embodiment of the present application provides another communication method for UWB. The method includes the steps of generating a fifth message indicating the termination of one or more measurement rounds, and transmitting the fifth message.

[0159] In this embodiment of the present application, the fifth message indicates that one or more measurement rounds are terminated in order to reduce resource overhead and unnecessary measurements.

[0160] According to the 27th aspect, one embodiment of the present application provides another communication method for UWB. The method includes: receiving a fifth message indicating the termination of measurement in one or more measurement rounds; and terminating measurement in one or more measurement rounds based on the fifth message.

[0161] In this embodiment of the present application, one or more measurement rounds are terminated based on a fifth message in order to reduce resource overhead and unnecessary measurements.

[0162] In possible implementations of the 26th or 27th aspect, one or more measurement rounds are multiple consecutive measurement rounds. Multiple consecutive measurement rounds are multiple measurement rounds that are consecutive in time.

[0163] In possible implementations of the 26th or 27th aspect, the fifth message indicating the termination of measurement for one or more measurement rounds means that the fifth message includes identifiers (e.g., measurement round indices) of one or more measurement rounds. In other words, the fifth message includes identifiers of one or more measurement rounds for which measurement needs to be terminated.

[0164] In possible implementations of the 26th or 27th aspect, the fifth message indicating the termination of measurement for one or more measurement rounds means that a value F contained in the fifth message indicates the termination of measurement for the fth measurement round after the current measurement round, where F is a non-negative integer and the fth measurement round is contained within one or more measurement rounds.

[0165] In possible implementations of the 26th or 27th aspect, the fifth message indicating the termination of measurement for one or more measurement rounds is equivalent to the fifth message indicating the termination of measurement for all remaining measurement rounds.

[0166] In possible implementations of the 26th or 27th aspect, the fifth message indicating the termination of measurement in one or more measurement rounds means that the fifth message includes a second bitmap, where the j-th bit in the second bitmap corresponds to the j-th measurement round, and when the j-th bit is set to a specified value, the j-th bit indicates the termination of the j-th measurement round, and the j-th measurement round is included in one or more measurement rounds.

[0167] In possible implementations of the 26th or 27th aspect, one or more measurement rounds are multiple consecutive measurement rounds. The fifth message indicating the end of measurement for one or more measurement rounds includes the fifth message including a first value and a second value, where the first value indicates the initial measurement round in the multiple consecutive measurement rounds and the second value indicates the final measurement round in the multiple consecutive measurement rounds.

[0168] In possible implementations of the 26th or 27th aspect, the fifth message includes a target field, which indicates whether a completed measurement round corresponding to the measurement task is configured for the fifth message.

[0169] In possible implementations of the 26th or 27th aspect, the fifth message is a POLL message, a Response message, a Report message, or a SOR message.

[0170] According to the 28th aspect, one embodiment of the present application provides another communication method for UWB. The method includes the steps of: generating a sixth message, the sixth message indicating a recommendation (suggestion or request) to complete measurements of S measurement rounds; and transmitting the sixth message, where S is an integer greater than 0. In the present application, recommendation may be replaced with request, suggestion, or another word whose meaning is similar to that of recommendation. For example, the sixth message indicates that a second device recommends (suggests or requests) the completion of measurements of S measurement rounds. The second device is an initiator or responder of a measurement task.

[0171] In this embodiment of the present application, the sixth message indicates a recommendation to terminate S measurement rounds in order to terminate one or more measurement rounds. This further reduces resource overhead and unnecessary measurements.

[0172] In a possible implementation of the 28th aspect, the method further includes the step of receiving a seventh message, the seventh message indicating the termination of one or more measurement rounds. For a possible implementation of the seventh message, see the possible implementation of the fourth message in the 8th aspect.

[0173] In a possible implementation of the 28th aspect, the method further includes the step of terminating the measurement of one or more measurement rounds based on the 7th message.

[0174] In a possible implementation of the 28th embodiment, the method further includes the step of completing measurements for S measurement rounds.

[0175] According to the 29th aspect, one embodiment of the present application provides another communication method for UWB. The method includes receiving a sixth message indicating a recommendation (suggestion or request) to terminate measurements of S measurement rounds; and, based on the sixth message, terminating measurements of S measurement rounds, sending a seventh message, or performing a rejection, wherein the seventh message indicates terminating measurements of one or more measurement rounds. For possible implementations of the seventh message, see the possible implementations of the fourth message in the eighth aspect. Rejection may be not responding to the sixth message, i.e., no processing is performed after the sixth message is received, or sending a recommendation indicating rejection of the sixth message. Terminating measurements of S measurement rounds includes skipping sending a POLL message.

[0176] In this embodiment of the present application, measurements are completed for S measurement rounds, or a seventh message is sent based on the sixth message, thereby avoiding unnecessary measurements and further reducing resource overhead.

[0177] In possible implementations of the 28th or 29th aspect, the sixth message indicates a recommendation to terminate measurements for S measurement rounds, wherein the sixth message includes identifiers for the S measurement rounds (e.g., measurement round indices). In other words, the sixth message includes identifiers for the S measurement rounds that need to be terminated.

[0178] In possible implementations of the 28th or 29th aspect, the sixth message indicates a recommendation to complete the measurement of S measurement rounds, where the value F contained in the sixth message indicates a recommendation to complete the measurement of the fth measurement round after the current measurement round, where F is a non-negative integer and the fth measurement round is included in S measurement rounds.

[0179] In possible implementations of the 28th or 29th aspect, the sixth message indicating a recommendation to complete measurements for S measurement rounds includes the sixth message indicating a recommendation to complete measurements for all remaining measurement rounds.

[0180] In possible implementations of the 28th or 29th aspect, the sixth message indicates a recommendation to terminate the measurement of S measurement rounds, wherein the sixth message includes a third bitmap, the j-th bit in the third bitmap corresponds to the j-th measurement round, and when the j-th bit is set to a specified value, the j-th bit indicates a recommendation to terminate the measurement of the j-th measurement round, the j-th measurement round is included in S measurement rounds, and j is a non-negative integer.

[0181] In possible implementations of the 28th or 29th aspect, S measurement rounds are multiple consecutive measurement rounds. The sixth message indicating a recommendation to terminate the measurement of S measurement rounds includes: the sixth message includes a third value and a fourth value, the third value indicating the initial measurement round in the multiple consecutive measurement rounds, and the fourth value indicating the last measurement round in the multiple consecutive measurement rounds.

[0182] In possible implementations of the 28th or 29th aspect, the sixth message includes a target field, which indicates whether a completed measurement round corresponding to the measurement task is configured for the sixth message.

[0183] In possible implementations of the 28th or 29th aspect, the sixth message is a response message or a report message.

[0184] In possible implementations of the 28th or 29th aspect, the seventh message is a POLL message.

[0185] According to a 30th aspect, one embodiment of the present application provides another communication device having functions to implement the behavior in the method embodiment of a 26th aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The processing unit is configured to generate a fifth message. The fifth message indicates the termination of measurement in one or more measurement rounds. The transceiver module is configured to transmit the fifth message.

[0186] For possible implementations of the communication device in the 30th aspect, please refer to the possible implementations in the 26th aspect.

[0187] For the technical effects brought about by possible implementations of the 30th aspect, please refer to the description of the technical effects of the 26th aspect or the possible implementations of the 26th aspect.

[0188] According to a 31st aspect, one embodiment of the present application provides another communication device having functions to implement the behavior in the method embodiment of a 27th aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a fifth message. The fifth message indicates the termination of measurement in one or more measurement rounds. The processing unit is configured to terminate measurement in one or more measurement rounds based on the fifth message.

[0189] For possible implementations of the communication device in the 31st aspect, please refer to the possible implementations in the 27th aspect.

[0190] For the technical effects brought about by possible implementations of the 31st aspect, please refer to the description of the technical effects of the 27th aspect or the possible implementations of the 27th aspect.

[0191] According to a 32nd aspect, one embodiment of the present application provides another communication device. The communication device has functions to implement the behavior in the method embodiment of a 28th aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The processing unit is configured to generate a sixth message. The sixth message indicates a recommendation (suggestion or request) to complete S measurement rounds. The transceiver module is configured to transmit the sixth message, where S is an integer greater than 0.

[0192] For possible implementations of the communication device in the 32nd aspect, please refer to the possible implementations in the 28th aspect.

[0193] For the technical effects brought about by possible implementations of the 32nd aspect, please refer to the description of the technical effects of the 28th aspect or the possible implementations of the 28th aspect.

[0194] According to a 33rd aspect, one embodiment of the present application provides another communication device. The communication device has functions to implement the behavior in the method embodiment of a 29th aspect. The communication device may be a communication device, a component of a communication device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or some of the functions of a communication device. The functions of the communication device may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. In a possible implementation, the communication device includes a transceiver module and a processing module. The transceiver module is configured to receive a sixth message. The sixth message indicates a recommendation (suggestion or request) to terminate measurements of S measurement rounds. The processing unit is configured to terminate measurements of S measurement rounds, or to send a seventh message, or to perform a rejection based on the sixth message. The seventh message indicates terminating measurements of one or more measurement rounds.

[0195] For possible implementations of the communication device in the 33rd aspect, please refer to the possible implementations in the 29th aspect.

[0196] For the technical effects brought about by possible implementations of the 33rd aspect, please refer to the description of the technical effects of the 29th aspect or the possible implementations of the 29th aspect.

[0197] According to the 34th aspect, one embodiment of the present application provides another communication device. The communication device includes a processor, the processor is coupled to a memory, the memory is configured to store a program or instruction, and when the program or instruction is executed by the processor, the communication device performs a method according to any one of the 26th to 29th aspects.

[0198] According to the 35th aspect, one embodiment of the present application provides another communication device, the communication device comprising a processing circuit and an interface circuit, the interface circuit being configured to acquire or output data, and the processing circuit being configured to perform a method in any one of the 26th to 29th aspects.

[0199] According to the 36th aspect, one embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer is able to perform a method in any one of the 26th to 29th aspects.

[0200] According to the 37th aspect, one embodiment of the present application provides a computer program product. The computer program product includes a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer is able to perform a method in any one of the 26th to 29th aspects.

[0201] According to the 38th aspect, one embodiment of the present application provides a communication system including a communication device in the 30th aspect or any possible implementation of the 30th aspect, and a communication device in the 31st aspect or any possible implementation of the 31st aspect.

[0202] According to the 39th aspect, one embodiment of the present application provides a communication system including a communication device in the 32nd aspect or any possible implementation of the 32nd aspect, and a communication device in the 33rd aspect or any possible implementation of the 33rd aspect.

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

[0204] [Figure 1] This diagram shows each phase of the distance measurement round in conventional technology. [Figure 2] This is a diagram of a distance measuring block in conventional technology. [Figure 3] This is a diagram illustrating the initialization process for NBA-MMS UWB ranging. [Figure 4A] This is a diagram of 1-to-many NBA-MMS UWB ranging. [Figure 4B] This is a diagram of one-to-many NBA-MMS UWB ranging based on interlaced mode. [Figure 5] This figure shows an example of a star topology structure. [Figure 6] This figure shows an example of a point-to-point topology or mesh topology. [Figure 7] An example of a UWB system to which the technical solution according to one embodiment of this application can be applied is shown. [Figure 8] This is an interaction flowchart of a communication method for UWB according to one embodiment of this application. [Figure 9] This is an interaction flowchart of another UWB communication method according to one embodiment of this application. [Figure 10] This is an interaction flowchart of another communication method for UWB according to one embodiment of this application. [Figure 11] This is an interaction flowchart of a communication method for another UWB according to one embodiment of the present application. [Figure 12] This is a diagram of the one-to-many NBA-MMS UWB initialization phase according to one embodiment of this application. [Figure 13] This is an interaction flowchart of a communication method for another UWB according to one embodiment of the present application. [Figure 14A] This is a diagram of the measurement round in measurement block N (Block N) according to one embodiment of this application. [Figure 14B]This is a diagram of the measurement round in measurement block M-1 (Block M-1) and measurement block (Block M) according to one embodiment of this application. [Figure 14C] This figure shows a measurement block M-1 (Block M-1) and other measurement rounds in a measurement block (Block M) according to one embodiment of this application. [Figure 14D] This figure shows a measurement block M-1 (Block M-1) and other measurement rounds in a measurement block (Block M) according to one embodiment of this application. [Figure 14E] This figure shows a measurement block M-1 (Block M-1) and other measurement rounds in a measurement block (Block M) according to one embodiment of this application. [Figure 14F] This figure shows a measurement block M-1 (Block M-1) and other measurement rounds in a measurement block (Block M) according to one embodiment of this application. [Figure 14G] This is a drawing that receives an SOR message for parameter configuration updates in the slot before the next round begins. [Figure 14H] This diagram shows that in one or more slots in the next round of RCP, an SOR message is received for parameter configuration updates. [Figure 14I] This diagram shows how to receive SOR messages for parameter configuration updates in one or more slots in the MRP for the next round or the current round. [Figure 15] The diagram shows that the POLL message sent by the initiator to the first responder also carries a slot that will be broadcast to all responders for the next update. [Figure 16] The initiator, based on the report message, indicates to all responders that they will broadcast a slot for the next update. [Figure 17]The initiator indicates that, based on the response message, it will broadcast a slot for the next update to all responders. [Figure 18] This is an interaction flowchart of a communication method for another UWB according to one embodiment of the present application. [Figure 19] This is a diagram showing the structure of a communication device 1900 according to one embodiment of this application. [Figure 20] This is a diagram showing the structure of another communication device 200 according to one embodiment of this application. [Figure 21] This is a diagram showing the structure of another communication device 210 according to one embodiment of this application. [Modes for carrying out the invention]

[0205] In the specification, claims, and accompanying drawings of this application, terms such as “first” and “second” are intended solely to distinguish different subjects and not to describe a particular order. It should be understood that the various numbers in the embodiments of this application are for distinction only to facilitate explanation and are not intended to limit the scope of the embodiments of this application. The sequential numbering of the processes described above does not imply an order of execution. The order of execution of the processes should be determined based on the function and internal logic of the processes. Furthermore, the terms “include,” “have,” or any other variation thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a set of steps or units is not limited to the listed steps or units, but instead may, at their discretion, further include steps or units not listed, or may, at their discretion, further include other steps or units specific to those processes, methods, products, or devices.

[0206] The “embodiments” as used herein mean that certain features, structures, or characteristics described in conjunction with the embodiments may be included in at least one embodiment of this application. The terms used in various places herein do not necessarily refer to the same embodiment and are not exclusive, independent, or optional embodiments of another embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0207] The terms used in the following embodiments of this application are intended to describe specific embodiments only and are not intended to limit this application. The singular terms “one,” “a,” “the,” and “this” as used herein and in the appended claims are also intended to include the plural unless explicitly specified in the context. The terms “and / or” as used herein should be understood to mean and include any or all possible combinations of one or more enumerated items. For example, “A and / or B” can mean three cases: A alone, B alone, and both A and B, where A and B can be singular or plural. The terms “multiple” as used herein mean two or more. In the textual descriptions of this application, the letter “ / ” typically indicates an “or” relationship between related objects.

[0208] In the embodiments of this application, "B corresponding to A" indicates that a correspondence exists between A and B, and that B may be determined based on A. However, it should be further understood that determining (or generating) B based on (or in accordance with) A does not mean that B is determined (or generated) solely based on (or in accordance with) A, and that B may alternatively be determined (or generated) based on (or in accordance with) A and / or other information.

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

[0210] Narrowband-assisted multi-millisecond ultra-wideband (NBA-MMS UWB): Ultra-wideband systems have large bandwidths, and devices in ultra-wideband systems need to have ultra-high-speed data reception and transmission capabilities. However, the spectral efficiency of impulse radio ultra-wideband (IR-UWB) systems based on impulse transmission is low, and the power consumption overhead required by IR-UWB solutions when transmitting the same information is much higher than the power consumption overhead of other narrowband short-range protocols (e.g., Bluetooth® or ZigBee). In ranging, positioning, or sensing scenarios, the accuracy of a device's measurement, positioning, or sensing is highly dependent on the signal bandwidth. A larger signal bandwidth indicates higher accuracy of sensing, positioning, or ranging by the device. Therefore, to ensure accuracy in ranging and sensing and reduce power consumption, it is considered appropriate to receive and transmit reference signals for ranging, positioning, or sensing using a UWB system, while other data / control messages / synchronization messages are transmitted according to narrowband (NB) protocols.

[0211] A technical solution for UWB that combines narrowband-supported UWB with multi-millisecond transmission is also known as NBA-MMS UWB.

[0212] Rangefinder round, positioning round, sensing round, measurement period, communication period: The IEEE 802.15.4z standard defines a ranging round as a ranging round. A ranging round is defined as follows: 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 in each ranging round is a ranging slot. A ranging round is divided into three phases: a ranging control phase, a ranging phase, and a measurement report phase. Figure 1 shows the phases of a ranging round in the prior art. Details are shown in Figure 1. In the IEEE 802.15.4z standard, the ranging control phase includes one ranging slot. However, the IEEE 802.15.4ab standard, currently under discussion and development, allows for a range measurement control phase to include two or more range measurement slots.

[0213] In the first slot of the ranging round shown in Figure 1, the controller sends a ranging control message (RCM). The RCM may also carry a message to update the round structure of the ranging round, for example, the round duration.

[0214] An updated ranging round (hereinafter sometimes abbreviated as "round") and an unupdated ranging round may or may not be adjacent in time. The durations of different rounds may or may not be the same. For illustrative purposes, the following example uses the default case where the durations of different rounds are the same.

[0215] Figure 2 shows a case where an updated ranging round (hereinafter sometimes abbreviated as "round") and an unupdated ranging round are not temporally adjacent. Figure 2 is a diagram of a ranging block in the prior art. As shown in Figure 2, a ranging block may have a temporal structure that includes multiple ranging rounds. Optionally, ranging blocks appear periodically and repeatedly. Optionally, the duration of the ranging rounds within a ranging block is the same. As shown in Figure 2, for a particular ranging process, the initiator and responder perform the ranging process in a ranging round within a ranging block, for example, round 1 shown in Figure 2. In this application, the initiator may be referred to as the initiator and is a UWB device that initiates a ranging / sensing / communication procedure. In the ranging / sensing / communication process, the initiator may be a transmitter or a receiver. In this application, the initiator may be referred to as the responder and is a UWB device that responds to a ranging / sensing / communication process initiated by a UWB initiator device. In the ranging / sensing / communication process, the responder may be a transmitter or a receiver. After a ranging round is completed, a specific ranging process is performed in round 1 of the next ranging block. From Figure 2, it can be seen that two adjacent round 1s are not adjacent in time, i.e., there is a time interval between the two adjacent round 1s. In the interval slot between two adjacent round 1s, the device may turn off the receiver to sleep in order to reduce power consumption. The durations of adjacent ranging blocks may be the same or different. For example, ranging blocks with different durations in adjacent ranging blocks may be placed in a hyper-block. Below, for illustrative purposes, we will use an example where the durations of adjacent ranging blocks are the same by default.

[0216] Before NBA-MMS UWB ranging can be performed (or initiated), initialization and setup processes must be performed (or executed) between the devices involved. For example, the initiator is the controller. The initiator must first broadcast an advertisement message to notify all responders that NBA-MMS UWB ranging needs to be performed now. The broadcast advertisement message may be carried in an advertising poll (ADV-POLL) message / advertising start message. After a responder receives an ADV-POLL message, if ranging needs to be performed, the responder feeds back an advertising response (ADV-RESP) message to the initiator. The ADV-RESP message contains the parameter configuration information required by the responder. After receiving the ADV-RESP message, the initiator may decide whether to accept the parameter configuration proposed by the responder, or may notify the responder of the final parameter configuration result based on a start-of-ranging (SOR) message. The SOR message may carry a parameter confirmation message for the responder's ADV-RESP message, or a parameter change / update message for the responder's ADV-RESP message. After a certain period following the responder's receipt of the SOR message, the initiator and responder may initiate the NBA-MMS UWB ranging process. The length of this period may be determined based on the Time offset to MMS POLL information in the SOR message. Figure 3 illustrates the initialization process for NBA-MMS UWB ranging.

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

[0218] In the one-to-many NBA-MMS UWB ranging shown in Figure 4A, the initiator and each responder sequentially perform NBA-MMS UWB ranging. In other words, the initiator and each responder complete the processes of exchanging polling / start (POLL) and response (RESP) messages, exchanging multi-millisecond (MMS) blocks, ranging, and reporting the ranging results. The ranging result report includes both reports from responders to the initiator and reports from the initiator to the responders. The ranging process shown in Figure 4A is sometimes referred to as one-to-many NBA-MMS UWB ranging based on concatenate mode. Note that this application is also applicable to one-to-many ranging processes based on other modes, such as one-to-many NBA-MMS UWB ranging based on interlacing mode. See Figure 4B. Figure 4B is a diagram of one-to-many NBA-MMS UWB ranging based on interlaced mode. As shown in Figure 4B, in one-to-many NBA-MMS UWB ranging based on interlaced mode, each responder transmits MMS fragments sequentially, rather than the next responder transmitting all MMS fragments only after the current responder has transmitted all of them. In embodiments of this application, one-to-many NBA-MMS UWB based on concatenated mode is used below as an example for illustrative purposes. The methods in the relevant embodiments are also applicable to one-to-many NBA-MMS UWB processes based on interlaced mode. Details are not described.

[0219] In embodiments of this application, a single positioning process, i.e., a process for completing a positioning task, is defined as a positioning round. A positioning round may have a different name, which is not limited in this application. A positioning round may be a period (or duration) sufficient to complete an entire positioning task. The meaning of a positioning round is the same as that of a distance-measuring round, the difference being that one corresponds to distance measurement and the other to positioning. The minimum processing time unit of each positioning round is a positioning slot. A positioning round may be divided into three phases: a positioning control phase, a positioning phase, and a positioning report phase.

[0220] In embodiments of this application, a single sensing process, i.e., a process for completing a sensing task, is defined as a sensing ground. A sensing ground may have other names, which are not limited to this application. A sensing ground may be a period (or duration) sufficient to complete an entire sensing task. The meaning of a sensing ground is similar to that of a distance-measuring round, the difference being that one corresponds to distance measurement and the other to sensing. The minimum processing time unit of each sensing ground is a sensing slot. A sensing ground may be divided into three phases: a sensing control phase, a sensing phase, and a sensing report phase.

[0221] The measurement period is the period during which one or more UWB devices complete one or more measurement tasks. These measurement tasks may include ranging tasks, positioning tasks, sensing tasks, etc. The measurement period can be a ranging round, a positioning round, or a sensing round. The communication period is the period during which one or more UWB devices complete one or more communication tasks.

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

[0223] In this application, the signal carrier for messages carrying parameter configuration information is not limited. In other words, the carrier carrying messages such as the first message and the second message may be based on an NB signal, a UWB signal, or a Bluetooth signal. For example, in an NBA-MMS ranging process, the ADV-POLL / ADV-RESP / SOR / POLL / RESP / REPORT messages may be transmitted using an NB signal. As another example, in a non-NBA-MMS ranging process, the carrier carrying messages such as the first message and the second message may use a UWB signal.

[0224] In this application, the channel for messages carrying parameter configuration information is not limited. For example, in the following, ADV-POLL / ADV-RESP / SOR messages may use the discovery channel by default, or ADV-POLL / ADV-RESP / SOR messages may use the operation channel. POLL / RESP / REPORT messages may use the operation channel by default, or POLL / RESP / REPORT messages may use the discovery channel.

[0225] Format of compression header information elements: To reduce the duty cycle of NB signals, ADV-POLL messages, ADV-RESP messages, and SOR messages may be carried in messages based on a compressed header IE, as shown in Table 1-1. Table 1-1 shows an example of a message format based on a compressed header IE.

[0226] [Table 1]

[0227] SHR (synchronization header) indicates the synchronization header, PHR is the PHY header, PSDU (PHY service data unit) indicates the physical layer service data unit, and PHY (physical layer) is the physical layer. Table 1-2 shows an example of the compressed PSDU format.

[0228] [Table 2]

[0229] FC stands for frame control and is used to control the format of the header information element (header IE). The FC field occupies one octet.

[0230] The Address field indicates the device address of the device receiving the message shown in Table 1-1. The Address field occupies two octets.

[0231] The Message ID field is the message identification field, indicating which message the current compressed PSDU field corresponds to. The message content corresponding to the Message ID field is used to determine the type and size of the data content carried in the Content field within the compressed PSDU's frame format. The Message ID field occupies one octet.

[0232] The Content field is the data content carried in the compressed PSDU. The field's value is a variable and is determined based on the message content corresponding to the Message ID field.

[0233] The CRC field is a cyclic redundancy check (CRC) field used to perform error detection on the compressed PSDU in Table 1-2. The CRC field occupies two octets.

[0234] Compressed POLL / RESP / REPORT message format:

[0235] To reduce the duty cycle of NB signals, POLL / RESP / REPORT messages may be carried in messages based on compressed PSDUs, as shown in Table 2-1. Table 2-1 is an example of a POLL / RESP / REPORT message format based on compressed PSDUs.

[0236] [Table 3]

[0237] The meanings of the fields in Table 2-1 are the same as those in Table 1-1. Further details are not explained here. Table 2-2 shows an example format of a compressed PSDU.

[0238] [Table 4]

[0239] The meanings of the Address field, Message ID field, Content field, and CRC field are the same as those in Table 1-2. Further details are not provided here. The message IDs in Tables 1-1, 1-2, 2-1, and 2-2 are not limited to the embodiments of this application.

[0240] The following describes prior art 1 and prior art 2 related to the communication solution provided in the embodiments of this application.

[0241] Conventional Technology 1: Conventional Technology 1 provides scheduling information elements for UWB ranging, namely ranging device management information elements (RDM IE). Table 3 shows the format of the RDM IE in the Conventional Technology.

[0242] [Table 5]

[0243] Specifically, the meanings of some of the fields in Table 3 are as follows:

[0244] The SIU (slot index used) field indicates the access mode used in the current ranging process. If SIU=0, the current RDM IE is used to manage the ranging process based on conflicting access. If SIU=1, the current RDM IE is used to manage the ranging process based on scheduled access.

[0245] The Address Size field indicates the address type of the devices participating in the ranging process. If Address Size=0, it indicates that all devices associated with the current RDM List have short addresses, meaning their address length is 2 octets (bytes). If Address Size=1, it indicates that all devices associated with the current RDM List have extended addresses (long addresses), meaning their address length is 8 octets (bytes).

[0246] The RDM List Length field indicates the number of elements in the RDM List, i.e., the number of list elements in the format shown in Table 4. Table 4 shows the format of list elements in the RDM List in Prior Art 1. In the embodiments of this application, the list elements may be referred to as scheduling list elements.

[0247] The RDM List field is a list, and the format of the elements within the list is shown in Table 4.

[0248] [Table 6]

[0249] Specifically, the meanings of some of the fields in Table 4 are as follows:

[0250] The Ranging Role field indicates the ranging role of the device corresponding to the Address field of the current list element. If Ranging Role=0, it indicates that the device is a ranging responder. If Ranging Role=1, it indicates that the device is a ranging initiator.

[0251] The Ranging Slot Index field indicates the subscript of the slot assigned to the device participating in the ranging and corresponding to the current list element. The device address is determined based on the Address field in Table 4.

[0252] The Address field indicates the address of the device participating in the distance measurement and corresponding to the current list element.

[0253] Please refer to Table 4. The proportion of Address fields in the RDM List elements is too high. If the number of list elements in the RDM List field is too large, the overall transmission efficiency will decrease.

[0254] For devices with short addresses (2-octet device addresses), the proportion of Address fields in the RDM List elements is approximately 2 / 3 ≈ 66.7%.

[0255] For devices with long addresses (8-octet device addresses), the proportion of Address fields in the RDM List elements is approximately 8 / 9 ≈ 88.9%.

[0256] Conventional technology 2: Conventional Technology 2 provides a bitmap-based scheduling information element (IE) format for UWB. Table 5 shows the format of the bitmap-based scheduling IE provided in Conventional Technology 2.

[0257] [Table 7]

[0258] The Control field occupies one octet, while the scheduling list field occupies one or more octets. Table 6 shows the format of the Control field in the bitmap-based scheduling IE provided in Conventional Technology 2.

[0259] [Table 8]

[0260] Address Type=0 indicates that the device address is a short address, i.e., the address length is 2 octets (16 bits). Address Type=1 indicates that the device address is a long address (or extended address), i.e., the address length is 8 octets (64 bits). The device address here is the address of the device scheduled by the bitmap-based scheduling IE, i.e., the address of the device associated with the scheduling list.

[0261] Scheduling List Length indicates the number of list elements in the scheduling list field. The list elements are carried within the scheduling list field. Table 7 shows the format of list elements in the scheduling list in Conventional Art 2.

[0262] [Table 9]

[0263] The bitmap in Table 7 represents a one-dimensional bit sequence, for example, 0000100100100000. Bitmap Size indicates the length of the bitmap. Table 8 shows the relationship between the value of Bitmap Size and the length of the bitmap. Table 8 shows the relationship between the value of Bitmap Size and the length of the bitmap.

[0264] [Table 10]

[0265] For example, the bitmap shown in Table 7 represents a bit sequence with a length of 8, that is, it represents 8 slots (each bit corresponds to one slot), that is, the corresponding value of Bitmap Size is 0. When the bit is 1, it indicates that the device corresponding to the list element corresponding to the bitmap participates in ranging and transmits a UWB signal within the slot corresponding to the bit. Correspondingly, when the bit is 0, it indicates that the device does not transmit a UWB signal within the slot corresponding to bit 0.

[0266] [Table 11]

[0267] The bitmap shown in Table 9 sequentially shows slots 1 to slot 8 (or slots 0 to slot 7) from left to right. When all the bits corresponding to slot 2, slot 4, slot 5, slot 7, and slot 8 are 1, it indicates that the device transmits UWB signals in slot 2, slot 4, slot 5, slot 7, and slot 8. When all the bits corresponding to slot 1, slot 3, and slot 6 are 0, it indicates that the device does not transmit UWB signals in slot 1, slot 3, and slot 6.

[0268] Note that, for example, the method for describing the bitmap in Table 9 is, by default, a left-to-right instruction method. In other words, the bitmap shows a continuous sequence of near and far slots from left to right. For example, in the case of a bitmap with a length of 1 octet, the bitmap shows slots 1 through 8 (or slots 0 through 7) sequentially from left to right. Furthermore, the bitmap in the embodiments of this application may alternatively be described from right to left, i.e., show a continuous sequence of near and far slots. The order in which the bitmap is described is not limited to the embodiments of this application. This specification will be explained by using the left-to-right instruction method as an example.

[0269] Refer to Table 7. The proportion of Address fields in the Scheduling List elements is excessively high. If the number of list elements in the Scheduling List field is excessively large, the overall transmission efficiency decreases.

[0270] Table 10 shows the proportion of the Address field in the list elements of the RDM List for devices with short addresses (2-octet device addresses). Table 10 shows the overhead proportion of the Address field for devices with short addresses.

[0271] [Table 12]

[0272] For devices with long addresses (8-octet device addresses), Table 11 shows the proportion of the Address field within the list elements of the RDM List. Table 11 shows the overhead proportion of the Address field for devices with long addresses.

[0273] [Table 13]

[0274] From Tables 10 and 11, it can be seen that the proportion of Address fields in the list elements of the scheduling list field is not negligible. For a typical number of scheduling slots, for example, if the number of scheduling slots is 16 or less (i.e., bitmaps with a length of 1 or 2 octets are used), the proportion of Address fields is 40% or 50%, even for devices with short addresses. From the above analysis, it can be seen that the overall transmission efficiency of scheduling designs in Conventional Art 2 is low.

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

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

[0277] Figure 7 shows an example of a UWB system to which a technical solution according to one embodiment of this application can be applied. The UWB system includes an anchor (only one anchor is shown) and one or more tags (only tag 1 and tag 2 are shown). The protocols supported by the anchor and tags may include protocols such as IEEE 802.15.4a, IEEE 802.15.4z, and IEEE 802.15.4ab. Indeed, with the continued evolution and development of communication technology, the WLAN protocol may further include next-generation protocols such as IEEE 802.15.4ab. The anchor may be an access point, and the tags may be a station (STA). Both the access point and the STA support the WLAN protocol, which may include IEEE 802.11be (or referred to as Wi-Fi 7 or EHT protocol).

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

[0279] An access point may be an entire device, or a chip, processing system, etc., installed in the entire device. A device on which a chip or processing system is installed can implement the methods and functions of the embodiments of this application under the control of the chip or processing system (i.e., AP). The AP in the embodiments of this application is a device that provides services to a station (STA) and may support, for example, IEEE 802.15.4a, IEEE 802.15.4z, IEEE 802.15.4ab, or their next generation. For example, the AP may be a communications server, router, switch, bridge, computer, or communications entity such as a mobile phone. AP may include anchors, macro base stations, micro base stations (also called small cells), picocell base stations, femtocell base stations, relay stations, access points, gNBs, transmission reception points (TRPs), evolved node Bs (eNBs), radio network controllers (RNCs), home base stations (e.g., home evolved node Bs or home node Bs, HNBs), baseband units (BBUs), Wi-Fi access points (APs), integrated access and backhaul (IABs), and the like. Indeed, AP may alternatively be chips and processing systems within these devices in various forms to implement the methods and functions in the embodiments of this application.

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

[0281] In the multi-node NBA-MMS UWB system, since the octet overhead occupied by the device address is excessively large, the signaling overhead of the configuration information list (for example, the RDM List in the prior art 1 and the scheduling list in the prior art 2) is large. In this application, in order to reduce the proportion of the device address in the configuration information list and further reduce the signaling overhead of the configuration information list, a method of compressing the device address is designed.

[0282] Unless otherwise specified, note that for illustrative purposes, the initiator will be used as the controller by default. The methods provided in this application are also applicable to corresponding descriptions where the responder is the controller or where the controller is a third-party device. In addition, unless otherwise specified, the one-to-many case will be used by default for illustrative purposes, i.e., one initiator corresponds to multiple responders. The methods provided in this application are also applicable to corresponding descriptions where multiple initiators correspond to multiple responders. Furthermore, unless otherwise specified, the following will be illustrated by default using an example in which, before each measurement round begins, the initiator broadcasts a configuration update message for the measurement round (e.g., a ranging round) to all responders based on a measurement start message. Correspondingly, after receiving the measurement round configuration update message, the responders complete the parameter update configuration and begin measuring the current round and subsequent measurement rounds based on the updated parameters (until the next parameter update configuration). The method provided in this application is also applicable to the corresponding description in which an initiator broadcasts a measurement start message at a different time, for example, broadcasts a configuration update message for a measurement round based on the measurement start message during the measurement reporting phase of each measurement round.

[0283] In addition, unless otherwise specified, measurement round configuration update messages are broadcast by default in the measurement start message. This also applies to the corresponding descriptions of cases where measurement round configuration update messages are broadcast by being carried in a separate message. For example, the method provided in this application is applicable when measurement round configuration update messages are carried in a POLL message sent by the initiator to the responder in NBA-MMS UWB ranging. For example, in one-to-many NBA-MMS UWB ranging, the ranging round configuration update message is carried in a POLL message sent by the initiator to the initial responder. The initial responder is the responder among several responders that performs ranging with the initiator first in time. In this case, the POLL message is sent in a broadcast manner. As another example, in NBA-MMS UWB ranging, measurement round configuration update messages are carried in a RESPONSE message sent by the responder to the initiator. As another example, in NBA-MMS UWB ranging, configuration update messages for a measurement round are carried in REPORT messages sent by initiator(responder) to responder(initiator). The method provided in this application is applicable to the exemplary case described above. In addition, unless otherwise specified, the Address Size field is used by default below to trigger and enable the functionality defined in the embodiments of this application. The method provided in this application is applicable to corresponding descriptions when a different field is used for triggering, for example, when a different field other than the Address Size field is defined. In addition, for the sake of simplicity, it is assumed below that, by default, in the initial measurement start message, the order in which the list elements appear corresponds to the order of the device subscripts, i.e., list element #0, list element #1, ..., and list element #N correspond to device 0, device 1, ..., and device N, respectively.The corresponding descriptions are also applicable to other cases. For example, the method provided in this application is also applicable to the corresponding cases where list element #0, list element #1, ..., and list element #N correspond to device 2, device 4, ..., and device N, respectively. In addition, unless otherwise specified, the ranging process is used as an example by default below. The method provided in this application is also applicable to the corresponding descriptions of other measurement processes, such as sensing and positioning. In other words, the example below uses ranging as the measurement process for illustrative purposes. In addition, unless otherwise specified, updated rounds and unupdated rounds are not temporally adjacent by default below. The method provided in this application is also applicable to the corresponding descriptions of rounds that are temporally adjacent.

[0284] In addition, unless otherwise specified, the following uses NBA-MMS UWB ranging as an example for explanation purposes by default. The corresponding explanations are also applicable to other measurement applications such as ranging, sensing, and positioning. Other ranging methods include, but are not limited to, non-NBA-MMS ranging (ranging that does not include NBA ranging or MMS) and MMS ranging (ranging that does not include NBA but includes MMS).

[0285] Referring to the attached drawings, the communication solution for UWB provided in the embodiments of this application will be described below.

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

[0287] 801: The transmitter generates the first message.

[0288] The transmitter may be a UWB device that supports the UWB standard. The transmitter may be an AP or a station. The transmitter may be an FFD or an RFD. The transmitter may be a ranging, sensing, positioning, or communication initiator, i.e., a ranging initiator, sensing initiator, positioning initiator, or communication initiator; or a ranging, sensing, positioning, or communication responder, i.e., a ranging responder, sensing responder, positioning responder, or communication responder; or a third-party device (which may be called a controller device), i.e., not a ranging, sensing, positioning, or communication initiator or responder. For example, the transmitter is an initiator and the first message is a measurement start message or a polling / start POLL message. The measurement start message may be a SOR message, a sensing start message, a positioning start message, or a communication start message. A polling message may also be called a polling message. The name of the POLL message is not limited in this application.

[0289] A first message may carry a first device parameters list (DPL), the first DPL containing one or more list elements. Each list element contains parameter configuration information for one device (the device corresponding to the list element). Alternatively, each list element may contain scheduling information for one device (the device corresponding to the list element), the scheduling information indicating time units that may be occupied by the device to transmit UWB signals, i.e., time units used by the device to transmit UWB signals. In embodiments of this application, the device parameter configuration information corresponding to a list element in the first DPL may be information used by the device to determine the device's parameter configuration, or information used to change / update the device's parameter configuration. The names of DPLs are not limited in this application, and DPLs as used herein are merely examples.

[0290] The first message includes a first bitmap. The first bitmap may be contained in a compressed device identifier (CPDID) field within the first message. The name of the field containing the first bitmap within the first message is not limited. For illustrative purposes, the following example uses a CPDID field containing the first bitmap. The first bitmap may contain N bits, where N is an integer greater than 0. The i-th bit in the first bitmap corresponds to the i-th UWB device. In this application, the i-th bit in the first bitmap is the i-th bit that is arranged sequentially (for example, from left to right or right to left, hereinafter explained by using left to right as an example) within the first bitmap. Each of one or more bits in the first bitmap corresponds to one UWB device. For example, the length of the first bitmap is 8, and each bit in the first bitmap corresponds to one UWB device, that is, the 0th bit (initial bit) corresponds to the 0th UWB device, the 1st bit corresponds to the 1st UWB device, ..., the 7th bit corresponds to the 7th UWB device. Table 12 shows an example of the first bitmap.

[0291] [Table 14]

[0292] In Table 12, each bit from left to right corresponds to one UWB device. For example, assume that the bits from left to right correspond to the 0th UWB device through the 7th UWB device. When a bit is 0, it indicates that the first DPL does not contain parameter configuration information for the UWB device corresponding to the bit. When a bit is 1, it indicates that the first DPL contains parameter configuration information for the UWB device corresponding to the bit. In another example, the length of the first bitmap is 16, and each of the first 12 bits arranged sequentially in the first bitmap corresponds to one UWB device, i.e., the 0th bit corresponds to the 0th UWB device, the 1st bit corresponds to the 1st UWB device, ..., the 11th bit corresponds to the 11th UWB device. The last 6 bits arranged sequentially in the first bitmap do not correspond to a UWB device. If the i-th bit of the first bitmap is set to a specified value, the i-th bit indicates the location of the parameter configuration information for the i-th UWB device in the first DPL. The location of the parameter configuration information for the i-th UWB device within the first DPL can be understood as the location of the list element corresponding to the i-th UWB device within the first DPL. The specified value is 0 or 1. Below, we will use the specified value 1 as an example for explanation. i is between 1 and N, inclusive. If the i-th bit of the first bitmap is not set to the specified value, the i-th bit indicates that the first DPL does not contain the parameter configuration information for the i-th UWB device. If the i-th bit of the first bitmap is set to the specified value, the i-th bit indicates that the first DPL contains the parameter configuration information for the i-th UWB device.

[0293] 802: The transmitter sends the first message.

[0294] In response, one or more receivers receive the first message. For example, the transmitter is both the initiator and the controller, and the receiver is the responder. In another example, the transmitter is the controller and the receiver is the responder.

[0295] In possible implementations, the first DPL contains one or more sequentially arranged list elements. If the i-th bit is the f-th bit in the first bitmap that is sequentially arranged and set to a specified value, then the i-th bit indicates that the f-th list element in the first DPL contains parameter configuration information for the i-th UWB device, where F is an integer greater than 0 and less than or equal to N. The number of bits in the first bitmap that are set to a specified value may be equal to the number of list elements in the first DPL. For example, the length of the first bitmap is 8, the value of the 3 bits in the first bitmap is 1, and the first DPL contains 3 list elements. The f-th bit in the first bitmap that is sequentially arranged and has a specified value corresponds to the f-th list element in the first DPL. In other words, the order of one or more sequentially arranged list elements in the first DPL matches the order in the first bitmap of one or more UWB devices that correspond to one or more list elements. Table 13 shows another example of the first bitmap.

[0296] [Table 15]

[0297] The length of the first bitmap is 8, and each bit in the first bitmap corresponds to one UWB device, i.e., the 0th bit corresponds to the 0th UWB device, the 1st bit corresponds to the 1st UWB device, ..., the 7th bit corresponds to the 7th UWB device. The values ​​of the 0th, 4th, and 5th bits in the first bitmap are specified values, indicating that the list elements in the first DPL are, respectively, the list element corresponding to the 0th UWB device, the list element corresponding to the 4th UWB device, and the list element corresponding to the 5th UWB device. See Table 14. From Tables 13 and 14, it can be seen that the first list element, sequentially placed within the first DPL, contains the parameter configuration information for the first UWB device; the second list element, sequentially placed within the first DPL, contains the parameter configuration information for the fourth UWB device; and the third list element, sequentially placed within the first DPL, contains the parameter configuration information for the fifth UWB device.

[0298] [Table 16]

[0299] In Table 14, Device Parameters List element #0 is the list element corresponding to the 0th UWB device; for example, Device Parameters List element #0 is the update parameter set for the 0th UWB device. Device Parameters List element #1 is the list element corresponding to the 4th UWB device; for example, Device Parameters List element #1 is the update parameter set for the 4th UWB device. Device Parameters List element #2 is the list element corresponding to the 5th UWB device; for example, Device Parameters List element #2 is the update parameter set for the 5th UWB device. The update parameter set for a UWB device is used to update the parameter settings of the UWB device. In this application, TBD (To be determined) represents any value; this is not limited in this application. For example, the length of a device parameter list element in Table 14 is represented by Octets:TBD, indicating that the length of a device parameter list element may occupy one or more octets, i.e., the length of a device parameter list element is not limited. In other words, the length of the device parameter list elements can be flexibly configured based on requirements, and this is not limited to the present application.

[0300] In possible implementations, the first message further includes a first field, the first field indicating that the location of the UWB device parameter configuration information in the first DPL is identified using the first bitmap. The first field contains one or more bits. For example, the first field contains one bit. When the value of the bit is 1, the first field indicates that the first bitmap is used to identify the location of the UWB device parameter configuration information in the first DPL. In another example, the first field contains two bits, and when the value of the two bits (i.e., the binary value represented by the two bits) is 2, the first field indicates that the first bitmap is used to identify the location of the UWB device parameter configuration information in the first DPL. The first field may be referred to as the address size field or another field, which is not limited herein. Table 15 shows examples of the meanings of the values ​​of the first field. The values ​​of the first field in Table 15 are examples only and are not limited. In this implementation, the first field indicates that the first bitmap is used to identify the location of the UWB device parameter configuration information within the first DPL, and as a result, the receiver knows the location of the UWB device parameter configuration information within the first DPL, identified by the first bitmap, based on the first field.

[0301] [Table 17]

[0302] In possible implementations, the first message further includes a field indicating the length of the first bitmap. The field in the first message indicating the length of the first bitmap may be referred to as the CPDID Size field or another field, not limited to this application.

[0303] The device parameters management field in the first message is used to update the parameter configuration information for one or more responders. The device parameters management field may have other names, which are not limited herein. Table 16 shows an example of the format of the device parameters management field in the first message.

[0304] [Table 18]

[0305] The CPDID Size field indicates the size of the CPDID field. In other words, the CPDID Size field indicates the length of the first bitmap. The CPDID Size field may occupy 1 bit. For example, the CPDID Size field occupies 1 bit. When the value of the CPDID Size field is 0, it indicates that the size of the CPDID field is 1 octet. When the value of the CPDID Size field is 1, it indicates that the size of the CPDID field is 2 octets. The CPDID Size field is only valid when the configuration indicates that the device address is configured in a compressed format. In other words, the CPDID Size field is only valid when the Address Size field indicates that the CPDID field (including the first bitmap) is used to identify the location of the UWB device parameter configuration information within the DPL. The CPDID Size field is optional. In some possible embodiments, the length of the CPDID field is fixed, for example, fixed to 1 octet or 2 octets. In this case, the device parameters management field may not include the CPDID Size field. In some possible embodiments, the length of the CPDID field is variable. In this case, the length of the CPDID field must be indicated by the CPDID Size field.

[0306] The CPDID field is a field containing a first bitmap that indicates the location of the UWB device's parameter configuration information in the DPL. In other words, the CPDID field can indicate whether or not the UWB device's parameter configuration information is located in the DPL, and can also indicate the location of the UWB device's parameter configuration information within the DPL. In other words, the CPDID field indicates the UWB device corresponding to each list element in the DPL. In other words, the CPDID field contains the compressed identifier of the parameter configuration of one or more UWB devices. The CPDID field exists only if the configuration indicates that the device address is configured in a compressed manner. In other words, the CPDID field exists only if the Address Size field indicates that the CPDID field (containing the first bitmap) is used to identify the location of the UWB device's parameter configuration information within the DPL.

[0307] The Device Parameters List Length field indicates the number of list elements in the DPL. The Device Parameters List Length field can occupy up to 6 bits. The Device Parameters List Length field is optional. If the Address Size field (i.e., the first field) indicates that the CPDID field is used to identify the location of the UWB device's parameter configuration information within the first DPL, then the Device Parameters List Length field shown in Table 16 is not valid. In this case, the number of list elements in the DPL can be directly determined based on the sum of the number of bits with a value of 1 in the CPDID field.

[0308] The Address Size field (i.e., the first field) indicates that the CPDID field (containing the first bitmap) is used to identify the location of the UWB device parameter configuration information within the first DPL. The Address Size field may occupy 2 bits. See Table 15. The Address Size field introduces a new value of 2, triggering the CPDID Size field and enabling the presence of the CPDID field. The Address Size field may be referred to as other fields, but is not limited herein.

[0309] The RFU occupies 7 bits and is reserved for future use.

[0310] Please note that Table 16 is merely an example of the format of the device parameters management field in the first message. The location and size of each subfield within device parameters management are not limited in this application.

[0311] Table 17 shows an example of the format of list elements within DPL.

[0312] [Table 19]

[0313] From Tables 13 and 14, it is possible to understand that the receiver does not need to read the receiver's device address, but may learn whether an update needs to be performed in the current round by reading the first bitmap. Table 17 shows examples of list elements in the DPL. The CPDID field indicates the location of the list element in the DPL corresponding to the UWB device, and as a result, the device address in the list element may be omitted, reducing the signaling overhead for updating the list element. Note that Table 17 is just one example of a list element. Any list element carrying a device address may, based on the CPDID field, indicate the location of the list element in the DPL corresponding to the UWB device, and therefore the device address in the list element is omitted. Below, we will further describe some examples in which the CPDID field indicates the location of the parameter configuration information of the UWB device in the DPL.

[0314] 803: The receiver determines the location of the parameter configuration information for the i-th UWB device in the first DPL if the i-th bit is set to a specified value.

[0315] Before performing step 803, the receiver may know the correspondence between one or more bits in the first bitmap and UWB devices (or device addresses). For example, before receiving the first message, the receiver receives a configuration message and determines the correspondence between one or more bits in the first bitmap and UWB devices based on the configuration message. In a possible implementation of step 803, if the i-th bit is the f-th bit in the first bitmap that is sequentially placed and set to a specified value, it is determined that the f-th list element in the first DPL contains the parameter configuration information for the i-th UWB device, where F is an integer greater than 0. For example, the first bitmap is shown in Table 13, and the values ​​of the 0th, 4th, and 5th bits in the first bitmap are specified values. This indicates that the list elements in the first DPL are, in order, the list element corresponding to the 0th UWB device, the list element corresponding to the 4th UWB device, and the list element corresponding to the 5th UWB device. The receiver may determine, based on the first bitmap, that the parameter configuration information for the 0th UWB device is in the initial list element of the first DPL, the parameter configuration information for the 4th UWB device is in the second list element of the first DPL, and the parameter configuration information for the 5th UWB device is in the third list element of the first DPL.

[0316] The i-th UWB device may or may not be a receiver. Step 803 is merely an example of a receiver determining the location of parameter configuration information for a UWB device in the first DPL. It should be understood that any receiver may similarly determine the location of parameter configuration information for another UWB device in the first DPL.

[0317] In the embodiments of this application, the first bitmap indicates the location of the parameter configuration information of the UWB device within the DPL, so the device address in the list element can be omitted, and the signaling overhead for updating the list element can be reduced.

[0318] Figure 9 is an interaction flowchart of another communication method for UWB according to one embodiment of the present application. The method procedure in Figure 9 is a possible implementation of the method described in Figure 8. The method procedures in Figures 8 and 9 are applicable to scenarios with a small number of receivers (e.g., 16 or fewer receivers). In this implementation, the transmitter sends a second message to the receiver so that the receiver determines the correspondence between the UWB device and bits in a bitmap later transmitted by the transmitter. As shown in Figure 9, the method includes the following steps:

[0319] 901: The transmitter sends a second message.

[0320] In response, one or more receivers receive a second message. The second message may be a broadcast message. For example, the second message may be a SOR message or POLL message broadcast by the transmitter to all responders participating in the measurement before the initial measurement round.

[0321] The second message contains a second DPL, which contains one or more sequentially arranged list elements. Any list element in the second DPL contains the address of the UWB device corresponding to that list element, i.e., the device address. In other words, any list element in the second DPL contains a device address, and the device address is the address of the UWB device corresponding to any list element. The i-th sequentially arranged list element in the second DPL contains the parameter configuration information of the corresponding i-th UWB device. For example, the second DPL contains eight sequentially arranged list elements, each containing one device address. Table 18 shows an example of a second DPL.

[0322] [Table 20]

[0323] In Table 18, the second DPL contains eight sequentially arranged list elements. List element #0 contains the address of the 0th UWB device, list element #1 contains the address of the 1st UWB device, ..., list element #7 contains the address of the 7th UWB device. In Table 18, the i-th list element sequentially arranged within the second DPL contains the parameter configuration information of the corresponding i-th UWB device.

[0324] 902: Based on the second message, the receiver determines that the i-th list element, sequentially placed within the second DPL, contains the parameter configuration information for the corresponding i-th UWB device.

[0325] i is an integer greater than 0. Alternatively, the receiver determines, based on the second message, that the i-th list element sequentially placed within the second DPL contains parameter configuration information for the i-th UWB device. In this application, the parameter configuration information for the UWB device may include one or more of the following: measurement round update duration, number of MMS fragments, ranging phase duration (RPDuration), device scheduling slot, parameters related to MMS ranging sequence fragment (RSF), parameters related to ranging integrity fragment (RIF), channels used by the NB, and signal carriers used for measurement reporting (e.g., NB, UWB, and Bluetooth). Parameters related to RSFs and / or RIFs include, but are not limited to, the number of RSFs, the sequence used by the RSFs, the time offset from the start of the Ranging phase to the Initiator first RSF (TORPInitRSF), the time offset from the start of the Ranging phase to the Responder first RSF (TORPRespRSF), the time offset from the start of the Ranging phase to the Initiator first RIF (TORPInitRIF), the time offset from the start of the Ranging phase to the Responder first RIF (TORPRespRIF), the number of RIFs, and the length of the RIFs (e.g., the length of one or more chip units).The sequence used by the RSF may be determined based on the RSF code index and / or the RSF complementary set zeros. In this application, the parameter configuration information of the UWB device may include one or more of the above parameters related to the RSF and / or RIF.

[0326] It can be understood that, based on the second message, the receiver may determine which UWB devices are included in each list element where the parameter configuration information is sequentially arranged in the second DPL. Any receiver that receives the second message may perform step 902. The receiver may be the i-th UWB device. In other words, the receiver may determine the location of its parameter configuration information in the second DPL. In possible implementations, the receiver determines and records the location of its parameter configuration information in the second DPL. The receiver may further determine the location of the parameter configuration information of another UWB device and record it in the second DPL.

[0327] 903: The transmitter sends the first message.

[0328] For step 903, please refer to step 801.

[0329] 904: The receiver determines that the i-th bit of the first bitmap corresponds to the i-th UWB device.

[0330] Before receiving the first message, the receiver may record the location of the parameter configuration information for the i-th UWB device in the second DPL, i.e., record that the i-th list element, sequentially arranged in the second DPL, contains the parameter configuration information for the i-th UWB device. In a possible implementation of step 904, the receiver determines, based on the location of the recorded parameter configuration information for the i-th UWB device in the second DPL, that the i-th bit in the first bitmap corresponds to the i-th UWB device. It can be understood that, instead of determining only the i-th UWB device corresponding to the i-th bit in the first bitmap, the receiver may, in the same manner, determine UWB devices corresponding to one or more bits in the first bitmap. Some or all bits in the first bitmap correspond to list elements in the second DPL. Optionally, the UWB device corresponding to the i-th bit, sequentially arranged in the first bitmap, is the UWB device corresponding to the i-th list element, sequentially arranged in the second DPL. The i-th list element, arranged sequentially within the second DPL, contains parameter configuration information for the UWB device corresponding to the i-th list element. For example, the second DPL is shown in Table 18. The first bitmap contains 8 bits, and the 8 bits arranged sequentially within the first bitmap correspond to the 0th UWB device, the 1st UWB device, the 2nd UWB device, ..., the 7th UWB device.

[0331] 905: If the i-th bit is set to a specified value, determine the location of the parameter configuration information for the i-th UWB device in the first DPL.

[0332] For step 905, please refer to step 803.

[0333] In the embodiments of this application, the transmitter transmits a second message to the receiver, and the receiver, based on the second message, determines the correspondence between bits in a first bitmap subsequently transmitted by the transmitter and the UWB device, and indicates the location of the parameter configuration information of the UWB device in the DPL based on the first bitmap, so that the device address in the list element can be omitted and the signaling overhead for updating the list element can be reduced.

[0334] Next, examples of the format of list elements in DPL are described in Table 16. In these examples, according to the method in the embodiments of this application, the list elements in DPL do not include the device address or identification information of another device in order to shorten the length of the list elements. Tables 19 to 27 show some possible formats of list elements in DPL.

[0335] [Table 21]

[0336] The list elements in Table 19 indicate the time units occupied by the UWB device corresponding to the list element when transmitting UWB signals. The bitmap offset is used to determine the start time unit in which the UWB device corresponding to the list element (hereinafter referred to as UWB device 1) transmits UWB signals. The time unit bitmap indicates whether the time unit is used by the UWB device corresponding to the list element to transmit UWB signals. The time unit corresponding to the initial bit of the time unit bitmap is the start time unit. The bitmap offset is used to determine the time unit corresponding to the initial bit of the time unit bitmap, and it can be understood that the time unit corresponding to each bit in the time unit bitmap may be determined based on the bitmap offset and the time unit bitmap. The bitmap size field indicates the length of the time unit bitmap.

[0337] See Table 19. The bitmap size field occupies 2 bits, i.e., bits 0 and 1; the bitmap offset occupies 4 bits, i.e., bits 2 through 5; the reserved field occupies 2 bits, i.e., bits 6 and 7; and the time unit bitmap occupies one or more octets, i.e., the length of the time unit bitmap is variable. Table 19 is merely an example of list elements in DPL, and it should be understood that the number of bits occupied by each field and the position of each field in the list element are not limited.

[0338] [Table 22]

[0339] See Table 20. The bitmap size field occupies 2 bits, i.e., bits 0 and 1; the Bitmap Offset Presence field occupies 1 bit, i.e., bit 2; the reserved field occupies 5 bits, i.e., bits 3 through 7; the time unit bitmap occupies one or more octets, i.e., the length of the time unit bitmap is a variable value; the bitmap offset occupies 4 bits, i.e., bits 0 through 3; and the reserved field occupies 4 bits, i.e., bits 4 through 7. The Bitmap Offset Presence field indicates whether a list element contains a Bitmap Offset field. For example, when Bitmap Offset Presence=1, the Bitmap Offset field appears, i.e., the list element contains a Bitmap Offset field. When Bitmap Offset Presence=0, the Bitmap Offset field does not appear, i.e., the list element does not contain a Bitmap Offset field. Table 20 is merely an example of list elements in DPL, and it should be understood that the number of bits occupied by each field and the position of each field in the list element are not limited. For the function of each field in Table 20, please refer to Table 19.

[0340] [Table 23]

[0341] Please refer to Table 21. The reserved field occupies 1 bit, i.e., bit 15; the Starting Slot Index field occupies 7 bits; the Period Index field occupies 4 bits; and the Repetition Index field occupies 4 bits. The Starting Slot Index field indicates the start time unit when UWB device 1 transmits a UWB signal; the Period Index field indicates the scheduling period when UWB device 1 transmits a UWB signal; and the Repetition Index field indicates the number of repetitions when UWB device 1 transmits a UWB signal. Table 21 is merely an example of list elements in the DPL, and it should be understood that the number of bits occupied by each field and the position of each field in the list elements are not limited.

[0342] [Table 24]

[0343] Please refer to Table 22. The Rangering Role field and Receiver Address Presence field (receiver address presence field) in the prior art appear in the format of the list elements provided in the embodiments of this application. It should be understood that Table 22 is merely an example of list elements in DPL, and the number of bits occupied by each field and the position of each field in the list elements are not limited. In other words, the scheduling information provided in the embodiments of this application may allow the Rangering Role field and Receiver Address Presence field to appear, or may allow either the Rangering Role field or the Receiver Address Presence field to appear, for example, as shown in the following forms in Tables 23 and 24 below. This is not limited to the embodiments of this application.

[0344] [Table 25]

[0345] [Table 26]

[0346] Tables 22, 23, and 24 show examples of how fields from the prior art (e.g., the Ranged Role field and the Receiver Address Presence field) may be placed in the list elements provided in embodiments of this application. It should be understood that other fields from the prior art may be further placed in the list elements provided in embodiments of this application. For example, the Receiver Address and Presence fields shown in Tables 22-24 may be placed in the list elements as shown in Table 20. In other words, the Receiver Address and Presence fields may be located in the same list element along with the Bitmap Offset field, Bitmap field, Bitmap Size field, and Bitmap Offset Presence field. The order, position, and field size of fields such as the Bitmap Offset field, Ranged Role field, Receiver Address Presence field, Starting Slot Index field, Period Index field, and Repetition Index field are not limited to embodiments of this application. Tables 22, 23, and 24 are examples only.

[0347] [Table 27]

[0348] In Table 25, bit 0 is the Period Mode field. For example, fields related to the transmission period, such as the Starting Slot Index field, the Period Index field, and the Repetition Index field, appear and are valid only when Period Mode=1. Fields related to the transmission period, such as the Starting Slot Index field, the Period Index field, and the Repetition Index field, are not valid when Period Mode=0. It should be understood that Table 25 is merely an example of list elements in the DPL, and the number of bits occupied by each field and the position of each field in the list elements are not limited.

[0349] Please refer to Table 26. Embodiments of this application may be combined with list elements that include a slot index field.

[0350] [Table 28]

[0351] In Table 26, the meanings of the Ranged Role field and the Ranged Slot Index field are the same as in Table 4. The difference between Table 26 and Table 4 is that Table 26 does not include the device address field, i.e., address. According to the solution in the embodiments of this application, the list elements are compressed in Table 26. It should be understood that Table 26 is merely an example of list elements in DPL, and the number of bits occupied by each field and the position of each field in the list elements are not limited. Furthermore, the list elements provided in the embodiments of this application may, alternatively, be permitted to not include the Ranged Role field, as shown in Table 27.

[0352] [Table 29]

[0353] Table 27 is merely an example of list elements within a DPL, and it should be understood that the number of bits occupied by each field and the position of each field within the list element are not limited.

[0354] Furthermore, when there are no slots within the gap between adjacent slots on the scheduled device, the Range Slot Index field in the list element shown in Table 27 may be omitted, meaning the list element may not exist. In other words, each bit in the bitmap-based CPDID field shown in Table 12 represents both the corresponding device and the corresponding slot.

[0355] Tables 19 through 27 illustrate some examples of possible list elements. This is not particularly limited in the present invention. In other words, if any one or more list elements do not contain a device address, the invention falls within its scope of protection.

[0356] The above describes a proposed technique in which the first bitmap indicates the location of the parameter configuration information of a UWB device within the DPL. Below, we will describe a solution in which the UWB device identifier (which can be thought of as a shorter device address) indicates the location of the parameter configuration information of a UWB device within the DPL.

[0357] Figure 10 is an interaction flowchart of another communication method for UWB according to one embodiment of the present application. The method procedure in Figure 10 is applicable to scenarios with a large number of receivers (e.g., more than 16 receivers). As shown in Figure 10, the method includes the following steps:

[0358] 1001: The transmitter generates the first message.

[0359] The transmitter may be a UWB device that supports the UWB standard. The transmitter may be an AP or a station. The transmitter may be an FFD or an RFD. The transmitter may be a ranging, sensing, positioning, or communication initiator, i.e., a ranging initiator, sensing initiator, positioning initiator, or communication initiator; or a ranging, sensing, positioning, or communication responder, i.e., a ranging responder, sensing responder, positioning responder, or communication responder; or a third-party device (which may be called a controller device), i.e., not a ranging, sensing, positioning, or communication initiator or responder. For example, the transmitter is an initiator and the first message is a measurement start message or a polling / start POLL message. The measurement start message may be a SOR message, a sensing start message, a positioning start message, or a communication start message.

[0360] The first message includes a first list element, which includes parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device. The identifier for the i-th UWB device indicates the order of the list element for the i-th UWB device in the second message, within the second DPL. The identifier for the i-th UWB device corresponds to the device address of the i-th UWB device. The identifier for the i-th UWB device can be considered as the ID of the i-th UWB device. In embodiments of this application, the UWB device identifier may be referred to as a temporary shorter device ID (TSDID) or by another name, not limited to this application. The second message is information transmitted before the first message is transmitted, and the second message carries the address of the i-th UWB device. The second DPL is included in the second message. For example, the first message contains the first DPL, the first list element is a list element within the first DPL, the second message contains the second DPL, the identifier of the i-th UWB device indicates the order of the list elements of the i-th UWB device in the second message within the second DPL. The list elements within the second DPL are arranged in order. In other words, the list elements within the second DPL are arranged in order.

[0361] 1002: The transmitter sends the first message.

[0362] In response, one or more receivers receive the first message. For example, the transmitter is both the initiator and the controller, and the receiver is the responder. In another example, the transmitter is the controller and the receiver is the responder.

[0363] In possible implementations, the first message further includes a first field, the first field indicating the use of an identifier for the i-th UWB device to identify the location of the i-th UWB device's parameter configuration information within the first DPL. It can be understood that the first field indicates the use of an identifier for the UWB device to identify the location of the UWB device's parameter configuration information within the first DPL. The first field may be referred to as the address size field or another field, which is not limited herein. The device parameters management (DPM) field in the first message includes the first DPL, which is used to update the parameter configuration information for one or more responders. The name device parameters management DPM is not limited herein and is merely an example. Table 28-1 shows an example of a device parameters management field in the first message. For the function of each field in Table 28-1, see the function of each field in Table 16.

[0364] [Table 30]

[0365] The CPDID Size field in Table 28-1 is either invalid or does not contain a CPDID Size field. The Address Size field in Table 28-1 may be considered the first field. Table 28-2 shows examples of the meaning of the values ​​for the first field.

[0366] [Table 31]

[0367] The values ​​of the first field in Table 28-2 are merely examples and are not limiting. In this implementation, the first field indicates that the identifier of the i-th UWB device is used to identify the location of the parameter configuration information of the i-th UWB device within the first DPL, and as a result, the receiver knows the location of the parameter configuration information within the first DPL based on the first field, and the location of the parameter configuration information of the UWB device is identified by the identifier of the UWB device.

[0368] 1003: The receiver determines the first list element based on the identifier of the i-th UWB device.

[0369] Before performing step 1003, the receiver can know the identifier of the i-th UWB device. For example, before receiving the first message, the receiver receives a configuration message and determines the identifier of the i-th UWB device based on the configuration message. For example, in the SOR message broadcast by the transmitter to all responders participating in ranging before the initial ranging round, each list element in the DPL uses the actual address of the device, i.e., the device address (2 or 8 octets). In the process of parsing the DPL, each receiver knows the order in which the receiver's list elements appear in the DPL and records that order as the receiver's identifier. For example, the receiver records the order of the list elements of the i-th UWB device in the second message in the second DPL and uses that order as the identifier of the i-th UWB device.

[0370] Step 1003 can be understood as the receiver determining a first list element in the first message containing parameter configuration information for the i-th UWB device based on the identifier of the i-th UWB device. It can be understood that any receiver may determine a list element in the first message containing parameter configuration information for the UWB device based on the identifier of the UWB device. The identifier of the i-th UWB device occupies less than two octets. For example, the identifier of the i-th UWB device occupies one node. The technical essence of the embodiments of this application is to replace the device identifier in the list element in the first DPL with a shorter TSDID in order to reduce signaling overhead.

[0371] In embodiments of this application, the receiver can determine a list element in a first message containing parameter configuration information for a UWB device based on the identifier of the UWB device. Since a TSDID is used, the device identifier in the list element is changed from a 2-octet or 8-octet device address to a 1-octet TSDID. This reduces signaling consumption.

[0372] Figure 11 is an interaction flowchart of another communication method for UWB according to one embodiment of the present application. The method procedure in Figure 11 is a possible implementation of the method described in Figure 10. In this implementation, the transmitter sends a second message to the receiver so that the receiver determines the identifier of the UWB device. As shown in Figure 11, the method includes the following steps:

[0373] 1101: The transmitter sends a second message.

[0374] In response, one or more receivers receive the first message. For example, the transmitter is both the initiator and the controller, and the receivers are the responders. In another example, the transmitter is the controller and the receivers are the responders. The second message may be a broadcast message. For example, the second message may be a SOR message or POLL message broadcast by the transmitter to all responders participating in the measurement before the initial measurement round.

[0375] The second message contains the address of the i-th UWB device, where i is a non-negative integer. For example, the second message contains a second DPL, which contains one or more list elements, each containing the address of a UWB device (2 or 8 octets). In this example, the list elements in the second DPL are arranged in order, and the i-th list element in the second DPL contains the address of the i-th UWB device. In other words, the i-th list element in the second DPL is the list element of the i-th UWB device in the second message. Table 28-3 shows an example of a second DPL.

[0376] [Table 32]

[0377] Please refer to Table 28-3. The list elements arranged sequentially within the second DPL are list element #0 to list element #4, corresponding to the 0th UWB device to the 4th UWB device, respectively. In subsequent measurement rounds, the 0th UWB device to the 4th UWB device will use TSDID 0, 1, 2, 3, and 4, respectively. For example, the 0th UWB device will use TSDID 0 in subsequent measurement rounds. In another example, the 1st UWB device will use TSDID 1 in subsequent measurement rounds.

[0378] 1102: The receiver determines the order in the DPL of the list elements of the i-th UWB device in the second message and records that order as the identifier of the i-th UWB device.

[0379] The receiver may be the i-th UWB device. In other words, the receiver may determine the order of the list elements of receivers in the second message within the DPL and record that order as the receiver identifier. Alternatively, the receiver may not be the i-th UWB device.

[0380] 1103: The transmitter sends the first message.

[0381] For step 1103, please refer to step 1001.

[0382] 1104: The receiver determines the first list element based on the identifier of the i-th UWB device.

[0383] For step 1104, see step 1003. For example, the first message contains the first DPL, the first list element is a list element within the first DPL, and the first list element contains the identifier of the i-th UWB device. Based on the identifier of the i-th UWB device, the receiver determines the first list element within the first DPL, i.e., the list element containing the parameter configuration information of the i-th UWB device. Table 28-4 shows an example of the first DPL in the first message.

[0384] [Table 33]

[0385] Refer to Table 28-4. The first DPL contains list elements corresponding to the 0th UWB device, the 4th UWB device, and the 5th UWB device, respectively. List element #0 contains the parameter configuration information for the 0th UWB device, list element #1 contains the parameter configuration information for the 4th UWB device, and list element #2 contains the parameter configuration information for the 5th UWB device. Assume that in subsequent rounds, the parameter settings for the 0th UWB device, the 4th UWB device, and the 5th UWB device need to be updated. The transmitter may send a first message carrying the first DPL shown in Table 28-4. List element #1 in Table 28-4 is used as an example. Table 29 shows an example of the format of the list elements.

[0386] [Table 34]

[0387] Table 29 shows that in the list element corresponding to the fourth UWB device within the first DPL, the device address (2 or 8 octets) of the fourth UWB device is directly replaced with the TSDID (1 octet length) of the fourth UWB device, reducing the signaling overhead of the list element. The last column of Table 29 is the identifier of the fourth UWB device, i.e., the TSDID of the fourth UWB device. Table 29 shows the possible formats of the list elements (included in the DPL) in Table 28-1. The possible formats of the list elements in Table 28-1 involve adding the TSDID of the UWB device to any of the list elements shown in Tables 19 through 27, and the position of the added TSDID of the UWB device is not limited.

[0388] It can be understood that any receiver may determine a list element in a first message containing the receiver's parameter configuration information based on the receiver's identifier. For example, the i-th UWB device may determine a first list element based on the identifier of the i-th UWB device, and then update the parameter configuration of the i-th UWB device based on the first list element. In another example, after determining a first list element based on the identifier of the i-th UWB device, the i-th UWB device may determine the time units it can occupy by transmitting UWB signals based on the first list element.

[0389] A modification of the method shown in Figures 10 and 11 is as follows: In the NBA-MMS UWB system, the controller directly uses a one-octet device address as the device identifier in subsequent measurement rounds during an earlier time phase, such as the device discovery phase or the connection phase. In other words, according to the modified method, a shorter one-octet device address may be used directly in the initial and subsequent SOR messages, and the compressed device address does not need to be additionally determined in the manner shown in the embodiments described above.

[0390] In embodiments of this application, the receiver can determine a list element in a first message containing parameter configuration information for a UWB device based on the identifier of the UWB device. Since a TSDID is used, the device identifier in the list element is changed from a 2-octet or 8-octet device address to a 1-octet TSDID. This reduces signaling consumption.

[0391] The method procedures shown in Figures 8 to 10 are, in fact, solutions for compressed device addresses. It should be understood that the compressed device address solutions provided in this application are applicable to multiple messages, including, but are not limited to, ADV-POLL / ADV-RESP / SOR messages, POLL / RESP / REPORT messages, and any other messages that can carry a compression method. The compressed device address solutions provided in this application are applicable to multiple frame formats, including, but are not limited to, frame formats based on compressed MAC Header IE shown in Tables 1-1 and 1-2, frame formats based on compressed PSDU shown in Tables 38 to 40 below, and frame formats based on nested IE. The compressed device address solutions provided in this application are also applicable to messages based on various message and frame format combinations. For example, a message in an embodiment of this application may be carried in an ADV-POLL / ADV-RESP / SOR message based on a compressed MAC header IE format, i.e., the field carrying the DPL is included in the content field of the format shown in Table 1-2. In other examples, the messages in the embodiments of this application may alternatively be carried in POLL / RESP / REPORT messages based on a compressed PSDU format, i.e., the fields carrying the DPL are included in the content field in the format shown in Table 37. In conclusion, regardless of the message / frame format, any message / frame format that essentially includes the compressed device address provided in this application falls within the scope of protection of this application.

[0392] The above describes a device address compression method designed in this application to reduce the proportion of device addresses in the configuration information list and further reduce the signaling overhead of the configuration information list. The following describes an optimized solution for the initialization phase of a one-to-many NBA-MMS UWB provided in an embodiment of this application.

[0393] The initialization procedure shown in Figure 3 is applicable to the one-to-one case. In the one-to-many case, the initiator can receive multiple ADV-RESP messages, and these multiple ADV-RESP messages are from responders responding to ADV-POLL messages. In this case, the initiator cannot know in advance which responders will respond to ADV-POLL messages, and therefore cannot receive ADV-RESP messages sent by responders performing NBA-MMS UWB measurements in a scheduling manner. The number of responders that the initiator can process and access is limited, and the initiator consumes a large amount of energy while waiting for the reception of ADV-RESP messages for extended periods. Embodiments of this application provide a solution in which the initiator indicates a contention-based access period (CAP) in a broadcast ADV-POLL message or another message. CAP is used for multiple responders to compete to report ADV-RESP messages. In the next one-to-many NBA-MMS UWB measurement round, only responders that successfully acquire a channel through competition and upload an ADV-RESP message in the CAP phase can be served by the initiator. Figure 12 is a diagram of the one-to-many NBA-MMS UWB initialization phase according to one embodiment of the present application. As shown in Figure 12, the initiator indicates CAP in a broadcast ADV-POLL message, and multiple responders report ADV-RESP messages in a competition manner in CAP. The initiator serves responders that successfully acquire a channel through competition and upload an ADV-RESP message in the CAP phase. The SOR message sent by the initiator carries information indicating when the initiator will send the next SOR message.The competition-based access processing methods used in the CAP phase are not limited to the embodiments of this application, as long as the competition-based access method can effectively process multiple ADV-RESP messages in the CAP phase. The competition-based access processing methods used in the CAP phase include, but are not limited to, carrier sense multiple access with collision avoidance (CSMA-CA), randomization, and access based on received signal strength (if a collision occurs, responders corresponding to ADV-RESP messages with higher received signal strength can perform access, while responders corresponding to ADV-RESP messages with lower received signal strength cannot).

[0394] As shown in Figure 12, after the initiator and responder complete the handshake connection by exchanging ADV-POLL and ADV-RESP, the initiator broadcasts an SOR message to determine the parameter configuration used by the NBA-MMS measurement round, and the initiator and responder(s) perform one-to-many NBA-MMS UWB measurements based on the parameter configuration. After the measurement round is completed, the NBA-MMS UWB system may need to update parameters, such as the update duration of the measurement round, the number of MMS fragments, and the channels used by the NB. As shown in Figure 12, before a new measurement round starts, the initiator must send an SOR message containing the updated parameters to the responder. In this case, if a slot for receiving SOR messages is not pre-specified, the responder does not know when it will receive a potentially updated SOR message. Consequently, the responder may respond to potentially updated SOR messages during the pause between updated and unupdated measurement rounds, and a large amount of undecided energy is consumed by the responder. Therefore, in order to ensure that the responder can pre-turn on the receiver at a specific moment before each round to receive potentially updated SOR messages, thus avoiding energy waste by the responder, in each SOR message, the initiator may, based on the requirements, indicate in the SOR message the slot in which the next SOR message will appear. For example, as shown in Figure 12, the SOR message may carry a Time offset for the next SOR, which is used to help the responder determine the arrival slot for the next, possibly updated, SOR message.

[0395] Figure 13 is an interaction flowchart of another communication method for UWB according to one embodiment of the present application. As shown in Figure 13, the method includes the following steps:

[0396] 1301: The first device sends the first message.

[0397] In response, one or more second devices receive a first message. The first message indicates the expiration of a CAP, which is the period during which a response message to the first message is permitted. The first message is included in a measurement start message or a pole / start pole message. A measurement start message may be a SOR message, a sensing start message, a positioning start message, or a communication start message. The first device may be an AP or a station. The first device may be an FFD or an RFD. The first device may be a ranging, sensing, positioning, or communication initiator, i.e., a ranging initiator, sensing initiator, positioning initiator, or communication initiator, or it may be a third-party device (which may be called a controller device), i.e., it may not be a ranging, sensing, positioning, or communication initiator or responder. For example, the first device is the initiator, the first message is an ADV-POLL message, which notifies all responders that an NBA-MMS UWB measurement needs to be performed now. The second device is a responder.

[0398] In possible implementations, the first message includes a first field indicating the expiration date of the CAP. The first field may be referred to as the ADV-RESP CAP Timeout field or another field. For example, the first message is an ADV-RESP message, and the first field is carried in the content field shown in Table 1-2. Table 30-1 shows an example of a content field that carries the first field.

[0399] [Table 35]

[0400] Protocol Version Presence is used to control whether or not the Protocol Version field exists. For example, Protocol Version Presence=0 indicates that the Protocol Version field does not exist. Protocol Version Presence=1 indicates that the Protocol Version field exists.

[0401] Advertising Identity Presence is used to control the presence or absence of the Advertising Identity field. For example, Advertising Identity Presence=0 indicates that the Advertising Identity field does not exist. Advertising Identity Presence=1 indicates that the Advertising Identity field exists.

[0402] ADV-RESP CAP Timeout Presence is used to control whether or not the ADV-RESP CAP Timeout field exists. For example, if ADV-RESP CAP Timeout Presence=0, it indicates that the ADV-RESP CAP Timeout field does not exist. If ADV-RESP CAP Timeout Presence=1, it indicates that the ADV-RESP CAP Timeout field exists.

[0403] The protocol version indicates the protocol version used by the current UWB application.

[0404] Advertising Identity indicates the type of ADV-POLL message.

[0405] ADV-RESP CAP Timeout indicates the expiration date (or end date) of the CAP phase.

[0406] If the current ADV-POLL message does not contain an ADV-RESP CAP Timeout field (i.e., the corresponding ADV-RESP CAP Timeout Presence=0), the system's default value for ADV-RESP CAP Timeout is reused by default.

[0407] Furthermore, if ADV-POLL is a broadcast message, the Address field shown in Table 1-2 should use the broadcast address, for example, 0xFFFF.

[0408] In possible implementations, the first message further includes information indicating the CAP start time. For example, the CAP start time is the end time at which the first device sends the first message. In another example, the CAP start time is a slot after the end time at which the first device sends the first message. Another example of a content field carrying the first field is to add an ADV-RESP CAP start field to the content field shown in Table 30-1, where the ADV-RESP CAP start field indicates the CAP start time. Table 30-2 shows another example of a content field carrying the first field.

[0409] [Table 36]

[0410] Compared to Table 30-1, Table 30-2 adds the ADV-RESP CAP Start field and presence control field, i.e., the ADV-RESP CAP Start Presence field, which corresponds to the ADV-RESP CAP Start field. ADV-RESP CAP Start Presence is used to control whether or not the ADV-RESP CAP Start field exists. For example, ADV-RESP CAP Start Presence=0 indicates that the ADV-RESP CAP Start field does not exist. ADV-RESP CAP Start Presence=1 indicates that the ADV-RESP CAP Start field exists. The ADV-RESP CAP Start field indicates the start time of the CAP. In addition to the ADV-POLL messages shown in Table 30-2, the instruction scheme may alternatively be based on other messages that include, but are not limited to, instruction messages in time phases prior to the initialization and setup process. Details are not described here. In this implementation, the first message further includes information indicating the start time of the CAP, thereby allowing the responder to learn the start time of the CAP. This makes it possible to reduce the power consumption of the responder.

[0411] 1302: The target's second device sends a second message to the first device before the CAP expires.

[0412] The second message contains the second parameter configuration information for the target's second device. The second message may also be an ADV-RESP message carrying the parameter configuration information required by the target's second device. For example, the first message is an ADV-POLL message used to notify all responders that NBA-MMS UWB ranging needs to be performed now. After the target's second device (responder) receives the ADV-POLL message, if ranging needs to be performed, the target's second device feeds back an ADV-RESP (Advertisement-RESPONSE) message to the first device (initiator). The ADV-RESP message carries the parameter configuration information required by the first device. The target's second device is the second device that receives the first message and successfully acquires the channel through the conflict before the CAP expires. It should be understood that any second device that receives the first message and successfully acquires the channel through the conflict before the CAP expires may perform similar actions to the target's second device. For example, before step 1302 is executed, the target's second device conflicts for a channel, and after acquiring the channel through the conflict before the CAP expires, the target's second device sends the second message through the channel acquired through the conflict.

[0413] In possible implementations, the target's second device (i.e., the responder) listens for SOR messages in a slot after the CAP phase. For example, the slot after the CAP phase may be the slot immediately following the CAP phase, or any other slot. In other words, the initiator can broadcast an initial SOR message, i.e., the following third message, in the first or another slot after the CAP phase has finished.

[0414] 1303: The first device sends the third message.

[0415] In response, one or more second devices receive a third message. The third message may include first parameter configuration information for some or all of the multiple second devices, and information indicating when the fourth message is sent. For example, the third message is a SOR message sent by the first device for an ADV-RESP message, i.e., a second message sent by multiple second devices (responders). The SOR message may carry an acknowledgment message for the parameter configuration information in the ADV-RESP message sent by the second device, or it may carry a change / update message for the parameter configuration information in the ADV-RESP message sent by the second device. In embodiments of this application, both the acknowledgment message for the parameter configuration information in the ADV-RESP message sent by the second device and the change / update message for the parameter configuration information in the ADV-RESP message sent by the second device may be considered as the first parameter configuration information of the second device. The fourth message is used to update the first parameter configuration information of at least one of the multiple or all of the second devices. The fourth message may be a SOR message or POLL message sent by the first device after the first device has sent the third message.

[0416] In possible implementations, the third message includes a second field, which indicates that the third message contains information indicating the time when the fourth message is sent. The second field may be referred to as the Time offset for the next SOR Presence field or another field. The third message may further include the addresses of some or all of the second devices. A field within the third message that indicates the moment when the fourth message is sent may be referred to as the Time offset for the next SOR field. For example, the third message is a SOR message, and the second field is carried by the content field shown in Table 1-2. Table 31 shows an example of a content field carrying the second field.

[0417] [Table 37]

[0418] Device Parameters Management enabled is used to control whether or not the DPM field exists. For example, if Device Parameters Management enabled=0, it indicates that the DPM field does not exist. If Device Parameters Management enabled=1, it indicates that the DPM field exists.

[0419] The Time offset for the next SOR Presence, i.e., the second field, is used to control whether or not the Time offset for the next SOR field exists. For example, if Time offset for the next SOR Presence = 0, it indicates that the Time offset for the next SOR field does not exist. If Time offset for the next SOR Presence = 1, it indicates that the Time offset for the next SOR field exists.

[0420] Device Parameters Management is a field for managing device parameters. If multiple devices exist, the field is a list field.

[0421] The Time offset for the next SOR indicates the moment when the fourth message is transmitted. For example, the Time offset for the next SOR indicates the time elapsed from the currently broadcasting SOR message (i.e., the third message) to the next SOR message. The unit of the time elapsed may be ranging scheduling time units (RSTUs) or slots. The unit of the time elapsed is not limited in this application.

[0422] Table 32 shows an example of the DPM field format.

[0423] [Table 38]

[0424] Address Size indicates the type of device address within the DPL. For example, if the Address Size value is 0, all list elements in the DPL use short addresses to identify devices. If the Address Size value is 1, all list elements in the DPL use long addresses to identify devices. Device Parameter List Length indicates the number of elements in the DPL. Table 33 shows an example of the DPL field format.

[0425] [Table 39]

[0426] Device Parameters List Element#0 is a list element within the DPL. Table 34 shows an example of the format of a list element within the DPL.

[0427] [Table 40]

[0428] The Channel configuration Presence parameter is used to control whether or not the Channel configuration field exists. For example, Channel configuration Presence=0 indicates that the Channel configuration field does not exist. Channel configuration Presence=1 indicates that the Channel configuration field exists.

[0429] The MMS fragment configuration Presence parameter is used to control whether or not an MMS fragment configuration field exists. For example, when MMS fragment configuration Presence = 0, it indicates that the MMS fragment configuration field does not exist. When MMS fragment configuration Presence = 1, it indicates that the MMS fragment configuration field exists.

[0430] The MMS preamble parameter presence is used to control whether or not an MMS preamble parameter field exists. For example, when MMS preamble parameters Presence = 0, it indicates that the MMS preamble parameter field does not exist. When MMS preamble parameters Presence = 1, it indicates that the MMS preamble parameter field exists.

[0431] NB data rate Presence is used to control whether or not the NB data rate field exists. For example, NB data rate Presence=0 indicates that the NB data rate field does not exist. NB data rate Presence=1 indicates that the NB data rate field exists.

[0432] The Time Offset to Next MMS POLL Packet Presence parameter is used to control whether or not the Time Offset to Next MMS POLL Packet field exists. For example, if Time Offset to Next MMS POLL Packet Presence = 0, this indicates that the Time Offset to Next MMS POLL Packet field does not exist. If Time Offset to Next MMS POLL Packet Presence = 1, this indicates that the Time Offset to Next MMS POLL Packet field exists.

[0433] The channel configuration field is used to configure the channels required for NBA-MMS UWB ranging.

[0434] The MMS fragment configuration field is used to configure the parameters required in the MMS process of NBA-MMS UWB ranging, such as the number of fragments in the MMS process.

[0435] The MMS preamble parameter field is used to configure the relevant parameter configuration of the preamble used by the fragments required in the MMS process of NBA-MMS UWB ranging.

[0436] The following Time Offset to Next MMS POLL Packet is used to define the time length from the time the current device receives the SOR message to the time the initiator initiates the POLL message. The unit of the time length may be a Range Scheduling Time Unit (RSTU) or a slot. The unit of the time length is not limited in this invention.

[0437] The Address field indicates the device address. Further details will not be explained here.

[0438] Furthermore, when a SOR message is a broadcast message, the Address field shown in Table 1-2 uses the broadcast address, for example, 0xFFFF.

[0439] 1304: Based on the third message, the target's second device determines the parameter configuration information of the target's second device and the time when the first device sends the fourth message.

[0440] In some embodiments, a first device (initiator) and responders (including the second target device) may initiate the NBA-MMS UWB ranging process a certain period after the second target device receives a third message. The length of this period may be determined based on Time offset to MMS POLL information, which is included in the third message.

[0441] 1305: The target's second device determines, based on the third message, that the i-th list element, sequentially placed within the second DPL, contains the parameter configuration information for the corresponding i-th UWB device.

[0442] i is an integer greater than 0. Alternatively, the receiver determines, based on the third message, that the i-th list element, arranged sequentially within the second DPL, contains the parameter configuration information for the i-th UWB device. The target second device may or may not be the i-th UWB device. The third message contains the second DPL, which contains one or more sequentially arranged list elements, and any list element within the second DPL contains the address of the UWB device corresponding to that list element. Table 18 is an example of the second DPL. The i-th list element, arranged sequentially within the second DPL, contains the parameter configuration information for the corresponding i-th UWB device. The order of steps 1305 and 1304 is not limited.

[0443] 1306: The first device sends the fourth message.

[0444] Correspondingly, one or more second devices receive a fourth message. A target second device among the one or more second devices is used as an example. The target second device may begin responding to the fourth message, which may be sent by the first device, at the time the first device sends the fourth message, as determined by the target second device. The fourth message may be a SOR message used to update the parameter configuration of one or more second devices. The fourth message may include a first bitmap, which contains N bits. The i-th bit in the first bitmap corresponds to the i-th UWB device. If the i-th bit is set to a specified value, the i-th bit indicates the location of the first parameter configuration information for the i-th UWB device in the first DPL. i is between 1 and N, and N is an integer greater than 0. The first DPL is included in the fourth message.

[0445] In possible implementations, the first DPL contains multiple sequentially arranged list elements. If the i-th bit is the f-th bit, which is sequentially arranged in the first bitmap and set to a specified value, then the i-th bit indicates that the f-th list element in the first DPL contains the first parameter configuration information for the i-th UWB device, where F is an integer greater than 0.

[0446] In possible implementations, the fourth message further includes a third field, which indicates the use of a first bitmap to identify the location of the first parameter configuration information of the UWB device within the first DPL.

[0447] In possible implementations, the fourth message further includes a field indicating the length of the first bitmap.

[0448] 1307: The target's second device determines that the i-th bit of the first bitmap corresponds to the i-th UWB device.

[0449] For step 1307, please refer to step 904.

[0450] 1308: The second target device determines the location of the parameter configuration information for the i-th UWB device in the first DPL if the i-th bit is set to the specified value.

[0451] For step 1308, please refer to step 803. For example, the second target device is the i-th UWB device. After determining the location of the parameter configuration information for the i-th UWB device in the first DPL, the second target device can retrieve the parameter configuration information for the second target device and update its parameter configuration based on the retrieved information.

[0452] 1305': The target's second device determines the order of the list elements of the i-th UWB device in the third message within the second DPL and records that order as the identifier of the i-th UWB device.

[0453] The third message carries the address of the i-th UWB device, where i is a non-negative integer. The third message contains a second DPL, which contains one or more sequentially arranged list elements, each containing the address of a UWB device (2 or 8 octets). In this example, the list elements in the second DPL are arranged sequentially, and the i-th sequentially arranged list element in the second DPL contains the address of the i-th UWB device. In other words, the i-th sequentially arranged list element in the second DPL is the list element of the i-th UWB device in the second message. Table 27 shows an example of a second DPL. The order of steps 1305' and 1304 is not limited.

[0454] 1306': The first device sends the fourth message.

[0455] Correspondingly, one or more second devices receive a fourth message. The target second device among the one or more second devices is used as an example. The target second device may begin responding to the fourth message, which may be sent by the first device, at the time the first device sends the fourth message, as determined by the target second device. The fourth message may be a SOR message used to update the parameter configuration of one or more second devices. The fourth message includes a first list element, which includes the first parameter configuration information of the i-th UWB device and the identifier of the i-th UWB device. The identifier of the i-th UWB device indicates the order of the list element of the i-th UWB device in the third message within the second DPL. The second DPL is included in the third message. The i-th UWB device is one of several second devices. Optionally, the identifier occupies less than two octets. For example, the identifier occupies one octet.

[0456] In possible implementations, the fourth message further includes a first field, which indicates that the identifier of the i-th UWB device is used to identify the location of the i-th UWB device's first parameter configuration information within the first DPL.

[0457] 1307': The second target device determines the first list element based on the identifier of the i-th UWB device.

[0458] The first list element contains the first parameter configuration information for the i-th UWB device and the identifier for the i-th UWB device. For step 1307', see step 1003. For example, the second target device is the i-th UWB device. After determining the first list element, the second target device may obtain the parameter configuration information for the second target device and update the parameter configuration of the second target device based on the obtained parameter configuration information.

[0459] It should be noted that steps 1305 to 1308 and steps 1305' to 1307' are all optional. The method procedure in Figure 13 may include steps 1305 to 1308, or steps 1305' to 1307', or only steps 1301 to 1304.

[0460] In possible implementations, a third message indicates the termination of the measurement for the current round or the next round to reduce resource overhead and unnecessary measurements. In this implementation, after receiving the third message, the target's second device terminates the measurement for the current round or the next round. When the third message indicates the termination of the measurement for the current round, it may carry information indicating the termination of the measurement for the current round, but does not need to carry parameter configuration information and information indicating when the fourth message is sent. When the third message indicates the termination of the measurement for the next round, it may carry parameter configuration information and information indicating the termination of the measurement for the next round, but does not need to carry information indicating when the fourth message is sent. The current round and the next round may or may not be temporally adjacent. The information indicating the termination of the measurement for the next round may, alternatively, be expressed in another form. For example, an expiration date may be indicated based on when the fourth message is received to indicate the termination of the measurement for the next round. For example, if the target's second device has not received the fourth message when the expiration date arrives, the measurement for the next round is terminated. In another example, the timing of the reception of the fourth message indicates whether a bit is valid, and when the bit indicates that the timing of the fourth message has expired, it indicates that the measurement for the next round should be terminated. The specific form of the termination instruction is not limited in this invention.

[0461] In possible implementations, the fourth message indicates that the current round of measurement or the next round of measurement should be terminated to reduce resource overhead and unnecessary measurements. In this implementation, after receiving the fourth message, the target's second device terminates the current round of measurement or the next round of measurement. When the fourth message indicates that the current round of measurement should be terminated, it may carry information indicating that the current round of measurement should be terminated, but it does not need to carry parameter configuration information. When the fourth message indicates that the next round of measurement should be terminated, it may carry parameter configuration information and information indicating that the next round of measurement should be terminated.

[0462] In another possible implementation, the fourth message indicates the termination of measurement for one or more measurement rounds. In other words, the fourth message indicates the termination of measurement for one or more rounds of measurement. For example, the fourth message indicates the termination of measurement for multiple measurement rounds, which may or may not be temporally adjacent. In another example, the fourth message indicates the termination of measurement for multiple measurement rounds, which may be located in the same measurement block or in different measurement blocks. A single measurement block contains one or more measurement rounds. Temporarily adjacent may mean that multiple measurement rounds in the same measurement block are adjacent, or that one or more trailing measurement rounds in a previous measurement block are adjacent to one or more leading measurement rounds in the current measurement block.

[0463] In this implementation, the fourth message indicates that one or more measurement rounds will be terminated to reduce resource overhead and unnecessary measurements. Furthermore, the time resources corresponding to the terminated measurement rounds may be used by another measurement procedure.

[0464] In possible implementations, one or more measurement rounds are multiple consecutive measurement rounds.

[0465] In possible implementations, a fourth message indicating the termination of measurement for one or more measurement rounds includes: The fourth message includes identifiers for one or more measurement rounds (e.g., measurement round indices). In other words, the fourth message includes identifiers for one or more measurement rounds for which measurement needs to be terminated.

[0466] In possible implementations, a fourth message indicates the end of measurement for one or more measurement rounds, where a value F contained in the fourth message indicates the end of measurement for the Fth measurement round, and F is a non-negative integer, and the Fth measurement round is included in one or more measurement rounds. For example, the current measurement round, i.e., round 1, is used as the reference point and indicates the end of measurement for round (measurement round) relative to round 1. For example, a value of 0 indicates that measurement for round 1 has ended, i.e., measurement for the current measurement round has ended, and a value of 1 indicates that measurement for round 2 has ended.

[0467] In possible implementations, a fourth message indicating the completion of measurement for one or more measurement rounds may include: The fourth message indicating the completion of measurement for all remaining measurement rounds. For example, a specific value included in the fourth message indicates that measurement for all remaining rounds has been completed. For example, the specific value is the maximum value of a field occupied by a particular value.

[0468] In possible implementations, a fourth message indicating the end of measurement for one or more measurement rounds includes the following: the fourth message includes a second bitmap, the j-th bit in the second bitmap corresponds to the j-th measurement round, and if the j-th bit is set to a specified value, the j-th bit indicates the end of the j-th measurement round, the j-th measurement round is included in one or more measurement rounds, and j is a non-negative integer.

[0469] In possible implementations, one or more measurement rounds are multiple consecutive measurement rounds. The fourth message indicating the end of measurement for one or more measurement rounds includes the fourth message containing a first value and a second value, where the first value indicates the initial measurement round in multiple consecutive measurement rounds, and the second value indicates the final measurement round in multiple consecutive measurement rounds.

[0470] In possible implementations, the fourth message includes a target field, and when the target field is set to the first value, it indicates that the fourth message has completed the measurement round.

[0471] The following provides some examples of how a fourth message indicates the termination of one or more measurement rounds.

[0472] Example 1: The fourth message indicates the termination of measurement for multiple consecutive measurement rounds (hereafter rounds). The fourth message includes a value (which may be called the measurement termination indicator value). When the value is N, it indicates the termination of measurement for all assigned measurement rounds (including the current measurement block and the Nth measurement block) from round #i (i.e., measurement round #i) in the current measurement block (hereafter block) to round #i in the subsequent Nth block. i is a non-negative integer and represents the index value of the round. For example, suppose one measurement block contains multiple measurement rounds, and the current measurement round is measurement round 1. When the measurement termination indicator value N in the fourth message is equal to 2, the distance measurement for a total of three measurement rounds is terminated, where the three measurement rounds include the current measurement round and two subsequent measurement rounds, e.g., round 1, round 2, and round 3, as shown in Figure 14A. Figure 14A is a diagram of measurement rounds in measurement block N (Block N) according to one embodiment of the present application. As shown in Figure 14A, round 1, round 2, and round 3 within measurement block N are measurement rounds that need to be completed. Example 2: The fourth message indicates the completion of measurements for multiple consecutive measurement rounds, and the fourth message includes the identifier (e.g., round index) of the last measurement round in the multiple consecutive measurement rounds. The initial measurement round in the multiple consecutive measurement rounds is the current measurement round. The identifier of the last measurement round in the multiple consecutive measurement rounds may be the index of the last measurement round, or it may be an index value relative to the current measurement round (i.e., a relative index value). For example, the current measurement round, i.e., round i, is used as the reference point. The fourth message indicates the completion of distance measurement for subsequent rounds (measurement rounds) relative to round i, for example, the identifier of the last measurement round in the multiple consecutive measurement rounds is F, and it indicates that the measurement of round i + F has been completed.The possible formats for the identifier of the last measurement round in a series of consecutive measurement rounds included in the fourth message are shown in Table 35-1 or Table 35-2.

[0473] [Table 41]

[0474] As shown in Table 35-2, the identifier for the last measurement round in a series of consecutive measurement rounds contained in the fourth message occupies two octets, and the Termination Round Index indicates the index of the last measurement round in a series of consecutive measurement rounds.

[0475] [Table 42]

[0476] As shown in Table 35-2, the identifier of the last measurement round in a series of consecutive measurement rounds included in the fourth message occupies two octets, and the Relative Round Index Termination indicates the index value of the last measurement round in a series of consecutive measurement rounds relative to the current measurement round.

[0477] Example 3: The fourth message indicates the termination of measurement for one or more measurement rounds, and the fourth message includes identifiers for one or more measurement rounds. For example, the fourth message includes identifiers for measurement rounds, and the fourth message indicates the termination of measurement for a measurement round. The format of the measurement round identifiers included in the fourth message may alternatively be similar to the format shown in Table X-1 (for example, relative index values ​​based on the round index may be used, or index values ​​for measurement rounds may be used). Further details are not described here again. In this example, the fourth message may indicate the termination of any round, whether the rounds are consecutive or not, for example, indicating the termination of rounds 3, 6, 8, 10, and 11, or indicating the termination of a single round.

[0478] Example 4: The fourth message includes a second bitmap, where the jth bit of the second bitmap corresponds to the jth measurement round, and if the jth bit is set to a specified value, the jth bit indicates that the jth measurement round is finished, where the jth measurement round is contained in one or more measurement rounds, and j is a non-negative integer. As shown in Table 35-3, it can be seen that the bitmap scheme can flexibly indicate the end of any number of rounds of measurement.

[0479] [Table 43]

[0480] Each bit in the Round Index Bitmap (i.e., the second bitmap) represents a round. A value of 0 for a bit indicates that the measurement of the round is not yet complete, and a value of 1 indicates that the measurement of the round is complete. Bits in the Round Index Bitmap can represent the absolute value of the round index. Alternatively, bits in the Round Index Bitmap may represent the relative value of the round index (i.e., the relative index value), that is, as shown in Table 35-4, the first bit in the Round Index Bitmap represents the current round i, and another subsequent bit represents another subsequent round relative to round i. Further details are not explained here.

[0481] [Table 44]

[0482] In Table 35-4, the first bit in the Relative Round Index Bitmap indicates the current round i, i.e., the current measurement round.

[0483] Example 4: The fourth message indicates the completion of measurements for multiple measurement rounds, where the multiple measurement rounds are contained within two or more measurement blocks, and the fourth message contains identifiers for the multiple measurement rounds. This example is applicable when the current round and subsequent rounds are located in different blocks. For example, Figure 14B shows round 1 in block M-1 and round 1 in block M. Figure 14B is a diagram of the rounds of measurement in measurement block M-1 and measurement block M according to one embodiment of the present application. In another example, Figure 14C shows round 0 in block M-1 and round 1 in block M. Figure 14C is a diagram of the other measurement rounds in measurement block M-1 and measurement block M according to one embodiment of the present application. Possible formats for the identifiers of the measurement rounds contained in the fourth message are shown in Table 35-5 or Table 35-6.

[0484] [Table 45]

[0485] The Block Index field indicates the measurement block in which the measurement round that needs to be completed is located, and the Round Index field indicates the measurement round that needs to be completed. Table 35-5 may contain multiple rows (lists), each row (each list element) indicating a measurement round that needs to be completed.

[0486] [Table 46]

[0487] Each bit in the Block Index Bitmap represents a block. A corresponding value of 0 for a bit indicates that the block does not contain a round from which the measurement must be completed, and a value of 1 indicates that the block contains a round from which the measurement must be completed. Bits in the Block Index Bitmap may also represent the absolute value of the block index. In addition, bits in the Block Index Bitmap may alternatively represent the relative value of the block index (i.e., the relative index value), where the first bit in the Block Index Bitmap represents the current block i, and another subsequent bit represents another subsequent block relative to block i.

[0488] A Round Index Bitmap List contains multiple Round Index Bitmaps; that is, each list element in a Round Index Bitmap List is a Round Index Bitmap. In other words, for each Round Index Bitmap in a Round Index Bitmap List, the bit value corresponding to the block in the Block Index Bitmap where the Round Index Bitmap is located is 1.

[0489] Each bit in the Round Index Bitmap represents a round. A value of 0 for a bit indicates that the measurement of the round is not yet complete, and a value of 1 indicates that the measurement of the round is complete. Bits in the Round Index Bitmap can also represent the absolute value of the round index. Alternatively, bits in the Round Index Bitmap may represent the relative value of the round index (i.e., the relative index value), where the first bit in the Round Index Bitmap represents the current round i, and another subsequent bit represents another subsequent round relative to round i. For example, when the Block Index Bitmap is 00110000, it means that blocks 2 and 3 contain rounds that need to be completed, meaning that the Round Index Bitmap List contains two list elements. The first list element is the Round Index Bitmap corresponding to block 2, and the second list element is the Round Index Bitmap corresponding to block 3. Furthermore, if the Round Index Bitmap corresponding to block 2 is 00000111, it means that the measurements for rounds 5, 6, and 7 in block 2 need to be completed. If the Round Index Bitmap corresponding to block 3 is 10011000, it means that the measurements for rounds 0, 3, and 4 in block 3 need to be completed.

[0490] Furthermore, it extends to timing structures including hyper measurement blocks, i.e., cases where the time lengths of different blocks do not have to be the same, or where the number of rounds within different blocks and / or the time lengths of a single round within a block do not have to be the same. Figure 14D shows measurement block M-1 and other measurement rounds in measurement block M according to one embodiment of the present application. As shown in Figure 14D, block M-1 includes three rounds, with round 1 used for measurement between the initiator and the responder. Block M includes four rounds, with round 4 used for measurement between the initiator and the responder. The round length of block M-1 may be the same as or different from the round length of block M. When the hyper measurement block shown in Figure 14D is used for measurement between the initiator and the responder, possible formats for the measurement round identifier included in the fourth message are shown in Table 35-7.

[0491] [Table 47]

[0492] The Hyper Block Index field indicates the hyper block where the measurement round that needs to be completed is located, the Block Index field indicates the measurement block where the measurement round that needs to be completed is located, and the Round Index field indicates the measurement round where the measurement round that needs to be completed is located.

[0493] Example 5: The fourth message directly indicates the block index of the block where the measurement needs to be completed. Regardless of the number of rounds initially used for measurement within the block, the corresponding distance measurement is completed when the block index is indicated. See Table 35-8 for details.

[0494] [Table 48]

[0495] The Termination Block Index indicates the block index of the block whose measurement needs to be terminated. Table 35-8 may contain multiple rows, each row indicating the block index of the block whose measurement needs to be terminated. Alternatively, a fourth message carries the block index, and the fourth message indicates that the measurement from the current block to the block corresponding to the block index is to be terminated.

[0496] Example 6: The fourth message directly indicates a round in the current block where the measurement needs to be terminated, and one or more rounds in the block may have been originally used for the measurement between the current initiator and responder. The corresponding measurement of the round indicated as terminated is terminated. Relative and absolute indications are included. Subsequent blocks reuse the termination method of the current block, i.e., a round in a subsequent block where the measurement needs to be terminated is the same as a round in the current block where the measurement needs to be terminated. Figure 14E is a diagram of other measurement rounds in measurement block M-1 (Block M-1) and measurement block (Block M) according to one embodiment of the present application. As shown in Figure 14E, the gray rounds (i.e., round 1 in each block) indicate the round in the block that is originally used for the measurement between the current initiator and responder. Figure 14F is a diagram of other measurement rounds in measurement block M-1 (Block M-1) and measurement block (Block M) according to one embodiment of the present application. As shown in Figure 14F, the gray rounds (i.e., round 1, round 2, and round 3 within each block) indicate the rounds within the block that are originally used for the measurement between the current initiator and responder. Tables 35-9 and 35-10 show examples of the instruction format for the fourth message.

[0497] [Table 49]

[0498] Table 35-9 shows the rounds that need to be terminated in the current block, using a relative indication method. When Number of rounds to be terminated = 0, it indicates that the measurement of the current round is terminated (assuming the subscript of the current round is i). When Number of rounds to be terminated = N, it indicates that the measurement of rounds from the current round i to round i+N is terminated, where round includes round i and round i+N. A specific value indicates that the measurement of all remaining rounds is terminated.

[0499] For subsequent blocks (not the current block), the same termination method is used, meaning that the measurement of all rounds from round i to round i+N in the subsequent block is terminated, and the round includes round i and round i+N.

[0500] [Table 50]

[0501] Table 35-10 shows the number of rounds that need to be terminated, using an absolute indication method. When Number of rounds to be terminated = 0, it indicates that the measurement of round 0 in the current block should be terminated. When Number of rounds to be terminated = N, it indicates that the measurements of rounds from round 0 to round N in the current block should be terminated, where rounds include round 0 and round N. A specific value indicates that the measurements of all remaining rounds should be terminated.

[0502] For subsequent blocks (not the current block), the same termination method is used, meaning that the measurement of all rounds from round 0 to round N in the subsequent block is terminated, and the rounds include round 0 and round N.

[0503] In embodiments of this application, the first device transmits a first message. The first message indicates the expiration date of the CAP, and as a result, the target second device transmits a second message before the expiration date. This can reduce the duration for which the second message is received in order to reduce energy consumption. The first device transmits a third message. The third message includes information indicating when a fourth message is transmitted. This can reduce the duration for which the target second device allows the receiver to receive an updated SOR message, in order to reduce energy consumption.

[0504] The following further explains the function of the Time offset for the next SOR field in Table 13.

[0505] In possible implementations, when the Time offset for the next SOR field in Table 13 does not exist, i.e., when the Time offset for the next SOR Presence field is 0, the current system reuses the default value of the Time offset for the next SOR field or the last configured value of the Time offset for the next SOR field to indicate a slot for the responder to receive an SOR message for parameter configuration updates. In other words, when the value of the Time offset for the next SOR field uses the default value or reuses the last configured value, the responder periodically listens for SOR messages sent by the initiator for parameter configuration updates, where the period length is the Time offset for the next SOR. Correspondingly, when the initiator updates the time length for receiving the next SOR message in the SOR message within the current total ranging service duration, the responder essentially listens for SOR messages sent by the initiator for parameter configuration updates in a non-periodic manner.

[0506] In possible implementations, the initiator may further configure a function to disable the Time offset for the next SOR field, i.e., the system does not reserve a slot for the responder to receive possible SOR messages for configuration updates. In this case, the responder cannot receive a SOR message for parameter configuration updates in the designated slot and reuses the configuration of the initial SOR message to complete the distance measurement.

[0507] In possible implementations, a Control field is added to enable and disable the Time offset for the next SOR. For example, the third message is a SOR message, and the Time offset for the next SOR field is carried in the content field shown in Table 1-2. Table 36 shows an example of a content field that carries the Time offset for the next SOR field.

[0508] [Table 51]

[0509] For the meanings of the Device Parameters Management enabled field, Device Parameters Management field, and Time offset for the next SOR field in Table 36, please refer to the field meanings in Table 31. The Time offset for the next SOR Control field can be used to enable and disable Time offset for the next SOR. Table 37 shows the values ​​and meanings of the Time offset for the next SOR Control field.

[0510] [Table 52]

[0511] The meaning of the value in the Time offset for the next SOR Control field is merely an example and not limited to it.

[0512] In possible implementations, the slot position indicated by the Time offset for the next SOR field is one of the following: a slot before the start of a subsequent measurement round (which may be abbreviated as a round), one or more slots in the measurement control phase of the next round, a slot in the measurement report phase (MRP) of the next round, a slot in the ranging phase (RP) of the next round, and a slot in the RP or MRP phase of the current round. When a SOR message for parameter configuration update appears in the MRP phase of the current / next round, the SOR message may be transmitted in an unused slot(s) of the MRP phase. In another example, the SOR message may instead be carried in a report message sent by the initiator to the responder, i.e., the report message carries the SOR message. This is not limited to the present invention. Figure 14G is a diagram showing the reception of a SOR message for parameter configuration update in a slot before the start of the next round. Figure 14H is a diagram showing the reception of a SOR message for parameter configuration update in one or more slots in the RCP of the next round. Figure 14I shows the reception of SOR messages for parameter configuration updates in one or more slots within the MRP for the next round or the current round. Furthermore, as shown in Figure 14G, it can be seen that unused slots within the MRP may be used by the initiator to broadcast SOR messages.

[0513] In possible implementations, the message for parameter configuration updates does not have to be carried by a SOR message, but by another message. In other words, the third message does not have to be a SOR message. In this case, Time offset for the next SOR may also be referred to by another name, for example, Time offset for the next update. This is not limited to the present application.

[0514] For example, in a one-to-many NBA-MMS UWB system, the DPL and Time offset for the next update, which are sent to all responders (as shown in Table 32), may be carried in a POLL message sent by the initiator to the first responder. In other words, the POLL message for the first responder is sent in a broadcast manner. In this case, the parameter configuration becomes effective in the current round, i.e., in the measurement phase after the POLL and RESP have been exchanged, as shown in Figure 15. Figure 15 shows that the POLL message sent by the initiator to the first responder also carries the slot, i.e., the Time offset for the next update, which is for the next update and is broadcast to all responders. The Time offset for the next update may indicate whether the next POLL message or another message carries a message for the parameter update.

[0515] In another example, the Time offset for the next update may be implicitly indicated instead. For example, whether the POLL message sent by the initiator to the first responder in the next round uses a broadcast address is indicated to show whether the Time offset for the next update field will appear in the next round. When it is indicated that the POLL message sent by the initiator to the first responder in the next round does not use a broadcast address, it means that in the next round, the responder (not the initial responder) will not listen for the POLL message sent by the initiator to the first responder to get a message for parameter updates. This is similar to Table 37. The responder either reuses the previous parameter configuration or uses the system's default parameter configuration. Further details are not discussed here again.

[0516] As another example, in a one-to-many NBA-MMS UWB system, the DPL and Time offset for the next update, which are sent to all responders during the MRP phase, may be carried in a report message sent to the responders by the initiator. In other words, the report message to any responder is sent in a broadcast manner. In this case, as shown in Figure 16, the updated parameter configuration becomes effective in the next round (not the current round). Figure 16 shows that the initiator broadcasts the slot for the next update, i.e., the Time offset for the next update, to all responders based on the report message. As another example, in a one-to-many NBA-MMS UWB system, the initiator sends the DPL to all responders in an unused slot during the MRP phase. In other words, in addition to receiving a report message containing measurement information, any responder also receives a message containing the DPL, and both the report message containing measurement information and the message containing the DPL are sent in a broadcast manner. In this case, the updated parameter configuration will take effect in the next round (not the current round). Alternatively, the updated parameter configuration may take effect in the current round, i.e., a phase after RCP (RP phase or MRP phase).

[0517] In another example, if the responder is the controller (i.e., the initiator is not the controller), the DPL and Time offset for the next update may instead be carried in a response message sent by the responder during the RCP phase. In other words, the response message sent by the responder is sent in a broadcast manner. In this case, as shown in Figure 17, the updated parameter configuration becomes effective in the next round (not the current round). Figure 17 shows that the initiator broadcasts a slot for the next update, i.e., the Time offset for the next update, to all responders based on the response message. In this case, the updated parameter configuration may instead become effective in the current round, i.e., a phase after RCP (RP phase or MRP phase).

[0518] In addition, since POLL / response / report messages can be carried within NB messages, a compressed PSDU format of the NB signal can be used to carry POLL / response / report messages, reducing the duty cycle of the NB signal during operation, reducing the energy consumed by device processing, and reducing interference between devices. Table 1-1 shows examples of compressed PSDU formats that can carry POLL / response / report messages. Table 38 shows exemplary formats of compressed PSDUs.

[0519] [Table 53]

[0520] For the meaning of the fields in Table 38, please refer to the field definitions in Table 1-2. Further details will not be explained here.

[0521] Tables 39, 40, and 41 show examples of the format in which Time offset for the next update information is carried in POLL / response / report messages, based on the format shown in Table 38.

[0522] [Table 54]

[0523] [Table 55]

[0524] [Table 56]

[0525] The specific values ​​of the Message ID are not limited in this application. The Message ID values ​​and their meanings shown in Tables 39, 40, and 41 are all examples.

[0526] Figure 18 is an interaction flowchart of another communication method for UWB according to one embodiment of the present application. As shown in Figure 18, the method includes the following steps:

[0527] 1801: The first device sends the first message.

[0528] In response, one or more second devices receive a first message. The first message indicates the expiration of the CAP. The CAP is the period during which a response message to the first message is permitted. For example, the first message includes a first field, the first field indicating that the first message contains information indicating the expiration of the CAP. For step 1801, see step 1301.

[0529] 1802: The target's second device sends a second message to the first device before the CAP expires.

[0530] Correspondingly, the first device receives a second message. The second message may be a response message sent by the target second device to the first message. In some embodiments, the first device may receive response messages to the first message from one or more second devices before the expiration of the CAP. For step 1802, see step 1302.

[0531] 1803: The first device sends the third message.

[0532] In possible implementations, the third message carries information indicating when the fourth message is sent. The fourth message is sent to some or all of the second devices. For example, the third message is a POLL message, and the fourth message is a POLL message sent by the first device after the first device has sent the third message.

[0533] In possible implementations, the third message includes a second field, which indicates that the third message contains information indicating the time when the fourth message is sent. The third message may further include the addresses of some or all of the second devices. The field in the third message that indicates the moment when the fourth message is sent is sometimes referred to as the Time offset for the next POLL field. The second field is used to control whether or not the Time offset for the next POLL field exists. For example, if the value of the second field is 0, the Time offset for the next POLL field does not exist. If the value of the second field is 1, the Time offset for the next POLL field exists.

[0534] In possible implementations, a third message indicates the termination of the current round of measurement or the next round of measurement to reduce resource overhead and unnecessary measurements.

[0535] In possible implementations, the fourth message indicates that the measurement for the current round or the next round should be terminated to reduce resource overhead and unnecessary measurements.

[0536] In embodiments of this application, the first device transmits a first message. The first message indicates the expiration date of the CAP, and as a result, the target second device transmits a second message before the expiration date. This can reduce the duration for which the second message is received in order to reduce energy consumption. The first device transmits a third message. The third message includes information indicating when a fourth message is transmitted. This can reduce the duration for which the target second device allows the receiver to receive an updated SOR message, in order to reduce energy consumption.

[0537] The following describes the structure of a communication device capable of implementing the communication method for UWB provided in the embodiments of this application, with reference to the attached drawings.

[0538] Figure 19 shows the structure of a communication device 1900 according to one embodiment of the present application. The communication device 1900 may implement corresponding functions or steps implemented by the transmitter in the embodiment of the method described above, or corresponding functions or steps implemented by the receiver in the embodiment of the method described above, or corresponding functions or steps implemented by the first device in the embodiment of the method described above, or corresponding functions or steps implemented by the second target device in the embodiment of the method described above. The communication device may include a processing module 1910 and a transceiver module 1920. In possible implementations, the device may further include a storage unit. The storage unit may be configured to store instructions (code or program) and / or data. The processing module 1910 and the transceiver module 1920 may be coupled to the storage unit. For example, the processing module 1910 may read instructions (code or program) and / or data from the storage unit to implement the corresponding method. The above units may be arranged independently, or partially or fully integrated. For example, the transceiver module 1920 may include a transmit module and a receive module. The transmit module may be a transmitter, and the receive module may be a receiver. The entity corresponding to the transceiver module 1920 may be a transceiver or a communication interface.

[0539] In several possible implementations, the communication device 1900 can implement corresponding operations and functions of the transmitter in the embodiments of the method described above. For example, the communication device 1900 may be a transmitter or a component used in a transmitter (e.g., a chip or circuit). For example, the transceiver module 1920 may be configured to perform all the receiving or transmitting operations performed by the transmitter in the embodiments of Figures 8 to 11, e.g., step 802 in the embodiment shown in Figure 8, steps 901 and 903 in the embodiment shown in Figure 9, and step 1002 in the embodiment shown in Figure 10, and steps 1101 and 1103 in the embodiment shown in Figure 11. The processing module 1910 is configured to perform all operations other than receiving and transmitting operations performed by the transmitter in the embodiments of Figures 8 to 11, e.g., step 801 in the embodiment shown in Figure 8.

[0540] In several possible implementations, the communication device 1900 can implement corresponding operations and functions of the receiver in the embodiments of the method described above. For example, the communication device 1900 may be a receiver or a component used in a receiver (e.g., a chip or circuit). The transceiver module 1920 may be configured to perform all receive or transmit operations performed by the receiver in the embodiments shown in Figures 8 to 11, e.g., step 802 in the embodiment shown in Figure 8, steps 901 and 903 in the embodiment shown in Figure 9, step 1002 in the embodiment shown in Figure 10, and steps 1101 and 1103 in the embodiment shown in Figure 11. The processing module 1910 is configured to perform all operations other than receive and transmit operations performed by the receiver, e.g., step 803 in the embodiment shown in Figure 8, and steps 902, 904, and 905 in the embodiment shown in Figure 9.

[0541] In several possible implementations, the communication device 1900 can implement corresponding behaviors and functions of the first device in the method embodiments described above. For example, the communication device 1900 may be the first device or a component used in the first device (e.g., a chip or circuit). For example, the transceiver module 1920 may be configured to perform all receive or transmit operations performed by the first device in the embodiments shown in Figures 13 and 18. The processing module 1910 may be configured to perform all operations performed by the first device other than receive and transmit operations.

[0542] In several possible implementations, the communication device 1900 can implement corresponding operations and functions of the target second device in the embodiments of the method described above. For example, the communication device 1900 may be the target second device, or a component (e.g., a chip or circuit) used in the target second device. For example, the transceiver module 1920 may be configured to perform all receive or transmit operations performed by the target second device in the embodiments shown in Figures 13 and 18. The processing module 1910 may be configured to perform all operations performed by the target second device other than receive and transmit operations.

[0543] Figure 20 is a diagram illustrating the structure of another communication device 200 according to one embodiment of the present application. The communication device in Figure 20 may be the transmitter, the receiver, the first device, or the second target device described above.

[0544] As shown in Figure 20, the communication device 200 includes at least one processor 2010 and a transceiver 2020.

[0545] In some embodiments of this application, the processor 2010 and the transceiver 2020 may be configured to perform functions, operations, etc., performed by the transmitter. For example, the transceiver 2020 may be configured to perform all receive or transmit operations performed by the transmitter in the embodiments of Figures 8 to 11. For example, the processor 2010 may be configured to perform all operations performed by the transmitter in the embodiments of Figures 8 to 11, other than receive and transmit operations.

[0546] In some embodiments of this application, the processor 2010 and the transceiver 2020 may be configured to perform functions, operations, etc., that are performed by the receiver. For example, the transceiver 2020 may be configured to perform all receive or transmit operations performed by the receiver in the embodiments of Figures 8 to 11. For example, the processor 2010 may be configured to perform all operations other than receive and transmit operations that are performed by the receiver in the embodiments of Figures 8 to 11.

[0547] In some embodiments of this application, the processor 2010 and the transceiver 2020 may be configured to perform functions, operations, etc., that are performed by the first device. For example, the transceiver 2020 may be configured to perform all receive or transmit operations that are performed by the first device in the embodiments shown in Figures 13 and 18. For example, the processor 2010 may be configured to perform all operations other than receive and transmit operations that are performed by the first device in the embodiments shown in Figures 13 and 18.

[0548] In some embodiments of this application, the processor 2010 and the transceiver 2020 may be configured to perform functions, operations, etc., that are performed by the target second device. For example, the transceiver 2020 may be configured to perform all receive or transmit operations that are performed by the target second device in the embodiments shown in Figures 13 and 18. For example, the processor 2010 may be configured to perform all operations other than receive and transmit operations that are performed by the target second device in the embodiments shown in Figures 13 and 18.

[0549] The transceiver 2020 is configured to communicate with another device / device via a transmission medium. The processor 2010 is configured to receive and transmit data and / or signaling using the transceiver 2020 and to implement the method in the method embodiment described above. The processor 2010 may implement the functions of the processing module 1910, and the transceiver 2020 may implement the functions of the transceiver module 1920.

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

[0551] Optionally, the communication device 200 may further include at least one memory 2030 configured to store program instructions and / or data. The memory 2030 is coupled to the processor 2010. The coupling in embodiments of this application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or otherwise, and is used for information exchange between devices, units, or modules. The processor 2010 can cooperate with the memory 2030. The processor 2010 can execute program instructions stored in the memory 2030. At least one of the at least one memory may be included in the processor.

[0552] The processor 2010 can read the software program in memory 2030, interpret and execute the software program's instructions, and process the software program's data. When data needs to be transmitted wirelessly, the processor 2010 performs baseband processing on the data to be transmitted and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal in the form of electromagnetic waves via the antenna. When the data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal via the antenna, converts the radio frequency signal back to a baseband signal, and outputs the baseband signal to the processor 2010. The processor 2010 converts the baseband signal back to data and processes it.

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

[0554] The specific connecting medium between the transceiver 2020, processor 2010, and memory 2030 is not limited to the embodiments of this application. In the embodiments of this application, the memory 2030, processor 2010, and transceiver 2020 are connected via bus 2040 in Figure 20. The bus is represented in Figure 20 by the use of a thick line. The methods of connection between other components are merely examples for illustrative purposes and are not limited thereto. Buses may be classified as address buses, data buses, control buses, etc. For ease of representation, only one thick line represents a bus in Figure 20, but this does not mean that there is only one bus or only one type of bus.

[0555] In embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component that can implement or perform the methods, steps, and logic block diagrams disclosed in embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed with reference to embodiments of this application may be performed and achieved directly by the hardware processor or by using a combination of hardware and software modules within the processor.

[0556] Figure 21 is a diagram illustrating the structure of another communication device 210 according to one embodiment of the present application. As shown in Figure 21, the communication device shown in Figure 21 includes a logic circuit 2101 and an interface 2102. The processing module 1910 in Figure 19 may be implemented using the logic circuit 2101, and the transceiver module 1920 in Figure 19 may be implemented using the interface 2102. The logic circuit 2101 may be a chip, processing circuit, integrated circuit, system on chip (SoC), etc., and the interface 2102 may be a communication interface, input / output interface, etc. In the embodiments of the present application, the logic circuit may be further coupled to the interface. The specific method of connection between the logic circuit and the interface is not limited to the embodiments of the present application.

[0557] In some embodiments of this application, logic circuits and interfaces may be configured to perform functions, operations, etc., that are performed by the transmitter.

[0558] In some embodiments of this application, logic circuits and interfaces may be configured to perform functions, operations, etc., that are performed by the receiver.

[0559] In some embodiments of this application, logic circuits and interfaces may be configured to perform functions, operations, etc., that are performed by the first device.

[0560] In some embodiments of this application, logic circuits and interfaces may be configured to perform functions, operations, etc., that are performed by a target second device.

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

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

[0563] This application further provides a communication system including a transmitter and a receiver.

[0564] This application further provides a communication system including a first device and a second target device.

[0565] This application further provides a chip comprising a communication interface and a processor. The communication interface is configured to receive and transmit signals of the chip. The processor is configured to execute computer program instructions, thereby enabling the communication device comprising the chip to perform the method of the above embodiment.

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

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

[0568] 1900 Communication equipment 1910 Processing Module 1920 Transceiver Module 200 Communication devices 2010 Processor 2020 Transceiver 2030 memory 2040 Bus 210 Communication equipment 2101 Logic Circuit 2102 Interface

Claims

1. A communication method for ultra-wideband (UWB), A step of generating a first message, wherein the first message includes a first bitmap, the first bitmap includes N bits, the i-th bit of the first bitmap corresponds to the i-th UWB device, and if the i-th bit is set to a specified value, the i-th bit indicates the position of the parameter configuration information of the i-th UWB device in a first device parameter list (DPL), where i is between 1 and N, and N is an integer greater than 0, and the first DPL is included in the first message. The steps of sending the first message and Methods that include...

2. A communication method for ultra-wideband (UWB), A step of receiving a first message, wherein the first message includes a first bitmap, the first bitmap includes N bits, and the i-th bit in the first bitmap corresponds to the i-th UWB device. If bit i is set to a specified value, the step of determining the position of the UWB device parameter configuration information i in a first device parameter list (DPL), wherein i is between 1 and N, N is an integer greater than 0, and the first DPL is included in the first message. Methods that include...

3. The method according to claim 1 or 2, wherein the first DPL includes one or more sequentially arranged list elements, and if the i bit is the F bit sequentially arranged in the first bitmap and set to the specified value, then the i bit indicates that the F list element in the first DPL includes the parameter configuration information of the i UWB device, where F is an integer greater than 0.

4. The method according to claim 3, wherein the first message further comprises a first field indicating that the first field uses the first bitmap to identify the location of parameter configuration information of a UWB device in the first DPL.

5. The method according to any one of claims 1 to 4, wherein the first message further includes a field indicating the length of the first bitmap.

6. The method according to any one of claims 1 to 5, wherein the first message is included in a measurement start message or a polling / start POLL message.

7. Prior to the step of sending the first message, the method, Steps to send a second message, wherein the second message includes a second DPL, the second DPL includes one or more sequentially arranged list elements, any list element in the second DPL includes the address of a UWB device corresponding to the arbitrary list element, and the sequentially arranged i-th list element in the second DPL includes the parameter configuration information of the corresponding i-th UWB device. The method according to claim 1, further comprising:

8. The first DPL includes a plurality of sequentially arranged list elements, and if bit i is set to the specified value, the step of determining the position of the parameter configuration information of i for the UWB device in the first device parameter list DPL is: Steps to determine that the list element of the first DPL contains the parameter configuration information of the UWB device i, where F is an integer greater than 0, if the i bit is the Fth bit in the first bitmap that is sequentially arranged and set to the specified value, The method according to claim 2, including the method described in claim 2.

9. Before receiving the first message, the method, A step of receiving a second message, wherein the second message includes a second DPL, the second DPL includes one or more sequentially arranged list elements, and any list element in the second DPL includes the address of a UWB device corresponding to the any list element. Steps to determine, based on the second message, that the i-th list element arranged sequentially within the second DPL contains the parameter configuration information of the corresponding i-th UWB device, wherein i is an integer greater than 0, and It further includes, If bit i is set to the specific value, the step of determining the position of the parameter configuration information of the i UWB device in the first device parameter list DPL is: The steps include determining that bit i in the first bitmap corresponds to the UWB device i, If bit i is set to the specified value, the steps include determining the position of the parameter configuration information of the UWB device i in the first DPL and including, The method according to claim 2 or 8.

10. A communication method for ultra-wideband (UWB), A step of generating a first message, wherein the first message includes a first list element, the first list element includes parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the list element for the i-th UWB device in the second message within the device parameter list DPL, the second message is information transmitted before the first message is transmitted, the second message includes the address of the i-th UWB device, and the DPL is included in the second message, and The steps of sending the first message and Methods that include...

11. A communication method for ultra-wideband (UWB), Steps include receiving a first message, wherein the first message includes a first list element, the first list element includes parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the list element for the i-th UWB device in the second message within the device parameter list DPL, the second message being information transmitted before the first message is transmitted, the second message including the address of the i-th UWB device, and the DPL being included in the second message, The steps of determining the first list element based on the identifier and Methods that include...

12. The method according to claim 10 or 11, wherein the identifier occupies less than two octets.

13. The method according to any one of claims 10 to 12, wherein the first message further comprises a first field, the first field indicating that the identifier of the i UWB device is used to identify the location of the parameter configuration information of the i UWB device in the first DPL.

14. The method according to any one of claims 11 to 13, wherein the first message is included in a measurement start message or a polling / start POLL message.

15. Before receiving the first message, the method, The steps include receiving the second message and The steps of determining the order of the list elements of the i UWB device in the second message within the DPL and recording the order as the identifier The method according to claim 11, further comprising:

16. A communication device, A processing module is configured such that it generates a first message, the first message includes a first bitmap, the first bitmap includes N bits, the i-th bit of the first bitmap corresponds to the i-th UWB device, and if the i-th bit is set to a specified value, the i-th bit indicates the position of the parameter configuration information of the i-th UWB device in a first device parameter list (DPL), where i is between 1 and N, and N is an integer greater than 0, and the first DPL is included in the first message. A transceiver module configured to transmit the first message and A communication device equipped with the following features.

17. A communication device, A transceiver module is configured to receive a first message, the first message comprising a first bitmap, the first bitmap comprising N bits, the i-th bit in the first bitmap corresponding to the i-th UWB device, If bit i is set to a specified value, the position of the parameter configuration information of the UWB device i in the first device parameter list (DPL) is determined, where i is between 1 and N, N is an integer greater than 0, and the first DPL is configured to be included in the first message. A communication device equipped with the following features.

18. The communication device according to claim 16 or 17, wherein the first DPL includes one or more sequentially arranged list elements, and if the i bit is the F bit in the first bitmap that is sequentially arranged and set to the specified value, then the i bit indicates that the F list element in the first DPL includes the parameter configuration information of the i UWB device, where F is an integer greater than 0.

19. The communication device according to claim 18, wherein the first message further comprises a first field indicating that the first field uses the first bitmap to identify the location of parameter configuration information of a UWB device in the first DPL.

20. The communication device according to any one of claims 16 to 19, wherein the first message further includes a field indicating the length of the first bitmap.

21. The communication device according to any one of claims 16 to 20, wherein the first message is included in a measurement start message or a polling / start POLL message.

22. The communication device according to claim 16, further configured such that the transceiver module transmits a second message, the second message comprising a second DPL, the second DPL comprising one or more sequentially arranged list elements, any list element in the second DPL comprising the address of a UWB device corresponding to the arbitrary list element, and the sequentially arranged i-th list element in the second DPL comprising the parameter configuration information of the corresponding i-th UWB device.

23. The first DPL mentioned above includes multiple list elements arranged in order, The communication device according to claim 17, wherein the processing module is particularly configured to determine that the list element of the i UWB device contains the parameter configuration information of the i UWB device if the i bit is the fth bit in the first bitmap that is arranged sequentially and set to the specified value, and F is an integer greater than 0.

24. The transceiver module is further configured to receive a second message, the second message comprising a second DPL, the second DPL comprising one or more sequentially arranged list elements, and any list element in the second DPL comprising the address of the UWB device corresponding to the any list element. The processing module is further configured such that, based on the second message, the i-th list element sequentially placed within the second DPL contains the parameter configuration information for the corresponding i-th UWB device, where i is an integer greater than 0. The processing module is particularly configured to determine that the i bit of the first bitmap corresponds to the i UWB device, and if the i bit is set to the specified value, to determine the position of the parameter configuration information of the i UWB device within the first DPL within the first DPL. The communication device according to claim 17 or 23.

25. A communication device, A processing module is configured to generate a first message, the first message including a first list element, the first list element including parameter configuration information for the i-th UWB device and an identifier for the i-th UWB device, the identifier indicating the order of the i-th UWB device list element in the device parameter list DPL in the second message, the second message being information sent before the first message is sent, the second message including the address of the i-th UWB device, and the DPL being included in the second message. A transceiver module configured to transmit the first message and A communication device equipped with the following features.

26. A communication device, A transceiver module is configured to receive a first message, the first message including a first list element, the first list element including parameter configuration information for the i-th UWB device, and the identifier for the i-th UWB device, the identifier indicating the order of the list element for the i-th UWB device in the second message within the device parameter list DPL, the second message being information sent before the first message is sent, the second message including the address of the i-th UWB device, and the DPL being included in the second message. A processing module configured to determine the first list element based on the identifier, A communication device equipped with the following features.

27. The communication device according to claim 25 or 26, wherein the identifier occupies less than two octets.

28. The communication device according to any one of claims 25 to 27, wherein the first message further comprises a first field, the first field indicating that the identifier of the i UWB device is used to identify the location of the parameter configuration information of the i UWB device in the first DPL.

29. The communication device according to any one of claims 25 to 28, wherein the first message is included in a measurement start message or a polling / start POLL message.

30. The transceiver module is further configured to receive the second message, The processing module is further configured to determine the order of the list elements of the i UWB device in the second message within the DPL, and to record the order as the identifier. The communication device according to claim 26.

31. A communication device comprising a processor, wherein the processor is coupled to a memory, the memory stores computer program instructions, and the processor is configured to execute the computer program instructions so that the communication device performs the method according to any one of claims 1 to 30.

32. It's a tip, A communication interface configured to receive and transmit signals from the aforementioned chip, A communication device comprising the chip includes a processor configured to execute computer program instructions so that it performs the method described in any one of claims 1 to 30. A chip equipped with this feature.

33. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer is able to perform the method according to any one of claims 1 to 30.

34. A computer program product wherein, when the computer program product is executed on a computer, the computer becomes capable of performing the method described in any one of claims 1 to 30.

Images