EP1482745A2 - Verfahren und Anordnung zur Anmeldung eines Endgerätes an einem Kommunikationsknoten - Google Patents
Verfahren und Anordnung zur Anmeldung eines Endgerätes an einem Kommunikationsknoten Download PDFInfo
- Publication number
- EP1482745A2 EP1482745A2 EP04010494A EP04010494A EP1482745A2 EP 1482745 A2 EP1482745 A2 EP 1482745A2 EP 04010494 A EP04010494 A EP 04010494A EP 04010494 A EP04010494 A EP 04010494A EP 1482745 A2 EP1482745 A2 EP 1482745A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- terminal
- communication
- communication node
- access parameters
- nodes
- 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
Links
- 238000004891 communication Methods 0.000 title claims abstract description 191
- 238000000034 method Methods 0.000 title claims abstract description 49
- 230000005540 biological transmission Effects 0.000 claims description 6
- 230000006870 function Effects 0.000 claims description 6
- 238000013475 authorization Methods 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000003292 diminished effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000006163 transport media Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/42—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker
- H04Q3/54—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised
- H04Q3/545—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised using a stored programme
- H04Q3/54508—Configuration, initialisation
- H04Q3/54516—Initialization, software or data downloading
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
-
- 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
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
- H04Q3/0033—Provisions for intelligent networking customer-controlled
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/04—Special services or facilities for emergency applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/06—Lines and connections with preferential service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/38—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
-
- 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/13103—Memory
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13109—Initializing, personal profile
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13167—Redundant apparatus
-
- 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/13389—LAN, internet
Definitions
- the invention relates to a method for registering a terminal at a communication node and an arrangement for Execution of the procedure.
- each terminal In communication networks are usually a variety of Terminals and multiple communication nodes arranged.
- circuit-switched communication arrangements for example in ISDN systems, each terminal is in each case at one Communication node (switching device) permanently logged and thus firmly assigned. This assignment is included given by the wiring, so that a terminal device, for example a telephone or fax machine, just like that Switching device is registered, with this Terminal is also physically connected.
- cordless Terminals are each at a particular communication node logged in, even if at times as a "guest" other Use communication nodes; this procedure is also called Known as "roaming".
- the terminals in voice data networks are one of the communication nodes in the respective Speech data network permanently assigned and registered with this.
- a voice data network can in principle be any network component, So every terminal and every communication node, with any other network component data (in particular Exchange voice data).
- the Terminals in voice data networks are often called "clients" referred to, because these terminals are significantly different from different circuit-switched terminals. So you can for example as a telephone with network connection or also as a computer with a communication software installed on it be designed.
- the object of the invention is to propose a method with the effort to configure a communication network diminished, and to propose an arrangement in the assignment of terminals to communication nodes associated with little manual effort.
- the object is for the method by the features of the claim 1 and for the arrangement by the features of Patent claim 15 solved.
- the solution provides for the procedure that first the registry the communication node and its access parameters takes place in an information store. Thereafter, an access takes place of the terminal on the information store and in the Follow the transmission of the access parameters of at least one the communication node to the terminal. After all the terminal is added based on the received access parameters logged in one of these communication nodes.
- the solution provides for the arrangement that in the communication network an information store is located in the communication node with the respective access parameters are registered.
- the terminal comprises means for access to the information store, with the access parameters suitable communication node through the terminal the information store are retrievable, and wherein the Terminal at one of the appropriate communication nodes based the access parameter logs.
- the method is characterized by the characterizing features of the dependent Claims 2 to 14 advantageously designed.
- the advantages described for the method apply mutatis mutandis, for the arrangement.
- the communication network is a voice data network and used as a communication node gatekeeper
- the procedure can be used for the common VoIP networks be used. This is especially true for the VoIP networks according to the H.323 and the SIP standard, where in the latter the gatekeepers also as “proxies” or “SIP proxies” be designated.
- the procedure can also be used for other VoIP standards over functional equivalents to gatekeepers and proxies.
- a voice data terminal or one with a Telephony feature equipped computer can be the well-known and common devices from VoIP networks easily the communication node assign.
- Step a) From the set of all registered communication nodes can from the information store the access parameters of the appropriate Communication nodes are filtered out by in Step a) as access parameter information about that of the respective Communication nodes support communication protocols and / or details of the number of each in total logged on terminals are registered.
- Step b) when accessing a request profile of the terminal to the information store, and in step c) from the information store to the terminal the access parameters such communication nodes are transmitted, which correspond to the requirement profile.
- the transmitted access parameters are in the terminal for additional logons are available if the in step c) transmitted access parameters stored by the terminal become.
- step d) If in step d) the registration of the terminal by the Terminal itself is done, is unnecessary in the communication network the operation of a separate login instance.
- step c) the access parameters of several communication nodes are transmitted to the terminal, and by in step d) in cases where the application of the Terminal at the first of these communication nodes not was successful, as long as further communication nodes, whose access parameters were stored in step c) are repeated until either a successful registration has taken place has, or all with access parameters from the terminal stored communication nodes are processed.
- Procedure beginning with step b) is repeated in the meantime the communication network added communication nodes or those where again capacities have been released, found by the terminal and to log on used.
- This registration is advantageously automatic, without manual intervention by a user or administrator.
- a service In such communication networks, in which the automatic Registration of the terminals at communication nodes not is desired, the assignment of the terminals to the communication node through a dedicated instance, a service. This will be in one Memory area of the information store Information about stored several terminals of the communication network.
- the service becomes the one based on the one in step a) in the information store registered communication nodes and based the information stored in the memory area about the Terminals the respective assignment of the terminals to the communication node performed.
- the registration of the terminals in step d) then takes place in each case at the associated preferred communication node.
- Step e) The failure of the communication node to which the terminal logged in can be collected by adding an additional Step e) is added.
- This Process step e) provides that the registration of the terminal at another of those communication nodes whose Access parameters were transmitted in step c) takes place, if the communication node to which the terminal is logged is, fails.
- the function of a terminal for example, permissions, can by logging in a user at the communication node, on which the terminal is registered, controlled become.
- step d) is then in the application of the terminal additionally the user of this terminal logged in at the communication nodes.
- a Standard user with a standard authorization to the communication node is notifiable, and by the terminal with logged on to the default node at the communication node is, as long as no other user on this terminal the communication node is logged, is the terminal always with the scope of use, for the standard user is defined, usable.
- This standard scope of use includes at least the emergency call function.
- the single figure shows a schematic representation a communication network with a data network, two communication nodes, two terminals and one information store.
- FIG. 1 shows a communication network in which as components communication nodes KN1, KN2, terminals EG1, EG2 and an information memory DB are arranged. These Components communicate with each other using a Data network LAN.
- the data network LAN is a so-called IP network, So a network in which components using the Internet Protocol (IP) packet-switched data, in particular Voice data, exchange.
- IP Internet Protocol
- the data network LAN instead of the data network LAN also other transport media for the data be used.
- the communication nodes KN1, KN2 become H.323 gatekeepers used, each for a number H.323-supporting Terminals EG1, EG2 form the login instance and, in addition, perform other functions to which the Frame of this embodiment is not discussed further shall be.
- H.323 gatekeeper can - at use SIP protocol or other communication protocols - SIP proxies or functionally identical communication nodes used become.
- the terminals EG1, EG2 are VoIP telephones, that is to say, telephony terminals which are used in voice data networks are formed.
- telephony terminals trained clients also computer (PC's) with a telephony software (so-called "soft phones") or other communication devices with a voice data interface used.
- PC's computer
- soft phones telephony software
- the terminal EG1 is considered as an example in the following.
- the information store DB is a database, on the the components of the communication network can access.
- the information storage DB in the Fig. 1 is shown as a separate device, the functionality of the information storage DB also from other network components be taken over.
- the information store DB is a so-called distributed information memory DB acts, so to a database whose components are on different network components are distributed.
- the information storage DB is used primarily for storage of data used to register the communication nodes KN1, KN2 serve, and thus the storage of this Communication node KN1, KN2 associated access parameters.
- the information store DB also stored other information become; this capability of the information memory DB is added a later described further embodiment of the invention used.
- the communication nodes KN1, KN2 register with their Access parameters after switching on ("run-up") in the Information memory DB.
- To the access parameters of the communication nodes KN1, KN2 belongs in each case to the network address the communication node KN1, KN2 in the data network LAN, the the communication node KN1, KN2 after each time it is turned on was assigned. This assignment can be static or done dynamically. Here she becomes dynamic the DHCP (Dynamic Host Configuration Protocol) method performed; this method is well known and will not be further elaborated here.
- To the transferred Access parameters still include the information about how many terminals at each communication node KN1, KN2 can be registered and how many Terminals at the current utilization of the communication nodes KN1, KN2 can still be registered to each of these.
- the latter information about the number of remaining ones Login capacity will of course change after each Registration or deregistration of a terminal EG1, EG2. Therefore this information is received from the communication nodes KN1, KN2 in periodically again to the information store DB transmitted.
- the interval is for this Transmissions are chosen so that they take place when the remaining in the respective communication node KN1, KN2 Remaining capacity around a certain threshold (in this Example is the threshold value 10) compared to the last one Message has changed.
- a certain threshold in this Example is the threshold value 10
- others can Intervals, especially time intervals selected become.
- Incidentally can also be completely based on the information about the total capacity and the remaining capacity of the communication nodes KN1, KN2 are omitted, because - as in this example - If there is insufficient residual capacity, the application a terminal EG1, EG2 from the respective communication node KN1, KN2 is denied and consequently the affected terminal EG1, EG2 a logon attempt on a another of the communication node KN1, KN2 makes.
- the terminal EG1 builds a Connection to the information store DB. That's it Terminal equipped with a control unit that comes with a Interface over the data network to a user interface of the information memory DB accesses.
- the terminal EG1 thereby a requirement profile, which the minimum requirements for one of the required communication nodes KN1, KN2 describes.
- This requirement profile includes, for example, information about the required Communication protocols (voice codecs), minimum number of administrable communication connections etc.
- This address can be found in the network components be stored by an administrator; in the present Case, however, it is the address of the information store DB when switching on the terminals EG1, EG2 or the communication node KN1, KN2 this by means of additional information of the DHCP method is transmitted.
- step a) of the communication node KN1, KN2 to the information memory DB transmitted access parameters in each case the requirements of the requirement profile satisfy which of the terminal EG1 to the information store DB in step b) has been transmitted. Consequently the information memory DB transmits in method step c) to the terminal EG1 the access parameters of both suitable Communication node KN1, KN2.
- the terminal EG1 now announces itself at the communication node KN1 on; this process is shown in FIG. 1 on the basis of d) marked arrow shown schematically.
- the control unit of the terminal EG1 with a Software equipped to log in according to one in the Data network agreed protocol; one speaks in this regard also from an implemented "protocol stack".
- step d) the registration of the terminal EG1 in the Communication node KN1 fails because, for example, the Communication node KN1 in the meantime its capacity limit has reached or failed, the terminal is building EG1 connects to another communication node, whose access parameters are transmitted from the information memory DB have been on to look at this alternative communication node to register.
- this is the communication node KN2.
- This evasive method is but only possible if - as in the present case - in Method step c) of the terminal EG1 not only the access parameters of the communication node KN1, but also those of the communication node KN2 have been stored.
- the login attempts will be continued until either a successful login to one of the communication nodes KN1, KN2 has taken place, or until all Communication node KN1, KN2 whose access parameters in process step c) have been processed.
- the terminal EG1 reconnects to the access parameters to the information store DB on again or to transfer the requirement profile and a list of Access parameters of suitable communication nodes KN1, KN2 retrieve. This happens because in the meantime, after the last time retrieval of access parameters, for example another communication node, not shown here, may have been added to the communication network, or other changes in the structure of the communication network may have occurred.
- the sum of all the access parameters in the information store DB registered communication node KN1, KN2 can as a first amount of information will be considered below PBX set is called.
- Analogous to the PBX set can in the information storage DB also has a second amount of information stored, which is called EP set in the following.
- the mapping service can be the assignment of terminals EG1, EG2 to communication nodes KN1, KN2 according to different Control aspects, for example, with the aim of a uniform utilization of the communication nodes KN1, KN2, or with the goal of being the least expensive communication node KN1, KN2 prefers to use etc.
- this assignment determines the association service for each of the terminals EG1, EG2 a preferred communication node KN1, KN2. in the It is assumed below that the communication node KN1 the preferred communication node for the terminal EG1 is.
- the association service now transmits to the terminal EG1 the Access parameters of the preferred communication node KN1, whereupon the terminal EG1 at the communication node KN1 logs on.
- the mapping service can do the Terminal EG1 also register itself at the communication node KN1 and transmit to the terminal EG1 information about that it is now registered at the communication node KN1 is.
- EG1 notify themselves at the communication nodes KN1, KN2, but also the users of the terminals EG1, EG2.
- Reason for this is, for example, the allocation of different permissions to different users, For example, only selected users are paid May use external communication links. From a terminal EG1, which at the communication node KN1 is logged in, so for example, only external Telephone calls are made when a user is using the right to make external phone calls the terminal EG1 logged on to the communication node KN1 is.
- the terminal EG1 logs in process step d) as described above first to then in the same process step a so-called.
- "Standard user” at to register the communication node KN1.
- This "standard user” is at least the authorization allocated emergency calls respectively. If at a later date a user with a different authorization over the terminal EG1 at the communication node KN1 logs, instead of the Standard user of this "regular" user in the communication node KN1 linked to the terminal EG1, so that the terminal EG1 attains its full functionality. reports at a later time the "regular" User via the terminal EG1 from the communication node KN1, the terminal EG1 becomes the default user again assigned.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
Claims (15)
- Verfahren zur Anmeldung eines Endgerätes (EG1, EG2) an einem Kommunikationsknoten (KN1, KN2) in einem Kommunikationsnetzwerk,
wobei in dem Kommunikationsnetzwerk mehrere Kommunikationsknoten (KN1, KN2) angeordnet sind,
gekennzeichnet durch
folgende Verfahrensschritte:a) Registrierung der Kommunikationsknoten (KN1, KN2) und deren Zugangsparameter in einem Informationsspeicher (DB),b) Zugriff des Endgerätes (EG1, EG2) auf den Informationsspeicher (DB),c) Übermittlung der Zugangsparameter zumindest eines der Kommunikationsknoten (KN1, KN2) zu dem Endgerät (EG1, EG2), undd) Anmeldung des Endgerätes (EG1, EG2) anhand der erhaltenen Zugangsparameter bei einem dieser Kommunikationsknoten (KN1, KN2). - Verfahren nach Patentanspruch 1,
dadurch gekennzeichnet, dass als das Kommunikationsnetzwerk ein Sprach-Datennetzwerk verwendet wird, und
dass als Kommunikationsknoten (KN1, KN2) jeweils Gatekeeper benutzt werden. - Verfahren nach Patentanspruch 2,
dadurch gekennzeichnet, dass als das Endgerät (EG1, EG2) ein Sprachdaten-Endgerät oder ein mit einer Telephonie-Funktion ausgestatteter Computer verwendet wird. - Verfahren nach einem der vorhergehenden Patentansprüche,
dadurch gekennzeichnet, dass in Schritt a) als die Zugangsparameter Angaben über die von dem jeweiligen Kommunikationsknoten (KN1, KN2) unterstützten Kommunikationsprotokolle und / oder Angaben über die Anzahl der jeweils insgesamt anmeldbaren Endgeräte (EG1, EG2) registriert werden. - Verfahren nach einem der vorhergehenden Patentansprüche,
dadurch gekennzeichnet, dass in Schritt a) die Zugangsparameter Angaben über die Anzahl der aktuell anmeldbaren Endgeräte (EG1, EG2) umfasst, und
dass diese Angaben regelmäßig von den Kommunikationsknoten (KN1, KN2) jeweils zu dem Informationsspeicher (DB) übermittelt werden. - Verfahren nach einem der vorhergehenden Patentansprüche,
dadurch gekennzeichnet, dass in Schritt b) beim Zugriff ein Anforderungsprofil des Endgerätes (EG1, EG2) zu dem Informationsspeicher (DB) übermittelt wird, und
dass in Schritt c) von dem Informationsspeicher (DB) zu dem Endgerät (EG1, EG2) die Zugangsparameter derjenigen Kommunikationsknoten (KN1, KN2) übermittelt werden, die dem Anforderungsprofil entsprechen. - Verfahren nach einem der vorhergehenden Patentansprüche,
dadurch gekennzeichnet, dass die in Schritt c) übermittelten Zugangsparameter von dem Endgerät (EG1, EG2) gespeichert werden. - Verfahren nach einem der vorhergehenden Patentansprüche,
dadurch gekennzeichnet, dass in Schritt d) die Anmeldung des Endgerätes (EG1, EG2) durch das Endgerät (EG1, EG2) selbst erfolgt. - Verfahren nach Patentanspruch 7 oder 8,
dadurch gekennzeichnet, dass in Schritt c) die Zugangsparameter mehrerer Kommunikationsknoten (KN1, KN2) zu dem Endgerät (EG1, EG2) übermittelt werden, und
dass Schritt d) in den Fällen, in denen die Anmeldung des Endgeräts (EG1, EG2) bei einem ersten dieser Kommunikationsknoten (KN1, KN2) nicht erfolgreich verläuft, so lange bei weiteren Kommunikationsknoten (KN1, KN2), deren Zugangsparameter in Schritt c) gespeichert wurden, wiederholt wird, bis entweder eine erfolgreiche Anmeldung stattgefunden hat, oder alle mit Zugangsparametern von dem Endgerät (EG1, EG2) gespeicherten Kommunikationsknoten (KN1, KN2) abgearbeitet sind. - Verfahren nach Patentanspruch 9,
dadurch gekennzeichnet, dass in den Fällen, in denen alle gespeicherten Kommunikationsknoten (KN1, KN2) abgearbeitet wurden und bei keinem dieser Kommunikationsknoten (KN1, KN2) eine erfolgreiche Anmeldung stattgefunden hat, das Verfahren beginnend mit Schritt b) wiederholt wird. - Verfahren nach einem der vorhergehenden Patentansprüche,
dadurch gekennzeichnet, dass in einem Speicherbereich des Informationsspeichers (DB) Angaben über mehrere Endgeräte (EG1, EG2) des Kommunikationsnetzwerks gespeichert werden,
dass durch einen Dienst anhand der in Schritt a) in dem Informationsspeicher (DB) registrierten Kommunikationsknoten (KN1, KN2) und anhand der in dem Speicherbereich gespeicherten Angaben über die Endgeräte (EG1, EG2) die jeweilige Zuordnung der Endgeräte (EG1, EG2) zu den Kommunikationsknoten (KN1, KN2) vorgenommen wird,
dass als Ergebnis der Zuordnung zu jedem der Endgeräte (EG1, EG2) jeweils ein bevorzugter Kommunikationsknoten (KN1, KN2) bestimmt wird, und
dass in Schritt d) die Anmeldung der Endgeräte (EG1, EG2) jeweils bei dem zugeordneten bevorzugten Kommunikationsknoten (KN1, KN2) erfolgt. - Verfahren nach einem der vorhergehenden Patentansprüche, gekennzeichnet durch
folgenden zusätzlichen Verfahrensschritt:e) Anmeldung des Endgerätes (EG1, EG2) an einem weiteren derjenigen Kommunikationsknoten, deren Zugangsparameter in Schritt c) übermittelt wurden, wenn der Kommunikationsknoten (KN1, KN2), an dem das Endgerät (EG1, EG2) bislang angemeldet ist, ausfällt. - Verfahren nach einem der vorhergehenden Patentansprüche, gekennzeichnet durch,
die Anmeldung eines Benutzers an demjenigen Kommunikationsknoten (KN1, KN2), an dem das Endgerät (EG1, EG2) angemeldet ist. - Verfahren nach Patentanspruch 13,
dadurch gekennzeichnet, dass an dem Kommunikationsknoten (KN1, KN2) verschiedene Benutzer mit unterschiedlichen Berechtigungen anmeldbar sind, dass in Schritt d) bei der Anmeldung des Endgerätes (EG1, EG2) zusätzlich der Benutzer dieses Endgerätes (EG1, EG2) bei dem Kommunikationsknoten (KN1, KN2) angemeldet wird,
dass ein Standard-Benutzer mit einer Standard-Berechtigung an dem Kommunikationsknoten (KN1, KN2) anmeldbar ist, und
dass das Endgerät (EG1, EG2) mit dem Standard-Benutzer bei dem Kommunikationsknoten (KN1, KN2) angemeldet ist, so lange kein anderer Benutzer über dieses Endgerät (EG1, EG2) an dem Kommunikationsknoten (KN1, KN2) angemeldet ist. - Anordnung zur Anmeldung eines Endgerätes (EG1, EG2) an einem Kommunikationsknoten (KN1, KN2) in einem Kommunikationsnetzwerk,
dadurch gekennzeichnet, dass in dem Kommunikationsnetzwerk ein Informationsspeicher (DB) angeordnet ist, in dem die Kommunikationsknoten (KN1, KN2) mit den jeweiligen Zugangsparametern registriert sind, dass das Endgerät (EG1, EG2) Mittel zum Zugriff auf den Informationsspeicher (DB) aufweist,
dass die Zugangsparameter geeigneter Kommunikationsknoten (KN1, KN2) durch das Endgerät (EG1, EG2) aus dem Informationsspeicher (DB) abrufbar sind, und
dass das Endgerät (EG1, EG2) Mittel zum Anmelden bei einem der geeigneten Kommunikationsknoten (KN1, KN2) anhand der Zugangsparameter aufweist.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10324372 | 2003-05-28 | ||
DE10324372A DE10324372B4 (de) | 2003-05-28 | 2003-05-28 | Verfahren und Anordnung zur Anmeldung eines Endgerätes an einem Kommunikationsknoten |
Publications (3)
Publication Number | Publication Date |
---|---|
EP1482745A2 true EP1482745A2 (de) | 2004-12-01 |
EP1482745A3 EP1482745A3 (de) | 2006-04-12 |
EP1482745B1 EP1482745B1 (de) | 2008-04-09 |
Family
ID=33103638
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04010494A Expired - Lifetime EP1482745B1 (de) | 2003-05-28 | 2004-05-03 | Verfahren und Anordnung zur Anmeldung eines Endgerätes an einem Kommunikationsknoten |
Country Status (4)
Country | Link |
---|---|
US (1) | US20050018620A1 (de) |
EP (1) | EP1482745B1 (de) |
CN (1) | CN100584029C (de) |
DE (2) | DE10324372B4 (de) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007042107A1 (de) * | 2005-10-10 | 2007-04-19 | Nokia Siemens Networks Gmbh & Co. Kg | Direkter verbindungsaufbau von einem abgemeldeten sip endgerät zu einer notrufzentrale |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8735394B2 (en) * | 2005-02-18 | 2014-05-27 | Abraxis Bioscience, Llc | Combinations and modes of administration of therapeutic agents and combination therapy |
DE102005008590B3 (de) | 2005-02-24 | 2006-03-23 | Siemens Ag | Verfahren zum Aufnehmen einer VoIP-Kommunikation mittels einer Peer-to-Peer-Datenbank |
US9521210B2 (en) * | 2006-10-06 | 2016-12-13 | At&T Intellectual Property I, L.P. | Methods and apparatus to install voice over internet protocol (VoIP) devices |
US9219615B2 (en) | 2011-01-28 | 2015-12-22 | Throughtek Co., Ltd. | Remote information communication system and linking method thereof |
US9775039B2 (en) * | 2014-11-18 | 2017-09-26 | T-Mobile Usa, Inc. | Data stitching for networked automation |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1014633A2 (de) * | 1998-12-23 | 2000-06-28 | Nortel Networks Corporation | Skalierbare Gatekeepers in einem Internettelefoniesystem und Betriebsverfahren |
US20020169865A1 (en) * | 2001-01-22 | 2002-11-14 | Tarnoff Harry L. | Systems for enhancing communication of content over a network |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06261043A (ja) * | 1993-03-05 | 1994-09-16 | Hitachi Ltd | 無線lanシステム及びその制御方法 |
US6035339A (en) * | 1997-03-13 | 2000-03-07 | At&T Corporation | Network information delivery system for delivering information based on end user terminal requirements |
US6574197B1 (en) * | 1998-07-03 | 2003-06-03 | Mitsubishi Denki Kabushiki Kaisha | Network monitoring device |
US6986157B1 (en) * | 1998-12-21 | 2006-01-10 | 3Com Corporation | Method and system for dynamic service registration in a data-over-cable system |
US7197044B1 (en) * | 1999-03-17 | 2007-03-27 | Broadcom Corporation | Method for managing congestion in a network switch |
US6633549B1 (en) * | 1999-09-27 | 2003-10-14 | Cisco Technology Inc. | Auto-detection of ISDN BRI services |
US7230944B1 (en) * | 1999-12-30 | 2007-06-12 | Geologic Solutions, Inc. | System and method of host routing when host computer is within a home network and/or a complementary network |
JP2001285476A (ja) * | 2000-03-28 | 2001-10-12 | Fujitsu Ltd | Ip端末収容方法及びそのゲートウェイ装置及びゲートキーパー装置及びip端末 |
EP1185035A1 (de) * | 2000-08-25 | 2002-03-06 | Media-Streams.com AG | System zur Entdeckung von H.323 Gatekeepers in Datennetzen |
US7072650B2 (en) * | 2000-11-13 | 2006-07-04 | Meshnetworks, Inc. | Ad hoc peer-to-peer mobile radio access system interfaced to the PSTN and cellular networks |
US6980977B2 (en) * | 2000-11-30 | 2005-12-27 | Yokogawa Electric Corporation | System for acquiring and analyzing personal profile data and providing the service of delivering various information |
FI110902B (fi) * | 2000-12-15 | 2003-04-15 | Nokia Corp | Pakettidatayhteyksien järjestäminen toimistojärjestelmässä |
US8363647B2 (en) * | 2001-04-03 | 2013-01-29 | Voxpath Networks, Inc. | System and method for configuring an IP telephony device |
US20020196776A1 (en) * | 2001-06-26 | 2002-12-26 | Hsiang-Yu Chiang | Communication system of automatically setting basic data of voice over IP devices |
US7139263B2 (en) * | 2001-10-19 | 2006-11-21 | Sentito Networks, Inc. | Voice over IP architecture |
-
2003
- 2003-05-28 DE DE10324372A patent/DE10324372B4/de not_active Expired - Fee Related
-
2004
- 2004-05-03 EP EP04010494A patent/EP1482745B1/de not_active Expired - Lifetime
- 2004-05-03 DE DE502004006749T patent/DE502004006749D1/de not_active Expired - Lifetime
- 2004-05-27 US US10/855,022 patent/US20050018620A1/en not_active Abandoned
- 2004-05-28 CN CN200410045790A patent/CN100584029C/zh not_active Expired - Fee Related
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1014633A2 (de) * | 1998-12-23 | 2000-06-28 | Nortel Networks Corporation | Skalierbare Gatekeepers in einem Internettelefoniesystem und Betriebsverfahren |
US20020169865A1 (en) * | 2001-01-22 | 2002-11-14 | Tarnoff Harry L. | Systems for enhancing communication of content over a network |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007042107A1 (de) * | 2005-10-10 | 2007-04-19 | Nokia Siemens Networks Gmbh & Co. Kg | Direkter verbindungsaufbau von einem abgemeldeten sip endgerät zu einer notrufzentrale |
Also Published As
Publication number | Publication date |
---|---|
EP1482745B1 (de) | 2008-04-09 |
CN1574971A (zh) | 2005-02-02 |
DE10324372B4 (de) | 2005-04-14 |
DE502004006749D1 (de) | 2008-05-21 |
US20050018620A1 (en) | 2005-01-27 |
EP1482745A3 (de) | 2006-04-12 |
DE10324372A1 (de) | 2005-01-13 |
CN100584029C (zh) | 2010-01-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE602005004636T2 (de) | Verfahren und Vorrichtung zum Behandeln von Benutzeranfragen zum Verlassen oder Wechseln eines Multicast-Kanals | |
DE10144023B4 (de) | Vorrichtung und Verfahren zur automatischen Benutzerprofil-Konfiguration | |
EP1487186B1 (de) | Redundanten Betrieb eines Endgerätes an zumindest zwei Kommunikationsknoten | |
DE4438522A1 (de) | Einrichtung zur Übertragung von Datenströmen in Datenkommunikationsnetzen | |
DE69938252T2 (de) | Sicherheit in telekommunikationsnetzübergangseinrichtungen | |
EP1482745B1 (de) | Verfahren und Anordnung zur Anmeldung eines Endgerätes an einem Kommunikationsknoten | |
DE10316236B4 (de) | Verfahren und Anordnung zur Konfiguration einer Einrichtung in einem Datennetz | |
EP2875626B1 (de) | Verfahren und anordnung zum aufbau einer telekommunikationsverbindung | |
EP1525714B1 (de) | Konfiguration eines auf einem breitband kabelverteilnetz beruhenden telefoniezugangsnetzes und einer zugehörigen paketbasierten vermittliungsstelle | |
EP2875627B1 (de) | Verfahren und anordnung zum aufbau von telekommunikationsverbindungen | |
WO2004032448A1 (de) | Datenkommunikationssystem, rechner, sowie datenkommunikationsverfahren zum parallelen betrieb von standard-basierten und proprietären ressourcen | |
EP2782313B1 (de) | Verfahren zur automatischen übertragung einer information zur inbetriebnahme eines für die sprachkommunikation eingerichteten kommunikationsendgerätes an ein für die textkommunikation eingerichtetes kommunikationsendgerät | |
WO2005094050A1 (de) | Kommunikationsserver, system und verfahren zur steuerung und überwachung von endgeräten mittels cti | |
EP1422910B1 (de) | Betriebsmodus für ein Kommunikationssystem | |
WO2007036403A1 (de) | Abwesenheitsassistenzsystem für multimediafähige kommunikationssysteme | |
EP3959850B1 (de) | Verfahren zum bereitstellen von verbindungsherstellungsdaten sowie anordnung mit einer mehrzahl von kommunikationsservern und einem vermittler | |
EP1089530B1 (de) | Verfahren zum Verifizieren eines Bereitschaftszustandes einer an einer Kommunikationsanlage angemeldeten Applikation | |
EP1584176A1 (de) | Verfahren und anordnung zur steuerung und/oder überwachung eines an ein kommunikations-system angeschlossenen endgerätes | |
WO2004006094A1 (de) | Verfahren zur aktualisierung von diensten in kommunikations-netzwerken | |
DE102004053928A1 (de) | Verfahren und Systemsteuerung für den Aufbau einer IP-Telefonieverbindung | |
DE10204009A1 (de) | Verfahren zum Konfigurieren und Registrieren von Applikationen in einem Kommunikationsnetzwerk | |
EP1542423A1 (de) | Kommunikationssystem zur Verwendung mehrerer Kommunikationsprotokolle | |
EP1486046A1 (de) | Lastverteilung auf periphere einrichtungen eines paketbasierten vermittlungssystems | |
EP1744529A1 (de) | Verfahren zur Steigerung der Verfügbarkeit von Diensten in einem Peer-to-Peer-Kommunikationsnetz | |
EP2315410A1 (de) | Bündelfunksystem auf Basis von Sprache-über-Internet Protokoll und entsprechendes Betriebsverfahren |
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 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL HR LT LV MK |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL HR LT LV MK |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04M 7/00 20060101ALI20060223BHEP Ipc: H04M 3/42 20060101ALI20060223BHEP Ipc: H04Q 3/00 20060101ALI20060223BHEP Ipc: H04Q 3/545 20060101AFI20040708BHEP Ipc: H04L 29/12 20060101ALI20060223BHEP |
|
17P | Request for examination filed |
Effective date: 20061012 |
|
AKX | Designation fees paid |
Designated state(s): DE FR GB IT SE |
|
17Q | First examination report despatched |
Effective date: 20061201 |
|
17Q | First examination report despatched |
Effective date: 20061201 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
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 Free format text: NOT ENGLISH |
|
REF | Corresponds to: |
Ref document number: 502004006749 Country of ref document: DE Date of ref document: 20080521 Kind code of ref document: P |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
ET | Fr: translation filed | ||
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: 20090112 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: 732E Free format text: REGISTERED BETWEEN 20121025 AND 20121031 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: TP Owner name: SIEMENS ENTERPRISE COMMUNICATIONS GMBH & CO. K, DE Effective date: 20130108 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: FRITZSCHE PATENT, DE |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: FRITZSCHE PATENT, DE Effective date: 20130313 Ref country code: DE Ref legal event code: R081 Ref document number: 502004006749 Country of ref document: DE Owner name: SIEMENS ENTERPRISE COMMUNICATIONS GMBH & CO. K, DE Free format text: FORMER OWNER: SIEMENS AKTIENGESELLSCHAFT, 80333 MUENCHEN, DE Effective date: 20130313 Ref country code: DE Ref legal event code: R081 Ref document number: 502004006749 Country of ref document: DE Owner name: UNIFY GMBH & CO. KG, DE Free format text: FORMER OWNER: SIEMENS AKTIENGESELLSCHAFT, 80333 MUENCHEN, DE Effective date: 20130313 Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: FRITZSCHE PATENTANWAELTE, DE Effective date: 20130313 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: FRITZSCHE PATENT, DE |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 502004006749 Country of ref document: DE Owner name: UNIFY GMBH & CO. KG, DE Free format text: FORMER OWNER: SIEMENS ENTERPRISE COMMUNICATIONS GMBH & CO. KG, 81379 MUENCHEN, DE Effective date: 20131112 Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: FRITZSCHE PATENT, DE Effective date: 20131112 Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: FRITZSCHE PATENTANWAELTE, DE Effective date: 20131112 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: CD Owner name: UNIFY GMBH & CO.KG, DE Effective date: 20140429 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: SE Payment date: 20160523 Year of fee payment: 13 Ref country code: IT Payment date: 20160524 Year of fee payment: 13 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: SCHAAFHAUSEN PATENTANWAELTE PARTNERSCHAFTSGESE, DE Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 Country of ref document: DE Representative=s name: FRITZSCHE PATENTANWAELTE, DE Ref country code: DE Ref legal event code: R081 Ref document number: 502004006749 Country of ref document: DE Owner name: UNIFY GMBH & CO. KG, DE Free format text: FORMER OWNER: UNIFY GMBH & CO. KG, 81379 MUENCHEN, DE |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 14 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: EUG |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20170504 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 15 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20170503 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 502004006749 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: FR Payment date: 20230517 Year of fee payment: 20 Ref country code: DE Payment date: 20230519 Year of fee payment: 20 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20230522 Year of fee payment: 20 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R071 Ref document number: 502004006749 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: PE20 Expiry date: 20240502 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION Effective date: 20240502 |