Occupancy state-aware stadium venue standby scheduling system and method

Abstract

The application relates to the field of venue perception and device cooperative control, and discloses a stadium venue candidate scheduling system and method based on occupancy state perception. An edge state controller generates release evidence with a release generation according to continuous effective idle observation, and a candidate scheduling server establishes an exclusive candidate token with a binding release generation in combination with a use qualification and an available time period. When a candidate enters, the edge state controller initiates a sampling request with a current review mark, reviews a venue state only with newly collected observation after the request, and generates a time-limited execution permission. After the server confirms the exclusive occupation, the edge state controller rechecks whether the permission is not revoked, not used, the release generation, the local validity period and the occupancy state, and outputs an access execution instruction after the recheck is passed. The system and method are used for candidate position replacement of a stadium venue, and errors caused by buffer idle observation, state reversal and delayed instructions are inhibited.

Description

Technical Field

[0001] This invention relates to the fields of occupancy sensing, resource scheduling, and equipment collaborative control of sports venues, and in particular to a sports venue standby scheduling system and method that links site occupancy observation with standby admission execution. Background Technology

[0002] Independent courts within sports venues typically accept reservations by time slot. When a reservation is cancelled, the original user ends early, or a time slot becomes available, the venue can offer the corresponding court to a waiting list user. Because reservation records describe eligibility for use, while sensing devices describe actual occupancy, the update times and meanings of the two are different.

[0003] Chinese patent application CN108140224A discloses a technique for generating seat availability information from images and selecting seats, with the waiting reservation process also considering the estimated start time of vacancy. Chinese patent application CN120525250A relates to multi-source data, resource occupancy analysis, and resource scheduling for sports venues. The above disclosures indicate that occupancy information can be used as input for space reservation or scheduling.

[0004] When sensing devices, scheduling servers, and site execution terminals are connected via a network, there is a time interval between candidate allocation and actual admission. The idle records held by the server may have been overturned by new occupancy events, and observations resent after reconnection may have a more recent reception time, resulting in earlier actual acquisition. Simply checking for appointment conflicts or the idle status of the server cache does not indicate that the observations used by the edge state controller to output admission execution commands still correspond to the current site.

[0005] Furthermore, temporary user absences and the expiration of original usage eligibility require separate handling. If a site is released due to lack of observation while the eligibility is still valid, an unnecessary replacement may occur; if another candidate is provided immediately after the execution receipt is lost, the admission instructions corresponding to two eligibility statuses may be applied to the same site consecutively. Therefore, a clear constraint relationship needs to be maintained between the validity of idle observations, candidate eligibility, and site-side admission execution. Summary of the Invention

[0006] The technical problem to be solved by this invention is: in the case of asynchronous updates between stadium site occupancy observation and candidate admission, how to suppress the generation of admission instructions using cached idle observations or expired release criteria, and how to avoid continuing to perform conflicting admission processing on the same site when the execution result is uncertain.

[0007] To address the aforementioned technical problems, this invention provides a sports venue standby scheduling system based on occupancy status awareness, comprising a venue awareness node, an edge status controller, a standby scheduling server, and a venue execution terminal. The venue awareness node outputs observation records containing venue identification, acquisition sequence number, acquisition time, and validity information to the edge status controller.

[0008] The edge state controller forms continuous and valid idle observations based on a pre-configured set of necessary sensing nodes. After satisfying the idle confirmation duration, it generates release evidence containing a release generation. When an observation fails or the site becomes occupied, the original release evidence is invalidated and the release generation is updated at the site end. The candidate scheduling server combines the release evidence, the release conditions of the original eligibility, and subsequent reservations to determine the available time window, and establishes an exclusive candidate token bound to the release generation for candidate requests with compatible durations.

[0009] After a candidate user accepts the request, when the site execution terminal initiates an entry verification, the edge state controller sends a sampling request with a verification identifier to the set of necessary sensing nodes. Upon receiving the request, the sensing nodes collect new observations and associate the verification identifier with the collected records. Only when all necessary node return records are collected and verified within the preset response time limit, and all returned records are valid idle observations that meet the current request and the release generation remains unchanged, does the edge state controller issue a timed execution permission and send the permission identifier and its binding information to the candidate scheduling server.

[0010] The standby scheduling server re-verifies the token and exclusive placeholder, enters the execution preparation state, records the permission identifier, and returns a submission confirmation for the permission and token combination. The edge state controller processes the submission confirmation sequentially with the site's observation failure, timed failure, and permission revocation processes. If the permission has not been revoked, is a currently executable and unused permission locally, the local execution verification time is earlier than the permission expiration time, the release generation is still consistent, and the physical state is still valid and idle, the permission-used flag is successfully persisted first, and then the admission execution command is output; otherwise, the output is blocked. The site execution terminal updates the site admission indication according to the command, or drives the corresponding controlled channel to perform a release.

[0011] In one implementation, the set of necessary sensing nodes includes video sensing nodes and millimeter-wave sensing nodes. The nodes remain occupied when any valid source determines that there are people in the site. Idle observations are accumulated only when all necessary sources are valid, all indicate that there are no people, and the worst acquisition time span between nodes does not exceed the preset maximum acquisition time span. When there is no clear valid occupation and the idle status cannot be confirmed due to missing observations, exceeding age, or unclear attribution, the node is converted to unknown. The accumulated interval is cleared for both occupied and unknown nodes.

[0012] In one implementation, the release evidence, candidate token, and timed execution permission are also associated with the controller startup identifier and site space configuration version to distinguish the observation basis before and after controller restart and changes in site boundaries and sensor coverage configuration.

[0013] In one implementation, the standby scheduling server manages regular reservations and standby allocations using the same resource ledger, maintaining exclusive constraints on the same site and unique constraints on the same standby request using a valid token. During the execution preparation state, an exclusive vacancy is maintained; for unused permits, the corresponding execution preparation vacancy is only released after the edge state controller confirms that the permit is unused and has been revoked or expired; if a permit is used or its usage status is unclear, the command execution and access status are checked according to the permit revocation and execution result verification rules in this specification, and the vacancy is retained until a release conclusion is obtained. When an instruction has been output or the execution result is unclear, the system transitions to an entry pending confirmation or verification state.

[0014] The present invention also provides a sports venue standby scheduling method corresponding to the above system, which completes the standby access processing by generating release evidence, establishing standby tokens, performing post-request sampling verification, confirming exclusive occupancy, and performing time-limited execution verification at the venue.

[0015] Compared to processing that only uses server caching of idle states, this invention retains the determination of whether the release criterion is still valid at the site receiving real-time observations, and allows this criterion to be released via generation constraint candidate tokens and execution permissions. When a site changes from idle to occupied and then back to idle, the new idle state cannot restore the permission of the old generation, thereby preventing old instructions from regaining execution eligibility after state reversal.

[0016] This review identifier is associated with the observation when a new acquisition process is generated, enabling entry review to exclude seemingly fresh observations formed solely through re-receiving, forwarding, or re-marking of cached idle results. Combined with local license validity and pre-execution verification, this limits the use of licenses that are delayed after observation review is completed.

[0017] The execution preparation, entry pending confirmation, and usage status are recorded separately, and an exclusive occupancy is maintained when the execution result is uncertain, so that changes in occupancy after normal entry are handled differently from abnormal occupancy before unauthorized entry. The above effect comes from the control relationship, and does not rely on the premise that the sensing device has no missed detections or communication has no delays, nor does it take the reservation sorting rule itself as an improvement in sensing accuracy. Attached Figure Description

[0018] Figure 1 This is a schematic diagram showing the composition and communication connection of the system of the present invention;

[0019] Figure 2 A schematic diagram illustrating the process of generating and invalidating evidence for release;

[0020] Figure 3 An interactive diagram illustrating the process of verifying candidates' entry and ensuring a timely passage through the normal route;

[0021] Figure 4 This is a schematic diagram illustrating the normal state transition and exception handling entry point for the candidate token;

[0022] Figure 5 This is a schematic diagram of the process for revoking a license and verifying the execution result. Detailed Implementation

[0023] The embodiments of the present invention are described below with reference to the accompanying drawings. The configuration values ​​are all example values; specific parameters are set according to the acquisition frequency, communication latency, and site coverage conditions.

[0024] I. Site and System Configuration

[0025] See Figure 1 Each complete court with fixed spatial boundaries is defined as an exclusively allocable court, and different courts are distinguished by court identifiers. Taking an indoor badminton court as an example, the same court is occupied by only one reservation or waiting list qualification during overlapping usage periods. For facilities where full-court and half-court usage overlap, overlapping areas can be grouped into the same conflicting resource group in the resource ledger; this embodiment uses non-overlapping complete courts.

[0026] Site sensing node 1 is connected to edge status controller 2 via a wired or wireless data link; edge status controller 2 communicates with waitlist scheduling server 3; site execution terminal 4 communicates with edge status controller 2 and waitlist scheduling server 3. Edge status controller 2 is deployed on the site side, waitlist scheduling server 3 maintains reservation and waitlist records, and site execution terminal 4 is set outside the entrance of the corresponding site to prevent users who scan the code from entering the monitored site before verification.

[0027] Each site configuration requires a set of sensing nodes. A specific configuration includes a set of video sensing nodes covering the site and a set of millimeter-wave sensing nodes covering the site. When the coverage of a single node of a type of equipment is insufficient, multiple nodes of that type of equipment will jointly cover the site, and the set records the required coverage area corresponding to each node; only when all required areas have effective observations can idle observations be formed for automatic release.

[0028] The video sensing node receives images from a fixed camera, outputs the human object detector, along with the human category, detection confidence score, and bounding box. The midpoint of the lower edge of the bounding box or the detected foot point is used as the ground contact position. A projection mapping from the image plane to the ground plane is obtained using at least four, and any three of them are non-collinear, field control points. This position is mapped to field coordinates, and its assignment is determined by the inclusion relationship between the point and the field polygon. If the viewpoint does not meet the ground mapping conditions or the foot point cannot be reliably determined, the corresponding observation is invalid. The human detector provides the observation input; this embodiment does not change its training method.

[0029] Millimeter-wave sensing nodes output the presence of personnel or their coordinates based on radar echoes, which are then mapped to the same site coordinates after installation location and orientation calibration. Nodes without coordinate output are only used within their verified coverage areas. Field configuration ensures that the presence of stationary personnel is also considered a detection target; the absence of moving targets cannot be directly equated to the absence of personnel. Node outputs of self-test faults, coverage verification failures, missing communication heartbeats, or obstruction faults are all recorded in validity information.

[0030] An undefined zone is established along the site boundaries. If a human or radar target falls within this zone and its affiliation cannot be determined, the target is not forcibly assigned to any site. For each adjacent site involved, if there is another area with clearly defined and valid manned observations, it is considered occupied; otherwise, it is considered unknown because its vacancy cannot be confirmed. The width of the undefined zone is set according to the allowable limits of calibration error and equipment position error. When the configuration changes, the site space configuration version is updated, and vacancy evidence is re-established.

[0031] Each observation record includes a site identifier, node identifier, node activation identifier, site spatial configuration version, monotonically increasing acquisition sequence number, acquisition time, occupancy value, and validity information; the return record used for this entry verification is also associated with the verification identifier. The occupancy value indicates whether the site is occupied or unoccupied; invalid observations are not interpreted as unoccupied. The node activation identifier changes when the node restarts, and the acquisition sequence number is not reused within the same startup. The edge state controller also records the reception time, but does not use the reception time to replace the acquisition time.

[0032] II. Evidence of Continuous Idleness and Release

[0033] See Figure 2The edge state controller 2 fuses the records of the necessary sensing node set according to a preset cycle. When any valid record indicates that someone is in the site area, the site's physical state is occupied; when all records of the necessary nodes are valid, the time span is within the allowable range, and all indicate that no one is present, the current fused observation is a valid idle observation; otherwise, it is unknown. When there is a conflict between a person's observation and an unoccupied observation of a healthy device, it is treated as a person's observation, and the conflict record is retained. Clearly valid occupancy takes precedence over unknown factors such as unclear boundary attribution; when the same node simultaneously has a clearly defined target within the site and a target with unclear boundaries, the former's valid person's observation is retained, while the latter is only prevented from forming an idle conclusion.

[0034] The node acquisition times are mapped to the monotonic time base of the edge state controller, and an acceptable clock mapping error is set. For a fixed site, the required set of nodes is denoted as... , No. The time for determining the next fusion is ,node The time of acquisition after mapping is The upper bound of the mapping error at the acquisition time is The maximum allowed age for data collection is For manned observations, a clearly defined region attribution means that at least one valid target is clearly located at the site; for unmanaged observations, it is also required that there are no undefined targets involving the site. When a node is healthy, meets the region attribution conditions according to the above rules, and its upper error limit does not exceed the configured limit, its data collection age must also satisfy equation (1); if any condition is not met, the node's validity value... The value is 0 when all conditions are met, and 1 when all conditions are met. The upper bound of the error, the age of data collection, and the time span described below are all measured in seconds.

[0035] (1)

[0036] To form an effective idle fusion observation, the effective unmanned records of each necessary node should also satisfy the worst-case acquisition time span constraint of equation (2). When there are effective manned observations with clear regional affiliation, they are still judged as occupied according to the aforementioned priority rule for effective manned observations, and are not reclassified as unknown due to the acquisition time span of other nodes exceeding the limit. Among them, This is the preset maximum data acquisition time span. The possible intervals corresponding to the node acquisition times are: to Therefore, a conservative verification is performed by subtracting the earliest interval endpoint from the latest interval endpoint. In equation (2), node indexes are used... The maximum and minimum values ​​for each index are both in the set of required nodes. The value is taken from the top; subsequent formulas only apply to values ​​that are also indexed by nodes. The terms that take extreme values ​​are taken from this range, while other maximum and minimum values ​​are taken from the time or duration expressions listed in the formula.

[0037] (2)

[0038] Record node occupancy value A value of 1 indicates someone is present, and a value of 0 indicates no one is present; fused observations Determined by equation (3), the values ​​1, 0, and −1 represent occupied, effectively idle observations, and unknowns, respectively. In the equation, "all" and "exist" refer to the required set of nodes. ; The time span is defined by equation (2).

[0039]

[0040]

[0041] (3)

[0042] Duplicate or out-of-order records do not overwrite the current record. A new fusion sample for accumulating duration is only formed when all necessary nodes provide a collection sequence number higher than the last recorded record; repeatedly performing fusion on the same set of records does not extend the idle time. The fusion determination number is retained, numbered... When a new fusion sample is formed by the next fusion determination, the time of that determination is used. Update cumulative; the fusion determination number corresponding to the first new fusion sample in the current continuous valid idle sample segment is: The confirmed idle time is updated only when a new fused sample is formed, according to equation (4). All fused observations within this sample segment are 0, and the time interval between adjacent new fused samples does not exceed the allowable interval. The startup identifier and spatial configuration version remain unchanged. If any condition is not met, someone is observed, the observation period expires, or the timed check finds that the allowed interval has been exceeded, the sample segment and old evidence are immediately cleared; if the current new sample is effectively idle, the sample segment can be re-established from the sample, and the duration is 0.

[0043] (4)

[0044] For confirmed idle time, Idle confirmation duration, Take a positive value. Only... Furthermore, evidence for release can only be formed while the current necessary observations remain valid. This has not yet been achieved. Unattended observations are only used for accumulation and do not indicate that the site release conditions have been met. Timers and observation events enter the same site processing queue, allowing evidence invalidation to be triggered even in cases of aging without new information.

[0045] Edge state controller 2 stores the release generation for each site. During a continuous period of valid idle time, the release generation remains unchanged; once existing release evidence is overturned due to occupancy, observation failure, or configuration change, the original evidence is invalidated, and the release generation is incremented. Subsequent valid idle evidence is then re-established using the incremented generation. Repeated reception of the same fault in an unknown state does not require repeated incrementing, and refreshing consecutive valid idle observations does not change the generation.

[0046] Release evidence includes site identifier, edge state controller activation identifier, release generation, site space configuration version, start and end times of continuous idle intervals, and the latest acquisition sequence number and acquisition time of each necessary node. When the edge state controller restarts, it changes the activation identifier and sets the physical state to unknown. Even if the release generation is recounted from the initial value, the old evidence cannot be used because the activation identifier is different.

[0047] The standby scheduling server 3 records the physical status of the venue and the original usage eligibility. The release conditions for the original usage eligibility are only met when there is no currently valid reservation, the original reservation has been cancelled, the original user's early termination record submitted through identity verification has taken effect, or the reservation has expired and there are no renewal reservations; simultaneously, maintenance locks and existing exclusive allocations are checked. If a user briefly leaves the venue within a valid reservation period without a valid termination record, their usage eligibility is maintained.

[0048] A physical state of "valid idle" only proves the existence of perceptual evidence that can be used for further verification, not that the eligibility has been released. Before establishing a token, the candidate scheduling server 3 verifies the release evidence against the current reservation eligibility version, maintenance status, and resource ledger. Changes in reservation eligibility or maintenance status invalidate old candidate eligibility that has not yet entered the execution preparation state through resource ledger version control. For candidates that have already entered the execution preparation state, maintenance lock changes first prohibit new allocations in the resource ledger, while simultaneously maintaining the old token and requesting the revocation of the corresponding license. The revocation and execution results are then verified according to the license revocation and execution result verification rules in this manual.

[0049] III. Available Time Windows and Waiting Tokens

[0050] A waitlist request includes a request identifier, user identifier, on-site check-in record, acceptable venue set, allowed start time range, and minimum usage duration. Check-in terminals can be set up in fixed waiting areas, with the upper bound of the route time between the terminal and the venue serving as the configuration input for arrival time estimation. Each waitlist request can hold at most one valid waitlist token at any given time.

[0051] Record the current time when a substitute is provided. The estimated time for the completion of the site handover is alternate users The allowed duration is The upper bound of the time taken to reach the destination is The upper bound of the total configuration time required for access instruction transmission, release, and entry preparation is: The shortest usage time is The allowed start time range is to The total duration is conservatively calculated from the time the user arrives, the venue is handed over, and access can be submitted. Waiting list start time. Determine according to formula (5); if the user requests a later start, allow until... Start using it again. Note the earliest of the following times: reservation start time, maintenance start time, and closing time. The end handover retention time is Available endpoint Determine according to formula (6).

[0052] (5)

[0053] (6)

[0054] A current candidate request is considered feasible only if the user accepts the current location, the original usage rights have been released, there is no maintenance lock, exclusive occupancy is possible, and equation (7) is satisfied. The permitted starting range should satisfy... ;like If the remaining interval is insufficient for the minimum usage time, the allocation will be rejected.

[0055] (7)

[0056] All the above times use the same server time base; the duration is non-negative, and the minimum usage duration is specified. If there is no next reservation or maintenance plan, only the earliest value is taken from the existing boundary and closing time. The end point of the closing or allowed opening interval must exist. First, the handover completion estimate is used; if the actual handover is not completed, the admission instruction cannot be output, and if the actual completion is late, the actual time is used for recalculation. The three stages of providing candidates, accepting candidates, and submitting entry are respectively calculated using Equation (5) or Equation (8), and the already completed acceptance and arrival processes are not counted repeatedly.

[0057] In equation (8), For the actual moment of acceptance, This is the time of this verification submission. , These represent the start time of the recalculation in each of the two phases, and the arrival time, respectively. The calculation begins upon acceptance and ends when the user arrives at the time of verification submission. The server replaces the start time of the recalculation in equation (7) with the start time of each phase. At the same time, verify the corresponding acceptance and arrival deadlines. This refers to the upper limit of the total configuration time required for the transmission, release, and entry preparation of the access instruction. If the service has not started by the scheduled start time, the remaining time must be checked again to ensure it does not encroach on subsequent reservations. This upper limit of the total configuration time is used for window verification and is not considered the valid duration of the time-limited execution permit. The output of the access instruction and the terminal release must still meet the expiration limits in the local execution verification and terminal execution period rules, respectively. Entry preparation after release can be completed within the preparation period reserved at the window and will not extend the already issued permit.

[0058]

[0059] (8)

[0060] When creating a candidate token, the resource ledger is pre-empted from the expected time of arrival and start of preparation to the available end point. The reserved time interval must be locked; the preparation or waiting phase must not overlap with other reservations if only the minimum usage duration is locked. Upon acceptance and submission, the reserved time interval is recalculated and checked for overlap with other regular reservations or waitlists. Any necessary extensions must succeed within the same resource transaction; failures will result in no admission permission being submitted. The minimum usage duration is used to verify whether the currently available time window satisfies the waitlist request and does not automatically become the basis for re-allocating subsequent time slots for that venue. The end point of the reserved time interval is used for planned allocation and is not a condition for automatically releasing the reservation when preparation or execution results are uncertain; the release of such reservations is still handled according to the permission revocation and execution result verification rules in this specification.

[0061] The backup scheduling server 3 can select from feasible requests in ascending order of submission time. If submission times are the same, the order is determined by the request identifier. Requests that do not meet the requirements of the current window retain their original submission time and wait for other windows. The sorting rule is configured for request selection and does not change the determination of the validity of released evidence.

[0062] The standby scheduling server 3 uses the same resource ledger to handle both regular reservations and standby allocations. When creating a token, it locks the resource record and standby request record for the corresponding venue within a serialized transaction, checks that the intended allocation interval does not overlap with existing intervals and that the request has no other valid tokens, and then simultaneously writes the venue placeholder and standby token. When using mutually exclusive resource groups, the entire conflict group is locked according to a fixed resource identifier order.

[0063] The standby token includes a token identifier, standby request identifier, site identifier, release generation, controller activation identifier, space configuration version, reservation eligibility version, intended usage range, and acceptance and arrival deadlines. The token identifier is unique in this allocation. Notifications are sent only after the transaction is committed, and resentments reference the same token. Upon acceptance, the validity period, bound evidence, and remaining usage time are checked again; upon successful acceptance, the status changes to "accepted."

[0064] The transaction version of the resource ledger is updated with allocation operations, while the release generation is only updated when the physical release basis becomes invalid; the two are maintained separately. Changes in the transaction version caused by creating a candidate token do not change the physical release generation, thus preventing transaction version updates due to resource locking from incorrectly determining that an established candidate token has become invalid.

[0065] IV. Entry verification and time limit implementation

[0066] Figure 3 This shows the normal path, where vertical dashed lines represent the lifelines of each participant, horizontal arrows represent message passing, and rectangles represent the local processing of the corresponding participant. See also Figure 3 The standby user presents the token-corresponding credentials at the site execution terminal 4 outside the site boundary. The standby scheduling server 3 verifies the association between the credentials and the accepted token, and sends a verification request containing the token and its bound version to the edge state controller 2. The edge state controller 2 verifies that the site identifier, start identifier, space configuration version, and release generation are consistent with the current ones, and that the physical state is still valid and idle. Then, it generates a non-reusable verification identifier for this verification.

[0067] Edge state controller 2 records the current start identifier and corresponding acquisition sequence number baseline of each necessary sensing node, and sends sampling requests containing the current review identifier and the corresponding baseline to these nodes. The node start identifier returned in the record should be consistent with the start identifier of the current record. After receiving the sampling request, the node schedules the next actual acquisition. The sequence number of the acquired record is greater than the baseline, and the current review identifier is associated with the record when it is generated. For continuously running cameras, a new image with an exposure start time no earlier than the time the node receives the current request is selected; for radar, a new measurement cycle with a measurement start time no earlier than the time the node receives the current request is selected.

[0068] Nodes must not retrieve previously unattended results from existing caches and only append a verification identifier before returning them. If a sensor cannot directly identify the verification identifier, the node adapter program located at its acquisition interface controls the acquisition barrier: first, it records the arrival of the request and the underlying frame sequence number; then, it only receives frames acquired after the barrier and whose acquisition time meets the requirements, and associates the verification identifier when forming an observation. Devices that cannot obtain the above acquisition sequence relationship are not used for automatic admission verification.

[0069] Edge State Controller 2 verifies the review identifier, node start identifier, spatial configuration version, acquisition sequence number, and acquisition time of each returned record. The review passes only if all necessary nodes have returned valid unattended observations acquired after this request, the acquisition time span between nodes does not exceed the configured value, the local time from initiating the review to collecting and completing the verification of all returned records does not exceed the response time limit, and the original release generation remains unchanged. An execution license is not generated if any necessary result is missing, if someone is returned, or if a quality failure occurs.

[0070] by This indicates the status of the review. This indicates that the node returns an identifier associated with the record. This indicates the collection sequence number of the returned record. Indicates the baseline of this sequence number. Indicates the local time when the node received the request. This indicates the local time at which the actual sampling of the record began. The node side associates the record using formula (9); and A monotonic clock from the same node eliminates the need for direct comparison of wall clocks from different devices. A larger sequence number cannot replace the actual sampling start time to meet the requirements.

[0071] (9)

[0072] Record the local time when the edge state controller initiates the review as The local time when all records are collected and the verification is completed is The review response time limit is In addition to all nodes satisfying the valid idle requirements in equations (1) to (3), equation (9), and the binding generation remaining unchanged, equation (10) must also be satisfied; if any required return value is missing, the pass / fail judgment will not be entered.

[0073] (10)

[0074] After the review is approved, the edge state controller 2 saves the time-limited execution license locally, which includes a license identifier. This review includes the following identifiers: identifier, token identifier, venue identifier, release generation, activation identifier, space configuration version, and local expiration time. Let the configuration license duration be... ,but Determined according to formula (11). Where... The nodes actually used in this review The time of acquisition after the observation is mapped is fixed during calculation; subsequent new observations cannot extend the existing permit. No later than the earliest failure time under the conservative collection age constraint of this review observation; if If the license is not issued, the expiration date will be determined entirely using the controller's monotonic clock. After a license is granted, the edge state controller 2 sends the license identifier and its associated verification identifier, token identifier, site identifier, release generation, start identifier, and space configuration version to the candidate scheduling server 3 for generating a submission confirmation for the license and token combination; the license expiration and usage status are still maintained by the edge state controller.

[0075] (11)

[0076] For the same site and candidate token, Edge State Controller 2 retains only one currently pending review or unfinished execution permit. When the same entry request is resent, the original review identifier and current processing result are reused, and multiple valid permits are not generated in parallel. If re-review is required, the original permit is first invalidated and feedback is provided, and then a new review identifier is created. If the original permit has been used or its usage status is unclear, the command execution and access status are first checked according to the permit revocation and execution result verification rules in this manual. The invalidation of the original permit should not be used as the basis for reissuing the execution permit. During local execution, it is also checked that the received permit identifier is the currently saved permit identifier.

[0077] In the resource transaction, the standby scheduling server 3 verifies that the token is still in an accepted state and has not timed out, the venue is still exclusively held by the token, the reservation qualification version has not changed and there is no maintenance lock, and recalculates the remaining usage window using the actual current time. If successful, the token is switched to the execution preparation state, the permission identifier is recorded, and a submission confirmation is output. The submission confirmation only applies to this permission and token combination and cannot be used as permission for other requests.

[0078] Edge state controller 2 uses a serial event processing queue for the same site. Observation state updates, timed failures, permission revocations, and execution verifications are all processed in this queue. After receiving the submission confirmation, it calculates whether the pre-execution verification has passed according to equation (12). In the equation, This is a value that passes the pre-execution validation. This indicates that the license has not been revoked, is still a locally executable license, and that the license identifier, bound token, site, launch, configuration, and release generations all match; if any of these conditions are not met, the value is 0. This indicates that confirmation has been received from the server regarding the license and token combination. This is a permission flag; it is 0 when not in use. This is the local execution verification time using the monotonic time base of the edge state controller; This indicates that the latest necessary observations are still valid, the merged status is idle, and the continuous confirmation conditions are still met. Each logic value is either 0 or 1. This represents a logical AND operation. A pass value of 1 does not indicate that the admission command has been output or executed; the admission execution command containing the command identifier will only be output after the verification passes and the flag is successfully persisted to 1. Otherwise, output will be blocked. When the persistence or command execution status is uncertain, a placeholder is maintained and verified according to the license revocation and execution result verification rules. The command identifier and license identifier are one-to-one. Once a license is revoked, it exits the executable state, and the revocation result is persisted before the feedback server; delayed old submission confirmations, duplicate entry requests, or duplicate review results cannot restore the executable state of the license.

[0079] (12)

[0080] When a new manned event, quality failure, observation aging, or configuration change is processed locally before the submission confirmation, the updated release generation or invalid status will cause the license to fail verification. Even if the failure event has not yet been sent to the alternate scheduling server 3, the site will directly reject the old license. If the site later becomes idle again, the old license will still be invalid due to the different release generation.

[0081] Upon receiving the access execution command, the site execution terminal 4 updates the site access indication or drives the controlled channel corresponding to the site to perform a single access release. When using a controlled channel, the execution terminal should support querying the execution status by command identifier, deduplicating duplicate commands, and checking the command execution deadline. The electronic sign implementation outputs an access indication, which does not imply that it can physically prevent others from entering. Neither implementation uses suddenly turning off the lighting of the site in use as an access control method. The command also carries the site, permission, command identifier, and execution deadline, which is taken as the local permission expiration time stored by the controller. When using a controlled channel, the execution terminal maps the deadline given by the controller to the monotonic time base of the execution terminal through a verified clock mapping, and then subtracts the upper bound of the mapping error expressed by the time base to obtain a conservative deadline for terminal verification; access is only granted when the terminal's local time is earlier than the conservative deadline and the command has not yet been executed; expired or overdue commands are rejected and feedback is provided. If the mapping fails or the execution terminal does not have the above-mentioned status query, deadline check, and command deduplication capabilities, automatic access is stopped, and verification is initiated. The above checks cannot replace site observations and are still limited by sampling intervals and actuator action delays.

[0082] The permission usage flag is used to limit the number of times the same permission command can be output. If a failure occurs after the flag is persisted but before actual execution, the permission usage flag should be retained, and the terminal execution status should be checked first. The permission execution command should not be resent if the execution status is unclear. This may result in a situation where permission is not executed and verification is required, but an uncertain result will not be interpreted as permission for another person being generated immediately after it was never executed.

[0083] Rules for License Revocation and Verification of Execution Results

[0084] See Figure 5Once the execution readiness state is established, the server must not immediately release resources due to user cancellation, notification timeout, or other reservation requests. The server requests the edge state controller to revoke the license. The revocation request and execution verification are processed sequentially in the same field queue. Only when the license usage flag is still 0 can the controller set the license to non-executable, persist the revocation result, and then return "unused and revoked". Upon expiration, the usage flag must also be queried and "unused and expired" confirmed. The server can only release the execution readiness placeholder after receiving one of these confirmations. If the usage flag is already 1, even if the license subsequently expires or the release generation changes, the above-mentioned unused confirmation cannot be made. The command execution and pass status must be checked. Exclusive placeholders are maintained until a release conclusion is obtained after verification, preventing commands that have been issued but are still in the link or execution queue from conflicting with the next candidate. During verification, if the terminal clearly indicates that the old command was not executed or was rejected, and confirms that its execution deadline has passed and it can no longer be executed, and there is no corresponding passage record and continuous valid free evidence has been obtained again, then the old qualification can be revoked and the release conditions can be re-checked. If the supplemented execution, passage, and occupancy records can be linked, then it can be put into use. If the evidence is still incomplete, the occupancy will continue, and the site personnel will verify the invalidation of the old command and the actual site status before processing. Maintenance lock changes also trigger the above revocation request: when revoking the first processing, it blocks the subsequent old submission confirmation; when the execution verification has passed and the use flag is set to 1, it will switch to command and passage verification, and the use flag cannot be rolled back or the old occupancy can only be released due to the maintenance lock. When the maintenance lock still exists, even if the old occupancy has been released according to the above verification, the site cannot be reassigned.

[0085] The review, submission confirmation, and execution status messages contain the sender's identity and session association information, and are transmitted through an authenticated communication channel. Execution status messages include the command output status associated with the license identifier and command identifier, and the terminal execution result: the command output status is fed back by the edge status controller, and the terminal execution result is fed back by the site execution terminal; the server updates the candidate token status based on the verified corresponding status record. If no clear result is received, the original placeholder is maintained, and processing is carried out according to the license revocation and execution result verification rules. Offline release with cached credentials is not accepted when the link is interrupted. The review identifier is used to constrain the order of observation acquisition and does not replace observation validity and authentication with a random identifier itself.

[0086] V. Status Feedback and Anomaly Recovery

[0087] See Figure 4In the normal access path, the candidate token sequentially goes through the states of Provided, Accepted, Execution Preparation, Access Pending Confirmation, and In Use. After the access execution instruction has been issued, the site is maintained and the site enters the Access Pending Confirmation state; if a change in occupancy occurs before execution preparation, the old candidate qualification is revoked and the release conditions are reassessed; if execution preparation has begun but no instruction has been issued, the candidate qualification expires but the exclusive occupancy is not released, and a request to revoke the permit should be made, and the status is unclear, requiring verification; after the instruction has been issued, the occupancy is not released individually if the qualification expires or the permit expires, but must be verified in conjunction with execution and access feedback. Figure 4 This shows the entry points for normal state transition and exception handling. Figure 5 List two exit verification paths: one for unused licenses that have been revoked or expired, and the other for licenses that have been marked as used but whose commands have not been executed and cannot be executed again. The latter path must also have no corresponding access records and obtain continuous and valid free evidence again, retain the used mark, and after removing the old occupancy, still need to jointly check the eligibility for use, maintain the lock, and release evidence.

[0088] When using an independent controlled channel, the terminal verifies the token corresponding to the credential, records the access feedback for the same command, and matches it with changes in site occupancy that occur after the access and within a specified associated time limit. The sequence is based on the actual occurrence order of the access event and the occupancy change, not the order in which the two types of feedback messages are received. Only when the credential access record and the occupancy change can be correlated is the token put into use. If an unknown person occupies the site first, without credential access feedback, or if the feedback does not match, the system enters a verification state and maintains site occupancy; this occupancy is not considered as fulfillment of the waiting user's obligation. Once the completed execution, access, and occupancy records can be correlated, the process follows the aforementioned permission revocation and execution result verification rules.

[0089] When there is no uniquely associated controlled access point for an open area, anonymous occupancy observation only indicates that someone is currently in the area and cannot determine who entered. On-site credentials or staff confirmation can be linked to waitlist tokens; the area remains in a pending confirmation or verification state until confirmation is obtained. Even with the above confirmation methods, the access instructions output by the system are not interpreted as physical isolation of the open area.

[0090] Tokens that have been offered but not accepted are revoked at the acceptance deadline, and tokens that have been accepted but have not yet entered the execution preparation state are revoked upon reaching the deadline. After revocation, the current physical status and release evidence are checked, and tokens are only offered to the next candidate if the conditions for valid idleness and eligibility for use are met again. For execution preparation or entry pending confirmation status, the permission and command status are checked first, and the absence of the site is not assumed due to a simple timeout.

[0091] Once in use, a brief period of vacancy only changes the physical status and does not automatically terminate the usage privilege. Upon receiving an authenticated early termination record, or after the usage period expires, a combined judgment is made regarding physical vacancy and privilege release. If someone is still available by the expiration date, the system remains in an unfillable state and displays a timeout notification.

[0092] When a necessary sensing node restarts, its node startup identifier changes, and the corresponding old observations and old verification return records cannot be used for the current judgment. Based on this, the edge state controller invalidates release evidence and unused permits that depend on old observations, clears the accumulated continuous idle time, and reconstructs the observation records. When the edge state controller itself restarts, its startup identifier changes, and the site physical state is first set to unknown. Old release evidence, old verification results, and old permits cannot be restored to an executable state. For cases where permits have been used or the execution result is uncertain, the server maintains its original occupancy, first verifying the command and access status; only after a release conclusion is reached, continuous valid idle time evidence is obtained again, and the conditions for release are met, are candidates provided again.

[0093] VI. Configuration and Timing Examples

[0094] A configuration for illustrating the process uses fusion observation once per second, allowing the latest observation acquisition age to be 2 seconds, the maximum interval between adjacent fusion observations to be 1.5 seconds, the effective acquisition time span between nodes to be 1 second, and the continuous idle confirmation duration to be 20 seconds; the current review response time limit is 2 seconds, the configuration permission duration is 2 seconds, and the actual expiration time is taken as the earlier boundary according to formula (11). When the clock mapping error exceeds 0.1 seconds, the observation of the corresponding node is marked as invalid; the site physical status is still determined according to formula (3), that is, it is occupied when there are other valid manned observations, otherwise it is unknown when the effective idle condition cannot be met. The actual deployment should set these values ​​according to the equipment sampling and field link to make the response time limit cover the normal acquisition, return and verification process, while restricting the use of expired results.

[0095] To illustrate the calculation of available windows, assume the venue meets the conditions for continuous vacancy and early termination at 18:22, and the handover is also completed; the next reservation starts at 19:00, with a 2-minute handover period at the end, making the available end point 18:58. The waiting list user is allowed 1 minute for acceptance, 2 minutes for arrival, 1 minute for access instruction transmission, release, and entry preparation (upper limit of the total time). Requesting a minimum usage of 30 minutes, the waiting list start time is 18:26, and the minimum usage end time is 18:56, satisfying the window conditions. A waiting list request of 35 minutes under the same conditions does not satisfy this window. Alternatively, suppose the handover is actually completed at 18:30, with other conditions remaining unchanged and the user's allowed start range covering this time period, then the earliest start time for the waiting list is 18:31; the 30-minute usage will end at 19:01, exceeding 18:58, and the waiting list cannot be provided. If the earliest allowed start time is 18:40, then the minimum usage time will be calculated from 18:40. If the available end time is still 18:58 and the minimum usage time is still 30 minutes, the minimum usage end time is 19:10, therefore this alternative cannot be provided. The aforementioned 1 minute is the upper limit of the total time reserved in the window for instruction transmission, release, and entry preparation. Delaying the execution of a single admission instruction by 1 minute is not allowed; each instruction must still meet the permission and terminal expiration restrictions in the local execution verification and terminal execution period rules.

[0096] Example of continuous idle confirmation: New fused samples are generated once per second from 0 to 20 seconds. All samples are validly idle and meet the interval limit. When the 21st sample arrives, the accumulated time is 20 seconds, reaching the confirmation threshold. If an unknown observation is processed at the 12th second, the previous accumulated time is immediately reset to zero, and the complete confirmation time is re-accumulated at least once more. Repeating the same sequence number 20 times does not constitute 20 seconds of continuous evidence. Example of permission: When verification passes, the local time is 100 seconds, the configured permission duration is 2 seconds, and the earliest valid observation deadline is 101.2 seconds. Therefore, the permission deadline is set to 101.2 seconds. Output is rejected when the verification execution time equals 101.2 seconds.

[0097] Assuming the candidate token binding and release generation is 12, the required node collection sequence numbers before this review are 100 and 200, respectively, and the review identifier is Q1. Nodes should return records with collection sequence numbers greater than their respective baselines and whose actual collection occurred after the Q1 request. If the received data after reconnection is an unattended observation prior to the request, even if the received time is more recent or contains other review identifiers, the Q1 review cannot pass.

[0098] If, after Q1 review is approved but before confirmation is received, the controller detects someone in the area, the release basis for generation 12 becomes invalid and the generation increments. Even if the server retains generation 12, it cannot enable the old license to be executed at the site. The newly formed idle evidence after the personnel leave belongs to a new release generation, and the old Q1 license does not become effective again.

[0099] If the permission verification passes and the instruction has been output, and a matching credential access feedback and a change in room occupancy are subsequently received, the token enters the "in use" state. If only a change in occupancy is received but access feedback is missing, the token remains in exclusive occupancy and is verified. This distinction avoids misjudging a change in occupancy caused by a candidate user's normal entry as a failure event that should be released to the next candidate.

[0100] This implementation method constrains the execution eligibility under the observed state and message processing order. If the sensing device simultaneously misses detection, or if unauthorized personnel enter or enter an open area before the sampling interval has been observed, this cannot be eliminated solely by version checks; the system will stop automatic replacement and retain the verification state after detecting the anomaly. Therefore, the specific effect should be adapted to the sensing coverage and execution terminal capabilities.

[0101] VII. Implementation of the corresponding methods

[0102] Under the same inventive concept, the corresponding method first involves site sensing nodes collecting and marking occupancy observations, then establishing continuous free intervals by the edge state controller, and generating release evidence after a preset free confirmation duration is reached; then, the candidate scheduling server jointly verifies the eligibility for use and the available time period, and establishes exclusive tokens binding the release generation for feasible candidates.

[0103] Upon receiving an entry request with an accepted token, the edge state controller initiates a sampling request with a verification identifier. Within the response time limit, it collects and verifies all necessary node return records. After confirming the request, if the newly collected valid idle observations and binding generations still meet the requirements, a timed execution permit is formed, and the permit identifier and its binding information are sent to the server. The candidate scheduling server confirms that the token still exclusively holds the site, records the execution preparation and permit identifier, and returns a submission confirmation for the permit and token combination. The edge state controller verifies in its local serial processing sequence that the permit has not been revoked, is a currently executable and unused permit, the local execution verification time is earlier than the permit expiration time, and the generation and physical state. If the verification passes and the used flag is successfully persisted, the access execution instruction is output; otherwise, the instruction is blocked. The site execution terminal updates the access indication or performs a release according to the instruction and completes the entry or verification process according to the feedback.

[0104] The aforementioned data processing functions are implemented through a processor, memory, and communication interface. Site observation, release evidence, tokens, permissions, and command status are stored separately and associated with their respective identifiers; failure events and execution verifications are arranged in the same site serial queue, and ordinary reservations and waitlists are arranged in the same authoritative resource ledger, constituting the implementation method for maintaining the aforementioned control relationship.

Claims

1. A sports venue standby scheduling system based on occupancy status awareness, characterized in that, This includes site sensing nodes, edge status controllers, backup scheduling servers, and site execution terminals; The site sensing node is used to collect occupancy observations of the corresponding site and output observation records containing site identifier, collection sequence number, collection time and validity information. The edge state controller is used to determine the physical state of the site based on the observation records of the pre-configured set of necessary sensing nodes. When the continuous effective idle observation meets the idle confirmation time, it generates release evidence containing the site identifier and release generation. When the observation fails or the physical state of the site changes to occupancy, it invalidates the release evidence and updates the release generation. The standby scheduling server is used to combine the release evidence, the release conditions of the original usage qualification and the subsequent reservation to determine the available time window of the venue, select a standby request whose usage duration is compatible with the available time window of the venue, establish an exclusive standby token that binds the venue identifier and the release generation, and receive the acceptance information of the corresponding standby user. The edge state controller is also used to respond to the entry verification initiated by the site execution terminal for the accepted candidate token, and send a sampling request with the current verification identifier to the set of necessary sensing nodes; after receiving the sampling request, each necessary sensing node collects new occupancy observations, and returns them after associating the current verification identifier when forming the observation record; Only when all necessary sensing node return records are collected and verified within the preset response time limit, and each return record corresponds to the current review identifier, is a valid idle observation, and the release generation bound to the candidate token is still the current release generation, a time-limited execution permit is generated that binds the current review identifier, candidate token, and release generation, and the permit identifier and its binding information are sent to the candidate scheduling server. The standby scheduling server is also used to, after confirming that the standby token is valid and the site is still exclusively held by the standby token, switch the standby token to the execution preparation state, record the permission identifier and output a submission confirmation for the combination of the permission and the standby token, and maintain exclusive site occupancy for the execution preparation state; when the corresponding time-limited execution permission has not been used, the occupancy is allowed to be released only after receiving feedback from the edge state controller confirming that the permission has not been used and has been revoked or has not been used and has expired; when the corresponding permission has been used or the usage status is unclear, the command execution and passage status are checked, and the occupancy is maintained until a release conclusion is obtained; The edge state controller is further configured to, upon receiving the submission confirmation from the candidate scheduling server, verify in the serial processing sequence of the same site that the timed execution permit has not been revoked, is a locally executable and unused permit, the local execution verification time is earlier than the local expiration time of the permit, the release generation has not changed, and the site's physical state is still validly idle. After the verification passes and the permit has been successfully persisted as a used permit, the controller outputs an admission execution instruction to the site execution terminal; otherwise, it blocks the admission execution instruction. The site execution terminal is configured to update the admission indication of the corresponding site according to the admission execution instruction, or drive the controlled channel corresponding to the site to perform a release.

2. The sports venue standby scheduling system according to claim 1, characterized in that, The necessary set of sensing nodes includes video sensing nodes and millimeter-wave sensing nodes; the video sensing nodes map the human body detection location to a pre-calibrated site area, and the millimeter-wave sensing nodes map the human presence detection results to the same site area. The edge state controller determines the physical state of the site as occupied when any valid observation indicates that there is someone in the site area. When all observations of the necessary sensing node set are valid and indicate that there is no one, and the worst acquisition time span between nodes determined according to the acquisition time of each observation and the upper bound of its clock mapping error does not exceed the preset maximum acquisition time span, the current fused observation is determined as a valid idle observation. If neither of the above two conditions is met, the physical state of the site is determined to be unknown.

3. The sports venue standby scheduling system according to claim 2, characterized in that, The edge state controller clears the cumulative interval of continuous idle observations when the observation and acquisition age exceeds the allowable age, the interval between adjacent effective observations exceeds the allowable interval, or there is a detection target with unclear site boundary ownership. When the edge state controller initiates this sampling request, it records the node start identifier of each necessary sensing node and the baseline of the collection sequence number within the same start, and includes the corresponding baseline in the sampling request. The node start identifier in the observation record returned by each necessary sensing node is consistent with the node start identifier of this record, and has a collection sequence number greater than the corresponding baseline. The observation occupied by this node is a newly collected observation after the node receives this sampling request. The verification identifier is associated with this observation when the observation record is formed. Cache observations collected before the request are not returned as records for this verification.

4. The sports venue standby scheduling system according to claim 1, characterized in that, The release evidence, candidate token, and timed execution permission are also bound to the start identifier of the edge state controller and the site space configuration version. When the edge state controller restarts or the site space configuration changes, it sets the site physical state to unknown and invalidates the previously formed release evidence and timed execution permission. After obtaining continuous and valid idle observations that meet the idle confirmation duration, it generates new release evidence.

5. The sports venue standby scheduling system according to claim 1, characterized in that, The conditions for releasing the original usage qualification include any one of the following: no current valid reservation, the original reservation has been cancelled, the early termination record verified by the original user has taken effect, or the original reservation has expired and there is no renewal reservation, and the venue is not in a maintenance lockout state at the same time. If the original reservation is still valid and the release conditions are not met, the standby scheduling server retains its original eligibility and prohibits the creation of the standby token solely based on unattended observations.

6. The sports venue standby scheduling system according to claim 1, characterized in that, The standby scheduling server will subtract the end handover retention time from the earliest of the next reservation start time, maintenance start time, and closing time to obtain the end point of the available time window for the venue. The estimated arrival time is determined based on the current time, the allowed waiting time, and the upper limit of the arrival time. The later of the handover completion time and the estimated arrival time is added to the upper limit of the total configuration time required for admission instruction transmission, release, and entry preparation. This is then compared with the earliest time allowed for the waiting user to start, and the later one is taken as the waiting start time. A waiting token is provided only when the waiting start time is not later than the latest time allowed for the waiting user to start, and the waiting start time plus the shortest usage time of the waiting request is not later than the destination. When accepting the waiting token and outputting the submission confirmation, the remaining available time is verified according to the remaining arrival time of each stage and the upper limit of the total configuration time.

7. The sports venue standby scheduling system according to claim 1, characterized in that, The standby scheduling server processes ordinary reservations and standby allocations through the same resource ledger, and establishes the standby token after verifying that there is no overlapping allocation of venues and that there are no other valid standby tokens for the standby request in the same transaction; The admission execution instruction includes a command identifier that corresponds one-to-one with the license identifier of the timed execution permit; the edge state controller persists the usage flag of the permit and associates the recorded processing status with the command identifier. For repeated submissions of the same command identifier, it returns the existing processing status without outputting the admission execution instruction again; the admission execution instruction carries the command execution deadline time using the monotonic time base of the edge state controller; the site execution terminal deduplicates duplicate commands according to the command identifier, and maps the command execution deadline time to the monotonic time base of the execution terminal through a verified clock mapping, and then subtracts the upper bound of the mapping error represented by the time base to obtain the conservative deadline time of the terminal; execution is only performed when the local time of the terminal is earlier than the conservative deadline time and the command has not yet been executed, and execution is rejected for expired or overdue commands; when the execution result is uncertain, the candidate scheduling server maintains the exclusive occupancy of the site and queries the command status of the site execution terminal. Before the execution result is verified with the physical status of the site, it prohibits the output of admission execution instructions for another candidate token for the same site.

8. The sports venue standby scheduling system according to claim 1, characterized in that, The site execution terminal includes a credential verification terminal corresponding to the site and a passage actuator for the controlled channel. After the access execution command is output, the candidate scheduling server will change the corresponding candidate token to an entry pending confirmation state. Only when the credential passage feedback corresponding to the candidate token can be associated with the site occupancy change that occurs after the passage and within the specified associated time limit, it will be changed to a usage state. If an occupancy change occurs before the access execution command is output, the candidate qualification corresponding to the old release evidence will become invalid. Specifically, if the execution preparation state has not yet been entered, the candidate token will be revoked and the release conditions will be reassessed. If the execution preparation state has been entered, the site will be exclusively occupied and the permission will be revoked. If the permission has been used or the usage status is unclear, the system will enter a verification state. If the access execution command has been output but the occupancy change cannot be associated with the credential passage feedback, the site will be occupied and the system will enter a verification state. It is prohibited to cancel the occupancy simply because the candidate qualification has expired or the permission has expired.

9. The sports venue standby scheduling system according to claim 1, characterized in that, The edge state controller will set the local expiration time of the time-limited execution permit. Determined as: ； in, The required set of sensing nodes, For the nodes in this set, In order to collect and complete the verification of the returned records for this review, To configure the license duration, The nodes used in this review The observations are mapped to the acquisition times after the monotonic time reference of the edge state controller. This represents the maximum allowed collection age for this node. This is the upper bound of the mapping error at that acquisition time; each For this calculation, it is fixed that subsequent new observations cannot extend the existing local validity period of the permit; when At that time, the time-limited execution license will not be generated.

10. A method for scheduling reserve venues in sports stadiums based on occupancy status awareness, characterized in that, include: Site occupancy observations are collected by site sensing nodes. When the continuous and effective idle observations of the pre-configured set of necessary sensing nodes meet the preset idle confirmation time, the edge state controller generates release evidence containing site identifiers and release generations. The standby scheduling server combines the release evidence, the release conditions of the original eligibility, and subsequent reservations to determine the available time window, selects standby requests with compatible durations, establishes an exclusive standby token that binds the venue identifier and release generation, and receives acceptance information from standby users. In response to an entry verification initiated for an accepted candidate token, the edge state controller sends a sampling request with the verification identifier. Upon receiving the sampling request, each necessary sensing node collects new occupancy observations and returns them after associating the verification identifier with the observation record. Within the preset response time limit, collect and complete the verification of all necessary sensing node return records. When each return record corresponds to the current review identifier, is a valid idle observation, and the release generation remains unchanged, generate a timed execution permit that binds the current review identifier, the candidate token, and the release generation, and send the permit identifier and its binding information to the candidate scheduling server. Once the standby scheduling server confirms that the standby token is valid and the site is still exclusively held by the standby token, the standby token is switched to the execution preparation state. The license identifier is recorded and a submission confirmation for the combination of the license and the standby token is output. The site is kept exclusively occupied for the execution preparation state. If the corresponding time-limited execution license has not been used, the occupancy is allowed to be released only after receiving feedback from the edge state controller confirming that the license has not been used and has been revoked or has not been used and has expired. If the corresponding license has been used or the usage status is unclear, the command execution and passage status are checked, and the occupancy is maintained until a release conclusion is obtained. After receiving the submission confirmation from the candidate scheduling server, the edge state controller verifies in the serial processing sequence of the same site whether the timed execution permit has not been revoked, is a currently executable and unused permit, the local execution verification time is earlier than the local expiration time of the permit, the release generation has not changed, and the site physical state is still validly idle. After the verification is passed and the permit has been successfully persisted as a used permit, the edge state controller outputs an admission execution instruction to the site execution terminal; otherwise, it blocks the admission execution instruction. The site execution terminal updates the access indication of the corresponding site according to the access execution instruction, or drives the controlled channel corresponding to the site to perform a release; wherein, when the observation fails or the physical state of the site changes to occupied, the edge state controller invalidates the release evidence and updates the release generation.

Images