Method and communication system for identifying calling/called party
Claim Score by NHIP
Abstract
A method and communication system is provided to identify a calling/called party when the call is being set up but before the call is answered. In the method, a first terminal and a second terminal are respectively provided with opposing terminal's image data before the call is answered. The image data of the first and second terminals can be registered in a media server disposed between the first and second terminals, and the image data can be transmitted between the first terminal and the media server and between the second terminal and the media server in accordance with an SIP protocol.
Term
Term ended
Expired 28 February 2025, 1.6 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
39 claims: 11 independent, 28 dependent
- 1A method of identifying a calling party and call conditions of a called party, comprising the steps of:registering image data of a calling party in at least one a first terminal or a media server;transmitting the image data and a call request of the first terminal to a second terminal via the media server;displaying the image data of the calling party on the second terminal;transmitting image data of the called party previously registered in the media server to the first terminal when at least one of the image data or the call request is transmitted to the media server, wherein the image data of the called party include different images for different call conditions;and displaying the image data of the called party on the first terminal.
- 9A method of identifying another party, comprising the steps of:registering image data of a calling party and different image data corresponding to call conditions of a called party in a media server;transmitting a call request and an image data forwarding request of a first terminal to the media server;transmitting the registered image data of the calling party from the media server to a second terminal in response to the image data forwarding request;and displaying the image data of the calling party on the second terminal.
- 16A communication system for identifying another party, comprising:a first terminal having a communication unit for requesting a call, an SIP system for transmitting image data of a calling party and receiving image data corresponding to a call condition of a called party, a display for displaying the image data of the called party, and an image database for registering the image data of the calling party;a media server having an SIP system for transmitting the image data of the calling party received from the first terminal to the called party and transmitting the image data corresponding to the call condition of the called party to the first terminal, an image database for registering the image data of the called party in accordance with the call condition, and means for selecting one of the image data of the called party corresponding to the call condition;and a second terminal having a communication unit for responding to the call requested from the first terminal to open a communication channel with the first terminal, an SIP system for receiving the image data of the calling party from the first terminal, and a display for displaying the image data of the calling party.
- 19A communication system for identifying another party, comprising:a first terminal having a communication unit for requesting a call, an SIP system for transmitting an image data forwarding request of a calling party and receiving image data corresponding to a call condition of a called party, and a display for displaying the image data of the called party;a media server having an SIP system for transmitting the image data of the calling party to the called party in response to the image data forwarding request and transmitting the image data corresponding to a call condition of the called party to the first terminal, an image database for registering the image data in accordance with the call condition, and means for selecting one of the image data of the called party corresponding to the call condition;and a second terminal having a communication unit for responding to the call requested from the first terminal to open a communication channel with the first terminal, an SIP system for receiving the image data of the calling party from the first terminal, and a display for displaying the image data of the calling party.
- 23A method of identifying call conditions of a called party, comprising the steps of:transmitting a call request of the first terminal to a second terminal via a media server;transmitting image data of the called party to the first terminal, wherein the image data of the called party include different images for different call conditions;and displaying the image data of the called party on the first terminal.
- 24Broadest claimClaim Score 86, broad(NHIP)A method of identifying another party, comprising the steps of:registering different image data corresponding to call conditions of a second terminal;transmitting a call request of a first terminal to the second terminal;transmitting the registered image data corresponding to the call condition of the second terminal;and displaying the image data received from the second terminal on the first terminal.
- 25A communication system for identifying another party, comprising:a first terminal having a communication unit for requesting a call, an SIP system for receiving image data corresponding to a call condition of a called party, and a display for displaying the image data of the called party;a media server having an SIP system for transmitting the image data corresponding to the call condition of the called party to the first terminal, an image database for registering the image data of the called party in accordance with the call condition, and means for selecting one of the image data of the called party corresponding to the call condition;and a second terminal having a communication unit for responding to the call requested from the first terminal to open a communication channel with the first terminal.
- 26A media server for transmitting image data identifying a call condition of a called terminal, the media server comprising:a communication unit;a database;and a controller cooperating with the communication unit and the database to: register image data of the called terminal in the database of the media server, the image data of the called terminal identifying a call condition of the called terminal;and transmit the registered image data of the called terminal to the calling terminal after determining that a call request from the calling terminal to the called terminal is generated, wherein the transmitting process is performed before the call request is accepted by the called terminal, wherein the image data of the called terminal include different images for different call conditions, and the image data of the called terminal include at least one of avatar data, still picture data, moving picture data, text data, or a combination thereof.
- 30A method for transmitting image data identifying a call condition of a called terminal, the method comprising:registering, by a media server, image data of the called terminal in an image database of the media server, the image data of the called terminal identifying a call condition of the called terminal;and transmitting, by the media server, the registered image data of the called terminal to the calling terminal after determining that a call request from the calling terminal to the called terminal is generated, wherein the transmitting process is performed before the call request is accepted by the called terminal, wherein the image data of the called terminal include different images for different call conditions, and the image data of the called terminal include at least one of avatar data, still picture data, moving picture data, text data, or a combination thereof.
- 34A media server for transmitting image data identifying a calling terminal, the media server comprising:a communication unit;a database;and a controller cooperating with the communication unit and the database to: register image data of the calling terminal in the database;and transmit the registered image data of the calling terminal to the called terminal after determining that a call request from the calling terminal to the called terminal is generated, wherein the transmitting process is performed before the call request is accepted by the called terminal, wherein the image data of the calling terminal include at least one of avatar data, still picture data, moving picture data, text data, or a combination thereof.
- 37A method for transmitting image data identifying a calling terminal, the method comprising:registering, by a media server, image data of the calling terminal in an image database of the media server;and transmitting, by the media server, the registered image data of the calling terminal to the called terminal after determining that a call request from the calling terminal to the called terminal is generated, wherein the transmitting process is performed before the call request is accepted by the called terminal, wherein the image data of the calling terminal include at least one of avatar data, still picture data, moving picture data, text data, or a combination thereof.
Independent claims11
98 paragraphs in 4 sections, as filed
0001This application is a Reissue Application of U.S. Pat. No. 7,499,528B2 issued on Mar. 3, 2009 which is incorporated by reference and which claims foreign priority benefits of Korean Patent Application No. 10-2004-0013939 filed Mar. 2, 2004 in Republic of Korea. Notice: More than one reissue application has been filed for the reissue of U.S. Pat. No. 7,499,528B2. The U.S. reissue applications are application Ser. No. 12/859,175 filed Aug. 18, 2010, application Ser. No. 12/859,201 filed Aug. 18, 2010, application Ser. No. 12/859,207 filed Aug. 18, 2010, application Ser. No. 12/859,216 filed Aug. 18, 2010, application Ser. No. 12/859,225 filed Aug. 18, 2010, and application Ser. No. 13/020,319 filed Feb. 3, 2011.
BACKGROUND OF THE INVENTION
00021. Field of the Invention
0003The present invention relates to a communication system, and more particularly, to a method and communication system for identifying a calling/called party (sender/caller or recipient) before calling or answering.
00042. Description of the Related Art
0005Various methods of identifying the calling/called party are being introduced.
0006There is a well-known method of transmitting the caller's phone number to the recipient's terminal during the ringing signal or when the call is being set up but before the call is answered, such that the recipient can see the caller's phone number on the terminal display. However, if the recipient does not know the phone number, the recipient cannot identify the caller.
0007In another method, caller's name, avatar/image as well as the caller's phone number, which are previously stored in the recipient's terminal, are displayed on the terminal display. However, the recipient cannot also identify the caller with this method when the caller's name and avatar/image are not stored in the recipient terminal.
SUMMARY OF THE INVENTION
0008Accordingly, the present invention is directed to a method and communication system for identifying a calling/called party that substantially obviates one or more problems due to limitations and disadvantages of the related art.
0009An object of the present invention is to provide a method and communication system for identifying a calling/called party, in which image data of a calling party can be transmitted to a called party without adding additional software and hardware, thereby decreasing manufacturing and operating costs.
0010Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
0011To achieve these objects and other advantages and in accordance with the purpose of the invention, as embodied and broadly described herein, a method of identifying a calling/called party includes the steps of: registering image data of a calling party in a first terminal; transmitting the image data and a call request of the first terminal to a second terminal via a media server; and displaying the image data of the calling party on the second terminal.
0012In another aspect of the present invention, there is provided a method of identifying a calling/called party, including the steps of: registering image data of calling party and called party in a media server in accordance with a call condition; transmitting a call request and an image data forwarding request of a first terminal to the media server; transmitting the registered image data of the calling party from the media server to a second terminal in response to the image data forwarding request; and displaying the image data of the calling party on the second terminal.
0013In a further another aspect of the present invention, there is provided a communication system for identifying a calling/called party, including: a first terminal having a communication unit for requesting a call, an SIP system for transmitting image data of a calling party and receiving image data of a called party, a display for displaying the image data of the called party, and an image database for registering the image data of the calling party; a media server having an SIP system for transmitting the image data of the calling party received from the first terminal to the called party and transmitting the image data of the called party to the first terminal, an image database for registering the image data of the called party in accordance with a call condition, and means for selecting one of the image data of the called party corresponding to the call condition; and a second terminal having a communication unit for responding to the call requested from the first terminal to open a communication channel with the first terminal, an SIP system for receiving the image data of the calling party from the first terminal, and a display for displaying the image data of the calling party.
0014In a still further another aspect of the present invention, there is provided a communication system for identifying a calling/called party, including: a first terminal having a communication unit for requesting a call, an SIP system for transmitting an image data forwarding request of a calling party and receiving image data of a called party, and a display for displaying the image data of the called party; a media server having an SIP system for transmitting the image data of the calling party to the called party in response to the image data forwarding request and transmitting the image data of the called party to the first terminal, an image database for registering the image data in accordance with a call condition, and means for selecting one of the image data of the called party corresponding to the call condition; and a second terminal having a communication unit for responding to the call requested from the first terminal to open a communication channel with the first terminal, an SIP system for receiving the image data of the calling party from the first terminal, and a display for displaying the image data of the calling party.
0015It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
0016The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. In the drawings:
0017<figref idref="DRAWINGS">FIG. 1</figref> is a block diaphragm of a communication system according to a preferred embodiment the present invention;
0018<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart showing a method of transmitting an avatar data registered in a terminal according to a preferred embodiment of the present invention; and
0019<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart showing a method of transmitting an avatar data registered in a media server according to a preferred embodiment of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
0020Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
0021<figref idref="DRAWINGS">FIG. 1</figref> is a block diaphragm of a communication system according to a preferred embodiment the present invention;
0022Referring to <figref idref="DRAWINGS">FIG. 1</figref>, an communication system includes: a first and second terminals <b>10</b> and <b>30</b> for making a call and answering the call; and a media server <b>20</b> for transmitting image data of the calling party to the called party, transmitting image data of the called party to the calling party, and storing the image data.
0023The image data can be any kind of picture or character, such as an avatar, a still picture, a moving picture, and a text so long as the calling party and called party can be identified with the image data. The avatar is an image of a person used to represent somebody, and it is available from the Internet. The still picture and moving picture can be stored using a camera of a terminal. The text can be used to identify the calling party or the called party instead of the avatar or the pictures. For example, the text may include personal information such as physical and characteristic information.
0024Both the first terminal <b>10</b> and the second terminal <b>30</b> are capable of making and answering a call. Therefore, the first terminal <b>10</b> may be a calling terminal and the second terminal <b>30</b> answering terminal, and vice versa.
0025In the embodiments of the present invention, the first terminal <b>10</b> is illustrated as a calling terminal and the second terminal <b>30</b> is illustrated as an answering terminal.
0026The elements of the first terminal <b>10</b> and the second terminal are similar. That is, the first and second terminals <b>10</b> and <b>30</b> may include communication units <b>11</b> and <b>31</b>, session initiation protocol (SIP) systems <b>12</b> and <b>32</b>, image databases <b>17</b> and <b>37</b>, and displays <b>18</b> and <b>38</b>, respectively.
0027Each of the communication units <b>11</b> and <b>31</b> is capable of requesting a call and accepting a call request. For example, when the calling party requests a call with the communication unit <b>11</b> of the first terminal <b>10</b>, the communication unit <b>31</b> of the second terminal <b>30</b> receives the requested call and generates a ringing signal or activates a vibration mechanism for the called party. If the called party accepts the requested call, the communication unit <b>31</b> sends a call-accepting message to the communication unit <b>11</b> to open a communication channel between the first terminal <b>10</b> and second terminal <b>30</b>. That is, the communication units <b>11</b> and <b>31</b> are provided to request a call, accept the call, and open/close the communication channel.
0028A base station, a mobile switching center, and other stations (not shown in <figref idref="DRAWINGS">FIG. 1</figref>) may be located between the communication unit <b>11</b> and the communication unit <b>31</b> for the communication therebetween. The call requested at the communication unit <b>11</b> may be transmitted to the communication unit <b>31</b> via the base station, the mobile switching center, and other stations. Also, the call-accepting message at the communication unit <b>31</b> may be transmitted to the communication unit <b>11</b> via the base station, the mobile switching center, and other stations.
0029The SIP systems <b>12</b> and <b>32</b> set and release SIP channel connections. Also, the SIP systems <b>12</b> and <b>32</b> send data to the other locations and receive receipt notification messages from the other locations. For this purpose, the SIP systems <b>12</b> and <b>32</b> may include SIP connection setup/release units <b>14</b> and <b>34</b>, and real time transport protocol/real time control protocol (RTP/RTCP) transmitting units <b>16</b> and <b>36</b>, respectively.
0030The SIP connection setup/release units <b>14</b> and <b>34</b> are provided to set SIP channel connections between the first terminal <b>10</b> and the media server <b>20</b> and between the second terminal <b>30</b> and the media server <b>20</b> before opening RTP/RTCP channels therebetween. That is, the RTP/RTCP channels are opened after the SIP channel connections are set. Therefore, the first terminal <b>10</b> can transmit RTP data (e.g., avatar data of the calling party) to the media server <b>20</b>, and the second terminal <b>30</b> can receive the avatar data of the calling party from the media server <b>20</b>. Also, the first terminal <b>10</b> can receive a receipt notification message (e.g., a BYE message) from the media server <b>20</b> after transmitting the avatar data of the calling party to the media server <b>20</b>, and the media server <b>20</b> can receive a receipt notification message from the second terminal <b>30</b> after transmitting the avatar data of the calling party to the second terminal <b>30</b>.
0031After this communication operation, the SIP connection setup/release units <b>14</b> and <b>34</b> release the SIP channel connections.
0032Preferably, the SIP systems <b>12</b> and <b>32</b> operate in association with the communication units <b>11</b> and <b>31</b>. That is, the SIP system <b>12</b> operates when the communication unit <b>11</b> sends the call request to the communication unit <b>31</b>. Also, the SIP system <b>32</b> operates to receive the avatar data of the calling party from the media server <b>20</b> when the communication unit <b>31</b> receives the call request.
0033The SIP system <b>12</b> operates at the same time when the communication unit <b>11</b> sends the call request. Foremost, the SIP connection setup/release unit <b>14</b> of the SIP system <b>12</b> sets the SIP channel connection to connect the first terminal <b>10</b> with the media server <b>20</b>.
0034Then, the RTP/RTCP transmitting unit <b>16</b> transmits the avatar data according to the following ways:
0035In one way, the avatar data registered in the first terminal <b>10</b> are transmitted to the second terminal <b>30</b> through the media server <b>20</b> in accordance with the RTP protocol.
0036In another way, the avatar data of the calling party are previously registered in the media server <b>20</b>, and the media server <b>20</b> transmits the avatar data to the called party in accordance with the RTP protocol when requested to send the avatar data to the called party.
0037The former will now be more fully described and the latter will be described later in association with the media server <b>20</b>.
0038The avatar data may be registered in the image database <b>17</b> of the first terminal <b>10</b>. It will be apparent to those of skill in the art that the avatar data include still picture data, moving picture data, text data, etc., as well as the avatar data. Meanwhile, the image database <b>37</b> of the second terminal <b>30</b> is not necessary in this way because the avatar data of the called party are already registered in the media server <b>20</b>.
0039Further, another avatar data of another called party may be registered in the image database <b>17</b> if the first terminal <b>10</b> have requested a call at least one time to the another called party.
0040The RTP/RTCP transmitting unit <b>16</b> reads the avatar data of the calling party from the image database <b>17</b> and transmits the avatar data to the media server <b>20</b> through the RTP channel. The media server <b>20</b> transmits the received avatar data to the second terminal <b>30</b> for displaying the avatar data on the display <b>38</b> of the second terminal <b>30</b>.
0041Herein, the media server <b>20</b> sends a receipt notification message (e.g., a BYE message) to the first terminal <b>10</b> through the RTCP channel the time when the media server <b>20</b> receives the avatar data of the calling party from the first terminal <b>10</b>. Therefore, the first terminal <b>10</b> can be informed that the avatar data are successfully transmitted to the media server <b>20</b>.
0042When the avatar data of the calling party are displayed on the display <b>38</b> of the second terminal <b>30</b>, the display <b>18</b> of the first terminal <b>10</b> displays the avatar data of the called party received from the media server <b>20</b>.
0043The display of avatar data of the called party on the display <b>18</b> of the first terminal <b>10</b> will be more fully described later when the overall operation of the communication system of the present invention is described.
0044The second terminal <b>30</b> has the similar configuration to the first terminal <b>10</b>. Since the second terminal <b>30</b> is illustrated as an answering terminal, the avatar data of the calling party are displayed on the display <b>38</b> of the second terminal <b>30</b>.
0045In case the second terminal <b>30</b> is a calling terminal, an avatar data registered in the image database <b>37</b> of the second terminal <b>30</b> may be transmitted to the first terminal <b>10</b> to display the avatar data on the display <b>18</b>.
0046The media server <b>20</b> may include an SIP system <b>22</b>, a scheduling unit <b>27</b>, and an image database <b>28</b>.
0047In case the avatar data of the calling party are registered in the first terminal <b>10</b>, the avatar data of the calling party may not be registered in the image database <b>28</b> of the media server <b>20</b>. In this case, the avatar data of the calling party may be transmitted from the first terminal <b>10</b> to the second terminal <b>30</b> via the media server <b>20</b>. The media server <b>20</b> may temporarily store the avatar data of the calling party during transmission of the avatar data of the calling party, and the temporarily stored avatar data may be deleted or not deleted after the transmission.
0048The SIP system <b>22</b> of the media server <b>20</b> is compatible with the SIP systems <b>12</b> and <b>32</b> of the first and second terminals <b>10</b> and <b>30</b>. The SIP system <b>22</b> may include an SIP connection setup/release unit <b>24</b> and an RTP/RTCP transmitting unit <b>26</b> to correspond with the SIP systems <b>12</b> and <b>32</b>.
0049When the SIP connection setup/release unit <b>14</b> sends an SIP channel connection request to the media server <b>20</b>, the media server <b>20</b> accepts the request and sets the SIP channel connection with the first terminal <b>10</b>. Through the SIP channel, the first terminal <b>10</b> can send the avatar data of the calling party (RTP data) to the media server <b>20</b>, and the media server <b>20</b> can send the receipt notification message (e.g., a BYE message) to the first terminal <b>10</b> in response to the received avatar data.
0050The scheduling unit <b>27</b> and the image database <b>28</b> may be provided to register the avatar data of the calling/called party.
0051The calling and called parties can register different avatar data for different call conditions.
0052For example, the called party can register different avatar data in the image database <b>28</b> for different call conditions, such as when ready to receive a call, receiving another call, has the terminal <b>30</b> powered off, and incapable of receiving a call (e.g., when in a theater, a meeting, or a bathroom).
0053The scheduling unit <b>27</b> checks the call condition of the called party and selects one of the avatar data corresponding to the checked call condition. Also, other data such as identifiers, phone numbers, as well as the avatar data can be registered in the image database <b>28</b> for both the calling and called parties.
0054In this manner, the avatar data are registered and set according to the call condition. Therefore, when the first terminal <b>10</b> sends a call request and an avatar data forwarding request, the media server <b>20</b> searches the avatar data of the image database <b>28</b> according to the identifier or phone number of the calling party to find an avatar corresponding to the calling party and sends the avatar to the second terminal <b>30</b>, such that the avatar of the calling party can be displayed on the display <b>38</b> of the second terminal <b>30</b>.
0055Further, the media server <b>20</b> checks the call condition of the second terminal <b>30</b>, selects an avatar corresponding to the call condition form the image database <b>28</b>, and sends the avatar to the first terminal <b>10</b> for displaying on the display <b>18</b>.
0056Hereinafter, a method of identifying a calling/called party will now be described. There are two ways of transmitting the avatar data: one way is to transmit the avatar data that are registered in the terminal <b>10</b> or terminal <b>30</b>, and another way is to transmit the avatar data that are previously registered in the media server <b>20</b>.
0057<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart showing a method of transmitting an avatar data registered in a terminal according to a preferred embodiment of the present invention; and
0058Referring to <figref idref="DRAWINGS">FIGS. 1 and 2</figref>, avatar data of the calling party are registered in the image database <b>17</b> of the first terminal <b>10</b> in operation S<b>41</b>. Herein, the avatar data of the calling party are not registered in the media server <b>20</b>. The avatar data may include still picture data, moving picture data, text data, as well as avatar data. The avatar data are image data representing a person and it is available from the Internet. Also, the still picture and moving picture data may be picture data of the calling party taken with a camera such as a built-in camera of the terminal <b>10</b>. Information about the calling party may be contained in the text data to represent the calling party. The calling party can register one of the avatar data, the still picture data, the moving picture data, the text data, and a combination thereof.
0059In operation S<b>42</b>, the first terminal <b>10</b> of the calling party transmits a call request to the second terminal <b>30</b> of the called party. The way of the call request is well known in the art.
0060In operation S<b>43</b>, the SIP channel connection is set between the first terminal <b>10</b> and the media server <b>20</b>. After the SIP channel is set, data and control signals can be transmitted between the first terminal <b>10</b> and the media server <b>20</b>.
0061In operation S<b>44</b>, the first terminal <b>10</b> transmits the avatar data of the calling party from the image database <b>17</b> to the media server <b>20</b> through the RTP channel in the form of packet.
0062In operation S<b>45</b>, the media server <b>20</b> sends a receipt notification message (e.g., a BYE message) to the first terminal <b>10</b> through the RTCP channel when the media server <b>20</b> receives the avatar data of the calling party.
0063In operation S<b>46</b>, the media server <b>20</b> transmits the received avatar data of the calling party to the second terminal <b>30</b> through the RTP channel between the media server <b>20</b> and the second terminal <b>30</b>. After the avatar data of the calling party are transmitted to the second terminal <b>30</b>, the avatar data may be deleted from the media server <b>20</b>. The RTP and RTCP channels are opened between the media server <b>20</b> and the second terminal <b>30</b> before the avatar data of the calling party are transmitted to the second terminal <b>30</b>. The called party can open the RTP and RTCP channels by manipulating the second terminal <b>30</b>, for example, pressing an “ON” button.
0064In operation S<b>47</b>, the second terminal <b>30</b> displays the received avatar data of the calling party. Therefore, the called party of the second terminal <b>30</b> can exactly identify the calling party through the displaying avatar data. The second terminal <b>30</b> may register the received avatar data of the calling party in the image database <b>37</b> to display the registered avatar data instead of repeatedly receiving the avatar data from the first terminal <b>10</b> when the first terminal <b>10</b> requests a call again.
0065In operation S<b>48</b>, the media server <b>20</b> asks the second terminal <b>30</b> for a call condition through the RTCP channel, and correspondingly the second terminal <b>30</b> sends its call condition to the media server <b>20</b> through the RTCP channel, such that the media server <b>20</b> can check the call condition of the second terminal <b>30</b>.
0066When the calling party makes a call to the called party, the called party may be in various situations such as when ready to receive a call, receiving another call, being on duty, and incapable of receiving a call. Also, the second terminal <b>30</b> of the called party may be power-off or incapable of receiving a call. The term “call condition(s)” is used to denote such situations and conditions. That is, when the media server <b>20</b> asks the second terminal <b>30</b> for the call condition, the second terminal <b>30</b> may inform the media server <b>20</b> of its call condition among such situations and conditions. The call condition checking operation is well known to those of skill in the art.
0067In operation S<b>49</b>, the media server <b>20</b> selects an avatar of avatar data of the called party corresponding to the checked call condition from the image database <b>28</b>. For this operation, the called party can register avatar data having different avatars, pictures and texts in image database <b>28</b> of the media server <b>20</b> for different call conditions. Also, since the calling party of the first terminal <b>10</b> can be a called party, the calling party of the first terminal <b>10</b> can register his/her avatar data in the image database <b>28</b> for different call conditions.
0068In operation S<b>50</b>, the media server <b>20</b> transmits the selected avatar of the called party to the first terminal <b>10</b> through the RTP channel.
0069In operation S<b>51</b>, the first terminal <b>10</b> displays the received avatar of the called party. The first terminal <b>10</b> may register the received avatar of the called party in its image database <b>17</b> for later usage, for the same purpose as is described in operation S<b>47</b>.
0070In operation S<b>52</b>, the SIP channel connection between the <b>10</b> and the media server <b>20</b> is released.
0071Therefore, each of the calling party and the called party can see the avatar of the opposing party when making and answering a call, thereby exactly identifying the opposing party.
0072If the second terminal <b>30</b> accepts the call request of the first terminal <b>10</b> in operation S<b>53</b>, communication channel between the first and second terminals <b>10</b> and <b>30</b> is open for the communication therebetween in operation S<b>54</b>.
0073After the communication between the terminals <b>10</b> and <b>30</b>, the communication channel is closed as is well known in the art.
0074<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart showing a method of transmitting an avatar data previously registered in a media server according to a preferred embodiment of the present invention.
0075Referring to <figref idref="DRAWINGS">FIGS. 1 and 3</figref>, avatar data for different call conditions are registered in the media server <b>20</b> in operation S<b>61</b>. Both the called party and the calling party can register their avatar data for their different call conditions, and the avatar data may be registered together with identifiers and phone numbers.
0076The terminals <b>10</b> and <b>30</b> do not store opposing party's avatar data. But the terminals <b>10</b> and <b>30</b> may store the opposing party's avatar data after a call (described later).
0077The avatar data may include still picture data, moving picture data, text data, etc., as well as avatar data.
0078The avatar data may be registered in the media server with the first terminal <b>10</b>, the second terminal <b>30</b>, a personal computer (PC), or other devices.
0079In operation S<b>62</b>, the calling party of the first terminal <b>10</b> requests a call to the media server <b>20</b>. The operation of the call request is well known in the art.
0080In operation S<b>63</b>, the SIP channel connection is set between the first terminal <b>10</b> and the media server <b>20</b> in response to the call request. After the SIP channel is set, data and control signals can be transmitted between the first terminal <b>10</b> and the media server <b>20</b>.
0081In operation S<b>64</b>, the first terminal <b>10</b> transmits an avatar data forwarding request to the media server <b>20</b> through the RTP channel. Since the avatar data of the calling party are already registered in the media server <b>20</b>, the first terminal <b>10</b> can request the media server <b>20</b> to send the avatar data of the calling party to the second terminal <b>30</b> by transmitting the avatar data forwarding request.
0082In operation S<b>65</b>, the media server <b>20</b> sends a receipt notification message (e.g., a BYE message) to the first terminal <b>10</b> through the RTCP channel when the media server <b>20</b> receives the avatar data forwarding request. That is, the media server <b>20</b> sends the receipt notification message to inform the first terminal <b>10</b> that the avatar data forwarding request is successfully received. Therefore, the first terminal <b>10</b> can check that its avatar data forwarding request is successfully transmitted to the media server <b>20</b>.
0083In operation S<b>66</b>, the media server <b>20</b> transmits the avatar data of the calling party from the image database <b>28</b> to the second terminal <b>30</b> through the RTP channel in response to the avatar data forwarding request. The second terminal <b>30</b> may request to open the RTP and RTCP channels between the media server <b>20</b> and the second terminal <b>30</b> before the avatar data of the calling party are transmitted to the second terminal <b>30</b>. That is, the called party can open the RTP and RTCP channels by manipulating the second terminal <b>30</b>, for example, pressing an “ON” button.
0084In operation S<b>67</b>, the second terminal <b>30</b> displays the received avatar data of the calling party. Therefore, the called party of the second terminal <b>30</b> can exactly identify the calling party through the displaying avatar data. The second terminal <b>30</b> may register the received avatar data of the calling party in the image database <b>37</b> to display them instead of repeatedly receiving the avatar data from the media server <b>20</b> when the first terminal <b>10</b> requests a call again.
0085In operation S<b>68</b>, the media server <b>20</b> asks the second terminal <b>30</b> for a call condition through the RTCP channel, and correspondingly the second terminal <b>30</b> sends its call condition to the media server <b>20</b> through the RTCP channel, such that the media server <b>20</b> can check the call condition of the second terminal <b>30</b>.
0086The term “call condition” denotes the same meaning as described above.
0087In operation S<b>69</b>, the media server <b>20</b> selects an avatar of the avatar data of the called party corresponding to the checked call condition from the image database <b>28</b>. Since the avatar data having different avatars, pictures and texts that are previously registered in image database <b>28</b> of the media server <b>20</b> for different call conditions, the media server <b>20</b> can easily select the avatar corresponding to the call condition.
0088In operation S<b>70</b>, the media server <b>20</b> transmits the selected avatar of the called party to the first terminal <b>10</b> through the RTP channel.
0089In operation S<b>71</b>, the first terminal <b>10</b> displays the received avatar of the called party. The first terminal <b>10</b> may register the received avatar of the called party in its image database <b>17</b> for later usage, for the same purpose as is described in operation S<b>67</b>.
0090In operation S<b>72</b>, the SIP channel connection between the <b>10</b> and the media server <b>20</b> is released.
0091Therefore, each of the calling party and the called party can see the avatar of the opposing party when making and answering a call, thereby exactly identifying the opposing party.
0092If the second terminal <b>30</b> accepts the call request of the first terminal <b>10</b> in operation S<b>73</b>, communication channel between the first and second terminals <b>10</b> and <b>30</b> is open for the communication therebetween in operation S<b>74</b>.
0093After the communication between the terminals <b>10</b> and <b>30</b>, the communication channel is closed as is well known in the art.
0094As described above, the calling party and called party easily identify the opposing party using the SIP protocol, such that the called party can selectively answer the call depending on the calling party, and the calling party can be informed promptly when dialing a wrong number.
0095Further, in case the calling party does not register the avatar data in the media server, the calling party can utilize the avatar data of his/her terminal to transmit the avatar to the called party when making a call.
0096Furthermore, when the called party receives a call at least one time from the calling party, the called party can register the avatar data of the calling party in the terminal for later usage, such that the terminal of the called party can display the registered avatar data instead of repeatedly receiving the avatar data when the same calling party called. In the same way, when the calling party requests a call to the called party, the calling party can register the avatar data received from the called party for later usage instead of repeatedly receiving the avatar data of the called party.
0097The method and communication system of the present invention provides an easy way of identifying the calling/called party by utilizing the well known SIP protocol without adding additional software and hardware.
0098It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
Contents4
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| USRE44951E | Cited by | United States of America | Search report |
| WO0217602A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| EP0741484A2 | Cites | European Patent Office (EPO) | Applicant |
| CN1413409A | Cites | China | Applicant |
| US2003032413A1 | Cites | United States of America | Applicant |
| US2003055981A1 | Cites | United States of America | Applicant |
| US2003095650A1 | Cites | United States of America | Applicant |
| US2003139172A1 | Cites | United States of America | Applicant |
| US2004032503A1 | Cites | United States of America | Applicant |
| US2004055011A1 | Cites | United States of America | Applicant |
| US2004091090A1 | Cites | United States of America | Applicant |
| US2004101046A1 | Cites | United States of America | Applicant |
| US2004165703A1 | Cites | United States of America | Applicant |
| US2004209644A1 | Cites | United States of America | Applicant |
| US2005032507A1 | Cites | United States of America | Applicant |
| US2005143053A1 | Cites | United States of America | Applicant |
| US2005146599A1 | Cites | United States of America | Applicant |
| US2005169446A1 | Cites | United States of America | Applicant |
| US2005195950A1 | Cites | United States of America | Search report |
| US2006020991A1 | Cites | United States of America | Applicant |
| US2006159247A1 | Cites | United States of America | Applicant |
| US2006258396A1 | Cites | United States of America | Applicant |
| US2006268349A1 | Cites | United States of America | Applicant |
| US2007091832A1 | Cites | United States of America | Applicant |
| US2008045184A1 | Cites | United States of America | Applicant |
| US2011273540A1 | Cites | United States of America | Applicant |
| US4715059A | Cites | United States of America | Search report |
| US4943994A | Cites | United States of America | Applicant |
| US4995073A | Cites | United States of America | Applicant |
| US5042061A | Cites | United States of America | Search report |
| US5146349A | Cites | United States of America | Search report |
| US5586171A | Cites | United States of America | Applicant |
| US5606365A | Cites | United States of America | Search report |
| US5608788A | Cites | United States of America | Search report |
| US5715301A | Cites | United States of America | Applicant |
| US5771065A | Cites | United States of America | Applicant |
| US5818606A | Cites | United States of America | Applicant |
| US5875239A | Cites | United States of America | Applicant |
| US5890071A | Cites | United States of America | Applicant |
| US5898824A | Cites | United States of America | Search report |
| US5907604A | Cites | United States of America | Applicant |
| US5930818A | Cites | United States of America | Applicant |
| US5999599A | Cites | United States of America | Applicant |
| US6167469A | Cites | United States of America | Search report |
| US6185433B1 | Cites | United States of America | Applicant |
| US6192257B1 | Cites | United States of America | Applicant |
| US6198738B1 | Cites | United States of America | Applicant |
| US6226367B1 | Cites | United States of America | Applicant |
| US6243448B1 | Cites | United States of America | Applicant |
| US6269094B1 | Cites | United States of America | Applicant |
| US6272126B1 | Cites | United States of America | Applicant |
| US6509924B2 | Cites | United States of America | Applicant |
| US6529742B1 | Cites | United States of America | Applicant |
| US6600508B2 | Cites | United States of America | Search report |
| US6870917B2 | Cites | United States of America | Applicant |
| US6876734B1 | Cites | United States of America | Applicant |
| US6981275B1 | Cites | United States of America | Applicant |
| US7031746B2 | Cites | United States of America | Applicant |
| US7065197B1 | Cites | United States of America | Applicant |
| US7085253B2 | Cites | United States of America | Applicant |
| US7088802B2 | Cites | United States of America | Applicant |
| US7092735B2 | Cites | United States of America | Applicant |
| US7130296B2 | Cites | United States of America | Applicant |
| US7155211B2 | Cites | United States of America | Applicant |
| US7174163B2 | Cites | United States of America | Applicant |
| US7177627B2 | Cites | United States of America | Applicant |
| US7180991B2 | Cites | United States of America | Applicant |
| US7239338B2 | Cites | United States of America | Applicant |
| US7248677B2 | Cites | United States of America | Applicant |
| US7272134B2 | Cites | United States of America | Applicant |
| US7301661B2 | Cites | United States of America | Applicant |
| US7313227B2 | Cites | United States of America | Applicant |
| US7423770B2 | Cites | United States of America | Applicant |
| US7443416B2 | Cites | United States of America | Search report |
| US7493138B2 | Cites | United States of America | Applicant |
| US7499528B2 | Cites | United States of America | Search report |
| US7536178B2 | Cites | United States of America | Applicant |
| US7623186B2 | Cites | United States of America | Applicant |
| US7634731B2 | Cites | United States of America | Applicant |
| US7643168B2 | Cites | United States of America | Search report |
| US7643619B2 | Cites | United States of America | Applicant |
| US7660404B2 | Cites | United States of America | Applicant |
| US7738886B1 | Cites | United States of America | Applicant |
| USH1714H | Cites | United States of America | Applicant |
21 members in 5 offices
Priority claims11
| Document | Office | Kind | Date |
|---|---|---|---|
| 1020040013939 | Republic of Korea | – | |
| 20040013939 | Republic of Korea | A | |
| 20040013939 | Republic of Korea | A | |
| 6938405 | United States of America | A | |
| 6938405 | United States of America | A | |
| 85920710 | United States of America | A | |
| 1020040013939 | – | – | – |
| 11069384 | – | – | – |
| KR20040013939 | – | – | – |
| US20050069384 | – | – | – |
| US20100859207 | – | – | – |
Members21
| Document | Office | Kind | |
|---|---|---|---|
| CN1665254A | China | A | |
| EP1571813A1 | European Patent Office (EPO) | A1 | |
| KR20050088928A | Republic of Korea | A | |
| US2005195950A1 | United States of America | A1 | |
| US2006067287A1 | United States of America | A1 | |
| KR100690870B1 | Republic of Korea | B1 | |
| WO2007066170A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007066170A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CN101164360A | China | A | |
| US7499528B2 | United States of America | B2 | |
| CN100536505C | China | C | |
| US7817649B2 | United States of America | B2 | |
| USRE43559EThis record | United States of America | E | |
| USRE43648E | United States of America | E | |
| USRE43852E | United States of America | E | |
| USRE43893E | United States of America | E | |
| USRE44066E | United States of America | E | |
| USRE44067E | United States of America | E | |
| USRE44951E | United States of America | E | |
| CN104219223A | China | A | |
| CN104219223B | China | B |
97 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Email NotificationEML_NTR | EML_NTR | |
| Mailing Corrected Notice of AllowabilityMCNOA | MCNOA | |
| Reasons for AllowanceEX.R | EX.R | |
| Corrected Notice of AllowabilityCNOA | CNOA | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Workflow - Request for RCE - FinishFRCE | FRCE | |
| Workflow - Request for RCE - FinishFRCE | FRCE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Quick Path IDS RequestQPREQ | QPREQ | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail-Record Petition Decision of Granted to Withdraw from Issue - with assigned Patent NO.MP015 | MP015 | |
| Record Petition Decision of Granted to Withdraw from Issue - with assigned Patent NO.P015 | P015 | |
| Withdrawal Patent Case from IssueWFIS | WFIS | |
| Petition EnteredPET. | PET. | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Notice of Reissue Published in Official GazetteNRE. | NRE. | |
| Application Is Now CompleteCOMP | COMP | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail-Petition Decision - GrantedMPTGR | MPTGR | |
| Petition Decision - GrantedPTGR | PTGR | |
| Petition EnteredPET. | PET. | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail-Petition Decision - DismissedMPTDI | MPTDI | |
| Petition Decision - DismissedPTDI | PTDI | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Petition EnteredPET. | PET. | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Email NotificationEML_NTR | EML_NTR | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Cleared by OIPE CSRL194 | L194 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Preliminary AmendmentA.PE | A.PE | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
3 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP |
Numbers
- Publication
- RE043559
- Publication, DOCDB
- RE43559
- Publication, EPODOC
- USRE43559E
- Application
- 12859207
- Application, DOCDB
- 85920710
- Application, EPODOC
- US20100859207
Titles
- English
- Method and communication system for identifying calling/called party
Classification
- CPC, 6
- H04M3/42042
- H04M1/576
- H04M3/42059
- H04M3/42093
- H04M7/006
- H04M2242/22
- IPC, 4
- H04M1 64
- H04M1 57
- H04M3 42
- H04N7 14
- USPC, 13
- 379088190
- 348014090
- 348014120
- 348014140
- 348222100
- 358001150
- 358001160
- 358407000
- 379088130
- 379142070
- 379142170
- 455415000
- 710062000