CN111131427A - Cross-domain cooperative system based on central domain and implementation method - Google Patents
Cross-domain cooperative system based on central domain and implementation method Download PDFInfo
- Publication number
- CN111131427A CN111131427A CN201911313821.XA CN201911313821A CN111131427A CN 111131427 A CN111131427 A CN 111131427A CN 201911313821 A CN201911313821 A CN 201911313821A CN 111131427 A CN111131427 A CN 111131427A
- Authority
- CN
- China
- Prior art keywords
- domain
- service data
- queue
- receiving
- central
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
Abstract
The invention discloses a cross-domain cooperative system based on a central domain, which relates to the technical field of networks and comprises an initiating domain, the central domain, a receiving domain and a monitoring domain, wherein a message queue middleware with extremely high reliability is introduced, a protocol based on a josn format is adopted, the initiating domain, the central domain, the receiving domain and the monitoring domain are all enabled to face the message queue middleware to send requests, and the requests are waited to respond in a message queue. In terms of lightweight service requests, providing lightweight services in a representational state transfer manner by the target system; in order to solve the problem of low file transmission performance, a special file server is introduced as an intermediate exchange entity file, so that a user can conveniently know the cross-domain service progress in real time, a metadata queue and a log queue are designed to carry out full-flow monitoring on a collaborative process, decoupling among an initiating domain, a central domain, a receiving domain and a monitoring domain is realized through the structural design, the labor cost is reduced, and the robustness and the user experience of a system are improved.
Description
Technical Field
The invention relates to the technical field of networks, in particular to a cross-domain cooperation system based on a central domain and an implementation method.
Background
The existing cross-domain collaboration between systems is mostly implemented based on Simple Object Access Protocol (SOAP) data transmission. SOAP adopts HTTP as communication protocol, sends request through remote procedure call protocol, and uses XML as data interactive format, and the requesting party and the receiving party must mutually open ports. When the system initiates a cross-domain agreement, the initiating unit, the receiving unit, the receiver and the service data are all encapsulated into information such as a message object, a transmission object, a file object and the like, a Uniform Resource Locator (URL) is combined according to an IP address and a port number of the receiving system, a request is initiated through the URL, and after the receiving system receives a sent SOAP request, the information such as the message object, the transmission object, the file object and the like is analyzed, converted into a corresponding service object for storage, and the received information is fed back. The entity file is also transmitted through SOAP, and when a large file is transmitted, the requester cannot respond later.
The prior art has the following defects:
the cooperation is carried out in a remote calling mode, a requester and a receiver are required to mutually open ports, and the system safety is reduced. The remote invocation seriously depends on whether the service provided by the opposite side system is normal or not, the processes of request and receiving are bound together, and the coupling degree is very high. Once the receiving system service is down, the request of the requesting party will display the transmission failure, and it is difficult for the requesting party to determine the error condition. The adoption of SOAP is inefficient in sending attachments when the attachment needs to reach a target system after passing through a plurality of nodes, especially in the case of transmitting a service scene of a large attachment. In addition, SOAP direct sending attachments can be intercepted, and huge loss is brought to users. The log records are also recorded by SOAP, the integrity of the log records cannot be ensured, and the log records cannot be recorded completely when any node in the middle of the transmission process goes down. Particularly, when the heterogeneous systems cooperate, the SOAP encapsulates message objects, transmission objects and file objects, the heterogeneous systems are not transparent, the heterogeneous systems are required to encapsulate corresponding objects, codes between the systems are seriously coupled, and particularly under the condition that different companies are responsible for different systems, the development complexity is high and the labor cost is high.
Disclosure of Invention
In order to solve the defects of the prior art, in a first aspect, an embodiment of the present invention provides a cross-domain collaborative system based on a central domain, where the system includes an initiating domain, a central domain, a receiving domain, and a monitoring domain, where:
the initiating domain is used for sending the service data to the central domain;
the central domain is used for receiving the service data and acquiring the identification, the number, the name and the version of the service data, so that the service data can be conveniently inquired subsequently;
the central domain is further configured to send the service data to the receiving domain;
the receiving domain is used for analyzing the service data and generating task information and opinion information according to an analysis result; the task information comprises a task name, a task handler, task creation time and a task state, wherein the task state comprises sending, receiving and finishing, and the opinion information comprises a signer name, signing time, whether to agree or not and opinion content;
and the monitoring domain is used for recording the interactive process among the initiating domain, the central domain and the receiving domain.
Preferably, the initiating domain configures an initiating domain queue, and the initiating domain queue is configured to send service data to the central domain.
Preferably, the central domain configures a central domain queue, where the central domain queue is configured to receive the service data sent by the initiating domain and forward the service data to the receiving domain.
Preferably, the receiving domain configures a receiving domain queue, where the receiving domain queue is used to receive the service data forwarded by the central domain.
Preferably, the monitoring domain configures a metadata queue and a log queue, wherein the metadata queue is used for recording attribute information of the service data, the attribute information includes a document number, a document name, an initiating domain identifier, an initiating domain name, a receiving domain identifier, a receiving domain name, a document state, creation time and exception information, and the document state includes new creation, failed transmission, processing, exception and completion;
the log queue is configured to record an interaction process among the initiating domain, the central domain, and the receiving domain, where the interaction process includes: the initiating domain, the central domain and the receiving domain process business data progress, a current domain, an operator, operation time and operation content.
Preferably, the service data includes a josn file, an xml file, and an entity file.
Preferably, the initiating domain configures a first retry queue, the central domain configures a second retry queue, and the receiving domain configures a third retry queue, where the first retry queue is used to repair the abnormal service data processed by the initiating domain, the second retry queue is used to repair the abnormal service data processed by the central domain, and the third retry queue is used to repair the abnormal service data processed by the receiving domain.
Preferably, the originating domain configures a first pending queue, the central domain configures a second pending queue, and the receiving domain configures a third pending queue, where the first pending queue is used to store the service data requiring manual intervention in the originating domain, the second pending queue is used to store the service data requiring manual intervention in the central domain, and the third pending queue is used to store the service data requiring manual intervention in the receiving domain.
In a second aspect, an embodiment of the present invention provides a method for implementing cross-domain collaboration by using the cross-domain collaboration system based on a central domain set forth in the first aspect, where the method includes the following steps:
packaging service data by using an initiating domain, transmitting the service data to a central domain by using a file server uploading service, creating metadata corresponding to the service data and generating a corresponding log, and transmitting the metadata and the log to a monitoring domain;
the central domain queue acquires the identification, the number, the name and the version of the service data, generates a corresponding log, sends the service data to a receiving domain and sends the log to the monitoring domain;
the receiving domain analyzes the service data, generates task information, opinion information and corresponding logs according to an analysis result, sends the task information and the opinion information to the central domain, and sends the logs to the monitoring domain;
the central domain receives the task information and the opinion information, generates a corresponding log, forwards the task information and the opinion information to the initiating domain and sends the log to the monitoring domain;
and the initiating domain receives and stores the task information and the opinion information, generates a corresponding log and sends the log to the monitoring domain.
The cross-domain cooperative system based on the central domain and the implementation method thereof provided by the embodiment of the invention have the following beneficial effects:
(1) in the interactive process of the service data, all the systems face the message queue middleware by adopting the message queue, so that the mutual coupling among the systems is realized, and the labor cost is reduced;
(2) the lightweight service of the expression state transfer mode is provided, the development difficulty is reduced, and the service performance is improved;
(3) a special file server is erected to provide file uploading and downloading functions, and file transmission efficiency is improved;
(4) the metadata queue and the log queue are introduced to uniformly record the logs, log query service is provided, the consistency of users participating in the cooperation process is ensured, and the robustness of the system and the user experience in the cooperation process are improved.
Drawings
Fig. 1 is a structural diagram of a cross-domain collaborative system based on a central domain according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the following embodiments and accompanying drawings. The illustrative embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention to the embodiments and descriptions of the present invention.
Noun interpretation
Domain: the system deployed by one unit is called a domain, and information such as an IP address, a system number, a system name, a system version and the like is encapsulated.
A central domain: the domain designated as the data center is called a central domain, all domains need to be registered with the central domain, and the central domain pushes all registered domain information to connected systems and records and stores collaborative data of all systems.
Cross-domain collaboration: refers to the process of sending, receiving and feeding back data among different domains.
As a specific embodiment, referring to fig. 1, a cross-domain collaboration system based on a central domain provided by an embodiment of the present invention includes: the method comprises an initiating domain, a central domain, a receiving domain and a monitoring domain, wherein:
the initiating domain is used for sending the service data to the central domain.
The central domain is used for receiving the service data and acquiring the identification, the number, the name and the version of the service data, so that the service data can be conveniently inquired subsequently.
The central domain is also used to send the service data to the receiving domain.
The receiving domain is used for analyzing the service data and generating task information and opinion information according to an analysis result; the task information comprises a task name, a task processor, task creation time and a task state, the task state comprises sending, receiving and finishing, and the opinion information comprises a signer name, signing time, whether to agree or not and opinion content.
And the monitoring domain is used for recording the interaction process among the initiating domain, the central domain and the receiving domain.
Optionally, the originating domain configures an originating domain queue, and the originating domain queue is used for sending the service data to the central domain.
Optionally, the central domain is configured with a central domain queue, and the central domain queue is configured to receive the service data sent by the originating domain and forward the service data to the receiving domain.
Optionally, the receiving domain configures a receiving domain queue, where the receiving domain queue is used to receive the service data forwarded by the central domain.
Optionally, a monitoring domain configures a metadata queue and a log queue, wherein the metadata queue is used for recording attribute information of the service data, the attribute information includes a document number, a document name, an initiating domain identifier, an initiating domain name, a receiving domain identifier, a receiving domain name, a document state, creation time and abnormal information, and the document state includes new creation, failed transmission, processing, abnormal occurrence and completed completion;
the log queue is used for recording the interactive process among the initiating domain, the central domain and the receiving domain, wherein the interactive process comprises the following steps: the initiating domain, the central domain and the receiving domain process the service data progress, the current domain, the operator, the operation time and the operation content.
Optionally, the business data includes a josn file, an xml file, and an entity file.
Optionally, the initiating domain configures a first retry queue, the central domain configures a second retry queue, and the receiving domain configures a third retry queue, where the first retry queue is used to repair the service data processed abnormally by the initiating domain, the second retry queue is used to repair the service data processed abnormally by the central domain, and the third retry queue is used to repair the service data processed abnormally by the receiving domain.
Optionally, the originating domain configures a first pending queue, the central domain configures a second pending queue, and the receiving domain configures a third pending queue, where the first pending queue is used to store the service data that needs manual intervention in the originating domain, the second pending queue is used to store the service data that needs manual intervention in the central domain, and the third pending queue is used to store the service data that needs manual intervention in the receiving domain.
The invention provides a cross-domain cooperative system based on a central domain, which relates to the technical field of networks and comprises an initiating domain, the central domain, a receiving domain and a monitoring domain, wherein a message queue middleware with extremely high reliability is introduced, a protocol based on a josn format is adopted, the initiating domain, the central domain, the receiving domain and the monitoring domain are enabled to face the message queue middleware to send requests, and the requests are waited to respond in a message queue. In terms of lightweight service requests, providing lightweight services in a representational state transfer manner by the target system; in order to solve the problem of low file transmission performance, a special file server is introduced as an intermediate exchange entity file, so that a user can conveniently know the cross-domain service progress in real time, a metadata queue and a log queue are designed to carry out full-flow monitoring on a collaborative process, decoupling among an initiating domain, a central domain, a receiving domain and a monitoring domain is realized through the structural design, the labor cost is reduced, and the robustness and the user experience of a system are improved.
As another specific embodiment, an embodiment of the present invention provides a method for implementing cross-domain collaboration by using the cross-domain collaboration system based on a central domain provided in the first aspect, where the method includes the following steps:
packaging the service data by using an initiating domain, transmitting the service data to a central domain by using a file server uploading service, creating metadata corresponding to the service data and generating a corresponding log, and transmitting the metadata and the log to a monitoring domain;
the central domain queue acquires the identification, the number, the name and the version of the service data, generates a corresponding log, sends the service data to a receiving domain and sends the log to a monitoring domain;
receiving domain analysis service data, generating task information, opinion information and corresponding logs according to analysis results, sending the task information and the opinion information to a central domain, and sending the logs to a monitoring domain;
the central domain receives the task information and the opinion information, generates a corresponding log, forwards the task information and the opinion information to an initiating domain and sends the log to the monitoring domain;
and the initiating domain receives and stores the task information and the opinion information, generates a corresponding log and sends the log to the monitoring domain.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
It will be appreciated that the relevant features of the method and apparatus described above are referred to one another. In addition, "first", "second", and the like in the above embodiments are for distinguishing the embodiments, and do not represent merits of the embodiments.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In addition, the memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (9)
1. A cross-domain cooperative system based on a central domain is characterized by comprising an initiating domain, the central domain, a receiving domain and a monitoring domain, wherein:
the initiating domain is used for sending the service data to the central domain;
the central domain is used for receiving the service data and acquiring the identification, the number, the name and the version of the service data, so that the service data can be conveniently inquired subsequently;
the central domain is further configured to send the service data to the receiving domain;
the receiving domain is used for analyzing the service data and generating task information and opinion information according to an analysis result; the task information comprises a task name, a task handler, task creation time and a task state, wherein the task state comprises sending, receiving and finishing, and the opinion information comprises a signer name, signing time, whether to agree or not and opinion content;
and the monitoring domain is used for recording the interactive process among the initiating domain, the central domain and the receiving domain.
2. The domain-centric based cross-domain collaboration system of claim 1,
and the initiating domain configures an initiating domain queue, wherein the initiating domain queue is used for sending the service data to the central domain.
3. The domain-centric based cross-domain collaboration system of claim 1,
and the central domain is configured with a central domain queue, and the central domain queue is used for receiving the service data sent by the initiating domain and forwarding the service data to the receiving domain.
4. The domain-centric based cross-domain collaboration system of claim 1,
and configuring a receiving domain queue by the receiving domain, wherein the receiving domain queue is used for receiving the service data forwarded by the central domain.
5. The domain-centric based cross-domain collaboration system of claim 1,
the monitoring domain is configured with a metadata queue and a log queue, wherein the metadata queue is used for recording attribute information of the service data, the attribute information comprises a document number, a document name, an initiating domain identifier, an initiating domain name, a receiving domain identifier, a receiving domain name, a document state, creation time and abnormal information, and the document state comprises new creation, failed transmission, processing, abnormal occurrence and completion;
the log queue is configured to record an interaction process among the initiating domain, the central domain, and the receiving domain, where the interaction process includes: the initiating domain, the central domain and the receiving domain process business data progress, a current domain, an operator, operation time and operation content.
6. The domain-centric based cross-domain collaboration system of claim 1,
the service data comprises a josn file, an xml file and an entity file.
7. The center-domain based cross-domain collaborative system according to any one of claims 1-6,
the initiating domain is configured with a first retry queue, the central domain is configured with a second retry queue, and the receiving domain is configured with a third retry queue, wherein the first retry queue is used to repair the abnormal service data processed by the initiating domain, the second retry queue is used to repair the abnormal service data processed by the central domain, and the third retry queue is used to repair the abnormal service data processed by the receiving domain.
8. The center-domain based cross-domain collaborative system according to any one of claims 1-6,
the initiating domain configures a first pending queue, the central domain configures a second pending queue, and the receiving domain configures a third pending queue, where the first pending queue is used to store the service data requiring manual intervention in the initiating domain, the second pending queue is used to store the service data requiring manual intervention in the central domain, and the third pending queue is used to store the service data requiring manual intervention in the receiving domain.
9. A method for implementing cross-domain collaboration using the center-domain based cross-domain collaboration system as claimed in any one of claims 1 to 8, comprising:
packaging service data by using an initiating domain, sending the service data to a central domain by using a file server, creating metadata corresponding to the service data and generating a corresponding log, and sending the metadata and the log to a monitoring domain;
the central domain queue acquires the identification, the number, the name and the version of the service data, generates a corresponding log, sends the service data to a receiving domain and sends the log to the monitoring domain;
the receiving domain analyzes the service data, generates task information, opinion information and corresponding logs according to an analysis result, sends the task information and the opinion information to the central domain, and sends the logs to the monitoring domain;
the central domain receives the task information and the opinion information, generates a corresponding log, forwards the task information and the opinion information to the initiating domain and sends the log to the monitoring domain;
and the initiating domain receives and stores the task information and the opinion information, generates a corresponding log and sends the log to the monitoring domain.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911313821.XA CN111131427B (en) | 2019-12-19 | 2019-12-19 | Cross-domain cooperative system based on central domain and implementation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911313821.XA CN111131427B (en) | 2019-12-19 | 2019-12-19 | Cross-domain cooperative system based on central domain and implementation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111131427A true CN111131427A (en) | 2020-05-08 |
| CN111131427B CN111131427B (en) | 2022-09-23 |
Family
ID=70498425
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911313821.XA Active CN111131427B (en) | 2019-12-19 | 2019-12-19 | Cross-domain cooperative system based on central domain and implementation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111131427B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150312378A1 (en) * | 2014-04-28 | 2015-10-29 | Oracle International Corporation | System and method for supporting a proxy model for across-domain messaging in a transactional middleware machine environment |
| CN106095957A (en) * | 2016-06-16 | 2016-11-09 | 北京航空航天大学 | Cross-domain many wave files synchronous method of distributed file system and device |
| CN108777699A (en) * | 2018-04-13 | 2018-11-09 | 西安电子科技大学 | A kind of application cross-domain access method under the domain collaborative multi framework based on Internet of Things |
| CN110321273A (en) * | 2019-07-09 | 2019-10-11 | 政采云有限公司 | A kind of business statistical method and device |
| CN110365790A (en) * | 2019-07-23 | 2019-10-22 | 深圳市东微智能科技股份有限公司 | Method for message transmission, device, cascade network equipment and readable storage medium storing program for executing |
-
2019
- 2019-12-19 CN CN201911313821.XA patent/CN111131427B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150312378A1 (en) * | 2014-04-28 | 2015-10-29 | Oracle International Corporation | System and method for supporting a proxy model for across-domain messaging in a transactional middleware machine environment |
| CN106095957A (en) * | 2016-06-16 | 2016-11-09 | 北京航空航天大学 | Cross-domain many wave files synchronous method of distributed file system and device |
| CN108777699A (en) * | 2018-04-13 | 2018-11-09 | 西安电子科技大学 | A kind of application cross-domain access method under the domain collaborative multi framework based on Internet of Things |
| CN110321273A (en) * | 2019-07-09 | 2019-10-11 | 政采云有限公司 | A kind of business statistical method and device |
| CN110365790A (en) * | 2019-07-23 | 2019-10-22 | 深圳市东微智能科技股份有限公司 | Method for message transmission, device, cascade network equipment and readable storage medium storing program for executing |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111131427B (en) | 2022-09-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108416577B (en) | Block chain service system | |
| US11050607B2 (en) | Proxy with a function as a service (FAAS) support | |
| KR102136945B1 (en) | Service implementation method, device and system based on FIX protocol | |
| CN111327662B (en) | Communication method and management device of heterogeneous Internet of things platform | |
| CN107133231B (en) | Data acquisition method and device | |
| CN112055078B (en) | Data transmission method, device, computer equipment and storage medium | |
| CN112492054A (en) | Multiplexing method, device and equipment for UDP (user Datagram protocol) port | |
| CN112838940A (en) | Network controller framework and data processing method | |
| CN113612686A (en) | Traffic scheduling method and device and electronic equipment | |
| CN105099769A (en) | Method, device and system for processing abnormal operations of service platform | |
| CN114040032A (en) | Protocol conversion method, system, storage medium and electronic equipment | |
| CN114465867A (en) | Server maintenance method and device, storage medium and processor | |
| CN114598749A (en) | Service access method and device | |
| CN111131427B (en) | Cross-domain cooperative system based on central domain and implementation method | |
| CN110620819B (en) | Block chain interaction method and device, computer equipment and readable storage medium | |
| CN111526028B (en) | Data processing method, device and equipment | |
| EP4042649A1 (en) | A method of capturing packets from a container in a cluster background | |
| CN114553666B (en) | Channel event reporting method, system, device and storage medium | |
| CN113746794B (en) | Account processing method and device, electronic equipment and computer storage medium | |
| CN110581826B (en) | Core network communication method, device and system | |
| US11582345B2 (en) | Context data management interface for contact center | |
| CN109600403B (en) | Method and device for sending information | |
| CN112165529A (en) | Method, device, equipment and medium for low-cost cross-network data exchange | |
| CN111913789A (en) | Program tracking method, device and medium supporting micro-service architecture | |
| CN115297066B (en) | Resource dynamic cooperation method, device, server and medium |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 100094 No. 28, Yongfeng Road, Beijing, Haidian District Applicant after: Beijing Shenzhou Aerospace Software Technology Co.,Ltd. Address before: 100094 No. 28, Yongfeng Road, Beijing, Haidian District Applicant before: BEIJING SHENZHOU AEROSPACE SOFTWARE TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |