Service-based message access layer frame and implementation method thereof

• US 20160352736A1
• Filed: 12/19/2014
• Published: 12/01/2016
• 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
• Granted Patent: US 9,832,198 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 service-based 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 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 sending the data acceptable to the application back end to the application back end for a data handling by cloud. The present invention guarantees a security of a connection from the application front end to the application back end and an access speed and avoids a large technical developing workload. The present invention is applicable to an access service from the application front end to the application back end.

Claims

1-9. -9. (canceled)

10. :

A service-based message access layer frame, comprising;

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

said controller comprises a configuration file parser and a database access service;

said controller is for initiating, initializing and coordinating said receiver, said account password checker, said session processor and said repeater;

said receiver is for receiving a request of an application front end in various forms;

after receiving data in different formats, said receiver translates the received data in the different formats into data in a consistent format and then sends the data in the consistent formation to said session processor;

said account password checker is for controlling and validating an access of the request of the application front end and thereafter sending the request to said repeater;

said session processor, serving as a main handling module of said whole service-based message access layer frame, is for handling the request with a login management, a rights management, a behavior auditing, a log, a single sing-on and interface exposing; and

said repeater is for translating the handled 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 to be handled by cloud.

11. :

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

12. :

A method for implementing a service-based message access layer frame, comprising steps of;

(1) after initiating a system, parsing a configuration file, initiating a database access service, and initializing and initiating a receiver, an account password checker, a session processor and a repeater of the service-based message access layer frame by a controller;

(2) after an application front end sends a request, 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 by the receiver;

(3) handling a client request and sending the handled client request to the repeater, by the account password checker and the session processor which serve as main information handling modules of the frame; and

(4) translating the handled 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, by the repeater.

13. :

method for implementing the service-based message access layer frame, as recited in claim 12, wherein a working process of the controller comprises steps of;

(a) reading and parsing the configuration file;

initiating 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;

(b) initiating 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;

(c) initiating the database access service;

initiating the account password checker with a connection provided by the database access service; and

obtaining validation information of an account from a database; and

(d) finally initiating the session processor which has no session therein initially;

and the controller has a handling logic that;

a strategy assigned by the configuration file determines which modules the request passes through and how the request is handled;

once a problem occurs, a handling chain is stopped and the request is returned to the controller in advance;

the controller, according to returned abnormal information, returns a response to the client request in advance through the receiver and finishes a request response.

14. :

The method for implementing the service-based message access layer frame, as recited in claim 12, wherein the receiver, as a server, continually receives the request of the application front end and, after receiving, assigns a unique identification (ID) to each the request.

15. :

The method for implementing the service-based message access layer frame, as recited in claim 13, wherein the receiver, as a server, continually receives the request of the application front end and, after receiving, assigns a unique identification (ID) to each the request.

16. :

The method for implementing the service-based message access layer frame, as recited in claim 12, wherein;

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 a unique ID, sessionId;

each application front end is assigned the sessionId 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 sessionId in the request.

17. :

The method for implementing the service-based message access layer frame, as recited in claim 13, wherein;

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 a unique ID, sessionId;

each application front end is assigned the sessionId 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 sessionId in the request.

18. :

The method for implementing the service-based message access layer frame, as recited in claim 14, wherein;

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 a unique ID, sessionId;

each application front end is assigned the sessionId 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 sessionId in the request.

19. :

The method for implementing the service-based message access layer frame, as recited in claim 15, wherein;

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 a unique ID, sessionId;

each application front end is assigned the sessionId 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 sessionId in the request.

20. :

The method for implementing the service-based message access layer frame, as recited in claim 12, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.

21. :

The method for implementing the service-based message access layer frame, as recited in claim 13, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.

22. :

The method for implementing the service-based message access layer frame, as recited in claim 14, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.

23. :

The method for implementing the service-based message access layer frame, as recited in claim 15, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.

24. :

The method for implementing the service-based message access layer frame, as recited in claim 16, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.

25. :

The method for implementing the service-based message access layer frame, as recited in claim 17, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.

26. :

The method for implementing the service-based message access layer frame, as recited in claim 18, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.

27. :

The method for implementing the service-based message access layer frame, as recited in claim 19, wherein the step of handling the request comprises steps of;

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

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

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

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

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

after sending response information, destroying corresponding connection information by the receiver, 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.