A signing obligation integration weaving method and system based on a signed security ontology and a storage medium
Patent Information
- Application Number
- CN202610940386.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-26
- Publication Date
- 2026-10-09
AI Technical Summary
针对现有签署义务与签署过程分离、需人工配置的问题,本发明提供一种基于签署安全本体的签署义务一体化编织方法、系统及存储介质
其一,以签署安全本体推理派生签署义务、一体化编织,弥补义务与过程分离;其二,签署接口随义务自动生成;其三,是数据相关行为证明方法在签署场景的方法论核心,安全义务内生方法。
Smart Images

Figure CN122885941A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the fields of data security and electronic signatures, and in particular to a method, system and storage medium for integrating signing obligations with a signature security ontology, which is the core of the electronic signature 2.0 methodology. Background Technology
[0002] Electronic signatures should derive signing obligations from the document to be signed and the signatory's obligations, making these obligations inherent in the signing process. Traditional electronic signatures only complete the signing action; the signing obligations are separated from the signing process and require manual configuration.
[0003] The root cause is the lack of a secure signature ontology (covering both the signing object and the signing entity) from which signing obligations can be derived and signing interfaces can be automatically generated. Therefore, how to integrate signing obligations with a secure signature ontology and make the obligations intrinsic to the signing process is the core issue of eSignature 2.0. Summary of the Invention
[0004] (a) Technical problems to be solved To address the problems of existing signing obligations being separated from the signing process and requiring manual configuration, this invention provides a method, system, and storage medium for integrating signing obligations based on a signing security ontology.
[0005] (II) Technical Solution This invention establishes a secure signing ontology (signing object ontology + signing subject ontology); a signing obligation inference engine derives signing obligations from these two ontologies; and a signing interface is automatically generated based on the signing obligations, thus integrating and embedding signing obligations into the signing process. This invention is the core methodology of data-related behavior proof methods in signing scenarios, with signing obligations being intrinsically derived from the secure obligation intrinsic method.
[0006] (III) Beneficial Effects First, it uses the security ontology to derive signing obligations and integrates them to compensate for the separation of obligations and processes. Second, the signing interface is automatically generated along with the obligation. Third, it is the core methodology of data-related behavior proof methods in the signing scenario, an endogenous method of security obligations. Attached Figure Description
[0007] Figure 1 A schematic diagram illustrating the integrated weaving of signing obligations based on the Security Signature Ontology (SSO).
[0008] Figure 2 A schematic diagram of two types of ontologies for signing a security ontology.
[0009] Figure 3 Flowchart for reasoning and interface generation for signing obligations.
[0010] Figure 4A schematic diagram illustrating the integration of obligations under the agreement.
[0011] Figure 5 This diagram illustrates the connection between data-related behavior proof methods and endogenous security obligation methods. Detailed Implementation
[0012] The present invention will be further described in detail below with reference to the accompanying drawings, taking the integrated signing obligation of one-to-one signing as an example.
[0013] 1. Overall Mechanism See Figure 1 The signing obligation is derived from the signing object and the signing subject through the reasoning engine, the signing interface is automatically generated, and the process is integrated.
[0014] 2. Sign the security entity. See Figure 2 The signing security ontology consists of the signing object ontology (document semantics) and the signing subject ontology (subject capabilities), which together serve as the input for obligation reasoning.
[0015] 3. Reasoning and Interface Generation See Figure 3 The signing obligation reasoning engine derives signing obligations based on the reasoning of two entities and automatically generates signing interfaces based on the obligations.
[0016] 4. Integrated weaving See Figure 4 The object ontology and the subject ontology are integrated; obligations are derived from the ontology; interfaces are automatically generated along with obligations; and obligations are inherent in the signing process.
[0017] 5. Integration with methods for proving data-related behaviors and methods for endogenous security obligations. See Figure 5 This invention is the core methodology of data-related behavior proof methods in signing scenarios, where the signing obligation is intrinsically derived from the subject matter (intrinsic security obligation method). The above embodiments are for illustrative purposes only and not for limitation; all equivalent substitutions and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. A method for integrating signing obligations based on a signing security ontology, characterized in that, include: A signing security ontology is established, which includes a signing object ontology and a signing subject ontology. A signing obligation reasoning engine is used to derive the signing obligations to be performed in this signing based on the signing object ontology and the signing subject ontology. A signing interface is automatically generated based on the signing obligations, so that the signing obligations are integrated into the signing process.
2. The method according to claim 1, characterized in that, The signing object ontology describes the semantics of the document to be signed, including the document type and terms.
3. The method according to claim 1, characterized in that, The signing entity ontology describes the semantics of the signing party, including the entity's capabilities and roles.
4. The method according to claim 1, characterized in that, The signing obligation inference engine derives the signing obligation based on the two ontologies.
5. The method according to claim 1, characterized in that, The signing interface is automatically generated based on the derived signing obligations.
6. The method according to claim 1, characterized in that, The signing obligation is integrated into the signing process and is associated with the signing object.
7. The method according to claim 1, characterized in that, The method described is the core methodology of the behavior proof method based on data ontology in the signing scenario.
8. The method according to claim 1, characterized in that, The signing obligation is derived from the endogenous method of security obligations.
9. The method according to claim 1, characterized in that, The signing obligation is re-derived as the subject of the signing or the signing entity changes.
10. The method according to claim 1, characterized in that, The reasoning and weaving process will be documented.
11. The method according to claim 10, characterized in that, The traces are recorded using SM3 hashing, and the signatures are recorded using SM2.
12. A signing obligation integrated weaving system based on a signing security ontology, characterized in that, include: The ontology module is used to maintain the ontology of the signing object and the ontology of the signing entity; The reasoning module is used to derive signed obligations based on the reasoning of the two entities; An interface module is used to automatically generate a signing interface based on the signing obligation; the system is used to execute the method of any one of claims 1 to 11.
13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 11.