WO2016074572A1 - 业务数据处理方法、装置及系统 - Google Patents

业务数据处理方法、装置及系统 Download PDF

Info

Publication number
WO2016074572A1
WO2016074572A1 PCT/CN2015/093629 CN2015093629W WO2016074572A1 WO 2016074572 A1 WO2016074572 A1 WO 2016074572A1 CN 2015093629 W CN2015093629 W CN 2015093629W WO 2016074572 A1 WO2016074572 A1 WO 2016074572A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
tag information
receiving device
processing device
receiving
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/CN2015/093629
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.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding 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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to US15/524,591 priority Critical patent/US10642907B2/en
Priority to KR1020177013535A priority patent/KR101978951B1/ko
Priority to EP15858159.5A priority patent/EP3220607B1/en
Priority to SG11201701856PA priority patent/SG11201701856PA/en
Priority to JP2017543868A priority patent/JP6475852B2/ja
Publication of WO2016074572A1 publication Critical patent/WO2016074572A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/226—Delivery according to priorities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/275—Synchronous replication
    • 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/95—Retrieval from the web
    • G06F16/951—Indexing; Web crawling techniques
    • 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/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9538—Presentation of query results
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H04L67/5651—Reducing the amount or size of exchanged application data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682—Policies or rules for updating, deleting or replacing the stored data

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a service data processing method, apparatus, and system.
  • the packets can be sent out at any time, and the receiver cannot determine when the packets will arrive.
  • Asynchronous transmission spreads the synchronization operation to multiple stages, which can greatly reduce the concurrency risk of the system and improve the system efficiency. Therefore, it is widely used, and the asynchronous transmission method also brings the problem of data integrity, that is, the receiver cannot determine the received data. Whether the data arrived is complete. For a service that relies on data integrity, since the receiver cannot determine whether the received data is complete, when the service is performed based on the received data, the service may be failed.
  • aspects of the present application provide a service data processing method, apparatus, and system for determining data integrity and ensuring successful business development.
  • An aspect of the present application provides a service data processing method, including:
  • the receiving device sends a query request carrying the tag information to the processing device, so that the processing device queries whether there is data carrying the tag information locally; and the tag information is used to identify that the receiving device needs to perform the target service. data;
  • the receiving device performs the target service according to the received data carrying the tag information.
  • Another aspect of the present application provides a service data processing method, including:
  • the processing device receives the query request sent by the receiving device, where the query request carries the tag information, where the tag information is used to identify data required by the receiving device to perform the target service;
  • the processing device queries, according to the query request, whether there is data that carries the tag information locally;
  • the processing device sends the query result information to the receiving device, so that the receiving device determines whether to perform the target service according to the query result information.
  • a receiving apparatus including:
  • a sending module configured to send, to the processing device, a query request that carries the tag information, where the processing device queries whether the data that carries the tag information exists locally; the tag information is used to identify the receiving device to perform a target service Required data;
  • a receiving module configured to receive query result information sent by the processing device
  • a service processing module configured to: when the query result information indicates that the processing device does not have data carrying the tag information, perform the target according to data that is received by the receiving module and carries the tag information; business.
  • a processing apparatus including:
  • a receiving module configured to receive a query request sent by the receiving device, where the query request carries tag information, where the tag information is used to identify data required by the receiving device to perform a target service;
  • a querying module configured to query, according to the query request, whether the data carrying the tag information exists locally;
  • a sending module configured to send the query result information of the query module to the receiving device, where the receiving device determines, according to the query result information, whether to perform the target service.
  • a service data processing system includes: a receiving device, a sending device, and a forwarding device;
  • the sending device is configured to generate data carrying the tag information, and send the data carrying the tag information to the forwarding device; the tag information is used to identify data required by the receiving device to perform a target service ;
  • the forwarding device is configured to forward data carrying the tag information to the receiving device, and Receiving, by the receiving device, the query request carrying the tag information, querying whether the data carrying the tag information exists locally according to the query request, and returning query result information to the receiving device;
  • the receiving device is configured to receive data carried by the forwarding device and carry the tag information, and send the query request to the forwarding device, and receive the query result information returned by the forwarding device, and When the query result information indicates that the forwarding device does not locally have the data carrying the tag information, the target service is performed according to the received data carrying the tag information.
  • the receiving device identifies the data required to carry out the target service by using the tag information, and sends a query request carrying the tag information to the processing device, so that the processing device queries whether the data carrying the tag information exists locally and returns the query.
  • the result information is determined according to the query result information returned by the processing device, whether all data required for carrying out the target service, that is, the integrity is received, and if the query result information indicates that the processing device does not have the data carrying the tag information, indicating that the target has been received All the data required for the service, that is, the data carried by the receiving device carrying the tag information is complete, and then the target service is carried out according to the received data carrying the tag information, so that the successful operation can be guaranteed.
  • FIG. 1 is a schematic flowchart of a service data processing method according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a service data processing method according to another embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a message delivery system according to an embodiment of the present disclosure.
  • FIG. 3b is a schematic structural diagram of a receiving apparatus according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic structural diagram of a processing apparatus according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a service data processing system according to an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a service data processing method according to an embodiment of the present application. As shown in Figure 1, the method includes:
  • the receiving device sends a query request carrying the tag information to the processing device, so that the processing device queries whether the data carrying the tag information exists locally; the tag information is used to identify data required by the receiving device to perform the target service.
  • the receiving device receives the query result information sent by the processing device.
  • the receiving device performs the target service according to the received data carrying the tag information.
  • This embodiment provides a service data processing method, which can be executed by a receiving device.
  • the receiving device may be any device that needs to perform services based on data provided by the processing device, and may be, for example, various application clients, servers, or terminal devices.
  • the service carried out by the receiving device is not limited, as long as the service that relies on data integrity belongs to the service in this embodiment.
  • the data required for different services is not the same, but the processing flow is the same for any business.
  • the embodiment is described by taking any service as an example, and the service is referred to as a target service.
  • the data required to carry out the target service is identified by the tag information, that is, the data required to carry out the target service carries the tag information.
  • the processing device is a device responsible for providing data to the receiving device.
  • the processing device transmits data carrying the tag information to the receiving device for the receiving device to perform the target service.
  • the receiving device sends the carrying device to the processing device A query request with tag information for the processing device to query whether there is data carrying tag information locally.
  • a query service is provided, and the query service implements the following functions: receiving a query request sent by the receiving device, obtaining tag information from the query request, querying whether there is data carrying the tag information locally, and querying The result information is provided to the receiving device.
  • the processing device has sent all the data required to carry out the target service to the receiving device before receiving the query request, which means that the processing device does not locally have the data carrying the tag information, and the query result information indicates that the processing device is local. There is no data carrying tag information.
  • the processing device does not send all the data required to carry out the target service to the receiving device before receiving the query request, which means that after receiving the query request, the processing device locally has data carrying the tag information, so The query result information indicates that the processing device locally has data carrying the tag information.
  • the receiving device receives the query result information sent by the processing device, and identifies the query result information; if the query result information indicates that the processing device does not locally have the data carrying the tag information, it means that the received target service is required to be carried out. All the data, that is, the data required to carry out the target business is complete, and the receiving device carries out the target service based on the received data carrying the marked information, so as to ensure the successful implementation of the target business.
  • the query result information indicates that the data that carries the tag information exists locally in the processing device, that is, all the data required to carry out the target service has not been received, that is, the data required for the target service is not complete, and the information may continue.
  • the data carried by the processing device carrying the tag information is sent to perform the target service after receiving all the data required to carry out the target service.
  • the processing device generally transmits various data to the receiving device according to its own scheduling policy, and the various data herein includes data carrying the tag information.
  • the scheduling policy may be a priority policy, and the processing device may sequentially send various data according to priorities of various data.
  • the scheduling policy may be a timing polling policy, and when the receiving device is polled, the data carrying the tag information is transmitted to the receiving device.
  • the processing device may continue to transmit the data carrying the tag information to the receiving device according to its own scheduling policy.
  • This embodiment can facilitate the drop without changing the scheduling strategy of the processing device. Low changes to the processing unit.
  • the receiving device may send a data acquisition request to the processing device to request the processing device to preferentially transmit the data carrying the tag information;
  • the data carrying the tag information may be preferentially transmitted according to the data acquisition request; the receiving device continues to receive the data carrying the tag information sent by the processing device.
  • the implementation method can timely acquire the data required for carrying out the target business, and is beneficial to improving the efficiency and timeliness of carrying out the target business.
  • the processing device may be a device capable of providing data, such as a transmitting device that generates data and provides it to the receiving device.
  • the processing device may be a forwarding device located between the transmitting device and the receiving device responsible for data forwarding, ie receiving data transmitted by the transmitting device and forwarding to the receiving device.
  • the transmitting device may generate data carrying the tag information and receive the data carrying the tag information to the receiving device before receiving the query request.
  • the processing device may receive the data carrying the tag information sent by the receiving device before receiving the query request, and forward the data carrying the tag information to the receiving device according to its own scheduling policy. Before forwarding the data carrying the tag information, the forwarding device may store the data carrying the tag information, for example, the data carrying the tag information may be stored in the database. It should be noted that when the forwarding device forwards the data carrying the tag information to the receiving device, if the data is not successfully forwarded, the unsuccessfully forwarded data is stored for further forwarding.
  • the tag information can be various information that can uniquely identify the data needed to carry out the target service.
  • the tag information may include: an identifier of the receiving device and an identifier of the target service, and the two pieces of information may uniquely identify the target service carried out on the receiving device, and uniquely identify data required to carry out the target service.
  • the marking information may further include: a service type and a time period identifier to which the service for generating the data required for the target service belongs; where the service type may uniquely identify the service that generates the data, that is, the source that can uniquely identify the data, and the time period The time period during which the data required to carry out the target business is identified, and the two pieces of information can also uniquely identify the data required to carry out the target business.
  • T For example, for the data aggregation business involved in the bank, it is generally necessary to T on T+1 day.
  • the data of different business types generated by the day is classified and classified, and the data required for the summary business can be uniquely determined by the service type and the time period identifier.
  • the receiving device identifies the data required to carry out the target service by using the tag information, and sends a query request carrying the tag information to the processing device, so that the processing device queries whether the data carrying the tag information exists locally and returns.
  • Query result information according to the query result information returned by the processing device, determine whether all data required for carrying out the target service, that is, integrity, is received. If the query result information indicates that the processing device does not have data carrying the tag information, the description has been received. All the data required for the target service, that is, the data carried by the receiving device carrying the tag information is complete, and then the target service is carried out according to the received data carrying the tag information, thereby ensuring successful business development and thus improving the business. Performance and efficiency.
  • FIG. 2 is a schematic flowchart of a service data processing method according to another embodiment of the present application. As shown in Figure 2, the method includes:
  • the processing device receives a query request sent by the receiving device, where the query request carries tag information, where the tag information is used to identify data required by the receiving device to perform a target service.
  • the processing device queries, according to the query request, whether the data carrying the tag information exists locally.
  • the processing device sends the query result information to the receiving device, so that the receiving device determines, according to the query result information, whether to perform the target service.
  • This embodiment provides a service data processing method, which can be executed by a processing device.
  • the processing device is the device responsible for providing data to the receiving device.
  • the processing device transmits data carrying the tag information to the receiving device for the receiving device to perform the target service.
  • the receiving device may be any device that needs to perform services based on data provided by the processing device, and may be, for example, various application clients, servers, or terminal devices.
  • the service carried out by the receiving device is not limited, as long as the service that relies on data integrity belongs to the service in this embodiment.
  • the data required for different services is not the same, but the processing flow is the same for any business.
  • the embodiment is described by taking any service as an example, and the service is referred to as a target service.
  • the marking information is used to identify the development target.
  • the data required for the target business that is, the data required to carry out the target business carries the tag information.
  • the processing device cooperates with the receiving device to receive the query request carrying the tag information sent by the receiving device, obtain the tag information from the query request, and query whether the local presence exists.
  • the data carrying the tag information is provided, and the query result information is provided to the receiving device, so that the receiving device can determine whether to perform the target service according to the query result information.
  • the processing device has sent all the data required to carry out the target service to the receiving device before receiving the query request, which means that the processing device does not locally have the data carrying the tag information, and the query result information indicates that the processing device is local. There is no data carrying tag information.
  • the processing device does not send all the data required to carry out the target service to the receiving device before receiving the query request, which means that after receiving the query request, the processing device locally has data carrying the tag information, so The query result information indicates that the processing device locally has data carrying the tag information.
  • the process of determining whether to perform the target service according to the query result information includes: receiving the query result information sent by the processing device, and identifying the query result information; if the query result information indicates that the processing device does not locally have the data carrying the tag information Means that all the data required to carry out the target business, that is, the data required to carry out the target service, is complete, and the receiving device carries out the target service based on the received data carrying the marked information, so as to ensure success. Carry out the target business. If the query result information indicates that the data carrying the tag information exists locally in the processing device, meaning that all the data required for the target service has not been received, that is, the data required for the target service is not complete, the receiving device may continue to send. The data carrying the tag information is used to carry out the target service after receiving all the data required to carry out the target business.
  • the processing device is a forwarding device located between the transmitting device and the receiving device responsible for data forwarding. Based on this, the forwarding device receives the data carrying the tag information sent by the sending device before receiving the query request sent by the receiving device, and forwards the data carrying the tag information to the receiving device according to the local scheduling policy.
  • a specific application scenario such as the messaging system shown in Figure 3a. Taking the messaging system as an example, the processing device can serve as a message center in the messaging system; the transmitting device can serve as a message transmitting end in the messaging system; the receiving device can transmit as the message The message receiver in the system.
  • the message sending end sends a message carrying the tag information to the message center; the message center receives and receives the received message carrying the tag information into the database, and sends the message carrying the tag to the message receiving end according to the local scheduling policy; When the forwarding fails, the message backlog appears in the database.
  • the message receiving end needs to carry out the service, it can query the message center and determine whether to continue the service according to the query result information returned by the message center.
  • the processing device is a transmitting device that generates data and transmits data to the receiving device. Based on this, the transmitting device generates data carrying the tag information before receiving the inquiry request sent by the receiving device, and transmits the data carrying the tag information to the receiving device. For example, the transmitting device may also transmit data carrying the tag information to the receiving device according to the local scheduling policy.
  • the processing device may continue to send the data carrying the tag information to the receiving device according to the local scheduling policy.
  • This embodiment does not require modification of the scheduling strategy of the processing device, and can reduce modifications to the processing device.
  • the processing device may further receive a data acquisition request sent by the receiving device for requesting the processing device to preferentially transmit the data carrying the tag information; the processing device is configured according to The data acquisition request transmits data carrying the tag information to the receiving device.
  • the embodiment can provide data to the receiving device in time, which is beneficial to improving the efficiency and timeliness of the receiving device performing the target service.
  • the processing device herein may be a transmitting device or a forwarding device.
  • the tag information can be various information that can uniquely identify the data needed to carry out the target service.
  • the tag information may include: an identifier of the receiving device and an identifier of the target service, and the two pieces of information may uniquely identify the target service carried out on the receiving device, and uniquely identify data required to carry out the target service.
  • the marking information may further include: a service type and a time period identifier to which the service for generating the data required for the target service belongs; where the service type may uniquely identify the service that generates the data, that is, the source that can uniquely identify the data, and the time period The time period during which the data required to carry out the target business is identified, and the two pieces of information can also uniquely identify the data required to carry out the target business.
  • the processing device cooperates with the receiving device, and receives the query request carrying the tag information sent by the receiving device, and queries whether the data carrying the tag information exists locally and returns the query result information according to the query request, so that The receiving device determines, according to the query result information returned by the processing device, whether all the data, that is, the integrity required for carrying out the target service, is received, and then determining whether to carry out the target service, can ensure successful business development, thereby improving the performance and efficiency of the business.
  • FIG. 3b is a schematic structural diagram of a receiving apparatus according to an embodiment of the present disclosure. As shown in FIG. 3b, the device includes: a sending module 31, a receiving module 32, and a service processing module 33.
  • the sending module 31 is configured to send, to the processing device, a query request that carries the tag information, where the processing device queries whether the data carrying the tag information exists locally; the tag information is used to identify the receiving device to perform the target The data required for the business.
  • the receiving module 32 is configured to receive query result information sent by the processing device.
  • the service processing module 33 is connected to the receiving module 32, and is configured to receive, according to the query result information received by the receiving module 32, that the processing device does not have the data carrying the tag information, according to the The data of the tag information carries out the target service.
  • the sending module 31 is further configured to: when the query result information received by the receiving module 32 indicates that the processing device has data carrying the tag information, send a data acquisition request to the processing device, The data carrying the tag information is preferentially transmitted by requesting the processing device.
  • the receiving module 32 is further configured to continue to receive data that is sent by the processing device and that carries the tag information.
  • the processing device is a forwarding device located between the transmitting device and the receiving device responsible for data forwarding; or the processing device is a transmitting device.
  • the foregoing marking information may include: a service type to which a service for generating data required to perform the target service belongs, and a time period identifier for identifying a time period of data required to perform the target service. .
  • the receiving apparatus may be any apparatus that needs to perform services based on data provided by the processing apparatus, and may be, for example, various application clients, servers, or terminal devices.
  • the receiving device identifies the data required to carry out the target service by using the tag information, and sends a query request carrying the tag information to the processing device, so that the processing device queries whether the data carrying the tag information exists locally and returns.
  • Query result information according to the query result information returned by the processing device, determine whether all data required for carrying out the target service, that is, integrity, is received. If the query result information indicates that the processing device does not have data carrying the tag information, the description has been received. All the data required for the target service, that is, the data carried by the receiving device carrying the tag information is complete, and then the target service is carried out according to the received data carrying the tag information, thereby ensuring successful business development and thus improving the business. Performance and efficiency.
  • FIG. 4 is a schematic structural diagram of a processing apparatus according to an embodiment of the present application. As shown in FIG. 4, the apparatus includes: a receiving module 41, a querying module 42 and a transmitting module 43.
  • the receiving module 41 is configured to receive a query request sent by the receiving device, where the query request carries tag information, where the tag information is used to identify data required by the receiving device to perform a target service.
  • the query module 42 is connected to the receiving module 41, and is configured to query, according to the query request received by the receiving module 41, whether the data carrying the tag information exists locally.
  • the sending module 43 is connected to the query module 42 and configured to send the query result information of the query module 42 to the receiving device, so that the receiving device determines whether to perform the target service according to the query result information.
  • the processing device is a forwarding device located between the transmitting device and the receiving device responsible for data forwarding.
  • the receiving module 41 is further configured to receive data that is sent by the sending device and that carries the tag information.
  • the sending module 43 is further configured to use a local scheduling policy. The data carrying the tag information is forwarded slightly to the receiving device.
  • the processing device is a transmitting device.
  • the sending device further includes: a generating module, configured to generate data carrying the tag information.
  • the sending module 43 is further configured to send data carrying the tag information to the receiving device.
  • the receiving module 41 is further configured to: when the query result information indicates that the processing device has data carrying the tag information, receive, by the receiving device, the request for the process The device preferentially transmits a data acquisition request carrying the data of the tag information.
  • the sending module 43 is further configured to send data carrying the tag information to the receiving device according to the data acquisition request.
  • the foregoing marking information may include: a service type to which a service for generating data required to perform the target service belongs, and a time period identifier for identifying a time period of data required to perform the target service. .
  • the processing device provided in this embodiment cooperates with the receiving device, and receives the query request carrying the tag information sent by the receiving device, and queries whether the data carrying the tag information exists locally and returns the query result information according to the query request, so that The receiving device determines, according to the query result information returned by the processing device, whether all the data, that is, the integrity required for carrying out the target service, is received, and then determining whether to carry out the target service, can ensure successful business development, thereby improving the performance and efficiency of the business.
  • FIG. 5 is a schematic structural diagram of a service data processing system according to an embodiment of the present application. As shown in FIG. 5, the system includes a transmitting device 51, a forwarding device 52, and a receiving device 53.
  • the sending device 51 is configured to generate data carrying the tag information, and send the data carrying the tag information to the forwarding device; the tag information is used to identify data required by the receiving device to perform a target service.
  • the forwarding device 52 is configured to forward data carrying the tag information to the receiving device, and receive a query request that is sent by the receiving device and carry the tag information, and query whether the local presence exists according to the query request. Carrying the data of the tag information and returning the query result information to the receiving device.
  • the receiving device 53 is configured to receive the number of the tag information carried by the forwarding device And sending the query request to the forwarding device, receiving the query result information returned by the forwarding device, and indicating, in the query result information, that the forwarding device does not locally have data carrying the tag information And performing the target service according to the received data carrying the tag information.
  • the sending device, the forwarding device and the receiving device cooperate, and the transmitting device sends the data carrying the tag information to the receiving device through the forwarding device, and the forwarding device receives the query request carrying the tag information sent by the receiving device, Querying, according to the query request, whether the data carrying the tag information exists locally and returning the query result information, so that the receiving device determines, according to the query result information returned by the processing device, whether all data required for carrying out the target service, that is, integrity is received, Determining whether to carry out the target business can ensure successful business development, thereby improving the performance and efficiency of conducting business.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional unit described above is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the methods described in various embodiments of the present application. Part of the steps.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请提供一种业务数据处理方法、装置及系统。一种方法包括：接收装置向处理装置发送携带有标记信息的查询请求，以供处理装置查询本地是否存在携带有标记信息的数据；标记信息用于标识接收装置开展目标业务所需的数据；接收装置接收处理装置发送的查询结果信息；若查询结果信息指示处理装置不存在携带有标记信息的数据，接收装置根据已接收到的携带有标记信息的数据开展目标业务。本申请可以确定数据的完整性，保证成功开展业务。

Description

业务数据处理方法、装置及系统 【技术领域】
本申请涉及通信技术领域，尤其涉及一种业务数据处理方法、装置及系统。
【背景技术】
对于异步传输方式，发送方把数据分组后，可以在任何时候把这些分组发送出去，接收方无法确定这些分组会在什么时候到达。
异步传输把同步操作分散到多个阶段，可以大大降低系统的并发风险，并提高系统效率，因此被大量采用，同时异步传输方式也带来了数据完整性的问题，即接收方无法确定已接收到的数据是否完整。对于依赖于数据完整性的业务，由于接收方无法确定接收到的数据是否完整，所以在基于所接收的数据开展业务时，可能导致业务失败。
【发明内容】
本申请的多个方面提供一种业务数据处理方法、装置及系统，用以确定数据的完整性，保证成功开展业务。
本申请的一方面，提供一种业务数据处理方法，包括：
接收装置向处理装置发送携带有标记信息的查询请求，以供所述处理装置查询本地是否存在携带有所述标记信息的数据；所述标记信息用于标识所述接收装置开展目标业务所需的数据；
所述接收装置接收所述处理装置发送的查询结果信息；
若所述查询结果信息指示所述处理装置不存在携带有所述标记信息的数据，所述接收装置根据已接收到的携带有所述标记信息的数据开展所述目标业务。
本申请的另一方面，提供一种业务数据处理方法，包括：
处理装置接收接收装置发送的查询请求，所述查询请求携带有标记信息，所述标记信息用于标识所述接收装置开展目标业务所需的数据；
所述处理装置根据所述查询请求，查询本地是否存在携带有所述标记信息的数据；
所述处理装置将查询结果信息发送所述接收装置，以供所述接收装置根据所述查询结果信息确定是否开展所述目标业务。
本申请的又一方面，提供一种接收装置，包括：
发送模块，用于向处理装置发送携带有标记信息的查询请求，以供所述处理装置查询本地是否存在携带有所述标记信息的数据；所述标记信息用于标识所述接收装置开展目标业务所需的数据；
接收模块，用于接收所述处理装置发送的查询结果信息；
业务处理模块，用于在所述查询结果信息指示所述处理装置不存在携带有所述标记信息的数据时，根据所述接收模块已接收到的携带有所述标记信息的数据开展所述目标业务。
本申请的又一方面，提供一种处理装置，包括：
接收模块，用于接收接收装置发送的查询请求，所述查询请求携带有标记信息，所述标记信息用于标识所述接收装置开展目标业务所需的数据；
查询模块，用于根据所述查询请求，查询本地是否存在携带有所述标记信息的数据；
发送模块，用于将所述查询模块的查询结果信息发送所述接收装置，以供所述接收装置根据所述查询结果信息确定是否开展所述目标业务。
本申请的又一方面，提供一种业务数据处理系统，包括：接收装置、发送装置和转发装置；
所述发送装置，用于生成携带有标记信息的数据，并将携带有所述标记信息的数据发送给所述转发装置；所述标记信息用于标识所述接收装置开展目标业务所需的数据；
所述转发装置，用于向所述接收装置转发携带有所述标记信息的数据，并 接收所述接收装置发送的携带有所述标记信息的查询请求，根据所述查询请求查询本地是否存在携带有所述标记信息的数据，并向所述接收装置返回查询结果信息；
所述接收装置，用于接收所述转发装置转发的携带有所述标记信息的数据，并向所述转发装置发送所述查询请求，接收所述转发装置返回的所述查询结果信息，并在所述查询结果信息指示所述转发装置本地不存在携带有所述标记信息的数据时，根据已接收到的携带有所述标记信息的数据开展所述目标业务。
在本申请中，接收装置通过标记信息标识开展目标业务所需的数据，并向处理装置发送携带有标记信息的查询请求，以供处理装置查询本地是否存在携带有该标记信息的数据并返回查询结果信息，根据处理装置返回的查询结果信息确定是否接收到开展目标业务所需的所有数据，即完整性，若查询结果信息指示处理装置不存在携带有标记信息的数据，说明已经接收到开展目标业务所需的全部数据，即接收装置接收的携带有标记信息的数据是完整的，于是根据已接收到的携带有标记信息的数据开展目标业务，可以保证成功开展业务。
【附图说明】
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请一实施例提供的业务数据处理方法的流程示意图；
图2为本申请另一实施例提供的业务数据处理方法的流程示意图；
图3a为本申请一实施例提供的消息传送系统的结构示意图；
图3b为本申请一实施例提供的接收装置的结构示意图；
图4为本申请一实施例提供的处理装置的结构示意图；
图5为本申请一实施例提供的业务数据处理系统的结构示意图。
【具体实施方式】
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1为本申请一实施例提供的业务数据处理方法的流程示意图。如图1所示，该方法包括：
101、接收装置向处理装置发送携带有标记信息的查询请求，以供处理装置查询本地是否存在携带有该标记信息的数据；该标记信息用于标识接收装置开展目标业务所需的数据。
102、接收装置接收处理装置发送的查询结果信息。
103、若上述查询结果信息指示处理装置不存在携带有标记信息的数据，接收装置根据已接收到的携带有上述标记信息的数据开展目标业务。
本实施例提供一种业务数据处理方法，可由接收装置来执行。接收装置可以是任何需要基于处理装置提供的数据开展业务的装置,例如可以是各种应用客户端、服务器或终端设备等。
本实施例对接收装置所开展的业务不做限定，只要是依赖于数据完整性的业务均属于本实施例所说的业务。不同业务所需的数据并不相同，但对任何业务来说，其处理流程均相同。为便于描述，本实施例以开展任一业务为例进行说明，并将该业务称为目标业务。在本实施例中，通过标记信息来标识开展目标业务所需的数据，即开展目标业务所需的数据携带有标记信息。
其中，处理装置是负责向接收装置提供数据的装置。处理装置向接收装置发送携带有标记信息的数据，以供接收装置开展目标业务。
为了确定开展目标业务所需的数据的完整性，接收装置向处理装置发送携 带有标记信息的查询请求，以供处理装置查询本地是否存在携带有标记信息的数据。对处理装置来说，提供一种查询服务，该查询服务实现以下功能：接收接收装置发送的查询请求，从查询请求中获取标记信息，查询本地是否存在携带有该标记信息的数据，并将查询结果信息提供给接收装置。
一种情况下，处理装置在接收查询请求之前，已经将开展目标业务所需的数据全部发送给接收装置，意味着处理装置本地不存在携带有标记信息的数据，于是查询结果信息指示处理装置本地不存在携带有标记信息的数据。另一种情况下，处理装置在接收到查询请求之前尚未将开展目标业务所需的数据全部发送给接收装置，意味着接收到查询请求之后，处理装置本地还存在携带有标记信息的数据，于是查询结果信息指示处理装置本地存在携带有标记信息的数据。
基于上述，接收装置接收处理装置发送的查询结果信息，对查询结果信息进行识别；若查询结果信息指示处理装置本地不存在携带有标记信息的数据，意味着已接收到的开展目标业务所需的所有数据，即开展目标业务所需的数据是完整的，于是接收装置根据已接收到的携带有标记信息的数据开展目标业务，这样可以保证成功开展目标业务。
可选的，若上述查询结果信息指示处理装置本地存在携带有标记信息的数据，意味着尚未接收到开展目标业务所需的所有数据，即开展目标业务所需的数据尚不完整，则可以继续接收处理装置发送的携带有标记信息的数据，以便于在接收到开展目标业务所需的所有数据之后，开展目标业务。
处理装置一般是按照自己的调度策略，向接收装置发送各种数据，这里的各种数据包括携带有标记信息的数据。例如，该调度策略可以是优先级策略，则处理装置可以根据各种数据的优先级，依次发送各种数据。又例如，该调度策略可以是定时轮询策略，当轮询到接收装置时，向接收装置发送携带有标记信息的数据。
基于上述，在上述查询结果信息指示处理装置本地存在携带有标记信息的数据的情况下，处理装置可以继续按照自己的调度策略，向接收装置发送携带有标记信息的数据。该实施方式可以不用改动处理装置的调度策略，有利于降 低对处理装置的改动。
或者，在上述查询结果信息指示处理装置本地存在携带有标记信息的数据的情况下，接收装置可以向处理装置发送数据获取请求，以请求处理装置优先发送携带标记信息的数据；基于此，处理装置可以根据数据获取请求，优先发送携带有标记信息的数据；接收装置继续接收处理装置发送的携带有标记信息的数据。该实施方式可以及时获取开展目标业务所需的数据，有利于提高开展目标业务的效率和及时性。
在一可选实施方式中，处理装置可以是能够提供数据的装置，例如可以是产生数据并提供给接收装置的发送装置。或者，处理装置还可以是位于发送装置和接收装置之间负责数据转发，即接收发送装置发送的数据并可以转发给接收装置的转发装置。
若处理装置是发送装置，则发送装置在接收查询请求之前，可以生成携带有标记信息的数据，并向接收装置发送携带有标记信息的数据。
若处理装置是转发装置，则处理装置在接收查询请求之前，可以接收接收装置发送的携带有标记信息的数据，并按照自己的调度策略向接收装置转发携带有标记信息的数据。其中，在转发携带有标记信息的数据之前，转发装置可以存储携带有标记信息的数据，例如可以将携带有标记信息的数据存储到数据库中。值得说明的是，转发装置向接收装置转发携带有标记信息的数据时，若未成功转发该数据，该未被成功转发的数据会被存储起来以便继续转发。
值得说明的是，标记信息可以是各种能够唯一标识开展目标业务所需的数据的信息。例如，该标记信息可以包括：接收装置的标识和目标业务的标识，这两个信息可以唯一标识在接收装置上所开展的目标业务，也就唯一标识了开展目标业务所需的数据。或者，该标记信息还可以包括：产生开展目标业务所需的数据的业务所属的业务类型和时间段标识；这里业务类型可以唯一标识产生数据的业务，即可以唯一标识数据的来源，而时间段标识用于标识开展目标业务所需的数据所在的时间段，通过这两个信息也可以唯一标识出开展目标业务所需的数据。例如：对于银行涉及的数据汇总业务，一般需要在T+1日对T 日产生的不同业务类型的数据进行汇总分类，则可以通过业务类型和时间段标识唯一确定开展汇总业务所需的数据。
在本实施例中，接收装置通过标记信息标识开展目标业务所需的数据，并向处理装置发送携带有标记信息的查询请求，以供处理装置查询本地是否存在携带有该标记信息的数据并返回查询结果信息，根据处理装置返回的查询结果信息确定是否接收到开展目标业务所需的所有数据，即完整性，若查询结果信息指示处理装置不存在携带有标记信息的数据，说明已经接收到开展目标业务所需的全部数据，即接收装置接收的携带有标记信息的数据是完整的，于是根据已接收到的携带有标记信息的数据开展目标业务，可以保证成功开展业务，进而提高了开展业务的性能和效率。
图2为本申请另一实施例提供的业务数据处理方法的流程示意图。如图2所示，该方法包括：
201、处理装置接收接收装置发送的查询请求，该查询请求携带有标记信息，该标记信息用于标识接收装置开展目标业务所需的数据。
202、处理装置根据上述查询请求，查询本地是否存在携带有上述标记信息的数据。
203、处理装置将查询结果信息发送给接收装置，以供接收装置根据查询结果信息确定是否开展目标业务。
本实施例提供一种业务数据处理方法，可由处理装置来执行。处理装置是负责向接收装置提供数据的装置。处理装置向接收装置发送携带有标记信息的数据，以供接收装置开展目标业务。
其中，接收装置可以是任何需要基于处理装置提供的数据开展业务的装置,例如可以是各种应用客户端、服务器或终端设备等。
本实施例对接收装置所开展的业务不做限定，只要是依赖于数据完整性的业务均属于本实施例所说的业务。不同业务所需的数据并不相同，但对任何业务来说，其处理流程均相同。为便于描述，本实施例以开展任一业务为例进行说明，并将该业务称为目标业务。在本实施例中，通过标记信息来标识开展目 标业务所需的数据，即开展目标业务所需的数据携带有标记信息。
为了使接收装置能够确定开展目标业务所需的数据的完整性，处理装置与接收装置相配合，接收接收装置发送的携带有标记信息的查询请求，从查询请求中获取标记信息，查询本地是否存在携带有该标记信息的数据，并将查询结果信息提供给接收装置，使得接收装置可以根据查询结果信息确定是否开展目标业务。
一种情况下，处理装置在接收查询请求之前，已经将开展目标业务所需的数据全部发送给接收装置，意味着处理装置本地不存在携带有标记信息的数据，于是查询结果信息指示处理装置本地不存在携带有标记信息的数据。另一种情况下，处理装置在接收到查询请求之前尚未将开展目标业务所需的数据全部发送给接收装置，意味着接收到查询请求之后，处理装置本地还存在携带有标记信息的数据，于是查询结果信息指示处理装置本地存在携带有标记信息的数据。
基于上述，接收装置根据查询结果信息确定是否开展目标业务的过程包括：接收处理装置发送的查询结果信息，对查询结果信息进行识别；若查询结果信息指示处理装置本地不存在携带有标记信息的数据，意味着已接收到的开展目标业务所需的所有数据，即开展目标业务所需的数据是完整的，于是接收装置根据已接收到的携带有标记信息的数据开展目标业务，这样可以保证成功开展目标业务。若上述查询结果信息指示处理装置本地存在携带有标记信息的数据，意味着尚未接收到开展目标业务所需的所有数据，即开展目标业务所需的数据尚不完整，则可以继续接收处理装置发送的携带有标记信息的数据，以便于在接收到开展目标业务所需的所有数据之后，开展目标业务。
在一可选实施方式中，处理装置是位于发送装置与接收装置之间负责数据转发的转发装置。基于此，转发装置在接收接收装置发送的查询请求之前，接收发送装置发送的携带有标记信息的数据，并根据本地的调度策略向接收装置转发携带有标记信息的数据。一种具体的应用场景，如图3a所示消息传送系统。以消息传送系统为例，处理装置可以作为该消息传送系统中的消息中心；发送装置可以作为该消息传送系统中的消息发送端；接收装置可以作为该消息传送 系统中的消息接收端。消息发送端向消息中心发送携带有标记信息的消息；消息中心接收并将接收的携带有标记信息的消息存储到数据库中，并按照本地的调度策略向消息接收端发送携带有标记的消息；当转发失败时，数据库中会出现消息积压；当消息接收端需要开展业务时，可以向消息中心进行查询，并根据消息中心返回的查询结果信息确定是否继续开展业务。
在另一可选实施方式中，处理装置是产生数据并向接收装置发送数据的发送装置。基于此，发送装置在接收接收装置发送的查询请求之前，生成携带有标记信息的数据，并向接收装置发送携带有标记信息的数据。例如，发送装置也可以根据本地调度策略向接收装置发送携带有标记信息的数据。
基于上述各可选实施方式，在查询结果信息指示处理装置存在携带有标记信息的数据的情况下，处理装置可以继续按照本地调度策略向接收装置发送携带有标记信息的数据。该实施方式不需要改动处理装置的调度策略，可以降低对处理装置的改动。或者，在查询结果信息指示处理装置存在携带有标记信息的数据的情况下，处理装置还可以接收接收装置发送的用于请求处理装置优先发送携带有标记信息的数据的数据获取请求；处理装置根据该数据获取请求，向接收装置发送携带有标记信息的数据。该实施方式可以及时将数据提供给接收装置，有利于提高接收装置开展目标业务的效率和及时性。值得说明的是，这里的处理装置可以是发送装置，也可以是转发装置。
值得说明的是，标记信息可以是各种能够唯一标识开展目标业务所需的数据的信息。例如，该标记信息可以包括：接收装置的标识和目标业务的标识，这两个信息可以唯一标识在接收装置上所开展的目标业务，也就唯一标识了开展目标业务所需的数据。或者，该标记信息还可以包括：产生开展目标业务所需的数据的业务所属的业务类型和时间段标识；这里业务类型可以唯一标识产生数据的业务，即可以唯一标识数据的来源，而时间段标识用于标识开展目标业务所需的数据所在的时间段，通过这两个信息也可以唯一标识出开展目标业务所需的数据。例如：对于银行涉及的数据汇总业务，一般需要在T+1日对T日产生的不同业务类型的数据进行汇总分类，则可以通过业务类型和时间段标 识唯一确定开展汇总业务所需的数据。
在本实施例中，处理装置与接收装置相配合，通过接收接收装置发送的携带有标记信息的查询请求，根据查询请求查询本地是否存在携带有该标记信息的数据并返回查询结果信息，以使接收装置根据处理装置返回的查询结果信息确定是否接收到开展目标业务所需的所有数据，即完整性，进而确定是否开展目标业务，可以保证成功开展业务，进而提高了开展业务的性能和效率。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
图3b为本申请一实施例提供的接收装置的结构示意图。如图3b所示，该装置包括：发送模块31、接收模块32和业务处理模块33。
发送模块31，用于向处理装置发送携带有标记信息的查询请求，以供所述处理装置查询本地是否存在携带有所述标记信息的数据；所述标记信息用于标识所述接收装置开展目标业务所需的数据。
接收模块32，用于接收所述处理装置发送的查询结果信息。
业务处理模块33，与接收模块32连接，用于在接收模块32接收的查询结果信息指示所述处理装置不存在携带有所述标记信息的数据时，根据所述接收模块已接收到的携带有所述标记信息的数据开展所述目标业务。
在一可选实施方式中，发送模块31还用于，在接收模块32接收的查询结果信息指示所述处理装置存在携带有所述标记信息的数据时，向所述处理装置发送数据获取请求，以请求所述处理装置优先发送携带有所述标记信息的数据。相应的，接收模块32还用于，继续接收所述处理装置发送的携带有所述标记信息的数据。
在一可选实施方式中，处理装置是位于发送装置与所述接收装置之间负责数据转发的转发装置；或者，所述处理装置是发送装置。
在一可选实施方式中，上述标记信息可以包括：产生开展所述目标业务所需的数据的业务所属的业务类型和用于标识开展所述目标业务所需的数据所在时间段的时间段标识。
本实施例提供的接收装置可以任何需要基于处理装置提供的数据开展业务的装置,例如可以是各种应用客户端、服务器或终端设备等。
本实施例提供的接收装置，通过标记信息标识开展目标业务所需的数据，并向处理装置发送携带有标记信息的查询请求，以供处理装置查询本地是否存在携带有该标记信息的数据并返回查询结果信息，根据处理装置返回的查询结果信息确定是否接收到开展目标业务所需的所有数据，即完整性，若查询结果信息指示处理装置不存在携带有标记信息的数据，说明已经接收到开展目标业务所需的全部数据，即接收装置接收的携带有标记信息的数据是完整的，于是根据已接收到的携带有标记信息的数据开展目标业务，可以保证成功开展业务，进而提高了开展业务的性能和效率。
图4为本申请一实施例提供的处理装置的结构示意图。如图4所示，该装置包括：接收模块41、查询模块42和发送模块43。
接收模块41，用于接收接收装置发送的查询请求，所述查询请求携带有标记信息，所述标记信息用于标识所述接收装置开展目标业务所需的数据。
查询模块42，与接收模块41连接，用于根据接收模块41接收的查询请求，查询本地是否存在携带有所述标记信息的数据。
发送模块43，与查询模块42连接，用于将所述查询模块42的查询结果信息发送所述接收装置，以供所述接收装置根据所述查询结果信息确定是否开展所述目标业务。
在一可选实施方式中，处理装置是位于发送装置和所述接收装置之间负责数据转发的转发装置。基于此，接收模块41还用于，接收所述发送装置发送的携带有所述标记信息的数据。相应的，发送模块43还用于，根据本地的调度策 略向所述接收装置转发携带有所述标记信息的数据。
在一可选实施方式中，处理装置是发送装置。基于此，该发送装置还包括：生成模块，用于生成携带有所述标记信息的数据。相应的，发送模块43还用于，向所述接收装置发送携带有所述标记信息的数据。
在一可选实施方式中，接收模块41还用于，在所述查询结果信息指示所述处理装置存在携带有所述标记信息的数据时，接收所述接收装置发送的用于请求所述处理装置优先发送携带有所述标记信息的数据的数据获取请求。相应的，发送模块43还用于，根据所述数据获取请求，向所述接收装置发送携带有所述标记信息的数据。
在一可选实施方式中，上述标记信息可以包括：产生开展所述目标业务所需的数据的业务所属的业务类型和用于标识开展所述目标业务所需的数据所在时间段的时间段标识。
本实施例提供的处理装置，与接收装置相配合，通过接收接收装置发送的携带有标记信息的查询请求，根据查询请求查询本地是否存在携带有该标记信息的数据并返回查询结果信息，以使接收装置根据处理装置返回的查询结果信息确定是否接收到开展目标业务所需的所有数据，即完整性，进而确定是否开展目标业务，可以保证成功开展业务，进而提高了开展业务的性能和效率。
图5为本申请一实施例提供的业务数据处理系统的结构示意图。如图5所示，该系统包括：发送装置51、转发装置52和接收装置53。
发送装置51，用于生成携带有标记信息的数据，并将携带有所述标记信息的数据发送给所述转发装置；所述标记信息用于标识所述接收装置开展目标业务所需的数据。
所述转发装置52，用于向所述接收装置转发携带有所述标记信息的数据，并接收所述接收装置发送的携带有所述标记信息的查询请求，根据所述查询请求查询本地是否存在携带有所述标记信息的数据，并向所述接收装置返回查询结果信息。
所述接收装置53，用于接收所述转发装置转发的携带有所述标记信息的数 据，并向所述转发装置发送所述查询请求，接收所述转发装置返回的所述查询结果信息，并在所述查询结果信息指示所述转发装置本地不存在携带有所述标记信息的数据时，根据已接收到的携带有所述标记信息的数据开展所述目标业务。
关于发送装置51、转发装置52和接收装置53的具体工作原理和具体实现结构可参见上述相应方法实施例和装置实施例，在此不再赘述。
本实施例提供的系统，发送装置、转发装置和接收装置相配合，发送装置通过转发装置向接收装置发送携带有标记信息的数据，转发装置通过接收接收装置发送的携带有标记信息的查询请求，根据查询请求查询本地是否存在携带有该标记信息的数据并返回查询结果信息，以使接收装置根据处理装置返回的查询结果信息确定是否接收到开展目标业务所需的所有数据，即完整性，进而确定是否开展目标业务，可以保证成功开展业务，进而提高了开展业务的性能和效率。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (20)

  1. 一种业务数据处理方法，其特征在于，包括：
    接收装置向处理装置发送携带有标记信息的查询请求，以供所述处理装置查询本地是否存在携带有所述标记信息的数据；所述标记信息用于标识所述接收装置开展目标业务所需的数据；
    所述接收装置接收所述处理装置发送的查询结果信息；
    若所述查询结果信息指示所述处理装置不存在携带有所述标记信息的数据，所述接收装置根据已接收到的携带有所述标记信息的数据开展所述目标业务。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    若所述查询结果信息指示所述处理装置存在携带有所述标记信息的数据，所述接收装置向所述处理装置发送数据获取请求，以请求所述处理装置优先发送携带有所述标记信息的数据；
    所述接收装置继续接收所述处理装置发送的携带有所述标记信息的数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述处理装置是位于发送装置与所述接收装置之间负责数据转发的转发装置；或者
    所述处理装置是发送装置。
  4. 根据权利要求1或2所述的方法，其特征在于，所述标记信息包括：产生开展所述目标业务所需的数据的业务所属的业务类型和用于标识开展所述目标业务所需的数据所在时间段的时间段标识。
  5. 一种业务数据处理方法，其特征在于，包括：
    处理装置接收接收装置发送的查询请求，所述查询请求携带有标记信息，所述标记信息用于标识所述接收装置开展目标业务所需的数据；
    所述处理装置根据所述查询请求，查询本地是否存在携带有所述标记信息的数据；
    所述处理装置将查询结果信息发送所述接收装置，以供所述接收装置根据 所述查询结果信息确定是否开展所述目标业务。
  6. 根据权利要求5所述的方法，其特征在于，所述处理装置是位于发送装置和所述接收装置之间负责数据转发的转发装置；
    所述处理装置接收接收装置发送的查询请求之前，包括：
    所述转发装置接收所述发送装置发送的携带有所述标记信息的数据，并根据本地的调度策略向所述接收装置转发。
  7. 根据权利要求5所述的方法，其特征在于，所述处理装置为发送装置；
    所述处理装置接收接收装置发送的查询请求之前，包括：
    所述发送装置生成携带有所述标记信息的数据，并向所述接收装置发送携带有所述标记信息的数据。
  8. 根据权利要求5或6或7所述的方法，其特征在于，若所述查询结果信息指示所述处理装置存在携带有所述标记信息的数据，所述方法还包括：
    所述处理装置接收所述接收装置发送的用于请求所述处理装置优先发送携带有所述标记信息的数据的数据获取请求；
    所述处理装置根据所述数据获取请求，向所述接收装置发送携带有所述标记信息的数据。
  9. 根据权利要求5或6或7所述的方法，其特征在于，所述标记信息包括：产生开展所述目标业务所需的数据的业务所属的业务类型和用于标识开展所述目标业务所需的数据所在时间段的时间段标识。
  10. 一种接收装置，其特征在于，包括：
    发送模块，用于向处理装置发送携带有标记信息的查询请求，以供所述处理装置查询本地是否存在携带有所述标记信息的数据；所述标记信息用于标识所述接收装置开展目标业务所需的数据；
    接收模块，用于接收所述处理装置发送的查询结果信息；
    业务处理模块，用于在所述查询结果信息指示所述处理装置不存在携带有所述标记信息的数据时，根据所述接收模块已接收到的携带有所述标记信息的数据开展所述目标业务。
  11. 根据权利要求10所述的装置，其特征在于，
    所述发送模块还用于，在所述查询结果信息指示所述处理装置存在携带有所述标记信息的数据时，向所述处理装置发送数据获取请求，以请求所述处理装置优先发送携带有所述标记信息的数据；
    接收模块还用于，继续接收所述处理装置发送的携带有所述标记信息的数据。
  12. 根据权利要求10或11所述的装置，其特征在于，所述处理装置是位于发送装置与所述接收装置之间负责数据转发的转发装置；或者
    所述处理装置是发送装置。
  13. 根据权利要求10或11所述的装置，其特征在于，所述标记信息包括：产生开展所述目标业务所需的数据的业务所属的业务类型和用于标识开展所述目标业务所需的数据所在时间段的时间段标识。
  14. 一种处理装置，其特征在于，包括：
    接收模块，用于接收接收装置发送的查询请求，所述查询请求携带有标记信息，所述标记信息用于标识所述接收装置开展目标业务所需的数据；
    查询模块，用于根据所述查询请求，查询本地是否存在携带有所述标记信息的数据；
    发送模块，用于将所述查询模块的查询结果信息发送所述接收装置，以供所述接收装置根据所述查询结果信息确定是否开展所述目标业务。
  15. 根据权利要求14所述的装置，其特征在于，所述处理装置是位于发送装置和所述接收装置之间负责数据转发的转发装置；
    所述接收模块还用于，接收所述发送装置发送的携带有所述标记信息的数据；
    所述发送模块还用于，根据本地的调度策略向所述接收装置转发携带有所述标记信息的数据。
  16. 根据权利要求14所述的装置，其特征在于，所述处理装置为发送装置；
    所述发送装置还包括：
    生成模块，用于生成携带有所述标记信息的数据；
    所述发送模块还用于，向所述接收装置发送携带有所述标记信息的数据。
  17. 根据权利要求14或15或16所述的装置，其特征在于，
    所述接收模块还用于，在所述查询结果信息指示所述处理装置存在携带有所述标记信息的数据时，接收所述接收装置发送的用于请求所述处理装置优先发送携带有所述标记信息的数据的数据获取请求；
    所述发送模块还用于，根据所述数据获取请求，向所述接收装置发送携带有所述标记信息的数据。
  18. 根据权利要求14或15或16所述的装置，其特征在于，所述标记信息包括：产生开展所述目标业务所需的数据的业务所属的业务类型和用于标识开展所述目标业务所需的数据所在时间段的时间段标识。
  19. 一种业务数据处理系统，其特征在于，包括：接收装置、发送装置和转发装置；
    所述发送装置，用于生成携带有标记信息的数据，并将携带有所述标记信息的数据发送给所述转发装置；所述标记信息用于标识所述接收装置开展目标业务所需的数据；
    所述转发装置，用于向所述接收装置转发携带有所述标记信息的数据，并接收所述接收装置发送的携带有所述标记信息的查询请求，根据所述查询请求查询本地是否存在携带有所述标记信息的数据，并向所述接收装置返回查询结果信息；
    所述接收装置，用于接收所述转发装置转发的携带有所述标记信息的数据，并向所述转发装置发送所述查询请求，接收所述转发装置返回的所述查询结果信息，并在所述查询结果信息指示所述转发装置本地不存在携带有所述标记信息的数据时，根据已接收到的携带有所述标记信息的数据开展所述目标业务。
  20. 根据权利要求19所述的系统，其特征在于，所述标记信息包括：产生开展所述目标业务所需的数据的业务所属的业务类型和用于标识开展所述目标业务所需的数据所在时间段的时间段标识。
PCT/CN2015/093629 2014-11-11 2015-11-03 业务数据处理方法、装置及系统 Ceased WO2016074572A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US15/524,591 US10642907B2 (en) 2014-11-11 2015-11-03 Processing service data
KR1020177013535A KR101978951B1 (ko) 2014-11-11 2015-11-03 서비스 데이터의 처리
EP15858159.5A EP3220607B1 (en) 2014-11-11 2015-11-03 Service data processing methods and devices
SG11201701856PA SG11201701856PA (en) 2014-11-11 2015-11-03 A method, a means and a system for processing service data
JP2017543868A JP6475852B2 (ja) 2014-11-11 2015-11-03 サービスデータを処理するための方法、装置、および、システム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410632878.7 2014-11-11
CN201410632878.7A CN105656769B (zh) 2014-11-11 2014-11-11 业务数据处理方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2016074572A1 true WO2016074572A1 (zh) 2016-05-19

Family

ID=55953729

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/093629 Ceased WO2016074572A1 (zh) 2014-11-11 2015-11-03 业务数据处理方法、装置及系统

Country Status (7)

Country Link
US (1) US10642907B2 (zh)
EP (1) EP3220607B1 (zh)
JP (1) JP6475852B2 (zh)
KR (1) KR101978951B1 (zh)
CN (1) CN105656769B (zh)
SG (1) SG11201701856PA (zh)
WO (1) WO2016074572A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106372868B (zh) * 2016-09-06 2020-02-18 联动优势科技有限公司 一种对写入区块链的交易数据的验证方法和装置
CN109815256A (zh) * 2018-12-21 2019-05-28 聚好看科技股份有限公司 一种数据处理方法、装置、电子设备和存储介质
KR102663509B1 (ko) * 2020-11-27 2024-05-03 한양대학교 에리카산학협력단 쿼리 처리 시스템, 장치 및 방법
CN114791926A (zh) * 2022-05-06 2022-07-26 中国建设银行股份有限公司 一种机构信息管理方法及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483653A (zh) * 2009-02-17 2009-07-15 杭州华三通信技术有限公司 网络设备向应用层提供应用层数据的方法、设备和系统
CN103209195A (zh) * 2012-01-11 2013-07-17 国家电网公司 数据获取方法、终端以及远端设备
CN103218454A (zh) * 2013-05-06 2013-07-24 百度在线网络技术（北京）有限公司 基于音频数据的文件查找方法、装置和系统
CN104703202A (zh) * 2013-12-04 2015-06-10 中国移动通信集团公司 一种数据获取系统及方法

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA1263721A (en) * 1985-10-18 1989-12-05 Owen Lloyd Nelson Communication system for the transfer of small digital message blocks and large digital message blocks
US5878228A (en) * 1996-11-15 1999-03-02 Northern Telecom Limited Data transfer server with time slots scheduling base on transfer rate and predetermined data
US6219648B1 (en) 1997-03-31 2001-04-17 Sbc Technology Resources, Inc. Apparatus and method for monitoring progress of customer generated trouble tickets
US6366947B1 (en) * 1998-01-20 2002-04-02 Redmond Venture, Inc. System and method for accelerating network interaction
US7343412B1 (en) * 1999-06-24 2008-03-11 International Business Machines Corporation Method for maintaining and managing dynamic web pages stored in a system cache and referenced objects cached in other data stores
JP2002373109A (ja) * 2001-06-13 2002-12-26 Nec Corp データ先読みシステムおよび先読み方法
US7487262B2 (en) 2001-11-16 2009-02-03 At & T Mobility Ii, Llc Methods and systems for routing messages through a communications network based on message content
US7319858B2 (en) 2001-11-16 2008-01-15 Cingular Wireless Ii, Llc System and method for querying message information
WO2005093667A1 (en) * 2004-03-25 2005-10-06 Nokia Corporation Method, device and system for information based automated selective data handling and provision by identification means
JP4581870B2 (ja) * 2005-06-29 2010-11-17 ブラザー工業株式会社 通信システム、情報処理装置、及びプログラム
JP4872412B2 (ja) * 2006-03-31 2012-02-08 日本電気株式会社 情報検知処理方法及び装置
US7937464B2 (en) 2006-11-10 2011-05-03 Bally Gaming, Inc. Download progress management gaming method
US7996521B2 (en) 2007-11-19 2011-08-09 Experian Marketing Solutions, Inc. Service for mapping IP addresses to user segments
JP5178685B2 (ja) * 2009-10-26 2013-04-10 株式会社日立製作所 情報処理システム、情報処理装置、および情報処理方法
JP5641843B2 (ja) 2010-09-24 2014-12-17 シスメックス株式会社 検体分析システム、検体分析装置および検体分析装置の制御方法
JP2013210701A (ja) 2012-03-30 2013-10-10 Oki Electric Ind Co Ltd サーバ、更新情報管理方法および表示制御方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483653A (zh) * 2009-02-17 2009-07-15 杭州华三通信技术有限公司 网络设备向应用层提供应用层数据的方法、设备和系统
CN103209195A (zh) * 2012-01-11 2013-07-17 国家电网公司 数据获取方法、终端以及远端设备
CN103218454A (zh) * 2013-05-06 2013-07-24 百度在线网络技术（北京）有限公司 基于音频数据的文件查找方法、装置和系统
CN104703202A (zh) * 2013-12-04 2015-06-10 中国移动通信集团公司 一种数据获取系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3220607A4 *

Also Published As

Publication number Publication date
KR20170072282A (ko) 2017-06-26
US20180189395A1 (en) 2018-07-05
SG11201701856PA (en) 2017-06-29
EP3220607A1 (en) 2017-09-20
CN105656769B (zh) 2018-11-09
CN105656769A (zh) 2016-06-08
KR101978951B1 (ko) 2019-05-16
US10642907B2 (en) 2020-05-05
EP3220607A4 (en) 2018-08-22
JP2017535899A (ja) 2017-11-30
JP6475852B2 (ja) 2019-02-27
EP3220607B1 (en) 2022-06-08

Similar Documents

Publication Publication Date Title
CN105337961B (zh) 和客户端进行通信的方法以及服务器
US20150215400A1 (en) File Upload Method And System
US9392081B2 (en) Method and device for sending requests
WO2011113372A1 (zh) 多群组操作同步的方法、系统和群组服务器
WO2014008811A1 (zh) 推送信息的方法、系统及服务器
CN112422438A (zh) 一种处理组播报文的方法及装置
JP6213755B2 (ja) コンテンツ共有方法およびソーシャル同期装置
CN106603711B (zh) 通信方法、系统及消息服务器
CN105657000A (zh) 消息传送方法及装置
CN104270302B (zh) 在线订单的传送系统及传送方法
WO2016074572A1 (zh) 业务数据处理方法、装置及系统
CN102647365A (zh) 处理消息及消息状态的方法、装置和数据交换服务器
CN103037000B (zh) 一种发布订阅系统及其通知消息处理方法
CN112527530A (zh) 消息处理方法、装置、设备、存储介质及计算机程序产品
US10268532B2 (en) Application message processing system, method, and application device
CN105357329B (zh) 跨idc网络环境下业务数据的传输方法、装置及系统
WO2012116579A1 (zh) 一种信息反馈方法和相应的服务器
WO2012174838A1 (zh) 一种网元消息并发处理方法及系统
KR101545663B1 (ko) 다중-사용자 관계 체인을 변경하는 기기, 시스템 및 방법
CN101753561B (zh) 业务的集群处理方法及集群系统
CN105447000A (zh) 一种事务消息的传输方法和设备
CN104022941A (zh) 一种会议即时通讯系统及其实现方法
CN117596288A (zh) 一种消息传输方法、装置、电子设备及存储介质
CN103152245A (zh) 一种巡航路线控制方法及系统
CN103873355A (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: 15858159

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015858159

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015858159

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 11201701856P

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 2017543868

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20177013535

Country of ref document: KR

Kind code of ref document: A