Layered design architecture of servitization system
By introducing a hierarchical design architecture of abstract service layer, logical service layer and instance service layer in the service system, the problem of difficult service design in SOA is difficult to achieve reusability, inheritability and evolution, and the reuse of system design is improved and high cohesion.
Patent Information
- Application Number
- CN202510020200.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-07
- Publication Date
- 2025-02-14
- Estimated Expiration
- Not applicable · inactive patent
Smart Images
Figure CN119440522A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of computer system design, and in particular to a service-oriented system layered design architecture. Background Art
[0002] Service-oriented architecture (SOA) is a method for designing, developing, deploying and managing discrete logical unit (service) models in a computing environment. In the SOA model, all functions are defined as independent services. Services complete the overall logic of the business through interaction and coordination. All services are connected through a service bus or process manager. This loosely coupled architecture allows each service to interact without considering the internal implementation details of both parties and the platform on which they are deployed. SOA can flexibly build systems and business processes, but the abstract services of SOA lack a technical solution for service reuse, service inheritance, service evolution, and hierarchical design of service architecture. Summary of the invention
[0003] The embodiments of the present application provide a service-oriented system layered design architecture, which can effectively make the service design reusable, inheritable and evolvable.
[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.
[0005] According to a first aspect of an embodiment of the present application, a service-oriented system layered design architecture is provided, including: an abstract service layer, a logic service layer and an instance service layer; The abstract service layer is designed with an abstract service object for defining basic information of the service; the basic information of the service includes the service name, service operation name, service interface name, service signal type name and service operation type; The logic service layer is designed with logic service objects for defining specific service operation logic; The instance service layer is designed with instance service objects for defining specific platform configuration information and deployment relationships.
[0006] In some embodiments of the present application, based on the above solution, the creation method of the abstract service object includes: Obtained by creating it separately; Or it can be obtained by reverse engineering the logic service object.
[0007] In some embodiments of the present application, based on the above solution, the creation method of the logical service object includes: Derived from the abstract service object; Or by creating it separately.
[0008] In some embodiments of the present application, based on the above solution, the creation method of the instance service object includes: Generated by instantiating the logic service object.
[0009] In some embodiments of the present application, based on the aforementioned solution, the abstract service object is divided into: a base class service template, a collection class service template and a twin class service template according to different application scenarios; The base service template only defines the basic information of the service and its service operations / service interfaces, and cannot design the processing logic of the service operations; The collection service template only defines the basic information of the service operation / service interface, but does not define the specific service to which the service operation / service interface belongs; The twin service template only defines the basic information of the service template and does not design the service operation / service interface.
[0010] In some embodiments of the present application, based on the aforementioned scheme, when the abstract service object is a twin-class service template, the twin-class service template is reversely generated from the logical service object, and the service operation and service interface of the twin-class service template are the same as those of the logical service object.
[0011] The technical solution of the present application realizes the hierarchical expression of service object design by dividing the service object into a three-layer design of abstract service object, logical service object and instance service object; the hierarchical design makes the design hierarchy of the service-oriented system clearer, and different layers focus on the design of different levels, thereby improving the high cohesion of the system; the hierarchical design also makes the layers highly reusable, thereby improving the reusability of the system design.
[0012] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings: Figure 1 A schematic diagram of a hierarchical design architecture of a service-oriented system according to an embodiment of the present application is shown; Figure 2 A schematic diagram of a base class service template architecture according to an embodiment of the present application is shown; Figure 3 A schematic diagram of a collection service template architecture according to an embodiment of the present application is shown; Figure 4 A schematic diagram of a twin service template architecture according to an embodiment of the present application is shown. DETAILED DESCRIPTION
[0014] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.
[0015] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.
[0016] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0017] The character “ / ” generally indicates that the previous and next associated objects are in an “or” relationship.
[0018] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution in the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is only a part of the embodiment of the present invention, not all the embodiments. Based on the embodiment of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0019] Some embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. In the absence of conflict, the following embodiments and features in the embodiments may be combined with each other.
[0020] In response to the technical defects existing in the prior art, the embodiment of the present application proposes a hierarchical design architecture for a service-oriented system. This design architecture makes the service design of the service-oriented system inheritable, evolvable, and reusable through the hierarchical design of service objects and the template design of service objects.
[0021] For details, see Figure 1 , showing a schematic diagram of a service-oriented system layered design architecture according to an embodiment of the present application.
[0022] like Figure 1 As shown, a service-oriented system layered design architecture provided by an embodiment of the present application includes: an abstract service layer, a logic service layer and an instance service layer; The abstract service layer is designed with an abstract service object for defining basic information of the service; the basic information of the service includes the service name, service operation name, service interface name, service signal type name and service operation type; The logic service layer is designed with logic service objects for defining specific service operation logic; The instance service layer is designed with instance service objects for defining specific platform configuration information and deployment relationships.
[0023] It should be noted that the service object is a combination of the basic construction elements in the service-oriented system architecture. In this application, the service objects are divided into three categories: abstract service objects, logical service objects and instance service objects.
[0024] like Figure 1 As shown, the three service layers, namely the abstract service layer, the logical service layer and the instance service layer, are arranged in sequence from top to bottom. The abstract service objects in the abstract service layer only play the role of defining the basic information of the service and do not design the processing logic of the specific service.
[0025] The logical service objects in the logical service layer define the specific service operation logic, including the establishment of service dependencies, which is similar to program source code.
[0026] The instance service object in the instance service layer is a specific running service entity that defines specific platform configuration information and deployment relationships, similar to a compiled executable program. Runtime concerns such as master-slave logic, load balancing, network routing, protocol conversion, and traffic monitoring are all designed in the instance service layer.
[0027] It is understandable that the layered design approach makes the design levels of the service-oriented system clearer, with different layers focusing on designs at different levels, thus improving the high cohesion of the system; the layered design also allows for high reuse between layers, thus improving the reusability of the system design.
[0028] In some feasible embodiments, based on the above solution, the creation method of the abstract service object includes: Obtained by creating it separately; Or it can be obtained by reverse engineering the logic service object.
[0029] For example, Figure 1 As shown, the abstract service objects in the abstract service layer can be created independently or reversely generated from the logical service objects in the logical service layer.
[0030] In some feasible embodiments, based on the above solution, the creation method of the logical service object includes: Derived from the abstract service object; Or by creating it separately.
[0031] For example, Figure 1 As shown, the logical service objects of the logical service layer can be derived from the abstract service objects in the abstract service layer, or can be created independently.
[0032] The logical service objects in the logical service layer can be reversed to generate abstract service objects in the abstract service layer.
[0033] In some feasible embodiments, based on the above solution, the creation method of the instance service object includes: Generated by instantiating the logic service object.
[0034] For example, Figure 1 As shown, the instance service object of the instance service layer is generated by instantiating the logical service object of the logical service layer, and one logical service object can form multiple instance service objects.
[0035] The instance service layer software entity can select the corresponding service objects for assembly and deployment according to functional requirements, performance requirements, etc.
[0036] In some feasible embodiments, based on the above scheme, the abstract service object is divided into: base class service template, collection class service template and twin class service template according to different application scenarios; The base service template only defines the basic information of the service and its service operations / service interfaces, and cannot design the processing logic of the service operations; The collection service template only defines the basic information of the service operation / service interface, but does not define the specific service to which the service operation / service interface belongs; The twin service template only defines the basic information of the service template and does not design the service operation / service interface.
[0037] For example, see Figure 2, showing a schematic diagram of a base class service template architecture according to an embodiment of the present application.
[0038] like Figure 2 As shown, the base class service template only defines the basic information of the service and its service operations / service interfaces, and cannot design the processing logic of the service operations. The base class service template can be created directly or generated through reverse abstraction of the logical service object.
[0039] The logical service layer can derive specific logical service objects by inheriting the base class service template.
[0040] For example, see Figure 3 , showing a schematic diagram of a collection service template architecture according to an embodiment of the present application.
[0041] The collection service template only defines the basic information of the service operation / service interface, but does not define the specific service to which the service operation / service interface belongs. It only stores these service operations / service interfaces through the collection service template, and manages and retrieves them through the collection service template. It is also impossible to design the service operation processing logic.
[0042] A collection service template can be created directly, and the service operation / service interface of the collection service template can be generated by reverse abstraction of the service operation / service interface of the logical service object in the logical service layer.
[0043] You can select service operations from the collection service template and put them into the service of the logic service layer to form the service operations of the logic layer service, and perform detailed processing logic design (including specific service dependencies) on them.
[0044] For example, see Figure 4 , showing a schematic diagram of a twin-class service template architecture according to an embodiment of the present application.
[0045] The twin service template only defines the basic information of the service template, does not design the service operation / service interface, and only uses the twin service template as an intermediate bridge (reference).
[0046] The twin service template is generated by reverse engineering the logical service object and completes the twin binding of the two. The only difference between the two is the service name, and the other service operations and service interfaces are the same.
[0047] The service replica of the logical service layer generated by the twin class service template has service operations / service interfaces that are consistent with and synchronized in real time with the logical service objects of the twin's logical service layer, but are dependent on by other services as two independent service objects.
[0048] It can be understood that this technical solution realizes the inheritable design of the logical service objects in the logical service layer through the base class service template designed in the abstract service layer, thereby improving the efficiency of service-oriented system design.
[0049] Through the collection service template designed in the abstract service layer, the evolvable design of the logical service objects in the logical service layer is realized, thereby improving the efficiency of service-oriented system design.
[0050] Through the twin service template designed in the abstract service layer, the reusability design of the logical service objects in the logical service layer is realized, thereby improving the efficiency of service-oriented system design.
[0051] By performing relevant deployment design and configuration on instance service objects at the instance service layer, rapid construction of software entities can be achieved.
[0052] In summary, the service-oriented system layered design architecture provided by the technical solution of this application realizes the capabilities of service reusability, service inheritance, and service evolution through the layered design of the service-oriented system, thereby improving the design efficiency of the service-oriented system.
[0053] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary techniques in the art that are not disclosed in the present application. It should be understood that the present application is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.
Claims
1. A service-oriented system layered design architecture, characterized in that: include: Abstract service layer, logical service layer and instance service layer; The abstract service layer is designed with an abstract service object for defining basic information of the service; The basic information of the service includes the service name, service operation name, service interface name, service signal type name and service operation type; The logic service layer is designed with logic service objects for defining specific service operation logic; The instance service layer is designed with instance service objects for defining specific platform configuration information and deployment relationships.
2. The service-oriented system layered design architecture according to claim 1, characterized in that: The creation method of the abstract service object includes: Obtained by creating it separately; Or it can be obtained by reverse engineering the logic service object.
3. The service-oriented system layered design architecture according to claim 1, characterized in that: The creation method of the logical service object includes: Derived from the abstract service object; Or by creating it separately.
4. The service-oriented system layered design architecture according to claim 1, characterized in that: The creation method of the instance service object includes: Generated by instantiating the logic service object.
5. The service-oriented system layered design architecture according to any one of claims 1 to 4, characterized in that: The abstract service object is divided into: base class service template, collection class service template and twin class service template according to different application scenarios; The base service template only defines the basic information of the service and its service operations / service interfaces, and cannot design the processing logic of the service operations; The collection service template only defines the basic information of the service operation / service interface, but does not define the specific service to which the service operation / service interface belongs; The twin service template only defines the basic information of the service template and does not design the service operation / service interface.
6. The service-oriented system layered design architecture according to claim 5, characterized in that: When the abstract service object is a twin service template, the twin service template is reversely generated from the logical service object, and the service operation and service interface of the twin service template are the same as those of the logical service object.