CN106899485B - Service notification method and device - Google Patents

Service notification method and device Download PDF

Info

Publication number
CN106899485B
CN106899485B CN201510967567.0A CN201510967567A CN106899485B CN 106899485 B CN106899485 B CN 106899485B CN 201510967567 A CN201510967567 A CN 201510967567A CN 106899485 B CN106899485 B CN 106899485B
Authority
CN
China
Prior art keywords
service
notification
server
information
client
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.)
Active
Application number
CN201510967567.0A
Other languages
Chinese (zh)
Other versions
CN106899485A (en
Inventor
张华�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN202011445398.1A priority Critical patent/CN112492043A/en
Priority to CN201510967567.0A priority patent/CN106899485B/en
Publication of CN106899485A publication Critical patent/CN106899485A/en
Application granted granted Critical
Publication of CN106899485B publication Critical patent/CN106899485B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Tourism & Hospitality (AREA)
  • Human Resources & Organizations (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

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

Service notification method and device
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, 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, and the client 11 may be located on a handheld terminal of a distributor. Moreover, the service notification of the present disclosure, that is, the distributor has sent the service product corresponding to each service to the user, needs to notify the user that the service corresponding to each service is completed through the client 11; for example, for a take-out service, it may be that the distributor should prompt the user of each order service that the meal has been sent to.
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.
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 one of the services, or click one by one to trigger multiple services; 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.
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 in parallel according to the contact information 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 and enable the user to better know which service is currently notified, the server may refine the prompt information when prompting the user. 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.
For example, the server may obtain the mobile phone numbers of users of a plurality of orders to be notified of the business according to the order numbers, and in this example, the server may also obtain business provider information, that is, store information providing a takeout service, such as a store name "a certain package of bunks". 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.
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.
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 (11)

1. A service notification method is applied to a server and comprises the following steps:
receiving a notification request corresponding to at least one service, which is sent by a service provider through a client, wherein the notification request carries service identifiers corresponding to the at least one service respectively;
respectively acquiring contact information of a plurality of users corresponding to the at least one service according to the service identification, and contacting the plurality of users according to the contact information to perform parallel service notification;
respectively acquiring service provider information corresponding to the at least one service according to the service identifier, and converting the service provider information from a text format into a voice format;
and when the plurality of users are contacted to carry out service notification according to the contact information, service provider information of the corresponding service is prompted to the plurality of users by voice.
2. The method of claim 1, further comprising, after contacting the plurality of users for a service notification according to the contact information:
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.
3. The method of claim 1, further comprising, after contacting the plurality of users for service notification based on the contact information:
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 prompt for requesting the service notification again.
4. A service notification method is applied to a client, and comprises the following steps:
receiving a notification trigger corresponding to at least one service from a service provider;
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 corresponding service provider information according to the service identifiers, converts the service provider information from a text format into a voice format, and contacts a plurality of users of the at least one service to send service notifications containing the service provider information converted into the voice format in parallel.
5. The method of claim 4, further comprising, after sending a notification request corresponding to the at least one service to a server:
receiving first state information corresponding to one of the services, which is sent by the server, wherein the first state information is used for indicating that the server successfully notifies a user service corresponding to the service;
and closing the notification request function corresponding to the service according to the first state information.
6. The method of claim 4, further comprising, after sending a notification request corresponding to the at least one service to a server:
receiving second state information corresponding to one of the services, which is sent by the server, wherein the second state information is used for indicating that the server fails to notify a user service corresponding to the service;
and executing prompt of the service re-notification request according to the second state information.
7. A service notification device is applied to a server side, and comprises:
the request receiving module is used for receiving a notification request which is sent by a service provider through a client and corresponds to at least one service, wherein the notification request carries service identifiers respectively corresponding to the at least one service;
the notification execution module is used for respectively acquiring the contact information of a plurality of users corresponding to the at least one service according to the service identification, and contacting the plurality of users according to the contact information to perform parallel service notification;
the information conversion module is used for respectively acquiring service provider information corresponding to the at least one service according to the service identification and converting the service provider information from a text format to a voice format;
the notification execution module is further configured to, when the plurality of users are contacted to perform service notification according to the contact information, further prompt the service provider information of the corresponding service to the plurality of users by voice.
8. The apparatus of claim 7, further comprising:
a state feedback module for performing 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.
9. A service notification device applied to a client side includes:
the trigger receiving module is used for receiving a notification trigger corresponding to at least one service from a service provider;
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 acquires corresponding service provider information according to the service identifiers, converts the service provider information from a text format into a voice format, and contacts a plurality of users of the at least one service to send service notifications containing the service provider information converted into the voice format in parallel.
10. The apparatus of claim 9, further comprising:
a first state receiving module, configured to receive first state information corresponding to one of the services, where the first state information is used to indicate that a user service corresponding to the service is successfully notified by the server;
and the first function management module is used for closing the notification request function corresponding to the service according to the first state information.
11. The apparatus of claim 9, further comprising:
a second state receiving module, 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 server fails to notify a user service corresponding to the service;
and the second function management module is used for executing prompt of the service re-notification request according to the second state information.
CN201510967567.0A 2015-12-21 2015-12-21 Service notification method and device Active CN106899485B (en)

Priority Applications (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

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510967567.0A CN106899485B (en) 2015-12-21 2015-12-21 Service notification method and device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202011445398.1A Division CN112492043A (en) 2015-12-21 2015-12-21 Service notification method and device

Publications (2)

Publication Number Publication Date
CN106899485A CN106899485A (en) 2017-06-27
CN106899485B true CN106899485B (en) 2020-10-30

Family

ID=59191208

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202011445398.1A Pending CN112492043A (en) 2015-12-21 2015-12-21 Service notification method and device
CN201510967567.0A Active CN106899485B (en) 2015-12-21 2015-12-21 Service notification method and device

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202011445398.1A Pending CN112492043A (en) 2015-12-21 2015-12-21 Service notification method and device

Country Status (1)

Country Link
CN (2) CN112492043A (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
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

Family Cites Families (11)

* Cited by examiner, † Cited by third party
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
JP2014228908A (en) * 2013-05-20 2014-12-08 日立オムロンターミナルソリューションズ株式会社 Takeout forgotten medium notification system
CN103577959B (en) * 2013-11-11 2018-02-02 中国联合网络通信集团有限公司 Server, client, the push of commodity distribution information and recognition methods
CN104135515B (en) * 2014-07-25 2018-05-01 北京奇虎科技有限公司 Service providing method and device
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
CN106899485A (en) 2017-06-27
CN112492043A (en) 2021-03-12

Similar Documents

Publication Publication Date Title
US9374459B1 (en) Integrating two-dimensional bar codes and embedded links with call center operation
US10812347B2 (en) Connected machine initiated service
CN105139506B (en) Number obtaining method, device, server-side and system based on positioning mobile terminal
US10673954B2 (en) Digital service interface
CN107800901B (en) User call processing method, device, computer equipment and storage medium
CN105184945B (en) The method, apparatus and system and server-side of a kind of queuing number-taking
CN104253910A (en) Interaction method and interaction system for voice service calls
US8600417B1 (en) Consumer care system
CN106899485B (en) Service notification method and device
CN109413285A (en) A kind of communication means and device
CN112769680A (en) Enterprise instant voice service center management method, system and storage medium
CN103813036B (en) Communication connection allocation method and system thereof
US10574814B2 (en) System and method for message redirection
CN102148904A (en) Method and device for processing call
CN103200591A (en) Method for processing mobile network call requests
CN107018243A (en) A kind of call information processing method and device
CN106375268A (en) Delivery calling method, server and terminal
US20150271326A1 (en) System and method for processing calls to an invalid called-to number
CN115766942A (en) Customer service switching method, device, equipment and storage medium
US8073130B2 (en) Customer automated response system
CN203942648U (en) A kind of system of chauffeur information service
CN105306756A (en) Terminal state interaction method, call centre, terminal and call centre system
CN103139407B (en) Internet telephone system and device thereof
CA3109728C (en) Connected machine initiated service
KR20160021573A (en) Apparatus for connecting calls to receiving terminal and method for the same

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant