CN115640465A - Cross-region and cross-merchant resource sharing method and system - Google Patents
Cross-region and cross-merchant resource sharing method and system Download PDFInfo
- Publication number
- CN115640465A CN115640465A CN202211670517.2A CN202211670517A CN115640465A CN 115640465 A CN115640465 A CN 115640465A CN 202211670517 A CN202211670517 A CN 202211670517A CN 115640465 A CN115640465 A CN 115640465A
- Authority
- CN
- China
- Prior art keywords
- account
- merchant
- service
- target
- recommended
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a cross-region and cross-merchant resource sharing method and a cross-region and cross-merchant resource sharing system, which belong to the field of sharing service, wherein the method comprises the following steps: receiving a sharing service request sent by a target user account, wherein the sharing service request records a required service type and a current position of a user; identifying all membership cards owned by the target user account; identifying the affiliated merchant account of each member card as a target merchant account; identifying a related merchant account associated with each target merchant account as a target related merchant account; selecting a recommended merchant account from all the target merchant accounts and the target associated merchant accounts based on the type of the required service and the current position of the user; and feeding back the merchant information corresponding to the recommended merchant account to the target user account. The method and the device have the advantages that the utilization rate of member services of both the merchant and the user can be improved, and the effect of resource sharing is achieved.
Description
Technical Field
The invention relates to the field of sharing services, in particular to a cross-region and cross-merchant resource sharing method and system.
Background
With the improvement of living standard, service industries such as health care, nail art, home service and the like are developed at a high speed, and the number of storefronts of merchants is increasing continuously. Usually, consumers have the option of transacting membership cards at frequently visiting merchants, thereby reducing long-term consumption costs.
However, for consumers who frequently go on business and travel on business, the utilization rate of the membership cards handled by the consumers is low due to frequent lives in different regions, and in order to meet personal consumption demands, the consumers handle the membership cards in different merchants in different regions, so that a great amount of additional expenses and inconvenience in life are caused. For the merchant, the number of visits of the consumer who registers the member is not large for the above reasons, and therefore, a large amount of promotion is still required to continuously obtain new customers, which causes additional expenses.
Disclosure of Invention
In order to solve the above problems, the present application provides a cross-region and cross-merchant resource sharing method and system.
In a first aspect, the present application provides a cross-region and cross-merchant resource sharing method, which adopts the following technical solution:
a cross-region and cross-merchant resource sharing method is based on a platform server in a cross-region and cross-merchant resource sharing system, wherein a sharing platform is built in the platform server, and a merchant account and a user account are registered in the sharing platform, and the method comprises the following steps:
receiving a sharing service request sent by a target user account, wherein the sharing service request records a required service type and a current position of a user;
identifying all membership cards owned by the target user account;
identifying the affiliated merchant account of each member card as a target merchant account;
identifying a correlated merchant account correlated with each target merchant account as a target correlated merchant account;
selecting a recommended merchant account from all the target merchant accounts and the target associated merchant accounts based on the type of the required service and the current position of the user;
and feeding back merchant information corresponding to the recommended merchant account to the target user account.
Optionally, the sharing platform further registers a service staff account related to the merchant account;
after the selecting out of the recommended merchant account, the method further comprises:
identifying whether the shared service request carries a door-to-door service tag;
and when the identification result is yes, canceling the step of feeding back the merchant information corresponding to the recommended merchant account to the target user account, and executing the following processing:
selecting a recommended service personnel account from the service personnel accounts associated with all the recommended merchant accounts based on the current position of the user;
feeding back account information of all the recommended service personnel accounts to the target user account;
based on the received selection instruction, selecting a final service staff account from the recommended service staff accounts;
and sending a service notice to the final service staff account.
Optionally, the method further includes:
if the target membership card is identified in the sharing service request, the step of identifying all the membership cards owned by the target user account is cancelled, and the merchant account to which the target membership card belongs is taken as the target merchant account.
Optionally, the selecting a recommended service staff account from the service staff accounts associated with all the recommended merchant accounts based on the current location of the user includes:
identifying the positions of service personnel registered by all service personnel accounts associated with the recommended merchant account;
and sequentially comparing the positions of the service personnel with the current position of the user, and taking the service personnel account corresponding to the position of the service personnel with the distance difference smaller than a preset difference threshold value as a recommended service personnel account.
Optionally, the method further includes:
after receiving a personal location update request sent by a first service personnel account, updating the location of the service personnel registered by the first service personnel account.
Optionally, the sending of the service notification to the final service staff account specifically includes:
sending a prepayment receiving notice to the target user account;
and after receiving a payment confirmation notification fed back by the target user account, sending a service notification to the final service staff account.
Optionally, after the receiving of the payment confirmation notification fed back by the target user account, sending a service notification to the final service staff account, further includes:
after receiving a service completion notification fed back by the target user account, confirming a payment type based on the payment confirmation notification;
when the payment type is direct payment, allocating the prepayment to the final service staff account and the associated merchant account according to a preset first allocation rule;
when the payment type is membership card balance payment, identifying a target membership card selected by the target user account;
and distributing the prepayment to the merchant account number to which the target member card belongs, the final service staff account number and the merchant account number related to the final service staff account number according to a preset second distribution rule.
In a second aspect, the present application provides a cross-region and cross-merchant resource sharing system, which adopts the following technical solution:
a cross-region and cross-merchant resource sharing system comprises a platform server and a user side, wherein the platform server comprises:
the information receiving module is used for receiving a sharing service request sent by a target user account, and the sharing service request records a required service type and a current position of a user;
the user account identification module is used for identifying all membership cards owned by the target user account;
the target merchant account number specifying module is used for identifying the merchant account number of each member card as a target merchant account number;
the associated merchant account identification module is used for identifying the associated merchant account associated with each target merchant account as a target associated merchant account;
a recommended merchant account selecting module, configured to select a recommended merchant account from all the target merchant accounts and the target associated merchant accounts based on the demand service type and the current location of the user;
and the information sending module is used for feeding back the merchant information corresponding to the recommended merchant account to the target user account.
In a third aspect, the present application provides a server terminal, which adopts the following technical solution:
a server terminal comprising a memory and a processor, the memory having stored thereon a computer program that can be loaded by the processor and that executes the method according to the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium, which adopts the following technical solutions:
a computer readable storage medium comprising a computer program stored thereon which can be loaded by a processor and which performs the method according to the first aspect.
In summary, the present application includes at least one of the following beneficial technical effects:
1. through the establishment of the sharing platform, an entity merchant can register merchant accounts on line and synchronize member card information on line, and then the merchant can select other merchants in different areas and in different industry types to become associated merchants, so that the sharing of the member card and member resources is realized, the utilization rate of member services of both the merchant and a user (namely a consumer) is improved, and the resource sharing is realized.
Drawings
FIG. 1 is a schematic diagram of a resource sharing system for embodying cross-regional cross-business resource sharing in one embodiment of the present application;
FIG. 2 is a schematic flowchart illustrating a method for resource sharing across regions and businesses in an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram illustrating a method for cross-regional and cross-business resource sharing in another embodiment of the present application;
fig. 4 is a block diagram of a system for embodying a platform server in an embodiment of the present application.
Description of reference numerals: 41. an information receiving module; 42. a user account identification module; 43. a target merchant account number specifying module; 44. a correlated merchant account identification module; 45. a recommended merchant account selecting module; 46. and an information sending module.
Detailed Description
The technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, and do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present application. Furthermore, the terms "target," "second," "third," 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 "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; the connection can be mechanical connection or electrical connection; the two elements may be directly connected or indirectly connected through an intermediate medium, or may be communicated with each other inside the two elements, or may be wirelessly connected or wired connected. The specific meaning of the above terms in this application will be understood to be a specific case for those of ordinary skill in the art.
In addition, the technical features mentioned in the different embodiments of the present application described below may be combined with each other as long as they do not conflict with each other.
The embodiment of the application discloses a cross-region and cross-merchant resource sharing system, which refers to fig. 1 and comprises a platform server and a user side. A sharing platform is set up in the platform server, and a merchant account and a user account are registered in the sharing platform. The user side can be a mobile phone, a tablet computer, a computer and other devices, and different personnel can log in a merchant account or a user account through a customized APP installed in the user side, so that communication is established with the platform server, and interaction with the sharing platform is realized.
Based on the above system, an embodiment of the present application further discloses a cross-region and cross-merchant resource sharing method, and with reference to fig. 2, the method may specifically include the following steps:
s201: and receiving a sharing service request sent by a target user account, wherein the sharing service request records a required service type and the current position of a user.
The user account refers to an account registered by a consumer, and the target user account may be any one of all registered user accounts, specifically, a user account that has issued a request for sharing a service.
For example, a consumer may log in a target user account through a customized APP in a user terminal owned by the consumer, and send a shared service request to the platform server through an operation in an operation interface in the customized APP. The shared service request carries the type of the required service selected by the consumer and the current position of the user. The required service type can be health care, housekeeping service, nail art service and the like, the current position of the user can be manually input or selected by a consumer, and the current position can also be automatically determined through a self-contained positioning function in the user side, such as a GPS positioning function, a Beidou positioning function and the like.
S202: all membership cards owned by the target user account are identified.
For example, the platform server may identify a source account of the sharing service request, i.e., a target user account, and further identify all membership cards owned by the target user account.
S203: and identifying the affiliated merchant account of each member card as a target merchant account.
For example, the consumer a may transact the member card a offline at the merchant B, and then the merchant B may send a request to the platform server through the owned merchant account to mark the user account owned by the consumer a as the member account, and make the platform server issue the member card corresponding to the merchant account to the user account owned by the consumer a, where the merchant account of the merchant B is the account to which the member card belongs. The consumer a can also directly transact the membership card of the merchant B online by using the owned user account through the sharing platform, which is not described herein again.
For example, the platform server may further identify the affiliated merchant account of each membership card, and use the affiliated merchant account as the target merchant account.
S204: and identifying the associated merchant account number associated with each target merchant account number as the target associated merchant account number.
For example, the merchant may establish an association relationship between the owned merchant account and other merchant accounts based on the recommendation or personal selection of the sharing platform, so that the merchant accounts are associated with each other. After S203, the platform server may further identify a correlated merchant account of the target merchant account, and use the correlated merchant account as the target correlated merchant account.
S205: and selecting a recommended merchant account from all the target merchant accounts and the target associated merchant accounts based on the type of the required service and the current position of the user.
For example, the platform server may select a target merchant account and/or a target associated merchant account that meets the requirement from all the target merchant accounts and the target associated merchant accounts as the recommended merchant account based on the demand service type and the current location of the user identified from the shared service request.
S206: and feeding back the merchant information corresponding to the recommended merchant account to the target user account.
For example, the platform server may generate a recommendation list in which merchant information of each recommended merchant account is recorded, and feed back the recommendation list to the target user account, so that a consumer having the target user account may view and select the target user account through the user terminal.
Optionally, referring to fig. 3, in another embodiment, a service person account number associated with the merchant account number is also registered in the sharing platform. In this case, after S205 described above, the following may be further included:
s301: identifying whether the shared service request carries a portal service tag.
For example, before sending the shared service request, the consumer may select the portal service through a corresponding interface in the customized APP in the user side, so that the user side adds a portal service tag in a subsequent generated shared service request. The platform server can identify whether the received shared service request carries the door-to-door service tag. When the recognition result is no, continuing to execute the step S206; when the recognition result is yes, the execution of S206 is cancelled, and S302 is entered.
S302: and selecting the recommended service personnel account number from the service personnel account numbers associated with all the recommended merchant account numbers based on the current position of the user.
Further, in another embodiment, S302 may specifically include the following:
s3021: and identifying the positions of the service personnel registered by all the service personnel accounts associated with the recommended merchant account.
Illustratively, the service person position is registered in each service person account, and comprises the city, the area, the detailed address and the like of the service person. The platform server can respectively identify the positions of the service personnel registered by all the service personnel accounts associated with the recommended merchant account.
Further, in another embodiment, in order to facilitate the service personnel to update their own location and to facilitate the service personnel to find part-time during the travel or business trip, the method may further include the following steps:
and after receiving a personal position updating request sent by the first service personnel account, updating the position of the service personnel registered by the first service personnel account.
The first service person account may be any one of all service person accounts.
For example, after a service person to which the first service person account belongs reaches a new location different from a location of a registered service person, a personal location update request may be sent to the platform server through the carried user terminal, and after receiving the personal location update request sent by the first service person account, the platform server may update the location of the service person registered by the first service person account based on new location information carried in the personal location update request.
S3022: and sequentially comparing the positions of the service personnel with the current position of the user, and taking the service personnel account corresponding to the position of the service personnel with the distance difference smaller than a preset difference threshold value as a recommended service personnel account.
For any service person account, the platform server may compare the location of the registered service person with the current location of the user, and thus confirm the distance difference between the two. When the distance difference is smaller than a preset difference threshold value, such as 5km, 10km and the like, the service staff account can be used as the recommended service staff account. The platform server may perform the above-described processing on each of the service person accounts associated with the recommended merchant account in sequence until all of the recommended service person accounts are screened out.
S303: and feeding back account information of all the recommended service personnel accounts to the target user account.
For example, the platform server may sort account information of all recommended service person accounts, and send the sorted account information to the target user account for the consumer to check and select.
S304: and selecting a final service personnel account from the recommended service personnel accounts based on the received selection instruction.
Illustratively, after the customer completes the selection, the customer may send a selection instruction in which a selection result, that is, a final service staff account number is recorded to the platform server through the user side, so that the platform server can select the final service staff account number from all recommended service staff account numbers.
S305: and sending a service notice to the final service staff account.
For example, the platform server may send a service notification carrying information such as a current location of the user, a contact information of the user (which may be recorded in the target user account), and the like to the final service staff account, so that the service staff to which the final service staff account belongs can provide home service.
By adopting the technical scheme, on one hand, the work of the service personnel is not limited to the affiliated merchants and the positions of the merchants, so that the service personnel can work according to the requirements of the service personnel on business trips or travels conveniently. On the other hand, for the consumer, the service staff of the mental apparatus can be selected to carry out the home service, and the user experience is improved.
Optionally, in another embodiment, the method may further include the following:
if it is recognized that the target member card is specified in the received sharing service request before S202, the execution of S202 is cancelled, and in S203, the merchant account to which the target member card belongs is directly used as the target merchant account.
Optionally, in another embodiment, S305 includes, but is not limited to, the following:
and sending a prepayment receiving notice to the target user account.
For example, to prevent malicious billing of individual ill-centered consumers, the platform server may first send a pre-payment receipt notification to the target user account via the shared platform.
And after receiving a payment confirmation notice fed back by the target user account, sending a service notice to the final service staff account.
For example, after the consumer completes online payment through the user terminal logged in with the target user account, the target user account may send a payment confirmation notification to the platform server. The platform server sends a service notification to the final service staff account after receiving the payment confirmation notification.
Meanwhile, for the capital safety of the consumer, the prepayment can be temporarily stored in a platform capital account of the sharing platform and cannot be directly transferred to a final service staff account.
Further, in another embodiment, after the step of sending the service notification to the final service staff account after receiving the payment confirmation notification fed back by the target user account, the following steps may be further included:
and after receiving the service completion notification fed back by the target user account, confirming the payment type based on the payment confirmation notification.
For example, after the service is completed, the consumer may send a service completion notification to the platform server through the user terminal logged in with the target user account. The platform server, upon receiving the service completion notification, may confirm the payment type based on the previously received payment confirmation notification. The payment type may include direct payment, membership card balance payment, and the like.
And when the payment type is direct payment, allocating the prepayment to the final service personnel account and the associated merchant account according to a preset first allocation rule.
For example, when the payment type is identified as direct payment, the platform server may allocate the prepaid fee between the final attendant account and the associated merchant account in proportion based on a preset first allocation rule. In some embodiments, the remaining prepaid fee may be allocated after deduction of the share platform credit.
And when the payment type is membership card balance payment, identifying a target membership card selected by the target user account.
The target membership card may be any one or more of all membership cards owned by the target user account.
For example, when the payment type is identified as membership card balance payment, the platform server may further identify a target membership card selected for payment by the target user account.
And allocating the prepayment to the merchant account number to which the target member card belongs, the final service staff account number and the merchant account number associated with the final service staff account number according to a preset second allocation rule.
For example, the platform server may allocate the prepaid fee among the merchant account to which the target member card belongs, the final service person account, and the merchant account associated with the final service person account according to a preset second allocation rule.
Based on the foregoing method, an embodiment of the present application further discloses a platform server, and with reference to fig. 4, the platform server includes:
the information receiving module 41 is configured to receive a shared service request sent by a target user account, where the shared service request records a required service type and a current location of a user.
And the user account identification module 42 is used for identifying all the membership cards owned by the target user accounts.
And a target merchant account number specifying module 43, configured to identify the merchant account number of each member card as a target merchant account number.
And the associated merchant account identification module 44 is configured to identify an associated merchant account associated with each target merchant account as a target associated merchant account.
And a recommended merchant account selecting module 45, configured to select a recommended merchant account from all the target merchant accounts and the target associated merchant accounts based on the demand service type and the current location of the user.
And the information sending module 46 is configured to feed back the merchant information corresponding to the recommended merchant account to the target user account.
Optionally, the platform server further includes:
and the shared service request identification module is used for identifying whether the shared service request carries a visiting service label or not after the recommended merchant account is selected.
And the recommended service person account selecting module is used for selecting recommended service person accounts from the service person accounts associated with all the recommended merchant accounts based on the current position of the user when the identification result of the shared service request identification module is positive.
The information sending module 46 is further configured to feed back account information of all recommended service personnel accounts to the target user account.
The platform server also comprises a final service staff account number selection module used for selecting the final service staff account number from the recommended service staff account number based on the received selection instruction.
The information sending module 46 is further configured to send a service notification to the final service staff account.
Optionally, the target merchant account number designating module 43 is further configured to, after the sharing service request identifying module identifies that the target member card is not designated in the sharing service request, cancel the step of identifying all member cards owned by the target user account number, and use the merchant account number to which the target member card belongs as the target merchant account number.
Optionally, the recommended service person account selecting module is specifically configured to perform the following processing:
and identifying the positions of the service personnel registered by all the service personnel accounts associated with the recommended merchant account.
And sequentially comparing the positions of the service personnel with the current position of the user, and taking the service personnel account corresponding to the position of the service personnel with the distance difference smaller than a preset difference threshold value as a recommended service personnel account.
Optionally, the platform server further includes a service staff position updating module, configured to update a service staff position registered by the first service staff account after receiving a personal position updating request sent by the first service staff account.
Optionally, the information sending module 46 is specifically configured to send a prepaid charging notification to the target user account.
The information sending module 46 is further configured to send a service notification to the final service staff account after the information receiving module 41 receives the payment confirmation notification fed back by the target user account.
Optionally, the platform server further includes:
and the payment type confirmation module is used for confirming the payment type based on the payment confirmation notice after receiving the service completion notice fed back by the target user account.
And the distribution module is used for distributing the prepayment to the final service staff account and the associated merchant account according to a preset first distribution rule when the payment type is direct payment.
And the target membership card identification module is used for identifying the target membership card selected by the target user account when the payment type is membership card balance payment.
The distribution module is further used for distributing the prepayment to the merchant account number to which the target member card belongs, the final service staff account number and the merchant account number related to the final service staff account number according to a preset second distribution rule.
The embodiment of the application also discloses a server terminal, which comprises a memory and a processor, wherein the memory is stored with a computer program which can be loaded by the processor and can execute the cross-region and cross-merchant resource sharing method.
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 the processor to implement the cross-regional and cross-business resource sharing method provided by the above method embodiments.
The above examples are only used to illustrate the technical solutions of the present application, and do not limit the scope of protection of the application. It is to be understood that the embodiments described are only some of the embodiments of the present application and not all of them. All other embodiments, which can be derived by a person skilled in the art from these embodiments without making any inventive step, are within the scope of the present application.
Claims (10)
1. A cross-region and cross-merchant resource sharing method is characterized in that the method is based on a platform server in a cross-region and cross-merchant resource sharing system, a sharing platform is built in the platform server, and a merchant account and a user account are registered in the sharing platform, and the method comprises the following steps:
receiving a sharing service request sent by a target user account, wherein the sharing service request records a required service type and a current position of a user;
identifying all membership cards owned by the target user account;
identifying the affiliated merchant account of each member card as a target merchant account;
identifying a related merchant account associated with each target merchant account as a target related merchant account;
based on the demand service type and the current position of the user, selecting a recommended merchant account from all the target merchant accounts and the target associated merchant accounts;
and feeding back merchant information corresponding to the recommended merchant account to the target user account.
2. The method for resource sharing across regions and merchants according to claim 1, wherein the sharing platform further registers an account number of a service person associated with a merchant account number;
after the picking up of the recommended merchant account, the method further comprises:
identifying whether the shared service request carries a door service tag;
and when the identification result is yes, canceling the step of feeding back the merchant information corresponding to the recommended merchant account to the target user account, and executing the following processing:
selecting a recommended service personnel account from the service personnel accounts associated with all the recommended merchant accounts based on the current position of the user;
feeding back account information of all the recommended service personnel accounts to the target user account;
based on the received selection instruction, selecting a final service staff account from the recommended service staff accounts;
and sending a service notice to the final service staff account.
3. The method of claim 1, wherein the method further comprises:
if the target membership card is identified in the sharing service request, the step of identifying all the membership cards owned by the target user account is cancelled, and the merchant account to which the target membership card belongs is taken as the target merchant account.
4. The cross-region and cross-merchant resource sharing method according to claim 2, wherein the selecting a recommended service person account from the service person accounts associated with all the recommended merchant accounts based on the current location of the user comprises:
identifying the positions of service personnel registered by all service personnel accounts associated with the recommended merchant account;
and sequentially comparing the positions of the service personnel with the current position of the user, and taking the service personnel account corresponding to the position of the service personnel with the distance difference smaller than a preset difference threshold value as a recommended service personnel account.
5. The method of claim 4, wherein the method further comprises:
after receiving a personal location update request sent by a first service personnel account, updating the location of the service personnel registered by the first service personnel account.
6. The cross-region and cross-merchant resource sharing method according to claim 2, wherein the sending of the service notification to the final service staff account specifically includes:
sending a prepayment receiving notice to the target user account;
and after receiving a payment confirmation notification fed back by the target user account, sending a service notification to the final service staff account.
7. The method for resource sharing across regions and merchants according to claim 6, wherein after the sending a service notification to the final service staff account after receiving the payment confirmation notification fed back by the target user account, further comprising:
after receiving a service completion notification fed back by the target user account, confirming a payment type based on the payment confirmation notification;
when the payment type is direct payment, allocating the prepayment to the final service staff account and the associated merchant account according to a preset first allocation rule;
when the payment type is membership card balance payment, identifying a target membership card selected by the target user account;
and distributing the prepayment to the merchant account number to which the target member card belongs, the final service staff account number and the merchant account number related to the final service staff account number according to a preset second distribution rule.
8. A cross-region and cross-merchant resource sharing system is characterized by comprising a platform server and a user side, wherein the platform server comprises:
the information receiving module is used for receiving a sharing service request sent by a target user account, and the sharing service request records a required service type and a current position of a user;
the user account identification module is used for identifying all membership cards owned by the target user account;
the target merchant account number specifying module is used for identifying the merchant account number of each member card as a target merchant account number;
the correlated merchant account identification module is used for identifying a correlated merchant account correlated with each target merchant account to serve as the target correlated merchant account;
a recommended merchant account selecting module, configured to select a recommended merchant account from all the target merchant accounts and the target associated merchant accounts based on the demand service type and the current location of the user;
and the information sending module is used for feeding back the merchant information corresponding to the recommended merchant account to the target user account.
9. A server terminal comprising a memory and a processor, the memory having stored thereon a computer program that can be loaded by the processor and that executes the method according to any of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which can be loaded by a processor and which executes the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211670517.2A CN115640465B (en) | 2022-12-26 | 2022-12-26 | Cross-region and cross-merchant resource sharing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211670517.2A CN115640465B (en) | 2022-12-26 | 2022-12-26 | Cross-region and cross-merchant resource sharing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115640465A true CN115640465A (en) | 2023-01-24 |
| CN115640465B CN115640465B (en) | 2023-03-31 |
Family
ID=84949840
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211670517.2A Active CN115640465B (en) | 2022-12-26 | 2022-12-26 | Cross-region and cross-merchant resource sharing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115640465B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105096151A (en) * | 2014-05-15 | 2015-11-25 | 中国移动通信集团公司 | Information recommendation method, device, and server |
| US20160224964A1 (en) * | 2015-02-03 | 2016-08-04 | Mastercard International Incorporated | Systems and methods for managing payment account holders |
| CN106709758A (en) * | 2016-12-19 | 2017-05-24 | 浙江网新恒天软件有限公司 | Intelligent recommendation and distribution solution for service class commodities in electronic commerce products |
| CN109858959A (en) * | 2019-01-18 | 2019-06-07 | 深圳壹账通智能科技有限公司 | Credit card recommended method, device, computer equipment and storage medium |
| CN110335117A (en) * | 2019-07-03 | 2019-10-15 | 武汉金康高科技有限公司 | A kind of member's sharing method and system |
| CN112529655A (en) * | 2020-12-03 | 2021-03-19 | 江苏财经职业技术学院 | Electronic commerce transaction system based on mobile phone terminal |
-
2022
- 2022-12-26 CN CN202211670517.2A patent/CN115640465B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105096151A (en) * | 2014-05-15 | 2015-11-25 | 中国移动通信集团公司 | Information recommendation method, device, and server |
| US20160224964A1 (en) * | 2015-02-03 | 2016-08-04 | Mastercard International Incorporated | Systems and methods for managing payment account holders |
| CN106709758A (en) * | 2016-12-19 | 2017-05-24 | 浙江网新恒天软件有限公司 | Intelligent recommendation and distribution solution for service class commodities in electronic commerce products |
| CN109858959A (en) * | 2019-01-18 | 2019-06-07 | 深圳壹账通智能科技有限公司 | Credit card recommended method, device, computer equipment and storage medium |
| CN110335117A (en) * | 2019-07-03 | 2019-10-15 | 武汉金康高科技有限公司 | A kind of member's sharing method and system |
| CN112529655A (en) * | 2020-12-03 | 2021-03-19 | 江苏财经职业技术学院 | Electronic commerce transaction system based on mobile phone terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115640465B (en) | 2023-03-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104639756B (en) | A kind of method and device for showing short message | |
| EP3522081A1 (en) | System and method for arranging transport amongst parties through use of mobile devices | |
| US20130246301A1 (en) | Providing user feedback for transport services through use of mobile devices | |
| EP3886007A1 (en) | Information processing method and information processing system | |
| US20060136254A1 (en) | System and method for dispatching transportation to persons who want transportation | |
| US20240070624A1 (en) | Systems and methods for least cost acquirer routing for pricing models | |
| US10021243B2 (en) | Telephone call placement | |
| JP5003143B2 (en) | Electronic money system | |
| KR101930359B1 (en) | Systems and methods for delivering logistics to people and people | |
| CN115081991A (en) | Raw material management method and device, electronic equipment and storage medium | |
| CN110610340A (en) | Spare part management method, device, equipment and computer readable storage medium | |
| KR20130142213A (en) | Proxy driving system using smart phone and method for managing the same | |
| US20170024837A1 (en) | Method and apparatus for improving a public transport system | |
| CN115640465B (en) | Cross-region and cross-merchant resource sharing method and system | |
| JP6646008B2 (en) | Payment system, host terminal, payment method, program, and vehicle | |
| CN111784294A (en) | Method, device, server and storage medium for determining prepaid luggage service | |
| KR101033006B1 (en) | Business Taxi card service system | |
| CN110648209A (en) | Tourism order processing method | |
| KR101533003B1 (en) | Method and system for providing goods transport service and apparatus therefor | |
| CN111698195B (en) | Information interaction method and device | |
| US20200184432A1 (en) | Systems and Methods for Transferring Funds to a Pre-Paid Account | |
| JP2017010181A (en) | Adjustment system and method | |
| JP4329754B2 (en) | Service providing system and terminal device thereof | |
| KR102417808B1 (en) | Method, system and computer readable storage medium for handling self-payment and non-payment | |
| JP7272536B2 (en) | Transportation fee calculation system and computer program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |