CN115733837B - Information processing method, gateway, system and storage medium - Google Patents

Abstract

The embodiment of the application discloses an information processing method, a gateway, a system and a storage medium, wherein the method is applied to an edge gateway and comprises the following steps: determining a sub-account sending out the request information in response to the input request information carrying the authentication information; determining a main account matched with the sub-account; determining primary authentication information associated with the primary account; generating a platform request based on the master authentication information and the request information; and sending the platform request to a platform gateway so that the platform gateway determines a request result matched with the request information. The embodiment of the application can simplify the steps of applying related services on the basis of expanding the user range of the application capability, and can improve the efficiency of applying related information.

Description

Information processing method, gateway, system and storage medium

Technical Field

The present application relates to the field of Internet of Things, and in particular to an information processing method, gateway, system and storage medium.

Background technique

In the related technologies, IoT card users usually need to use self-developed calling functions or entrust a third-party platform to call related business capabilities on the IoT card capability exposure service platform, which makes the calling process of business capabilities more complicated and the cost of capability calling is higher.

Summary of the invention

In order to solve the above technical problems, the embodiments of the present application provide an information processing method, a gateway, a system and a storage medium, which expand the user scope of application capabilities through sub-accounts that can issue relevant request information; and then on the basis of associating a main account with multiple sub-accounts to achieve flexible calling of application capabilities, the relevant request information is sent to the platform gateway through the edge gateway, which can improve the calling efficiency of relevant business capabilities and reduce the cost required for calling relevant business capabilities.

To achieve the above purpose, the technical solution of this application is implemented as follows:

The present application provides an information processing method, which is applied to an edge gateway. The method includes:

In response to the input request information carrying the sub-authentication information, determining the sub-account that issued the request information;

determining a master account that matches the sub-account;

Determining master authentication information associated with the master account;

generating a platform request based on the primary authentication information and the request information;

The platform request is sent to a platform gateway so that the platform gateway determines a request result that matches the request information.

The present application provides an information processing method, which is applied to a platform gateway. The method includes:

Receive identification information of a target (Application Programming Interface, API) sent by an edge gateway; wherein the target API is an API whose processing time for processing request information is greater than a preset time;

Receiving a platform request sent by the edge gateway;

In a case where the API corresponding to the platform request is the target API, based on the call time carried in the platform request, controlling the target API to generate a request result corresponding to the platform request;

Send the request result to the edge gateway.

An embodiment of the present application provides an edge gateway, comprising: a first processor, a first memory, and a first communication bus; wherein the first communication bus is used to implement a communication connection between the first processor and the first memory;

The first processor is used to execute the program in the first memory to implement the information processing method applied to the edge gateway.

An embodiment of the present application provides a platform gateway, comprising: a second processor, a second memory, and a second communication bus; wherein the second communication bus is used to implement a communication connection between the second processor and the second memory;

The second processor is used to execute the program in the second memory to implement the information processing method applied to the platform gateway.

An embodiment of the present application also provides a computer storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors to implement the above-mentioned information processing method.

An embodiment of the present application also provides an information processing system, including the above-mentioned edge gateway and platform gateway.

The information processing method, gateway, system and storage medium provided by the embodiments of the present application firstly determine the subaccount that issues the request information in response to the input request information carrying sub-authentication information; secondly, determine the main account that matches the subaccount; determine the main authentication information associated with the main account; then, generate a platform request based on the main authentication information and the request information; finally, send the platform request to the platform gateway so that the platform gateway determines the request result that matches the request information. In this way, the user range of application capabilities can be expanded through subaccounts that can issue relevant request information; and then, on the basis of realizing that a main account is associated with multiple subaccounts to realize flexible calling of application capabilities, the relevant request information is sent to the platform gateway through the edge gateway, which can improve the calling efficiency of relevant business capabilities and reduce the cost required for calling relevant business capabilities.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of an information processing method applied to an edge gateway provided in an embodiment of the present application;

FIG2 is a flow chart of another information processing method applied to an edge gateway provided in an embodiment of the present application;

FIG3 is a flow chart of an information processing method applied to a platform gateway provided in an embodiment of the present application;

FIG4 is a schematic diagram of a flow chart of an information processing method provided in an embodiment of the present application;

FIG5 is a schematic diagram of a system structure consisting of an edge gateway and a platform gateway provided by an embodiment of the present application;

FIG6 is a schematic diagram of a process of processing services by a management platform provided in an embodiment of the present application;

FIG7 is a schematic diagram of a process flow of an edge gateway processing service provided in an embodiment of the present application;

FIG8 is a schematic diagram of the structure of an edge gateway provided in an embodiment of the present application;

FIG9 is a schematic diagram of the structure of a platform gateway provided in an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

It should be understood that the "embodiments of the present application" or "the aforementioned embodiments" mentioned throughout the specification mean that specific features, structures or characteristics related to the embodiments are included in at least one embodiment of the present application. Therefore, "in the embodiments of the present application" or "in the aforementioned embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. In the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments.

Unless otherwise specified, the information processing device performs any step in the embodiments of the present application, and the processor of the information processing device may perform the step. It is also worth noting that the embodiments of the present application do not limit the order in which the information processing device performs the following steps. In addition, the methods used to process data in different embodiments may be the same method or different methods. It should also be noted that any step in the embodiments of the present application can be independently executed by the information processing device, that is, when the information processing device executes any step in the following embodiments, it may not rely on the execution of other steps.

In the related technologies, the IoT card capability exposure service platform provides eight capabilities including IoT card management, roaming positioning, terminal control, security protection, business processing, data statistics, artificial intelligence (AI) and exclusive customization. The IoT card capability exposure service platform implements the call of related capabilities through gateway management access authorization, traffic control and back-end routing; among them, when the customer of the IoT card initiates a request to call the API capability, the request first enters the gateway, and is routed to the correct back-end service after passing the gateway's authentication and traffic control. These gateways and back-end services are deployed in the internal business system and provided to customers in the form of RESTFUL interfaces.

At the same time, corporate customers who access the IoT card capability exposure service platform usually use the following three methods to call related business capabilities.

1. Enterprise customers develop a set of API capability calling functions and embed them into internal systems or hardware. According to the API user manual, they assemble the corresponding Uniform Resource Locator (URL) capability request address and parameters, parse the returned results, and implement capability calling.

2. Purchase a third-party platform with integrated API capabilities and entrust card-related services to a third party.

3. Access the corresponding API capabilities through the browser URL address.

Therefore, for corporate customers who are not familiar with API business, self-research and development will greatly increase the investment of manpower and material resources. At the same time, for enterprises that purchase third-party platforms, hosting card-related businesses on third-party platforms makes it impossible to view the records and logs of API calls, making maintenance extremely difficult. Not only does it not reduce the difficulty of calling and maintaining API capabilities, but it increases the complexity of business processes. It is also very inconvenient for small and medium-sized customers who obtain API capabilities through browser URL addresses.

In addition to the above shortcomings, these three situations also have the following defects:

(1) A card-opening customer has only one account for generating authentication information. When the authentication information fails, other sub-accounts under the same account will fail to call the authentication information. When multiple sub-accounts obtain authentication information at the same time, competition is likely to occur, causing the authentication information just obtained by other sub-accounts to become invalid, and bringing pressure on the gateway on the API side to obtain authentication information.

(2) Card-opening customers cannot flexibly use the cards they own, such as group management, that is, assigning cards to different departments. Corporate customers cannot intelligently implement data statistics services using API call capabilities, and must implement them by calling API capabilities, which invisibly increases the customer's calling costs.

(3) The IoT card capability exposure service platform provides some commonly used and time-consuming capabilities to the outside world. Some capabilities have large delays, and the API gateway does not have relevant optimization solutions.

Based on the above problems, an embodiment of the present application provides an information processing method, which is applied to an edge gateway. As shown in FIG1 , the method includes the following steps:

Step 101: In response to an input request message carrying sub-authentication information, determine the sub-account that issued the request message.

In the embodiment of the present application, the edge gateway may be any electronic device with data processing capabilities.

Among them, the edge gateway can be a gateway deployed at the edge of the network, which connects the physical and digital worlds through network connection, protocol conversion and other functions, and provides lightweight connection management, real-time data analysis and application management functions. In the embodiment of the present application, the edge gateway is a device or server that can exchange information with the platform gateway, that is, the API side gateway of the capability exposure platform.

It should be noted that the request information carrying the sub-authentication information may be based on the request information carrying the sub-authentication information input by any client deployed on the edge gateway.

Authentication refers to verifying whether the user has the right to access the system. Accordingly, the sub-authentication information can be text or digital information to verify whether the user has the right to access the relevant gateway or device. At the same time, the request information includes but is not limited to the sub-authentication information, and can also include: the request URL corresponding to the request task, the attribute information of the request task, etc.

In the embodiment of the present application, the sub-account that sends the request information can be the account information of the IoT card, and the sub-account can be the primary card account of the IoT card, i.e., the primary account, or the secondary card account, i.e., the secondary account; wherein the secondary account is subordinate to the primary account. In the following other embodiments of the present application, the sub-account that sends the request information refers to the secondary account.

The request information may be information entered by the staff operating the edge gateway after logging into the relevant client based on the sub-account to apply for calling the relevant API capabilities.

Step 102: Determine a main account that matches the sub-account.

In an embodiment of the present application, the edge gateway determines the main account to which the sub-account belongs, that is, the primary account corresponding to the secondary account; wherein the edge gateway can determine the main account that matches the sub-account based on the internally stored account database; at the same time, the account database can be set by the edge gateway, that is, each main account and its corresponding sub-account are generated or set in advance based on relevant rules.

It should be noted that in the embodiment of the present application, a main account can be associated with at least one sub-account, and a sub-account is subordinate to a unique main account.

Step 103: Determine the master authentication information associated with the master account.

In an embodiment of the present application, the edge gateway obtains the main authentication information associated with the main account; wherein, there is a mapping relationship between the main authentication information and the sub-authentication information; that is, there is a subordinate relationship between the sub-account and the main account, and there is also a mapping relationship between the sub-authentication information and the main authentication information.

The main authentication information may be in any form such as numbers, letters, and graphics, or any combination of the above forms; correspondingly, the composition form of the sub-authentication information may be the same as or different from that of the main authentication information.

It should be noted that the primary authentication information associated with the primary account can be stored in the authentication cache interval inside the edge gateway in real time, that is, when the edge gateway determines the primary account, it searches the authentication cache interval for the primary authentication information associated with the primary account; wherein, the primary authentication information stored in the authentication cache interval can be updated according to a preset period, so as to ensure that the primary authentication information associated with the primary account stored in the cache database of the edge gateway is always real-time and valid, that is, the determined primary authentication information associated with the primary account can be real-time and valid.

Step 104: Generate a platform request based on the primary authentication information and the request information.

In an embodiment of the present application, the edge gateway generates a platform request based on the primary authentication information and the request information; wherein, part of the content in the request information may be adjusted based on the primary authentication information to obtain a platform request for sending to the platform gateway.

Among them, the platform request is the request that needs to be sent to the platform gateway, and the request information is the request information generated by the relevant sub-account based on the edge gateway, that is, the request information is the transit request information of the platform request.

In a feasible implementation, the edge gateway adjusts the sub-authentication information in the request information to the main authentication information, and replaces the edge gateway address in the request information with the platform gateway address, thereby obtaining a platform request for sending to the platform gateway.

It should be noted that the task attributes of the request in the platform request and the request information are the same. For example, if the requested task in the request information is a positioning task, then the requested task in the platform request is also a positioning task.

Step 105: Send the platform request to a platform gateway, so that the platform gateway determines a request result that matches the request information.

In an embodiment of the present application, the edge gateway sends the determined platform request to the platform gateway, so that the platform gateway determines a request result that matches the request information.

In the embodiments of the present application, there is no limitation on the information interaction method between the edge gateway and the platform gateway.

It should be noted that in the embodiment of the present application, the edge gateway determines the main account matching the sub-account and the main authentication information associated with the main account in sequence based on the sub-account that sends the request information; and based on the main authentication information and the request information, generates a platform request sent to the platform gateway, so that the platform gateway determines the request result that matches the request information; in this way, by setting up a sub-account that can send relevant request information, the user range of the application capability can be expanded, that is, on the basis of realizing the association of one main account with multiple sub-accounts to realize the flexible call of the application capability, the relevant request information is sent to the platform gateway through the edge gateway, which can improve the efficiency of sending the request information and reduce the cost of sending the relevant request information.

The information processing method provided by the embodiment of the present application is applied to the edge gateway. First, in response to the input request information carrying sub-authentication information, the sub-account that issues the request information is determined; secondly, the main account that matches the sub-account is determined; the main authentication information associated with the main account is determined; then, based on the main authentication information and the request information, a platform request is generated; finally, the platform request is sent to the platform gateway so that the platform gateway determines the request result that matches the request information. In this way, the user range of the application capability is expanded through the sub-account that can issue relevant request information; and then, on the basis of realizing that a main account is associated with multiple sub-accounts to realize the flexible call of the application capability, the relevant request information is sent to the platform gateway through the edge gateway, which can improve the call efficiency of the relevant business capabilities and reduce the cost required for the call of the relevant business capabilities.

Based on the foregoing embodiments, the embodiments of the present application further provide an information processing method, which is applied to an edge gateway. As shown in FIGS. 1 and 2 , the method includes the following steps:

Step 201: In response to the request information, authenticate the sub-authentication information to obtain an authentication result.

In an embodiment of the present application, the edge gateway responds to the request information, authenticates the sub-authentication information in the request information, that is, verifies it, and obtains an authentication result; wherein the authentication result can be expressed as pass, fail, success or failure, etc.

In a feasible implementation, before the edge gateway executes step 201, that is, before the edge gateway authenticates the sub-authentication information in response to the request information and obtains the authentication result, the following steps A1 and A2 may be executed:

Step A1: In response to the login information input based on the sub-account, generate the sub-authentication information associated with the sub-account.

In an embodiment of the present application, the edge gateway generates sub-authentication information associated with the sub-account in response to login information input based on the sub-account; wherein the sub-authentication information is information that is associated and matched with the sub-account login information in real time.

The sub-authentication information associated with the sub-account may be numbers, numbers and letters, pictures, and other information.

Step A2: Generate the request information in response to the initial request information input based on the sub-authentication information.

In an embodiment of the present application, the edge gateway generates request information in response to the initial request information input based on the sub-authentication information; wherein, the initial request information input based on the sub-authentication information and the sub-authentication information are merged to obtain the request information.

Among them, the initial request information may include but is not limited to: the gateway address corresponding to the request-related service, the name information of the request-related service, the time information of the request-related service, etc.; accordingly, the edge gateway combines the initial request information and the sub-authentication information according to preset rules to obtain the request information.

It should be noted that in the embodiment of the present application, the edge gateway generates corresponding sub-authentication information and request information in response to the login information and initial request information input based on the sub-account in sequence; in this way, the accuracy of the obtained request information can be higher.

Step 202: When the authentication result passes verification, determine that the sub-account associated with the sub-authentication information is the sub-account that issued the request information.

In an embodiment of the present application, when the authentication result is verified, that is, when the authentication result indicates that the sub-authentication information is passed, the edge gateway determines the sub-account associated with the sub-authentication information as the sub-account that issued the request information.

It should be noted that in the embodiment of the present application, the sub-account that issues the request information is determined by authenticating and verifying the sub-authentication information in the request information; in this way, the sub-account that issues the request information can be determined efficiently and accurately.

In a feasible implementation, the edge gateway determines the main account that matches the sub-account, that is, the edge gateway performs step 102 provided in the above embodiment, which can be implemented by the following steps 203:

Step 203: Determine in the account database the main account that matches the sub-account.

The account database at least includes each primary account and a set of accounts associated with each primary account.

In an embodiment of the present application, the edge gateway may pre-set multiple sub-accounts associated with each master account, and store each master account and multiple sub-accounts associated with each master account in the account database of the edge gateway.

It should be noted that the account database not only stores each main account and multiple sub-accounts associated with each main account; correspondingly, it also stores the subordinate relationship between each main account and its corresponding sub-account.

In a feasible implementation method, a management platform can be deployed on the edge gateway in advance, and multiple sub-accounts can be set up and deployed for each main account through the management platform, and then each main account and multiple sub-accounts associated with each main account, that is, the sub-account set, are stored in the account database.

It should be noted that one main account is associated with multiple sub-accounts, and the business functions that can be realized within the multiple sub-accounts can be exactly the same, partially the same, or completely different.

Accordingly, the edge gateway determines the master authentication information associated with the master account, that is, the edge gateway performs step 103 provided in the above embodiment, which can be implemented by the following steps 204:

Step 204: Determine the primary authentication information associated with the primary account in the authentication cache interval.

The authentication cache interval stores the master authentication information associated with each master account.

In an embodiment of the present application, the edge gateway obtains and updates the master authentication information associated with each master account in real time based on an internal related client, such as a management platform, and then stores the updated master authentication information and the corresponding master account in the authentication cache interval.

The edge gateway determines the master authentication information associated with the master account in the authentication cache interval updated in real time based on the acquired master account; each master account is associated with one master authentication information, and the master authentication information is updated over time.

It should be noted that in the embodiment of the present application, the edge gateway determines the main account matching the sub-account and the main authentication information associated with the main account based on the pre-deployed account database and authentication cache interval in turn; in this way, the efficiency and accuracy of determining the main account and the main authentication information can be improved.

In a feasible implementation, the edge gateway generates a platform request based on the primary authentication information and the request information, that is, the edge gateway executes step 104 provided in the above embodiment, which can be implemented by the following steps 205 and 206:

Step 205: Replace the sub-authentication information in the request information with the main authentication information to generate intermediate request information.

In an embodiment of the present application, the edge gateway replaces the sub-authentication information in the request information based on the acquired main authentication information to obtain the intermediate request information.

Step 206: Replace the edge gateway address in the intermediate request information with the platform gateway address, and generate the platform request for sending to the platform gateway.

In an embodiment of the present application, after obtaining the intermediate request information carrying the primary authentication information, the edge gateway replaces the edge gateway address in the intermediate request information with the platform gateway address, and generates a platform request for sending to the platform gateway.

Among them, the edge gateway address is the gateway address generated when the edge gateway obtains the initial request information based on the sub-authentication information, and the gateway address is merged with the initial request information, sub-authentication information, etc. to generate the corresponding request information; that is, the edge gateway address exists in both the request information and the intermediate request information.

It should be noted that in the embodiment of the present application, the edge gateway converts the relevant information in the request information, that is, adjusts the internal authentication information and gateway address to obtain the main request information related to the main account sent to the platform gateway; in this way, the platform gateway can obtain the request that matches the main account, so that the platform gateway can process the request information in a timely manner.

In a feasible implementation, after the edge gateway sends the platform request to the platform gateway so that the platform gateway determines the request result that matches the request information, that is, after the edge gateway executes step 105 or step 206 provided in the above embodiment, the edge gateway may also execute the following steps B1 and B2:

Step B1: Receive the request result sent by the platform gateway.

In an embodiment of the present application, after sending the platform request to the platform gateway, the edge gateway receives a request result sent by the platform gateway in response to the platform request; wherein the request result may be result information corresponding to the platform request.

Step B2: parse the request result to obtain a parsing result, and send the parsing result to the client associated with the sub-account.

In an embodiment of the present application, the edge gateway parses the request result to obtain a corresponding analysis result, and sends the analysis result to an electronic device associated with the sub-account, that is, the analysis result corresponding to the request information issued by the sub-account is fed back to the client associated with the sub-account.

It should be noted that in an embodiment of the present application, the edge gateway can also obtain the request result generated by the platform gateway, and forward the corresponding request result to the client associated with the sub-account; in this way, the relevant business request results can be efficiently and conveniently forwarded to the client that issued the relevant business request, so that the relevant client can execute the relevant business.

In some embodiments, before the edge gateway determines the sub-account that issued the request information in response to the input request information carrying the sub-authentication information, that is, before the edge gateway executes step 101 provided in the above embodiment, it may also execute the following steps C1 and C2:

Step C1: Determine the processing time of each application programming interface API deployed on the platform gateway for processing request information.

In an embodiment of the present application, the edge gateway can also parse and determine in advance the processing time of the request information corresponding to the processing of each API deployed on the platform gateway; wherein, the edge gateway can obtain the processing time of the request corresponding to each API processing through relevant analysis applications.

Step C2: determine the API whose processing time is longer than the preset time as the target API.

In an embodiment of the present application, the edge gateway screens the APIs deployed on the platform gateway based on the processing time, obtains the APIs whose processing time is greater than the preset time, and determines them as the target APIs; wherein the preset time can be determined according to a preset strategy, and the embodiment of the present application does not impose any limitation on this.

Step C3: Send the identification information of the target API to the platform gateway, so that the platform gateway controls the target API to process the corresponding request information in advance.

In an embodiment of the present application, the edge gateway sends the identification information corresponding to the screened target API to the platform gateway, so that the platform gateway controls the target API to process the corresponding request information in advance. In this way, when the request information corresponding to the relevant account application is processed by the target API, the target API can be controlled to be processed in advance, so as to improve processing efficiency and thereby improve user experience.

The information processing method provided in the embodiment of the present application deploys multiple sub-accounts associated with the main account on the edge gateway in advance, and timely updates and obtains the main authentication information associated with the main account, and then authenticates and filters the sub-accounts that issue relevant request information, thereby simplifying the steps of applying for related services on the basis of expanding the user range of application capabilities and improving the efficiency of applying for related information.

The present application also provides an information processing method, which is applied to a platform gateway. As shown in FIG. 3 , the method includes the following steps:

Step 301: Receive identification information of a target API sent by an edge gateway.

The target API is an API whose processing time for processing request information is greater than a preset time.

In an embodiment of the present application, the platform gateway receives identification information of the target API sent by the edge gateway in order to mark the target API, and then when the processing API corresponding to the request information is obtained as the target API, the processing time of the target API is controlled based on a preset strategy.

Step 302: Receive a platform request sent by the edge gateway.

In an embodiment of the present application, the platform gateway receives a platform request sent by the edge gateway to parse the platform request, and then selects a corresponding API from within the platform gateway to process it.

Step 303: When the API corresponding to the platform request is the target API, based on the calling time carried in the platform request, control the target API to generate a request result corresponding to the platform request.

In an embodiment of the present application, when the platform gateway obtains that the API corresponding to the platform request is the target API, it can adjust the time for the target API to process the platform request based on the request processing time carried inside the platform request, that is, the call time carried in the platform request, that is, control the target PAI to generate a request result corresponding to the platform request.

Step 304: Send the request result to the edge gateway.

In an embodiment of the present application, the platform gateway sends the request result to the edge gateway so that the edge gateway forwards the request result to the client associated with the sub-account that issued the request information.

The information processing method provided in the embodiment of the present application is applied to the platform gateway to obtain the identification information and request information of the target API sent by the edge gateway, and when the API corresponding to the request information is the target PAI, the time for the target API to process the platform request is adjusted according to the request processing time inside the platform request; in this way, the request result can be prepared accordingly in combination with the relevant request time, which can reduce the time for the relevant client to obtain the request result, thereby improving the efficiency of processing business.

Based on this, the embodiment of the present application also provides an information processing method, as shown in FIG4 , the method comprises the following steps:

Step 401: The edge gateway determines the processing time of each API processing request information deployed on the platform gateway.

Step 402: The edge gateway determines the API whose processing time is longer than the preset time as the target API.

Step 403: The edge gateway sends the identification information of the target API to the platform gateway, so that the platform gateway controls the target API to process the corresponding request information in advance.

Accordingly, the platform gateway receives the identification information of the target API sent by the edge gateway.

Step 404: The edge gateway generates sub-authentication information associated with the sub-account in response to the login information input based on the sub-account.

Step 405: The edge gateway generates request information based on the initial request information input by the sub-authentication information.

Step 406: The edge gateway authenticates the sub-authentication information in response to the request information to obtain an authentication result.

Step 407: When the authentication result passes verification, the edge gateway determines that the sub-account associated with the sub-authentication information is the sub-account that issued the request information.

Step 408: The edge gateway determines a master account that matches the sub-account in the account database.

Step 409: The edge gateway determines the primary authentication information associated with the primary account in the authentication cache interval.

Step 410: The edge gateway replaces the sub-authentication information in the request information with the main authentication information to generate intermediate request information.

Step 411: The edge gateway replaces the edge gateway address in the intermediate request information with the platform gateway address, and generates a platform request for sending to the platform gateway.

Step 412: The edge gateway sends the platform request to the platform gateway, so that the platform gateway determines the request result that matches the request information.

Accordingly, the platform gateway receives the platform request sent by the edge gateway.

Step 413: When the API corresponding to the platform request is the target API, the platform gateway controls the target API to generate a request result corresponding to the platform request based on the call time carried in the platform request.

Step 414: The platform gateway sends the request result to the edge gateway.

Correspondingly, the edge gateway receives the request result sent by the platform gateway.

Step 415: The edge gateway parses the request result to obtain a parsing result, and sends the parsing result to the client associated with the subaccount.

Based on this, the embodiment of the present application deploys an edge gateway on the platform gateway side, as shown in Figure 5, which is a schematic diagram of the system structure composed of an edge gateway and a platform gateway provided by the embodiment of the present application. Among them, 501 is the edge gateway, that is, the corresponding client side, which can be a client server, and 502 is the platform gateway, that is, the capability exposure platform API side; a management platform and a gateway can be deployed simultaneously on the edge gateway side; wherein, the administrator can create multiple users based on the management platform, use them as secondary accounts on the API side, allocate different numbers of cards to different users, and allocate corresponding card operation permissions to them. The management platform can also provide an operation interface for calling API capabilities, view records and logs of calling API capabilities, perform statistical analysis of call data, disassemble capability call tariff packages, etc.

At the same time, a gateway is deployed on the customer side. The customer can initiate a request to obtain API capabilities through the secondary account created on the management platform. After receiving the request, the gateway authenticates and filters the secondary account, assembles the authentication information, and forwards the request to the API side gateway to obtain the corresponding capabilities.

In addition, a notification receiving function is added to the platform gateway. The API gateway combines the received notification messages, the actual time consumption of API capabilities, the timing of customer calls to API capabilities and other information to analyze the API capabilities that actually take a long time. Based on multiple back-end services (such as back-end service 1, back-end service 2 and back-end service 3 in 502), the data required for the corresponding capabilities is prioritized and the required data is directly returned when the customer calls, saving the waiting time of the customer call.

It should be noted that in the embodiment of the present application, the edge gateway includes the gateway and management platform on the client side in 501, and the data generated by the corresponding processing can be stored in the cache area in 501.

As shown in FIG6 , a flow chart of a management platform processing business provided by an embodiment of the present application is provided; wherein, the management platform can be used by multiple accounts at the same time, and each account can maintain its corresponding business on the management platform. When the execution starts and the system is started, that is, 601 and 602 are executed, the administrator can enter the card-opening customer information, create a system user, maintain the card information, group the card and maintain the system user information, that is, 606 and 607 are executed. During the execution of this step, the primary account and secondary account of the card-opening customer can be stored and maintained, that is, 609 and 610 are executed. At the same time, a scheduled task can be started to obtain the authentication information of the API capability call for the card-opening customer maintained in the system, and the authentication information is saved in the cache, that is, 608, 612 and 611 are executed. In addition, before executing 606 or 608, the management platform can also start another scheduled task to analyze the API capability call behavior and notify the API side gateway of the commonly used and time-consuming API information, that is, 603 to 605. After executing the above steps, the relevant operations can be ended, that is, 613.

It should be noted that when the system user of the management platform clicks the corresponding menu, the underlying layer obtains the authentication information of the card-opening customer to which the user belongs, concatenates the API capability address and call parameters, and initiates an API capability call request to the API side gateway, that is, the platform gateway, to obtain the corresponding API capabilities.

Correspondingly, as shown in FIG7, a schematic diagram of a flow of edge gateway processing services provided by an embodiment of the present application; wherein the edge gateway is the gateway in FIG501 to authenticate and filter the secondary account, assemble the authentication information after passing, forward the request to the API side gateway, and obtain the corresponding capability. wherein, the system is started, first the edge gateway intercepts the request of the customer to call the API capability, that is, executes 701 and 702; secondly, parses the authentication information A corresponding to the secondary account on the management platform side carried in the request; that is, executes 703, corresponding to the sub-authentication information of the sub-account in the embodiment of the present application; again, executes 704, obtains the secondary account information on the management platform side according to the authentication information A, obtains the card opening customer information according to the secondary account, that is, corresponds to the main account in the embodiment of the present application; then obtains the authentication information B on the API side corresponding to the card opening customer from the cache of 708, replaces the authentication information B with the original authentication information A of the customer requesting the API capability, and then forwards the request to the API side gateway, that is, 707, that is, executes 705, and finally returns the result to the customer, that is, executes 706. It should be noted that if an exception occurs during the parsing of the request parameters, the error log is printed in step 709. Finally, the process ends, that is, step 710.

Applied to the information processing method in the embodiment of the present application, the account on the API side gateway (platform gateway) is A (main account), and the corresponding authentication information is A'; the account on the edge gateway side (edge gateway) is B (sub-account), and the corresponding authentication information is B'. Among them, B is the sub-account associated with the A account. When the sub-account B performs a real-time query of the card usage through the edge gateway, the following steps are performed:

In the first step, the secondary account B obtains the authentication information B` through the edge gateway.

Step 2: Customer B initiates a request for "real-time query of card usage".

Step 3: The edge gateway intercepts the request from customer B, authenticates B, and after authentication, parses the requested customer information as B.

Step 4: Find the associated primary account A based on the information in B, and obtain the authentication information A` of the API gateway corresponding to the A account in the cache.

Step 5: The edge gateway assembles the address of the request API gateway and initiates a request to the API gateway.

Step 6: The edge gateway receives the response from the API gateway, processes it appropriately, and returns the processing result to client B.

Based on this, the information processing method provided in the embodiment of the present application deploys a gateway and a management platform on the client side in an edge computing manner, and at the same time uses a secondary account to expand the user range, thereby flexibly managing the card and improving the success rate of capability calls; in addition, the capability call behavior is calculated and analyzed on the client side in the form of edge computing, and notified to the server. The server also increases the customer behavior analysis capability, intelligently discovers customer behavior, and improves customer experience.

It should be noted that, by adding the edge gateway provided in the embodiment of the present application, all API call records or logs can be saved locally on the customer, which is convenient for the customer to view and maintain; at the same time, the client-side gateway has a behavior analysis function for calling API capabilities, analyzes the customer's commonly used and time-consuming API capabilities, and notifies the server; it provides a multi-account form, that is, it introduces a secondary account, avoids competition for authentication information when calling API capabilities, and reduces the pressure on the API-side gateway; in this way, group customers can flexibly use the cards they own, such as grouping cards, that is, assigning cards to different departments, and classifying and managing them; and then they can do data statistics business on the customer side, which reduces the call cost. At the same time, based on the local call data, further statistical analysis can be done, which is conducive to business expansion.

The information processing method provided in the embodiment of the present application is applied to edge gateways and platform gateways. By deploying a set of edge gateways and management platforms that call API capabilities, it can provide customers with API capability services while reducing the pressure on the API-side gateway to call, increase the analysis function of the customer's API capability calls, and notify the API-side gateway of commonly used and time-consuming capabilities; add a monitoring function on the API gateway side, and after receiving the notification, compare and analyze the API capabilities and the customer's notification information, analyze the customer's commonly used and time-consuming API capabilities, and prepare relevant data before the customer calls these capabilities, and directly return the results when the customer calls, thereby reducing customer waiting time and improving customer experience.

Based on the foregoing embodiments, an embodiment of the present application provides an edge gateway 800, which can be applied to the information processing method provided in the embodiments corresponding to FIG. 1 , FIG. 2 , and FIG. 4 . As shown in FIG. 8 , the edge gateway 800 may include: a first processor 810 , a first memory 820 , and a first communication bus 830 ;

The first communication bus 830 is used to realize the communication connection between the first processor 810 and the first memory 820;

The first processor 810 is used to execute the information processing program stored in the first memory 820 to implement the following steps:

In response to the input request information carrying the sub-authentication information, determining the sub-account that issued the request information;

determining a master account that matches the sub-account;

Determining master authentication information associated with the master account;

generating a platform request based on the primary authentication information and the request information;

The platform request is sent to a platform gateway so that the platform gateway determines a request result that matches the request information.

In other embodiments of the present application, the first processor 810 is used to execute the information processing program stored in the first memory 820 in response to the input request information carrying the sub-authentication information, and determine the sub-account that issued the request information based on the sub-authentication information, which can be implemented by the following steps:

In response to the request information, authenticating the sub-authentication information to obtain an authentication result;

In the case where the authentication result passes the verification, the sub-account associated with the sub-authentication information is determined to be the sub-account that issued the request information.

In other embodiments of the present application, the first processor 810 is used to execute the information processing program stored in the first memory 820 in response to the request information, authenticate the sub-authentication information, and before obtaining the authentication result, may further perform the following steps:

generating the sub-authentication information associated with the sub-account in response to login information input based on the sub-account;

The request information is generated in response to initial request information input based on the sub-authentication information.

In other embodiments of the present application, the first processor 810 is used to execute the information processing program stored in the first memory 820 to determine the primary account that matches the account, which can be achieved by the following steps:

In an account database, determining a primary account matching the account; wherein the account database includes at least each primary account and a set of accounts associated with each primary account;

Accordingly, the determining the master authentication information associated with the master account includes:

In the authentication cache interval, the primary authentication information associated with the primary account is determined; wherein the authentication cache interval stores the primary authentication information associated with each primary account.

In other embodiments of the present application, the first processor 810 is used to execute the information processing program stored in the first memory 820 to generate a platform request based on the primary authentication information and the request information, which can be implemented by the following steps:

Replacing the sub-authentication information in the request information with the main authentication information to generate intermediate request information;

The edge gateway address in the intermediate request information is replaced with the platform gateway address to generate the platform request for sending to the platform gateway.

In other embodiments of the present application, the first processor 810 is used to execute the information processing program stored in the first memory 820 to send the platform request to the platform gateway so that the platform gateway determines the request result that matches the request information, and then further perform the following steps:

Receiving the request result sent by the platform gateway;

The request result is parsed to obtain a parsing result, and the parsing result is sent to a client associated with the sub-account.

In other embodiments of the present application, the first processor 810 is used to execute the information processing program stored in the first memory 820 in response to the input request information carrying the sub-authentication information, and before determining the sub-account that issued the request information, the following steps may be performed:

Determine the processing time of each application programming interface API deployed on the platform gateway for processing request information;

The API whose processing time is longer than the preset time is determined as the target API;

The identification information of the target API is sent to the platform gateway, so that the platform gateway controls the target API to process the corresponding request information in advance.

It should be noted that the specific implementation process of the steps executed by the first processor in this embodiment can refer to the implementation process in the information processing method provided in the embodiments corresponding to Figure 1, Figure 2 or Figure 4, and will not be repeated here.

The edge gateway provided in the embodiment of the present application deploys multiple sub-accounts associated with the main account on the edge gateway in advance, and timely updates and obtains the main authentication information associated with the main account, and then authenticates and filters the sub-accounts that issue relevant request information, thereby expanding the user range of application capabilities and simplifying the steps of applying for related services, while improving the efficiency of applying for related information.

Based on the foregoing embodiments, an embodiment of the present application provides a platform gateway 900, which can be applied to the information processing method provided in the embodiments corresponding to FIG. 3 and FIG. 4 . As shown in FIG. 9 , the platform gateway 900 may include: a second processor 910, a second memory 920, and a second communication bus 930;

The second communication bus 930 is used to realize the communication connection between the second processor 910 and the second memory 920;

The second processor 910 is used to execute the information processing program stored in the second memory 920 to implement the following steps:

Receive identification information of a target API sent by an edge gateway; wherein the target API is an API whose processing time for processing request information is greater than a preset time;

Receiving a platform request sent by the edge gateway;

In a case where the API corresponding to the platform request is the target API, based on the call time carried in the platform request, controlling the target API to generate a request result corresponding to the platform request;

Send the request result to the edge gateway.

It should be noted that the specific implementation process of the steps executed by the second processor in this embodiment can refer to the implementation process in the information processing method provided in the corresponding embodiment of Figure 3 or 4, and will not be repeated here.

The platform gateway provided in the embodiment of the present application obtains the identification information and request information of the target API sent by the edge gateway, and when the API corresponding to the request information is the target PAI, adjusts the time for the target API to process the platform request according to the request processing time inside the platform request; in this way, it is possible to prepare the request result accordingly in combination with the relevant request time, which can reduce the time for the relevant client to obtain the request result, thereby improving the efficiency of processing business.

Based on the foregoing embodiments, an embodiment of the present application provides an information processing system, which includes an edge gateway and a platform gateway as provided in the foregoing embodiments.

Based on the foregoing embodiments, the embodiments of the present application also provide a computer storage medium, which stores one or more programs, and the one or more programs can be executed by one or more processors to implement the information processing method provided in the embodiments corresponding to Figures 1 to 4.

It should be noted that the above-mentioned computer-readable storage medium can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc (CD-ROM) and other memories; it can also be various electronic devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

The present application is described with reference to the flowchart and/or block diagram of the method, device (system) and computer program product according to the embodiment of the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, and the combination of the process and/or box in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims (7)

1. An information processing method, characterized in that it is applied to an edge gateway, the method comprising: In response to the input request information carrying the sub-authentication information, determining the sub-account that issued the request information; determining a master account that matches the sub-account; Determining master authentication information associated with the master account; generating a platform request based on the primary authentication information and the request information; Sending the platform request to a platform gateway so that the platform gateway determines a request result that matches the request information; The generating a platform request based on the primary authentication information and the request information includes: Replacing the sub-authentication information in the request information with the main authentication information to generate intermediate request information; Replacing the edge gateway address in the intermediate request information with the platform gateway address, and generating the platform request for sending to the platform gateway; Before determining the subaccount that issued the request information in response to the input request information carrying the sub-authentication information, the method further includes: Determine the processing time of each application programming interface API deployed on the platform gateway for processing request information; The API whose processing time is longer than the preset time is determined as the target API; The identification information of the target API is sent to the platform gateway, so that the platform gateway controls the target API to process the corresponding request information in advance. 2. The method according to claim 1, characterized in that the step of determining the sub-account that issued the request information in response to the input request information carrying the sub-authentication information comprises: In response to the request information, authenticating the sub-authentication information to obtain an authentication result; In the case where the authentication result passes the verification, the sub-account associated with the sub-authentication information is determined to be the sub-account that issued the request information. 3. The method according to claim 2, characterized in that before authenticating the sub-authentication information in response to the request information and obtaining the authentication result, the method further comprises: generating the sub-authentication information associated with the sub-account in response to login information input based on the sub-account; The request information is generated in response to initial request information input based on the sub-authentication information. 4. The method according to claim 1, wherein determining the main account matching the sub-account comprises: In an account database, determining a master account that matches the sub-account; wherein the account database includes at least each master account and a set of sub-accounts associated with each master account; Accordingly, the determining the master authentication information associated with the master account includes: In the authentication cache interval, the primary authentication information associated with the primary account is determined; wherein the authentication cache interval stores the primary authentication information associated with each primary account. 5. The method according to claim 1, characterized in that after sending the platform request to the platform gateway so that the platform gateway determines the request result matching the request information, the method further comprises: Receiving the request result sent by the platform gateway; The request result is parsed to obtain a parsing result, and the parsing result is sent to a client associated with the sub-account. 6. An edge gateway, characterized in that it comprises: a first processor, a first memory and a first communication bus; wherein the first communication bus is used to realize the communication connection between the first processor and the first memory; The first processor is used to execute the program in the first memory to implement the information processing method according to any one of claims 1 to 5. 7. A computer storage medium, characterized in that the computer storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the information processing method according to any one of claims 1 to 5.