WO2019062007A1 - 数据传输方法、装置、终端设备及介质 - Google Patents

数据传输方法、装置、终端设备及介质 Download PDF

Info

Publication number
WO2019062007A1
WO2019062007A1 PCT/CN2018/077247 CN2018077247W WO2019062007A1 WO 2019062007 A1 WO2019062007 A1 WO 2019062007A1 CN 2018077247 W CN2018077247 W CN 2018077247W WO 2019062007 A1 WO2019062007 A1 WO 2019062007A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
uploaded
institution
organization
grouping
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/077247
Other languages
English (en)
French (fr)
Inventor
田正伟
冯超
薛艳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Priority to SG11201809741WA priority Critical patent/SG11201809741WA/en
Priority to US16/088,807 priority patent/US11146571B2/en
Publication of WO2019062007A1 publication Critical patent/WO2019062007A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201—Market modelling; Market analysis; Collecting market data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities

Definitions

  • the present application belongs to the field of data processing technologies, and in particular, to a data transmission method, apparatus, terminal device, and medium.
  • the embodiments of the present application provide a data transmission method, device, terminal device, and medium, to solve the problem of data transmission through serial communication, and low data transmission efficiency.
  • a first aspect of the embodiments of the present application provides a data transmission method, including:
  • the data of the to-be-uploaded business of the institutions with complete audit data in each institution is grouped for the first time;
  • the business data to be uploaded of the institution whose audit data is complete in each institution is uploaded to the system.
  • a second aspect of the embodiments of the present application provides a data transmission apparatus, including:
  • a data acquisition unit configured to acquire service data to be uploaded sent by multiple institutions
  • the identifier obtaining unit is configured to obtain a service identifier carried in the to-be-uploaded business data of the organization that has complete audit data in each institution;
  • a first grouping unit configured to first group the to-be-uploaded business data of the organization that has complete the audit data in each institution according to the obtained business identifier of the organization in which the audit data is complete in each institution;
  • a size determining unit configured to determine a size of the to-be-uploaded business data of the organization that audits the data integrity in each institution;
  • a packet data size determining unit configured to obtain, according to the determined size of the service data to be uploaded of the organization that completes the audit data in each institution, the data size of each packet after the first grouping
  • a second grouping unit configured to perform a second grouping of the grouping result after the first grouping according to a data size of each packet after the first grouping and a preset group of data transmission sizes
  • the data uploading unit is configured to upload the service data to be uploaded of the organization whose audit data is complete in each institution according to the grouping result of the second grouping.
  • a third aspect of the embodiments of the present application provides a data transmission terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing The computer readable instructions implement the following steps:
  • the data of the to-be-uploaded business of the institutions with complete audit data in each institution is grouped for the first time;
  • the business data to be uploaded of the institution whose audit data is complete in each institution is uploaded to the system.
  • a fourth aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions that, when executed by at least one processor, implement the following steps:
  • the data of the to-be-uploaded business of the institutions with complete audit data in each institution is grouped for the first time;
  • the business data to be uploaded of the institution whose audit data is complete in each institution is uploaded to the system.
  • the service data to be uploaded sent by the multiple organizations is obtained, and the service data of the to-be-uploaded service of each organization is checked, and the service identifier carried in the data to be uploaded of the organization with complete audit data is obtained, according to the obtained identification identifier.
  • the organization that audits the complete data performs the first grouping, and then determines the size of the data to be uploaded of the organization that completes the audit data, and further determines the data size of each packet after the first grouping, according to each group after the first grouping.
  • the data size and the preset set of data transmission size, the second grouping of the grouping result after the first grouping, according to the grouping result of the second grouping, the business data to be uploaded of the organization that completes the audit data in each institution Uploading the system can quickly complete data uploading, solve the problem of data transmission through serial communication, and low data transmission efficiency. At the same time, due to data grouping, the requirements for data uploading are reduced, which is suitable for practical applications.
  • FIG. 1 is a schematic flowchart of a data transmission method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data transmission method according to still another embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a data transmission procedure according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a data transmission terminal device according to an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • an angle trigger of a terminal is used as an example.
  • the terminal may be a smart phone or a tablet. Wait for mobile terminals.
  • the processing of the terminal may include the following steps:
  • S101 Acquire service data to be uploaded sent by multiple organizations.
  • the method may further include: detecting whether the connection with the various organizations is normal, and receiving the to-be-uploaded service data sent by each mechanism when detecting that the connection is normal, when detecting that the connection is abnormal The processing is stopped, and the service data to be uploaded sent by each organization is started to be received until the connection is detected to be normal.
  • the method further includes: checking whether the data to be uploaded sent by each organization meets the requirements according to the preset service data requirement, and if the data to be uploaded sent by each organization meets the requirements, Step S102 is performed. Otherwise, the request for re-acquiring data is sent to the organization that fails to meet the requirements, and the data sent by the organization that fails to meet the requirements is received.
  • whether the data to be uploaded is complete can be set according to actual needs, for example, whether the data to be uploaded is non-empty, whether the length limit and the format limit are met.
  • it is an example to review whether the data to be uploaded of each institution is complete that is, to check whether the data to be uploaded of each institution is complete, and receive the data A sent by the organization A and the data B sent by the organization B as an example to review the data to be uploaded. Whether the data A sent by the auditing institution A is complete and whether the data B sent by the auditing institution B is complete.
  • S103 Obtain a service identifier carried in the to-be-uploaded service data of the organization whose audit data is complete in each organization.
  • the service identifier carried in the data to be uploaded may be the name of the service, the label of the service, and the like.
  • the service identifier carried in the service data to be uploaded by the organization A is the service 1
  • the service data to be uploaded by the organization B is carried.
  • the service identifier is business 2 and so on.
  • S104 Perform the first grouping of the to-be-uploaded business data of the organizations with complete audit data in each institution according to the obtained business identifiers of the organizations with complete audit data in each institution.
  • each service identifier may be classified, and the business data to be uploaded of the organization with complete audit data is grouped for the first time according to the classification result, so as to verify the complete data.
  • the organization is the organization A, the organization B, the organization C, and the organization D.
  • the service identifier carried in the service data to be uploaded by the organization A is the service 1
  • the service identifier carried in the service data to be uploaded by the organization B is the service 2
  • the organization C is to be uploaded.
  • the service identifier carried in the service data is the service 1
  • the service identifier carried in the service data to be uploaded by the organization D is the service 4, and the service identifiers of the four organizations are classified.
  • the service 1 is a class and the service 2 is a class.
  • the organization A to be uploaded business data and the organization C to be uploaded business data are grouped into one group
  • the organization B to be uploaded business data and the organization D to be uploaded business data are grouped into one group.
  • S105 Determine the size of the to-be-uploaded business data of the organization whose audit data is complete in each institution.
  • the data size is recorded, and the service data to be uploaded by each organization with complete audit data can be sorted according to the data size, which is convenient for subsequent operations. Data grouping.
  • S106 Obtain a data size of each packet after the first grouping according to the determined size of the service data to be uploaded of the organization whose audit data is complete in each institution.
  • the organization A, the organization B, the organization C, and the organization D are taken as an example, and the size of the service data to be uploaded by the institution A, the institution B, the institution C, and the institution D is determined in step S105, for example, the mechanism.
  • the data to be uploaded by A is 50 megabytes
  • the data to be uploaded by organization B is 30 megabytes
  • the data to be uploaded by organization C is 60 megabytes
  • the data to be uploaded by institution D is 40 megabytes, if the first of the four institutions
  • the result of the sub-grouping is as described in step S104.
  • the data to be uploaded by the organization A and the data to be uploaded by the organization C are grouped into one group.
  • the data size of the group is 110 megabytes
  • the business data to be uploaded by the organization B and the business data to be uploaded by the organization D are Divided into a group, the data size of this group is 70 trillion.
  • S107 Perform a second grouping of the grouping result after the first grouping according to the data size of each packet after the first grouping and the preset data transmission size.
  • the preset data transmission size may be set according to actual conditions, for example, a preset data transmission size is 100 megabytes, or the above-mentioned organization A, organization B, organization C, and organization D are taken as an example, and the organization A is to be uploaded.
  • the data and the information to be uploaded by the organization C are grouped into one group.
  • the data size of the group is 110 megabytes.
  • the data to be uploaded by the organization B and the data to be uploaded by the organization D are grouped into one group.
  • the data size of the group is 70 megabytes.
  • the data size of the organization A to be uploaded and the data to be uploaded by the organization C exceeds 100 megabytes.
  • the data to be uploaded by the organization C and the data to be uploaded by the organization B can be exchanged, that is, the data interchange adjustment between different groups is performed.
  • the adjusted service data of the organization A to be uploaded and the business data to be uploaded by the organization B are grouped into one group.
  • the data size of the group is 80 megabytes
  • the business data to be uploaded by the organization C and the business data to be uploaded by the organization D are grouped into one group.
  • the data size of this group is 100 megabytes, and the size of the two sets of data does not exceed 100 megabytes.
  • S108 Upload the service data to be uploaded of the organization whose audit data is complete in each institution according to the grouping result of the second group.
  • the business data to be uploaded by each institution is uploaded to the system at one time, thereby improving the data uploading efficiency.
  • the method may further include: detecting whether the connection with the system is normal, and when the connection is normal, according to the organization that is inspecting the data in each organization to be uploaded.
  • the result of the grouping of the service data is to upload the service data uploading system of the organization whose audit data is complete in each institution, and stop processing when the connection is abnormal, until the detection connection is normal, and then start uploading the service data of the organization to be uploaded.
  • the data transmission method in the embodiment of the present application can quickly complete data uploading, solve the problem of data transmission through serial communication, and low data transmission efficiency, and reduce data uploading requirements due to data packetization. Suitable for practical applications.
  • FIG. 2 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
  • the difference between the above embodiments in this embodiment is S201 ⁇ S204, where S205 ⁇ S211 are the same as S102 ⁇ S108 in the previous embodiment.
  • S201 Receive a login request sent by multiple institutions, where the login request carries an identity of the organization.
  • the identity of the organization can be set according to actual needs, and can be the name of the organization, the ID of the organization, and the identification number.
  • S202 Find, in the identifier of the pre-stored organization, whether there is an identity identifier carried in the login request sent by multiple organizations. Specifically, the identity of the organization that can be accessed is stored in advance, and whether the identity of the foregoing institution is found in the identity of the pre-stored organization.
  • S203 If the identity of the pre-existing organization finds the identity of the multiple organizations, the step of acquiring the to-be-uploaded service data sent by the multiple organizations is performed.
  • the identity of the foregoing organization is found in the identity of the pre-existing organization, it indicates that each institution is an organization that allows access, and after the access is completed, the service data to be uploaded sent by each institution is obtained.
  • S204 If the identity of the to-be-registered organization is not found in the identifier of the pre-stored organization, the login-inviting institution is denied to log in, and the login failure information is sent to the to-be-registered institution, where the to-be-registered institution sends the login request. Any of a number of institutions. Specifically, if the identity of the organization to be logged in is not found in the identity of the pre-stored organization, the organization to be logged in is not allowed to access, stops processing, and does not establish a connection with the organization to be logged in.
  • FIG. 3 is a schematic flowchart of a data transmission method according to still another embodiment of the present application.
  • the difference between the above embodiments in this embodiment is S301 ⁇ S304, wherein S305 ⁇ S310 are the same as S103 ⁇ S108 in the previous embodiment.
  • S301 Acquire data to be uploaded sent by multiple organizations.
  • S302 Send a prompt to each organization whether the service data to be uploaded is correct.
  • a prompt is sent to each organization whether the service data to be uploaded is correct, and the prompt carries the corresponding service data to be uploaded, and the organization A is used as an example to send a prompt to the organization A whether the service data to be uploaded is correct, and the prompt carrying mechanism The service data to be uploaded sent by A.
  • Steps of separately checking whether the to-be-uploaded service data of each institution is complete is performed, if the information returned by the respective organizations confirming that the service data to be uploaded is correct is received. Specifically, after receiving the information confirmed by the respective organizations to confirm the business data to be uploaded, it is checked whether the data to be uploaded of each institution is complete, and the subsequent processing is performed normally.
  • S304 If receiving the information that is confirmed by the to-be-reviewed organization to confirm that the service data to be uploaded is incorrect, send a service data acquisition request to the to-be-reviewed institution, and receive the new to-be-uploaded service data sent by the to-be-reviewed institution, and execute the The steps of checking whether the data to be uploaded of each institution is complete are respectively reviewed, and the to-be-audited institution is any one of a plurality of organizations that send data to be uploaded.
  • the information to be uploaded by the organization to be audited confirms that the data to be uploaded is incorrect, the new data to be uploaded sent by the organization to be audited is received, and the organization that sends the information confirming the error of the data to be uploaded is resent to be uploaded.
  • the data of the business to be uploaded of each institution is checked for completeness.
  • FIG. 4 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
  • the difference between the above embodiments in this embodiment is S409 ⁇ S411, wherein S401 ⁇ S408 are the same as S101 ⁇ S108 in the previous embodiment.
  • S409 Receive a data upload result returned by the system.
  • S410 If the data uploading result is that the data uploading is successful, sending the data uploading success information to the organization that reviews the data integrity in each institution.
  • S411 If the data uploading result is that the data uploading fails, the step of re-executing the grouping result according to the second grouping by the preset time interval, and the step of uploading the service data uploading system of the organization with the auditing data integrity in each institution .
  • the system After receiving the service data to be uploaded by each system, the system receives the data upload result returned by the system, and if the data upload result is successful data upload, the upload success information is sent to each institution; otherwise, the upload failure information is sent to each institution.
  • the preset time interval is re-according to the grouping result of the service data to be uploaded of each institution, the service data to be uploaded of each institution is uploaded to the system to ensure that the data uploading system is resent when the system fails to receive data, and the data is satisfied.
  • the preset time interval is set as needed, and may be 5 seconds, 10 seconds, or the like.
  • FIG. 5 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
  • the difference between the embodiment corresponding to FIG. 1 is that the checking whether the service data to be uploaded of each institution is complete may be S502.
  • S501 is the same as S101 in the previous embodiment
  • S503 to S508 are the same as S103 to S108 in the previous embodiment.
  • S502 Review whether the data to be uploaded of each organization carries a preset keyword, and separately check whether the format of the data to be uploaded of each institution meets the preset format requirement.
  • the keyword and the format requirement may be preset according to actual needs, and whether the keyword is carried in the service data to be uploaded by each institution, and whether the format of the service data to be uploaded by each institution meets the preset format requirement, for example, each institution uploads
  • the data is used for system certification, and the keywords can be set to include: identity, data name, and so on.
  • the format requirements include: the uploaded data should carry the name field and the identification field.
  • the execution of the data to be uploaded of the organization that completes the audit data in each institution is performed.
  • the steps of carrying the business identity by setting keywords and formats, it is verified whether the data to be uploaded by each institution meets the requirements of subsequent system data processing, and subsequent processing is performed after the verification is passed, so as to ensure the correctness and effectiveness of subsequent data processing, and is suitable for application.
  • FIG. 6 is a schematic diagram showing the operating environment of the data transmission program provided by the embodiment of the present application.
  • the data transmission program 600 is installed and runs in the terminal device 60.
  • the terminal device 60 can be a mobile terminal, a palmtop computer, a server, or the like.
  • the terminal device 60 can include, but is not limited to, a memory 601, a processor 602, and a display 603.
  • the memory 601 may be an internal storage unit of the terminal device 60, such as a hard disk or memory of the terminal device 60, in some embodiments.
  • the memory 601 may also be an external storage device of the terminal device 60 in other embodiments, such as a plug-in hard disk equipped on the terminal device 60, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, flash card, etc.
  • SMC smart memory card
  • secure digital device Secure Digital, SD
  • the memory 601 may also include both an internal storage unit of the terminal device 60 and an external storage device.
  • the memory 601 is configured to store application software and various types of data installed in the terminal device 60, such as program codes of the data transmission program 600.
  • the memory 601 can also be used to temporarily store data that has been output or is about to be output.
  • the processor 602 can be a central processor (Central) in some embodiments A processing unit (CPU), a microprocessor or other data processing chip for running program code or processing data stored in the memory 601, such as executing the data transfer program 600 or the like.
  • Central central processor
  • CPU central processing unit
  • microprocessor microprocessor or other data processing chip for running program code or processing data stored in the memory 601, such as executing the data transfer program 600 or the like.
  • the display 603 may be an LED display, a liquid crystal display, a touch liquid crystal display, and an OLED (Organic) in some embodiments. Light-Emitting Diode, organic light-emitting diodes, etc.
  • the display 603 is used to display information processed in the terminal device 60 and a user interface for displaying visualizations, such as an application menu interface, an application icon interface, and the like.
  • the components 601-603 of the terminal device 60 communicate with one another via a system bus.
  • FIG. 7 is a functional block diagram of a data transmission program 600 provided by an embodiment of the present application.
  • the data transmission program 600 may be divided into a data acquisition unit 701, a complete review unit 702, an identifier acquisition unit 703, a first grouping unit 704, a size determining unit 705, a packet data size determining unit 706, The second grouping unit 707 and the data uploading unit 708.
  • the data obtaining unit 701 is configured to acquire service data to be uploaded sent by multiple institutions.
  • the complete review unit 702 is configured to separately check whether the business data to be uploaded of each institution is complete.
  • the identifier obtaining unit 703 is configured to obtain a service identifier carried in the to-be-uploaded service data of the organization in which the audit data is complete in each institution.
  • the first grouping unit 704 is configured to perform, for the first time, grouping the to-be-uploaded service data of the organization that has complete the audit data in each institution according to the acquired service identifiers of the organizations that have complete the audit data in each institution.
  • the size determining unit 705 is configured to determine the size of the service data to be uploaded of the organization that audits the data integrity in each institution.
  • the packet data size determining unit 706 is configured to obtain the data size of each packet after the first grouping according to the determined size of the service data to be uploaded of the organization that reviews the data integrity in each institution.
  • the second grouping unit 707 is configured to perform the second grouping of the grouping result after the first grouping according to the data size of each packet after the first grouping and the preset group of data transmission sizes.
  • the data uploading unit 708 is configured to upload, according to the grouping result of the second grouping, the to-be-uploaded business data of the organization whose audit data is complete in each institution.
  • the data transmission program 600 may also be divided into a login request receiving unit 709, an identity identification unit 710, and a failure information sending unit 711.
  • the login request receiving unit 709 is configured to receive a login request sent by multiple organizations, where the login request carries an identity of the organization.
  • the identity identifier searching unit 710 is configured to search, in the identity identifier of the pre-stored organization, whether there is an identity identifier carried in the login request sent by multiple organizations.
  • the data obtaining unit 701 is configured to perform the step of acquiring the to-be-uploaded service data sent by the multiple organizations, if the identity of the plurality of organizations is found in the identifier of the pre-stored organization.
  • the failure information sending unit 711 is configured to: if the identity of the to-be-registered organization is not found in the identifier of the pre-stored institution, reject the login of the to-be-registered institution, and send the login failure information to the to-be-registered institution, the to-be-registered
  • the organization is any one of a plurality of organizations that send a login request.
  • the data transmission program 600 may also be divided into a prompt sending unit 712 and a request sending unit 713.
  • the prompt sending unit 712 is configured to send, to each organization, a prompt for whether the service data to be uploaded is correct.
  • the complete review unit 702 is configured to perform, if the information returned by the respective organizations confirming that the service data to be uploaded is correct, perform the steps of separately checking whether the data to be uploaded of each institution is complete.
  • the request sending unit 713 is configured to send a service data acquisition request to the to-be-reviewed institution, and receive a new to-be-uploaded service sent by the to-be-reviewed institution, if receiving the information that is confirmed by the organization to be audited and confirming that the service data to be uploaded is incorrect.
  • the data, the complete review unit 702 performs the steps of separately checking whether the to-be-uploaded service data of each institution is complete, and the to-be-audited institution is any one of a plurality of organizations that send the service data to be uploaded.
  • the data transmission program 600 may also be divided into a result receiving unit 714 and a success information sending unit 715.
  • the result receiving unit 714 is configured to receive a data upload result returned by the system.
  • the success information sending unit 715 is configured to: if the data uploading result is that the data uploading is successful, send the data uploading success information to the organization that audits the data integrity in each institution.
  • the data uploading unit 708 is configured to: if the data uploading result is a data uploading failure, re-execute the grouping result according to the second grouping by using a preset time interval, and the to-be-uploaded service of the organization that completes the auditing data in each institution The steps of the data upload system.
  • the complete review unit 702 is configured to separately check whether the to-be-uploaded service data of each organization carries a preset keyword, and separately check whether the format of the to-be-uploaded service data of each institution meets the preset format requirement.
  • the integrated modules/units if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium.
  • the computer readable instructions when executed by a processor, may implement the steps of the various method embodiments described above.
  • the computer readable instructions comprise computer readable instruction code, which may be in the form of source code, an object code form, an executable file or some intermediate form or the like.
  • the computer readable medium can include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard drive, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read-Only) Memory), random access memory (RAM, Random) Access Memory), electrical carrier signals, telecommunications signals, and software distribution media.
  • ROM Read Only memory
  • RAM Random Access Memory
  • electrical carrier signals telecommunications signals
  • telecommunications signals and software distribution media. It should be noted that the content contained in the computer readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable media Does not include electrical carrier signals and telecommunication signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computing Systems (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Game Theory and Decision Science (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Abstract

本申请适用于数据处理技术领域，提供了一种数据传输方法、装置、终端设备及介质。该方法包括：获取多个机构发送的待上传业务数据；分别审核上述待上传业务数据是否完整；获取审核数据完整的机构的待上传业务数据中携带的业务标识；根据业务标识，对审核数据完整的机构的待上传业务数据进行第一次分组；确定待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；按照第二次分组的分组结果，将审核数据完整的机构的待上传业务数据上传系统，可以快速完成数据上传，解决现有通过串行通信方式进行数据传输，数据传输效率低的问题。

Description

数据传输方法、装置、终端设备及介质
本申请申明享有2017年9月26日递交的申请号为201710880095.4、名称为“数据传输方法及终端设备”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请属于数据处理技术领域，尤其涉及数据传输方法、装置、终端设备及介质。
 背景技术
随着社会进步及科技的发展，互联网技术也得到飞速的发展，尤其是进入互联网+时代后，互联网企业在伴随其业务飞速发展的同时，各个机构需求也越来越复杂且多变，需要传输的数据越来越大。以系统月结制证为例，各个机构需要将需要制证的数据上传到系统，现有数据传输方式为串行通信，即一个机构传输完数据后，下一个机构才能上传数据，如果遇到某个机构传输数据量大，排在该机构后面的其他机构只能排队等候，数据传输效率低，制证周期长，无法满足机构业务需求。
 技术问题
有鉴于此，本申请实施例提供了数据传输方法、装置、终端设备及介质，以解决现有通过串行通信方式进行数据传输，数据传输效率低的问题。
 技术解决方案
本申请实施例的第一方面提供了一种数据传输方法，包括：
获取多个机构发送的待上传业务数据；
分别审核各个机构的待上传业务数据是否完整；
获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
确定各个机构中审核数据完整的机构的待上传业务数据的大小；
根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
本申请实施例的第二方面提供了一种数据传输装置，包括：
数据获取单元，用于获取多个机构发送的待上传业务数据；
完整审核单元，用于分别审核各个机构的待上传业务数据是否完整；
标识获取单元，用于获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
第一分组单元，用于根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
大小确定单元，用于确定各个机构中审核数据完整的机构的待上传业务数据的大小；
分组数据大小确定单元，用于根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
第二分组单元，用于根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
数据上传单元，用于按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
本申请实施例的第三方面，提供了一种数据传输终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
获取多个机构发送的待上传业务数据；
分别审核各个机构的待上传业务数据是否完整；
获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
确定各个机构中审核数据完整的机构的待上传业务数据的大小；
根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
本申请实施例的第四方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，所述计算机可读指令被至少一个处理器执行时实现如下步骤：
获取多个机构发送的待上传业务数据；
分别审核各个机构的待上传业务数据是否完整；
获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
确定各个机构中审核数据完整的机构的待上传业务数据的大小；
根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
 有益效果
本申请实施例，通过获取多个机构发送的待上传业务数据，审核各个机构的待上传业务数据是否完整，获取审核数据完整的机构的待上传业务数据中携带的业务标识，根据获取的标识对审核数据完整的机构进行第一次分组，然后再确定审核数据完整的机构的待上传业务数据的大小，进一步确定第一次分组后每一个分组的数据大小，根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组，按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统，可以快速完成数据上传，解决现有通过串行通信方式进行数据传输，数据传输效率低的问题，同时由于数据分组，降低对数据上传的要求，适合实际应用。
 附图说明
图 1是本申请实施例提供的一种数据传输方法的示意流程图；
图2是本申请另一实施例提供的一种数据传输方法的示意流程图；
图3是本申请再一实施例提供的一种数据传输方法的示意流程图；
图4是本申请又一实施例提供的一种数据传输方法的示意流程图；
图5是本申请又一实施例提供的一种数据传输方法的示意流程图；
图6是本申请实施例提供的一种数据传输程序的示意性框图；
图7是本申请实施例提供的一种数据传输终端设备的示意性框图。
 本发明的实施方式
为了说明本申请所述的技术方案，下面通过具体实施例来进行说明。
参见图1，图1是本申请实施例提供的一种数据传输方法的示意流程图，在该实施例中，是以终端的角度触发为例进行说明，这里，终端可以为智能手机、平板电脑等移动终端。如图1所示，在该实施例中，终端的处理过程可以包括以下步骤：
S101：获取多个机构发送的待上传业务数据。
这里，在获取多个机构发送的待上传业务数据之前，还可以包括：检测与各个机构的连接是否正常，在检测连接正常时，接收各个机构发送的待上传业务数据，在检测连接不正常时，停止处理，直到检测连接正常时才开始接收各个机构发送的待上传业务数据。在获取多个机构发送的待上传业务数据之后，还可以包括：根据预设的业务数据要求审核各个机构发送的待上传业务数据是否符合要求，若审核各个机构发送的待上传业务数据符合要求，执行步骤S102，否则，向审核不符合要求的机构发送再次获取数据的请求，接收审核不符合要求的机构再次发送的数据。
S102：分别审核各个机构的待上传业务数据是否完整。
具体地，审核待上传业务数据是否完整可以根据实际需要设置，例如审核待上传业务数据是否非空，是否满足长度限制和格式限制等。这里，审核各个机构的待上传业务数据是否完整即分别审核每个机构的待上传业务数据是否完整，以接收到机构A发送的数据A和机构B发送的数据B为例，审核待上传业务数据是否完整为审核机构A发送的数据A是否完整，并且审核机构B发送的数据B是否完整。
S103：获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识。具体地，待上传业务数据中携带的业务标识可以为业务的名称、业务的标号等，例如机构A的待上传业务数据中携带的业务标识为业务1，机构B的待上传业务数据中携带的业务标识为业务2等。
S104：根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组。
这里，在获取各个机构中审核数据完整的机构的业务标识后，可以对各个业务标识进行分类，根据分类结果对审核数据完整的机构的待上传业务数据进行第一次分组，以审核数据完整的机构为机构A、机构B、机构C和机构D为例，机构A待上传业务数据中携带的业务标识为业务1，机构B待上传业务数据中携带的业务标识为业务2，机构C待上传业务数据中携带的业务标识为业务1，机构D待上传业务数据中携带的业务标识为业务4，对上述四个机构的业务标识进行分类，业务1为一类，业务2为一类，根据该分类结果，将机构A待上传业务数据与机构C待上传业务数据分为一组，将机构B待上传业务数据与机构D待上传业务数据分为一组。
S105：确定各个机构中审核数据完整的机构的待上传业务数据的大小。
具体地，在确定各个机构中审核数据完整的机构的待上传业务数据的大小后，对各个数据大小进行记录，可以按照数据大小对各个审核数据完整的机构待上传业务数据进行排序，方便后续进行数据分组。
S106：根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小。
这里，还是以上述审核数据完整的机构为机构A、机构B、机构C和机构D为例，步骤S105中确定机构A、机构B、机构C和机构D的待上传业务数据的大小，例如机构A的待上传业务数据是50兆，机构B的待上传业务数据是30兆，机构C的待上传业务数据是60兆，机构D的待上传业务数据是40兆，如果四个机构的第一次分组结果为步骤S104所述，机构A待上传业务数据与机构C待上传业务数据分为一组，该组的数据大小是110兆，将机构B待上传业务数据与机构D待上传业务数据分为一组，该组的数据大小是70兆。
S107：根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组。
具体地，预设一组数据传输大小可以根据实际情况设置，例如预设一组数据传输大小为100兆，还是以上述机构A、机构B、机构C和机构D为例，机构A待上传业务数据与机构C待上传业务数据分为一组，该组的数据大小是110兆，将机构B待上传业务数据与机构D待上传业务数据分为一组，该组的数据大小是70兆，机构A待上传业务数据与机构C待上传业务数据分组的数据大小超过100兆，可以将机构C待上传业务数据与机构B待上传业务数据互换一下，即不同分组之间的数据互换调整一下，调整后机构A待上传业务数据与机构B待上传业务数据分为一组，该组的数据大小是80兆，将机构C待上传业务数据与机构D待上传业务数据分为一组，该组的数据大小是100兆，两组数据的大小均未超过100兆，符合要求，停止调整。
S108：按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。这里，按照分组结果一次性将各个机构待上传业务数据上传至系统，提高数据上传效率。在将各个机构中审核数据完整的机构的待上传业务数据上传系统之前，还可以包括：检测与系统的连接是否正常，在检测连接正常时，按照对各个机构中审核数据完整的机构的待上传业务数据的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统，在检测连接不正常时，停止处理，直到检测连接正常时才开始将机构的待上传业务数据上传系统。
从以上描述可知，本申请实施例的数据传输方法，可以快速完成数据上传，解决现有通过串行通信方式进行数据传输，数据传输效率低的问题，同时由于数据分组，降低对数据上传的要求，适合实际应用。
请参阅图2，图2为本申请另一实施例提供的一种数据传输方法的示意流程图。本实施例上述实施例的区别在于S201~S204，其中S205~S211与上一实施例中的S102~S108相同。
S201：接收多个机构发送的登录请求，所述登录请求携带有机构的身份标识。这里，机构的身份标识可以根据实际需要设置，可以为机构的名称、机构的ID（identification，身份标识号）等。
S202：在预存的机构的身份标识中查找是否有多个机构发送的登录请求中携带的身份标识。具体地，预先存储可以接入的机构的身份标识，在预先存储的机构的身份标识中查找是否有上述机构的身份标识。
S203：若在预存的机构的身份标识查找到多个机构的身份标识，则执行所述获取多个机构发送的待上传业务数据的步骤。这里，若在预存机构的身份标识查找到上述机构的身份标识，说明各个机构是允许接入的机构，在接入完成后，获取各个机构发送的待上传业务数据。
S204：若在预存的机构的身份标识没有查找到待登录机构的身份标识，则拒绝所述待登录机构登录，发送登录失败信息给所述待登录机构，所述待登录机构为发送登录请求的多个机构中的任意一个机构。具体地，若在预存的机构的身份标识没有查找到待登录机构的身份标识，说明待登录机构是不允许接入的机构，停止处理，不与待登录机构建立连接。
请参阅图3，图3为本申请再一实施例提供的一种数据传输方法的示意流程图。本实施例上述实施例的区别在于S301~S304，其中S305~S310与上一实施例中的S103~S108相同。
S301：获取多个机构发送的待上传业务数据。
S302：向各个机构发送一个待上传业务数据是否正确的提示。这里，向各个机构发送一个待上传业务数据是否正确的提示，该提示携带相应的待上传业务数据，以机构A为例，向机构A发送一个待上传业务数据是否正确的提示，该提示携带机构A发送的待上传业务数据。
S303：若接收到各个机构返回的确认待上传业务数据正确的信息，则执行所述分别审核各个机构的待上传业务数据是否完整的步骤。具体地，在接收到各个机构返回的确认待上传业务数据正确的信息后，审核各个机构的待上传业务数据是否完整，保证后续处理正常进行。
S304：若接收到待审核机构返回的确认待上传业务数据错误的信息，则向所述待审核机构发送业务数据获取请求，接收所述待审核机构发送的新的待上传业务数据，执行所述分别审核各个机构的待上传业务数据是否完整的步骤，所述待审核机构为发送待上传业务数据的多个机构中的任意一个机构。这里，若待审核机构返回的确认待上传业务数据错误的信息，则接收待审核机构发送的新的待上传业务数据，在接收到发送确认待上传业务数据错误的信息的机构重新发送的待上传业务数据后，分别审核各个机构的待上传业务数据是否完整。
请参阅图4，图4为本申请又一实施例提供的一种数据传输方法的示意流程图。本实施例上述实施例的区别在于S409~S411，其中S401~S408与上一实施例中的S101~S108相同。
S409：接收所述系统返回的数据上传结果。S410：若所述数据上传结果为数据上传成功，则向各个机构中审核数据完整的机构发送数据上传成功信息。S411：若所述数据上传结果为数据上传失败，则经过预设时间间隔重新执行所述按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统的步骤。
具体地，在系统接收各个机构的待上传业务数据后，接收系统返回的数据上传结果，若该数据上传结果为数据上传成功，发送上传成功信息至各个机构，否则，发送上传失败信息至各个机构，经过预设时间间隔重新按照对各个机构的待上传业务数据的分组结果，将各个机构的待上传业务数据上传系统，保证在系统接收数据失败的情况下，再次发送数据上传系统，满足多种应用场景需要。这里，预设时间间隔根据需要设置，可以为5秒、10秒等。
请参阅图5，图5为本申请又一实施例提供的一种数据传输方法的示意流程图。与图1对应的实施例的区别在于：所述分别审核各个机构的待上传业务数据是否完整可以为S502。其中S501与上一实施例中的S101相同，S503~S508与上一实施例中的S103~S108相同。
S502：分别审核各个机构的待上传业务数据是否携带预设关键字，且分别审核各个机构的待上传业务数据的格式是否符合预设格式要求。这里，可以根据实际需要预先设置关键字和格式要求，校验各个机构待上传业务数据中是否携带有该关键字，各个机构待上传业务数据的格式是否符合预设格式要求，例如，各个机构上传的数据是用于系统制证，可以设置关键字包括：身份标识、数据名称等。设置格式要求包括：上传的数据要携带名称字段和标识字段等。若审核各个机构的待上传业务数据携带预设关键字，且各个机构的待上传业务数据的格式符合预设格式要求，则执行所述获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识的步骤。这里，通过设置关键字和格式，校验各个机构待上传业务数据是否符合后续系统数据处理要求，在校验通过后才进行后续处理，保证后续数据处理的正确性和有效性，适合应用。
对应于上文实施例所述的数据传输方法，图6示出了本申请实施例提供的数据传输程序的运行环境示意图。为了便于说明，仅示出了与本实施例相关的部分。在本实施例中，所述的数据传输程序600安装并运行于终端设备60中。该终端设备60可以是移动终端、掌上电脑、服务器等。该终端设备60可包括，但不仅限于，存储器601、处理器602及显示器603。
所述存储器601在一些实施例中可以是所述终端设备60的内部存储单元，例如该终端设备60的硬盘或内存。所述存储器601在另一些实施例中也可以是所述终端设备60的外部存储设备，例如所述终端设备60上配备的插接式硬盘，智能存储卡（Smart Media Card，SMC），安全数字（Secure Digital，SD）卡，闪存卡（Flash Card）等。进一步地，所述存储器601还可以既包括所述终端设备60的内部存储单元也包括外部存储设备。所述存储器601用于存储安装于所述终端设备60的应用软件及各类数据，例如所述数据传输程序600的程序代码等。所述存储器601还可以用于暂时地存储已经输出或者将要输出的数据。
所述处理器602在一些实施例中可以是一中央处理器（Central Processing Unit，CPU），微处理器或其他数据处理芯片，用于运行所述存储器601中存储的程序代码或处理数据，例如执行所述数据传输程序600等。
所述显示器603在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED（Organic Light-Emitting Diode，有机发光二极管）触摸器等。所述显示器603用于显示在所述终端设备60中处理的信息以及用于显示可视化的用户界面，例如应用菜单界面、应用图标界面等。所述终端设备60的部件601-603通过系统总线相互通信。
请参阅图7，是本申请实施例提供的数据传输程序600的功能模块图。在本实施例中，所述的数据传输程序600可以被分割成数据获取单元701、完整审核单元702、标识获取单元703、第一分组单元704、大小确定单元705、分组数据大小确定单元706、第二分组单元707和数据上传单元708。
其中，数据获取单元701，用于获取多个机构发送的待上传业务数据。完整审核单元702，用于分别审核各个机构的待上传业务数据是否完整。标识获取单元703，用于获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识。第一分组单元704，用于根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组。大小确定单元705，用于确定各个机构中审核数据完整的机构的待上传业务数据的大小。分组数据大小确定单元706，用于根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小。第二分组单元707，用于根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组。数据上传单元708，用于按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
可选的，所述的数据传输程序600还可以被分割成登录请求接收单元709、身份标识查找单元710和失败信息发送单元711。其中，登录请求接收单元709，用于接收多个机构发送的登录请求，所述登录请求携带有机构的身份标识。身份标识查找单元710，用于在预存的机构的身份标识中查找是否有多个机构发送的登录请求中携带的身份标识。数据获取单元701，用于若在预存的机构的身份标识查找到多个机构的身份标识，则执行所述获取多个机构发送的待上传业务数据的步骤。失败信息发送单元711，用于若在预存的机构的身份标识没有查找到待登录机构的身份标识，则拒绝所述待登录机构登录，发送登录失败信息给所述待登录机构，所述待登录机构为发送登录请求的多个机构中的任意一个机构。
可选的，所述的数据传输程序600还可以被分割成提示发送单元712和请求发送单元713。其中，提示发送单元712，用于向各个机构发送一个待上传业务数据是否正确的提示。完整审核单元702，用于若接收到各个机构返回的确认待上传业务数据正确的信息，则执行所述分别审核各个机构的待上传业务数据是否完整的步骤。请求发送单元713，用于若接收到待审核机构返回的确认待上传业务数据错误的信息，则向所述待审核机构发送业务数据获取请求，接收所述待审核机构发送的新的待上传业务数据，完整审核单元702执行所述分别审核各个机构的待上传业务数据是否完整的步骤，所述待审核机构为发送待上传业务数据的多个机构中的任意一个机构。
可选的，所述的数据传输程序600还可以被分割成结果接收单元714和成功信息发送单元715。其中，结果接收单元714，用于接收所述系统返回的数据上传结果。成功信息发送单元715，用于若所述数据上传结果为数据上传成功，则向各个机构中审核数据完整的机构发送数据上传成功信息。数据上传单元708，用于若所述数据上传结果为数据上传失败，则经过预设时间间隔重新执行所述按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统的步骤。
可选的，完整审核单元702，用于分别审核各个机构的待上传业务数据是否携带预设关键字，且分别审核各个机构的待上传业务数据的格式是否符合预设格式要求。
所述集成的模块/单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，也可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一计算机可读存储介质中，该计算机可读指令在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机可读指令包括计算机可读指令代码，所述计算机可读指令代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器（ROM，Read-Only Memory）、随机存取存储器（RAM，Random Access Memory）、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读介质不包括电载波信号和电信信号。

Claims (20)

  1. 一种数据传输方法，其特征在于，包括：
    获取多个机构发送的待上传业务数据；
    分别审核各个机构的待上传业务数据是否完整；
    获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
    根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
    确定各个机构中审核数据完整的机构的待上传业务数据的大小；
    根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
    根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
    按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
  2. 如权利要求1所述的数据传输方法，其特征在于，还包括：
    接收多个机构发送的登录请求，所述登录请求携带有机构的身份标识；
    在预存的机构的身份标识中查找是否有多个机构发送的登录请求中携带的身份标识；
    若在预存的机构的身份标识查找到多个机构的身份标识，则执行所述获取多个机构发送的待上传业务数据的步骤；
    若在预存的机构的身份标识没有查找到待登录机构的身份标识，则拒绝所述待登录机构登录，发送登录失败信息给所述待登录机构，所述待登录机构为发送登录请求的多个机构中的任意一个机构。
  3. 如权利要求1所述的数据传输方法，其特征在于，还包括：
    向各个机构发送一个待上传业务数据是否正确的提示；
    若接收到各个机构返回的确认待上传业务数据正确的信息，则执行所述分别审核各个机构的待上传业务数据是否完整的步骤；
    若接收到待审核机构返回的确认待上传业务数据错误的信息，则向所述待审核机构发送业务数据获取请求，接收所述待审核机构发送的新的待上传业务数据，执行所述分别审核各个机构的待上传业务数据是否完整的步骤，所述待审核机构为发送待上传业务数据的多个机构中的任意一个机构。
  4. 如权利要求1所述的数据传输方法，其特征在于，还包括：
    接收所述系统返回的数据上传结果；
    若所述数据上传结果为数据上传成功，则向各个机构中审核数据完整的机构发送数据上传成功信息；
    若所述数据上传结果为数据上传失败，则经过预设时间间隔重新执行所述按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统的步骤。
  5. 如权利要求1所述的数据传输方法，其特征在于，所述分别审核各个机构的待上传业务数据是否完整包括：
    分别审核各个机构的待上传业务数据是否携带预设关键字，且分别审核各个机构的待上传业务数据的格式是否符合预设格式要求。
  6. 一种数据传输装置，其特征在于，包括：
    数据获取单元，用于获取多个机构发送的待上传业务数据；
    完整审核单元，用于分别审核各个机构的待上传业务数据是否完整；
    标识获取单元，用于获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
    第一分组单元，用于根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
    大小确定单元，用于确定各个机构中审核数据完整的机构的待上传业务数据的大小；
    分组数据大小确定单元，用于根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
    第二分组单元，用于根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
    数据上传单元，用于按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
  7. 根据权利要求6所述的数据传输装置，其特征在于，还包括：
    登录请求接收单元，用于接收多个机构发送的登录请求，所述登录请求携带有机构的身份标识；
    身份标识查找单元，用于在预存的机构的身份标识中查找是否有多个机构发送的登录请求中携带的身份标识；
    数据获取单元，用于若在预存的机构的身份标识查找到多个机构的身份标识，则执行所述获取多个机构发送的待上传业务数据的步骤；
    失败信息发送单元，用于若在预存的机构的身份标识没有查找到待登录机构的身份标识，则拒绝所述待登录机构登录，发送登录失败信息给所述待登录机构，所述待登录机构为发送登录请求的多个机构中的任意一个机构。
  8. 根据权利要求6所述的数据传输装置，其特征在于，还包括：
    提示发送单元，用于向各个机构发送一个待上传业务数据是否正确的提示；
    完整审核单元，用于若接收到各个机构返回的确认待上传业务数据正确的信息，则执行所述分别审核各个机构的待上传业务数据是否完整的步骤；
    请求发送单元，用于若接收到待审核机构返回的确认待上传业务数据错误的信息，则向所述待审核机构发送业务数据获取请求，接收所述待审核机构发送的新的待上传业务数据；
    完整审核单元，用于执行所述分别审核各个机构的待上传业务数据是否完整的步骤，所述待审核机构为发送待上传业务数据的多个机构中的任意一个机构。
  9. 根据权利要求6所述的数据传输装置，其特征在于，还包括：
    结果接收单元，用于接收所述系统返回的数据上传结果；
    成功信息发送单元，用于若所述数据上传结果为数据上传成功，则向各个机构中审核数据完整的机构发送数据上传成功信息；
    数据上传单元，用于若所述数据上传结果为数据上传失败，则经过预设时间间隔重新执行所述按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统的步骤。
  10. 根据权利要求6所述的数据传输装置，其特征在于，所述完整审核单元，用于分别审核各个机构的待上传业务数据是否携带预设关键字，且分别审核各个机构的待上传业务数据的格式是否符合预设格式要求。
  11. 一种数据传输终端设备，其特征在于，包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
    获取多个机构发送的待上传业务数据；
    分别审核各个机构的待上传业务数据是否完整；
    获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
    根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
    确定各个机构中审核数据完整的机构的待上传业务数据的大小；
    根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
    根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
    按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
  12. 根据权利要求11所述的数据传输终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    接收多个机构发送的登录请求，所述登录请求携带有机构的身份标识；
    在预存的机构的身份标识中查找是否有多个机构发送的登录请求中携带的身份标识；
    若在预存的机构的身份标识查找到多个机构的身份标识，则执行所述获取多个机构发送的待上传业务数据的步骤；
    若在预存的机构的身份标识没有查找到待登录机构的身份标识，则拒绝所述待登录机构登录，发送登录失败信息给所述待登录机构，所述待登录机构为发送登录请求的多个机构中的任意一个机构。
  13. 根据权利要求11所述的数据传输终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    向各个机构发送一个待上传业务数据是否正确的提示；
    若接收到各个机构返回的确认待上传业务数据正确的信息，则执行所述分别审核各个机构的待上传业务数据是否完整的步骤；
    若接收到待审核机构返回的确认待上传业务数据错误的信息，则向所述待审核机构发送业务数据获取请求，接收所述待审核机构发送的新的待上传业务数据，执行所述分别审核各个机构的待上传业务数据是否完整的步骤，所述待审核机构为发送待上传业务数据的多个机构中的任意一个机构。
  14. 根据权利要求11所述的数据传输终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    接收所述系统返回的数据上传结果；
    若所述数据上传结果为数据上传成功，则向各个机构中审核数据完整的机构发送数据上传成功信息；
    若所述数据上传结果为数据上传失败，则经过预设时间间隔重新执行所述按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统的步骤。
  15. 根据权利要求11所述的数据传输终端设备，其特征在于，所述分别审核各个机构的待上传业务数据是否完整包括：
    分别审核各个机构的待上传业务数据是否携带预设关键字，且分别审核各个机构的待上传业务数据的格式是否符合预设格式要求。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其特征在于，所述计算机可读指令被至少一个处理器执行时实现如下步骤：
    获取多个机构发送的待上传业务数据；
    分别审核各个机构的待上传业务数据是否完整；
    获取各个机构中审核数据完整的机构的待上传业务数据中携带的业务标识；
    根据获取的各个机构中审核数据完整的机构的业务标识，对各个机构中审核数据完整的机构的待上传业务数据进行第一次分组；
    确定各个机构中审核数据完整的机构的待上传业务数据的大小；
    根据确定的各个机构中审核数据完整的机构的待上传业务数据的大小，获得第一次分组后每一个分组的数据大小；
    根据第一次分组后每一个分组的数据大小和预设一组数据传输大小，对第一次分组后的分组结果进行第二次分组；
    按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统。
  17. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述计算机可读指令被至少一个处理器执行时还实现如下步骤：
    接收多个机构发送的登录请求，所述登录请求携带有机构的身份标识；
    在预存的机构的身份标识中查找是否有多个机构发送的登录请求中携带的身份标识；
    若在预存的机构的身份标识查找到多个机构的身份标识，则执行所述获取多个机构发送的待上传业务数据的步骤；
    若在预存的机构的身份标识没有查找到待登录机构的身份标识，则拒绝所述待登录机构登录，发送登录失败信息给所述待登录机构，所述待登录机构为发送登录请求的多个机构中的任意一个机构。
  18. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述计算机可读指令被至少一个处理器执行时还实现如下步骤：
    向各个机构发送一个待上传业务数据是否正确的提示；
    若接收到各个机构返回的确认待上传业务数据正确的信息，则执行所述分别审核各个机构的待上传业务数据是否完整的步骤；
    若接收到待审核机构返回的确认待上传业务数据错误的信息，则向所述待审核机构发送业务数据获取请求，接收所述待审核机构发送的新的待上传业务数据，执行所述分别审核各个机构的待上传业务数据是否完整的步骤，所述待审核机构为发送待上传业务数据的多个机构中的任意一个机构。
  19. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述计算机可读指令被至少一个处理器执行时还实现如下步骤：
    接收所述系统返回的数据上传结果；
    若所述数据上传结果为数据上传成功，则向各个机构中审核数据完整的机构发送数据上传成功信息；
    若所述数据上传结果为数据上传失败，则经过预设时间间隔重新执行所述按照第二次分组的分组结果，将各个机构中审核数据完整的机构的待上传业务数据上传系统的步骤。
  20. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述分别审核各个机构的待上传业务数据是否完整包括：
    分别审核各个机构的待上传业务数据是否携带预设关键字，且分别审核各个机构的待上传业务数据的格式是否符合预设格式要求。
PCT/CN2018/077247 2017-09-26 2018-02-26 数据传输方法、装置、终端设备及介质 Ceased WO2019062007A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
SG11201809741WA SG11201809741WA (en) 2017-09-26 2018-02-26 Data transmission method, apparatus, terminal device, and medium
US16/088,807 US11146571B2 (en) 2017-09-26 2018-02-26 Data transmission method, apparatus, terminal device, and medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710880095.4A CN107786308B (zh) 2017-09-26 2017-09-26 数据传输方法及终端设备
CN201710880095.4 2017-09-26

Publications (1)

Publication Number Publication Date
WO2019062007A1 true WO2019062007A1 (zh) 2019-04-04

Family

ID=61433691

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077247 Ceased WO2019062007A1 (zh) 2017-09-26 2018-02-26 数据传输方法、装置、终端设备及介质

Country Status (4)

Country Link
US (1) US11146571B2 (zh)
CN (1) CN107786308B (zh)
SG (1) SG11201809741WA (zh)
WO (1) WO2019062007A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111447046B (zh) * 2020-03-26 2023-04-25 广州市百果园信息技术有限公司 业务数据传输方法、装置、设备和存储介质
CN114037196A (zh) * 2021-07-14 2022-02-11 北京天元创新科技有限公司 一种数据质量审核方法及系统
CN113722158B (zh) * 2021-10-08 2022-08-30 亿次网联(杭州)科技有限公司 电子设备及其掉电保护方法、装置、存储介质
CN116781726A (zh) * 2023-07-04 2023-09-19 中国第一汽车股份有限公司 一种信息同步方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070140167A1 (en) * 2005-12-16 2007-06-21 Samsung Electronics Co., Ltd. Apparatus and method for reducing map channel overhead in a broadband wireless communication system
CN105430035A (zh) * 2014-09-18 2016-03-23 腾讯科技（北京）有限公司 一种上传网络数据的方法和装置
CN106576339A (zh) * 2014-06-27 2017-04-19 高通股份有限公司 用于高效支持长期演进上行链路上的可变比特率语音话务的方法和装置
CN107087280A (zh) * 2016-02-16 2017-08-22 中兴通讯股份有限公司 一种数据传输方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931881A (zh) * 2009-06-22 2010-12-29 华为技术有限公司 业务内容同步方法、装置和系统
CN103532909B (zh) * 2012-07-04 2019-01-22 中兴通讯股份有限公司 多流业务并发传输方法、子系统、系统及多接口终端
JP6446995B2 (ja) * 2013-10-29 2019-01-09 株式会社リコー 情報処理システム及び情報処理方法
US9898497B2 (en) * 2015-03-31 2018-02-20 Oracle International Corporation Validating coherency between multiple data sets between database transfers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070140167A1 (en) * 2005-12-16 2007-06-21 Samsung Electronics Co., Ltd. Apparatus and method for reducing map channel overhead in a broadband wireless communication system
CN106576339A (zh) * 2014-06-27 2017-04-19 高通股份有限公司 用于高效支持长期演进上行链路上的可变比特率语音话务的方法和装置
CN105430035A (zh) * 2014-09-18 2016-03-23 腾讯科技（北京）有限公司 一种上传网络数据的方法和装置
CN107087280A (zh) * 2016-02-16 2017-08-22 中兴通讯股份有限公司 一种数据传输方法及装置

Also Published As

Publication number Publication date
US20200314110A1 (en) 2020-10-01
CN107786308B (zh) 2019-05-07
CN107786308A (zh) 2018-03-09
SG11201809741WA (en) 2019-04-29
US11146571B2 (en) 2021-10-12

Similar Documents

Publication Publication Date Title
CN111897842A (zh) 数据校验的方法、装置、计算机系统及介质
US10362086B2 (en) Method and system for automating submission of issue reports
CN113254969B (zh) 业务数据处理方法、装置、电子设备及存储介质
CN106105154B (zh) 数据上载的方法、装置及系统
CN110969417B (zh) 政务事项同步方法、装置、系统、计算机设备和存储介质
WO2019062007A1 (zh) 数据传输方法、装置、终端设备及介质
US20140215301A1 (en) Document template auto discovery
CN112732567B (zh) 基于ip的mock数据测试方法、装置、电子设备及存储介质
US9372916B2 (en) Document template auto discovery
WO2018121266A1 (zh) 一种应用程序获取方法和装置以及一种终端设备
CN110267215A (zh) 一种数据检测方法、设备及存储介质
CN112084114B (zh) 用于测试接口的方法和装置
CN110324361A (zh) 信息认证的方法、装置、计算设备和介质
CN114020689A (zh) 数据处理方法、数据处理装置、电子设备及存储介质
CN113128987B (zh) 信息处理方法、装置、计算机系统及可读存储介质
US20180176781A1 (en) Method and device for managing wireless access point
CN114925337A (zh) 数据的标注方法、装置和电子设备
CN110855718B (zh) 企业用户的注册方法、装置、电子设备及计算机可读介质
CN112163036A (zh) 区块链信息的构建和查询方法及相关装置
CN117130684A (zh) 任务处理方法、代理端创建方法及装置、电子设备
CN111338642B (zh) 确定应用下载途径的方法、设备、终端及存储介质
CN112579553B (zh) 用于记录信息的方法和装置
CN111193595B (zh) 电子签名的错误检测方法、装置、设备和存储介质
CN116128649A (zh) 批量交易的处理方法、装置、设备及存储介质
CN110727945B (zh) 病毒扫描方法、设备以及计算机可读介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18862706

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 24.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18862706

Country of ref document: EP

Kind code of ref document: A1