Industrial scene multi-terminal heterogeneous data fusion method and system

Abstract

The present invention provides a method and system for multi-terminal heterogeneous data fusion in industrial scenarios, including: step S1: using a gateway server to register context information of a remote service; step S2: configuring the CORS policy of the gateway server; step S3: initiating an HTTP request on the front end based on an encapsulated JS SDK; step S4: the gateway server performs addressing and discovery of the service according to the remote service information, and initiates a call; step S5: after the gateway server obtains the service response data, it encapsulates the response data in a preset format for use by the service caller in the service response callback processing function.

Description

Technical Field

[0001] The present invention relates to the field of remote service call technology, specifically, to a method and system for integrating multi-terminal heterogeneous data in industrial scenarios. More specifically, it relates to a standard client tool that supports industrial scenarios with diverse application servers and non-uniform interactive data structures, and can be widely used for service calls of multi-terminal heterogeneous data. Background Art

[0002] As users' requirements for front-end development increase, the need for an easy-to-use, flexible, and efficient front-end development framework is growing. This is why the Xinrong project was born, aiming to address issues such as complex development technology, difficulty in cross-system display, lack of multi-screen integration capabilities, the inability to separate the front-end and back-end, inconsistent interface styles, and heavy development workload.

[0003] As a front-end framework, the Xinrong project needs to interact with back-end projects for data. To standardize and simplify the remote service call process while ensuring compatibility with diverse business models, service scenarios, and back-end frameworks, it's imperative to develop a standardized, efficient, and flexible client that can access back-end services in diverse industrial scenarios.

[0004] Patent document 107633075A (application number: 201710872072.9) discloses a multi-source heterogeneous data fusion platform and fusion method. The fusion platform includes a data acquisition unit, a data storage unit, a data standardization unit, a user portrait construction unit, a knowledge graph construction unit and a visualization unit; the data acquisition unit is used to collect multi-source heterogeneous data; the data storage unit is used to cache multi-source heterogeneous data; the data standardization unit performs lexical, grammatical and / or semantic analysis on multi-source heterogeneous data to obtain standardized text data; the user portrait construction unit uses quantified student labels to construct student user portraits; the knowledge graph construction unit constructs student knowledge graphs, teacher knowledge graphs and course knowledge graphs, and associates the course knowledge graphs, student knowledge graphs and teacher knowledge graphs to obtain student-centered course connections, social relationships and teacher-student relationships; the visualization unit displays student-centered course connections, social relationships and teacher-student relationships.

[0005] Common remote service call methods include RPC (Remote Produce Call) and REST. The former uses TCP as the underlying transmission protocol, which is fast and efficient. The latter, HTTP, is an application layer protocol that specifies the request format, response format, resource location, and operation methods for network transmission. Because the Xinrong platform needs to be applied in various industrial scenarios, it requires encapsulation at the API level. The RPC method, which limits development languages, was eliminated, and the cross-language, cross-platform HTTP protocol was adopted as the remote call standard for unified client tools. Summary of the Invention

[0006] In response to the shortcomings of the prior art, the present invention aims to provide a method and system for merging multi-terminal heterogeneous data in industrial scenarios, thereby enabling front-end applications to call back-end heterogeneous data services in a unified manner.

[0007] According to the present invention, a method for fusing multi-terminal heterogeneous data in an industrial scenario includes:

[0008] Step S1: registering the context information of the remote service with the gateway server;

[0009] Step S2: Configure the CORS policy of the gateway server;

[0010] Step S3: Initiate an HTTP request on the front end based on the encapsulated JS SDK;

[0011] Step S4: The gateway server performs addressing discovery service according to the remote service context information and initiates a call;

[0012] Step S5: After obtaining the service response data, the gateway server encapsulates the response data according to a preset format for use by the service caller in the service response callback processing function.

[0013] Preferably, the context information of the remote service includes: a unique identifier of the server application, a unique identifier of the remote service, a service protocol type, and a service target address;

[0014] The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier;

[0015] The unique identifier of the remote service indicates the name of the backend service to be called;

[0016] The service protocol type is the protocol used by the backend service, including HTTP and TCP;

[0017] The service target address is the IP address and port number of the host where the backend service is located.

[0018] Preferably, the CORS policy includes:

[0019] Access-Control-Allow-Origin: Allows the specified IP to access the domain;

[0020] Access-Control-Max-Age: indicates that the cross-origin access rights of the current request do not need to be repeatedly verified within the preset time;

[0021] Access-Control-Allow-Methods: indicates the HTTP methods allowed for cross-origin requests, including GET, POST, PUT, and DELETE;

[0022] Access-Control-Allow-Headers: indicates the header information allowed in the access request.

[0023] Preferably, the step S3 adopts: initiating an HTTP request on the front end based on the encapsulated JS SDK, the request parameters including the unique identifier of the server application, the unique identifier of the remote service, the service request parameters and the service response callback processing function;

[0024] The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier;

[0025] The unique identifier of the remote service indicates the name of the backend service to be called;

[0026] The service request parameter is a JSON structure with a unified structure, including a data area, a standard attribute area and an extended data area;

[0027] The response callback function is the business code for processing the data returned by the backend. Custom operations are performed in the callback function for the data returned by different projects and different backends, and JSON data in the same format as the request parameters is returned.

[0028] Preferably, the step S4 adopts: the gateway server performs addressing and discovery service according to the unique identifier of the server application and the unique identifier of the remote service, converts according to the service protocol type, and initiates a call in accordance with the protocol of the service provider.

[0029] Preferably, the gateway server performs addressing discovery service according to the unique identifier of the server application and the unique identifier of the remote service: obtaining the full element information of the remote service according to the unique identifier of the server application and the unique identifier of the remote service;

[0030] The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to parse the parameters of the organization front-end HTTP request and initiate a service call.

[0031] Preferably, the step S5 adopts: after the gateway server obtains the service response data, it encapsulates the response data in a fixed JSON format for use by the service caller in the service response callback processing function;

[0032] Service response data encapsulation means that the gateway server places the service call results in the data area of ​​a unified JSON structure, and sets the service request status code and call prompt information in the standard attribute area.

[0033] According to the present invention, a multi-terminal heterogeneous data fusion system for industrial scenarios includes:

[0034] Module M1: Registering remote service context information using the gateway server;

[0035] Module M2: Configure the CORS policy of the gateway server;

[0036] Module M3: Initiates HTTP requests on the front end based on the encapsulated JS SDK;

[0037] Module M4: The gateway server performs addressing and discovery services based on the remote service context information and initiates a call;

[0038] Module M5: After the gateway server obtains the service response data, it encapsulates the response data according to a preset format for use by the service caller in the service response callback processing function.

[0039] Preferably, the context information of the remote service includes: a unique identifier of the server application, a unique identifier of the remote service, a service protocol type, and a service target address;

[0040] The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier;

[0041] The unique identifier of the remote service indicates the name of the backend service to be called;

[0042] The service protocol type is the protocol used by the backend service, including HTTP and TCP;

[0043] The service target address is the IP address and port number of the host where the backend service is located.

[0044] Preferably, the CORS policy includes:

[0045] Access-Control-Allow-Origin: Allows the specified IP to access the domain;

[0046] Access-Control-Max-Age: indicates that the cross-origin access rights of the current request do not need to be repeatedly verified within the preset time;

[0047] Access-Control-Allow-Methods: indicates the HTTP methods allowed for cross-origin requests, including GET, POST, PUT, and DELETE;

[0048] Access-Control-Allow-Headers: indicates the header information allowed in the access request. Compared with the existing technology, the present invention has the following advantages:

[0049] 1. This invention adopts a standardized remote service calling method, which solves the shortcomings of traditional service calling methods such as confusion and complex parameters when dealing with various types of industrial heterogeneous data services. It effectively improves the efficiency of service calling during the development process and uses gateway technology to integrate and convert the potential value of heterogeneous user trial data.

[0050] 2. The present invention enables secure operation of data resources, provides convenient operation, and personalized processing of heterogeneous server-side data;

[0051] 3. This invention aims to build a unified and standardized client for heterogeneous data structures and diverse server development frameworks in different projects, and specifies a set of usage standards to meet the needs of different industrial scenarios;

[0052] 4. The heterogeneous data fusion method provided by the present invention performs unified registration for services of different protocol types, simplifies the front-end application calling method, and the front-end application can uniformly use the HTTP protocol to request back-end services of different protocols;

[0053] 5. This invention encapsulates the standard JS SDK, and the service calling method is simple and unified, and the way of processing service responses is also unified;

[0054] 6. The protocol conversion capability of the gateway server in the present invention is open and scalable, and can meet the communication protocols such as MQTT and ICE used in industrial scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Other features, objects and advantages of the present invention will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0056] Figure 1 Schematic diagram of multi-terminal heterogeneous data fusion system in industrial scenarios. DETAILED DESCRIPTION

[0057] The present invention will be described in detail below with reference to specific embodiments. The following examples will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those skilled in the art, several changes and improvements can be made without departing from the scope of the present invention. These all fall within the scope of protection of the present invention.

[0058] Example 1

[0059] According to the present invention, a method for fusion of multi-terminal heterogeneous data in industrial scenarios is provided. Figure 1 As shown, including:

[0060] Step S1: registering the context information of the remote service with the gateway server; the context information of the remote service includes: the server application unique identifier (APPID), the remote service unique identifier (SID), the service protocol type (TYPE) and the service target address (URL);

[0061] Specifically, the unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier;

[0062] The unique identifier of the remote service indicates the name of the backend service to be called;

[0063] The service protocol type is the protocol used by the backend service, including HTTP and TCP;

[0064] The service target address is the IP address and port number of the host where the backend service is located.

[0065] Step S2: Configure the CORS policy of the gateway server to allow cross-domain access;

[0066] Specifically, the CORS policy includes:

[0067] Access-Control-Allow-Origin: Allows the specified IP to access the domain;

[0068] Access-Control-Max-Age: Indicates the number of seconds within which the cross-origin access rights of the current request do not need to be repeatedly verified;

[0069] Access-Control-Allow-Methods: indicates the HTTP methods allowed for cross-origin requests, including GET, POST, PUT, and DELETE;

[0070] Access-Control-Allow-Headers: Indicates which header information is allowed in the access request.

[0071] Step S3: Initiate an HTTP request on the front end based on the encapsulated JS SDK; the request parameters include the unique identifier of the server application, the unique identifier of the remote service, the service request parameters, and the service response callback processing function;

[0072] The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier;

[0073] The unique identifier of the remote service indicates the name of the backend service to be called;

[0074] The service request parameter is a JSON structure with a unified structure, including a data area, a standard attribute area and an extended data area;

[0075] The response callback function is the business code for processing the data returned by the backend. Custom operations are performed in the callback function for the data returned by different projects and different backends, and JSON data in the same format as the request parameters is returned.

[0076] Step S4: The gateway server performs addressing and discovery of services based on the unique identifier of the server application and the unique identifier of the remote service, converts the service protocol type, and initiates a call in accordance with the protocol of the service provider.

[0077] Specifically, the gateway server performs addressing discovery service according to the unique identifier of the server application and the unique identifier of the remote service: obtaining the full element information of the remote service according to the unique identifier of the server application and the unique identifier of the remote service;

[0078] The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to parse the parameters of the organization front-end HTTP request and initiate a service call.

[0079] Step S5: After obtaining the service response data, the gateway server encapsulates the response data according to a preset format for use by the service caller in the service response callback processing function.

[0080] Specifically, the step S5 adopts: after the gateway server obtains the service response data, it encapsulates the response data in a fixed JSON format for use by the service caller in the service response callback processing function;

[0081] Service response data encapsulation means that the gateway server places the service call results in the data area of ​​a unified JSON structure, and sets the service request status code and call prompt information in the standard attribute area.

[0082] According to the present invention, a multi-terminal heterogeneous data fusion system for industrial scenarios includes:

[0083] Module M1: Registering remote service context information using a gateway server; the remote service context information includes: server application unique identifier (APPID), remote service unique identifier (SID), service protocol type (TYPE) and service target address (URL);

[0084] Specifically, the unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier;

[0085] The unique identifier of the remote service indicates the name of the backend service to be called;

[0086] The service protocol type is the protocol used by the backend service, including HTTP and TCP;

[0087] The service target address is the IP address and port number of the host where the backend service is located.

[0088] Module M2: Configure the CORS policy of the gateway server to allow cross-domain access;

[0089] Specifically, the CORS policy includes:

[0090] Access-Control-Allow-Origin: Allows the specified IP to access the domain;

[0091] Access-Control-Max-Age: Indicates the number of seconds within which the cross-origin access rights of the current request do not need to be repeatedly verified;

[0092] Access-Control-Allow-Methods: indicates the HTTP methods allowed for cross-origin requests, including GET, POST, PUT, and DELETE;

[0093] Access-Control-Allow-Headers: Indicates which header information is allowed in the access request.

[0094] Module M3: Initiates an HTTP request on the front end based on the encapsulated JS SDK; the request parameters include the server application unique identifier, the remote service unique identifier, the service request parameters, and the service response callback processing function;

[0095] The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier;

[0096] The unique identifier of the remote service indicates the name of the backend service to be called;

[0097] The service request parameter is a JSON structure with a unified structure, including a data area, a standard attribute area and an extended data area;

[0098] The response callback function is the business code for processing the data returned by the backend. Custom operations are performed in the callback function for the data returned by different projects and different backends, and JSON data in the same format as the request parameters is returned.

[0099] Module M4: The gateway server addresses and discovers services based on the unique identifier of the server application and the unique identifier of the remote service, converts the service protocol type, and initiates a call in accordance with the protocol of the service provider.

[0100] Specifically, the gateway server performs addressing discovery service according to the unique identifier of the server application and the unique identifier of the remote service: obtaining the full element information of the remote service according to the unique identifier of the server application and the unique identifier of the remote service;

[0101] The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to parse the parameters of the organization front-end HTTP request and initiate a service call.

[0102] Module M5: After the gateway server obtains the service response data, it encapsulates the response data according to a preset format for use by the service caller in the service response callback processing function.

[0103] Specifically, the module M5 adopts: after the gateway server obtains the service response data, it encapsulates the response data in a fixed JSON format for use by the service caller in the service response callback processing function;

[0104] Service response data encapsulation means that the gateway server places the service call results in the data area of ​​a unified JSON structure, and sets the service request status code and call prompt information in the standard attribute area.

[0105] Example 2

[0106] Example 2 is a preferred example of Example 1

[0107] like Figure 1 As shown, the present invention provides a method for fusion of multi-terminal heterogeneous data in industrial scenarios, comprising the following steps:

[0108] Step S1: Register the context information of each heterogeneous data service in the gateway server. Specifically:

[0109] In step S1, the context information of the backend heterogeneous data service is entered in the gateway server management interface, including the ID of the application to which the service belongs (APPID), the service ID (SID), the service protocol type (TYPE), and the service target address (URL). The context information of the service is as follows:

[0110] "BSMS,S_BS_AP_01,HTTP,10.25.10.32:9080 / service".

[0111] Step S2: Configure the CORS policy of the gateway server to allow cross-domain access. Specifically:

[0112] The CORS policy configured in step S2 includes Access-Control-Allow-Origin, Access-Control-Max-Age, Access-Control-Allow-Methods, and Access-Control-Allow-Headers.

[0113] In step S2, configure Access-Control-Allow-Origin to the IP address or domain name of the front-end application, Access-Control-Max-Age to 7200 (two hours), Access-Control-Allow-Methods to GET and POST, and Access-Control-Allow-Headers to x-token.

[0114] Step S3: The service caller initiates an HTTP request on the front end based on the encapsulated JS SDK. The request parameters must include: application identifier (APPID), service identifier (SID), service request parameters, and service response callback processing function.

[0115] In step S3, the service caller actually initiates an HTTP request to the gateway server. The application identifier and service identifier in the request parameters are the service information registered in step 1, for example, BSMS, S_BS_AP_01. The service request parameters are the data to be passed to the service S_BS_AP_01, and the service response callback handler is the business logic statement that processes the result data returned by S_BS_AP_01.

[0116] Step S4: The gateway server performs address discovery based on the application identifier and service identifier, converts the service based on the service protocol type, and initiates a call in accordance with the service provider's protocol.

[0117] In step S4, when the gateway server receives the front-end service request, it searches for complete service information based on the application identifier and service identifier. For example, according to the BSMS, S_BS_AP_01 finds that the service protocol type is HTTP and the service address is 10.25.10.32:9080 / service. It then initiates an HTTP request to the target address.

[0118] Step S5: After the gateway server obtains the backend service response data, it packages it into a result with a unified format for use by the front-end application.

[0119] After the gateway server obtains the response data of the backend heterogeneous service in step S5, it needs to package the backend data in different formats into data in a unified format and pass it to the service response callback processing function in step 3.

[0120] Example 3

[0121] Example 3 is a preferred embodiment of Example 1 and / or Example 2.

[0122] The present invention is used in the production and operation scenario of a steel enterprise, taking "integrated display of the equipment status of a production line and the steel output of the production line" as an example to illustrate the implementation method of multi-terminal heterogeneous data fusion in an industrial scenario.

[0123] (1) The developer registers the service information of the backend system in the gateway server management interface, namely BSMS, S_BS_AP_01, HTTP, 10.25.10.32:9080 / service and BIQS, S_QE_AX_01, TCP, 10.25.10.41:65322. Among them, BSMS is the business system, S_BS_AP_01 is a service in the business system, which can query the steel production of a specified production line. The service protocol is HTTP, and the service target address is 10.25.10.32:9080 / service. BIQS is the production business system, S_QE_AX_01 is a service in the production system, which can query the equipment status of a specified production line. The service protocol is TCP, and the service target address is 10.25.10.41:65322.

[0124] (2) Configure the CORS policy on the gateway server to allow cross-domain access to the server where the front-end application is deployed. For example, if the IP address of the front-end application server is 10.25.10.21, configure the Access-Control-Allow-Origin of the gateway server to 10.25.10.21.

[0125] (3) Introduce the JS SDK tool library into the front-end application and use the API provided by the SDK to initiate service calls. For example, to request the steel production of production line QT04, you should use E.send('BSMS','S_BS_AP_01','QT04',callback1). To request the equipment status of production line QT04, you should use E.send('BIQS','S_QE_AX_01','QT04',callback2). Among them, callback1 and callback2 are the corresponding service response data processing functions, and the parameters of the processing functions are the data in a unified format packaged by the gateway server.

[0126] (4) After receiving the two service requests, the gateway server queries the corresponding service address and uses HTTP and TCP clients to initiate a request to the background server according to the protocol type. The request contains the parameter information required by the service (Production Line QT04).

[0127] (5) After the gateway server obtains the request result of the background service, it packages it into response data with a unified format. For example, after obtaining the production line output information, it stores it in the data area and sets the request status code to 0, indicating that the call is successful.

[0128] (6) The front-end application can parse and use the backend response data in the service response data processing function. The parameters in the callback functions callback1 and callback2 are the packaged response data. The front-end application can integrate and use them according to business needs.

[0129] Those skilled in the art will appreciate that, in addition to implementing the system, device, and various modules provided by the present invention in purely computer-readable program code, it is entirely possible to implement the same program in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, embedded microcontrollers, and the like by logically programming the method steps. Therefore, the system, device, and various modules provided by the present invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; the modules for implementing various functions can also be considered both software programs for implementing the method and structures within the hardware component.

[0130] The above describes specific embodiments of the present invention. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art may make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. The embodiments of this application and the features in the embodiments may be combined with each other in any manner unless there is a conflict.

Claims

1. A method for fusion of multi-terminal heterogeneous data in industrial scenarios, characterized by: include: Step S1: registering context information of a remote service that meets preset requirements using a gateway server; Step S2: Configure the CORS policy of the gateway server; Step S3: Initiate an HTTP request on the front end based on the encapsulated JSSDK; Step S4: The gateway server performs addressing discovery service according to the remote service context information and initiates a call; Step S5: After the gateway server obtains the service response data, it encapsulates the response data in a preset format for use by the service caller in the service response callback processing function; The context information of the remote service that meets the preset requirements includes: the unique identifier of the server application, the unique identifier of the remote service, the service protocol type and the service target address; The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier; The unique identifier of the remote service indicates the name of the backend service to be called; The service protocol type is the protocol used by the backend service, including HTTP and TCP; The service target address is the IP address and port number of the host where the backend service is located; The step S4 adopts: the gateway server performs addressing and discovery of services according to the unique identifier of the server application and the unique identifier of the remote service, converts the service protocol type according to the service protocol type, and initiates the call in accordance with the protocol of the service provider; The gateway server performs addressing discovery service based on the unique identifier of the server application and the unique identifier of the remote service: obtaining full-factor information of the remote service based on the unique identifier of the server application and the unique identifier of the remote service; The conversion according to the service protocol type means that the gateway server uses the service provider's protocol to parse the parameters of the organization's front-end HTTP request and initiate a service call; The step S5 adopts: after the gateway server obtains the service response data, it encapsulates the response data in a fixed JSON format for use by the service caller in the service response callback processing function; Service response data encapsulation means that the gateway server places the service call results in the data area of ​​a unified JSON structure, and sets the service request status code and call prompt information in the standard attribute area.

2. The method for fusion of multi-terminal heterogeneous data in industrial scenarios according to claim 1 is characterized in that: The CORS policy includes: Access-Control-Allow-Origin: Allows the specified IP to access the domain; Access-Control-Max-Age: indicates that the cross-origin access rights of the current request do not need to be repeatedly verified within the preset time; Access-Control-Allow-Methods: indicates the HTTP methods allowed for cross-origin requests, including GET, POST, PUT, and DELETE; Access-Control-Allow-Headers: indicates the header information allowed in the access request.

3. The method for fusion of multi-terminal heterogeneous data in industrial scenarios according to claim 1 is characterized in that: The step S3 adopts: initiating an HTTP request on the front end based on the encapsulated JSSDK, and the request parameters include the unique identifier of the server application, the unique identifier of the remote service, the service request parameters and the service response callback processing function; The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier; The unique identifier of the remote service indicates the name of the backend service to be called; The service request parameter is a JSON structure with a unified structure, including a data area, a standard attribute area and an extended data area; The response callback function is the business code for processing the data returned by the backend. Custom operations are performed in the callback function for the data returned by different projects and different backends, and JSON data in the same format as the request parameters is returned.

4. An industrial scenario multi-terminal heterogeneous data fusion system, characterized by: include: Module M1: Registering remote service context information using the gateway server; Module M2: Configure the CORS policy of the gateway server; Module M3: Initiates HTTP requests on the front end based on the encapsulated JSSDK; Module M4: The gateway server performs addressing and discovery services based on the remote service context information and initiates a call; Module M5: After the gateway server obtains the service response data, it encapsulates the response data according to the preset format for use by the service caller in the service response callback processing function; The context information of the remote service includes: a unique identifier of the server application, a unique identifier of the remote service, a service protocol type, and a service target address; The unique identifier of the server application is the project name passed in by the service caller, and the gateway server can automatically discover the address of the server application based on the application identifier; The unique identifier of the remote service indicates the name of the backend service to be called; The service protocol type is the protocol used by the backend service, including HTTP and TCP; The service target address is the IP address and port number of the host where the backend service is located; The module M4 adopts: the gateway server performs addressing and discovery of services according to the unique identifier of the server application and the unique identifier of the remote service, converts the service protocol type, and initiates a call in accordance with the protocol of the service provider; The gateway server performs addressing discovery service based on the unique identifier of the server application and the unique identifier of the remote service: obtaining full-factor information of the remote service based on the unique identifier of the server application and the unique identifier of the remote service; The conversion according to the service protocol type means that the gateway server uses the service provider's protocol to parse the parameters of the organization's front-end HTTP request and initiate a service call; The module M5 adopts: after the gateway server obtains the service response data, it encapsulates the response data in a fixed JSON format for use by the service caller in the service response callback processing function; Service response data encapsulation means that the gateway server places the service call results in the data area of ​​a unified JSON structure, and sets the service request status code and call prompt information in the standard attribute area.

5. The industrial scenario multi-terminal heterogeneous data fusion system according to claim 4 is characterized in that: The CORS policy includes: Access-Control-Allow-Origin: Allows the specified IP to access the domain; Access-Control-Max-Age: indicates that the cross-origin access rights of the current request do not need to be repeatedly verified within the preset time; Access-Control-Allow-Methods: indicates the HTTP methods allowed for cross-origin requests, including GET, POST, PUT, and DELETE; Access-Control-Allow-Headers: indicates the header information allowed in the access request.

Images