CN115981881B - Industrial scene multi-terminal heterogeneous data fusion method and system - Google Patents
Industrial scene multi-terminal heterogeneous data fusion method and systemInfo
- Publication number
- CN115981881B CN115981881B CN202111198848.6A CN202111198848A CN115981881B CN 115981881 B CN115981881 B CN 115981881B CN 202111198848 A CN202111198848 A CN 202111198848A CN 115981881 B CN115981881 B CN 115981881B
- Authority
- CN
- China
- Prior art keywords
- service
- gateway server
- unique identifier
- server
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides an industrial scene multi-terminal heterogeneous data fusion method and system, comprising the following steps of S1, utilizing a gateway server to register context information of remote service, S2, configuring a CORS strategy of the gateway server, S3, initiating an HTTP request at the front end based on a packaged JS SDK, S4, enabling the gateway server to address and discover service according to the remote service information and initiate call, S5, after obtaining service response data, packaging the response data according to a preset format, and enabling a service calling party to use the service response callback processing function.
Description
Technical Field
The invention relates to the technical field of remote service call, in particular to a method and a system for fusing multi-terminal heterogeneous data of an industrial scene, more particularly to a standard client tool which supports the industrial scene of diverse application service ends and non-uniform interactive data structures and can be widely applied to service call of the multi-terminal heterogeneous data.
Background
With the increasing demands of users on front ends, there is also an increasing demand for an easy-to-use, flexible, efficient front end development framework. The trust and fusion project is generated, and aims to solve the problems of complex development technology, difficult cross-system display, poor multi-screen fusion capability, incapability of separating front ends and rear ends, non-uniform interface style, large development workload and the like.
The fusion project is used as a front-end framework, and needs to interact data with the back-end project. In the process of remote service call, in order to normalize and simplify the interaction process and simultaneously to be compatible with different business modes, service scenes and background frameworks, development of a set of unified, normative, efficient and flexible clients capable of accessing background services in different industrial scenes is needed.
Patent document 107633075A (application number: 201710872072.9) discloses a multi-source heterogeneous data fusion platform and a fusion method, wherein the fusion platform comprises a data acquisition unit, a data storage unit, a data standardization unit, a user image construction unit, a knowledge graph construction unit and a visualization unit, the data acquisition unit is used for acquiring multi-source heterogeneous data, the data storage unit is used for caching the multi-source heterogeneous data, the data standardization unit carries out lexical, grammatical and/or semantic analysis on the multi-source heterogeneous data to obtain standardized text data, the user image construction unit utilizes quantized student labels to construct user images of students, the knowledge graph construction unit constructs knowledge graphs of the students, knowledge graphs of teachers and knowledge graphs of courses, the knowledge graph of the students and the knowledge graph of teachers are related to obtain course connection, social relationship and teacher-student relationship centered on the students, and the visualization unit displays the course connection, the social relationship and the teacher-student relationship centered on the students.
Common remote service calling modes include RPC (Remote Produce Call) and REST modes, the former adopts TCP as a bottom layer transmission protocol, the speed is high, the efficiency is high, and the latter HTTP protocol is an application layer protocol and prescribes a request format, a response format, a resource positioning and operating mode and the like of network transmission. Since the converged platform needs to be applied in different industrial scenarios, encapsulation is required at the API level. The RPC mode limiting the development language is eliminated, and the cross-language and cross-platform HTTP protocol is adopted as the remote call standard of the unified client tool.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a multi-terminal heterogeneous data fusion method and system for industrial scenes. The characteristic that the front-end application calls the back-end heterogeneous data service in a unified mode is realized.
The invention provides an industrial scene multi-terminal heterogeneous data fusion method, which comprises the following steps:
step S1, registering context information of remote service by using a gateway server;
step S2, configuring a CORS strategy of a gateway server;
Step S3, initiating an HTTP request at the front end based on the packaged JS SDK;
step S4, the gateway server performs addressing discovery service according to the remote service context information and initiates calling;
and S5, after the gateway server acquires the service response data, the response data is packaged according to a preset format for the service calling party to use in the service response callback processing function.
Preferably, the context information of the remote service comprises a unique identifier of a 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 a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service protocol type is a protocol used by the back-end service and comprises HTTP and TCP;
the service target address is the IP address and port number of the host where the back-end service is located.
Preferably, the CORS strategy comprises:
Access-Control-alloy-Origin, allowing the specified IP to cross-domain Access;
Access-Control-Max-Age, which means that the cross-domain Access authority of the current request does not need to be checked repeatedly in the preset time;
Access-Control-Low-Methods, representing HTTP Methods that Allow cross-domain requests, including GET, POST, PUT and DELETE;
Access-Control-Allow-Headers, which represents the Header information allowed to be carried in the Access request.
Preferably, the step S3 is that an HTTP request is initiated at the front end based on the encapsulated JS SDK, and the request parameters comprise a unique identifier of a server application, a unique identifier of remote service, service request parameters and a service response callback processing function;
The unique identifier of the server application is a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service request parameters are JSON structures with unified structures and comprise a data area, a standard attribute area and an extended data area;
The response callback function is a service code for processing the back-end returned data, and is used for carrying out self-defined operation on the data returned by different items and different back-ends in the callback function, and returning JSON data with unified parameters with the request.
Preferably, the step S4 adopts that the gateway server performs addressing discovery service according to the unique identifier of the application of the service end and the unique identifier of the remote service, performs conversion according to the service protocol type, and initiates the call according to the protocol of the service provider.
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, and obtains 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;
The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to analyze and organize parameters of the front-end HTTP request and initiate service call.
Preferably, the step S5 is that after the gateway server obtains the service response data, the gateway server encapsulates the response data according to a fixed JSON format for a service calling party to use in a service response callback processing function;
The service response data encapsulation means that the gateway server places the service calling result in a data area of a JSON structure with uniform structure, sets a service request status code in a standard attribute area and calls prompt information.
The invention provides an industrial scene multi-terminal heterogeneous data fusion system, which comprises:
A module M1 for registering context information of the remote service using the gateway server;
a module M2, configuring a CORS strategy of a gateway server;
A module M3, initiating an HTTP request at the front end based on the encapsulated JS SDK;
the gateway server performs addressing discovery service according to the remote service context information and initiates calling;
And the module M5 is used for encapsulating the response data according to a preset format after the gateway server acquires the service response data, so that the service calling party can use the service response callback processing function.
Preferably, the context information of the remote service comprises a unique identifier of a 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 a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service protocol type is a protocol used by the back-end service and comprises HTTP and TCP;
the service target address is the IP address and port number of the host where the back-end service is located.
Preferably, the CORS strategy comprises:
Access-Control-alloy-Origin, allowing the specified IP to cross-domain Access;
Access-Control-Max-Age, which means that the cross-domain Access authority of the current request does not need to be checked repeatedly in the preset time;
Access-Control-Low-Methods, representing HTTP Methods that Allow cross-domain requests, including GET, POST, PUT and DELETE;
Access-Control-Allow-Headers, which represents the Header information allowed to be carried in the Access request. Compared with the prior art, the invention has the following beneficial effects:
1. The invention adopts the standardized remote service calling method, solves the defects of chaotic mode and complex parameters when the traditional service calling mode faces to multi-class industrial heterogeneous data service, effectively improves the service calling efficiency in the development process, and utilizes gateway technology to fuse and convert heterogeneous potential user trial data value;
2. the invention realizes safe operation of data resources, provides convenient operation and individuation processing of heterogeneous server data;
3. According to the method, a unified and normative client is built aiming at heterogeneous data structures and various server development frames in different projects, and a set of use standards are designated to meet the requirements in different industrial scenes;
4. The heterogeneous data fusion method provided by the invention performs unified registration aiming at the services of different protocol types, simplifies the front-end application calling mode, and enables the front-end application to uniformly use the HTTP protocol to request the services of different protocols at the rear end;
5. The invention encapsulates the standard JS SDK, the service calling mode is simple and uniform, and the mode of processing service response is uniform;
6. The protocol conversion capability of the gateway server is open and extensible, and can meet the communication protocols such as MQTT, ICE and the like used in industrial scenes.
Drawings
Other features, objects and advantages of the present invention will become more apparent upon reading of the detailed description of non-limiting embodiments, given with reference to the accompanying drawings in which:
fig. 1 is a schematic diagram of an industrial scene multi-terminal heterogeneous data fusion system.
Detailed Description
The present invention will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the present invention, but are not intended to limit the invention in any way. It should be noted that variations and modifications could be made by those skilled in the art without departing from the inventive concept. These are all within the scope of the present invention.
Example 1
The method for fusing multi-terminal heterogeneous data of an industrial scene provided by the invention, as shown in figure 1, comprises the following steps:
The method comprises the steps of S1, registering context information of remote service by using a gateway server, wherein the context information of the remote service comprises a unique service end application identifier (APPID), a unique Service Identifier (SID), a service protocol TYPE (TYPE) and a service target address (URL);
Specifically, the unique identifier of the server application is a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service protocol type is a protocol used by the back-end service and comprises HTTP and TCP;
the service target address is the IP address and port number of the host where the back-end service is located.
Step S2, configuring a CORS strategy of a gateway server, and allowing cross-domain access;
Specifically, the CORS strategy includes:
Access-Control-alloy-Origin, allowing the specified IP to cross-domain Access;
Access-Control-Max-Age, which means how many seconds the cross-domain Access right of the current request does not need to be checked repeatedly;
Access-Control-Low-Methods, representing HTTP Methods that Allow cross-domain requests, including GET, POST, PUT and DELETE;
Access-Control-Allow-Headers indicates which Header information is allowed to be carried in the Access request.
Step S3, initiating an HTTP request at the front end based on the packaged JS SDK, wherein the request parameters comprise a unique identifier of a server application, a unique identifier of a remote service, a service request parameter and a service response callback processing function;
The unique identifier of the server application is a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service request parameters are JSON structures with unified structures and comprise a data area, a standard attribute area and an extended data area;
The response callback function is a service code for processing the back-end returned data, and is used for carrying out self-defined operation on the data returned by different items and different back-ends in the callback function, and returning JSON data with unified parameters with the request.
And S4, the gateway server performs addressing discovery service according to the unique identifier of the service end application and the unique identifier of the remote service, performs conversion according to the service protocol type, and initiates calling according to the protocol of the service provider.
The gateway server obtains the full-element information of the remote service according to the unique identifier of the application of the server and the unique identifier of the remote service;
The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to analyze and organize parameters of the front-end HTTP request and initiate service call.
And S5, after the gateway server acquires the service response data, the response data is packaged according to a preset format for the service calling party to use in the service response callback processing function.
The gateway server encapsulates the response data according to a fixed JSON format after obtaining the service response data, so that a service calling party can use the response data in a service response callback processing function;
The service response data encapsulation means that the gateway server places the service calling result in a data area of a JSON structure with uniform structure, sets a service request status code in a standard attribute area and calls prompt information.
The invention provides an industrial scene multi-terminal heterogeneous data fusion system, which comprises:
the method comprises the steps of (1) registering context information of a remote service by using a gateway server, wherein the context information of the remote service comprises a unique service end application identifier (APPID), a unique Service Identifier (SID), a service protocol TYPE (TYPE) and a service target address (URL);
Specifically, the unique identifier of the server application is a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service protocol type is a protocol used by the back-end service and comprises HTTP and TCP;
the service target address is the IP address and port number of the host where the back-end service is located.
A module M2, configuring a CORS strategy of a gateway server, and allowing cross-domain access;
Specifically, the CORS strategy includes:
Access-Control-alloy-Origin, allowing the specified IP to cross-domain Access;
Access-Control-Max-Age, which means how many seconds the cross-domain Access right of the current request does not need to be checked repeatedly;
Access-Control-Low-Methods, representing HTTP Methods that Allow cross-domain requests, including GET, POST, PUT and DELETE;
Access-Control-Allow-Headers indicates which Header information is allowed to be carried in the Access request.
The module M3 initiates an HTTP request at the front end based on the packaged JS SDK, wherein the request parameters comprise a unique identifier of a server application, a unique identifier of remote service, a service request parameter and a service response callback processing function;
The unique identifier of the server application is a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service request parameters are JSON structures with unified structures and comprise a data area, a standard attribute area and an extended data area;
The response callback function is a service code for processing the back-end returned data, and is used for carrying out self-defined operation on the data returned by different items and different back-ends in the callback function, and returning JSON data with unified parameters with the request.
And the gateway server performs addressing discovery service according to the unique identifier of the service end application and the unique identifier of the remote service, performs conversion according to the service protocol type, and initiates call according to the protocol of the service provider.
The gateway server obtains the full-element information of the remote service according to the unique identifier of the application of the server and the unique identifier of the remote service;
The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to analyze and organize parameters of the front-end HTTP request and initiate service call.
And the module M5 is used for encapsulating the response data according to a preset format after the gateway server acquires the service response data, so that the service calling party can use the service response callback processing function.
The module M5 is used for encapsulating the response data according to a fixed JSON format after the gateway server obtains the service response data, so that a service calling party can use the service response callback processing function;
The service response data encapsulation means that the gateway server places the service calling result in a data area of a JSON structure with uniform structure, sets a service request status code in a standard attribute area and calls prompt information.
Example 2
Example 2 is a preferred example of example 1
As shown in fig. 1, the invention provides a multi-terminal heterogeneous data fusion method for an industrial scene, which comprises the following steps:
and step S1, registering the context information of each heterogeneous data service in the gateway server. Specifically:
in step S1, the context information of the back-end heterogeneous data service is entered in the gateway server management interface, including an identifier (APPID), a Service Identifier (SID), a service protocol TYPE (TYPE), and a service destination address (URL) of an application to which the service belongs. The context information of the service is as follows:
“BSMS,S_BS_AP_01,HTTP,10.25.10.32:9080/service”。
and step S2, configuring a CORS strategy of the gateway server, and allowing cross-domain access. Specifically:
The CORS policies configured in step S2 include Access-Control-alloy-Origin, access-Control-Max-Age, access-Control-alloy-Methods, and Access-Control-alloy-Headers.
In step S2, the Access-Control-alloy-Origin configures an IP address or domain name of the front-end application, the Access-Control-Max-Age configures 7200 (two hours), the Access-Control-alloy-Methods configures GET and POST, and the Access-Control-alloy-Headers configures x-token.
And step S3, the service calling party initiates an HTTP request at the front end based on the encapsulated JS SDK, wherein the request parameters comprise application identification (APPID), service Identification (SID) and service request parameters, and the service response calls back a processing function.
In step S3, the service caller actually initiates an HTTP request to the gateway server, and the application identifier and the service identifier in the request parameter during the call are the service information registered in step S1, for example, BSMS, s_bs_ap_01. The service request parameter is data which needs to be transmitted into the service S_BS_AP_01, and the service response callback processing function is a business logic statement for processing the returned result data of the S_BS_AP_01.
Step S4, the gateway server performs addressing discovery service according to the application identifier and the service identifier, performs conversion according to the service protocol type, and initiates call according to the protocol of the service provider
And in the step S4, when the gateway server receives the front-end service request, the gateway server searches complete service information according to the application identifier and the service identifier. For example, according to BSMS, s_bs_ap_01 finds that the protocol type of the service is HTTP and the service address is 10.25.10.32:9080/service. An HTTP request is then initiated to the destination address.
And S5, after the gateway server acquires the background service response data, packaging and converting the background service response data into a result with uniform format for front-end application.
After the gateway server obtains the response data of the back-end heterogeneous service in step S5, the gateway server needs to package and convert the background data with different formats into data with uniform format, and then transmits the data to the service response callback processing function in step S3.
Example 3
Example 3 is a preferred example of example 1 and/or example 2
The invention is oriented to a production and operation scene of a certain iron and steel enterprise, and takes 'fusion display of equipment state of a certain production line and steel yield of the production line' as an example to describe the implementation mode of multi-terminal heterogeneous data fusion in an industrial scene.
(1) The developer registers service information of the background 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 respectively. The BSMS is an operation system, the S_BS_AP_01 is a service in the operation system, the steel yield of a specified production line can be queried, the service protocol is HTTP, and the service target address is 10.25.10.32:9080/service. BIQS is a production service system, s_qe_ax_01 is a service in the production system, and can query the device status under the specified production line, the service protocol is TCP, and the service destination address is 10.25.10.41:65322.
(2) The gateway server configures the CORS policy to allow cross-domain access by the server where the front-end application is deployed, e.g. the IP of the server of the front-end application is 10.25.10.21. The Access-Control-alloy-Origin of the gateway server is configured to be 10.25.10.21.
(3) The JS SDK tool library is introduced into the front-end application, and the API provided by the SDK is used for initiating service call. For example, the steel yield of the request line QT04 should be e.send ('BSMS', 's_bs_ap_01', 'QT04', callback 1), the equipment status of the request QT04 line should be e.send ('BIQS', 's_qe_ax_01', 'QT04', callback 2). The callback1 and the callback2 are corresponding service response data processing functions respectively, and parameters of the processing functions are data with unified format after being packaged by the gateway server.
(4) After receiving the two service requests, the gateway server inquires the corresponding service address, and initiates a request to a background server by using HTTP and TCP clients according to the protocol type, wherein the request comprises parameter information production line QT04 required by the service.
(5) And after the gateway server acquires the request result of the background service, the request result is packaged into response data with uniform format, for example, after the production line output information is acquired, the response data is stored in a data area, and a request state code is set to be 0 to indicate that the call is successful.
(6) The front-end application can analyze and use the response data of the background in the service response data processing function, parameters in callback functions callback1 and callback2 are packaged response data, and the front-end application can be used in a fusion mode according to the root business needs.
Those skilled in the art will appreciate that the systems, apparatus, and their respective modules provided herein may be implemented entirely by logic programming of method steps such that the systems, apparatus, and their respective modules are implemented as logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc., in addition to the systems, apparatus, and their respective modules being implemented as pure computer readable program code. Therefore, the system, the device and the respective modules thereof provided by the invention can be regarded as a hardware component, and the modules for realizing various programs included therein can be regarded as a structure in the hardware component, and the modules for realizing various functions can be regarded as a structure in the hardware component as well as a software program for realizing the method.
The foregoing describes specific embodiments of the present application. It is to be understood that the application is not limited to the particular embodiments described above, and that various changes or modifications may be made by those skilled in the art within the scope of the appended claims without affecting the spirit of the application. The embodiments of the application and the features of the embodiments may be combined with each other arbitrarily without conflict.
Claims (5)
1. The industrial scene multi-terminal heterogeneous data fusion method is characterized by comprising the following steps of:
s1, registering context information meeting preset requirements of remote service by using a gateway server;
step S2, configuring a CORS strategy of a gateway server;
step S3, initiating an HTTP request at the front end based on the packaged JSSDK;
step S4, the gateway server performs addressing discovery service according to the remote service context information and initiates calling;
Step S5, after the gateway server obtains the service response data, the response data is packaged according to a preset format for the service calling party to use in the service response callback processing function;
the context information meeting the preset requirements of the remote service comprises a unique identifier of the application of the server, a unique identifier of the remote service, a service protocol type and a service target address;
The unique identifier of the server application is a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service protocol type is a protocol used by the back-end service and comprises HTTP and TCP;
the service target address is the IP address and port number of the host where the back-end service is located;
The gateway server addresses and discovers the service according to the unique identifier of the application of the server and the unique identifier of the remote service, converts according to the service protocol type and initiates the call according to the protocol of the service provider;
the gateway server performs addressing discovery service according to the unique identifier of the server application and the unique identifier of the remote service, and obtains 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;
The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to analyze and organize parameters of the front-end HTTP request and initiate service call;
After the gateway server obtains the service response data, the gateway server encapsulates the response data according to a fixed JSON format for a service calling party to use in a service response callback processing function;
The service response data encapsulation means that the gateway server places the service calling result in a data area of a JSON structure with uniform structure, sets a service request status code in a standard attribute area and calls prompt information.
2. The industrial scenario multi-terminal heterogeneous data fusion method of claim 1, wherein the CORS strategy comprises:
Access-Control-alloy-Origin, allowing the specified IP to cross-domain Access;
Access-Control-Max-Age, which means that the cross-domain Access authority of the current request does not need to be checked repeatedly in the preset time;
Access-Control-Low-Methods, representing HTTP Methods that Allow cross-domain requests, including GET, POST, PUT and DELETE;
Access-Control-Allow-Headers, which represents the Header information allowed to be carried in the Access request.
3. The industrial scenario multi-terminal heterogeneous data fusion method according to claim 1, wherein the step S3 is characterized in that an HTTP request is initiated at the front end based on the packaged JSSDK, and the request parameters comprise a unique identifier of a server application, a unique identifier of a remote service, a service request parameter and a service response callback processing function;
The unique identifier of the server application is a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service request parameters are JSON structures with unified structures and comprise a data area, a standard attribute area and an extended data area;
The response callback function is a service code for processing the back-end returned data, and is used for carrying out self-defined operation on the data returned by different items and different back-ends in the callback function, and returning JSON data with unified parameters with the request.
4. An industrial scene multi-terminal heterogeneous data fusion system, comprising:
A module M1 for registering context information of the remote service using the gateway server;
a module M2, configuring a CORS strategy of a gateway server;
module M3, initiating an HTTP request at the front end based on the encapsulated JSSDK;
the gateway server performs addressing discovery service according to the remote service context information and initiates calling;
The gateway server packages the response data according to a preset format after obtaining the service response data, and the response data is used by a service calling party in a service response callback processing function;
The context information of the remote service comprises a unique identifier of a 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 a project name transmitted by a service calling party, and the gateway server can automatically discover the address of the server application according to the application identifier;
The unique identification of the remote service indicates the name of the back-end service to be called;
The service protocol type is a protocol used by the back-end service and comprises HTTP and TCP;
the service target address is the IP address and port number of the host where the back-end service is located;
The gateway server carries out addressing discovery service according to the unique identifier of the application of the service end and the unique identifier of the remote service, carries out conversion according to the service protocol type, and initiates calling according to the protocol of the service provider;
the gateway server performs addressing discovery service according to the unique identifier of the server application and the unique identifier of the remote service, and obtains 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;
The conversion according to the service protocol type means that the gateway server uses the protocol of the service provider to analyze and organize parameters of the front-end HTTP request and initiate service call;
After the gateway server obtains the service response data, the gateway server encapsulates the response data according to a fixed JSON format for a service calling party to use in a service response callback processing function;
The service response data encapsulation means that the gateway server places the service calling result in a data area of a JSON structure with uniform structure, sets a service request status code in a standard attribute area and calls prompt information.
5. The industrial scenario multi-terminal heterogeneous data fusion system of claim 4, wherein the CORS strategy comprises:
Access-Control-alloy-Origin, allowing the specified IP to cross-domain Access;
Access-Control-Max-Age, which means that the cross-domain Access authority of the current request does not need to be checked repeatedly in the preset time;
Access-Control-Low-Methods, representing HTTP Methods that Allow cross-domain requests, including GET, POST, PUT and DELETE;
Access-Control-Allow-Headers, which represents the Header information allowed to be carried in the Access request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111198848.6A CN115981881B (en) | 2021-10-14 | 2021-10-14 | Industrial scene multi-terminal heterogeneous data fusion method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111198848.6A CN115981881B (en) | 2021-10-14 | 2021-10-14 | Industrial scene multi-terminal heterogeneous data fusion method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115981881A CN115981881A (en) | 2023-04-18 |
| CN115981881B true CN115981881B (en) | 2025-08-22 |
Family
ID=85956801
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111198848.6A Active CN115981881B (en) | 2021-10-14 | 2021-10-14 | Industrial scene multi-terminal heterogeneous data fusion method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115981881B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101502067A (en) * | 2006-08-15 | 2009-08-05 | 中兴通讯股份有限公司 | Home gateway network storage system and network access method thereof |
| CN104038414A (en) * | 2013-08-21 | 2014-09-10 | 江南大学 | Multiprotocol intelligent household gateway apparatus and system thereof |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8195823B2 (en) * | 2000-04-17 | 2012-06-05 | Circadence Corporation | Dynamic network link acceleration |
| CN105450589B (en) * | 2014-07-31 | 2018-12-14 | 阿里巴巴集团控股有限公司 | Remote invocation method and system |
| CN112612629B (en) * | 2020-12-28 | 2024-05-24 | 广东广宇科技发展有限公司 | Method and system for realizing component type data interface |
-
2021
- 2021-10-14 CN CN202111198848.6A patent/CN115981881B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101502067A (en) * | 2006-08-15 | 2009-08-05 | 中兴通讯股份有限公司 | Home gateway network storage system and network access method thereof |
| CN104038414A (en) * | 2013-08-21 | 2014-09-10 | 江南大学 | Multiprotocol intelligent household gateway apparatus and system thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115981881A (en) | 2023-04-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3399715B1 (en) | Protocol conversion method, platform, and protocol conversion gateway | |
| Alaya et al. | Toward semantic interoperability in oneM2M architecture | |
| CN104640237B (en) | A kind of Internet of things system | |
| CN103139234B (en) | A kind of device and method of data, services encapsulation | |
| CN107450899B (en) | Method and device for generating terminal control script | |
| KR20170055530A (en) | Systems and methods for enabling access to third party services via service layer | |
| CN103095609A (en) | Access adaptive method and device based on Internet of things terminals | |
| CN106559251A (en) | A kind of Compilation Method and corresponding interface, component and system based on YANG models | |
| WO2011137788A1 (en) | Device management method, middleware, and machine-to-machine communication platform, device and system | |
| CN102137144B (en) | Method and system for configuration management of third-party software as well as management server | |
| WO2010130165A1 (en) | Method and system for generating open telecommunication service based on internet | |
| CN106936932A (en) | A kind of method wrapped by cloud service protocol access robot software | |
| CN107809332A (en) | Compound interface configures and compound interface call method, device | |
| Alaya et al. | Towards semantic data interoperability in oneM2M standard | |
| WO2024012001A1 (en) | Method and system for implementing access to open source community in multi-modal network | |
| CN115981881B (en) | Industrial scene multi-terminal heterogeneous data fusion method and system | |
| CN112367297B (en) | Service control method and device | |
| CN115550468A (en) | Service request processing method, device, equipment and medium | |
| CN100527717C (en) | Information display in accordance with inserting family gateway and interactive method | |
| CN116582364A (en) | Data access method, system, device, electronic device and readable storage medium | |
| CN112367296B (en) | Service control method and device | |
| CN112416321B (en) | Application generation method, device, storage medium and electronic device | |
| CN111371823B (en) | Method for client to access micro-service in non-WEB scene | |
| CN115145989A (en) | Data sharing method and device based on data model of Internet of things | |
| CN119696877B (en) | Access authentication and data arrangement method and device based on visualization technology |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |