WO2007004933A1 - Procédé et agencement pour établir une session de communication à commutation de paquets - Google Patents

Procédé et agencement pour établir une session de communication à commutation de paquets Download PDF

Info

Publication number
WO2007004933A1
WO2007004933A1 PCT/SE2005/001084 SE2005001084W WO2007004933A1 WO 2007004933 A1 WO2007004933 A1 WO 2007004933A1 SE 2005001084 W SE2005001084 W SE 2005001084W WO 2007004933 A1 WO2007004933 A1 WO 2007004933A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
file
opposite
message
opposite terminal
Prior art date
Application number
PCT/SE2005/001084
Other languages
English (en)
Inventor
Robert Skog
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to KR1020087002626A priority Critical patent/KR101177601B1/ko
Priority to CNA2005800509307A priority patent/CN101213823A/zh
Priority to EP05755308A priority patent/EP1900183A4/fr
Priority to PCT/SE2005/001084 priority patent/WO2007004933A1/fr
Priority to MX2007015971A priority patent/MX2007015971A/es
Publication of WO2007004933A1 publication Critical patent/WO2007004933A1/fr

Links

Classifications

    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M19/00—Current supply arrangements for telephone systems
    • H04M19/02—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone
    • H04M19/04—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone the ringing-current being generated at the substations
    • H04M19/041—Encoding the ringing signal, i.e. providing distinctive or selective ringing capability
    • 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
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier

Definitions

  • the present invention relates generally to a method and arrangement for providing a selective ring-back or ringing function when setting up a packet-switched communication session.
  • the invention provides a novel solution for using selected media content to generate a "greeting" either in a ring-back or a ringing signal, while waiting for an answer during the call-setup procedure.
  • GPRS General Packet Radio Service
  • WCDMA Wideband Code Division Multiple Access
  • Multimedia services typically involve transmission of encoded data representing text, documents, images, audio files and video files in different formats and combinations.
  • multimedia will be used in this description as generally referring to any choice of media types, apart from ordinary voice dialogues, and typically with some visual content, which is communicated by using the packet based IP (Internet Protocol) transport technology.
  • IP Internet Protocol
  • media content will be used to represent any such encoded data used when exercising multimedia services.
  • IP Multimedia Subsystem A network architecture called "IP Multimedia Subsystem” (IMS) has been developed by the 3 rd Generation Partnership Project (3GPP) as an open standard, to give operators of access networks the ability to offer multimedia services in the packet domain.
  • IMS is a platform for enabling services based on IP transport, more or less independent of the access technology used, and is basically not restricted to any limited set of specific services.
  • SIP Session Initiation Protocol
  • SIP Session Initiation Protocol
  • the SIP standard is thus used by IMS systems and SIP-enabled terminals to establish and control IP multimedia communications.
  • a message called "invite” is defined in SIP to initiate a session during session set-up.
  • the SIP invite message includes, among other things, information on required codec (s) and other communication parameters needed for the forthcoming session.
  • Fig. 1 is a simplified illustration of a basic, network structure for providing multimedia services by means of an IMS service network.
  • a first mobile terminal A is connected to a first radio access network 100 and communicates with a second mobile terminal B connected to a second radio access network 102, in a communication session S involving one or more multimedia services.
  • An IMS network 104 is connected to the first radio access network 100 and handles the session with respect to terminal A.
  • a corresponding IMS network 106 handles the session on behalf of terminal B, and the two IMS networks 104 and 106 may be controlled by different operators.
  • two communicating terminals A and B may of course be connected to the same access network and/or may belong to the same IMS network.
  • the session S is generally managed, using SIP signalling, by specific nodes in each IMS network, here generally referred to as "session managing nodes" 108.
  • These nodes typically include S-CSCF (Serving Call Session Control Function) , I-CSCF (Interrogating Call Session Control
  • Each IMS network 104,106 also includes one or more application servers 110 for enabling various multimedia services. Further, a main database element HSS (Home Subscriber Server) 112 stores subscriber and authentication data as well as service information, among other things. IMS network 106 is basically similar to network 104. The various specific functions of the shown network elements 108-112 are generally known in the art, but they are not necessary to describe here further to understand the context of the present invention. Of course, the IMS networks 104,106 contain numerous other nodes and functions, which are not shown here for the sake of simplicity.
  • a simple ring-back tone is traditionally emitted at terminal A to indicate that a ringing signal has been activated at terminal B.
  • any type of ringing signal can typically be pre-selected by the user of the called terminal, such as a piece of music, vibration or any recorded sound
  • the ring-back tone given at the calling terminal normally consists of a dull repeated tone.
  • ⁇ music ring-back tone a service is available for entertaining a calling party with music while he/she is waiting for an answer from the called party, sometimes referred to as ⁇ music ring-back tone". This service is often used by telephone exchanges at authorities and enterprises where the answer can be greatly delayed, e.g.
  • a ring-back sound or audio piece is transferred ⁇ in-band" to the calling terminal A over a channel reserved for the call being setup.
  • SIP also allows for the ring-back tone as well as the ringing signal to be selected by the opposite party, for multimedia sessions in the IMS context.
  • a header field called "Alert info" has been defined to accommodate an identity of an alternative ringing signal or ring-back tone, respectively.
  • the intention is that the network of terminal A may add a URL (Uniform Resource Locator) or the like in that field of an ⁇ invite' message, to direct terminal B to a corresponding server for fetching a file or the like containing the indicated ringing signal.
  • URL Uniform Resource Locator
  • Fig. 2 is a simplified signalling diagram for a conventional packet-switched call-setup between a calling terminal A connected to a first IMS network 104, and a called terminal B connected to a second IMS network 106, using SIP signalling.
  • the figure illustrates how a personalised greeting feature can be implemented according to the prior art.
  • terminal A sends an ⁇ invite' message towards terminal B to initiate a multimedia session.
  • a suitable session managing node in IMS network 104 now has the opportunity of adding an identity of a ringing file in the above-mentioned alert info field in the ⁇ invite' message, such as a URL, as indicated in a step 202.
  • terminal B may use the ringing file identity URL to fetch the proposed ringing file from a corresponding server and play it as a ringing signal during the call-setup.
  • Terminal B also responds by sending a standard ⁇ 180 ringing' message towards terminal A, in a next step 204, to indicate activation of a ringing signal at terminal B.
  • a suitable session managing node in IMS network 106 can now add an identity of a ring- back file, such as a URL, in the above-mentioned alert info field in the ⁇ 180 ringing' message, as indicated in a step 206.
  • a ring-back file identity URL can be used to fetch the proposed file from a corresponding server and play it as a ring-back tone during the call-setup while waiting for an answer.
  • the terminal user must configure it in advance by defining subscriber preferences or the like in the corresponding IMS network.
  • the network Upon call-setup, the network must then retrieve the ring-back file or ringing file identity as defined, e.g. based on the identity of the opposite party and/or other factors, in order to provide it to the opposite terminal.
  • the network must, for each session-setup, perform a delaying routine of determining whether a specific user-selected greeting (i.e. a ring-back tone or ringing signal) is to be provided at the opposite terminal, and adding a corresponding file identity in a session-setup message, e.g. as described above.
  • a specific user-selected greeting i.e. a ring-back tone or ringing signal
  • the called or calling terminal must fetch or download the indicated file from a server to enable this function each time a session is being set up, involving added consumption of precious bandwidth. This procedure may also take some time, such that the called party may well have answered before the file has been downloaded for play- out, making the whole process pointless
  • Applicant's own Swedish patent application SE 0501419-6 describes a solution for providing a ring-back presentation to a calling terminal after receiving a call setup request for a first communication session.
  • a second packet-based communication session is established with the calling terminal to provide pre-defined media content as said ring-back presentation to the calling terminal over the second session.
  • the inventive method is to be executed in a first communication terminal, for providing a personalised call greeting to an opposite second communication terminal during a setup procedure for a packet-switched multimedia session.
  • at least one file identity is retrieved that has been predefined for the opposite terminal and refers to at least one media file containing said call greeting.
  • the retrieved file identity is sent to the opposite terminal, wherein the opposite terminal can retrieve and playout at least one corresponding file as said call greeting if the file(s) has been stored therein previously.
  • the opposite terminal is a calling terminal, it may be identified by receiving a session initiating message, and when SIP signalling is used, the session initiating message is an SIP ⁇ invite' message. The retrieved file identity may then be sent to the opposite terminal embedded in a response message to the session initiating message. When using SIP signalling, the response message is an SIP ⁇ 180 ringing' message. If the opposite terminal is a called terminal, it is identified when its telephone number is entered. The retrieved file identity may then be sent to the opposite terminal embedded in a session initiating message. When SIP signalling is used, the session initiating message is an SIP ⁇ invite' message.
  • the file identity may be sent as a URN.
  • a network address of a server having the file may be sent together with the file identity as a URL or a URI, wherein the opposite terminal can fetch a corresponding file from said server for playout as said call greeting, if the file has not been stored in the opposite terminal previously.
  • the URN or URL or URI can be embedded in an existing header field called ⁇ Alert info' in an SIP ⁇ invite' message or an SIP ⁇ 180 ringing' message, respectively.
  • the file identity may have been predefined for any unknown opposite terminal and then refers to a media file containing a default call greeting. Also, different file identities may have been defined for different potential opposite terminals, and/or depending on current date or time of day, week or season, and/or depending on a user status.
  • a text string is retrieved associated with the calling terminal and containing said call greeting, and the retrieved text string is sent to the opposite terminal, wherein the opposite terminal can display the text string as said call greeting.
  • the present invention further encompasses a first communication terminal adapted to provide a personalised call greeting to an opposite second communication terminal during a setup procedure for a packet-switched multimedia session.
  • the first communication terminal includes means for identifying the opposite terminal, means for retrieving at least one file identity that has been predefined for the opposite terminal and refers to at least one media file containing said call greeting, and means for sending the retrieved file identity to the opposite terminal, wherein the opposite terminal can retrieve and playout at least one corresponding file as said call greeting if the file(s) has been stored therein previously.
  • the identifying means may be adapted to identify the opposite terminal by receiving a session initiating message.
  • the session initiating message is an SIP ⁇ invite' message.
  • the sending means may be adapted to send the retrieved file identity to the opposite terminal embedded in a response message to the session initiating message.
  • the response message is an SIP ⁇ 180 ringing' message.
  • the identifying means is adapted to identify the opposite terminal when its telephone number is entered.
  • the sending means may be adapted to send the retrieved file identity to the opposite terminal embedded in a session initiating message.
  • the session initiating message is an SIP ⁇ invite' message.
  • the sending means may be adapted to send the file identity as a URN.
  • the sending means may be adapted to send a network address of a server having the file together with the file identity as a URL or a URI, wherein the opposite terminal can fetch a corresponding file from said server for playout as said call greeting, if the file has not been stored in the opposite terminal previously.
  • the terminal is adapted to use SIP signalling
  • the URN or URL or URI is embedded in an existing header field called ⁇ Alert info' in an SIP ⁇ invite' message or an SIP ⁇ 180 ringing' message, respectively.
  • the file identity may have been predefined for any unknown opposite terminal and refers to a media file containing a default call greeting. Further, different file identities have been defined for different potential opposite terminals, and/or depending on the current date or time of the day, week or season, and/or depending on a user status .
  • the present invention further encompasses a first communication terminal having means for identifying the opposite terminal, means for retrieving a text string associated with the calling terminal and containing said call greeting, and means for sending the retrieved text string to the opposite terminal, wherein the opposite terminal can display the text string as said call greeting.
  • Fig. 1 is a schematic view of a conventional network structure for communicating multimedia content .
  • Fig. 2 is a signalling diagram illustrating a packet- switched session-setup procedure involving a personalised greeting feature, according to the prior art.
  • Fig. 3 is a block diagram of two terminals during a session-setup procedure involving a personalised call greeting in the manner of a ring-back tone, according to one embodiment .
  • - Fig. 4 is a block diagram of two terminals during a session-setup procedure involving a personalised call greeting in the manner of a ringing signal, according to another embodiment.
  • Fig. 5 is a flow chart illustrating a basic procedure for providing a personalised call greeting to an opposite terminal during a session-setup procedure, in accordance with the present invention.
  • Fig. 6 is a flow chart illustrating a basic procedure for receiving a personalised call greeting from an opposite terminal during a session-setup procedure, according to another embodiment.
  • Fig. 7 is a flow chart illustrating a basic procedure for receiving a personalised call greeting from an opposite terminal during a session-setup procedure, according to yet another embodiment .
  • call greeting will be used to represent any type of media content presented to a user of an opposite terminal, while waiting for an answer during a session-setup procedure for a packet-switched multimedia session.
  • a call greeting can be presented at a called terminal in the manner of a ringing signal, or at a calling terminal in the manner of a ring-back tone, although the call greeting can be composed of any visual and/or audible media type(s).
  • an image of the calling person may be displayed at the called terminal, at the same time a specific audio sequence, or a default ringing signal, is played out.
  • the present invention is not limited to any specific media types as call greetings.
  • the phrases ⁇ in the manner of a ringing signal" and "in the manner of a ring-back tone" merely refer to the direction of the greeting.
  • the expression "playout" of a file is intended to represent any method of presenting a call greeting on a terminal, e.g. by playing an animation, a video clip or an audio clip, or by displaying an image or an icon, regardless of the file format used. Further, the term “a file” may refer to any number of media files making up the intended call greeting.
  • a calling terminal A and a called terminal B are involved in a setup procedure for a packet-switched multimedia session.
  • the basic idea is that a file identity is sent to the opposite terminal, and that the file in question has presumably already been stored therein, and can therefore be retrieved as a call greeting.
  • a call greeting will be presented to the calling terminal A in the manner of a ring-back tone.
  • a first step 3:1 illustrates that terminal A generally sends a session initiating message to terminal B, such as the above- described SIP message ⁇ invite' , by means of a schematically illustrated communication entity 304.
  • Terminal B receives the session initiating message at a likewise schematically illustrated communication entity 300.
  • Terminal B then identifies the calling terminal A, as typically given in the session initiating message, and checks whether a personalised call greeting is to be presented to the user of terminal A by consulting a database 302 in terminal B. It is assumed that a user of terminal B has pre-stored a number of known potential callers in " database 302 together with identities of selected media files to be played out at the corresponding terminal during session setup. It is also possible to define one or more files to be used as a "default" call greeting for any unknown opposite terminal. Furthermore, different call greeting files may have been defined depending on the current date or time of the day, week or season, and/or depending on a user status.
  • a step 3:2 generally indicates that a file identity associated with the calling terminal is retrieved from the database 302.
  • terminal B duly responds to the session initiating message of step 3:1 by sending a response message, e.g. the above-described SIP message ⁇ 180 ringing', the retrieved file identity is added to this response message, which is then sent to terminal A in a step 3:3.
  • terminal B may insert a URN (Universal Resource Name) in that field, which is a standardised file name type, before sending the message in step 3:3.
  • URN Universal Resource Name
  • a URN is uniquely defined and may be built in the manner of e.g. "urn: song. seme. com: happysong", which can easily be accommodated in the Alert info field.
  • a terminal user may have freely defined any more or less "ordinary" name of a call greeting file that may well be non-unique, assuming that the opposite terminal has a file stored with that particular name, e.g. as received at an earlier occasion.
  • terminal A When terminal A receives the file identity of step 3:3, it may be able to retrieve the indicated file in a following step 3:4 from a database 306 containing various files.
  • a modern terminal has a storage unit or database containing a collection of various files that a terminal user may have downloaded previously, for different reasons, or that may have been stored "by default" in connection with the manufacturing and/or configuration of the terminal.
  • terminal A happens to have the indicated file stored in database 306, and can therefore easily retrieve the file therefrom and provide it to a schematically illustrated "playout" entity 308, in a step 3:5, for playout in the manner of a "ring-back tone".
  • the playout entity 308 of terminal A may comprise any components needed for the playout of media, such as decoders, a display screen, a loudspeaker, etc.
  • terminal B may also provide a network address of a server having the file, together with the file identity in the message of step 3:3.
  • a URL Uniform Resource Locator
  • URI Uniform Resource Identifier
  • terminal A can thus fetch the file from the server, as given by the network address, and play it out, or at least store it in database 306 for playout another time when setting up a new session with terminal B.
  • terminal B may provide the entire greeting as a text string accommodated in the response message of step 3:3, e.g. in the above- mentioned Alert info header field in ⁇ 180 ringing' .
  • terminal A can "play out", in this case display, the text string immediately after step 3:3, whereas steps 3:4 and 3:5 can therefore be omitted.
  • a call greeting as selected by the user of terminal A will be presented to the user of terminal B, in the manner of a ringing signal.
  • the called terminal B can be identified. It is then checked whether a personalised call greeting is to be presented when calling terminal B, by consulting a database 402 in terminal A.
  • a number of potential callers have been pre-stored in database 402 along with identities of selected media files to be played at the corresponding terminal during session setup. Also here, one or more files may also have been defined for presenting a default call greeting in case the opposite terminal is unknown.
  • a first step 4:1 generally indicates that a file identity associated with the called terminal B is retrieved from the database 402.
  • a file identity associated with the called terminal B is retrieved from the database 402.
  • terminal A will generally send a session initiating message to terminal B, such as the above-described SIP message ⁇ invite' , by means of a communication entity 400, which will be received at a corresponding communication entity 404 in terminal B.
  • the file identity retrieved in step 4:1 is first added to the session initiating message, e.g. in the above- described header field "Alert info" in an ⁇ invite' message if SIP signalling is used for the session setup.
  • terminal A may insert a URN in that field before sending the message in step 4:2.
  • the file in question may have been stored in terminal B, and in that case can be retrieved as a call greeting. If not, a URL or a URI or a 'text string may be inserted in the message instead, in a manner similar to the above exemplary alternatives that were given for Fig. 3.
  • terminal B When terminal B receives the file identity of step 4:2, it may be able to retrieve the indicated file in a following step 4:3 from a database 406 containing various files, just like database 306 in Fig. 3. Also in this example, terminal B happens to have the indicated file stored in database 406, and can therefore retrieve the file therefrom and provide it to a playout entity 408, in a step 4:4, for playout in the manner of a "ringing signal".
  • the session-setup procedure itself may continue conventionally from that point, although not shown here.
  • Fig. 5 is a basic flow chart of a procedure, as executed in a first terminal, for providing a personalised call greeting to an opposite second terminal during a setup procedure for a packet-switched session, in accordance with the present invention.
  • the session setup is generally started, by either receiving a session initiating message (e.g. SIP ⁇ invite' ) or when a telephone number is entered.
  • the opposite terminal is identified, by means of either a received session initiating message or an entered telephone number.
  • a call greeting is to be provided at the opposite terminal, e.g. by checking a database such as those 302,402 described in Fig's 3 and 4, respectively. If not, a "regular" procedure takes over in a step 506, meaning that a default ringing signal or ring-back tone may be used. However, if it is determined in step 504 that a call greeting is to be provided, a call greeting file associated with the opposite terminal is selected in a step 508. More precisely, a corresponding file identity is retrieved, e.g. as in the above-described steps 3:2 and 4:1, respectively. The file identity is then sent to the opposite terminal, in a final step 510. It should be noted that the described procedure of Fig. 5 is valid both for a calling terminal providing a call greeting in the manner of a ringing signal, and for a called terminal providing a call greeting in the manner of a ring- back tone.
  • Fig. 6 is a flow chart illustrating a basic procedure, as executed in a first terminal, for receiving a personalised call greeting from an opposite second terminal during a call-setup procedure for a packet-switched session, according to another embodiment.
  • the session setup is generally started, by either receiving a session initiating message (e.g. SIP invite) from the opposite terminal, or by sending a session initiating message (e.g. SIP invite) to the opposite terminal when a telephone number has been entered.
  • a file identity is received from the opposite terminal, e.g. as a URN, which may be either embedded in a received session initiating message (e.g. SIP ⁇ invite' ) , or embedded in a received response message (e.g. SIP ⁇ 180 ringing').
  • a step 604 it is determined whether the indicated file is stored in the terminal, e.g. by checking a database therein such as the ones 306,406 described in Fig's 3 and 4, respectively. If not, a regular procedure may again take over by a activating a default .ringing signal or ring-back tone, in a step 606. However, if it is determined in step 604 that the indicated file is actually stored in the terminal, the file can be retrieved and played out, in a final step 608. It should be noted that the described procedure of Fig. 6 is valid both for a calling terminal receiving a call greeting in the manner of a ring-back tone, and for a called terminal receiving a call greeting in the manner of a ringing signal.
  • a session setup is generally started, as similar to step 600 in the preceding example, by either receiving a session initiating message (e.g. SIP invite) from the opposite terminal, or by sending a session initiating message (e.g.
  • a session initiating message e.g. SIP invite
  • a file identity together with location information on where the file can be fetched is received from the opposite terminal, e.g. as a URL as described above.
  • the received file identity and location information may be either embedded in a received session initiating message (e.g. SIP ⁇ invite' ) , or embedded in a received response message (e.g. SIP ⁇ 180 ringing' ) .
  • a step 704 it is determined whether the indicated file is stored in the terminal, e.g. by checking a database therein such as ⁇ the ones 306,406 described in Fig's 3 and 4, respectively. If so, the file can be retrieved and played out, in a step 706, just like step 608 in the preceding example. However, if it is determined in step 704 that the indicated file is not stored in the terminal, the indicated file can be fetched from a server by using the indicated location information, in a step 708. At the same time, a default ring-back tone or ringing signal may be activated, as indicated by an optional parallel step 710. If the terminal manage to fetch the file in due time, e.g.
  • the file can be played out as a call greeting in a final step 712.
  • the fetched file is preferably also stored in the terminal in step 712 for later playout another time when setting up a new session with terminal B. It should be noted that the described procedure of Fig. 7 is valid both for a calling terminal receiving a call greeting in the manner of a ring- back tone, and for a called terminal receiving a call greeting in the manner of a ringing signal.
  • the feature of selectively providing a call greeting to an opposite calling or called terminal during a packet-switched session-setup is facilitated considerably.
  • the signalling and processing load required for this feature, as well as the time delay before the call greeting can be played out is minimised since only a file identity of relatively small size is communicated.
  • the file containing the selected call greeting is hopefully already available in the terminal where it can be immediately played out.
  • the inventive solution can be seen as suggesting a particular call greeting by means of the indicated file, which may be accepted if it is stored in the opposite terminal. Otherwise, a default signal or tone is generated, without any extra signalling or bandwidth being wasted.
  • more than one file may make up the call greeting such that a plurality of file identities can be sent to the opposite terminal, to indicate playout of plural corresponding files simultaneously or in sequence.
  • a conventional function with a default ringing signal or ring-back tone may be activated at the same time as a personalised call greeting is played out according to the present solution. For example, it may be desirable to emit a conventional ringing signal at the same time a selected image or video clip is displayed at a called terminal. It may also be desirable to emit a conventional ring-back tone at the same time a selected audio clip and/or video clip is played at a calling terminal, etc.
  • a user may also send a particular file to another terminal, or propose downloading thereof from a server, in order to later send the file's corresponding identity during a subsequent session setup to have the file played out as a call greeting according to the present invention.
  • the present solution allows for selective call greetings based on the identity of the opposite terminal, such that certain pre-selected terminals may receive a specific call greeting, whereas others may not. Groups of specific potential callers may also be defined to receive different call greetings, and so forth. It is also possible to select different call greeting files depending on various time factors, such as the current date or time of the day, week or season, etc. Still further, a succession of different call greetings may be presented if the session setup is increasingly delayed. Moreover, it is also possible for the user to define different call greeting files depending on a user status, such as "busy”, and even “busy: meeting", “busy: at cinema”, “busy: sleeping”, etc. While the invention has been described with reference to specific exemplary embodiments, the description is in general only intended to illustrate the inventive concept and should not be taken as limiting the scope of the invention, which is defined by the appended claims.

Abstract

L'invention se rapporte à un procédé et à un agencement destinés à procurer un accueil d'appel personnalisé vers un second terminal de communication opposé (A) pendant une procédure d'établissement destinée à une session multimédia à commutation de paquets. Le terminal opposé est tout d'abord identifié, puis une identité de fichier, associée au terminal appelant et contenant ledit accueil d'appel, est récupérée (3:2). L'identité de fichier est envoyée (3:3) au terminal opposé où le terminal opposé peut restituer un fichier correspondant audit accueil d'appel si le fichier y a été mémorisé au préalable.
PCT/SE2005/001084 2005-07-01 2005-07-01 Procédé et agencement pour établir une session de communication à commutation de paquets WO2007004933A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020087002626A KR101177601B1 (ko) 2005-07-01 2005-07-01 패킷 교환 통신 세션을 설정하는 방법 및 장치
CNA2005800509307A CN101213823A (zh) 2005-07-01 2005-07-01 用于建立分组交换的通信会话的方法和设备
EP05755308A EP1900183A4 (fr) 2005-07-01 2005-07-01 Procédé et agencement pour établir une session de communication à commutation de paquets
PCT/SE2005/001084 WO2007004933A1 (fr) 2005-07-01 2005-07-01 Procédé et agencement pour établir une session de communication à commutation de paquets
MX2007015971A MX2007015971A (es) 2005-07-01 2005-07-01 Un metodo y arreglo para configurar una sesion de comunicacion conmutada en paquetes.

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2005/001084 WO2007004933A1 (fr) 2005-07-01 2005-07-01 Procédé et agencement pour établir une session de communication à commutation de paquets

Publications (1)

Publication Number Publication Date
WO2007004933A1 true WO2007004933A1 (fr) 2007-01-11

Family

ID=37604704

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2005/001084 WO2007004933A1 (fr) 2005-07-01 2005-07-01 Procédé et agencement pour établir une session de communication à commutation de paquets

Country Status (5)

Country Link
EP (1) EP1900183A4 (fr)
KR (1) KR101177601B1 (fr)
CN (1) CN101213823A (fr)
MX (1) MX2007015971A (fr)
WO (1) WO2007004933A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8938055B2 (en) 2010-12-14 2015-01-20 Metaswitch Networks Ltd System and method for establishing data communication using pre-configured user data
US8983043B2 (en) 2010-10-18 2015-03-17 Metaswitch Networks Ltd Data communication
US9008287B2 (en) 2010-10-18 2015-04-14 Metaswitch Networks Ltd Data communication
US9049210B2 (en) 2010-10-18 2015-06-02 Metaswitch Networks Ltd Data communication
US9071950B2 (en) 2010-10-18 2015-06-30 Metaswitch Networks Ltd Systems and methods of call-based data communication

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040081304A1 (en) * 2002-10-07 2004-04-29 Lg Electronics Inc. System and method of generating ring back tone
US20040174966A1 (en) * 2000-12-29 2004-09-09 Koch Robert A. Methods, systems, and products for providing communications services
WO2005018211A1 (fr) * 2003-08-14 2005-02-24 Aksys Networks Inc. Systeme telephonique voip (voix sur protocole internet) sans serveur
EP1592216A1 (fr) * 2004-04-29 2005-11-02 Hewlett-Packard Development Company, L.P. Distribution de contenu pendant l'établissement d'une communication
US20060023862A1 (en) * 2004-07-27 2006-02-02 Geoff Sutcliffe Methods, systems, devices, and products for providing ring backs

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1314301B1 (fr) * 2000-08-22 2007-12-26 Symbian Limited Procede et appareil pour la transmission d'information liee a l'utilisateur au moyen d'un dispositif hertzien
DE10052932A1 (de) * 2000-10-25 2002-05-08 Siemens Ag Auswahl eines Rufsignals
US20020172338A1 (en) * 2001-05-21 2002-11-21 Lee Anne Yin-Fee Multimedia caller identification
EP1271912A1 (fr) * 2001-06-20 2003-01-02 BRITISH TELECOMMUNICATIONS public limited company Tonalités de sonnerie distinctives transmises d'une mémoire appartenant à un réseau

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040174966A1 (en) * 2000-12-29 2004-09-09 Koch Robert A. Methods, systems, and products for providing communications services
US20040081304A1 (en) * 2002-10-07 2004-04-29 Lg Electronics Inc. System and method of generating ring back tone
WO2005018211A1 (fr) * 2003-08-14 2005-02-24 Aksys Networks Inc. Systeme telephonique voip (voix sur protocole internet) sans serveur
EP1592216A1 (fr) * 2004-04-29 2005-11-02 Hewlett-Packard Development Company, L.P. Distribution de contenu pendant l'établissement d'une communication
US20060023862A1 (en) * 2004-07-27 2006-02-02 Geoff Sutcliffe Methods, systems, devices, and products for providing ring backs

Non-Patent Citations (1)

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

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8983043B2 (en) 2010-10-18 2015-03-17 Metaswitch Networks Ltd Data communication
US9008287B2 (en) 2010-10-18 2015-04-14 Metaswitch Networks Ltd Data communication
US9049210B2 (en) 2010-10-18 2015-06-02 Metaswitch Networks Ltd Data communication
US9071950B2 (en) 2010-10-18 2015-06-30 Metaswitch Networks Ltd Systems and methods of call-based data communication
US9723032B2 (en) 2010-10-18 2017-08-01 Metaswitch Networks Ltd Data communication
US10171678B2 (en) 2010-10-18 2019-01-01 Metaswitch Networks Ltd Systems and methods of call-based data communication
US8938055B2 (en) 2010-12-14 2015-01-20 Metaswitch Networks Ltd System and method for establishing data communication using pre-configured user data

Also Published As

Publication number Publication date
EP1900183A4 (fr) 2010-11-03
MX2007015971A (es) 2008-03-06
KR101177601B1 (ko) 2012-08-27
CN101213823A (zh) 2008-07-02
KR20080031926A (ko) 2008-04-11
EP1900183A1 (fr) 2008-03-19

Similar Documents

Publication Publication Date Title
US8687787B2 (en) Method and arrangement for making a call-setup
AU2002244511B2 (en) A system and method for customising call alerts
US8548418B1 (en) Methods and devices for distributing ringtone
CN1801862B (zh) 在ims网络中向用户装置提供多媒体回铃服务的方法和设备
KR100827126B1 (ko) 통신 시스템에서 멀티미디어 포탈 컨텐츠 제공 방법 및시스템
US9137357B2 (en) Method and apparatus for implementing and filtering customized ringing signals
US20100104082A1 (en) Method and apparatus for implementing multimedia customized rbt and multimedia customized rt services
US20060174014A1 (en) System and method for transmitting/receiving alerting information for mobile terminal in a wireless communication system
US9368120B2 (en) Methods and systems for controlling calling party access to called device
CN1964396A (zh) 实现彩铃复制的方法、系统及装置
US20100323676A1 (en) Method, systems, and device for implementing color ring back tone service
WO2005062593A1 (fr) Systeme ou methode de reponse automatique, tel que serveur d'audio-messagerie
CN101222680B (zh) 早期媒体播放实现方法和系统
EP1786188B1 (fr) Système et procédé pour fournir un contenu multimédia pendant l'établissement d'un appel
KR101177601B1 (ko) 패킷 교환 통신 세션을 설정하는 방법 및 장치
WO2010043168A1 (fr) Procédé d'envoi et de réception de fichier de tonalité d'appel multimédia
US20070165814A1 (en) Method and a system for providing ringback information
US20080095078A1 (en) System and method for providing a calling-party-designated ring announcement to a called party terminal
CN102571819A (zh) 一种实现多媒体彩铃业务的方法、系统和装置
WO2010063179A1 (fr) Procédé et terminal pour filtrage de service de sonnerie
CN101202789A (zh) 播放个性化彩色振铃音的方法

Legal Events

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

Ref document number: 200580050930.7

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: MX/a/2007/015971

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 2005755308

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 1020087002626

Country of ref document: KR