Apparatus and method for specifying receiver enable time in UWB communication and ranging system
By using the MLME-RX-ENABLE.request primitive and MCPS-DATA.indication primitive in the UWB communication system, combined with the RSTU counter value, the receiver enable time is optimized, and the receiver enablement in the UWB communication and ranging system is solved. It can manage problems and improve the system's ranging and communication efficiency.
Patent Information
- Application Number
- CN202080037646.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-05-14
- Filing Date
- 2020-05-20
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-05-20
AI Technical Summary
In UWB communication and ranging systems, it is difficult for the prior art to effectively manage and optimize the enable time of a specified receiver, affecting the ranging capability and communication efficiency.
By introducing a media access control (MAC) sub-layer management entity in a wireless communication system, using the MLME-RX-ENABLE.request primitive, combined with the value and number of the ranging scheduling time unit (RSTU) counter, determine whether the receiver is from another A network entity receives the frame and generates the MCPS-DATA.indication primitive in response to the reception situation.
It realizes a network entity that supports ranging capability in the UWB communication system, improves the management accuracy and efficiency of receiver enable time, and improves the system ranging and communication performance.
Smart Images

Figure CN113853813B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to an architecture and method for specifying receiver enable time in a UWB communication and ranging system. Background Art
[0002] The 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 called a ranging device (RDEV), an enhanced ranging device (ERDEV), 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 defined in the IEEE standard. The PAC network may use several topologies such as mesh, star, etc. to support interactions between PDs to implement various services. Summary of the invention
[0003] Technical issues
[0004] Embodiments of the present disclosure provide an architecture and method for specifying receiver enable time in a UWB communication and ranging system.
[0005] Problem Solution
[0006] In one embodiment, a network entity supporting ranging capabilities within a wireless communication system is provided. The network entity includes a transceiver, and the network entity also includes a processor operably connected to the transceiver, the processor being configured to: identify a medium access control (MAC) sublayer management entity receive enable request (MLME-RX-ENABLE.request) primitive, which includes a list of ranging scheduling time unit (RSTU) counter (RxOnTime) values and a number of RSTUs (RxOnDuration), wherein the MLME-RX-ENABLE.request primitive is sent from a higher layer to the MAC layer; in response to identifying the MLME-RX-ENABLE.request primitive, identify a value of a MAC RSTU counter (MAC RSTU_COUNTER); determine whether the value of MACRSTU_COUNTER is set to an RxOnTime value in the list of RxOnTime values of the MLME-RX-ENABLE.request primitive; increase the value of MAC RSTU_COUNTER; determine whether the transceiver has received a frame from another network entity based on the value of MAC RSTU_COUNTER; and in response to determining that the transceiver has received a frame, generate a MAC common part sublayer indication (MCPS-DATA.indication) primitive. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:
[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] Figure 4a A high-level diagram of an OFDMA transmission path according to an embodiment of the present disclosure is shown;
[0012] Figure 4b A high-level diagram of an OFDMA receive path according to an embodiment of the present disclosure is shown;
[0013] Figure 5 An 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 round structure according to an embodiment of the present disclosure is shown;
[0016] Figure 8 An exemplary ranging controller, a controlled object, 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 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 service primitive according to an embodiment of the present disclosure is shown;
[0022] Fig.14 An exemplary MAC sublayer reference model according to an embodiment of the present disclosure is shown;
[0023] Fig.15a shows an exemplary MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.MLME-RX-ENABLE.confirm message sequence chart for a controller according to an embodiment of the present disclosure;
[0024] Fig.15b shows an exemplary MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart for a controller according to an embodiment of the present disclosure;
[0025] Fig.16 shows an exemplary MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart for a controller according to an embodiment of the present disclosure;
[0026] Fig.17a shows an exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart for a controller according to an embodiment of the present disclosure;
[0027] Fig.17b shows an exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart for a controller according to an embodiment of the present disclosure;
[0028] Fig.18 An exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart for a controlled object according to an embodiment of the present disclosure is shown;
[0029] Fig.19 The MLME-RX-ENABLE.indication flow chart of ERDEV according to an embodiment of the present disclosure is shown, wherein RxAutoOff=TRUE;
[0030] Fig. 20 A flowchart of a method for specifying a receiver enable time according to an embodiment of the present disclosure is shown.
[0031] Best Mode for Carrying Out the Invention
[0032] Embodiments of the present disclosure provide an architecture and method for specifying receiver enable time in a UWB communication and ranging system.
[0033] In one embodiment, a network entity supporting ranging capability in a wireless communication system is provided. The network entity includes a transceiver, and the network entity also includes a processor operably connected to the transceiver, the processor being configured to: identify a medium access control (MAC) sublayer management entity receive enable request (MLME-RX-ENABLE.request) primitive, which includes a list of ranging scheduling time unit (RSTU) counter (RxOnTime) values and the number of RSTUs (RxOnDuration), wherein the MLME-RX-ENABLE.request primitive is sent from a higher layer to the MAC layer; in response to identifying the MLME-RX-ENABLE.request primitive, identify a value of a MAC RSTU counter (MAC RSTU_COUNTER); determine whether the value of the MAC RSTU_COUNTER is set to an RxOnTime value included in the RxOnTime value list of the MLME-RX-ENABLE.request primitive; increase the MAC RSTU_COUNTER value; determine whether the transceiver has received a frame from another network entity based on the value of the MAC RSTU_COUNTER; and in response to determining that the transceiver has received a frame, generate a MAC common part sublayer indication (MCPS-DATA.indication) primitive.
[0034] In another embodiment, a method for a network entity supporting ranging capability in a wireless communication system is provided. The method includes: identifying a medium access control (MAC) sublayer management entity receive enable request (MLME-RX-ENABLE.request) primitive, including a list of ranging scheduling time unit (RSTU) counter (RxOnTime) values and the number of RSTUs (RxOnDuration), wherein the MLME-RX-ENABLE.request primitive is sent from a higher layer to the MAC layer; in response to identifying the MLME-RX-ENABLE.request primitive, identifying a value of a MAC RSTU counter (MAC RSTU_COUNTER); determining whether the value of the MAC RSTU_COUNTER is set to an RxOnTime value included in the RxOnTime value list of the MLME-RX-ENABLE.request primitive; increasing the MAC RSTU_COUNTER value; determining whether a frame is received from another network entity based on the value of the MAC RSTU_COUNTER; and generating a MAC common part sublayer indication (MCPS-DATA.indication) primitive in response to determining that the frame is received.
[0035] In another embodiment, a non-transitory computer-readable medium including program code is provided, which, when executed by at least one processor, causes a network entity supporting ranging capability in a wireless communication system to: identify a medium access control (MAC) sublayer management entity receive enable request (MLME-RX-ENABLE.request) primitive, which includes a list of ranging scheduling time unit (RSTU) counter (RxOnTime) values and the number of RSTUs (RxOnDuration), wherein the MLME-RX-ENABLE.request primitive is sent from a higher layer to the MAC layer; in response to identifying the MLME-RX-ENABLE.request primitive, identify a value of a MAC RSTU counter (MAC RSTU_COUNTER); determine whether the value of MAC RSTU_COUNTER is set to an RxOnTime included in the RxOnTime value list of the MLME-RX-ENABLE.request primitive; increase the value of MAC RSTU_COUNTER; based on the MAC The value of RSTU_COUNTER determines whether the transceiver receives a frame from another network entity; and in response to determining that the transceiver receives the frame, generates a MAC common part sublayer indication (MCPS-DATA.indication) primitive.
[0036] Other technical features may be readily apparent to those skilled in the art from the following drawings, descriptions and claims.
[0037] Before proceeding to the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout the patent document. The term "connection" 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 cover direct and indirect communication. 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 to include, include within, interconnect with, include, include within, connect to or connect with, connect to or connect with, communicate with, collaborate with, interweave, parallel, approach, bind to or bind with, have, have the characteristics of, have... and... The relationship etc. of. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. Whether local or remote, the functions associated with any particular controller can be centralized or distributed. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one of the items 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, B, and C.
[0038] 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 implemented 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, examples, related data or parts thereof that are suitable for implementation with suitable 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-temporary" computer-readable medium excludes wired, wireless, optical or other communication links that transmit temporary electrical signals or other temporary signals. Non-temporary computer-readable media include media that can permanently store data, and media that can store data and then rewrite data, such as rewritable optical discs or erasable storage devices.
[0039] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that, in many instances, such definitions apply to past, as well as future uses of such defined words and phrases.
[0040] The following discussion Figures 1 to 20 , and various embodiments used to describe the principles of the present disclosure in this patent document are only illustrative and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.
[0041] The following documents and standards descriptions are incorporated by reference into the present disclosure as if fully set forth herein: IEEE Standard for Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Peer-Aware Communications, IEEE Standard 802.15.8, 2017; IEEE Standard for Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-rate Wireless Personal Area Networks (WPANs), Amendment 1: Addition of Alternative PHY, IEEE Standard 802.15.4a (2007), IEEE Standard for Low-rate Wireless Networks, IEEE Standard 802.15.4 (2015), and IEEE 802.15.4z MAC.
[0042] Through the following detailed description, it is briefly shown that multiple specific embodiments and implementations including the best mode for implementing the present disclosure, the various aspects, features and advantages of the present disclosure are obvious. The present disclosure may also have other different embodiments, and its multiple details may be modified in various obvious aspects without departing from the essence and scope of the present disclosure. Therefore, the drawings and descriptions should be considered to be illustrative in nature, rather than restrictive. The present disclosure is shown in the drawings of the drawings by way of example and not by way of limitation.
[0043] The following Figure 1-4b Various embodiments are described that may be implemented 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 does not imply physical or architectural limitations on how different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any appropriately configured communication system.
[0044] Figure 1 An exemplary wireless network according to an embodiment of the present disclosure is shown. Figure 1 The illustrated implementation of the wireless network is for illustration only, and other implementations of the wireless network 100 may be used without departing from the scope of the present disclosure.
[0045] like Figure 1As 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.
[0046] gNB 102 provides wireless broadband access to network 130 for a first plurality of user devices (UEs) 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 WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, a laptop, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs include UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G, LTE, LTE-A, WiMAX, WiFi, or other wireless communication technologies.
[0047] 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 transceiver point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macro cell, a femto cell, a WiFi access point (AP), or other wirelessly enabled devices. A base station may provide wireless access according to one or more wireless communication protocols, such as 5G 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), LTE Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Moreover, depending on the network type, the term "user device" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "receiving point" or "user device". For convenience, the terms "user device" and "UE" used in this patent document refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (e.g., a mobile phone or smartphone) or a commonly considered fixed device (e.g., a desktop computer or vending machine).
[0048] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as being generally circular for purposes of illustration and explanation only. It should be appreciated that coverage areas associated with a gNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB, and variations in the radio environment associated with natural and man-made obstacles.
[0049] As described in more detail below, one or more of the UEs 111-116 include circuitry, programming, or a combination thereof for using an architecture for specifying receiver enable times in a UWB communication and ranging system. In certain embodiments, one or more of the gNBs 101-103 include circuitry, programming, or a combination thereof for using an architecture for specifying receiver enable times in a UWB communication and ranging system.
[0050] Although Figure 1 One embodiment of a wireless network is shown, but may be Figure 1 Various changes may be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable configuration. Moreover, 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 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, for example, an external telephone network or other type of data network.
[0051] Figure 2 An exemplary gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown in FIG. is for illustration only. Figure 1 The gNBs 101 and 103 in FIG. 1 may have the same or similar configurations. However, there are multiple configurations of gNBs. Figure 2 The scope of this disclosure is not limited to any particular implementation of gNB.
[0052] 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.
[0053] RF transceivers 210a-210n receive input RF signals from antennas 205a-205n, such as signals transmitted by UEs in network 100. RF transceivers 210a-210n down-convert the input 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.
[0054] The TX processing circuit 215 receives analog or digital data (e.g., voice data, web 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 generate a processed baseband or IF signal. The RF transceivers 210a-210n receive the output processed baseband or IF signals from the TX processing circuit 215 and up-convert the baseband or IF signals to RF signals that are transmitted through the antennas 205a-205n.
[0055] 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 through 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.
[0056] 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.
[0057] 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 can move data into or out of the memory 230 as required by the executing process.
[0058] The controller / processor 225 is also connected to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or via a network. The interface 235 can support communication over any suitable wired or wireless connection. For example, when the gNB 102 is part of a cellular communication system (e.g., one that supports 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 an access point, the interface 235 can allow the gNB 102 to communicate over a wired or wireless local area network, or via a wired or wireless connection to a larger network (e.g., the Internet). The interface 235 includes any suitable structure that supports communication over a wired or wireless connection, such as an Ethernet or RF transceiver.
[0059] Memory 230 is connected to controller / processor 225. A portion of memory 230 may include RAM and another portion of memory 230 may include flash memory or other ROM.
[0060] Although Figure 2 One embodiment of the gNB 102 is shown, but may be Figure 2 For example, gNB 102 may include any number of Figure 2 As a specific embodiment, the access point may include multiple interfaces 235, and the controller / processor 225 may support routing functions to route data between different network addresses. As another specific embodiment, although a single instance of the TX processing circuit 215 and a single instance of the RX processing circuit 220 are shown, the gNB 102 may include multiple instances of each (e.g., one for each RF transceiver). Furthermore, Figure 2 The various components may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.
[0061] 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. Figure 3 The scope of the present disclosure is not limited to any particular implementation of a UE.
[0062] 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.
[0063] 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 sends the processed baseband signal to speaker 330 (e.g., for voice data), or to processor 340 for further processing (e.g., for web browsing data).
[0064] The TX processing circuit 315 receives analog or digital voice data from the microphone 320, or receives other outgoing baseband data (e.g., web data, email, or interactive video game data) from the processor 340. The TX processing circuit 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or intermediate frequency signal. The RF transceiver 310 receives the outgoing processed baseband or IF signal from the TX processing circuit 315 and up-converts the baseband or IF signal to an RF signal that is transmitted through the antenna 305.
[0065] The processor 340 may include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 to control the overall operation of the UE 116. For example, according to well-known principles, 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. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.
[0066] The processor 340 is also capable of executing other processes and programs that are resident in the memory 360, such as processes for CSI reporting on uplink channels. The processor 340 may move data into or out of the memory 360 as required by the executed process. In some embodiments, the processor 340 is configured to execute the application 362 based on the OS 361 or in response to a signal received from the gNB or operator. The processor 340 is also connected 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.
[0067] Processor 340 is also connected to touch screen 350 and display 355. An operator of UE 116 may enter 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 (e.g., from a website).
[0068] Memory 360 is connected to processor 340. A portion of memory 360 may include random access memory (RAM), while another portion of memory 360 may include flash memory, or other read-only memory (ROM).
[0069] Although, Figure 3 One embodiment of UE 116 is shown, but may be used for 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 embodiment, 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). Figure 3 The UE 116 is shown configured as a mobile phone or smart phone, but the UE may be configured to operate as other types of mobile or stationary devices.
[0070] Figure 4a is a high level diagram of a transmit path circuit. For example, the transmit path circuit may be used for orthogonal frequency division multiple access (OFDMA) communications. Figure 4b is a high-level diagram of a receive path circuit. For example, the receive path circuit may be used for orthogonal frequency division multiple access (OFDMA) communications. Figure 4a and 4b In the embodiment, for downlink communication, the transmit path circuit may be implemented in the base station (gNB) 102 or the relay station, and the receive path circuit may be implemented in the user device (e.g., Figure 1In other examples, for uplink communications, the receive path circuit 450 may be implemented in a base station (e.g., Figure 1 The transmit path circuit may be implemented in a user device (e.g., a gNB 102) or a relay station, while the transmit path circuit may be implemented in a user device (e.g., Figure 1 The method is implemented in a user device 116).
[0071] The transmit path circuit includes a channel coding and modulation module 405, a serial to parallel (S to P) module 410, an inverse fast Fourier transform (IFFT) module of size N 415, a parallel to serial (P to S) module 420, an add cyclic prefix module 425, and an upconverter (UC) 430. The receive path circuit 450 includes a downconverter (DC) 455, a remove cyclic prefix module 460, a serial to parallel (S to P) module 465, a fast Fourier transform (FFT) module of size N 470, a parallel to serial (P to S) module 475, and a channel decoding and demodulation module 480.
[0072] Figure 4a 400 and Figure 4b At least some components in 450 may be implemented in software, while other components may be implemented in configurable hardware or a mixture of software and configurable hardware. In particular, the FFT module and IFFT module described in this disclosure may be implemented in a configurable software algorithm, where the value of N may be modified according to the implementation.
[0073] In addition, although the present disclosure relates to an embodiment for realizing fast Fourier transform and inverse fast Fourier transform, this is only for illustration and is not interpreted as limiting the scope of the present disclosure. In another embodiment of the present disclosure, the fast Fourier transform function and the inverse fast Fourier transform function can be 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 variable N can be any integer (i.e., 1, 2, 3, 4, etc.), and for FFT and IFFT functions, the value of variable N can be any integer of a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).
[0074] In the transmit path circuit 400, the channel coding and modulation module 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 module 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 module 415 then performs an IFFT operation on the N parallel symbol streams to produce a time domain output signal. The parallel to serial module 420 converts (i.e., multiplexes) the parallel time domain output symbols from the size-N IFFT module 415 to produce a serial time domain signal. The add cyclic prefix module 425 then inserts a cyclic prefix into the time domain signal. Finally, the output of the add cyclic prefix module 425 is modulated (ie, up-converted) to RF frequency by an up-converter 430 for transmission over a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.
[0075] The transmitted RF signal arrives at UE 116 after passing through the wireless channel, and the reverse operation of the operation at gNB 102 is performed. Downconverter 455 downconverts the received signal to baseband frequency, and removes the cyclic prefix by remove cyclic prefix module 460 to produce a serial time-domain baseband signal. Serial to parallel module 465 converts the time-domain baseband signal into parallel time-domain signals. Then, FFT module 470 of size N performs an FFT algorithm to produce N parallel frequency-domain signals. Parallel to serial module 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation module 480 demodulates the modulation symbols and then decodes them to recover the original input data stream.
[0076] Each of gNBs 101-103 may implement a transmit path similar to that for transmitting in the downlink to user devices 111-116 and may implement a receive path similar to that for receiving in the uplink from user devices 111-116. Similarly, each of user devices 111-116 may implement a transmit path corresponding to the architecture for transmitting in the uplink to gNB 101-103 and may implement a receive path corresponding to the architecture for receiving in the downlink from gNB 101-103.
[0077] 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.
[0078] The PAC network can use several topologies such as mesh, star and / or peer to support interactions between PDs for various services. Although the present disclosure uses PAC networks and PDs as examples to develop and illustrate the present disclosure, it should be noted that the present disclosure is not limited to these networks. The general concepts developed in the present disclosure can be used in various types of networks with different types of scenarios.
[0079] Figure 5 An exemplary electronic device 501 according to an embodiment of the present disclosure is shown. Figure 5 The illustrated implementation of the electronic device 501 is for illustration only and is not intended to limit the scope of the present disclosure to any particular implementation.
[0080] A PD may be an electronic device with communication and ranging capabilities. According to IEEE standard specifications, the 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. 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.
[0081] Reference Figure 5 , the electronic device 501 in the network environment 500 can communicate with the electronic device 502 through the first network 598 (e.g., a short-range wireless communication network), or communicate with the electronic device 504 or the server 508 through 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 through the server 508.
[0082] According to one embodiment, the electronic device 501 may include a processor 520, a memory 530, an input device 550, a sound output device 555, a display device 560, an audio 570, a sensor 576, an interface 577, a haptic 579, a camera 580, a power management 588, a battery 589, a communication interface 590, a subscriber identification module (SIM) 596, or an antenna 597. In some embodiments, at least one of these components (e.g., the display device 560 or the camera 580) may be omitted from the electronic device 501, or one or more other components may be added to the electronic device 501. In some embodiments, some components may be implemented as a single integrated circuit. For example, a sensor 576 (e.g., a fingerprint sensor, an iris sensor, or an illumination sensor) may be implemented as embedded in the display device 560 (e.g., a display).
[0083] The processor 520 may run, for example, software (e.g., program 540) to control at least one other component (e.g., hardware component or software component) of the electronic device 501 connected to the processor 520, and may perform various data processing or calculations. According to one embodiment of the present disclosure, as at least a part of the data processing or calculation, the processor 520 may load a command or data received from another component (e.g., sensor 576 or communication interface 590) into the volatile memory 532, process the command or data stored in the volatile memory 532, and store the result data in the non-volatile memory 534.
[0084] 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)) that is independent of or combined with the main processor 521 in operation. Additionally or alternatively, the auxiliary processor 523 may be adapted to consume less power than the main processor 521, or adapted to be specifically used for a specified function. The auxiliary processor 523 may be implemented to be separate from the main processor 521, or to be implemented as a part of the main processor 521.
[0085] When the main processor 521 is in an inactive (e.g., sleep) state, the auxiliary processor 523 may control at least some functions or states related to at least one component (e.g., display device 560, sensor 576, or communication interface 590) among the components of the electronic device 501, or when the main processor 521 is in an active state (e.g., running an application), the auxiliary processor 523 may control at least some functions or states related to at least one component (e.g., display device 560, sensor 576, or communication interface 590) among the components of the electronic device 501 together with the main processor 521. According to an embodiment, the auxiliary processor 523 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., camera module 580 or communication interface 590) that is functionally related to the auxiliary processor 523.
[0086] 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 module 576). The various data may include, for example, software (e.g., the program 540) and input data or output data for commands related thereto. The memory 530 may include a volatile memory 532 or a non-volatile memory 534.
[0087] The program 540 may be stored as software in the memory 530 , and may include, for example, an operating system (OS) 542 , middleware 544 , or an application 546 .
[0088] The input device 550 may receive commands or data to be used by other components of the electronic device 501 (e.g., the processor 520) from outside the electronic device 501 (e.g., the user). The input device 550 may include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus).
[0089] The sound output device 555 can output a sound signal to the outside of the electronic device 501. The sound output device 555 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as playing multimedia or playing records, and the receiver can be used for incoming calls. Depending on the embodiment, the receiver can be implemented as a separate speaker or as a part of the speaker.
[0090] 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 holographic device, or a projector, and a control circuit for controlling one of the display, the holographic device, and the projector. According to an 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.
[0091] The audio 570 may convert sound into an electrical signal, or vice versa. According to an embodiment, the audio 570 may obtain sound through the input device 550, or output sound through the sound output device 555 or an earphone of an external electronic device (e.g., the electronic device 502) directly connected to the electronic device 501 (e.g., using a wired cable) or wirelessly connected.
[0092] The sensor 576 may detect an operating state (e.g., power or temperature) of the electronic device 501 or an environmental state (e.g., a state of a user) outside the electronic device 501, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 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.
[0093] The interface 577 may support one or more specific protocols that will be used to connect the electronic device 501 directly (e.g., wired) or wirelessly to an external electronic device (e.g., the electronic device 502). According to an embodiment of the present disclosure, the interface 577 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.
[0094] The connection terminal 578 may include a connector, wherein the electronic device 501 can be physically connected to an external electronic device (e.g., the electronic device 502) through the connector. 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).
[0095] The haptic module 579 may convert the electrical signal into mechanical stimulation (eg, vibration or motion) or electrical stimulation that can be recognized by the user's sense of touch or kinesthetic sense. According to an embodiment, the haptic module 579 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.
[0096] 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.
[0097] The power management 588 may manage the power supply to the electronic device 501. According to an 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 an embodiment, the battery 589 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.
[0098] The communication interface 590 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 501 and an external electronic device (e.g., electronic device 502, electronic device 504, or server 508), and perform communication through the established communication channel. The communication interface 590 may include one or more communication processors capable of operating independently from the processor 520 (e.g., an application processor (AP)), and support direct (e.g., wired) communication or wireless communication.
[0099] 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 through a first network 598 (e.g., a short-range communication network such as Bluetooth, 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))).
[0100] 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 identify and authenticate the electronic device 501 in a communication network (such as the first network 598 or the second network 599) using user information (e.g., International Mobile Subscriber Identity (IMSI)) stored in the subscriber identification module 596.
[0101] The antenna module 597 may transmit a signal or power to the outside of the electronic device 501 (e.g., an external electronic device) or receive a signal or power from the outside of the electronic device 501 (e.g., an external electronic device). According to an embodiment, the antenna module 597 may include an antenna including a radiating element, and the radiating element is formed of a conductive material or a conductive pattern formed in or on a substrate (e.g., a PCB). According to an embodiment, the antenna module 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 598 or a second network 599) may be selected from the plurality of antennas by, for example, a communication interface 590 (e.g., a wireless communication interface 592). Subsequently, a signal or power may be transmitted or received between the communication interface 590 and the external electronic device through the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as part of the antenna module 597.
[0102] At least some of the above components can be connected to each other via an inter-peripheral communication scheme (e.g., a bus, a general purpose input output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) and communicate signals (e.g., commands or data) therebetween.
[0103] According to an embodiment of the present disclosure, commands or data may be sent or received between the electronic device 501 and the external electronic device 504 through the server 508 connected to the second network 599. Each electronic device 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 performed at the electronic device 501 may be performed at one or more of the external electronic devices 502, 504, or 508. For example, if the electronic device 501 can automatically perform a function or service, or in response to a request from a user or another device, instead of the electronic device 501 performing a function or service or in addition to the electronic device 501 performing a function or service, the electronic device 501 may request one or more external electronic devices to perform at least a part of 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 perform additional functions or additional services related to the request, and transmit the execution result to the electronic device 501. The electronic device 501 may provide a result, with or without further processing of the result, as at least part of a reply to the request. For this purpose, for example, cloud computing, distributed computing or client-server computing technologies may be used.
[0104] The electronic device according to various embodiments may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. According to one embodiment of the present disclosure, the electronic device is not limited to those described above.
[0105] The various embodiments described herein may be implemented as software (e.g., program 140) including one or more instructions stored in a storage medium (e.g., internal memory 536 or external memory 538) readable by a machine (e.g., electronic device 501). For example, a processor (e.g., processor 520) of a machine (e.g., electronic device 501) may call at least one of the one or more instructions stored in the storage medium and execute the instruction with or without one or more other components under the control of the processor, which allows the machine to perform at least one function according to the operation of at least one instruction called. The one or more instructions may include code generated by a compiler, or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory" refers only to the fact that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between a semi-permanent storage location of data in a storage medium and a temporary storage location of data in a storage medium.
[0106] According to the embodiments of the present disclosure, the methods of various embodiments of the present disclosure may be applied to computer program products. Computer program products may be traded between sellers and buyers as products. Computer program products may be distributed in the form of machine-readable storage media (such as compact disc read-only memory (CD-ROM)), or via application stores (such as PlayStore). TM ) online distribution (e.g. downloading or uploading), or directly between two user devices (e.g. smart phones). If distributed online, at least parts of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium, for example a memory of a manufacturer's server, a server of an application store, or a relay server.
[0107] According to various embodiments of the present disclosure, each component (such as a module or a 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 group components may be omitted, or one or more other components may be added, or multiple components (such as a module or a program) may be additionally integrated into a single component. In this case, according to various embodiments, the integrated component may still perform one or more functions of each component in the multiple components in the same or similar manner as one or more functions performed by the corresponding components in 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.
[0108] A ranging block is a time period used for ranging, each ranging block includes an integer multiple of ranging rounds, where a ranging round is a time period to complete a whole ranging measurement cycle involving a group of RDEVs participating in ranging measurement. Each ranging round is further subdivided into an integer number of ranging slots, where a ranging slot is a sufficiently long time period to transmit at least one RFRAME.
[0109] Figure 6 An exemplary ranging configuration 600 is shown in accordance with an embodiment of the disclosure. Figure 6 The embodiment of the ranging configuration 600 shown is for illustration only and does not limit the scope of the present disclosure to any particular embodiment. In one embodiment, the ranging configuration 600 may be configured as follows: Figure 8 In one embodiment, the ranging configuration 600 may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0110] Figure 6 The ranging block structure is shown, where the ranging block is divided into N ranging rounds, each ranging round includes M ranging slots.
[0111] The general ranging round structure includes a ranging control period, in which ranging control messages are sent to configure the ranging round, followed by one or more ranging periods and data periods. These data periods usually include the transmission of ranging related data using certain information elements (IEs) defined in the standard. The most common ranging round structure is as follows: Figure 7 shown.
[0112] Figure 7 An exemplary general ranging round structure 700 according to an embodiment of the present disclosure is shown. Figure 7 The embodiment of the general ranging round structure 700 shown is for illustration only and does not limit the scope of the present disclosure to any particular embodiment. Figure 8 As shown, a controller, a controlled object, an initiator, and / or a responder may use a general ranging round structure 700. 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 round structure 700.
[0113] In the present disclosure, the following nomenclature is used: controller: a ranging device that defines and controls ranging parameters by sending ranging control messages within a ranging control period; controlled object: a ranging device that utilizes ranging parameters received from a controller; initiator: a ranging device that initiates a ranging exchange by sending the first message of the exchange, or a device that sends ranging assistance data (in a payload) / data; and responder: a ranging device that receives ranging assistance data (in a payload) / data and / or responds to a message received from the initiator.
[0114] Figure 8 An exemplary ranging controller, a controlled object, an initiator, and a responder 800 according to an embodiment of the present disclosure are shown. Figure 8 The illustrated implementation of the ranging controller, controlled object, initiator, and responder 800 is for illustration only and does not limit the scope of the present disclosure to any particular implementation.
[0115] The relevant IE is the Advanced Ranging Control IE, as shown in Figure 1, which is usually sent during the ranging control period. The controller uses the Advanced Ranging Control IE (ARC IE) to send ranging configuration information to a controlled object (in a unicast frame) or to multiple controlled objects (in a multicast / broadcast frame). The format of the content field of the ARC IE can be as follows: Fig. 9 shown.
[0116] Fig. 9 An example Advanced Ranging Control IE 900 defined in 802.15.4z according to an embodiment of the present disclosure is shown. Fig. 9 The implementation of the Advanced Ranging Control IE 900 defined in 802.15.4z shown in FIG. 1 is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In one implementation, as Figure 8 As shown, the controller, the controlled object, the initiator and / or the responder may use the advanced ranging control IE 900 defined in 802.15.4z. In one embodiment, the advanced ranging control IE 900 defined in 802.15.4z may be provided by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0117] The ranging mode values are shown in Table 1. Other details of ARC IE can be found in the IEEE standard specification.
[0118] Table 1 Ranging mode values
[0119]
[0120]
[0121] The optional structure of the Advanced Ranging Control IE in the revised 802.15.4z is as follows Fig.10 shown.
[0122] Fig.10 An exemplary Advanced Ranging Control IE content field format 1000 defined in 802.15.4z according to an embodiment of the present disclosure is shown. Fig.10 The illustrated implementation of the Advanced Ranging Control IE Content Field Format 1000 defined in 802.15.4z is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In one implementation, the Advanced Ranging Control IE Content Field Format 1000 defined in 802.15.4z may be represented by: Figure 8 In one embodiment, the advanced ranging control IE content field format 1000 defined in 802.15.4z may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0123] For schedule-based ranging with multiple devices, the Ranging Schedule (RS) IE may be used to convey resource allocations, which include Fig.11 The RS table fields and RS table length field are shown. The RS table length field indicates the number of rows in the RS table.
[0124] Fig.11 An exemplary ranging scheduling IE 1100 according to an embodiment of the present disclosure is shown. Fig.11 The illustrated implementation of the ranging scheduling IE 1100 is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In one implementation, the ranging scheduling IE 1100 may be implemented as follows: Figure 8 In one embodiment, the ranging scheduling IE 1100 may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0125] Fig.12 An exemplary row 1200 of a ranging schedule according to an embodiment of the disclosure is shown. Fig.12 The embodiment of row 1200 of the ranging schedule shown is for illustration only and does not limit the scope of the present disclosure to any particular embodiment. In one embodiment, row 1200 of the ranging schedule may be composed of Figure 8In one embodiment, row 1200 of the ranging schedule table may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0126] like Fig.12 As shown, each row of the RS table includes a slot index field of a time slot, an address field of a device assigned to the time slot, and a device type field indicating the role of the assigned device. Different types of addresses can be used according to device capabilities and vendor specifications. If the device type of a specific address is 0, the device is a responder, otherwise, the device is an initiator.
[0127] Fig.13 An exemplary service primitive 1300 according to an embodiment of the present disclosure is shown. Fig.13 The illustrated implementation of the service primitive 1300 is for illustration only and does not limit the scope of the present disclosure to any particular implementation. Figure 8 As shown, the service primitive 1300 can be used by a controller, a controlled object, an initiator, and / or a responder. In one embodiment, the service primitive 1300 can be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0128] The service of a layer is the capability that the layer provides to users in the next higher layer or sublayer by building the functionality of the layer on the services of the next lower layer. Fig.13 As shown, Fig.13 The relationship between the service level and two corresponding users and their related layer (or sub-layer) peer protocol entities is shown.
[0129] A service is specified by describing the information flow between N users and N layers. The information flow is modeled by discrete temporary events, which are characterized by the provision of a service. Each event consists of passing a service primitive from one layer to another through a layer service access point (SAP) associated with N users. Service primitives convey the required information by providing a specific service. These service primitives are abstract in that they only specify the service provided, not the means by which the service is provided. The definition is independent of any other interface implementation. A service is specified by describing a service primitive and the parameters that characterize it.
[0130] A primitive can be one of four general types: (1) Request: Request primitives are used to request the initiation of a service; (2) Indication: Indication primitives are used to indicate internal events to the user; (3) Response: Response primitives are used to complete a process previously invoked by an Indication primitive; and (4) Confirmation: Confirmation primitives are used to communicate the results of one or more associated previous service requests.
[0131] The MAC sublayer provides the interface between the next higher layer and the PHY. The MAC sublayer conceptually includes a management entity called the MLME. This entity provides a service interface through which layer management can be invoked. The MLME is also responsible for maintaining a database of management objects belonging to the MAC sublayer. This database is called the MAC sublayer PIB.
[0132] Fig.14 An exemplary MAC sublayer reference model 1400 according to an embodiment of the present disclosure is shown. Fig.14 The illustrated implementation of the MAC sublayer reference model 1400 is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In one implementation, the MAC sublayer reference model 1400 may be configured as follows: Figure 8 In one embodiment, the MAC sublayer reference model 1400 may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0133] The MAC sublayer provides two services accessed through two SAPs: (1) MAC data service accessed through the MAC common part sublayer (MCPS) data SAP (MCPS-SAP); and (2) MAC management service accessed through the MAC layer management entity SAP (MLME-SAP).
[0134] These two services provide the interface between the next higher layer and the PHY.In addition to these external interfaces, there is an implicit interface between the MLME and the MCPS that allows the MLME to use the MAC data services.
[0135] The MLME-RX-ENABLE.request primitive allows the next higher layer to request to disable a receiver or enable it for a limited period of time. A receiver is enabled or disabled only once for each primitive request. The MLME-RX-ENABLE.confirm primitive reports the result of the attempt to enable or disable a receiver.
[0136] In one embodiment, primitives for specifying receiver enable times are provided.
[0137] These primitives are used to enable or disable the receiver of the device at a given time. In such embodiments, a scheme is provided to enable or disable the receiver multiple times through a single primitive request. Although the description here is in terms of the duration of the ranging round duration, other durations are not excluded, such as superframe duration, frame duration, beacon interval, interframe duration, etc.
[0138] In one example S1, a MLME-RANGING-ROUND-RX-ENABLE.request is provided by specifying the number and duration of receiver on times.
[0139] The next higher layer can disable the receiver multiple times or enable the receiver multiple times for limited periods of time in a ranging round by using a single primitive request MLME-RANGING-ROUND-RX-ENABLE.request.
[0140] The semantics of this primitive are as follows:
[0141]
[0142] The primitive parameter definitions are shown in Table 2.
[0143] Table 2 MLME-RX-ENABLE.request parameters specifying the number and duration of receiver enable
[0144]
[0145]
[0146] The MLME-RANGING-ROUND-RX-ENABLE.request primitive is generated by the next higher layer and issued to the MLME to enable a receiver for a fixed duration at a time relative to the start of the current or next ranging round. This primitive may also be generated to cancel a previously generated request to enable a receiver. The receiver is enabled based on a time in RSTU units specified by the list of integers in RxOnTimes and is disabled after the corresponding duration specified in chronological order by the list of integers in RxOnDurations. The lengths of the lists of integers specified in RxOnTimes and RxOnDurations may be the same.
[0147] The MLME may consider the request to enable or disable the receiver as secondary to the device's other responsibilities (e.g., GTS, coordinator beacon tracking, or beacon transmission). When this primitive is issued to enable a receiver, the device may enable the device's receiver until the device has a conflicting responsibility, or the time specified by RxOnDuration has expired. In the event of a conflicting responsibility, the device may interrupt the receive operation. After the interrupt operation is completed, the RxOnDuration may be checked to determine whether the time has expired, if so, the operation is completed, if not, the receiver is re-enabled until the device has another conflicting responsibility, or the time specified by RxOnDuration has expired. When this primitive is issued to disable a receiver, the device may disable the device's receiver unless the device has a conflicting responsibility.
[0148] Before attempting to enable the receiver, the MLME first determines whether each corresponding (RxOnTimes + RxOnDurations) is less than the number of RSTUs in the entire ranging round duration defined by the previous ranging control message. If the RSTU of the corresponding (RxOnTimes + RxOnDurations) is not less than the ranging round duration, the MLME issues a MLME-RXENABLE.confirm primitive with ON_TIME_TOO_LONG status.
[0149] The MLME then determines whether the receiver can be enabled within the current ranging round. If the current time measured from the start of this ranging round is less than each of the (RxOnTimes), the MLME attempts to enable the receiver in the current ranging round. If the current time measured from the start of this ranging round is greater than or equal to one or more of the RxOnTimes, and DeferPermit is equal to TRUE, the MLME defers to the next ranging round and attempts to enable the receiver in the next ranging round. Otherwise, if the MLME cannot enable the receiver in the current ranging round and delaying the receive enable operation to the next ranging round is not allowed, the MLME issues a MLME-RX-ENABLE.confirm primitive with a PAST_TIME status. If the RxOnDuration parameter is equal to zero, the MLME requests the PHY to disable the receiver.
[0150] In one example S2, a MLME-RANGING-ROUND-RX-ENABLE.request through a bitmap specification is provided.
[0151] The next higher layer can use bitmap specification to disable the receiver multiple times within a ranging round or enable the receiver multiple times for a limited time through a single primitive request MLME-RANGING-ROUND-RX-ENABLE.request. Each ranging round consists of multiple ranging scheduling time units (RSTUs). The RxOnTimes bitmap, which has a number of bits equal to the number of RSTUs in the ranging round, conveys whether the receiver is enabled or disabled for the corresponding RSTU. This does not exclude the use of other durations or nomenclatures for RSTUs (e.g., time slots, frames, etc.), and other durations or nomenclatures for ranging rounds (e.g., superframes, beacon intervals, etc.), nor does it exclude the use of bitmaps or similar discrete markings and / or indicators to specify primitives for receiver enablement or disablement for any discrete time interval (including when consecutive time intervals have unequal durations).
[0152] The semantics of this primitive are as follows:
[0153]
[0154] The primitive parameter definitions are shown in Table 3.
[0155] Table 3 MLME-RX-ENABLE.Request parameters specified by bitmap
[0156]
[0157]
[0158] When RxOnTimes is transmitted through a bitmap indicating the ON or OFF state of the receiver per RSTU per bit, RxOnDurations information is transmitted. However, in this scheme, it is not excluded to specify it.
[0159] In one embodiment, a primitive for confirming a receiver enable time is provided.
[0160] In example S3, MLME-RANGING-ROUND-RX-ENABLE.confirm is provided by enumeration.
[0161] The MLME-RANGING-ROUND-RX-ENABLE.confirm primitive reports the result of an attempt to enable or disable a receiver.
[0162] The semantics of this primitive are as follows:
[0163] MLME-RANGING-ROUND-RX-ENABLE.confirm(
[0164] Status ).
[0166] The primitive parameter definitions are shown in Table 4.
[0167] The MLME-RANGING-ROUND-RX-ENABLE.confirm primitive is generated by the MLME and sent to the next higher layer in response to the MLME-RANGING-ROUND-RX-ENABLE.request primitive. This primitive returns a success status if the request to enable or disable the receiver is successful, otherwise it returns an appropriate error code for each enable and disable request in MLME-RANGING-ROUND-RX-ENABLE.request.
[0168] Table 4 lists the MLME-RANGING-ROUND-RX-ENABLE.confirm parameters
[0169]
[0170] In Example S4, MLME-RANGING-ROUND-RX-ENABLE.confirm via a bitmap is provided.
[0171] The MLME-RANGING-ROUND-RX-ENABLE.confirm primitive reports the result of an attempt to enable or disable a receiver.
[0172] The semantics of this primitive are as follows:
[0173] MLME-RANGING-ROUND-RX-ENABLE.confirm(
[0174] Status ).
[0176] The primitive parameter definitions are shown in Table 5.
[0177] The MLME-RANGING-ROUND-RX-ENABLE.confirm primitive is generated by the MLME and sent to the next higher layer in response to the MLME-RANGING-ROUND-RX-ENABLE.request primitive. This primitive returns a bitmap indicating whether the attempt to enable or disable the receiver in each RSTU was successful. The length of the bitmap (the number of bits in the bitmap) corresponds to the number of RSTUs or the number of discrete durations or intervals used to specify the number of times the receiver is enabled or disabled. This does not exclude the use of other durations or nomenclature for RSTUs (e.g., time slots, frames, etc.), and other durations or nomenclature for ranging rounds (e.g., superframes, beacon intervals, etc.), nor does it exclude the use of bitmaps or similar discrete markers and / or indicators for any discrete time intervals (including when consecutive time intervals have unequal durations) to specify the receiver enable or disable primitive.
[0178] Table 5 MLME-RANGING-ROUND-RX-ENABLE.confirm parameters via bitmap
[0179]
[0180]
[0181] In one embodiment, a message sequence chart for primitives for receiver enablement request and confirmation is provided.
[0182] Fig.15a and 15b as well as Fig.16 Example message diagrams for MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm are shown for the controller and the controlled plant, respectively.
[0183] Fig.15a An example MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart 1500 for a controller is shown in accordance with an embodiment of the present disclosure. Fig.15aThe implementation of the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1500 for a controller shown in FIG. 1 is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In an implementation, the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1500 for a controller may be implemented as follows: Figure 8 In an embodiment, the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1500 for a controller may be used by a network entity (e.g., Figure 1 BS101-BS103 shown, Figure 1 Terminals 111-116) shown are used.
[0184] Fig.15b An exemplary MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart 1550 for a controller is shown according to an embodiment of the disclosure. Fig.15b The implementation of the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1550 for the controller shown in FIG. 1 is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In an implementation, the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1550 for the controller may be as follows: Figure 8 In an embodiment, the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1550 for the controller may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1Terminals 111-116) shown are used.
[0185] Fig.16 An example MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart 1600 for a controller is shown in accordance with an embodiment of the present disclosure. Fig.16 The implementation of the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1600 for a controller shown in FIG. 1 is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In an implementation, the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1600 for a controller may be as follows: Figure 8 In an embodiment, the MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1600 for a controller may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0186] In an embodiment, a primitive for requesting the start of a ranging round is provided.
[0187] The next higher layer uses MLME-RANGING-ROUND-START.request to indicate the start timing of the ranging round. Since the time structure of the ranging round can be managed by the next higher layer, this primitive can indicate and align the MAC timing structure.
[0188] The semantics of this primitive is:
[0189] MLME-RANGING-ROUND-START.request(
[0190] RangingRoundStart ).
[0192] The MLME-RANGING-ROUND-START.request is generated by the next higher layer and sent to the MLME at the precise moment when the ranging round starts to indicate the start of the ranging round and to align the MAC timing structure. All MAC timing counters and durations of the MLME-RANGING-ROUND-RX-ENABLE.request primitive are relative to the MLME-RANGING-ROUND-START.request primitive.
[0193] Table 6 MLME-RANGING-ROUND-START.request parameters
[0194]
[0195] Fig.17a An exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart 1700 for a controller is shown according to an embodiment of the present disclosure. Fig.17a The illustrated implementation of the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1700 for a controller is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In an implementation, the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1700 for a controller may be implemented as follows: Figure 8 In an embodiment, the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1700 for a controller may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0196] Fig.17b An exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart 1750 for a controller is shown according to an embodiment of the present disclosure. Fig.17b The illustrated implementation of the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1750 for a controller is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In an implementation, the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1750 for a controller may be implemented as follows: Figure 8 In an embodiment, the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1750 for the controller may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0197] Fig.18 An exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence chart 1800 for a controlled plant according to an embodiment of the present disclosure is shown. Fig.18The illustrated implementation of the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1800 for a controlled plant is for illustration only and does not limit the scope of the present disclosure to any particular implementation. In an implementation, the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1800 for a controlled plant may be implemented as follows: Figure 8 In an embodiment, the MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence diagram 1800 for a controlled object may be executed by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0198] Fig.15a and 15b as well as Fig.16 Example message diagrams for MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm for the controller and the controlled plant, respectively, are shown. For both the controller and the controlled plant, the MLME-RANGING-ROUND-START.request is sent by the next higher layer at the start of the ranging cycle. This indicates the start of a ranging round. For the controller, the MLME-RANGING-ROUND-RX-ENABLE.request is sent by the next higher layer to the MAC after the next higher layer of the controller has set up the configuration of the ranging round including the ranging round schedule. This can be as follows Fig.17a After the next higher layer transmits the RCM to the MAC as shown, or it can be as shown Fig.17b Before the controller sends the RCM to the MAC, either of these two options is determined by the implementation choice. Fig.18As shown, after receiving the RCM and scheduling information (ARC IE and RDM IE), MLME-RANGING-ROUND-RX-ENABLE.request is sent by the next higher layer to MAC.
[0199] In one embodiment, a receiver enabled time reference for an enhanced ranging device (ERDEV) is provided.
[0200] The 802.15.4z standard specifies ERDEV. Receiver enable, such as MLME-RX-ENABLE.request, is a primitive transmitted by the next higher layer to the MAC of ERDEV to enable the receiver. This primitive specifies the time and duration for enabling the receiver. The time of enabling is relative to a reference. If the device is an ERDEV, and if the device is beacon-enabled, the beacon is selected as the time reference. If the device is an ERDEV, and if the device is not beacon-enabled, the RSTU counter value is transmitted to the timestamp parameter of the MCPS-DATA.indication primitive of the next higher layer as a reference for transmitting the receiver enable time and duration according to the RSTU. Further details are as described in other embodiments.
[0201] In one embodiment, a primitive for enabling Rx using a beacon or timestamp parameter is provided.
[0202] In Example S4, primitives for using MLME-RX-ENABLE.request are provided.
[0203] In the case of non-beacon enabled ERDEV, the next higher layer can directly specify the RSTU counter value to specify the RxOnTime. When the TxTimeSpecificed parameter of MCPS-DATA.indication is set to RSTU_TIME, the next higher layer can use the timestamp parameter of the most recent RCM as a reference to the RSTU counter value to specify the RxOnTime. The next higher layer can use the timestamp parameter of the MCPS-DATA.indication from any other message to maintain synchronization. When the RSTU counter value of RxOnTime is less than the current RSTU value, RxOnTime can be understood as the RSTU with reference to the counter value after wrapping when DeferPermit is true.
[0204] For a beacon-enabled ERDEV, when the TxTimeSpecificed parameter of the MCPS-DATA.indication is set to RSTU_TIME, the next higher layer may specify the RxOnTime using the timestamp parameter of the most recent beacon (enhanced beacon frame) as a reference for the RSTU counter value.
[0205] The semantics of this primitive are as follows:
[0206]
[0207] The primitive parameter definitions are shown in Table 7.
[0208] Table 7 MLME-RX-ENABLE.request parameters for ERDEV
[0209]
[0210]
[0211] The next higher layer of ERDEV can request the receiver to be enabled multiple times for a limited duration or disabled multiple times within a ranging round through a single MLME-RX-ENABLE.request primitive. This is achieved by configuring the RxOnTime and RxOnDuration parameters as a list of integers as shown in Table 8 and other parameters as shown in Table 7.
[0212] Table 8 MLME-RX-ENABLE.Request vector parameters for ERDEV
[0213]
[0214]
[0215] The LME-RX-ENABLE.request primitive is generated by the next higher layer and sent to the MLME to enable a receiver for a fixed duration at a time specified using the RSTU counter value. This primitive may also be generated to cancel a previously generated request to enable a receiver. Receivers are enabled based on a time in RSTUs specified by the list of integers in RxOnTime and are disabled after the corresponding durations specified in chronological order by the list of integers in RxOnDuration. The lengths of the lists of integers specified in RxOnTime and RxOnDuration may be the same.
[0216] The MLME may consider the request to enable or disable the receiver as secondary to the device's other responsibilities (e.g., GTS, coordinator beacon tracking, or beacon transmission). When the primitive is issued to enable the receiver, the device may enable the receiver until the device has a conflicting responsibility or the time specified by RxOnDuration has expired. In the event of a conflicting responsibility, the device may interrupt the receive operation. After the interrupt operation is completed, the RxOnDuration may be checked to determine whether the time has expired, if so, the operation is completed, if not, the receiver is re-enabled until the device has another conflicting responsibility or the time specified by RxOnDuration has expired. When the primitive is issued to disable the receiver, the device may disable the receiver unless the device has a conflicting responsibility.
[0217] The MLME then determines whether the receiver can be enabled for the specified RSTU counter value. If the current RSTU counter value is lower than the specified counter value of RxOnTime, the MLME attempts to enable the receiver within the current ranging round. If the current RSTU counter value is higher than the specified counter value of RxOnTime and DeferPermit is equal to TRUE, the MLME delays until the RSTU counter wraps around and attempts to enable the receiver within this ranging round; otherwise, if the MLME cannot enable the receiver within the current ranging round and delaying the receive enable operation until after the wrap is not allowed, the MLME issues an MLME-RX-ENABLE.confirm primitive with a PAST_TIME status.
[0218] If the RxOnDuration parameter is equal to zero, the MLME requests the PHY to disable the receiver.
[0219] In one embodiment, primitives are provided for receiving enable confirmation using beacons or timestamps.
[0220] In implementation S5, MLME-RX-ENABLE.confirm is provided.
[0221] The MLME-RX-ENABLE.confirm primitive reports the result of an attempt to enable or disable a receiver.
[0222] The semantics of this primitive are as follows:
[0223] MLME-RX-ENABLE.confirm(
[0224] Status ).
[0226] The primitive parameters are defined in Tables 9 and 10 as a vector corresponding to the MLME-RX-ENABLE.request vector parameter of ERDEV.
[0227] The MLME-RX-ENABLE.confirm primitive is generated by the MLME and sent to the next higher layer in response to the MLME-RX-ENABLE.request primitive. For each enable and disable request in MLME-RX-ENABLE.request, the primitive returns a success status if the request to enable or disable the receiver is successful, otherwise it returns an appropriate error code.
[0228] Table 9 MLME-RX-ENABLE.confirm parameters of ERDEV
[0229]
[0230] Table 10 MLME-RX-ENABLE.confirm vector parameters of ERDEV
[0231]
[0232] In one embodiment, a primitive is provided for indicating that a frame was not received.
[0233] In example S6, MLME-RX-ENABLE.indication is provided.
[0234] The semantics of this primitive are as follows:
[0235] MLME-RX-ENABLE.indication(
[0236] TimeStamp ).
[0238] If no frame is received within the duration specified by RxOnTime + RxOnDuration for each instance of RxOnTime, the MLME-RX-ENABLE.indication primitive of ERDEV reports a timeout.
[0239] Table 11MLME-RX-ENABLE.indication parameters of ERDEV
[0240]
[0241] Fig.19A flow chart 1900 of MLME-RX-ENABLE.indication of ERDEV according to an embodiment of the present disclosure is shown, wherein RxAutoOff=TRUE, which may be performed by a network entity. Fig.19 The embodiment of the flowchart 1900 shown in FIG. 1 is for illustration only and does not limit the scope of the present disclosure to any particular embodiment. In one embodiment, the flowchart 1900 may be as follows: Figure 8 In one embodiment, flowchart 1900 may be used by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116 shown) are executed.
[0242] like Fig.19 As shown, in step 1902, the network entity identifies the MLME-RX-ENABLE.request in the ERDEV. In step 1904, the network entity identifies the MAC / MAC RSTU_COUNTER. In step 1906, the network entity determines whether RSTU_COUNTER == RxOnTime. If yes in step 1906, the network entity waits for a frame and increases the MAC RSTU_COUNTER in step 1908. If no in step 1906, the network entity performs step 1904 again. In step 1910, the network entity determines whether a frame is received. If a frame is received in step 1910, the network entity issues an appropriate indication primitive (e.g., MCPS-DATA.indication) and disables the receiver in step 1914. If no frame is received in step 1910, the network entity determines whether RSTU_COUNTER <= RxOnTime + RxOnDuration in step 1916. If yes in step 1916, the network entity performs step 1908 again. If no in step 1916 , the network entity issues a RX-ENABLE.indication with a timestamp parameter in step 1918 .
[0243] Fig. 20 A flowchart of a method 2000 for specifying a receiver enable time according to an embodiment of the present disclosure is shown, which may be executed by a network entity. Fig. 20 The embodiment of method 2000 shown is for illustration only and does not limit the scope of the present disclosure to any particular embodiment. In one embodiment, method 2000 may be performed as follows: Figure 8 In one embodiment, method 2000 may be performed by a network entity (e.g., Figure 1 As shown in BS101-103, Figure 1 Terminals 111-116) shown are used.
[0244] like Fig. 20 As shown, method 2000 starts from step 2002.
[0245] In step 2002, the network entity identifies a medium access control (MAC) sublayer management entity receive enable request (MLME-RX-ENABLE.request) primitive including a list of ranging scheduling time unit (RSTU) counter (RxOnTime) values and the number of RSTUs (RxOnDuration), wherein the MLME-RX-ENABLE.request primitive is sent from a higher layer to the MAC layer.
[0246] In one embodiment, in step 2002, the MLME-RX-ENABLE.indication primitive includes a timestamp parameter including the current value of the MAC RSTU_COUNTER, and the MLME-RX-ENABLE.indication primitive is sent from the MAC layer to a higher layer.
[0247] In such an embodiment, the current value of the MAC RSTU_COUNTER is determined based on the RxOnTime value and the RxOnDuration.
[0248] In such an embodiment, the MLME-RX-ENABLE.request primitive also includes a receive auto-off (RxAutoOff) indicating the state of the transceiver for receiving frames.
[0249] In one embodiment, when RxAutoOff is set to TRUE, the transceiver is disabled after receiving a frame; when RxAutoOff is set to FALSE, the transceiver remains enabled during the RxOnDuration.
[0250] In one embodiment, when RxAutoOff is set to TRUE, a MCPS-DATA.indication primitive is sent from the MAC layer to a higher layer; and the MCPS-DATA.indication primitive includes an indication that a packet is received from the another network entity.
[0251] Thereafter, in step 2004, the network entity identifies a value of a MAC RSTU counter (MAC RSTU_COUNTER) in response to identifying the MLME-RX-ENABLE.request primitive.
[0252] Thereafter, in step 2006, the network entity determines whether the value of the MAC RSTU_COUNTER is set to an RxOnTime value included in the list of RxOnTime values of the MLME-RX-ENABLE.request primitive.
[0253] Thereafter, in step 2006, the network entity increases the value of the MAC RSTU_COUNTER.
[0254] Next, in step 2010, the network entity determines whether a frame is received from another network entity based on the value of the MAC RSTU_COUNTER.
[0255] Finally, in step 2012, the network entity generates a MAC common part sublayer indication (MCPS-DATA.indication) primitive in response to determining that the frame is received.
[0256] In one embodiment, after generating and sending the MCPS-DATA.indication primitive from the MAC layer to higher layers, the network entity prohibits receiving frames.
[0257] In one embodiment, the network entity determines whether the value of the MAC RSTU_COUNTER is less than or equal to the sum of the RxOnTime value and the RxOnDuration in response to determining that the frame was not received.
[0258] In one embodiment, the network entity generates the MLME-RX-ENABLE.indication primitive in response to determining that the value of the MAC RSTU_COUNTER is greater than the sum of the RxOnTime value and the RxOnDuration.
[0259] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be made by those skilled in the art accordingly. The present disclosure includes these changes and modifications that fall within the scope of the appended claims. Any description in the present disclosure should not be understood as implying that any specific element, step or function is an essential element that must be included in the scope of the claims. The scope of protection of this application is defined by the claims.
Claims
1. A device supporting ranging capability in a wireless communication system, the device include: Transceiver; as well as a processor operably connected to the transceiver, the processor being configured to: receiving, at a medium access control MAC layer, a receive enable request MLME-RX-ENABLE.request from a higher layer, wherein the MLME-RX-ENABLE.request includes first information associated with at least one time of a ranging scheduling time unit RSTU for which a receiver side of the transceiver is to be enabled and second information associated with at least one time duration for which the receiver side of the transceiver is to be enabled; Based on the MLME-RX-ENABLE.request, identifying whether a receiver side of the transceiver can be enabled for a predetermined time period; as well as A receive enable confirmation MLME-RX-ENABLE.confirm is sent from the MAC layer to the higher layer to report a result of determining to enable the receiver side of the transceiver.
2. The device according to claim 1, in, The processor is further configured to, upon receiving the MLME-RX-ENABLE.request for enabling the receiver side of the transceiver, enable the receiver side of the transceiver until the device has conflicting responsibilities or a duration specified by the second information expires.
3. The device as claimed in claim 2, in, The processor is further configured to: interrupting the receiving operation in the event that the device has conflicting responsibilities; After completing the interrupt operation, checking the second information to determine whether the duration has expired; In case the duration has expired, completing the receiving operation; as well as If the duration has not expired, the receiver side of the transceiver is re-enabled until the device has another conflicting responsibility, or the duration expires.
4. The device according to claim 1, in, In case the MLME-RX-ENABLE.request for enabling the receiver side of the transceiver is successful, the MLME-RX-ENABLE.confirm includes a SUCCESS status.
5. The device according to claim 1, in, The processor is further configured to: Wherein, in a case where a sum of the enabling time obtained based on the first information and the duration obtained based on the second information is not less than a predetermined time interval, the MLME-RX-ENABLE.confirm includes an ON_TIME_TOO_LONG state.
6. The device according to claim 1, in, The MLME-RX-ENABLE.request further includes a receive auto-off RxAutoOff of TRUE or FALSE, and Wherein, the processor is further configured to: disabling the receiver side of the transceiver immediately after receiving data if the RxAutoOff is TRUE; and In the case where the RxAutoOff is FALSE, the receiver side of the transceiver is kept enabled after receiving data.
7. The device according to claim 6, in, The processor is further configured to: disabling a receiver side of the transceiver at the end of the enablement period; and A receive enable indication MLME-RX-ENABLE.indication including the timestamp parameter of RSTU is issued.
8. The device according to claim 7, in, In case the RxAutoOff is TRUE and no frames are received during the enable period, the MLME-RX-ENABLE.indication is issued.
9. A method performed by a device supporting ranging capability in a wireless communication system, the method include: receiving, at a medium access control MAC layer, a receive enable request MLME-RX-ENABLE.request from a higher layer, wherein the MLME-RX-ENABLE.request comprises first information associated with at least one time of a ranging scheduling time unit RSTU for which a receiver side of a transceiver is to be enabled and second information associated with at least one time duration for which the receiver side of the transceiver is to be enabled; Based on the MLME-RX-ENABLE.request, identifying whether a receiver side of the transceiver can be enabled for a predetermined time period; and A receive enable confirmation MLME-RX-ENABLE.confirm is sent from the MAC layer to the higher layer to report a result of determining to enable the receiver side of the transceiver.
10. The method of claim 9, further comprising: include: When the MLME-RX-ENABLE.request for enabling the receiver side of the transceiver is received, the receiver side of the transceiver is enabled until the device has conflicting responsibilities or a duration specified by the second information expires.
11. The method of claim 9, further comprising: include: interrupting the receiving operation in the event that the device has conflicting responsibilities; After completing the interrupt operation, checking the second information to determine whether the duration has expired; In case the duration has expired, completing the receiving operation; as well as If the duration has not expired, the receiver side of the transceiver is re-enabled until the device has another conflicting responsibility, or the duration expires.
12. The method according to claim 9, in, In case the MLME-RX-ENABLE.request for enabling the receiver side of the transceiver is successful, the MLME-RX-ENABLE.confirm includes a SUCCESS status.
13. The method of claim 9, in, In a case where a sum of the enabling time obtained based on the first information and the duration obtained based on the second information is not less than a predetermined time interval, the MLME-RX-ENABLE.confirm includes an ON_TIME_TOO_LONG state.
14. The method of claim 9, in, The MLME-RX-ENABLE.request further includes a receive auto-off RxAutoOff of TRUE or FALSE, and The method comprises: disabling the receiver side of the transceiver immediately after receiving data if the RxAutoOff is TRUE; and In the case where the RxAutoOff is FALSE, the receiver side of the transceiver is kept enabled after receiving data.
15. A computer-readable medium storing program code, which, when executed by at least one processor, enables an apparatus supporting ranging capability in a wireless communication system: receiving, at a medium access control MAC layer, a receive enable request MLME-RX-ENABLE.request from a higher layer, the MLME-RX-ENABLE.request comprising first information associated with at least one time of a ranging scheduling time unit RSTU for which a receiver side of a transceiver is to be enabled and second information associated with at least one time duration for which the receiver side of the transceiver is to be enabled; Based on the MLME-RX-ENABLE.request, identifying whether a receiver side of the transceiver can be enabled for a predetermined time period; and A receive enable confirmation MLME-RX-ENABLE.confirm is sent from the MAC layer to the higher layer to report a result of determining to enable the receiver side of the transceiver.
