CN107577467A - A kind of java implementation methods of TOSCA specifications - Google Patents
A kind of java implementation methods of TOSCA specifications Download PDFInfo
- Publication number
- CN107577467A CN107577467A CN201710985478.8A CN201710985478A CN107577467A CN 107577467 A CN107577467 A CN 107577467A CN 201710985478 A CN201710985478 A CN 201710985478A CN 107577467 A CN107577467 A CN 107577467A
- Authority
- CN
- China
- Prior art keywords
- modules
- topology
- node
- type
- event
- 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.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention provides a kind of java implementation methods of TOSCA specifications, reads the Yaml files for customization type；File stream is parsed based on snakeyaml；The file after parsing is decomposed according to system event type；The file after decomposing is read, the file after decomposition is stored in global object topology.Java is set to realize TOSCA specifications, the data structure of support includes：Data object, array of data and data scale.A kind of document for meeting TOSCA specifications is parsed by way of snakeyaml parsing yaml files, wherein data type can be with self-defined, and conveniently extends.The analytic method of the file of TOSCA specifications can be met by realization.Realize based on java use to realize TOSCA Layout Standards.
Description
Technical field
The present invention relates to data processing field, more particularly to a kind of java implementation methods of TOSCA specifications.
Background technology
Across the isomerous environment establishment of IT personnel is supported, safeguard and is multiplexed architecture, middleware and application program using layout
Template, either automate an operation flow or whole data center.These layout templates are to provide application program topology
A kind of mode, efficiency is higher than manual script compilation, while provides structure block for standardization flow, also faster to service
Deliver to provide and create repeatability.Backstage, layout solution should also with it is existing exploitation and service management work adfluxion into.This
A little solutions should support plug and play to integrate by application programming interface (API).
TOSCA (the topological layout standard of cloud application, Topology Orchestration Specification for
Cloud Applications) it is to organize (XML maker) to manage by OASIS.From the track record of TOSCA programming facilities
Seen with development speed, developed quite ripe, many tissues are bet and promote its success.While in business and open
Attracted eyeball in source item, won such as Cloudify, IBM Cloud Orchestrator and OpenStack Heat
The heart of a young woman.Also adopted simultaneously by telecommunication supplier leader's Alcatel-Lucent, Huawei and Cisco.But there is presently no based on
TOSCA Layout Standards are realized in java use.
The content of the invention
In order to overcome above-mentioned deficiency of the prior art, the present invention provides a kind of java implementation methods of TOSCA specifications, side
Method includes：Read the Yaml files for customization type；File stream is parsed based on snakeyaml；According to system thing
Part type is decomposed the file after parsing；The file after decomposing is read, the file after decomposition is stored in global object
In topology.
Preferably, step is parsed to file stream based on snakeyaml and also included：
The file stream for obtaining file stream starts event and file stream End Event, and is solved since event file stream
Analysis, judges event type one by one, until file stream End Event.
Preferably, judge that event type also includes one by one：
Parse the key assignments of each event；
The key assignments of each event includes：Tosca_definitions_version modules for event version,
Description modules be event in character types, datatype_definitions modules, node_types modules,
Topology_template modules are object type.
Preferably, respectively to datatype_definitions modules, node_types modules, topology_
Template modules are parsed；
Datatype_definitions modules, node_types modules and topology_template moulds are parsed respectively
Block is inherited from that type, shows inheritance；
Datatype_definitions modules, node_types modules, topology_template modules are belonged to
Property description, attribute description, which includes, shows type and default field；
Datatype_definitions modules, node_types modules and topology_template have been read respectively
After module attribute and default field, by its datatype_definitions module, node_types modules, topology_
Template modules are put into datatypes lists to be used for other attributes.
Preferably, datatype_definitions modules, node_types modules, topology_ are parsed respectively
The field of template modules；
Node_type modules preserve customized node type and extend use for node_template modules, and provide
The field type of the node_type module definitions defined is used only in node_template modules.That is node_type modules are
Node definition, node_template modules are node instance；
Node_template modules include properties, attributes, interfaces and requirements tetra-
Individual attribute；Wherein properties is object properties；Attributes is the mark of storage, is 32 uuid；interfaces
Realized comprising implements scripts, dependencies is relied on and three elements of inputs input parameters；
Node_type modules and node_template modules after the completion of grammer format analysis by being stored in node_types
In register and node_templates registers, and uniformly it is put into global object topology, whole tosca specifications parsing
Complete.
Preferably, step includes before reading the Yaml files for customization type：
The data model of TOSCA specifications is established, data model includes topology_template modules, node_
Templates modules, attributes modules, artifacts modules, interfaces modules, requirements modules；
Topology_template modules are used for describing the general name of whole topological structure, the description of node_template modules
The details of node template, the details of node template include attribute attributes, external file attifacts, connect
Mouth interfaces, and rely on requirements.
Preferably, step also includes before reading the Yaml files for customization type：
The Yaml files of customization type include：What system provided, for defining the normative_ of data type
The topology.yaml of oneself applied topology of types.yaml and the description of user's input；
First parse normative_types.yaml and preserve data type, and data type is stored in global object,
For being used during parsing topology.yaml files.
Preferably, the file stream of step acquisition file stream starts event and file stream End Event, and opening from file stream
Beginning event starts to parse, and judges event type one by one, until file stream End Event also includes：
The beginning event of document and the End Event of document in file stream event are obtained, since document event
Parsing, until the End Event of document；
The beginning and end event of object type data in resolution file stream, event is opened since object type data
Begin to parse, until the End Event of object type data；
The beginning and end event of character types data in resolution file stream, event is opened since character types data
Begin to parse, until the End Event of character types data；
The beginning and end event of list type data in resolution file stream, event is opened since list type data
Begin to parse, until the End Event of list type data.
Preferably, step reads the file after decomposing, and the file after decomposition is stored in into it in global object topology
Also include afterwards：
When file after decomposition is DATA_type types, the fundamental type data defined in file are read, will be fixed in file
The fundamental type data of justice are preserved into global object topology；
When file after decomposition is node_type categorical datas, preserve into global object topology.
Preferably, step reads the file after decomposing, and the file after decomposition is stored in into it in global object topology
Also include afterwards：
Read the topology.yaml files of user；
The topology.yaml files of user are decomposed according to the event type of user；
User's topology.yaml files after decomposing are read respectively, and user's topology.yaml files include：node_
Template modules, topology.yaml fileinfos, topology.yaml FileVersions and topology.yaml files
Title；
User's topology.yaml files after decomposition are preserved into global object topology.
As can be seen from the above technical solutions, the present invention has advantages below：
By the java implementation methods of TOSCA specifications, java is set to realize TOSCA specifications, the data structure of support includes：Number
According to object, array of data and data scale.Met by way of snakeyaml parsing yaml files to parse one kind
The document of TOSCA specifications, wherein data type can be with self-defined, and conveniently extend.TOSCA specifications can be met by realizing
The analytic method of file.Realize based on java use to realize TOSCA Layout Standards.
Brief description of the drawings
In order to illustrate more clearly of technical scheme, the required accompanying drawing used in description will be made below simple
Ground introduction, it should be apparent that, drawings in the following description are only some embodiments of the present invention, for ordinary skill
For personnel, on the premise of not paying creative work, other accompanying drawings can also be obtained according to these accompanying drawings.
Fig. 1 is the java implementation method flow charts of TOSCA specifications；
Fig. 2 is the java implementation method embodiment flow charts of TOSCA specifications.
Embodiment
To enable goal of the invention, feature, the advantage of the present invention more obvious and understandable, will use below specific
Embodiment and accompanying drawing, the technical scheme protected to the present invention are clearly and completely described, it is clear that implementation disclosed below
Example is only part of the embodiment of the present invention, and not all embodiment.Based on the embodiment in this patent, the common skill in this area
All other embodiment that art personnel are obtained under the premise of creative work is not made, belong to the model of this patent protection
Enclose.
The present embodiment provides a kind of java implementation methods of TOSCA specifications, as shown in figure 1, method includes：
S11, read the Yaml files for customization type；
S12, file stream is parsed based on snakeyaml；
Specifically, the file stream for obtaining file stream starts event and file stream End Event, and the thing since file stream
Part starts to parse, and judges event type one by one, until file stream End Event.
The beginning event of document and the End Event of document in file stream event are obtained, since document event
Parsing, until the End Event of document；
The beginning and end event of object type data in resolution file stream, event is opened since object type data
Begin to parse, until the End Event of object type data；
The beginning and end event of character types data in resolution file stream, event is opened since character types data
Begin to parse, until the End Event of character types data；
The beginning and end event of list type data in resolution file stream, event is opened since list type data
Begin to parse, until the End Event of list type data.
Judge that event type also includes one by one：
Parse the key assignments of each event；The key assignments of each event includes：Tosca_definitions_version modules are
The version of event, description modules are character types, datatype_definitions modules, node_ in event
Types modules, topology_template modules are object type.
Datatype_definitions modules, node_types modules, topology_template modules are entered respectively
Row parsing；
Datatype_definitions modules, node_types modules and topology_template moulds are parsed respectively
Block is inherited from that type, shows inheritance；
Datatype_definitions modules, node_types modules, topology_template modules are belonged to
Property description, attribute description, which includes, shows type and default field；
Datatype_definitions modules, node_types modules and topology_template have been read respectively
After module attribute and default field, by its datatype_definitions module, node_types modules, topology_
Template modules are put into datatypes lists to be used for other attributes.
Datatype_definitions modules, node_types modules, topology_template modules are parsed respectively
Field；
Node_type modules preserve customized node type and extend use for node_template modules, and provide
The field type of the node_type module definitions defined is used only in node_template modules.That is node_type modules are
Node definition, node_template modules are node instance；
Node_template modules include properties, attributes, interfaces and requirements tetra-
Individual attribute；Wherein properties is object properties；Attributes is the mark of storage, is 32 uuid；interfaces
Realized comprising implements scripts, dependencies is relied on and three elements of inputs input parameters；
Node_type modules and node_template modules after the completion of grammer format analysis by being stored in node_types
In register and node_templates registers, and uniformly it is put into global object topology, whole tosca specifications parsing
Complete.
YAML of the present invention is the language for writing configuration file.The data structure that YAML is supported has three kinds：Object：
The set of key-value pair, also known as map (mapping)/Hash (hashes)/dictionary (dictionary)；Array：One group in due order
The value of sequence arrangement, also known as sequence (sequence)/list (list)；Scale (scalars)：Single, not subdivisible value.
YAML establishes corresponding data model, including topology_template, node_ according to TOSCA specifications
Templates, attributes, artifacts, interfaces, requirements etc..Wherein topology_
Template is used for describing the general name of whole topological structure, and node_template describes the details of node template, wherein wrapping
Attribute attributes, external file attifacts, interface interfaces are included, and relies on requirements.
Node_template tables：The information of one node template.
| Sequence number | Field information | Explanation |
| 1 | attributes | The unique mark of storage, 32 uuid |
| 2 | artifacts | The title of storage |
| 3 | interfaces | The total capacity of storage, unit GB |
| 4 | requirements | Capacity, unit GB are used in storage |
S13, the file after parsing is decomposed according to system event type；
S14, the file after decomposing is read, the file after decomposition is stored in global object topology.
In the present invention, step includes before reading the Yaml files for customization type：
The data model of TOSCA specifications is established, data model includes topology_template modules, node_
Templates modules, attributes modules, artifacts modules, interfaces modules, requirements modules；
Topology_template modules are used for describing the general name of whole topological structure, the description of node_template modules
The details of node template, the details of node template include attribute attributes, external file attifacts, connect
Mouth interfaces, and rely on requirements.
In the present invention, step also includes before reading the Yaml files for customization type：
The Yaml files of customization type include：What system provided, for defining the normative_ of data type
The topology.yaml of oneself applied topology of types.yaml and the description of user's input；
First parse normative_types.yaml and preserve data type, and data type is stored in global object,
For being used during parsing topology.yaml files.
In the present invention, a further embodiment is：
S21, read the Yaml files for customization type；
S22, file stream is parsed based on snakeyaml；
S221, when the file after decomposition is DATA_type types, the fundamental type data defined in file are read, by text
Fundamental type data defined in part are preserved into global object topology；
S222, when the file after decomposition is node_type categorical datas, preserve into global object topology.
S23, the file after decomposing is read, the file after decomposition is stored in global object topology
S24, read the topology.yaml files of user；
S25, the topology.yaml files of user are decomposed according to the event type of user；
S26, reads user's topology.yaml files after decomposing respectively, and user's topology.yaml files include：
Node_template modules, topology.yaml fileinfos, topology.yaml FileVersions and
Topology.yaml file names；
S27, user's topology.yaml files after decomposition are preserved into global object topology.
In the present invention, Yaml document analysis includes two files, and one is that system provides, for defining data type
Normative_types.yaml and user input description oneself applied topology topology.yaml.So need elder generation
Parse normative_types.yaml and preserve data type, and data type is stored in global object, for parsing
Used during topology.yaml files.
Document is parsed using snakeyaml parse methods, returns to parsing event Event iterator
Iterator, event include following several：
DocumentEnd,DocumentStart,MappingEnd,MappingStart,Scalar,SequenceEnd,
SequenceStart,StreamEnd,StreamStart。
Wherein StreamStart and StreamEnd be read file stream beginning and end event, DocumentStart
With the event that DocumentEnd is parsing document beginning and end, MappingStart and MappingEnd are reading object class
The beginning and end event of type data, Scalar be read character types data event, SequenceStart and
SequenceEnd is the event identifier of read list categorical data beginning and end, is introduced from Yaml, and these event packages contain
The possible data type that all Yaml is included.
The present invention can define a kind of Yaml document formats for meeting TOSCA specifications by analytic method.Then, TOSCA
Specification is the cloud application Layout Standard of standard, based on this can flexible layout cloud application topological structure.And implementation method is also simple
List, it is readily appreciated that, convenient extension.
The foregoing description of the disclosed embodiments, professional and technical personnel in the field are enable to realize or using the present invention.
A variety of modifications to these embodiments will be apparent for those skilled in the art, as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the present invention.Therefore, it is of the invention
The embodiments shown herein is not intended to be limited to, and is to fit to and principles disclosed herein and features of novelty phase one
The most wide scope caused.
Claims (10)
1. a kind of java implementation methods of TOSCA specifications, it is characterised in that method includes：
Read the Yaml files for customization type；
File stream is parsed based on snakeyaml；
The file after parsing is decomposed according to system event type；
The file after decomposing is read, the file after decomposition is stored in global object topology.
2. the java implementation methods of TOSCA specifications according to claim 1, it is characterised in that
Step is parsed based on snakeyaml to file stream also to be included：
The file stream for obtaining file stream starts event and file stream End Event, and is parsed since event file stream,
Event type is judged one by one, until file stream End Event.
3. the java implementation methods of TOSCA specifications according to claim 2, it is characterised in that
Judge that event type also includes one by one：
Parse the key assignments of each event；
The key assignments of each event includes：Tosca_definitions_version modules are version, the description of event
Module is character types, datatype_definitions modules, node_types modules, topology_ in event
Template modules are object type.
4. the java implementation methods of TOSCA specifications according to claim 3, it is characterised in that
Datatype_definitions modules, node_types modules, topology_template modules are solved respectively
Analysis；
Datatype_definitions modules, node_types modules and topology_template modules are parsed respectively
That type is inherited from, shows inheritance；
Attribute is carried out to datatype_definitions modules, node_types modules, topology_template modules to retouch
State, attribute description, which includes, shows type and default field；
Datatype_definitions modules, node_types modules and topology_template modules have been read respectively
After attribute and default field, by its datatype_definitions module, node_types modules, topology_
Template modules are put into datatypes lists to be used for other attributes.
5. the java implementation methods of TOSCA specifications according to claim 4, it is characterised in that
Datatype_definitions modules, node_types modules, the word of topology_template modules are parsed respectively
Section；
Node_type modules preserve customized node type and extend use for node_template modules, and provide node_
The field type of the node_type module definitions defined is used only in template modules.I.e. node_type modules are that node is determined
Justice, node_template modules are node instance；
Node_template modules include tetra- category of properties, attributes, interfaces and requirements
Property；Wherein properties is object properties；Attributes is the mark of storage, is 32 uuid；Interfaces is included
Implements scripts are realized, dependencies is relied on and three elements of inputs input parameters；
Node_type modules and node_template modules are deposited by node_types is stored in after the completion of grammer format analysis
In device and node_templates registers, and uniformly it is put into global object topology, whole tosca specifications have parsed
Into.
6. the java implementation methods of TOSCA specifications according to claim 1, it is characterised in that
Step includes before reading the Yaml files for customization type：
The data model of TOSCA specifications is established, data model includes topology_template modules, node_templates
Module, attributes modules, artifacts modules, interfaces modules, requirements modules；
Topology_template modules are used for describing the general name of whole topological structure, and node_template modules describe node
The details of template, the details of node template include attribute attributes, external file attifacts, interface
Interfaces, and rely on requirements.
7. the java implementation methods of TOSCA specifications according to claim 1, it is characterised in that
Step also includes before reading the Yaml files for customization type：
The Yaml files of customization type include：What system provided, for defining the normative_ of data type
The topology.yaml of oneself applied topology of types.yaml and the description of user's input；
First parse normative_types.yaml and preserve data type, and data type is stored in global object, for solution
Used when analysing topology.yaml files.
8. the java implementation methods of TOSCA specifications according to claim 2, it is characterised in that
The file stream that step obtains file stream starts event and file stream End Event, and is solved since event file stream
Analysis, judges event type one by one, until file stream End Event also includes：
The beginning event of document and the End Event of document in file stream event are obtained, is solved since document event
Analysis, until the End Event of document；
The beginning and end event of object type data in resolution file stream, is solved since event object type data
Analysis, until the End Event of object type data；
The beginning and end event of character types data in resolution file stream, is solved since event character types data
Analysis, until the End Event of character types data；
The beginning and end event of list type data in resolution file stream, is solved since event list type data
Analysis, until the End Event of list type data.
9. the java implementation methods of TOSCA specifications according to claim 1, it is characterised in that
Step reads the file after decomposing, and also includes after the file after decomposition is stored in global object topology：
When file after decomposition is DATA_type types, the fundamental type data defined in file are read, defined in file
Fundamental type data are preserved into global object topology；
When file after decomposition is node_type categorical datas, preserve into global object topology.
10. the java implementation methods of TOSCA specifications according to claim 1, it is characterised in that
Step reads the file after decomposing, and also includes after the file after decomposition is stored in global object topology：
Read the topology.yaml files of user；
The topology.yaml files of user are decomposed according to the event type of user；
User's topology.yaml files after decomposing are read respectively, and user's topology.yaml files include：node_
Template modules, topology.yaml fileinfos, topology.yaml FileVersions and topology.yaml files
Title；
User's topology.yaml files after decomposition are preserved into global object topology.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710985478.8A CN107577467A (en) | 2017-10-20 | 2017-10-20 | A kind of java implementation methods of TOSCA specifications |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710985478.8A CN107577467A (en) | 2017-10-20 | 2017-10-20 | A kind of java implementation methods of TOSCA specifications |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107577467A true CN107577467A (en) | 2018-01-12 |
Family
ID=61037848
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710985478.8A Pending CN107577467A (en) | 2017-10-20 | 2017-10-20 | A kind of java implementation methods of TOSCA specifications |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107577467A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069788A (en) * | 2020-09-10 | 2020-12-11 | 杭州安恒信息技术股份有限公司 | Method, device and equipment for analyzing yaml file and storage medium |
| CN112464037A (en) * | 2020-10-23 | 2021-03-09 | 北京思特奇信息技术股份有限公司 | TOSCA service processing method, processing system and processor |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100458793C (en) * | 2007-05-10 | 2009-02-04 | 浪潮集团山东通用软件有限公司 | Mapping conversion method between data access level Xml format data and relational data |
| WO2016079399A1 (en) * | 2014-11-21 | 2016-05-26 | Fastconnect | Methods for managing the life cycle of a cloud application using a plurality of cloud infrastructures |
-
2017
- 2017-10-20 CN CN201710985478.8A patent/CN107577467A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100458793C (en) * | 2007-05-10 | 2009-02-04 | 浪潮集团山东通用软件有限公司 | Mapping conversion method between data access level Xml format data and relational data |
| WO2016079399A1 (en) * | 2014-11-21 | 2016-05-26 | Fastconnect | Methods for managing the life cycle of a cloud application using a plurality of cloud infrastructures |
Non-Patent Citations (2)
| Title |
|---|
| QINGHUA GAO: "TOSCA简介", 《HTTP://QINGHUA.GITHUB.IO/TOSCA/》 * |
| RESENTMENT: "JAVA使用SNAKEYAML解析YAML", 《HTTPS://WWW.CNBLOGS.COM/RESENTMENT/P/5872798.HTML》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069788A (en) * | 2020-09-10 | 2020-12-11 | 杭州安恒信息技术股份有限公司 | Method, device and equipment for analyzing yaml file and storage medium |
| CN112464037A (en) * | 2020-10-23 | 2021-03-09 | 北京思特奇信息技术股份有限公司 | TOSCA service processing method, processing system and processor |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108399256B (en) | Heterogeneous database content synchronization method and device and middleware | |
| Maali et al. | A publishing pipeline for linked government data | |
| CN109726128A (en) | A kind of method for generating test case, device and server | |
| WO2017059014A1 (en) | Interoperability of transforms under a unified platform and extensible transformation library of those interoperable transforms | |
| CN109376866B (en) | Method and device for recording metadata and method and device for running quantum program | |
| CN110275861A (en) | Date storage method and device, storage medium, electronic device | |
| US8429599B2 (en) | Computer method and system for enforcing derived union constraints | |
| CN102722769A (en) | Experimental data processing system and method | |
| CN105868311A (en) | Data analyzing method and device | |
| CN108363566A (en) | File configuration method, intelligent terminal and storage medium in a kind of project development process | |
| US20070143330A1 (en) | Processing an XML schema | |
| WO2019223178A1 (en) | Cross-platform task scheduling method and system, computer device, and storage medium | |
| CN109460250A (en) | A kind of generation method and equipment of application program | |
| CN107577467A (en) | A kind of java implementation methods of TOSCA specifications | |
| CN102833102B (en) | Customer premise equipment system of set-card separated type gateway and data configuration management method | |
| CN101170436B (en) | A method for managing template in network management system | |
| CN104021216B (en) | Message proxy server and information publish subscription method and system | |
| Palmer et al. | RAVEN: Using smartphones for collaborative disaster data collection. | |
| CN103905233B (en) | Realize method, system and the access network device of analog sensor plug and play | |
| CN103646015B (en) | Transmission, the method and system for receiving and transmitting XML message | |
| CN108683740A (en) | A kind of method and system of the promotion configuration access speed based on UCI | |
| CN109298899A (en) | A kind of file automating application method of juvenile's game configuration and electronic equipment | |
| US8027362B2 (en) | Methods and systems for pushing and pulling network data in user interface design | |
| CN110209578A (en) | A kind of information on-line testing platform | |
| CN109445755A (en) | A kind of multi version hadoop integrated approach and device based on OSGI |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200522 Address after: Building S01, Inspur Science Park, No. 1036, Inspur Road, high tech Zone, Jinan City, Shandong Province, 250000 Applicant after: Tidal Cloud Information Technology Co.,Ltd. Address before: 450000 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180112 |
|
| RJ01 | Rejection of invention patent application after publication |