Architecture and method for controlling exchange of ranging results

Abstract

A method and apparatus of a first network entity in a wireless communication system supporting ranging capability are provided, the method and apparatus including generating a medium access control (MAC) common part sublayer data request (MCPS-DATA.request) primitive including a ranging enable indicator and a ranging request measurement and control IE (RRMC IE) with a reply time request, transmitting first MAC data including the RRMC IE to a second network entity, receiving second MAC data including a ranging reply time instantaneous IE (RRTI IE) and the RRMC IE from the second network entity, and identifying a local value of a receive ranging counter (RxRangingCounter).

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to ranging operations in wireless communication systems. In particular, architectures and methods of controlling exchange of ranging results in wireless communication networks are presented. BACKGROUND

[0002] Peer Aware Communications (PAC) networks are fully distributed communication networks that allow for direct communication between PAC Devices (PDs). PAC networks can employ several topologies such as mesh, star, etc. to support interactions between PDs for various services. SUMMARY

[0003] [TECHNICAL PROBLEM]

[0004] Embodiments of the present disclosure provide architectures and methods of controlling exchange of ranging results in wireless communication networks.

[0005] [TECHNICAL SOLUTION]

[0006] In one embodiment, a first network entity in a wireless communication system supporting ranging capability is provided. The first network entity includes a processor configured to generate a medium access control (MAC) common part sublayer data request (MCPS-DATA.request) primitive including a ranging enable indicator and a ranging request measurement and control IE (RRMC IE) with a response time request. The first network entity further includes a transceiver operably connected to the processor, the transceiver configured to transmit, to a second network entity, first MAC data including the RRMC IE, receive, from the second network entity, second MAC data including a ranging response time instantaneous IE (RRTI IE) and the RRMC IE. The processor of the first network entity is further configured to identify a local value of a receive ranging counter (RxRangingCounter). BRIEF DESCRIPTION OF DRAWINGS

[0007] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings in which like reference numerals represent like components:

[0008] FIG. 1 An exemplary wireless network is shown in accordance with an embodiment of the present disclosure;

[0009] FIG. 2 An exemplary gNB is shown in accordance with an embodiment of the present disclosure;

[0010] FIG. 3 An exemplary UE is shown in accordance with an embodiment of the present disclosure;

[0011] FIG. 4A shows a high-level diagram of an orthogonal frequency division multiple access transmit path in accordance with an embodiment of the present disclosure;

[0012] FIG. 4B illustrates a high level diagram of an orthogonal frequency division multiple access receive path, according to embodiments of the disclosure;

[0013] FIG. 5 An exemplary electronic device is shown, according to embodiments of the disclosure;

[0014] FIG. 6 An exemplary many-to-many scenario is shown, according to embodiments of the disclosure;

[0015] FIG. 7 An exemplary one-sided two-way ranging is shown, according to embodiments of the disclosure;

[0016] FIG. 8 An exemplary two-sided two-way ranging with three messages is shown, according to embodiments of the disclosure;

[0017] FIG. 9 An exemplary ranging request response time IE content field format is shown, according to embodiments of the disclosure;

[0018] FIG. 10 An exemplary destination list content field format is shown, according to embodiments of the disclosure;

[0019] FIG. 11 An exemplary ranging flight time IE content field format is shown, according to embodiments of the disclosure;

[0020] FIG. 12 An exemplary ranging round trip measurement IE content field format is shown, according to embodiments of the disclosure;

[0021] FIG. 13 An exemplary ranging response time instantaneous IE content field format is shown, according to embodiments of the disclosure;

[0022] FIG. 14 An exemplary ranging response time delay IE content field format is shown, according to embodiments of the disclosure;

[0023] FIG. 15 An exemplary ranging angle of arrival delay IE content field format is shown, according to embodiments of the disclosure;

[0024] FIG. 16 An exemplary ranging control one-sided TWR IE content field format is shown, according to embodiments of the disclosure;

[0025] FIG. 17 An exemplary ranging control two-sided TWR IE content field format is shown, according to embodiments of the disclosure;

[0026] FIG. 18An exemplary time structure of a ranging cycle is shown in accordance with embodiments of the present disclosure;

[0027] FIG. 19 An exemplary ranging device nomenclature: Controller and Controller is shown in accordance with embodiments of the present disclosure;

[0028] FIG. 20 An exemplary ranging cycle structure is shown in accordance with embodiments of the present disclosure;

[0029] FIG. 21 An exemplary content field of a Ranging Schedule (RS) IE is shown in accordance with embodiments of the present disclosure;

[0030] FIG. 22 An exemplary row of a RS table is shown in accordance with embodiments of the present disclosure;

[0031] FIG. 23 An exemplary RTR IE content field is shown in accordance with embodiments of the present disclosure;

[0032] FIG. 24 An exemplary row of a Provider List is shown in accordance with embodiments of the present disclosure;

[0033] FIG. 25 An exemplary RAR IE content field is shown in accordance with embodiments of the present disclosure;

[0034] FIG. 26 An exemplary row of a Provider List is shown in accordance with embodiments of the present disclosure;

[0035] FIG. 27 Another exemplary RAR IE content field is shown in accordance with embodiments of the present disclosure;

[0036] FIG. 28 Another exemplary row of a Provider List is shown in accordance with embodiments of the present disclosure;

[0037] FIG. 29 An exemplary RRR IE content field is shown in accordance with embodiments of the present disclosure;

[0038] FIG. 30 Another exemplary row of a Provider List is shown in accordance with embodiments of the present disclosure;

[0039] FIG. 31 Another exemplary RRR IE content field is shown in accordance with embodiments of the present disclosure;

[0040] FIG. 32 Another exemplary row of a Provider List is shown in accordance with embodiments of the present disclosure;

[0041] FIG. 33A flow diagram of a method for scheduled-based ranging according to embodiments of the disclosure is shown;

[0042] FIG. 34 An exemplary message sequence chart for multicast ranging according to embodiments of the disclosure is shown, where the ranging controller is the initiator and the requester;

[0043] FIG. 35 An exemplary RRR IE content field format according to embodiments of the disclosure is shown;

[0044] FIG. 36 An exemplary row / element of a provider list according to embodiments of the disclosure is shown;

[0045] FIG. 37 Another exemplary row / element of a provider list according to embodiments of the disclosure is shown;

[0046] FIG. 38 An exemplary RR IE content field format according to embodiments of the disclosure is shown;

[0047] FIG. 39 An exemplary row / element of a RR table according to embodiments of the disclosure is shown;

[0048] FIG. 40 Another exemplary row / element of a RR table according to embodiments of the disclosure is shown;

[0049] FIG. 41 An exemplary message sequence chart for one-to-many SS-TWR with RRR and RR IE according to embodiments of the disclosure is shown;

[0050] FIG. 42 An exemplary message sequence chart for one-to-many DS-TWR with RRR and RR IE according to embodiments of the disclosure is shown;

[0051] FIG. 43 An exemplary message sequence chart for one-to-many DS-TWR with RRR and RR IE according to embodiments of the disclosure is shown, where the initiator requests ToF;

[0052] FIG. 44 An exemplary message sequence chart for one-to-many DS-TWR with RRR and RR IE according to embodiments of the disclosure is shown, where the initiator requests response time and round trip time;

[0053] FIG. 45 An exemplary RRRC IE content field format according to embodiments of the disclosure is shown;

[0054] FIG. 46 An exemplary row / element of a RRRC table according to embodiments of the disclosure is shown;

[0055] FIG. 47 An exemplary row / element of a RRRC table is shown in accordance with an embodiment of the present disclosure;

[0056] FIG. 48 An exemplary simplified row / element of a RRRC table is shown in accordance with an embodiment of the present disclosure;

[0057] FIG. 49 An exemplary revised ranging result request IE (RRR IE) with one control octet is shown in accordance with an embodiment of the present disclosure;

[0058] FIG. 50 An exemplary element / row in a RRR table is shown in accordance with an embodiment of the present disclosure;

[0059] FIG. 51 An exemplary RR table for a device sending a RRR IE is shown in accordance with an embodiment of the present disclosure;

[0060] FIG. 52 Another exemplary revised ranging result request IE (RRR IE) with one control octet is shown in accordance with an embodiment of the present disclosure;

[0061] FIG. 53 An exemplary revised ranging result request IE (RRR IE) with a ranging control bit is shown in accordance with an embodiment of the present disclosure;

[0062] FIG. 54 An exemplary revised ranging report IE (RR IE) with one control octet is shown in accordance with an embodiment of the present disclosure;

[0063] FIG. 55 An exemplary element / row in a RR table is shown in accordance with an embodiment of the present disclosure;

[0064] FIG. 56 Another exemplary revised ranging report IE (RR IE) with one control octet is shown in accordance with an embodiment of the present disclosure;

[0065] FIG. 57 An exemplary revised ranging request and report control (RRRC) IE with one control octet is shown in accordance with an embodiment of the present disclosure;

[0066] FIG. 58 An exemplary RRMC IE (or RRR IE) with a ranging control information field is shown in accordance with an embodiment of the present disclosure;

[0067] FIG. 59An exemplary message sequence chart for one-to-many SS-TWR is shown, according to embodiments of the disclosure;

[0068] FIG. 60 An exemplary message sequence chart for one-to-many DS-TWR is shown, according to embodiments of the disclosure: no ranging result request from initiator;

[0069] FIG. 61 An exemplary message sequence chart for one-to-many DS-TWR is shown, according to embodiments of the disclosure: no ranging result request from initiator with delay pattern;

[0070] FIG. 62 An exemplary message sequence chart for one-to-many DS-TWR is shown, according to embodiments of the disclosure: request for first reply time and second round trip time from initiator;

[0071] FIG. 63 An exemplary message sequence chart for one-to-many DS-TWR is shown, according to embodiments of the disclosure: ranging result request from initiator;

[0072] FIG. 64 An exemplary ranging reply time instant IE content field format is shown, according to embodiments of the disclosure;

[0073] FIG. 65 An exemplary RRTI table row element format is shown, according to embodiments of the disclosure;

[0074] FIG. 66 An exemplary message sequence chart for SS-TWR with delayed reply time result is shown, according to embodiments of the disclosure;

[0075] FIG. 67 An exemplary message sequence chart for SS-TWR with embedded reply time is shown, according to embodiments of the disclosure;

[0076] FIG. 68 An exemplary message sequence chart for DS-TWR with delayed reply time result is shown, according to embodiments of the disclosure;

[0077] FIG. 69 An exemplary message sequence chart for DS-TWR with three messages is shown, according to embodiments of the disclosure;

[0078] FIG. 70 An exemplary message sequence chart for one-to-many SS-TWR is shown, according to embodiments of the disclosure;

[0079] FIG. 71An exemplary message sequence chart for one-to-many DS-TWR is shown according to embodiments of the present disclosure: no request for ranging results from the initiator;

[0080] FIG. 72 An exemplary message sequence chart for one-to-many DS-TWR is shown according to embodiments of the present disclosure: no request for ranging results from the initiator;

[0081] FIG. 73 An exemplary message sequence chart for one-to-many DS-TWR is shown according to embodiments of the present disclosure: no request for ranging results from the initiator;

[0082] FIG. 74 An exemplary message sequence chart for M2M SS-TWR is shown according to embodiments of the present disclosure;

[0083] FIG. 75 An exemplary message sequence chart for M2M DS-TWR is shown according to embodiments of the present disclosure; and

[0084] FIG. 76 A flowchart of a method for secure ranging operation is shown according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0085] [BEST MODE]

[0086] In one embodiment, a first network entity in a wireless communication system supporting ranging capability is provided. The first network entity includes a processor configured to generate a media access control (MAC) common part sublayer data request (MCPS-DATA.request) primitive including a ranging enable indicator and a ranging request measurement and control IE (RRMC IE) having a response time request. The first network entity also includes a transceiver operably connected to the processor, the transceiver configured to transmit first MAC data including the RRMC IE to a second network entity, receive second MAC data including a ranging response time instant IE (RRTI IE) and the RRMC IE from the second network entity. The processor of the first network entity is further configured to identify a local value of a receive ranging counter (RxRangingCounter).

[0087] In another embodiment, a second network entity in a ranging capability enabled wireless communication system is provided. The second network entity includes a transceiver configured to receive first MAC data from a first network entity, the first MAC data including a ranging enable indicator and a ranging request measurement and control IE (RRMC IE) with a response time request, wherein the RRMC IE is generated by the first network entity in a media access control (MAC) common part sublayer data request (MCPS-DATA.request); and send second MAC data including a ranging response time instantaneous IE (RRTI IE) and the RRMC IE to the first network entity. The second network entity also includes a processor operably connected to the transceiver, the processor configured to identify a local value of a receive ranging counter (RxRangingCounter).

[0088] In yet another embodiment, a method of a first network entity in a ranging capability enabled wireless communication system is provided. The method includes generating a media access control (MAC) common part sublayer data request (MCPS-DATA.request) primitive including a ranging enable indicator and a ranging request measurement and control IE (RRMC IE) with a response time request; sending first MAC data including the RRMC IE to a second network entity; receiving second MAC data including a ranging response time instantaneous IE (RRTI IE) and the RRMC IE from the second network entity; and identifying a local value of a receive ranging counter (RxRangingCounter).

[0089] Other technical features can be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0090] Before undertaking a detailed description of embodiments, a thorough overview of certain word and phrase usage is beneficial. The term “coupled” and variations thereof, means any direct or indirect communication between two or more elements, whether electrically, mechanically, or otherwise, regardless of whether those elements are physically in contact with one another. The terms “transmit,” “receive,” and “communicate,” and variations thereof, include direct and indirect communication. The terms “include,” “comprise,” and “comprising,” and variations thereof, mean non- limiting inclusion. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and variations thereof, means includes, is included in, interconnects with, contains, is contained within, connects to or with, couples to or with, is communicable with, cooperates with, interleafs with, is proximate to, is bound to or with, has a property of, has relations with, and / or the like. The term “controller” means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items can be utilized and only one item from the list can be needed. For example, “at least one of A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0091] Furthermore, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof, which are adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links, as well as a medium that has a transitory signal, but a non-transitory computer readable medium includes a medium that can store data for a period of time (e.g., a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory). The term “user equipment” (UE) refers to any device that can send and receive data, such as a mobile phone, a personal computer, a wireless-enabled enabled PDA, a gaming console, a media player, a navigation device, an e-book reader, or any other device that can send and receive data.

[0092] Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art will understand that such definitions apply to not only the

[0093] [INVENTION MODE]

[0094] The following discussion FIGS. 1-76 The principles of the disclosure described in this patent document can be implemented in any of a variety of systems or devices. One of skill in the art will understand that the principles of the disclosure can be implemented in any suitably arranged system or device.

[0095] The following documents and standards are hereby incorporated by reference into this disclosure as if fully set forth herein: IEEE Standard for Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Peer Aware Communications, IEEE Std 802.15.8, 2017; and IEEE Standard for Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area Networks (WPANs), IEEE Std 802.15.4, 2105.

[0096] Aspects, features and advantages of the present disclosure will become apparent to those of ordinary skill in the art from the following detailed description, taken in conjunction with the accompanying drawings. The present disclosure can also have other and different embodiments, and modifications and substitutions can be made in various obvious respects, all without departing from the spirit and scope of the present disclosure. Accordingly, the drawings and descriptions are to be regarded as illustrative in nature, and not as restrictive. The disclosure is shown by way of example, and not by way of limitation, in the figures of the accompanying drawings.

[0097] The following FIG. 1 FIG. 4B depicts various embodiments implemented in wireless communication systems and use orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. FIGS. 1-3 The description of the drawings does not imply any physical or architectural limitation to the manner in which different embodiments can be implemented. Different embodiments of the present disclosure can be implemented in any suitably-arranged communication system.

[0098] FIG. 1An example wireless network according to embodiments of the present disclosure is illustrated. FIG. 1 The illustrated embodiment of the wireless network is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present disclosure.

[0099] As FIG. 1 illustrated, the wireless network includes a gNB 101 (e.g., base station (BS)), a gNB 102, and a gNB 103. The gNB 101 communicates with the gNB 102 and the gNB 103. The gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0100] The gNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipment devices (UEs) within a coverage area 120 of the gNB 102. The first plurality of UEs includes a UE 111, which can be located in a small business (SB); a UE 112, which can be located in an enterprise (E); a UE 113, which can be located in a WiFi hotspot (HS); a UE 114, which can be located in a first residence (R); a UE 115, which can be located in a second residence (R); and a UE 116, which can be a mobile device (M), such as a cell phone, a wireless laptop computer, a wireless PDA, or the like. The gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the gNB 103. The second plurality of UEs includes the UE 115 and the UE 116. In some embodiments, one or more of the gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G / LTE / LTE-A / WiMAX / WiFi, or other wireless communication techniques.

[0101] Depending on the network type, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations can provide wireless access to a plurality of UEs 115 using one or more wireless communication protocols, such as 5G 3GPP New Radio Interface / Access (NR), Long-Term Evolution (LTE), LTE-Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms "BS" and "TRP" are used interchangeably herein to refer to a network infrastructure component that provides wireless access to remote terminals. Further, depending on the network type, the term "user equipment" or "UE" can refer to any component, such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receive point," or "user device." For the sake of convenience, the terms "user equipment" and "UE" are used interchangeably herein to refer to a remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or typically thought of as a fixed device (such as a desktop computer or vending machine).

[0102] Dotted lines show the approximate extents of the coverage areas 120 and 125 ascertained for purposes of illustration and explanation only. It is clearly understood that the coverage areas associated with gNBs, such as the coverage areas 120 and 125, can have other shapes, including irregular shapes, depending upon the configuration of gNBs and variations in the radio environment associated with natural and man-made obstructions.

[0103] As described in more detail below, one or more of the UEs 111-116 include circuitry, programming or a combination thereof for CSI reporting in an advanced wireless communication system. In certain embodiments, one or more of the gNBs 101-103 include circuitry, programming or a combination thereof for CSI acquisition in an advanced wireless communication system.

[0104] Although FIG. 1 One example of a wireless network is illustrated, but FIG. 1Various changes can be made. For example, the wireless network can include any number of gNBs and any number of UEs arranged suitably. Furthermore, gNB 101 can communicate directly with any number of UEs and provide those UEs access to the network 130 for wireless broadband Internet access. Similarly, each of gNBs 102 and 103 can communicate directly with the network 130 and provide UEs access to the network 130 for wireless broadband Internet access. Furthermore, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0105] FIG. 2 An exemplary gNB 102 according to embodiments of the present disclosure is illustrated. FIG. 2 The illustrated embodiment of the gNB 102 is for illustration only, FIG. 1 The gNBs 101 and 103 can have the same or similar configuration. However, gNBs have a variety of configurations and FIG. 2 The scope of the present disclosure is not limited to any particular implementation of a gNB.

[0106] As FIG. 2 As illustrated, the gNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. The gNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0107] The RF transceivers 210a-210n receive, from the antennas 205a-205n, incoming RF signals such as signals transmitted by UEs in the network 100. The RF transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to the RX processing circuitry 220, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The RX processing circuitry 220 transmits the processed baseband signals to the controller / processor 225 for further processing.

[0108] The TX processing circuitry 215 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The RF transceivers 210a-210n receive the outgoing processed baseband or IF signals from the TX processing circuitry 215 and up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0109] The controller / processor 225 can include one or more processors or other processing devices to manage the overall operation of the gNB 102. For example, the controller / processor 225 can control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 210a-210n, the RX processing circuitry 220, and the TX processing circuitry 215 in accordance with well-known principles. The controller / processor 225 can support additional functions as well, such as more advanced wireless communication functions.

[0110] For instance, the controller / processor 225 can support beamforming or directional routing operations in which output signals from multiple antennas 205a-205n are weighted differently and combined. The controller / processor 225 can support any of a variety of other functions of the gNB 102.

[0111] The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as an OS. The controller / processor 225 can move data into or out of memory 230 as needed by executing processes.

[0112] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems, e.g., through a backhaul connection or through the network. This interface 235 could support communications with other gNBs, with the core network, with public networks, such as the Internet, or with virtually any other device or system. The interface 235 could support communications through wired or wireless connections, or both. For example, the interface 235 could allow the gNB 102 to communicate with other gNBs over a wired or wireless backhaul connection to a cellular network. When the gNB 102 is implemented as part of a cellular system, such as a system supporting 5G, LTE, or LTE-A, the interface 235 can allow the gNB 102 to communicate with the other gNBs over a wired or wireless backhaul connection to a cellular network. When the gNB 102 is implemented as an access point, the interface 235 can allow the gNB 102 to communicate with other devices, such as other access points, over a wired or wireless local area network, or with a larger network, such as the Internet. The interface 235 includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver.

[0113] The memory 230 is coupled to the controller / processor 225. The memory 230 can include both read-only and re-writeable memory, such as flash memory or other ROM, and RAM.

[0114] Although FIG. 2 One example of a gNB 102 has been shown and described, various changes can be made to FIG. 2 For instance, the gNB 102 could include any number of FIG. 2Each of the components shown. As a particular example, an access point can include multiple interfaces 235, and the controller / processor 225 can support routing functions to route data between different network addresses. As another particular example, although shown as including a single instance of TX processing circuitry 215 and a single instance of RX processing circuitry 220, a gNB 102 can include multiple instances of each (such as one per RF transceiver). FIG. 2 The various components in the gNB 102 can be combined, further subdivided, or omitted and additional components can be added according to particular needs.

[0115] FIG. 3 An example UE 116 according to embodiments of the present disclosure is shown. FIG. 3 The embodiment of the UE 116 shown is for illustration only, FIG. 1 The UEs 111-115 can have the same or similar configuration. However, UEs have a wide variety of configurations and FIG. 3 The scope of the present disclosure is not limited to any particular implementation of a UE.

[0116] As FIG. 3 The UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, TX processing circuitry 315, a microphone 320, and receive (RX) processing circuitry 325, as shown. The UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touchscreen 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0117] The RF transceiver 310 receives, from the antenna 305, an incoming RF signal transmitted by a gNB of the network 100. The RF transceiver 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry 325 transmits the processed baseband signal to the speaker 330 (e.g., for voice data) or to the processor 340 for further processing (e.g., for web browsing data).

[0118] The TX processing circuitry 315 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to produce a processed baseband or IF signal. The RF transceiver 310 receives the outgoing processed baseband or IF signal from the TX processing circuitry 315 and up-converts the baseband or IF signal to RF signals that are transmitted via the antenna 305.

[0119] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 can control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 310, the RX processing circuitry 325, and the TX processing circuitry 315 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0120] The processor 340 is also capable of executing other processes and programs stored in the memory 360, such as a process for CSI reporting on uplink channels. The processor 340 can move data into or out of the memory 360 as required by the processes. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS 361 or in response to signals received from gNBs or an operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0121] The processor 340 is also coupled to the touchscreen 350 and the display 355. The operator of the UE 116 can use the touchscreen 350 to enter data into the UE 116. The display 355 can be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites.

[0122] The memory 360 is coupled to the processor 340. Part of the memory 360 can include random access memory (RAM), and another part of the memory 360 can include a flash memory or other read-only memory (ROM).

[0123] Although FIG. 3 One example of a UE 116 is shown, but FIG. 3 various changes can be made FIG. 3The various components in the computer system 300 can be combined, further subdivided, or omitted and additional components can be added according to particular needs. As a particular example, the processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, while FIG. 3 The UE 116 is shown configured as a mobile, or cell phone, but can be configured to operate as other types of mobile or stationary devices.

[0124] FIG. 4A is a high-level block diagram of transmit path circuitry. For instance, the transmit path circuitry can be used for an orthogonal frequency division multiplexing access (OFDMA) communication. FIG. 4B is a high-level diagram of receive path circuitry. For instance, the receive path circuitry can be used for an orthogonal frequency division multiplexing access (OFDMA) communication. In FIGS. 4A and 4B, for downlink communication, the transmit path circuitry can be implemented in a base station (gNB) 102 or relay station, and the receive path circuitry can be implemented in a user equipment (e.g., UE 116) of FIG. 1. In other examples, for uplink communication, the receive path circuitry 450 can be implemented in a base station (e.g., gNB 102) or relay station, and the transmit path circuitry can be implemented in a user equipment (e.g., UE 116) of FIG. 1. FIG. 1 FIG. 1 FIG. 1

[0125] The transmit path circuitry includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size N inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and a

[0126] At least some of the components in FIGS. 4A 400 and 4B 450 can be implemented with software, while other components can be implemented by configurable hardware or by a mixture of software and configurable hardware. In particular, it is noted that the FFT and IFFT blocks described in this disclosure document can be implemented as configurable software algorithms, where the value of N can be modified according to the implementation.

[0127] ​​​Furthermore, although the present disclosure relates to embodiments that implement a Fast Fourier Transform and an Inverse Fast Fourier Transform, this is merely exemplary and is not to be construed as limiting the scope of the present disclosure. It can be appreciated that in alternative embodiments of the present disclosure, the Fast Fourier Transform function and the Inverse Fast Fourier Transform function can be readily replaced by a Discrete Fourier Transform (DFT) function and an Inverse Discrete Fourier Transform (IDFT) function, respectively. It can be appreciated that for the DFT and IDFT functions, the value of the N variable can be any integer (i.e., 1, 4, 3, 4, etc.), whereas for the FFT and IFFT functions, the value of the N variable can be any integer that is a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

[0128] In transmit path circuitry 400, channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., LDPC coding) and modulates (e.g., quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) the input bits to produce a sequence of frequency domain modulation symbols. A serial-to-parallel block 410 converts (i.e., de-multiplexes) the serial modulated symbols to parallel data to produce N parallel symbol streams where N is the IFFT / FFT size used in the BS 102 and UE 116. An N-point IFFT block 415 then performs an IFFT operation on the N parallel symbol streams to produce time domain output signals. A parallel-to-serial block 420 converts (i.e., multiplexes) the parallel time domain output symbols from IFFT block 415 to produce a serial time domain signal. A cyclic prefix block 425 then inserts a cyclic prefix to the time domain signal. Finally, an up-converter 430 modulates (i.e., up-converts) the output of cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at baseband before conversion to the RF frequency.

[0129] The transmitted RF signal arrives at the UE 116 after passing through the wireless channel and reverse operations to those performed at the gNB 102 are performed. A down-converter 455 down-converts the received signal to baseband frequency and a remove cyclic prefix block 460 removes the cyclic prefix to produce the serial time domain baseband signal. A serial-to-parallel block 465 converts the time domain baseband signal to parallel time domain signals. An N-point FFT block 470 then performs an FFT algorithm to produce N parallel frequency domain signals. A parallel-to-serial block 475 converts the parallel frequency domain signals to a sequence of modulated data symbols. The modulated symbols are decoded and demodulated by a channel decoding and demodulation block 480 to recover the original input data stream.

[0130] Each of gNBs 101-103 can implement a transmit path that is analogous to transmitting in the downlink to user equipment 111-116 and can implement a receive path that is analogous to receiving in the uplink from user equipment 111-116. Similarly, each of user equipment 111-116 can implement a transmit path corresponding to the architecture for transmitting in the uplink to gNBs 101-103 and can implement a receive path corresponding to the architecture for receiving in the downlink from gNBs 101-103.

[0131] A peer awareness communication (PAC) network is a fully distributed communication network that allows for direct communication between PAC devices (PDs). The PAC network can employ several topologies such as mesh, star, etc. to support interactions between PDs for various services. While the present disclosure sets forth and describes the present disclosure using PAC networks and PDs as examples, it should be noted that the present disclosure is not limited to these networks. The general concepts set forth in the present disclosure can be used in various types of networks with different types of scenarios.

[0132] FIG. 5 An exemplary electronic device 501 according to embodiments of the present disclosure is shown. FIG. 5 The illustrated embodiment of electronic device 501 is for illustration only. FIG. 5 The scope of the present disclosure is not limited to any particular implementation. Electronic device 501 can perform one or more functions of 111-116 as described below. In one embodiment, electronic device can be 111-116 and / or 101-103 as described below. FIG. 1 The scope of the present disclosure is not limited to any particular implementation. Electronic device 501 can perform one or more functions of 111-116 as described below. In one embodiment, electronic device can be 111-116 and / or 101-103 as described below. FIG. 1 The scope of the present disclosure is not limited to any particular implementation. Electronic device 501 can perform one or more functions of 111-116 as described below. In one embodiment, electronic device can be 111-116 and / or 101-103 as described below.

[0133] A PD can be an electronic device. FIG. 5 An exemplary electronic device 501 according to various embodiments is shown. Referring to FIG. 5 Electronic device 501 can communicate with electronic device 502 via a first network 598 (e.g., a short-range wireless communication network), or with electronic device 104 or server 508 via a second network 599 (e.g., a long-range wireless communication network). According to one embodiment, electronic device 501 can communicate with electronic device 504 via server 508.

[0134] According to an embodiment, the electronic device 501 can include a processor 520, a memory 530, an input device 550, a sound output device 555, a display device 560, an audio 570, a sensor 576, an interface 577, a haptic 579, a camera 580, power management 588, a battery 589, a communication interface 590, a subscriber identification module (SIM) 596, or an antenna 597. In some embodiments, at least one (e.g., the display device 560 or the camera 580) of the components can be omitted from the electronic device 501, or one or more other components can be added in the electronic device 501. In some embodiments, some of the components can be implemented as single integrated circuitry. For example, the sensor 576 (e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) can be implemented as embedded in the display device 560 (e.g., a display).

[0135] The processor 520 can execute, for example, software (e.g., a program 540) to control at least one other component (e.g., a hardware or software component) of the electronic device 501 coupled with the processor 520 and can perform various data processing or computation. According to one embodiment of the disclosure, as at least a part of the data processing or computation, the processor 520 can load a command or data received from another component (e.g., the sensor 576 or the communication interface 590) to a volatile memory 532, process the command or the data stored in the volatile memory 532, and store resulting data in a non-volatile memory 534.

[0136] According to an embodiment of the disclosure, the processor 520 can include a main processor 521 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 523 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that can operate independently of, or in conjunction with, the main processor 521. Additionally or alternatively, the auxiliary processor 523 can be adapted to consume less power than the main processor 521 or to be specialized for a specified function. The auxiliary processor 523 can be implemented as separate from, or as part of, the main processor 521.

[0137] When the main processor 521 is in an inactive (e.g., sleep) state, the auxiliary processor 523 can control at least part of a function or state related to at least one of the components (e.g., the display device 560, the sensor 576, or the communication interface 590) of the electronic device 501 instead of the main processor 521, or when the main processor 521 is in an active state (e.g., executing an application), the auxiliary processor 523 controls at least part of a function or state related to at least one of the components (e.g., the display device 560, the sensor 576, or the communication interface 590) of the electronic device 501 together with the main processor 521. According to an embodiment, the auxiliary processor 523 (e.g., an image signal processor or a communication processor) can be implemented as a part of another component functionally related to the auxiliary processor 523 (e.g., the camera 580 or the communication interface 190).

[0138] The memory 530 can store various data used by at least one component (e.g., the processor 520 or the sensor 576) of the electronic device 501. The various data can include, for example, software (e.g., the program 540) and input data or output data for a command related thereto. The memory 530 can include the volatile memory 532 or the non-volatile memory 534.

[0139] The program 540 can be stored in the memory 530 as software, and can include, for example, an operating system (OS) 542, middleware 544, or an application program 546.

[0140] The input device 550 can receive a command or data to be used by another component (e.g., the processor 520) of the electronic device 501, from the outside (e.g., a user) of the electronic device 501. The input device 550 can include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus pen).

[0141] The sound output device 555 can output sound signals to the outside of the electronic device 501. The sound output device 555 can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as playing multimedia or playing a record, and the receiver can be used for incoming calls. According to an embodiment, the receiver can be implemented as independent of the speaker, or as a part of the speaker.

[0142] The display device 560 can visually provide information to the outside (e.g., a user) of the electronic device 501. The display device 560 can include, for example, a display, a hologram device, or a projector, and a control circuit for controlling a corresponding one of the display, the hologram device, and the projector. According to an embodiment, the display device 560 can include a touch circuit adapted to detect a touch, or a sensor circuit (e.g., a pressure sensor) adapted to measure the intensity of force caused by the touch.

[0143] The audio 570 can convert sounds into electrical signals, and vice versa. According to an embodiment, the audio 570 can obtain sounds via the input device 550, or output sounds via the sound output device 555 or a headphone of an external electronic device (e.g., an electronic device 502) directly (e.g., using a wired line) or wirelessly coupled with the electronic device 501.

[0144] The sensor 576 can detect an operational state (e.g., power or temperature) of the electronic device 501 or an environmental state (e.g., a state of a user) external to the electronic device 501, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor 576 can include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0145] The interface 577 can support one or more designated protocols to be used for directly (e.g., using a wired line) or wirelessly coupling the electronic device 501 with an external electronic device (e.g., the electronic device 502). According to an embodiment of the disclosure, the interface 577 can include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0146] The connection terminal 578 can include a connector through which the electronic device 501 can be physically connected with the external electronic device (e.g., the electronic device 502). According to an embodiment, the connection terminal 578 can include, for example, a HDMI connector, a USB connector, a SD card connector, or an audio connector (e.g., a headphone connector).

[0147] The haptic 579 can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that can be recognized by a user through his tactile sensation or kinesthetic sensation. According to an embodiment, the haptic 579 can include, for example, an electric motor, a piezoelectric element, or an electric stimulator.

[0148] The camera 580 can capture still images or moving images. According to an embodiment of the disclosure, the camera 580 can include one or more lenses, image sensors, image signal processors, or flashes.

[0149] The power management 588 can manage power supplied to the electronic device 501. According to an embodiment, the power management 588 can be implemented as at least a part of, for example, a power management integrated circuit (PMIC). The battery 589 can supply power to at least one component of the electronic device 501. According to an embodiment, the battery 589 can include, for example, a primary cell that is not rechargeable, a secondary cell that is rechargeable, or a fuel cell.

[0150] The communication interface 590 can support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 501 and an external electronic device (e.g., the electronic device 502, the electronic device 504, or the server 508) and performing communication via the established communication channel. The communication interface 590 can include one or more communication processors that are independent from the processor 520 (e.g., an application processor (AP)) and that support direct (e.g., wired) communication or wireless communication.

[0151] According to an embodiment of the disclosure, the communication interface 590 can include a wireless communication interface 592 (e.g., a cellular communication interface, a short-range wireless communication interface, or a global navigation satellite system (GNSS) communication interface) or a wired communication interface 594 (e.g., a local area network (LAN) communication interface or a power line communication (PLC)). A corresponding one of these communication interfaces can communicate with an external electronic device via the first network 598 (e.g., a short-range communication network, such as Bluetooth, wireless-fidelity (Wi-Fi), ultra-wideband (UWB), or infrared data association (IrDA)) or the second network 599 (e.g., a long-range communication network, such as a cellular network, the Internet, or a computer network (e.g., LAN or wide area network (WAN)).

[0152] The various types of communication interfaces described above can be implemented as a single component (e.g., a single chip), or can be implemented as a plurality of components (e.g., a plurality of chips) separated from each other. The wireless communication interface 592 can use subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module 596 to identify and authenticate the electronic device 501 in a communication network (e.g., the first network 598 or the second network 599).

[0153] The antenna 597 can transmit or receive a signal or power to or from the outside (e.g., an external electronic device) of the electronic device 501. According to an embodiment, the antenna 597 can include an antenna including a radiating element composed of a conductive material or a conductive pattern formed in or on a substrate (e.g., a PCB). According to an embodiment, the antenna 597 can include a plurality of antennas. In this case, at least one antenna suitable for a communication scheme used in a communication network (e.g., the first network 198 or the second network 599) can be selected from the plurality of antennas, for example, by the communication interface 590 (e.g., the wireless communication interface 592). Then, a signal or power can be transmitted or received between the communication interface 590 and the external electronic device via the selected at least one antenna. According to an embodiment, other components (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element can be additionally formed as part of the antenna 597.

[0154] At least a part of the above-described components can be coupled to each other and communicate signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).

[0155] According to an embodiment of the disclosure, commands or data can be transmitted or received between the electronic device 501 and the external electronic device 504 via the server 508 coupled with the second network 599. Each of the electronic devices 502 and 504 can be a device of a same type as or different from the electronic device 501. According to an embodiment, all or a part of operations that are to be performed by the electronic device 501 can be performed by one or more of the external electronic devices 502, 504, or 508. For example, if the electronic device 501 is capable of automatically performing a function or a service, or responding to a request received from a user or another device, the electronic device 501, instead of, or in addition to, performing the function or the service, can request one or more of the external electronic devices to perform at least part of the function or the service. The one or more external electronic devices receiving the request can perform at least part of the requested function or service, or an additional function or an additional service related to the request, and transfer a result of the performance to the electronic device 501. The electronic device 501 can provide the result, with or without further processing of the result, as at least part of a response to the request. To that end, cloud computing, distributed computing, or client-server computing technology can be used, for example.

[0156] The electronic device according to various embodiments can be one of a variety of types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. According to embodiments of this disclosure, the electronic device is not limited to the devices described above.

[0157] The various embodiments described herein can be implemented as software (e.g., program 140) comprising one or more instructions stored in a machine-readable storage medium (e.g., internal memory 536 or external memory 538). For example, a processor (e.g., processor 520) of the machine (e.g., electronic device 501) can invoke at least one of the one or more instructions stored in the storage medium and execute the instructions with or without one or more other components under the control of the processor. This allows the machine to perform at least one function according to the invoked at least one instruction. The one or more instructions may include code generated by a compiler or code executed by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory" means only that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but this term does not distinguish between cases where data is stored semi-permanently in the storage medium and cases where data is stored temporarily in the storage medium.

[0158] According to embodiments of this disclosure, methods according to various embodiments of this disclosure can be included and provided in a computer program product. The computer program product can be traded as a product between a seller and a buyer. The computer program product can be distributed in the form of a machine-readable storage medium (e.g., an optical disc read-only memory (CD-ROM)), or distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™), or directly between two user devices (e.g., smartphones). If distributed online, at least a portion of the computer program product can be temporarily generated or at least temporarily stored in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store server, or a relay server.

[0159] According to various embodiments of the present disclosure, each component (e.g., a module or a program) of the above-described components can include a single entity or multiple entities. According to various embodiments, one or more of the above-described components can be omitted, or one or more other components can be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) can be integrated into a single component. In such a case, according to various embodiments, the integrated component can still perform one or more functions of the plurality of components in the same or similar manner as they are performed by the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or other components can be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more operations can be executed in a different order or omitted, or one or more other operations can be added.

[0160] Ultra-wideband communication, achieved by transmitting short radio pulses, brings some key benefits to wireless communication, including low-complexity transceiver design, large capacity through the use of large bandwidth, and robustness to inter-symbol interference (ISI) in multi-path environments. At the same time, the extremely narrow pulses also reduce the probability of interception and detection by third parties, which is promising for data services with high security requirements, such as secure ranging. Currently, IEEE 802.15.4z is exploring and developing enhancements to the capabilities of low-rate and high-rate UWB pulse radios with the aim of providing better integrity and efficiency.

[0161] Ranging and relative positioning are essential for various location-based services and applications, such as direct Wi-Fi, Internet of Things (Iots), etc. With the tremendous growth of network devices, it is foreseeable that there will be a high demand for ranging requests in the near future, which means that the entire ranging message exchange occurs frequently in the network. This can exacerbate the bottleneck of battery capacity limitation. For mobile devices and self-sufficient static devices, such as low-power sensors, energy efficiency becomes even more critical.

[0162] Another key issue in dense environments is to meet the latency of scheduled ranging sessions for different pairs of ranging. Based on the ranging process defined in the IEEE specification, a dedicated time slot can be allocated for each pair of ranging. If there are a large number of ranging requests, it can result in long latency for the scheduled pairs later.

[0163] Therefore, it is necessary to implement a more efficient ranging protocol to reduce the number of message exchanges required for a large number of pairs of ranging. In the present disclosure, an optimized ranging process is provided between a group of devices and another group of devices. As FIG. 6As shown, one or more devices in Group 1 have ranging requests to one or more devices in Group 2, and vice versa. Utilizing the broadcast characteristics of wireless channels, optimized transmission mechanisms can be implemented based on ranging operations, namely single-sided two-way ranging (SS-TWR) and double-sided two-way ranging (DS-TWR), significantly reducing the number of information exchanges required compared to current standards.

[0164] FIG. 6 An exemplary many-to-many scenario 600 according to an embodiment of the present disclosure is shown. FIG. 6 The many-to-many scenario 600 shown in the illustration is for informational purposes only. FIG. 6 This disclosure is not intended to limit the scope to any particular implementation. FIG. 1 As shown, each node in group 1 and group 2 can perform the following actions: FIG. 1 One or more functions 111-116 and 101-103 are shown. In one embodiment, each node in group 1 and group 2 can be one of 111-116 and / or one of 101-103, such as FIG. 6 As shown.

[0165] like FIG. 6 As shown, Group 1 and Group 2 are determined by one or more devices. One or more devices from Group 1 have ranging requests to one or more devices from Group 2.

[0166] In this disclosure, for a pair of devices implementing ranging message exchange, the devices and associated messages are provided by the following corresponding terms: initiator; device that initializes a first ranging frame (RFRAME) and sends it to one or more responders; responder, device that expects to receive the first RFRAME from one or more initiators; polling, the RFRAME sent by the initiator, and the ranging response. The RFRAME is sent by the responder.

[0167] Two aspects are omitted from the IEEE standard specification that are essential for future use. The first is the optimized transmission process between one or more initiators and one or more responders, which could be crucial for energy efficiency. Since polling can be broadcast to multiple responders, an initiator can initialize a multicast (i.e., one-to-many) ranging cycle by sending a single polling poll instead of initiating multiple unicast ranging cycles. Similarly, since ranging responses can also be broadcast to multiple initiators, responders can embed request data from different initiators into a single ranging response message. Utilizing the broadcast nature of wireless channels, this optimized transmission process promises to be the future direction of UWB networks.

[0168] Another overlooked aspect is contention-based ranging selection in UWB networks. In the IEEE specification, a ranging cycle consists of only a single device pair: one initiator and one responder. Within a ranging cycle, transmissions are implicitly scheduled: the responder / initiator expects to receive a message from the remote end and can begin transmitting after receiving it. Multiple ranging cycles can be scheduled using a CFP table of synchronization frames. However, other use cases may exist that are not supported by the IEEE standard specification. For example, the initiator broadcasts polling, but the initiator does not have prior knowledge of who can respond. Similarly, the responder may not have prior knowledge of who can initiate ranging, so the responder might wait and listen for specific time periods to collect polls from different initiators separately.

[0169] In this disclosure, the UWB network is configured with ranging requests between one group of devices and another group of devices. For example... FIG. 7 As shown, one or more devices in Group 1 have ranging requests to one or more devices in Group 2, and vice versa. To accommodate the optimized ranging transmission process and other new use cases, the configuration of device roles needs to be determined and exchanged before the ranging cycle begins; that is, whether a device is configured as an initiator or a responder, and scheduling information for scheduling-based ranging. To establish a standalone UWB network, this disclosure defines new control IEs and ranging scheduling IEs for initiators and responders, which can be exchanged on the UWB MAC. However, this invention does not preclude other methods of exchanging information via higher layers or out-of-band management.

[0170] FIG. 7 An exemplary one-sided bidirectional ranging 700 according to an embodiment of the present disclosure is shown. FIG. 7 The embodiment of the single-sided bidirectional ranging 700 shown is for illustrative purposes only. FIG. 5 This disclosure is not intended to limit the scope to any particular implementation. It may be applicable as follows: FIG. 7 The electronic device 501 shown performs unilateral bidirectional ranging 700.

[0171] SS-TWR involves a simple measurement of the round-trip latency of a single message from the initiator to the responder, and the response sent back to the initiator. SS-TWR operates as follows: FIG. 8 As shown, device A initiates the exchange and device B responds to complete the exchange. Each device precisely timestamps the sending and receiving times of message frames, so time T can be calculated by simple subtraction. round and T reply Therefore, the obtained flight time T prop It can be estimated using the following equation:

[0172]

[0173] FIG. 8An exemplary two-sided bidirectional ranging method with three messages 800 is illustrated according to an embodiment of this disclosure. FIG. 8 The embodiment of two-sided bidirectional ranging with three messages 800 shown is for illustrative purposes only. FIG. 5 This disclosure is not intended to limit the scope to any particular implementation. It may be applicable as follows: FIG. 8 The illustrated electronic device 501 performs bidirectional ranging with three messages 800.

[0174] exist FIG. 9 The diagram illustrates a DS-TWR with three messages, which reduces estimation errors caused by clock drift due to long response delays. Device A is the initiator that initializes the first round-trip measurement, while device B acts as a responder, responding to complete the first round-trip measurement while simultaneously initiating the second round-trip measurement. Each device precisely timestamps the message transmission and reception times, and the resulting time-of-flight estimate T... prop It can be calculated using the following expression:

[0175]

[0176] FIG. 9 An exemplary ranging request response time IE content field format 900 according to an embodiment of the present disclosure is shown. FIG. 9 The example shown, illustrating the distance measurement request response time IE content field format 900, is for illustrative purposes only. FIG. 9 This disclosure is not intended to limit the scope to any particular implementation. FIG. 5 As shown, the IE content field format 900 for the distance measurement request response time can be represented as follows: FIG. 9 The electronic device shown is used.

[0177] Referring to the payload IE used for ranging control and the transmission of timestamps from the IEEE 802.15.8 document, the relevant ranging IE is described here.

[0178] The Ranging Request Response Time (RRRT) IE is used as part of ranging exchange to request ranging response times from remote devices participating in the exchange. If the RRRT IE is used to request response time values ​​from a specific device or multiple devices in a multicast / broadcast / many-to-many scenario, the RRRT IE may include a destination list field and a destination list length field, such as... FIG. 10 As shown. The Destination List Length field indicates the number of rows in the destination list, which can be equivalent to the number of devices that need to send response times.

[0179] FIG. 10 An exemplary destination list content field format 1000 according to an embodiment of the present disclosure is shown. FIG. 10The embodiment of the destination list content field format 1000 shown is for illustration only. FIG. 5 The scope of the present disclosure is not limited to any particular implementation. As FIG. 10 shown, the destination list content field format 1000 can be used by an electronic device as FIG. 11 shown.

[0180] Each row of the destination list includes a field for the MAC address of the destination device to send a reply time as FIG. 11 shown. The MAC address can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address.

[0181] A ranging time of flight (RTOF) information element (IE) can be used to transfer ranging results to a remote end upon request. Since multiple ranging results between a device and other devices can be embedded in one data frame, MAC address, or other short address, for example, a multicast group address can be added to the IE so that the device can extract the ranging results specific to the device. If a single device pair participates in the ranging cycle, the address field need not be used. An example of the RTOF IE content field format is shown in FIG. 11 . Other examples are not precluded.

[0182] FIG. 11 An example ranging time of flight IE content field format 1100 according to embodiments of the present disclosure is shown. FIG. 5 The embodiment of the ranging time of flight IE content field format 1100 shown is for illustration only. FIG. 10 The scope of the present disclosure is not limited to any particular implementation. As FIG. 12 shown, the ranging time of flight IE content field format 1100 can be used by an electronic device as FIG. 12 shown.

[0183] The ranging round trip measurement IE (RRTM IE) content includes the time difference between the transmission time of a ranging frame (RFRAME) that initiates a round trip measurement and the reception time of a response RFRAME for each source address that completes the round trip. The address field can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address. If a single device pair participates in the ranging cycle, the address field need not be used. FIG. 12 An example of the RRTM IE content field format is shown in . Other examples are not precluded.

[0184] FIG. 5 An example ranging round trip measurement IE content field format 1200 according to embodiments of the present disclosure is shown. FIG. 12 The embodiment of the ranging round trip measurement IE content field format 1200 shown is for illustration only. FIG. 13 The scope of the present disclosure is not limited to any particular implementation. AsFIG. 13 The round trip measurement IE content field format 1200 can be used in the ranging round trip measurement IE content field format 1200 as shown in FIG. 12. FIG. 13 in the electronic device 501 as shown in FIG. 1.

[0185] The RRTI IE content includes the time difference between the reception time of the most recently received RFRAME for each source address and the transmission time of the RFRAME containing the IE. The address field can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address. If a single device pair participates in the ranging cycle, the address field need not be used. In FIG. 5 An exemplary RRTI IE content field format is shown in FIG. 13. Other examples are not excluded.

[0186] FIG. 13 An exemplary ranging response time instant IE content field format 1300 according to embodiments of the present disclosure is shown. FIG. 14 The embodiment of the ranging response time instant IE content field format 1300 as shown in FIG. 13 is for illustration only and can be used in the electronic device as shown in FIG. 1. FIG. 14 The scope of the present disclosure is not limited to any particular implementation. FIG. 14 The scope of the present disclosure is not limited to any particular implementation.

[0187] The ranging response time delay IE (RRTD IE) content includes the time difference between the reception time of the most recently received RFRAME for each source address and the transmission time of the most recently transmitted response RFRAME prior to the frame containing the IE. The address field can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address. If a single device pair participates in the ranging cycle, the address field need not be used. In FIG. 5 An example of the RRTD IE content field format is shown in FIG. 14. Other examples are not excluded.

[0188] FIG. 14 An exemplary ranging response time delay IE content field format 1400 according to embodiments of the present disclosure is shown. FIG. 15 The embodiment of the ranging response time delay IE content field format 1400 as shown in FIG. 14 is for illustration only and can be used in the electronic device as shown in FIG. 1. FIG. 15 The scope of the present disclosure is not limited to any particular implementation. FIG. 15 The scope of the present disclosure is not limited to any particular implementation.

[0189] Ranging Angle of Arrival (AoA) Delay (RAD) IE content includes the AoA estimate at the device receiving the request for AoA. The RAD IE is used as part of a two-way ranging exchange and is used in cases where the AoA cannot be determined until after the device has transmitted a reply, and in this case the RAD IE carries the AoA in a subsequent frame. When the RAD IE is used in a multicast / broadcast frame (e.g., Multicast / Broadcast / Multi-to-Multi Ranging), the RAD IE content can include the MAC address or device ID of the source requesting the AoA estimate. The address field can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address. Otherwise, the RAD IE has a zero-length content field. The content field of the RAD IE can be formatted as shown in FIG. 5

[0190] FIG. 15 An exemplary Ranging Angle of Arrival Delay IE content field format 1500 according to embodiments of the present disclosure is shown. FIG. 16 The embodiment of the Ranging Angle of Arrival Delay IE content field format 1500 shown in FIG. 16 may be used in the electronic device shown in FIG. 16 The scope of the present disclosure is not limited to any particular implementation.

[0191] Ranging Report Control Single-Sided TWR (RRCST) IE is used to control SS-TWR message exchange. In FIG. 5 An exemplary RCST IE content field format is shown in Table 1. Other examples are not precluded.

[0192] FIG. 16 An exemplary Ranging Control Single-Sided TWR IE content field format 1600 according to embodiments of the present disclosure is shown. FIG. 17 The embodiment of the Ranging Control Single-Sided TWR IE content field format 1600 shown in FIG. 17 may be used in the electronic device shown in FIG. 17 The scope of the present disclosure is not limited to any particular implementation.

[0193] Table 1 Values for Control Information Field in Ranging Report Control Single-Sided TWR IE

[0194]

[0195] Ranging Report Control Double-Sided TWR (RRCDT) IE is used to control DS-TWR message exchange. In FIG. 5 An exemplary RCDT IE content field format is shown in Table 2. Other examples are not precluded.

[0196] FIG. 17 ​An exemplary ranging control two-way TWR IE content field format 1700 according to embodiments of the present disclosure is shown. FIG. 18 The illustrated embodiment of the ranging control two-way TWR IE content field format 1700 is for illustration only. FIG. 18 The illustrated electronic device. FIG. 18 The scope of the present disclosure is not limited to any particular implementation.

[0197] Table 2 Values of control information field in ranging report control two-way TWR IE

[0198]

[0199] FIG. 5 An exemplary time structure of a ranging cycle 1800 according to embodiments of the present disclosure is shown. FIG. 1 The illustrated embodiment of the time structure of the ranging cycle 1800 is for illustration only. FIG. 18 The scope of the present disclosure is not limited to any particular implementation.

[0200] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use the ranging cycle 1800 as shown in FIG. 34 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 34 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 18 The electronic device 501 can also be implemented as a initiator or responder as shown in FIG. 19 The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 19

[0201] The ranging configuration incorporates control information of a ranging cycle, which is composed of multiple time slots as shown in FIG. 19 A time slot is a basic time unit to implement message exchange. Other conventions to achieve the same functionality as the ranging cycle and time slot are not excluded in the present disclosure. Depending on device capability, time slot duration and time slot number in the ranging cycle can be adjusted in the ranging configuration, or fixed as default settings. One or more pairs of devices can participate in the ranging cycle to implement ranging request.

[0202] FIG. 5 An exemplary ranging device nomenclature 1900: controller and controller according to embodiments of the present disclosure is shown. FIG. 1 The illustrated embodiment of the ranging device nomenclature 1900 is for illustration only. FIG. 19 The scope of the present disclosure is not limited to any particular implementation.

[0203] ​In one embodiment, such as FIG. 6 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The ranging device naming convention shown is 1900. Electronic device 501 can be as follows: FIG. 19 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 20 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 20 As shown.

[0204] The ranging configuration settings determined by the next higher layer can be sent to one or more ranging controllers from the ranging controller (guiding device), such as... FIG. 20 As shown. Utilizing different network configurations, ranging configurations can be transmitted via dedicated data frames sent to one or more devices, or the ranging configuration can be embedded in synchronization frames broadcast to all devices in the network. Furthermore, this disclosure does not exclude other methods for exchanging ranging configuration information, such as via higher-layer or out-of-band management.

[0205] FIG. 5 An exemplary ranging loop structure 2000 according to an embodiment of the present disclosure is shown. FIG. 1 The embodiment of the ranging loop structure 2000 shown is for illustrative purposes only. FIG. 20 This disclosure is not intended to limit the scope to any particular implementation.

[0206] In one embodiment, such as FIG. 6 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The ranging loop structure 2000 is shown. Electronic device 501 can be as follows: FIG. 20 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 21 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 21 As shown.

[0207] The ranging configuration includes the structure of a ranging cycle, which comprises one or more polling cycles (PP) and one or more ranging response cycles (RRP), wherein a PP consists of one or more time slots for sending polling messages from the initiator, and an RRP consists of one or more time slots for sending response messages from the responder. FIG. 21Two examples of SS-TWR and DS-TWR with three message exchanges are shown, without excluding other examples. A ranging cycle can start from a ranging control period to exchange ranging configuration over UWB MAC. However, if ranging configuration is exchanged at higher layer, a ranging cycle can also start from a polling period.

[0208] For SS-TWR, one ranging cycle contains a PP and a RRP. For DS-TWR with three messages, one ranging cycle contains a first PP, a RRP, and a second PP. Each period includes one or more slots, where transmissions from initiators / responders can be scheduled as determined by next higher layer, or can contend for slots in the respective period, respectively.

[0209] FIG. 5 Exemplary content fields of a ranging schedule (RS) IE 2100 according to an embodiment of the present disclosure are shown. FIG. 1 The embodiments of the content fields of the ranging schedule (RS) IE 2100 shown are for illustration only. FIG. 21 The scope of the present disclosure is not limited to any particular implementation.

[0210] In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 6 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 34 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 34 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 22 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 22 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 22 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2.

[0211] FIG. 5 Exemplary rows of a RS table 2200 according to an embodiment of the present disclosure are shown. FIG. 1 The embodiments of the rows of the RS table 2200 shown in FIG. 2 are for illustration only. FIG. 22 The scope of the present disclosure is not limited to any particular implementation.

[0212] In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 6 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 34 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 34 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2. FIG. 18 In one embodiment, an electronic device 501 (e.g., one of 101-103 and 111-116 as shown in FIG. 1) can use the content fields of the ranging schedule (RS) IE 2100 as shown in FIG. 2.FIG. 21 The electronic device 501 can also be implemented as a responder, as shown in FIG. 22 .

[0213] For scheduled-based ranging, a ranging schedule (RS) IE can be used to schedule time slots of a ranging cycle, as shown in FIG. 22 . Examples of content fields of the RS IE are shown in FIG. 23 and FIG. 23 .

[0214] The RS IE contains a RS table, where each row of the table represents a time slot in the ranging cycle. As shown in FIG. 23 , a first field of a row represents a time slot index. A second field indicates the presence of a device ID / MAC address and a device type. If this value is 0, the time slot is reserved but not yet scheduled. If this value is 1, the time slot is assigned to a ranging device with a MAC address and a device type represented by the following fields.

[0215] The present disclosure does not exclude other structures of content fields for implementing similar functions.

[0216] FIG. 5 An exemplary RTR IE content field 2300 according to an embodiment of the present disclosure is shown. FIG. 1 The embodiment of the RTR IE content field 2300 shown is for illustration only. FIG. 23 The scope of the present disclosure is not limited to any particular implementation.

[0217] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use the RTR IE content field 2300 as shown in FIG. 34 . The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 34 . The electronic device 501 can also be implemented as a responder, as shown in FIG. 24 . The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 24 . FIG. 24

[0218] An exemplary row of a provider list 2400 according to an embodiment of the present disclosure is shown. FIG. 5 The embodiment of the row of the provider list 2400 shown is for illustration only. FIG. 1 The scope of the present disclosure is not limited to any particular implementation. FIG. 24 In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in

[0219] . The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 6The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The provider list shown is row 2400. Electronic device 501 can be, for example... FIG. 23 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 24 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 23 As shown.

[0220] A ranging device can use a Time-of-Flight (RTR) Request IE to request ranging results, i.e., the Time of Flight (ToF), from other ranging devices, which can then calculate the ToF associated with the requester. An example of the content fields of an RTR IE is shown in [link to RTR Request IE]. FIG. 24 and FIG. 25 As shown in the image.

[0221] like FIG. 25 As shown, the RTR IE can have three fields. The first field indicates the presence of subsequent fields. For unicast ranging, since the request address and provider address can be found in the address field of the MAC header, the address field is not needed in the RTR IE, and the provider address value is zero. If the ranging device wants to request ranging results from multiple remote ends via broadcast / multicast messages, the ranging device can list the addresses of the desired providers in the RTR IE. The value of the existing provider address can be 1, and the length of the provider list indicates the number of desired providers. In this disclosure, it is not excluded that... FIG. 25 Other address types can be determined by the device configuration and DstAddrMode of MCPS-DATA.request.

[0222] FIG. 5 An exemplary RAR IE content field 2500 according to an embodiment of this disclosure is shown. FIG. 1 The example of RARIE content field 2500 shown is for illustrative purposes only. FIG. 25 This disclosure is not intended to limit the scope to any particular implementation.

[0223] In one embodiment, such as FIG. 6 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The RAR IE content field 2500 is shown. Electronic device 501 can be as follows: FIG. 26 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 26The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 26 As shown.

[0224] FIG. 5 An exemplary row of a provider list 2600 according to an embodiment of this disclosure is shown. FIG. 1 The example shown in the provider list 2600 is for illustrative purposes only. FIG. 26 This disclosure is not intended to limit the scope to any particular implementation.

[0225] In one embodiment, such as FIG. 6 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The provider list 2600 shown is row 2600. Electronic device 501 can be, for example... FIG. 25 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 26 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 23 As shown.

[0226] A ranging device can use a Ranging Angle of Arrival Request (RAR) IE to request ranging results, i.e., the angle of arrival (AoA), from other ranging devices that have antenna arrays to estimate the requester's AoA. An example of the content fields of a RAR IE is shown in [link to RAR IE content field]. FIG. 23 and FIG. 26 As shown in the image.

[0227] The first octet of the RAR IE contains an indicator of presence, i.e., the provider address exists (and...). FIG. 27 The AoA (or AoA) is requested in the AoA, AoA (or AoA) is requested in the AoA, AoA (or AoA) is requested in the AoA, AoA (or AoA) is requested in the AoA, AoA (or AoA) is requested in the AoA, AoA (or AoA) field of the desired provider is requested; otherwise, it is not. Bits 3 through 7 are reserved to maintain a complete octet, but bits 3 through 7 can also be removed. FIG. 27 Similarly, when the value of the provider address is zero, there are no fields for provider list length and provider list; otherwise, the provider list length indicates the number of providers, and the provider list stack expects the provider addresses, as shown. FIG. 27 As shown.

[0228] FIG. 28 Another exemplary RAR IE content field 2700 according to an embodiment of this disclosure is shown. FIG. 28 The example of RAR IE content field 2700 shown is for illustrative purposes only.FIG. 28 The scope of the disclosure is not limited to any particular implementation.

[0229] FIG. 5 Another exemplary row of the provider list 2800 is shown in accordance with an embodiment of the disclosure. FIG. 1 The illustrated embodiment of the row of the provider list 2800 is for illustration only. FIG. 28 The scope of the disclosure is not limited to any particular implementation.

[0230] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use a row 2800 of the provider list as shown in FIG. 34 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 34 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 5 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 1 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 27 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in

[0231] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use a RAR IE content field 2700 as shown in FIG. 34 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 34 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 27 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 28 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 27 As shown, the electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2. The electronic device 501 can also be implemented as an initiator or a responder as shown in

[0232] The disclosure does not exclude other structures of the content field. For example, a requester can request AoA azimuth from a provider and AoA elevation from another provider. Thus, the RAR IE can be modified as FIG. 26 and FIG. 29

[0233] When the value of the provider address present is zero for unicast ranging, the provider list length field in FIG. 29 is not needed and the address field of the row in the provider list can also be removed. When the value of the provider address present is 1, the provider list length indicates the number of providers and the provider list stores the addresses of the providers and the type of AoA request. In the disclosure, the FIG. 29 ​An address type other than 27, which can be determined by the device configuration of MCPS-DATA.request and DstAddrMode.

[0234] FIG. 5 An exemplary RRR IE content field 2900 according to an embodiment of the disclosure is shown. FIG. 1 The embodiment of the RRR IE content field 2900 shown is for illustration only. FIG. 29 The scope of the disclosure is not limited to any particular implementation.

[0235] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use a row of the provider list 3000 as shown in FIG. 34 The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 34 The electronic device 501 can also be implemented as an initiator or responder as shown in FIG. 30 The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 30 FIG. 30

[0236] FIG. 5 A further exemplary row 3000 of a provider list 3000 according to an embodiment of the disclosure is shown. FIG. 1 The embodiment of the row of the provider list 3000 shown is for illustration only. FIG. 30 The scope of the disclosure is not limited to any particular implementation.

[0237] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use a row of the provider list 3000 as shown in FIG. 34 The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 34 The electronic device 501 can also be implemented as an initiator or responder as shown in FIG. 29 The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 30 FIG. 29

[0238] The request for AoA and ToF can be implemented by a single IE, which can be defined as a ranging result request (RRR) IE. FIG. 23 and FIG. 27 Examples of content fields are shown in

[0239] FIG. 29 With​​​​FIG. 30 and FIG. 31 are the same. For unicast ranging, the value of the provider address present is zero and the fields of the provider list length in FIG. 31 and the address field in FIG. 31 are not needed. Each row of the provider list contains an indicator of the requested information, i.e., AoA for the orientation field, AoA for the altitude field, and ToF. For example, if the value of the ToF request is 1, the requester needs the ToF estimate from the provider.

[0240] FIG. 5 Another exemplary RRR IE content field 3100 according to embodiments of the present disclosure is shown. FIG. 1 The embodiment of the RRR IE content field 3100 shown is for illustration. Other embodiments of the RRR IE content field 3100 can be used. FIG. 31 The scope of the present disclosure is not limited to any particular implementation.

[0241] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use the RRR IE content field 3100 as shown in FIG. 34 The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 34 The electronic device 501 can also be implemented as an initiator or responder as shown in FIG. 32 The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 32 FIG. 32

[0242] FIG. 5 Yet another exemplary row of the provider list 3200 according to embodiments of the present disclosure is shown. FIG. 1 The embodiment of the row of the provider list 3200 shown is for illustration. Other embodiments of the row of the provider list 3200 can be used. FIG. 32 The scope of the present disclosure is not limited to any particular implementation.

[0243] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 6 may use the row of the provider list 3200 as shown in FIG. 34 The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 34 The electronic device 501 can also be implemented as an initiator or responder as shown in FIG. 31 The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 32 FIG. 31

[0244] ​​​​If the same type of request applies to all providers, then it can be used. FIG. 31 and FIG. 33 The content field of the RRR IE shown.

[0245] like FIG. 33 As shown, the first octet's three bit fields are used to indicate the type of information requested. Bits 4 through 7 are reserved, but can also be removed. For unicast ranging, the value of the existing provider address is zero, and the required information is... FIG. 33 The provider list length and the provider list itself. If the value of the existing provider address is 1, then the provider list length represents the number of providers, and the provider list stacks the provider addresses.

[0246] When the requester is a ranging controller, both RS IE and RRR (or RTR, RAR) IE can be inserted into the scheduled RFRAME or data frame sent by the controller. The RRR IE indicates the request information from the controller, while the RS IE is used to schedule reserved time slots so that the desired provider / controller can send back the requested information.

[0247] When the requester is a ranging controller and the provider is a ranging controller, an RRR (or RTR, RAR)IE can be inserted into a scheduled RFRAME or data frame sent by the requester to the provider / controller. The controller can then directly use the reserved time slots to send the requested information to one or more requesters / controllers.

[0248] When both the requester and the provider are ranging controllers, the exchange of ranging results between independent UWB networks can be achieved in three steps: (1) Step 1, the requester broadcasts an RRR (or RTR, RAR) IE in a scheduled RFRAME or data frame; (2) Step 2, after step 1, the controller knows the requests from different ranging devices and schedules the provider in a reserved time slot via an RS IE; (3) Step 3, after step 1, the provider knows the requests from different requesters and sends the requested information in a scheduled time slot.

[0249] FIG. 5 A flowchart of a scheduling-based ranging method 3300 according to an embodiment of the present disclosure is shown. FIG. 1 The embodiments of method 3300 shown are for illustrative purposes only. FIG. 33 This disclosure is not intended to limit the scope to any particular implementation.

[0250] In one embodiment, such as FIG. 6 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows:FIG. 34 The method 3300 is shown. The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as FIG. 33 shown. The electronic device 501 can also be implemented as a starter or a responder as FIG. 33 shown. The electronic device 501 can also be implemented as a controller or a controller as FIG. 34 shown.

[0251] To summarize the above schemes, FIG. 34 Operation procedures for different cases are shown.

[0252] For contention-based ranging, since the ranging controller does not need to schedule time slots. The requester, as the ranging controller or the responder, can contend for time slots to send the ranging result request, i.e., RRR, RTR or RAR IE.

[0253] As FIG. 34 shown, the method 3300 starts at step 3302. In step 3302, the method 3300 determines whether the requester is a ranging controller. In step 3302, if the method 3300 determines that the requester is a ranging controller, the requester / controller sends RS IE and RRR (or RTR, RAR) IE to the scheduler provider via scheduled RFRAME or data frame in step 3304. In step 3308, the provider sends the requested information via scheduled time slots. In step 3302, if the method determines that the requester is not a ranging controller, the method 3300 determines whether the provider is a ranging controller in step 3310. In step 3310, the method 3300 determines that the provider is a ranging controller, the requester / controller sends RRR (or RTR, RAR) IE to the provider / controller via scheduled RFRAME or data frame in step 3312. In step 3314, the provider / controller sends the requested information via reserved time slots. In step 3310, if the method determines that the provider is not a ranging controller, the requester broadcasts RRR (or RTR, RAR) IE in a scheduled RFRAME or data frame. In step 3318, the controller schedules the provider on reserved time slots via RS IE. In step 3320, the provider sends the requested information via scheduled time slots.

[0254] FIG. 5 An exemplary message sequence chart 3400 of multicast ranging is shown, in which the ranging controller is a starter and a requester, according to an embodiment of the present disclosure. FIG. 1 The embodiment of the message sequence chart 3400 is shown for illustration only. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0255] In one embodiment, asFIG. 6 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The message sequence diagram 3400 is shown. Electronic device 501 can be as follows: FIG. 34 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 35 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 35 As shown.

[0256] FIG. 35 An example of a message sequence diagram (MSC) with multicast ranging is shown, where the ranging controller is both the initiator and the requester. The first RS IE in the ranging control message / frame is used to configure the ranging loop. The last time slot of the ranging loop is reserved by the ranging controller and is later scheduled to responder-1 via the second RS IE. Thus, responder-1 can use the last time slot of the ranging loop to send the ranging result to the requester / controller. Various examples of MSCs for different use cases may exist and are not excluded from this disclosure.

[0257] Different Intermediate Requests (IEs) are defined to satisfy requests for timestamp-related information in IEEE standard specifications. For example, a Ranging Request Response Time (RRRT) IE can be used to request a ranging response time from the device receiving the IE. Ranging Report Control Two-Sided TWR (RRCDT) IEs and Ranging Report Control One-Sided TWR (RRCST) IEs can be used for the exchange of response times and / or round-trip measurements of DS-TWR and SS-TWR, respectively. However, the Modified Ranging Result Request (RRR) IE in this embodiment can implement the functionality of these IEs for requests for timestamp-related information and AoA. This disclosure does not exclude other suitable terms for the IE.

[0258] FIG. 5 An exemplary RRR IE content field format 3500 according to an embodiment of the present disclosure is shown. FIG. 1 The example of RRR IE content field format 3500 shown is for illustrative purposes only. FIG. 35 This disclosure is not intended to limit the scope to any particular implementation.

[0259] In one embodiment, such as FIG. 6 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: ​ The RRR IE content field format shown is 3500. Electronic device 501 can be as follows: ​One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: ​ The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 34 As shown.

[0260] FIG. 35 The corrected RRR IE content field format is shown. The first field, Provider Address Presence (PAP), indicates the presence of the address field in each row / element of the provider list. If this value is 1, it indicates presence. FIG. 36 The address field must be present in the list of providers; otherwise, it will not exist. The Provider List Length (PLL) field indicates the number of rows / elements in the provider list, which is equal to the number of providers.

[0261] For unicast ranging between a ranging initiator and a ranging responder, the provider address can be specified by the destination address field of the MHR. Therefore, the PAP field can be set to zero, and FIG. 36 The address field does not exist.

[0262] For multi-node ranging, such as FIG. 35 As shown, a ranging device can broadcast appropriate RFRAME or data messages with RRR IEs to multiple providers. If the rows / elements of the RRR IEs are stacked in a predetermined fixed order to list requests to different providers, the address field may be absent, provided that the predetermined order has already been exchanged between the ranging devices. Therefore, in this case, FIG. 35 The PAP field can be set to zero.

[0263] FIG. 36 Exemplary rows / elements of a provider list 3600 according to embodiments of this disclosure are shown. FIG. 36 The examples of rows / elements in the provider list 3600 shown are for illustrative purposes only. FIG. 5 This disclosure is not intended to limit the scope to any particular implementation.

[0264] In one embodiment, such as FIG. 1 The electronic device 501 shown (e.g., such as...) FIG. 36 The figures 101-103 and 111-116 shown can be used as follows: FIG. 6 The provided provider list 3600 shows rows / elements. Electronic device 501 can be, for example... FIG. 34 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 36 As shown.

[0265] Notice, FIG. 35 One of the reserved fields in the code can be used to indicate the existence of an address. Therefore, it is possible to remove... FIG. 36 The provider addresses that exist in the list are included, and the length of the provider list becomes one octet.

[0266] The first bit field of each row / element in the provider list is the Address Type (AT). If this value is 1, a short address of 2 octets is used in the address field; otherwise, an extended address of 8 octets is used, and vice versa. The AT field provides flexibility for exchanging requests in UWB networks with mixed address types. More bits can be used in the AT field to distinguish more address types, which is not excluded by this disclosure. If the ranging devices in the network have the same address type, i.e., 2 octets or 8 octets, the provider's address type can be specified by DstAddrMode of MCPS-DATA.request and can be removed. FIG. 36 The address type field in the code. Therefore, FIG. 37 Simplified to FIG. 37 .

[0267] FIG. 37 Another exemplary row / element of a provider list 3700 according to an embodiment of this disclosure is shown. FIG. 37 The examples of rows / elements in the provider list 3700 shown are for illustrative purposes only. FIG. 5 This disclosure is not intended to limit the scope to any particular implementation.

[0268] In one embodiment, such as FIG. 1 The electronic device 501 shown (e.g., such as...) FIG. 37 The figures 101-103 and 111-116 shown can be used as follows: FIG. 6 The provided provider list 3700 is shown in rows / elements. Electronic device 501 can be, for example... FIG. 34 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 36 As shown.

[0269] exist FIG. 37 and FIG. 35 In the context of the Response Time Request (RTR) field, it indicates whether a response time has been requested from the provider for sending a response to a message with an RRRIE: if the RTR value is 1, a response time is requested; otherwise, no response time is requested.

[0270] The Round Trip Measurement Request (RMR) field indicates whether a round trip measurement from the provider was requested when a message with an RRR IE was received: if the RMR value is 1, a round trip measurement was requested; otherwise, no request was made.

[0271] The following bit fields used for Time of Flight (TOFR), AoA (AoA) and AoA (AER) requests indicate whether the Time of Flight (TOF), AoA in the AoA field, and AoA in the AoA field have been requested: if the requested bit field has a value of 1, the corresponding information has been requested; otherwise, no request has been made.

[0272] FIG. 36 and FIG. 37 (or FIG. 38 The modified RRR IE with content field format shown in the figure can be used to implement the functions of RRRT, RRCST, RRCDT and RRA IE in IEEE 802.15.4z for requesting certain information.

[0273] Different Intermediate Entities (IEs) are defined to implement the reporting of timestamp-related information and AoA (Aspect-of-Authorization) data as specified in the IEEE standard. For example, the Ranging Response Time Instantaneous (RRTI) IE can be used to transmit the response time of a ranging response message, while the Ranging Round-Trip Measurement (RRTM) IE can be used to transmit round-trip time measurements. In this embodiment, the newly defined IE, namely the Ranging Report (RR) IE, can be used to implement the exchange of time-related information and AoA data. This disclosure does not exclude other suitable terms for the IE. Examples of content field formats are provided in... FIG. 39 and FIG. 38 As shown in the image.

[0274] FIG. 38 An exemplary RR IE content field format 3800 according to an embodiment of the present disclosure is shown. FIG. 5 The example of RR IE content field format 3800 shown is for illustrative purposes only. FIG. 1 This disclosure is not intended to limit the scope to any particular implementation.

[0275] In one embodiment, such as FIG. 38 The electronic device 501 shown (e.g., such as...) FIG. 6 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The RR IE content field format shown is 3800. Electronic device 501 can be as follows: FIG. 34 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 39 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 39 As shown.

[0276] FIG. 39 Exemplary rows / elements of RR table 3900 according to an embodiment of this disclosure are shown. FIG. 5 The example of rows / elements in RR table 3900 shown is for illustrative purposes only. FIG. 1 This disclosure is not intended to limit the scope to any particular implementation.

[0277] In one embodiment, such as FIG. 39 The electronic device 501 shown (e.g., such as...) FIG. 6 The figures 101-103 and 111-116 shown can be used as follows: FIG. 34 The rows / elements of RR table 3900 are shown. Electronic device 501 can be as follows: FIG. 34 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 38 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 35 As shown.

[0278] like FIG. 39 As shown, the RR IE content field format is similar to FIG. 35 The format of the RR IE is shown below. The first field indicates the presence of the address field in each element of the Distance Report (RR) table: if the value is 1, the address field exists; otherwise, it does not. The RR table length field indicates the number of rows / elements in the RR table, which is equal to the number of distance measuring devices requesting certain information.

[0279] For unicast ranging between a ranging initiator and a ranging responder, the requester's address can be specified by the destination address field of the MHR. Therefore, the AP's field can be set to zero, and FIG. 38 The address field does not exist.

[0280] For multi-node ranging, the ranging device can broadcast information such as... to multiple destinations. FIG. 39 The appropriate RFRAME or data message for the RR IE is shown. If the rows / elements of the RR IE are stacked in a predetermined fixed order to list ranging result reports for different destinations, the address field may be absent, provided that the predetermined order has already been exchanged between ranging devices. Therefore, in this case, FIG. 39 The AP field can be set to zero.

[0281] Notice, FIG. 40 One of the reserved fields in the code can also be used to indicate an existing address. Therefore, it is possible to remove... FIG. 40 The address that exists in it, and the size of the RR table becomes an octet.

[0282] The first bit field of each row / element of the RR table is the address type (AT). If the value is 1, a short address of 2 octets is used in the address field, otherwise an extended address of 8 octets is used in the address field, and vice versa. The AT field provides flexibility in exchanging requests in a UWB network with mixed address types. More bits in the AT field can be used to distinguish more address types, which is not excluded by the present disclosure. If the ranging devices of the network have the same address type, i.e., 2 octets or 8 octets address, the address type can be specified by the DstAddrMode of the MCPS-DATA.request, and the address type field in FIG. 40 may be removed. Thus, FIG. 40 is simplified to FIG. 5 .

[0283] FIG. 1 Another exemplary row / element of the RR table 4000 according to an embodiment of the present application is shown. FIG. 40 The embodiments of the row / element of the RR table 4000 shown in FIG. 6 do not limit the scope of the present disclosure to any particular implementation.

[0284] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 34 may use the row / element of the RR table 4000 as shown in FIG. 34 . The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 35 . The electronic device 501 can also be implemented as an initiator or responder as shown in FIG. 36 . The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 37 . FIG. 38

[0285] The fields of reply time present (RTP), round trip measurement present (RMP), ToF present (TOFP), AoA azimuth present (AAP), and AoA altitude present are indicators that the following fields are present, respectively, including RX to TX reply time, TX to RX round trip time, time of flight (ToF), AoA azimuth, and AoA altitude. If the value of the indicator is 1, the corresponding field for reporting certain information is present, otherwise it is not present.

[0286] ​The Delay Mode field is an indicator that indicates whether a separate data frame following the ranging transmission is used to transmit the ranging report: if the value is 1, the delay mode is enabled, and the RR IE is inserted into a separate data message to report timestamp-related information and / or AoA of the most recently completed ranging period; otherwise, the ranging report IE is embedded in the RFRAME within the ranging period to report certain information.

[0287] For example, if the PPDU format of RFRAME is SP3 as specified in the IEEE standard, the ranging report cannot be transmitted via RFRAME because there is no MAC header or payload in the SP3 frame. Therefore, an RRIE can be inserted into the data message after the ranging period, and the delay mode field can be set to 1 to indicate that the delay mode is enabled.

[0288] Another example of enabling delayed mode is sending the requested ranging response time and / or round-trip time after the ranging period, because the ranging device may not be able to calculate the response / round-trip time in time and embed the ranging report into the RFRAME. Therefore, a separate data message after the ranging period can be used to exchange the ranging report IE with a delayed mode field value of 1.

[0289] Similar to the definition in the IEEE standard specification, the RX to TX response time field has the following characteristics: FIG. 39 and FIG. 40 (or FIG. 40 The time difference between the reception time of the most recently received RFRAME (or RRRRT IE from a specific source) and the transmission time of the corresponding RFRAME, as shown in the diagram. These time values ​​are referenced to the RMRARKER. In the IEEE standard specification, the time unit bit is specified as the ranging counter time unit bit.

[0290] Similar to the definition in the IEEE 802.15.4z specification, the TX to RX round-trip time field is the time difference between the transmission time of the RFRAME that initiates the round-trip measurement and the reception time of the response RFRAME that completes the round-trip measurement. The time unit is the same as the time unit of the RX to TX response time field, i.e., the ranging counter time unit.

[0291] The TOF, AoA azimuth, and AoA height fields follow the same definitions as those in IEEE 802.15.4z, and will not be repeated here.

[0292] FIG. 41 and FIG. 41 (or FIG. 41The RR IE with content field format shown in the diagram can be used to implement the functions of RRTI, RRTD, RRTM, RAR, and RTOF IE in IEEE 802.15.4z, which are used to report certain information. Note that the size of the field reporting certain information is... FIG. 5 The example shown is provided below. Depending on the use case and implementation, this disclosure does not exclude other field sizes.

[0293] In one embodiment, two examples of message sequence diagrams (MSCs) based on RRR and RRIE are shown for SS-TWR and DS-TWR with one-to-many ranging. Various different MSCs can be implemented to accommodate different ranging requests / reports, which is not excluded from this disclosure.

[0294] FIG. 1 An exemplary message sequence diagram 4100 of a one-to-many SS-TWR with RRR and RR IE according to an embodiment of the present disclosure is shown. FIG. 41 The embodiment of message sequence diagram 4100 shown is for illustrative purposes only. FIG. 6 This disclosure is not intended to limit the scope to any particular implementation.

[0295] In one embodiment, such as FIG. 34 The electronic device 501 shown (e.g., such as...) FIG. 34 The figures 101-103 and 111-116 shown can be used as follows: FIG. 41 The message sequence diagram 4100 is shown. Electronic device 501 can be as follows: FIG. 41 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 41 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 39 As shown.

[0296] exist FIG. 40 In the process, the ranging initiator initializes the ranging transfer by enabling the MCPS-DATA.request and RRR IE parameters of the Range parameter to request a response time from the responder. After the first ranging transfer, MCPS-DATA.confirm reports the transfer time to the higher layer in units of the ranging counter time.

[0297] Upon receiving a ranging initiation message, higher layers of the responder can generate a ranging report (RR) IE with a response time and transmit the RR IE to the MAC layer. Simultaneously, different responders can request different types of ranging results, reflected in the RRR IE within the ranging response message. For example, as... FIG. 42 As shown, responder-1 directly requests the RRR IE via...FIG. 42 The RRR (TOFR) IE in the Ranging Response message indicates the time of flight (ToF). The responder-N requests the round trip time from the ranging initiator, which is indicated by the RRR (RMR) IE. After sending the Ranging Response message, the MAC layer of the responder reports the time of transmission in ranging counter time units.

[0298] By the reply time requested in the response message, the higher layer of the ranging initiator is able to estimate the time of flight (ToF), which enables the final ranging result. In FIG. 42 The points marked by (R) are used to mark the time when the ToF can be estimated.

[0299] After the transmission of one ranging cycle including the Ranging Initiation message and the Ranging Response message, the higher layer of the ranging initiator forms the RR IE, which includes the ranging reports to different responders. For the ranging report to responder-1, the corresponding row / element of the RR table with the TOFP field of 1 contains the ToF field as shown in FIG. 5 (or FIG. 1 ) For the ranging report to responder-N, the corresponding row / element of the RR table with the RMP field of 1 contains the round trip time field. Upon receiving the ranging report, the MCPS-DATA.indication reports certain information requested to the higher layer of the responder.

[0300] FIG. 42 An exemplary message sequence chart 4200 for one-to-many DS-TWR with RRR and RR IE according to embodiments of the present disclosure is shown. FIG. 6 The embodiments of the message sequence chart 4200 shown are for illustration. Other embodiments can be used. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0301] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 34 may use the message sequence chart 4200 as shown in FIG. 42 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 42 The electronic device 501 can also be implemented as a responder or a responder as shown in FIG. 43 The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 43 FIG. 5

[0302] FIG. 1 An example of a message sequence chart for one-to-many DS-TWR is shown. Compared to SS-TWR, FIG. 43 ​​A second round-trip measurement is implemented with an additional ranging transmission from the initiator. In the ranging response message, the high layer of the responder conveys the RRRIE to request the round-trip time of the first round-trip measurement and the reply time of the second ranging transmission from the initiator, which is indicated by the RRR (RTR, RMR) IE.

[0303] FIG. 6 An example message sequence chart 4300 for one-to-many DS-TWR with RRR and RR IE is shown, in accordance with an embodiment of the present disclosure, where the initiator requests ToF. FIG. 34 The embodiment of the message sequence chart 4300 shown is for illustration only. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0304] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 44 may use the message sequence chart 4300 as shown. The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown. The electronic device 501 can also be implemented as an initiator or a responder as shown. The electronic device 501 can also be implemented as a controller or a controller as shown. FIG. 44 FIG. 44 FIG. 5 FIG. 1 FIG. 44

[0305] FIG. 6 An example message sequence chart 4400 for one-to-many DS-TWR with RRR and RR IE is shown, in accordance with an embodiment of the present disclosure, where the initiator requests reply time and round-trip time. FIG. 34 The embodiment of the message sequence chart 4400 shown is for illustration only. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0306] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 42 may use the message sequence chart 4400 as shown. The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown. The electronic device 501 can also be implemented as an initiator or a responder as shown. The electronic device 501 can also be implemented as a controller or a controller as shown. FIG. 42 FIG. 43 FIG. 44 FIG. 43 FIG. 43

[0307] ​​​​​​​​​​Upon reception of the request in the ranging response message, the higher layer of the ranging initiator forms a ranging report (RR) IE including the round trip time of the first round trip measurement and the reply time of the second ranging transmission to the different responder. After reception of this information and the local reception time, the ranging responder is able to estimate the time of flight (ToF) in FIG. 44 Since no report message is requested, no additional message is reported back to the initiator in FIG. 45 the ranging result. FIG. 46 and FIG. 45 Two other MSC examples of a one-to-many DS-TWR are shown, which include a request for the ranging result from the initiator.

[0308] In FIG. 45 , the ranging initiator embeds a TOFR field value of 1 into the RRR IE to request the ToF from the responder, which is indicated by the RRR(TOFR) IE in the ranging initiation message. The same request can also be inserted from the ranging initiator into the second ranging transmission, which is not excluded by the present disclosure. After completion of the full ranging cycle of the DS-TWR, the ranging responder sends back the ranging result, i.e. the ToF, via the RR IE, which is shown by the dashed box in FIG. 45 .

[0309] In FIG. 5 , the ranging initiator can also request the reply time of the response RFRAME and the round trip time of the second round trip measurement instead of the ToF, based on which the ranging initiator is able to estimate the ToF.

[0310] In the ranging initiation message, the ranging initiator requests the reply time of the response RFRAME from the ranging responder via the RRR IE, which is indicated by the RRR(RTR) IE. In the response RFRAME, the ranging responder not only sends the request for the reply time of the RFRAME of the second initiator and the round trip time of the first round trip measurement to the initiator, but also sends the reply time to the initiator, which is indicated by the RRR(RTR, RMR) and RR IE with the reply time, respectively. The second RFRAME of the ranging initiator contains the ranging report of the requested information and the request for the round trip time, which are exchanged via the RR IE and the RR IE, respectively.

[0311] Upon reception of the request of the initiator in the second RFRAME, the ranging responder uses a separate data message to convey the round trip time of the second round trip measurement. Thus, the initiator is also able to estimate the total ToF.

[0312] In the above embodiments, the RRR IE for controlling ranging requests and the RR IE for controlling ranging reports can be merged into a single IE, namely the Ranging Request and Reporting Control (RRRC) IE. An example of the content field format is... FIG. 1 and FIG. 45 As shown in the image.

[0313] FIG. 6 An exemplary RRRC IE content field format 4500 according to an embodiment of the present disclosure is shown. FIG. 34 The example of RRRC IE content field format 4500 shown is for illustrative purposes only. FIG. 34 This disclosure is not intended to limit the scope to any particular implementation.

[0314] In one embodiment, such as FIG. 46 The electronic device 501 shown (e.g., such as...) FIG. 46 The figures 101-103 and 111-116 shown can be used as follows: FIG. 46 The RRRC IE content field format shown is 4500. Electronic device 501 can be as follows: FIG. 5 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 1 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 46 As shown.

[0315] FIG. 6 An exemplary row / element of RRRC table 4600 according to an embodiment of the present invention is shown. FIG. 34 The example of rows / elements in RRRC Table 4600 shown is for illustrative purposes only. FIG. 34 The scope of this invention is not limited to any particular implementation.

[0316] In one embodiment, such as FIG. 45 The electronic device 501 shown (e.g., such as...) FIG. 35 The figures 101-103 and 111-116 shown can be used as follows: FIG. 38 The rows / elements of RRRC table 4600 are shown. Electronic device 501 can be as follows: FIG. 46 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 46 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 47 As shown.

[0317] FIG. 47 The format of the content fields shown is similar to FIG. 47 and FIG. 47The content field format is as follows. The first field indicates the presence of the address field in each row / element of the RRRC table: if the value is 1, the address field exists; otherwise, it does not. The RRRC table length field indicates the number of rows / elements in the RRRC table, which is equal to the number of ranging requests and ranging reports that the ranging device can send to one or more destinations.

[0318] The first field of each row / element in the RRRC table is the Address Type (AT). If this value is 1, a short address of 2 octets is used in the address field; otherwise, an extended address of 8 octets is used, and vice versa. The AT field provides flexibility for exchanging requests in UWB networks with mixed address types. More bits can be used in the AT field to distinguish more address types, which is not excluded by this disclosure. If the ranging devices in the network have the same address type, i.e., 2 octets or 8 octets, the address type can be specified by DstAddrMode of MCPS-DATA.request, and can be removed. FIG. 5 The address type field in the code. Therefore, FIG. 1 Simplified to FIG. 47 .

[0319] FIG. 6 An exemplary row / element of RRRC table 4700 according to an embodiment of the present invention is shown. FIG. 34 The example of rows / elements in RRRC Table 4700 shown is for illustrative purposes only. FIG. 34 This disclosure is not intended to limit the scope to any particular implementation.

[0320] In one embodiment, such as FIG. 46 The electronic device 501 shown (e.g., such as...) FIG. 47 The figures 101-103 and 111-116 shown can be used as follows: FIG. 39 The rows / elements of RRRC table 4700 are shown. Electronic device 501 can be as follows: FIG. 40 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 46 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 47 As shown.

[0321] exist FIG. 47 (or FIG. 48 In the RRRC table, the Request / Report Indicator (RRI) field indicates whether the row / element in the RRRC table is to send a ranging request or a ranging report to a specific destination.

[0322] If the RRI value is 1, the element will send a ranging request, where the requested information can be represented by the following fields, including a reply time request (RTR), a round trip measurement request (RMR), a ToF request (TOFR), an AoA azimuth request (AAR), and an AoA elevation request (AER). If the value of the request field is 1, the destination is requested for the corresponding information, otherwise it is not requested. The delay mode (DM) field configured by the ranging requester will let the destination know whether to send a ranging report in the RFRAME or to send a delay data message: if the DM value is 1, the destination can send the ranging report in a separate data message after the current ranging period, otherwise the ranging report can be embedded into the responding RFRAME.

[0323] In the case where the RRI value is 1, there are no fields for ranging reports including RX-to-TX reply time, TX-to-RX round trip time, ToF, AoA azimuth, and AoA elevation.

[0324] If the RRI value is zero, this element of the RRRC table is used to send a ranging report to a specific destination. In this case, the fields of RTR, RMR, TOFR, AAR, AER are used to indicate the presence of the corresponding fields for ranging reports, including RX-to-TX reply time, TX-to-RX round trip time, ToF, AoA azimuth, and AoA elevation. If the request field is 1, the corresponding field for reporting certain information is present, otherwise it is not present. Note that the fields for ranging reports follow the same definition as in FIG. 47 or FIG. 48 .

[0325] The RRRC table with elements as shown in FIG. 48 (or FIG. 48 ) can stack multiple ranging requests and / or ranging reports to different destinations. Timestamp-related information and / or AoA can be requested or reported via the same IE. Some implementations and use cases can not support certain features. For example, AoA estimation requests devices with antenna arrays, which are not applicable at all times. Therefore, a subset of the fields for ranging requests / reports can be kept from FIG. 5 . FIG. 1 An example of a simplified row / element of the RRRC table is shown, which contains only timestamp-related information. Compared to the simplification of FIG. 48 , other simplifications of the RRRC table elements / rows are not excluded by the present disclosure. FIG. 6 An example of a simplified row / element of the RRRC table 4800 according to an embodiment of the present application is shown. FIG. 34 The embodiment of the simplified row / element of the RRRC table 4800 shown in FIG. 34 The scope of the present application is not limited to any particular embodiment.

[0326] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 41-44 may use the simplified row / element of the RRRC table 4800 as shown in FIG. 41-44 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 49 The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 49 The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 49 FIG. 5

[0327] The ranging procedure and the corresponding message sequence chart with RRRC IE is similar to the ranging procedure and the corresponding message sequence chart via RRR and RR IE as shown in FIG. 1 The functions of RRR, RR IE introduced in the above embodiments can be implemented by RRRC IE. When the request / report indicator field value is 1, the element / row of the RRRC table will request certain information, which is the same as the information of the row / element in the provider list. When the request / report indicator field value is 0, the element / row of the RRRC table will report certain information, which is the same as the information of the row / element in the RR table. Therefore, FIG. 49 The RRR, RR IE in

[0328] FIG. 6 An example revised ranging result request IE (RRR IE) with one control octet 4900 according to an embodiment of the application is shown. FIG. 34 The embodiment of the revised ranging result request IE (RRR IE) with one control octet 4900 as shown is for illustration only. FIG. 34 The scope of the disclosure is not limited to any particular implementation.

[0329] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 50 may use the revised ranging result request IE (RRR IE) with one control octet 4900 as shown in FIG. 50 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 50 The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 5 The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 1 FIG. 50 ​​​​

[0330] FIG. 6 Exemplary elements / rows in the RRR table 5000 according to embodiments of the present disclosure are shown. FIG. 34 The embodiments of the elements / rows in the RRR table 5000 shown in FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0331] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 35 may use the elements / rows in the RRR table 5000 as shown in FIG. 49 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 50 The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 49 The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 51 FIG. 51

[0332] The ranging result request IE (RRR IE) introduced in the foregoing embodiments can be used to send a ranging request to different devices. In each element of FIG. 51 , there can be one control octet to indicate the requested information to a specific ranging device. If the same request applies to multiple ranging devices, one control octet can be used to indicate the requested information, which can apply to all devices receiving the IE. The number of control octets required is reduced from the number of destinations to one. FIG. 51 An example of the content field format for the revised RRR IE is shown, in which the elements or rows of the content field format are shown in FIG. 5

[0333] In FIG. 1 , the address present field is used to indicate whether the RRR table length and RRR table field exist: if the address present field value is 1, the RRR table length and RRR table field exist, otherwise the RRR table length and RRR table field do not exist. The RRR table length is equal to the number of rows or elements in the RRR table, which is the same as the number of devices that can receive the RRR IE.

[0334] ​​​If the RRR IE is transmitted in a unicast frame, the MHR specifies the destination address. Therefore, the RRR table length and RRR table fields are not needed. When the RRR IE is transmitted in a broadcast and multicast message, the device sending the IE expects to receive the requested information from all devices receiving the RRR IE, then the RRR table length and RRR table fields are not needed either. However, if the requesting device expects responses from a specified set of devices, then the RRR table length and RRR table fields are present to list the addresses of those devices. The control flow using the RRR table can be illustrated in FIG. 51 .

[0335] FIG. 6 An exemplary RRR table for a device sending RRR IE 5100 according to an embodiment of the disclosure is shown. FIG. 34 The illustrated embodiment of the RRR table for a device sending RRR IE 5100 is for illustration only. FIG. 34 The scope of the disclosure is not limited to any particular implementation.

[0336] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 51 may use a RRR table for a device sending RRR IE 5100 as shown in FIG. 36 . The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 49 . The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 49 . The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 52 . FIG. 52

[0337] As shown in FIG. 52 , the method 5100 starts at step 5102. In step 5102, the method 5100 determines whether a request with a RRR IE is sent to all devices that can receive the request. In step 5102, if the method determines that the request is sent to all devices, the method 5100 sets address present = 0 in step 5108. In step 5102, if the method determines that the request is not sent to all devices, the method 5100 determines that the request with the RRR IE is sent to more than one specified device in step 5104. In step 5104, the method determines that the request is sent to more than one specified device, then in step 5110, the method sets address present = 1. In step 5104, the method determines that the request is not sent to more than one specified device, then in step 5106, the method 5100 sets address present = 0.

[0338] With reference to FIG. 5 ​The bit fields requested in the middle are similar, such as FIG. 1 Bits 1-5 of the first control octet shown indicate whether specific information is requested: if the request bit field value is 1, the corresponding information is requested; otherwise, no request is made. These bit fields are associated with requests for response time, round-trip measurement, time of flight (TOF), AoA in the bearing field, and AoA in the altitude field, respectively. Bits 6-7 can be reserved for future use to request other information.

[0339] use FIG. 52 The structure specified in the document allows for the use of multiple RRR IEs in a broadcast message if the device requests different sets of information from different destinations, with different RRR IEs used to exchange different sets of requested information.

[0340] FIG. 6 Another exemplary modified ranging result request IE (RRR IE) with a control octet 5200 is shown according to an embodiment of the present disclosure. FIG. 34 The embodiment shown, which has a modified ranging result request IE (RRR IE) with a control octet 5200, is for illustrative purposes only. FIG. 34 This disclosure is not intended to limit the scope to any particular implementation.

[0341] In one embodiment, such as FIG. 52 The electronic device 501 shown (e.g., such as...) FIG. 50 The figures 101-103 and 111-116 shown can be used as follows: FIG. 53 The illustrated modified ranging result request IE (RRRIE) has a control octet 5200. Electronic device 501 can be as follows: FIG. 53 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 53 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 5 As shown.

[0342] The address type, i.e., a 2-byte or 8-byte address, can be specified by `DstAddrMode` in `MCPS-DATA.request`. However, if the address type cannot be specified in this way, one of the reserved bits can be used to indicate the address type. Therefore, the content field format of RRR IE becomes... FIG. 1 While each element of the RRR table remains consistent with... FIG. 53 The same as shown.

[0343] The address type field is valid when the address present field value is 1 and the RRR table is present. The address type field can indicate whether a 2-octet short address or an 8-octet extended address is used in the RRR table: if the address type field value is 1, a 2-octet short address is used in the RRR table, otherwise an 8-octet extended address is used in the RRR table.

[0344] FIG. 6 An exemplary revised ranging result request IE (RRR IE) with ranging control bits 5300 according to embodiments of the application is shown. FIG. 34 The illustrated embodiment of the revised ranging result request IE (RRR IE) with ranging control bits 5300 is for illustration only. FIG. 34 The scope of the disclosure is not limited to any particular implementation.

[0345] In one embodiment, as FIG. 49 illustrated, electronic device 501 (e.g., 101-103 and 111-116 as FIG. 53 illustrated) can use a revised ranging result request IE (RRR IE) with ranging control bits 5300 as FIG. 50 illustrated. Electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as FIG. 53 illustrated. Electronic device 501 can also be implemented as an initiator or responder as FIG. 54 illustrated. Electronic device 501 can also be implemented as a controller or controller as FIG. 54 illustrated.

[0346] If the ranging process is not fixed by an in-band or out-of-band coordination process before the ranging starts, the two reserved bits in FIG. 54 may also be used to indicate the status of the RFRAME transmitting the RRR IE. Specifically, the revised RRR IE content field format can be found in FIG. 5 while the elements of the RRR table remain the same as in FIG. 1 . The values of the ranging control information field are shown in Table 3 below.

[0347] Table 3 Values of the ranging control information field in the RRR IE

[0348]

[0349] FIG. 54 The revised RRR IE with the ranging control information field specified in Table 3 as illustrated in can achieve the same functionality as the RCDT IE for unicast ranging. In addition, the revised RRR IE can also be used to request information for multi-node ranging and control the ranging process, e.g., one-to-many, or many-to-many.

[0350] FIG. 6 An exemplary revised ranging report IE (RR IE) with one control octet 5400 is shown in accordance with an embodiment of the present disclosure. In FIG. 34 the embodiment of the revised ranging report IE (RR IE) with one control octet 5400 shown in FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0351] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 38 may use a revised ranging report IE (RR IE) with one control octet 5400 as shown in FIG. 54 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 54 The electronic device 501 can also be implemented as an initiator or responder as shown in FIG. 55 The electronic device 501 can also be implemented as a controller or controller as shown in FIG. 55 FIG. 55

[0352] The ranging report IE (RR IE) introduced in the foregoing embodiments can be used to send ranging related measurements to different devices. In FIG. 5 each element of the ranging report IE (RR IE), there can be one control octet to indicate the presence of the reported information to a specific ranging device. If the same set of information needs to be reported to different devices, one control octet can be used to indicate the reported information, which can apply to all devices receiving the IE. The number of control octets needed is reduced from the number of destinations to one. FIG. 1 An exemplary content field format for the revised RR IE is shown in FIG. 55 The elements or rows of the content field format are shown in

[0353] FIG. 6 Exemplary elements / rows in a RR table 5500 in accordance with an embodiment of the present disclosure are shown. FIG. 34 The embodiment of the elements / rows in the RR table 5500 shown is for illustration only. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0354] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 55 may use a revised ranging report IE (RR IE) with one control octet 5400 as shown in FIG. 54 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 56 ​​The elements / rows in the RR table 5500 shown. The electronic device 501 can be one of the electronic devices in at least one of the group 1 or group 2 shown. The electronic device 501 can also be implemented as a FIG. 55 starter or responder as shown. The electronic device 501 can also be implemented as a controller or controller as shown. FIG. 55 FIG. 53

[0355] The first bit of the control octet, the address present field, is used to indicate whether the address field is present in each element of the RR table as shown in FIG. 56 : if the address present field value is 1, the address field of the RRR table element is present, otherwise it is not. Bits 1-5 are the report present fields that indicate whether certain information is present in the elements of the RR table: if the report present field is 1, the corresponding information is present in each element of the RR table, otherwise it is not. The 6th bit of the control octet is used to indicate whether this ranging report is transmitted in an RFRAME or in a deferred data message: if the value is zero, the RR IE is embedded in an RFRAME, otherwise it is transmitted in a deferred data message.

[0356] The address type, i.e., 2 octet or 8 octet address, can be specified by the DstAddrMode of the MCPS-DATA.request. However, if the address type cannot be specified in this manner, the reserved bits in FIG. 56 may be used to indicate the address type. Thus, the content field format of the RR IE becomes FIG. 56 while each element of the RR table still remains the same as shown in FIG. 5 .

[0357] The address type field is valid when the address present field value is 1. The address type field can indicate whether the 2 octet short address or the 8 octet extended address is used in the RR table: if the address type field value is 1, the 2 octet short address is used in the RR table, otherwise the 8 octet extended address is used in the RR table.

[0358] In FIG. 1 , the RX to TX response time field is a 2 octet field with the format as shown in FIG. 56 ​​The time difference between the time of reception of the RFRAME requesting the response time and the time of transmission of the responding RFRAME most recently received from the particular source, as indicated in the RRR IE. If the delay mode field value is zero, the RR IE reporting the response time is embedded in the responding RFRAME. If the delay mode field value is 1, the RR IE is embedded in a delay data message, and the response time delivered is associated with the RFRAME most recently transmitted prior to this data message. The TX to RX round trip time field is the time difference between the time of transmission of the RFRAME initiating the round trip measurement and the time of reception of the responding RFRAME completing the round trip measurement. The TOF field contains the time of flight estimate.

[0359] The reference for the time values, i.e., response time, round trip time, and TOF, is the RMARKER. The time values are all unsigned integer time values, with the time unit specified as the ranging counter time unit in IEEE 802.15.4z.

[0360] The AoA azimuth field, if present, reports the estimated angle of arrival in the azimuth field of the received RFRAME with the RRR IE requesting the AoA for the azimuth field. The AoA elevation field, if present, reports the estimated angle of arrival in the elevation field of the received RFRAME with the RRR IE requesting the AoA for the elevation field. The above fields reporting the AoA contain unsigned integers. The unit for the AoA azimuth is 2 -16 times 360 degrees, while the unit for the AoA elevation is 2 -16 times 180 degrees.

[0361] FIG. 6 Another exemplary revised ranging report IE (RR IE) with one control octet 5600 according to embodiments of the present disclosure is shown. In this example, the revised ranging report IE (RR IE) with one control octet 5600 is shown as being used in a ranging request (RREQ) 5500. FIG. 34 The embodiment of the revised ranging report IE (RR IE) with one control octet 5600 shown in FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0362] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 57 may use a revised ranging report IE (RR IE) with one control octet 5600 as shown in FIG. 57 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 57 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 5 The electronic device 501 can also be implemented as a initiator or responder as shown in FIG. 1 The electronic device 501 can also be implemented as a controller or controller as shown inFIG. 57 shown.

[0363] FIG. 6 An exemplary revised ranging request and report control (RRRC) IE with one control octet 5700 is shown in accordance with an embodiment of the present disclosure. FIG. 34 The embodiment of the revised ranging request and report control (RRRC) IE with one control octet 5700 shown is for illustration only. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0364] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 57 may use a revised ranging request and report control (RRRC) IE with one control octet 5700 as shown in FIG. 55 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 45 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 46 The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 58 The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 58

[0365] The revised RR IE and the RR IE can be merged into a RRRC IE with a single control octet. The content field format of the revised RRRC IE is shown in FIG. 58 while each element of the RRRC table remains the same as in FIG. 5 The definition of the fields and the meaning of their values are the same as in

[0366] and FIG. 1 FIG. 58 Note that the control bit in the first octet can be applied to each element of the RRRC table.

[0367] The request / report indicator field is used to indicate whether this RRRC IE is used to request or report certain information: if the value is 1, this RRRC IE requests certain information, otherwise it is used to report certain information, and vice versa. If the RRRC IE is used for request, there can be no fields for measurement report in the RRRC table.

[0368] The address present field is used to indicate the presence of the address field in each element of the RRRC table: if the value is 1, each element of the RRRC table can contain the address field, otherwise it can not. If the RRRC IE is used for request and the field value of address present is zero, the RRRC table length and the RRRC table are not needed. ​​

[0369] If RRRC IE is used for a request, bits 2-6 indicate the request for certain information: if the bit field value is 1, the corresponding information is requested; otherwise, it is not. If RRRC IE is used for reporting, bits 2-6 indicate the reporting of certain information: if the bit field value is 1, the corresponding information is reported in the RRRC table.

[0370] The 7th bit of the control octet indicates the delay mode. If RRRCIE is used for a request, the delay mode field value allows the receiving device to know whether to embed the ranging report in an RFRAME or a delayed data message: if the value is 1, the ranging report can be sent using a delayed data message; otherwise, the ranging report can be embedded in an RFRAME. If RRRCIE is used for a report, the delay mode field value indicates whether the report is delayed or transmitted in an RFRAME: if the value is 1, the ranging report is sent in a delayed data message; otherwise, it is embedded in an RFRAME.

[0371] Other semantics used for the distance result request IE (RRR IE) and distance report IE (RR IE) are not excluded in this disclosure. In this embodiment, RRR IE is renamed to distance request measurement and control IE (RRMC IE), and RR IE is renamed to distance measurement information IE (RMI IE).

[0372] FIG. 6 An exemplary RRMC IE (or RRR IE) with a ranging control information field 5800 according to an embodiment of this disclosure is shown. FIG. 34 The example of an RRMC IE (or RRR IE) with a ranging control information field 5800 shown is for illustrative purposes only. FIG. 34 This disclosure is not intended to limit the scope to any particular implementation.

[0373] In one embodiment, such as FIG. 58 The electronic device 501 shown (e.g., such as...) FIG. 50 As shown in 101-103 and 111-116, it can be used with the following... FIG. 53 The ranging control information field 5800 shown is RRMC IE (or RRR IE). Electronic device 501 can be as follows: FIG. 58 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 50 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... FIG. 59 As shown.

[0374] like FIG. 59The length of the RRMC IE content field determines the RRMC table length and the presence of the RRMC table field as shown: if the length is one octet, there is no RRMC table length and RRCM table; if the length is more than one octet, there is RRMC table length and RRCM table. The RRMC table length is equal to the number of row elements in the RRMC table, which is the same as the number of devices requested to receive. The row element format of the RRMC table remains the same as FIG. 59 .

[0375] If the RRMC IE is transmitted in a unicast frame, the destination address is already specified by the MHR. Therefore, the RRMC table length and RRMC table field are not needed. When the RRMC IE is transmitted in a broadcast message, the device sending the IE intends to request all devices receiving the RRMC IE, then the RRMC table length and RRMC table field are not needed either. However, if the requesting device expects responses from a specified set of devices, the RRMC table length and RRMC table field are present to list the addresses of those devices.

[0376] The fields requesting different information, i.e., bits 0-4, remain the same as FIG. 59 shown. The value of the "ranging control information" field is shown in Table 3, which is used to indicate the use of RFRAME. With the content field format as FIG. 59 shown, if a device requests different sets of information from different destinations, multiple RRMC IEs can be used in a broadcast message, where different RRMC IEs are used to exchange different sets of requests.

[0377] In FIG. 5 , the address type, i.e., 2 octet or 8 octet address, can be specified by the DstAddrMode of the MCPS-DATA.request.

[0378] For one-to-many SS-TWR, the ranging exchange is initiated by the initiator, where the ranging request measurement and control IE (RRMC IE) is embedded in the ranging initiation message sent to multiple responders. The ranging control information field of the RRMC IE is set to zero according to Table 3, which is indicated by the RRMC(0) IE in FIG. 1 . The response time request field of the RRMC IE is set to 1, which requests the response time of the ERDEV. On the responder side, the MCPS-DATA.indication delivering the RRMC(0) IE informs the next higher layer to initiate the ranging response message, which transmits the ranging measurement information IE (RMI IE) together with the response time and RRMC IE. According to Table 3, the ranging control information field of the RRMC IE in the response RFRAME is set to 1, which is indicated by the RRMC(1) IE in FIG. 59The RRMC(1) IE in the message indicates.

[0379] For scheduled-based multi-node ranging, the responders transmit the ranging response messages in their assigned time slots, while for contention-based multi-node ranging, the responders contend in the time slots of the ranging response phase. After acquiring the ranging response messages, the initiator has the complete information to compute the TOF to different responders.

[0380] FIG. 6 An exemplary message sequence chart 5900 for one-to-many SS-TWR is shown in accordance with an embodiment of the present disclosure. FIG. 34 The illustrated embodiment of the message sequence chart 5900 is for illustration only. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0381] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 59 may use the message sequence chart 5900 as shown in FIG. 59 The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in FIG. 60 The electronic device 501 can be implemented as an initiator or a responder as shown in FIG. 60 The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 60 FIG. 5

[0382] FIG. 1 A message sequence chart for one-to-many SS-TWR between one initiator and N responders (i.e., responder-1, responder-2,..., responder-N) is shown, where the ranging response messages from different responders are scheduled to be transmitted in order. At the point labeled (R), the initiator has enough information to compute the ranging results for the corresponding pairs. Different responders can have different ranging result requests.

[0383] In FIG. 60 for example, responder-N requests the TX to RX round trip time, i.e., the round trip time request field value of the RRMC IE in the ranging response message is set to 1, while responder-1 directly requests the ranging result, i.e., the TOF request field value of the RRMC IE in the ranging response message is set to 1. The measurement report is completed by the final data message broadcast by the initiator transmitting multiple RMI IEs, where the destination of the measurement report can be distinguished by the address field of the RMI IEs. Note that if multiple responders request the same set of information (e.g., TOF), the measurement report can be implemented by one RMI IE in the final data message.

[0384] ​​FIG. 6 An example message sequence chart 6000 for one-to-many DS-TWR is shown according to embodiments of the present disclosure: there is no ranging result request from the initiator. FIG. 34 The illustrated embodiment of the message sequence chart 6000 is for illustration only. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0385] In one embodiment, the electronic devices 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 6000 as shown. The electronic devices 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown. The electronic devices 501 can also be implemented as the initiator or the responder as shown. The electronic devices 501 can also be implemented as the controller or the controller as shown. FIG. 60 FIG. 58 FIG. 59 FIG. 61 FIG. 61 FIG. 61

[0386] For one-to-many DS-TWR, a three-way ranging method can be considered in order to reduce the number of transmissions. The ranging exchange is initiated by the initiator, where the RRMC IE is embedded in the ranging initiation message and sent to multiple responders. According to Table 3, the ranging control information field value in the RRMC IE is 2, which is indicated by the RRMC(2) IE in FIG. 5

[0387] Once the responder receives the ranging initiation message, the responder can form a ranging response message, which contains the RRMC IE to initialize the second round trip measurement. According to Table 3, the ranging control information field value in the RRMC IE is set to 3, which is indicated by the RRMC(3) IE in FIG. 1

[0388] FIG. 61 ​​​​​​​​A message sequence chart for one-to-many DS-TWR is shown between one initiator and N responders (i.e., responder-1, responder-2,... responder-N), where ranging response messages from different responders are scheduled to be transmitted in sequence. At the point labeled (R), the responders have enough information to compute the ranging results. If the fields for the reply time request, round trip measurement request, and TOF request in the RRMC IE in the ranging initiation message are set to zero, the responders can not send back the ranging results or related time measurements to the initiator.

[0389] FIG. 6 An example message sequence chart 6100 for one-to-many DS-TWR is shown according to embodiments of the present disclosure: there is no ranging result request from the initiator with delay mode. FIG. 34 The embodiments of the message sequence chart 6100 shown are for illustration. Other embodiments of the message sequence chart 6100 can be used without departing from the scope of the present disclosure. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0390] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 6100 as shown. The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 1. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 1. The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 1. FIG. 61 FIG. 62 FIG. 62 FIG. 62 FIG. 5 FIG. 1

[0391] FIG. 62 A message sequence chart for one-to-many DS-TWR is shown when the delay mode field value is set to 1 in the ARC IE of the RCM. Thus, the initiator sends the first round trip time and the second reply time to the responders in a delayed data frame via the RMI IE, where the delay mode field of the RMI IE is set to 1.

[0392] FIG. 6 An example message sequence chart 6200 for one-to-many DS-TWR is shown according to embodiments of the present disclosure: request for the first reply time and the second round trip time from the initiator. FIG. 34 The embodiments of the message sequence chart 6200 shown are for illustration. Other embodiments of the message sequence chart 6200 can be used without departing from the scope of the present disclosure. FIG. 34 The scope of the present disclosure is not limited to any particular implementation.

[0393] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 6200 as shown. The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 1. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 1. The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 1. FIG. 62 FIG. 63 ​​​​​​​The figures 101-103 and 111-116 shown can be used as follows: FIG. 63 The message sequence diagram 6200 is shown. Electronic device 501 can be as follows: FIG. 63 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: FIG. 5 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... ​ As shown.

[0394] exist ​ In this process, the initiator requests the first response time and the second round-trip time at the responder by setting the response time request and round-trip time request fields to 1 in the RRMC IE of the ranging initiation message. When the RRMC(2) IE is received via MCPS-DATA.indication, the next higher layer of the responder initializes the second round-trip measurement via MCPS-DATA.request with the RRMC(3) IE. Simultaneously, the next higher layer of the responder creates an RMI IE that reports the response time of the ranging response message to the initiator. Since the initiator requests the second round-trip time from the responder, a separate data frame following the ranging transmission is used by each responder to send this information back. Therefore, the initiator is also able to calculate the TOF after the measurement reporting phase.

[0395] ​ An exemplary message sequence diagram 6300 for a one-to-many DS-TWR according to an embodiment of this disclosure is shown: a ranging result request from the initiator. ​ The embodiment of message sequence diagram 6300 shown is for illustrative purposes only. ​ This disclosure is not intended to limit the scope to any particular implementation.

[0396] In one embodiment, such as ​ The electronic device 501 shown (e.g., such as...) Figure 1 The figures 101-103 and 111-116 shown can be used as follows: Figure 63 The message sequence diagram shown is 6300. (As shown in the example...) Figure 6 As shown, electronic device 501 can be one of the electronic devices in group 1 or group 2. Electronic device 501 can also be implemented as follows: Figure 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... Figure 34 As shown.

[0397] exist Figure 63In this process, the initiator requests the ranging result (TOF) by setting the value of the TOF request field to 1 in the RRMC IE of the ranging initiation message. Therefore, the responder sends back the ranging result in separate data frames based on either time scheduling or contention (RMI IE).

[0398] In one embodiment, the RRR IE is renamed to the Ranging Request Measurement and Control IE (RRMC IE), and the RR IE is renamed to the Ranging Measurement Information IE (RMI IE).

[0399] Figure 64 An exemplary ranging response time instantaneous IE content field format 6400 according to an embodiment of the present disclosure is shown. Figure 64 The example of the instantaneous IE content field format 6400 for ranging response time shown is for illustrative purposes only. Figure 64 This disclosure is not intended to limit the scope to any particular implementation.

[0400] In one embodiment, such as Figure 5 The electronic device 501 shown (e.g., such as...) Figure 1 The figures 101-103 and 111-116 shown can be used as follows: Figure 64 The ranging response time instantaneous IE content field format 6400 is shown. Electronic device 501 can be as follows: Figure 6 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: Figure 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... Figure 34 As shown.

[0401] The Ranging Response Time Instantaneous IE (RRTI IE) transmits the response time of the response frame containing the RRTI IE relative to the frame containing the RRMC IE, where the Response Time Request field, which is the field requesting the response, is set to 1. The content fields of the RRTI IE can be formatted, such as... Figure 64 As shown.

[0402] Each element in the RRTI table can be formatted, such as Figure 65 As shown.

[0403] Figure 65 An exemplary RRTI table row element format 6500 according to an embodiment of the present invention is shown. Figure 65 The example of RRTI table row element format 6500 shown is for illustrative purposes only. Figure 65 This disclosure is not intended to limit the scope to any particular implementation.

[0404] In one embodiment, such as Figure 5The electronic device 501 (e.g., as Figure 1 The RRTI table row element format 6500 as Figure 65 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as Figure 6 The electronic device 501 can also be implemented as an initiator or responder as Figure 34 The electronic device 501 can also be implemented as a controller or controller as Figure 34

[0405] Figure 64 The address present field in the RRTI table is used to indicate the presence of the address field in each row element of the RRTI table as Figure 65

[0406] The RRTI table length field represents the number of row elements in the RRTI table. The RRTI table stacks the response time to different RDEVs.

[0407] The RX to TX response time field is the time difference between the reception time of the most recently received RFRAME that delivered a RRMC IE with the response time request field as 1 and the transmission time of the responding RFRAME that contains the RRTI IE. The reference for the above time value is the RMARKER. The time unit follows the ranging counter time unit in the IEEE 802.15.4z specification, while other appropriate time units are not excluded.

[0408] The RRTI IE can be used to report the response time in a RFRAME in response to multiple RDEVs that requested the response time through a RRMC IE with the response time request field as 1. Figure 65 The address field in the RRTI table can be used to specify the identity of the RDEV. For ranging between one initiator and one responder, the address field can be omitted because the address field is specified by the destination address field of the MAC header. For multi-node ranging, the address field can not exist if the response times to different RDEVs are stacked in a pre-agreed order.

[0409] For SS-TWR with delayed response time results, the ranging exchange is initiated by the next higher layer that invokes the MCPS-DA.request primitive to send a ranging frame that includes a ranging request measurement and control IE (RRMC IE) that requests ranging response time information. The ranging control information field is set according to Table 3.

[0410] ​​The response ranging frame completes the round-trip measurement, and the MCPS-DATA.confirm primitive provides the initiating side timestamp defining the round-trip time. On the responding side, the MCPS-DATA.indication primitive provides the responding side timestamp defining the response time of the round-trip measurement. This response time is transmitted to the initiating side in the ranging measurement information IE (RMI IE) carried in subsequent messages.

[0411] Figure 66 An exemplary message sequence diagram 6600 of an SS-TWR with delayed response time results according to an embodiment of the present disclosure is shown. Figure 66 The embodiment of message sequence diagram 6600 shown is for illustrative purposes only. Figure 66 This disclosure is not intended to limit the scope to any particular implementation.

[0412] In one embodiment, such as Figure 5 The electronic device 501 shown (e.g., such as...) Figure 1 The figures 101-103 and 111-116 shown can be used as follows: Figure 66 The message sequence diagram 6600 is shown. Electronic device 501 can be as follows: Figure 6 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: Figure 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... Figure 34 As shown.

[0413] Figure 66 A message sequence diagram for the above exchange is shown, where RRMC(0)IE indicates the RRMC IE carried with a ranging control information field value of 0. At the point marked (R), the initiator has sufficient information to calculate the TOF between the two devices.

[0414] Figure 67 An exemplary message sequence diagram 6700 for an SS-TWR with embedded response time is shown according to an embodiment of the present disclosure. Figure 67 The embodiment of message sequence diagram 6700 shown is for illustrative purposes only. Figure 67 The scope of this invention is not limited to any particular embodiment.

[0415] In one embodiment, such as Figure 5 The electronic device 501 shown (e.g., such as...) Figure 1 The figures 101-103 and 111-116 shown can be used as follows: Figure 67 The message sequence diagram 6700 is shown. Electronic device 501 can be as follows: Figure 6One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: Figure 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... Figure 34 As shown.

[0416] Figure 67 A message sequence diagram for the aforementioned exchange is shown, where RRMC(0)IE indicates the RRMC IE carried with a ranging control information field value of 0. The communication of the RPRT IE, shown in the dashed box, can occur at any convenient time before the ranging exchange is initiated, or it can be out-of-band. At the point marked (R), the initiating end has sufficient information to calculate the distance between the two devices.

[0417] DS-TWR essentially involves completing the SS-TWR exchange or combination results initiated at either end. A DS-TWR exchange is initiated by the next higher layer sending a ranging data frame carrying the RRMC (Range Control Information) field, which is set according to TALE 3. This frame and acknowledgment define the first round-trip measurement, while the RRMC IE delivery in the MCPS-DATA.indication primitive informs the next higher layer to initiate a second round-trip measurement by sending an RFRAME in the other direction.

[0418] The RMI IE includes an RRMC IE with a ranging control information field set according to Table 3 to indicate that this is a continuation of the exchange. The fields for response time request and round-trip measurement request have a value of 1 for requesting the response time and the first round-trip measurement. Confirmation of this message completes the second round-trip measurement. Subsequent messages from the initiator transmit the first round-trip time measurement and the response time for the second round-trip time measurement in the RMI IE.

[0419] Figure 68 An exemplary message sequence diagram 6800 of a DS-TWR with delayed response time results according to an embodiment of the present disclosure is shown. Figure 68 The embodiment of message sequence diagram 6800 shown is for illustrative purposes only. Figure 68 The scope of this invention is not limited to any particular implementation.

[0420] In one embodiment, such as Figure 5 The electronic device 501 shown (e.g., such as...) Figure 1 The figures 101-103 and 111-116 shown can be used as follows: Figure 68 The message sequence diagram 6800 is shown. Electronic device 501 can be as follows: Figure 6 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows:Figure 34 The electronic device 501 can also be implemented as a responder or responder as shown in Figure 34 .

[0421] Figure 68 An exemplary message sequence chart 6900 for DS-TWR with three messages is shown. At the point labeled (R), the responder has enough information to compute the distance between the two devices. Subsequent reporting of the ranging result to the initiator in an RMI IE depends on the value of the TOF request field in the initiating RRMC IE.

[0422] Figure 69 An exemplary message sequence chart 6900 for DS-TWR with three messages is shown. At the point labeled (R), the responder has enough information to compute the distance between the two devices. Subsequent reporting of the ranging result to the initiator in an RMI IE depends on the value of the TOF request field in the initiating RRMC IE. Figure 69 The embodiments of the message sequence chart 6900 are for illustration only. Figure 69 The scope of the present disclosure is not limited to any particular implementation.

[0423] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in Figure 5 may use the message sequence chart 6900 as shown. The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in Figure 1 . The electronic device 501 can also be implemented as a responder or responder as shown in Figure 69 . The electronic device 501 can also be implemented as a controller or controller as shown in Figure 6 . Figure 34 Figure 34 The embodiments of the message sequence chart 6900 are for illustration only.

[0424] To embed timestamp information into the RFRAME, DS-TWR with three messages requires the initiator to be able to embed the reply time as part of completing the second round-trip measurement. Referring to the message sequence chart of Figure 69 DS-TWR is initiated by an RFRAME carrying a RRMC IE with ranging control information fields set according to Table 3.

[0425] In this case, the initiator RRMC IE with a TOF request field value of 0 indicates that the initiator does not require reporting of the ranging result. The responder completes the first round-trip measurement and initiates the second measurement with an RFRAME carrying a RRMC IE with ranging control information fields set according to Table 3 to indicate that this is a continuation of the exchange.

[0426] ​The response time request and round-trip measurement request fields of the aforementioned RRMC IE are set to 1, indicating a request for the first round-trip measurement and the response time for the second round-trip measurement. The original initiator completes the exchange by sending a final RFRAME carrying the first round-trip time measurement in the RMI IE and the response time for the aforementioned second round-trip measurement in the RRTI IE.

[0427] At point (R), the responding end has sufficient information to calculate the distance between the two devices. If the initiator of the ranging exchange desires the result, it can request the result in the TOF request field of the initiating RRMC IE, and request the responding end to transmit the result in a subsequent RMI IE message at the end of the exchange, such as... Figure 68 As shown.

[0428] For a one-to-many SS-TWR, ranging exchange is initiated by the initiator, where the ranging request measurement and control IE (RRMCIE) is embedded in a ranging initiation message broadcast to multiple responders. The ranging control information field of the RRMCIE can be set to zero according to Table 3; this field is determined by… Figure 65 The RRMC(0)IE instruction in the middle.

[0429] The response time request field of the RRMC IE is set to 1, requesting the response time of the ERDEV. On the responder side, the MCPS-DATA.indication of the RRMC(0) IE informs the next higher layer to initiate a ranging response message. Using the RequestRrti used to set and insert the RRTI IE, the MCPS-DATA.request at the responder also transmits the RRMC IE to control the ranging process and send the request.

[0430] Figure 70 An exemplary message sequence diagram 7000 for a one-to-many SS-TWR is shown according to an embodiment of the present disclosure. Figure 70 The embodiment of message sequence diagram 7000 shown is for illustrative purposes only. Figure 70 This disclosure is not intended to limit the scope to any particular implementation.

[0431] In one embodiment, such as Figure 5 The electronic device 501 shown (e.g., such as...) Figure 1 The figures 101-103 and 111-116 shown can be used as follows: Figure 70 The message sequence diagram 7000 is shown. Electronic device 501 can be as follows: Figure 6 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: Figure 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as...Figure 34 as shown.

[0432] The ranging control information field in response RFRAME in response to RRMC IE can be set to 1, which is indicated by Figure 70 RRMC(1) IE in the response RFRAME is sent to the initiator, where the destination address in the MAC header can be the address of the initiator.

[0433] For scheduled multi-node ranging, the responders send the ranging response messages in their allocated time slots, while for contention-based multi-node ranging, the responders contend in the time slots of the ranging response phase. After obtaining the ranging response messages, the initiator has the complete information to calculate the TOF to different responders.

[0434] Figure 70 A message sequence chart for one-to-many SS-TWR between one initiator and N responders (i.e., responder-1, responder-2, …, responder-N) is shown, where the ranging response messages from different responders are scheduled to be transmitted in sequence. At the point labeled (R), the initiator has enough information to calculate the ranging results for the corresponding pairs. Different responders can have different ranging result requests.

[0435] In Figure 70 , for example, responder-N requests the TX-to-RX round trip time, i.e., the round trip time request field value of RRMC IE in the ranging response message is set to 1, while responder-1 directly requests the ranging result, i.e., the TOF request field value of RRMC IE in the ranging response message is set to 1. The measurement report is completed by the final data message broadcast by the initiator transmitting multiple RMI IEs, where the destination of the measurement report can be distinguished by the address field of the RMI IEs. Note that if multiple responders request the same set of information (e.g., TOF), the measurement report can be implemented by one RMI IE in the final data message.

[0436] For one-to-many DS-TWR, a three-way ranging method can be considered in order to reduce the number of transmissions. The ranging exchange is initiated by the initiator, where the RRMC IE is embedded in the ranging initiation message and sent to multiple responders. According to Table 3, the ranging control information field value in RRMC IE can be 2, which is indicated by Figure 71 RRMC(2) IE in

[0437] Figure 71 An exemplary message sequence chart 7100 for one-to-many DS-TWR according to embodiments of the present disclosure is shown: there is no ranging result request from the initiator. Figure 71 The embodiments of the message sequence chart 7100 shown are for illustration only.Figure 71 The scope of the disclosure is not limited to any particular implementation.

[0438] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 7100 as shown in FIG. 7. The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in FIG. 1. The electronic device 501 can also be implemented as an initiator or a responder as shown in FIG. 1. The electronic device 501 can also be implemented as a controller or a controller as shown in FIG. 1. Figure 5 Figure 1 Figure 71 Figure 6 Figure 34 Figure 34

[0439] Once the responder receives the ranging initiation message, the responder can form a ranging response message that contains a RRMC IE to initialize a second round-trip measurement. According to Table 3, the ranging control information field value in the RRMC IE can be 3, which is indicated by the RRMC(3) IE in Figure 71

[0440] Figure 71

[0441] Figure 72 ​​​​​​​​An exemplary message sequence chart 7200 for one-to-many DS-TWR is shown, according to an embodiment of the disclosure: request for first reply time and second round trip time from initiator. Figure 72 The embodiment of the message sequence chart 7200 shown is for illustration only. Figure 72 The scope of the present disclosure is not limited to any particular implementation.

[0442] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in Figure 5 may use the message sequence chart 7200 as shown in Figure 1 The electronic device 501 can be one of the electronic devices of at least one of Group 1 or Group 2 as shown in Figure 72 The electronic device 501 can also be implemented as an initiator or responder as shown in Figure 6 The electronic device 501 can also be implemented as a controller or controller as shown in Figure 34 Figure 34

[0443] In Figure 72 , the initiator requests the first reply time and the second round trip time at the responder by setting the reply time request and round trip time request fields to 1 in the RRMC IE of the ranging initiation message. When the RRMC(2) IE is received through MCPS-DATA.indication, the next higher layer of the responder initializes the second round trip measurement via MCPS-DATA.request with the RRMC(3) IE. At the same time, the RequestRrtiTx in MCPS-DATA.request is set to insert the RRTI IE in the response RFRAME. To send the final RFRAME, the next higher layer of the initiator sets the RequestRrti and RrtiNodeList of MCPS-DATA.request to insert the RRTI IE and also communicates the RMI IE reporting the first round trip time measurement to the MAC layer.

[0444] Since the initiator requests the second round trip time from the responder, a separate data frame after the ranging transmission is used by each responder to send this information back. Thus, the initiator is also able to calculate the TOF after the measurement report phase.

[0445] Figure 73 An exemplary message sequence chart 7300 for one-to-many DS-TWR is shown, according to an embodiment of the disclosure: ranging result request from initiator. Figure 73 The embodiment of the message sequence chart 7300 shown is for illustration only. Figure 73 The scope of the present disclosure is not limited to any particular implementation.​​

[0446] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 7300 as shown in FIG. 7. Figure 5 Figure 1 In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 7300 as shown in FIG. 7. Figure 73 Figure 6 In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 7300 as shown in FIG. 7. Figure 34 Figure 34 In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 7300 as shown in FIG. 7.

[0447] In Figure 73 , the initiator requests the ranging result, i.e., TOF, by setting the field value of TOF request to 1 in the RRMC IE of the ranging initiation message. Thus, the responder sends back the ranging result (RMI IE) in a separate data frame based on time schedule or contention, respectively.

[0448] For the case of multiple initiator to multiple initiator (M2M), the controller sends the RCM with ranging configuration to the multiple initiators and the initiators. In the case of one-to-many ranging, there is only one ranging initiation message from a single initiator in the ranging initiation phase (RIP), while multiple initiators can send the ranging initiation message in the RIP by scheduling or contention in M2M ranging. The ranging initiation message contains the RRMC IE, in which the ranging control information field value is set to 0 and the reply time request field value is set to 1.

[0449] After collecting the ranging initiation messages from different initiators, the next higher layer of the responder initiates the response RFRAME via MCPS-DATA.request, in which RequestRrtiTx and RrtiNodeList are set to insert the RRTI IE. Based on the time schedule or contention determined via the ranging configuration, the response RFRAME is sent to the initiators in the ranging response phase.

[0450] Figure 74 An exemplary message sequence chart 7400 for M2M SS-TWR according to an embodiment of the present disclosure is shown. Figure 74 The embodiments of the message sequence chart 7400 shown are for illustration only. Figure 74 The scope of the present disclosure is not limited to any particular implementation.

[0451] In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 7300 as shown in FIG. 7. Figure 5 Figure 1 In one embodiment, the electronic device 501 (e.g., 101-103 and 111-116 as shown in FIG. 1) can use the message sequence chart 7300 as shown in FIG. 7.​​​​Figure 74 The message sequence diagram 7400 is shown. Electronic device 501 can be as follows: Figure 6 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: Figure 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... Figure 34 As shown.

[0452] Figure 74 A message sequence diagram of M2MSS-TWR is shown between M initiators and N responders (i.e., initiator-1, initiator-2, ..., initiator-M and responders-1, responders-2, ..., responders-N), where the transmission of ranging initiation and ranging response messages is scheduled sequentially. Contention-based transmissions can also be performed for the ranging initiation and ranging response phases. At the point marked (R), the initiator has sufficient information to calculate the ranging result for the corresponding pair. The higher layers are responsible for ensuring that each desired response is provided at the appropriate time, allowing the MAC to send the required response at the specified time, and similarly enabling the receiver to receive any messages it needs to receive at the appropriate time.

[0453] The controller can use ARC IE and RDM IE to determine this. Figure 74 In this case, the responder does not request the ranging result. However, similar to Figure 70 The responder can also request ranging results from the initiator or request relevant time measurements to calculate the ranging results, which requires additional data frames sent from the initiator.

[0454] Figure 75 An exemplary message sequence diagram 7500 for M2M DS-TWR is shown according to an embodiment of the present disclosure. Figure 75 The embodiment of message sequence diagram 7500 shown is for illustrative purposes only. Figure 75 This disclosure is not intended to limit the scope to any particular implementation.

[0455] In one embodiment, such as Figure 5 The electronic device 501 shown (e.g., such as...) Figure 1 The figures 101-103 and 111-116 shown can be used as follows: Figure 75 The message sequence diagram 7500 is shown. Electronic device 501 can be as follows: Figure 6 One of the electronic devices in at least one of group 1 or group 2 shown. Electronic device 501 may also be implemented as follows: Figure 34 The initiator or responder shown. Electronic device 501 can also be implemented as a controller or controller, such as... Figure 34 As shown.

[0456] For M2M DS-TWR, based on the ranging configuration, multiple initiators can contend or time schedule a time slot in the ranging initiation phase to send a ranging initiation message that conveys a RRMC IE. The ranging control information field value in the RRMC IE can be 2, which is indicated by the RRMC(2) IE in Figure 75

[0457] After the ranging initiation phase, the responder forms a ranging response message that contains a RRMC IE to initialize a second round trip measurement. The ranging control information field value can be 3, which is indicated by the RRMC(3) IE in Figure 75

[0458] The ranging response message can also be sent by time scheduling or contention determined via the ranging configuration. Then, the initiator forms a final RFRAME that includes a RRTI IE to report the response time and a RMI IE to report the round trip time.

[0459] Figure 75 A message sequence chart of M2M DS-TWR between M initiators and N responders is shown, where the ranging initiation message and the ranging response message are both scheduled for transmission in sequence. At the point labeled (R), the responder has enough information to compute the ranging result. If the fields of the response time request, round trip measurement request, and TOF request in the RRMC IE in the ranging initiation message are set to zero, the responder can not send the ranging result or the related time measurement back to the initiator.

[0460] Figure 76 A flowchart of a method 7600 for secure ranging operation according to embodiments of the application that can be performed by a first network entity is shown. Figure 6 Embodiments of the method 7600 shown in Figure 6 The scope of the present disclosure is not limited to any particular implementation.

[0461] In one embodiment, an electronic device 501 (e.g., 101-103 and 111-116 as shown in Figure 5 may use the method 7600 as shown in Figure 1 The electronic device 501 can be one of the electronic devices in at least one of Group 1 or Group 2 as shown in Figure 76 The electronic device 501 can be implemented as an initiator or a responder as shown in Figure 6 The electronic device 501 can also be implemented as a controller or a controller as shown in Figure 34 The electronic device 501 can also be implemented as a controller or a controller as shown in Figure 34 The electronic device 501 can also be implemented as a controller or a controller as shown in ​​

[0462] As shown in FIG. 76, the method 7600 begins at step 7602. In step 7602, the first network entity generates a media access control (MAC) common part sublayer data request (MCPS-DATA.request) primitive including a ranging enable indicator and a ranging request measurement and control IE (RRMC IE) with a reply time request. Figure 76

[0463] In step 7604, the first network entity transmits the first MAC data including the RRMC IE to the second network entity.

[0464] In one embodiment, the RRMC IE includes a reply time request field, a round trip measurement request field, a time of flight (ToF) request field, an angle of arrival (AoA) azimuth request field, an AoA altitude request field, a ranging control information field, a reserved bit field, a RRMC table length field, and a RRMC table field.

[0465] In such an embodiment, the ranging control information field includes a value indicating that when the value is set to zero, the frame is used for a ranging initiation message for a single-sided two-way ranging (SS-TWR); when the value is set to 1, the frame is used for a ranging initiation message in response to a SS-TWR; when the value is set to 2, the frame is used for a ranging initiation message for a double-sided two-way ranging (DS-TWR); and the frame is used to continue the DS-TWR and initiate a second round trip time measurement.

[0466] In step 7606, the first network entity receives second MAC data including a ranging reply time instant IE (RRTI IE) and the RRMC IE from the second network entity.

[0467] In step 7608, the first network entity identifies a local value of a receive ranging counter (RxRangingCounter).

[0468] In one embodiment, the first network entity transmits the MCPS-DATA.request primitive from a higher layer to a MAC layer; after transmitting the first MAC data to the second network entity, transmits a MCPS-DATA.confirm primitive from the MAC layer to the higher layer including a local value of a transmit ranging counter (TxRangingCounter); and after receiving the second MAC data from the second network entity, transmits a MCPS-DATA.indication primitive from the MAC layer to the higher layer with a local value of a receive ranging counter (RxRangingCounter) and the RRMC IE.

[0469] ​In one embodiment, the first network entity generates a MCPS-DATA.request primitive including at least one ranging measurement information IE (RMI IE) having information requested by the first network entity; sends the MCPS-DATA.request primitive from a higher layer to a MAC layer; and sends first MAC data including a RRMC IE to the second network entity.

[0470] In such an embodiment, the at least one RMI IE includes an address present field, a reply time present field, a round trip measurement present field, a ToF present field, an AoA azimuth present field, an AoA elevation present field, a delay pattern field, a reserved field, an RMI list length field, and an RMI list field; the RMI list field includes an RX to Tx reply time field, a Tx to Rx round trip field, a ToF field, an AoA azimuth field, an AoA elevation field, and an address field.

[0471] While the present disclosure has been described with exemplary embodiments, various changes and modifications can be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read in the alternative unless expressly so stated.

Claims

1. A method performed by a first device in a wireless communication system, the method comprising: First Media Access Control (MAC) data is sent to multiple second devices. This first MAC data includes a first ranging request measurement and control information element (RRMC IE) with a response time request. Receive second MAC data, including the ranging response time instantaneous RRTI IE and the second RRMCIE, from at least one of the plurality of second devices, and Identify the reception time of the second MAC data. The first RRMC IE includes a response time request field, a round-trip time measurement request field, a time of flight (ToF) request field, an angle of arrival (AOA) azimuth request field, an AoA altitude request field, a distance control information field, a reserved bit field, an RRMC table length field, and an address field.

2. The method according to claim 1, further comprising: After sending the first MAC data, identify the time when the first MAC data was sent; as well as Based on the second MAC data, information for calculating the Time of Flight (ToF) to at least one of the plurality of second devices is identified.

3. The method of claim 1, wherein the address field contains at least one address, and the first RRMCIE is directed from the first device to the at least one address.

4. The method of claim 3, wherein the ranging control information field includes a value associated with the purpose of the frame: in, When the value is set to 0, the value indicates that the frame is used for the ranging initiation message of the unilateral bidirectional ranging SS-TWR. When the value is set to 1, it indicates that the frame was used in response to the SS-TWR ranging initiation message. Wherein, when the value is set to 2, the value indicates that the frame is used for a ranging initiation message in two-sided two-way ranging (DS-TWR), and When the value is set to 3, the value indicates that the frame is continuing DS-TWR and initiating a second round-trip time measurement.

5. The method according to claim 1, wherein: Send third MAC data, including at least one ranging measurement information RMI IE, to the plurality of second devices.

6. The method according to claim 5, wherein the at least one RMI IE includes an address presence field, a response time presence field, a round-trip time measurement presence field, a ToF presence field, an AoA orientation presence field, an AoA height presence field, a delay mode field, a reserved field, an RMI list length field, and an RMI list field.

7. The method of claim 6, wherein the RMI list fields include an RX to Tx response time field, a Tx to Rx round trip field, a ToF field, an AoA orientation field, an AoA height field, and an address field, and the at least one RMI IE is directed to the address field.

8. A method performed by a second device in a wireless communication system, the method comprising: Receives first media access control (MAC) data from a first device, the first MAC data including a first ranging request measurement and control information element (RRMC IE) with a response time request; as well as Send second MAC data, including the ranging response time instantaneous RRTI IE and the second RRMC IE, to the first device; and Identify the reception time of the first MAC data. The first RRMC IE includes a response time request field, a round-trip time measurement request field, a time of flight (ToF) request field, an angle of arrival (AOA) azimuth request field, an AoA altitude request field, a distance control information field, a reserved bit field, an RRMC table length field, and an address field.

9. The method according to claim 8, further comprising: After sending the second MAC data to the first device, the time of transmission of the second MAC data is identified.

10. The method of claim 8, wherein the ranging control information field includes a value associated with the purpose of the frame: in, When the value is set to 0, the value indicates that the frame is used for a ranging initiation message in unilateral two-way ranging (SS-TWR). When the value is set to 1, it indicates that the frame was used in response to the SS-TWR ranging initiation message. Wherein, when the value is set to 2, the value indicates that the frame is used for the ranging initiation message of the two-sided bidirectional ranging DS-TWR, and When the value is set to 3, the value indicates that the frame is continuing DS-TWR and initiating a second round-trip time measurement.

11. The method of claim 8, further comprising: Receive third MAC data from the first device, including at least one ranging measurement information RMI IE.

12. The method of claim 11, wherein the at least one RMI IE includes an address presence field, a response time presence field, a round-trip time measurement presence field, a ToF presence field, an AoA location presence field, an AoA height presence field, a delay mode field, a reserved field, an RMI list length field, and an RMI list field, and in, The RMI list fields include an RX to Tx response time field, a Tx to Rx round trip field, a ToF field, an AoA orientation field, an AoA height field, and an address field, and at least one RMI IE is directed to the address field.

13. A first device in a wireless communication system, the first device comprising: transceiver; as well as At least one processor is connected to the transceiver and configured to: First Media Access Control (MAC) data is sent to multiple second devices. This first MAC data includes a first ranging request measurement and control information element (RRMC IE) with a response time request. Receive second MAC data, including the ranging response time instantaneous RRTI IE and the second RRMCIE, from at least one of the plurality of second devices, and Identify the reception time of the second MAC data. The first RRMC IE includes a response time request field, a round-trip time measurement request field, a time of flight (ToF) request field, an angle of arrival (AOA) azimuth request field, an AoA altitude request field, a distance control information field, a reserved bit field, an RRMC table length field, and an address field.

Images