A retail screen WiFi control method based on Bluetooth smart scheduling

Abstract

This invention provides a retail screen WiFi control method based on Bluetooth intelligent scheduling, comprising: establishing a retail screen registration table in the store's local edge network, reading the device identifier, installation area identifier, and control domain identifier of the retail screen, and obtaining valid neighboring device information through Bluetooth near-field scanning; generating a near-field relationship table based on the valid neighboring device information, comparing the near-field relationship table with the area adjacency template, generating an authorized near-field topology fingerprint, and binding it with the WiFi access policy to form a screen-end control right verification record; when the retail screen issues a WiFi access request or WiFi control request, re-collecting the current neighboring device information and generating the current near-field topology fingerprint; matching the current near-field topology fingerprint with the authorized near-field topology fingerprint, and generating a control right verification result based on the topology anchoring device consistency rate, near-field relationship strength deviation value, and control domain conflict flag; and generating a WiFi access token and WiFi control command release permission when the verification passes.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of wireless communication and retail screen control technology, and particularly relates to a retail screen WiFi control method based on Bluetooth intelligent scheduling. BACKGROUND

[0002] With the increase in the number of retail screens in the scenarios of supermarket shelves, refrigerators, show windows and in-store stores, the retail screens usually complete network distribution or close-range maintenance through Bluetooth first, and then access the store network through WiFi, and the display updates, brightness adjustment and power-on / off control instructions are issued by the store gateway, edge control device or background system.

[0003] The existing method determines the control attribution of the retail screen according to the device identifier, account binding, WiFi name, WiFi password or background registration information. This method can confirm the logical identity of the retail screen, but it is difficult to prove whether the retail screen is still located in the registered installation area, and it is also difficult to confirm whether the store gateway, shelf beacon and adjacent retail screen around it still maintain the original deployment relationship.

[0004] In addition, in the multi-shelf, multi-refrigerator or open display area, the WiFi coverage range and the Bluetooth scanning range are likely to overlap. When the retail screen is misinstalled, re-powered, batch maintained or misconnected to the network of the adjacent area, the background may still release the WiFi access permission and control instructions due to the correct device identifier, resulting in the problem that the retail screen is controlled by the wrong domain and is misupdated, misadjusted in brightness or abnormally powered on / off across the area.

[0005] Therefore, the present application provides a retail screen WiFi control method based on Bluetooth intelligent scheduling. The above information disclosed in the background section is only used to strengthen the understanding of the background of the present disclosure, and it may contain prior art information that is not part of the common general knowledge of a person skilled in the art. SUMMARY

[0006] The purpose of the present application is to overcome the shortcomings of the prior art and provide a retail screen WiFi control method based on Bluetooth intelligent scheduling to solve the technical problems mentioned in the background.

[0007] To achieve the above-mentioned purpose, the present application provides the following technical solutions:

[0008] A retail screen WiFi control method based on Bluetooth intelligent scheduling, comprising the following steps:

[0009] S1, establishing a retail screen registration table in a local edge network of a store, reading the device identifier, installation area identifier and control domain identifier of the retail screen to form screen-end basic registration information, starting Bluetooth near-field scanning and screening adjacent device information to obtain valid adjacent device information;

[0010] S2, generating a near field relationship table according to the effective adjacent device information, comparing the near field relationship table with the area adjacent template, generating an authorized near field topology fingerprint, and binding the device identification, installation area identification, control domain identification and WiFi access strategy as a screen control right verification record;

[0011] S3, when the retail screen sends a WiFi access request or a WiFi control request, the edge network control node calls the screen control right verification record, controls the retail screen to perform a Bluetooth near field scan, and generates a current near field topology fingerprint;

[0012] S4, matching the current near field topology fingerprint with the authorized near field topology fingerprint, generating a control right verification result according to the topology anchoring device consistency rate, near field relationship strength deviation value and control domain conflict marker;

[0013] S5, when the control right verification result is passed, generating a WiFi access token and a WiFi control instruction release permission, enabling the retail screen to access the WiFi network in the control domain and perform control; when the control right verification result is not passed, refusing to generate a WiFi access token and a release permission, and generating a cross-area control risk record.

[0014] S1 specifically includes: establishing a retail screen registration table in a store local edge network, reading the device identification, installation area identification and control domain identification of a retail screen to be deployed or calibrated, and writing the edge network control node to form screen basic registration information; starting a Bluetooth near field scan according to the screen basic registration information, collecting the device identification, device type, Bluetooth signal strength interval and adjacent duration of adjacent devices within a preset scanning period to form original adjacent device information; screening the original adjacent device information according to the device type, adjacent duration and Bluetooth signal strength stability, eliminating device records that do not belong to the authorized range or are abnormally fluctuating, obtaining effective adjacent device information, and storing it in association with the screen basic registration information.

[0015] S2 specifically includes: calling a device pre-registration table according to the effective adjacent device information, determining the device type, belonging control domain identification, adjacent duration and Bluetooth signal strength stability of each adjacent device, and calculating the near field relationship strength of each adjacent device according to the adjacent duration and Bluetooth signal strength stability, and dividing the near field relationship level of each adjacent device to generate a near field relationship table for representing the installation relationship around the retail screen; taking the installation area identification as an index to call the area adjacent template, matching the near field relationship table with the area adjacent template, retaining the store gateway, shelf beacon and fixed adjacent retail screen that meet the near field relationship strength requirement as the topology anchoring device, and generating an authorized near field topology fingerprint; binding the authorized near field topology fingerprint, device identification, installation area identification, control domain identification and WiFi access strategy to form a screen control right verification record and store it in the edge network control node.

[0016] S3 specifically comprises: the edge network control node receives the WiFi access request or WiFi control request issued by the retail screen, reads the device identifier, request type, request time and request serial number, calls the screen control right verification record according to the device identifier, and verifies the request time limit, calibration version number and control domain identifier; after verification, the current scanning parameter is issued, the retail screen is controlled to re-execute the Bluetooth near field scanning before receiving the WiFi access token and WiFi control instruction, the current adjacent device information is collected and the current scanning sufficiency rate is judged; the current effective adjacent device information is obtained according to the screening criterion, and the current near field relationship table is formed according to the near field relationship generation criterion to generate the current near field topology fingerprint.

[0017] S4 specifically comprises: reading the authorized near field topology fingerprint, installation area identifier and control domain identifier from the screen control right verification record, matching the topology anchor device in the authorized near field topology fingerprint with the current topology anchor device in the current near field topology fingerprint according to the device identifier, device type, belonging control domain identifier and near field relationship level to obtain a matching detail table and a topology anchor device consistency rate; the near field relationship strength deviation value is calculated according to the matching detail table, and the control domain conflict mark is generated according to the belonging control domain identifier of the current topology anchor device; the control right verification result is generated according to the topology anchor device consistency rate, the near field relationship strength deviation value and the control domain conflict mark, and the missing device, the abnormal new device and the adjacent control domain identifier are recorded.

[0018] S5 specifically comprises: when the control right verification result is passed, the edge network control node checks the device identifier, control domain identifier of the retail screen, and request serial number and allowed control instruction type in the WiFi access request or WiFi control request according to the WiFi access strategy to generate the WiFi access token and WiFi control instruction release permission; the retail screen accesses the WiFi network in the corresponding control domain according to the WiFi access token, executes display update, brightness adjustment or power-on / off control after receiving the WiFi control instruction, and returns a control execution record; when the pre-check fails due to the request time limit, calibration version number or control domain identifier verification, or the current scanning is insufficient due to the current scanning sufficiency rate, or the control right verification result is not passed, the WiFi access token and release permission are refused to be generated, the request cache is cleared, the cross-area control risk record is generated and the to-be-reviewed state is determined.

[0019] The beneficial effects of the present application are:

[0020] The present application associates the effective adjacent device information obtained by the Bluetooth near field scanning with the device identifier, installation area identifier and control domain identifier of the retail screen, so that the control attribution of the retail screen is no longer dependent on the logical identity, and the actual installation environment can be further verified to improve the reliability of the control right judgment.

[0021] The application can identify abnormal conditions such as misinstallation, displacement or proximity to adjacent control domains of the retail screen by generating an authorized near-field topology fingerprint based on the store gateway, shelf beacon and fixed adjacent retail screen and comparing it with the current near-field topology fingerprint before WiFi access or control instruction release. WiFi access token and WiFi control instruction release permission are generated only after control right verification, so that the WiFi access permission is bound to the Bluetooth near-field environment verification result, avoiding incorrect release of control permission due to correct device identification.

[0022] The application can block the retail screen from being taken over by the wrong control domain and reduce the risk of cross-area misupdate, incorrect content display and abnormal shutdown by refusing to generate a WiFi access token and release permission when the control right verification fails, the pre-check fails or the current scan is insufficient, and generating a cross-area control risk record. The token release record, control execution record and cross-area control risk record are stored in association, so that each WiFi control process has traceable basis, facilitating subsequent recalibration, control domain audit and WiFi access strategy update. BRIEF DESCRIPTION OF DRAWINGS

[0023] Figure 1 A schematic diagram of the retail screen WiFi control method based on Bluetooth smart scheduling of the application;

[0024] Figure 2 A screen registration interface provided by the embodiment of the application;

[0025] Figure 3 A Bluetooth scanning configuration interface provided by the embodiment of the application;

[0026] Figure 4 A near-field topology fingerprint and area adjacency template matching interface provided by the embodiment of the application;

[0027] Figure 5 A control right verification interface provided by the embodiment of the application;

[0028] Figure 6 A WiFi token management interface provided by the embodiment of the application;

[0029] Figure 7 A control instruction issuing interface provided by the embodiment of the application. DETAILED DESCRIPTION

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

[0031] Example: Figures 1 to 7 As shown, this embodiment provides a retail screen WiFi control method based on Bluetooth intelligent scheduling, including the following steps:

[0032] S1. Establish a retail screen registration form in the local edge network of the store, read the device identifier, installation area identifier and control domain identifier of the retail screen to form basic registration information of the screen, start Bluetooth near field scanning and filter neighboring device information to obtain effective neighboring device information;

[0033] S2. Generate a near-field relationship table based on the valid adjacent device information, compare the near-field relationship table with the regional adjacency template, generate an authorized near-field topology fingerprint, and bind it with the device identifier, installation area identifier, control domain identifier and WiFi access policy as a screen control verification record.

[0034] S3. When the retail screen sends a WiFi access request or WiFi control request, the edge network control node retrieves the screen control verification record and controls the retail screen to perform Bluetooth near-field scanning to generate the current near-field topology fingerprint.

[0035] S4. Match the current near-field topology fingerprint with the authorized near-field topology fingerprint, and generate control rights verification results based on the topology anchoring device consistency rate, near-field relationship strength deviation value and control domain conflict flag;

[0036] S5. When the control verification result is successful, generate a WiFi access token and WiFi control command release permission to enable the retail screen to access the WiFi network within the control domain and execute control; when the control verification result is unsuccessful, refuse to generate a WiFi access token and release permission, and generate a cross-regional control risk record.

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

[0038] S110. Establish a retail screen registration form in the local edge network of the store, read the device identifier, installation area identifier, and control domain identifier of the retail screen to be deployed or calibrated, and write the device identifier, installation area identifier, and control domain identifier into the edge network control node to obtain the basic registration information of the screen.

[0039] Specifically, an edge network refers to a local communication network set up in a store to connect retail screens, store gateways, shelf beacons, and maintenance terminals; an edge network control node refers to a control device or control program deployed within the edge network to store retail screen registration forms, receive Bluetooth scan results, and perform subsequent control rights verification.

[0040] The device identifier is used to uniquely identify the retail screen, and its data source is at least one of the following: the screen firmware number, the screen label QR code number, or the screen security chip number written when the retail screen leaves the factory; the installation area identifier is used to characterize the actual installation location of the retail screen, and its data source is the shelf number, freezer number, display window number, or display area number entered by the deployment personnel during installation; the control domain identifier is used to characterize the store gateway or edge network control node that has the right to control the retail screen, and its data source is the store's local control domain configuration table.

[0041] After receiving deployment confirmation or calibration confirmation, the edge network control node writes the device identifier, installation area identifier, and control domain identifier of the same retail screen into the retail screen registration form, forming the basic registration information of the screen. The basic registration information of the screen serves as the index for S120 to initiate Bluetooth near-field scanning and as the data basis for S130 to associate and store information on valid adjacent devices.

[0042] S120. Start Bluetooth near-field scanning based on the basic registration information of the screen and collect information on neighboring devices around the retail screen within a preset scanning period. The information on neighboring devices includes the device identifier, device type, Bluetooth signal strength range, and duration of proximity of adjacent retail screens, store gateways, shelf beacons, or maintenance terminals.

[0043] Specifically, based on the basic registration information obtained from the screen via S110, the edge network control node sends a Bluetooth near-field scanning start command to the corresponding retail screen. The retail screen then receives Bluetooth broadcast packets or connection response packets from surrounding devices through its own Bluetooth module within a preset scanning period. The preset scanning period is set by the edge network control node in the deployment parameters, and is typically set to 30 to 120 seconds, with a scanning interval of 1 to 5 seconds. When the density of shelves in the store is high or there are many metal obstructions, a longer scanning period is used to reduce the impact of occasional obstructions on the scanning results.

[0044] The data sources for neighboring device information include device identifiers in Bluetooth broadcast packets, device types in the device pre-registration table, Bluetooth signal strength values ​​obtained from retail screen scanning, and time records of repeated scanning of the same neighboring device within the scanning cycle. Device types include adjacent retail screens, store gateways, shelf beacons, and maintenance terminals; devices not registered in the device pre-registration table are not directly used as authorized devices in subsequent topology fingerprint generation.

[0045] For the same adjacent device, the retail screen records Bluetooth signal strength values ​​multiple times within a preset scanning cycle, and determines the adjacency duration based on the number of times the adjacent device is effectively scanned, forming raw adjacent device information that includes device identifier, device type, Bluetooth signal strength sampling records, and scan time records. After the raw adjacent device information is sent to the edge network control node, it serves as input data for S130 to perform validity filtering.

[0046]

[0047] in, This represents the adjacency duration of the i-th adjacent device. This indicates the number of times the i-th adjacent device is effectively scanned within a preset scanning period. This represents the time interval between two adjacent Bluetooth scans, where i represents the sequence number of the neighboring device. Using this calculation method, the edge network control node converts the discrete scan results into an adjacency duration for filtering.

[0048] S130. Perform validity screening on the adjacent device information, remove device records with insufficient adjacent duration, device type not within the authorized range, or abnormal fluctuations in Bluetooth signal strength range, obtain valid adjacent device information corresponding to the retail screen, and store the valid adjacent device information in association with the screen's basic registration information.

[0049] Specifically, the edge network control node reads the original adjacent device information obtained from S120 and filters it according to device type, adjacent duration, and Bluetooth signal strength stability. The authorized scope is determined by the store's local control domain configuration table, including adjacent retail screens, store gateways, shelf beacons, and authorized maintenance terminals corresponding to the current control domain identifier.

[0050] For each adjacent device, the edge network control node first determines whether its device type falls within the authorized scope; then it determines whether the device has been stably present within the preset scanning period based on the adjacency duration; and finally, it determines whether the device is a stable near-field device based on the average Bluetooth signal strength and the Bluetooth signal strength fluctuation value.

[0051] The Bluetooth signal strength range is characterized by the average Bluetooth signal strength and the Bluetooth signal strength fluctuation value. The average Bluetooth signal strength is used to determine whether the adjacent device is within the allowed near field range, while the Bluetooth signal strength fluctuation value is used to exclude records of devices that are temporarily passing by, moving at a high speed, or being significantly affected by obstruction.

[0052]

[0053] in, This represents the average Bluetooth signal strength of the i-th neighboring device within a preset scanning period. This represents the number of times the Bluetooth signal strength value of the i-th neighboring device has been collected. This represents the Bluetooth signal strength value collected for the i-th neighboring device in the j-th time, where j represents the collection sequence number of the Bluetooth signal strength value.

[0054]

[0055] in, This represents the Bluetooth signal strength fluctuation value of the i-th adjacent device. This represents the maximum Bluetooth signal strength value of the i-th neighboring device within a preset scan period. This represents the minimum Bluetooth signal strength value of the i-th neighboring device within a preset scanning period.

[0056] When the i-th neighboring device's device type falls within the authorized range, the adjacency duration is not less than the minimum adjacency duration threshold, the average Bluetooth signal strength is within the preset strength range, and the Bluetooth signal strength fluctuation value is not greater than the maximum allowable fluctuation value of the Bluetooth signal strength, the edge network control node writes the neighboring device into the valid neighboring device information. Device records that do not meet any of the conditions are not included in the valid neighboring device information but are retained as abnormal scan records. The minimum adjacency duration threshold, preset strength range, and maximum allowable fluctuation value of Bluetooth signal strength are derived from calibration data during the store deployment phase and are also updated by the edge network control node based on historical stable scan results within the same installation area.

[0057] For example, a retail screen is installed on the left side of refrigerated display case A. The edge network control node receives scan records from adjacent retail screens, shelf beacons, store gateways, and maintenance terminals within a preset 60-second scan cycle. Among them, adjacent retail screens, shelf beacons, and store gateways appear continuously, their average Bluetooth signal strength is within the preset strength range, and their Bluetooth signal strength fluctuation does not exceed the maximum allowable fluctuation value of Bluetooth signal strength, so they are written into the valid adjacent device information. The maintenance terminal only appears in the first 8 seconds of the scan cycle, and its Bluetooth signal strength fluctuation exceeds the maximum allowable fluctuation value of Bluetooth signal strength, so it is excluded.

[0058] The edge network control node will eventually associate and store the effective adjacent device information with the screen-end basic registration information formed in S110, so that S210 can generate a near-field relationship table based on the effective adjacent device information.

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

[0060] S210. Based on the valid adjacent device information, determine the near-field relationship between each adjacent device and the retail screen according to the device type, Bluetooth signal strength range and adjacent duration, and generate a near-field relationship table to characterize the installation relationship around the retail screen.

[0061] Specifically, the edge network control node reads the valid adjacent device information obtained in S130, and simultaneously calls the screen-end basic registration information and device pre-registration table generated in S110. The device pre-registration table is used to record the device identifier, device type, control domain identifier, and whether it is a fixed deployment device of the adjacent device.

[0062] The near-field relationship table is a data table generated by the edge network control node based on the information of effective neighboring devices. It is used to characterize the near-field relationship between the retail screen and each effective neighboring device. It includes at least the device identifier of the retail screen, the device identifier of the neighboring device, the device type of the neighboring device, the average value of the Bluetooth signal strength, the Bluetooth signal strength fluctuation value, the duration of the adjacency, the strength of the near-field relationship, and the level of the near-field relationship.

[0063] Near-field relationship strength is used to characterize the stability of the near-field relationship between adjacent devices and retail screens. The edge network control node calculates the near-field relationship strength based on the adjacency duration and the Bluetooth signal strength fluctuation value. The longer the adjacency duration and the smaller the Bluetooth signal strength fluctuation value, the more suitable the adjacent device is as evidence of the physical installation relationship of the retail screen.

[0064]

[0065] in, This represents the near-field relationship strength of the i-th adjacent device. This represents the adjacency duration of the i-th adjacent device. Indicates the preset scan cycle. This represents the Bluetooth signal strength fluctuation value of the i-th adjacent device. This represents the maximum allowable fluctuation value of Bluetooth signal strength, and i represents the serial number of the adjacent device.

[0066] If the Bluetooth signal strength fluctuation value of the i-th neighboring device is greater than the maximum allowable fluctuation value of the Bluetooth signal strength, then the neighboring device has been removed in S130 and will not participate in the near-field relationship strength calculation.

[0067] The edge network control node pre-sets a first near-field strength threshold and a second near-field strength threshold, with the first near-field strength threshold being greater than the second near-field strength threshold. Based on the calculated near-field relationship strength, the edge network control node classifies adjacent devices into three levels: when the near-field relationship strength is greater than or equal to the first near-field strength threshold, it is classified as a stable near-field relationship; when the near-field relationship strength is less than the first near-field strength threshold but greater than or equal to the second near-field strength threshold, it is classified as a general near-field relationship; and when the near-field relationship strength is less than the second near-field strength threshold, it is classified as a relationship not involved in fingerprinting. The near-field relationship levels are arranged from highest to lowest in the order of stable near-field relationship, general near-field relationship, and relationship not involved in fingerprinting. Stable near-field relationships are used for subsequent S220 generation of authorized near-field topology fingerprints, while general near-field relationships serve as auxiliary verification records and are not involved in long-term physical installation relationship proof.

[0068] S220: Compare the near-field relationship table with the installation area identifier, retain the adjacent devices that are stably associated with the current installation area, remove temporary maintenance terminals and devices that are not in this control domain, and generate an authorized near-field topology fingerprint for the retail screen.

[0069] Specifically, the edge network control node does not directly compare the installation area identifier with the adjacent device information. Instead, it uses the installation area identifier as an index to retrieve the corresponding area adjacency template from the store's local control domain configuration table. The area adjacency template refers to the template data pre-established for the installation area identifier during the store deployment or calibration phase. It is used to record the topology anchoring devices that should exist in the installation area, the allowed device types, the allowed near-field relationship levels, and the allowed control domain identifiers.

[0070] The specific process for generating the regional adjacency template is as follows: When the store is initially deployed or the maintenance personnel confirm on-site and actively trigger calibration, under the premise that the retail screen is in the physically authorized installation location, the edge network control node controls the retail screen to perform multiple full Bluetooth near-field scans; extract the store gateway, shelf beacon and fixed adjacent retail screen whose device type meets the requirements and whose near-field relationship strength reaches the stable near-field relationship standard from the intersection of multiple scan results, and combine their device identifier, allowed near-field relationship level and the identifier of the control domain to generate a regional adjacency template bound to the installation area identifier.

[0071] Topology anchoring devices refer to devices that are permanently fixed near the installation area and used to verify the physical installation relationship of retail screens, including store gateways, shelf beacons, and fixed adjacent retail screens; maintenance terminals are only used as auxiliary devices during deployment or calibration and are not used as long-term topology anchoring devices.

[0072] The edge network control node matches the near-field relationship table generated by S210 with the regional adjacency template item by item, determines whether there is a topology anchoring device required by the regional adjacency template in the near-field relationship table, and determines whether the near-field relationship strength of the corresponding topology anchoring device meets the minimum near-field relationship strength threshold.

[0073]

[0074] Where M represents the region template matching rate, This indicates the number of topology anchoring devices in the near-field relationship table that successfully match the region adjacency template. This indicates the total number of topology anchoring devices required in the region adjacency template.

[0075] The edge network control node determines whether the current deployment location of the retail screen can form a stable correspondence with the adjacent template of the installation area identifier based on the area template matching rate. When the area template matching rate is not less than the minimum area template matching rate threshold, and all topology anchoring devices used to generate the authorized near-field topology fingerprint meet the minimum near-field relationship strength threshold, the edge network control node writes the successfully matched topology anchoring devices, their near-field relationship strength, near-field relationship level, and the identifier of their respective control domain into the authorized near-field topology fingerprint. The authorized near-field topology fingerprint refers to the structured data formed by the topology anchoring devices and their near-field relationships that meet the stable conditions within the installation area. It is used to compare with the current near-field topology fingerprint to determine whether the retail screen is still within the authorized physical installation area and control domain.

[0076] For example, the installation area of ​​retail screen 001 is identified as the area to the left of freezer A. The area adjacency template requires the existence of shelf beacon A1, store gateway 01, and adjacent retail screen 002. If all three topology anchoring devices in the near-field relationship table are successfully matched and the near-field relationship strength meets the requirements, they will be written into the authorized near-field topology fingerprint. If maintenance terminal M1 is also scanned, but it is not a long-term topology anchoring device, it will not be written into the authorized near-field topology fingerprint.

[0077] S230: Bind the authorized near-field topology fingerprint, device identifier, installation area identifier, control domain identifier, and WiFi access policy to form a screen control verification record. Store the screen control verification record in the edge network control node as the verification basis for subsequent release of WiFi access tokens and WiFi control commands.

[0078] Specifically, the WiFi access policy comes from the store's local control domain configuration table and includes at least the allowed WiFi network identifiers, the target store gateway, the access token validity period, the allowed control command types, and the verification failure handling rules. The on-screen control verification record refers to the record formed by binding the authorized near-field topology fingerprint, device identifier, installation area identifier, control domain identifier, and WiFi access policy. It includes at least the device identifier, installation area identifier, control domain identifier, authorized near-field topology fingerprint, WiFi access policy, generation time, and calibration version number.

[0079] After forming the screen control rights verification record, the edge network control node uses it as the sole record source for subsequent control rights determination of the retail screen: in S310, the screen control rights verification record is retrieved according to the device identifier; in S410 to S430, the authorized near-field topology fingerprint in the record is matched with the current near-field topology fingerprint; and in S510 to S530, the matching result determines whether to release the WiFi access token and WiFi control command.

[0080] Through the above binding, the WiFi control permissions of the retail screen no longer rely solely on device identification or account registration, but are simultaneously constrained by the installation area identification, control domain identification, and authorized near-field topology fingerprint, thereby providing an executable verification basis for subsequently blocking erroneous control domain takeovers.

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

[0082] After receiving a WiFi access request or WiFi control request from a retail screen, the S310 edge network control node reads the device identifier in the WiFi access request or WiFi control request and retrieves the corresponding screen control verification record based on the device identifier.

[0083] Specifically, a WiFi access request refers to the request data sent by a retail screen to an edge network control node when it needs to access the WiFi network within the corresponding control domain, used to apply for a WiFi access token; a WiFi control request refers to the request data sent by a retail screen to an edge network control node when it needs to receive WiFi control commands such as display updates, brightness adjustments, or power on / off control, used to apply for the release of control commands within the corresponding control domain.

[0084] When the retail screen is not yet connected to the WiFi network, the WiFi access request is sent to the edge network control node via the Bluetooth link; when the retail screen has an available WiFi link, the WiFi control request is sent via the WiFi link, or via the Bluetooth link when the WiFi link is unstable.

[0085] WiFi access or control requests must include at least the device identifier, request type, request time, request sequence number, and current communication method. Upon receiving a request, the edge network control node first reads the device identifier and then retrieves the screen-side control verification record stored in the S230 based on that identifier. The screen-side control verification record includes at least the device identifier, installation area identifier, control domain identifier, authorized near-field topology fingerprint, WiFi access policy, generation time, and calibration version number. The edge network control node also verifies the validity of the control domain identifier against the store's local control domain configuration table and determines whether the request has timed out based on the request time.

[0086]

[0087] Where Q represents the request timeout flag, and a value of 1 indicates that the request has not timed out; This indicates the time when the edge network control node receives a WiFi access request or a WiFi control request; Indicates the time when the retail screen generates a WiFi access request or WiFi control request; Indicates the maximum allowed duration of the request.

[0088] When the control rights verification record is missing, the device identifier does not match, the calibration version number is inconsistent, the control domain identifier is invalid, or the request timeliness flag is not 1, the edge network control node does not enter S320, but instead generates a control rights verification pre-failure record. The control rights verification pre-failure record includes the device identifier, request type, failure reason, and recording time, which is used to form a cross-regional control risk record or register the source of abnormal requests in S530.

[0089] S320: Before releasing the WiFi access token and WiFi control command, control the retail screen to re-perform Bluetooth near-field scanning to collect current neighboring device information, including the device identifier, device type, Bluetooth signal strength range, and neighboring duration of the currently scannable neighboring devices.

[0090] Specifically, after the S310 completes the pre-verification, the edge network control node sends the current scanning parameters to the corresponding retail screen based on the installation area identifier and control domain identifier in the screen control verification record. The current scanning parameters include the current scanning cycle, scanning interval, minimum number of samples, and allowed device types. The current neighboring device information refers to the neighboring device information collected in real time by the retail screen through Bluetooth near-field scanning after issuing a WiFi access request or WiFi control request and before receiving the WiFi access token and WiFi control command. Historical neighboring device information is not used directly.

[0091] The current Bluetooth near-field scanning acquisition fields are consistent with those of S120, including at least the device identifier of the adjacent device, device type, Bluetooth signal strength sampling value, and scan time record; among them, the device identifier and Bluetooth signal strength sampling value are obtained from the Bluetooth broadcast packet or connection response packet received by the retail screen Bluetooth module, and the device type and the control domain identifier are obtained from the device pre-registration table.

[0092] To balance real-time performance and stability, the current scanning cycle is shorter than the preset scanning cycle during deployment or calibration, but not less than the minimum scanning cycle set by the edge network control node. When stores are in a batch update scenario, the edge network control node sequentially sends the current scanning parameters to multiple retail screens according to the installation area identifier, avoiding Bluetooth broadcast congestion caused by multiple retail screens scanning simultaneously. After receiving the current scan result, the edge network control node determines whether the current scan has the basis for generating the current near-field topology fingerprint.

[0093]

[0094] Where P represents the current scan sufficiency rate, This indicates the number of valid Bluetooth signal strength samples obtained within the current scanning period. This indicates the number of scans to be performed within the current scan cycle.

[0095] When the current scan sufficiency rate is lower than the minimum scan sufficiency rate threshold, the edge network control node sends a rescan command to the retail screen; if the scan sufficiency rate is still lower than the minimum scan sufficiency rate threshold after rescanning, a current scan insufficiency record is generated, and the WiFi access token and WiFi control command are not released temporarily.

[0096] S330: Perform the same validity screening as S130 on the current adjacent device information, and obtain the current near-field topology fingerprint of the retail screen according to the same near-field relationship generation method as S210, so that the current near-field topology fingerprint can be compared with the authorized near-field topology fingerprint with the same caliber.

[0097] Specifically, the edge network control node reads the current neighboring device information obtained in S320, and calculates the neighboring duration, average Bluetooth signal strength, and Bluetooth signal strength fluctuation value of each current neighboring device according to the device type filtering rules, neighboring duration filtering rules, and Bluetooth signal strength stability filtering rules determined in S130, to obtain the current effective neighboring device information.

[0098] Subsequently, the edge network control node generates a current near-field relationship table based on the current effective neighboring device information, using the same near-field relationship strength calculation method as in S210. The fields of the current near-field relationship table are consistent with those in the near-field relationship table in S210, including at least the device identifier of the retail screen, the device identifier of the current neighboring device, the device type, the average Bluetooth signal strength, the Bluetooth signal strength fluctuation value, the adjacency duration, the current near-field relationship strength, and the current near-field relationship level.

[0099] The current topology anchored device is a device in the currently valid adjacent device information whose device type belongs to store gateway, shelf beacon, or fixed adjacent retail screen, and meets the current near-field relationship strength requirements. The current near-field topology fingerprint refers to the structured data formed by the edge network control node based on the current topology anchored devices that meet the conditions in the current near-field relationship table. It is used for subsequent comparison with the authorized near-field topology fingerprint. It includes at least the device identifier, request time, current scan cycle, current topology anchored device set, device identifier of each current topology anchored device, device type, current near-field relationship strength, current near-field relationship level, and the identifier of the control domain to which it belongs.

[0100]

[0101] in, This indicates the current near-field topology fingerprint generation flag; a value of 1 indicates that generating the current near-field topology fingerprint is allowed. P represents the current scan sufficiency rate. This represents the minimum scan fullness threshold; It represents the current near-field relationship strength of the i-th current adjacent device. Its calculation method is consistent with the near-field relationship strength in S210, and the data source is the current scanning phase. This represents the minimum near-field relationship strength threshold.

[0102] When the conditions for generating the current near-field topology fingerprint are met, the edge network control node generates the current near-field topology fingerprint. When the current scan result lacks the topology anchoring device in the authorized near-field topology fingerprint, or when there is a shelf beacon, store gateway, or fixed adjacent retail screen in the adjacent control domain, the edge network control node still generates the current near-field topology fingerprint based on the current scan result, and writes the missing device, abnormally added device, and the control domain identifier to the current near-field topology fingerprint.

[0103] For example, when retail screen 001 requests a display update, if the current scan result still includes shelf beacon A1, store gateway 01, and adjacent retail screen 002, and the current near-field relationship strength of these three devices meets the requirements, then a current near-field topology fingerprint is generated; if the current scan result lacks shelf beacon A1 but shows shelf beacon B1 belonging to an adjacent control domain, then shelf beacon B1 and its control domain identifier are written into the current near-field topology fingerprint for S410 to S430 to determine whether there is a cross-region control risk.

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

[0105] S410: Read the authorized near-field topology fingerprint, installation area identifier, control domain identifier, and WiFi access policy from the screen control verification record, and match the adjacent devices in the authorized near-field topology fingerprint with the adjacent devices in the current near-field topology fingerprint.

[0106] Specifically, the edge network control node reads the screen control verification record formed in S230 and the current near-field topology fingerprint formed in S330, and matches the set of topology anchoring devices in the authorized near-field topology fingerprint with the set of current topology anchoring devices in the current near-field topology fingerprint.

[0107] Matching is not based solely on Bluetooth signal strength, but rather on a combination of device identifier, device type, control domain identifier, and near-field relationship level. When a current topology anchoring device in the current near-field topology fingerprint matches a topology anchoring device in the authorized near-field topology fingerprint in terms of device identifier, device type, and control domain identifier, and the current near-field relationship level is not lower than the near-field relationship level requirement recorded in the authorized near-field topology fingerprint, the edge network control node records the current topology anchoring device as a successfully matched device.

[0108] The topology anchoring device consistency rate refers to the proportion of the number of topology anchoring devices in the current near-field topology fingerprint that successfully match the authorized near-field topology fingerprint to the total number of topology anchoring devices in the authorized near-field topology fingerprint. It is used to determine whether the fixed installation relationship around the retail screen is consistent.

[0109]

[0110] Where A represents the consistency rate of topology anchoring devices. This indicates the number of topology anchoring devices in the current near-field topology fingerprint that successfully match the authorized near-field topology fingerprint. This indicates the total number of topology anchoring devices in the authorized near-field topology fingerprint.

[0111] The edge network control node writes successfully matched devices, missing topology anchoring devices, and abnormally added current topology anchoring devices into the matching details table. The matching details table serves as the data source for S420 to determine whether the actual near-field environment is consistent.

[0112] S420. Based on the consistency of device identification, device type, Bluetooth signal strength range deviation, and adjacent duration deviation of adjacent devices, determine whether the actual near-field environment of the retail screen is still within the installation area corresponding to the installation area identification.

[0113] Specifically, the edge network control node, based on the matching details table obtained in S410, performs deviation judgment on the near-field relationship strength of successfully matched devices. Since the near-field relationship strength in S210 is jointly determined by the adjacency duration and the Bluetooth signal strength fluctuation value, and the current near-field relationship strength in S330 is generated using the same calculation method, this step uses the near-field relationship strength deviation value to uniformly represent the deviation of the Bluetooth signal strength range and the deviation of the adjacency duration, without introducing a new judgment method.

[0114] The near-field relationship strength deviation value refers to the degree of deviation between the current near-field relationship strength in the current near-field topology fingerprint and the near-field relationship strength in the authorized near-field topology fingerprint. It is used to determine whether the retail screen has shifted, been obstructed, or moved close to an adjacent control domain.

[0115]

[0116] Where B represents the deviation value of the near-field relationship strength, This indicates the number of topology anchoring devices in the current near-field topology fingerprint that successfully match the authorized near-field topology fingerprint. This represents the current near-field relationship strength of the v-th successfully matched topological anchoring device in the current near-field topological fingerprint. This represents the near-field relationship strength of the v-th successfully matched topology anchoring device in the authorized near-field topology fingerprint, where v represents the sequence number of the successfully matched topology anchoring device. By introducing the summation of absolute values, the system can accurately and objectively reflect the true degree of change and fluctuation in the overall near-field environment of the retail screen.

[0117] The edge network control node also generates a control domain conflict flag based on the control domain identifier of each currently anchored device in the current near-field topology fingerprint. The control domain conflict flag indicates whether there are any store gateways, shelf beacons, or fixed adjacent retail screens in the current near-field topology fingerprint that are inconsistent with the control domain identifier in the screen-end control rights verification record. When there are topology anchored devices in adjacent control domains, the edge network control node sets the control domain conflict flag to indicate that a conflict exists and records the corresponding device identifier, device type, control domain identifier, and current near-field relationship strength.

[0118] S430. When the current near-field topology fingerprint and the authorized near-field topology fingerprint meet the consistency condition, a control right verification pass result is generated; when the current near-field topology fingerprint and the authorized near-field topology fingerprint do not meet the consistency condition, a control right verification fail result is generated, and the inconsistent adjacent devices, the deviated Bluetooth signal strength range, and the corresponding installation area identifier are recorded.

[0119] Specifically, the edge network control node generates a control right verification result based on the topology anchoring device consistency rate obtained in S410, the near-field relationship strength deviation value obtained in S420, and the control domain conflict flag. The control right verification result includes a control right verification pass result and a control right verification fail result. The edge network control node generates a control right verification pass result only when the topology anchoring device consistency rate is not less than the minimum topology anchoring device consistency rate threshold, the near-field relationship strength deviation value is not greater than the maximum allowable near-field relationship strength deviation threshold, and the control domain conflict flag indicates that there is no conflict.

[0120]

[0121] Wherein, G represents the control verification pass flag, and a value of 1 indicates that the control verification pass result has been generated; A represents the topology anchoring device consistency rate. B represents the minimum topology anchoring device consistency threshold; B represents the near-field relationship strength deviation value. This indicates the maximum permissible near-field relationship strength deviation from the threshold; H represents the control domain conflict flag, with a value of 0 indicating that there are no topology anchoring devices in the current near-field topology fingerprint that are adjacent to the control domain, and a value of 1 indicating that there are topology anchoring devices in the current near-field topology fingerprint that are adjacent to the control domain.

[0122] If any one of the above conditions is not met, the edge network control node generates a control rights verification failure result. A control rights verification success result includes at least the device identifier, installation area identifier, control domain identifier, verification success time, and callable WiFi access policy, used by S510 to release the WiFi access token and generate WiFi control commands to release permissions. A control rights verification failure result includes at least the device identifier, installation area identifier, control domain identifier, missing topology anchoring device, abnormally added topology anchoring device, near-field relationship strength deviation value, control domain conflict marker, adjacent control domain identifier, and verification failure time, used by S530 to generate a cross-regional control risk record.

[0123] In specific supermarket and retail scenarios, the minimum topology anchoring device consistency rate threshold is preferably set between 0.6 and 0.8, and the maximum allowable near-field relationship strength deviation threshold is preferably set between 0.15 and 0.20. This parameter setting can accommodate minor signal fluctuations caused by reasonable personnel obstruction or goods movement, while strictly blocking risks caused by cross-regional boundary crossings or physical equipment displacement.

[0124] For example, the authorized near-field topology fingerprint of retail screen 001 includes shelf beacon A1, store gateway 01, and adjacent retail screen 002. All three devices belong to the control domain corresponding to store gateway 01. If the current near-field topology fingerprint only matches store gateway 01 and adjacent retail screen 002, and shelf beacon A1 is missing, and a new shelf beacon B1 belonging to the control domain of adjacent store gateway 02 is added, then even if two topology anchoring devices have been successfully matched, the edge network control node will still generate a control right verification failure result according to the control domain conflict flag, and write shelf beacon A1, shelf beacon B1, adjacent store gateway 02, and the corresponding near-field relationship strength into the verification failure details so that S530 can block the erroneous control domain from taking over.

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

[0126] S510. When the control rights verification result is a control rights verification pass result, the edge network control node generates a WiFi access token corresponding to the control domain identifier according to the WiFi access policy, and generates a WiFi control command consistent with the request type to release the license.

[0127] Specifically, the edge network control node reads the control verification result generated by S430 and calls the WiFi access policy in the screen control verification record in S230 to verify the device identifier, installation area identifier, control domain identifier, request sequence number, and allowed control command type. The WiFi access token is a temporary access credential generated by the edge network control node after the control verification is successful. It is used to allow the retail screen to access the WiFi network corresponding to the control domain identifier within a limited time. The WiFi access token differs from a fixed WiFi password; it is a temporary access credential bound to the device identifier, control domain identifier, WiFi network identifier, request sequence number, token generation time, and token validity period.

[0128] The WiFi network identifier, target store gateway, token validity period, and allowed control command type are derived from the store's local control domain configuration table; the request sequence number and request type are derived from the WiFi access request or WiFi control request in S310; and the control right verification pass time is derived from the control right verification pass result in S430.

[0129] The edge network control node generates a WiFi access token and a corresponding WiFi control command release permit only when the request type falls within the scope permitted by the WiFi access policy. The WiFi control command release permit is used to limit the types of WiFi control commands that the retail screen can receive after accessing the WiFi network within the corresponding control domain.

[0130] WiFi control commands refer to control data sent from the edge network control node to the retail screen through the target store gateway, including display update commands, brightness adjustment commands, or power on / off control commands. Display update commands include at least the display task number, material version number, and material verification value; brightness adjustment commands include at least the target brightness value or brightness level; and power on / off control commands include at least the target running status and execution time.

[0131] When the edge network control node generates a WiFi access token and WiFi control command release permission, it writes this release action into the token release record. The token release record includes the device identifier, control domain identifier, request sequence number, token generation time, token validity duration, control command type, release permission, and recording time.

[0132]

[0133] Where L represents the WiFi access token validity flag, and a value of 1 indicates that the WiFi access token is in a valid state; Indicates the duration for which the retail screen uses the WiFi access token; Indicates the time when the edge network control node generates the WiFi access token; Indicates the validity period of the WiFi access token.

[0134] When the WiFi access token is marked as valid (1), the retail screen accesses the WiFi network within the corresponding control domain; when the WiFi access token expires, the retail screen stops using the WiFi access token and re-initiates the WiFi access request.

[0135] The S520 retail screen accesses the WiFi network within the corresponding control domain based on the WiFi access token, and performs display updates, brightness adjustments, or power on / off control according to the WiFi control commands. After execution, it sends the control execution record back to the edge network control node. The control execution record includes the device identifier, control domain identifier, execution result, and execution time.

[0136] Specifically, after receiving the WiFi access token generated by S510, the retail screen first verifies whether the device identifier, control domain identifier, and request sequence number in the token match its own request. If they match and the WiFi access token is valid (marked as 1), the retail screen accesses the WiFi network corresponding to the target store gateway and records a successful WiFi access flag. After the retail screen accesses the WiFi network within the corresponding control domain, the edge network control node releases the permission based on the WiFi control command generated by S510 and sends the corresponding WiFi control command to the retail screen through the target store gateway.

[0137] After receiving the WiFi control command, the retail screen executes the corresponding action according to the type of control command: When the control command type is a display update command, the retail screen obtains the material package according to the display task number and material version number, and performs display switching after verifying the integrity of the material package according to the material checksum; when the control command type is a brightness adjustment command, the retail screen adjusts the display brightness according to the target brightness value or brightness level, and records the adjusted brightness state; when the control command type is a power on / off control command, the retail screen performs power on, power off, or standby switching according to the target operating state and execution time.

[0138] Control execution records refer to the data recorded by the retail screen after completing WiFi access and control actions and sent back to the edge network control node to prove that the WiFi control process has been executed. It includes at least the device identifier, installation area identifier, control domain identifier, request sequence number, WiFi access result, WiFi control command reception result, control action execution result, failure reason and execution time.

[0139] After receiving the control execution record, the edge network control node associates and stores it with the token release record in S510 and the screen control right verification record in S230, and uses it as the data source for subsequent recalibration, control domain auditing and WiFi access policy updates.

[0140]

[0141] Where X represents the control execution completion flag, and a value of 1 indicates that the control execution is complete; This indicates a successful WiFi connection. This indicates that the WiFi control command was successfully received. This indicates that the control action was successfully executed.

[0142] Only when WiFi access, WiFi control command reception, and control action execution are all successful will the edge network control node record the execution result as successful; if any 1 flag is not 1, the edge network control node will write the failed step and the reason for failure into the control execution record.

[0143] S530: When the control verification result is that the control verification fails, the edge network control node refuses to release the WiFi access token and WiFi control command to the retail screen, and generates a cross-region control risk record based on the inconsistent neighboring devices, the deviated Bluetooth signal strength range and the corresponding installation area identifier recorded in S430, so as to prevent the retail screen from being taken over by the wrong control domain.

[0144] Specifically, when the edge network control node receives a control rights verification failure result generated by S430, a control rights verification pre-failure record generated by S310, or a current scan insufficient record generated by S320, it does not generate a WiFi access token, does not generate a WiFi control command to release permission, does not issue a WiFi control command through the target store gateway, clears the cache of this request, and returns a rejection result to the retail screen.

[0145] Cross-regional control risk records refer to risk records generated by edge network control nodes when control rights verification fails. These records characterize inconsistencies between the current near-field environment and the authorized near-field environment of the retail screen, or the presence of devices from adjacent control domains. They include at least the device identifier, original installation area identifier, original control domain identifier, missing topology anchoring devices, abnormally added topology anchoring devices, adjacent control domain identifiers, near-field relationship strength deviation value, rejection reason, rejection release time, and handling status. Edge network control nodes determine the cross-regional control risk level value based on missing topology anchoring devices, abnormally added topology anchoring devices, and control domain conflicts.

[0146]

[0147] Where Y represents the risk level value for cross-regional control. This indicates the risk value of missing topology anchoring devices. This indicates an abnormal addition of a risk value for the topology anchoring device. This indicates the risk value of conflict within the control domain.

[0148] During implementation, if a topology anchoring device is missing, the risk value for missing topology anchoring device is set to 1; if no topology anchoring device is missing, the risk value for missing topology anchoring device is set to 0. If an abnormal topology anchoring device is added, the risk value for abnormally added topology anchoring device is set to 1; if no abnormal topology anchoring device is added, the risk value for abnormally added topology anchoring device is set to 0. If a control domain conflict exists, the risk value for control domain conflict is set to 2; if no control domain conflict exists, the risk value for control domain conflict is set to 0.

[0149] The edge network control node determines whether to set the retail screen to a pending review state based on the cross-regional control risk level value. The pending review state refers to the state set by the edge network control node when the retail screen continuously fails control verification or the cross-regional control risk level value reaches a preset risk level threshold. This state is used to prevent the retail screen from continuing to request WiFi access tokens and WiFi control commands before recalibration.

[0150] For example, if the current near-field topology fingerprint of a retail screen lacks a shelf beacon in the authorized near-field topology fingerprint, and a new shelf beacon belonging to an adjacent control domain is added, the edge network control node will refuse to generate a WiFi access token and WiFi control command release permission, and write the missing device, abnormally added device and adjacent control domain identifier into the cross-regional control risk record. If the same risk occurs repeatedly in the retail screen, the edge network control node will set it to a pending review status until the deployment or calibration process is re-executed.

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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 retail screen WiFi control method based on Bluetooth intelligent scheduling, characterized in that, Includes the following steps: S1. Establish a retail screen registration form in the store's local edge network, read the device identifier, installation area identifier, and control domain identifier of the retail screen to form basic registration information of the screen, start Bluetooth near-field scanning and filter neighboring device information to obtain valid neighboring device information; S2. Generate a near-field relationship table based on the valid adjacent device information, compare the near-field relationship table with the regional adjacency template, generate an authorized near-field topology fingerprint, and bind it with the device identifier, installation area identifier, control domain identifier and WiFi access policy as a screen control verification record. S3. When the retail screen sends a WiFi access request or WiFi control request, the edge network control node retrieves the screen control verification record and controls the retail screen to perform Bluetooth near-field scanning to generate the current near-field topology fingerprint. S4. Match the current near-field topology fingerprint with the authorized near-field topology fingerprint, and generate control rights verification results based on the topology anchoring device consistency rate, near-field relationship strength deviation value and control domain conflict flag.

2. The retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 1, characterized in that, Also includes: S5. When the control verification result is passed, a WiFi access token and WiFi control command release permission are generated, enabling the retail screen to access the WiFi network within the control domain and execute control. If the control verification result fails, the generation of WiFi access tokens and release of licenses will be refused, and a cross-regional control risk record will be generated.

3. The retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 1, characterized in that, S1 specifically includes: Establish a retail screen registration form in the store's local edge network, read the device identifier, installation area identifier, and control domain identifier of the retail screen to be deployed or calibrated, and write them into the edge network control node to form the basic registration information of the screen. Based on the basic registration information on the screen, Bluetooth near-field scanning is initiated. Within a preset scanning period, the device identifier, device type, Bluetooth signal strength range, and duration of proximity of adjacent devices are collected to form the original adjacent device information.

4. The retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 3, characterized in that, Also includes: The original neighboring device information is filtered according to device type, adjacency duration, and Bluetooth signal strength stability. Device records that are not within the authorized scope or have abnormal fluctuations are removed to obtain valid neighboring device information, which is then stored in association with the basic registration information on the screen.

5. The retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 1, characterized in that, S2 specifically includes: Based on the valid adjacent device information, the device pre-registration form is retrieved to determine the device type, control domain identifier, adjacent duration, and Bluetooth signal strength stability of each adjacent device. The near-field relationship strength of each adjacent device is calculated based on the adjacency duration and the stability of the Bluetooth signal strength, and the near-field relationship level of each adjacent device is divided to generate a near-field relationship table to characterize the installation relationship around the retail screen. Using the installation area identifier as an index, the area adjacency template is retrieved. The near-field relationship table is matched with the area adjacency template. Store gateways, shelf beacons, and fixed adjacent retail screens that meet the near-field relationship strength requirements are retained and used as topology anchoring devices to generate authorized near-field topology fingerprints.

6. The retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 5, characterized in that, Also includes: The authorized near-field topology fingerprint, device identifier, installation area identifier, control domain identifier, and WiFi access policy are bound together to form a screen-end control rights verification record and stored in the edge network control node.

7. The retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 1, characterized in that, S3 specifically includes: The edge network control node receives WiFi access requests or WiFi control requests from retail screens, reads the device identifier, request type, request time, and request sequence number, retrieves the screen control verification record based on the device identifier, and verifies the request validity period, calibration version number, and control domain identifier. After the verification is successful, the current scanning parameters are sent out, and the retail screen is controlled to re-perform Bluetooth near-field scanning before receiving WiFi access token and WiFi control command, to collect information on the current neighboring devices and determine the current scan sufficiency. The information of currently valid adjacent devices is obtained according to the filtering criteria, and then the current near-field relationship table is formed according to the near-field relationship generation criteria, generating the current near-field topology fingerprint.

8. A retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 1, characterized in that, S4 specifically includes: Read the authorized near-field topology fingerprint, installation area identifier, and control domain identifier from the screen control verification record. Match the topology anchoring device in the authorized near-field topology fingerprint with the current topology anchoring device in the current near-field topology fingerprint according to device identifier, device type, control domain identifier, and near-field relationship level to obtain a matching details table and topology anchoring device consistency rate. The near-field relationship strength deviation value is calculated based on the matching details table, and a control domain conflict flag is generated based on the control domain identifier of the current topology anchoring device. The control authority verification results are generated based on the consistency rate of topology anchoring devices, the deviation value of near-field relationship strength, and the control domain conflict markers. Missing devices, abnormally added devices, and adjacent control domain identifiers are recorded.

9. A retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 2, characterized in that, S5 specifically includes: When the control verification result is passed, the edge network control node checks the device identifier, control domain identifier, request sequence number and allowed control command type in the WiFi access request or WiFi control request of the retail screen according to the WiFi access policy, and generates WiFi access token and WiFi control command release permission. The retail screen accesses the WiFi network within the corresponding control domain based on the WiFi access token, receives WiFi control commands, performs display updates, brightness adjustments, or power on / off control, and sends back a control execution record.

10. A retail screen WiFi control method based on Bluetooth intelligent scheduling according to claim 9, characterized in that, Also includes: If the pre-verification fails due to a failure in request timeliness, calibration version number, or control domain identifier verification, or if the current scan is insufficient due to insufficient scan sufficiency, or if the control verification result is unsuccessful, the generation of the WiFi access token and the release of the license will be refused, the request cache will be cleared, a cross-region control risk record will be generated, and the status pending review will be determined.

Images