Search

KR-102962934-B1 - Device and method for specifying receiver activation times in UWB communication and ranging systems

KR102962934B1KR 102962934 B1KR102962934 B1KR 102962934B1KR-102962934-B1

Abstract

A method and apparatus for a network entity in a wireless communication system supporting a ranging capability are provided. The method and apparatus identify a MAC sublayer management entity receive enable request (MLME-RX-ENABLE.request) primitive comprising a list of ranging scheduling time unit (RSTU) counter (RxOnTime) values and an RSTU number (RxOnDuration), wherein the MLME-RX-ENABLE.request primitive is transmitted from an upper layer to the MAC layer; identify a value of MAC RSTU_COUNTER in response to identifying the MLME-RX-ENABLE.request primitive; determine whether the value of MAC RSTU_COUNTER is set to an RxOnTime value included in the list of RxOnTime values of the MLME-RX-ENABLE.request primitive; and determine whether a frame is received from another network entity based on the value of MAC RSTU_COUNTER. and in response to the determination that a frame is received, it includes generating a MAC Common Part Sublayer Indication (MCPS-DATA.indication) primitive.

Inventors

  • 파다키 아디트야 브이.
  • 리 제다
  • 엔지 분 룽

Assignees

  • 삼성전자주식회사

Dates

Publication Date
20260508
Application Date
20200520
Priority Date
20200514

Claims (15)

  1. In a device that supports ranging capability in a wireless communication system, Transmitter/receiver; and It includes a processor operatively connected to the above-mentioned transmitter and receiver, The above processor The MAC (medium access control) layer receives an enable access request (MLME-RX-ENABLE.request) including RxOnTime and RxOnDuration from the upper layer, The above RxOnTime includes a list of values associated with times in units of a ranging scheduling time unit (RSTU) during which the receiving side of the transceiver is activated, and The above RxOnDuration includes a list of values related to the durations during which the receiving side of the transceiver is active, and Based on the above RxOnTime and RxOnDuration, an operation related to enabling or disabling the receiving side of the transceiver is performed, and A device that transmits a reception enable confirmation (MLME-RX-ENABLE.confirm) from the MAC layer to the upper layer to report result information.
  2. In claim 1, the processor is a device that, when the receive enable request (MLME-RX-ENABLE.request) is received, enables the receiving side of the transceiver until the device has a collision duty or until the duration specified by the RxOnDuration expires.
  3. In paragraph 2, the processor If the above device has the above collision duty, it stops the receiving operation, and After the suspension operation is completed, the RxOnDuration is checked to determine whether the specified duration has expired, and When the above specified duration expires, the above receiving operation is completed, and A device that, if the specified duration has not expired, has another collision duty or reactivates the receiving side of the transceiver until the specified duration expires.
  4. In claim 1, the device wherein, when the reception enable request (MLME-RX-ENABLE.request) is successful, the reception enable confirmation (MLME-RX-ENABLE.confirm) includes a SUCCESS status.
  5. In claim 1, if the sum of the activation time obtained based on the RxOnTime and the duration obtained based on the RxOnDuration is not less than a predetermined time interval, the device in which the reception activation confirmation (MLME-RX-ENABLE.confirm) includes the state of ON_TIME_TOO_LONG.
  6. In paragraph 1, the reception enable request (MLME-RX-ENABLE.request) further includes RxAutoOff, and The above RxAutoOff includes a list of booleans indicating whether the receiving side of the transceiver is disabled, and If the value of the above RxAutoOff is TRUE, the receiving side of the above transceiver is deactivated immediately after receiving data, and A device in which, when the value of RxAutoOff is FALSE, the receiving side of the transceiver is maintained in an active state with respect to the value of RxOnDuration.
  7. In paragraph 6, the above processor At the end of the activation period specified by the above RxOnDuration, the receiving side of the above transceiver is deactivated, and A device that issues a receive enable indication (MLME-RX-ENABLE.indication) having a time stamp parameter of the above RSTU unit.
  8. A device according to claim 7 in which, if the value of RxAutoOff is TRUE and no frame is received during the activation period, the reception enable indication (MLME-RX-ENABLE.indication) is issued.
  9. In a method performed by a device that supports ranging capability in a wireless communication system, The MAC (medium access control) layer receives an enable request (MLME-RX-ENABLE.request) containing RxOnTime and RxOnDuration from the upper layer, The above RxOnTime includes a list of values associated with times in units of a ranging scheduling time unit (RSTU) during which the receiving side of the transmitter and receiver is active, and Step, wherein the above RxOnDuration includes a list of values related to the durations during which the receiving side of the transceiver is activated; A step of performing operations related to enabling or disabling the receiving side of the transceiver based on the above RxOnTime and the above RxOnDuration; and A method comprising the step of transmitting a reception enable confirmation (MLME-RX-ENABLE.confirm) from the MAC layer to the upper layer to report result information.
  10. In claim 9, a method further comprising the step of, when the reception enable request (MLME-RX-ENABLE.request) is received, activating the receiving side of the transceiver until the device has a collision obligation or until the duration specified by the RxOnDuration expires.
  11. In Paragraph 10, If the above device has the collision duty, a step of stopping the receiving operation; A step of checking the RxOnDuration to determine whether the specified duration has expired after the suspension operation is completed; A step of completing the receiving operation when the specified duration mentioned above has expired; and A method further comprising the step of reactivating the receiving side of the transceiver when the specified duration has not expired, or when the device has another collision duty, or until the specified duration expires.
  12. In claim 9, the method wherein, when the receive enable request (MLME-RX-ENABLE.request) is successful, the receive enable confirmation (MLME-RX-ENABLE.confirm) includes a SUCCESS status.
  13. In claim 9, if the sum of the activation time obtained based on the RxOnTime and the duration obtained based on the RxOnDuration is not less than a predetermined time interval, the reception activation confirmation (MLME-RX-ENABLE.confirm) includes the state of ON_TIME_TOO_LONG.
  14. In paragraph 9, the above reception enable request (MLME-RX-ENABLE.request) further includes RxAutoOff, and The above RxAutoOff includes a list of booleans indicating whether the receiving side of the transceiver is disabled, and If the value of the above RxAutoOff is TRUE, the receiving side of the above transceiver is deactivated immediately after receiving data, and A method in which, when the value of RxAutoOff is FALSE, the receiving side of the transceiver is maintained in an active state with respect to the value of RxOnDuration.
  15. delete

Description

Device and method for specifying receiver activation times in UWB communication and ranging systems The present disclosure generally relates to frameworks and methods for specifying receiver activation times in UWB communication and ranging systems. A peer-aware communication (PAC) network is a fully distributed communication network that allows direct communication between PAC devices (PDs). A PAC device is an electronic device capable of communication. Additionally, a PAC device may also possess a ranging capability. A PAC device may be referred to as a ranging device (RDEV), an enhanced ranging device (ERDEV), a secure ranging device (SRDEV), or any other similar name. An RDEV, ERDEV, or SRDEV may be part of an access point (AP), station (STA), eNB, gNB, UE, or any other communication node that possesses ranging capability as defined in IEEE standard specifications. PAC networks may employ various topologies, such as mesh or star, to support interactions between PDs for various services. For a more complete understanding of the present disclosure and its merits, the following description, taken in conjunction with the accompanying drawings in which similar reference numbers denote similar parts, will now be mentioned, among which: FIG. 1 illustrates an exemplary wireless network according to embodiments of the present disclosure; FIG. 2 illustrates an exemplary gNB according to embodiments of the present disclosure; FIG. 3 illustrates an exemplary UE according to embodiments of the present disclosure; FIG. 4a illustrates an upper-level diagram of an orthogonal frequency division multiple access transmission path according to embodiments of the present disclosure; FIG. 4b illustrates an upper-level diagram of an orthogonal frequency division multiple access receiving path according to embodiments of the present disclosure; FIG. 5 illustrates an exemplary electronic device according to embodiments of the present disclosure; FIG. 6 illustrates an exemplary ranging configuration according to embodiments of the present disclosure; FIG. 7 illustrates an exemplary general ranging round structure according to embodiments of the present disclosure; FIG. 8 illustrates an exemplary ranging controller, controller, initiator, and responder according to embodiments of the present disclosure; FIG. 9 illustrates an exemplary advanced ranging control IE as defined in 802.15.4z according to embodiments of the present disclosure; FIG. 10 illustrates an exemplary advanced ranging control IE content field format as defined in 802.15.4z according to embodiments of the present disclosure; FIG. 11 illustrates an exemplary ranging scheduling IE according to embodiments of the present disclosure; FIG. 12 illustrates an exemplary row of a ranging scheduling table according to embodiments of the present disclosure; FIG. 13 illustrates exemplary service primitives according to embodiments of the present disclosure; FIG. 14 illustrates an exemplary MAC sublayer reference model according to embodiments of the present disclosure; FIG. 15a illustrates exemplary MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence charts for a controller according to embodiments of the present disclosure; FIG. 15b illustrates exemplary MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence charts for a controller according to embodiments of the present disclosure; FIG. 16 illustrates exemplary MLME-RANGING-ROUND-RX-ENABLE.request and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence charts for a controller according to embodiments of the present disclosure; FIG. 17a illustrates exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence charts for a controller according to embodiments of the present disclosure; FIG. 17b illustrates exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence charts for a controller according to embodiments of the present disclosure; FIG. 18 illustrates exemplary MLME-RANGING-ROUND-START.request, MLME-RANGING-ROUND-RX-ENABLE.request, and MLME-RANGING-ROUND-RX-ENABLE.confirm message sequence charts for a controller according to embodiments of the present disclosure; FIG. 19 illustrates a flowchart for an MLME-RX-ENABLE.indication for an ERDEV having RxAutoOff=TRUE according to embodiments of the present disclosure; and FIG. 20 illustrates a flowchart of a method for specifying receiver activation times according to embodiments of the present disclosure. Before proceeding to the “Description of Specific Details for Carrying Out the Invention” below, it may be advantageous to mention the definitions of specific words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whethe