CN113242310A - Method and device for realizing service based on small program - Google Patents
Method and device for realizing service based on small program Download PDFInfo
- Publication number
- CN113242310A CN113242310A CN202110571511.9A CN202110571511A CN113242310A CN 113242310 A CN113242310 A CN 113242310A CN 202110571511 A CN202110571511 A CN 202110571511A CN 113242310 A CN113242310 A CN 113242310A
- Authority
- CN
- China
- Prior art keywords
- service
- service end
- applet
- saas
- account
- 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
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004891 communication Methods 0.000 claims abstract description 20
- 238000013507 mapping Methods 0.000 claims description 8
- 230000001960 triggered effect Effects 0.000 claims description 4
- 230000006870 function Effects 0.000 abstract description 19
- 230000008520 organization Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44568—Immediately runnable code
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention discloses a method and a device for realizing services based on small programs, wherein the method comprises the following steps: detecting a service request associated with a first service end of a target object configured in an applet; inquiring account number binding relation and service end binding relation stored in a background database, and determining a second service end which is bound with a first service end configured in the applet of the target object and is created in a service platform in advance; and the first service end calls each service component in the second service end to provide services. The mode can realize data communication between the service and the small program and provide more flexible and convenient service functions for the small program.
Description
The present application is a divisional application of an invention patent application entitled "method and apparatus for implementing services based on applets" with an application number of 202010613947.5, which is 30/06/2020.
Technical Field
The embodiment of the invention relates to the field of electronic information, in particular to a method and a device for realizing services based on applets.
Background
The applet is an application which can be used without downloading and installing, the dream of 'being reachable by a touch hand' of the application is realized, and the application can be opened by scanning or searching by a user; the concept of 'running after running' is also embodied, and a user does not need to be concerned about whether too many applications are installed. Applications become ubiquitous, readily available, but do not require installation and uninstallation. Therefore, the convenience of use of the user can be greatly improved by the small program.
SaaS is an abbreviation for Software-as-a-service. The SaaS provider builds all network infrastructures, software and hardware operation platforms required by informatization for enterprises and is responsible for a series of services such as implementation in the early stage, maintenance in the later stage and the like, and the enterprises can use the information system through the Internet without purchasing software and hardware, building a machine room and recruiting IT personnel. Therefore, the enterprise can rent the software service to the SaaS provider according to the actual requirement. Therefore, the SaaS service can be more flexibly and conveniently deployed.
At present, applets and various services (such as SaaS services) are mutually independent, the applets win a large number of user groups with the advantages of lightness and convenience, and the various services also gain the favor of the majority of users with the advantages of flexible renting and convenient deployment. However, a scheme capable of flexibly applying various services in an applet is not available at present, and the advantages of the two can not be superposed.
Disclosure of Invention
In view of the above, embodiments of the present invention are proposed to provide a method and apparatus for implementing services based on applets that overcome or at least partially solve the above problems.
According to an aspect of an embodiment of the present invention, there is provided a method for implementing a service based on an applet, including:
detecting a service request associated with a first service end of a target object configured in an applet;
inquiring account number binding relation and service end binding relation stored in a background database, and determining a second service end which is bound with a first service end configured in the applet of the target object and is created in a service platform in advance;
and the first service end calls each service component in the second service end to provide services.
Optionally, the invoking, by the first service end, each service component in the second service end to provide the service includes:
the first service end calls an information pushing assembly in the second service end to realize information pushing operation;
and/or the first service end calls a payment component in the second service end to realize payment operation.
Optionally, the detecting a service request associated with a first service end of the target object configured in the applet specifically includes:
when a login request triggered by the target object through a first object account is detected, a second object account bound with the first object account is logged in according to the account binding relationship;
The method further comprises the following steps: and starting the second service terminal according to the second object account.
Optionally, the determining a second service end, which is created in the service platform in advance and is bound to the first service end of the target object configured in the applet, includes:
acquiring service end identification information of a first service end, and judging whether a service end matched with the service end identification information is established in a service platform;
and if so, taking the service end matched with the service end identification information as a second service end bound with the first service end.
Optionally, the method further includes:
and if the service end matched with the service end identification information is not created in the service platform, creating a second service end bound with the first service end in the service platform.
Optionally, the creating, in the service platform, a second service end bound to the first service end includes:
binding a first identifier of the first service end and a second identifier of the second service end;
and acquiring service data corresponding to the first service end, and establishing a mapping relation between the second identifier and the service data so that the second service end calls the service data based on the mapping relation.
Optionally, the determining whether a service end matched with the service end identification information is created in the service platform includes:
matching the service end name and/or the service end address of each service end with name information and/or address information contained in the service end identification information respectively, and judging whether a service end matched with the service end identification information is created according to a matching result;
the matching priority of the service end address is higher than that of the service end name.
Optionally, if the first service end and the second service end have service type identifiers, the determining of the second service end, which is created in the service platform in advance and bound to the first service end configured in the applet by the target object, includes:
determining a second service end bound with a first service end of the target object configured in the applet according to the service type identifier;
wherein, the service type identifier comprises: merchant class service identification and/or aggregate payment class service identification.
Optionally, the target object is a merchant object, and the service end is a store service end affiliated to the merchant object.
According to another aspect of the embodiments of the present invention, there is provided an apparatus for implementing a service based on an applet, including:
means for detecting a service request associated with a first service configured by a target object in an applet;
a module for inquiring the account number binding relationship and the service end binding relationship stored in a background database, and determining a second service end which is bound with a first service end configured in the applet for the target object and is created in the service platform in advance;
and the module is used for enabling the first service end to call each service component in the second service end to provide services.
According to still another aspect of the embodiments of the present invention, there is provided an electronic apparatus including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the method for realizing the service based on the small program.
According to a further aspect of the embodiments of the present invention, there is provided a computer storage medium, in which at least one executable instruction is stored, and the executable instruction causes a processor to execute operations corresponding to the method for implementing a service based on an applet as described above.
In the method and the device for realizing the service based on the applet, the second service end can be called in the first service end to provide the service based on the account number binding relationship and the service end binding relationship stored in the background database, so that the service function can be applied to the applet, the data communication between the service and the applet is realized, and a more flexible and convenient service function is provided for the applet.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart illustrating a method for implementing a service based on an applet according to an embodiment of the present invention;
Fig. 2 is a flowchart illustrating a method for implementing a service based on an applet according to a second embodiment of the present invention;
FIG. 3 is a block diagram of an apparatus for implementing services based on applets according to a third embodiment of the present invention;
fig. 4 shows a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Example one
Fig. 1 shows a flowchart of a method for implementing a service based on an applet according to an embodiment of the present invention. As shown in fig. 1, the method includes:
step S110: the method comprises the steps of obtaining a first object account corresponding to a target object in an applet, creating a second object account bound with the first object account in a service platform, and storing the account binding relationship into a background database.
The target object may be various objects, for example, a merchant object, a user object, and the like. Accordingly, the first object account number is used to uniquely identify the target object in the applet. In order to realize the service in the applet, a second object account bound with the first object account needs to be created in the service platform. The service platform is used for realizing services. The second object account is subordinate to the service platform, and the object entities corresponding to the second object account and the first object account are the same. In this step, the first object account and the second object account need to be bound with each other, and the account binding relationship is stored in the background database, so as to realize the login-free function of logging in the second object account through the first object account. The service in this embodiment may be a SaaS service, or may be other various services, and the service type is not limited in the present invention.
Step S120: the method comprises the steps of obtaining a first service end of a target object configured in an applet, creating a second service end bound with the first service end in a service platform, and storing a service end binding relation into a background database.
The service end refers to a network terminal or an application program for providing service for a user in an online manner. The first service terminal is configured in the applet by the target object and is managed through the object account of the target object.
In order to facilitate the invoking of the service in the first service end, a second service end bound to the first service end needs to be created in the service platform. The second service end and the first service end correspond to the same service end entity, and the difference between the two service ends is as follows: the first business end is a business end which is created in the applet and corresponds to the business end entity, and the second business end is a business end which is created in the service platform and corresponds to the business end entity. In order to facilitate the mutual call between the first service end and the second service end, in this step, the binding relationship between the first service end and the second service end needs to be recorded, and the binding relationship between the first service end and the second service end needs to be stored in a background database.
Step S130: when a service request associated with a first service end configured by a target object in the applet is detected, a second service end bound with the first service end configured by the target object in the applet is determined according to an account binding relationship and a service end binding relationship stored in a background database, and a service is provided based on the second service end.
The service request associated with the first service end configured by the target object in the applet includes various network requests associated with the first service end, such as various types of login requests, access requests, and the like. Correspondingly, when a service request associated with a first service end configured by the target object in the applet is detected, the account binding relationship and the service end binding relationship stored in the background database are inquired, so that a second service end corresponding to the target object in the service platform is determined, and the service is provided based on the inquired second service end.
The second business terminal is configured based on the service platform, so that various service components realized based on the service platform can be flexibly deployed, and correspondingly, the first business terminal can directly call each service component in the second business terminal to provide services, thereby expanding the business function of the first business terminal.
Therefore, in the method for implementing the service based on the applet provided by the embodiment of the invention, the first object account corresponding to the target object in the applet and the second object account corresponding to the target object in the service platform can be bound with each other, the first service end configured in the applet of the target object and the second service end created in the service platform are bound with each other, and the second service end is called in the first service end to provide the service based on the binding relationship, so that the service function can be applied to the applet, the data communication between the service and the applet is further implemented, and a more flexible and convenient service function is provided for the applet.
Example II,
Fig. 2 shows a flowchart of a method for implementing a service based on an applet according to a second embodiment of the present invention, and in this embodiment, a service is an SaaS service, but the service in this embodiment may also be another service. As shown in fig. 2, the method includes:
Step S210: and acquiring a first object account corresponding to the target object in the applet.
In this embodiment, the target object mainly refers to a merchant object. Accordingly, the first object account number is used to uniquely identify the merchant object in the applet. For example, the first object account number may be a merchant PID (partner ID) that uniquely identifies a merchant.
Step S220: and creating a second object account bound with the first object account in the SaaS service platform, and storing the account binding relationship into a background database.
Specifically, in order to implement SaaS service in an applet, a second object account bound to a first object account needs to be created in the SaaS service platform. The SaaS service platform is used for realizing the SaaS service. The second object account is subordinate to the SaaS service platform, and the object entities corresponding to the second object account and the first object account are the same. Namely: the second object account and the first object account both correspond to the same merchant object. In this step, the first object account and the second object account need to be bound with each other, and the account binding relationship is stored in the background database, so as to realize the login-free function of logging in the second object account through the first object account.
Through the method, the first object account for the applet and the second object account for the SaaS service platform can be respectively created for the object entities of the same merchant object. Moreover, because the first object account and the second object account are bound with each other, the mutual login between the first object account and the second object account can be realized in the subsequent steps. For example, after the user logs in the first object account, the background can automatically log in the second object account based on the account binding relationship.
Step S230: the method comprises the steps of obtaining a first service end of a target object configured in an applet, creating a second service end bound with the first service end in a SaaS service platform, and storing a service end binding relation into a background database.
The service end refers to a network terminal or an application program for providing service for a user in an online manner. In this embodiment, the service end is a store service end belonging to a merchant object. Correspondingly, the first business end is a store business end configured by the merchant object in the applet and is managed through the object account of the merchant object.
In order to facilitate the invocation of the SaaS service in the first service end, a second service end bound to the first service end needs to be created in the SaaS service platform. The second service end and the first service end correspond to the same service end entity, and the difference between the two service ends is as follows: the first business end is a business end which is created in the applet and corresponds to the business end entity, and the second business end is a business end which is created in the SaaS service platform and corresponds to the business end entity. In order to facilitate the mutual call between the first service end and the second service end, in this step, the binding relationship between the first service end and the second service end needs to be recorded, and the binding relationship between the first service end and the second service end needs to be stored in a background database.
In particular, in order to facilitate the sharing of the service data and save the consumption of the storage space, in this embodiment, the second service end and the first service end may share the same service data, so that the background database only needs to maintain one service data to realize the sharing of the two service ends. Correspondingly, when a second business end bound with the first business end is created in the SaaS service platform, firstly, a first identifier of the first business end and a second identifier of the second business end are bound; then, the service data corresponding to the first service end is obtained, and a mapping relation between the second identifier and the service data is established, so that the second service end calls the service data based on the mapping relation. The first identifier may be a name of the first service end or various contents such as an organization hierarchical relationship, and similarly, the second identifier may be a name of the second service end or various contents such as an organization hierarchical relationship.
In addition, when creating the second service end bound to the first service end in the SaaS service platform, in order to avoid repeated creation, the following determination logic needs to be executed: acquiring service end identification information of a first service end, and judging whether an SaaS service end matched with the service end identification information is established in an SaaS service platform; if so, directly taking the SaaS service end matched with the service end identification information as a second service end bound with the first service end; and if not, creating the SaaS service end matched with the service end identification information in the SaaS service platform to serve as a second service end.
When judging whether a SaaS service end matched with the service end identification information is created in the SaaS service platform, respectively matching the service end name and/or the service end address of each SaaS service end with name information and/or address information contained in the service end identification information, and judging whether the SaaS service end matched with the service end identification information is created according to a matching result; considering that the name has a duplicate name, the address of each service end is necessarily unique (the same address can only correspond to one store), and therefore, the matching priority of the service end address is higher than that of the service end name.
Step S240: when a service request associated with a first service end configured by a target object in an applet is detected, a second service end bound with the first service end configured by the target object in the applet is determined according to an account binding relationship and a service end binding relationship stored in a background database, and SaaS service is provided based on the second service end.
The service request associated with the first service end configured by the target object in the applet includes various network requests associated with the first service end, such as various types of login requests, access requests, and the like. For example, when a login request triggered by a target object through a first object account is detected, a second object account bound with the first object account is logged in according to an account binding relationship, and accordingly, when the SaaS service is provided based on a second service terminal, the second service terminal is started according to the second object account, so that the SaaS service is provided based on the second service terminal. Therefore, in the method, the second object account bound with the first object account can be automatically logged in based on the account binding relationship, and the second service terminal is started according to the second object account. The second object account and the first object account correspond to the same merchant object entity, but the second object account is provided by the SaaS service platform, so that an auxiliary service function based on the SaaS service can be realized for the merchant object entity.
Correspondingly, when a service request associated with a first service end configured by the target object in the applet is detected, the account binding relationship and the service end binding relationship stored in the background database are inquired, so that a second service end corresponding to the target object in the SaaS service platform is determined, and the SaaS service is provided based on the inquired second service end.
Specifically, when providing the SaaS service based on the second service end, the method is implemented in the following manner: and acquiring a pre-configured service component corresponding to the second service end, and providing SaaS service matched with the service component to the first service end. The service components are implemented based on a SaaS service platform, and one or more service components corresponding to the second service end may be implemented, for example, the service components may include: an information push class component, and/or a payment class component. The information pushing type component can realize various types of information pushing operation, so that various types of information associated with the merchant object entity can be pushed to the user. The payment component is used for realizing payment operation and can be communicated with various third party payment platforms, so that the payment mode of a user is expanded. In short, through the above manner, the first service end located in the applet can directly call the service component located in the second service end of the SaaS service platform, so that the SaaS service function is realized in the applet. The second service end is configured based on the SaaS service platform, so that various SaaS service components realized based on the SaaS service platform can be flexibly deployed, and correspondingly, the first service end can directly call the SaaS service provided by each SaaS service component in the second service end, so that the service function of the first service end is expanded.
In addition, considering that the service end has a plurality of different types, in order to facilitate fast query of the second service end corresponding to the first service end, the query may be performed based on the service type identifier. Correspondingly, the first service end and the second service end are provided with service type identifiers, and when the second service end bound with the first service end configured in the applet by the target object is determined, the second service end bound with the first service end configured in the applet by the target object is determined according to the service type identifiers; the service type identifier comprises: merchant class service identification and/or aggregate payment class service identification.
To sum up, through the above manner, the first object account corresponding to the target object in the applet and the second object account corresponding to the target object in the SaaS service platform can be bound to each other, the first service end configured in the applet of the target object and the second service end created in the SaaS service platform are bound to each other, and then based on the binding relationship, the second service end is called in the first service end to provide the SaaS service, so that the SaaS service function can be applied to the applet, thereby realizing data communication between the SaaS service and the applet, and providing a more flexible and convenient service function for the applet. Moreover, the method is particularly suitable for the store business end, and the store business end realized by the small program can provide the SaaS service through the SaaS business end bound with the store business end.
For the convenience of understanding, the following describes specific implementation details in the above embodiments by taking a specific example as an example. In this example, the target object is a merchant object, and the business end is a store business end under a merchant flag.
First, a merchant account (i.e., the first mentioned object account) of a merchant object in an applet is obtained, and then a SaaS account bound to the merchant account is created, where the SaaS account is the second mentioned object account. The SaaS account and the merchant account both correspond to the same merchant object entity. Specifically, after a merchant logs in a merchant applet, a background firstly queries whether a merchant PID corresponding to a merchant account has an associated SaaS merchant (also called SaaS brand), and specifically, the query interface provided by the SaaS service platform can be used for querying so as to query whether the associated SaaS merchant exists through a bound partner enterprise PID. And if the corresponding SaaS merchant exists, directly multiplexing the SaaS merchant and the SaaS account number of the SaaS merchant. If the SaaS merchant is not inquired, the SaaS account needs to be created based on the communication number of the merchant PID, and the SaaS merchant is created based on the account name of the PID, wherein the SaaS merchant comprises a brand and a group corresponding to the merchant.
And then, establishing a login-free relationship between the merchant account and the SaaS account. Specifically, a login-free relationship needs to be established between the merchant applet and the SaaS service platform, so that the merchant can be ensured to be connected with the SaaS service platform. Meanwhile, the account data needs to be communicated with each other. Specifically, by using the data storage capacity, the account number of the merchant at the applet terminal is reused on the SaaS service platform, so that the merchant can realize multi-terminal login and multi-terminal use through one account number. In addition, if the merchant does not organize data on the SaaS service platform side, the establishment operation of the organization data can be performed through the SaaS service platform after the merchant logs in the SaaS service platform through the applet, so that the integrity of the organization framework is guaranteed. Therefore, in the step, a binding relationship is established between the PID registered by the current merchant and the SaaS merchant established by the merchant, and the binding relationship is recorded in a database in the SaaS domain.
Next, the establishment of the store business end and the construction operation of the binding relationship need to be realized. Specifically, when a merchant applet is created, information of a store service end is selected, and a binding relationship is established between the store service end (namely, a first service end) selected in the applet and a SaaS store service end (namely, a second service end) in a SaaS platform organization basis.
In addition, in the process of establishing the binding store relationship, if no SaaS store is created under the SaaS merchant of the SaaS platform, the SaaS store needs to be established, the established basic data is that store information in the applet is directly reused, after the establishment is completed, the applet and the store in the SaaS platform are established to be the binding relationship, and the binding relationship is stored in the SaaS platform.
If a SaaS merchant of the SaaS platform has a SaaS store created, the store in the applet will be matched with the store in the SaaS platform by the following rules:
(1) checking whether the shops in the small program have a SaaS shop binding relationship, and if so, directly multiplexing the binding relationship;
(2) checking whether an associated store exists in an associated database of stores in the applet, if so, further inquiring whether the associated store exists a bound SaaS store, if so, directly matching the SaaS store, establishing a binding relationship, and if not, matching through the following logic bottom-of-pocket principle:
the bottom-in-pocket matching principle is a principle of matching SaaS stores according to names and provincial areas. For example, if the names of stores in the applet and SaaS stores are the same, and the provincial city (county) is also the same, the matching is successful; for another example, if the names of stores in the applet and SaaS stores are the same but the provincial city (county) is different, the matching fails; as another example, if the store and SaaS store names in the applet are different and the provincial city (county) is also different, the matching fails; as another example, if the names of stores in the applet and SaaS stores are different but the provincial region (county) is the same, the address is checked, and if the addresses are the same, the matching is successful. And aiming at the condition of successful matching, establishing a binding relationship between an outlet in the applet and an SaaS outlet. After the matching operation, if the matching fails, a SaaS store (i.e., a second service end) is created.
In addition, in consideration of compatibility with other services, a service identity (i.e., a service type identifier) needs to be set for the SaaS store, and the service identity is used for implementing a quick query function. For example, a SaaS store created or bound in an applet needs to be marked with a service identity of a "light store" at the SaaS store; for another example, a service identity of a CRM is to be marked on a SaaS store created or bound in the CRM; for another example, a SaaS store created based on aggregated payment is to be marked with a service identity of "aggregated payment" at the SaaS store. Accordingly, the respective business only identifies the store of the respective business identity, which is then associated by the store owner. If the CRM side updates the binding relationship between the SaaS stores and the small program stores, the binding relationship between the light stores and the store main body of the aggregated payment class is also updated accordingly.
Therefore, in the embodiment, multiple service types such as a CRM service type, a light store service type, and an aggregate payment service type are set, and accordingly, corresponding service type identifiers are configured at both a first service end in the applet and a second service end in the SaaS platform, so that services of different service types only need to obtain service ends of corresponding service types, and the influence of mutual interference of multiple service types is avoided. The account binding relationship and the service end binding relationship can be realized in a physical binding mode, and the service ends and the service end entities thereof corresponding to different service types can be realized in a logical binding mode.
As can be seen, in the present example, SaaS service can be implemented based on an applet. The interconnection and intercommunication between the business small program and the basic organization capability of the SaaS platform are realized, and more flexible and complex business functions can be realized in the light business small program through the SaaS service of the SaaS platform. For example, a series of SaaS service-based business functions can be built within a merchant applet (light store) and an aggregated payment applet. The SaaS service can provide multiple business functions such as frequency promotion, repeated purchase, customer service list and the like for the merchant. For example, multiple functions such as pushing of electronic coupons, pushing of business information, ordering, payment and the like can be realized through the SaaS service. In a word, the scheme can interconnect and intercommunicate data of the small program of the merchant and the SaaS platform, so that complex and flexible basic capability construction is realized in the light merchant small program based on the capability of the SaaS platform, and the business function of the merchant small program is expanded by means of the SaaS platform.
In addition, in the above embodiment, the service platform is a SaaS service platform, but may also be other types of service platforms, and similarly, the service end may also be other types of service ends besides SaaS, which is not limited in the present invention.
EXAMPLE III
Fig. 3 shows an apparatus for implementing a service based on an applet, which is provided by a third embodiment of the present invention, and includes:
the account binding module 31 is adapted to acquire a first object account corresponding to a target object in an applet, create a second object account bound with the first object account in a service platform, and store an account binding relationship in a background database;
a service end binding module 32, adapted to obtain a first service end configured in the applet by the target object, create a second service end bound to the first service end in the service platform, and store a service end binding relationship in the background database;
the service module 33 is adapted to, when a service request associated with a first service end configured in the applet by the target object is detected, determine, according to the account binding relationship and the service binding relationship stored in the background database, a second service end bound with the first service end configured in the applet by the target object, and provide a service based on the second service end.
Optionally, the service module is specifically adapted to:
acquiring a service component which is configured in advance and corresponds to the second service end, and providing a service matched with the service component for the first service end;
The business service assembly is realized based on a service platform, and comprises: an information push class component, and/or a payment class component.
Optionally, the service module is specifically adapted to:
when a login request triggered by the target object through the first object account is detected, logging in a second object account bound with the first object account according to the account binding relationship;
and starting the second service terminal according to the second object account, and providing service based on the second service terminal.
Optionally, the service end binding module is specifically adapted to:
binding a first identifier of the first service end and a second identifier of the second service end;
and acquiring service data corresponding to the first service end, and establishing a mapping relation between the second identifier and the service data so that the second service end calls the service data based on the mapping relation.
Optionally, the service end binding module is specifically adapted to:
acquiring service end identification information of a first service end, and judging whether a service end matched with the service end identification information is established in a service platform;
If so, taking the service end matched with the service end identification information as a second service end bound with the first service end;
and if not, establishing a service end matched with the service end identification information in the service platform to serve as the second service end.
Optionally, the service end binding module is specifically adapted to:
matching the service end name and/or the service end address of each service end with name information and/or address information contained in the service end identification information respectively, and judging whether a service end matched with the service end identification information is created according to a matching result;
the matching priority of the service end address is higher than that of the service end name.
Optionally, if the first service end and the second service end have service type identifiers, the service module is specifically adapted to:
determining a second service end bound with a first service end of the target object configured in the applet according to the service type identifier;
wherein, the service type identifier comprises: merchant class service identification and/or aggregate payment class service identification.
Optionally, the target object is a merchant object, and the service end is a store service end affiliated to the merchant object.
The specific structure and the working principle of each module may refer to the description of the corresponding part of the method embodiment, and are not described herein again.
Example four
An embodiment of the present application provides a non-volatile computer storage medium, where the computer storage medium stores at least one executable instruction, and the computer executable instruction may execute the method for implementing the service based on the applet in any method embodiment. The executable instructions may be specifically configured to cause a processor to perform respective operations corresponding to the above-described method embodiments.
EXAMPLE five
Fig. 4 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.
As shown in fig. 4, the electronic device may include: a processor (processor)402, a Communications Interface 406, a memory 404, and a Communications bus 408.
Wherein:
the processor 402, communication interface 406, and memory 404 communicate with each other via a communication bus 408.
A communication interface 406 for communicating with network elements of other devices, such as clients or other servers.
The processor 402 is configured to execute the program 410, and may specifically execute relevant steps in the above-described method embodiment for implementing a service based on an applet.
In particular, program 410 may include program code comprising computer operating instructions.
The processor 402 may be a central processing unit CPU or an application Specific Integrated circuit asic or one or more Integrated circuits configured to implement embodiments of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 404 for storing a program 410. The memory 404 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 510 may be specifically configured to enable the processor 502 to execute the corresponding operations in the above method embodiments.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose devices may be used with the teachings herein. The required structure for constructing such a device will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in an apparatus according to an embodiment of the invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (10)
1. A method for implementing services based on applets, comprising:
detecting a service request associated with a first service end of a target object configured in an applet;
inquiring account number binding relation and service end binding relation stored in a background database, and determining a second service end which is bound with a first service end configured in the applet of the target object and is created in a service platform in advance;
And the first service end calls each service component in the second service end to provide services.
2. The method of claim 1, wherein the first service invoking each service component in the second service to provide services comprises:
the first service end calls an information pushing assembly in the second service end to realize information pushing operation;
and/or the first service end calls a payment component in the second service end to realize payment operation.
3. The method according to claim 1 or 2, wherein the detecting of the service request associated with the first service end of the target object configured in the applet specifically comprises:
when a login request triggered by the target object through a first object account is detected, a second object account bound with the first object account is logged in according to the account binding relationship;
the method further comprises the following steps: and starting the second service terminal according to the second object account.
4. The method according to any one of claims 1 to 3, wherein the determining a second service terminal created in the service platform in advance and bound to the first service terminal configured by the target object in the applet comprises:
Acquiring service end identification information of a first service end, and judging whether a service end matched with the service end identification information is established in a service platform;
and if so, taking the service end matched with the service end identification information as a second service end bound with the first service end.
5. The method of claim 4, wherein the method further comprises:
and if the service end matched with the service end identification information is not created in the service platform, creating a second service end bound with the first service end in the service platform.
6. The method of claim 5, wherein the creating a second service end bound with the first service end in the service platform comprises:
binding a first identifier of the first service end and a second identifier of the second service end;
and acquiring service data corresponding to the first service end, and establishing a mapping relation between the second identifier and the service data so that the second service end calls the service data based on the mapping relation.
7. The method of claim 4, wherein the determining whether a service end matching the service end identification information has been created in the service platform comprises:
Matching the service end name and/or the service end address of each service end with name information and/or address information contained in the service end identification information respectively, and judging whether a service end matched with the service end identification information is created according to a matching result;
the matching priority of the service end address is higher than that of the service end name.
8. An applet-based device that implements a service, comprising:
means for detecting a service request associated with a first service configured by a target object in an applet;
a module for inquiring the account number binding relationship and the service end binding relationship stored in a background database, and determining a second service end which is bound with a first service end configured in the applet for the target object and is created in the service platform in advance;
and the module is used for enabling the first service end to call each service component in the second service end to provide services.
9. A computing device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the corresponding operation of the method for realizing the service based on the small program according to any one of claims 1-7.
10. A computer storage medium having stored therein at least one executable instruction for causing a processor to perform operations corresponding to the applet based method for implementing a service as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110571511.9A CN113242310B (en) | 2020-06-30 | 2020-06-30 | Method and device for realizing service based on applet |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010613947.5A CN111770184B (en) | 2020-06-30 | 2020-06-30 | Method and device for realizing service based on small program |
| CN202110571511.9A CN113242310B (en) | 2020-06-30 | 2020-06-30 | Method and device for realizing service based on applet |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010613947.5A Division CN111770184B (en) | 2020-06-30 | 2020-06-30 | Method and device for realizing service based on small program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113242310A true CN113242310A (en) | 2021-08-10 |
| CN113242310B CN113242310B (en) | 2024-04-12 |
Family
ID=72723524
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110571511.9A Active CN113242310B (en) | 2020-06-30 | 2020-06-30 | Method and device for realizing service based on applet |
| CN202010613947.5A Active CN111770184B (en) | 2020-06-30 | 2020-06-30 | Method and device for realizing service based on small program |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010613947.5A Active CN111770184B (en) | 2020-06-30 | 2020-06-30 | Method and device for realizing service based on small program |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN113242310B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112508640A (en) * | 2020-11-30 | 2021-03-16 | 北京百度网讯科技有限公司 | Commodity processing method and component, electronic equipment and computer readable medium |
| CN112560076B (en) * | 2021-02-23 | 2021-05-18 | 浙江口碑网络技术有限公司 | Program page display method and device, computer equipment and readable storage medium |
| CN113312055B (en) * | 2021-05-28 | 2023-02-24 | 支付宝（中国）网络技术有限公司 | Applet launching method, device and equipment |
| CN113660204B (en) * | 2021-07-09 | 2024-01-23 | 北京航天云路有限公司 | Method for realizing unified integrated binding service |
| CN116664120B (en) * | 2023-06-15 | 2024-05-24 | 山东烟台烟草有限公司 | Method and system for realizing unique identification of consumer identity across payment channels |
| CN117933881A (en) * | 2024-01-25 | 2024-04-26 | 杭州认养一头牛智能科技有限公司 | Milk distribution control method, device, equipment and medium based on small program |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107645473A (en) * | 2016-07-20 | 2018-01-30 | 平安科技（深圳）有限公司 | The method and apparatus of data security protecting |
| CN108282392A (en) * | 2017-01-06 | 2018-07-13 | 网讯电通股份有限公司 | Business-binding system applied to communication software |
| CN108279986A (en) * | 2017-12-29 | 2018-07-13 | 亿阳安全技术有限公司 | A kind of distributed transaction processing method and device |
| CN109597640A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | A kind of account management method of application program, device, equipment and medium |
| CN109600349A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | A kind of shared implementation method, device, equipment and the medium of business datum |
| WO2019149049A1 (en) * | 2018-02-02 | 2019-08-08 | 华为技术有限公司 | Service processing method, terminal, server, and related product |
| CN111078424A (en) * | 2019-11-25 | 2020-04-28 | 苏州亿歌网络科技有限公司 | Information interaction method and device, computer equipment and storage medium |
| CN111131052A (en) * | 2019-12-20 | 2020-05-08 | 网易（杭州）网络有限公司 | Method and device for updating routing information |
| CN111160845A (en) * | 2019-12-06 | 2020-05-15 | 中国建设银行股份有限公司 | Service processing method and device |
| CN111260465A (en) * | 2020-01-20 | 2020-06-09 | 深圳乐信软件技术有限公司 | Business processing method, device, server and storage medium |
| CN111258565A (en) * | 2020-01-21 | 2020-06-09 | 深圳乐信软件技术有限公司 | Method, system, server and storage medium for generating small program |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060230136A1 (en) * | 2005-04-12 | 2006-10-12 | Kenneth Ma | Intelligent auto-archiving |
| CN108234505B (en) * | 2018-01-15 | 2020-08-04 | 口碑(上海)信息技术有限公司 | Account login method and system |
| CN108416195B (en) * | 2018-02-27 | 2020-09-25 | 平安科技（深圳）有限公司 | Cross-platform user authority management method and device, computer equipment and storage medium |
| CN109218402A (en) * | 2018-08-02 | 2019-01-15 | 胡雄风 | Hold cloud integrative solution |
| CN109118398A (en) * | 2018-08-10 | 2019-01-01 | 程龙兰 | A kind of commercial operation pattern having both psychological health education training and psychological consultation |
| CN109785478A (en) * | 2018-12-17 | 2019-05-21 | 珠海太川云社区技术股份有限公司 | Intelligent access control system and access control method based on small routine |
| CN109816825A (en) * | 2018-12-30 | 2019-05-28 | 重庆通宿科技有限责任公司 | Shared accommodation platform cloud lock system |
| CN109816380A (en) * | 2019-01-29 | 2019-05-28 | 河南紫云云计算股份有限公司 | Food and medicine digitlization delivery method and system are realized based on two dimensional code and H5 technology |
| CN110879728A (en) * | 2019-11-18 | 2020-03-13 | 口碑(上海)信息技术有限公司 | Method and device for starting small program |
-
2020
- 2020-06-30 CN CN202110571511.9A patent/CN113242310B/en active Active
- 2020-06-30 CN CN202010613947.5A patent/CN111770184B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107645473A (en) * | 2016-07-20 | 2018-01-30 | 平安科技（深圳）有限公司 | The method and apparatus of data security protecting |
| CN108282392A (en) * | 2017-01-06 | 2018-07-13 | 网讯电通股份有限公司 | Business-binding system applied to communication software |
| CN108279986A (en) * | 2017-12-29 | 2018-07-13 | 亿阳安全技术有限公司 | A kind of distributed transaction processing method and device |
| WO2019149049A1 (en) * | 2018-02-02 | 2019-08-08 | 华为技术有限公司 | Service processing method, terminal, server, and related product |
| CN109597640A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | A kind of account management method of application program, device, equipment and medium |
| CN109600349A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | A kind of shared implementation method, device, equipment and the medium of business datum |
| CN111078424A (en) * | 2019-11-25 | 2020-04-28 | 苏州亿歌网络科技有限公司 | Information interaction method and device, computer equipment and storage medium |
| CN111160845A (en) * | 2019-12-06 | 2020-05-15 | 中国建设银行股份有限公司 | Service processing method and device |
| CN111131052A (en) * | 2019-12-20 | 2020-05-08 | 网易（杭州）网络有限公司 | Method and device for updating routing information |
| CN111260465A (en) * | 2020-01-20 | 2020-06-09 | 深圳乐信软件技术有限公司 | Business processing method, device, server and storage medium |
| CN111258565A (en) * | 2020-01-21 | 2020-06-09 | 深圳乐信软件技术有限公司 | Method, system, server and storage medium for generating small program |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111770184B (en) | 2021-03-30 |
| CN111770184A (en) | 2020-10-13 |
| CN113242310B (en) | 2024-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111770184B (en) | Method and device for realizing service based on small program | |
| CN109547570B (en) | Service registration method, device, registration center management equipment and storage medium | |
| CN108234505B (en) | Account login method and system | |
| CN111464380B (en) | Method, device and system for parallel testing of multiple service items | |
| CN111639279B (en) | Graphic code generation method, target page loading method and device | |
| CN110738479B (en) | Order management method and system based on multi-person ordering | |
| CN111262897B (en) | Service call routing processing method, device and system | |
| CN110728505A (en) | Payment method, server, client and system based on multi-person order ordering | |
| CN112187934A (en) | Micro-service building method | |
| CN111523067A (en) | Page style processing method and device, storage medium and computer equipment | |
| CN111078424A (en) | Information interaction method and device, computer equipment and storage medium | |
| CN111443918A (en) | Channel access method and device for business object installation package | |
| CN106685708B (en) | Method, device and system for determining service relationship | |
| CN114640657A (en) | Multi-registration center fusion method and device | |
| CN110874365A (en) | Information query method and related equipment thereof | |
| CN110706070A (en) | Multi-user order ordering method, server, client and system | |
| CN113220453B (en) | Method and device for initiating transaction in blockchain system | |
| CN114048028A (en) | Service calling method and device, storage medium and electronic equipment | |
| CN116225549A (en) | Resource loading method, device, medium and equipment | |
| CN110162278B (en) | Adding method and device of built-in printer of POS machine | |
| JP5530893B2 (en) | Function expansion method of service providing system | |
| CN106790481A (en) | Equipment room data transmission method, device, server and computer-readable storage medium | |
| CN113536342A (en) | Block chain-based evidence storage management method, system, program product and storage medium | |
| CN111563183A (en) | Automatic generation method and device of visit record, computing equipment and storage medium | |
| CN112001800A (en) | Method and device for processing service in block chain system |
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 |