Business processing method and device

Abstract

The embodiment of the invention provides a business processing method, an execution main body of the method is a service platform, a plurality of area sites corresponding to a plurality of service areas are arranged in the service platform, and each area site comprises a corresponding buyer business site and a corresponding seller business site; the method comprises the steps of dividing a whole order service into a buyer service and a seller service, and further, on one hand, routing the buyer service to a buyer service site in a service area to which a corresponding buyer belongs, so that the buyer service site is in butt joint with the buyer based on an area user identifier, and the buyer service site is in butt joint with the seller based on the area user identifier. Processing the business of the buyer and locally storing the processed data, wherein the regional user identifier is determined based on a plurality of regional identifiers associated with the global identifier corresponding to the buyer; and on the other hand, the seller service is routed to a seller service site in the service area to which the corresponding seller belongs, so that the seller service site realizes processing of the seller service and local storage of processing data by being connected with the seller.

Description

[0001] This application is a divisional application of the invention patent application with the application number 2020107184834 and the title "Business Processing Method and Device", which was filed on July 23, 2020. Technical Field

[0002] The embodiments of this specification relate to the field of computer technology, and in particular, to a business processing method and device. Background Art

[0003] In the current trend of globalization, in order to better meet user needs, many service platforms carry out cross-domain services across countries or regions, enabling users on platforms in different countries or regions to conduct business transactions through the service platform. For example, Chinese buyers can purchase goods provided by sellers in other countries or regions. At the same time, in today's big data era, data security is particularly important. Most countries and regions have put forward regulatory requirements related to data security, and different countries or regions have different compliance requirements for business data. For example, some countries require that user data generated within their territory cannot be stored outside the country, and some other countries require that user data generated within their territory cannot be stored in the blacklisted countries they set.

[0004] In order to enable the cross-domain services carried out by service platforms to meet the differentiated data regulatory requirements of each country, the common practice in the industry currently is to physically isolate the services for different countries or regions. For example, a certain service platform establishes national sites in two countries, and the deployment and data storage of each site are completely isolated. This approach brings inconvenience to platform users. For example, if a Chinese buyer wants to use the services provided by other country sites outside the Chinese site, they need to re-register an account on other country sites, or if a Chinese seller wants to offer the goods they sell on other country sites, they need to re-sign a contract with other country sites.

[0005] Therefore, a solution for implementing cross-domain services is needed, which can effectively simplify the operation process of users on the service platform while meeting the differentiated data regulatory requirements of each region, so as to optimize the user experience. Summary of the Invention

[0006] The embodiments of this specification describe a business processing method and device, which can effectively simplify the operation process of users on the service platform while meeting the differentiated data regulatory requirements of each region, and achieve the optimization of the user experience.

[0007] According to a first aspect, a business processing method is provided. The execution subject of the method is a service platform. The service platform sets up multiple regional sites corresponding to multiple service regions, where each regional site includes a corresponding buyer business site and a seller business site. The method includes:

[0008] Receive a payment request initiated by a first buyer for a first order. The first buyer corresponds to a first global user identifier. The goods in the first order are provided by a first seller. The payment request includes a selected payment channel. Determine a first service area to which the buyer payment service corresponding to the payment request belongs; the first area site corresponding to the first service area includes a first buyer service site; the first buyer has a first area user identifier in the first service area, which is determined based on a number of area user identifiers associated with the first global user identifier; the registered location of the payment institution corresponding to the payment channel is in the first service area. Route the buyer payment service to the first buyer service site, so that the first buyer service site processes the buyer payment service by docking with the payment channel and docking with the first buyer based on the first area user identifier, and locally stores the business data generated by processing the buyer payment service. Obtain a payment success message corresponding to the payment request. Based on the payment success message, determine that the seller delivery service to be processed belongs to a second service area. The registered location of the first seller is in the second service area. The second area site corresponding to the second service area includes a second seller service site. Route the seller delivery service to the second seller service site, so that the second seller service site processes the seller delivery service by docking with the first seller and locally stores the business data generated by processing the seller delivery service.

[0009] In one embodiment, before receiving the payment request initiated by the first buyer for the first order, the method further includes: in response to the successful login of the first buyer, determine the first global user identifier corresponding to the first buyer; in response to receiving an order creation request initiated by the first buyer based on the goods, create the first order.

[0010] In a specific embodiment, determining that the first buyer corresponds to the first global user identifier includes: obtaining the username of the first buyer; performing a hash operation on the username to obtain the first global user identifier; or querying the first global user identifier based on a pre-established mapping relationship between the username and the global user identifier.

[0011] In another specific embodiment, after creating the first order and before receiving a payment request initiated by the first buyer for the first order, the method further includes: obtaining location element information of the first buyer; determining, according to the location element information, the service area where the first buyer is currently located as the first service area; determining, according to the several area user identifiers corresponding to several service areas, a first area user identifier of the first buyer in the first service area; obtaining several alternative payment channels for the first buyer to select, and the registered locations of the payment institutions corresponding to the several alternative payment channels are all located in the first service area.

[0012] Further, in an even more specific embodiment, the location element information includes at least one of the following: longitude and latitude information, network address, Internet Protocol (IP) address, and the delivery address included in the first order.

[0013] In another more specific embodiment, determining, according to the several area user identifiers corresponding to several service areas, a first area user identifier of the first buyer in the first service area includes: when there is no user identifier corresponding to the first service area among the several area user identifiers, creating a new user identifier as the first area user identifier; and classifying the first area user identifier into the several area user identifiers.

[0014] In an embodiment, determining the first service area to which the buyer payment service corresponding to the payment request belongs includes: determining the registered location corresponding to the payment channel and taking the service area where it is located as the first service area.

[0015] In a specific embodiment, after determining the first service area to which the buyer payment service corresponding to the payment request belongs and before routing the buyer payment service to the first buyer service site, the method further includes: determining, according to the several area user identifiers corresponding to several service areas, a first area user identifier of the first buyer in the first service area.

[0016] In an embodiment, based on the payment success message, determining that the seller delivery service to be processed belongs to a second service area includes: based on the payment success message, determining the registered location of the first seller and taking the service area where it is located as the second service area.

[0017] In one embodiment, after routing the seller delivery service to the second seller service site, the method further includes: routing the order settlement service corresponding to the first seller to the second seller service site, so that the second seller service site processes the order settlement service by docking with the second seller, and locally stores the service data generated by processing the order settlement service at the site.

[0018] In one embodiment, the several service areas correspond to several area sites; after routing the seller delivery service to the second seller service site, the method further includes: in response to an order viewing instruction issued by the first buyer, querying order information of multiple orders associated with the several area user identifiers from the several area sites for the first buyer to view, and the multiple orders include the first order.

[0019] In one embodiment, the several service areas correspond to several area sites; before receiving a payment request initiated by the first buyer for the first order, the method further includes: querying multiple historical orders associated with the several area user identifiers from the several area sites; and making product recommendations to the first buyer based on the purchased products included in the multiple historical orders.

[0020] According to a second aspect, there is provided a service processing method, where the execution subject of the method is a service platform, and the service platform is provided with multiple area sites corresponding to multiple service areas, and each area site includes a corresponding seller service site and a buyer service site; the method includes: determining that a first service needs to be processed currently; when determining that the processing of the first service needs to be docked with a first buyer, determining the first buyer service site corresponding to the first service area to which the first buyer belongs; where the first buyer corresponds to a first global user identifier and has a first area user identifier in the first service area, and the first area user identifier is determined based on several area user identifiers associated with the first global user identifier; routing the first service to the first buyer service site, so that the first buyer service site processes the first service by docking with the first buyer based on the first area user identifier, and locally stores the service data generated by processing the first service; when determining that the processing of the first service needs to be docked with a first seller, determining the second seller service site corresponding to the second service area to which the first seller belongs; where the registered place of the first seller is located in the second service area; routing the first service to the second seller service site, so that the second seller service site processes the first service by docking with the first seller, and locally stores the service data generated by processing the first service.

[0021] In one embodiment, the first service is the buyer payment service; determining that the first service needs to be processed currently includes: in response to a payment request initiated by a first buyer for a first order, determining that the buyer payment service needs to be processed currently, where the payment request includes a selected payment channel; wherein, when it is determined that the processing of the first service needs to be docked with the first buyer, determining the first buyer service site corresponding to the first service area to which the first buyer belongs includes: based on a plurality of buyer services that need to be docked with the buyer preset, determining that the buyer payment service is included in the plurality of buyer services; determining the first buyer service site corresponding to the first service area to which the first buyer belongs; wherein, the registered place of the payment institution corresponding to the payment channel is located in the first service area; wherein, routing the first service to the first buyer service site, so that the first buyer service site docks with the first buyer based on the first area user identifier, processes the first service, and locally stores the service data generated by processing the first service, includes: routing the buyer payment service to the first buyer service site, so that the first buyer service site docks with the payment channel and docks with the first seller based on the first area user identifier, processes the buyer payment service, and locally stores the service data generated by processing the buyer payment service.

[0022] In one embodiment, the first service is the seller delivery service; determining that the first service needs to be processed currently includes: in response to receiving a payment success message for a first order, determining that the seller delivery service needs to be processed currently, where the first order includes goods provided by the first seller; wherein, when it is determined that the processing of the first service needs to be docked with the first buyer, determining the first buyer service site corresponding to the first service area to which the first buyer belongs includes: based on a plurality of seller services that need to be docked with the seller preset, determining that the seller delivery service is included in the plurality of seller services.

[0023] According to a third aspect, there is provided a service processing apparatus integrated in a service platform. The service platform is provided with a plurality of regional sites corresponding to a plurality of service areas, and each regional site includes a corresponding buyer service site and a seller service site; the apparatus includes: a payment request receiving unit configured to receive a payment request initiated by a first buyer for a first order, the first buyer corresponding to a first global user identifier, the goods in the first order being provided by a first seller, and the payment request including a selected payment channel; a first area determination unit configured to determine a first service area to which the buyer payment service corresponding to the payment request belongs; the first regional site corresponding to the first service area includes a first buyer service site; the first buyer has a first regional user identifier in the first service area, which is determined based on a plurality of regional user identifiers associated with the first global user identifier; the registered location of the payment institution corresponding to the payment channel is located in the first service area; a payment service routing unit configured to route the buyer payment service to the first buyer service site, so that the first buyer service site processes the buyer payment service by docking with the payment channel and docking with the first buyer based on the first regional user identifier, and locally stores the service data generated by processing the buyer payment service; a payment success obtaining unit configured to obtain a payment success message corresponding to the payment request; a second area determination unit configured to determine, based on the payment success message, a second service area to which the seller delivery service to be processed belongs, the registered location of the first seller being located in the second service area, and the second regional site corresponding to the second service area includes a second seller service site; a delivery service routing unit configured to route the seller delivery service to the second seller service site, so that the second seller service site processes the seller delivery service by docking with the first seller and locally stores the service data generated by processing the seller delivery service.

[0024] According to a fourth aspect, there is provided a service processing apparatus integrated in a service platform. The service platform is provided with a plurality of regional sites corresponding to a plurality of service areas, and each of the regional sites includes a corresponding seller service site and a buyer service site. The apparatus includes: a service determination unit configured to determine that a first service needs to be processed currently; a buyer site determination unit configured to, when it is determined that the processing of the first service needs to be docked with a first buyer, determine a first buyer service site corresponding to a first service area to which the first buyer belongs; wherein, the first buyer corresponds to a first global user identifier and has a first regional user identifier in the first service area, and the first regional user identifier is determined based on a plurality of regional user identifiers associated with the first global user identifier; a buyer service routing unit configured to route the first service to the first buyer service site, so that the first buyer service site docks with the first buyer based on the first regional user identifier, processes the first service, and locally stores service data generated by processing the first service; a seller site determination unit configured to, when it is determined that the processing of the first service needs to be docked with a first seller, determine a second seller service site corresponding to a second service area to which the first seller belongs; wherein, the registration place of the first seller is located in the second service area; a seller service routing unit configured to route the first service to the second seller service site, so that the second seller service site processes the first service by docking with the first seller, and locally stores service data generated by processing the first service.

[0025] According to a fifth aspect, there is provided a computer-readable storage medium having a computer program stored thereon. When the computer program is executed on a computer, the computer is caused to execute the method described in the first aspect or the second aspect.

[0026] According to a sixth aspect, there is provided a computing device including a memory and a processor. An executable code is stored in the memory, and when the processor executes the executable code, the method described in the first aspect or the second aspect is implemented.

[0027] In summary, by adopting the service processing method disclosed in the embodiments of this specification, while ensuring that service data meets regulatory constraints, users only need to complete registration on the service platform once to use services provided by global sellers, and sellers and payment channels only need to be connected to the service platform once to be reused for global users or global buyers. This can undoubtedly greatly improve the user experience and effectively promote the development of services. Description of the Drawings

[0028] To more clearly illustrate the technical solutions of the multiple embodiments disclosed in this specification, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only the multiple embodiments disclosed in this specification. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0029] Figure 1 Schematic diagram showing the association of user global and regional identity identifiers according to an example;

[0030] Figure 2 Schematic diagram showing the deployment of a logical site according to an embodiment;

[0031] Figure 3 Schematic diagram showing the scenario architecture of a user using global services according to an embodiment;

[0032] Figure 4 Schematic diagram showing the flowchart of a service processing method according to an embodiment;

[0033] Figure 5 Schematic diagram showing the flowchart of a service processing method according to another embodiment;

[0034] Figure 6 Schematic diagram showing the structure of a service processing apparatus according to an embodiment;

[0035] Figure 7 Schematic diagram showing the structure of a service processing apparatus according to another embodiment. Detailed implementation manners

[0036] The following describes the multiple embodiments disclosed in this specification in conjunction with the drawings.

[0037] As mentioned above, in response to the differentiated regulatory requirements of different countries, the common practice in the industry is to physically isolate the services in different countries or regions. For example, a certain service platform (such as an e-commerce platform) establishes national sites in two countries, and these two national sites are completely isolated from the domain name, account system, system deployment to data storage.

[0038] Although this approach can meet regulatory constraints, it will affect the user experience and business development. For example, if a person wants to use services on two national sites established by a certain service platform, they need to register for an account on the two national sites separately. At this time, the same person will have two platform accounts. However, since the account systems of the two national sites are completely isolated and not connected, the user data corresponding to these two platform accounts is also isolated. This will affect the user experience. On the one hand, it requires the user to register repeatedly, which is cumbersome. On the other hand, in one national site established by the user on the platform, they cannot see their purchase records in another national site. Moreover, due to the isolation of user data, personalized recommendations can only be made based on each site separately, such as platform friend recommendations and product recommendations, etc., which will result in limited accuracy of the recommendation results, limited user experience, and at the same time restrict business development.

[0039] In addition, the two national sites are independent of each other. If a seller or payment institution wants to conduct business on the two national sites, they need to sign contracts with the two national sites separately. This will reduce the business enthusiasm of the seller and payment institution. At the same time, it will limit the number of sellers and payment institutions accessing the service platform, thus affecting the user experience on the service platform. In addition, the access cost of the payment channels provided by the seller and payment institution is high and the reusability is low, which will also restrict business development.

[0040] Based on this, the inventor proposes a business processing method, which is especially suitable for cross-domain business. Through this business processing method, while ensuring that business data meets regulatory constraints, it enables users to complete registration on the service platform only once and then use the services provided by global sellers. Sellers and payment channels only need to access the service platform once and then can be reused for global users or global buyers. This will undoubtedly greatly improve the user experience and at the same time effectively promote the development of the business.

[0041] To implement the above business processing method, the inventor mainly proposes the following two aspects of design:

[0042] On the one hand, establish a global platform user model, which includes the global user identifier (or full-region user identifier, global user identifier) of each user, and the regional user identifiers of each user in each country or region. In one example, Figure 1 shows the global user identifier A of user A included in the global platform user model, and its regional user identifiers in N (a positive integer) regions, specifically including the regional user identifier A1 in region 1 (the region numbered 1), etc.

[0043] It should be noted that since users are usually natural persons, who are independent, free, and mobile individuals, the supervision of the data they generate is usually carried out in the region where the data is generated. One of the main matters of supervision is to restrict the storage location of the data. For example, a certain country requires that user data generated within its territory be stored only within the country. However, it usually does not restrict the normal and compliant access to the data it supervises.

[0044] The global platform user model established above is itself an association relationship between some identifiers and does not contain user sensitive information. Therefore, it does not violate the data supervision rules. Moreover, the user identifier can be automatically generated by the service platform after identifying the same user in different regions, without the need for the user to re-register, or even be aware of it, thus saving user operations. In addition, through this global platform user model, the user data generated by the same user in different regions can be integrated. Therefore, no matter which region the user is in, services can be provided to the user based on the user's full data globally, thus greatly improving the user experience.

[0045] On the other hand, considering that the main characteristics of cross-domain business are that the buyer and the seller belong to different regions and the data supervision requirements in different regions are different, it is proposed to design logical sites for each country and region respectively, and divide the logical sites into buyer business sites for handling buyer business and seller business sites for handling seller business. Based on this, cross-domain business can be split into buyer business and seller business, and according to the region to which the buyer business belongs, the buyer business can be routed to the buyer business site in the corresponding region to enable this site to process the buyer business and locally store the buyer business data generated by the processing. Similarly, according to the other region to which the seller business belongs, the seller business can be routed to the seller business site corresponding to this other region to enable this site to process the seller business and locally store the seller business data generated by the processing. It should be understood that a site is a storage area where business execution logic, business data, etc. can be stored. A logical site means that it is a separate site logically, rather than a physically isolated site. A logical site can provide normal, compliant, and legal data access services to other sites or platforms.

[0046] In one example, Figure 2 shows multiple logical sites (or multiple regional sites) corresponding to multiple regions, where each logical site includes a buyer business site and a seller business site. The business routing module shown is used to route the buyer business and seller business included in the cross-domain business to the corresponding buyer business site and seller business site respectively.

[0047] It should be noted that for the determination of the location of the seller's business, it mainly depends on the region where the seller belongs in the seller's business. Before providing services, the seller usually needs to register or conduct identity registration with the relevant department, and the region where the registration is located has jurisdiction over the seller. Therefore, the region where the seller belongs can be determined based on the seller's registration location, and then the region where the seller belongs in the seller's business can be used as the location of the seller's business.

[0048] In addition, for the payment channel, similar to the seller, it has a natural identity, and the natural identity of the payment channel is the registration location of the payment institution behind it. The payment channel is mainly related to the buyer's payment business. When the buyer uses the services provided by the seller through the service platform, the buyer needs to pay for the service, and at this time, the selection of the payment channel is involved. Therefore, in the buyer's payment business, the location of the payment channel and the region where the buyer is located can be comprehensively considered to determine the region corresponding to the buyer's payment business for routing the buyer's payment business.

[0049] In an example, for intuitive understanding, Figure 3 shows a scenario of providing global services based on the global identity identifier and regional identity identifier of user A. Among them, the buyer business site 1 docks with the buyer business of user A based on the regional identity identifier A1; in addition, N (a positive integer) buyer business sites corresponding to N regions each dock with a local payment channel, and the corresponding N seller business sites each correspond to a local seller. In this way, the seller and the payment channel (or the payment institution behind it) only need to sign a contract with the service platform once to provide services for global buyers.

[0050] The above mainly introduces the inventive concept of the above-mentioned business processing method proposed by the inventor. Next, in combination with specific embodiments, the implementation steps of the above-mentioned business processing method will be described.

[0051] Specifically, Figure 4 shows a schematic flowchart of a business processing method according to an embodiment. The execution subject of this business processing method is the service platform. Specifically, the service platform sets up multiple regional sites corresponding to multiple service regions, and each regional site includes a corresponding buyer business site and a seller business site.

[0052] Regarding the above service platform, in one embodiment, the service platform may be implemented as a server cluster or a device cluster. In one embodiment, the service platform may be an e-commerce platform, an online trading platform, etc. The service platform allows service providers (sellers) to settle in and provide services or goods for users in the service platform. It should be noted that services and goods in this article can be considered equivalent, referring to generalized services and generalized goods. In one embodiment, the goods (or services) may include physical goods (such as mobile phones), virtual goods (such as e-books, video courses, music resources, etc.), consulting services, etc.

[0053] Regarding the above-mentioned multiple service regions, any one of the regions may be a separate country or region, or a geographical scope divided according to regulatory rules. For example, if several countries reach an agreement on data sharing or coordinated supervision, these countries can be grouped into the same service region. It should be understood that the multiple service regions are mutually exclusive, that is, there will be no overlapping geographical scopes. In addition, the service platform can determine the countries, regions or cities where it can carry out services according to its own development scale and business capabilities, and then divide multiple service regions according to its business coverage and current data supervision rules. In addition, since the multiple regional sites corresponding to the multiple service regions are all logical sites, they can be flexibly adjusted in the future according to the changes in business development and data supervision rules.

[0054] Regarding the above-mentioned multiple regional sites, they correspond to the multiple service regions, and each regional site corresponds to a service region for docking and processing the business belonging to the corresponding service region. For the description of the regional sites, reference can also be made to the previous description of the logical sites and sites, which will not be elaborated here.

[0055] Regarding the buyer business sites and seller business sites included in each regional site, the buyer business sites are used to dock and process local (the region to which they correspond) buyer business, and the seller business sites are used to dock and process local seller business. For the description of the buyer business sites and seller business sites, reference can also be made to the previous description of the buyer business sites and seller business sites.

[0056] The above introduces the regional sites, buyer business sites and seller business sites set up by the service platform. Based on these sites, the implementation of the above business processing method can be realized. As Figure 4 shown, the above business processing method includes the following steps:

[0057] Step S410: Receive a payment request initiated by a first buyer for a first order. The first buyer corresponds to a first global user identifier. The goods in the first order are provided by a first seller. The payment request includes a selected payment channel. Step S420: Determine a first service area to which the buyer payment service corresponding to the payment request belongs. The first regional site corresponding to the first service area includes a first buyer business site. The first buyer has a first regional user identifier in the first service area, which is determined based on a number of regional user identifiers associated with the first global user identifier. The number of regional user identifiers corresponds to a number of service areas. The registered location of the payment institution corresponding to the payment channel is in the first service area. Step S430: Route the buyer payment service to the first buyer business site, so that the first buyer business site processes the buyer payment service by docking with the payment channel and docking with the first buyer based on the first regional user identifier, and locally stores the business data generated from processing the buyer payment service. Step S440: Obtain a payment success message corresponding to the payment request. Step S450: Based on the payment success message, determine that the seller shipment service to be processed belongs to a second service area. The registered location of the first seller is in the second service area. The second regional site corresponding to the second service area includes a second seller business site. Step S460: Route the seller shipment service to the second seller business site, so that the second seller business site processes the seller shipment service by docking with the first seller and locally stores the business data generated from processing the seller shipment service.

[0058] Regarding the above steps, it should be noted first that the "first" in "first buyer", "first order", etc., and the "second" in "second service area", etc. are for the sake of clear description and are used for distinguishing similar things, without other restrictive effects such as sorting.

[0059] The above steps are specifically as follows:

[0060] First of all, in step S410, receive a payment request initiated by a first buyer for a first order. The first buyer corresponds to a first global user identifier. The goods in the first order are provided by a first seller. The payment request includes a selected payment channel. It should be noted that the above first buyer can be any user using the service platform, the above first order can be any order submitted by the first buyer, and the above first seller can be any service provider among the service providers who have entered the service platform.

[0061] Regarding the determination of the above-mentioned first global user identifier, in one embodiment, before the above step S410, the method may include: in response to the successful login operation of the first buyer, determining the first global user identifier corresponding to the first buyer. In a specific embodiment, the determination of the first global user identifier may include: obtaining the login user name corresponding to the successful login operation, and then performing a hash operation on the login user name to obtain the first global user identifier. It should be understood that there is a one-to-one correspondence between the original data and the encrypted data obtained after performing a hash operation on it. Therefore, the global user identifier obtained in this way has a one-to-one mapping relationship with the login account and can be used to uniquely identify the user safely and reliably. In another specific embodiment, the determination of the first global user identifier may further include: obtaining the login user name corresponding to the successful login operation, and then querying the first global user identifier corresponding to the login user name based on the pre-established mapping relationship between the user name and the global user identifier. In yet another specific embodiment, the determination of the first global user identifier may also include: according to the login user name, determining the regional user identifier corresponding to the login user name in its registration region from the registration information stored in multiple regional sites, and then determining the global user identifier corresponding to the regional user identifier according to the above-mentioned global platform user model, that is, the above-mentioned first global user identifier.

[0062] On the other hand, the determination of the above-mentioned first global user identifier can be triggered not only by a successful login operation, but also by other operations performed after a successful login, such as a click operation on a product picture, or a submission operation for an order, or a payment operation for an order. In addition, the above-mentioned first global user identifier can also be determined without logging in. In a specific embodiment, after receiving a platform access request (corresponding to a user opening the service platform interface), the service platform can obtain the MAC (Media Access Control Address) address of the device that sent the access request, and then determine the corresponding global user identifier according to the pre-established mapping relationship between the MAC address and the global user identifier, that is, the above-mentioned first global user identifier.

[0063] For the generation of the above-mentioned first global user identifier, in one embodiment, it may be performed when the user registers for a platform account. In a specific implementation, for a newly registered account that is successfully registered, a global user identifier corresponding to the new account may be generated through a hashing operation, or a data sequence may be generated using a random algorithm as the new global user identifier, and a mapping relationship between the new account and the new global user identifier may be established. In another embodiment, it may also be performed during the process of the user operating on the service platform. In a specific embodiment, after receiving a platform access request, the service platform may obtain the MAC address of the device that sent the access request, and then, according to the established mapping relationship between the MAC address and the global user identifier, check whether the MAC address of the device is included therein. If not, a new global user identifier corresponding thereto may be generated, and the mapping relationship may be updated using the new global user identifier.

[0064] The determination and generation of the first global user identifier are introduced above.

[0065] On the other hand, regarding the creation of the above-mentioned first order. In one embodiment, the order creation service may be completed by the service platform. Further, in a specific embodiment, the service platform may then send the service data of the order creation service to the buyer service site in the service area where the first buyer is located. It should be noted that in the case where the user abandons the payment for the first order, or in the case where the user cancels the first order without making a payment for the first order, the service platform may discard the service data of the first order.

[0066] Correspondingly, this step may include: the service platform receives the above-mentioned payment request from the user terminal used by the first buyer. It should be understood that the user uses the user interaction interface or the platform APP provided by the service platform through this user terminal (such as a smart phone, a tablet computer, etc.).

[0067] In another embodiment, the order creation service can also be completed by the buyer service site in the service area where the first buyer belongs. Specifically, in response to specific operations of the first buyer on the service platform, the pre-payment buyer service corresponding to the first buyer can be routed to the buyer service site in its area. The specific operations can include login operations, successful login operations, page scrolling operations, picture click operations, order submission operations, etc. The pre-payment buyer service can include platform login services, interface browsing services, order creation services, etc. In a specific embodiment, before routing the pre-payment buyer service to the buyer service site in the area where the first buyer is located, it is necessary to determine the area where the first buyer is located, and this area can be determined by the location element information of the first buyer obtained in real time. Specifically, in response to the above specific operations, the location element information of the first buyer can be obtained to determine the third service area where the first buyer is currently located. In a specific embodiment, the location element information can include: longitude and latitude information uploaded by the user terminal, network address, IP (Internet Protocol Address), the logistics receiving address or the logistics sending address of the first buyer. In this way, the third service area where the user is currently located can be determined, and then the order creation service can be routed to the third buyer service site in the corresponding third area site.

[0068] Correspondingly, this step may include: the service platform receiving a payment request initiated by the first buyer for the first order from the third buyer service site.

[0069] From the above, it is possible to receive the payment request initiated by the first buyer for the first order. And the goods in the first order are provided by the first seller, and the payment request includes the payment channel selected by the first buyer. Based on this, then in step S420, based on this payment request, it is determined that the buyer payment service to be processed belongs to the first service area.

[0070] As mentioned above, in the buyer payment service, there are users and payment channels involved. The service area where the user is located and the service area where the registered place of the payment structure corresponding to the payment channel is located may be the same or different. In the case of being the same, the common corresponding service area can be used as the first service area to which the buyer payment service belongs. In the case of being different, one of the two different service areas can be determined as the above first service area based on the guidance of data supervision requirements or the negotiation results between the service platform and the data supervision agencies in different service regions. Based on this, this step has multiple implementation manners.

[0071] In one embodiment, the service area to which the buyer payment service belongs can be determined from the perspective of the service area where the first buyer is located. In one example, before step S410, the method may further include: obtaining the location element information of the first buyer; then, based on the location element information, determining the third service area where the first buyer is currently located; and then, based on the third service area, obtaining a number of alternative payment channels (such as Yu'ebao payment, online banking payment of a certain bank, and payment via a certain wallet) to be provided for the first buyer to select.

[0072] In a specific example, the registered locations of the payment institutions corresponding to the number of alternative payment channels (such as Huabei payment, Yu'ebao payment, online banking payment of a certain bank, etc.) are all located in the third service area (such as China). Thus, the registered location corresponding to the payment channel selected from the number of alternative payment channels must also be located in the third service area. Accordingly, this step may include: determining the third service area as the service area to which the above-mentioned buyer payment service belongs. At this time, the above-mentioned first service area is equivalent to the third service area.

[0073] In another specific example, the service areas where the number of registered locations corresponding to the number of alternative payment channels are located can be service areas that allow the storage of locally generated service data (including buyer payment service data) in the above-mentioned third service area. This means that the service areas corresponding to the number of alternative payment channels may include the above-mentioned third service area or other service areas. Regardless of which payment channel the user selects, storing the buyer payment service data in the third service area complies with the data supervision requirements. Accordingly, this step may still include: determining the third service area as the service area to which the above-mentioned buyer payment service belongs. At this time, the above-mentioned first service area is still equivalent to the third service area.

[0074] In another embodiment, the service area to which the buyer payment service belongs can be determined from the perspective of the service area where the registered location of the payment institution to which the payment channel belongs is located. In one example, this step may include: querying the registered location corresponding to the selected payment channel, and then determining the service area where the registered location is located as the first service area to which the buyer payment service belongs. At this time, the first service area may be the same as the above-mentioned third service area. If not, if the data supervision requirements in the third service area allow the storage of its service data in the first service area, it is possible to assign the buyer payment service to the first service area. If the data supervision requirements in the third service area do not allow data to leave the country, it can be resolved through negotiation or switch to the above-mentioned embodiment of determining the first service area from the user perspective.

[0075] In addition, the above-mentioned first buyer has a first regional user identifier in the first service area, which is determined based on a number of regional user identifiers associated with the first global user identifier, and the number of regional user identifiers corresponds to a number of service areas. In one embodiment, after determining that the buyer payment service belongs to the first service area, the first regional user identifier of the first buyer in the first service area can be determined. In a specific embodiment, according to the first global user identifier of the first buyer, a number of regional user identifiers associated therewith and the corresponding number of service areas can be queried according to the above-mentioned global platform user model, and then it can be queried whether the first service area is included in the number of service areas. If it is included, the first regional user identifier corresponding to the first service area can be determined according to the mapping relationship between the number of service areas and the number of regional user identifiers; if it is not included, a new user identifier can be created as the first regional user identifier, and the corresponding relationship between the first regional user identifier and the first service area can be added to the mapping relationship between the number of service areas and the number of regional user identifiers. In another embodiment, after determining that the first buyer is located in the first service area, the corresponding first regional user identifier can also be determined. In a specific embodiment, in response to a successful login operation, an order submission operation, an interface browsing operation, etc., the location element information of the first buyer can be obtained, and then it can be determined that the first buyer is located in the first service area and the first regional user identifier that the first buyer has in the first service area. Based on this, the above-mentioned first regional user identifier can be obtained.

[0076] As described above, based on the payment request, it can be determined that the buyer payment service to be processed belongs to the first service area. Moreover, the first buyer has a first regional user identifier in the first service area. Additionally, according to the above settings of the service platform for the site, it can be clarified that the regional site corresponding to the first service area (referred to as the first regional site in the text) includes a buyer business site (referred to as the first buyer business site in the text) for processing the buyer business in the first service area.

[0077] Accordingly, step S430 can be executed to route the buyer payment service to the first buyer business site, so that the first buyer business site processes the buyer payment service by docking the payment channel and docking the first seller based on the first regional user identifier, and locally stores the business data generated by processing the buyer payment service.

[0078] It should be noted that for the connection between users and payment channels in the buyer payment service, existing technologies can be used. Among them, connecting to the first seller based on the user identifier in the first region means that during the process of connecting to the first buyer, the first region user identifier is used to identify the first buyer, so as to store its relevant business data, and at the same time, facilitate subsequent access and invocation. Among them, local storage means storing in the first service region, because the first service region is local relative to the first buyer's business site. Specifically, it can be stored within the first buyer's business site, or in an off-site local database. On the other hand, in one embodiment, if data related to the first region user identifier has been stored in the first buyer's business site, then the newly generated business data of this buyer payment service can be stored in an associated manner. In another embodiment, if the first region user identifier does not exist among the multiple region user identifiers stored in the first buyer's business site, then it is added to the multiple region user identifiers.

[0079] For ease of understanding, a brief introduction to the buyer payment service is provided. The processing of the buyer payment service mainly includes: connecting to the payment channel, so that the system of the payment institution corresponding to the payment channel deducts the amount to be paid for the first order from the payment account of the first buyer on the payment channel, and transfers the deducted amount to the financial account of the service platform. It should be understood that afterwards, the service platform will settle with the first seller according to the subsequent processing situation of the first order.

[0080] As described above, it is possible to route the buyer payment service to the first buyer's business site, so that the first buyer's business site completes the processing of the buyer payment service. Further, in step S440, a payment success message corresponding to the payment request can be obtained.

[0081] In one embodiment, after the system of the above payment institution successfully executes the deduction operation on the first buyer, it sends the payment success message to the first buyer's business site. Correspondingly, this step may include: the service platform receives the above payment success message from the above first buyer's business site. In another embodiment, after the system of the above payment institution successfully executes the deduction operation on the first buyer, it can send the payment success message to both the first buyer's business site and the service platform at the same time. Correspondingly, this step may include: receiving the above payment success message from the system of the above payment institution.

[0082] The above can obtain the payment success message. Based on this payment success message, in step S450, based on this payment success message, it is determined that the seller's shipping business to be processed belongs to the second service area, and the registration location of the first seller is located in the second service area. In one embodiment, this step may include: based on this payment success message, determining that the registration location of the above-mentioned first seller is located in the above-mentioned second service area; further, determining the second service area as the service area to which the seller's shipping business belongs. In another embodiment, this step may further include: based on the mapping relationship established in advance between the seller and the service area, determining the second service area corresponding to the first seller.

[0083] In yet another embodiment, the second service area corresponding to the first seller may be determined before step S450. For example, in response to the creation of the above-mentioned first order, or in response to the payment request of the above-mentioned first order, the second service area corresponding to the first seller is determined. Accordingly, in this step, the above-mentioned second service area determined in advance can be directly obtained as the service area to which the seller's shipping business belongs.

[0084] From the settings of the service platform for the site, it can be seen that the regional site corresponding to the second service area (referred to as the second regional site in the text) includes a seller business site (referred to as the second seller business site in the text). In one implementation manner, step S450 may be replaced by: based on this payment success message, determining that the seller's shipping business to be processed belongs to the second seller business site for processing. In one embodiment, the second seller business site corresponding to the first seller may be determined based on the mapping relationship established in advance between the seller and the seller business site.

[0085] From the above, it can be determined that the seller's shipping business to be processed belongs to the second service area, and it can be clarified that the second regional site corresponding to the second service area includes the second seller business site. Further, in step S460, the seller's shipping business can be routed to the second seller business site, so that the second seller business site processes the seller's shipping business by docking with the first seller and locally stores the business data generated by processing the seller's shipping business. It should be noted that, in one embodiment, it may also be determined in this step that the site responsible for processing the seller's shipping business is the second seller business site. In addition, for docking with the first seller in the seller's shipping business, it can be implemented using existing technologies. In this way, the routing of the seller's shipping business can be realized, so that the second seller business site completes the processing of the seller's shipping business by docking with the first seller.

[0086] By implementing the above steps S410 - S460, the processing of cross - domain services can be achieved. In one case, if the above - mentioned first service area and the second service area are different areas, the corresponding overall service is a cross - domain (cross - regional) service. In another case, the above - mentioned first service area and the second service area can also be the same area, in which case the processing of in - domain (same - regional) services can be achieved. In short, the above service processing method supports the processing of both in - domain and cross - domain services, facilitating the unified management of all services.

[0087] It should be noted that in one embodiment, after the above step S460, the method may further include: routing the order settlement service corresponding to the first seller to the second seller's service site, so that the second seller's service site processes the order settlement service by docking with the second seller and locally stores the service data generated from processing the order settlement service at the site. It should be noted that the order settlement service mainly includes the service platform transferring the payment for the delivered order to the corresponding seller. In a specific embodiment, there are various ways to trigger the routing of the order settlement service. For example, receiving a message of confirming receipt of goods for the first order from the above - mentioned first buyer's service site, or receiving such a message from the user terminal of the first buyer, or automatically triggering the routing of the order settlement service in response to a set period (such as 1 week or 1 month) for the order settlement service. In this way, by routing the order settlement service, the second seller's service site can complete the processing of the order settlement service.

[0088] On the other hand, as mentioned above, through the above service processing method, it is possible to enable the user to view all their data, and it is also possible to perform precise recommendations for the user using all this data to improve the user experience.

[0089] Specifically, several service areas associated with several regional identity identifiers of the first buyer correspond to several regional sites. Thus, in one embodiment, after the above step S460, the method may further include: in response to an order viewing instruction issued by the first buyer, querying the order information of multiple orders associated with the several regional user identifiers from the several regional sites for the first buyer to view, and the multiple orders include the first order. In this way, centralized viewing of orders in each service area can be achieved.

[0090] In another embodiment, before the above step S410, the method may further include: querying multiple historical orders associated with the several regional user identifiers from the several regional sites; and then making product recommendations to the first buyer based on the purchased products included in the multiple historical orders. In this way, it can assist the user in locating the target product, such as the product included in the first order.

[0091] In summary, by adopting the service processing method disclosed in the embodiments of this specification, while ensuring that service data meets regulatory constraints, users only need to complete registration on the service platform once to use the services provided by global sellers, and sellers and payment channels only need to be connected to the service platform once to be reused for global users or global buyers. This undoubtedly greatly improves the user experience and effectively promotes the development of the business.

[0092] In addition, it should be noted that by implementing the above service processing method, multi-channel payment services for an order and group buying services for multiple users can also be realized. The group buying service refers to supporting multiple users to jointly submit an order. Moreover, multiple channels can belong to different service regions, and multiple users can also belong to different service regions. In one embodiment, a user selects to pay for an order with an amount of (29 yuan) using both payment channel A (account balance of 10 yuan) and payment channel B (account balance of 20 yuan) at the same time. Among them, payment channel A corresponds to service region A, and payment channel B corresponds to service region B. At this time, the buyer payment business for this order can be split into two buyer payment businesses, which are respectively routed to the buyer business site A corresponding to service region A and the buyer business site B corresponding to service region B, so that the two buyer business sites can respectively connect to payment channel A and payment channel B and each complete the processing of one of the buyer payment businesses, thereby completing the payment for this order. Similarly, for the scenario of multiple users, the regional identity identifiers corresponding to each user can be determined respectively, and then split into multiple buyer businesses, which are respectively routed to the corresponding buyer business sites for processing. In this way, the service platform can realize multi-channel payment services and group buying services for users from different regions.

[0093] According to an embodiment of another aspect, the embodiments of this specification also disclose a service processing method. In this service processing method, the service platform judges the service to be processed. When it is judged that the service belongs to the buyer business, it is routed to the buyer business site in the corresponding region for processing, and when it is judged that the service belongs to the seller business, it is routed to the seller business site in the corresponding region for processing.

[0094] Specifically, Figure 5 The flowchart showing the service processing method according to another embodiment, and the execution subject of this service processing method is the service platform. Specifically, the service platform sets multiple regional sites corresponding to multiple service regions, and each regional site includes a corresponding buyer business site and a seller business site.

[0095] As Figure 5 shown, the method may include the following steps:

[0096] Step S510, determining that the first business needs to be processed currently; further, on the one hand, steps S520 and S530 may be executed. Specifically, in step S520, when it is determined that the processing of the first business needs to be connected to the first buyer, the first buyer business site corresponding to the first service area to which the first buyer belongs is determined; wherein the first buyer corresponds to the first global user identifier and has a first regional identity identifier in the first service area, which is determined based on a plurality of regional user identifiers associated with the first global user identifier; in step S530, the first business is routed to the first buyer business site, so that the first buyer business site is connected to the first service area based on the first regional user identifier. The first buyer is connected to the user identifier, the first business is processed, and the business data generated by the processing of the first business is locally stored; on the other hand, steps S540 and S550 may be executed. Specifically, in step S540, when it is determined that the processing of the first business needs to be connected to the first seller, the second seller business site corresponding to the second service area to which the first seller belongs is determined; wherein the registered place of the first seller is located in the second service area; in step S550, the first business is routed to the second seller business site, so that the second seller business site processes the first business by connecting to the first seller, and the business data generated by the processing of the first business is locally stored.

[0097] The above steps are as follows:

[0098] First, in step S510, it is determined that the first business needs to be processed. Specifically, in one embodiment, the service platform can determine the corresponding business to be processed based on the operation of the user or seller in the service platform. In another embodiment, the service platform can determine the corresponding business to be processed based on the message sent by the site set therein, combined with the preset business logic. In another embodiment, the service platform can also automatically trigger the processing of the business based on certain periodic businesses preset therein (for example, order settlement business with sellers).

[0099] Based on this, in a specific embodiment, the above-mentioned first business is a buyer payment business. Accordingly, this step may include: responding to a payment request initiated by the first buyer for the first order, determining that the buyer payment business currently needs to be processed, and the payment request includes a selected payment channel.

[0100] In another specific embodiment, the above-mentioned first business is a seller delivery business. Accordingly, this step may include: in response to receiving a payment success message for a first order, determining that the seller delivery business needs to be processed currently, and the first order includes goods provided by the first seller.

[0101] In this way, it can be determined that the first service currently needs to be processed.

[0102] It should be noted that the service platform provides services for buyers and sellers. Accordingly, the services processed therein can be services that need to be connected with buyers, services that need to be connected with sellers, or other services that do not need to be connected with buyers and sellers. The business transactions between buyers and sellers are realized through the service platform as an intermediary. Therefore, any transaction matters between buyers and sellers can be split into seller services that need to be connected with buyers and seller services that need to be connected with sellers.

[0103] Accordingly, for the determination of whether the first service belongs to a buyer service or a seller service. In one embodiment, multiple buyer services and multiple seller services can be preset according to the platform service content, and then used for the matching of the first service. That is to say, if the first service is a service that requires the participation of a buyer or a seller, it will surely fall into the multiple seller services or the multiple seller services. In a specific embodiment, the multiple buyer services can include order creation service, order buyer payment service, and personal information change service. In a specific embodiment, the seller services can include: seller new product listing (posting new products in the platform store) service, seller delivery service, and order settlement service.

[0104] In another embodiment, each service has its own execution logic. Accordingly, it is possible to directly determine whether it is necessary to connect with a buyer or a seller for executing the first service according to the service logic of the first service.

[0105] Based on this, after determining that the first service needs to be processed currently, on the one hand, steps S520 and S530 may be executed. Specifically, in one embodiment, the above first service is a buyer payment service. Therefore, step S520 may include: determining, based on the multiple buyer services that need to be connected with users preset in advance, that the multiple buyer services include the buyer payment service; further determining that the first service area to which the first buyer belongs corresponds to the first buyer service site, and the registration place of the payment institution corresponding to the payment channel is located in the first service area; further, step S530 may include: routing the buyer payment service to the first buyer service site, so that the first buyer service site processes the buyer payment service by connecting with the payment channel and connecting with the first seller based on the first area user identifier, and locally stores the service data generated by processing the buyer payment service.

[0106] On the other hand, steps S540 and S550 may be executed. Specifically, in one embodiment, the above first service is the seller shipping service. Thus, step S540 may include: determining, based on multiple seller services to be docked with sellers preset in advance, that the seller shipping service is included in the multiple seller services. Further, step S550 may include: routing the seller shipping service to the second seller service site, so that the second seller service site processes the seller shipping service by docking with the first seller, and locally stores the service data generated by processing the seller shipping service.

[0107] In addition, it should be noted that Figure 5 For the description of the steps in Figure 4 reference may also be made to the relevant description of the steps in

[0108] In summary, by adopting the service processing method disclosed in the embodiments of this specification, while ensuring that service data meets regulatory constraints, users only need to complete one registration on the service platform to use the services provided by global sellers, and sellers and payment channels only need to be connected to the service platform once to be reused for global users or global buyers. This undoubtedly can greatly improve the user experience and effectively promote the development of the business.

[0109] Corresponding to the service processing method disclosed in the above embodiments, the embodiments of this specification also disclose a service processing device. Specifically as follows:

[0110] Figure 6 FIG. shows a schematic structural diagram of a service processing device according to an embodiment. The device is integrated into a service platform, and the service platform is provided with multiple regional sites corresponding to multiple service regions, and each regional site includes a corresponding buyer service site and a seller service site. As Figure 6 shown, the device 600 includes:

[0111] A payment request receiving unit 601, configured to receive a payment request initiated by a first buyer for a first order. The first buyer corresponds to a first global user identifier, the goods in the first order are provided by a first seller, and the payment request includes a selected payment channel.

[0112] A first region determining unit 602, configured to determine a first service region to which the buyer payment service corresponding to the payment request belongs; the first service region corresponding to the first regional site includes a first buyer service site; the first buyer has a first regional user identifier in the first service region, which is determined based on several regional user identifiers associated with the first global user identifier; the registered location of the payment institution corresponding to the payment channel is located in the first service region.

[0113] The payment service routing unit 603 is configured to route the buyer payment service to the first buyer service site, so that the first buyer service site processes the buyer payment service by docking with the payment channel and docking with the first buyer based on the first regional user identifier, and locally stores the service data generated by processing the buyer payment service.

[0114] The payment success acquisition unit 604 is configured to acquire a payment success message corresponding to the payment request.

[0115] The second region determination unit 605 is configured to, based on the payment success message, determine that the seller delivery service to be processed belongs to the second service region, the registered place of the first seller is located in the second service region, and the second seller service site is included in the second region site corresponding to the second service region.

[0116] The delivery service routing unit 606 is configured to route the seller delivery service to the second seller service site, so that the second seller service site processes the seller delivery service by docking with the first seller, and locally stores the service data generated by processing the seller delivery service.

[0117] In one embodiment, the apparatus 600 further includes: a global identifier determination unit 607, configured to, in response to the successful login of the first buyer, determine the first global user identifier corresponding to the first buyer; an order creation unit 608, configured to, in response to receiving an order creation request initiated by the first buyer based on the commodity, create the first order.

[0118] In one embodiment, the global identifier determination unit 607 is specifically configured to: acquire the username of the first buyer; perform a hash operation on the username to obtain the first global user identifier; or, query the first global user identifier based on a pre-established mapping relationship between the username and the global user identifier.

[0119] In one embodiment, the apparatus 600 further includes: a location element acquisition unit 609, configured to acquire location element information of the first buyer; a buyer region determination unit 610, configured to determine the service region where the first buyer is currently located as the first service region according to the location element information; a region identifier determination unit 611, configured to determine the first regional user identifier of the first buyer in the first service region according to the several regional user identifiers corresponding to several service regions; an alternative channel acquisition unit 612, configured to acquire several alternative payment channels for the first buyer to select, and the registered places of the payment institutions corresponding to the several alternative payment channels are all located in the first service region.

[0120] In a specific embodiment, the location element information includes at least one of the following: longitude and latitude information, network address, Internet Protocol (IP) address, and the delivery address included in the first order.

[0121] In another specific embodiment, the area identification determination unit 611 is specifically configured to: when there is no user identification corresponding to the first service area among the several area user identifications, create a new user identification as the first area user identification; and classify the first area user identification into the several area user identifications.

[0122] In an embodiment, the first area determination unit 602 is specifically configured to: determine the registration location corresponding to the payment channel, and use the service area where it is located as the first service area.

[0123] In a specific embodiment, the apparatus 600 further includes: an area identification determination unit 611, configured to determine a first area user identification of the first buyer in the first service area according to the several area user identifications corresponding to several service areas.

[0124] In an embodiment, the second area determination unit 605 is configured to: based on the payment success message, determine the registration location of the first seller, and use the service area where it is located as the second service area.

[0125] In an embodiment, the apparatus 600 further includes: a settlement service routing unit 613, configured to route the order settlement service corresponding to the first seller to the second seller service site, so that the second seller service site processes the order settlement service by docking with the second seller, and locally stores the service data generated by processing the order settlement service at the site.

[0126] In an embodiment, the apparatus 600 further includes: an order viewing and processing unit 614, configured to, in response to an order viewing instruction issued by the first buyer, query order information of multiple orders associated with the several area user identifications from the several area sites for the first buyer to view, and the multiple orders include the first order.

[0127] In an embodiment, the apparatus 600 further includes a product recommendation unit 615, configured to: query multiple historical orders associated with the several area user identifications from the several area sites; and recommend products to the first buyer according to the purchased products included in the multiple historical orders.

[0128] In summary, by adopting the service processing device disclosed in the embodiments of this specification, while ensuring that service data meets regulatory constraints, users only need to complete registration on the service platform once to use the services provided by global sellers. Sellers and payment channels only need to be connected to the service platform once and can be reused for global users or global buyers. This will undoubtedly greatly improve the user experience and effectively promote the development of the business.

[0129] Figure 7 FIG. shows a schematic structural diagram of a service processing device according to another embodiment. The device 700 is integrated into a service platform, and the service platform is provided with a plurality of regional sites corresponding to a plurality of service regions, and each regional site includes a corresponding seller service site and a buyer service site. As Figure 7 shown, the device 700 includes:

[0130] A service determination unit 710, configured to determine that a first service needs to be processed currently; a buyer site determination unit 720, configured to determine a first buyer service site corresponding to a first service region to which the first buyer belongs when it is determined that the processing of the first service needs to be docked with a first buyer; wherein, the first buyer corresponds to a first global user identifier and has a first regional identity identifier in the first service region, and is determined based on a plurality of regional user identifiers associated with the first global user identifier; a buyer service routing unit 730, configured to route the first service to the first buyer service site, so that the first buyer service site docks with the first buyer based on the first regional user identifier, processes the first service, and locally stores the service data generated by processing the first service; a seller site determination unit 740, configured to determine a second seller service site corresponding to a second service region to which the first seller belongs when it is determined that the processing of the first service needs to be docked with a first seller; wherein, the registration location of the first seller is in the second service region; a seller service routing unit 750, configured to route the first service to the second seller service site, so that the second seller service site processes the first service by docking with the first seller and locally stores the service data generated by processing the first service.

[0131] In one embodiment, the first service is the buyer payment service; the service determination unit 710 is specifically configured to: in response to a payment request initiated by a first buyer for a first order, determine that the buyer payment service needs to be processed currently, where the payment request includes a selected payment channel; the buyer site determination unit 720 is specifically configured to: based on a plurality of buyer services that need to be docked with buyers preset, determine that the buyer payment service is included in the plurality of buyer services; determine a first buyer service site corresponding to the first service area to which the first buyer belongs; where the registered place of the payment institution corresponding to the payment channel is located in the first service area; the buyer service routing unit 730 is specifically configured to: route the buyer payment service to the first buyer service site, so that the first buyer service site processes the buyer payment service by docking the payment channel and docking the first seller based on the first area user identifier, and locally stores the service data generated by processing the buyer payment service.

[0132] In one embodiment, the first service is the seller delivery service; the service determination unit 710 is specifically configured to: in response to receiving a payment success message for a first order, determine that the seller delivery service needs to be processed currently, where the first order includes goods provided by the first seller; the seller site determination unit 740 is specifically configured to: based on a plurality of seller services that need to be docked with sellers preset, determine that the seller delivery service is included in the plurality of seller services.

[0133] In summary, by using the service processing device disclosed in the embodiments of this specification, while ensuring that service data meets regulatory constraints, users only need to complete one registration on the service platform to use the services provided by global sellers, and sellers and payment channels only need to be connected to the service platform once to be reused by global users or global buyers. This will undoubtedly greatly improve the user experience and effectively promote the development of the business.

[0134] As described above, according to an embodiment of another aspect, there is also provided a computer-readable storage medium, on which a computer program is stored. When the computer program is executed in a computer, the computer is made to execute the method described in combination with Figure 4 or Figure 5 as described.

[0135] According to an embodiment of another aspect, there is also provided a computing device, including a memory and a processor. An executable code is stored in the memory. When the processor executes the executable code, the method described in combination with Figure 4 or Figure 5 as described is implemented.

[0136] Those skilled in the art should be able to realize that in one or more of the above examples, the functions described in the multiple embodiments disclosed in this specification can be implemented by hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium.

[0137] The specific embodiments described above further elaborate on the objectives, technical solutions, and beneficial effects of the multiple embodiments disclosed in this specification. It should be understood that the above description is only the specific embodiments of the multiple embodiments disclosed in this specification and is not used to limit the protection scope of the multiple embodiments disclosed in this specification. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the multiple embodiments disclosed in this specification shall be included within the protection scope of the multiple embodiments disclosed in this specification.

Claims

1. A service processing method, the execution entity of the method being a service platform, the service platform being provided with a plurality of regional sites corresponding to a plurality of service areas, each of the regional sites including a corresponding seller service site and a buyer service site; the method includes: Determining that a first service needs to be processed currently; In the case where it is determined that the first service is a buyer or seller service obtained by splitting a cross-domain service, routing the first service to the corresponding buyer or seller service site according to the service area to which the first service belongs, so that this service site processes the first service and locally stores the service data generated by the processing.

2. The method according to claim 1, wherein In the case where it is determined that the first service is the buyer service, routing the first service to the corresponding buyer service site according to the service area to which the first service belongs, so that this service site processes the first service, including: In the case where it is determined that the processing of the first service needs to interface with a first buyer, determining the first buyer service site corresponding to the first service area to which the first buyer belongs; wherein, the first buyer corresponds to a first global user identifier and has a first regional user identifier in the first service area, which is determined based on a plurality of regional user identifiers associated with the first global user identifier; Routing the first service to the first buyer service site, so that the first buyer service site interfaces with the first buyer based on the first regional user identifier and processes the first service.

3. The method according to claim 2, wherein The first service is a buyer payment service; the determining that a first service needs to be processed currently includes: In response to a payment request initiated by a first buyer for a first order, determining that the buyer payment service needs to be processed currently, the goods in the first order being provided by a first seller, and the payment request including a selected payment channel; Wherein, in the case where it is determined that the processing of the first service needs to interface with a first buyer, determining the first buyer service site corresponding to the first service area to which the first buyer belongs includes: Based on a plurality of buyer services that need to interface with buyers set in advance, determining that the buyer payment service is included in the plurality of buyer services; Determining the first buyer service site corresponding to the first service area to which the first buyer belongs; wherein, the registered location of the payment institution corresponding to the payment channel is located in the first service area; Wherein, routing the first service to the first buyer service site, so that the first buyer service site interfaces with the first buyer based on the first regional user identifier and processes the first service, and locally stores the service data generated by processing the first service, includes: Routing the buyer payment service to the first buyer service site, so that the first buyer service site interfaces with the payment channel and interfaces with the first seller based on the first regional user identifier, processes the buyer payment service, and locally stores the service data generated by processing the buyer payment service.

4. The method according to claim 3, wherein, Before receiving a payment request initiated by a first buyer for a first order, the method further includes: In response to the successful login of the first buyer, determine the first global user identifier corresponding to the first buyer; In response to receiving an order creation request initiated by the first buyer based on the commodity, create the first order.

5. The method according to claim 4, wherein Determining the first global user identifier corresponding to the first buyer includes: Obtain the username of the first buyer; Perform a hash operation on the username to obtain the first global user identifier; alternatively, query the first global user identifier based on a pre-established mapping relationship between the username and the global user identifier.

6. The method according to claim 4, wherein After creating the first order and before receiving a payment request initiated by the first buyer for the first order, the method further includes: Obtain the location element information of the first buyer; Based on the location element information, determine the service area where the first buyer is currently located as the first service area; Based on the several regional user identifiers corresponding to several service areas, determine the first regional user identifier of the first buyer in the first service area; Obtain several alternative payment channels for the first buyer to select, and the registered places of the payment institutions corresponding to the several alternative payment channels are all located in the first service area.

7. The method according to claim 6, wherein Determining the first regional user identifier of the first buyer in the first service area based on the several regional user identifiers corresponding to several service areas includes: When there is no user identifier corresponding to the first service area among the several regional user identifiers, create a new user identifier as the first regional user identifier; Include the first regional user identifier in the several regional user identifiers.

8. The method according to claim 3, wherein Determine the first buyer business site corresponding to the first service area to which the first buyer belongs, including: Determine the registered place corresponding to the payment channel and use the service area where it is located as the first service area; Determine the first buyer business site corresponding to the first service area.

9. The method according to claim 3, wherein Before receiving a payment request initiated by the first buyer for the first order, the method further includes: Query, from the multiple regional sites, multiple historical orders associated with the several regional user identifiers; Based on the purchased commodities included in the multiple historical orders, recommend commodities to the first buyer.

10. The method according to claim 1, wherein In the case where it is determined that the first service is the seller's service, route the first service to the corresponding seller business site according to the service area to which the first service belongs, so that this business site processes the first service, including: In the case where it is determined that the processing of the first service needs to be docked with the first seller, determine the second seller business site corresponding to the second service area to which the first seller belongs; wherein, the registered place of the first seller is located in the second service area; Route the first service to the second seller business site so that the second seller business site processes the first service by docking with the first seller.

11. The method according to claim 10, wherein, The first service is a seller delivery service; determining that the first service needs to be processed currently includes: In response to receiving a payment success message for a first order, it is determined that the seller delivery service needs to be processed currently, and the first order includes goods provided by the first seller.

12. The method according to claim 10 or 11, wherein, When it is determined that the processing of the first service needs to interface with the first seller, determining the second seller service site corresponding to the second service area to which the first seller belongs includes: Based on multiple seller services that need to interface with sellers preset, determining that the seller delivery service is included in the multiple seller services; Determining the registration location of the first seller and using the service area where it is located as the second service area, thereby determining the second seller service site corresponding to the second service area.

13. The method according to claim 11, wherein, After routing the first service to the second seller service site, the method further includes: Routing the order settlement service corresponding to the first seller to the second seller service site, so that the second seller service site processes the order settlement service by interfacing with the second seller and locally stores the service data generated by processing the order settlement service at the site.

14. A service processing device, the device is integrated in a service platform, the service platform is provided with multiple area sites corresponding to multiple service areas, and each area site includes a corresponding seller service site and a buyer service site; the device includes: A service determination unit configured to determine that the first service needs to be processed currently; A service site determination unit configured to, when it is determined that the first service is a buyer or seller service obtained by splitting a cross-domain service, route the first service to the corresponding buyer or seller service site according to the service area to which the first service belongs, so that this service site processes the first service and locally stores the service data generated by the processing.

15. A computer-readable storage medium having a computer program stored thereon, wherein, When the computer program is executed in a computer, the computer is made to execute the method according to any one of claims 1-13.

16. A computing device, comprising a memory and a processor, wherein, An executable code is stored in the memory, and when the processor executes the executable code, the method according to any one of claims 1-13 is implemented.

Images