WO2006130783A2 - Procede et systeme pour contenu pousse lance par l'etablissement d'un appel - Google Patents

Procede et systeme pour contenu pousse lance par l'etablissement d'un appel Download PDF

Info

Publication number
WO2006130783A2
WO2006130783A2 PCT/US2006/021312 US2006021312W WO2006130783A2 WO 2006130783 A2 WO2006130783 A2 WO 2006130783A2 US 2006021312 W US2006021312 W US 2006021312W WO 2006130783 A2 WO2006130783 A2 WO 2006130783A2
Authority
WO
WIPO (PCT)
Prior art keywords
party
call
push content
content
push
Prior art date
Application number
PCT/US2006/021312
Other languages
English (en)
Other versions
WO2006130783A3 (fr
Inventor
Yue Jun Jiang
Original Assignee
Roamware, Inc.
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 Roamware, Inc. filed Critical Roamware, Inc.
Priority to BRPI0611016-9A priority Critical patent/BRPI0611016A2/pt
Priority to EP06760629A priority patent/EP1889428A4/fr
Publication of WO2006130783A2 publication Critical patent/WO2006130783A2/fr
Publication of WO2006130783A3 publication Critical patent/WO2006130783A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/02—Calling substations, e.g. by ringing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42017—Customized ring-back tones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42042—Notifying the called party of information on the calling party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services

Definitions

  • the present invention generally relates to systems and services that provide push content. More specifically, the present invention relates to call setup triggered push content providing systems and methods of handling call flow for these systems.
  • Content “push” is one such frequently-described means of distributing personally relevant digital content.
  • “Push” technology also called “server push,” typically has been used to describe an internet-based content delivery system where information is delivered from a central server to a client station based upon a predefined set of request parameters outlined by the client computer.
  • client computer user such as a home desktop user would subscribe to various information topics provided by a content provider and as that content is created by the content provider, such information is "pushed” or delivered across the internet to the desktop user and displayed on the users' computer.
  • the push concept is also used for providing mobile pushed content services.
  • the mobile push content services include SMS push service, WAP push service, push information service, missed call alerts, and push email service which are highly popular services and major sources of revenue for mobile operators.
  • Another mobile push content service namely, mobile TV, is a push broadcast service in demand.
  • multimedia push services such as multiple channels of multimedia information, video and TV for downloading the push content to mobile devices in idle mode for off-line viewing.
  • An example of such a service are client/server products known in the art for pushing network-based media content to handsets during downtime, such as the "Silverstripe" solution offered by bamboo Mediacasting (www.bamboomc.com).
  • the push content services known in the art do not enable a calling party to view the called party's latest profile (for example, pictures, blogs etc), or enable a called party to inform his calling friends of his new address.
  • the calling party is not able to communicate with multiple parties in a call- setup such as broadcasting to a group of friends stored in his handset's phonebook in one broadcast session to inform them of his new address.
  • the push content services known in the art typically allow for content to be pushed only in a single direction in an in-band manner (i.e. having both voice and push content in the same circuit switched or packet switched channel) and require changes (for example, by adding special additional parameters) to the existing signaling protocols (for example, ISUP, SIP etc).
  • a known push content service known as "push-to-talk" permits a calling party to talk instantly to a called party without involving the called party to answer the call and hear the calling party.
  • push to talk service is generally, implemented as a half-duplex service like a walkie-talkie service for mobile phones, and by definition occurs without call set up (phone ringing, requiring a called party to accept the call, etc.).
  • call- setup based push-to-talk has been proposed in the art, a generic extension of call-setup architecture to permit client-less push to talk is still needed.
  • UUlUJ Another known push content service relating to personal "ringback tone" service allows the calling party to hear a ring tone (e.g. music, audible) personalized by the called party but played at the network via the bearer path of the call rather than on the calling device side.
  • ringback tone does not typically permit, for example, a calling party to download or designate that ringback tone, audio file or corresponding ringtone for his own future use. Also, that ringback tone content is limited to audio content and cannot be viewed by ordinary devices. In yet another service relating to caller-defined ring tone service, the called party hears a ring tone (e.g. music, audible) personalized by the calling party but played on the called party's device.
  • ring tone e.g. music, audible
  • the present invention enables telecommunications networks originally designed for person-to-person conversations to offer any type of content or personalized media experience during the personal "attention grabbing" moment represented by extending the installed apparatus for call set up. That personalized experienced can be instantiated or designated by any party to the call being set up, by the network itself or by others. flexible means are provided for establishing this extension to state of the art call set up infrastructure widely available in today's common carrier networks.
  • the present invention provides a method for pushing content to at least one receiving party via a telecommunication network in the context of a call setup event. The method includes performing a call control function in response to a call setup initiated by a calling party to a called party. The call control function operates on at least one call parameter.
  • the method further includes applying an application logic based upon the at least one call parameter for determining at least one receiving party and the corresponding push content details of the at least one receiving party, and delivering the push content specified in the push content details to the at least one receiving party.
  • That receiving party can be the calling or the called party, or another party.
  • That at least one parameter can be set by the calling party, the called party, the network, a third party, pre- conf ⁇ gured, a priori, based on rules, or set by any party.
  • the present invention provides a system for providing call setup triggered push content to at least one receiving party via a first telecommunication network.
  • the system comprises a subscriber database, a network interface, an application module, and a content server.
  • the subscriber database stores at least one subscriber profile and preference settings.
  • the preference settings include the push content details of the subscriber.
  • the network interface performs a call control function in response to a call setup.
  • the call control function operates on at least one call parameter.
  • the application module applies application logic based upon the at least one call parameter for determining the at least one receiving party and the corresponding push content details of the at least one receiving party.
  • the content server delivers the push content specified in the push content details to the at least one receiving party.
  • [0016JFIG. 1 is a flowchart depicting a method for providing push content, in accordance with an embodiment of the present invention.
  • [0017JFIG-. 1 is a block diagram depicting a system for providing call setup triggered push content to at least one receiving party (not shown) in a telecommunications network, in accordance with an embodiment of the present invention.
  • FIG. 3 shows a database table depicting an exemplary subscription profile for a receiving party, in accordance with an embodiment of the present invention.
  • FIG. 4 shows the configuration of a receiving party profile channel, in accordance with an embodiment of the present invention.
  • FIG. 5 shows an exemplary configuration of a ring forward tone (RFT) channel by a receiving party, in accordance with an embodiment of the present invention.
  • RFT ring forward tone
  • FIG. 6 shows an example of a general push content permission control by a receiving party against a sending party, in accordance with an embodiment of the present invention.
  • FIG. 7 shows a table containing group definitions of a subscriber of CTPCS, in accordance with an embodiment of the present invention.
  • FIG. 8 depicts various options of supporting push content delivery to a device from
  • FIG. 9 illustrates an exemplary call flow based on an originating party call control.
  • FIG. 10 illustrates an exemplary call flow based on a terminating party call control.
  • FIG. 11 illustrates an exemplary signal flow of the interaction between a calling party A, a called party B and CTPCS while pushing content to the called party B in accordance with an embodiment of the present invention.
  • FIG. 12 illustrates an exemplary signal flow of the interaction between a calling party A, a called party B and CTPCS while pushing content to calling party A and called party B in accordance with an embodiment of the present invention.
  • FIG. 13 illustrates an exemplary signal flow depicting inter-working of call setup triggered push content service between operators for a pushed content to the called party.
  • FIG. 14 illustrates an exemplary signal flow depicting inter- working of call setup triggered push content service between operators for a pushed content to the called party of VPMN-2 and the calling party.
  • FIG. 14 illustrates an exemplary signal flow depicting inter- working of call setup triggered push content service between operators for a pushed content to the called party of VPMN-2 and the calling party.
  • FIG. 14 illustrates an exemplary signal flow depicting inter- working of call setup triggered push content service between operators for a pushed content to the called party of VPMN-2 and the calling party.
  • FIG. 16 illustrates an exemplary call flow depicting called party call control for delivering calling party defined ring tones to the called party.
  • FIG. 17 illustrates an exemplary call flow depicting calling party call control for delivering a called party defined ring tone to the calling party.
  • FIG. 18 illustrates an exemplary call flow depicting inter- working between operators where a calling party A of VPMN-I is calling a called party B of operator
  • VPMN-2 with a calling party defined ring tone that is subscribed by the called party.
  • FIG. 19 describes news flash service of CTPCS with respect to a subscriber each time the subscriber makes a call in accordance with an embodiment of the present invention.
  • FIG. 20 illustrates profile information of a call party pushed to the other call party in either or both directions in accordance with an embodiment of the present invention.
  • FIG. 21 illustrates signal flow of the profile of called party being sent to the subscribed calling party in accordance with an embodiment of the present invention.
  • the receiving party includes a calling party, a called party, both the parties, a group of parties or a third party (for example, parents, spouses, schools, employers, clubs, police, other emergency services, mailing lists etc).
  • the call party includes a calling party, a called party and a third party.
  • the sending party is the party that defines the push content to be sent to one or more receiving parties.
  • the sending party includes a calling party, a called party, a group of parties and a third party.
  • a subscriber is a " person wMb "Ms subscribed to a call setup triggered push content service. Based on different call events, the subscriber may be the called party, the calling party, or a third party.
  • the present invention provides a system and method for providing a call setup triggered push content to at least one receiving party.
  • the call setup draws the attention of a calling party who is intending a call and possibly also the attention of a called party who is notified (via for example, a ring-tone or a vibration alert) of the call.
  • the push content subscribed by the receiving party may be network-based provided by mobile operators or their content/service partners.
  • the push content subscribed by the receiving party may be uploaded by the calling party or the called party (the receiving device) at call-setup triggered push content system (CTPCS) for future personal usage or shared public usage, hi yet another embodiment, the push content subscribed by the receiving party may be uploaded by other call party (for example, a third party) at the CTPCS. hi yet another embodiment, the push content subscribed by the receiving party may be uploaded by a third party at the CTPCS.
  • the push content may be uploaded at the CTPCS independent of a call or just prior to a call, hi various embodiments, the push content may be delivered to the receiving party prior to the call being answered, while the call is in progress or after the call completion.
  • the push content includes ring tones and multimedia information.
  • the ring tone ringing on the calling party device may be defined either by the called party or the calling party (for example, top 5 ring tone downloads) at the CTPCS or the CTPCS (for example, a network-accessible "jukebox" or library of many content items), hi another embodiment, the ring tone ringing on the called device may be defined by the calling party or the called party (for example, hip hop ring tone download only from jukebox) at the CTPCS or the CTPCS (for example, the jukebox).
  • the present invention uses a voice channel to trigger voice communication when the calling party calls the called party. The voice call triggers a network application to start a session.
  • This voice communication triggers a data communication of pushing content via (SMS or data channel such as GPRS or IMS or any other data channel) to the receiving device (calling party or called party or third or both or all).
  • SMS content via
  • data channel such as GPRS or IMS or any other data channel
  • the receiving device can then play the content prior to the call being answered.
  • FIG. 1 is a flowchart depicting a method for providing push content, in accordance with an embodiment of the present invention.
  • the method is invoked in response to a call setup request from a calling party to a called party.
  • the call setup is initiated via the call setup request.
  • the call setup includes time for which the calling party to wait for a call answer after dialing the called party and the waiting time of the called party before an incoming call is notified to the called party or before the called party answers or refuses the call.
  • the call setup catches the attention of the called party due to for example, ringing/vibrating notification, and the attention of the calling party for requesting the call.
  • the method enables push content to be pushed to call parties' receiving devices (for example, a calling party, a called party or a third party) in either direction while the call setup is in progress, rather than when the call party receiving device is in an idle state.
  • a call-setup triggered push content system performs a call control function during the call setup from the calling party to the called party.
  • the call control function operates on at least one call parameter which is made available for determining how the call or the push content will be identified, provisioned or delivered.
  • call control parameters may be, but are not limited to, an application identifier, a calling party number, a calling party International Mobile Subscriber Identity (IMSI), a called party number, or a Visited Mobile Switching Center (VMSC) location.
  • IMSI International Mobile Subscriber Identity
  • VMSC Visited Mobile Switching Center
  • the CTPCS applies application logic to determine at least one receiving party and the corresponding push content details of the at least one receiving party based upon the at least one call parameter.
  • the receiving party includes a calling party, a called party, a third party and a group of parties.
  • call parties, subscribers, network operators, third parties or computer programs can define the push content details of each user of the CTPCS.
  • CTPCS stores the profile and preference settings of the receiving parties.
  • the profile and preference settings may include, for example, the identity of the calling party, the identity of the called party, a third party identity, the call history information, time of the day, season, relationships, default order to play the push content in case of simultaneous incoming calls from, for example, unknown callers or push content and combinations thereof.
  • a sending party defines the push content details to which the requested or delivered push content is to correspond.
  • the sending party can be a calling party, a called party, the network operator, a third party or a group of parties.
  • CTPCS may define the push content based on a history of calls of the at least one receiving party, or any other data observed about relevant call parties.
  • the push content may be selected by the sending party in accordance with different application logic, for example, the push content may be selected at subscription time or during subscription life independent of a particular call or just prior to making a particular call.
  • the push content specified in the push content details is delivered to the at least one receiving party.
  • the push content can include, by way of non-limiting example, a ring tone, a video tone, a news item, a stock report, a sports update, a quote of the day, a calling party profile, a called party profile, an audio file, a celebrity voice, a music item, a multimedia file, a television footage, an advertisement, incoming email headers, an information of calls related to other calling devices, or a combination thereof.
  • the ring tone includes a telecommunication network defined ring tone, an operator defined ring tone, and a call party (for example, calling party or called party or third party) defined ring tone.
  • the push content may be delivered to the receiving party while the call setup is not complete.
  • the push content is delivered/streamed and played to at least one receiving party while the call is initiated by the calling party and disconnected by the calling party without call completion.
  • the calling party may make a call and disconnect the call after sending the ring tone to the called party without the call setup being complete.
  • the call setup may ' De a group call in which the calling party may trigger an information broadcast (e.g. he has moved to a new job) to a group of users.
  • the delivered push content can be played over a voice or data channel, or can be played using a client installed on the at least one receiving party.
  • a client installed on the at least one receiving party.
  • that client may be designed to play content stored on the receiving device itself.
  • the delivered push content corresponding to the push content matched on caller ID and received from a known caller ID is played.
  • unmatched push content and simultaneous incoming calls from unknown caller IDs are received, the delivered push is played in the order of incoming calls and incoming push contents.
  • the receiving party has an option to override the push content.
  • the push content may be protected by a digital rights management (DRM) implementation.
  • DRM digital rights management
  • the push content is delivered to the receiving party either before a call is answered, while a call is in progress and/or after the call is complete.
  • the delivering of the push content includes streaming of the push content and/or downloading of the push content at the receiving party.
  • the delivery of the push content (that is suspended due to a call being answered) is resumed after the call completion.
  • the process of delivering the push content may be influenced by an activity reported by a client present on the receiving party device.
  • the activity may be a silent mode, a switched off ring forward tone mode, a stop interrupt by a subscriber, and/or a combination thereof. Also, at least one of storing, configuring, deleting, stopping, suspending, resuming and purchasing of the push content may be performed by the receiving party.
  • Examples of the push content may include by non-limiting example any of the following:
  • Calling party profile e.g. interests, blogs, pictures, recent activities etc
  • Called party profile e.g. interests, blogs, recent activities (e.g. relocation, bought a house, had a baby, had a promotion, changed job, recent pictures etc.) for the calling party to take peek before the called party answers the call.
  • Network-selected ring tone e.g. top 5 randomly selected, or from a jukebox
  • These ring tones can be music, audible, voice, jokes, videos, multimedia display etc.
  • Network-stored but calling party selected e.g. a one-time music gift or a pre- configured selection
  • calling party selected e.g. a one-time music gift or a pre- configured selection
  • These ring tones can be music, audible, voice, jokes, videos, multimedia display etc.
  • Network-stored but called party selected (e.g. a one-time music gift or a pre- configured selection) to ring on the calling party's device for each incoming call,
  • These ring tones can be music, audible, voice, jokes, videos, multimedia display etc.
  • the email-accounts selected will be based on the subscription preferences of the subscribers.
  • Real-time news channel e.g. text news, or TV news
  • the particular news channel selected will be based on the subscriptions of the subscribers.
  • Real-time sports update (e.g. tennis, golf, NBA, soccer etc) to flash on the calling party before the call is answered and/or on the called party's device for each incoming call.
  • the particular sports update selected will be based on the subscriptions of the subscribers. They can even be video/TV highlights of scoring moments.
  • Real-time weather updates to flash on the calling party before the call is answered and/or on the called party's device for each incoming call The particular weather update selected (e.g. home area, visiting country etc) will be based on the subscriptions of the subscribers. • Multiple channels of information updates to flash on the calling party before the call is answered and/or on the called party's device for each incoming call. For example, the called party can subscribe to news flash, email headers, weather, stock quotes etc flashing thru the screen while the incoming call is ringing.
  • Called party subscription can in particular save money for receiving calls when roaming abroad.
  • the call setup triggered push content service is a subscription- based service for the mobile operators.
  • the push content service includes different push contents and multiple services of the same push content.
  • a subscriber may subscribe to either or both a calling party received service and a called party received service. Both the calling party and the called party may be subscribers of their respective services for a call. While paying monthly subscription, any change in the subscribed push content or the subscribed push content service may lead to a different charging to the subscribers. This further increases the mobile operator's revenue.
  • FIG. 2 is a block diagram depicting a system for providing call setup triggered push content to at least one receiving party (not shown) in the telecommunications network, in accordance with an embodiment of the present invention.
  • the receiving party may be the calling party, the called party, and /or one or more third parties.
  • the figure shows a network 202, which is a call-based network.
  • network 202 provides for calls between its users.
  • network 202 is a General Packet Radio Service (GPRS) enabled GSM network.
  • GPRS General Packet Radio Service
  • Network 202 includes a Home Location Register (HLR) / Home Subscriber System (HSS) (hereinafter collectively referred to as HLR) 204, a Gateway Mobile Switching Center (GMSC) / Call Session Control Function (CSCF) (hereinafter collectively GMSC) 206, Mobile Switching Center (MSC) / Visited Location Register (VLR) (hereinafter collectively referred to as MSC) 208, Service GPRS Support Node (SGSN) 210, and Gateway GPRS Support Node (GGSN) 212. Further, network 202 uses an IP Multimedia System (IMS) / GPRS network 214. The functioning and interoperation of these elements in a GSM/GPRS network is well known in the art.
  • HLR Home Location Register
  • HSS Home Subscriber System
  • GMSC Gateway Mobile Switching Center
  • CSCF Call Session Control Function
  • MSC Mobile Switching Center
  • VLR Visited Location Register
  • SGSN Service GPRS Support Node
  • CTPCS call-triggered push content system
  • CTPCS 216 comprising a network interface 218, a subscriber database 220, an application module 222, and a content server 224.
  • CTPCS 216 further optionally includes a presence and permission (PnP) server 226, and a configuration server 228.
  • PnP presence and permission
  • CTPCS 216 interfaces with network 202 through network interface 218 and IMS/GPRS network 214.
  • PnP presence and permission
  • CTPCS 216 interfaces with network 202 through network interface 218 and IMS/GPRS network 214.
  • PnP presence and permission
  • CTPCS 216 interfaces with network 202 through network interface 218 and IMS/GPRS network 214.
  • device 230 is connected with network 202, and is subscribed to CTPCS 216.
  • Device 230 has a client software (hereinafter referred to as 'client') loaded on it, which enables device 230 to receive, present or render, and upload push content, m the context of the present invention, presenting push content on a device includes, but is not limited to, playing audio content, playing video content, and displaying text content on the screen of device 230.
  • the client may be configured to read out text content, hi an embodiment, the client further enables management of subscriber preferences and permissions, maintenance of presence information of a subscriber, or both. The function of the client is described in detail later in the document.
  • Network interface 218 interfaces CTPCS 216 with network 202. Further, network interface 218 performs a call control function.
  • the call control function can be similar to the that of a Signal/Service Control Point (SCP) or Service Node which allows a switch to suspend the call and request instructions (such as connecting the call to another number, monitoring call answer events etc) from the call control function.
  • Network interface 218 interfaces with network 202 via Signaling System 7 (SS7) protocol and / or Internet Protocol (IP).
  • SS7 Signaling System 7
  • IP Internet Protocol
  • network 202 is configured to pass the call control, along with at least one call parameter, to network interface 218.
  • HLR 204 stores the CTPCS subscriber's trigger profile.
  • the CTPCS subscriber is a subscriber who has subscribed to services offered by the CTPCS.
  • the trigger profile is downloaded to MSC 208 at which the subscriber's device is registered.
  • MSC 208, or CSCF in IP Multimedia Subsystem (IMS) passes the call control to network interface 218 for further instruction.
  • HLR 204 passes the subscriber's trigger profile to GMSC 206 at terminating call setup, to pass the call control to network interface 218 for further instruction.
  • the call parameters pass to network interface 218 and include details of the call, hi an embodiment, the call parameters can include, but are not limited to, an application identifier, a calling party number, a calling party International Mobile Subscriber Identity (IMSI), a called party number, a Visited Mobile Switching Center (VMSC) location.
  • IMSI International Mobile Subscriber Identity
  • VMSC Visited Mobile Switching Center
  • subscriber database 220 stores subscriber profiles including, by way of non-limiting example, job change, marital status change, and recent activities (e.g. just came back from Egypt). In an embodiment, subscriber database 220 stores the preference settings of the subscribers.
  • the profile and preference settings may include, for example, the push content details of the subscriber, the identity of a calling party, the identity of a called party, a third party identity, call history information, time of the day, season, and relationships.
  • subscriber database 220 stores locations of call parties, historical information, and timing information of call parties.
  • Historical information includes without limitation, one or more of, voice usage of the subscriber, data usage of the subscriber, frequency of calls to/from the subscriber, number of calls to/from the subscriber, missed calls in an interval, subscription history, information usage profile (e.g. loves music), set up history on the device, and / or download history.
  • Timing information includes the time of the call, season, and the time zone of the subscriber.
  • Call party location information includes the home country of the subscriber, the current location of the subscriber, and the current location of the call parties.
  • subscriber database 220 stores the service subscription profile for each subscriber that includes, without limitation, the channel of subscriptions of the subscriber, and the plan level of the subscriber.
  • Application module 222 applies application logic based upon the call parameters and / or the preference settings. More specifically, application module 222 determines the parties to whom content must be pushed in response to a call setup request, or the receiving parties. Further, application module 222 identifies the content to be pushed to these receiving parties, in response to the call setup request. When network interface 218 receives call control for a call setup request, it interfaces with and provides the call parameters to application module 222.
  • Application module 222 can be configured to generate such instruction by applying rules and logic based on the application for which the push content infrastructure is used. It would be apparent to one skilled in the art that a wide range of rules and logic may be applied by application module 222 without deviating from the sprit and scope of the present invention. Some examples of such rules and logic are described hereinafter to illustrate certain aspects of the present invention, and should not be considered limiting.
  • An example of application logic for push content relates to the application of ring tone forwarding.
  • the called party may subscribe to a ring tone jukebox for ringing on his/her device for an incoming call.
  • Application module 222 may be configured, for example, to select a different tone from a network accessible jukebox for each incoming call.
  • the called party may subscribe to a calling party defined push ring tone for ringing on his/her device, where the calling party has selected / uploaded a push ring tone.
  • application module 222 may select a more "urgent sounding" ring tone (with a higher pitch and / or volume) if the calling party has called the called party for more than a pre-defined number of times without getting an answer.
  • the predefined number may be a configured by the subscriber or by the operator of network 202.
  • application module 222 may select a different ring tone if the calling party has called the called party more than a pre-defined number of times within a configurable period.
  • Application module 222 may push the user profile of the calling party to the called party, and vice versa, before call setup. In an embodiment, if the calling party has been pushed with the called party profile in a previous call between them, and there is no change in the user profile of the called party since the last push, then no profile will be pushed.
  • Another example of application logic for push content relates to pushing other user information to the device, such as new email alerts, stock alerts, general news alerts, customized news alerts such as sports news, and country-specific news.
  • the email sender and subject of each new email may be pushed to the called party's device to be presented before, during and / or after the incoming call.
  • each stock data of his / her interest may be pushed to the called party's device for presentation before, during, and / or after an incoming call.
  • Other such channels that may be made available to subscribers of CTPCS 216 include, without limitation, a sports highlights channel (providing TV/video-based push content, or just a multimedia message), a country specific news channel (where the country of interest may be preconf ⁇ gured, or determined at the time of the call based on the current location of the subscriber), and a location specific weather channel (where the location of interest may be preconfigured, or determined at the time of the call based on the current location of the subscriber).
  • push content may include text, audio, video, and or multimedia advertisements.
  • the revenue generated from the advertisements may be used to finance the call.
  • Another example of the rules and logic applied by application module 222 includes determining if a ring tone needs to be pushed to a receiving party.
  • the calling party or the calling party's network operator
  • the called party may have subscribed to a push ring tone service.
  • application module 222 decides not to push the ring tone to the called party.
  • a subscriber of CTPCS 216 may subscribe to the service of new phone software upgrades.
  • subscriber database 220 stores information about the software downloads made by the subscriber.
  • application module 222 can determine if the software on the subscriber's device is up to date, using information from subscriber database 220. If the last downloaded version of software on a subscriber's device is not up to date, application module 222 may decide to push the latest version of the software to the subscriber's device.
  • PnP server 226 stores presence and permission related data of the subscribers.
  • PnP server 226 is responsible for the presence and availability of a client on the called party's device. Specifically, PnP server 226 maintains the presence status (for example, online, offline, silent mode, busy, and temporarily away) of each subscriber, hi an embodiment, if the called party is busy on another call, the client informs PnP server 226.
  • PnP server 226 wakes the client with a Wireless Application Protocol (WAP)-push Uniform Resource Locator (URL), or a Short Message Service (SMS) URL for the client to establish an IP connection and passes the IP address of the client to PnP server 226.
  • WAP Wireless Application Protocol
  • SMS Short Message Service
  • PnP server 226 may use a direct SS7 connection to send the SMS to the device rather than going thru a SMSC to reduce latency.
  • the direct SS7 connection may use a protocol for example, Mobile Application Part- Send Routing Information-Send Message (MAP-SRI-SM) followed by a Mobile Application Part - Forward SMS (MAP ForwardSMS).
  • MAP-SRI-SM Mobile Application Part- Send Routing Information-Send Message
  • MAP ForwardSMS Mobile Application Part - Forward SMS
  • PnP server 226 can also be responsible for server-side management of the Push Information (e.g. ring forward tone) permissions granted by the called party.
  • the called party uses the client on the device to configure the permission of the push information (e.g. ring forward tone service).
  • This can be defined as a whitelist and blacklist.
  • a whitelist is a list of callers who are permitted to push content to the called party.
  • a blacklist is a list of callers who are not permitted to push content to the called party.
  • default permission can be configured.
  • One such default permission for the application of ring forward tone for example, could be to play the ring tone of device's ordinary configuration.
  • Another default permission for ring forward tone is to grant permission to push content, thereby increasing the surprise and excitement factor.
  • a schema for a client-user interface on the receiving party for granting call party defined ring tone permissions is described in detail with reference to FIG. 6.
  • the pennission preferences of a client are uploaded to PnP server 226.
  • application module 222 uses permission preferences from PnP server 226 to determine the receiving parties of push content. It is advantageous to apply the permission preferences at CTPCS 216 instead of applying them at the device the since the caller ID might be lost when the call is delivered to the device. For example, when determining whether a calling party's defined ring forward tone should be pushed to the called party or not, the PnP server 226, which is on the network side, can use the calling party DD to check for conformance with permissions defined at PnP server 226.
  • out-of-band communication between PnP server 226 on the network side and the client on the device side can also be used to deliver Caller ID to outbound roamers.
  • the out-of-band communication uses a separate data bearer and voice bearer for call setup.
  • Application module 222 uses the presence and permission data stored in PnP server 226 for its application logic. Application module 222 could apply, for example, the logic that if a receiving party is in a switched-off mode or silent mode, no content is pushed to the receiving party. [0079] Once application module 222 has identified the receiving parties and the content to be pushed to them, it issues a request to content server 224 to deliver the push content accordingly.
  • Content server 224 maintains and delivers the push content to the receiving parties.
  • content server 224 comprises a push content database for maintaining the push content.
  • the push content database may comprise a network jukebox.
  • content server 224 downloads the push content to a receiving party device.
  • the push content is streamed to the receiving party device. Further, depending on receiving party device capability and application logic, the push content may be transferred to the receiving party device before the call answered, during the call, or after completion of the call.
  • the content can be pushed to receiving parties that may include, for example, the calling party, the called party, or both. Ln an embodiment, the content may be pushed to a group of parties, allowing the subscriber to make a call to generate push content and send it to a group of recipients.
  • the content can be any channel of multimedia data including, but not limited to, ring tones, video tones, real-time mobile television (TV), video-casts, sport highlights and scores, jokes, audible, pictures, flash texts, a quote of the day, multimedia, news, weather, email summary, stocks, voice message callers, Over-The-Air (OTA) configuration (for example, MMS or GPRS settings, WAP settings, Push To Talk Setting, Instant Messaging Presence Setting etc), software updates, and games.
  • OTA Over-The-Air
  • the push content can be provided by a network operator, a content operator, or a service operator. Further, a single operator may provide the network infrastructure, push content, and services.
  • the push content is provided or created by subscribers who upload the content to content server 224.
  • Subscriber created content for example music, or an audible
  • Subscriber created content can be published for other subscribers to use, optionally after an administrative vetting by the content operator.
  • each download of a published subscriber created content adds an increment of value to the creator's credit.
  • the value credited may be money, or other measures of value such as redeemable bonus points.
  • the upload of the subscriber's provided or created content can be at the time of call setup for at least the current one-time usage, or done prior to call set up for possible future usage many times. The current one-time usage will also be recorded for future usage as well.
  • Configuration server 228 allows configuration of the receiving party subscription and the preference settings.
  • configuration server 228 allows configuration of the sending party subscriptions and preference settings.
  • Configuration server 228 allows for such configuration through one or more configuration interfaces.
  • Configuration interfaces may be, for example, a Wireless Application Protocol (WAP) interface, or a Web interface.
  • WAP Wireless Application Protocol
  • a subscriber of CTPCS 216 can use the web interface of configuration server 228, or customer care, to specify subscriber's device model.
  • configuration server 228 sends a WAP-push, or SMS URL, or MMS alert with URL (for example, pointing to the client software) to the subscriber's device.
  • the URL enables the subscriber to retrieve the content (for example, the client software) of the URL, where the content may optionally include a downloadable installer of the client.
  • configuration server 228 can send a SMS URL to the device to see if the device client can retrieve the URL.
  • the device profile is sent via user agent profile to content server.
  • the delivery of the SMS URL, or WAP-push URL, or MMS alert with URL is advantageously done via direct SS7 SMS delivery, rather than through the Short Message Service Center (SMSC).
  • the direct SS7 delivery can go through network interface 218 as well.
  • the push content receiving party (calling or called party or third party) needs to have a client installed on its device 230 for using the service of CTPCS 216.
  • the client is not required if the push information can be supported by standard device features (for example SMS, WAP-push etc).
  • the non-receiving party (calling or called or third party) need not have the client on their device 230. However, if the non-receiving party also has the client, it can push pre-selected content, or content selected during call setup, to the receiving party.
  • the calling party can send an item (such as a ring tone, music, an audible, an MMS, and / or other multimedia) during a call.
  • the called party can also send an item when receiving a call.
  • the client is built-in on open phone system on Smart Phone devices such as Symbian, Java/J2ME phone, Window Mobile phone, BREW phone, Palm and Trio phone etc. Therefore, the client can be used without changing device 230.
  • the client may be downloaded over the air to a Smart phone device from content server 224. It can also be downloaded from a PC connection to device 320, or from another client equipped device 320 via Bluetooth, infrared, WiFi, or any other connection. Further, the operator may choose to charge for each download / transfer of the client, or offered the client free of charge.
  • the client includes a streaming client that can play content in streamed multimedia formats. Further, the client handles call control functions to present the pushed content (via streaming or using downloaded file) upon receiving an incoming call.
  • the client operates in two modes: a download-first mode, and a streaming mode.
  • the selection of the mode of operation is made based on the bearer service of network 202 (for example, 3G), and the capability of device 230.
  • the client downloads the pushed information (for example, a ring forward tone) before presenting the information on device 230 (for example, playing or ringing).
  • the client presents the push content as it is streamed from, for example, content server 224.
  • the client can also be configured to record/file streamed media as it is being played.
  • the operator can make access to the push content a subscription based service or a one-time paying service.
  • the regulation of access to the push content may be done using Digital Rights Management (DRM) control.
  • DRM Digital Rights Management
  • the recorded / filed content may be restricted to not play offline, unless there is a DRM associated with it.
  • the DRM restricts the presentation of the pushed content to a pre-defined number of times.
  • the DRM may allow only a one-time play of ring tone. In this case, playing of the ring tone is restricted to one-time, irrespective of whether it was delivered to device 230 in the streaming mode or the download-first mode.
  • the subscriber may purchase a ring tone to store it locally for incoming call configuration. This generates further revenue for the operator.
  • Any push content stored locally by the client can be played offline (e.g. news, TV) in idle mode, or online in connected mode (e.g. inserting audibles or music in the middle of a conversation to create a rich talk experience), or in call setup mode (e.g. when the information is already on the device, there is no need to push).
  • offline e.g. news, TV
  • connected mode e.g. inserting audibles or music in the middle of a conversation to create a rich talk experience
  • call setup mode e.g. when the information is already on the device, there is no need to push.
  • the client is equipped with a presence capability to alert the PnP server 226 of availability status of device 230.
  • the client informs PnP server 226 whether device 230 is already engaged in a call or not.
  • the client has a listening server capability that listens for pushed content (e.g. ring forward tone), or a request URL for it to start retrieving content in download-first mode or steaming mode.
  • pushed content e.g. ring forward tone
  • request URL for it to start retrieving content in download-first mode or steaming mode.
  • the client may be implemented as, for example, a Java, C++, Java 2 Platform
  • the open platform may be Symbian, Windows-
  • Device 230 may be a Session
  • IP IP Multimedia System
  • SIP Session Initiation Protocol
  • IMS IP Multimedia System
  • the client can be developed through Original Equipment
  • the client may be installed on any proprietary devices, in a manner analogous to Push-To-Talk clients, and Text-input (for example, T9) clients.
  • the operator or service provider can offer the download of these clients over the air, or web, or PC.
  • the operator may couple the client with some other client functionalities such as Push-To-Talk clients, VoIP (for example, Skype, Vonage Softphone, or any SIP apparatus) clients and / or Instant Messaging (IM) clients.
  • CTPCS 216 can function in an in-band mode and an out-of-band mode. In the in-band mode, the call setup and the push content are integrated in the same bearer. In the out-of-band mode a separate voice channel and data channel may be coordinated to perform call setup and to delivery push content respectively.
  • push content can be streamed or downloaded during the call.
  • both voice and push content can be carried and played on the same IP bearer channel.
  • an all IP network for example, an IMS/SIP network infrastructure
  • One commonly available type of device 230 is a Smart Phone device, often termed as a class B terminal in GSM GPRS parlance. Many class B terminals support only simultaneous voice and data attachment, and do not support simultaneous voice and data transmission. However, while one medium is transmitting on a class B device, the signaling for either medium can happen simultaneously. In the context of the present invention, this means that while the pushed content is downloading or streaming to the client, an incoming call can come in without interrupting the downloading/streaming and playing. However as soon as the call is answered, the data (e.g. GPRS) session need be suspended for such a class B terminal.
  • GPRS data
  • an incoming call can trigger the client to play the push ring tone in streaming mode.
  • the client can suspend the streaming or downloading.
  • Such streaming of a push content introduces negligible latency in call setup, since network interface 218 does not need to suspend the call for the download duration of the push content.
  • device 230 may not support simultaneous signaling and streaming/downloading. In this case, the network interface 218 will need to hold the call until the push content is completely downloaded to device 230. Once the client acknowledges the download completion, the call setup may be allowed to continue. This embodiment may generate significant latency to call setup, particularly if the pushed information is large. However, in this embodiment, it is assured that the pushed content can be presented by the client as soon as it detects an incoming call.
  • the CTPCS 216 has a dedicated access point name (APN) for the IP bearer channel used for pushing content. In another embodiment, CTPCS 216 can share an APN with other data services (e.g. MMS, email, WAP etc).
  • the operator may waive the local packet charge for traffic to and from CTPCS 216, and just charge a flat fee or monthly subscription fee for subscription to CTPCS 216.
  • CDMA Code Division Multiple Access
  • PDC Personal Digital Cellular
  • PHS Personal Handyphone System
  • IEEE Institute of Electrical and Electronics Engineers
  • WiFi WiFi
  • WiMax IEEE 802.16
  • the database table contains a 'Channel' column that lists the push channels available to the receiving party.
  • the receiving party can select multiple channels of push content from among these available channels, to receive push content from the selected channels.
  • a 'Subscribe' column marks the selection of channels for the receiving party.
  • the receiving party has selected to receive the profile of the other call party (calling party or called party or third party), and ring forward tones.
  • Other available channels listed in the 'Channel' column include a news channel, a stock quotes channel, an email headers channel, a sports score channel, an audibles channel, and a quote of the day channel.
  • application module 222 uses a different selected channel depending on factors such as the time of a call, to determine the content to be pushed to the receiving party before the call. In another embodiment, application module 222 randomly chooses a selected channel to determine the push content for pushing to the receiving party before the call.
  • the receiving party's subscription and the preference setting can be made through the web interface or the WAP interface of configuration server 228. Alternatively, these settings can be made through the client on the receiving party's device, which in turn interacts with configuration server 228.
  • Subscriber database 220 stores the subscription profile and preference settings.
  • the database table further has a 'Configuration' column, which stores links to the appropriate configurations for the selected push channels.
  • FIG. 4 shows the configuration of the profile channel for a receiving party.
  • a 'Which party's profile' column lists the call parties whose profile may be delivered as push content, namely a calling party and a called party.
  • the receiving party has indicated a 'Y' against both calling party and called party, in a 'Subscribe' column.
  • the receiving party has chosen to receive the other party's profile both as a calling party and as a called party.
  • the exact party profile parameters for example job change, marital status change, recent activities (e.g. just came back from Amsterdam) of interest to the receiving party can be stored as a part of another configuration in subscriber database 220 through configuration server 228 and / or the client.
  • a 'Configuration' column stores link to such further configuration details, if necessary.
  • FIG. 5 shows an exemplary configuration of a ring forward tone (RFT) channel by a receiving party, in accordance with an embodiment of the present invention.
  • RFT ring forward tone
  • a 'Ring Tone Source' column lists possible sources of ring tones, namely the calling party, the called party, and the network.
  • the network may deliver ring tones to the receiving party when the receiving party is the called party or the calling party. These two cases are represented in the column as "network-to-called-party" and "network-to-calling-party" respectively.
  • the figure shows that the receiving party wants the other party defined ring tone to ring on subscriber's device both as a calling party and as a called party.
  • subscriber also subscribed to network defined ring tone to ring on his device when subscriber's device is a called party.
  • the receiving party of CTPCS 216 of an operator must be a subscriber of the operator, while the non-receiving subscriber of CTPCS 216 of an operator does not have to be a subscriber of the operator.
  • the non-receiving subscriber of CTPCS 216 of an operator does not have to be a subscriber of the operator.
  • the caller can just go to the web interface / WAP interface of configuration server 228 to configure his preference of a caller defined ring tone to ring on receiving devices that subscribe to CTPCS 216 of operator 1.
  • application module 222 decides the receiving parties based on the presence and permission information from PnP server 226. For example, pushing/forwarding of content can be restricted to presence mode, that is, when the receiving party is present / available online. Further, permissions for the push content can be defined by the receiving party when the push content is defined by the non-receiving party.
  • FIG. 6 shows an example of a general push content permission control by a receiving party against a sending party.
  • the table shows permission control settings for a plurality of sending parties listed in a 'Name' column.
  • the sending parties include four individuals (John, Cathy, Steve, and Tom), one group (Family), and a default setting (denoted in the figure by an asterisk).
  • the table stores the phone numbers of each of the four individuals in a 'Phone #' column. Further, the table stores a permission setting for each of the users in a 'Permission' column. Last, the table stores the time at which the permission setting should be applied, under a 'Time' column.
  • FIG. 7 shows a table containing group definitions of a subscriber of CTPCS 216.
  • the table shows two groups defined by the subscriber, "Family” and "CoolFriend".
  • Group “Family” contains members “Brother”, “Sister”, “Mom”, and “Dad”.
  • Group “CoolFriend” contains members "Gene” and "Rich”.
  • Each member's phone number is stored in column 'Member #'.
  • each group has an associated group pin number, stored under a 'Group # PIN ID' column.
  • such group definitions may be used to define push content permissions as shown with reference to FIG. 6.
  • these definitions allow the subscriber to use a single call setup to push information (e.g. new job, marriage invitation, new home address) to a group via a two step process.
  • the first step is to call an operator's designated group number (e.g. a 800-number so caller ID can be captured).
  • the second step is to enter the group PIN for the captured caller ID.
  • Application module 222 controls the selection of content and delivery to individual members of the group.
  • the client allows the receiving party (calling or called or third party) to configure or keep the downloaded push content.
  • the receiving party pays a fee for this facility, for example for downloaded ringtones or music.
  • the configuration or storage information can be sent to the network side under consideration by the application logic as part of its information parameters.
  • Downloaded information can also be used to trigger further download (e.g. more details after the call). For example, detailed, full MP3 music, any news not watched or read completely can be further downloaded after the call.
  • Downloaded information e.g. ring tone
  • the downloading process can be streaming-based or completely downloaded first.
  • the download process can be stopped after the call is answered, or still continues depending on the device type/capability or can resume after the call is finished if suspended during the call.
  • FIG. 8 depicts various options of supporting push content delivery to device 230 from CTPCS 216.
  • the figure shows an SMS URL option 802, a WAP URL option 804, and an MMS Alert URL option 806 to deliver push content.
  • CTPCS 216 sends device 230 a URL via SMS. In response, device 230 downloads the push content from the URL. Similarly, in WAP URL option 804 and MMS Alert URL option 806, CTPCS 216 sends device 230 a URL via WAP and MMS Alert respectively.
  • CTPCS 216 directly pushes the push content to device 230.
  • the push content is addressed to device 230 using the IP address of device 230.
  • This option can be used if device 230 is connected and present with an IP address that can be seen by CTPCS 216.
  • CTPCS 216 can not see the IP address of device 230 (for instance, due to security reasons), hi this case, the client on device 230 may send a heartbeat signal to PnP server 226 and content server 224.
  • PnP server 226 updates the presence status of device 230 in response to the heartbeat signal.
  • content server 224 checks if there is any content to be taken back by / downloaded to the client on device 230. hi this manner, various embodiments of the present invention may be deployed on network architectures where the IP address of device 230 can not be seen by CTPCS 216.
  • the client on device 230 keeps an always-on IP connection with network 202.
  • the client on device 230 is woken up by an SMS trigger (with request URL) to establish an IP connection and streaming/download push content.
  • SMS trigger with request URL
  • the former approach is quicker, since establishing an IP connection can take up to a dozen seconds in many conventional networks.
  • FIG. 9 illustrates an exemplary call flow 900 based on an originating party call control.
  • a calling party A calls a called party B.
  • calling party A is the originating party.
  • MSC Call Session Control Function - CSCF
  • MSC 208 receives the call.
  • MSC 208 passes the control of the call to network interface 218 of CTPCS 216.
  • the call control is passed with at least one call parameter.
  • the call control parameters include, but are not limited to, an application identifier (also called an AppKey), calling party A number, calling party A MSI, Called party B number, and the VMSC location of calling party A.
  • network interface 218 requests application module 222 to apply application logic by passing the call parameters obtained from network interface 218.
  • Application module 222 applies the application logic in accordance with the call parameters. In an embodiment, if the application logic determines that there is no need for the call control to wait for the delivery of the push content, application module 222 sends an acknowledgement back to network interface 218 at 908.
  • Application module 222 determines whether the application identifier corresponds to the application identifier of the calling party or the called party or both and also determines the corresponding push content details of the at least one receiving party (for example, calling party or the called party or both).
  • application module 222 sends the push content details of the at least one receiving party to content server 224 to deliver the push content.
  • network interface 218 returns the call control to MSC (or CSCF) 208.
  • network interface 218 may have an associated and configurable timer that when expires returns the call control to MSC 208.
  • network interface 218 optionally tracks some call events (e.g. call connected/answered, busy etc).
  • content server 224 establishes push content exchange with calling party A. Then at 916, content server 224 sends an acknowledgement to application module 222 indicating that the request to push content according to the details specified at 910 has been processed.
  • application module 222 applies accounting logic to produce a Call Detail Record (CDR) and returns an acknowledgement to the network interface 218.
  • Network interface 218 may pass the call control back to the MSC (or CSCF) 208 at either the first acknowledgement from the application module 222 or the second acknowledgement from the application module 222 depending on for example, whether application module 222 has determined to pass the call control to MSC (or CSCF) 208 immediately or after the push content is delivered or about to be delivered to the receiving party.
  • MSC 208 continues the call setup between calling party A and called party B. Further, the push content is played on the device of calling party A before the call is answered. [013I]FIG.
  • FIG. 10 illustrates an exemplary call flow 1000 based on a terminating party call control.
  • a calling party A calls a called party B
  • GMSC Call Session Control Function - CSCF
  • HLR Home Subscriber System - HSS
  • HLR Home Subscriber System - HSS
  • HLR Home Subscriber System - HSS
  • HLR Home Subscriber System - HSS
  • HLR Home Subscriber System - HSS
  • HLR 204 returns the subscription routing profile of called party B, for example a call control trigger profile, to GMSC (or CSCF) 206.
  • GMSC 206 passes the control of the call to network interface 218 of CTPCS 216 of the called party operator.
  • the call control is passed with at least one call parameter.
  • the call control parameters include, but are not limited to, an application identifier (also called an AppKey), calling party A number, calling party A IMSI, Called party B number, and the VMSC location of calling party A.
  • network interface 218 requests application module 222 to apply application logic by passing the call parameters obtained from network interface 218.
  • Application module 222 applies the application logic in accordance with the call parameters.
  • application module 222 optionally sends an acknowledgement back to network interface 218 at 1012.
  • Application module 222 determines whether the application identifier corresponds to the application identifier of the calling party or the called party or both and also determines the corresponding push content details of the at least one receiving party (for example, calling party or the called party or both). At 1014, application module 222 sends the push content details of the at least one receiving party to content server 224 to deliver the push content. At 1016, network interface 218 returns the call control to GMSC (or CSCF) 206 depending upon for example, whether the call control is returned by the above optional acknowledgement or whether the application logic determines to wait for the push content to be delivered or not to the receiving party.
  • GMSC or CSCF
  • network interface 218 optionally tracks some call events (for example, call connected/answered, busy, etc) from the telecommunication network for further control or for billing purpose.
  • content server 224 establishes push content exchange with called party B. Then, at 1020, content server 224 sends an acknowledgement to application module 222 indicating that the request to push content according to the details specified at 1014 has been processed.
  • application module 222 applies accounting logic to produce a Call Detail Record (CDR) and returns an acknowledgement to network interface 218.
  • CDR Call Detail Record
  • Network interface 218 may pass the call control back to the GMSC (or CSCF) 206 at either the first acknowledgement from the application module 222 or the second acknowledgement from the application module 222 depending on for example, the application logic determining whether to wait for the push content to be delivered or not.
  • GMSC (or CSCF) 206 continues the call setup between calling party A and called party B. Further, the push content is played on the device of the receiving party (e.g. the called party B in this Figure) before the call is answered.
  • FIG. 11 illustrates the signal flow 1100 of the interaction between a calling party A, a called party B and CTPCS 216 while pushing content to the called party in accordance with an embodiment of the present invention.
  • a calling party A calls a called party B.
  • MSC or CSCF 208 of the calling party operator, receives the call.
  • MSC or CSCF 208 passes the control of the call to CTPCS 216.
  • the call control is passed with at least one call parameter.
  • the call control parameters include, but are not limited to, an application identifier (also called an AppKey), calling party A number, calling party A IMSI, Called party B number, and the VMSC location of calling party A.
  • CTPCS 216 applies the application logic identified by the application identifier provided by CTPCS 216.
  • CTPCS 216 determines whether the application identifier corresponds to the application identifier of the calling party and also determines if the called party is subscribed to receive the push content. It also determines whether the called party is also subscribed to the same operator as the calling party. At 1106, CTPCS 216 returns call control to MSC (or CSCF) 208 after optionally tracking some call events (e.g. call connected/answered, busy etc). At 1108, MSC (or CSCF) 208 continues the call setup. The terminating control of the called party at GMSC (or CSCF) 206 handles the push content service as explained in FIG. 10.
  • FIG. 12 illustrates the signal flow 1200 of the interaction between a calling party A, a called party B and CTPCS 216 while pushing content to calling party A in accordance with an embodiment of the present invention.
  • a calling party A calls a called party B.
  • MSC (or CSCF) 208 of the calling party operator receives the call.
  • MSC (or CSCF) 208 passes the control of the call to CTPCS 216.
  • the call control is passed with at least one call parameter, in an embodiment, the call control parameters include, but are not limited to, an application identifier (also called an AppKey), calling party A number, calling party A IMSI, Called party B number, and the VMSC location of calling party A.
  • an application identifier also called an AppKey
  • CTPCS 216 applies the application logic identified by the application identifier provided by CTPCS 216.
  • CTPCS 216 determines whether the application identifier corresponds to the application identifier of the calling party and also determines if the called party is subscribed to receive the push content. It also determines whether called party B is from the same operator.
  • CTPCS 216 returns call control to MSC 208 after optionally tracking some call events (e.g. call connected/answered, busy etc).
  • CTPCS 216 establishes push content exchange with calling party A and applies accounting logic to produce a CDR.
  • MSC or CSCF
  • the terminating control of the called party at GMSC (or CSCF) 206 handles the push content service as explained in FIG. 11.
  • GMSC or CSCF
  • GMSC or CSCF
  • GMSC or CSCF
  • GMSC or CSCF
  • FIG. 11 Embodiments of the present invention also provide for inter-working of call setup push content services between a plurality of operators. These embodiments are described hereinafter. The description assumes that the operators involved use different mobile networks, namely a first Visited Public Mobile Network (VPMN-I) and a second Visited Public Mobile Network (VPMN-2), and have established inter-working relationship for call setup triggered push content services.
  • VPMN-I Visited Public Mobile Network
  • VPMN-2 Visited Public Mobile Network
  • FIG. 13 illustrates an exemplary signal flow 1300 depicting inter-working of call setup triggered push content service between operators for a pushed content to the called party of VPMN-2.
  • a calling party A calls a called party B.
  • Calling party A is present in a first Visited Public Mobile Network (VPMN-I) while called party B is present in a second Visited Public Mobile Network (VPMN-2).
  • MSC or CSCF
  • MSC or CSCF 208 of VPMN-I receives the call.
  • MSC or CSCF
  • MSC or CSCF 208 of VPMN-I passes the control of the call to CTPCS 216 of VPMN-I.
  • the call control is passed with at least one call parameter, hi an embodiment, the call control parameters include, but are not limited to, an application identifier (also called an AppKey), calling party A number, calling party A IMSI, Called party B number, and the VMSC location of calling party A.
  • CTPCS 216 applies the application logic identified by the application identifier provided by CTPCS 216.
  • CTPCS 216 determines whether the application identifier corresponds to the application identifier of the calling party and also determines if the called party is subscribed to receive the push content. It also determines whether the called party is from the same operator.
  • CTPCS 216 of VPMN-I returns call control to MSC (or CSCF) 208 of VPMN-I after optionally tracking some events (e.g. call connected/answered, busy etc).
  • CTPCS 216 of the VPMN-I sends an MerOperatorSend-ContentPush command to CTPCS 216 of the VPMN-2.
  • the MerOperatorSend-ContentPush command includes calling party A details, called party B details, and a content link.
  • CTPCS 216 of the VPMN-2 issues an InterOperatorRetrieveContent command to CTPCS 216 of the VPMN-I.
  • CTPCS 216 of the VPMN-2 produces the CDR for called party B, while CTPCS 216 of the VPMN-I produces the CDR for calling party A.
  • CTPCS 216 of the VPMN-I passes the call control back to MSC/CSCF of the VPMN-I while the MSC/CSCF of the VPMN-I continues the call setup.
  • FIG. 14 illustrates an exemplary signal flow 1400 depicting inter-working of call setup triggered push content service between operators for a pushed content to the called party of VPMN-2 and the calling party.
  • a calling party A calls a called party B.
  • Calling party A is present in a first Visited Public Mobile Network (VPMN-I) while called party B is present in a second Visited Public Mobile Network (VPMN-2).
  • MSC or CSCF
  • MSC or CSCF 208 of VPMN-I receives the call.
  • MSC or CSCF
  • MSC or CSCF 208 of VPMN-I passes the control of the call to CTPCS 216 of VPMN-I.
  • the call control is passed with at least one call parameter.
  • the call control parameters include, but are not limited to, an application identifier (also called an AppKey), calling party A number, calling party A IMSI, Called party B number, and the VMSC location of calling party A.
  • CTPCS 216 applies the application logic identified by the application identifier provided by CTPCS 216.
  • CTPCS 216 determines whether the application identifier corresponds to the application identifier of the calling party and also determines if the called party is subscribed to receive the push content. It also determines whether called party B is from the same operator.
  • CTPCS 216 sets up a push content exchange with calling party A.
  • CTPCS 216 of VPMN-I returns call control to MSC (or CSCF) 208 of VPMN-I after optionally tracking some call events (e.g. call connected/answered, busy etc).
  • CTPCS 216 of the VPMN-I sends an InterOperatorSend-ContentPush command to CTPCS 216 of the VPMN-2.
  • the InterOperatorSend-ContentPush command includes calling party A details, called party B details, and a content link.
  • CTPCS 216 of the VPMN-2 issues an InterOperatorRetrieveContent command to CTPCS 216 of the VPMN-I.
  • CTPCS 216 of the VPMN-2 produces the CDR for called party B, while CTPCS 216 of the VPMN-I produces the CDR for calling party A.
  • CTPCS 216 of the VPMN-I passes the call control back to MSC/CSCF of the VPMN-I while the GMSC/CSCF of the VPMN-I continues the call setup.
  • FIG. 15 depicts the inter-working of CTPCS 216 of VPMN-I and CTPCS 216 of VPMN-2 where the defined content from called party B of VPMN-2 is being pushed to calling party A of VPMN-I.
  • calling party A of VPMN-I calls called party B of VPMN-2.
  • the call proceeds to VPMN-2 and reaches GMSC (or CSCF) 206 of VPMN-2.
  • GMSC (or CSCF) 206 of VPMN-2 interacts with HLR 204 of VPMN-2 to obtain call details such as the VMSC and IMSI of called party B.
  • GMSC (or CSCF) 206 of VPMN-2 passes the call control to CTPCS 216 of VPMN-2 with call parameters including, but not limited to, an application identifier (also called an AppKey), calling party A number, Called party B number, Called party B IMSI, and the VMSC location of called party B.
  • CTPCS 216 of VPMN-2 applies application logic of AppKey on the call parameters and data from subscriber database 220. It determines that called party B has defined push content for the calling party A of VPMN-I. Further, CTPCS 216 of VPMN-2 may push content to called party B (not shown) depending on the application logic. CTPCS 216 of VPMN-2 identifies the push content defined by called party B for calling party A.
  • CTPCS 216 of VPMN-2 sends an InterOperatorSend-ContentPush command to CTPCS 216 of VPMN-I.
  • CTPCS 216 of VPMN-I returns an InterOperatorRetrieveContent command to CTPCS 216 of VPMN-2.
  • CTPCS 216 of VPMN-I produces a CDR for calling party A and VPMN-2 for inter- working charge
  • CTPCS 216 of VPMN-2 produces CDR for called party B.
  • CTPCS 216 of VPMN-I establishes a push content exchange operation with the calling party A.
  • CTPCS 216 of VPMN-I produces another CDR for calling party A.
  • CTPCS 216 of VPMN-2 passes the call control back to GMSC (or CSCF) 206 of VPMN-2.
  • GMSC (or CSCF) 206 of VPMN-2 continues the call setup.
  • the call control is passed from a telecommunication network infrastructure to CTPCS 216. Therefore, in the description of the above figures, sometimes the network interface optionally sends an acknowledgment back (i.e. returning the call control) to the telecommunication network to continue the call setup.
  • the call control may be returned to the telecommunication network infrastructure at a time that is determined by, but not limiting to, at least one of the following events: (i) after the push content has started (ii) after the push content is completed (iii) after a configurable duration has passed since start of push content (iv) for stream-able push content, after a URL is downloaded.
  • the aforementioned events may also depend upon push content channel and type.
  • the telecommunication network infrastructure timers may also be reset using IN/CAP controls to provide for a longer return of call control.
  • Ring tone forwarding relates to delivering a call party (e.g. calling or called or third party) defined ring-tone to another (or same) call party (e.g. calling or called or third party).
  • a specific instance of ring forward tone service is to deliver calling party defined ring tone to the called party.
  • News flash service relates to providing push content containing news updates.
  • Call party profile service deals with pushing profiles of the calling party or called party, or portions thereof, at the time of call setup.
  • the application of ring tone forwarding is described hereinafter with reference to FIG. 16, 17, and 18.
  • the figures illustrate three examples of ring tone forwarding applications.
  • the first example is based on called party call control for delivering calling party defined ring tones to the called party.
  • the second example is based on calling party call control for delivering called party defined ring tones to the calling party.
  • the third example demonstrates inter- working between operators where a calling party of VPMN-I " is " calling a caUed " parly " ⁇ iF operator VPMN 2 with a calling party defined ring tone that is subscribed by the called party.
  • the RFT service includes ring tone download service, personalized (color) ring back tone service, and personalized Ring Forward Tone (RFT) service.
  • the present invention allows a subscriber of the ring tone download service to download more colorful polyphonic musical ring tones onto his device so that the musical ring tone may ring on the device when the subscriber receives a call.
  • the operator of the subscriber from both bearer (e.g. GPRS) and the billing service along with the service provider and the content provider may generate revenue from the service.
  • the personalized (color) ring back tone service the present invention allows the subscriber to set colorful music as ring back tone for callers.
  • the operator of the subscriber may generate revenue in a number of ways including, but not limited to, subscription, each change of a ring back tone and the billing service. Further, the service provider and the content provider may also generate revenue. Further, the subscriber may define the ring back tone he would prefer to hear when he calling a called party.
  • the present invention allows the subscriber to dictate the colorful ring tone (audio, music, video, multimedia etc) he wishes to be played on the called party's device as long as the called party grants such permission.
  • the operator may generate revenue from for example, the subscription of the calling/called party and bearer services of one call party on receiving the dictated music ring tone from the other call party.
  • the operator may further generate revenue from each change of a musical ring tone by a call party (for example, calling party / called party).
  • the ring forward tone may also be defined by a call party (calling or called) subscriber for the other call party (called or calling).
  • the ring forward tone service may provide the called party or the calling party or both parties unexpected pleasant surprises.
  • An operator or service provider may deploy one or more of the RFT services. Furthermore, these services can be deployed across operators. [0149]
  • the ring back tone service and the ring forward tone service may also help the operator and the content/service provider to publicize (for example, a viral marketing) the popular ring tones among the called parties and the calling parties.
  • the ring forward tone service plays the ring tone at the called party's device side or the calling party's device side or both.
  • the operator/service/content providers get revenue opportunities for example, when the receiving parties (called or calling or third party) of the ring forward tones decide to actually save or install the ring tone on the device after the first playing.
  • Digital Right Management may help to facilitate the revenue generating process.
  • the operator can make additional revenue when the subscribed call (calling or called) party chooses to pass the ring forward tone as a gift to the other call (called or calling) parties.
  • the ring forward tone service however requires a client in the receiving party device.
  • the client may be a downloadable (for example, Symbian, Java, Linux, Window, Brew, etc) to the device.
  • the client may control permission of the call parties allowed to dictate ring tone on the subscriber's device.
  • the ring forward tone may be an identification of the caller/callee for example, by style or type of music or a particular music or seasonal greetings or special days (e.g. anniversary, birth day etc) or humor.
  • the ring forward tone service also facilitates the calling party to hear a called party defined ring tone. For example, when A calls B, A could hear B's ring tone pushed to A's device as music, video, text, voice or jokes.
  • a ring forward tone may be sent to both calling and called parties simultaneously.
  • the ring forward tone for each receiving party may be network defined (e.g. from the jukebox) or defined by the receiving party (e.g. category of ring tone) or defined by the other call party in a call.
  • the RFT client may have a turn on/off switch to allow the receiving (e.g. called or calling or third) party to temporary switch off the ring forward tone service and let his/her device take over the control of a ring tone without changing any calling party's permission. This might be helpful in avoiding embarrassing situations.
  • the RFT client may detect if the receiving party device is in a silent mode or not and pass the information to the Presence and Permission server. The Presence and Permission Server in turn informs the content server either not to send a ring forward tone or send a URL for future retrieval if the ring forward tone is a gift from the calling party.
  • me jcsj i cneni may a ⁇ ow me nostmg party (e.g. called or calling) device to screen a changed ring forward tone or pre-verify it for the other call party (e.g. calling or called) before allowing the other call party to have the ring forward tone ringing on the receiving party's device for all future calls.
  • me nostmg party e.g. called or calling
  • the other call party e.g. calling or called
  • the operator may send WAP push or SMS to the subscribers with a URL to download the client and may also explain the RPT service.
  • the subscription procedure of the RFT service of a mobile operator for a subscriber may also require registration of the subscriber using a web service or a customer care service.
  • the RFT service may send a WAP push or SMS URL to the device.
  • the RFT service subscriber can then retrieve the URL to download the client to the device.
  • the RFT service subscriber can also indicate who else can download such a client to the RFT service.
  • the RFT service can track who has downloaded the client.
  • each RFT service subscriber may need a permission to download the client to help build up the critical mass.
  • the RFT service subscriber may have the added incentive to select, change and test ring forward tone any time. This may allow the subscriber to call the called party with one-time ring tone and to gift a ring tone to the called party.
  • the RFT service subscriber can also use the same client to select, change and test ring back tone.
  • the RFT subscriber can also use the same client to test, upload/record and download the ring tone or MP3 music.
  • the RFT service subscriber may be charged for sending a RFT as a gift to the called party using the client.
  • ring back tone service is a purely network-based service that does not requires any device changes and works across networks, however, it is expensive to play ring back tone using voice circuit resources as sometimes the resources are tied up and the call is connected without switch changes.
  • the RFT service using data bearer to play the ring forward tone is a much more cheaper proposition.
  • the RFT subscriber may avail any of the aforementioned services (e.g. select, change and test ring back tone, ring forward tone or just download ring tone/music etc). Also, it provides the operator further data revenue opportunities over the data bearer.
  • the data bearer usage itself for RFT can be ( ,rome, v/ ⁇ .
  • a free SMS URL can be sent to the called (or calling) device in the name of the sending party provided the sending party has given such permission which can be the default at the time of subscription.
  • the device supports web/WAP URL retrieval, the user agent profile is revealed to the content server for retrieving the right client (Symbian, Window Mobile or BREW etc) to the device.
  • ring forward tone service includes, but not limited to, the following:
  • the ring forward tone can be a music tone, a multi-media streaming, a MMS, a picture show, a video show, a personal announcement, a celebrity voice, humor recording, a signature music tone, and the like.
  • the RFT subscriber or call (calling or called) party can record their own personal video, music, picture show and MMS to be stored/uploaded in the network for streaming to the called party.
  • a RFT subscriber may specify a ring forward tone to be gifted to the calling/called party either via an IYR interface or by using the RFT client on the device or by using the dialing prefix/postfix to indicate the choice of the ring tone.
  • the calling party can preset a ring forward tone as a part of subscription.
  • the calling party can also use a one-time trigger to select a ring forward tone by prefixing or postfixing the dialed number or a USSD command or a web interface or a IVR or WAP (etc) before the call to reserve a ring forward tone for next call.
  • the RFT service may be deployed in an enterprise environment for a corporation. In this model, an enterprise can mandate its company employees during working hours to use company-oriented ring forward tones (e.g. promotion and ads) when the employees make or receive a call. The RFT service may be used by the enterprise for advertising purpose for either employee or general public.
  • the RFT service might involve playing a company designated music on the called parties of an employee during the office hours while at other times the employee may avail free ring forward tone service.
  • the enterprise might promote its advertising by playing a short company music tone in front of a subscriber.
  • the enterprise might offer/sponsor the ring forward tone service for free.
  • the receiving RFT subscriber device contains a client, it is possible for the subscriber to upload a musical ring tone at the content server for streaming the musical ring tone to the called party either at the time of the call or before the call is made.
  • the call (called or calling) party who receives a ring forward tone in a call can store, configure or purchase the RFT or subscribe the RFT to be heard by his called party using the client.
  • the RFT service allows a subscriber to download a RFT when the RFT receiving party (called or calling or third) hears the ring tone ringing on the device.
  • the RFT service may be integrated with music download service such as iTune. Since a short term (e.g. 15 sees) ring tone snippet can act as a test run to entice the receiving party to download the actual MP3 music equivalent of the ring tone in one click.
  • the RFT service essentially makes the device even a better tool for MP3 player because of the ease of trying out a snippet (from a ring forward tone) and the ease of downloading a MP3 music equivalent of the ring tone.
  • the ring forward tone service may be availed by wireless cellular operators and subscribers. Further it can be availed by the fixed line or internet operators (WiFi, WiMax, DSL, Cable modem etc), particularly in VoIP.
  • the VoIP client can be SIP based (e.g. GIZMO) or operator-defined (e.g. Skype).
  • GIZMO GIZMO
  • Skype open API a client that enables the calling party to dictate a ring forward tone that is sent out of band to the called party Skype client may be developed which can then stream in the incoming ring forward tone as a ring tone in addition to setting permissions to allow or disallow ring forward tone from certain callers.
  • a client that enables the calling party to receive a ring forward tone that is sent out of band from the called party Skpye client may be developed so that the calling Skype client can play the ring forward tone as a ring tone while waiting for the called party to answer.
  • the call (calling or called) party can subscribe to the RFT service via calling to rVR/Call-Center/Customer-care or internet/web as a subscriber of a fixed line operator (cable provider, RBOC etc).
  • the call (calling or called) device can be any phone device for example, a VoIP device with the RFT client.
  • the called party's device in the fixed line world must be able to receive the ring forward tone.
  • the receiving party device has a packet data connection to receive the ring forward tone.
  • the present invention supports IMS deployment strategies which integrate fixed line world with VoIP phone.
  • the RFT service can be such an IMS service for these fixed line/wireless combo-operators.
  • the RFT client may provide configuration options to grant personalized permissions to allow callers ring tone to ring on the receiving party devices when the receiving party devices receive calls from these callers.
  • the client can be integrated with presence and permission information to enable the subscriber to control when to allow ring forward tone service from callers.
  • the client can also maintain a constant IP connection/session so incoming calls' ring forward tones can be seamlessly streamed before they are answered.
  • a call (calling or called) party subscribes to an RFT service
  • the subscriber can get a jukebox of ring forward tones like yahoo music subscription at a monthly fee X from the operator.
  • the jukebox may send a ring forward tone to the subscribed called party, unless configured to be overwritten by the subscriber for that calling number.
  • the jukebox may send a ring forward tone to the subscribed calling party, unless configured to be overwritten by the subscriber for that called number.
  • each selection of an RFT for a party may have a monthly charge and a one-time fee although both may be free.
  • the receiving party has to be a subscriber of the operator allowing the RFT service.
  • the other call party has to be the operator subscriber if charged; otherwise the other call party can be subscribed to any other operator (other mobile, fixed).
  • the subscriber can get premium RFTs while the other operators (mobile or fixed line)' s subscribers can only freely set non-premium RFTs.
  • the source of the ring tone ringing on a calling party device can be defined by the network, by the called party or by the calling party at the network.
  • the source of the ring tone ringing on a called party device can be defined by the network, by the calling party at the network or by the called party at the network.
  • the application of ring tone forwarding is described hereinafter with reference to FIG. 16, 17, and 18.
  • the figures illustrate three examples of ring tone forwarding applications. The first example is based on called party call control for delivering calling party defined ring tones to the called party.
  • the second example is based on calling party call control for delivering called party defined ring tones to the calling party.
  • the third example demonstrates inter-working between operators where a calling party of VPMN-I is calling a called party of operator VPMN 2 with a calling party defined ring tone that is subscribed by the called party.
  • FIG. 16 illustrates a call flow 1600 depicting called party call control for delivering calling party defined ring tones to the called party in accordance with an embodiment of the present invention.
  • the call flow described in the figure assumes that a called party B has installed the client on the device, and that calling party A has set up the ring forward tone for called party B's device.
  • calling party A calls called party B.
  • This call setup request reaches GMSC 206 of called party B.
  • calling party A does not have to be a subscriber of the operator of called party B.
  • GMSC 206 queries HLR 204 of called party B via Mobile Application Part (MAP) Send Routing Information (SRI) command, to get a call trigger profile.
  • SRI Send Routing Information
  • HLR 204 of called party B returns Terminating - CAMEL Subscription Information (T-CSI) for called party B to GMSC 206.
  • T-CSI Terminating - CAMEL Subscription Information
  • GMSC 206 passes the call control via Intelligent Network/CAMEL Application Part (IN/CAP) Initial Detection Point (IDP) to network interface 218 of CTPCS 216 of the called party network, with at least one call parameter.
  • network interface 218 requests application module 222 to apply the Ring Forward Tone application logic.
  • Application module 222 uses the call parameters and data from subscriber database 220 to determine that a ring tone defined by calling party A needs to be pushed to called party B, where called party B is a subscriber of the calling party defined ring tone service. At 1612, application module 222 optionally sends an acknowledgement to network interface 218 depending upon whether it is set by the operator or whether the application module determines to wait for the delivery of the push content or not.
  • application module 222 sends an instruction to content server 224 to push content.
  • the instruction includes push content details which may include, but are not limited to, an indication of called party B as the recipient of the push content, and a ring tone content ID.
  • content server 224 requests presence and permission server 226 for Internet Protocol (IP) address information of called party B.
  • IP Internet Protocol
  • presence and permission server 226 returns the IP address of called party B to content server 224.
  • content server 224 establishes a push content exchange operation to deliver the ring tone to called party B.
  • content server 224 sends an acknowledgement to application module 222.
  • application module 222 sends an acknowledgement to network interface 218.
  • network interface 218 issues an Intelligent Network (ESf) CONTINUE command to GMSC 206.
  • network interface 218 issues the IN CONTINUE command to GMSC 206 in response to the first acknowledgement received from application module 222 after 1612.
  • GMSC 206 continues the normal call setup.
  • the client at called party B starts to play the pushed ring tone right after receiving it, or in other words after 1620. In another embodiment, the client at called party B starts to play the pushed ring tone at the incoming call, or in other words after 1628.
  • the client at called party B also interacts with a device call management menu to detect acceptance, rejection, or silencing of the call by called party B. Accordingly, the client will stop playing the ring tone if the called is accepted, rejected, or silenced.
  • a racing condition may occur if two simultaneous calls are received by called party B from different calling parties, hi an embodiment, to avoid the racing condition, the client may check the Caller ID of the incoming call to match with the pending ring forward tone session to play, in case there are more than one ring forward tone sessions pending. Even though there is one ring forward tone session pending, it could be possible that another simultaneous call without a ring forward tone control can come in. Therefore, in case the caller ID for the simultaneous incoming calls is unknown, the client may have a default configuration to address such a case. For example, one default configuration could be that if there is a pending ring forward tone session, the client will play the ring forward tone, even though caller ID is unknown.
  • FIG. 17 illustrates a call flow 1700 depicting calling party call control for delivering a called party defined ring tone to the calling party in accordance with an embodiment of the present invention. The call flow assumes that calling party A has installed the client on the device, and that called party B has set up the ring forward tone for calling party's device.
  • calling party A calls called party B and the call setup request reaches MSC 208.
  • MSC 208 passes the call control via IN/CAP IDP to network interface 218, with at least one call parameter.
  • network interface 218 requests application module 222 for applying application logic.
  • Application module 222 uses the call parameters from network interface 218 and data from subscriber database 220 to determine that a ring tone define by called party B needs to be pushed to calling party A.
  • application module 222 may optionally send an acknowledgement to network interface 218 depending on whether the operator sets or the application module determines to wait for the delivery of the push content or not. Upon receiving this acknowledgement, at 1710, network interface 218 may issue an CONTINUE command to MSC 208.
  • application module 222 instructs content server 224 to push content.
  • the instruction includes push content details which may include, but are not limited to, an indication of calling party A as the recipient of the push content, and a ring tone content ID.
  • content server 224 optionally requests presence and permission server 226 for Internet Protocol (IP) address information of calling party A, and retrieves this information.
  • IP Internet Protocol
  • content server 224 establishes a push content exchange operation to deliver the ring tone to calling party A.
  • content server 224 sends an acknowledgement to application module 222.
  • application module 222 generates a CDR and sends an acknowledgement to network interface 218.
  • network interface 218 had not issued an CONTINUE command to MSC 208 at 1710, it does so at this stage. Then at 1722, MSC 208 continues the normal call setup.
  • the client on the device of calling party A starts to play the pushed ring tone right away or when it receives an indication of the call ringing.
  • the client also interacts with the device call management menu for accepting or rejecting the call. Upon accepting or rejecting, the client will stop playing the ring forward tone.
  • FIG. 18 illustrates a call flow 1800 depicting inter-working between operators where a calling party of VPMN-I is calling a called party of operator VPMN-2 with a calling party defined ring tone that is subscribed by the called party in accordance with an embodiment of the present invention.
  • the call flow assumes that calling party A has also set up the ring forward tone for the called party's device.
  • calling party A of VPMN-I calls called party B of VPMN-2.
  • the call setup request is received by MSC 208 of VPMN-I.
  • MSC 208 of VPMN-I passes the call control via IN/CAP IDP command to CTPCS 216 of VPMN-I.
  • the IDP command includes at least one call parameter.
  • CTPCS 216 of VPMN-I uses the call parameters from MSC 208 of VPMN-I and data from subscriber database 220 of VPMN-I to determine that a ring tone defined by calling party A needs to be pushed to called party B, where called party B is a subscriber of calling party defined ring tone service and called party B is from VPMN-2.
  • VPMN-2 has CTPCS 216, and a ring forward tone inter- working relationship with VPMN-I.
  • CTPCS 216 of VPMN-I sends the ring tone defined by calling party A for called party B to the CTPCS 216 of VPMN-I.
  • CTPCS 216 of VPMN-I acknowledges the receipt of the calling party defined ring tone and produces the CDR.
  • CTPCS 216 of VPMN-I produces the CDR and issues CONTINUE to MSC 208 of VPMN-I at 1808.
  • CTPCS 216 of VPMN-I sends inter-operator send content push command to CTPCS 216 of VPMN-2 to facilitate inter-working between the operators at 1810.
  • CTPCS 216 of VPMN-2 issues inter-operator retrieve content command and applies accounting logic to produce CDR of the called party at 1812.
  • FIG. 19 describes the news flash service of the CTPCS with respect to a subscriber each time the subscriber makes a call in accordance with an embodiment of the present invention.
  • the subscriber includes a calling party, a called party or any individual who has subscribed to the service.
  • the embodiment describes the delivery of the news flash service when the subscriber makes a call, similar service may be defined when a subscriber receives a call.
  • the news flash includes text, TV, video or multimedia content.
  • the signaling flow may be based on an originating IN. In another embodiment, the signaling flow may be based on O-CSI-like implementation.
  • calling party A calls called party B.
  • MSC 208 passes the call control via IN IDP (CAP. INAP etc) command to network interface 218.
  • the IDP command includes at least one call parameter.
  • the network interface 218 requests instruction from application module 222 by passing the call parameters at 1906.
  • the application module 222 applies the application logic identified by the serviceKey using the data from network interface 218 and subscriber database 220 and optionally sends an acknowledgement back to network interface 218 depending on for example, whether application module 222 determines to wait for the delivery of the push content or not at 1908.
  • network interface 218 may issue an IN CONTINUE command to MSC 208.
  • the application module 222 determines whether the calling party has subscribed to the news flash service. It also determines the calling party to push content to (in this example, application module 222 determines the calling party, however, in other embodiments the application module may determine the called party or both) and the news flash content ID and sends the push content details to content server 224 at 1912.
  • content server 224 may communicate with PnP 226 to obtain the IP address of the calling party for establishing push content exchange at 1914.
  • the content server 224 establishes push content exchange with the calling party at 1916 in accordance with various embodiments described above.
  • the content server 224 returns an acknowledgement to application module 222 at 1918, which in turn produces a CDR of the calling party by applying accounting logics.
  • the application module 222 returns an acknowledgement to network interface 218 at 1920.
  • the network interface 218 may pass the call control back to the MSC 208 using BSf CONTINUE at either the first acknowledgement (1910) from application module 222 (for example, in streaming mode of push content) or the second acknowledgement from application module 222.
  • the MSC 208 may continue the call setup at 1922.
  • the calling party device client plays the news flash content before the call is answered.
  • FIG. 20 illustrates profile information of a call party pushed to the other call party in either or both directions in accordance with an embodiment of the present invention.
  • calling party A calls called party B.
  • the call reaches GMSC/CSCF 206 of the operator of the called party.
  • the GMSC/CSCF 206 issues SendRoutingMormation SRI to HLR 204 of the called party at 2004.
  • the HLR 204 returns IN/CAMEL trigger profile to GMSC/CSCF 206 at 2006.
  • GMSC/CSCF 206 passes the call control via IN IDP (CAP. INAP etc) command to network interface 218.
  • the IDP command includes at least one call parameter.
  • the network interface 218 requests instruction from application module 222 by passing the call parameters at 2010. [0192]
  • the application module 222 applies the application logic identified by the serviceKey using the data from network interface 218 and subscriber database 220 and optionally sends an acknowledgement back to network interface 218 depending on for example, whether application module 222 determines to wait for the delivery of the push content or not at 2012.
  • network interface 218 may issue an IN CONTINUE command to GMSC/CSCF 206.
  • the application module 222 determines whether the called party has subscribed to the calling party profile service. It obtains the calling party A profile content ID which may be obtained by filtering both calling party A and called party B profiles. For example, calling party A might have blocked his marriage status from access by called party B while called party B might not wish to know calling party A's job status.
  • the application module 222 determines the called party B to push content to (in this case, the called party, but it can also be calling party or both) and the calling party A profile content ID and sends them to content server 224 to push at 2016.
  • content server 224 may communicate with PnP 226 to obtain the IP address of the called party for establishing push content exchange at 2018. PnP 226 returns the IP address of the called party at 2020.
  • the content server 224 establishes push calling party profile exchange with the called party at 2022 in accordance with various embodiments described above. [0194]The content server 224 returns an acknowledgement to application module 222 at 2024, which in turn produces a CDR of the called party by applying accounting logics. The application module 222 returns an acknowledgement to network interface 218 at 2026. The network interface 218 may pass the call control back to GMSC/CSCF 206 using IN CONTINUE at either the first acknowledgement (2012) from application module 222 (for example, in streaming mode of push content) or the second acknowledgement from application module 222. The GMSC/CSCF 206 may continue the call setup at 2028. The called party device client plays the calling party profile before the call is answered or at the incoming call.
  • FIG. 21 illustrates the signal flow of the profile of called party being sent to the subscribed calling party in accordance with an embodiment of the present invention.
  • the signal flow may be based on an originating IN.
  • the signaling flow may be based on O-CSI-like implementation.
  • calling party A calls called party B.
  • the MSC 208 passes the call control via IN IDP (CAP. INAP etc) command to network interface 218 at 2104.
  • the IDP command includes at least one call parameter.
  • the network interface 218 requests instruction from application module 222 by passing the call parameters at 2106.
  • the application module 222 applies the application logic identified by the serviceKey using the data from network interface 218 and subscriber database 220 and optionally sends an acknowledgement back to network interface 218 depending on for example, whether application module 222 determines to wait for the delivery of the push content or not at 2108.
  • network interface 218 may issue an ESf CONTINUE command to MSC 208.
  • the application module 222 ucLcri ⁇ mes wnemer me caning party nas suDsc ⁇ oe ⁇ to me called party pro ⁇ ile service. It obtains the called party B profile content ID which may be obtained by filtering both calling party A and called party B profiles.
  • called party B might block his marriage status from access by calling party A while calling party A might not wish to know called party B's job status. Further, calling party A can also filter out the called party B as a whole since calling party A is not interested in called party B profile at all.
  • the application module 222 determines the calling party A to push content to (in this case, the calling party, but it can also be called party or both) and the called party B profile content ID and sends them to content server 224 to push at 2112.
  • content server 224 may communicate with PnP 226 to obtain the IP address of the called party for establishing push content exchange at 2114. PnP 226 returns the IP address of the called party.
  • the content server 224 establishes push called party profile exchange with the calling party at 2116 in accordance with various embodiments described above. [0198]The content server 224 returns an acknowledgement to application module 222 at 2118, which in turn produces a CDR of the calling party by applying accounting logics. The application module 222 returns an acknowledgement to network interface 218 at 2120. The network interface 218 may pass the call control back to MSC 208 using ESf CONTINUE at either the first acknowledgement (2108) from application module 222 (for example, in streaming mode of push content) or the second acknowledgement from application module 222. The MSC 208 may continue the call setup at 2122. The calling party device client plays the called party profile before the call is answered or at the incoming call.
  • the call setup push content service follows a normal call setup for phone conversations.
  • the present invention allows a call party (calling or called) or network (based on called party's subscription) dictated content (e.g. ring tone, news, profiles, stock scores, weather updates, video, music, audible, multimedia messages, email headlines etc) to be pushed to either a calling party or a called party or a third party and played by a client on the receiving party device instead of playing the locally pre-stored content (e.g ring tones, pictures, videos etc) on the device configured by the called party.
  • the call setup push content service does not require a special client on a non-receiving device, rattier it requires a special client on the receiving device only.
  • an operator may control the content to be pushed to the receiving party device. For example, the caller will not be able to make indecent/compromising remarks to the receiving party as opposed to Push-To-Talk service. Further, the operator permits a subscriber to upload his/her own recorded thing (music, voice, video etc) to the CTPCS, however, the operator may opt to check out the content first before allowing it on the CTPCS.
  • the call setup push content service however can leverage the push to talk architecture to facilitate the deployment of the call setup push content service.
  • the client present on the calling device in the push to talk architecture can also be used to transfer the push content from the calling device to the called device or vice versa in a call setup.
  • the operator may lose control of the push content.
  • the inter- working push to talk architecture may be used as a foundation for the inter-working of the call setup push content service.
  • the ring forward tone service is part of a normal call setup while the push to talk service bypasses any call setup.
  • the ring forward tone service is network controlled ring tone onto the receiving device, while the push to talk service is push-to- talking party's controlled conversation onto the receiving device. While the push to talk service requires clients on both the calling and the called party devices, the ring forward tone service only requires client on the receiving party device.
  • the push to talk architecture may form the basis for a possible option of implementing the ring forward tone service.
  • the push to talk architecture may provide presence and availability and contact management which form the basis for the ring forward service client on the receiving party device.
  • the push to talk service can theoretically push/stream any media to the receiving party device as opposed to the ring forward tone service of the present invention in which the RFT can be such a media.
  • the push to talk architecture can provide another form of ring forward tone service, namely, the calling/called party device with a push to talk client can be extended to send ring tone stored on the device to the CTPCS before streaming down to the receiving party device in parallel to a normal call setup.
  • the push to talk client can help to deliver caller ID end-to-end in an out of band IP communication.
  • the examples under the present invention are described using terms and constructs drawn largely from GSM mobile telephony infrastructure. However, use of these examples should not be interpreted to limiting the invention to those media.
  • the capabilities of the visited or non-accustomed network can be of use and provided through any type of telecommunications medium, including without limitation: (i) any mobile telephony network including, without limitation, GSM, 3GSM, 3G, CDMA, WCDMA or GPRS, satellite phones or other mobile telephone networks or systems; (ii) any so-called WiFi apparatus normally used in a home or subscribed network, but also configured for use on a visited or non-home or non-accustomed network, including apparatus not dedicated to telecommunications such as personal computers, Palm-type or Windows Mobile devices; (iii) an entertainment console platform such as Sony Playstation, PSP or other apparatus that are capable of sending and receiving telecommunications over home or non-home networks, or even (iv) fixed-line devices made for receiving communications,
  • this specification follows the path of a telecommunications call from a calling party to a subscriber or calling party.
  • the present invention provides push content at an attention catching event to the receiving parties and provides richer applications. Further, the content can be pushed to multiple parties and monitored by monitoring services.
  • that call can be for a normal voice call, in which the subscriber telecommunications equipment is also capable of visual, audiovisual or motion-picture display. Alternatively, those devices or calls can be for text, video, pictures or other communicated data.
  • ITU-T Recommendation Q.764 (1999), Signaling system No. 7 - ISDN user part signaling procedures.
  • ITU-T Recommendation Q.766 (1993), Performance objectives in the integrated services digital network application.

Abstract

La présente invention se rapporte à un procédé permettant de distribuer un contenu poussé lancé par l'établissement d'un appel à au moins une partie réceptrice par l'intermédiaire d'un premier réseau de télécommunication. Le procédé selon l'invention consiste à exécuter une fonction de commande d'appel, en réponse à l'établissement d'un appel effectué par une partie appelante à l'intention d'une partie appelée. La fonction de commande d'appel fonctionne sur au moins un paramètre d'appel. Le procédé consiste également à appliquer une logique d'application en fonction dudit paramètre d'appel, afin de déterminer ladite partie réceptrice et les détails du contenu poussé de ladite partie réceptrice, et à distribuer le contenu poussé spécifié par les détails de contenu poussé à ladite partie réceptrice. Le procédé se rapporte également à l'interfonctionnement entre des opérateurs, lorsque les parties appelante et appelée sont des abonnés d'opérateurs différents.
PCT/US2006/021312 2005-05-31 2006-05-31 Procede et systeme pour contenu pousse lance par l'etablissement d'un appel WO2006130783A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
BRPI0611016-9A BRPI0611016A2 (pt) 2005-05-31 2006-05-31 método e sistema para proporcionar uma ativação de chamada disparada por conteúdo push para pelo menos uma parte receptora através de uma primeira rede de telecomunicações
EP06760629A EP1889428A4 (fr) 2005-05-31 2006-05-31 Procede et systeme pour contenu pousse lance par l'etablissement d'un appel

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US59503205P 2005-05-31 2005-05-31
US60/595,032 2005-05-31

Publications (2)

Publication Number Publication Date
WO2006130783A2 true WO2006130783A2 (fr) 2006-12-07
WO2006130783A3 WO2006130783A3 (fr) 2007-10-11

Family

ID=37482325

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/021312 WO2006130783A2 (fr) 2005-05-31 2006-05-31 Procede et systeme pour contenu pousse lance par l'etablissement d'un appel

Country Status (4)

Country Link
EP (1) EP1889428A4 (fr)
CN (1) CN101273594A (fr)
BR (1) BRPI0611016A2 (fr)
WO (1) WO2006130783A2 (fr)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008083087A2 (fr) * 2006-12-26 2008-07-10 Kent Carl E Procédés et systèmes de distribution de contenu personnalisée à des dispositifs de télécommunication
WO2008090553A2 (fr) * 2007-01-22 2008-07-31 Yossi Glazer Système et procédé d'envoi de contenu numérique vers un dispositif mobile
US7421067B2 (en) 2006-04-19 2008-09-02 Emotive Communications, Inc. System and methodology for peer-to-peer voice communication employing a pushed interactive multimedia announcement
CN101822035A (zh) * 2007-12-27 2010-09-01 株式会社Ntt都科摩 服务器装置及消息发送方法
CN101835135A (zh) * 2010-03-30 2010-09-15 中兴通讯股份有限公司 一种实现语音呼叫视频化业务的系统和方法
EP2249554A1 (fr) * 2008-03-04 2010-11-10 Huawei Technologies Co., Ltd. Procédé et appareil pour réaliser une tonalité de retour d'appel caractéristique dans une session à correspondants multiples
CN102083017A (zh) * 2010-12-31 2011-06-01 东莞宇龙通信科技有限公司 天气信息的发送方法、系统及移动终端
EP2408164A1 (fr) * 2009-04-15 2012-01-18 ZTE Corporation Système d'affichage, procédé et serveur de service de ressource multimédia
EP2169895A4 (fr) * 2007-12-27 2012-02-22 Huawei Tech Co Ltd Procédé de contrôle d'appel, système de communication et dispositif associé
US8874086B2 (en) 2008-02-07 2014-10-28 Microsoft Corporation Providing relevant advertisements or other content based on a communications identifier
WO2016072736A1 (fr) * 2014-11-04 2016-05-12 Lg Electronics Inc. Procédé et appareil pour gérer un réglage de préférence pour des informations de niveau de confiance d'une identité d'appelant dans un système d'accès sans fil

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5628296B2 (ja) * 2009-05-04 2014-11-19 テレフオンアクチーボラゲット エル エム エリクソン（パブル） セッションプッシュ伝送
CN102685680A (zh) * 2011-03-16 2012-09-19 中兴通讯股份有限公司 广告推送方法及系统
CN103067881B (zh) * 2011-10-18 2015-07-29 深圳市哗宇通网络技术开发有限公司 一种基于信令的内容推送方法和系统
CN103401890B (zh) * 2012-06-14 2017-03-01 微软技术许可有限责任公司 用于通信事件的通知的装置和方法
GB201210598D0 (en) 2012-06-14 2012-08-01 Microsoft Corp Notification of communication events
GB201210596D0 (en) 2012-06-14 2012-08-01 Microsoft Corp Notification of communication events
GB201210600D0 (en) 2012-06-14 2012-08-01 Microsoft Corp Call invites
CN102855596A (zh) * 2012-07-13 2013-01-02 陶雨 一种居家养老服务综合调度系统及调度方法
CN102932760A (zh) * 2012-10-29 2013-02-13 北京小米科技有限责任公司 一种建立通话的方法、装置及设备
CN103905488B (zh) * 2012-12-26 2018-10-12 中国移动通信集团公司 一种移动终端广告投放方法和设备
CN104281957A (zh) * 2013-07-03 2015-01-14 壹源泉（福建）传媒有限公司 智能手机用户收费看广告的方法
CN103813031B (zh) 2014-02-18 2018-09-04 北京智谷睿拓技术服务有限公司 呼叫处理方法及装置
CN104092838A (zh) * 2014-07-09 2014-10-08 华为技术有限公司 传输信息的方法、服务器及终端
CN104468556B (zh) * 2014-12-01 2018-01-19 华为技术有限公司 一种推送业务的实现方法及设备
CN104469015A (zh) * 2014-12-12 2015-03-25 郑明� 移动终端上展示业务信息的方法及设备
CN106713381A (zh) * 2015-08-20 2017-05-24 上海触乐信息科技有限公司 推送服务信息的方法、装置和用户设备
CN105491526A (zh) * 2015-12-14 2016-04-13 西安大唐电信有限公司 一种基于SmallCell的移动互联网内容智能推送系统及实现方法
WO2018115351A1 (fr) * 2016-12-23 2018-06-28 Koninklijke Philips N.V. Système de traitement du ronflement parmi au moins deux utilisateurs
CN110661920B (zh) * 2019-09-27 2021-01-12 北京巨象具象科技有限公司 一种预制数据传播方法、装置和电子设备
CN110661926B (zh) * 2019-09-27 2021-07-06 北京巨象具象科技有限公司 一种预制数据传播方法、装置和电子设备
CN111131315B (zh) * 2019-12-31 2023-04-07 西安抱朴通信科技有限公司 一种会话连接方法、设备及介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040236836A1 (en) 2003-03-03 2004-11-25 Barry Appelman Recipient control of source audio identifiers for digital communications
US20050073999A1 (en) 2002-05-13 2005-04-07 Bellsouth Intellectual Property Corporation Delivery of profile-based third party content associated with an incoming communication

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6671370B1 (en) * 1999-12-21 2003-12-30 Nokia Corporation Method and apparatus enabling a calling telephone handset to choose a ringing indication(s) to be played and/or shown at a receiving telephone handset
AUPR690701A0 (en) * 2001-08-10 2001-08-30 Redpoint Pty Ltd A system and method for customising call alerts
EP1398943A1 (fr) * 2002-09-16 2004-03-17 Koninklijke KPN N.V. Système de télécommunication
US20050047362A1 (en) * 2003-08-25 2005-03-03 Motorola, Inc. System and method for transmitting caller information from a source to a destination
EP1592216A1 (fr) * 2004-04-29 2005-11-02 Hewlett-Packard Development Company, L.P. Distribution de contenu pendant l'établissement d'une communication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050073999A1 (en) 2002-05-13 2005-04-07 Bellsouth Intellectual Property Corporation Delivery of profile-based third party content associated with an incoming communication
US20040236836A1 (en) 2003-03-03 2004-11-25 Barry Appelman Recipient control of source audio identifiers for digital communications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1889428A4

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7421067B2 (en) 2006-04-19 2008-09-02 Emotive Communications, Inc. System and methodology for peer-to-peer voice communication employing a pushed interactive multimedia announcement
WO2008083087A2 (fr) * 2006-12-26 2008-07-10 Kent Carl E Procédés et systèmes de distribution de contenu personnalisée à des dispositifs de télécommunication
WO2008083087A3 (fr) * 2006-12-26 2008-10-02 Carl E Kent Procédés et systèmes de distribution de contenu personnalisée à des dispositifs de télécommunication
WO2008090553A2 (fr) * 2007-01-22 2008-07-31 Yossi Glazer Système et procédé d'envoi de contenu numérique vers un dispositif mobile
WO2008090553A3 (fr) * 2007-01-22 2010-02-25 Yossi Glazer Système et procédé d'envoi de contenu numérique vers un dispositif mobile
CN101822035A (zh) * 2007-12-27 2010-09-01 株式会社Ntt都科摩 服务器装置及消息发送方法
CN101822035B (zh) * 2007-12-27 2013-01-30 株式会社Ntt都科摩 服务器装置及消息发送方法
US8467771B2 (en) 2007-12-27 2013-06-18 Ntt Docomo, Inc. Server apparatus and message transmission method
EP2169895A4 (fr) * 2007-12-27 2012-02-22 Huawei Tech Co Ltd Procédé de contrôle d'appel, système de communication et dispositif associé
CN105678592A (zh) * 2008-02-07 2016-06-15 微软技术许可有限责任公司 基于通信标识符提供相关广告或其它内容
US8874086B2 (en) 2008-02-07 2014-10-28 Microsoft Corporation Providing relevant advertisements or other content based on a communications identifier
EP2249554A4 (fr) * 2008-03-04 2012-01-04 Huawei Tech Co Ltd Procédé et appareil pour réaliser une tonalité de retour d'appel caractéristique dans une session à correspondants multiples
EP2249554A1 (fr) * 2008-03-04 2010-11-10 Huawei Technologies Co., Ltd. Procédé et appareil pour réaliser une tonalité de retour d'appel caractéristique dans une session à correspondants multiples
EP2408164A1 (fr) * 2009-04-15 2012-01-18 ZTE Corporation Système d'affichage, procédé et serveur de service de ressource multimédia
EP2408164A4 (fr) * 2009-04-15 2013-01-02 Zte Corp Système d'affichage, procédé et serveur de service de ressource multimédia
EP2487926A3 (fr) * 2009-04-15 2013-07-17 ZTE Corporation Système, procédé et serveur de services pour la lecture de ressources multimédia
EP2503756A3 (fr) * 2009-04-15 2013-07-17 ZTE Corporation Système, procédé et serveur de services pour la lecture de ressources multimédia
CN101835135A (zh) * 2010-03-30 2010-09-15 中兴通讯股份有限公司 一种实现语音呼叫视频化业务的系统和方法
CN102083017A (zh) * 2010-12-31 2011-06-01 东莞宇龙通信科技有限公司 天气信息的发送方法、系统及移动终端
WO2016072736A1 (fr) * 2014-11-04 2016-05-12 Lg Electronics Inc. Procédé et appareil pour gérer un réglage de préférence pour des informations de niveau de confiance d'une identité d'appelant dans un système d'accès sans fil

Also Published As

Publication number Publication date
EP1889428A4 (fr) 2008-06-18
CN101273594A (zh) 2008-09-24
WO2006130783A3 (fr) 2007-10-11
BRPI0611016A2 (pt) 2010-08-17
EP1889428A2 (fr) 2008-02-20

Similar Documents

Publication Publication Date Title
US20070047523A1 (en) Method and system for call-setup triggered push content
EP1889428A2 (fr) Procede et systeme pour contenu pousse lance par l'etablissement d'un appel
US8385514B2 (en) Providing an advertisement to a calling party before ringback
KR101425230B1 (ko) 통신 네트워크 및 통신 네트워크 운영 방법
EP1839457B1 (fr) Procédé pour activer un service réseau-basé dans un réseau de transmission, appareil, dispositif et réseau pour cette fin
US8831578B2 (en) Managing multiple CLI identities
US8406252B1 (en) Presence-based network service availability announcements
US8326273B2 (en) System and method for playing a color ring back tone based on the called user's state presence information
US20110183659A1 (en) Community group client and community auto discovery solutions in a wireless communications network
US20100080361A1 (en) Method for Sharing Audio-only content, Audio-Visual content, and Visual-only content between Subscribers on a Telephone call
WO2006028762A2 (fr) Procedes de transmission d'un message vers un serveur de messages dans un reseau de messagerie vocale instantanee
US20070197224A1 (en) Client server outgoing call management system
US20070046823A1 (en) Color multimedia message
US10176493B2 (en) System and method for compensating telecommunication subscribers for permitting playing of advertisements as ring back tones and direct activation of advertised services
WO2008036008A1 (fr) Options de réponse multiples pour des tentatives de communication entrante
JP6544617B2 (ja) 広告配信システム、方法およびプログラム
EP1927055B1 (fr) Message multimedia en couleur

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680028025.6

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006760629

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: RU

ENP Entry into the national phase

Ref document number: PI0611016

Country of ref document: BR

Kind code of ref document: A2