CN112492043A - Service notification method and device - Google Patents
Service notification method and device Download PDFInfo
- Publication number
- CN112492043A CN112492043A CN202011445398.1A CN202011445398A CN112492043A CN 112492043 A CN112492043 A CN 112492043A CN 202011445398 A CN202011445398 A CN 202011445398A CN 112492043 A CN112492043 A CN 112492043A
- Authority
- CN
- China
- Prior art keywords
- service
- notification
- user
- delivery
- information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 235000012054 meals Nutrition 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
-
- 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/55—Push-based network services
Abstract
The disclosure relates to a service notification method and a device, wherein the method comprises the following steps: receiving a notification request corresponding to at least one service sent by a client, wherein the notification request carries service identifiers corresponding to the at least one service respectively; and respectively acquiring the contact information of the user corresponding to the at least one service according to the service identification, and contacting the user for service notification according to the contact information. The method and the device for notifying the service obviously improve the efficiency of service notification.
Description
Technical Field
The present disclosure relates to network technologies, and in particular, to a service notification method and apparatus.
Background
With the development of network technology, users are also gradually performing various services on the network. For example, the user may shop on the web, order for a takeout on the web, etc. With the increase of the online businesses of users, distributors for delivering various business products to the users have appeared, such as couriers for delivering express, takeout, and the like. When a distributor sends a business product (such as meal or express) of a user to a user position, the user is usually required to be notified to fetch, and an event that the distributor notifies the user can be called a business notification; in addition, in most cases, the product delivered by the dispenser is not only one user, but also products from a plurality of users may be delivered simultaneously, and the dispenser needs to notify the users one by one to fetch their products, which is inefficient.
Disclosure of Invention
In order to overcome the problems in the related art, the present disclosure provides a service notification method and apparatus to improve the efficiency of service notification.
According to a first aspect of the embodiments of the present disclosure, a service notification method is provided, including:
receiving a notification request corresponding to at least one service sent by a client, wherein the notification request carries service identifiers corresponding to the at least one service respectively;
and respectively acquiring the contact information of the user corresponding to the at least one service according to the service identification, and contacting the user for service notification according to the contact information.
According to a second aspect of the embodiments of the present disclosure, there is provided a service notification method, including:
receiving a notification trigger corresponding to at least one service;
and sending a notification request corresponding to the at least one service to a server according to the notification trigger, wherein the notification request carries service identifiers corresponding to the at least one service respectively, so that the server contacts a user of the at least one service according to the service identifiers to perform service notification.
According to a third aspect of the embodiments of the present disclosure, there is provided a service notification apparatus, including:
the request receiving module is used for receiving a notification request which is sent by a client and corresponds to at least one service, wherein the notification request carries service identifiers respectively corresponding to the at least one service;
and the notification execution module is used for respectively acquiring the contact information of the user corresponding to the at least one service according to the service identifier and contacting the user to perform service notification according to the contact information.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a service notification apparatus, including:
a trigger receiving module, configured to receive a notification trigger corresponding to at least one service;
and the request sending module is used for sending a notification request corresponding to the at least one service to the server according to the notification trigger, wherein the notification request carries service identifiers respectively corresponding to the at least one service, so that the server contacts a user of the at least one service according to the service identifiers to perform service notification.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: by contacting the users of at least one service in parallel to perform service notification when receiving the notification request of at least one service, the efficiency of service notification is remarkably improved compared with a one-by-one notification mode.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a system architecture of a business notification application, shown in accordance with an exemplary embodiment;
FIG. 2 is a flow diagram illustrating a method of service notification in accordance with an exemplary embodiment;
FIG. 3 is a flow diagram illustrating another method of service notification in accordance with an exemplary embodiment;
FIG. 4 is a flow chart illustrating yet another method of traffic notification in accordance with an exemplary embodiment;
FIG. 5 is a flow chart illustrating yet another method of traffic notification in accordance with an exemplary embodiment;
FIG. 6 is a schematic diagram illustrating the structure of a traffic notification apparatus in accordance with an exemplary embodiment;
fig. 7 is a schematic diagram illustrating the structure of another traffic notification apparatus according to an example embodiment;
fig. 8 is a schematic structural diagram illustrating yet another traffic notification apparatus according to an exemplary embodiment;
fig. 9 is a schematic structural diagram illustrating yet another traffic notification apparatus according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
The service notification method provided by the present disclosure may be executed by a system including a client 11 and a server 12 shown in fig. 1, and as shown in fig. 1, the client 11 may display a plurality of services, such as an exemplary service 1, a service 2, and a service 3. For example, the services displayed on the client 11 may be delivery services, such as delivery take-out, or delivery of couriers, which are delivered by a deliverer for a user. The client 11 may be located on a hand-held terminal of the dispenser. Moreover, the service notification of the present disclosure, that is, the distributor sends the service product (for example, the service product may be a takeout meal ordered by the user or an express item purchased by the user) corresponding to each service to the user, needs to notify, through the client 11, that the service of the user corresponding to each service is completed. For example, when the delivery service is a takeaway order of a takeaway service, the service notification may be used to prompt that a user meal corresponding to the takeaway order has been sent to an address specified by the user, and notify the user to take the meal; and, the service notification in the delivery service scenario may be referred to as a delivery service notification.
In order to implement the service notification, the client 11 may execute the flow of the service notification method illustrated in fig. 2, and the server 12 may execute the flow of the service notification method illustrated in fig. 3. It should be noted that the service notification method described in fig. 2 and fig. 3 may be applied to various service scenarios including a delivery service, for example, in a delivery service scenario, the service notification method may be used to perform a delivery service notification, notify a corresponding user to fetch a meal or take an express, and in other service scenarios, the method may also be used.
201. A notification trigger corresponding to at least one service is received.
202. And sending a notification request corresponding to the at least one service to a server according to the notification trigger, wherein the notification request carries service identifiers corresponding to the at least one service respectively, so that the server contacts a user of the at least one service according to the service identifiers to perform service notification.
301. Receiving a notification request corresponding to at least one service sent by a client, wherein the notification request carries service identifiers corresponding to the at least one service respectively.
302. And respectively acquiring the contact information of the user corresponding to the at least one service according to the service identification, and contacting the user to perform service notification according to the contact information.
As described in conjunction with fig. 2 and 3, in step 201, the client 11 may receive a notification trigger corresponding to at least one service. For example, the distributor may click and select a certain service by means of manual triggering, or each service correspondingly displays a button for triggering the sending of the notification request on the display interface of the client 11, so that the distributor may manually select the trigger button corresponding to the service to trigger the client 11 to send the notification request corresponding to the service to the server 12. The client in this step receives the notification trigger, which may be a button that is clicked by the distributor, and the distributor may click a button of at least one service, for example, all three services in fig. 1 need to perform service notification.
Optionally, when the distributor performs notification triggering, each service may be triggered one by one, or multiple services may be triggered at a time. For example, on the display interface of the client 11, a button for triggering the sending of the notification request may be displayed for each service, and the distributor may click the button one by one, for example, may click and trigger one of the services, or click and trigger multiple services one by one, for example, when the service is a distribution service, the notification request corresponding to each distribution service may be sent to the server one by one according to the notification trigger of each distribution service. Alternatively, a "one-touch" similar function button may be displayed on the interface, and the dispatcher clicking on the button may trigger multiple services to make notification requests simultaneously.
In step 202, the client 11 sends a notification request to the server 12, where the notification request is used to instruct the server 12 to notify the service to the users corresponding to the services. The request may carry service identifiers corresponding to the services, for example, a takeaway service, then a plurality of services displayed by the client 11 on the hand-held terminal of the distributor may be take the takeaway orders, and then the notification request may carry information for identifying the orders, such as order numbers.
Optionally, for multiple services, if the client 11 sends corresponding notification requests to each service, each request may carry a service identifier of the corresponding service. If the client 11 sends a request for requesting notification of multiple services, the request may carry service identifiers of the multiple services. That is, when sending a notification request for triggering at least one delivery service simultaneously to the server, the notification request may be sent, where the request carries a service identifier of the at least one delivery service.
The server 12 may receive a notification request sent by the client 11 in step 301, where the notification request corresponds to at least one service, and when there are notification requests corresponding to multiple services, the multiple services may be multiple services sent by the same client, or may also be multiple services sent by multiple clients. In step 302, in order to perform service notification on the user corresponding to each service, the server 12 may obtain user contact information corresponding to the service according to the service identifier carried in the notification request, and contact multiple users according to the contact information to perform service notification. For example, when there are multiple services, the users corresponding to the multiple services may be contacted in parallel to perform service notification.
For example, still taking a takeaway service as an example, a plurality of takeaway orders may be displayed in the client 11, and after a delivery arrives, the deliverer may click a trigger button corresponding to an order that needs to be notified, so that the client 11 may send a notification request of the orders to the server 12, and a service identifier carried in the request may be an order number. The server 12 may obtain a contact information of the user corresponding to the order according to the order number, where the contact information is a mobile phone number as an example. The server 12 can dial the mobile phone numbers of the users of multiple orders in parallel to notify, and the notification mode can be a voice prompt that "you order take a meal when you are delivered. In specific implementation, the cloud call center of the server side can perform parallel calling of a plurality of users.
The service notification method of this embodiment may initiate notification of multiple services in parallel, and may contact users corresponding to multiple services in parallel, so that efficiency of service notification is significantly improved compared with a conventional method in which a distributor needs to contact users one by one.
Fig. 4 illustrates another flow of the service notification method of the present disclosure, in this example, in order to give a clearer and more accurate prompt to the user, the user is also enabled to better know which service is currently notified, so that the user can better confirm whether the service notification is the service of the user, and the server can refine the prompt information when prompting the user. For example, the service end may further obtain service information corresponding to each service according to the service identifier carried in the notification request, and prompt the corresponding service information to the user when contacting multiple users for service notification according to the contact information.
Wherein, the service information includes but is not limited to: service provider information, address information involved in the service, etc. For example, taking a delivery takeout service as an example, when a user orders a takeout meal, the server may obtain where the takeout meal is to be sent, that is, a takeout meal delivery address, a mobile phone number of the user, a store where the user orders the meal, and the like, where the takeout order is a delivery service, and order information related to the takeout order obtained by the server may be referred to as service information.
As shown in fig. 4, the process may be executed by the server, and may include:
in step 401, the server receives a notification request sent by the client, and carries a service identifier.
For example, in the step of taking the takeaway service as an example, the server 12 may receive a notification request sent by the client 11, and the request may carry order numbers of a plurality of takeaway orders.
In step 402, the server obtains contact information of users corresponding to a plurality of services and service provider information according to the service identifiers.
In this step, the server may obtain service information corresponding to the service according to the service identifier, so as to prompt the service information to the user in the subsequent steps. For example, in a delivery service for take-out, the server may obtain service information, which is order information corresponding to a plurality of orders to be notified of the service, based on the order number, and may obtain a destination address to which the order is to be sent or a take-out store, for example. In this example, the service side acquires the service provider information, that is, the store information providing the takeout service, for example, the store name "a certain bunk". The server also obtains contact information of the user, such as a mobile phone number of the user. The mobile phone numbers and the shop information can be acquired by the server side when the user places a takeout order.
In step 403, the server converts the service provider information from a text format to a voice format.
For example, in this step, the server may perform text-to-speech format conversion. For example, the store information of the take-out service may be stored in text format at the service end, in this example, converted to speech. For example, "you order a shop" to send the going-out of the shop and please take a meal from the next building ", wherein the shop" may be obtained by format conversion in this step, and the information other than the shop in the prompting information may be preset voice, and the user may be prompted by adding the converted shop voice.
In step 404, the server contacts a plurality of users for service notification according to the contact information, and also prompts the service provider information of the corresponding service to the users by voice.
For example, for a certain order, the server may dial its mobile phone number to the user placing the order, and after the user answers the phone, make a voice prompt to the user that "you ordered the take-out of the store is reached, please take a meal down the floor", both prompting the user that the meal is reached and also prompting which store.
In the service notification method of the embodiment, when the service notification is performed on the user, the notification information is refined, so that the user can obtain more detailed and accurate notification information; moreover, the embodiment adopts a text-to-speech mode, can adapt to different information of different services, and is convenient to apply.
Fig. 5 illustrates another flow of the service notification method of the present disclosure, and in this example, after the service notification is performed on the user by the server, how to feed back the service notification result to the client, so that the distributor can know whether each user receives the service notification in time through the client. As shown in fig. 5, this embodiment may include the following flow, wherein the steps already described are not detailed again:
in step 501, the client sends a notification request to the server, carrying a service identifier.
In step 502, the server obtains the user contact information and the service provider information according to the service identifier, and converts the text to voice of the service provider information.
In step 503, the server notifies the user of the service according to the contact information and the service provider information, for example, performs a voice prompt on the user to prompt the user that the service has been executed.
In step 504, the server determines whether the user has acquired the service notification.
For example, the server may dial a mobile phone to the user, and may also detect whether the user answers the mobile phone; when the user answers the mobile phone, the voice service notice is played to the user. Therefore, the server can detect whether the user has acquired the service notification.
For example, it may be assumed that the user answers the phone call made by the server to the user's mobile phone, and the answering time reaches 10 seconds, it may be determined that the user has obtained the service notification, for example, the user has heard the voice prompt and knows that the self take-away meal has been sent. For another example, it may be assumed that the user does not answer the call at all, or even if the call is answered but the answering time is only 2 seconds, the user may be considered as not acquiring the service notification.
In this step, if the determination result is that the user obtains the service notification corresponding to the service, step 505 and step 506 may be executed; otherwise, if the determination result is that the user does not obtain the service notification corresponding to the service, step 507 and step 508 may be executed.
In step 505, the server feeds back the first status information notifying success to the client.
In step 506, the client obtains that the user has successfully notified according to the first status information, and then closes the notification request function corresponding to the service.
For example, the client may graying out a trigger button corresponding to the notification request of the service, so that the dispatcher cannot select triggering any more, thereby preventing the user from being harassed by repeated dialing by the dispatcher, and the graying out of the button may also enable the dispatcher to know that the notification of the service is successful.
In step 507, the server feeds back the second status information notifying the failure to the client.
In step 506, the client performs a prompt for a service re-notification request according to the second status information. For example, the order is prompted to the distributor, and the user of a certain order does not answer the call and does not redial. The way of prompting the distributor can be various, for example, the color of the trigger button corresponding to the service can be changed, and the green color is used for indicating the non-answering; or, a text prompt of non-answering can be directly displayed on the button, and the like, so that the distributor can timely know that a certain order needs to be notified again.
In the service notification method of the embodiment, the server notifies the client of the result of the service notification, and the client performs different prompts according to the result, so that the distributor can timely know whether the service notification of each service is received by the user, and can notify the user again as soon as possible when the service notification is not received.
The method described above is illustrated by taking a takeaway example as an example, but it is understood that the method is not limited to the application scenario, and the method may be applied to other scenarios, such as an express delivery application.
In order to execute the service notification method of the present disclosure, the present disclosure further provides a service notification apparatus, and as follows, the structure of the apparatus is briefly described, and specific principles may be combined with reference to the method embodiment. As shown in fig. 6, the service notification apparatus may be applied to a server, and may include: a request receiving module 61 and a notification execution module 62, wherein:
a request receiving module 61, configured to receive a notification request corresponding to at least one service and sent by a client, where the notification request carries service identifiers corresponding to the at least one service respectively;
and a notification execution module 62, configured to obtain, according to the service identifier, contact information of a user corresponding to the at least one service, respectively, and contact the user to perform service notification according to the contact information. The notification execution module 62 may further obtain service information corresponding to the at least one service according to the service identifier, and prompt the user about the service information of the corresponding service when the user is contacted to perform service notification.
When the service is a delivery service, the request receiving module may be specifically configured to receive a notification request corresponding to at least one delivery service, where the notification request is sent by a client on a deliverer terminal, and the notification request includes a service identifier corresponding to the delivery service. The notification execution module may be specifically configured to obtain, according to the service identifier, contact information of at least one user corresponding to the at least one delivery service, respectively, and contact the at least one user for delivering the service notification according to the contact information by voice.
Further, as shown in fig. 7, the apparatus at the server may further include: a state feedback module 63 configured to perform at least one of the following functions:
for one service, if it is detected that a user acquires a service notification corresponding to the service, feeding back first state information indicating success to the client, so that the client closes a notification request function corresponding to the service;
or, for one of the services, if it is detected that the user does not obtain the service notification corresponding to the service, feeding back second state information of notification failure to the client, so that the client performs a prompt for requesting to notify the service again.
Further, the apparatus may further include: an information conversion module 64.
An information conversion module 64, configured to obtain, according to the service identifier, service provider information corresponding to the at least one service, respectively, and convert the service provider information from a text format to a voice format;
the notification execution module 62 is further configured to prompt the user with voice information about a service provider of a corresponding service when the user is contacted to perform service notification according to the contact information.
Fig. 8 illustrates a service notification apparatus applied to a client, and as shown in fig. 8, the apparatus may include: a trigger receiving module 81 and a request sending module 82.
A trigger receiving module 81, configured to receive a notification trigger corresponding to at least one service;
a request sending module 82, configured to send, according to the notification trigger, a notification request corresponding to the at least one service to a server, where the notification request carries service identifiers corresponding to the at least one service, so that the server contacts a user of the at least one service to perform service notification according to the service identifiers. The service identifier can also enable the server to respectively obtain the service information corresponding to the at least one service according to the service identifier, and enable the server to prompt the service information of the corresponding service to the user when the server notifies the user of the service.
When the service is a delivery service, the trigger receiving module may be specifically a notification trigger for receiving at least one delivery service. The request sending module may be specifically configured to send, according to the notification trigger, a notification request corresponding to the at least one delivery service to a server of the delivery service, where the notification request carries a service identifier corresponding to the delivery service, so that the server obtains, according to the service identifier, contact information of at least one user corresponding to the at least one delivery service respectively and contacts the at least one user to perform a delivery service notification according to the contact information by voice.
Further, as shown in fig. 9, the apparatus may include:
a first state receiving module 83, configured to receive first state information, which is sent by the server and corresponds to one of the services, where the first state information is used to indicate that the server successfully notifies a user service corresponding to the service;
a first function management module 84, configured to close a notification request function corresponding to the service according to the first status information.
Further, the apparatus may further include: a second state receiving module 85, configured to receive second state information, which is sent by the server and corresponds to one of the services, where the second state information is used to indicate that the service has failed to notify a user service corresponding to the service;
and the second function management module 86 is configured to execute a prompt for the service re-notification request according to the second state information.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (14)
1. A method for notifying delivery services, the method comprising:
receiving a notification request corresponding to at least one delivery service sent by a client on a distributor terminal, wherein the notification request comprises a service identifier corresponding to the delivery service;
respectively acquiring contact information of at least one user corresponding to the at least one distribution service according to the service identifier;
and according to the contact information, the at least one user is contacted by voice to carry out delivery service notification.
2. The method of claim 1,
the delivery service is a take-out order of a take-out service;
and the delivery service notification is used for notifying a user corresponding to the takeout order to take the meal.
3. The method of claim 1, wherein said voice contacting said at least one user for delivery of a service notification based on said contact information comprises:
and performing voice contact on at least one user corresponding to the at least one delivery service in parallel.
4. The method of claim 1, further comprising, after the at least one user is contacted by voice for delivery of the service notification based on the contact information:
for one of the delivery services, if it is detected that a user acquires a delivery service notification corresponding to the delivery service, feeding back first state information indicating success to the client, so that the client closes a notification request function corresponding to the delivery service.
5. The method of claim 1, further comprising, after the at least one user is contacted by voice for delivery of the service notification based on the contact information:
for one of the delivery services, if it is detected that the user does not obtain a delivery service notification corresponding to the delivery service, feeding back second state information of notification failure to the client, so that the client performs prompt for requesting the delivery service to notify the delivery service again.
6. A method for delivery service notification, the method comprising:
receiving a notification trigger corresponding to at least one distribution service;
and sending a notification request corresponding to the at least one distribution service to a service end of the distribution service according to the notification trigger, wherein the notification request carries a service identifier corresponding to the distribution service, so that the service end respectively acquires contact information of at least one user corresponding to the at least one distribution service according to the service identifier and contacts the at least one user to carry out service distribution notification according to the contact information by voice.
7. The method of claim 6, wherein the sending a notification request corresponding to the at least one delivery service to a server of the delivery service according to the notification trigger comprises:
according to the notification trigger of each distribution service, sending notification requests corresponding to each distribution service to the server one by one;
or sending a notification request for triggering the at least one delivery service simultaneously to the server.
8. A method of traffic notification, the method comprising:
receiving a notification request corresponding to at least one service sent by a client, wherein the notification request carries service identifiers corresponding to the at least one service respectively;
respectively acquiring contact information of at least one user corresponding to the at least one service according to the service identifier, and respectively acquiring service information corresponding to the at least one service;
and contacting the at least one user for service notification according to the contact information, and prompting the service information of the corresponding service to the user.
9. The method of claim 8, wherein the service information comprises: service provider information; the contacting the at least one user for service notification according to the contact information and prompting the service information of the corresponding service to the user includes:
converting the service provider information from a text format to a voice format;
and when the at least one user is contacted for service notification, service provider information of the corresponding service is prompted to the user by voice.
10. A method of traffic notification, the method comprising:
receiving a notification trigger corresponding to at least one service;
and sending a notification request corresponding to the at least one service to a server according to the notification trigger, wherein the notification request carries service identifiers corresponding to the at least one service respectively, so that the server acquires service information corresponding to the at least one service and contact information of at least one user respectively according to the service identifiers, contacts the at least one user according to the contact information for service notification, and prompts the service information of the corresponding service to the user.
11. An apparatus for notifying delivery of a service, the apparatus comprising:
the system comprises a request receiving module, a service identification module and a service identification module, wherein the request receiving module is used for receiving a notification request which is sent by a client on a distributor terminal and corresponds to at least one distribution service, and the notification request comprises the service identification corresponding to the distribution service;
and the notification execution module is used for respectively acquiring the contact information of at least one user corresponding to the at least one distribution service according to the service identifier and contacting the at least one user to carry out distribution service notification according to the contact information by voice.
12. A delivery service notification apparatus, comprising:
a trigger receiving module, configured to receive a notification trigger corresponding to at least one delivery service;
and the request sending module is used for sending a notification request corresponding to the at least one delivery service to a server of the delivery service according to the notification trigger, wherein the notification request carries a service identifier corresponding to the delivery service, so that the server respectively acquires contact information of at least one user corresponding to the at least one delivery service according to the service identifier and contacts the at least one user to carry out delivery service notification according to the contact information by voice.
13. A traffic notification apparatus, comprising:
the request receiving module is used for receiving a notification request which is sent by a client and corresponds to at least one service, wherein the notification request carries service identifiers respectively corresponding to the at least one service;
a notification execution module, configured to respectively obtain contact information of at least one user corresponding to the at least one service according to the service identifier, and respectively obtain service information corresponding to the at least one service; and contacting the at least one user for service notification according to the contact information, and prompting the service information of the corresponding service to the user.
14. A traffic notification apparatus, comprising:
a trigger receiving module, configured to receive a notification trigger corresponding to at least one service;
and the request sending module is used for sending a notification request corresponding to the at least one service to a server according to the notification trigger, wherein the notification request carries service identifiers corresponding to the at least one service respectively, so that the server obtains service information corresponding to the at least one service and contact information of at least one user respectively according to the service identifiers, contacts the at least one user according to the contact information for service notification, and prompts the service information of the corresponding service to the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011445398.1A CN112492043A (en) | 2015-12-21 | 2015-12-21 | Service notification method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011445398.1A CN112492043A (en) | 2015-12-21 | 2015-12-21 | Service notification method and device |
| CN201510967567.0A CN106899485B (en) | 2015-12-21 | 2015-12-21 | Service notification method and device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510967567.0A Division CN106899485B (en) | 2015-12-21 | 2015-12-21 | Service notification method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112492043A true CN112492043A (en) | 2021-03-12 |
Family
ID=59191208
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510967567.0A Active CN106899485B (en) | 2015-12-21 | 2015-12-21 | Service notification method and device |
| CN202011445398.1A Pending CN112492043A (en) | 2015-12-21 | 2015-12-21 | Service notification method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510967567.0A Active CN106899485B (en) | 2015-12-21 | 2015-12-21 | Service notification method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN106899485B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111049938B (en) * | 2020-01-08 | 2022-10-18 | 贵阳货车帮科技有限公司 | Message notification method and device, electronic equipment and readable storage medium |
| CN113222198A (en) * | 2020-02-04 | 2021-08-06 | 北京京东振世信息技术有限公司 | Reservation method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103577959A (en) * | 2013-11-11 | 2014-02-12 | 中国联合网络通信集团有限公司 | Server, client terminal and merchandise distribution information pushing and identification method |
| JP2014228908A (en) * | 2013-05-20 | 2014-12-08 | 日立オムロンターミナルソリューションズ株式会社 | Takeout forgotten medium notification system |
| CN104636903A (en) * | 2015-02-13 | 2015-05-20 | 深圳支付界科技有限公司 | Method and system for automatically sending delivery information |
| CN105099889A (en) * | 2015-07-24 | 2015-11-25 | 拉扎斯网络科技（上海）有限公司 | Order notification method, apparatus and system |
| CN105162867A (en) * | 2015-09-17 | 2015-12-16 | 百度在线网络技术（北京）有限公司 | Notification method and device for delivery arrival |
| CN105162870A (en) * | 2015-09-18 | 2015-12-16 | 成都身边科技有限公司 | Express delivery notification method, device and system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101179626A (en) * | 2007-05-30 | 2008-05-14 | 华为技术有限公司 | Device, method and system for implementing hang-off notification service |
| CN101217725A (en) * | 2007-12-26 | 2008-07-09 | 深圳华为通信技术有限公司 | Incoming call display method and device |
| JP5261454B2 (en) * | 2010-08-27 | 2013-08-14 | 京セラ株式会社 | Telephone and telephone number registration method |
| CN103634195A (en) * | 2012-08-22 | 2014-03-12 | 中兴通讯股份有限公司 | Communication method and device |
| CN104135515B (en) * | 2014-07-25 | 2018-05-01 | 北京奇虎科技有限公司 | Service providing method and device |
-
2015
- 2015-12-21 CN CN201510967567.0A patent/CN106899485B/en active Active
- 2015-12-21 CN CN202011445398.1A patent/CN112492043A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2014228908A (en) * | 2013-05-20 | 2014-12-08 | 日立オムロンターミナルソリューションズ株式会社 | Takeout forgotten medium notification system |
| CN103577959A (en) * | 2013-11-11 | 2014-02-12 | 中国联合网络通信集团有限公司 | Server, client terminal and merchandise distribution information pushing and identification method |
| CN104636903A (en) * | 2015-02-13 | 2015-05-20 | 深圳支付界科技有限公司 | Method and system for automatically sending delivery information |
| CN105099889A (en) * | 2015-07-24 | 2015-11-25 | 拉扎斯网络科技（上海）有限公司 | Order notification method, apparatus and system |
| CN105162867A (en) * | 2015-09-17 | 2015-12-16 | 百度在线网络技术（北京）有限公司 | Notification method and device for delivery arrival |
| CN105162870A (en) * | 2015-09-18 | 2015-12-16 | 成都身边科技有限公司 | Express delivery notification method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106899485B (en) | 2020-10-30 |
| CN106899485A (en) | 2017-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105139506B (en) | Number obtaining method, device, server-side and system based on positioning mobile terminal | |
| CN103841517B (en) | A kind of system and method for chauffeur information service | |
| USRE43205E1 (en) | Skill based chat function in a communication system | |
| CN107800901B (en) | User call processing method, device, computer equipment and storage medium | |
| CA2947242C (en) | Voice call diversion to alternate communication method | |
| US20140105374A1 (en) | Providing additional information to called parties | |
| US20170330557A1 (en) | Method and system for providing visual interactive voice response (ivr) to an enhanced visual call (evc) client device | |
| CN111010527B (en) | Method and related device for establishing video call through short message link | |
| US8600417B1 (en) | Consumer care system | |
| CN102859982A (en) | Establishing a call between a first user and a second user | |
| US8774391B1 (en) | Integrating embedded links with call center operation | |
| CN106899485B (en) | Service notification method and device | |
| CN103813036B (en) | Communication connection allocation method and system thereof | |
| JP2011502426A (en) | Method and system for automatically switching between free directory assistance service and paid directory assistance service | |
| US7729479B2 (en) | Automatic generation of mixed media messages | |
| RU2009149704A (en) | METHOD, SYSTEM AND DEVICE FOR SUBMISSION OF CALLING INFORMATION | |
| CN103200591A (en) | Method for processing mobile network call requests | |
| US20150271326A1 (en) | System and method for processing calls to an invalid called-to number | |
| CN107018243A (en) | A kind of call information processing method and device | |
| CN102694788A (en) | Method and system for providing client side remote service from server side | |
| CN103635878A (en) | Information distribution system and method thereof | |
| US8073130B2 (en) | Customer automated response system | |
| CN203942648U (en) | A kind of system of chauffeur information service | |
| CN109450870B (en) | VOIP service processing method and device, storage medium and electronic device | |
| JP2009094699A (en) | Telephone connection control system, server apparatus, server processing program, and telephone connection control method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210312 |