CN114640718B

CN114640718B - Data processing method and device based on data processing system

Info

Publication number: CN114640718B
Application number: CN202210275874.2A
Authority: CN
Inventors: 黄湘龙
Original assignee: Alibaba Cloud Computing Ltd
Current assignee: Alibaba Cloud Computing Ltd
Priority date: 2022-03-18
Filing date: 2022-03-18
Publication date: 2023-06-23
Anticipated expiration: 2042-03-18
Also published as: CN114640718A

Abstract

The application provides a data processing method and device based on a data processing system. The data server may not execute the aforementioned action of "extracting the domain name in the Origin field in the cross-domain data request" to determine whether to allow the data server corresponding to another domain name to provide the data service in a cross-domain manner on the page of the domain name ", and if the data server receives the cross-domain data request forwarded by the gateway, the data server is often allowed to provide the cross-domain data service according to the cross-domain data request, so that the action of" generating the cross-domain data response according to the cross-domain data request and returning the cross-domain data response to the terminal "may be directly executed, and the efficiency of providing the data service to the outside in a cross-domain manner by the data server may be improved. In addition, the workload of workers can be reduced, and the labor cost is reduced. And secondly, the logic of the data service end can be simplified, and the management and maintenance cost of the data service end in the later period can be reduced.

Description

Data processing method and device based on data processing system

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data processing method and apparatus based on a data processing system.

Background

With the rapid development of technology, a browser is used as a main carrier for surfing the internet and watching videos of a terminal. For security reasons, the browser restricts cross-domain data requests initiated from the script. The default security constraint is a homologous policy (name-origin policy), i.e. JavaScript or Cookie can only access content under the same domain, for example, in the case that a user accesses a network resource through a browser, the browser security mechanism requires that the protocol, domain name and port of the resource and the source station must be consistent for normal access. However, these limitations sometimes cause a number of inconveniences and reasonable use is also affected. For example, for large and medium-sized internet integrated websites, because of development and classification of services, multiple domain names exist simultaneously to correspond to different services, and when users normally access the integrated websites by using a browser, there is often a requirement for cross-domain access.

As such, cross-domain access needs to be supported. For example, it is required to support cross-domain requests for a data service or the like from a service end corresponding to one domain name on a page of the other domain name.

Disclosure of Invention

The application shows a data processing method and device based on a data processing system.

In a first aspect, the present application shows a data processing method based on a data processing system, the system comprising: the gateway and at least one data service end are in communication connection, and the method is applied to the gateway and comprises the following steps:

receiving a cross-domain data request sent by a terminal based on a page of a first domain name, wherein the cross-domain data request at least carries a target service interface and the first domain name, and the target service interface comprises: a service interface of the target data service end of the at least one data service end, which is open to the outside, for the data service of the target type provided by the target data service end; the cross-domain data request is used for requesting the target data service end to provide the data service of the target type corresponding to the target service interface based on the page cross-domain of the first domain name;

determining whether the target data service end allows the page based on the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode according to the target service interface and the first domain name;

and under the condition that the page based on the first domain name is allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain manner, forwarding the cross-domain data request to the target data service end.

In a second aspect, the present application shows a data processing method based on a data processing system, the system comprising: the gateway is in communication connection with each data service end, and the method is applied to a target data service end in the at least one data service end and comprises the following steps:

receiving a cross-domain data request sent by the gateway;

the data request of the cross-domain at least carries a target service interface and a first domain name, and the target service interface comprises: a service interface of the target data service end of the at least one data service end, which is open to the outside, for the data service of the target type provided by the target data service end; the cross-domain data request is used for requesting the target data service end to provide the data service of the target type corresponding to the target service interface based on the page cross-domain of the first domain name; the cross-domain data request is sent to the gateway by the terminal based on the page of the first domain name, and is sent to the target data service end under the condition that the gateway determines that the target data service end allows the target data service end to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode according to the target service interface and the first domain name;

Extracting a target service interface in a cross-domain data request;

and generating a data response according to the data processing logic of the data service corresponding to the target service interface.

In a third aspect, the present application shows a data processing apparatus based on a data processing system, the system comprising: the device is applied to the gateway, and comprises:

the first receiving module is configured to receive a cross-domain data request sent by a terminal based on a page of a first domain name, where the cross-domain data request at least carries a target service interface and the first domain name, and the target service interface includes: a service interface of the target data service end of the at least one data service end, which is open to the outside, for the data service of the target type provided by the target data service end; the cross-domain data request is used for requesting the target data service end to provide the data service of the target type corresponding to the target service interface based on the page cross-domain of the first domain name;

the first determining module is used for determining whether the target data service end allows the page based on the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode according to the target service interface and the first domain name;

And the forwarding module is used for forwarding the cross-domain data request to the target data server under the condition that the target data server is allowed to request the cross-domain page based on the first domain name to provide the data service of the target type corresponding to the target service interface.

In a fourth aspect, the present application shows a data processing apparatus based on a data processing system, the system comprising: the device is applied to a target data service end in the at least one data service end, and comprises:

a third receiving module, configured to receive a cross-domain data request sent by the gateway;

The extraction module is used for extracting a target service interface in the cross-domain data request;

and the generation module is used for generating a data response according to the data processing logic of the data service corresponding to the target service interface.

In a fifth aspect, the present application shows an electronic device comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to perform the method as shown in any of the preceding aspects.

In a sixth aspect, the present application shows a non-transitory computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the method as set out in any of the preceding aspects.

In a seventh aspect, the present application shows a computer program product, which, when executed by a processor of an electronic device, enables the electronic device to perform the method as described in any of the preceding aspects.

Compared with the prior art, the application has the following advantages:

in the application, the data service end may not execute the aforementioned action of "extracting the domain name in the Origin field in the cross-domain data request" to determine whether to allow the data service end corresponding to another domain name to provide the data service on the page of the domain name in a cross-domain manner, and if the data service end receives the cross-domain data request forwarded by the gateway, the data service end is often allowed to provide the cross-domain data service according to the cross-domain data request, so that the action of "generating the cross-domain data response according to the cross-domain data request and returning the cross-domain data response to the terminal" can be directly executed, and the efficiency of the data service end to provide the data service to the outside in a cross-domain manner can be improved.

In addition, the data service end can not execute the action of the aforementioned ' extracting the one domain name in the Origin field in the cross-domain data request ', judging whether to allow the data service end corresponding to the other domain name to provide the data service on the page of the one domain name in a cross-domain mode ', so that the ' extracting the one domain name in the Origin field in the cross-domain data request ' can not be configured in the data service end, judging whether to allow the data service end corresponding to the other domain name to provide the data service on the page of the one domain name in a cross-domain mode, and therefore, the workload of workers can be reduced, and the labor cost can be reduced. And secondly, the logic of the data service end can be simplified, the management and maintenance cost of the data service end in the later period can be reduced, and the occupation of system resources (such as storage resources, calculation resources and the like) of the data service end can be reduced, so that the data service end can concentrate more system resources on the aspect of obtaining input data (cross-domain data request), then processing the input data to obtain output data (generating cross-domain data response according to the cross-domain data request) and outputting the output data (returning the cross-domain data response to the terminal), and the concurrency of the data service end can be improved, and the efficiency of providing data service to the outside in a cross-domain manner of the data service end is further improved.

Drawings

FIG. 1 is a block diagram of a data processing system of the present application.

FIG. 2 is a flow chart of steps of a data processing method based on a data processing system of the present application.

FIG. 3 is a flow chart of steps of a data processing method based on a data processing system of the present application.

FIG. 4 is a block diagram of a data processing apparatus based on a data processing system according to the present application.

Fig. 5 is a block diagram of a data processing apparatus based on a data processing system according to the present application.

Fig. 6 is a block diagram of the structure of an apparatus of the present application.

Detailed Description

In order that the above-recited objects, features and advantages of the present application will become more readily apparent, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings.

To support cross-domain access, various schemes such as CORS (Cross Origin Resource Sharing, cross-domain resource sharing) may be employed to achieve cross-domain access.

Taking CORS as an example: under the condition that a service end corresponding to another domain name needs to be requested to provide data service on a page of the domain name in a cross-domain mode, the terminal can add an Origin field into a request head of the cross-domain data request and store the domain name in the Origin field; after receiving the cross-domain data request, the server extracts the one domain name in the Origin field in the cross-domain data request, judges whether to allow the server corresponding to another domain name to provide data service on the page of the one domain name in a cross-domain mode, and generates a cross-domain data response according to the cross-domain data request and returns the cross-domain data response to the terminal under the condition that the server corresponding to the other domain name is allowed to provide data service on the page of the one domain name in a cross-domain mode, so that the purpose that the terminal requests the server corresponding to the other domain name on the page of the one domain name in a cross-domain mode to provide data service is achieved.

The inventors have analyzed the above-described manner and found that the above-described manner has the following problems:

the server needs to perform an action of "extracting the one domain name in the Origin field in the cross-domain data request" to determine whether to allow the server corresponding to another domain name to be requested to provide the data service in a cross-domain manner on the page of the one domain name. The operator needs to configure the function of "extracting the one domain name in the Origin field in the cross-domain data request" in the service side in advance, determine whether to allow the service side corresponding to another domain name to provide the data service on the page of the one domain name (for example, write the one domain name in the Origin field in the data request for extracting the cross-domain in the service side, determine whether to allow the service side corresponding to another domain name to provide the data service on the page of the one domain name in a cross-domain manner), and configure related interfaces, etc., which may cause the logic of the service side to be more complex, have high management maintenance cost for the service side in the later period, and execute the action of "extracting the one domain name in the Origin field in the data request for cross-domain manner, determine whether to allow the service side corresponding to another domain name to provide the data service on the page of the one domain name to provide the data service side, which may occupy system resources (for example, storage resources and computing resources, etc.) of the service side may occupy the system resources of the service side, and the service side may not be concentrated on the page of the one domain name to provide the data service side according to the cross-domain data request, thereby reducing the efficiency of the data request for the service side.

Secondly, in the scenario of the distributed system, the distributed system includes a plurality of service ends, and a worker configures the function of "extracting the one domain name in the Origin field in the cross-domain data request" in each service end in the distributed system in advance, and judges whether to allow the service end corresponding to another domain name to be requested on the page of the one domain name in a cross-domain manner to provide data service "respectively, so that the workload of the worker is increased. In addition, the server used in the above manner is often an nmginx server, and the function of "extracting the one domain name in the Origin field in the cross-domain data request" is configured in the server, and judging whether to allow the server corresponding to another domain name to be requested on the page of the one domain name in a cross-domain manner to provide the data service "needs to use command line configuration, so that the configuration complexity is high, the difficulty is high, and the later operation and maintenance cost is high. Resulting in high labor costs.

In view of this, a requirement of "providing data services for terminals across domains at a server of a distributed system" is provided, which improves the efficiency of providing data services to the outside across domains and reduces the labor cost of staff.

In order to improve the efficiency of providing data services to the outside of the service end in a cross-domain manner in the scene that the service end of the distributed system provides data services for the terminal in the cross-domain manner, the inventor finds that in the process of carrying out statistical analysis on the mode:

In the above manner, from the perspective of the server in the distributed system, the server performs the following operations:

the server receives the cross-domain data request, extracts the domain name in the Origin field in the cross-domain data request, and judges whether to allow the server corresponding to another domain name to be requested to provide data service in a cross-domain mode on the page of the domain name. Under the condition that the service end corresponding to the other domain name is allowed to request the cross-domain on the page of the one domain name to provide data service, generating a cross-domain data response according to the cross-domain data request, and returning the cross-domain data response to the terminal.

The actions performed by the server may be divided into two phases, analyzed:

a stage of: the server receives the cross-domain data request, extracts the domain name in the Origin field in the cross-domain data request, and judges whether to allow the server corresponding to another domain name to be requested to provide data service in a cross-domain mode on the page of the domain name.

Another stage: the server generates a cross-domain data response according to the cross-domain data request, and returns the cross-domain data response to the terminal.

The inventor also found that, in the above-mentioned another stage, the actions of "generating a cross-domain data response from a cross-domain data request and returning the cross-domain data response to the terminal" often need to be performed by the server itself. That is, for the server, it is necessary to obtain input data (data request of cross-domain), then process the input data to obtain output data (generate data response of cross-domain according to the data request of cross-domain), and output the output data (return data response of cross-domain to the terminal).

For the "extract the one domain name in the Origin field in the cross-domain data request, the act of determining whether to allow the cross-domain request of the service side corresponding to the other domain name on the page of the one domain name to provide the data service" may not be performed by the service side.

That is, the action of "extracting the one domain name in the Origin field in the cross-domain data request, determining whether to allow the service side corresponding to another domain name to be requested to provide the data service cross-domain on the page of the one domain name" is not necessarily performed by the service side.

In view of this, the inventors contemplate that "logic to extract the one domain name in the Origin field in the cross-domain data request, logic to determine whether to allow the data service to be provided by the service side corresponding to another domain name to be requested cross-domain on the page of the one domain name" may be decoupled from the service side.

Therefore, the function of extracting the domain name in the Origin field in the cross-domain data request and judging whether to allow the cross-domain request of the service end corresponding to the other domain name to provide the data service on the page of the domain name can be omitted from the service end, so that the workload of staff can be reduced, and the labor cost can be reduced.

And secondly, due to decoupling, the logic of the server can be simplified, the management and maintenance cost of the server in the later period can be reduced, and the occupation of system resources (such as storage resources, computing resources and the like) of the server can be reduced, so that the server can centralize more system resources to obtain input data (cross-domain data requests), then process the input data to obtain output data (cross-domain data responses are generated according to the cross-domain data requests), and output the output data (the cross-domain data responses are returned to the terminal), and the concurrency of the server can be improved, and the efficiency of the server for providing data services outside the cross-domain area can be further improved.

In order to decouple the logic of "extracting the one domain name in the Origin field in the cross-domain data request" from the service side, determining whether to allow the service side corresponding to another domain name to be requested cross-domain on the page of the one domain name, the inventor found that the logic of "extracting the one domain name in the Origin field in the cross-domain data request, determining whether to allow the service side corresponding to another domain name to be requested cross-domain on the page of the one domain name" is in the order of "get input data (cross-domain data request), then process the input data to obtain output data (generate a cross-domain data response from the cross-domain data request), and output the output data (return the cross-domain data response to the terminal)".

That is, the method includes the steps of firstly executing the action of "extracting the one domain name in the Origin field in the cross-domain data request, judging whether to allow the service end corresponding to another domain name to provide data service in a cross-domain manner on the page of the one domain name", then executing the action of "obtaining input data (the cross-domain data request), then processing the input data to obtain output data (generating a cross-domain data response according to the cross-domain data request), and outputting the output data (returning the cross-domain data response to the terminal)".

In view of this, the inventors contemplate setting up middleware, such as a gateway or the like, at a logical level between an application program and a server side of a distributed system.

The gateway may be configured with a function of "extracting the one domain name in the Origin field in the cross-domain data request, determining whether to allow the service terminal corresponding to another domain name to provide the data service in a cross-domain manner on the page of the one domain name", that is, configured with a logic of "extracting the one domain name in the Origin field in the cross-domain data request, determining whether to allow the service terminal corresponding to another domain name to provide the data service in a cross-domain manner on the page of the one domain name", so that the gateway may perform an action of "extracting the one domain name in the Origin field in the cross-domain data request, determining whether to allow the service terminal corresponding to another domain name to provide the data service in a cross-domain manner on the page of the one domain name".

With particular reference to FIG. 1, there is shown a block diagram of a data processing system of the present application, the system comprising:

the terminal 01 and the distributed system comprise at least one gateway 02 and at least one data server 03.

The terminal is in communication connection with each gateway, and data interaction can be carried out between the terminal and each gateway.

Each gateway is respectively connected with each data service end in a communication way. Each gateway can perform data interaction with each data server.

The data server has the capability of providing data services to the terminal across domains, for example, the server may generate a data response according to a data request sent by the terminal, and return the data response to the terminal.

The terminal may interact with the data server over a network based on the use of hypertext transfer protocol (Hypertext transferprotocol, HTTP) or hypertext transfer security protocol (Hyper Text Transfer Protocol over SecureSocket Layer, HTTPs).

The gateway can be used as a middleware between the terminal and the data service end, and under the condition that a user uses the page of the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain manner, the gateway can determine whether the target data service end allows the page of the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain manner according to at least the first domain name and the target service interface; under the condition that the page based on the first domain name is allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface, the gateway requests the data service end to provide the data service of the target type corresponding to the target service interface.

The server side can provide a plurality of different kinds of data services to the outside. Each kind of data service has a service interface to the outside, which may include an API (Application Programming Interface, application program interface), etc.

For any kind of data service, the kind of data service has corresponding data processing logic or static resources (such as video, pictures, voice or text, etc.), when the service end provides the kind of data service to the outside, the service end can use the data processing logic corresponding to the kind of data service to process corresponding data, obtain a processing result, and obtain a data response according to the processing result. Wherein the corresponding data may include context information of the user, etc. For the data service of the type, the data service end externally provides the data service of the type with a service interface and the like, and the terminal can request the service end to provide the data service of the type based on the service interface.

The context information of the user may include the location of the user, the occupation of the user, or the preference habits of the user, etc.

Under the condition that the terminal needs to request the service end to provide the data service of the type, the service end can call the data processing logic corresponding to the data service of the type according to the service interface corresponding to the data service of the type provided by the terminal, and process corresponding data based on the data processing logic corresponding to the data service of the type so as to provide the data service of the type for the terminal.

The same is true for each of the other classes of data services.

The data processing logic corresponding to the different kinds of data services may be different. The APIs that are open to the outside for heterogeneous data services may be different.

Specifically, referring to fig. 2, a flow chart of a data processing method based on a data processing system of the present application is shown, where the method is applied to the gateway shown in fig. 1, and the method includes:

in step S101, the receiving terminal sends a cross-domain data request based on a page of a first domain name, where the cross-domain data request at least carries a target service interface and the first domain name, and the target service interface includes: a service interface of the target data service end of the at least one data service end, which is open to the outside, for the data service of the target type provided by the target data service end; the cross-domain data request is used for requesting the target data service end to provide the data service of the target type corresponding to the target service interface based on the page cross-domain of the first domain name.

The domain name of the target data server may be different from the first domain name.

In the application, an application program may be installed in the terminal, the application program may include a browser, etc., the terminal may interact with the gateway through the application program, and the terminal may store service interfaces corresponding to various types of data services provided by the target data service end in advance through the application program. Thus, the terminal can use the application program to request the target data service end to provide the corresponding data service according to the service interface according to the actual demand.

The user may browse the page using the application in the terminal, for example, the user may control the application of the terminal to display the page of the first domain name, in one example, the terminal may obtain the page of the first domain name from the data service end corresponding to the first domain name using the application and display the page of the first domain name in the application, however, in the case that the application displays the page of the first domain name, some data services provided by the target data service end corresponding to the second domain name may need to be shared in the page of the first domain name, for example, an image, a video, or an audio provided by the target data service end corresponding to the second domain name is displayed in the page of the first domain name.

In this case, the cross-domain access is involved, so that the target data service end corresponding to the second domain name needs to be requested to provide the data service based on the page of the first domain name in a cross-domain manner, for example, the target data service end needs to be requested to provide the data service of the target type corresponding to the target service interface based on the page of the first domain name in a cross-domain manner.

The data service of the target class is one of a plurality of classes of data services externally provided by the target data service end corresponding to the second domain name, and the target service interface is a service interface for externally developing the data service of the target class. The target data service end corresponding to the second domain name provides a plurality of kinds of data services to the outside, and the service interfaces of the data services open to the outside are different. The first domain name and the second domain name may be different.

Under the condition that the target data service end is required to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode based on the page of the first domain name, the terminal can generate a cross-domain data request, the cross-domain data request at least carries the target service interface and the first domain name, and then step S102 is executed.

In one example, the cross-domain data request may include a cross-domain http request, or the like.

For example, the application program (browser) in the terminal displays a page (home.111.com) of the data service corresponding to the domain name www.111.com, and if an image www.222.com.jpg1 in the data service corresponding to the domain name www.222.com needs to be introduced into the page (home.111.com) of the data service corresponding to the domain name www.111.com, the page (home.111.com) causes the application program (e.g. browser) in the terminal to initiate a cross-domain http request (request to acquire the image www.222.com.jpg1) to the data service corresponding to the domain name www.222.com.

The request header of the cross-domain data request generated by the terminal can include the cross-domain request header.

The cross-domain request header may include a request header in access-control format. The data service side can provide the cross-domain data service only if the data service side is responding to the cross-domain request heads.

In this application, the access-control-formatted request header may include the following fields:

origin field: the Origin field may include a source domain name (e.g., the first domain name in this embodiment, etc.), i.e., it may be noted on which domain name the cross-domain data request originated based.

The gateway may determine whether the request header in the data request includes an Origin field when receiving the data request sent by the terminal, and may execute step S102 when including the Origin field, and may process the data request according to a normal procedure, which will not be described in detail herein, when not including the Origin field, indicating that the received data request is not a cross-domain data request, and may be a normal data request.

In step S102, it is determined, according to the target service interface and the first domain name, whether the target data service end allows the page based on the first domain name to request the target data service end to provide the data service of the target class corresponding to the target service interface in a cross-domain manner.

In one embodiment of the present application, the present step may be implemented by the following procedure, including:

1021. Acquiring a cross-domain name set which is read into a gateway in advance and is at least bound with a target service interface, wherein the cross-domain name set comprises: and supporting a source domain name based on the data service of the target type corresponding to the target service interface, which is requested to be provided by the target data service end in a cross-domain mode.

That is, at least which domain names are included in the cross-domain name set bound with the target service interface, the data service of the target class corresponding to the target service interface is supported by requesting the target data service terminal from the page based on which domain names in a cross-domain manner.

In this application, the gateway may extract the first domain name and the target service interface in the cross-domain data request, obtain the cross-domain name set that has been read into the gateway in advance and is bound to at least the target service interface, and then execute step 1022.

In one embodiment of the present application, any kind of data service that is open to the outside is used for the data service end.

If the function of supporting the "request the data service terminal to provide the data service of the type based on a domain name (which may be different from the domain name of the data service terminal) in a cross-domain manner" needs to be set in advance, a configuration instruction may be set in the gateway, where the configuration instruction carries a service interface of the type of data service that is open to the outside and the domain name, and the setting request is used for setting the function of supporting the "request the data service terminal to provide the data service of the type based on the domain name (which may be different from the domain name of the data service terminal)" in a cross-domain manner; then, the gateway can search a cross-domain name set corresponding to the service interface in a mapping relation between a service interface of which the data service end provides the data service to the outside and a cross-domain name set based on which the data service end is allowed to provide the data service in a cross-domain mode, and then can add the domain name in the searched cross-domain name set.

If the cross-domain name set corresponding to the service interface is not found, a cross-domain name set comprising the domain name can be generated, the service interface and the generated cross-domain name set form a corresponding table entry, and the corresponding table entry is stored in the mapping relation.

The same is true for each of the other kinds of data services for which the server is open to the outside.

With reference to the above manner, if a function of "requesting the target data service end to provide the data service of the target type corresponding to the target service interface based on the first domain name (which may be different from the second domain name of the target data service end)" needs to be configured in advance, a configuration instruction may be set in the gateway, where the configuration instruction carries the target service interface and the first domain name, and the configuration instruction is used to configure the function of "requesting the target data service end to provide the data service of the target type corresponding to the target service interface based on the first domain name (which may be different from the second domain name of the target data service end) in a domain-crossing manner; then, the gateway can search a cross-domain name set corresponding to the target service interface in a mapping relation between a service interface of the data service provided by the target data service end to the outside and a cross-domain name set based on which the data service is allowed to be provided by the target data service end in a cross-domain request mode, and then can add a first domain name in the searched cross-domain name set.

If the cross-domain name set corresponding to the target service interface is not found, a cross-domain name set comprising the first domain name can be generated, the target service interface and the generated cross-domain name set form a corresponding table entry, and the corresponding table entry is stored in the mapping relation.

In one possible manner, when acquiring the configuration instruction, the operator may be supported to manually control the gateway to acquire the configuration instruction by interacting with the gateway, for example, the user may input a configuration operation for configuring the domain name in the gateway (may be a specific button, the user may click the button to implement inputting the configuration operation), and the gateway receives the configuration operation for configuring the domain name in the gateway, where the gateway may learn that the user needs to input the configuration instruction in the gateway when receiving the configuration operation for configuring the domain name in the domain, so the gateway may acquire multiple service interfaces (may be all service interfaces or common partial service interfaces) that are open to the outside and acquire multiple candidate domain names respectively for each kind of data service provided by the target data service end according to the configuration operation. The plurality of candidate domain names include all domain names or partial domain names of vendors to which the target data service end belongs, and the like.

Then, a service interface and a plurality of candidate domain names, which are respectively opened to the outside, of each kind of data service provided by the target data service end to the outside can be displayed; the method comprises the steps of enabling a user to select a target service interface from a plurality of displayed service interfaces, and enabling the user to select a first domain name from a plurality of displayed candidate domain names.

In addition to displaying a plurality of service interfaces and a plurality of candidate domain names on a page of the gateway, a selected button can be displayed, and after a worker inputs a click operation on a displayed target service interface and a click operation on a displayed first domain name, a click operation on the selected button can also be input, so that the selected operation on the target service interface and the first domain name is input in the gateway.

And generating a configuration instruction according to the target service interface and the first domain name under the condition that the gateway at least receives the selected operation of the target service interface in the displayed multiple service interfaces and the first domain name in the displayed multiple candidate domain names.

When the gateway obtains the cross-domain name set which is read into the gateway in advance and is at least bound with the target service interface, the gateway can search the cross-domain name set corresponding to the target service interface in the mapping relation between the service interface of the data service provided by the target data service end to the outside and the cross-domain name set based on which the data service is allowed to be provided by the target data service end in a cross-domain mode.

Further, according to the actual requirement, it may be required to prohibit the page based on the first domain name from cross-domain requesting the target data service end to provide the data service of the target class corresponding to the target service interface, and in the case where the page based on the first domain name is required to prohibit the page based on the first domain name from cross-domain requesting the target data service end to provide the data service of the target class corresponding to the target service interface, a deletion instruction may be set in the gateway, where the deletion instruction carries the target service interface and the first domain name, and the deletion instruction is used to delete the function of "request the target data service end to cross-domain request the target data service end to provide the data service of the target class corresponding to the target service interface" based on the first domain name (which may be different from the second domain name of the target data service end).

Then, the gateway can search a cross-domain name set corresponding to the target service interface in a mapping relation between a service interface of the data service provided by the target data service end to the outside and a cross-domain name set based on which the data service is allowed to be provided by the target data service end in a cross-domain request mode, and then can delete the first domain name in the searched cross-domain name set.

In one possible manner, when acquiring the deletion instruction, the operator may be supported to manually control the gateway to acquire the deletion instruction by interacting with the gateway, for example, the user may input a deletion operation of deleting the domain name across domains in the gateway (may be a specific button, the user may click on the button to implement the deletion operation), and the gateway receives the deletion operation of deleting the domain name across domains input in the gateway, where the gateway may learn that the user needs to input the deletion instruction in the gateway when receiving the deletion operation, so the gateway may acquire a configured service interface supporting that the data service provided by the target data service end across domains is open to the outside according to the deletion operation.

And then displaying a service interface supporting cross-domain request of the target data service end to open to the outside of the data service provided by the outside, so that a user can select a target service interface from the displayed multiple service interfaces.

Under the condition of receiving the selected operation of the target service interface in the displayed service interfaces, acquiring a set domain name on which the data service supporting the cross-domain request of the target service end for providing the target type corresponding to the target service interface is based; for example, in a mapping relationship between a service interface of a data service provided by the target data service end to the outside and a cross-domain name set based on which the target data service end is allowed to be requested to provide the data service in a cross-domain manner, searching a cross-domain name set corresponding to the target service interface, and obtaining a domain name in the searched set.

Displaying domain names based on the data services supporting the cross-domain request of the target service end for providing the target types corresponding to the target service interfaces, so that a user can select a first domain name from the displayed domain names.

The method comprises the steps that a plurality of service interfaces and a plurality of domain names are displayed on a page of a gateway, a selected button can be displayed, and after a worker inputs a click operation on the displayed first domain name, the click operation on the selected button can be input, so that the selection operation of inputting the first domain name in the gateway is realized.

And generating a deleting instruction according to the target service interface and the first domain name under the condition that the gateway receives the selected operation of the first domain name in the displayed multiple domain names.

1022. And under the condition that the first domain name is positioned in the cross-domain name set, the determining end allows the page based on the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode.

In the case that the first domain name is located in the cross-domain name set, it is explained that the function of "requesting the target data service terminal to provide the data service of the target class corresponding to the target service interface based on the first domain name (which may be different from the second domain name of the target data service terminal) in a cross-domain manner" is configured in advance, and thus, the page based on the first domain name is allowed to request the target data service terminal to provide the data service of the target class corresponding to the target service interface in a cross-domain manner.

1023. And under the condition that the first domain name is not positioned in the cross-domain name set, determining that the page based on the first domain name is not allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface.

In the case that the first domain name is not located in the cross-domain name set, a function of "requesting the target data service terminal to provide the data service of the target class corresponding to the target service interface based on the first domain name (which may be different from the second domain name of the target data service terminal) in a cross-domain manner" is not configured in advance, and thus, the page based on the first domain name is not allowed to request the target data service terminal to provide the data service of the target class corresponding to the target service interface in a cross-domain manner.

In step S103, in the case that the page based on the first domain name is allowed to request the target data server to provide the data service of the target class corresponding to the target service interface in a cross-domain manner, forwarding the cross-domain data request to the target data server.

Thus, the target data service end can extract the target service interface in the cross-domain data request, and respond to the cross-domain data request according to the data processing logic of the data service of the target type corresponding to the target service interface.

For example, a data response is generated according to the data processing logic of the data service of the target type corresponding to the target service interface and related information (such as the context information of the user, etc.), the context information may include the occupation, the location, the learning and the hobbies of the user, etc., then the data service may be provided to the user according to the context information of the user, for example, the information of interest of the user is obtained according to the context information of the user, the information of interest of the user is recommended to the user, etc.), so that the data service corresponding to the target service interface is provided for the terminal in a cross-domain manner, further, the data response may be returned to the terminal, and the terminal receives the data response.

Alternatively, in another embodiment, a static resource (such as video, picture, voice or text) corresponding to the target service interface is acquired, a data response is generated according to the acquired static resource, and then the terminal returns a (cross-domain) data response, and the terminal receives the data response.

The response header of the data response generated by the target data server may include a cross-domain response header.

The cross-domain response header may include a response header in access-control format.

In this application, the access-control-formatted response header may include the following fields:

Access-Control-alloy-Origin field: whether the domain name in the Origin field in the data request for responding to the cross-domain can be legally cross-domain.

Access-Control-Request-Method field: a method for indicating allowed use in a cross-domain data request.

Further, in the case that the target data service terminal is not allowed to request the target data service terminal to provide the data service of the target class corresponding to the target service interface in a cross-domain manner based on the page of the first domain name, the cross-domain data request may not be forwarded to the target data service terminal, and further, a failure response may be sent to the terminal, where the failure response is used to indicate that the target data service terminal is not allowed to request the target data service terminal to provide the data service of the target class corresponding to the target service interface in a cross-domain manner based on the page of the first domain name. The terminal is informed that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode, so that the terminal can know that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode, further the user can know that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode, the user is prevented from unaware why the target data service end cannot be provided with the data service of the target type, and further user experience is prevented from being reduced.

In some possible cases, before the terminal sends the cross-domain data request to the target data service end via the gateway, a pre-request may be sent to the gateway first for verifying a cross-domain policy of the target data service end, for example, verifying whether to allow the first domain name-based page to request the target data service end to provide the data service of the target class corresponding to the target service interface in a cross-domain manner, where the first domain name-based page is allowed to request the target data service end to provide the data service of the target class corresponding to the target service interface in a cross-domain manner, and then the terminal requests the target data service end to provide the data service of the target class corresponding to the target service interface in a cross-domain manner based on the first domain name-based page.

For example, the terminal may send a pre-request to the gateway based on the page of the first domain name, where the gateway receives the pre-request sent by the terminal based on the page of the first domain name, where the pre-request carries at least the target service interface and the first domain name, and the pre-request is used to request whether to allow the page based on the first domain name to request the target data server to cross-domain provide the data service of the target class corresponding to the target service interface.

Wherein the pre-request includes a preflight request, etc.

The gateway, after receiving the request, may determine whether the request type is a cross-domain data request, a pre-request, or the like.

And under the condition that the request is determined to be a pre-request, determining whether to allow the page based on the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode according to the target service interface and the first domain name.

For example, referring to the content in step S102, a set of domain names of a cross-domain that have been read into the gateway in advance and bound at least to the target service interface is obtained, where the set of domain names of a cross-domain includes: and supporting a source domain name based on the data service of the target type corresponding to the target service interface, which is requested to be provided by the target data service end in a cross-domain mode. And under the condition that the first domain name is positioned in the cross-domain name set, determining to allow the page based on the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode. And under the condition that the first domain name is not positioned in the cross-domain name set, determining that the page based on the first domain name is not allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface.

And under the condition that the page based on the first domain name is allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain manner, generating an allowed response, and sending the allowed response to the terminal, wherein the allowed response is used for indicating that the page based on the first domain name is allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain manner.

In one example, the pre-request may include an http request or the like, including, for example, an Option request or the like. The request header of the pre-request may also include the pre-request header.

The pre-request header may include a request header in access-control format, including the following fields:

Access-Control-Request-Method field: a method for indicating a request for use in a cross-domain data request.

Access-Control-request-Header field: for indicating http header information used in cross-domain data requests.

Accordingly, the gateway may generate a pre-response (including an allow response, a reject response, etc.) corresponding to the pre-request.

The pre-response header may include the following fields:

Access-Control-Max-Age field: for responding to the pre-responded buffering time.

Access-Control-Allow-Credentials field: for responding to subsequent cross-domain data requests whether a cookie is allowed to be sent.

Access-Control-Allow-Methods field: a request method for allowing use in response to a subsequently transmitted cross-domain data request.

Access-Control-Allow-Headers field: the HTTP header field is used for responding to the subsequently transmitted cross-domain data request and allowing the HTTP header field to be used.

Thus, for the gateway, after receiving the Request, it can look at which resources are included in the Request Header of the Request, and if only the Origin field is included, it can be determined that the Request is a cross-domain data Request, and if the Origin field, the Access-Control-Request-Method field, and the Access-Control-Request-Header field are included, it is determined that the Request is a Request with advance.

Accordingly, the cross-domain data request sent by the receiving terminal based on the page of the first domain name may be the cross-domain data request sent by the receiving terminal according to the permission response and the page of the first domain name.

In another embodiment of the present application, under a condition that the page based on the first domain name is not allowed to cross-domain request that the target data service end provide the data service of the target class corresponding to the target service interface, a rejection response is generated, and the rejection response is sent to the terminal, where the rejection response is used to indicate that the page based on the first domain name is not allowed to cross-domain request that the target data service end provide the data service of the target class corresponding to the target service interface. The terminal is informed of the data service indicating that the target data service end is not allowed to provide the target type corresponding to the target service interface in a cross-domain mode based on the page of the first domain name, so that the terminal can know that the target data service end is not allowed to provide the data service of the target type corresponding to the target service interface in the cross-domain mode based on the page of the first domain name, and further a user can know that the target data service end is not allowed to provide the data service of the target type corresponding to the target service interface in the cross-domain mode based on the page of the first domain name, feedback is conducted on the user, and user experience is prevented from being reduced.

In this application, in some cases, the terminal may directly send a cross-domain data request to the target data server via the gateway, in other cases, the terminal needs to send a pre-request to the gateway first, and after obtaining an permission response returned by the gateway and indicating that the target data server is permitted to request, based on the page of the first domain name, to provide a data service of a target class corresponding to the target service interface, the terminal directly sends the cross-domain data request to the target data server via the gateway.

Under the condition that GET, HEAD or POST is recorded in a Method field in a request header of the request, application/x-www-form-urlencoded, multipart/form-data or text/play is recorded in a Content-Type field in the request header, and a self-defined request header in the request belongs to a set of security headers, the terminal can directly send a cross-domain data request to a target data server through a gateway. Otherwise, the terminal needs to send a pre-request to the gateway, and after obtaining an allowed response returned by the gateway and used for indicating that the target data server is allowed to provide the target type of data service corresponding to the target service interface based on the page request of the first domain name, the terminal directly sends a cross-domain data request to the target data server through the gateway.

The set of security headers includes: accept, accept-Language, content-Language, content-Type, DPR, downlink, save-Data, viewport-Width, etc.

Specifically, referring to fig. 3, a flow chart of a data processing method based on a data processing system of the present application is shown, where the method is applied to a target data server of at least one data server shown in fig. 1, and the method includes:

In step S201, a cross-domain data request sent by the gateway is received;

in step S202, extracting a target service interface in a cross-domain data request;

in step S203, a data response is generated according to the data processing logic of the data service corresponding to the target service interface.

It should be noted that, for the sake of simplicity of description, the method embodiments are all described as a series of combinations of actions, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may take place in other order or simultaneously in accordance with the present application. Further, those skilled in the art will appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts referred to are not necessarily required for the present application.

With reference to FIG. 4, there is shown a block diagram of a data processing apparatus of the present application based on a data processing system, the system comprising: the device is applied to the gateway, and comprises:

the first receiving module 11 is configured to receive a cross-domain data request sent by a terminal based on a page of a first domain name, where the cross-domain data request at least carries a target service interface and the first domain name, and the target service interface includes: a service interface of the target data service end of the at least one data service end, which is open to the outside, for the data service of the target type provided by the target data service end; the cross-domain data request is used for requesting the target data service end to provide the data service of the target type corresponding to the target service interface based on the page cross-domain of the first domain name;

A first determining module 12, configured to determine, according to the target service interface and the first domain name, whether the target data service end allows the page based on the first domain name to request the target data service end to provide a data service of a target class corresponding to the target service interface in a cross-domain manner;

and the forwarding module 13 is configured to forward the cross-domain data request to the target data server under the condition that the target data server is allowed to request the cross-domain page based on the first domain name to provide the data service of the target class corresponding to the target service interface.

In an alternative implementation, the apparatus further includes:

the first sending module is used for sending a failure response to the terminal under the condition that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode, wherein the failure response is used for indicating that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode.

In an alternative implementation, the first determining module includes:

the acquiring unit is configured to acquire a cross-domain name set that has been read into the gateway in advance and is bound to at least the target service interface, where the cross-domain name set includes: supporting a source domain name based on a data service of a target type corresponding to a target service interface provided by a target data service end requested in a cross-domain manner;

The first determining unit is used for determining that the terminal allows the page based on the first domain name to request the target data service terminal to provide the data service of the target type corresponding to the target service interface in a cross-domain mode under the condition that the first domain name is located in the cross-domain name set;

or,

and the second determining unit is used for determining that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode under the condition that the first domain name is not located in the cross-domain name set.

In an alternative implementation, the acquiring unit includes:

the searching subunit is used for searching the cross-domain name set corresponding to the target service interface in the mapping relation between the service interface of the data service provided by the target data service end to the outside and the cross-domain name set based on which the data service is allowed to be provided by the target data service end in a cross-domain request mode.

In an alternative implementation, the acquiring unit further includes:

the first acquisition subunit is used for acquiring a configuration instruction, wherein the configuration instruction carries a target service interface and a first domain name, and the configuration instruction is used for configuring a function of requesting a target data service end to provide a data service of a target type corresponding to the target service interface based on the first domain name in a cross-domain manner;

An adding subunit, configured to find a cross-domain name set corresponding to a target service interface in the mapping relationship; adding a first domain name in the searched cross-domain name set;

or the storage subunit is configured to generate a cross-domain name set including the first domain name if the cross-domain name set corresponding to the target service interface is not found, and form the corresponding table entry by the target service interface and the generated cross-domain name set, and store the corresponding table entry in the mapping relationship.

In an alternative implementation, the first obtaining subunit is specifically configured to:

receiving configuration operation of configuring a cross-domain name input in a gateway;

acquiring a plurality of service interfaces which are respectively open to the outside of each kind of data service provided by the target data service end to the outside according to configuration operation, and acquiring a plurality of candidate domain names;

displaying service interfaces of which the target data service end provides various types of data services to the outside and a plurality of candidate domain names;

and generating a configuration instruction according to the target service interface and the first domain name under the condition that at least the selected operation of the target service interface in the displayed multiple service interfaces and the first domain name in the displayed multiple candidate domain names is received.

In an alternative implementation, the acquiring unit further includes:

the second acquisition subunit is used for acquiring a deleting instruction, wherein the deleting instruction carries a target service interface and a first domain name, and the deleting instruction is used for deleting a function of requesting a target data service end to provide a data service of a target type corresponding to the target service interface in a cross-domain mode based on the first domain name;

the searching subunit is used for searching a cross-domain name set corresponding to the target service interface in the mapping relation;

and the deleting subunit is used for deleting the first domain name in the searched cross-domain name set.

In an alternative implementation, the second obtaining subunit is specifically configured to:

receiving a deleting operation of deleting the cross-domain name input in the gateway;

acquiring a configured service interface supporting the cross-domain request of the data service end to be externally provided and opening the data service according to the deleting operation;

displaying a service interface supporting cross-domain request of opening the data service provided by the target data service end to the outside;

under the condition of receiving the selected operation of the target service interface in the displayed service interfaces, acquiring a set domain name on which the data service supporting the cross-domain request of the target service end for providing the target type corresponding to the target service interface is based;

Displaying a domain name based on a data service supporting a cross-domain request of a target service end to provide a target type corresponding to a target service interface;

In an alternative implementation, the apparatus further includes:

the second receiving module is used for receiving a pre-request sent by the terminal based on the page of the first domain name, wherein the pre-request at least carries a target service interface and the first domain name and is used for requesting whether to allow the page based on the first domain name to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface;

the second determining module is used for determining whether to allow the page based on the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode according to the target service interface and the first domain name;

the second sending module is used for generating an permission response under the condition that the page based on the first domain name is allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode, and sending the permission response to the terminal, wherein the permission response is used for indicating that the page based on the first domain name is allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode;

Accordingly, the second receiving module includes:

and the receiving unit is used for receiving the cross-domain data request sent by the terminal according to the permission response and the page of the first domain name.

In an alternative implementation, the apparatus further includes:

and the third sending module is used for generating a rejection response and sending the rejection response to the terminal under the condition that the page based on the first domain name is not allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface, wherein the rejection response is used for indicating that the page based on the first domain name is not allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface.

With reference to FIG. 5, there is shown a block diagram of a data processing apparatus of the present application based on a data processing system, the system comprising: the device is applied to a target data service end in the at least one data service end, and comprises:

a third receiving module 21, configured to receive a cross-domain data request sent by the gateway;

An extracting module 22, configured to extract a target service interface in the cross-domain data request;

the generating module 23 is configured to generate a data response according to the data processing logic of the data service corresponding to the target service interface.

The embodiment of the application also provides a non-volatile readable storage medium, where one or more modules (programs) are stored, where the one or more modules are applied to a device, and the device may be caused to execute instructions (instractions) of each method step in the embodiment of the application.

Embodiments of the present application provide one or more machine-readable media having instructions stored thereon that, when executed by one or more processors, cause an electronic device to perform a method as described in one or more of the above embodiments. In this embodiment of the present application, the electronic device includes a server, a gateway, a sub-device, and the sub-device is a device such as an internet of things device.

Embodiments of the present disclosure may be implemented as an apparatus for performing a desired configuration using any suitable hardware, firmware, software, or any combination thereof, which may include a server (cluster), a terminal device, such as an IoT device, or the like.

Fig. 6 schematically illustrates an example apparatus 1300 that may be used to implement various embodiments described herein.

For one embodiment, fig. 6 illustrates an example apparatus 1300 having one or more processors 1302, a control module (chipset) 1304 coupled to at least one of the processor(s) 1302, a memory 1306 coupled to the control module 1304, a non-volatile memory (NVM)/storage 1308 coupled to the control module 1304, one or more input/output devices 1310 coupled to the control module 1304, and a network interface 1312 coupled to the control module 1304.

The processor 1302 may include one or more single-core or multi-core processors, and the processor 1302 may include any combination of general-purpose or special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, the apparatus 1300 can be a server device such as a gateway as described in embodiments of the present application.

In some embodiments, the apparatus 1300 may include one or more computer-readable media (e.g., memory 1306 or NVM/storage 1308) having instructions 1314 and one or more processors 1302 combined with the one or more computer-readable media configured to execute the instructions 1314 to implement the modules to perform actions described in this disclosure.

For one embodiment, the control module 1304 may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) 1302 and/or any suitable device or component in communication with the control module 1304.

The control module 1304 may include a memory controller module to provide an interface to the memory 1306. The memory controller modules may be hardware modules, software modules, and/or firmware modules.

Memory 1306 may be used to load and store data and/or instructions 1314 for device 1300, for example. For one embodiment, memory 1306 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, memory 1306 may include double data rate four synchronous dynamic random access memory (DDR 4 SDRAM).

For one embodiment, the control module 1304 may include one or more input/output controllers to provide interfaces to the NVM/storage 1308 and the input/output device(s) 1310.

For example, NVM/storage 1308 may be used to store data and/or instructions 1314. NVM/storage 1308 may include any suitable nonvolatile memory (e.g., flash memory) and/or may include any suitable nonvolatile storage device(s) (e.g., hard disk drive(s) (HDD), compact disk drive(s) (CD) and/or digital versatile disk drive (s)).

NVM/storage 1308 may include storage resources that are physically part of the device on which apparatus 1300 is installed, or may be accessible by the device without necessarily being part of the device. For example, NVM/storage 1308 may be accessed over a network via input/output device(s) 1310.

Input/output device(s) 1310 may provide an interface for apparatus 1300 to communicate with any other suitable device, input/output device 1310 may include a communication component, pinyin component, sensor component, and the like. The network interface 1312 may provide an interface for the device 1300 to communicate over one or more networks, and the device 1300 may communicate wirelessly with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols, such as accessing a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G, 5G, etc., or a combination thereof.

For one embodiment, at least one of the processor(s) 1302 may be packaged together with logic of one or more controllers (e.g., memory controller modules) of the control module 1304. For one embodiment, at least one of the processor(s) 1302 may be packaged together with logic of one or more controllers of the control module 1304 to form a System In Package (SiP). For one embodiment, at least one of the processor(s) 1302 may be integrated on the same mold as logic of one or more controllers of the control module 1304. For one embodiment, at least one of the processor(s) 1302 may be integrated on the same die with logic of one or more controllers of the control module 1304 to form a system on chip (SoC).

In various embodiments, apparatus 1300 may be, but is not limited to being: a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.), among other terminal devices. In various embodiments, the apparatus 1300 may have more or fewer components and/or different architectures. For example, in some embodiments, apparatus 1300 includes one or more cameras, a keyboard, a Liquid Crystal Display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an Application Specific Integrated Circuit (ASIC), and a speaker.

The embodiment of the application provides electronic equipment, which comprises: one or more processors; and one or more machine readable media having instructions stored thereon, which when executed by the one or more processors, cause the electronic device to perform the method as described in one or more of the present application.

For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.

In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable information processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable information processing terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable information processing terminal apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable information processing terminal device to cause a series of operational steps to be performed on the computer or other programmable terminal device to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal device provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present embodiments have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the application.

Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.

The foregoing has described in detail the data processing method and apparatus based on a data processing system provided in the present application, and specific examples have been applied herein to illustrate the principles and embodiments of the present application, where the foregoing examples are provided only to assist in understanding the method and core idea of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.

Claims

1. A data processing method based on a data processing system, the system comprising: the gateway and at least one data service end are in communication connection, and the method is applied to the gateway and comprises the following steps:

2. The method according to claim 1, wherein the method further comprises:

and under the condition that the page based on the first domain name is not allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface, sending a failure response to the terminal, wherein the failure response is used for indicating that the page based on the first domain name is not allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface.

3. The method of claim 1, wherein the determining, according to the target service interface and the first domain name, whether the target data service terminal allows the page based on the first domain name to request the target data service terminal to provide the data service of the target class corresponding to the target service interface in a cross-domain manner includes:

acquiring a cross-domain name set which is read into a gateway in advance and is at least bound with a target service interface, wherein the cross-domain name set comprises: supporting a source domain name based on a data service of a target type corresponding to a target service interface provided by a target data service end requested in a cross-domain manner;

under the condition that the first domain name is positioned in the cross-domain name set, the determining end allows a page based on the first domain name to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode;

Or,

and under the condition that the first domain name is not positioned in the cross-domain name set, determining that the page based on the first domain name is not allowed to cross-domain request the target data service end to provide the data service of the target type corresponding to the target service interface.

4. A method according to claim 3, wherein the obtaining a set of cross-domain names that have been read into the gateway in advance, at least bound to the target service interface, comprises:

and searching a cross-domain name set corresponding to the target service interface in a mapping relation between a service interface of which the data service provided by the target data service end externally is open to the outside and the cross-domain name set based on which the target data service end is allowed to be requested to provide the data service in a cross-domain mode.

5. The method according to claim 4, wherein the method further comprises:

acquiring a configuration instruction, wherein the configuration instruction carries a target service interface and a first domain name, and the configuration instruction is used for configuring a function of requesting a target data service end to provide a data service of a target type corresponding to the target service interface based on the first domain name in a cross-domain manner;

searching a cross-domain name set corresponding to a target service interface in the mapping relation; adding a first domain name in the searched cross-domain name set;

Or if the cross-domain name set corresponding to the target service interface is not found, generating a cross-domain name set comprising the first domain name, forming a corresponding table entry by the target service interface and the generated cross-domain name set, and storing the corresponding table entry in the mapping relation.

6. The method of claim 5, wherein the acquiring the configuration instruction comprises:

7. The method according to claim 4, wherein the method further comprises:

acquiring a deleting instruction, wherein the deleting instruction carries a target service interface and a first domain name, and the deleting instruction is used for deleting a function of requesting a target data service end to provide a data service of a target type corresponding to the target service interface based on the first domain name in a cross-domain manner;

Searching a cross-domain name set corresponding to a target service interface in the mapping relation;

and deleting the first domain name from the searched cross-domain name set.

8. The method of claim 7, wherein the acquiring the delete instruction comprises:

9. The method according to claim 1, wherein the method further comprises:

the method comprises the steps that a receiving terminal sends a pre-request based on a page of a first domain name, wherein the pre-request at least carries a target service interface and the first domain name and is used for requesting whether to allow the page of the first domain name to request a target data service end to provide data services of target types corresponding to the target service interface in a cross-domain mode;

determining whether to allow a page based on a first domain name to request a target data service end to provide data services of a target type corresponding to the target service interface in a cross-domain mode according to the target service interface and the first domain name;

under the condition that the page based on the first domain name is allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain manner, generating an allowed response, and sending the allowed response to the terminal, wherein the allowed response is used for indicating that the page based on the first domain name is allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain manner;

correspondingly, the cross-domain data request sent by the receiving terminal based on the page of the first domain name comprises the following steps:

and the receiving terminal receives a cross-domain data request sent by the page of the first domain name according to the permission response.

10. The method according to claim 9, wherein the method further comprises:

under the condition that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode, generating a rejection response, and sending the rejection response to the terminal, wherein the rejection response is used for indicating that the page based on the first domain name is not allowed to request the target data service end to provide the data service of the target type corresponding to the target service interface in a cross-domain mode.

11. A data processing method based on a data processing system, the system comprising: the gateway is in communication connection with each data service end, and the method is applied to a target data service end in the at least one data service end and comprises the following steps:

receiving a cross-domain data request sent by the gateway;

Extracting a target service interface in a cross-domain data request;

12. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any one of claims 1 to 11 when the program is executed.

13. A computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 11.