EP1797702A1 - Communications network - Google Patents

Communications network

Info

Publication number
EP1797702A1
EP1797702A1 EP05775942A EP05775942A EP1797702A1 EP 1797702 A1 EP1797702 A1 EP 1797702A1 EP 05775942 A EP05775942 A EP 05775942A EP 05775942 A EP05775942 A EP 05775942A EP 1797702 A1 EP1797702 A1 EP 1797702A1
Authority
EP
European Patent Office
Prior art keywords
processing means
control
access point
emergency
access
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
EP05775942A
Other languages
German (de)
French (fr)
Other versions
EP1797702B1 (en
Inventor
Karl Bittnar
Arno-Gert Fabritius
Viktor Karell
Klaus Kirchberger
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Unify GmbH and Co KG
Original Assignee
Siemens AG
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 Siemens AG filed Critical Siemens AG
Publication of EP1797702A1 publication Critical patent/EP1797702A1/en
Application granted granted Critical
Publication of EP1797702B1 publication Critical patent/EP1797702B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present invention relates to a communications network.
  • IP Internet Protocol
  • Telecommunication system 1 comprises a first Local Area Network (LAN) 2 located at a company's headquarters, a second LAN 3 located at a first branch office (not shown) , a third LAN 4 located at a second branch office (not shown) and a fourth LAN 5 located at a third branch office (not shown) .
  • the first LAN 2 is connected to a first router 6, the second LAN 3 to a second router 7 , the third LAN 4 to a third router 8 and the fourth LAN 5 to a fourth router 9.
  • These routers connect the LANs via a Wide Area Network (WAN) 10.
  • WAN Wide Area Network
  • a first access point 11 connects to the first Lan 2
  • a second access point 12 connects to the second LAN 3
  • a third access point 13 connects to the third LAN 4
  • fourth 14 and fifth 15 access points connect to the fourth LAN 5.
  • These access points 11 to 15 allow the connection of client terminals (not shown) to the LANs 2 to 5 and hence to the WAN 10.
  • the client terminals may either be traditional Time Divsion Multiplexed (TDM) devices, for example standard telephones or cordless telephones, or IP devices, for example IP telephones.
  • TDM Time Divsion Multiplexed
  • a central control system 16 connects to the first LAN 2 at the headquarters (not shown) and is responsible for controlling the operation of each of the access points 11 to 15.
  • Each of the access points 11 to 15 comprises a respective gateway card 11a to 15a and a plurality of peripheral cards lib to 15b.
  • the peripheral cards lib to 15b provide multiple peripheral ports for connection to client terminals, for example phones and/or trunk lines.
  • the gateway cards 11a to 15a are the controllers of the IP based Access Point.
  • Each of the cards 11a to 15a acts as a gateway between the LAN on one side of the card, and the client terminals on the other side of the card, converting payload data (e.g. voice data , fax data and ISDN-data) from TDM data to IP data and vice versa.
  • Each of the cards 11a to 15a provides a local TDM switching matrix, conference units and tone generators.
  • Each of the gateway cards 11a to 15a may be Siemens' HG 3575 cards.
  • the central control system 16 comprises a plurality of gateway cards 16a, a plurality of peripheral cards 16b, an administration and data processor 16c, a common control processor 16d and a back up common control processor 16e.
  • the plurality of peripheral cards 16b provide multiple peripheral ports for connection to client terminals, for example phones and/or trunk lines.
  • the gateways 16a translate payload data (voice/fax/ISDN-data) from TDM data on the client terminal side of the gateways to IP data on the LAN side of the gateways and vice versa. These gateways are used for connections between the IP based access points 11 to 15 and the central system 16.
  • These cards 16a may be Siemens' HG 3570 cards.
  • the Administration and Data Processor 16c runs administrative software and applications, whilst the common control processor 16d runs call processing software.
  • the back up common control processor 16e provides a back up to the common control processor 16d and in the event of the failure of the common control processor 16d, it can be switched into use without interrupting active calls.
  • the access points are controlled by the common control processor 16d. Every activity of the peripheral cards, for example, tones or displays at the phones and signaling messages at trunk interfaces are controlled by the common control processor 16d via a control link over the IP network. A complete set of administrative parameters in a database (not shown) in the central system 16 is kept in the memory of the control processor 16d. A persistent copy of the database is kept on hard disc which is controlled by the administration and data processor 16c.
  • a modem connection may be established between the central system 16 and some or all of the access points.
  • a connection between the central system 16 and the third access point 13, the fourth acess point 14 and the fifth access point ' 15 is made through the Public Switched Telephone Network (PSTN) 17 via a router 18 connected to the LAN 2 and a first modem 19 connected to the gateway
  • PSTN Public Switched Telephone Network
  • Embodiments of the present invention aim to alleviate the above described problems.
  • a distributed packet based communications network comprising: a central control system comprising control processing means; at least one access point remote from the central control system, the at least one access point for providing access to the packet based communications network, wherein under normal operating conditions the at least one access point is controlled by the control processing means; and emergency processing means distinct from the central control system for controlling the at least one access point when there is a failure in the control processing means control of the at least one access point.
  • FIG. 1 illustrates a communication system and has already been described
  • FIG. 2 illustrates a communication system and has already been described
  • FIG. 3 illustrates a communications system embodying the present invention.
  • a communications system 100 embodies the present invetion.
  • the communications system 100 functions identically to the system 1 illustrated in Figure 1. That is to say, the four access points 11 to 15 are all operated under the central control of the central system 16.
  • the system 100 is provided with an emergency de-centralised control system for controlling access points in the event of the failure of the IP network linking access points and the central system 16 or if the central system 16 is not actually available.
  • the first access point 11, the third access point 13 and the fourth access point 14 are provided with their own emergency control processors labelled lie, 13c and 14c respectively.
  • Each of the emergency control processors lie, 13c and 14c offer the same functionality as the central control. They possess the same software, the same patch status (i.e.software corrections applied to the system while running) and identical configuration data as do the administration and data processor 16c and the common control processor 16d of the central system 16.
  • Groups of access points are assigned to emergency control groups, each emergency control group comprising one of the emergency control processors lie, 13c and 14c.
  • the first access point 11 and the second access point 12 makeup a first emergency control group
  • the third access point 13 makes up a second emergency control group
  • the fourth access point 14 and fifth access point 15 make up a third emergency control group.
  • Each of the emergency control processors lie, 13c and 14c is in contact with the the gateway cards in its respective emergency group. Thus, if an access point of an emergency group loses contact with the central system the emergency processor of that group may take control of the access point.
  • a mechanism is provided for keeping the software status and the configuration data of the emergency control processors identical to that of the central system 16.
  • a backup server 22 is connected to the WAN 10, and in order to save on transmission bandwidth the software the software and database of the central system 16 is transmitted periodically, for example each day, to the backup server 22.
  • This backup server 22 is as a general rule a separate device from the central system 16 and the emergency control processors lie, 13c and 14c.
  • the central system 16 and all the emergency control processors lie, 13c and 14c have access via the IP network 10 to the backup server 22.
  • the emergency control processors lie, 13c and 14c check cyclically whether updated data is present on the server 22 and download it where necessary.
  • each emergency control processor maintains an identical database to that at the central control .
  • the emergency control processors lie, 13c and 14c can thus behave in exactly the same way as the central system processors .
  • a fault occurs when an access point can no longer be served by the central control 16. If an access point gateway card detects a problem with the signalling connection between the access point of that card and the central system 16, it reports that fact to the emergency processor of the emergency group to which the access point belongs.
  • the emergency processor decides according to preconfigured rules whether to take over control of the access point or not.
  • each access point in an emergency group is assigned a weight value of between zero and one, and when the total weight value of all access points in the emergegency group that have lost connection with the central system 16 equals or exceeds a predefined threshold, the emergency processor of the group takes over controll of those access points.
  • an emergency group comprising three access points each having a weight value of 0.5 and wherein the threshold is 1, it is only when at least two access points have reported a central system connection failure that the emergency processor steps in and assumes control of those access points.
  • an individual access point of particular importance for example an access point serving the telephones of senior managers, may be assigned a weight value equal to the threshold value so that if this access point loses connection with the central system, an emergency processor immediately asssumes control of it.
  • the access points in an emergency group may be configured to be taken over individually by the group's emergency processor as and when an access point loses contact with the central system 16.
  • the access points may be configured so that an immediate hand over to an emergency processor may be ordered by the system administrator.
  • the emergency processor instructs the gateway card of the access point to restart and to start up with the emergency processor.
  • the access point remains under the control of the emergency processor but notifies it that it has re ⁇ established contact with the central system 16.
  • the emergency processor decides in accordance with pre-defined rules whether and when emergency operation can be ended.
  • emergency control may be ended only if every access point in an emergency group has had a stable connection with the central system 16 for a configurable pre-determined time period.
  • Emergency control may only be ended at configurable pre-defined times of the day.
  • the system may be configured so that a system administrator may order the end of emergency control .
  • the emergency control processor instructs the gateway card of the access point to do a restart and to start up under the control of the central system 16.

Landscapes

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

Abstract

A distributed Internet Protocol (IP) communications network comprises a central control system comprising control processing means and at least one access point remote from the central control system for providing access to the packet based communications network. Under normal operating conditions the at least one access point is controlled by the control processing means. The network also comprises an emergency processing means distinct from the central control system for contolling the least one access point when there is a failure in the control processing means control of the at least one access point.

Description

Communications Network
The present invention relates to a communications network.
In the past, large companies having a corporate headquarters and multiple branch offices have tended to operate independent self-contained telecommunication systems at each of the branches and at the headquarters. Naturally, these independent systems would be networked together. The administrative effort and the costs involved in running such multiple independent systems was high.
More recently, by using Internet Protocol (IP) internetworking between the headquarters and the various branches, it has been possible to relocate parts of the headquarters central system into the branches, whilst retaining a single point of control at the headquarters.
Systems based on the HiPath 4000 IP Distributed
Architecture, provided by Siemens AG, are examples of such IP internetworked systems. An example of a HiPath 4000 IP Distributed Architecture system is shown schematically in Figure 1.
Telecommunication system 1 comprises a first Local Area Network (LAN) 2 located at a company's headquarters, a second LAN 3 located at a first branch office (not shown) , a third LAN 4 located at a second branch office (not shown) and a fourth LAN 5 located at a third branch office (not shown) . The first LAN 2 is connected to a first router 6, the second LAN 3 to a second router 7 , the third LAN 4 to a third router 8 and the fourth LAN 5 to a fourth router 9. These routers connect the LANs via a Wide Area Network (WAN) 10.
A first access point 11 connects to the first Lan 2, a second access point 12 connects to the second LAN 3, a third access point 13 connects to the third LAN 4 and fourth 14 and fifth 15 access points connect to the fourth LAN 5. These access points 11 to 15 allow the connection of client terminals (not shown) to the LANs 2 to 5 and hence to the WAN 10. In a typical HiPath 4000 system the client terminals may either be traditional Time Divsion Multiplexed (TDM) devices, for example standard telephones or cordless telephones, or IP devices, for example IP telephones.
A central control system 16 connects to the first LAN 2 at the headquarters (not shown) and is responsible for controlling the operation of each of the access points 11 to 15. Each of the access points 11 to 15 comprises a respective gateway card 11a to 15a and a plurality of peripheral cards lib to 15b. The peripheral cards lib to 15b provide multiple peripheral ports for connection to client terminals, for example phones and/or trunk lines. The gateway cards 11a to 15a are the controllers of the IP based Access Point. Each of the cards 11a to 15a acts as a gateway between the LAN on one side of the card, and the client terminals on the other side of the card, converting payload data (e.g. voice data , fax data and ISDN-data) from TDM data to IP data and vice versa. Each of the cards 11a to 15a provides a local TDM switching matrix, conference units and tone generators. Each of the gateway cards 11a to 15a may be Siemens' HG 3575 cards.
The central control system 16 comprises a plurality of gateway cards 16a, a plurality of peripheral cards 16b, an administration and data processor 16c, a common control processor 16d and a back up common control processor 16e.
Again, the plurality of peripheral cards 16b provide multiple peripheral ports for connection to client terminals, for example phones and/or trunk lines. The gateways 16a translate payload data (voice/fax/ISDN-data) from TDM data on the client terminal side of the gateways to IP data on the LAN side of the gateways and vice versa. These gateways are used for connections between the IP based access points 11 to 15 and the central system 16. These cards 16a may be Siemens' HG 3570 cards.
The Administration and Data Processor 16c runs administrative software and applications, whilst the common control processor 16d runs call processing software. The back up common control processor 16e provides a back up to the common control processor 16d and in the event of the failure of the common control processor 16d, it can be switched into use without interrupting active calls.
The access points are controlled by the common control processor 16d. Every activity of the peripheral cards, for example, tones or displays at the phones and signaling messages at trunk interfaces are controlled by the common control processor 16d via a control link over the IP network. A complete set of administrative parameters in a database (not shown) in the central system 16 is kept in the memory of the control processor 16d. A persistent copy of the database is kept on hard disc which is controlled by the administration and data processor 16c.
Such systems have reduced administrative outlay but an increased dependence on the availability of the network and of the central system. If the central control fails, no further telecommunication is possible - in the corporate HQ or in the branches. A very high availability of the central control is achieved by duplicating the control processors.
As illustrated in Figure 2, in order to maintain control of access points upon failure of the WAN 10, a modem connection may be established between the central system 16 and some or all of the access points. In figure 2, a connection between the central system 16 and the third access point 13, the fourth acess point 14 and the fifth access point' 15 is made through the Public Switched Telephone Network (PSTN) 17 via a router 18 connected to the LAN 2 and a first modem 19 connected to the gateway
13a, a second modem 20 connected to the gateway 14a and a third modem 21 connected to the gateway 15a. Access points without modem connections, in this example, the second access point 12, go out of service when their WAN connections fail. However, even back up systems such as this are useless in the event of total failure of the central system brought on by a catastrophy such as flooding or destruction of the building.
Embodiments of the present invention aim to alleviate the above described problems. According to the present invention there is provided a distributed packet based communications network comprising: a central control system comprising control processing means; at least one access point remote from the central control system, the at least one access point for providing access to the packet based communications network, wherein under normal operating conditions the at least one access point is controlled by the control processing means; and emergency processing means distinct from the central control system for controlling the at least one access point when there is a failure in the control processing means control of the at least one access point.
The above and further features of the invention are set forth with particularity in the appended claims and together with advantages thereof will become clearer from consideration of the following detailed description of an exemplary embodiment of the invention given with reference to the accompanying drawings, in which:
Figure 1 illustrates a communication system and has already been described;
Figure 2 illustrates a communication system and has already been described;
Figure 3 illustrates a communications system embodying the present invention.
Referring now to Figure 3 of the drawings, in which identical features as those illustrated in Figure 1 are given like reference numerals, a communications system 100 embodies the present invetion.
Under normal operating conditions the communications system 100 functions identically to the system 1 illustrated in Figure 1. That is to say, the four access points 11 to 15 are all operated under the central control of the central system 16.
The system 100 is provided with an emergency de-centralised control system for controlling access points in the event of the failure of the IP network linking access points and the central system 16 or if the central system 16 is not actually available. To this end, the first access point 11, the third access point 13 and the fourth access point 14 are provided with their own emergency control processors labelled lie, 13c and 14c respectively.
Each of the emergency control processors lie, 13c and 14c offer the same functionality as the central control. They possess the same software, the same patch status (i.e.software corrections applied to the system while running) and identical configuration data as do the administration and data processor 16c and the common control processor 16d of the central system 16. Groups of access points are assigned to emergency control groups, each emergency control group comprising one of the emergency control processors lie, 13c and 14c. In the system 100, the first access point 11 and the second access point 12 makeup a first emergency control group, the third access point 13 makes up a second emergency control group and, the fourth access point 14 and fifth access point 15 make up a third emergency control group. Each of the emergency control processors lie, 13c and 14c is in contact with the the gateway cards in its respective emergency group. Thus, if an access point of an emergency group loses contact with the central system the emergency processor of that group may take control of the access point.
A mechanism is provided for keeping the software status and the configuration data of the emergency control processors identical to that of the central system 16.
A backup server 22 is connected to the WAN 10, and in order to save on transmission bandwidth the software the software and database of the central system 16 is transmitted periodically, for example each day, to the backup server 22. This backup server 22 is as a general rule a separate device from the central system 16 and the emergency control processors lie, 13c and 14c. The central system 16 and all the emergency control processors lie, 13c and 14c have access via the IP network 10 to the backup server 22. The emergency control processors lie, 13c and 14c check cyclically whether updated data is present on the server 22 and download it where necessary. Thus each emergency control processor maintains an identical database to that at the central control . In an emergency the emergency control processors lie, 13c and 14c can thus behave in exactly the same way as the central system processors .
A fault occurs when an access point can no longer be served by the central control 16. If an access point gateway card detects a problem with the signalling connection between the access point of that card and the central system 16, it reports that fact to the emergency processor of the emergency group to which the access point belongs. The emergency processor decides according to preconfigured rules whether to take over control of the access point or not. In one embodiment, each access point in an emergency group is assigned a weight value of between zero and one, and when the total weight value of all access points in the emergegency group that have lost connection with the central system 16 equals or exceeds a predefined threshold, the emergency processor of the group takes over controll of those access points. So for example, in an emergency group comprising three access points each having a weight value of 0.5 and wherein the threshold is 1, it is only when at least two access points have reported a central system connection failure that the emergency processor steps in and assumes control of those access points. Naturally, an individual access point of particular importance, for example an access point serving the telephones of senior managers, may be assigned a weight value equal to the threshold value so that if this access point loses connection with the central system, an emergency processor immediately asssumes control of it.
In alternative embodiment, the access points in an emergency group may be configured to be taken over individually by the group's emergency processor as and when an access point loses contact with the central system 16.
Naturally, the access points may be configured so that an immediate hand over to an emergency processor may be ordered by the system administrator.
In a preferred embodiment, to take over control of an access point, the emergency processor instructs the gateway card of the access point to restart and to start up with the emergency processor.
If the central system 16 succedes in re-establishing a control connection to an Access Point in emergency operation, the access point remains under the control of the emergency processor but notifies it that it has re¬ established contact with the central system 16. The emergency processor decides in accordance with pre-defined rules whether and when emergency operation can be ended.
For example, emergency control may be ended only if every access point in an emergency group has had a stable connection with the central system 16 for a configurable pre-determined time period. Emergency control may only be ended at configurable pre-defined times of the day. The system may be configured so that a system administrator may order the end of emergency control .
To end emergency control of an access point, the emergency control processor instructs the gateway card of the access point to do a restart and to start up under the control of the central system 16.
Having thus described the present invention by reference to preferred embodiments it is to be well understood that the embodiments in question are exemplary only and that modifications and variations such as will occur to those possessed of appropriate knowledge and skills may be made without departure from the scope of the invention as set forth in the appended claims.

Claims

1. A distributed packet based communications network comprising: a central control system comprising control processing means; at least one access point remote from the central control system, the at least one access point for providing access to the packet based communications network, wherein under normal operating conditions the at least one access point is controlled by the control processing means; and emergency processing means distinct from the central control system for controlling the least one access point when there is a failure in the control processing means control of the at least one access point.
2. A system according to claim 1 comprising means for providing the emergency processing means with the same functionality as the control processing means.
3. A system according to claim 2 further comprising a server to which data from the central control system is uploaded for downloading to the emergency processing means for the emergency processing means to maintain the same functionality as the control processing means.
4. A system according to any preceding claim wherein upon detection of a failure in the control processing means control of the at least one access point, the emergency control processor determines whether to take control of the at least one access point in dependence upon predetermined rules.
5. A system according to any preceding claim wherein the at least one access point provides TDM user terminals access to the packet based communications network.
6. A system according to any preceding claim comprising a plurality of access points, which access points form a group of access points and wherein the emergency processing means is for controlling any of the access points in the group when there is a failure in the control processing means control of any of the access points in the group.
7. A system according to any preceding claim comprising a plurality of groups of access points, each group comprising one or more access points and an emergency processing means for controlling any of the one or more access points when there is a failure in the control processing means control of the any of the one or more access points.
8. A processing means arranged for use as an emergency processing means in the system of any of claims 1 to 7.
9. An access point comprising the processing means of claim 8 for use in the system of any of claims 1 to 7.
EP05775942.5A 2004-10-05 2005-08-18 Communications network Active EP1797702B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0422005A GB2419059A (en) 2004-10-05 2004-10-05 Communications network
PCT/EP2005/008943 WO2006037400A1 (en) 2004-10-05 2005-08-18 Communications network

Publications (2)

Publication Number Publication Date
EP1797702A1 true EP1797702A1 (en) 2007-06-20
EP1797702B1 EP1797702B1 (en) 2018-10-24

Family

ID=33428036

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05775942.5A Active EP1797702B1 (en) 2004-10-05 2005-08-18 Communications network

Country Status (5)

Country Link
US (1) US8339937B2 (en)
EP (1) EP1797702B1 (en)
CN (1) CN101036377B (en)
GB (1) GB2419059A (en)
WO (1) WO2006037400A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070183417A1 (en) * 2006-02-09 2007-08-09 Maleport Joel J Data traffic router
US20100110877A1 (en) * 2008-10-30 2010-05-06 Symbol Technologies, Inc. System and method for failover of mobile units in a wireless network
BR112012030595B1 (en) 2010-06-02 2020-02-04 Koninl Philips Electronics Nv method for controlling a lighting system and lighting system
JP5812915B2 (en) * 2012-03-28 2015-11-17 京セラ株式会社 Mobile terminal, data management method and data management program
CN104094577B (en) 2012-08-13 2017-07-04 统一有限责任两合公司 Method and apparatus for evaluating the state of mobile body indirectly

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5528595A (en) * 1974-06-09 1996-06-18 U.S. Robotics, Inc. Modem input/output signal processing techniques
US5559800A (en) * 1994-01-19 1996-09-24 Research In Motion Limited Remote control of gateway functions in a wireless data communication network
US6424700B1 (en) * 1999-12-09 2002-07-23 Nortel Networks Corporation Network based distributed PBX with connection loss survival features
US7039046B1 (en) * 2000-05-20 2006-05-02 Ciena Corporation Network device including central and distributed switch fabric subsystems
JP4516707B2 (en) * 2001-07-10 2010-08-04 株式会社エヌ・ティ・ティ・ドコモ Network control apparatus, mobile communication system, and mobile communication network control method
US20030035414A1 (en) * 2001-08-20 2003-02-20 Siemens Information System and method for mixed mode public and private gatekeeper system
US7257629B2 (en) * 2001-09-27 2007-08-14 Siemens Communications, Inc. Method and apparatus for providing back-up capability in a communication system
US7023794B2 (en) * 2002-02-11 2006-04-04 Net2Phone, Inc. Method and architecture for redundant SS7 deployment in a voice over IP environment
US7206306B2 (en) * 2002-03-26 2007-04-17 Siemens Communications, Inc. System and method for emergency call diversion
US7197664B2 (en) * 2002-10-28 2007-03-27 Intel Corporation Stateless redundancy in a network device
US7340247B1 (en) * 2003-05-29 2008-03-04 Airespace, Inc. Wireless network infrastructure including wireless discovery and communication mechanism

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US8339937B2 (en) 2012-12-25
GB2419059A (en) 2006-04-12
CN101036377B (en) 2015-09-16
GB0422005D0 (en) 2004-11-03
CN101036377A (en) 2007-09-12
EP1797702B1 (en) 2018-10-24
WO2006037400A1 (en) 2006-04-13
US20080304478A1 (en) 2008-12-11

Similar Documents

Publication Publication Date Title
US6304566B1 (en) Telecommunication system
US6292482B2 (en) Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses
US7027435B2 (en) Method and device for call diversion via an agent in a communications system
US7184430B2 (en) Telecommunication system
US20060083182A1 (en) Capability management for automatic dialing of video and audio point to point/multipoint or cascaded multipoint calls
EP1791298B1 (en) A system and method for processing the link fault of the broad band access device
WO1997039561A1 (en) Multimedia switching apparatus
CN103430524A (en) A backup sip server for the survivability of an enterprise network using sip
EP1797702B1 (en) Communications network
US7310308B2 (en) Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses
US7630294B2 (en) Method and communication arrangement for alternately operating a terminal at at least two communication nodes
US6424700B1 (en) Network based distributed PBX with connection loss survival features
US7463731B2 (en) Apparatus and method for dual mode phone
AU733799B2 (en) Incoming call routing
US6181696B1 (en) Method and apparatus for controlling network switches
JP2000349901A (en) Internet protocol network bypass system
WO2002058352A9 (en) Simultaneous, transparent use of a telephone line for voice and data communications
KR100438071B1 (en) Method of send call route re-setting for VoIP gateway with internet network trouble
JP2606072B2 (en) Call control method
WO1999000954A1 (en) Telecommunication system
WO1999000952A1 (en) Telecommunication system
US20050108410A1 (en) Distribution of load to peripheral facilities of a packet-based switching system
JP3784172B2 (en) Dealing call system
CN117336196A (en) Method and system for supporting SDWAN networking by IPPBX
de Mello et al. Satellite VoIP access gateway

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20070302

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE FR GB IT SE

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE FR GB IT SE

17Q First examination report despatched

Effective date: 20080514

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SIEMENS ENTERPRISE COMMUNICATIONS GMBH & CO. KG

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: UNIFY GMBH & CO. KG

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: UNIFY GMBH & CO. KG

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/14 20060101ALI20180420BHEP

Ipc: H04M 3/42 20060101AFI20180420BHEP

INTG Intention to grant announced

Effective date: 20180515

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB IT SE

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602005054852

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181024

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602005054852

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181024

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20190725

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602005054852

Country of ref document: DE

Representative=s name: SCHAAFHAUSEN PATENTANWAELTE PARTNERSCHAFTSGESE, DE

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240627

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240611

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240625

Year of fee payment: 20