CN113722745A

CN113722745A - eCTD universal technology document submission management method and system

Info

Publication number: CN113722745A
Application number: CN202111178598.XA
Authority: CN
Inventors: 顾伟伟; 张晓东; 王建英
Original assignee: Suzhou Kerite Information Technology Co ltd
Current assignee: Suzhou Kerite Information Technology Co ltd
Priority date: 2021-07-13
Filing date: 2021-10-10
Publication date: 2021-11-30
Anticipated expiration: 2041-10-10
Also published as: CN113722745B; CN113486373A

Abstract

The design scheme of the disclosure provides an eCTD general technical document submission management method and a system, by analyzing the collaborative relationship attribute of the to-be-encrypted submission path information and the encrypted submission path information in the submitted general technical document list, and the business cooperative relationship information between the two is considered, the target cooperative relationship attribute information can be obtained, the determination of the encryption compensation task corresponding to the candidate encryption type submission path information is realized, so as to determine the target cooperative relationship attribute information aiming at the encryption compensation task, can determine the encryption task of the entity to be encrypted in the submitted technical document list and the task configuration information corresponding to the encryption task of the entity to be encrypted, when the entity to be encrypted is indicated to be encrypted based on the task configuration information, the service cooperation information of the encryption entity is considered, and the encryption interference condition of the encryption entity when the entity to be encrypted is avoided.

Description

eCTD universal technology document submission management method and system

Technical Field

The disclosure relates to the technical field of eCTD, in particular to an eCTD general technology document submission management method and system.

Background

The eCTD (Electronic Common Technical Document) as an internationally recognized file writing format can be used for making a registration application file with a perfect structure submitted to a drug registry, and is a unified registration application file format determined by the ICH for unifying the format and the content of the drug used by people in application registration.

In the delivery management process of the eCTD file, in consideration of the fact that some key content structure data need to be specially encrypted, a lot of encrypted delivery path information is generated, and in the related art, the inventor researches and discovers that the encryption interference condition of a lot of encryption entities exists when the entity to be encrypted of the eCTD file is encrypted, so how to avoid the encryption interference condition of the encryption entity when the entity to be encrypted is a technical problem to be solved urgently in the field.

Disclosure of Invention

In order to overcome at least the above disadvantages in the prior art, the present disclosure aims to provide an eCTD universal technology document submission management method and system, where the objective collaborative relationship attribute information can be obtained by performing collaborative relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted universal technology document list and considering the business collaborative relationship information therebetween, so as to determine an encryption compensation task corresponding to the candidate encrypted submission path information, and further achieve collaborative relationship attribute analysis to determine the objective collaborative relationship attribute information for the encryption compensation task. The encryption task of the entity to be encrypted in the submitted technical document list and the task configuration information corresponding to the encryption task of the entity to be encrypted can be determined, and when the entity to be encrypted is indicated to be encrypted and executed based on the task configuration information, the service cooperation information of the encryption entity can be taken into account, so that the encryption interference condition of the encryption entity when the entity to be encrypted is avoided.

In a first aspect, the present disclosure provides an eCTD universal technology document submission management method, which is applied to an eCTD cloud service platform in communication with a document submission service terminal, where the method includes:

acquiring to-be-encrypted submission path information and encrypted submission path information in a submitted general technical document list;

performing collaborative relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted general technology document list based on the business collaborative relationship information of the business collaborative information between the to-be-encrypted submission path information and the encrypted submission path information in the submitted general technology document list to obtain target collaborative relationship attribute information;

determining encryption type submission path information with cooperative encryption nodes in the cooperative relationship attribute analysis process as candidate encryption type submission path information, and determining an encryption compensation task corresponding to the candidate encryption type submission path information according to cooperative adaptation degree information of an encryption type submission path stream between the encryption type submission path information in the target cooperative relationship attribute information and the candidate encryption type submission path information;

performing cooperative relationship attribute analysis on the encryption compensation task corresponding to the candidate encryption type submission path information and the candidate encryption type submission path information to obtain target cooperative relationship attribute information aiming at the encryption compensation task;

and determining an entity encryption task to be encrypted in the submitted general technical document list and task configuration information corresponding to the entity encryption task to be encrypted according to the target cooperative relationship attribute information and the target cooperative relationship attribute information aiming at the encryption compensation task.

In a possible example of the first aspect, the obtaining of the to-be-encrypted delivery path information and the encrypted delivery path information in the delivered technical document list includes:

acquiring at least two groups of entity record information to be encrypted and at least two groups of encrypted entity record information in the submitted universal technical document list;

acquiring submitted encrypted routing information of the entity record information to be encrypted and encrypted sharing information of the entity record information to be encrypted between the at least two groups of entity record information to be encrypted, and acquiring submitted encrypted routing information of the encrypted entity record information and encrypted sharing information of the encrypted entity record information between the at least two groups of entity record information to be encrypted;

fusing the at least two groups of entity record information to be encrypted according to the submitting encryption route information of the entity record information to be encrypted and the encryption sharing information of the entity record information to be encrypted to obtain the submitting path information to be encrypted in the submitted general technical document list; the group of to-be-encrypted submission path information comprises at least one group of to-be-encrypted entity record information;

fusing the at least two groups of encrypted entity record information according to the submission encrypted routing information of the encrypted entity record information and the encrypted sharing information of the encrypted entity record information to obtain encrypted submission path information in the submitted general technical document list; the set of encryption class delivery path information includes at least one set of encryption entity record information.

In a possible example of the first aspect, the performing, based on the service coordination relationship information of the service coordination information between the to-be-encrypted submission path information and the encrypted submission path information in the submitted technical document list, coordination relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted technical document list to obtain target coordination relationship attribute information includes:

determining the encryption type submission path information in the submitted general technical document list as encryption type submission path information aiming at collaborative relationship attribute analysis, and determining the to-be-encrypted type submission path information in the submitted general technical document list as to-be-encrypted type submission path information aiming at collaborative relationship attribute analysis; the record information of the encryption entity in the encryption type submission path information aiming at the collaborative relationship attribute analysis is determined from the record information corresponding to the document submission service of the submitted general technical document list;

acquiring entity record information to be encrypted in record information corresponding to the document submission service; determining delivery encryption routing information of the recording information between the entity recording information to be encrypted in the recording information corresponding to the document delivery service and the entity recording information to be encrypted in the class delivery path information to be encrypted analyzed for the collaborative relationship attribute as business collaborative relationship information of the business collaborative relationship information between the encryption class delivery path information to be analyzed for the collaborative relationship attribute and the class delivery path information to be encrypted analyzed for the collaborative relationship attribute;

and when the business cooperation relation index of the business cooperation relation information of the business cooperation information is greater than or equal to a business cooperation relation index threshold, performing cooperation relation attribute analysis on the encrypted submission path information aiming at the cooperation relation attribute analysis and the to-be-encrypted submission path information aiming at the cooperation relation attribute analysis to obtain the target cooperation relation attribute information.

In a possible example of the first aspect, the candidate encryption class submission path information includes encryption entity record information of a collaborative stop in the submitted technical document list; the number of the target cooperative relationship attribute information is at least two; the encryption type submission path information in each target collaborative relationship attribute information respectively comprises encryption entity record information of uncoordinated stay in the submitted general technical document list; the determining, according to the cooperative adaptation degree information of the encrypted cooperative information stream between the encryption-based delivery path information in the target cooperative relationship attribute information and the candidate encryption-based delivery path information, an encryption compensation task corresponding to the candidate encryption-based delivery path information includes:

acquiring a first document object collaborative stay tag of the candidate encryption type submission path information according to the encryption entity record information of the collaborative stay;

respectively acquiring a second document object collaborative stay tag of the encrypted type submission path information in each target collaborative relationship attribute information according to the encrypted entity record information which is not collaboratively stayed and is included in each target collaborative relationship attribute information;

acquiring label adaptation degrees between the first document object collaborative stopping label and a second document object collaborative stopping label corresponding to each target collaborative relationship attribute information respectively;

determining cooperative adaptation degree information of an encrypted cooperative information stream between the encrypted type submission path information in each target cooperative relationship attribute information and the candidate encrypted type submission path information respectively according to the label adaptation degree corresponding to each target cooperative relationship attribute information;

when the number of the target cooperative relationship attribute information is larger than the first target number and smaller than or equal to the second target number, determining an encryption compensation task corresponding to the to-be-encrypted submission path information in the target cooperative relationship attribute information as an encryption compensation task corresponding to the candidate encryption submission path information; the target cooperative relationship attribute information refers to target cooperative relationship attribute information in which a correlation coefficient of cooperative adaptation degree information of a corresponding encrypted cooperative information stream is greater than or equal to a correlation coefficient threshold of the encrypted cooperative information stream;

the number of submitting encryption route types of the encryption entity record information of the cooperative stay is at least two; the acquiring a first document object collaborative stop tag of the candidate encryption class submission path information according to the encryption entity record information of the collaborative stop includes:

acquiring a recording information cooperative encryption node corresponding to each piece of encryption entity recording information of at least two pieces of encryption entity recording information of cooperative stay respectively;

acquiring a first associated collaborative encryption node corresponding to the encrypted entity record information of at least two collaborative dwells according to the record information collaborative encryption node corresponding to the encrypted entity record information of each collaborative dwelling; determining the first associated collaborative encryption node as the first document object collaborative stay tag;

the at least two pieces of target cooperative relationship attribute information comprise Xth target cooperative relationship attribute information, wherein X is a positive integer less than or equal to the total number of the at least two pieces of target cooperative relationship attribute information; the Xth target cooperative relationship attribute information comprises at least two submitting encryption route types of encryption entity record information which is not cooperatively stayed; the obtaining, according to the encryption entity record information that is not co-located and included in each target co-relationship attribute information, a second document object co-located tag of the encryption type delivery path information in each target co-relationship attribute information, respectively, includes:

acquiring a record information cooperative encryption node corresponding to each piece of uncoordinated staying encryption entity record information in at least two pieces of uncoordinated staying encryption entity record information included in the Xth target cooperative relationship attribute information;

acquiring at least two second associated cooperative encryption nodes corresponding to the recording information of the encryption entity which does not stop in cooperation according to the recording information cooperative encryption node corresponding to the recording information of the encryption entity which does not stop in cooperation;

and determining the second associated collaborative encryption node as a second document object collaborative stop tag of the encryption type submission path information in the Xth target collaborative relationship attribute information.

In a possible example of the first aspect, the number of candidate encryption class delivery path information is at least two; the method further comprises the following steps:

when the number of the target collaborative relationship attribute information is less than or equal to the first target number, respectively determining the target collaborative relationship attribute information where the encrypted collaborative relationship submission path information with the largest correlation coefficient corresponding to the collaborative adaptation degree information of the encrypted collaborative information stream between each candidate encrypted submission path information is located as a candidate collaborative relationship attribute information combination corresponding to each candidate encrypted submission path information;

respectively determining the encryption compensation tasks corresponding to the to-be-encrypted submission path information in the candidate collaborative relationship attribute information combination corresponding to each candidate encryption submission path information as the candidate encryption compensation tasks corresponding to each candidate encryption submission path information;

determining the total number of encryption certificates of at least two encryption tasks corresponding to the encryption task to be determined according to the candidate encryption compensation task corresponding to each candidate encryption type submission path information;

acquiring first record information of the number of total encryption certificates of at least two encryption tasks in an encryption compensation task corresponding to-be-encrypted submission path information of at least two target cooperative relationship attribute information;

determining the total number of encryption certificates of each candidate encryption class submission path information aiming at the first target encryption task of the encryption task to be determined according to the first record information;

determining the encryption task to be determined, which respectively has the total encryption certificate quantity of the first target encryption task corresponding to each candidate encryption class submission path information, as an encryption compensation task corresponding to each candidate encryption class submission path information; and the second record information of the total number of the encryption certificates of at least two encryption tasks in the encryption compensation task corresponding to each candidate encryption class submission path information is matched with the first record information.

In one possible example of the first aspect, the method further comprises:

when the number of the target collaborative relationship attribute information is larger than the second target number, counting encryption task matching information of the total number of encryption certificates of at least two encryption tasks of the encryption task to be determined in the encryption compensation task corresponding to the entity record information to be encrypted of the target collaborative relationship attribute information; the total number of the encryption certificates of the at least two encryption tasks is determined according to the encryption compensation task corresponding to the to-be-encrypted submission path information in the target cooperative relationship attribute information;

determining the total encryption certificate quantity of the candidate encryption class submission path information for a second target encryption task of the encryption task to be determined from the total encryption certificate quantity of at least two encryption tasks according to the cooperative adaptation degree information of the encryption cooperative information stream between the candidate encryption class submission path information and the target cooperative relationship attribute information and the encryption task matching information;

and determining the encryption task to be determined with the total number of the encryption certificates of the second target encryption task as an encryption compensation task corresponding to the candidate encryption class submission path information.

In one possible example of the first aspect, the method further comprises:

determining an encryption compensation task corresponding to the to-be-encrypted submission path information in the target cooperative relationship attribute information as an encryption compensation task corresponding to the target cooperative relationship attribute information; determining the target collaborative relationship attribute information and the target collaborative relationship attribute information aiming at the encryption compensation task as a collaborative relationship attribute information combination in the submitted technical document list; combining the collaborative relationship attribute information with the corresponding encryption compensation task to determine the collaborative relationship attribute information as a target encryption compensation task; adding the same encryption entity service distribution label for the encryption class submission path information in the target encryption compensation task and the cooperative relationship attribute information combination; respectively mapping the target encryption compensation tasks with the encryption entity service distribution labels to target models;

the updating times of strategy iterative updating of the target encryption compensation task through the decision tree network-based model are greater than the updating times of strategy iterative updating of the target encryption compensation task through the random forest tree network model; the updating times of strategy iterative updating of the target encryption compensation task through the random forest tree network model are greater than the updating times of strategy iterative updating of the target encryption compensation task through the support vector machine model;

and the number of the first and second electrodes,

the loss parameter of the decision tree network-based model for the target encryption compensation task is smaller than the loss parameter of the random forest tree network model for the target encryption compensation task; the loss parameter of the random forest tree network model for the target encryption compensation task is smaller than the loss parameter of the support vector machine model for the target encryption compensation task;

the determining, according to the target coordination relationship attribute information and the target coordination relationship attribute information for the encryption compensation task, an entity-to-be-encrypted encryption task in the submitted technical document list and task configuration information corresponding to the entity-to-be-encrypted encryption task includes:

determining the encryption task of the entity to be encrypted in the submitted universal technical document list according to the encryption type submission path information in the collaborative relationship attribute information combination;

and acquiring the target encryption compensation task with the encryption entity service distribution label from a target model according to the encryption entity service distribution label of the encryption type submission path information in the cooperative relationship attribute information combination, and determining the acquired target encryption compensation task as task configuration information corresponding to the entity encryption task to be encrypted.

In a second aspect, an embodiment of the present disclosure further provides an eCTD universal technology document delivery management system, where the eCTD universal technology document delivery management system includes a document delivery service terminal and an eCTD cloud service platform in communication with the document delivery service terminal, and the system includes:

the eCTD cloud service platform is used for:

In a third aspect, an embodiment of the present disclosure further provides an eCTD cloud service platform, where the eCTD cloud service platform includes a processor, a machine-readable storage medium, and a network interface, where the machine-readable storage medium, the network interface, and the processor are connected through a bus system, the network interface is used for being communicatively connected with at least one document delivery service terminal, the machine-readable storage medium is used for storing a program, an instruction, or a code, and the processor is used for executing the program, the instruction, or the code in the machine-readable storage medium to perform the first aspect or the eCTD universal technology document delivery management method in any possible implementation manner of the first aspect.

In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, where instructions are stored, and when executed, cause a computer to perform the method for managing delivery of an eCTD universal technology document in the first aspect or any one of the possible implementation manners of the first aspect.

Based on any one of the above aspects, in the embodiment of the disclosure, by performing collaborative relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted general-purpose technical document list, and the business cooperative relationship information among the business cooperative relationship information is considered, the target cooperative relationship attribute information can be obtained, the determination of the encryption compensation task corresponding to the candidate encryption type submission path information is realized, the cooperative relationship attribute analysis is realized to determine the target cooperative relationship attribute information aiming at the encryption compensation task, the encryption task of the entity to be encrypted in the submitted general technical document list and the task configuration information corresponding to the encryption task of the entity to be encrypted can be determined, when the entity to be encrypted is indicated to be encrypted based on the task configuration information, the service cooperation information of the encryption entity is considered, and the encryption interference condition of the encryption entity when the entity to be encrypted is avoided.

Drawings

To more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present disclosure and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings may be obtained from the drawings without inventive effort.

Fig. 1 is a schematic application scenario diagram of an eCTD universal technology document submission management system according to an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of an eCTD universal technology document submission management method provided in the embodiment of the present disclosure;

fig. 3 is a functional module schematic diagram of an eCTD universal technology document submission management apparatus according to an embodiment of the disclosure;

fig. 4 is a schematic structural block diagram of an eCTD cloud service platform for implementing the above-described eCTD general technical document submission management method according to the embodiment of the present disclosure.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only examples or embodiments of the present description, and that for a person skilled in the art, the present description can also be applied to other similar scenarios on the basis of these drawings without inventive effort. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.

Flow charts are used in this description to illustrate operations performed by a system according to embodiments of the present description. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, the various steps may be processed in reverse order or simultaneously. Meanwhile, other operations may be added to the processes, or a certain step or several steps of operations may be removed from the processes.

Fig. 1 is an interaction diagram of an eCTD universal technology document submission management system 10 according to an embodiment of the present disclosure. The eCTD general-technology document delivery management system 10 may include an eCTD cloud service platform 100 and a document delivery service terminal 200 communicatively connected to the eCTD cloud service platform 100. The eCTD general technology document delivery management system 10 shown in FIG. 1 is only one possible example, and in other possible embodiments, the eCTD general technology document delivery management system 10 may include only one of the components shown in FIG. 1 or may also include other components.

In this embodiment, the eCTD cloud service platform 100 and the document delivery service terminal 200 in the eCTD general technical document delivery management system 10 may cooperatively execute the eCTD general technical document delivery management method described in the following method embodiment, and the specific steps of the eCTD cloud service platform 100 and the document delivery service terminal 200 may refer to the detailed description of the following method embodiment.

In order to solve the technical problem in the foregoing background art, fig. 2 is a schematic flowchart of an eCTD general technical document submission management method provided in the embodiment of the present disclosure, and the eCTD general technical document submission management method provided in this embodiment may be executed by the eCTD cloud service platform 100 shown in fig. 1, and the eCTD general technical document submission management method is described in detail below.

Step S110, obtaining the submission path information to be encrypted and the submission path information of the encryption in the submitted general technical document list.

For example, the submitted common technical document list may be a corresponding common technical document list under a certain eCTD task in an encryption process. The to-be-encrypted delivery path information may be understood as service cooperation information in a corresponding delivery path process to be encrypted, and the encrypted delivery path information may be understood as service cooperation information in a corresponding delivery path process that has been encrypted. Further, the business cooperation information may include a cooperation task, a cooperation object, a cooperation time, and the like.

Step S120, performing coordination relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted general-purpose technical document list based on the service coordination relationship information of the service coordination information between the to-be-encrypted submission path information and the encrypted submission path information in the submitted general-purpose technical document list, so as to obtain target coordination relationship attribute information.

For example, the service cooperation relationship information may be understood as a service cooperation logic between different delivery path information during service authorized access, and such service cooperation logic may be a service cooperation logic in a data area or a time sequence, for example, a cooperation is generated between each other. The business cooperation relationship information is related to the cooperation relationship attribute information of the business function, so that when the cooperation relationship attribute analysis is carried out, the business cooperation relationship information is taken into account, the state difference of the entity to be encrypted and the encryption entity in the working use process can be distinguished, and the global cooperation relationship attribute analysis is realized.

Step S130, determining the encryption-based delivery path information having the collaborative encryption node in the collaborative relationship attribute analysis process as candidate encryption-based delivery path information, and determining an encryption compensation task corresponding to the candidate encryption-based delivery path information according to the collaborative adaptation degree information of the encryption-based collaboration information stream between the encryption-based delivery path information in the target collaborative relationship attribute information and the candidate encryption-based delivery path information.

For example, the collaborative encryption node may be obtained by analyzing and processing in advance according to a historical business collaborative logic record, and the collaborative encryption node is used for representing that the encryption-type delivery path information may generate a business collaborative logic influence on the delivered technical document list, and indirectly or directly result in the business collaborative logic of the delivered technical document list. The encrypted cooperative information flow may be understood as a data flow corresponding to a service template when different delivery path information is in working use. The cooperative adaptation degree information may be used to characterize the degree of adaptation between different encrypted cooperative information streams. The encryption compensation task corresponding to the candidate encryption class delivery path information may be used to instruct the corresponding encryption entity to perform the adjustment of the encryption path. The encryption compensation task may include an encryption compensation update indication for the encryption entity.

Step S140, performing cooperative relationship attribute analysis on the encryption compensation task corresponding to the candidate encryption type delivery path information and the candidate encryption type delivery path information to obtain target cooperative relationship attribute information for the encryption compensation task.

For example, the target cooperative relationship attribute information can take the randomness of the non-interactive object in the working and using process into account, for example, the encryption entity does not adjust the working and using line according to the corresponding encryption compensation task and randomly disturbs the line, if the encryption entity is encrypted and monitored in real time, the encryption cost is greatly increased, so that the encryption execution of the entity to be encrypted can be indicated in reverse by determining the target cooperative relationship attribute information, and the encryption execution efficiency is improved as much as possible.

Step S150, determining an encryption task of an entity to be encrypted in the submitted technical document list and task configuration information corresponding to the encryption task of the entity to be encrypted according to the target coordination relationship attribute information and the target coordination relationship attribute information for the encryption compensation task.

For example, the task configuration information corresponding to the encryption task of the entity to be encrypted may include an encryption adjustment indication for a plurality of work use procedures of the entity to be encrypted. It can be understood that the difficulty of executing encryption on the entity to be encrypted is lower than that of executing encryption on the entity to be encrypted, so that the difficulty and uncertainty of encryption can be reduced by executing encryption on the entity to be encrypted, and the encryption interference condition of the entity to be encrypted when the entity to be encrypted is encrypted can be avoided by taking the business cooperation information of the entity to be encrypted into account.

In summary, based on steps S110 to S150, by performing coordination relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted technical document list and considering the service coordination relationship information therebetween, target coordination relationship attribute information can be obtained, so that the determination of the encryption compensation task corresponding to the candidate encrypted submission path information can be achieved, and further, coordination relationship attribute analysis is achieved to determine the target coordination relationship attribute information for the encryption compensation task. Therefore, the encryption task of the entity to be encrypted in the submitted technical document list and the task configuration information corresponding to the encryption task of the entity to be encrypted can be determined. Therefore, when the entity to be encrypted is indicated to be encrypted based on the task configuration information, the service cooperation information of the encryption entity can be taken into account, and the encryption interference condition of the encryption entity when the entity to be encrypted is avoided.

In the following, some alternative embodiments will be described, which should be understood as examples and not as technical features essential for implementing the present solution.

For some possible embodiments, the obtaining of the to-be-encrypted class submission path information and the encryption class submission path information in the submitted technical document list described in step S110 may include the following steps S111 to S114.

Step S111, obtaining at least two sets of record information of the entity to be encrypted and at least two sets of record information of the encrypted entity in the submitted technical document list.

Step S112, obtaining the delivery encryption routing information of the record information of the entity to be encrypted and the encryption sharing information of the record information of the entity to be encrypted between the at least two sets of record information of the entity to be encrypted, and obtaining the delivery encryption routing information of the record information of the entity to be encrypted and the encryption sharing information of the record information of the entity to be encrypted between the at least two sets of record information of the entity to be encrypted. For example, the submitted encrypted routing information may be calculated according to the service trajectory curve of the corresponding submitted path information on the routing task at different time intervals. The encrypted shared information may be understood as shared state data corresponding to the entity to be encrypted used by the opposite work during interaction, for example, collaborative relationship attribute data generated based on an authorization prompt that may be performed during interaction.

Step S113, according to the submitted encrypted routing information of the entity record information to be encrypted and the encrypted sharing information of the entity record information to be encrypted, fusing the at least two groups of entity record information to be encrypted to obtain the submitted path information to be encrypted in the submitted general technical document list; the group of delivery path information to be encrypted comprises at least one group of entity record information to be encrypted. For example, the recorded information fusion may splice or fuse the service flow curves to obtain corresponding service coordination information.

Step S114, according to the submitted encrypted routing information of the encrypted entity record information and the encrypted sharing information of the encrypted entity record information, fusing the at least two groups of encrypted entity record information to obtain encrypted submitted path information in the submitted general technical document list; the set of encryption class delivery path information includes at least one set of encryption entity record information.

In this way, by implementing the contents described in the above steps S111 to S114, the delivery encryption route information and the encryption sharing information can be taken into account, so as to ensure that the delivery path information of the to-be-encrypted type and the encryption type delivery path information can completely reflect the actual encryption status of the delivered technical document list.

In some embodiments, the service collaboration relationship information described in step S120 based on the service collaboration information between the to-be-encrypted delivery path information and the encrypted delivery path information in the delivered technical document list is used to perform collaboration relationship attribute analysis on the to-be-encrypted delivery path information and the encrypted delivery path information in the delivered technical document list to obtain target collaboration relationship attribute information, which may include the contents described in the following steps S1201 to S1203.

Step S1201, determining the encryption type submission path information in the submitted general technical document list as encryption type submission path information aiming at collaborative relationship attribute analysis, and determining the to-be-encrypted type submission path information in the submitted general technical document list as the to-be-encrypted type submission path information aiming at collaborative relationship attribute analysis; and the record information of the encryption entity in the encryption type submission path information aiming at the analysis of the collaborative relationship attribute is determined from the record information corresponding to the document submission business service aiming at the submitted general technical document list. For example, the document delivery service may be a data stream acquired by a corresponding acquisition script, and the record information may be obtained by performing AI analysis based on the document delivery service, and since the relevant technology of AI analysis is a conventional technical means, details are not described herein.

Step S1202, acquiring entity record information to be encrypted in record information corresponding to the document delivery service; and determining delivery encryption routing information of the recording information between the entity recording information to be encrypted in the recording information corresponding to the document delivery service and the entity recording information to be encrypted in the class delivery path information to be encrypted analyzed for the collaborative relationship attribute as business collaborative relationship information of the business collaborative relationship information between the encryption class delivery path information to be analyzed for the collaborative relationship attribute and the class delivery path information to be encrypted analyzed for the collaborative relationship attribute.

Step S1203, when the business cooperation relationship index of the business cooperation relationship information of the business cooperation information is greater than or equal to the business cooperation relationship index threshold, performing a cooperation relationship attribute analysis on the encrypted submission path information for the cooperation relationship attribute analysis and the to-be-encrypted submission path information for the cooperation relationship attribute analysis to obtain the target cooperation relationship attribute information. For example, the service cooperation relation index is used to represent the service cooperation logic degree between the entity to be encrypted and the encryption entity, and the larger the service cooperation relation index is, the larger the service cooperation logic degree between the entity to be encrypted and the encryption entity is. The service collaboration index threshold may be adjusted according to actual conditions, and is not limited herein.

Thus, when the contents described in the above steps S1201 to S1203 are applied, the determination of the business cooperation information for the analysis of the cooperation relationship attribute may be implemented based on the document delivery business service, so that the business cooperation relationship information between the business cooperation information of different delivery path information is accurately determined by delivering the encrypted routing information, and the cooperation relationship attribute analysis is accurately implemented in real time by combining the business cooperation relationship index, thereby ensuring that the target cooperation relationship attribute information takes into account the mutual business cooperation logic of the entity to be encrypted and the encryption entity on the road, and providing a reliable decision basis for the subsequent encryption task generation.

In some embodiments, the candidate encryption class submission path information includes encryption entity record information of a collaborative stop in the submitted technical document manifest; the number of the target cooperative relationship attribute information is at least two; the encryption-based delivery path information in each target collaborative relationship attribute information respectively includes encryption entity record information that is not collaboratively stayed in the delivered technical document list, and on the basis of the above contents, the determining, by the cooperative adaptation degree information of the encryption-based collaborative information stream between the encryption-based delivery path information in the target collaborative relationship attribute information and the candidate encryption-based delivery path information, of the encryption-based delivery path information described in step S130 is an encryption compensation task corresponding to the candidate encryption-based delivery path information, which may include the following steps S1301 to S1305.

Step S1301, obtaining a first document object collaborative stop tag of the candidate encryption type submission path information according to the encryption entity record information of the collaborative stop.

Step S1302, obtaining a second document object collaborative stop tag of the encrypted delivery path information in each target collaborative relationship attribute information respectively according to the encryption entity record information that does not collaboratively stop and is included in each target collaborative relationship attribute information.

Step S1303, obtaining the label adaptation degrees between the first document object collaborative stopping label and the second document object collaborative stopping label corresponding to each target collaborative relationship attribute information. For example, the tag adaptation degree may be obtained by calculating a tag attribute value between different document object collaborative stay tags, the tag attribute value may be used to distinguish different document object collaborative stay tags, and a value of the tag adaptation degree may be 0 to 1, that is, the higher the value of the tag adaptation degree is, the higher a correlation between different document object collaborative stay tags is, or the higher a degree of influence between different document object collaborative stay tags is, for example, a service flow of collaborative stay may influence a service flow of non-collaborative stay.

Step S1304, determining cooperative adaptation degree information of the encrypted cooperative information stream between the encrypted-type delivery path information in each target cooperative relationship attribute information and the candidate encrypted-type delivery path information, respectively, according to the label adaptation degree corresponding to each target cooperative relationship attribute information.

Step S1305, when the number of the target cooperative relationship attribute information is greater than the first target number and less than or equal to the second target number, determining an encryption compensation task corresponding to the to-be-encrypted delivery path information in the target cooperative relationship attribute information as an encryption compensation task corresponding to the candidate encrypted delivery path information; the target cooperative relationship attribute information refers to target cooperative relationship attribute information in which a correlation coefficient of cooperative adaptation degree information of a corresponding encrypted cooperative information stream is greater than or equal to a correlation coefficient threshold of the encrypted cooperative information stream. For example, the correlation coefficient may also take a value of 0 to 1.

In this way, by implementing the steps S1301 to S1305, when determining the encryption compensation task corresponding to the candidate encryption class delivery path information, the influence of the cooperative staying behavior of the encryption entity on the change of the encryption state of the entity to be encrypted can be considered, so that the encryption compensation task corresponding to the candidate encryption class delivery path information can comprehensively consider the change of the encryption state of the entity to be encrypted and the change of the encryption state of the encryption entity.

For some possible embodiments, the number of delivery encryption route types of the encryption entity record information of the collaborative stop is at least two, and based on this, the obtaining the first document object collaborative stop tag of the candidate encryption class delivery path information according to the encryption entity record information of the collaborative stop described in step S1301 includes: acquiring a recording information cooperative encryption node corresponding to each piece of encryption entity recording information of at least two pieces of encryption entity recording information of cooperative stay respectively; acquiring a first associated collaborative encryption node corresponding to the encrypted entity record information of at least two collaborative dwells according to the record information collaborative encryption node corresponding to the encrypted entity record information of each collaborative dwelling; and determining the first associated collaborative encryption node as the first document object collaborative stay tag.

In some possible embodiments, the at least two pieces of target collaborative relationship attribute information include xth piece of target collaborative relationship attribute information, where X is a positive integer less than or equal to the total number of the at least two pieces of target collaborative relationship attribute information; the number of delivery encryption routing types of the uncoordinated stayed encryption entity record information included in the xth target cooperative relationship attribute information is at least two, based on which, the obtaining of the second document object cooperative stay tag of the encryption class delivery path information in each target cooperative relationship attribute information according to the uncoordinated stayed encryption entity record information included in each target cooperative relationship attribute information described in step S1302 may include: acquiring a record information cooperative encryption node corresponding to each piece of uncoordinated staying encryption entity record information in at least two pieces of uncoordinated staying encryption entity record information included in the Xth target cooperative relationship attribute information; acquiring at least two second associated cooperative encryption nodes corresponding to the recording information of the encryption entity which does not stop in cooperation according to the recording information cooperative encryption node corresponding to the recording information of the encryption entity which does not stop in cooperation; and determining the second associated collaborative encryption node as a second document object collaborative stop tag of the encryption type submission path information in the Xth target collaborative relationship attribute information.

For some possible embodiments, the number of the candidate encryption class submission path information is at least two, and further, the method may further include the following steps S21-S24.

Step S21, when the number of the target cooperative relationship attribute information is less than or equal to the first target number, determining target cooperative relationship attribute information where the encrypted cooperative information of which correlation coefficient is the largest corresponding to the cooperative adaptation degree information of the encrypted cooperative information stream between each candidate encrypted type delivery path information is located as a candidate cooperative relationship attribute information combination corresponding to each candidate encrypted type delivery path information, respectively.

Step S22, determining the encryption compensation task corresponding to the to-be-encrypted submission path information in the candidate collaborative relationship attribute information combination corresponding to each candidate encryption submission path information as the candidate encryption compensation task corresponding to each candidate encryption submission path information, respectively.

Step S23, determining the total number of encryption certificates of at least two encryption tasks corresponding to the encryption task to be determined according to the candidate encryption compensation task corresponding to each candidate encryption type submission path information; acquiring first record information of the number of total encryption certificates of at least two encryption tasks in an encryption compensation task corresponding to-be-encrypted submission path information of at least two target cooperative relationship attribute information; and determining the total number of encryption certificates of each candidate encryption class submission path information aiming at the first target encryption task of the encryption task to be determined according to the first record information.

Step S24, determining the encryption task to be determined, which has the total number of encryption certificates of the first target encryption task corresponding to each candidate encryption type delivery path information, as the encryption compensation task corresponding to each candidate encryption type delivery path information; and the second record information of the total number of the encryption certificates of at least two encryption tasks in the encryption compensation task corresponding to each candidate encryption class submission path information is matched with the first record information.

In this way, by performing the above steps S21 to S24, the encryption compensation task can be determined from the level of the total number of encryption certificates of the encryption tasks, thereby ensuring that the encryption compensation task corresponding to each candidate encryption class delivery route information matches the actual road encryption situation.

On the basis of the above, the following contents described in steps S25 to S27 may be further included.

Step S25, when the number of the target cooperative relationship attribute information is greater than the second target number, counting encryption task matching information of the total number of encryption certificates of at least two encryption tasks of the encryption task to be determined in the encryption compensation task corresponding to the entity record information to be encrypted of the target cooperative relationship attribute information; and the total number of the encryption certificates of the at least two encryption tasks is determined according to the encryption compensation task corresponding to the to-be-encrypted submission path information in the target cooperative relationship attribute information.

Step S26, determining, according to the cooperative adaptation degree information of the encrypted cooperative information stream between the candidate encryption-based delivery path information and the target cooperative relationship attribute information, and the encryption task matching information, a total encryption certificate quantity of the candidate encryption-based delivery path information for the second target encryption task of the encryption task to be determined from the total encryption certificate quantities of at least two encryption tasks.

Step S27, determining the encryption task to be determined having the total number of encryption certificates of the second target encryption task as an encryption compensation task corresponding to the candidate encryption-based delivery path information.

In an actual implementation process, the encryption status changes in real time, and in order to realize accurate prediction of subsequent encryption status as much as possible to determine a corresponding encryption task, the encryption task needs to be updated iteratively, and to achieve the purpose, the scheme may further include the following contents: determining an encryption compensation task corresponding to the to-be-encrypted submission path information in the target cooperative relationship attribute information as an encryption compensation task corresponding to the target cooperative relationship attribute information; determining the target collaborative relationship attribute information and the target collaborative relationship attribute information aiming at the encryption compensation task as a collaborative relationship attribute information combination in the submitted technical document list; combining the collaborative relationship attribute information with the corresponding encryption compensation task to determine the collaborative relationship attribute information as a target encryption compensation task; adding the same encryption entity service distribution label for the encryption class submission path information in the target encryption compensation task and the cooperative relationship attribute information combination; and respectively mapping the target encryption compensation tasks with the encryption entity service distribution labels to target models.

In some examples, the target model may include a decision tree network-based model, a random forest tree network model, and a support vector machine model, and in an actual implementation process, the number of times of policy iterative updating performed on the target encryption compensation task through the decision tree network-based model is greater than the number of times of policy iterative updating performed on the target encryption compensation task through the random forest tree network model; and the updating times of strategy iterative updating of the target encryption compensation task through the random forest tree network model are greater than the updating times of strategy iterative updating of the target encryption compensation task through the support vector machine model.

Further, the loss parameter of the decision tree network-based model for the target encryption compensation task is smaller than the loss parameter of the random forest tree network model for the target encryption compensation task; and the loss parameter of the random forest tree network model for the target encryption compensation task is smaller than the loss parameter of the support vector machine model for the target encryption compensation task.

It is understood that the training process and the parameter tuning process of the different types of neural network models described above are prior art and will not be further described here.

On the basis of the above, the determining, according to the target coordination relationship attribute information and the target coordination relationship attribute information for the encryption compensation task, the entity to be encrypted encryption task in the submitted technical document list and the task configuration information corresponding to the entity to be encrypted encryption task, which are described in step S150, may include the following steps S1501 and S1502.

Step S1501, determining the encryption task of the entity to be encrypted in the submitted technical document list according to the encryption type submission path information in the collaborative relationship attribute information combination.

Step S1502, according to an encryption entity service distribution tag included in the encryption type delivery path information in the collaborative relationship attribute information combination, obtains the target encryption compensation task having the encryption entity service distribution tag from a target model, and determines the obtained target encryption compensation task as task configuration information corresponding to the entity encryption task to be encrypted.

In this way, the target encryption compensation task with the encryption entity traffic distribution label can be determined based on different types of machine learning networks, thereby realizing iterative updating of the encryption compensation task, so as to realize accurate prediction of subsequent encryption conditions as much as possible to determine the corresponding encryption task.

Fig. 3 is a schematic functional module diagram of an eCTD universal technical document submission management device 300 according to an embodiment of the present disclosure, and in this embodiment, the functional modules of the eCTD universal technical document submission management device 300 may be divided according to a method embodiment executed by the eCTD cloud service platform 100, that is, the following functional modules corresponding to the eCTD universal technical document submission management device 300 may be used to execute each method embodiment executed by the eCTD cloud service platform 100. The functions of the functional modules of the eCTD universal technology document delivery management device 300 are described in detail below.

The obtaining module 310 is configured to obtain to-be-encrypted submission path information and encrypted submission path information in the submitted general technical document list.

The first analysis module 320 is configured to perform coordination relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted technical document list based on the service coordination relationship information of the service coordination information between the to-be-encrypted submission path information and the encrypted submission path information in the submitted technical document list, so as to obtain target coordination relationship attribute information.

The first determining module 330 is configured to determine, as candidate encryption-based delivery path information, encryption-based delivery path information in which a collaborative encryption node exists in a collaborative relationship attribute analysis process, and determine, according to collaborative adaptation information of an encryption collaborative information stream between the encryption-based delivery path information in the target collaborative relationship attribute information and the candidate encryption-based delivery path information, an encryption compensation task corresponding to the candidate encryption-based delivery path information.

The second analysis module 340 is configured to perform collaborative relationship attribute analysis on the encryption compensation task corresponding to the candidate encryption type submission path information and the candidate encryption type submission path information to obtain target collaborative relationship attribute information for the encryption compensation task.

The second determining module 350 is configured to determine, according to the target coordination relationship attribute information and the target coordination relationship attribute information for the encryption compensation task, an entity-to-be-encrypted encryption task in the submitted technical document list and task configuration information corresponding to the entity-to-be-encrypted encryption task.

It should be noted that the division of the modules of the above apparatus is only a logical division, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the obtaining module 310 may be a processing element separately set up, or may be implemented by being integrated into a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and the processing element of the apparatus calls and executes the functions of the obtaining module 310. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when some of the above modules are implemented in the form of encrypted program code by a processing element, the processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. As another example, these modules may be integrated together, implemented in the form of a system-on-a-chip (SOC).

Fig. 4 illustrates a hardware structure diagram of an eCTD cloud service platform 100 for implementing the above-described eCTD general technical document delivery management method according to an embodiment of the present disclosure, and as shown in fig. 4, the eCTD cloud service platform 100 may include a processor 110, a machine-readable storage medium 120, a bus 130, and a transceiver 140.

In a specific implementation process, the at least one processor 110 executes computer-executable instructions stored in the machine-readable storage medium 120, so that the processor 110 may execute the method for managing document delivery of the eptd general technology according to the above method embodiment, where the processor 110, the machine-readable storage medium 120, and the transceiver 140 are connected through the bus 130, and the processor 110 may be configured to control the transceiving action of the transceiver 140, so as to perform data transceiving with the document delivery service terminal 200.

For a specific implementation process of the processor 110, reference may be made to the above-mentioned method embodiments executed by the eCTD cloud service platform 100, and implementation principles and technical effects thereof are similar, and details of this embodiment are not described herein again.

In the embodiment shown in fig. 4, it should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor, or in a combination of the hardware and software modules within the processor.

The machine-readable storage medium 120 may comprise high-speed RAM memory and may also include non-volatile storage NVM, such as at least one disk memory.

The bus 130 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus 130 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, the buses in the figures of the present disclosure are not limited to only one bus or one type of bus.

In addition, the embodiment of the disclosure also provides a readable storage medium, in which computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the method for managing the delivery of the eCTD universal technical document is implemented.

Finally, it should be understood that the embodiments described herein are merely illustrative of the principles of the embodiments of the present disclosure. Other variations are also possible within the scope of the present description. Thus, by way of example, and not limitation, alternative configurations of the embodiments of the specification can be considered consistent with the teachings of the specification. Accordingly, the embodiments of the present description are not limited to only those embodiments explicitly described and depicted herein.

Claims

1. An eCTD (eCTD-based document delivery management) method is applied to an eCTD cloud service platform communicated with a document delivery service terminal, and comprises the following steps:

2. The eCTD universal technology document submission management method according to claim 1, wherein the obtaining of the to-be-encrypted submission path information and the encrypted submission path information in the submitted universal technology document list includes:

3. The eCTD universal technology document submission management method according to claim 1, wherein the performing, based on the service collaboration relationship information of the service collaboration information between the to-be-encrypted submission path information and the encrypted submission path information in the submitted universal technology document list, the collaboration relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted universal technology document list to obtain target collaboration relationship attribute information includes:

4. The eCTD universal technology document submission management method of claim 1, wherein the candidate encryption-type submission path information includes encryption entity record information of a collaborative stay in the submitted universal technology document manifest; the number of the target cooperative relationship attribute information is at least two; the encryption type submission path information in each target collaborative relationship attribute information respectively comprises encryption entity record information of uncoordinated stay in the submitted general technical document list; the determining, according to the cooperative adaptation degree information of the encrypted cooperative information stream between the encryption-based delivery path information in the target cooperative relationship attribute information and the candidate encryption-based delivery path information, an encryption compensation task corresponding to the candidate encryption-based delivery path information includes:

5. The eCTD (eCTD-based universal technology document submission management method of claim 4, wherein the number of the candidate encryption-based submission path information is at least two; the method further comprises the following steps:

6. The eCTD generic technology document delivery management method of claim 4, further comprising:

7. The eCTD universal technology document submission management method according to claim 1, wherein the determining, according to the target collaborative relationship attribute information and the target collaborative relationship attribute information for the encryption compensation task, an entity-to-be-encrypted encryption task in the submitted universal technology document list and task configuration information corresponding to the entity-to-be-encrypted encryption task includes:

and acquiring a target encryption compensation task with the encryption entity service distribution label from a target model according to the encryption entity service distribution label of the encryption type submission path information in the cooperative relationship attribute information combination, and determining the acquired target encryption compensation task as task configuration information corresponding to the entity encryption task to be encrypted.

8. An eCTD (eCTD-based technology-universal technology document delivery management system), which comprises a document delivery service terminal and an eCTD cloud service platform communicated with the document delivery service terminal, wherein the system comprises:

the eCTD cloud service platform is used for:

9. The eCTD universal technology document submission management system according to claim 8, wherein the obtaining of the submission path information to be encrypted and the encryption-based submission path information in the submitted universal technology document list includes:

10. The eCTD universal technology document submission management system according to claim 9, wherein the performing, based on the service collaboration relationship information of the service collaboration information between the to-be-encrypted submission path information and the encrypted submission path information in the submitted universal technology document list, the collaboration relationship attribute analysis on the to-be-encrypted submission path information and the encrypted submission path information in the submitted universal technology document list to obtain target collaboration relationship attribute information includes: