Managing timing of electronic shelf tag connections

By managing the timing method of ESL connection in AP, predicting and optimizing the completion time of the ESL connection, the problem of large time gap between ESL and AP communication links in the prior art is solved, and data transmission efficiency and throughput of the ESL system are improved.

CN120112912APending Publication Date: 2025-06-06QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280101368.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-11-11
Publication Date
2025-06-06

AI Technical Summary

Technical Problem

In the prior art, the communication link establishment time gap between the electronic shelf tag (ESL) and the access point (AP) is large, resulting in data delivery delays, and conventional attempts to reduce the time gap may reduce the operational efficiency of the ESL or increase tissue complexity.

Method used

By implementing a timing method for managing the establishment of a connection with the ESL in the AP, the completion time of the first connection is predicted and a connection request is sent to the second ESL during the first connection to reduce the time gap between the first connection and the second connection.

Benefits of technology

It effectively reduces the communication link time gap between AP and ESL, improves data transmission efficiency, and increases the overall data throughput of the ESL system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120112912A_ABST
    Figure CN120112912A_ABST
Patent Text Reader

Abstract

Aspects include a method, executable by an access point (AP), for managing timing to establish a communication link with an electronic shelf label (ESL). An AP may perform a communication operation with a first ESL using a first connection during a first connection duration and send a connection request to a second ESL before completing the communication operation with the first ESL during the first connection duration. The AP may establish a second connection with the second ESL based on the connection request transmitted to the second ESL. The AP may establish the second connection with the second ESL in a second connection duration that begins at or shortly after the end of the first connection duration.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] Electronic shelf labels (ESLs) are devices that can be used in supermarkets, supply stores, warehouses, etc. to generally monitor and control inventory tracking, product mapping, price change rollouts, and customer experience. ESLs can communicate with a network access point (AP) using an energy-efficient, short-range wireless communication protocol such as Bluetooth Low Energy.

[0002] The AP may broadcast periodic advertisement (PA) messages at substantially regular intervals. Such PA messages may include an operation code for accessing a bootstrap ESL, or may serve as a synchronization signal for use by the ESL. Once the data download is complete, the connection between the AP and the ESL is disconnected. In order to perform subsequent communication activities, a reconnection is required, and the AP may transmit an AUX_CONNECT_REQ (ACRQ) message to the ESL. In operation, the AP may communicate with hundreds or thousands of ESLs. Summary of the invention

[0003] Various aspects of the present disclosure include methods for managing the timing of establishing a connection with an ESL, such as an asynchronous connectionless (ACL) communication link, and an access point (AP) configured to perform the method. Various aspects may include: performing a communication operation with a first electronic shelf label (ESL) using a first connection during a first connection duration; transmitting a connection request to a second ESL before completing the communication operation with the first ESL during the first connection duration; and establishing a second connection with the second ESL based on the connection request transmitted to the second ESL.

[0004] In some aspects, establishing the second connection with the second ESL based on the connection request transmitted to the second ESL may include: establishing the second connection with the second ESL in a second connection duration, the second connection duration starting at the end of the first connection duration. In some aspects, sending the connection request to the second ESL before completing the communication operation with the first ESL during the first connection duration may include: sending the connection request to the second ESL in a sub-event during the first connection duration, in which the second ESL receives a synchronization signal from the AP. In some aspects, sending the connection request to the second ESL before completing the first connection duration with the first ESL may include: sending the connection request to the second ESL at an offset time before the first connection is completed, wherein the offset time may include a time interval based on a wake-up period of the second ESL.

[0005] In some aspects, establishing the second connection with the second ESL based on the connection request transmitted to the second ESL may include: receiving a connection response from the second ESL during the first connection duration based on the connection request transmitted to the second ESL; and establishing the second connection with the second ESL at the end of the first connection duration based on the connection response received from the second ESL. Some aspects may include: sending a connection request to a third ESL before the first connection duration with the first ESL is completed in response to not receiving a connection response from the second ESL; and establishing the second connection with the third ESL based on a connection response received from the third ESL in response to the connection request sent to the third ESL.

[0006] Some aspects may include sending data to the second ESL at the beginning of the second connection duration. Some aspects may include sending data to the second ESL at the end of a wake-up period of the second ESL. In some aspects, establishing the second connection with the second ESL based on the connection request transmitted to the second ESL may include sending first data to the second ESL before the end of the first connection duration, and sending second data to the second ESL in a second connection duration, the second connection duration starting at the end of the first connection duration. In some aspects, sending the first data to the second ESL before the end of the first connection duration may include sending the first data to the second ESL after a wake-up period of the second ESL, the wake-up period of the second ESL ending before the end of the first connection duration.

[0007] Further aspects may include an AP configured with a processor configured to perform one or more operations of any of the methods outlined above. Further aspects may include an AP having a processor configured to perform one or more operations of any of the methods outlined above. Further aspects may include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause the processor of the AP to perform the operations of any of the methods outlined above. Further aspects may include an AP having components for performing the functionality of any of the methods outlined above. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The accompanying drawings, which are incorporated herein and constitute a part of this specification, illustrate exemplary embodiments of the claims and, together with the general description given above and the detailed description given below, serve to explain features of the claims.

[0009] Figure 1A is a system block diagram illustrating an ESL system suitable for implementing any of the various embodiments.

[0010] Figure 1B is a system block diagram illustrating an example configuration for signal communications in an ESL system implementing some embodiments.

[0011] Figure 2 is a component block diagram illustrating an example computing and wireless modem system on a chip suitable for use in a computing device implementing any of the various embodiments.

[0012] FIG. 3A to FIG. 3C is a timeline illustrating aspects of a method for managing the timing of establishing a connection with an ESL according to various embodiments.

[0013] Figure 4 is a process flow diagram of a method of managing the timing of establishing a connection with an ESL according to various embodiments.

[0014] FIG. 5A to FIG. 5E is a process flow diagram of operations that may be performed as part of a method of managing the timing of establishing a connection with an ESL according to various embodiments.

[0015] Figure 6 is a component block diagram of an ESL suitable for use in various implementations.

[0016] Figure 7 is a component block diagram of an access point suitable for use in various embodiments.

[0017] Figure 8 is a component block diagram of a server suitable for use in various implementations.

[0018] Fig. 9 is a component block diagram of a user mobile device suitable for use in various embodiments. DETAILED DESCRIPTION

[0019] Various embodiments will be described in detail with reference to the accompanying drawings. Where possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.

[0020] Various embodiments include methods for enabling an access point (AP) to manage establishing a connection with an electronic shelf label (ESL), such as an asynchronous connection-oriented logical transport (ACL) communication link, to reduce time gaps between communication links established between the AP and the ESL, and an AP configured to implement the method. Various embodiments improve the operation of the AP, ESL, and ESL system by reducing time gaps between ACL communication links, thereby increasing the overall data throughput from the AP to the ESL in the ESL system.

[0021] The term "electronic shelf label" or "ESL" is used herein to refer to a computing device with an electronic display that can be placed or fixed to a store shelf, in a shelf, on a shelf, or near a shelf. The ESL may include a processor, a memory, a display, and one or more wireless transceivers, wherein the processor may be programmed or provided with data to render an image (e.g., text, a barcode, a trademark, etc.) that conveys (e.g., to a person) information about a product near the device. In some aspects, the ESL may be battery powered so that it can be placed on or near a product without the need for a power infrastructure. Alternatively, the ESL may also be powered by the shelf to which the ESL is fixed.

[0022] The ESL can be programmed, reprogrammed, or updated (e.g., via a guidance message sent by the AP) so that the product information rendered on the display can be updated at any time. Thus, the ESL can provide the functionality of a paper shelf label with the added efficiency of enabling product information (e.g., price) to be changed without physically replacing the shelf label.

[0023] Although various embodiments are described with reference to the ESL being placed on a shelf within a store, the ESL may also be positioned on large goods (e.g., furniture, appliances, etc.), on or near a shelf or stack of goods, on a pallet on which products are positioned, and other locations where products may be provided for sale or selection. Further, the ESL may be used for other purposes, such as being placed on a door to indicate an empty or occupied state. The use of the term "shelf" (or as represented by the "S" in the ESL) is not intended to limit the claims to tags positioned only on shelves.

[0024] In some configurations, the ESL may include an XR tag that transmits signals to an extended reality (XR) device (e.g., smart glasses, a display screen of a smart phone, or other device configured to provide an extended reality display), the signals being configured to cause the XR device to generate a visible display. What is visible on the display of the XR device based on the signals from the XR tag may be visible when a store picker or other user views the ESL (i.e., orients the XR glasses in the direction of the ESL). For example, an XR device for a bag of potato chips may display product-related information, such as "Lays Potato Chips $1.99". The information provided by the XR tag may be the same or different than the information visible in the ESL to a normal user who is not using XR glasses or another XR device. In some embodiments, the ESL may not include a display, but may instead operate as an XR anchor to transmit operational messages and other information to the XR device. For example, when a user wearing XR glasses views a product (e.g., Lays Potato Chips), a small window may appear on the user interface (UI) displaying product information (e.g., “Lays Potato Chips $1.99”).

[0025] As used herein, the term "computing device" refers to an electronic device equipped with at least a processor, a memory, and a device for presenting an output (such as, the position of one or more objects of interest). In some embodiments, the computing device may include a wireless communication device (such as, a transceiver and an antenna) configured to communicate with a wireless communication network. The computing device may include any one or all of the following: an external smart device, a baseband, a smart watch, a smart ring, a smart necklace, smart glasses, smart contact lenses, a contactless sleep tracking device, smart furniture such as a smart bed or a smart sofa, smart exercise equipment, an Internet of Things (IoT) device, an augmented / virtual reality device, a cellular phone, a smart phone, a portable computing device, a personal or mobile multimedia player, a laptop computer, a tablet computer, a 2-in-1 laptop / desktop computer, a smartbook, an ultrabook, an Internet-enabled multimedia cellular phone, an entertainment device (e.g., a wireless game controller, a music and video player, a satellite radio, etc.), and similar electronic devices including a memory, a wireless communication component, and a programmable processor. In some embodiments, the computing device may be a personal wearable device. As used herein, the term "intelligent" in connection with a device refers to a device that includes a processor for automatic operation, for collecting and / or processing data, and / or can be programmed to perform all or part of the operations described with respect to the various embodiments.

[0026] The term "mobile wireless device" as used herein refers to computing devices including any or all of the following: customer smartphones, store picker's mobile wireless devices, cellular telephones, portable computing devices, laptop computers, tablet computers, smartbooks, ultrabooks, PDAs, Internet-enabled multimedia cellular telephones, wearable devices (including smart watches, smart clothing, smart glasses, earbuds, headphones, smart wristbands), and similar electronic devices that include memory, wireless communication components, and programmable processors.

[0027] The term "user mobile device" is used to refer to a mobile wireless device that is specifically configured to support a user within a store, such as a store picker operation running within a store picker system according to various embodiments. The store picker wireless device may include a processor, memory, an electronic display, a wireless transceiver including a Bluetooth transceiver and a Wi-Fi transceiver, a barcode scanner, and other components for store picking.

[0028] As used herein, the term "store" when used with reference to a physical location refers to a wholesale, retail, or other building in which products are stored for sale and / or distribution. Stores may include, but are not limited to, warehouses, fulfillment centers, department stores, specialty stores, markets, supermarkets, hypermarkets, convenience stores, discount stores, superstores, and / or other storage facilities.

[0029] The term "product" as used herein refers to one or more items, articles, commodities or substances collected, refined, manufactured and / or assembled and maintained in a store or the like, such as products that may be identified on a shopping list and picked by a store picker.

[0030] The term "system on chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that includes multiple resources and / or processors integrated on a single substrate. A single SOC may include circuits for digital, analog, mixed signal, and radio frequency functions. A single SOC may also include any number of general and / or specialized processors (digital signal processors, modem processors, video processors, etc.), storage blocks (e.g., ROM, RAM, flash memory, etc.), and resources (e.g., timers, voltage regulators, oscillators, etc.). The SOC may also include software for controlling the integrated resources and processors and for controlling peripheral devices.

[0031] The term "system-in-package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computing units, cores and / or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SOCs that are coupled together via a high-speed communication circuit system and packaged together in close proximity (such as on a single motherboard or in a single computing device). The proximity of the SOCs facilitates high-speed communication and sharing of memory and resources.

[0032] Typically, the connection between the AP and the ESL is established before the ESL is associated with the AP (e.g., to perform a bootstrap operation), or the connection is established to perform synchronization or other operations. For example, when the AP needs to perform a general attribute (GATT) operation or a data transfer operation (OTS), the AP and the ESL can establish a connection (which may require some brief negotiation between the AP and the ESL) and transfer data. In some embodiments, the AP can broadcast periodic advertisement (PA) messages at substantially regular intervals. Such PA messages may include an operation code for accessing (e.g., synchronizing or associating with the AP) a bootstrap ESL, or may serve as a synchronization signal for use by the ESL.

[0033] When the boot, synchronization or other operations are completed, the AP may drop the connection and reallocate communication resources for communication with another ESL, and the previous ESL may enter a low power or sleep mode. For example, once data download is complete, the connection between the AP and the ESL may be disconnected (e.g., to release the allocated resources). In order to perform subsequent communication activities, a reconnection is required.

[0034] In some embodiments, the AP may transmit an AUX_CONNECT_REQ (ACRQ) message to the ESL, as provided in the Periodic Advertisement with Response (PAwR) specification, which is sometimes referred to as a "fast connect" mechanism for establishing an ACL communication link between the AP and the ESL. The fast connect reconnect mechanism includes a host controller interface (HCI) command for initiating a create connection request based on the PA queue. The controller entity may send an auxiliary connection request (ACRQ) message (e.g., an AUX_CONNECT_REQ Bluetooth message) in a sub-event slot of a periodic announcement queue, in which an auxiliary synchronization indication (AUX_SYNC_IND) message is periodically sent. The AUX_SYNC_IND message can be used as a synchronization message between the AP and the ESL.

[0035] In operation, an AP may communicate with hundreds or thousands of ESLs. An AP may support a limited number of connections to an ESL. Typically, an AP may establish connections in a serial manner, creating a new connection after an existing connection is completed. However, various factors may cause a time gap between two connections (e.g., with an ESL). First, after receiving an ACRQ from an AP, an ESL will typically transition from a low-power operating mode or a sleep operating mode to a full-power operating mode or a "wake-up" operating mode. During the time required for the ESL to transition from a low-power operating mode to a full-power mode, the ESL may not be able or ready to receive communications from the AP. (As a non-limiting example, such an ESL operating mode transition may require up to 60 milliseconds). Second, an ESL (or ESL group) may not be available for synchronization with an AP at the start of each PA sub-event. For example, an ESL may be arranged (e.g., organized or associated) as a group, and each group may have its own PA. The communication resources released at a particular point in time may be the only available resources of a PA associated with one or more ESLs in the group. In some cases, after completing the first connection with the first ESL, the AP may wait two or more sub-event intervals until the second ESL is available to receive the transmission of the ACRQ. Third, communication delays may be caused by signal interference, which may prevent the ESL from receiving the ACRQ and / or may prevent the AP from receiving a response from the ESL, such as an auxiliary (AUX) connection response (ACRP) message.

[0036] The presence of a time gap between two connections to an ESL may delay data transfer to or from the ESL. In systems where hundreds or even thousands of ESLs are deployed, the time gaps between connections may aggregate to cause significant delays in data transfer and other operations. However, conventional attempts to reduce the gaps between ESL connections tend to degrade the operation of the ESL or are impractical for actual operation. For example, configuring the ESL to always operate in full-power mode can reduce (or eliminate) the transition time from a low-power sleep mode, but may quickly consume the limited power of the ESL. As another example, while deploying a very large number of ESLs can provide ESLs that are available at each PA sub-event time, increasing the number of ESLs increases the organizational complexity required to provide well-distributed sub-event groups (e.g., a grouping strategy for organizing the ESLs into groups).

[0037] Various embodiments include a method for managing the timing of an ESL communication link and an AP configured to implement the method. In various embodiments, the AP may be configured to predict when a communication operation during a first connection with an ESL will be completed, and perform operations to reduce the time gap between the first connection and the subsequent second connection with the second ESL. In some embodiments, the AP may determine the completion time of the first connection based on a 12.5 millisecond frame. In various embodiments, the scheduling logic of the AP may be configured to reduce the time gap between ESL communication links (such as ACL communication links) by initiating a process of establishing a communication link with the second ESL before the communication link with the first ESL is terminated. In various embodiments, when the AP is performing a communication operation with the first ESL using a first connection during the first connection duration, the AP may send a connection request to the second ESL before completing the communication operation with the first ESL during the first connection duration. Then, the AP may establish a second connection with the second ESL based on the connection request transmitted to the second ESL. In some embodiments, the AP may establish a second connection with the second ESL in a second connection duration, which begins at the end of the first connection duration or substantially at the end of the first connection duration (such as a short time after the end of the first connection duration), for example, within a frame or frame duration (for example, each frame has a duration of 12.5ms) or within a duration of several milliseconds (for example, within 12.5ms). The phrase "at the end of the first connection" or "at the end of the first connection" includes "substantially at the end of the first connection" in its meaning. In some embodiments, the AP may send a connection request to the second ESL in a sub-event during the first connection duration, in which the second ESL receives a synchronization signal from the AP.

[0038] In some embodiments, the AP may send a connection request to the second ESL at an offset time before the first connection is completed (i.e., a time offset from the first connection completion time). In some embodiments, the offset time may be a time interval based on the wake-up time period of the second ESL. As used herein, a "wake-up time period" refers to the amount of time required for the second ESL to be able to receive communications from the AP (as an example, the amount of time required for the second ESL to switch operating modes so as to be able to communicate with the AP). In such embodiments, the AP may determine the time when the first connection duration ends. The AP may determine a connection request sending time before the end of the first connection based on the offset time, so that the connection request sending time is during the first connection duration. The AP may send a connection request at the determined connection request sending time during the first connection duration.

[0039] In some embodiments, the AP may receive a connection response from the second ESL during the first connection duration based on a connection request transmitted to the second ESL. In such embodiments, the AP may establish a second connection with the second ESL at the end of the first connection duration based on a connection response received from the second ESL.

[0040] In some embodiments, if the AP does not receive a connection response from the ESL, the AP may send a connection request to another ESL (third ESL) before completing the first connection duration with the first ESL. For example, the second ESL may not receive a connection request from the AP, or the AP may not receive a response or confirmation from the second ESL. However, the AP may have one or more opportunities to send a connection request to another ESL (third ESL) because the AP sent the initial connection request early enough before the end of the first connection duration. The AP may establish a second connection with the third ESL based on a connection response received from the ESL in response to a connection request sent to the third ESL.

[0041] In various embodiments, the AP may send data to the second ESL at the beginning of the second connection duration. In some embodiments, the AP may send data to the second ESL at the end of the wake-up period of the second ESL. In some embodiments, the wake-up period of the ESL may end before the end of the first connection duration. In such embodiments, the AP may send the first data to the second ESL before the end of the first connection duration, and may send the second data to the second ESL in the second connection duration, which begins at the end of the first connection duration. In some embodiments, the AP may send the first data to the second ESL at the end of the wake-up period of the second ESL, where the wake-up period ends before the end of the first connection duration.

[0042] Various embodiments improve the operation of ESLs, APs, and ESL systems by enabling the AP to manage the establishment of connections (communication links) with ESLs to the time gaps between connections established with different ESLs. Various embodiments improve the operation of APs, ESLs, and ESL systems by reducing the time gaps between ACL communication links, thereby increasing the overall data throughput from APs to ESLs that can be achieved in the ESL system.

[0043] Figure 1A 1 is a block diagram of components of an ESL system 100 suitable for implementing various embodiments. System elements deployable within a given store 10 may include multiple ESLs 110 deployed on shelves 50 configured to communicate with a plurality of APs 130 connected to a store management entity server 150.

[0044] The ESL 110 may be positioned on a shelf 50 associated with a product (labeled a, b, c, d, e, f, g, h, i, j, k, and m). Each ESL 110 may include a display 115 on which a product name, product code, price, inventory information, barcode, etc. are presented. Some ESLs 110 may also include an illuminator 117, such as a light emitting diode (LED) or other visible light generating devices configured to illuminate to attract the attention of a store picker and / or other customers, as described herein. In some embodiments, some ESLs 110 may include a speaker or vibration generating device for generating visual, auditory, and / or tactile notifications. Each ESL 110 may include a beacon transmitter and is configured to detect adjacent ESLs such as via a Bluetooth signal or a Bluetooth low energy (BLE) signal. In some embodiments, some ESLs 110 may include one or more sensors, such as, but not limited to, a proximity sensor for detecting when an individual is standing near the ESL 110, a microphone for monitoring ambient noise and receiving voice from a customer or a store picker, etc. In some embodiments, the various ESLs deployed in the ESL system 100 can be configured and / or equipped with different capabilities or the same capabilities.

[0045] The ESL 110 may be configured to receive communications from the store management entity server 150, such as via a wireless communication link 112 that may be relayed via the AP 130. Thus, the store management entity server 150 may configure each ESL 110 with product information to be displayed and a duty cycle regarding when the ESL should be activated to receive signals and transmit wireless beacons. The store management entity server 150 may control the periodicity of the ESL duty cycle so as to minimize battery consumption / usage, thereby extending operating life, while ensuring that the ESL is responsive to customers and store pickers, such as by increasing the duty cycle when an individual is near the ESL (e.g., close enough to see and / or read the display of the ESL). Further, the management entity server 150 may configure the ESL 110 to generate appropriate indications (e.g., visual, audible, and / or tactile indications) at appropriate times (such as when the ESL is associated with a product on a shopping list of a user that appears nearby (e.g., within a predetermined distance). In various embodiments, the store management entity server 150 may be located within or near the store, or remotely located and accessed via the communication network 154 .

[0046] ESLs 110 may be configured to exchange wireless communications (such as wireless beacons or tones) with each other via wireless link 112 for various purposes, including in particular for determining the relative and actual location of the ESLs on shelf 50 and relative to each other, as described herein.

[0047] In some embodiments, the ESL system 100 deployed in the store 10 may also include other mechanisms for determining the precise location of the ESL and individual store pickers or customers. For example, in some embodiments, the system may include an ultrasonic transmitter 134, which may be configured to periodically or intermittently allow (for example) ultrasonic tones that can be received by a microphone on each ESL 110 for the purpose of determining the relative position of each ESL via a sound ranging process. As another example, in some embodiments, the system may include an infrared transmitter, which may be configured to emit an infrared beam that can be received by a photodetector on each ESL for the purpose of determining relative position via IR ranging technology. As another example, the system may include a camera 132 coupled to a store management entity server 150, which may be positioned to provide imaging of the ESL 110 and individuals (e.g., store pickers, customers, and / or other individuals). The store management entity server 150 may use image data received from such cameras 132 to determine the location of each ESL and individuals. In some embodiments, the camera 132 may be positioned on the shelf to view the product and individuals near the product. In some embodiments, the ESL 110 may include a camera and be configured to send images to the store management entity server 150 via a wireless link 112 with the AP 130 .

[0048] The store management entity server 150 may be configured with a detailed map of product locations within the store, referred to as a floor plan, which is correlated or calibrated to an indoor positioning system (such as supported by the ESL 110 as described). The store management entity server 150 may also contain information from an inventory system that keeps track of product inventory to avoid sending store pickers to locations where out-of-stock products are located.

[0049] The AP 130 may be configured to communicate with the ESL 110 to provide communication with the store management entity server 150. In some embodiments, the AP may be configured with a camera or coupled to a camera to provide visual images of the ESL as well as customers and store pickers, thereby providing more accurate location information as described herein. The AP 130 may also be configured with antenna arrays that are capable of determining the angle of arrival (AOA) of wireless communications, thereby providing further positioning information to the store management entity server 150.

[0050] The user mobile device 120 can be any form of mobile device, not just a smart phone as illustrated. For example, in addition to being a personal mobile device, the mobile device 120 that can be used in the system 100 can also include a smart watch, a body camera, augmented reality glasses (e.g., smart glasses), and facility-specific or enterprise-specific handheld devices configured specifically for store pickers.

[0051] Figure 1B 1 illustrates further details of communication links that may be utilized in the ESL system 100 according to some embodiments. Figure 1A and Figure 1B , ESL 110 may be configured to communicate with AP 130 via wireless link 112a (such as Bluetooth), and exchange wireless signals with other ESL 110 via wireless link 112b. For example, ESL 110 may send certain BLE signals 112a, such as ESL advertisements configured to be received by nearby AP 130 and used to guide ESL 110. In addition, ESL 110 on the opposite side of the aisle (i.e., the interval between two shelves 50) may send certain BLE signals 112b, which are configured to be received by nearby ESL 110 and used for the purpose of determining the relative position of the corresponding equipment. BLE signals 112a, 112b may be broadcast at a set or selected power level, so that the interval distance can be estimated based on the measured received signal strength indicator (RSSI) of the signal received by other ESL 110. AP 130 may be coupled to store management entity server 150 via wired connection 132.

[0052] The user mobile device 120, which may be held, carried, or otherwise associated with a store picker or customer, may receive beacon signals from the ESL, such as through a wireless link, and communicate with the store management entity server 150 via wireless communications, such as BLE, Wi-Fi, or various types of cellular communications. The AP 130 may be configured to communicate with the user mobile device 120 to provide communications with the store management entity server 150. The AP 130 may also provide the user mobile device 120 with access to an external communication network, such as a communication network 154, to enable the customer to access a remote server 156, such as to compare stores, research products, and otherwise provide Internet access support.

[0053] The user mobile device 120 used by the store picker may receive beacon signals (e.g., BT or BLE) from each ESL 110, but may also communicate received beacon information (e.g., identity code and RSSI information) directly to the store management entity server 150 via a separate communication 122. Such separate communication 122 may be via Wi-Fi communication (e.g., via the AP 130) or via a cellular data network (e.g., a fifth generation (5G) cellular network).

[0054] Figure 2is a component block diagram illustrating a non-limiting example of a computing and wireless modem system 200 suitable for use in a computing device such as an AP or some ESL for implementing any of the various embodiments. The various embodiments may be implemented on a number of single-processor and multi-processor computer systems, including system-on-chip (SOC) or system-in-package (SIP).

[0055] Reference Figures 1A to 2 , the illustrated example computing system 200 (which may be a SIP in some embodiments) includes two SOCs 202, 204 coupled to a clock 206, a voltage regulator 208, and a radio module 266, which is configured to transmit and receive wireless communications (including BLE messages) via an antenna (not shown and an inertial measurement unit) (IMU) 268. When the computing system 200 is used in an Ap or ESL, the radio module 266 may be configured to broadcast a BLE beacon as described herein. In some specific implementations, the first SOC 202 may operate as a central processing unit (CPU) of a user's mobile device, which executes these instructions by performing arithmetic, logic, control, and input / output (I / O) operations specified by the instructions of the software application. In some specific implementations, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing large-capacity, high-speed (such as 5Gbps, etc.) or very high-frequency short wavelength (such as 38GHz millimeter wave spectrum, etc.) communications.

[0056] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor 216, one or more coprocessors 218 (such as a vector coprocessor) connected to one or more of these processors, memory 220, custom circuits 222, system components and resources 224, interconnects / bus modules 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, multiple millimeter wave transceivers 256, memory 258, and various additional processors 260, such as an application processor, a packet processor, etc.

[0057] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of other processors / cores. For example, the first SOC 202 may include a processor that executes a first type of operating system (such as FreeBSD, LINUX, OS X, etc.) and a processor that executes a second type of operating system (such as MICROSOFT WINDOWS). In addition, any or all of the processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (such as a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0058] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuits for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations, such as decoding data packets and processing encoded audio and video signals for presentation in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components used to support processors and software clients running on user mobile devices. The system components and resources 224 or custom circuits 222 may also include circuits for docking with peripheral devices (such as cameras, electronic displays, wireless communication devices, external memory chips, etc.).

[0059] The first SOC 202 and the second SOC 204 may communicate via an interconnect / bus module 250. The various processors 210, 212, 214, 216, 218, 252, 260 may be interconnected to one or more memory elements 220, system components and resources 224, and custom circuits 222, and a thermal management unit 232 via an interconnect / bus module 226. Similarly, the processor 252 may be interconnected to a power management unit 254, a millimeter wave transceiver 256, a memory 258, and various additional processors 260 via an interconnect / bus module 264. The interconnect / bus modules 226, 250, 264 may include an array of reconfigurable logic gates or implement a bus architecture (such as CoreConnect, AMBA, etc.). Communications may be provided by advanced interconnects, such as a high-performance network on chip (NoC).

[0060] The first SOC 202 or the second SOC 204 may also include an input / output module (not illustrated) for communicating with resources external to the SOC, such as a clock 206 and a voltage regulator 208. Resources external to the SOC, such as a clock 206 and a voltage regulator 208, may be shared by two or more of the internal SOC processors / cores.

[0061] Figure 3A is a timeline illustrating aspects of a method 300a for managing the timing of establishing a connection with an ESL according to some embodiments. Figures 1A to 3A , the AP may use the first connection 310 to perform communication operations with the first ESL during the first connection duration 314. For example, Figure 3A , the first connection duration 310 illustrated in 5 lasts from sub-event 80. The AP may send data 304a, 304b, 304c, 304d, 304e, and 304f to the first ESL during different sub-events. For example, the AP may send data 304a during sub-event 5, data 304b during sub-event 6, data 304c during sub-event 77, data 304d during sub-event 78, data 304e during sub-event 79, and data 304f during sub-event 80. In some embodiments, the increment between data 304a and 304b and between other adjacent data transmissions (such as between 304c and 304d, etc.) may be substantially equal to the group length. In various embodiments, a "group" is a logical concept attached to or associated with a sub-frame. In some embodiments, there may be 128*12.5ms in a 1.6s frame, which may cover 128 groups. An ESL may belong to (be associated with) at least one group. In some embodiments, an ESL may "wake up" (ie, provide power to RF components and / or circuits) for the group with which the ESL is associated and for an associated time period.

[0062] In some embodiments, after the AP establishes a first connection 310 with a first ESL (e.g., starting at sub-event 5) and before the connection with the first ESL 310 is completed, the AP may send a connection request (ACRQ) to one or more second ESLs during the first connection duration. If the AP does not receive an acknowledgment (e.g., ACRP) from the ESL, the AP may select another ESL and send an ACRQ to the selected next ESL.

[0063] For example, the AP may send ACRQ 302a to ESL 2 in sub-event 50. If the AP does not receive an acknowledgment from ESL 2 before the deadline, the AP may select ESL 3 in sub-event 71 and send ACRQ 302b to ESL 3. If the AP does not receive an acknowledgment from ESL 3 before the deadline, the AP may select ESL 4 in sub-event 72 and send ACRQ 302c to ESL 4. Figure 3A In the example illustrated in , the AP may select a second ESL candidate and send an ACRQ to the selected ESL candidate in any sub-event from sub-event 7 to sub-event 72. In some embodiments, the AP may send one or more ACRQs 302a, 302b, 302c, etc. during sub-events in which the AP may otherwise send periodic advertisements for synchronization with one or more other ESLs.

[0064] In response to receiving a response or confirmation (e.g., ACRP) from the ESL, the AP may establish a connection with the ESL that has transmitted the response for the second ESL 312. In some embodiments, the AP may establish a connection with the second ESL 312 at the end of the first connection 310. In some embodiments, the AP may establish the second connection 312 for a second connection duration 316 that begins at the end of (or substantially close to or just after) the first connection duration 314. For example, the AP may establish the second connection 312 within a frame duration (and / or within a 12.5 millisecond duration) between the end of data transmission 304f (in sub-event 80) and the start of data transmission 304g (in sub-event 81). Configuring the AP to send ACRQs 302a to 302c to the second ESL during the first connection duration 314 can reduce the time gap between the first connection 310 with the first ESL in the first connection duration 314 and the second connection 312 with the second ESL in the second connection duration 316.

[0065] In some implementations, during the second connection duration 316 , the AP may transmit a connection request 306 (eg, an ACRQ) to the third ESL to initiate a process for establishing a third connection with the third ESL at the end of the second connection duration 316 .

[0066] Figure 3B is a timeline illustrating aspects of a method 300b for managing the timing of establishing a connection with an ESL according to some embodiments. Figures 1A to 3B , the AP may send data to the second ESL at the beginning of the second connection duration 312. In some embodiments, the AP may send data to the second ESL at the end of the wake-up period of the second ESL.

[0067] In some embodiments, the AP may determine an offset time 320. In some embodiments, the offset time 320 may represent the amount of time required for the ESL to be ready to receive data from the AP. For example, the offset time 320 may be a time interval based on the wake-up period required for the second ESL to transition from a sleep mode of operation or a low-power mode of operation in which it is currently operating to a full-power mode of operation in which the second ESL can communicate with the AP. In some embodiments, the AP may determine the offset time period as WinOffset=Z*12.5ms+1.25ms, where WinOffset represents the offset time, 12.5ms represents the frame duration during the connection duration, Z represents the number of frames, and 1.25ms represents 10 divisions of a subframe. For example, if the ESL requires 5 frames to be ready to receive data from the AP (i.e., Z=5), then WinOffset=5 frames*12.3ms+1.25ms=63.75ms. In this example, WinOffset will accommodate the second ESL transition time of approximately 60 milliseconds. In this example, the AP sends a connection request 302 (eg, an ACRQ) to the second ESL during sub-event 72 , and the AP receives a connection response from the second ESL during sub-event 72 .

[0068] In some embodiments, the AP may transmit data to the second ESL at the end of the offset time 320. In some embodiments, the end of the offset time 320 may represent the first opportunity for the second ESL to be ready to receive data from the AP (e.g., after completing the operating state transition from the low power mode to the full power mode). In this way, the AP may delay transmitting data to the second ESL, or wait to transmit data to the second ESL until the time when the second ESL is able to receive data. During the offset time 320, the AP may maintain a first connection 310 with the first ESL. Since the second ESL completes the operating mode transition to the full power mode during the first connection duration 314, the AP may establish a second connection 312 with the second ESL in a second connection duration 316, which begins at or shortly after the end of the first connection duration 314. In some embodiments, the end of the first connection duration 314 may be the time when the AP ends or completes communication with the first ESL.

[0069] In some embodiments, the AP may configure the offset time 320 to end at the beginning of the second connection duration 316, at which the second connection 312 with the second ESL begins. In some embodiments, the AP may send a connection request to the second ESL at the beginning of the offset time 320. Sending the connection request to the second ESL at the beginning of the offset time 320 may enable the second ESL to complete the transition to a full-power operating mode before or at the end of the first connection duration 314, so that the AP can establish the second connection 312 with the second ESL at the beginning of the second interval 316, which may begin at the end of the first connection duration 314. In this way, the AP can manage communications with the second ESL so that the AP can establish the second connection "in time" at the end of the first connection duration 314 when the first connection 310 with the first ESL is completed.

[0070] Figure 3C is a timeline illustrating aspects of a method 300c for managing the timing of establishing a communication link with an ESL according to various embodiments. Figures 1A to 3C In some cases, the AP may not be able to establish a second connection with the second ESL at the time originally planned by the AP because the communication with the first ESL (i.e., the connection with the first ESL) was not completed at the time expected or planned by the AP, which may be due to less than ideal RF communication conditions causing the communication to take longer than originally planned. As another example, the AP may not be able to receive a connection response after transmitting only one connection request. For example, the AP and / or ESL may be deployed in an environment that is not conducive to clear RF communication, or the AP and / or ESL may encounter signal coexistence or interference from other signals (such as Wi-Fi signals).

[0071] For example, the first connection duration 314 of the first connection 310 with the first ESL may extend beyond the end of the offset time 320. If the AP operates in a poor RF environment, such as due to coexistence with other RF signals (e.g., Wi-Fi) or other RF noise, the AP may transmit multiple connection requests to the ESL before receiving a connection response, and the end time of the connection with the first ESL 310 may be later than the end of the offset time 320. In this case, the AP may transmit the first data 330a to the second ESL before the connection with the first ESL 310 is completed, and then the AP may delay transmitting the second data 330b until after the connection with the first ESL 310 is completed.

[0072] In some embodiments, the AP may send a connection request 302a (e.g., ACRQ) to the second ESL, and the AP may receive a connection response (e.g., ACRP) from the second ESL. In such embodiments, the AP may send first data 330a to the second ESL during the first connection duration 314 of the first connection 310 with the first ESL (if communication link resources are available). For example, the AP may send the first data 330a to the second ESL after the offset time 320 during the first data transmission period 322. The AP may then delay the transmission of the second data 330b until after the second connection duration 316 begins. In some embodiments, the AP may delay the transmission of the second data 330b by the second data delay period 324.

[0073] In some embodiments, in order to send the first data 330a to the second ESL, the AP may use communication resources and / or transmission opportunities that the AP could otherwise use to send to the first ESL. In such embodiments, after the first data transmission period 322, the AP may resume sending data to the first ESL in the remainder of the first connection duration 314. The AP may send the second data 330b at the beginning of the second connection duration 316. In some embodiments, the AP may adopt a delay mechanism, such as a supervision timeout or another suitable mechanism that enables the AP to delay transmitting the second data 330b to the second ESL. In some embodiments, the delay mechanism may enable the AP to delay transmitting the second data 330b, 330c by up to a threshold duration (e.g., up to 10 seconds). In this way, the AP can manage the timing of communication with the ESL in a suboptimal RF environment.

[0074] Figure 4 is a process flow diagram of a method 400 for managing the timing of establishing a communication link with an ESL according to various embodiments. Figures 1A to 4 , the components for performing each of the operations of method 400 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 702 and / or 704) and / or a transceiver (e.g., 717) of an AP (e.g., 130, 306), etc.

[0075] In block 402, the processor may perform a communication operation with a first electronic shelf label (ESL) using a first connection during a first connection duration. For example, the processor may perform a communication operation with the first ESL 310 during the first connection duration 314.

[0076] In block 404, the processor may send a connection request to the second ESL before completing the communication operation with the first ESL during the first connection duration. For example, the processor may transmit one or more communication requests 302 to the second ESL during the first connection duration 314. In some embodiments, the processor may send the connection request to the second ESL in a sub-event during the first connection duration in which the second ESL receives a synchronization signal from the AP. In some embodiments, the processor may send the connection request to the second ESL at an offset time before the first connection is completed, wherein the offset time is a time interval based on a wake-up period of the second ESL (e.g., at least as long as the wake-up period).

[0077] In block 406, the processor may establish a second connection with the second ESL based on the connection request transmitted to the second ESL. In some embodiments, the processor may establish the second connection with the second ESL in a second connection duration that begins at the end of the first connection duration. For example, the processor may establish the second connection 312 with the second ESL in a second connection duration 316 that begins at the end of the first connection duration 314.

[0078] Figure 5A is a process flow diagram of operations 500a that may be performed as part of method 400 of managing the timing of establishing a communication link with an ESL according to various embodiments. Figures 1A to 5A , the components for performing each operation in operation 500a may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 702 and / or 704) and / or a transceiver (e.g., 717) of an AP (e.g., 130, 306), etc.

[0079] After performing the operations of block 404 of method 400 as described, the processor may receive a connection response from the second ESL during the first connection duration based on the connection request transmitted to the second ESL in block 502. For example, the processor may receive a connection response from the second ESL (ESL B) during the first connection duration 314 based on one or more connection requests 302 transmitted by the AP to the second ESL.

[0080] In block 504, the processor may establish a second connection with the second ESL at the end of the first connection duration based on a connection response received from the second ESL. For example, the processor may establish the second connection 312 with the second ESL based on a connection response received by the AP from the second ESL.

[0081] Figure 5Bis a process flow diagram of operation 500b that may be performed as part of method 400 of managing the timing of establishing a communication link with an ESL according to various embodiments. Figures 1A to 5B , the components for performing each operation in operation 500b may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 702, and / or 704) and / or a transceiver (e.g., 717) of an AP (e.g., 130, 306), etc.

[0082] After performing the operations of block 404 of method 400 as described, the processor may, in response to not receiving a connection response from the second ESL, send a connection request to a third ESL before the first connection duration with the first ESL is completed in block 510. For example, the processor may send a second connection request 302b, a third connection request 302c, etc. to another ESL (third ESL) in response to not receiving a connection response from the second ESL.

[0083] In block 512, the processor may establish a second connection with the third ESL based on a connection response received from the third ESL in response to a connection request sent to the second ESL. For example, based on a connection response received from the third ESL in response to the second connection request 302b (or the third connection request 302c, etc.), the processor may establish the second connection 312 with the third ESL at the beginning of the second connection duration 316.

[0084] Figure 5C is a process flow diagram of operations 500c that may be performed as part of method 400 of managing the timing of establishing a communication link with an ESL according to various embodiments. Figures 1A to 5C , the components for performing each operation in operation 500c may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 702, and / or 704) and / or a transceiver (e.g., 717) of an AP (e.g., 130, 306), etc.

[0085] After performing the operations of block 406 of method 400 as described, the processor may send data to the second ESL at the beginning of the second connection duration in block 520. For example, the processor may send data 304g to the second ESL at the beginning of the second connection duration 316.

[0086] Figure 5D is a process flow diagram of operations 500d that may be performed as part of method 400 of managing the timing of establishing a communication link with an ESL according to various embodiments. FIG. 1A to FIG. 5D, the components for performing each operation in operation 500d may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 702, and / or 704) and / or a transceiver (e.g., 717) of an AP (e.g., 130, 306), etc.

[0087] After performing the operations of block 406 of method 400 as described, the processor may send data to the second ESL at the end of the wake-up period of the second ESL in block 522. For example, the processor may begin sending data 304g, 304h to the second ESL at the end of offset time 320. As noted above, in some embodiments, the end of offset time 320 may also be the beginning of the second connection duration 316.

[0088] Figure 5E is a process flow diagram of operations 500e that may be performed as part of method 400 of managing the timing of establishing a communication link with an ESL according to various embodiments. Figures 1A to 5E , the components for performing each operation in operation 500e may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 702, and / or 704) and / or a transceiver (e.g., 717) of an AP (e.g., 130, 306), etc.

[0089] After performing the operations of block 404 of method 400 as described, in block 530, the processor may send the first data to the second ESL before the first connection duration ends. In some embodiments, the processor may send the first data to the second ESL during a wake-up period of the second ESL before the first connection duration ends. For example, the processor may send the first data 330a to the second ESL before the first connection duration 314 ends.

[0090] In block 532, the processor may send second data to the second ESL in a second connection duration that begins at the end of the first connection duration. For example, the processor may send second data 330b to the second ESL in a second connection duration 316 that may begin at the end of the first connection duration 314.

[0091] Figure 6 is a component block diagram of an example of an ESL 110 suitable for use in various embodiments. Figures 1A to 6, the ESL 110 may include a display 115 and an illuminator 117 (e.g., an LED or other type of visible indicator) coupled to a processor 602 configured with processor executable instructions configured to cause the processor to perform the operations of the various embodiments. The processor 602 may be coupled to a wireless transceiver 604, such as a BLE transceiver or a combination of a BLE and Wi-Fi transceiver, which is coupled to an antenna 606 for transmitting and receiving radio frequency (RF) signals as described herein. In various embodiments, the processor 602 may include a SOC (e.g., 202, 204). The ESL 110 may be powered by a battery 608, so that the display does not have to be connected to a wired power source. Alternatively, the ESL 110 may be powered by an external power source.

[0092] Figure 7 is a block diagram of components of AP 130 suitable for use in various embodiments. Figures 1A to 7 , the AP 130 may generally include processors 702, 704 coupled to volatile memory 706 and optionally large-capacity non-volatile memory 708. The AP 130 may also include peripheral memory access devices (such as flash drives) coupled to the processors 702, 704. The AP 130 may also include a network access port 714 (or interface) coupled to the processors 702, 704 for establishing a data connection with a network (such as the Internet and / or a local area network coupled to other system computers and servers). The AP 130 may include additional access ports such as USB, Firewire, Thunderbolt, etc. for coupling to peripherals, external memory or other devices. The AP 130 may include one or more antennas 707 coupled to a transceiver 717 for transmitting (i.e., sending) and receiving electromagnetic radiation, which may be connected to a wireless communication link.

[0093] Figure 8 1 is a component block diagram of a store management entity server 150 suitable for various embodiments. Figures 1A to 8, the store management entity server 150 may typically include a processor 801 coupled to a volatile memory 802 and a large capacity non-volatile memory (such as a disk drive 803). The store management entity server 150 may also include a peripheral memory access device coupled to the processor 801, such as a floppy disk drive, a compact disc (CD) or a digital video disc (DVD) drive 806. The store management entity server 150 may also include a network access port 804 (or interface) coupled to the processor 801 for establishing a data connection with a network (such as the Internet and / or a local area network coupled to other system computers and servers). The store management entity server 150 may include one or more antennas 807 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless communication link. The store management entity server 150 may include additional access ports for coupling to peripheral devices, external memory or other devices, such as USB, Firewire, Thunderbolt, etc.

[0094] Fig. 9 is a component block diagram of a user mobile device 120 suitable for use as a user mobile device or consumer user equipment (UE) when configured with processor-executable instructions to perform the operations of various embodiments. Figures 1A to 9 , the user mobile device 120 may include a first SOC 202 (e.g., a SOC-CPU) coupled to a second SOC 204 (e.g., a 5G-capable SOC). The first SOC 202 and the second SOC 204 may be coupled to an internal memory 906, a display 915, and may be coupled to a speaker 914. Additionally, the user mobile device 120 may include an antenna 904 for transmitting and receiving electromagnetic radiation, which may be connected to a radio module 266 configured to support a wireless local area network data link (e.g., BLE, Wi-Fi, etc.) and / or a wireless wide area network (e.g., a cellular telephone network) coupled to one or more processors in the first SOC 202 and / or the second SOC 204. The user mobile device 120 typically also includes a menu selection button 920 for receiving user input.

[0095] The typical user mobile device 120 may also include an inertial measurement unit (IMU) 268, which includes a plurality of micro-electromechanical sensor (MEMS) elements configured to sense movement associated with acceleration and rotation of the device and provide this movement information to the first SOC 202. In addition, one or more of the processors in the first SOC 202 and the second SOC 204, the wireless transceiver 266 may include digital signal processor (DSP) circuitry (not separately shown).

[0096] In some embodiments, the user mobile device 120 can be used as a mobile AP to diagnose an ESL that has problems establishing communication with an AP or other fixed infrastructure. For example, the user mobile device 120 can be repurposed by a store management entity server by configuring the user mobile device 120 with an AP protocol so that the user mobile device 120 can be recognized by the ESL as an AP.

[0097] The processors of the ESL 110, the user mobile device 120, and the store management entity server 150 may be any programmable microprocessor, microcomputer, or one or more multi-processor chips that can be configured by software instructions (applications) to perform a variety of functions including the functions of the various embodiments described herein. In some user mobile devices, multiple processors may be provided (such as one processor dedicated to wireless communication functions within the SOC 204 and one processor dedicated to running other applications within the SOC 202). Typically, software applications may be stored in the memory 906, which are then accessed and loaded into the processor. The processor may include internal memory sufficient to store application software instructions.

[0098] The various embodiments illustrated and described are provided merely as examples of various features of the claims. However, the features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment, and may be used or combined with other embodiments shown and described. In addition, the claims are not intended to be limited to any one example embodiment. For example, one or more of the methods and operations 300a to 300c, 400, and 500a to 500e may replace or be combined with one or more of the methods and operations 300a to 300c, 400, and 500a to 500e.

[0099] Specific implementation examples are described in the following paragraphs. Although some of the specific implementation examples in the following specific implementation examples are described in terms of example methods, other example implementations may include: the example methods discussed in the following paragraphs implemented by an AP, the AP including a processor configured to perform the operations of these example methods; the example methods discussed in the following paragraphs implemented by an AP, the AP including components for performing the functions of these example methods; the example methods discussed in the following paragraphs implemented in a processor used in an AP, the processor being configured to perform the operations of the example methods; and the example methods discussed in the following paragraphs implemented in a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause the processor of the AP to perform the operations of these example methods.

[0100] Embodiment 1. A method executed by a processor of an access point (AP), the method comprising: performing a communication operation with a first electronic shelf label (ESL) using a first connection during a first connection duration; sending a connection request to a second ESL before completing the communication operation with the first ESL during the first connection duration; and establishing a second connection with the second ESL based on the connection request transmitted to the second ESL.

[0101] Embodiment 2. The method according to embodiment 1, wherein establishing the second connection with the second ESL based on the connection request transmitted to the second ESL includes: establishing the second connection with the second ESL in a second connection duration, and the second connection duration starts when the first connection duration ends.

[0102] Embodiment 3. A method according to any one of Embodiments 1 and 2, wherein sending the connection request to the second ESL before completing the communication operation with the first ESL during the first connection duration includes: sending the connection request to the second ESL in a sub-event during the first connection duration, in which the second ESL receives a synchronization signal from the AP.

[0103] Embodiment 4. A method according to any one of embodiments 1 to 3, wherein sending the connection request to the second ESL before completing the first connection with the first ESL includes: sending the connection request to the second ESL at an offset time before the first connection is completed, wherein the offset time includes a time interval based on a wake-up time period of the second ESL.

[0104] Embodiment 5. A method according to any one of Embodiments 1 to 4, wherein establishing the second connection with the second ESL based on the connection request transmitted to the second ESL includes: receiving a connection response from the second ESL during the first connection duration based on the connection request transmitted to the second ESL; and establishing the second connection with the second ESL at the end of the first connection duration based on the connection response received from the second ESL.

[0105] Embodiment 6. According to the method described in any one of Embodiments 1 to 5, the method further includes: sending a connection request to a third ESL before the first connection with the first ESL is completed in response to not receiving a connection response from the second ESL; and establishing the second connection with the third ESL based on a connection response received from the third ESL in response to the connection request sent to the third ESL.

[0106] Embodiment 7. The method according to any one of embodiments 1 to 6 further comprises: sending data to the second ESL at the beginning of the second connection duration.

[0107] Embodiment 8. The method according to any one of embodiments 1 to 7 further comprises: sending data to the second ESL at the end of the wake-up period of the second ESL.

[0108] Embodiment 9. A method according to any one of Embodiments 1 to 8, wherein establishing the second connection with the second ESL based on the connection request transmitted to the second ESL includes: sending first data to the second ESL before the end of the first connection duration, and the method further includes: sending second data to the second ESL during a second connection duration, and the second connection duration starts when the first connection duration ends.

[0109] Embodiment 10. A method according to Embodiment 9, wherein sending the first data to the second ESL before the first connection duration ends comprises: sending the first data to the second ESL after a wake-up time period of the second ESL, the wake-up time period of the second ESL ending before the first connection duration ends.

[0110] Several different cellular and mobile communication services and standards are available or contemplated in the future, all of which may enable and benefit from various aspects. Such services and standards may include, for example, the Third Generation Partnership Project (3GPP), Long Term Evolution (LTE) system, third generation wireless mobile communication technology (3G), fourth generation wireless mobile communication technology (4G), fifth generation wireless mobile communication technology (5G), Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) system (e.g., cdmaOne, CDMA1020TM), EDGE, Advanced Mobile Phone System (AMPS), Digital AMPS (IS-136 / TDMA), Evolution Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Local Area Network (WLAN), Wi-Fi Protected Access I and II (WPA, WPA2), Integrated Digital Enhanced Network (iDEN), C-V2X, V2V, V2P, V2I and V2N, etc. For example, each of these technologies involves the transmission and reception of voice, data, signaling and / or content messages. It should be understood that any reference to terminology and / or technical details related to individual telecommunication standards or technologies is for illustrative purposes only and is not intended to limit the scope of the claims to a particular communication system or technology unless specifically recited in the claim language.

[0111] The foregoing method descriptions and process flow charts are provided only as illustrative examples, and are not intended to require or imply that the operations of the various embodiments must be performed in the order given. As will be appreciated by those skilled in the art, the order of operations in the foregoing embodiments may be performed in any order. Words such as "thereafter", "then", "next", etc. are not intended to limit the order of operations; these words are used to guide the reader through the description of the method. In addition, any reference to a claim element in the singular form (e.g., a reference using the article "one", "an", or "said") should not be interpreted as limiting the element to the singular.

[0112] The various exemplary logic blocks, modules, components, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits, and operations have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. The technician may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as departing from the scope of the claims.

[0113] The hardware for implementing the various exemplary logic components, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or executed with a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. Although a general purpose processor may be a microprocessor, in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver smart objects, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuits specific to a given function.

[0114] In one or more embodiments, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored as one or more instructions or codes on a non-transient computer-readable storage medium or a non-transient processor-readable storage medium. The operation of the method or algorithm disclosed herein can be implemented in a processor-executable software module or a processor-executable instruction, which can reside on a non-transient computer-readable or processor-readable storage medium. A non-transient computer-readable or processor-readable storage medium can be any storage medium that can be accessed by a computer or a processor. By way of example and without limitation, such non-transient computer-readable or processor-readable storage media can include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage smart objects, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. Disks and optical disks as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and blue discs, wherein disks generally reproduce data magnetically, and optical discs reproduce data optically with lasers. The above combinations are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a non-transitory processor-readable storage medium and / or computer-readable storage medium, which may be incorporated into a computer program product.

[0115] The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but should be accorded the broadest scope consistent with the following claims and the principles and novel features disclosed herein.

Claims

1. A method executed by a processor of an access point (AP), the method include: performing a communication operation with a first electronic shelf label (ESL) using the first connection during a first connection duration; sending a connection request to a second ESL before completing the communication operation with the first ESL during the first connection duration; as well as A second connection is established with the second ESL based on the connection request transmitted to the second ESL.

2. The method of claim 1 , wherein the second connection is established with the second ESL based on the connection request transmitted to the second ESL include: The second connection is established with the second ESL in a second connection duration, and the second connection duration starts when the first connection duration ends.

3. The method of claim 1 , wherein the connection request is sent to the second ESL before the communication operation with the first ESL is completed during the first connection duration. include: The connection request is sent to the second ESL in a sub-event during the first connection duration, during which the second ESL receives a synchronization signal from the AP.

4. The method of claim 1 , wherein the connection request is sent to the second ESL before the first connection duration with the first ESL is completed. include: The connection request is sent to the second ESL at an offset time before the first connection is completed, wherein the offset time includes a time interval based on a wake-up period of the second ESL.

5. The method of claim 1 , wherein the second connection is established with the second ESL based on the connection request transmitted to the second ESL include: receiving a connection response from the second ESL during the first connection duration based on the connection request transmitted to the second ESL; as well as The second connection is established with the second ESL at the end of the first connection duration based on the connection response received from the second ESL.

6. The method according to claim 1, further comprising: include: sending a connection request to a third ESL before the first connection duration with the first ESL is completed in response to not receiving a connection response from the second ESL; as well as The second connection is established with the third ESL based on a connection response received from the third ESL in response to the connection request sent to the third ESL.

7. The method according to claim 1, further comprising: include: Data is sent to the second ESL at the beginning of a second connection duration.

8. The method according to claim 1, further comprising: include: Data is sent to the second ESL at the end of the wake-up period of the second ESL.

9. The method of claim 1, wherein the second connection is established with the second ESL based on the connection request transmitted to the second ESL include: before the first connection duration ends, sending first data to the second ESL, The method also includes sending second data to the second ESL in a second connection duration, the second connection duration starting when the first connection duration ends.

10. The method according to claim 9, wherein the first data is sent to the second ESL before the first connection duration ends. include: The first data is sent to the second ESL after a wake-up period of the second ESL, the wake-up period of the second ESL ending before the first connection duration ends.

11. An access point (AP), wherein the access point (AP) include: Transceiver; as well as a processor coupled to the transceiver and comprising firmware (FW), the processor being configured to: performing a communication operation with a first electronic shelf label (ESL) using the first connection during a first connection duration; sending a connection request to a second ESL before completing the communication operation with the first ESL during the first connection duration; as well as A second connection is established with the second ESL based on the connection request transmitted to the second ESL.

12. The AP of claim 11, wherein the processor is further configured to establish the second connection with the second ESL in a second connection duration, the second connection duration starting when the first connection duration ends.

13. The AP of claim 11, wherein the processor is further configured to: send the connection request to the second ESL in a sub-event during the first connection duration, in which sub-event the second ESL receives a synchronization signal from the AP.

14. The AP of claim 11, wherein the processor is further configured to: send the connection request to the second ESL at an offset time before the first connection is completed, wherein the offset time comprises a time interval based on a wake-up period of the second ESL.

15. The AP of claim 11, wherein the processor is further configured to: receiving a connection response from the second ESL during the first connection duration based on the connection request transmitted to the second ESL; and The second connection is established with the second ESL at the end of the first connection duration based on the connection response received from the second ESL.

16. The AP of claim 11, wherein the processor is further configured to: sending a connection request to a third ESL before the first connection duration with the first ESL is completed in response to not receiving a connection response from the second ESL; and The second connection is established with the third ESL based on a connection response received from the third ESL in response to the connection request sent to the third ESL.

17. The AP of claim 11, wherein the processor is further configured to send data to the second ESL at the beginning of a second connection duration.

18. The AP of claim 11, wherein the processor is further configured to send data to the second ESL at the end of a wake-up period of the second ESL.

19. The AP of claim 11, wherein the processor is further configured to: Sending first data to the second ESL before the first connection duration ends; and Second data is sent to the second ESL in a second connection duration, and the second connection duration starts when the first connection duration ends.

20. The AP of claim 19, wherein the processor is further configured to: send the first data to the second ESL after a wake-up period of the second ESL, the wake-up period of the second ESL ending before the first connection duration ends.

21. An access point (AP), wherein the access point (AP) include: means for performing a communication operation with a first electronic shelf label (ESL) using the first connection during a first connection duration; means for sending a connection request to a second ESL prior to completing said communication operation with said first ESL during said first connection duration; as well as Means for establishing a second connection with the second ESL based on the connection request transmitted to the second ESL.

22. The AP of claim 21, wherein the means for establishing the second connection with the second ESL based on the connection request transmitted to the second ESL comprises means for establishing the second connection with the second ESL in a second connection duration, the second connection duration starting at the end of the first connection duration.

23. The AP according to claim 21, wherein the component for sending the connection request to the second ESL before completing the communication operation with the first ESL during the first connection duration includes a component for sending the connection request to the second ESL in a sub-event during the first connection duration, in which the second ESL receives a synchronization signal from the AP.

24. The AP of claim 21, wherein the component for sending the connection request to the second ESL before completing the first connection with the first ESL includes a component for sending the connection request to the second ESL at an offset time before completion of the first connection, wherein the offset time includes a time interval based on a wake-up time period of the second ESL.

25. The AP of claim 21, wherein the means for establishing the second connection with the second ESL based on the connection request transmitted to the second ESL include: means for receiving a connection response from the second ESL during the first connection duration based on the connection request transmitted to the second ESL; as well as Means for establishing the second connection with the second ESL at the end of the first connection duration based on the connection response received from the second ESL.

26. The AP according to claim 21, wherein the AP further include: means for sending a connection request to a third ESL before the first connection duration with the first ESL is completed in response to not receiving a connection response from the second ESL; as well as Means for establishing the second connection with the third ESL based on a connection response received from the third ESL in response to the connection request sent to the third ESL.

27. The AP of claim 21, further comprising means for sending data to the second ESL at the beginning of a second connection duration.

28. The AP of claim 21, further comprising means for sending data to the second ESL at the end of an awake time period of the second ESL.

29. The AP according to claim 21, wherein the component for establishing the second connection with the second ESL based on the connection request transmitted to the second ESL includes a component for sending first data to the second ESL before the end of the first connection duration, and the AP also includes a component for sending second data to the second ESL during a second connection duration, and the second connection duration starts when the first connection duration ends.

30. A non-transitory processor-readable medium having stored thereon processor-executable instructions configured to cause a processing device in an access point (AP) to perform operations comprising: performing a communication operation with a first electronic shelf label (ESL) using the first connection during a first connection duration; sending a connection request to a second ESL before completing the communication operation with the first ESL during the first connection duration; as well as A second connection is established with the second ESL based on the connection request transmitted to the second ESL.