Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q11/00—Selecting arrangements for multiplex systems
  • H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/1302—Relay switches
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13034—A/D conversion, code compression/expansion
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/1304—Coordinate switches, crossbar, 4/2 with relays, coupling field
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/1307—Call setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13091—CLI, identification of calling line
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13196—Connection circuit/link/trunk/junction, bridge, router, gateway
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13204—Protocols
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13209—ISDN
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/1327—Release and resetting of connection
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13282—Call forward, follow-me, call diversion
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13292—Time division multiplexing, TDM
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13335—Simulation, emulation
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13345—Intelligent networks, SCP
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13386—Line concentrator
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13389—LAN, internet

Definitions

• the present invention introduces IP-end points in a TDM- switch. More particularly, the invention provides a solution whereby an IP subscriber connection can be established relating to a TDM-switched connection. In realizing this solution, the invention further offloads the TDM traffic over IP network without a routing data base, extends the redundancy concept in the sense that the IP network is backed by TDM and provides wide range of TDM features to these IP- endpoints.
• TDM TDM network
• IP IP-based network
• IP intellectual property
• an object of the invention is to provide services for such an IP / TDM network.
• IP-CON IP-Connection
• TDM features are still available.
• some features in TDM require the knowledge of existence of the active (ongoing) call, which may have been moved from TDM into IP by an IP-CON of the present invention.
• the invention aims to maintain and extend these services. This leverages complexity of feature handling.
• An object of the present invention is to maintain the TDM switch.
• An object of the present invention is to not impact the TDM switch.
• An object of the present invention is not introduce a new node .
• An object of the present invention is to offer IP-endpoints on the TDM switch.
• An object of the present invention is to utilize TDM routing function.
• An object of the present invention is to utilize TDM administration.
• An object of the present invention is to use minimal TDM resources for introduced IP-endpoints.
• An object of the present invention is to utilize the feature fabric capability of the TDM switch for introduced IP- endpoints .
• An object of the present invention is to provide scalability.
• An object of the present invention is to provide a generic solution independent from the TDM-switch.
• An object of the present invention is enable the usage of TDM-feature fabric in the new IP-CON environment with limited exceptions .
• An object of the present invention is to provide TDM call services for an IP subscriber connection.
• an IP-subscriber connection in correspondence to an existing TDM connection between a subscriber A on an A-side of the TDM connection and a subscriber B on a B-side of the TDM connection.
• a set up signal including IP connection information and a caller ID of the subscriber A is sent to the B-side over the existing TDM connection.
• the A-side is invited to set up an IP connection from the B-side including IP connection information and a caller ID of the subscriber B.
• the IP-subscriber connection is established based on the IP connection information and caller ID from the subscriber A and the subscriber B.
• the IP-concentrator sets a trigger that causes a TDM switch on the A-side to pass control of an incoming call to the IP concentrator on the A- side.
• the TDM switch is instructed to resume call processing of the incoming call when the trigger is triggered.
• FIG 1 illustrates the TDM emulated IP call of the present invention
• Figure 2 illustrates the TDM emulated IP call basic flow of the present invention
• FIG. 3 illustrates the IP-CON basic call flow of the present invention.
• Figure 4 illustrates the call flow for a call waiting according to the present invention.
• IPCON IP- Concentrator
• IPCON is a call agent for the IP-subscribers.
• FIG. 1 assumes that the calling and the called termination are both IP-end points. At first glance, the figure resembles the common IP to TDM-TDM to IP call, seizing both IP and TDM resources for a single call. However, the figure includes some important differences. As will be made clear in the description below, the solution presented here adopts the philosophy that the TDM path is excessive and obsolete.
• the A-IPCON 102 receives the call request 104 from an A IP- subscriber 106, and forwards a corresponding setup 108 to the TDM-switch 110 (via, for example GR303 / V5) .
• the subscriber 106 is authenticated by the A-IPCON 102 to determine the subscriber's IP nature.
• the subscriber is further validated by the TDM-Switch 110 for its subscription.
• the call is then authenticated by the TDM network 112.
• the routing functionality of the TDM is utilized to select the facility.
• the TDM facilities are seized through the TDM network to the terminating office 114.
• the terminating office 114 is invoked to present the call to B-IPCON 116.
• a bearer- channel 118 is seized and TDM path between the involved A and B-IPCONs 102, 116 is setup.
• the A-IPCON and B-IPCON 102, 116 use the provided TDM path to exchange signals with each other. There are three methods to realize this signaling (explained later) .
• IPCONs 102, 116 attempt to setup an IP- connection 118. Once the IP-connection between A and B-IPCON 102, 116 is setup, the IPCONs 102, 116 negotiate the bearer path 118 through the IP-network 120. After the bearer path is established, the IPCONs 102, 116 can drop the TDM call so that the combinational path IP-TDM-TDM-IP from now on can be collapsed into one single IP path.
• the A-IPCON and B-IPCON 102, 116 of the previously described solution use the provided TDM path to exchange signals with each other.
• the instant solution provides the IP-CONs 102, 116 with at least three methods to realize this signaling.
• an A-IPCON 102 sends UU-info at the time of setup request, which is forwarded through to the B-IPCON 116.
• the B-IPCON 116 detects the IP nature of the originator.
• the B-IPCON 116 can initiate an IP-connection back toward the A- IPCON 102 using the information collected from the UU-info.
• the TDM-call presentation to the B- IPCON 116 includes the necessary information about the A- IPCON 102 using calling name delivery.
• the B-IPCON 116 detects the IP-nature of the origination.
• the B-IPCON 116 can initiate a backward IP-connection to the A-IPCON 102.
• an ISDN or Analog configuration there is provided an ISDN or Analog configuration. After the TDM-call is answered, the bearer path 118 is bi-directionally established. Hence, both IPCONs 102. 116 can exchange information inband. Any one of the IPCONs 102, 116 can be chosen to initiate the IP-connection.
• the three methods may be utilized individually or in any combination. A combination of the above three methods may guaranty interoperability between different implementations of IPCON.
• IP-TDM-TDM-IP IP-TDM-TDM-IP
• IPCONs can decide to drop any one of them or re-establish any one of them at any given time during the call. This can be used as a unique feature to empower a connection to become fault tolerant.
• the capability to decide provided by this solution to realize a connection on any one of the two networks (TDM or IP) offers a great deal of flexibility to dynamically control the load distribution. This solution is, in particular, beneficial for network congestion control .
• the TDM connection should not be dropped.
• the connection should remain as a TDM, regardless of the nature of the subscribers .
• the IPCON is a GR303/V5 concentrator, and all IP- subscribers behind the IPCON appear as regular subscriber to the TDM switch. Therefore, the administration of these IP- subscribers can be incorporated into the TDM-switch without any impact. Since the IPCON initiates every call through the TDM switch, therefore the TDM-feature fabric can be fully utilized.
• the IPCONs act as the call agents.
• the TDM pathway is set up.
• an IP call request 201 is sent from the subscriber A to the call agent.
• An SS7 IAM signal 203 is then sent to the signaling transfer protocol device from the switch.
• a TDM BEARER_PATH SETUP signal 204 is sent from the switch on the subscriber A side to the switch on the subscriber B side.
• an IP REINVITE signal 206 (that may include such information as the CALL ID, B-IPCON ID, etc.) is transmitted from the call agent on the B side to the call agent on the A side.
• An IP HANDSHAKE 207 is returned from the A side call agent and the B side call agent sends an IP call request to the B subscriber.
• the IP BEARER PATH SETUP 209 is set up.
• the B subscriber transmits an IP CONNECT signal 210 to the call agent on the B side.
• the B side call agent sends an IP CONNECT signal 211 to the A side call agent.
• the IP call connection is completed when the A side call agent sends an IP CONNECT signal 212 to the subscriber A.
• the TDM connection may be abandoned at this point and pure IP path communications allowed to proceed alone.
• the B side call agent sends a TDM RELEASE signal 213 to the B side switch.
• the B side switch sends an SS7 RELEASE signal 214 to the A side switch.
• the A side switch sends a TDM RELEASE signal 215 to the A side call agent.
• a first subscriber IP-subl 302 sets up a call flow to a second subscriber IP-sub2 312.
• a first IP connection IP- CON1 304 signals a switch 1 306 to connect through to a second switch 2 308 that signals a second IP connection IP- CON2 310.
• these elements establish an active IP call 312.
• a user-initiated call 314 invokes an offhook setup invite 316 from the IP subscriber 1 302 to the IP-Conl 304.
• Dependent on the subscriber type, ringback may be provided.
• a setup signal 318 is then provided from IP-CON1 to the Switch 1 306.
• a TDM callsetup 320 is sent from the switch 1 306 to the switch 2 308.
• a setup signal 322 is then sent from the switch 2 308 to the second IP-CON2 310.
• the IP-CON2 send an IP-CON2 info signal 324 to the IP-CON1 304.
• the TDM call up to the "call presented" ringing is established.
• the IP-CONs can decide to continue with the TDM or establish a pure IP path and switch the subscribers to IP communications.
• FIG. 4 depicts as an example suggested call flow 400 for call waiting.
• an IP subscriber 1 402 an IP-CON 1 404, switch 1 406, a switch 2 408, an IP-CON2 410 and an IP subscriber 2 412.
• the IP call is set up.
• the present invention re-establishes connection to the subscriber A TDM environment in order to allow an incoming TDM call service or call feature to be applied to the subscriber A. It must be remembered, however, that the solution is not so simple. If someone attempts to call subscriber A, the TDM switch will determine that the party A is idle and will try to deliver the call. Although subscriber A has the subscription, he will not receive anything. In fact, this will cause spurious error which are too ambiguous to comment on here. On the switch side, the call waiting tone is forwarded.
• the problem is how can TDM features be provided to such subscribers who are re-connected via the TDM connection but who are unavailable because they are actually in communication with an established IP connection.
• the solution provided here is to recognize that the set up can be toggled between the 2 calls (TDM / IP) . But in order to do this, the invention must provide some special mechanisms in order to arrange for TDM call services and features.
• the idea is to trigger TDM switching as soon as the call comes in for the A side party.
• a trigger which may be an advanced intelligent network (AIN) trigger, that is triggered as soon as a TDM call comes in.
• AIN advanced intelligent network
• the idea is that that the call is not handled in the TDM switch, but rather by the IP-side since the IP is handling the current call connection.
• the first thing the TDM switch does is send a query to a SCP (signalling control point) .
• SCP signal control point
• the concentrator to be the SCP for this case. This causes the TDM switch to forward the query to the IP controller, here the IP-concentrator.
• the IP- concentrator is the only element that knows the true status of the parties and, thus, is the device capable of handling the incoming call.
• the IP- concentrator sends a signal to the TDM switch that indicates to the TDM switch that the call may be established.
• the TDM switch proceeds to connect the incoming call to the A subscriber.
• the IP-concentrator creates the TDM call and sends to the TDM switch that should go ahead with services.
• Termination_Attempt are armed. In laymen's terms, this means that whenever a remote caller wants to terminate to this subscriber, i.e., connect, then the IP-concentrator is sent a set_up message. The Global translation resolves to point to the IP-concentrator. Thus, for an incoming call the trigger is triggered, and the TDM switch sends an IN-query to the IPCON. A TCAP dialog between the switch and the IP-CON, informs the IP-CON of an incoming call for an IP-CON subscriber. The TDM-switch is not aware of the real status of the IP-CON subscriber, but the IP-CON is aware of ongoing transactions and, thus, is capable of making the connection.
• the IP-CON initially determines whether its subscriber is involved in an IP-call. In this case, the IP-CON verifies which IP-CON (own or partner) originated the call. Next, the IP-CON informs the partner IP-CON of the need to reestablish the ongoing IP-call over TDM. As a next step the originator IP-CON reestablishes the TDM call. Finally, the IP-CON instructs the TDM switch is via TCAP message (CONTINUE ) instructed to resume the incoming call processing. On the other hand, when the IP-CON determines its subscriber is idle then the IP-CON sends a CONTINUE signal to the TDM switch to instruct the TDM switch to resume the incoming call processing.
• TCAP message CONTINUE
• IP-concentrator plays two roles. As concentrator of IP, the IP concentrator collects and bundles IP packets and decides when enough are accumulated in the buffer to be sent. Second, but also as scp) .
• any other type of call service may be implemented using the following technique. Initially, a new incoming call signal 414 for the subscriber 1 is initiated and sent to the switch 1 406. Then, a termination attempt 416 is sent from the switch 1 406 to the IP-CON1 404. Since the originator of the call should re-establish the TDM call, the IP-CONl 404 sends a setup signal 418 to the switch 1 406 and the switch 1 406 sends a TDM set up call signal 420 to the second switch 408.
• the switch 2 408 signals a termination attempt 422 to the IP CON 2 410 and the IP CON 2 410 signals its response to continue 424. In return, the switch 2 408 sends a setup signal 426 to the IP CON2 410. The basic call flow for TDM is continued until the TDM path is re-established.
• the next step is to provide for the call feature.
• the IP CON 1 signals a response continue signal 428 to the switch 1 406 and the switch 1 406 verifies the call waiting subscription.
• the switch 1 406 signals 430 the IP CON1 404 to set up a call waiting tone.
• the IP CONl 404 issues a signal 432 that causes the IP subscriber 1 to sound the call waiting tone.
• the first subscriber receives the call waiting tone and puts the first call on hold in order to receive the new call.
• Another way of resolving the problem is to use a pre-existing Call Forwarding feature that is, for example, provided by the TDM network. This may be applied according to the call flow processing already described above.
• an IP-CON establishes an IP call for one of its subscribers, that IP- CON activates Call Forwarding feature for that particular subscriber so that any incoming call for that subscriber gets forwarded to the IP-CON.
• the IP-CON can decide how to proceed with delivery of the new incoming call.
• the IP-CON should have knowledge of the subscriber service-subscription. Since the details of call forwarding are already known, the description here shall not elaborate on the inner workings of this know call feature service.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Telephonic Communication Services (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=34886265

Family Applications (1)

Country Status (3)

Family Cites Families (4)

• 2005
  • 2005-01-19 EP EP05707803A patent/EP1716719A2/de not_active Withdrawn
  • 2005-01-19 WO PCT/EP2005/050214 patent/WO2005081574A2/en not_active Application Discontinuation
  • 2005-01-19 CN CNA2005800053296A patent/CN1930906A/zh active Pending

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events