Method and apparatus for digital delivery

Abstract

The present invention provides a method and device for digital delivery. In the method for digital delivery, a deliverable upload request is received, wherein the deliverable upload request includes the type and address information of the deliverable to be uploaded and the project identifier of the digital delivery project matching the deliverable to be uploaded; the deliverable to be uploaded is obtained according to the address information of the deliverable to be uploaded; the delivery review condition matching the deliverable to be uploaded is queried according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded; it is determined whether the deliverable to be uploaded satisfies the matching delivery review condition; if the matching delivery review condition is satisfied, deliverable pending confirmation information is sent to a digital content recipient corresponding to the digital delivery project; in response to receiving confirmation information matching the deliverable pending confirmation information, the deliverable to be uploaded is stored in a delivered file system corresponding to the digital delivery project.

Description

Technical Field

[0001] The present invention relates to the technical field of digital factories and smart factories, and in particular to a method and device for digital delivery. Background Art

[0002] With the rapid development of digital technology and Internet technology, digital delivery technology, as an important component of digital factory and smart factory technology, has also been widely used. Generally speaking, digital delivery refers to the process of digitally creating and handing over static information generated during the construction phase of an engineering project with factory objects as the core. Therefore, how to improve the quality and efficiency of digital delivery has become an important issue that needs to be solved. Summary of the invention

[0003] In view of the above, the present invention provides a method and device for digital delivery. By using this method and device, the cost of building a new corresponding delivery system can be saved, and the quality and efficiency of digital delivery can be improved.

[0004] According to one aspect of the present invention, a method for digital delivery is provided, comprising: receiving a deliverable upload request, wherein the deliverable upload request includes the type and address information of the deliverable to be uploaded and a project identifier of a digital delivery project that matches the deliverable to be uploaded; acquiring the deliverable to be uploaded according to the address information of the deliverable to be uploaded; querying a delivery review condition that matches the deliverable to be uploaded according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded; determining whether the deliverable to be uploaded satisfies the matching delivery review condition; if the matching delivery review condition is satisfied, sending deliverable pending confirmation information to a digital content recipient corresponding to the digital delivery project; and in response to receiving confirmation information that matches the deliverable pending confirmation information, storing the deliverable to be uploaded in a delivered file system corresponding to the digital delivery project.

[0005] According to another aspect of the present invention, there is provided an apparatus for digital delivery, comprising: a request receiving unit configured to receive a deliverable upload request, wherein the deliverable upload request includes the type and address information of the deliverable to be uploaded and the project identifier of the digital delivery project matching the deliverable to be uploaded; a deliverable acquisition unit configured to acquire the deliverable to be uploaded according to the address information of the deliverable to be uploaded; a condition query unit configured to query the delivery review condition matching the deliverable to be uploaded according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded; a condition judgment unit configured to judge whether the deliverable to be uploaded satisfies the matching delivery review condition; a confirmation unit configured to send deliverable to-be-confirmed information to a digital content recipient corresponding to the digital delivery project if the matching delivery review condition is satisfied; and in response to receiving the confirmation information matching the deliverable to-be-confirmed information, store the deliverable to be uploaded in a delivered file system corresponding to the digital delivery project.

[0006] According to another aspect of the present invention, there is provided an apparatus for digital delivery, comprising: at least one processor, and a memory coupled to the at least one processor, the memory storing instructions, which, when executed by the at least one processor, causes the at least one processor to execute the method for digital delivery as described above.

[0007] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the method for digital delivery as described above is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A further understanding of the nature and advantages of the content of this specification may be achieved by referring to the following drawings. In the drawings, similar components or features may have the same reference numerals.

[0009] Figure 1 An exemplary architecture of a method and apparatus for digital delivery according to an embodiment of the present specification is shown.

[0010] Figure 2 A flowchart showing an example of a method for digital delivery according to an embodiment of the present specification is shown.

[0011] Figure 3 A flowchart showing an example of a query process of a delivery review condition according to an embodiment of the present specification.

[0012] Figure 4 A flowchart showing an example of a process of determining whether a delivery review condition is satisfied according to an embodiment of the present specification.

[0013] Figure 5 A flowchart showing an example of a process for determining whether content delivery review conditions are met according to an embodiment of the present specification.

[0014] Figure 6 A flowchart showing yet another example of a method for digital delivery according to an embodiment of the present specification is shown.

[0015] Figure 7 A flowchart showing an example of a process of generating a project confirmation request according to an embodiment of the present specification.

[0016] Figure 8 A signaling diagram showing still another example of a method for digital delivery according to an embodiment of this specification.

[0017] Fig. 9 A block diagram showing an example of an apparatus for digital delivery according to an embodiment of the present specification.

[0018] Fig.10 A block diagram showing yet another example of an apparatus for digital delivery according to an embodiment of the present specification.

[0019] Fig.11 A block diagram showing still another example of an apparatus for digital delivery according to an embodiment of the present specification.

[0020] Fig.12 A block diagram showing an example of an apparatus for digital delivery according to an embodiment of the present specification. DETAILED DESCRIPTION

[0021] The subject matter described herein will be discussed below with reference to example implementations. It should be understood that the discussion of these implementations is only to enable those skilled in the art to better understand and implement the subject matter described herein, and is not a limitation of the scope of protection, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of protection of the embodiments of this specification. Various processes or components may be omitted, substituted or added to each example as needed. In addition, the features described relative to some examples may also be combined in other examples.

[0022] As used herein, the term "including" and its variations represent open terms, meaning "including but not limited to". The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other definitions may be included below, whether explicit or implicit. Unless the context clearly indicates otherwise, the definition of a term is consistent throughout the specification.

[0023] The term "deliverables" may refer to various electronic files that carry the delivery information to achieve the handover. "Deliverables" may include but are not limited to at least one of the following: data, documents, 3D models, graphics, etc.

[0024] The method and apparatus for digital delivery according to the embodiments of this specification will be described in detail below with reference to the accompanying drawings.

[0025] Figure 1 An exemplary architecture 100 of a method and apparatus for digital delivery according to an embodiment of the present specification is shown.

[0026] exist Figure 1 In the embodiment, the network 110 is used to interconnect the terminal device 120 and the digital delivery system 130.

[0027] The network 110 may be any type of network capable of interconnecting network entities. The network 110 may be a single network or a combination of various networks. In terms of coverage, the network 110 may be a local area network (LAN), a wide area network (WAN), etc. In terms of carrier media, the network 110 may be a wired network, a wireless network, etc. In terms of data exchange technology, the network 110 may be a circuit switching network, a packet switching network, etc.

[0028] The terminal device 120 may be any type of electronic computing device that can connect to the network 110, access a server or website on the network 110, process data or signals, etc. For example, the terminal device 120 may include various desktop computers, laptop computers, smart phones, etc. In one embodiment, the terminal device 120 may be used by a user. In some cases, the terminal device 120 may interact with the digital delivery system 130. It is understood that there may be different numbers of terminal devices 120 connected to the network 110. In one example, there may be multiple terminal devices 120, such as terminal devices 121, 122, 123, 124, 125, etc. In one example, a user may send a deliverable upload request for digital delivery project X to the digital delivery system 130 through the terminal device 121. The digital delivery system 130 may send a deliverable pending confirmation information to the terminal device 122 corresponding to the digital delivery project X after determining that the deliverable upload request meets the matching delivery review conditions. After the user confirms that it is correct, the confirmation information for the digital delivery project X may be sent to the digital delivery system 130 through the terminal device 122. It can be understood that, in one example, the user can also interact with the digital delivery system 130 through the terminal devices 123, 124, 125 corresponding to the digital delivery project Y, which will not be repeated here.

[0029] It should be understood that Figure 1 All network entities shown in the figure are exemplary. Any other network entities may be involved in the architecture 100 according to specific application requirements.

[0030] Figure 2 A flow chart of a method 200 for digital delivery according to an embodiment of the present specification is shown.

[0031] like Figure 2 As shown, at 210, a deliverable upload request is received.

[0032] In this embodiment, the above-mentioned deliverable upload request may include the type and address information of the deliverable to be uploaded and the project identifier of the digital delivery project that matches the deliverable to be uploaded. In one example, the type of the deliverable to be uploaded may include but is not limited to at least one of the following: data, documents, three-dimensional models, graphics, etc. In one example, the address information may be used to indicate a network address from which the above-mentioned deliverable to be uploaded may be obtained, such as a URL (Uniform Resource Locator). In one example, at least one digital delivery project may be created in advance, and each digital delivery project has a corresponding project identifier for distinguishing different digital delivery projects. The project identifier of the digital delivery project that matches the deliverable to be uploaded may be used to locate the digital delivery project to which the deliverable to be uploaded belongs, so that relatively isolated deliverable management for different digital delivery projects can be achieved.

[0033] At 220 , the deliverable to be uploaded is obtained according to the address information of the deliverable to be uploaded.

[0034] In an example, the deliverable to be uploaded, such as data, documents, three-dimensional models, graphics, etc., may be obtained from the network address indicated by the address information of the deliverable to be uploaded.

[0035] At 230 , a delivery review condition matching the deliverable to be uploaded is searched according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded.

[0036] In this embodiment, delivery review conditions corresponding to the types of deliverables to be uploaded for various digital delivery projects may be pre-stored. The above delivery review conditions may include various preset conditions for reviewing deliverables to be uploaded. In one example, digital delivery project X may correspond to delivery review conditions a1 and a2 corresponding to data types, delivery review conditions b1, b2, and b3 corresponding to file types, and delivery review conditions c1 and c2 corresponding to three-dimensional model types. Thus, the delivery review conditions matching the above deliverables to be uploaded can be queried.

[0037] Optionally, the delivery review condition may include at least one of a format review condition and a content review condition.

[0038] Optionally, continue to see Figure 3 , Figure 3 A schematic diagram showing an example of a query process 300 for delivery review conditions according to an embodiment of the present specification.

[0039] like Figure 3 As shown, at 310, at least one audit condition matching the project identifier of the digital delivery project is queried from a preset audit condition library.

[0040] In this embodiment, the preset review condition library may include format review conditions. The above-mentioned format review conditions may include various preset conditions for format review of the deliverables to be uploaded. In one example, the format review conditions may include but are not limited to at least one of the following: the format of the file (such as data, documents, three-dimensional models, graphics, etc.) belongs to one of the allowed formats, the size of the file (such as data, documents, three-dimensional models, graphics, etc.) does not exceed the specified upper limit, the data includes attributes and attribute values, the data type meets the requirements, the document passes the security scan, and the three-dimensional model uses a unified coordinate system and coordinate origin. It can be understood that the allowed formats and specified upper limits corresponding to different digital delivery projects may be different.

[0041] At 320 , a format review condition matching the type of the deliverable to be uploaded is searched from the at least one review condition that has been searched.

[0042] In one example, the allowed formats and specified upper limits corresponding to different types of deliverables to be uploaded may be different. For example, the allowed formats corresponding to the document type may include .doc and .pdf. The allowed formats corresponding to the 3D model type may include .dxf and .dwg. For another example, the specified upper limit corresponding to the document type may be 200MB. The specified upper limit corresponding to the data type may be 500MB. The specified upper limit corresponding to the 3D model type may be 1GB.

[0043] Based on this, this solution can query the format review conditions that match the deliverable upload request.

[0044] Back to Figure 2 At 240, it is determined whether the deliverable to be uploaded satisfies the matching delivery review conditions.

[0045] Optionally, continue to see Figure 4 , Figure 4 A schematic diagram showing an example of a process 400 for determining whether a delivery review condition is satisfied according to an embodiment of the present specification.

[0046] like Figure 4 As shown, at 410, it is determined whether the deliverable to be uploaded satisfies the queried matching format review condition.

[0047] If the determination at 410 is yes, at 420 , it is determined whether the deliverable to be uploaded meets the content review conditions.

[0048] In this embodiment, the preset review condition library may also include content review conditions. The above-mentioned content review conditions may include various preset conditions for reviewing the content of the deliverables to be uploaded. In one example, the content review conditions may include but are not limited to at least one of the following: the title and directory of the file (such as data, documents, three-dimensional models, graphics, etc.) are consistent with the terms in the text, the title of the file (such as data, documents, three-dimensional models, graphics, etc.) is consistent with the digital delivery project to which it belongs, the data measurement unit meets the requirements, the document has no missing content compared to the corresponding document template, and the three-dimensional model content is complete.

[0049] Optionally, continue to see Figure 5 , Figure 5 A flowchart showing an example of a process 500 for determining whether content delivery review conditions are met according to an embodiment of the present specification.

[0050] like Figure 5 As shown, at 510 , at least two associated files associated with the deliverable to be uploaded are obtained from a delivered file system corresponding to the digital delivery project.

[0051] In this embodiment, each digital delivery project may correspond to a delivered file system. Each delivered file system may store various files that belong to the corresponding digital delivery project and have been confirmed. In one example, the associated file may be a file that belongs to the same digital delivery project as the deliverable to be uploaded and is of the same type. In one example, the associated file may be a file that belongs to the same digital delivery project as the deliverable to be uploaded, has the same delivery content and is of a different type. In one example, the consistency of the delivery content may include, but is not limited to, at least one of the following: the deliverer information (e.g., "XX Company") is consistent, the file title contains the same keyword (e.g., "XX Equipment"), and the factory area involved in the file (e.g., "Workshop X") is consistent.

[0052] At 520 , it is determined whether the deliverable to be uploaded and at least two associated files meet content consistency requirements.

[0053] In this embodiment, the content consistency between the deliverable to be uploaded and each associated file can be determined. In one example, if the deliverable to be uploaded and each associated file are both of the document type, the keywords of the deliverable to be uploaded and each associated file can be extracted respectively, and then the overlap rate between the keywords corresponding to the deliverable to be uploaded and each associated file can be determined as the content consistency corresponding to the deliverable to be uploaded and each associated file. A content consistency representative value (such as a maximum value, a minimum value, an average value, etc.) is determined according to the determined content consistency. If the determined content consistency representative value is greater than a preset content threshold, it is considered that the deliverable to be uploaded and at least two associated files meet the content consistency requirement. In one example, if the deliverable to be uploaded is of a three-dimensional model type, and the associated file is of a document type consistent with the factory area involved in the deliverable to be uploaded, each device bit number can be extracted from the deliverable to be uploaded, and the number of times the device bit number appears in the associated document can be determined. If the number exceeds the preset threshold, it is considered that the deliverable to be uploaded and at least two associated files meet the content consistency requirement.

[0054] If the judgment is yes, at 530, it is determined that the deliverable to be uploaded meets the content review condition.

[0055] Based on this, this solution can determine whether the deliverable to be uploaded meets the content review conditions through the consistency of information between files.

[0056] Back to Figure 4 If the judgment at 420 is yes, at 430 , it is determined whether the deliverable to be uploaded meets the matching delivery review conditions.

[0057] If the determination at 410 or 420 is negative, at 440 , it is determined that the deliverable to be uploaded does not satisfy the matching delivery review condition.

[0058] Based on this, this solution can comprehensively judge whether the deliverables to be uploaded meet the matching delivery review conditions from the two aspects of format and content.

[0059] Back to Figure 2 If 240 is judged as yes, execute the following steps 250-260.

[0060] At 250 , deliverables receipt confirmation information is sent to the digital content recipient corresponding to the digital delivery item.

[0061] In one example, the deliverable to be confirmed information may be used to indicate that the deliverable that has passed the delivery review condition has been uploaded and is to be confirmed. In one example, the digital content recipient may be a terminal used by a user to receive the deliverable to be uploaded. In one example, the deliverable to be confirmed information may include basic information of the deliverable to be confirmed, such as the acquisition address, name, uploader information, etc.

[0062] At 260 , in response to receiving confirmation information matching the deliverable to-be-confirmed information, the deliverable to be uploaded is stored in a delivered file system corresponding to the digital delivery project.

[0063] In one example, if the digital content recipient confirms that the deliverable to be uploaded meets the requirements, a confirmation message matching the deliverable to be confirmed message may be sent. In one example, each digital delivery project may correspond to a delivered file system. After receiving the confirmation message, the corresponding deliverable to be uploaded may be stored in the corresponding delivered file system. Thus, the confirmed deliverables of each digital delivery project may be managed.

[0064] Continue to see Figure 6 , Figure 6 A flowchart of yet another example of a method 600 for digital delivery according to an embodiment of the present specification is shown.

[0065] like Figure 6 As shown, at 610, a digital delivery project request is received.

[0066] In this embodiment, the above-mentioned digital delivery project establishment request may include digital delivery mode information. The digital delivery mode information can be used to indicate the digital content delivery party, the digital content recipient and the corresponding permissions. In one example, the digital delivery mode information can be used to indicate the owner (owner) execution mode or the owner EP (Engineering, Procurement) execution mode information. In one example, the permissions of the digital content delivery party may include uploading deliverables. The permissions of the digital content recipient may include reviewing the uploaded deliverables to confirm or reject. In one example, the digital delivery mode information can be used to indicate the third-party licensor execution mode. In one example, the permissions of the third-party licensor as the digital content delivery party may include uploading deliverables and reviewing the deliverables uploaded by the subcontractor to confirm or reject. The permissions of the owner as the digital content recipient may include reviewing the deliverables uploaded by the third-party licensor to confirm or reject.

[0067] At 620, according to the digital content recipient indicated by the digital delivery mode information, a delivery requirement document of the digital delivery project corresponding to the digital delivery project establishment request is obtained.

[0068] In one example, a delivery requirement document of a digital delivery project corresponding to a digital delivery project establishment request may be obtained from a digital content recipient, wherein the delivery requirement document may be used to specify a delivery standard for a deliverable.

[0069] At 630 , a project confirmation request indicative of a digital delivery project is generated based on the delivery requirements document.

[0070] In one example, the generated project confirmation request may include an address for obtaining the delivery requirement document.

[0071] Optionally, continue to see Figure 7 , Figure 7 A flowchart showing an example of a process 700 for generating a project confirmation request according to an embodiment of the present specification.

[0072] like Figure 7 As shown, at 710, the model delivery review conditions are extracted from the delivery requirement document.

[0073] In one example, the model delivery review conditions may include conditions for specifying the delivery standard of deliverables of the three-dimensional model type. In one example, the model delivery review conditions may include a specified coordinate system, coordinate origin, component naming rules, etc.

[0074] At 720, a seed file is generated according to the model delivery review conditions.

[0075] In this embodiment, the generated seed file can be a template that meets the above-mentioned model delivery review conditions. In one example, the seed file can include a seed DGN file and a seed DWG file. By copying the seed DGN file or the seed DWG file, a new DGN file or DWG file can be created, thereby ensuring that the created design model and / or drawing model also meets the above-mentioned model delivery review conditions.

[0076] At 730, a project confirmation request indicating a digital delivery project is generated based on the delivery requirements document and the generated seed file.

[0077] In one example, the generated project confirmation request may include a delivery requirement file and an acquisition address of the generated seed file.

[0078] Based on this, this solution can automatically generate a seed file based on the delivery requirement file, which helps the delivery party to more efficiently create deliverables of the 3D model type that meets the delivery requirements.

[0079] Back to Figure 6 , at 640 , a project confirmation request is sent to the digital content delivery party indicated by the digital delivery mode information.

[0080] At 650 , in response to receiving confirmation information matching the project confirmation request, a project establishment success message is sent to the sender of the digital delivery project establishment request.

[0081] In this embodiment, the above-mentioned project establishment success information may include a project identifier of the digital delivery project.

[0082] At 660, a deliverable upload request is received.

[0083] At 670 , the deliverable to be uploaded is acquired according to the address information of the deliverable to be uploaded.

[0084] At 680 , a delivery review condition matching the deliverable to be uploaded is searched according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded.

[0085] At 690 , it is determined whether the deliverable to be uploaded satisfies the matching delivery review conditions.

[0086] If the answer is yes, the following steps are performed: At 691, a delivery item to-be-confirmed information is sent to a digital content recipient corresponding to the digital delivery project.

[0087] At 693 , in response to receiving the confirmation information matching the deliverable to-be-confirmed information, the deliverable to be uploaded is stored in the delivered file system corresponding to the digital delivery project.

[0088] It should be noted that the above steps 660-692 can refer to the corresponding description of steps 210-260 of the above embodiment, which will not be repeated here.

[0089] Based on this, this solution can send a project confirmation request containing delivery requirement document information to the corresponding digital content delivery party, so that the digital content delivery party can obtain more information before the project is established, which helps to upload deliverables that meet the requirements, thereby improving the confirmation pass rate of deliverables and improving the efficiency of digital delivery.

[0090] Continue to see Figure 8 , Figure 8 A signaling diagram showing yet another example of a method 800 for digital delivery according to an embodiment of the present specification.

[0091] like Figure 8 As shown, at 810, a digital delivery project request is received.

[0092] In this embodiment, the above-mentioned digital delivery project establishment request may include digital delivery mode information. The digital delivery mode information may be used to indicate the digital content deliverer, the digital content recipient, and the corresponding permissions. The above-mentioned digital delivery mode information may include information for indicating the engineering general contracting mode. In one example, the engineering general contracting may include engineering-procurement-construction (EPC). In one example, the authority of the EPC contractor as the digital content deliverer may include uploading deliverables and reviewing the deliverables uploaded by the subcontractor to confirm or reject them. The authority of the owner as the digital content recipient may include reviewing the deliverables uploaded by the EPC contractor to confirm or reject them.

[0093] At 820, according to the digital content recipient indicated by the digital delivery mode information, a delivery requirement document of the digital delivery project corresponding to the digital delivery project establishment request is obtained.

[0094] At 830 , a project confirmation request indicative of a digital delivery project is generated based on the delivery requirements document.

[0095] At 840 , a project confirmation request is sent to the digital content delivery party indicated by the digital delivery mode information.

[0096] At 850, confirmation information matching the project confirmation request is received.

[0097] At 860, a project establishment success message is sent to the sender of the digital delivery project establishment request.

[0098] At 870, a SCE deliverable upload request is received.

[0099] In this embodiment, the subcontractor deliverable upload request may be a deliverable upload request submitted by a subcontractor corresponding to the engineering general contracting model indicated by the above-mentioned digital delivery model information.

[0100] At 880, the delivery review conditions matching the subcontractor deliverable upload request are queried.

[0101] At 890 , it is determined whether the deliverable indicated by the subcontractor deliverable upload request satisfies the queried matching delivery review condition.

[0102] It should be noted that the specific description of the above steps 880-890 is similar to the relevant description of steps 230-240 in the aforementioned embodiment, and will not be repeated here.

[0103] If the answer is yes, the following steps are performed: At 892, the subcontractor deliverables pending confirmation information is sent to the general contractor corresponding to the subcontractor deliverables upload request.

[0104] In this embodiment, the information on the pending receipt of subcontractor deliverables can be used to indicate that deliverables uploaded by the subcontractor and that have passed the delivery review conditions have been uploaded and are awaiting confirmation. In one example, the digital content recipient may be a terminal used by a user for receiving the above-mentioned deliverables to be uploaded. In one example, the general contractor corresponding to the subcontractor deliverable upload request may be the general contractor corresponding to the sender of the subcontractor deliverable upload request. The information on the pending receipt of subcontractor deliverables may include basic information of the deliverables to be confirmed uploaded by the above-mentioned subcontractor, such as the acquisition address, name, uploader information, etc.

[0105] At 894, confirmation information matching the SCE deliverables pending confirmation information is received.

[0106] In this embodiment, if the corresponding general contractor confirms that the deliverables uploaded by the subcontractor meet the requirements, it can send confirmation information that matches the deliverables to be confirmed information of the subcontractor.

[0107] At 896 , the deliverables indicated by the SCE deliverable upload request are stored in the deliverables-to-be-confirmed file system corresponding to the digital delivery project.

[0108] In one example, each digital delivery project may correspond to a file system of deliverables to be confirmed. After receiving the confirmation information sent by the general contractor, the deliverables indicated by the corresponding subcontractor's deliverable upload request may be stored in the corresponding file system of deliverables to be confirmed. Thus, the deliverables of each digital delivery project that have been confirmed by the general contractor and are to be confirmed by the digital content recipient can be managed.

[0109] At 8100, a deliverable upload request is received.

[0110] In one example, the deliverable upload request may be sent by a general contractor.

[0111] At 8110, the deliverable to be uploaded is obtained according to the address information of the deliverable to be uploaded.

[0112] At 8120, the delivery review conditions matching the deliverable to be uploaded are queried according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded.

[0113] At 8130, it is determined whether the deliverable to be uploaded satisfies the matching delivery review conditions.

[0114] If the answer is yes and the delivery timing requirements are met, execute the following steps 8131-8135.

[0115] In this embodiment, if 8130 judges as yes, it can be further determined whether the delivery timing requirement is met. In one example, the delivery timing requirement may include but is not limited to at least one of the following: reaching the scheduled progress node, the target plan is completed, and the specified time interval is reached. In one example, if the scheduled progress indicates that a certain delivery should be completed on X month X day, then the delivery timing requirement is met when it reaches X month X day. In one example, once the project master schedule, the device master schedule, the project control plan, the project resource plan, etc. are completed, the delivery timing requirement is met. In one example, if a specified time interval (such as one day, one week, 15 days, one month) is reached, the delivery timing requirement is met.

[0116] At 8131, a deliverable matching the deliverable to be uploaded is searched from the deliverable to be confirmed file system corresponding to the digital delivery project.

[0117] In one example, the deliverable that matches the deliverable to be uploaded may be any deliverable in the corresponding deliverable to be confirmed file system that has not been confirmed by the digital content recipient. In one example, the deliverable that matches the deliverable to be uploaded may be a deliverable that meets the delivery timing requirement corresponding to the deliverable upload request. For example, the deliverable may be at the same predetermined progress node indicated by the project corresponding to the deliverable upload request, or may belong to the same target plan as the deliverable upload request.

[0118] At 8133, deliverables to be confirmed are generated based on the deliverables to be uploaded and the matched deliverables found.

[0119] In this embodiment, the generated deliverables to be confirmed information may include basic information of the deliverables to be confirmed, such as acquisition address, name, uploader information, etc. The deliverables to be confirmed may include the deliverables to be uploaded and the matched deliverables found.

[0120] At 8135, a delivery item pending confirmation information is sent to a digital content recipient corresponding to the digital delivery project.

[0121] At 8140 , in response to receiving confirmation information that matches the deliverable to-be-confirmed information, the deliverable to be uploaded is stored in a delivered file system corresponding to the digital delivery project.

[0122] It should be noted that the above steps 8100-8130, 8135-8140 can refer to the relevant descriptions of steps 210-240 and 250-260 in the aforementioned embodiments respectively, and will not be repeated here.

[0123] Based on this, this solution provides a digital delivery method for the EPC model. Through the control of the recipient of information and the corresponding permissions, the general contractor is responsible for the deliverables uploaded by itself and the above-mentioned deliverables of the subcontractor. In addition, through the control of the file system of deliverables to be confirmed and the delivery timing corresponding to the digital delivery project, the frequency of disturbance to the recipient of digital content is reduced while ensuring timely understanding of the progress of digital delivery.

[0124] Optionally, if the determination at 8130 is no or in response to receiving rejection information that matches the deliverables to be confirmed information, at 8151 , deliverables rectification information is generated.

[0125] In this embodiment, if the digital content recipient confirms that the deliverable to be uploaded does not meet the requirements, a rejection message matching the deliverable to be confirmed information may be sent. The deliverable rectification information may be used to indicate that the deliverable indicated by the deliverable to be confirmed information needs to be rectified. In one example, the deliverable rectification information may include basic information of the deliverable to be rectified, such as an identifier of the deliverable. Optionally, the deliverable rectification information may also include rectification information of the deliverable to be rectified, such as reasons for rejection, rectification suggestions, and the like.

[0126] At 8153, deliverable rectification information is sent to the general contractor corresponding to the subcontractor deliverable upload request.

[0127] Based on this, a digital delivery method for the EPC model is provided. Through the control of the recipient of rectification information and the corresponding permissions, the general contractor is responsible for the deliverables uploaded by itself and the above-mentioned deliverables of the subcontractor, which helps to integrate digital delivery with overall project management and improve system integration and efficiency.

[0128] use Figure 1-Figure 8 The method for digital delivery disclosed in the document can query the corresponding delivery review conditions according to the received deliverable upload request, and automatically perform a preliminary review of the deliverable, and only send the deliverables that have passed the review to the digital content recipient, and store them in the delivered file system corresponding to the corresponding digital delivery project after confirmation. This realizes the platform management of multiple digital delivery projects, saves the cost of building a new corresponding delivery system for each digital delivery, and performs a preliminary review of the deliverables through the delivery review conditions corresponding to the digital delivery projects managed by the platform, thereby improving the quality and efficiency of digital delivery.

[0129] Fig. 9 FIG. 9 is a block diagram showing an example of a device 900 for digital delivery according to an embodiment of the present specification. The device embodiment can be used with Figure 2-Figure 8 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0130] like Fig. 9 As shown, the apparatus 900 for digital delivery may include a request receiving unit 910 , a deliverable obtaining unit 920 , a condition query unit 930 , a condition judgment unit 940 and a confirmation unit 950 .

[0131] The request receiving unit 910 is configured to receive a deliverable upload request. The deliverable upload request includes the type and address information of the deliverable to be uploaded and the project identifier of the digital delivery project matching the deliverable to be uploaded. The operation of the request receiving unit 910 can refer to the above Figure 2 The operation of 210 is described.

[0132] The delivery acquisition unit 920 is configured to acquire the delivery to be uploaded according to the address information of the delivery to be uploaded. The operation of the delivery acquisition unit 920 can refer to the above Figure 2 The operation of 220 is described.

[0133] The condition query unit 930 is configured to query the delivery review conditions matching the deliverable to be uploaded according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded. The operation of the condition query unit 930 can refer to the above Figure 2 The operation of 230 is described.

[0134] The condition judgment unit 940 is configured to judge whether the deliverable to be uploaded satisfies the matching delivery review condition. The operation of the condition judgment unit 940 can refer to the above Figure 2 The operation of 240 is described.

[0135] In one example, the condition judgment unit 940 may be further configured to: judge whether the deliverable to be uploaded satisfies the matched format review condition found; if the matched format review condition is satisfied, judge whether the deliverable to be uploaded satisfies the content review condition; if the matched content review condition is satisfied, determine that the deliverable to be uploaded satisfies the matched delivery review condition; if the matched format review condition is not satisfied, determine that the deliverable to be uploaded does not satisfy the matched delivery review condition. The operation of the condition judgment unit 940 may refer to the above. Figure 4 The operations of 410-440 are described.

[0136] In one example, the conditional judgment unit 940 may be further configured to: obtain at least two associated files associated with the deliverable to be uploaded from the delivered file system corresponding to the digital delivery project; determine whether the deliverable to be uploaded and the at least two associated files meet the content consistency requirement; if the content consistency requirement is met, determine that the deliverable to be uploaded meets the content review condition. The operation of the conditional judgment unit 940 can refer to the above Figure 5 The operations of 510-530 are described.

[0137] The confirmation unit 950 is configured to send a delivery confirmation information to the digital content recipient corresponding to the digital delivery project if the matching delivery review condition is met; in response to receiving the confirmation information matching the delivery confirmation information, store the deliverable to be uploaded in the delivered file system corresponding to the digital delivery project. The operation of the confirmation unit 950 can refer to the above Figure 2 The operation of the 250 is described.

[0138] Reference below Fig.10 , Fig.10 A block diagram showing yet another example of an apparatus 1000 for digital delivery according to an embodiment of the present specification.

[0139] like Fig.10 As shown, the device 1000 for digital delivery may include a project establishment unit 1010 , a request receiving unit 1020 , a deliverable acquisition unit 1030 , a condition query unit 1040 , a condition judgment unit 1050 and a confirmation unit 1060 .

[0140] The project establishment unit 1010 is configured to receive a digital delivery project establishment request, wherein the digital delivery project establishment request includes digital delivery mode information, and the digital delivery mode information is used to indicate the digital content deliverer, the digital content recipient and the corresponding permissions; according to the digital content recipient indicated by the digital delivery mode information, obtain the delivery requirement document of the digital delivery project corresponding to the digital delivery project establishment request; according to the delivery requirement document, generate a project confirmation request indicating the digital delivery project; send the project confirmation request to the digital content deliverer indicated by the digital delivery mode information; in response to receiving confirmation information matching the project confirmation request, send project establishment success information to the sender of the digital delivery project establishment request, wherein the project establishment success information includes the project identifier of the digital delivery project. The operation of the project establishment unit 1010 can refer to the above Figure 6 The operations of 610-650 are described.

[0141] In one example, the project establishment unit 1010 may be further configured to: extract the model delivery review conditions from the delivery requirement document; generate a seed file according to the model delivery review conditions; and generate a project confirmation request indicating the digital delivery project according to the delivery requirement document and the generated seed file. The operation of the project establishment unit 1010 may refer to the above Figure 2 The operations of 710-730 are described.

[0142] It should be noted that the request receiving unit 1020, the delivery acquisition unit 1030, the condition query unit 1040, the condition judgment unit 1050 and the confirmation unit 1060 can refer to the above Fig. 9 The operations of the request receiving unit 910, the deliverable obtaining unit 920, the condition query unit 930, the condition judgment unit 940 and the confirmation unit 950 are described.

[0143] Reference below Fig.11 , Fig.11 A block diagram showing yet another example of an apparatus 1100 for digital delivery according to an embodiment of the present specification.

[0144] like Fig.11 As shown, the device 1100 for digital delivery may include a project establishment unit 1110, a general contracting confirmation unit 1120, a request receiving unit 1130, a deliverable acquisition unit 1140, a condition query unit 1150, a condition judgment unit 1160 and a confirmation unit 1170.

[0145] The general contractor confirmation unit 1120 is configured to receive a subcontractor's deliverable upload request; query the delivery review conditions that match the subcontractor's deliverable upload request; in response to the deliverable indicated by the subcontractor's deliverable upload request satisfying the queried matching delivery review conditions, send the subcontractor's deliverable pending confirmation information to the general contractor corresponding to the subcontractor's deliverable upload request; in response to receiving the confirmation information that matches the subcontractor's deliverable pending confirmation information, store the deliverable indicated by the subcontractor's deliverable upload request in the deliverable pending confirmation file system corresponding to the digital delivery project. The operation of the general contractor confirmation unit 1110 can refer to the above Figure 8 The operation of 870-896 is described.

[0146] The confirmation unit 1170 may be further configured to: if the matching delivery review conditions are met, in response to meeting the delivery timing requirements, query the deliverables matching the deliverables to be uploaded from the deliverables to be confirmed file system corresponding to the digital delivery project; generate deliverables to be confirmed information based on the deliverables to be uploaded and the matched deliverables found; send the deliverables to be confirmed information to the digital content recipient corresponding to the digital delivery project; in response to receiving the confirmation information matching the deliverables to be confirmed information, store the deliverables to be uploaded in the delivered file system corresponding to the digital delivery project. The operation of the confirmation unit 1170 may refer to the above. Figure 8 Describe the operation of 8130-8140.

[0147] It should be noted that the project establishment unit 1110, the request receiving unit 1130, the deliverable acquisition unit 1140, the condition query unit 1150, and the condition judgment unit 1160 can refer to the above Fig.10 The operations of the project establishment unit 1010, the request receiving unit 1020, the deliverable acquisition unit 1030, the condition query unit 1040, and the condition judgment unit 1050 are described.

[0148] Optionally, the device 1100 for digital delivery may further include a rectification unit 1110. The rectification unit 1110 may be configured to: generate deliverable rectification information in response to the deliverable indicated by the subcontractor deliverable upload request not satisfying the queried matching delivery review condition or in response to receiving rejection information matching the deliverable to be confirmed information; and send the deliverable rectification information to the general contractor corresponding to the subcontractor deliverable upload request. The operation of the rectification unit 1110 may refer to the above Figure 8 Describe the operation of 8151-8153.

[0149] Reference above Figures 1 to 11 , embodiments of the method and apparatus for digital delivery according to the embodiments of this specification are described.

[0150] The device for digital delivery in the embodiments of this specification may be implemented in hardware, software, or a combination of hardware and software. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor of the device in which it is located reading the corresponding computer program instructions in the memory into the memory and running them. In the embodiments of this specification, the device for digital delivery may be implemented, for example, using an electronic device.

[0151] Fig.12 A block diagram showing an example of an apparatus 1200 for digital delivery according to an embodiment of the present specification.

[0152] like Fig.12 As shown, the apparatus 1200 for digital delivery may include at least one processor 1210, a memory (e.g., a non-volatile memory) 1220, a memory 1230, and a communication interface 1240, and the at least one processor 1210, the memory 1220, the memory 1230, and the communication interface 1240 are connected together via a bus 1250. At least one processor 1210 executes at least one computer-readable instruction stored or encoded in the memory (i.e., the above-mentioned element implemented in the form of software).

[0153] In one embodiment, a computer executable instruction is stored in a memory, which when executed causes at least one processor 1210 to: receive a deliverable upload request, wherein the deliverable upload request includes the type and address information of the deliverable to be uploaded and the project identifier of the digital delivery project matching the deliverable to be uploaded; obtain the deliverable to be uploaded according to the address information of the deliverable to be uploaded; query the delivery review condition matching the deliverable to be uploaded according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded; determine whether the deliverable to be uploaded satisfies the matching delivery review condition; if the matching delivery review condition is satisfied, send deliverable pending confirmation information to a digital content recipient corresponding to the digital delivery project; and in response to receiving confirmation information matching the deliverable pending confirmation information, store the deliverable to be uploaded in a delivered file system corresponding to the digital delivery project.

[0154] It should be understood that the computer executable instructions stored in the memory, when executed, cause at least one processor 1210 to perform the above combined operations in various embodiments of the present specification. Figure 1-8 Describes the various operations and functions.

[0155] According to one embodiment, a program product such as a computer-readable medium is provided. The computer-readable medium may have instructions (i.e., the above-mentioned elements implemented in the form of software), which, when executed by a computer, causes the computer to perform the above-mentioned combination of various embodiments of this specification. Figure 1-8 Describes the various operations and functions.

[0156] Specifically, a system or device equipped with a readable storage medium can be provided, on which software program codes that implement the functions of any of the above-mentioned embodiments are stored, and a computer or processor of the system or device can read and execute instructions stored in the readable storage medium.

[0157] In this case, the program code itself read from the machine-readable medium can realize the function of any one of the above-mentioned embodiments, and thus the machine-readable code and the machine-readable storage medium storing the machine-readable code constitute a part of the present invention.

[0158] The computer program code required for the operation of each part of this specification can be written in any one or more programming languages, including object-oriented programming languages, such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB, NET and Python, conventional procedural programming languages ​​such as C language, Visual Basic 2003, Perl, COBOL 2002, PHP and ABAP, dynamic programming languages ​​such as Python, Ruby and Groovy, or other programming languages. The program code can be run on the user's computer, or run on the user's computer as an independent software package, or run partly on the user's computer and another part on the remote computer, or all on the remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any network form, such as a local area network (LAN) or a wide area network (WAN), or connected to an external computer (e.g., via the Internet), or in a cloud computing environment, or used as a service, such as software as a service (SaaS).

[0159] Examples of readable storage media include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD-RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or a cloud via a communication network.

[0160] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0161] Not all steps and units in the above-mentioned processes and system structure diagrams are necessary, and some steps or units can be ignored according to actual needs. The execution order of each step is not fixed and can be determined according to needs. The device structure described in the above-mentioned embodiments can be a physical structure or a logical structure, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or some components in multiple independent devices may be implemented together.

[0162] The term "exemplary" as used throughout this specification means "serving as an example, instance, or illustration" and does not imply "preferred" or "advantageous" over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, the techniques may be implemented without these specific details. In some instances, in order to avoid obscuring the concepts of the described embodiments, well-known structures and devices are shown in block diagram form.

[0163] The optional implementation modes of the embodiments of the present specification are described in detail above in conjunction with the accompanying drawings. However, the embodiments of the present specification are not limited to the specific details in the above implementation modes. Within the technical concept of the embodiments of the present specification, various simple modifications can be made to the technical solutions of the embodiments of the present specification, and these simple modifications all belong to the protection scope of the embodiments of the present specification.

[0164] The above description of the contents of this specification is provided to enable any person of ordinary skill in the art to implement or use the contents of this specification. Various modifications to the contents of this specification will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of protection of the contents of this specification. Therefore, the contents of this specification are not limited to the examples and designs described herein, but are consistent with the widest range of principles and novel features disclosed herein.

Claims

1. A method for digital delivery, comprising: Receiving a deliverable upload request, wherein the deliverable upload request includes type and address information of the deliverable to be uploaded and a project identifier of a digital delivery project matching the deliverable to be uploaded; Acquire the deliverable to be uploaded according to the address information of the deliverable to be uploaded; Querying the delivery review conditions matching the deliverable to be uploaded according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded; Determining whether the deliverable to be uploaded meets the matching delivery review conditions; If the matching delivery review conditions are met, Sending a delivery confirmation message to the digital content recipient corresponding to the digital delivery project; In response to receiving confirmation information matching the deliverable to-be-confirmed information, the deliverable to be uploaded is stored in a delivered file system corresponding to the digital delivery item.

2. The method of claim 1, wherein: The querying of the delivery review conditions matching the deliverable to be uploaded according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded includes: Querying at least one audit condition matching the project identifier of the digital delivery project from a preset audit condition library, wherein the preset audit condition library includes a format audit condition; A format review condition matching the type of the deliverable to be uploaded is searched from the at least one review condition found.

3. The method of claim 2, wherein: The delivery review conditions also include content review conditions. The step of judging whether the deliverable to be uploaded satisfies the matching delivery review conditions includes: Determining whether the deliverable to be uploaded meets the matched format review condition found; If the matching format review conditions are met, Determining whether the deliverable to be uploaded meets the content review conditions; If the matching content review condition is met, determining that the deliverable to be uploaded meets the matching delivery review condition; If the matching format review condition is not met, it is determined that the deliverable to be uploaded does not meet the matching delivery review condition.

4. The method of claim 3, wherein: The determining whether the deliverable to be uploaded satisfies the content review condition includes: Acquire at least two associated files associated with the deliverable to be uploaded from a delivered file system corresponding to the digital delivery project; Determining whether the deliverable to be uploaded and the at least two associated files meet content consistency requirements; If the content consistency requirement is met, it is determined that the deliverable to be uploaded meets the content review condition.

5. The method according to any one of claims 1 to 4, wherein: Before receiving the deliverable upload request, the method further includes: Receiving a digital delivery project establishment request, wherein the digital delivery project establishment request includes digital delivery mode information, and the digital delivery mode information is used to indicate a digital content deliverer, a digital content recipient, and corresponding permissions; According to the digital content recipient indicated by the digital delivery mode information, obtaining a delivery requirement document of the digital delivery project corresponding to the digital delivery project establishment request; generating a project confirmation request indicating the digital delivery project based on the delivery requirement document; Sending the project confirmation request to the digital content delivery party indicated by the digital delivery mode information; In response to receiving confirmation information matching the project confirmation request, sending project establishment success information to the sender of the digital delivery project establishment request, wherein the project establishment success information includes a project identifier of the digital delivery project.

6. The method of claim 5, wherein: Before generating a project confirmation request indicating the digital delivery project according to the delivery requirement document, the method further includes: Extracting model delivery review conditions from the delivery requirements document; Generate a seed file according to the model delivery review conditions, Generating a project confirmation request indicating the digital delivery project according to the delivery requirement document includes: A project confirmation request indicating the digital delivery project is generated based on the delivery requirement file and the generated seed file.

7. The method of claim 5, wherein: The digital delivery mode information includes information indicating the engineering general contracting mode. Before receiving the deliverable upload request, the method further includes: Receive upload requests for subcontractor deliverables; Querying the delivery review conditions that match the subcontractor's deliverable upload request; In response to the deliverable indicated by the subcontractor deliverable upload request satisfying the queried matching delivery review condition, Sending a subcontractor deliverable to-be-confirmed receipt message to the general contractor corresponding to the subcontractor deliverable upload request; In response to receiving confirmation information matching the unconfirmed receipt information of the subcontractor deliverable, storing the deliverable indicated by the subcontractor deliverable upload request in the unconfirmed deliverable file system corresponding to the digital delivery project, The sending of the delivery item to-be-confirmed information to the digital content recipient corresponding to the digital delivery project includes: In response to meeting the delivery timing requirements, Searching for deliverables matching the deliverables to be uploaded from the deliverables to be confirmed file system corresponding to the digital delivery project; Generate deliverables to be confirmed information according to the deliverables to be uploaded and the matched deliverables found; The deliverable to-be-acknowledged information is sent to a digital content recipient corresponding to the digital delivery item.

8. The method of claim 7, wherein: The method further comprises: In response to the deliverable indicated by the subcontractor deliverable upload request not satisfying the queried matching delivery review condition or in response to receiving rejection information matching the deliverable to-be-confirmed information, Generate deliverable rectification information; The deliverable rectification information is sent to the general contractor corresponding to the subcontractor deliverable upload request.

9. An apparatus for digital delivery, comprising: A request receiving unit is configured to receive a deliverable upload request, wherein the deliverable upload request includes the type and address information of the deliverable to be uploaded and the project identifier of the digital delivery project matching the deliverable to be uploaded; A delivery acquisition unit, configured to acquire the delivery to be uploaded according to the address information of the delivery to be uploaded; A condition query unit, configured to query a delivery review condition matching the deliverable to be uploaded according to the project identifier of the digital delivery project and the type of the deliverable to be uploaded; A condition judgment unit, configured to judge whether the deliverable to be uploaded satisfies a matching delivery review condition; The confirmation unit is configured to send the deliverable to be confirmed information to the digital content recipient corresponding to the digital delivery project if the matching delivery review conditions are met; in response to receiving the confirmation information matching the deliverable to be confirmed information, store the deliverable to be uploaded in the delivered file system corresponding to the digital delivery project.

10. The device of claim 9, wherein: The device also includes: A project establishment unit is configured to receive a digital delivery project establishment request, wherein the digital delivery project establishment request includes digital delivery mode information, and the digital delivery mode information is used to indicate a digital content deliverer, a digital content recipient and corresponding permissions; obtain a delivery requirement document of a digital delivery project corresponding to the digital delivery project establishment request according to the digital content recipient indicated by the digital delivery mode information; generate a project confirmation request indicating the digital delivery project according to the delivery requirement document; send the project confirmation request to the digital content deliverer indicated by the digital delivery mode information; and send project establishment success information to the sender of the digital delivery project establishment request in response to receiving confirmation information matching the project confirmation request, wherein the project establishment success information includes a project identifier of the digital delivery project.

11. The device of claim 10, wherein: The digital delivery mode information includes information indicating the engineering general contracting mode. The device also includes: The general contractor confirmation unit is configured to: receive a subcontractor deliverable upload request; query the delivery review conditions that match the subcontractor deliverable upload request; in response to the deliverable indicated by the subcontractor deliverable upload request satisfying the query matching delivery review conditions, send the subcontractor deliverable pending confirmation information to the general contractor corresponding to the subcontractor deliverable upload request; in response to receiving the confirmation information that matches the subcontractor deliverable pending confirmation information, store the deliverable indicated by the subcontractor deliverable upload request in the pending confirmation deliverable file system corresponding to the digital delivery project, The acknowledgment unit is further configured to: In response to meeting the delivery timing requirements, Searching for deliverables matching the deliverables to be uploaded from the deliverables to be confirmed file system corresponding to the digital delivery project; Generate deliverables to be confirmed information according to the deliverables to be uploaded and the matched deliverables found; The deliverable to-be-acknowledged information is sent to a digital content recipient corresponding to the digital delivery item.

12. An apparatus for digital delivery, comprising: At least one processor, a memory coupled to the at least one processor, and a computer program stored on the memory, wherein the at least one processor executes the computer program to implement the method according to any one of claims 1 to 8.

13. A computer-readable storage medium storing a computer program, wherein the computer program implements the method according to any one of claims 1 to 8 when executed by a processor.

Images