WO2001074099A1 - Infrastructure de radiocommunications utilisant un protocole de communication par paquets - Google Patents

Infrastructure de radiocommunications utilisant un protocole de communication par paquets Download PDF

Info

Publication number
WO2001074099A1
WO2001074099A1 PCT/GB2001/001434 GB0101434W WO0174099A1 WO 2001074099 A1 WO2001074099 A1 WO 2001074099A1 GB 0101434 W GB0101434 W GB 0101434W WO 0174099 A1 WO0174099 A1 WO 0174099A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet data
data network
mobile station
mobile
network
Prior art date
Application number
PCT/GB2001/001434
Other languages
English (en)
Inventor
Mark Wentworth Rayne
Original Assignee
Simoco International Limited
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 Simoco International Limited filed Critical Simoco International Limited
Priority to AU42637/01A priority Critical patent/AU4263701A/en
Priority to EP01915552A priority patent/EP1183886A1/fr
Publication of WO2001074099A1 publication Critical patent/WO2001074099A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/181—Transcoding devices; Rate adaptation devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H04L2012/6421—Medium of transmission, e.g. fibre, cable, radio, satellite
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H04L2012/6472—Internet

Definitions

  • the present invention relates to a mobile radio communications system and to a method of operating a mobile radio communications system.
  • mobile radio telecommunications systems such as the GSM (Global 0 System for Mobile communications) public cellular telephone system comprise a fixed radio network comprising plural base stations for communicating with mobile stations of the system.
  • the base stations are linked together by a fixed radio network infrastructure 5 ' which includes one or more switches which route the audio speech signals through the fixed network from one radio base station to another.
  • the switches are usually operated and must be capable of operating in a so-called circuit-mode switching arrangement, in which the 0 switches are arranged to provide in effect a fixed circuit between the network terminals while a call is proceeding.
  • the switches used in such mobile radio communications systems, and the associated fixed network 5 controllers, are relatively expensive specialist equipment usually designed or adapted specifically for the particular type of radio system in question.
  • the number and type of switches used is often also the limiting factor in determining the traffic capacity of 0 the radio system, since the switches determine how many audio channels can be handled simultaneously by the fixed radio network.
  • a radio network 5 infrastructure for a mobile radio communications system, the radio network infrastructure comprising: plural interconnected base stations, the base stations being adapted to communicate with mobile stations of the radio system via a mobile radio system communications protocol; wherein: the radio network infrastructure comprises a packet data communications network interconnecting the base stations which uses a packet data network communications protocol; and the network infrastructure further comprises means for converting communications in the mobile radio system communications protocol received at a base station from a mobile station to the packet data network communications protocol for onward transmission through the network infrastructure, and means for converting communications in the packet data network communications protocol from the network for a mobile station to the mobile radio system communications protocol for onward transmission by a base station to the mobile station.
  • a method of operating a mobile radio communications system comprising: using a mobile radio system communications protocol for radio communications between the mobile stations and base stations; using a packet data network communications protocol for communications between the base stations via the fixed network; converting communications in the mobile radio system communications protocol received at a base station from a mobile station to the packet data network communications protocol for onward transmission through the fixed network; and converting communications in the packet data network communications protocol from the fixed network for a mobile station to the mobile radio system communications protocol for onward transmission by a base station to the mobile station.
  • the fixed network of the mobile radio system comprises a packet data communications network, rather than the more usual circuit-mode switch based network.
  • IP Internet protocol
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • the present invention thus effectively combines a packet data fixed infrastructure with a mobile radio system air-interface. It thus combines the benefits of effective radio communications with the benefit of being able to interconnect and control radio base stations using inexpensive, readily available packet data network equipment and protocols.
  • messages and other information received in one communications protocol should be converted appropriately to the other protocol, i.e. communications in the radio system's communications protocol used over the air (radio) -interface between the mobile stations and the base stations should be converted appropriately (e.g. placed in properly formatted data packets) to the packet data communications protocol used for the fixed infrastructure, and vice-versa.
  • the communications being routed through the packet data network and converted between the packet data communications protocol and the air-interface communications protocol can comprise all forms of communication such as speech (e.g. speech frames), short data messages, etc., and not just packet data (e.g. IP packets) that is already in a packet data format but may need some modification to, e.g., be transmitted over the air interface to a packet data based device in a mobile station (e.g. an IP-based protocol within the mobile station) .
  • the communications protocol conversion can take place where desired in the fixed network, but preferably takes place at or near a node of the packet data network to which the relevant base station is connected.
  • the network infrastructure further comprises a controller associated with each base station for interfacing between the mobile radio system protocol used for communications between the base station and the mobile stations, and the packet data network communications protocol used for communications between base stations via the packet data network, where the conversion takes place.
  • controllers are preferably located at the node of the network to which their associated base station (s) connect (i.e. such that each base station is connected to the packet data network via an interfacing controller) .
  • Each interfacing controller should convert information and requests destined for and received from its associated base station or base stations appropriately for onward transmission.
  • the number of such interfacing controllers used in the fixed network can be selected as desired.
  • a single network interfacing controller may be associated with and accessible by plural base stations (e.g. all those base stations at a single base site and/or connecting to the same network node) , or each base station may have its own individual single controller.
  • a radio network infrastructure for a mobile radio communications system, comprising: plural interconnected base stations, the base stations being adapted to communicate with mobile stations of the radio system via a mobile radio system communications protocol; wherein: the radio network infrastructure comprises a packet data communications network interconnecting the base stations which uses a packet data network communications protocol; and the network infrastructure further comprises a controller associated with each base station for interfacing between the mobile radio system protocol used for communications between the base station and the mobile stations, and the packet data network communications protocol used for communications between base stations via the packet data network.
  • each mobile station is allocated a corresponding packet data network address to which communications, data, etc., intended for it can be routed.
  • each mobile station's packet data network address is preferably associated with the mobile station's allocated radio system protocol address (e.g. number), where appropriate, so that the system can convert between the packet data network and radio system addresses of the mobile stations (which will usually differ) to allow calls, etc., to be properly routed.
  • a request from one mobile station to place a speech call to another mobile station will be converted into a request from a device with a given packet data network address to send some packets of data to another packet data network address. This could be achieved by, for example, inserting the speech frames into data packets each individually addressed to the intended destination and placing them on the packet data network.
  • the packet data network address for a mobile station can be selected as desired. It is preferably an address at or associated with the network node (e.g. interfacing controller) to which the base station serving the mobile station is connected. Where the packet data network comprises an Internet Protocol network, it could, for example, comprise a full Internet Protocol address, or a port number at a given Internet Protocol address (e.g. at the Internet Protocol address of the interfacing controller associated with the mobile station's current serving base station) .
  • the use of port numbers for the mobile stations ' addresses permits larger numbers of mobile stations to be accommodated at each separate packet data network (e.g. Internet Protocol) address (since for example, in TCP or UDP a 16-bit port number is defined at each network (IP) address) , and thus allows each network address to carry very many separate mobile station connections.
  • IP network
  • the mobile stations' packet data network addresses, together with their corresponding radio system addresses, where necessary, should be stored in the packet data network infrastructure and kept updated in an appropriate manner to allow the relevant addresses to be determined (e.g. by the interfacing controllers) when a call to or from a particular mobile station arrives.
  • one or more databases storing the addresses and accessible by the interfacing controllers, etc . could be provided throughout the packet data network, which databases are kept updated with each mobile station's current packet data network address.
  • Each network node, interfacing controller and/or base station could also have a local data cache in which it stores the addresses of mobile stations that have recently communicated through it or its associated base station (s) .
  • a mobile station's packet data network address is preferably changed appropriately as the mobile station moves between base stations of the radio system in use (e.g. to an address at or associated with the new network node (e.g. interfacing controller) to which the mobile station's new serving base station is connected). This allows data packets always to be routed efficiently to the current network node the mobile station is at.
  • the new network node e.g. interfacing controller
  • each mobile station is represented by an agent on the packet data network to which all communications in the packet data network intended for the mobile station can be sent and which agent carries out the interfacing and conversion between the communications protocol used over the air- interface and the packet data network communications protocol used for the packet data network fixed infrastructure.
  • the agent can thus be used to, effectively, provide and manage the link between the packet data network and its mobile station.
  • This packet data network "link" agent is, effectively, a projection of the mobile station on to the packet data network and appears, to the packet data network, to be the mobile station.
  • Each mobile station preferably has its own individual packet data network "link” agent.
  • packet data network ' agents ' is known (see, for example, Minar, M. , Kramar, K.H. , Maes, P. Cooperating Mobile agents for Dynamic Network Routing, MIT Media Lab, E15-302 20 Ames St., Cambridge MA 02139, USA.), and the mobile station agents can be arranged as would normally be the case for packet data network agents on the packet data network in question. Thus they will typically encapsulate a thread of execution along with a bundle of code and data, run independently of all other agents, be a self-contained program, be able to roam around the packet data network (i.e.
  • the agents are therefore effectively movable software capable of running at any suitable location in the packet data network that provide functions to facilitate communications between the packet data network and the mobile station which the agent represents .
  • the packet data network "link" agent representing a mobile station on the packet data network could be treated as a mobile host as used in the Mobile IP protocol (see, for example, Perkins, C.E., Mobile IP - Design Principles and Practices, Addison Wesley, 1998, ISBN 0-201-63469-4) .
  • the mobile "link” agent would be effectively considered as a migrating IP unit and therefore be allocated corresponding Mobile IP Agents.
  • a method of operating a mobile radio communications system in which system communication between mobile stations and base stations of the system is carried out using a mobile radio system communications protocol, and the fixed radio network infrastructure connecting the base stations of the system comprises a packet data network which uses a packet data communications protocol, the method comprising: representing each mobile station on the packet data network by means of an agent on the packet data network to which all packet data network communications intended for the mobile station can be sent, and which agent is operable to interface between the radio system communications protocol used for communication between mobile stations and base stations of the system and the packet data communications protocol used within the fixed network.
  • a radio network infrastructure for connecting base stations of a mobile radio communications system, comprising: a packet data network which uses a packet data communications protocol; means for creating and storing agents on the packet data network for representing mobile stations on the packet data network and for interfacing between a radio system communications protocol used for communication between mobile stations and base stations of the system and the packet data communications protocol used within the network; and means for sending all packet data network communications intended for a mobile station to that mobile station's packet data network agent.
  • the mobile station packet data network representative agents are preferably able to carry out, preferably all, functions necessary to interface between the mobile station and the packet data network and most preferably carry whatever information is necessary to allow the packet data network to communicate with their respective mobile station.
  • each packet data network "link” agent is preferably able to convert radio network addresses into packet data network addresses, and preferably carries its corresponding mobile station's radio system protocol address, so that, for example, when a message arrives from the packet data network addressed to the mobile station's packet data network representative agent, the agent can readdress the message for transmission to the mobile station.
  • the agents are preferably also able to convert packet data network communications for the mobile station into the radio system communications protocol and, preferably, vice-versa. Thus they can preferably take data from the radio link and insert it into individually addressed packets and post them on the packet data network. They are preferably also able to cause the fixed network (i.e. base stations) to transmit messages, data, etc., that they receive to their mobile station.
  • the link agent if a circuit mode call is in progress, the link agent preferably strips off the packet data protocol headers and tails of the packets addressed to itself that it receives, and places the content into transmission timeslots on the radio interface. If packet data is being communicated over the air interface, the link agent preferably obtains radio timeslots for its mobile station and places entire packets in the time slots.
  • Each mobile station's packet data network "link" agent preferably also carries other data relating to its mobile station's operation and requirements. This can include, for example, data defining the permissions and privileges of the mobile station (e.g. what type of calls it can make and what priority it can use) .
  • the link agent could also store some quality of service information indicating the current or recent average air interface bit error rate. This could be used, for example, to agree a quality contract with another correspondent for a particular connection - e.g. it would allow an appropriate slot rate and channel protection level to be determined for a video connection.
  • the link agent preferably also stores the IP addresses of any data terminals connected to the mobile station, and also preferably maintains call timers, etc.
  • the packet data network link agents can also carry out, preferably all, call set-up and registration functions for their mobile station.
  • they can preferably, for example, establish the availability of a desired correspondent for a circuit mode call, by, for example, exchanging messages with the other party's link agent.
  • the packet data network agent can perform these functions by for example, making use of basic services provided by a base site controller of the radio system for accessing the base station functions, and by interrogating data stores elsewhere on the packet data network by making use of packet data communication facilities.
  • a mobile station's packet data network agent will present a packet data network address representing the mobile station to the packet data network and receive messages from the packet data network for the mobile station.
  • the agent will know the correct translation into the mobile station's radio communications protocol address, and act to pass the re-addressed information on to the mobile station by invoking the functions of the appropriate base station of the network to cause it to transmit the information to the mobile station (using the mobile station's true air-interface address).
  • the mobile stations' packet data network agents should each have an appropriate packet data network address (which will typically effectively be the mobile station's packet data network address).
  • the mobile station's packet data network "link" agent would assume the IP address notionally assigned to the mobile station.
  • the link agent could assume the address of the network node in which it currently resides.
  • These addresses may be arranged, selected and stored as discussed above for the mobile station's packet data network addresses.
  • the packet data network agents could have Internet Protocol addresses, or port numbers at a particular Internet Protocol address (which would typically be the address of the relevant base station or base station controller, i.e. the address of the computer which currently hosts the agent) .
  • a mobile station's agent is preferably located at, and, preferably, where appropriate, has a packet data network address associated with, the packet data network node connecting to the mobile station's serving base station.
  • a packet data network address associated with, the packet data network node connecting to the mobile station's serving base station.
  • the packet data network agents for the mobile stations can be created as necessary by the system.
  • an agent is preferably created when a mobile station first communicates with a given base station.
  • the agent can be created where desired in the packet data network. It is, for example, preferably created in and by the base station interfacing controller associated with the base station with which the mobile station is communicating.
  • the packet data network representative agent of a mobile station preferably moves within the packet data network (and, where appropriate, changes its network address as it moves) as a mobile station moves between base stations of the radio system in use. This facilitates more rapid communication with a mobile station as it moves around the radio system.
  • the mobile station's packet data network agent is preferably transferred to a network location (e.g. an interfacing controller) associated with the new base station.
  • a network location e.g. an interfacing controller
  • the packet data network agents preferably move themselves and their associated data around the packet data network as their respective mobile stations move around the network.
  • the transfer of a packet data network agent to a new location could be achieved by creating a new agent at the new location (e.g. in the new base station's interfacing controller) .
  • a new packet data network agent is preferably created at the network location (e.g. interfacing controller) of the new base station.
  • the new agent may be created anew at the new network location, or the existing packet data network agent could copy itself or move its program code (and data, etc.) to the network location for the new base station (e.g. as part of the handover process) .
  • the new agent should be given the complete state of the old agent, except for any essential differences relating to, for example, the new location (e.g. its packet data network address (location) may have changed to one associated with the new base station), etc.
  • the mobile station's original agent used for the previous base station is left in operation for a limited period of time (e.g. 60 seconds) after the new agent is created, so that it can forward any already transmitted data packets that arrive after the change of base station to the new agent.
  • the existing agent therefore preferably notes the packet data network address of the new agent so that it can send data packets directly to the address of the new agent and, for example, avoid having to seek the new agent's address from elsewhere in the system.
  • each mobile station has two packet data network agents allocated to it, a 'home' packet data network agent having an effectively fixed packet data network address, and the above packet data network "link" agent associated with the base station currently serving the mobile station.
  • the home agent remains at the same 'home' location and packet data network address in the packet data network, but the link agent moves and changes addresses within the packet data network as the mobile station moves between base stations of the radio system.
  • the home agent serves as a default location for routing communications for the mobile station to when the address of the link agent is not known.
  • the home agent therefore preferably keeps track of and stores the mobile station's present packet data network 'location', by keeping an up-to-date record of the current location of the mobile station's link agent.
  • the fixed network preferably therefore updates a mobile station's home agent with the new location (address) of its link agent whenever the link agent moves locations in the fixed network.
  • the home agent could, for example, be a Mobile IP Home Agent, where Mobile IP is being used.
  • a message i.e. data packets
  • the address of the mobile station's home agent can be retrieved, and then the message either forwarded to the home agent (in which case the mobile station's packet data network home agent should be arranged to forward any messages it receives for the mobile station to the mobile station's link agent), or the address of the mobile station's link agent retrieved from the home agent and the message then forwarded to the mobile station's link agent.
  • the link agent should then forward it to the mobile station. (Where Mobile IP is being used, there may be no need to retrieve the Home Agent's address, because messages sent to the Mobile Station's IP address appear on the subnet to which the Home Agent is connected, and the Home Agent will recognize the address and collect and forward the packets.)
  • the packet data network link agent should know and store the home agent's address. Thus, when the mobile link agent already exists but is recreated at a new base site, it should retrieve its state table from the previous copy of the mobile link agent, and will therefore automatically obtain the address of its home agent, since the home agent address is known by the mobile link agent as part of its state table. However, when the mobile station is switched on and registers, the mobile station's link agent is newly created and only knows the mobile station's radio network address. In this case the link agent can examine a data base to discover the mobile station's IP address and home agent address. It can then also obtain any permissions, information, etc., about the mobile station from the home agent, if desired.
  • the link agent could determine the mobile station's home agent's network address, for example, by accessing a centralised store of mobile -station home agent addresses (although a local data cache that stores home agent addresses of recent visitors to the base station could also be provided to allow quicker retrieval of home agent details for mobile stations that have recently communicated via the base station) .
  • the link agent preferably then advises the home agent of its existence or of its new address (e.g. base station controller's IP address and a port number), e.g. so that the home agent can send any data packets addressed to the mobile station to the new link agent's location.
  • a mobile station can also be allocated an associated Mobile IP Foreign Agent, as well as a Mobile IP Home Agent and its packet data network "link" agent.
  • the mobile link agent could at each new base station make its presence known to the local Foreign Agent and the address of the new Foreign Agent would be forwarded to the Home Agent, so that the link agent can receive packets, which would be sent to it via the Foreign Agent (which it would share with other roamed mobile stations currently using that network node) .
  • the Foreign Agent would act to forward messages to the mobile station's link agent, which link agent would then manage the communication from the IP network to the mobile station via the radio protocols . It would be possible for a mobile station to be known by multiple packet data network (IP) addresses, thus allowing it to possess multiple applications. In this case it would be necessary to allow the mobile station's packet data network link agent to use any of these addresses, as appropriate. Each address would also have to be registered separately with the home agent or home agents (for example a mobile internet application could connect through the mobile station which has an entirely different IP address) . It would in this case be necessary for the single network link agent to handle both sets of communication, to avoid complications over which application gets the air-interface time.
  • IP packet data network
  • the mobile station's link agent When the mobile station moves to a new base site, the mobile station's link agent would have to update the two (or more) home agents with its new location (or, where Mobile IP Foreign Agents are being used, with the new local Foreign Agent; in this case it would also have to present itself to the Foreign Agent twice (or more) , once for each address) .
  • the packet data network (and preferably the mobile station's packet data network link agent, where used) is arranged to store data packets (e.g. up to some predetermined time or data limit) which cannot be immediately passed on to a mobile station (e.g. because the mobile station is temporarily out of contact with the fixed radio network (which may occur relatively frequently given the relatively unreliable connection between the network and the mobile station via the air-interface) ) , for subsequent transmission to the mobile station.
  • data packets e.g. up to some predetermined time or data limit
  • call control and mobile station mobility management can be handled as desired in the fixed network. For example, they could be handled by a single control means in the fixed network. However, they are preferably handled by plural control means distributed throughout the network, e.g. preferably by the interfacing controllers of the network. Using plural distributed controllers to handle these decisions is believed to provide increased speed and better scalability.
  • the mobile stations' packet data network agents, where used, could also handle some or all of these decisions.
  • the methods in accordance with the present invention may be implemented at least partially using software e.g. computer programs. It will thus be seen that when viewed from further aspects the present invention provides computer software specifically adapted to carry out the methods hereinabove described when installed on data processing means, and a computer program element comprising computer software code portions for performing the methods hereinabove described when the program element is run on a computer.
  • the invention also extends to a computer software carrier comprising such software which when used to operate a radio system comprising a digital computer causes in conjunction with said computer said system to carry out the steps of the method of the present invention.
  • a computer software carrier could be a physical storage medium such as a ROM chip, CD ROM or disk, or could be a signal such as an electronic signal over wires, an optical signal or a radio signal such as to a satellite or the like.
  • FIG. 1 is a schematic diagram of a mobile radio communications system in accordance with the present invention.
  • FIG. 2 is a schematic diagram of two base station controllers in accordance with the present invention.
  • the present embodiment relates to a mobile radio communications system which uses a standard mobile radio system air-interface communications protocol, such as the GSM standard (see, e.g. Mouly, M. , Paulet, M, The GSM System for Mobile Communications, Cell & Sys . , 4 rue Elisee Reclus, F-91120 Palaiseau, France, 1992, IBSN 2-9507190-0-7), or the TETRA standard (see, e.g.
  • GSM Global System for Mobile Communications
  • Cell & Sys . 4 rue Elisee Reclus, F-91120 Palaiseau, France, 1992, IBSN 2-9507190-0-7
  • TETRA see, e.g.
  • TETRA Terrestrial Trunked Radio
  • V+D Voice plus DATA
  • AI Air Interface
  • ETS 300 392-2 European Telecommunications Standards Institute, F-06921 Sophia Antipolis, CEDEX - FRANCE
  • a packet data network fixed infrastructure which uses a packet data communications protocol, such as an Internet Protocol based system, such as UDP, rather than being interconnected in the traditional fashion, using circuit switches .
  • UDP Internet Protocol based system
  • each mobile station is represented on the packet data network by a packet data network software "link" 'agent', which agent will move with the mobile station when it moves to a new base station, and represents its respective mobile station to the packet data network.
  • the mobile station's link agent acts as the link between the mobile station and the packet data network. It converts between the radio system's communications protocol and the packet data network's communications protocol, and converts between the radio system's addresses and the packet data network's addresses, for its mobile station, appropriately.
  • messages such as
  • the base station controller should also determine the mobile station's home agent's address, e.g. by making an enquiry to a server containing an address database, or by examining a local cache of recent visitor details.
  • the link agent would then immediately register with the mobile station's home agent .
  • the base station controller could obtain the home address of the mobile station, and its home agent by checking its local cache, or a central database, against the mobile station's radio identity, using its own (Base Station Controller's) address for the reply address. It would then create the new mobile link agent, and furnish it with these two items of information, and also its (the base station controller's) address as the address of the Foreign Agent (if it is using Mobile IP Foreign Agents - alternatively, the mobile link agent could discover the
  • the base station controller could provide the mobile link agent with the base station controller's address plus a reserved port number.
  • the mobile agent can now find the home agent itself by checking the local cache and a central data base .
  • a link agent copies itself across to the base site controller for the new base station as part of the handover process (or it may be created from existing code at the new base station controller) .
  • the new link agent is given the complete state of the old link agent, except that its packet data network address may be changed to one that is appropriate to the new base station's controller.
  • the new link agent will then register with the mobile station's home agent, so that all new incoming data packets can be forwarded to the new link agent address.
  • the link agents are effectively movable software that move themselves and their data around the packet data network as their respective mobile stations move around the network.
  • Figure 1 shows schematically a mobile radio system in accordance with the present invention.
  • the system includes a number of radio base stations 2, 3, 4, 5, 6, 16, 26 and 28, each connected to a radio antenna 7, 34, 8, 17, 27 and 29. It also includes plural mobile stations, two of which, mobile stations 1 and 18, in radio communication with base stations 2 and 16, respectively, are shown.
  • the base stations of the fixed radio network are interconnected by ethernet buses 12, 14, and routers are used to interconnect separate networks (e.g. routers 13 and 19) or to connect a network to a serial link (for example router 23 interconnects ethernet 14 to PSTN gateway 20 via a serial link - where an external network link is present, the external network could have controllers and/or "agents" for interfacing between the packet data network and the external network as appropriate).
  • Data, etc. is communicated around the fixed network using any suitable packet data routing method. (See, for example, Stevens, W. Richard, "TCP/IP Illustrated, Volume 1 - The Protocols " , Addison Wesley, 1994, ISBN 0-201-63346-9) .
  • the packet data network also includes a home location database server 25 which keeps records of the mobile station's home agent's addresses.
  • Each base station has an associated base site interfacing controller 9, 10, 11, 15, 22, 24, which carries out the usual base station control functions, but also houses or hosts the home and link agents of mobile stations and thus acts to interface and convert
  • the calling mobile link agent can, if desired, first check if the called party's mobile link agent happens to be present at the location before sending data packets all around the network - a base station controller data cache could be checked for this information.
  • Each base site controller also includes a data cache for storing, e.g. link and home agent addresses of mobile stations that have recently communicated through its associated base station (s) .
  • the base site controllers also handle all decisions concerning registration of mobile stations to base sites, call requests and handover requests (i.e. call control and mobility management) , as using distributed base site controllers to handle these functions is believed to provide benefits of speed and scalability when the methods of the present invention are employed.
  • call control and mobility management i.e. call control and mobility management
  • base site controller 9 is associated with a single base station, base station 2, but base site controller 11 is associated with plural base stations 4, 5 and 6.
  • FIG. 2 gives a more detailed view of the base station and base site controller arrangement.
  • Radio messages from a mobile station are received by base site antenna 7, and travel through RF feeder 42 into radio base station 2.
  • the TETRA air- interface protocol is in use, and the messages are interpreted in TETRA protocol stack 41.
  • Other air- interface protocols such as the GSM (Global System for Mobile Communications) protocol, could equally be used.
  • GSM Global System for Mobile Communications
  • the protocol stack implementation could also be split between the radio base station and the base site controller, or entirely installed in the base site controller.
  • the base station 2 may be connected to its associated base site controller 9 by any suitable means such as by a serial connection using a well known protocol such as SLIP (Serial Line IP) or PPP (Point to Point Protocol) .
  • SLIP Serial Line IP
  • PPP Point to Point Protocol
  • TETRA messages and user data are then sent via PPP protocol stack 39 (for example) and serial link 38 to be received at the base site controller 9 in PPP stack 37, using any suitable known method.
  • Each base site controller contains a software or logic module 36 which can support the execution of identical software procedures in multithreaded operation, such that they appear to execute independently and simultaneously, each at a different point in its sequence of operations.
  • This module handles call control and mobility management, and stores the packet data network link agents of the mobile stations, as appropriate.
  • Each base site controller can accommodate a number of concurrently running home agents and visiting link agents.
  • base site controller 9 includes in its software module 36 one or more software 'agents' representative of mobile stations which are communicating via the base station 2, including a link agent 33 which corresponds to mobile station 1.
  • the home and link agents for each mobile station are given as their packet data network addresses port numbers (e.g. a TCP/UDP port number) at the packet data network (IP) address of the relevant base site controller.
  • IP packet data network
  • each mobile station would have a link agent, which link agent attaches to a particular port number in the base station controller associated with the base station currently serving the mobile station and is assigned a port number on the visited base station controller for the duration of its visit, and a home agent attached, for example, to a port on the mobile station's home base station controller.
  • Each agent in effect manages a packet data (IP) network port on behalf of its mobile station.
  • Mobile station 1 has radio identity '123456', and has a home agent 32 at base site controller 22, with packet data network (IP) address 128.8.120.04 and port number 6196, will be considered.
  • Base site controller 9 has packet data network address 128.8.128.56.
  • Base site controller 9 examines its data cache records but is unable to find an entry for mobile station 123456. It therefore sends an enquiry to the home location database server 25 of the packet data network, and obtains responses of IP address 128.8.120.04 and port number 6196, for the mobile station l's home agent.
  • the base site controller 9 now creates a new link agent 33 to act on behalf of mobile station 123456, using port number 3657, and provides it with 128.8.120.04 port 6196 as the home agent's address and 128.8.128.56 port 3657 as the link agent's address.
  • the newly created link agent 33 sends a registration message to the home agent at address
  • the base site controller may attempt to authenticate the mobile station, using, e.g., the services of an authentication server connected somewhere on the packet data network (not shown in Figure 1) . If the authentication fails, the mobile station's link agent is deleted.
  • link agent 30 (which is in base site controller 15) receives a request to call mobile station 123456, and obtains the equivalent packet data network home agent address either from a local data cache (if it has called mobile station 1 recently, for example) , or by a request to home location database server 25. It then sends the call request to network address 128.8.120.04 port 6196.
  • Home agent 32 of mobile station 1 at base site controller 22 collects the call request and forwards it to mobile station l's link agent 33 at address 128.8.128.56, port 3657 (i.e. at base site controller 9) .
  • Base site controller 9 forwards the call request message to mobile station l's link agent 33 at port 3657.
  • the link agent 33 endeavours to reserve the resources required to make the call, and ascertain the availability of mobile station 1 by calling on the radio protocol services provided by the base station controller. If a call is possible, it sends a call acceptance message to the link agent of mobile station 18, via mobile station 18 ' s home agent, if necessary. When the call acceptance is received by mobile station 18 's link agent 30, link agent 30 completes the call connection (in conjunction with mobile station 18) .
  • mobile station 1 decides that it needs to move on to radio base station 3 in the middle of its call. It requests the handover, and its link agent 33 sends a complete copy of its own state table to base site controller 10. (It could also send a copy of the agent code, but it may be more efficient to just transmit the state table and execute code pre-stored in the base site controller.)
  • Base site controller 10 creates a copy 31 of mobile station l's link agent, but gives it the new address 128.8.128.57, port 2249. The new mobile link agent 31 should then register its location with the home agent 32 at 128.8.120.04 port 6196.
  • Old link agent 33 at base site controller 9 preferably remains active for about 60 seconds to redirect any late data packets. It then terminates itself.
  • the packet data network link agents representing the mobile stations on the packet data network could be given their own full packet data network (e.g. Internet Protocol) addresses. Where the Internet Protocol is used, the addresses could be full 8-bit number addresses, and/or subnet addresses.
  • Internet Protocol Internet Protocol
  • the mobile stations' packet data network link agents would take the appearance of mobile nodes as used in the Mobile IP protocol (see, for example, Perkins, C.E., Mobile IP - Design Principles and Practices, Addison Wesley, 1998, ISBN 0-201-63469-4) .
  • each mobile station's link agent would be considered as a migrating IP unit, and a Mobile IP Foreign Agent could provide a 'care-of ' address for the migrated unit.
  • the Mobile IP Home Agent would be connected to the migrating unit's (mobile station's) home subnet and would forward any data packets sent to the mobile station to .the foreign agent (by packing them inside data packets addressed to the Foreign Agent) .
  • the Foreign Agent would unpack any data packets it receives and send them on to the mobile station's mobile link agent which would examine the data and determine if it is signalling information or user data.
  • the link agent would repackage user data and ask the base site controller to transmit it to the mobile radio unit.
  • the link agent would use signalling information to connect or modify calls, reserve radio resources or provide information, etc.
  • mobile station 1 in Figure 1 has radio identity '123456'.
  • mobile station 1 also has a home IP network address of '128.8.120.143, and a Home Agent 32 at base site controller 22, with IP address 128.8.120.04.
  • base site controller 9 has IP address 128.8.128.56.
  • base station controller 9 When mobile station 1 is switched on when in range of base station 2, it will send a registration request to radio base station 2, using its identity 123456. This is passed straight to base site controller 9 via the serial connection. As before, base site controller 9 examines its cache records but is unable to find an entry for mobile station 123456. It therefore sends an enquiry to the home location database server 25, and obtains responses 128.8.120.143 for the mobile station's IP address, and 128.8.120.04 as the mobile station l's Home Agent's address.
  • the base site controller 9 now creates a new link agent 33 to act on behalf of mobile station 123456, giving it IP address 128.8.120.143, and provides it with 128.8.120.04 as the mobile station's Home Agent's address and 128.8.128.56 as the mobile station ' s Foreign Agent ' s address .
  • the link agent 33 sends a registration message to the Home Agent 128.8.120.04, quoting 128.8.128.56 as its current Foreign Agent.
  • the base site controller may attempt to authenticate the mobile station, using the services of an authentication server connected somewhere on the IP network (not shown in Figure 1) . If the authentication fails, the link agent is deleted.
  • link agent 30 (which is in base site controller 15) will receive a request to call mobile station 123456, and obtains the equivalent IP address either from a local cache (if it has called mobile station 1 recently, for example) , or by a request to home location server 25. It sends the call request to IP address 128.8.120.143. The request is collected by the Home Agent 32 at base site controller 22, and tunnelled to address 128.8.128.56 (by packing the data packets inside data packets addressed to address
  • the Foreign Agent resident in base site controller 9 forwards the call request message to mobile station l's link agent 33, which endeavours to reserve the resources required to make the call, and ascertain the availability of mobile station 1. If a call is possible, link agent 33 sends a call acceptance message to the IP address of mobile station 18. If mobile station 18 is away from home, this message will go via mobile station 18' s Home Agent (not shown) and the Foreign Agent at base site controller 15 and mobile station 18 ' s link agent 30. When the call acceptance is received by mobile station 18 's link agent 30, its link agent 30 completes the call connection (in conjunction with mobile station 18) .
  • the network or routers deliver all 128.8.120.143 packets to the ethernet subnet corresponding to this address.
  • the Home Agent on host 128.8.120.04 is connected to this subnet, and sees these packets. It collects all packets addressed to host 128.8.120.143 and sends each inside a larger packet addressed to the Foreign Agent at 128.8.128.56 (often referred to as "tunnelling" , as is known in the art) .
  • the Foreign Agent unpacks one of these packets it finds inside a packet addressed to 128.8.120.143. By checking its data base, it discovers that this is the address of a mobile station link agent executing on its own hardware, and passes the packet on to the link agent .
  • mobile station 1 decides that it needs to move on to radio base station 3 in the middle of its call. It requests the handover, and its link agent 33, as before, sends a complete copy of its own state table to base site controller 10.
  • Base site controller creates a copy 31 of the link agent, and gives it a new address 128.8.128.57.
  • the new link agent 31 registers its location with the Home Agent 32 at 128.8.120.04, and speech data packets from mobile station 18 are routed to the new base site controller 10 by the Home Agent 32.
  • link agent 33 at base site controller 9 may remain active for about 60 seconds to redirect any late packets and then terminate itself.
  • the present invention provides a mobile radio communications system that permits the use of relatively inexpensive, flexible and readily available packet data (e.g. IP) protocol hardware and software to interconnect base stations of the radio system, using standard packet data (e.g. IP) protocols to provide mobility management and manage the routing of data packets to a mobile station through the packet data network.
  • packet data e.g. IP
  • IP packet data
  • standard radio terminal units that have no knowledge of packet data protocols may be used in the system, and the packet data network needs no knowledge of the radio system's radio protocols.

Landscapes

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

Abstract

L'invention concerne un système radio mobile comprenant plusieurs stations de base radio (2, 3, 4, 5, 6, 16, 26 et 28), connectée chacune à une antenne radio (7, 34, 8, 17, 27 et 29). Ledit système comprend également des stations mobiles multiples, telles que des stations mobiles (1 et 18), qui sont en radiocommunication respectivement avec des stations de base (2 et 16). Les stations de base du réseau de radio fixe sont interconnectées par des bus Ethernet (12, 14). Des données, entre autres, sont communiquées autour du réseau fixe au moyen de tout procédé d'acheminement de paquets de données approprié. Chaque station de base possède une commande (9, 10, 11, 15, 22, 24) d'interface de site de base correspondante, qui réalise les fonctions usuelles de commande de station de base, mais qui accueille également des agents de réseau de paquets de données qui représentent les stations mobiles sur le réseau de paquets de données et qui assurent l'interface et la conversion entre le protocole de communication du système radio utilisé entre les stations mobiles et les stations de base, et le protocole de communications de réseau de paquets de donnés utilisé dans le réseau de paquets de données fixe.
PCT/GB2001/001434 2000-03-28 2001-03-28 Infrastructure de radiocommunications utilisant un protocole de communication par paquets WO2001074099A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU42637/01A AU4263701A (en) 2000-03-28 2001-03-28 Radio communications infrastructure using a packet communication protocol
EP01915552A EP1183886A1 (fr) 2000-03-28 2001-03-28 Infrastructure de radiocommunications utilisant un protocole de communication par paquets

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0007518A GB0007518D0 (en) 2000-03-28 2000-03-28 Mobile radio communications system
GB0007518.4 2000-03-28

Publications (1)

Publication Number Publication Date
WO2001074099A1 true WO2001074099A1 (fr) 2001-10-04

Family

ID=9888592

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2001/001434 WO2001074099A1 (fr) 2000-03-28 2001-03-28 Infrastructure de radiocommunications utilisant un protocole de communication par paquets

Country Status (4)

Country Link
EP (1) EP1183886A1 (fr)
AU (1) AU4263701A (fr)
GB (2) GB0007518D0 (fr)
WO (1) WO2001074099A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0910198A2 (fr) * 1997-10-14 1999-04-21 Lucent Technologies Inc. Système de gestion de mobilité
WO2000011849A1 (fr) * 1998-08-20 2000-03-02 Nokia Networks Oy Procede et appareil assurant un multiplexage utilisateur dans un protocole en temps reel -

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB8910085D0 (en) * 1989-05-03 1989-06-21 British Telecomm Mobile communications system
GB9206209D0 (en) * 1992-03-21 1992-05-06 Roke Manor Research Improvements in or relating to mobile radio network
SE9304119D0 (sv) * 1993-12-10 1993-12-10 Ericsson Ge Mobile Communicat Apparatuses and mobile stations for providing packet data communication in digital TDMA cellular systems
FI94700C (fi) * 1994-01-21 1995-10-10 Nokia Telecommunications Oy Matkaviestinjärjestelmän verkkoelementti ja menetelmä pakettimuotoista datasiirtoa varten matkaviestinjärjestelmässä
FI980024A (fi) * 1998-01-07 1999-07-08 Nokia Networks Oy Solukkoradiojärjestelmä ja menetelmä tukiaseman yhdistämiseksi solukko radiojärjestelmään

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0910198A2 (fr) * 1997-10-14 1999-04-21 Lucent Technologies Inc. Système de gestion de mobilité
WO2000011849A1 (fr) * 1998-08-20 2000-03-02 Nokia Networks Oy Procede et appareil assurant un multiplexage utilisateur dans un protocole en temps reel -

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PERKINS C E: "MOBILE IP", IEEE COMMUNICATIONS MAGAZINE, IEEE SERVICE CENTER. PISCATAWAY, N.J, US, vol. 35, no. 5, 1 May 1997 (1997-05-01), pages 84 - 86,91-99, XP000657114, ISSN: 0163-6804 *

Also Published As

Publication number Publication date
GB0107765D0 (en) 2001-05-16
GB0007518D0 (en) 2000-05-17
EP1183886A1 (fr) 2002-03-06
AU4263701A (en) 2001-10-08
GB2360913A (en) 2001-10-03

Similar Documents

Publication Publication Date Title
JP4023631B2 (ja) コンパティブルでない移動ネットワーク内でローミングする移動局とのパケットデータ通信
US6496704B2 (en) Systems and methods for internetworking data networks having mobility management functions
EP1677482B1 (fr) Système de distribution de paquets, dispositif d'enregistrement pour un PAN, dispositif de commande pour un PAN, dispositif de transfert de paquets, et procédé de distribution de paquets
CN103856995B (zh) 用于移动性管理的伪线
CN1714558B (zh) 支持端口标识的移动ip注册
JP4615172B2 (ja) セル方式通信システム
JP3927625B2 (ja) 統合無線通信システムと通信方法
EP0804844B1 (fr) Systeme et procedes de radiocommunications par paquets, permettant d'acheminer de fa on independante d'un protocole un paquet de donnees dans des reseaux de radiocommunications par paquets
FI112897B (fi) Menetelmä tiedonsiirtoverkossa ja tiedonsiirtolaite
US6501746B1 (en) Mobile IP dynamic home address resolution
JP3910632B2 (ja) 遠距離通信システム内の遠距離通信ネットワーク範囲を拡大するための方法ならびに構成
EP1206098B1 (fr) Home agent et méthode de transfert de paquet IP
CN101218814B (zh) 用于优化移动vpn通信的方法和装置
JP3182059B2 (ja) 移動無線パケットデータ通信システムにおける交換局間キャリアへの均等アクセス
US6822971B1 (en) Apparatus, and association method, for identifying data with an address
JP2004536503A (ja) 異種ネットワーク中のモバイルｉｐノードのための方法及びシステム
JP2006505154A (ja) モバイルｉｐの動的ホームエージェント割当ての方法及び装置
EP1221820A3 (fr) Agencement de connexions de données par paquèts dans un système bureautique
EP1552635B1 (fr) Enregistreur mobile
WO1999052236A1 (fr) Dispositif et procede de communication sans fil de donnees en paquets
EP1445898B1 (fr) Système de contrôle de communication mobile
US7613811B1 (en) Selecting a communications protocol
JP3524999B2 (ja) 異種ネットワーク間相互接続におけるアドレス解決装置
US20020039358A1 (en) Method for separating and processing signal and bearer in all IP radio access network
WO2001074099A1 (fr) Infrastructure de radiocommunications utilisant un protocole de communication par paquets

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

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

AL Designated countries for regional patents

Kind code of ref document: A1

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2001915552

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2001915552

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWW Wipo information: withdrawn in national office

Ref document number: 2001915552

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP