Transmission method, device and equipment for generic online batch interface
By using a generic online batch interface transmission method, the problem of agreeing on file parsing format between the consumer and the service provider in traditional interface design is solved. This enables custom parsing communication of data files and interface reuse, reducing development costs and improving user experience.
Patent Information
- Application Number
- CN202511081579.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-04
- Publication Date
- 2025-12-19
AI Technical Summary
In traditional interface design, consumers and service providers need to agree on the file parsing format, which leads to high development costs and inconsistent input parameter file formats for different business logics, making it impossible to achieve sharing and reuse.
This paper provides a generic online batch interface transmission method. The consumer requests the batch number from the service provider, serializes the object list data into a file, uploads it to the file sharing center, and obtains the deserialization result data from the service provider through the path. It supports asynchronous execution and status monitoring, reducing development complexity and cost.
It implements custom parsing communication for online batch processing of data files, simplifies the consumer access process, supports interface reuse, reduces development costs, and improves user experience.
Smart Images
Figure CN121173797A_ABST
Abstract
Description
Technical Field
[0001] The embodiments in this specification relate to the field of data processing technology and are applicable to financial technology system scenarios. In particular, they relate to a transmission method, apparatus, and device for a generic online batch interface. Background Technology
[0002] The biggest drawback of traditional interface design is that consumers and service providers need to agree on a file parsing format in order to parse the file content for business processing. This results in high development costs for consumers to integrate the interface, and the input parameter file formats for different business logics are inconsistent, making it impossible to share and reuse them. Summary of the Invention
[0003] To address the problems existing in the prior art, this specification provides a generic online batch interface transmission method, apparatus, and device. This solves the problem that in traditional online batch interface designs, the consumer and service provider need to agree on a file parsing format in order to parse the file content for business processing, resulting in high access development costs and inconsistent input parameter file formats for different business logics, making sharing and reuse impossible.
[0004] The specific technical solutions of the embodiments in this specification are as follows:
[0005] On the one hand, embodiments of this specification provide a transmission method for a generic online batch interface, the method comprising:
[0006] After the consumer inputs the list of objects, they request the service provider to obtain the batch number.
[0007] Serialize the object list data into an object list file;
[0008] The service provider requests the batch number and object list file attribute information to the service provider so that the service provider can deserialize the object list file corresponding to the object list file attribute information to obtain the object list data, execute the batch processing business of the object list data, and serialize the result data into the result file with the batch number.
[0009] The result file of the batch number is monitored, and the result file is deserialized to obtain the result data.
[0010] Furthermore, when requesting the service provider to obtain the batch number, the method further includes:
[0011] The service provider records the batch number in its database.
[0012] Furthermore, when requesting the service provider with the batch number and object list file attribute information, the method further includes:
[0013] If the service provider successfully queries the database record using the batch number, it sets the status of the task record with the batch number in the processing task record table to "ready to process". When the service provider polls the batch processing task record table to obtain the task record with the batch number, it performs the step of deserializing the object list file corresponding to the object list file attribute information to obtain the object list data.
[0014] Furthermore, requesting the service provider with the batch number and object list file attribute information further includes:
[0015] The system requests the service provider with the batch number, batch processing business type, and object list file attribute information, so that the service provider can complete the task record of the batch number in the task record table according to the batch processing business type.
[0016] Furthermore, after serializing the object list data into an object list file, the method further includes:
[0017] Upload the object list file to the file sharing center and obtain the first path of the object list file;
[0018] The request to the service provider, carrying the batch number and object list file attribute information, further includes:
[0019] The system requests the service provider with the batch number and the object list file attribute information including the first path, so that the service provider can obtain the object list file from the file sharing center through the first path.
[0020] Furthermore, the method also includes:
[0021] After the service provider serializes the result data into a result file with the batch number, the method further includes:
[0022] The service provider uploads the result file to the file sharing center and obtains the second path of the result file;
[0023] The result file from monitoring the batch number further includes:
[0024] When the processing status of the batch number being monitored is "processing complete", request the service provider to obtain the second path;
[0025] The result file is obtained from the file sharing center via the second path.
[0026] Furthermore, after requesting the service provider to obtain the batch number, the method further includes:
[0027] The batch number is returned to the consumer.
[0028] Furthermore, after returning the batch number to the consumer, the method further includes:
[0029] Update the business processing status corresponding to the batch number based on the serialization status of the object list file, the monitoring status of the batch number, or the deserialization status of the result file.
[0030] Furthermore, the method also includes:
[0031] If a query request for the business processing status of the batch number is received from the consumer, the business processing status corresponding to the batch number will be returned to the consumer.
[0032] On the other hand, embodiments of this specification also provide a transmission device for a generic online batch interface, the device comprising:
[0033] The first request unit is used to request the service provider to obtain the batch number after the consumer inputs the object list data;
[0034] A serialization unit is used to serialize the object list data into an object list file;
[0035] The second request unit is used to request the service provider carrying the batch number and object list file attribute information, so that the service provider can deserialize the object list file corresponding to the object list file attribute information to obtain the object list data, execute the batch processing business of the object list data, and serialize the result data into the result file of the batch number.
[0036] The monitoring unit is used to monitor the result file of the batch number and deserialize the result file to obtain the result data.
[0037] On the other hand, embodiments of this specification also provide a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the above-described method.
[0038] On the other hand, embodiments of this specification also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.
[0039] Using the embodiments in this specification, a custom parsing communication for online batch processing of data files is implemented, featuring an object-oriented interface that is easy for consumers to access. During the user platform construction process, tasks such as batch maintenance of potential customers, batch maintenance of customer lists, and batch maintenance of public-private linkage lists are made reusable through generic object-oriented interface design, reducing the access cost for consumers. Attached Figure Description
[0040] To more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0041] Figure 1 The figure shown is a schematic diagram of an implementation system for a transmission method of a generic online batch interface according to an embodiment of this specification.
[0042] Figure 2 The diagram shown is a schematic flowchart of a transmission method for a generic online batch interface in an embodiment of this specification.
[0043] Figure 3 The diagram shown is a schematic representation of the process by which the SDK uploads the result file to the file sharing center in an embodiment of this specification.
[0044] Figure 4 The diagram shown is a schematic representation of the process by which the service provider uploads the result file to the file sharing center in an embodiment of this specification.
[0045] Figure 5 The diagram shown is a flowchart illustrating the process of updating the business processing status corresponding to the batch number in an embodiment of this specification.
[0046] Figure 6 The diagram shown is a structural schematic of a transmission device for a generic online batch interface according to an embodiment of this specification.
[0047] Figure 7 The diagram shown is a structural schematic of the computer device in an embodiment of this specification.
[0048] [Explanation of Figure Markers]:
[0049] 101. Consumer;
[0050] 102. Service Provider;
[0051] 601. First Request Unit;
[0052] 602. Serialization unit;
[0053] 603. Second Request Unit;
[0054] 604. Monitoring Unit;
[0055] 702. Computer equipment;
[0056] 704. Processing equipment;
[0057] 706. Storage resources;
[0058] 708. Drive system;
[0059] 710. Input / Output Module;
[0060] 712. Input devices;
[0061] 714. Output devices;
[0062] 716. Presentation equipment;
[0063] 718. Graphical User Interface;
[0064] 720. Network interface;
[0065] 722. Communication link;
[0066] 724. Communication bus. Detailed Implementation
[0067] The technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the embodiments of this specification, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of the embodiments of this specification.
[0068] It should be noted that the terms "first," "second," etc., in the description, claims, and accompanying drawings of the embodiments herein are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, apparatus, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.
[0069] It should be noted that the acquisition, storage, use, and processing of data in the technical solutions of the embodiments of this specification all comply with the relevant provisions of national laws and regulations.
[0070] It should be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, they do not mean that the applicant has used or necessarily used the solution.
[0071] like Figure 1 The diagram illustrates a system implementation of a generic online batch interface transmission method according to an embodiment of this specification, including a consumer 101 and a service provider 102. The consumer 101 and the service provider 102 can communicate via a network, which may include a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof, and is connected to a website, user equipment (e.g., a computing device), and a backend system.
[0072] Users first input a list of objects to be processed in batches through consumer 101. An SDK can be deployed on consumer 101 to process the object list data. Service provider 102 can then perform the batch processing.
[0073] Optionally, consumer 101 can be a device with cellular communication capabilities, such as a mobile phone, handheld device, wearable device, computer, or tablet, or substantially any type of wireless device. Server 102 can be a node in a cloud computing system (not shown), or each server can be a separate cloud computing system comprising multiple computers interconnected by a network and operating as a distributed processing system.
[0074] In addition, it should be noted that, Figure 1 The examples shown are merely one application environment provided by the embodiments in this specification. In practical applications, other application environments may also be included, and this specification does not impose any limitations.
[0075] To address the problems existing in the prior art, this specification provides a transmission method for a generic online batch interface. Figure 2 The diagram illustrates a flowchart of a generic online batch interface transmission method according to an embodiment of this specification. While the diagram depicts the batch processing procedure, it may include more or fewer steps based on conventional or non-creative work. The order of steps listed in the embodiment is merely one possible execution order among many and does not represent the only possible order. In actual system or device products, the methods shown in the embodiment or the accompanying drawings can be executed sequentially or in parallel. Specifically, as shown... Figure 2 As shown, the method may include:
[0076] Step 201: After the consumer inputs the object list data, they request the service provider to obtain the batch number;
[0077] Step 202: Serialize the object list data into an object list file;
[0078] Step 203: Send a request to the service provider with the batch number and object list file attribute information, so that the service provider can deserialize the object list file corresponding to the object list file attribute information to obtain the object list data, execute the batch processing business of the object list data, and serialize the result data into the result file with the batch number;
[0079] Step 204: Listen to the result file of the batch number and deserialize the result file to obtain the result data.
[0080] Using the embodiments in this specification, a custom parsing communication for online batch processing of data files is implemented, featuring an object-oriented interface that is easy for consumers to access. During the user platform construction process, tasks such as batch maintenance of potential customers, batch maintenance of customer lists, and batch maintenance of public-private linkage lists are made reusable through generic object-oriented interface design, reducing the access cost for consumers.
[0081] In the embodiments of this specification, a generic online batch processing interface is first defined, which can take in an object list file and call the service provider's business functions.
[0082] Users can input a list of object data through the consumer side. This list of object data represents the data that the user needs to add, delete, modify, and / or query in batches. After the consumer inputs the data, the SDK can request a batch number from the service provider. The batch number is a unique identifier for the current batch processing task, allowing the SDK to process and track the current batch processing task based on the batch number.
[0083] Specifically, the service provider defines and obtains a globally unique batch number, records the batch number in the database, and uses a generic online batch processing interface to associate it with batch processing business for data identification and service query.
[0084] After obtaining the batch number, the SDK serializes the object list data into an object list file. For example, it defines a batch processing interface and a parameter-to-file method, constructs a map collection containing object list data, object type names, and special requirement business information, and serializes the object list data table into a String type using ObjectMapper. Then, it creates an object list file and writes the String type information into the object list file.
[0085] This can be understood as follows: the consumer does not need to pre-agree on the parsing format with the service provider. Instead, it directly inputs the data to be added, deleted, modified, or queried in list form. The SDK serializes the object list data input by the consumer to obtain an object list file, which the service provider then deserializes to obtain the object list data for batch processing. This avoids developing a message interface between the consumer and the service provider, saving development costs for consumer integration. Furthermore, because the consumer no longer cares about the service provider's data format, user operations are simpler, improving the user's batch processing experience.
[0086] In addition, the SDK can be deployed on the consumer side as needed, realizing interface sharing and reuse, and reducing the development cost of the service provider.
[0087] According to one embodiment of this specification, in order to facilitate file transfer between the SDK and the consumer, such as Figure 3 As shown, after the SDK serializes the object list data into an object list file, the method further includes:
[0088] Step 301: Upload the object list file to the file sharing center and obtain the first path of the object list file;
[0089] The request to the service provider, carrying the batch number and object list file attribute information, further includes:
[0090] Step 302: Request the service provider with the batch number and the object list file attribute information including the first path, so that the service provider can obtain the object list file from the file sharing center through the first path.
[0091] In this embodiment of the specification, because the batch processing data volume is very large, this embodiment abandons the method of directly transferring files between the SDK and the service provider. Instead, it adopts a file sharing method. The SDK uploads the object list file to the file sharing center and obtains the storage path of the object list file in the file sharing center. Then, it requests the service provider with the batch number and the first path. The service provider then retrieves the object list file from the file sharing center through the first path, thereby reducing the link overhead between the SDK and the service provider that would otherwise be caused by the large size of the object list file. In addition, with this file sharing method, transmission control can be executed independently by the SDK without the need for cooperation between the SDK and the service provider, thereby reducing development difficulty and cost.
[0092] Similarly, such as Figure 4 As shown, after the service provider serializes the result data into a result file with the batch number, the method further includes:
[0093] Step 401: The service provider uploads the result file to the file sharing center and obtains the second path of the result file;
[0094] The result file from monitoring the batch number further includes:
[0095] Step 402: When the processing status of the batch number being monitored is "processing complete", request the service provider to obtain the second path;
[0096] Step 403: Obtain the result file from the file sharing center via the second path.
[0097] This can be understood as follows: after the service provider completes batch processing, it can upload the result file to a file sharing center, and the SDK can then download the result file from the file sharing center. This reduces the link overhead between the SDK and the service provider due to the large size of the result file. Furthermore, with this file sharing method, transmission control can be executed independently by the service provider, without the need for cooperation between the SDK and the service provider, thus reducing development difficulty and cost.
[0098] In some other embodiments of this specification, because the batch processing data volume is large, the SDK may take a long time to serialize the object list data into an object list file or upload the object list file. Therefore, after inputting the object list data, the service provider will be in a state of waiting for a return value for a certain period of time. During this time, the service provider will be unable to process other business and the user experience will be reduced. Based on this, the embodiments of this specification adopt a method of asynchronous execution of batch number acquisition and object list data serialization. That is, after the consumer inputs the list data, the SDK immediately requests the service provider to obtain the batch number, and simultaneously executes the object list data serialization process asynchronously. Because the service provider only needs to generate and store one batch number, the time required for the service provider to return the batch number is much shorter than the time required for object list data serialization. Therefore, after requesting the service provider to obtain the batch number, the SDK returns the batch number to the consumer.
[0099] After receiving feedback from the SDK, the service provider can handle other user business and improve the user experience.
[0100] According to one embodiment of this specification, in order to further improve the user experience, such as Figure 5 As shown, after the SDK returns the batch number to the consumer, the method further includes:
[0101] Step 501: Update the business processing status corresponding to the batch number according to the serialization status of the object list file, the monitoring status of the batch number, or the deserialization status of the result file;
[0102] Step 502: If a business processing status query request for the batch number is received from the consumer, the business processing status corresponding to the batch number is returned to the consumer.
[0103] This can be understood as, through Figure 5 This method allows consumers to check the processing status of the corresponding batch number, further improving the user experience.
[0104] In the embodiments described in this specification, when the service provider receives a request to obtain a batch number, in addition to recording the batch number in the database, it can also create a task record for the batch number and store the task record in the task record table.
[0105] This can be understood as the service provider processing batch processing tasks by processing task records.
[0106] However, because the process of requesting and retrieving batch number and object list data serialization on the SDK side is executed asynchronously, the processing data on the SDK side is not yet ready when the service provider generates the batch number. Therefore, the task record for the batch number is still in an empty shell state and there is no actual data to process. Therefore, when the service provider creates the task record for the batch number, it can set the task record in the task record table to the initial state. The service provider does not need to poll the task record in the initial state in the task record table.
[0107] After the batch processing data is prepared on the SDK side, it will request the service provider with the batch number, batch processing business type, and object list file attribute information. The service provider will complete the task record with the batch number in the task record table according to the batch processing business type and the first path in the object list file attribute information, and then set the status of the task record with the batch number in the processing task record table to ready for processing.
[0108] When the service provider polls the batch processing task record table and obtains the task record with the batch number, it retrieves the object list file from the file sharing center through the first path and performs deserialization of the object list file to obtain the object list data.
[0109] Then, the object list data is batch-processed according to the batch processing business type to obtain the result data.
[0110] Subsequently, the service provider can serialize the result data to obtain the result file with the batch number, then upload the result file to the file sharing center and obtain the second path of the result file. A message carrying the batch number and indicating completion can be broadcast via a message broker (e.g., Kafka).
[0111] After the task record with the batch number obtained by listening to Kafka messages on the SDK side is processed, the second path of the result file corresponding to the batch number is obtained from the service provider through the batch number. The result file is obtained through the second path, and the result file is deserialized to obtain the result data, which is then returned to the consumer.
[0112] It should be noted that the SDK and the service provider can negotiate the serialization format in advance, associate the serialization format with the batch processing business type, and perform serialization or deserialization operations according to the serialization format.
[0113] In some other embodiments of this specification, when the SDK requests data from the service provider using a batch number, the service provider can verify the batch number and the SDK's identifier. Only after successful verification can subsequent processing proceed, ensuring that batch processing is not disrupted and improving the security of the batch processing object list data and / or result data. Based on this inventive concept, communication between the SDK and the consumer can also be verified. The verification process can refer to the verification process between the SDK and the service provider, and will not be elaborated here.
[0114] In some other embodiments of this specification, after the SDK requests the service provider with the batch number and object list file attribute information, the service provider verifies the batch number and the SDK's identifier and returns a start processing message for the batch number to the SDK. Then, the SDK can start listening to whether the batch number generates a result file (e.g., listening to whether the service provider sends a processing completion message for the task record of the batch number). The process of the SDK listening to the batch number and the process of the service provider processing the task record of the batch number can be executed in parallel.
[0115] In some other embodiments of this specification, the service provider's task record table can be a queue, and each task record in the queue is processed in the order of its entry time. When the status of a certain task record is not ready for processing, the task record is skipped.
[0116] Furthermore, the service provider and SDK can also support a task record status query function. Specifically, the SDK sends a task record status query request for a batch number to the service provider. The service provider determines the queuing status of the task record corresponding to that batch number in the task record table and returns it to the SDK. Of course, the task record status query function can also be triggered by the consumer. For example, the consumer sends a task record query request for a batch number to the SDK. Then, the SDK executes the step of querying the task record status of that batch number from the service provider, obtains the queuing status of the task record corresponding to that batch number, and returns the queuing status of the task record corresponding to that batch number to the consumer.
[0117] Based on the same inventive concept, embodiments of this specification also provide a transmission device for a generic online batch interface, such as... Figure 6 As shown, it includes:
[0118] The first request unit 601 is used to request the service provider to obtain the batch number after the consumer inputs the object list data;
[0119] Serialization unit 602 is used to serialize the object list data into an object list file;
[0120] The second request unit 603 is used to request the service provider carrying the batch number and object list file attribute information, so that the service provider can deserialize the object list file corresponding to the object list file attribute information to obtain the object list data, execute the batch processing business of the object list data, and serialize the result data into the result file of the batch number.
[0121] The monitoring unit 604 is used to monitor the result file of the batch number and deserialize the result file to obtain the result data.
[0122] Furthermore, the service provider records the batch number in its database.
[0123] Furthermore, if the service provider successfully queries the database record using the batch number, it sets the status of the task record for the batch number in the processing task record table to "ready to process". When the service provider polls the batch processing task record table to obtain the task record for the batch number, it performs the step of deserializing the object list file corresponding to the object list file attribute information to obtain the object list data.
[0124] Furthermore, requesting the service provider with the batch number and object list file attribute information further includes:
[0125] The system requests the service provider with the batch number, batch processing business type, and object list file attribute information, so that the service provider can complete the task record of the batch number in the task record table according to the batch processing business type.
[0126] Furthermore, the device is also used to: serialize the object list data into an object list file, upload the object list file to a file sharing center, and obtain the first path of the object list file;
[0127] The request to the service provider, carrying the batch number and object list file attribute information, further includes:
[0128] The system requests the service provider with the batch number and the object list file attribute information including the first path, so that the service provider can obtain the object list file from the file sharing center through the first path.
[0129] Furthermore, after the service provider serializes the result data into a result file with the batch number, the method further includes:
[0130] The service provider uploads the result file to the file sharing center and obtains the second path of the result file;
[0131] The result file from monitoring the batch number further includes:
[0132] When the processing status of the batch number being monitored is "processing complete", request the service provider to obtain the second path;
[0133] The result file is obtained from the file sharing center via the second path.
[0134] Furthermore, the device is further configured to: after requesting the service provider to obtain the batch number, return the batch number to the consumer.
[0135] Furthermore, the device is further configured to: after returning the batch number to the consumer, update the business processing status corresponding to the batch number according to the serialization status of the object list file, the monitoring status of the batch number, or the deserialization status of the result file.
[0136] Furthermore, the device is further configured to: if it receives a business processing status query request from the consumer for the batch number, return the business processing status corresponding to the batch number to the consumer.
[0137] The beneficial effects obtained by the above-described device are the same as those obtained by the above-described method, and will not be described in detail in the embodiments of this specification.
[0138] like Figure 7The diagram illustrates the structure of a computer device according to an embodiment of this specification. The computer device in this embodiment is capable of executing the methods described in the embodiments of this specification. The computer device 702 may include one or more processing devices 704, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 702 may also include any storage resource 706 for storing information of any kind, such as code, settings, data, etc. Without limitation, for example, the storage resource 706 may include any type of RAM, any type of ROM, flash memory, hard disk, optical disk, etc. More generally, any storage resource can use any technology to store information. Furthermore, any storage resource may provide volatile or non-volatile retention of information. Furthermore, any storage resource may represent a fixed or removable component of the computer device 702. In one case, when the processing device 704 executes associated instructions stored in any storage resource or combination of storage resources, the computer device 702 may perform any operation of the associated instructions. The computer device 702 also includes one or more drive systems 708 for interacting with any storage resources, such as hard disk drive systems, optical disk drive systems, etc.
[0139] Computer device 702 may also include an input / output module 710 (I / O) for receiving various inputs (via input device 712) and providing various outputs (via output device 714). A specific output mechanism may include a presentation device 716 and an associated graphical user interface (GUI) 718. In other embodiments, the input / output module 710 (I / O), input device 712, and output device 714 may be omitted, and the device may function solely as a computer device within a network. Computer device 702 may also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the components described above together.
[0140] Communication link 722 can be implemented in any way, such as via a local area network, a wide area network (e.g., the Internet), a point-to-point connection, or any combination thereof. Communication link 722 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
[0141] This specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.
[0142] This specification also provides computer-readable instructions, wherein when a processor executes the instructions, the program therein causes the processor to perform the above-described method.
[0143] It should be understood that in the various embodiments of this specification, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this specification.
[0144] It should also be understood that, in the embodiments of this specification, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the embodiments of this specification, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.
[0145] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the embodiments in this specification.
[0146] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0147] In the embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, devices, or units, or they may be electrical, mechanical, or other forms of connection.
[0148] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments described in this specification, depending on actual needs.
[0149] Furthermore, the functional units in the various embodiments of this specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0150] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this specification, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this specification. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0151] This specification describes the principles and implementation methods of the embodiments using specific examples. The above descriptions of the embodiments are only for the purpose of helping to understand the methods and core ideas of the embodiments in this specification. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the embodiments in this specification. Therefore, the content of this specification should not be construed as a limitation on the embodiments in this specification.
Claims
1. A transmission method for a generic online batch interface, characterized in that, The method includes: After the consumer inputs the list of objects, they request the service provider to obtain the batch number. Serialize the object list data into an object list file; The service provider requests the batch number and object list file attribute information to the service provider so that the service provider can deserialize the object list file corresponding to the object list file attribute information to obtain the object list data, execute the batch processing business of the object list data, and serialize the result data into the result file with the batch number. The result file of the batch number is monitored, and the result file is deserialized to obtain the result data.
2. The method according to claim 1, characterized in that, When requesting the service provider to obtain the batch number, the method further includes: The service provider records the batch number in its database.
3. The method according to claim 2, characterized in that, When requesting the service provider with the batch number and object list file attribute information, the method further includes: If the service provider successfully queries the database record using the batch number, it sets the status of the task record with the batch number in the processing task record table to "ready to process". When the service provider polls the batch processing task record table to obtain the task record with the batch number, it performs the step of deserializing the object list file corresponding to the object list file attribute information to obtain the object list data.
4. The method according to claim 3, characterized in that, The request to the service provider, carrying the batch number and object list file attribute information, further includes: The system requests the service provider with the batch number, batch processing business type, and object list file attribute information, so that the service provider can complete the task record with the batch number in the task record table according to the batch processing business type.
5. The method according to claim 1, characterized in that, After serializing the object list data into an object list file, the method further includes: Upload the object list file to the file sharing center and obtain the first path of the object list file; The request to the service provider, carrying the batch number and object list file attribute information, further includes: The system requests the service provider with the batch number and the object list file attribute information including the first path, so that the service provider can obtain the object list file from the file sharing center through the first path.
6. The method according to claim 1, characterized in that, The method further includes: After the service provider serializes the result data into a result file with the batch number, the method further includes: The service provider uploads the result file to the file sharing center and obtains the second path of the result file; The result file from monitoring the batch number further includes: When the processing status of the batch number being monitored is "processing complete", request the service provider to obtain the second path; The result file is obtained from the file sharing center via the second path.
7. The method according to claim 1, characterized in that, After requesting the service provider to obtain the batch number, the method further includes: The batch number is returned to the consumer.
8. The method according to claim 7, characterized in that, After returning the batch number to the consumer, the method further includes: Update the business processing status corresponding to the batch number based on the serialization status of the object list file, the monitoring status of the batch number, or the deserialization status of the result file.
9. The method according to claim 8, characterized in that, The method further includes: If a query request for the business processing status of the batch number is received from the consumer, the business processing status corresponding to the batch number will be returned to the consumer.
10. A transmission device for a generic online batch interface, characterized in that, The device includes: The first request unit is used to request the service provider to obtain the batch number after the consumer inputs the object list data; A serialization unit is used to serialize the object list data into an object list file; The second request unit is used to request the service provider carrying the batch number and object list file attribute information, so that the service provider can deserialize the object list file corresponding to the object list file attribute information to obtain the object list data, execute the batch processing business of the object list data, and serialize the result data into the result file of the batch number. The monitoring unit is used to monitor the result file of the batch number and deserialize the result file to obtain the result data.
11. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 9.
12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 9.