CN117082146B - Cross-service multi-judicial service comprehensive integrated scheduling system - Google Patents

Cross-service multi-judicial service comprehensive integrated scheduling system Download PDF

Info

Publication number
CN117082146B
CN117082146B CN202311328275.3A CN202311328275A CN117082146B CN 117082146 B CN117082146 B CN 117082146B CN 202311328275 A CN202311328275 A CN 202311328275A CN 117082146 B CN117082146 B CN 117082146B
Authority
CN
China
Prior art keywords
service
request
interface
data
unit
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
Application number
CN202311328275.3A
Other languages
Chinese (zh)
Other versions
CN117082146A (en
Inventor
许建峰
孙福辉
陈奇伟
董玉红
崔衍
黄国栋
李晓慧
张雅雯
丁峰
郭新刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Judicial Big Data Research Institute Co ltd
People's Court Information Technology Service Center
Original Assignee
China Judicial Big Data Research Institute Co ltd
People's Court Information Technology Service Center
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Judicial Big Data Research Institute Co ltd, People's Court Information Technology Service Center filed Critical China Judicial Big Data Research Institute Co ltd
Priority to CN202311328275.3A priority Critical patent/CN117082146B/en
Publication of CN117082146A publication Critical patent/CN117082146A/en
Application granted granted Critical
Publication of CN117082146B publication Critical patent/CN117082146B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
    • H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Abstract

The specification provides a multi-element judicial service integrated dispatching system crossing services, comprising: a service registration management unit for acquiring the service packaged according to the first interface specification and distributing Token information; the service proxy unit receives the service request of each service unit through the unified integrated access module, and opens a unified integrated page of the corresponding service according to the service request and the first authentication information; establishing a mapping relation between knowledge service and business units through a national service routing module; establishing a mapping relation among the business unit, the knowledge service and the business data through a national service routing module and a standardized interface management module; the service units send service requests through the unified integrated interface, receive service processing results fed back by the service proxy units and send service data through the data unified interface; the service units can be connected with each other in a unified integrated access mode, so that the connection efficiency is improved.

Description

Cross-service multi-judicial service comprehensive integrated scheduling system
Technical Field
The invention relates to the technical field of computer software, in particular to a cross-service multi-judicial service comprehensive integrated scheduling system.
Background
At present, a large number of mature and applicable intelligent knowledge services exist in the whole country, but as various services are developed by different manufacturers by adopting different technical systems, service interfaces are not uniform, interface parameters of various business units of an organization are not consistent, one-to-one connection with the business units of the organization is needed, if the knowledge services need to call data information such as cases, files, documents and the like of the business units of the organization, the knowledge services also need to be connected with related data interfaces of the business units of the organization, so that the popularization and application of the existing intelligent knowledge services in the whole country are greatly limited.
However, as service manufacturers scatter and service interfaces are not uniform, problems of complex butt joint, repeated butt joint, low butt joint efficiency and the like exist when the intelligent knowledge service is in butt joint with a service unit of an organization, and national large-scale popularization and application of the existing intelligent knowledge service are limited. In order to solve the problems, a comprehensive integrated scheduling scheme is provided for the existing multi-element intelligent knowledge service, the ideal goal of one-time butt joint of the knowledge service and nationwide use is achieved, and the intelligent level of political work is improved by assistance.
Disclosure of Invention
Aiming at the problems in the prior art, the aim of the specification is to provide a multi-element judicial service integrated dispatching system for cross-service so as to solve the problems of complex butt joint, repeated butt joint, low butt joint efficiency and the like in the prior art when intelligent knowledge service is used for butt joint of a mechanism service unit.
In order to solve the technical problems, the specific technical scheme in the specification is as follows:
in one aspect, the present disclosure provides a cross-business, multi-judicial service integrated scheduling system, including:
the service registration management unit is used for issuing a first interface specification, acquiring a service packaged according to the first interface specification, and distributing Token information to a business unit applying the service;
the service agent unit is used for receiving the service request of each service unit, and opening a corresponding service unified integrated page according to the service request and first authentication information, wherein the first authentication information is generated according to the user ID of the service unit and Token information of the service unit; the service unit is used for calling the service data stored by the service unit and enabling the service to process the service data; the service processing unit is used for processing the service and obtaining a processing result;
And the service units are used for sending service data through a data unified interface, sending service request parameters to the service proxy unit through a unified integrated interface and receiving the processing results forwarded by the service proxy unit, wherein the data unified interface and the unified integrated interface accord with a second interface specification.
As an embodiment of the present specification, the service agent unit includes:
the unified integrated access module is used for receiving the service request according to the service unified integrated access interface of the service unit, authenticating the service request according to a first authentication instruction of the security control module, encrypting a request parameter after authentication is completed, and sending the encrypted request parameter to the national service routing module;
the national service routing module is used for receiving a service request and opening a routing address of the requested service according to a second authentication instruction of the security control module; the system is also used for receiving the data request of the requested service, forwarding the data request parameters to the standardized interface management module to acquire service data, and forwarding the service processing result of the service to the unified integrated access module;
The standardized interface management module is configured to dock the data unified interface of the service unit according to the second interface specification, obtain service data in the service unit through the data unified interface according to the service request and third authentication information, and send the service data to the national service routing module, where the data unified interface includes a case unified interface, a file unified interface and a document unified interface;
the security control module is used for encrypting a service request sent by a service unit by adopting an encryption algorithm and also used for verifying whether the service unit has permission to open the unified integrated page by using the first authentication instruction; the service unit is further used for verifying whether the service unit has permission to open a service page or not by using the second authentication instruction; and the third authentication instruction is used for verifying whether the service request has authority to call the data unifying interface.
As one embodiment of the present specification, the services of the service registration management unit include a page service and an API service;
when the business unit calls the page service, the unified integrated page is opened through the unified integrated access module, and the quick switching of each service is performed through the unified integrated page; after the unified integrated access module receives the response result of the page service, the response result is fed back to a target service page of the unified integrated page;
And when the service unit calls the API service, the unified integrated access module directly feeds back the received service response result to the service unit.
As an embodiment of the present specification, further comprising:
the service unified integrated access interface is used for sending the service request sent by the service unit to the service proxy unit; the service agent unit is used for forwarding the service processing result to the service unit;
when the service unit initiates a service request to a service proxy unit, a request header containing Token information and user information identification and request parameters containing information such as a case number, a case identification, a service ID, an interface ID, a signature, a manager and the like are transmitted to the unified integrated access module through the service unified integrated access interface; and after the service is processed to obtain a calculation result, returning a service result to the service unit through the service unified integrated access interface.
As one embodiment of the present specification, the national service routing module includes a proxy gateway and a service status monitoring control;
the proxy gateway is used for inquiring a service address matched with the service request parameter according to the service request and sending a request service parameter to the service address, wherein the request service parameter is determined according to the unified integrated access service request; the system is also used for inquiring the address of the data unified interface matched with the service request parameters according to the service request, and sending the service request parameters and the address to the standardized interface management module, wherein the request parameters of the inquired data are determined according to the service request;
The service state monitoring control is used for monitoring the running state of the service and giving an alarm when the service is in downtime or overload running.
As one embodiment of the present specification, the service broker gateway includes a knowledge service broker gateway;
when a service unit is accessed to knowledge service of the service registration management unit in a unified way, token information is uniformly distributed to the service unit through the service registration management unit so as to define service calling authority of the service unit;
when a service unit accesses a service, the service unit maps to the real address of the proxied service through the gateway URL set by the knowledge service proxy gateway so that the service unit uses the service.
As one embodiment of the present specification, the proxy gateway includes a data unification interface proxy gateway;
the data unified interface proxy gateway counts the data convergence condition of each province according to a preset list, and for the provinces with data convergence, the national service routing module directly initiates routing to the data unified interface of the province advanced organization: after the national service routing module receives a request of service for service data in a service unit, the request parameter and a routing address matched with the request parameter are sent to the standardized interface management module; the standardized interface management module extracts key information in the request parameters and then routes the key information to a unified data interface of the provincial high-level institution to acquire corresponding service data;
For provinces of incomplete data aggregation, the national service routing module carries out multi-level routing on each level mechanism of the province, and after receiving a request of service on the service data, the national service routing module sends request parameters and routing addresses matched with the request parameters to the standardized interface management module; the standardized interface management module extracts key information in the request parameters, further matches the routing address of the corresponding mechanism data interface according to the request parameters, and further maps the routing address to the real address of the corresponding hierarchical mechanism data interface through the service proxy gateway and invokes service data.
As an embodiment of the present specification, the case unifying interface includes a case number obtaining interface and a case information query interface;
the obtained case number interface is used for inquiring the case number meeting the conditions by the target service;
responding to the target service to inquire the number of cases, and transmitting a data inquiry request head containing Token information, user information identification, request id and signature information to the standardized interface management module by the target service through the national service routing module; the security control module authenticates the query request by using a third authentication instruction, and if authentication is performed, a first request parameter set is sent to an acquired case number interface of a service unit through the standardized interface management module, wherein the first request parameter set comprises an accurate case number, a manager, a case type, a case date, a modification time, a contractor and a case person; the standardized interface management module obtains a query result according to the first request parameter set and sends the query result to the target service through the national service routing module;
The case information query interface is used for querying basic information of the case by the target service;
responding to the basic information of the target service query case, and transmitting a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module by the target service through the national service routing module; the security control module authenticates the data query request head by using a third authentication instruction, and if authentication is passed, the standardized interface management module initiates a case information query interface calling request and sends a second request parameter set to the case information query interface, wherein the second request parameter set comprises a case identifier, an accurate case number, a manager, a case type, the number of result sets, an offset, a case date, a modification time, a contractor and a case person; and the standardized interface management module acquires a query result according to the second request parameter set and feeds the query result back to the target service through the national service routing module.
As one embodiment of the present specification, the file unifying interface includes a file total information acquiring interface and a single material downloading interface in the file;
The volume total information interface is used for acquiring the total catalog and the material information of the volume;
the method comprises the steps that a target service is responded to obtain a full-volume catalog and material information of a file, and the target service transmits a data query request head containing Token information, user information identification, request id and signature information to a standardized interface management module through a national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, initiates a request for calling a volume full information acquisition interface to the standardized interface management module and sends a third request parameter set to the volume full information acquisition interface, wherein the third request parameter set comprises a case number, a case identification and a distributed deployment condition; the standardized interface management module obtains a query result according to the third request parameter set and sends the query result to the target service through the national service routing module;
the single material downloading interface in the file is used for downloading the single material in the file;
when the target service requests downloading, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, the standardized interface management module transmits a fourth request parameter set to a single material download interface in the file, wherein the fourth request parameter set comprises a document number, a case identification, an id value corresponding to a root node and a code value of a sponsor organization; and the standardized interface management module acquires a downloading result according to the fourth request parameter set and sends the downloading result to the target service unit in a binary file stream form through the national service routing module.
As one embodiment of the present specification, the document unified interface includes a document information acquiring interface and a document entity acquiring interface;
the document information acquisition interface is used for acquiring document information related to the case;
when a target service obtains document information related to a case, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if authentication is passed, the standardized interface management module requests the acquired case document information interface and transmits a fifth request parameter set to the acquired case document information interface, wherein the fifth request parameter set comprises a case number, a case identifier, a document type, a secondary document type and a code value of a manager; the standardized interface management module obtains a result according to the fifth request parameter set and sends a query result to the target service through the national service routing module;
the method comprises the steps that a single document entity interface is obtained and used for downloading a single document in a document;
When the target service downloads a single document in the document, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, the standardized interface management module transmits a sixth request parameter set to the acquired single document entity interface, wherein the sixth request parameter set comprises a case number, a case identification, a document number, a document type and a code value of a sponsor organization; and the standardized interface management module acquires a downloading result according to the request parameters and sends the downloading result to the target service in a binary file stream form through the national service routing module.
As one embodiment of the present specification, the system further comprises a success acquisition analysis module;
the achievement collection analysis module is used for carrying out buried point recording on the behavior of calling service by the business unit at the unified integrated access module; the achievement collection analysis module is also used for evaluating the dispatching system according to the service calling behavior of the business unit.
By adopting the technical scheme, all service interfaces are unified through the first interface specification, knowledge services issued by all service manufacturers are acquired, and then the data unified interfaces and unified integrated interfaces of the business units of the mechanism are modified according to the second interface specification, so that all services can be conveniently and rapidly docked with the business units through the unified interfaces, and the docking efficiency is improved.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments, as illustrated in the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 illustrates a topology diagram of a cross-business, multi-judicial service integrated scheduling system according to an embodiment of the present disclosure;
FIG. 2 illustrates a detailed topology of a cross-business, multi-judicial service integrated scheduling system according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram showing the coordination among the modules of the multi-judicial service integrated dispatching system of the cross-business embodiment of the present disclosure;
fig. 4 shows a schematic diagram of a computer device according to an embodiment of the present description.
Description of the drawings:
402. a computer device;
404. a processor;
406. a memory;
408. a driving mechanism;
410. an input/output module;
412. an input device;
414. an output device;
416. a presentation device;
418. a graphical user interface;
420. a network interface;
422. a communication link;
424. a communication bus.
Detailed Description
The technical solutions of the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.
It should be noted that the terms "first," "second," and the like in the description and the claims, and in the foregoing figures, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the present description described herein may be capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or device.
A topology diagram of a cross-business, multi-judicial service integrated scheduling system, as shown in fig. 1, comprising:
the service registration management unit is used for issuing a first interface specification, acquiring a service packaged according to the first interface specification, and distributing Token information to the service;
the service agent unit is used for receiving the service request of each service unit, and opening a corresponding service unified integrated page according to the service request and first authentication information, wherein the first authentication information is generated according to the user ID of the service unit and Token information of the service unit; the service unit is used for calling the service data stored by the service unit and enabling the service to process the service data; the service processing unit is used for processing the service and obtaining a processing result;
and the service units are used for sending service data through a data unified interface, sending service request parameters to the service proxy unit through a unified integrated interface and receiving the processing results forwarded by the service proxy unit, wherein the data unified interface and the unified integrated interface accord with a second interface specification.
By adopting the technical scheme, all service interfaces are unified through the first interface specification, knowledge services issued by all service manufacturers are acquired, and then the data unified interfaces and unified integrated interfaces of the business units of the mechanism are modified according to the second interface specification, so that all services can be conveniently and rapidly docked with the business units through the unified interfaces, and the docking efficiency is improved.
In the specification, a first interface specification is formulated for the highest-level organization, and the first interface specification prescribes the specifications of service use interfaces produced by all service manufacturers, so that all services use a uniform interface, and organizations in different areas can conveniently dock with all the services. When the service needs to be added into the dispatching system, the service registration management module tests whether an interface used by the service is consistent with an interface instance specified by the first interface specification, if so, the service is adopted and registered, and then Token information is distributed to service units subscribed to the service which is successfully registered.
In this specification, the service proxy unit is mainly used for connecting a service with a service unit used by an organization, providing the service for the service unit, and using service data of the organization to make the service run, so as to finally obtain a processing result required by the organization. Services in this specification include case-standing assistance, principal portrayal, speech recognition, canonical sentency intelligence assistance, case-like intelligence push, etc.
In the present specification, in order to make the service unit use services conveniently and smoothly, the data unified interfaces and the unified integration interfaces of the service unit in each place in the present specification are all obtained by modification according to the second interface specification. In this specification, a data unified interface is an interface for a service unit to send service data. Currently, because the data unified interfaces of the service units in all places are inconsistent, for example, the data unified interface of the data transmission unit of the service unit A is of type A, and the data unified interface of the data transmission unit of the service unit B is of type B. If the service unit A and the service unit B both need to use the service C, if the service C only supports the data unified interface of the type A, the service unit B cannot use the service C, so that the office efficiency of the service unit B is affected, and the service C is not beneficial to popularization. Therefore, the data unifying interface types of the service units are required to be unified, and each service is convenient to call.
In addition, the service agent unit in the specification provides an integrated framework, through which the page type service can be rapidly switched, so that the service unit service efficiency is improved, but the integrated framework needs the service unit to be acquired by using a unified integrated interface matched with the service unit type, so that the unified integrated interfaces of all the service units in the specification are modified according to the second interface specification. After transformation is completed, the unified integrated interface of the service unit in the specification can conveniently and rapidly receive the integrated frame, for example, when the service unit needs to use three services, if the three services are page type services, the integrated frame can be contacted with all the services and displays one of the services, when the service unit needs to display other services, the operation of repeatedly butting the service by the service unit can be avoided through rapid switching of the integrated frame, and the service butting efficiency is improved.
A detailed topology of a cross-business, multi-judicial service integrated scheduling system, as shown in fig. 2, the service agent unit comprising:
the unified integrated access module is used for receiving the service request according to the service unified integrated access interface of the service unit, authenticating the service request according to a first authentication instruction of the security control module, encrypting a request parameter after authentication is completed, and sending the encrypted request parameter to the national service routing module;
The national service routing module is used for receiving a service request and opening a routing address of the requested service according to a second authentication instruction of the security control module; the system is also used for receiving the data request of the requested service, forwarding the data request parameters to the standardized interface management module to acquire service data, and forwarding the service processing result of the service to the unified integrated access module;
the standardized interface management module is configured to dock the data unified interface of the service unit according to the second interface specification, obtain service data in the service unit through the data unified interface according to the service request and third authentication information, and send the service data to the national service routing module, where the data unified interface includes a case unified interface, a file unified interface and a document unified interface;
the security control module is used for encrypting a service request sent by a service unit by adopting an encryption algorithm and also used for verifying whether the service unit has permission to open the unified integrated page by using the first authentication instruction; the service unit is further used for verifying whether the service unit has permission to open a service page or not by using the second authentication instruction; and the third authentication instruction is used for verifying whether the service request has authority to call the data unifying interface.
As one embodiment herein, the services of the service registration management unit include a page service and an API service;
when the business unit calls the page service, the unified integrated page is opened through the unified integrated access module, and the quick switching of each service is performed through the unified integrated page; after the unified integrated access module receives the response result of the page service, the response result is fed back to a target service page of the unified integrated page;
and when the service unit calls the API service, the unified integrated access module directly feeds back the received service response result to the service unit.
For API service (including API service-A class and API service-B class), the specification provides an API service calling interface for the business unit through the unified integrated access module, so that unified scheduling of the business unit on the API service is realized.
In order to facilitate understanding of the coordination relationship between the modules, the present disclosure will be described in terms of steps of sending a service request by a service unit and then receiving a processing result after service operation, as shown in fig. 3, which is a schematic diagram of coordination between modules of the cross-service multi-judicial service integrated dispatching system.
Step 301, a service unit initiates a service request to a unified integrated access module.
Step 302, the security control module uses the first authentication information to determine whether the registration information of the service unit is consistent, that is, whether Token information corresponding to the user ID is consistent with the reserved Token; if not, go to step 303; if so, step 304 is performed.
Step 303, refusing to provide service to the business unit.
Step 304, determining whether the unified integration page needs to be opened according to the service request, if not, executing 306, and if so, executing 305.
And 305, the unified integrated access module opens a unified integrated page according to the service request.
Step 306, the security control module encrypts the service request and sends the encrypted service request to the national service routing module.
Step 307, the security control module uses the second authentication instruction to determine whether the service unit has the access target service authority, if not, step 308 is executed, and if so, step 309 is executed.
Step 308, refusing to provide service to the business unit.
Step 309, determining whether the service needs to use the unified data interface according to the service request parameter, if so, executing step 310, and if not, executing step 315.
Step 310, the security control module uses the third authentication instruction to determine whether the service unit has the authority to invoke the unified interface, if not, step 311 is executed, and if so, step 312 is executed;
step 311, refusing to provide service to the business unit.
Step 312, the national service routing module determines the address of the calling data interface and sends the data request parameter to the standardized interface management module;
step 313, the standardized interface management module invokes the unified interface data according to the request parameters and sends the data to the national service routing module.
Step 314, the national service routing module adds the business data to the service request.
Step 315, the national service routing module sends the service request to the target service to obtain the processing result of the target service, and returns to the unified integrated access module.
And step 316, the unified integrated access module displays the processing result of the page service by using the unified integrated page, or sends the processing result of the API service to the business unit.
As an embodiment of the present specification, the case unifying interface includes a case number obtaining interface and a case information query interface;
the obtained case number interface is used for inquiring the case number meeting the conditions by the target service;
Responding to the target service to inquire the number of cases, and transmitting a data inquiry request head containing Token information, user information identification, request id and signature information to the standardized interface management module by the target service through the national service routing module; the security control module authenticates the query request by using a third authentication instruction, and if authentication is performed, a first request parameter set is sent to an acquired case number interface of a service unit through the standardized interface management module, wherein the first request parameter set comprises an accurate case number, a manager, a case type, a case date, a modification time, a contractor and a case person; the standardized interface management module obtains a query result according to the first request parameter set and sends the query result to the target service through the national service routing module;
the case information query interface is used for querying basic information of the case by the target service;
responding to the basic information of the target service query case, and transmitting a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module by the target service through the national service routing module; the security control module authenticates the data query request head by using a third authentication instruction, and if authentication is passed, the standardized interface management module initiates a case information query interface calling request and sends a second request parameter set to the case information query interface, wherein the second request parameter set comprises a case identifier, an accurate case number, a manager, a case type, the number of result sets, an offset, a case date, a modification time, a contractor and a case person; and the standardized interface management module acquires a query result according to the second request parameter set and feeds the query result back to the target service through the national service routing module.
As one embodiment of the present specification, the file unifying interface includes a file total information acquiring interface and a single material downloading interface in the file;
the volume total information interface is used for acquiring the total catalog and the material information of the volume;
the method comprises the steps that a target service is responded to obtain a full-volume catalog and material information of a file, and the target service transmits a data query request head containing Token information, user information identification, request id and signature information to a standardized interface management module through a national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, initiates a request for calling a volume full information acquisition interface to the standardized interface management module and sends a third request parameter set to the volume full information acquisition interface, wherein the third request parameter set comprises a case number, a case identification and a distributed deployment condition; the standardized interface management module obtains a query result according to the third request parameter set and sends the query result to the target service through the national service routing module;
the single material downloading interface in the file is used for downloading the single material in the file;
When the target service requests downloading, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, the standardized interface management module transmits a fourth request parameter set to a single material download interface in the file, wherein the fourth request parameter set comprises a document number, a case identification, an id value corresponding to a root node and a code value of a sponsor organization; and the standardized interface management module acquires a downloading result according to the fourth request parameter set and sends the downloading result to the target service unit in a binary file stream form through the national service routing module.
As one embodiment of the present specification, the document unified interface includes a document information acquiring interface and a document entity acquiring interface;
the document information acquisition interface is used for acquiring document information related to the case;
when a target service obtains document information related to a case, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if authentication is passed, the standardized interface management module requests the acquired case document information interface and transmits a fifth request parameter set to the acquired case document information interface, wherein the fifth request parameter set comprises a case number, a case identifier, a document type, a secondary document type and a code value of a manager; the standardized interface management module obtains a result according to the fifth request parameter set and sends a query result to the target service through the national service routing module;
The method comprises the steps that a single document entity interface is obtained and used for downloading a single document in a document;
when the target service downloads a single document in the document, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, the standardized interface management module transmits a sixth request parameter set to the acquired single document entity interface, wherein the sixth request parameter set comprises a case number, a case identification, a document number, a document type and a code value of a sponsor organization; and the standardized interface management module acquires a downloading result according to the request parameters and sends the downloading result to the target service in a binary file stream form through the national service routing module.
As one embodiment of the present specification, the national service routing module includes a proxy gateway and a service status monitoring control;
the proxy gateway is used for inquiring a service address matched with the service request parameter according to the service request and sending a request service parameter to the service address, wherein the request service parameter is determined according to the unified integrated access service request; the system is also used for inquiring the address of the data unified interface matched with the service request parameters according to the service request, and sending the service request parameters and the address to the standardized interface management module, wherein the request parameters of the inquired data are determined according to the service request;
The service state monitoring control is used for monitoring the running state of the service and giving an alarm when the service is in downtime or overload running.
The proxy gateway herein implements a gateway proxy for a service, i.e. a URL of a service accessed through the gateway, i.e. a gateway IP + specified service proxy path. For example: http [ s ]/{ IP }/{ vendor }/{ service } represents the access URL of the A service, wherein { IP } represents the IP address of the gateway; { vendor } represents an A service provider name (e.g., 123); { service } represents an A service name (e.g., 123). When the business unit accesses the a service, the set gateway URL will be mapped to the real address of the proxied a service, for example: 192.168.3.4.
as one embodiment of the present specification, the proxy gateway includes a data unified interface proxy gateway and a knowledge service proxy gateway;
the data unified interface proxy gateway counts the data convergence condition of each province according to a preset list, and for the provinces with which data convergence is completed (namely, all the provinces of service data are converged to the province advanced institution), the national service routing module directly initiates routing to the unified integrated access module of the province advanced institution: after the national service routing module receives a request of service for service data in a service unit, the request parameter and a routing address matched with the request parameter are sent to the standardized interface management module; the standardized interface management module extracts key information in the request parameters and then routes the key information to a unified data interface of the provincial high-level institution to acquire corresponding service data;
For provinces of incomplete data aggregation, the national service routing module carries out multi-level routing on each level mechanism (a high-level mechanism, a medium-level mechanism and a basic mechanism) of the province, and after receiving a request of service on the service data, the national service routing module sends a request parameter and a routing address matched with the request parameter to the standardized interface management module; the standardized interface management module extracts key information in the request parameters, further matches the routing address of the corresponding mechanism data interface according to the request parameters, and further maps the routing address to the real address of the corresponding hierarchical mechanism data interface through the service proxy gateway and invokes service data.
The key information in this specification may include case numbers, sponsors, etc.
When a service unit is accessed to knowledge service of the service registration management unit in a unified way, token information is uniformly distributed to the service unit through the service registration management unit so as to define service calling authority of the service unit;
when a service unit accesses a service, the service unit maps to the real address of the proxied service through the gateway URL set by the knowledge service proxy gateway so that the service unit uses the service.
Specifically, each service manufacturer sets a corresponding knowledge service access interface according to the proxy gateway URL specified by the national service routing module, accesses the URL of the service, namely the gateway IP+the specified service proxy path through the national service routing module, and when the service unit accesses the service, the URL of the gateway through the setting will be mapped to the real address of the proxied service.
It should be noted that after the knowledge services and service units of multiple providers exist, if the service providers need to be replaced, the service provided by different providers can be seamlessly switched by only carrying out relevant configuration change on the service through the national service routing module, and secondary docking with an organization service unit is not needed, if the organization service unit initially docks with the OCR service provided by the A provider, the routing address is the proxy path of gateway IP+A provider OCR service, if the organization service unit needs to be replaced with the OCR service of the B provider, the OCR service proxy path of the A provider in the routing address is replaced with the OCR service proxy path of the B provider in the configuration management center, so that the routing address is changed into the proxy path of gateway IP+B provider OCR service, and secondary docking is not needed.
As an embodiment of the present specification, further comprising: the service unified integrated access interface is used for sending the service request sent by the service unit to the service proxy unit; the service agent unit is used for forwarding the service processing result to the service unit;
when the service unit initiates a service request to a service proxy unit, a request header containing Token information and user information identification and request parameters containing information such as a case number, a case identification, a service ID, an interface ID, a signature, a manager and the like are transmitted to the unified integrated access module through the service unified integrated access interface; and after the service is processed to obtain a calculation result, returning a service result to the service unit through the service unified integrated access interface.
As an embodiment of the present specification, the encryption algorithm includes SM2 and SM4, and the SM2 signature algorithm is mainly divided into three steps to implement signature of the message based on solving the discrete logarithm problem: (1) key pair generation; (2) business unit hash generation; (3) digital signature generation.
SM4 is a block cipher algorithm with a packet length of 128 bits (i.e., 16 bytes, 4 words) and a key length of 128 bits (i.e., 16 bytes, 4 words). The encryption and decryption process adopts a 32-round iteration mechanism, each round of encryption key is needed, the encryption process is divided into two steps, and the encryption process consists of 32 rounds of iteration and 1 inverse sequence transformation; the decryption process of SM4 is identical to the encryption process and also includes 32 iterations and one reverse order transformation. Only at the time of round iteration, the round keys need to be used in reverse order. When a person skilled in the art encrypts a service request using an encryption algorithm, any one of them may be selected, which is not limited in this specification.
As an embodiment of the specification, the achievement collection analysis module is mainly used for carrying out buried point recording and storage aiming at the service unit calling action in the unified integrated access module, constructing a multi-angle achievement analysis and evaluation method based on the means of system buried point, log analysis and the like, realizing multidimensional evaluation of knowledge service efficiency and providing data support for service improvement and iteration. The specification designs a knowledge service efficiency evaluation system which covers four major categories of business evaluation, operation evaluation, iteration evaluation and popularization evaluation and has 20 dimensions in total, so as to be used for carrying out statistical analysis on the success of the knowledge service, and the connotation of specific evaluation indexes is shown in the following table 1.
TABLE 1 knowledge service application success analysis evaluation index System Table
As shown in fig. 4, for a computer device provided in an embodiment of the present description, the computer device 402 may include one or more processors 404, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 402 may also include any memory 406 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 406 may include any one or more of the following combinations: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may store information using any technique. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 402. In one case, when the processor 404 executes associated instructions stored in any memory or combination of memories, the computer device 402 can perform any of the operations of the associated instructions. The computer device 402 also includes one or more drive mechanisms 408 for interacting with any memory, such as a hard disk drive mechanism, optical disk drive mechanism, and the like.
The computer device 402 may also include an input/output module 410 (I/O) for receiving various inputs (via an input device 412) and for providing various outputs (via an output device 414). One particular output mechanism may include a presentation device 416 and an associated Graphical User Interface (GUI) 418. In other embodiments, input/output module 410 (I/O), input device 412, and output device 414 may not be included, but merely as a computer device in a network. Computer device 402 may also include one or more network interfaces 420 for exchanging data with other devices via one or more communication links 422. One or more communication buses 424 couple the above-described components together.
The communication link 422 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the internet), a point-to-point connection, etc., or any combination thereof. Communication link 422 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
Corresponding to the method in fig. 3, the present embodiment also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above method.
The present description also provides computer-readable instructions, wherein the program therein causes the processor to perform the method as shown in fig. 3 when the processor executes the instructions.
It should be understood that, in various embodiments of the present disclosure, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation of the embodiments of the present disclosure.
It should also be understood that, in the embodiments of the present specification, the term "and/or" is merely one association relationship describing the association object, meaning that three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In the present specification, the character "/" generally indicates that the front and rear related objects are an or relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the various example components and steps have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present specification.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purposes of the embodiments of the present description.
In addition, each functional unit in each embodiment of the present specification may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present specification is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present specification. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The principles and embodiments of the present specification are explained in this specification using specific examples, the above examples being provided only to assist in understanding the method of the present specification and its core ideas; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope based on the ideas of the present specification, the present description should not be construed as limiting the present specification in view of the above.

Claims (10)

1. A cross-business, multi-judicial service integrated scheduling system, comprising:
the service registration management unit is used for issuing a first interface specification, acquiring a service packaged according to the first interface specification, and distributing Token information to a business unit applying the service;
the service agent unit is used for receiving the service request of each service unit, and starting a unified integrated page of the corresponding service according to the service request and first authentication information, wherein the first authentication information is generated according to the user ID of the service unit and Token information of the service unit; the service unit is used for calling the service data stored by the service unit and enabling the service to process the service data; the service processing unit is used for processing the service and obtaining a processing result;
The service agent unit includes:
the unified integrated access module is used for receiving a service request according to a service unified integrated access interface of the service unit, authenticating the service request according to a first authentication instruction of the security control module, encrypting a request parameter after authentication is completed, and sending the encrypted request parameter to the national service routing module;
the national service routing module is used for receiving a service request and opening a routing address of the requested service according to a second authentication instruction of the security control module; the system is also used for receiving the data request for requesting service, forwarding the data request parameters to a standardized interface management module to acquire service data, and forwarding the service processing result of the service to the unified integrated access module;
the standardized interface management module is configured to dock a data unified interface of the service unit according to the second interface specification, obtain service data in the service unit through the data unified interface according to the service request and third authentication information, and send the service data to the national service routing module, where the data unified interface includes a case unified interface, a file unified interface and a document unified interface;
The security control module is used for encrypting a service request sent by a service unit by adopting an encryption algorithm and also used for verifying whether the service unit has permission to open the unified integrated page by using the first authentication instruction; the service unit is further used for verifying whether the service unit has permission to open a service page or not by using the second authentication instruction; the method is also used for verifying whether the service request has authority to call the data unified interface or not by using a third authentication instruction;
and the service units are used for sending service data through a data unified interface, sending service request parameters to the service proxy unit through a unified integrated interface and receiving the processing results forwarded by the service proxy unit, wherein the data unified interface and the unified integrated interface accord with a second interface specification.
2. The cross-business, multi-judicial service integrated scheduling system of claim 1, wherein,
the services of the service registration management unit comprise page services and API services;
when the business unit calls the page service, the unified integrated page is opened through the unified integrated access module, and the quick switching of each service is performed through the unified integrated page; after the unified integrated access module receives the response result of the page service, the response result is fed back to a target service page of the unified integrated page;
And when the service unit calls the API service, the unified integrated access module directly feeds back the received service response result to the service unit.
3. The cross-business, multi-judicial service integrated scheduling system of claim 1, further comprising:
the service unified integrated access interface is used for sending the service request sent by the service unit to the service proxy unit; the service agent unit is used for forwarding the service processing result to the service unit;
when the service unit initiates a service request to a service proxy unit, transmitting a request header containing Token information and user information identification and request parameters containing case numbers, case identifications, service IDs, interface IDs, signatures and administrative court information to the unified integrated access module through the service unified integrated access interface; and after the service is processed to obtain a calculation result, returning a service result to the service unit through the service unified integrated access interface.
4. The cross-business multi-judicial service integrated scheduling system of claim 1, wherein the national service routing module includes a proxy gateway and a service status monitoring control;
The proxy gateway is used for inquiring a service address matched with the service request parameter according to the service request and sending a request service parameter to the service address, wherein the request service parameter is obtained according to the unified integrated access service request; the system is also used for inquiring the address of the data unified interface matched with the service request parameters according to the service request, and sending the service request parameters and the address to the standardized interface management module, wherein the request parameters of the inquired data are determined according to the service request;
the service state monitoring control is used for monitoring the running state of the service and giving an alarm when the service is in downtime or overload running.
5. The cross-business, multi-judicial service integrated scheduling system of claim 4, wherein the service broker gateway comprises a knowledge service broker gateway;
when a service unit is accessed to knowledge service of the service registration management unit in a unified way, token information is uniformly distributed to the service unit through the service registration management unit so as to define service calling authority of the service unit;
when a service unit accesses a service, the service unit maps to the real address of the proxied service through the gateway URL set by the knowledge service proxy gateway so that the service unit uses the service.
6. The cross-business, multi-judicial service, integrated, scheduling system of claim 4, wherein the proxy gateway comprises a data unification interface proxy gateway;
the data unified interface proxy gateway counts the data convergence condition of each province according to a preset list, and for the provinces with data convergence, the national service routing module directly initiates routing to the data unified interface of the province high-rise: after the national service routing module receives a request of service for service data in a service unit, the request parameter and a routing address matched with the request parameter are sent to the standardized interface management module; the standardized interface management module extracts key information in the request parameters and then routes the key information to a unified data interface of the provincial high-rise to obtain corresponding service data;
for provinces of incomplete data aggregation, the national service routing module carries out multi-level routing on courts of each level of the province, and after receiving a request of service on the service data, the national service routing module sends request parameters and routing addresses matched with the request parameters to the standardized interface management module; the standardized interface management module extracts key information in the request parameters, further matches the routing address of the corresponding court data interface according to the request parameters, and further maps the routing address to the real address of the corresponding hierarchical court data interface through the service proxy gateway and invokes service data.
7. The cross-business multi-judicial service comprehensive integrated scheduling system of claim 1, wherein the case unifying interface comprises a case number acquisition interface and a case information query interface;
the obtained case number interface is used for inquiring the case number meeting the conditions by the target service;
responding to the target service to inquire the number of cases, and transmitting a data inquiry request head containing Token information, user information identification, request id and signature information to the standardized interface management module by the target service through the national service routing module; the security control module authenticates the query request by using a third authentication instruction, and if authentication is performed, a first request parameter set is sent to an acquired case number interface of a service unit through the standardized interface management module, wherein the first request parameter set comprises an accurate case number, a administrative court, a case type, a case date, a modification time, a contractor and a case person; the standardized interface management module obtains a query result according to the first request parameter set and sends the query result to the target service through the national service routing module;
the case information query interface is used for querying basic information of the case by the target service;
Responding to the basic information of the target service query case, and transmitting a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module by the target service through the national service routing module; the security control module authenticates the data query request head by using a third authentication instruction, and if authentication is passed, the standardized interface management module initiates a case information query interface calling request and sends a second request parameter set to the case information query interface, wherein the second request parameter set comprises a case identifier, an accurate case number, a agency, a case type, a result set number, an offset, a case date, a modification time, a contractor and a case person; and the standardized interface management module acquires a query result according to the second request parameter set and feeds the query result back to the target service through the national service routing module.
8. The cross-business, multi-judicial service integrated scheduling system of claim 1, wherein,
the file unifying interface comprises a file total information acquisition interface and a single material downloading interface in the file;
The volume total information interface is used for acquiring the total catalog and the material information of the volume;
the method comprises the steps that a target service is responded to obtain a full-volume catalog and material information of a file, and the target service transmits a data query request head containing Token information, user information identification, request id and signature information to a standardized interface management module through a national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, initiates a request for calling a volume full information acquisition interface to the standardized interface management module and sends a third request parameter set to the volume full information acquisition interface, wherein the third request parameter set comprises a case number, a case identification and a distributed deployment condition; the standardized interface management module obtains a query result according to the third request parameter set and sends the query result to the target service through the national service routing module;
the single material downloading interface in the file is used for downloading the single material in the file;
when the target service requests downloading, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, the standardized interface management module transmits a fourth request parameter set to a single material download interface in the file, wherein the fourth request parameter set comprises a document number, a case identification, an id value corresponding to a root node and a code value of a agency; and the standardized interface management module acquires a downloading result according to the fourth request parameter set and sends the downloading result to the service unit in a binary file stream form through the national service routing module.
9. The cross-business, multi-judicial service integrated scheduling system of claim 1, wherein,
the document unified interface comprises a document information acquisition interface and a single document entity acquisition interface;
the document information acquisition interface is used for acquiring document information related to the case;
when a target service obtains document information related to a case, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if authentication is passed, the standardized interface management module requests the acquired case document information interface and transmits a fifth request parameter set to the acquired case document information interface, wherein the fifth request parameter set comprises a case number, a case identifier, a document type, a secondary document type and code values of a agency; the standardized interface management module obtains a result according to the fifth request parameter set and sends a query result to the target service through the national service routing module;
The method comprises the steps that a single document entity interface is obtained and used for downloading a single document in a document;
when the target service downloads a single document in the document, the target service transmits a data query request head containing Token information, user information identification, request id and signature information to the standardized interface management module through the national service routing module; the security control module authenticates the data query request header by using a third authentication instruction, and if the authentication is passed, the standardized interface management module transmits a sixth request parameter set to the acquired single document entity interface, wherein the sixth request parameter set comprises a case number, a case identification, a document number, a document type and a code value of a agency; and the standardized interface management module acquires a downloading result according to the request parameters and sends the downloading result to the target service in a binary file stream form through the national service routing module.
10. The cross-business multi-judicial service comprehensive integrated scheduling system of claim 1, further comprising a success collection analysis module;
the achievement collection analysis module is used for carrying out buried point recording on the behavior of calling service by the business unit at the unified integrated access module; the achievement collection analysis module is also used for evaluating the dispatching system according to the service calling behavior of the business unit.
CN202311328275.3A 2023-10-13 2023-10-13 Cross-service multi-judicial service comprehensive integrated scheduling system Active CN117082146B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311328275.3A CN117082146B (en) 2023-10-13 2023-10-13 Cross-service multi-judicial service comprehensive integrated scheduling system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311328275.3A CN117082146B (en) 2023-10-13 2023-10-13 Cross-service multi-judicial service comprehensive integrated scheduling system

Publications (2)

Publication Number Publication Date
CN117082146A CN117082146A (en) 2023-11-17
CN117082146B true CN117082146B (en) 2024-01-23

Family

ID=88704630

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311328275.3A Active CN117082146B (en) 2023-10-13 2023-10-13 Cross-service multi-judicial service comprehensive integrated scheduling system

Country Status (1)

Country Link
CN (1) CN117082146B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110049048A (en) * 2019-04-22 2019-07-23 易联众民生(厦门)科技有限公司 A kind of data access method, equipment and the readable medium of government affairs public service
CN110784527A (en) * 2019-10-18 2020-02-11 三体云智能科技有限公司 Information management system and method
CN112532413A (en) * 2019-09-18 2021-03-19 亦非云互联网技术（上海）有限公司 Business support Saas system, method, medium and device based on micro-service architecture
CN116489214A (en) * 2023-04-25 2023-07-25 国电南瑞科技股份有限公司 Unified service scheduling method, device, medium and equipment based on micro service gateway

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110049048A (en) * 2019-04-22 2019-07-23 易联众民生(厦门)科技有限公司 A kind of data access method, equipment and the readable medium of government affairs public service
CN112532413A (en) * 2019-09-18 2021-03-19 亦非云互联网技术（上海）有限公司 Business support Saas system, method, medium and device based on micro-service architecture
CN110784527A (en) * 2019-10-18 2020-02-11 三体云智能科技有限公司 Information management system and method
CN116489214A (en) * 2023-04-25 2023-07-25 国电南瑞科技股份有限公司 Unified service scheduling method, device, medium and equipment based on micro service gateway

Also Published As

Publication number Publication date
CN117082146A (en) 2023-11-17

Similar Documents

Publication Publication Date Title
US11212335B2 (en) Network management interface
CN106790420B (en) A kind of more session channel method for building up and system
US8321952B2 (en) Method and system for monitoring online computer network behavior and creating online behavior profiles
US7792939B2 (en) Method and system for obtaining secure shell host key of managed device
CN105556894B (en) For being connected to the network the method and system of automation
KR101038124B1 (en) Data transfer controlling method, content transfer controlling method, content processing information acquisition method and content transfer system
US6983379B1 (en) Method and system for monitoring online behavior at a remote site and creating online behavior profiles
EP1379045B1 (en) Arrangement and method for protecting end user data
US7290286B2 (en) Content provider secure and tracable portal
US20060167897A1 (en) Administration of a broker-based publish/subscribe messaging system
WO2008127608A2 (en) A system and method for creating a list of shared information on a peer-to-peer network
WO2007064169A1 (en) Method and apparatus for transmitting message in heterogeneous federated environment, and method and apparatus for providing service using the message
CN110059055B (en) File storage and reading method and device based on distributed private cloud
KR100661006B1 (en) Home network device management system and method thereof
CN108429739A (en) A kind of method, system and the terminal device of identification honey jar
CN117082146B (en) Cross-service multi-judicial service comprehensive integrated scheduling system
US20030204586A1 (en) Intelligent data replicator
CN114006724B (en) Method and system for discovering and authenticating encryption DNS resolver
CN106060155B (en) The method and device of P2P resource-sharing
CN117319083B (en) Cross-chain sharing method, device, system and equipment for heterogeneous privacy data
CN117395138A (en) Device point table configuration method, device, computer device and readable storage medium
CN107209751A (en) Method for processing business and device
CN107547478A (en) Message transmitting method, apparatus and system
CN116305215A (en) Double-chain block chain data encryption and deletion method, device, system and equipment
CN116340978A (en) Double-chain block chain data encryption updating method, device, system and equipment

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