CN116016475A

CN116016475A - Data drilling service platform, access method and related equipment

Info

Publication number: CN116016475A
Application number: CN202211098204.4A
Authority: CN
Inventors: 王妙玉; 陈文森; 吴宁泉; 李昌; 周亮
Original assignee: Guangdong Hotata Smart Home Co Ltd
Current assignee: Guangdong Hotata Smart Home Co Ltd
Priority date: 2022-09-08
Filing date: 2022-09-08
Publication date: 2023-04-25

Abstract

The embodiment of the application provides a data drilling service platform, an access method and related equipment, and relates to the technical field of data processing; the platform supports access to a target system, comprising: the WEB front end is configured to display data obtained by accessing the WEB back end and/or the application server; the WEB back end is configured to provide access service for the WEB front end; the application server is respectively configured with interfaces for providing access services for the WEB front end and/or the target system; a login authorization server configured to provide login authorization services to the WEB front-end and/or the target system; the data storage module comprises a first database for caching first data and a second database for storing second data; the first data is associated with a login authorization service; the second data is associated with accessing the service. According to the method and the device, login authorization service, WEB front end, WEB back end and external interface API are respectively developed and deployed, so that risks can be effectively isolated, maintainability is improved, and the problem of high concurrency of target system access is solved.

Description

Data drilling service platform, access method and related equipment

Technical Field

The application relates to the technical field of data processing, in particular to a data drilling service platform, an access method and related equipment.

Background

In order to better carry out data management, standard non-uniform and scattered data can be integrated together to generate standard result data, and then the data is displayed on a WEB visual interface or provided for an external system to be accessed through a data drilling service. If the existing WEB project is developed and deployed to the Tomcat based on the mode of using an SSM framework, the part of requests for external system access can have high concurrency problem, a plurality of machines are required to be deployed for solving the high concurrency problem, but the problem of asynchronous Session login state is caused, and a Session sharing strategy is required to be added for solving the login state problem, so that the whole network is slow in response due to the fact that more bandwidth is easily consumed in implementation based on the prior art, the whole project is very bulky finally, development and debugging are difficult, and project maintainability is low; in addition, if the WEB visualization is problematic, normal access of an external system may be affected, resulting in serious production accidents.

Disclosure of Invention

The embodiment of the application provides a data drilling service platform, an access method and related equipment for solving at least one technical problem. The technical scheme is as follows:

In a first aspect, an embodiment of the present application provides a data drilling service platform, supporting access of a target system; the platform comprises:

the WEB front end is configured to display data obtained by accessing the WEB back end and/or each application server;

a WEB backend configured to provide access services to the WEB front-end;

the application servers are respectively provided with interfaces for providing access services for the WEB front end and/or the target system;

a login authorization server configured to provide login authorization services to the WEB front-end and/or the target system;

the data storage module comprises a first database for caching first data and a second database for storing second data; the first data is associated with the login authorization service; the second data is associated with the access service.

In a possible embodiment, the WEB backend and/or each application server is accessed through an nmginx reverse proxy; each application server is deployed on a different machine.

In a possible embodiment, at least two main bodies in the WEB backend, the at least one application server, the login authorization server and the first database are deployed on the same machine in a combined deployment mode;

Wherein the combined deployment pattern is related to at least one of the following information:

access amount; the method comprises the steps that a main body with lower access quantity and a main body with higher access quantity are combined and deployed on the same machine, and/or at least two main bodies with lower access quantity are combined and deployed on the same machine;

the degree of interaction; the method comprises the steps of deploying a main body combination with frequent interaction on the same machine;

the degree of consumption of bandwidth; and deploying the main body with smaller occupied bandwidth and the main body with larger occupied bandwidth on the same machine, and/or deploying at least two main body with smaller occupied bandwidth on the same machine.

In a possible embodiment, the login authorization server is configured to perform authentication on authentication information carried by the login request when receiving the login request of the WEB front end and/or the target system, and if the authentication is passed, generate a token configured with a valid duration for feedback, and transmit the token and user information determined based on the authentication information to the first database for caching.

In a possible embodiment, the WEB front end is configured to send the token to the WEB backend and/or the application server after obtaining the token, carrying the token in an access request; or after obtaining the token, the target system carries the token in an access request and sends the access request to the application server;

And the WEB back end and/or the application server are/is configured to perform service processing corresponding to the access request if the first database is confirmed to cache the token when the access request is received.

In a possible embodiment, the target system includes a subsystem for performing a target task set by at least one target home device; wherein the target task includes at least one of:

for at least one target home device, drilling service platform synchronization data from the data;

implementing authorization service for at least one target home device through the login authorization server;

accessing an application server, and updating target information of at least one target home device;

responding to a setting event of at least one target household device through the application server;

accessing the application server to obtain a temporary key of at least one target household device;

responding to a request of a third party platform for at least one target household device through the application server;

implementing, by the application server, a message service for at least one target home device;

and triggering at least one target household device in the target scene through the application server.

In a second aspect, an embodiment of the present application provides an access method, which is applied to a WEB front end in the data drilling service platform in the first aspect; the method comprises the following steps:

responding to the access operation of the operation object, carrying a token fed back by the login authorization server in an access request and sending the access request to the WEB back end and/or the application server;

and receiving feedback of the WEB back end and/or the application server for the access request.

In a possible embodiment, the sending the token fed back by the login authorization server to the WEB backend and/or the application server in the access request includes:

the method comprises the steps that an existing first token is carried in an access request and is sent to a WEB back end and/or an application server, if feedback unauthorized information is received, authentication information corresponding to an operation object is carried in a login request and is sent to a login authorization server, and after a second token fed back by the login authorization server is received, the second token is carried in the access request and is sent to the WEB back end and/or the application server again;

the first token and the second token are configured with effective duration, and the token indicates that the WEB front end is unauthorized after the effective duration is over.

In a possible embodiment, the method further comprises at least one of the following steps:

if the access operation is an initial drilling operation implemented for the drillable object, displaying field information and a hierarchical relationship thereof corresponding to the drilling level of the operation in a form of a tree diagram, and/or displaying field information corresponding to each hierarchy in the drilling process in a form of a table;

if the access operation is a downward drilling operation implemented for the drillable object, displaying lower field information of the currently displayed field;

if the access operation is an upward drilling operation implemented for the drillable object, displaying upper field information of the currently displayed field;

and if the access operation is an unfolding operation implemented for the drillable object, displaying field information of all levels of the drillable object in a form of a tree diagram.

In a third aspect, an embodiment of the present application provides an access method, which is applied to a target system supported by the data drilling service platform in the first aspect; the method comprises the following steps:

responding to the access operation of the operation object, carrying a token fed back by the login authorization server in an access request and sending the access request to the application server;

And receiving feedback of the application server for the access request.

In a possible embodiment, the sending the token fed back by the login authorization server to the application server with the access request includes:

the existing third token is carried in an application server in an access request to be sent, if the feedback unauthorized information is received, authentication information corresponding to the operation object is carried in a login request to be sent to a login authorization server, and after a fourth token fed back by the login authorization server is received, the fourth token is carried in the access request to be sent to the application server again;

and the third token and the fourth token are configured with effective duration, and the token indicates that the target system is unauthorized after the effective duration is over.

In a fourth aspect, embodiments of the present application provide an electronic device, where the electronic device includes a memory, a processor, and a computer program stored on the memory, where the processor executes the computer program to implement the steps of the method described in the second aspect.

In a fifth aspect, embodiments of the present application provide a target system, including: an electronic device loaded with a client; the electronic device comprising a memory, a processor and a computer program stored on the memory, characterized in that the processor executes the computer program to carry out the steps of the method according to the third aspect.

In a sixth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the access method provided in the second or third aspect described above.

In a seventh aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements the steps of the access method provided in the second or third aspect described above.

The beneficial effects that technical scheme that this application embodiment provided brought are:

the embodiment of the application provides a data drilling service platform which can support access of a target system; specifically, when data is displayed to the WEB front end or is provided for a target system to access through the data drilling service, the data drilling service can be split into four parts of the WEB front end, the WEB rear end, the login authorization service and the external interface API for development and deployment; the WEB front end is configured to display data obtained by accessing the WEB back end and/or each application server; the WEB back end is configured to provide access service to the WEB front end, namely the WEB back end is provided with business service related to the WEB front end; the application server is configured to provide access services to the WEB front-end and/or the target system through the interface API, i.e. the application server is deployed with business services related to the WEB front-end and/or the target system; the login authorization server is configured to provide login authorization services to the WEB front end and/or the target system; correspondingly, the data drilling service platform also comprises a data storage module, wherein the data storage module comprises a first database for caching first data and a second database for storing second data; wherein the first data is associated with a login authorization service and the second data is associated with an access service. The data drilling service platform provided by the application can effectively isolate risks among various parts, is beneficial to improving the overall robustness and maintainability of upgrading iteration, reduces the consumed bandwidth, improves the response speed of a network, and can also effectively solve the high concurrency problem of target system access.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that are required to be used in the description of the embodiments of the present application will be briefly described below.

Fig. 1 is a schematic architecture diagram of a data drilling service platform according to an embodiment of the present application;

fig. 2 is a schematic architecture diagram of another data drilling service platform according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a data processing flow according to an embodiment of the present disclosure;

FIG. 4 is a schematic flow chart of access through a target system according to an embodiment of the present application;

fig. 5 is a schematic flow chart of access through a WEB front end according to an embodiment of the present application;

fig. 6 is a flow chart of an access method according to an embodiment of the present application;

FIG. 7 is a flowchart illustrating another access method according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Embodiments of the present application are described below with reference to the drawings in the present application. It should be understood that the embodiments described below with reference to the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application, and the technical solutions of the embodiments of the present application are not limited.

As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless expressly stated otherwise, as understood by those skilled in the art. It will be further understood that the terms "comprises" and "comprising," when used in this application, specify the presence of stated features, information, data, steps, operations, elements, and/or components, but do not preclude the presence or addition of other features, information, data, steps, operations, elements, components, and/or groups thereof, all of which may be included in the present application. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. The term "and/or" as used herein indicates that at least one of the items defined by the term, e.g., "a and/or B" may be implemented as "a", or as "B", or as "a and B".

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The embodiment of the application relates to Big data (Big data), which refers to a data set which cannot be captured, managed and processed by a conventional software tool within a certain time range, and is a massive, high-growth-rate and diversified information asset which needs a new processing mode to have stronger decision-making ability, insight discovery ability and flow optimization ability. With the advent of the cloud age, big data has attracted more and more attention, and special techniques are required for big data to effectively process a large amount of data within a tolerant elapsed time. Technologies applicable to big data include massively parallel processing databases, data mining, distributed file systems, distributed databases, cloud computing platforms, the internet, and scalable storage systems.

And more particularly to data warehouse technology (ETL), which is used to describe the process of extracting (extracting), converting (transforming), and loading (loading) data from a source to a destination.

The technical solutions of the embodiments of the present application and technical effects produced by the technical solutions of the present application are described below by describing several exemplary embodiments. It should be noted that the following embodiments may be referred to, or combined with each other, and the description will not be repeated for the same terms, similar features, similar implementation steps, and the like in different embodiments.

As shown in fig. 1, an embodiment of the present application provides a data drilling service platform that supports access by external systems, such as may be provided to a target system for access.

Optionally, a generic interface API may be provided for the target system in embodiments of the present application to support access by the target system to the data drilling service platform.

Alternatively, the target system may be an application or a service part of the data drilling service platform, or may refer to a system independent of the data drilling service platform. In the aspect of adapting to the whole ecological environment of the enterprise, the data drilling service platform can be developed and deployed by users in the enterprise for business processing, and correspondingly, the target system can be a system for users outside the enterprise to apply. At this time, the target system may be regarded as an external system; in a control scenario of a home device, the target system may be an intelligent linked system that jointly manages a plurality of home devices.

The target system may include an electronic device loaded with a client, and a user may operate on the electronic device to access data through the target system.

Specifically, the data drilling service platform may include: the system comprises a WEB front end, a WEB back end, an application server (provided with a public interface API) and a login authorization server.

The WEB front end realizes the visualization of platform data and is configured to display data obtained by accessing the WEB back end and/or each application server. It can be understood that the WEB front end belongs to a website front part, and operates on a browser such as a PC end, a mobile terminal and the like to display the page and the content of the browsed WEB page to a user; if the project is a comprehensive platform for intelligent home, the foreground can comprise a website home page, a user registration and login module, a device connection module, a device control module and the like.

Alternatively, as shown in fig. 2, the WEB front end may be written in Typescript (an open programming language, which is built by adding static type definitions on the basis of JavaScript), and static resource files such as html, js, css and pictures are generated by packing by weback (front-end resource modular management and packing tool) and deployed to a static resource directory under nglnx. Wherein weback is a static module packaging tool for JavaScript applications. When weback processes an application, a dependency graph is built internally, which corresponds to each module required to map to an item, and generates a corresponding static resource file. On the basis, the WEB front end can access the WEB back end and/or each application server through the Nginx reverse proxy. The Reverse Proxy (Reverse Proxy) method refers to a method that a Proxy server receives a connection request on an external network, and then forwards the request to a server on an internal network, and returns a result obtained from the server to a client requesting connection on the external network.

Optionally, the nmginx reverse proxy may also balance the load of each application server based on a series of proxy rules; the proxy rules may include: time-dependent polling allocation, weight-dependent polling allocation, etc. The time polling allocation refers to allocating each request to different application servers one by one according to time sequence. The distribution of the polling according to the weight means that the proportion of the application server receiving the request is the weight proportion of the respective configuration, and the weight is in direct proportion to the access ratio; the proxy rules may be applied in cases where the application server performance is not balanced.

The WEB back end and the WEB front end interact and can be used for data storage and analysis. Optionally, the WEB backend may be developed using a Springboot framework. As shown in fig. 3, the WEB front end may be regarded as a client, and the WEB back end may be regarded as a WEB server; and the client initiates a request to the WEB server, and the WEB server returns response data.

And each application server is configured with a universal interface API, so that the access of the WEB front end and the target system can be supported. Optionally, the number of deployed application servers may be adjusted according to the access volume; the monitoring of the access quantity can be implemented through the cooperation of the Actator component of the Springboot and the target system, and the data analysis can be carried out by combining the access quantity obtained by the Actator component and the target system respectively to determine whether the deployment of the application server needs to be increased or reduced or not so as to reduce the resource consumption while ensuring the response speed; the increase in the number of application servers can effectively promote the ability to receive concurrent requests. Optionally, the application servers may be deployed in a single machine deployment manner, that is, each application server does not belong to a different machine; as shown in fig. 2, the common interface APIs are each deployed on a single machine.

Wherein the login authorization server is configured to provide login authorization services to the WEB front-end and/or the target system. That is, in the embodiment of the present application, the login authorization service is developed and deployed separately. Specifically, in the embodiment of the present application, in order to ensure data security, all requests for acquiring or modifying service data need to be authorized by means of login authentication.

Correspondingly, the data drilling service platform further comprises a data storage module for providing data storage service. In particular, as shown in fig. 3, the data storage module may include a first database and a second database; the first database is used for caching data, and can be implemented by a key-value database, such as a Redis (remote dictionary service) memory database; the cached first data is generated by the login authorization server and can comprise user information UserInfo, token and the like. The second database is for storing second data related to access services, which may be implemented using MySQL database.

The manner of deploying the plurality of deployed machines according to the embodiments of the present application is described below.

In a possible embodiment, regarding each part of the platform, such as the WEB backend, at least one application server, a login authorization server and at least two entities in the first database may be deployed on the same machine in a combined deployment manner; wherein the combined deployment style is related to at least one of the following information:

(1) Access amount; in combining based on the access amount, a principal with a lower access amount may be combined with a principal with a higher access amount, and/or at least two principals with lower access amount may be deployed in combination on the same machine.

Specifically, considering that the access amount of the response required by the login authorization server, the WEB back end and the first database is smaller, the method can adapt to the arrangement of at least two services in a single machine. As shown in fig. 2, the login authorization server and the WEB backend may be located on the same machine; at this time, as the access amount of the response required by the first database when deployed on a single machine is smaller, the machine also has larger response capability and is not utilized, so that one of the application servers and the first database can be deployed in combination.

Optionally, considering that service response time is too long and may affect user experience, a suitable combination may be selected according to the load of a machine and the estimated access amount for each subject. The following illustrates, example 1: considering in a normalization manner, assuming that the load amount of one machine is 1, the access amount of the login authorization server is 0.301, the access amount of the WEB backend is 0.275, the access amount of the first database is 0.32, the access amount of the application server A1 is 0.62, and the access amount of the application server A2 is 0.81; the login authorization server and the WEB back end can be considered to be combined and deployed, and as the combined access quantity of the login authorization server and the WEB back end is 0.576, the access quantity exceeds 50% of the load quantity of one machine, and other main bodies are not selected for combination any more in order to ensure normal operation of the machine; then, when the first database is deployed, the first database and at least one application server can be combined, the current access amount of the first database is 0.32, in order to avoid that the combined access amount exceeds the load amount of the machine, the first database and the application server A1 can be considered to be deployed in a combined way, and the application server A2 is deployed independently; the deployment results may be referred to the framework example shown in fig. 2.

Alternatively, in example 1 above, the access amounts of the different application servers are dynamic, i.e. it is contemplated to combine the first database with any application server.

(2) The degree of interaction; specifically, the interaction degree may be determined based on the total amount of interaction per unit time; when the application scene is the use of household equipment, deducing can be carried out according to a month as a unit time, and the total interaction amount among all the main bodies is analyzed; considering in a normalized manner, the threshold may be set to 0.5, and the subject with the total interaction amount greater than 0.5 is regarded as the subject with frequent interaction, and the subject with less interaction is not greater than 0.5. The following description is made in connection with example 2 shown in table 1 below:

TABLE 1

	Authorized login server	WEB backend	A first database	Application server
					Authorized login server	-	0.12	0.23	0.26
WEB backend	0.12	-	0.007	0.78
					A first database	0.23	0.007	-	0.01
Application server	0.26	0.78	0.01	-

Considering that interaction is needed among the main bodies, when the main bodies with frequent interaction are deployed in a combined mode, the interaction among the machines can be transferred to the interaction of the modules inside the machines, so that the main bodies with frequent interaction are deployed in the same machine in a combined mode, resources consumed by the interaction among the machines can be effectively reduced, and the resource utilization rate is improved. In example 2 described above, the total amount of interaction between the WEB backend and the application server is the largest and greater than the threshold value of 0.5, and the WEB backend and the application server may be combined when they are regarded as a subject of frequent interaction.

Alternatively, in the above example 1, when at least two subjects having a low access amount are considered to be combined, it is found that the access amounts of the login authorization server, the WEB backend, and the first database are all relatively small, so that the combination manner can be considered simultaneously in combination with the case shown in the above example 2, and it is seen from the above example 2 that the first database and the application server interact frequently, so that it can be considered to combine the first database and the application server, and the login authorization server and the WEB backend.

(3) The degree of consumption of bandwidth; specifically, when different combinations of principals are considered for deployment on the same machine, the influence of network bandwidth among principals needs to be considered; in order to effectively ensure the data transmission rate between the main bodies, the main bodies with smaller occupied bandwidth and the main bodies with larger occupied bandwidth can be combined and deployed on the same machine, and/or at least two main bodies with smaller occupied bandwidth are combined and deployed on the same machine, so that the data transmission efficiency between the main bodies is ensured while the network bandwidth is reasonably utilized.

In an embodiment, when considering the combined deployment manner between the principals, at least one item of information of the above-mentioned access amount, interaction degree, and consumption degree of the bandwidth may be referred to. Optionally, considering that the information such as the access amount received by the main body, the interaction degree between the main bodies, the consumption degree of bandwidth and the like in the process of online application of the data drilling platform is dynamic, a main body deployment model can be configured, the situation of each item of information can be monitored in real time, an alarm is given when the situation exceeds the deployment expected situation, and the adjustment of the platform framework is prompted. If the fact that the two currently deployed application servers cannot load the user demands is detected, at least one application server is expanded according to the current access quantity prompt.

The interaction between the various parts of the data drilling service platform is described below in connection with figures 3, 4 and 5.

Specifically, considering that multiple machines may be deployed in the embodiments of the present application, a single sign-on mode of Redis (for example, a single sign-on mode of providing a cache service with a database in another form may also be used).

In the embodiment of the application, the user is supported to access through the target system and also supported to access through the WEB front end, and no matter the user is supported to access through the target system or the WEB front end, when data acquisition or data adjustment is requested, a request carrying authentication information needs to be sent to the login authorization server first, if the login authorization server authenticates the authentication information and passes the authentication, the login authorization server returns a Token with timeliness corresponding to the login request, and information of the Token and the user corresponding to the authentication information is cached in a dis. Alternatively, the authentication information may include an account number and a password of the user login.

When authenticating authentication information, the login authorization server can acquire user data from a MySQL database, and check account numbers and passwords in the authentication information based on the acquired user data.

Optionally, the login authorization server may further provide a registration service, and when the user performs account registration through the WEB front end and/or the target system, the login authorization server may transmit the acquired user data to MySQL for data storage, and generate Token return at the same time, without the WEB front end and/or the target system initiating a login request again.

Then, after the WEB front end obtains the token, the token can be carried in the access request and sent to the WEB back end and/or the application server. Alternatively, a Token may be appended to the request header.

The target system, after obtaining the token, may then send the token to the application server, carrying it in the access request. Alternatively, a Token may be appended to the request header.

When the WEB backend or the application server receives the access request through the interface API, it needs to check whether the Token in the request header is cached in the Redis, if so, refresh the Token expiration time, then continue the service processing of the access request (such as obtaining big data result data from MySQL database, user feedback/investigation related processing, etc.), if not, return 401 (unauthorized) status code.

The Token belongs to temporary and has a time-efficient identification. The login authorization server can synchronously configure effective duration for the login authorization server when the token is generated; the effective duration may be preset or may vary with the service scenario.

Optionally, when the effective duration is a preset duration, after the WEB backend and/or the application server determines that the Redis caches the corresponding Token for the first time, the countdown timer may be triggered to monitor the effective duration of the Token, and in the effective duration, when the WEB backend and/or the application server receives an access request of the corresponding Token, it is not necessary to check whether the Redis caches the Token, which is beneficial to improving response efficiency of the request and reducing consumption of bandwidth.

Optionally, when the effective duration is changed along with the service scene, the token reaches the effective duration when the WEB front end and/or the target system exits from the current login state, and the token is automatically updated to be in a failure state.

Optionally, when the WEB backend and/or the application server determine that the Redis has the corresponding Token cached for the first time, refreshing the expiration time of the Token at the same time, and when the valid duration of the Token is reached, triggering to delete the Token cached in the Redis and the corresponding user information UserInfo.

The following describes specific content that the data drilling service platform supports access by the target system.

In a possible embodiment, the target system may include a subsystem for performing a target task set by at least one target home device; such as different subsystems being responsible for different task modules or different home devices.

Optionally, the target tasks performed by the target system may include at least one of:

task 1: and for at least one target home device, synchronizing data from the data drill service platform.

Specifically, in the continuous data alternation, the target system may not be able to synchronize the data of the target home device in real time, so as to avoid misoperation or resource waste caused by data asynchronization, and the target system may synchronize the data with the data drilling service platform according to the setting during operation. Alternatively, the synchronization data may relate to synchronization from the target system to the data drilling platform, or may relate to synchronization from the data drilling platform to the target system.

Task 2: and implementing authorization service for at least one target household device through the login authorization server.

Specifically, the data drilling service platform can provide authorization service for the target system through logging in the authorization server, and can realize functions of access through an authorization code mode, maintenance of a Token, inquiry of user information UserInfo and the like.

For example, for a target home device (intelligent lock), the target system may manage user information with which the intelligent lock is operated by logging in an authorization server; if a user updates the user information for operating the intelligent lock through the target system, a login authorization server in the data drilling service platform provides service for the target system; it will be appreciated that in this process, the first database interacting with the login authorization server will update the user information synchronously as instructed by the login authorization server.

Task 3: and accessing an application server, and updating target information of at least one target household device.

Specifically, in the interaction between the user and the target system, part of the information fed back by the target system to the user may affect the operation performed by the user, based on which the target system may update the target information of the served target home device by accessing the application server. For example, for an intelligent clothes hanger, weather information fed back to a user by a target system may affect the operation performed by the user on the intelligent clothes hanger, so that the target system may be set to acquire real-time weather information from an application server at regular time, or the application server may be accessed to acquire real-time weather information when the user uses the target system to operate on the intelligent clothes hanger.

Task 4: and responding to the setting event of at least one target household device through the application server.

Specifically, to better adapt to the user's use needs and lifestyle, event responses may be set for the target home devices. If the cleaning robot is started at a preset time point of each day, the cleaning robot can be triggered to complete the cleaning task of the whole house at the corresponding event point by the application server.

Task 5: and accessing the application server to obtain the temporary key of at least one target household device.

Specifically, the target home device may provide temporary management authority to the temporary user in addition to the management authority to the authenticated user. For the intelligent lock, when the user A goes out to business trip and entrusts the user B to enter the house to water the green plant, the user A can apply the temporary key of the intelligent lock to the application server through the target system (with valid time, the temporary key is invalid after the valid time is ended) and provide the temporary key to the user B, so that the user B can open the intelligent lock through the temporary key in the valid time. Optionally, the temporary key is generated by the application server after obtaining the request sent by the target system.

Task 6: and responding to the request of the third party platform for at least one target household device through the application server.

In particular, considering that home devices used by a user may be provided by different merchants, different home devices may be provided by different platforms for application services. In order to better implement the cooperation between home devices provided by different merchants, the application server of the data drilling platform can also respond to the request of the third party platform for at least one target home device. If the intelligent television is on screen, in order to obtain better sound effect, the intelligent television can be used for playing video, and the intelligent sound box can be used for playing audio; at this time, if the intelligent television is a product of a manufacturer a and the intelligent sound box is a product of a manufacturer B, when the user triggers the screen throwing operation, the third party platform serving for the intelligent television can send an audio playing request to an application server associated with the intelligent sound box and serving for the intelligent sound box, so that the application server of the data drilling platform triggers the intelligent sound box and the intelligent television to synchronously play data.

Task 7: and implementing message service for at least one target home device through the application server.

Specifically, for the operation condition of the target home device, the message service can also be implemented through the application server. In a car networking scenario, the application server may calculate, in real time, a distance between a car terminal (user operation device of a target system) and a location of a target home device (intelligent clothes airing machine), and if a travel time required for determining the distance is less than a time required for the intelligent clothes airing machine to complete a current ultraviolet irradiation task, the application server may actively send a message to the car terminal to feed back an operation condition of the intelligent clothes airing machine, prompt a user whether to close or pause the task, so as to avoid that implementation of the ultraviolet irradiation task affects a life travel of the user.

Task 8: and triggering at least one target household device in the target scene through the application server.

Specifically, the user can trigger the target home equipment through the target system under the set target scene. If the indoor light sensation value is lower than the preset threshold value, the lighting device of the intelligent clothes airing machine is turned on or the intelligent lamp is turned on, the application server can receive the environmental parameters reported by the intelligent clothes airing machine or the intelligent lamp in real time, and when the current indoor light sensation value is determined to be lower than the preset threshold value through the environmental parameters, the lighting device of the intelligent clothes airing machine is triggered to be turned on or the intelligent lamp is triggered to be turned on.

The following specifically describes an access method applied to a WEB front end in an embodiment of the present application.

Specifically, as shown in fig. 6, the access method includes the following steps S101 to S102:

step S101: and responding to the access operation of the operation object, carrying the token fed back by the login authorization server in the access request and sending the access request to the WEB back end and/or the application server.

Specifically, in the embodiment of the application, interaction is performed in a single sign-on mode, and when the operation object triggers to access at the WEB front end in a login authorization state, an access request can be directly sent to the background (the WEB back end and/or the application server). The WEB front end is judged whether to be in a login authorization state or not, and judgment can be carried out through a token fed back by a login authorization server.

As shown in fig. 5, in step S101, the token fed back by the login authorization server is carried in the access request and sent to the WEB backend and/or the application server, and the method includes the following step A1:

step A1: and carrying the existing first token in the access request to send to the WEB back end and/or the application server, carrying authentication information corresponding to the operation object in the login request to send to the login authorization server if the feedback unauthorized information is received, and carrying the second token in the access request to send to the WEB back end and/or the application server again after receiving the second token fed back by the login authorization server.

Specifically, whether the first token is in a valid state is judged, the cached token can be obtained from the first database to judge, and if the first token is cached in the first database, the first token can be determined to be in the valid state; if the first token is not cached in the first database, it may be determined that the first token is in a failure state. Optionally, the first database may be configured with a countdown timer, and after the token is cached and the effective duration of the token is calculated by triggering, the relevant data of the token is actively deleted for a corresponding duration. When the WEB backend and/or the application server determine that the first token is in the failure state, unauthorized information (such as a status code 401) will be fed back to the WEB front-end.

Step S102: and receiving feedback of the WEB back end and/or the application server for the access request.

Specifically, as shown in fig. 5, the operation object does not need to perceive the judgment process of login authentication authorization, and the process is completed interactively by the WEB front end, the first database, the WEB back end, the application server and/or the login authorization server; for the operation object, the operation object can sense that the access operation is implemented, and finally, the feedback of the application server and/or the WEB back end for the access request is obtained; when the feedback is received, corresponding response data can be displayed at the WEB front end.

In a possible embodiment, when an operating user uses the WEB front end for access for the first time, the user can log in for access after registration is completed; at this time, when the operation user performs the access operation, the WEB front end prompts the operation user to register, in the process of registering, the WEB front end can directly send a registration request to the login authorization server, and after the login authorization server allocates corresponding account resources, the WEB front end feeds back a token, at this time, the WEB front end completes the operations of registering and logging through the registration request, and can subsequently send an access request to the WEB back end and/or the application server directly based on the token fed back by the login authorization server.

In a possible embodiment, the access method further comprises at least one of the following steps:

step 1: if the access operation is an initial drilling operation implemented for the drillable object, displaying field information and hierarchical relation thereof corresponding to the drilling level of the operation in a form of a tree diagram, and/or displaying field information corresponding to each hierarchy in the drilling process in a form of a table.

Specifically, when the data drilling operation is not displayed, the user performs the drilling operation on a certain drillable object, and because the depths of drillable objects of different drillable objects are different, the user may default to drilling to the end of the drillable depth or drilling to a designated drilling level when performing the initial drilling operation. The data display aiming at the initial drilling operation can comprise two modes, wherein the mode 1 is a result display mode, and particularly, field information with different levels and the hierarchical relationship thereof are displayed on an interface in a form of a tree diagram; the mode 2 is a process display mode, and specifically, field information corresponding to each level in the drilling process is displayed on an interface in a table form.

Step 2: and if the access operation is a downward drilling operation carried out on the drillable object, displaying lower field information of the currently displayed field.

Specifically, the drill-down operation may be implemented in a presentation of the data drill-down, where the user may choose to drill down one or more levels, where appropriate, the underlying field information of the currently displayed field may be displayed at the interface. If the current display field is displayed in the form of a tree diagram, the lower field information is also suitable for being displayed in the form of a tree diagram; if the currently displayed field is displayed in a tabular form, the lower field information is also displayed in a tabular form.

Step 3: and if the access operation is a drill-up operation implemented on the drillable object, displaying upper field information of the currently displayed field.

In particular, the drill-up operation may be performed after responding to at least one drill-down or initial drill-up operation, and the user may choose to drill-up one or more levels and adaptively display upper field information of the currently displayed field at the interface. If the current display field is displayed in the form of a tree diagram, the upper layer field information is also suitable for being displayed in the form of a tree diagram; if the currently displayed field is displayed in a tabular form, the upper layer field information is also displayed in the tabular form.

Step 4: and if the access operation is an unfolding operation implemented for the drillable object, displaying field information of all levels of the drillable object in a form of a tree diagram.

Specifically, the unfolding operation can be implemented in the data drilling display process, and through the operation, a user can intuitively know the number of layers of the drillable object, field information of different layers and the upper-lower relationship among the layers at one time.

Optionally, for the above steps 1-4, corresponding operation controls may be displayed in the WEB front end, for example, a drop-down frame or an interaction area for controlling data drilling may be laid out on the interface, and trigger controls corresponding to the four operations of initial drilling, drill-down, drill-up and expansion are displayed in the drop-down frame or the interaction area.

The above cases of steps 1-4 are illustrated: for example, for the target home equipment A, a user can set the use data for different time and region in a self-defined way to drill; when the data drilling display is carried out, a user can select field information of different levels to display, for example, aiming at a region, the data drilling can carry out data display of upper and lower levels according to the division of administrative areas; for example, when displaying the usage data of Guangdong province, the user may perform a drill-down operation, at which time the interface will further display the usage data of each city in Guangdong province; the user may then further conduct drill down operations on the usage data for the Guangzhou city, and the interface will further display the usage data for the various regions within the Guangzhou city.

The following specifically describes an access method applied to an intelligent system in an embodiment of the present application.

In particular, it is understood that, by access of the target system, it is an operation object to perform an operation on a client included in the target system. As shown in fig. 7, the access method includes the following steps S201 to S202:

step S201: and responding to the access operation of the operation object, carrying the token fed back by the login authorization server in the access request and sending the access request to the application server.

Specifically, in the embodiment of the application, interaction is performed in a single sign-on mode, and when an operation object is accessed through APP trigger of a target system in a sign-on authorized state, an access request can be directly sent to a background (application server). The judgment of whether the target system is in the login authorization state or not can be performed through a token fed back by the login authorization server.

In step S201, the token fed back by the login authorization server is carried in the access request and sent to the application server, which includes the following step B1:

step B1: and carrying the existing third token to the application server in the access request for transmission, carrying authentication information corresponding to the operation object in the login request for transmission to the login authorization server if the feedback unauthorized information is received, and carrying the fourth token to the access request for transmission to the application server again after receiving the fourth token fed back by the login authorization server.

Specifically, whether the third token is in the valid state is judged, the cached token can be obtained from the first database to judge, and if the third token is cached in the first database, the third token can be determined to be in the valid state; if the third token is not cached in the first database, the third token can be determined to be in a failure state. Optionally, the first database may be configured with a countdown timer, and after the token is cached and the effective duration of the token is calculated by triggering, the relevant data of the token is actively deleted for a corresponding duration. Wherein when the application server determines that the third token is in a disabled state, unauthorized information (e.g., state code 401) is fed back to the target system.

Step S202: and receiving feedback of the application server for the access request.

Specifically, as shown in fig. 4, the operation object does not need to perceive a judgment process of login authentication authorization, and the process is completed interactively by the target system, the first database, the application server and/or the login authorization server; what is perceived by an object of operation (e.g., an APP user) is that an access operation is performed, and feedback from the application server for the access request is finally obtained.

In a possible embodiment, when the operating user uses the target system for access for the first time, the user can log in for access after registration is completed; at this time, when the operation user performs the access operation, the target system prompts the operation user to register, in the process of registering, the target system can directly send a registration request to the login authorization server, and after the login authorization server allocates corresponding account resources, the target system feeds back a token, at this time, the target system completes the operations of registering and logging through the registration request, and can subsequently send the access request to the application server directly based on the token fed back by the login authorization server.

It should be noted that, in the optional embodiments of the present application, related data such as related information (e.g., authentication information, user information) and the like, when the embodiments of the present application are applied to specific products or technologies, permission or consent of the use object needs to be obtained, and collection, use and processing of the related data need to comply with related laws and regulations and standards of related countries and regions. That is, in the embodiments of the present application, if data related to the subject is involved, the data needs to be obtained through the subject authorization consent, and in compliance with relevant laws and regulations and standards of the country and region.

The embodiment of the application also provides an access device applied to the WEB front end, which may include: the system comprises a first sending module and a first receiving module.

The first sending module is used for responding to the access operation of the operation object, carrying the token fed back by the login authorization server in the access request and sending the token to the WEB back end and/or the application server; the first receiving module is used for receiving feedback of the WEB back end and/or the application server for the access request.

In a possible embodiment, when the first sending module is configured to send the token fed back by the login authorization server to the WEB backend and/or the application server in the access request, the first sending module is specifically configured to: the method comprises the steps that an existing first token is carried in an access request and is sent to a WEB back end and/or an application server, if feedback unauthorized information is received, authentication information corresponding to an operation object is carried in a login request and is sent to a login authorization server, and after a second token fed back by the login authorization server is received, the second token is carried in the access request and is sent to the WEB back end and/or the application server again; the first token and the second token are configured with effective duration, and the token indicates that the WEB front end is unauthorized after the effective duration is over.

In a possible embodiment, the display module is further configured to perform at least one of the following:

The embodiment of the application also provides a target system for access, wherein the target system comprises an access device, and the target system specifically comprises: a second transmitting module and a second receiving module.

The second sending module is used for responding to the access operation of the operation object, carrying the token fed back by the login authorization server in the access request and sending the access request to the application server; the second receiving module is used for receiving feedback of the application server for the access request.

In a possible embodiment, the second sending module is specifically configured to, when performing sending to the application server the token fed back by the login authorization server in the access request, carry the token: the existing third token is carried in an application server in an access request to be sent, if the feedback unauthorized information is received, authentication information corresponding to the operation object is carried in a login request to be sent to a login authorization server, and after a fourth token fed back by the login authorization server is received, the fourth token is carried in the access request to be sent to the application server again; and the third token and the fourth token are configured with effective duration, and the token indicates that the target system is unauthorized after the effective duration is over.

The apparatus of the embodiments of the present application may perform the method provided by the embodiments of the present application, and implementation principles of the method are similar, and actions performed by each module in the apparatus of each embodiment of the present application correspond to steps in the method of each embodiment of the present application, and detailed functional descriptions of each module of the apparatus may be referred to in the corresponding method shown in the foregoing, which is not repeated herein.

An electronic device is provided in an embodiment of the present application, including a memory, a processor, and a computer program stored on the memory, where the processor executes the computer program to implement steps of an access method.

In an alternative embodiment, there is provided an electronic device, as shown in fig. 8, the electronic device 4000 shown in fig. 8 includes: a processor 4001 and a memory 4003. Wherein the processor 4001 is coupled to the memory 4003, such as via a bus 4002. Optionally, the electronic device 4000 may further comprise a transceiver 4004, the transceiver 4004 may be used for data interaction between the electronic device and other electronic devices, such as transmission of data and/or reception of data, etc. It should be noted that, in practical applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 is not limited to the embodiment of the present application.

The processor 4001 may be a CPU (Central Processing Unit ), general purpose processor, DSP (Digital Signal Processor, data signal processor), ASIC (Application Specific Integrated Circuit ), FPGA (Field Programmable Gate Array, field programmable gate array) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor 4001 may also be a combination that implements computing functionality, e.g., comprising one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

Bus 4002 may include a path to transfer information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus or an EISA (Extended Industry Standard Architecture ) bus, or the like. The bus 4002 can be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 8, but not only one bus or one type of bus.

Memory 4003 may be, but is not limited to, ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, RAM (Random Access Memory ) or other type of dynamic storage device that can store information and instructions, EEPROM (Electrically Erasable Programmable Read Only Memory ), CD-ROM (Compact Disc Read Only Memory, compact disc Read Only Memory) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store a computer program and that can be Read by a computer.

The memory 4003 is used for storing a computer program that executes an embodiment of the present application, and is controlled to be executed by the processor 4001. The processor 4001 is configured to execute a computer program stored in the memory 4003 to realize the steps shown in the foregoing method embodiment.

Among them, electronic devices include, but are not limited to: the terminal is loaded with the WEB front end and the terminal is loaded with the client in the intelligent system.

Embodiments of the present application provide a computer readable storage medium having a computer program stored thereon, where the computer program, when executed by a processor, may implement the steps and corresponding content of the foregoing method embodiments.

The embodiments of the present application also provide a computer program product, which includes a computer program, where the computer program can implement the steps of the foregoing method embodiments and corresponding content when executed by a processor.

The terms "first," "second," "third," "fourth," "1," "2," and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the present application described herein may be implemented in other sequences than those illustrated or otherwise described.

It should be understood that, although the flowcharts of the embodiments of the present application indicate the respective operation steps by arrows, the order of implementation of these steps is not limited to the order indicated by the arrows. In some implementations of embodiments of the present application, the implementation steps in the flowcharts may be performed in other orders as desired, unless explicitly stated herein. Furthermore, some or all of the steps in the flowcharts may include multiple sub-steps or multiple stages based on the actual implementation scenario. Some or all of these sub-steps or phases may be performed at the same time, or each of these sub-steps or phases may be performed at different times, respectively. In the case of different execution time, the execution sequence of the sub-steps or stages may be flexibly configured according to the requirement, which is not limited in the embodiment of the present application.

The foregoing is merely an optional implementation manner of the implementation scenario of the application, and it should be noted that, for those skilled in the art, other similar implementation manners based on the technical ideas of the application are adopted without departing from the technical ideas of the application, and also belong to the protection scope of the embodiments of the application.

Claims

1. A data drilling service platform, characterized in that it supports access of a target system; the platform comprises:

a WEB backend configured to provide access services to the WEB front-end;

2. The data drilling service platform of claim 1, wherein WEB backend and/or application servers are accessed through an nginix reverse proxy; each application server is deployed on a different machine.

3. The data drilling service platform according to claim 1 or 2, wherein at least two of the WEB backend, the at least one application server, the login authorization server and the first database are deployed on the same machine in a combined deployment manner;

4. The data drilling service platform according to claim 1, wherein the login authorization server is configured to authenticate authentication information carried by the login request when receiving the login request of the WEB front end and/or the target system, and if the authentication is passed, generate a token with a valid duration configured correspondingly for feedback, and transmit the token and user information determined based on the authentication information to the first database for caching.

5. The data drilling service platform of claim 4, wherein the WEB front end is configured to send the token to the WEB back end and/or the application server, after obtaining the token, carrying the token in an access request; or after obtaining the token, the target system carries the token in an access request and sends the access request to the application server;

6. The data drilling service platform of claim 1, wherein the target system comprises a subsystem for performing target tasks set by at least one target home device; wherein the target task includes at least one of:

synchronizing data with the data drilling service platform for at least one target home device;

7. An access method, characterized by being applied to a WEB front end in the data drilling service platform according to any one of claims 1-6; the method comprises the following steps:

8. The method according to claim 7, wherein the step of sending the token fed back by the login authorization server to the WEB backend and/or the application server in the access request includes:

9. The method of claim 7, further comprising at least one of the following steps:

10. An access method, characterized by being applied to a target system supported by the data drilling service platform of any one of claims 1-6; the method comprises the following steps:

and receiving feedback of the application server for the access request.

11. The method according to claim 10, wherein the step of sending the token fed back by the login authorization server to the application server with the access request includes:

12. An electronic device comprising a memory, a processor and a computer program stored on the memory, characterized in that the processor executes the computer program to carry out the steps of the method according to any one of claims 7-9.

13. A target system, comprising: an electronic device loaded with a client; the electronic device comprising a memory, a processor and a computer program stored on the memory, characterized in that the processor executes the computer program to carry out the steps of the method according to any one of claims 10-11.

14. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 7-9 or 10-11.

15. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method of any of claims 7-9 or 10-11.