Service-based message access layer frame and implementation method thereof

• US 9,832,198 B2
• Filed: 12/19/2014
• Issued: 11/28/2017
• Est. Priority Date: 05/09/2014
• Status: Active Grant

• Current Assignee: G-Cloud Technology Company Limited
• Original Assignee: G-Cloud Technology Company Limited
• Inventors: Mo, Zhanpeng, Yang, Song, Ji, Tongkai
• Primary Examiner(s): Truong, Thanhnga B
• Application Number:
  US14/772,338
• Publication Number:
  US 20160352736A1
• Time in Patent Office: 1,075 Days
• Field of Search: 726 1- 8, 709219, 709224, 709225, 709227, 709228, 709229, 370310, 370328, 370338, 370401, 713151, 713155, 713168, 705 35, 705 712, 705 713
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A message access layer frame and an implementation method thereof are provided, relating to a technical field of software. After initiating a system, a controller parses a configuration file, initiates a database access service unit and initializes and initiates other components. After an application front end sends a request, a receiver receives the request of the application front end, translates the request into data in a consistent format and sends the data in the consistent format to a next handling module. An account password checker and a session processor, serving as main information handling modules of the frame, handle a client request and send the handled client request to the repeater. A repeater translates the handled data in the consistent format into data acceptable to an application back end and sends the data acceptable to the application back end to the application back end for a data handling by cloud.

Claims

1. A message access layer frame, comprising:

a controller, a receiver, an account password checker, a session processor and a repeater, wherein;

the controller comprises a configuration file parser and a database access service unit; and

, the controller initiates, initializes and coordinates the receiver, the account password checker, the session processor and the repeater;

the receiver receives a request of an application front end in various forms, and after receiving data in different formats, translates the received data in the different formats into data in a consistent format, and then sends the data in the consistent formation to the session processor;

the account password checker controls and validates an access of the request of the application front end and thereafter sends the request to the repeater;

the session processor, serving as a main handling module of the whole message access layer frame, handles the request with a login management, a right management, a behavior auditing, a log, a single sign-on and interface exposing;

the repeater translates the handled data in the consistent format into data acceptable to an application back end, and then sends the data acceptable to the application back end to the application back end to be handled by cloud; and

the message access layer frame has a working process that;

after initiating a system, the controller parses a configuration file through the configuration file parser and initiates the database access service unit;

then the controller initiates the receiver according to the configuration file, wherein the receiver is different in accordance with the different application front ends and depends on a communication protocol of the application front end;

next, the controller initiates the repeater, wherein the repeater is different in accordance with the different application back ends and depends on a communication manner of the application back end;

thereafter, the controller initiates the account password checker with a connection provided by the database access service unit, and obtains validation information of an account from a database; and

finally, the controller initiates the session processor which has no session therein initially;

after the application front end sends the request, the receiver receives the request of the application front end, translates the request of the application front end into the data in the consistent format and sends the data in the consistent format to the session processor, wherein;

the receiver, as a server, continually receives the request of the application front end and, after receiving, assigns a unique ID to each request;

the session processor contains connection information from the different application front ends, wherein the connection information is called sessions, and each session is distinguished by the unique ID, session Id; and

the session processor extracts the session ID from each request and checks whether the session ID already exists;

if the session ID exists, which means that the session already exists, the session is sent to the repeater;

if the session ID does not exist, which means that the session is a new session, the session is sent to the account password checker for an authentication;

if the authentication is failed, an error code is directly returned to the application front end without continuing sending the session; and

if the authentication is passed, the session is registered and success authentication information is returned to the application front end;

after the repeater receives the data in the consistent format, the repeater translates the data in the consistent format into the data acceptable to the application back end, and then sends the data acceptable to the application back end to the application back end for a data handling by cloud; and

after sending response information, the receiver destroys the corresponding connection information, wherein the receiver is merely responsible for receiving and returning the request;

each request is independent; and

, once handling of the request is finished, the receiver readily eliminates the corresponding connection information and waits for a next request.

2. The message access layer frame, as recited in claim 1, wherein the request of the application front end comes from a web front end or a client of a customized application layer protocol.

3. A method for implementing a message access layer frame, comprising steps of:

initiating a system;

parsing a configuration file through a configuration file parser and initiating a database access service unit by a controller;

initiating a receiver, a repeater, an account password checker and a session processor by the controller;

after an application front end sends a request, the receiver receiving the request of the application front end, translating the request of the application front end into data in a consistent format and sending the data in the consistent format to the session processor, wherein;

the receiver, as a server, continually receives the request of the application front end and, after receiving, assigns a unique ID to each request;

obtaining connection information from the different application front ends by the session processor, wherein the connection information is called sessions, and each session is distinguished by the unique ID, session Id; and

, the session processor extracting the session ID from each request and checking whether the session ID already exists;

if the session ID exists, which means that the session already exists, sending the session to the repeater;

if the session ID does not exist, which means that the session is a new session, sending the session to the account password checker for an authentication;

if the authentication is failed, returning an error code directly to the application front end without continuing sending the session; and

if the authentication is passed, registering the session and returning success authentication information to the application front end;

after the repeater receives the data in the consistent format, the repeater translating the data in the consistent format into data acceptable to an application back end, and then sending the data acceptable to the application back end to the application back end for a data handling by cloud; and

after sending response information, the receiver destroying the corresponding connection information, wherein the receiver is merely responsible for receiving and returning the request;

each request is independent; and

, once handling of the request is finished, the receiver readily eliminates the corresponding connection information and waits for a next request.

4. The method for implementing the message access layer frame, as recited in claim 3, wherein:

the receiver is initiated according to a configuration file;

the repeater is different in accordance with the different application back ends and depends on a communication manner of the application back end;

the account password checker is initiated with a connection provided by the database access service unit; and

the session processor has no session therein initially.

5. The method for implementing the message access layer frame, as recited in claim 3, wherein:

each application front end is assigned the session Id after connecting to the message access layer frame for a first time and being checked by the account password checker; and

subsequent connections of the application front end must contain the session Id in the request.

6. The method for implementing the message access layer frame, as recited in claim 4, wherein:

each application front end is assigned the session Id after connecting to the message access layer frame for a first time and being checked by the account password checker; and

subsequent connections of the application front end must contain the session Id in the request.