CN114900559A

CN114900559A - Management system, terminal, management method, and storage medium

Info

Publication number: CN114900559A
Application number: CN202210376000.6A
Authority: CN
Inventors: 吴阻剑; 李良斌; 陈孝良
Original assignee: Beijing SoundAI Technology Co Ltd
Current assignee: Beijing SoundAI Technology Co Ltd
Priority date: 2022-04-11
Filing date: 2022-04-11
Publication date: 2022-08-12

Abstract

The application provides a management system, a terminal, a management method and a storage medium, and belongs to the technical field of internet. The management system includes: the system comprises a plurality of subsystems, a registry and a gateway, wherein the types of services provided by the subsystems are different; the gateway is used for responding to an access request sent by the terminal and sending a query request to the registration center, wherein the access request carries a target subsystem identifier corresponding to a target subsystem to be accessed by the terminal; the registration center is used for determining a target service address corresponding to the target subsystem identifier from the corresponding relation between the subsystem identifier and the service address when receiving the query request, and returning the target service address; the gateway is also used for sending an access request to the target subsystem based on the target service address; and the target subsystem is used for sending an access result determined based on the access request to the terminal when receiving the access request sent by the gateway based on the target service address. The management system improves the flexibility of service management.

Description

Management system, terminal, management method, and storage medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to a management system, a terminal, a management method, and a storage medium.

Background

With the development of internet technology, terminals can provide background services by means of servers. In the related art, a server is usually adopted to provide background services for a terminal, but as the functions of the terminal become more and more complex, the types of services required to be provided by the server are more and more, and the increase or modification of any service can cause the redeployment of the server, and the flexibility is poor.

Disclosure of Invention

The embodiment of the application provides a management system, a terminal, a management method and a storage medium, which can improve the flexibility of service management. The technical scheme is as follows:

according to an aspect of an embodiment of the present application, there is provided a management system, including: a plurality of subsystems, a registry and a gateway, each subsystem providing a different type of service;

the gateway is used for responding to an access request sent by a terminal and sending a query request to the registration center, wherein the access request carries a target subsystem identifier corresponding to a target subsystem to be accessed by the terminal, the target subsystem is any one of the subsystems, and the query request carries the target subsystem identifier;

the registry is used for determining a target service address corresponding to the target subsystem identifier from the corresponding relation between the subsystem identifier and the service address when the query request is received, and returning the target service address;

the gateway is further used for sending the access request to the target subsystem based on the target service address;

and the target subsystem is used for sending an access result determined based on the access request to the terminal when receiving the access request sent by the gateway based on the target service address.

In one possible implementation, the target subsystem includes a login authentication subsystem; the login authentication subsystem is used for:

receiving a login request sent by the gateway based on the target service address, wherein the login request is sent by the terminal in response to a login operation triggered in a login interface of a running target application, and the login request carries a target account and a target password input in the login interface;

and sending login success information to the terminal under the condition that the target account and the target password which correspond to each other in a one-to-one mode are inquired from the corresponding relation between the account and the password, or sending login failure information to the terminal under the condition that any one of the target account and the target password is not inquired from the corresponding relation between the account and the password.

In a possible implementation manner, the subsystem is configured to send a registration request to the registry, where the registration request carries a subsystem identifier and a service address of the subsystem;

and the registration center is used for responding to the registration request and storing the corresponding relation between the subsystem identification and the service address.

In one possible implementation, the subsystem comprises a third party services subsystem;

and the third-party service subsystem is used for providing services for the third-party system based on the access request when the access request sent by the third-party system is received through the gateway.

In one possible implementation, the subsystem includes an elevator subsystem, a gas cylinder subsystem, a data statistics subsystem, or a video surveillance subsystem.

According to another aspect of embodiments of the present application, there is provided a terminal, including a processor and a memory, where at least one program code is stored, and the at least one program code is loaded and executed by the processor to implement the following steps:

displaying a management interface corresponding to a management system, wherein the management system comprises a gateway, a registration center and a plurality of subsystems, the types of services provided by the subsystems are different, and the types of the services provided by the subsystems are displayed in the management interface;

responding to a trigger operation of the type of service provided by a target subsystem, and sending an access request to the gateway, wherein the target subsystem is any one of the subsystems, and the access request carries a target subsystem identifier corresponding to the target subsystem;

receiving an access result which is sent by the target subsystem and determined based on the access request;

the access request is used for the gateway to send a query request to the registry, the query request is used for the registry to return the target service address corresponding to the target subsystem identifier, and the target service address is used for the gateway to send the access request to the target subsystem based on the target service address.

In one possible implementation, the target subsystem is a login authentication subsystem; the at least one program code is loaded into and executed by the processor to perform the steps of:

responding to login operation triggered in a login interface of the running target application, and sending a login request to the login authentication subsystem through the gateway, wherein the login request carries a target account and a target password input in the login interface;

when login success information or login failure information sent by the login authentication subsystem is received, displaying the login success information or the login failure information;

the login request is used for the login authentication subsystem to send login success information to the terminal under the condition that the target account and the target password which correspond to each other in a one-to-one mode are inquired from the corresponding relation between the account and the password, or to send login failure information to the terminal under the condition that any one of the target account and the target password is not inquired from the corresponding relation between the account and the password.

According to another aspect of the embodiments of the present application, there is provided a management method performed by a management system, the management system including a gateway, a registry, and a plurality of subsystems, each of the subsystems providing different types of services, the management method including:

the gateway responds to an access request sent by a terminal, and sends a query request to the registration center, wherein the access request carries a target subsystem identifier corresponding to a target subsystem to be accessed by the terminal, the target subsystem is any one of the subsystems, and the query request carries the target subsystem identifier;

when the registration center receives the query request, determining a target service address corresponding to the target subsystem identifier from the corresponding relation between the subsystem identifier and the service address, and returning the target service address;

the gateway sends the access request to the target subsystem based on the target service address;

and when receiving the access request sent by the gateway based on the target service address, the target subsystem sends an access result determined based on the access request to the terminal.

According to another aspect of the embodiments of the present application, there is provided a management method, executed by a terminal, the management method including:

According to another aspect of the embodiments of the present application, there is provided a computer-readable storage medium, in which at least one program code is stored, and the at least one program code is loaded and executed by a processor to implement the management method in any one of the above-mentioned possible implementation manners.

According to another aspect of embodiments of the present application, there is provided a computer program product comprising computer program code stored in a computer-readable storage medium, from which a processor reads the computer program code, the processor executing the computer program code to implement the management method as described in any one of the above possible implementations.

The embodiment of the application provides a management system, the types of services provided by each subsystem in the system are different, and the registration center stores the corresponding relation between the subsystem identifier of each subsystem and the service address, so that when a terminal accesses a target subsystem, the corresponding target service address can be obtained from the registration center through a gateway according to the target subsystem identifier of the target subsystem, and thus the gateway can forward an access request to the subsystem corresponding to the target service address, so that the subsystems can provide corresponding services for the terminal, a plurality of subsystems can provide services for the terminal independently, even if new services to be added to the management system or one subsystem need to modify the services, the influence on other subsystems is small, and the flexibility of service management is greatly improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a management system provided in an embodiment of the present application;

FIG. 2 is a flow chart of a management method provided by an embodiment of the present application;

FIG. 3 is a flow chart of another management method provided by an embodiment of the present application;

FIG. 4 is a flow chart of yet another management method provided by an embodiment of the present application;

FIG. 5 is a flow chart of yet another management method provided by an embodiment of the present application;

fig. 6 is a schematic structural diagram of a server provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

It will be understood that the terms "first," "second," and the like as used herein may be used herein to describe various concepts, which are not limited by these terms unless otherwise specified. These terms are only used to distinguish one concept from another.

As used herein, the terms "at least one," "a plurality," "each," "any," and the like, at least one comprises one, two, or more than two, and a plurality comprises two or more than two, each referring to each of the corresponding plurality, and any referring to any one of the plurality.

It should be noted that the information (including but not limited to information of elevator, information of gas cylinder, information of video monitoring, etc.), data (including but not limited to data for processing, stored data, displayed data, etc.) referred to in the present application are authorized by users or fully authorized by each party, and the collection, use and processing of the related data need to comply with the relevant laws and regulations and standards of the relevant country and region. For example, the account number and password referred to in this application are obtained with sufficient authorization.

Fig. 1 is a schematic structural diagram of a management system 100 provided in an embodiment of the present application, and referring to fig. 1, the management system 100 includes a plurality of subsystems 101, a registry 102, and a gateway 103, where types of services provided by each subsystem 101 are different.

Wherein both the subsystem 101 and the registry 102 may be provided as servers. Optionally, the server is at least one of a server, a server cluster composed of multiple servers, a cloud server, a cloud computing platform, and a virtualization center, which is not limited in this embodiment of the present application. Alternatively, the different subsystems 101 may be called by an RPC Call (Remote Procedure Call). It should be noted that each subsystem 101 may share one database, or each subsystem 101 may also have an independent database, which is not limited in the embodiment of the present application.

In the embodiment of the present application, the terminal 200 can perform information interaction with the management system 100 to realize access to the management system, for example, the terminal 200 accesses any subsystem 101, that is, the terminal 200 invokes a service provided by the subsystem 101. Optionally, the terminal 200 includes, but is not limited to, a smartphone, a tablet, a laptop, or a desktop computer. The terminal 200 can access the management system 100 through the internet. Optionally, the terminal 200 has installed thereon a target application for accessing the management system 100. For example, the target application is an administrative application, a browser, or any application that contains a web view control.

In the embodiment of the present application, the target subsystem is any subsystem 101 in the multiple subsystems 101, and a process of accessing the target subsystem 101 by the terminal 200 is taken as an example for description:

the gateway 103 is configured to send, in response to an access request sent by the terminal 200, an inquiry request to the registry 102, where the access request carries a target subsystem identifier corresponding to a target subsystem 101 to be accessed by the terminal 200, and the inquiry request carries the target subsystem identifier;

the registry 102 is used for determining a target service address corresponding to the target subsystem identifier from the corresponding relation between the subsystem identifier and the service address when receiving the query request, and returning the target service address;

the gateway 103 is also used for sending 101 an access request to the target subsystem based on the target service address;

and the target subsystem 101 is used for sending an access result determined based on the access request to the terminal when receiving the access request sent by the gateway based on the target service address.

In this embodiment of the application, the management system and the terminal can implement a process of accessing the target subsystem by the terminal through the following interaction embodiment shown in fig. 2, which is not described herein again in this embodiment of the application.

The management method provided by the embodiment of the application can be applied to various service access scenes, and the application scenes of the management method are introduced below. For example, the target subsystem includes an elevator subsystem, taking a terminal accessing the elevator subsystem as an example, a user triggers a type "elevator" in a management interface displayed by the terminal, the terminal responds to the type being triggered and sends an access request to the gateway, the gateway sends the access request to the elevator subsystem through the management method provided by the embodiment of the application, and the elevator subsystem returns a corresponding access result through the management method provided by the embodiment of the application, so that the terminal can display the access result for the user to view.

It should be noted that the above application scenarios are only exemplary, and do not limit the service access scenarios, and the present application can be applied to any other service access scenarios besides the above scenarios.

In the embodiment of the present application, the services provided by the subsystems in the management system may be set as needed, which is not limited in the present application. Optionally, taking as an example that the management system is a management system for a liquefied gas station, the subsystems include an elevator subsystem, a gas cylinder subsystem, a data statistics subsystem or a video monitoring subsystem. And the management system comprises a plurality of subsystems, each subsystem can be an elevator subsystem, a gas cylinder subsystem, a data statistics subsystem or a video monitoring subsystem, at least two of the elevator subsystem, the gas cylinder subsystem, the data statistics subsystem and the video monitoring subsystem can be included in the plurality of subsystems, and the plurality of subsystems can comprise not only subsystems with different service types but also subsystems with the same service type.

Wherein the elevator subsystem is used to provide elevator-type services, illustratively the services provided by the elevator subsystem include: at least one of services such as elevator maintenance task management, maintenance items, maintenance lists, maintenance company management, maintenance worker management, contract management, camera management, service reminding and the like. Wherein the cylinder subsystem is used for providing cylinder type services, exemplarily, the services provided by the cylinder subsystem include: at least one of the services of gas cylinder basic information management, gas cylinder file management, gas cylinder distribution diagram, gas cylinder query, gas cylinder filling record, gas cylinder scrap record, gas cylinder circulation track, gas cylinder abnormity warning, gas cylinder inspection information and the like. The video monitoring subsystem is configured to provide a video monitoring type service, and exemplarily, the service provided by the video monitoring subsystem includes: and at least one of services such as video monitoring and checking, equipment management, safety monitoring and warning, vehicle identification and recording and the like of the liquefied gas station. The data statistics subsystem is configured to provide data statistics type services, and the services provided by the data statistics subsystem exemplarily include: at least one of gas station data statistics, elevator data statistics, gas cylinder basic information statistics, monitoring alarm statistics, gas cylinder filling statistics, abnormal information statistics and the like. Optionally, the data statistics subsystem performs data statistics at regular time, and correspondingly, the data statistics subsystem performs data statistics at intervals of a preset duration. The preset duration may be set as needed, which is not limited in the embodiment of the present application, for example, the preset duration includes at least one of durations of 1 month, 1 quarter, half year, and 1 year. The data statistics is carried out at regular time, so that the data counted by the data statistics subsystem can be timely updated, and the accuracy of the data is ensured.

It should be noted that the services provided by the above subsystems are only exemplary, and do not limit the services provided by the multiple subsystems, and the management system provided in the embodiment of the present application may include any other subsystem that provides a service in addition to the multiple subsystems.

Fig. 2 is a flowchart of a management method according to an embodiment of the present application. In the embodiment of the present application, a service access process is realized through information interaction between a terminal and a management system, as shown in fig. 2, and the method includes the following steps:

201. the terminal displays a management interface corresponding to the management system, the management system comprises a gateway, a registration center and a plurality of subsystems, the types of services provided by the subsystems are different, and the types of the services provided by the subsystems are displayed in the management interface.

When a user wants to view or manage information through the management system, the user can trigger the terminal to display a management interface corresponding to the management system. Optionally, a target application capable of accessing the management system is installed in the terminal, and the user triggers the terminal to run the target application, so that the terminal is triggered to display the management interface in the target application. The management interface displays the type of service provided by each subsystem, for example, if the subsystem is an elevator subsystem, the management interface displays the type "elevator" corresponding to the elevator subsystem, and if the subsystem is a gas cylinder subsystem, the management interface displays the type "gas cylinder" corresponding to the gas cylinder subsystem.

202. The terminal responds to the trigger operation of the type of the service provided by the target subsystem, and sends an access request to the gateway, wherein the target subsystem is any one of the subsystems, and the access request carries a target subsystem identifier corresponding to the target subsystem.

In the embodiment of the application, since the terminal shows the type of the service provided by each subsystem in the management interface, when a user wants to view or manage information in any subsystem, the terminal can be triggered to invoke the service provided by the subsystem. For example, the target subsystem comprises an elevator subsystem, a type 'elevator' is shown in the management interface, the user triggers the type 'elevator' through a terminal, and the terminal generates an access request in response to a triggering operation of the type 'elevator'.

The access request is used for calling the service provided by the target subsystem, the target subsystem provides the service through the interface, and the access request is also used for calling the service provided by the interface. The type of service provided by each subsystem exposed in the management interface corresponds to the interface of that subsystem. The subsystem identification corresponding to the subsystem is used for uniquely identifying the subsystem so as to distinguish different subsystems. The subsystem identifier corresponding to the subsystem may be set as needed, which is not limited in this embodiment of the application.

In the embodiment of the application, the terminal can send the access request to the target subsystem by means of the gateway, so that the terminal does not need to store the service address of the subsystem, the storage space of the terminal is saved, the terminal only needs to send the access request to the gateway, and the workload of the terminal is reduced.

203. And the gateway responds to the access request sent by the terminal and sends a query request to the registration center, wherein the query request carries the target subsystem identification.

Where the gateway may be seen as an intermediary connecting the terminal and the subsystem. After receiving an access request sent by a terminal, a gateway acquires a target subsystem identifier carried by the access request, and generates an inquiry request, wherein the inquiry request is used for inquiring a target service address corresponding to the target subsystem identifier from a registration center, namely the target service address corresponding to the target subsystem, so that the inquiry request also carries the target subsystem identifier.

204. When the registry receives the query request, the target service address corresponding to the target subsystem identifier is determined from the corresponding relation between the subsystem identifier and the service address, and the target service address is returned.

The registry stores the corresponding relation between the subsystem identification and the service address corresponding to each subsystem. For example, the registry is a Nacos (Naming and configuration service, a registry for registering and configuring services). When receiving a query request sent by a gateway, a registry acquires a target subsystem identifier carried by the query request, and queries a target service address corresponding to the target subsystem identifier from a stored corresponding relation between the subsystem identifier and the service address.

Optionally, in a case that the target subsystem identifies a corresponding target service address, the target service address is sent to the gateway, and the gateway performs the operation of step 205. Optionally, when the target service address corresponding to the target subsystem identifier is not queried, query failure information is sent to the gateway, where the query failure information is used to indicate that the target service address corresponding to the target subsystem identifier is not queried, and the gateway receives the query failure information. If the target service address corresponding to the target subsystem is not queried, the gateway cannot send the access request of the terminal to the target subsystem, and the gateway can send access failure information to the terminal, wherein the access failure information is used for indicating that the access request is not sent to the target subsystem. Optionally, the terminal displays a prompt message in response to receiving the access failure message, where the prompt message is used to prompt that the relevant information of the target subsystem is not obtained. The content included in the prompt message may be set as needed, which is not limited in this application. For example, taking the target subsystem as an elevator subsystem as an example, if the terminal receives the access failure information, the terminal displays a prompt message that the relevant information of the elevator is not obtained, and the user can check the prompt message through the terminal, so that a relevant technician can be reminded to check the corresponding subsystem in time to ensure that the subsystem can provide services normally. The embodiment of the present application is described by taking an example that a registry can query a target service address corresponding to a target subsystem identifier.

Optionally, the subsystem in the management system may send its subsystem identifier and service address to the registry, so that the registry stores the subsystem identifier and service address, and the method provided in this embodiment further includes the following steps: the subsystem sends a registration request to a registration center, wherein the registration request carries a subsystem identifier and a service address of the subsystem; the registry stores a correspondence between the subsystem identification and the service address in response to the registration request. In a possible implementation manner, the subsystem can provide the service for the terminal after the service is deployed, and then the subsystem sends a registration request to the registry after the service is deployed. The subsystem in the embodiment of the application can send the subsystem identification and the service address of the subsystem to the registration center, so that the registration center can register the subsystem, the corresponding storage of the subsystem identification and the service address is realized, the registration center can provide a function of inquiring the service address corresponding to the subsystem, and data support is provided for a service access process.

205. The gateway sends an access request to the target subsystem based on the target service address.

And after receiving the target service address returned by the registration center, the gateway sends an access request to the target subsystem. Since the target subsystem corresponding to the obtained target service address is a subsystem to be accessed by the terminal, the target service address can be regarded as a real request address of an access request sent by the terminal.

In this embodiment of the present application, before sending an access request, a gateway needs to acquire routing information corresponding to a target subsystem, where the routing information indicates a path pointing to a service address of the target subsystem, and the gateway sends the access request to the target subsystem through the path. The gateway stores routing information corresponding to each subsystem in advance. Optionally, the gateway obtains a prefix carried by a request path in the target service address, queries routing information matching the routing prefix from stored routing information, and determines the routing information as routing information of the target subsystem. Accordingly, the gateway sends an access request to the target subsystem based on the path indicated by the routing information. The prefix of the request path in the service address and the routing prefix of the routing information can both uniquely identify the subsystem, and the gateway can query the routing information of the target subsystem through matching between the prefixes.

206. And when receiving an access request sent by the gateway based on the target service address, the target subsystem sends an access result determined based on the access request to the terminal.

The access request carries request parameters, when the target subsystem receives the access request, corresponding processing is carried out according to the request parameters carried by the access request, an access result is obtained through processing, and the access result is sent to the terminal. And the target subsystem sends the access result to the terminal through the gateway. Optionally, the data format in the access result is JSON (JavaScript Object Notation) format, and JS is a programming language.

207. And the terminal receives an access result which is sent by the target subsystem and determined based on the access request.

And the terminal receives the access result sent by the target subsystem through the gateway. Optionally, the terminal displays in the management interface according to the access result, for example, if the user triggers the type "elevator" corresponding to the elevator subsystem displayed in the management interface, the elevator subsystem returns the access result, the access result includes service identifiers "service 1", "service 2", and "service 3" of a plurality of services provided by the elevator subsystem, and the terminal displays the plurality of service identifiers in the management interface for the user to select the required service.

Optionally, the subsystem comprises a third party service subsystem, the third party service subsystem being capable of providing services for an external system; accordingly, when the third-party service subsystem receives the access request sent by the third-party system through the gateway, the third-party system is provided with services based on the access request. Optionally, when the third-party service subsystem receives an access request sent by the third-party system through the gateway, based on the access request, an implementation manner of providing a service for the third-party system is the same as the implementation manner of steps 201 to 206, and details are not described here again.

Illustratively, the third party service subsystem is provided with at least one of elevator equipment state reporting service, media data uploading service and information synchronization service. Optionally, the third-party system sends the access request in response to a target event, where the target event may be set as needed, which is not limited in this application. Correspondingly, if the target event is a request for reporting the state of the elevator equipment, the third-party system sends an access request to call the elevator equipment state reporting service provided by the third-party service subsystem, wherein the access request carries the state of the elevator equipment, the third-party service subsystem receives the access request of the third-party system through the gateway and stores the state of the elevator equipment carried by the access request, and the state reporting of the elevator equipment is realized. If the target event is a request for uploading media data, the third-party system sends an access request to call a media data uploading service provided by the third-party service subsystem, wherein the access request carries the media data, the third-party service subsystem receives the access request of the third-party system through the gateway, stores the media data carried by the access request, and uploads the media data. The media data includes video streaming media or other media data, which is not limited in this embodiment of the present application. If the target event is a request for synchronizing information, the third-party system sends an access request to call information synchronization service provided by the third-party service subsystem, the access request carries information to be synchronized, the third-party service subsystem receives the access request of the third-party system through the gateway and stores the information carried by the access request, and information synchronization is achieved.

In the embodiment of the application, the third-party system can call the service provided by the third-party service subsystem, and the purpose of providing the service for the external system is achieved.

According to the embodiment of the application, each subsystem provides different services, the subsystems are relatively independent and have small dependence, the management system is constructed by using the micro-service framework, each subsystem is registered in the registration center, and an access for external access is provided for the subsystems through the gateway, so that distributed transactions of the management system are realized. The operation of each subsystem is not influenced by other subsystems, so that the stability and the safety of the management system are guaranteed; for the concurrency requirement of partial subsystems, the subsystems can be flexibly deployed, so that good flexibility is provided; on the basis of not influencing the existing service, a new subsystem can be constructed in the management system, and the management system provided by the embodiment of the application has high expandability.

In the embodiment of the application, the subsystem comprises a login authentication subsystem, the login authentication subsystem can authenticate an access request of the terminal and determine whether the terminal has the authority of accessing the target subsystem, if the terminal has the authority of accessing the target subsystem, the gateway sends the access request of the terminal to the target subsystem, and if the terminal does not have the authority of accessing the target subsystem, the gateway returns error information, and the error information indicates that the terminal cannot access the target subsystem.

Optionally, all access requests triggered by the terminal through the management interface of the management system need to be processed uniformly through the gateway, and accordingly, after receiving the access request of the terminal, the gateway sends the access request to the login authentication subsystem, and the login authentication subsystem authenticates the access request, so as to determine whether the terminal has the authority to access the target subsystem. The terminal can call the service provided by the subsystem only by logging in an account, and the account is used for uniquely distinguishing different users. And directly returning error information to an access request sent by a terminal which does not log in the account, wherein the access request can be regarded as an unauthorized access request. For an access request sent by a terminal logged in with an account, after acquiring a target service address corresponding to a target subsystem identifier carried by the access request, a gateway sends the access request to a target subsystem. When the terminal logs in an account, a login request is sent to the gateway, the gateway forwards the login request to the login authentication subsystem, if the login is successful, the login authentication subsystem returns token (token) information of the terminal, and the terminal stores the token information and carries the token information when an access request is sent subsequently.

Optionally, for an access request sent by a terminal logged in with an account, the gateway may further authenticate the access request through the login authentication subsystem. Correspondingly, the gateway sends the access request to a login authentication subsystem, the login authentication subsystem determines whether the target subsystem identifier carried by the access request belongs to a white list, if so, passing information is sent to the gateway, and the passing information indicates that the terminal has the authority of accessing the target subsystem. The white list comprises at least one subsystem identification, and the subsystem corresponding to the at least one subsystem identification is a subsystem which can be accessed without authentication. The white list may be set as needed, which is not limited in this embodiment of the application. If the target subsystem identification belongs to the white list, the authentication operation of the access request can be skipped, namely the access request is not authenticated, so that the authentication process is saved, and the access efficiency is improved.

If the access request does not belong to the white list, the login authentication subsystem verifies the token information carried by the access request and judges whether the token information is valid. Wherein token information is typically in the request header of the access request. Optionally, the login authentication subsystem acquires token information corresponding to the account currently logged in by the terminal from the cache database, compares the token information with token information carried by the access request, and if the two token information are consistent, the token information is valid, that is, the verification is passed, and the terminal has the right to access the target subsystem; and if the two token information are inconsistent, the token information is invalid, the verification fails, and the terminal does not have the authority of accessing the target subsystem.

The following describes a login authentication process by taking a target subsystem as a login authentication subsystem and an access request as a login request, fig. 3 is a flowchart of another management method provided in the embodiment of the present application, and referring to fig. 3, the method includes the following steps:

301. and the terminal responds to login operation triggered in a login interface of the running target application and sends a login request to the login authentication subsystem through the gateway, wherein the login request carries a target account and a target password input in the login interface.

The user triggers the terminal to run the target application, and the terminal displays a login interface in the target application. Optionally, an input area and a login control are displayed in the login interface, a user inputs a target account and a target password in the input area to trigger the login control, and the terminal responds to the trigger operation of the login control, acquires the target account and the target password input in the input area, and sends a login request to the gateway.

302. And the login authentication subsystem receives a login request sent by the gateway based on the target service address.

Optionally, the implementation manners of step 301 to step 302 are the same as the implementation manners of step 201 to step 205, and are not described herein again.

After step 302, if the target account and the target password input by the user are correct, the login authentication subsystem performs the operation of step 303, then the terminal performs the operation of step 304, if the target account and the target password input by the user are not correct, the login authentication subsystem performs the operation of step 305, and then the terminal performs the operation of step 306.

303. And the login authentication subsystem sends login success information to the terminal under the condition that the target account and the target password which correspond to each other one by one are inquired from the corresponding relation between the account and the password.

The login authentication subsystem stores a registered account and a password corresponding to the account, and the account and the password are stored correspondingly. After receiving the login request, the login authentication subsystem acquires a target account and a target password in the login request, inquires the target account and the target password from the stored corresponding relation between the account and the password, and if the target account and the target password are inquired, the login authentication subsystem sends login success information to the terminal through the gateway, and the login success information carries token information. The login success information indicates that the login is successful, and the information content may be set as needed, which is not limited in the present application.

304. The terminal receives the login success information.

After the login success information is received, the token information is stored by the terminal, and a management interface is displayed in the target application.

305. And the login authentication subsystem sends login failure information to the terminal under the condition that any one of the target account and the target password is not inquired from the corresponding relation between the account and the password.

The login authentication subsystem inquires a target account and a target password from the stored corresponding relation between the account and the password, and if at least one of the target account and the target password is not inquired, the target account and the target password input by a user in the terminal are not correct, and the login authentication subsystem sends login failure information to the terminal through the gateway. The login failure information indicates that the login is failed, and the information content may be set as required, which is not limited in the present application.

306. The terminal receives the login failure information.

Optionally, after receiving the login failure information, the terminal displays a prompt message in the login interface, where the prompt message prompts that the login is failed, and the information content may be set as required, which is not limited in this application. For example, the prompt message is "account number or password error", so as to prompt the user to re-input the account number or password.

In the embodiment of the application, different target applications are provided with different login authorities. The target application may be an application corresponding to the management system, that is, an application that can access each subsystem in the management system, or the target application may also be an application corresponding to a specific subsystem, that is, an application that can access a part of the subsystems. For example, taking an example that a plurality of subsystems of the management system further include an elevator subsystem, a gas cylinder subsystem, a data statistics subsystem and a video monitoring subsystem besides a login authentication subsystem, target applications are a security management application, a gas distributor application, a maintenance worker application and a browser capable of running a management website corresponding to the management system, wherein each target application can access the login authentication subsystem, and each subsystem in the management system can be accessed by the security management application and the browser capable of running the management website; the gas distribution worker application can also access the gas cylinder subsystem, and the maintenance worker application can also access the elevator subsystem. The account capable of logging in the management website comprises an account of a gas station manager, an account of a maintenance manager and an account of a market manager, the account capable of logging in the security management application comprises an account of a market manager, the account capable of logging in the maintenance application comprises an account of a maintenance worker, and the account capable of logging in the gas distribution worker application comprises an account of a gas station operator.

Optionally, the login authentication subsystem stores, for each application identifier of the target application, a corresponding relationship between a corresponding account and a password, where an account in the corresponding relationship between the account and the password stored in the target application is an account capable of logging in the target application, and an account not included in the corresponding relationship between the account and the password is an account incapable of logging in the target application. The login request sent by the terminal carries an application identifier of the target application. After receiving a login request, the login authentication subsystem acquires the corresponding relation between the account and the password, which is stored corresponding to the application identifier, from the corresponding relation between the account and the password, inquires a target account and a target password carried by the login request from the corresponding relation between the account and the password, if the target account can be inquired, the target account can log in the target application, and if the target account cannot be inquired, the target account cannot log in the target application.

In the embodiment of the application, the login request sent by the terminal is verified through the corresponding relation between the stored account and the password in the login authentication subsystem, so that whether the target account and the target password input by the user are correct or not can be verified, the fact that the terminal logged in with the account can access the subsystem can be guaranteed, and the safety of the management system can be improved.

All the above optional technical solutions may be combined arbitrarily to form optional embodiments of the present application, and are not described herein again.

In the embodiment of the present application, the management system and the terminal can implement a service access process through the interactive embodiment shown in fig. 2, or the management system and the terminal can further respectively perform respective steps in the foregoing embodiments, which are described in detail in the embodiments shown in fig. 4 and fig. 5 below.

Fig. 4 is a flowchart of another management method provided in an embodiment of the present application. The embodiment of the present application is executed by a management system, and the management system includes: a plurality of subsystems, a registry and a gateway, each subsystem providing a different type of service, see fig. 4, the method comprising the steps of:

401. the gateway responds to an access request sent by the terminal, and sends a query request to the registration center, wherein the access request carries a target subsystem identifier corresponding to a target subsystem to be accessed by the terminal, the target subsystem is any one of the subsystems, and the query request carries the target subsystem identifier.

402. When the registry receives the query request, the target service address corresponding to the target subsystem identifier is determined from the corresponding relation between the subsystem identifier and the service address, and the target service address is returned.

403. The gateway sends an access request to the target subsystem based on the target service address.

404. And when receiving an access request sent by the gateway based on the target service address, the target subsystem sends an access result determined based on the access request to the terminal.

The management system provided by the embodiment of the application has different types of services provided by each subsystem, and the registration center stores the corresponding relation between the subsystem identifier of each subsystem and the service address, so that when a terminal accesses a target subsystem, the corresponding target service address can be obtained from the registration center through the gateway according to the target subsystem identifier of the target subsystem, and the gateway can forward an access request to the subsystem corresponding to the target service address, so that the subsystems can provide corresponding services for the terminal, and thus, a plurality of subsystems can provide services for the terminal independently, even if new services to be added to the management system or one subsystem needs to modify the services, the influence on other subsystems is small, and the flexibility of service management is greatly improved.

Fig. 5 is a flowchart of another management method provided in an embodiment of the present application. The embodiment of the application is executed by a terminal, and referring to fig. 5, the method includes the following steps:

501. the terminal displays a management interface corresponding to the management system, the management system comprises a gateway, a registration center and a plurality of subsystems, the types of services provided by the subsystems are different, and the types of the services provided by the subsystems are displayed in the management interface.

502. The terminal responds to the trigger operation of the type of the service provided by the target subsystem, and sends an access request to the gateway, wherein the target subsystem is any one of the subsystems, and the access request carries a target subsystem identifier corresponding to the target subsystem.

503. And the terminal receives an access result which is sent by the target subsystem and determined based on the access request.

The access request is used for the gateway to send a query request to the registry, the query request is used for the registry to return a target service address corresponding to the target subsystem identifier, and the target service address is used for the gateway to send the access request to the target subsystem based on the target service address.

In the embodiment of the application, when the terminal accesses the target subsystem, the corresponding target service address can be obtained from the registration center through the gateway according to the target subsystem identifier of the target subsystem, so that the gateway can forward the access request to the subsystem corresponding to the target service address, and the subsystem can provide corresponding service for the terminal.

Fig. 6 is a schematic structural diagram of a server 600 according to an embodiment of the present application. The server 600 may have a relatively large difference due to different configurations or performances, and may include a processor (CPU) 601 and a memory 602, where the memory 602 is used for storing at least one program code, and the at least one program code is loaded and executed by the processor 601 to implement the management method in the foregoing embodiments. Certainly, the server 600 may further have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input and output, and the server 600 may further include other components for implementing functions of the terminal, which is not described herein again.

Those skilled in the art will appreciate that the architecture shown in FIG. 6 does not constitute a limitation on server 600, and may include more or fewer components than those shown, or combine certain components, or employ a different arrangement of components.

The embodiment of the application provides a terminal, which comprises a processor and a memory, wherein at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor, so as to realize the management method in the embodiment.

Fig. 7 is a block diagram of a terminal 700 according to an embodiment of the present application. The terminal 700 may be a portable mobile terminal such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 700 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so on.

In general, terminal 700 includes: a processor 701 and a memory 702.

The processor 701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 701 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 701 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 701 may be integrated with a GPU (Graphics Processing Unit) that is responsible for rendering and drawing content that the display screen needs to display. In some embodiments, the processor 701 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

Memory 702 may include one or more computer-readable storage media, which may be non-transitory. Memory 702 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 702 is used to store at least one computer program for execution by the processor 701 to implement the answer determination method for the question provided by the method embodiments herein.

In some embodiments, the terminal 700 may further optionally include: a peripheral interface 703 and at least one peripheral. The processor 701, memory 702, and peripheral interface 703 may be connected by buses or signal lines. Various peripheral devices may be connected to peripheral interface 703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 704, a display screen 705, a camera assembly 706, an audio circuit 707, a positioning component 708, and a power source 709.

The peripheral interface 703 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 701 and the memory 702. In some embodiments, processor 701, memory 702, and peripheral interface 703 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 701, the memory 702, and the peripheral interface 703 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 704 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 704 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 704 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 704 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuitry 704 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 704 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 705 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 705 is a touch display screen, the display screen 705 also has the ability to capture touch signals on or over the surface of the display screen 705. The touch signal may be input to the processor 701 as a control signal for processing. At this point, the display 705 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 705 may be one, disposed on a front panel of the terminal 700; in other embodiments, the display 705 can be at least two, respectively disposed on different surfaces of the terminal 700 or in a folded design; in other embodiments, the display 705 may be a flexible display disposed on a curved surface or on a folded surface of the terminal 700. Even more, the display 705 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The Display 705 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.

The camera assembly 706 is used to capture images or video. Optionally, camera assembly 706 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 706 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuitry 707 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 701 for processing or inputting the electric signals to the radio frequency circuit 704 to realize voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different portions of the terminal 700. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The loudspeaker can be a traditional film loudspeaker and can also be a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 707 may also include a headphone jack.

The positioning component 708 is used to locate the current geographic Location of the terminal 700 for navigation or LBS (Location Based Service). The Positioning component 708 may be a Positioning component based on the united states GPS (Global Positioning System), the chinese beidou System, the russian graves System, or the european union's galileo System.

Power supply 709 is provided to supply power to various components of terminal 700. The power source 709 may be alternating current, direct current, disposable batteries, or rechargeable batteries. When the power source 709 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, the terminal 700 can also include one or more sensors 170. The one or more sensors 170 include, but are not limited to: acceleration sensor 711, gyro sensor 712, pressure sensor 713, optical sensor 714, and proximity sensor 715.

The acceleration sensor 711 can detect the magnitude of acceleration in three coordinate axes of a coordinate system established with the terminal 700. For example, the acceleration sensor 711 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 701 may control the display screen 705 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 711. The acceleration sensor 711 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 712 may detect a body direction and a rotation angle of the terminal 700, and the gyro sensor 712 may cooperate with the acceleration sensor 711 to acquire a 3D motion of the terminal 700 by the user. From the data collected by the gyro sensor 712, the processor 701 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensors 713 may be disposed on a side frame of terminal 700 and/or underneath display 705. When the pressure sensor 713 is disposed on a side frame of the terminal 700, a user's grip signal on the terminal 700 may be detected, and the processor 701 performs right-left hand recognition or shortcut operation according to the grip signal collected by the pressure sensor 713. When the pressure sensor 713 is disposed at a lower layer of the display screen 705, the processor 701 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 705. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The optical sensor 714 is used to collect the ambient light intensity. In one embodiment, the processor 701 may control the display brightness of the display screen 705 based on the ambient light intensity collected by the optical sensor 714. Specifically, when the ambient light intensity is high, the display brightness of the display screen 705 is increased; when the ambient light intensity is low, the display brightness of the display screen 705 is adjusted down. In another embodiment, the processor 701 may also dynamically adjust the shooting parameters of the camera assembly 706 according to the ambient light intensity collected by the optical sensor 714.

A proximity sensor 715, also known as a distance sensor, is typically disposed on the front panel of the terminal 700. The proximity sensor 715 is used to collect a distance between the user and the front surface of the terminal 700. In one embodiment, when the proximity sensor 715 detects that the distance between the user and the front surface of the terminal 700 gradually decreases, the processor 701 controls the display 705 to switch from the bright screen state to the dark screen state; when the proximity sensor 715 detects that the distance between the user and the front surface of the terminal 700 is gradually increased, the processor 701 controls the display 705 to switch from the breath-screen state to the bright-screen state.

Those skilled in the art will appreciate that the configuration shown in fig. 7 is not intended to be limiting of terminal 700 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

In an exemplary embodiment, there is also provided a computer readable storage medium having at least one program code stored therein, the at least one program code being loaded and executed by a processor to implement the management method in the above-described embodiments. The computer readable storage medium may be a memory. For example, the computer-readable storage medium may be a ROM (Read-Only Memory), a RAM (Random Access Memory), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage terminal, and the like.

In an exemplary embodiment, there is also provided a computer program product comprising computer program code stored in a computer readable storage medium, a processor reading the computer program code from the computer readable storage medium, the processor executing the computer program code to implement the management method as in the above embodiments.

In some embodiments, the computer program according to the embodiments of the present application may be deployed to be executed on one computer device or on multiple computer devices located at one site, or may be executed on multiple computer devices distributed at multiple sites and interconnected by a communication network, and the multiple computer devices distributed at the multiple sites and interconnected by the communication network may constitute a block chain system. The computer device may be provided as a terminal or a server.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The present application is intended to cover various modifications, alternatives, and equivalents, which may be included within the spirit and scope of the present application.

Claims

1. A management system, characterized in that the management system comprises: a plurality of subsystems, a registry and a gateway, each subsystem providing a different type of service;

2. The system of claim 1, wherein the target subsystem comprises a login authentication subsystem; the login authentication subsystem is used for:

receiving a login request sent by the gateway based on the target service address, wherein the login request is sent by the terminal in response to a login operation triggered in a login interface of a running target application, and the login request carries a target account and a target password;

3. The system according to claim 1, wherein the subsystem is configured to send a registration request to the registry, where the registration request carries a subsystem identifier and a service address of the subsystem;

4. The system of claim 1, wherein the subsystem comprises a third party services subsystem;

5. The system of any of claims 1-4, wherein the subsystem comprises an elevator subsystem, a gas cylinder subsystem, a data statistics subsystem, or a video surveillance subsystem.

6. A terminal comprising a processor and a memory, the memory having stored therein at least one program code, the at least one program code loaded into and executed by the processor to perform the steps of:

7. The terminal of claim 6, wherein the target subsystem is a login authentication subsystem; the at least one program code is loaded into and executed by the processor to perform the steps of:

8. A management method performed by a management system including a gateway, a registry, and a plurality of subsystems, each of the subsystems providing a different type of service, the management method comprising:

9. A management method, performed by a terminal, the management method comprising:

10. A computer-readable storage medium having at least one program code stored therein, the at least one program code being loaded and executed by a processor to implement the management method of claim 9.

11. A computer program product, characterized in that the computer program product comprises computer program code, which is stored in a computer-readable storage medium, from which a processor reads the computer program code, which the processor executes to implement the management method as claimed in claim 9.