Communication method for UWB, and related product
Patent Information
- Application Number
- PCT/CN2024/096897
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-06-12
- Filing Date
- 2024-05-31
- Publication Date
- 2024-12-19
Smart Images
Figure CN2024096897_19122024_PF_FP_ABST
Abstract
Description
Communication method and related products for UWB
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on June 12, 2023, with application number 202310695309.6, and priority to the Chinese patent application entitled “Communication Methods and Related Products for UWB”, all contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communications, and in particular to a communication method and related products for UWB. Background Art
[0003] Ultra-wideband (UWB) technology is a wireless communication and sensing ranging technology that utilizes nanosecond-scale, non-sinusoidal, narrow pulses to transmit signals, thus occupying a very wide spectrum. Due to its narrow pulses and extremely low radiation spectral density, UWB systems offer advantages such as strong multipath resolution, low power consumption, and enhanced confidentiality, attracting widespread attention in the industry. The Institute of Electrical and Electronics Engineers (IEEE) has incorporated UWB technology into its IEEE 802 series of wireless standards, releasing the UWB-based wireless personal area network (WPAN) standard, IEEE 802.15.4a, and its evolved version, IEEE 802.15.4z. The development of the next-generation UWB WPAN standard, IEEE 802.15.4ab, is also underway. The IEEE 802.15.4ab standard aims to provide a comprehensive upgrade to UWB.
[0004] A UWB device group includes multiple devices that support the UWB standard, also known as UWB devices. Existing solutions for discovering and connecting multiple UWB devices within a UWB device group incur significant signaling overhead. Therefore, research is needed to develop solutions for discovering and connecting multiple UWB devices within a UWB device group that reduce signaling overhead.
[0005] Summary of the Invention
[0006] The embodiment of the present application discloses a communication method for UWB, which can save signaling overhead.
[0007] In a first aspect, embodiments of the present application provide a UWB communication method, the method comprising: generating a first communication frame, the first communication frame including a first field, the first field being used to indicate device capabilities of multiple UWB devices in a UWB device group; and transmitting the first communication frame. The multiple UWB devices in the UWB device group refer to some or all of the UWB devices in the UWB device group.
[0008] In an embodiment of the present application, a first communication frame is sent to indicate the device capabilities of multiple UWB devices in a UWB device group. This reduces signaling overhead compared to each device in the UWB device group sending a communication frame indicating its own device capabilities. Furthermore, sending the first communication frame reduces time overhead compared to each device in the UWB device group sending a communication frame indicating its own device capabilities.
[0009] In one possible implementation, after sending the first communication frame, the method further includes: receiving a second communication frame, the second communication frame including a second field and a third field; the second field is used to instruct the proxy device in the UWB device group to update the device address of the proxy device, and the third field includes the updated device address of the proxy device; or, the second field is used to instruct the proxy device in the UWB device group to update the device address of one or more UWB devices in the UWB device group, the third field includes the sub-identifier of the first UWB device in the UWB device group and the updated device address of the first UWB device, and the first UWB device is any one of the one or more UWB devices.
[0010] In this implementation, a second communication frame is received to update the device addresses of one or more UWB devices in the UWB device group based on the second communication frame. This reduces signaling overhead compared to sending a communication frame for updating the short address for each device in the UWB device group that requires a short address update. Furthermore, receiving the second communication frame takes less time than receiving a communication frame for updating the short address for each device in the UWB device group that requires a short address update, thus reducing time overhead.
[0011] In one possible implementation, after sending the first communication frame, the method further includes: receiving a third communication frame, the third communication frame including an address list, the address list including multiple address list elements, the device address included in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i in the UWB device group, where i is an integer greater than or equal to 0. The device address included in the address list element may be a short address.
[0012] In this implementation, by receiving the third communication frame, the device addresses of multiple devices in the UWB device group can be obtained, which can save signaling overhead.
[0013] In one possible implementation, after sending the first communication frame, the method further includes: receiving a fourth communication frame, the fourth communication frame including a first list, the first list including multiple scheduling list elements, the first scheduling list element in the first list including a first sub-list, and the first sub-list is used to indicate parameter configuration information or scheduling information of multiple UWB devices in the UWB device group.
[0014] In this implementation, the sublist included in the first scheduling list element is used to indicate parameter configuration information or scheduling information for multiple UWB devices within a UWB device group. Because the first list includes multiple scheduling list elements, the parameter configuration information or scheduling information for each UWB device within the multiple UWB device groups can be obtained through the fourth communication frame, reducing signaling overhead.
[0015] In one possible implementation, after sending the first communication frame, the method further includes: sending a fifth communication frame, the fifth communication frame including a first bitmap and a second list, the first bitmap including N bits, the i-th bit in the first bitmap corresponding to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement reporting information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier of i in the UWB device group.
[0016] In this implementation, when the i-th bit in the first bitmap takes a set value, the i-th bit is used to indicate the position of the measurement report information of the i-th UWB device in the second list. It can be understood that the first bitmap indicates the position of the measurement report information of multiple devices within the UWB device group in the second list, enabling the combined reporting of the measurement report information of multiple devices within the UWB device group, with reduced signaling overhead.
[0017] In one possible implementation, after sending the first communication frame, the method further includes: sending a sixth communication frame, the sixth communication frame including a third list, the third list being used to indicate measurement reporting information of multiple UWB devices within the UWB device group, the first list element in the third list including a sub-identifier of the first UWB device within the UWB device group, the first list element being used to indicate measurement reporting information of the first UWB device, and the first UWB device being any one of the multiple UWB devices.
[0018] In this implementation, the first list element includes a sub-identifier of the first UWB device within the UWB device group. The sub-identifier within the UWB device group can indicate the device corresponding to the list element in the third list, avoiding the need to directly indicate the Device Address (2 bytes / 8 bytes), thereby reducing signaling overhead.
[0019] In one possible implementation, the first field includes multiple capability list elements, one capability list element in the first field is used to indicate the device capability of one of the multiple UWB devices; before sending the first communication frame, the method further includes: assigning a first address to a first UWB device, the first address being derived from the device address of a proxy device in the UWB device group and a first sub-identifier of the first UWB device in the UWB device group, the first UWB device being any one of the multiple UWB devices. Exemplarily, the first address is a short address, for example, having a length of 2 bytes.
[0020] In this implementation, a first address is allocated to the first UWB device, so that the first UWB device obtains required information according to the first address.
[0021] In one possible implementation, the first communication frame carries the long address of the proxy device in the UWB device group (which may be referred to as the device long address); after sending the first communication frame, the method further includes: receiving a connection response frame, the connection response frame carrying the short address of the proxy device (which may be referred to as the device short address); based on the short address of the proxy device and the sub-identifier of the non-proxy device in the UWB device group, determining the short address of the non-proxy device in the UWB device group, the long address of the proxy device being longer than the short address of the proxy device. Optionally, the first communication frame also carries the long address of the non-proxy device in the UWB device group. The non-proxy devices in the UWB device group refer to all devices in the UWB device group except the proxy device.
[0022] In this implementation, the short address of the non-proxy device in the UWB device group is determined based on the short address of the proxy device and the sub-identifier of the non-proxy device in the UWB device group; so that the proxy device and the controller can use the short address instead of the long address in the subsequent interaction process, thereby saving signaling overhead.
[0023] In a second aspect, an embodiment of the present application provides another communication method for UWB, the method comprising: receiving a first communication frame, the first communication frame comprising a first field, the first field being used to indicate the device capabilities of multiple UWB devices in a UWB device group; and obtaining the device capabilities of multiple UWB devices in the UWB device group based on the first communication frame.
[0024] In the embodiments of the present application, the device capabilities of multiple UWB devices in a UWB device group are obtained based on a first communication frame (one communication frame); compared to obtaining the device capabilities of multiple UWB devices based on multiple communication frames, signaling overhead can be reduced. In addition, obtaining the device capabilities of multiple UWB devices based on the first communication frame can save time compared to obtaining the device capabilities of multiple UWB devices based on multiple communication frames.
[0025] In one possible implementation, after receiving the first communication frame, the method further includes: sending a second communication frame, the second communication frame including a second field and a third field; the second field is used to instruct the proxy device in the UWB device group to update the device address of the proxy device, and the third field includes the updated device address of the proxy device; or, the second field is used to instruct the proxy device in the UWB device group to update the device address of one or more UWB devices in the UWB device group, the third field includes a sub-identifier of the first UWB device in the UWB device group and the updated device address of the first UWB device, and the first UWB device is any one of the one or more UWB devices.
[0026] In this implementation, a second communication frame is sent to indicate an update of the device address of one or more UWB devices in the UWB device group. This reduces signaling overhead compared to sending a communication frame for updating the short address for each device in the UWB device group that requires a short address update. Furthermore, sending the second communication frame takes less time than sending a communication frame for updating the short address for each device in the UWB device group that requires a short address update, thus reducing time overhead.
[0027] In one possible implementation, after receiving the first communication frame, the method further includes: sending a third communication frame, the third communication frame including an address list, the address list including a plurality of address list elements, the device address contained in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i in the UWB device group, and i is an integer greater than or equal to 0. Exemplarily, device i (device with sub-identifier i) in the UWB device group obtains its own short address by reading the i-th list element in the address list. In the present application, the sub-identifier of a device refers to the sub-identifier of the device in the UWB device group. Exemplarily, the device address contained in the i-th address list element is a short address, for example, with a length of 2 bytes.
[0028] In this implementation, sending the third communication frame can enable multiple devices in the UWB device group to obtain their respective device addresses, thereby saving signaling overhead.
[0029] In one possible implementation, after receiving the first communication frame, the method further includes: sending a fourth communication frame, the fourth communication frame including a first list, the first list including multiple scheduling list elements, the first scheduling list element in the first list including a first sublist, the first sublist being used to indicate parameter configuration information or scheduling information for multiple UWB devices in the UWB device group. Exemplarily, the fourth communication frame is sent via broadcast or multicast. For example, the fourth communication frame is sent via multicast to proxy devices in the multiple UWB device groups.
[0030] In this implementation, the first sublist included in the first scheduling list element is used to indicate parameter configuration information or scheduling information for multiple UWB devices within a UWB device group. Because the first list includes multiple scheduling list elements, the fourth communication frame can indicate parameter configuration information or scheduling information for each UWB device within the multiple UWB device groups. Compared to sending a communication frame for each UWB device group, signaling overhead is reduced.
[0031] In one possible implementation, after receiving the first communication frame, the method further includes: receiving a fifth communication frame, the fifth communication frame including a first bitmap and a second list, the first bitmap including N bits, the i-th bit in the first bitmap corresponding to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement reporting information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier of i in the UWB device group.
[0032] In this implementation, when the i-th bit in the first bitmap takes a set value, the i-th bit is used to indicate the position of the measurement report information of the i-th UWB device in the second list. It can be understood that the first bitmap indicates the position of the measurement report information of multiple devices within the UWB device group in the second list, enabling the combined reporting of the measurement report information of multiple devices within the UWB device group, with reduced signaling overhead.
[0033] In one possible implementation, after receiving the first communication frame, the method further includes: receiving a sixth communication frame, the sixth communication frame including a third list, the third list being used to indicate measurement reporting information of multiple UWB devices within the UWB device group, the first list element in the third list including a sub-identifier of the first UWB device within the UWB device group, the first list element being used to indicate measurement reporting information of the first UWB device, and the first UWB device being any one of the multiple UWB devices.
[0034] In this implementation, the first list element includes a sub-identifier of the first UWB device within the UWB device group. The sub-identifier within the UWB device group can indicate the device corresponding to the list element in the third list, avoiding the need to directly indicate the Device Address (2 bytes / 8 bytes), thereby reducing signaling overhead.
[0035] In one possible implementation, the first communication frame carries the long address (which may be referred to as the device long address) of the proxy device in the UWB device group. After receiving the first communication frame, the method further includes: sending a connection response frame, the connection response frame carrying the short address of the proxy device. Optionally, the first communication frame also carries the long addresses of non-proxy devices in the UWB device group.
[0036] In this implementation, a connection response frame carrying the short address of the proxy device is sent so that the proxy device and the controller can use the short address instead of the long address in subsequent interactions, thereby saving signaling overhead.
[0037] In one possible implementation, the first field includes multiple capability list elements, one capability list element in the first field is used to indicate the device capability of one of the multiple UWB devices; after receiving the first communication frame, the method further includes: determining a sub-identifier of the device corresponding to the f-th capability list element based on the order of the f-th capability list element in the multiple capability list elements, where f is an integer greater than or equal to 1. Exemplarily, the capability list in the first field includes multiple capability list elements, the f-th capability list element in the capability list is used to indicate the device capability of device #f in a UWB device group, and the f-th capability list element is the f-th capability list element in the capability list; and determining the sub-identifier of the device corresponding to the f-th capability list element (i.e., device #f) to be f.
[0038] In this implementation, based on the order of the fth capability list element among multiple capability list elements, the sub-identifier of the device corresponding to the fth capability list element is determined. The first communication frame does not need to carry information indicating the sub-identifier, which can save signaling overhead.
[0039] In a possible implementation of the first aspect or the second aspect, the first scheduling list element also includes a second bitmap, the second bitmap includes N bits, the i-th bit in the second bitmap corresponds to the i-th UWB device, and when the i-th bit takes a set value, the i-th bit is used to indicate the position of the parameter configuration information or scheduling information of the i-th UWB device in the first sublist, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
[0040] In this implementation, when the i-th bit in the second bitmap takes a set value, the i-th bit is used to indicate the position of the parameter configuration information or scheduling information of the i-th UWB device in the first sublist. It will be appreciated that the second bitmap can indicate the device corresponding to each list element in the first sublist, avoiding the direct use of the device address as the device identifier and reducing signaling overhead.
[0041] In a possible implementation manner of the first aspect or the second aspect, the first scheduling list element further includes a sixth field, and the sixth field is used to indicate information shared by multiple UWB devices in the UWB device group.
[0042] In this implementation, the sixth field is used to indicate information shared by multiple UWB devices in a UWB device group, which can save signaling overhead.
[0043] In a possible implementation manner of the first aspect or the second aspect, the first scheduling list element further includes a field for indicating the length of the second bitmap.
[0044] In one possible implementation, the first sublist includes one or more list elements arranged in order. When the i-th bit is the F-th bit in the second bitmap arranged in order and taking the set value, the i-th bit indicates that the F-th list element in the first sublist includes parameter configuration information or scheduling information of the i-th UWB device, and F is an integer greater than 0.
[0045] In this implementation, the UWB device corresponding to each list element can be accurately determined.
[0046] In a possible implementation of the first or second aspect, the first sub-list includes a second list element, the second list element is used to indicate parameter configuration information or scheduling information of the first UWB device, and the second list element includes a sub-identifier of the first UWB device within the UWB device group. Exemplarily, the length of the sub-identifier of any device within the UWB device group is shorter than the length of the short address of the any device.
[0047] In this implementation, the second list element includes the sub-identifier of the first UWB device in the UWB device group. The sub-identifier of the first UWB device replaces its device short address. Since the sub-identifier is shorter than the device short address, signaling overhead can be saved.
[0048] In a possible implementation manner of the first aspect or the second aspect, the fifth communication frame further includes a field for indicating the length of the first bitmap.
[0049] In a possible implementation manner of the first aspect or the second aspect, the first communication frame further includes a fourth field, and the fourth field is used to indicate that the first communication frame comes from a proxy device in the UWB device group.
[0050] In this implementation, the first communication frame further includes a fourth field to indicate that the first communication frame is sent by a proxy device in the UWB device group.
[0051] In a possible implementation of the first aspect or the second aspect, the first field is used to indicate a first device capability, which is a device capability possessed by each UWB device in the UWB device group; or, the first field includes multiple capability list elements, and a capability list element in the first field is used to indicate a device capability of a UWB device among the multiple UWB devices.
[0052] In this implementation, the first field is used to indicate the device capabilities of multiple UWB devices in the UWB device group; compared to each device in the UWB device group sending a communication frame indicating its own device capabilities to the controller, signaling overhead can be saved.
[0053] In a possible implementation of the first aspect or the second aspect, the first communication frame also includes a fifth field; when the value of the fifth field is a first value, the first field is used to indicate the first device capability; when the value of the fifth field is a second value, the first field includes the multiple capability list elements.
[0054] In this implementation, the value of the fifth field is related to the format of the first field, and the format of the first field can be determined through the fifth field.
[0055] In a possible implementation of the first aspect or the second aspect, the first field includes the multiple capability list elements, and the multiple capability list elements have a mapping relationship with the device addresses of the multiple UWB devices. The capability list elements do not include device addresses.
[0056] In this implementation, a plurality of capability list elements and device addresses of a plurality of UWB devices have a mapping relationship, so that the device addresses of the plurality of UWB devices can be obtained based on the plurality of capability list elements, thereby saving signaling overhead.
[0057] In a possible implementation of the first aspect or the second aspect, the i-th capability list element in the first field is used to indicate the device capability of the i-th UWB device, the order of the i-th capability list element in the multiple capability list elements and the device address of the proxy device in the UWB device group are used to determine the device address of the i-th UWB device, and i is an integer greater than or equal to 0.
[0058] In this implementation, the order of the i-th capability list element in multiple capability list elements and the device address of the proxy device in the UWB device group are used to determine the device address of the i-th UWB device. In this way, the i-th capability list element does not need to include the device address of the i-th UWB device, which can save signaling overhead.
[0059] In a possible implementation manner of the first aspect or the second aspect, the first communication frame further includes a field for indicating an address of a proxy device in the UWB device group.
[0060] In a third aspect, an embodiment of the present application provides another communication method for UWB, the method comprising: generating a fourth communication frame, the fourth communication frame comprising a first list, the first list comprising multiple scheduling list elements, the first scheduling list element in the first list comprising a first sub-list, the first sub-list being used to indicate parameter configuration information or scheduling information of multiple UWB devices in the UWB device group; and sending the fourth communication frame.
[0061] In this embodiment of the present application, the first sublist included in the first scheduling list element is used to indicate parameter configuration information or scheduling information for multiple UWB devices within a UWB device group. Because the first list includes multiple scheduling list elements, the fourth communication frame can indicate parameter configuration information or scheduling information for each UWB device within the multiple UWB device groups. Compared to sending a communication frame for each UWB device group, signaling overhead is reduced.
[0062] In one possible implementation, before sending the fourth communication frame, the method further includes: receiving a first communication frame, the first field in the first communication frame including multiple capability list elements, one capability list element in the first field being used to indicate a device capability of a UWB device in a UWB device group; determining a sub-identifier of a device corresponding to the f-th capability list element based on the order of the f-th capability list element in the multiple capability list elements, where f is an integer greater than or equal to 1. Exemplarily, the capability list in the first field includes multiple capability list elements, the f-th capability list element in the capability list is used to indicate the device capability of device #f in the UWB device group, and the f-th capability list element is the f-th capability list element in the capability list; and determining the sub-identifier of the device corresponding to the f-th capability list element (i.e., device #f) to be f.
[0063] In this implementation, based on the order of the fth capability list element among multiple capability list elements, the sub-identifier of the device corresponding to the fth capability list element is determined. The first communication frame does not need to carry information indicating the sub-identifier, which can save signaling overhead.
[0064] In a fourth aspect, an embodiment of the present application provides another communication method for UWB, the method comprising: receiving a fourth communication frame, the fourth communication frame comprising a first list, the first list comprising multiple scheduling list elements, the first scheduling list element in the first list comprising a first sub-list, the first sub-list being used to indicate parameter configuration information or scheduling information of multiple UWB devices within the UWB device group; based on the fourth communication frame, obtaining parameter configuration information or scheduling information of multiple UWB devices within the UWB device group.
[0065] In this embodiment of the present application, the sublist included in the first scheduling list element is used to indicate parameter configuration information or scheduling information for multiple UWB devices within a UWB device group. Because the first list includes multiple scheduling list elements, the parameter configuration information or scheduling information for each UWB device within the multiple UWB device groups can be obtained through the fourth communication frame, and signaling overhead is relatively low.
[0066] In a possible implementation of the third aspect or the fourth aspect, the first scheduling list element also includes a second bitmap, the second bitmap includes N bits, the i-th bit in the second bitmap corresponds to the i-th UWB device, and when the i-th bit takes a set value, the i-th bit is used to indicate the position of the parameter configuration information or scheduling information of the i-th UWB device in the first sublist, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
[0067] In this implementation, when the i-th bit in the second bitmap takes a set value, the i-th bit is used to indicate the position of the parameter configuration information or scheduling information of the i-th UWB device in the first sublist. It will be appreciated that the second bitmap can indicate the device corresponding to each list element in the first sublist, avoiding the direct use of the device address as the device identifier and reducing signaling overhead.
[0068] In a possible implementation manner of the third aspect or the fourth aspect, the first scheduling list element further includes a sixth field, and the sixth field is used to indicate information shared by multiple UWB devices in the UWB device group.
[0069] In this implementation, the sixth field is used to indicate information shared by multiple UWB devices in a UWB device group, which can save signaling overhead.
[0070] In a possible implementation manner of the third aspect or the fourth aspect, the first scheduling list element further includes a field for indicating the length of the second bitmap.
[0071] In a possible implementation of the third aspect or the fourth aspect, the first sublist includes one or more list elements arranged in order, and when the i-th bit is the F-th bit arranged in order in the second bitmap that takes the set value, the i-th bit indicates that the F-th list element in the first sublist includes parameter configuration information or scheduling information of the i-th UWB device, and F is an integer greater than 0.
[0072] In this implementation, the UWB device corresponding to each list element can be accurately determined.
[0073] In a possible implementation of the third aspect or the fourth aspect, the first sub-list includes a second list element, the second list element is used to indicate parameter configuration information or scheduling information of the first UWB device, and the second list element includes a sub-identifier of the first UWB device in the UWB device group.
[0074] In this implementation, the second list element includes the sub-identifier of the first UWB device in the UWB device group. The sub-identifier of the first UWB device replaces its device short address. Since the sub-identifier is shorter than the device short address, signaling overhead can be saved.
[0075] In a fifth aspect, an embodiment of the present application provides another communication method for UWB, the method comprising: generating a fifth communication frame, the fifth communication frame comprising a first bitmap and a second list, the first bitmap comprising N bits, the i-th bit in the first bitmap corresponding to the i-th UWB device, and when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement report information of the i-th UWB device in the second list, wherein i is greater than or equal to 0 and i is less than or equal to N, where N is an integer greater than 0; and sending the fifth communication frame. Exemplarily, the i-th UWB device is a device with a sub-identifier of i.
[0076] In the embodiment of the present application, when the i-th bit in the first bitmap takes a set value, the i-th bit is used to indicate the position of the measurement report information of the i-th UWB device in the second list. It can be understood that the first bitmap indicates the position of the measurement report information of multiple devices within the UWB device group in the second list, which enables the combined reporting of the measurement report information of multiple devices within the UWB device group, reducing signaling overhead.
[0077] In a sixth aspect, an embodiment of the present application provides another communication method for UWB, the method comprising: receiving a fifth communication frame, the fifth communication frame comprising a first bitmap and a second list, the first bitmap comprising N bits, the i-th bit in the first bitmap corresponding to the i-th UWB device, and when the i-th bit takes a set value, the i-th bit is used to indicate the position of measurement report information of the i-th UWB device in the second list, wherein i is greater than or equal to 0 and i is less than or equal to N, where N is an integer greater than 0; when the i-th bit takes the set value, determining the position of the measurement report information of the i-th UWB device in the second list. The i-th UWB device is a device with a sub-identifier of i within the UWB device group.
[0078] In the embodiment of the present application, when the i-th bit in the first bitmap takes a set value, the position of the measurement reporting information of the i-th UWB device in the second list is determined; signaling overhead can be saved.
[0079] In a possible implementation of the fifth aspect or the sixth aspect, the second list includes one or more list elements arranged in order, and when the i-th bit is the H-th bit arranged in order in the first bitmap that takes the set value, the i-th bit indicates that the H-th list element in the second list includes the measurement reporting information of the i-th UWB device, and H is an integer greater than 0.
[0080] In a seventh aspect, an embodiment of the present application provides another communication method for UWB, the method comprising: generating a sixth communication frame, the sixth communication frame comprising a third list, the third list being used to indicate measurement reporting information of multiple UWB devices within the UWB device group, a first list element in the third list comprising a sub-identifier of a first UWB device within the UWB device group, the first list element being used to indicate measurement reporting information of the first UWB device, the first UWB device being any one of the multiple UWB devices; and transmitting the sixth communication frame. Exemplarily, the length of the sub-identifier of the first UWB device within the UWB device group is less than or equal to 1 byte.
[0081] In this embodiment of the present application, the first list element includes a sub-identifier of the first UWB device within the UWB device group. The sub-identifier within the UWB device group can indicate the device corresponding to the list element in the third list, avoiding the need to directly indicate the device address (2 bytes / 8 bytes), thereby achieving the purpose of saving signaling overhead.
[0082] In an eighth aspect, an embodiment of the present application provides another communication method for UWB, the method comprising: receiving a sixth communication frame, the sixth communication frame comprising a third list, the third list being used to indicate measurement reporting information of multiple UWB devices within the UWB device group, the first list element in the third list comprising a sub-identifier of a first UWB device within the UWB device group, the first list element being used to indicate measurement reporting information of a first UWB device, the first UWB device being any one of the multiple UWB devices; obtaining measurement reporting information of multiple UWB devices within the UWB device group according to the sixth communication frame.
[0083] In an embodiment of the present application, measurement reporting information of multiple UWB devices within a UWB device group is obtained based on the sixth communication frame. The first list element includes a sub-identifier of the first UWB device within the UWB device group, which avoids directly indicating the device address (2 bytes / 8 bytes) of the first UWB device, thereby achieving the purpose of saving signaling overhead.
[0084] In one possible implementation, before receiving the sixth communication frame, the method further includes: receiving a first communication frame, the first field in the first communication frame including a plurality of capability list elements, one capability list element in the first field being used to indicate a device capability of a UWB device in a UWB device group; determining a sub-identifier of a device corresponding to the f-th capability list element based on the order of the f-th capability list element in the plurality of capability list elements, where f is an integer greater than or equal to 1. Exemplarily, the capability list in the first field includes a plurality of capability list elements, the f-th capability list element in the capability list being used to indicate a device capability of device #f in a UWB device group, the f-th capability list element being the f-th capability list element in the capability list; and determining the sub-identifier of the device corresponding to the f-th capability list element (i.e., device #f) to be f.
[0085] In this implementation, based on the order of the fth capability list element among multiple capability list elements, the sub-identifier of the device corresponding to the fth capability list element is determined. The first communication frame does not need to carry information indicating the sub-identifier, which can save signaling overhead.
[0086] In a ninth aspect, an embodiment of the present application provides a communication device having the function of implementing the behavior in the method embodiment of the first aspect above. The communication device may be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate a first communication frame, the first communication frame includes a first field, and the first field is used to indicate the device capabilities of multiple UWB devices in the UWB device group; the transceiver module is used to send the first communication frame.
[0087] In one possible implementation, the transceiver module is further used to receive a second communication frame, the second communication frame including a second field and a third field; the second field is used to instruct the proxy device in the UWB device group to update the device address of the proxy device, and the third field includes the updated device address of the proxy device; or, the second field is used to instruct the proxy device in the UWB device group to update the device address of one or more UWB devices in the UWB device group, and the third field includes a sub-identifier of the first UWB device in the UWB device group and the updated device address of the first UWB device, and the first UWB device is any one of the one or more UWB devices.
[0088] In one possible implementation, the transceiver module is further configured to receive a third communication frame, the third communication frame including an address list, the address list including multiple address list elements, the device address included in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i in the UWB device group, where i is an integer greater than or equal to 0. The device address included in the address list element may be a short address.
[0089] In one possible implementation, the transceiver module is also used to receive a fourth communication frame, the fourth communication frame including a first list, the first list including multiple scheduling list elements, the first scheduling list element in the first list including a first sub-list, and the first sub-list is used to indicate parameter configuration information or scheduling information of multiple UWB devices in the UWB device group.
[0090] In one possible implementation, the transceiver module is further used to send a fifth communication frame, the fifth communication frame including a first bitmap and a second list, the first bitmap including N bits, the i-th bit in the first bitmap corresponding to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement reporting information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
[0091] In one possible implementation, the transceiver module is further used to send a sixth communication frame, the sixth communication frame including a third list, the third list being used to indicate measurement reporting information of multiple UWB devices in the UWB device group, the first list element in the third list including a sub-identifier of a first UWB device in the UWB device group, the first list element being used to indicate measurement reporting information of a first UWB device, and the first UWB device being any one of the multiple UWB devices.
[0092] In one possible implementation, the first field includes multiple capability list elements, and a capability list element in the first field is used to indicate the device capability of a UWB device among the multiple UWB devices; the transceiver module is also used to assign a first address to a first UWB device, and the first address is obtained by the device address of the proxy device in the UWB device group and the first sub-identifier of the first UWB device in the UWB device group, and the first UWB device is any one of the multiple UWB devices.
[0093] In one possible implementation, the first communication frame carries the long address of the proxy device in the UWB device group (which may be called the device long address); the transceiver module is also used to receive a connection response frame, and the connection response frame carries the short address of the proxy device (which may be called the device short address); based on the short address of the proxy device and the sub-identifier of the non-proxy device in the UWB device group, the short address of the non-proxy device in the UWB device group is determined, and the length of the long address of the proxy device is longer than the short address of the proxy device.
[0094] Possible implementations of the communication device of the ninth aspect can refer to the various possible implementations of the first aspect.
[0095] For the technical effects brought about by various possible implementation methods of the ninth aspect, reference may be made to the introduction to the technical effects of the first aspect or various possible implementation methods of the first aspect.
[0096] In the tenth aspect, an embodiment of the present application provides another communication device, which has the function of implementing the behavior in the method embodiment of the second aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or by hardware executing corresponding software implementations, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first communication frame, the first communication frame includes a first field, and the first field is used to indicate the device capabilities of multiple UWB devices in the UWB device group; the processing module is used to obtain the device capabilities of multiple UWB devices in the UWB device group based on the first communication frame.
[0097] In one possible implementation, the transceiver module is further used to send a second communication frame, the second communication frame including a second field and a third field; the second field is used to instruct the proxy device in the UWB device group to update the device address of the proxy device, and the third field includes the updated device address of the proxy device; or, the second field is used to instruct the proxy device in the UWB device group to update the device address of one or more UWB devices in the UWB device group, and the third field includes a sub-identifier of the first UWB device in the UWB device group and the updated device address of the first UWB device, and the first UWB device is any one of the one or more UWB devices.
[0098] In one possible implementation, the transceiver module is further used to send a third communication frame, wherein the third communication frame includes an address list, the address list includes multiple address list elements, and the device address contained in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i in the UWB device group, where i is an integer greater than or equal to 0.
[0099] In one possible implementation, the transceiver module is also used to send a fourth communication frame, the fourth communication frame includes a first list, the first list includes multiple scheduling list elements, the first scheduling list element in the first list includes a first sub-list, and the first sub-list is used to indicate parameter configuration information or scheduling information of multiple UWB devices in the UWB device group.
[0100] In one possible implementation, the transceiver module is further used to receive a fifth communication frame, the fifth communication frame including a first bitmap and a second list, the first bitmap including N bits, the i-th bit in the first bitmap corresponding to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement reporting information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
[0101] In one possible implementation, the transceiver module is further used to receive a sixth communication frame, the sixth communication frame including a third list, the third list being used to indicate measurement reporting information of multiple UWB devices in the UWB device group, the first list element in the third list including a sub-identifier of a first UWB device in the UWB device group, the first list element being used to indicate measurement reporting information of a first UWB device, and the first UWB device being any one of the multiple UWB devices.
[0102] In a possible implementation, the first communication frame carries the long address of the proxy device in the UWB device group; the transceiver module is further configured to send a connection response frame, wherein the connection response frame carries the short address of the proxy device.
[0103] In one possible implementation, the first field includes multiple capability list elements, and a capability list element in the first field is used to indicate the device capability of a UWB device among the multiple UWB devices; the processing module is further used to determine the sub-identifier of the device corresponding to the fth capability list element based on the order of the fth capability list element among the multiple capability list elements, where f is an integer greater than or equal to 1.
[0104] Possible implementations of the communication device of the tenth aspect can refer to the various possible implementations of the second aspect.
[0105] For the technical effects brought about by various possible implementation methods of the tenth aspect, reference may be made to the introduction to the technical effects of the second aspect or various possible implementation methods of the second aspect.
[0106] On the eleventh aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method of the third aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate a fourth communication frame, the fourth communication frame includes a first list, the first list includes multiple scheduling list elements, the first scheduling list element in the first list includes a first sublist, and the first sublist is used to indicate parameter configuration information or scheduling information of multiple UWB devices in the UWB device group; the transceiver module is used to send the fourth communication frame.
[0107] In one possible implementation, the transceiver module is further used to receive a first communication frame, the first field in the first communication frame includes multiple capability list elements, and a capability list element in the first field is used to indicate the device capability of a UWB device in the UWB device group; the processing module is further used to determine the sub-identifier of the device corresponding to the fth capability list element based on the order of the fth capability list element in the multiple capability list elements, where f is an integer greater than or equal to 1.
[0108] Possible implementations of the communication device of the eleventh aspect may refer to the various possible implementations of the third aspect.
[0109] For the technical effects brought about by various possible implementation methods of the eleventh aspect, reference may be made to the introduction to the technical effects of the third aspect or various possible implementation methods of the third aspect.
[0110] In a twelfth aspect, an embodiment of the present application provides another communication device, which has the function of implementing the behavior in the embodiment of the method of the fourth aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a fourth communication frame, the fourth communication frame includes a first list, the first list includes multiple scheduling list elements, the first scheduling list element in the first list includes a first sublist, and the first sublist is used to indicate the parameter configuration information or scheduling information of multiple UWB devices in the UWB device group; the processing module is used to obtain the parameter configuration information or scheduling information of multiple UWB devices in the UWB device group based on the fourth communication frame.
[0111] For possible implementations of the communication device of the twelfth aspect, reference may be made to various possible implementations of the fourth aspect.
[0112] For the technical effects brought about by various possible implementation methods of the twelfth aspect, reference may be made to the introduction to the technical effects of various possible implementation methods of the fourth aspect or the second aspect.
[0113] In a thirteenth aspect, an embodiment of the present application provides a communication device having the function of implementing the behavior in the embodiment of the method of the fifth aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate a fifth communication frame, the fifth communication frame includes a first bitmap and a second list, the first bitmap includes N bits, the i-th bit in the first bitmap corresponds to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement report information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, and the N is an integer greater than 0; the transceiver module is used to send the fifth communication frame, the i-th UWB device is a device with a sub-identifier of i in the UWB device group.
[0114] For possible implementations of the communication device of the thirteenth aspect, reference may be made to various possible implementations of the fifth aspect.
[0115] For the technical effects brought about by various possible implementation methods of the thirteenth aspect, reference may be made to the introduction to the technical effects of the fifth aspect or various possible implementation methods of the fifth aspect.
[0116] In a fourteenth aspect, an embodiment of the present application provides another communication device, which has the function of implementing the behavior in the method embodiment of the sixth aspect above. The communication device can be a communication device, or it can be a component of a communication device (such as a processor, a chip, or a chip system, etc.), or it can be a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or they can be implemented by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a fifth communication frame, the fifth communication frame includes a first bitmap and a second list, the first bitmap includes N bits, the i-th bit in the first bitmap corresponds to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement reporting information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group; the processing module is used to determine the position of the measurement reporting information of the i-th UWB device in the second list when the i-th bit takes the set value.
[0117] For possible implementations of the communication device of the fourteenth aspect, reference may be made to various possible implementations of the sixth aspect.
[0118] For the technical effects brought about by various possible implementation methods of the fourteenth aspect, reference may be made to the introduction to the technical effects of the sixth aspect or various possible implementation methods of the sixth aspect.
[0119] In a fifteenth aspect, an embodiment of the present application provides a communication device having the function of implementing the behavior in the embodiment of the method of the seventh aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate a sixth communication frame, the sixth communication frame includes a third list, the third list is used to indicate the measurement reporting information of multiple UWB devices in the UWB device group, the first list element in the third list includes the sub-identifier of the first UWB device in the UWB device group, the first list element is used to indicate the measurement reporting information of the first UWB device, and the first UWB device is any one of the multiple UWB devices; the transceiver module is used to send the sixth communication frame.
[0120] For possible implementations of the communication device of the fifteenth aspect, reference may be made to various possible implementations of the seventh aspect.
[0121] For the technical effects brought about by various possible implementation methods of the fifteenth aspect, reference may be made to the introduction to the technical effects of the seventh aspect or various possible implementation methods of the seventh aspect.
[0122] In a sixteenth aspect, an embodiment of the present application provides another communication device, which has the function of implementing the behavior in the embodiment of the method of the eighth aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a sixth communication frame, the sixth communication frame includes a third list, the third list is used to indicate the measurement reporting information of multiple UWB devices in the UWB device group, the first list element in the third list includes the sub-identifier of the first UWB device in the UWB device group, the first list element is used to indicate the measurement reporting information of the first UWB device, and the first UWB device is any one of the multiple UWB devices; the processing module is used to obtain the measurement reporting information of the multiple UWB devices in the UWB device group according to the sixth communication frame.
[0123] For possible implementations of the communication device of the sixteenth aspect, reference may be made to various possible implementations of the eighth aspect.
[0124] For the technical effects brought about by various possible implementation methods of the sixteenth aspect, reference may be made to the introduction to the technical effects of the eighth aspect or various possible implementation methods of the eighth aspect.
[0125] In a seventeenth aspect, an embodiment of the present application provides another communication device, comprising a processor coupled to a memory, the memory storing computer program instructions, the processor configured to execute the computer program instructions, causing the communication device to perform the method described in any one of aspects 1 to 8 above. Exemplarily, the communication device may be a chip, the processor may be a processing unit within the chip, and the memory may be a random access memory or cache within the chip.
[0126] In the embodiment of the present application, during the execution of the above method, the process of sending information (or signals) in the above method can be understood as the process of outputting information based on the instructions of the processor. When outputting information, the processor outputs the information to the transceiver so that it can be transmitted by the transceiver. After being output by the processor, the information may also need to undergo other processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before being input into the processor.
[0127] For operations such as sending and / or receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual functions or internal logic in the relevant descriptions, they can be generally understood as instructions output based on the processor.
[0128] During implementation, the processor may be a processor specifically configured to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. For example, the processor may also be configured to execute a program stored in a memory. When the program is executed, the communication device performs the method described in the first aspect or any possible implementation of the first aspect.
[0129] In a possible implementation, the memory is located outside the communication device. In a possible implementation, the memory is located inside the communication device.
[0130] In a possible implementation, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.
[0131] In a possible implementation, the communication device further includes a transceiver, and the transceiver is configured to receive signals or send signals.
[0132] In the eighteenth aspect, an embodiment of the present application provides another communication device, which includes a processing circuit and an interface circuit, the interface circuit is used to obtain data or output data; the processing circuit is used to execute the method shown in any one of the above-mentioned first aspect to the above-mentioned eighth aspect.
[0133] In the nineteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program includes program instructions, which, when executed, enable the computer to execute the method shown in any one of the above-mentioned first to eighth aspects.
[0134] In the twentieth aspect, an embodiment of the present application provides a computer program product, which includes a computer program, and the computer program includes program instructions, which, when executed, enable the computer to execute the method shown in any one of the above-mentioned aspects from the first aspect to the eighth aspect.
[0135] In aspect 21, an embodiment of the present application provides a communication system, comprising the communication device described in aspect 9 or any possible implementation of aspect 9, and the communication device described in aspect 10 or any possible implementation of aspect 10.
[0136] In aspect 22, an embodiment of the present application provides a communication system, comprising the communication device described in aspect 11 or any possible implementation of aspect 11, and the communication device described in aspect 12 or any possible implementation of aspect 12.
[0137] In aspect 23, an embodiment of the present application provides a communication system, comprising the communication device described in aspect 13 or any possible implementation of aspect 13, and the communication device described in aspect 14 or any possible implementation of aspect 14.
[0138] In aspect 24, an embodiment of the present application provides a communication system, comprising the communication device described in aspect 15 or any possible implementation of aspect 15, and the communication device described in aspect 16 or any possible implementation of aspect 16.
[0139] In aspect 25, an embodiment of the present application provides a chip comprising a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes a method as shown in any one of aspects 1 to 8 above. BRIEF DESCRIPTION OF THE DRAWINGS
[0140] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.
[0141] FIG1 shows a schematic diagram of various stages of a distance measuring wheel;
[0142] FIG2 is a schematic diagram showing a distance measurement block;
[0143] FIG3 is a schematic diagram of an NBA-MMS UWB ranging initialization process and ranging process;
[0144] FIG4A is a schematic diagram of a one-to-many NBA-MMS UWB ranging;
[0145] FIG4B is a schematic diagram of one-to-many NBA-MMS UWB ranging based on an interleaved pattern;
[0146] FIG5 is a flow chart of discovery and connection between a controller and a controlled entity;
[0147] FIG6 is a schematic diagram of an example of a star topology;
[0148] FIG7 is a schematic diagram of an example of a point-to-point topology or a mesh topology;
[0149] FIG8 is an example of a UWB system to which the technical solution provided in an embodiment of the present application is applicable;
[0150] FIG9 is an interactive flow chart of a communication method for UWB provided in an embodiment of the present application;
[0151] FIG10 is an interactive flow chart of another communication method for UWB provided in an embodiment of the present application;
[0152] FIG11 is an interactive flow chart of another communication method for UWB provided in an embodiment of the present application;
[0153] FIG12 is an interactive flow chart of another communication method for UWB provided in an embodiment of the present application;
[0154] FIG13 is an interactive flow chart of another communication method for UWB provided in an embodiment of the present application;
[0155] FIG14 is an interactive flow chart of another communication method for UWB provided in an embodiment of the present application;
[0156] FIG15 is an interactive flow chart of another communication method for UWB provided in an embodiment of the present application;
[0157] FIG16 is a schematic structural diagram of a communication device 1600 provided in an embodiment of the present application;
[0158] FIG17 is a schematic structural diagram of another communication device 170 provided in an embodiment of the present application;
[0159] FIG18 is a schematic structural diagram of another communication device 180 provided in an embodiment of the present application. DETAILED DESCRIPTION
[0160] The terms "first" and "second" in the specification, claims and drawings of the present application are only used to distinguish different objects, rather than to describe a specific order. It will be understood that the various digital numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and inherent logic. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.
[0161] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It will be understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0162] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification of the present application and the appended claims, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include plural expressions, unless there is a clear contrary indication in the context. It should also be understood that the term "and / or" used in the present application refers to and includes any or all possible combinations of one or more listed items. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The term "multiple" used in the present application refers to two or more. In the textual description of the present application, the character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0163] It is understood that in each embodiment of the present application, "A corresponds to B" means that there is a corresponding relationship between A and B, and B can be determined according to A. However, it should also be understood that determining (or generating) B according to (or based on) A does not mean that B is determined (or generated) only according to (or based on) A, and B can also be determined (or generated) according to (or based on) A and / or other information.
[0164] In order to facilitate understanding of the solutions of the present application, the following first introduces the terms and technical solutions involved in the embodiments of the present application.
[0165] Narrow-band assisted multi millisecond ultra-wideband (NBA-MMS UWB).
[0166] UWB systems have a large bandwidth, requiring UWB devices to transmit and receive ultra-high-speed data. However, impulse radio ultra-wideband (IR-UWB) systems, which rely on pulse transmission, have low spectral efficiency. When transmitting the same information, IR-UWB solutions consume significantly more power than other narrowband, short-range protocols (such as Bluetooth or ZigBee). In ranging, positioning, or sensing scenarios, the accuracy of UWB device measurement, positioning, or sensing is significantly affected by the signal bandwidth. The larger the signal bandwidth, the higher the accuracy of the sensing, positioning, or ranging capability of the UWB device. Therefore, it is considered to transmit and receive signals used for ranging, positioning, or sensing via the UWB system, while transmitting all other data, control messages, and synchronization messages via narrowband (NB) protocols. This approach ensures ranging, positioning, or sensing accuracy while saving power.
[0167] The above-mentioned UWB technology solution that combines narrowband assisted UWB and multi-millisecond transmission is also called NBA-MMS UWB.
[0168] Ranging wheel, positioning wheel, sensing wheel, and measuring cycle.
[0169] In the IEEE 802.15.4z standard, a single ranging process is defined as a ranging round. In the IEEE 802.15.4z standard, a ranging round is defined as: a ranging round is a period of sufficient duration to complete one entire range-measurement cycle involving the set of ERDEVs participating in the ranging exchange. The minimum processing time unit of each ranging round is a ranging slot. Exemplarily, a ranging round can be divided into three phases: a ranging control phase, a ranging phase, and a measurement report phase, as shown in Figure 1. Figure 1 shows a schematic diagram of each phase of a ranging round. In the IEEE 802.15.4z standard, the ranging control phase includes one ranging slot, while in the IEEE 802.15.4ab standard currently under discussion and specification, the ranging control phase may include more than one ranging slot.
[0170] In the first time slot of the ranging wheel shown in Figure 1, the controller sends a ranging control message (RCM). The RCM may carry updates about the wheel structure of the ranging wheel, such as an update to the round duration.
[0171] The new and old ranging rounds (hereinafter referred to as rounds) may be adjacent or non-adjacent in time. The durations of different rounds may be the same or different. The following description assumes that the durations of different rounds are the same.
[0172] Figure 2 illustrates the situation where the old and new ranging rounds are not adjacent in time. Figure 2 is a schematic diagram of a ranging block. As shown in Figure 2, a ranging block can be a time structure containing multiple ranging rounds. Optionally, the ranging block may recur periodically. Optionally, the duration of each ranging round in a ranging block is equal. As shown in Figure 2, for a specific ranging process, its initiator and responder will conduct a ranging round within a ranging block, such as Round 1 of ranging block (M-1) shown in Figure 2. After the ranging round is completed, the specific ranging process will be conducted in Round 1 of the next ranging block (i.e., Block M). As shown in Figure 2, two consecutive Round 1s are not adjacent in time, meaning that there is a time interval between them. During the time interval between two consecutive Round 1s, the UWB device can shut down the receiver and put it into sleep mode to save power. The durations of adjacent ranging blocks can be the same or different. For example, ranging blocks with different durations of adjacent ranging blocks may be located in a hyper-block. The following description assumes that the durations of adjacent ranging blocks are the same.
[0173] In this application, the initiator can be referred to as the initiator, that is, the UWB device that initiates the ranging / perception / positioning / communication process. During the ranging / perception / positioning / communication process, the initiator can be either the transmitter or the receiver. In this application, the responder can be referred to as the responder, that is, the UWB device that responds to the ranging / perception / positioning / communication process initiated by the initiator. During the ranging / perception / communication process, the responder can be either the transmitter or the receiver.
[0174] Before conducting (or starting) NBA-MMS UWB ranging, the relevant devices need to conduct (or execute) an initialization and establishment process. Taking the initiator as the controller as an example, the initiator first broadcasts a notification message to inform all responders that NBA-MMS UWB ranging is currently being conducted. The broadcast notification message can be carried by an advertisement poll (ADV-POLL) message. After receiving the ADV-POLL message, if the responder needs to conduct ranging, it can feedback an advertisement response message / advertisement response (ADV-RESP) message to the initiator. The ADV-RESP message can carry the parameter configuration information required by the responder (hereinafter referred to as parameter configuration). After receiving the ADV-RESP message, the initiator can decide whether to confirm and adopt the parameter configuration proposed by the responder, and can inform the responder of the final parameter configuration through the start-of-ranging (SOR) message. Exemplarily, the SOR message may carry a confirmation message for the parameter configuration in the ADV-RESP message. Exemplarily, the SOR message may carry a change / update message for the parameter configuration in the ADV-RESP message.
[0175] After the responder receives the SOR message, after a certain interval, the initiator and responder can start the NBA-MMS UWB ranging process. The length of this interval can be determined by the Time Offset to MMS POLL information in the SOR message. Figure 3 shows an NBA-MMS UWB ranging initialization process and a schematic diagram of the ranging process. As shown in Figure 3, the NBA-MMS UWB ranging initialization process includes: the initiator broadcasts an ADV-POLL message; the responder responds to the ADV-POLL message with an ADV-RESP message; after receiving the ADV-RESP message, the initiator sends a SOR message; the NBA-MMS UWB ranging process includes: the initiator and responder exchange query / initiate (POLL) messages and response (RESP) messages, multi-millisecond (MMS) block interactive ranging, and ranging result reporting (report) interaction.
[0176] NBA-MMS UWB ranging can be applied in one-to-one scenarios, where one initiator corresponds to one responder, or in one-to-many scenarios, where one initiator corresponds to multiple responders, as shown in Figure 4A. Figure 4A is a schematic diagram of one-to-many NBA-MMS UWB ranging.
[0177] In the one-to-many NBA-MMS UWB ranging shown in Figure 4A, the initiator and each responder carry out NBA-MMS UWB ranging one by one. That is, the initiator and each responder will complete the interaction of POLL messages and RESP messages, MMS block interactive ranging, and ranging result reporting (report) interaction process. The ranging result report includes both the responder's report to the initiator and the initiator's report to the responder. The ranging process shown in Figure 4A can be called a one-to-many NBA-MMS UWB ranging based on the concatenation mode. It should be noted that the present application is also applicable to one-to-many ranging processes in other modes, for example, one-to-many NBA-MMS UWB ranging based on the interlacing mode, see Figure 4B. Figure 4B is a schematic diagram of a one-to-many NBA-MMS UWB ranging based on the interlacing mode. As shown in FIG4B , in one-to-many NBA-MMS UWB ranging based on the interleaved mode, each responder sends MMS blocks in sequence, rather than waiting for the previous responder to send all MMS blocks before the next responder sends all MMS blocks.
[0178] In an embodiment of the present application, a single positioning process, i.e., the process of completing a positioning task, is defined as a positioning wheel. The positioning wheel can be called by other names, which are not limited by this application. The positioning wheel can be a time period (or time cycle) sufficient to complete a complete positioning task. The meaning of the positioning wheel is similar to that of the ranging wheel, the difference being that one is the time cycle corresponding to ranging, and the other is the time cycle corresponding to positioning. The minimum processing time unit of each positioning wheel is the positioning slot. In a positioning wheel, it can be divided into three phases: the positioning control phase, the positioning phase, and the positioning report phase.
[0179] In an embodiment of the present application, a single perception process, that is, a process of completing a perception task, is defined as a perception round. The perception round can be other names, which are not limited in this application. The perception round can be a time period (or time period) sufficient to complete a complete perception task. The meaning of the perception wheel is similar to that of the ranging wheel, the difference being that one is the time period corresponding to ranging and the other is the time period corresponding to perception. The minimum processing time unit of each perception round is the sensing slot. In a perception round, it can be divided into three phases: the sensing control phase, the sensing phase, and the sensing report phase.
[0180] A measurement cycle is the time period during which one or more UWB devices complete one or more measurement tasks. These tasks can include ranging, positioning, or sensing. A measurement cycle can be a ranging, positioning, or sensing round.
[0181] In addition, it should be noted that the names of the different stages in a single measuring wheel (such as a ranging wheel, a sensing wheel, a positioning wheel, etc.) are only examples and do not constitute any limitation on the scope of protection of this application. For example, the above-mentioned measurement control stage can be understood as a stage for configuring the parameters required in the measuring wheel. For another example, the above-mentioned measurement stage can be understood as a stage for performing measurements. For another example, the above-mentioned measurement result reporting stage can be understood as a stage for reporting measurement results, and can also be called the end of the measurement stage. In addition, it should be noted that in the embodiments of the present application, the size of each field represents the number of bits occupied by each field.
[0182] The following describes a discovery and association process between a controller and a controlled entity.
[0183] Figure 5 is a flow chart of discovery and connection between a controller and a controlled party. The controller can be the initiator, and the controlled party can be the responder. As shown in Figure 5, the discovery and connection process between the controller and the controlled party includes: the controlled party sends a connection request frame (Association Request Command) frame to the controller; after receiving the connection request frame, the controller returns a connection response frame (Association Response Command) frame to the controlled party, and the connection response frame is used to inform the controlled party whether access is allowed. The connection request frame can be called an Association Request frame. The connection response frame can be called an Association Response frame. Exemplarily, the content field of the connection response frame will carry the content shown in Table 1 below.
[0184] Table 1
[0185] The Association Status field indicates the association status; its specific values and meanings are shown in Table 2 below. The Session Configuration field indicates the basic configuration information for the session during the current task. The Updated Short Address field indicates the updated short address assigned to the controlled party, which is different from the short address in the control party's connection request frame header. In this document, octets represent bytes. For example, in Table 1, octets: 1 indicates that the Association Status field is one byte long; octets: 0 / 1 indicates that the Session Configuration field is either 0 bytes long (i.e., not included in Table 1) or one byte long. For another example, a field length of octets: 2 / 8 indicates, as shown in Table 5 below, that the field length is either 2 bytes or 8 bytes. The length of fields represented by octets is uniformly described here and will not be further elaborated below. Furthermore, the names, positions, and lengths of the fields in each table are not specified in this document. In other words, the fields in the tables provided herein are examples only, and the names, positions, and lengths of the fields are not specified.
[0186] Illustratively, the Updated Short Address field exists only when Association Status = 0x04, as shown in Table 2 below.
[0187] Table 2
[0188] When Association Status = 0x04, it indicates that the current short address of the controlled device is already occupied / allocated / duplicate. The controller needs to return a new short address to the controlled device, which is the Updated Short Address field in Table 1. The controlled device will use the Updated Short Address in Table 1 as its updated short address for device identification purposes during information exchange with the controller.
[0189] The process in Figure 5 can only handle the connection interaction between a single responder and initiator. A UWB device group includes multiple devices that support the UWB standard. The process in Figure 5 cannot use the interaction of a connection request frame and a connection response frame to complete the discovery and connection of multiple devices in the UWB device group. Therefore, it can only use multiple connections. The interaction of request frames and response frames can complete the discovery and connection of multiple devices in the UWB device group, resulting in a large signaling overhead. Therefore, it is necessary to study a solution for discovering and connecting multiple UWB devices in a UWB device group with less signaling overhead. To this end, the present application provides a solution for discovering and connecting multiple UWB devices in a UWB device group with less signaling overhead. Compared with the process in Figure 5, the technical solution provided by the present application can reduce the number of signaling interactions between the initiator and the responder, and reduce the duration of the connection phase, that is, improve the connection efficiency.
[0190] The following describes a solution for unified scheduling of multiple different types of services.
[0191] In order to achieve unified scheduling of multiple different types of services, a unified scheduling information element (IE) can be used to implement scheduling instructions for multiple different types of services. For example, the format of a scheduling information element is shown in Table 3 below.
[0192] Table 3
[0193] In Table 3, the Scheduling List Length field occupies bits 0-3; the Scheduling List Type field occupies bits 4-6; the Address Size field occupies bit 7; the Receiver Address Present field occupies bit 8; and the Reserved field occupies bits 9-15. The bits occupied by a field are indicated in a similar manner below and are not further explained. In this document, if the length of a field is indicated by "Octets: Variable" or "Variable," the length of the field is variable. The meanings of some fields in Table 3 are as follows.
[0194] The Scheduling List Length field indicates the number of scheduling list elements contained in the Scheduling List field. The Scheduling List field contains multiple scheduling list elements. Each scheduling list element contains a device short address. In other words, each scheduling list element in Table 3 can only be used to provide scheduling information for a single device.
[0195] Address Size field: Indicates the type of the device address. For example, if the value of the Address Size field is 0, it indicates that the device address is a short address; if the value of the Address Size field is 1, it indicates that the device address is a long address.
[0196] Receiver Address Present field: Indicates whether the Receiver Address field exists in the scheduling cell. For example, if the value of the Receiver Address Present field is 0, it means that the Receiver Address field does not exist; if the value of the Receiver Address Present field is 1, it means that the Receiver Address field exists.
[0197] The Reserved field is a reserved field.
[0198] Scheduling List Type field: indicates the scheduling method used by each scheduling list element in the Scheduling List field; the scheduling method represented by the value (or numerical value) of the Scheduling List Type field is shown in Table 4 below.
[0199] Table 4
[0200] For example, in combination with Tables 3 to 4, under the various values of the Scheduling List Type field, the corresponding formats of the scheduling list elements in the SchedulingList in Table 3 are shown in Tables 5 to 9 below. When Scheduling List Type = 0, the scheduling list element format of Per-Slot scheduling is shown in Table 5 below. When Scheduling List Type = 1, the scheduling list element format of Consecutive scheduling is shown in Table 6 below. When Scheduling List Type = 2, the scheduling list element format of Bitmap-based scheduling is shown in Table 7 below. When Scheduling List Type = 3, the scheduling list element format of Periodic scheduling is shown in Table 8 below. When Scheduling List Type = 4, the scheduling list element format of FRU transmission scheduling is shown in Table 9 below.
[0201] Table 5
[0202] Among them, Slot Index represents the index of the scheduling time slot, and Sender Address represents the address of the sending end device (which may be referred to as the sending end).
[0203] Table 6
[0204] Sender Address indicates the address of the sending device.
[0205] Table 7
[0206] The meanings of the fields in Table 7 are as follows: Scheduling Bitmap Size indicates the length of the Scheduling Bitmap; the Bitmap Offset field indicates the bitmap offset; Scheduling Bitmap indicates the bitmap required for scheduling. Sender Address indicates the address of the sending device. Receiver Address indicates the address of the receiving device (receiver).
[0207] Table 8
[0208] The meanings of the fields in Table 8 are as follows: the Starting Slot Index field indicates the starting time slot of the device scheduling; the Scheduling Step field indicates the time step or period of the scheduling; the Scheduling Repetition field indicates the number of repetitions of the scheduling; and the Sender Address indicates the address of the sending device.
[0209] Table 9
[0210] The meanings of the fields in Table 9 are as follows: The Starting Slot Index field, the Starting Slot Index field, the Scheduling Repetition field, and the Sender Address field are consistent with those in Table 8 and are not repeated here. The Receiver Address field indicates the address of the receiving device. The Sequence Index field indicates the sequence index of the sequence required for ranging. The Number of Gaps field indicates the number of time slots used by the sequence. The Sequence Repetition field indicates the number of repetitions of the sequence.
[0211] In the above-mentioned scheme for unified scheduling of multiple different types of services, each scheduling list element schedules and allocates time slots for a device. If scheduling is allocated to multiple devices in a UWB device group in advance, multiple scheduling list elements are required, which will lead to a large signaling overhead. Each scheduling list element contains at least one short address. When there are multiple scheduling list elements, it will lead to a large scheduling signaling overhead. Therefore, it is necessary to study a scheduling scheme for devices in a UWB device group with low signaling overhead. The present application also provides a scheduling scheme for devices in a UWB device group, which can reduce signaling overhead. Furthermore, the present application also provides a measurement information reporting scheme for UWB device groups.
[0212] The following describes the scenarios to which the technical solutions provided in this application are applicable.
[0213] The technical solution provided in this application can operate in a star topology, a point-to-point topology, or a mesh topology. The technical solution provided in this application can also operate in other topologies, which are not limited by this application. Figure 6 is a schematic diagram of an example of a star topology. As shown in Figure 6, the star topology involves a central control node, such as the personal area network (PAN) or coordinator shown in Figure 6. The technical solution provided in this application is applicable to data communication / perception / ranging / positioning between the central control node and one or more other devices in a star topology. Figure 7 is a schematic diagram of an example of a point-to-point topology or a mesh topology. The technical solution provided in this application is also applicable to communication / perception / ranging / positioning between different devices in a point-to-point topology or a mesh topology (Figure 7). In Figures 6 and 7, the black nodes are full-function devices (FFDs) and the white nodes are reduced-function devices (RFDs). FFDs can act as PAN coordinators or coordinators, while RFDs cannot act as PAN coordinators or coordinators. FFD devices can communicate with each other and between FFD devices and RFD devices. RFD devices cannot communicate directly with each other and can only communicate with FFD devices or forward data through an FFD device. In a UWB system, an FFD can be an anchor device or a tag device with strong computing capabilities (such as a UWB tag installed on a smartphone); while an RFD is a tag device with only partial computing capabilities.
[0214] The technical solutions provided in this application are mainly applicable to UWB systems, such as UWB systems that support IEEE 802.15.4a standard, IEEE 802.15.4z standard, IEEE 802.15.4ab standard, or the next generation standard of IEEE 802.15.4ab standard. It will be readily understood by those skilled in the art that the various aspects involved in this application can be extended to other networks that adopt various standards or protocols, such as BLUETOOTH (Bluetooth), high performance wireless LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe) and wide area network (WAN), personal area network (PAN) or other networks now known or developed later. Therefore, regardless of the coverage range and wireless access protocol used, the technical solutions provided in this application can be applied to any suitable wireless network.
[0215] Refer to Figure 8, which is an example of a UWB system to which the technical solution provided in an embodiment of the present application is applicable. The UWB system includes a controller, one or more UWB device groups (only UWB device group #1 and UWB device group #2 are shown). A UWB device group includes a proxy device and one or more non-proxy devices. As shown in Figure 8, UWB device group #1 includes proxy device #1, and one or more non-proxy devices (only device #1 and device #2 are shown); UWB device group #2 includes proxy device #2, and one or more non-proxy devices (only device #3 and device #4 are shown). It should be noted that the oval in Figure 8 represents a UWB device group, not a geographical area. The protocols supported by the controller and the devices in the UWB device group may include IEEE 802.15.4a, IEEE 802.15.4z, IEEE 802.15.4ab and other protocols. Of course, with the continuous evolution and development of communication technology, the WLAN protocol may also include the next generation protocol of IEEE 802.15.4ab, etc. The controller may be an access point, and the devices in the UWB device group may be stations (STAs). Both the access point and the STA support a WLAN protocol, which may include IEEE 802.11be (also known as Wi-Fi 7, EHT protocol).
[0216] An access point is a device with wireless communication capabilities that supports WLAN protocols and can communicate with other devices in a WLAN network (such as stations or other access points). It can also communicate with other devices. In a UWB system, there are one or more access point (AP) stations and one or more non-AP stations (non-AP STAs). For ease of description, this document refers to access point stations as access points (APs) and non-AP stations as stations (STAs).
[0217] An access point can be a complete device or a chip or processing system installed in a complete device. Devices equipped with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of the chip or processing system (i.e., AP). The AP in the embodiments of the present application is a device that provides services to stations (STAs) and can support, for example, IEEE 802.15.4a, IEEE 802.15.4z, IEEE 802.15.4ab or their successors. For example, an AP can be a communication entity such as a communication server, a router, a switch, a bridge, a computer, or a mobile phone. APs may include anchor points, macro base stations, micro base stations (also known as small stations), pico base stations, femto base stations, relay stations, access points, gNBs, transmission reception points (TRPs), evolved Node Bs (eNBs), radio network controllers (RNCs), home base stations (e.g., home evolved Node Bs, or home Node Bs, HNBs), base band units (BBUs), WiFi access points (APs), integrated access and backhaul (IABs), etc. Of course, APs may also be chips and processing systems in these various forms of devices, thereby implementing the methods and functions of the embodiments of the present application.
[0218] A station is a device with wireless communication capabilities that supports communication using the WLAN protocol and has the ability to communicate with other stations or access points in a WLAN network. For example, a STA is any communication device that allows a user to communicate with an AP and, in turn, with a WLAN. This communication device can be a complete device, or a chip or processing system installed in a complete device. Devices equipped with these chips or processing systems can implement the methods and functions of the embodiments of this application under the control of the chip or processing system (i.e., the station). STAs may include tags / smart tags, mobile phones, mobile stations (MS), tablet computers, computers with wireless transceiver capabilities (e.g., laptops), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, subscriber units, cellular phones, wireless data cards, personal digital assistants (PDAs), tablet computers, laptop computers, and machine type communication (MTC) terminals. Stations may include various handheld devices with wireless communication capabilities, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem. For example, a station can be a handheld device (handset) with wireless communication capabilities, an in-vehicle device, a wearable device, or a terminal in the Internet of Things (IoT), the Internet of Vehicles (IoV), or any terminal in 5G and post-5G communication systems, etc. This application does not limit this. The station can support the IEEE 802.15 series of protocols, such as IEEE 802.15.4a, IEEE 802.15.4z, and IEEE 802.15.4ab.
[0219] It should be noted that, unless otherwise specified, the following description assumes that the initiator is the controller and the responder is the controlee. The technical solutions proposed in this application are applicable to the case where the responder is the controller or the controller is a third-party device. In other words, the following description assumes that the initiator and controller are synonymous, and the responder and controlee are synonymous, unless otherwise specified.
[0220] In addition, unless otherwise specified, the following description assumes a one-to-many scenario, that is, a scenario where one initiator corresponds to multiple responders. The corresponding description can naturally be extended to the scenario where multiple initiators correspond to multiple responders, and the technical solutions proposed in this application are applicable to all of them.
[0221] In addition, this application does not impose any restrictions on the signals carrying the various frames mentioned below, such as the Association Request Command frame, the Association Response Command frame, the frame carrying scheduling information, and the frame carrying measurement report content. For example, the signal carrying these frames can be a UWB signal, a narrowband signal, or a Bluetooth signal.
[0222] In addition, unless otherwise specified, the following description assumes that the ranging process is used as an example. The corresponding description applies to other measurement processes, such as perception and positioning, and the technical solutions proposed in this application are applicable. In other words, the following description takes the ranging process as an example.
[0223] In addition, unless otherwise specified, the following descriptions of the distance measuring wheels assume that the time between the new and old rounds is not adjacent. The corresponding descriptions are applicable to the case where the distance measuring wheels are adjacent in time.
[0224] The following description will be made by taking the short address length as 2 bytes as an example. When the short address length is other lengths, the technical solutions proposed in the embodiments of the present application are also applicable and will not be described in detail here.
[0225] In addition, the embodiments of the present application do not impose any limitation on the values of the Association Status field that appear below, and the values used in the demonstrations given are only examples.
[0226] The following first introduces the discovery and connection scheme of multiple UWB devices within a UWB device group provided by this application in conjunction with Figure 9. Figure 9 is an interactive flow chart of a communication method for UWB provided by an embodiment of this application. As shown in Figure 9, the method includes:
[0227] 901. A proxy device generates a first communication frame.
[0228] A proxy device (proxy) can be a UWB device in a UWB device group, and the proxy device can interact with the controller (or initiator) as a representative of each UWB device in the UWB device group (i.e., the controlled or responder). Exemplarily, the proxy device is the UWB device in the UWB device group that receives the best signal quality from the controller. Exemplarily, the proxy device is the UWB device in the UWB device group that is closest to the controller. Exemplarily, the proxy device is the device with the most remaining power or the strongest signal transceiving capability in the UWB device group. Exemplarily, each device in the UWB device group can select a proxy device according to a certain rule. The rule for selecting a proxy device can be the most remaining power, the strongest signal transceiving capability, the closest distance to the controller, or the best signal quality of receiving the controller, etc. The embodiments of the present application do not limit the rules for selecting a proxy device.
[0229] In one possible implementation, the proxy device performs the following operations before executing step 901: obtaining (receiving) the device capability information of multiple UWB devices in the UWB device group. That is, the proxy device can summarize the device capability information of each UWB device in the UWB device group in which it is located. Exemplarily, each UWB device in the UWB device group (except the proxy device) sends its own device capability information to the proxy device through a wired network or wireless connection with the proxy device. For example, each UWB device in the UWB device group can be connected by wire, and the proxy device is the coordinator, and each UWB device transmits its own device capability information to the proxy device through wired transmission. The proxy device can also obtain the device capability information of multiple UWB devices in the UWB device group by other means, which are not limited here.
[0230] The first communication frame includes a first field. This first field is used to indicate the device capabilities of multiple UWB devices in the UWB device group. For example, the first communication frame can be an Association Request Command frame, or another communication frame used to enable discovery and connection between a controller and a controlled device. The following description assumes that the first communication frame is an Association Request Command frame.
[0231] In one possible implementation, the first communication frame further includes a fourth field, which is used to indicate that the first communication frame comes from a proxy device in the above-mentioned UWB device group. Exemplarily, the length of the fourth field is 1 bit; when the value of the fourth field is 1, the fourth field is used to indicate that the first communication frame comes from a proxy device in the UWB device group; when the value of the fourth field is 0, the fourth field is used to indicate that the first communication frame comes from a non-proxy device in the UWB device group. The fourth field is also used to indicate that the short address indicated in the Source Address field in the first communication frame is the short address of the proxy device, and the short address also serves as the group identifier (group ID) of the UWB device group to which the proxy device belongs. Exemplarily, when the value of the fourth field is 1, the fourth field is used to indicate that the short address indicated in the Source Address field in the first communication frame is the short address of the proxy device, and the short address also serves as the group identifier of the UWB device group to which the proxy device belongs. The fourth field can be called a Group Proxy Indicator field, or can be called other fields, which is not limited in the embodiments of the present application.
[0232] In one possible implementation, the first field is used to indicate a first device capability, which is a device capability possessed by each UWB device in the UWB device group; or the first field includes multiple capability list elements, with one capability list element in the first field indicating a device capability of one of the multiple UWB devices. If the first field indicates the first device capability, it indicates (or implies) that all devices in the UWB device group where the proxy device resides have the same device capability, namely, the first device capability. If the first field includes multiple capability list elements, it indicates that the device capabilities possessed by each device in the UWB device group where the proxy device resides are not necessarily the same. The first field is used to indicate the device capabilities of multiple UWB devices in the UWB device group. The first field may be called a UWB HRP Capability Information List field. The first field may be a capability information list, comprising one or more capability list elements. When the first field includes one capability list element, the capability list element indicates the first device capability. When the first field includes multiple capability list elements, the capability list element in the first field indicates the device capability of one of the multiple UWB devices.
[0233] Exemplarily, the first communication frame further includes a fifth field; when the value of the fifth field is the first value, the first field is used to indicate the capability of the first device; when the value of the fifth field is the second value, the first field includes the multiple capability list elements. For example, the first value is 0 and the second value is 1. The fifth field is used to indicate the type of the first field. In other words, the fifth field is used to indicate the format type adopted by the first field. The fifth field may be referred to as a Capability Information List Type field. For example, when the value of the fifth field is 0 (i.e., Capability Information List Type = 0), the first field only includes one capability list element, which indicates the capability of the first device. An example of the first field is shown in Table 10 below.
[0234] Table 10
[0235] The meaning of each field in Table 10 is as follows: The LPDC field indicates whether the current device supports Low-density Parity-check (LDPC). For example, when the value of the LPDC field is 0, it means that the current device does not support LDPC; when the value of the LPDC field is 1, it means that the current device supports LDPC.
[0236] The High Throughput field indicates whether the current device supports high throughput. For example, if the value of the High Throughput field is 0, it means that the current device does not support high throughput; if the value of the High Throughput field is 1, it means that the current device supports high throughput.
[0237] The Supported AIFS field indicates the set of acknowledgment interframe spacing (AIFS) values supported by the current device, such as 16us, 32us, 64us, etc. In this document, the TBD (To be determined) field indicates a reserved field, that is, an undefined field.
[0238] For another example, when the value of the fifth field is 1 (i.e., Capability Information List Type = 1), the first field includes multiple capability list elements, and a capability list element in the first field is used to indicate the device capability of a UWB device among multiple UWB devices. An example of the first field is shown in Table 11 below.
[0239] Table 11
[0240] The capability information list (i.e., the first field) shown in Table 11 contains N capability list elements. Among them, the value N can be determined by the Number of controlees within the Group field in the first communication frame, and the Number of controlees within the Group field is used to indicate the number of UWB devices (including proxy devices) in the UWB device group. Exemplarily, the format of each capability list element in Table 11 is consistent with Table 10 and is not repeated here. Exemplarily, the capability list element in the first field may include a device short address field, that is, a field for the device short address. For example, UWB HRP Capability Information List#0 in Table 11 includes the short address of device #0; UWB HRP Capability Information List#1 in Table 11 includes the short address of device #1; UWB HRP Capability Information List#N-1 in Table 11 includes the short address of device #N-1. Exemplarily, the capability list element in the first field may include a device long address field, that is, a field for the device long address. For example, UWB HRP Capability Information List#0 in Table 11 includes the long address of Device#0; UWB HRP Capability Information List#1 in Table 11 includes the long address of Device#1; and UWB HRP Capability Information List#N-1 in Table 11 includes the long address of Device#N-1.
[0241] It should be pointed out that: in combination with Tables 10 to 11, each capability list element may not contain the device short address field. For example, referring to Table 11, the order in which the capability list elements appear in the first field corresponds to the sub-identifier of each device in the UWB device group, that is, Sub-ID. In Table 11, the 0th list element in the first field corresponds to the device with sub-identifier 0 in the UWB device group, that is, device #0; the 1st list element in the first field corresponds to the device with sub-identifier 1 in the UWB device group, that is, device #1; the N-1th list element in the first field corresponds to the device with sub-identifier 1 in the UWB device group, that is, device #N-1.
[0242] In other words, the controller can obtain the device capability information of the device with sub-identifier i in the UWB device group by reading the i-th capability list element (0≤i≤N-1) in Table 11. Exemplarily, the controller uses the device capability indicated by the i-th capability list element in the first field as the device capability of the UWB device with sub-identifier i in the UWB device group. The role of including the device short address field in the capability list element is to indicate which device the capability list element corresponds to, that is, which device the capability list element indicates the device capability of. The order in which the capability list elements in the first field appear can indicate which device each capability list element corresponds to. For example, the 0th list element in the first field corresponds to the device with sub-identifier 0 in the UWB device group. Since the order in which the capability list elements in the first field appear can serve as the device short address, the device short address field may not be included in the capability list element.
[0243] Exemplarily, the first field includes multiple capability list elements, and one capability list element in the first field is used to indicate the device capability of one of the multiple UWB devices; after receiving the first communication frame, the controller performs the following operations: based on the order of the f-th capability list element in the multiple capability list elements, determining the sub-identifier of the device corresponding to the f-th capability list element, where f is an integer greater than or equal to 1. Exemplarily, the capability list in the first field includes multiple capability list elements, and the f-th capability list element in the capability list is used to indicate the device capability of device #f in the UWB device group, and the f-th capability list element is the f-th capability list element in the capability list; determining the sub-identifier of the device corresponding to the f-th capability list element (i.e., device #f) to be f. In this implementation, the sub-identifier of the device corresponding to the f-th capability list element is determined based on the order of the f-th capability list element in the multiple capability list elements. The first communication frame does not need to carry information indicating the sub-identifier, which can save signaling overhead.
[0244] Exemplarily, the first field includes multiple capability list elements, and the multiple capability list elements have a mapping relationship with the device addresses of the above-mentioned multiple UWB devices. In this article, the device address includes a device short address (e.g., 2 bytes) and a device long address (e.g., 8 bytes). For example, the i-th capability list element in the first field is used to indicate the device capabilities of the i-th UWB device, and the order of the i-th capability list element in the above-mentioned multiple capability list elements and the device address of the proxy device in the above-mentioned UWB device group are used to determine the device address of the above-mentioned i-th UWB device, where i is an integer greater than or equal to 0. Assuming that the order of the i-th capability list element in the above-mentioned multiple capability list elements is i (i.e., the i-th capability list element), and the device address of the proxy device is A, then the device address of the i-th UWB device is A+i.
[0245] 902. The proxy device sends a first communication frame to the controller.
[0246] Accordingly, the controller receives the first communication frame from the proxy device. The proxy device is the controlled entity. Exemplarily, the proxy device and the devices in the UWB device group in which the proxy device resides are all stations, and the controller is the AP. Exemplarily, the proxy device and the devices in the UWB device group in which the proxy device resides are all APs, and the controller is the station. An example of the first communication frame is shown in Table 12 below.
[0247] Table 12
[0248] The meanings of the fields in Table 12 are as follows: The Frame Control field indicates the frame control field. The Sequence Number indicates the frame count. The Destination Address field indicates the destination address of the current frame, that is, the address of the receiving device. The Source Address field indicates the source address of the current frame, that is, the address of the sending device. The AuxiliarySecurityHeader field indicates the additional security enhancement function frame header. IE indicates the information element field. The Command ID field indicates the type corresponding to the current frame. The Content field indicates the content contained in the current frame. The Frame Check Sequence (FCS) is used to check whether the current frame has errors.
[0249] Note: When the frame header (MAC header, MHR) shown in Table 12 is the MHR of the Association Request Command frame, the value of the command ID field is 0x01, which will not be repeated below.
[0250] In this document, the symbol " / " means "or". For example, "0 / 1" means "0 byte" or "1 byte". For another example, "0 / 2 / 8" means "0 field" or "2 bytes" or "8 bytes". Exemplarily, whether "0 / 1" means 0 byte or 1 byte is determined by the control information. For example, for Table 12, "0 / 1" means 0 byte or 1 byte, which is determined by the Frame Control field. Similarly, for Table 12, "0 / 2 / 8" means "0 field" or "2 bytes" or "8 bytes", which is determined by the Frame Control field.
[0251] An example of the Frame Control (FC) field in Table 12 is shown in Table 13 below.
[0252] Table 13
[0253] The meaning of each field in Table 13 is as follows: The Frame type field indicates the frame type. The Security enabled field indicates whether the security capability is enabled. The Frame Pending field indicates whether the frame is waiting for processing. The AR field indicates whether the confirmation reception request is triggered. The PAN ID Compression field indicates the compression of the PAN ID field, where PAN represents personal area networks. The Group Proxy Indicator field indicates whether the current frame comes from the proxy device of the UWB group. The Sequence Number Suppression field is used to indicate whether the sequence number is compressed. The IE present field is used to indicate whether the IE exists in the current frame. The Destination Addressing Mode field is used to indicate the address type of the destination device address. The Frame Version field indicates the protocol version used by the current frame. The Source Addressing Mode field is used to indicate the address type of the source device address.
[0254] When the value of the Group Proxy Indicator field (ie, the first field) in Table 13 is 1, an example of the Content field in Table 12 is shown in Table 14 below.
[0255] Table 14
[0256] Session ID represents the service identifier owned by the current UWB service process. The Device Group List Management field is used to manage the format of the UWB HRP Capability Information List field (i.e., the first field). Exemplarily, the format of the Device Group List Management field is shown in Table 15 below. In this application, when TBD represents the length of the field, TBD represents any numerical value, and this application does not limit this. For example, the length of the UWB HRP Capability Information List field in Table 14 is expressed as Octets:TBD, indicating that the length of the field can occupy one or more bytes, that is, the length of the field is not limited. In other words, the length of the UWB HRP Capability Information List field can be flexibly configured as needed, and this application does not limit it.
[0257] Table 15
[0258] Capability Information List Type field (i.e., the fifth field): is used to indicate the format type adopted by the UWB HRP Capability Information List field (i.e., the first field) in Table 14. Exemplarily, when Capability Information List Type = 0, the first field includes only one capability list element, and an example of the first field is shown in Table 10; when Capability Information List Type = 1, the first field includes multiple capability list elements, and an example of the first field is shown in Table 11. The Number of controlees within the Group field is used to indicate the number of UWB devices (including proxy devices) within the UWB device group. The RFU field is a reserved field.
[0259] In one possible implementation, the proxy device assigns a short address to each device in the UWB device group to which it belongs. Exemplarily, before executing step 902, the proxy device performs the following operations: assigning a first address to the first UWB device, the first address being obtained by the device address of the proxy device in the UWB device group (i.e., the device short address) and the first sub-identifier of the first UWB device in the UWB device group, where the first UWB device is any device in the UWB device group. Exemplarily, the UWB device group includes N devices; the proxy device assigns short addresses A+1, A+2, ..., A+(N-1) to other devices in the UWB device group; where A is the short address of the proxy device. In other words, the device short addresses A to A+(N-1) will be assigned to all N devices in the UWB device group. The aforementioned values 0 to N-1 are the sub-identifiers (Sub-IDs) of each device in the UWB device group to which the proxy device belongs. Exemplarily, the Sub-ID of the proxy device is 0, that is, Sub-ID = 0 is assigned to the proxy device, that is, the short address A is the short address of the proxy device; the proxy device assigns the short address A+1 to the device with sub-identifier Sub-ID = 1; assigns the short address A+2 to the device with sub-identifier Sub-ID = 2; and so on. Each device in the UWB device group can know its own sub-identifier in the group. Exemplarily, the proxy device assigns a sub-identifier to each device in the UWB device group, so that the sub-identifiers of the N devices in the UWB device group are values 0 to N-1, where the sub-identifiers of any two devices are different. As can be seen from the foregoing, the short address A also serves as the group identifier Group ID of the UWB device group.
[0260] For example, based on the short address allocation method for proxy devices described above, the controller can know that the short address of the i-th device (with sub-identifier i in the UWB device group) in the UWB device group is A+i, where A is the short address of the proxy device. For example, the controller uses the device capabilities indicated by the i-th capability list element in the first field as the device capabilities of the device with the short address A+i. For another example, the controller uses A+i as the short address of the device associated with the i-th capability list element in the first field.
[0261] 903. The controller obtains device capabilities of multiple UWB devices in the UWB device group according to the first communication frame.
[0262] 904. The controller sends a connection response frame to the proxy device.
[0263] In response, the proxy device receives an Association Request Command frame from the controller. The Association Request Command frame is used to indicate whether multiple devices within the UWB device group are permitted to access the controller. In other words, the Association Request Command frame informs the proxy device whether multiple devices within the UWB device group are permitted to access the controller. Step 904 is one implementation method. The controller may also inform the proxy device whether multiple devices within the UWB device group are permitted to access the controller through other methods.
[0264] In one possible implementation, the connection response frame is used to indicate whether each device in the UWB device group is allowed to access the controller. In other words, the connection response frame is used to indicate that each device in the UWB device group is allowed to access the controller, or the connection response frame is used to indicate that each device in the UWB device group is not allowed to access the controller. Exemplarily, the first field in the first communication frame is used to indicate the first device capability, which is the device capability that each UWB device in the UWB device group has; the connection response frame is used to indicate whether each device in the UWB device group is allowed to access the controller, and the content field of the connection response frame is as shown in Table 1 above. In this example, the content field of the connection response frame can be regarded as including a list element, which is used to indicate whether each device in the UWB device group is allowed to access the controller.
[0265] In one possible implementation, the content field in the connection response frame includes multiple list elements, each list element is used to indicate whether a device in the UWB device group is allowed to access the controller. The format of each list element can be found in Table 1. Exemplarily, there are N devices in the UWB device group, and the content field in the connection response frame includes N list elements, each of which corresponds one-to-one to the N devices. Each list element is used to indicate whether its corresponding device is allowed to access the controller, where N is an integer greater than 1.
[0266] Exemplarily, the connection response frame includes a format indication field, which is used to indicate the format type used by the content field in the connection response frame. For example, when the value of the format indication field is 0, the format indication field is used to indicate that the content field in the connection response frame includes a single list element, as shown in Table 1. When the value of the format indication field is 1, the format indication field is used to indicate that the content field in the connection response frame includes multiple list elements, each list element corresponding to a device in the UWB device group, and the format of each list element can be found in Table 1.
[0267] In an embodiment of the present application, a proxy device sends a first communication frame to a controller; based on the first communication frame, the controller obtains the device capabilities of multiple UWB devices in a UWB device group. This reduces signaling overhead compared to each device in the UWB device group individually sending a communication frame indicating its capabilities to the controller. Furthermore, the proxy device sending the first communication frame to the controller takes less time than each device in the UWB device group individually sending a communication frame indicating its capabilities to the controller, thus saving time overhead.
[0268] If the controller finds that one or more short addresses provided by the proxy device are already occupied / allocated / duplicate, the controller will reallocate the short addresses of one or more devices in the UWB device group. The following describes a method for reallocating the short addresses of one or more devices in a UWB device group, provided in an embodiment of the present application, in conjunction with FIG10 .
[0269] FIG10 is another interactive flow of a communication method for UWB provided in an embodiment of the present application. The method flow in FIG10 can be understood as a process for a controller to reallocate the short addresses of one or more devices in a UWB device group. As shown in FIG10 , the method includes:
[0270] 1001. The proxy device sends a first communication frame to the controller.
[0271] Accordingly, the controller receives the first communication frame from the proxy device. Step 1001 can refer to step 902. For a description of the first communication frame, please refer to the description in Figure 9 and will not be repeated here. Note that in the embodiment shown in Figure 10, the first field in the first communication frame includes multiple capability list elements, each of which indicates the device capabilities of one of the multiple UWB devices. The capability list element may or may not include a device short address field.
[0272] 1002. The controller obtains device capabilities of multiple UWB devices in the UWB device group according to the first communication frame.
[0273] Step 1002 may refer to step 903 .
[0274] 1003. The controller determines, based on the first communication frame, that the short addresses of one or more devices in the UWB device group are occupied.
[0275] Exemplarily, the first field in the first communication frame includes multiple capability list elements, each capability list element including a short address, i.e., the short address of a device in the UWB device group; when the short addresses included in one or more capability list elements in the first field are occupied, the controller determines that the short addresses of one or more devices in the UWB device group are occupied. Herein, "the short address is occupied" can be replaced with "the short address is allocated" or "the short address is repeated."
[0276] Exemplarily, the first field in the first communication frame includes multiple capability list elements, each capability list element does not include a short address (or a device short address field); the controller determines the short address of each device in the UWB device group based on the first communication frame; then, the controller determines that the short address of one or more devices in the UWB device group is occupied. An example of the controller determining the short address of each device in the UWB device group based on the first communication frame is as follows: the controller uses A+i as the short address of the device associated with the i-th capability list element in the first field; the first communication frame includes the short address A of the proxy device, and the i-th capability list element is used to indicate the device capabilities of its associated device.
[0277] It should be noted that steps 1001 to 1003 are optional, and the embodiment of the present application does not limit the implementation method of the controller determining that the short address of one or more devices in the UWB device group is occupied.
[0278] 1004. The controller sends a second communication frame to the proxy device.
[0279] Correspondingly, the proxy device receives a second communication frame from the controller. The second communication frame may be an association response command frame. The second communication frame may include a second field and a third field. The second field is used to instruct the proxy device in the UWB device group to update the device address of the proxy device, and the third field includes the updated device address of the proxy device. In other words, the second field is used to instruct the proxy device to update its own short address; the short addresses of the remaining devices in the UWB device group will be determined by the updated short address of the proxy device combined with the Sub-ID of each device. Alternatively, the second field is used to instruct the proxy device to update the device address of one or more UWB devices in the UWB device group, and the third field includes the sub-identifier of the first UWB device in the UWB device group and the updated device address of the first UWB device. The first UWB device is any one of the one or more UWB devices. It can be understood that the second field is used to indicate the format type of the third field. Exemplarily, when the value of the second field is 0, the third field includes the updated device address of the proxy device; when the value of the second field is 1, the third field includes the sub-identifier of the first UWB device within the UWB device group and the updated device address of the first UWB device. In this example, different values of the second field result in different formats of the third field, i.e., the third field contains different content. An example of the format of the content field in the second communication frame is shown in Table 16 below.
[0280] Table 16
[0281] In Table 16, the Association Status field indicates the association status, and the specific value and meaning are shown in Table 2 above; the Session Configuration field indicates the basic configuration information of the session during the current task; the Updated Address Management field is used to update the device address of one or more UWB devices in the UWB device group. As can be seen from Table 16, a new status value is added to the Association Status field of the content field of the second communication frame (assuming that the status value is 0x05). For example, when the value of the Association Status field is 0x05, the format of the content field of the second communication frame is as shown in Table 16. Among them, the Updated Short Address Management field is a newly added field, as shown in Table 17.
[0282] Table 17
[0283] The Updated Type field (ie, the second field) indicates the format type of the Updated Short Address List field (ie, the third field).
[0284] Exemplarily, when Updated Type = 0, the short addresses of all devices in the UWB device group are updated; only the short address of the proxy device is updated, and the short addresses of the remaining devices are determined by combining the updated short address of the proxy device with the Sub-ID of each device. Exemplarily, when Updated Type = 1, the short addresses of one or more devices in the UWB device group are updated, and the corresponding one or more updated short addresses are provided in the Updated Short Address List field.
[0285] The Updated Short Address List Length field indicates the number of list elements contained in the Updated Short Address List field, and is effective when Updated Type = 1. For ease of description, the value represented by the Updated Short Address List Length field is hereinafter represented by the value M (an integer greater than 0).
[0286] Examples of the format of the Updated Short Address List field shown in Table 17 can be shown in the following Tables 18 to 21.
[0287] For example, when Updated Type=0, the format of the Updated Short Address List field is as shown in Table 18 below.
[0288] Table 18
[0289] In Table 18, the short address in the Updated Short Address field is the updated address of the proxy device. As can be seen from Table 18, the Updated Short Address List field now only provides the proxy device's updated short address, A'. Accordingly, short addresses A'+1 through A'+(N-1) are assigned to other devices with Sub-IDs 1 through N-1, respectively. These "other devices" here refer to non-proxy devices within the same UWB device group as the proxy device.
[0290] For example, when Updated Type=1, the format of the Updated Short Address List field is as shown in Table 19 below.
[0291] Table 19
[0292] An example of the format of each list element shown in Table 19 is shown in Table 20 below.
[0293] Table 20
[0294] As can be seen from Tables 19 and 20, the list elements in the Updated Short Address List field provide updated short addresses for devices requiring short address updates. The Original Short Address field identifies the device requiring a short address update, while the Updated Address field contains the corresponding updated short address. For example, the short address contained in the Original Short Address field is the short address requiring an update, and the short address contained in the Original Short Address field is the corresponding updated short address.
[0295] In addition, another example of the format of each list element shown in Table 19 is shown in Table 21 below.
[0296] Table 21
[0297] The Sub-ID is the sub-identifier of the device whose short address is being updated, and the Updated Address field is the corresponding updated short address. Table 21 differs from Table 20 in that the original short address (2 bytes) of the device whose short address needs to be updated is replaced with the Sub-ID (1 byte), which reduces signaling overhead.
[0298] It should be noted that the embodiment of the present application does not limit the size of the Sub-ID. For example, the Sub-ID can also be represented by 4 bits, as shown in the following Table 22. Table 22 is an example of the format of each list element in the Updated Short Address List.
[0299] Table 22
[0300] In Table 22, the RFU field indicates a reserved field, and the meanings of other fields are the same as those in Table 21.
[0301] 1005. The proxy device updates the device addresses of one or more UWB devices in the UWB device group based on the second communication frame.
[0302] One possible implementation of step 1005 is as follows: the proxy device updates the device addresses of one or more UWB devices in the UWB device group stored in the proxy device, and transmits the updated device addresses to the corresponding devices. For example, the second communication frame carries a first updated address and a second updated address, where the first updated address is an updated short address provided for the first device in the UWB device group, and the second updated address is an updated short address provided for the second device in the UWB device group. The proxy device transmits the first updated address to the first device and the second updated address to the second device.
[0303] In an embodiment of the present application, a controller sends a second communication frame to a proxy device; based on the second communication frame, the proxy device updates the device address of one or more UWB devices in the UWB device group. This reduces signaling overhead compared to sending a communication frame for updating the short address for each device in the UWB device group that requires a short address update. Furthermore, the controller sending the second communication frame to the proxy device takes less time than sending a communication frame for updating the short address for each device in the UWB device group that requires a short address update, thus saving time overhead.
[0304] FIG11 is another interactive flow of a communication method for UWB provided in an embodiment of the present application. The method flow in FIG11 can be understood as a process in which a controller assigns short addresses to a proxy device and each device in its UWB device group. As shown in FIG11 , the method includes:
[0305] 1101. The proxy device sends a first communication frame to the controller.
[0306] Accordingly, the controller receives the first communication frame from the proxy device. Step 1101 can refer to step 902. For the description of the first communication frame, please refer to the description in Figure 9 and will not be repeated here. It should be noted that in the embodiment shown in Figure 11, the first communication frame can carry the long address of the proxy device (device long address) and the long addresses of other devices in the UWB device group where the proxy device is located. In other words, the proxy device will use a long address in the first communication frame, such as an 8-byte address (8B). In this article, it is assumed that the long address of the proxy device is B_0, and the long addresses of other devices in the UWB device group where the proxy device is located are: B_1 to B_(N-1).
[0307] Illustratively, the format of the content field of a first communication frame carrying the aforementioned long addresses B_0 to B_(N-1) is shown in Table 23 below.
[0308] Table 23
[0309] The Session ID field represents the service identifier for the current UWB service process. The UWB HRP Capability Information List Length field represents the number of list elements in the UWB HRP Capability Information List field, which is used to indicate the device capabilities of multiple devices within a UWB device group. An example of the format of the UWB HRP Capability Information List field in Table 23 is shown in Table 24 below.
[0310] Table 24
[0311] The order in which the list elements in Table 24 appear corresponds to the Sub-ID of each device in the UWB device group. For example, the order (or sequence value) of the 0th to N-1th list elements appearing from left to right in Table 24 is 0 to N-1, respectively, and these orders will also serve as the Sub-IDs of the devices corresponding to the corresponding list elements. For example, the 0th list element appearing from left to right in Table 24 corresponds to device #0, and the Sub-ID of device #0 is 0; the 1st list element appearing from left to right in Table 24 corresponds to device #1, and the Sub-ID of device #1 is 1; and by analogy, the N-1th list element appearing from left to right in Table 24 corresponds to device #N-1, and the Sub-ID of device #N-1 is N-1. An example of the format of each list element listed in Table 24 is shown in Table 25 below.
[0312] Table 25
[0313] As shown in Table 27, the Device Address field is 8 bytes, which means it uses a long address and corresponds to any of the long addresses B_0 through B_(N-1) mentioned above. The meanings of the other fields in Table 27 can be found in Table 14 and are not repeated here.
[0314] 1102. The controller obtains device capabilities of multiple UWB devices in the UWB device group according to the first communication frame.
[0315] Step 1102 may refer to step 903. Step 1101 and step 1102 are optional. In other words, the method flow in FIG11 may not include step 1101 and step 1102.
[0316] 1103. The controller sends a connection response frame to the proxy device.
[0317] Accordingly, the proxy device receives a connection response frame from the controller. Step 1003 can refer to step 904. The connection response frame carries the short address of the proxy device. Exemplarily, the content field in the connection response frame includes the short address of the proxy device. An example of the content field in the connection response frame is shown in Table 26 below.
[0318] Table 26
[0319] Among them, the Short Address field in Table 26 (assuming it is C) is the short address assigned to the proxy device. The meanings of other fields in Table 26 can refer to the meanings of the fields in Table 16. Short address C will be assigned to the device with long address B, and this device is the proxy device. In addition, short addresses C+1 to C+(N-1) will be assigned to other devices in the UWB device group where the proxy device is located. Exemplarily, short addresses C+1 to C+(N-1) will be assigned to the devices corresponding to long addresses B_1 to B_(N-1) respectively. The controller can determine the short address of each device in the UWB device group where the proxy device is located and store these short addresses. Exemplarily, the controller determines that the short address of the device corresponding to long address B_1 is C+1; determines that the short address of the device corresponding to long address B_2 is C+2; and so on.
[0320] 1104. The proxy device allocates short addresses to devices in the UWB device group based on the short address of the proxy device carried in the connection response frame.
[0321] A possible implementation of step 1104 is as follows: the proxy device assigns a short address to each non-proxy device in the UWB device group based on the short address of the proxy device carried in the connection response frame and the sub-identifier of each non-proxy device in the UWB device group. For example, the proxy device assigns the short address C+1 to the device corresponding to the long address B_1; assigns the short address C+2 to the device corresponding to the long address B_2; and so on, assigns the short address C+(N-1) to the device corresponding to the long address B_(N-1). Assigning short addresses to devices in the UWB device group may include: the proxy device transmitting the corresponding short address to each device in the UWB device group. Both the controller and the proxy device use the short address of the proxy device in combination with the sub-identifier of the non-proxy device to determine the short address of each non-proxy device in the UWB device group. Therefore, the short address of any non-proxy device is the same for the controller and the proxy device.
[0322] In an embodiment of the present application, the proxy device assigns short addresses to devices in the UWB device group based on the short address of the proxy device carried in the connection response frame; so that the proxy device and the controller can use short addresses instead of long addresses in subsequent interactions, thereby saving signaling overhead.
[0323] FIG12 is another interactive flow of a communication method for UWB provided in an embodiment of the present application. The difference between the method flow in FIG12 and the method flow in FIG11 is that in the method flow in FIG12 , the controller provides a complete short address for each device in the UWB device group, while in the method flow in FIG11 , the controller only provides a short address for the proxy device. As shown in FIG12 , the method includes:
[0324] 1201. The proxy device sends a first communication frame to the controller.
[0325] Accordingly, the controller receives the first communication frame from the proxy device. Step 1201 can refer to step 902. For a description of the first communication frame, refer to the description in FIG. 9 and are not repeated here. A field in the first communication frame can indicate the number of devices within the UWB device group. For example, the "Number of controlees within the Group" field in the first communication frame is used to indicate the number of devices within the UWB device group.
[0326] 1202. The controller obtains device capabilities of multiple UWB devices in the UWB device group according to the first communication frame.
[0327] Step 1102 may refer to step 903. Step 1201 and step 1202 are optional. In other words, the method flow in FIG12 may not include step 1201 and step 1202.
[0328] 1203. The controller sends a third communication frame to the proxy device.
[0329] Accordingly, the proxy device receives a third communication frame from the controller. The third communication frame may be an Association Response Command frame. The third communication frame may include an address list, the address list including multiple address list elements, the device address contained in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i in the UWB device group, and i is an integer greater than or equal to 0. Each address list element may contain a short address. The third communication frame is also used to indicate whether multiple devices in the UWB device group are allowed to access the controller. For specific implementation methods, please refer to the description of the connection response frame in the embodiment shown in Figure 9. In this article, an address list element can be regarded as a short address. Exemplarily, the content field of the third communication frame includes an address list, which includes N address list elements. N can be provided by the Number of controlees within the Group field in the aforementioned first communication frame. An example of the content field in the third communication frame is shown in Table 27 below.
[0330] Table 27
[0331] The Short Address List field shown in Table 27 is an address list containing N short addresses. The meanings of the other fields in Table 27 can be found in the meanings of the fields in Table 16. N can be provided by the Number of controlees within the Group field in the aforementioned first communication frame (Table 15). The Short Address List field is the above-mentioned address list, and the N short addresses contained in the Short Address List field can be multiple address list elements included in the address list. An example of the Short Address List field shown in Table 27 is shown in Table 28 below.
[0332] Table 28
[0333] Each Short Address List element in Table 28 is a short address (2 bytes), and the order in which each address list element appears is consistent with the Sub-ID of the device to which it corresponds. For example, the device address contained in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i within the UWB device group. In other words, device i within the UWB device group (with Sub-ID i) can obtain its own short address by reading the i-th element in the address list.
[0334] Exemplarily, the Sub-ID of each device within a UWB device group can be determined by the order in which the capability list elements appear in the UWB HRP Capability Information List field (i.e., the first field) in the first communication frame sent by the proxy device. In other words, the controller can determine the Sub-ID of each device within a UWB device group based on the order in which the capability list elements appear in the first field of the first communication frame. For example, the controller determines that the Sub-ID of the device corresponding to the i-th capability list element in the first field is i.
[0335] 1204. The proxy device obtains the short address of each device in the UWB device group based on the third communication frame.
[0336] The proxy device can transmit the short address of each device in the UWB device group to the corresponding device, so that each device in the UWB device group can obtain its own short address.
[0337] In an embodiment of the present application, the controller sends a third communication frame to the proxy device to inform the proxy device of the short address of each device in the UWB device group; so that the proxy device and the controller can use the short address instead of the long address in the subsequent interaction process, thereby saving signaling overhead.
[0338] The following describes the scheduling scheme for devices within a UWB device group provided by the present application in conjunction with Figure 13. Figure 13 is another interactive process of a communication method for UWB provided in an embodiment of the present application. The method flow in Figure 13 can be an independent method flow; it can also be combined with any of the method flows in Figures 9 to 12 above. In other words, the embodiment shown in Figure 13 can be an independent embodiment; it can also be combined with the aforementioned embodiments. Exemplarily, the controller and the devices within the UWB device group execute any of the method flows in Figures 9 to 12 before executing the method flow in Figure 13. As shown in Figure 13, the method includes:
[0339] 1301. The controller generates a fourth communication frame.
[0340] The fourth communication frame can be a SOR message or a POLL message, or other messages, which is not limited in this application. The fourth communication frame includes a first list, and the first list includes multiple scheduling list elements. The first scheduling list element in the first list includes a first sublist. The first sublist is used to indicate the parameter configuration information or scheduling information of multiple UWB devices in the first UWB device group (the scheduling information is used as an example below). The second scheduling list element in the first list includes a second sublist. The second sublist is used to indicate the scheduling information of multiple UWB devices in the second UWB device group. The first scheduling list element and the second scheduling list element are any two different scheduling list elements in the first list, and the first UWB device group and the second UWB device group are different. It can be understood that each scheduling list element included in the first list corresponds to a UWB device group. In this application, the scheduling list elements in the first list are introduced by taking the first scheduling list element as an example. An example of the content field of the fourth communication frame is shown in Table 29 below.
[0341] Table 29
[0342] The tiered scheduling list field contains the above-mentioned first list; the Scheduling List Length field is used to indicate the number of scheduling list elements in the tiered scheduling list field; and the Scheduling List Type field is used to indicate whether the fourth communication frame contains a tiered scheduling list field. For example, when the value of the Scheduling List Type field is equal to 6, the SchedulingList field shown in Table 3 will not appear, but the Tiered SchedulingList field will appear. The first list may be referred to as a first-tier scheduling list. The Scheduling List Type field may not be included in Table 29. An example of a Tiered SchedulingList is shown in Table 30 below.
[0343] Table 30
[0344] Table 30 contains K scheduling list elements, each of which corresponds to a UWB device group. Exemplarily, each scheduling list element contains scheduling information for each device in a UWB device group. The first scheduling list element can be any scheduling list element in Table 30.
[0345] In one possible implementation, the first scheduling list element further includes a second bitmap, the second bitmap comprising N bits. The i-th bit in the second bitmap (e.g., the i-th bit in order from left to right) corresponds to the i-th UWB device, i.e., the UWB device with sub-identifier i. When the i-th bit takes a set value, the i-th bit is used to indicate the position of the scheduling information of the i-th UWB device in the first sublist, where i is greater than or equal to 0 and i is less than or equal to N, where N is an integer greater than 0. Exemplarily, the first sublist includes one or more list elements arranged in sequence. When the i-th bit is the F-th bit in the second bitmap arranged in sequence to take a set value, the i-th bit indicates that the F-th list element in the first sublist includes the scheduling information of the i-th UWB device, where F is an integer greater than 0. The set value is 0 or 1, and is not limited here. In an implementation, indicating the position of the scheduling information of a device in a UWB device group in the first sublist using the second bitmap is applicable when the number of devices in the UWB device group is small (e.g., when the number of devices in the UWB device group is less than or equal to 16).
[0346] Illustratively, the second bitmap is included in the Bitmap indicator for group responders field in Table 31 below. An example format of the scheduling list element in Table 30 is shown in Table 31 below.
[0347] Table 31
[0348] The Address size of proxy responder field indicates the length of the Address of Proxy responder field. For example, when Address size of proxy responder = 0, the Address of Proxy responder field is 2 bytes long; when Address size of proxy responder = 1, the Address of Proxy responder field is 8 bytes long.
[0349] The bitmap indicator length field is used to indicate the length of the Bitmap indicator for group responders field. For example, when bitmap indicator length = 0, the length of the Bitmap indicator for group responders field is 1 byte; when bitmap indicator length = 1, the length of the Bitmap indicator for group responders field is 2 bytes.
[0350] Sub-Scheduling Type field: The content of the field is consistent with the Scheduling List Type field in Table 3. It is not repeated here.
[0351] The Common Configuration Control Enabled field triggers the Common Configuration Control field and the Common Configuration field. This field is valid / present only when periodic scheduling and / or RSF transmission scheduling are used. For example, the Common Configuration Control field and the Common Configuration field are valid / present only when the Sub-Scheduling Type field is 3 or 4.
[0352] Illustratively, when Common Configuration Control enabled=0, the Common Configuration Control and Common Configuration fields do not exist; when Common Configuration Control enabled=1, the Common Configuration Control and Common Configuration fields exist.
[0353] Common Configuration Control field; used to control the fields that appear in the Common Configuration field, as shown in Table 37 below.
[0354] Common Configuration field: This field represents the common fields of all devices in the UWB device group. In other words, if a field appears in the Common Configuration field, it will not appear in the list elements of the Sub-Scheduling List in Table 31, as shown in Table 39 below.
[0355] Bitmap indicator for group responders field (including the second bitmap): This field is used to determine the device corresponding to each list element in the Sub-Scheduling List field (including the first sub-list). The Sub-Scheduling List field can be called the second-layer scheduling list. Exemplarily, the order of the bits in the second bitmap is consistent with the order of the sub-identifiers of the devices in the first UWB device group; when the value of any bit is 1, it means that the list element (Sub-Scheduling List element) of the device corresponding to the Sub-ID corresponding to the order of the bit will appear in the first sub-list (Sub-Scheduling List); wherein, the order of the list element in the first sub-list is consistent with the order of the bits with a value of 1 in the Bitmap indicator for group responders field. The example format of the Sub-Scheduling List field in Table 31 is shown in Table 32 below.
[0356] Table 32
[0357] In Table 32, each list element is used to indicate scheduling information of a UWB device in the first UWB device group.
[0358] The function of the Bitmap indicator for group responders field in Table 31 is further explained by the following example: Assume that the length of the Bitmap indicator for group responders field is 1 byte.
[0359] Example 1: A bitmap indicator for group responders shown in Table 31 is shown in Table 33 below.
[0360] Table 33
[0361] As shown in Table 33, the values of the first, fifth, and sixth bits in the second bitmap are 1, which means that the scheduling information of the proxy device, responder #4, and responder #5 will appear in the Sub-Scheduling List in Table 31. In other words, the Sub-Scheduling List will contain three list elements, with the first list element being the scheduling information of the proxy device (element subscripts start at 0), the second list element being the scheduling information of responder #4, and the third list element being the scheduling information of responder #5, as shown in Table 34 below.
[0362] Table 34
[0363] Example 2: Another Bitmap indicator for group responders shown in Table 31 is shown in Table 35 below.
[0364] Table 35
[0365] As shown in Table 35, the values of the second to fifth bits in the second bitmap are 1, which means that the scheduling information of responder#1, responder#2, responder#3, and responder#4 will appear in the Sub-Scheduling List in Table 31. In other words, the Sub-Scheduling List will contain four list elements, with the first list element containing the scheduling information of responder#1, the second list element containing the scheduling information of responder#2, the third list element containing the scheduling information of responder#3, and the fourth list element containing the scheduling information of responder#4, as shown in Table 36 below.
[0366] Table 36
[0367] An example format of the aforementioned Common Configuration Control field is shown in Table 37 below.
[0368] Table 37
[0369] The Scheduling Step Presence field controls (or indicates) whether the Scheduling Step field in the Common Configuration field is effective. For example, when the value of the Scheduling Step Presence field is 1, the Scheduling Step field in the Common Configuration field is effective; when the value of the Scheduling Step Presence field is 0, the Scheduling Step field in the Common Configuration field is not effective. The Scheduling Step field indicates the scheduling time step used for scheduling. For example, it can be used to indicate the scheduling period size.
[0370] The Scheduling Repetition Presence field controls whether the Scheduling Repetition field in the Common Configuration field is effective. For example, when the Scheduling Repetition Presence field is 1, the Scheduling Repetition field in the Common Configuration field is effective. When the Scheduling Repetition Presence field is 0, the Scheduling Repetition field in the Common Configuration field is not effective. The Scheduling Repetition field indicates the number of scheduling repetitions.
[0371] The Sequence Index Presence field controls the presence of the Sequence Index field in the Common Configuration field. For example, when the Sequence Index Presence field is 1, the Sequence Index field in the Common Configuration field is present; when the Sequence Index Presence field is 0, the Sequence Index field in the Common Configuration field is absent. The Sequence Index field indicates the corresponding subscript of the sequence used for ranging.
[0372] The Number of Gaps Presence field controls the presence of the Number of Gaps field in the Common Configuration field. For example, when the value of the Number of Gaps Presence field is 1, the Number of Gaps field in the Common Configuration field is present; when the value of the Number of Gaps Presence field is 0, the Number of Gaps field in the Common Configuration field is absent. The Number of Gaps field indicates the number of time intervals used by the sequence used for ranging.
[0373] The Sequence Repetition Presence field controls the presence of the Sequence Repetition field in the Common Configuration field. For example, when the Sequence Repetition Presence field is 1, the Sequence Repetition field in the Common Configuration field is present; when the Sequence Repetition Presence field is 0, the Sequence Repetition field in the Common Configuration field is absent. The Sequence Repetition field indicates the number of repetitions of the sequence used for ranging.
[0374] RFU is a reserved field.
[0375] Assuming that the Scheduling StepPresence field and the Scheduling RepetitionPresence field in Table 39 are set to 1 and the remaining fields are set to 0, an example format of the corresponding Common Configuration field is shown in Table 38 below.
[0376] Table 38
[0377] For example, the length of the Scheduling Step / Scheduling Repetition field is less than 1 byte; when its corresponding control field Scheduling Step Presence field / Scheduling Repetition field is 0, it means that the bit corresponding to the Scheduling Step / Scheduling Repetition field is not effective, that is, the value is 0, and is not processed.
[0378] An example of the format of each Sub-Scheduling List element field in Table 32 is shown in Table 39 below.
[0379] Table 39
[0380] The Starting Slot Index field is used to indicate the starting time unit for the UWB device to transmit the UWB signal. The Receiver Address field indicates the address of the receiving device. The Sequence Index indicates the sequence index corresponding to the ranging sequence used. The Number of Gaps field indicates the number of time intervals adopted by the sequence used for ranging. The Sequence Repetition field indicates the number of repetitions of the sequence used for ranging. The Bitmap indicator for group responders field can indicate the position of the scheduling information of each device in the Sub-Scheduling List element field. In other words, the devices in the UWB device group can determine the position of their respective list elements in the Sub-Scheduling List element field based on the Bitmap indicator for group responders field; this avoids directly indicating the address (Sender Address) of each device, thereby achieving the purpose of saving signaling overhead. In addition, through the Common Configuration field, repeated indications of the same configuration can be avoided, further achieving the purpose of saving signaling overhead.
[0381] For the Receiver Address field shown in Table 39, if the device corresponding to the Receiver Addresses field is also within the current UWB device group, the aforementioned bitmap can also be used for indication. In other words, for the aforementioned example, Tables 31 and 39 are correspondingly changed to Tables 40 and 41. Another example format of the Schedule List element in Table 30 is shown in Table 40 below.
[0382] Table 40
[0383] In Table 40, the Bitmap indicator for receiver address Presence field is used to indicate whether the Bitmap indicator for receiver address field in the scheduling list element exists; the Bitmap indicator for receiver address field is used to indicate the receiving end corresponding to each list element in the Sub-Scheduling List field; the meaning of other fields is the same as that of the fields in Table 31.
[0384] As shown in Table 40, the Bitmap indicator for receiver address Presence field and the Bitmap indicator for receiver address field can be added to the format of the scheduling list element of the Tiered SchedulingList shown in Table 31, thereby indicating the receiving end corresponding to each Sub-Scheduling List element field through a bitmap. Accordingly, an example format of the Sub-Scheduling List element field in the Sub-Scheduling List field shown in Table 40 is shown in Table 41 below.
[0385] Table 41
[0386] As can be seen from Table 41, the Bitmap indicator for receiver address field is used to indicate the receiving end corresponding to each Sub-Scheduling List element field, avoiding direct indication of the Receiver Address, thereby saving signaling overhead.
[0387] In another possible implementation, the first sublist includes a second list element, the second list element is used to indicate the scheduling information of the first UWB device, the second list element includes the sub-identifier of the first UWB device in the UWB device group, and does not include the device address of the first UWB device. Each list element in the first sublist is used to indicate the scheduling information of its corresponding UWB device, and each list element includes the sub-identifier of its corresponding device in the UWB device group, and does not include the device address of its corresponding device. The sub-identifier of the device in the UWB device group can play the role of a device short address or a device long address. That is, the sub-identifier of the device in the UWB device group can replace (substitute) the device short address or the device long address of the device. In other words, the sub-identifier included in each list element serves as an identifier of the list element. The length of the sub-identifier of the device in the UWB device group is shorter than the length of the device short address. Exemplarily, the length of the sub-identifier of the device in the UWB device group is 1 byte. In this implementation, the second list element includes the sub-identifier of the first UWB device in the UWB device group, but does not include the device address of the first UWB device. Since the length of the sub-identifier is shorter than the length of the device short address, signaling overhead can be saved.
[0388] Another example format of the schedule list element in Table 30 is shown in Table 42 below.
[0389] Table 42
[0390] In Table 42, the Sub-Scheduling List Length field is used to indicate the number of list elements in the Sub-Scheduling List field, and the meanings of other fields are the same as those in Table 31. An example format of a list element in the Tiered Scheduling List field is shown in Table 43 below.
[0391] Table 43
[0392] Compared with Table 41, Table 43 compresses the size of the Sender Address field and the Receiver Address field in the original Table 41 to 1 byte each through Sub-ID, which can save scheduling signaling overhead.
[0393] 1302. The controller sends a fourth communication frame to the proxy device.
[0394] Correspondingly, the proxy device receives the fourth communication frame from the controller.
[0395] 1303. The proxy device transmits scheduling information to the first UWB device based on the fourth communication frame.
[0396] The scheduling information transmitted by the proxy device to the first UWB device is the scheduling information of the first UWB device carried in the fourth communication frame. The first UWB device is an example of a non-proxy device within the UWB device group in which the proxy device resides. Step 1303 can be understood as: the proxy device transmits the corresponding scheduling information to one or more non-proxy devices within the UWB device group based on the fourth communication frame.
[0397] Step 1303 can be replaced by: the proxy device transmits a fourth communication frame to each device in its UWB device group; and each device in the UWB device group obtains its own scheduling information based on the fourth communication frame. Steps 1302 to 1303 can be replaced by: the controller broadcasts the fourth communication frame; and each device in the UWB device group obtains its own scheduling information based on the received fourth communication frame. This embodiment of the application does not limit the manner in which each device in the UWB device group obtains its own scheduling information.
[0398] 1304. The first UWB device uses its own scheduling information to perform the measurement task.
[0399] Step 1304 can be understood as: one or more devices in the UWB device group perform the measurement task using their respective scheduling information.
[0400] The measurement task may be a sensing task, a ranging task, or a positioning task, etc. Step 1304 is optional, and the embodiment of the present application does not limit the operations performed by each device in the UWB device group using its own scheduling information.
[0401] In an embodiment of the present application, a two-layer (or hierarchical) scheduling indication method is used to indicate the scheduling information of each device in multiple UWB device groups. When the second-layer scheduling uses a bitmap to filter out the required scheduling information and indicates it to the devices in the UWB device group, it avoids directly using the device address as the device identifier, which can save signaling overhead. This is suitable for situations where there are fewer devices in the UWB device group. When the second-layer scheduling uses a sub-identifier instead of a device short address, since the length of the sub-identifier is shorter than the length of the device short address, signaling overhead can be saved.
[0402] The following describes the measurement information reporting scheme for UWB device groups provided by the present application in conjunction with Figure 14. Figure 14 is another interactive process of a communication method for UWB provided by an embodiment of the present application. The method flow in Figure 14 can be an independent method flow; it can also be combined with any of the method flows in Figures 9 to 13 above. In other words, the embodiment shown in Figure 14 can be an independent embodiment; it can also be combined with the aforementioned embodiments. Exemplarily, the controller and the devices in the UWB device group execute any of the method flows in Figures 9 to 13 before executing the method flow in Figure 14. As shown in Figure 14, the method includes:
[0403] 1401. The proxy device generates a fifth communication frame.
[0404] The fifth communication frame may be a report message. The fifth communication frame includes a first bitmap and a second list. The above-mentioned first bitmap includes N bits. The i-th bit in the above-mentioned first bitmap corresponds to the i-th UWB device, that is, the device with sub-identifier i. When the above-mentioned i-th bit takes a set value (exemplarily, the set value is 0 or 1), the above-mentioned i-th bit is used to indicate the position of the measurement report information of the i-th UWB device in the second list, the above-mentioned i is greater than or equal to 0, the above-mentioned i is less than or equal to N, and the above-mentioned N is an integer greater than 0. Exemplarily, the sub-identifiers of the N devices in the UWB device group are 0 to N-1, and the i-th bit in the first bitmap (for example, the i-th bit from left to right in the first bitmap) corresponds to the device with sub-identifier i. The measurement report information of the i-th UWB device may be the information obtained by the i-th UWB device performing the measurement task.
[0405] Assuming the set value is 1, the number of bits in the first list that are 1 is equal to the number of list elements in the second list. Exemplarily, the second list includes one or more list elements arranged in sequence. When the i-th bit is the H-th sequentially arranged bit in the first list that takes the set value, the i-th bit indicates that the H-th list element in the second list includes measurement reporting information for the i-th UWB device, where H is an integer greater than 0. An example of the first list is shown in Table 44 below.
[0406] Table 44
[0407] The values of the second, fourth, and fifth bits in the first bitmap are 1, which means that the measurement report information (content) of responder#1, responder#3, and responder#4 will appear in the second list. In other words, the second list will contain three list elements, with the first list element being the measurement report information of responder#1, the second list element being the measurement report information of responder#3, and the third list element being the measurement report information of responder#4, as shown in Table 45 below.
[0408] Table 45
[0409] An example format of each list element (Measurement Report List element field) in Table 45 is shown in Table 46 below.
[0410] Table 46
[0411] The meaning of each field in Table 46 is as follows: TX-to-RX Reply Time indicates the response time required for the responding end to respond to the initiating end in ranging, RX-to-TX Round-Trip Time indicates the signal round-trip time experienced by the initiating end in ranging, TOF indicates the air flight time of the ranging signal, AOA Azimuth indicates the azimuth of the arrival angle, where AoA stands for (angle of arrival); AOA Azimuth FOM indicates the quality factor of AOA Azimuth, where FoM stands for (Figure of merit); AOA Elevation indicates the altitude angle of arrival, and AOA Elevation FOM indicates the quality factor of the altitude angle of arrival.
[0412] As can be seen from Table 46, the list elements in the second list do not include device addresses. The first bitmap indicates the device corresponding to each list element in the second list. In other words, the first bitmap indicates the position of the measurement reporting information (or list element) of each device in the UWB device group in the second list. As can be seen, the list elements in the second list do not need to include device addresses, thus saving signaling overhead.
[0413] An example of the frame format of the fifth communication frame is shown in Table 47 below.
[0414] Table 47
[0415] The meaning of each field in Table 47 is as follows: The Payload IEs field in Table 46 may carry content related to the measurement report. An example of the format of measurement reporting information that may be included in the Payload IEs field is shown in Table 48.
[0416] Table 48
[0417] The Bitmap selector Size field is used to indicate the length of the Bitmap selector field (including the first bitmap). For example, when Bitmap selector Size = 0, the length of the Bitmap selector field is 1 byte; when Bitmap selector Size = 1, the length of the Bitmap selector field is 2 bytes.
[0418] The Bitmap selector field, which contains the first bitmap, is used to indicate the device to which each list element in the Measurement Report List field (including the second list) corresponds. For example, the order of the bits in the first bitmap corresponds to the Sub-ID of each device in the UWB device group. When the value of any bit is 1, it means that the list element of the responder corresponding to the sequence value of the bit (Sub-ID value) will appear in the Measurement Report List.
[0419] To trigger the method of indicating the device corresponding to the list element in the Measurement Report List field through the aforementioned Bitmap Selector field, one possible implementation is to set the value of the Address Size Specifier field in Table 48 to 01. For example, the meaning of the value of the Address Size Specifier field is shown in Table 49 below.
[0420] Table 49
[0421] Referring to a device based on a bitmap selector means indicating the device corresponding to each list element in the Measurement Report List field (including the second list) through the first bitmap.
[0422] Before executing step 401, the proxy device may perform the following operations: obtain (or collect) measurement reporting information from each device in the UWB device group. The proxy device may generate a fifth communication frame based on the measurement reporting information from each device in the UWB device group. The proxy device may obtain (or collect) the measurement reporting information from each device in the UWB device group in a manner similar to or identical to obtaining device capability information from each device in the UWB device group, and will not be further described here.
[0423] 1402. The proxy device sends a fifth communication frame to the controller.
[0424] Accordingly, the controller receives the fifth communication frame from the proxy device.
[0425] 1403. The controller obtains measurement reporting information of one or more devices in the UWB device group based on the fifth communication frame.
[0426] Exemplarily, the controller determines the device corresponding to each list element in the second list based on the first bitmap in the fifth communication frame. In other words, the controller determines which device's measurement reporting information is contained in each list element in the second list based on the first bitmap in the fifth communication frame. For example, refer to Table 44 (showing an example of the first bitmap) and Table 45 (showing an example of the second list); the values of the second, fourth, and fifth bits in the first bitmap are 1, which means that the measurement reporting information (content) of responder#1 device, responder#3 device, and responder#4 device will appear in the second list; the controller can determine that the second list will contain 3 list elements based on the first bitmap, and the first list element is the measurement reporting information of responder#1, the second list element is the measurement reporting information of responder#3, and the third list element is the measurement reporting information of responder#4.
[0427] In the embodiment of the present application, when the i-th bit in the first bitmap takes a set value, the i-th bit is used to indicate the position of the measurement report information of the i-th UWB device in the second list. It can be understood that the first bitmap indicates the position of the measurement report information of multiple devices within the UWB device group in the second list, which enables the combined reporting of the measurement report information of multiple devices within the UWB device group, reducing signaling overhead.
[0428] The following describes the measurement information reporting scheme for UWB device groups provided by the present application in conjunction with Figure 15. Figure 15 is another interactive process of a communication method for UWB provided by an embodiment of the present application. The method flow in Figure 15 can be an independent method flow; it can also be combined with any of the method flows in Figures 9 to 13 above. In other words, the embodiment shown in Figure 15 can be an independent embodiment; it can also be combined with the aforementioned embodiments. Exemplarily, the controller and the devices in the UWB device group execute any of the method flows in Figures 9 to 13 before executing the method flow in Figure 15. As shown in Figure 15, the method includes:
[0429] 1501. The proxy device generates a sixth communication frame.
[0430] The sixth communication frame may be a report message. The sixth communication frame may include a third list, and the third list is used to indicate the measurement report information of multiple UWB devices in the above-mentioned UWB device group. The first list element in the third list includes the sub-identifier of the first UWB device in the UWB device group. The first list element is used to indicate the measurement report information of the first UWB device. The first UWB device is any one of the above-mentioned multiple UWB devices. The first list element may not include the device address of the first UWB device. Exemplarily, each list element in the third list includes the sub-identifier of its corresponding device, but does not include the device address of its corresponding device. In this embodiment of the present application, the sub-identifier of the device in the UWB device group can play the role of the device address. That is, the sub-identifier of the device in the UWB device group can replace (replace) the device address of the device. Therefore, each list element in the third list may not include the device address of its corresponding device. In this embodiment of the present application, the Sub-ID of the UWB group device is used instead of the device address to indicate the list element in the third list. An example of the frame format of the sixth communication frame is shown in Table 50 below.
[0431] Table 50
[0432] The meanings of the fields in Table 50 are the same as those in Table 48 and are not repeated here. For the Address Size Specifier field in Table 50, the following trigger status is added, as shown in Table 51.
[0433] Table 51
[0434] The format of each list element (Measurement Report List element field) in the Measurement Report List field in Table 50 is shown in Table 52 below.
[0435] Table 52
[0436] As can be seen from Table 52, the device is indicated by the Sub-ID field (1 byte), that is, the Sub-ID is used as the device identifier, which can avoid directly indicating the Device Address (2 bytes / 8 bytes), thereby saving signaling overhead.
[0437] 1502. The proxy device sends a sixth communication frame to the controller.
[0438] Accordingly, the controller receives the sixth communication frame from the proxy device.
[0439] 1503. The controller obtains measurement reporting information of one or more devices in the UWB device group based on the sixth communication frame.
[0440] In an embodiment of the present application, the Sub-ID of the UWB grouping device is used instead of the device address to indicate the device corresponding to the list element in the third list, which can avoid directly indicating the Device Address (2 bytes / 8 bytes), thereby achieving the purpose of saving signaling overhead.
[0441] The following describes the structure of a communication device that can implement the communication method provided in the embodiment of the present application in conjunction with the accompanying drawings. The following only briefly describes the communication device. For details on the implementation of the solution, please refer to the description of the method embodiment above, which will not be repeated below.
[0442] Figure 16 is a schematic diagram of the structure of a communication device 1600 provided in an embodiment of the present application. The communication device 1600 can implement the functions or steps implemented by the proxy device in each of the above-mentioned method embodiments, or can also implement the functions or steps implemented by the controller in each of the above-mentioned method embodiments. The communication device may include a processing module 1610 and a transceiver module 1620. In one possible implementation, it may also include a storage unit, which can be used to store instructions (code or program) and / or data. The processing module 1610 and the transceiver module 1620 can be coupled to the storage unit. For example, the processing module 1610 can read the instructions (code or program) and / or data in the storage unit to implement the corresponding method. The above-mentioned units can be provided independently or partially or fully integrated. For example, the transceiver module 1620 may include a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The entity corresponding to the transceiver module 1620 can be a transceiver or a communication interface.
[0443] In some possible implementations, communication device 1600 can implement the corresponding behaviors and functions of the controller in the above-described method embodiments. For example, communication device 1600 can be a proxy device in a UWB device group, or a component (e.g., a chip or circuit) used in a proxy device. Transceiver module 1620 can, for example, be used to perform all receiving or transmitting operations performed by the proxy device in the embodiments of Figures 9 to 15. Processing module 1610 is used to perform all operations performed by the proxy device in the embodiments of Figures 9 to 15 except for the transmitting and receiving operations.
[0444] In some possible implementations, the communication device 1600 can implement the corresponding behaviors and functions of the controller in the above-described method embodiments. For example, the communication device 1600 can be a controller, or a component (e.g., a chip or circuit) used in the controller. The transceiver module 1620 can, for example, be used to perform all receiving or sending operations performed by the controller in the embodiments of Figures 9 to 15. The processing module 1610 is used to perform all operations performed by the controller in the embodiments of Figures 9 to 15 except for the sending and receiving operations.
[0445] Figure 17 is a schematic diagram of the structure of another communication device 170 provided in an embodiment of the present application. The communication device in Figure 17 can be the above-mentioned proxy device or the above-mentioned controller.
[0446] As shown in FIG. 17 , the communication device 170 includes at least one processor 1710 and a transceiver 1720 .
[0447] In some embodiments of the present application, the processor 1710 and the transceiver 1720 may be configured to execute functions or operations performed by a proxy device. For example, the transceiver 1720 is configured to execute all receiving or sending operations performed by the proxy device in the embodiments of Figures 9 to 15. For example, the processor 1710 is configured to execute all operations performed by the proxy device in the embodiments of Figures 9 to 15 except for the sending and receiving operations.
[0448] In some embodiments of the present application, the processor 1710 and the transceiver 1720 may be configured to execute functions or operations performed by a controller. The transceiver 1720 may be configured to, for example, execute all receiving or transmitting operations performed by the controller in the embodiments of Figures 9 to 15. The processor 1710 may be configured to, for example, execute all operations performed by the controller in the embodiments of Figures 9 to 15 except for the transmitting and receiving operations.
[0449] Transceiver 1720 is used to communicate with other devices / apparatuses via a transmission medium. Processor 1710 utilizes transceiver 1720 to transmit and receive data and / or signaling, and is used to implement the methods described in the above method embodiments. Processor 1710 can implement the functions of processing module 1610, and transceiver 1720 can implement the functions of transceiver module 1620.
[0450] Optionally, transceiver 1720 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily used for converting baseband signals into radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, display, and keyboard, are primarily used for receiving user input and outputting data to the user.
[0451] Optionally, the communication device 170 may further include at least one memory 1730 for storing program instructions and / or data. The memory 1730 is coupled to the processor 1710. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 1710 may operate in conjunction with the memory 1730. The processor 1710 may execute program instructions stored in the memory 1730. At least one of the at least one memory may be included in the processor.
[0452] Processor 1710 can read software programs stored in memory 1730, interpret and execute instructions within the software programs, and process data within the software programs. When data needs to be transmitted wirelessly, processor 1710 performs baseband processing on the data to be transmitted and outputs the baseband signal to the RF circuit. The RF circuit then performs RF processing on the baseband signal and transmits it via an antenna in the form of electromagnetic waves. When data is transmitted to the communication device, the RF circuit receives the RF signal via the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to processor 1710. Processor 1710 converts the baseband signal into data and processes the data.
[0453] In another implementation, the above-mentioned RF circuit and antenna can be set independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna can be arranged remotely from the communication device.
[0454] The specific connection medium between the transceiver 1720, processor 1710, and memory 1730 is not limited in the embodiments of the present application. In Figure 17, the memory 1730, processor 1710, and transceiver 1720 are connected via a bus 1740. The bus is represented by a bold line in Figure 17. The connection methods between other components are merely illustrative and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 17 only uses a single bold line, but this does not mean that there is only one bus or only one type of bus.
[0455] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.
[0456] Figure 18 is a schematic diagram of the structure of another communication device 180 provided in an embodiment of the present application. As shown in Figure 18, the communication device shown in Figure 18 includes a logic circuit 1801 and an interface 1802. The processing module 1610 in Figure 16 can be implemented with a logic circuit 1801, and the transceiver module 1620 in Figure 16 can be implemented with an interface 1802. Among them, the logic circuit 1801 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 1802 can be a communication interface, an input and output interface, etc. In the embodiment of the present application, the logic circuit and the interface can also be coupled to each other. The embodiment of the present application does not limit the specific connection method of the logic circuit and the interface.
[0457] In some embodiments of the present application, the logic circuit and interface may be used to execute the functions or operations performed by the aforementioned proxy device.
[0458] In some embodiments of the present application, the logic circuit and interface may be used to execute the functions or operations performed by the aforementioned controller.
[0459] The present application also provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed on a computer, the computer executes the method of the above embodiment.
[0460] The present application also provides a computer program product, which includes instructions or a computer program. When the instructions or the computer program are run on a computer, the method in the above embodiment is executed.
[0461] The present application also provides a communication system, including the above-mentioned controller and the above-mentioned agent device.
[0462] The present application also provides a chip, which includes: a communication interface and a processor; the communication interface is used for sending and receiving signals of the above-mentioned chip; the processor is used to execute computer program instructions so that the communication device including the above-mentioned chip executes the method in the above-mentioned embodiment.
[0463] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
[0464] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
Claims
1. A communication method for ultra-wideband UWB, characterized in that: include: Generate a first communication frame, the first communication frame comprising a first field, the first field being used to indicate device capabilities of a plurality of UWB devices in the UWB device group; The first communication frame is sent.
2. The method according to claim 1, characterized in that: After sending the first communication frame, the method further includes: receiving a second communication frame, wherein the second communication frame includes a second field and a third field; The second field is used to instruct the proxy device in the UWB device group to update the device address of the proxy device, and the third field includes the updated device address of the proxy device; Alternatively, the second field is used to instruct the proxy device in the UWB device group to update the device address of one or more UWB devices in the UWB device group, and the third field includes a sub-identifier of the first UWB device in the UWB device group and the updated device address of the first UWB device, and the first UWB device is any one of the one or more UWB devices.
3. The method according to claim 1, characterized in that: After sending the first communication frame, the method further includes: A third communication frame is received, wherein the third communication frame includes an address list, wherein the address list includes multiple address list elements, wherein the device address contained in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i in the UWB device group, and i is an integer greater than or equal to 0.
4. The method according to any one of claims 1 to 3, characterized in that: After sending the first communication frame, the method further includes: A fourth communication frame is received, the fourth communication frame comprising a first list, the first list comprising a plurality of scheduling list elements, the first scheduling list element in the first list comprising a first sub-list, the first sub-list being used to indicate parameter configuration information or scheduling information of a plurality of UWB devices in the UWB device group.
5. The method according to any one of claims 1 to 4, characterized in that: After sending the first communication frame, the method further includes: A fifth communication frame is sent, the fifth communication frame including a first bitmap and a second list, the first bitmap including N bits, the i-th bit in the first bitmap corresponds to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement reporting information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
6. The method according to any one of claims 1 to 4, characterized in that: After sending the first communication frame, the method further includes: A sixth communication frame is sent, the sixth communication frame including a third list, the third list is used to indicate measurement reporting information of multiple UWB devices in the UWB device group, a first list element in the third list includes a sub-identifier of a first UWB device in the UWB device group, the first list element is used to indicate measurement reporting information of a first UWB device, and the first UWB device is any one of the multiple UWB devices.
7. The method according to any one of claims 1 to 6, characterized in that: The first field includes a plurality of capability list elements, and a capability list element in the first field is used to indicate a UWB device in the plurality of UWB devices; before sending the first communication frame, the method further includes: A first address is assigned to a first UWB device, the first address being obtained by a device address of a proxy device in the UWB device group and a first sub-identifier of the first UWB device in the UWB device group, the first UWB device being any one of the plurality of UWB devices.
8. A communication method for ultra-wideband (UWB), characterized in that: include: receiving a first communication frame, the first communication frame comprising a first field, the first field being used to indicate device capabilities of a plurality of UWB devices in a UWB device group; The device capabilities of the plurality of UWB devices in the UWB device group are obtained according to the first communication frame.
9. The method according to claim 8, characterized in that After receiving the first communication frame, the method further includes: Sending a second communication frame, wherein the second communication frame includes a second field and a third field; The second field is used to instruct the proxy device in the UWB device group to update the device address of the proxy device, and the third field includes the updated device address of the proxy device; Alternatively, the second field is used to instruct the proxy device in the UWB device group to update the device address of one or more UWB devices in the UWB device group, and the third field includes a sub-identifier of the first UWB device in the UWB device group and the updated device address of the first UWB device, and the first UWB device is any one of the one or more UWB devices.
10. The method according to claim 8, characterized in that After receiving the first communication frame, the method further includes: A third communication frame is sent, wherein the third communication frame includes an address list, wherein the address list includes multiple address list elements, wherein the device address contained in the i-th address list element in the address list is the device address of the UWB device with sub-identifier i in the UWB device group, and i is an integer greater than or equal to 0.
11. The method according to any one of claims 8 to 10, characterized in that: After receiving the first communication frame, the method further includes: A fourth communication frame is sent, wherein the fourth communication frame includes a first list, the first list includes multiple scheduling list elements, the first scheduling list element in the first list includes a first sub-list, and the first sub-list is used to indicate parameter configuration information or scheduling information of multiple UWB devices in the UWB device group.
12. The method according to any one of claims 8 to 11, characterized in that After receiving the first communication frame, the method further includes: A fifth communication frame is received, the fifth communication frame including a first bitmap and a second list, the first bitmap including N bits, the i-th bit in the first bitmap corresponds to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the measurement reporting information of the i-th UWB device in the second list, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
13. The method according to any one of claims 8 to 11, characterized in that After receiving the first communication frame, the method further includes: A sixth communication frame is received, the sixth communication frame comprising a third list, the third list being used to indicate measurement reporting information of multiple UWB devices within the UWB device group, a first list element in the third list comprising a sub-identifier of a first UWB device within the UWB device group, the first list element being used to indicate measurement reporting information of a first UWB device, and the first UWB device being any one of the multiple UWB devices.
14. The method according to any one of claims 1 to 13, characterized in that: The first communication frame further includes a fourth field, and the fourth field is used to indicate that the first communication frame comes from a proxy device in the UWB device group.
15. The method according to any one of claims 1 to 14, characterized in that The first field is used to indicate a first device capability, where the first device capability is a device capability possessed by each UWB device in the UWB device group; Alternatively, the first field includes a plurality of capability list elements, and a capability list element in the first field is used to indicate a device capability of a UWB device among the plurality of UWB devices.
16. The method according to claim 15, characterized in that The first communication frame also includes a fifth field; When the value of the fifth field is the first value, the first field is used to indicate the first device capability; When the value of the fifth field is the second value, the first field includes the multiple capability list elements.
17. The method according to claim 15 or 16, characterized in that The first field includes the plurality of capability list elements, and the plurality of capability list elements have a mapping relationship with the device addresses of the plurality of UWB devices.
18. The method according to claim 17, characterized in that The i-th capability list element in the first field is used to indicate the device capability of the i-th UWB device, the order of the i-th capability list element in the multiple capability list elements and the device address of the proxy device in the UWB device group are used to determine the device address of the i-th UWB device, and i is an integer greater than or equal to 0.
19. The method according to claim 4 or 10, characterized in that: The first scheduling list element also includes a second bitmap, the second bitmap includes N bits, the i-th bit in the second bitmap corresponds to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the parameter configuration information or scheduling information of the i-th UWB device in the first sublist, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
20. The method according to claim 19, characterized in that The first sub-list includes one or more list elements arranged in order. When the i-th bit is the F-th bit in the second bitmap arranged in order and taking the set value, the i-th bit indicates that the F-th list element in the first sub-list includes parameter configuration information or scheduling information of the i-th UWB device, and F is an integer greater than 0.
21. The method according to claim 4 or 10, characterized in that: The first sub-list includes a second list element, where the second list element is used to indicate parameter configuration information or scheduling information of the first UWB device, and the second list element includes a sub-identifier of the first UWB device in the UWB device group.
22. A communication method for ultra-wideband (UWB), characterized in that: include: Generate a fourth communication frame, the fourth communication frame comprising a first list, the first list comprising a plurality of scheduling list elements, a first scheduling list element in the first list comprising a first sub-list, the first sub-list being used to indicate parameter configuration information or scheduling information of a plurality of UWB devices in the UWB device group; The fourth communication frame is sent.
23. A communication method for ultra-wideband (UWB), characterized in that: include: receiving a fourth communication frame, the fourth communication frame comprising a first list, the first list comprising a plurality of scheduling list elements, a first scheduling list element in the first list comprising a first sub-list, the first sub-list being used to indicate parameter configuration information or scheduling information of a plurality of UWB devices in the UWB device group; Based on the fourth communication frame, parameter configuration information or scheduling information of a plurality of UWB devices in the UWB device group is obtained.
24. The method according to claim 22 or 23, characterized in that The first scheduling list element also includes a second bitmap, the second bitmap includes N bits, the i-th bit in the second bitmap corresponds to the i-th UWB device, when the i-th bit takes a set value, the i-th bit is used to indicate the position of the parameter configuration information or scheduling information of the i-th UWB device in the first sublist, the i is greater than or equal to 0, the i is less than or equal to N, the N is an integer greater than 0, and the i-th UWB device is a device with a sub-identifier i in the UWB device group.
25. The method according to claim 24, characterized in that The first sub-list includes one or more list elements arranged in order. When the i-th bit is the F-th bit in the second bitmap arranged in order and taking the set value, the i-th bit indicates that the F-th list element in the first sub-list includes parameter configuration information or scheduling information of the i-th UWB device, and F is an integer greater than 0.
26. The method according to claim 22 or 23, characterized in that The first sub-list includes a second list element, where the second list element is used to indicate parameter configuration information or scheduling information of the first UWB device, and the second list element includes a sub-identifier of the first UWB device in the UWB device group.
27. A communication device, characterized in that: The method comprises a module or a unit for implementing the method according to any one of claims 1 to 26.
28. A communication device, characterized in that: The device comprises a processor, the processor is coupled to a memory, the memory stores computer program instructions, and the processor is used to execute the computer program instructions so that the communication device performs the method according to any one of claims 1 to 26.
29. A chip, characterized in that: include: A communication interface, used for sending and receiving signals of the chip; as well as A processor, configured to execute computer program instructions so that a communication device including the chip executes the method according to any one of claims 1 to 26.
30. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed, the computer is enabled to perform the method according to any one of claims 1 to 26.
31. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 26.
Citation Information
Patent Citations
Multi-node cooperation distance measuring method in ultra wide band wireless sensor network
CN103037416A
Ranging-specific mac service and pib attributes for IEEE 802.15.4z
CN113302517A
Wireless communication method and device, communication equipment and storage medium
CN114342486A
Method of manufacturing plastic-based article, injection mold for manufacturing plastic-based article, injection mold set for manufacturing plastic-based article, and plastic-based article
KR102617428B1
Multi-link communication
US20210014776A1