CN109189590A - Memory management method and device based on RESTful service - Google Patents
Memory management method and device based on RESTful service Download PDFInfo
- Publication number
- CN109189590A CN109189590A CN201810932221.0A CN201810932221A CN109189590A CN 109189590 A CN109189590 A CN 109189590A CN 201810932221 A CN201810932221 A CN 201810932221A CN 109189590 A CN109189590 A CN 109189590A
- Authority
- CN
- China
- Prior art keywords
- token
- request
- client
- storage
- equipment
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/549—Remote execution
Abstract
The invention discloses a kind of memory management methods and device based on RESTful service, include the following steps: S1 client platform by sending operation of the HTTP request completion to storage equipment；S2 stores the serve end program in equipment when responding the request of different clients platform, it is required that token is applied in first call in request end, the serve end program is after receiving the application token request from client, it parses relevant parameter in this request and is matched with parameter in device databases, return to requesting party's token after verifying is correct；With S3 when carrying out other operation requests to storage equipment after obtaining token, need in the HTTP head requested every time comprising this token.The invention has the advantages that: the requests using unified back-end services response different platform or system.
Description
Technical field
The present invention relates to technical field of memory, it particularly relates to a kind of memory management method based on RESTful service
And device.
Background technique
In the business production system of current different industries, storage system and its service are become more and more important, such as with
In data storage, data protection, data backup and remote copy etc..It is deposited different from the personal use based on single physical disk
Storage, the business production system activity of current various industries are highly dependant on depositing for high-performance, high security and high reliability
Storage system.With the development of the times, the management program in storage apparatus field in addition to traditional end Web, the pipe based on mobile terminal APP
Reason program is also emerging in multitude, and integration of equipments quotient is for Deep integrating user production system, storage system, data protection system
System and cloud platform, the opening API for storing equipment is also constantly proposing requirements at the higher level, but does not use unified back-end services
Respond the request of different platform or system.
REST refers to one group of framework constraint condition and principle, if a framework meets the constraint condition and original of REST
Then, then it is referred to as RESTful framework, and RESTful framework is disclosed using the state of rear end program and function as resource to client,
Each resource obtains a unique address using URL, and all resources all pass through unified interface and externally provide response service,
It is each request must comprising rear end understand request necessary to information, use the HTTP method of standard, as GET, PUT,
POST, DELETE are requested.
For the problems in the relevant technologies, currently no effective solution has been proposed.
Summary of the invention
For above-mentioned technical problem in the related technology, the present invention proposes a kind of storage management based on RESTful service
Method and device, can be using the request of unified back-end services response different platform or system.
To realize the above-mentioned technical purpose, the technical scheme of the present invention is realized as follows:
A kind of memory management method based on RESTful service, includes the following steps:
S1 client platform is by sending operation of the HTTP request completion to storage equipment；
S2 stores the serve end program in equipment when responding the request of different clients platform, it is desirable that calls for the first time request end
When apply for token, the serve end program parses related in this request after receiving the application token request from client
Simultaneously and in device databases parameter is matched parameter, returns to requesting party's token after verifying is correct；With
S3 needs in the HTTP head requested every time when carrying out other operation requests to storage equipment after obtaining token comprising this
Token.
Further, in step S1, the client platform includes web administration end, the mobile end APP.
Further, in step S1, it is described to storage equipment operation include creation iSCSI link, creation disk and
Data protection.
Further, in step S1, the storage equipment is stored as block in cloud platform, and cloud platform passes through storage equipment
Block store driver calls storage device interface, and provides block storage medium for cloud platform.
Further, in step S2, apply for the administrator account for needing to provide storage equipment when token and equipment system
System code, token format are 128 character strings that 16 systems indicate.
Further, if user will modify memory apparatus system administrator's password or from now on because replacement hardware causes systematic code to become
More, then it needs to re-call and obtains the new token of token interface application.
Further, in step S3, further comprise:
S31 stores device service end program when receiving other requests of non-application token, and will parse token format first is
It is no correct, it then parses the concrete operations of client transmission and whether client is had permission and carry out this operation and authenticate；
S32 carries out the operation of client request if authenticating successfully, unsuccessfully returns to HTTP status code 401；With
HTTP status code is returned if the related resource created in storage server after the operation of S33 progress client request
201, if status code 200 is returned if establishing resource not in storage server.
Another aspect of the present invention provides a kind of storage device based on RESTful service, comprising:
Client platform, including web administration end, the mobile end APP, the client platform are completed by sending HTTP request to depositing
The operation of equipment is stored up, the operation to storage equipment includes creation iSCSI link, creation disk and data protection；With
Equipment is stored, serve end program is when responding the request of different clients platform, it is desirable that request end is in first call
Apply for token, the serve end program parses related ginseng in this request after receiving the application token request from client
Simultaneously and in device databases parameter is matched number, requesting party's token is returned to after verifying is correct, to storage after obtaining token
When equipment carries out other operation requests, need in the HTTP head requested every time comprising this token.
Further, apply needing to provide the administrator account and device systems code of storage equipment, token when token
Format is 128 character strings that 16 systems indicate, if user will modify memory apparatus system administrator's password or hard because replacing from now on
Part causes systematic code to change, then needs to re-call the new token of acquisition token interface application.
Further, storage device service end program will parse first when receiving other requests of non-application token
Whether token format is correct, then parses the concrete operations of client transmission and whether has permission this operation of progress to client
It is authenticated；The operation of client request is carried out if authenticating successfully, unsuccessfully returns to HTTP status code 401；Carry out client
HTTP status code 201 is returned to after the operation of request if the related resource created in storage server, if do not deposited
Establishing resource then returns to status code 200 in storage server.
Beneficial effects of the present invention: using the request of unified back-end services response different platform or system.
Detailed description of the invention
It in order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, below will be to institute in embodiment
Attached drawing to be used is needed to be briefly described, it should be apparent that, the accompanying drawings in the following description is only some implementations of the invention
Example, for those of ordinary skill in the art, without creative efforts, can also obtain according to these attached drawings
Obtain other attached drawings.
Fig. 1 is the signal of the managing device of the storage system based on RESTful service described according to embodiments of the present invention
Figure；
Fig. 2 is the flow chart of the memory management method based on RESTful service described according to embodiments of the present invention；
Fig. 3 is the flow chart of the memory management method based on RESTful service described according to embodiments of the present invention.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art's every other embodiment obtained belong to what the present invention protected
Range.
Based on the relevant operation of RESTful architecture design storage equipment, the resources of storage media in equipment will be stored,
The requesting methods such as GET, POST, PUT, DELETE using http protocol respond the various operations for resource in storage equipment,
Such as:
It obtains medium-related information in storage equipment and uses GET method；
Increase storage equipment intermediary qualitative correlation and operates with POST method；
It updates storage equipment intermediary qualitative correlation and operates with PUT method；
It deletes storage equipment intermediary qualitative correlation and operates with DELETE method.
As shown in Figure 1-3, the memory management method based on RESTful service described according to embodiments of the present invention, including
Following steps:
Different client platforms such as web administration end, the mobile end APP, are completed by sending HTTP request to storage equipment
Operation, such as creation iSCSI link, create disk, data protection etc., the storage equipment can be deposited as block in cloud platform
Storage, cloud platform call storage device interface by the block store driver of storage equipment, provide block storage medium for cloud platform,
Such as the cinder of openstack platform.
Service routine in storage device needs request end in first call when responding the request of different front-end platforms
Apply for token.When applying for token, it is desirable to provide store the administrator account and device systems code of equipment, storage equipment clothes
Business end program will parse relevant parameter and and device data in this request after receiving the application token request from client
Parameter is matched in library, and requesting party's token is returned to after verifying is correct, and token format is 128 characters that 16 systems indicate
String.If user will modify memory apparatus system administrator's password or from now on because replacement hardware causes systematic code to change, need to adjust again
With the new token of acquisition token interface application.
After obtaining token to storage equipment carry out other operation requests when, need include in the HTTP head requested every time
This token.Whether storage device service routine will parse first token format when receiving other requests of non-application token
Correctly, then parse client transmission concrete operations and to client whether have permission carry out this operation authenticate, such as
Fruit authenticates the operation for successfully then carrying out client request, unsuccessfully returns to HTTP status code 401.After the operation for carrying out client request
HTTP status code 201 is returned to if the related resource created in storage server, if do not created in storage server
It builds resource and then returns to status code 200.
Another aspect of the present invention provides a kind of storage device based on RESTful service, comprising:
Client platform, including web administration end, the mobile end APP, the client platform is by sending HTTP request completion pair
The operation of equipment is stored, the operation to storage equipment includes creation iSCSI link, creation disk and data protection；With
Equipment is stored, serve end program is when responding the request of different clients platform, it is desirable that apply in first call request end
Token, the serve end program receive from client application token request after, parse this request in relevant parameter simultaneously
It is matched with parameter in device databases, returns to requesting party's token after verifying is correct, to storage equipment after obtaining token
When carrying out other operation requests, need in the HTTP head requested every time comprising this token.
In one particular embodiment of the present invention, apply needing to provide the administrator account of storage equipment when token
And device systems code, token format is 128 character strings that 16 systems indicate, if user will modify memory apparatus system management from now on
Member's password causes systematic code to change because replacing hardware, then needs to re-call the new token of acquisition token interface application.
In one particular embodiment of the present invention, storage device service end program is receiving other non-for applying for token
When request, will parse whether token format is correct first, and then parse the concrete operations of client transmission and be to client
It is no have permission carry out this operation authenticated；The operation of client request is carried out if authenticating successfully, unsuccessfully returns to HTTP shape
State code 401；HTTP state is returned if the related resource created in storage server after carrying out the operation of client request
Code 201, if returning to status code 200 if establishing resource not in storage server.
In order to facilitate understanding above-mentioned technical proposal of the invention, below by way of in specifically used mode to of the invention above-mentioned
Technical solution is described in detail.
When specifically used, the memory management method according to the present invention based on RESTful service, for different visitors
Application token interface is called to obtain token by http protocol in family end (Web, APP, Cinder)；Equipment is added in HTTP to enable
Board calls storage equipment to create disk function；Client computer (Windows, Linux) is created by disk management program carry equipment
Build disk；Device token is added in HTTP calls storage device data defencive function to carry out data guarantor to created disk
Shield；Device token is added in HTTP calls storage equipment creation snapshot functions to carry out snapshot to created disk.
In conclusion by means of above-mentioned technical proposal of the invention, it can be different flat using unified back-end services response
The request of platform or system.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, all in essence of the invention
Within mind and principle, any modification, equivalent replacement, improvement and so on be should all be included in the protection scope of the present invention.
Claims (10)
1. a kind of memory management method based on RESTful service, which comprises the steps of:
S1 client platform is by sending operation of the HTTP request completion to storage equipment；
S2 stores the serve end program in equipment when responding the request of different clients platform, it is desirable that calls for the first time request end
When apply for token, the serve end program parses related in this request after receiving the application token request from client
Simultaneously and in device databases parameter is matched parameter, returns to requesting party's token after verifying is correct；With
S3 needs in the HTTP head requested every time when carrying out other operation requests to storage equipment after obtaining token comprising this
Token.
2. the memory management method according to claim 1 based on RESTful service, which is characterized in that in step S1, institute
Stating client platform includes web administration end, the mobile end APP.
3. the memory management method according to claim 1 based on RESTful service, which is characterized in that in step S1, institute
Stating includes creation iSCSI link, creation disk and data protection to the operation of storage equipment.
4. the memory management method according to claim 1 based on RESTful service, which is characterized in that in step S1,
The storage equipment is stored as block in cloud platform, and cloud platform calls storage equipment to connect by storing the block store driver of equipment
Mouthful, and block storage medium is provided for cloud platform.
5. the memory management method according to claim 1 based on RESTful service, which is characterized in that in step S2, Shen
It please need to provide the administrator account and device systems code of storage equipment when token, token format is what 16 systems indicated
128 character strings.
6. the memory management method according to claim 5 based on RESTful service, which is characterized in that if user will be from now on
Modification memory apparatus system administrator's password causes systematic code to change because replacing hardware, then needs to re-call acquisition token interface
Apply for new token.
7. the memory management method according to claim 1 based on RESTful service, which is characterized in that in step S3, into
One step includes:
S31 stores device service end program when receiving other requests of non-application token, and will parse token format first is
It is no correct, it then parses the concrete operations of client transmission and whether client is had permission and carry out this operation and authenticate；
S32 carries out the operation of client request if authenticating successfully, unsuccessfully returns to HTTP status code 401；With
HTTP status code is returned if the related resource created in storage server after the operation of S33 progress client request
201, if status code 200 is returned if establishing resource not in storage server.
8. a kind of storage device based on RESTful service characterized by comprising
Client platform, including web administration end, the mobile end APP, the client platform are completed by sending HTTP request to depositing
The operation of equipment is stored up, the operation to storage equipment includes creation iSCSI link, creation disk and data protection；With
Equipment is stored, serve end program is when responding the request of different clients platform, it is desirable that request end is in first call
Apply for token, the serve end program parses related ginseng in this request after receiving the application token request from client
Simultaneously and in device databases parameter is matched number, requesting party's token is returned to after verifying is correct, to storage after obtaining token
When equipment carries out other operation requests, need in the HTTP head requested every time comprising this token.
9. the storage device according to claim 8 based on RESTful service, which is characterized in that needed when application token
The administrator account and device systems code of storage equipment are provided, token format is 128 character strings that 16 systems indicate, if
User will modify memory apparatus system administrator's password or from now on because replacement hardware causes systematic code to change, then will need to re-call acquisition
The new token of token interface application.
10. the storage device according to claim 8 based on RESTful service, which is characterized in that storage device service end
For program when receiving other requests of non-application token, whether correct, then parse client if will parse token format first
Hold send concrete operations and to client whether have permission carry out this operation authenticate；Client is carried out if authenticating successfully
The operation of request is held, HTTP status code 401 is unsuccessfully returned；If created in storage server after the operation of progress client request
The related resource built then returns to HTTP status code 201, if not returning to status code if establishing resource in storage server
200。
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810932221.0A CN109189590A (en) | 2018-08-16 | 2018-08-16 | Memory management method and device based on RESTful service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810932221.0A CN109189590A (en) | 2018-08-16 | 2018-08-16 | Memory management method and device based on RESTful service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109189590A true CN109189590A (en) | 2019-01-11 |
Family
ID=64918069
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810932221.0A Pending CN109189590A (en) | 2018-08-16 | 2018-08-16 | Memory management method and device based on RESTful service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109189590A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110032337A (en) * | 2019-03-15 | 2019-07-19 | 启迪云计算有限公司 | A kind of third party's storage cluster management method based on WEB navigation |
| CN110247905A (en) * | 2019-06-05 | 2019-09-17 | 黄疆 | The data backup memory method and system of secure authentication mode based on Token |
| CN116208668A (en) * | 2023-05-05 | 2023-06-02 | 北京零壹视界科技有限公司 | Data caching method, device, equipment and medium based on content distribution network |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106302346A (en) * | 2015-05-27 | 2017-01-04 | 阿里巴巴集团控股有限公司 | The safety certifying method of API Calls, device, system |
| CN106651586A (en) * | 2016-12-30 | 2017-05-10 | 上海富聪金融信息服务有限公司 | Multi-distributor oriented financial product marketing open service platform |
| CN107360131A (en) * | 2017-05-27 | 2017-11-17 | 广东网金控股股份有限公司 | A kind of method, server and the system of the control of service request legitimacy |
| US20170366538A1 (en) * | 2015-08-07 | 2017-12-21 | Amazon Technologies, Inc. | Validation for requests |
| CN107689870A (en) * | 2017-08-29 | 2018-02-13 | 杭州绿湾网络科技有限公司 | Client method for authenticating and system |
| US9973547B1 (en) * | 2016-02-09 | 2018-05-15 | Vecima Networks Inc. | Method and systems for adaptively managing hypertext transfer protocol sessions in a content delivery network |
-
2018
- 2018-08-16 CN CN201810932221.0A patent/CN109189590A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106302346A (en) * | 2015-05-27 | 2017-01-04 | 阿里巴巴集团控股有限公司 | The safety certifying method of API Calls, device, system |
| US20170366538A1 (en) * | 2015-08-07 | 2017-12-21 | Amazon Technologies, Inc. | Validation for requests |
| US9973547B1 (en) * | 2016-02-09 | 2018-05-15 | Vecima Networks Inc. | Method and systems for adaptively managing hypertext transfer protocol sessions in a content delivery network |
| CN106651586A (en) * | 2016-12-30 | 2017-05-10 | 上海富聪金融信息服务有限公司 | Multi-distributor oriented financial product marketing open service platform |
| CN107360131A (en) * | 2017-05-27 | 2017-11-17 | 广东网金控股股份有限公司 | A kind of method, server and the system of the control of service request legitimacy |
| CN107689870A (en) * | 2017-08-29 | 2018-02-13 | 杭州绿湾网络科技有限公司 | Client method for authenticating and system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110032337A (en) * | 2019-03-15 | 2019-07-19 | 启迪云计算有限公司 | A kind of third party's storage cluster management method based on WEB navigation |
| CN110247905A (en) * | 2019-06-05 | 2019-09-17 | 黄疆 | The data backup memory method and system of secure authentication mode based on Token |
| CN116208668A (en) * | 2023-05-05 | 2023-06-02 | 北京零壹视界科技有限公司 | Data caching method, device, equipment and medium based on content distribution network |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111801923B (en) | Replication of resource types and schema metadata for multi-tenant identity cloud services | |
| CN112166588B (en) | Tenant replication bootstrapping for multi-tenant identity cloud services | |
| US9473419B2 (en) | Multi-tenant cloud storage system | |
| US10484385B2 (en) | Accessing an application through application clients and web browsers | |
| US8544072B1 (en) | Single sign-on service | |
| JP5429912B2 (en) | Authentication system, authentication server, service providing server, authentication method, and program | |
| US8219814B2 (en) | System and method of user credential management | |
| US20160065563A1 (en) | Method and apparatus for accessing third-party resources | |
| WO2016173199A1 (en) | Mobile application single sign-on method and device | |
| CN103930897A (en) | Mobile application, single sign-on management | |
| CN106572087B (en) | Voice outbound system | |
| CN106357699A (en) | Network system, service platform and login method and system of service platform | |
| US20150256603A1 (en) | System and method for aggregating and providing data from enterprise systems to mobile devices | |
| CN109189590A (en) | Memory management method and device based on RESTful service | |
| CN109067785A (en) | Cluster authentication method, device | |
| CN111832000A (en) | Single sign-on method, system, equipment and computer readable storage medium | |
| CN113505354B (en) | Data processing method, device and storage medium | |
| TW201909072A (en) | Method, device, and apparatus for loss reporting, removing loss report, and service management of electronic account | |
| CN109660567A (en) | A kind of communication connecting method, server, terminal device and system | |
| CN111382985A (en) | To-do message integrated pushing system and working method | |
| WO2014152076A1 (en) | Retry and snapshot enabled cross-platform synchronized communication queue | |
| CN111464534A (en) | Session keeping method and device in distributed system | |
| CN109450990A (en) | A kind of cloud storage implementation method and electronic equipment based on educational system | |
| CN107911443A (en) | A kind of session information processing method, device, server and readable storage medium storing program for executing | |
| CN112068929A (en) | Unified management method for accessing multi-architecture cloud platform to third-party web service |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190111 |