WO2002015549A2 - Systeme et procede pour transferer des communications dans des reseaux locaux a commutation par paquets - Google Patents

Systeme et procede pour transferer des communications dans des reseaux locaux a commutation par paquets Download PDF

Info

Publication number
WO2002015549A2
WO2002015549A2 PCT/US2001/025716 US0125716W WO0215549A2 WO 2002015549 A2 WO2002015549 A2 WO 2002015549A2 US 0125716 W US0125716 W US 0125716W WO 0215549 A2 WO0215549 A2 WO 0215549A2
Authority
WO
WIPO (PCT)
Prior art keywords
subscriber
gateway
port
call
point
Prior art date
Application number
PCT/US2001/025716
Other languages
English (en)
Other versions
WO2002015549A3 (fr
Inventor
Subrata Mukherjee
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 AU2001284998A priority Critical patent/AU2001284998A1/en
Publication of WO2002015549A2 publication Critical patent/WO2002015549A2/fr
Publication of WO2002015549A3 publication Critical patent/WO2002015549A3/fr

Links

Classifications

    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/58—Arrangements for transferring received calls from one subscriber to another; Arrangements affording interim conversations between either the calling or the called party and a third party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present invention relates generally to packet switched local area networks, and specifically to call transfer mechanisms within packet switched local area networks .
  • IP Voice over Internet Protocol
  • H.320 and H.324I/M are utilized.
  • H.324 standards apply to Public Switched Telephony Networks (PSTNs)
  • PSTNs Public Switched Telephony Networks
  • PLMNs Public Land Mobile Networks
  • LANs Local Area Networks
  • H.323 standards are used.
  • H.323 endpoints may be integrated into personal computers, implemented in standalone devices, such as wireline or wireless telephones or implemented in wireless telecommunications systems.
  • H.323 endpoints advantageously provide real-time audio, video and/or data communications capabilities in point-to-point or multipoint conferences.
  • Each H.323 endpoint is registered with a Gatekeeper for the H.323 system.
  • the Gatekeeper stores an IP address for the H.323 endpoint, so that when a connection to that H.323 endpoint is requested, the Gatekeeper knows how to route the connection.
  • the IP address for the MS typically includes the IP address for a Mobile Switching Center (MSC) serving the MS for call signaling.
  • MSC Mobile Switching Center
  • H.323 systems currently support call transfer services, which allows the transferring end-point, which is the party that has one held call and one active call, to connect the remote end-points of the two calls and disconnect itself.
  • the protocol used by the H.323 network for the call transfer function is specified by H.450 standards. In the H.450 solution, after the transferring end-point invokes call transfer, the original two calls are released and a new call is established' between the transferred end-point and the transferred-to end-point.
  • both the transferred end-point and transferred-to end-point are within the H.323 system, .the speech and/or data (commonly referred to as the media stream or media packets) are routed directly between the transferred end-point and transferred-to end-point.
  • This requires both the transferred end-point and the transferred-to end-point to change the address of sent packets from the transferring end-point's address to each other's address.
  • both the transferred end-point and the transferred-to end-point must have knowledge of the call transfer and have the ability to perform the address switch. Implementing part of the call transfer functionality within the H.323 end-points themselves is neither efficient, nor desirable.
  • the H.450 solution is extremely difficult to implement when either the transferred subscriber and/or the transferred-to subscriber are within another system, such as the PLMN/PSTN. Since the PLMN/PSTN does not support H.323 protocols, when the transferred and/or transferred-to subscriber belongs to the PLMN/PSTN, the H.450 standard will not be supported by these subscribers. Therefore, in order to perform call transfer when one or both of the remote parties is within the PLMN/PSTN, the H.323 network must intercept the H.450 messages and simulate end-point behaviors in the Gateway that is responsible for PLMN/PSTN and H.323 interworking.
  • the transferring subscriber (hereinafter referred to as the A subscriber) is within the H.323 network and both the transferred subscriber (hereinafter referred to as the B subscriber) and the transferred-to subscriber (hereinafter referred to as the C subscriber) are outside of the H.323 network
  • the speech and/or data from subscriber B is routed to the Gateway.
  • the Gateway must have knowledge about the call transfer and must route the speech and/or data to subscriber C.
  • the speech and/or data from subscriber C is routed to the Gateway, and the Gateway must route the speech and/or data from subscriber C to subscriber B.
  • the Gateway must include the end-point functionality for H.450 call transfer handling. It is neither desirable, nor efficient, to require Gateways to include part of the call transfer functionality. It is, therefore, an object of the present invention to route the media packets through the transferring end- point after the call is transferred between the transferred and transferred-to end-points. It is a further object of the present invention to enable the transferring end-point to be free to make other transactions after call transfer.
  • the present invention is directed to telecommunications systems and methods for providing call transfer services within H.323 networks.
  • the transferring end-point relays the media packets received from the transferred end-point to the transferred-to end-point, and likewise relays media packets received from the transferred-to end-point to the transferred end-point.
  • the transferring end-point is taken out of the call after transferring the call so that it can make/receive new calls.
  • inter- working with the PLMN/PSTN is easy to implement since no call transfer functionality needs to be included within the Gateway.
  • no additional functionality needs to be included within the transferred and/or transferred-to end-points since both end-points still route media packets to the transferring end-point.
  • FIGURE 1 is a block diagram of a conventional H.323 system
  • FIGURES 2A-2D are block diagrams of an H.323 system implementing the call transfer service where the transferring end-point, transferred end-point and transferred-to end-point are all within the H.323 system, in accordance with embodiments of the present invention
  • FIGURE 3 is a signaling diagram illustrating the signaling involved in performing the call transfer service shown in FIGURES 2A-2D;
  • FIGURES 4A-4D are block diagrams illustrating the implementation of the call transfer service within an H.323 system where the transferring end-point and transferred-to end-point are within the H.323 system, but the transferred subscriber is outside of the H.323 system, in accordance with embodiments of the present invention;
  • FIGURES 5A-5D are block diagrams illustrating the implementation of the call transfer service within an H.323 system where the transferring end-point is within the H.323 system, but the transferred subscriber and transferred-to subscriber are outside of the H.323 system, in accordance with embodiments of the present invention
  • FIGURES 6A and 6B are block diagrams of an H.323 system implementing the call transfer service where the transferring end-point has performed an inter-A-bis Gateway (AGW) handover;
  • AGW inter-A-bis Gateway
  • FIGURE 7 is a signaling diagram illustrating the signaling involved in performing the call transfer service shown in FIGURES 6A and 6B
  • FIGURES 8A and 8B are block diagrams illustrating the implementation of the call transfer service within an H.323 system where the transferring end-point has performed a handover outside of the H.323 system
  • FIGURE 9 is a signaling diagram illustrating the signaling involved in performing the call transfer service shown in FIGURES 8A and 8B;
  • FIGURE 10 is a signaling diagram illustrating the signaling involved in disconnecting the transferred call in accordance with any embodiment of the present invention.
  • FIGURE 11 is a block diagram illustrating the implementation of the call transfer service within an H.323 system when the transferring subscriber is a regular H.323 end-point (i.e. fixed type).
  • each H.323 end-point is registered with an H.323 Gatekeeper for the H.323 system.
  • the Gatekeeper stores an Internet Protocol (IP) address for the H.323 end-point, and uses the IP address to route a connection to that H.323 end-point.
  • IP Internet Protocol
  • the H.323 end-point includes a Mobile Station (MS) 20, such as a cellular telephone
  • the IP address for the MS 20 for call signaling typically includes the IP address for a Mobile Switching Center (MSC) 54 serving the MS 20.
  • MSC Mobile Switching Center
  • the IP address includes the IP address of an A-bis Gateway (AGW) 40 connected to the MSC 54, along with a specific port number for that MS 20. The port number is associated with a specific media port for the MS 20 within the AGW 40.
  • AGW A-bis Gateway
  • the H.323 end-point from the Gatekeeper's perspective consists of at least both the AGW 40 and the MS 20 for media connections.
  • the AGW 40 is connected to an associated Base Transceiver Station (BTS) 30, which operates as a transceiver for transmitting and receiving data and control messages to and from the MS 20 over an air interface 25.
  • BTS Base Transceiver Station
  • the AGW 40 has both a signaling connection (shown by the dotted line 80) and a media connection (shown by the solid line 90) to it's associated BTS 30.
  • each AGW 40 may have a media connection 90 to other AGW' s 40 depending on the call scenario.
  • the AGW 40 also has a signaling connection 80 to the MSC 54 and a Base Station Controller (BSC) 52, which is responsible for controlling one or more BTS's 30.
  • BSC Base Station Controller
  • the MSC 54 and BSC 52 nodes can be included together within a single node, referred to herein as an Access Node 50.
  • the MSC 54 is termed a Network Access Controller and the BSC 52 is termed a Radio Network Server.
  • the AGW 40 converts between the circuit- switched signaling and data transport used by the BTS 30 and the packet-switched signaling and data transport used by the H.323 system 10.
  • H.323 end-points 20 and subscribers outside of the H.323 system 10 are routed through a Gateway 70, which converts the speech and/or data between the IP format used by the H.323 system 10 and the PLMN/PSTN format.
  • Calls coming into the H.323 system 10 from outside are routed through the Gateway 70 to the Gatekeeper 60, and subsequently to the desired H.323 end- point 20.
  • media packets are transmitted directly between the H.323 end-point 20 and the Gateway 70 over the media connection 90, and speech and/or data is transmitted between the Gateway 70 and the non-H.323 subscriber (not shown) via the non-H.323 subscriber's network (not shown).
  • FIGURES 2A-2D of the drawings if an MS 20 within the H.323 system 10 (hereinafter referred to as subscriber A) makes or receives a call from another H.323 end-point 85 (hereinafter referred to as subscriber B) , and at some point thereafter, puts subscriber B 85 on hold and either places a new call to another H.323 end-point 95 (hereinafter referred to as subscriber C) or receives a call from subscriber C 95, and subscriber A 20 wants to connect subscriber B 85 with subscriber C 95 into a new call between themselves, subscriber A 20 can invoke the call transfer service.
  • subscriber's B and C can be any H.323 end-point, such as another MS, an IP phone, a PC phone or a PBX terminal within the H.323 system 10.
  • the call transfer service enables the controlling mobile subscriber (subscriber A) who has one active call (subscriber C) and one held call (subscriber B) , each of which can be an incoming or outgoing call, to connect the remote parties of the two calls (subscribers B and C) and release the controlling subscriber's (subscriber A) own connection.
  • the controlling subscriber (subscriber A) is then free to make or receive other calls.
  • the call transfer service can be invoked using any man machine interface (MMI) , such as pressing SEND" on the MS 20.
  • MMI man machine interface
  • the signaling connection 80 for the call between subscriber A 20 and subscriber B 85 goes from subscriber A (MS) 20 to the BTS 30, AGW 40, Access Node 50, Gatekeeper 60 and finally to subscriber B 85.
  • the signaling connection 80 goes from subscriber A 20 to the BTS 30, AGW 40, Access Node 50, Gatekeeper 60 and finally to subscriber C 95.
  • MSC and BSC functionality shown in FIGURE 1 are within two separate nodes, the connection would go to both the BSC and the MSC.
  • the media connection 90 for the call between subscriber A 20 and subscriber B 85 normally goes from subscriber A 20 to the BTS 30 to the media port (MP) 42 in the AGW 40 for subscriber A 20 and then from the real time protocol (RTP) port 44 assigned to the call in the AGW 40 (hereinafter referred to as RTP
  • B 85 is the held call, the media connection between MP 42 and RTP (held) 44 is broken, so that media from subscriber A 20 cannot reach subscriber B 85, and vice-versa.
  • the media connection 90 goes from subscriber A 20 to the BTS 30, to the MP 42 in the AGW 40 and then directly from the RTP port 46 in the AGW 40 assigned to the call (hereinafter referred to as RTP (active) 46) to subscriber C 95.
  • subscriber A 20 sends a DTAP FACILITY message to the Access Node 50 (step 300) , which checks to make sure that subscriber A 20 is allowed to invoke the call transfer and has one active call (subscriber C 95) and one held call (subscriber B 85) (step 310) . Thereafter, the Access Node 50 sends a Media Port Disconnect Request (MPDR) message to the AGW 40 (step 320) , ordering the AGW 40 to break the link between the MP 42 for subscriber A 20 and RTP (active) 46. In response, the AGW 40 stops relaying the media packets received at the AGW 40 for the active call to the BTS 30 (step 330) .
  • MPDR Media Port Disconnect Request
  • the Access Node 50 sends a Start Relay
  • AGW 40 to start relaying media packets received on RTP
  • the Access Node 50 also sends another Start Relay Request message to the AGW 40 (step 350) ordering the AGW 40 to start relaying media packets received on RTP (held) 44 to the IP address of the active call (subscriber C 95) .
  • the Access Node 50 sends a Disconnect message to the MS 20 for the held call (A-B call) (step 360) .
  • the held call is now disconnected from subscriber A 20.
  • the Access Node 50 sends a Disconnect message for the active call to the MS 20 (step 370) to release the active call.
  • the Access Node 50 sends a message to the BTS 30
  • step 380 the MS 20 is free to make and receive new calls, and the MS 20 is not involved in the call connection between subscriber B 85 and subscriber C 95. Thereafter, the Access Node 50 marks the call transferred between the transferred-to 95 and transferred 85 end-points (step 390) .
  • the signaling connection 80 for the transferred call goes from subscriber B 85 to the Gatekeeper 60, to the
  • Access Node 50 to the AGW 40, back to the Access Node 50, back to the Gatekeeper 60 and finally to subscriber C 95.
  • the media connection 90 for the transferred call goes directly from subscriber B 85, to RTP
  • the signaling connection 80 for the call between subscriber A 20 and subscriber B 85 goes from subscriber A 20 to the BTS 30, AGW 40, Access Node 50, Gatekeeper 60, Gateway 70 and finally to subscriber B 85.
  • the signaling connection 80 goes from subscriber A 20 to the BTS 30, AGW 40, Access Node 50, Gatekeeper 60 and finally to subscriber C 95.
  • the media connection 90 (speech and/or data) for the call between subscriber A 20 and subscriber B 85 normally goes from subscriber B 85 to the Gateway 70, where the speech and/or data are converted from circuit-switched into packet-switched, to RTP (held) 44 in the AGW 40 and then to subscriber A 20 via the MP 42 in the AGW 40 for subscriber A 20 and the BTS 30.
  • the media connection 90 between MP 42 and RTP (held) 44 is broken so that media from subscriber A 20 cannot reach subscriber B 85, and vice- versa.
  • the media connection 90 goes from subscriber A 20 to the BTS 30, to the MP 42 in the AGW 40 for subscriber A 20 and then directly from RTP (active) 46 in the AGW 40 to subscriber C 95.
  • the signaling connection 80 for the transferred call goes from subscriber B 85 to the Gateway 70, to the Gatekeeper 60, to the Access Node 50, to the AGW 40, back to the Access Node 50, back to the Gatekeeper 60 and finally to subscriber C 95.
  • the media connection 90 for the transferred call goes from subscriber B 85, to the Gateway 70, to RTP (held) 44 in the AGW 40, and then directly to subscriber C 95 for speech and/or data originated by subscriber B 85, and from subscriber C 95 to RTP (active) 46 in the AGW 40 to the Gateway 70 and finally to subscriber B 85 for media packets originated by subscriber C 95.
  • FIGURES 5A-5D of the drawings when both remote parties (subscriber's B 85 and C 95) are outside of the H.323 system 10, here shown within the PLMN/PSTN 15, the process is similar to that described in connection with FIGURES 4A-4D of the drawings.
  • more than one Gateway 70 may be involved if subscriber's B 85 and C 95 are within different networks served by different Gateways 70. For example, if subscriber B 85 and subscriber C 95 are within two different countries, two Gateways 70 may be involved.
  • FIGURES 5A-5D For convenience, only one Gateway 70 is shown in FIGURES 5A-5D.
  • the signaling connection 80 for the call between subscriber A 20 and subscriber B 85 goes from subscriber A 20 to the BTS 30, AGW 40, Access Node 50, Gatekeeper 60, Gateway 70 and finally to subscriber B 85.
  • the signaling connection 80 goes from subscriber A 20 to the BTS 30, AGW 40, Access Node 50, Gatekeeper 60, Gateway 70 and finally to subscriber C 95.
  • the media connection 90 (speech and/or data) for the call between subscriber A 20 and subscriber B 85 is not active since subscriber B 85 is the held call, and therefore, the connection between MP 42 and RTP (held) 44 is broken.
  • the media connection 90 goes from subscriber A 20 to the BTS 30, to the MP port 42 in the AGW 40 for subscriber A 20, from RTP (active) 46 in the AGW 40 to the Gateway 70 and finally to subscriber C 95.
  • the signaling connection 80 for the transferred call goes from subscriber B 85 to the Gateway 70, to the Gatekeeper 60, to the Access Node 50, to the AGW 40, back to the Access Node 50, back to the Gatekeeper 60, back to the Gateway 70 and finally to subscriber C 95.
  • the media connection 90 for the transferred call goes from subscriber B 85 to the Gateway 70, to RTP (held) 44 in the AGW 40, back to the Gateway 70 and finally to subscriber C 95 for speech and/or data originated by subscriber B 85.
  • the media connection 90 goes from subscriber C 95, to the Gateway 70, to RTP (active) 46 in the AGW 40, back to the Gateway 70 and finally to subscriber B 85.
  • the situation is more complicated if subscriber A has performed an internal handover within the H.323 system when subscriber A invokes the call transfer service. An internal handover would normally occur when the MS has moved to a different cell served by a different BTS within the H.323 system.
  • the media connection for the two calls (held call and active call) before the call transfer has been invoked is shown in FIGURE 6A.
  • both of the remote parties subscribers B 85 and C 95
  • subscribers B 85 and C 95 can be within any system, as discussed in connection with FIGURES 4 and 5.
  • the media connection 90 for the call between subscriber A 20 and subscriber B 95 is not active, and therefore, the connection between MP 42 and RTP (held) 44 is broken, so that media from subscriber A 20 cannot reach subscriber B, and vice-versa.
  • the media connection 90 is shown going directly between subscriber B 85 to RTP (held) 44 in the anchor AGW 40a, which is the AGW_ 40a that subscriber A 20 has been handed over from.
  • the media connection 90 is more complicated.
  • the connection goes from subscriber A 20 to the BTS 30, to the MP 42 for subscriber A 20 in the non-anchor AGW 40b, which is the AGW 40b that subscriber A 20 has been handed over to, from the RTP port 49 for the call in the non- anchor AGW 40b to RTP (active) 46 in the anchor AGW 40a and finally to subscriber C 95.
  • the media connection goes from subscriber C 95 to RTP (active) 46 in the anchor AGW 40a, to the RTP port 49 assigned to the call in the non-anchor AGW 40b, to the BTS 30 via the MP 42 for subscriber A 20 in the non- anchor AGW 40b and finally to subscriber A 20.
  • RTP active
  • the MS 20 sends a DTAP FACILITY message to the Access Node 50 (step 700) .
  • the Access Node 50 checks to * make sure that subscriber A 20 has one active call (subscriber C 95) and one held call (subscriber B 85) (step 710) .
  • the Access Node 50 sends a Stop Relay Request message to the anchor AGW 40a to order the anchor AGW 40a to stop relaying packets between RTP (active) 46 in the anchor AGW 40a and the RTP port 49 in the non-anchor AGW 40b (step 720) . Thereafter, the Access Node 50 sends the Start Relay Request message to the anchor AGW 40a, which orders the anchor AGW 40a to start relaying media packets received on RTP (active) 46 to the IP address of the end-point associated with the held call (subscriber B 85) (step 730) .
  • the Access Node 50 also sends another Start Relay Request message to the anchor AGW 40a, which orders the anchor AGW 40a to start relaying media packets received on RTP (held) 44 (from subscriber B 85) to the IP address of the end-point associated with the active call (subscriber C 95) (step 740) .
  • subscribers B 85 and C 95 are involved in a call between themselves, but the MS (subscriber A 20) is not yet free to make and receive new calls. Therefore, as discussed above in connection with FIGURE 3, in order to free subscriber A 20, the Access Node 50 sends a Disconnect message to the MS 20 for the held call (A-B call) (step 750) .
  • the held call is now disconnected from subscriber A 20.
  • the same process occurs for the active call (Access Node 50 sends a Disconnect message (step 760) for the active call to the MS 20) .
  • the Access Node 50 sends a message to the BTS 30 (step 770) . Now, the MS 20 is free to make and receive new calls, and the MS 20 is not involved in the call connection between subscriber B 85 and subscriber C 95. Finally, to release the assigned RTP port 49 in the non-anchor AGW 40b, the Access Node 50 orders the non-anchor AGW 40b to release the assigned RTP port 49 in the non-anchor AGW 40b (step 780) . Thereafter, the Access Node 50 marks the call transferred between the transferred-to and transferred end- points (step 790) .
  • media packets originated by subscriber B 85 go from subscriber B 85 to RTP (held) 44 in the anchor AGW 40a and then to subscriber C 95.
  • the media connection 90 goes from subscriber C 95 to RTP (active) 46 in the anchor AGW 40a to subscriber B 85.
  • FIGURE 8A A similar situation occurs when subscriber A has performed an external handover to a BTS outside of the H.323 system.
  • the media connection 90 is close to that shown in FIGURE 6A, except that there is not a non-anchor AGW. Instead, the media packets from subscriber C 95 for the active call are routed between RTP (active) 46 in the AGW 40 originally serving the MS 20 and an RTP port 72 for the MS 20 in the Gateway 70.
  • the Gateway 70 converts the media packets from packet-switched to circuit-switched and transmits the circuit-switched speech and/or data from the RTP port 72 for the MS 20 in the Gateway 70 to the PLMN 15, which relays the speech and/or data to the MS 20 via a MSC 54, BSC 52 and BTS 30 within the PLMN 15 serving the MS 20.
  • speech and/or data received from the MS 20 at the RTP port 72 in the Gateway 70 are converted into media packets and routed to subscriber C 95 via RTP (active) 46 within the AGW 40.
  • the call transfer service can still be invoked even in this case.
  • the MS 20 sends a DTAP FACILITY message to the Access Node 50 (step 900) . It should be understood that all messages sent between the Access Node 50 and the MS 20 (and MSC 54, BSC 52 and BTS 30) within the PLMN 15 go through the Gateway 70.
  • the Access Node 50 then checks to make sure that subscriber A 20 has one active call and one held call (step 910) .
  • the Access Node 50 sends the Stop Relay Request message to the AGW 40, which orders the AGW 40 to stop relaying packets from RTP (active) 46 in the AGW 40 to the RTP port 72 for the MS 20 in the Gateway 70 (step 920) . Thereafter, the Access Node 50 sends the Start Relay Request message to the AGW 40, which orders the AGW 40 to start relaying voice packets received on RTP (active) 46 to the IP address of the end-point for the held call (subscriber B 85) (step 930) .
  • the Access Node 50 also sends another Start Relay Request message to the AGW 40 that orders the AGW 40 to start relaying voice packets received on RTP (held) 44 to the IP address of the end- point for the active call (subscriber C 95) (step 940) .
  • subscribers B 85 and C 95 are involved a call between themselves, but subscriber A 20 is not yet free to make and receive new calls. Therefore, in order to free subscriber A 20, the Access Node 50 sends a Disconnect message (encapsulated in a MAP_ Forward_Access_Signalling message) to the MS 20 for the held call (A-B call) (step 950) .
  • the held call is now disconnected from subscriber A.
  • Access Node 50 sends an encapsulated Disconnect message (step 960) for the active call to the MS 20) .
  • the Access Node 50 sends a message (encapsulated in a MAP_ Forward_Access_Signalling message) to the BTS 30 within the PLMN 15 (step 970) .
  • the MS 20 is free to make and receive new calls, and the MS 20 is not involved in the call connection between subscriber B 85 and subscriber C 95.
  • the Access Node 50 sends a message to release the handover call to the Gatekeeper 60 (step 980) .
  • the Access Node 50 marks the call transferred between the active and held end-points (step 990) .
  • media packets originated by subscriber B 85 go .from subscriber B 85 to RTP (held) 44 in the AGW 40 and then to subscriber C 95.
  • the media connection 90 goes from subscriber C 95 to RTP (active) 46 in the AGW 40 to subscriber B 85.
  • FIGURE 10 of the drawings the steps for either subscriber B or subscriber C to disconnect the transferred call are shown. It should be noted that it makes no difference in the disconnect process where subscriber's B and C are located or whether there is one AGW, two AGWs or one AGW and one Gateway involved.
  • the Gatekeeper 60 transmits a Release Complete message to the Access Node 50 for the A-B call (step 100) .
  • the Access Node 50 sends a Release Complete message to the Gatekeeper 60 for the A-C call (step 110) .
  • the Access Node 50 sends a release RTP message to the AGW 40 for releasing RTP (active) (step
  • the AGW 40 After the AGW 40 releases RTP (active), the AGW 40 sends an Acknowledgment message back to the Access Node 50 (step 130) .
  • the Access Node 50 also sends a release RTP message to the AGW 40 for releasing RTP (held) (step 140) .
  • the AGW 40 After the AGW 40 releases RTP (held) , the AGW 40 sends an Acknowledgment message back to the Access Node 50 (step 150). Finally, the Access Node 50 releases all of it's resources for the A-B call and the A-C call (step 160) .
  • the same two charging records that were generated before call transfer keep gathering data and are not closed until B or C disconnects.
  • neither the B nor C subscriber needs to have knowledge of the transfer (i.e. subscriber's B and C still route to subscriber A, so they do not need to change the IP address of the receiving end-point) .
  • inter-working with the PLMN/PSTN is easily implemented without impacting the Gateway.
  • the above-described call transfer system and method can also be used when the transferring end-point is a regular (fixed) H.323 end-point, such as a PC, IP phone or PBX.
  • the H.323 end-point 40 needs to perform similar actions.
  • the controlling node for the call transfer service is the H.323 end-point 40 itself, whereas for the situation where the H.323 end-point includes an MS, the controlling node is the
  • the signaling 80 and media connections 90 will be similar to those shown in FIGURES 4 and 5, except that the Access Node 50 and AGW 40 of FIGURES 4 and 5 are replaced by the transferring H.323 end-point 40.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un système et un procédé de télécommunication pour fournir des services de transfert de communications dans des réseaux H.323. Dans ce système, l'extrémité de transfert qui appelle un transfert de communication retransmet les paquets multimédias reçus de l'extrémité transférée vers l'extrémité à laquelle est transférée la communication, et de même, retransmet les paquets multimédias reçus de l'extrémité vers laquelle est transférée la communication à l'extrémité transférée. Cependant l'extrémité de transfert est désengagée de la communication après avoir transférer cette dernière, de manière à pouvoir effectuer/recevoir de nouvelles communications.
PCT/US2001/025716 2000-08-17 2001-08-17 Systeme et procede pour transferer des communications dans des reseaux locaux a commutation par paquets WO2002015549A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001284998A AU2001284998A1 (en) 2000-08-17 2001-08-17 System and method for call transfer in packet switched local area networks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/641,437 2000-08-17
US09/641,437 US6904027B1 (en) 2000-08-17 2000-08-17 System and method for call transfer in packet switched local area networks

Publications (2)

Publication Number Publication Date
WO2002015549A2 true WO2002015549A2 (fr) 2002-02-21
WO2002015549A3 WO2002015549A3 (fr) 2002-04-25

Family

ID=24572371

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/025716 WO2002015549A2 (fr) 2000-08-17 2001-08-17 Systeme et procede pour transferer des communications dans des reseaux locaux a commutation par paquets

Country Status (3)

Country Link
US (1) US6904027B1 (fr)
AU (1) AU2001284998A1 (fr)
WO (1) WO2002015549A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012058817A1 (fr) * 2010-11-05 2012-05-10 Huawei Technologies Co., Ltd. Procédé de fourniture d'un raccourci de trafic local dans un réseau de communication mobile orienté paquet

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7061894B2 (en) * 2001-08-07 2006-06-13 Industrial Technology Research Institute System and method for providing voice communications for radio network
US8774155B2 (en) * 2006-02-03 2014-07-08 Broadcom Corporation Transporting call data via a packet data network
US8660555B2 (en) * 2006-11-03 2014-02-25 Core Wireless Licensing S.A.R.L. Quality of service mechanism
US8619668B2 (en) * 2007-06-07 2013-12-31 Qualcomm Incorporated Mobility management mode selection in multiple access wireless networks
CN102792643B (zh) * 2009-12-09 2016-01-20 爱立信(中国)通信有限公司 基于分组的通信网络中的呼叫交换

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5999965A (en) * 1996-08-20 1999-12-07 Netspeak Corporation Automatic call distribution server for computer telephony communications
US6014377A (en) * 1998-08-05 2000-01-11 Us West, Inc. System and method for an integrated wireline/wireless service using private branch exchange lines
US6466662B1 (en) 1998-12-21 2002-10-15 Siemens Aktiengesellschaft Method of implementing a call transfer from the active status in a communications network based on ITU-T standard H.323
US6535730B1 (en) * 1998-12-31 2003-03-18 At&T Corp. Wireless centrex conference call adding a party
US6731609B1 (en) * 1998-12-31 2004-05-04 Aspect Communications Corp. Telephony system for conducting multimedia telephonic conferences over a packet-based network
US6614784B1 (en) * 1999-01-15 2003-09-02 Telefonaktiebolaget L M Ericsson (Publ) System and method for providing supplementary services (SS) in an integrated telecommunications network
US6650745B1 (en) * 1999-06-10 2003-11-18 Avaya Technologies Corp. Method and apparatus for dynamically exchanging data among participants to a conference call
US6603849B2 (en) * 1999-08-20 2003-08-05 Ericsson Inc. System and method for call re-direction in H.323 network
US6577622B1 (en) * 1999-09-27 2003-06-10 3Com Corp. System and method for using a portable information device to establish a conference call on a telephony network
US6646997B1 (en) * 1999-10-25 2003-11-11 Voyant Technologies, Inc. Large-scale, fault-tolerant audio conferencing in a purely packet-switched network
US6687360B2 (en) * 1999-12-30 2004-02-03 At&T Corp. Personal IP follow-me service
US6650901B1 (en) * 2000-02-29 2003-11-18 3Com Corporation System and method for providing user-configured telephone service in a data network telephony system
US6731630B1 (en) * 2000-02-29 2004-05-04 3Com Corporation Flexible dial plan for a data network telephony system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012058817A1 (fr) * 2010-11-05 2012-05-10 Huawei Technologies Co., Ltd. Procédé de fourniture d'un raccourci de trafic local dans un réseau de communication mobile orienté paquet

Also Published As

Publication number Publication date
US6904027B1 (en) 2005-06-07
WO2002015549A3 (fr) 2002-04-25
AU2001284998A1 (en) 2002-02-25

Similar Documents

Publication Publication Date Title
US7675906B2 (en) Media communication system, and terminal apparatus and signal conversion apparatus in said system
EP1665686B1 (fr) Systeme et procede pour fournir de la transparence dans les caracteristiques de reseau prive
US7751376B2 (en) System for establishing data transmission path between mobile phone terminals
US6954518B1 (en) Voice over IP voice mail system configured for placing an outgoing call and returning subscriber to mailbox after call completion
EP1325618B1 (fr) Transmission de la voix sur des systemes a commutation par paquets sans fil
EP1362456B1 (fr) Systeme et procede d'interception de telecommunications
EP1665830B1 (fr) Systeme et procede pour distribuer des caracteristiques de reseau prive a un reseau public
EP1661417B1 (fr) Procedes et systemes de transfert d'appel dans une passerelle de medias
CA2368474A1 (fr) Traitement d'appels effectues a partir de portables dans des reseaux de communication fonde sur un protocole de commutation de paquets
US7496088B2 (en) Method for establishing a call in a telecommunications network; telecommunications network; and controlling device for packet networks
US6904027B1 (en) System and method for call transfer in packet switched local area networks
KR100488258B1 (ko) Ｗｃｄｍａ망과 ｃｄｍａ2000 1ｘｅｖ-ｄｏ망 사이의화상전화 연동 방법
KR20050013684A (ko) 이동 통신망에서의 화상 전화 서비스 제공 방법
JP2008141490A (ja) 緊急通報制御装置、無線通信端末および基地局
JP2002354144A (ja) ゲートウェイ及びルータ
KR20020049675A (ko) 이동 통신 시스템에서 영상 호 제어 방법
KR20030059532A (ko) 인터넷 프로토콜 기반 이동 교환국을 포함하는 이동 통신시스템

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
NENP Non-entry into the national phase

Ref country code: JP