EP1277361B1 - Architecture et acheminement de paquets dans un reseau de type multisupport - Google Patents

Architecture et acheminement de paquets dans un reseau de type multisupport Download PDF

Info

Publication number
EP1277361B1
EP1277361B1 EP01921412A EP01921412A EP1277361B1 EP 1277361 B1 EP1277361 B1 EP 1277361B1 EP 01921412 A EP01921412 A EP 01921412A EP 01921412 A EP01921412 A EP 01921412A EP 1277361 B1 EP1277361 B1 EP 1277361B1
Authority
EP
European Patent Office
Prior art keywords
mobile node
network
node
dxb
mbn
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP01921412A
Other languages
German (de)
English (en)
Other versions
EP1277361A1 (fr
Inventor
Lin Xu
Toni Paila
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Siemens Networks Oy
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 Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to EP07112040A priority Critical patent/EP1838114B1/fr
Publication of EP1277361A1 publication Critical patent/EP1277361A1/fr
Application granted granted Critical
Publication of EP1277361B1 publication Critical patent/EP1277361B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes
    • 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]
    • 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/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • 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/14—Backbone network devices

Definitions

  • a multi-bearer network is a network having the capability to carry a data packet via one of several alternative bearers.
  • the term "multi-bearer network” should be interpreted as meaning "multi-bearer-type network", or in other words, a network arrangement which provides multiple different bearer types for data packet delivery.
  • An example of an MBN is a concept known as MEMO (Multimedia Environment for Mobiles), see reference 1- Additionally, the MBN supports mobility of a subscriber terminal.
  • An example of terminal mobility is IP (Internet Protocol) mobility, which is the topic of standard RFC2002 and an internet Draft " Mobility Support in IPv6", by C. Perkins and D.
  • IPv6 Internet Protocol, Version 6 (IPv6) Specification
  • RFC-2373 IP Version 6 Addressing Architecture
  • a generic problem underlying the invention is that the MEMO concept is very limited. It only contemplates one uplink bearer type, namely GSM (Global System for Mobile Communication), and one downlink bearer type, namely DAB (Digital Audio Broadcast).
  • 'uplink' means from the mobile node MN to the correspondent node CN and 'downlink' means the inverse direction.
  • WO-A-99 31846 discloses a method for routing data to a mobile node, the method comprising maintaining reachability information on a mobile node, and setting a destination to which received data is to be sent if the mobile node is unreachable.
  • WO-A-99 31853 discloses a method for routing data to a mobile node, the method comprising determining locations of agent nodes, and transmitting successive data units from a stream of data units intended for the mobile node to different ones of the agent nodes. IP. It is advantageous to keep the volume of signalling messages as low as possible, and according to D3, this is achieved through a proxy known as care-taker (CT) keeping the mobile node informed of changes in the path messages of the on-going sessions.
  • CT care-taker
  • WO-A-00 45560 (prior art falling under Art. 54(3) EPC) describes a public mobile access data network in which a home agent/foreign agent model is used where the home and foreign agents transfer data packets over the network via a tunnel.
  • the home network addresses serve as IP addresses that are dynamically re-allocated to label-switched paths as the mobile node moves from one foreign agent to another.
  • EP-A-1 047 244 (prior art falling under Art. 54(3) EPC) discloses a method for configuring a QoS session between a mobile node and a correspondent node.
  • a source address of IP packets from the mobile node is modified to identify the mobile node's address in a foreign network.
  • the source address of the IP packets may be modified in the foreign network.
  • the source address may be further modified in the correspondent network to the mobile node's home address.
  • One of the specific problems is how to select an optimal bearer for each data packet in varying situations in an MBN. Data packets have different quality-of-service requirements. Situations may vary because the subscriber moves or the network load changes. Another specific problem is how to route the traffic to the mobile node via the selected bearer and to design suitable network elements and MBN architecture.
  • the object of the invention is to provide methods and equipment for solving the specific problem related to bearer selection in an MBN.
  • resource availability information concerning a downlink bearer network and subscriber preference information concerning a mobile node are received and maintained in a service support node set.
  • the service support node set also maintains traffic policy information concerning a multi-bearer network.
  • a routing table is generated on the basis of the subscriber preference information, the traffic policy information and the resource availability data, and the routing table is used for routing one or a few initial data packets of a new session from the correspondent node to the mobile node.
  • a binding update is performed between the mobile node and the correspondent node, and an address associated with the centralized traffic policy controller is stored as the mobile node's care-of address in its home agent.
  • An initial data packet is routed via the home agent and the centralized traffic policy controller to a bearer network interface unit serving the mobile node.
  • an address of the bearer network interface unit is stored as the mobile node's care-of address in the correspondent node.
  • subsequent data packets are routed directly from the correspondent node to the bearer network interface unit such that the subsequent data packets bypass the home agent and the centralized traffic policy controller.
  • the invention is based on a novel distribution of functions within an MBN.
  • the functions are distributed over four major nodes or node sets.
  • the MBN comprises a physical or virtual backbone network.
  • a second node set comprises a home registration unit (HRU) for storing subscriber registration and preference information, such as access right information.
  • HRU home registration unit
  • subscriber registration and preference information such as access right information.
  • HRU home registration unit
  • preference information such as access right information.
  • a subscriber may be a national subscriber and not pay for any roaming support. Another user may elect roaming support in major European cities. The available options depend entirely on the service providers.
  • the HAN node set also comprises an MBN home agent (MHA), which is a special version of a home agent. It supports a mobile node that uses an MBN-specified IP address as its home addresses. Each MN subscriber which is registered for MBN service has an entry in the HRU of the home network. An MBN serves its subscribers regardless of which IP address is used as the mobile node's home address for communicating with the correspondent node.
  • MHA MBN home agent
  • a key concept in the mobile-IP protocol is the home agent (HA).
  • the home agent is a routing entity in a mobile node's home network which tunnels packets for delivery to the mobile node when it is away from its home network, and maintains current location information for the mobile node.
  • the home agent per se is known to the skilled reader.
  • the invention is also partially based on the idea that the home agent function is supplemented with a home register unit (HRU) which is a separate entity from the home agent. Separating the home register unit from the home agent allows more freedom in positioning the home agent.
  • the home agent can be located virtually in any network, and the mobile node can use its own IP address instead of the one provided by the MBN.
  • a mobile node is allowed to use either an IP address provided by the MBN or an IP address provided by some other network. If the mobile node uses an MBN-provided IP address as its home address for communicating with its correspondent node, the MHA acts as the mobile node's home agent. If the MN uses an IP address provided by eg a corporate network, the home agent in that network is the mobile node's home agent.
  • a third node set called service support nodes (SSN) is in charge of centralized traffic policy control, mobility management and resource reservation decisions.
  • the SSN node set also controls starts of sessions and routes the first packet(s) of new sessions. Normally the SSN node set does not route subsequent packets of ongoing sessions. Instead, the mobile node updates its mobility binding with its correspondent node, after which the traffic bypasses the SSN nodes. For some reason, a mobile node may not want to send a mobility binding update message. In this case, the SSN nodes route all traffic to the mobile node.
  • the service support nodes comprise a traffic policy controller (TPC) within the backbone network. Later in this application, the traffic policy controller is frequently shortened to "traffic controller".
  • the traffic (policy) controller makes centralized routing policy decisions but does not route all packets itself. It only routes the first packet or the first few packets of a new session and helps other network elements to communicate directly with each other.
  • the SSN nodes also comprise a resource coordination unit (RCU) from which the TPC checks resource availability before making decisions about traffic allocation.
  • the traffic controller also requests the resource coordination unit to reserve resources for a flow when necessary (for guaranteed service).
  • the traffic controller selects a downlink bearer on the basis of traffic flow or/and traffic class.
  • the SSN node set also comprises a mobility management unit (MMU) which supports the mobile node in handovers within a TPC area and between two TPC areas.
  • MMU mobility management unit
  • the TPC, RCU and MMU are preferably closely coupled or within the same network element. This means that the mobile node is not burdened with addressing these functions separately. Instead, these functions share a common IP address, and the MN communicates with the TPC which distributes MN-originated information with the RCU and the MMU.
  • Each traffic policy controller has an area of responsibility. Such an area will be called a TPC area.
  • the TPC area comprises the cells broadcasting the TPC's IP address or other unique TPC identifier. Because the cell size varies and the cells are partially overlapping, the TPC area has no clearly-defined geographical border, and a mobile node may be located geographically in two or more neighbouring TPC areas simultaneously. However, the mobile node can be registered with (ie reachable via) one TPC at any time. In such a situation, the mobile node selects the TPC controlling the cell with the best signal quality. Moreover, the area of a certain TPC is likely to be different between the various bearer networks. In other words, the TPC area for DVB is different from the TPC area for DAB.
  • a fourth node set acts as interfaces to the various bearer networks.
  • the primary function of the interface units is to encapsulate IP packets into protocols suitable for the bearer network in question, and to control incoming traffic to a bearer network or a broadcast cell.
  • the interface unit of a broadcast cell also monitors and controls the resource usage and reports resource availability to the SSN nodes.
  • Each interface unit (IU) toward the broadcast bearer networks comprises or is closely coupled to a resource management unit (RMU).
  • the RMU controls the physical resource allocation in each cell under it. It also acts as a peer entity of the resource coordination unit to respond to resource allocation requests. More specifically, the RCU makes decisions concerning resource allocation but the RMU maps each data flow to one or more physical or logical channels of the specific broadcast station.
  • the bearers include a first set of bidirectional bearers.
  • bidirectional bearers are circuit-switched mobile networks, such as GSM (Global System for Mobile communications), and packet-switched mobile networks, such as GPRS (General Packet Radio Service), and third generation mobile networks, such as UMTS (Universal Mobile Telecommunications System), which offer both circuit-switched and packet-switched bearers.
  • the bearers also include a second set of unidirectional bearers. Examples of unidirectional bearers are digital audio broadcast (DAB) and digital video broadcast (DVB).
  • DAB digital audio broadcast
  • DVD digital video broadcast
  • the set of unidirectional bearers can also be called broadcast bearers, and the set of bidirectional bearers can also be called non-broadcast bearers.
  • a multi-bearer network comprises a backbone network which is preferably based on IPv6 (Internet Protocol version 6) with mobility support.
  • the backbone network has border gateway nodes towards the Internet and interface units (IU) towards the various bearer networks.
  • the invention provides mobility support in an MBN in an elegant manner.
  • the mobile node and its correspondent node are not burdened with addressing each node or functionality separately.
  • the mobile node is only required to have some rights in one bidirectional (uplink) bearer network.
  • FIG. 1 is a block diagram illustrating an overall network architecture.
  • Reference sign MN denotes the mobile node.
  • Reference sign CN denotes the mobile node's correspondent node, which is a host or server the mobile node is communicating with.
  • the mobile node MN communicates with its correspondent node CN via a multi-bearer network MBN which offers several alternative bearers for a data packet DP.
  • the MBN comprises a physical or virtual backbone network (BB).
  • the mobile node MN is able to communicate with several bearer networks BN.
  • the bearer networks comprise at least one bidirectional bearer network (in this example: GSM, GPRS or UMTS) and at least one unidirectional or broadcast bearer network (in this example: DAB and DVB).
  • the DAB and DVB are commonly referred to as DxB.
  • the DxB networks are the principal bearers for downlink traffic.
  • the mobile node uses the bidirectional (uplink) bearers primarily for accessing the services of the MBN, although some bidirectional bearers, most notably the UMTS, can be used for downlink traffic with a moderately high speed.
  • the bearer networks are shown as distinct in Figure 1, but in reality they are geographically overlapping, and a mobile node may have access to all bearer networks at the same time.
  • the bearer networks BN per se are known to the skilled reader, and especially the bidirectional bearer networks can be largely treated as black boxes.
  • Each data packet DP comprises a header H and a payload part PL.
  • a data packet typically has several headers inside each other, because each protocol layer inserts its own header. However, each protocol layer only handles its own header, and a model with only one network layer header is usually sufficient for describing the invention.
  • the header indicates, directly or indirectly, a quality-of-service requirement QoS for the data packet.
  • An example of a direct QoS indication is a case where a data packet header includes a parameter which is or which can be directly mapped to a quality-of-service requirement parameter.
  • An example of an indirect QoS indication is a case where a (Transmission Control Protocol) data packet header indicates a port number which in turn indicates the QoS requirement.
  • 'quality of service' is a very generic term indicating certain requested or negotiated transmission characteristics, such as bit rate, maximum delay and/or packet loss probability.
  • quality of service is indicated by or mapped to one (or more) of the existing appropriate fields, such as the Traffic Class field of IPv6.
  • the term 'traffic class' is used to refer collectively to the fields which are used to indicate the quality-of-service requirement.
  • the MBN communicates with the CN via an IP Network IPN, such as the Internet or an intranet/extranet.
  • IP Network IPN such as the Internet or an intranet/extranet.
  • a border gateway node BG interfaces the MBN to the IP network IPN.
  • the border gateway BG is typically a simple (but sufficiently powerful) router which preferably includes a firewall function FW.
  • a backbone network BB combines the different bearer networks BN.
  • the backbone network may be the MBN operator's internal network.
  • a physical example of a backbone network is a highspeed local-area network or a wide-area network.
  • the backbone network BB is based on lPv6 (Internet Protocol version 6) or a later version, with mobility support.
  • the access control node set is implemented as an MBN authentication centre MAC, which provides centralized grant or denial of the mobile node's rights to services via the backbone network BB.
  • the MAC also stores subscriber preference information related to the mobile node.
  • a second node or node set supplements the mobile IP home agent function.
  • the HAN nodes comprise a home registration unit (HRU) for storing subscriber registration and preference information, such as access right information.
  • the HAN nodes also comprise an MBN home agent (MHA), which is a special version of the home agent. Separating the home register unit from the home agent allows more freedom in positioning the home agent.
  • the home agent can be located virtually in any network, and the mobile node can use its own IP address instead of the one provided by the MBN. Accordingly, in the example shown in Figure 1 the home agent HA of the mobile node MN is in the MN's corporate network CNW.
  • the home agent HA is a key concept in the mobile-IP protocol. For each mobile node, there is one home agent.
  • the home agent is a routing entity in a mobile node's home network which tunnels packets for delivery to the mobile node when it is away from its home network, and maintains current location information for the mobile node. It tunnels datagrams for delivery to, and detunnels datagrams from, a mobile node when the mobile node is away from its home network.
  • the home register unit HRU stores the user registration information, such as an Access Permission List (APL, see Figure 6) which indicates the MN's rights in each BN.
  • the HRU also stores the subscriber's preference information, which indicates what quality of service the subscriber requires from various applications (or for specific incoming traffic classes).
  • An example of such preference information is the QMTC table shown in Figure 4.
  • the HRU of a visiting MN may be located in a different MBN. In such a case, the HRU of the visited MBN may consult the HRU of the MN's home MBN. If the traffic handling policy of the MN's home network differs from the policy of the visited network, the HRU should adapt the preference information accordingly, such that the user receives the expected quality of service.
  • a third node set called SSN (service support nodes), provides centralized administration and distribution of traffic policies (see Figures 3 and 4).
  • the SSN node set combines the MN-specific subscriber preference information and operator-specific policy information into an MN-specific traffic handling policy which the SSN node set used to make decisions concerning cell and/or channel selection.
  • the MN-specific traffic handling policy is also distributed to the interface nodes which route the packets of ongoing sessions. It may route the first data packet(s) of new sessions but does not route subsequent data packets of ongoing sessions if the MN sends its updated mobility binding information to the CN.
  • the traffic control node set also supports centralized mobility management for managing the mobility of the mobile node within the downlink bearer networks DxB, and it makes centralized resource reservation decisions within the downlink bearer networks.
  • the SSN node set comprises a traffic (policy) controller TPC.
  • Each traffic controller comprises or is closely coupled to a resource coordination unit RCU and a mobility management unit MMU.
  • a fourth node set acts as interfaces to the bearer networks BN.
  • the IU nodes also carry out the resource reservation decisions in the downlink bearer networks DxB.
  • the interface units are labelled xx_IU, where 'xx' is the relevant bearer network.
  • the backbone network BB preferably has one (or more) interface unit towards each bearer network having inherent mobility support (GSM, GPRS and UMTS) and one interface unit towards each cell in a bearer network not having inherent mobility support (DxB).
  • Each DxB interface unit comprises or is closely coupled to a resource management unit (RMU).
  • RMU resource management unit
  • the mobile node MN must be able to communicate with several bearer networks BN. It implements IPv6 with mobility support. It monitors selected links (physical channels of DxB) for router advertisement messages. Thus it gains knowledge of the various routers within the MBN.
  • the MN has a unique MIN number (MBN interface number) for automatic care-of address configuration.
  • the MN is able to send an authentication message for registering with the backbone network BB via an interface unit IU of a bidirectional BN, the IU consequently forwarding the authentication request to the MBN authentication centre MAC.
  • the mobile node is able to initiate a binding update procedure for registering its own location information with its home agent HA and the correspondent node CN.
  • the mobile node is also able to edit its mapping from IP Quality of Service (QoS) to MBN Traffic Class (MBN_TC, see Figure 4).
  • QoS IP Quality of Service
  • MBN_TC MBN Traffic Class
  • An example of a QoS-to-MBN traffic class mapping is as follows. When users enter or update their subscriptions, they can select their QoS and MBN_TC mappings. The MBN operator can provide several mapping tables, each of which corresponds to a different price or tariff. The user selects one mapping table. Later on, the user may modify the mapping table (by calling the operator), access and modify its profile (eg via a web/wap browser or by using special software). Once the mapping is changed, the charging method will be changed accordingly.
  • the traffic controller TPC uses such mappings as a basis for determining the specific xx_IU unit via which a given kind of traffic is conveyed.
  • FIG. 2 illustrates a general addressing concept within the MBN.
  • IPv6 employs two types of care-of addresses (COA): a primary COA and a co-located COA. Because of the addressing structure of IPv6, there is usually no need to have separate foreign agents for mobility support (in contrast to IPv4), and the COAs are co-located COAs.
  • COA care-of addresses
  • a mobile node may have multiple COAs, and a single home agent may store more than one COA for one mobile node. But at any one time, only one COA is registered as the primary COA to which the home agent tunnels MN-terminated data.
  • the home agent HA knows the care-of address associated with the traffic controller TPC.
  • the mobile node's primary COA is the subnetwork prefix of the TPC plus the MN's MIN.
  • An advantage of this addressing scheme is that the TPC is able to see the MN's address and route the data to its final destination even if the HA encrypts MN-terminated tunnelled data.
  • the primary COA registered in the home agent is associated with the traffic policy controller TPC.
  • the COA's prefix is the TPC's subnetwork prefix and the last part is the mobile node's own MIN.
  • the TPC acts as a router for the traffic heading toward the COA.
  • the COA stored in the CN is associated with the relevant interface unit IU. This address allocation trick forces the traffic to be routed via the TPC during the start of a session, and allows traffic routing directly via the selected IU during the remainder of the session.
  • the MN and the CN may open a second session in parallel to the first session. The data packets of the parallel session may be routed directly to the MN via the IU if no resource reservation is needed.
  • the home agent HA maintains the primary COA 202 of the mobile node MN.
  • the primary COA 202 is the IP address 202 of the traffic controller TPC used by MN.
  • the HA may also store the IP address 204 of the MN within the subnetwork under the downlink interface unit currently used by the MN.
  • the traffic controller TPC maintains the IP address 208 of the downlink interface unit y_IU currently used by the MN and the IP address 206 of another downlink interface unit x_IU.
  • the downlink interface units in turn maintain the mobile node's COA (210 and 212) in each respective subnetwork.
  • the first packet is routed by using the addresses 202, 208 and 212.
  • subsequent packets are routed by using the mobile node's COA 214 within the subnetwork defined by the downlink interface unit y_IU.
  • FIG 3 shows an example of a traffic handling policy table THPT.
  • MBN_TC MBN Traffic Class
  • the THPT defines the traffic handling policy to be applied.
  • the THPT can be similar or different between different MBN networks.
  • Column ST indicates the service type of the traffic class.
  • service type is a generic term and not a name of a field in an IPv4 packet header.
  • BE best effort
  • GS guaranteed service
  • BW means bandwidth (measured by some appropriate and sufficient metrics)
  • IMP means importance. Low-importance data packets are discarded first if sufficient bandwidth is not available.
  • the column marked "other" can be used for example to implement policies with time dependant validity. This means that daytime priorities can be different from nighttime priorities.
  • This table is subscriber-specific and maps IPv6 traffic classes IP_TPC into MBN traffic classes MBN_TPC.
  • the traffic class in question is indicated by the packet's header.
  • ACAL Available Care-of Address List
  • SPx is the subnetwork prefix of subnetwork x
  • MIN is the MBN interface number for the mobile node.
  • the mobile node continuously measures signal strength (or some other signal quality parameter, such as the bit error ratio) of each available broadcast channel.
  • the mobility management unit MMU It sends the measurement results to the mobility management unit MMU, which maintains a list of channels having an acceptable signal quality. Then the MMU translates this list into a list of care-of addresses wherein each channel corresponds to a combination of the relevant subnetwork prefix and the mobile node's care-of address. Then the MMU arranges the ACAL list according to preference (signal quality) and sends the ACAL list to the traffic controller TPC. It is the traffic controller's responsibility to make the final decision concerning the care-of address to be used. Three example situations illustrate the decision-making process.
  • the mobile node In a first situation, the mobile node is powered on but does not receive data from any CN.
  • the packet When the first packet arrives from a CN, the packet is tunnelled by the HA to the MN's COA associated with the TPC.
  • the TPC acting as a default router, receives the packet and makes the cell/channel decision on the basis of the ACAL list. After making the decision, it pages the MN, builds a routing path to the MN via the selected IU, and routes the packet via the IU to the MN.
  • the TPC also informs the MMU about the decision so that the MMU can monitor the signal quality (strength) of the active cell and make appropriate handover decisions.
  • the MMU updates the ACAL list. If the MMU determines that a handover is necessary, it sends the TPC a request to select a new cell on the basis of the new ACAL. In this case too, the TPC informs the MMU about the decision, and the MMU assists the MN to complete the handover.
  • the MN may have to be handed over to another cell/channel.
  • the TPC makes the decision on the basis of the ACAL and instructs the MMU to perform the rest of the handover.
  • FIG 6 is a signalling diagram illustrating registration and resource reservation.
  • Each MBN has a traffic handling policy table THPT (see Figure 3).
  • the MN wants to initiate a registration process.
  • the MN is assumed to have some rights in one uplink network, which in this example is the GPRS network.
  • the MN has no rights yet in the broadcast networks, but it monitors the broadcast links to obtain the identifier or IP address of the traffic controller TPC which controls the area in question.
  • the MN sends the authentication centre MAC an authentication request comprising the MN's MIN (MBN interface number) and the IP address of the TPC (obtained in the previous step).
  • the MN is authenticated by the authentication centre MAC.
  • the authentication process is the topic of a co-pending patent application filed on the same day as the present application.
  • the MAC knows whether the MN is allowed to access this MBN. If the authentication is completed successfully, in step RR6 the MAC consults the home registration unit HRU to get the MN's Access Permission List APL, which indicates the MN's rights in each BN.
  • the HRU of a visiting MN may be located in a different MBN.
  • the TPC also negotiates with the HRU to obtain the subscriber's preferences, such as the QMTC table shown in Figure 4.
  • the MAC decides whether the TPC is appropriate, considering the APL list.
  • step RR8 the MAC informs the TPC that the authentication was successful, and reports the subscriber preference information.
  • the MN receives an indication that the authentication was completed successfully.
  • the MAC establishes a security association between the MN and the SSN (the TPC, MMU and RCU). For example, a session key may be distributed to the MN and the SSN. The session key allows encrypted communication between the MN and the SSN.
  • a registration step RR11 the MN sends its address in the uplink and downlink bearer networks to the TPC.
  • step RR12 the MN reports the following information to the TPC, which passes it on to the MMU (which preferably shares the TPC's IP address): 1) signal quality of each available cell/channel in the broadcast network(s), and 2) available bidirectional bearers.
  • the TPC/MMU selects the acceptable cell(s)/channel(s) in the broadcast network(s) and prepares the ACAL list (Available Care-of Address List, see Figure 5).
  • step RR16 the MMU gives the ACAL list to the TPC.
  • the MN's COA within the HA is the COA associated with the TPC.
  • the HA updates and acknowledges the MN's mobility binding. Any correspondent node CN may now reach the MN via its HA by sending a packet with the IP address of the MN.
  • FIG. 7 is a signalling diagram illustrating the start of a session.
  • the set of events begins in step SS2 in which the MN's correspondent node CN knows the MN's IP address IP(MN).
  • the CN does not know the mobility binding in the HA.
  • the first user data packet is routed to the HA.
  • 'data' refers to data packets of session 1
  • 'data 2' refers to data packets of session 2.
  • the packet is tunnelled to the TPC.
  • the TPC uses the QMTC table to classify the incoming packet to its MBN traffic class.
  • the TPC uses the ACAL table (which combines the subscriber's preference, the MBN operator's traffic policies, and available traffic/resource information (resource availability data) obtained from the RCU) to select a downlink bearer.
  • ACAL table which combines the subscriber's preference, the MBN operator's traffic policies, and available traffic/resource information (resource availability data) obtained from the RCU
  • Steps SS10 to SS16 relate to resource reservation, which the TPC performs only when necessary (for guaranteed service).
  • Resource reservation is specific to the data flow. For example, if the data flow in question belongs to MBN traffic class 5, the TPC reserves a certain amount of bandwidth in the selected cell (under the COA indicated by the ACAL).
  • the RCU preferably maintains a database (eg a fast look-up table) that indicates resource availability in all cells under the TPC, and in the neighbouring cells (for smooth handover). If the incoming traffic belongs to best effort service, the TPC selects the cell only on the basis of the resource availability table.
  • the TPC checks 1) if resource reservation has been performed, and 2) if not, how much bandwidth has to be reserved (based on the QMTC and THPT tables). By looking at the resource availability table, the TPC determines a suitable channel, but it requests the RCU to perform the actual channel reservation.
  • the RCU makes a decision about resource reservation and sends the decision to the downlink interface unit DL_IU (in this example: a DVB interface unit). Steps SS14 and SS16 are the corresponding acknowledgements.
  • Steps SS18 and SS20 relate to paging the mobile node MN. If the MN is not active in the selected bearer or channel, it needs to be paged. In step SS18, the MN is paged via the uplink interface unit UL_IU (a GPRS interface unit in this example). Step SS20 is the paging response from the MN.
  • UL_IU uplink interface unit
  • step SS22 the first user data packet to the MN is forwarded to the downlink interface unit DL_IU.
  • step SS24 the DL_IU checks that the recipient's COA is authorized and the resource reservation is valid.
  • step SS26 the DL_IU forwards the first user data packet to the MN.
  • the COA is associated with the DL_IU.
  • the subnetwork prefix is the same as with the DL_IU, and the second part of the address is the MIN.
  • step SS30 the CN updates the MN's mobility binding.
  • step SS32 the CN begins to send MN-terminated data packets directly to the DL_IU, thus bypassing the intervening elements (the HRU, the HA and the TPC).
  • the CN may have sent more than one packet before receiving the MN's updated mobility binding in step SS28, in which case the TPC may have to route more than one packet to the MN.
  • step SS34 if the same CN needs to open another session for the MN, and the new session requires best effort service (no resource reservation needed), the data of the new session is sent just like the data in step SS32 (the final step being shown by a dotted arrow). But if the new session requires guaranteed service (which in turn requires resource reservation), the first packet of the new session is routed from the DL_IU to the TPC, as shown in step SS36. In step SS38, the TPC performs resource reservation for the second session. This step comprises the detailed steps of SS10 to SS16. In step SS40, the first data packet of the second session is routed to the MN. In step SS42, subsequent packets of the second session are routed to the MN.
  • the IU can simply delete the information related to the MN from its cache and inform the TPC about its action.
  • the MN may maintain a similar timer. If it receives no packets before the timer expires, the MN stops monitoring the broadcast bearer for user data. If the MN is still expecting data when the timer is about to expire, the MN may request the IU to temporarily extend the time limit. The IU may accept or reject the request.
  • the mobile node only monitors one bearer type (network) at a time.
  • the subscriber data related to the mobile node can include a default bearer type, such as GSM or UMTS.
  • the mobile node should be paged on this bearer.
  • the mobile node can be ordered to monitor the selected bearer type by sending a modified page message which indicates the selected bearer type, channel, possible decryption data, etc. Alternatively, such information can be sent in a separate message, such as a data call or the like.
  • FIG. 8 illustrates a cellular broadcast network.
  • the cellular broadcast network concept has been introduced for data broadcasting in DxB networks.
  • the concept introduces DxB microcells.
  • a DxB network may comprise two overlapping cell structures. Such areas are covered by normal DxB cells 81, called macrocells, and by smaller cells 82 to 85, called microcells.
  • the microcells provide content which is customized according to a particular site.
  • a preferred embodiment of the invention introduces two new elements, namely an aggregate interface unit AIU and a broadcast router BR. Each broadcast router BR is coupled to a single microcell transmitter.
  • AIU acts not only as a router for the BRs, but also as a centralized resource management unit. Employing the AIU and BR elements reduces key management load and signalling related to resource management.
  • FIG 9 illustrates packet routing and the various data structures in a system as shown in Figure 8.
  • the aggregate interface unit AIU comprises a channel allocation table CAT having a resource entry for each combination of a broadcast router BR and channel.
  • the CAT table may indicate usage of the resources by some appropriate metric.
  • the channel identifiers Ch1 to Chn may represent physical channels, such as several 8MHz channels in a DVB-T network.
  • Each broadcast router BR1 to BRn comprises a channel mapping table CMT1, CMT2, etc.
  • the channel mapping tables map the mobile node's care-of address COA to a channel identifier.
  • Reference signs 91 to 9n denote the microcells under one AIU.
  • x and y are two indices within the range of 1 to n.
  • Reference sign 95 denotes a data packet arriving to the AIU.
  • the data packet's header indicates the COA as COA(BRx_MN), which means the BRx subnetwork prefix plus the mobile node's MIN.
  • the AIU's own IP address IP(AIU) is only used when the AIU needs to receive signalling packets from other units, such as the TPC, but this address is not used for routing data to the MN.
  • the AIU uses the CAT table to convert the data packet 95 to a data packet 96 whose header indicates the COA of BRy, under which the MN is located.
  • BRy uses its channel mapping table CMT to convert the data packet 96 to a data packet 97, which is an IP packet encapsulated in a DxB packet.
  • the data packet 97 has a DxB header in addition to the IP header.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Claims (6)

  1. Procédé d'acheminement de paquets de données (DP) vers un noeud mobile (MN) à partir de son noeud correspondant (CN), via un réseau support multiple, ou MBN, ce réseau support multiple fournissant de multiples types de supports différents pour l'acheminement de paquets de données, le MBN comprenant :
    au moins un réseau support de liaison montante (GSM, GPRS, UMTS),
    au moins un réseau support de liaison descendante (DxB), et
    un réseau fédérateur (BB) comprenant
    un ensemble de noeuds de contrôle d'accès (MAC),
    un ensemble de noeuds de support de service (SSN),
    un ensemble d'unités interfaces (IU), et
    des moyens formants passerelles (BG/FW) vers un réseau IP (IPN),
    dans lequel le MBN comprend en outre, ou est couplé pour fonctionner à un agent personnel (HA, HAN),
    caractérisé par
    la réception et la mise à jour, dans l'ensemble de noeuds de support de service (SSN), d'informations de disponibilité de ressources (RR12) concernant le au moins un réseau support de liaison descendante (DxB) ;
    la réception et la mise à jour, dans l'ensemble de noeuds de support de service (SSN), d'informations de préférences d'abonné (QMTC) concernant le noeud mobile ;
    la mise à jour, dans l'ensemble de noeuds de support de service (SSN), d'informations de politique de trafic (THPT) concernant le MBN ;
    dans un contrôleur centralisé de politique de trafic (TPC) compris dans l'ensemble de noeuds de support de service (SSN), la génération d'une table d'acheminements (ACAL) en se basant sur les informations de préférences d'abonnés (QMTC), les informations de politique de trafic (THPT) et les données de disponibilité de ressources (RR12), et l'utilisation de la table d'acheminements (ACAL) pour l'acheminement (SS26) d'un ou quelques paquet(s) de données initial(ux) d'une nouvelle session depuis le noeud correspondant (CN) vers le noeud mobile (MN) ;
    l'exécution d'une mise à jour de liaison entre le noeud mobile (MN) et le noeud correspondant (CN) ;
    le stockage d'une adresse (202) associée au contrôleur centralisé de politique de trafic (TPC) en tant qu'adresse dédiée au noeud mobile dans son agent personnel (HA) ;
    l'acheminement (SS4, SS6) d'un paquet de données initial via l'agent personnel et le contrôleur centralisé de politique de trafic vers une unité interface de réseau porteur (DL_IU) desservant le noeud mobile ;
    en réponse audit acheminement, le stockage d'une adresse (214) de l'unité interface de réseau porteur en tant qu'adresse dédiée au noeud mobile dans le noeud correspondant (CN) ;
    en réponse à ladite mise à jour de liaison, l'acheminement (SS32, SS34, SS42) des paquets de données suivants, directement depuis le noeud correspondant (CN) vers l'unité d'interface de réseau porteur (DL_IU), moyennant quoi les paquets de données contournent l'agent personnel (HA) et le contrôleur centralisé de politique de trafic.
  2. Procédé selon la revendication 1, caractérisé en ce que l'acheminement du paquet de données initial comprend les étapes de :
    déterminer si l'en-tête du paquet de données indique un service garanti ; et, si oui :
    réserver des ressources nécessaires dans le réseau support de liaison montante (DxB).
  3. Réseau fédérateur (BB) d'un réseau de support multiple, ou MBN, pour acheminer des paquets de données (DP) vers un noeud mobile (MN) depuis son noeud correspondant (CN), le réseau de support multiple constituant différents types de supports d'acheminements de paquets de données, le MBN comprenant
    au moins un réseau support de liaison montante (GSM, GPRS, UMTS),
    au moins un réseau support de liaison descendante (DxB),
    le réseau fédérateur comprenant
    un ensemble de noeuds de contrôle d'accès (MAC),
    un ensemble de noeuds de support de service (SSN),
    un ensemble d'unités interfaces (IU), et
    des moyens formants passerelles (BG/FW) vers un réseau IP (IPN),
    dans lequel le MBN comprend, ou est couplé pour fonctionner à, un agent personnel (HA, HAN),
    caractérisé par
    le fait que l'ensemble de noeuds de contrôle d'accès (MAC) est prévu pour l'octroi ou le rejet centralisé des droits du noeud mobile (MN) aux services, via le réseau fédérateur (BB), et pour le stockage des informations de préférences d'abonné (QMTC) associées au noeud mobile ;
    l'ensemble de noeuds de support de service (SSN) étant prévu pour :
    - l'administration et la distribution centralisées des politiques de trafic (THPT) ;
    - la gestion centralisée de mobilité pour gérer la mobilité du noeud mobile à l'intérieur de chaque réseau de support de liaison descendante (DxB) ;
    - le contrôle centralisé des ressources pour prendre des décisions de réservation de ressources à l'intérieur de chaque réseau support de liaison descendante (DxB) ; et
    l'ensemble d'unités interfaces (IU) étant prévu pour être interfacé avec, et pour prendre les décisions de réservation de ressources dans le, au moins un réseau support de liaison descendante (DxB) ;
    dans lequel l'ensemble de noeuds de support de service (SSN) comprend une unité de gestion de mobilité (MMU) pour la gestion centralisée de mobilité du noeud mobile dans le au moins un réseau support de liaison descendante (DxB), l'ensemble de noeuds de support de service (SSN) étant configuré pour
    recevoir les informations de préférences d'abonné (QMTC) associées au noeud mobile :
    mettre à jour les données de disponibilité des ressources (RR12) et exécuter des commandes de réservation de ressources (SS12)concernant au moins un réseau support de liaison descendante (DxB) ;
    combiner, dans un contrôleur centralisé de politique de trafic, les informations de politique de trafic (THPT), lesdits informations de préférences d'abonné (QMTC) et lesdites données de disponibilité de ressources (RR12) dans une table d'acheminements (ACAL), et acheminer un ou quelques paquets de données initiaux d'une nouvelle session en se basant sur ladite table d'acheminements ; et
    transmettre les décisions de réservation de ressources (SS12)à au moins une unité interface de liaison descendante (DxB_IU) ;
    dans lequel l'ensemble d'unités interfaces (DxB_IU) est configuré pour
    transférer une requête d'accès initiale (RR2) depuis le noeud mobile (MN) vers l'ensemble de noeuds de contrôle d'accès (MAC), l'ensemble de noeuds de contrôle d'accès contrôlant l'accès aux services à l'intérieur de, et via, le réseau fédérateur (BB) ;
    recevoir et prendre des décisions de réservation de ressources (SS12) concernant le réseau support de liaison descendante (DxB);
    acheminer des paquets de données vers le noeud mobile (MN) selon lesdites politiques de trafic spécifiques des noeuds (QMTC);
    dans lequel l'ensemble d'unités interfaces (DxB_IU) comprend une unité de gestion de ressources (RMU) couplée à l'unité interface (DxB IU), pour exécuter les décisions de réservation de ressources (SS12);
    dans lequel le noeud mobile (MN) comprend une interface radio vers des réseaux supports (BN) multiples différents, au moins un réseau support étant un réseau de diffusion, le noeud mobile étant configuré pour
    s'inscrire auprès du réseau fédérateur (BB, MAC) contrôlant lesdits réseaux supports (BN) multiples différents ; et,
    en réponse à l'inscription auprès du réseau fédérateur, mettre à jour la liaison de mobilité du noeud mobile via le réseau fédérateur ;
    dans lequel le MBN est configuré pour
    exécuter une mise à jour de liaison entre le noeud mobile (MN) et le noeud correspondant (CN) ;
    stocker une adresse associée au contrôleur centralisé de politique de trafic (TPC) comprise dans l'ensemble de noeuds de support de service (SSN) en tant qu'adresse dédiée au noeud mobile dans son agent personnel (HA) ; et
    acheminer un paquet de données initial via l'agent personnel et le contrôleur centralisé de politique de trafic vers une unité interface de réseau support (DL_IU) desservant le noeud mobile.
  4. Réseau fédérateur (BB) selon la revendication 3, caractérisé en ce que la table d'acheminements (ACAL) est configurée pour allouer au moins une adresse IP à une combinaison de cellules/canaux à l'intérieur du au moins un réseau support de liaison descendante (DxB).
  5. Réseau fédérateur (BB) selon la revendication 3, caractérisé en ce que chaque unité interface est configurée pour définir un sous-réseau IP comprenant toutes les cellules sous l'unité interface concernée.
  6. Réseau fédérateur (BB) selon la revendication 3 ou 5, caractérisé en ce que l'ensemble d'unités interfaces (DxB_IU, AIU, BR) est configuré pour supporter des structures de cellules multiples se chevauchant géographiquement (81 ; 82 - 85) dans un réseau DAB et/ou DVB.
EP01921412A 2000-03-31 2001-03-29 Architecture et acheminement de paquets dans un reseau de type multisupport Expired - Lifetime EP1277361B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07112040A EP1838114B1 (fr) 2000-03-31 2001-03-29 Architecture et acheminement de paquets dans un réseau de type à porteuses multiples

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
FI20000752 2000-03-31
FI20000752A FI110227B (fi) 2000-03-31 2000-03-31 Arkkitehtuuri ja paketinreititys monipalveluverkossa
PCT/FI2001/000306 WO2001076286A1 (fr) 2000-03-31 2001-03-29 Architecture et acheminement de paquets dans un reseau de type multisupport

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP07112040A Division EP1838114B1 (fr) 2000-03-31 2001-03-29 Architecture et acheminement de paquets dans un réseau de type à porteuses multiples

Publications (2)

Publication Number Publication Date
EP1277361A1 EP1277361A1 (fr) 2003-01-22
EP1277361B1 true EP1277361B1 (fr) 2007-07-25

Family

ID=8558077

Family Applications (2)

Application Number Title Priority Date Filing Date
EP01921412A Expired - Lifetime EP1277361B1 (fr) 2000-03-31 2001-03-29 Architecture et acheminement de paquets dans un reseau de type multisupport
EP07112040A Expired - Lifetime EP1838114B1 (fr) 2000-03-31 2001-03-29 Architecture et acheminement de paquets dans un réseau de type à porteuses multiples

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP07112040A Expired - Lifetime EP1838114B1 (fr) 2000-03-31 2001-03-29 Architecture et acheminement de paquets dans un réseau de type à porteuses multiples

Country Status (8)

Country Link
EP (2) EP1277361B1 (fr)
CN (1) CN1270555C (fr)
AT (2) ATE368359T1 (fr)
AU (1) AU2001248408A1 (fr)
DE (2) DE60129545T2 (fr)
ES (1) ES2288939T3 (fr)
FI (1) FI110227B (fr)
WO (1) WO2001076286A1 (fr)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7426393B2 (en) 2001-11-19 2008-09-16 Nokia Corporation Method and system of identifying network services
EP1451979B1 (fr) 2001-11-27 2006-12-20 Nokia Corporation Transmission d'un message de mise a jour obligatoire indiquant une adresse d'attention afin de transferer des paquets de donnees a une noeud mobile par l'intermediaire d'une interface unidirectionnelle
WO2003088599A1 (fr) 2002-04-12 2003-10-23 Nokia Corporation Gestion qos fondee sur une politique dans plusieurs reseaux d'acces radio
EP1518183A2 (fr) * 2002-06-28 2005-03-30 Nokia Corporation Procede pour enregistrer l'adresse d'origine d'un noeud mobile avec un agent d'origine
US20040121778A1 (en) * 2002-10-08 2004-06-24 Interdigital Technology Corporation Quality of service mapping between various types of wireless communication systems
JP3990976B2 (ja) * 2002-12-19 2007-10-17 株式会社エヌ・ティ・ティ・ドコモ 移動ノード、モビリティ制御装置、通信制御方法及び通信システム
JP4210168B2 (ja) * 2003-07-09 2009-01-14 株式会社エヌ・ティ・ティ・ドコモ 移動端末、制御装置、ホームエージェント及びパケット通信方法
GB0400080D0 (en) 2004-01-05 2004-02-04 Nokia Corp Controlling data sessions in a communications system
PL1702450T3 (pl) * 2004-01-05 2020-01-31 Nokia Technologies Oy Sterowanie sesjami danych w układzie komunikacyjnym
JP4494853B2 (ja) * 2004-04-20 2010-06-30 株式会社エヌ・ティ・ティ・ドコモ 移動ノード、移動制御ノード、パケット通信システム、及び移動検出方法
DE102004038057A1 (de) * 2004-08-02 2006-02-23 Teles Ag Informationstechnologien Verfahren zur Datenübertragung zwischen einem Server in oder an einem hybriden Netzwerk und einer Empfangseinrichtung des hybriden Netzwerkes (dynamische Senderauswahl)
JP4462042B2 (ja) * 2005-01-14 2010-05-12 パナソニック株式会社 ルータ選択方法、ホームエージェント装置、移動ルータ、および移動ネットワークシステム
US7640020B2 (en) * 2005-12-19 2009-12-29 Motorola, Inc. Method and apparatus for assigning backhaul methods
JP2010500782A (ja) * 2006-08-09 2010-01-07 テレフオンアクチーボラゲット エル エム エリクソン（パブル） モバイルｉｐシステムにおけるパケットのルーティングを行うための方法と装置
JP5187195B2 (ja) * 2007-01-18 2013-04-24 日本電気株式会社 モバイルｉｐ制御システム、モバイルｉｐ制御方法、およびモバイルｉｐ制御プログラム
US8611358B2 (en) 2011-04-06 2013-12-17 Hewlett-Packard Development Company, L.P. Mobile network traffic management
CN106658468A (zh) * 2016-11-30 2017-05-10 努比亚技术有限公司 数据卡业务切换的方法及终端

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5901352A (en) 1997-02-20 1999-05-04 St-Pierre; Sylvain System for controlling multiple networks and associated services
US6137791A (en) 1997-03-25 2000-10-24 Ericsson Telefon Ab L M Communicating packet data with a mobile station roaming within an incompatible mobile network
US6549522B1 (en) * 1997-12-17 2003-04-15 British Telecommunications Public Limited Company Mobile data rate enhancement via foreign agent load balancing
DE69821393T2 (de) * 1997-12-17 2004-11-11 British Telecommunications P.L.C. Proxy-Leitweglenkung
FI106503B (fi) 1998-09-21 2001-02-15 Nokia Networks Oy IP-liikkuvuusmekanismi pakettiradioverkkoa varten
FI106825B (fi) 1998-09-21 2001-04-12 Nokia Networks Oy IP-liikkuvuusmekanismi pakettiradioverkkoa varten
US6973057B1 (en) * 1999-01-29 2005-12-06 Telefonaktiebolaget L M Ericsson (Publ) Public mobile data communications network
EP1047244A1 (fr) 1999-04-20 2000-10-25 Lucent Technologies Inc. Mobile-IP supportant la qualité de service pour données envoyées d'un noeud mobile à un noeud correspondant
FI20000662A (fi) 2000-03-21 2001-09-22 Nokia Oyj Solunvaihto useaa välitystekniikkaa tukevassa verkossa

Also Published As

Publication number Publication date
EP1838114B1 (fr) 2010-03-24
ATE462279T1 (de) 2010-04-15
FI110227B (fi) 2002-12-13
WO2001076286A1 (fr) 2001-10-11
DE60129545D1 (de) 2007-09-06
CN1270555C (zh) 2006-08-16
ATE368359T1 (de) 2007-08-15
FI20000752A0 (fi) 2000-03-31
DE60141660D1 (de) 2010-05-06
EP1838114A2 (fr) 2007-09-26
DE60129545T2 (de) 2008-04-10
AU2001248408A1 (en) 2001-10-15
CN1522547A (zh) 2004-08-18
EP1277361A1 (fr) 2003-01-22
FI20000752A (fi) 2001-10-01
EP1838114A3 (fr) 2007-12-26
ES2288939T3 (es) 2008-02-01

Similar Documents

Publication Publication Date Title
EP1277367B1 (fr) Procede de transfert dans un reseau mobile sans fil de protocole internet
US7466719B2 (en) Packet routing in a multi-bearer-type network
US7437154B2 (en) Heterogeneous mobile radio system
EP1277361B1 (fr) Architecture et acheminement de paquets dans un reseau de type multisupport
US7242932B2 (en) Mobile internet protocol on a signaling channel
FI108983B (fi) Liikkuvuusagentin valinta accessverkossa
KR101706005B1 (ko) 무선 통신 시스템에서 셀룰러 세션을 설정하는 방법 및 장치
US6721297B2 (en) Method and apparatus for providing IP mobility for mobile networks
FI108832B (fi) IP-reitityksen optimointi accessverkossa
US7471957B2 (en) Paging method and system for a radio access network
US6519235B1 (en) Mobile radio communication packet data network
US7917151B2 (en) Flexible network architecture with user group support
WO2001072076A1 (fr) Transfert intercellulaire dans un reseau du type a porteuses multiples
US8477729B2 (en) Support for multi-homing protocols using transient registration and expanded binding revocation messages
WO2007038947A1 (fr) Architecture de reseau et procede pour l'acces aux stations d'utilisateur
Sargento et al. Ubiquitous Access through the Integration of Mobile Ad-hoc Networks
Salberg WLAN-GPRS interworking
EP2068527A1 (fr) Contrôle de réseau d'une sélection de carte et de sélection d'itinéraire dans un environnement IP mobile
Karagiannis et al. Mobility support for ubiquitous Internet

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20021025

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17Q First examination report despatched

Effective date: 20060515

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

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

Owner name: NOKIA SIEMENS NETWORKS OY

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60129545

Country of ref document: DE

Date of ref document: 20070906

Kind code of ref document: P

ET Fr: translation filed
PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

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

Effective date: 20070725

Ref country code: NL

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

Effective date: 20070725

Ref country code: PT

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

Effective date: 20071226

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2288939

Country of ref document: ES

Kind code of ref document: T3

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

Ref country code: CH

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

Effective date: 20070725

Ref country code: AT

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

Effective date: 20070725

Ref country code: LI

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

Effective date: 20070725

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

Ref country code: BE

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

Effective date: 20070725

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

Ref country code: GR

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

Effective date: 20071026

Ref country code: DK

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

Effective date: 20070725

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

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

Ref country code: SE

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

Effective date: 20071025

26N No opposition filed

Effective date: 20080428

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

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080331

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

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080331

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

Ref country code: CY

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

Effective date: 20070725

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

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080329

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

Ref country code: TR

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

Effective date: 20070725

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 60129545

Country of ref document: DE

Representative=s name: SAMSON & PARTNER, PATENTANWAELTE, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 60129545

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04Q0007220000

Ipc: H04W0084000000

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 60129545

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04Q0007220000

Ipc: H04W0084000000

Effective date: 20140630

Ref country code: DE

Ref legal event code: R082

Ref document number: 60129545

Country of ref document: DE

Representative=s name: SAMSON & PARTNER, PATENTANWAELTE, DE

Effective date: 20140521

Ref country code: DE

Ref legal event code: R081

Ref document number: 60129545

Country of ref document: DE

Owner name: NOKIA SOLUTIONS AND NETWORKS OY, FI

Free format text: FORMER OWNER: NOKIA SIEMENS NETWORKS OY, ESPOO, FI

Effective date: 20140521

Ref country code: DE

Ref legal event code: R082

Ref document number: 60129545

Country of ref document: DE

Representative=s name: SAMSON & PARTNER PATENTANWAELTE MBB, DE

Effective date: 20140521

REG Reference to a national code

Ref country code: ES

Ref legal event code: PC2A

Owner name: NOKIA SOLUTIONS AND NETWORKS OY

Effective date: 20141121

REG Reference to a national code

Ref country code: FR

Ref legal event code: CD

Owner name: NOKIA SOLUTIONS AND NETWORKS OY, FI

Effective date: 20141201

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

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

Ref country code: GB

Payment date: 20190327

Year of fee payment: 19

Ref country code: DE

Payment date: 20190319

Year of fee payment: 19

Ref country code: IT

Payment date: 20190326

Year of fee payment: 19

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

Ref country code: FR

Payment date: 20190213

Year of fee payment: 19

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

Ref country code: ES

Payment date: 20190401

Year of fee payment: 19

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60129545

Country of ref document: DE

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

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200331

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201001

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20200329

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

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200329

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20210811

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

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200329

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

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200330