Secure ranging framework without PHY payload

By identifying and sending the ranging request report information elements of the scrambled timestamp sequence in the wireless communication network, safe and efficient ranging control messages are realized, solving the problem of inefficient ranging operation in wireless communication, and improving the inter-device ranging request and response process.

CN113287033BActive Publication Date: 2024-11-22SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980087850.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-12-20
Filing Date
2019-12-31
Publication Date
2024-11-22
Estimated Expiration
2039-12-31

AI Technical Summary

Technical Problem

In wireless communication networks, it is difficult for the prior art to achieve secure ranging operation without physical layer payload, especially in the ranging request and response between multiple devices, and there is a problem of inefficiency.

Method used

By identifying the Scrambled Timestamp Sequence (STS) Physical Layer Protocol Data Unit (PPDU) Format 3 (SP3) Ranging Request Report Information Element (SRRR IE) in the receiving device group in the sending device and using in-band or band The external mechanism sends a range measurement control message (RCM) to achieve safe ranging during time-scheduled ranging operations.

Benefits of technology

It improves the efficiency and security of ranging operation, reduces the number of information exchanges, adapts to the ranging request and response process between multiple devices, optimizes the use of wireless channels, and reduces the demand for battery capacity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113287033B_ABST
    Figure CN113287033B_ABST
Patent Text Reader

Abstract

A method for a transmitting device in a wireless communication system supporting ranging capability is provided. The method includes: determining at least one receiving device in a group of receiving devices participating in a ranging operation; identifying a scrambled timestamp sequence (STS) physical layer protocol data unit (PPDU) format 3 (SP3) ranging request report information element (SRRR IE) of at least one receiving device in the group of receiving devices; and sending a ranging control message (RCM) including the SRRR IE to at least one receiving device in the group of receiving devices participating in the ranging operation using an in-band mechanism or an out-of-band mechanism, wherein the RCM including the SRRR IE is sent in a time-scheduled ranging operation.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to ranging operations in wireless communication systems. In particular, secure ranging operations without physical payload in wireless communication networks are presented. Background Art

[0002] A Peer Aware Communication (PAC) network is a fully distributed communication network that allows direct communication between PAC devices (PDs). The PAC network can adopt several topologies such as mesh, star, etc. to support interaction between PDs for various services. Summary of the invention

[0003] Technical issues

[0004] Embodiments of the present disclosure provide secure ranging operations without physical layer payload in a wireless communication network.

[0005] Problem Solution

[0006] In one embodiment, a transmitting device supporting ranging capability in a wireless communication system is provided. The transmitting device includes a processor, which is configured to: determine at least one receiving device in a receiving device group that participates in a ranging operation; and identify a scrambled timestamp sequence (STS) physical layer protocol data unit (PPDU) format 3 (SP3) ranging request report information element (SRRR IE) of at least one receiving device in the receiving device group. The transmitting device also includes a transceiver operably connected to the processor, and the transceiver is configured to use an in-band mechanism or an out-of-band mechanism to send a ranging control message (RCM) including the SRRR IE to at least one receiving device in the receiving device group participating in the ranging operation, wherein the RCM including the SRRR IE is sent in a time-scheduled ranging operation. BRIEF DESCRIPTION OF THE 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 parts:

[0008] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0009] Figure 2 An example gNB according to an embodiment of the present disclosure is shown;

[0010] Figure 3 An example UE according to an embodiment of the present disclosure is shown;

[0011] Figure 4a A high-level diagram of an OFDMA transmission path according to an embodiment of the present disclosure is shown;

[0012] Figure 4b A high-level diagram of an OFDMA receive path according to an embodiment of the present disclosure is shown;

[0013] Figure 5 An example electronic device according to an embodiment of the present disclosure is shown;

[0014] Figure 6 An example many-to-many scenario according to an embodiment of the present disclosure is shown;

[0015] Figure 7 An example single-sided two-way ranging according to an embodiment of the present disclosure is shown;

[0016] Figure 8 An example bilateral two-way ranging with three messages according to an embodiment of the present disclosure is shown;

[0017] Fig. 9 shows an example ranging time of flight IE content field format according to an embodiment of the present disclosure;

[0018] Fig.10 An example ranging round trip measurement IE content field format according to an embodiment of the present disclosure is shown;

[0019] Fig.11 shows an example ranging reply time instant IE content field format according to an embodiment of the present disclosure;

[0020] Fig.12 An example ranging reply time extension IE content field format according to an embodiment of the present disclosure is shown;

[0021] Fig.13 An example ranging angle of arrival delay IE content field format according to an embodiment of the present disclosure is shown;

[0022] Fig.14 shows an example ranging control single-sided TWR IE content field format according to an embodiment of the present disclosure;

[0023] Fig.15 shows an example ranging control bilateral TWR IE content field format according to an embodiment of the present disclosure;

[0024] Fig.16 Three example security ranging PPDU formats according to embodiments of the present disclosure are shown;

[0025] Fig.17 shows an example time structure of a ranging round according to an embodiment of the present disclosure;

[0026] Fig.18 shows example ranging device terminology (controller and controlled) according to an embodiment of the present disclosure;

[0027] Fig.19 An example ranging round structure according to an embodiment of the present disclosure is shown;

[0028] Fig. 20 shows an example ranging request measurement and control IE content field format according to an embodiment of the present disclosure;

[0029] Fig.21 shows an example RRMC table row element format according to an embodiment of the present disclosure;

[0030] Fig. 22 An example ranging measurement information IE content field format according to an embodiment of the present disclosure is shown;

[0031] Fig.23 shows an example RMI table row element format according to an embodiment of the present disclosure;

[0032] Fig.24 An example NHD ranging round structure according to an embodiment of the present disclosure is shown;

[0033] Fig.25 An example NHD ranging round structure with a request exchange period according to an embodiment of the present disclosure is shown;

[0034] Fig.26 shows an example Angle of Arrival NHD Ranging Request IE content field format according to an embodiment of the present disclosure;

[0035] Fig. 27 Another example Angle of Arrival NHD Ranging Request IE content field according to an embodiment of the present disclosure is shown;

[0036] Fig.28 shows another example Angle of Arrival NHD Ranging Request IE content field according to an embodiment of the present disclosure;

[0037] Fig.29 shows an example Angle of Arrival NHD Ranging Request IE Content field format including one or more requests according to an embodiment of the present disclosure;

[0038] Fig.30 Another example Angle of Arrival NHD Ranging Request IE content field format including one or more requests according to an embodiment of the present disclosure is shown;

[0039] Fig.31 shows an example reply time NHD ranging request IE content field format according to an embodiment of the present disclosure;

[0040] Fig.32 Another example reply time NHD ranging request IE content field format according to an embodiment of the present disclosure is shown;

[0041] Fig.33 Another example reply time NHD ranging request IE content field format according to an embodiment of the present disclosure is shown;

[0042] Fig.34 shows an example reply time NHD ranging request IE content field format including one or more requests according to an embodiment of the present disclosure;

[0043] Fig.35 Another example reply time NHD ranging request IE content field format including one or more requests according to an embodiment of the present disclosure is shown;

[0044] Fig.36 An example round trip measurement NHD ranging request IE content field format according to an embodiment of the present disclosure is shown;

[0045] Fig.37 shows an example round trip measurement NHD ranging request IE according to an embodiment of the present disclosure;

[0046] Fig.38 shows an example round trip measurement NHD ranging request IE content field according to an embodiment of the present disclosure;

[0047] Fig.39 An example round trip measurement NHD ranging request IE content field format including one or more requests according to an embodiment of the present disclosure is shown;

[0048] Fig.40 Another example round trip measurement NHD ranging request IE content field format including one or more requests according to an embodiment of the present disclosure is shown;

[0049] Fig.41 shows an example message exchange diagram of NHD ranging (multicast SS-TWR) according to an embodiment of the present disclosure;

[0050] Fig.42a shows an example message sequence chart for NHD ranging (multicast SS-TWR) utilizing the next higher layer according to an embodiment of the present disclosure;

[0051] Figure 42b shows an example message sequence chart for NHD ranging (multicast SS-TWR) utilizing the next higher layer according to an embodiment of the present disclosure;

[0052] Fig.43 shows an example message exchange diagram of NHD ranging (multicast DS-TWR) according to an embodiment of the present disclosure;

[0053] Fig.44a shows an example message sequence chart for NHD ranging (multicast DS-TWR) utilizing the next higher layer according to an embodiment of the present disclosure;

[0054] Figure 44b shows an example message sequence chart for NHD ranging (multicast DS-TWR) utilizing the next higher layer according to an embodiment of the present disclosure;

[0055] Fig.45 shows an example NHD ranging request report IE content field according to an embodiment of the present disclosure;

[0056] Fig.46 shows an example NHD ranging request report IE content field according to an embodiment of the present disclosure;

[0057] Fig.47 shows an example NHD ranging request report IE content field with a ToF request field according to an embodiment of the present disclosure;

[0058] Fig.48 shows an example NHD ranging request report IE content field with an NRRR table according to an embodiment of the present disclosure;

[0059] Fig.49a An example message sequence chart of NHD ranging (multicast SS-TWR) with request exchange by NRRR IE according to an embodiment of the present disclosure is shown;

[0060] Fig.49b An example message sequence chart of NHD ranging (multicast SS-TWR) with request exchange by NRRR IE according to an embodiment of the present disclosure is shown;

[0061] Fig.50a An example message sequence chart of NHD ranging (multicast DS-TWR) with request exchange by NRRR IE according to an embodiment of the present disclosure is shown;

[0062] Fig.50b An example message sequence chart of NHD ranging (multicast DS-TWR) with request exchange by NRRR IE according to an embodiment of the present disclosure is shown;

[0063] Fig.51a An example message sequence chart of SP3 one-to-many SS-TWR according to an embodiment of the present disclosure is shown;

[0064] Fig.51b An example message sequence chart of SP3 one-to-many SS-TWR according to an embodiment of the present disclosure is shown;

[0065] Fig.52a An example message sequence chart of SP3 one-to-many DS-TWR according to an embodiment of the present disclosure is shown;

[0066] Fig.52bshows an example message sequence chart of SP3 one-to-many DS-TWR according to an embodiment of the present disclosure; and

[0067] Fig.53 A flow chart of a method for secure ranging operation according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0068] Best Mode for Carrying Out the Invention

[0069] In one embodiment, a transmitting device in a wireless communication system supporting ranging capability is provided. The transmitting device includes a processor, the processor being configured to: determine at least one receiving device in a receiving device group participating in a ranging operation; and identify a ranging request report information element (SRRR IE) for identifying a scrambled timestamp sequence (STS) physical layer protocol data unit (PPDU) format 3 (SP3) for at least one receiving device in the receiving device group. The transmitting device also includes a transceiver operably connected to the processor, the transceiver being configured to send a ranging control message (RCM) including the SRRR IE to at least one receiving device in the receiving device group participating in the ranging operation using an in-band mechanism or an out-of-band mechanism, wherein the RCM including the SRRR IE is sent in a time-scheduled ranging operation.

[0070] In another embodiment, a receiving device in a wireless communication system supporting ranging capability is provided. The receiving device includes a transceiver, which is configured to receive a ranging control message (RCM) including a scrambled timestamp sequence (STS) physical layer protocol data unit (PPDU) format 3 (SP3) ranging request report information element (SRRR IE) from at least one transmitting device in a group of transmitting devices participating in a ranging operation using an in-band mechanism or an out-of-band mechanism, wherein the RCM including the SRRRIE is sent in a time-scheduled ranging operation. The receiving device also includes a processor operably connected to the transceiver, the processor being configured to: determine at least one transmitting device in the group of transmitting devices participating in the ranging operation; and identify the SRRR IE of at least one transmitting device in the group of transmitting devices.

[0071] In yet another embodiment, a method for a transmitting device in a wireless communication system supporting ranging capability is provided. The method includes: determining at least one receiving device in a group of receiving devices participating in a ranging operation; identifying a scrambled timestamp sequence (STS) physical layer protocol data unit (PPDU) format 3 (SP3) ranging request report information element (SRRR IE) of at least one receiving device in the group of receiving devices; and sending a ranging control message (RCM) including the SRRR IE to at least one receiving device in the group of receiving devices participating in the ranging operation using an in-band mechanism or an out-of-band mechanism, wherein the RCM including the SRRR IE is sent in a time-scheduled ranging operation.

[0072] Other technical features may be easily understood by those skilled in the art based on the following drawings, descriptions and claims.

[0073] Invention Mode

[0074] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "connection" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives cover both direct and indirect communication. The terms "include" and "comprise" and their derivatives mean to include without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives mean to include, be included in, interconnect with, include, be included in, be connected to, or be connected with, be connected to, or be connected with, can communicate with, collaborate with, interweave, juxtapose, be adjacent to, be coupled to, or be coupled with, have, have the property of, have a relationship with, etc. The term "controller" means any device, system or part thereof that controls at least one operation. Such controllers can be implemented with hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items can be used, and only one item from the list may be needed. For example, "at least one of A, B, and C" includes any combination of: A, B, C, A and B, A and C, B and C, A and B and C.

[0075] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or parts thereof suitable 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 that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and then rewritten, such as rewritable optical discs or erasable memory devices.

[0076] Definitions for additional specific words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0077] The following discusses Figures 1 to 53 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be interpreted in any way to limit the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0078] The following documents and standard descriptions are hereby incorporated into the present disclosure by reference 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, 2015.

[0079] Aspects, features, and advantages of the present disclosure will be readily apparent from the following detailed description simply by illustrating a number of specific embodiments and implementations including the best mode contemplated for practicing the present disclosure, the present disclosure being capable of other different embodiments and its several details being capable of modification in various obvious respects, all without departing from the spirit and scope of the present disclosure. Accordingly, the drawings and description should be regarded as illustrative in nature and not restrictive. In the accompanying drawings, the present disclosure is illustrated by way of example and not by way of limitation.

[0080] The following Figures 1 to 4b Various embodiments are described for implementation in a wireless communication system and for implementation using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. Figures 1 to 3 The description is not intended to impose physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0081] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown. Figure 1 The embodiment of the wireless network shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

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

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

[0084] Depending on the network type, the term "base station" or "BS" may refer to any component (or set of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macro cell, a femto cell, a WiFi access point (AP), or other devices that support wireless functions. The base station may provide wireless access according to 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 convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. In addition, depending on the network type, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point" or "user device". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

[0085] Dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as generally circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with a gNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0086] As described in more detail below, one or more of 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 gNBs 101-103 include circuitry, programming, or a combination thereof for CSI acquisition in an advanced wireless communication system.

[0087] Although Figure 1 An example of a wireless network is shown, but Figure 1 Various changes may be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. In addition, gNB 101 may communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 may communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. In addition, gNBs 101, 102, and / or 103 may provide access to other or additional external networks, such as an external telephone network or other type of data network.

[0088] Figure 2 An example gNB 102 is shown according to an embodiment of the present disclosure. Figure 2 The embodiment of gNB 102 shown is for illustration only, and Figure 1 gNBs 101 and 103 may have the same or similar configurations. However, gNBs have a variety of configurations, and Figure 2 There is no intent to limit the scope of this disclosure to any particular implementation of a gNB.

[0089] like Figure 2 As shown, gNB 102 includes multiple antennas 205a to 205n, multiple RF transceivers 210a to 210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. gNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

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

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

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

[0093] For example, the controller / processor 225 may support beamforming or directional routing operations, in which outgoing signals from the multiple antennas 205a to 205n are weighted differently to effectively steer the outgoing signals in a desired direction. Any of a variety of other functions may be supported in the gNB 102 via the controller / processor 225.

[0094] Controller / processor 225 is also capable of executing programs and other processes, such as an OS, that reside in memory 230. Controller / processor 225 may move data into or out of memory 230 as required by the executing process.

[0095] The controller / processor 225 is also connected to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or network. The interface 235 can support communication over any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a system supporting 5G, LTE, or LTE-A), the interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 can allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure that supports communication over a wired or wireless connection, such as an Ethernet or RF transceiver.

[0096] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0097] Although Figure 2 An example of a gNB 102 is shown, but the Figure 2 For example, gNB 102 may include any number of Figure 2 As a specific example, the access point may include multiple interfaces 235, and the controller / processor 225 may support routing functions to route data between different network addresses. As another specific example, although shown as including a single instance of TX processing circuitry 215 and a single instance of RX processing circuitry 220, the gNB 102 may include multiple instances of each (such as one for each RF transceiver). In addition, Figure 2 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0098] Figure 3 An example UE 116 is shown according to an embodiment of the disclosure. Figure 3 The embodiment of UE 116 shown is for illustration only, and Figure 1 UEs 111 to 115 may have the same or similar configurations. However, UEs have various configurations, and Figure 3 The scope of the present disclosure is not limited to any particular implementation of a UE.

[0099] like Figure 3As shown, UE 116 includes antenna 305, radio frequency (RF) transceiver 310, TX processing circuit 315, microphone 320 and receive (RX) processing circuit 325. UE 116 also includes speaker 330, processor 340, input / output (I / O) interface (IF) 345, touch screen 350, display 355 and memory 360. Memory 360 includes operating system (OS) 361 and one or more application programs 362.

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

[0101] The TX processing circuit 315 receives analog or digital voice data from the microphone 320, or receives other outgoing baseband data (such as network data, email, or interactive video game data) from the processor 340. The TX processing circuit 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the outgoing processed baseband or IF signal from the TX processing circuit 315 and up-converts the baseband or IF signal into an RF signal that is transmitted via the antenna 305.

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

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

[0104] Processor 340 is also coupled to touch screen 350 and display 355. An operator of UE 116 may use touch screen 350 to input data into UE 116. Display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text (e.g., from a website) and / or at least limited graphics.

[0105] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

[0106] Although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 Various components in the embodiment may be combined, further subdivided, or omitted, and additional components may be added as required. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smart phone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0107] Figure 4a is a high-level diagram of a transmit path circuit. For example, the transmit path circuit may be used for orthogonal frequency division multiple access (OFDMA) communications. Figure 4b is a high-level diagram of a receive path circuit. For example, the receive path circuit can be used for orthogonal frequency division multiple access (OFDMA) communications. Figure 4a and Figure 4b In the embodiment, for downlink communication, the transmit path circuit may be implemented in a base station (gNB) 102 or a relay station, and the receive path circuit may be implemented in a user equipment (e.g., Figure 1In other examples, for uplink communications, the receive path circuit 450 may be implemented in a base station (e.g., Figure 1 The transmission path circuit may be implemented in a user equipment (e.g., a gNB 102) or a relay station, and the transmission path circuit may be implemented in a user equipment (e.g., Figure 1 is implemented in the user device 116).

[0108] The transmit path circuitry includes a channel coding and modulation block 405, a serial-to-parallel (SP) conversion block 410, an inverse fast Fourier transform (IFFT) block of size N 415, a parallel-to-serial (PS) conversion block 420, an add cyclic prefix block 425, and an upconverter (UC) 430. The receive path circuitry 450 includes a downconverter (DC) 455, a remove cyclic prefix block 460, a serial-to-parallel (SP) conversion block 465, a fast Fourier transform (FFT) block of size N 470, a parallel-to-serial (PS) conversion block 475, and a channel decoding and demodulation block 480.

[0109] Figure 4a 400 and Figure 4b At least some of the components in 450 may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. Specifically, please note that the FFT block and IFFT block described in this disclosure document may be implemented as a configurable software algorithm, where the value of size N may be modified depending on the implementation.

[0110] In addition, although the present disclosure is directed to embodiments that implement fast Fourier transform and inverse fast Fourier transform, this is merely exemplary and cannot be interpreted as limiting the scope of the present disclosure. It is understood that in alternative embodiments of the present disclosure, the fast Fourier transform function and the inverse fast Fourier transform function can be easily replaced by discrete Fourier transform (DFT) function and inverse discrete Fourier transform (IDFT) function, respectively. It is understood that for DFT and IDFT functions, the value of variable N can be any integer (i.e., 1, 2, 3, 4, etc.), and for FFT and IFFT functions, the value of variable N can be any integer as a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

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

[0112] The transmitted RF signal arrives at UE 116 after passing through the wireless channel, and the reverse operation of that at gNB 102 is performed. Downconverter 455 downconverts the received signal to baseband frequency, and remove cyclic prefix block 460 removes the cyclic prefix to produce a serial time-domain baseband signal. Serial-to-parallel conversion block 465 converts the time-domain baseband signal into parallel time-domain signals. FFT block 470 of size N then performs an FFT algorithm to produce N parallel frequency-domain signals. Parallel-to-serial conversion block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates and then decodes the modulation symbols to recover the original input data stream.

[0113] Each of the gNBs 101 to 103 may implement a transmit path similar to that for transmitting in the downlink to the user equipments 111 to 116, and may implement a receive path similar to that for receiving in the uplink from the user equipments 111 to 116. Similarly, each of the user equipments 111 to 116 may implement a transmit path corresponding to the architecture for transmitting in the uplink to the gNBs 101 to 103, and may implement a receive path corresponding to the architecture for receiving in the downlink from the gNBs 101 to 103.

[0114] A peer-aware communication (PAC) network is a fully distributed communication network that allows direct communication between PAC devices (PDs). A PAC network can adopt several topologies such as mesh, star, etc. to support interaction between PDs for various services. Although the present disclosure uses PAC networks and PDs as examples to develop and illustrate the present disclosure, it should be noted that the present disclosure is not limited to these networks. The general concepts developed in the present disclosure can be employed in different kinds of scenarios in various types of networks.

[0115] Figure 5 An example electronic device 500 is shown in accordance with an embodiment of the present disclosure. Figure 5 The illustrated embodiment of electronic device 500 is for illustration only. Figure 5 The scope of the present disclosure is not limited to any particular implementation.

[0116] A PD may be an electronic device. Figure 5 An example electronic device 501 is shown in a network environment 500 according to various embodiments. Figure 5 , the electronic device 501 in the network environment 500 may communicate with the electronic device 502 via a first network 598 (e.g., a short-range wireless communication network), or communicate with the electronic device 504 or the server 508 via a second network 599 (e.g., a long-range wireless communication network). According to one embodiment, the electronic device 501 may communicate with the electronic device 504 via the server 508.

[0117] According to one embodiment, the electronic device 501 may 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, a 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 of the components (e.g., the display device 560 or the camera 580) may be omitted from the electronic device 501, or one or more other components may be added to the electronic device 501. In some embodiments, some components may be implemented as a single integrated circuit. For example, a sensor 576 (e.g., a fingerprint sensor, an iris sensor, or an illumination sensor) may be implemented as embedded in a display device 560 (e.g., a display).

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

[0119] According to one embodiment of the present disclosure, the processor 520 may 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)), which may operate independently of the main processor 521 or in conjunction with the main processor 521. Additionally or alternatively, the auxiliary processor 523 may be adapted to consume less power than the main processor 521, or be dedicated to a specific function. The auxiliary processor 523 may be implemented to be independent of the main processor 521 or as part of the main processor 521.

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

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

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

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

[0124] The sound output device 555 can output a sound signal to the outside of the electronic device 501. The sound output device 555 may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or playing recordings, and the receiver may be used for incoming calls. According to one embodiment, the receiver may be implemented as being separated from the speaker, or as a part of the speaker.

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

[0126] The audio 570 can convert sound into an electrical signal, and vice versa. According to one embodiment, the audio 570 can obtain sound via the input device 550, or output sound via the sound output device 555 or an earphone of an external electronic device (e.g., electronic device 502) directly (e.g., using a wired line) or wirelessly connected to the electronic device 501.

[0127] The sensor 576 may detect an operating state (e.g., power or temperature) of the electronic device 501 or an environmental state (e.g., a user's state) outside the electronic device 501, and then generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor 576 may include, for example, a gesture sensor, a gyroscope 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 illumination sensor.

[0128] The interface 577 may support one or more designated protocols for the electronic device 501 to be directly (e.g., using a wired line) or wirelessly connected to an external electronic device (e.g., the electronic device 502). According to one embodiment of the present disclosure, the interface 577 may 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.

[0129] The connection terminal 578 may include a connector, and the electronic device 501 may be physically connected to an external electronic device (e.g., the electronic device 502) via the connector. According to one embodiment, the connection terminal 578 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0130] The haptic 579 may convert the electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus, which the user may recognize via his or her sense of touch or kinesthetic sense. According to one embodiment, the haptic 579 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

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

[0132] The power management 588 may manage the power supplied to the electronic device 501. According to one embodiment, the power management 588 may be implemented as, for example, at least a portion of a power management integrated circuit (PMIC). The battery 589 may supply power to at least one component of the electronic device 501. According to one embodiment, the battery 589 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0133] The communication interface 590 may 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., electronic device 502, electronic device 504, or server 508) and performing communication via the established communication channel. The communication interface 590 may include one or more communication processors that may operate independently of the processor 520 (e.g., an application processor (AP)) and support direct (e.g., wired) communication or wireless communication.

[0134] According to one embodiment of the present disclosure, the communication interface 590 may 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 may communicate with an external electronic device via a first network 598 (e.g., a short-range communication network such as Bluetooth, Wireless Fidelity (Wi-Fi) Direct, Ultra Wideband (UWB), or Infrared Data Association (IrDA)) or a second network 599 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a Wide Area Network (WAN))).

[0135] These different types of communication interfaces may be implemented as a single component (e.g., a single chip), or may be implemented as multiple components (e.g., multiple chips) that are separate from each other. The wireless communication interface 592 may identify and authenticate the electronic device 501 in a communication network (such as the first network 598 or the second network 599) using subscriber information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the subscriber identification module 596.

[0136] The antenna 597 can send or receive signals or power to or from the outside of the electronic device 501 (e.g., an external electronic device). According to one embodiment, the antenna 597 may 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 one embodiment, the antenna 597 may include a plurality of antennas. In this case, at least one antenna suitable for the communication scheme used in the communication network (such as the first network 198 or the second network 599) can be selected from the plurality of antennas by the communication interface 590 (e.g., a wireless communication interface 592), for example. Then, a signal or power can be sent or received between the communication interface 590 and the external electronic device via the selected at least one antenna. According to one embodiment, another component other than the radiating element (e.g., a radio frequency integrated circuit (RFIC)) can be additionally formed as a part of the antenna 597.

[0137] At least some of the above components can be interconnected and pass signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, general purpose input output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).

[0138] According to one embodiment of the present disclosure, commands or data may be sent or received between the electronic device 501 and the external electronic device 504 via a server 508 connected to the second network 599. Each of the electronic devices 502 and 504 may be a device of the same type or a different type as the electronic device 501. According to one embodiment, all or some operations to be performed at the electronic device 501 may be performed at one or more of the external electronic devices 502, 504, or 508. For example, if the electronic device 501 may automatically or in response to a request from a user or another device to perform a function or service, the electronic device 501 may request one or more external electronic devices to perform at least a portion of the function or service instead of or in addition to the electronic device 501 performing the function or service. The one or more external electronic devices that receive the request may perform at least a portion of the requested function or service, or an additional function or additional service related to the request, and transmit the result of the execution to the electronic device 501. The electronic device 501 may provide the result, whether or not the result is further processed, as at least part of a reply to the request. To this end, for example, cloud computing, distributed computing, or client-server computing techniques may be used.

[0139] The electronic device according to various embodiments may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. According to one embodiment of the present disclosure, the electronic device is not limited to those devices described above.

[0140] The various embodiments described herein may be implemented as software (e.g., program 140) that includes one or more instructions stored in a storage medium (e.g., internal memory 536 or external memory 538) that can be read by a machine (e.g., electronic device 501). For example, a processor (e.g., processor 520) of a machine (e.g., electronic device 501) may call 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 be operated to perform at least one function according to at least one instruction called. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Among them, the term "non-transitory" simply means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but this term does not distinguish between data being semi-permanently stored in the storage medium and data being temporarily stored in the storage medium.

[0141] According to one embodiment of the present disclosure, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or via an application store (e.g., PlayStore). TM ) online distribution or direct distribution (e.g., download or upload) between two user devices (e.g., smartphones). If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium, such as a memory of a manufacturer's server, an application store's server, or a relay server.

[0142] According to various embodiments of the present disclosure, each of the above-mentioned components (e.g., a module or a program) may include a single entity or multiple entities. According to various embodiments, one or more of the above-mentioned components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., a module or a program) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform one or more functions of each of the multiple components in the same or similar manner as one or more functions are performed by a corresponding one of the multiple components before integration. According to various embodiments, the operations performed by a module, a program or another component may be performed sequentially, in parallel, repeatedly or heuristically, or one or more operations may be performed or omitted in a different order, or one or more other operations may be added.

[0143] Ultra-wideband communication achieved by sending short radio pulses brings some key benefits to wireless communications, including low-complexity transceiver design, large capacity achieved by utilizing large bandwidth, and robustness to inter-symbol interference (ISI) in multipath environments. At the same time, extremely narrow pulses also reduce the probability of being intercepted and detected by third parties, which is promising for data services with high security requirements (e.g., secure ranging). Currently, IEEE 802.15.4z is exploring and developing enhancements to low-rate and high-rate UWB pulse radio capabilities, aiming to provide better integrity and efficiency.

[0144] Ranging and relative positioning are essential for various location-based services and applications (e.g., Wi-Fi Direct, Internet of Things (IoT), etc.). With the massive increase in network devices, a high demand for ranging requests can be foreseen in the near future, which means that comprehensive ranging message exchanges occur frequently in the network. This may exacerbate the bottleneck limited by battery capacity. For mobile devices and autonomous static devices (e.g., low-power sensors), energy efficiency becomes more critical.

[0145] Another key issue in dense environments is the waiting time for different ranging pairs to complete the scheduled ranging sessions. Based on the ranging process defined in the IEEE specification, each ranging pair can be assigned a dedicated time slot. If there are a large number of ranging requests, it may cause a long waiting time for the later scheduled pairs.

[0146] Therefore, implementing a more efficient ranging protocol is necessary to reduce the number of message exchanges required for many ranging pairs. In the present disclosure, an optimized ranging process is provided between one device group and another device group. Figure 6 As shown, one or more devices of group 1 have ranging requests to one or more devices of group 2, and vice versa. By utilizing the broadcast characteristics of the wireless channel, an optimized transmission mechanism can be implemented based on ranging operations (i.e., single-sided two-way ranging (SS-TWR) and double-sided two-way ranging (DS-TWR)), respectively, which greatly reduces the number of information exchanges required compared to the current standard.

[0147] Figure 6 An example many-to-many scenario 600 is shown according to an embodiment of the present disclosure. Figure 6 The illustrated embodiment of many-to-many scenario 600 is for illustration only. Figure 6 The scope of the present disclosure is not limited to any particular implementation.

[0148] like Figure 6 As shown, one or more devices are used to determine group 1 and group 2. One or more devices from group 1 have ranging requests to one or more devices from group 2.

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

[0150] There are two aspects that are omitted in the IEEE standard specification, which are essential for future use cases. The first aspect is the optimized transmission process between one or more initiators and one or more responders, which may be crucial for energy saving purposes. Because polls can be broadcast to multiple responders, an initiator can initialize a multicast (i.e., one-to-many) ranging round by sending a single poll instead of initiating multiple unicast ranging rounds. Similarly, since ranging responses can also be broadcast to multiple initiators, responders can embed data from requests from different initiators in a single ranging response message. Optimizing the transmission process by leveraging the broadcast nature of the wireless channel is promising for future UWB networks.

[0151] Another overlooked aspect is the option for contention-based ranging in UWB networks. In the IEEE specification, a ranging round contains only one pair of devices, namely, an initiator and a responder. Within a ranging round, transmissions are implicitly scheduled: the responder / initiator expects to receive a message from the far end and can then start sending. The CFP table of the synchronization frame can schedule multiple ranging rounds. However, there may also be other use cases that cannot be supported by the IEEE standard specification. For example, the initiator broadcasts a poll, but it does not know in advance who will answer. Similarly, the responder may not know in advance who will initialize the ranging, so it may continue to wait and listen for a period of time to collect polls from different initiators respectively.

[0152] In the present disclosure, a UWB network is provided with a ranging request between one device group and another device group. Figure 6 As shown, one or more devices of group 1 have ranging requests to one or more devices of group 2, and vice versa. In order to accommodate the optimized ranging transmission process and other new use cases, the configuration of the device role needs to be determined and exchanged before the ranging round begins (i.e., whether the device is configured as an initiator or responder, and the scheduling information for scheduled ranging). In order to establish an independent UWB network, the present disclosure defines new control IEs and ranging scheduling IEs for initiators and responders, which can be exchanged on the UWB MAC. However, the present disclosure does not exclude other methods of exchanging information via higher layers or out-of-band management.

[0153] Figure 7 An example single-sided two-way ranging 700 is shown according to an embodiment of the disclosure. Figure 7 The illustrated embodiment of single-sided two-way ranging 700 is for illustration only. Figure 7 The scope of the present disclosure is not limited to any particular implementation.

[0154] SS-TWR involves a simple measurement of the round-trip delay of a single message from an initiator to a responder and the response back to the initiator. The operation of SS-TWR is as follows: Figure 7 As shown, device A initiates the exchange and device B responds to complete the exchange. Each device accurately timestamps the send and receive times of the message frames, and the time T can therefore be calculated by simple subtraction round and T reply Therefore, the flight time T can be estimated by the following formula prop :

[0155]

[0156] Figure 8 An example bilateral two-way ranging 800 with three messages is shown in accordance with an embodiment of the disclosure. Figure 8 The illustrated embodiment of dual two-way ranging 800 with three messages is for illustration only. Figure 8 The scope of the present disclosure is not limited to any particular implementation.

[0157] Figure 8 A DS-TWR with three messages is shown, which reduces the estimation error caused by clock drift caused by long response delays. Device A is the initiator that initializes the first round-trip measurement, and device B responds as the responder to complete the first round-trip measurement and initialize the second round-trip measurement. Each device accurately timestamps the send and receive times of the message, and the resulting flight time estimate T can be calculated by prop :

[0158]

[0159] If necessary, the ranging time of flight (RTOF) information element (IE) can be used to transmit the ranging results to the remote end. Since multiple ranging results between one device and other devices may be embedded in one data frame, a MAC address or other short address (e.g., a multicast group address) can be added to this IE so that the device can extract the ranging results dedicated to it. If only one pair of devices participates in the ranging round, the address field does not need to be used. Fig. 9 An example of the RTOF IE content field format is shown in . Other examples are not excluded.

[0160] Fig. 9 An example ranging time of flight IE content field format 900 is shown in accordance with an embodiment of the disclosure. Fig. 9 The illustrated embodiment of the ranging time of flight IE content field format 900 is for illustration only. Fig. 9 The scope of the present disclosure is not limited to any particular implementation.

[0161] The Ranging Round Trip Measurement IE (RRTM IE) content includes the time difference between the transmission time of the Ranging Frame (RFRAME) that initiates the round trip measurement and the reception time of the response RFRAME that completes the round trip for each source address. The address field can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address. If only one pair of devices participates in the ranging round, the address field does not need to be used. Fig.10 An example RRTM IE content field format is shown in FIG. Other examples are not excluded.

[0162] Fig.10 An example ranging round trip measurement IE content field format 1000 is shown according to an embodiment of the present disclosure. Fig.10 The illustrated embodiment of the ranging round trip measurement IE content field format 1000 is for illustration only. Fig.10 The scope of the present disclosure is not limited to any particular implementation.

[0163] 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 this IE. The address field can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address. If only one pair of devices participates in the ranging round, the address field does not need to be used. Fig.11 An example RRTI IE content field format is shown in FIG. Other examples are not excluded.

[0164] Fig.11 An example ranging reply time instant IE content field format 1100 is shown according to an embodiment of the present disclosure. Fig.11 The embodiment of the ranging reply time transient IE content field format 1100 shown in FIG. 1 is for illustration only. Fig.11 The scope of the present disclosure is not limited to any particular implementation.

[0165] The Ranging Reply Time Delay IE (RRTD IE) content includes the time difference between the reception time of the most recently received RFRAME and the transmission time of the most recently transmitted response RFRAME before the frame containing this IE for each source address. The address field can be a 16-bit short address, a 48-bit MAC address, or a 64-bit extended address. If only one pair of devices participates in a ranging round, the address field does not need to be used. Fig.12 An example RRTD IE content field format is shown in FIG. Other examples are not excluded.

[0166] Fig.12 An example ranging reply time extension IE content field format 1200 is shown according to an embodiment of the present disclosure. Fig.12 The illustrated embodiment of the ranging reply time extension IE content field format 1200 is for illustration only. Fig.12The scope of the present disclosure is not limited to any particular implementation.

[0167] The Ranging Angle of Arrival (AoA) Extension (RAD) IE content includes an estimate of the AoA at the device that received the AoA request. The RAD IE is used as part of a two-way ranging exchange and is used for situations where the device cannot determine the AoA until after a reply has been sent, and in this case, the RAD IE carries the AoA in subsequent frames. When the RAD IE is used in a multicast / broadcast frame (e.g., multicast / broadcast / many-to-many ranging), the RAD IE content may 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 may be formatted as follows: Fig.13 shown.

[0168] Fig.13 An example ranging angle of arrival delay IE content field format 1300 is shown according to an embodiment of the present disclosure. Fig.13 The embodiment of the ranging angle of arrival delay IE content field format 1300 shown in FIG. 1 is for illustration only. Fig.13 The scope of the present disclosure is not limited to any particular implementation.

[0169] The Ranging Report Control Single-Side TWR (RRCST) IE is used to control the SS-TWR message exchange. Fig.14 Example RCST IE content field formats are shown in TABLE 1. Other examples are not excluded.

[0170] Fig.14 An example ranging control single-sided TWR IE content field format 1400 is shown according to an embodiment of the disclosure. Fig.14 The illustrated embodiment of the ranging control single-sided TWR IE content field format 1400 is for illustration only. Fig.14 The scope of the present disclosure is not limited to any particular implementation.

[0171] Table 1. Values ​​of the control information field in the ranging report control unilateral TWR IE

[0172] Control Information Value meaning 0 This frame indicates that the responder does not need TX-RX round trip time and ranging results. 1 This frame indicates that the responder requires a TX-RX round trip time at the end of the exchange. 2 This frame indicates that the responder requires ranging results at the end of the exchange.

[0173] The Ranging Report Control Bilateral TWR (RRCDT) IE is used to control the DS-TWR message exchange. Fig.15 Example RCDT IE content field formats are shown in TABLE 2 and TABLE 3. Other examples are not excluded.

[0174] Fig.15 An example ranging control bilateral TWR IE content field format 1500 is shown according to an embodiment of the disclosure. Fig.15 The illustrated embodiment of the ranging control two-sided TWR IE content field format 1500 is for illustration only. Fig.15 The scope of the present disclosure is not limited to any particular implementation.

[0175] Table 2. Values ​​of the control information field in the ranging report control bilateral TWR IE

[0176]

[0177]

[0178] The main enhancement of secure ranging is the inclusion of a scrambled timestamp sequence (STS) in the basic PHY protocol data unit (PPDU) format. Since one or more remote ends in the trusted group know the unique STS of the device, secure ranging can be performed within the trusted group and the chance of being attacked is significantly reduced. In the present disclosure, the framework is based on the fact that the STS of the device has been successfully exchanged, which can be done via (for example) higher layer control or out-of-band management. How to initialize / update the STS and exchange the STS between devices is not within the scope of the present disclosure.

[0179] Three security ranging PPDU formats may be supported, the differences between the formats being the location of the STS and the presence of the PHR and PHY payload fields, such as Fig.16 shown. Fig.16 The abbreviations in the figure represent the following definitions: synchronization header (SHR); scrambled time stamp sequence (STS); and PHY header (PHY).

[0180] Fig.16 An example three security ranging PPDU format 1600 is shown according to an embodiment of the present disclosure. Fig.16 The three embodiments of the safety ranging PPDU format 1600 shown are for illustration only. Fig.16 The scope of the present disclosure is not limited to any particular implementation.

[0181] exist Fig.16 (For example, Fig.16 The position of STS in (a) and (b) is different. Fig.16 (For example, Fig.16 (c)) format, without PHY header or data field (NHD). Fig.16 (For example, Fig.16 The ranging in the PPDU format of (c)) is used as the NHD safety ranging. Other conventions that meet similar concepts are not excluded in the present disclosure.

[0182] The advantage of supporting NHD secure ranging can be demonstrated in some use cases. Since there are fewer fields in NHDRFRAME, the transmit power can be more distributed on the STS to improve ranging performance. On the other hand, NHD RFRAME can tolerate a worse link budget than the other two formats because the other two formats require a higher signal-to-interference-and-noise ratio (SINR) to decode the PHR and PHR payload.

[0183] However, it is not clear how to control NHD safety ranging. As shown in the IEEE specification, the relevant ranging IE can be directly transmitted in the RFRAME to control the Fig.16 (For example, (a) and (b)) show the ranging process of the PPDU format. Fig.16 There is no PHR or PHY payload field in the format (e.g., (c)), so the ranging IE cannot be embedded in the NHD RFRAME, and a new framework / procedure is required to support NHD secure ranging.

[0184] In the present disclosure, it can be considered that the UWB network is provided with ranging requests between one device group and another device group. Figure 6 As shown, one or more devices of group 1 have ranging requests to one or more devices of group 2, and vice versa. To support NHD secure ranging for standalone UWB networks, the present disclosure defines a framework for new control IEs and ranging procedures, where existing ranging IEs for timestamp or angle reporting can still be used.

[0185] Fig.17 An example time structure 1700 of a ranging round according to an embodiment of the disclosure is shown. Fig.17 The illustrated embodiment of the timing structure 1700 of a ranging round is for illustration only. Fig.17 The scope of the present disclosure is not limited to any particular implementation.

[0186] The ranging configuration is incorporated into Fig.17 The control information of the ranging round composed of multiple time slots shown. The time slot is the basic time unit for completing information exchange. Other conventions that implement the same functions as ranging rounds and time slots are not excluded in the present disclosure. Depending on the device capabilities, the time slot duration and the number of time slots in a ranging round can be adjusted in the ranging configuration, or the time slot duration and the number of time slots can be fixed to the default settings. One or more pairs of devices can participate in a ranging round to satisfy a ranging request.

[0187] Fig.18 An example ranging device nomenclature 1800 (controller and controlled) is shown according to an embodiment of the present disclosure. Fig.18 The illustrated embodiment of the ranging device named 1800 is for illustration only. Fig.18The scope of the present disclosure is not limited to any particular implementation.

[0188] The settings of the ranging configuration determined by the next higher layer may be sent from the ranging controller (leader device) to one or more ranging slaves, such as Fig.18 As shown. For different network forms, the ranging configuration can be transmitted via a dedicated data frame sent to one or more devices, or can be embedded in a synchronization frame broadcast to devices in the network. At the same time, the present disclosure does not exclude other methods of exchanging ranging configuration information, for example, via higher layers or out-of-band management.

[0189] Fig.19 An example ranging round structure 1900 is shown according to an embodiment of the disclosure. Fig.19 The illustrated embodiment of the ranging round structure 1900 is for illustration only. Fig.19 The scope of the present disclosure is not limited to any particular implementation.

[0190] The ranging configuration includes a ranging round structure including one or more polling periods (PPs) and one or more ranging response periods (RRPs), wherein the PP consists of one or more time slots for sending polling messages from the initiator and the RRP consists of one or more time slots for sending response messages from the responder.

[0191] Fig.19 Two examples of SS-TWR and DS-TWR with three message exchanges are shown respectively, other examples are not excluded. A ranging round can start from a ranging control period to exchange ranging configurations on the UWB MAC. However, if the ranging configurations are exchanged at a higher layer, a ranging round can also start from a polling period.

[0192] For SS-TWR, one ranging round contains one PP and one RRP. For DS-TWR with three messages, one ranging round contains the first PP, one RRP and the second PP. Each cycle includes one or more time slots, where the transmission from the initiator / responder can be scheduled as determined by the next higher layer, or the transmission from the initiator / responder can contend for the time slot in the corresponding cycle respectively.

[0193] Fig. 20 An example ranging request measurement and control IE content field format 2000 is shown according to an embodiment of the present disclosure. Fig. 20 The illustrated embodiment of the ranging request measurement and control IE content field format 2000 is for illustration only. Fig. 20 The scope of the present disclosure is not limited to any particular implementation.

[0194] The Ranging Request Measurement and Control IE (RRMC IE) may be used to send ranging requests to different devices and control the ranging process. Fig. 20 The content field format of the RRMC IE is shown in FIG. Fig.21 A row element that displays the content field format in .

[0195] Fig.21 An example RRMC table row element format 2100 is shown according to an embodiment of the present disclosure. Fig.21 The illustrated embodiment of the RRMC table row element format 2100 is for illustration only. Fig.21 The scope of the present disclosure is not limited to any particular implementation.

[0196] like Fig. 20 As shown, the length of the RRMC IE content field determines the existence of the RRMC table length field and the RRMC table field: if the length of the RRMC IE is one octet, the RRMC table length and the RRMC table do not exist; if the length exceeds one octet, the RRMC table length and the RRMC table exist. 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 receiving the request.

[0197] If the RRMC IE is transmitted in a unicast frame, the destination address is already specified by the MHR. Therefore, the RRMC Table Length field and the RRMC Table field are not required. When the RRMC IE is transmitted in a broadcast message, the device sending this IE intends to request the device receiving the IE, and the RRMC Table Length field and the RRMC Table field are also not required. However, if the device issuing the request expects a response from a specified group of devices, the RRMC Table Length field and the RRMC Table field exist to list the addresses of those devices.

[0198] The reply time request (RTR) field indicates whether a reply time is requested for sending a response to the message ERDEV with this RRMC IE: if the RTR field value is 1, a reply time is requested, otherwise not requested.

[0199] The Round Trip Measurement Request (RMR) field indicates whether the ERDEV is requested to make a round trip measurement upon receiving a message with this RRMC IE: if the RMR field value is 1, round trip measurement is requested, otherwise not.

[0200] The TOF Request (TOFR) field indicates whether the ranging result, i.e., the time of flight, is requested: if the TOFR field value is 1, the ranging result is requested, otherwise it is not requested. For SS-TWR, the initiator is able to calculate TOF after ranging transmission. The responder can request TOF by setting the TOFR field to 1 in the RRMC IE of the ranging response message. For DS-TWR, the responder is able to calculate TOF after ranging. The initiator can request TOF by setting the TOFR field to 1 in the RRMC IE of the ranging initiation message.

[0201] The AOA azimuth request (AAR) and AOA elevation request (AER) fields indicate whether to request azimuth AOA and elevation AOA: if the field value is 1, the corresponding information is requested, otherwise it is not requested.

[0202] Use as Fig. 20 As shown in the content field format, 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.

[0203] exist Fig.21 In , the address type (i.e., 2-octet or 8-octet address) can be specified by the DstAddrMode of MCPS-DATA.request.

[0204] The values ​​of the ranging control information field are described in the following Table 3, which is used to indicate the purpose of RFRAME.

[0205] Table 3. Values ​​of the Ranging Control Information field in the RRMC IE

[0206]

[0207]

[0208] The ranging measurement information IE (RMI IE) may be used to send ranging related measurements to one or more devices. Fig. 20 The content field format of the RMI IE is shown in Figure 1, where the row element of the RMI IE is Fig. 22 Displayed in.

[0209] Fig. 22 An example ranging measurement information IE content field format 2200 is shown according to an embodiment of the present disclosure. Fig. 22 The illustrated embodiment of the ranging measurement information IE content field format 2200 is for illustration only. Fig. 22 The scope of the present disclosure is not limited to any particular implementation.

[0210] Fig. 22The first bit of the control octet in the address field is used to indicate the Fig.23 Whether there is an address field in each row element of the RMI table shown: if the address field value is 1, the address field of the RMI table row element is present, otherwise it is not present. For multi-node ranging, the ERDEV can report measurements via the RMI IE, which lists measurement reports to different destinations in the RMI table. The address field of the RMI table row element is used to distinguish the ERDEV requesting specific information. For unicast ranging, the address field can be omitted.

[0211] Fig.23 An example RMI table row element format 2300 is shown according to an embodiment of the present disclosure. Fig.23 The illustrated embodiment of the RMI table row element format 2300 is for illustration only. Fig.23 The scope of the present disclosure is not limited to any particular implementation.

[0212] Bits 1 to 5 are used to indicate whether specific information exists in the row element of the RMI table: if the field value is 1, the corresponding information is present in each row element of the RMI table, otherwise it is not present.

[0213] Bit 6 of the control octet is used to indicate whether this RMI IE is transmitted in an RFRAME or in a Deferred Data message: if the value of bit 6 is 0, this RMI IE is embedded in an RFRAME, otherwise it is transmitted in a Deferred Data message.

[0214] exist Fig.23 In the RX-TX Reply Time field, the RX-TX Reply Time field is the time difference between the reception time of the most recently received RFRAME with a RRMC IE requesting a reply time from a particular source and the transmission time of the responding RFRAME. If the Deferred Mode field value is 0, the RMI IE reporting the reply time is embedded in the responding RFRAME. If the Deferred Mode field value is 1, the RMI IE is embedded in the Deferred Data message, and the transmitted reply time is associated with the most recently transmitted RFRAME prior to this data message. The TX-RX Round Trip Time field is the time difference between the transmission time of the RFRAME that initiated the round-trip measurement and the reception time of the responding RFRAME that completed the round-trip measurement. The TOF field contains a time of flight estimate.

[0215] The reference to these time values ​​(ie, reply time, round trip time, and TOF) is RMARKER. These time values ​​are unsigned integer time values ​​whose time units are the ranging counter time units specified in the IEEE standard specification.

[0216] The AOA Azimuth field (if present) reports the estimated angle of arrival in the azimuth domain of a received RFRAME with an RRMC IE requesting an azimuth AOA. The AOA Elevation field (if present) reports the estimated angle of arrival in the elevation domain of a received RFRAME with an RRMC IE requesting an elevation AOA. These fields for reporting AOA contain unsigned integers. The units of AOA Azimuth are 2. -16 Multiply by 360 degrees, and the unit of AOA elevation angle is 2 -16 Multiply by 180 degrees.

[0217] If an address field is present in each row element of the RMI table, the address type (ie, 2 octet or 8 octet address) may be specified by the DstAddrMode of the MCPS-DATA.request.

[0218] Fig.24 An example NHD ranging round structure 2400 is shown according to an embodiment of the disclosure. Fig.24 The illustrated embodiment of the NHD ranging round structure 2400 is for illustration only. Fig.24 The scope of the present disclosure is not limited to any particular implementation.

[0219] In one embodiment 0, a time structure of a NHD safety ranging round is provided. Fig.24 The time structure of the NHD safety ranging round is configured in this way.

[0220] The controller can obtain requests from different controlled persons respectively via higher layers or out-of-band management. The present disclosure introduces a ranging IE for supporting NHD secure ranging, which is transmitted in an RC frame / message, such as Fig.18 Specifically, these ranging IEs each contain a request from the requester to the other remote end for specific information (e.g., AoA, reply time). The exchange of these requests may also be performed via higher layers or out-of-band management, which is not excluded by the present disclosure.

[0221] After the ranging configuration in the RC frame / message, NHD ranging is done on the allocated time slot. Note that since there is no PHY payload in the NHD RFRAME to distinguish messages from different devices, the NHD ranging message exchange needs to be scheduled in advance. Therefore, contention-based NHD ranging cannot be supported. The ranging scheduling allocation can be a separate IE transmitted in the RC frame / message, or exchanged via higher layers, which is not limited by the present disclosure.

[0222] After the NHD ranging period, the ranging device is scheduled in sequence to send data frames in the data reporting period, which convey the requested information to different requesters respectively. Since the NHD RFRAME has no PHR or PHY payload, dedicated data / measurement reports can be scheduled to exchange the requested information. There may be some use cases that do not require requests to the far end, where the data / measurement reporting period in the time structure can be removed. For example, the device can estimate the AoA of the far end via the received NHDRFRAME, and the device has no request to the far end.

[0223] Fig.25 An example NHD ranging round structure with a request exchange period 2500 is shown according to an embodiment of the disclosure. Fig.25 The illustrated embodiment of the NHD ranging round structure with request exchange period 2500 is for illustration only. Fig.25 The scope of the present disclosure is not limited to any particular implementation.

[0224] If requests cannot be exchanged via higher layers, and the controller cannot obtain requests from different controlees, a request exchange cycle can be used to exchange requests between devices, such as Fig.25 shown.

[0225] Specifically, each requester may be scheduled to send a request IE to one or more remote ends in a dedicated data frame during a request exchange period. Scheduling assignments may be done by IE or payload fields in RC frames, or scheduling assignments may be scheduled via higher layers. After a successful exchange of requests, the NHD ranging period begins.

[0226] In one embodiment 1, a NHD Safety Ranging IE is provided. With the knowledge of the requests from the controlees, the controller forms the NHD Safety Ranging IE related to these requests and broadcasts to the controlees.

[0227] Fig.26 An example Angle of Arrival NHD Ranging Request IE content field format 2600 is shown according to an embodiment of the disclosure. Fig.26 The illustrated embodiment of the Angle of Arrival NHD Ranging Request IE Content Field Format 2600 is for illustration only. Fig.26 The scope of the present disclosure is not limited to any particular implementation.

[0228] In one example 1, an angle of arrival NHD ranging request IE is provided. The NHD ranging request AoA (NRRA) IE may be used in an RC frame / message to indicate an AoA request from a requester to a provider. The general IE format may refer to the IEEE specification, and Fig.26 An example of IE content fields is shown in Figure 1.

[0229] The NRRA IE contains two address fields: one for the requester and the other for the provider. Depending on the use case and device capabilities, different types of addresses may be used, for example, 2-octet multicast group address, 6-octet MAC address, and 8-octet extended address. One or more NRRA IEs may be transmitted in an RC frame / message, distinguished by their respective address fields.

[0230] For use cases with many initiators and many responders, two address fields are required to distinguish a pair of devices. However, there are other variations that can save one or two address fields. For example, for unicast NHD security ranging, if the controller requests AoA at the controlled device, the controller can send an NRRA IE without a content field in the RC frame, because the pair of requester and provider can be distinguished by the address field of the MAC frame. For multicast NHD security ranging (i.e., only one initiator and multiple responders), if the controller is also the initiator and requests an AoA report from the controlled device / responder, the NRRA IE in the RC frame does not need to contain the requester's address field, because the responder implicitly knows that the request is from the initiator / controller.

[0231] Fig. 27 Another example Angle of Arrival NHD Ranging Request IE content field 2700 is shown according to an embodiment of the present disclosure. Fig. 27 The illustrated embodiment of the Angle of Arrival NHD Ranging Request IE Contents field 2700 is for illustration only. Fig. 27 The scope of the present disclosure is not limited to any particular implementation.

[0232] To support the various use cases described above, Fig. 27 The address presence indicator is introduced in . The first two bit fields represent the indicators of the requester address presence and the provider address presence, respectively. Note that the address type can be determined by the DstAddrMode of MCPS-DATA.request.

[0233] Fig.28 Yet another example Angle of Arrival NHD Ranging Request IE content field 2800 is shown according to an embodiment of the present disclosure. Fig.28 The illustrated embodiment of the Angle of Arrival NHD Ranging Request IE Contents field 2800 is for illustration only. Fig.28 The scope of the present disclosure is not limited to any particular implementation.

[0234] This disclosure does not exclude the implementation of Fig.19 Other structures with similar content fields in the . Fig.28 It is shown that the first two bits of the octet are used as address presence indicators, while the other bits of the octet are reserved.

[0235] like Fig.25 As shown, if the controller has no prior knowledge of the request from the controlled device, it can transmit request frames / messages with different devices in the request exchange cycle. Fig.26 The NRRA IE of the content field is shown.

[0236] In this case, if Figures 26 to 28 Both address fields of the NRRA IE shown may be ignored since the requester / provider addresses are already determined by the source / destination address fields of the MAC header.

[0237] If the controller is aware of the controlee's request via higher layers or out-of-band management, one or more NRRA IEs may be used in the RC frame / message broadcast by the controller. There may also be other variations to convey these requests in the RC frame / message. For example, the NRRA IE may be formed as Fig.29 , where each row of the NRRA table contains the address fields of the requester and provider, respectively, such as Fig.26 (or Fig. 27 and Fig.28 ) is shown in FIG. NRRA table length indicates the number of rows in the NRRA table, which is equivalent to the number of AoA requests for this ranging round.

[0238] Fig.29 An example Angle of Arrival NHD Ranging Request IE content field format 2900 including one or more requests is shown according to an embodiment of the present disclosure. Fig.29 The illustrated embodiment of the Angle of Arrival NHD Ranging Request IE Content Field Format 2900 is for illustration only. Fig.29 The scope of the present disclosure is not limited to any particular implementation.

[0239] Fig.30 Another example Angle of Arrival NHD Ranging Request IE content field format 3000 including one or more requests according to an embodiment of the disclosure is shown. Fig.30 The illustrated embodiment of the Angle of Arrival NHD Ranging Request IE Content Field Format 3000 is for illustration only. Fig.30 The scope of the present disclosure is not limited to any particular implementation.

[0240] Other structures of NRRAIE with NRRA table fields that implement similar functions are not excluded. For example, Fig.30 The Address Presence field is shown at the beginning of the NRRA IE, and each row of the table maintains the same Fig.26 If the requester / provider address can be determined from the source / destination address of the MAC header, then the value of the corresponding Address Present field is zero and such address need not be included in every row of the NRRA table.

[0241] Fig.31 An example reply time NHD ranging request IE content field format 3100 is shown according to an embodiment of the present disclosure. Fig.31 The illustrated embodiment of the reply time NHD ranging request IE content field format 3100 is for illustration only. Fig.31 The scope of the present disclosure is not limited to any particular implementation.

[0242] In one example 2, a reply time NHD ranging request IE is provided. A reply time NHD ranging request (NRRRT) IE may be used in an RC frame / message to indicate a reply time request from a requester to a provider's NHD RFRAME. The general IE format may refer to the IEEE specification, and Fig.31 An example of the IE content field is shown in FIG.

[0243] Similar to the NRRA IE, the NRRRT IE contains two address fields: one for the requester and the other for the provider. Depending on the use case and device capabilities, different types of addresses may be used, such as 2-octet multicast group addresses, 6-octet MAC addresses, and 8-octet extended addresses. One or more NRRA IEs may be transmitted in an RC frame / message, distinguished by their respective address fields.

[0244] For use cases with many initiators and many responders, two address fields are required to distinguish a pair of devices. However, there are other variations that can save one or two address fields. For example, for unicast NHD security ranging, if the controller requests a reply time from the controlled device, the controller can send an NRRRT IE without a content field in the RC frame, because the pair of requester and provider can be distinguished by the address field of the MAC frame. For multicast NHD security ranging (i.e., only one initiator and multiple responders), if the controller is also the initiator and requests a reply time from the controlled device / responder for an RFRAME, the NRRRT IE in the RC frame does not need to include the requester's address field, because the responder implicitly knows that the request comes from the initiator / controller.

[0245] Fig.32 Another example reply time NHD ranging request IE content field format 3200 according to an embodiment of the present disclosure is shown. Fig.32 The illustrated embodiment of the reply time NHD ranging request IE content field format 3200 is for illustration only. Fig.32 The scope of the present disclosure is not limited to any particular implementation.

[0246] To support the various use cases described above, Fig.32The address presence indicator is introduced in . The first two bit fields represent the indicators of the requester address presence and the provider address presence, respectively. Note that the address type can be determined by the DstAddrMode of MCPS-DATA.request.

[0247] Fig.33 Yet another example reply time NHD ranging request IE content field format 3300 according to an embodiment of the present disclosure is shown. Fig.33 The illustrated embodiment of the reply time NHD ranging request IE content field format 3300 is for illustration only. Fig.33 The scope of the present disclosure is not limited to any particular implementation.

[0248] This disclosure does not exclude the implementation of Fig.24 Other structures with similar content fields in the . Fig.33 It is shown that the first two bits of the octet are used as address presence indicators, while the other bits of the octet are reserved.

[0249] exist Fig.25 In the case where the controller has no prior knowledge of the request from the controlled device, it can transmit request frames / messages with different devices in the request exchange cycle. Fig.31 The NRRRT IE of the content field shown in .

[0250] In this case, if Figure 31 to Figure 33 Both address fields of the NRRRT IE shown may be ignored since the requester / provider addresses are already determined by the source / destination address fields of the MAC header.

[0251] Fig.34 An example reply time NHD ranging request IE content field format 3400 including one or more requests according to an embodiment of the disclosure is shown. Fig.34 The illustrated embodiment of the reply time NHD ranging request IE content field format 3400 is for illustration only. Fig.34 The scope of the present disclosure is not limited to any particular implementation.

[0252] If the controller is aware of the controlee's request via higher layers or out-of-band management, one or more NRRRT IEs may be used in the RC frame / message broadcast by the controller. There may also be other variations to convey these requests in the RC frame / message. For example, we may Fig.34 The content fields of the NRRRT IE are formed as shown, where each row of the NRRRT table contains the address fields of the requester and the provider, respectively, such as Fig.31 (or Fig.32 and Fig.33). The NRRRT table length indicates the number of rows in the NRRRT table, which is equivalent to the number of reply time requests for this ranging round.

[0253] Fig.35 Another example reply time NHD ranging request IE content field format 3500 including one or more requests according to an embodiment of the disclosure is shown. Fig.35 The illustrated embodiment of the reply time NHD ranging request IE content field format 3500 is for illustration only. Fig.35 The scope of the present disclosure is not limited to any particular implementation.

[0254] Other structures of the NRRRT IE with NRRRT table fields that implement similar functions are not excluded. For example, Fig.35 The address presence field is shown at the beginning of the NRRRT IE, and each row of the table maintains the same Fig.31 If the requester / provider address can be determined from the source / destination address of the MAC header, then the value of the corresponding Address Present field is zero, and such address need not be included in every row of the NRRRT table.

[0255] Fig.36 An example round trip measurement NHD ranging request IE content field format 3600 is shown according to an embodiment of the present disclosure. Fig.36 The illustrated embodiment of the round trip measurement NHD ranging request IE content field format 3600 is for illustration only. Fig.36 The scope of the present disclosure is not limited to any particular implementation.

[0256] In one example 3, a round trip measurement NHD ranging request IE is provided. A round trip measurement NHD ranging request may be used in an RC frame / message to indicate a round trip measurement request from a requester to a provider. The general IE format may refer to the IEEE specification, and Fig.36 An example of IE content fields is shown in Figure 1.

[0257] Similar to NRRA, NRRRT IE, NRRRTM IE contains two address fields: one for requester and the other for provider. Depending on the use case and device capabilities, different types of addresses can be used, for example, 2 octet multicast group address, 6 octet MAC address and 8 octet extension address. One or more NRRA IEs can be transmitted in an RC frame / message, which are distinguished by their respective address fields.

[0258] For use cases with many initiators and many responders, two address fields are required to distinguish a pair of devices. However, there are other variations that can save one or two address fields. For example, for unicast NHD security ranging, if the controller requests a round-trip time from the controllede, the controller can send an NRRRTM IE without a content field in the RC frame, because the pair of requester and provider can be distinguished by the address field of the MAC frame. For multicast NHD security ranging, if the controller is also the initiator of DS-TWR and requests a second round-trip time from the controllede / responder, the NRRRTM IE in the RC frame does not need to contain the requester's address field, because the responder implicitly knows that the request is from the initiator / controller.

[0259] Fig.37 An example round trip measurement NHD ranging request IE 3700 is shown according to an embodiment of the present disclosure. Fig.37 The illustrated embodiment of the round trip measurement NHD ranging request IE 3700 is for illustration only. Fig.37 The scope of the present disclosure is not limited to any particular implementation.

[0260] To support the various use cases described above, Fig.37 The address presence indicator is introduced in . The first two bit fields represent the indicators of the requester address presence and the provider address presence, respectively. Note that the address type can be determined by the DstAddrMode of MCPS-DATA.request.

[0261] This disclosure does not exclude the implementation of Fig.37 Other structures with similar content fields in the . Fig.38 It is shown that the first two bits of the octet are used as address presence indicators, while the other bits of the octet are reserved.

[0262] Fig.38 An example round trip measurement NHD ranging request IE content field 3800 is shown according to an embodiment of the present disclosure. Fig.38 The illustrated embodiment of the Round Trip Measurement NHD Ranging Request IE Contents field 3800 is for illustration only. Fig.38 The scope of the present disclosure is not limited to any particular implementation.

[0263] like Fig.25 As shown, if the controller has no prior knowledge of the request from the controlled device, it can transmit request frames / messages with different devices in the request exchange cycle. Fig.36 In this case, if Figures 36 to 38Both address fields of the NRRRTM IE shown may be ignored since the requester / provider addresses are already determined by the source / destination address fields of the MAC header.

[0264] Fig.39 An example round trip measurement NHD ranging request IE content field format 3900 including one or more requests according to an embodiment of the present disclosure is shown. Fig.39 The illustrated embodiment of the round trip measurement NHD ranging request IE content field format 3900 is for illustration only. Fig.39 The scope of the present disclosure is not limited to any particular implementation.

[0265] If the controller is aware of the controlee's request via higher layers or out-of-band management, one or more NRRRTM IEs may be used in the RC frame / message broadcast by the controller. There may also be other variations to convey these requests in the RC frame / message. For example, we may Fig.39 The content fields of the NRRRTM IE are formed as shown, where each row of the NRRRTM table contains the address fields of the requester and the provider, respectively. Fig.36 (or Fig.37 and Fig.38 ) is shown in FIG. NRRRTM table length indicates the number of rows in the NRRRTM table, which is equivalent to the number of round trip time requests for this ranging round.

[0266] Other structures of NRRRTM IE with NRRRTM table fields that implement similar functions are not excluded. For example, Fig.40 The address presence field is shown at the beginning of the NRRRTM IE, and each row of the table maintains the same Fig.36 If the requester / provider address can be determined from the source / destination address of the MAC header, then the value of the corresponding Address Present field is zero, and such address need not be included in every row of the NRRRTM table.

[0267] Fig.40 Another example round trip measurement NHD ranging request IE content field format 4000 including one or more requests according to an embodiment of the disclosure is shown. Fig.40 The illustrated embodiment of the Round Trip Measurement NHD Ranging Request IE Content Field Format 4000 is for illustration only. Fig.40 The scope of the present disclosure is not limited to any particular implementation.

[0268] Fig.41 An example message exchange diagram 4100 of NHD ranging (multicast SS-TWR) according to an embodiment of the disclosure is shown. Fig.41 The embodiment of the message exchange diagram 4100 shown is for illustration only. Fig.41The scope of the present disclosure is not limited to any particular implementation.

[0269] Fig.42a An example message sequence chart 4200 for NHD ranging (multicast SS-TWR) utilizing the next higher layer according to an embodiment of the disclosure is shown. Fig.42a The embodiment of the message sequence chart 4200 shown is for illustration only. Fig.42a The scope of the present disclosure is not limited to any particular implementation.

[0270] Figure 42b An example message sequence chart 4250 is shown for NHD ranging (multicast SS-TWR) utilizing the next higher layer according to an embodiment of the disclosure. Figure 42b The embodiment of the message sequence chart 4250 shown is for illustration only. Figure 42b The scope of the present disclosure is not limited to any particular implementation.

[0271] Fig.43 An example message exchange diagram 4300 of NHD ranging (multicast DS-TWR) according to an embodiment of the disclosure is shown. Fig.43 The embodiment of the message exchange diagram 4300 shown is for illustration only. Fig.43 The scope of the present disclosure is not limited to any particular implementation.

[0272] Fig.44a An example message sequence chart 4400 for NHD ranging (multicast DS-TWR) utilizing the next higher layer according to an embodiment of the disclosure is shown. Fig.44a The embodiment of the message sequence chart 4400 shown is for illustration only. Fig.44a The scope of the present disclosure is not limited to any particular implementation.

[0273] Figure 44b An example message sequence chart 4450 is shown for NHD ranging (multicast DS-TWR) utilizing the next higher layer according to an embodiment of the disclosure. Figure 44b The embodiment of the message sequence chart 4450 shown is for illustration only. Figure 44b The scope of the present disclosure is not limited to any particular implementation.

[0274] In one embodiment, a NHD safety ranging process is provided. In this embodiment, an example of a detailed NHD ranging process is provided by Figure 41 to Figure 44a and Figure 44b The message exchange diagram in FIG. 1 corresponds to multicast SS-TWR and DS-TWR, respectively. Unicast ranging can be viewed as a special case of multicast ranging. The process presented in this embodiment can also be generalized to accommodate use cases with many initiators and many responders. The present disclosure provides a method with Fig.24An example of a ranging process of the round structure presented. Fig.25 Other variations of the ranging process in the round structure.

[0275] In one example 4, NHD ranging (multicast SS-TWR) is provided.

[0276] Fig.41 An example multicast SS-TWR using NHD ranging is shown, which includes three periods corresponding to RC frames / messages, NHD ranging, and data / measurement reports. i " represents the i-th responder, and "I" represents the initiator. In this example, the first responder is the controller, and the others are controlled. At the beginning of the ranging round, the RC frame transmits the ranging configuration information and request related IE. For example, NRRA (R 1 |I) indicates that the first responder requests AoA at the initiator, and NRRRTM (R 1 |I) indicates the round trip time for the first responder to request RFRAME from the initiator.

[0277] After the RC frame / message, NHD ranging begins. Since ranging scheduling is done by the RC frame or higher layers before NHD ranging, the device can know the identity of the remote end associated with the received RFRAME. The PHY layer of each device passes the timestamp of the received RFRAME to the MAC layer of each device so that this information can be used to calculate the reply time or round-trip time measurement.

[0278] After the NHD ranging period, the device is scheduled to send the requested information in the data / measurement report period, where there are ranging IEs such as RRTM IE, RRTD IE in the IEEE specification. For example, the initiator transmits the AoA and round-trip time to the first responder in RAD IE, RRTM IE, respectively. Responder-1 and responder-N embed the requested reply time in the RRTD IE to the initiator, respectively.

[0279] The controller can also be the initiator, and the corresponding message exchange diagram is simple and omitted here.

[0280] In one example 5, NHD ranging (multicast DS-TWR) is provided.

[0281] Fig.43 shows an example multicast DS-TWR using NHD ranging, which is similar to Fig.41. The main difference is that there is a second polling message from the initiator in the NHD ranging cycle. At the beginning of the ranging round, the request is broadcast from the controller to the controlled. For example, the initiator requests AoA reports from both Responder-1 and Responder-N. After the NHD ranging, the device is scheduled to send a data report with the requested information. For example, the initiator sends the reply time and round-trip time to Responder-1, and Responder-1 and Responder-N send AoA reports back to the initiator respectively. In this example, the controller plays the role of the responder. The controller can also be the initiator, and the corresponding message exchange diagram is simple and omitted here.

[0282] Fig.45 An example NHD ranging request report IE content field 4500 is shown according to an embodiment of the present disclosure. Fig.45 The illustrated embodiment of the NHD Ranging Request Report IE Content field 4500 is for illustration only. Fig.45 The scope of the present disclosure is not limited to any particular implementation.

[0283] In one embodiment 3, a NHD safety ranging request is provided.

[0284] The NHD Ranging Request IE introduced in E1 can also be combined into a single IE, namely the NHD Ranging Request Report (NRRR) IE. Fig.45 An example of the content field is shown in FIG.

[0285] In the first 1-octet control field, the first bit field is used to indicate the presence of the requester address, i.e., "0": the requester address field is not used; "1": the requester address field exists. The second bit field is used to indicate the type of the requester address, for example, "0": 2-octet short address; "1": 8-octet extended address. Other variations of this bit field including other options for the address type are not excluded in the present disclosure. Similarly, Bit: 2 and Bit: 3 are used to indicate the presence and address type of the provider address.

[0286] Bits: 4 to 6 are used to present a request for certain information, i.e., "0": information of the corresponding field is not requested; "1": information of the corresponding field is requested. Therefore, the requester can request a combination of AOA, reply time, and round-trip measurement via the same IE. The last bit field of an octet control field (i.e., bit: 7) is reserved for future use. The size of the last two fields of the requester and provider address is determined by the first four bits of the control field.

[0287] Fig.45 The structure of the content field in the _address_field provides flexibility to accommodate a mix of address field types. For example, the requester address can be a 2-octet short address, while the provider address can be an 8-octet extended address.

[0288] Fig.46 An example NHD ranging request report IE content field 4600 is shown according to an embodiment of the present disclosure. Fig.46 The illustrated embodiment of the NHD Ranging Request Report IE Content field 4600 is for illustration only. Fig.46 The scope of the present disclosure is not limited to any particular implementation.

[0289] On the other hand, the address type of both the requester and the provider can also be determined as a short address or an extended address by the DstAddrMode of MCPS-DATA.request. Therefore, it is not necessary to include the field of the address type, and the content field of the NRRR IE is reduced.

[0290] Fig.47 An example NHD ranging request report IE content field 4700 with a ToF request field is shown according to an embodiment of the present disclosure. Fig.47 The illustrated embodiment of the NHD Ranging Request Report IE Content field 4700 is for illustration only. Fig.47 The scope of the present disclosure is not limited to any particular implementation.

[0291] To exchange requests for final ranging results (i.e., time of flight (ToF)) from other devices, a bit field for ToF request can be added to Fig.46 , this is Fig.47 Shown in.

[0292] The 1-bit field of ToF request is used to indicate the presence of ToF request, i.e., if the value is "1", the ToF request exists, otherwise it does not exist. The other fields remain the same as Fig.38 Please note that the present disclosure does not exclude other bit combinations of requesting AOA, reply time, round trip time and / or ToF.

[0293] Fig.48 An example NHD ranging request report IE content field 4800 with an NRRR table is shown according to an embodiment of the present disclosure. Fig.48 The illustrated embodiment of the NHD Ranging Request Report IE Content field 4800 is for illustration only. Fig.48 The scope of the present disclosure is not limited to any particular implementation.

[0294] There can be requests between different pairs of requesters and providers. On the one hand, multiple NRRR IEs with different address fields can be transmitted through the ranging control message. On the other hand, similar to Fig.39 , the NRRR IE may include a table to stack requests for different ranging pairs. Therefore, the content field of the NRRR IE becomes Fig.48 :

[0295] The first octet field indicates the row number in the NRRR table, which corresponds to the number of ranging pairs that need to exchange request reports. Each row of the NRRR table follows Fig.45 (or Fig.46 and Fig.47 )'s content field structure.

[0296] Fig.49a An example message sequence chart 4900 of NHD ranging (multicast SS-TWR) with request exchange by NRRR IE according to an embodiment of the present disclosure is shown. Fig.49a The embodiment of the message sequence chart 4900 shown is for illustration only. Fig.49a The scope of the present disclosure is not limited to any particular implementation.

[0297] Fig.49b An example message sequence chart 4950 of NHD ranging (multicast SS-TWR) with request exchange by NRRR IE according to an embodiment of the present disclosure is shown. Fig.49b The embodiment of the message sequence chart 4950 shown is for illustration only. Fig.49b The scope of the present disclosure is not limited to any particular implementation.

[0298] Fig.50a An example message sequence chart 5000 of NHD ranging (multicast DS-TWR) with request exchange by NRRR IE according to an embodiment of the disclosure is shown. Fig.50a The illustrated embodiment of the message sequence chart 5000 is for illustration only. Fig.50a The scope of the present disclosure is not limited to any particular implementation.

[0299] Fig.50b An example message sequence chart 5050 of NHD ranging (multicast DS-TWR) with request exchange by NRRR IE according to an embodiment of the disclosure is shown. Fig.50b The embodiment of the message sequence chart 5050 shown is for illustration only. Fig.50b The scope of the present disclosure is not limited to any particular implementation.

[0300] The ranging process of request exchange via NRRR IE is similar to Fig.42a and Figure 42b as well as Fig.44a and Figure 44b . Fig.49a and Fig.49b as well as Fig.50a and Fig.50b Message sequence charts for multicast SS-TWR and multicast DS-TWR are presented.

[0301] Similar to Fig.42a and Figure 42b , Fig.49a and Fig.49b An example multicast SS-TWR request exchange by NRRR IE is shown, which includes three periods corresponding to RC frames / messages, NHD ranging, and data / measurement reports. i " represents the i-th responder, and "I" represents the initiator. In this example, the first responder is the controller, and the others are controlled. At the beginning of the ranging round, the RC frame transmits the ranging configuration information and request related IE. For example, NRRR (R 1 |I) Indicates the AoA, reply time, or round trip measurement at the first responder requesting the initiator.

[0302] After the RC frame / message, NHD ranging begins. Since ranging scheduling is done by the RC frame or higher layers before NHD ranging, the device can know the identity of the remote end associated with the received RFRAME. The PHY layer of each device passes the timestamp of the received RFRAME to the MAC layer of each device so that this information can be used to calculate the reply time or round-trip time measurement.

[0303] After the NHD ranging period, the device is scheduled to send the requested information in the data / measurement report period, where there are ranging IEs such as RRTM IE, RRTD IE in the IEEE specification. For example, the initiator transmits the AoA and round-trip time to the first responder in RAD IE, RRTM IE, respectively. Responder-1 and responder-N embed the requested reply time in the RRTD IE to the initiator, respectively.

[0304] Similar to Fig.44a and Figure 44b , Fig.50a and Fig.50b An example multicast DS-TWR request exchange by NRRR IE is shown, which is similar to Fig.49a and Fig.49b The main difference is that there is a second polling message from the initiator in the NHD ranging cycle. At the beginning of a ranging round, a request is broadcast from the controller to the controlled.

[0305] For example, the initiator requests an AoA report from both Responder-1 and Responder-N. After NHD ranging, the device is scheduled to send a data report with the requested information. For example, the initiator sends the reply time and round trip time to Responder-1, and Responder-1 and Responder-N send back AoA reports to the initiator respectively. In this example, the controller plays the role of the responder. The controller can also be the initiator, and the corresponding message exchange diagram is simple and omitted here.

[0306] In one embodiment 4, a NHD ranging procedure with RMI IE for measurement reporting is provided.

[0307] Fig.51a An example message sequence chart 5100 of SP3 one-to-many SS-TWR according to an embodiment of the present disclosure is shown. Fig.51a The embodiment of the message sequence chart 5100 shown is for illustration only. Fig.51a The scope of the present disclosure is not limited to any particular implementation.

[0308] Fig.51b An example message sequence chart 5150 of SP3 one-to-many SS-TWR according to an embodiment of the present disclosure is shown. Fig.51b The embodiment of the message sequence chart 5150 shown in is for illustration only. Fig.51b The scope of the present disclosure is not limited to any particular implementation.

[0309] Fig.52a An example message sequence chart 5200 of SP3 one-to-many DS-TWR according to an embodiment of the present disclosure is shown. Fig.52a The embodiment of the message sequence chart 5200 shown is for illustration only. Fig.52a The scope of the present disclosure is not limited to any particular implementation.

[0310] Fig.52b An example message sequence chart 5250 of an SP3 one-to-many DS-TWR according to an embodiment of the present disclosure is shown. Fig.52b The embodiment of the message sequence chart 5250 shown is for illustration only. Fig.52b The scope of the present disclosure is not limited to any particular implementation.

[0311] During the development of the IEEE specification, the ranging measurement information IE (RMI IE) can be used to exchange time measurement information or AOA information after ranging transmission. This embodiment shows the ranging process of NHD SS-TWR and NHDDS-TWR through a message sequence chart (MSC). The present disclosure does not exclude other semantics of NHD ranging and ranging related IEs. For example, in the IEEE specification, NHD ranging is renamed to SP3 ranging (such as Fig.16 (For example, STS PPDU format 3 shown in (c)), and the NRRR IE for exchange request introduced in the above embodiment 3 is renamed as SP3 ranging request report IE (SRRR IE). Fig.51a and Fig.51b as well as Fig.52a and Fig.52b An example of SS-TWR and DS-TWRMSC for one-to-many ranging based on SP3 (or NHD) RFRAME is shown.

[0312] For the ranging control phase and SP3 ranging phase, Fig.51a and Fig.51b Keep with Fig.49a and Fig.49b Same. After the SP3 ranging phase, the RDEV is scheduled in the measurement report phase to send the requested information. For example, the initiator transmits the AOA and round trip time to the responder-1 via the RMI IE. The responder-1 and responder-N respectively embed the requested reply time in the RMI IE to the initiator.

[0313] Fig.52a and Fig.52b shows an example of one-to-many DS-TWR using SP3 ranging, which is similar to Fig.51a and Fig.51b The main difference is that there is a second SP3 RFRAME from the initiator during the ranging phase. The ranging control phase and the SP3 ranging phase remain the same. Fig.50a and Fig.50b same.

[0314] At the beginning of the ranging round, a request is broadcast from the controller to the controlled. For example, the initiator requests an AOA report from both Responder-1 and Responder-N by setting the RAOA field of the SRRR IE to 1. After the SP3 ranging phase, the RDEV is scheduled to send its data report with the requested information via the RMI IE. For example, the initiator sends the reply time and round trip time to Responder-1, and Responder-1 and Responder-N send AOA reports back to the initiator, respectively. In this example, the controller plays the role of the responder. The controller can also be the initiator.

[0315] Fig.53 A flowchart of a method 5300 for secure ranging operation according to an embodiment of the present disclosure is shown, and the method may be executed by a transmitting device. Fig.53 The illustrated embodiment of method 5300 is for illustration only. Fig.53 The scope of the present disclosure is not limited to any particular implementation.

[0316] like Fig.53 As shown, the method 5300 starts at step 5302. In step 5302, the transmitting device determines at least one receiving device in a group of receiving devices participating in a ranging operation.

[0317] Subsequently, in step 5304, the transmitting device identifies a scrambled timestamp sequence (STS) physical layer protocol data unit (PPDU) format 3 (SP3) ranging request report information element (SRRRIE) of at least one receiving device in the group of receiving devices.

[0318] In one embodiment, the SRRR IE includes: a field for requester address presence (RAP), which indicates the presence of the requester address field; a field for provider address presence (PAP), which indicates the presence of the provider address field; a field for indicating whether an arrival angle report (RAOA) is required; a field for indicating whether a reply time report (RRT) is required; a field for indicating whether a round-trip time report (RRTT) is required; a field for indicating whether a flight time report (RTOF) is required; a field for reserved information, which indicates a reserved portion for future use; a field for a requester address, which transmits the address of a device requesting the information indicated by RAOA, RRT, RRTT and RTOF; and a field for a provider address, which indicates the address of a device measuring the requested information indicated by RAOA, RRT, RRTT and RTOF.

[0319] In such embodiments, the lengths of the field for the provider address and the field for the requester address are determined from the length of the SRRR IE; the reply time and the round-trip time are calculated based on a timestamp counted at a media access layer (MAC); and corresponding to a value of 1 for the RRT in the SRRR IE, a response of the reply time from at least one receiving device in the receiving device group is separately embedded in a ranging measurement information IE (RMI IE) received from at least one receiving device in the receiving device group.

[0320] Finally, in step 5306, the transmitting device sends a ranging control message (RCM) including the SRRR IE to at least one receiving device in the group of receiving devices participating in the ranging operation using an in-band mechanism or an out-of-band mechanism. In step 5306, the RCM including the SRRR IE is sent in the ranging operation scheduled in time.

[0321] In one embodiment, the transmitting device configures the time-scheduled ranging operation via an IE in a static or dynamic scheme.

[0322] In one embodiment, the transmitting device identifies a multi-node SP3 ranging including the transmitting device and at least two receiving devices in a group of receiving devices, and transmits an RCM including a SRRR IE that does not include a requester address field.

[0323] In one embodiment, the transmitting device transmits an RCM including two or more SRRR IEs to at least one receiving device in the receiving device group to distinguish different device pairs in the receiving device group.

[0324] In one embodiment, for single-sided two-way ranging (SS-TWR) with multi-node SP3 ranging, a transmitting device sends an RCM including ranging configuration information and an SRRR IE to at least one receiving device in a receiving device group at the beginning of a ranging round (RR) to exchange information requests for one or more ranging pairs; multi-node SP3 ranging is scheduled via an in-band or out-of-band mechanism; and each time slot for multi-node SP3 ranging is allocated to a ranging device (RDEV).

[0325] In one embodiment, for dual-side two-way ranging (DS-TWR) with SP3 packets, a transmitting device sends an RCM including ranging configuration information and an SRRR IE to at least one receiving device in a receiving device group in a broadcast manner at the beginning of an RR to exchange information requests for one or more ranging pairs; and receives a response with an RMI IE corresponding to the ranging configuration information and the request IE from at least one receiving device in the receiving device group.

[0326] Although the disclosure has been described with exemplary embodiments, various changes and modifications may be conceived by those skilled in the art. The disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. Any description in this application should not be construed as implying that any particular element, step or function is an essential element that must be included within the scope of the claims.

Claims

1. A control device in a wireless communication system, the control device include: Transceiver; as well as at least one processor coupled to the transceiver and configured to: Identify a scrambled timestamp sequence STS physical layer protocol data unit PPDU format 3SP3 ranging request report information element SRRRIE for the controlled device, wherein the SRRRIE indicates whether specific information is requested, sending a ranging control message RCM including the SRRRIE to the controlled device, and A ranging operation is performed with the controlled device using an SP3 packet, wherein the SP3 packet has no physical layer header or data in a physical layer protocol data unit PPDU.

2. The control device according to claim 1, in, The at least one processor is further configured to configure a time-scheduled ranging operation via an IE to exchange information between the control device and the controlled device based on a time slot.

3. The control device according to claim 1, in, The SRRRIE includes: A field for indicating whether a requester address field exists in the SRRR IE or the size of the requester address field; A field for indicating whether a provider address field exists in the SRRR IE or the size of the provider address field; A field to indicate whether angle of arrival reporting is required; A field to indicate whether a response time report is required; A field to indicate whether round-trip time reporting is required; and A field to indicate whether flight time reporting is required; Wherein, based on a field for indicating whether a requester address field exists in the SRRR IE or a size of the requester address field, the SRRR IE further includes the requester address field, and Wherein, based on a field for indicating whether a provider address field exists in the SRRR IE or a size of the provider address field, the SRRR IE further includes the provider address field.

4. The control device according to claim 3, in: The reply time and the round trip time are calculated based on time information of a ranging frame RFRAME identified at a medium access control MAC layer.

5. The control device according to claim 3, in, In the case where the value of the field in the SRRR IE for indicating whether the arrival angle report is required is 1, the arrival angle is embedded in the ranging measurement information RMIIE.

6. The control device according to claim 3, in, In case that the control device requests the specific information, the at least one processor is further configured to send an RCM including an SRRRIE excluding the requester address field.

7. The control device according to claim 1, in, The RCM includes two or more SRRR IEs to distinguish different device pairs from the controlling device and a group of controlled devices participating in a ranging operation.

8. The control device according to claim 1, in, For unilateral two-way ranging SS-TWR using multi-node SP3 ranging: The at least one processor is further configured to send an RCM including ranging configuration information and the SRRRIE to the controlled device at the beginning of a ranging round, wherein an in-band or out-of-band mechanism is used for the multi-node SP3 ranging, and Each time slot used for the multi-node SP3 ranging is allocated to a device participating in the ranging operation.

9. The control device according to claim 1, in, For dual-directional ranging (DS-TWR) using SP3 packets: The at least one processor is further configured to: At the beginning of a ranging round, an RCM including ranging configuration information and the SRRRIE is sent to the controlled device in a broadcast manner, and A response having ranging measurement information RMIIE corresponding to the ranging configuration information and the SRRR IE is received from the controlled device.

10. A controlled device in a wireless communication system, the controlled device include: Transceiver; as well as at least one processor coupled to the transceiver and configured to: receiving a ranging control message RCM including a scrambled time stamp sequence STS physical layer protocol data unit PPDU format 3SP3 ranging request report information element SRRR IE from a control device, wherein the SRRRIE indicates whether specific information is requested, identifying the SRRRIE based on the RCM, and A ranging operation is performed with the control device using an SP3 packet having no physical layer header or data in a physical layer protocol data unit PPDU.

11. The controlled device according to claim 10, in, The SRRR IE includes: A field for indicating whether a requester address field exists in the SRRR IE or the size of the requester address field; A field for indicating whether a provider address field exists in the SRRR IE or the size of the provider address field; A field to indicate whether angle of arrival reporting is required; A field to indicate whether a response time report is required; A field to indicate whether round-trip time reporting is required; and A field to indicate whether flight time reporting is required; Wherein, based on a field for indicating whether a requester address field exists in the SRRR IE or a size of the requester address field, the SRRR IE further includes the requester address field, and Wherein, based on a field for indicating whether a provider address field exists in the SRRR IE or a size of the provider address field, the SRRR IE further includes the provider address field.

12. The controlled device according to claim 11, in: The reply time and the round trip time are calculated based on time information of a ranging frame RFRAME identified at a medium access control MAC layer.

13. The controlled device of claim 10, wherein the RCM comprises two or more SRRR IEs to distinguish different device pairs from the controlling device and a group of devices participating in a ranging operation.

14. A method for operating a control device in a wireless communication system, the method include: Identify a scrambled timestamp sequence STS physical layer protocol data unit PPDU format 3SP3 ranging request report information element SRRRIE for the controlled device, the SRRR IE indicating whether specific information is requested, sending a ranging control message RCM including the SRRRIE to the controlled device, and A ranging operation is performed with the controlled device using an SP3 packet, wherein the SP3 packet has no physical layer header or data in a physical layer protocol data unit PPDU.