CN114841784A

CN114841784A - Service providing method, device, equipment and storage medium based on shared locker

Info

Publication number: CN114841784A
Application number: CN202210746140.8A
Authority: CN
Inventors: 马凯; 常文静; 曾永兰; 王建行; 江洋
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2022-06-29
Filing date: 2022-06-29
Publication date: 2022-08-02

Abstract

The application discloses a service providing method, device, equipment and storage medium based on a shared locker, which are applied to the field of shared lockers. The method comprises the following steps: sending a commodity page of the first sharing locker to a user client, wherein the commodity page comprises at least one commodity sold through the first sharing locker, and the at least one commodity comprises the first commodity; receiving a purchase request of a user client for purchasing a first commodity; generating a purchase order of a first commodity by taking the first shared storage cabinet as a distribution address; sending a purchase order to a merchant client providing the first item, the purchase order being used to instruct the first item to be distributed to the first shared locker. The method realizes the online commodity ordering service based on the shared storage cabinet.

Description

Service providing method, device, equipment and storage medium based on shared locker

Technical Field

The present application relates to the field of shared lockers, and in particular, to a service providing method, device, equipment and storage medium based on a shared locker.

Background

The takeout service is a local life service in which goods purchased by a user are delivered to a place designated by the user by a delivery person.

In the related art, the take-away application presents nearby take-away merchants, in which a list of items is provided, to the user based on the user's location. The user may select one of the takeaway merchants, shop for the goods and edit the delivery address to generate an order. The server sends the order to the take-away merchant, and the take-away merchant arranges the delivery personnel to deliver the commodity to the delivery address specified by the user.

Disclosure of Invention

The embodiment of the application provides a service providing method, a service providing device, service providing equipment and a storage medium based on a shared locker, and realizes online commodity ordering service based on the shared locker. The technical scheme is as follows.

According to an aspect of the present application, there is provided a service providing method based on a shared locker, the method being performed by a server, the method comprising:

sending an item page of a first shared locker to a user client, wherein the item page comprises at least one item sold through the first shared locker, and the at least one item comprises a first item;

receiving a purchase request of the user client for purchasing the first commodity;

generating a purchase order of the first commodity by taking the first shared locker as a distribution address;

sending the purchase order to a merchant client providing the first commodity, wherein the purchase order is used for indicating the first commodity to be distributed to the first shared locker.

According to another aspect of the present application, there is provided a service providing method based on a shared locker, the method being performed by a user client, the method comprising:

receiving an item page sent by a server and associated with a first shared locker, wherein the item page comprises at least one item sold through the first shared locker, and the at least one item comprises a first item;

in response to an operation of purchasing the first commodity, sending a purchase request for purchasing the first commodity to the server;

displaying a purchase order for purchasing the first commodity by taking the first shared locker as a distribution address.

According to another aspect of the present application, there is provided a service providing apparatus based on a shared locker, the apparatus including:

the system comprises a first sending module, a second sending module and a third sending module, wherein the first sending module is used for sending commodity pages of a first sharing locker to a user client, the commodity pages comprise at least one commodity sold through the first sharing locker, and the at least one commodity comprises a first commodity;

the first receiving module is used for receiving a purchase request of the user client for purchasing the first commodity;

the generation module is used for generating a purchase order of the first commodity by taking the first shared storage cabinet as a distribution address;

the first sending module is configured to send the purchase order to a merchant client that provides the first article, where the purchase order is used to instruct to distribute the first article to the first shared locker.

the second receiving module is used for receiving a commodity page which is sent by the server and is associated with the first sharing locker, wherein the commodity page comprises at least one commodity sold through the first sharing locker, and the at least one commodity comprises a first commodity;

the second sending module is used for responding to the operation of purchasing the first commodity and sending a purchase request for purchasing the first commodity to the server;

and the display module is used for displaying a purchase order for purchasing the first commodity by taking the first shared storage cabinet as a distribution address.

According to another aspect of the present application, there is provided a computer device comprising: a processor and a memory, the memory having stored therein at least one instruction, at least one program, set of codes, or set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the shared locker-based service providing method as described above.

According to another aspect of the present application, there is provided a computer-readable storage medium having stored therein at least one instruction, at least one program, set of codes, or set of instructions, which is loaded and executed by a processor to implement the shared locker-based service providing method as described above.

In another aspect, embodiments of the present application provide a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the shared locker-based service providing method provided in the above-mentioned alternative implementation manner.

The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects.

The shared locker is used as a carrier of commodity ordering service, commodities are sold through the shared locker, commodity ordering is carried out through the shared locker, a distribution address of the ordering is automatically bound to be the shared locker, and commodity distribution is achieved through the shared locker. In addition, different commodities can be configured to be sold by aiming at the shared lockers at different positions, so that the types of the commodities sold by the shared lockers are matched with the types of surrounding users, and the users can purchase the commodities more conveniently through the shared lockers.

According to the method, commodities sold by each shared locker are stored in a server, the server sends the commodities sold by the shared lockers to a user client side for displaying according to needs, the user client side sends a purchase request to the server in response to user operation, the server generates a purchase order based on the purchase request and the issued shared lockers, and the issued shared lockers are used as distribution addresses of the purchase order. After the purchase order is generated, the purchase order is sent to the merchant client, and the merchant is instructed to distribute the commodities to the issued shared storage cabinet. After the distribution is successful, the server sends the pickup code of the shared storage cabinet to the user client, so that the user can take out the commodity from the shared storage cabinet according to the pickup code.

Compared with the method in the related art, the method provided by the embodiment of the application simplifies the overall flow of the commodity ordering service, the server does not need to match nearby commodities for the user in real time based on user positioning, only the commodities sold by each shared storage cabinet need to be read, and the load of the server in the commodity display stage is reduced; the distribution address of the purchase order placed by the shared storage cabinet is directly bound with the shared storage cabinet placed by the shared storage cabinet, so that the user client does not need to receive the operation of editing the distribution address when placing the order, the ordering process is simplified, the man-machine interaction efficiency is improved, and the purchase order of the commodity ordering service is quickly generated.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a block diagram of an implementation environment provided by an exemplary embodiment of the present application;

FIG. 2 is a flowchart of a shared locker based service providing method according to an exemplary embodiment of the present application;

FIG. 3 is a schematic diagram of a goods page of a service providing method based on a shared locker according to an exemplary embodiment of the present application;

FIG. 4 is a schematic diagram of a service providing method based on a shared locker according to an exemplary embodiment of the present application;

FIG. 5 is a flowchart of a shared locker based service provisioning method according to another exemplary embodiment of the present application;

FIG. 6 is a flowchart of a method for clicking on an item page entry to an item page according to an exemplary embodiment of the present application;

FIG. 7 is a schematic diagram of obtaining location authorization for a shared locker based service providing method according to an exemplary embodiment of the present application;

FIG. 8 is a flow chart illustrating a server decision for a shared locker based service provisioning method according to an exemplary embodiment of the present application;

FIG. 9 is a schematic diagram of a pickup interface of a shared locker based service providing method according to an exemplary embodiment of the present application;

FIG. 10 is a schematic diagram of a shared locker switching method for a shared locker-based service providing method according to an exemplary embodiment of the present application;

FIG. 11 is a flowchart of a method for scanning a first shared locker graphical code into a merchandise page according to an exemplary embodiment of the present application;

FIG. 12 is a flow chart illustrating a server decision for a shared locker based service provisioning method according to another exemplary embodiment of the present application;

FIG. 13 is a schematic diagram of a pickup interface of a shared locker based service providing method according to another exemplary embodiment of the present application;

FIG. 14 is a flowchart of a method for scanning a second shared locker graphical code into a merchandise page, as provided by an exemplary embodiment of the present application;

FIG. 15 is a flowchart of a method for updating a merchandise page of a first shared locker, according to an exemplary embodiment of the present application;

FIG. 16 is a flowchart of a method for entering a merchandise page on a first shared locker as provided by an exemplary embodiment of the present application;

FIG. 17 is a flowchart of a method for pushing a merchandise page to a user client according to an exemplary embodiment of the present application;

FIG. 18 is a flowchart of a method for anonymously ordering items through shared lockers according to an exemplary embodiment of the present application;

FIG. 19 is a schematic diagram of a shared locker based service provider according to an exemplary embodiment of the present application;

FIG. 20 is a schematic diagram of a shared locker based service provider according to another exemplary embodiment of the present application;

fig. 21 is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present application, it is to be noted that, unless otherwise explicitly specified or limited, the terms "connected" and "connected" are to be interpreted broadly, e.g., as being fixed or detachable or integrally connected; can be mechanically or electrically connected; may be directly connected or indirectly connected through an intermediate. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art.

FIG. 1 illustrates a schematic diagram of a shared locker system provided by an exemplary embodiment of the present application. The shared locker system 100 comprises: shared locker 110, user device 120, server 130, merchant device 140.

The shared locker 110 comprises one or more lockers 112 that may be used to store. Alternatively, the shared locker 110 may have a graphic code on the cabinet of the shared locker 110, and the user may scan the graphic code into the pickup page of the shared locker 110. Optionally, the shared locker 110 also comprises a screen 111 available for human interaction. A graphic code for the user to scan the pick-up, a numeric keypad for the user to input the pick-up code, and other controls for human-computer interaction may be displayed on the screen 111. Optionally, the shared locker 110 is installed or operated with a user client for providing goods ordering services. Optionally, the user client is further configured to provide a locker opening and pickup service for sharing the locker. When the shared locker 110 runs the user client, a user interface of the user client, such as a goods page or pickup page, is displayed on the screen of the shared locker 110. The background services of the user clients are provided by the server 130.

The user device 120 is installed or operated with a user client for providing a goods ordering service. Optionally, the user client is further configured to provide a locker opening and pickup service for sharing the locker. The user client may be an application or an applet. When the user device 120 runs the user client, a user interface of the user client, such as a goods page or pickup page, is displayed on the screen of the user device 120. The background services of the user clients are provided by the server 130.

The user client may be implemented in the form of an applet. An applet is a program that relies on a host program to operate. The host program provides a basic running environment for the small program to run, and background services of the host program and the small program are generally provided by different servers. Background services such as hosting programs are provided by the hosting server. The host program may be any one of an instant messenger program, a micro blogging program, a voice call program, a conference program, a web community program, a payment program, a shopping program, a friend-making program, a marriage program, a game program, an online education program, or other social programs.

The device types of the user equipment 120 include: at least one of a smart phone, a smart television, a smart car, a wearable device, a tablet computer, an electronic book reader, an MP3 (Moving Picture Experts Group Audio Layer III, motion video Experts Group 3) player, an MP4 (Moving Picture Experts Group 4) player, a laptop portable computer, and a desktop computer.

Only one user device is shown in fig. 1, but there are multiple other user devices 120 that may access the server 130 in different embodiments. Optionally, there are one or more user devices 120 as terminals corresponding to the developer, a development and editing platform of the user client is installed on the user device 120, the developer can edit and update the user client on the user device 120, and transmit the updated application installation package to the server 130 through a wired or wireless network; the user device 120 may download the pickup application installation package from the server 130 to effect an update to the user client.

The user client is used for displaying the commodity page, receiving the purchase operation of the user on the commodity page and sending a purchase request to the server so as to facilitate the server to generate a purchase order of the commodity ordering service. Optionally, the user client is further configured to send a locker opening request to the server, and the server sends a locker opening instruction to the shared locker to open a designated locker door of the shared locker, so as to implement user pickup.

The merchant device 140 is installed or operated with a merchant client for managing goods ordering services provided by a merchant. The merchant client may be an application or an applet. When the merchant device 140 operates the merchant client, a user interface of the merchant client, such as a goods editing page or an order page, is displayed on the screen of the merchant device 140. The background services of the merchant clients described above are provided by server 130.

The device types of merchant device 140 include: at least one of a smartphone, a smart television, a smart car, a wearable device, a tablet, an e-book reader, an MP3 player, an MP4 player, a laptop portable computer, and a desktop computer.

Only one merchant device is shown in fig. 1, but there are a plurality of other merchant devices 140 that may access the server 130 in different embodiments. Optionally, there are one or more merchant devices 140 corresponding to the developer, a development and editing platform of the merchant client is installed on the merchant device 140, the developer may edit and update the merchant client on the merchant device 140, and transmit the updated application installation package to the server 130 through a wired or wireless network; merchant device 140 may download the pickup application installation package from server 130 to enable updates to the merchant client.

The merchant client and the user client are two clients which are respectively developed by the same application program aiming at users with different identities. Such as merchant clients and user clients of a shopping application. The application program may be at least one of a takeout program, a local service program, a commodity ordering program, a shopping program, and a delivery program. The merchant client and the user client provide background services by the same server.

The server 130 is a server that provides background services for the shared locker 110, the user device 120, and the merchant device 140. The server 130 includes at least one of a server, a plurality of servers, a cloud computing platform, and a virtualization center. The server 130 is connected to the shared locker 110, the user device 120, and the merchant device 140, respectively, via a wireless or wired network. The server 130 is configured to receive a pickup request sent by the user device 120, and send a pickup instruction to the shared locker 110 based on the pickup request, so that the shared locker 110 opens a specified cabinet door based on the pickup instruction. The server 130 is further configured to send a goods page to the user device 120 and/or the shared locker 110, and receive a goods purchase request sent by the user device 120 and/or the shared locker 110, so as to implement selling local distribution services based on the shared locker. Illustratively, the server stores and maintains therein at least one of: the system comprises a commodity list of each shared locker, user account information of each user, merchant account information of each merchant and information of each shared locker.

In an illustrative example, the server 130 includes a processor, a locker database, and a user-oriented Input/Output Interface (I/O Interface). Wherein, the processor is used for loading the instruction stored in the server 130 and processing the data in the locker database; the locker database is used for storing storage indication information associated with the shared locker, such as locker identification, goods order identification stored by the locker, user account number and the like; the user-oriented I/O interface is used to exchange data with the shared locker 110 and the user device 120 via a wireless or wired network.

With reference to the foregoing description of the implementation environment, a method for providing a service based on a shared locker according to an embodiment of the present application is described, and the implementation subjects of the method are illustrated as a server, a shared locker, or a user device shown in fig. 1.

Fig. 2 is a flowchart illustrating a method for providing a service based on a shared locker, which is performed by a server, which may be a server in the shared locker system shown in fig. 1, according to an exemplary embodiment of the present application. The method comprises the following steps.

Step 210: and sending an article page of the first shared locker to the user client, wherein the article page comprises at least one article sold through the first shared locker, and the at least one article comprises the first article.

The user client runs on user equipment or a shared storage cabinet. The user client is used for providing commodity ordering service. The user client can display the goods sold by the shared storage cabinet, place orders to purchase the goods in response to the purchase operation, display the distribution progress of the orders, display pickup codes after the orders are distributed to the shared storage cabinet, provide after-sales services of the orders, communicate with merchants or distribution personnel on line and the like.

Optionally, the user client is further configured to provide a cabinet opening and pickup service for the shared locker, the user client may send a cabinet opening request to the server, where the cabinet opening request includes a pickup code, the server sends a cabinet opening instruction to the shared locker after verifying the pickup code, and the shared locker opens the corresponding cabinet door in response to the cabinet opening instruction.

Optionally, the goods page may further include a pickup control of the shared locker in addition to the goods sold by the first shared locker, where the pickup control is configured to send a request for opening the locker to the server in response to a pickup operation of the user. In an optional implementation manner, the user client is a pickup client of the shared locker, and on the basis of the original function of the pickup client of the shared locker, the commodities sold by the shared locker are additionally displayed, so that the user can browse the commodities sold by the shared locker during pickup, and then order purchase of the heart instrument commodities is facilitated. Therefore, the goods page of the first shared locker can be further displayed as a pickup page on the user client, the pickup page includes a pickup control and a goods display area, and at least one goods sold by the first shared locker is displayed in the goods display area. As shown in fig. 3, a pickup control 301 and a commodity list 302 are displayed on the user interface of the user client, where the commodity list includes at least one commodity sold by the first shared locker.

In the embodiment of the application, the shared locker is divided into two types of goods selling support service and goods selling non-support service. The shared locker supporting goods selling service has a goods page, and the goods page comprises at least one goods sold by the shared locker. Wherein the at least one item is provided by the same merchant, or the at least one item is provided by a different merchant. The shared storage cabinet is equivalent to a commodity display way, preset commodities are displayed to a user through the shared storage cabinet, and differentiated commodity recommendation is achieved for a single place. For example, different merchandise may be sold for different shared lockers (location, type, locker size). For example, respective commodities are respectively set for shared lockers at different positions of factories, communities, office buildings and the like. Or different commodities are set for different kinds of shared lockers. For example, the respective saleable commodities are arranged on different shared storage cabinets with the functions of automatic sterilization, freezing, heating and safety. For example, medicines can be sold for a shared storage cabinet with an automatic sterilizing function, fresh foods can be sold for a shared storage cabinet with a freezing function, catering can be sold for a shared storage cabinet with a heating function, and valuables can be sold for a shared storage cabinet with a safe function.

The shared locker supporting the commodity selling service stores at least one commodity sold by the shared locker in the server. The goods sold by the shared storage cabinet are maintained and updated by background workers, namely, the goods sold by the shared storage cabinet are manually set or automatically set by an algorithm and are not obtained by matching nearby merchants in real time based on the position.

The shared storage cabinet is used as a selling supermarket for delaying goods taking, maintenance personnel of the shared storage cabinet are responsible for putting commodities on shelves and putting commodities off shelves, after a user places an order on the shared storage cabinet, the server sends the order to a merchant, the merchant distributes the commodities to the shared storage cabinet, and the server sends pickup information to the user to prompt the user to get the commodities from the shared storage cabinet.

In another optional implementation, the shared locker may also serve as an intermediate merchant, at least one commodity of at least one merchant is shelved on the shared locker, and the user may purchase different commodities of different merchants at the intermediate merchant of the shared locker. For example, as shown in FIG. 4, merchandise A of merchant 1 and merchandise D of merchant 2 are sold in the first shared locker, and the user may purchase merchandise A and merchandise D next time in the first shared locker. That is, the user client displays an order as an order, the order includes two commodities of two merchants, and after receiving the order of the first shared locker, the server places an order for commodity a to merchant 1, respectively, so that the commodity a is distributed to the first shared locker; ordering the commodity D from the merchant 2, and distributing the commodity D to the first shared storage cabinet. In this way, the user can quickly place an order to purchase the commodities of multiple merchants. In addition, the shared locker may also provide its own preference rules, such as a full-discount rule or a discount rule, as an intermediate merchant.

Optionally, the server stores at least one commodity sold by the first shared locker, all commodities that can be sold by the first shared locker are called candidate commodities, and the commodity page of the first shared locker sent by the server includes at least one candidate commodity. That is, the server may send different merchandise pages corresponding to the first shared locker to the user client according to a preset rule. For example, the server may send different commodity pages corresponding to the first shared locker to the user client according to various information such as user purchasing habits, date of the day, current time, weather conditions, and the like. For example, when the user purchases afternoon tea every afternoon, the server may select afternoon tea commodities from the candidate commodities sold by the first shared locker, generate an afternoon tea commodity page, and send the afternoon tea commodity page sold by the first shared locker to the user client.

Of course, the server may also store at least one commodity list sold by the first shared locker, where each commodity list includes at least one commodity. The commodity page sent by the server to the user client comprises at least one commodity list. For example, the server may sort the candidate items sold by the first shared locker from multiple dimensions into multiple item lists, such as a lunch list, a dinner list, an afternoon tea list, a holiday list, a rainy list, and so on. The server sends at least one commodity list to the user client according to the requirement.

The goods sold by the shared locker can also be set by the maintenance personnel according to the request of the merchant, for example, the merchant near the shared locker can apply for selling some goods through the shared locker, and the maintenance personnel can respond to the request of the merchant according to the requirement and put the goods on shelf. In this way, the merchant can realize the goods sale in a fixed-point and oriented way, and not provide the distribution service for all distribution places in one area. For example, a private canteen can directionally provide working meals to a shared storage cabinet in an office building, and after a user places an order, the private canteen can distribute all the working meals scheduled by the office building to the shared storage cabinet at one time, so that the distribution cost is reduced for a merchant, and the batch receiving and distribution are realized.

Alternatively, the goods sold in the shared locker are goods that can be distributed to the shared locker through a local distribution service (takeout distribution). Alternatively, the local delivery service refers to a delivery service in which a delivery distance is within twenty kilometers and goods (goods) are delivered from one place to another by a single delivery person. That is, the goods sold in the shared locker are not in the shared locker when the user places an order, but are distributed to the shared locker after the user places an order, and the user takes the goods from the shared locker after the distribution of the goods is completed.

In an alternative implementation, the items sold by the shared locker are items offered by merchants in the vicinity of the shared locker. In the embodiments of the present application, the vicinity means that a distance between two locations is smaller than a distance threshold, or that the two locations are connected to one administrative area (an autonomous region, a direct prefecture city, a special administrative region, a prefecture city, a region, an autonomous state, a union, a district, a county, a street, a town, a county, or the like) or two administrative areas. That is, the maintenance personnel of the shared locker screens the merchants and the goods from the merchants located near the shared locker, and puts the goods on the shelf in the shared locker, so that the shared locker sells the goods.

Illustratively, the commodity page comprises at least one commodity information of commodity, total quantity of the commodity, commodity price, commodity picture, commodity name, commodity description, commodity allowance, purchase control, merchant name, commodity sales volume, commodity goodness of comment, selection control, group-piecing progress and preferential activity.

Optionally, the first shared locker is an expected delivery address of the user client determined by the server. That is, in a case where the first shared locker is an expected delivery address of the user client, the goods page of the first shared locker is sent to the user client.

Step 220: and receiving a purchase request of a user client for purchasing a first commodity.

The purchase request includes: the identification of the first commodity, the identification of the first shared locker, the purchase quantity, the timestamp, the user account number, the identification of the merchant providing the first commodity, and the contact information are one of the few.

The purchase request is sent to the server by the user client when receiving the commodity purchasing operation and submitting an order based on the purchased commodity. For example, when a user purchases an item in the item page of the first shared locker, the item purchased under the item page is delivered to the first shared locker by default without editing the delivery address, and the delivery address is not changeable.

Illustratively, the purchase request is sent by the user client after receiving an operation of purchasing a first commodity on a commodity page of the first shared locker. That is, the purchase request indicates that the path of purchasing the goods is through the first shared locker, so that the server sets the delivery address of the order as the first shared locker after confirming that the purchase path is the first shared locker.

In this embodiment, only the first product is taken as an example. The first item may refer to one or more items sold by the first shared locker. When the first item includes a plurality of items, the plurality of items are provided by one merchant or by a plurality of merchants.

Step 230: and generating a purchase order of the first commodity by taking the first shared storage cabinet as a distribution address.

After receiving the purchase request, the server generates a purchase order of the first commodity by using the first shared locker as a distribution address under the condition that the ordering route of the purchase request is a commodity page of the first shared locker. For example, the order placement path field in the shopping request is the identifier of the first shared locker, and the server generates the purchase order by using the first shared locker as the distribution address.

Or, in response to receiving a purchase operation on the goods page of the first shared locker, the user client sends a purchase request to the server by using the first shared locker as a delivery address, and at this time, the purchase request includes a delivery address field as the first shared locker.

In the method provided by the embodiment of the application, the goods purchased through the first shared locker are assigned to be distributed to the first shared locker, and the distribution address cannot be changed (cannot be distributed to other shared lockers or cannot be edited by other users). If the user needs to distribute the commodities to other shared lockers, the commodity pages of other shared lockers can be opened, and the commodities are ordered from the commodity pages of other shared lockers to be purchased.

Illustratively, after the server generates the purchase order of the first commodity, the server sends the purchase order to the user client, so that the user client confirms the order information and makes payment, and in response to successful payment, the purchase order is validated, and the server proceeds to step 240.

Illustratively, the purchase order includes at least one of the following information: the contact information, the user account number, the order placing time, the payment amount, the first commodity, the commodity quantity, the merchant providing the first commodity, the estimated delivery time/the specified delivery time and the distribution address are the first shared storage cabinet.

For example, when the first article includes a plurality of articles provided by a plurality of merchants respectively, the purchase order includes a user-side purchase order and a merchant-side purchase order, the user-side purchase order displays all the articles in one order, and the user can confirm article information in one order and make payment. And in response to successful payment, the server generates merchant side purchase orders of all merchants for all the merchants respectively based on the user side purchase orders, and sends the merchant side purchase orders to all the merchant clients, so that the merchants distribute the commodities to the first shared storage cabinet according to the orders.

In another optional implementation manner, if the first shared locker provides the commodities in the multiple merchants, when a user places an order to purchase the commodities, one order can only purchase the commodities in one merchant, for example, after the user selects a first commodity in a commodity page, the user enters a commodity page of the first merchant providing the first commodity, the commodity page displays the commodities sold by the first merchant in the first shared locker, and the user can select the commodities provided by the first merchant in the commodity page and place the order to purchase, at this time, the purchase order only includes the commodities sold in the first merchant. If the user wants to purchase the commodities of other merchants, the user needs to open the commodity pages of the other merchants through the commodity page of the first shared locker so as to purchase the commodities provided by the other merchants. The purchase request generated by this method may still be bound to the first shared locker, for example, the purchase request indicates that the ordering route is the merchandise page of the first shared locker, or the purchase request indicates that the delivery address is the first shared locker.

Step 240: sending a purchase order to a merchant client providing the first item, the purchase order being used to instruct the first item to be distributed to the first shared locker.

After the purchase order payment is successful, the server sends the purchase order to the merchant client that provides the first item. For example, if the first item is provided by the first merchant, the first item is sent to the merchant client logged in the merchant account of the first merchant, so that the first merchant prepares an item based on the purchase order, and distributes the first item to the first shared locker. And after the order is finished, the server settles the order to the merchant client.

For example, the first merchant distributes the first commodity to the first shared locker according to the purchase order, and the server sends the pickup code to the user client or the contact information in response to the distribution of the first commodity to the first shared locker, so that the user opens the door of the first shared locker according to the pickup code to pick up the first commodity.

In summary, the method provided in this embodiment provides a service providing method based on shared lockers, and the shared lockers are used to sell takeout commodities, each shared locker has a commodity list, and the commodity lists of the shared lockers can be maintained and updated through a background, so that the takeout commodities can be recommended differently for users at different locations. For example, the commodities sold by the shared locker near the office area are set as the commodities of the work meal type, so that office staff can purchase work meals conveniently. Or, the commodities sold by the shared storage cabinet at the periphery of the school are set to be gift commodities such as flowers and the like in the teacher section, so that users at the periphery of the school can conveniently purchase festival gifts.

Fig. 5 is a flowchart illustrating a service providing method based on a shared locker, which is performed by a user client, where the user client may run on a user device or the shared locker as shown in fig. 1. The method comprises the following steps.

Step 410: and receiving an article page sent by the server and associated with the first shared locker, wherein the article page comprises at least one article sold through the first shared locker, and the at least one article comprises the first article.

The user client receives and displays a commodity page of the first shared locker, wherein the commodity page comprises at least one commodity sold by the first shared locker. For example, the user client displays a goods page as shown in FIG. 3.

Step 420: in response to an operation to purchase the first item, a purchase request to purchase the first item is sent to the server.

The operation of purchasing the first commodity includes: and selecting the first commodity and submitting an order.

For example, if a user account is logged in the user client, the user client defaults to send a purchase request of the first commodity to the server by using a mobile phone number bound to the user account as contact information. Alternatively, the purchase request does not include contact information, and the user may enter the contact information after generating the purchase order.

For example, the operation to purchase the first item may be an operation to click the immediate preemptive control 303 in FIG. 3.

Step 430: and displaying a purchase order for purchasing the first commodity by taking the first shared locker as a distribution address.

The server generates a purchase order based on a purchase request sent by the user client, and the user client receives and displays the purchase order sent by the server so that the user can confirm order information. At this point, the user may change the contact information in the purchase order or cancel the order. But the user may not change the delivery address.

And after the user confirms that the order information is correct, order payment is carried out, the user client sends a payment message to the server, and the server responds to the successful payment and confirms that the order takes effect. The server sends the validated purchase order to the user client.

Illustratively, the embodiment of the present application provides five scenarios in which a server sends a commodity page to a user client:

1. a user clicks an entrance of a commodity page;

2. scanning a graphic code of a first shared storage cabinet by a user;

3. the user scans the graphic code of the second shared locker, and the second shared locker does not support commodity selling service;

4. a user enters a commodity page on the first shared storage cabinet, or the server updates the commodity page to the first shared storage cabinet;

5. the server actively pushes the commodity page to the user.

For the above five scenarios, the following five embodiments are provided.

Scene 1: the user clicks on the entry of the goods page.

FIG. 6 is a flowchart illustrating a method for providing a service based on a shared locker, which is performed by a user client and a server, where the user client runs on a user device as shown in FIG. 1, and the server may be a server in the shared locker system as shown in FIG. 1. The method comprises the following steps.

Step 501: and the user client receives the operation of clicking the commodity page entrance.

The item page entries may be arbitrary. For example, the user may open a user client/applet into the goods page. That is, the goods page is the home page of the user's client/applet. As another example, the user may click on a merchandise page entry in the user's client/applet. That is, the goods page may also be an intermediate page of the user client/applet.

Step 502: the user client sends a page acquisition request to the server.

The user client sends a page acquisition request to the server in response to the operation of clicking the commodity page entrance, wherein the commodity page entrance is used for opening a commodity page, and the page acquisition request is used for requesting to acquire a commodity page of a shared locker supporting commodity sale service. The page acquisition request comprises at least one of a user account and positioning information. The user account and location information is used to assist the server in determining the intended delivery address of the user client.

(1) The page acquisition request includes a user account.

In response to receiving an operation of clicking a commodity page entry, a user client sends a page acquisition request to a server, wherein the page acquisition request comprises a user account logged in the user client, and the user account is used for assisting the server to determine that a first shared locker is an expected delivery address of the user client.

The method comprises the steps that a server receives a page acquisition request sent by a user client, wherein the page acquisition request is used for requesting to acquire a commodity page and comprises a user account logged in the user client; acquiring a historical delivery address of a user account; determining a first shared locker supporting goods sale service in a historical distribution address; reading at least one commodity sold through the first shared locker; and sending a commodity page of the first shared locker to the user client, wherein the commodity page comprises at least one commodity.

Illustratively, the first shared locker is a shared locker supporting goods sale service which is placed last time in the historical delivery address of the user account.

Illustratively, a user account is logged in on a user client, and the user account is logged in on the user client before clicking a commodity page entry, or the user performs a user account login operation after clicking the commodity page entry, and sends a page acquisition request to the server after the user successfully logs in.

(2) The page acquisition request includes positioning information.

In response to receiving the operation of clicking the commodity page entrance, the user client sends a page acquisition request to the server, wherein the page acquisition request comprises positioning information of the user client, and the positioning information is used for assisting the server to determine that the first shared locker is an expected distribution address of the user client.

The method comprises the steps that a server receives a page obtaining request sent by a user client, wherein the page obtaining request is used for requesting to obtain a commodity page and comprises positioning information of the user client; determining a first shared storage cabinet which meets the distance condition with the positioning information and supports commodity selling service; reading at least one commodity sold through the first shared locker; and sending a commodity page of the first shared locker to the user client, wherein the commodity page comprises at least one commodity.

Illustratively, the first shared locker is the shared locker supporting the goods sale service closest to the user client.

Illustratively, the user client has the right of obtaining the positioning of the user equipment, and the user client obtains the positioning information of the user equipment when clicking the commodity page entry, or the user firstly obtains positioning authorization after clicking the commodity page entry, and sends a page obtaining request to the server after the authorization is successful. For example, if the location authorization is not obtained or the location authorization is not received successfully, the user client may also send a page obtaining request to the server, but the page obtaining request does not include the location information.

For example, the user client is a pickup program of the shared locker, and as shown in (1) in fig. 7, in response to receiving an operation of clicking a commodity page entry, an identity selection page is displayed; in response to receiving the operation of selecting the customer identity, an item page and a location authorization acquisition popup as shown in (2) in fig. 7 are displayed. And responding to the obtained positioning authorization, and sending a page acquisition request to the server by the user client, wherein the page acquisition request comprises positioning information.

For example, the page obtaining request may further include both the user account and the positioning information, and in this case, the server may preferentially determine the expected delivery address based on the historical delivery address or preferentially determine the expected delivery address according to the positioning information. Or selecting a shared locker which supports commodity selling service and is closest to the positioning information from the historical distribution address.

Step 503: the server determines the expected delivery address as a first shared locker.

For example, after receiving a page acquisition request of a commodity page, the server first selects an expected delivery address for the user client. Since the commodity page is only used for displaying commodities sold by the shared locker supporting the commodity sale service, the server needs to determine the shared locker possibly selected by the user first, and then the commodity page of the shared locker can be provided for the user client.

The user who expects the delivery address to select for the server may want to order the shared locker.

In an alternative implementation, the decision logic for the server to select a shared locker as the intended delivery address is shown in FIG. 8, which includes the following steps.

Step 601: the server firstly judges whether the page acquisition request contains positioning information, if so, the step 602 is executed; otherwise, go to step 603.

Step 602: and under the condition that the page acquisition request contains the positioning information, the server judges whether the city where the positioning information is located is a trial city. Illustratively, only the pilot city is provided with a shared locker supporting commodity sale. If so, go to step 604, otherwise go to step 605.

Step 603: and the server reads the user account in the page acquisition request, acquires the historical delivery address of the user account, and judges whether the delivery address belonging to the trial city exists in the historical delivery address. If not, go to step 605, otherwise go to step 610.

Step 604: and under the condition that the current test point city is determined to be located based on the positioning information, reading the user account in the page acquisition request, and acquiring the historical delivery address based on the user account. And judging whether a shared locker supporting commodity sale exists in the historical distribution address. If yes, go to step 606; otherwise, step 607 is executed.

Step 605: and in the case that the current position is determined not to be in the test point city based on the positioning information, displaying a conventional pickup page. Or, under the condition that the historical delivery address does not cover the test point city, displaying a conventional pickup page. The items sold by the shared locker are not shown on the conventional pickup page. Illustratively, the conventional pickup page is a pickup page of the shared locker, and the pickup page includes a pickup control used for opening a cabinet door of the shared locker.

Step 606: and when the first shared locker supporting goods sale service exists in the historical distribution address, determining the first shared locker as an expected distribution address, and acquiring goods sold by the first shared locker for display.

Step 607: under the condition that the shared locker supporting the commodity sale service does not exist in the historical distribution address, acquiring the shared locker supporting the commodity sale service in the nearby range according to the positioning information, and if the shared locker supporting the commodity sale service exists in the nearby range, executing step 608; otherwise, go to step 609. The nearby range may be a circular range centered on the positioning information and having a preset distance as a radius.

Step 608: and under the condition that a first shared locker supporting goods sale service exists in the nearby range, determining the first shared locker as an expected distribution address, and acquiring goods sold by the first shared locker for displaying.

Step 609: in the case where there is no shared locker supporting goods sale service in the vicinity, no participatable shared locker is displayed, and a blank (no goods) goods page is displayed. Or, in the case that the historical distribution address does not contain the shared locker supporting the goods sale service, displaying that no participatable shared locker exists, and displaying a blank goods page.

Step 610: and judging whether the historical distribution address comprises a shared storage cabinet supporting commodity sale service or not under the condition that the page acquisition request does not contain positioning information and the historical distribution address comprises a distribution address covering the trial city. If so, step 611 is performed. If not, go to step 609.

Step 611: when a first shared locker supporting goods selling service exists in the historical delivery address, the first shared locker is determined as the delivery address, and goods for sale are displayed based on the first shared locker.

Step 504: the server reads at least one item sold by the first shared locker.

After the expected delivery address is determined, the goods sold by the first sharing storage cabinet are read.

For example, the goods sold by the first shared locker can be automatically adjusted in real time according to preset rules. Or, the goods sold by the first sharing locker can be divided into a plurality of goods lists, and the server can read at least one goods list from the plurality of goods lists according to preset conditions.

For example, the first shared locker may sell different items at different time periods; the merchandise sold by the first shared locker during the morning hours may include at least one of: reserving commodities for lunch on the same day and reserving commodities for dinner on the same day; the goods sold by the first shared locker in the midday period comprise at least one of the following goods: the current evening meal booking commodity, the tomorrow breakfast booking commodity and the next working day breakfast booking commodity; the items sold by the first shared locker during the evening hours include at least one of: a tomorrow breakfast scheduled commodity, a tomorrow lunch scheduled commodity, a next workday breakfast scheduled commodity, and a next workday lunch scheduled commodity.

Therefore, the shared storage cabinet can recommend lunch or dinner to the user in the morning and recommend dinner or breakfast in the tomorrow. In an alternative scenario, when the user purchases breakfast and opens the pickup page to the first shared locker code for taking breakfast, lunch or dinner sold by the first shared locker can be displayed on the pickup page, and the user can order the pickup page for taking lunch or dinner.

For another example, the first shared locker may sell different merchandise on different dates; the items sold by the first shared locker on the event date comprise at least one event item; the goods sold by the first shared locker in holidays comprise at least one holiday goods. In an alternative scenario, the commodities sold by the first shared locker can be controlled to be automatically updated to various types of rice dumplings sold by various merchants at the morning, so that the user can book the rice dumplings at the afternoon through the first shared locker.

In addition, after the server reads at least one commodity sold by the first shared storage cabinet, the sequencing of the commodities can be automatically adjusted based on the user information.

In summary, the server may read the goods sold by the first shared locker according to the information such as the current time, the current date, and the weather today, and obtain the goods list.

Step 505: and the server sends a commodity page of the first shared locker to the user client.

The server sends a goods page of the first shared locker to the user client, where the goods page includes the goods list of the first shared locker read by the server in step 504.

Step 506: and the user client displays a commodity page of the first shared locker.

Illustratively, the user client receives and displays a merchandise page of the first shared locker. For example, the goods page may include at least one of a pickup control and a position switching control in addition to the goods sold by the first shared locker.

The pickup control is used for opening the cabinet door of the shared locker. The pickup control can be specially used for opening the cabinet door of the first shared storage cabinet, the pickup control can also be used for jumping to a pickup page, and a user can open the cabinet door of any shared storage cabinet on the pickup page.

For example, as shown in (1) of FIG. 9, a merchandise page is provided on which a pick control 304 and a listing 305 of the items sold by the first shared locker are displayed. In response to receiving the triggering operation on the pickup control, displaying a code scanning pickup page as shown in (2) in fig. 9, wherein a user can click the code scanning removal control on the code scanning pickup page to display the code scanning page, and the user scans the graphic code on the shared locker to access the pickup page of the shared locker (as shown in (3) in fig. 9), and the user can open the designated cabinet door of the shared locker by one key on the pickup page or open the designated cabinet door of the shared locker by inputting the pickup code.

And the position switching control is used for switching and displaying the commodity pages of other shared lockers. And in response to receiving the operation of selecting the third shared locker through the position switching control, sending a page acquisition request of a commodity page of the third shared locker to the server, reading and returning the commodity page of the third shared locker by the server, and switching and displaying the commodity page as the commodity page of the third shared locker by the user client.

Since the expected delivery address (the first shared locker) which is possibly selected by the user is predicted by the server when entering the goods page for the first time, when the user wants to purchase goods sold by other shared lockers, the user can switch to the shared locker which the user wants to buy by clicking the position switching control to browse and purchase the goods.

For example, as shown in (1) in fig. 10, a position switching control 306 is displayed on the goods page. In response to receiving a trigger operation on the position toggle control 306, displaying a shared locker selection page as shown in (2) of fig. 10, in which at least one candidate shared locker and its selection control 307 are provided; and in response to receiving the triggering operation on the selection control 307, switching the distribution address to the selected shared locker, jumping back to the commodity page, and displaying the commodity page corresponding to the switched shared locker. For example, the shared locker may be displayed on a page as the number of the shared locker, e.g., shared locker 1, shared locker 2; the shared locker may also be displayed on the page as the location of the shared locker, e.g., first technology park a, first technology park B.

In summary, according to the method provided by this embodiment, when a user wants to enter a vending page (goods page) of the shared locker, the server determines an expected delivery address according to the purchase history of the user account or the location of the user client. In addition, the server can read different commodities sold by the shared storage cabinet according to various factors such as time, date and the like, and the commodities are close to the requirements of users, so that the users can conveniently browse and shop the commodities.

Scene 2: the user scans the graphic code of the first shared locker.

FIG. 11 is a flowchart illustrating a method for providing a service based on a shared locker, which is performed by a user client and a server, where the user client runs on a user device as shown in FIG. 1, and the server may be a server in the shared locker system as shown in FIG. 1. The method comprises the following steps.

Step 701: the user client scans the graphic code of the first shared locker.

Illustratively, the body of the shared storage cabinet is printed with respective graphic codes. Or the screen of the shared locker displays respective graphic codes of the shared locker.

The graphic code is used for opening a pickup page/commodity page (the two pages can be the same page) of the shared locker.

For example, the user may open the code scan function of the host program, scan the graphic code of the first shared locker, and open the applet on the pages of the merchandise.

Step 702: the user client sends a page acquisition request to the server.

In response to scanning the graphical code of the first shared locker, the user client sends a page fetch request to the server, the page fetch request including an identification of the first shared locker.

The page acquisition request sent to the server by scanning the graphic code of the first shared locker contains the identifier of the first shared locker.

Because the user client is located near the first shared locker (it can be guaranteed that the user can only successfully scan the code near the first shared locker through other technical means such as bluetooth) when the user can scan the graphic code of the first shared locker, and the server stores the position of the first shared locker, the page acquisition request does not need to report the positioning information of the user client. Of course, in this scenario, the page acquisition request may also include the location information of the user client.

Step 703: the server determines the expected delivery address as a first shared locker.

The server receives a page acquisition request sent by a user client, wherein the page acquisition request is used for requesting to acquire a commodity page, and the page acquisition request comprises an identifier of a first shared locker obtained by scanning a graphic code of the first shared locker.

When the server receives a page acquisition request containing the identifier of the first shared locker, whether the first shared locker supports commodity sale service is judged, if so, the first shared locker is directly used as an expected distribution address to read commodities, and if not, the shared locker which supports the commodity sale service nearby can be acquired based on the first shared locker. In this embodiment, the first shared locker supporting the merchandise sales service will be described as an example.

In an alternative implementation, the logic for the server to select the shared locker as the expected delivery address in the code scanning scenario is shown in fig. 12, which includes the following steps.

Step 801: and the server reads the identifier of the (first) shared locker in the page acquisition request, reads the position of the shared locker and judges whether the city where the shared locker is located is a test point city. If yes, go to step 802; otherwise, step 803 is executed.

Step 802: under the condition that the position of the shared storage cabinet is a trial city, judging whether the shared storage cabinet supports commodity selling service; if so, go to step 804, otherwise go to step 805.

Step 803: and under the condition that the position of the shared locker is not the trial city, displaying the conventional shared locker pickup page. For example, as shown in (1) in fig. 13, the user scans the two-dimensional code of the shared locker on the code scanning interface, if the shared locker does not support the goods sale service, the conventional pickup page shown in (2) in fig. 13 is displayed, the user inputs the pickup code on the pickup page, the user jumps to the open page shown in (3) in fig. 13, and the user clicks the open control on the open page to open the designated cabinet door.

Step 804: and in the case that the shared locker supports goods selling service, taking the shared locker as an expected distribution address, and enabling the user client to display a goods page of the shared locker.

Step 805: when the shared locker does not support the goods sale service, whether other shared lockers supporting the goods sale service exist nearby is judged based on the position of the shared locker. If yes, go to step 806; otherwise, step 807 is performed.

Step 806: and under the condition that other shared lockers supporting goods selling service exist nearby, determining the other shared lockers as expected distribution addresses, and enabling the user client to display goods pages of the other shared lockers.

Step 807: and under the condition that other shared lockers supporting commodity selling service do not exist nearby, displaying prompt information that the current position is temporarily not opened, and displaying a blank commodity page. For example, a commodity page shown in (1) in fig. 10 is displayed, a position switching control is displayed on the commodity page, and a user can switch to other shared lockers supporting commodity selling services by clicking the position switching control.

Step 504: the server reads at least one item sold by the first shared locker.

Steps 504 to 506 can be explained with reference to the embodiment shown in fig. 6.

In summary, according to the method provided by this embodiment, the user may also open the commodity page of the shared locker by directly scanning the two-dimensional code on the shared locker. When a user scans the two-dimensional code of the shared storage cabinet to take a commodity, the commodity sold by the shared storage cabinet is displayed on the commodity taking page, so that the user can continuously reserve other commodities while taking the commodity, and the user can conveniently and quickly shop. In addition, as the goods sold through the shared storage cabinet are bound to the shared storage cabinet, when a user cannot know the specific location of the current location, the user can find the nearby shared storage cabinet, order placement is carried out through the shared storage cabinet, and the user does not need to edit the distribution address, so that the purchase of local distribution service can be realized.

Scene 3: the user scans the graphical code of the second shared locker.

FIG. 14 is a flowchart illustrating a method for providing a service based on a shared locker, which is performed by a user client and a server, where the user client runs on a user device as shown in FIG. 1, and the server may be a server in the shared locker system as shown in FIG. 1. The method comprises the following steps.

Step 704: the user client scans the graphical code of the second shared locker.

Referring to the related description in the embodiment shown in fig. 11, the present embodiment provides an example in which a user scans a shared locker that does not support goods sale service. That is, the second shared locker does not support merchandise sales services.

Step 705: the user client sends a page acquisition request to the server.

In response to scanning the graphic code of the second shared locker, the user client sends a page acquisition request to the server, wherein the page acquisition request comprises an identifier of the second shared locker; the second shared locker does not support commodity sale service, and the first shared locker and the second shared locker meet a distance condition and support commodity sale service.

And the page acquisition request sent to the server by scanning the graphic code of the second shared locker comprises the identifier of the second shared locker.

Step 706: the server determines the expected delivery address as a first shared locker.

The server receives a page acquisition request sent by a user client, wherein the page acquisition request is used for requesting to acquire a commodity page, and the page acquisition request comprises an identifier of a second shared locker obtained by scanning a graphic code of the second shared locker; reading the position of the second shared locker under the condition that the second shared locker does not support goods sale service; and determining a first shared locker which meets the distance condition with the position of the second shared locker and supports goods selling service.

When the server receives a page acquisition request containing the identifier of the second shared locker, whether the second shared locker supports commodity sale service is judged, if so, the second shared locker is directly used as an expected distribution address to read commodities, and if not, the shared locker which supports the commodity sale service nearby can be acquired based on the second shared locker.

For example, the logic for determining that the server selects the shared locker as the expected delivery address in the code scanning scenario is described with reference to fig. 12.

Step 504: the server reads at least one item sold by the first shared locker.

Step 506: and the user client displays the commodity page of the first shared locker.

In summary, in the method provided in this embodiment, the user may also open the commodity page of the shared locker by directly scanning the two-dimensional code on the shared locker. When a user scans the two-dimensional code of the shared storage cabinet to take a commodity, the commodity sold by the shared storage cabinet is displayed on the commodity taking page, so that the user can continuously reserve other commodities while taking the commodity, and the user can conveniently and quickly shop. When the shared locker currently scanned by the user does not support the commodity sale service, the shared locker which supports the commodity sale service nearby can be automatically recommended to the user, so that the user can browse and select and purchase the special products sold by other shared lockers.

Scene 4: the user enters the commodity page on the first shared storage cabinet, or the server updates the commodity page to the first shared storage cabinet.

1. In one implementation, the first shared locker may store goods for sale therein, and when the goods for sale need to be updated, the server sends a goods update message to the first shared locker to update the goods for sale stored in the first shared locker. At this time, if the user clicks and browses the goods sold by the first shared locker, the first shared locker can directly read the locally stored saleable goods and display the goods page of the first shared locker.

Fig. 15 is a flowchart illustrating a shared locker-based service providing method according to an exemplary embodiment of the present application, where the method is performed by a user client and a server, the user client runs on a first shared locker as shown in fig. 1, and the server may be a server in the shared locker system as shown in fig. 1. The method comprises the following steps.

Step 707: and the server sends a commodity updating message to the first shared locker, wherein the commodity updating message comprises a commodity page of the first shared locker.

Illustratively, the first shared locker has stored therein a pages of merchandise. When the maintainer updates the goods sold in the first shared locker, the server sends a goods updating message to the first shared locker, wherein the goods updating message is used for indicating the first shared locker to update a local stored goods page. And the first shared storage cabinet receives the commodity updating message and updates the locally stored saleable commodities according to the commodity updating message.

Step 708: the first shared locker receives an operation of clicking an item page entry.

And when the first sharing storage cabinet receives the operation of triggering the commodity page entrance by the user, reading and displaying the locally stored commodity page.

In an alternative implementation, the first shared locker may also display the goods page by default, in which case step 708 may be skipped; and the first shared locker responds to the received commodity updating message sent by the server and updates and displays the commodity page of the first shared locker.

Step 506: the first shared locker displays a goods page of the first shared locker.

Step 506 may refer to the relevant explanation in the embodiment shown in fig. 6.

2. In another implementation manner, the first shared locker responds to the operation of clicking the goods page inlet, and the goods page of the first shared locker is obtained from the server in real time.

Fig. 16 is a flowchart illustrating a shared locker-based service providing method according to an exemplary embodiment of the present application, where the method is performed by a user client and a server, the user client runs on a first shared locker as shown in fig. 1, and the server may be a server in the shared locker system as shown in fig. 1. The method comprises the following steps.

For example, a merchandise page entry may be displayed on the screen of the first shared locker, and the user may enter the merchandise page by clicking on the merchandise page entry.

Step 709: the first shared locker sends a page acquisition request to the server.

In response to receiving an operation of clicking a commodity page entrance, the first shared locker sends a page acquisition request to the server, wherein the page acquisition request comprises an identifier of the first shared locker.

Step 710: the server determines the expected delivery address as a first shared locker.

When the server receives a page fetch request containing an identification of the first shared locker, the first shared locker is taken as an expected delivery address to read the goods.

Step 504: the server reads at least one item sold by the first shared locker.

Step 505: and the server sends the commodity page of the first shared locker to the first shared locker.

In the scenario provided by this embodiment, the first shared locker may further have a face recognition function, and then the user may directly distribute the service on and off the first shared locker without passing through other user devices. For example, when the user forgets to bring a mobile phone, the user can find a nearby shared locker supporting commodity sale service, browse commodities sold by the user, place an order, and pay through face recognition. After the estimated delivery time, the user can open the cabinet door where the commodity is located through face recognition, and the commodity is taken out, so that the local distribution service is more intelligent and convenient.

For example, the first shared locker displays the goods page of the first shared locker in response to receiving an operation of clicking the goods page entry. And responding to the operation of selecting the second commodity, and displaying an order confirmation page of the second commodity, wherein the order confirmation page comprises the predicted delivery time and a face payment control. Responding to the received triggering operation on the face payment control, and displaying a face recognition interface; and after the face recognition is successful, completing order payment. The server sends an order to the merchant client providing the second commodity, so that the merchant distributes the second commodity to the first shared locker. And then, the first shared storage cabinet responds to the received face recognition piece taking operation, a face recognition interface is displayed, and the cabinet door where the second commodity is located is opened in response to the successful face recognition, so that the user can take out the second commodity.

In summary, in the method provided by this embodiment, the user can directly browse the goods sold by the user on the shared locker and place the order. When the shared storage cabinet supports the face recognition function, ordering, distribution and pickup processes of local distribution service can be carried out without a mobile phone, so that the local distribution service is more intelligent and convenient.

Scene 5: the server actively pushes the commodity page to the user.

FIG. 17 is a flowchart illustrating a method for providing a service based on a shared locker, which is performed by a user client and a server, where the user client runs on a user device as shown in FIG. 1, and the server may be a server in the shared locker system as shown in FIG. 1. The method comprises the following steps.

Step 711: and the server sends the push message to the user client.

For example, the server may also periodically obtain a group of potential users of each shared locker, and send a push message of a goods page of the shared locker to the group of potential users, so that the users can enter the goods page to view goods sold by the shared locker.

The server reads at least one user account including a first shared locker in the historical distribution address; reading at least one commodity sold through the first shared locker; and sending push messages to user clients corresponding to the at least one user account respectively, wherein the push messages comprise commodity pages of the first shared storage cabinet, and the commodity pages comprise at least one commodity.

Step 712: and the user client responds to the operation of viewing the push message and displays the commodity page of the first shared locker.

The user client receives a push message sent by the server, wherein the push message comprises a commodity page associated with a first shared locker, and the first shared locker is a historical distribution address of the user client.

When a user account on the user client purchases goods in the first shared locker once, the user client may receive a push message of a goods page of the first shared locker sent by the server, and when the user clicks the push message, the user client displays the goods page of the first shared locker.

In summary, in the method provided in this embodiment, the server may also actively push the commodity page to the historical ordering user of each shared locker, so that the user enters the commodity page of each shared locker to browse and purchase commodities, and commodity pushing is directionally implemented.

In an alternative implementation, the items sold by the first shared locker comprise at least one group purchase item.

The commodity page also comprises the group-combining progress of the group-buying commodity; the grouping progress is the grouping progress of the group purchase commodities in the first shared storage cabinet; or the group-piecing progress is the progress of a merchant providing the group-buying goods receiving the group-buying order in the first shared locker; wherein the grouping schedule comprises at least one of: order quantity progress, commodity quantity progress, and order amount progress.

The embodiment of the application provides two display modes of the grouping progress.

Mode 1: and displaying respective grouping progress for each commodity.

Namely, each group purchase commodity sold by the first sharing storage cabinet corresponds to a respective group-piecing progress, when the group-piecing progress meets the group-piecing success condition, the group-piecing is successful, the server generates a group-piecing order, and sends the group-piecing order to the client of the merchant providing the group purchase commodity, so that the merchant distributes the group purchase commodity to the first sharing storage cabinet.

Mode 2: and displaying respective grouping progress for each merchant.

Namely, each group-buying merchant selling the commodities in the first shared locker corresponds to a respective group-piecing progress, when the group-piecing progress meets the group-piecing success condition, the group-piecing is successful, the server generates a group-piecing order, and sends the group-piecing order to the merchant client of the group-buying merchant, so that the group-buying merchant distributes the group-buying commodities to the first shared locker.

For example, the grouping success condition may be set from multiple dimensions, for example, the total number of orders exceeds a threshold, or the total number of commodities exceeds a threshold, or the total amount of orders exceeds a threshold.

In an alternative implementation manner, a part of merchants are provided with pickup fees, and the commodity list of the first shared locker can be edited by the user client. When the user wants to purchase the goods in the fourth merchant but the delivery fee of the fourth merchant is less than the delivery fee of the fourth merchant, the user client responds to the operation of editing the goods list of the first shared locker, adds the goods provided by the fourth merchant/the fourth merchant as the group-buying merchant/group-buying goods into the goods list of the first shared locker, so that other users can see the group-buying when browsing the goods list of the first shared locker, and a plurality of users can conveniently collect the order to reach the delivery fee of the fourth merchant.

In an optional implementation manner, at least one merchant may be further displayed on the merchandise page of the first shared locker in the above embodiment, and the merchandise page of one merchant is displayed in response to an operation of clicking the merchant.

In an optional embodiment, the first shared locker is used for purchasing commodities, user information can be protected, the user information is completely hidden from the merchant, and the user information safety is guaranteed.

Fig. 18 is a flowchart illustrating a shared locker-based service providing method according to an exemplary embodiment of the present application, which is performed by a user client, a server and a merchant client, wherein the user client runs on a first shared locker as shown in fig. 1, and the server may be a server in the shared locker system as shown in fig. 1. The merchant client runs on a merchant device as shown in fig. 1. The method comprises the following steps.

Step 901: the first shared locker receives an operation to anonymously purchase a first item.

For example, an anonymous purchase control may be provided on the goods page of the first shared locker, and in response to receiving a trigger operation on the anonymous purchase control corresponding to the first goods, a purchase request for anonymously purchasing the first goods may be sent to the server.

Alternatively, an anonymous purchase control may be provided on a display page of a purchase order for the first item, and in response to receiving an operation to check the anonymous purchase control, a purchase request to anonymously purchase the first item is sent to the server, and the purchase order is updated to be displayed as the first purchase order for anonymous purchase.

Step 902: the first shared locker sends a purchase request to the server for anonymously purchasing the first item.

Illustratively, the purchase request includes pickup information. The pickup information may be contact information or face recognition information.

The contact information is used for sending the pickup code, so that the user can pick up the pickup from the first shared storage cabinet based on the pickup code.

The face recognition information is used as a pick-up code to open the cabinet door to which the first commodity is distributed.

Step 903: the server generates a first purchase order to purchase a first item.

The server receives a purchase request sent by the first shared locker for anonymously purchasing the first commodity, wherein the purchase request comprises contact information. And generating a first purchase order of the first commodity by taking the first shared locker as a distribution address, wherein the first purchase order comprises contact person information.

The server generates a first purchase order containing pickup information after receiving the anonymous purchase request. The first purchase order is not provided to the merchant client but is stored by the server. The server generates a second purchase order, which only includes the information related to the product and does not include the information related to the user. For example, the second purchase order does not include pickup information, user account information for the order placing user, and the like. The second purchase order is provided to the merchant client, so that the merchant distributes the first goods to the first shared locker according to the second purchase order. The first purchase order and the second purchase order are stored in association in a server.

Step 904: the server sends a first purchase order to the first shared locker to complete an order payment process.

After the server generates the first purchase order, the first purchase order is sent to the first shared storage cabinet, so that the user can confirm order information and pay.

Step 905: the server generates a second purchase order to purchase the first item.

The server generates a second purchase order of the first commodity by taking the first shared locker as a distribution address, wherein the second purchase order does not comprise contact information.

Wherein, the execution of step 904 and step 905 may not have a fixed sequence.

Step 906: the server sends a second purchase order to the merchant client.

The server sends a second purchase order to the merchant client that provides the first item.

When the first commodity is distributed to the first sharing storage cabinet, the server reads the contact person information in the first purchase order and sends the pick-up code to the contact person information, so that the user can pick up the first commodity from the first sharing storage cabinet based on the pick-up code.

In summary, in the method provided in this embodiment, the order information received by the merchant client completely does not include information related to the user, and the merchant cannot know who the order was placed, to whom the order is to be distributed, or cannot know the contact way of the placed person, thereby protecting the information security of the user in all directions.

The following are embodiments of the apparatus of the present application, and for details that are not described in detail in the embodiments of the apparatus, reference may be made to corresponding descriptions in the above method embodiments, and details are not described herein again.

Fig. 19 is a schematic structural diagram illustrating a service providing apparatus based on a shared locker according to an exemplary embodiment of the present application. The apparatus may be implemented as all or a part of a server by software, hardware or a combination of both, and includes:

a first sending module 1004, configured to send, to the user client, a merchandise page of the first shared locker, where the merchandise page includes at least one merchandise sold through the first shared locker, and the at least one merchandise includes the first merchandise;

a first receiving module 1001, configured to receive a purchase request for a user client to purchase a first commodity;

the generating module 1002 is configured to generate a purchase order of a first commodity by using a first shared locker as a distribution address;

a first sending module 1004 for sending a purchase order to a merchant client providing the first item, the purchase order for instructing the first item to be distributed to the first shared locker.

In an alternative embodiment, the first sending module 1004 is configured to send the goods page of the first shared locker to the user client if the first shared locker is the expected delivery address of the user client.

In an alternative embodiment, the apparatus further comprises:

a first receiving module 1001, configured to receive a page obtaining request sent by a user client, where the page obtaining request is used to request to obtain a commodity page, and the page obtaining request includes a user account logged in by the user client;

a reading module 1003, configured to obtain a historical delivery address of the user account;

a determining module 1005, configured to determine a first shared locker supporting goods sale service in a historical distribution address;

a reading module 1003 for reading at least one commodity sold through the first shared locker;

the first sending module 1004 is configured to send, to the user client, a goods page of the first shared locker, where the goods page includes at least one good.

In an alternative embodiment, the apparatus further comprises:

a first receiving module 1001, configured to receive a page obtaining request sent by a user client, where the page obtaining request is used to request to obtain a commodity page, and the page obtaining request includes location information of the user client;

a determining module 1005, configured to determine a first shared locker which satisfies a distance condition with the positioning information and supports a commodity sale service;

In an alternative embodiment, the apparatus further comprises:

a first receiving module 1001, configured to receive a page obtaining request sent by a user client, where the page obtaining request is used to request to obtain a commodity page, and the page obtaining request includes an identifier of a first shared locker obtained by scanning a graphic code of the first shared locker;

In an alternative embodiment, the apparatus further comprises:

a first receiving module 1001, configured to receive a page obtaining request sent by a user client, where the page obtaining request is used to request to obtain a commodity page, and the page obtaining request includes an identifier of a second shared locker obtained by scanning a graphic code of the second shared locker;

a reading module 1003, configured to read a location of the second shared locker when the second shared locker does not support a goods sale service;

a determining module 1005, configured to determine a first shared locker which satisfies a distance condition with a location of a second shared locker and supports a goods sale service;

In an alternative embodiment, the apparatus further comprises:

the reading module 1003 is configured to read at least one user account of the first shared locker included in the historical distribution address;

the first sending module 1004 is configured to send a push message to user clients corresponding to at least one user account, where the push message includes a commodity page of the first shared locker, and the commodity page includes at least one commodity.

In an alternative embodiment, the first shared locker may sell different items at different time periods;

the items sold by the first shared locker during the morning hours include at least one of: reserving commodities for lunch on the same day and reserving commodities for dinner on the same day;

the goods sold by the first shared locker in the midday period comprise at least one of the following goods: the commodity is reserved for dinner in the same day, the commodity is reserved for breakfast in the next weekday, and the commodity is reserved for breakfast in the next weekday;

the items sold by the first shared locker during the evening hours include at least one of: a tomorrow breakfast scheduled commodity, a tomorrow lunch scheduled commodity, a next workday breakfast scheduled commodity, and a next workday lunch scheduled commodity.

In an alternative embodiment, the first shared locker may sell different items on different dates;

the items sold by the first shared locker on the event date comprise at least one event item;

the goods sold by the first shared locker in holidays comprise at least one holiday goods.

In an alternative embodiment, the at least one item comprises a group purchase item; the commodity page also comprises a grouping progress; the grouping progress is the grouping progress of the group purchase commodities in the first shared storage cabinet; or the group-piecing progress is the progress of a merchant providing group-buying goods receiving a group-buying order in the first shared locker;

wherein the grouping schedule comprises at least one of: order quantity progress, commodity quantity progress, and order amount progress.

In an alternative embodiment, the user client runs on a first shared locker;

a first receiving module 1001, configured to receive a purchase request for anonymously purchasing a first commodity, where the purchase request includes contact information, and the request is sent by a first shared locker;

a generating module 1002, configured to generate a first purchase order of a first commodity by using a first shared locker as a distribution address, where the first purchase order includes contact information;

a generating module 1002, configured to generate a second purchase order for the first commodity by using the first shared locker as a distribution address, where the second purchase order does not include contact information;

a first sending module 1004 for sending the second purchase order to the merchant client providing the first item.

Fig. 20 is a schematic structural diagram illustrating a shared locker-based service providing apparatus according to an exemplary embodiment of the present application. The apparatus may be implemented as all or a portion of a user device or a first shared locker by software, hardware, or a combination of both, and includes:

a second receiving module 1102, configured to receive a commodity page sent by the server and associated with the first shared locker, where the commodity page includes at least one commodity sold through the first shared locker, and the at least one commodity includes the first commodity;

a second sending module 1101, configured to send, in response to an operation of purchasing a first product, a purchase request for purchasing the first product to the server;

the display module 1103 is configured to display a purchase order for purchasing a first commodity using the first shared locker as a distribution address.

In an alternative embodiment, the second sending module 1101 is configured to send, in response to receiving an operation of clicking a commodity page entry, a page obtaining request to the server, where the commodity page entry is used to open a commodity page, the page obtaining request includes a user account logged in on a user client, and the user account is used to assist the server in determining that the first shared locker is an expected delivery address of the user client.

In an alternative embodiment, the second sending module 1101 is configured to send, in response to receiving an operation of clicking a commodity page entry, a page obtaining request to the server, where the commodity page entry is used to open a commodity page, the page obtaining request includes location information of the user client, and the location information is used to assist the server in determining that the first shared locker is an expected delivery address of the user client.

In an alternative embodiment, the second sending module 1101 is configured to send a page obtaining request to the server in response to scanning the graphic code of the first shared locker, where the page obtaining request includes an identifier of the first shared locker.

In an alternative embodiment, the second sending module 1101 is configured to send, to the server, a page obtaining request in response to scanning a graphical code of the second shared locker, where the page obtaining request includes an identifier of the second shared locker;

the second shared locker does not support commodity sale service, and the first shared locker and the second shared locker meet a distance condition and support commodity sale service.

In an alternative embodiment, the apparatus is for implementing a first shared locker;

the second sending module 1101 is configured to send, in response to receiving an operation of clicking a commodity page entry, a page obtaining request to a server, where the commodity page entry is used to open a commodity page, and the page obtaining request includes an identifier of a first shared locker.

In an alternative embodiment, the second receiving module 1102 is configured to receive a push message sent by the server, where the push message includes an item page associated with a first shared locker, and the first shared locker is a historical delivery address of the user client.

the merchandise sold by the first shared locker during the morning hours may include at least one of: reserving commodities for lunch on the same day and reserving commodities for dinner on the same day;

the goods sold by the first shared locker in the midday period comprise at least one of the following goods: the current evening meal booking commodity, the tomorrow breakfast booking commodity and the next working day breakfast booking commodity;

the items sold by the first shared locker on the event date include: at least one movable item;

the commodities sold by the first shared locker in holidays comprise: at least one holiday commodity.

In an alternative embodiment, the at least one item comprises a group purchase item; the commodity page also comprises a grouping progress; the grouping progress is the grouping progress of the group purchase commodities in the first shared storage cabinet; or the group-piecing progress is the progress of a merchant providing the group-buying goods receiving the group-buying order in the first shared locker;

Referring to fig. 21, a block diagram of a computer device 1200 according to an exemplary embodiment of the present application is shown. The computer device may be a user device, a shared locker, or a merchant device.

Generally, computer device 1200 includes: a processor 1201 and a memory 1202.

The processor 1201 may include one or more processing cores, such as a 4-core processor, an 8-core processor, or the like. The processor 1201 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1201 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1201 may be integrated with a GPU (Graphics Processing Unit) that is responsible for rendering and drawing content that the display screen needs to display. In some embodiments, the processor 1201 may further include an AI (Artificial Intelligence) processor for processing a computing operation related to machine learning.

Memory 1202 may include one or more computer-readable storage media, which may be tangible and non-transitory. Memory 1202 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 1202 is used to store at least one instruction for execution by the processor 1201 to implement the shared locker based service providing methods provided herein.

In some embodiments, the computer device 1200 may further optionally include: a peripheral interface 1203 and at least one peripheral. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1204, touch display 1205, camera assembly 1206, audio circuitry 1207, positioning assembly 1208, and power supply 1209.

The peripheral interface 1203 may be used to connect at least one peripheral associated with I/O (Input/Output) to the processor 1201 and the memory 1202. In some embodiments, the processor 1201, memory 1202, and peripheral interface 1203 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1201, the memory 1202 and the peripheral device interface 1203 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 1204 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 1204 communicates with a communication network and other communication devices by electromagnetic signals. The radio frequency circuit 1204 converts an electric signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electric signal. Optionally, the radio frequency circuit 1204 comprises: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 1204 may communicate with other terminals through at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the rf circuit 1204 may further include NFC (Near Field Communication) related circuits, which are not limited in this application.

The Location component 1208 is used to locate a current geographic Location of the computer device 1200 for navigation or LBS (Location Based Service). The Positioning component 1208 can be a Positioning component based on the Global Positioning System (GPS) in the united states, the beidou System in china, or the galileo System in russia.

Those skilled in the art will appreciate that the configuration shown in FIG. 21 is not intended to be limiting of the computer device 1200 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

The present application further provides a terminal, including: the system comprises a processor and a memory, wherein at least one instruction, at least one program, a code set or an instruction set is stored in the memory, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to realize the shared locker-based service providing method provided by the method embodiments.

The present application further provides a computer device, comprising: the system comprises a processor and a memory, wherein at least one instruction, at least one program, a code set or an instruction set is stored in the storage medium, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to realize the shared locker-based service providing method provided by the method embodiments.

The present application further provides a computer-readable storage medium, in which at least one instruction, at least one program, a code set, or a set of instructions is stored, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by a processor to implement the shared locker-based service providing method provided by the above method embodiments.

The present application also provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the shared locker-based service providing method provided in the above-mentioned alternative implementation manner.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A service providing method based on a shared locker, wherein the method is executed by a server, and the method comprises:

2. The method of claim 1, wherein sending the goods page of the first shared locker to the user client comprises:

sending the goods page of the first shared locker to the user client if the first shared locker is an expected delivery address of the user client.

3. The method of claim 2, wherein the sending the goods page of the first shared locker to the user client if the first shared locker is an expected delivery address of the user client comprises:

receiving a page acquisition request sent by the user client, wherein the page acquisition request is used for requesting to acquire the commodity page and comprises a user account logged in on the user client;

acquiring a historical delivery address of the user account;

determining the first shared locker supporting goods sale service in the historical distribution address;

reading the at least one item sold through the first shared locker;

sending the goods page of the first shared locker to the user client, the goods page including the at least one good.

4. The method of claim 2, wherein the sending the goods page of the first shared locker to the user client if the first shared locker is an expected delivery address of the user client comprises:

receiving a page acquisition request sent by the user client, wherein the page acquisition request is used for requesting to acquire the commodity page and comprises positioning information of the user client;

determining the first shared locker which meets a distance condition with the positioning information and supports commodity selling service;

reading the at least one item sold through the first shared locker;

5. The method of claim 2, wherein the sending the goods page of the first shared locker to the user client if the first shared locker is an expected delivery address of the user client comprises:

receiving a page acquisition request sent by the user client, wherein the page acquisition request is used for requesting to acquire the commodity page, and the page acquisition request comprises an identifier of the first shared locker obtained by scanning the graphic code of the first shared locker;

reading the at least one item sold through the first shared locker;

6. The method of claim 2, wherein the sending the goods page of the first shared locker to the user client if the first shared locker is an expected delivery address of the user client comprises:

receiving a page acquisition request sent by the user client, wherein the page acquisition request is used for requesting to acquire the commodity page, and the page acquisition request comprises an identifier of a second shared locker obtained by scanning a graphic code of the second shared locker;

reading the position of the second shared locker under the condition that the second shared locker does not support goods sale service;

determining the first shared locker which meets a distance condition with the position of the second shared locker and supports the goods sale service;

reading the at least one item sold through the first shared locker;

7. The method of claim 2, wherein the sending the goods page of the first shared locker to the user client if the first shared locker is an expected delivery address of the user client comprises:

reading at least one user account in a historical distribution address, wherein the at least one user account comprises the first shared locker;

reading the at least one item sold through the first shared locker;

sending a push message to the user clients corresponding to the at least one user account, wherein the push message includes the commodity page of the first shared locker, and the commodity page includes the at least one commodity.

8. The method of any of claims 1 to 7, wherein the first shared locker sells different items of merchandise at different time periods;

the goods sold by the first shared locker in the morning hours include at least one of: reserving commodities for lunch on the same day and reserving commodities for dinner on the same day;

the merchandise sold by the first shared locker during the midday period may include at least one of: the current evening meal booking commodity, the next breakfast booking commodity in the tomorrow, and the like;

the items sold by the first shared locker during the evening hours include at least one of: the breakfast scheduled goods for tomorrow, the lunch scheduled goods for tomorrow, the breakfast scheduled goods for next working day, and the lunch scheduled goods for next working day.

9. The method of any of claims 1 to 7, wherein the first shared locker sells different items of merchandise on different dates;

the goods sold by the first shared locker in holidays comprise: at least one holiday commodity.

10. The method of any one of claims 1 to 7, wherein the at least one commodity comprises a group purchase commodity; the commodity page further comprises a group-piecing progress; the group-piecing progress is the progress of the group-buying goods in the first shared storage cabinet; or the group-piecing progress is the progress of a merchant providing the group purchase commodity receiving a group purchase order in the first shared locker;

11. The method of any one of claims 1 to 7, wherein the user client runs on the first shared locker;

the receiving a purchase request of the user client to purchase the first commodity comprises:

receiving the purchase request sent by the first shared locker for anonymously purchasing the first commodity, wherein the purchase request comprises contact information;

the generating a purchase order for the first commodity by using the first shared locker as a distribution address comprises:

generating a first purchase order for the first commodity by taking the first shared locker as a distribution address, wherein the first purchase order comprises the contact information;

generating a second purchase order for the first commodity with the first shared locker as a distribution address, the second purchase order not including the contact information;

the sending the purchase order to the merchant client that provides the first item includes:

sending the second purchase order to the merchant client that provided the first item.

12. A service providing method based on a shared locker, the method being performed by a user client, the method comprising:

receiving a commodity page sent by a server and associated with a first shared locker, wherein the commodity page comprises at least one commodity sold through the first shared locker, and the at least one commodity comprises a first commodity;

13. The method of claim 12, further comprising:

sending a page acquisition request to the server in response to receiving an operation of clicking a commodity page entry, wherein the commodity page entry is used for opening the commodity page, the page acquisition request comprises a user account logged in on the user client, and the user account is used for assisting the server in determining that the first shared locker is an expected delivery address of the user client.

14. The method of claim 12, further comprising:

sending a page acquisition request to the server in response to receiving an operation of clicking a commodity page entry, wherein the commodity page entry is used for opening the commodity page, the page acquisition request comprises positioning information of the user client, and the positioning information is used for assisting the server in determining that the first shared locker is an expected distribution address of the user client.

15. The method of claim 12, further comprising:

sending a page acquisition request to the server in response to scanning the graphic code of the first shared locker, the page acquisition request including an identification of the first shared locker.

16. The method of claim 12, further comprising:

sending a page acquisition request to the server in response to scanning a graphical code of a second shared locker, the page acquisition request comprising an identification of the second shared locker;

the second shared locker does not support commodity sale service, and the first shared locker and the second shared locker meet a distance condition and support the commodity sale service.

17. The method of claim 12, wherein the user client runs on the first shared locker; the method further comprises the following steps:

and responding to the operation of clicking a commodity page inlet, and sending a page acquisition request to the server, wherein the commodity page inlet is used for opening the commodity page, and the page acquisition request comprises the identifier of the first shared locker.

18. The method of claim 12, wherein receiving the goods page associated with the first shared locker sent by the server comprises:

receiving a push message sent by the server, wherein the push message comprises the commodity page associated with the first shared locker, and the first shared locker is a historical delivery address of the user client.

19. The method of any of claims 12 to 18, wherein the first shared locker sells different items of merchandise at different time periods;

the goods sold by the first shared locker in the midday period comprise at least one of the following goods: the current evening meal booking commodity, the next breakfast booking commodity in the tomorrow, and the like;

20. The method of any of claims 12 to 18, wherein the first shared locker sells different items of merchandise on different dates;

21. The method of any one of claims 12 to 18, wherein the at least one commodity comprises a group purchase commodity; the commodity page further comprises a group-piecing progress; the group-piecing progress is the progress of the group-buying goods in the first shared locker; or the group-piecing progress is the progress of a merchant providing the group purchase commodity receiving a group purchase order in the first shared locker;

22. A service providing apparatus based on a shared locker, the apparatus comprising:

the generating module is used for generating a purchase order of the first commodity by taking the first shared storage cabinet as a distribution address;

23. A service providing apparatus based on a shared locker, the apparatus comprising:

a second sending module, configured to send, to the server, a purchase request for purchasing the first commodity in response to an operation of purchasing the first commodity;

24. A computer device, wherein the computer comprises: a processor and a memory, the memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the shared locker based service providing method of any of claims 1 to 21.

25. A computer-readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the shared locker-based service providing method according to any of claims 1 to 21.