Processing method and system of park data service switching center

Abstract

The invention provides a processing method and system of a park data service switching center, which are used for configuring a specific processing architecture of the park data service switching center and continuously providing a series of matching schemes from the aspect of details. Therefore, automatic and intelligent integration can be carried out on application information systems dispersedly constructed by enterprises, low-cost, stable and efficient data exchange services are realized among the application information systems, and the high-quality data exchange requirements of the park for different application information systems are met.

Description

Technical Field

[0001] This application relates to the field of communications, and specifically relates to a processing method and system for a park data service exchange center. Background Art

[0002] With the continuous development of enterprises, considering the improvement of production and operation efficiency, reduction of operation risks and costs, and enhancement of the overall management level and sustainable operation ability of enterprises, in actual situations, various professional management systems are usually built. And the data sharing, data exchange, and data support among these management systems are becoming more and more frequent, and the call for unified data exchange management is getting louder and louder.

[0003] The inventors of this application found that a series of professional management systems adopted by enterprises usually involve different system products on the market. In this case, there are often information islands among professional management systems. More specifically, as a system product, professional management systems often do not consider data exchange with other system products during the original design. Thus, for enterprises, especially micro and small enterprises, the data exchange between different professional management systems depends on manual operations, which obviously has the problems of inconvenient operation and low work efficiency. Summary of the Invention

[0004] This application provides a processing method and system for a park data service exchange center, which configures a specific processing architecture for the park data service exchange center and continues to provide a series of supporting solutions in detail. In this way, the application information systems built dispersedly by enterprises can be automatically and intelligently integrated, and low-cost, stable, and efficient data exchange services can be realized among the application information systems, meeting the high-quality data exchange requirements of the park for different application information systems.

[0005] In the first aspect, this application provides a processing method for a park data service exchange center. The method includes:

[0006] A first device reports a data acquisition request to the park data service exchange center. Among them, the first device is included in different devices, corresponding to the park data service exchange center configured for the target park. For different devices, business configuration processing including application registration, application authentication, interface definition, service configuration, interface binding, and subscription creation has been completed in advance. Different devices are deployed with corresponding application information systems;

[0007] The park data service exchange center extracts target data reported by a second device in response to the data acquisition request. Among them, the second device is included in different devices;

[0008] The campus data service exchange center feeds back the target data to the first device, completing the response to the data acquisition request.

[0009] In combination with the first aspect of the present application, in a first possible implementation manner of the first aspect of the present application, the method further includes:

[0010] Under the triggering of the locally configured triggering policy or the triggering instruction issued by the campus data service exchange center, the third device reports the data exchange content to the campus data service exchange center;

[0011] The campus data service exchange center responds to other data acquisition requests of the fourth device based on the data exchange content.

[0012] In combination with the first aspect of the present application, in a second possible implementation manner of the first aspect of the present application, the method further includes:

[0013] The campus data service exchange center performs business configuration processing including application registration, application authentication, interface definition, service configuration, interface binding and subscription creation.

[0014] In combination with the first aspect of the present application, in the third possible implementation method of the first aspect of the present application, with respect to registered applications, the application types involved include WEB applications, mobile applications, AI applications, algorithm applications, data applications, and 4C client applications.

[0015] In combination with the first aspect of the present application, in a fourth possible implementation manner of the first aspect of the present application, with respect to the registered application, the issuing address involved is an address for providing an interface or application deployment, and the data service exchange center detects whether the network between itself and the current application is in an unobstructed state through the issuing address;

[0016] If it is in a smooth state, it is determined that the current situation is that the normal data exchange service involved in the current application can be carried out. If it is not in a smooth state, it is determined that the current situation is that the data exchange service involved in the current application can be ignored.

[0017] In combination with the first aspect of the present application, in the fifth possible implementation method of the first aspect of the present application, with respect to application authentication, the campus data service exchange center generates a unique application access identifier for the current device and its application to perform identity authentication processing for subsequent data access.

[0018] In combination with the first aspect of the present application, in the sixth possible implementation method of the first aspect of the present application, with respect to defining the interface, the interface protocols involved specifically include HTTP / HTTPS protocol, WEBSERVICE protocol, MODBUS-TCP protocol, OPC protocol and DB direct connection protocol.

[0019] In combination with the first aspect of the present application, in the seventh possible implementation manner of the first aspect of the present application, the service classification involved in the configuration service specifically includes the received data type and the pushed data type, and the subscription number involved in creating a subscription specifically relates to production services and consumption services.

[0020] In a second aspect, the present application provides a park data service exchange system for executing the method provided in the first aspect of the present application or any possible implementation manner of the first aspect of the present application.

[0021] In a third aspect, the present application provides a computer-readable storage medium storing multiple instructions suitable for a processor to load and execute the method provided in the first aspect of the present application or any possible implementation manner of the first aspect of the present application.

[0022] From the above content, it can be concluded that the present application has the following beneficial effects:

[0023] For the data exchange target involved in the park, the present application configures a specific processing architecture of a park data service exchange center and continues to provide a series of supporting solutions in terms of details. In this way, the application information systems built dispersedly by enterprises can be automatically and intelligently integrated, and low-cost, stable, and efficient data exchange services can be realized between the application information systems, meeting the high-quality data exchange requirements of the park for different application information systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0025] Figure 1 It is a schematic diagram of a system architecture of a processing system of a park data service exchange center of the present application;

[0026] Figure 2 It is a schematic flowchart of a processing method of a park data service exchange center of the present application;

[0027] Figure 3 It is a schematic diagram of a structure of a device involved in a processing system of a park data service exchange center of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0028] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope of protection of the present application.

[0029] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments described here can be implemented in an order different from that shown or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or modules does not have to be limited to those steps or modules clearly listed, but may include other steps or modules not clearly listed or inherent to these processes, methods, products or devices. The naming or numbering of steps that appear in the present application does not mean that the steps in the method flow must be executed in the time / logical order indicated by the naming or numbering. The named or numbered process steps can be changed in the order of execution according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved.

[0030] The division of modules in the present application is a logical division. In actual implementation, there may be other division methods. For example, multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed coupling, direct coupling or communication connection to each other can be through some interfaces. The indirect coupling or communication connection between modules can be electrical or other similar forms, which are not limited in the present application. And the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed to multiple circuit modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the present application.

[0031] Before introducing the processing method of the park data service exchange center provided by the present application, the background content involved in the present application will be introduced first.

[0032] First, refer to Figure 1A schematic diagram of a system architecture of the processing system of the park data service exchange center of the present application is shown. It can be seen that the processing system of the park data service exchange center involved in the present application involves multiple devices and the park data service exchange center. It is easy to understand that among these devices, in the application scenario of the park, there is a need for data exchange. Therefore, this purpose can be achieved through the park data service exchange center. Among them, there are:

[0033] For these devices, they can be user equipment (UE), or different types of devices such as server devices or physical hosts. Among them, UE can specifically be different types of terminal devices such as smart phones, tablet computers, all-in-one computers, smart bracelets, and personal digital assistants (PDA). Applications related to park work or application information systems are deployed on these devices;

[0034] For the park data service exchange center, it is usually a server device. Of course, it does not exclude the possibility of using different types of devices such as physical hosts. As long as the corresponding application programs are installed, and specifically, the device cluster method can be used for specific deployment work.

[0035] On this basis, continue to refer to Figure 2 A schematic flowchart of a processing method of the park data service exchange center of the present application is shown. As Figure 2 shown, the processing method of the park data service exchange center provided by the present application specifically may include the following steps S201 to step S203:

[0036] Step S201, the first device reports a data acquisition request to the park data service exchange center. Among them, the first device is included among different devices, corresponding to the park data service exchange center configured for the target park. For different devices, business configuration processing including application registration, application authentication, interface definition, service configuration, interface binding, and subscription creation has been completed in advance, and corresponding application information systems are deployed on different devices;

[0037] It can be understood that for the convenience of description, the present application uses the first, second, third, and fourth to distinguish between different devices.

[0038] When the first device has a data acquisition requirement based on the data exchange service, obviously, in the form of a data acquisition request, it can trigger the park data service exchange center to perform corresponding data exchange service processing.

[0039] Among them, it should be noted that the data exchange service provided by the park data service exchange center in this application specifically targets the application scenario of the park, or is limited to the scope of equipment involved in the park, rather than being able to perform data exchange arbitrarily. It has a certain degree of limitation in scope, and thus it is able to achieve high-quality data exchange services within a small range.

[0040] In addition, for the devices that can perform data exchange within the park scope, the solution of this application also involves the preliminary configuration work, that is, the business configuration processing including application registration, application authentication, interface definition, service configuration, interface binding, and subscription creation mentioned here.

[0041] The business configuration processing in these six aspects is a specific implementation solution for how to better achieve data exchange services conceived for the application scenario of the park in the actual situation of this application, and has better practical significance.

[0042] Specifically, there are:

[0043] (1) Application registration

[0044] All applications that need to obtain data or provide data register the name, code, application type, distribution address, registration time, etc. of the application information.

[0045] (2) Application authentication

[0046] Generate private keys for application access, etc.

[0047] (3) Interface definition

[0048] Define the interface name, code, belonging application, classification, protocol, address, parameters, etc.

[0049] (4) Service configuration

[0050] Configure the service name, code, belonging application, service classification, etc.

[0051] (5) Interface binding

[0052] Bind interfaces of the same classification to the configured service, and one service supports binding multiple interfaces of the same classification.

[0053] (6) Subscription creation

[0054] Select service information and create a subscription number for the external access address.

[0055] Correspondingly, in the actual application of the solution of this application, it may also involve the above-mentioned preliminary configuration work. That is, as an exemplary embodiment, the method of this application may further include:

[0056] The park data service exchange center conducts business configuration processing including aspects such as registering applications, application authentication, defining interfaces, configuring services, binding interfaces, and creating subscriptions.

[0057] Furthermore, for (1) the aspect of registering applications, the involved application types include different types of applications such as WEB applications, mobile applications, AI applications, algorithm applications, data applications, and 4C client applications.

[0058] It can be understood that in the solution of this application, the devices with data exchange requirements are specifically determined by whether they are equipped with pre-registered relevant applications, and these applications are a series of application information systems. In the embodiments here, they are the different applications / application information systems that this application can specifically involve. Starting from the type, more specific supporting solutions are given. Thus, it can be seen that this application can flexibly meet the data exchange requirements of different types of applications including data transmission, data sharing, and data support in actual situations.

[0059] In addition, as another exemplary embodiment, for (1) the aspect of registering applications, the issued address involved can specifically be the address for providing interfaces or application deployment. The data service exchange center detects whether the network between itself and the current application is in a smooth state through the issued address;

[0060] If it is in a smooth state, it is determined that the current situation allows for normal data exchange services involved in the current application. If it is not in a smooth state, it is determined that the current situation allows for ignoring the data exchange services involved in the current application.

[0061] It can be seen from the embodiments here that in the solution of this application, when the data service exchange center promotes data exchange services, it not only involves the application of dedicated interfaces / addresses but also involves real-time / dynamic status monitoring, so as to promote the processing of data exchange services normally only in the normal state, that is, the smooth state. In the abnormal state / non-smooth state, the data exchange processing initiated by requests such as data acquisition requests can be directly ignored, achieving the effect of simplifying the data processing work of the data service exchange center and making the data exchange services of the entire system more concise, stable, and efficient.

[0062] In addition, for devices that are not in a normal state / smooth state, the data service exchange center can also wait for a preset waiting duration and then check the change in the smooth state during this period for further network stability analysis. For example, if the frequency / times of not being in the normal state is higher than the corresponding threshold, the corresponding issued address can be reallocated, the device can be checked for abnormalities, or a prompt / warning can be sent to the corresponding staff, etc. In this way, through active or passive means, the devices joined to the processing system of the park data service exchange center can maintain a stable network state with the park data service exchange center, laying a foundation for stable data exchange requirements.

[0063] In addition, regarding (2) application authentication, as can be seen from the above content, it can involve the application of private keys to improve data security through encryption and decryption mechanisms.

[0064] In this regard, as another exemplary embodiment, the park data service exchange center generates a unique application access identifier for the current device and its application for identity verification processing during subsequent data access.

[0065] It can be understood that for each device joined to the processing system of the park data service exchange center, a dedicated application access identifier (private key) can be configured respectively. In this way, on the premise of ensuring data security during data transmission between the device / application and the park data service exchange center, it can further isolate between devices / applications, and further avoid the possibility of greater security risks caused by the leakage of individual application access identifiers in terms of details. At the same time, it also plays a role in facilitating management, such as facilitating the update and maintenance of application access identifiers for individuals and subsequent tracking / tracing processing.

[0066] In addition, as another exemplary embodiment, regarding (3) defining interfaces, the interface protocols involved can specifically include different types of protocols such as HTTP / HTTPS protocol, WEBSERVICE protocol, MODBUS-TCP protocol, OPC protocol, and DB direct connection protocol, etc.

[0067] It can be understood that this embodiment provides a specific implementation solution from a practical level for the communication connection types that can be adopted between different devices and the park data service exchange center in this application (relying on communication protocols), and has good practicability.

[0068] In addition, regarding the data exchange service involved in this application, it can be understood that it can involve local devices sharing data of other devices (this corresponds to Figure 1The data acquisition scenarios of the illustrated embodiments) may also involve the local device sharing local data with other devices. Corresponding to these two major types of service types, there are also corresponding classification settings in terms of (5) configuration services and (6) creating subscriptions. Among them, each service subscription number exists uniquely, and the data requirements are obtained by accessing the subscription number to obtain the corresponding data.

[0069] Correspondingly, as another exemplary embodiment, the service classifications involved in (5) configuration services may specifically include received data types and pushed data types, and the subscription numbers involved in (6) creating subscriptions may specifically involve production services and consumption services.

[0070] Step S202, the park data service exchange center extracts the target data reported by the second device in response to the data acquisition request, where the second device is included among different devices;

[0071] It can be understood that after receiving the data acquisition request initiated by the first device and triggering the corresponding data exchange process, the park data service exchange center can, according to the data acquisition target pointed to by the data acquisition request, obtain, in accordance with a preset data acquisition method, the target reported by the second device and subjected to data format standardization processing for use in the feedback of the data acquisition request.

[0072] Among them, it should be noted that in actual situations, corresponding to the situation of instructing the second device to report data in real time, as the data source, the second device can either report data only after being triggered by the trigger instruction of the park data service exchange center after the park data service exchange center receives the data acquisition request initiated by the first device; or, corresponding to the situation where the second device autonomously reports data for data exchange services, the second device can also report data according to other trigger strategies when the park data service exchange center does not receive the data acquisition request initiated by the first device or regardless of whether the park data service exchange center receives the data acquisition request initiated by the first device. These are all possible and can be adjusted according to the application requirements in specific applications and the execution strategies of specific configurations.

[0073] In addition, in some special cases, the second device can also be the first device. After all, the data exchange service involved in this application is essentially aimed at different application information systems, and different application information systems on the same device may also have data exchange requirements. Therefore, it is possible for the first device and the second device to be the same device.

[0074] In the specific processing process, the park data service exchange center will analyze the data content reported by the second device, and when it is determined that data format conversion is required, convert it into the data format adapted to the first device that initiates the data acquisition request.

[0075] Among them, if the application information systems on both sides are of the same type or even the same system, data format conversion may not be involved. In addition, in actual situations, it may also be the case that the data acquirer wants the original data on the data source side, and obviously no data format conversion is required in this case.

[0076] Therefore, due to the flexible and changeable application requirements in actual situations, data format conversion policies / rules can be pre-configured to determine whether data format conversion operations are specifically required.

[0077] In addition, this application can also configure a standard data format for the park data service exchange center to store and process the data involved in the data exchange service.

[0078] That is to say, the park data service exchange center will extract the target data reported by the second device and subjected to data format standardization processing. Among them, data format standardization processing refers to the standardization processing carried out between the data formats involved in different application information systems.

[0079] The purpose of this data format standardization processing is to configure one or even several unified standard data formats among the devices / applications added to the processing system of the park data service exchange center of this application, taking into account the differences in data formats between different application information systems. This can facilitate data management work including storage, and at the same time can be more conveniently and accurately converted into the data formats adapted to different devices.

[0080] In addition, it can be understood that the standard data format involved in this data format standardization processing, in actual applications, since it is a self-configured data format, an encryption mechanism can be introduced or superimposed when considering data security to play a role in data encryption.

[0081] Furthermore, the standard data format involved in this data format standardization processing, in actual applications, can also introduce a dynamic adjustment mechanism. Based on the quantitative indicators such as the monitoring data conversion efficiency, data conversion accuracy (or data conversion exception rate), and user satisfaction within the monitoring time window, combined with their respective corresponding weights, the final data format performance score is determined under the weighted mechanism. In this way, as the monitoring time window rolls and updates in the data format set, the target standard data format that adapts to real-time application conditions is continuously rotated, so as to ensure better data exchange service quality by combining different indicators in detail.

[0082] In addition, in addition to selecting a new target standard data format from a set of data formats including preset different standard data formats, in some cases, it can also be that the park data service exchange center independently generates / constructs a new standard data format. This involves the independent generation / construction process of the standard data format, and can combine the monitoring results of factors such as the monitoring data conversion efficiency, data conversion accuracy, and user satisfaction within the monitoring time window to iteratively update the standard data format, so as to achieve a higher degree of adaptation and real-time standard data format configuration effect.

[0083] Among them, for the independent generation / construction process of the standard data format, it can specifically be implemented through corresponding artificial intelligence (AI) products, such as a deep learning neural network, so as to achieve an efficient and highly adaptable independent generation / construction process effect of the standard data format through powerful AI technology.

[0084] Obviously, the model input of the independent generation / construction model of the standard data format is the monitoring results of factors such as the monitoring data conversion efficiency and data conversion accuracy within the monitoring time window, and this also corresponds to the configuration content of the training samples during the model training process.

[0085] In addition, the independent generation / construction model of the standard data format can also directly target the data formats of the different application information systems involved, and use the different formats involved as the technical / model input to carry out the corresponding new process of independent generation / construction of the standard data format. And in actual applications, whenever a new device is detected to be added to the system, or whenever it is detected that the original device is configured with a new application information system, or whenever it is detected that the original application information system adapts to a new data format, the corresponding data format can be obtained, and based on this, the model input can be updated to carry out a new round of independent generation / construction process of the standard data format, so that the determined standard data format always maintains the solution goal of being highly adaptable to the different application information systems and their data formats involved in the system.

[0086] Regarding the configuration work of the model, the specific model structure, model training architecture, and loss function during the model training process can either adopt existing solutions, or be further optimized and improved on the basis of existing solutions, or adopt novel self-developed solutions. These are all possible in actual situations and can be adaptively adjusted according to actual needs.

[0087] Step S203, the park data service exchange center feeds back the target data to the first device to complete the response to the data acquisition request.

[0088] After the target data corresponding to the current data acquisition request is extracted, obviously, it can be sent to the first device to complete the response / feedback to the data acquisition request initiated by the first device.

[0089] As an example, System 2 can access Subscription No. 01. The park data service exchange center will first find the corresponding production service 01, call the interface 01 under the production service 01 to obtain the production data, then call the interface under the consumption service to process the production data, and then send the data to System 2. Since there is no consumption service, the production data can be directly sent to System 2 to complete the response to a data acquisition request.

[0090] After receiving the target data sent by the park data service exchange center, the first device can perform corresponding data application processing according to the preset or real-time data application requirements / policies, such as storage, forwarding, content display, or further data analysis, etc. Obviously, the specific processing content in the data application link is relatively flexible in actual situations and can be adaptively configured according to the actual situation.

[0091] In addition, for the above solution content, it can be seen that the introduction of the data exchange service involved in the solution of this application is mainly from the perspective or application scenario of the first device that initiates the data acquisition request. For different devices added to the system, in addition to the data exchange requirements of the corresponding data providers, it can also involve the data exchange requirements as data users, which corresponds to the received / pushed data types and production / consumption services mentioned above.

[0092] In response to this, as another exemplary embodiment, under the trigger of the trigger policy configured locally or the trigger instruction sent by the park data service exchange center, the third device reports the data exchange content to the park data service exchange center;

[0093] Based on the data exchange content, the park data service exchange center responds to other data acquisition requests of the fourth device.

[0094] Among them, the third device can be the first device, or it can also be other devices other than the first device. Similarly, the fourth device can be the second device, or it can also be other devices other than the second device.

[0095] Finally, generally speaking, for the above solution content, aiming at the data exchange objectives involved in the park, this application configures a processing architecture for a specific park data service exchange center, and continues to provide a series of supporting solutions in terms of details. In this way, the application information systems built dispersedly by enterprises can be automatically and intelligently integrated, and low-cost, stable and efficient data exchange services can be realized between the application information systems, meeting the high-quality data exchange requirements of the park for different application information systems.

[0096] More specifically, this application integrates the application information systems built dispersedly, enables several application information systems to transmit and share data, improves the utilization rate of information resources, ensures the interconnection and interoperability between distributed heterogeneous systems, solves data exchange problems such as data collection, update, summary, distribution and consistency, and performs data fusion processing on data from multiple sources that are inconsistent with each other, so as to achieve the goal of data integration in a fast and low-cost manner, and can maintain the independence and expandability flexibility of each application information system.

[0097] In addition, this application also provides a processing system for the park data service exchange center from the perspective of the hardware structure, corresponding to Figure 1 as shown, the processing system of the park data service exchange center includes devices configured with application information systems and the park data service exchange center. For these devices, for the convenience of description, they can be collectively referred to as the devices involved in the processing system of the park data service exchange center. In this regard, refer to Figure 3 , Figure 3 as shown is a schematic structural diagram of the devices involved in the processing system of the park data service exchange center of this application. Specifically, the devices involved in the processing system of the park data service exchange center of this application may include a processor 301, a memory 302, and an input / output device 303. The processor 301 is used to implement each step of the execution subject corresponding to the processing method of the park data service exchange center in the Figure 2 corresponding embodiment when executing the computer program stored in the memory 302.

[0098] Exemplarily, the computer program can be divided into one or more modules / units. One or more modules / units are stored in the memory 302 and executed by the processor 301 to complete this application. One or more modules / units can be a series of computer program instruction segments capable of performing specific functions, and this instruction segment is used to describe the execution process of the computer program in the computer device.

[0099] The devices involved in the processing system of the park data service exchange center may include, but are not limited to, a processor 301, a memory 302, and an input / output device 303. Those skilled in the art can understand that the illustration is only an example of the devices involved in the processing system of the park data service exchange center, and does not constitute a limitation on the devices involved in the processing system of the park data service exchange center. It may include more or fewer components than those shown in the figure, or combine some components, or different components. For example, the devices involved in the processing system of the park data service exchange center may also include network access devices, buses, etc. The processor 301, the memory 302, the input / output device 303, etc. are connected through a bus.

[0100] The processor 301 may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may also be any conventional processor, etc. The processor is the control center of the devices involved in the processing system of the park data service exchange center, and uses various interfaces and lines to connect all parts of the entire device.

[0101] The memory 302 can be used to store computer programs and / or modules. The processor 301 realizes various functions of the computer device by running or executing the computer programs and / or modules stored in the memory 302, and by calling the data stored in the memory 302. The memory 302 may mainly include a program storage area and a data storage area. Among them, the program storage area may store an operating system, application programs required for at least one function, etc.; the data storage area may store data created according to the use of the devices involved in the processing system of the park data service exchange center, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disks, memory, plug-in hard disks, smart media cards (SMCs), secure digital (SD) cards, flash cards, at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage devices.

[0102] When the processor 301 is used to execute the computer program stored in the memory 302, it can specifically implement the functions of the following corresponding execution entities:

[0103] The first device reports a data acquisition request to the park data service exchange center. Among them, the first device is included among different devices, corresponding to the park data service exchange center configured for the target park, and business configuration processing including application registration, application authentication, interface definition, service configuration, interface binding, and subscription creation has been pre-completed for different devices.

[0104] The park data service exchange center extracts the target data reported by the second device in response to the data acquisition request. Among them, the second device is included among different devices.

[0105] The park data service exchange center feeds back the target data to the first device to complete the response to the data acquisition request.

[0106] In an exemplary embodiment, triggered by a locally configured trigger policy or a trigger instruction issued by the park data service exchange center, the third device reports data exchange content to the park data service exchange center.

[0107] The park data service exchange center responds to other data acquisition requests of the fourth device based on the data exchange content.

[0108] In another exemplary embodiment, the park data service exchange center performs business configuration processing including application registration, application authentication, interface definition, service configuration, interface binding, and subscription creation.

[0109] In another exemplary embodiment, for the aspect of application registration, the application types involved include WEB applications, mobile applications, AI applications, algorithm applications, data applications, and 4C client applications.

[0110] In another exemplary embodiment, for the aspect of application registration, the issued address involved is the address for providing an interface or application deployment. The data service exchange center detects whether the network between itself and the current application is unobstructed through the issued address.

[0111] If it is in an unobstructed state, it is determined that the current situation allows for normal data exchange services involved in the current application. If it is not in an unobstructed state, it is determined that the current situation allows for ignoring the data exchange services involved in the current application.

[0112] In another exemplary embodiment, for the aspect of application authentication, the park data service exchange center generates a unique application access identifier for the current device and its application to perform identity verification processing during subsequent data access.

[0113] In yet another exemplary embodiment, with respect to defining the interface, the interface protocols involved specifically include the HTTP / HTTPS protocol, the WEBSERVICE protocol, the MODBUS-TCP protocol, the OPC protocol, and the DB direct connection protocol.

[0114] In yet another exemplary embodiment, the service classifications involved in the configuration service specifically include the received data type and the pushed data type. The subscription numbers involved in creating subscriptions specifically relate to production services and consumption services.

[0115] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the devices involved in the processing system of the above-described park data service exchange center can refer to, for example, Figure 1 the description of the processing method of the park data service exchange center in the corresponding embodiment, and will not be specifically elaborated herein.

[0116] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions, or by controlling relevant hardware through instructions. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0117] Therefore, the present application provides a computer-readable storage medium, which stores multiple instructions that can be loaded by a processor to execute the steps of the processing method of the park data service exchange center in the present application, as Figure 2 described in the corresponding embodiment. The specific operations can refer to, for example, Figure 2 the description of the processing method of the park data service exchange center in the corresponding embodiment, and will not be elaborated herein.

[0118] Among them, the computer-readable storage medium may include: Read Only Memory (ROM), Random Access Memory (RAM), magnetic disk, optical disc, etc.

[0119] Since the instructions stored in the computer-readable storage medium can execute the steps of the processing method of the park data service exchange center in the present application, as Figure 2 described in the corresponding embodiment, the beneficial effects achievable by the processing method of the park data service exchange center in the present application can be realized. For details, see the previous description and will not be elaborated herein. Figure 2

[0120] ​The above has introduced in detail the processing method of the park data service exchange center provided by this application, the processing system of the park data service exchange center, and the computer-readable storage medium. In this article, specific examples are used to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method of this application and its core idea; at the same time, for those skilled in the art, according to the idea of this application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to this application.

Claims

1. A processing method of a campus data service exchange center, characterized in that: The method comprises: The first device reports a data acquisition request to the campus data service exchange center, wherein the first device is included in different devices, and the campus data service exchange center configured in the corresponding target campus has pre-completed business configuration processing including application registration, application authentication, interface definition, service configuration, interface binding, and subscription creation for the different devices, and the different devices are deployed with corresponding application information systems; The campus data service exchange center extracts the target data reported by the second device in response to the data acquisition request, wherein the second device is included in the different devices; The campus data service exchange center feeds back the target data to the first device to complete the response to the data acquisition request.

2. The method according to claim 1, characterized in that The method further comprises: Under the triggering of the locally configured triggering policy or the triggering instruction issued by the campus data service exchange center, the third device reports the data exchange content to the campus data service exchange center; The campus data service exchange center responds to other data acquisition requests of the fourth device based on the data exchange content.

3. The method according to claim 1, characterized in that The method further comprises: The campus data service exchange center performs the business configuration processing including the application registration aspect, the application authentication aspect, the interface definition aspect, the service configuration aspect, the interface binding aspect and the subscription creation aspect.

4. The method according to claim 1, characterized in that: Regarding the registered applications, the application types involved include WEB applications, mobile applications, AI applications, algorithm applications, data applications and 4C client applications.

5. The method according to claim 1, characterized in that Regarding the registered application, the delivery address involved is the address for providing the interface or application deployment, and the data service exchange center detects whether the network between itself and the current application is in a smooth state through the delivery address; If it is in a smooth state, it is determined that the current situation is that the normal data exchange service involved in the current application can be performed; if it is not in a smooth state, it is determined that the current situation is that the data exchange service involved in the current application can be ignored.

6. The method according to claim 1, characterized in that Regarding the application authentication, the campus data service exchange center generates a unique application access identifier for the current device and its application to perform identity authentication processing during subsequent data access.

7. The method according to claim 1, characterized in that Regarding the interface definition, the interface protocols involved specifically include HTTP / HTTPS protocol, WEBSERVICE protocol, MODBUS-TCP protocol, OPC protocol and DB direct connection protocol.

8. The method according to claim 1, characterized in that The service classification involved in the configuration service specifically includes receiving data types and pushing data types, and the subscription number involved in creating a subscription specifically involves production services and consumption services.

9. A campus data service exchange system, characterized in that: Used to perform the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the method according to any one of claims 1 to 8.

Images