WO2024026714A1

WO2024026714A1 - Managing channel map update information in local wireless networks

Info

Publication number: WO2024026714A1
Application number: PCT/CN2022/109900
Authority: WO
Inventors: Zhuxian GU; Zaiyong CHEN; Nicolas Graube; Robin Heydon; Zhaoming YANG; Jiayin WU; Jie Zhang; Zhengjinyang JIANG; Xiuzhuo SHANG
Original assignee: Qualcomm Incorporated
Priority date: 2022-08-03
Filing date: 2022-08-03
Publication date: 2024-02-08

Abstract

Various aspects include methods for managing channel map update information that may be performed by access points (APs) and electronic shelf labels (ESLs). An AP may identify whether there will be a conflict between broadcasting channel map update information for reception by one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs, add channel map update information to the AUX connection request message in response to identifying that there will be a conflict, and broadcast the AUX connection request message including the channel map update information. An ESL may receive from an AP an AUX connection request message that includes channel map update information, identify from the AUX connection request message updated channel map information and channel timing information, and use the updated channel map information and channel timing information to communicate with the AP.

Description

Managing Channel Map Update Information In Local Wireless Networks

BACKGROUND

Electronic Shelf Labels (ESLs) are devices that can be used in supermarkets, supply stores, warehouses, and the like to monitor and control inventory tracking, product mapping, price change rollouts, and the customer experience generally. ESLs may communicate with a network access point (AP) using an energy-efficient, short range wireless communication protocol such as Bluetooth Low Energy. An AP may broadcast periodic advertisement (PA) messages at substantially regular intervals. Such PA messages may include operational code to access onboarding ESLs, or may serve as synchronization signals for use by ESLs. PA messages also may include Channel Map Update (CMU) information to provide ESLs an updated channel map with lower interference channels. The connection between the AP and ESLs is torn down once a data download is completed. When another data download is required, a reconnection is require, the AP may send an AUX_CONNECT_REQ (ACRQ) message to the ESL. However, there are circumstances in which the ACRQ message will occupy the time slot of other signals, such as an AUX_SYNC_IND which could contain CMU info if the AP is performing the CMU process.

SUMMARY

Various aspects of the present disclosure include methods, systems, and devices for managing channel map update information transmitted in wireless communication networks based on Bluetooth communication protocols. Various aspects may include identifying whether there will be a conflict between broadcasting channel map update information for reception by one or more electronic shelf labels (ESLs) and broadcasting an AUX connection request message (e.g., AUX_CONNECT_REQ) for reception by the one or more ESLs, adding channel map update information to the AUX connection request message in response to identifying the conflict between transmitting the channel map update information and transmitting the AUX connection request message, and broadcasting the AUX connection request message including the channel map update information.

In some aspects, identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs may include identifying whether there will be a conflict between broadcasting a periodic advertisement sync packet including the channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs.

In some aspects, identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs may include identifying that the conflict will occur while broadcasting the channel map update information.

In some aspects, identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs may include identifying that the conflict will occur while broadcasting the AUX connection request message.

In some aspects, adding the channel map update information to the AUX connection request message may include adding a channel map field including channel map information and a timing field indicating channel timing information to the AUX connection request message.

Various aspects may include an ESL receiving from an access point (AP) an AUX connection request message that includes channel map update information, identifying, from the AUX connection request message, updated channel map information and channel timing information, and using the updated channel map information and channel timing information to communicate with the AP.

In some aspects, receiving from the AP the AUX connection request message that includes channel map update information may include receiving the AUX connection request message during a time allocated for a periodic advertisement from the AP.

Further aspects include an ESL and an AP and/or a store management entity server (or other entity) configured with a processor for performing one or more operations of any of the methods summarized above. Further aspects include an ESL having a processor configured to perform one or more operations of any of the methods summarized above. Further aspects include an AP having a processor configured to perform one or more operations of any of the methods summarized above. Further aspects include a store management entity server (or other entity) that includes a processor configured to perform one or more operations of any of the methods summarized above. Further aspects may include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of an ESL or an AP to perform operations of any of the methods summarized above. Further aspects include an ESL or an AP having means for performing functions of any of the methods summarized above.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitute 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 the features of the claims.

FIG. 1A is a system block diagram illustrating an ESL system suitable for implementing any of various embodiments.

FIG. 1B is a system block diagram illustrating an example configuration of signal communications in an ESL system implementing some embodiments.

FIG. 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 various embodiments.

FIG. 3A is a timeline illustrating messages broadcast by an AP according to various embodiments.

FIG. 3B is a message flow diagram illustrating a reconnection mechanism and a block diagram illustrating a structure of an AUX connection request message according to various embodiments.

FIG. 3C is a block diagram illustrating an AUX connection request message according to various embodiments.

FIG. 4 is a process flow diagram of a method of managing channel map update information in accordance with various embodiments.

FIG. 5 is a process flow diagram of a method of managing channel map update information in accordance with various embodiments.

FIG. 6 is a component block diagram of an ESL suitable for use with various embodiments

FIG. 7 is a component block diagram of an access point suitable for use with various embodiments.

FIG. 8 is a component block diagram of a server suitable for use with various embodiments.

FIG. 9 is a component block diagram of a user mobile device suitable for use with various embodiments.

DETAILED DESCRIPTION

Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the claims.

Various embodiments include methods, and access points (APs) and ESLs configured to implement the methods, for enabling an AP to broadcast, and to enable an ESL to receive from the AP, channel map update information even when periodic advertising messages that normally carry channel map update information are preempted by another message that is broadcast by the AP. Various embodiments improve the operation of ESLs, APs, and ESL systems by enabling ESLs to remain in sync with an AP.

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 secured to, in, on, or near store shelves. The ESL may include a processor, memory, a display, and one or more wireless transceivers, in which the processor may be programmed or provided data to render images (e.g., text, bar codes, trademarks, etc. ) that communicate information (e.g., to people) regarding products near the device. In some aspects, ESLs may be battery powered to enable placement on or near products without the need for a power infrastructure. Alternatively, an ESL may be supplied power by the shelve to which the ESL is secured.

ESLs may be programmed, reprogrammed or updated (e.g., via onboarding messages transmitted by the AP) so that product information rendered on the display can be updated at any time. Thus, the ESLs may serve the function of paper shelf labels with the added efficiency of enabling product information (e.g., prices) to be changed without physically replacing shelf labels.

While various embodiments are described with reference to ESLs being placed on shelves within a store, ESLs may also be positioned on large goods (e.g., furniture, appliances, etc. ) , on or near stands or stacks of goods, on pallets on which products are positioned, and other locations where products may be offered for sale or selection. Further, ESLs may be used for other purposes, such as placed on doors to indicate vacant or occupied status. Use of the term “shelf” (or as signified by the “S” in ESL) is not intended to limit the claims to labels that are only positioned on shelves.

In some configurations, ESLs may include extended reality (XR) tags that may send signals to an XR device (e.g., smart glasses, display screen of a smart phone, or other device configured to provide extended reality displays) configured to cause the XR device to generate a visible display. The content visible on a display of an XR device based on signals of the XR tag may be viewable while a store picker or other user looks at (i.e., orients the XR glasses in the direction of) the ESL. For example, an XR device directed at a bag of potato chips may display product related information such as “Lays Potato Chips $1.99. ” The information provided by the XR tags may be the same or different than what is viewable in the ESL to normal users that do not use XR glasses or another XR device. In some embodiments, the ESL may not include a display, but rather may operate as an XR anchor to send operation messages and other information to XR devices. For example, when a user wearing XR glasses looks at a product (e.g., Lays Potato Chips) , a small window may appear on a user interface (UI) showing product information (e.g., “Lays Potato Chips $1.99” ) .

As used herein, the term “computing device” refers to an electronic device equipped with at least a processor, memory, and a device for presenting output such as a location of an object or objects of interest. In some embodiments, a computing device may include wireless communication devices such as a transceiver and antenna configured to communicate with wireless communication networks. A computing device may include any one or all of an outer smart device, a base-band, smart watches, smart rings, smart necklaces, smart glasses, smart contact lenses, contactless sleep tracking devices, smart furniture such as a smart bed or smart sofa, smart exercise equipment, Internet of Things (IoT) devices, augmented/virtual reality devices, cellular telephones, smartphones, portable computing devices, personal or mobile multimedia players, laptop computers, tablet computers, 2-in-1 laptop/table computers, smart books, ultrabooks, multimedia Internet-enabled cellular telephones, entertainment devices (e.g., wireless gaming controllers, music and video players, satellite radios, etc. ) , and similar electronic devices that include a memory, wireless communication components and a programmable processor. In some embodiments, a computing device may be wearable device by a person. As used herein, the term “smart” in conjunction with a device, refers to a device that includes a processor for automatic operation, for collecting and/or processing of data, and/or may be programmed to perform all or a portion of the operations described with regard to various embodiments.

The term “mobile wireless device” is used herein to refer to computing devices that include any one or all of customer smartphones, a store picker’s mobile wireless device, cellular telephones, portable computing devices, laptop computers, tablet computers, smartbooks, ultrabooks, palmtop computers, multimedia Internet-enabled cellular telephones, wearable devices including smart watches, smart clothing, smart glasses, earbuds, headphones, smart wrist bands, and similar electronic devices that include a memory, wireless communication components and a programmable processor.

The term “user mobile device” is used to refer to a mobile wireless device that is specifically configured to support users within a store, such as the store picker job functioning within a store picker system according to various embodiments. A store picker wireless device may include a processor, memory, an electronic display, wireless transceiver (s) including a Bluetooth transceiver and Wi-Fi transceiver, a barcode scanner, and other components useful for store picking.

The term “store” when used herein with reference to a physical place refers to a wholesale, retail, or other building in which products are stored for sale and/or distribution. A store may include (but is not limited to) a warehouse, fulfillment center, department store, specialty store, market, supermarket, hypermarket, convenience store, discount store, super store, and/or other storage facility.

The term “product” is used herein to refer to one or more items, articles, merchandise, or substances that are collected, refined, manufactured, and/or assembled and are maintained in a store or the like, such as products that may be identified on a shopping list and picked by store pickers.

The term “system on chip” (SOC) is used herein to refer to a single integrated circuit (IC) chip that contains multiple resources and/or processors integrated on a single substrate. A single SOC may contain circuitry for digital, analog, mixed-signal, and radio-frequency functions. A single SOC may also include any number of general purpose and/or specialized processors (digital signal processors, modem processors, video processors, etc. ) , memory blocks (e.g., ROM, RAM, Flash, etc. ) , and resources (e.g., timers, voltage regulators, oscillators, etc. ) . SOCs may also include software for controlling the integrated resources and processors, as well as for controlling peripheral devices.

The term “system in a package” (SIP) may be used herein to refer to a single module or package that contains multiple resources, computational 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, the SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unifying substrate. A SIP may also include multiple independent SOCs coupled together via high speed communication circuitry and packaged in close proximity, such as on a single motherboard or in a single computing device. The proximity of the SOCs facilitates high speed communications and the sharing of memory and resources.

ESLs may communicate with a network access point (AP) using an energy-efficient, short range communication protocol such as the Bluetooth Low Energy (BLE) protocol. An AP may broadcast periodic advertisement (PA) messages at substantially regular intervals, which messages may include operational code to access onboarding ESLs, or may serve as synchronization signals for use by ESLs. For example, an AP may send a PA message periodically at 12.5 millisecond (ms) intervals. In some implementations, the PA message may include a packet data unit (PDU) type specified as AUX_SYNC_IND. The PA message may include instructions (e.g., opcode) to access onboarded ESLs. The PA message may not include instructions or other code (e.g., the PA message may be “empty” ) , and in such configuration may serve as a synchronization message to enable ESLs to remain in synchronization with the AP. Some PA messages also may include Channel Map Update (CMU) information to provide ESLs an updated channel map with lower interference channels. In some embodiments, CMU information may be carried in an Additional Controller Advertising Data (ACAD) field of an AUX_SYNC_IND PDU. In some embodiments, a process of broadcasting and/or implementing updated CMU information may require up to about 9.6 seconds.

In an ESL system, an AP and an ESL may establish an active communication link (e.g., a BLE connection) for a short time to associate the ESL with the AP, or to read or write profile attributes (such as Generic ATTribute (GATT) Profile attributes) or to transmit a large block of data to the ESL, such as a price picture or firmware image. After completion of such communication operations, the AP and the ESL terminate the BLE connection. The ESL may maintain synchronization with the AP by receiving PA messages transmitted by the AP (also referred to as a PA train) . In some embodiments, the AP and the ESL may establish synchronization during association operations, onboarding operations, or resynchronization operations, and ESLs may synchronize with the AP via an AUX_SYNC_IND PDU or another suitable message.

When another data download to an ESL is required, the AP may send a message to the ESL to establish a new connection. In some embodiments, to establish a BLE communication link (e.g., an Asynchronous Connection-Less (ACL) communication link) , the AP may use the PA train and broadcast an AUX connection request message to initiate the establishment of the communication link. In some embodiments, the AUX connection request message may include an AUX_CONNECT_REQ (also referred to herein as ACRQ) message. However, in some cases the connection (or reconnection) process may conflict with the CMU information, preventing the ESL from receiving the CMU information. For example, the timing of the broadcast of an AUX_CONNECT_REQ (ACRQ) message may occur during a time designated for broadcast of a periodic advertising message such as the AUX_SYNC_IND PDU, such as a same slot or transmission opportunity. If an ACRQ message persistently occupies the time slot of the AUX_SYNC_IND PDU, an ESL may lose synchronization with the AP.

For example, an AP may be configured to preempt the broadcast of a periodic advertising message and to broadcast the AUX connection request message instead. However, the AUX connection request message (e.g., AUX_CONNECT_REQ or ACRQ) does not include CMU information. In the event that the AP switches to using updated CMU information, those ESLs that have not received the updated CMU information may lose synchronization with the AP. While out of synchronization with the AP, such ESLs may not receive price update information or other important operational data from the AP. Further, ESLs that lose synchronization with the AP may send signals in an attempt to reconnect with the AP, such as Connectable Advertising Packets, consuming wireless communication resources in a reconnection process.

Various embodiments include methods, and APs configured to implement the methods, for managing channel map update information. Various embodiments may enable an AP to broadcast, and enable an ESL to receive from the AP, channel map update information even when periodic advertising messages that normally carry channel map update information are preempted by another message that is broadcast by the AP, such as an AUX connection request message. Various embodiments may include identifying, by a processor of an AP, whether there will be a conflict between broadcasting channel map update information for reception by one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs. The processor of the AP may add channel map update information to the AUX connection request message in response to identifying that there will be a conflict between broadcasting the channel map update information and broadcasting the AUX connection request message. For example, the processor of the AP may configure a payload portion of the AUX connection request message (e.g., an AUX_CONNECT_REQ message) to include the channel map update information. The processor of the AP may broadcast the AUX connection request message including the channel map update information for reception by one or more ESLs.

In some embodiments, the AP may identify whether there will be a conflict between broadcasting a periodic advertisement sync packet including the channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs. In some embodiments, the AP may identify that the conflict will occur while broadcasting the channel map update information. In some embodiments, the AP may identify that the conflict will occur while broadcasting the AUX connection request message. In some embodiments, the AP may identify that the AUX connection request message will preempt the channel map update information, or will preempt the sending of a message that includes the channel map update information (such as a periodic advertisement message) .

In some embodiments, the AP may add to the AUX connection request message a channel map field including channel map information and a timing field indicating channel timing information. In some embodiments, the AP may add a field for Link Layer Data (an LLData field) or an Additional LLD data (ALLD) field to the AUX connection request message. In some embodiments, the AP may add the channel map update information to the AUX connection request message in response to determining that the AUX connection request message will preempt the channel map update information, or will preempt the sending of a message that includes the channel map update information (such as a periodic advertisement message) .

Various embodiments include methods, and ESLs configured to implement the methods, for managing channel map update information. Various embodiments may include receiving, by a processor of an ESL from an AP, an AUX connection request message that includes channel map update information. The processor of the ESL may identify from the AUX connection request message (i.e., within the channel map update information included in the AUX connection request message) updated channel map information and channel timing information, and may use the updated channel map information and channel timing information to communicate with the AP. In some embodiments, the AP may receive the AUX connection request message during a time (such as a time slot) allocated for a periodic advertisement from the AP.

Various embodiments improve the operation of ESLs, APs, and ESL systems by enabling ESLs to remain in sync with an AP. Various embodiments improve the operation of ESLs, APs, and ESL systems by enabling the broadcast, reception, and use of channel map update information in messages other than periodic advertisement messages.

FIG. 1A is a component block diagram of an ESL system 100 suitable for implementing various embodiments. System elements that may be deployed within a given store 10 may include a plurality of ESLs 110 deployed on shelves 50 that are configured to communicate with a number of APs 130 that are connected to a store management entity server 150.

ESLs 110 may be positioned on shelves 50 associated with products (labeled a, b, c, d, e, f, g, h, i, j, k, and m) . Each ESL 110 may include a display 115 on which is presented product name, product codes, prices, stocking information, barcodes, and the like. Some ESLs 110 may further include an illuminator 117, such as a light emitting diode (LED) or other visible light generating devices configured to illuminate to draw 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 to generate visual, audible, and/or tactile notifications. Each ESL 110 may include a beacon transmitter and be configured to detect neighboring ESLs, such as via BLE signals. Some ESLs 110 may include one or more sensors, such as (but not limited to) a proximity sensor to detect when an individual is standing near the ESL 110, a microphone for monitoring ambient noise as well as receiving speech from a customer or store picker in some embodiments, and/or the like. In some embodiments, various ESLs deployed in the ESL system 100 may be configured and/or equipped with different capabilities or with the same capabilities.

The ESLs 110 may be configured to receive communications from the store management entity server 150, such as through wireless communication links 112 that may be relayed via the APs 130. Thus, the store management entity server 150 may configure each ESL 110 with product information to be displayed, as well as duty cycles for when the ESL should activate to receive signals and transmit wireless beacons. The store management entity server 150 may control the periodicity of ESL duty cycles in order to minimize battery drain/usage, so as to extend the operating life, while ensuring the ESL is responsive to customers and store pickers, such as by increasing the duty cycle when individuals are within proximity of an ESL (e.g., close enough to see and/or read a display of the ESL) . Further, management entity server 150 may configure ESLs 110 to generate an appropriate indication (e.g., visual, audible, and/or tactile indications) at an appropriate time, such as when an ESL is associated with a product that appears on a shopping list of a user that is 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 located remotely and accessed via a communication network 154.

ESLs 110 may be configured to exchange wireless communications with each other through wireless links 112, such as wireless beacons or tones, for various purposes, including in particular for determining the relative and actual location of the ESLs on shelves 50 and with respect to one another as described herein.

In some embodiments, the ESL system 100 deployed within a store 10 may also include other mechanisms for determining the precise location of ESLs and individual store pickers or customers. For example, in some embodiments, the system may include ultrasonic emitters 134 that may be configured to periodically or episodically admit ultrasonic tones (for example) that can be received by a microphone on each ESL 110 for purposes of determining relative location of each ESL via sound ranging processes. As another example, in some embodiment, the system may include infrared emitters that may be configured to emit an infrared light beam that can be received by a photo-detector on each ESL for the purpose of determining relative location via IR ranging techniques. As another example, the system may include cameras 132 coupled to the store management entity server 150 that may be positioned to provide imaging of ESLs 110 as well as individuals (e.g., store pickers, customers, and/or other individuals) . Image data received from such cameras 132 may be used by the store management entity server 150 to determining the location of each ESL and individuals. In some embodiments, the camera 132 may be positioned on the shelves so as to view products as well as individuals near the products. In some embodiments, ESLs 110 may include a camera and be configured to transmit images to the store management entity server 150 via a wireless link 112 with an AP 130.

The store management entity server 150 may be configured with detailed maps of the locations of products within the store, referred to as a planogram, that is correlated or calibrated to an indoor location system, such as supported by the ESLs 110 as described. The store management entity server 150 may also incorporate information from an inventory system that keeps track of the products stocks in order to avoid sending a store picker to the location of a product that is out of stock.

The APs 130 may be configured to communicate with ESLs 110 to provide communications with the store management entity server 150. In some embodiments, APs may be configured with cameras or be coupled to cameras to provide visual images of ESLs as well as customers and store pickers to provide more precise location information as described herein. APs 130 may also be configured with antenna arrays that enable determining the angle of arrival (AOA) of wireless communications, providing further localization information to the store management entity server 150.

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

FIG 1B illustrates further details of communication links that may be utilized in the ESL system 100 according to some embodiments. With reference to FIGs. 1A and 1B, ESLs 110 may be configured to communicate with APs 130 via wireless links 112a, such as Bluetooth, and to exchange wireless signals with other ESLs 110 via wireless links 112b. For example, ESLs 110 may transmit certain BLE signals 112a, such ESL advertisements that are configured to be received by a nearby AP 130 and used to onboard the ESL 110. In addition, ESLs 110 on opposite sides of an aisle (i.e., the separation between two shelves 50) may transmit certain BLE signals 112b that are configured to be received by a nearby ESL 110 and used for the purposes of determining relative positions of the respective devices.

BLE signals

112a, 112b may be broadcast at a set or select power level, enabling separation distances to be estimated based upon the measured received signal strength indicator (RSSI) of the signals received by other ESLs 110. APs 130 may be coupled to the store management entity server 150 via wired connections 132.

User mobile devices 120, which may be held, carried, or otherwise associated with a store picker or customer may receive a beacon signal, such as through a wireless link from ESLs and communicate with the store management entity server 150 via wireless communications, such as BLE, Wi-Fi, or cellular communications of various types. The APs 130 may be configured to communicate with user mobile devices 120 to provide communications with the store management entity server 150. The APs 130 may also provide user mobile devices 120 with access to external communication networks, such as the communication network 154, to enable customers to access remote servers 156, such as to comparison shop, research products, and otherwise provide Internet access support.

User mobile devices 120 used by store pickers may receive beacon signals (e.g., BT or BLE) from each of the ESLs 110 but also communicate received beacon information (e.g., identity code and RSS I information) directly to the store management entity server 150 via separate communications 122. Such separate communications 122 may be via Wi-Fi communications (e.g., via APs 130) or via cellular data networks (e.g., fifth generation (5G) cellular networks) .

FIG. 2 is 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 ESLs, for implementing any of various embodiments. Various embodiments may be implemented on a number of single processor and multiprocessor computer systems, including a system-on-chip (SOC) or system in a package (SIP) .

With reference to FIGS. 1A-2, the illustrated example computing system 200 (which may be a SIP in some embodiments) includes a two

SOCs

202, 204 coupled to a clock 206, a voltage regulator 208, a radio module 266 configured to send 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 Aps or ESLs, the radio module 266 may be configured to broadcast BLE beacons as described herein. In some implementations, the first SOC 202 may operate as central processing unit (CPU) of the user mobile device that carries out the instructions of software application programs by performing the arithmetic, logical, control and input/output (I/O) operations specified by the instructions. In some implementations, the second SOC 204 may operate as a specialized processing unit. For example, the second SOC 204 may operate as a specialized 5G processing unit responsible for managing high volume, high speed (such as 5 Gbps, etc. ) , or very high frequency short wave length (such as 38 GHz mmWave spectrum, etc. ) communications.

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 vector co-processor) connected to one or more of the processors, memory 220, custom circuitry 222, system components and resources 224, an interconnection/bus module 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 interconnection/bus module 264, a plurality of mmWave transceivers 256, memory 258, and various additional processors 260, such as an applications processor, packet processor, etc.

Each

processor

210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor/core may perform operations independent of the 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. ) .

The first and

second SOC

202, 204 may include various system components, resources and custom circuitry for managing sensor data, analog-to-digital conversions, wireless data transmissions, and for performing other specialized operations, such as decoding data packets and processing encoded audio and video signals for rendering 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 the processors and software clients running on a user mobile device. The system components and resources 224 or custom circuitry 222 also may include circuitry to interface with peripheral devices, such as cameras, electronic displays, wireless communication devices, external memory chips, etc.

The first and

second SOC

202, 204 may communicate via interconnection/bus module 250.

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 circuitry 222, and a thermal management unit 232 via an interconnection/bus module 226. Similarly, the processor 252 may be interconnected to the power management unit 254, the mmWave transceivers 256, memory 258, and various additional processors 260 via the interconnection/bus module 264. The interconnection/

bus module

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 high-performance networks-on chip (NoCs) .

The first or

second SOCs

202, 204 may further 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 clock 206, voltage regulator 208) may be shared by two or more of the internal SOC processors/cores.

FIG. 3A is a timeline 300a illustrating messages broadcast by an AP (e.g., 130) according to various embodiments. With reference to FIGS. 1A-3A, the broadcast by an AP of an AUX connection request message, for example, an AUX_CONNECT_REQ (ACRQ) may conflict with (collide with, be scheduled at a same time or slot as) a message carrying CMU information (e.g., a periodic advertisement message, such as an AUX_SYNC_IND PDU) . For example, while the broadcast of CMU information 304a does not conflict with AUX

connection request message

302a or 302b, and no CMU information conflicts with AUX connection request messages 302c-302e, the broadcast of CMU information 304b conflicts with AUX connection request message 302f. In some embodiments, in the event of a conflict, the AP may preempt the broadcast of the CMU information 304b and instead broadcast the AUX connection request message 302f.

FIG. 3B is a message flow diagram 300b illustrating a reconnection mechanism and a block diagram 300c illustrating a structure of an AUX connection request message according to various embodiments. With reference to FIGS. 1A-3B, in various embodiments, an AP 306 (e.g., 130) may include a Host module (Host A) and a Link Layer module (LL A) , and an ESL 308 (e.g., 110) may include a Link Layer module (LL B) and a Host module (Host B) . The AP 306 may send an AUX connection request message (e.g., AUX_CONNECT_REQ PDU) to the ESL 308. The AUX connection request message may include a payload 310 including various fields such as an initiating device’s address (InitA) field an advertising device’s address (AdvA) field, and a Link Layer data (LLData) field. The LLData field may include a variety of sub-fields that include signal format and timing information to enable the ESL 308 to establish or reestablish a communication link or session with the AP 306.

FIG. 3C is a block diagram illustrating an AUX connection request message 300d according to various embodiments. With reference to FIGS. 1A-3C, in various embodiments an AP (e.g., 130, 306) may add channel map update information to the AUX connection request message in response to identifying that there will be a conflict between broadcasting a channel map update information and broadcasting an AUX connection request message. In some embodiments, the AP may add a field 314, such as an Additional LLData (ALLD) field, to a payload portion 312 of the AUX connection request message. In various embodiments, the reconfigured AUX connection request message 300d may include a new AUX_CONNECTION_REQ message format.

The field 314 may be configured to include channel map update information. In various embodiments, the channel map update information added to the AUX connection request message 300d may be the same as channel map update information that the AP may provide in a periodic advertisement message. The field 314 may include a variety of sub-fields, including a new channel map field 316 ( “new channel map for PA subevent” ) and a timing information field 318 ( “Instant” ) . The information including in the added field 314 enables a receiving ESL to obtain the channel map update information, such as updated channel map information (e.g., from field 316) and channel timing information (e.g., from field 318) which the ESL may use remain in synchronization with the AP, to communicate with the AP.

FIG. 4 is a process flow diagram of a method 400 of managing channel map update information in accordance with various embodiments. With reference to FIGS. 1A–4, means for performing each of the operations of the 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) and the like.

In block 402, the processor may identify whether there will be a conflict between broadcasting channel map update information for reception by one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs. In some embodiments, the processor may identify whether there will be a conflict between broadcasting a periodic advertisement sync packet that includes the channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs. In some embodiments, the processor may identify an upcoming conflict while performing one or more operations. For example, the processor may identify that the conflict will occur while broadcasting the channel map update information. As another example, the processor may identify that the conflict will occur while broadcasting the AUX connection request message.

In block 404, the processor may add channel map update information to the AUX connection request message in response to identifying that there will be a conflict between broadcasting the channel map update information and broadcasting the AUX connection request message. In some embodiments, the processor may add to the AUX connection request message (e.g., an AUX_CONNECT_REQ or another suitable message) a channel map field including channel map information (e.g., 316) and a timing field indicating channel timing information (e.g., 318) to the AUX connection request message. In some embodiments, the channel map update information that is added to the AUX connection request message is substantially the same as channel map update information that may otherwise be sent by the AP in a periodic advertisement message (e.g., AUX_SYNC_IND or another suitable message) .

In block 406, the processor may broadcast the AUX connection request message including the channel map update information.

FIG. 5 is a process flow diagram of a method 500 of managing channel map update information in accordance with various embodiments. With reference to FIGS. 1A–5, means for performing each of the operations of the method 500 may include a processor (e.g., 210, 212, 214, 216, 218, 252, 260, and/or 602) and/or a transceiver (e.g., 604) of an ESL (e.g., 110, 308) and the like.

In block 502, the processor may receive from an AP (e.g., 130, 306) an AUX connection request message that includes channel map update information. In some embodiments, the processor may receive the AUX connection request message during a time allocated for a periodic advertisement (e.g., AUX_SYNC_IND or another suitable message) from the AP. In some embodiments, the time allocated may include a slot or another suitable transmission opportunity.

In block 504, the processor may identify from the AUX connection request message (i.e., within the channel map update information included in the AUX connection request message) updated channel map information and channel timing information. In some embodiments, the processor may be configured to identify or obtain a data field appended to the AUX connection request message, such as an ALLD field (e.g., 314) or another suitable data structure. In some embodiments, the processor may be configured to identify or obtain information from one or more subfields of the data field appended to the AUX connection request message, such as a channel map field including channel map information (e.g., 316) and a timing field indicating channel timing information (e.g., 318) to the AUX connection request message.

In block 506, the processor may use the updated channel map information and channel timing information to communicate with the AP. For example, the processor may switch to using one or more channels based on the channel map information and associated channel timing information.

FIG. 6 is a component block diagram of an example of an ESL 110 suitable for use with various embodiments. With reference to FIGS. 1A–6, an ESL 110 may include a display 115 and an illuminator 117 (e.g., an LED or other type of visible indicator) that our coupled to a processor 602 that is configured with processor-executable instructions configured to cause the processor to perform operations of various embodiments. The processor 602 may be coupled to a wireless transceiver 604, such as a BLE transceiver or a combination BLE and Wi-Fi transceiver, that is coupled to an antenna 606 for sending and receiving radio frequency (RF) signals as described herein. In various embodiments, the processor 602 may include an SOC (e.g., 202, 204) . An ESL 110 may be powered by a battery 608, freeing the display from having to be connected to a wired power supply. Alternatively, the ESL 110 may be powered from an external source.

FIG. 7 is a component block diagram of an AP 130 suitable for use with various embodiments. With reference to FIGS. 1A–7, the AP 130 may typically include a

processor

702, 704 coupled to volatile memory 706 and optionally a larger capacity nonvolatile memory 708. The AP 130 may also include a peripheral memory access device, such as a flash drive, coupled to the

processor

702, 704. The AP 130 may also include network access ports 714 (or interfaces) coupled to the

processor

702, 704 for establishing data connections 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, and the like 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 sending (i.e., transmitting) and receiving electromagnetic radiation that may be connected to a wireless communication link.

FIG. 8 is a component block diagram of a store management entity server 150 suitable for use with various embodiments. With reference to FIGS. 1A–8, the store management entity server 150 may typically include a processor 801 coupled to volatile memory 802 and a large capacity nonvolatile memory, such as a disk drive 803. The store management entity server 150 may also include a peripheral memory access device, such as a floppy disc drive, compact disc (CD) or digital video disc (DVD) drive 806 coupled to the processor 801. The store management entity server 150 may also include network access ports 804 (or interfaces) coupled to the processor 801 for establishing data connections 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 sending and receiving electromagnetic radiation that may be connected to a wireless communication link. The store management entity server 150 may include additional access ports, such as USB, Firewire, Thunderbolt, and the like for coupling to peripherals, external memory, or other devices.

FIG. 9 is a component block diagram of a user mobile device 120 suitable for use as a user mobile device or a consumer user equipment (UE) when configured with processor executable instructions to perform operations of various embodiments. With reference to FIGS. 1A–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 and

second SOCs

202, 204 may be coupled to internal memory 906, a display 915, and to a speaker 914. Additionally, the user mobile device 120 may include an antenna 904 for sending and receiving electromagnetic radiation that may be connected to a radio module 266 configured to support wireless local area network data links (e.g., BLE, Wi-Fi, etc. ) and/or wireless wide area networks (e.g., cellular telephone networks) coupled to one or more processors in the first and/or

second SOCs

202, 204. The user mobile device 120 typically also include menu selection buttons 920 for receiving user inputs.

A typical user mobile device 120 may also include an inertial measurement unit (IMU) 268 that includes a number of micro-electromechanical sensor (MEMS) elements configured to sense accelerations and rotations associated movements of the device, and provide such movement information to the first SOC 202. Also, one or more of the processors in the first and

second SOCs

202, 204, wireless transceiver 266 may include a digital signal processor (DSP) circuit (not shown separately) .

In some embodiments, a user mobile device 120 may be used as a moving AP to diagnose ESLs that have issues establishing communication with the APs or other fixed infrastructure. For example, the user mobile device 120 may be repurposed by the store management entity server by configuring the user mobile device 120 with AP protocols so that the user mobile device 120 may be recognized by ESL as an AP.

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

Various embodiments illustrated and described are provided merely as examples to illustrate various features of the claims. However, 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 that are shown and described. Further, the claims are not intended to be limited by any one example embodiment. For example, one or more of the operations of the methods 400 and/or 500 may be substituted for or combined with one or more operations of the methods 400 and/or 500.

Implementation examples are described in the following paragraphs. While some of the following implementation examples are described in terms of example methods, further example implementations may include: the example methods discussed in the following paragraphs implemented by an ESL, an AP, a store management entity server (or other entity) , and/or a user mobile device, including a processor configured to perform operations of the example methods; the example methods discussed in the following paragraphs implemented by an ESL, an AP, a store management entity server (or other entity) , and/or a user mobile device, including means for performing functions of the example methods; the example methods discussed in the following paragraphs implemented in a processor used in an ESL, an AP, a store management entity server (or other entity) , and/or a user mobile device that is configured to perform the operations of the example methods; and the example methods discussed in the following paragraphs implemented as a non-transitory processor-readable storage medium having stored thereon processor- executable instructions configured to cause a processor or modem processor to perform the operations of the example methods.

Example 1. A method of managing channel map update information performed by a processor of an access point (AP) , including identifying whether there will be a conflict between broadcasting channel map update information for reception by one or more electronic shelf labels (ESLs) and broadcasting an AUX connection request message for reception by the one or more ESLs, adding channel map update information to the AUX connection request message in response to identifying that there will be a conflict between broadcasting the channel map update information and broadcasting the AUX connection request message, and broadcasting the AUX connection request message including the channel map update information.

Example 2. The method of example 1, in which identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs includes identifying whether there will be a conflict between broadcasting a periodic advertisement sync packet including the channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs.

Example 3. The method of either of examples 1 or 2, in which identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs includes identifying that the conflict will occur while broadcasting the channel map update information.

Example 4. The method of any of examples 1-3, in which identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs includes identifying that the conflict will occur while broadcasting the AUX connection request message.

Example 5. The method of any of examples 1-4, in which adding the channel map update information to the AUX connection request message includes adding a channel map field including channel map information and a timing field indicating channel timing information to the AUX connection request message.

Example 6. A method of managing channel map update information performed by a processor of an electronic shelf label (ESL) , including receiving from an access point (AP) an AUX connection request message that includes channel map update information, identifying, from the AUX connection request message, updated channel map information and channel timing information, and using the updated channel map information and channel timing information to communicate with the AP.

Example 7. The method of example 6, in which receiving from the AP the AUX connection request message that includes channel map update information includes receiving the AUX connection request message during a time allocated for a periodic advertisement from the AP.

A number of different cellular and mobile communication services and standards are available or contemplated in the future, all of which may implement and benefit from various aspects. Such services and standards may include, e.g., third generation partnership project (3GPP) , long term evolution (LTE) systems, 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) systems (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 &II (WPA, WPA2) , integrated digital enhanced network (iDEN) , C-V2X, V2V, V2P, V2I, and V2N, etc. Each of these technologies involves, for example, the transmission and reception of voice, data, signaling, and/or content messages. It should be understood that any references to terminology and/or technical details related to an individual telecommunication standard or technology are for illustrative purposes only, and are not intended to limit the scope of the claims to a particular communication system or technology unless specifically recited in the claim language.

The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the operations of various embodiments must be performed in the order presented. As will be appreciated by one of skill 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 the operations; these words are used to guide the reader through the description of the methods. Further, any reference to claim elements in the singular, for example, using the articles “a, ” “an, ” or “the” is not to be construed as limiting the element to the singular.

Various illustrative logical blocks, modules, components, circuits, and algorithm operations described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and operations have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such embodiment decisions should not be interpreted as causing a departure from the scope of the claims.

The hardware used to implement various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of receiver smart objects, e.g., 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 circuitry that is specific to a given function.

In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or non-transitory processor-readable storage medium. The operations of a method or algorithm disclosed herein may be embodied in a processor-executable software module or processor-executable instructions, which may reside on a non-transitory computer-readable or processor-readable storage medium. Non-transitory computer-readable or processor-readable storage media may be any storage media that may be accessed by a computer or a processor. By way of example but not limitation, such non-transitory computer-readable or processor-readable storage media may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage smart objects, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above 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.

The preceding 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 readily apparent to those skilled in the art, and the generic 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 is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.

Claims

A method of managing channel map update information performed by a processor of an access point (AP) , comprising:

identifying whether there will be a conflict between broadcasting channel map update information for reception by one or more electronic shelf labels (ESLs) and broadcasting an AUX connection request message for reception by the one or more ESLs;

adding channel map update information to the AUX connection request message in response to identifying that there will be a conflict between broadcasting the channel map update information and broadcasting the AUX connection request message; and

broadcasting the AUX connection request message including the channel map update information.
The method of claim 1, wherein identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs comprises identifying whether there will be a conflict between broadcasting a periodic advertisement sync packet including the channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs.
The method of claim 1, wherein identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs comprises identifying that the conflict will occur while broadcasting the channel map update information.
The method of claim 1, wherein identifying whether there will be a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs comprises identifying that the conflict will occur while broadcasting the AUX connection request message.
The method of claim 1, wherein adding the channel map update information to the AUX connection request message comprises adding a channel map field including channel map information and a timing field indicating channel timing information to the AUX connection request message.
An access point (AP) , comprising:

a transceiver; and

a processor coupled to the transceiver and configured to:

identify whether there will be a conflict between broadcasting channel map update information for reception by one or more electronic shelf labels (ESLs) and broadcasting an AUX connection request message for reception by the one or more ESLs;

add channel map update information to the AUX connection request message in response to identifying that there will be a conflict between broadcasting the channel map update information and broadcasting the AUX connection request message; and

broadcast the AUX connection request message including the channel map update information.
The AP of claim 6, wherein the processor is further configured to identify whether there will be a conflict between broadcasting a periodic advertisement sync packet including the channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs.
The AP of claim 6, wherein the processor is further configured to identify that a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs will occur while broadcasting the channel map update information.
The AP of claim 6, wherein the processor is further configured to identify that a conflict between broadcasting channel map update information for reception by the one or more ESLs and broadcasting an AUX connection request message for reception by the one or more ESLs will occur while broadcasting the AUX connection request message.
The AP of claim 6, wherein the processor is further configured to add a channel map field including channel map information and a timing field indicating channel timing information to the AUX connection request message.
A method of managing channel map update information performed by a processor of an electronic shelf label (ESL) , comprising:

receiving from an access point (AP) an AUX connection request message that includes channel map update information;

identifying, from the AUX connection request message, updated channel map information and channel timing information; and

using the updated channel map information and channel timing information to communicate with the AP.
The method of claim 11, wherein receiving from the AP the AUX connection request message that includes channel map update information comprises receiving the AUX connection request message during a time allocated for a periodic advertisement from the AP.
An electronic shelf label (ESL) , comprising:

a transceiver; and

a processor coupled to the transceiver and configured to:

receive from an access point (AP) an AUX connection request message that includes channel map update information;

identify, from the AUX connection request message, updated channel map information and channel timing information; and

use the updated channel map information and channel timing information to communicate with the AP.
The ESL of claim 13, wherein the processor is further configured to receive the AUX connection request message during a time allocated for a periodic advertisement from the AP.