EP1834499B1 - Method and system for service access control in shared networks - Google Patents

Method and system for service access control in shared networks Download PDF

Info

Publication number
EP1834499B1
EP1834499B1 EP05822023A EP05822023A EP1834499B1 EP 1834499 B1 EP1834499 B1 EP 1834499B1 EP 05822023 A EP05822023 A EP 05822023A EP 05822023 A EP05822023 A EP 05822023A EP 1834499 B1 EP1834499 B1 EP 1834499B1
Authority
EP
European Patent Office
Prior art keywords
operator
service
admission control
network
admission
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.)
Not-in-force
Application number
EP05822023A
Other languages
German (de)
French (fr)
Other versions
EP1834499A4 (en
EP1834499A1 (en
Inventor
Rickard Ljung
Anders Dahl N
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.)
Telia Co AB
Original Assignee
TeliaSonera AB
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 TeliaSonera AB filed Critical TeliaSonera AB
Publication of EP1834499A1 publication Critical patent/EP1834499A1/en
Publication of EP1834499A4 publication Critical patent/EP1834499A4/en
Application granted granted Critical
Publication of EP1834499B1 publication Critical patent/EP1834499B1/en
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18Negotiating wireless communication parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12Access point controller devices

Definitions

  • the present invention relates to a method of sharing a Radio Access-Network, RAN, in one or more areas by at least two operators, wherein the determination whether to grant admission or not of a User Equipment, UE, to the RAN is performed in an admission control algorithm.
  • the invention also relate to a radio access network intended to be shared in one or more areas by at least two operators, comprising admission control means to determine whether to grant admission of a service request from a User Equipment, UE, to the network, RAN, or not.
  • a Radio Access Network In a shared network two or more operators share a Radio Access Network, RAN, in one or more areas. However, the different operators may wish to differentiate their services from the RAN to their respective customers. If not all operators in the shared network want to invest in new Universal Mobile Telecommunication System, UMTS, Terrestrial Radio Access Network, UTRAN, technology as for example High Speed Downlink Packet Access, HSDPA, High Speed Uplink Packet Access, HSUPA, (even called Enhanced Dedicated Channel, E-DCH), Multimedia Broadcast Multicast Service, MBMS, or Voice over IP, VoIP, bearers, it should be possible to block customers of the operators not investing in the new technology. Moreover, in a rural area one operator might want interactive service with bit rates up to 384 kbps, whereas other operators might be content with 128 kbps.
  • HSDPA High Speed Downlink Packet Access
  • HSUPA High Speed Uplink Packet Access
  • MBMS Multimedia Broadcast Multicast Service
  • Voice over IP Voice over IP
  • EP 1 443 790 describes a method and a system for sharing the capacity in a radio access multi operator mobile network. It is based on the pre-release 6 roaming based network sharing solution. For the sharing decision the operator, that serves the subscriber demanding the resource, is identified. The available resources for the serving operator are checked, and the use of the available resources in the network, based on a set of sharing rules, is controlled. The means of sharing rules are to prioritize home subscribers over roaming subscribers (e.g. customers of virtual network operators or operators using national roaming), or to control the resource allocation (power) to guarantee each operator an agreed capacity share.
  • roaming subscribers e.g. customers of virtual network operators or operators using national roaming
  • power resource allocation
  • a resource controller is operable to allocate a radio resource to a subscriber unit in response to an operator identity associated with a service of the subscribers unit, such that different quality of service is achieved for different operators.
  • the cellular communication system has a common radio access network resource divided into a first partition for a first operator and a second partition for a second operator, and the resource controller is operable to allocate resources from the first partition if the operator identity corresponds to the first operator and from the second partition if the operator identity corresponds to the second operator.
  • US 2004/00157600 a technique is described for determining whether to grant access for a user equipment to a radio access network in a present position of the user equipment within a communications system.
  • the communications system comprises a control node handling services for the user equipment and an access node controlling the access network.
  • US 2002/01223348 discloses a technique for precluding or rejecting accesses, in competition areas, to cells of a first operator's network attempted by or on behalf of a mobile terminal which subscribes to a second operators network. Any cell of the first operator network for which the second operator network has a competing cell is designated as a restricted cell, and attempted utilization of the restricted cell by the user equipment unit which subscribes to the second operator network is rejected.
  • An enhanced Network Sharing, NS, support is presently being standardized in 3rd Generation Partnership Project in 3GPP, for Release 6.
  • Each operator will be able to have its PLMN identity broadcast in the shared network and each operator has a core network.
  • the core network nodes MSC and SGSN can be shared as well.
  • Virtual network operators are not included in our usage the term "operator" here.
  • the 3GPP standard allows differentiation of the services to different customers, but this is managed and controlled by the Core Network, CN.
  • the aim of this service differentiation is to set different QoS on the same service to different customers.
  • Letting CN manage the above proposed service admission control is not a good way forward for two reasons, first, CN is not involved in some of the signaling procedures in question, second it does not prevent abuse from an operator.
  • the Radio Network Controller When old UE:s request a service the Radio Network Controller, RNC, will read the Network Resource Identifier, NRI, in the "Initial Direct Transfer" message. The idea is that the most significant bits in the NRI could specify a customer's operator. The RNC uses this information to route the traffic to the correct Core Network, CN, i.e. the CN belonging to the operator for the specific user.
  • NRI Network Resource Identifier
  • the new UE:s that support the enhanced network sharing feature will also send an NRI.
  • the 3GPP standardization does not require that the NRI:s will be used for routing the traffic to the correct CN.
  • the new UE will, however, send information of selected Public Land Mobile Network, PLMN, (selected CN), which could then be used for routing.
  • PLMN Public Land Mobile Network
  • the operator information i.e. the NRI information for old UE:s and selected CN (selected PLMN) or NRI for new UE:s, is also used in the admission control algorithm. If the operator information is associated with operator A then the admission control can reject a request of using HSDPA or MBMS etc, whereas operator B's customers are granted such requests if the available resources admit it.
  • a "service admission control" in addition to, or as a part of, the admission control for QoS in the Controlling RNC, CRNC, and some service admission parameters are a part of the set of admission control parameters.
  • differentiation is admitted of allowed UTRAN service access between operators in a shared network.
  • the functionality is implemented as a part of the QoS admission control function in CRNC of the UMTS networks, alternatively as a service admission control in SRNC that is separate from the QoS admission control.
  • HSDPA True/False
  • HSDPA True/False
  • HSDPA True/False
  • MBMS True/False
  • operator A True/False ... etc.
  • the service admission parameters comprise Operation and Management, O&M, parameters set by the UTRAN supporting company, or set by network manufacturer, viz hard coded from operator perspective. If each of the operators which shares network manages a part of the UTRAN, the hard coded solution could be preferred to avoid abuse from an operator. The network manufacturer will then update the parameter settings as new UTRAN technology is ordered.
  • O&M Operation and Management
  • the RNC maps the operator information, in the NRI or in the selected PLMN information contained in the "Initial direct transfer" message, to an integer, where integer number “1” could mean operator A, "2" operator B, etc.
  • integer number "1” could mean operator A, "2" operator B, etc.
  • the service admission control is performed by the Serving Radio Network Controller, SRNC, and a UE request is sent to a Drift Radio Network Controller, DRNC, by SRNC only if the service admission control admits the request.
  • the DRNC is arranged to inform the SRNC about wishes to set up or modify a radio bearer, the SRNC then performs the service admission control and grants the requested set up or modification from DRNC if admitted by the service admission control.
  • 3GPP standard does not support sending the explicit operator information to the DRNS is to place the service admission control function in the SRNC instead. This is a feasible solution since it is the SRNC that requests radio bearer set ups and modifications at the DRNC.
  • the SRNC performs the service admission control and sends the requests to the DRNC only when the service admission admits the request.
  • the DRNC informs the SRNC that it wishes to modify or set up a radio bearer, and the SRNC then performs the service admission control.
  • the SRNC grants the request from the DRNC if the service admission admits it.
  • figure 1 illustrates the functionality with the initial direct transfer message carrying the NRI
  • figure 2 is a message sequence chart illustrating an example of SRNC relocation.
  • figure 3 illustrates an example of admission control
  • figure 4 illustrates an example of Radio Resource Control
  • figure 5 illustrates an example of radio access bearer modification
  • figure 6 illustrates inter-node B synchronized serving High Speed Downlink Shared Channel, HS-DSCH, cell change at hard handover
  • figure 7 shows an example of physical channel reconfiguration.
  • the new UE s from supporting the NRI solution as well. Anyhow, if the NRI solution is not supported, the selected PLMN information that the RNC receives from the UE in the initial direct transfer message, as illustrated in figure 1 , could be used in the service admission control feature.
  • the admission control process gets the operator information i.e. the integer number, as mentioned above.
  • the service admission control and the now existing Quality of Service, QoS perform an admission check of the request.
  • the request is granted if the request is admitted by both procedures.
  • the service admission control procedure either relies on that the operator information is received as an input into the procedure at each request of a "radio bearer change", e.g. Radio Bearer Reconfiguration, Transport Channel Reconfiguration, or Physical Channel Reconfiguration or that the operator information for the radio bearer is stored in the procedure together with the bearer's identity number.
  • a radio bearer change e.g. Radio Bearer Reconfiguration, Transport Channel Reconfiguration, or Physical Channel Reconfiguration or that the operator information for the radio bearer is stored in the procedure together with the bearer's identity number.
  • the Controlling RNC, CRNC, of a Node B is the RNC which performs admission and congestion control on the cells of the Node B. If more than one RNC is involved in the connection path between a UE and the CN, a RNC is either a SRNC or a DRNC. A UTRAN connected UE has one and only one SRNC, but it may have zero, one or more DRNC:s.
  • a SRNC is responsible for routing traffic to the correct CN node (the routing mechanism is under the Radio Resource Control's RRC's responsibility). Hence, the SRNC has the NRI or selected PLMN information.
  • the NRI routing works as in Iu-flex, e.g. SRNC relocation.
  • the CN is involved in the SRNC relocation, and it is the CN that sets up the connection between the new SRNC and the SGSN node. This procedure is illustrated in figure 2 which illustrates SRNS Relocation in a situation with a UE connected to two CN nodes.
  • the operator information can be passed along to the new SRNC at SRNC relocations.
  • the relocation request message sent from CN to target SRNC can contain the operator information (PLMN identity) in a release 6 network.
  • the new SRNC knows which CN it is connected to and can determine the operator belonging of the UE backwards, i.e. from the CN connection information the RNC can conclude the most significant bits of the NRI. Normally, the RNC looks at the NRI and concludes which CN to connect/route to. This works in the Multi Operator Core Network, MOCN, case, i.e., under the assumption that the operators only share the UTRAN. In the GWCN case it should be possible to coordinate S-RNTI numbers between the operators so that for example the most significant bits indicate operators belonging.
  • the S-RNTI is sent from the SRNC to the target RNC at SRNC relocation.
  • a DRNC may perform macro diversity combining and splitting. It routes the data transparently between the Iub and Iur interface to the SRNC, except when common or shared channels are used in the UE connection.
  • the SRNC performs admission control or capacity management on the cells which is controlled by the SRNC, and the DRNC performs admission control on the cells under its control, as illustrated in figure 3 .
  • the DRNC does not get or possess neither the NRI nor the selected CN (PLMN) of a UE.
  • the 3GPP standard does not support sending neither the NRI nor the selected CN (PLMN) form SRNC to DRNC (CRNC).
  • the DRNC cannot perform service admission control based on operator information of this kind, however this information could be added in an existing message from the SRNC to the DRNC (CRNC).
  • One solution to the lack of explicit operator information in a DRNC can be to always perform SRNS relocation when a user moves to an area controlled by a different RNC, or that one use the non-described procedure that EP 1 443 790 relies on.
  • a solution to the problem that the 3GPP standard does not support sending the explicit operator information to the DRNC is to place the service admission control function in the SRNC instead.
  • the SRNC requests radio bearer setups and modifications at the DRNC.
  • the SRNC performs the service admission control and sends the request to the DRNC only if the service admission admits the request, as discussed above.
  • the DRNC informs the SRNC of a wish to modify or set up a radio bearer, and the SRNC can then perform the service admission control.
  • the SRNC grants the request from the DRNC if the service admission admits it.
  • After SRNC relocation the new SRNC gets the operator information as described earlier.
  • each RNC with SRNC functionality will need to have a set of service admission parameters for each location area or cell in the entire network. This is the reason why placing the service admission control in the admission control according to the present invention involves an important advantage.
  • Some examples of signaling procedures in 25.931 are displayed to verify that the SRNC is involved in the radio bearer establishment and modification procedure even for DRNC:s.
  • MBMS and HSUPA are not yet standardized, but there is no reason for deviation from the present signaling procedures for these technologies.
  • Figure 4 is a message sequence chart illustrating a first example of re-establishment of a RRC connection, anchor approach, in dedicated transport channel, DCH, state.
  • Figure 5 illustrates an example showing modification of a radio access bearer established on a DCH with UE in macro diversity between two RNC:s.
  • a Network Subsystem Application Part, NSAP, synchronized procedure is used and a successful case is shown.
  • NSAP Network Subsystem Application Part
  • a failure message can be sent in any point of the illustrated message sequence chart.
  • Figure 6 is a message sequence chart illustrating a third example with Inter-Note B synchronized serving HS-DSCH cell change at hand over.
  • the source Node B and the target Node B are controlled by two different DRNC:s, referred to as source DRNC and target DRNC, respectively.
  • source DRNC the High Speed-Downlink Shared Channel
  • target DRNC the shared channel of HSDPA
  • Figure 7 shows the message sequence chart for an example for the physical channel reconfiguration in dedicated channel DCH, Radio Resource Control, RRC, state. This procedure can be used, for example, to change the Up-Link, UL, scrambling code of a UE.

Abstract

In a method of sharing a Radio Access Network, RAN, in one or more areas by at least two operators the determination whether to grant admission or not of a User Equipment, UE, to the RAN is performed in an admission control algorithm. A Radio Network Controller, RNC, is reading Network Resource Identifier, NRI, information contained in an “Initial Direct Transfer” message sent by the UE when requesting a service, and the read NRI information is used in a service admission control to check a plurality of service admission parameters as a part of a set of admission control parameters to grant or reject the requested service depending on whether the operator associated with the NRI has invested in needed technology or not. A corresponding radio access network comprises admission control means to determine whether to grant admission of a User Equipment, UE, to the network, RAN, or not. A Radio Network Controller, RNC, is arranged to read NRI, information contained in the “Initial Direct Transfer” message sent by an UE, when requesting a service, and sending the read NRI information to the admission control means to check a plurality of service admission parameters as a part of a set of admission control parameters to grant or reject the requested service depending on whether the operator associated with the NRI has invested in needed technology or not.

Description

    Technical Field
  • The present invention relates to a method of sharing a Radio Access-Network, RAN, in one or more areas by at least two operators, wherein the determination whether to grant admission or not of a User Equipment, UE, to the RAN is performed in an admission control algorithm. The invention also relate to a radio access network intended to be shared in one or more areas by at least two operators, comprising admission control means to determine whether to grant admission of a service request from a User Equipment, UE, to the network, RAN, or not.
  • Background
  • In a shared network two or more operators share a Radio Access Network, RAN, in one or more areas. However, the different operators may wish to differentiate their services from the RAN to their respective customers. If not all operators in the shared network want to invest in new Universal Mobile Telecommunication System, UMTS, Terrestrial Radio Access Network, UTRAN, technology as for example High Speed Downlink Packet Access, HSDPA, High Speed Uplink Packet Access, HSUPA, (even called Enhanced Dedicated Channel, E-DCH), Multimedia Broadcast Multicast Service, MBMS, or Voice over IP, VoIP, bearers, it should be possible to block customers of the operators not investing in the new technology. Moreover, in a rural area one operator might want interactive service with bit rates up to 384 kbps, whereas other operators might be content with 128 kbps.
  • EP 1 443 790 describes a method and a system for sharing the capacity in a radio access multi operator mobile network. It is based on the pre-release 6 roaming based network sharing solution. For the sharing decision the operator, that serves the subscriber demanding the resource, is identified. The available resources for the serving operator are checked, and the use of the available resources in the network, based on a set of sharing rules, is controlled. The means of sharing rules are to prioritize home subscribers over roaming subscribers (e.g. customers of virtual network operators or operators using national roaming), or to control the resource allocation (power) to guarantee each operator an agreed capacity share.
  • In WO 2004/030393 a resource management for a cellular communication system is described. A resource controller is operable to allocate a radio resource to a subscriber unit in response to an operator identity associated with a service of the subscribers unit, such that different quality of service is achieved for different operators. The cellular communication system has a common radio access network resource divided into a first partition for a first operator and a second partition for a second operator, and the resource controller is operable to allocate resources from the first partition if the operator identity corresponds to the first operator and from the second partition if the operator identity corresponds to the second operator.
  • In US 2004/00157600 a technique is described for determining whether to grant access for a user equipment to a radio access network in a present position of the user equipment within a communications system. The communications system comprises a control node handling services for the user equipment and an access node controlling the access network. US 2002/01223348 discloses a technique for precluding or rejecting accesses, in competition areas, to cells of a first operator's network attempted by or on behalf of a mobile terminal which subscribes to a second operators network. Any cell of the first operator network for which the second operator network has a competing cell is designated as a restricted cell, and attempted utilization of the restricted cell by the user equipment unit which subscribes to the second operator network is rejected.
  • Today's technology thus allows for admission control of different services to ensure a certain level of Quality of Service, QoS. An enhanced Network Sharing, NS, support is presently being standardized in 3rd Generation Partnership Project in 3GPP, for Release 6. Each operator will be able to have its PLMN identity broadcast in the shared network and each operator has a core network. The core network nodes MSC and SGSN can be shared as well. Virtual network operators are not included in our usage the term "operator" here. The 3GPP standard allows differentiation of the services to different customers, but this is managed and controlled by the Core Network, CN. The aim of this service differentiation is to set different QoS on the same service to different customers. Letting CN manage the above proposed service admission control is not a good way forward for two reasons, first, CN is not involved in some of the signaling procedures in question, second it does not prevent abuse from an operator.
  • When this NS approach is available there will exist UE:s that support this enhanced network sharing feature (from Rel-6) and old UE:s that do not support this enhanced network sharing feature. The.network will however be able to handle both UE types. The routing of the traffic to the CN:s of the different operators in the shared network might be performed by somewhat different methods for old and new UE:s.
  • When old UE:s request a service the Radio Network Controller, RNC, will read the Network Resource Identifier, NRI, in the "Initial Direct Transfer" message. The idea is that the most significant bits in the NRI could specify a customer's operator. The RNC uses this information to route the traffic to the correct Core Network, CN, i.e. the CN belonging to the operator for the specific user.
  • The new UE:s that support the enhanced network sharing feature will also send an NRI. However, the 3GPP standardization does not require that the NRI:s will be used for routing the traffic to the correct CN. The new UE will, however, send information of selected Public Land Mobile Network, PLMN, (selected CN), which could then be used for routing.
  • "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes" (3GPP TS 23.228 version 5.2.0 Release 5); ETSI TS 123 236 v5.2.0 (2002-03) discloses a method of routing a Mobile Station, MS, within the service area of a Radio Access Network (RAN) node to a Core Network, CN, by determining Network Resource Identifier, NRI, information sent out by the MS as part of an Initial-direct-transfer message to the RAN node. The preamble of claims 1 and 11 is based on this document.
    NOKIA: "Intra domain connection of RAN nodes to multiple CN nodes, example procedures" (3GPP TSG SA WG2) describes similar procedures.
    The purpose of the present invention is to propose a technique for differentiating allowed service access between operators in a shared network of the above indicated kind.
  • Disclosure of the Invention
  • This purpose is obtained by a method and a network of the kind mentioned in the introductory portion and having the characterizing features of claims 1 and 8 respectively.
  • In the present invention the operator information, i.e. the NRI information for old UE:s and selected CN (selected PLMN) or NRI for new UE:s, is also used in the admission control algorithm. If the operator information is associated with operator A then the admission control can reject a request of using HSDPA or MBMS etc, whereas operator B's customers are granted such requests if the available resources admit it. Hence, there will be a "service admission control" in addition to, or as a part of, the admission control for QoS in the Controlling RNC, CRNC, and some service admission parameters are a part of the set of admission control parameters. With the present invention differentiation is admitted of allowed UTRAN service access between operators in a shared network. The functionality is implemented as a part of the QoS admission control function in CRNC of the UMTS networks, alternatively as a service admission control in SRNC that is separate from the QoS admission control.
  • According to advantageous embodiments of the invention the above mentioned parameters will be of the type: HSDPA, operator A = True/False, HSDPA, operator B = True/False, MBMS, operator A = True/False ... etc.
  • According to other advantageous embodiments of the invention the service admission parameters comprise Operation and Management, O&M, parameters set by the UTRAN supporting company, or set by network manufacturer, viz hard coded from operator perspective. If each of the operators which shares network manages a part of the UTRAN, the hard coded solution could be preferred to avoid abuse from an operator. The network manufacturer will then update the parameter settings as new UTRAN technology is ordered.
  • According to still other advantageous embodiments of the invention the RNC maps the operator information, in the NRI or in the selected PLMN information contained in the "Initial direct transfer" message, to an integer, where integer number "1" could mean operator A, "2" operator B, etc. In this way, the service admission control will not need two procedures and two sets of parameters to manage "old" and "new" UE:s.
  • According to the present invention, the service admission control is performed by the Serving Radio Network Controller, SRNC, and a UE request is sent to a Drift Radio Network Controller, DRNC, by SRNC only if the service admission control admits the request. Moreover, the DRNC is arranged to inform the SRNC about wishes to set up or modify a radio bearer, the SRNC then performs the service admission control and grants the requested set up or modification from DRNC if admitted by the service admission control. In this way a solution to the problem that 3GPP standard does not support sending the explicit operator information to the DRNS is to place the service admission control function in the SRNC instead. This is a feasible solution since it is the SRNC that requests radio bearer set ups and modifications at the DRNC. Hence, the SRNC performs the service admission control and sends the requests to the DRNC only when the service admission admits the request. Alternatively the DRNC informs the SRNC that it wishes to modify or set up a radio bearer, and the SRNC then performs the service admission control. The SRNC grants the request from the DRNC if the service admission admits it. Placing the service admission control in the CRNC should be possible, since for example EP 1 443 790 claims, and is based on, that it is possible to pass on information of operator belongings to the CRNC in a pre-release 6 UMTS network even though EP 1 443 790 does not describe how.
  • Brief Description of the Drawings
  • The invention will now be described in greater details with reference to the enclosed drawings on which figure 1 illustrates the functionality with the initial direct transfer message carrying the NRI, figure 2 is a message sequence chart illustrating an example of SRNC relocation., figure 3 illustrates an example of admission control, figure 4 illustrates an example of Radio Resource Control, RRC re-establishment - Dedicated Channel, DCH, re-establishment, figure 5 illustrates an example of radio access bearer modification, figure 6 illustrates inter-node B synchronized serving High Speed Downlink Shared Channel, HS-DSCH, cell change at hard handover, and figure 7 shows an example of physical channel reconfiguration.
  • Detailed Description of Preferred Embodiment
  • As mentioned above an enhanced network sharing support is standardized in 3GGPP for Release 6. With this NS approach there will exist UE:s that support this enhanced network sharing feature (from Rel-6) and old UE:s that do not. The network will however, be able to handle both UE types. Thus when old UE:s request a service the RNC will read the NRI in the "Initial Direct Transfer" message as illustrated in figure 1. The RNC then uses this information to route the traffic to the correct CN. In Rel-6 UE this message also carries selected PLMN, as selected CN, at least at registration. In this later case, NRI:s for these UE:s might not be organized so that the most significant NRI bits specify the operator. On the other hand, nothing in the standard will prevent the new UE:s from supporting the NRI solution as well. Anyhow, if the NRI solution is not supported, the selected PLMN information that the RNC receives from the UE in the initial direct transfer message, as illustrated in figure 1, could be used in the service admission control feature.
  • When there is a new request of resources for a new radio bearer then the admission control process gets the operator information i.e. the integer number, as mentioned above. The service admission control and the now existing Quality of Service, QoS, perform an admission check of the request. The request is granted if the request is admitted by both procedures. The service admission control procedure either relies on that the operator information is received as an input into the procedure at each request of a "radio bearer change", e.g. Radio Bearer Reconfiguration, Transport Channel Reconfiguration, or Physical Channel Reconfiguration or that the operator information for the radio bearer is stored in the procedure together with the bearer's identity number. When there is a request of a radio bearer change the service admission control checks whether it is an allowed change or not from a service perspective.
  • The Controlling RNC, CRNC, of a Node B is the RNC which performs admission and congestion control on the cells of the Node B. If more than one RNC is involved in the connection path between a UE and the CN, a RNC is either a SRNC or a DRNC. A UTRAN connected UE has one and only one SRNC, but it may have zero, one or more DRNC:s.
  • A SRNC is responsible for routing traffic to the correct CN node (the routing mechanism is under the Radio Resource Control's RRC's responsibility). Hence, the SRNC has the NRI or selected PLMN information. The NRI routing works as in Iu-flex, e.g. SRNC relocation. The CN is involved in the SRNC relocation, and it is the CN that sets up the connection between the new SRNC and the SGSN node. This procedure is illustrated in figure 2 which illustrates SRNS Relocation in a situation with a UE connected to two CN nodes. The operator information can be passed along to the new SRNC at SRNC relocations. For example, the relocation request message sent from CN to target SRNC can contain the operator information (PLMN identity) in a release 6 network. Alternatively, the new SRNC knows which CN it is connected to and can determine the operator belonging of the UE backwards, i.e. from the CN connection information the RNC can conclude the most significant bits of the NRI. Normally, the RNC looks at the NRI and concludes which CN to connect/route to. This works in the Multi Operator Core Network, MOCN, case, i.e., under the assumption that the operators only share the UTRAN. In the GWCN case it should be possible to coordinate S-RNTI numbers between the operators so that for example the most significant bits indicate operators belonging. The S-RNTI is sent from the SRNC to the target RNC at SRNC relocation.
  • A DRNC may perform macro diversity combining and splitting. It routes the data transparently between the Iub and Iur interface to the SRNC, except when common or shared channels are used in the UE connection.
  • Hence, the SRNC performs admission control or capacity management on the cells which is controlled by the SRNC, and the DRNC performs admission control on the cells under its control, as illustrated in figure 3.
  • The DRNC does not get or possess neither the NRI nor the selected CN (PLMN) of a UE. The 3GPP standard does not support sending neither the NRI nor the selected CN (PLMN) form SRNC to DRNC (CRNC). Hence, the DRNC cannot perform service admission control based on operator information of this kind, however this information could be added in an existing message from the SRNC to the DRNC (CRNC). One solution to the lack of explicit operator information in a DRNC can be to always perform SRNS relocation when a user moves to an area controlled by a different RNC, or that one use the non-described procedure that EP 1 443 790 relies on.
  • A solution to the problem that the 3GPP standard does not support sending the explicit operator information to the DRNC is to place the service admission control function in the SRNC instead. This is a feasible solution since the SRNC requests radio bearer setups and modifications at the DRNC. Hence, the SRNC performs the service admission control and sends the request to the DRNC only if the service admission admits the request, as discussed above. Alternatively, the DRNC informs the SRNC of a wish to modify or set up a radio bearer, and the SRNC can then perform the service admission control. The SRNC grants the request from the DRNC if the service admission admits it. After SRNC relocation the new SRNC gets the operator information as described earlier.
  • If one wants to perform different service admissions in different location areas or even on different cells, performing the service admission control in the SRNC will be somewhat complex. Basically, each RNC with SRNC functionality will need to have a set of service admission parameters for each location area or cell in the entire network. This is the reason why placing the service admission control in the admission control according to the present invention involves an important advantage.
  • Some examples of signaling procedures in 25.931 are displayed to verify that the SRNC is involved in the radio bearer establishment and modification procedure even for DRNC:s. MBMS and HSUPA are not yet standardized, but there is no reason for deviation from the present signaling procedures for these technologies.
  • Figure 4 is a message sequence chart illustrating a first example of re-establishment of a RRC connection, anchor approach, in dedicated transport channel, DCH, state.
  • Figure 5 illustrates an example showing modification of a radio access bearer established on a DCH with UE in macro diversity between two RNC:s. A Network Subsystem Application Part, NSAP, synchronized procedure is used and a successful case is shown. For an unsuccessful case it is important to note that a failure message can be sent in any point of the illustrated message sequence chart.
  • Figure 6 is a message sequence chart illustrating a third example with Inter-Note B synchronized serving HS-DSCH cell change at hand over. The source Node B and the target Node B are controlled by two different DRNC:s, referred to as source DRNC and target DRNC, respectively. In this case the High Speed-Downlink Shared Channel, HS-DSCH, the shared channel of HSDPA, mobility procedure is performed in a single step.
  • Figure 7 shows the message sequence chart for an example for the physical channel reconfiguration in dedicated channel DCH, Radio Resource Control, RRC, state. This procedure can be used, for example, to change the Up-Link, UL, scrambling code of a UE.
  • Abbreviations
  • 3GPP
    3rd Generation Partnership Project
    CN
    Core Network
    CRNC
    Controlling RNC
    DCH
    Dedicated Channel
    DL
    Downlink
    DRNC
    Drift RNC
    DSCH
    Downlink Shared Channel
    HSDPA
    High Speed Downlink Packet Access
    HSUPA
    High Speed Uplink Packet Access
    HS-DSCH
    High Speed Downlink Shared Channel
    GWCN
    Gateway Core Network
    MBMS
    Multimedia Broadcast Multicast Service
    MOCN
    Multi Operator Core Network
    NBAP
    Node B application Part
    NRI
    Network Resource Identifier
    NS
    Network Sharing
    O&M
    Operation & Management
    PLMN
    Public Land Mobile Network
    QoS
    Quality of Service
    RAB
    Radio Access Bearer
    RAN
    Radio Access Network
    RANAP
    Radio Access Network Application Part
    RB
    Radio Bearer
    RNC
    Radio Network Controller
    RNSAP
    Radio Network Subsystem Application Part
    RRC
    Radio Resource Control
    SRNC
    Serving RNC
    UE
    User Equipment
    UMTS
    Universal Mobile Telecommunication System
    UL
    Uplink
    UTRAN
    UMTS Terrestrial Radio Access Network
    VoIP
    Voice over IP

Claims (15)

  1. A method of sharing a Radio Access Network (RAN) in one or more areas by at least two operators, in which method the determination whether to grant admission or not of a User Equipment (UE) to the RAN is performed in an admission control algorithm, wherein a Radio Network Controller (RNC) is reading Network Resource Identifier (NRI) information, and said read NRI information is used in a service admission control to check a plurality of service admission parameters as a part of a set of admission control parameters to grant or reject the requested service depending on whether the operator associated with the NRI has invested in needed technology or not, wherein said NRI information is contained in an "Initial Direct Transfer" message sent by the UE when requesting a service, and traffic is routed to correct Core Network (CN) by a Serving Radio Network Controller (SRNC), characterized in that the service admission control is performed by the SRNC and in that a UE request is sent to a Drift Radio Network Controller (DRNC) by the SRNC only if the service admission control admits the request, and, wherein the DRNC is arranged to inform the SRNC about wishes to set up or modify a radio bearer, the SRNC then performs the service admission control and grants the requested set up or modification from DRNC if admitted by the service admission control.
  2. The method according to claim 1, characterized in that said plurality of service admission parameters comprises Operation and Management (O&M) parameters set by Universal Mobile Telecommunication System (UMTS), Terrestrial Radio Access Network (UTRAN), supporting company or set by network manufacturer.
  3. The method according to claim 2, said network sharing being performed as standardized in 3rd Generation Partnership Project (3GPP) for Release 6, characterized in that said plurality of service admission parameters comprises High Speed Downlink Packet Access (HSDPA), Operator A = True/False, HSDPA, Operator B = True/False; High Speed Uplink Packet Access (HSUPA), Operator A = True/False, HSUPA, Operator B = True/False; Multimedia Broadcast Multicast Service (MBMS), Operator A = True/False, MBMS, Operator B = True/False; and/or Voice over IP (VoIP), Operator A = True/False, VoIP, Operator B = True/False.
  4. The method according to any of the preceding claims, characterized in that the Radio Network Controller (RNC) maps information about the operator to an integer identity number for the operator.
  5. The method according to claim 4, characterized in that, in case of a request of resources for a new radio bearer, operator information is supplied to the admission control and a Quality of Service (QoS) admission control of the request is performed, and, if the request is admitted by both admission controls, the service admission control relies on operator information sent at each request of a radio bearer change, or on operator information for the radio bearer stored together with the bearer's identity number.
  6. The method according to claim 5, characterized in that the allowance of a requested radio bearer change is checked in the service admission control from a service perspective.
  7. The method according to any of the preceding claims, characterized in that admission and congestion controls on the cells of a specific node are performed by a Controlling Radio Network Controller (CRNC) of said node.
  8. A Radio Access Network (RAN) adapted to be shared in one or more areas by at least two operators, comprising admission control means to determine whether to grant admission of a User Equipment (UE) to the RAN, or not, a Radio Network Controller (RNC) arranged to read Network Resource Identifier (NRI) information and sending said read NRI information to said admission control means to check a plurality of service admission parameters as a part of a set of admission control parameters to grant or reject the requested service depending on whether the operator associated with the NRI has invested in needed technology or not, said NRI information is contained in an "Initial Direct Transfer" message sent by a UE, when requesting a service, and a Serving Radio Network Controller (SRNC) is arranged to route traffic to correct Core Network (CN), characterized in that the SRNC is arranged to perform the service admission control, in that the SRNC is adapted to send a UE request to a Drift Radio Network Controller (DRNC) only if the service admission control admits the request, in that the DRNC is arranged to inform the SRNC about desires to set up or modify a radio bearer, and in that the SRNC is arranged to then perform the service admission control and grant the requested set up or modification from DRNC if admitted by the service admission control.
  9. The network according to claim 8, characterized in that said plurality of service admission parameters comprises Operation and Management (O&M) parameters set by Universal Mobile Telecommunication System (UMTS), Terrestrial Radio Access Network (UTRAN), supporting company or set by network manufacturer.
  10. The network according to claim 9, said network sharing being performed as standardized in 3rd Generation Partnership Project, 3GPP, for Release 6, characterized in that said plurality of service admission parameters comprises High Speed Downlink Packet Access (HSDPA), Operator A = True/False, HSDPA, Operator B = True/False; High Speed Uplink Packet Access (HSUPA), Operator A = True/False, HSUPA, Operator B = True/False; Multimedia Broadcast Multicast Service (MBMS), Operator A = True/False, MBMS, Operator B = True/False; and/or Voice over IP (VoIP), Operator A = True/False, VoIP, Operator B = True/False.
  11. The network according to any of the claims 8 - 10, characterized in that the Radio Network Controller (RNC) is arranged to map information about the operator to an integer identity number for the operator.
  12. The network according to claim 11, characterized in that, in case of a request of resources for a new radio bearer, said admission control means are arranged to receive operator information and perform admission control and a Quality of Service (QoS) admission control of the request, and, if the request is admitted by both controls, the service admission control is relying on operator information sent at each request of a radio bearer change, or on operator information for the radio bearer stored together with the bearer's identity number.
  13. The network according to claim 12, characterized in that the admission control means are arranged to check the allowance of a requested radio bearer change in said service admission control from a service perspective.
  14. The network according to any of the claims 8 - 13, characterized in that a Controlling Radio Network Controller (CRNC) of a specific node is arranged to control said node admission and congestion on the cells of said node.
  15. The network according to any of the claims 8 - 14, wherein more than one RNC are involved in the connection between a UE and the Core Network (CN), characterized in that each RNC is either a Serving Radio Network Controller (SRNC) or a Drift Radio Network Controller (DRNC).
EP05822023A 2004-12-30 2005-12-21 Method and system for service access control in shared networks Not-in-force EP1834499B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SE0403221A SE529376C3 (en) 2004-12-30 2004-12-30 Method and system for controlling service access in shared networks
PCT/SE2005/001995 WO2006071179A1 (en) 2004-12-30 2005-12-21 Method and system for service access control in shared networks

Publications (3)

Publication Number Publication Date
EP1834499A1 EP1834499A1 (en) 2007-09-19
EP1834499A4 EP1834499A4 (en) 2011-09-28
EP1834499B1 true EP1834499B1 (en) 2012-04-25

Family

ID=34102163

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05822023A Not-in-force EP1834499B1 (en) 2004-12-30 2005-12-21 Method and system for service access control in shared networks

Country Status (8)

Country Link
US (1) US7894338B2 (en)
EP (1) EP1834499B1 (en)
AT (1) ATE555625T1 (en)
DK (1) DK1834499T3 (en)
ES (1) ES2386686T3 (en)
NO (1) NO20073001L (en)
SE (1) SE529376C3 (en)
WO (1) WO2006071179A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103797841A (en) * 2013-08-19 2014-05-14 华为技术有限公司 Admission control method and device

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4645338B2 (en) * 2005-07-20 2011-03-09 日本電気株式会社 Wireless communication system, wireless control station, and service changing method used for them
CN100455138C (en) * 2006-08-01 2009-01-21 上海华为技术有限公司 Method for resharing service after kernal network fault recovery
WO2008084316A1 (en) 2007-01-08 2008-07-17 Nokia Corporation Method for fast circuit switched service enabling handover from packet-switched only networks
CN100488314C (en) * 2007-01-24 2009-05-13 中兴通讯股份有限公司 A method for restricting the access of the user terminal in the 3G network
WO2008110093A1 (en) * 2007-03-09 2008-09-18 Huawei Technologies Co., Ltd. Method and device for accessing net to manage radio resources
CN101267579A (en) * 2007-03-13 2008-09-17 华为技术有限公司 Processing method, device and system for direct transfer message
JP4844751B2 (en) 2007-03-30 2011-12-28 日本電気株式会社 Network resource management system, method, and radio control apparatus
US8706123B2 (en) * 2008-03-24 2014-04-22 Qualcomm Incorporated Common data channel resource usage report
KR20140062177A (en) * 2008-04-25 2014-05-22 인터디지탈 패튼 홀딩스, 인크 Method and apparatus for cell reselection in a mobile communications network
US8463277B2 (en) * 2008-06-09 2013-06-11 Mediatek Inc. Method for allocating paging resource to a mobile station having multiple subscriber identities and resource allocating apparatus thereof
KR101277102B1 (en) 2008-10-31 2013-06-20 닛본 덴끼 가부시끼가이샤 Mobile communication system, core network node, control station, and communication method
CN102204368B (en) 2008-10-31 2015-01-07 日本电气株式会社 Mobile communication system, control station, base station, communication method
KR20100083271A (en) * 2009-01-13 2010-07-22 삼성전자주식회사 Method and apparatus for sharing mobile broadcasting service
US8290518B2 (en) * 2009-02-05 2012-10-16 Zte (Usa) Inc. Paging mechanisms for mobile stations with multiple subscriptions
ES2351830B1 (en) * 2009-02-05 2011-12-12 Vodafone España, S.A.U. NETWORK PROCEDURE AND CONTROLLER TO SWITCH BETWEEN SHARED NETWORK ARCHITECTURES.
KR101308864B1 (en) 2009-04-20 2013-09-16 닛본 덴끼 가부시끼가이샤 Gateway apparatus, communication control method, and non-transitory computer readable medium storing communication control program
CN101674628A (en) * 2009-09-30 2010-03-17 中兴通讯股份有限公司 Route reselection method and radio network controller
CN102695211A (en) * 2011-03-24 2012-09-26 中兴通讯股份有限公司 Method and system for radio resource control
KR101515594B1 (en) * 2012-05-21 2015-04-28 주식회사 케이티 Apparatus for processing digital signal, apparatus for processing wireless siganl and signal processing system
US20210051523A1 (en) * 2018-01-25 2021-02-18 Nokia Solutions And Networks Oy Method, Apparatus and Computer Program for Modification of Admission Control Criteria

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001091382A1 (en) * 2000-05-22 2001-11-29 Nokia Corporation System and method for providing a connection in a communication network
ES2282350T3 (en) 2001-07-27 2007-10-16 Telefonaktiebolaget Lm Ericsson (Publ) REDIRECTION OF SUBSCRIBERS.
MXPA04012158A (en) * 2002-06-06 2005-04-19 Thomson Licensing Sa Interworking function (iwf) as logical radio network controller (rnc) for hybrid coupling in an interworking between wlan and a mobile communications network.
US7415274B2 (en) 2003-02-19 2008-08-19 Nokia Corporation Routing procedure for a communication system
EP1609328A1 (en) 2003-03-20 2005-12-28 Telefonaktiebolaget LM Ericsson (publ) Method for transferring a mobile terminal in e.g. an umts-network from one server node in a pool to another server node in the same pool
JP4303236B2 (en) * 2004-12-07 2009-07-29 三星電子株式会社 Method and apparatus for notifying radio access network of core network selected by terminal in network sharing system
US7904055B2 (en) * 2005-08-23 2011-03-08 Lg Electronics Inc. Communicating message in mobile communication system
CN101300754B (en) * 2005-10-31 2012-02-22 Lg电子株式会社 Method of transmitting and receiving radio access information in a wireless mobile communications system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103797841A (en) * 2013-08-19 2014-05-14 华为技术有限公司 Admission control method and device
CN103797841B (en) * 2013-08-19 2017-11-24 华为技术有限公司 A kind of admittance control method and device

Also Published As

Publication number Publication date
NO20073001L (en) 2007-09-24
EP1834499A4 (en) 2011-09-28
ATE555625T1 (en) 2012-05-15
SE529376C2 (en) 2007-07-24
US7894338B2 (en) 2011-02-22
SE0403221D0 (en) 2004-12-30
SE529376C3 (en) 2007-08-21
EP1834499A1 (en) 2007-09-19
US20080112353A1 (en) 2008-05-15
SE0403221L (en) 2006-07-01
DK1834499T3 (en) 2012-07-23
ES2386686T3 (en) 2012-08-27
WO2006071179A1 (en) 2006-07-06

Similar Documents

Publication Publication Date Title
EP1834499B1 (en) Method and system for service access control in shared networks
US7471957B2 (en) Paging method and system for a radio access network
EP1532779B1 (en) Mbms ptp and ptm channel change
EP1670275B1 (en) Method and apparatus for informing a radio access network of a selected core network from user equipment in a network sharing system
CA2383366C (en) Domain selecting system and method
EP2514240B1 (en) Resource sharing in communications systems
EP1360858B1 (en) Method for determining whether to grant access of a user equipment to a radio access network
KR101341559B1 (en) Flexible Network Architecture with User Group Support
EP1657862B1 (en) Centralized dynamical resource reservation method based on the exchange of service specific capacity settings in a multi-RAT network
CN102223691B (en) Changing method in mobile communication system
US20040029587A1 (en) Method for supporting a handover between radio access networks
EP1440594B1 (en) Forwarding a mobile subscriber identity between core network nodes
US20040213297A1 (en) Method for multiplexing data streams onto a transport bearer between an originating network node and a receiving network node
EP1429567B1 (en) Improved OpenRAN architecture for Radio Network Controller, Mobile Communication System and method of controlling Radio Base Station device
DK2074856T3 (en) RAB-Differentiation between network operators in a shared network
GB2369002A (en) Mobility management in a UMTS network
AU2001265850A1 (en) Method for supporting a handover between radio access networks

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: 20070730

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20110829

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/00 20090101AFI20110824BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602005033919

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04Q0007380000

Ipc: H04W0028160000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/16 20090101AFI20111024BHEP

Ipc: H04W 4/00 20090101ALI20111024BHEP

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 BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

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: AT

Ref legal event code: REF

Ref document number: 555625

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120515

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602005033919

Country of ref document: DE

Effective date: 20120614

REG Reference to a national code

Ref country code: DK

Ref legal event code: T3

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20120425

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2386686

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20120827

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 555625

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120425

REG Reference to a national code

Ref country code: EE

Ref legal event code: FG4A

Ref document number: E007027

Country of ref document: EE

Effective date: 20120717

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

Ref country code: PL

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: 20120425

Ref country code: IS

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: 20120825

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: 20120425

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: 20120425

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

Ref country code: SI

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: 20120425

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: 20120726

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: 20120827

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: 20120425

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

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: 20120425

Ref country code: SK

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: 20120425

Ref country code: CZ

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: 20120425

Ref country code: RO

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: 20120425

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: 20120425

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

26N No opposition filed

Effective date: 20130128

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602005033919

Country of ref document: DE

Effective date: 20130128

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

Ref country code: BG

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: 20120725

Ref country code: MC

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

Effective date: 20121231

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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 NON-PAYMENT OF DUE FEES

Effective date: 20121231

Ref country code: LI

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

Effective date: 20121231

Ref country code: IE

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

Effective date: 20121221

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

Ref country code: TR

Payment date: 20131126

Year of fee payment: 9

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: 20121221

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

Ref country code: HU

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: 20051221

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

Ref country code: ES

Payment date: 20141226

Year of fee payment: 10

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

Ref country code: IT

Payment date: 20141219

Year of fee payment: 10

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

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

Ref country code: LT

Payment date: 20151120

Year of fee payment: 11

Ref country code: EE

Payment date: 20151211

Year of fee payment: 11

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

Ref country code: LV

Payment date: 20151211

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

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: 20151221

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: 20151222

REG Reference to a national code

Ref country code: LT

Ref legal event code: MM4D

Effective date: 20161221

REG Reference to a national code

Ref country code: EE

Ref legal event code: MM4A

Ref document number: E007027

Country of ref document: EE

Effective date: 20161231

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

Ref country code: LT

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

Effective date: 20161221

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

Ref country code: LV

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

Effective date: 20161221

Ref country code: TR

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

Effective date: 20151221

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

Ref country code: EE

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

Effective date: 20161231

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20180629

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

Ref country code: FI

Payment date: 20181210

Year of fee payment: 5

Ref country code: DK

Payment date: 20181221

Year of fee payment: 14

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

Ref country code: DE

Payment date: 20191210

Year of fee payment: 15

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

Ref country code: FR

Payment date: 20191219

Year of fee payment: 15

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

Ref country code: GB

Payment date: 20191220

Year of fee payment: 15

REG Reference to a national code

Ref country code: FI

Ref legal event code: MAE

REG Reference to a national code

Ref country code: DK

Ref legal event code: EBP

Effective date: 20191231

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 NON-PAYMENT OF DUE FEES

Effective date: 20191221

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

Ref country code: DK

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

Effective date: 20191231

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602005033919

Country of ref document: DE

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

Effective date: 20201221

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: 20201231

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

Ref country code: DE

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

Effective date: 20210701

Ref country code: GB

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

Effective date: 20201221