A Bluetooth-based WiFi scheduling method for retail screens to alleviate AP pressure

Abstract

This invention provides a method for Bluetooth-based WiFi scheduling in retail screens to alleviate AP pressure. The method includes: after powering on, keeping the WiFi communication module in an unconnected state, enabling the Bluetooth communication module, receiving AP pressure level, WiFi access window, task urgency level, and WiFi wake-up phase information from adjacent retail screens to form a scheduling constraint set; generating candidate WiFi wake-up phases based on the scheduling constraint set, and estimating the expected WiFi occupancy time by combining the task type to be executed, historical transmission records, and AP processing capacity to form phase occupancy segments; broadcasting the phase occupancy segments of this retail screen via the Bluetooth communication module and receiving phase occupancy segments from adjacent retail screens to form a neighborhood phase segment set, determining phase overlap, and generating phase conflict results; when phase conflicts exist, generating a target WiFi wake-up phase based on the conflict severity and the most recent WiFi access result, and writing it into a local phase table.

Description

Technical Field

[0001] This invention relates to the field of wireless communication access scheduling technology, and in particular to a method for scheduling WiFi via Bluetooth on retail screens to alleviate AP pressure. Background Technology

[0002] With the development of digital management in retail stores, electronic shelf labels, retail LCD screens, and shelf displays are being deployed in large numbers to display prices, promotional information, advertising materials, and status prompts. Existing retail screens typically connect to the store's access point (AP) via WiFi and interact with servers or edge network nodes to complete tasks such as server registration, material verification, material discrepancy requests, status reporting, and online confirmation.

[0003] In scenarios such as power outage recovery, unified restart at night, batch deployment of new stores, centralized updates of promotional materials, or recovery after AP maintenance, a large number of retail screens within the same store area often activate their WiFi communication modules at similar times according to the same firmware logic, and centrally perform AP association, address acquisition, server connection, and material verification. At this time, even if the data volume of a single retail screen is small, the simultaneous access of the group will generate a large number of connection requests, management frames, small packet reports, and failure retry requests in a short period of time, resulting in increased AP association latency, address acquisition failures, slower business response, and even repeated disconnections.

[0004] Therefore, this invention proposes a Bluetooth-based WiFi scheduling method for retail screens to alleviate AP pressure. The information disclosed in the background section is only for enhancing understanding of the background of this disclosure and may therefore contain prior art information that is not common knowledge to those skilled in the art. Summary of the Invention

[0005] The purpose of this invention is to address the shortcomings of existing technologies by providing a method for Bluetooth-based WiFi scheduling in retail screens to alleviate AP pressure, thereby solving the technical problems mentioned in the background section.

[0006] To achieve the above objectives, the present invention provides the following technical solution:

[0007] A method for Bluetooth-based WiFi scheduling in retail screens to alleviate AP pressure includes the following steps:

[0008] S1. After the retail screen is powered on, read the screen identifier, store area identifier, local phase table, the most recent WiFi access result and the type of task to be executed, keep the WiFi communication module in an unconnected state, and enable the Bluetooth communication module to receive the AP pressure status level, WiFi access window, task urgency level and WiFi wake-up phase information to form a set of scheduling constraints.

[0009] S2. Based on the scheduling constraint set, generate candidate WiFi wake-up phases within the available WiFi access window, and estimate the expected WiFi occupancy time based on the type of task to be executed, historical transmission records, and AP processing capacity to form phase occupancy segments.

[0010] S3. Broadcast the phase occupancy segment of this retail screen and receive the phase occupancy segment of adjacent retail screens through the Bluetooth communication module to form a set of neighborhood phase segments, determine phase overlap and generate phase conflict results;

[0011] S4. When the phase conflict result is a conflict, generate the target WiFi wake-up phase based on the conflict severity, task urgency level, the most recent WiFi access result and the local phase table, and write it into the local phase table.

[0012] S5. After the validity verification is passed at the access time corresponding to the target WiFi wake-up phase, the WiFi communication module is turned on to access the AP and execute the corresponding task, the WiFi access result is fed back, and the local phase table is updated.

[0013] S1 specifically includes: after the retail screen is powered on, reading the screen identifier, store area identifier, local phase table, most recent WiFi access result, and task type to be executed, keeping the WiFi communication module in an unconnected state, and only enabling the Bluetooth communication module to generate a basic scheduling status record; receiving the AP pressure status level, WiFi access window, task urgency level, and WiFi wake-up phase information broadcast by edge network nodes, gateways, or adjacent retail screens through the Bluetooth communication module to obtain the regional Bluetooth scheduling context; determining the necessity of access based on the basic scheduling status record and the regional Bluetooth scheduling context, removing expired data, and forming a scheduling constraint set containing available WiFi access windows, prohibited access windows, occupied WiFi wake-up phases, and narrowband IoT fallback markers.

[0014] S2 specifically includes: reading the available WiFi access window, prohibited access window, AP pressure status level, task urgency level, and occupied WiFi wake-up phase according to the scheduling constraint set; removing expired data; generating candidate WiFi wake-up phases within the available WiFi access window with the highest score; estimating the expected WiFi occupancy time based on the candidate WiFi wake-up phases, the type of task to be executed, the most recent WiFi access result, historical transmission records, and AP processing capacity; and determining whether narrowband IoT fallback backhaul is allowed; and combining the screen identifier, store area identifier, corresponding AP identifier, candidate WiFi wake-up phase, expected WiFi occupancy time, task urgency level, and effective time into a phase occupancy segment for broadcasting and phase overlap judgment.

[0015] S3 specifically includes: determining the area broadcast cycle based on the effective time of the phase occupancy segment, the AP pressure status level, and broadcast parameters; broadcasting the phase occupancy segment of this retail screen through the Bluetooth communication module; and verifying the received phase occupancy segments of adjacent retail screens by identifying the store area, corresponding AP, effective time, screen, and data source to form a neighborhood phase segment set; comparing the phase occupancy segment of this retail screen with the neighborhood phase segment set one by one, judging phase overlap based on the candidate WiFi wake-up phase and the expected WiFi occupancy duration, and forming a phase overlap record; and generating a phase conflict result based on the phase overlap record, which includes the conflict status, conflict screen list, conflict time range, and conflict severity.

[0016] S4 specifically includes: when the phase conflict result is a conflict, calculating the phase retention priority value of this retail screen and adjacent retail screens based on the conflict screen list, conflict time range, conflict severity, task urgency level, most recent WiFi access result, and local phase table, and determining whether to perform phase backoff correction, and generating phase backoff parameters when it is determined to perform; within the currently available WiFi access window, searching for candidate WiFi wake-up phases slot by slot according to the phase backoff parameters, avoiding neighboring phase segment sets and prohibited access windows, and generating target WiFi wake-up phases; writing the target WiFi wake-up phase, expected WiFi occupancy time, corresponding AP identifier, task urgency level, phase status, backoff reason marker, and phase confirmation status into the local phase table, and sending the phase confirmation status through the Bluetooth communication module.

[0017] S5 specifically includes: the retail screen reads the local phase table, verifies the valid time, phase confirmation status, AP pressure status level, and available WiFi access window before the access time corresponding to the target WiFi wake-up phase. After successful verification, the WiFi communication module is activated to access the AP, and a WiFi access process record is generated. After successful WiFi access, server registration, material verification, material difference request, or status reporting tasks are executed according to the task type to be executed. If WiFi access fails, the Bluetooth communication module is kept on and the next round of phase breakage scheduling or Bluetooth hold-up status is entered. The WiFi access result is generated based on the WiFi access process record and task execution results, fed back through the Bluetooth communication module, and the local phase table is corrected.

[0018] The beneficial effects of this invention are as follows:

[0019] This invention obtains the AP stress level, WiFi access window, and phase occupancy segments of adjacent retail screens via Bluetooth communication before the retail screen activates its WiFi communication module. This allows the retail screens to complete pre-access scheduling without occupying AP resources, reducing the instantaneous impact of simultaneous access on the AP from the source. By generating and broadcasting candidate WiFi wake-up phases, expected WiFi occupancy durations, and phase occupancy segments, retail screens within the same store area can declare in advance the time range within which they plan to occupy WiFi access resources, reducing the situation where multiple retail screens compete for the same AP at similar times.

[0020] This invention uses a set of neighboring phase segments to determine phase overlap and generates phase conflict results and severity when conflicts exist. This allows retail screens to perform phase backoff correction based on explicit conflict data, avoiding the need for retrying at fixed intervals and resulting in concentrated access. By generating a target WiFi wake-up phase based on task urgency level, the most recent WiFi access result, and the local phase table, it prioritizes high-priority tasks such as server registration, material difference requests, and abnormal status reporting, while delaying low-frequency, non-urgent tasks such as online confirmation, thus improving AP resource utilization efficiency.

[0021] This invention suppresses AP pressure amplification caused by repeated reconnections from failed WiFi screens by keeping the Bluetooth communication module active when WiFi access fails and determining whether to enter Bluetooth hold-up mode or proceed to the next round of phase breakage scheduling based on the most recent WiFi access results of adjacent retail screens. The WiFi access process record and task execution results are fed back to adjacent retail screens, gateways, or edge network nodes, and the local phase table is corrected. This allows the next round of scheduling to adjust the access timing based on the actual WiFi usage time and the cause of failure, forming a continuously optimized peak-shifting access closed loop. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of a retail screen Bluetooth-based WiFi scheduling method to alleviate AP pressure according to the present invention;

[0023] Figure 2 This is a schematic diagram illustrating the management of retail screen status and WiFi access status in this invention;

[0024] Figure 3 This is a schematic diagram of the generation of the regional Bluetooth scheduling context in this invention;

[0025] Figure 4 This is a schematic diagram of phase occupancy segment overlap detection and phase conflict result generation in this invention;

[0026] Figure 5 This is a schematic diagram of phase backoff correction and target WiFi wake-up phase generation in the present invention;

[0027] Figure 6 This is a schematic diagram illustrating WiFi access execution under the target WiFi wake-up phase in this invention;

[0028] Figure 7 This is a schematic diagram of AP pressure status monitoring and updating in this invention;

[0029] Figure 8 This is a schematic diagram of the scheduling parameter configuration in this invention. Detailed Implementation

[0030] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0031] Example: Figures 1 to 8 As shown, this embodiment provides a method for Bluetooth-based WiFi scheduling in retail screens to alleviate AP pressure, including the following steps:

[0032] S1. After the retail screen is powered on, read the screen identifier, store area identifier, local phase table, the most recent WiFi access result and the type of task to be executed, keep the WiFi communication module in an unconnected state, and enable the Bluetooth communication module to receive the AP pressure status level, WiFi access window, task urgency level and WiFi wake-up phase information to form a set of scheduling constraints.

[0033] S2. Based on the scheduling constraint set, generate candidate WiFi wake-up phases within the available WiFi access window, and estimate the expected WiFi occupancy time based on the type of task to be executed, historical transmission records, and AP processing capacity to form phase occupancy segments.

[0034] S3. Broadcast the phase occupancy segment of this retail screen and receive the phase occupancy segment of adjacent retail screens through the Bluetooth communication module to form a set of neighborhood phase segments, determine phase overlap and generate phase conflict results;

[0035] S4. When the phase conflict result is a conflict, generate the target WiFi wake-up phase based on the conflict severity, task urgency level, the most recent WiFi access result and the local phase table, and write it into the local phase table.

[0036] S5. After the validity verification is passed at the access time corresponding to the target WiFi wake-up phase, the WiFi communication module is turned on to access the AP and execute the corresponding task, the WiFi access result is fed back, and the local phase table is updated.

[0037] S1 specifically includes the following sub-steps:

[0038] After the S110 retail screen is powered on, it first reads the screen identifier, store area identifier, shelf location identifier, most recent local phase table, most recent WiFi access result and task type stored on the local machine, and keeps the WiFi communication module in an unconnected state, only turning on the Bluetooth communication module for low-power monitoring, and generates the basic scheduling status record of the retail screen.

[0039] AP stands for wireless access point. The WiFi communication module is used by the retail screen to connect to the AP and interact with edge network nodes or servers. The local phase table includes at least the last target WiFi wake-up phase, the last estimated WiFi usage duration, the last corresponding AP identifier, the last WiFi access result, and the phase generation time. The WiFi wake-up phase represents the relative time position of the retail screen's planned WiFi communication module activation within a scheduling cycle, and does not represent the physical electrical signal phase.

[0040] If the retail screen does not read a valid local phase table, the retail screen will be marked as a first-time network access and the first-time network access mark will be written into the basic scheduling status record. If the most recent WiFi access result is a failure, the failure reason mark will be written into the basic scheduling status record. The failure reason mark includes AP association failure, address acquisition failure, edge network connection failure, or server connection failure.

[0041] The types of tasks to be executed include server registration, material verification, material difference request, status reporting, and low-frequency online confirmation. The retail screen determines whether there is an initial basis for the existence of WiFi access requirements in this round based on the type of task to be executed. Thus, the basic scheduling status record output by S110 saves the identity, location, historical access status, and task requirements of this retail screen, and provides local input for S120 to receive the regional Bluetooth scheduling context and S130 to generate the scheduling constraint set.

[0042] For example, if a retail screen is powered on again after a power outage, and it reads that the last target WiFi wake-up phase was 18 seconds after the start of the scheduling cycle, the last estimated WiFi usage time was 4 seconds, the last WiFi access result was successful, and the task to be executed is only low-frequency online confirmation, then the retail screen will not be marked as an emergency access object in the basic scheduling status record to avoid prematurely activating the WiFi communication module when the AP pressure level is high.

[0043] It should be noted that the WiFi and Bluetooth communication modules in this retail screen are implemented based on a single-chip time division multiplexing (TDM) architecture or an independent dual-antenna architecture. When the WiFi communication module remains in an unconnected state, the system will fully allocate radio frequency resources to the Bluetooth communication module to ensure the reliability of Bluetooth monitoring and broadcasting.

[0044] S120: The retail screen receives the AP pressure status level, WiFi access window, task urgency level, WiFi wake-up phase information of adjacent retail screens, and the most recent access result of adjacent retail screens broadcast by the gateway, edge network node, or adjacent retail screens in the same store area through the Bluetooth communication module, and obtains the area Bluetooth scheduling context.

[0045] Edge network nodes are set up on the local network side of the store. They use Simple Network Management Protocol (SNMP) to call the AP management interface to obtain the number of currently associated retail screens. They use System Log Protocol (Syslog) to parse the store gateway logs and AP controller logs to extract the average AP association time and average address time. They also combine the historical WiFi access results of the retail screens to calculate the WiFi access failure rate, and then calculate the AP pressure value. After converting the AP pressure value into an AP pressure status level, it is broadcast to the retail screens in the same store area via Bluetooth communication module or gateway.

[0046] AP pressure value is calculated according to the following formula:

[0047]

[0048] Where P represents the AP stress value; N represents the number of currently associated retail screens; This indicates the maximum number of retail screens that an AP can be associated with; This indicates the average AP association time within the most recent statistical period; This indicates the maximum preset time limit for association; This indicates the average address retrieval time within the most recent statistical period; This indicates the maximum time limit for retrieving the preset address; This indicates the WiFi access failure rate within the most recent statistical period; , , , This represents the weights, and the sum of the four is 1.

[0049] In a preferred embodiment, to accurately measure the instantaneous concurrent pressure of the AP, the above weights are respectively set to: Take 0.4, Take 0.3, Take 0.2, Take 0.1.

[0050] The above data comes from AP operation logs, edge network node collection records, and WiFi access results transmitted back from retail screens, and does not use manual estimates. AP stress levels are divided into low-pressure, medium-pressure, and high-pressure states according to AP stress values, which are used to subsequently limit the WiFi access window.

[0051] Edge network nodes also divide WiFi access windows at fixed scheduling intervals and calculate the remaining access capacity of each window based on the declared phase occupancy segments:

[0052]

[0053] in, This represents the remaining access capacity of the i-th WiFi access window; This represents the number of retail screens allowed to access the network in the i-th WiFi access window; This indicates the number of WiFi access windows already occupied by adjacent retail screens in the i-th WiFi access window; i represents the sequence number of the WiFi access window. When When the value is greater than 0 and the AP pressure status level is not high pressure, the window is marked as an available WiFi access window; when... When the value is 0 or the AP pressure status level is high pressure, this window is marked as a prohibited access window.

[0054] For example, a 60-second scheduling cycle is divided into 12 5-second windows. If a window allows 5 retail screens to access and has received 4 phase occupancy segments, then the remaining access capacity of that window is 1, and it still belongs to the available WiFi access window. If 5 phase occupancy segments have been received, then the window is marked as a prohibited access window. The area Bluetooth scheduling context output by S120 serves as the data source for S130 to generate the scheduling constraint set.

[0055] S130: Based on the basic scheduling status record obtained in S110 and the regional Bluetooth scheduling context obtained in S120, the retail screen determines the necessity of WiFi access for the current period and forms a set of scheduling constraints.

[0056] The necessity of WiFi access is determined jointly based on the type of task to be executed, the urgency level of the task, the local phase table, the result of the most recent WiFi access, the AP stress level, the WiFi access window, and the narrowband IoT fallback status. When the type of task to be executed is server registration, material verification, material difference request, or status reporting, and the AP stress level is not high, the retail screen is determined to participate in the WiFi access of the current cycle. When the type of task to be executed is only low-frequency online confirmation, and the AP stress level is high, the retail screen is determined not to participate in the WiFi access of the current cycle, and is allowed to send low-frequency fallback status through narrowband IoT.

[0057] Narrowband IoT is used to send low-frequency online confirmations, abnormal statuses, or phase confirmations when WiFi access is temporarily unavailable or edge network nodes are temporarily unreachable. It is not used to carry out material download tasks.

[0058] The timing meaning of the WiFi wake-up phase is determined by the following formula:

[0059]

[0060] Where A represents the WiFi wake-up phase; This indicates the planned activation time of the WiFi communication module for retail displays; Indicates the start time of the current scheduling cycle.

[0061] If the scheduling cycle starts at 10:00:00, and the retail screen plans to activate its WiFi communication module at 10:00:18, then the WiFi wake-up phase of this retail screen is 18 seconds. The scheduling constraint set includes the available WiFi access window, the prohibited access window, the task urgency level, the AP stress level, the WiFi wake-up phase already occupied by adjacent retail screens, the data source marker, the valid time marker, and a marker indicating whether this retail screen is allowed to perform low-frequency fallback status transmission via narrowband IoT.

[0062] Retail screens discard AP pressure status levels, WiFi access windows, and WiFi wake-up phase information of adjacent retail screens that have not been updated within the valid time to prevent expired data from participating in subsequent calculations. The scheduling constraint set output by S130 is directly used as input for S210 to generate candidate WiFi wake-up phases, and is further used by S220 to estimate the expected WiFi occupancy duration and by S230 to form phase occupancy segments.

[0063] S2 specifically includes the following sub-steps:

[0064] In S210, when the retail screen generates candidate WiFi wake-up phases based on the scheduling constraint set formed in S130, it first reads the available WiFi access window, the prohibited access window, the AP pressure status level, the task urgency level, the WiFi wake-up phases already occupied by adjacent retail screens, the data source marker, and the valid time marker, and then removes window data that exceeds the valid time and adjacent retail screen phase data. A candidate WiFi wake-up phase refers to the relative time position at which the retail screen plans to activate its WiFi communication module within the current scheduling cycle; its generation process includes window selection and phase selection within the window.

[0065] The retail screen first calculates a window score for each available WiFi access window. The window score is determined according to the following formula:

[0066]

[0067] in, This represents the window score of the i-th available WiFi access window; i represents the index of the available WiFi access window. This represents the normalized value of the remaining access capacity in the i-th available WiFi access window; This represents the historical access success rate of this retail screen within the time period of the i-th available WiFi access window; This indicates the task urgency matching value; This represents the phase occupancy density of adjacent retail screens within the i-th available WiFi access window.

[0068] , , , These represent weights, and all are non-negative. In a preferred embodiment, to balance AP capacity and emergency task requirements, the above weights are configured as follows: Take 0.4, Take 0.2, Take 0.3, The value is set to 0.1. The normalized value of the remaining access capacity mentioned above is derived from the remaining access capacity of the WiFi access window in S130. The historical access success rate is derived from the local phase table and the most recent WiFi access result. The task urgency matching value is derived from the type of task to be executed. The phase occupancy density is derived from the WiFi wake-up phases already occupied by adjacent retail screens. The available WiFi access window with the highest window score and not belonging to the prohibited access window is selected as the candidate window by the retail screen.

[0069] After selecting a candidate window, the retail screen determines the candidate WiFi wake-up phase within the candidate window, specifically calculated according to the following formula:

[0070]

[0071] in, Indicates the candidate WiFi wake-up phase; Indicates the starting phase of the i-th available WiFi access window; M represents the integer value converted from the identifier of this retail screen. The specific conversion method is: extract the last four bytes of the hexadecimal characters of the MAC address of this retail screen and directly convert them into the corresponding decimal integer as the value of M; This represents the number of phase slots that can be allocated within the i-th available WiFi access window; This indicates the time interval between two adjacent phase slots; This represents the modulo operation. By using screen identifiers to participate in the modulo operation, a stable candidate WiFi wake-up phase can be formed for the same retail screen under the same set of scheduling constraints.

[0072] For example, if an available WiFi access window starts at the 20th second of the current scheduling cycle, with a window length of 5 seconds, a phase slot interval of 1 second, and 5 allocable phase slots, and the integer value obtained from the conversion of a retail screen identifier is modulo 3 when divided by 5, then the candidate WiFi wake-up phase is at the 23rd second. The candidate WiFi wake-up phase output by S210 is entered into S220 to estimate the expected WiFi occupancy duration, and then into S230 to form a phase occupancy segment.

[0073] Based on the candidate WiFi wake-up phase output by S210, the type of task to be executed in S130, the most recent WiFi access result, material verification requirements, status reporting requirements, AP processing capabilities fed back by edge network nodes, and local historical transmission records, the retail screen estimates the expected WiFi access duration for this WiFi connection. The expected WiFi access duration refers to the time required from when the retail screen starts its WiFi communication module and connects to the AP until it completes the server registration, material verification, material difference request, or status reporting task and releases the WiFi access resources.

[0074] The estimated WiFi usage time consists of basic connection time, service data transmission time, and retry compensation time, calculated using the following formula:

[0075]

[0076] in, Indicates the estimated duration of WiFi usage; L represents the basic connection time; L represents the amount of data that needs to be transmitted via WiFi in this task; V represents the effective transmission rate recorded when this retail screen last successfully connected. This indicates the time spent on retry compensation.

[0077] The basic connection time is derived from the AP association time, address acquisition time, and edge network connection time in the most recent statistical period; the amount of data to be transmitted via WiFi in this task is derived from the data volume record corresponding to the type of task to be executed; the effective transmission rate is derived from the WiFi access process record formed when the retail screen successfully executed WiFi service recently; the retry compensation time is derived from the reason for the most recent WiFi access failure and the historical failure rate.

[0078] For retail screens that only perform low-frequency online confirmation and whose AP pressure status level is high, the S220 does not configure them to immediately occupy WiFi access resources. Instead, it marks their expected WiFi usage time as low priority access and allows them to send low-frequency fallback status via narrowband IoT. Narrowband IoT is only used to send screen identification, store area identification, online status, abnormal status, or phase confirmation status, and is not used for the main process of material download, material difference file transfer, and server registration.

[0079] For example, if a retail screen only needs to report its status, with a data size of 2KB, a basic connection time of 1.2s, an effective transmission rate of 200KB / s, and a retry compensation time of 0s, then the estimated WiFi usage time is recorded as 2s at the smallest granularity. If a retail screen needs to execute a material difference request, with a data size of 600KB, a basic connection time of 1.5s, an effective transmission rate of 150KB / s, and a 1s retry compensation time corresponding to the most recent address acquisition failure, then the estimated WiFi usage time is 6.5s, and recorded as 7s at the scheduling granularity. The estimated WiFi usage time output by S220 is entered into S230, and together with the candidate WiFi wake-up phase, determines the time range within which the retail screen plans to occupy WiFi access resources.

[0080] S230 and the retail screen combine the candidate WiFi wake-up phase output by S210, the estimated WiFi usage duration output by S220, and the local data already generated by S110 and S130 into a phase usage segment, and mark it as a phase usage segment to be broadcast in the local cache. The phase usage segment includes at least the screen identifier, store area identifier, shelf location identifier, corresponding AP identifier, candidate WiFi wake-up phase, estimated WiFi usage duration, task urgency level, most recent WiFi access result, generation time, validity period, data source marker, and a marker indicating whether narrowband IoT fallback status feedback is allowed.

[0081] Among them, screen identifiers are used to distinguish different retail screens, store area identifiers and shelf location identifiers are used to limit the Bluetooth phase negotiation range, corresponding AP identifiers are used to determine the subsequent access object, candidate WiFi wake-up phase and expected WiFi occupancy duration are used by S320 to determine whether the planned occupancy time range of this retail screen overlaps with that of adjacent retail screens, task urgency level and most recent WiFi access result are used by S410 to determine the fallback object after a phase conflict occurs, generation time and validity time are used by S310 to remove expired phase occupancy segments, data source markers are used to confirm whether the segment is generated based on a valid regional Bluetooth scheduling context, and whether narrowband IoT fallback status backhaul is allowed is used by S430 and S520 to perform low-frequency status backhaul when the edge network node is unavailable or WiFi access fails.

[0082] After the phase occupancy segment is formed, the retail screen does not immediately turn on the WiFi communication module, but enters the Bluetooth broadcast waiting state, waiting for the S310 to broadcast the phase occupancy segment to the adjacent retail screen through the Bluetooth communication module, and receiving the phase occupancy segment broadcast by the adjacent retail screen.

[0083] For example, a phase occupancy segment includes: screen identifier A102, store area identifier R03, shelf location identifier F2-05, corresponding AP identifier AP-2, candidate WiFi wake-up phase of 23s, estimated WiFi occupancy duration of 4s, task urgency level of medium, most recent WiFi access result of success, generation time of the 8th second of the current scheduling cycle, and effective time of 10s. This segment indicates in subsequent S320 that this retail screen plans to occupy WiFi access resources from the 23rd to the 27th second. If an adjacent retail screen has declared a phase occupancy segment from the 22nd to the 25th second, then S330 generates a phase conflict result, and S410-S430 performs phase backoff correction.

[0084] S3 specifically includes the following sub-steps:

[0085] After entering the Bluetooth phase negotiation phase, S310 and the retail screen determine the area broadcast period based on the phase occupancy segment to be broadcast formed in S230, and send the phase occupancy segment to be broadcast within the area broadcast period through the Bluetooth communication module, while receiving the phase occupancy segment sent by the adjacent retail screen.

[0086] The regional broadcast period is determined by the effective time of the phase occupancy segment, the AP pressure status level, and the broadcast parameters sent by the edge network nodes, and is calculated according to the following formula:

[0087]

[0088] in, Indicates the regional broadcast cycle; Indicates the minimum broadcast period; Indicates the maximum broadcast period; This indicates the effective time of the phase occupancy segment; K represents the broadcast correction factor, max represents the maximum value function, and min represents the minimum value function. The higher the AP pressure status level, the larger the broadcast correction factor value. For example, K is 1.0 when the AP pressure status level is low, 1.2 when it is medium, and 1.5 when it is high.

[0089] The effective time of the aforementioned phase occupancy segment comes from S230, the AP stress status level comes from S130, and the broadcast parameters come from the edge network node or gateway configuration records. After receiving the phase occupancy segment from an adjacent retail screen, the retail screen sequentially performs store area identification verification, corresponding AP identification verification, effective time verification, screen identification deduplication verification, and data source mark verification.

[0090] Fragments whose store area identifiers are inconsistent with those on this retail screen will not participate in this round of phase conflict judgment; fragments with different corresponding AP identifiers and not belonging to the same AP load group will not participate in this round of phase conflict judgment; fragments whose generation time exceeds the valid time will be removed; when there are multiple fragments with the same screen identifier, the fragment with the latest generation time and valid data source tag will be retained. An AP load group refers to a set of APs pre-configured by edge network nodes that share the same store backhaul link, the same AP controller, or the same wireless coverage area load statistics caliber.

[0091] After the above filtering, the retail screens form a neighborhood phase segment set. The neighborhood phase segment set is used to represent the time distribution of adjacent retail screens facing the same AP or the same AP load group within the same store area, and is used as the input for S320 to determine phase overlap.

[0092] For example, if the store area of ​​this retail screen is identified as R03 and the corresponding AP is identified as AP-2, and three phase occupancy segments are received, the first segment from R03 and corresponding to AP-2 and within the valid time will be retained; the second segment from R04 will be discarded; and the third segment from R03 but whose generation time exceeds the valid time will be discarded. This avoids irrelevant or expired segments from affecting subsequent phase judgment.

[0093] S320: The retail screen compares the phase occupancy segment of its own retail screen with the set of neighboring phase segments formed in S310 one by one to determine whether the time range in which the retail screen plans to occupy WiFi access resources overlaps with the time range in which adjacent retail screens plan to occupy WiFi access resources.

[0094] The time range of this retail screen is determined by the candidate WiFi wake-up phase and the expected WiFi usage duration. The time range of adjacent retail screens is determined by the candidate WiFi wake-up phase and the expected WiFi usage duration within their phase usage segments. The phase overlap duration is calculated using the following formula:

[0095]

[0096] in, This indicates the duration of phase overlap between this retail screen and the j-th adjacent retail screen; Indicates the candidate WiFi wake-up phase for this retail screen; This indicates the estimated WiFi usage time for this retail screen; This represents the candidate WiFi wake-up phase for the j-th adjacent retail screen; This represents the expected WiFi usage time for the j-th adjacent retail screen; j represents the index of the adjacent retail screen in the neighborhood phase segment set.

[0097] When the phase overlap duration is greater than 0, it is determined that there is a phase overlap between this retail screen and the adjacent retail screen; when the phase overlap duration is equal to 0, it is determined that there is no phase overlap. If a phase overlap exists, the retail screen reads the screen identifier, task urgency level, most recent WiFi access result, corresponding AP identifier, and overlap time range corresponding to the adjacent retail screen that is overlapping, forming a phase overlap record. The phase overlap record includes at least the conflicting screen identifier, phase overlap duration, overlap start time, overlap end time, task urgency level of the adjacent retail screen, and most recent WiFi access result of the adjacent retail screen, and serves as the basis for S330 to generate phase conflict results.

[0098] For example, if the candidate WiFi wake-up phase of this retail screen is 23s and the expected WiFi usage time is 4s, then this retail screen plans to use 23s to 27s; if the adjacent retail screen plans to use 22s to 25s, then the phase overlap time is 2s, and a phase overlap record should be formed.

[0099] S330 and the retail screen generate phase conflict results based on the phase overlap record formed in S320. When there is no phase overlap record, the phase conflict result is marked as conflict-free, and the candidate WiFi wake-up phase of this retail screen is used as the target WiFi wake-up phase to be confirmed. Subsequently, it enters S430 to write to the local phase table, and the WiFi communication module remains in an unconnected state until the corresponding access time is reached. When there is a phase overlap record, the phase conflict result is marked as conflicted, and a list of conflicting screens, conflict time range, and conflict severity are generated.

[0100] The severity of a conflict is determined by the sum of phase overlap durations, the number of conflict screens, the AP stress status level, and the highest task urgency among the conflict screens, calculated using the following formula:

[0101]

[0102] Where G represents the severity of the conflict; This represents the sum of the phase overlap durations between this retail screen and all adjacent retail screens; This indicates the estimated WiFi usage time for this retail screen; This indicates the number of adjacent retail screens that overlap with this retail screen in phase; This indicates the maximum number of screens that can conflict. This indicates the numerical value corresponding to the AP pressure status level; This indicates the value corresponding to the highest task urgency among the adjacent retail screens where the conflict occurred; , , , These represent weights, and all are non-negative numbers.

[0103] In a preferred embodiment, to prioritize high-urgency tasks and suppress large-scale conflicts, the aforementioned weights are set as follows: Take 0.3, Take 0.2, Take 0.2, Take 0.3. Wherein, the value corresponding to the task urgency level... The values ​​are: 3 for high urgency, 2 for medium urgency, and 1 for low urgency.

[0104] The phase conflict results should include at least the retail screen identifier, candidate WiFi wake-up phase, expected WiFi occupancy duration, conflict status, list of conflicting screens, phase overlap duration for each conflicting screen, conflict time range, conflict severity, corresponding AP identifier, task urgency level, and result generation time.

[0105] The conflict status is used by S410 to determine whether to initiate a backoff correction; the conflict screen list and task urgency level are used by S410 to identify the backoff target; the conflict time range is used by S420 to avoid conflicted time periods; the conflict severity is used by S420 to determine the delay range; and the result generation time is used by S430 to determine whether the phase conflict result is still valid. Therefore, the phase conflict result output by S330 can directly support subsequent phase backoff correction and local phase table writing.

[0106] S4 specifically includes the following sub-steps:

[0107] S410. When the phase conflict result output by S330 indicates a conflict, the retail screen does not directly activate the WiFi communication module. Instead, it determines whether the retail screen needs to perform phase backoff correction based on the conflict screen list, conflict time range, conflict severity, task urgency level, most recent WiFi access result, and local phase table in the phase conflict result.

[0108] To avoid relying solely on the urgency of a single task for decision-making, each retail screen calculates its own phase retention priority value and that of adjacent retail screens in the conflicting screen list. The phase retention priority value is determined according to the following formula:

[0109]

[0110] in, This represents the phase retention priority value of the x-th retail screen; x represents the retail screen number participating in the same phase conflict judgment. This represents the numerical value corresponding to the task urgency level of the x-th retail screen; This represents the compensation value corresponding to the most recent WiFi access failure of the x-th retail screen; This represents the compensation value corresponding to the number of historical access failures for the x-th retail screen; This represents the yield tendency value corresponding to the most recent successful WiFi access for the xth retail screen, when it is currently only performing a regular status report. , , , These represent weights, and all are non-negative numbers.

[0111] In a specific application scenario, to ensure that retail screens that have failed multiple times can be connected first, the recommended values ​​for the above weights are: Take 0.4, Take 0.3, Take 0.2, Take 0.1.

[0112] The above task urgency level comes from the phase occupancy segment formed by S230, the most recent WiFi access result and the number of historical access failures come from the basic scheduling status record and local phase table of S110, and the conflict screen list and conflict severity come from the phase conflict result of S330.

[0113] When the phase retention priority value of this retail screen is lower than the phase retention priority value of any adjacent retail screen in the conflict screen list, it is determined that this retail screen will perform a backoff correction; when the phase retention priority value of this retail screen is not lower than the phase retention priority value of all adjacent retail screens in the conflict screen list, it is determined that this retail screen will retain the candidate WiFi wake-up phase, and the candidate WiFi wake-up phase will be entered into S430 as the target WiFi wake-up phase to be confirmed.

[0114] If this retail screen performs a backoff correction, phase backoff parameters are generated. These parameters include the backoff direction, minimum backoff interval, maximum number of backoffs, avoidance time range, number of extension windows, and backoff reason flags. The avoidance time range is derived from the conflict time range in S330, and the backoff reason flags include at least low urgency backoff, normal status reporting backoff, historical access success backoff, and high conflict severity backoff.

[0115] For example, if this retail screen only performs low-frequency online confirmation and the most recent WiFi access was successful, while the adjacent retail screen performs material difference request and the most recent address acquisition failed, then the phase retention priority value of the adjacent retail screen is higher than that of this retail screen, and this retail screen generates phase backoff parameters and enters S420.

[0116] Based on the phase backoff parameters generated by S410, the retail screen in S420 re-searches for the target WiFi wake-up phase within the currently available WiFi access window. During the search, the retail screen starts with the candidate WiFi wake-up phases formed by S210, generates candidate WiFi wake-up phases slot by slot according to the minimum backoff interval, and recalculates the planned WiFi access resource occupation time range for each candidate WiFi wake-up phase; this time range is determined by the candidate WiFi wake-up phase and the expected WiFi occupation time formed by S220.

[0117] The candidate WiFi wake-up phase is determined according to the following formula:

[0118]

[0119] in, This represents the candidate WiFi wake-up phase obtained in the nth search; Indicates the candidate WiFi wake-up phase; n represents the number of backoff searches; This indicates the minimum yield interval.

[0120] For each candidate WiFi wake-up phase obtained, the retail screen compares the time range corresponding to the candidate WiFi wake-up phase with the set of neighboring phase segments according to the phase overlap duration calculation method in S320. When the phase overlap duration is 0, the candidate WiFi wake-up phase does not fall into the prohibited access window, and the expected WiFi occupancy time corresponding to the candidate WiFi wake-up phase does not exceed the remaining time of the currently available WiFi access window, the candidate WiFi wake-up phase is determined as the target WiFi wake-up phase.

[0121] If no suitable candidate WiFi wake-up phase is found within the maximum number of backoff attempts, or if the remaining time of the currently available WiFi access window is insufficient to cover the expected WiFi occupancy time, the retail screen reads the available WiFi access window, prohibited access window, AP stress status level, remaining access capacity, and phase occupancy density from S130, and postpones the target WiFi wake-up phase to the next available WiFi access window.

[0122] The delayed target WiFi wake-up phase is determined according to the following formula:

[0123]

[0124] in, Indicates the target WiFi wake-up phase; This indicates the starting phase of the kth next available WiFi access window; k represents the sequence number of the next available WiFi access window; m represents the sequence number of the phase slot selected in the kth next available WiFi access window. This indicates the time interval between two adjacent phase slots.

[0125] The next available WiFi access window should meet the following criteria: it should not be a blocked window, its remaining access capacity should be greater than 0, the AP's stress level should not be high, and its phase occupancy density should be lower than the preset density. If multiple next available WiFi access windows exist, the window with the larger remaining access capacity, higher historical access success rate, and lower phase occupancy density should be selected first.

[0126] For example, the candidate WiFi wake-up phase for this retail screen is 23s, the expected WiFi usage time is 4s, the conflict time range is 23s to 25s, and the minimum backoff interval is 1s. If the 24s and 25s still overlap with the adjacent retail screen, while the 26s to 30s do not overlap and belong to the available WiFi access window, then the 26s will be determined as the target WiFi wake-up phase. If there is no available phase slot in the current window and the next window is a prohibited access window, then the process will continue to the next available WiFi access window.

[0127] S430 and the retail screen will write the target WiFi wake-up phase generated by S420, or the candidate WiFi wake-up phase confirmed and retained in S410, into the local phase table, and send the phase confirmation status to adjacent retail screens, gateways or edge network nodes through the Bluetooth communication module.

[0128] The local phase table after writing includes at least the screen identifier, store area identifier, shelf location identifier, corresponding AP identifier, target WiFi wake-up phase, estimated WiFi usage time, task urgency level, phase generation time, effective time, phase status, retreat reason marker, phase confirmation status, whether pending confirmation execution is allowed, data source marker, and whether narrowband IoT fallback status return is allowed.

[0129] The phase status includes a conflict-free confirmation status and a yield confirmation status; the yield reason marker comes from the phase yield parameter of S410; the phase confirmation status is used to indicate whether the target WiFi wake-up phase has been communicated to the adjacent retail screen, gateway or edge network node through the Bluetooth communication module; the valid time is used by S510 to determine whether the WiFi communication module can be turned on according to the local phase table.

[0130] When the phase confirmation status is pending confirmation, the target WiFi wake-up phase is still within the valid time, the AP pressure status level has not reached the high pressure state, and the task urgency level is not lower than the medium level, the flag indicating whether pending confirmation is allowed to be executed will be set to allowed; otherwise, it will be set to disallowed.

[0131] After a retail screen sends a phase confirmation status, if it receives confirmation feedback from an adjacent retail screen, gateway, or edge network node within two regional broadcast cycles, it marks the phase confirmation status as confirmed. If no confirmation feedback is received, it marks the phase confirmation status as pending confirmation and continues to keep the WiFi communication module in an unconnected state until the access time corresponding to the target WiFi wake-up phase is reached, at which point it re-verifies the validity time of the local phase table and whether the pending confirmation flag is allowed.

[0132] Bluetooth phase confirmation serves as the standard feedback method. When the edge network node is unavailable, Bluetooth broadcast confirmation fails repeatedly, and there is a risk of prolonged unconfirmation on the retail screen, the retail screen sends a low-frequency fallback status via narrowband IoT. This low-frequency fallback status only includes screen identification, store area identification, phase confirmation status, abnormal status, and time stamp; it does not include material data and does not replace the main WiFi business process. If the task to be executed is a material difference request, narrowband IoT only sends a waiting WiFi access status; if the task to be executed is a low-frequency online confirmation, narrowband IoT sends an online confirmation status.

[0133] The local phase table and phase confirmation status output by S430 directly serve as the basis for S510 to read the target WiFi wake-up phase, activate the WiFi communication module, and connect to the AP. At the same time, they serve as the basic data for S530 to correct the local phase table for the next round based on the WiFi access results.

[0134] S5 specifically includes the following sub-steps:

[0135] The S510 and retail screen continuously read the local phase table written by the S430 and perform validity checks before reaching the access time corresponding to the target WiFi wake-up phase. Validity checks include: verifying whether the local phase table is within a valid time period; verifying whether the phase confirmation status is confirmed or whether the flag indicating pending confirmation is allowed; verifying whether the AP pressure status level recently received by the Bluetooth communication module has not reached a high-pressure state; and verifying whether the access time corresponding to the target WiFi wake-up phase still falls within the available WiFi access window.

[0136] The activation time of the WiFi communication module is determined according to the following formula:

[0137]

[0138] in, Indicates the activation time of the WiFi communication module; Indicates the start time of the current scheduling period; This indicates the target WiFi wake-up phase.

[0139] The start time of the current scheduling cycle is derived from the local clock of the retail screen or the cycle start time broadcast by the edge network node, and the target WiFi wake-up phase is derived from the local phase table written by S430. If the validity verification passes, the retail screen starts the WiFi communication module at the WiFi communication module's start time and connects to the AP according to the corresponding AP identifier in the local phase table; if the local phase table has expired, the AP pressure status level has changed to high pressure, the target WiFi wake-up phase falls into the prohibited access window, or the "Allow execution" flag is set to "Not allowed", the retail screen does not start the WiFi communication module, returns to the Bluetooth hold state, and waits for the next round of Bluetooth group phase breakage scheduling.

[0140] During the access process, the retail screen generates a WiFi access process record. The WiFi access process record includes at least the screen identifier, store area identifier, corresponding AP identifier, target WiFi wake-up phase, actual WiFi start time, AP association result, AP association time, address acquisition result, address acquisition time, edge network connection result, server connection result, failure stage, failure reason, actual WiFi occupancy start time and actual WiFi occupancy end time.

[0141] AP association results and AP association time are derived from WiFi communication module driver logs; address acquisition results and address acquisition time are derived from network protocol stack records; edge network connection results are derived from the handshake results between the retail screen and the edge network node; server connection results are derived from application layer response records; and the actual WiFi usage start and end time is derived from the retail screen's local clock.

[0142] For example, if the current scheduling cycle starts at 10:00:00 and the target WiFi wake-up phase is 26 seconds, the retail screen will complete the validity verification before 10:00:26. If the verification passes, the retail screen will activate the WiFi communication module and record the AP association, address acquisition, and edge network connection processes to record the processing results of each stage of WiFi access and provide data basis for S530 to correct the local phase table.

[0143] After successfully connecting to WiFi, the S520 and retail screen perform tasks such as server registration, material verification, material difference request, or status reporting according to the task type read by the S110, and prioritize completing near-end data interaction with edge network nodes.

[0144] The server registration task is considered successful when the edge network node or server returns a registration confirmation; the material verification task is considered successful when the local material version number matches the target material version number and the material segment verification is completed; the material difference request task is considered successful when the missing segment list is confirmed to be received by the edge network node or server, or when the missing segments are downloaded; the status reporting task is considered successful when the edge network node or server returns a receipt confirmation.

[0145] The completion rate of material segment verification is determined by the following formula:

[0146]

[0147] in, This indicates the completion rate of material segment verification; This indicates the number of media segments that have passed verification; This indicates the total number of segments in the target material.

[0148] The number of media fragments is derived from the media summary issued by the edge network node, the local cache record of the retail screen, and the target media version list. When the media fragment verification completion rate is equal to 1, the media verification task is considered complete; when the media fragment verification completion rate is less than 1, a missing fragment list is generated and written into the task execution result for media difference requests in the current or next round of WiFi access.

[0149] If WiFi access fails, the retail screen does not immediately restart the WiFi communication module. Instead, it keeps the Bluetooth communication module active and receives the latest WiFi access result from adjacent retail screens under the same AP or the same AP load group via Bluetooth. When multiple adjacent retail screens experience the same failure stage, it is determined to be an abnormal regional AP load, and the retail screen enters Bluetooth hold-up mode. When only the retail screen fails and the task urgency level is high, the retail screen enters the next round of phase fragmentation scheduling and writes the failure stage and failure reason into the local phase table. Narrowband IoT is only enabled during low-frequency online confirmation, abnormal states, waiting for WiFi access status, or phase confirmation status feedback. It is not used for material fragmentation transmission and does not replace the server registration main process.

[0150] For example, if the target material has 20 segments and 18 segments have passed verification locally, the segment verification completion rate is 0.9, and the retail screen generates a list of missing segments. If multiple retail screens in the same store area fail to obtain the address at the same time, the retail screen will stop the current reconnection and enter Bluetooth hold mode to avoid increasing the AP pressure again.

[0151] Based on the WiFi access process record formed by S510 and the task execution result formed by S520, the S530 and retail screen generate WiFi access results and feed them back to adjacent retail screens, gateways or edge network nodes through the Bluetooth communication module.

[0152] WiFi access results should include at least the screen identifier, store area identifier, corresponding AP identifier, target WiFi wake-up phase, actual WiFi start-up time, AP association result, address acquisition result, edge network connection result, server connection result, task execution result, failure stage, failure reason, actual WiFi usage time, whether Bluetooth hold-up mode is entered, whether narrowband IoT fallback backhaul is enabled, result generation time, and next round scheduling suggestion flag.

[0153] The actual WiFi usage time is determined by the following formula:

[0154]

[0155] in, Indicates the actual WiFi usage time; This indicates the time when the WiFi communication module is turned on and begins connecting to the AP; This indicates the time when the WiFi task is completed, fails, exits, or releases WiFi access resources.

[0156] The retail screen adjusts the estimated WiFi usage time for the next round based on the actual WiFi usage time. The adjustment rule is determined according to the following formula:

[0157]

[0158] in, This indicates the revised estimated WiFi usage time; This indicates the estimated WiFi usage time obtained by S220. Indicates the actual WiFi usage time; This represents the smoothing coefficient, with a value ranging from 0 to 1.

[0159] If the access is successful, the retail screen updates the effective transmission rate based on the actual data volume and business data transmission time of this task, and writes the effective transmission rate, the corrected estimated WiFi usage time, the task execution result, and the actual WiFi usage time into the local phase table. If the access fails, the retail screen writes the failure stage, the reason for failure, whether it entered Bluetooth hold-up state, and whether it enabled narrowband IoT fallback backhaul into the local phase table, and increases the failure compensation criteria in the next round of phase hold-up priority. The edge network node updates the AP stress status level based on the received WiFi access result, and the retail screen participates in the next round of Bluetooth group phase fragmentation scheduling based on the updated local phase table.

[0160] For example, if the estimated WiFi usage time is 7 seconds and the actual WiFi usage time is 5 seconds, with a smoothing coefficient of 0.6, the corrected estimated WiFi usage time is 6.2 seconds. This will be recorded at the scheduling granularity when the next phase usage segment is formed. If the estimated usage time is 4 seconds but the actual usage time is 9 seconds, the estimated WiFi usage time will be increased in the next round to avoid the retail screen underestimating the WiFi usage time and causing phase conflict with adjacent retail screens again.

[0161] All the above formulas are performed using dimensionless numerical calculations; the relevant formulas are based on empirical models that approximate the real situation, obtained through extensive data collection and software simulation fitting. The preset parameters and thresholds involved in the formulas can be conventionally set and adjusted by those skilled in the art according to the physical constraints of the actual application scenario.

[0162] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0163] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0164] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for Bluetooth-based WiFi scheduling in retail screens to alleviate AP pressure, characterized in that, Includes the following steps: S1. After the retail screen is powered on, read the screen identifier, store area identifier, local phase table, the most recent WiFi access result and the type of task to be executed, keep the WiFi communication module in an unconnected state, and enable the Bluetooth communication module to receive the AP pressure status level, WiFi access window, task urgency level and WiFi wake-up phase information to form a set of scheduling constraints. S2. Based on the scheduling constraint set, generate candidate WiFi wake-up phases within the available WiFi access window, and estimate the expected WiFi occupancy time based on the type of task to be executed, historical transmission records, and AP processing capacity to form phase occupancy segments. S3. Broadcast the phase occupancy segment of this retail screen and receive the phase occupancy segment of adjacent retail screens through the Bluetooth communication module to form a set of neighborhood phase segments, determine phase overlap and generate phase conflict results; S4. When the phase conflict result is that there is a conflict, generate the target WiFi wake-up phase based on the conflict severity, task urgency level, the most recent WiFi access result and the local phase table, and write it into the local phase table.

2. The retail screen Bluetooth-based WiFi scheduling method for alleviating AP pressure according to claim 1, characterized in that, Also includes: S5. After the validity verification is passed at the access time corresponding to the target WiFi wake-up phase, the WiFi communication module is turned on to access the AP and execute the corresponding task, the WiFi access result is fed back, and the local phase table is updated.

3. A retail screen Bluetooth-based WiFi scheduling method for alleviating AP pressure according to claim 1, characterized in that, S1 specifically includes: After the retail screen is powered on, it reads the screen identifier, store area identifier, local phase table, most recent WiFi access result and task type to be executed, keeps the WiFi communication module in an unconnected state, and only enables the Bluetooth communication module to generate a basic scheduling status record. The region's Bluetooth scheduling context is obtained by receiving AP stress status level, WiFi access window, task urgency level, and WiFi wake-up phase information broadcast by edge network nodes, gateways, or adjacent retail screens via the Bluetooth communication module.

4. A method for alleviating AP pressure on retail screens via Bluetooth-based WiFi scheduling, as described in claim 3, is characterized in that... Also includes: Based on the basic scheduling status record and the regional Bluetooth scheduling context, the necessity of access is determined, expired data is removed, and a set of scheduling constraints is formed, which includes available WiFi access windows, prohibited access windows, occupied WiFi wake-up phases, and narrowband IoT fallback flags.

5. A method for Bluetooth-based WiFi scheduling in retail screens to alleviate AP pressure according to claim 1, characterized in that, S2 specifically includes: Based on the scheduling constraint set, read the available WiFi access window, prohibited access window, AP stress status level, task urgency level and occupied WiFi wake-up phase, remove expired data, and generate candidate WiFi wake-up phases in the available WiFi access window with the highest score. Based on the candidate WiFi wake-up phase, the type of task to be executed, the most recent WiFi access result, historical transmission records, and AP processing capacity, estimate the expected WiFi usage time and determine whether narrowband IoT fallback backhaul is allowed. The screen identifier, store area identifier, corresponding AP identifier, candidate WiFi wake-up phase, estimated WiFi occupancy duration, task urgency level, and effective time are combined into a phase occupancy segment for broadcasting and phase overlap judgment.

6. A method for alleviating AP pressure on retail screens via Bluetooth-based WiFi scheduling, as described in claim 1, characterized in that, S3 specifically includes: The regional broadcast cycle is determined based on the effective time of the phase occupancy segment, the AP pressure status level, and the broadcast parameters. The phase occupancy segment of this retail screen is broadcast through the Bluetooth communication module. The received phase occupancy segments of adjacent retail screens are verified by store area identification, corresponding AP identification, effective time, screen identification, and data source mark, forming a set of neighboring phase segments. The phase occupancy segment of this retail screen is compared one by one with the set of phase segments in the neighboring area. Phase overlap is determined based on the candidate WiFi wake-up phase and the expected WiFi occupancy duration, and a phase overlap record is formed.

7. A retail screen Bluetooth-based WiFi scheduling method for alleviating AP pressure according to claim 6, characterized in that, Also includes: Phase conflict results are generated based on phase overlap records. The phase conflict results include conflict status, conflict screen list, conflict time range, and conflict severity.

8. A method for Bluetooth-based WiFi scheduling in retail screens to alleviate AP pressure according to claim 1, characterized in that, S4 specifically includes: When the phase conflict result is that there is a conflict, the phase retention priority value of this retail screen and adjacent retail screens is calculated based on the conflict screen list, conflict time range, conflict severity, task urgency level, most recent WiFi access result and local phase table, and it is determined whether to perform phase backoff correction, and phase backoff parameters are generated when it is determined to perform. Within the currently available WiFi access window, the system searches for candidate WiFi wake-up phases slot by slot based on the phase backoff parameter, avoiding neighboring phase segment sets and prohibited access windows, and generates the target WiFi wake-up phase.

9. A method for alleviating AP pressure on retail screens via Bluetooth-based WiFi scheduling, as described in claim 8, characterized in that, Also includes: Write the target WiFi wake-up phase, estimated WiFi usage time, corresponding AP identifier, task urgency level, phase status, backoff reason marker, and phase confirmation status into the local phase table, and send the phase confirmation status through the Bluetooth communication module.

10. A method for alleviating AP pressure on retail screens via Bluetooth-based WiFi scheduling, as described in claim 2, characterized in that, S5 specifically includes: The retail screen reads the local phase table and verifies the valid time, phase confirmation status, AP pressure status level, and available WiFi access window before the access time corresponding to the target WiFi wake-up phase. After the verification is successful, the WiFi communication module is activated to access the AP, and a WiFi access process record is generated. After successful WiFi access, perform tasks such as server registration, material verification, material difference request, or status reporting according to the type of task to be executed. If WiFi access fails, keep the Bluetooth communication module enabled and enter the next round of phase breakage scheduling or Bluetooth hold status. The WiFi access result is generated based on the WiFi access process record and task execution result, fed back through the Bluetooth communication module, and the local phase table is corrected.

Images