CN116777627A - Method, device, equipment and storage medium for processing delivered object - Google Patents

Abstract

The application provides a method, a device, equipment and a storage medium for processing delivered objects. Relates to the technical field of big data. The method comprises the following steps: acquiring service information of each delivery object to be pulled at the current moment, and generating pulling strategy information of each delivery object; judging whether the delivery object in the pull emergency state exists before the delivery deadline of each delivery object arrives; if not, pulling each delivery object from the service end according to the pulling strategy information; if any delivery object in all delivery objects is pulled from the service end and the execution fails, sending information of the pulling failure to the service end; if the execution is successful when the deliveries are pulled from the service end, repeating the steps of acquiring the service information of the deliveries to be pulled at the current moment and generating pulling strategy information of the deliveries according to the service information until all the deliveries are successfully pulled. The method solves the problems that the delivery drawing efficiency is low and the drawing strategy cannot be adjusted according to the actual situation in the prior art.

Description

Method, device, equipment and storage medium for processing delivered object

Technical Field

The present application relates to the field of big data technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing a delivered object.

Background

The current collection of deliveries in the financial field basically adopts a separate push mode and a separate pull mode. The pushing is to provide a delivery platform, so that people of each business group submit delivery on the platform to push, and the pulling is to pull the rear end of the delivery platform to each business group.

The active party of the collection method in the push mode has corresponding deliveries in service groups every time the service triggers/changes, personnel of the service groups need to submit the deliveries when the deliveries exist, and the deliveries of the latest version are submitted to the delivery platform. The initiative of the collection mode of the 'pull' mode is on the collection platform, and the platform can regularly or irregularly get to each service group according to a certain strategy to pull the corresponding delivery object, thereby being convenient for service personnel.

However, the inventors have found that the "push" mode of collection has the disadvantage that the service personnel handle the service while also handling the deliveries, and the workload is multiplied if there are more flows or updates to the flows. The collection mode of the 'pull' mode cannot dynamically adjust the pulling frequency according to actual conditions, and the situation that the delivery deadline is not pulled yet possibly occurs, so that the delivery collection work cannot be completed efficiently and conveniently.

Disclosure of Invention

The application provides a method, a device, equipment and a storage medium for processing a delivered object, which are used for solving the problems that the pulling efficiency of the delivered object is low and the pulling strategy cannot be adjusted according to actual conditions in the prior art.

In a first aspect, the present application provides a method for processing a delivered object, applied to a service device, including: acquiring service information of each delivery object to be pulled at the current moment, and generating pulling strategy information of each delivery object according to the service information; judging whether the delivery object in the pull emergency state exists before the delivery deadline of each delivery object arrives; if the deliveries in the pulling emergency state do not exist, pulling all the deliveries from the service end according to the pulling strategy information; if the execution fails when any delivery object in all delivery objects is pulled from the service end, sending information of pulling failure aiming at any delivery object to the service end; and if the execution is successful when the deliveries are pulled from the service end, repeating the steps of acquiring the service information of the deliveries to be pulled at the current moment and generating the pulling strategy information of the deliveries according to the service information until all the deliveries are successfully pulled.

In one possible design, the service information of each deliverable includes delivery information and delivery information of the deliverable; correspondingly, the generating pulling policy information of each delivery object according to the service information includes: and generating pulling strategy information of each delivery object according to the production information and the delivery information.

In one possible design, wherein the commissioning information includes a commissioning point and a commissioning type for each delivery; the delivery information comprises historical pulling data of each delivery object and delivery deadline date; correspondingly, the generating the pulling policy information of each delivery object according to the production information and the delivery information includes: determining the production quantity of each delivery object according to the production point and the production type; determining preliminary pulling strategy information of each delivery object according to the production quantity and the historical pulling frequency; and determining the number of days from the current moment according to the date of the delivery deadline, and adjusting the preliminary pulling strategy information according to the number of days to obtain the pulling strategy information of each delivery.

In one possible design, the determining whether the deliveries in the pull-out emergency state exist before the delivery deadline of each of the deliveries arrives further includes: and if the delivery object in the pull emergency state exists, pulling the delivery object in the pull emergency state in real time.

In one possible design, the method further comprises: before the delivery deadline of each delivery object arrives, checking whether all delivery objects are pulled; if any delivery object is checked to be not pulled, triggering and executing the operation of pulling the delivery object from the service end once; and if the operation of pulling any delivery object from the service end fails to be executed, sending information of pulling failure aiming at any delivery object to the service end.

In a second aspect, the present application provides a delivery processing apparatus, comprising: the acquisition module is used for acquiring service information of each delivery object to be pulled at the current moment and generating pulling strategy information of each delivery object according to the service information; the judging module is used for judging whether the delivery object in the pulling emergency state exists before the delivery deadline of each delivery object arrives; the pulling module is used for pulling each delivery object from the service end according to the pulling strategy information if the delivery object in the pulling emergency state does not exist; the sending module is used for sending information of pulling failure aiming at any delivery object to the service end if the execution fails when any delivery object is pulled from the service end; and the repeated execution module is used for repeatedly executing the steps of acquiring the service information of each delivery to be pulled at the current moment and generating the pulling strategy information of each delivery according to the service information if the execution is successful when the delivery is pulled from the service end, until all the deliveries are successfully pulled.

In a third aspect, an embodiment of the present application provides a service device, including: at least one processor and memory; the memory stores computer-executable instructions; the at least one processor executes computer-executable instructions stored in the memory, causing the at least one processor to perform the method of handling deliverables as described above in the first aspect and the various possible designs of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored therein computer executable instructions which, when executed by a processor, implement the method for handling deliverables according to the first aspect and the various possible designs of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements the method of handling deliverables as described in the first aspect and the various possible designs of the first aspect.

According to the processing method, the device, the equipment and the storage medium for the deliveries, the service information of each deliverate to be pulled at the current moment is obtained, the pulling strategy information of each deliverate is generated according to the service information, the deliveries are pulled according to the pulling strategy information under the condition that the deliveries in the pulling emergency state do not exist, after the pulling is successful, the new pulling strategy information is generated according to the service information of each deliverate to be pulled at the current moment, the circulation operation is performed until the pulling of all deliveries is successful, the operation of the deliveries at the service end is not needed, the pulling efficiency is improved, and meanwhile, the adjustment of the pulling strategy according to the actual situation is realized.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is an application scenario diagram of a method for processing a delivery object according to an embodiment of the present application;

FIG. 2 is a flowchart of a method for handling deliverables according to an embodiment of the present application;

FIG. 3 is a second flowchart of a method for handling deliverables according to an embodiment of the present application;

FIG. 4 is a third flowchart of a method for handling deliverables according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a handling apparatus for deliveries according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a service device according to an embodiment of the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

In the technical scheme of the application, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the information such as financial data or user data are in accordance with the regulations of related laws and regulations, and the public welfare is not violated.

The current collection of deliveries in the financial field basically adopts a separate push mode and a separate pull mode. The pushing is to provide a delivery platform, so that people of each business group submit delivery on the platform to push, and the pulling is to pull the rear end of the delivery platform to each business group. The active party of the collecting method in the push mode has corresponding deliveries in service groups every time the service triggers/changes, personnel in the service groups need to submit the deliveries when the deliveries exist, and the latest version of the deliveries are submitted to the deliveries platform. The collection mode of the pull mode is that an active party is on a collection platform, the platform can regularly or irregularly pull corresponding delivery objects to each business group according to a certain strategy, so that business personnel are facilitated, but the collection mode is based on the scene that the delivery objects are submitted to be normally distributed or balanced, in actual work, the workload of delivering the delivery objects by day is concentrated and huge, and the mode has the defect that the pull frequency cannot be dynamically adjusted according to actual conditions, so that the condition that the cut-off time is not pulled yet is possible under the extreme condition.

Aiming at the technical problems, the application provides the following technical conception: and generating pulling strategy information of each delivery object, pulling the delivery object according to the pulling strategy information, and generating new pulling strategy information for the rest delivery objects after the pulling is successful until the pulling of all the delivery objects is successful, so that the pulling efficiency is improved, and the pulling strategy of the delivery objects can be dynamically controlled.

The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 1 is an application scenario diagram of a method for processing a delivered object according to an embodiment of the present application. As shown in fig. 1, the application scenario includes: service end 101 and service device 102, wherein service end 101 contains multiple types of deliveries (individual) produced by service group personnel, such as deliveries a, b, c and d in pull emergency state. The service device 102 pulls the deliveries from the service end 101 according to certain pulling policy information.

The service end 101 may be a personal computer, a mobile phone, a tablet computer, a notebook computer, or other computer devices. The server 102 may be a physical server or a cloud server.

Based on the application scenario shown in fig. 1, the embodiment of the application further provides a method for processing the delivered object. Fig. 2 is a flowchart of a method for handling a delivered object according to an embodiment of the present application. The execution subject of the method of the present embodiment may be the service device 102 shown in fig. 1. As shown in fig. 2, the method for processing the delivery object includes:

s201, acquiring service information of each delivery object to be pulled at the current time, and generating pulling strategy information of each delivery object according to the service information.

In this embodiment, the service information of each delivery object includes the delivery information and the delivery information of the delivery object. And generating pulling strategy information of each delivery object according to the production information and the delivery information.

Deliveries in the financial domain may include database data and documents within the financial institution, such as accounting class data, flow data, etc. The process from delivery to delivery of the delivery object contains a lot of information about the delivery object, and according to the information, how to pull each delivery object can be obtained, namely, the pulling strategy information of each delivery object is obtained.

Specifically, the production information comprises production points and production types of all deliveries; the delivery information includes historical pull data for each delivery and delivery deadline.

In the application, the deliveries can be used for the online of all systems in a financial institution, the delivery points of all the deliveries can be understood as the date of the online planning of the set systems, the delivery types comprise daily delivery of a conventional version and agile delivery, and the delivery types determine the types and the quantity of the deliveries. The historical pulling data of each delivery object in the delivery information gives information such as the pulling time node, the pulling time frequency and the like of the same type (or a plurality of) delivery objects in the previous pulling process. The delivery deadline refers to the time deadline when the delivery is made.

S202, judging whether the delivery object in the pull emergency state exists before the delivery deadline of each delivery object arrives, and if not, executing step S203.

In this embodiment, the deliveries in the pull emergency state may refer to the deliveries that need to be immediately subjected to the delivery process, so that the deliveries in the pull emergency state should be immediately pulled, rather than waiting for the next pull to be performed. If the deliveries in the pull emergency state do not exist, all the deliveries can be processed according to the normal pull strategy.

S203, pulling each delivery object from the service end according to the pulling policy information.

In this embodiment, the pulling policy information may include information such as a time node when the service device pulls each delivery object in the service end, a time frequency when the service device pulls each delivery object, and a type and number of the delivery objects to be pulled. The service equipment can accurately and efficiently finish the pulling of the delivery object from the service end according to the information.

S204, judging whether the execution is successful when any delivery object is pulled from the service end, if not, executing step S205, and if so, executing step S206.

In this embodiment, when any delivery object of each delivery object is pulled from the service end, there may be a case that the pulling is unsuccessful, and the service device needs to perform the judgment.

S205, sending information of pull failure aiming at any delivery object to a service end.

In this embodiment, when the service device pulls any delivery object from the service point, the service device does not succeed in pulling, and at this time, the service device needs to feed back information about pull failure of any delivery object to the service end, so that the service end resets the delivery object with pull failure to a state to be pulled, and the situation that the delivery object with pull failure is missed in the next pull process is avoided.

S206, repeatedly executing the steps S201 to S204 until all deliveries are successfully pulled.

In this embodiment, after the execution is successful when any of the deliveries is pulled from the service end in step S204, the service information of each of the deliveries at the service end may have changed, specifically, the delivery point and the delivery type of each of the deliveries in the delivery information, and one or more of the historical pulling data and the delivery deadline date of each of the deliveries in the delivery information may have changed.

Therefore, when the next round of delivery is to be pulled, the service information of each delivery to be pulled at the current moment needs to be acquired, the pulling policy information of each delivery is regenerated, and the pulling operation of the next round of delivery is performed according to the regenerated pulling policy information of each delivery, so that the operation is circulated until all the deliveries are successfully pulled.

In summary, according to the processing method of the deliveries of the embodiment, by acquiring service information of each delivery to be pulled at the current time and generating pulling policy information of each delivery according to the service information, when no deliveries in a pulling emergency state exist, pulling each delivery according to the pulling policy information, generating new pulling policy information according to the service information of each delivery to be pulled at the current time after successful pulling, and performing a cyclic operation until all deliveries are successfully pulled, so that a service end is not required to operate the deliveries, and the pulling policy can be adjusted according to actual conditions while the pulling efficiency is improved.

Fig. 3 is a second flowchart of a method for processing deliveries provided in the embodiment of the present application, where the embodiment provides a specific method for producing pull policy information of each deliveries according to production information and delivery information in the above embodiment. As shown in fig. 3, the method for processing the delivery object comprises the following steps:

s301: determining the production quantity of each delivery object according to the production point and the production type;

in this embodiment, the delivery point of each delivery object is known to be the date on line of the system schedule, and the type of delivery determines the type and number of delivery objects, so that the delivery quantity of each delivery object can be determined according to the delivery point and the delivery type of each delivery object.

S302: determining preliminary pulling strategy information of each delivery object according to the production quantity and the historical pulling data;

in this embodiment, on the premise that the production quantity of the deliveries and the historical pull data are known, the preliminary pull policy information of the deliveries of the current quantity may be generated by referring to the pull policy of the deliveries in the historical pull data.

S303: and determining the number of days from the current moment according to the date of the delivery deadline, and adjusting the preliminary pulling strategy information according to the number of days to obtain the pulling strategy information of each delivery.

In this embodiment, the overall trend of the pull frequency of the deliveries is that the pull frequency is very low at the beginning and is higher as the delivery deadline is approached, so that the preliminary pull policy information can be adjusted according to the days of the delivery deadline from the current time, and the pull frequency of the delivery deadline is gradually increased, so as to obtain the final pull policy information of each deliveries. The specific adjustment method is set according to the actual situation, and the application is not particularly limited.

In summary, according to the processing method of the deliveries of the embodiment, the delivery quantity of each delivery is determined according to the delivery point and the delivery type, the preliminary pulling policy information of each delivery is determined according to the delivery quantity and the historical pulling data, and finally the preliminary pulling policy information is adjusted according to the date of the delivery deadline to obtain the pulling policy information of each delivery, so that the data of each aspect of the deliveries are fully considered, and each type of (each) deliveries can generate the respective optimal pulling policy according to the characteristics of the deliveries.

Fig. 4 is a flowchart III of a method for handling deliverables according to an embodiment of the present application. This embodiment provides another method of handling deliveries. As shown in fig. 4, the method for processing the delivery object comprises the following steps:

s401, acquiring service information of each delivery object to be pulled at the current time, and generating pulling strategy information of each delivery object according to the service information.

S402, judging whether the delivery object in the pull emergency state exists before the delivery deadline of each delivery object arrives, if yes, executing step S403, and if not, executing step S404.

S403, pulling the delivery object in the pulling emergency state in real time.

In this embodiment, the fact that the deliveries in the pull emergency state are known in step S202 may mean that the deliveries need to be immediately delivered, so that the deliveries in the pull emergency state should be pulled in real time, so that the deliveries in the pull emergency state are delivered in time.

S404, pulling each delivery object from the service end according to the pulling policy information.

S405, judging whether the execution is successful when any delivery object is pulled from the service end, if not, executing the step S406, and if so, repeating the step S401.

S406, sending information of pull failure aiming at any delivery object to a service end.

S407, before the delivery deadline of each delivery object arrives, checking whether all delivery objects are pulled.

In this embodiment, each delivery object is delivered by the service device, and in order to accurately complete delivery of each delivery object according to the time limit, it is necessary to ensure that all delivery objects have been pulled from the service end before the delivery deadline of each delivery object arrives, and only then can it be ensured that each delivery object can complete delivery according to the time limit.

And S408, if any delivery object is checked to be not pulled, triggering and executing the operation of pulling the delivery object from the service end once.

In this embodiment, if it is checked that any delivery object has completed pulling before the delivery deadline arrives, it is ensured that delivery can be completed on time before the delivery deadline arrives. If it is checked that any delivery object is not completely pulled before the delivery deadline arrives, it is indicated that the rest delivery object is at the service end, so that the service equipment cannot deliver the delivery object on time, at this time, the operation of pulling the delivery object from the service end once is triggered to be executed, that is, all the rest delivery object at the service end is pulled once instead of pulling according to the pulling policy information produced before, so that the operation can ensure that all delivery objects are pulled before the delivery deadline, and further delivery of the delivery object is completed on time.

S409, judging whether the operation of pulling any delivery object from the service end is successful.

In this embodiment, when any delivery object is pulled from the service end, there may be a case that the pulling is unsuccessful, and the service device needs to perform the judgment.

S410, sending information of pull failure aiming at any delivery object to a service end.

In this embodiment, when the service device pulls any delivery object from the service point, the service device does not pull successfully, and at this time, the service device needs to feed back information of failure in pulling to the service end, so as to remind the service end of which delivery object has not been successfully pulled.

It should be noted that, steps S407 to S410 in fig. 4 may be performed after step S406, or may be performed after other steps in fig. 4, and the embodiment is not particularly limited.

In summary, according to the processing method of the deliveries of the embodiment, by pulling each deliverate according to the pulling policy information until all deliveries are successfully pulled, checking whether all deliveries are pulled before the delivery deadline of each deliverate arrives, and alarming to the service end when the delivery is failed to be pulled, the automatic pulling operation of the deliveries is realized, and the operation and maintenance cost is reduced.

Fig. 5 is a schematic structural diagram of a handling device for deliveries according to an embodiment of the present application. As shown in fig. 5, the delivery processing apparatus includes: an acquisition module 501, a judgment module 502, a first pulling module 503, a sending module 504 and a repeated execution module 505.

The acquiring module 501 is configured to acquire service information of each delivery to be pulled at a current time, and generate pulling policy information of each delivery according to the service information.

A judging module 502, configured to judge whether a delivery object in a pull emergency state exists before the delivery deadline of each delivery object arrives.

The first pulling module 503 is configured to, if there is no deliveries in the emergency state of pulling, pull each deliveries from the service end according to the pulling policy information.

And the sending module 504 is configured to send, to the service end, information about a pull failure for any delivery object if the execution fails when any delivery object of the delivery objects is pulled from the service end.

And the repeated execution module 505 is configured to repeatedly execute the steps of acquiring the service information of each delivery to be pulled at the current time and generating the pulling policy information of each delivery according to the service information if the execution is successful when each delivery is pulled from the service end, until all deliveries are successfully pulled.

In some embodiments, the service information of each deliverable includes delivery information and delivery information of the deliverable, and the obtaining module 501 is further specifically configured to generate pull policy information of each deliverable according to the delivery information and the delivery information.

In some embodiments, the commissioning information includes a commissioning point and a commissioning type for each delivery; the delivery information comprises historical pulling data of each delivery object and delivery deadline date; the obtaining module 501 is further specifically configured to determine a delivery quantity of each delivery object according to a delivery point and a delivery type; determining preliminary pulling strategy information of each delivery object according to the production quantity and the historical pulling frequency; and determining the number of days from the current moment according to the date of the delivery deadline, and adjusting the preliminary pulling strategy information according to the number of days to obtain the pulling strategy information of each delivery.

In some embodiments, the handling device of the deliverables further comprises: a second pull module 506; the second pulling module 506 is configured to pull, in real time, the deliveries in the pull emergency state if the deliveries in the pull emergency state exist.

In some embodiments, the handling device of the deliverables further comprises: an inspection module 507; a checking module 507, configured to check whether all deliveries are pulled out before the delivery deadline of each deliveries arrives; if any delivery object is checked to be not pulled, triggering and executing the operation of pulling the delivery object from the service end once; if the operation execution of pulling any delivery object from the service end fails, sending information of pulling failure aiming at any delivery object to the service end.

The processing device for the delivered object provided by the embodiment of the application can be used for executing the technical scheme of the processing method for the delivered object in the embodiment, and the implementation principle and the technical effect are similar, and are not repeated here.

It should be noted that, it should be understood that the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. For example, the first pulling module 503 may be a processing element that is set up separately, may be implemented in a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program codes, and the functions of the first pulling module 503 may be called and executed by a processing element of the apparatus. The implementation of the other modules is similar. In addition, all or part of the modules can be integrated together or can be independently implemented. The processing element here may be an integrated circuit with 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 a software form.

Fig. 6 is a schematic structural diagram of a service device according to an embodiment of the present application. As shown in fig. 6, the service device may include: a transceiver 601, a processor 602, a memory 603.

Processor 602 executes computer-executable instructions stored in memory, causing processor 602 to perform the aspects of the embodiments described above. The processor 602 may be a general purpose processor including a central processing unit CPU, a network processor (network processor, NP), etc.; but may also be a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.

The memory 603 is coupled to the processor 602 via a system bus and communicates with each other, the memory 603 being adapted to store computer program instructions.

The transceiver 601 may be used to obtain a task to be run and configuration information of the task to be run.

The system bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The system bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus. The transceiver is used to enable communication between the database access device and other computers (e.g., clients, read-write libraries, and read-only libraries). The memory may include random access memory (random access memory, RAM) and may also include non-volatile memory (non-volatile memory).

The service device provided by the embodiment of the present application may be the terminal device of the above embodiment.

The embodiment of the application also provides a chip for running the instruction, which is used for executing the technical scheme of the processing method of the deliverables in the embodiment.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer instructions, and when the computer instructions run on a computer, the computer is caused to execute the technical scheme of the processing method of the delivered object in the embodiment.

The embodiment of the application also provides a computer program product, which comprises a computer program stored in a computer readable storage medium, wherein at least one processor can read the computer program from the computer readable storage medium, and the technical scheme of the processing method of the delivered object in the embodiment can be realized when the at least one processor executes the computer program.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

In addition, each functional module in the embodiments of the present application may be integrated in one processing unit, or each module may exist alone physically, or two or more modules may be integrated in one unit. The units formed by the modules can be realized in a form of hardware or a form of hardware and software functional units.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or processor to perform some of the steps of the methods of the various embodiments of the application.

It should be understood that the above processor may be a central processing unit (Central Processing Unit, abbreviated as CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, abbreviated as DSP), application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as 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 application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.

The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.

The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or to one type of bus.

The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). Of course, the processor and the storage medium may reside as discrete components in an electronic control unit or master control device.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims (10)

1. A method of handling deliverables, applied to a service device, comprising:

acquiring service information of each delivery object to be pulled at the current moment, and generating pulling strategy information of each delivery object according to the service information;

judging whether the delivery object in the pull emergency state exists before the delivery deadline of each delivery object arrives;

if the deliveries in the pulling emergency state do not exist, pulling all the deliveries from the service end according to the pulling strategy information;

if the execution fails when any delivery object in all delivery objects is pulled from the service end, sending information of pulling failure aiming at any delivery object to the service end;

and if the execution is successful when the deliveries are pulled from the service end, repeating the steps of acquiring the service information of the deliveries to be pulled at the current moment and generating the pulling strategy information of the deliveries according to the service information until all the deliveries are successfully pulled.

2. The method of claim 1, wherein the business information for each delivery includes delivery information and delivery information for the delivery;

correspondingly, the generating pulling policy information of each delivery object according to the service information includes:

and generating pulling strategy information of each delivery object according to the production information and the delivery information.

3. The method of claim 2, wherein the commissioning information includes a commissioning point and a commissioning type for each delivery; the delivery information comprises historical pulling data of each delivery object and delivery deadline date;

correspondingly, the generating the pulling policy information of each delivery object according to the production information and the delivery information includes:

determining the production quantity of each delivery object according to the production point and the production type;

determining preliminary pulling strategy information of each delivery object according to the production quantity and the historical pulling data;

and determining the number of days from the current moment according to the date of the delivery deadline, and adjusting the preliminary pulling strategy information according to the number of days to obtain the pulling strategy information of each delivery.

4. The method of claim 1, wherein the determining whether there is a delivery in a pull-out emergency state before the delivery deadline of each delivery arrives further comprises:

and if the delivery object in the pull emergency state exists, pulling the delivery object in the pull emergency state in real time.

5. The method of any one of claims 1-4, further comprising:

before the delivery deadline of each delivery object arrives, checking whether all delivery objects are pulled;

if any delivery object is checked to be not pulled, triggering and executing the operation of pulling the delivery object from the service end once;

and if the operation of pulling any delivery object from the service end fails to be executed, sending information of pulling failure aiming at any delivery object to the service end.

6. A delivery processing apparatus, comprising:

the acquisition module is used for acquiring service information of each delivery object to be pulled at the current moment and generating pulling strategy information of each delivery object according to the service information;

the judging module is used for judging whether the delivery object in the pulling emergency state exists before the delivery deadline of each delivery object arrives;

the first pulling module is used for pulling all deliveries from the service end according to the pulling strategy information if the deliveries in the pulling emergency state do not exist;

the sending module is used for sending information of pulling failure aiming at any delivery object to the service end if the execution fails when any delivery object is pulled from the service end;

and the repeated execution module is used for repeatedly executing the steps of acquiring the service information of each delivery to be pulled at the current moment and generating the pulling strategy information of each delivery according to the service information if the execution is successful when the delivery is pulled from the service end, until all the deliveries are successfully pulled.

7. The apparatus of claim 6, wherein the business information for each delivery includes delivery information and delivery information for the delivery;

correspondingly, the acquisition module is specifically configured to: and generating pulling strategy information of each delivery object according to the production information and the delivery information.

8. A service apparatus, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-5.

9. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1-5.

10. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-5.