Digital certificate generation method, order matching method, electronic device, and storage medium
By embedding structured, coded trade capability data into digital certificates, the problem of asynchronous supplier authentication and capability data is solved, improving the accuracy and efficiency of order matching and supporting cross-system interoperability.
Patent Information
- Application Number
- CN202611306968.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-26
- Publication Date
- 2026-11-10
AI Technical Summary
In existing technologies, the supplier's identity verification information and trade capability attribute data are asynchronous in lifecycle management, which increases the time overhead of order matching and makes it difficult to guarantee accuracy.
By identifying the supplier's multi-dimensional trade capability attribute data with a target object identifier, encoding it according to a structured coding pattern, and writing it into an extended field during the digital certificate generation process, and then having the authentication system sign it to generate a digital certificate, the same-source association between identity credentials and multi-dimensional trade capability data is achieved.
It enables the synchronization of supplier authentication and trade capability data, reduces order matching time overhead, ensures matching accuracy and efficiency, and supports cross-system interoperability.
Smart Images

Figure CN123070975A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of supply chain management technology, and in particular to a digital certificate generation method, an order matching method, an electronic device, and a storage medium. Background Technology
[0002] Against the backdrop of digital transformation in supply chain management, the trade procurement sector has created a demand for automated execution capabilities in supplier management systems. In electronic transactions, it is necessary not only to verify the authenticity of suppliers' identities but also to accurately and in real-time assess their trading capabilities in order to achieve rapid and automatic matching of procurement needs with supplier capabilities.
[0003] Currently, digital certificates issued by electronic certification service providers (CAs) based on the X.509 standard are typically used as supplier identity verification information. However, the centralized database of the trade management system independently stores the supplier's multi-dimensional capability attribute data. This results in asynchrony between the supplier's identity verification information and trade capability attribute data in the actual order matching process, which not only increases the time cost of order matching but also makes it difficult to guarantee the accuracy of order matching. Summary of the Invention
[0004] This invention provides a digital certificate generation method, an order matching method, an electronic device, and a storage medium to address the shortcomings of existing technologies where the supplier's identity verification information and trade capability attribute data are asynchronous in lifecycle management. This not only increases the time overhead of order matching but also makes it difficult to guarantee the accuracy of order matching. The invention achieves atomic association and synchronization of the supplier's identity verification information and trade capability attribute data, thereby reducing the time overhead of order matching and ensuring the accuracy of order matching.
[0005] This invention provides a digital certificate generation method for use in an authentication system, the method comprising: In response to a supplier's certificate application or certificate renewal request, the latest multi-dimensional trade capability attribute data of the supplier is obtained from the trade management system. Based on the multi-dimensional trade capability attribute data, a certificate to be signed for the supplier is generated; the certificate to be signed includes a basic information field and an extended field; the basic information field stores the certificate version number, certificate serial number, issuer information, validity period information, as well as the supplier's identity information and public key information; the extended field stores the multi-dimensional trade capability attribute data identified by a target object identifier and encoded in a structured coding pattern, and the target object identifier is used to identify the trade capability semantic type of the data carried by the extended field; The certificate to be signed is signed based on the private key information of the authentication system to obtain signature information; The supplier's digital certificate is generated based on the certificate to be signed and the signature information.
[0006] According to a digital certificate generation method provided by the present invention, the multi-dimensional trade capability attribute data includes multiple data such as available product categories, production capacity limit data, qualification certification data, historical fulfillment rate data, serviceable geographical area data, credit rating, latest review time data, and additional remarks information. The qualification certification data includes at least one qualification certification entry, and each qualification certification entry includes a qualification type identifier, an issuing authority, and a qualification expiration date.
[0007] According to a digital certificate generation method provided by the present invention, the validity period information includes the effective time and the expiration time; The steps for determining the failure time include: Among the qualification expiration times of each qualification certification entry in the qualification certification data, the earliest expiration time is determined, and the expiration time is determined to be earlier than or equal to the earliest expiration time.
[0008] According to a digital certificate generation method provided by the present invention, the multi-dimensional trade capability attribute data is written into the extended field through the following steps: The multi-dimensional trade capability attribute data is organized according to a nested hierarchical structure; the nested hierarchical structure includes a root sequence, sub-sequences, and basic types; According to the structured encoding pattern, the organized multi-dimensional trade capability attribute data is encoded into at least one target byte stream; When there are multiple extended fields, each target byte stream is written into the extended field corresponding to each target byte stream according to the target object identifier corresponding to each target byte stream.
[0009] According to a digital certificate generation method provided by the present invention, the step of encoding the organized multi-dimensional trade capability attribute data into at least one target byte stream according to the structured encoding pattern includes: The multi-dimensional trade capability attribute data after organization is encoded into an initial byte stream according to the encoding format of data serialization encoding; Based on the data characteristics of the trade capability attribute data of each dimension and the resource information occupied by the initial byte stream, the initial byte stream is optimized and encoded to obtain at least one target byte stream; The optimized encoding includes at least one of unique encoding, compressed encoding, and split encoding; the compressed encoding includes prefix arc sharing encoding and / or number mapping encoding.
[0010] According to a digital certificate generation method provided by the present invention, before writing each of the target byte streams into the extended field corresponding to each of the target byte streams according to the target object identifier corresponding to each of the target byte streams, the method further includes: Each field in the target byte stream is divided into public fields, restricted fields, or sensitive fields; Keep the public fields in each of the target byte streams in plaintext; The symmetric key of the authentication system is used to encrypt the restricted fields in each of the target byte streams; Sensitive fields in each of the target byte streams are encrypted using the public key information of the supplier's demand side.
[0011] According to a digital certificate generation method provided by the present invention, the certificate update request is triggered when a positive change event is pushed by the trade management system, and the positive change event is used to indicate that the content of the supplier's multi-dimensional trade capability attribute data has changed; The process of obtaining the latest multi-dimensional trade capability attribute data of the supplier from the trade management system includes: In response to the certificate update request, verify the authenticity of the positive change event with the trade management system; If the positive change event passes the authenticity verification, the latest multi-dimensional trade capability attribute data of the supplier is obtained from the trade management system; all qualification certification entries in the latest multi-dimensional trade capability attribute data are in an unexpired state.
[0012] According to a digital certificate generation method provided by the present invention, the method further includes: Upon receiving a negative change event pushed by the trade management system, the system verifies the authenticity of the negative change event; the negative change event is used to indicate that some of the supplier's qualification certification items have expired or its credit rating has been reduced. If the negative change event passes the authenticity verification, the supplier's current digital certificate is added to the revocation list, and the extended fields of the supplier's current digital certificate are updated according to the event type of the negative change event. Based on the updated extended fields, a new digital certificate for the supplier is generated. The system publishes the current revocation status of the vendor's digital certificate and pushes the new digital certificate to subscribers who have subscribed to the vendor's certificate change notifications.
[0013] According to a digital certificate generation method provided by the present invention, the extended field further includes tag information and version information; the tag information is used to identify that the content information of the extended field is non-critical extended information; the version information is used to identify the data structure version of the extended field.
[0014] The present invention also provides an order matching method applied to a procurement system, the method comprising: Obtain the demand information for pending orders and a list of candidate supplier digital certificates; the list of candidate supplier digital certificates includes digital certificates from multiple candidate suppliers. The identity validity of the digital certificates of each candidate supplier is verified, and based on the verification results of the digital certificates of each candidate supplier, the digital certificates of each supplier to be matched that have passed the identity validity verification are obtained from the list of candidate supplier digital certificates. Based on the target object identifier in the extended field of the digital certificate of each of the suppliers to be matched, the multi-dimensional trade capability attribute data of each supplier to be matched is parsed. The demand information is matched with the multi-dimensional trade capability attribute data of each of the suppliers to be matched, and the matching results are output. The digital certificate of each of the candidate vendors is generated based on the digital certificate generation method described in any of the above.
[0015] According to an order matching method provided by the present invention, the verification of the identity validity of the digital certificates of each candidate supplier includes: For each candidate vendor's digital certificate, the signature information of the digital certificate is verified using the public key information of the authentication system to obtain a first verification result; Based on the validity period information in the basic information field of the digital certificate, verify whether the digital certificate has expired to obtain a second verification result; Based on the certificate serial number in the basic information field of the digital certificate, verify whether the digital certificate has been revoked to obtain a third verification result; If the first verification result indicates that the digital certificate has passed the signature verification, the second verification result indicates that the digital certificate has not expired, and the third verification result indicates that the digital certificate has not been revoked, then the digital certificate is determined to have passed the identity validity verification. The digital certificates of each candidate vendor are iterated through to obtain the verification results of each candidate vendor's digital certificate.
[0016] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement any of the digital certificate generation methods or order matching methods described above.
[0017] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the digital certificate generation method or order matching method as described above.
[0018] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements any of the digital certificate generation methods or order matching methods described above.
[0019] The digital certificate generation method, order matching method, electronic device, and storage medium provided by this invention obtain the latest multi-dimensional trade capability attribute data from the trade management system when responding to certificate application or certificate update requests. This data is identified by a target object identifier, encoded using a structured coding pattern, and written into the extended field of the digital certificate. This binds the supplier's identity credentials and multi-dimensional trade capability attribute data to the same digital certificate carrier, and achieves integrity protection through a single signature operation of the authentication system. This eliminates the temporal asynchrony and information inconsistency caused by the separate storage of identity credentials and capability attribute data. It allows the relying party to directly obtain reliable trade capability attribute data while verifying the digital certificate without performing a secondary database query. Furthermore, the identification of trade capability semantic types by the target object identifier and the adoption of a structured coding pattern ensure that the data carried in the extended field has a unified, machine-resolvable semantic specification, providing a foundation for interoperability of trade capability attribute data between different systems, thereby effectively improving the accuracy and efficiency of order matching. Attached Figure Description
[0020] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0021] Figure 1 This is a flowchart illustrating the digital certificate generation method provided by the present invention.
[0022] Figure 2 This is a flowchart illustrating the order matching method provided by the present invention.
[0023] Figure 3This is a schematic diagram of the supply chain management cluster provided by the present invention.
[0024] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation
[0025] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.
[0026] All actions involving the acquisition of signal information or data in this application are carried out in compliance with the relevant local data protection regulations and policies, and with the permission of the relevant device owner.
[0027] Currently, in the fields of electronic authentication and supply chain management, Public Key Infrastructure (PKI) based on the X.509 standard is widely used for supplier authentication. Within this framework, digital certificates, serving as supplier identity credentials, primarily carry their public key and identity information, but cannot convey their trading capabilities. The certainty and stability of supplier identity credentials directly impact the effectiveness of procurement decisions. Meanwhile, the supplier's multi-dimensional capability attribute data is typically stored independently in the centralized database of the trade management system. The accuracy and timeliness of this multi-dimensional capability attribute data directly affect the quality of procurement decisions and the operational efficiency of the supply chain. In actual business processes, the procurement system first uses digital certificates to complete identity verification, and then accesses a remote database interface to retrieve the capability attribute data associated with that identity for logical order matching.
[0028] However, because the identity credentials represented by digital certificates and the multi-dimensional capability attribute data in the trade management system are logically and physically separate, stored in different databases without a real-time synchronization mechanism, data association is typically achieved through scheduled batch imports or manual maintenance. Scheduled batch imports are performed every other day or weekly, resulting in asynchronous time-series management of identity credential lifecycle management and multi-dimensional capability attribute data change management. This leads to situations where digital certificates are updated but multi-dimensional capability attribute data is not synchronized, or supplier qualifications have expired but the digital certificate is still trusted by the procurement system within its validity period. Furthermore, in scenarios with a large number of suppliers, manual maintenance causes the error and omission rates to increase with scale.
[0029] Meanwhile, under the aforementioned separate architecture, order matching in the procurement system relies on two independent operational phases: the first phase verifies the validity of digital certificates through public key infrastructure, and the second phase queries the trade management system's database to compare multi-dimensional capability attribute data to see if they meet matching conditions. These two phases lack an atomic linkage mechanism; that is, between the successful verification in the first phase and the query in the second phase, the supplier's multi-dimensional capability attribute data may have changed, leading to inconsistencies between the matching results and the supplier's real-time status. Furthermore, in scenarios with a large number of suppliers and matching conditions containing multi-dimensional constraints, the time overhead of the two phases is cumulative, and the query pressure on the centralized database increases with the number of suppliers and the number of constraint dimensions. If a network outage or database failure occurs, order matching cannot be executed.
[0030] Furthermore, although RFC 5280 in the X.509 standard defines the basic framework for digital certificate extension fields, specifying only the object identifier (OID) of the basic extension and its purpose, it does not define dedicated data structures and semantic specifications for trade matching scenarios. In this situation, existing extension fields often record information in the form of free text or simple key-value pairs, lacking a unified, machine-parseable hierarchical semantic model. This makes it difficult for different procurement systems to unify the parsing logic of the content carried by the extension fields, thus hindering interoperability in cross-system collaboration scenarios.
[0031] Furthermore, when the number of suppliers grows to thousands and the matching conditions include multi-dimensional constraints, the query pressure on the centralized database increases exponentially, and network outages or database failures can render the matching service unavailable.
[0032] In summary, existing technologies suffer from several problems: the identity credentials carried by digital certificates and the multi-dimensional capability attribute data are stored separately, leading to asynchronous timing and inconsistencies; order matching relies on two independent operation stages and lacks atomic association, thus affecting matching accuracy and efficiency; and the extended fields of digital certificates lack a structured semantic model for trade matching scenarios, making cross-system interoperability impossible.
[0033] To address this issue, this application provides a digital certificate generation method. This method, in response to a supplier's certificate application or update request, retrieves the supplier's latest multi-dimensional trade capability attribute data from a trade management system. Following a structured coding pattern, this multi-dimensional trade capability attribute data is identified by a target object identifier and written into an extended field of the digital certificate. Then, it combines the supplier's identity information and public key information to generate a certificate to be signed. Finally, the authentication system signs the digital certificate using its private key. This binds the supplier's identity credentials and multi-dimensional trade capability attribute data to the same digital certificate carrier, enabling them to achieve a common-source association in a single issuance operation of the authentication system, thereby resolving the issue of identity credentials and multi-dimensional capability attribute data... This addresses the timing asynchrony and information inconsistency issues arising from separate storage. Furthermore, it enables the procurement system to directly parse multi-dimensional trade capability attribute data from extended fields to complete order matching after verifying the validity of digital certificates, eliminating the need for secondary queries to remote databases. This resolves the lack of atomicity between the two operation stages and the resulting issues with matching accuracy and efficiency. Simultaneously, by assigning target object identifiers to the multi-dimensional trade capability attribute data carried by the extended fields to identify the semantic type of trade capability and organizing them using a structured coding pattern, different procurement systems can parse the extended fields based on a unified semantic model. This solves the problem of cross-system interoperability caused by the lack of a structured semantic model for the extended fields.
[0034] Figure 1 This is a flowchart illustrating the digital certificate generation method provided by the present invention. Figure 1 As shown, this embodiment of the invention provides a digital certificate generation method. This method is applied to an authentication system, meaning the entity executing this method is the authentication system. Here, the authentication system refers to a Certificate Authority (CA) qualified to issue digital certificates. It holds the private key information used to issue digital certificates and publicly discloses the public key information corresponding to this private key information so that various dependent parties can verify the digital certificates it issues. The method specifically includes steps 110, 120, 130, and 140.
[0035] Step 110: In response to the supplier's certificate application request or certificate renewal request, obtain the latest multi-dimensional trade capability attribute data of the supplier from the trade management system.
[0036] It should be noted that, for the sake of simplicity, the trade capability attribute data may also be referred to as capability attribute data or capability data in the following text.
[0037] The certificate application request here refers to the request initiated by a supplier to the certification system in order to obtain a digital certificate when it does not yet hold one. For example, when a supplier first joins a trade platform, it submits a certificate issuance application to the certification system through the front-end page, client program, or application programming interface provided by the certification system.
[0038] The certificate renewal request here refers to a request initiated to the authentication system to reissue a digital certificate when the system already holds the supplier's digital certificate. Examples include a renewal application initiated when the supplier's digital certificate is nearing its expiration date, or a certificate reconstruction application initiated when the supplier's trading capabilities change. It is understood that both certificate application requests and certificate renewal requests carry a supplier identifier to uniquely identify the supplier, allowing the authentication system to locate the data acquisition target based on this identifier.
[0039] The trade management system here refers to the business system that stores and maintains the trade profile data of each supplier. As the sole data source for multi-dimensional trade capability attribute data, it is responsible for collecting, reviewing, and updating the multi-dimensional capability attribute data of suppliers.
[0040] Optionally, after receiving a certificate application request or certificate renewal request, the certification system can extract the supplier identifier from the request and, based on the supplier identifier, obtain the supplier's latest multi-dimensional trade capability attribute data from the trade management system through a pre-established data interaction channel.
[0041] The data interaction channel here can be any pre-agreed data transmission channel between the authentication system and the trade management system. For example, this data interaction channel could be a Representational State Transfer (REST) style application programming interface (API) exposed by the trade management system, through which the authentication system obtains attribute data returned in JavaScript Object Notation (JSON) format. Alternatively, it could be a message queue channel deployed between the authentication system and the trade management system; or it could be a shared database middleware between the authentication system and the trade management system. This embodiment does not limit the specific form of the data interaction channel.
[0042] The latest multi-dimensional trade capability attribute data mentioned here refers to the attribute data of the supplier across multiple capability dimensions recorded in the trade management system and verified at the current time node when the authentication system initiates the acquisition operation. This multi-dimensional trade capability attribute data refers to structured data that characterizes the supplier's performance capabilities in trade activities from multiple different capability dimensions. The capability dimensions covered can be set according to the matching needs of actual business scenarios, and may include multiple dimensions such as those representing the scope of supply, the scale of supply, the qualification and compliance status, historical performance, service coverage, and credit status.
[0043] It should be noted that when embedding trade capability attribute data into digital certificates, the latest trade capability attribute data is obtained instead of historical data. This is to ensure that the capability attributes written into the digital certificate are consistent with the supplier's actual capability status at the time of issuance, and to avoid issuing certificates with outdated data.
[0044] Step 120: Generate a certificate to be signed for the supplier based on the multi-dimensional trade capability attribute data; the certificate to be signed includes a basic information field and an extended field; the basic information field stores the certificate version number, certificate serial number, issuer information, validity period information, and the supplier's identity information and public key information; the extended field stores the multi-dimensional trade capability attribute data identified by a target object identifier and encoded in a structured encoding mode; the target object identifier is used to identify the trade capability semantic type of the data carried by the extended field.
[0045] It should be noted that the certificate to be signed here refers to an intermediate certificate structure that has completed field content filling but has not yet been signed by the authentication system. For example, it can be a To Be Signed Certificate (TBSCcertificate) structure conforming to the X.509 standard. Logically, the certificate to be signed can be divided into two parts: basic information fields and extended fields.
[0046] The basic information field is used to carry the certificate's own metadata and the supplier's identity credential information, specifically including the following: The certificate version number is used to identify the version of the certificate format that the certificate follows, for example, the value is version 3 in the X.509 standard; A certificate serial number is a unique integer identifier assigned by an authentication system to each digital certificate it issues. Any two digital certificates issued by the same authentication system have different certificate serial numbers, so that the relying party can uniquely locate the digital certificate through the certificate serial number. Issuer information, used to record the name and other identifying information of the authentication system that issued the digital certificate; Validity information is used to record the trustworthy time range of the digital certificate; Supplier identity information is used to record the supplier's main identification information, such as at least one of the supplier's company name, unified social credit code, registered address, etc. The supplier's public key information is used to record the public key and the corresponding public key algorithm identifier in the asymmetric key pair held by the supplier.
[0047] The extension field is an extensible carrying area in the certificate to be signed, distinct from the basic information field. For example, it can be an extension structure defined by the X.509 standard. Each extension includes three parts: an extension type identifier, a key marker, and an extension value. In this embodiment, the authentication system can encode the multi-dimensional trade capability attribute data obtained in step 110 into a byte stream according to a structured encoding mode. This byte stream is then written as an octet string (also called an OCTET STRING) into the extension value part of the extension. The extension type identifier of the extension is set as the target object identifier, and the key marker of the extension is set as a non-key information marker.
[0048] Optionally, during the generation of the certificate to be signed, the authentication system may first construct a blank certificate framework conforming to the X.509 standard.
[0049] For example, the structure of a blank certificate frame can be defined using Abstract Syntax Notation One (ASN.1), with the following specific structure: { Certificate ::= SEQUENCE { tbsCertificate TBSCertificate, signatureAlgorithm AlgorithmIdentifier, signatureValue BIT STRING } TBSCertificate ::= SEQUENCE { version [0] INTEGER {v3(2)}, serialNumber INTEGER, signatureAlgorithmIdentifier, Issuer Name, validity SEQUENCE { notBefore UTCTime, notAfter UTCTime }, subject Name, subjectPublicKeyInfo SubjectPublicKeyInfo, extensions [3] Extensions } }
[0050] The detailed structure of the Extensions field area is as follows: { Extensions ::= SEQUENCE OF Extension Extension ::= SEQUENCE { extnID OBJECT IDENTIFIER, critical BOOLEAN DEFAULT FALSE, extnValue OCTET STRING } }
[0051] In this structure, `Certificate` is the digital certificate and serves as the root sequence. `tbsCertificate` records the core content of the digital certificate, i.e., the subsequence field of the subject to be signed. `signatureAlgorithm` is the algorithm identifier field recording the algorithm used by the authentication system to sign the subject. `signatureValue` is the bit string field recording the signature information generated by the authentication system. `TBSCertificate` is the subsequence corresponding to the subject to be signed. `version` is an integer field recording the certificate version number. `serialNumber` is an integer field recording the unique serial number of the certificate assigned by the authentication system, i.e., the certificate serial number. `signature` is the algorithm identifier field recording the signature algorithm. `issuer` is the name field recording the certificate issuer information. `validity` is a subsequence field recording the certificate validity period information. `subject` is the name field recording the vendor's identity information. `subjectPublicKeyInfo` is a subsequence field recording the vendor's public key information. `extensions` is the extension field area. `notBefore` records the Coordinated Universal Time (UTC) of the effective date. The Time (UTC) field, notAfter is the UTC field that records the expiration time; Extension is the subsequence corresponding to a single extension item, extnID is the object identifier field that identifies the type of extension item, critical is a boolean field that marks whether the extension item is a mandatory critical attribute, and extnValue is an eight-bit byte string field that stores the specific content of the extension item.
[0052] The length of the extended value of the extended field can be configured according to the actual scenario, such as 200-500 bytes or 800-1200 bytes. The length of the basic information field can also be configured according to the actual scenario, such as 800-1200 bytes. The length of the signature information can also be configured according to the actual scenario, such as 64-72 bytes. This embodiment does not make specific limitations on these.
[0053] Subsequently, the certificate version number, the certificate serial number assigned by the authentication system's serial number allocator, the authentication system's own issuer information, the validity period information determined according to the issuance policy, and the supplier's identity information and public key information extracted from the certificate application request or certificate update request are sequentially filled into the basic information field of the blank certificate framework to form the basic certificate framework.
[0054] The conventional purpose of extended fields in a standard certificate is to supplement identity information, and the data stored therein is mostly simple strings or fixed enumeration values. Therefore, to transform the semantic function of extended fields from supplementing identity information to becoming a trade capability credential—that is, to fully embed the structured semantic model of trade capability attributes into extended fields without compromising X.509 certificate standard compatibility—this embodiment can write multi-dimensional trade capability attribute data encoded according to a structured encoding pattern, identified by a target object identifier, into the extended fields of the basic certificate framework containing the basic information fields, thereby obtaining a complete certificate to be signed.
[0055] The target object identifier here refers to the object identifier (OID) that the authentication system pre-registers with the object identifier registration management agency, specifically used to identify the semantic type of trade capability. For example, the authentication system can pre-register with the object identifier registration center to apply for a company-specific object identifier arc as the company root arc. For example, the company root arc can be "1.2.156.XXXXX", where "XXXXX" is the company number actually assigned after registration. Subsequently, the authentication system establishes a sub-arc under the company root arc specifically for trade capability extension. For example, the trade capability extension sub-arc can be "1.2.156.XXXXX.1", and determines the object identifier corresponding to the trade capability extension sub-arc as the target object identifier. The target object identifier identifies the semantic type of the trade capability of the data carried by the extended field. In addition, the authentication system can also establish a sub-arc under the company root arc to carry other custom extensions. For example, the other custom extension sub-arc can be "1.2.156.XXXXX.2", so as to distinguish and manage custom extensions other than trade capability extensions.
[0056] It should be noted that, unlike the object identifiers used in existing standard extensions which are only used to identify supplementary identity information such as key usage and alternate names of entities, the semantic type identified by the target object identifier mentioned in this embodiment is a trade capability semantic type. That is, when any parser reads this target object identifier, it can determine that the data carried in the corresponding extended value is the supplier's multi-dimensional trade capability attribute data, and then parse the extended value according to the preset parsing rules corresponding to the target object identifier. Thus, the target object identifier establishes a definite mapping relationship between encoded data and business semantics, making the data carried in the extended field machine-recognizable and parsable structured data, rather than free text whose business meaning cannot be determined.
[0057] The structured encoding pattern here refers to the pre-agreed encoding rules between the authentication system and various parsing parties, which can unambiguously encode multi-dimensional trade capability attribute data into a byte stream and support reverse decoding and reconstruction. For example, this structured encoding pattern can be implemented using data serialization encoding rules, that is, serializing multi-dimensional attribute data into a binary byte stream according to a preset field order and data type convention; correspondingly, the parsing party can reconstruct the attribute data of each dimension from the byte stream according to the same convention.
[0058] Step 130: Sign the certificate to be signed based on the private key information of the authentication system to obtain signature information.
[0059] It should be noted that the private key information here refers to the private key in the asymmetric key pair held by the authentication system for issuing digital certificates. This private key is kept in the authentication system's internal secure environment and is not disclosed to external parties.
[0060] Optionally, during the signing process, the authentication system first obtains the digest value of the complete byte content of the certificate to be signed, and then uses the private key information to perform a signature operation on the digest value according to a preset signature algorithm to obtain the signature information. The signature algorithm here can be selected according to the actual deployed cryptographic system. For example, the signature algorithm here can be an asymmetric public-key cryptographic algorithm using 256-bit elliptic curve parameters as defined by the national cryptographic standard, namely SM2, or a cryptographic hash algorithm that can convert input data of arbitrary length into a hash digest of fixed 256-bit length, namely SM3. Other asymmetric signature algorithms can also be used, and this embodiment does not limit this.
[0061] It should be noted that because the signature operation covers the entire content of the certificate to be signed, and the certificate contains both basic information fields and extended fields, the resulting signature information simultaneously protects the integrity of the supplier's identity verification information and multi-dimensional trade capability attribute data. If either party tampers with any dimension of the attribute data in the extended fields after the certificate is issued, the relying party will fail to verify the signature using the public key information of the authentication system, thus ensuring the end-to-end integrity and authenticity of the multi-dimensional trade capability attribute data in the extended fields.
[0062] Step 140: Generate the supplier's digital certificate based on the certificate to be signed and the signature information.
[0063] Optionally, the authentication system can encapsulate the certificate to be signed, the signature algorithm identifier, and the signature information according to a preset certificate encapsulation structure to obtain the vendor's digital certificate. For example, according to the X.509 standard certificate structure, the certificate subject to be signed, the signature algorithm identifier, and the signature information are sequentially organized into a complete certificate sequence, thus obtaining a digital certificate that can be released externally.
[0064] After generating a digital certificate, the authentication system can also distribute the digital certificate to the supplier and / or publish the digital certificate to the certificate store so that the purchasing system and other dependent parties can obtain and use the digital certificate in business processes such as order matching.
[0065] The method provided in this embodiment retrieves the latest multi-dimensional trade capability attribute data from the trade management system when responding to certificate application or certificate renewal requests. This data is identified by a target object identifier, encoded using a structured coding pattern, and written into the extended field of the digital certificate. This binds the supplier's identity credentials and multi-dimensional trade capability attribute data to the same digital certificate carrier, and achieves integrity protection through a single signature operation of the authentication system. This eliminates the temporal asynchrony and information inconsistency caused by the separate storage of identity credentials and capability attribute data. It allows the relying party to directly obtain reliable trade capability attribute data while verifying the digital certificate without performing a secondary database query. At the same time, the identification of trade capability semantic types by the target object identifier and the adoption of a structured coding pattern give the data carried by the extended field a unified, machine-resolvable semantic specification, providing a foundation for interoperability of trade capability attribute data between different systems, thereby effectively improving the accuracy and efficiency of order matching.
[0066] In some embodiments, the multi-dimensional trade capability attribute data includes multiple data such as available product categories, production capacity limits, qualification certification data, historical fulfillment rate data, available geographic areas, credit rating, latest review time data, and additional remarks. The qualification certification data includes at least one qualification certification entry, and each qualification certification entry includes a qualification type identifier, an issuing authority, and a qualification expiration date.
[0067] It should be noted that the multi-dimensional trade capability attribute data here can be defined as a structured data structure using Abstract Syntax Notation One (ASN.1), and each dimension of the data corresponds to the following fields in this data structure: The available product category data corresponds to the supplyCategory field in the data structure. Its data type is an array of object identifiers, which is used to record the category codes corresponding to the range of product categories that the supplier can supply. The category codes can be organized using a standard commodity classification system, such as the category codes under the United Nations Standard Products and Services Code (UNSPSC) system, so that different systems can maintain a consistent understanding of the same category.
[0068] The capacity limit data corresponds to the capacityLimit field in the data structure. Its data type is integer, i.e., INTEGER. It is used to record the maximum quantity of goods that a supplier can supply per unit of time. The unit of measurement can be set to pieces / month or tons / month depending on the form of the goods.
[0069] The qualification certification data corresponds to the `qualificationList` field in the data structure. Its data type is sequence (SEQUENCE), used to characterize the compliance status of various qualification certifications held by the supplier. It includes at least one qualification certification entry. Each qualification certification entry includes three items: qualification type identifier, issuing body, and qualification expiration date. The qualification type identifier can be recorded using a qualification type object identifier to uniquely identify the type of qualification, such as the corresponding type identifiers for quality management system certification, environmental management system certification, and Forest Stewardship Council (FSC) certification. The issuing body records the name of the organization that issued the qualification. The qualification expiration date records the expiration date of the qualification's validity. Refining the qualification certification data into an entry-level structure allows for subsequent verification of the validity period of each qualification.
[0070] Historical fulfillment rate data corresponds to the historical fulfillment rate field historyFulfillmentRate in the data structure. Its data type is integer, that is, INTEGER type, which is used to represent the supplier's fulfillment performance in historical trade activities. Its value ranges from 0 to 100.
[0071] The data for serviceable geographic areas corresponds to the geographicScope field in the data structure. Its data type is a string array, specifically a UTF8String array, which is used to record the area codes corresponding to the geographic coverage areas for which the supplier can provide delivery services. For example, administrative division codes can be used to record each serviceable area.
[0072] Credit rating, corresponding to the credit rating field creditTier in the data structure, is an enumeration type, also known as ENUMERATED, used to represent the credit status of suppliers. Its enumeration values can be divided into four levels: A, B, C, and D.
[0073] The latest audit time data corresponds to the audit time field lastAuditTime in the data structure. Its data type is time, specifically UTCTime. It is used to record the time when the trade management system last completed the audit of the supplier's capability attribute data, so that the parser can determine the timeliness of the capability attribute data.
[0074] Additional notes information corresponds to the special capability notes field specialRequirement in the data structure. Its data type is string, specifically UTF8String, and it is used to record supplementary capability descriptions beyond the above dimensions, such as special capability notes possessed by the supplier. For example, this additional notes information can record that the supplier supports customized printing.
[0075] The method provided in this embodiment refines the supplier's performance capability into multiple dimensions such as supply scope, supply scale, qualification compliance, historical performance, service coverage, credit status, review timeliness, and supplementary descriptions. It also refines the qualification certification data into an item-level structure that includes qualification type identifier, issuing authority, and qualification expiration time. This allows the trade capability information carried by the digital certificate to cover all the judgment dimensions required for order matching, providing complete and verifiable data information for order matching.
[0076] In some embodiments, the validity period information includes the effective time and the expiration time; the step of determining the expiration time includes: determining the earliest expiration time among the expiration times of each qualification certification entry in the qualification certification data, and determining the expiration time as earlier than or equal to the earliest expiration time.
[0077] The effective time is used to record the start time when a digital certificate begins to be trusted, such as the issuance time; the expiration time is used to record the end time when a digital certificate stops being trusted.
[0078] It should be noted that, unlike the method of uniformly setting the expiration time to a fixed period after the issuance date, in this embodiment, the authentication system, during the process of generating the certificate to be signed, iterates through the qualification expiration time of each qualification qualification entry in the qualification authentication data, and determines the earliest one, which is recorded as the earliest expiration qualification time. Then, the expiration time of the digital certificate is determined to be earlier than or equal to the earliest expiration qualification time.
[0079] For example, if a supplier's qualification certification data contains two qualification certification entries, one is a quality management system certification entry with an expiration date of June 1, 2027, and the other is a Forest Stewardship Council certification entry with an expiration date of December 31, 2025, then the certification system determines the earliest expiration date of the qualification to be December 31, 2025, and determines the expiration date of the supplier's digital certificate to be no later than December 31, 2025.
[0080] The method provided in this embodiment binds the expiration time of the digital certificate to the earliest expiration time of each qualification and certification entry, so that the digital certificate implicitly guarantees that all qualification and certification entries in its extended field are within the validity period at any time before its expiration time. Furthermore, this setting constitutes a fallback mechanism for data consistency. Even if the dependent party is offline and cannot obtain certificate change notifications, the digital certificate will naturally expire when any qualification it carries expires, thereby avoiding the situation where the qualification has expired but the digital certificate is still trusted.
[0081] In some embodiments, the multi-dimensional trade capability attribute data is written into the extended fields through the following steps: organizing the multi-dimensional trade capability attribute data according to a nested hierarchical structure; the nested hierarchical structure includes a root sequence, sub-sequences, and basic types; encoding the organized multi-dimensional trade capability attribute data into at least one target byte stream according to the structured encoding mode; and, if there are multiple extended fields, writing each target byte stream into the extended field corresponding to each target byte stream according to the target object identifier corresponding to each target byte stream.
[0082] It should be noted that the conventional purpose of extended fields is to supplement identity information, and the data they carry is mostly simple strings or fixed enumeration values. However, multi-dimensional trade capability attribute data is hierarchical data with nested structures. Therefore, fully encoding this hierarchical data and adapting it to the octet encapsulation format of the extended fields presents a structural adaptation problem. To address this, this embodiment uses a method of organizing data according to a nested hierarchical structure to solve the structural adaptation problem.
[0083] The nested hierarchical structure here is organized according to a three-level nested architecture of root sequence, subsequence, and basic type: the root sequence serves as the outermost container, containing all the top-level fields of multi-dimensional trade capability attribute data; the subsequence serves as the middle layer container, used to encapsulate list-type attribute data, such as qualification certification data nested as a subsequence under the root sequence, and each qualification certification entry further contains three fields as a subsequence: qualification type identifier, issuing authority, and qualification expiration time; the basic type serves as the innermost data unit, used to carry atomic data such as integers, strings, time, and enumeration values.
[0084] Optionally, the nested hierarchical structure can be defined using ASN.1. For example, the nested hierarchical structure of multi-dimensional trade capability attribute data can be defined as follows: { TradeCapability ::= SEQUENCE { version INTEGER (0..255), supplyCategory SEQUENCE OF OBJECT IDENTIFIER, capacityLimit INTEGER (0..2147483647), qualificationList SEQUENCE OF QualificationInfo, historyFulfillmentRate INTEGER (0..100), geographicScope SEQUENCE OF UTF8String, creditTier ENUMERATED {A(1), B(2), C(3), D(4)}, lastAuditTime UTCTime, specialRequirement UTF8String OPTIONAL } QualificationInfo ::= SEQUENCE { qualType OBJECT IDENTIFIER, issuer UTF8String, validUntil UTCTime } }
[0085] Among them, TradeCapability is the root sequence, version is an integer field that records the version of the extended field data structure, supplyCategory is a list of object identifiers that records the available product categories, capacityLimit is an integer field that records the upper limit of production capacity, qualificationList is a list of subsequences that record qualification certification data, historyFulfillmentRate is an integer field that records the historical fulfillment rate data, geographicScope is a list of strings that records the available geographical areas, creditTier is an enumerated field that records the credit rating, lastAuditTime is a time field that records the latest audit time data, and specialRequirement is an optional string field that records additional remarks information; QualificationInfo is the subsequence corresponding to the qualification certification item, qualType is the qualification type identifier field, issuer is the issuing authority field, and validUntil is the qualification expiration time field.
[0086] After organization is completed, the certification system encodes the multi-dimensional trade capability attribute data into at least one target byte stream according to a structured coding pattern. Here, the target byte stream refers to the binary byte sequence ultimately written into the extended fields; its number is determined based on the resource consumption of the encoding result and can be one or more.
[0087] When there are multiple extended fields, the authentication system assigns a corresponding target object identifier to each target byte stream and writes each target byte stream into its corresponding extended field according to its corresponding target object identifier.
[0088] It should be noted that the identifiers for each target object can be pre-assigned from the trade capability extension sub-arcs established by the authentication system under the enterprise root arc.
[0089] For example, if the enterprise root arc is "1.2.156.XXXXX" and the trade capability extension sub-arc is "1.2.156.XXXXX.1", then subordinate sub-arcs can be reserved for each dimension under the trade capability extension sub-arc. That is, subordinate sub-arc 1 corresponds to the supply category field supplyCategory, subordinate sub-arc 2 corresponds to the capacity limit field capacityLimit, subordinate sub-arc 3 corresponds to the qualification list field qualificationList, subordinate sub-arc 4 corresponds to the historyFulfillmentRate field historyFulfillmentRate, subordinate sub-arc 5 corresponds to the geographic scope field geographicScope, subordinate sub-arc 6 corresponds to the credit rating field creditTier, subordinate sub-arc 7 corresponds to the audit time field lastAuditTime, and subordinate sub-arc 8 corresponds to the special capability remarks field specialRequirement, so as to distinguish and identify the attribute content carried by different target byte streams and their internal fields.
[0090] The method provided in this embodiment organizes hierarchical trade capability attribute data with nested structures into a structured form that can be unambiguously encoded through a three-layer nested architecture of root sequence, subsequence, and basic type, thus solving the structural adaptation problem between hierarchical data and extended field encapsulation format. At the same time, by writing the corresponding target byte stream according to the target object identifier when there are multiple extended fields, the multi-dimensional trade capability attribute data can be fully carried under the capacity constraints of the extended fields, ensuring the integrity and parsability of the data writing.
[0091] In some embodiments, encoding the organized multi-dimensional trade capability attribute data into at least one target byte stream according to the structured encoding mode includes: encoding the organized multi-dimensional trade capability attribute data into an initial byte stream according to the encoding format of data serialization encoding; optimizing the encoding of the initial byte stream based on the data characteristics of each dimension of trade capability attribute data and the resource information occupied by the initial byte stream to obtain at least one target byte stream; wherein the optimized encoding includes at least one of unique encoding, compression encoding, and split encoding; the compression encoding includes prefix arc sharing encoding and / or number mapping encoding.
[0092] It should be noted that although the X.509 standard specifies a maximum allowable size of 65,536 bytes for a single extended field, in practical applications, due to constraints on certificate transmission efficiency and parsing performance, it is generally recommended to limit a single extended field to within 1,024 bytes. Furthermore, multi-dimensional trade capability attribute data, after serialization and encoding, typically occupies 200 to 500 bytes, and may reach 800 to 1,200 bytes in scenarios involving multiple product categories and certification entries. This creates a contradiction between the limited length of extended fields and the capacity of embedded data structures. This embodiment addresses this contradiction by optimizing the encoding.
[0093] Specifically, the authentication system first encodes the organized multi-dimensional trade capability attribute data into an initial byte stream according to the data serialization encoding format. The data serialization encoding format here can be implemented using an encoding format based on the Type-Length-Value (TLV) structure, that is, for each data unit, its type marker, length marker, and value content are recorded sequentially.
[0094] Subsequently, the authentication system optimizes the encoding of the initial byte stream based on the data characteristics of the trade capability attribute data of each dimension and the resource information occupied by the initial byte stream.
[0095] The data characteristics here refer to the features of each dimension attribute data in terms of type, value range and structure. For example, credit rating is an enumeration type with limited values, and the data of the geographic areas that can be served is a list of codes with a common prefix. The resource information here refers to the quantitative information of storage resources occupied, such as the length of the initial byte stream.
[0096] Specifically, optimized coding includes at least one of the following: Uniqueness encoding. This involves using Distinguished Encoding Rules (DER) to encode data. Unlike Basic Encoding Rules (BER), which allow multiple valid encoding forms for the same data, DER ensures that identical data produces a unique byte stream, thus eliminating encoding ambiguity, guaranteeing consistent decoding results for the same extended field by any parser, and ensuring the deterministic nature of the byte content relied upon for signature verification. Building upon uniqueness encoding, type-length-value level encoding optimizations can be performed based on data characteristics. For example, credit ratings of enumerated types can be encoded using 1-byte integers, string fields can use minimum length marker encoding (short strings use 1-byte markers, long strings use multi-byte markers), and lists of object identifiers can use sequence aggregation encoding to avoid recording the same type marker repeatedly.
[0097] Compression encoding. Compression encoding here includes prefix arc sharing encoding and / or numeric mapping encoding. Prefix arc sharing encoding refers to sharing the recording of a common prefix arc for multiple object identifiers with the same prefix arc, only recording the sub-arc differences that distinguish each object identifier from the common prefix arc. For example, when all category object identifiers in the available product category data are under the same trade capability extension sub-arc, only the common arc needs to be recorded once, and only the sub-arc difference values are transmitted. Numeric mapping encoding refers to mapping enumerable string data to a pre-agreed numeric code for recording. For example, mapping the region name in the available geographic region data to a six-digit administrative division numeric code, replacing region A1 with the numeric code 310000, thereby reducing the byte size of the string data.
[0098] Split encoding. This means that when the resource information occupied by the initial byte stream, i.e., its length, exceeds a preset resource threshold, the initial byte stream is split into multiple target byte streams. For example, if the preset resource threshold is set to 1024 bytes, when the length of the initial byte stream exceeds this threshold, the authentication system will split the multi-dimensional trade capability attribute data into a core capability part and a detailed capability part, encoding them separately. The core capability part includes data on available product categories, production capacity limits, credit rating, and the latest approval time. The detailed capability part includes qualification certification data, serviceable geographical area data, historical fulfillment rate data, and additional remarks. These two parts are encoded into two target byte streams, each assigned a different target object identifier to be written into two independent extended fields.
[0099] The method provided in this embodiment eliminates encoding ambiguity and ensures the determinism of the verification benchmark through unique encoding. It reduces the byte stream's occupation of extended field storage resources through prefix arc sharing encoding and digital mapping encoding. By splitting the encoding, attribute data exceeding the carrying capacity of a single extended field can be distributed and stored completely in multiple extended fields. Thus, under the capacity constraint of extended fields, it achieves complete and unambiguous carrying of multi-dimensional trade capability attribute data, and resolves the contradiction between the limited length of extended fields and the capacity of embedded data structures.
[0100] In some embodiments, before writing each of the target byte streams into the extended fields corresponding to each of the target byte streams according to the target object identifier corresponding to each of the target byte streams, the method further includes: dividing each field in each of the target byte streams into public fields, restricted fields, or sensitive fields; keeping the public fields in each of the target byte streams in plaintext; encrypting the restricted fields in each of the target byte streams using the symmetric key of the authentication system; and encrypting the sensitive fields in each of the target byte streams using the public key information of the supplier's demand side.
[0101] It should be noted that the sensitivity of data in each dimension of the multi-dimensional trade capability attribute data varies. If all data is written in plaintext to the extended fields, any entity that obtains the digital certificate can read all the supplier's capability information, posing a problem of exposing commercial information. To address this, this embodiment designs a field-level hierarchical protection mechanism.
[0102] Specifically, before writing multi-dimensional trade capability attribute data into the extended fields, the certification system categorizes the fields in each target byte stream into three types: public fields, restricted fields, and sensitive fields. Public fields are those that can be parsed by all verifiers, such as fields corresponding to available product categories, serviceable geographic areas, and credit ratings. Restricted fields are those that can only be parsed by authorized verifiers, such as fields corresponding to capacity limits and historical fulfillment rates. Sensitive fields are those containing supplier-specific information that can only be parsed by specific demanders, such as fields corresponding to additional remarks information.
[0103] For public fields, the authentication system keeps them in plaintext, that is, writes them directly in their original encoded form, which can be parsed by any verifier.
[0104] For restricted fields, the authentication system uses a symmetric key maintained by the authentication system to encrypt them. For example, it uses the SM4 symmetric encryption algorithm in commercial cryptography standards to encrypt the value of the restricted field with the SM4 symmetric key maintained by the authentication system, and then embeds the encrypted octet into the target byte stream to replace the original value. Accordingly, only the authorized verification party holding the symmetric key can decrypt and restore the value of the restricted field.
[0105] For sensitive fields, the authentication system uses the public key information of the supplier's client to encrypt them. For example, using SM2, the value of the sensitive field is embedded after asymmetric encryption with the public key of the specific client. Accordingly, only the specific client holding the corresponding private key can decrypt and read the content of the sensitive field.
[0106] The method provided in this embodiment achieves a hierarchical disclosure and on-demand decryption privacy protection mechanism by dividing each field into public fields, restricted fields, and sensitive fields and applying differentiated encryption protection. This allows different verification parties to read capability information of different granularities based on their own keys and authorization status. While ensuring that the information required for order matching is available, it avoids exposing the supplier's production capacity, performance, and proprietary capabilities and other commercial information to unauthorized entities.
[0107] In some embodiments, the certificate update request is triggered upon receiving a positive change event pushed by the trade management system, the positive change event indicating a change in the content of the supplier's multi-dimensional trade capability attribute data; obtaining the supplier's latest multi-dimensional trade capability attribute data from the trade management system includes: in response to the certificate update request, verifying the authenticity of the positive change event with the trade management system; if the positive change event passes the authenticity verification, obtaining the supplier's latest multi-dimensional trade capability attribute data from the trade management system; all qualification certification entries in the latest multi-dimensional trade capability attribute data are in an unexpired state.
[0108] It should be noted that the trade management system, as the sole data source for multi-dimensional trade capability attributes, generates structured change events when any capability attribute changes. Positive change events here refer to events that indicate a change in the content of the supplier's multi-dimensional trade capability attribute data without triggering changes that restrict the supplier's capabilities. For example, the event corresponding to a change in the supplier's maximum production capacity data from 10,000 units per month to 20,000 units per month.
[0109] It should be noted that any change event, whether positive or negative, can be organized using a structured data format. This format can record information such as supplier identifier, change type, change fields, values before and after the change, change time, and reason for the change. This allows the authentication system to differentiate processing logic based on the change type. For example, a change event can be defined as follows: {"supplierId":"A", "changeType":"NEGATIVE", "changeField":"qualificationList.FSC", "oldValue":"validUntil:2025-12-31", "newValue":"EXPIRED", "changeTime":"2026-01-01T00:00:00+08:00", "reason": "FSC certification expired and was not renewed" }
[0110] Among them, supplierId is the supplier identifier field, changeType is the change type field, changeField is the location information of the change field, oldValue is the value before the change, newValue is the value after the change and it indicates that the qualification has expired, changeTime is the change time, and reason is the reason for the change.
[0111] Change events can be pushed from the trade management system to the authentication system through a pre-established secure message channel, such as a message queue channel established using the Transport Layer Security (TLS) protocol combined with SM2 two-way authentication, to ensure the confidentiality and source credibility of change events during transmission.
[0112] Optionally, upon receiving a positive change event triggering a certificate update request, the authentication system does not directly issue a new certificate based on the changes contained in the event. Instead, it first verifies the authenticity of the positive change event with the trade management system. For example, by calling the query interface of the trade management system, it cross-compares the changed fields and their changed values recorded in the event with the current records in the trade management system. If they match, the positive change event is deemed to have passed the authenticity verification. This prevents forged change events from driving the authentication system to issue digital certificates containing false capability attribute data.
[0113] If the positive change event passes authenticity verification, the certification system retrieves the supplier's latest multi-dimensional trade capability attribute data from the trade management system. It's important to note that this retrieves the full, up-to-date data, not just the changed fields, to ensure overall consistency across all dimensions when writing the new digital certificate. Furthermore, all qualification certification entries in this latest multi-dimensional trade capability attribute data are still valid; that is, in a positive change scenario, all of the supplier's qualifications are within their validity period. The certification system can then use this data to re-execute complete structured coding and issue a new digital certificate.
[0114] It should be noted that the certificate serial number of a newly issued digital certificate can be incremented based on the original certificate serial number, so that the relying party can determine the latest version of the digital certificate by comparing the certificate serial numbers.
[0115] The method provided in this embodiment drives certificate update requests with positive change events pushed by the trade management system, and reissues digital certificates with all the latest data after the authenticity verification is passed. This allows the trade capability attributes in the digital certificate to be updated in tandem with the improvement of the supplier's capabilities, eliminating the lag in change response. At the same time, the authenticity verification process prevents the interference of forged change events on the issuance process, ensuring the authenticity of the capability attribute data in the newly issued digital certificate.
[0116] In some embodiments, the method further includes: upon receiving a negative change event pushed by the trade management system, verifying the authenticity of the negative change event with the trade management system; the negative change event is used to indicate that some of the supplier's qualification certification entries have expired or its credit rating has been reduced; if the negative change event passes the authenticity verification, adding the supplier's current digital certificate to the revocation list, updating the extended fields of the supplier's current digital certificate according to the event type of the negative change event, generating a new digital certificate for the supplier based on the updated extended fields; publishing the revocation status of the supplier's current digital certificate, and pushing the new digital certificate to subscribers who subscribe to the supplier's certificate change notifications.
[0117] It should be noted that negative change events refer to events that result in limitations on a supplier's capabilities. Specifically, they indicate that some of the supplier's certifications have expired or their credit rating has been lowered. Examples include the expiration of a supplier's Forest Stewardship Council certification or the downgrade of a supplier's credit rating from B to D. The notification channel and verification method for negative change events are the same as those for positive change events, and will not be repeated here.
[0118] If a negative change event passes authenticity verification, the authentication system adds the vendor's current digital certificate to the revocation list. This revocation list can be a Certificate Revocation List (CRL). The authentication system writes the current digital certificate's serial number to the CRL and can record the revocation reason as "certificate replacement," along with the revocation date.
[0119] Subsequently, the authentication system updates the extended fields of the current digital certificate based on the event type of the negative change event. For example, if the event type is "certification entry expires," the authentication system removes the expired certification entry from the certification data carried by the extended fields; if the event type is "credit rating downgrade," the authentication system updates the credit rating carried by the extended fields to the downgraded rating. The authentication system then re-executes structured coding and signing based on the updated extended fields to generate a new digital certificate for the vendor. It should be noted that the expiration time of the new digital certificate can be redefined as the earliest expiration time among the remaining valid certification entries.
[0120] In addition, to ensure consistency between revocation and issuance, the authentication system can use database transaction operations to perform the above processing. That is, the operation of adding the current digital certificate to the revocation list and the operation of issuing a new digital certificate are completed in the same transaction, ensuring the atomicity of the two and avoiding the intermediate state where the old certificate has been revoked but the new certificate has not been issued.
[0121] In addition, the authentication system can record the operation time, change content and operator information of each change operation in an anti-tamper log, such as in a blockchain ledger or a log system with anti-tamper capabilities, to form a traceable change audit record.
[0122] After completing the revocation and issuance of a new certificate, the authentication system publishes the current revocation status of the digital certificate and pushes the new digital certificate to subscribers who have subscribed to the vendor's certificate change notifications. This revocation status can be communicated in real time via the Online Certificate Status Protocol (OCSP), allowing any dependent party to detect the revocation status within seconds when initiating a certificate status query to the authentication system. Subscriber pushes can be implemented using a webhook approach; that is, after issuing a new certificate or revoking an old certificate, the authentication system proactively pushes the new digital certificate or revocation notification to the pre-subscribed procurement system. Correspondingly, upon receiving the change notification, the procurement system can refresh its locally maintained vendor certificate cache and, if the revocation is triggered by a credit rating downgrade or qualification expiration, remove the vendor from the candidate list, preventing them from being included in subsequent order matching.
[0123] The following description uses a specific example scenario to illustrate this embodiment.
[0124] A supplier holds a digital certificate with serial number 1001. The extended fields of this certificate contain qualification certification data including a Quality Management System certification entry and a Forest Stewardship Council (FSC) certification entry. The FSC certification entry's expiration date is December 31, 2025. When this qualification expires and is not renewed, the trade management system pushes a negative change event to the certification system. This event records the supplier's identifier, the change type as negative change, the changed field as the FSC certification entry in the qualification certification data, the original validity period of the entry before the change, the expired value after the change, the change time, and the reason for the change as the certification expiring and not being renewed. The certification system verifies the authenticity of the event with the trade management system. Upon successful verification, it adds the digital certificate with certificate serial number 1001 to the certificate revocation list within the same database transaction, recording the reason for revocation as certificate replacement. Simultaneously, it issues a new digital certificate with certificate serial number 1002. The extended field of this new digital certificate has the Forest Stewardship Council (FSC) certification entry removed, the credit rating remains unchanged, and its expiration date is redefined as the qualification expiration date of the remaining quality management system certification entry, i.e., June 1, 2027. The byte usage of the extended field is also reduced accordingly due to the entry removal. Subsequently, the certification system publishes the revocation status of the digital certificate with certificate serial number 1001 via the online certificate status protocol and pushes the new digital certificate with certificate serial number 1002 to subscribers. Correspondingly, the procurement system removes the supplier from the current candidate list after detecting that the old certificate has been revoked. In subsequent orders requiring only quality management system certification, the supplier re-enters the candidate range with the new digital certificate; however, in subsequent orders requiring both FSC certification and certification, the supplier is no longer matched.
[0125] The method provided in this embodiment, through a negative change event-driven instant revocation and reissue mechanism, keeps the status of digital certificates linked to the actual capability status of the supplier. This shortens the change response cycle from a day-long period relying on timed batch imports to a second-level perception based on online certificate status protocols, eliminating the risk that a digital certificate may still be trusted even if its qualification has expired. At the same time, transactional revocation and reissue operations and tamper-proof change audit records ensure the atomicity and traceability of the certificate status switching process.
[0126] In some embodiments, the extended field further includes tag information and version information; the tag information is used to identify that the content information of the extended field is non-critical extended information; the version information is used to identify the data structure version of the extended field.
[0127] It's important to note that transforming the semantic function of the extended field from identity supplementation to trade capability bearing must be achieved without compromising X.509 certificate standard compatibility. Otherwise, existing certificate verification software that doesn't support this extension might reject the entire digital certificate when encountering an unrecognized extension. To address this, the authentication system sets a marker in the extended field, indicating its content as non-critical extended information—essentially setting the critical marker of the extended item to non-critical. Thus, certificate verification software that doesn't support the target object identifier can safely ignore this extended field when parsing the digital certificate, performing only regular authentication logic, thereby achieving backward compatibility. Meanwhile, procurement systems that support the target object identifier can parse and utilize the multi-dimensional trade capability attribute data in this extended field.
[0128] Furthermore, the authentication system sets version information in the header of the data carried by the extended field to identify the data structure version of that extended field. It should be noted that the version information can be implemented using a 1-byte version number. The authentication system increments the version number as the data structure of the multi-dimensional trade capability attribute data evolves. Correspondingly, when parsing the extended field, the certificate verifier first reads this version number and selects the parser corresponding to the data structure version based on the version number. This ensures that both old and new versions of digital certificates can be correctly parsed after data structure evolution, achieving backward compatibility.
[0129] For example, in a negative change scenario, the version number of the data carried by the extended field of the newly issued digital certificate can be incremented from 1 to 2 based on the original digital certificate.
[0130] The method provided in this embodiment ensures the compatibility of digital certificates with existing verification software that does not support trade capability extensions by using non-critical extended marking information, and reserves version management capabilities for the subsequent evolution of the data structure by using version information, thereby ensuring the compatibility of digital certificates while realizing the semantic carrying of trade capabilities.
[0131] Figure 2 This is a flowchart illustrating the order matching method provided by the present invention. Figure 2 As shown in the figure, this embodiment of the invention also provides an order matching method, the execution subject of which can be a procurement system. The method specifically includes steps 210, 220, 230, and 240.
[0132] Step 210: Obtain the demand information of the orders to be processed and a list of candidate supplier digital certificates; the list of candidate supplier digital certificates includes digital certificates from multiple candidate suppliers.
[0133] The "pending orders" here refer to purchase orders initiated by the buyer that have not yet had a supplier selected. The "demand information" here refers to the set of demand attributes extracted from the pending orders, used for comparison with supplier capabilities. These attributes may include, for example, multiple items such as the category code of the required goods, purchase quantity, delivery region, and required qualification types. The "candidate supplier digital certificate list" here includes digital certificates from multiple candidate suppliers, each candidate supplier's digital certificate being based on, for example... Figure 1 The digital certificate generation method shown generates a multi-dimensional trade capability attribute data identified by the target object identifier in its extended fields.
[0134] It should be noted that the procurement system can obtain the list of candidate supplier digital certificates from its locally maintained supplier certificate cache, or it can obtain the list of candidate supplier digital certificates from the certificate store published by the certification system. This embodiment does not limit this.
[0135] Step 220: Verify the identity validity of the digital certificates of each candidate supplier, and based on the verification results of the digital certificates of each candidate supplier, obtain the digital certificates of each supplier to be matched that have passed the identity validity verification from the list of candidate supplier digital certificates.
[0136] Optionally, the procurement system can verify the identity and validity of each candidate supplier's digital certificate based on the basic information field in the digital certificate of each candidate supplier. Specifically, it can verify whether the candidate supplier's digital certificate is genuinely issued by the certification system, is within its validity period, and has not been revoked.
[0137] Then, based on the verification results, the procurement system identifies the suppliers corresponding to the digital certificates that have passed the identity validity verification as the suppliers to be matched.
[0138] Step 230: Based on the target object identifier in the extended field of the digital certificate of each of the suppliers to be matched, parse the multi-dimensional trade capability attribute data of each supplier to be matched.
[0139] Optionally, the procurement system iterates through the extensions in the digital certificates of the suppliers to be matched. When it reads an extension whose extension type is identified as the target object identifier, it determines that the extension value of the extension carries multi-dimensional trade capability attribute data. Then, it reverse-decodes the byte stream in the extension value according to the structured encoding mode corresponding to the target object identifier to restore the attribute data of each dimension.
[0140] It should be noted that, in order to restore the decoded encoded values to business semantics, the procurement system can perform mapping decoding based on a pre-maintained structure mapping table from object identifiers to semantics. This structure mapping table is used to map each object identifier in the data encoded according to distinguishable encoding rules to user-readable semantic information such as category names and qualification names, realizing bidirectional conversion from encoding to semantics.
[0141] For example, a category object identifier under the extended sub-arc of trade capabilities, such as the object identifier "1.2.156.XXXXX.1.1", can be mapped to the category name "corrugated cardboard box", and the category code corresponding to this category name is "14111507". Thus, after parsing the category object identifier in the supplyCategory field, the procurement system can reverse-lookup the mapping table to reconstruct the corresponding category code and category name, and determine whether it matches the category code in the demand information of the pending order. Similarly, the procurement system can maintain a mapping table between administrative division codes and region names to reconstruct readable region names from the numerical codes in the serviceable geographic area data, comparing them with the delivery region of the pending order. It can also maintain a registry of qualification type object identifiers, which records qualification type object identifiers corresponding to various qualification types such as quality management system certification, environmental management system certification, and Forest Stewardship Council certification. After parsing the qualification certification data, the procurement system verifies whether the qualification type identifiers are registered in this registry to prevent counterfeit qualification types from being mixed in.
[0142] In addition, the aforementioned structure mapping table and registry can be distributed through configuration certificates periodically issued by the authentication system to ensure the authenticity and timeliness of the mapping data itself.
[0143] Step 240: Perform multi-dimensional matching between the demand information and the multi-dimensional trade capability attribute data of each of the suppliers to be matched, and output the matching results.
[0144] The multi-dimensional matching here can be performed dimension by dimension according to preset matching rules. The matching rules include at least one or any combination of category matching, production capacity matching, regional matching, qualification matching, and credit rating screening: Category matching determines whether the category code in the demand information belongs to the supplyable category data of the supplier to be matched; Production capacity matching determines whether the purchase quantity in the demand information is less than or equal to the upper limit of the production capacity of the supplier to be matched; Regional matching determines whether the delivery area in the demand information belongs to the serviceable geographical area data of the supplier to be matched; Qualification matching iterates through the qualification types required by the demand information and determines whether there are corresponding qualification certification entries in the qualification certification data of the supplier to be matched, and whether the expiration time of each corresponding entry is later than the current time; Credit rating screening determines whether the credit rating of the supplier to be matched meets the rating conditions set in the demand information.
[0145] Optionally, in addition to dimension-by-dimensional matching, the procurement system can also perform consistency verification at the logical layer: for example, if the historical fulfillment rate data of the supplier to be matched is lower than the preset fulfillment rate threshold, even if its capacity limit data meets the requirements, it will be marked as a high-risk supplier in the matching results instead of being directly excluded; or, if the latest audit time data of the supplier to be matched is more than the preset audit validity period from the current time, it will be marked as pending audit update in the matching results.
[0146] If all dimensions meet the matching rules, the procurement system outputs a successful matching result. For example, it sorts the successfully matched suppliers according to their credit rating and / or historical performance rate data and outputs the results. The matching results can include the judgment details of each matching dimension, credit rating, historical performance rate data, additional remarks and marking information. If any dimension does not meet the matching rules, the procurement system outputs a failed matching result and records the specific dimension that was not met and the reasons for the failure, so that the purchaser can locate the cause of the mismatch.
[0147] It should be noted that since all the capability attribute data required for order matching is carried on the digital certificate itself, and its integrity is protected by the signature information of the authentication system, the procurement system can complete the integrity verification and matching comparison of the multi-dimensional trade capability attribute data in the digital certificate with the public key information of the authentication system even when offline, without having to access the centralized trade database in real time.
[0148] The offline status here refers to the operational status where the network connection between the procurement system and the certification system and / or trade management system is interrupted, and the certificate status query cannot be initiated in real time. This could be due to network link failure, temporary unavailability of the certification system's status query service, or other similar situations.
[0149] Furthermore, considering that in offline mode, although the procurement system can complete signature verification based on the public key information of the authentication system and expiration verification based on the validity period information, it cannot obtain the revocation status of digital certificates in real time through the online certificate status protocol. That is, there is a possibility that the digital certificate has been revoked due to a negative change event, but the procurement system has not yet realized it. Therefore, this embodiment also provides an offline verification degradation strategy, which specifically includes: When the procurement system is offline, it can mark the matching results obtained offline as pending online confirmation. This allows the procurement system to postpone subsequent order allocation operations based on the matching results, or to display the pending online confirmation mark when showing the matching results to the purchaser.
[0150] Upon detecting a restored network connection, the procurement system automatically triggers an online certificate status protocol query. This query, based on the certificate serial numbers of the digital certificates corresponding to the matching results marked as pending network confirmation, initiates an online certificate status protocol query with the authentication system to confirm the latest status of each digital certificate. If the query result indicates that the digital certificate has not been revoked, the procurement system removes the pending network confirmation mark from the corresponding matching result, confirming it as a valid match. If the query result indicates that the digital certificate has been revoked, the procurement system removes the corresponding matching result and removes the supplier corresponding to that digital certificate from the candidate list.
[0151] It should be noted that by using the offline verification downgrade strategy, it can be ensured that even if the procurement system cannot obtain any change notifications in an offline state, the digital certificate will naturally expire when any qualification it carries expires, thus being excluded from the expiration verification process. Furthermore, for revocations triggered by negative changes such as credit rating reductions that occurred before the expiration time, supplementary verification can be performed by online certificate status protocol queries that are automatically triggered after the network is restored and the network confirmation mark is connected. This ensures both the feasibility of matching operations in an offline state and supplementary verification of digital certificates in an online state.
[0152] The method provided in this embodiment merges the two independent stages of identity verification and database query in the prior art into an atomic determination based on a single digital certificate carrier by completing identity validity verification and multi-dimensional trade capability attribute data parsing and comparison in a single certificate processing flow. This eliminates the problem of inconsistency between the matching results and the real-time status of the supplier due to the lack of atomic association between the two stages, and reduces the overhead of secondary queries to the centralized database. At the same time, based on the offline verification feature of digital certificates, order matching no longer depends on the real-time availability of the centralized database, avoiding the concentrated query pressure caused by the increase in the number of suppliers and constraint dimensions, and also avoiding the situation where order matching cannot be executed due to network interruption or database failure, effectively improving the accuracy and execution efficiency of order matching.
[0153] In some embodiments, verifying the identity validity of the digital certificates of each candidate vendor includes: for each candidate vendor's digital certificate, verifying the signature information of the digital certificate using the public key information of the authentication system to obtain a first verification result; verifying whether the digital certificate has expired based on the validity period information in the basic information field of the digital certificate to obtain a second verification result; verifying whether the digital certificate has been revoked based on the certificate serial number in the basic information field of the digital certificate to obtain a third verification result; determining that the digital certificate has passed the identity validity verification when the first verification result indicates that the digital certificate has passed the signature verification, the second verification result indicates that the digital certificate has not expired, and the third verification result indicates that the digital certificate has not been revoked; and traversing the digital certificates of each candidate vendor to obtain the verification result of the digital certificates of each candidate vendor.
[0154] Optionally, for each candidate supplier's digital certificate, the procurement system performs the following verification: Signature Verification. The procurement system uses the publicly available public key information from the authentication system to verify the signature information of the digital certificate according to the signature algorithm identifier recorded in the digital certificate, obtaining the first verification result. For example, when the signature algorithm is SM2 elliptic curve public key cryptography combined with SM3 cryptographic hash algorithm, the procurement system re-executes the hash operation on the part of the digital certificate to be signed, and uses the public key information from the authentication system to verify the correspondence between the signature information and the hash result. This verifies whether the identity verification information and multi-dimensional trade capability attribute data in the digital certificate have been tampered with since issuance. If the identity verification information and multi-dimensional trade capability attribute data in the digital certificate have not been tampered with since issuance, the first verification result is determined to be successful; otherwise, the first verification result is determined to be unsuccessful.
[0155] Expiration Verification. The procurement system reads the validity period information from the basic information field of the digital certificate and compares the current time with the effective and expiration times in the validity period information. If the current time falls between the effective and expiration times, a second verification result is obtained indicating that the digital certificate has not expired. Since the expiration time is earlier than or equal to the earliest expiration time of the qualification certificate, the second verification result indicates that it has not expired, meaning that all qualification certification items carried by the digital certificate are within their validity period.
[0156] Revocation verification. The procurement system reads the certificate serial number from the basic information field of the digital certificate and verifies whether the digital certificate has been revoked based on the certificate serial number to obtain a third verification result. Specifically, revocation verification can be achieved by initiating an online certificate status protocol query to the authentication system, that is, obtaining the revocation status of the digital certificate in real time based on the certificate serial number; it can also be achieved by downloading the certificate revocation list published by the authentication system and checking whether the certificate serial number is recorded in the certificate revocation list; or it can be achieved by attaching the online certificate status protocol response during the handshake transmission, etc., which are not limited in this embodiment.
[0157] Furthermore, if the first verification result indicates that the digital certificate has passed the signature verification, the second verification result indicates that the digital certificate has not expired, and the third verification result indicates that the digital certificate has not been revoked, the procurement system determines that the digital certificate has passed the identity validity verification.
[0158] If any one of the above three verifications fails, the digital certificate is deemed to have failed the identity validity verification.
[0159] The procurement system can obtain the verification results of each candidate supplier's digital certificate by iterating through each digital certificate in the candidate supplier digital certificate list and repeating the above verification.
[0160] The method provided in this embodiment verifies digital certificates by jointly executing signature verification, expiration verification, and revocation verification. This ensures that each digital certificate involved in order matching is genuinely issued by the authentication system, is within its validity period, and has not been revoked. This ensures the integrity and timeliness of the multi-dimensional trade capability attribute data in the extended fields, thereby effectively improving the accuracy of order matching.
[0161] The following describes a complete trade management process formed by the digital certificate generation method and order matching method provided in the various embodiments of the present invention, using a complete example scenario.
[0162] The digital certificate generation process includes: First, the certification system receives a certificate application request initiated by supplier A.
[0163] Then, the authentication system calls the REST-style application programming interface in the trade management system to retrieve the latest multi-dimensional trade capability attribute data of supplier A, returned in JSON format, from the trade management system. The specific content is as follows: Available product categories: Corrugated cardboard outer carton, category code 14111507; Corrugated cardboard inner carton, category code 14111508; Maximum production capacity: 10,000 units / month; Certification data: Quality Management System Certification, also known as ISO 9001 certification, issued by SGS, with an expiry date of June 1, 2027; Forest Stewardship Council (FSC) certification, issued by the Forest Stewardship Council, with an expiry date of December 31, 2025. Historical contract fulfillment rate: 95%; Available geographic area data: Area A1, administrative division code 310000; Area A2, administrative division code 320000; Area A3, administrative division code 330000; Credit rating: B; Latest review date: January 15, 2025; Additional notes: Customized printing is supported.
[0164] The authentication system then organizes the multi-dimensional trade capability attribute data according to the nested hierarchical structure of ASN.1 and encodes it into a target byte stream according to distinguishable encoding rules. In this example, the length of the encoded target byte stream can be on the order of 350 bytes. Each data unit is encoded in the order of label, length, and value: byte 30 is a sequence type label, byte 02 is an integer type label, byte 06 is an object identifier type label, byte 0C is an octet type label, byte 17 is a time type label, and byte 0A is an enumeration type label; the bytes after the label record the length occupied by the value content, and the bytes after the length record the value content itself.
[0165] For example, the specific structure of the target byte stream encoded in this instance is as follows: { 30 82 01 5A 02 01 01 30 1A 06 0A 2A 86 XX XX XX XX XX XX 01 01 06 0A 2A 86 XX XX XX XX XX XX 01 02 02 02 27 10 30 82 01 00 30 7F 06 0A 2A 86 XX XX XX XX XX XX 03 01 0C 03 53 47 53 17 0D 32 37 30 36 30 31 30 30 30 30 30 30 5A 30 7F 06 0A 2A 86 XX XX XX XX XX XX 03 02 0C 03 46 53 43 17 0D 32 35 31 32 33 31 30 30 30 30 30 30 5A 02 01 5F 30 12 0C 06 33 31 30 30 30 30 0C 06 33 32 30 30 30 30 0C 06 33 33 30 30 30 30 0A 01 02 17 0D 32 35 30 31 31 35 30 30 30 30 30 30 5A 0C 15 E6 94 AF E6 8C 81 E5 AE 9A }
[0166] "30 82 01 5A" is the root sequence of the target byte stream, representing the beginning of the entire multi-dimensional trade capability attribute data structure. Here, the hexadecimal "30" is the tag byte for the sequence type, indicating that this data unit is a sequence container; the hexadecimal "82 01 5A" is the length byte, where "82" indicates that the length marker occupies the following two bytes, and "015A" indicates the total length of the subsequent value content bytes.
[0167] The root sequence contains nested data units, each of which is nested within the following structure: The first data unit is the version field, with the encoded value "02 01 01". The first byte "02" is the tag byte of integer type; the second byte "01" is the length byte, indicating the bytes occupied by the value content; and the third byte "01" is the value content byte, indicating that the version number of the data structure is version 1.
[0168] The second data unit is the available product category field, with a code value of "30 1A". "30" indicates that this field is a sequence type container, and "1A" indicates the length of the container's value content. Within this sequence are two nested sub-data units of object identifier type, carrying the product category object identifiers corresponding to the corrugated outer carton and the corrugated inner carton, respectively. Each sub-data unit consists of a tag byte of the object identifier type, a length byte indicating the ten-byte value, and a value byte carrying the encoded values of each arc segment of the object identifier. The first arc segments of the two product category object identifiers are identical, with only the last arc segment values being 1 and 2 respectively to distinguish the two categories. For example, the code value for the product category object identifier corresponding to the corrugated outer carton is "06 0A 2A 86 XX XX XX XX XX XX XX 01 01", and the code value for the product category object identifier corresponding to the corrugated inner carton is "06 0A 2A 86 XX XX XX XX XX XX 0102".
[0169] The third data unit is the capacity limit field, with the encoded value "02 02 27 10". Here, "02" is the tag byte of integer type; the second byte "02" indicates that the value content occupies two bytes; the value content byte "27 10" is the hexadecimal representation of 10,000, indicating that the supplier's capacity limit is 10,000 pieces per month.
[0170] The fourth data unit is the qualification certification list field, with a code value of "30 82 01 00". It is a sequence type data unit occupying more than 256 bytes. Within this sequence, there are two nested qualification certification entry substructures of the same sequence type: one is a quality management system certification entry, with a code value of "30 7F". This entry contains, in sequence, the byte code corresponding to the qualification type object identifier, the issuing organization name characters, and the time code bytes indicating the expiration date; the other is a Forest Stewardship Council certification entry, with a code value of "30 7F". This entry also contains, in sequence, the byte code corresponding to the qualification type object identifier, the issuing organization name characters, and the time code bytes indicating the expiration date.
[0171] The fifth data unit is the historical fulfillment rate field, with the encoded value "02 01 5F". Here, "02" is the tag byte of integer type, "01" is the length byte, and the value content byte "5F" is the hexadecimal representation of 95, indicating that the supplier's historical fulfillment rate is 95%.
[0172] The sixth data unit is the geographic region field, with a code value of "30 12". Here, "30" indicates that the field is a sequence type container, and "12" indicates the length of the sequence. Within this sequence are three string type sub-data units, whose values are the byte codes corresponding to the administrative division numerical codes 310000, 320000, and 330000, respectively, indicating the three service areas A1, A2, and A3. Each sub-data unit consists of a string type label byte, a length byte indicating the six-byte value, and a value byte corresponding to the six-digit numerical code. The seventh data unit is the credit rating field, with the encoded value "0A 01 02". Here, "0A" is the tag byte of the enumeration type, "01" is the length byte, and the value byte "02" corresponds to the second level in the preset enumeration list, indicating that the supplier's credit rating is B.
[0173] The eighth data unit is the review time field, with the encoded value "17 0D 32 35 30 31 31 35 30 3030 30 30 30 5A". Here, "17" is the tag byte of the Coordinated Universal Time type, "0D" is the length of the value content, and the time information carried by the content byte is used to indicate that the latest review time is January 15, 2025. The ninth data unit is a special capability remarks field, with the encoded value "0C 15 E6 94 AF E6 8C 81E5 AE 9A". Here, "0C" is an octet of the tag byte type, "15" is the length of the value content, and the value content byte carries the Unicode conversion format (Universal Character Set Transformation Format-8 bit, UTF-8) byte encoding corresponding to the text "Support Fixed".
[0174] As can be seen from the above encoding structure, after the multi-dimensional trade capability attribute data is encoded by distinguishable encoding rules, each dimension of data is unambiguously carried in the target byte stream with a deterministic combination of labels, lengths and values. Any parser can restore the attribute data of each dimension from the target byte stream one by one according to the same encoding convention.
[0175] Subsequently, the authentication system writes the target byte stream as an octet into the extended value part of the extension item, and sets the extension type identifier of the extension item to the target object identifier, namely the trade capability extension sub-arc 1.2.156.XXXXX.1.
[0176] Subsequently, the authentication system uses the SM2 elliptic curve public key cryptography algorithm in conjunction with the SM3 cryptographic hash algorithm, and uses its private key information to sign the entire subject of the certificate to be signed, generating a signature value with a length of 64 to 72 bytes.
[0177] Subsequently, the certification system determined the expiration date of the digital certificate to be December 31, 2025, which is the earliest expiration date corresponding to the Forest Stewardship Council certification entry. At this point, Supplier A's digital certificate can be obtained.
[0178] As can be seen from the above, before issuance, the extended field area of the certificate to be signed is empty, or only contains standard extended items such as key usage and basic constraints; after issuance, an extended item is added to the extended field area. The extended type identifier of this extended item is target object identifier 1.2.156.XXXXX.1, and the extended value is the target byte stream of the aforementioned 350 bytes. Accordingly, the total size of the digital certificate increases from the 1000-byte level to the 1350-byte level, that is, the identity verification information part occupies 800-1200 bytes, the trade capability extension part occupies 200-500 bytes in typical scenarios, and the signature value occupies 64-72 bytes.
[0179] The order matching process includes: First, the procurement system extracts the demand information of the pending order initiated by the purchaser as follows: corrugated cardboard boxes corresponding to category code 14111507, a purchase quantity of 5,000 pieces, a delivery area corresponding to region A1 corresponding to administrative division code 310000, and a required qualification type of quality management system certification.
[0180] The procurement system then retrieves a list of candidate supplier digital certificates, and supplier A's digital certificate is on this list and includes trade capability extensions.
[0181] Subsequently, the procurement system verifies the identity and validity of the digital certificates of candidate suppliers, such as Supplier A's digital certificate. The system uses the public key information from the authentication system to verify the signature information of the digital certificate using the SM2 elliptic curve public key cryptography algorithm combined with the SM3 cryptographic hash algorithm. The signature verification is successful. A comparison confirms that the current time, June 17, 2025, is earlier than the expiration time, December 31, 2025, meaning the certificate has not expired. Furthermore, a query using the online certificate status protocol shows that the certificate serial number is not on the revocation list. With all three verifications passed, Supplier A is selected as the supplier to be matched.
[0182] Subsequently, the procurement system extracts the target byte stream from the extended value of the extended item in Supplier A's digital certificate and parses it according to the structured encoding pattern to obtain attribute data for each dimension: Available product category data is restored to category codes 14111507 and 14111508 through a reverse lookup of the structure mapping table using object identifiers; the capacity limit data is directly read from a four-byte integer as 10,000 units / month; qualification certification data is parsed into quality management system certification items and Forest Stewardship Council certification items, with the former expiring on June 1, 2027, and the latter on December 31, 2025; serviceable geographic area data is restored to codes 310000, 320000, and 330000 through string decoding; credit rating is read from a 1-byte enumeration value as Grade B. Historical fulfillment rate data is decoded to 95%.
[0183] Subsequently, the procurement system performed multi-dimensional matching: For category matching, order category code 14111507 falls within the available category data, and the match was successful; for capacity matching, the procurement quantity of 5,000 units is less than or equal to the capacity limit of 10,000 units, and the match was successful; for region matching, delivery region code 310000 falls within the serviceable geographical region data, and the match was successful; for qualification matching, the required quality management system certification has a corresponding qualification certification item, and its expiration date is June 1, 2027, which is later than the current time, June 17, 2025, and the match was successful. Since all dimensions met the matching rules, the procurement system output a successful matching result. This result records: supplier identifier is supplier A, matching status is complete match, matching details show that all four dimensions (category, capacity, region, and qualification) were successful, credit rating is B, historical fulfillment rate is 95%, and additional remarks indicate support for customized printing.
[0184] As can be seen from the above, the extended field is not modified during the verification phase; it is only parsed and read. The data carried by the extended field remains unchanged throughout the verification process, and its integrity is continuously protected by the signature value.
[0185] As can be seen from the above, the digital certificate generation method and order matching method provided by this invention address the data silos formed by the separate storage of identity information and capability attribute data in different databases. By embedding multi-dimensional trade capability attribute data into the extended fields of the digital certificate through structured encoding, the method achieves consistency between identity information and capability attribute data. Regarding the two independent steps of identity verification and capability query, the method merges the dual determinations into a single atomic operation using a single digital certificate carrier, reducing the overhead of secondary queries to the centralized database. Addressing the lack of unified semantics in the extended fields, the method uses an abstract syntax markup semantic model covering eight dimensions and a dedicated target object identifier, making the data carried by the extended fields parsable, scalable, and interoperable. Addressing the single-point performance bottleneck and availability risk of centralized matching, since capability attribute data is bound and distributed with the digital certificate, the procurement system can complete verification and matching offline using only the public key information of the authentication system, eliminating the single-point dependency on the centralized database. Regarding the lag in change response, the method uses a real-time revocation and update mechanism linked by the trade management system, authentication system, and procurement system, shortening the daily cycle of change response from relying on timed batch imports to a second-level perception based on the online certificate status protocol.
[0186] Figure 3 This is a schematic diagram of the supply chain management cluster provided by the present invention.
[0187] like Figure 3 As shown, the supply chain management cluster includes an authentication system 310, a trade management system 320, and a procurement system 330. The authentication system is used to execute the digital certificate generation method; for specific implementation steps, please refer to [link to implementation details]. Figure 1 The procurement system is used to execute order matching methods; see below for specific implementation steps. Figure 2 .
[0188] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention, such as... Figure 4As shown, the electronic device may include: a processor 410, a communications interface 420, a memory 430, and a communication bus 440, wherein the processor 410, communications interface 420, and memory 430 communicate with each other through the communication bus 440. The processor 410 can call logical instructions in the memory 430 to execute a digital certificate generation method. This method includes: in response to a certificate application request or certificate update request from a supplier, obtaining the latest multi-dimensional trade capability attribute data of the supplier from a trade management system; generating a certificate to be signed for the supplier based on the multi-dimensional trade capability attribute data; the certificate to be signed includes a basic information field and extended fields; the basic information field stores a certificate version number, certificate serial number, issuer information, validity period information, and the supplier's identity information and public key information; the extended fields store the multi-dimensional trade capability attribute data identified by a target object identifier and encoded according to a structured coding pattern, the target object identifier being used to identify the trade capability semantic type of the data carried by the extended fields; and performing a digital certificate generation method based on the private key information of the authentication system. The method involves: signing a certificate to obtain signature information; generating a digital certificate for the supplier based on the certificate to be signed and the signature information; or an order matching method, which includes: obtaining demand information for an order to be processed and a list of candidate supplier digital certificates; the list of candidate supplier digital certificates includes multiple candidate supplier digital certificates; verifying the identity validity of each candidate supplier's digital certificate, and obtaining the digital certificates of each supplier to be matched that have passed the identity validity verification from the list of candidate supplier digital certificates based on the verification results; parsing the multi-dimensional trade capability attribute data of each supplier to be matched based on the target object identifier in the extended field of each supplier's digital certificate; performing multi-dimensional matching between the demand information and the multi-dimensional trade capability attribute data of each supplier to be matched, and outputting the matching result.
[0189] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0190] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the digital certificate generation method provided by the above methods. The method includes: in response to a certificate application request or certificate update request from a supplier, obtaining the latest multi-dimensional trade capability attribute data of the supplier from a trade management system; generating a certificate to be signed for the supplier based on the multi-dimensional trade capability attribute data; the certificate to be signed includes a basic information field and an extended field; the basic information field stores a certificate version number, a certificate serial number, issuer information, validity period information, and the supplier's identity information and public key information; the extended field stores the multi-dimensional trade capability attribute data identified by a target object identifier and encoded according to a structured coding pattern, the target object identifier being used to identify the extended field. The method includes: a semantic type of trade capability carried by the data; signing the certificate to be signed based on the private key information of the authentication system to obtain signature information; generating the supplier's digital certificate based on the certificate to be signed and the signature information; or an order matching method, which includes: obtaining the demand information of the order to be processed and a list of candidate supplier digital certificates; the list of candidate supplier digital certificates includes multiple candidate supplier digital certificates; verifying the identity validity of each candidate supplier's digital certificate, and obtaining the digital certificates of each supplier to be matched that have passed the identity validity verification based on the verification results of each candidate supplier's digital certificate; parsing the multi-dimensional trade capability attribute data of each supplier to be matched based on the target object identifier in the extended field of each supplier's digital certificate; performing multi-dimensional matching between the demand information and the multi-dimensional trade capability attribute data of each supplier to be matched, and outputting the matching result.
[0191] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a digital certificate generation method provided by the methods described above. This method includes: in response to a certificate application request or certificate update request from a supplier, obtaining the latest multi-dimensional trade capability attribute data of the supplier from a trade management system; generating a certificate to be signed by the supplier based on the multi-dimensional trade capability attribute data; the certificate to be signed includes a basic information field and extended fields; the basic information field stores a certificate version number, a certificate serial number, issuer information, validity period information, and the supplier's identity information and public key information; the extended fields store the multi-dimensional trade capability attribute data encoded in a structured coding pattern and identified by a target object identifier, the target object identifier being used to identify the trade capability semantic type of the data carried by the extended fields; based on... The authentication system uses its private key information to sign the certificate to be signed, obtaining signature information; it then generates the supplier's digital certificate based on the certificate to be signed and the signature information; or, an order matching method, which includes: obtaining the demand information of the order to be processed and a list of candidate supplier digital certificates; the list of candidate supplier digital certificates includes multiple candidate supplier digital certificates; verifying the identity validity of each candidate supplier's digital certificate, and based on the verification results of each candidate supplier's digital certificate, obtaining the digital certificates of each supplier to be matched that have passed the identity validity verification from the list of candidate supplier digital certificates; parsing the multi-dimensional trade capability attribute data of each supplier to be matched based on the target object identifier in the extended field of each supplier's digital certificate; performing multi-dimensional matching between the demand information and the multi-dimensional trade capability attribute data of each supplier to be matched, and outputting the matching result.
[0192] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0193] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0194] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for generating a digital certificate, characterized in that, Applied to an authentication system, the method includes: In response to a supplier's certificate application or certificate renewal request, the latest multi-dimensional trade capability attribute data of the supplier is obtained from the trade management system; Based on the multi-dimensional trade capability attribute data, a certificate to be signed for the supplier is generated; the certificate to be signed includes a basic information field and an extended field; the basic information field stores the certificate version number, certificate serial number, issuer information, validity period information, as well as the supplier's identity information and public key information; the extended field stores the multi-dimensional trade capability attribute data identified by a target object identifier and encoded in a structured coding pattern, and the target object identifier is used to identify the trade capability semantic type of the data carried by the extended field; The certificate to be signed is signed based on the private key information of the authentication system to obtain signature information; The supplier's digital certificate is generated based on the certificate to be signed and the signature information.
2. The digital certificate generation method according to claim 1, characterized in that, The multi-dimensional trade capability attribute data includes various data such as available product categories, production capacity limits, qualification certification data, historical fulfillment rate data, serviceable geographic areas, credit rating, latest review time data, and additional remarks. The qualification certification data includes at least one qualification certification entry, and each qualification certification entry includes a qualification type identifier, an issuing authority, and a qualification expiration date.
3. The digital certificate generation method according to claim 2, characterized in that, The validity period information includes the effective date and the expiration date; The steps for determining the failure time include: Among the qualification expiration times of each qualification certification entry in the qualification certification data, the earliest expiration time is determined, and the expiration time is determined to be earlier than or equal to the earliest expiration time.
4. The digital certificate generation method according to any one of claims 1-3, characterized in that, The multi-dimensional trade capability attribute data is written into the extended field through the following steps: The multi-dimensional trade capability attribute data is organized according to a nested hierarchical structure; the nested hierarchical structure includes a root sequence, sub-sequences, and basic types; According to the structured encoding pattern, the organized multi-dimensional trade capability attribute data is encoded into at least one target byte stream; When there are multiple extended fields, each target byte stream is written into the extended field corresponding to each target byte stream according to the target object identifier corresponding to each target byte stream.
5. The digital certificate generation method according to claim 4, characterized in that, The step of encoding the organized multi-dimensional trade capability attribute data into at least one target byte stream according to the structured encoding pattern includes: The multi-dimensional trade capability attribute data after organization is encoded into an initial byte stream according to the encoding format of data serialization encoding; Based on the data characteristics of the trade capability attribute data of each dimension and the resource information occupied by the initial byte stream, the initial byte stream is optimized and encoded to obtain at least one target byte stream; The optimized encoding includes at least one of unique encoding, compressed encoding, and split encoding; the compressed encoding includes prefix arc sharing encoding and / or number mapping encoding.
6. The digital certificate generation method according to claim 4, characterized in that, Before writing each of the target byte streams into the extended field corresponding to each of the target byte streams according to the target object identifier corresponding to each of the target byte streams, the method further includes: Each field in the target byte stream is divided into public fields, restricted fields, or sensitive fields; Keep the public fields in each of the target byte streams in plaintext; The symmetric key of the authentication system is used to encrypt the restricted fields in each of the target byte streams; Sensitive fields in each of the target byte streams are encrypted using the public key information of the supplier's demand side.
7. The digital certificate generation method according to any one of claims 1-3, characterized in that, The certificate update request is triggered when a positive change event is pushed by the trade management system. The positive change event is used to indicate that the content of the supplier's multi-dimensional trade capability attribute data has changed. The process of obtaining the latest multi-dimensional trade capability attribute data of the supplier from the trade management system includes: In response to the certificate update request, verify the authenticity of the positive change event with the trade management system; If the positive change event passes the authenticity verification, the latest multi-dimensional trade capability attribute data of the supplier is obtained from the trade management system; all qualification certification entries in the latest multi-dimensional trade capability attribute data are in an unexpired state.
8. The digital certificate generation method according to any one of claims 1-3, characterized in that, The method further includes: Upon receiving a negative change event pushed by the trade management system, the system verifies the authenticity of the negative change event; the negative change event is used to indicate that some of the supplier's qualification certification items have expired or its credit rating has been reduced. If the negative change event passes the authenticity verification, the supplier's current digital certificate is added to the revocation list, and the extended fields of the supplier's current digital certificate are updated according to the event type of the negative change event. Based on the updated extended fields, a new digital certificate for the supplier is generated. The system publishes the current revocation status of the vendor's digital certificate and pushes the new digital certificate to subscribers who have subscribed to the vendor's certificate change notifications.
9. The digital certificate generation method according to any one of claims 1-3, characterized in that, The extended field also includes tag information and version information; the tag information is used to identify that the content information of the extended field is non-critical extended information; the version information is used to identify the data structure version of the extended field.
10. An order matching method, characterized in that, Applied to a procurement system, the method includes: Obtain the demand information for pending orders and a list of candidate supplier digital certificates; the list of candidate supplier digital certificates includes digital certificates from multiple candidate suppliers. The identity validity of the digital certificates of each candidate supplier is verified, and based on the verification results of the digital certificates of each candidate supplier, the digital certificates of each supplier to be matched that have passed the identity validity verification are obtained from the list of candidate supplier digital certificates. Based on the target object identifier in the extended field of the digital certificate of each of the suppliers to be matched, the multi-dimensional trade capability attribute data of each supplier to be matched is parsed. The demand information is matched with the multi-dimensional trade capability attribute data of each of the suppliers to be matched, and the matching results are output. The digital certificate of each of the candidate suppliers is generated based on the digital certificate generation method as described in any one of claims 1-9.
11. The order matching method according to claim 10, characterized in that, The verification of the identity validity of the digital certificates of each of the candidate suppliers includes: For each candidate vendor's digital certificate, the signature information of the digital certificate is verified using the public key information of the authentication system to obtain a first verification result; Based on the validity period information in the basic information field of the digital certificate, verify whether the digital certificate has expired to obtain a second verification result; Based on the certificate serial number in the basic information field of the digital certificate, verify whether the digital certificate has been revoked to obtain a third verification result; If the first verification result indicates that the digital certificate has passed the signature verification, the second verification result indicates that the digital certificate has not expired, and the third verification result indicates that the digital certificate has not been revoked, then the digital certificate is determined to have passed the identity validity verification. The digital certificates of each candidate vendor are iterated through to obtain the verification results of each candidate vendor's digital certificate.
12. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the digital certificate generation method as described in any one of claims 1-9, or the order matching method as described in any one of claims 10-11.
13. A non-transitory 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 digital certificate generation method as described in any one of claims 1-9, or the order matching method as described in any one of claims 10-11.
