Cross-platform service access method, apparatus, device, and storage medium

Abstract

The application provides a cross-platform service access method and device, equipment and a storage medium, wherein the method comprises the following steps: receiving, by a second platform, a service access request input through a first platform, wherein the service access request comprises an identifier of the first platform and a first platform user identifier of a preset user on the first platform; querying, by the second platform, identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform, to obtain a second platform user identifier of the preset user on the second platform; and executing, by the second platform, an operation corresponding to the service access request based on the second platform user identifier. The second platform user identifier is determined through the identity matching information, and then the service access is executed by the second platform based on the second platform user identifier, so that the platforms are automatically associated, and cross-platform service access is realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, in particular to a cross-platform service access method and device, equipment and a storage medium. BACKGROUND

[0002] With the fierce competition in the Internet field, mergers and acquisitions between different sub-sectors and between different sectors are becoming more common. After mergers and acquisitions, the first problem to be solved is the matching of users between two platforms.

[0003] Taking the acquisition of platform B by platform A as an example, in the prior art, the user needs to log in to platform A or B before performing the association operation, that is, associating the user information in platform A with the user information in platform B. If the user does not manually perform the association operation, when the user logs in to platform A and uses a function of platform B in platform A, or enters platform B from platform A, since the user information between platform A and platform B is not matched, the function of platform B cannot be used in platform A or platform B is entered from platform A.

[0004] However, manually performing the association operation is not conducive to information exchange between platforms, and also leads to poor user experience. SUMMARY

[0005] Therefore, the embodiments of the present application provide a cross-platform service access method, device, equipment and storage medium to automatically associate different platforms and realize cross-platform service access, thereby improving user experience.

[0006] In a first aspect, the embodiments of the present application provide a cross-platform access method, comprising:

[0007] receiving, by a second platform, a service access request input through a first platform, wherein the service access request comprises an identifier of the first platform and a first platform user identifier of a preset user in the first platform;

[0008] querying, by the second platform, identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform, to obtain a second platform user identifier of the preset user in the second platform;

[0009] executing, by the second platform, an operation corresponding to the service access request based on the second platform user identifier.

[0010] In an optional implementation, before the step of querying, by the second platform, the identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform, the method further comprises:

[0011] receiving, by the second platform, an identity matching request input through the first platform, the identity matching request comprising: the identifier of the first platform, the first platform user identifier, and identity access information of the preset user on the first platform;

[0012] obtaining, by the second platform, the user identifier of the preset user on the first platform according to the identity access information;

[0013] querying, by the second platform, the user identifier from a user database of the second platform;

[0014] if the user identifier is queried, matching, by the second platform, the first platform user identifier and a second platform user identifier corresponding to the user identifier in the user database to obtain the identity matching information.

[0015] In an optional implementation, before the step of querying, by the second platform, the identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform, the method further comprises:

[0016] if the user identifier is not queried, creating a new user in the user database by using the user identifier and generating the second platform user identifier;

[0017] matching, by the second platform, the first platform user identifier and the generated second platform user identifier to obtain the identity matching information.

[0018] In an optional implementation, the identity access information is an identity access code; and the step of obtaining, by the second platform, the user identifier of the preset user on the first platform according to the identity access information comprises:

[0019] obtaining, by the second platform, the user identifier from the first platform according to the identity access code.

[0020] In an optional implementation, the user identifier comprises a plurality of first sub-user identifiers with preset priorities; and the step of querying, by the second platform, the user identifier from a user database of the second platform comprises:

[0021] According to the preset priority, the second platform is used to sequentially query the plurality of first sub-user identifiers from the user database;

[0022] If the user identifier is queried, the second platform is used to match the first platform user identifier and the corresponding second platform user identifier of the user identifier in the user database to obtain the identity matching information, including:

[0023] If a preset number of first sub-user identifiers are queried, the second platform is used to match the first platform user identifier and the second platform user identifier to obtain the identity matching information.

[0024] In an optional implementation, the user identifier includes a plurality of second sub-user identifiers; and the second platform is used to query the user identifier from the user database of the second platform, including:

[0025] The second platform is used to respectively query the plurality of second sub-user identifiers from the user database;

[0026] If the user identifier is queried, the second platform is used to match the first platform user identifier and the corresponding second platform user identifier of the user identifier in the user database to obtain the identity matching information, including:

[0027] If a second sub-user identifier satisfying a preset matching verification condition is queried, the second platform is used to match the first platform user identifier and the second platform user identifier to obtain the identity matching information.

[0028] In an optional implementation, the method further includes:

[0029] If the type of the queried second sub-user identifier is a preset identifier type, or the number of the queried second sub-user identifiers satisfies a preset number condition, it is determined that the queried second sub-user identifier satisfies the preset matching verification condition.

[0030] In a second aspect, the embodiments of the present application further provide a cross-platform access method, including:

[0031] A receiving module is configured to receive, by using a second platform, a service access request input through a first platform, wherein the service access request includes an identifier of the first platform and a first platform user identifier of a preset user in the first platform;

[0032] The query module is configured to query, by using the second platform, identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform, to obtain a second platform user identifier of the preset user on the second platform.

[0033] The execution module is configured to execute, by using the second platform, an operation corresponding to the service access request based on the second platform user identifier.

[0034] In an optional implementation, the receiving module is further configured to:

[0035] receive, by using the second platform, an identity matching request input through the first platform, the identity matching request comprising the identifier of the first platform, the first platform user identifier, and identity access information of the preset user on the first platform;

[0036] The apparatus further comprises:

[0037] The obtaining module is configured to obtain, by using the second platform, a user identifier of the preset user on the first platform according to the identity access information.

[0038] The query module is further configured to query, by using the second platform, the user identifier from a user database of the second platform.

[0039] The matching module is configured to, if the user identifier is queried, match, by using the second platform, the first platform user identifier and a second platform user identifier corresponding to the user identifier in the user database, to obtain the identity matching information.

[0040] In an optional implementation, the apparatus further comprises:

[0041] The creating module is configured to, if the user identifier is not queried, create a new user in the user database by using the user identifier, and generate the second platform user identifier.

[0042] The matching module is further configured to match, by using the second platform, the first platform user identifier and the generated second platform user identifier, to obtain the identity matching information.

[0043] In an optional implementation, the identity access information is an identity access code; and the obtaining module is specifically configured to:

[0044] obtain, by using the second platform, the user identifier from the first platform according to the identity access code.

[0045] In an optional implementation, the user identifier includes: a plurality of first sub-user identifiers with preset priorities; the query module is specifically configured to:

[0046] According to the preset priorities, the second platform is used to sequentially query the plurality of first sub-user identifiers from the user database;

[0047] The matching module is specifically configured to:

[0048] If a preset number of first sub-user identifiers are queried, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain the identity matching information.

[0049] In an optional implementation, the user identifier includes: a plurality of second sub-user identifiers; the query module is specifically configured to:

[0050] The second platform is used to respectively query the plurality of second sub-user identifiers from the user database;

[0051] The matching module is specifically configured to:

[0052] If a second sub-user identifier that meets a preset matching verification condition is queried, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain the identity matching information.

[0053] In an optional implementation, the apparatus further includes:

[0054] The determination module is configured to determine that the queried second sub-user identifier meets the preset matching verification condition if a type of the queried second sub-user identifier is a preset identifier type, or a number of the queried second sub-user identifiers meets a preset number condition.

[0055] In a third aspect, an electronic device is provided, including: a processor, a memory, and a bus, the memory stores machine readable instructions executable by the processor, when the electronic device is running, the processor and the memory communicate through the bus, and the processor executes the machine readable instructions to execute the method in any one of the first aspect.

[0056] In a fourth aspect, a computer readable storage medium is provided, the computer readable storage medium stores a computer program, and the computer program is executed by a processor to execute the method in any one of the first aspect.

[0057] The application provides a cross-platform service access method, device, equipment and storage medium, and the method comprises the following steps: receiving, by a second platform, a service access request input through a first platform, wherein the service access request comprises an identifier of the first platform and a first platform user identifier of a preset user in the first platform; querying, by the second platform, identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform, to obtain a second platform user identifier of the preset user in the second platform; and executing, by the second platform, an operation corresponding to the service access request based on the second platform user identifier. The second platform user identifier is determined through the identity matching information, and then the service access is executed by the second platform based on the second platform user identifier, so that the platforms are automatically associated, and cross-platform service access is realized.

[0058] In order to make the above objectives, characteristics and advantages of the present application more apparent, the following will describe a preferred embodiment in detail, and the accompanying drawings will be referred to, as follows. BRIEF DESCRIPTION OF DRAWINGS

[0059] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the present application, and therefore should not be regarded as a limitation to the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.

[0060] Figure 1 Flowchart of the cross-platform service access method provided by the embodiment of the present application Figure One

[0061] Figure 2 Flowchart of the cross-platform service access method provided by the embodiment of the present application Figure Two

[0062] Figure 3 Flowchart of the cross-platform service access method provided by the embodiment of the present application Figure Three

[0063] Figure 4 Flowchart of the cross-platform service access method provided by the embodiment of the present application Figure Four

[0064] Figure 5 Flowchart of the cross-platform service access method provided by the embodiment of the present application Figure Five

[0065] Figure 6 Structure diagram of the cross-platform service access device provided by the embodiment of the present application

[0066] Figure 7 ​​​​​A structural schematic diagram of an electronic device provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0067] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application and are not all the embodiments of the present application. The components of the embodiments of the present application described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application.

[0068] It should be noted that the terms "first", "second", "third", and the like are only used to distinguish descriptions and cannot be understood as indicating or implying relative importance.

[0069] In view of the problem that platform user information between two or more platforms is not matched after the current enterprise acquisition or merger, manual association is often required for the user, however, manual association is not only not conducive to information intercommunication between platforms, but also leads to poor user experience. Based on this, the present application provides a cross-platform business access method. When a second platform receives a business access request input through a first platform, the second platform queries identity matching information between the second platform and the first platform to obtain a second platform user identifier of a preset user in the second platform, and then the second platform performs business access based on the second platform user identifier, so as to automatically associate the platforms, realize cross-platform business access, and improve user experience without manual association of the user.

[0070] The cross-platform business access method provided by the present application will be described below in combination with several specific embodiments.

[0071] Figure 1 A flowchart of the cross-platform business access method provided by an embodiment of the present application is shown. Figure One The execution subject of the present embodiment can be an electronic device such as a mobile phone, a computer, and the like.

[0072] As shown in Figure 1 The method can include the following steps.

[0073] S101, a second platform receives a business access request input through a first platform.

[0074] The first platform and the second platform can be arranged on the electronic device, the first platform can be a waybill management platform, and the second platform can be a cold chain information platform.

[0075] In actual application, if the first platform needs to access the second platform, the user can input a business access request for the second platform through the first platform, that is, the second platform receives the business access request input through the first platform.

[0076] The business access request includes the identifier of the first platform and the first platform user identifier of the preset user on the first platform, and the first platform user identifier is the login user identifier of the preset user on the first platform, for example, the account and password information of the preset user on the first platform, that is, the preset user needs to log in to the first platform and then access the second platform through the first platform.

[0077] S102, the second platform queries the identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform, and obtains the second platform user identifier of the preset user on the second platform.

[0078] The second platform can save a plurality of identity matching information between the second platform and a plurality of other platforms, and the second platform can determine the identity matching information between the second platform and the first platform from the plurality of identity matching information according to the identifier of the first platform, and then determine the second platform user identifier from the identity matching information according to the first platform user identifier, wherein the second platform user identifier is the login user identifier of the preset user on the second platform, for example, the account and password information of the preset user on the second platform.

[0079] It is worth noting that the identity matching information between the second platform and the first platform is used to indicate the correspondence between the second platform user identifier and the first platform user identifier, and the second platform user identifier can be determined according to the first platform user identifier and the correspondence.

[0080] S103, the second platform executes the operation corresponding to the business access request based on the second platform user identifier.

[0081] The operation corresponding to the business access request includes but is not limited to adding, deleting, querying, modifying some information on the second platform, for example, viewing the waybill information of a cold chain waybill through the first platform, including but not limited to waybill number, starting point, terminal point, starting time, terminal time, etc., and clicking the waybill number to jump to the second platform to view the cold chain transportation information of the cold chain waybill, including but not limited to cold chain transportation goods, goods category, goods weight, etc.

[0082] In other words, users can access the second platform's services based on the second platform's identifier without needing to verify and match again. For example, when logging in from platform A to use the functions of platform B, there is no need to enter the account information of platform B again for verification and matching in order to use the functions of platform B. This automatically associates the first platform and the second platform, enabling cross-platform service access.

[0083] It is worth noting that this application uses the first platform and the second platform as examples for illustration. When multiple platforms such as the third platform and the fourth platform are embedded in the first platform, this scheme can be used to perform different automatic associations to achieve cross-platform business access.

[0084] In the cross-platform service method of this embodiment, a second platform receives a service access request input through the first platform. The second platform queries identity matching information between the second and first platforms based on the user identifier and the identifier of the first platform to obtain the second platform user identifier of the preset user on the second platform. The second platform then executes the operation corresponding to the service access request based on the second platform user identifier. By determining the second platform user identifier through identity matching information, and then executing service access based on the second platform user identifier, the platform is automatically associated, thus realizing cross-platform service access.

[0085] Figure 2 A flowchart illustrating the cross-platform service access method provided in this application embodiment. Figure Two ,like Figure 2 As shown, in an optional implementation, before step S102, where the second platform queries the identity matching information between the second platform and the first platform based on the user identifier of the first platform and the identifier of the first platform, to obtain the user identifier of the preset user on the second platform, the method may further include:

[0086] S201. The second platform is used to receive the identity matching request input through the first platform.

[0087] The identity matching request can be a business access request or a login request for the second platform that is entered for the first time through the first platform. For example, if a user clicks on the waybill number for the first time through the first platform, it will trigger the business access request to be sent to the second platform through the first platform. Or, if a user clicks on the login information for the second platform through the first platform, it will trigger the login request to be sent to the second platform through the first platform.

[0088] In actual application, if the first time business access to the second platform is needed through the first platform, the user can input the first time business access request or login request for the second platform through the first platform, and the second platform receives the identity matching request input through the first platform accordingly.

[0089] The identity matching request includes the identity of the first platform, the user identity of the first platform, and the identity access information of the preset user on the first platform.

[0090] The identity access information can be the identity information of the preset user saved in the first platform.

[0091] It is worth noting that the first platform and the second platform can each be provided with a user matching special interface. Taking the first platform as an example, the first platform sends the identity matching request to the second platform through the user matching special interface of the first platform, or the second platform acquires the identity matching request through the user matching special interface of the first platform. By separately setting the user matching special interface in the background, the basic information of the user is prevented from being transmitted in the webpage, and the user privacy is prevented from being leaked.

[0092] S202, the second platform acquires the user identity of the preset user on the first platform according to the identity access information.

[0093] The user identity is the identity of the preset user saved in the first platform, such as a phone number, an ID number, a name, a date of birth, a driver's license number, etc., and the identity access information can be the user identity.

[0094] In an optional implementation, the identity access information can be identity code information, and the second platform can acquire the user identity from the first platform according to the identity code information. The identity code information can be an encoded information generated for the user identity, and the first platform saves a mapping relationship between the identity code information and the user identity. The second platform can query the mapping relationship according to the identity code information to acquire the user identity from the first platform.

[0095] It can be understood that the second platform can query the user identity from the first platform through the identity matching special interface of the first platform according to the identity code information. In this way, the identity code information is transmitted through the identity matching special interface to acquire the user identity, the basic information of the user is prevented from being transmitted in the webpage, the user privacy is prevented from being leaked, the personal information security is ensured, and of course, the user can have an identity code information on the second platform, and the specific implementation manner is similar to the above process.

[0096] S203, the second platform queries the user identity from the user database of the second platform.

[0097] S204, if the user identifier is queried, the second platform is used to match the first platform user identifier and the second platform user identifier corresponding to the user identifier in the user database to obtain identity matching information.

[0098] The user database of the second platform is used to save the identifier information of the user registered and logged in on the second platform and the platform user identifier of the user registered and logged in on the second platform.

[0099] The second platform is used to query the user identifier from the user database of the second platform. If the user identifier is queried, it indicates that the preset user has registered and logged in on the second platform, that is, the preset user is an old user of the second platform. Then, the second platform is used to match the first platform user identifier and the second platform user identifier corresponding to the user identifier in the user database to obtain identity matching information.

[0100] In this way, the first platform user identifier and the second platform user identifier of the preset user can be matched to obtain identity matching information. Thus, after the preset user logs in the first platform, the preset user can directly access the second platform without the need of re-verification and matching, so as to automatically associate the first platform and the second platform and realize cross-platform business access.

[0101] It is worth noting that the second platform can also be used to send the identity matching information to the first platform through the user matching special interface of the first platform, or the second platform can be used to send the second platform user identifier to the first platform through the user matching special interface of the first platform, so that the first platform matches the first platform user identifier and the second platform user identifier to obtain the identity matching information. In this way, when the first platform receives the business access request input by the second platform, the first platform can be used to query the identity matching information to obtain the first platform user identifier of the preset user on the first platform, and the first platform can be used to execute the operation corresponding to the business request based on the first platform user identifier, so that the user can directly use the function of the first platform when logging in the second platform without the need of re-verification and matching. The specific mode is similar to the above process.

[0102] In the cross-platform business method of the embodiment, after the second platform receives the identity matching request, the user database of the second platform can be queried. When the user identifier is queried, that is, if the preset user is an old user of the second platform, the first platform user identifier and the second platform user identifier are matched to obtain identity matching information. Thus, the first platform and the second platform are automatically associated through the identity matching information, and subsequent cross-platform business access can be realized.

[0103] Figure 3 Flowchart of the cross-platform business access method provided by the embodiment of the application Figure Three For example, Figure 3As shown, in an optional implementation, before step S102, where the second platform queries the identity matching information between the second platform and the first platform based on the user identifier of the first platform and the identifier of the first platform, to obtain the user identifier of the preset user on the second platform, the method may further include:

[0104] S301. If the user identifier cannot be found, the user identifier is used to create a new user in the user database and generate a second platform user identifier.

[0105] If the user identifier cannot be found in the user database of the second platform, it means that the default user has not registered or logged in on the first platform. In other words, the default user is a new user for the second platform. In this case, the user identifier is used to create a new user in the user database and generate a new user identifier for the second platform.

[0106] S302. The user identifier of the first platform is matched with the generated user identifier of the second platform using the second platform to obtain identity matching information.

[0107] The second platform is used to match the user identifier of the first platform with the generated user identifier of the second platform to obtain identity matching information. In this way, the user can directly access the second platform after logging into the first platform without further verification and matching, so as to automatically associate the first platform and the second platform and realize cross-platform business access.

[0108] In the cross-platform service access method of this embodiment, if the preset user is a new user on the second platform, a second platform user identifier is generated, and the first platform user identifier and the second platform user identifier are matched to obtain identity matching information. Thus, the first platform and the second platform are automatically associated through the identity matching information, enabling subsequent cross-platform service access.

[0109] Figure 4 A flowchart illustrating the cross-platform service access method provided in this application embodiment. Figure Four ,like Figure 4 As shown, in an optional implementation, step S203, querying the user identifier from the user database of the second platform using the second platform, may include:

[0110] S401. Based on the preset priority, the second platform sequentially queries multiple first sub-user identifiers from the user database.

[0111] User identifiers include: multiple first sub-user identifiers with preset priorities. The higher the priority, the better it can represent the user's identity. The multiple first sub-user identifiers can be arranged from high to low priority, for example: ID card number > name > phone number, or phone number > ID card number > name.

[0112] Accordingly, in step S204, if the user identifier is found, the first platform user identifier is matched with the corresponding second platform user identifier in the user database by using the second platform to obtain the identity matching information, which can include:

[0113] In step S402, if a preset number of first sub-user identifiers are found, the first platform user identifier is matched with the second platform user identifier by using the second platform to obtain the identity matching information.

[0114] According to the preset priority of the multiple first sub-user identifiers, the second platform is used to sequentially query the multiple first sub-user identifiers from the user database. If a preset number of first sub-user identifiers are found, it indicates that the preset user is also an old user for the second platform. Then, the first platform user identifier is matched with the second platform user identifier by using the second platform to obtain the identity matching information, wherein the second platform user identifier is at least the login user identifier of the sub-user identifier in the second platform.

[0115] It is worth noting that the user logging in the first platform and the second platform can save some user identifiers in the first platform and the second platform. However, the user identifiers saved by the first platform and the second platform can be the same or different. Therefore, by querying according to the priority, when a preset number of first sub-user identifiers can be found in the user database of the second platform, it is determined that the preset user has registered and logged in the second platform, thereby improving the matching accuracy.

[0116] For example, the preset number can be at least two. Taking the multiple first sub-user identifiers in the priority from high to low as an example: phone number > name > ID number > SMS, the second platform is used to query in the user database of the second platform based on the multiple first sub-user identifiers. If the phone number can be queried, the name will be further queried. If the name can be queried, the first platform user identifier is matched with the second platform user identifier. The user can access the second platform by using the second platform user identifier. At the same time, the second platform user identifier is fed back to the first platform by using the user matching special interface of the first platform. The first platform also matches the first platform user identifier with the second platform user identifier. When the user logs in the first platform by using the second platform to use the function of the first platform, it is not necessary to verify and match again.

[0117] It is worth mentioning that if the name cannot be queried (i.e. the name in the user database and the queried name are inconsistent, or there is no name in the user database), the ID number is queried, if the ID number cannot be queried (i.e. the ID number in the user database and the queried ID number are inconsistent, or there is no ID number in the user database), the SMS verification is started, after the verification is passed, the first platform user identifier and the second platform user identifier are matched, and the missing name and ID number in the user database are synchronized to be filled, or the name and ID number are stored in the user database, or when the user logs in the second platform, it is required to choose one to keep and then update the confirmation.

[0118] In the cross-platform access method of the embodiment, according to the preset priority, the second platform is used to query multiple first sub-user identifiers from the user database in sequence, if a preset number of first sub-user identifiers are queried, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain identity matching information. According to the priority, the sub-user identifier is queried, and when at least two sub-user identifiers are queried, it is determined that the preset user has registered and logged in the second platform, then the identity matching information is obtained by matching, thereby improving the matching accuracy. In addition, according to the preset priority, all first sub-user identifiers do not need to be queried, but when a preset number of first user identifiers are queried, identity matching is performed, thereby further improving the processing speed.

[0119] Figure 5 Flowchart of the cross-platform service access method provided by the embodiment Figure Five As shown in Figure 5 In an optional embodiment, step S203, using the second platform to query the user identifier from the user database of the second platform can include:

[0120] S501, using the second platform to query multiple second sub-user identifiers from the user database respectively.

[0121] The user identifier includes multiple second sub-user identifiers, such as a phone number, an ID number, a name, a date of birth, a driver's license number, etc. The second platform is used to query multiple second sub-user identifiers from the user database respectively, and multiple query results are obtained.

[0122] Correspondingly, step S204, if the user identifier is queried, the first platform user identifier and the corresponding second platform user identifier in the user database are matched by using the second platform to obtain identity matching information, which can include:

[0123] S502, if the second sub-user identifier meeting the preset matching verification condition is queried, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain identity matching information.

[0124] If the second sub-user identifier meeting the preset matching verification condition is queried, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain identity matching information. In this way, identity matching can be performed when the second sub-user identifier queried meets the preset matching verification condition.

[0125] The method further comprises:

[0126] If the type of the second sub-user identifier queried is a preset identifier type, or the number of the second sub-user identifier queried meets a preset number condition, it is determined that the second sub-user identifier queried meets the preset matching verification condition.

[0127] The preset identifier type can be a necessary type for identity matching verification, such as name and / or phone number, and the preset number condition can be a preset number threshold or a preset number ratio. The preset number ratio is the ratio between the number of the second sub-user identifier that can be queried and the number of all second sub-user identifiers. The preset number threshold can be greater than or equal to 2, and the preset number ratio can be greater than or equal to 1 / 2.

[0128] That is, when the type of the second sub-user identifier queried is the preset identifier type, it is determined that the second sub-user identifier queried meets the preset matching verification condition, which indicates that the preset user is an old user of the second platform. Then, the first platform user identifier and the second platform user identifier are matched to obtain identity matching information.

[0129] Alternatively, when the type of the second sub-user identifier queried reaches the preset number threshold or the preset number ratio, it is determined that the second sub-user identifier queried meets the preset matching verification condition, which indicates that the preset user is an old user of the second platform. Then, the first platform user identifier and the second platform user identifier are matched to obtain identity matching information.

[0130] In the cross-platform access method of the embodiment, if the second sub-user identifier queried meets the preset matching verification condition, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain identity matching information, thereby improving the matching accuracy.

[0131] Figure 6 The structure of the cross-platform service access device provided by the embodiment of the application is shown in the figure. As shown in the figure, the device can include: Figure 6 ​

[0132] The receiving module 601 is configured to receive, by the second platform, a service access request input through the first platform, the service access request comprising: an identity of the first platform, and a first platform user identity of a preset user on the first platform;

[0133] The querying module 602 is configured to query, by the second platform, identity matching information between the second platform and the first platform according to the first platform user identity and the identity of the first platform, to obtain a second platform user identity of the preset user on the second platform;

[0134] The executing module 603 is configured to execute, by the second platform, an operation corresponding to the service access request based on the second platform user identity.

[0135] In an optional implementation, the receiving module 601 is further configured to:

[0136] receive, by the second platform, an identity matching request input through the first platform, the identity matching request comprising: the identity of the first platform, the first platform user identity, and identity access information of the preset user on the first platform;

[0137] The apparatus further comprises:

[0138] The obtaining module 604 is configured to obtain, by the second platform, the user identity of the preset user on the first platform according to the identity access information;

[0139] The querying module 602 is further configured to query, by the second platform, the user identity from a user database of the second platform;

[0140] The matching module 605 is configured to, if the user identity is queried, match, by the second platform, the first platform user identity and a second platform user identity corresponding to the user identity in the user database, to obtain the identity matching information.

[0141] In an optional implementation, the apparatus further comprises:

[0142] The creating module 606 is configured to, if the user identity is not queried, create a new user in the user database by using the user identity, and generate a second platform user identity;

[0143] The matching module 605 is further configured to match, by the second platform, the first platform user identity and the generated second platform user identity, to obtain the identity matching information.

[0144] In an optional implementation, the identity access information is an identity access code; and the obtaining module 604 is specifically configured to:

[0145] obtain, by the second platform, the user identity from the first platform according to the identity access code.

[0146] In an optional implementation, the user identifier includes: a plurality of first sub-user identifiers with preset priorities; the query module 602 is specifically configured to:

[0147] According to the preset priorities, the second platform is used to sequentially query the plurality of first sub-user identifiers from the user database;

[0148] The matching module 605 is specifically configured to:

[0149] If a preset number of first sub-user identifiers are queried, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain the identity matching information.

[0150] In an optional implementation, the user identifier includes: a plurality of second sub-user identifiers; the query module 602 is specifically configured to:

[0151] The second platform is used to respectively query the plurality of second sub-user identifiers from the user database;

[0152] The matching module 605 is specifically configured to:

[0153] If a second sub-user identifier that meets the preset matching verification condition is queried, the first platform user identifier and the second platform user identifier are matched by using the second platform to obtain the identity matching information.

[0154] In an optional implementation, the apparatus further includes:

[0155] The determination module 607 is configured to determine that the queried second sub-user identifier meets the preset matching verification condition if the type of the queried second sub-user identifier is a preset identifier type, or the number of the queried second sub-user identifiers meets a preset number condition.

[0156] The description of the processing procedure of each module in the apparatus and the interaction procedure between the modules can refer to the related description in the above method embodiments, and will not be described in detail here.

[0157] Figure 7 The structural schematic diagram of the electronic device provided in the embodiments of the present application is shown in FIG. 7, which can include: Figure 7 As shown in FIG. 7, the device can include: a processor 701, a memory 702 and a bus 703, the memory 702 stores machine readable instructions executable by the processor 701, when the electronic device is running, the processor 701 and the memory 702 communicate through the bus 703, the processor 701 executes the machine readable instructions to execute the above method.

[0158] The embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to perform the method.

[0159] In the embodiment of the present application, the computer program executed by the processor can further execute other machine readable instructions to perform the method as described in the embodiment. For the specific method steps and principles of execution, refer to the description of the embodiment, which will not be described in detail here.

[0160] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other manners. The described device embodiments are merely illustrative. For example, the division of the units is only a logical function division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0161] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, that is, can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments.

[0162] In addition, each functional unit in the embodiments provided by the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0163] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts of the technical solutions that make contributions to the prior art or the parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0164] It should be noted that like reference numerals and letters refer to like items throughout the accompanying drawings, and once an item is defined in one drawing, it should not be further defined and explained in subsequent drawings, and further, the terms "first", "second", "third" and the like are used only to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

[0165] Finally, it should be noted that the above-described embodiments are merely specific embodiments of the present application, and are used to illustrate the technical solutions of the present application, but are not limiting, and the protection scope of the present application is not limited thereto, although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily think of changes to the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to some technical features, and these modifications, changes or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A cross-platform service access method, characterized by, The method comprises the following steps: receiving, by a second platform, a service access request input through a first platform, wherein the service access request comprises an identity of the first platform and a first platform user identity of a preset user on the first platform; querying, by the second platform, identity matching information between the second platform and the first platform according to the first platform user identity and the identity of the first platform, to obtain a second platform user identity of the preset user on the second platform; executing, by the second platform, an operation corresponding to the service access request based on the second platform user identity; Before the step of querying, by the second platform, the identity matching information between the second platform and the first platform according to the first platform user identity and the identity of the first platform, to obtain the second platform user identity of the preset user on the second platform, the method further comprises the following steps: receiving, by the second platform, an identity matching request input through the first platform, wherein the identity matching request comprises the identity of the first platform, the first platform user identity, and identity access information of the preset user on the first platform, and the identity access information is identity information of the preset user saved by the first platform; obtaining, by the second platform, the user identity of the preset user on the first platform according to the identity access information; querying, by the second platform, the user identity from a user database of the second platform; if the user identity is found, matching, by the second platform, the first platform user identity with a second platform user identity corresponding to the user identity in the user database, to obtain the identity matching information; the identity access information is an identity access code; and the step of obtaining, by the second platform, the user identity of the preset user on the first platform according to the identity access information comprises the following step: obtaining, by the second platform, the user identity from the first platform according to the identity access code.

2. The method of claim 1, wherein, Before the step of querying, by the second platform, the identity matching information between the second platform and the first platform according to the first platform user identity and the identity of the first platform, to obtain the second platform user identity of the preset user on the second platform, the method further comprises the following steps: if the user identity is not found, creating a new user in the user database by using the user identity and generating the second platform user identity; matching, by the second platform, the first platform user identity with the generated second platform user identity, to obtain the identity matching information.

3. The method of claim 1, wherein, the user identity comprises a plurality of first sub-user identities with a preset priority; and the step of querying, by the second platform, the user identity from the user database of the second platform comprises the following step: querying, by the second platform, the plurality of first sub-user identities from the user database in sequence according to the preset priority. If the user identifier is found, the second platform is used to match the first platform user identifier and the corresponding second platform user identifier of the user identifier in the user database to obtain the identity matching information, including: If a preset number of first sub-user identifiers are found, the second platform is used to match the first platform user identifier and the second platform user identifier to obtain the identity matching information.

4. The method of claim 1, wherein, The user identifier includes a plurality of second sub-user identifiers, and the second platform is used to query the user identifier from the user database of the second platform, including: The second platform is used to query the plurality of second sub-user identifiers from the user database respectively; If the user identifier is found, the second platform is used to match the first platform user identifier and the corresponding second platform user identifier of the user identifier in the user database to obtain the identity matching information, including: If a second sub-user identifier satisfying a preset matching verification condition is found, the second platform is used to match the first platform user identifier and the second platform user identifier to obtain the identity matching information.

5. The method of claim 4, wherein, The method further includes: If the type of the found second sub-user identifier is a preset identifier type, or the number of the found second sub-user identifiers satisfies a preset number condition, it is determined that the found second sub-user identifier satisfies the preset matching verification condition.

6. A cross-platform service access apparatus characterized by comprising: Including: A receiving module is configured to receive, by using a second platform, a service access request input through a first platform, wherein the service access request includes an identifier of the first platform and a first platform user identifier of a preset user in the first platform; A querying module is configured to query, by using the second platform, identity matching information between the second platform and the first platform according to the first platform user identifier and the identifier of the first platform to obtain a second platform user identifier of the preset user in the second platform; An executing module is configured to execute, by using the second platform, an operation corresponding to the service access request based on the second platform user identifier; The receiving module is further configured to: receive, by using the second platform, an identity matching request input through the first platform, wherein the identity matching request includes the identifier of the first platform, the first platform user identifier, and identity access information of the preset user in the first platform, and the identity access information is identity information of the preset user saved by the first platform; An obtaining module is configured to obtain, by using the second platform, a user identifier of the preset user in the first platform according to the identity access information; The querying module is further configured to query, by using the second platform, the user identifier from a user database of the second platform; A matching module is configured to, if the user identifier is found, match, by using the second platform, the first platform user identifier and the corresponding second platform user identifier of the user identifier in the user database to obtain the identity matching information; The identity access information is an identity access code; and the obtaining module is specifically configured to obtain, by the second platform, the user identifier from the first platform according to the identity access code.

7. An electronic device, comprising: Comprise: A processor, a memory and a bus, the memory stores machine readable instructions executable by the processor, when the electronic device is running, the processor and the memory communicate through the bus, the processor executes the machine readable instructions to execute the method of any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by the processor to execute the method of any one of claims 1 to 5.

Images