WO2009030659A1 - Procédé d'adressage de communications d'abonnés mobiles lors de l'utilisation d'une transmission de données en mode paquet pour des applications ferroviaires - Google Patents

Procédé d'adressage de communications d'abonnés mobiles lors de l'utilisation d'une transmission de données en mode paquet pour des applications ferroviaires Download PDF

Info

Publication number
WO2009030659A1
WO2009030659A1 PCT/EP2008/061485 EP2008061485W WO2009030659A1 WO 2009030659 A1 WO2009030659 A1 WO 2009030659A1 EP 2008061485 W EP2008061485 W EP 2008061485W WO 2009030659 A1 WO2009030659 A1 WO 2009030659A1
Authority
WO
WIPO (PCT)
Prior art keywords
rbc
fzg
address
packet
addresses
Prior art date
Application number
PCT/EP2008/061485
Other languages
German (de)
English (en)
Inventor
Detlef Kendelbacher
Volker Pliquett
Fabrice Stein
Original Assignee
Siemens Aktiengesellschaft
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 Aktiengesellschaft filed Critical Siemens Aktiengesellschaft
Publication of WO2009030659A1 publication Critical patent/WO2009030659A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/20—Trackside control of safe travel of vehicle or train, e.g. braking curve calculation
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/70—Details of trackside communication
    • 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/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • 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
    • H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
    • 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/50—Address allocation
    • H04L61/5084—Providing for device mobility
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/20—Trackside control of safe travel of vehicle or train, e.g. braking curve calculation
    • B61L2027/202—Trackside control of safe travel of vehicle or train, e.g. braking curve calculation using European Train Control System [ETCS]
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L2205/00—Communication or navigation systems for railway traffic
    • B61L2205/02—Global system for mobile communication - railways [GSM-R]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]

Definitions

  • a rail application is the European Train Control System (ETCS), a European standardized system for train control and train control at the railways, with the aim of ensuring the interoperability of train traffic across borders.
  • ETCS uses GSM mobile radio in Level 2 and 3 and currently transmits train control data via connection-oriented data channels.
  • Packet oriented data services such as GPRS use packet-address based connectionless communication instead of telephone numbers and connection-oriented channels. cation, in which individual data packets are transmitted. Mobile and stationary subscribers require packet addresses for data exchange, eg IP addresses, instead of telephone numbers. The structure of packet addresses depends on the used packet-oriented data service. The packet addresses can be assigned temporarily due to a limited address range - dynamic addressing.
  • the dynamic allocation of packet address addresses places special demands on mobile data communication, since the addresses of mobile and stationary subscribers may change, for example after a re-login to the mobile radio network.
  • a dynamic assignment of nodes and packet addresses necessary.
  • the dynamic addressing of users in railway applications places additional demands on these rail services. For example, the addresses of vehicles and line centers may change during ETCS operation.
  • the inventive method is for applications that mobile data transmission in Area of railways use, provided. It is explained using the example of the European Train Control System ETCS. However, it is also usable for any rail services using mobile data transmission.
  • the abbreviation RBC - Radio Block Center which derives from the ETCS, is representative of stationary facilities for data transmission, while the abbreviation FZG - Vietnamese - is used to represent mobile devices for data transmission.
  • the destination RBC is the fixed entity with which a mobile subscriber must communicate as part of the train service.
  • the ETCS address provides a means of addressing participants at the application level. It can be replaced in other rail services by a corresponding orbital service specific user address or subscriber identifier.
  • the ADC acts as a central stationary instance for the determination of packet addresses of communication authorities - central information. It contains a memory that contains a dynamic allocation of ETCS addresses to packet addresses. This memory is updated regularly. FZG and RBC with communication needs can contact the ADZ to get information about the packet address of a communication partner.
  • the only instance in the mobile network is the requirement to be reachable under a static address. This can be realized by one or more permanently assigned packet addresses. Alternatively, a name service may be used to address the ADF.
  • the ADZ address is known to all participants of the railway service, which is technically realized, for example, by project planning.
  • the ADC should be designed to be redundant, for example, with several fixed packet addresses to meet the high availability requirements that are placed on a central facility in railway operations.
  • the mobile network several ADF can be set, for example, each rail operator a to optimize the communications ⁇ routes.
  • FZGe must have additional information of the currently competent ADZ or contact different ADZs one after the other or in parallel for their inquiries.
  • an ADF can be integrated if necessary into a RBC, so that the one or more RBCs zusharm ⁇ Lich take the ADF function.
  • RBC and optional FZG are extended with additional memory and management functions for address management.
  • RBC receive memory and functions for managing dynamic address data of known FZG and RBC. The data is always updated when a) new packet addresses are assigned to FZG, eg when an FZG is added to the ETCS system b) new packet addresses are assigned to RBC, eg after Maintenance work .
  • RBC can use this address data to provide information to FZG about required parcel addresses.
  • FZG can be expanded to include storage and RBC dynamic address data management capabilities.
  • the local storage of RBC address data can be the
  • the communication between FZG and ADZ serves to determine the package address of the RBC responsible for the FZG.
  • the vehicle transmits to the ADC the ETCS address of the RBC and receives the current packet address of the RBC.
  • FZG further communication takes place between FZG and RBC.
  • This communication is used to determine the packet address of the currently responsible RBC destination RBC.
  • a request is made for the unknown packet address of the destination RBC in a RBC with a known packet address.
  • the RBC determines the Packet address of the target RBC, usually the neighbor RBC, and deliver it to the FZG.
  • FZG - Target RBC Parallel to the application communication can optionally be an additional communication between FZG and destination RBC for the purpose of transmitting the ETCS addresses and packet addresses for multiple adjacent RBC to the FZG, so that these addresses are immediately available locally when communication needs - vehicle -Adresscache.
  • the communication between RBC provides for the distribution of the currently valid address data, namely ETCS addresses and associated packet addresses, to a defined distribution circuit of RBC.
  • the distribution circuit usually consists of the neighbor RBC and can be flexibly defined for each RBC.
  • Each RBC supplies the address data of all known vehicles and RBC to all RBC in the distribution circuit.
  • the RBCs are able to initiate communication with known FZG and RBC, as well as provide parcel address information to FZG.
  • All RBCs belonging to an ADZ provide up-to-date address data via known RBC and optionally via known FZG to the ADZ. With this communication, the address database in the ADZ is kept up to date, so that the
  • ADZ is always able to deliver current packet addresses from RBC and optionally from FGZ to requesting instances.
  • setup logs are executed before the actual application communication in order to get the current packet address of the mobile or fixed communication partner. They can run both on the initiative of stationary and mobile participants. Real-time requests are made to these protocols.
  • the update logs are executed continuously and largely independent of the application communication. They run between fixed and mobile participants without
  • Real-time requirements i. with low priority, from and synchronize existing information about current addresses of subscribers.
  • the update logs can work both cyclically and event-driven.
  • To store the address data e.g. After failures or maintenance, to be able to synchronize, a complete transfer of the present address information is required - no delta transfer.
  • This protocol is used by mobile and / or fixed subscribers for requesting unknown packet addresses in known subscribers.
  • the application takes place, for example, when an FZG wants to establish a communication relationship with an RBC with an unknown packet address, for example for the purpose of RBC handover, and in the local Database in the FZG the package address of the searched RBC does not exist.
  • the FZG makes a request to the destination RBC's packet address at a RBC with a known packet address.
  • the FZG transfers the ETCS address of the destination RBC and receives its packet address if this information is available.
  • This protocol is mobile and / or fixed
  • Participants used to request unknown packet addresses at the ADZ are Participants used to request unknown packet addresses at the ADZ. Its application occurs, for example, when an FZG wants to establish a communication relationship with an RBC of unknown packet address, e.g. for the purpose of new inclusion in the ETCS, and neither in the local database in the FZG the required IP address exists, nor by application of the primary setup protocol, the searched IP address could be provided.
  • the FZG makes a request to the ADZ for the packet address of the searched RBC.
  • the FZG hands over the ETCS address of the searched RBC and receives its packet address, if this information is available.
  • the primary setup protocol is first used to determine the unknown IP address using a known subscriber address. If the request is unsuccessful using the primary setup protocol, the secondary setup protocol will be used to request the desired packet address from the ADF.
  • Update logs are available in three forms: a) ADZ update protocol:
  • the ADZ update protocol is used to update the packet address database in the ADZ.
  • Each RBC transmits to the ADZ the ETCS addresses and the packet addresses of all registered RBCs.
  • the ETCS addresses and the packet addresses of the FZG registered in the RBC are also transmitted to the ADZ.
  • the ADZ update protocol ensures that contents and changes in the address database of the fixed subscribers are continuously transmitted to the ADZ, e.g. Changes in RBC
  • the packet addresses of the RBC can be permanently assigned in the transmission network.
  • the ADZ update protocol can be executed offline in this case, e.g. by designing the ADZ.
  • the RBC update protocol is used to exchange address ⁇ information between stationary participants. Neighboring RBCs continually exchange content and changes in their local address database to synchronize their data status. By means of the RBC update protocol, the packet addresses and ETCS addresses of the FZG registered in one RBC are transmitted to the neighboring RBC. Furthermore, the current packet addresses registered in the RBC and the ETCS addresses can also be reported by the RBC to the neighboring RBC. The exchange of addresses can be up a fixed range of RBC, eg, only direct neighbor RBC, to reduce the amount of information.
  • the RBC update protocol distributes known FZG and optionally RBC address information along the route. If necessary, the RBCs can then establish links with FZG and RBC or provide address information.
  • the packet addresses of the RBCs can be fixedly assigned, e.g. by projecting.
  • no online update of the RBC addresses between the RBCs is required during runtime of the system, and the RBC update protocol can be limited to the distribution of FZG addresses.
  • the FZG update protocol is used to update the address database in mobile subscribers. It runs in the background while an FZG exchanges data with an RBC as part of the application communication.
  • the RBC uses the FZG update protocol to transmit to the FZG all RBC packet and ETCS addresses stored in its local database. These are expediently the addresses of neighboring RBCs. With this information, the FZG will be able to immediately find the current RBC handover address of the next target RBC in its local database and establish a new communication relationship.
  • the use of the FZG update protocol is optional and requires the management of local data storage in the FZG. With Nutz speeds up between FZG and RBC - address cache.
  • Fig. 1 An overall view of the data connections of
  • Participant, Fig. 2 the communication from the mobile to the fixed
  • FIG. 6 shows the sequence of an RBC update protocol
  • FIG. 7 shows the sequence of an FZG update protocol
  • the FZG - RBC communication is established on the initiative of the FZG.
  • FZG and RBC are identified in the ETCS with unique ETCS addresses.
  • the ETCS address of the respective destination RBC will be announced to the FZG during its journey over the ETCS route.
  • the transmission of the address of the destination RBC to the FZG can be done by means of balises.
  • a valid IP address is required as the packet address of the current target RBC.
  • To determine the required IP address of the target RBC in the vehicle a three-stage procedure is carried out, which is the same for all operational scenarios.
  • Level 1 Based on the ETCS address of the target RBC is stored in the local database of the
  • FZG searched for the associated IP address. If an entry exists, the communication with the stored IP address is established. The implementation of the next two
  • Steps are omitted in this case. If there is no entry or no local database, or the communication fails due to an outdated IP address, it continues with level 2.
  • Stage 2 With the known IP address of the last contacted RBC, the FZG executes the primary setup protocol. This is a query of the searched IP address in a known RBC - usually the neighbor RBC. If the RBC can select the required IP address from its local database, it is transmitted to the FZG. The FZG establishes the connection to the destination RBC with the transmitted IP address. If the communication to the target RBC is successful, stage 3 is no longer performed. If the neighboring RBC can not deliver the IP address you are looking for, or the connection to the target RBC fails.
  • Level 3 If levels 1 and 2 are unsuccessful, the secondary setup protocol is executed by the FZG as a fallback procedure.
  • the FZG requests the searched IP address at the ADZ.
  • the address of the ADC is known in all FZGen - configured - and can therefore be used at any time.
  • the FZG passes the ETCS address of the destination RBC to the ADF.
  • the ADZ then transmits the corresponding current IP address to the FZG. With the transmitted IP address, the FZG establishes a connection to the destination RBC.
  • the communication FZG - RBC can also be established on the initiative of the RBC. If the RBC has already had communication with the FZG in the past, its IP address is
  • Level 1 The ETCS address of the FZG is used to search for the associated IP address in the local database of the RBC. If an entry exists, the communication with the stored IP address is established. The implementation of the next two stages is omitted in this case. If there is no entry or the communication fails due to an outdated IP address, it continues with level 2.
  • Stage 2 The RBC polls the searched IP address on a RBC with a known IP address - Neighbor RBC. To do this, the RBC applies the primary setup protocol. If the neighboring RBC can select the required IP address from its local database, it is transmitted to the RBC. The RBC establishes the connection to the FZG with the transmitted IP address. If the communication to the FZG is successful, the execution of stage 3 is omitted. If the neighboring RBC can not deliver the searched IP address or if the connection to the FZG fails, it continues with level 3.
  • Level 3 If levels 1 and 2 are unsuccessful, If necessary, run the secondary setup protocol.
  • the RBC requests the requested IP address at the ADZ.
  • the address of the ADC is known in all RBCs - configured - and can therefore be used at any time.
  • the RBC passes the destination RBC's ETCS address to the ADF.
  • the ADZ then transmits the corresponding current IP address to the RBC. With the transmitted IP address, the RBC establishes a connection to the FZG.
  • the optional local address database in the FZG contains RBC's ETCS and IP addresses. These addresses are updated by the FZG update protocol. This optional protocol will be executed when the FZG communicates with the responsible RBC for ETCS data transmission. The transmission of the address data can take place with a lower priority than the transmission of the ETCS train control data. Multiplexing the data in the transport layer of the standardized EURORADIO protocol with the address data of the FZG update protocol is possible.
  • the FZG update protocol updates the addresses of all neighbor RBCs in FZG. As a result, these addresses are immediately available onboard during the RBC handover and need not be requested via setup protocols at the time the connection is established.
  • the sequence of the FZG update protocol is shown in FIG.
  • the address database in the RBC contains the ETCS and IP addresses of all FZGs communicating in the area of the RBC and the neighboring RBC as well as the ETCS and IP addresses of the RBC and the neighboring RBC.
  • the RBC update log synchronizes the datasets adjacent RBC by transmitting the stored FZG and RBC addresses between neighbor RBCs.
  • the transfer of addresses can be restricted to FZG and RBC in a defined environment in order to optimize the data volume. By way of example, only the addresses of the FZG communicating directly with the RBC are transmitted to the direct neighbor RBC.
  • When setting up a new communication with a FZG its ETCS and IP address is stored in the address database of the RBC.
  • the RBC update protocol continues to distribute the address information of the FZG to the neighboring RBC.
  • the transmission can take place via landline communication resources between the RBCs that already exist for the ETCS communication.
  • the RBC update protocol must ensure that even after a RBC has failed, its database is re-synchronized with the neighboring RBC.
  • the flow of the RBC update protocol is shown in Fig. 6 - right side.
  • the address database in the ADZ contains the ETCS and IP addresses of all RBCs in a specified area.
  • the ETCS and IP addresses of all FZG can be managed in a defined area.
  • the area size is freely selectable; For example, an ADC may be responsible for a country.
  • ADZ address database
  • its address database must be kept up to date using the ADZ update protocol. This can be done either online via online data communication RBC ⁇ ADZ or offline via configuration ADZ.
  • the ADZ update log is executed between each RBC in the specified area and the ADF.
  • the protocol transmits hold the local address database of the RBC to the ADZ. Since address information, for example the current IP address of a communicating FZG, can be reported by several RBCs to the ADZ, it is expedient to supplement the address information with information on actuality, for example by a time stamp, so that the ADZ always has the most up-to-date Information stand from the messages of the RBC can select.
  • the sequence of the ADZ update protocol is shown in Fig. 6 - left side.
  • the particular advantage of the method according to the invention is that it can be used for all railway services for data transmission in IP-based networks.
  • the railways are able to tap into the potential of packet-oriented data services in the GSM-R.
  • the process can be integrated into existing ETCS systems while maintaining the current standard - EURORADIO. Furthermore, existing standards for data transmission in railway services for the application of the method can be easily extended.
  • the required setup and update logs are simple and resource efficient. Their integration into the ETCS and other rail services can be cost-effective and low-risk.
  • the wireless setup and update protocols between FZG and RBC can be carried out without changing the EURORADIO standard together with the transmission of the ETCS data.
  • EURORADIO protocols For a shared use of EURORADIO protocols only needs to be assigned a new service ID.
  • a protocol-separated transmission for ETCS and setup / update data done.
  • the required storage and management functions can be easily integrated into existing systems, for example integration of an ADC into an RBC.
  • the additional investment needs are relatively low.
  • previous application addressing methods can be used unchanged in the ETCS, for example transmission of ETCS addresses of the RBCs from balises. It is not necessary to configure the IP addresses of RBC or FZG.
  • the address management according to the method described is open and expandable.
  • New FZG and RBC are automatically integrated into the process.
  • the method can be used in local and temporal mixed operation with connection-oriented channels.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mechanical Engineering (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé d'adressage de communications d'abonnés mobiles pour une transmission de données en mode paquet aux fins d'applications ferroviaires. L'invention vise à créer, pour les applications de données ferroviaires mobiles, une gestion dynamique d'adresses qui prenne en compte les relations de communication variables entre des équipements mobiles et fixes, les adresses de paquets variables des interlocuteurs, l'entretien, le dépannage et les extensions du système, le comportement en temps réel nécessaire et les limitations et conditions marginales spéciales des ressources radio. Ces exigences sont satisfaites par la gestion dynamique d'adresses selon l'invention. Le procédé selon l'invention est prévu pour des applications qui utilisent une transmission mobile de données dans le domaine ferroviaire et est expliqué à la lumière du système européen de protection automatique des trains ETCS. Il est en outre utilisable pour des services ferroviaires quelconques ayant recours à une transmission mobile de données.
PCT/EP2008/061485 2007-09-03 2008-09-01 Procédé d'adressage de communications d'abonnés mobiles lors de l'utilisation d'une transmission de données en mode paquet pour des applications ferroviaires WO2009030659A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102007041959A DE102007041959B4 (de) 2007-09-03 2007-09-03 Verfahren zur Kommunikationsadressierung mobiler Teilnehmer bei Verwendung von paketorientierter Datenübertragung für Bahnanwendungen
DE102007041959.9 2007-09-03

Publications (1)

Publication Number Publication Date
WO2009030659A1 true WO2009030659A1 (fr) 2009-03-12

Family

ID=40254479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/061485 WO2009030659A1 (fr) 2007-09-03 2008-09-01 Procédé d'adressage de communications d'abonnés mobiles lors de l'utilisation d'une transmission de données en mode paquet pour des applications ferroviaires

Country Status (2)

Country Link
DE (1) DE102007041959B4 (fr)
WO (1) WO2009030659A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2765053A2 (fr) 2013-02-06 2014-08-13 Insight Design Services Limited Système de diagnostic de train ferroviaire
EP3220613A1 (fr) * 2016-03-17 2017-09-20 Thales Deutschland GmbH Procédé de fonctionnement d'un réseau de communication par paquets dans un réseau ferroviaire
WO2018054667A1 (fr) * 2016-09-20 2018-03-29 Siemens Aktiengesellschaft Procédé d'encapsulation de la commande d'appareils radiotéléphoniques mobiles dans des véhicules ferroviaires à système etcs et véhicule ferroviaire à système etcs

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6129521B2 (ja) * 2012-11-19 2017-05-17 株式会社日立製作所 列車のリアルタイム走行情報を活用した運行関連情報表示システム及び方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1596620A1 (fr) * 2004-05-14 2005-11-16 Nortel Networks Limited Système et procédé de traitement d'un numéro fonctionnel pour applications de télécommunications
WO2006082033A1 (fr) * 2005-02-01 2006-08-10 Nortel Networks Limited Systeme et procede destines a la transmission de messages courts dans un reseau de telecommunication hybride sans fil-filaire

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6633761B1 (en) * 2000-08-11 2003-10-14 Reefedge, Inc. Enabling seamless user mobility in a short-range wireless networking environment
US6965584B2 (en) * 2001-02-27 2005-11-15 Telcordia Technologies, Inc. Dynamic forward assignment of internet protocol addresses in wireless networks
US7272121B2 (en) * 2001-06-19 2007-09-18 Telcordia Technologies, Inc. Methods and apparatus for a modular wireless system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1596620A1 (fr) * 2004-05-14 2005-11-16 Nortel Networks Limited Système et procédé de traitement d'un numéro fonctionnel pour applications de télécommunications
WO2006082033A1 (fr) * 2005-02-01 2006-08-10 Nortel Networks Limited Systeme et procede destines a la transmission de messages courts dans un reseau de telecommunication hybride sans fil-filaire

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
EURORADIO INTERFACE GROUP: "Radio Transmission FFFIS for EuroRadio", UIR ERTMS/GSM-R, UNISIG, 2003, XP002512194, Retrieved from the Internet <URL:http://gsm-r.uic.asso.fr/docs/specifications/euroradio_fffis_v12.pdf> [retrieved on 20090126] *
FROEMEL M: "BAHN FREI FUER GSM. GSM-RAILWAY - TECHNIK UND ANWENDUNGEN", NET - ZEITSCHRIFT FUER KOMMUNIKATIONSMANAGEMENT, NET VERLAGSSERVICE, WOLTERSDORF, DE, vol. 52, no. 12, 1 January 1998 (1998-01-01), pages 54 - 57, XP000802247, ISSN: 0947-4765 *
GSM-R OPERATOS GROUP: "UIC Project EIRENE, System Requirements Specification", EIRENE, EUROPEAN INTEGRATED EAILWAY RADIO ENHANCED NETWORK, 17 May 2006 (2006-05-17), XP002512195, Retrieved from the Internet <URL:http://www.era.europa.eu/Documents/ERTMS%20Documentation/Mandatory%20Specifications/EIRENE-SRSv15.pdf> [retrieved on 20090126] *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2765053A2 (fr) 2013-02-06 2014-08-13 Insight Design Services Limited Système de diagnostic de train ferroviaire
EP3220613A1 (fr) * 2016-03-17 2017-09-20 Thales Deutschland GmbH Procédé de fonctionnement d'un réseau de communication par paquets dans un réseau ferroviaire
KR20170108889A (ko) * 2016-03-17 2017-09-27 탈레스 도이칠란트 게엠베하 철도 시스템의 패킷 기반 통신 네트워크 작동 방법
EP3220613B1 (fr) 2016-03-17 2019-12-18 Thales Management & Services Deutschland GmbH Procédé de fonctionnement d'un réseau de communication par paquets dans un réseau ferroviaire
KR102070397B1 (ko) * 2016-03-17 2020-03-02 탈레스 매니지먼트 앤드 서비씨즈 도이칠란트 게엠베하 철도 시스템의 패킷 기반 통신 네트워크 작동 방법
WO2018054667A1 (fr) * 2016-09-20 2018-03-29 Siemens Aktiengesellschaft Procédé d'encapsulation de la commande d'appareils radiotéléphoniques mobiles dans des véhicules ferroviaires à système etcs et véhicule ferroviaire à système etcs

Also Published As

Publication number Publication date
DE102007041959B4 (de) 2010-09-02
DE102007041959A1 (de) 2009-03-05

Similar Documents

Publication Publication Date Title
DE102007041177B4 (de) Verfahren zum ETCS-Online-Schlüsselmanagement
DE60215005T2 (de) Dynamisches Netzwerk und Wegeleitverfahren für ein dynamisches Netzwerk
EP1094962B1 (fr) Procede de communication optimise pour services de regulation de la circulation avec appui radio
DE19922288A1 (de) Anordnung zur mobilen Kommunikation
DE10145596A1 (de) Netzwerk mit mehreren Sub-Netzwerken
EP3811570B1 (fr) Procédé de configuration, procédé de fourniture des informations de topologie, utilisation, appareil, programme informatique et support lisible par ordinateur
DE102007041959B4 (de) Verfahren zur Kommunikationsadressierung mobiler Teilnehmer bei Verwendung von paketorientierter Datenübertragung für Bahnanwendungen
EP1719303A1 (fr) Procede pour etablir une liaison entre un demandeur de service (client) et un prestataire de services (serveur) dans un reseau de communication mobile decentralise
EP3220613B1 (fr) Procédé de fonctionnement d&#39;un réseau de communication par paquets dans un réseau ferroviaire
DE102014102035B4 (de) Computereinrichtung, System mit einer Computereinrichtung und Computerprogramm
DE102008039427B4 (de) Parametrisierbare Auswahl eines Kommunikationssystems auf Basis von Namenauflösungsmechanismen
DE10001098A1 (de) Verfahren zur dezentralen Übertragung und Verteilung von Nutzdaten zwischen Teilnehmern eines Telekommunikationsnetzwerkes
EP1376940B1 (fr) Procédé pour la transmission de données
DE10119492B4 (de) Verfahren zur Verwaltung der Mobilität von Telefonapparaten in einem schnurlosen Fernmeldenetz
DE102020123413B4 (de) Verfahren zur Datenübertragung in einem Ad-hoc-Netzwerk
DE10047131B4 (de) Verfahren zum Betreiben eines Zugangsnetzes
EP1370095B1 (fr) Procédé de détermination de position dans un réseau de téléphonie mobile
EP1774754B1 (fr) Terminal de communication mobile pour une utilisation dans plusieurs reseaux locaux sans fil et modes de fonctionnement associes
DE10205907A1 (de) Verfahren zum Wechseln von IP-Zugangsnetzen bei bestehender Verbindung zu einer entfernten IP-Einrichtung und Kommunikationssystem zum Durchführen eines solchen Verfahrens
EP1452041A1 (fr) Procede et dispositif reseau pour mettre a disposition en particulier des services de communication personnalises dans un systeme de communication
DE102004026359B4 (de) Drahtloses Informationssystem mit mobilen Endgeräten und Verfahren zum Betrieb dieses Informationssystems
WO2005036841A1 (fr) Procede et dispositif pour actualiser une liste d&#39;abonnes dans un systeme de communication
WO2007144214A1 (fr) Procédé et dispositif pour le placement de paquets de données entre des terminaux mobiles d&#39;utilisateur et un réseau de radiotéléphonie mobile
EP2484139A1 (fr) Système cellulaire numérique de radiocommunication à ressources partagées avec extension de réseau à large bande selon les besoins

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08803467

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08803467

Country of ref document: EP

Kind code of ref document: A1