Business platform architecture system based on digital twin objects

Abstract

The invention provides a business platform architecture system based on digital twin objects, which comprises a front-end module, an engine module and a storage module which are coupled in sequence, and the engine module at least comprises a digital engine; wherein the front-end module is suitable for receiving a service request of a user and sending the service request to the engine module; and the engine module is suitable for utilizing a digital engine to call the twinning extension service to extract the data resources in the storage module to process the professional request when the business request is determined to be the professional request. The system fully meets the personalized requirements of users, reduces the influence on the system architecture, and reduces the construction and maintenance cost of the system.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a business middle-end architecture system based on digital twin objects. Background Art

[0002] At present, the business middle platform for power marketing and customer service is designed and built according to the traditional microservice architecture, in which the business middle platform consists of middle platform microservices, data microservices and databases, and the business application consists of front-end applications and front-end microservices. The middle platform microservices are divided into different business capability centers according to the domain model design method, such as customer center, customer service center, billing center, etc., focusing on the accumulation of core capabilities of power marketing and customer service, and supporting the business management and operation of power marketing and customer service and the construction of business ecology.

[0003] Part of the personalized needs of each province of the power grid enterprise can be supported by front-end applications and front-end microservices orchestration, and part of it needs to be expanded by the middle-office service. The fundamental reason for the expansion of the middle-office service is that the domain model design method is not perfect, it relies heavily on business scenarios, and the differences in business scenarios of each province are not fully considered, resulting in insufficient universality of the domain model. The continuous changes in market demand, the continuous development of customer service business, and the various differences in customer service business of each province have posed challenges to the stability of various business middle platforms, such as the power customer service business middle platform and the power marketing service business middle platform. Summary of the invention

[0004] In view of this, the purpose of this application is to propose a business middle-end architecture system based on digital twin objects that overcomes the above-mentioned problems or at least partially solves the above-mentioned problems.

[0005] Based on the above objectives, this application provides a business middle platform architecture system based on digital twin objects, including:

[0006] A front-end module, an engine module and a storage module coupled in sequence, wherein the engine module at least includes a digital engine;

[0007] The front-end module is adapted to receive a user's service request and send the service request to the engine module;

[0008] The engine module is suitable for using the digital engine to call the twin extension service to extract data resources in the storage module to process the professional request when it is determined that the business request is a professional request.

[0009] Optionally, the front-end module includes a front-end application and a front-end microservice sub-module;

[0010] The front-end application is suitable for performing data interaction with the user to receive the service request;

[0011] The foreground microservice submodule is suitable for parsing the business request to determine the type of the business request and calling the corresponding engine according to the type of the business request.

[0012] Optionally, the engine module further includes a work order engine, which is adapted to automatically generate a work order and monitor the processing process of the work order according to the business needs of the user when the type of the business request is a type related to the work order.

[0013] Optionally, the engine module further includes a business engine adapted to configure and manage business objects according to business needs of users when the type of the business request is a type related to a businessperson.

[0014] Optionally, the engine module also includes a data microservice sub-module, which is suitable for receiving processing requests from each engine and calling the data stored in the storage module to respond to the processing requests.

[0015] Optionally, the digital engine is also suitable for calling the digital twin object to process the business request when the type of the business request is a non-professional request related to the digital twin.

[0016] Optionally, the storage module includes a process database sub-coupled to the work order engine, suitable for storing and managing business process data related to the work order.

[0017] Optionally, the storage module includes a business configuration and credential database coupled to the business engine, suitable for storing and managing relevant data of business configuration and credentials.

[0018] Optionally, the storage module includes an entity archive and a status database coupled to the digital engine, suitable for storing and managing detailed information and status information of the digital entity.

[0019] Optionally, the storage module includes an entity ledger database coupled to the twin extension service, suitable for storing and managing ledger information of digital entities.

[0020] As can be seen from the above, the business middle platform architecture device based on digital twin objects provided by this application fully meets the personalized needs of users, reduces the impact on the system architecture, and reduces the cost of system construction and maintenance. Fully meet personalized needs, fully consider the system changes brought about by the personalized needs of each network province from the perspective of architecture design, and establish flexible configurations and scalable functions through work order engine process configuration, business engine rule configuration, professional function extension service development, etc., to meet the adaptation requirements of the personalized needs of the network province, realize the dynamic expansion of the external services of the middle platform, support the rich and diverse service products, agile iteration, improve flexibility, and effectively meet the new service needs of multiple subjects, multiple contents, and multiple methods. Reduce the impact on the system architecture, the digital twin object corresponds to the objective reality in reality, and its existence is not affected by the business status, so new business, business content changes, business requirements changes, business model additions or modifications, etc. have little effect on the digital twin object, so that the business middle platform can be stable, unified and orderly updated, which is conducive to ensuring the stability and universality of the business middle platform. Reduce system construction and maintenance costs, use digital twin objects to construct general services as the basis of the business middle platform, and only need to configure the work order engine process, business engine rules, professional function extension services, etc.; and the upper-level business applications, including front-end applications, front-end microservices, data microservices, etc., do not need to be changed, which will greatly reduce the construction and maintenance costs of the business middle platform.

[0021] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the present application or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 This is a schematic diagram of the business middle platform of the microservice architecture in related technologies;

[0024] Figure 2 A schematic diagram of a business middle platform architecture system 100 based on a digital twin object according to an embodiment of the present application;

[0025] Figure 3 A functional view diagram of a business middle platform architecture system 100 based on a digital twin object according to an embodiment of the present application;

[0026] Figure 4A schematic diagram of a service call link of a business middle platform architecture system 100 based on a digital twin object according to an embodiment of the present application;

[0027] Figure 5 A schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0029] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be the usual meanings understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing in front of the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0030] The business middle platform is to formulate enterprise-level standards and mechanisms, standardize the business rules and links that can be shared within the enterprise through information technology, and provide services in a unified manner, effectively reducing the communication costs of various organizational entities within the enterprise, improving production efficiency, and responding to market needs and changes in an agile manner to enhance the core competitiveness of the enterprise. Its core principles are centralized control and distributed execution, creating a strong basic support, flexible front-end tentacles, and agile acceptance of market needs and changes, rooting the business capabilities of the enterprise in the social environment, and enhancing the core competitiveness of the enterprise.

[0031] The business middle platform carries the core key business of the enterprise, is the core business capability of the enterprise, and is also the focus of the enterprise's digital transformation. The construction goal of the business middle platform is to deposit reusable business capabilities into the business middle platform, realize enterprise-level business capability reuse and interconnection and collaboration between various business segments, ensure the stability and efficiency of key business links, and improve business innovation efficiency.

[0032] The main goal of the business middle platform is to achieve the reuse of enterprise-level business capabilities, so the construction of the business middle platform must give priority to solving the problem of duplicate construction and reuse of business capabilities. By reconstructing the business model, the duplicated business capabilities scattered in different channels and business scenarios, such as Internet applications and traditional core applications, will be deposited into the enterprise-level middle platform business model, facing all business scenarios and fields of the enterprise, to achieve capability reuse and process integration. The core value of the business middle platform lies in transforming the business capability IT model into a business capability asset model, thereby improving business agility and the speed of responding to the market, and then achieving the goal of improving enterprise quality transformation, reducing costs and increasing efficiency.

[0033] Currently, the business platform for power marketing and customer service is designed and built according to the traditional microservice architecture (such as Figure 1 As shown in the figure, the business middle platform consists of middle platform microservices, data microservices and databases, and the business application consists of front-end applications and front-end microservices. The middle platform microservices are divided into different business capability centers according to the domain model design method. The front-end microservices call the middle platform microservices provided by different business capability centers to provide common service capability support for the front-end applications. The middle platform microservices access the database by calling the data microservices.

[0034] However, in the related art, there are the following disadvantages:

[0035] (1) The service scope of power grid enterprises is vast, and each province serves customers according to local conditions. As a result, there are various differences in business habits and content. Changes in business needs can be attributed to new businesses, changes in business content, and changes in business requirements. These changes lead to the addition or modification of business models. Changes in business models will lead to a series of changes in the service model, data model, and other aspects of the existing business middle-end architecture, resulting in additional new development work and ultimately system changes.

[0036] (2) Business objects can be seen as unified language descriptions of business scenarios, but the business scenarios of each network and province are often different. Such differences will be reflected in the business objects, and in turn lead to adjustments to the domain model, and ultimately lead to changes in the business middle platform.

[0037] In order to solve the problems existing in the above-mentioned prior art, the solution of this application is proposed. This application provides a business middle platform architecture device based on digital twin objects, which fully meets the personalized needs of users, reduces the impact on the system architecture, and reduces the system construction and maintenance costs. Fully meet personalized needs, fully consider the system changes brought about by the personalized needs of each network province from the architectural design, and establish flexible configurations and scalable functions through work order engine process configuration, business engine rule configuration, professional function extension service development and other methods to meet the adaptation requirements of the network province's personalized needs, realize the dynamic expansion of the external services of the middle platform, support the rich and diverse service products, agile iteration, improve flexibility, and effectively meet the new service needs of multiple subjects, multiple contents, and multiple methods. Reduce the impact on the system architecture, the digital twin object corresponds to the objective reality in reality, and its existence is not affected by the business status. Therefore, new business, business content changes, business requirements changes, business model additions or modifications, etc. have little effect on the digital twin object, so that the business middle platform can be stable, unified and orderly updated, which is conducive to ensuring the stability and universality of the business middle platform. Reduce system construction and maintenance costs, use digital twin objects to construct general services as the basis of the business middle platform, and only need to configure the work order engine process, business engine rules, professional function extension services, etc.; and the upper-level business applications, including front-end applications, front-end microservices, data microservices, etc., do not need to be changed, which will greatly reduce the construction and maintenance costs of the business middle platform.

[0038] In a specific example, the relevant terms of this embodiment are explained as follows:

[0039] Engine: It is the core component of a program or system. Using the engine, developers can quickly create and lay out the functions required by the program, or use it to assist the operation of the program.

[0040] Digital twin: It makes full use of physical models, sensor updates, operation history and other data, integrates multi-disciplinary, multi-physical quantity, multi-scale, and multi-probability simulation processes, completes mapping in virtual space, and thus reflects the entire life cycle of the corresponding physical equipment.

[0041] Digital entity (virtual entity): refers to the mapping of physical entity in the information system.

[0042] Digital twin object: refers to a unified digital entity object of a certain type of physical entity in an information system, and a corresponding model created in the virtual world through digital modeling and simulation technology. By creating a digital twin object, the physical object can be simulated, simulated and analyzed in the virtual world to achieve the purpose of optimizing design, prediction and decision-making.

[0043] Digital twin engine: It is the core component that drives the digital twin object. The digital twin engine is an operation and control device developed based on the configurable digital twin object.

[0044] Microservice: A service unit with high cohesion formed by splitting according to business capabilities and business relevance, which can be independently deployed, run, upgraded and evolved.

[0045] Microservice architecture: an application architecture oriented towards business capability planning. The services in the microservice architecture are business modules extracted based on business capabilities. They are independently developed and deployed, but need to cooperate with each other to complete the entire business function.

[0046] like Figure 2 As shown, the present application proposes a business middle platform architecture system 100 based on digital twin objects. The system 100 includes a front-end module, an engine module and a storage module coupled in sequence.

[0047] The front-end module includes the front-end application and the front-end microservice sub-modules.

[0048] like Figure 3 As shown, the engine module includes the work order engine, business engine, digital engine, microservice sub-module, professional extension service and other microservices.

[0049] It consists of a work order engine, a business engine, a twin engine, function extension services, data microservices, other microservices, and corresponding process databases, business configuration and credential databases, entity archives and status databases, entity ledger databases, etc.

[0050] Among them, the business middle platform service part is provided by the work order engine, business engine, twin engine, function extension service, data microservice, etc., which are described in detail as follows:

[0051] 1. Work Order Engine

[0052] The work order engine implements business flow management. It automatically generates work orders according to business needs and monitors the processing of work orders. The work order engine can also flexibly configure the processing flow and links of work orders according to business needs to meet various complex business needs. Work distribution is achieved by configuring roles in business links, and multiple dispatching methods such as designated dispatching, grid dispatching, grabbing orders, and automatic dispatching can be implemented. Business process support enables the execution procedures of each business link to be customized and flexibly configured. By extracting the common business capabilities of existing businesses to form a business unit library, the existing business units can be directly reused; for the design of new business units, analysis and extraction are included in the business unit library, which effectively reduces the workload of business design and supports agile business iteration. Work order management is driven by business processes, and dispatch is initiated from the business center. The business center calls the work order engine to dispatch. The work order engine generates business to-do items to the PC and mobile terminals based on the work order information and scheduling rules issued by the business center.

[0053] 2. Business Engine

[0054] The business engine implements business object configuration and management. Business configuration can customize the attributes and behaviors of business objects according to business needs and form business rules to meet various complex business needs. The business engine separates the business decision-making part of the application that is dynamic and changeable over time and space, and uses predefined semantic modules to write business decisions. Users or developers configure and manage it when needed, so as to separate business decisions from application code, accept data input, interpret business rules, and make business decisions based on business rules. The business engine tests and compares the data objects currently submitted to the engine with the business rules loaded in the engine, activates those business rules that meet the current data status, and triggers the corresponding operations in the application according to the execution logic declared in the business rules. Through the standardized and modular construction of the business rule library, the business engine can form a flexible and adaptable business rule library covering all businesses.

[0055] 3. Twin Engines

[0056] The digital twin engine is the core component that drives the digital twin object. The digital twin engine is an operation and control device developed based on the configurable digital twin object. The digital twin engine is composed of twin operation management tools, twin engine body, twin object management, twin configuration maintenance tools, etc.

[0057] 4. Professional extension services

[0058] Specialized business services in digital twin objects are provided by professional function extension services. For professional business services, such as electricity billing services, the digital twin engine converts digital twin services into messages and sends them to professional function extension services for processing.

[0059] 5. Data Microservices

[0060] Data microservices interact specifically with the database. Data microservices are responsible for maintaining aggregated business and data consistency, ensuring the integrity of aggregated internal business, and supporting the implementation of business operations such as adding, deleting, modifying, and querying the database or their combined orchestration operations. For database read and write operations, the digital twin engine calls the data microservice to complete them.

[0061] In the digital twin engine, the core is the management, operation and control of the digital twin object. In the present invention, the digital twin object consists of five parts: attributes, services, events, relationships, and others. The specific description is as follows:

[0062] 1. Attributes are dynamically extensible parameter descriptions of digital twin objects, which can describe and manage new parameters of new digital twin objects. Attributes include object identification, parameters, and status. Attributes can be described in the form of key-value pairs, where the key represents the name of the attribute and the value represents the value or type of the attribute.

[0063] 2. Services can be described in a similar way to RPC. Services include service name, service identifier, service description, calling method, input list, and output list. Input parameters and output results can be attributes or the return value of another service. Functions can be abstracted into services to achieve dynamic and extensible service descriptions, so that new functions of new digital twin objects can be described and managed.

[0064] 3. Events can be described by name and trigger conditions. Trigger conditions can be changes in the state of a physical entity or system or the occurrence of other events. Events include event identifiers and state lists.

[0065] 4. Relationship description: The connection relationship between digital twin objects includes inheritance, association, aggregation, combination, generalization and other relationship types. The relationship should include relationship identifier, relationship object and other contents. For example, the relationship description between digital entities can describe and manage various relationships between entities. Relationship has two meanings: one is the relationship between the entity as a whole and the entity individual, and the other is the information exchange relationship between the entity as a whole and other individuals.

[0066] 5. Other parts include task lists, clocks, etc. Among them, the task list describes the tasks or operations that the digital twin object needs to perform, and requires a dynamically extensible task description, so that the process of receiving instructions and processing by the management digital entity can be described; when there are many automatic tasks, multiple tasks can be received, and priority response and reasonable arrangement of automatic tasks are required. The clock describes the time attributes of the digital twin object, including the current time, time offset, and time unit.

[0067] TSL (Thing Specification Language) can be used to describe the properties, services, events, relationships, task lists, and clocks in digital twin objects. Through TSL description, a mapping relationship between digital twin objects and physical entities or systems can be established to achieve real-time interaction and information transfer between the physical world and the virtual world, and to achieve more flexible and diverse interactive operations. Based on various records and operations in the business model, the properties, services, events, and other aspects of the digital twin object can be improved. By establishing inheritance, association, and other relationships between digital twin objects, duplicate content between digital twin object models can be eliminated.

[0068] The storage module includes the process database, business configuration and credential database, entity archive and status database and entity ledger database.

[0069] The specific description is as follows:

[0070] 1. Process database.

[0071] The process database is responsible for storing and managing the relevant data of the business process. The process database can record each link and step of the process, as well as the processing results of each link and step.

[0072] 2. Business configuration and credential database.

[0073] The business configuration and voucher database is responsible for storing and managing the relevant data of business configuration and vouchers. The business configuration and voucher database can record the configuration information of each link and step of the business, as well as the voucher information of each link and step. For example, in customer service management, metering equipment management, billing management, contract account receivables and payables management, each module has its corresponding business configuration and business vouchers. Customer service management has contact sheets, metering equipment management has meter reading work sheets, billing management has billing vouchers, and contract receivables and payables management has financial vouchers, etc.

[0074] 3. Entity archives and status database.

[0075] The entity archive and model database is responsible for storing and managing detailed information and status information of digital entities. The entity archive and model library can record the attributes, relationships and behaviors of digital entities, as well as the status information of entities. The digital twin engine reads the archive information and initialization information of digital entities from the entity archive and status database, and writes the latest status information when the status of a digital entity is updated.

[0076] 4. Physical ledger database.

[0077] The entity ledger database is responsible for storing and managing the ledger information of digital entities. The entity ledger database records the ledger information of digital entities throughout their life cycle and saves process records, including information such as the attributes, relationships, and behaviors of entities.

[0078] like Figure 4 As shown, the access links between the modules of the system 100 in this embodiment are as follows:

[0079] 1. The front-end application calls the front-end microservice;

[0080] 2. The front-end microservices call the services provided by various engines, and some query microservices can also directly call the data microservices without going through the middle-end microservices;

[0081] 3. Various engine services call data microservices;

[0082] 4. For professional business services, such as billing services, the digital twin engine converts the twin service into a message and sends it to the professional function adaptation service for processing.

[0083] 5. Data microservice access storage module.

[0084] The front-end application is directly facing various users. According to the interaction needs of the front-end application, it orchestrates and integrates the business service capabilities of the business middle platform to provide support for the interaction and display of the front-end interface.

[0085] Front-end microservices are the carriers of innovative and personalized applications. They call business middle-end services through application service orchestration to meet the rapidly changing needs of the business and provide sufficient flexibility for business research and development.

[0086] The engine module consists of the work order engine, business engine, digital twin engine, etc. When the digital twin object is used as the aggregate root, the software structure of each aggregate root is exactly the same, so it can be merged to form a general business service based on the digital twin engine. When executing the digital twin object service, the digital twin engine is responsible for executing the get / set operation service of the twin object attribute.

[0087] Specialized business services in digital twin objects are provided by professional function extension services. For professional business services, such as billing services, the digital twin engine converts the twin service into a message and sends it to the professional function extension service for processing.

[0088] According to the scheme of this application, a business middle platform architecture system based on digital twin objects is provided to fully meet the personalized needs of users, reduce the impact on the system architecture, and reduce the cost of system construction and maintenance. Fully meet personalized needs, fully consider the system changes brought about by the personalized needs of each network province from the perspective of architecture design, and establish flexible configurations and scalable functions through work order engine process configuration, business engine rule configuration, professional function extension service development, etc., to meet the adaptation requirements of the personalized needs of the network province, realize the dynamic expansion of the external services of the middle platform, support the rich and diverse service products, agile iteration, improve flexibility, and effectively meet the new service needs of multiple subjects, multiple contents, and multiple methods. Reduce the impact on the system architecture, the digital twin object corresponds to the objective reality in reality, and its existence is not affected by the business status. Therefore, new business, changes in business content, changes in business requirements, additions or modifications to business models, etc. have little effect on the digital twin object, so that the business middle platform can be stable, unified and orderly updated, which is conducive to ensuring the stability and universality of the business middle platform. Reduce system construction and maintenance costs, use digital twin objects to construct general services as the basis of the business middle platform, and only need to configure the work order engine process, business engine rules, professional function extension services, etc.; and the upper-level business applications, including front-end applications, front-end microservices, data microservices, etc., do not need to be changed, which will greatly reduce the construction and maintenance costs of the business middle platform.

[0089] For the convenience of description, the above device is described in terms of functions divided into various modules. Of course, when implementing the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0090] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0091] Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in the devices described in the embodiment, or alternatively may be located in one or more devices different from the devices in the examples. The modules in the foregoing examples may be combined into one module or may be divided into multiple submodules.

[0092] Based on the same technical concept, corresponding to any of the above-mentioned embodiment systems, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and run on the processor. When the processor executes the program, it implements the functions of different modules in the business middle-office architecture system based on digital twin objects described in any of the above embodiments.

[0093] Figure 5 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0094] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0095] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0096] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0097] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0098] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0099] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0100] Based on the same technical concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable the computer to execute the functions of different modules in the business middle-end architecture system based on digital twin objects as described in any of the above embodiments.

[0101] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0102] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0103] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0104] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0105] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of the present application.

Claims

1. A business middle platform architecture system based on digital twin objects, characterized in that: include: A front-end module, an engine module and a storage module coupled in sequence, wherein the engine module at least includes a digital engine; The front-end module is adapted to receive a user's service request and send the service request to the engine module; The engine module is suitable for using the digital engine to call the twin extension service to extract data resources in the storage module to process the professional request when it is determined that the business request is a professional request.

2. The system according to claim 1, characterized in that The front-end module includes a front-end application and a front-end microservice sub-module; The front-end application is suitable for performing data interaction with the user to receive the service request; The foreground microservice submodule is suitable for parsing the business request to determine the type of the business request and calling the corresponding engine according to the type of the business request.

3. The system according to claim 2, characterized in that The engine module also includes a work order engine, which is suitable for automatically generating a work order and monitoring the processing process of the work order according to the user's business needs when the type of the business request is a type related to the work order.

4. The system according to claim 2, characterized in that The engine module also includes a business engine, which is suitable for configuring and managing business objects according to the business needs of users when the type of the business request is a type related to business personnel.

5. The system according to any one of claims 1 to 4, characterized in that: The engine module also includes a data microservice submodule, which is suitable for receiving processing requests from each engine and calling the data stored in the storage module to respond to the processing request.

6. The system according to claim 1, characterized in that The digital engine is also suitable for calling the digital twin object to process the business request when the type of the business request is a non-professional request related to the digital twin.

7. The system according to claim 3, characterized in that The storage module includes a process database sub-coupled to the work order engine, and is suitable for storing and managing business process data related to the work order.

8. The system according to claim 4, characterized in that The storage module includes a business configuration and credential database sub-coupled to the business engine, and is suitable for storing and managing business configuration and credential related data.

9. The system according to claim 1, characterized in that The storage module includes an entity archive and a status database coupled to the digital engine, and is suitable for storing and managing detailed information and status information of digital entities.

10. The system according to claim 1, characterized in that The storage module includes an entity ledger database coupled to the twin extension service, which is suitable for storing and managing ledger information of digital entities.

Images