LBE large space project application starting method and system

Abstract

The application discloses an LBE large-space project application starting method and system, and the method comprises the following steps: setting the application starter as a unique starter application in an enterprise device management platform; maintaining the identification information and resource requirement parameters of a plurality of play applications through the application starter; responding to a starting instruction of a target play application; obtaining the real-time resource state of each LBE device, and matching a target device from the plurality of LBE devices based on the real-time resource state and the resource requirement parameters of the target play application; and starting the target play application on the target device based on the identification information of the play application. By setting the application starter as a unique starting application, and by uniformly maintaining the play application information, matching the device resources and starting the target application, the dynamic scheduling and efficient sharing of a plurality of play applications on a single device are realized, and the device utilization rate is significantly improved.

Description

Technical Field

[0001] This invention relates to the field of large-space immersive project management technology, and in particular to a method and system for launching LBE large-space projects. Background Technology

[0002] In large-scale LBE (Location-Based Entertainment) applications, operators typically need to deploy multiple theatrical applications within the same venue to meet diverse user experience needs. However, due to the limitations of Pico's enterprise device management platform's technical architecture, this platform only allows one Launcher application per device, meaning that only that single application can be launched directly after the device is powered on. Under this constraint, a single device is usually fixed to one or two theatrical applications. If switching to other theatrical applications is required, operators must manually intervene by resetting device parameters and reconfiguring applications. Because of the lack of a dynamic adaptation mechanism between device resources and the needs of the theatrical applications, the device's computing resources (such as CPU and memory), storage space, and peripheral interfaces cannot be flexibly allocated according to the actual needs of the theatrical applications, resulting in a large number of devices being idle during off-peak hours. Actual operational data shows that this fixed-binding model results in an average device utilization rate consistently below 30%, significantly increasing equipment procurement and maintenance costs and restricting the resource optimization and allocation capabilities of LBE projects in multi-theatrical rotation operation scenarios, making it difficult to meet the urgent need for efficient device reuse in large-scale commercial operations. Summary of the Invention

[0003] In view of this, the present invention proposes a method and system for launching LBE large-space projects, which can realize dynamic scheduling and efficient sharing of multiple theatrical applications by a single device. The present invention provides the following technical solution: A method for launching LBE (Large Space Environment) projects, applicable to application launchers for LBE projects, includes: In the enterprise device management platform, set the application launcher as the only launcher application; The application launcher maintains the identification information and resource requirement parameters of multiple theatrical applications; Responding to the launch command of the target program application; Obtain the real-time resource status of each LBE device, and match the target device from multiple LBE devices based on the real-time resource status and the resource requirement parameters of the target program application. On the target device, the target drama application is launched based on the identification information of the drama application.

[0004] Optionally, maintaining the identification information and resource requirement parameters of multiple drama applications through the application launcher includes: Establish a drama application index table, in which the application package name of each drama application is recorded as identification information, and the CPU utilization threshold, memory requirement and peripheral interface type required for each drama application to run are recorded as resource requirement parameters. The program application index table is dynamically updated in response to installation, uninstallation, or update operations of the program application.

[0005] Optionally, the launch command in response to the target program application includes: Receive the start command issued by the operations personnel through a unified management interface; The launch command is validated for legality, including verifying the operator's access rights and the integrity of the command parameters. After verification, the startup instructions are classified and sorted according to preset priority rules, and then distributed to the device resource scheduling module to trigger subsequent resource matching operations.

[0006] Optionally, matching a target device from multiple LBE devices based on the real-time resource status and the resource requirement parameters of the target program application includes: Obtain the remaining CPU resources, remaining memory capacity, current load rate, and device health status of each LBE device as real-time resource status; From all LBE devices, a set of candidate devices that meet the minimum resource requirements for the target program application is selected; Each device in the candidate device set is scored based on a multi-objective weighted scoring mechanism. The scoring dimensions include resource matching degree, load rate, health status, and distance between the device and the user experience area. The device with the highest score is selected as the target device based on the scoring results. Perform resource allocation pre-verification, and allocate the target device to the target drama application after successful verification.

[0007] Optionally, launching the target drama application based on the identification information of the drama application includes: The application launcher acts as an intermediary calling interface to send an application launch request to the target device's operating system based on the identification information. The application launcher remains in the foreground, while the target program application is launched and runs in the background. During the operation of the target program application, the application launcher continuously monitors its running status and resource usage; In response to the shutdown command of the target TV show application, the application launcher releases the resources allocated to the target TV show application by the target device and reintegrates the target device into the set of available devices.

[0008] Optionally, obtaining the real-time resource status of each LBE device includes: By establishing long-term connections with each LBE device, the online status, power consumption, CPU utilization, memory usage, and network bandwidth of the devices are collected according to a preset cycle. The collected raw state data is standardized, including unifying the data format, unit conversion, and outlier removal. When the status parameters of any device reach a preset threshold, an alarm is triggered and the operations personnel are notified.

[0009] This invention further discloses an LBE (Large Space Environment) project application launch system, comprising: The launcher setting module is used to set the application launcher as the only launcher application in the enterprise device management platform; The maintenance module is used to maintain the identification information and resource requirement parameters of multiple drama applications through the application launcher; The instruction response module is used to respond to the start instruction of the target program application; The resource matching module is used to obtain the real-time resource status of each LBE device, and match the target device from multiple LBE devices based on the real-time resource status and the resource requirement parameters of the target program application. An application launch module is used to launch the target drama application on the target device based on the identification information of the drama application.

[0010] The present invention further discloses a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0011] The present invention further discloses an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the above-described method.

[0012] The present invention further discloses a computer program product, including a computer program that implements the above-described method when executed by a processor.

[0013] According to the technical solution of this invention, the present invention sets the application launcher as a unique launcher application in the enterprise equipment management platform, and uses this launcher to uniformly maintain the identification information and resource requirement parameters of multiple theatrical applications. When a launch command for a target theatrical application is received, the resource status of each LBE device is obtained in real time, and the optimal target device is dynamically matched based on the resource requirement parameters of the target application. Finally, the application is directly launched on the target device according to the identification information. Thus, under the limitation that the platform only allows a single launcher, flexible switching and efficient sharing of multiple theatrical applications on a single device are realized, significantly improving equipment utilization and greatly reducing hardware procurement and operating costs. At the same time, the centralized application information maintenance and resource status awareness mechanism allows operators to complete the unified scheduling of multiple applications without switching between scattered management interfaces, improving operational efficiency. Based on the dynamic matching and rapid launch process of real-time resource status, the millisecond-level connection between command response and performance switching is ensured, solving the problems of command delay, application conflict and user experience gap in the existing solution. Attached Figure Description

[0014] For illustrative and not limiting purposes, the present invention will now be described in conjunction with embodiments and accompanying drawings, wherein: Figure 1 This is a flowchart illustrating the LBE large space project application launch method in an embodiment of the present invention. Figure 2 This is a schematic diagram of the components of the LBE large space project application startup system in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of the electronic device in an embodiment of the present invention. Detailed Implementation

[0015] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present application.

[0016] It should be noted that, where there is no conflict, the embodiments and features of the embodiments in this application can be combined with each other. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0017] refer to Figure 1This embodiment discloses an application launch method for LBE large-space projects, applied to an application launcher for LBE large-space projects. The application launcher is a computer program product deployed in the system management backend or edge server of the LBE large-space project, used to achieve unified management and dynamic scheduling of multiple LBE devices and multiple theatrical applications. The method includes the following steps: S100: In the enterprise device management platform, set the application launcher as the only launcher application. This step addresses the technical bottleneck of existing enterprise device management platforms that only allow one launcher application, preventing devices from freely switching between multiple program applications. This implementation uses the Pico enterprise device management platform as an example for specific illustration.

[0018] Specifically, operators upload the APK installation package of this launcher to the Pico Enterprise Device Management Platform, select this launcher as the default launcher in the launcher settings, save the policy, and then distribute it to the target device. Upon receiving the policy, the device automatically restarts, and this launcher becomes the system-level launcher for that device. After the device powers on, this launcher is automatically launched and kept running in the foreground. Through these settings, this launcher gains long-term, persistent control over the device. Because this launcher itself possesses the ability to maintain identification information for multiple theatrical applications, perceive resource requirements, and dynamically schedule them, although the Pico Enterprise Device Management Platform still follows the "single device, single launcher" rule, this implementation uses this launcher as a unified entry point. It internally maintains a list of all theatrical applications that need to be operated, and upon receiving an operational instruction, dynamically selects the target device and launches the corresponding theatrical application based on the device's resource status. This achieves flexible switching and on-demand operation of multiple theatrical applications on a single device.

[0019] It should be noted that once this launcher is set as the sole launcher, it will always run in the foreground. Subsequent launches of the show applications can run in the background or be switched to the foreground as needed. However, this launcher retains control over the device and the ability to receive commands, ensuring that operational commands can still be responded to in a timely manner in multi-application concurrent scenarios.

[0020] Therefore, this step, without altering the underlying mechanism of the Pico enterprise device management platform, embeds the launcher into the core control layer of the device through policy configuration, laying the foundation for subsequent centralized management of multiple applications and dynamic scheduling of device resources. This step requires only a one-time configuration, enabling the device to support multiple applications and significantly reducing the manual operation costs of device binding and unbinding.

[0021] S200: The application launcher maintains the identification information and resource requirement parameters of multiple theatrical applications. After completing the platform configuration in step S100, the application launcher will perform application information maintenance operations to build a data foundation for unified management of multiple theatrical applications. The application launcher internally establishes and manages a structured theatrical application index table.

[0022] This index table assigns a separate record to each deployed application, explicitly recording two core pieces of data: first, identification information, specifically using a unique and immutable application package name, such as "com.lbe.show.a" or "com.lbe.game.b," which is the sole basis for the operating system to identify and invoke a specific application; second, resource requirements parameters, including the CPU utilization threshold (e.g., not exceeding 70%), memory requirements (e.g., not less than 2GB), and required peripheral interface types (e.g., connecting to a specific model of VR controller or positioning base station) necessary for the application's stable operation. The initial data for the index table can be entered in two ways: first, during the LBE project deployment phase, operations personnel can import the configuration lists of each application in batches through the management interface provided by the application launcher; second, when a new application is installed on a device for the first time, the application launcher automatically listens for application installation broadcasts in the system and parses the package name from the newly installed application, while simultaneously supplementing the complete resource requirements parameters using a preset resource configuration template or manual input.

[0023] The maintenance process in this implementation is dynamically updated. When an installation, uninstallation, or version update operation is detected for a TV application, an update process is immediately triggered, synchronously modifying the corresponding record in the index table. For uninstallation operations, the relevant record is directly deleted; for update operations, its resource requirement parameters are re-verified and updated to ensure that the index table always remains consistent with the actual installed TV application status on the device. This dynamic maintenance mechanism guarantees the accuracy and real-time performance of subsequent resource matching and application invocation, providing crucial data support for achieving efficient and reliable device sharing.

[0024] Therefore, by constructing a centralized and structured database of program application information, the program applications scattered across various devices and installation packages are abstracted into a unified data entity, enabling the launcher to perceive runnable applications and their resource consumption characteristics. On the one hand, centralized maintenance of identification information (package names) provides standardized call handles for subsequent one-click launch, avoiding the inefficient operation of operators manually searching and clicking application icons on different devices. On the other hand, the explicit definition of resource requirement parameters allows the device resource scheduling module to perform precise device screening and resource allocation based on application requirements, thus laying a data foundation for device sharing. Compared with the existing technology of scattered storage of application information and reliance on manual memory for maintenance, this step optimizes application management from the device perspective to the application perspective, significantly reducing information maintenance costs in multi-program scenarios and fundamentally avoiding application launch failures due to incorrect package names or resource misjudgments.

[0025] S300: Response to the launch command of the target program application. The response to the launch command of the target program application is executed by the command response module inside the application launcher. Its core function is to receive and process the operation requests from operators through a unified management interface. Specifically, operators select the target program application to be launched through a visual unified management interface deployed in the management backend (such as a web management console or a dedicated management terminal) and click the "Launch" button to trigger the issuance of the launch command. After the launch command is sent to the application launcher, it is first validated for legitimacy. The validation process includes two key aspects: first, verifying the identity and permissions of the operator to ensure that they have the authorization to launch the selected program application; second, checking the completeness of the command parameters, such as confirming whether the identification information of the target program application exists in the aforementioned maintained program application index table, and whether the command contains the necessary performance configuration parameters, etc. If the validation fails, an error message is returned to the operation interface, terminating the subsequent process.

[0026] After successful verification, the startup commands will be categorized (e.g., distinguishing between regular startup, emergency startup, or test startup) and sorted according to preset priority rules (e.g., emergency commands take precedence over regular commands). Once sorted, the startup commands will be distributed to the device resource scheduling module to trigger subsequent device resource matching and allocation operations.

[0027] S400: Obtain the real-time resource status of each LBE device, and match the target device from multiple LBE devices based on the real-time resource status and the resource requirement parameters of the target program application.

[0028] This step aims to establish a global awareness of equipment resource status and, based on the dynamic matching of application resource requirements and real-time equipment resources, automatically select the optimal execution equipment for theatrical applications. It is the core decision-making step for realizing equipment sharing and dynamic resource scheduling.

[0029] Specifically, the initiator establishes a long-term connection with the status monitoring units of all LBE large-space devices (including VR glasses, positioning base stations, computing servers, etc.) and continuously collects real-time operating status data of each device according to a configurable preset period. The collected status parameters include at least: Remaining CPU resources: The number of CPU cores currently available to the device or the remaining CPU utilization rate; Remaining memory capacity: The amount of physical memory currently available to the device (in MB or GB); Current load rate: The ratio of the resources currently used by the device to the total resources, with a value range of 0 to 1; Equipment health status: Equipment is operating normally, normal = 1, minor fault = 0.5, serious fault = 0; Distance between device and user experience area: The distance between the current location of the device and the center point of the preset experience area of ​​the target drama application (unit: meters); Optional parameters include remaining storage space, network bandwidth, and battery power.

[0030] To achieve high-concurrency status data acquisition for large-scale device clusters, this implementation method adopts the following technical solution: Long connection pool management: The initiator maintains long TCP connections with each device. The connection pool has a built-in heartbeat detection mechanism (sending a heartbeat packet every 500ms) to automatically maintain disconnection and reconnection, ensuring the continuous availability of the status acquisition channel.

[0031] Data standardization processing: The raw collected data is standardized, including unifying the data format (e.g., converting the memory units reported by each device to MB), unit conversion (e.g., converting CPU utilization from percentage to a decimal format of 0-1), and outlier removal (e.g., filtering out -1 or null values ​​caused by network jitter). The standardized status data is then centrally reported to the time-series database (InfluxDB) in the system management backend for persistent storage via an encrypted transmission channel (using AES-256 encryption algorithm), and simultaneously pushed to the application-layer monitoring panel for real-time visualization.

[0032] Threshold alarm mechanism: When the status parameters of any device reach the preset threshold (e.g., battery level below 20%, CPU utilization above 90%, device health status below 0.5), the system will automatically trigger an alarm notification and immediately notify the operations personnel to intervene through pop-up windows, SMS, or WeChat robot.

[0033] This step aggregates heterogeneous status data scattered across various physical devices into a unified, real-time, and reliable global resource view, providing accurate input data for subsequent resource matching, while ensuring the operational stability of the device group through threshold alarms.

[0034] Furthermore, real-time resource data of all online devices is read from the global device resource status pool, and the resource requirement parameters (denoted as R_j) pre-configured in the target program application's program application index table are obtained, including minimum CPU core count requirement (C_j_min), minimum memory capacity requirement (M_j_min), minimum storage space requirement (S_j_min), minimum network bandwidth requirement (B_j_min), and peripheral interface type requirements. Subsequently, all LBE devices are traversed, and devices that simultaneously meet the following hardware resource constraints are selected to form a candidate device set U: The number of remaining CPU cores in the device, C_i ≥ C_j_min; The remaining memory capacity of the device is M_i ≥ M_j_min; Remaining storage space on the device: S_i ≥ S_j_min; Device network bandwidth Bi ≥ Bj ≥ min; The equipment health status H_i ≥ 0.5 (i.e., at least at the level of minor fault or above).

[0035] If the candidate device set U is empty, the system immediately returns a "No available devices" message to the operations personnel and suggests adjusting application resource requirements or checking device status. If U is not empty, the system proceeds to the next scoring stage.

[0036] To select the optimal device with the highest matching degree with the target program from multiple candidate devices, this implementation method adopts a multi-objective weighted scoring mechanism to comprehensively and quantitatively evaluate the candidate devices from multiple dimensions such as resource matching degree, load rate, health status, and distance.

[0037] For each device i in the candidate device set U, the device resource scheduling module calculates its matching score Score_i according to the following multi-objective weighted scoring function: Score_i = 0.3×C_score + 0.25×M_score + 0.2×L_score + 0.15×H_score - 0.1×D_score. Here, 0.3, 0.25, 0.2, 0.15, and 0.1 are preset importance weights for each indicator, which can be adjusted according to the actual operational needs of the project. For example, if memory resources are more important, the weight of 0.25 can be increased, while the weights of other indicators can be decreased to ensure that the sum of the five weights is 1.

[0038] The specific calculation logic for each sub-item score is as follows: CPU Resource Matching Score (C_score): Measures how well the device's remaining CPU resources meet the minimum CPU requirements of an application. The calculation formula is: C_score = min(Number of remaining CPU cores on the device ÷ Minimum CPU requirement of the application, 2). The maximum score for this indicator is 2. When the number of remaining CPU cores on the device is twice or more of the application's requirements, a full score of 2 points is obtained; otherwise, it is calculated linearly proportionally. Memory resource matching score (M_score): Measures how well the device's remaining memory capacity meets the application's minimum memory requirements. The calculation formula is: M_score = min(device's remaining memory capacity ÷ application's minimum memory requirement, 2), and the scoring logic is the same as C_score, with a maximum score of 2.

[0039] Load factor score (L_score): Measures the current workload of the device. The lower the load factor, the higher the score. The calculation formula is: L_score = 1 - device current load factor, where the device current load factor is defined as the ratio of occupied resources to total resources, and the value ranges from 0 to 1. Therefore, the value range of L_score is also 0 to 1. Health status score (H_score): The health status parameter value of the device is directly taken. The score is 1 for normal devices, 0.5 for devices with minor faults, and 0 for devices with serious faults (which have been removed in the screening stage, so the H_score value of candidate devices is only 1 or 0.5).

[0040] Distance Score (D_score): This metric is a deduction item; the farther the device is from the user experience area, the more points are deducted. The calculation formula is: D_score = min(Distance from device to experience area ÷ Maximum distance threshold of the venue, 1), where the maximum distance threshold of the venue is a preset constant (e.g., 50 meters). When the device distance exceeds this threshold, D_score is 1.

[0041] After calculating the scores of all candidate devices, the device resource scheduling module executes the following decision rules: Optimal device selection: Sort candidate devices in descending order of their Score_i, and select the device with the highest score as the target device. If multiple devices have the same score, further compare their distances to the score D_score and select the device closest to it; if D_scores are still the same, select the device with the smallest device number to avoid conflict.

[0042] Resource allocation pre-verification: Before formally issuing resource allocation instructions to the target device, a resource allocation pre-verification step is performed. Specifically, a lightweight resource pre-allocation request is sent to the target device, requiring the device to confirm in real time that its current resource status still meets the application requirements. If the device returns a successful confirmation, the formal allocation process begins; if it returns insufficient resources or times out without response, the device is removed from the candidate device set U, and the scoring and selection process is repeated to select the second-best device from the remaining candidate devices as the new target device.

[0043] After the pre-verification is successful, a formal resource allocation instruction is issued to the target device, which includes the following operations: Resource reservation: Based on the resource requirements of the target application, and combined with the "on-demand allocation + reserved buffer" strategy, an appropriate amount of resources are allocated to the application. In this implementation, the CPU resource allocation ratio = min(C_j_min / C_i_total×1.2, 0.8), where C_i_total is the total number of CPU cores on the device, 1.2 is the reserved buffer coefficient, and 0.8 is the upper limit of CPU usage for a single application to avoid excessive resource consumption by a single application; memory allocation capacity = M_j_min×1.3; the allocation of other resources is similar.

[0044] Device Marking: Mark the target device as "Assigned - Program Application X Running" and temporarily remove it from the candidate device pool for subsequent application launch commands until the resource is released after the application is closed. At this point, the target device matching and resource allocation process is complete.

[0045] S500: On the target device, the target drama application is launched based on the identification information of the drama application.

[0046] Specifically, the application launcher acts as an intermediary to call the interface and sends an application launch request to the target device's operating system based on the application package name identifier recorded in the program application index table.

[0047] During this process, the application launcher remains in the foreground, while the target TV show application is launched and runs in the background. While the target TV show application is running, the application launcher continuously monitors its running status and resource usage.

[0048] When a shutdown command is received for the target program application, the application launcher performs a resource release operation, releasing the resources allocated to the target device for the target program application and re-including the target device in the set of available devices for subsequent scheduling.

[0049] In summary, this implementation sets the LBE large-space project application launcher as the sole Launcher application in the Pico enterprise equipment management platform. This launcher uniformly maintains the identification information and resource requirement parameters of multiple theatrical applications. Upon receiving a launch command from a target theatrical application, it acquires the real-time resource status of each LBE device and matches this status with the resource requirement parameters of the target theatrical application to determine the target device. Finally, using the launcher as an intermediary interface, the target theatrical application is launched on the target device based on the identification information. The launcher always runs in the foreground while the theatrical application runs in the background. This effectively solves the problem of fixed binding between devices and theatrical applications caused by the Pico platform only allowing a single Launcher. It achieves dynamic scheduling and efficient sharing of multiple theatrical applications on a single device, significantly improving equipment resource utilization, reducing operating costs, and ensuring smooth switching and stable operation in multi-theatrical rotation scenarios.

[0050] refer to Figure 2 This embodiment further discloses an LBE large space project application launch system, including: The launcher setting module 21 is used to set the application launcher as the only launcher application in the enterprise device management platform. The enterprise device management platform is specifically the Pico enterprise device management platform. By establishing a connection with this platform, the launcher setting module invokes the LBE large-space project application launcher program in the Pico enterprise device management platform and sets this application launcher as the device's only launcher application. After the device restarts, this application launcher becomes the system-level launcher for the device, gaining long-term resident control over the device, laying the foundation for subsequent multi-application management and device resource scheduling.

[0051] The maintenance module 22 is used to maintain the identification information and resource requirement parameters of multiple LBE (Large-Scale Beta Environment) applications through the application launcher. The maintenance module 22 pre-enters basic information of all LBE applications to establish an application information database. The identification information includes the application's package name and application index; the resource requirement parameters include threshold parameters such as the minimum number of CPU cores, minimum memory capacity, minimum storage space, and minimum network bandwidth required for the application to run. Operators can configure and update the application information through the system management backend. The maintenance module dynamically maintains the application information database in response to the installation, uninstallation, or update operations of the applications.

[0052] The instruction response module 23 is used to respond to the launch instruction of the target program application. Integrated into the system management backend, the instruction response module 23 is connected to the operator's terminal on one end and to the maintenance module, resource matching module, and application launch module on the other. After the operator issues the launch instruction of the target program application through the unified control interface of the system management backend, the instruction response module receives the instruction, performs a validity check on the instruction (including verifying the operator's permissions and the integrity of the instruction parameters), classifies and prioritizes the instruction after successful verification, and quickly distributes the instruction to the resource matching module through the service bus to trigger subsequent resource matching operations.

[0053] The resource matching module 24 is used to acquire the real-time resource status of each LBE device and, based on the real-time resource status and the resource requirement parameters of the target program application, match a target device from multiple LBE devices. The resource matching module 24 engages in bidirectional data interaction with the device status acquisition and reporting module and the maintenance module. On one hand, it acquires the remaining resource quantity of each LBE device in real time through the device status acquisition and reporting module (including the remaining number of CPU cores, remaining memory capacity, remaining storage space, network bandwidth, current device load rate, device health status, distance between the device and the user experience area, etc.); on the other hand, it obtains the resource requirement threshold of the target program application from the maintenance module. When a start command for the target program application is received, the resource matching module, based on the optimal resource matching algorithm, filters candidate devices that meet the resource requirements of the application from currently idle or low-load devices, calculates the matching score of each candidate device using a multi-objective weighted scoring function, selects the device with the highest score as the target device, and sends a resource allocation command to the target device.

[0054] Application startup module 25 is used to launch the target drama application on the target device based on the identification information of the drama application. The application startup module 25 is deployed on each LBE device and communicates with the maintenance module and the resource matching module. After the resource matching module completes the target device selection and resource allocation, the application startup module receives the startup command, extracts the package name information of the target drama application, and launches the drama application on the target device by calling the operating system's application startup interface. After the application starts, this module monitors its running status in real time; in response to the drama application's shutdown command, this module releases the device resources occupied by the application and re-includes the target device in the available device set for reuse by other drama applications.

[0055] In this embodiment, the application launcher adopts a software architecture design of "layered architecture + modular drive", which is divided into a perception layer, access layer, core service layer, application layer and data layer. Each layer works together from top to bottom, and the core logic of the four parts is integrated in the corresponding layer to ensure the stable and efficient operation of the system.

[0056] Specifically, the core of the perception layer carries the underlying perception functions of the device status acquisition and reporting module, integrating various device status acquisition drivers, including but not limited to VR glasses battery level acquisition drivers, CPU / memory status reading drivers, and positioning device accuracy acquisition drivers. This layer directly interfaces with the device hardware's status monitoring unit to collect and initially filter raw status data, providing the data input foundation for the device status acquisition and reporting module.

[0057] The access layer is responsible for the unified access and transmission adaptation of various types of data and commands, and includes the following components: Communication protocol adaptation unit: Supports multiple protocols such as TCP / UDP / MQTT, enabling unified access and conversion of heterogeneous communication protocols; Data encryption unit: Employs the AES-256 encryption algorithm to encrypt and protect transmitted data; Connection Management Unit: Maintains long-term connections with various devices and applications, providing stable link support for communication between the four main modules.

[0058] The core service layer is the core function implementation layer of the system, integrating the core logic of the device status acquisition and reporting module (data processing part), the multi-application centralized management and control module, the command rapid processing module, and the device resource scheduling module. Each module interacts with data through a service bus, which uses a lightweight RPC framework (such as gRPC) to achieve low-latency communication between modules. Simultaneously, the core service layer has a built-in load balancing module, which can dynamically allocate computing resources when multiple applications are concurrently managing or multiple devices are simultaneously reporting their status, ensuring service stability in high-concurrency scenarios.

[0059] At the application layer, a unified visual control interface is provided to meet the needs of operations personnel and system management. This interface includes the following functional modules: device status monitoring panel, application control console, command issuance entry point, and alarm notification window. This layer serves as the interaction platform between the centralized control modules for multiple applications and operations personnel, enabling visualization and convenience of operational procedures.

[0060] The data layer is responsible for the storage and management of all system data and includes the following database components: Time Series Database (InfluxDB): Used to store time series data of device status uploaded by the device status acquisition and reporting module; Relational database (MySQL): Used to store application information, device information, and operational instruction logs of the multi-application centralized management module and instruction rapid processing module; Cache database (Redis): Used to cache hot data, such as the list of currently running applications and the real-time resource status of devices, providing fast data reading support for resource matching calculations of the device resource scheduling module and improving the overall system response efficiency.

[0061] Based on this, the operating logic of the application launcher is as follows: After the system starts up, the access layer first establishes long-term connections with all LBE large-space devices and program applications, and completes communication protocol adaptation and encryption channel initialization. Then, the device status acquisition driver of the perception layer starts, collects the original status data of the devices according to the preset cycle, and uploads it to the device status acquisition and reporting module of the core service layer after being encrypted by the access layer. The device status acquisition and reporting module performs standardized processing on the data (unified data format, unit conversion, and outlier removal), and then pushes it to the data layer for storage on the one hand, and synchronizes it to the monitoring panel of the application layer in real time for display on the other hand.

[0062] When operators issue operation commands through the application layer interface, the commands are initially verified for protocol adaptation and legality at the access layer before being passed to the command rapid processing module of the core service layer. After classifying and prioritizing the commands, this module distributes them to the corresponding modules through the service bus. After the target module executes the command, it feeds back the execution result to the application layer interface through the core service layer and the access layer, and stores the relevant log data in the data layer.

[0063] The device resource scheduling module reads device resource status data from the data layer cache in real time, obtains application resource requirements from the multi-application centralized management module, completes resource allocation decisions through the optimal resource matching algorithm, and then sends resource allocation instructions to the corresponding devices through the core service layer to achieve dynamic resource scheduling.

[0064] Figure 3 A schematic diagram of the physical structure of an electronic device provided in an embodiment of the present invention, such as... Figure 3 As shown, the electronic device 50 includes: a processor 501, a memory 502, and a bus 503; The processor 501 and the memory 502 communicate with each other via the bus 503; the processor 501 is used to call the program instructions in the memory 502 to execute the methods provided in the above-described embodiments.

[0065] This embodiment provides a non-transitory computer-readable storage medium that stores computer instructions that cause a computer to execute the methods provided in the above-described embodiments.

[0066] Those skilled in the art will understand that all or part of the steps of the above-described method implementation can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above-described method implementation. The aforementioned storage medium includes various storage media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.

[0067] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0068] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of each embodiment or some parts of the embodiments.

[0069] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for launching LBE (Large-Scale Environment) large-space projects, applied to an application launcher for LBE large-space projects, characterized in that, include: In the enterprise device management platform, set the application launcher as the only launcher application; The application launcher maintains the identification information and resource requirement parameters of multiple theatrical applications; Responding to the launch command of the target program application; Obtain the real-time resource status of each LBE device, and match the target device from multiple LBE devices based on the real-time resource status and the resource requirement parameters of the target program application. On the target device, the target drama application is launched based on the identification information of the drama application.

2. The LBE large-space project application launch method according to claim 1, characterized in that, The maintenance of identification information and resource requirement parameters for multiple theatrical applications through the application launcher includes: Establish a drama application index table, in which the application package name of each drama application is recorded as identification information, and the CPU utilization threshold, memory requirement and peripheral interface type required for each drama application to run are recorded as resource requirement parameters. The program application index table is dynamically updated in response to installation, uninstallation, or update operations of the program application.

3. The method for launching LBE large-space projects according to claim 1, characterized in that, The launch command in response to the target program application includes: Receive the start command issued by the operations personnel through a unified management interface; The launch command is validated for legality, including verifying the operator's access rights and the integrity of the command parameters. After verification, the startup instructions are classified and sorted according to preset priority rules, and then distributed to the device resource scheduling module to trigger subsequent resource matching operations.

4. The method for launching LBE large-space projects according to claim 1, characterized in that, The process of matching a target device from multiple LBE devices based on the real-time resource status and the resource requirement parameters of the target program application includes: Obtain the remaining CPU resources, remaining memory capacity, current load rate, and device health status of each LBE device as real-time resource status; From all LBE devices, a set of candidate devices that meet the minimum resource requirements for the target program application is selected; Each device in the candidate device set is scored based on a multi-objective weighted scoring mechanism. The scoring dimensions include resource matching degree, load rate, health status, and distance between the device and the user experience area. The device with the highest score is selected as the target device based on the scoring results. Perform resource allocation pre-verification, and allocate the target device to the target drama application after successful verification.

5. The method for launching LBE large-space projects according to claim 1, characterized in that, The activation of the target drama application based on the identification information of the drama application includes: The application launcher acts as an intermediary calling interface to send an application launch request to the target device's operating system based on the identification information. The application launcher remains in the foreground, while the target program application is launched and runs in the background. During the operation of the target program application, the application launcher continuously monitors its running status and resource usage; In response to the shutdown command of the target TV show application, the application launcher releases the resources allocated to the target TV show application by the target device and reintegrates the target device into the set of available devices.

6. The method for launching LBE large-space projects according to claim 1, characterized in that, The process of obtaining the real-time resource status of each LBE device includes: By establishing long-term connections with each LBE device, the online status, power consumption, CPU utilization, memory usage, and network bandwidth of the devices are collected according to a preset cycle. The collected raw state data is standardized, including unifying the data format, unit conversion, and outlier removal. When the status parameters of any device reach a preset threshold, an alarm is triggered and the operations personnel are notified.

7. A startup system for LBE (Large-Scale Environment) projects, characterized in that, include: The launcher setting module is used to set the application launcher as the only launcher application in the enterprise device management platform; The maintenance module is used to maintain the identification information and resource requirement parameters of multiple drama applications through the application launcher; The instruction response module is used to respond to the start instruction of the target program application; The resource matching module is used to obtain the real-time resource status of each LBE device, and match the target device from multiple LBE devices based on the real-time resource status and the resource requirement parameters of the target program application. An application launch module is used to launch the target drama application on the target device based on the identification information of the drama application.

8. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-6.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method of any one of claims 1-6.

10. A computer program product, comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the method of any one of claims 1-6.

Images