CN109522003B - Public subassembly is extended to electric power business system - Google Patents
Public subassembly is extended to electric power business system Download PDFInfo
- Publication number
- CN109522003B CN109522003B CN201811276067.2A CN201811276067A CN109522003B CN 109522003 B CN109522003 B CN 109522003B CN 201811276067 A CN201811276067 A CN 201811276067A CN 109522003 B CN109522003 B CN 109522003B
- Authority
- CN
- China
- Prior art keywords
- component
- service
- components
- service end
- business
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000011161 development Methods 0.000 claims abstract description 39
- 238000010276 construction Methods 0.000 claims abstract description 25
- 238000005538 encapsulation Methods 0.000 claims abstract description 8
- 238000009472 formulation Methods 0.000 claims abstract description 4
- 239000000203 mixture Substances 0.000 claims abstract description 4
- 238000012544 monitoring process Methods 0.000 claims abstract description 4
- 230000008520 organization Effects 0.000 claims abstract description 4
- 230000018109 developmental process Effects 0.000 claims description 37
- 238000000034 method Methods 0.000 claims description 10
- 230000008569 process Effects 0.000 claims description 10
- 230000033772 system development Effects 0.000 claims description 8
- 238000004891 communication Methods 0.000 claims description 3
- 238000013461 design Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 claims description 3
- 230000007246 mechanism Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005457 optimization Methods 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 230000009897 systematic effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/06—Energy or water supply
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Marketing (AREA)
- Tourism & Hospitality (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Public Health (AREA)
- Water Supply & Treatment (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides an electric power business system expansion public component, wherein the construction of the expansion public component comprises three parts, namely code specification formulation, unified framework type selection and development environment and a release platform; after the frame type selection and development environment are determined, developing and determining a basic component, a technical component, a business component and a typical page; the basic components comprise transaction control, unified authority control, unified authentication and parameter configuration, exception handling and log output and system running condition monitoring; the technical components comprise a uniform page style, rich client side expansion controls, uniform check sum alarm, Excel/word export, service encapsulation, a chart and a report; the business components include role selection, organization structure tree, role selection tree, user tree/people tree, attachment upload and download, and workflow encapsulation. The invention aims to build a set of practical, easy-to-use and efficient public components and aims to solve the common problem in the construction of the informatization system.
Description
Technical Field
The invention belongs to the technical field of electric power informatization, and particularly relates to an electric power business system expansion public component.
Background
With the rapid development of global information-oriented industry, the information-oriented construction projects developed by the power system are steadily increasing, and more business departments participate in the information-oriented construction. Under the wave of rapid development of the information system, the deficiency of the infrastructure of the information system is gradually highlighted. The quality of system construction is not uniform in informatization systems built by different development teams and different suppliers, and for implementation modes of different business requirements, the eight-door system has the defects that the center of gravity is too much in the construction process, the business requirements are realized, and systematic research on rigid indexes such as system safety is lacked. Under the business background, for some common problems in the information system construction process, including the improvement of the reliability, expandability, safety and robustness of the system and the requirements of standardization and standardization in the information system construction process, the optimization and refinement of the implementation mode under the existing business requirement scene develop systematic and targeted research and construction, and further form a set of effective, easy-to-popularize and easy-to-manage and distribute information system construction framework, which has become an urgent requirement.
Disclosure of Invention
The invention aims to construct a set of practical, easy-to-use and efficient public components, aims to solve the common problem in the construction of an information system, is popularized to subsequent development work, and completes system optimization work in the project construction process.
The invention particularly relates to an electric power business system expansion public component, wherein the construction of the expansion public component comprises three major parts, namely code specification formulation, unified framework type selection and development environment and a release platform; the coding specification is formulated into a universal coding specification, so that the information system is standardized and standardized; the unified framework type selection and development environment is a framework which is most suitable for the informatization construction of the power service system, the security, reliability and expansibility of the service system are guaranteed in the development framework, the development environment is defined according to the guarantee, the difference among different projects is unified, and the technical risk is reduced to the maximum extent; the publishing platform is used for displaying various components in a centralized manner, and a business system can visually know the design idea of the public component complete code frame, the use mode of each component and the notice information.
After the frame type selection and development environment are determined, developing and determining a basic component, a technical component, a business component and a typical page; the basic components comprise transaction control, unified authority control, unified authentication and parameter configuration, exception handling and log output and system running condition monitoring; the basic assembly aims at improving safety, reliability and expansibility, and a unified system construction framework is built; the technical components comprise a uniform page style, rich client side expansion controls, a uniform check sum alarm, an Excel/word output, service encapsulation, a chart and a report; the technical component is based on a rich client technology, is combined with the used components of the existing power service system, and carries out customized expansion development on the functions of the components, so that the power service system has higher practical significance and a more convenient use mode, is directly called by the power service system, and does not need to pay attention to the implementation of a bottom layer; the service components comprise role selection, group organization structure tree, role selection tree, user tree/personnel tree, accessory uploading and downloading and workflow encapsulation; the service component is combined with common power service, a universal component is customized, and a power service system can be directly used without repeated development; the typical page provides standard implementation examples and templates for common display modes and controls, and is used for reference of a power business system and unified implementation modes; the typical pages include lists, tree + master-slave lists, tree + list + details, chart controls, report interfaces, and component use cases.
Further, the components of the client maintain the consistency of the versions and the real-time performance of updating in an online reference mode, and the specific mechanism comprises: a user respectively initiates requests for different functions in a service system A and a service system B in a browser mode, but both the two functions use the same client component C; the service system responds to the user request, needs to load the client component C and initiates a request to the multi-node routing and caching equipment in a direct reference mode; the multi-node routing and caching device preferentially accesses local cached resources, and directly returns a cache object to the user equipment if the client component C is cached; if the multi-node routing and caching equipment does not locally cache the client component C, the client component C is obtained through the uniform resource storage equipment and then returned to the user.
Furthermore, when the client component C is used at the same time, different functions in different service systems acquire a uniform client component from the same resource address, so that the consistency of versions of the client component is ensured; and uniformly updating and managing the public resources on the resource storage equipment to meet the real-time requirement of updating all service system components.
Furthermore, because the service end component can not realize the quote of the online resources like the client end component, the process of compiling the service system source code by the development environment is used as an entry point, and the distribution of the service end component is realized; due to the complex characteristics of the service end components, the management of the mutual dependency relationship of the service end components is separately introduced, so that the availability and the stability of the service end components are improved.
Further, the distribution mode of the service-side component includes: in a development environment, a service end component used in the business system is appointed, and in the system compiling process, a request is initiated to a dependency relationship management device according to the dependency condition of the service end component; the dependency relationship management device analyzes the dependency relationship according to a specified service end component in the development environment, when the service system needs to use the service end component A and the service end component A has the dependency relationship with the service end component B, C, D, the service end components are required to be provided at the same time to normally operate, and a request is sent to the storage device of the service end component according to a result obtained by analyzing the dependency relationship; and the server end component storage device returns a uniform component to the business system development environment according to the requested server end component, so that the business system development environment can complete the construction of related modules of the business system.
Further, the server side component is managed in a centralized manner in the storage device of the server side component, so that the timeliness of updating the component is ensured; and when the business system is compiled in a development environment, the latest component is acquired, and the synchronization of the component versions among the business systems is ensured.
Further, necessary components and general modules of system operation are extracted to obtain general modules and components, and the general modules and the components are sorted and split according to business requirements to obtain a plurality of independent functional modules; the independent functional modules depend on the universal modules and the components, and have communication and dependency relationship with each other; the independent function module is capable of local updates.
Drawings
FIG. 1 is a block diagram of a construction module of an extended common component of a power business system of the present invention;
FIG. 2 is a schematic diagram illustrating an embodiment of a client component according to the present invention;
FIG. 3 is a schematic diagram of a distribution mode of the service-side component according to the present invention.
Detailed Description
The following describes in detail a specific embodiment of an electric power business system expansion common component according to the present invention with reference to the accompanying drawings.
As shown in fig. 1, the construction of the power business system development common component of the present invention includes three major parts, i.e., the formulation of coding specifications, the unified framework model selection and development environment, and the release platform; the coding specification is formulated into a universal coding specification, so that the information system is standardized and standardized; the unified framework type selection and development environment is a framework which is most suitable for the informatization construction of the power service system, the security, reliability and expansibility of the service system are guaranteed in the development framework, the development environment is defined according to the guarantee, the difference among different projects is unified, and the technical risk is reduced to the maximum extent; the publishing platform is used for displaying various components in a centralized manner, and a business system can visually know the design idea of the public component complete code frame, the use mode of each component and the notice information.
After the frame type selection and development environment are determined, developing and determining a basic component, a technical component, a business component and a typical page; the basic components comprise transaction control, unified authority control, unified authentication and parameter configuration, exception handling and log output and system running condition monitoring; the basic assembly aims at improving safety, reliability and expansibility, and a unified system construction framework is built; the technical components comprise a uniform page style, rich client side expansion controls, a uniform check sum alarm, an Excel/word output, service encapsulation, a chart and a report; the technical component is based on a rich client technology, is combined with the used components of the existing power service system, and carries out customized expansion development on the functions of the components, so that the power service system has higher practical significance and a more convenient use mode, is directly called by the power service system, and does not need to pay attention to the implementation of a bottom layer; the service components comprise role selection, group organization structure tree, role selection tree, user tree/personnel tree, accessory uploading and downloading and workflow encapsulation; the service component is combined with common power service, a universal component is customized, and a power service system can be directly used without repeated development; the typical page provides standard implementation examples and templates for common display modes and controls, and is used for reference of a power business system and unified implementation modes; the typical pages include lists, tree + master-slave lists, tree + list + details, chart controls, report interfaces, and component use cases.
As shown in fig. 2, the components of the client maintain version consistency and update instantaneity by using an online reference manner, and the specific mechanism includes: a user respectively initiates requests for different functions in a service system A and a service system B in a browser mode, but both the two functions use the same client component C; the service system responds to the user request, needs to load the client component C and initiates a request to the multi-node routing and caching equipment in a direct reference mode; the multi-node routing and caching device preferentially accesses local cached resources, and directly returns a cache object to the user equipment if the client component C is cached; if the multi-node routing and caching equipment does not locally cache the client component C, the client component C is obtained through the uniform resource storage equipment and then returned to the user. Different functions in different service systems acquire uniform client components from the same resource address when the client component C is used at the same time, so that the consistency of versions of the client components is ensured; and uniformly updating and managing the public resources on the resource storage equipment to meet the real-time requirement of updating all service system components.
As shown in fig. 3, since the service end component cannot implement the reference of online resources like the client end component, the process of compiling the service system source code by the development environment is used as an entry point, so as to implement the distribution of the service end component; due to the complex characteristics of the service end components, the management of the mutual dependency relationship of the service end components is separately introduced, so that the availability and the stability of the service end components are improved. The distribution mode of the service end component comprises the following steps: in a development environment, a service end component used in the business system is appointed, and in the system compiling process, a request is initiated to a dependency relationship management device according to the dependency condition of the service end component; the dependency relationship management device analyzes the dependency relationship according to a specified service end component in the development environment, when the service system needs to use the service end component A and the service end component A has the dependency relationship with the service end component B, C, D, the service end components are required to be provided at the same time to normally operate, and a request is sent to the storage device of the service end component according to a result obtained by analyzing the dependency relationship; and the server end component storage device returns a uniform component to the business system development environment according to the requested server end component, so that the business system development environment can complete the construction of related modules of the business system. The server side component is managed in a centralized manner in the storage equipment of the server side component, so that the timeliness of updating the component is ensured; and when the business system is compiled in a development environment, the latest component is acquired, and the synchronization of the component versions among the business systems is ensured.
Extracting necessary components and general modules of system operation to obtain general modules and components, and sorting and splitting the general modules and the components according to business requirements to obtain a plurality of independent functional modules; the independent functional modules depend on the universal modules and the components, and have communication and dependency relationship with each other; the independent function module is capable of local updates.
Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of the present invention and not for limiting the same. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (7)
1. An electric power business system expansion public component is characterized in that the construction of the expansion public component comprises three major parts, namely code specification formulation, unified framework type selection and development environment and a release platform; the coding specification is formulated into a universal coding specification, so that the information system is standardized and standardized; the unified framework type selection and development environment is a framework which is most suitable for the informatization construction of the power service system, the security, reliability and expansibility of the service system are guaranteed in the development framework, the development environment is defined according to the guarantee, the difference among different projects is unified, and the technical risk is reduced to the maximum extent; the publishing platform is used for displaying various components in a centralized manner, and a business system can visually know the design idea of a public component complete code frame, the use mode of each component and the notice information;
after the frame type selection and development environment are determined, developing and determining a basic component, a technical component, a business component and a typical page; the basic components comprise transaction control, unified authority control, unified authentication and parameter configuration, exception handling and log output and system running condition monitoring; the basic assembly aims at improving safety, reliability and expansibility, and a unified system construction framework is built; the technical components comprise a uniform page style, rich client side expansion controls, a uniform check sum alarm, an Excel/word output, service encapsulation, a chart and a report; the technical component is based on a rich client technology, is combined with the used components of the existing power service system, and carries out customized expansion development on the functions of the components, so that the power service system has higher practical significance and a more convenient use mode, is directly called by the power service system, and does not need to pay attention to the implementation of a bottom layer; the service components comprise role selection, group organization structure tree, role selection tree, user tree/personnel tree, accessory uploading and downloading and workflow encapsulation; the service component is combined with common power service, a universal component is customized, and a power service system can be directly used without repeated development; the typical page provides standard implementation examples and templates for common display modes and controls, and is used for reference of a power business system and unified implementation modes; the typical pages include lists, tree + master-slave lists, tree + list + details, chart controls, report interfaces, and component use cases.
2. The electric power business system development common component of claim 1, wherein the component of the client maintains version consistency and update real-time performance in an online reference manner, and the specific mechanism comprises: a user respectively initiates requests for different functions in a service system A and a service system B in a browser mode, but both the two functions use the same client component C; the service system responds to the user request, needs to load the client component C and initiates a request to the multi-node routing and caching equipment in a direct reference mode; the multi-node routing and caching device preferentially accesses local cached resources, and directly returns a cache object to the user equipment if the client component C is cached; if the multi-node routing and caching equipment does not locally cache the client component C, the client component C is obtained through the uniform resource storage equipment and then returned to the user.
3. The electric power business system expansion common component of claim 2, wherein different functions in different business systems obtain a unified client component from the same resource address when the client component C is used simultaneously, so that the consistency of versions of the client component is ensured; and uniformly updating and managing the public resources on the resource storage equipment to meet the real-time requirement of updating all service system components.
4. The electric power business system expansion common component as claimed in claim 1, wherein the service end component is distributed by using the process of compiling business system source codes by the development environment as an entry point because the service end component cannot realize online resource reference like the client end component; due to the complex characteristics of the service end components, the management of the mutual dependency relationship of the service end components is separately introduced, so that the availability and the stability of the service end components are improved.
5. The electric power business system expansion common component of claim 4, wherein the distribution mode of the service end component comprises: in a development environment, a service end component used in the business system is appointed, and in the system compiling process, a request is initiated to a dependency relationship management device according to the dependency condition of the service end component; the dependency relationship management device analyzes the dependency relationship according to a specified service end component in the development environment, when the service system needs to use the service end component A and the service end component A has the dependency relationship with the service end component B, C, D, the service end components are required to be provided at the same time to normally operate, and a request is sent to the storage device of the service end component according to a result obtained by analyzing the dependency relationship; and the server end component storage device returns a uniform component to the business system development environment according to the requested server end component, so that the business system development environment can complete the construction of related modules of the business system.
6. The electric power business system expansion common component of claim 5, wherein the service end component is managed centrally in a storage device of the service end component, so as to ensure timeliness of component updating; and when the business system is compiled in a development environment, the latest component is acquired, and the synchronization of the component versions among the business systems is ensured.
7. The electric power business system expansion common component according to claim 1, wherein necessary components and common modules for system operation are extracted to obtain common modules and components, and the common modules and the components are arranged and split according to business requirements to obtain a plurality of independent functional modules; the independent functional modules depend on the universal modules and the components, and have communication and dependency relationship with each other; the independent function module is capable of local updates.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811276067.2A CN109522003B (en) | 2018-10-30 | 2018-10-30 | Public subassembly is extended to electric power business system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811276067.2A CN109522003B (en) | 2018-10-30 | 2018-10-30 | Public subassembly is extended to electric power business system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109522003A CN109522003A (en) | 2019-03-26 |
| CN109522003B true CN109522003B (en) | 2021-07-09 |
Family
ID=65774046
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811276067.2A Active CN109522003B (en) | 2018-10-30 | 2018-10-30 | Public subassembly is extended to electric power business system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109522003B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113126979B (en) * | 2021-04-16 | 2022-03-25 | 多点(深圳)数字科技有限公司 | Visual business building system capable of achieving secondary programming by separating from server |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7693897B2 (en) * | 2005-08-26 | 2010-04-06 | Harris Corporation | System, program product, and methods to enhance media content management |
| CN102324074A (en) * | 2011-10-28 | 2012-01-18 | 山东城通科技有限公司 | Informatization application cluster platform of small and medium enterprises |
| CN104702568B (en) * | 2013-12-05 | 2017-11-21 | 浙江大华系统工程有限公司 | A kind of Business Management Platform |
| US10360000B2 (en) * | 2014-06-02 | 2019-07-23 | Blackwatch International | Generic template node for developing and deploying model software packages made up of interconnected working nodes |
| CN105278373A (en) * | 2015-10-16 | 2016-01-27 | 中国南方电网有限责任公司电网技术研究中心 | Substation integrated information processing system realizing method |
| CN105956830A (en) * | 2016-05-11 | 2016-09-21 | 中煤电气有限公司 | J2EE framework based enterprise-level visualization application development platform |
| CN106846226A (en) * | 2017-01-19 | 2017-06-13 | 湖北省基础地理信息中心（湖北省北斗卫星导航应用技术研究院） | A kind of space time information assembling management system |
| CN107491858A (en) * | 2017-07-05 | 2017-12-19 | 北京科东电力控制系统有限责任公司 | A kind of electric power transaction platform based on micro services application architecture |
| CN107844293B (en) * | 2017-11-01 | 2018-09-14 | 广州供电局有限公司 | A kind of implementation method in electric power enterprise mobile application common component library |
| CN108229825A (en) * | 2018-01-04 | 2018-06-29 | 焦点科技股份有限公司 | A kind of BI management systems based on development process closed loop |
-
2018
- 2018-10-30 CN CN201811276067.2A patent/CN109522003B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109522003A (en) | 2019-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107370786B (en) | General information management system based on micro-service architecture | |
| CN104160381A (en) | Managing tenant-specific data sets in a multi-tenant environment | |
| JP2014194813A (en) | System, method and graphical user interface for workflow generation, deployment and/or execution | |
| CN111274001A (en) | Micro-service management platform | |
| CN105283847A (en) | Local store data versioning | |
| KR101086620B1 (en) | Smart office system and server for managing the sames and method for managing the sames | |
| CN111178849A (en) | Linear process engine implementation method, device, equipment and storage medium | |
| CN111221871A (en) | Real-time query task issuing method, platform, equipment and storage medium | |
| CN111143391A (en) | Data sharing exchange method and system | |
| CN102567334A (en) | Office automation system based on heterogeneous data | |
| CN112947992A (en) | Method and device for managing code version | |
| Boujbel et al. | Muscadel: A deployment dsl based on a multiscale characterization framework | |
| CN109522003B (en) | Public subassembly is extended to electric power business system | |
| Russell et al. | The vine toolkit: A java framework for developing grid applications | |
| CN113190517B (en) | Data integration method and device, electronic equipment and computer readable medium | |
| CN113014618A (en) | Message processing method and system and electronic equipment | |
| CN111711695A (en) | Distributed equipment management system based on cloud platform | |
| US8984476B2 (en) | Target application creation | |
| CN108737485A (en) | For the method and system of the operation of Internet of Things resource | |
| KR20130137878A (en) | Method for total managing open-source systems and total management server thereof | |
| CN105429805A (en) | Distributed network management system and information processing method | |
| CN114979279A (en) | Micro-service module scheduling method for data request | |
| CN114138758A (en) | Data cleaning and merging method and device based on multi-source system and readable medium | |
| CN113253991A (en) | Task visualization processing method and device, electronic equipment and storage medium | |
| CN107707596A (en) | Flow accumulation cloud service center system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Shen Hua Inventor after: Zhang Wei Inventor after: Ji Yu Inventor after: Xu Xiaodie Inventor before: Zhang Wei Inventor before: Ji Yu Inventor before: Xu Xiaodie |