DL/T 1992-2019 English PDFUS$1199.00 · In stock
Delivery: <= 7 days. True-PDF full-copy in English will be manually translated and delivered via email. DL/T 1992-2019: SOA application technology standard for power enterprises Status: Valid
Basic dataStandard ID: DL/T 1992-2019 (DL/T1992-2019)Description (Translated English): SOA application technology standard for power enterprises Sector / Industry: Electricity & Power Industry Standard (Recommended) Classification of Chinese Standard: F20 Classification of International Standard: 27.100 Word Count Estimation: 52,560 Date of Issue: 2019-06-04 Date of Implementation: 2019-10-01 Regulation (derived from): Natural Resources Department Announcement No. 7 of 2019 Issuing agency(ies): National Energy Administration DL/T 1992-2019: SOA application technology standard for power enterprises---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.SOA application technology standard for power enterprises ICS 27.100 F 20 Record number. 63143-2018 People's Republic of China Electric Power Industry Standard SOA application technical standards for power enterprises 2019-06-04 released 2019-10-01 implementation Issued by National Energy Administration Table of contentsForeword...IIII 1 Scope...3 2 Normative references...3 3 Terms and definitions...3 4 Abbreviations...4 5 SOA Application Technology Framework...4 6 Technical requirements for service realization...17 7 Technical Requirements for Service Interaction...33 Appendix A (informative appendix) Service primitive reference...47 Appendix B (informative appendix) Service interface protocol information...48 Appendix C (informative appendix) Service quality measurement methods...50 Appendix D (informative appendix) Service registration information reference...52ForewordThis standard is formulated to standardize the technical framework of SOA application, technical requirements for service realization, and technical requirements for service interaction. This standard was proposed and interpreted by the Standardization Management Center of the China Electricity Council. This standard is under the jurisdiction of the Power Industry Information Standardization Technical Committee. Drafting organizations of this standard. China Southern Power Grid Co., Ltd., Dingxin Information Technology Co., Ltd., Yunnan Power Grid Co., Ltd. Company, Yunnan Yundian Tongfang Technology Co., Ltd. The main drafters of this standard. Wang Zhiying, Heng Xingchen, Dong Can, Zhang Shijun, Dong Zhaojie, Zhou Xingdong, Wu Bo, Hu Yonghua, Zhang Yi, Zhang Jianwen, Xu Bingyuan, Deng Anming, Fang Junting, Duan Fuliang, Huang Zaiyu, Tai Lulu, Cao Wei, Liu Li. This standard was issued for the first time. The opinions or opinions during the implementation of this standard will be fed back to the Standardization Management Center of China Electricity Council (No. 2 Baiguang Road, Beijing) One, 100761). SOA application technical standards for power enterprises1 ScopeThis standard specifies the SOA application technology framework of Service-Oriented Architecture (SOA), Service realization technical requirements and service interaction technical requirements. This standard applies to SOA-based application system development and information integration construction, SOA project consulting and SOA project supervision of power companies Rationale.2 Normative referencesThe following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this document. For undated references, the latest version (including all amendments) applies to this document. GB/T 29262-2012 Information Technology Service-Oriented Architecture (SOA) Terminology GB/T 29263-2012 Information Technology Service Oriented Architecture (SOA) Application General Technical Requirements GB/T 32427-2015 Information Technology SOA Maturity Model and Evaluation Method GB/T 32428-2015 Information Technology SOA Service Quality Model and Evaluation Specification GB/T 32429-2015 Information technology SOA application life cycle process GB/T 32430-2015 Information Technology SOA Application Service Analysis and Design GB/T 32419.1-2016 Information Technology SOA Technical Implementation Specification Part 1.Service Description GB/T 32419.2-2016 Information Technology SOA Technical Implementation Specification Part 2.Service Registration and Discovery GB/T 32419.3-2016 Information Technology SOA Technical Implementation Specification Part 3.Service Management GB/T 32419.4-2016 Information Technology SOA Technical Implementation Specification Part 4.Publish and Subscribe-based Data Service Interface GB/T 33846.1-2017 Information Technology SOA Support Function Unit Interoperability Part 1.Overall Framework GB/T 33846.2-2017 Information Technology SOA Support Function Unit Interoperability Part 2.Technical Requirements3 Terms and definitionsGB/T 29262-2012, GB/T 32427-2015, GB/T 32419.2-2016 and the following terms and definitions apply In this document. 3.1 Service integration development The behavior of combining multiple services according to a certain pattern to form new services that meet specific business needs. 3.2 Service primitive The actions of service logic processing are described from the perspective of service users. 3.3 Enterprise architecture It is commonly used by various large-scale organizations in the world to promote the integration of business and information, control the overall situation in rapid change, and optimize the investment structure. A set of effective methods to reduce the cost of change and control the risk of change. It includes corporate strategy, organization, functions, business processes, IT The complete and integrated description of system, data, network deployment, etc. reflects the status of enterprise business and reflects the mapping relationship between business and IT, Be able to clarify the supporting relationship of various IT facilities to the business. 3.4 Domain-driven design A software development method that realizes complex requirements by closely linking software implementation with the evolution of core business concepts. 3.5 Service instance An assembly that can provide external services. 3.6 Service interactive communication Provide functional units of access, load balancing, transmission, routing and conversion between the service requester and the service consumer, in actual interaction In the process, the implementation of service interaction communication includes enterprise service bus, service gateway, etc. 3.7 Identity synchronization keeps the identity data of the same entity in different information systems in a consistent relative relationship. 3.8 Integration The process of bringing together some isolated information or elements in a certain way, establishing connections, and forming an organic whole. 3.9 API gateway Provide API hosting services, covering the full life cycle management of API publishing, management, operation and maintenance, and sales. Assisting users is simple, fast, Low-cost, low-risk realization of micro-service aggregation, front-end separation, system integration, open functions and data to partners and developers. Note. For the description of API abbreviations, see 4 abbreviations of this standard.4 Abbreviations5 SOA Application Technology Framework5.1 Conceptual Model of SOA Application See GB/T 29263-2012 Chapter 4 SOA Application Conceptual Model. 5.2 SOA Application Technology Reference Model 5.2.1 Overview The SOA application technology reference model is suitable for the construction, operation and management process of SOA applications. See 4 in GB/T 29263-2012 in this section The SOA application technology reference model, based on the original reference model, refines the technical requirements of each solid line in the SOA application technology reference model begging. The SOA application technology reference model mainly includes 9 parts. a) IT infrastructure is an existing operating environment that carries SOA applications and a basic environment that can be configured and expanded in the future; b) SOA resources are IT resources such as application systems, data and existing services required to realize SOA applications. These resources exist in In enterprises, government departments and other organizations, as the initial source of services in the construction of SOA applications; based on SOA resources, Services can be formed through processes such as encapsulation and extraction. For specific requirements, see 6 Technical Requirements for Service Implementation in this standard; c) SOA supporting technologies and services are the general term for basic technical capabilities and basic technical services supporting SOA applications; d) Business public services are a series of industry/domain-oriented applications, reusable, and certain business functions. Can interact with each other based on the functions and capabilities provided by SOA supporting technologies and services, and thereby achieve richer business logic For technical requirements related to service interaction, see 7 Service Interaction Technical Requirements of this standard; e) The power industry application is user-oriented, based on the power industry’s “generation, transmission, transformation, distribution, and use” and other links and specific business fields. IT systems required by the domain; f) User is the general term for people, systems, equipment and other services that use SOA applications; g) Quality refers to the degree to which SOA applications meet user needs or expectations; h) Security is the general term for mechanisms and strategies to ensure the safe operation of SOA applications; i) Governance is the management and control strategy and mechanism formulated for SOA applications, covering the entire life cycle of SOA applications. 5.2.2 Supporting technology and service requirements for SOA applications 5.2.2.1 Service description capability requirements The service description capability should meet the following requirements. a) Provide standard information models and access interfaces to describe the relevant attributes of services and resources; b) Meet the specific technical standards of the relevant service descriptions. For specific requirements, see 6.1 Service Descriptions of this standard. 5.2.2.2 Service registration and discovery capability requirements Service registration and discovery capabilities should meet the following requirements. a) Provide service registration functions and access interfaces to register, retrieve and discover services and resources; b) Provide an active release interface for service additions and changes, so that users can perceive and discover service changes in a timely manner; c) Comply with the specific technical standards related to service registration and discovery. For specific requirements, see 7.2.1 Service Registration and Discovery of this standard. 5.2.2.3 Service development capability requirements Service development capabilities should meet the following requirements. a) The environment for design, development, configuration, debugging, testing and operation required for building new services shall be provided; b) Service-based packaging of existing application systems or data resources should be supported; c) Relevant tools or environments should be provided to test service design compliance, service coupling, service autonomy, etc.; d) Comply with the specific technical standards for related service development. See 6.5 Service Development of this standard for specific requirements. 5.2.2.4 Service preparation capability requirements The service preparation capability should meet the following requirements. a) Invoke a series of services in a logical sequence to form a larger granular service; b) Provide a runtime container environment for the prepared service; c) Comply with the specific technical standards for the preparation of related services. 5.2.2.5 Service orchestration capability requirements The service orchestration capability should meet the following requirements. a) Based on several other services, build new services that meet the business process through service process modeling and orchestration; b) Provide a process execution engine to provide interpretation, execution, control, and management functions for the deployed business process scripts; c) Comply with the specific technical standards for related service scheduling. For specific requirements, see 7.2.2 Service scheduling of this standard. 5.2.2.6 Service management capability requirements Service management capabilities should meet the following requirements. a) Provide information on service design, service development, service testing, service deployment, service release, service use, service change, service withdrawal For the management measures and processes of the service and other processes to realize the full life cycle management of the service, see 5.3 Service life cycle process of this standard; b) Real-time monitoring, warning and other related management operations of the service status; c) Compliance with specific technical standards for related service management. 5.2.2.7 Service interaction communication capability requirements The service interaction communication capability shall meet the following requirements. a) Provide service access, routing, load balancing, message conversion, transmission and other functions; b) Have the ability to integrate with service management; c) Provide a mechanism and quality assurance for interaction between services; d) Comply with the specific technical standards of relevant service interactive communication. For specific requirements, see 7.1.4 Service Interactive Communication Unit of this standard. 5.2.2.8 Information service requirements Information services should meet the following requirements. a) Provide information collection, cataloging, publishing and retrieval functions; b) Compliance with specific technical standards of relevant information services. 5.2.2.9 Show service requirements The display service shall meet the following requirements. a) Provide a complete set of display functions that support multi-channel human-computer interaction; b) Comply with the specific technical standards of relevant display services. 5.2.2.10 Identity management service requirements Identity management services should meet the following requirements. a) Provide a set of extensible management functions of organization, personnel, roles, certification, etc.; b) Meet the specific technical standards of relevant user management services. 5.2.2.11 Authorized service requirements The authorization service shall meet the following requirements. a) Provide identity authentication and access control functions based on identity management services; b) Comply with the specific technical standards of relevant authorized services. 5.2.2.12 Business public service requirements for SOA applications In the process of realizing SOA application systems, it is necessary to gradually accumulate and form the characteristics of the power industry that can support SOA application development Characteristic business public services. Business public services shall meet the following requirements. a) Satisfy the various elements of the service, and can achieve certain power industry business functions; b) Strong reusability within a certain range; c) Conform to the standards or regulations of the electric power industry and the field. 5.2.3 SOA application quality requirements 5.2.3.1 General requirements In addition to functional requirements, SOA applications also need to meet the following quality requirements. a) Reliability; b) ease of use; c) efficiency; d) Maintainability; e) Portability; f) Platform independence. 5.2.3.2 Service quality requirements The quality of service should at least meet the following requirements. a) Functional correctness; b) Reasonable service granularity; c) Loose coupling; d) Reusability; e) Scalability; f) Interoperability; g) Autonomy; h) Statelessness; i) Independence of affairs. 5.3 Service life cycle process 5.3.1 Overview This section gives the requirements of the service life cycle process in SOA applications, and defines the purpose and output of the process, as well as the completion process Required activities. The service life cycle process is described in four process groups. analysis and design process, creation process, assembly process, and operation and maintenance process. This section adds service planning process, service use process, service life cycle process in GB/T 32429-2015 5 service life cycle process. The service change process and the service orchestration process include a total of 14 processes, as shown in Figure 2. 5.3.2 Service analysis and design process 5.3.2.1 Service planning process 5.3.2.1.1 Purpose Service planning is to undertake the top-level design and planning of the organization, from an overall perspective, facing the organization's integrity and forward-looking information needs, The overall planning and optimization design of the organization’s service resources form the organization’s service resource library plan, which is used as service design and development The main basis for the issue. 5.3.2.1.2 Output The output of the service planning process is service resource library planning, including service domains, service lists, and service conceptual design. 5.3.2.1.3 Activities and tasks The service planning process includes five activities. business decomposition, application decomposition, data decomposition, service identification, and service organization. See for specific requirements 6.2 Service planning of this standard. 5.3.2.2 Service analysis process 5.3.2.2.1 Purpose Service analysis is based on the overall requirements of SOA applications, taking the service domain and service list planning of the service resource library as a reference basis, and comprehensive The process of gradually discovering and screening services in multiple dimensions using multiple methods and means. 5.3.2.2.2 Output The output results of the service analysis process include. a) Candidate service list. including service name, function description, service source, service consumer, service provider, service process information Information and other service demand information; b) Consistency and traceability correspondence between service requirements and business requirements; c) Analysis results of correctness and testability of service requirements. 5.3.2.2.3 Activities and tasks The service analysis process includes target analysis, domain analysis, process analysis, data analysis, business dimension service analysis, system dimension service analysis, Seven activities including service identification and screening. See 6.3 Service Analysis of this standard for specific requirements. 5.3.2.3 Service design process 5.3.2.3.1 Purpose The service design is based on the service conceptual design of the service resource library as a reference to classify the services obtained in the service analysis process, A series of activities such as definition (statute) and management. 5.3.2.3.2 Output The output of the service design process includes. a) Service classification; b) Service interface definition list; c) Detailed protocol of service interface; d) Service realization matrix; e) Design review opinions; f) Consistency and traceability correspondence between service design and service requirements. 5.3.2.3.3 Activities and tasks The service design process includes service classification, service definition, service interface design, service realization method decision, service design review, etc. 5 Events. For specific requirements, see 6.4 Service Design of this standard. 5.3.3 Service creation process 5.3.3.1 Service development process 5.3.3.1.1 Purpose Service development is the process of turning a defined service interface detailed protocol into a deployable service through technical development means. 5.3.3.1.2 Output The output of the service development process includes. a) Deployable service package; b) Service description doc...... |
