CN111967850A

CN111967850A - Data reporting monitoring method and device and electronic equipment

Info

Publication number: CN111967850A
Application number: CN202010840504.XA
Authority: CN
Inventors: 费宣
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-08-19
Filing date: 2020-08-19
Publication date: 2020-11-20
Anticipated expiration: 2040-08-19
Also published as: CN111967850B

Abstract

The embodiment of the specification provides a data reporting monitoring method and device and electronic equipment. The method comprises the following steps: sensing the delivery behavior of the data delivery client according to a preset sensing rule or a matching rule corresponding to the data delivery client; when the submission behavior is sensed to occur, acquiring a newly added file under a file directory in the data submission client, and taking the newly added file as a submission file corresponding to the submission behavior; or, collecting the message reported by the data reporting client, and acquiring the reporting file corresponding to the reporting behavior from the message; and uploading the reporting behavior information and the reporting file information to a reporting platform server in a preset transmission mode so that the reporting platform server can monitor the data reporting result according to the reporting behavior information and the reporting file information. The technical scheme can be applied to the field of supervision, and monitoring of supervision submission behaviors is achieved.

Description

Data reporting monitoring method and device and electronic equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for monitoring data delivery, and an electronic device.

Background

According to the related requirements of the supervision departments (such as the bank prison, the certificate prison, the national foreign exchange administration, the Chinese people's bank and the like) in China on the supervision of the financial institutions, various business application systems of the institutions such as the external banks and the like need to actively report supervision data to each supervision institution periodically or aperiodically, wherein the system for collecting the business data and reporting the business data to the mouth is called as a supervision reporting system.

Supervision data (such as supervision reports) may relate to a large amount of company core data, and supervision data reporting is a very careful and high-risk action, and in the process of supervision reporting by using a client corresponding to a supervision reporting system, due to the fact that supervision reporting operators in charge of various business systems perform reporting independently, outlets of supervision reporting are relatively dispersed, and when different reporting managers of a plurality of reporting teams perform reporting respectively, operational risks are easy to occur, and therefore problems of missing reporting, late reporting and the like are caused. In addition, the data content reported to the monitoring organization is uncontrollable, and the files reported to the monitoring organization by different reporting clients cannot be completely and accurately mastered.

Based on the prior art, a technical scheme that files reported by different reporting clients to a supervision mechanism can be accurately sensed and collected, so that reporting behaviors of the different reporting clients can be monitored and early warned is provided.

Disclosure of Invention

The embodiment of the specification provides a data delivery monitoring method, a data delivery monitoring device and electronic equipment, and aims to solve the problem that in the prior art, files reported to a supervision organization by different delivery clients cannot be completely and accurately mastered.

In order to solve the above technical problem, the embodiments of the present specification are implemented as follows:

the embodiment of the specification provides a data reporting and monitoring method, which comprises the following steps:

sensing the delivery behavior of the data delivery client according to a preset sensing rule or a matching rule corresponding to the data delivery client;

when the submission behavior is sensed to occur, acquiring a newly added file under a file directory in the data submission client, and taking the newly added file as a submission file corresponding to the submission behavior; or, collecting the message reported by the data reporting client, and acquiring the reporting file corresponding to the reporting behavior from the message;

and uploading the reporting behavior information and the reporting file information to a reporting platform server in a preset transmission mode so that the reporting platform server can monitor the data reporting result according to the reporting behavior information and the reporting file information.

The data report monitoring device provided by the embodiment of the specification comprises:

the sensing module is used for sensing the delivery behavior of the data delivery client according to a pre-configured sensing rule or a matching rule corresponding to the data delivery client;

the acquisition module is used for acquiring a newly added file under a file directory in the data delivery client when the delivery behavior is sensed to occur, and taking the newly added file as a delivery file corresponding to the delivery behavior; or, collecting the message reported by the data reporting client, and acquiring the reporting file corresponding to the reporting behavior from the message;

and the uploading module is used for uploading the reporting behavior information and the reporting file information to the reporting platform server in a preset transmission mode so that the reporting platform server can monitor the data reporting result according to the reporting behavior information and the reporting file information.

An electronic device provided in an embodiment of the present specification includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the above-mentioned data report monitoring method.

The embodiment of the specification adopts at least one technical scheme which can achieve the following beneficial effects:

sensing the submission behavior of the data submission client according to a pre-configured sensing rule or a matching rule corresponding to the data submission client; when the submission behavior is sensed to occur, acquiring a newly added file under a file directory in a data submission client, and taking the newly added file as a submission file corresponding to the submission behavior; or, collecting a message reported by a data reporting client, and acquiring a reporting file corresponding to a reporting behavior from the message; and uploading the reporting behavior information and the reporting file information to a reporting platform server in a preset transmission mode so that the reporting platform server monitors the data reporting result according to the reporting behavior information and the reporting file information. Based on the scheme, the reporting files reported by the data sending clients to the supervision mechanism are sensed and collected by configuring sensing rules or matching rules, and monitoring and early warning of the reporting behaviors of the data sending clients are further realized.

Drawings

In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic diagram of an overall architecture of a platform involved in a practical application scenario according to the solution of the present specification;

fig. 2 is a schematic flow chart of a data reporting monitoring method provided in an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of a data reporting and monitoring device provided in an embodiment of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any inventive step based on the embodiments of the present disclosure, shall fall within the scope of protection of the present application.

As described above, as banking business is widely developed, in order to meet related regulatory requirements, enterprise operation data of an external bank or other organizations needs to be reported to a regulatory organization periodically or aperiodically. There are many different channels for supervisory data reporting, such as: e-mail delivery, C/S client delivery, webpage delivery, offline mail, etc. The operator in charge of reporting the supervision data can select a corresponding reporting channel according to actual requirements to report the supervision data to the supervision organization.

In the prior art, as related supervision departments in the banking industry continuously advance to perfect a supervision system, the requirements related to supervision and delivery are in a gradually rising situation; because the supervision data files (such as supervision reports, supervision reports and the like) may relate to a large amount of core data of companies, and supervision submission is a very careful and high-risk action, in the current collection process of the submission data files, the submission data is generally distributed in a plurality of different business systems (such as the financial data is responsible for the financial department, and the business data is responsible for the corresponding business department); and a plurality of different business departments are respectively responsible for reporting supervision data generated by the business of the department, so when supervision reporting operators responsible for various business systems respectively and independently report, the export of supervision reporting is relatively dispersed, and the problems of report missing, report late and the like caused by operational risks are easy to occur.

In addition, because the requirements of supervision reporting on reporting time points are strict, the collection, reporting and other work of reporting data need to be guaranteed to be completed within a specified time. However, in the existing method of reporting through a distributed outlet, the content reported to the monitoring authority is not controllable, and the content reported to the monitoring authority by all the reporting clients cannot be completely and accurately mastered. Therefore, the reporting behavior of each reporting client cannot be monitored, so that a manager in charge of monitoring reporting cannot know whether numerous reporting files are reported to a monitoring mechanism in time or not, and cannot know whether the reported files have the problems of missing report, wrong report or late report and the like.

Based on the above problems, in the embodiments of the present specification, the configuration file is used to sense and collect the files that are submitted to the monitoring mechanism by different data submitting clients, and the submission behaviors and the submission files of the data submitting clients are returned to the unified submission platform, and all the submission channels that are connected to the monitoring mechanism are closed up in a centralized manner, so that the monitoring and early warning of the submission behaviors of different data submitting clients are realized.

Fig. 1 is a schematic diagram of an overall architecture of a platform related to the technical solution of the present specification in an actual application scenario. The platform overall architecture comprises a data delivery client, a monitoring program client and a delivery platform server; the data delivery client may include a client corresponding to any data delivery channel, for example, a dedicated line C/S client is just one of the channels for delivering by the docking supervisory authority, and the following embodiments of the present specification describe an application scenario in which monitoring and early warning performed by using the C/S client as a delivery behavior of the delivery channel, and certainly the application scenario does not constitute a limitation to the technical solution of the present specification.

One monitoring program client can correspond to a plurality of data reporting clients (such as C/S clients), and different C/S clients can be monitored by one monitoring program client by configuring monitoring configuration files corresponding to different C/S clients in advance in the monitoring program client. The following embodiments of the present specification are described with a monitor client as an execution subject.

The reporting platform server is used for collecting reporting files uploaded by the client side from various different reporting channels, filing and storing the reporting files uploaded by the different reporting channels, analyzing and judging the reporting behaviors and the reporting files of the C/S client side through a reporting file list in the reporting platform server, finding out whether the C/S client side has the problems of missing report, wrong report or late report and the like, and sending a reporting early warning to the C/S client side to avoid loss.

Based on the above-described scenarios, the following describes the embodiments of the present specification in detail.

Fig. 2 is a schematic flow chart of a data reporting monitoring method provided in an embodiment of the present specification, where the method specifically includes the following steps:

in step S210, the delivery behavior of the data delivery client is sensed according to a pre-configured sensing rule or a matching rule corresponding to the data delivery client.

In one or more embodiments of the present specification, the embodiments of the present specification are described by monitoring delivery behavior in a C/S client, and therefore, before describing a monitoring process of delivery behavior of the C/S client in detail, a brief description is first given to the C/S client and a process of delivering a file to a regulatory agency by using the C/S client, where the specific contents are as follows:

the data reporting client can be a data reporting client provided by a monitoring mechanism when a C/S client reporting channel is adopted to report monitoring data, namely the C/S client. The C/S client is a data security server provided by a supervision organization and used for reporting data in a private line, and specified supervision data can be reported through the client; in practical application, the C/S client may adopt, for example, a bank report 1104 client.

The C/S client is a software program client established by adopting a C/S structure, data transmission with a supervision mechanism can be realized on a special network through the C/S client, and an operator in charge of data reporting can directly utilize the C/S client to upload supervision data (namely reporting files) to be reported to the supervision mechanism. In practical application, before the supervision data is uploaded to a supervision organization by using the C/S client, a series of encryption processing can be carried out on the data, so that the safety of data transmission is ensured. The data transmission between the C/S client and the supervision mechanism can be realized based on a transmission channel of an FTP protocol.

In practical application, the C/S clients corresponding to different monitoring authorities are different, and the behaviors generated after the data reporting by the different C/S clients are different, so that the sensing and collecting modes of the reporting behaviors of the C/S clients are not completely the same for different types of the C/S clients, and the following process of sensing the behaviors when the C/S clients report the monitoring data by combining the specific embodiments is described in detail by taking the two types of the C/S clients as an example, and specifically may include the following contents:

for a first type of C/S client, a log file is arranged in the C/S client, and after the C/S client is used for reporting the supervision data, a log corresponding to the reporting action is generated in the C/S client, namely for the C/S client of the type, when the reporting action occurs, a log related to the reporting action is generated in the C/S client, and the name of the reporting file and the date of the reported data are carried in the log; for example, when a report is reported by a certain C/S client, a log file "xxx report with xxx date reported at xxx time" may be generated.

Further, in this embodiment of the present specification, for the C/S client of the first type, the following manner may be adopted to sense the delivery behavior of the data delivery client, and specifically, the following may be included:

when monitoring that the data submission client generates a new log file, executing matching operation on the log file according to the preset matching rule, and judging that the current data submission client performs submission behavior after matching is successful;

and when the submission behavior is judged to occur, extracting the file name corresponding to the submission file and the data date of the submission file from the log file.

Specifically, in this embodiment of the present specification, because a new log is generated when a posting action occurs in a C/S client of this type, a log related to the posting action (i.e., a posting action log) may be matched by monitoring a log file in the C/S client of this type, recording a change of the log file in the C/S client, and matching a name of the log file newly generated in the C/S client by using a preset matching rule. And when the name of the delivery file carried by the delivery behavior log and the data date of the delivery data are successfully matched, determining that the delivery behavior of the current C/S client side occurs, and further collecting the delivery behavior.

In a specific embodiment of the present specification, according to the content of the foregoing embodiment, after the C/S client generates the reporting behavior log, the reporting behavior log may carry the following information, "xxx report on xxx date reported by xxx time"; therefore, according to the format of the information carried by the delivery behavior log, a corresponding matching rule can be configured, for example, the format of the information can be used as a matching rule, and after a content log matched with the format is generated in the C/S client, the C/S client can be considered to have a delivery behavior, so that the sensing of the delivery behavior of the C/S client is realized.

For the second type of C/S client, the C/S client may not generate the delivery log file, but generate a file directory corresponding to the date of the delivery data when the delivery action occurs, and file the delivery file to the bottom of the directory after the delivery file is completely delivered.

Further, in this embodiment of the present specification, for the above-mentioned second type C/S client, the following manner may be adopted to sense the delivery behavior of the data delivery client, and specifically, the following may be included:

monitoring the file directory of the data delivery client or the number of files under the file directory, and judging that the delivery behavior of the data delivery client occurs when the file directory of the data delivery client or the number of files under the file directory changes;

and after the submission behavior is judged to occur, extracting a file directory newly added in the data submission client or a file under the file directory, and extracting a file name corresponding to the submission file and the data date of the submission file from the file directory.

Specifically, in the embodiment of the present specification, since a new file directory is generated when a posting action occurs in a C/S client of this type, it is possible to record a change in the number of files in the file directory in the C/S client by monitoring the file directory in the C/S client of this type, thereby determining whether the posting action occurs in the C/S client; for example, when it is monitored that a newly added or deleted file is in the file directory, it is determined that a delivery action has occurred at the current C/S client, so that the file name of the delivery file and the data date of the delivery file can be further extracted from the file directory.

In a specific embodiment of the present specification, since whether the posting action occurs is determined based on monitoring the change of the number of files in the file directory in the C/S client, a sensing rule may be configured in advance, that is, when it is monitored that the file directory of the datagram client or the number of files in the file directory changes, it is determined that the posting action occurs at the current datagram client.

Based on the content of the technical scheme, the embodiment of the specification realizes the sensing and the collection of the reporting behavior by arranging a universal and configurable log file change monitoring and/or file directory change monitoring tool in the monitoring program client. In practical application, the sensing rule and the matching rule can be preset in the monitoring program client in a configuration file mode, so that the monitoring program client can sense and collect the reporting behavior of the C/S client.

In step S220, when the occurrence of the posting action is sensed, acquiring a newly added file under a file directory in the data posting client, and using the newly added file as the posting file corresponding to the posting action; or, collecting the message reported by the data reporting client, and acquiring the reporting file corresponding to the reporting behavior from the message.

In one or more embodiments of the present specification, after the sensing of the delivery behavior of the C/S client is completed through step S210, a delivery file corresponding to the delivery behavior is further searched for and obtained. Because different C/S clients do not archive file directories in the same manner, the embodiment of the present specification describes in detail the manner of acquiring the file delivered by the C/S client in the following three situations, specifically as follows:

acquiring a file reported by the C/S client under the first condition, wherein the file directory in the C/S client is an archived file directory; therefore, the following method may be adopted to obtain a new file under a file directory in the data delivery client, and use the new file as a delivery file corresponding to the delivery behavior, specifically:

and monitoring the filing file directory in the data delivery client, acquiring a newly added file after monitoring that the newly added file is generated under the filing file directory, and taking the newly added file as a delivery file corresponding to the delivery behavior.

Acquiring the reported file of the C/S client under the second condition, wherein the file directory in the C/S client is a fragmented archived file directory; therefore, the following method may be adopted to obtain a new file under a file directory in the data delivery client, and use the new file as a delivery file corresponding to the delivery behavior, specifically:

and performing monitoring operation on a fragment type filing file directory in the data submission client, acquiring the fragment file after monitoring that a new fragment file is generated under the fragment type filing file directory, performing file splicing operation according to the file sequence number of the fragment file, and taking the spliced file as a submission file corresponding to the submission behavior.

For the acquisition of the delivery file of the C/S client under the third situation, when there is no archive file directory in the C/S client, the delivery file corresponding to the delivery behavior may be acquired from the packet by collecting the packet reported by the data delivery client, specifically:

collecting FTP messages reported by the data reporting client through an FTP protocol, and acquiring reporting files reported by the current data reporting client from the collected FTP messages;

and when the FTP message contains fragment file data, splicing and assembling the acquired fragment file data into a delivery file.

In step S230, the delivery behavior information and the delivery file information are uploaded to the delivery platform server through a predetermined transmission method, so that the delivery platform server monitors the data delivery result according to the delivery behavior information and the delivery file information.

In one or more embodiments of the present disclosure, after the sensing and collecting of the delivery behavior and the obtaining of the delivery file are completed through step S210 and step S220, the delivery behavior and the delivery file may be returned to the delivery platform server, and the delivery behavior of the C/S client is analyzed by the delivery platform server, to determine whether the delivery behavior of the C/S client meets a preset requirement, such as whether there are problems of missed delivery, wrong delivery, late delivery, and the like, and when the above problems occur, a delivery warning is sent to the C/S client, so that an operator who performs data delivery through the C/S client corrects the problems in time.

Further, in the embodiment of the present specification, because the submission file is usually large, and the monitoring program client and the submission platform server are connected through a private network, and the bandwidth of the private network is usually very low (generally about 2M), the embodiment of the present specification provides a custom protocol to implement fragment transmission of the submission file.

The self-defined protocol of the scheme can comprise the following three types of message protocols, and the reporting behavior information and the reporting file information are uploaded to the reporting platform server through the three types of message protocols, wherein the specific transmission process comprises the following contents:

sending a reporting request to the reporting platform server through a first message protocol, wherein the reporting request comprises reporting behavior information and reporting file information;

fragmenting and transmitting the submission file to the submission platform server through a second message protocol;

and transmitting the last fragment file to the delivery platform server through a third message protocol so as to prompt the delivery platform server to check and combine the received fragment files, and filing and storing the combined delivery files by the delivery platform server.

In practical application, the messages of the monitoring program client can be divided into three types, namely an INIT protocol, a CONTENT protocol and an END protocol, namely message protocols corresponding to the three types, wherein the INIT protocol is used for initiating a client reporting request, the reporting request can include reporting behavior information and reporting file information, and the reporting file information can include information such as a file name, a file size and a file fragment number; the CONTENT protocol is used for transmitting the CONTENT of the fragment file, and if the submission file does not need to be fragmented, the END type message protocol is directly transmitted; and the END protocol is used for transmitting the last file fragment, reminding the reporting platform server to check and combine the fragment files and ending the transmission of the reporting request.

In addition, in one or more embodiments of the present specification, after the monitoring program client returns the delivery behavior information and the delivery file information to the delivery platform server through the protocol, the monitoring program client monitors the data delivery result according to the delivery behavior information and the delivery file information, which specifically includes the following contents:

the delivery platform server compares the delivery file list with the delivery behavior information and the delivery file information respectively according to a pre-stored delivery file list, and judges whether the delivery behavior of the data delivery client side meets a preset requirement or not according to a comparison result;

and when the delivery behavior of the data delivery client does not meet the preset requirement, sending a delivery early warning to the data delivery client, wherein the delivery early warning is used for informing the data delivery client of problems generated in the data delivery process.

For example, when a delivery deadline of a delivery action and a file list of all files to be delivered are preset in the delivery platform server, if all the delivery files in the delivery file list uploaded by the monitoring program client are not received within the delivery deadline, a delivery warning is sent to the monitoring program client to notify that there is a risk of overdue or missed delivery of the delivery.

In practical application, the delivery platform server can not only receive the delivery behavior information and the delivery file information generated by monitoring the delivery channels of the C/S client, but also acquire the delivery behavior information and the delivery file information generated by monitoring other delivery channels, so that the delivery platform server can also be considered as a server corresponding to the unified delivery platform.

Based on the same idea, an embodiment of the present specification further provides a data reporting and monitoring device, and as shown in fig. 3, the structural schematic diagram of the data reporting and monitoring device provided in the embodiment of the present specification is shown, where the device 300 mainly includes:

the sensing module 301 is configured to sense a delivery behavior of a data delivery client according to a preconfigured sensing rule or a matching rule corresponding to the data delivery client;

an obtaining module 302, configured to obtain, when it is sensed that the posting action occurs, a newly added file in a file directory in the data posting client, and use the newly added file as a posting file corresponding to the posting action; or, collecting the message reported by the data reporting client, and acquiring the reporting file corresponding to the reporting behavior from the message;

the uploading module 303 is configured to upload the reporting behavior information and the reporting file information to the reporting platform server in a predetermined transmission manner, so that the reporting platform server monitors a data reporting result according to the reporting behavior information and the reporting file information.

An embodiment of the present specification further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the above-mentioned data reporting monitoring method.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiments of the apparatus, the electronic device, and the nonvolatile computer storage medium, since they are substantially similar to the embodiments of the method, the description is simple, and the relevant points can be referred to the partial description of the embodiments of the method.

The apparatus, the electronic device, the nonvolatile computer storage medium and the method provided in the embodiments of the present description correspond to each other, and therefore, the apparatus, the electronic device, and the nonvolatile computer storage medium also have similar advantageous technical effects to the corresponding method.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the various elements may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.

As will be appreciated by one skilled in the art, the present specification embodiments may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of the present specification, and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method of data reporting monitoring, the method comprising:

2. The method of claim 1, wherein the awareness rules include determining that a delivery action is currently performed on the datagram client when a change in a file directory of the datagram client or a change in the number of files in the file directory is monitored.

3. The method of claim 2, wherein sensing the delivery behavior of the data delivery client according to preconfigured sensing rules comprises:

4. The method of claim 1, sensing delivery behavior of a delivery client according to a preconfigured matching rule corresponding to the delivery client, comprising:

5. The method of claim 1, wherein the file directory within the messaging client is an archive file directory;

the acquiring of the newly added file under the file directory in the data submission client, and using the newly added file as the submission file corresponding to the submission behavior, includes:

6. The method of claim 1, wherein the file directory within the messaging client is a tiled archived file directory;

7. The method of claim 1, wherein the collecting the message reported by the data reporting client and acquiring the reporting file corresponding to the reporting action from the message comprises:

8. The method according to claim 1, wherein the predetermined transmission method includes three types of messaging protocols, and the uploading the delivery behavior information and the delivery file information to the delivery platform server through the predetermined transmission method includes:

9. The method of claim 1, wherein the delivery platform server monitors the result of the data delivery according to the delivery behavior information and the delivery file information, and comprises:

10. A datagram monitoring device, the device comprising:

11. The apparatus of claim 10, the perception module further to:

12. The apparatus of claim 10, the perception module further to:

13. The apparatus of claim 10, the file directory within the messaging client being an archive file directory, the obtaining module further to:

14. The apparatus of claim 10, the file directory within the messaging client being a tiled archived file directory, the obtaining module further to:

15. The apparatus of claim 10, the acquisition module further to:

16. The apparatus of claim 10, wherein the predetermined transmission mode comprises three types of messaging protocols, and the upload module is further configured to:

17. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of claims 1 to 9 when executing the program.