WO2022083378A1 - Procédé et dispositif de traitement de données - Google Patents

Procédé et dispositif de traitement de données Download PDF

Info

Publication number
WO2022083378A1
WO2022083378A1 PCT/CN2021/119245 CN2021119245W WO2022083378A1 WO 2022083378 A1 WO2022083378 A1 WO 2022083378A1 CN 2021119245 W CN2021119245 W CN 2021119245W WO 2022083378 A1 WO2022083378 A1 WO 2022083378A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
platform
information
object information
stored
Prior art date
Application number
PCT/CN2021/119245
Other languages
English (en)
Chinese (zh)
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
Application filed by 北京沃东天骏信息技术有限公司, 北京京东世纪贸易有限公司 filed Critical 北京沃东天骏信息技术有限公司
Publication of WO2022083378A1 publication Critical patent/WO2022083378A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • G06F21/46—Structures or tools for the administration of authentication by designing passwords or checking the strength of passwords

Definitions

  • the embodiments of the present application relate to computer technology, and in particular, to a data processing method and apparatus.
  • B2B (Business-to-Business) platform refers to a business platform that exchanges and transmits data and information and conducts transaction activities between enterprises through a private network or the Internet.
  • Embodiments of the present application provide a data processing method and apparatus to overcome the problem of low data processing efficiency.
  • an embodiment of the present application provides a data processing method, which is applied to the first platform, including:
  • the account information includes at least one account and at least one object information associated with each account;
  • the first account, the first object information and the target object information are stored in the first platform to obtain account information of the first account corresponding to the second platform.
  • storing the first account, the first object information and the target object information in the first platform includes:
  • the first account, the first object information and the target object information are associated and stored in the first platform.
  • the method further includes:
  • a first data unit corresponding to the first account is created in the first platform.
  • storing the first account, the first object information, and the target object information in the first platform in association with the first platform includes:
  • the first account number, the first object information and the target object information are associated and stored in the first data unit.
  • the method further includes:
  • the first account and the second object information are associated and stored on the first platform.
  • the method further includes:
  • the third platform After the third platform successfully authenticates the first account, the first account and the second object information are associated and stored in the second data unit.
  • the object information includes at least one of the following information: enterprise information, identity information, platform information, business model information, role information, and permission code information.
  • an embodiment of the present application provides a data processing apparatus, applied to the first platform, including:
  • a receiving module configured to receive the first account number sent by the second platform
  • the obtaining module is configured to obtain target object information corresponding to the first account from the account information stored in the first platform, wherein the account information includes at least one account and the associated information of each account. at least one object information;
  • the receiving module is further configured to receive the first object information corresponding to the first account sent by the second platform;
  • a processing module configured to store the first account, the first object information and the target object information in the first platform, and obtain account information of the first account corresponding to the second platform.
  • the processing module is specifically used for:
  • the first account, the first object information and the target object information are associated and stored in the first platform.
  • the receiving module is also used for:
  • the processing module is specifically used for:
  • a first data unit corresponding to the first account is created in the first platform.
  • the processing module is also used to:
  • the first account number, the first object information and the target object information are associated and stored in the first data unit.
  • the receiving module is also used for:
  • the processing module is specifically used for:
  • the first account and the second object information are associated and stored on the first platform.
  • the processing module is also used to:
  • the processing module is specifically used for:
  • the third platform After the third platform successfully authenticates the first account, the first account and the second object information are associated and stored in the second data unit.
  • the object information includes at least one of the following information: enterprise information, identity information, platform information, business model information, role information, and authority code information.
  • an embodiment of the present application provides a data processing device, including:
  • a processor configured to execute the program stored in the memory, and when the program is executed, the processor is configured to execute the method described in any one of the above first aspect and various possible designs of the first aspect.
  • embodiments of the present application provide a computer-readable storage medium, including instructions, which, when executed on a computer, cause the computer to execute the first aspect and any of the various possible designs of the first aspect. method.
  • Embodiments of the present application provide a data processing method and device, the method comprising: receiving a first account number sent by a second platform.
  • target object information corresponding to the first account is obtained, wherein the account information includes at least one account and at least one object information associated with each account.
  • the first account, the first object information and the target object information are stored in the first platform to obtain account information of the first account corresponding to the second platform.
  • FIG. 1 is a system schematic diagram of a data processing method provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of information for first platform maintenance provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of an implementation of a business model provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another implementation of a business model provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another implementation of the business model provided by the embodiment of the present application.
  • FIG. 6 is a schematic diagram of still another implementation of the business model provided by the embodiment of the present application.
  • FIG. 7 is a flowchart of a data processing method provided by an embodiment of the present application.
  • FIG. 8 is a flowchart of a data processing method provided by another embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a data processing method provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a data processing apparatus provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a hardware structure of a data processing device provided by an embodiment of the present application.
  • B2B (Business-to-Business) refers to a business model in which data and information are exchanged and transmitted, and transactions are carried out between enterprises through private networks or the Internet. It closely integrates the enterprise intranet and enterprise products and services with customers through B2B websites or mobile clients, and provides better services for customers through the rapid response of the network, thereby promoting the business development of the enterprise. It can be listed that both the supply and demand sides of the B2B e-commerce transaction are merchants, which may be, for example, enterprises, companies, and the like.
  • the existing B2B platforms are mainly divided into the following two types:
  • One is the platform type, which is to build a matching platform, where the seller publishes commodities, sets prices and rules, the buyer registers, selects and purchases, the seller performs the delivery, and the platform provides intermediate services;
  • the other is the self-operated platform, which is mainly for the seller to build the platform, and the seller will also conduct upstream centralized procurement, and provide platform transaction services, and the buyer will choose and purchase.
  • the B2B platform introduced in the prior art has two disadvantages.
  • One disadvantage is that multiple platforms cannot directly reuse the mode, and the data in multiple platforms is isolated and does not have the ability to open up horizontally in the account system.
  • the same company entity cannot be logged in on multiple platforms, nor can the basic information of the company be exchanged.
  • the same user needs to register separately on different platforms, and each time they register, they must fill in the company Therefore, the registration and login process of the platform is cumbersome, that is to say, the data between the various platforms cannot be exchanged.
  • Another disadvantage is that the mode of the platform cannot be switched and adjusted freely and autonomously, all of which are applied and processed in a fixed mode, and the mode architecture is not supported for vertical and in-depth switching of the mode.
  • the platform-based B2B platform it cannot be The model of self-operated platform handles business.
  • the present application proposes the following technical idea: build a general platform, in which the account information of each company can be recorded, so that each business platform can be supported according to this unified general platform. Register and log in to achieve data exchange.
  • FIG. 1 is a system schematic diagram of a data processing method provided by an embodiment of the present application.
  • FIG. 1 there are currently a first platform, a second platform, and a third platform.
  • the second platform and the third platform may be, for example, a B2B platform
  • the first platform may be a general platform between the second platform and the third platform, which is used to realize data intercommunication between the second platform and the third platform.
  • the first platform can build a system of general accounts, for example, account information of each platform can be stored. Therefore, by building the first platform in this application, data intercommunication between the second platform and the third platform can be realized.
  • the person A has registered on platform 1, and the account information and related information of the person A are stored in the first platform.
  • the account information of the person A is stored, and the account information can include the basic information that the person A fills in when he registers on the platform 1.
  • the current person A registers on the platform 2, there is no need to fill in these basic information.
  • the person A can log in directly on the platform 2 according to his existing account.
  • FIG. 1 is an introduction with the first platform as the general platform of the second platform and the third platform.
  • the first platform can be used as the general platform of multiple platforms, and this embodiment provides services for the first platform
  • the number of B2B platforms is not particularly limited.
  • FIG. 2 is a schematic diagram of information maintained by the first platform provided by the embodiment of the present application:
  • the account information may include enterprise information.
  • a basic information table of the enterprise may be constructed in the first platform, and the enterprise information is stored in the basic information table of the enterprise, wherein the enterprise Information is a virtual aggregate of B2B accounts.
  • the enterprise information may include, for example, the company's identification, name, code, tax number, legal person ID number and other basic information related to the enterprise.
  • This embodiment does not specifically limit the specific implementation of the enterprise information. Any information related to an enterprise can be used as the enterprise information in this embodiment.
  • association relationship between enterprises such as parent-subsidiary relationship
  • a custom inheritance relationship within the authorized scope can be carried out based on the association relationship definition, and the association relationship between enterprises can be stored, for example, in the basic information table of the enterprise. , or may also be stored in a separate table for indicating the association relationship between enterprises, which is not limited in this embodiment.
  • the account information may also include the account number.
  • a basic information table of the account number may be constructed in the first platform, and the account number is stored in the basic information table of the account number.
  • the basic information table of the account stores multiple accounts, for example, account-related information such as the password and registration time of each account may also be stored.
  • an account can correspond to multiple enterprises.
  • enterprise A there is currently an enterprise A and an enterprise B, and enterprise B is a subsidiary of enterprise A, then the current account can correspond to enterprise A at the same time.
  • enterprise B and an enterprise can also correspond to multiple accounts.
  • an association relationship between accounts can be established, such as parent and sub-accounts, etc., and a custom inheritance relationship within the authorized scope can be carried out based on the association relationship definition.
  • the association relationship between accounts can be stored, for example, in the basic information table of the account. , or may also be stored in a separate table for indicating the association relationship between accounts, which is not limited in this embodiment.
  • the account information also includes identity information.
  • an identity information table may be constructed in the first platform, wherein each identity is established within the scope of the enterprise, that is, each identity is established within the scope of the enterprise.
  • An enterprise has a separate set of identity information, and the same identity can only be used within the same enterprise.
  • the current identity information of enterprise A can include general manager, cashier, procurement, operation and other position information. B does not apply. Enterprise B has its own set of identity information.
  • the relationship between identity information and accounts is a many-to-many relationship, that is, an account is allowed to have multiple identities.
  • an account is allowed to have multiple identities.
  • enterprise A and enterprise B are parent and subsidiary companies, it is possible that person A works as a cashier in enterprise A.
  • Enterprise B is responsible for purchasing, then the account of this person A can correspond to two identities of cashier and procurement at the same time; at the same time, one identity can also correspond to multiple accounts, for example, for the cashier, there can be multiple cashiers, and there can be multiple account.
  • account information may also include platform information.
  • a business platform information table may be constructed in the first platform, and the current target business platform may be identified based on the business platform information.
  • An account number may represent different company entities corresponding to different business platforms, such as It is said that account 1 represents that company A corresponds to business platform 1, wherein the platform information can be, for example, a platform identifier.
  • the account information may also include business model information.
  • a business model information table may be constructed in the first platform, corresponding to different business platforms.
  • the business model and the business platform are in a one-to-many relationship, that is, a business platform.
  • the business model can be, for example, the platform type or self-operated type described above. Therefore, the business platform in this application can support two or more business models at the same time.
  • account information may also include role information.
  • a role information table may be constructed in the first platform, corresponding to different role information in the business model, wherein the role and the business model are in a one-to-many relationship, and one account can represent A company has multiple roles.
  • the roles can be, for example, various participants in the B2B scenario, and the roles can include, for example, platform parties, suppliers, agents, distributors, sales agents, B/C customers, operators, etc., where B customers refer to Corporate customers, C customers refer to individual customers.
  • the account information may also include permission code information, for example, permission code information may be constructed in the first platform, and independent permission code information may be formed based on the combination of different information tables of each account.
  • an account corresponding to enterprise A corresponding to identity 1, and role 1 in platform 1 and mode 1, will have a separate authorization code based on the corresponding scenario.
  • association relationship there may be an association relationship between the various pieces of information introduced above.
  • a separate relationship table may be used to store the association relationship between each piece of information, wherein the relationship between the pieces of information is
  • the association relationship may take the account number as the basic unit, that is to say, the account information corresponding to the account number is specifically stored.
  • each information in the account information introduced above is only an exemplary introduction.
  • the specific implementation of each information can be selected according to actual needs, as long as it is used to indicate that each corresponding The data of the information is sufficient, and the specific implementation of the information included in the account information can also be selected and expanded according to actual needs, which is not particularly limited in this embodiment.
  • the service platform in this application can support multiple service modes.
  • the following describes possible implementations of the service modes supported by the service platform in this application with reference to Fig. 3 to Fig. 6 , and Fig. 3 is implemented in this application.
  • Figure 4 is a schematic diagram of another implementation of the business mode provided by the embodiment of the application
  • Figure 5 is a schematic diagram of another implementation of the business mode provided by the embodiment of the application
  • Figure 6 is a schematic diagram of another implementation of the business mode provided by the embodiment of the application.
  • the business model of all B2B platforms is nothing more than the combination of multiple identities to form a transaction link. By configuring different identities in the transaction link, multiple business models can be realized.
  • the participants in the business model may include: platform, suppliers, agents, distributors, distributors, B/C customers, operators, etc., which can also be understood as the roles introduced above .
  • the participants include: suppliers, agents, operators, platforms and B/C customers.
  • agents, operators and platform parties are the main parties, that is, the roles assumed by the business platform, and suppliers and B/C customers are other participants of the platform, that is, roles that the platform does not assume.
  • the self-operated mode is realized, that is, based on the platform, the main body purchases from upstream suppliers to sell to downstream customers, and also plays the role of an operator.
  • the participants include: suppliers, agents, operators, platforms and B/C customers.
  • the platform party is the main party, and the others are other participants of the B2B platform.
  • the POP mode is realized, that is, based on the platform, the participating parties purchase from upstream suppliers to sell to downstream customers, and the participating parties assume the operational role.
  • the participants include: suppliers, agents, operators, distributors, and platforms.
  • the platform party and the agent are the main party, and the others are other participants of the B2B platform.
  • the pallet mode is realized, that is, based on the platform, the main party assumes the role of an agent, purchases from upstream and sells it to downstream distributor customers, and the participant assumes the role of operation.
  • the participating parties include: agents, operators, distributors, and platform parties.
  • the platform party and the operator are the main party, and the others are other participants of the B2B platform.
  • the buying and selling model is realized, that is, based on the platform, the main party assumes the roles of the platform party and the operator, and the upstream agents sell directly to the downstream distributor customers to realize the model of B2B matching transactions.
  • the four business models described above are only exemplary introductions.
  • the configuration of the participants, the main party, and the permissions of the corresponding participants can be used to realize the various transaction modes based on the general platform. support.
  • the configuration of multiple business modes supported by the business platform can be implemented simply and efficiently.
  • FIG. 7 is a flowchart of the data processing method provided by the embodiment of the present application.
  • the method includes:
  • the second platform is a B2B platform.
  • the user will register a separate account on the second platform, and then use the registered account number and password on the second platform.
  • this will result in the inability to communicate the login status and data communication between the B2B platforms.
  • the account registered on the second platform cannot be logged in on the third platform. It needs to be executed completely on the third platform. registration process.
  • the account is for the user, and each user can correspond to their own account.
  • the user can use the same account to register and log in on each platform, so as to realize the data of intercommunication.
  • the first account is an existing account, that is to say, the first account is an account registered on a B2B platform other than the second platform, assuming that the account belongs to user A.
  • user A can directly use his existing account to log in on the second platform. For example, you can log in according to the account number and password, or you can log in according to the account-related information, such as the business license number of the enterprise and the last 6 digits of the legal person ID card.
  • the specific login information can be determined according to the requirements of the second platform. The embodiment does not limit this.
  • the user currently needs to register on the second platform. Although the user can log in according to the first account, the user's permission information on the second platform has not been configured. The relevant information of the user corresponding to the second platform is not stored. In order to effectively realize data intercommunication, the relevant information of the second platform needs to be stored in the first platform.
  • the second platform may send the first account to the first platform, and after the first platform receives the first account sent by the second platform, it may be determined that the user corresponding to the first account currently needs to register on the first platform.
  • Account information may be stored in the first platform in this embodiment, and the account information may be used to record relevant information of each platform.
  • the account information includes at least one account, and each account is associated with At least one object information.
  • each account can be associated with at least one object information, wherein the object information can include, for example, the enterprise information introduced in the above embodiment: , identity information, platform information, business model information, role information, and permission code information.
  • object information can include, for example, the enterprise information introduced in the above embodiment: , identity information, platform information, business model information, role information, and permission code information.
  • the account information stored in the first platform includes the first account, and in this embodiment, the target associated with the first account can be obtained in the account information.
  • Object information it can be understood that the target object information is information that is common among various platforms and does not need to be filled in repeatedly.
  • the target object information may be, for example, enterprise information, such as the company's name, logo, tax ID number, legal person ID number and other related information, wherein the target object information may include all enterprise information, or Part of the corporate information can also be included.
  • the target object information may also include any kind of object information among the account information introduced above.
  • This embodiment does not specifically limit the specific implementation manner of the target object information, which may be based on actual needs.
  • the information content included in the target object information can be determined according to the information that the user does not need to fill in repeatedly when the user registers on the business platform.
  • the first object information is the information corresponding to the first account on the second platform. It can be understood that the target object information introduced above is the basic object information, and the current first object information is personalized in each platform.
  • the information, for example, the first object information may include at least one of the following: identity information, platform information, business model information, and role information.
  • the second platform After receiving the information output by the user, the second platform sends the information to the first platform.
  • the specific implementation manner of the first object information may be selected according to actual requirements, which is not particularly limited in this embodiment. In the actual implementation process, the specific implementation of the first object information may depend on the requirements of the second platform. In a possible implementation manner, it can be understood that the first object information may be object information other than the target object information.
  • the first platform After the first platform receives the first account and the first object information, and acquires the target object information corresponding to the first account, the first object information and the target object information are the registration information of the first account corresponding to the second platform, wherein , because the target object information is stored in the first platform, there is no need to repeat filling in the registration process, and it can be obtained directly from the first platform.
  • the first account, the first object information and the target object information are stored in the first platform, so that the account information of the first account corresponding to the second platform can be obtained, that is to say, the relevant account information of the second platform is stored In the first platform, it is ensured that the account information of each business platform will be stored in the first platform, so as to facilitate data exchange.
  • the first account may correspond to a plurality of object information, and each object information and the first account may be associated and stored as a piece of data, as the account corresponds to account information of a certain user in a certain platform.
  • the first object information and the target object information may be combined into object information corresponding to the second platform, and the combined information and the first account number may be associated and stored.
  • the first object information and the target object information may be directly stored in association with the first account.
  • the data processing method provided by the embodiment of the present application includes: receiving a first account number sent by a second platform.
  • target object information corresponding to the first account is obtained, wherein the account information includes at least one account and at least one object information associated with each account.
  • the first account, the first object information and the target object information are stored in the first platform to obtain account information of the first account corresponding to the second platform.
  • FIG. 8 is a flowchart of the data processing method provided by another embodiment of the present application.
  • the method includes:
  • the third platform is the business platform where the user registers for the first time, that is, the user has not registered on other business platforms before registering on the third platform, so the current user does not have an account.
  • the user can register on the third platform to obtain the first account, and the user will fill in the second object information in the process of registering on the third platform, wherein the second object information may include, for example, at least one of the following information: : Enterprise information, identity information, platform information, business model information, role information, and permission code information.
  • the second object information in this embodiment should include at least the target object information introduced above, because the first account and the object information associated with the first account have not been stored in the third platform at present, so The user is required to fill in the complete object information.
  • the third platform can send the first account and the second object information to the first platform, so that the first platform can store the information, so that the data can be exchanged with other platforms to avoid Fill in the information repeatedly during the registration process.
  • each account corresponds to at least one piece of object information, wherein, for example, an account and a corresponding piece of object information can be stored in one data unit, then each Multiple object information corresponding to an account can store multiple data units, wherein by storing each account and corresponding object information in one data unit, data storage and management are facilitated.
  • the data unit may be in any format as long as it can store data.
  • the first platform may create a second data unit corresponding to the first account in the first platform.
  • the first platform can create a second data unit corresponding to the identity of the general manager when creating the second data unit.
  • the third platform may, for example, authenticate the first account. After the third platform successfully authenticates the first account, it may determine that the first account is allowed to be used on the third platform. At the same time, the first platform may determine the first account and the second account. The object information meets the requirements. At this time, the first platform can store the first account number and the second object information in the second data unit, so as to facilitate data exchange with other business platforms.
  • S804, S805, and S806 are similar to the implementation manners of S701, S702, and S703, which are not repeated here.
  • the second platform can authenticate the first account. It can be understood that in the B2B platform, the account registered by the user actually represents the enterprise. Therefore, when the user registers on the business platform, the enterprise needs to Therefore, the second platform can authenticate the first account to determine whether the first account is currently allowed to register.
  • the second platform may, for example, receive the registration-allowing information sent by the enterprise, so as to determine that the authentication of the first account is passed; or, the second platform may also perform the registration process according to the user's first registration information and requirement information. By comparison, it is determined whether the authentication of the first account is passed.
  • This embodiment does not specifically limit the specific implementation of determining the authentication information corresponding to the first account, which can be selected according to actual needs.
  • the second platform After determining that the authentication of the first account is passed, the second platform sends authentication information to the first platform.
  • the first platform When the first platform receives the authentication information sent by the second platform, it can determine that the second platform allows the first account to be used, and the first platform can create a first data unit corresponding to the first account, wherein the first data unit is the same as the above
  • the introduced second data unit is similar, except that the above-mentioned first data unit corresponds to the third platform, and the current first data unit corresponds to the second platform.
  • S809 Associate and store the first account number, the first object information, and the target object information in the first data unit.
  • the first account number, the first object information and the target information are associated and stored in the first data unit.
  • the first object information and the target object information may be determined as account information corresponding to the first account, and stored in the first data unit in association.
  • the third platform in this embodiment refers to the service platform where the user registers for the first time in each service platform, and the second platform refers to each service platform except the third platform, wherein the second platform Platform and third platform do not specifically refer to a business platform.
  • the data processing method provided by the embodiment of the present application includes: receiving the first account number and the second object information sent by the third platform.
  • a second data unit corresponding to the first account is created in the first platform.
  • the third platform successfully authenticates the first account, the first account and the second object information are associated and stored in the second data unit.
  • target object information corresponding to the first account is obtained, wherein the account information includes at least one account and at least one object information associated with each account.
  • Receive authentication information corresponding to the first account sent by the second platform where the authentication information is used to indicate that the authentication of the first account on the second platform has passed.
  • a first data unit corresponding to the first account is created in the first platform.
  • the first account number, the first object information and the target object information are associated and stored in the first data unit.
  • FIG. 9 is a schematic flowchart of the data processing method provided by the embodiment of the present application.
  • FIG. 9 there are currently a first platform, a second platform, and a third platform, wherein each platform has been introduced in the above embodiment, and will not be repeated here.
  • the third platform can send the information of the first account and the second object to the first platform, and the first platform creates the second data unit.
  • the first account and the second object can be The information is associated and stored in the second data unit, but the currently created second data unit has not yet taken effect, because it has not yet been determined whether the authentication of the first account in the third platform is successful.
  • the second data unit may be, for example, identity 1, and identity 1 may be currently created in the first platform, where identity 1 may include, for example, a business platform, a business model, and in this embodiment The identity of 1 can also be associated with stored enterprise information.
  • the user After the user completes the registration on the third platform, he can log in on the third platform according to the registered first account and the corresponding password. After the user logs in, for example, the company's authentication information can be filled in, or the third platform can receive The authentication information sent to the company to confirm that the first account is currently allowed to be used on the third platform.
  • the first platform can authenticate the first account according to the company authentication information sent by the third platform. For example, when the company authentication information indicates that the first account is valid, the first platform can determine that the second data unit is valid, and at this time the first account is valid. The first account and the second object information associated with the first account are recorded in a platform.
  • the first platform may notify the third platform that the information of the first account and the second object has been stored, and at this time, the third platform may determine that the first account is effective.
  • the first account and the object information corresponding to the first account have been stored in the first platform, and then the user can use the first account to directly register and log in to other business platforms.
  • the user has not registered on the second platform, but the user can directly log in on the second platform according to the first account, when the second platform receives the login request corresponding to the first account , it can be determined whether the first account is an existing account.
  • each business platform may store an existing account, and the second platform may determine whether the first account is an existing account according to locally stored information; or, the second platform may also store the first account The account number is sent to the first platform, so that the first platform inquires whether the first account number is an existing account.
  • the process of registering a new account is performed, that is, the process performed by the third platform described above.
  • the first account is an existing account, it can be verified whether the login request of the first account is passed.
  • the implementation manner of verifying the login request of the first account can be selected according to actual requirements, as long as it can verify whether the login information of the first account is correct, which is not particularly limited in this embodiment.
  • the second platform can determine the authentication information, where the authentication information is used to indicate whether the first account is allowed to be used on the second platform, and then the second platform can send the authentication information to the first platform.
  • the second platform can also send the first account to the first platform, after that, the first platform creates the first data unit corresponding to the first account, and determines that the first data unit is valid according to the authentication information, and the second platform according to the first data unit.
  • the information that a data unit is valid it can be determined that the first account is valid in the second platform.
  • the second platform can prompt the user to fill in the information of the first object corresponding to the second platform, and the second platform will receive the first object.
  • the information is sent to the first platform.
  • the first platform can obtain target information corresponding to the first account according to the first account, and determine the target information and the first object information as the object information of the first account corresponding to the second platform, and store the target information in association with the first object in the second platform. in a data unit.
  • the object information in this embodiment actually indicates the rights and interests information of each account, that is to say, the operation authority of each account on each business platform.
  • the current first data unit is identity 2
  • the rights and interests information based on the business platform 2 can be supplemented based on the rights and interests information of the identity 1 introduced above, and maintained on the first platform uniformly.
  • the data processing method provided by the embodiments of the present application realizes that users can use a set of account systems in different
  • the business platform and different transaction modes can be settled in controllably, realizing the general and simple configuration implementation of the general platform, and because the first platform realizes data interoperability, in the process of entering each business platform, there is no need to repeat the basics. registration information, effectively improving the efficiency of data processing.
  • FIG. 10 is a schematic structural diagram of a data processing apparatus provided by an embodiment of the present application.
  • the apparatus 100 includes: a receiving module 1001 , an obtaining module 1002 and a processing module 1003 .
  • Obtaining module 1002 configured to obtain target object information corresponding to the first account in the account information stored in the first platform, wherein the account information includes at least one account and each account associated with the account at least one object information of ;
  • the receiving module 1001 is further configured to receive the first object information corresponding to the first account sent by the second platform;
  • a processing module 1003 configured to store the first account, the first object information and the target object information in the first platform, and obtain the account information of the first account corresponding to the second platform .
  • the processing module 1003 is specifically used for:
  • the first account, the first object information and the target object information are associated and stored in the first platform.
  • the receiving module 1001 is also used for:
  • the processing module 1003 is specifically used for:
  • a first data unit corresponding to the first account is created in the first platform.
  • processing module 1003 is also used for:
  • the first account number, the first object information and the target object information are associated and stored in the first data unit.
  • the receiving module 1001 is also used for:
  • the processing module 1003 is specifically used for:
  • the first account and the second object information are associated and stored on the first platform.
  • processing module 1003 is also used for:
  • the processing module 1003 is specifically used for:
  • the third platform After the third platform successfully authenticates the first account, the first account and the second object information are associated and stored in the second data unit.
  • the object information includes at least one of the following information: enterprise information, identity information, platform information, business model information, role information, and permission code information.
  • FIG. 11 is a schematic diagram of a hardware structure of a data processing device provided by an embodiment of the present application.
  • the data processing device 110 of this embodiment includes: a processor 1101 and a memory 1102;
  • memory 1102 for storing computer-executed instructions
  • the processor 1101 is configured to execute the computer-executed instructions stored in the memory, so as to implement each step performed by the data processing method in the foregoing embodiment. For details, refer to the relevant descriptions in the foregoing method embodiments.
  • the memory 1102 may be independent or integrated with the processor 1101 .
  • the data processing device further includes a bus 1103 for connecting the memory 1102 and the processor 1101 .
  • Embodiments of the present application further provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when a processor executes the computer-executable instructions, the data processing method performed by the above data processing device is implemented .
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules is only a logical function division. In actual implementation, there may be other division methods.
  • multiple modules may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in electrical, mechanical or other forms.
  • the above-mentioned integrated modules implemented in the form of software functional modules may be stored in a computer-readable storage medium.
  • the above-mentioned software function modules are stored in a storage medium, and include several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to execute the various embodiments of the present application. part of the method.
  • processor may be a central processing unit (English: Central Processing Unit, referred to as: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processor, referred to as: DSP), application-specific integrated circuits (English: Application Specific Integrated Circuit, referred to as: ASIC) and so on.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the invention can be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory may include high-speed RAM memory, and may also include non-volatile storage NVM, such as at least one magnetic disk memory, and may also be a U disk, a removable hard disk, a read-only memory, a magnetic disk or an optical disk, and the like.
  • NVM non-volatile storage
  • the bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, or the like.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus and so on.
  • the buses in the drawings of the present application are not limited to only one bus or one type of bus.
  • the above-mentioned storage medium may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Except programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable except programmable read only memory
  • PROM programmable read only memory
  • ROM read only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.
  • the aforementioned program can be stored in a computer-readable storage medium.
  • the steps including the above method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de traitement de données. Ledit procédé consiste : à recevoir un premier compte envoyé par une seconde plate-forme (S701) ; à acquérir, à partir d'informations de compte stockées dans une première plate-forme, des informations d'objet cible correspondant au premier compte, les informations de compte comprenant au moins un compte et au moins un élément d'information d'objet associé à chaque compte (S702) ; à recevoir des premières informations d'objet correspondant au premier compte envoyées par la seconde plate-forme (S703) ; et à stocker le premier compte, les premières informations d'objet et les informations d'objet cible dans la première plate-forme pour obtenir des informations de compte du premier compte correspondant à la seconde plate-forme (S704). En construisant la première plate-forme pour stocker des informations de compte de diverses plates-formes de service, un utilisateur peut utiliser le même compte pour se connecter à différentes plates-formes de service, et l'utilisateur n'a pas besoin de remplir de manière répétée des informations d'objet de base dans le processus d'enregistrement des plates-formes de service, ce qui permet d'obtenir un interfonctionnement de données entre les plates-formes de service et d'assurer l'efficacité du traitement de données.
PCT/CN2021/119245 2020-10-22 2021-09-18 Procédé et dispositif de traitement de données WO2022083378A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011137541.0 2020-10-22
CN202011137541.0A CN113761490A (zh) 2020-10-22 2020-10-22 数据处理方法及装置

Publications (1)

Publication Number Publication Date
WO2022083378A1 true WO2022083378A1 (fr) 2022-04-28

Family

ID=78785899

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/119245 WO2022083378A1 (fr) 2020-10-22 2021-09-18 Procédé et dispositif de traitement de données

Country Status (2)

Country Link
CN (1) CN113761490A (fr)
WO (1) WO2022083378A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115208664A (zh) * 2022-07-15 2022-10-18 平安科技（深圳）有限公司 多平台用户统一识别的方法、装置、设备和存储介质
WO2023246480A1 (fr) * 2022-06-24 2023-12-28 北京字跳网络技术有限公司 Procédé et appareil d'authentification d'identité, dispositif, support et produit

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114422172B (zh) * 2021-12-08 2024-04-05 深圳市明源云科技有限公司 账号切换方法、装置、设备及存储介质
CN114726629B (zh) * 2022-04-12 2024-03-12 树根互联股份有限公司 权限配置方法、系统、装置、电子设备及可读存储介质
CN116566737B (zh) * 2023-06-27 2023-09-26 云账户技术(天津)有限公司 基于SaaS平台的权限配置方法、装置及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103312701A (zh) * 2013-05-30 2013-09-18 腾讯科技（深圳）有限公司 一种联系人信息整合方法、服务器、终端以及系统
CN104767714A (zh) * 2014-01-03 2015-07-08 腾讯科技（深圳）有限公司 一种关联用户资源信息的方法、终端及系统
CN108494799A (zh) * 2018-04-18 2018-09-04 家园网络科技有限公司 数据共享方法和系统
CN109951475A (zh) * 2019-03-15 2019-06-28 东莞市大易产业链服务有限公司 多平台用户账户信息同步方法及系统、服务器

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104735021B (zh) * 2013-12-18 2018-12-11 腾讯科技（深圳）有限公司 一种帐号登录方法、装置和系统
CN109274685B (zh) * 2018-11-02 2021-09-17 深圳壹账通智能科技有限公司 多系统登录方法、装置、计算机设备和存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103312701A (zh) * 2013-05-30 2013-09-18 腾讯科技（深圳）有限公司 一种联系人信息整合方法、服务器、终端以及系统
CN104767714A (zh) * 2014-01-03 2015-07-08 腾讯科技（深圳）有限公司 一种关联用户资源信息的方法、终端及系统
CN108494799A (zh) * 2018-04-18 2018-09-04 家园网络科技有限公司 数据共享方法和系统
CN109951475A (zh) * 2019-03-15 2019-06-28 东莞市大易产业链服务有限公司 多平台用户账户信息同步方法及系统、服务器

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023246480A1 (fr) * 2022-06-24 2023-12-28 北京字跳网络技术有限公司 Procédé et appareil d'authentification d'identité, dispositif, support et produit
CN115208664A (zh) * 2022-07-15 2022-10-18 平安科技（深圳）有限公司 多平台用户统一识别的方法、装置、设备和存储介质

Also Published As

Publication number Publication date
CN113761490A (zh) 2021-12-07

Similar Documents

Publication Publication Date Title
WO2022083378A1 (fr) Procédé et dispositif de traitement de données
US20220198418A1 (en) Systems and methods for commerce in a distributed system with blockchain protocols and smart contracts
US20220392299A1 (en) Systems and methods for authenticated blockchain data distribution
JP6660062B2 (ja) 暗号化統合プラットフォーム
JP6838000B2 (ja) 暗号技法を使用した取引における意思の難読化
CN107993047B (zh) 一种基于区块链的保单销售佣金权益管理方法
US20180189753A1 (en) Infrastructure for obligation management and validation
US20190180329A1 (en) Cognitive determination system connecting social network and blockchain network
US6092053A (en) System and method for merchant invoked electronic commerce
US20160203448A1 (en) Cryptocurrency verification system
US20150081567A1 (en) Electronic transaction system and method with participant authentication via separate authority from real-time payment validation
US11336453B2 (en) Transactions between services in a multi-tenant architecture
KR20190059491A (ko) 블록체인상에서 공유 분산장부와 외부 저장장치에 정보를 분리저장하여 구현한 안전한 전자상거래시스템
JP2002023628A (ja) 電子的貿易取引サーバ、売主用クライアント、買主用クライアント及び電子的貿易取引方法
US20210150527A1 (en) System and method for transferring data representing transactions between computing nodes of a computer network
TW201802741A (zh) 訂單信息處理以及訂單類型轉換處理方法及裝置
TW201626301A (zh) 電子憑證產生裝置及其系統
US11055675B2 (en) Systems and methods for e-certificate exchange and validation
WO2020155204A1 (fr) Procédé et appareil de transaction de nom de domaine fondé sur une chaîne de blocs
CN111902838A (zh) 因特网数据使用控制系统
JP2023015223A (ja) 電子ブロックチェーンに組み込まれる取引の妥当性を確認するシステムと方法
CN113723951A (zh) 基于区块链的权益转移系统
TW201335873A (zh) 使用特定（ａｄ ｈｏｃ）線上群組之批量採購商議的方法及系統
KR102350522B1 (ko) 비대면 부동산 계약을 위한 계약 이행 서비스 제공 시스템
JP2023500260A (ja) 代理相互台帳認証

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21881797

Country of ref document: EP

Kind code of ref document: A1