WO2021088641A1 - 数据发送方法、处理方法、接收方法及其设备、存储介质 - Google Patents

数据发送方法、处理方法、接收方法及其设备、存储介质 Download PDF

Info

Publication number
WO2021088641A1
WO2021088641A1 PCT/CN2020/122254 CN2020122254W WO2021088641A1 WO 2021088641 A1 WO2021088641 A1 WO 2021088641A1 CN 2020122254 W CN2020122254 W CN 2020122254W WO 2021088641 A1 WO2021088641 A1 WO 2021088641A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
data
message
end device
request message
Prior art date
Application number
PCT/CN2020/122254
Other languages
English (en)
French (fr)
Inventor
韩雪
Original Assignee
中兴通讯股份有限公司
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
Priority claimed from CN201911080915.7A external-priority patent/CN112788074B/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021088641A1 publication Critical patent/WO2021088641A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • 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/566—Grouping or aggregating service requests, e.g. for unified processing
    • 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/562—Brokering proxy services

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of information management technology, and in particular to a data sending method, processing method, terminal device, front-end device, data exchange center and receiving method thereof, and computer-readable storage medium.
  • tasks are usually scheduled manually or by setting execution strategies. Tasks are started at a fixed time according to a set script, but When the task is completed and the execution result cannot be notified to the third-party business system in time, it can only be checked manually through operation and maintenance on a regular basis, and cannot be effectively combined with the actual business.
  • an embodiment of the present application provides a data sending method applied to a terminal device, including: acquiring task data, sending the task data to a first front-end device; and sending the task data to a first front-end device of the first front-end device.
  • a message middleware sends a task request message, and the task request message includes a task identifier associated with the task data.
  • an embodiment of the present application provides a data processing method applied to a front-end device, including: receiving task data from a first terminal device; receiving a task request message from the first terminal device, the task request message It includes a task identifier, the task identifier is associated with the task data; the task request message is sent to the data exchange center; the data extraction request from the data exchange center is received, and the task data is sent to the data exchange center.
  • an embodiment of the present application also provides a data processing method, applied to a data exchange center, including: receiving a task request message from a first front-end device, the task request message including a task identifier; according to the task The request message triggers a data processing task, extracts task data associated with the task identifier in the first intermediate library of the first front-end device, and writes the extracted task data into the second intermediate library of the second front-end device.
  • an embodiment of the present application also provides a data processing method applied to a front-end device, including: receiving task data from a data switching center; receiving a task notification message from the data switching center, where the task notification message includes Task identifier, the task identifier is associated with the task data; the task notification message is sent to the second terminal device; the data extraction request from the second terminal device is received, and the task data is sent to the second terminal equipment.
  • the present application also provides a data receiving method applied to a terminal device, including: receiving a task notification message from a second front-end device, the task notification message including a task identifier; according to the task notification message, Extract the task data associated with the task identifier in the second intermediate library of the second front-end device.
  • the present application also provides a terminal device, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • a terminal device including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • the processor executes the computer program, the implementation is as described in this application.
  • the present application also provides a front-end device, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • a front-end device including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • the processor executes the computer program
  • the computer program Apply for the data processing method described in the embodiment of the second aspect, or implement the data processing method described in the embodiment of the fourth aspect of this application.
  • the present application also provides a data exchange center, including: a memory, a processor, and a computer program stored in the memory and running on the processor.
  • the processor implements the application when the computer program is executed.
  • this application also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the data sending method described in the embodiment of the first aspect, or to execute The data processing method described in the embodiment of the second aspect is used to execute the data processing method described in the embodiment of the third aspect or the data processing method described in the embodiment of the fourth aspect is used to execute the data processing method described in the embodiment of the fourth aspect. Perform the data receiving method described in the embodiment of the fifth aspect.
  • Figure 1 is a system schematic diagram of an existing ETL system
  • Figure 2 is a system schematic diagram of a data management system provided by an embodiment of the present application.
  • FIG. 3 is a method flowchart of a first embodiment of a data sending method for a first terminal device according to an embodiment of the present application
  • FIG. 4 is a method flowchart of a first embodiment of a data processing method for a first front-end device according to an embodiment of the present application
  • FIG. 5 is a method flowchart of a first embodiment of a data processing method of a data exchange center provided by an embodiment of the present application
  • FIG. 6 is a flowchart of an implementation manner of step 301 in FIG. 5;
  • FIG. 7 is a flowchart of another implementation manner of step 301 in FIG. 5;
  • FIG. 8 is a method flowchart of a second embodiment of a data processing method for a data exchange center according to an embodiment of the present application
  • FIG. 9 is a method flowchart of the first embodiment of the data processing method of the second front-end device provided by an embodiment of the present application
  • FIG. 10 is a method flowchart of a first embodiment of a data receiving method for a first terminal device according to an embodiment of the present application
  • FIG. 11 is a flowchart of an implementation manner of step 501 in FIG. 10;
  • FIG. 12 is a flowchart of another implementation manner of step 501 in FIG. 10;
  • FIG. 13 is a structural block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 14 is a structural block diagram of a front-end device according to an embodiment of the present application.
  • FIG. 15 is a structural block diagram of a data exchange center according to an embodiment of the present application.
  • FIG. 16 is a visual interface diagram of a Jms message interface configuration according to an embodiment of the present application.
  • FIG. 17 is a visual configuration interface diagram of Jms message service configuration according to an embodiment of the present application.
  • FIG. 18 is a visual configuration interface diagram of Kafka message service configuration according to an embodiment of the present application.
  • FIG. 19 is a visual configuration interface diagram of ETL task mapping according to an embodiment of the present application.
  • FIG. 20 is a diagram of a service-driven management interface according to an embodiment of the present application.
  • ETL Extract-Transform-Load
  • Figure 1 is an existing ETL system. Structure, the user extracts the required data from distributed and heterogeneous data sources, transforms or cleans the extracted data according to the pre-designed rules, and finally uses the pre-defined data warehouse model to convert the processed data Load it into the data warehouse.
  • different heterogeneous data sources do not have planned and unified target data.
  • the core of ETL is the conversion process. Extraction and loading can be used as the input and output of the conversion.
  • ETL task scheduling is mostly performed manually or by setting execution strategies. For example, tasks are started at a fixed time according to a set script, but when the task is completed and the execution result cannot be notified in time to third-party business systems, it can only be performed manually on a regular basis. Check whether the data extraction, conversion, and loading are completed, which cannot be effectively combined with actual business.
  • the embodiments of the present application provide a data sending method, processing method, receiving method, terminal equipment, front-end equipment, data exchange center and its computer-readable storage medium, which realizes effective control of data processing tasks and improves The efficiency of data interaction improves the versatility and integration degree of docking different business platforms.
  • Figure 2 is a system schematic diagram of a data management system provided by an embodiment of the present application.
  • the system may include, but is not limited to, a first terminal device, a first front-end device, a data switching center, and a second front-end device.
  • Equipment and second terminal equipment The first terminal device and the second terminal device may be various electronic devices, such as computers, mobile terminals, servers, or other electronic devices with processor and data storage functions, such as external processing modules, distributed devices, and so on.
  • the first terminal device and the second terminal device may be on different service platforms.
  • the task data of the first terminal device cannot be directly transmitted to the second terminal device.
  • the data needs to be extracted, converted, and loaded to the second terminal device through the ETL tool.
  • the second terminal device for example, the data exchange center shown in FIG. 2 includes a server of an ETL tool, through which task data can be extracted, converted, and loaded.
  • the first front-end device is set between the first terminal device and the data switching center for coordinating the communication process between the first terminal device and the data switching center
  • the second front-end device is set between the second terminal device and the data switching center for use To coordinate the communication process between the second terminal device and the data exchange center.
  • the first front-end device and the second front-end device may be front-end devices.
  • the front-end devices have the function of isolating the host, ensuring that external applications cannot directly access core services, such as banks’ various services. Class external interface (telecommunications agency charging, bank-securities pass).
  • the front-end computer provides a bridge between business channels and the host of core services. It generally plays the role of managing and scheduling transactions initiated by business channels, and can reduce the burden of the core background server through the call of the front-end processor.
  • the business systems at both ends of the internal and external networks of government and enterprises require data exchange, and front-end computers are arranged in front of their respective business systems to realize data exchange.
  • the first front-end device and the second front-end device are equipped with intermediate libraries, such as the first intermediate library of the first device and the second intermediate library of the second device.
  • the intermediate library functions as a transfer and storage task data. Function, for security and isolation, ETL tools cannot directly extract task data from each platform, but need to store task data in the first intermediate library, and then extract it by ETL tools. Similarly, ETL tools cannot directly extract task data. To write to the memory or database of the platform, the task data needs to be written to the second intermediate library first, and then the task data is extracted from the intermediate library from the terminal device receiving the data. As shown in Figure 2, the first terminal device, the first intermediate library, the ETL tool, the second intermediate library, and the second terminal device are sequentially connected to establish a transmission channel for task data.
  • the message middleware mechanism control is used in the embodiment of this application.
  • the process of task data processing such as controlling the execution process of ETL tools.
  • the first front-end device is provided with a first message middleware
  • the second front-end device is provided with a second message middleware
  • the first terminal device and the second terminal device are configured
  • a message middleware interface so that the task information can be transmitted through the message middleware mechanism.
  • the above-mentioned message middleware includes any form of components that can improve reliable and efficient data transmission services for distributed systems, or other forms of software tools.
  • the data exchange center is also provided with a message proxy module, and the ETL tool communicates with the message proxy module through a message proxy interface.
  • the message middleware mechanism is suitable for accessing the application program interface (API) of the message system independent of the manufacturer. It provides an interface for applications to create, send, receive and read messages, such as JMS message middleware or Kafka in the Java Message Service Specification
  • Message middleware is a commonly used communication mechanism for message middleware.
  • the first middleware and the second middleware can be implemented by JMS or Kafka on the Java platform, and can also be message-oriented middleware adapters for non-Java platforms.
  • the message middleware communication mechanism includes message producers, consumers and message middleware.
  • the producer publishes the message, the message middleware forwards the message from the producer to the consumer, and the consumer receives and processes the message.
  • the first terminal device is the producer of the message
  • the second terminal device is the consumer of the message
  • the data exchange center is the consumer of the first terminal device and the producer of the second terminal device.
  • the data exchange center obtains the task request message from the first terminal device through the message middleware, and the data exchange center triggers the data processing task in response to the task request message, and extracts the corresponding data from the first intermediate library of the first front-end device.
  • Task data after processing the data, write it to the second intermediate library of the second front-end device to complete the ETL task, and then the data exchange center acts as the message producer and sends the data to the second message middleware of the second front-end device.
  • the second terminal device sends a task notification message to notify the second terminal device that the task data can be extracted from the second intermediate library.
  • the first terminal device, the first message middleware, the message proxy module, the second message middleware, and the second terminal device are connected in sequence to establish a transmission channel for notification messages.
  • the notification messages of the first terminal device, the data exchange center, and the second terminal device are transmitted through the message middleware mechanism, they belong to the asynchronous communication mode.
  • the first terminal device sends the task request message to the first terminal device.
  • Message middleware has queue and topic modes.
  • the queue mode can also be called point-to-point mode, which is generally pulled by consumers actively, and messages can be deleted after confirmation. Even if there are multiple subscribers, the message in the queue can only be consumed by one consumer.
  • system A sends a message to the queue, and the message middleware finds that the destination queue pointed to by the queue is actually located in system B. It puts the information in A special local queue-Transmission Queue.
  • Establish a message channel from system A to system B the message channel agent will read the message from the transmission queue, and pass this information to system B, and then wait for confirmation. Only after the message middleware receives the confirmation that the system B has successfully received the message, it will actually delete the message from the transmission queue.
  • the topic mode is also known as the publish/subscribe mode.
  • the publish/subscribe function enables the distribution of messages to break through the geographical direction of the destination queue, and make the messages distributed according to a specific topic or even content. Users or applications can receive all messages according to the topic or content. Message needed.
  • the publish/subscribe function makes the coupling relationship between the sender and the receiver looser.
  • the sender does not need to care about the destination address of the receiver, and the receiver does not need to care about the sending address of the message, but only according to the subject of the message. Of sending and receiving.
  • task data of the first terminal device needs to be sent to the second terminal device. Because the first terminal device and the second terminal device are on different platforms, the data cannot be directly interoperable. , The task data needs to be extracted, converted, and loaded to the second terminal device through the ETL tool.
  • the first terminal device, the data exchange center, and the second terminal device are configured with interfaces and/or plug-ins for communicating with the message middleware.
  • the first terminal device obtains the task data that needs to be processed and needs to instruct the ETL tool how to process the task data Task content.
  • the first terminal device obtains the task identifier, which may be automatically generated by the system or input or configured by the user. For example, keywords may be extracted from the task data to automatically generate the task identifier, or a visual interface may be provided to the user for input or configuration by the user. Configuration.
  • the task identifier is associated with task data, that is, the data exchange center can process related task data according to the task identifier.
  • the association between the task identifier and the task data can be pre-appointed with the data exchange center and the second terminal device.
  • the relationship between the data, or the connection between the task ID and the task data is established by mapping, or the information of the task data can be extracted and associated with the task ID. For example, the database name or the name of the data table of the task data is used as the task ID, then the task ID is automatically established The association of task ID and task data.
  • the task identifier can be agreed to be various message types, such as the aforementioned database name or data table name, etc.
  • the first terminal device generates a task request message according to the above-mentioned task identifier and the configured message middleware interface information, that is, the task request message includes two parts of content, one part is used to indicate the message sending object, and the other part is used to indicate ETL How the tool performs the task, for example, in one embodiment, the task identifier is used to indicate the processing data object of the ETL tool, which is the name of the data table of the task data, and the task trigger of the ETL tool triggers the extraction of corresponding task data through the task content message.
  • the task identifier is used to instruct the ETL tool to process the data object, and also to instruct the ETL tool to perform the corresponding task.
  • the data exchange center needs to agree or set the task identifier and the data processing task.
  • the first terminal device only needs to send the task identifier to the data exchange center to instruct the ETL tool to execute the specified ETL task.
  • the first terminal device first sends the task data to be processed to the first intermediate library of the first front-end device, which can be sent in a serial or parallel manner, and the sending method of the task data is not repeated here.
  • the first terminal device sends the task request message to the data interaction center through the first message middleware of the first front-end device. As described above, it can be sent in a queue or topic mode.
  • the first terminal device When the topic mode is adopted, the first terminal device needs to set first message topic information.
  • the first message topic information includes a first message topic for classifying messages, and the data exchange center needs to subscribe to the first message topic in advance.
  • the task request message sent by the first terminal device to the first front-end device includes the first message subject information and the task identifier, when the first message middleware of the first front-end device receives the task request message from the first terminal device , Save the task request message under the first message topic. Since the data exchange center subscribes to the first message topic, the first message middleware will send the task request message to the data exchange center to achieve Sending of task request messages.
  • a first terminal device and a second terminal device are given.
  • multiple terminal devices can also be set and the front-end devices can be configured accordingly.
  • the data exchange center can subscribe to multiple message topics of multiple terminal devices. This embodiment is suitable for data sending tasks to multiple objects. For example, the task content of task request information is to send current task data to multiple third-party platforms.
  • the first terminal device needs to set the first queue information, the first queue information includes the first queue name, and the data exchange center needs to subscribe to the first queue name in advance; the first front-end device sends the first queue name to the first queue name.
  • the task request message sent by the front-end device includes the first queue information and the task identifier.
  • the first message middleware of the first front-end device receives the task request message from the first terminal device, it saves the task request message to Under the first queue name, since the data exchange center has subscribed to the first queue name, the first message middleware will send the task request message to the data exchange center to realize the sending of the task request message.
  • the queue mode there is only one consumer, that is, the task request message can only be sent to one data exchange center.
  • the data exchange center is provided with a message agent module, which is used to realize the receiving, sending and triggering of data processing tasks of message middleware messages.
  • the data exchange center can also provide a visual interface for users to configure, for example, through the platform of the data interaction center to configure the business system configuration middleware notification message interface, configuration task identification and data processing task association mapping.
  • the above-mentioned configuration can be performed locally in the data exchange center, or can be configured by remotely accessing the data interaction center, for example, through a visual operation interface provided by a browser or a software program.
  • the message broker module realizes the reception of message middleware messages by subscribing to middleware messages.
  • the message broker module can adopt topic mode or queue mode to realize message subscription and reception.
  • topic mode adopted, the message broker module is set to subscribe to the first message topic.
  • the first message middleware receives the task request information including the first message subject message, it will send the task request information to the message agent module.
  • queue mode adopted, the message agent module subscribes to the first queue name, and after the first message middleware receives task request information including the first queue name, the task request information is sent to the message agent module.
  • the message agent module After the message agent module receives the task request message, it obtains the task ID. Since the data exchange center has established a mapping between the task ID and the data processing task, the task ID can trigger the ETL tool to execute the corresponding data processing task. According to the data processing task mapped by the task identifier, the task data corresponding to the task identifier is obtained from the first intermediate library of the first front-end device, and the task data is processed and then written to the second intermediate library of the second front-end device. Another embodiment is that for platform data interactions with common data formats, the ETL tool may not process the task data, and directly load the task data from the task data in the first intermediate library to the second intermediate library. in.
  • the ETL tool After the ETL tool completes the data processing task, it needs to notify the second terminal device to receive the task data. At this time, the ETL tool sends the notification information to the message broker module through the message middleware component. After the message broker module receives the notification information, it sends the notification information to the message broker through the message middleware mechanism.
  • the second terminal device sends a task notification message, where the task notification message includes a task identifier associated with the task data.
  • the message agent module sends a task notification message to the second middleware of the second front-end device, where the task notification message includes the task identifier associated with the task data, and the second middleware sends the task notification message according to the task notification message.
  • the task notification message is sent to the second terminal device.
  • the task notification message includes the second message topic information, the second message topic information includes the second message topic, and the second terminal device has subscribed to the second message topic, so the second middleware will The task notification message is sent to the second terminal device.
  • the task notification message includes second queue information, the second queue information includes the second queue name, and the second terminal device subscribes to the second queue name, so the second middleware notifies the task The message is sent to the second terminal device.
  • the second terminal device When the second terminal device receives the task notification message, it knows that the processed task data has been stored in the second front-end device, and the second terminal device responds to the task notification message from the second intermediate library of the second front-end device. Extract the task data corresponding to the task identifier.
  • the active control of ETL tasks is realized through the message middleware mechanism, without manual execution or by setting execution strategies, the processing process of ETL tasks can be controlled according to business needs and execution conditions, which can be effective with business It can be combined with a wide range of applications.
  • the message middleware mechanism can realize the decoupling of the platform and the application system, reduce the difficulty of development and maintenance, and has good versatility.
  • the terminal device described in the embodiment of the present application may be various electronic devices, such as a computer, a mobile terminal, a server, or Other electronic devices with a processor and data storage function, such as external processing modules, distributed devices, etc., the method includes but not limited to the following steps:
  • Step 101 Obtain task data, and send the task data to a first front-end device
  • Step 102 Send a task request message to a first message middleware of the first front-end device, where the task request message includes a task identifier associated with the task data.
  • the terminal device sends the task data to the first front-end device, it sends a task request message to the first message middleware of the first front-end device for passing through the message middleware of the first message middleware.
  • the software mechanism sends the task request message to the data exchange center to trigger or control the execution of the data processing task.
  • the task request message includes the task identifier associated with the task data, so the data exchange center can identify the task identifier and execute the data processing task corresponding to the task identifier.
  • the task request message containing the task identifier can be sent to the first message middleware to realize the control of the data processing task processing.
  • control information of the task is sent using the message middleware mechanism, on the one hand, the control of the data processing task can be realized more conveniently, and it is easy to be combined with the business. On the other hand, it can realize the decoupling of the platform and the application system, reducing the development and The difficulty of maintenance has good versatility.
  • the task request message conforms to a message middleware communication specification, such as a JMS message conforming to the JMS specification or a Kafka message conforming to the Kafka specification.
  • the message middleware specification includes a topic mode and a queue mode.
  • the task request message When the task request message is sent in the topic mode, the task request message includes the first message topic message; when the task request message is sent in the queue mode, the task request message includes the first message.
  • the first message subject message or the first queue message is generated by the system according to an agreement or set by the user according to an agreement, for example, it may be input by the user through a visual interface.
  • the first terminal device may search for connection factory objects and sending target objects through JNDI (Java Naming and Directory Interface, Java Naming and Directory Service Interface).
  • JNDI is a standard Java naming system interface provided by SUN.
  • JNDI provides a unified client API.
  • the manager maps the JNDI API to a specific naming service and directory system. , So that Java applications can interact with these naming services and directory services.
  • JNDI implements high-reliability JNDI.
  • JNDI's load balancing and error recovery are ensured.
  • an application server in the cluster guarantees the independence of the local JNDI tree and has a global JNDI tree.
  • Each application server binds the deployed service object to its own local JNDI tree, and at the same time it binds to a shared global JNDI tree to realize the connection between the global JNDI and its own JNDI.
  • a data processing method provided by an embodiment of the present application is applied to a front-end device.
  • the front-end device described in the embodiment of the present application refers to an intermediate device used in the field.
  • ATM, POS, smart card, UnionPay gold card, telephone banking, bond-yintong, silver tax, instant payment, provident fund management system, electronic remittance and intra-city clearing systems are used in the fields of finance, government and enterprise.
  • the front-end processor may be an external hardware device, a hardware device installed in a computer, or a front-end system simulated by a virtual machine, including an intermediate library and message middleware for storing task data.
  • the method includes but is not limited to the following steps:
  • Step 201 Receive task data from a first terminal device
  • Step 202 Receive a task request message from a first terminal device, where the task request message includes a task identifier, and the task identifier is associated with the task data.
  • Step 203 Send the task request message to the data exchange center
  • Step 204 Receive a data extraction request from the data exchange center, and send the task data to the data exchange center.
  • the front-end device is responsible for the transfer of task data and the processing of task request information. After receiving the task data from the first terminal device, the task data is stored in the intermediate library of the front-end device, and the message middleware After receiving the task request message from the first terminal device, determine the sender of the task request message, and send the task request message to the corresponding data exchange center.
  • the communication mode of the message middleware includes a topic mode and a queue mode.
  • the task request message is a topic mode
  • the task request message includes the first message topic information
  • the message middleware saves the task request message in the first message topic information Corresponding to the first message topic, and send the task request message to consumers who have subscribed to the first message topic.
  • the message middleware if the data exchange center subscribes to the first message topic, the message middleware The task request message will be sent to the data exchange center to realize the sending of the task request message.
  • the task request message When the task request message is in the queue mode, the task request message includes the first queue information, the message middleware saves the task request message under the first queue name corresponding to the first queue information, and the message middleware saves the task The request message is sent to the data exchange center corresponding to the name of the first queue to realize the sending of the task request message.
  • a data processing method provided by an embodiment of this application is applied to a data exchange center.
  • the data exchange center described in this embodiment of the application may be a server, a computer device, a terminal device, or an intermediate device.
  • a local server, a local area network server, or a cloud server can be used, or a virtual host that can build a server can be selected.
  • the method includes:
  • Step 301 Receive a task request message from a first front-end device, where the task request message includes a task identifier;
  • Step 302 Trigger a data processing task according to the task request message, extract task data associated with the task identifier in the first intermediate library of the first front-end device, and write the extracted task data to the second front-end device The second intermediate library.
  • the data exchange center mainly implements task data processing. Unlike manual or preset execution strategies in some cases, the data exchange center in this embodiment executes the data processing task in response to the task request message. After receiving the task request message from the first front-end device, the data exchange center extracts the corresponding task ID from the task request message, and executes the data processing task corresponding to the task ID, that is, from the first front-end device The task data associated with the task identifier is extracted from the first intermediate library, and the extracted task data is written into the second intermediate library of the second front-end device. For example, after extracting the task data, the task data is processed and then written into the second intermediate library of the second front-end device, so as to adapt to data specifications between different platforms.
  • step 301 further includes the following steps:
  • Step 3011 monitor the subject information of the first message
  • Step 3012 Receive a task request message corresponding to the subject information of the first message from the first front-end device, where the task request message includes a task identifier.
  • the data exchange center communicates in the topic mode of the message middleware mechanism.
  • the data exchange center subscribes to the first message topic.
  • the first front-end device receives the task request message from the first terminal device, and The task request message includes the first message subject information.
  • the first front-end device saves the task request message under the first message subject.
  • the first front-end device After the data exchange center monitors the first message subject message, the first front-end device will The task request message is sent to the data exchange center.
  • step 301 includes the following steps:
  • Step 3013 monitor the first queue information
  • Step 3014 Receive a task request message corresponding to the first queue information from the first front-end device, where the task request message includes a task identifier.
  • the data exchange center communicates in the queue mode of the message middleware.
  • the data exchange center monitors the first queue information.
  • the first front-end device receives the task request message from the first terminal device, and the task If the request message includes the first queue information, the first front-end device will send the task request message to the data exchange center.
  • the data exchange center includes an ETL tool and a message proxy module.
  • the ETL tool is responsible for performing data processing tasks
  • the message proxy module is responsible for receiving and sending messages that control the data processing.
  • the communication interface of the data exchange center needs to be configured.
  • the visual interface of the interface of the data exchange center Taking the Jms message as an example, the user chooses to call the Jms notification message interface, and enters the access information of the first front-end device through the visual interface, such as IP address, port Wait.
  • the Jms notification message interface needs to be customized according to the requirements of the service platform.
  • the Jms interface in the above embodiment and its interface meaning are as follows:
  • the user After configuring the first front-end device notification message interface, the user configures the message service that needs to be monitored through the message middleware service configuration interface.
  • the message middleware service configuration interface Refer to Figure 17, taking the Jms message specification as an example, and select the corresponding Jms interface and the corresponding Jms specification
  • the data exchange center monitors the subscribed message topic, it can obtain the jms message corresponding to the subscribed message topic through the first message middleware of the first front-end device.
  • the data exchange center and the first terminal device The agreed message topic is the first message topic, that is, the data exchange center subscribes to the first message topic, and the task request message sent by the first terminal device also includes the first topic information.
  • the task request information sent by the first terminal device can be passed through the message middleware. It is sent to the data exchange center, and the corresponding task identifier can be obtained through the above-mentioned Jms message interface.
  • the task identifier in Table 1 is the table name and the primary key value.
  • Kafka notification interface is selected.
  • Kafka notification interface is also customized according to the requirements of the business platform.
  • Kafka interface and its interface in this embodiment The meaning is as follows:
  • the user configures the message service that needs to be monitored through the message middleware service configuration interface, selects the corresponding Kafka interface and the message processing plug-in corresponding to the Kafka specification, and configures the message topic (Topic) that needs to be subscribed.
  • the data exchange center monitors the subscribed message topic, it can obtain the Kafka message corresponding to the subscribed message topic through the first message middleware of the first front-end device.
  • the data exchange center and the first terminal device The agreed message topic is the first message topic, that is, the data exchange center subscribes to the first message topic, and the task request message sent by the first terminal device also includes the first topic information. Therefore, the task request information sent by the first terminal device can be passed through the message middleware. It is sent to the data exchange center, and the corresponding task identifier can be obtained through the Kafka message interface mentioned above.
  • the task identifiers in Table 2 above are the database name and the table name.
  • the data exchange center needs to pre-configure the mapping relationship between the agreed task identifier and the data processing task.
  • the user configures the task mapping through the ETL task mapping interface, and the user enters more than one task identifier in the keyword column , Select the corresponding ETL task in the ETL task name column, so that the mapping relationship between the task identifier and the data processing task is established.
  • users can create, delete, start, modify, and filter services on the service-driven management interface.
  • One-to-one mapping relationship between multiple task identifications and multiple data processing tasks can be set, and the mapping relationship between one task identification and multiple data processing tasks can also be set, multiple data processing corresponding to one task identification Tasks can be executed in the form of task sets.
  • the data exchange center After the data exchange center obtains the task identifier, it triggers the ETL tool to execute the corresponding data processing task or task set according to the pre-configured mapping relationship between the task identifier and the data processing task.
  • the ETL tool extracts the task data corresponding to the task identifier from the first intermediate library of the first intermediate device, processes the task data and writes it into the second intermediate library of the second intermediate device.
  • a data processing method is provided for an embodiment of this application, which is applied to a data exchange center, and includes the following steps:
  • Step 301 Receive a task request message from a first front-end device, where the task request message includes a task identifier;
  • Step 302 Trigger a data processing task according to the task request message, extract task data associated with the task identifier in the first intermediate library of the first front-end device, and write the extracted task data to the second front-end device The second intermediate library.
  • Step 303 Send a task notification message to the second message middleware of the second front-end device, where the task notification message includes a task identifier associated with the task data.
  • the data processing center sends a task notification message to the second front end processor of the second terminal device.
  • the task notification message is also sent through the message middleware mechanism, and the task notification message is sent to the message middleware of the second front-end device, wherein the task notification message includes the task identifier corresponding to the processed task data
  • the same task identifier as the task request message is used, for example, the table name and primary key value of the data table.
  • different task IDs can also be set as required.
  • the message broker module is notified through the message middleware output component to send a task notification message to the user of the message.
  • the message agent module is the Jms agent.
  • the sent task request message In order to adapt to the message middleware mechanism, the sent task request message must conform to the corresponding format. If the topic mode is adopted, the sent task request message includes the second message subject information, and the second message subject information includes the second subject, The second topic needs to be agreed with the second terminal device, that is, the second terminal device subscribes to the second topic. If the queue mode is adopted, the sent task request message includes the second queue information, and similarly, the second terminal device needs to subscribe to the second queue information.
  • the task request message can adopt the JMS message format or the Kafka message format.
  • the data exchange center can search for connection factory objects and sending target objects through JNDI (Java Naming and Directory Interface, Java Naming and Directory Service Interface).
  • JNDI Java Naming and Directory Interface, Java Naming and Directory Service Interface
  • an embodiment of the present application provides a data processing method, which is applied to a front-end device.
  • the front-end device in the embodiment of the present application refers to an intermediate device used in the field.
  • ATM, POS, smart card, UnionPay gold card, telephone banking, bond-yintong, silver tax, instant payment, provident fund management system, electronic remittance and intra-city clearing systems are used in the fields of finance, government and enterprise.
  • the front-end processor may be an external hardware device, a hardware device installed in a computer, or a front-end system simulated by a virtual machine, including an intermediate library and message middleware for storing task data.
  • the method includes but is not limited to the following steps:
  • Step 401 receiving task data from the data exchange center
  • Step 402 Receive a task notification message from the data exchange center, where the task notification message includes a task identifier, and the task identifier is associated with the task data.
  • Step 403 Send the task notification message to the second terminal device
  • Step 404 Receive a data extraction request from a second terminal device, and send the task data to the second terminal device.
  • the front-end device is responsible for the transfer of task data and the processing of task request information.
  • the task data is stored in the intermediate library of the front-end device, and the message middleware After receiving the task request message from the data exchange center, determine the sender of the task request message, and send the task request message to the corresponding second terminal device.
  • the communication mode of the message middleware includes a topic mode and a queue mode.
  • the task notification message includes the second message topic information
  • the message middleware saves the task notification message to the second message topic information Corresponding to the second message topic, and send the task notification message to consumers who have subscribed to the second message topic.
  • the message will be The software sends the task notification message to the second terminal device to realize the sending of the task notification message.
  • the task notification message When the task notification message is in the queue mode, the task notification message includes the second queue information, the message middleware saves the task notification message under the second queue name corresponding to the second queue information, and the message middleware saves the task The notification message is sent to the second terminal device corresponding to the second queue name to realize the sending of the task notification message.
  • an embodiment of the application provides a data receiving method, which is applied to a terminal device, and is applied to a terminal device.
  • the terminal device described in the embodiment of the application may be various electronic devices, such as computers and mobile terminals.
  • Server or other electronic equipment with processor and data storage function, such as external processing module, distributed equipment, etc., the method includes but not limited to the following steps:
  • Step 501 Receive a task notification message from a second front-end device, where the task notification message includes a task identifier.
  • Step 502 Extract the task data associated with the task identifier in the second intermediate library of the second front-end device according to the task notification message.
  • the terminal device is the user of the task data.
  • the terminal device receives the task notification message through the second front-end device, it learns that the task data has been stored in the database of the second front-end device. Extract the task data associated with the task identifier in the second intermediate library of the second front-end device according to the task identifier in the task notification message. Since the second terminal device only needs to perform the data extraction operation in response to the task notification message, there is no need to perform data extraction manually or by setting an execution strategy, and can cooperate to control the transmission and transmission of data tasks according to business needs and execution conditions.
  • the processing process can be effectively combined with the business and has a wide range of applications.
  • the message middleware mechanism can realize the decoupling of the platform and the application system, reduce the difficulty of development and maintenance, and has good versatility.
  • step 501 further includes the following steps:
  • Step 5011 monitor the second topic information
  • Step 5012 Receive a task notification message corresponding to the second message subject information from the second front-end device, where the task notification message includes a task identifier.
  • the second terminal device communicates in the topic mode of the message middleware, and the second terminal device subscribes to the second message topic.
  • the second front-end device receives the task request message from the data exchange center, and The task request message includes the second message subject information, and the second front-end device saves the task request message under the second message subject.
  • the second front-end device After the second terminal device monitors the second message subject message, the second front-end device will The task request message is sent to the second terminal device.
  • step 501 includes the following steps:
  • Step 5013 monitor the second queue information
  • Step 5014 Receive a task notification message corresponding to the second queue information from the second front-end device, where the task request message includes a task identifier;
  • the second terminal device communicates in the queue mode of the message middleware.
  • the second terminal device monitors the second queue information.
  • the second front-end device receives the task notification message from the data exchange center, the If the task notification message includes the second queue information, the second front-end device will send the task notification message to the second terminal device.
  • the terminal device 100 may be any type of various electronic devices, such as a computer, a mobile terminal, a server, or other devices with a processor and data storage function.
  • Electronic equipment such as external processing modules, distributed equipment, etc.
  • the terminal device 100 includes: a memory 101, a processor 102, and a computer program (not shown in the figure) that is stored on the memory 101 and can run on the processor 102.
  • the processor 102 and the memory 101 can pass through a bus. Or connect in other ways. In Fig. 13, connection through a bus is taken as an example.
  • the non-transitory software programs and instructions required to implement the data sending method or data receiving method applied to the terminal device in the above embodiment are stored in the memory 101, and when executed by the processor 102, the data of the terminal device in the above embodiment is executed.
  • the sending method or the data receiving method for example, execute the method steps 101 to 102 in FIG. 3, the method steps 501 to 502 in FIG. 10, the method steps 5011 to 5012 in FIG. 11, and the method step 5013 in FIG. 12 described above. To 5014.
  • the terminal front-end device 200 can be any type of various electronic devices, such as a computer, a mobile terminal, a server, or a processor and storage data. Functional other electronic equipment, such as external processing modules, distributed equipment, etc.
  • the front-end device 200 includes: a memory 201, a processor 202, and a computer program (not shown in the figure) that is stored on the memory 201 and can run on the processor 202, and the processor 202 and the memory 201 can pass through
  • the bus or other means are connected.
  • the bus connection is taken as an example.
  • the non-transitory software programs and instructions required to implement the data processing method applied to the front-end device in the foregoing embodiment are stored in the memory 201, and when executed by the processor 202, the data processing method of the front-end device in the foregoing embodiment is executed For example, the method steps 201 to 204 in FIG. 4 and the method steps 401 to 404 in FIG. 9 described above are executed.
  • FIG. 15 shows, an embodiment of the present application provides a data exchange center 300, the data exchange center 300, the data exchange center 300 can be any type of various electronic equipment, such as computers, mobile terminals, servers or Processors and other electronic devices that store data functions, such as external processing modules, distributed devices, etc.
  • various electronic equipment such as computers, mobile terminals, servers or Processors and other electronic devices that store data functions, such as external processing modules, distributed devices, etc.
  • the data exchange center 300 includes: a memory 301, a processor 302, and a computer program (not shown in the figure) that is stored on the memory 301 and can run on the processor 302.
  • the processor 302 and the memory 301 can be It is connected through a bus or other means. In FIG. 15, the connection through a bus is taken as an example.
  • the non-transitory software programs and instructions required to implement the data processing method applied to the data exchange center 300 in the foregoing embodiment are stored in the memory 301, and when executed by the processor 302, the data processing of the front-end device in the foregoing embodiment is executed
  • the method for example, executes the method steps 301 to 302 in FIG. 5, the method steps 3011 to 3012 in FIG. 6, the method steps 3013 to 3014 in FIG. 7, and the method steps 301 to 303 in FIG. 8 described above.
  • an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or a controller, for example, as shown in FIG.
  • the execution of one of the processors 102 in 13 can make the above-mentioned processor 102 execute the data sending method of the terminal device in the above-mentioned embodiment, for example, execute the above-described method steps 101 to 102 in FIG. 3.
  • being executed by a processor 102 in FIG. 13 can cause the processor 102 to execute the data receiving method of the terminal device in the foregoing embodiment. For example, to execute the method steps 501 to 502 in FIG. 10 described above, and the steps in FIG. 11 Method steps 5011 to 5012, method steps 5013 to 5014 in FIG. 12.
  • being executed by a processor 202 in FIG. 14 can cause the processor 202 to execute the data processing method of the front-end device in the foregoing embodiment, for example, to execute the method steps 201 to 204 in FIG. 4 and FIG. 9 described above. Steps 401 to 404 in the method.
  • execution by a processor 302 in FIG. 15 can cause the processor 302 to execute the data processing method of the data exchange center in the foregoing embodiment, for example, to execute the method steps 301 to 302 in FIG. 5 and FIG. 6 described above.
  • the device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the embodiment of the application includes: acquiring task data, sending the task data to a first front-end device, and sending a task request message to the first message middleware of the first front-end device.
  • the task identifier associated with the task data receiving task data from a first terminal device, receiving a task request message from the first terminal device, the task request message including a task identifier, the task identifier is associated with the task data,
  • the task request message is sent to the data exchange center, the data extraction request from the data exchange center is received, and the task data is sent to the data exchange center; the task request message is received from the first front-end device, the task request
  • the message includes a task identifier; a data processing task is triggered according to the task request message, task data associated with the task identifier in the first intermediate library of the first front-end device is extracted, and the extracted task data is written into the second front-end device
  • the second intermediate library of the device receives the task data from the data exchange center; receives the task notification message from the data exchange
  • the task identifier is associated with the task data, and the task data and the task request message are transmitted separately to realize the effective control of the data processing task, which improves the efficiency of data interaction.
  • the message middleware communication mechanism can be used. Improve the versatility of docking different services.
  • the active control of data tasks is realized through the message middleware mechanism, without manual execution or by setting execution strategies, the processing process of data tasks can be controlled according to business needs and execution conditions, and it can be effectively carried out with business. Combined, the scope of application is wide.
  • the message middleware mechanism can realize the decoupling of the platform and the application system, reduce the difficulty of development and maintenance, and has good versatility.
  • computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

数据发送方法、处理方法、接收方法及其设备、存储介质。其中，所述数据处理方法包括：接收来自第一前置设备的任务请求消息，所述任务请求消息包括任务标识（301），根据所述任务请求消息触发数据处理任务，抽取第一前置设备第一中间库中与所述任务标识关联的任务数据，并将所抽取的任务数据写入第二前置设备的第二中间库（302）。

Description

数据发送方法、处理方法、接收方法及其设备、存储介质
相关申请的交叉引用
本申请基于申请号为201911080915.7、申请日为2019年11月07日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于信息管理技术领域，尤其涉及一种数据发送方法、处理方法、终端设备、前置设备、数据交换中心及其接收方法及计算机可读存储介质。
背景技术
随着政府、企业电子信息化建设的进一步推进，政企组织内部各系统之间的数据交流需求也在不断加强。然而，各个系统设计建设的时期不同、业务模式不同，信息化建设缺乏整体的、统一的设计。多数系统是由不同厂商在不同的平台架构上，使用了不同的技术开发，信息共享交互困难，存在了大量的信息孤岛和流程孤岛。
为了有效整合分散异构的信息资源，消除“信息孤岛”现象，现有的数据服务系统上，通常任务的调度多为手工执行或通过设定执行策略，任务根据设定脚本固定时间启动，但任务何时完成以及执行结果并不能及时通知第三方业务系统，只能通过运维定期人工查看，无法有效的和实际业务相结合。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
第一方面，本申请实施例提供了一种数据发送方法，应用于终端设备，包括：获取任务数据，将所述任务数据发送至第一前置设备；向所述第一前置设备的第一消息中间件发送任务请求消息，所述任务请求消息包括与所述任务数据关联的任务标识。
第二方面，本申请实施例提供了一种数据处理方法，应用于前置设备，包括：接收来自第一终端设备的任务数据；接收来自第一终端设备的任务请求消息，所述任务请求消息包括任务标识，所述任务标识与所述任务数据关联；将所述任务请求消息发送至数据交换中心；接收来自数据交换中心的数据抽取请求，将所述任务数据发送至所述数据交换中心。
第三方面，本申请实施例还提供了一种数据处理方法，应用于数据交换中心，包括：接收来自第一前置设备的任务请求消息，所述任务请求消息包括任务标识；根据所述任务请求消息触发数据处理任务，抽取第一前置设备第一中间库中与所述任务标识关联的任务数据，并将所抽取的任务数据写入第二前置设备的第二中间库。
第四方面，本申请实施例还提供了一种数据处理方法，应用于前置设备，包括：接收来自数据交换中心的任务数据；接收来自数据交换中心的任务通知消息，所述任务通知消息包括任务标识，所述任务标识与所述任务数据关联；将所述任务通知消息发送至第二终端设备；接收来自第二终端设备的数据抽取请求，将所述任务数据发送至所述第二终端设备。
第五方面，本申请还提供了一种数据接收方法，应用于终端设备，包括：接收来自第二前置设备的任务通知消息，所述任务通知消息包括任务标识；根据所述任务通知消息，抽取所述第二前置设备第二中间库中与所述任务标识关联的任务数据。
第六方面，本申请还提供了一种终端设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如本申请第一方面实施例所述的数据发送方法，或者，实现如本申请第五方面实施例所述的数据接收方法。
第七方面，本申请还提供了一种前置设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如本申请第二方面实施例所述的数据处理方法，或者，实现本申请第四方面实施例所述的数据处理方法。
第八方面，本申请还提供了一种数据交换中心，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现本申请第三方面实施例所述的数据处理方法。
第九方面，本申请还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行第一方面实施例所述的数据发送方法，或者，用于执行第二方面实施例所述的数据处理方法，或者，用于执行第三方面实施例所述的数据处理方法，或者，用于执行第四方面实施例所述的数据处理方法，或者，用于执行第五方面实施例所述的数据接收方法。
本申请的其他特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术本申请技术方方案，并不构成对本申请技术方案的限制。
图1是现有ETL系统的系统原理图；
图2是本申请一个实施例提供的数据管理系统的系统原理图；
图3是本申请一个实施例提供的第一终端设备的数据发送方法第一实施例的方法流程图；
图4是本申请一个实施例提供的第一前置设备的数据处理方法第一实施例的方法流程图；
图5是本申请一个实施例提供的数据交换中心的数据处理方法第一实施例的方法流程图；
图6是图5步骤301一种实施方式的方法流程图；
图7是图5步骤301另一种实施方式的方法流程图；
图8是本申请一个实施例提供的数据交换中心的数据处理方法第二实施例的方法流程图；
图9是本申请一个实施例提供的第二前置设备的数据处理方法第一实施例的方法流程图
图10是本申请一个实施例提供的第一终端设备的数据接收方法第一实施例的方法流程图；
图11是图10中步骤501一种实施方式的方法流程图；
图12是图10中步骤501另一种实施方式的方法流程图；
图13是本申请一个实施方式的终端设备的结构框图；
图14是本申请一个实施方式的前置设备的结构框图；
图15是本申请一个实施方式的数据交换中心的结构框图；
图16是本申请一个实施方式的Jms消息接口配置的可视化界面图；
图17是本申请一个实施方式的Jms消息服务配置的可视化配置界面图；
图18是本申请一个实施方式的Kafka消息服务配置的可视化配置界面图；
图19是本申请一个实施方式的ETL任务映射的可视化配置界面图；
图20是本申请一个实施方式的服务驱动管理界面图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不 用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
为了有效整合分散异构的信息资源，消除“信息孤岛”现象，目前需要采用ETL(Extract-Transform-Load，抽取-转换-加载)工具编排处理任务，参照图1所示，为现有ETL系统结构，用户从分布的、异构数据源中提取出所需的数据，按照预先设计好的规则对抽取到的数据进行转换或清洗，最终按照预先定义好的数据仓库模型，将处理后的数据加载到数据仓库中去。但是不同异构数据源并没有规划好的统一的目标数据，而ETL的核心是转换过程，抽取和加载可以作为转换的输入和输出。
目前ETL任务的调度多为手工执行或通过设定执行策略，例如任务根据设定脚本固定时间启动，但任务何时完成以及执行结果并不能及时通知第三方业务系统，只能通过运维定期人工查看数据的抽取、转换、加载是否完成，无法有效的和实际业务相结合。
基于此，本申请实施例提供了一种数据发送方法、处理方法、接收方法、终端设备、前置设备、数据交换中心及其计算机可读存储介质，实现对数据处理任务的有效控制，提高了数据交互的效率，提高对接不同业务平台的通用性和结合程度。
参照图2所示，图2是本申请一个实施例提供的数据管理系统的系统原理图，该系统可以包括但不限于第一终端设备、第一前置设备、数据交换中心、第二前置设备和第二终端设备。其中第一终端设备和第二终端设备可以为各种的电子设备，例如计算机、移动终端、服务器或具有处理器和存储数据功能的其他电子设备，例如外置处理模块，分布式设备等。所述第一终端设备和第二终端设备可以分别处于不同的业务平台，这时第一终端设备的任务数据不能直接传输到第二终端设备，需要通过ETL工具对数据进行提取、转换、加载到第二终端设备，例如图2所示的数据交换中心包括ETL工具的服务器，通过该ETL工具能够实现任务数据的提取、转换、加载。第一前置设备设置于第一终端设备与数据交换中心之间用于协调第一终端设备与数据交换中心的通信过程，第二前置设备设置于第二终端设备和数据交换中心之间用于协调第二终端设备和数据交换中心的通信过程。
所述第一前置设备和第二前置设备可以为前置机，从网络和安全角度来看，前置机有隔离主机的作用，保证外部的应用不能直接访问核心服务，比如银行的各类外部接口(电信代收费、银证通)。从业务角度来看，前置机提供了业务渠道与核心服务的主机交流的一个桥梁。它一般起着管理和调度业务渠道发起的交易的作用，经过前置机的调用可以减轻核心后台服务器的负担。目前政企内外网两端的业务系统需要数据交换，在各自业务系统前布置前置机，实现数据交换。本实施例中，第一前置设备和第二前置设备配置有中间库，例如第一设备的第一中间库和第二设备的第二中间库，中间库起到中转和存储任务数据的功能，为了安全和隔离，ETL工具不能直接抽取各个平台的任务数据，而需要将任务数据先存储在第一中间库中，再由ETL工具进行抽取，同理，ETL工具也不能直接将任务数据写入平台的存储器或数据库，而需要将任务数据先写入到第二中间库中，再由接收数据的终端设备到中间库中提取任务数据。如图2所示，第一终端设备、第一中间库、ETL工具、第二中间库、第二终端设备依次连接建立了任务数据的传输通道。
为了对任务数据的传输，处理过程进行有效的跟踪管理，实现平台和应用系统的解耦，提高数据处理的效率及能更好地适应各种平台，本申请实施例中利用消息中间件机制控制任务数据的处理过程，例如控制ETL工具的执行过程。参照图2所示，所述第一前置设备设置有第一消息中间件，所述第二前置设备设置有第二消息中间件，同时，所述第一终端设备和第二终端设备配置有消息中间件接口，以便可以通过消息中间件机制实现任务信息的传递。上述消息中间件，包括任意形式的可以面向分布式系统提高可靠和高效的数据传送服务的组件，或者其它形式的软件工具。
所述数据交换中心也设置有消息代理模块，ETL工具通过消息代理接口与所述消息代理模块通信。消息中间件机制适用于访问消息系统独立于厂商的应用程序接口(API)，它提供给应用程序创建、发送、接收和读取消息的接口，例如Java消息服务规范中的JMS消息中间件或Kafka消息中间件则是常用的消息中间件通信机制。第一中间件和第二中间件可以是Java平台的JMS或Kafka实现，也可以是非Java平台的面向消息中间件的适配器。在消息中间件通信机制中，包括消息的生产者、消费者和消息中间件，生产者发布消息，消息中间件将消息从生产者转发到消费者，消费者接收并处理消息。在本申请实施例中，第一终端设备是消息的生产者，第二终端设备为消息的消费者，数据交换中心是相对于第一终端设备的消费者，也是相对于第二终端设备的生产者，数据交换中心通过消息中间件获取来自第一终端设备的任务请求消息，数据交换中心响应所述的任务请求消息触发数据处理任务，从第一前置设备的第一中间库中提取相应的任务数据，进行数据的处理后写入到第二前置设备的第二中间库中，完成ETL任务，然后数据交换中心作为消息的生产者，通过第二前置设备的第二消息中间件向第二终端设备发送任务通知消息，以便通知第二终端设备可以从第二中间库中提取任务数据。如图2所示，所述第一终端设备、第一消息中间件、消息代理模块、第二消息中间件、第二终端设备依次连接建立了通知消息的传输通道。
由于第一终端设备、数据交换中心和第二终端设备的通知消息是通过消息中间件机制传输的，属于异步通信模式，以第一终端设备为例，第一终端设备将任务请求消息发到第一消息中间件后，无需等待数据交换中心的响应，后续的通信流程由第一消息中间件负责完成，因此实现了第一终端设备与数据交换中心的解耦。消息中间件有队列和主题模式，其中队列模式也可以称为点对点模式，一般是消费者主动拉取，确认之后就可以删除消息。即使有多个订阅者，队列中的消息只能被一个消费者消费，例如，系统A向队列发送一条信息，消息中间件发现队列所指向的目的队列实际上位于系统B，它将信息放到本地的一个特殊队列-传输队列(Transmission Queue)。建立一条从系统A到系统B的消息通道，消息通道代理将从传输队列中读取消息，并传递这条信息到系统B，然后等待确认。只有消息中间件接到系统B成功收到信息的确认之后，它才从传输队列中真正将该信息删除。主题模式也称为发布/订阅模式，发布/订阅功能使消息的分发可以突破目的队列地理指向的限制，使消息按照特定的主题甚至内容进行分发，用户或应用程序可以根据主题或内容接收到所需要的消息。发布/订阅功能使得发送者和接收者之间的耦合关系变得更为松散，发送者不必关心接收者的目的地址，而接收者也不必关心消息的发送地址，而只是根据消息的主题进行消息的收发。
参照图2所示，本申请一个实施例提供的系统，第一终端设备的任务数据需要发送到第二终端设备，由于第一终端设备和第二终端设备所处的平台不同，数据不能直接互通，需要通过ETL工具对任务数据进行抽取、转换、加载到第二终端设备。
第一终端设备、数据交换中心和第二终端设备配置有与消息中间件通信的接口和/或插件，第一终端设备获取需要处理的任务数据及需要指示ETL工具如何对该任务数据进行处理的任务内容。
第一终端设备获取任务标识，所述任务标识可以是系统自动生成或由用户输入或配置，例如可以在任务数据中提取关键字自动生成任务标识，或者可以向用户提供可视化界面，供用户输入或配置。所述任务标识与任务数据关联，即数据交换中心能够根据该任务标识对相关的任务数据进行处理，任务标识与任务数据的关联，可以和数据交换中心、第二终端设备预先约定任务标识和任务数据的关系，或者通过映射的方式建立任务标识和任务数据的联系，也可以提取任务数据的信息与任务标识进行关联，例如将任务数据的数据库名称或数据表名称作为任务标识，则自动建立了任务标识与任务数据的关联。
所述任务标识可以约定为各种消息类型，例如上述的数据库名称或数据表名称等。第一终端设备依据上述的任务标识和配置好的消息中间件接口信息生成任务请求消息，即所 述任务请求消息包括两部分内容，一部分为用于指示消息发送对象，另一部分为用于指示ETL工具如何执行任务，例如一种实施方式中，任务标识用于指示ETL工具的处理数据对象，为任务数据的数据表名称，ETL工具的任务触发通过任务内容消息触发提取对应的任务数据。另一种实施方式中，所述任务标识除了用于指示ETL工具的处理数据对象外，还用于指示ETL工具执行对应的任务，这时需要数据交换中心约定或设置任务标识与数据处理任务的关联，第一终端设备只需要将所述任务标识发送至数据交换中心，即可指示ETL工具执行指定的ETL任务。
第一终端设备首先将待处理的任务数据发送至第一前置设备的第一中间库中，可以采用串行或并行的方式进行发送，任务数据的发送方式在此不再赘述。第一终端设备通过第一前置设备的第一消息中间件将所述任务请求消息发送至数据交互中心，如上所述，可以通过队列或主题模式发送。
当采用主题模式时，第一终端设备需要设置第一消息主题信息，所述第一消息主题信息包括用于对消息进行分类的第一消息主题，数据交换中心需要预先订阅所述第一消息主题；第一终端设备向第一前置设备发送的任务请求消息包括所述第一消息主题信息和任务标识，当第一前置设备的第一消息中间件接收来自第一终端设备的任务请求消息，将所述任务请求消息保存到第一消息主题下，由于数据交换中心订阅了所述的第一消息主题，因此第一消息中间件会将所述的任务请求消息发送至数据交互中心，实现任务请求消息的发送。参照图2所示，本实施例中，给出了一个第一终端设备和一个第二终端设备，在另一些实施例中，也可以设置多个终端设备并对应配置前置设备，这时所述数据交换中心可以订阅多个终端设备的多条消息主题，该实施例适用于对多个对象的数据发送任务，例如任务请求信息的任务内容是将当前任务数据发送给多个第三方平台。
当采用队列模式时，第一终端设备需要设置第一队列信息，所述第一队列信息包括第一队列名称，数据交换中心需要预先订阅所述第一队列名称；第一前置设备向第一前置设备发送的任务请求消息包括所述第一队列信息和任务标识，当第一前置设备的第一消息中间件接收来自第一终端设备的任务请求消息，将所述任务请求消息保存到第一队列名称下，由于数据交换中心订阅了所述的第一队列名称，因此第一消息中间件会将所述的任务请求消息发送至数据交换中心，实现任务请求消息的发送。在队列模式下只有一个消费者，即所述任务请求消息只会发送到一个数据交换中心。
数据交换中心设置有消息代理模块，用于实现消息中间件消息的接收、发送和触发数据处理任务。其中数据交换中心也可以提供可视化界面让用户进行配置，例如通过数据交互中心的平台配置业务系统配置中间件通知消息接口、配置任务标识与数据处理任务的关联映射。上述配置可以在数据交换中心本地进行，也可以远程访问数据交互中心进行配置，例如通过浏览器或软件程序提供的可视化操作界面进行配置。
所述消息代理模块通过订阅中间件消息实现消息中间件消息的接收，消息代理模块可以采用主题模式或队列模式实现消息的订阅和接收，当采用主题模式时，设置消息代理模块订阅第一消息主题，当第一消息中间件接收到包括第一消息主题消息的任务请求信息后，会将所述任务请求信息发送至消息代理模块。同理，当采用队列模式时，消息代理模块订阅了第一队列名称，第一消息中间件接收到包括第一队列名称的任务请求信息后，所述任务请求信息发送至消息代理模块。
消息代理模块接收到任务请求消息后，获得任务标识，由于数据交换中心建立了任务标识与数据处理任务之间的映射，因此通过该任务标识即可触发ETL工具执行对应的数据处理任务，ETL工具根据任务标识映射的数据处理任务从第一前置设备的第一中间库中获取任务标识对应的任务数据，对所述任务数据进行处理后写入到第二前置设备的第二中间库。另一种实施方式是，对于数据格式共通的平台数据交互，ETL工具也可以不对所述的任务数据进行处理，直接将所述任务数据从第一中间库中的任务数据加载到第二中间库中。
ETL工具完成数据处理任务后，需要通知第二终端设备接收任务数据，这时ETL工具 通过消息中间件组件向消息代理模块发送通知信息，消息代理模块接收到通知信息后，通过消息中间件机制向第二终端设备发送任务通知消息，其中所述任务通知消息包括与所述任务数据关联的任务标识。具体地，消息代理模块向第二前置设备的第二中间件发送任务通知消息，所述任务通知消息包括与所述任务数据关联的任务标识，第二中间件根据所述任务通知消息，将任务通知消息发送至第二终端设备。当采用主题模式通信时，任务通知消息中包括第二消息主题信息，所述第二消息主题信息包括第二消息主题，第二终端设备订阅了第二消息主题，因此第二中间件将所述任务通知消息发送至第二终端设备。当采用队列模式通信时，任务通知消息中包括第二队列信息，所述第二队列信息包括第二队列名称，第二终端设备订阅了第二队列名称，因此第二中间件将所述任务通知消息发送至第二终端设备。
当第二终端设备接收到任务通知消息后，得知处理好的任务数据已经存储在第二前置设备，第二终端设备响应所述的任务通知消息从第二前置设备的第二中间库中提取对应所述任务标识的任务数据。
本申请上述实施例中，通过消息中间件机制实现了对ETL任务的主动控制，无需手工执行或通过设定执行策略，可根据业务的需要和执行条件控制ETL任务的处理过程，能够与业务有效进行结合，适用范围广。同时，采用消息中间件机制能够实现平台与应用系统的解耦，降低了开发和维护的难度，具有较好的通用性。
参照图3所示，是本申请一个实施例提供的一种数据发送方法，应用于终端设备，本申请实施例所述的终端设备可以为各种的电子设备，例如计算机、移动终端、服务器或具有处理器和存储数据功能的其他电子设备，例如外置处理模块，分布式设备等，所述方法包括但不限于以下步骤：
步骤101，获取任务数据，将所述任务数据发送至第一前置设备；
步骤102，向所述第一前置设备的第一消息中间件发送任务请求消息，所述任务请求消息包括与所述任务数据关联的任务标识。
本实施例中，终端设备将任务数据发送到第一前置设备后，再向第一前置设备的第一消息中间件发送任务请求消息，用于通过所述第一消息中间件的消息中间件机制将所述的任务请求消息发送至数据交换中心，以便触发或控制数据处理任务的执行。所述任务请求消息包括与所述任务数据关联的任务标识，因此数据交换中心能够识别该任务标识并执行对应所述任务标识的数据处理任务，对于第一前置设备来说，只需要按约定向第一消息中间件发送包含任务标识的任务请求消息即可实现对数据处理任务处理的控制。由于任务的控制信息是利用消息中间件机制进行发送，一方面能够更方便地实现数据处理任务的控制，便于与业务进行结合，另一方面能够实现平台与应用系统的解耦，降低了开发和维护的难度，具有较好的通用性。
本申请一实施例中，所述任务请求消息符合消息中间件通信规范，例如符合JMS规范的JMS消息或符合Kafka规范的Kafka消息。
消息中间件规范有主题模式和队列模式，当采用主题模式发送任务请求消息时，所述任务请求消息包括第一消息主题消息；当采用队列模式发送任务请求消息时，所述任务请求消息包括第一队列消息。所述第一消息主题消息或第一队列消息按照约定由系统生成或由用户按约定进行设置，例如可以是通过可视化界面供用户输入。
本申请一实施例中，第一终端设备可以通过JNDI(Java Naming and DirectoryInterface，Java命名和目录服务接口)查找连接工厂对象和发送目标对象。JNDI是SUN公司提供的一种标准的Java命名系统接口，JNDI提供统一的客户端API，通过不同的访问提供者接口JNDI API的实现，由管理者将JNDI API映射为特定的命名服务和目录系统，使得Java应用程序可以和这些命名服务和目录服务之间进行交互。JNDI实现了高可靠性JNDI，通过服务器的集群，保证了JNDI的负载平衡和错误恢复。在全局共享的方式下，集群中的一个应用服务器保证本地JNDI树的独立性，并拥有全局的JNDI树。每个应用服务器在把部 署的服务对象绑定到自己本地的JNDI树的同时，还绑定到一个共享的全局JNDI树，实现全局JNDI和自身JNDI的联系。
参照图4所示，本申请一个实施例提供的一种数据处理方法，应用于前置设备，本申请实施例所述的前置设备是指用于现场的中间设备。例如金融、政企领域采用前置机的有ATM、POS、智能卡、银联金卡、电话银行、券银通、银税通、即缴费、公积金管理系统、电子汇兑和同城清算等系统。所述前置机可以是一个外挂的硬件设备，也可以是设置于计算机中的一个硬件装置，也可以是虚拟机模拟的前置系统，包括用于存储任务数据的中间库和消息中间件。所述方法包括但不限于以下步骤：
步骤201，接收来自第一终端设备的任务数据；
步骤202，接收来自第一终端设备的任务请求消息，所述任务请求消息包括任务标识，所述任务标识与所述任务数据关联；
步骤203，将所述任务请求消息发送至数据交换中心；
步骤204，接收来自数据交换中心的数据抽取请求，将所述任务数据发送至所述数据交换中心。
本实施例中，前置设备负责任务数据的中转及任务请求信息的处理，当接收来自第一终端设备的任务数据后，将所述任务数据存储于前置设备的中间库中，消息中间件接收到来自第一终端设备的任务请求消息后，判断任务请求消息的发送对象，将所述任务请求消息发送至相应的数据交换中心。
消息中间件的通信模式包括主题模式和队列模式，当所述任务请求消息为主题模式时，任务请求消息包括第一消息主题信息，消息中间件将所述任务请求消息保存到第一消息主题信息对应的第一消息主题下，并将所述任务请求消息发送给订阅了所述第一消息主题的消费者，在本实施例中，若数据交换中心订阅了第一消息主题，则消息中间件会将所述的任务请求消息发送至数据交换中心，实现任务请求消息的发送。当任务请求消息为队列模式时，任务请求消息包括第一队列信息，消息中间件将所述任务请求消息保存到第一队列信息对应的第一队列名称下，同时消息中间件将所述的任务请求消息发送至对应所述第一队列名称的数据交换中心，实现任务请求消息的发送。
参照图5所示，本申请一个实施例提供的一种数据处理方法，应用于数据交换中心，本申请实施例所述的数据交换中心可以是服务器、计算机设备、终端设备、中间设备，其中服务器可以采用本地服务器、局域网服务器或云服务器，也可以选用能搭建服务器的虚拟主机，所述方法包括：
步骤301，接收来自第一前置设备的任务请求消息，所述任务请求消息包括任务标识；
步骤302，根据所述任务请求消息触发数据处理任务，抽取第一前置设备第一中间库中与所述任务标识关联的任务数据，并将所抽取的任务数据写入第二前置设备的第二中间库。
本申请实施例中，数据交换中心主要实现任务数据的处理，与在一些情况下的手工或预设执行策略不同，本实施例中的数据交换中心响应任务请求消息执行响应的数据处理任务，当数据交换中心接收到来自第一前置设备的任务请求消息后，从所述任务请求消息中提取相应的任务标识，并执行对应所述任务标识的数据处理任务，即从第一前置设备的第一中间库中提取与所述任务标识关联的任务数据，并将所抽取的任务数据写入第二前置设备的第二中间库。例如，抽取所述的任务数据后，对所述任务数据进行处理后在写入第二前置设备的第二中间库，以便适配不同平台之间的数据规范。
参照图6所示，所述步骤301还包括以下步骤：
步骤3011，监听第一消息主题信息；
步骤3012，接收来自第一前置设备与所述第一消息主题信息对应的任务请求消息，所述任务请求消息包括任务标识。
本实施例中，数据交换中心以消息中间件机制的主题模式进行通信，所述数据交换中 心订阅了第一消息主题，当第一前置设备接收到来自第一终端设备的任务请求消息，而该任务请求消息包括第一消息主题信息，第一前置设备将所述任务请求消息保存到第一消息主题下，数据交换中心监听到第一消息主题消息后，第一前置设备将所述任务请求消息发送至数据交换中心。
参照图7所示，所述步骤301的另一种实施方式，包括以下步骤：
步骤3013，监听第一队列信息；
步骤3014，接收来自第一前置设备与所述第一队列信息对应的任务请求消息，所述任务请求消息包括任务标识。
本实施例中，数据交换中心以消息中间件的队列模式进行通信，所述数据交换中心监听第一队列信息，当第一前置设备接收到来自第一终端设备的任务请求消息，而该任务请求消息包括第一队列信息，则第一前置设备会将所述的任务请求消息发送至数据交换中心。
本申请的一实施例中，所述数据交换中心包括ETL工具和消息代理模块，ETL工具负责执行数据处理任务，消息代理模块负责接收、发送控制所述数据处理的消息。
为了实现中间件消息的接收和发送，需要对数据交换中心的通信接口进行配置。首先，参照图16所示，为数据交换中心的接口的可视化界面，以Jms消息为例，用户选择调用Jms通知消息接口，通过可视化界面输入第一前置设备的访问信息，例如IP地址、端口等。其中所述Jms通知消息接口需要根据业务平台要求定制，例如，上述实施例的Jms接口及其接口含义如下所示：
{
“group”:xxx,
“id”:xxx
}
Figure PCTCN2020122254-appb-000001
表1 Jms接口含义
配置好第一前置设备通知消息接口后，用户通过消息中间件服务配置界面配置所需要监听的消息服务，参照图17所示，以Jms消息规范为例，选择对应的Jms接口及对应Jms规范的消息处理插件，配置所需订阅的消息主题(Topic)。当数据交换中心监听到所订阅的消息主题后，可通过第一前置设备的第一消息中间件获取对应所订阅消息主题的jms消息，在本实施例中，数据交换中心和第一终端设备约定消息主题为第一消息主题，即数据交换中心订阅第一消息主题，第一终端设备发送的任务请求消息也包括第一主题信息，因此第一终端设备发出的任务请求信息可以通过消息中间件发送至数据交换中心，通过上述的Jms消息接口可以获取对应的任务标识。例如表1中的任务标识为表名和主键值。
类似地，也可以采用其他的消息中间件规范，例如采用Kafka消息规范，则选择Kafka通知接口，所述Kafka通知接口也是根据业务平台需求定制的，例如，本实施例中的Kafka接口及其接口含义如下所示：
{
"data":
[{"database":"xxx","xxx":"start"}]
}
Figure PCTCN2020122254-appb-000002
Figure PCTCN2020122254-appb-000003
表2 Kafka接口含义
参照图18所示，用户通过消息中间件服务配置界面配置所需要监听的消息服务，选择对应的Kafka接口及对应Kafka规范的消息处理插件，配置所需订阅的消息主题(Topic)。当数据交换中心监听到所订阅的消息主题后，可通过第一前置设备的第一消息中间件获取对应所订阅消息主题的Kafka消息，在本实施例中，数据交换中心和第一终端设备约定消息主题为第一消息主题，即数据交换中心订阅第一消息主题，第一终端设备发送的任务请求消息也包括第一主题信息，因此第一终端设备发出的任务请求信息可以通过消息中间件发送至数据交换中心，通过上述的Kafka消息接口可以获取对应的任务标识。例如上述表2中的任务标识为数据库名和表名。
数据交换中心需要预先配置约定的任务标识和数据处理任务之间的映射关系，例如参照图19所示，用户通过ETL任务映射界面进行任务映射配置，用户在关键字一栏输入一个以上的任务标识，在ETL任务名称一栏选择对应的ETL任务，这样建立了任务标识与数据处理任务的映射关系。参照图20所示，用户可以在服务驱动管理界面对服务进行新建、删除、启动、修改和筛选的操作。其中可以设置多个任务标识与多个数据处理任务之间的一一对应的映射关系，也可以设置一个任务标识与多个数据处理任务之间的映射关系，一个任务标识对应的多个数据处理任务可以组成任务集的形式被执行。
当数据交换中心获取任务标识后，根据预先配置的任务标识与数据处理任务的映射关系触发ETL工具执行相应的数据处理任务或任务集。ETL工具从第一中间设备的第一中间库中提取对应所述任务标识的任务数据，对所述任务数据进行处理后写入到第二中间设备的第二中间库中。
参照图8所示，为本申请一实施例提供了一种数据处理方法，应用于数据交换中心，包括以下步骤：
步骤301，接收来自第一前置设备的任务请求消息，所述任务请求消息包括任务标识；
步骤302，根据所述任务请求消息触发数据处理任务，抽取第一前置设备第一中间库中与所述任务标识关联的任务数据，并将所抽取的任务数据写入第二前置设备的第二中间库。
步骤303，向所述第二前置设备的第二消息中间件发送任务通知消息，所述任务通知消息包括与所述任务数据关联的任务标识。
当数据交换中心的ETL工具执行数据处理任务后，需要通知数据的使用方接收处理后的任务数据。数据处理中心向第二终端设备的第二前置机发送任务通知消息。所述任务通知消息也通过消息中间件机制进行发送，将所述任务通知消息发送至第二前置设备的消息中间件中，其中所述任务通知消息包括与处理后的任务数据对应的任务标识，本实施例中，采用与任务请求消息相同的任务标识，例如为数据表的表名和主键值。当然也可以根据需要设置不同的任务标识。
具体地，参照图2所示，当数据交换中心的ETL工具执行完数据处理任务或任务集后，通过消息中间件输出组件通知消息代理模块向消息的使用方发送任务通知消息。以Jms消息输出组件为例，由于采用Jms消息机制，所述消息代理模块为Jms agent，ETL工具完成数据处理任务后，发送rest消息给Jms agent，所述rest消息及消息含义如下：
http://ip:port/beas/Jms/produce？content＝xxx,target＝xxx
http method：POST or GET
Figure PCTCN2020122254-appb-000004
Figure PCTCN2020122254-appb-000005
表3 rest消息含义
为了适配消息中间件机制，发送的任务请求消息需要符合相应的格式，若采用主题模式，所发送的任务请求消息包括第二消息主题信息，所述的第二消息主题信息包括第二主题，所述第二主题需要和第二终端设备进行约定，即第二终端设备订阅所述第二主题。若采用队列模式，所发送的任务请求消息包括第二队列信息，同理第二终端设备需要订阅所述第二队列信息。任务请求消息可以采用JMS消息格式或Kafka消息格式。
本申请一实施例中，数据交换中心可以通过JNDI(Java Naming and DirectoryInterface，Java命名和目录服务接口)查找连接工厂对象和发送目标对象。
参照图9所示，本申请实施例提供了一种数据处理方法，应用于前置设备，本申请实施例所述的前置设备是指用于现场的中间设备。例如金融、政企领域采用前置机的有ATM、POS、智能卡、银联金卡、电话银行、券银通、银税通、即缴费、公积金管理系统、电子汇兑和同城清算等系统。所述前置机可以是一个外挂的硬件设备，也可以是设置于计算机中的一个硬件装置，也可以是虚拟机模拟的前置系统，包括用于存储任务数据的中间库和消息中间件。所述方法包括但不限于以下步骤：
步骤401，接收来自数据交换中心的任务数据；
步骤402，接收来自数据交换中心的任务通知消息，所述任务通知消息包括任务标识，所述任务标识与所述任务数据关联；
步骤403，将所述任务通知消息发送至第二终端设备；
步骤404，接收来自第二终端设备的数据抽取请求，将所述任务数据发送至所述第二终端设备。
本实施例中，前置设备负责任务数据的中转及任务请求信息的处理，当接收来自数据交换中心处理后的任务数据，将所述任务数据存储于前置设备的中间库中，消息中间件接收到来自数据交换中心的任务请求消息后，判断任务请求消息的发送对象，将所述任务请求消息发送至相应的第二终端设备。
消息中间件的通信模式包括主题模式和队列模式，当所述任务通知消息为主题模式时，任务通知消息包括第二消息主题信息，消息中间件将所述任务通知消息保存到第二消息主题信息对应的第二消息主题下，并将所述任务通知消息发送给订阅了所述第二消息主题的消费者，在本实施例中，若第二终端设备订阅了第二消息主题，则消息中间件会将所述的任务通知消息发送至第二终端设备，实现任务通知消息的发送。当任务通知消息为队列模式时，任务通知消息包括第二队列信息，消息中间件将所述任务通知消息保存到第二队列信息对应的第二队列名称下，同时消息中间件将所述的任务通知消息发送至对应所述第二队列名称的第二终端设备，实现任务通知消息的发送。
参照图10所示，本申请实施例提供了一种数据接收方法，应用于终端设备，应用于终端设备，本申请实施例所述的终端设备可以为各种的电子设备，例如计算机、移动终端、服务器或具有处理器和存储数据功能的其他电子设备，例如外置处理模块，分布式设备等，所述方法包括但不限于以下步骤：
步骤501，接收来自第二前置设备的任务通知消息，所述任务通知消息包括任务标识；
步骤502，根据所述任务通知消息，抽取所述第二前置设备第二中间库中与所述任务标识关联的任务数据。
本申请实施例中，终端设备为任务数据的使用方，当终端设备通过第二前置设备接收任务通知消息后，得知任务数据已经存储在第二前置设备的数据库中。根据任务通知消息中的任务标识抽取所述第二前置设备第二中间库中与所述任务标识关联的任务数据。由于第二终端设备只需要响应所述任务通知消息执行响应的数据提取操作，因此无需手工执行或通过设定执行策略进行数据的提取，可根据业务的需要和执行条件配合控制数据任务的传输和处理过程，能够与业务有效进行结合，适用范围广。同时，采用消息中间件机制能 够实现平台与应用系统的解耦，降低了开发和维护的难度，具有较好的通用性。
参照图11所示，所述步骤501还包括以下步骤：
监听第二消息主题信息，接收来自第二前置设备与所述第二消息主题信息对应的任务通知消息；
步骤5011，监听第二主题信息；
步骤5012，接收来自第二前置设备与所述第二消息主题信息对应的任务通知消息，所述任务通知消息包括任务标识。
本实施例中，第二终端设备以消息中间件的主题模式进行通信，所述第二终端设备订阅了第二消息主题，当第二前置设备接收到来自数据交换中心的任务请求消息，而该任务请求消息包括第二消息主题信息，第二前置设备将所述任务请求消息保存到第二消息主题下，第二终端设备监听到第二消息主题消息后，第二前置设备将所述任务请求消息发送至第二终端设备。
参照图12所示，所述步骤501的另一种实施方式，包括以下步骤：
步骤5013，监听第二队列信息；
步骤5014，接收来自第二前置设备与所述第二队列信息对应的任务通知消息，所述任务请求消息包括任务标识；
本实施例中，第二终端设备以消息中间件的队列模式进行通信，所述第二终端设备监听第二队列信息，当第二前置设备接收到来自数据交换中心的任务通知消息，而该任务通知消息包括第二队列信息，则第二前置设备会将所述的任务通知消息发送至第二终端设备。
参照图13所示，本申请实施例提供了一种终端设备100，该终端设备100可以是任意类型的各种的电子设备，例如计算机、移动终端、服务器或具有处理器和存储数据功能的其他电子设备，例如外置处理模块，分布式设备等。
具体地，所述终端设备100包括：存储器101、处理器102及存储在存储器101上并可在处理器102上运行的计算机程序(图中未示出)，处理器102和存储器101可以通过总线或者其他方式连接，图13中以通过总线连接为例。
实现上述实施例中应用于终端设备的数据发送方法或数据接收方法所需的非暂态软件程序以及指令存储在存储器101中，当被处理器102执行时，执行上述实施例中终端设备的数据发送方法或数据接收方法，例如，执行以上描述的图3中的方法步骤101至102、图10中的方法步骤501至502、图11中的方法步骤5011至5012、图12中的方法步骤5013至5014。
参照图14所示，本申请实施例提供了一种前置设备200，该终端前置设备200可以是任意类型的各种的电子设备，例如计算机、移动终端、服务器或具有处理器和存储数据功能的其他电子设备，例如外置处理模块，分布式设备等。
具体地，所述前置设备200包括：存储器201、处理器202及存储在存储器201上并可在处理器202上运行的计算机程序(图中未示出)，处理器202和存储器201可以通过总线或者其他方式连接，图14中以通过总线连接为例。
实现上述实施例中应用于前置设备的数据处理方法所需的非暂态软件程序以及指令存储在存储器201中，当被处理器202执行时，执行上述实施例中前置设备的数据处理方法，例如，执行以上描述的图4中的方法步骤201至204、图9中的方法步骤401至404。
参照图15所示，本申请一个实施例提供一种数据交换中心300，该数据交换中心300，该数据交换中心300可以是任意类型的各种的电子设备，例如计算机、移动终端、服务器或具有处理器和存储数据功能的其他电子设备，例如外置处理模块，分布式设备等。
具体地，所述该数据交换中心300包括：存储器301、处理器302及存储在存储器301上并可在处理器302上运行的计算机程序(图中未示出)，处理器302和存储器301可以通过总线或者其他方式连接，图15中以通过总线连接为例。
实现上述实施例中应用于数据交换中心300的数据处理方法所需的非暂态软件程序以 及指令存储在存储器301中，当被处理器302执行时，执行上述实施例中前置设备的数据处理方法，例如，执行以上描述的图5中的方法步骤301至302、图6中的方法步骤3011至3012，图7中的方法步骤3013至3014，图8中的方法步骤301至303。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被一个处理器或控制器执行，例如，被图13中的一个处理器102执行，可使得上述处理器102执行上述实施例中终端设备的数据发送方法，例如，执行以上描述的图3中的方法步骤101至102。
例如，被图13中的一个处理器102执行，可使得上述处理器102执行上述实施例中终端设备的数据接收方法例如，执行以上描述的图10中的方法步骤501至502、图11中的方法步骤5011至5012、图12中的方法步骤5013至5014。
再如，被图14中的一个处理器202执行，可使得上述处理器202执行上述实施例中前置设备的数据处理方法，例如执行以上描述的图4中的方法步骤201至204、图9中的方法步骤401至404。
再如，被图15中的一个处理器302执行，可使得上述处理器302执行上述实施例中数据交换中心的数据处理方法，例如执行以上描述的图5中的方法步骤301至302、图6中的方法步骤3011至3012，图7中的方法步骤3013至3014，图8中的方法步骤301至303。
以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
本申请实施例包括：获取任务数据，将所述任务数据发送至第一前置设备，向所述第一前置设备的第一消息中间件发送任务请求消息，所述任务请求消息包括与所述任务数据关联的任务标识；接收来自第一终端设备的任务数据,接收来自第一终端设备的任务请求消息，所述任务请求消息包括任务标识，所述任务标识与所述任务数据关联,将所述任务请求消息发送至数据交换中心,接收来自数据交换中心的数据抽取请求，将所述任务数据发送至所述数据交换中心；接收来自第一前置设备的任务请求消息，所述任务请求消息包括任务标识；根据所述任务请求消息触发数据处理任务，抽取第一前置设备第一中间库中与所述任务标识关联的任务数据，并将所抽取的任务数据写入第二前置设备的第二中间库；接收来自数据交换中心的任务数据；接收来自数据交换中心的任务通知消息，所述任务通知消息包括任务标识，所述任务标识与所述任务数据关联；接收来自第二前置设备的任务通知消息，所述任务通知消息包括任务标识,根据所述任务通知消息，抽取所述第二前置设备第二中间库中与所述任务标识关联的任务数据。
根据本申请实施例提供的方案，通过任务标识与任务数据关联，任务数据与任务请求消息分别传输的方式实现对数据处理任务有效控制，提高了数据交互的效率，利用消息中间件通信机制，能提高对接不同业务的通用性。
本申请实施例中，通过消息中间件机制实现了对数据任务的主动控制，无需手工执行或通过设定执行策略，可根据业务的需要和执行条件控制数据任务的处理过程，能够与业务有效进行结合，适用范围广。同时，采用消息中间件机制能够实现平台与应用系统的解耦，降低了开发和维护的难度，具有较好的通用性。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、 可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的一些实施进行了具体说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不脱离本申请范围的前提下还可作出种种的等同变形或替换，这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (18)

  1. 一种数据发送方法，应用于终端设备，包括：
    获取任务数据，将所述任务数据发送至第一前置设备；
    向所述第一前置设备的第一消息中间件发送任务请求消息，所述任务请求消息包括与所述任务数据关联的任务标识。
  2. 根据权利要求1所述的一种数据发送方法，其中，所述任务请求消息还包括用于消息中间件通信的第一消息主题信息或第一队列信息。
  3. 根据权利要求1所述的一种数据发送方法，其中，所述任务请求消息为JMS消息或Kafka消息。
  4. 一种数据处理方法，应用于前置设备，包括：
    接收来自第一终端设备的任务数据；
    接收来自第一终端设备的任务请求消息，所述任务请求消息包括任务标识，所述任务标识与所述任务数据关联；
    将所述任务请求消息发送至数据交换中心；
    接收来自数据交换中心的数据抽取请求，将所述任务数据发送至所述数据交换中心。
  5. 根据权利要求4所述的一种数据处理方法，其中，所述将所述任务请求消息发送至数据交换中心，包括以下之一的步骤：
    所述任务请求消息包括第一消息主题信息，将所述任务请求消息发送至订阅所述第一消息主题信息的数据交换中心；
    所述任务请求消息包括第一队列信息，将所述任务请求消息发送至对应所述第一队列信息的数据交换中心。
  6. 一种数据处理方法，应用于数据交换中心，包括：
    接收来自第一前置设备的任务请求消息，所述任务请求消息包括任务标识；
    根据所述任务请求消息触发数据处理任务，抽取第一前置设备第一中间库中与所述任务标识关联的任务数据，并将所抽取的任务数据写入第二前置设备的第二中间库。
  7. 根据权利要求6所述的一种数据处理方法，其中，所述接收来自第一前置设备的任务请求消息包括以下之一的步骤：
    监听第一消息主题信息，接收来自第一前置设备与所述第一消息主题信息对应的任务请求消息；
    监听第一队列信息，接收来自第一前置设备与所述第一队列信息对应的任务请求消息。
  8. 根据权利要求6所述的一种数据处理方法，还包括以下步骤：
    向所述第二前置设备的第二消息中间件发送任务通知消息，所述任务通知消息包括与所述任务数据关联的任务标识。
  9. 根据权利要求8所述的一种数据处理方法，其中，所述任务通知消息包括用于消息中间件通信的第二消息主题信息或第二队列信息。
  10. 根据权利要求8所述的一种数据处理方法，其中，所述任务通知消息为JMS消息或Kafka消息。
  11. 一种数据处理方法，应用于前置设备，包括：
    接收来自数据交换中心的任务数据；
    接收来自数据交换中心的任务通知消息，所述任务通知消息包括任务标识，所述任务标识与所述任务数据关联；
    将所述任务通知消息发送至第二终端设备；
    接收来自第二终端设备的数据抽取请求，将所述任务数据发送至所述第二终端设备。
  12. 根据权利要求11所述的一种数据处理方法，其中，所述将所述任务通知消息发送 至第二终端设备，包括以下之一的步骤：
    所述任务通知消息包括第二消息主题信息，将所述任务通知消息发送至订阅所述第二消息主题信息的第二终端设备；
    所述任务通知消息包括第二队列信息，将所述任务通知消息发送至对应所述第二队列信息的第二终端设备。
  13. 一种数据接收方法，应用于终端设备，包括：
    接收来自第二前置设备的任务通知消息，所述任务通知消息包括任务标识；
    根据所述任务通知消息，抽取所述第二前置设备第二中间库中与所述任务标识关联的任务数据。
  14. 根据权利要求13所述的一种数据接收方法，其中，所述接收来自第二前置设备的任务通知消息，包括以下之一的步骤：
    监听第二消息主题信息，接收来自第二前置设备与所述第二消息主题信息对应的任务通知消息；
    监听第二队列信息，接收来自第二前置设备与所述第二队列信息对应的任务通知消息。
  15. 一种终端设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至3中任意一项所述的数据发送方法，或者，实现如权利要求13至14中任意一项所述的数据接收方法。
  16. 一种前置设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求4至5中任意一项所述的数据处理方法，或者，实现如权利要求11至12中任意一项所述的数据处理方法。
  17. 一种数据交换中心，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求6至10中任意一项所述的数据处理方法。
  18. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行权利要求1至3中任意一项所述的数据发送方法，或者，用于执行权利要求4至5中任意一项所述的数据处理方法，或者，用于执行权利要求6至10中任意一项所述的数据处理方法，或者，用于执行权利要求11至12中任意一项所述的数据处理方法，或者，用于执行权利要求13至14中任意一项所述的数据接收方法。
PCT/CN2020/122254 2019-11-07 2020-10-20 数据发送方法、处理方法、接收方法及其设备、存储介质 WO2021088641A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911080915.7 2019-11-07
CN201911080915.7A CN112788074B (zh) 2019-11-07 数据发送方法、处理方法、接收方法及其设备、存储介质

Publications (1)

Publication Number Publication Date
WO2021088641A1 true WO2021088641A1 (zh) 2021-05-14

Family

ID=75748207

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/122254 WO2021088641A1 (zh) 2019-11-07 2020-10-20 数据发送方法、处理方法、接收方法及其设备、存储介质

Country Status (1)

Country Link
WO (1) WO2021088641A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113487340A (zh) * 2021-05-24 2021-10-08 康键信息技术（深圳）有限公司 业务解耦处理方法、装置、设备及存储介质
CN113626211A (zh) * 2021-06-29 2021-11-09 欧电云信息科技(江苏)有限公司 消息队列的切换方法、切换系统、电子设备及存储介质
CN115150466A (zh) * 2022-06-29 2022-10-04 北京百度网讯科技有限公司 一种数据分发的实现方法、装置、电子设备及存储介质
CN115499435A (zh) * 2022-08-08 2022-12-20 中亿(深圳)信息科技有限公司 任务调度方法、系统、电子设备及计算机可读存储介质
CN115529288A (zh) * 2022-09-21 2022-12-27 上海浦东发展银行股份有限公司 一种消息推送的方法、装置、计算机设备
CN116545706A (zh) * 2023-05-15 2023-08-04 合芯科技(苏州)有限公司 一种数据安全传输控制系统、方法、装置及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557551A (zh) * 2009-05-11 2009-10-14 成都市华为赛门铁克科技有限公司 一种移动终端访问云服务的方法、装置和通信系统
CN101562774A (zh) * 2009-05-22 2009-10-21 北京立通无限科技有限公司 信息管理的方法及系统
CN102693297A (zh) * 2012-05-16 2012-09-26 华为技术有限公司 数据处理方法、节点和提取、转换和加载etl系统
US20130325788A1 (en) * 2012-05-31 2013-12-05 Cellco Partnership D/B/A Verizon Wireless Etl data transit method and system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557551A (zh) * 2009-05-11 2009-10-14 成都市华为赛门铁克科技有限公司 一种移动终端访问云服务的方法、装置和通信系统
CN101562774A (zh) * 2009-05-22 2009-10-21 北京立通无限科技有限公司 信息管理的方法及系统
CN102693297A (zh) * 2012-05-16 2012-09-26 华为技术有限公司 数据处理方法、节点和提取、转换和加载etl系统
US20130325788A1 (en) * 2012-05-31 2013-12-05 Cellco Partnership D/B/A Verizon Wireless Etl data transit method and system

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113487340A (zh) * 2021-05-24 2021-10-08 康键信息技术（深圳）有限公司 业务解耦处理方法、装置、设备及存储介质
CN113626211A (zh) * 2021-06-29 2021-11-09 欧电云信息科技(江苏)有限公司 消息队列的切换方法、切换系统、电子设备及存储介质
CN115150466A (zh) * 2022-06-29 2022-10-04 北京百度网讯科技有限公司 一种数据分发的实现方法、装置、电子设备及存储介质
CN115150466B (zh) * 2022-06-29 2023-08-15 北京百度网讯科技有限公司 一种数据分发的实现方法、装置、电子设备及存储介质
CN115499435A (zh) * 2022-08-08 2022-12-20 中亿(深圳)信息科技有限公司 任务调度方法、系统、电子设备及计算机可读存储介质
CN115499435B (zh) * 2022-08-08 2023-08-11 中亿(深圳)信息科技有限公司 任务调度方法、系统、电子设备及计算机可读存储介质
CN115529288A (zh) * 2022-09-21 2022-12-27 上海浦东发展银行股份有限公司 一种消息推送的方法、装置、计算机设备
CN115529288B (zh) * 2022-09-21 2024-04-19 上海浦东发展银行股份有限公司 一种消息推送的方法、装置、计算机设备
CN116545706A (zh) * 2023-05-15 2023-08-04 合芯科技(苏州)有限公司 一种数据安全传输控制系统、方法、装置及电子设备
CN116545706B (zh) * 2023-05-15 2024-01-23 合芯科技(苏州)有限公司 一种数据安全传输控制系统、方法、装置及电子设备

Also Published As

Publication number Publication date
CN112788074A (zh) 2021-05-11

Similar Documents

Publication Publication Date Title
WO2021088641A1 (zh) 数据发送方法、处理方法、接收方法及其设备、存储介质
CN107729139B (zh) 一种并发获取资源的方法和装置
US8984535B2 (en) System and method for facilitating the exchange of information among applications
US20190132276A1 (en) Unified event processing for data/event exchanges with existing systems
US20050278294A1 (en) Systems and methods for a collaboration presence framework
US10326720B2 (en) Messaging queue service API optimization system
US20050273714A1 (en) Systems and methods for an embedded collaboration client
US8484281B2 (en) System and method for callbacks based on web service addressing
AU2005246375A1 (en) Systems and methods for enterprise collaboration
US11784959B2 (en) Message transfer agent architecture for email delivery systems
CN113391979A (zh) 监控数据展示的处理方法、设备、系统及存储介质
CN112256246A (zh) 一种用于电力系统中支持跨语言调用的微服务集成架构
CN110476154A (zh) 用于数据收集的代理服务器设备和方法
CN112527523A (zh) 面向高性能计算多云的分布式消息传递方法及系统
CN108259605B (zh) 一种基于多数据中心的数据调用系统及方法
CN113220432A (zh) 多云互联方法、装置、设备、存储介质及产品
CN112788074B (zh) 数据发送方法、处理方法、接收方法及其设备、存储介质
CN109298956A (zh) 文件传输方法、装置及终端设备
CN115334155A (zh) 一种消息队列代理方法和装置
CN112511636B (zh) 数据传输系统、方法、装置、计算机设备及存储介质
CN115250276A (zh) 分布式系统及数据处理的方法和装置
CN113760487A (zh) 一种业务处理方法和装置
CN111258775A (zh) 消息处理方法、装置、设备和存储介质
CN103856359A (zh) 获取信息的方法和系统
US11824941B2 (en) Accessing representational state transfer application programming interfaces using simple mail transfer protocol

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: 20884469

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20884469

Country of ref document: EP

Kind code of ref document: A1

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

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20/02/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20884469

Country of ref document: EP

Kind code of ref document: A1