Component policy execution method, apparatus, device, medium, and program product

Abstract

Embodiments of the present disclosure disclose component policy execution method, device, equipment, medium and program product. A specific embodiment of the method comprises: in response to the design state platform having uploaded component policy package information and established a component type, obtaining component policy configuration information set on a policy configuration page in the design state platform, the component policy configuration information comprising: target matching relationship and policy package parameter configuration corresponding to the component policy package information, the target matching relationship being a corresponding relationship between the component policy package information and the component type; obtaining a component policy design file for the component policy configuration information derived from the design state platform; and importing the component policy design file into a running state platform to perform scheduling and execution of a policy package corresponding to the component policy design file. The embodiment is related to component definition and development, and through the design state platform and the running state platform, accumulation, sedimentation and scheduling use of the component policy package can be efficiently realized, and component use efficiency is improved.

Description

Technical Field

[0001] Embodiments of this disclosure relate to the field of component definition and development, specifically to component policy execution methods, apparatus, electronic devices, media, and products. Background Technology

[0002] Currently, as software scales up, monolithic architectures are increasingly revealing problems (such as maintenance difficulties and poor scalability). To improve system maintainability and flexibility, modular design has become mainstream. Component extension allows for the dynamic addition of new features or replacement of existing modules through standardized interfaces or protocols, without modifying the underlying code. However, there is currently an overabundance of custom component requirements, hindering the efficient accumulation and refinement of components, leading to ineffective code maintenance and hindering the improvement of the efficiency of custom component usage and maintenance.

[0003] The information disclosed in this background section is only intended to enhance the understanding of the background of the inventive concept, and therefore may contain information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0005] Some embodiments of this disclosure provide component policy execution methods, apparatuses, devices, media, and program products to address the technical problems mentioned in the background section above.

[0006] In a first aspect, some embodiments of this disclosure provide a component policy execution method, comprising: responding to a design-state platform having uploaded component policy package information and established a component type, obtaining component policy configuration information set on a policy configuration page in the design-state platform, wherein the component policy configuration information includes: a target matching relationship and policy package parameter configurations corresponding to the component policy package information, the target matching relationship being a correspondence between the component policy package information and the component type; obtaining a component policy design file exported from the design-state platform for the component policy configuration information; and importing the component policy design file into a runtime platform to schedule and execute the policy package corresponding to the component policy design file.

[0007] Optionally, the component strategy package information is uploaded through the following steps: obtaining the component strategy package and the strategy package configuration description, wherein the component strategy package is generated based on a standard software development kit, and the strategy package configuration description is generated based on a preset configuration specification; and uploading the component strategy package and the strategy package configuration description as component strategy package information to the design-state platform.

[0008] Optionally, the component type is the configuration result after filling in the description information of each type on the component type configuration page, and the component type configuration page is the configuration page in the design-state platform.

[0009] Optionally, the policy package parameter configuration is set on the policy configuration page in relation to the policy package configuration description.

[0010] Optionally, the strategy package corresponding to the component strategy design file is scheduled to be executed through the following steps: according to the loading execution parameters corresponding to the strategy package, the loading execution of the strategy package corresponding to the component strategy design file is executed using the strategy trigger corresponding to the runtime platform, wherein the loading execution parameters are one of the following: parameters representing loading execution according to event-driven methods, and parameters representing loading execution on a timed basis.

[0011] Optionally, the component type is a warehouse task type, and the component strategy package information is warehouse task strategy package information; and the step of responding to the fact that the component strategy package information has been uploaded and the component type has been established on the design-state platform, and obtaining the component strategy configuration information set on the strategy configuration page of the design-state platform, includes: responding to the fact that the warehouse task strategy package information has been uploaded and the warehouse task type has been established on the design-state platform, and obtaining the warehouse task strategy configuration information set on the strategy configuration page of the design-state platform; and the step of obtaining the component strategy design file exported from the design-state platform for the component strategy configuration information includes: obtaining the task strategy design file exported from the design-state platform for the warehouse task strategy configuration information; and the step of importing the component strategy design file into the runtime platform to schedule and execute the strategy package corresponding to the component strategy design file includes: importing the task strategy design file into the runtime platform to schedule and execute the strategy package corresponding to the task strategy design file.

[0012] Optionally, the warehousing task type is obtained by abstracting and processing various warehousing tasks and task execution requirements in the warehousing task scenario.

[0013] Secondly, some embodiments of this disclosure provide a component strategy execution apparatus, comprising: a first acquisition unit configured to, in response to a design-state platform having uploaded component strategy package information and established a component type, acquire component strategy configuration information set on a strategy configuration page in the design-state platform, wherein the component strategy configuration information includes: a target matching relationship and strategy package parameter configurations corresponding to the component strategy package information, the target matching relationship being a correspondence between the component strategy package information and the component type; a second acquisition unit configured to acquire a component strategy design file exported from the design-state platform for the component strategy configuration information; and an import unit configured to import the component strategy design file into a runtime platform for scheduling and execution of the strategy package corresponding to the component strategy design file.

[0014] Optionally, the component type is a warehouse task type, and the component strategy package information is warehouse task strategy package information; and the first acquisition unit can be configured to: in response to the design-state platform having uploaded the warehouse task strategy package information and established the warehouse task type, acquire the warehouse task strategy configuration information set on the strategy configuration page of the design-state platform. The second acquisition unit can be configured to: acquire the task strategy design file exported from the design-state platform for the warehouse task strategy configuration information. The import unit can be configured to: import the task strategy design file into the runtime platform for scheduling and execution of the strategy package corresponding to the task strategy design file.

[0015] Thirdly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, such that when the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any implementation of the first aspect.

[0016] Fourthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method as described in any implementation of the first aspect.

[0017] Fifthly, some embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0018] The above embodiments of this disclosure have the following beneficial effects: Through the component strategy execution method of some embodiments of this disclosure, the accumulation, sedimentation, and scheduling of component strategy packages can be efficiently realized through the design-state platform and the runtime platform, thereby improving the efficiency of component usage. Specifically, the reason for the inefficient use of related components is that there is a proliferation of component customization needs, making it impossible to efficiently accumulate and sediment components, resulting in the inability to achieve effective operation and maintenance of code and improve the efficiency of customized component usage and maintenance. Based on this, the component strategy execution method of some embodiments of this disclosure firstly, in response to the fact that the component strategy package information has been uploaded to the design-state platform and the component type has been established, obtains the component strategy configuration information set on the strategy configuration page in the design-state platform. The component strategy configuration information includes: target matching relationship and strategy package parameter configuration corresponding to the component strategy package information. The target matching relationship is the correspondence between the component strategy package information and the component type. Here, by establishing a matching relationship between the component strategy package information and the component type based on the uploaded component strategy package information and the component type in the design-state platform, the triggering execution status of the strategy content corresponding to the component strategy package information and the usage scenario of the component strategy package information can be reflected. In addition, by configuring the strategy package parameters corresponding to the component strategy package information, specific scenarios can be implemented, allowing the component strategy package information to be adapted to specific scenarios. Therefore, by setting component strategy configuration information, the strategy package corresponding to the component strategy package information can be adapted for use in specific scenarios, achieving the accumulation and consolidation of component strategy package information, and also facilitating the efficient use of component strategy packages in the future. Then, the component strategy design file for the component strategy configuration information exported from the design-state platform is obtained, and the target design file is used to facilitate subsequent operation and scheduling. Finally, the component strategy design file is imported into the runtime platform for efficient scheduling and execution of the strategy package corresponding to the component strategy design file. In summary, through the design-state platform, the accumulation and consolidation of component strategy packages can be achieved by setting component strategy configuration information, ensuring the efficiency of subsequent use of component strategy packages. Furthermore, the runtime platform enables efficient scheduling and use of the component strategy design file corresponding to the component strategy package. Based on this, the component strategy package is implemented. Attached Figure Description

[0019] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0020] Figure 1 This is a schematic diagram of an application scenario of a component strategy execution method according to some embodiments of this disclosure;

[0021] Figure 2 This is a flowchart of some embodiments of the component strategy execution method according to this disclosure;

[0022] Figure 3 These are flowcharts of other embodiments of the component strategy execution method according to this disclosure;

[0023] Figure 4 This is a schematic diagram showing the definition of the warehouse task strategy package corresponding to the warehouse task strategy package information;

[0024] Figure 5 This is a schematic diagram illustrating the development and loading process of a warehouse task strategy package in a warehouse scenario;

[0025] Figure 6 This is a schematic diagram of the structure of some embodiments of the component strategy execution apparatus according to the present disclosure;

[0026] Figure 7 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0027] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0028] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0029] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0030] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0031] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0032] Before performing any of the operations involving the information disclosed herein (such as task strategy configuration information), the relevant organizations or individuals shall fulfill their obligations, including conducting information security impact assessments, informing the information subjects, and obtaining prior authorization and consent from the information subjects.

[0033] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0034] Figure 1 This is a schematic diagram of an application scenario of a component strategy execution method according to some embodiments of the present disclosure.

[0035] exist Figure 1 In the application scenario, firstly, in response to the fact that the design-state platform 102 has uploaded component strategy package information 103 and established component type 104, the electronic device 101 can obtain the component strategy configuration information set on the strategy configuration page 105 in the design-state platform 102. The component strategy configuration information includes: a target matching relationship and the strategy package parameter configuration corresponding to the component strategy package information 103. The target matching relationship is the correspondence between the component strategy package information 103 and the component type 104. In this application scenario, the component strategy package information 103 can be component strategy package information A. The component type 104 can be a UI component type. Then, the electronic device 101 can obtain the component strategy design file 106 exported from the design-state platform 102 for the component strategy configuration information. Finally, the electronic device 101 can import the component strategy design file 106 into the runtime platform 107 to schedule and execute the strategy package corresponding to the component strategy design file 106.

[0036] It should be noted that the aforementioned electronic device 101 can be either hardware or software. When the electronic device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the electronic device is software, it can be installed in the hardware devices listed above. It can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0037] It should be understood that Figure 1 The number of electronic devices shown is merely illustrative. Any number of electronic devices can be used depending on the implementation requirements.

[0038] Continue to refer to Figure 2 The diagram illustrates a flow 200 of some embodiments of a component policy enforcement method according to the present disclosure. This component policy enforcement method includes the following steps:

[0039] Step 201: In response to the fact that the component strategy package information has been uploaded and the component type has been established on the design-state platform, obtain the component strategy configuration information set on the strategy configuration page of the design-state platform.

[0040] In some embodiments, in response to the design-state platform having uploaded component strategy package information and established component types, the execution entity of the aforementioned component strategy execution method (e.g., Figure 1The electronic device 101 shown can access component policy configuration information set on the policy configuration page of the design-state platform via wired or wireless connection. The design-state platform can be a platform that supports various processing of components or component policy packages. For example, various processing may include: component input processing, component development processing, component function expansion processing, component parameter configuration, component loading processing, component policy package input processing, component policy package development processing, component policy package parameter configuration, and component policy package loading processing. A component can be a simple encapsulation of data and methods, and is a basic unit constituting a larger system. A component can exist independently and have certain functions, typically referring to an independent software module containing certain functions and interfaces, capable of interacting with other modules. A component policy package can be a collection of components containing specific strategies or algorithms. That is, a component policy package can be a package of feature processing strategies or feature processing algorithms developed with customized research and development under specific needs. In other words, a component policy package can be a customized collection of components used to solve specific problems or achieve specific functions. A component policy package can include multiple components, each implementing a specific strategy or algorithm. These components may have certain dependencies and all adhere to component-based design principles, allowing for independent development and deployment. The design-state platform can be a pre-developed platform for processing components in various scenarios. Customized or commonly used components or component strategy packages for each scenario can be stored and integrated on the design-state platform for easy use and maintenance. Therefore, the design-state platform can significantly improve the efficiency of component or component strategy package usage and maintenance. Component strategy package information can be information related to the component strategy package. For example, component strategy package information may include: component strategy package identifier, strategy description, and parameter description. Component types can be categorized based on the function, purpose, and characteristics of the component or component strategy package. Component types can be the result of abstracting the execution task corresponding to the component or the execution task corresponding to the component strategy package. In practice, component types can be, but are not limited to, one of the following: front-end components, back-end components, general components, navigation components, input components, feedback components, and task types of each sub-task corresponding to each strategy in the target task. The target task can be a specific task in each scenario. Each strategy in the target task can be a processing strategy tailored to specific customized needs. Each strategy corresponds to a subtask. Each subtask is abstracted to determine its corresponding task type. For example, for a delivery task as the target task, the corresponding strategies could include: a duration calculation strategy and a route optimization strategy. The corresponding component strategy packages could include: a strategy package corresponding to the duration calculation strategy and a strategy package corresponding to the route optimization strategy. The strategy package corresponding to the duration calculation strategy could be a customized strategy package used to calculate delivery time.The strategy package corresponding to the route optimization strategy can be a customized strategy package for calculating the optimal route. Each subtask can include: a subtask for duration calculation and a subtask for route optimization. The task types corresponding to each subtask can include: duration calculation task type and route optimization task type. The strategy configuration page can be a configuration page for the configuration information corresponding to the component strategy package. The configuration information corresponding to the component strategy package can be the settings for the component strategy configuration information. The component strategy configuration information includes: target matching relationship and the strategy package parameter configuration corresponding to the component strategy package information. The target matching relationship is the correspondence between the component strategy package information and the component type. The target matching relationship can characterize under which component type the component strategy package information is scheduled and used. For example, for the target task type corresponding to the target strategy under the target task type, the corresponding target matching relationship can characterize the relationship of calling the component strategy package information corresponding to the component strategy package to complete the subtask under the target task type. The target matching relationship can characterize the calling relationship between the two, and also characterize the calling triggering relationship corresponding to the component strategy package. That is, the execution of the component strategy package can be triggered by the component type. It's important to note that a component strategy package can also be a strategy package that represents the component's execution flow. The corresponding target matching relationship can represent the execution position of the component type within the component's execution flow. Strategy package parameter configurations can be the parameter configurations corresponding to the component strategy package. That is, strategy package parameter configurations can be the parameter configurations that the component strategy package needs to execute under the task corresponding to the component type. In other words, the strategy logic corresponding to the component strategy package under the corresponding task can only be executed if the strategy package parameters are configured correctly.

[0041] As an example, the aforementioned execution entity can pop up an instruction box on the design-state platform to instruct the setting of component policy configuration information on the policy configuration page of the design-state platform in order to obtain component policy configuration information.

[0042] In some optional implementations of certain embodiments, the component strategy package information is uploaded through the following steps:

[0043] The first step is to obtain the component strategy package and its configuration description. The component strategy package is generated based on a standard software development kit (SDK), and the strategy package configuration description is generated based on a preset configuration specification. The strategy package configuration description can be the relevant descriptive content required for the normal execution of the component strategy package. For example, it may include, but is not limited to, at least one of the following: strategy package parameter name, strategy package parameter range, strategy package execution task information, and strategy package condition requirements. The standard software development kit can be a standard, pre-configured software development kit (SDK). The configuration specification can be a pre-configured configuration specification requirement for the component strategy package. The configuration requirements may include, but are not limited to, at least one of the following: the order of various strategy package configurations, and the format requirements between various strategy package configurations. Each strategy package configuration may include, but is not limited to, at least one of the following: strategy package parameter name, strategy package parameter range, strategy package execution task information, and strategy package condition requirements. The strategy package configuration description can be a configuration file in a first format. For example, the first format can be a JSON package format. The component strategy package can be a strategy package in a second format. The second format can be a JAR file.

[0044] Here, standard software development tools can be used to expose the task view to implement the component strategy package strategy.

[0045] The second step is to upload the component strategy package and the strategy package configuration description as component strategy package information to the design state platform.

[0046] In some optional implementations of certain embodiments, the component type is the configuration result after filling in the various type description information on the component type configuration page. The component type configuration page is the configuration page in the design-state platform. Specifically, the component type configuration page can be a settings page for configuring component types. The type description information can be information describing the type characteristics of the component type. For example, the type description information can be the applicable scenarios for the component type, or task-related description information for which the component type applies.

[0047] In some optional implementations of certain embodiments, the policy package parameter configuration is set on the policy configuration page in relation to the policy package configuration description. In practice, the policy package parameter configuration can be set by a skilled technician on the policy configuration page in relation to the policy package configuration description.

[0048] Step 202: Obtain the component strategy design file exported from the design state platform for the component strategy configuration information.

[0049] In some embodiments, the aforementioned execution entity can obtain the component policy design file for the component policy configuration information exported from the design-state platform via wired or wireless means. The component policy design file can be a design file related to the component policy package in a target compression format. For example, the target compression format can be a ZIP compression format.

[0050] As an example, upon detecting the submit control of the target manipulated object on the strategy configuration page of the design-state platform, the aforementioned execution entity can obtain the component strategy design file corresponding to the exported component strategy configuration of the design-state platform.

[0051] Step 203: Import the component strategy design file into the runtime platform to schedule and execute the strategy package corresponding to the component strategy design file.

[0052] In some embodiments, the aforementioned execution entity can import the component strategy design file into a runtime platform to schedule and execute the strategy package corresponding to the component strategy design file. The runtime platform can be a platform that executes the component or the component strategy package. Here, the runtime platform can be a platform for scheduling and executing components or component strategy packages. In practice, the runtime platform can decompress the component strategy design file to schedule and execute the component strategy package. The runtime platform can implement functions such as data file storage, data persistence, and data caching.

[0053] In some optional implementations of certain embodiments, the strategy package corresponding to the component strategy design file is scheduled for execution through the following steps:

[0054] Based on the loading execution parameters corresponding to the strategy package, the aforementioned execution entity can utilize the strategy trigger corresponding to the runtime platform to execute the loading of the strategy package corresponding to the component strategy design file. The loading execution parameters are one of the following: parameters representing event-driven loading execution, or parameters representing timed loading execution. Loading execution parameters can be the content of loading and scheduling component strategy packages. The strategy trigger can be a device that triggers the execution of the component strategy package. Parameters representing timed loading execution can be parameters for loading scheduling according to a custom time. Parameters representing event-driven loading execution can be parameters that trigger scheduling execution when a new task is available.

[0055] The above embodiments of this disclosure have the following beneficial effects: Through the component strategy execution method of some embodiments of this disclosure, the accumulation, sedimentation, and scheduling of component strategy packages can be efficiently realized through the design-state platform and the runtime platform, thereby improving the efficiency of component usage. Specifically, the reason for the inefficient use of related components is that there is a proliferation of component customization needs, making it impossible to efficiently accumulate and sediment components, resulting in the inability to achieve effective operation and maintenance of code and improve the efficiency of customized component usage and maintenance. Based on this, the component strategy execution method of some embodiments of this disclosure firstly, in response to the fact that the component strategy package information has been uploaded to the design-state platform and the component type has been established, obtains the component strategy configuration information set on the strategy configuration page in the design-state platform. The component strategy configuration information includes: target matching relationship and strategy package parameter configuration corresponding to the component strategy package information. The target matching relationship is the correspondence between the component strategy package information and the component type. Here, by establishing a matching relationship between the component strategy package information and the component type based on the uploaded component strategy package information and the component type in the design-state platform, the triggering execution status of the strategy content corresponding to the component strategy package information and the usage scenario of the component strategy package information can be reflected. In addition, by configuring the strategy package parameters corresponding to the component strategy package information, specific scenarios can be implemented, allowing the component strategy package information to be adapted to specific scenarios. Therefore, by setting component strategy configuration information, the strategy package corresponding to the component strategy package information can be adapted for use in specific scenarios, achieving the accumulation and consolidation of component strategy package information, and also facilitating the efficient use of component strategy packages in the future. Then, the component strategy design file for the component strategy configuration information exported from the design-state platform is obtained, and the target design file is used to facilitate subsequent operation and scheduling. Finally, the component strategy design file is imported into the runtime platform for efficient scheduling and execution of the strategy package corresponding to the component strategy design file. In summary, through the design-state platform, the accumulation and consolidation of component strategy packages can be achieved by setting component strategy configuration information, ensuring the efficiency of subsequent use of component strategy packages. Furthermore, the runtime platform enables efficient scheduling and use of the component strategy design file corresponding to the component strategy package. Based on this, the component strategy package is implemented.

[0056] Further reference Figure 3 The diagram illustrates flow 300 of another embodiment of the component policy enforcement method according to this disclosure. This component policy enforcement method includes the following steps:

[0057] Step 301: In response to the fact that the design-state platform has uploaded the warehouse task strategy package information and established the warehouse task type, obtain the warehouse task strategy configuration information set on the strategy configuration page of the design-state platform.

[0058] In some embodiments, in response to the design-state platform having uploaded the warehouse task strategy package information and established the warehouse task type, the execution entity (e.g., Figure 1 The electronic device 101 shown can obtain the warehouse task strategy configuration information set on the strategy configuration page of the design-state platform via wired or wireless means. Here, the component type is the warehouse task type, and the component strategy package information is the warehouse task strategy package information. The warehouse task strategy package information can be information related to the warehouse task strategy package. The warehouse task strategy package can be a component strategy package related to the warehouse task. For example, the warehouse task strategy package information may include: warehouse task strategy package identifier, warehouse task strategy package strategy description, and warehouse task strategy package parameter description. The warehouse task type can be a type classified according to the function, purpose, and characteristics of the warehouse component or warehouse task component strategy package. The warehouse task type can be the result of abstracting the warehouse execution task corresponding to the warehouse component or the warehouse execution task corresponding to the warehouse task component strategy package. The design-state platform can be the component processing platform corresponding to the Warehouse Control System (WCS). The warehouse task strategy configuration information is the configuration settings corresponding to the warehouse task strategy package.

[0059] As an example, Figure 4 This diagram illustrates the definition of the warehouse task strategy package corresponding to the warehouse task strategy package information.

[0060] like Figure 4 As shown, you can define a repository task strategy package by filling in the strategy package ID, strategy package name, and strategy implementation logic (i.e., the details of the strategy implementation) on the strategy package definition page. The strategy package definition page supports various custom settings for repository task strategy packages.

[0061] In some optional implementations of certain embodiments, the warehouse task type is obtained by abstracting the various warehouse tasks and task execution requirements in a warehouse task scenario. In practice, warehouse task relationships can be obtained by abstracting the various tasks (e.g., business tasks, WCS tasks, equipment tasks, etc.) in a warehouse task scenario through on-demand scheduling, task splitting, task reorganization, and controlling the execution rhythm of each task (e.g., immediate execution, priority sorting, wave execution, bomb disposal, and order grouping).

[0062] Step 302: Obtain the task strategy design file exported from the design-state platform for the warehouse task strategy configuration information.

[0063] In some embodiments, the aforementioned execution entity may obtain a task strategy design file exported from the design-state platform, which specifies the configuration information for the warehousing task strategy. The task strategy design file may be a packaged file related to a warehousing task strategy package in a predetermined format. In practice, the task strategy design file may include: a warehousing task strategy package, a warehousing task type, and parameter configurations corresponding to the warehousing task strategy package.

[0064] Step 303: Import the task strategy design file into the runtime platform to schedule and execute the strategy package corresponding to the task strategy design file.

[0065] In some embodiments, the aforementioned execution entity can import the task strategy design file into a runtime platform to schedule and execute the strategy package corresponding to the task strategy design file. The runtime platform can be a component scheduling platform corresponding to the warehouse control system.

[0066] See Figure 5 This diagram illustrates the development and loading process of a warehouse task strategy package in a warehouse scenario.

[0067] For warehousing scenarios, there are certain differences in business logic and processes, data attributes, connected devices, connected systems, strategies for different stages in the system, and user interfaces. Specific warehousing task strategy packages include: strategy packages corresponding to protocols, business strategy packages adapted to different business stages, strategy packages corresponding to process nodes, and model strategy packages corresponding to different device systems and business systems.

[0068] like Figure 5 As shown, the WCS unified design platform (i.e., the design-state platform) supports developers in generating repository task strategy packages (i.e., the packages in the diagram) and repository task strategy package configuration descriptions (i.e., the descriptions and other files related to the repository task strategy packages in the diagram) by following the specifications and standard settings of the SDK packages. On the WCS unified design platform, repository task strategy configuration information (i.e., node configurations, strategy configurations, etc. in the diagram) can be generated based on the repository task strategy packages and their configuration descriptions. When exporting task strategy design files on the WCS unified design platform, the task strategy design files are installed into the WCS runtime environment to achieve dynamic loading of strategy packages corresponding to protocols, business strategy packages adapted to different business processes, strategy packages corresponding to process nodes, and model strategy packages corresponding to different device systems and business systems.

[0069] from Figure 3 It can be seen from this that, with Figure 2 Compared to the description of some corresponding embodiments, Figure 3The component strategy execution method flow 300 in some corresponding embodiments can realize the development, storage and invocation of various warehouse task strategy packages in the warehouse task scenario, which greatly improves the efficiency of component usage and subsequent development in the warehouse task scenario.

[0070] Further reference Figure 6 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of a component policy execution device, which are similar to... Figure 2 Corresponding to the method embodiments shown, this component policy execution device can be specifically applied to various electronic devices.

[0071] like Figure 6 As shown, a component strategy execution device 600 includes: a first acquisition unit 601, a second acquisition unit 602, and an import unit 603. The first acquisition unit 601 is configured to, in response to the upload of component strategy package information and the establishment of component types on the design-state platform, acquire component strategy configuration information set on the strategy configuration page of the design-state platform. The component strategy configuration information includes: a target matching relationship and strategy package parameter configurations corresponding to the component strategy package information; the target matching relationship is the correspondence between the component strategy package information and the component type. The second acquisition unit 602 is configured to acquire a component strategy design file exported from the design-state platform for the component strategy configuration information. The import unit 603 is configured to import the component strategy design file into the runtime platform for scheduling and execution of the strategy package corresponding to the component strategy design file.

[0072] In some optional implementations of certain embodiments, the component type is a warehouse task type, and the component strategy package information is warehouse task strategy package information; and the first acquisition unit 601 can be further configured to: in response to the design-state platform having uploaded the warehouse task strategy package information and established the warehouse task type, acquire the warehouse task strategy configuration information set on the strategy configuration page of the design-state platform. The second acquisition unit 602 can be further configured to: acquire the task strategy design file exported from the design-state platform for the warehouse task strategy configuration information. The import unit 603 can be further configured to: import the task strategy design file into the runtime platform for scheduling and execution of the strategy package corresponding to the task strategy design file.

[0073] It is understandable that the units described in the component strategy execution device 600 and the reference Figure 2 The steps in the described method correspond to each other. Therefore, the operations, features, and beneficial effects described above for the method also apply to the component policy execution device 600 and the units contained therein, and will not be repeated here.

[0074] The following is for reference. Figure 7 It illustrates electronic devices suitable for implementing some embodiments of this disclosure (e.g., Figure 1 A schematic diagram of the structure of electronic device 101)700 in the middle. Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0075] like Figure 7 As shown, the electronic device 700 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory 702 or a program loaded from a storage device 708 into a random access memory 703. The random access memory 703 also stores various programs and data required for the operation of the electronic device 700. The processing unit 701, the read-only memory 702, and the random access memory 703 are interconnected via a bus 704. An input / output interface 705 is also connected to the bus 704.

[0076] Typically, the following devices can be connected to the input / output interface 705: input devices 706 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 707 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 708 including, for example, magnetic tape, hard disk, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 An electronic device 700 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 7 Each box shown can represent a device or multiple devices as needed.

[0077] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 709, or installed from a storage device 708, or installed from a read-only memory 702. When the computer program is executed by the processing device 701, it performs the functions defined in the methods of some embodiments of this disclosure.

[0078] It should be noted that, in some embodiments of this disclosure, the computer-readable medium described above may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0079] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0080] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: respond to the fact that the design-state platform has uploaded component policy package information and established component types; obtain component policy configuration information set on the policy configuration page of the design-state platform, wherein the component policy configuration information includes: target matching relationships and policy package parameter configurations corresponding to the component policy package information, the target matching relationship being the correspondence between the component policy package information and the component type; obtain a component policy design file exported from the design-state platform for the component policy configuration information; and import the component policy design file into the runtime platform for scheduling and execution of the policy package corresponding to the component policy design file.

[0081] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0082] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0083] The units described in some embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including a first acquisition unit, a second acquisition unit, and an import unit. The names of these units do not necessarily limit the specific unit; for example, the second acquisition unit may also be described as "a unit that acquires a component policy design file exported from the design-state platform for the component policy configuration information."

[0084] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0085] Some embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements any of the component strategy execution methods described above.

[0086] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A component strategy execution method, comprising: In response to the fact that the component strategy package information has been uploaded and the component type has been established on the design-state platform, the component strategy configuration information set on the strategy configuration page of the design-state platform is obtained. The component strategy configuration information includes: target matching relationship and strategy package parameter configuration corresponding to the component strategy package information. The target matching relationship is the correspondence between the component strategy package information and the component type. Obtain the component strategy design file exported from the design-state platform for the component strategy configuration information; The component strategy design file is imported into the runtime platform to schedule and execute the strategy package corresponding to the component strategy design file.

2. The method according to claim 1, wherein, The component strategy package information is uploaded through the following steps: Obtain the component strategy package and the strategy package configuration description, wherein the component strategy package is generated based on the standard software development kit, and the strategy package configuration description is generated based on the preset configuration specification; The component strategy package and the strategy package configuration description are uploaded to the design-state platform as component strategy package information.

3. The method according to claim 1, wherein, The component type is the configuration result after filling in the description information of each type on the component type configuration page, which is the configuration page in the design-state platform.

4. The method according to claim 2, wherein, The strategy package parameter configuration is set on the strategy configuration page according to the strategy package configuration description.

5. The method according to claim 1, wherein, The strategy package corresponding to the component strategy design file is scheduled for execution through the following steps: Based on the loading execution parameters corresponding to the strategy package, the loading execution of the strategy package corresponding to the component strategy design file is executed using the strategy trigger corresponding to the runtime platform. The loading execution parameters are one of the following: parameters representing loading execution according to event-driven methods, and parameters representing loading execution on a timed basis.

6. The method according to claim 1, wherein, The component type is a warehouse task type, and the component strategy package information is warehouse task strategy package information; as well as The step of responding to the fact that the component strategy package information has been uploaded to the design-state platform and the component type has been established, and obtaining the component strategy configuration information set on the strategy configuration page of the design-state platform, includes: In response to the fact that the warehouse task strategy package information has been uploaded to the design-state platform and the warehouse task type has been established, the warehouse task strategy configuration information set on the strategy configuration page in the design-state platform is obtained; And the acquisition of the component strategy design file for the component strategy configuration information exported from the design state platform, including: Obtain the task strategy design file exported from the design-state platform, which contains the configuration information for the warehouse task strategy. The step of importing the component strategy design file into the runtime platform to schedule and execute the strategy package corresponding to the component strategy design file includes: The task strategy design file is imported into the runtime platform to schedule and execute the strategy package corresponding to the task strategy design file.

7. The method according to claim 6, wherein, The warehousing task type is obtained by abstracting and processing various warehousing tasks and task execution requirements in the warehousing task scenario.

8. A component strategy execution apparatus, comprising: The first acquisition unit is configured to, in response to the uploaded component strategy package information and the establishment of component type on the design-state platform, acquire the component strategy configuration information set on the strategy configuration page of the design-state platform. The component strategy configuration information includes: target matching relationship and strategy package parameter configuration corresponding to the component strategy package information. The target matching relationship is the correspondence between the component strategy package information and the component type. The second acquisition unit is configured to acquire a component strategy design file exported from the design state platform for the component strategy configuration information; The import unit is configured to import the component strategy design file into the runtime platform to schedule and execute the strategy package corresponding to the component strategy design file.

9. An electronic device, comprising: One or more processors; Storage device, on which one or more programs are stored, When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-7.

10. A computer-readable medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.

11. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-7.

Images