Data transmission method, apparatus and electronic device

CN117527270BActive Publication Date: 2026-09-22吉林亿联银行股份有限公司
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202210886099.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-26
Publication Date
2026-09-22
Estimated Expiration
2042-07-26

AI Technical Summary

Benefits of technology

[0016]在本发明实施例中,采用联合登录的同时进行数据传输和数据校验的方式,首先接收第一平台发送的请求登录第二平台的请求报文,然后基于业务数据标识,从第一平台获取目标业务的业务数据,并对业务数据进行校验,得到校验结果,然后在业务数据满足预设校验规则的情况下,生成登录凭证,最后基于登录凭证登录第二平台,并将业务数据从第一平台传输至第二平台。其中,请求报文至少包括业务数据标识,校验结果表征业务数据是否满足预设校验规则。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117527270B_ABST
    Figure CN117527270B_ABST
Patent Text Reader

Abstract

The application discloses a data transmission method and device and electronic equipment, and relates to the technical field of computers. The method comprises the following steps: receiving a request message for requesting to log in to a second platform sent by a first platform, wherein the request message comprises at least a service data identifier; obtaining service data of a target service from the first platform based on the service data identifier, and performing verification on the service data to obtain a verification result, wherein the verification result indicates whether the service data meets a preset verification rule; generating a login credential in the case that the service data meets the preset verification rule; logging in to the second platform based on the login credential, and transmitting the service data from the first platform to the second platform. The application solves the technical problem of resource waste caused by the fact that data cannot be used after successful login and then data transmission in the prior art.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically, to a data transmission method, apparatus, and electronic device. Background Technology

[0002] With the rapid development of computer technology, various applications have emerged in an endless stream. To provide users with richer content and services, it's common practice to integrate multiple third-party H5 page programs into the application, and to avoid frequent login switching and reduce most of the registration process through unified login. Here, H5 page programs refer to web applications based on Hyper Text Markup Language (HTML) 5.0, i.e., HTML5, and unified login means that users can verify their login on certain third-party partner sites.

[0003] However, in current real-world business scenarios, the common practice is to perform data transmission and verification only after successful login. This approach leads to unusable data and wasted resources. Furthermore, for each business scenario, developers need to configure corresponding interfaces to implement data transmission and verification, resulting in a significant waste of human resources.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This invention provides a data transmission method, apparatus, and electronic device to at least solve the technical problem in the prior art where data becomes unusable after successful login, leading to resource waste.

[0006] According to one aspect of the present invention, a data transmission method is provided, comprising: receiving a request message sent by a first platform requesting login to a second platform, wherein the request message includes at least a service data identifier; obtaining service data of a target service from the first platform based on the service data identifier, and verifying the service data to obtain a verification result, wherein the verification result indicates whether the service data meets a preset verification rule; generating a login credential if the service data meets the preset verification rule; logging into the second platform based on the login credential, and transmitting the service data from the first platform to the second platform.

[0007] Furthermore, the data transmission method also includes: obtaining a business information identifier from the request message, and determining the target business from multiple services of the first platform based on the business information identifier; and determining the business data from multiple business data of the first platform based on the business data identifier.

[0008] Furthermore, the data transmission method also includes: obtaining business data of the target business from the first platform based on the business data identifier; determining verification configuration information based on the business data, wherein the verification configuration information represents the rules for verifying the business data; and verifying the business data based on the verification configuration information to obtain the verification result.

[0009] Furthermore, the data transmission method also includes: performing field validation and data type validation on the business data according to the validation configuration information to obtain a first validation result and a second validation result, wherein the first validation result indicates whether a field in the business data is a target field, and the second validation result indicates whether the business data is a target data type; and determining the validation result based on the first validation result and the second validation result.

[0010] Furthermore, the data transmission method also includes generating login credentials when the field in the business data is the target field and the business data is of the target data type.

[0011] Furthermore, the data transmission method also includes: generating a prompt message when a field in the business data is a non-target field or the business data is a non-target data type, and sending the prompt message to the first platform, wherein the prompt message indicates that the login credential generation failed.

[0012] Furthermore, the data transmission method also includes: obtaining the attribute information of the target object from the request message; binding the login credential with the attribute information, business information identifier, and business data identifier of the target object to obtain a first login credential; logging into the second platform based on the first login credential, and transmitting the business data from the first platform to the second platform.

[0013] According to another aspect of the present invention, a data transmission apparatus is also provided, comprising: a receiving module, configured to receive a request message sent by a first platform requesting login to a second platform, wherein the request message includes at least a service data identifier; an obtaining module, configured to obtain service data of a target service from the first platform based on the service data identifier, and verify the service data to obtain a verification result, wherein the verification result indicates whether the service data meets a preset verification rule; a generating module, configured to generate a login credential if the service data meets the preset verification rule; and a login module, configured to log in to the second platform based on the login credential and transmit the service data from the first platform to the second platform.

[0014] According to another aspect of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the above-described data transmission method at runtime.

[0015] According to another aspect of the present invention, an electronic device is also provided, the electronic device including one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are configured to run the programs, wherein the programs are configured to execute the above-described data transmission method during runtime.

[0016] In this embodiment of the invention, a method of simultaneous data transmission and verification during joint login is adopted. First, a request message from a first platform requesting login to a second platform is received. Then, based on the business data identifier, the business data of the target business is obtained from the first platform and verified to obtain a verification result. If the business data meets preset verification rules, a login credential is generated. Finally, the login credential is used to log in to the second platform, and the business data is transmitted from the first platform to the second platform. The request message includes at least a business data identifier, and the verification result indicates whether the business data meets the preset verification rules.

[0017] In the above process, by receiving the request message sent by the first platform to log in to the second platform, a business data identifier can be obtained, providing an accurate data foundation for subsequently obtaining the business data of the target business. Based on the business data identifier, the business data of the target business can be obtained from the first platform, providing an accurate data foundation for transmitting business data while logging in. Furthermore, by verifying the business data, it can be determined whether the business data meets the preset verification rules, realizing a process of pre-verification of business data while logging in, avoiding waste of resources. If the business data meets the preset verification rules, a login credential can be generated, thereby enabling login to the second platform based on the login credential and transmitting business data from the first platform to the second platform. This realizes a process of transmitting business data while logging in, saving developers' time costs and human resource costs.

[0018] Therefore, the technical solution of this invention achieves the goal of simultaneous data transmission and data verification during joint login, thereby avoiding resource waste and solving the technical problem of resource waste caused by data unusable when data is transmitted after successful login in the prior art. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0020] Figure 1 This is a flowchart of an optional data transmission method according to an embodiment of the present invention;

[0021] Figure 2 This is a flowchart of an optional data transmission based on federated login according to an embodiment of the present invention;

[0022] Figure 3 This is a schematic diagram of an optional data transmission device according to an embodiment of the present invention;

[0023] Figure 4 This is a schematic diagram of an optional electronic device according to an embodiment of the present invention. Detailed Implementation

[0024] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention 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 the embodiments of the invention 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 a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises 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 apparatus.

[0026] It should be noted that all relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) involved in this invention are information and data authorized by the user or fully authorized by all parties. For example, this system has an interface with the relevant user or organization. Before obtaining relevant information, it needs to send an acquisition request to the aforementioned user or organization through the interface, and obtain the relevant information after receiving consent from the aforementioned user or organization.

[0027] Example 1

[0028] According to an embodiment of the present invention, a method embodiment of a data transmission method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0029] Figure 1 This is a flowchart of an optional data transmission method according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0030] Step S101: Receive a request message from the first platform requesting to log in to the second platform, wherein the request message includes at least a business data identifier.

[0031] In the above steps, a request message for logging into the second platform sent by the first platform can be received by an application system, processor, electronic device, or other device. Optionally, in this embodiment, the request message for logging into the second platform sent by the first platform is received by a server. The first platform can be a client, and the second platform can be an H5 page application. Figure 2 This is a flowchart of an optional data transmission based on federated login according to an embodiment of the present invention, such as... Figure 2 As shown, the client sends a federated login request message to the server to obtain a federated login token. The token is a string generated by the server and serves as an identifier for the client's request. Optionally, `busi_data` can be used as a business data identifier to identify the actual business data. This business data is stored as a Java Map object, which maps keys to values. Using the business data identifier, the business data can be transmitted to the server in key-value pairs.

[0032] It should be noted that, in the above process, by receiving the request message sent by the first platform to log in to the second platform, the business data identifier can be obtained, which provides an accurate data foundation for subsequently obtaining the business data of the target business.

[0033] Step S102: Based on the business data identifier, obtain the business data of the target business from the first platform, and verify the business data to obtain the verification result. The verification result indicates whether the business data meets the preset verification rules.

[0034] In the above steps, the target business can be a business in different scenarios, such as payment services or video services. Taking payment services as an example, after a user places an order on the client, corresponding business data is generated, and the user needs to be redirected to the cashier H5 page program to complete the payment. Simultaneously with the joint login on the cashier H5 page program, the business data can be transferred to the cashier H5 page program based on the business data identifier. Optionally, the preset verification rules can be used to check whether the content of the business data exists, whether the format of the business data conforms to preset format requirements, etc.

[0035] It should be noted that in the above process, by obtaining the business data of the target business from the first platform, an accurate data foundation is provided for transmitting business data while logging in. Furthermore, by verifying the business data, it can be determined whether the business data meets the preset verification rules, thus realizing the process of performing pre-verification of business data while logging in and avoiding waste of resources.

[0036] Step S103: If the business data meets the preset verification rules, generate login credentials.

[0037] In the above steps, the login credentials can be a token. A token is generated when the business data meets the preset verification rules, that is, when the business data verification is successfully passed.

[0038] It should be noted that, in the above process, by generating login credentials, accurate access credentials are provided for logging into the second platform.

[0039] Step S104: Log in to the second platform based on the login credentials and transfer business data from the first platform to the second platform.

[0040] In the above steps, after successfully generating login credentials, i.e., tokens, you can log in to the second platform based on the tokens and transfer business data from the first platform, i.e., the client, to the second platform, i.e., the H5 page program.

[0041] It should be noted that in the above process, by transmitting business data from the first platform to the second platform, the process of transmitting business data at the same time as logging in is realized, which saves the time cost of developers and saves human resource costs.

[0042] Based on the scheme defined in steps S101 to S104 above, it can be understood that in this embodiment of the invention, the method of simultaneous data transmission and data verification during joint login involves first receiving a request message from the first platform requesting login to the second platform; then, based on the business data identifier, obtaining the business data of the target business from the first platform and verifying the business data to obtain a verification result; then, if the business data meets the preset verification rules, generating a login credential; and finally, logging into the second platform based on the login credential and transmitting the business data from the first platform to the second platform. The request message at least includes a business data identifier, and the verification result indicates whether the business data meets the preset verification rules.

[0043] It is noteworthy that in the above process, by receiving the request message sent by the first platform to log in to the second platform, a business data identifier can be obtained, providing an accurate data foundation for subsequently acquiring the business data of the target business. Based on the business data identifier, the business data of the target business can be obtained from the first platform, providing an accurate data foundation for transmitting business data while logging in. Furthermore, by verifying the business data, it can be determined whether the business data meets the preset verification rules, realizing a process of pre-verification of business data while logging in, avoiding waste of resources. If the business data meets the preset verification rules, a login credential can be generated, thereby enabling login to the second platform based on the login credential and transmitting business data from the first platform to the second platform. This realizes a process of transmitting business data while logging in, saving developers' time costs and human resource costs.

[0044] Therefore, the technical solution of this invention achieves the goal of simultaneous data transmission and data verification during joint login, thereby avoiding resource waste and solving the technical problem of resource waste caused by data unusable when data is transmitted after successful login in the prior art.

[0045] In one optional embodiment, before obtaining the business data of the target business from the first platform based on the business data identifier, verifying the business data, and obtaining the verification result, the business information identifier is first obtained from the request message, and the target business is determined from multiple businesses of the first platform based on the business information identifier. Then, the business data is determined from multiple business data of the first platform based on the business data identifier.

[0046] Optionally, the business information identifier can be a business scenario code, represented by `busi_scene`, where different business scenarios correspond to different business scenario codes. For example... Figure 2As shown, the request message also includes a business scenario code (busi_scene). Using this business information identifier, the target business corresponding to the business scenario code can be determined from multiple business scenarios on the first platform (the client). Furthermore, based on the business data identifier, busi_data, the business data corresponding to busi_data can be determined from multiple business data sets on the first platform (the client).

[0047] It should be noted that by using business information identifiers and business data identifiers, the target business and business data can be accurately identified, ensuring the accurate transmission of business data.

[0048] In one optional embodiment, in the process of obtaining business data of the target business from the first platform based on the business data identifier, verifying the business data, and obtaining the verification result, the process first involves obtaining the business data of the target business from the first platform based on the business data identifier, then determining verification configuration information based on the business data, and finally verifying the business data based on the verification configuration information to obtain the verification result. The verification configuration information represents the rules for verifying the business data.

[0049] Optional, such as Figure 2 As shown, after receiving the request message, the server retrieves the business data corresponding to the business data identifier (busi_data) from the first platform (client). Then, based on the business scenario code (busi_scene) of the target business corresponding to the business data, it retrieves the verification configuration information for the business scenario corresponding to the business scenario code from the database. Optionally, the verification configuration information can be rules for verifying the business data, such as verifying whether fields in the business data exist or whether the business data type meets the configured business data type requirements.

[0050] It should be noted that, based on the verification configuration information, business data can be accurately verified, realizing the process of pre-verifying business data at the same time as login, thus avoiding waste of resources.

[0051] In one optional embodiment, during the process of validating business data based on validation configuration information and obtaining validation results, the business data is first validated for both field validation and data type validation according to the validation configuration information, resulting in a first validation result and a second validation result. Then, the validation result is determined based on the first and second validation results. The first validation result indicates whether a field in the business data is the target field, and the second validation result indicates whether the business data is the target data type.

[0052] Optionally, field validation can check if a field in the business data exists, i.e., whether an empty string exists; data type validation can check if the type of the business data is consistent with the data type in the validation configuration information. The target field can be a field that does not contain empty strings, and the target data type can be a data type consistent with the data type in the validation configuration information. For example, if the data type in the validation configuration information is character, then the target data type is also character. Optional, such as... Figure 2 As shown, based on the business scenario code (busi_scene), the verification configuration information for the corresponding business scenario is retrieved from the database. Then, based on the verification configuration information, field verification and data type verification are performed on the business data to obtain the first verification result and the second verification result. Finally, the verification result is determined based on the first verification result and the second verification result.

[0053] It should be noted that, based on the verification configuration information, accurate verification of fields and data types in business data can be achieved, thereby avoiding the waste of resources due to unusable data.

[0054] In one optional embodiment, during the process of generating login credentials, if the business data meets the preset verification rules, login credentials are generated when the field in the business data is the target field and the business data is the target data type.

[0055] Optional, such as Figure 2 As shown, if the field in the business data is the target field (i.e., a field without empty strings), and the business data is of the target data type (i.e., a character type consistent with the data type in the verification configuration information), the data verification is successfully passed, and a login credential (token) is generated. The data type in the verification configuration information and the target data type can also be other data types; this embodiment does not impose any limitations.

[0056] In an alternative embodiment, if a field in the business data is a non-target field or the business data is a non-target data type, a prompt message is generated and sent to the first platform, wherein the prompt message indicates that the login credential generation failed.

[0057] Optionally, if a field in the business data is a non-target field (i.e., contains an empty string), or if the business data is a non-target data type (i.e., not a character type consistent with the data type in the validation configuration information), for example, if the business data is an integer but the validation configuration information specifies a character type, then the business data is considered a non-target data type. Figure 2 As shown, if data verification fails, a prompt message is generated and sent to the first platform, i.e., the client. The prompt message may include information such as verification failure.

[0058] It should be noted that in the above process, by judging whether the business data meets the preset verification rules, the accurate transmission of business data is achieved, resource waste is avoided, and the security and reliability of joint login are guaranteed.

[0059] In one optional embodiment, during the process of logging into the second platform based on login credentials and transmitting business data from the first platform to the second platform, the attribute information of the target object is first obtained from the request message. Then, the login credentials are bound to the attribute information, business information identifier, and business data identifier of the target object to obtain the first login credentials. Finally, the first login credentials are used to log into the second platform and transmit business data from the first platform to the second platform.

[0060] Optionally, the attribute information of the target object can be a user ID, represented by user_id, such as... Figure 2 As shown, the request message also includes a user ID (user_id). After generating the login credential, i.e., the token, the token is bound to the target object's attribute information, i.e., the user ID (user_id), the business information identifier, i.e., the business scenario code (busi_scene), and the business data identifier, i.e., the business data (busi_data), to obtain the first login credential, i.e., the bound token. Optionally, the bound token can be stored in a caching system for subsequent processing. Further, as... Figure 2 As shown, the bound token is returned to the client, enabling the client to log in to the second platform, i.e., the H5 page program, based on the bound token.

[0061] It's worth noting that unified login allows users to verify their login on certain third-party partner sites. For example, after logging into their account within the application, a user can access the H5 page application without needing to log in again using unified login technology. In unified login applications, it's necessary to transmit business-related data based on the business scenario and perform pre-verification of that data. During this process, the second platform, the H5 page application, can successfully obtain user information using the user ID (user_id) in the bound token. Based on business data (busi_data), the process of transmitting business data during login is achieved. Based on the business scenario code (busi_scene), the process of accurately pre-verifying business data during login is achieved, avoiding resource waste.

[0062] Therefore, the technical solution of this invention achieves the goal of simultaneous data transmission and data verification during joint login, thereby avoiding resource waste and solving the technical problem of resource waste caused by data unusable when data is transmitted after successful login in the prior art.

[0063] Example 2

[0064] According to an embodiment of the present invention, an embodiment of a data transmission device is provided, wherein, Figure 3 This is a schematic diagram of an optional data transmission device according to an embodiment of the present invention, such as... Figure 3 As shown, the device includes: a receiving module 301, used to receive a request message sent by a first platform requesting login to a second platform, wherein the request message includes at least a service data identifier; an obtaining module 302, used to obtain service data of a target service from the first platform based on the service data identifier, and to verify the service data to obtain a verification result, wherein the verification result indicates whether the service data meets preset verification rules; a generating module 303, used to generate a login credential if the service data meets the preset verification rules; and a login module 304, used to log in to the second platform based on the login credential and to transmit the service data from the first platform to the second platform.

[0065] It should be noted that the receiving module 301, the obtaining module 302, the generating module 303, and the login module 304 mentioned above correspond to steps S101 to S104 in the above embodiments. The examples and application scenarios implemented by the four modules and the corresponding steps are the same, but are not limited to the content disclosed in the above embodiment 1.

[0066] Optionally, the data transmission device further includes: a first determining module, configured to obtain a service information identifier from a request message and determine a target service from multiple services of the first platform based on the service information identifier; and a second determining module, configured to determine service data from multiple service data of the first platform based on a service data identifier.

[0067] Optionally, the acquisition module includes: a first acquisition module, used to acquire business data of the target business from the first platform based on the business data identifier; a determination module, used to determine verification configuration information based on the business data, wherein the verification configuration information represents the rules for verifying the business data; and a verification module, used to verify the business data based on the verification configuration information and obtain the verification result.

[0068] Optionally, the verification module includes: a first verification module, used to perform field verification and data type verification on the business data according to the verification configuration information, and obtain a first verification result and a second verification result, wherein the first verification result indicates whether the field in the business data is the target field, and the second verification result indicates whether the business data is the target data type; and a determination module, used to determine the verification result based on the first verification result and the second verification result.

[0069] Optionally, the generation module includes a processing module for generating login credentials when the field in the business data is the target field and the business data is of the target data type.

[0070] Optionally, the data transmission device further includes: a prompting module, used to generate a prompting message when a field in the business data is a non-target field or the business data is a non-target data type, and send the prompting message to the first platform, wherein the prompting message indicates that the login credential generation failed.

[0071] Optionally, the login module includes: an acquisition module for acquiring attribute information of the target object from the request message; a processing module for binding the login credential with the attribute information, business information identifier, and business data identifier of the target object to obtain a first login credential; and a transmission module for logging into the second platform based on the first login credential and transmitting business data from the first platform to the second platform.

[0072] Example 3

[0073] According to another aspect of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, and the computer program is configured to execute the above-described data transmission method at runtime.

[0074] Example 4

[0075] According to another aspect of the present invention, an electronic device is also provided, wherein, Figure 4 This is a schematic diagram of an optional electronic device according to an embodiment of the present invention, such as... Figure 4 As shown, the electronic device includes one or more processors; and a memory for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to run the programs, wherein the programs are configured to execute the aforementioned data transmission method during runtime.

[0076] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0077] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0078] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0079] 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 units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0080] Furthermore, the functional units in the various embodiments of the present invention 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.

[0081] 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 solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, 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 the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0082] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A data transmission method, characterized in that, include: Receive a request message from the first platform requesting login to the second platform, wherein the request message includes at least a business data identifier; Based on the business data identifier, business data of the target business is obtained from the first platform, and the business data is verified to obtain a verification result, wherein the verification result indicates whether the business data meets the preset verification rules. If the business data meets the preset verification rules, a login credential is generated; Log in to the second platform based on the login credentials, and transmit the business data from the first platform to the second platform; Login to the second platform based on the login credentials, and transmit the business data from the first platform to the second platform, including: Obtain the attribute information of the target object from the request message; The login credential is bound to the attribute information, business information identifier, and business data identifier of the target object to obtain the first login credential. Log in to the second platform based on the first login credential, and transmit the business data from the first platform to the second platform.

2. The method according to claim 1, characterized in that, Before obtaining the target business's business data from the first platform based on the business data identifier, and verifying the business data to obtain the verification result, the method further includes: Obtain a service information identifier from the request message, and determine the target service from multiple services of the first platform based on the service information identifier; Based on the business data identifier, the business data is determined from multiple business data sources on the first platform.

3. The method according to claim 1, characterized in that, Based on the business data identifier, business data of the target business is obtained from the first platform, and the business data is verified to obtain a verification result, including: Based on the business data identifier, obtain the business data of the target business from the first platform; Verification configuration information is determined based on the business data, wherein the verification configuration information represents the rules for verifying the business data; Based on the verification configuration information, the business data is verified to obtain the verification result.

4. The method according to claim 3, characterized in that, Based on the verification configuration information, the business data is verified to obtain the verification result, including: Based on the verification configuration information, the business data is subjected to field verification and data type verification respectively to obtain a first verification result and a second verification result. The first verification result indicates whether the field in the business data is the target field, and the second verification result indicates whether the business data is the target data type. The verification result is determined based on the first verification result and the second verification result.

5. The method according to claim 4, characterized in that, If the business data meets the preset verification rules, a login credential is generated, including: The login credential is generated when the field in the business data is the target field and the business data is of the target data type.

6. The method according to claim 5, characterized in that, The method further includes: If a field in the business data is a non-target field, or if the business data is a non-target data type, a prompt message is generated and sent to the first platform, wherein the prompt message indicates that the login credential generation failed.

7. A data transmission device, characterized in that, include: The receiving module is used to receive a request message sent by the first platform to log in to the second platform, wherein the request message includes at least a business data identifier; The acquisition module is used to acquire business data of the target business from the first platform based on the business data identifier, and to verify the business data to obtain a verification result, wherein the verification result indicates whether the business data meets the preset verification rules. The generation module is used to generate login credentials when the business data meets the preset verification rules; The login module is used to log in to the second platform based on the login credentials and to transmit the business data from the first platform to the second platform; The login module includes: an acquisition module for acquiring attribute information of a target object from a request message; a processing module for binding the login credential with the attribute information, business information identifier, and business data identifier of the target object to obtain a first login credential; and a transmission module for logging into the second platform based on the first login credential and transmitting business data from the first platform to the second platform.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the data transmission method according to any one of claims 1 to 6 when it is run.

9. An electronic device, characterized in that, The electronic device includes one or more processors; A memory for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to be configured to run the programs, wherein the programs are configured to execute the data transfer method as described in any one of claims 1 to 6 at runtime.

Citation Information

Patent Citations

  • Service execution method and device and service execution system

    CN112559092A