A system, method and platform for extending processing based on discrete data models

Abstract

The application belongs to the technical field of product data management, and particularly relates to a discrete data model extension processing system, method and platform. The discrete data model extension processing system comprises a source unit for providing a system basic service architecture; a context creation management unit for creating and managing system storage paths and domain positions; a life cycle template construction unit for constructing system business object state data blocks; and a type extension processing unit for real-time management of system business model types, attributes and binding extension processing model life cycles, team templates and storage positions. The application also relates to corresponding methods, platforms and storage media, and can quickly extend business data models and meet the data model extension processing of business requirements.

Description

Technical Field

[0001] This invention belongs to the field of product data management technology, specifically relating to an extended processing system, method, and platform based on a discrete data model. Background Technology

[0002] With the development of the internet, microservices have emerged as an architectural style. A large, complex software application is composed of one or more microservices. Each microservice can be deployed independently, and they are loosely coupled. Each microservice focuses on completing a single task and performing that task well. In a microservice architecture, business data models are separated into different services based on business domains. However, some models are used by all services and need to be redundant across them. This allows for database sharding and table partitioning to reduce the query pressure on a single database.

[0003] In today's mainstream manufacturing applications, the complexity and strong coupling of business logic prevent the use of microservice architecture to decompose these applications. However, with the rapid development of production technology, management software also needs to iterate quickly to meet new business scenarios. Existing monolithic applications are increasingly unable to meet the demands. Therefore, it is necessary to propose an extended processing system, method, and platform based on a discrete data model to address the aforementioned technical deficiencies. Summary of the Invention

[0004] To address the technical problems and shortcomings of existing monolithic applications that cannot be decomposed using a microservice architecture due to their complex business logic and strong coupling, and the increasing inadequacy of existing monolithic applications to meet the demands of rapid advancements in production technology, this invention provides an extended processing system, method, and platform based on a discrete data model. In other words:

[0005] The first objective of this invention is to provide an extended processing system based on a discrete data model.

[0006] The second objective of this invention is to provide an extended processing method based on a discrete data model;

[0007] The third objective of this invention is to provide an extended processing platform based on a discrete data model;

[0008] The fourth objective of this invention is to provide a computer-readable storage medium;

[0009] The first objective of this invention is achieved as follows: the system specifically includes: a source unit for providing the system's basic service architecture; a context creation and management unit for creating and managing the system's storage paths and domain locations; a lifecycle template construction unit for building the system's business object status data module; and a type extension processing unit for real-time management of the system's business model types, attributes, and binding extension processing model lifecycles, team templates, and storage locations.

[0010] Furthermore, the system also includes a management generation unit for managing various business services that depend on the basic services and generating a unique identifier primary key for each business service.

[0011] Furthermore, the context creation management unit includes a hierarchical division module for dividing the context into sites, organizations, and product libraries; and a corresponding quantity limit module for real-time limiting of the number of applications and site management related to each other.

[0012] An isolation module for real-time complete data isolation between organizations under a site; a finished goods library creation module for creating product libraries under an organization;

[0013] This is a distributed caching module used to cache and share container, organization, and domain information in the system to various business services in a distributed manner.

[0014] Furthermore, the lifecycle template construction unit is configured with:

[0015] The first building module is used to construct the state of each stage of the system business object; the second building module is used to construct the conditions for the transition between the states of the system business object; the third building module is used to construct the management process required to confirm each state of the system business object; the fourth building module is used to construct the dynamic permission configuration of the system business object at each stage; the information acquisition module is used to obtain lifecycle stage information from the cache; and the permission setting module is used to set the state of each stage of the business object, start the process and set dynamic permissions.

[0016] Furthermore, the type extension processing unit is provided with:

[0017] The first module is used to divide the system business object permission policy into static permissions; the second module is used to divide the system business object permission policy into dynamic permissions; and the team division module is used to redundancy related data across various services and manage it according to their own needs.

[0018] Furthermore, the type extension processing unit is also provided with:

[0019] The first extension module is used to uniformly register all types of managed data models in the service to the corresponding modules and manage them in real time.

[0020] This is a second extension module used to maintain the root type by adding subtypes and setting different type names, lifecycles, and management processes.

[0021] A third extension module for implementing requirements by adding new attribute classes to the type management attribute list.

[0022] This invention also provides a method for extending processing based on a discrete data model, the method specifically including the following steps:

[0023] Create the system's basic service architecture;

[0024] Based on the system's basic service architecture, create the system's storage path and domain location;

[0025] Construct a template for the system's business object status data module;

[0026] The system manages the business model types, attributes, and bindings of extended processing models, as well as team templates and storage locations in real time.

[0027] Furthermore, the method also includes the steps of: real-time management of various business services that depend on the basic service, and generating a unique identifier primary key for each business service;

[0028] The steps for creating the system's basic service architecture also include the following steps:

[0029] Real-time complete isolation of data between organizations under the site;

[0030] The system caches and shares container, organization, and domain information in a distributed manner across various business services.

[0031] The step of constructing the system business object status data module template also includes the following steps:

[0032] Configure the state of each stage of the business object, the conditions for transition between states, the management process required for each state, and the dynamic permissions for each stage;

[0033] The real-time management system's business model type, attributes, and bound extended processing model lifecycle, team template, and storage location steps also include the following steps:

[0034] The system's business object permission policy is divided into static permissions and dynamic permissions.

[0035] The present invention also provides an extended processing platform based on a discrete data model, the platform comprising:

[0036] Processor, memory, and platform control program based on discrete data model extended processing;

[0037] The processor executes the platform control program based on discrete data model extension processing, which is stored in the memory. The platform control program based on discrete data model extension processing implements the steps of the discrete data model extension processing method as described above.

[0038] The present invention also provides a computer-readable storage medium storing a platform control program based on discrete data model extended processing, wherein the platform control program based on discrete data model extended processing implements the method steps of the method based on discrete data model extended processing.

[0039] Compared with the prior art, the present invention has the following beneficial effects:

[0040] This invention provides a discrete data model-based extended processing system, comprising: a source unit for providing the system's basic service architecture; a context creation and management unit for creating and managing system storage paths and domain locations; a lifecycle template construction unit for building system business object state data modules; and a type extended processing unit for real-time management of system business model types, attributes, and binding extended processing model lifecycles, team templates, and storage locations, along with corresponding methods, platforms, and storage media; enabling rapid extension of business data models and meeting their business needs. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic diagram of a system architecture based on extended processing of discrete data models according to the present invention;

[0043] Figure 2 This is a schematic diagram of the process architecture of a method for extended processing based on a discrete data model according to the present invention;

[0044] Figure 3 This is a schematic diagram of a platform architecture based on extended processing of discrete data models according to the present invention;

[0045] Figure 4 This is a schematic diagram of a computer-readable storage medium architecture in one embodiment of the present invention;

[0046] Figure 5This is a schematic diagram of the architecture of one embodiment of the system based on extended processing of discrete data models according to the present invention;

[0047] Figure 6 This is a schematic diagram of the architecture of a second embodiment of the system based on extended processing of discrete data models according to the present invention;

[0048] Figure 7 This is a schematic diagram of the architecture of a third embodiment of the system based on extended processing of discrete data models according to the present invention;

[0049] Figure 8 This is a schematic diagram of the architecture of a fourth embodiment of the system based on extended processing of discrete data models according to the present invention;

[0050] Figure 9 This is a schematic diagram of the architecture of the fifth embodiment of the system based on extended processing of discrete data models according to the present invention;

[0051] Figure 10 This is a schematic diagram of the architecture of a sixth embodiment of the system based on extended processing of discrete data models according to the present invention;

[0052] Figure 11 This is a schematic diagram of the architecture of the seventh embodiment of the system based on extended processing of discrete data models according to the present invention;

[0053] Figure 12 This is a schematic diagram of the eighth architecture of a system embodiment based on extended processing of discrete data models according to the present invention;

[0054] The objectives, features, and advantages of this invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0055] To facilitate a clearer understanding of the objectives, technical solutions, and advantages of this invention, the invention will be further described below in conjunction with the accompanying drawings and specific embodiments. Those skilled in the art can easily understand other advantages and effects of this invention from the content disclosed in this specification.

[0056] This invention can also be implemented or applied through other different specific examples, and various details in this specification can also be modified and changed based on different viewpoints and applications without departing from the spirit of this invention.

[0057] It should be noted that if the embodiments of the present invention involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of the components in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indicators will also change accordingly.

[0058] Furthermore, if the embodiments of this invention involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Secondly, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed by this invention.

[0059] Preferably, the discrete data model-based extended processing system of the present invention is applied in one or more terminals or servers. The terminal is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0060] The terminal can be a desktop computer, laptop, handheld computer, or cloud server, etc. The terminal can interact with the customer via a keyboard, mouse, remote control, touchpad, or voice control device.

[0061] This invention provides a system and method for extending the processing of discrete data models.

[0062] like Figure 2 The diagram shown is a flowchart of an extended processing method based on a discrete data model provided in an embodiment of the present invention.

[0063] In this embodiment, the method for extended processing based on discrete data models can be applied to terminals or fixed terminals with display functions. The terminals are not limited to personal computers, smartphones, tablets, desktop computers or all-in-one computers with cameras, etc.

[0064] The method for extended processing based on discrete data models can also be applied to a hardware environment consisting of a terminal and a server connected to the terminal via a network. The network includes, but is not limited to, wide area networks (WANs), metropolitan area networks (MANs), or local area networks (LANs). The method for extended processing based on discrete data models in this embodiment can be executed by the server, by the terminal, or by both the server and the terminal.

[0065] For example, for terminals requiring discrete data model-based extended processing, the discrete data model-based extended processing functionality provided by the method of this invention can be directly integrated onto the terminal, or a client for implementing the method of this invention can be installed. Alternatively, the method provided by this invention can also run on servers or other devices in the form of a Software Development Kit (SDK), providing an interface for discrete data model-based extended processing functionality in the form of an SDK. Terminals or other devices can then implement this functionality through the provided interface.

[0066] The present invention will be further described below with reference to the accompanying drawings.

[0067] like Figure 1 As shown, this invention provides an extended processing system based on a discrete data model, the system specifically comprising:

[0068] The system includes: a source unit for providing basic service architecture; a context creation and management unit for creating and managing system storage paths and domain locations; a lifecycle template building unit for building system business object state data modules; and a type extension processing unit for real-time management of system business model types, attributes, and binding extension processing model lifecycles, team templates, and storage locations.

[0069] The system also includes a management generation unit for managing various business services that depend on the basic services and generating a unique identifier primary key for each business service.

[0070] The aforementioned context creation management unit includes a hierarchical division module for dividing the context into sites, organizations, and product libraries; and a corresponding quantity limit module for real-time limiting of the number of applications and site management related to each other.

[0071] An isolation module for real-time complete data isolation between organizations under a site; a finished goods library creation module for creating product libraries under an organization;

[0072] This is a distributed caching module used to cache and share container, organization, and domain information in the system to various business services in a distributed manner.

[0073] The lifecycle template construction unit includes: a first construction module for constructing the states of each stage of a system business object; a second construction module for constructing the conditions for transitions between the states of a system business object; a third construction module for constructing the management processes required to confirm the states of each system business object; a fourth construction module for constructing the phased dynamic permission configuration of a system business object; an information acquisition module for retrieving lifecycle stage information from the cache; and a permission setting module for setting the states of each stage, the startup process, and the dynamic permissions for the business object.

[0074] The type extension processing unit is equipped with: a first partitioning module for dividing the system business object permission policy into static permissions; a second partitioning module for dividing the system business object permission policy into dynamic permissions; and a team partitioning module for redundantly allocating relevant data to various services and managing it according to their own needs.

[0075] The type extension processing unit is also provided with a first extension module for uniformly registering all types of managed data models in the service to the corresponding modules and managing them in real time.

[0076] The second extension module is used to maintain the type by adding subtypes under the root type and setting different type names, lifecycles, and management processes; the third extension module is used to implement requirements by adding attribute classes in the type management attribute list.

[0077] In other words, as shown in the appendix Figure 1-12 As shown, in the present invention, an extended processing system based on a discrete data model is provided. First, the basic management function module of the system is implemented in the basic service. Other services are business services extended on the basis of the basic service. Each module in the basic service provides SDK methods to provide characteristic behavior capabilities for each business service.

[0078] Through the context management module, the context defines the system storage path and domain location. The context is divided into three levels: site, organization, and product repository. An application can only manage one site, and there can be multiple organizations under a site. Data between organizations is completely isolated, but they can share the data and templates under the site. Multiple product repositories can be created under an organization. The product repository is used to store business data models to meet the needs of various business scenarios. With the help of distributed caching, the container, organization, and domain information in this module are shared with various business services. The basic SDK provides interfaces for container management and domain management, and manages the storage location of cached data.

[0079] The lifecycle template module defines the states of business objects at each stage, the conditions for transitions between states, the management processes required for each state, and the configuration of dynamic permissions for each stage. A distributed cache is used to share lifecycle template data to various business services, which can directly retrieve lifecycle stage information from the cache; and set the states, startup processes, and dynamic permissions for each stage of the business object.

[0080] The object permission policy module divides permission policies into two main categories: static permissions: site policies, organization policies, and container policies for products / standard libraries; and dynamic permissions: lifecycle permissions, process permissions, and business object permissions.

[0081] The team module serves as a common data model that all business services need to use, yet it does not require aggregated queries. Therefore, it is redundantly distributed across various services, with each service essentially having its own team module that can be managed according to its own needs.

[0082] The type management module defines the types and attributes of business data models, as well as their lifecycles, team templates, and storage locations. Through extended models: Type management is responsible for registering all type-hosted data models in each service to this module for unified management when the service starts. The root type of type management uses the data model's class name as its internal name. After a model is registered with type management, its lifecycle, team template, storage location, and coding rules can be maintained. Extended subtypes: When there are multiple similar business data models, subtypes can be added under the root type for maintenance, setting different type names, lifecycles, and even management processes. Extended type attributes: Each type has different attributes; for example, components include structural components and software components. Besides common attributes, they also need personalized attribute requirements, which can be implemented by adding attribute classes to the attribute list in type management.

[0083] In other words, a service registration model is defined in the basic services to manage various business services that depend on the basic services; and a unique identifier primary key is generated for each business service.

[0084] All root types registered to the type management module through a model need to be marked with the identifier of the service to which they belong. In the basic SDK component package, a service startup event is defined. In this event, all data models managed by the type are scanned and registered to the type management module via RPC remote call. At the same time, the service that registered the model is recorded. The SDK defines interfaces for extending the table structure and calculating the available data column fields. When a user adds a type attribute in the type management module, the available data table column fields and the extended table structure are calculated by RPC remote call based on the identifier of the service to which the type belongs.

[0085] Specifically, the interface for calculating available data column fields has the following input parameters: the model class name to which the type belongs, and the service identifier primary key to which the model belongs; the main logic is to remotely call the service to which the model belongs via RPC to obtain the actual physical table column fields that the current model already exists in the database; and to calculate whether there are any available column fields by using the table column fields associated with the used attributes in the type management.

[0086] For the extended table structure interface: Input parameters: model class name to which the type belongs, service identifier primary key to which the model belongs, number of columns to be extended, name, and column type; Main logic: remotely call the service to which the model belongs via RPC, the model obtains the table name, column type, and quantity, calculates the name of the extended column and the corresponding data type in the database, assembles it into an altertable SQL statement to execute the extended column; after success, record the usage relationship between the attribute and the table column in the type management.

[0087] To achieve the above objectives, such as Figure 2 As shown, the present invention also provides a method for extending processing based on a discrete data model: the method specifically includes the following steps:

[0088] S1. Create the system's basic service architecture;

[0089] S2. Based on the system's basic service architecture, create the system's storage path and domain location;

[0090] S3. Construct a template for the system business object status data module;

[0091] S4 manages the business model types, attributes, and bindings of extended processing models, as well as team templates and storage locations in real time.

[0092] The method further includes the following steps: S50, real-time management of each business service that depends on the basic service, and generating a unique identifier primary key for each business service;

[0093] The steps for creating the system's basic service architecture also include the following steps:

[0094] S11. Real-time complete isolation of data between organizations under the site;

[0095] S12. Cache and share container, organization, and domain information in the system to various business services in a distributed manner;

[0096] The step of constructing the system business object status data module template also includes the following steps:

[0097] S31. Construct the state of each stage of the business object, the conditions for transition between states, the management process required for each state, and the configuration of dynamic permissions for each stage.

[0098] The real-time management system's business model type, attributes, and bound extended processing model lifecycle, team template, and storage location steps also include the following steps:

[0099] S41. Divide the system business object permission policy into static permissions and dynamic permissions.

[0100] For specific details on the methods and steps, please refer to the descriptions in the system above; they will not be repeated here.

[0101] To achieve the above objectives, the present invention also provides a platform based on extended processing of discrete data models, such as... Figure 3 As shown, it includes:

[0102] Processor, memory, and platform control program based on discrete data model extended processing;

[0103] The processor executes the platform control program based on the discrete data model extension processing. This platform control program is stored in the memory. The platform control program implements the method steps of the discrete data model extension processing, for example:

[0104] S1. Create the system's basic service architecture;

[0105] S2. Based on the system's basic service architecture, create the system's storage path and domain location;

[0106] S3. Construct a template for the system business object status data module;

[0107] S4 manages the business model types, attributes, and bindings of extended processing models, as well as team templates and storage locations in real time.

[0108] The specific details of the steps have been explained above and will not be repeated here.

[0109] In this embodiment of the invention, the platform-embedded processor based on discrete data model extended processing can be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits with the same or different functions, including combinations of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The processor connects to various components using various interfaces and lines, and executes programs or units stored in memory, as well as calls data stored in memory, to perform various functions and process data based on discrete data model extended processing.

[0110] The memory is used to store program code and various data. It is installed in the platform based on discrete data model extended processing and enables high-speed and automatic access to programs or data during operation.

[0111] The memory includes read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium capable of carrying or storing data.

[0112] To achieve the above objectives, the present invention also provides a computer-readable storage medium, such as... Figure 4 As shown, the computer-readable storage medium stores a platform control program based on discrete data model extended processing. This platform control program implements the method steps of the discrete data model extended processing method, for example:

[0113] S1. Create the system's basic service architecture;

[0114] S2. Based on the system's basic service architecture, create the system's storage path and domain location;

[0115] S3. Construct a template for the system business object status data module;

[0116] S4 manages the business model types, attributes, and bindings of extended processing models, as well as team templates and storage locations in real time.

[0117] The specific details of the steps have been explained above and will not be repeated here.

[0118] In the description of embodiments of the present invention, it should be noted that any process or method description in the flowcharts or otherwise described herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of the present invention includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order according to the functions involved, as should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0119] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processing module, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, a “computer-readable medium” can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM).

[0120] Furthermore, the computer-readable medium can even be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0121] In this embodiment of the invention, to achieve the above objective, the present invention also provides a chip system, the chip system including at least one processor, wherein when program instructions are executed in the at least one processor, the chip system performs the method steps of the discrete data model-based extended processing, for example:

[0122] S1. Create the system's basic service architecture;

[0123] S2. Based on the system's basic service architecture, create the system's storage path and domain location;

[0124] S3. Construct a template for the system business object status data module;

[0125] S4 manages the business model types, attributes, and bindings of extended processing models, as well as team templates and storage locations in real time.

[0126] The specific details of the steps have been explained above and will not be repeated here.

[0127] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0128] This invention provides a discrete data model-based extended processing system, comprising: a source unit for providing the system's basic service architecture; a context creation and management unit for creating and managing system storage paths and domain locations; a lifecycle template construction unit for building system business object state data modules; and a type extended processing unit for real-time management of system business model types, attributes, and binding extended processing model lifecycles, team templates, and storage locations, along with corresponding methods, platforms, and storage media; enabling rapid extension of business data models and meeting their business needs.

[0129] The embodiments described above are merely illustrative of several implementations of the present invention, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these modifications and improvements all fall within the scope of protection of the present invention. Therefore, the scope of protection of this patent should be determined by the appended claims.

Claims

1. A discrete data model-based extended processing system, characterized in that... The system specifically includes: a source unit for providing the system's basic service architecture; a context management module for creating and managing system storage paths and domain locations; a lifecycle template construction unit for building system business object state data modules; and a type extension processing unit for real-time management of system business model types, attributes, and binding extension processing model lifecycles, team division templates, and storage locations. The system defines a service registration model within the basic services provided by the source unit to manage various business services that depend on the basic services. The context management module uses a distributed cache to share container, organization, and domain information with the business services. The distributed cache shares the various stages of the business object's state defined by the lifecycle template module, the transition conditions between states, the management processes required for each state, and the staged dynamic permission data with each business service. The type extension processing unit is configured with: A team division module used to redundancy relevant data across various services and manage it according to their own needs; The first extension module is used to uniformly register all types of managed data models in the service to the corresponding modules and manage them in real time. A type management module used to define the types and attributes of business data models, as well as the lifecycle, team templates, and storage locations of the models bound to them; Furthermore, when each service starts, it is responsible for registering all types of managed data models in the service to the type management module for management. In the basic SDK component package, a service startup event is defined. In this event, all types of managed data models are scanned and registered to the type management module via RPC remote call, while recording the services registered for the model.

2. The extended processing system based on a discrete data model according to claim 1, characterized in that... The system also includes a management generation unit for managing various business services that depend on the basic services and generating a unique identifier primary key for each business service.

3. The extended processing system based on a discrete data model according to claim 1, characterized in that... The context management module includes a hierarchical division module for classifying contexts into sites, organizations, and product libraries; This module is used to limit the corresponding quantity of applications and site management in real time. An isolation module used for real-time complete isolation of data between organizations under a site; Finished Goods Library Creation Module for creating product libraries under an organization; This is a distributed caching module used to cache and share container, organization, and domain information in the system to various business services in a distributed manner.

4. The extended processing system based on a discrete data model according to claim 1, characterized in that... The lifecycle template construction unit is configured with: The first building module is used to construct the states of system business objects at each stage; the second building module is used to construct the conditions for transitions between the states of system business objects; the third building module is used to construct the management processes required to confirm the states of system business objects; and the fourth building module is used to construct the phased dynamic permission configuration of system business objects. It also includes an information retrieval module for obtaining lifecycle stage information from the cache, and a permission setting module for setting the status of each stage, the startup process, and setting dynamic permissions for business objects.

5. The extended processing system based on a discrete data model according to claim 1, characterized in that... The type extension processing unit is configured with: The first module is used to divide the system business object permission policy into static permissions; the second module is used to divide the system business object permission policy into dynamic permissions; and the team division module is used to redundancy related data across various services and manage it according to their own needs.

6. A discrete data model-based extended processing system according to claim 1 or 5, characterized in that... The type extension processing unit is further provided with: The first extension module is used to uniformly register all types of managed data models in the service to the corresponding modules and manage them in real time. This is a second extension module used to maintain the root type by adding subtypes and setting different type names, lifecycles, and management processes. A third extension module for implementing requirements by adding new attribute classes to the type management attribute list.

7. A method for extending processing based on discrete data models, characterized in that... The method specifically includes the following steps: Create a system basic service architecture, and define a service registration model in the basic service architecture to manage various business services that depend on the basic services; Based on the aforementioned system infrastructure architecture, system storage paths and domain locations are created, and the created storage path and domain location information is shared to various business services through distributed caching. Build a template for the status data of system business objects, and share the built lifecycle template data to various business services through distributed caching; The real-time management system includes business model types, attributes, and bound extended processing model lifecycles, team division templates, and storage locations; wherein, the steps for defining the business model types of the real-time management system further include: When each business service starts, all types of managed data models are scanned through the service startup event, and the scanned data models are registered to the type management module through remote procedure calls, while the service identifier of the registered model is recorded. The type management module defines the type and attributes of business data models, as well as binds lifecycles to models, assigns templates to teams, and defines storage locations. In response to the operation of adding a new type attribute, the corresponding business service is called remotely based on the service identifier of the type targeted by the operation to calculate the available data column fields or extend the database table structure.

8. The method for extending processing based on a discrete data model according to claim 7, characterized in that... The method further includes the steps of: real-time management of each business service that depends on the basic service, and generating a unique identifier primary key for each business service; The steps for creating the system's basic service architecture also include the following steps: Real-time complete isolation of data between organizations under the site; The system caches and shares container, organization, and domain information in a distributed manner across various business services. The step of constructing the system business object status data module template also includes the following steps: Configure the state of each stage of the business object, the conditions for transition between states, the management process required for each state, and the dynamic permissions for each stage; The real-time management system's business model type, attributes, and bound extended processing model lifecycle, team template, and storage location steps also include the following steps: The system's business object permission policy is divided into static permissions and dynamic permissions.

9. A processing platform based on a discrete data model, characterized in that... The platform includes: Processor, memory, and platform control program based on discrete data model extended processing; The processor executes the platform control program based on discrete data model extension processing, which is stored in the memory. The platform control program based on discrete data model extension processing implements the steps of the method based on discrete data model extension processing as described in any one of claims 7 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a platform control program based on discrete data model extended processing, which implements the method steps of discrete data model extended processing as described in any one of claims 7 to 8.

Images