Architecture and method for acknowledging multiple messages in UWB communication and ranging systems

Abstract

A method and apparatus for a first network entity in a wireless communication system supporting ranging capability are provided. The method and apparatus include: identifying one or more ranging cycles for sending a ranging control message (RCM) in a ranging block, the RCM having a multiple message reception confirmation request (MMRCR) for sending at least one first message, the at least one first message including at least one of a group of ranging messages or a group of ranging assistance data messages; sending the RCM with the MMRCR to a second network entity; sending ranging assistance data to the second network entity in at least one ranging cycle in one or more ranging cycles after the RCM, wherein the ranging assistance data is associated with the MMRCR; and receiving a ranging multiple message reception confirmation RMMRC corresponding to the sending of the at least one first message from the second network entity.

Description

Technical Field

[0001] The present disclosure generally relates to an architecture and method for acknowledging multiple messages in a UWB communication and ranging system. Background Art

[0002] A peer-aware communication (PAC) network is a fully distributed communication network that allows direct communication between PAC devices (PDs). A PAC device is an electronic device with communication capabilities. In addition, a PAC device may also have ranging capabilities. A PAC device may be referred to as a ranging device (RDEV), or an enhanced ranging device (ERDEV), or a secure ranging device (SRDEV) or any other similar name. RDEV, ERDEV or SRDEV may be part of an access point (AP), a station (STA), an eNB, a gNB, a UE or any other communication node with ranging capabilities as defined in the IEEE standard specification. A PAC network may adopt several topologies such as a mesh, a star, etc. to support interactions between PDs for various services. Summary of the invention

[0003] [Technical issues]

[0004] Embodiments of the present disclosure provide an architecture and method for acknowledging multiple messages in a UWB communication and ranging system.

[0005] [Technical solution]

[0006] In one embodiment, a first network entity supporting ranging capability in a wireless communication system is provided. The first network entity includes a processor, the processor being configured to identify one or more ranging cycles for sending a ranging control message (RCM) in a ranging block, the RCM having a multiple message reception confirmation request (MMRCR) for the transmission of at least one first message, the at least one first message including at least one of a group of ranging messages or a group of ranging assistance data messages. The first network entity also includes a transceiver operably connected to the processor, the transceiver being configured to: send the RCM with the MMRCR to a second network entity; send ranging assistance data to the second network entity in at least one ranging cycle of the one or more ranging cycles after the RCM, wherein the ranging assistance data is associated with the MMRCR; and receive a ranging multiple message reception confirmation (RMMRC) corresponding to the transmission of the at least one first message from the second network entity. 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 in conjunction with the accompanying drawings, wherein like reference numerals represent like components:

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

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

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

[0011] FIG4a shows a high-level schematic diagram of an OFDMA transmission path according to an embodiment of the present disclosure;

[0012] FIG4 b shows a high-level schematic diagram of an OFDMA receive path according to an embodiment of the present disclosure;

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

[0014] Figure 6 An exemplary ranging configuration according to an embodiment of the present disclosure is shown;

[0015] Figure 7 An exemplary general ranging loop structure according to an embodiment of the present disclosure is shown;

[0016] Figure 8 An exemplary ranging controller, a controlled person, an initiator, and a responder according to an embodiment of the present disclosure are shown;

[0017] Fig. 9 An exemplary Advanced Ranging Control IE defined in 802.15.4z according to an embodiment of the present disclosure is shown;

[0018] Fig.10 An exemplary Advanced Ranging Control IE content field format as defined in 802.15.4z according to an embodiment of the present disclosure is shown;

[0019] Fig.11 An exemplary ranging scheduling IE according to an embodiment of the present disclosure is shown;

[0020] Fig.12 shows an exemplary row of a ranging schedule according to an embodiment of the present disclosure;

[0021] Fig.13 An exemplary message sequence chart for one-to-one multiple message acknowledgement (MMACK) according to an embodiment of the present disclosure is shown;

[0022] Fig.14 An exemplary message sequence chart for multicast or multi-node message acknowledgement (MMACK) according to an embodiment of the present disclosure is shown;

[0023] Fig.15An exemplary message sequence diagram for multiple many-to-many messages according to an embodiment of the present disclosure is shown;

[0024] Fig.16a An exemplary multiple message acknowledgement request bit for indicating MMAR in an ARC IE according to an embodiment of the present disclosure is shown;

[0025] Fig.16b Another exemplary multiple message acknowledgement request bit indicating MMAR in the ARC IE according to an embodiment of the present disclosure is shown;

[0026] Fig.17a An exemplary flow chart of using the MMAR or MMRCR bit in the ARC IE to indicate a multiple message confirmation IE according to an embodiment of the present disclosure is shown;

[0027] Fig.17b Another exemplary flow chart showing the use of the MMAR or MMRCR bit in the ARC IE to indicate a multiple message confirmation IE according to an embodiment of the present disclosure;

[0028] Fig.18 shows an exemplary format for an MMAR indicator using a one-bit field of the ARC IE content field according to an embodiment of the present disclosure;

[0029] Fig.19a An exemplary flow chart showing the use and / or reuse of a one-bit field to indicate MMAR in an ARC IE according to an embodiment of the present disclosure is shown;

[0030] Fig.19b Another exemplary flow chart showing the use and / or reuse of a one-bit field to indicate MMAR in an ARC IE according to an embodiment of the present disclosure;

[0031] Fig. 20 An exemplary flow chart of using IE to indicate multi-message confirmation according to an embodiment of the present disclosure is shown;

[0032] Fig.21 An exemplary flow chart of determining the length of a multi-message confirmation bitmap via a ranging scheduling IE according to an embodiment of the present disclosure is shown;

[0033] Fig. 22 An exemplary content field of an IE according to an embodiment of the present disclosure is shown, which is used to transmit the length of the MMACK bitmap;

[0034] Fig.23 An exemplary content field of an IE according to an embodiment of the present disclosure is shown, which is used for multi-message confirmation;

[0035] Fig.24shows an exemplary content field of an IE for an MMACK with an address being acknowledged according to an embodiment of the present disclosure;

[0036] Fig.25 shows an exemplary row of an MMACK table according to an embodiment of the present disclosure;

[0037] Fig.26 shows an exemplary RMMRC IE content field format according to an embodiment of the present disclosure;

[0038] Fig. 27 shows an exemplary MMRC list element format according to an embodiment of the present disclosure; and

[0039] Fig.28 An exemplary flow chart of a method for confirming multiple messages according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0040] In one embodiment, a first network entity supporting ranging capability in a wireless communication system is provided. The first network entity includes a processor, the processor being configured to identify one or more ranging cycles for sending a ranging control message (RCM) in a ranging block, the RCM having a multiple message reception confirmation request (MMRCR) for the transmission of at least one first message, the at least one first message including at least one of a group of ranging messages or a group of ranging assistance data messages. The first network entity also includes a transceiver operably connected to the processor, the transceiver being configured to: send the RCM with the MMRCR to a second network entity; send ranging assistance data to the second network entity in at least one ranging cycle of the one or more ranging cycles after the RCM, wherein the ranging assistance data is associated with the MMRCR; and receive a ranging multiple message reception confirmation (RMMRC) corresponding to the transmission of the at least one first message from the second network entity.

[0041] In another embodiment, a second network entity supporting ranging capability in a wireless communication system is provided. The second network entity includes a processor configured to identify one or more ranging cycles for receiving a ranging control message (RCM) in a ranging block, the RCM having a multiple message reception confirmation request (MMRCR) for reception of at least one first message, the at least one first message including at least one of a group of ranging messages or a group of ranging assistance data messages. The second network also includes a transceiver configured to: receive the RCM with the MMRCR from the first network entity; and receive ranging assistance data from the first network entity in at least one ranging cycle of the one or more ranging cycles after the RCM, wherein the ranging assistance data is associated with the MMRCR; and send a ranging multiple message reception confirmation (RMMRC) corresponding to reception of the at least one first message to the first network entity.

[0042] In yet another embodiment, a method for a first network entity supporting ranging capability in a wireless communication system is provided. The method includes: identifying one or more ranging cycles for sending a ranging control message (RCM) in a ranging block, the RCM having a multiple message reception confirmation request (MMRCR) for the transmission of at least one first message, the at least one first message including at least one of a group of ranging messages or a group of ranging assistance data messages; sending the RCM with the MMRCR to a second network entity; sending ranging assistance data to the second network entity in at least one ranging cycle in the one or more ranging cycles after the RCM, wherein the ranging assistance data is associated with the MMRCR; and receiving a ranging multiple message reception confirmation RMMRC corresponding to the transmission of the at least one first message from the second network entity.

[0043] Other technical features will be apparent to those skilled in the art from the following drawings, description and claims.

[0044] Invention Mode

[0045] Before proceeding to 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 "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives include direct and indirect communication. The term "ranging" and its derivatives mean that the basic measurement for ranging between devices is achieved by the sending and receiving of one or more messages. The terms "include" and "comprise" and their derivatives are intended to include without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, included in, connected to or connected with, coupled to or coupled with, communicable with, collaborate with, intertwine, parallel, approach, bound to or bound with, have, have the characteristics of, have a relationship with, etc. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such controllers may be implemented in hardware, a combination of hardware and software, and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether local or remote. The phrase "at least one," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0046] 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 is included 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 appropriate computer-readable program codes. 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 excludes wired, wireless, optical or other communication links that transmit temporary electrical or other signals. A non-transitory computer-readable medium includes a medium that can permanently store data and a medium that can store data and then rewrite data, such as a rewritable optical disc or an erasable storage device.

[0047] Definitions for certain other words and phrases are provided throughout this patent document. Those skilled in the art should understand that in many, if not most, instances, such definitions apply to both past and future tenses of such defined words and phrases.

[0048] Discussed below Figures 1 to 28 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 invention can be implemented in any suitably arranged system or device.

[0049] The following documents and standard descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: (i) Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Peer-Aware Communications, IEEE Std 802.15.8, 2017, and (ii) Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-rate Wireless Personal Area Networks (WPANs), Amendment 1: Addition of Alternative Physical Layers, IEEE Std 802.15.4a (2007).

[0050] Various aspects, features and advantages of the present disclosure will become apparent from the following detailed description simply by illustrating a number of specific embodiments and implementations, including the best mode contemplated for carrying out the present disclosure. The present disclosure is also capable of other and different embodiments, and its several details may be modified in various obvious respects, all without departing from the spirit and scope of the present disclosure. Therefore, the drawings and description are to be regarded as illustrative in nature and not restrictive. The present disclosure is shown in an exemplary manner and not in a limiting manner in the figures of the accompanying drawings.

[0051] The following Figure 1 -4b describes various embodiments of implementing and using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques in a wireless communication system. Figure 1-3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the disclosure may be implemented in any suitably arranged communications system.

[0052] Figure 1 An exemplary 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.

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

[0054] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UE) within coverage area 120 of gNB 102. The first plurality of UEs include: 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 Wi-Fi 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 computer, 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 the gNBs 101-103 may communicate with each other and with the UEs 111-116 using 5G, LTE, LTE-A, WiMAX, Wi-Fi, or other wireless communication technologies.

[0055] Depending on the network type, the term "base station" or "BS" may refer to any component (or collection 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 Wi-Fi access point (AP), or other wirelessly enabled devices. A base station may provide wireless access according to one or more wireless communication protocols, for example, 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 a network infrastructure component that provides wireless access to a remote terminal. 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 equipment". 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).

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

[0057] As described in greater detail below, one or more of the UEs 111-116 include circuitry, programming, or a combination thereof for acknowledging a plurality of messages in a UWB communication and ranging system. 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 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 types of data networks.

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

[0059] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-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.

[0060] RF transceivers 210a-210n receive incoming RF signals from antennas 205a-205n, such as signals sent by UEs in network 100. RF transceivers 210a-210n downconvert the incoming RF signals to produce 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.

[0061] The TX processing circuit 215 receives analog or digital data (e.g., voice data, website data, email, or interactive video game data) from the controller / processor 225. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the output baseband data to produce a processed baseband or IF signal. The RF transceivers 210a-210n receive the processed baseband or IF signal from the output of the TX processing circuit 215 and up-convert the baseband or IF signal to an RF signal that is transmitted via the antennas 205a-205n.

[0062] 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 via the RF transceivers 210a-210n, the RX processing circuitry 220, and the TX processing circuitry 215 in accordance with well-known principles. The controller / processor 225 may also support additional functionality, such as more advanced wireless communication functionality.

[0063] For example, the controller / processor 225 may support beamforming or directional routing operations, in which the output signals from the multiple antennas 205a-205n are weighted differently to effectively steer the output signals in a desired direction. The controller / processor 225 may support any of a variety of other functions in the gNB 102.

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

[0065] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or via a network. The interface 235 can support communication over any appropriate wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., 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 with a larger network (e.g., the Internet) via a wired or wireless local area network or via a wired or wireless connection. The interface 235 includes any suitable structure that supports communication over a wired or wireless connection, such as an Ethernet or RF transceiver.

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

[0067] 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 functionality for routing data between different network addresses. As another specific example, although shown as including a single instance of the TX processing circuit 215 and a single instance of the RX processing circuit 220, the gNB 102 may include multiple instances of each component (e.g., one instance per 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.

[0068] Figure 3 An exemplary UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown is for illustration only. Figure 1 UEs 111-115 may have the same or similar configurations. However, UEs may have a variety of configurations, and Figure 3 The scope of the present disclosure is not limited to any particular implementation of a UE.

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

[0070] RF transceiver 310 receives an incoming RF signal from antenna 305 transmitted by a gNB of network 100. RF transceiver 310 downconverts the incoming RF signal to produce 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 transmits the processed baseband signal to speaker 330 (e.g., for voice data) or processor 340 for further processing (e.g., for website browsing data).

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

[0072] The processor 340 may include one or more processors or other processing devices and executes 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 through 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.

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

[0074] Processor 340 is also coupled to touch screen 350 and display 355. An operator of UE 116 may input data into UE 116 using touch screen 350. Display 355 may be a liquid crystal display, light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website.

[0075] 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).

[0076] although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 The 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 also be configured to operate as other types of mobile or stationary devices.

[0077] FIG4a is a high-level schematic diagram of a transmit path circuit. For example, the transmit path circuit can be used for orthogonal frequency division multiple access (OFDMA) communications. FIG4b is a high-level schematic diagram of a receive path circuit. For example, the receive path circuit can be used for orthogonal frequency division multiple access (OFDMA) communications. In FIG4a and FIG4b, for downlink communications, the transmit path circuit can be implemented in a base station (gNB) 102 or a relay station, and the receive path circuit can be implemented in a user equipment (e.g., Figure 1 In other examples, for uplink communications, the receive path circuit 450 may be implemented in a base station (e.g., Figure 1The 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 The method is implemented in user equipment 116).

[0078] The transmit path circuitry includes a channel coding and modulation block 405, a serial to parallel (S to P) block 410, an inverse fast Fourier transform (IFFT) block of size N 415, a parallel to serial (P to S) 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 (S to P) block 465, a fast Fourier transform (FFT) block of size N 470, a parallel to serial (P to S) block 475, and a channel decoding and demodulation block 480.

[0079] At least some of the components in Figures 4a 400 and 4b 450 may be implemented in software, while other components may be implemented by configurable hardware or by a mixture of software and configurable hardware. In particular, it should be noted that the FFT block and IFFT block described in this disclosure may be implemented as a configurable software algorithm, where the value of size N may be modified depending on the implementation.

[0080] In addition, although the present disclosure relates 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 a discrete Fourier transform (DFT) function and an inverse discrete Fourier transform (IDFT) function, respectively. It is understood that for DFT and IDFT functions, the value of the N variable can be any integer (i.e., 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of the N variable can be any integer as a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

[0081] 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 modulates (e.g., quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) the input bits to produce a frequency domain modulation symbol sequence. The serial to parallel block 410 converts (i.e., demultiplexes) the serial modulation symbols into parallel data to produce N parallel symbol streams, where N is the size of the IFFT / FFT 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. Then, the add cyclic prefix block 425 inserts a 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.

[0082] The transmitted RF signal arrives at UE 116 after passing through the wireless channel, and operations reverse to those at gNB 102 are performed. Downconverter 455 downconverts the received signal to baseband frequency and removes the cyclic prefix block 460 removes the cyclic prefix to produce a serial time-domain baseband signal. Serial to parallel block 465 converts the time-domain baseband signal to 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 block 475 converts the parallel frequency-domain signals to a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

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

[0084] A Peer Aware Communication (PAC) network is a fully distributed communication network that allows direct communication between PAC devices (PDs). A Wireless Personal Area Network (WPAN) or simply a Personal Area Network (PAN) can be a fully distributed communication network. A WPAN or PAN is a communication network that allows wireless connections between PAN devices (PDs). PAN devices and PAC devices can be used interchangeably, as a PAC network is also a PAN network and vice versa.

[0085] The PAC network can adopt several topologies such as mesh, star and / or peer to support the interaction between PDs for various services. Although the present disclosure uses PAC networks and PDs as examples to illustrate and describe the present disclosure, it should be noted that the present disclosure is not limited to these networks. The general concepts described in the present disclosure can be used in various types of networks with different types of scenarios.

[0086] Figure 5 An exemplary electronic device 501 according to an embodiment of the present disclosure is shown. Figure 5 The embodiment of electronic device 501 shown is for illustration only. Figure 5 The scope of the present disclosure is not limited to any particular implementation.

[0087] PDs may be electronic devices with communication and ranging capabilities. An electronic device may be referred to as a ranging device (RDEV), or an enhanced ranging device (ERDEV), or a secure ranging device (SRDEV), or any other similar name according to IEEE standard specifications. An RDEV, ERDEV, or SRDEV may be part of an access point (AP), a station (STA), an eNB, a gNB, a UE, or any other communication node with ranging capabilities.

[0088] Reference Figure 5 , the electronic device 501 in the network environment 500 can communicate with the electronic device 502 via the first network 598 (e.g., a short-range wireless communication network), or communicate with the electronic device 504 or the server 508 via the second network 599 (e.g., a long-range wireless communication network). According to one embodiment, the electronic device 501 can communicate with the electronic device 504 via the server 508.

[0089] According to an 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 tactile module 579, a camera 580, a power management 588, a battery 589, a communication interface 590, a user identification module (SIM) 596, or an antenna 597. In some embodiments, at least one (e.g., display device 560 or camera 580) component 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).

[0090] 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 invention, as at least part of the data processing or calculation, the processor 520 may load commands or data received from another component (e.g., sensor 576 or communication interface 590) into the volatile memory 532, process the commands or data stored in the volatile memory 532, and store the resulting data in the non-volatile memory 534.

[0091] According to an 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)), and the auxiliary processor 523 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 specified function. The auxiliary processor 523 may be implemented to be independent of the main processor 521, or as part of the main processor 521.

[0092] When the main processor 521 is in an inactive (e.g., sleeping) state, the auxiliary processor 523, instead of the main processor 521, may control at least some of the functions or states related to at least one of the components of the electronic device 501 (e.g., the display device 560, the sensor 576, or the communication interface 590), or when the main processor 521 is in an active state (e.g., executing an application), control at least some of the functions or states related to at least one of the components of the electronic device 501 (e.g., the display device 560, the sensor 576, or the communication interface 590) together with the main processor 521. 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., a camera 580 or a communication interface 190) that is functionally related to the auxiliary processor 523.

[0093] 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., 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.

[0094] 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 an application program 546 .

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

[0096] The sound output device 555 can output sound signals 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 to connect calls. According to one embodiment, the receiver may be implemented as being independent of the speaker, or as a part of the speaker.

[0097] The display device 560 can 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 hologram device, or a projector, and a control circuit for controlling a corresponding one of the display, the hologram device, and the projector. According to one embodiment, the display device 560 may include a touch circuit suitable for detecting a touch, or a sensor circuit (e.g., a pressure sensor) suitable for measuring the strength of the force caused by the touch.

[0098] 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 directly (e.g., using a wired line) output sound via a sound output device 555 or an earphone of an external electronic device (e.g., the electronic device 502), or wirelessly couple with the electronic device 501 to output sound.

[0099] The sensor 576 may detect an operating state (e.g., power or temperature) of the electronic device #01 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.

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

[0101] The connection terminal 578 may include a connector through which the electronic device 501 can be physically connected to an external electronic device (e.g., the electronic device 502). According to an 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).

[0102] The haptic module 579 may convert the electrical signal into mechanical stimulation (eg, vibration or motion) or electrical stimulation, which may be recognized by the user through his sense of touch or kinesthetic sense. According to one embodiment, the haptic module 579 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0103] The camera 580 may capture a still image or a moving image. According to an embodiment of the present disclosure, the camera 580 may include one or more lenses, an image sensor, an image signal processor, or a flash.

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

[0105] The communication interface 590 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (e.g., electronic device 502, electronic device 504, or server 508), and perform communication via the established communication channel. The communication interface 590 may include one or more communication processors that operate independently of the processor 520 (e.g., application processor (AP)) and support direct (e.g., wired) communication or wireless communication.

[0106] According to an 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))).

[0107] These various 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) separated from each other. The wireless communication interface 592 may use user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 596 to identify and authenticate the electronic device 501 in the communication network (e.g., the first network 598 or the second network 599).

[0108] The antenna 597 may send or receive a signal 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 formed 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 a communication scheme used in a communication network (e.g., a first network 198 or a second network 599) may be selected from the plurality of antennas, for example, by the communication interface 590 (e.g., a wireless communication interface 592). Then, a signal or power may 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)) may be additionally formed as part of the antenna 597.

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

[0110] According to an embodiment of the present disclosure, a command or data may be sent or received between an electronic device 501 and an external electronic device 504 via a server 508 coupled to a 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 on the electronic device 501 may be performed on one or more of the external electronic devices 502, 504, or 508. For example, if the electronic device 501 can automatically perform a function or service, or in response to a request from a user or another device, the electronic device 501 may request one or more external electronic devices to perform at least a part of the function or service without performing the function or service, or may request one or more external electronic devices to perform at least a part of the function or service in addition to performing the function or service. The one or more external electronic devices receiving the request may perform at least a part 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 with or without further processing of the result as at least a part of the reply to the request. To this end, for example, cloud computing, distributed computing, or client-server computing technology may be used.

[0111] 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 an embodiment of the present disclosure, the electronic device is not limited to those described above.

[0112] The various embodiments described herein may be implemented as software (e.g., program 140) that includes one or more instructions stored in a machine (e.g., electronic device 501) readable storage medium (e.g., internal memory 536 or external memory 538). 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 instruction 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 executed 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" only means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between the case where data is semi-permanently stored in the storage medium and the case where data is temporarily stored in the storage medium.

[0113] According to an embodiment of the present disclosure, the method according to each embodiment of the present disclosure may be included in and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. 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 (e.g., downloading or uploading), or directly 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, a server of an application store, or a relay server.

[0114] According to various embodiments of the present disclosure, each component (e.g., module or program) of the above-mentioned components 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., modules or programs) 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 tentatively, or one or more operations may be performed or omitted in a different order, or one or more other operations may be added.

[0115] A ranging block is a time period used for ranging. Each ranging block includes an integer multiple of ranging cycles, where a ranging cycle is a time period to complete a complete ranging cycle involving a set of RDEVs participating in ranging measurements. Each ranging cycle is further subdivided into an integer number of ranging slots, where a ranging slot is a time period of sufficient length for transmitting at least one RFRAME.

[0116] Figure 6 An exemplary ranging configuration 600 is shown in accordance with an embodiment of the present disclosure. Figure 6 The embodiment of the ranging configuration 600 shown in FIG. 6 is for illustration only. Figure 6 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the ranging configuration 600 can be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, the ranging configuration 600 may be configured by a network entity (e.g., Figure 1 BS 101-103 as shown, and Figure 1 Terminals 111-116) shown are used.

[0117] Figure 6 The ranging block structure is shown, where the ranging block is divided into N ranging cycles, each ranging cycle consisting of M ranging slots.

[0118] The general ranging cycle structure includes a ranging control period, in which a ranging control message is sent to configure the ranging cycle. The ranging control period is followed by one or more ranging periods and data periods. These data periods usually include the use of certain information elements (IEs) defined in the standard to transmit ranging related data. The most common ranging cycle structure is as follows Figure 7 shown.

[0119] Figure 7 An exemplary general ranging loop structure 700 is shown according to an embodiment of the present disclosure. Figure 7 The illustrated embodiment of the general ranging loop structure 700 is for illustration only. Figure 7 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the general ranging loop structure 700 can be used by a controller, a controlled person, an initiator and / or a responder, such as Figure 8 In one embodiment, a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 The terminals 111-116) shown may use a general ranging cycle structure 700.

[0120] In the present disclosure, the following nomenclature is used: controller: ranging device that defines and controls ranging parameters by sending ranging control messages in a ranging control period; controlee: ranging device that utilizes ranging parameters received from the controller; initiator: ranging device that initiates ranging exchange by sending the first message of the exchange or by a device sending ranging assistance data (under payload) / data; and responder: ranging device that receives ranging assistance data (under payload) / data and / or responds to a message received from the initiator.

[0121] Figure 8 An exemplary ranging controller, controlled party, initiator, and responder 800 according to an embodiment of the present disclosure is shown. Figure 8 The embodiments of ranging controller, controlled persons, initiators, and responders 800 shown in FIG. 8 are for illustration only. Figure 8 The scope of the present disclosure is not limited to any particular implementation.

[0122] The relevant IE for this is the Advanced Ranging Control IE, as is typically sent during a ranging control period. The Advanced Ranging Control IE (ARC IE) is used by the controller to send ranging configuration 22 information to the controller (in a unicast frame) or to multiple controlees (in a multicast / broadcast frame). The content field of the ARC IE may be formatted as follows: Fig. 9 shown.

[0123] Fig. 9 An exemplary Advanced Ranging Control IE as defined in 802.15.4z 900 is shown in accordance with an embodiment of the present disclosure. Fig. 9 The embodiment of the Advanced Ranging Control IE defined in 802.15.4z 900 shown in FIGURE 9 is for illustration only. Fig. 9 The scope of the present disclosure is not limited to any particular implementation. Figure 8 As shown, the controller, controlled party, initiator and / or responder may use the Advanced Ranging Control IE defined in 802.15.4z 900. In one embodiment, a network entity (e.g., Figure 1BS 101-103 as shown, Figure 1 Terminals 111-116) shown may use the Advanced Ranging Control IE defined in 802.15.4z900.

[0124] The ranging mode values ​​are shown in Table 1. Other details of the ARC IE can be found in the IEEE standard specification.

[0125] Table 1 Ranging mode values

[0126] Distance measurement mode value Ranging frame type and ranging method 0 Unsafe OWR 1 Unsafe SS-TWR 2 Unsafe DS-TWR 4 Secure OWR with payload 5 Safe SS-TWR with Payload 6 Secure DS-TWR with payload 7 Secure OWR without payload 8 Safety SS-TWR without payload 9 Safety DS-TWR without payload

[0127] The optional structure of the Advanced Ranging Control IE based on the revision in 802.15.4z is as follows Fig.10 shown.

[0128] Fig.10 FIG. 1 shows an exemplary Advanced Ranging Control IE content field format as defined in 802.15.4z 1000 according to an embodiment of the present disclosure. Fig.10 The embodiment of the Advanced Ranging Control IE Content Field Format defined in 802.15.4z1000 shown in FIGURE 1 is for illustration only. Fig.10 The scope of the present disclosure is not limited to any particular implementation. Figure 8 As shown, the controller, controlled party, initiator and / or responder may use the Advanced Ranging Control IE Content Field format defined in 802.15.4z 1000. In one embodiment, a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 The terminals 111 - 116 shown may use the Advanced Ranging Control IE Content field format defined in 802.15.4z 1000 .

[0129] For schedule-based ranging with multiple devices, the Ranging Schedule (RS) IE may be used to convey resource allocations including, for example, Fig.11 The RS table and RS table length fields are shown. The RS table length field indicates the number of rows in the RS table.

[0130] Fig.11 An exemplary ranging scheduling IE 1100 according to an embodiment of the present disclosure is shown. Fig.11 The illustrated embodiment of the ranging scheduling IE 1100 is for illustration only. Fig.11 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the ranging scheduling IE 1100 can be used by a controller, a controlled person, an initiator and / or a responder, such as Figure 8 In one embodiment, the ranging scheduling IE 1100 may be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0131] Fig.12 An exemplary row of the ranging schedule 1200 is shown according to an embodiment of the present disclosure. Fig.12 The embodiment of the rows of the ranging schedule 1200 shown in FIG. 1 is for illustration only. Fig.12 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the rows of the ranging schedule 1200 can be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, the rows of the ranging schedule table 1200 may be populated by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0132] Each row of the RS table includes a slot index field for the time slot, an address field for the device assigned to the time slot, and a device type field for indicating the role of the assigned device, such as Fig.12 As shown. Depending on the device capabilities and vendor specifications, different types of addresses can be used. If the device type for a particular address is 0, the device is a responder. Otherwise, the device is an initiator.

[0133] The ranging method field of the ARC IE may be used to indicate that the current ranging cycle is used for ranging assistance information exchange as shown in Table 2.

[0134] Table 2 Ranging method field values

[0135] Ranging Method Field Value The selected ranging method 00 One-way ranging 01 One-way two-way distance measurement 10 Dual-side bidirectional distance measurement 11 Range-Aiding Information Exchange

[0136] In one embodiment, a ranging cycle multiple message acknowledgement is provided.

[0137] The ranging cycle includes several message exchanges between the controller, the controlled, the initiator and the responder. These messages may include ranging related frames (RFRAMES), or when other possible exchanges are not excluded, these messages may carry data, such as but not limited to ranging assistance data or both ranging assistance data and ranging related frames. The recipient of these messages may be required to confirm the received message. A multiple message confirmation (MMACK) is described in detail for confirming multiple messages within the ranging cycle with a single confirmation message from the recipient. Note that confirming multiple messages with a single confirmation message from the receiver or recipient includes, but is not limited to, the illustrative examples described in the present disclosure.

[0138] Fig.13An exemplary message sequence chart for a one-to-multiple message acknowledgement (MMACK) 1300 is shown in accordance with an embodiment of the present disclosure. Fig.13 The illustrated embodiment of a message sequence chart for a one-to-one multiple message acknowledgement (MMACK) 1300 is for illustration only. Fig.13 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the message sequence diagram for one-to-one multiple message acknowledgement (MMACK) 1300 may be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 In one embodiment, the message sequence diagram for one-to-one multi-message confirmation (MMACK) 1300 may be executed by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 shown.

[0139] Fig.13 A message sequence diagram showing MMACK in a one-to-one messaging sequence. Device A sends multiple messages to device B along with an MMACK request (MMAR). Device B then sends back an MMACK when all messages are received. The message and MMACKS time slots may be scheduled, or may be contention based, or may be a combination of both.

[0140] Fig.14 An exemplary message sequence chart for a multicast or multi-node message acknowledgement (MMACK) 1400 is shown in accordance with an embodiment of the present disclosure. Fig.14 The embodiment of the message sequence chart for multicast or multi-node message acknowledgement (MMACK) 1400 shown in FIG. 1 is for illustration only. Fig.14 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the message sequence diagram of the multicast or multi-node message acknowledgement (MMACK) 1400 may be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 In one embodiment, the message sequence diagram for multicast or multi-node message confirmation (MMACK) 1400 may be executed by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 shown.

[0141] Fig.14A message sequence diagram of MMACK is shown, where device A1 to AN sends a multicast or multi-node message and MMAR to device B1 to BM. Upon completion of the forward message from (device A1 to AN), device B1 to BM acknowledges all messages to different initiators by sending MMACK via multicast or multi-node messages. Messages and MMACKS time slots may be scheduled, or may be contention-based, or may be a combination of both.

[0142] Note that the present disclosure does not exclude any number of devices or any combination of devices on the initiator side or the responder side. In addition, transmission types include but are not limited to one-to-one, one-to-many, many-to-one, many-to-many, unicast, multicast, multi-node, broadcast and any combination.

[0143] A multiple message acknowledgement may also be referred to as a multiple message receive acknowledgement message (MMRCM). A multiple message acknowledgement request may also be referred to as a multiple message receive acknowledgement request (MMRCR).

[0144] Fig.15 An exemplary message sequence diagram multiple message receipt confirmation for multiple many-to-many messages 1500 is shown according to an embodiment of the present disclosure. Fig.15 The illustrated embodiment of the message sequence diagram multiple message receipt confirmation for multiple many-to-many messages 1500 is for illustration only. Fig.15 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, a message sequence diagram for multiple many-to-many messages 1500 multiple message receipt confirmations can be sent by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 In one embodiment, the message sequence diagram for multiple many-to-many messages 1500, multiple message receipt confirmation can be executed by the controller, the controlled, the initiator and / or the responder, such as Figure 8 shown.

[0145] Fig.15 A message sequence diagram multiple message receipt confirmation for multiple many-to-many messages is shown.

[0146] In one embodiment, a method for a multiple message acknowledgement request (MER) is provided.

[0147] In one example of scheme 1 (S1), a multiple message confirmation request indication bit in the IE is provided.

[0148] Such an Advanced Ranging Control IE (not exclusive of other IEs) can be used as an indicator indicating a Multiple Message Acknowledgement Request (MMAR) as a one-bit field in an existing information element in 802.15.4z or any such similar standard. This can also be referred to as a Multiple Message Receive Acknowledgement Request (MMRCR).

[0149] Fig.16a An exemplary multiple message acknowledgement request bit 1600 indicating MMAR in an ARC IE according to an embodiment of the present disclosure is shown. Fig.16a The illustrated embodiment of the multiple message acknowledgement request bit 1600 is for illustration only. Fig.16a The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the multi-message confirmation request bit 1600 can be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) as shown may use the multiple message confirmation request bit 1600.

[0150] Fig.16b Another exemplary multiple message acknowledgement request bit 1650 indicating MMAR in an ARC IE according to an embodiment of the present disclosure is shown. Fig.16b The illustrated embodiment of the multiple message acknowledgement request bit 1650 is for illustration only. Fig.16b The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the multiple message confirmation request bit 1650 can be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) as shown may use the multiple message confirmation request bit 1650.

[0151] exist Fig.16a and Fig.16b 1 shows a diagram of the fields of the ARC IE for supporting the multiple message acknowledgement request bit for two different ARC IE formats. Other formats of the ARC IE or other IE for transmitting the multiple message acknowledgement request bit are not excluded. The multiple message acknowledgement request bit is set to 1 to indicate MMAR, otherwise the bit is set to 0. Fig.17a and Fig.17b A flow chart for determining an indication of MMAR is shown in FIG.

[0152] Fig.17a FIG. 1 shows an exemplary flow chart of using the MMAR or MMRCR bit in the ARC IE to indicate a multiple message confirmation IE 1700 according to an embodiment of the present disclosure. Fig.17a The embodiment of the flow chart for indicating the multiple message confirmation IE 1700 shown in FIG. 1 is for illustration only. Fig.17aThe scope of the present disclosure is not limited to any particular implementation. In one embodiment, the flowchart indicating the multi-message confirmation IE 1700 can be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 In one embodiment, the flowchart indicating the multi-message confirmation IE 1700 can be executed by a controller, a controlled person, an initiator and / or a responder, such as Figure 8 shown.

[0153] like Fig.17a As shown, in step 1702, the network entity receives a ranging control message or ARC. In step 1704, the network entity determines whether the multiple message acknowledgement request bit is set to "1". In step 1704, if the bit is not set to "1", the network entity recognizes that no MMAR is indicated in step 1706. In step 1704, if the bit is set to "1", the network entity recognizes that MMAR is indicated and configured for MMACK in step 1708.

[0154] Fig.17b Another exemplary flow chart illustrating the use of the MMAR or MMRCR bit in the ARC IE to indicate the multiple message confirmation IE 1750 according to an embodiment of the present invention. Fig.17b The embodiment of the flowchart of the multi-message confirmation IE 1750 shown in FIG. 1 is for illustration only. Fig.17b The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the flowchart indicating the multi-message confirmation IE 1750 can be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 In one embodiment, the flowchart indicating the multi-message confirmation IE 1750 can be executed by a controller, a controlled person, an initiator and / or a responder, such as Figure 8 shown.

[0155] like Fig.17b As shown, in step 1710, the network entity receives a ranging control message or ARC. In step 1712, the network entity determines whether a multiple message reception confirmation request (MMRCR) bit is set to "1". In step 1712, if the bit is not set to "1", the network entity recognizes that no MMAR is requested in step 1714. In step 1712, if the bit is set to "1", the network entity recognizes that MMRC is requested and configured for MMRCM in step 1716.

[0156] In one example of scheme 2, a multiple message confirmation request indicator using a one-bit field in an advanced ranging control IE is provided.

[0157] When the "delay mode" bit is not used, an existing one-bit field may be used (and / or reused), such as (including but not limited to) "delay mode" to indicate a multiple message acknowledgement request (MMAR). For example, when the ranging cycle is used for ranging assistance information exchange, the delay mode may be reused for the MMAR. This illustration does not exclude the use or reuse of any one-bit field or subfield in the ARC IE or other IEs. The illustrative frame format is as follows: Fig.18 shown.

[0158] Fig.18 An exemplary format for an MMAR indicator using a one-bit field of the ARC IE content field 1800 is shown in accordance with an embodiment of the present disclosure. Fig.18 The illustrated embodiment of the format for the MMAR indicator using a one-bit field of the ARC IE Content field 1800 is for illustration only. Fig.18 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the format for the MMAR indicator using a one-bit field of the ARC IE content field 1800 may be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 The illustrated terminals 111 - 116 ) may use the format for the MMAR indicator using a one-bit field of the ARC IE content field 1800 .

[0159] Fig.19a An exemplary flow chart illustrating the use and / or reuse of a one-bit field to indicate MMAR in ARC IE 1900 according to an embodiment of the present invention. Fig.19a The embodiment of a flow chart of MMAR in ARC IE 1900 shown in FIG. 1 is for illustration only. Fig.19a The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 The flowchart of using and / or reusing a one-bit field to indicate the MMAR in the ARC IE 1900 can be executed by the controller, the controlled person, the initiator and / or the responder, such as Figure 8 shown.

[0160] like Fig.19a As shown, in step 1902, the network entity receives a ranging control message or an ARC IE. In step 1904, the network entity determines whether a cycle for ranging assistance information is exchanged. In step 1904, if there is no exchange, the network entity recognizes that MMAR is not indicated in step 1906. In step 1904, if there is an exchange, the network entity determines in step 1908 whether the MMAR bit is set to "1". In step 1908, if the MMAR bit is set to "1", the network entity recognizes that MMAR is indicated in step 1912 and is configured for MMACK. In step 1908, if the MMAR bit is not set to "1", the network entity recognizes that MMAR is not indicated in step 1910.

[0161] Fig.19b Another exemplary flow chart illustrating the use and / or reuse of a one-bit field to indicate MMAR in ARC IE 1950 according to an embodiment of the present invention. Fig.19b The embodiment of the flow chart of the MMAR in ARC IE 1950 shown in FIGURE 1 is for illustration only. Fig.19b The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 The flowchart of using and / or reusing a one-bit field to indicate the MMAR in the ARC IE 1950 can be executed by the controller, the controlled person, the initiator and / or the responder, such as Figure 8 shown.

[0162] like Fig.19b As shown, in step 1902, the network entity receives a ranging control message or an ARC IE. In step 1916, the network entity determines whether the MMAR bit is set to "1" in step 1916. In step 1916, if the MMAR bit is set to "1", the network entity recognizes that MMAR is indicated in step 1920 and configures for MMACK. In step 1916, if the MMAR bit is not set to "1", the network entity recognizes that MMAR is not indicated in step 1918.

[0163] In one example of solution 3, a multi-message confirmation request using a new IE is provided.

[0164] To indicate a multiple message acknowledgement request, a new header or payload IE may be defined. This IE may be referenced using a name such as, but not limited to, a Multiple Message Acknowledgement Request IE (MMAR IE). Upon receipt of this IE, the MMAR indication may be determined. This IE may not include any content fields, as the presence of the IE itself acts as an indicator. However, the present disclosure does not exclude IEs formatted with content fields (e.g., including but not limited to those described in Scheme 4) to convey this information. Fig. 20 An illustrative flow chart for determining an MMAR indication is shown in . The IE itself may be sent via a message such as, but not limited to, a ranging control message.

[0165] Fig. 20 An exemplary flow chart of using IE to indicate multiple message confirmation 2000 according to an embodiment of the present disclosure is shown. Fig. 20 The embodiment of the flowchart of multiple message confirmation 2000 shown in FIG. 2 is for illustration only. Fig. 20 The scope of the present disclosure is not limited to network entities (e.g., Figure 1 BS 101-103 as shown, Figure 1 In one embodiment, the flowchart indicating the multi-message confirmation 2000 may be implemented by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 In one embodiment, the flowchart indicating the multi-message confirmation 2000 can be executed by a controller, a controlled person, an initiator and / or a responder, such as Figure 8 shown.

[0166] like Fig. 20 As shown, in step 2002, the network entity receives a message from a controller or an initiator. In step 2004, the network entity determines whether there is an IE indicating a multiple message acknowledgement request. In step 2004, if there is an IE indicating a multiple message acknowledgement request, the network entity recognizes that MMAR is indicated and is configured for MMACK. In step 2004, if there is no IE indicating a multiple message acknowledgement request, the network entity recognizes that MMAR is not indicated in step 2006.

[0167] In one embodiment, a method of acknowledging multiple messages in a ranging cycle is provided.

[0168] The multi-message confirmation IE (MMACK IE) can be used by a responder (or a recipient of multiple messages) to confirm multiple messages. Other names for this IE are not excluded. The above-mentioned multiple messages can come from a single initiator or multiple initiators. In the case where the multiple messages confirmed originate from multiple initiators (many-to-one data transmission or many-to-many data transmission), the mode of transmitting the message including MMACK is selected accordingly (including but not limited to unicast, multicast, multi-node, etc.). A receiver or responder can use multi-message confirmation to confirm multiple messages originating from the same initiator, or to confirm multiple messages originating from multiple initiators (or senders).

[0169] Each message is acknowledged in a multi-message acknowledgement by a binary bitmap string. Each bit in the bitmap string can be mapped to a time slot or a message or any other message / frame / information identifier respectively. The length of the acknowledgement bitmap is equal to the number of messages sent by the initiator (or transmitter) or the total number of messages sent by all initiators (or transmitters) to all responders (or receivers). Each bit acknowledges the reception of a message. The bit is set to 1 to convey a successful reception, otherwise the bit is set to 0 to convey that the message was not received (or vice versa).

[0170] The scheme that comprises coding or compression to transmit this confirmation bitmap is not excluded. If the MMACK bitmap string and the subsequent bit can represent the confirmation of the subsequent message, and the MSB represents the confirmation of the final message, then the confirmation bit for the first message can correspond to the least significant bit. The scheme of vice versa can also be used, or any other scheme can be used to map the bit position in the bitmap string to correspond to a specific message. The present disclosure does not exclude any such method.

[0171] Several methods are described in this disclosure for a responder to determine the number of bitmaps. However, the method by which a responder determines the number of bitmaps is not limited to the method in this disclosure. The length of the bitmap may be sent by the controller and / or the initiator via higher layers through out-of-band signaling.

[0172] In one example of scheme 4, a method for determining the length of a multi-message confirmation bitmap via a ranging scheduling IE is provided.

[0173] The controller sends the ranging schedule IE to inform the scheduling of time slots. The schedule allocates time slots to all initiators that initiate message transmission. The total number of such time slots gives the total number of messages sent by one or more initiators in this cycle. The responder can determine the length of the bitmap based on the scheduling information included in the ranging schedule IE. Fig.21 An illustrative flow chart is shown in .

[0174] Fig.21 An exemplary flow chart for determining the length of the multi-message confirmation bitmap 2100 via the ranging scheduling IE according to an embodiment of the present disclosure is shown. Fig.21 The embodiment of the flowchart of the length of the multi-message acknowledgement bitmap 2100 shown is for illustration only. Fig.21 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the flowchart for determining the length of the multi-message confirmation bitmap 2100 can be performed by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 In one embodiment, the flowchart for determining the length of the multi-message confirmation bitmap 2100 may be executed by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 shown.

[0175] like Fig.21 As shown, in step 2102, the network entity receives the ranging scheduling IE. In step 2104, the network entity determines the number of time slots scheduled for data transmission. In step 2106, the network entity identifies the length of the MMACK bitmap, which is the number of time slots scheduled for data transmission. In one example of scheme S5, it is provided that the length of the multi-message confirmation bitmap is transmitted via the IE.

[0176] The Multiple Message Acknowledgement Request IE (MMAR IE) may convey the length of the MMACK bitmap in the content field. This may be the same IE with the content field described in Option 2, or it may be a different IE. The content field of the IE may be formatted as Fig. 22 shown.

[0177] Fig. 22 FIG. 2 shows an exemplary content field of an IE for transmitting the length of the MMACK bitmap 2200 according to an embodiment of the present disclosure. Fig. 22 The embodiment of the content field of the IE of the length of the MMACK bitmap 2200 shown is for illustration only. Fig. 22 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the content field of the IE used to transmit the length of the MMACK bitmap 2200 can be used by the controller, the controlled, the initiator and / or the responder, such as Figure 8 In one embodiment, the content field of the IE used to transmit the length of the MMACK bitmap 2200 may be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0178] In one example of scheme 6, a multi-message confirmation using an IE without a content field is provided. An IE without any content field may be used to transmit an MMACK. Since the IE is used with a MAC frame that may have the ability to carry data, the MMACK bitmap carrying information may be included in the data field of the MAC payload of the frame using the IE.

[0179] In one example of scheme 7, a multi-message confirmation using a multi-message confirmation IE having a content field is provided.

[0180] MMACK can be transmitted via an IE having a content field including MMACK bitmap information. The bitmap conveys the receipt or non-receipt of a specific message. The content field of the IE can be formatted as Fig.23 shown.

[0181] Fig.23 Exemplary content fields of an IE for a multi-message confirmation 2300 according to an embodiment of the present disclosure are shown. Fig.23 The illustrated embodiment of the content fields of the IE for the multi-message acknowledgement 2300 is for illustration only. Fig.23 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the content field of the IE for multi-message confirmation 2300 can be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, the content field of the IE for multi-message confirmation 2300 may be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0182] In one example of Scheme 8, a multi-message confirmation with an initiator address using IE is provided.

[0183] Messages from many initiators can be acknowledged with MMACK using an IE with the initiator address and the MMACK bitmap string to acknowledge all messages from that initiator (or sender). The IE can include a table to acknowledge multiple initiators in a single message. The content fields of the IE can be formatted as Fig.24 shown.

[0184] Fig.24 Exemplary content fields of an IE for an MMACK with an address in acknowledgment 2400 are shown according to an embodiment of the present disclosure. Fig.24 The illustrated embodiment of the exemplary content fields of the IE for the MMACK with the address in the acknowledgment 2400 is for illustration only. Fig.24The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the content field of the IE for the MMACK with the address in the confirmation 2400 can be used by the controller, the controlled person, the initiator and / or the responder, such as Figure 8 In one embodiment, the content field of the IE for the MMACK with the address in the confirmation 2400 may be determined by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0185] Each row of the MMACK table is formatted as follows: Fig.25 shown.

[0186] Fig.25 An exemplary row of the MMACK table 2500 is shown, in accordance with an embodiment of the present disclosure. Fig.25 The embodiment of the rows of MMACK table 2500 shown in FIG. 2 is for illustration only. Fig.25 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the rows of MMACK table 2500 may be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, the rows of MMACK table 2500 may be populated by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0187] In one example of scheme 9, a multiple message received confirmation (MMRC) message with an optional initiator address using IE is provided.

[0188] Messages from many initiators can be acknowledged using the MMRCM using an IE with an optional initiator address and MMRC bitmap string to acknowledge all messages from that initiator (or sender). In scheduled mode, where each time slot is scheduled for a unique initiator (or sender), the initiator address need not be used. The Ranging Multiple Message Receive Confirmation IE (RMMRCIE) includes a table for sending receive confirmations to multiple initiators in a single message. The content fields of the IE are formatted as follows: Fig.26 shown.

[0189] Fig.26 An exemplary RMMRC IE content field format 2600 is shown according to an embodiment of the present disclosure. Fig.26 The illustrated embodiment of the RMMRC IE content field format 2600 is for illustration only. Fig.26The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the RMMRC IE content field format 2600 can be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, the RMMRC IE content field format 2600 may be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0190] If the initiator's address exists in the MMRC list element, the address exists bit is set to "1", otherwise the address exists bit is set to "0".

[0191] If a 2-octet short address is used in the MMRC list, the Address Length bit used is set to "0", otherwise, the Address Length bit used is set to "1" to indicate an 8-octet long address (if it is used in the MMRC list). If the Address Present bit is "0", this field is ignored.

[0192] Each row of the MMACK table is formatted as follows: Fig.25 shown.

[0193] Fig. 27 An exemplary MMRC list element format 2700 is shown according to an embodiment of the present disclosure. Fig. 27 The embodiment of the MMRC list element format 2700 shown is for illustration only. Fig. 27 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, the MMRC list element format 2700 can be used by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 In one embodiment, the MMRC list element format 2700 may be provided by a network entity (e.g., Figure 1 BS 101-103 as shown, Figure 1 Terminals 111-116) shown are used.

[0194] When the address field is present, it indicates the address of the initiator to which the MMRC bitmap of the corresponding list element indicates receipt confirmation.

[0195] The MMRC bitmap length is given by the upper limit (number of acknowledged slots / 8).

[0196] The MMRC bitmap field includes a binary bitmap string. Each bit is mapped to a time slot in the ranging cycle (one or more) for which the RMMRC IE is used to send a message reception confirmation. Each bit confirms the reception of a message in a time slot. The bit is set to 1 to confirm successful reception, otherwise the bit is set to 0 to convey that the message was not received or was not addressed to the MMRC transmitter in the time slot. The first time bit sent in this field refers to the first time slot, and subsequent bits refer to subsequent time slots in chronological order. When the number of bits sent in the MMRC bitmap is greater than the number of time slots using reception confirmation, the last sent bit given by ExtraBits = (NumberOfBitsinMMRCBitmap-NumberOfSlotsForReceiptConfirmation) is discarded.

[0197] Fig.28 An exemplary flow chart of a method 2800 for confirming multiple messages according to an embodiment of the present disclosure is shown, which may be performed by a network entity (eg, Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116 shown) are executed. Fig.28 The embodiment of the flowchart of method 2800 shown is for illustration only. Fig.28 The scope of the present disclosure is not limited to any particular implementation. In one embodiment, method 2800 may be performed by a controller, a controlled person, an initiator, and / or a responder, such as Figure 8 shown.

[0198] like Fig.28 As shown, method 2800 starts at step 2802. In step 2802, a network entity identifies one or more ranging cycles in a ranging block to transmit a ranging control message (RCM) having a multiple message reception confirmation request (MMRCR) for transmission of at least one first message, the at least one first message including at least one of a group of ranging messages or a group of ranging assistance data messages.

[0199] Then, in step 2804, the network entity sends the RCM with the MMRCR to the second network entity.

[0200] Subsequently, in step 2806, the network entity sends ranging assistance data to the second network entity in at least one ranging cycle of the one or more ranging cycles after the RCM, wherein the ranging assistance data is associated with the MMRCR.

[0201] Finally, in step 2808, the network entity receives a ranging multiple message reception confirmation (RMMRC) corresponding to the transmission of the at least one first message from the second network entity.

[0202] In one embodiment, in step 2808, the RMMRC also includes at least one confirmation corresponding to the transmission of at least one second message sent from another first network entity to the second network entity; the at least one second message includes at least one of another ranging message or another ranging assistance data message.

[0203] In one embodiment, the network entity identifies a reception mode of the RMMRC; and receives the RMMRC based on the identified reception mode, the reception mode being determined to be at least one of a contention-based reception mode or a scheduling mode.

[0204] In one embodiment, the network entity sends an RCM or an Advanced Ranging Control Information Element (ARC IE) including an ARC IE to the second network entity using one of the messages to be sent to the second network entity.

[0205] In the above embodiment, the ARC IE includes a multi-node mode field, a ranging cycle usage field, a scrambled time stamp sequence (STS) group configuration field, a scheduling mode field, a delay mode field, a time structure indicator field, an RCM validity cycle field, an MMRCR field, a ranging block duration field, a ranging cycle duration field, and a ranging slot duration field; when the first network entity sends the MMRCR to the second network entity, the MMRCR field is set to 1.

[0206] In one embodiment, the network entity receives the RMMRC via at least one of a group of multicast messages or a group of multimode messages. In such an embodiment, the RMMRC includes an RMMRC IE, the RMMRC IE includes an MMRC list length field and an MMRC list field; the MMRC list length field indicates the number of elements in the MMRC list field; the MMRC list field includes an address field, an MMRC bitmap length field, and an MMRC bitmap field, the MMRC bitmap field includes a binary bitmap string; each bit of the binary bitmap string is mapped to each time slot in a group of time slots in at least one ranging cycle, wherein the RMMRC IE is used to send a message reception confirmation corresponding to the sending of at least one first message; each bit of the binary bitmap string is set to 1 to confirm the successful reception of the sending of at least one first message, otherwise each bit of the binary bitmap string is set to 0.

[0207] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

[0208] Nothing in this application should be construed as implying that any particular element, step, or function is an essential element that must be included in the scope of the claims. The scope of the patented subject matter is limited solely by the claims. Furthermore, any of the claims is intended not to violate 35 U.S.C. §112(f) unless the exact words "means for..." are followed by a participle.

Claims

1. A first device supporting ranging capability in a wireless communication system, the first device comprising: a memory storing one or more instructions; At least one processor configured to execute the one or more instructions to: Generate a ranging control message RCM, the RCM including a multiple message reception confirmation request MMRCR information, wherein the MMRCR information indicates whether a multiple message reception confirmation is requested; sending the generated RCM to the second device in a ranging block including a plurality of ranging cycles; and receiving a multiple message reception confirmation message MMRCM from the second device to confirm reception of the multiple messages, The MMRCM includes a ranging multi-message reception confirmation RMMRC IE, the RMMRC IE includes an MMRC list length field and an MMRC list field, and The MMRC list length field indicates the number of elements in the MMRC list field, and the elements of the MMRC list field include an address field, an MMRC bitmap length field, and an MMRC bitmap field.

2. The first device according to claim 1, wherein: The MMRCM is sent by the second device via a multicast or multi-node message to acknowledge receipt of the multiple messages sent from one or more devices including the first device.

3. The first device of claim 1 , wherein the at least one processor is further configured to execute the one or more instructions to: The MMRCM is received according to at least one of a contention-based mode, a scheduled mode, or a combination of the contention-based mode and the scheduled mode. 4 . The first device according to claim 1 , wherein the at least one processor is further configured to execute the one or more instructions to: send the generated RCM including an Advanced Ranging Control Information Element (ARC IE) to the second device.

5. The first device according to claim 4, wherein: The ARC IE includes a multi-node mode field, a ranging cycle usage field, a scrambled time stamp sequence STS packet configuration field, a scheduling mode field, a delay mode field, a time structure indicator field, an RCM validity cycle field, an MMRCR field, a ranging block duration field, a ranging cycle duration field, and a ranging slot duration field; and When the multiple message reception confirmation is requested, the MMRCR field is set to 1.

6. The first device of claim 1, wherein the MMRC bitmap field comprises a binary bitmap string.

7. The first device according to claim 6, wherein: Each bit of the binary bitmap string is mapped to a time slot in at least one ranging cycle of the ranging block to confirm successful reception of a message sent in the time slot.

8. A second device supporting ranging capability in a wireless communication system, the second device comprising: a memory storing one or more instructions; At least one processor configured to execute the one or more instructions to: receiving a ranging control message RCM from a first device in a ranging block including a plurality of ranging cycles; identifying the received RCM, the received RCM including multiple message reception confirmation request MMRCR information, wherein the MMRCR information indicates whether multiple message reception confirmation is requested; and Sending a multiple message reception confirmation message MMRCM to the first device to confirm the reception of the multiple messages, The MMRCM includes a ranging multi-message reception confirmation RMMRC IE, the RMMRC IE includes an MMRC list length field and an MMRC list field, and The MMRC list length field indicates the number of elements in the MMRC list field, and the elements of the MMRC list field include an address field, an MMRC bitmap length field, and an MMRC bitmap field.

9. The second device according to claim 8, wherein: The MMRCM is sent by the second device via a multicast or multi-node message to acknowledge receipt of the multiple messages sent from one or more devices including the first device.

10. The second device of claim 8, wherein the at least one processor is further configured to execute the one or more instructions to: The MMRCM is sent according to at least one of a contention-based mode, a scheduled mode, or a combination of the contention-based mode and the scheduled mode.

11. The second device of claim 8, wherein the at least one processor is further configured to execute the one or more instructions to: receive the RCM including an Advanced Ranging Control Information Element (ARC IE) from the first device.

12. The second device according to claim 11, wherein: The ARC IE includes a multi-node mode field, a ranging cycle usage field, a scrambled time stamp sequence STS packet configuration field, a scheduling mode field, a delay mode field, a time structure indicator field, an RCM validity cycle field, an MMRCR field, a ranging block duration field, a ranging cycle duration field, and a ranging slot duration field; and When the multiple message reception confirmation is requested, the MMRCR field is set to 1.

13. The second device of claim 8, wherein the MMRC bitmap field comprises a binary bitmap string.

14. The second device according to claim 13, wherein: Each bit of the binary bitmap string is mapped to a time slot in at least one ranging cycle of the ranging block to confirm successful reception of a message sent in the time slot.

15. A method for a first device supporting ranging capability in a wireless communication system, the method comprising: Generate a ranging control message RCM, the RCM including a multiple message reception confirmation request MMRCR information, wherein the MMRCR information indicates whether a multiple message reception confirmation is requested; sending the generated RCM to the second device in a ranging block including a plurality of ranging cycles; and receiving a multiple message reception confirmation message MMRCM from the second device to confirm reception of the multiple messages, The MMRCM includes a ranging multiple message reception confirmation RMMRC IE, the RMMRC IE includes an MMRC list length field and an MMRC list field, and The MMRC list length field indicates the number of elements in the MMRC list field, and the elements of the MMRC list field include an address field, an MMRC bitmap length field, and an MMRC bitmap field.

Images