WO2011089583A2 - Découverte facile du contenu - Google Patents

Découverte facile du contenu Download PDF

Info

Publication number
WO2011089583A2
WO2011089583A2 PCT/IB2011/050313 IB2011050313W WO2011089583A2 WO 2011089583 A2 WO2011089583 A2 WO 2011089583A2 IB 2011050313 W IB2011050313 W IB 2011050313W WO 2011089583 A2 WO2011089583 A2 WO 2011089583A2
Authority
WO
WIPO (PCT)
Prior art keywords
communication
service
menu tree
enabled device
server
Prior art date
Application number
PCT/IB2011/050313
Other languages
English (en)
Other versions
WO2011089583A3 (fr
Inventor
Taron Mohan
Original Assignee
Taron Mohan
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 Taron Mohan filed Critical Taron Mohan
Publication of WO2011089583A2 publication Critical patent/WO2011089583A2/fr
Publication of WO2011089583A3 publication Critical patent/WO2011089583A3/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72436User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. short messaging services [SMS] or e-mails
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72469User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/005Discovery of network devices, e.g. terminals

Definitions

  • the present invention relates to a system for providing value added services on handheld devices. More specifically, the present invention relates to provisioning of one or more service menu tree on handheld devices and integrating the menu tree with the device internal service configuration capabilities.
  • the present application cross references related Indian patent application no. 140/ Del/ 2010
  • the present invention obviates the aforesaid drawbacks and provides a system and a method for providing a menu tree on a telecommunication enabled device.
  • the method includes receiving a first communication from the telecommunication enabled device after the telecommunication enabled device is switched on for the first time.
  • the first communication includes a device code and a first network identification code.
  • the method maps the menu tree corresponding to the first communication and generates at least one second communication including the menu tree and a service routing logic.
  • the method further delivers the second communication to a service discovery client on the telecommunication enabled device, wherein the second communication is meant to update the pre-installed service menu on the service discovery client.
  • the present invention provides a method for updating a service menu pre-installed on the telecommunication enabled device.
  • the method includes sending a first communication to a service management server after the telecommunication enabled device is switched on for the first time.
  • the first communication includes a device code and a first network identification code.
  • the method receives at least one second communication from the service management server.
  • the second communication includes a menu tree update configuration delivery string.
  • the method further updates the pre-installed service menu on a service discovery client with the received menu tree.
  • the system includes a server with a service menu management block for mapping the menu tree corresponding to a first communication received from the telecommunication enabled device after the telecommunication enabled device is switched on for the first time.
  • the first communication includes a device code and a first network identification code.
  • the server further includes a user interface management block for mapping a user interface corresponding to the first communication.
  • the server generates at least one second communication including the menu tree and a service routing logic and delivers the second communication to a service discovery client on the telecommunication enabled device.
  • the second communication is meant to update the pre-installed menu tree on the service discovery client.
  • Fig. 1 illustrates a service management server 100 in accordance with an embodiment of the present invention.
  • Fig. 2 illustrates the service management server 100 in accordance with another embodiment of the present invention.
  • Fig. 3 illustrates a telecommunication enabled device 114 in accordance with an embodiment of the present invention.
  • Fig. 4 illustrates a method of first time registration of the device 114 at server 100 in accordance with an embodiment of the present invention.
  • Fig. 5 illustrates a method of updating the menu tree in case when the network service provider is same in accordance with an embodiment of the present invention.
  • Fig. 6 illustrates a method of updating the menu tree in case of changed MSISDN in accordance with an embodiment of the present invention.
  • Fig. 7 illustrates a call flow for menu tree transmission after the telecommunication enabled device is switched on for the first time in accordance with an embodiment of the present invention.
  • Fig. 8 illustrates call flow for menu tree transmission for changed MSISDN in accordance with an embodiment of the present invention.
  • Fig. 9 illustrates a call flow for menu tree mapping with server 100 in accordance with an embodiment of the present invention. Detailed description
  • Fig. 1 illustrates a service management server 100 in accordance with an embodiment of the present invention.
  • the service management server 100 comprises an advertisement engine 102, a service menu management block 104, a user interface management block 106, a content database 108, a service database 110 and one or more communication channels 112.
  • the service management server 100 communicates with a telecommunication enabled device 114 like mobile phone, via one or more of communication channels 112.
  • server 100 may communicate with a telecommunication enabled device 114 via a voice channel.
  • server 100 may communicate with a telecommunication enabled device 114 via a data channel like GPRS.
  • Content database 108 may store information relating to content being served to the telecommunication enabled device 114 while service database 110 may store details of any interaction of the telecommunication enabled device 114 with server 100 and other details of telecommunication enabled device 114.
  • Content includes without limitation menu tree, advertisements etc. Details of interaction include without limitation, time and date of interaction, content requested, network identification code, etc. Other details of telecommunication enabled device include without limitation, device code, device capabilities, device type, version number of the menu tree installed on device 114, etc.
  • the content database 108 and the service database 110 are depicted as two separate entities, one would appreciate that there may be a single database that hosts all the content in it.
  • a network service provider may host its own service management server 100 or there may be a common service management server 100 serving multiple network service providers. Connectivity between multiple service management servers may be provided via Internet or a telecommunication network. Telecommunication networks include without limitation global system for mobile communications (GSM), code division multiple access (CDMA), asynchronous transfer mode (ATM) etc. Integration of multiple service management servers may be provided over SMS/ GPRS/ Voice/ USSD services.
  • the service management server 100 is responsible for the functioning of a system at the server end.
  • the service management server 100 receives a first communication from a service discovery client installed on the telecommunication enable device 114. In one embodiment, server 100 may receive the first communication via the communication channel 112 facilitating data transmission.
  • the first communication may be received in the form of for example, a Short Messaging Service (SMS) or an http call over GPRS.
  • server 100 may receive the first communication via the communication channel 112 facilitating voice exchange.
  • the first communication may be received as a call from the telecommunication enabled device 114.
  • the first communication includes a device code, a first network identification code, a country code, date and time of transmission, media partner ID, version number of the menu tree installed on it, and the like.
  • the device code may be for example an international mobile equipment identity (IMEI) while the first network identification code may be for example mobile station integrated services digital network (MSISDN), which can be mapped to the country and the network code.
  • IMEI international mobile equipment identity
  • MSISDN mobile station integrated services digital network
  • the server 100 decodes the first transmission to obtain the device code and other information encoded with it. Decoding includes decoding a message using standard algorithms or analyzing the http call to obtain the device code and other information embedded in it.
  • the server 100 may obtain the device make and model from the first communication and translate this to the device compatibility chart for premium content, media partner, branding partner and the like for building or offering services specific to the same, if needed.
  • server 100 may integrate with network elements like home location register (HLR), intelligent network (IN), device management module etc. for inputs on the user MSISDN, device IMEI code, user agent (UA) profile, device code, and the like.
  • HLR home location register
  • I intelligent network
  • device management module etc. for inputs on the user MSISDN, device IMEI code, user agent (UA) profile, device code, and the like.
  • Server 100 stores the first communication in the service database 110 with the time and date stamp against the device code obtained from the first communication.
  • server 100 may store subscriber service usage logs, menu tree version number, content of second communication, etc. in the service database 110. The communications are saved for reference at a later point in time.
  • the server 100 stores file transfer protocol (FTP) uploads, really simple syndication (RSS) feeds, extensible markup language (XML) feeds etc. in the content database 108 and information on the overall content / service life cycle management.
  • FTP file transfer protocol
  • RSS really simple syndication
  • XML extensible markup language
  • the first communication is received after the device 114 is switched on for the first time by a subscriber subscribed to this service.
  • Server 100 generates a menu tree based upon for example, the country code and the first network identification code obtained from the first communication. To generate the menu tree, server 100 communicates with the service menu management block 104.
  • the service menu management block 104 may be a logical block or a separate server communicating with server 100 via Internet.
  • the service menu management block 104 generates the menu tree based on different permutations. For example, service menu management block 104 may generate the menu tree based upon a network service provider or a country where the services are provided or capabilities of the telecommunication enabled device 114 or a media partner or combinations of the above.
  • the service menu management block 104 also generates a service routing logic using which the menu tree would be delivered to the telecommunication enabled device 114.
  • Service routing may be provided via SMS, GPRS, etc.
  • service menu management block 104 is responsible for reporting management like management information system (MIS) reports.
  • MIS reports may track all events, subscriber content, and the service transaction logs on the service management server 100 including voice calls initiated from the service discovery client. These reports may be utilized in handling profiling, recommendation and / or revenue reporting.
  • the reports may be helpful to for example, device manufacturers, other device manufactures (ODM) partners, media partner, brand owner, content provider, platform provider, etc.
  • ODM device manufactures
  • the menu tree once updated on the service discovery client is updated from time to time to incorporate any new service offerings by the network service provider.
  • the service discovery client accesses the services listed in the menu tree.
  • the version number of the last update is mapped to the latest version of the service menu tree available. If version numbers differ, then the updated menu tree / display text / call to action parameters are delivered over for example, SMS / http over GPRS.
  • the updated menu tree may be customized based upon user's profile and behaviour.
  • the service discovery client is updated silently in the background with the new received updates. In case the subscriber switches from one network service provider, say first network service provider, to another network service provider, say second network service provider, a third communication is received from the telecommunication enabled device with a second network identification code.
  • the second network identification code for example MSISDN remains same when a subscriber switches from the first network service provider to the second network service provider.
  • a look up table is used that contains mapping of MSISDN to the network service provider. If there is a change in the menu tree for the second network identification code, the updated menu tree is delivered to the device 114 over SMS / http over GPRS for an update to the service discovery client.
  • the third communication includes without limitation, device code, date and time stamp of communication, second network identification code etc.
  • server 100 also communicates with the advertisement engine 102 and the user interface management block 106 while generating a second communication.
  • the advertisement engine 102 and the user interface management block 106 may be logical blocks within server 100 or separate servers communicating with server 100 via Internet.
  • the advertisement engine 102 may handle images, videos or text banners / scrolling messages serving on the wireless application protocol (WAP) and the Web, while individual SMS gateways have their own advertisement tagging capability or can also feed SMS text banners for scrolling text feeds on the device 114.
  • WAP wireless application protocol
  • the user interface management block 106 is responsible for any changes to the user interface (UI) required on the UI of the service discovery client.
  • the user interface management block 106 manages headers and footers on the images displayed, theme designs, design templates and the like.
  • the user interface management block 106 also manages the position where a search box or an advertisement may be displayed on the UI of the service discovery client.
  • the Second Communication Server 100 generates the second communication which includes one or more of the menu tree, updated UI, and advertisements.
  • the second communication may be delivered as a single or a string of SMSs to the service discovery client.
  • the second communication may be delivered as an http string over GPRS channel.
  • the second communication updates the pre-installed service menu on the service discovery client with the menu tree embedded in it.
  • the second communication may be delivered via communication channel 112 for example, a GPRS channel.
  • the second communication over SMS / GPRS may comprise the following:
  • FIG. 2 illustrates the service management server 100 in accordance with another embodiment of the present invention.
  • server 100 may include a campaign manager 202, a recommendation engine 204, a caller ring back tone (CRBT) / ring back tone (RBT) engine 206, and a charging gateway 208.
  • CRBT caller ring back tone
  • RBT ring back tone
  • the campaign manager 202 manages campaigns centrally with uniform format for all campaigns.
  • the selection of targets can be from multiple databases for higher strike rate. These databases may either be hosted locally or with different network service providers.
  • the targets may be selected taking into account do not disturb (DND) / opt-in list filtering and may be deployed for specific promotions if needed.
  • Server 100 may provide bulk SMS / multimedia messaging service (MMS) / WAP push engine integration for broadcasting such campaigns.
  • MMS multimedia messaging service
  • the recommendation engine 204 is capable of handling millions of transactions.
  • the engine is scalable and a self learning module which allows an administrator to tweak the offerings with controls for content bias/browsed and actually downloaded content as well as defining the content type hierarchy for each content category available on the menu tree.
  • Recommendation engine 204 handles the content / service recommendation based on the above criteria and may be built over time for a subscriber profiled user menu.
  • CRBT/ RBT engine 206 integrates with the metadata on these platforms hosted externally and brings the service discovery/ configuration capability through the menu tree on the device 114.
  • Charging gateway 208 handles volume and event based call detail record (CDR) processing and billing management. It provides a complete billing interface based on the standard intelligent network (IN) connection protocols including Diameter, simple object access protocol (SOAP), Diameter or User Communication Interface Protocol (UCIP) etc., for handling multiple billing environments across different network service providers globally. It brings in capabilities for:
  • Fig. 3 illustrates the telecommunication enabled device 114 in accordance with an embodiment of the present invention.
  • the telecommunication enabled device 114 includes a transceiver 302, a chipset 304, a memory 306, a processor 308, and an update block 310.
  • Memory 306 includes a memory bank of random access memory (RAM) and read only memory (ROM) memories.
  • Each device 114 has a pre-installed service discovery client (SDC) 312. When the device 114 is switched on, maybe the first time or after some time lapse for example 1 month, the service discovery client 312 has to be updated.
  • the service discovery client 312 may vary for different network service providers, or based upon a country where the service is accessed.
  • the transceiver 302 transmits the first communication to the service management server 100 after the device 114 is switched on for the first time.
  • the transceiver 302 transmits the first communication via one of a circuit- switched network or a packet-switched network and maybe in the form of for example, an SMS or an http call.
  • the first communication includes a device code, a first network identification code, a country code, date and time of transmission, media partner identification (ID) and the like.
  • the device code may be for example international mobile equipment identity (IMEI) while the first network identification code may be for example MSISDN.
  • server 100 sends the updated information on one or more of the menu tree or the UI or advertisements.
  • server 100 sends a third communication to server 100.
  • the third communication specifies the device code, a second network identification code, a country code, date and time of transmission, etc.
  • the transceiver 302 receives a second communication from server 100 that includes one or more of an updated menu tree, advertisements or updated UI.
  • the processor 308 processes the second communication and updates the service discovery client 312.
  • the device 114 may send an acknowledgement to the server 100 on successful update of the service discovery client 312.
  • the menu tree includes a call to action for one or more of short messaging service (SMS), voice or general packet radio service (GPRS)actions available in the telecommunication enabled device for each of the menu tree links, a service access parameter management control within the service discovery client for each of the display links in the service discovery client, and a configuration string also sent over the second communication to the telecommunication enabled device for managing the service access parameters within the telecommunication enabled device.
  • SMS short messaging service
  • GPRS general packet radio service
  • Fig. 4 illustrates a method of first time registration in accordance with an embodiment of the present invention.
  • the method starts at step 400 when a telecommunication enabled device 114 is switched on the first time after a subscriber purchases it.
  • the telecommunication enabled device 114 sends a first communication to the service management server 100.
  • the first communication may be sent in the form of an SMS and may contain a long code SMS server for global reading of SMS messages.
  • Server 100 receives the first communication at step 402.
  • the server 100 decodes the first communication to obtain the device code, first network identification code and other information encoded in the first communication at step 404.
  • Server 100 uses this information to map the services to for example, the country, media, brand, network service provider partner and the device capabilities.
  • Server 100 determines at step 406 whether a mapping of the menu tree at the service discovery client is done. To determine this, server 100 queries the content database 108 and service database 110 a menu tree corresponding to the first network service provider and the device code. If the menu tree needs to be updated at the service discovery client, server 100 generates a second communication with the menu tree and other updates like UI update, advertisements, etc., at step 408. Otherwise the method stops at step 410. The second communication is then converted into one or more messages for example an http call over GPRS or SMS to be delivered to the service discovery client at step 412. Optionally, server 100 may receive an acknowledgement from the telecommunication enabled device 114 after the menu tree is successfully updated. The above method is repeated at predetermined intervals to ensure timely update of the menu tree at the service discovery client.
  • Fig. 5 illustrates a method 500 in case when the network service provider is same but the menu tree needs to be updated.
  • server 100 receives a request from device 114 regarding one of the services offered in the menu tree. The request may be received via an SMS or an http call. Server 100 obtains the information from the SMS / http call at step 504. Information includes the service that is requested, for example if messaging service is requested, the request may be to compose, or forward the message. Thereafter, server 100 checks if the received network identification code along with the device code matches with the network identification code stored in service database 110 for the same device code at step 506. The network identification code in the service database may be the first network identification code or the second network identification code.
  • server 100 matches the version number of the last updated menu tree with the latest version of the service menu tree available on the content database 108 at step 508. If there is a change, server 100 generates a second communication with the updated menu tree / display text / call to action parameters at step 510 and delivers it over SMS / http over GPRS at step 512.
  • the service discovery client 312 is updated silently in the background for the new updates.
  • Fig. 6 illustrates a method in case of changed MSISDN in accordance with an embodiment of the present invention.
  • the method starts at step 602 with server 100 receiving a third communication from service discovery client 312.
  • server 100 decodes the third communication to obtain the device code and a second network identification code along with other information like country code, date and time, etc at step 604.
  • Server compares the information received with the third communication with the corresponding information stored in the service database 110 at step 606. For example, server 100 compares the received device code and received second network identification code with the corresponding device code and the network identification code stored on the service database 110.
  • server 100 If there is a change in the network identification code, server 100 generates a second communication with the updated menu tree mapped to the second network identification code at step 608 and communicates this as a response to device 114 over for example SMS / GPRS to update the menu tree / UI / Call to action etc.
  • Fig. 7 illustrates a call flow for menu tree transmission after telecommunication enabled device 114 is switched on for the first time in accordance with an embodiment of the present invention.
  • the service discovery client 312 sends a first communication for example an SMS, to a centralised global SMS long code.
  • the telecommunication enabled device 114 keeps a track of the first communication being sent by setting a flag value to 1. This flag value is stored at the service discovery client 312.
  • the service discovery client 312 may further deactivate additional communications from being sent after the device is switched on.
  • the short message service center (SMSC) receives the first communication and forwards it to the service management server 100 at step 704.
  • the server 100 stores the first communication in the service database 110 against the device code like IMEI /MSISDN.
  • the parameters of the first communication includes date, time, MSISDN, device code, etc.
  • server 100 queries the content database 108 for the menu tree with the above details.
  • the content database 108 retrieves the menu tree mapped to the parameters of the first communication and delivers the same to server 100 at step 708.
  • Server 100 generates a second communication namely, SMS string or a single SMS or an http call over GPRS with the menu tree details for pushing it into the telecommunication enabled device 114.
  • Server 100 stores the date and time, MSISDN and the version of the menu tree in the service database 110.
  • server 100 forwards the SMS to the SMSC at step 710.
  • the SMSC in turn delivers it to the telecommunication enabled device 114 at step 712.
  • the second communication is delivered silently onto the telecommunication enabled device 114 to avoid interruption at the subscriber's end.
  • the menu tree is sent over http / GPRS, the information may be forwarded via the gateways at the network service providers' end. If the menu tree is sent over http / GPRS, the same is delivered to the service discovery client 312 when the telecommunication enabled device 114 is powered on and the updated parameters are reflected in the service discovery client 312.
  • the telecommunication enabled device 114 sends an acknowledgement trigger back to server 100 once the menu tree is updated, to avoid resending of same information.
  • Fig. 8 illustrates a call flow for changed network service provider code in accordance with an embodiment of the present invention.
  • the network service provider code for example MSISDN changes too.
  • the services configured to a network service provider / country / media partner may change with a change in MSISDN. Under such variations, the present invention works as follows:
  • the service discovery client 312 sends a third communication in the form of a SMS or an http call over GPRS to a long code with the device code or over data packets, second network identification code, date and time, etc.
  • the third communication is forwarded to a SMSC.
  • the SMSC forwards the third communication to the service management server 100 at step 804 which in turn stores the third communication.
  • the server 100 sends a query to the content database 108 to obtain details of the menu tree mapped to the third communication at step 806.
  • the query may include a country code and a network identification code.
  • Server 100 receives the details in step 808 and compares the old menu against old parameters and the new parameters coming into the server 100 with the new MSISDN. In case the parameters are different, a new menu tree is generated and pushed over either a SMS or an http call over GPRS to the telecommunication enabled device 114 (steps 810 and 812). In case the parameters are similar to the previous one, then no menu tree is generated and delivered (step 814).
  • Fig. 9 illustrates a call flow for SMS menu tree mapping with server 100 in accordance with an embodiment of the present invention.
  • a mobile originated (MO) message from the device including the Country Code, Network Code, Device ID and Media Partner ID is sent to the SMSC.
  • the SMSC forwards the message to server 100 at step 904.
  • Server 100 sends the query for the menu tree with the above details to the content database 108.
  • the content database 108 retrieves the relevant menu tree mapped to these parameters and generates a second communication to be delivered to the device 114.
  • the second communication may be in the form of a single SMS or a SMS string.
  • the second communication is forwarded to SMSC at step 906 which in turn pushes it to the telecommunication enabled device 114 at step 908.
  • the complete service menu tree is generated in the service discovery client 312.
  • the telecommunication enabled device 114 checks for last SMS delivery. On successful delivery of all SMS to device 114, the complete menu tree is generated in service discovery client 312.
  • the updates are delivered over GPRS, a packet string is delivered to device 114 and the updates are confirmed for an acknowledgement to the server 100 as a confirmation on this update.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention surmonte les inconvénients ci-dessus et fournit un système et un procédé destinés à fournir une arborescence de menus sur un dispositif à fonctions de télécommunications. Le système comprend un serveur avec un bloc de gestion de menus de services, destiné à mapper l'arborescence de menus correspondant à une première communication reçue du dispositif à fonctions de télécommunications après que le dispositif à fonctions de télécommunications est mis en service pour la première fois. La première communication comprend un code de dispositif et un premier code d'identification de réseau. Le serveur comprend en outre un bloc de gestion de l'interface utilisateur, destiné mapper une interface utilisateur correspondant à la première communication. Le serveur produit au moins une seconde communication qui comprend l'arborescence de menus et une logique de routage de service et il fournit la seconde communication à un client de découverte des services sur le dispositif à fonctions de télécommunications. La seconde communication est destinée à mettre à jour l'arborescence de menus préinstallée sur le client de découverte des services.
PCT/IB2011/050313 2010-01-25 2011-01-25 Découverte facile du contenu WO2011089583A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN141DE2010 2010-01-25
IN141/DEL/2010 2010-01-25

Publications (2)

Publication Number Publication Date
WO2011089583A2 true WO2011089583A2 (fr) 2011-07-28
WO2011089583A3 WO2011089583A3 (fr) 2012-01-12

Family

ID=44307334

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2011/050313 WO2011089583A2 (fr) 2010-01-25 2011-01-25 Découverte facile du contenu

Country Status (1)

Country Link
WO (1) WO2011089583A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018006807A1 (fr) * 2016-07-04 2018-01-11 中兴通讯股份有限公司 Procédé, appareil et système de traitement de tonalité de retour d'appel personnalisée

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040046804A1 (en) * 2002-09-11 2004-03-11 Chang Peter H. User-driven menu generation system with multiple submenus
US20080016464A1 (en) * 2002-10-18 2008-01-17 Xiuzhi Gao Customizable Database-Driven Menu Structure for a Portable Computing Device
US20080312903A1 (en) * 2007-06-12 2008-12-18 At & T Knowledge Ventures, L.P. Natural language interface customization

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040046804A1 (en) * 2002-09-11 2004-03-11 Chang Peter H. User-driven menu generation system with multiple submenus
US20080016464A1 (en) * 2002-10-18 2008-01-17 Xiuzhi Gao Customizable Database-Driven Menu Structure for a Portable Computing Device
US20080312903A1 (en) * 2007-06-12 2008-12-18 At & T Knowledge Ventures, L.P. Natural language interface customization

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018006807A1 (fr) * 2016-07-04 2018-01-11 中兴通讯股份有限公司 Procédé, appareil et système de traitement de tonalité de retour d'appel personnalisée
CN107580150A (zh) * 2016-07-04 2018-01-12 南京中兴新软件有限责任公司 彩铃处理方法、装置及系统

Also Published As

Publication number Publication date
WO2011089583A3 (fr) 2012-01-12

Similar Documents

Publication Publication Date Title
US7930208B2 (en) Method and system for delivery of advertising content in short message service (SMS) messages
US8315178B2 (en) Method and system for wireless message-based advertising
US8804917B2 (en) System and method for providing a personalized identity to a destination
US9767518B1 (en) Method and system for providing custom background-downloads
US8204057B2 (en) Methods, systems, and computer program products for providing an enriched messaging service in a communications network
US7890586B1 (en) Mass multimedia messaging
US7546120B1 (en) Method and system for managing transmission of media to multiple subscribers
US20160155155A1 (en) System and method for managing shared/forwarded advertisement
JP2004129270A (ja) インスタントボイスメッセージング方法及びインスタントボイスメッセージング装置。
US8666036B2 (en) Alert provisioning system and method
WO2006081725A1 (fr) Méthode et système pour assortir la page web d’un terminal mobile de communication
EP2005721A2 (fr) Système et procédé de rétroaction utilisateur de dispositif sans fil
US9191792B2 (en) Provision of additional content to mobile communication devices
US8095642B1 (en) Method and apparatus for dynamically adjusting frequency of background-downloads
CN101325746A (zh) 一种发送消息的方法和系统
WO2008110656A1 (fr) Procédé et appareil pour surveiller des communications d'utilisateurs
KR100436424B1 (ko) 무선 단말기에 대한 정보 서비스 제공 방법과, 이에적합한 정보 서비스 시스템 및 메시징 에이전트 시스템
US9065934B2 (en) System, an apparatus, a client device and a method for providing pricing information
US8666037B2 (en) Alert provisioning system and method
WO2011089583A2 (fr) Découverte facile du contenu
US20150052210A1 (en) System and method for broadcasting rich media to devices over multiple carriers
US20070061193A1 (en) Advertisement on demand service
KR101165414B1 (ko) 광고통화서비스 시스템
KR101300996B1 (ko) Mms를 활용한 위치 기반 광고 서비스 제공 방법 및 시스템
KR20090132478A (ko) 공유/회송된 광고를 관리하기 위한 시스템 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11734443

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11734443

Country of ref document: EP

Kind code of ref document: A2