Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/10—Architectures or entities
  • H04L65/1016—IP multimedia subsystem [IMS]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/10—Architectures or entities
  • H04L65/102—Gateways
  • H04L65/1023—Media gateways
  • H04L65/103—Media gateways in the network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/1066—Session management
  • H04L65/1083—In-session procedures
  • H04L65/1093—In-session procedures by adding participants; by removing participants
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/1066—Session management
  • H04L65/1083—In-session procedures
  • H04L65/1094—Inter-user-equipment sessions transfer or sharing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/1066—Session management
  • H04L65/1101—Session protocols
  • H04L65/1104—Session initiation protocol [SIP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/40—Support for services or applications
  • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
  • H04L65/4046—Arrangements for multi-party communication, e.g. for conferences with distributed floor control

Definitions

• a conventional Internet Protocol Multimedia Subsystem (IMS) network is an architectural framework for delivering Internet Protocol (IP) services.
• the conventional IMS network may implement a signaling protocol to establish, modify, and/ or terminate various forms of communication.
• One type of signaling protocol may be Session
• SIP Initiation Protocol
• a set of user equipments may use SIP and have a shared phone number.
• the set of conventional UEs may also undertake a registration procedure.
• the registration procedure may allow each UE to be assigned a unique contact address.
• Network elements in the conventional IMS/ SIP network may use the unique contact address to send an INVITE request to each conventional UE when there is an incoming call to the shared phone number, such that the set of conventional UEs ring simultaneously. This allows a subscriber to answer the incoming call at any of the conventional UEs.
• Example embodiments provide a method and / or network element capable of joining SIP communication devices into an existing call.
• a network element may join SIP communication devices by receiving an incoming call from a calling communication device and establishing a connection between the calling communication device and at least one associated
• the set of associated communication devices may be notified of the connection and a conference procedure may be performed in response to an unconnected communication device being activated, such that a multi-way conference connection is established between the calling communication device, the at least one associated communication device, and the at least one unconnected communication device.
• a notification apparatus may include an application server.
• the application server may be configured to: receive an incoming call from a calling communication device; establish a connection between the calling communication 805254 3
• FIG. 1 illustrates an IMS network according to an example
• FIG. 2 illustrates a method of joining SIP communication devices into an existing call according to an example embodiment.
• FIG. 3 is a signal flow diagram further defining step SI 00 of FIG. 2 according to an example embodiment.
• FIG. 4 is a signal flow diagram further defining step S200 of FIG. 2 according to an example embodiment. 805254 4
• FIG. 5 is a signal flow diagram further defining step S300 of FIG. 2 according to an example embodiment.
• FIG. 6 is a signal flow diagram further defining step S400 of FIG. 2 according to an example embodiment.
• FIGS. 7A-7B are signal flow diagrams further defining step S500 of FIG. 2 according to an example embodiment.
• FIGS. 8A-8B are signal flow diagrams further defining step S600 of FIG. 2 according to an example embodiment.
• FIG. 9 is a signal flow diagram further defining step S700 of FIG. 2 according to an example embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS
• first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
• second element could be termed a first element, without departing from the scope of example embodiments.
• the term "and/ or" includes any and all combinations of one or more of the associated listed items.
• UE user equipment
• FIG. 1 illustrates an IMS network 100 according to an example embodiment.
• FIG. 1 includes three UEs (101 , 103, and 105).
• a first user equipment (UE- 1 101) may be a calling communication device, whereas a second (UE-2 103) and third (UE-3 105) user equipment may be associated with each other by a shared identifier.
• the shared identifier may be, but is not limited to, a shared phone number and/ or a shared Uniform Resource Identifier (URI) field.
• the associated UEs (UE-2 103 and UE-3 105) may each individually register with the IMS network 100.
• the UEs use SIP to communicate with a Call Session Control Function (CSCF) 109.
• the CSCF 109 may be a collection of SIP servers and/ or proxies used to process SIP signaling packets in the IMS network 100.
• the CSCF may include a Proxy-CSCF (P-CSCF), a Serving-CSCF (S- CSCF), and an Interrogating-CSCF (I-CSCF).
• P-CSCF may be a first point of contact. Messages sent and/ or received by a UE in the IMS network 100 travel through the P-CSCF.
• the S-CSCF may be a central node in the SIP signaling plane.
• the I-CSCF may be a querying function.
• Incoming calls travel through the I-CSCF.
• SIP INVITE requests travel through the I-CSCF.
• the S-CSCF 109 includes an S-CSCF 1 1 1.
• the UEs' communication with the S-CSCF 1 1 1 is discussed further below. 805254 7
• the various network elements 107 may include, but are not limited to: (i) access networks (e.g., Digital Subscriber Line Access Multiplexer, etc.), (ii) gateways (e.g., Border Gateway, IMS Gateway, Signaling Gateway, Media Gateway, etc.), and (iii) any other intermediary IMS elements (Network Attachment Subsystem, Building Automation System, Access-Resource and Admission Function, Policy Decision Function, Service-Based Policy Decision Function, etc.)
• access networks e.g., Digital Subscriber Line Access Multiplexer, etc.
• gateways e.g., Border Gateway, IMS Gateway, Signaling Gateway, Media Gateway, etc.
• any other intermediary IMS elements Network Attachment Subsystem, Building Automation System, Access-Resource and Admission Function, Policy Decision Function, Service-Based Policy Decision Function, etc.
• the S-CSCF 1 1 1 utilizes the SIP to communicate with an Application Server (AS) 1 15 and a Media Resource Function (MRF) 1 13.
• the AS 1 15 may be an SIP entity that executes various services provided to the UEs.
• the AS 1 15 may also be aware that the associated UEs (UE- 2 103 and UE-3 105) have a shared identifier.
• the AS 1 15 may become aware of this fact if, or when, the associated UEs register with the IMS network 100.
• the MRF 1 13 may provide media related functions (e.g., a multi-way conference connection, media manipulation, announcements, etc.).
• the MRF 1 13 may include a Media Resource Function Controller (MRFC) and a Media Resource Function Processor (MRFP).
• the MRFC may act as an SIP user agent to the S-CSCF 1 1 1.
• the MRFP may implement the actual media related functions.
• FIG. 2 illustrates a method of joining SIP communication devices into an existing call according to an example embodiment.
• the method described in FIG. 2 can be implemented in the network architecture illustrated in FIG. 1 , but is 805254 8
• step SI 00 an incoming call from a calling UE is received.
• the call may be received by the AS.
• associated UEs are alerted that the incoming call has arrived, per step S200.
• step S300 a connection between the calling UE and at least one of the associated UEs is established. Step S300 may also include
• step S600 a conference procedure is performed in response to an unconnected UE being activated.
• the conference procedure may automatically add the calling UE, the associated at least one connected UE, and the initially unconnected UE into a multi- way conference call.
• the call may be terminated per step S600.
• FIG. 3 is a signal flow diagram further defining step SI 00 of FIG. 2 according to an example embodiment.
• the method described in FIG. 3 can be implemented in the network architecture illustrated in FIG. 1 , but is not limited to this
• a calling UE sends an INVITE request to the S-CSCF in step SlO l .
• the INVITE request may be the incoming call.
• the destination address of the INVITE request may be the shared
• step SI 03 the S-CSCF forwards the INVITE request 805254 9
• step SI 05 the AS may forward an INVITE request to the S-CSCF that is intended to be received by the associated UE-2.
• the INVITE request may include a unique public identity
• the S-CSCF may be aware that the
• step SI 09 the AS forwards an INVITE request, which includes a unique public identity corresponding to the associated UE-3 request, to the S-CSCF.
• the S- CSCF forwards the INVITE request to the associated UE-3, per step Si l l . It should be noted that steps SI 05, SI 07, SI 09, and Si l l may be performed simultaneously. Also, the AS may then track
• FIG. 4 is a signal flow diagram further defining step S200 of FIG. 2 according to an example embodiment.
• the method described in FIG. 4 can be implemented in the network architecture illustrated in FIG. 1 , but is not limited to this
• the associated UEs may send ringing alerts to the AS. More specifically, the associated UE-2 sends a ringing alert to the S-CSCF in step S201. The S-CSCF forwards this ringing alert to the AS. Once received by the AS, the AS forwards the associated UE-2's 805254 10
• FIG. 5 is a signal flow diagram further defining step S300 of FIG. 2 according to an example embodiment.
• the method described in FIG. 5 can be implemented in the network architecture illustrated in FIG. 1 , but is not limited to this
• a subscriber will activate at least one of the associated UEs (e.g., answer the call).
• the associated UE-2 answers the call and sends an answer confirmation to the S-CSCF.
• the answer confirmation is an "OK" message.
• the OK message may include an answer in a format for describing streaming media initialization parameters (e.g., a Session Description Protocol answer).
• the S-CSCF forwards the OK message to the AS in step S303.
• the AS forwards an OK message with a UE-2 identifier to the S-CSCF.
• the UE-2 identifier may include the SDP answer from the UE-2.
• step S307 the S-CSCF forwards an OK message, along with the UE-2 identifier, to the UE- 1.
• the UE- 1 is the calling UE. Accordingly, a connection between the UE- 1 and the UE-2 is established thereafter, per step S309. 805254 1 1
• a call session with the associated UE-3 may be terminated. More specifically, the AS may cancel the outstanding INVITE with the unconnected associated UE-3.
• the AS sends a cancellation message to the S-CSCF.
• the cancellation message may be a SIP CANCEL message.
• the cancellation message is forwarded by the S-CSCF to the UE-3 in step S313.
• the unconnected associated UE-3 sends a cancellation acknowledgment (ACK) back to the S-CSCF, per step S315.
• the cancellation acknowledgement may be an SIP OK CANCEL message.
• the S-CSCF forwards the cancellation to the AS in step S317.
• FIG. 6 is a signal flow diagram further defining step S400 of FIG. 2 according to an example embodiment.
• the method described in FIG. 6 can be implemented in the network architecture illustrated in FIG. 1 , but is not limited to this
• the AS may notify all the associated UEs of the connection between the calling UE- 1 and the associated UE-2.
• FIG. 6 illustrates this notifying procedure. More specifically, in step S401 the AS sends a call notification message to the S-CSCF.
• the call notification message may be a SIP NOTIFY 805254 12
• the call notification message may also be used by the unconnected UE-3 to inform a subscriber that the line is busy and/ or active.
• a call notification message may be used to activate a light source and / or some other computerized form of subscriber notification, similar to conventional PSTN phones (e.g., an "in use,” or "call in progress,” light).
• step S403 the S-CSCF forwards the call notification message to the unconnected associated UE-3.
• the AS may also forward the call notification message to the connected associated UE-2 (not shown).
• step S405 the unconnected UE-3 sends a confirmation OK NOTIFY message to the S-CSCF.
• the S-CSCF forwards the OK NOTIFY message to the AS, per step S407.
• FIGS. 7A-7B are signal flow diagrams further defining step S500 of FIG. 2 according to an example embodiment. For the purpose of explanation, the method described in FIGS. 7A-7B can be
• FIG. 1 implemented in the network architecture illustrated in FIG. 1 , but is not limited to this implementation. Therefore, reference numerals from FIG. 1 are not necessarily used in FIGS. 7A-7B.
• step S501 illustrates a join call request being sent by the unconnected UE-3 to the S-CSCF.
• the join call request is sent in response to the UE-3 being picked up by a user and/ or subscriber.
• the join call request may be a SIP INVITE request.
• the SIP INVITE request may include a special value in the SIP 805254 13
• the S-CSCF then forwards the join call request to the AS in step S503.
• the AS may activate a conferencing procedure to join the calling UE- 1 and all the associated UEs with the shared identifier.
• the conference may be a multi-way conference connection, such that all the parties may be joined.
• the parties may be joined using the MRF.
• an INVITE message is sent from the AS to the MRF.
• the INVITE message includes an offer, with a UE-3 identifier, to enter into a conference connection.
• the offer may be an SDP offer from the UE-3.
• the MRF may respond by sending a confirmation of the INVITE message.
• the confirmation is an OK INVITE message sent to the AS, per step S507.
• the OK INVITE may include an SDP answer from the MRF.
• the AS forwards the OK INVITE from the MRF to the S-CSCF.
• the S-CSCF forwards the OK INVITE to the unconnected associated UE-3, per step S51 1.
• the unconnected associated UE-3 responds by sending an ACK back to the S-CSCF (step S513), which is then forwarded to the AS (step S515).
• the AS forwards the ACK to the MRF.
• the calling UE- 1 and the connected associated UE-2 may also be joined to the multi-way conference connection, as shown in FIG. 7B.
• the AS sends a REINVITE message to the S-CSCF, per step S521.
• the REINVITE message may not include an SDP message.
• the S-CSCF forwards the REINVITE message to the connected associated UE-2.
• the UE-2 may respond by sending a confirmation of the REINVITE message.
• step S529 the AS sends an INVITE message, with an offer from the connected associated UE-2, to the MRF.
• the MRF confirms the INVITE by responding with an OK INVITE message sent to the AS, as shown in step S531.
• the AS sends an ACK to the S- CSCF (step S533), which is forwarded by the S-CSCF to the connected associated UE-2 (step S535).
• the AS also sends an ACK to the MRF, per step S537. In this manner, the connected associated UE-2 is also joined to the multi-way conference connection alongside the
• the calling UE- 1 may be joined to the multi-way conference
• step S541 the AS sends a REINVITE message to the S-CSCF, which is thereafter forwarded by the S-CSCF to the calling UE- 1 in step S543.
• the REINVITE message may not include an SDP message.
• the calling UE- 1 Upon receipt of the REINVITE message, the calling UE- 1 responds by sending an OK REINVITE message to the S-CSCF (step S545), which is forwarded by the S-CSCF to the AS (step S547).
• step S549 the AS sends an INVITE message, with an offer from the calling UE- 1 , to the MRF.
• the MRF confirms the INVITE by responding with an OK INVITE message sent to the AS, as shown in step S551.
• the AS sends an ACK to the S-CSCF (step S553), which is forwarded by the S-CSCF to the connected associated UE-2 (step S555).
• the AS also sends an ACK to the MRF, per step S557. In this manner, the calling UE-2 is also joined to the multi-way conference connection alongside the connected associated UE-2 and the previously unconnected
• FIGS. 8A-8B are signal flow diagrams further defining step S600 of FIG. 2 according to an example embodiment.
• the method described in FIGS. 8A-8B can be
• FIG. 1 implemented in the network architecture illustrated in FIG. 1 , but is not limited to this implementation. Therefore, reference numerals from FIG. 1 are not necessarily used in FIGS. 8A-8B.
• the multi- way conference connection may then be terminated.
• Each of the associated UEs may disconnect simultaneously or at different intervals.
• the connected UE-2 may disconnect from the multi-way conference connection while the calling UE- 1 and the previously unconnected UE-3 may remain in the multi-way conference connection.
• the calling UE- 1 and the previously unconnected UE-3 may be transferred to a connection other than the multi-way conference connection when the connected UE-2 disconnects.
• FIG. 8A illustrates an example embodiment of the connected UE-2 disconnecting from the multi-way conference connection while the calling UE- 1 and the previously unconnected UE-3 remain in the multi-way conference connection.
• the connected associated UE-2 (now a terminating associated UE-2) hangs up, causing a BYE message to be sent from the associated UE-2 to the S- CSCF, as shown in step S601.
• the S-CSCF forwards the BYE message to the AS.
• the AS being informed that the terminating associated UE-2 intends to disconnect from the multi-way conference connection, forwards the BYE message to the MRF as shown in step S605.
• the BYE message may include information corresponding to 805254 16
• the corresponding information is dialog from the terminating associated UE-2 to the MRF.
• the MRF responds in step S607 by sending a confirmation OK BYE message to the AS, which the AS forwards to the S-CSCF in step S609.
• the S-CSCF likewise forwards the confirmation OK BYE message to the terminating associated UE-2 in step S61 1.
• the terminating Upon receipt of the confirmation OK BYE message, the terminating
• step S613 the multi-way conference connection is disconnected from the multi-way conference connection as shown in step S613, such that only the calling UE- 1 and the previously unconnected associated UE-3 remain in the multi- way conference connection. Accordingly, because the multi-way conference connection still exists, all unconnected associated UEs may still be notified that the line remains active. Eventually, the multi-way conference connection may be completely terminated by the remaining UEs in the multi-way conference connection.
• the previously unconnected UE-3 (now terminating associated UE-3) hangs up in step S615, causing a BYE message to be sent to the S-CSCF.
• the S-CSCF forwards the BYE message to the AS, as shown in step S-617.
• the AS then forwards the BYE message, along with dialog from the terminating associated UE-3, to the MRF as shown in step S619.
• the MRF responds in step S621 by sending a confirmation OK BYE message to the AS, which the AS forwards to the S-CSCF in step S623.
• the S-CSCF likewise forwards the confirmation OK BYE message to the terminating associated UE-3 in step S627.
• the terminating associated UE-3 is disconnected from the multi-way conference connection as shown in step S629. 805254 17
• the calling UE- 1 may be disconnected from the multi-way conference connection in a similar fashion to the above described terminating associated UEs. However, because the calling UE- 1 is the last remaining UE in the multi-way conference connection, the AS may initiate the termination process. More specifically, the AS sends a
• step S633 BYE message, with dialog from the calling UE- 1 , to the MRF as shown in step S631.
• the MRF responds in step S633 by sending a
• step S635 the AS sends to the S-CSCF a BYE message, which the S-CSCF forwards to the calling UE- 1 in step S37.
• the calling UE- 1 Upon receipt of the BYE message, the calling UE- 1 sends its own confirmation OK BYE message to the S-CSCF in step S639, which the S-CSCF forwards to the AS in step S643.
• the calling UE- 1 also disconnects from the multi-way conference connection in step S641 , such that the multi- way conference connection is terminated.
• FIG. 9 is a signal flow diagram further defining step S700 of FIG. 2 according to an example embodiment.
• the method described in FIG. 9 can be implemented in the network architecture illustrated in FIG. 1 , but is not limited to this
• the associated UEs may be notified that the line corresponding to the shared phone number is idle. For example, in step S701 of FIG. 9 the AS sends a line-idle notification to the S- CSCF, which in step S703 the S-CSCF forwards to the associated UE- 2. As previously discussed with respect to FIG. 8A, the associated UE-2, which is currently idle, may then respond with a confirmation 805254 18
• the associated UE-2 responds by sending an OK NOTIFY message to the S-CSCF in step S705.
• the S- CSCF then forwards the OK NOTIFY message to the AS, per step S707.
• step S709 the AS sends a line-idle notification to the S-CSCF, which in step S71 1 the S- CSCF forwards to the associated UE-3.
• step S713 the associated UE-3 responds by sending an OK NOTIFY message to the S-CSCF, which the S-CSCF then forwards to the AS, per step S715.

Landscapes

• Engineering & Computer Science (AREA)
• Multimedia (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Business, Economics & Management (AREA)
• General Business, Economics & Management (AREA)
• Telephonic Communication Services (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (1)

Family

ID=43501110

Family Applications (1)

Country Status (7)

Families Citing this family (11)

Citations (1)

Family Cites Families (15)

• 2009
  • 2009-12-08 US US12/654,019 patent/US9641557B2/en active Active
• 2010
  • 2010-11-17 KR KR1020127017516A patent/KR101395589B1/ko active IP Right Grant
  • 2010-11-17 EP EP10782135.7A patent/EP2510664B1/en active Active
  • 2010-11-17 CN CN201080055408.9A patent/CN102696213B/zh active Active
  • 2010-11-17 WO PCT/US2010/056941 patent/WO2011071665A1/en active Application Filing
  • 2010-11-17 JP JP2012543131A patent/JP5832446B2/ja active Active
  • 2010-12-02 TW TW099141973A patent/TWI477125B/zh active

Patent Citations (1)

Also Published As

Similar Documents

Legal Events