EP2534884B1 - Method and telecommunications infrastructure enabling localized time controlled access for a device - Google Patents
Method and telecommunications infrastructure enabling localized time controlled access for a device Download PDFInfo
- Publication number
- EP2534884B1 EP2534884B1 EP11702985.0A EP11702985A EP2534884B1 EP 2534884 B1 EP2534884 B1 EP 2534884B1 EP 11702985 A EP11702985 A EP 11702985A EP 2534884 B1 EP2534884 B1 EP 2534884B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- access
- time interval
- network node
- grant time
- access grant
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 19
- 238000004891 communication Methods 0.000 description 14
- 230000006978 adaptation Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
Definitions
- the invention relates to the field of telecommunications. More specifically, the invention relates to the field of controlling access for a device to a telecommunications infrastructure.
- Telecommunications networks that provide wireless access (e.g. GSM, UMTS, WiMax, LTE, WLAN) have developed tremendously over the past years.
- voice and data services can be provided to communication devices having a high mobility, i.e. the communication devices are not bound to a particular location and are freely movable through the area covered by the network or the networks of roaming partner operators.
- a gateway node of the telecommunications network enables connection to a further network, for example a network based on IP, such as the internet.
- M2M machine-to-machine
- MTC machine-type communications
- M2M is currently being standardized in 3GPP (see e.g. TS 22.368).
- MTC applications typically involve hundreds, thousands or millions of communication devices which each act as a communication device to the telecommunication network.
- Such communication devices may be stationary or non-stationary.
- An example involves the electronic reading of e.g. 'smart' electricity meters at the homes of a large customer base over the telecommunications network from a server connected to the further network.
- sensors examples include sensors, meters, vending or coffee machines, car meters for route pricing applications, navigation equipment, etc. that can be equipped with communication modules that allow exchanging in- formation with other equipment such as a data processing centre over the telecommunications network.
- a data processing centre may also be monitored by the server.
- the data processing centre may e.g. store the data and/or provide a schedule for maintenance people to repair or refill a machine, meter or sensor or may update information in the device.
- the data processing centre may be configured for processing data received from mobile communications devices, e.g. for road pricing applications.
- a device may need to send/receive data regularly to/from a server, for instance every 24 hours, but has no further requirements about a specific time.
- a network operator may decide to schedule network access for these devices in a non-busy time period, as was e.g. disclosed in EP 2 096 884 .
- Granting and denying access can pertain to network attaches as well as connection setups and allows the network operator to control the use of network resources.
- the group time interval may not be a suitable period in all parts of a telecommunications network or for visited networks in case of moving devices, such as navigation systems or road pricing devices in vehicles.
- the non-busy period of the home operator is not necessarily a non-busy period for the visited operator, wherein the telecommunications network of the home operator and the telecommunications network of the visited operator form a telecommunications infrastructure. This could be because the visited and home operators are in different time zones, or because the visited operator has already scheduled devices for other M2M applications in the group time interval assigned by the home operator.
- the devices may still need to send information to or retrieve information from the server, e.g. map updates for a navigation device.
- US 6 230 017 B1 discloses that a mobile station is permitted to operate only in cells identified in the subscriber's record in the HLR.
- the information for geographically restricting operation includes a first list of allowed cells and a second list of allowed cells.
- the first list is utilized for determining in what cells the mobile station can operate during a first time period
- the second list is utilized for determining in what cells the mobile station can operate during a second time period.
- a method for controlling wireless access to a telecommunications infrastructure for a device is disclosed.
- a first access grant time interval applicable for granting access for the device to the telecommunications infrastructure is stored in a device register system.
- the device register system may e.g. register information about the subscription of the device and/or information on the device itself.
- the first access grant time interval is applied when the device requests access to the telecommunications infrastructure via a first network node of the telecommunications infrastructure.
- a second access grant time interval is applied in a second network node of the telecommunications infrastructure when the device requests access via the second network node.
- the second access grant time interval is applicable for granting access for the device to the telecommunications infrastructure and is different from the first access grant time interval.
- a telecommunications infrastructure comprising a device register system, a first network node and a second network node.
- the device register system is configured for storing a first access grant time interval applicable for granting access for the device to the telecommunications infrastructure.
- the device register system may e.g. register information about the subscription of the device and/or information on the device itself.
- the first network node is configured for granting access during the first access grant time interval when the device requests access via the first network node.
- the second network node comprises or is configured to exchange information with an access controlling system configured for applying a second access grant time interval to control access to the telecommunications infrastructure when the device requests access via the second network node.
- the second access grant time interval is applicable for granting access for the device to the telecommunications infrastructure and is different from the first access grant time interval.
- a visiting network for the device comprising the second network node of the telecommunications infrastructure is disclosed.
- the disclosed method and system enable the (first) access grant time interval that is applicable for the device to (temporarily) be adapted to a different (second) access grant time interval for that same device in a different part of the telecommunications infrastructure.
- the method and system provide flexibility in the access grant time interval in different parts of the network. Accordingly, local circumstances in the different parts of the telecommunications infrastructure may be taken into account when deciding on the access of the device to the telecommunications infrastructure.
- Examples of such local circumstances include a telecommunication network covering multiple time zones, wherein the time zone for the first network node differs from the time zone for the second network node. It also enables operators of visited networks employing a second network node to adapt the access grant time interval of the first network node of the home network of the device according to the needs or requirements of the visited network, as defined in claims 2 and 8.
- the visited network operator has the ability to adapt the access grant time interval in which access is granted to a grant access time interval that is better suited to serve its own needs or requirements regarding e.g. network traffic load or contractual obligations to third parties.
- the adaptation of the first access grant time interval may comprise shifting the entire time interval, or modifying at least one of the start time and the end time of the first access grant time interval or to split the time interval into multiple intervals.
- the access grant time interval may be the time interval assigned to a single device or to a group of devices.
- access to the telecommunications infrastructure via the second network node may be granted outside the first and/or second access grant time interval.
- access outside the first and/or second access grant time interval may be granted under different conditions, such as higher prices, lower quality of service etc.
- the conditions may depend on one or more network parameters at the second network node, e.g. the traffic load.
- the conditions may be communicated to the device with either an accept message or a reject access message. If an accept message is used, the device is responsible for not establishing the connection if it does not want to accept the conditions.
- the device may repeat a request for the connection setup in the case that it wants to accept the conditions, the second network, being aware that this is a re-request can immediately grant access.
- the device may also beforehand communicate acceptable conditions to the second network node with the request for access to the telecommunications infrastructure.
- a device configured for performing this functionality is also disclosed in the present application.
- telecommunications infrastructure may either include a single telecommunications network (e.g. covering multiple time zones) or multiple telecommunications networks (e.g. located in two or more operator domains between which the device may roam).
- Examples of the device register system include a Home Location Register (HLR) of a 2G/3G network, a Home Subscriber Server (HSS) of an LTE network or an AAA database of a WLAN network.
- Examples of first and second network nodes include SGSNs of a telecommunications infrastructure comprising a 2G/3G network, MMEs of a telecommunications infrastructure comprising an LTE network or AAA proxies or Wireless Access Points of a telecommunications infrastructure comprising a WLAN network.
- the second network node is informed of the first access grant time interval, e.g. by transferring information regarding this time interval to the second network node. Accordingly, the second network node is informed about the preference and/or contractual obligations for the device when accessing the telecommunications infrastructure via the first network node and can adapt the first access grant time interval to the second access grant time interval as far as necessary.
- the difference between the first and second access grant time interval may result in an approval of access by a device register system in a first part of the network for access to the telecommunications infrastructure, whereas the device is denied access to the telecommunications infrastructure at the second network node.
- the second network node may send an information message to the device register system informing it that the an acceptable access request of the device was nevertheless rejected.
- accounting messages may be used for this purpose, informing the device register system (or other accounting system in the home network) of a "null session".
- the second network node preferably informs the device register system of the fact that it wants to locally apply the second access grant time interval such that the device register system refrains from applying the first access grant time interval.
- the device may be informed about the applicable second access grant time interval, e.g. with the reject access message.
- the device register system may also be informed about the applicable second access grant time interval as defined in claims 4 and 10. This provides information to the operator of a home network when traffic can be expected and enables the operator of the devices to obtain information on their devices from the device register system for e.g. troubleshooting or data arrival prediction purposes.
- a forbidden time interval may apply during which the home network of the device will not accept access by the device to the telecommunications infrastructure.
- the device register system may store the first access grant time interval and the forbidden time interval.
- the forbidden time interval is taken into account by the second network node when applying or selecting the second access grant time interval.
- the forbidden time interval e.g. stored in the HLR or HSS of the home network, should be obeyed and cannot be adapted by further nodes or visited network operators.
- the forbidden time interval is determined based on the expected and/or observed load in the home network, service windows and agreements with M2M application owners.
- the forbidden time interval can be adapted based on the information received from one or more of the second network nodes.
- the second network node may, in an embodiment of the invention, retrieve at least the access grant time interval and possibly also the forbidden time interval from the device register system storing the first access grant time interval and/or the forbidden time interval (e.g. from the HLR (in the home network)).
- the second network node may then, in an embodiment of the invention, adapt the access grant time interval to a time interval that is more suitable.
- the adaptation of the time interval may be a shift of the time interval.
- the adaptation can be determined by the second network node itself, e.g. based on expected and/or observed load for this network node or on information from a time register.
- the time register may contain service windows, agreements with other M2M application customers and expected and/or observed network load.
- FIG. 1 shows a schematic illustration of a telecommunications network 1.
- the telecommunications network 1 enables data sessions between an application server 2 and a communication device 3 over a data network 4, wherein access of the communication device 3 to the telecommunications network 1 is wireless.
- the lower branch of FIG. 1 represents a GPRS or UMTS telecommunications network comprising a Gateway GPRS Support Node (GGSN), a Serving GPRS Support Node (SGSN) and a Radio Access Network (GERAN or UTRAN).
- GGSN Gateway GPRS Support Node
- SGSN Serving GPRS Support Node
- GERAN Radio Access Network
- the access network comprises a Base Station Controller (BSC) connected to a plurality of Base Station Transceivers (BTSs), both not shown.
- BSC Base Station Controller
- BTSs Base Station Transceivers
- RNC Radio Network Controller
- the GGSN and the SGSN are conventionally connected to a Home Location Register (HLR) that contains subscription information of the communication devices 3.
- HLR Home Location Register
- the HLR is combined with an authentication centre (AuC) for authenticating communication devices 3 in the network.
- AuC authentication centre
- the upper branch in FIG. 1 represents a next generation telecommunications network, commonly indicated as Long Term Evolution (LTE) or Evolved Packet System (EPS).
- a network comprises a PDN Gateway (P-GW) and a Serving Gateway (S-GW).
- the E-UTRAN of the EPS comprises evolved NodeBs (eNodeBs or eNBs), not shown, providing wireless access for a communication device 3 that is connected to the S-GW via a packet network.
- the S-GW is connected to a Home Subscriber Server HSS and a Mobility Management Entity MME for signalling purposes.
- the HSS includes a subscription profile repository and an authentication centre (AuC).
- the operator of application server 2 may have access to the HLR/HSS of the telecommunications network.
- FIG. 2 is a telecommunications infrastructure 10 having two operator domains according to an embodiment of the invention.
- FIG. 2 also shows two mobile communications devices 3A and 3B.
- Device 3A is within coverage of the home operator
- device 3B is within coverage of a visited network of a visited operator.
- Both devices 3A, 3B are M2M devices and make use of a subscription that allows them to access the network of the home operator within a specific access grant time interval, in this case common to both devices.
- the time interval for this group of devices 3A, 3B is registered in the HLR (in the home network).
- the SGSN in case of UMTS
- MME in case of LTE
- the SGSN/MME will allow device 3A to access the network.
- the SGSN/MME will normally deny device 3A to access the network.
- the SGSN/MME may inform device 1 about the applicable access grant time interval, so device 3A will know the earliest possible time that it can attempt to successfully access the network.
- device 3A may still access the network, albeit under amended conditions e.g. at a higher charge and/or at a lower quality of service.
- the SGSN/MME When device 3B accesses the telecommunications infrastructure 10, its request for access is received by the SGSN/MME in the domain of the visited network operator.
- This SGSN/MME will also request information from the HLR (located with the home operator) and may indicate that it intends to apply a local time interval for controlling access.
- the information from the HLR may again include the access grant time interval and may also include the forbidden time interval from the HLR.
- the SGSN/MME checks whether this access grant time interval is a suitable time interval for the visited network.
- the visited network may have a "time register" that contains conditions and time intervals, which register the SGSN/MME can consult to decide on a proper access grant time interval (this time register may be located in the foreign HLR or elsewhere).
- the visited SGSN/MME decides to adapt the time interval (marked 'granted 02:00-04:00' in the figure) it will have to ensure that the adapted time interval is not within the forbidden time interval that is specified by the home operator. A further adjustment may be needed to resolve a conflict with the forbidden time interval.
- the SGSN/MME decides to adapt it to 02:00-04:00, which does not conflict with 'forbidden 07:00-12:00' specified by the home operator.
- the SGSN/MME will then allow device 3B to access the infrastructure 10 if the time is within the adapted time interval (and provided that all other conditions are met).
- the SGSN/MME When the current time is outside the adapted time interval, the SGSN/MME will deny device 3B to access the infrastructure. Optionally the SGSN/MME may inform device 3B about the adapted time interval, so device 3B will know the earliest possible time that it can attempt to successfully access the network.
- the M2M device 3B may optionally store this adapted time interval for later use.
- the visited SGSN/MME may optionally inform the home operator, e.g. the HLR, about this adaptation.
- the home operator e.g. the HLR
- the forbidden time interval stored in the home HLR is defined by the home operator. It can be based on parameters such as: expected and/or observed network load, agreements with other M2M applications, service windows, and agreements with the owner of the M2M server for the specific applications (e.g. the M2M server has a specific service window, or has other reasons for not being able to serve the M2M devices during the forbidden period).
- the invention is not limited to a single time interval and that adapting a time interval may also comprise splitting a time interval into multiple time intervals or joining multiple time intervals.
- the information with regard to time intervals can be formulated absolute, e.g. "between 16.00 and 17.00” or relative, e.g. "between one and two hours from now", “within 3 hours”.
- FIG. 3 depicts another embodiment of the invention applicable in a single operator domain, wherein the SGSN can adapt the time interval on a local or regional basis. That would distribute the burden on the centralized GGSN/PDN-GW and HLR. This is especially advantageous when a dedicated HLR and GGSN/PDN-GW are used to handle M2M traffic or when a single operator network spans multiple time zones.
- the (first) access grant time interval and the forbidden time interval as well as the adapted (second) access grant time interval and the forbidden time intervals are not complementary to each other, i.e. that these do not cover an entire reference period (e.g. a 24-hour period). This is indicated in FIGS. 4A and 4B .
- the adapted time interval is smaller than the group time interval (marked 'access grant time') interval and partly overlaps that interval.
- the reference period may e.g. be one day, one week or one month.
- FIG. 5 provides a flow chart showing an implementation example of applying a local access grant time interval in the telecommunications infrastructure 10 of FIG. 2 or 3 .
- the flow chart depicts a packet switched (PS) attach request by device 3A formerly connected to an old SGSN and now connected to a new SGSN (e.g. resulting from a hand-over involving switching SGSN areas) for which a locally defined access grant time interval applies.
- PS packet switched
- the old SGSN functions as a first network node
- the new SGSN functions as a second network node.
- the HLR is the device register system.
- step 1 device 3A initiates a PS Attach procedure by generating an Attach Request message to the new SGSN.
- the message contains the IMSI of device 3A and possibly indicates an Access Condition.
- P-TMSI Packet-Temporary Mobile Subscriber Identity
- the parameter(s) reflecting the Access Condition may contain information about the ability of the device 3A to access the infrastructure 10 outside the applicable access grant time interval, e.g. the price or acceptable quality of service.
- step 2 since the actual serving network node has changed from an old SGSN to a new SGSN and if the device 3A has identified itself by IMSI, the new SGSN performs an Identity Check to the old SGSN. If the device 3A is unknown in both the old and the new SGSN, the new SGSN performs an Identity Check with the device 3A wherein device 3A responds with the IMSI (step 3).
- Step 4 involves authentication. IMEI checking may also be performed (not shown).
- the new SGSN informs the HLR by sending an Update Location message in step 5.
- the Update Location message contains the IMSI of the device 3A and the address of the new SGSN.
- the Update Location message also contains an indicating field LTI indicating that the new SGSN applies a local access grant time interval. The LTI indication may be used by the HLR to ignore the access grant time interval defined in the HLR and applicable when requesting access via the old SGSN.
- the HLR sends a Cancel Location message to the old SGSN, which message is acknowledged by the old SGSN.
- the HLR sends an Insert Subscriber Data message to the new SGSN.
- the parameters contained in this message may include the IMSI of device 3A, the access grant time interval as stored in the HLR, the forbidden time interval and, possibly, the access conditions.
- the new SGSN validates whether the device 3A is still within reach of the SGSN and may adapt the access grant time interval according to local requirements or needs.
- the forbidden time interval may not be adjusted and the adaptation of the access grant time interval should be such that an overlap with the specified forbidden time interval is avoided.
- step 9 if all checks are successful, the new SGSN returns an Insert Subscriber Data Acknowledgement message to the HLR.
- the message includes the locally adapted access grant time interval that is temporarily stored in the HLR.
- step 10 the HLR acknowledges the Update Location message of step 5 by sending an Update Location Acknowledgement message to the new SGSN.
- step 11 the new SGSN now checks if the Attach Request from the device 3A falls within the adapted access grant time interval as explained previously with reference to FIG. 2 .
- access may still be granted when the Access Conditions received from device 3A in step 1 match the Access Conditions received from the HLR/HSS in step 7.
- Attach Request of step 1 falls within the adapted access grant time.interval or if the Access Conditions are fulfilled an Attach Accept is sent to the device 3A as illustrated by step 12a.
- This Attach Accept message contains the IMSI, the applicable access time interval and, possibly, the forbidden time interval.
- the device 3A is now aware when it is allowed to send Attach Requests, at least until handover to a further new SGSN.
- Attach Request does not fall within the Local Access Grant Time interval or the Access Conditions are not fulfilled.
- Attach Reject message contains the IMSI, the applicable access time interval and, possibly, the forbidden time interval.
- the device 3A is now aware when it is allowed to send Attach Requests, at least until handover to a further new SGSN.
- device 3A may repeat an Attach Request to the new SGSN at a later time within the communicated access grant time interval or when it meets the Access Conditions when outside the local access grant time interval and forbidden time interval.
- FIG. 6 provides a schematic illustration of a telecommunications infrastructure 20 according to a third embodiment of the invention.
- the telecommunications infrastructure 20 involves a WLAN network comprising a user database DB in a combination with an AAA server of a wireless internet provider WISP as a device register system and a AAAn proxy as a second network node.
- a roaming mechanism is implemented based on RADIUS roaming using the RADIUS AAA protocol.
- RADIUS AAA is defined in RFC 2138 and RFC 2139.
- the end-user has a subscription with the WISP.
- the WISP hands out credentials (e.g. username/password) to the end-user.
- the user can login with his device 3 and use the hotspot if the hotspot owner and WISP belong to the same "alliance" (i.e. having roaming agreements in place, either direct or via an intermediate party).
- the relevant network elements are AAA Proxy, AAA Server and Access Controller and Access Point.
- the Access Controller and Access Point are combined into the Public WiFi Access Point.
- the AAA Proxy is referred to as 3GPP AAA Proxy
- the AAA Server is called 3GPP AAA Server.
- the Access Controller is called Wireless Access Gateway, which in FIG. 6 is combined into the Public WiFi Access Point.
- AAA proxies may be present in the infrastructure 20.
- the WISP can control whenever a device 3 is allowed access to the infrastructure 20 by defining a (first) access grant time interval in the user database.
- AAA server receives incoming access requests, checks the user credentials and, possibly, applies the first access grant time interval, to decide whether or not a particular device 3 may access the infrastructure.
- FIG. 7 provides a diagram showing an implementation example of applying a local access grant time interval in the telecommunications infrastructure of FIG. 6 .
- a device 3 connects to a WiFi hotspot outside its access grant time interval as defined by the global WISP.
- the local hotspot provider decides to adapt the access grant time interval.
- step 1 the device 3 requests access to the public WiFi Access Point (AP) providing user credentials.
- the WiFi AP forwards a RADIUS Access Request to the AAA Proxy in step 2 that forwards the RADIUS AAA Request to the AAA Server in step 3.
- the AAA Proxy includes a RADIUS parameter, e.g. an indicating field LTI indicating that the AAA Proxy applies a local access grant time interval, in the forwarded message.
- the LTI indication may be used by the AAA Server to ignore the access grant time interval defined in the user database.
- the LTI indication may also be provided by the WiFi AP.
- step 4 the AAA Sever verifies the user credentials and profile. In this step, it will appear if a time-based subscription applies for device 3A
- step 5 if the AAA Server has positively verified the credentials, it is observed that the access request is received outside the first access grant time interval and outside a forbidden time interval.
- the LTI indicator may be used to disregard application of the first access grant time interval stored in the user database.
- step 6 the AAA Server sends an Access Accept message as the credentials are positively verified and the first access grant time interval is disregarded.
- the Access Accept message includes the first access grant time interval and the forbidden time interval.
- step 7 the AAA Proxy adapts the access grant time interval received from the AAA Server. As the Access Request from step 1 is outside this adapted time interval, the AAA Proxy changes the Access Accept message from step 6 in an Access Reject message in steps 8 and 9, even though the credentials have been positively verified and, possibly, the Access Request in step 1 was received within the first access grant time interval. Steps 7 and 8 may alternatively be performed by the WiFi AP.
- the Access Reject message of step 8 contains the adapted access grant time interval and, optionally, the forbidden time interval, to inform device 3 when it may access.
- RADIUS AAA is a stateless protocol
- the AAA server and user database is preferably informed of the Access Reject message. This is advantageously performed by making use of the existing Accounting messages as indicated in FIG. 7 .
- the AAA Proxy sends an Accounting Start message to AAA Server (step 10a) which is stored in Accounting DB (step 10b).
- AAA Proxy sends Accounting Stop message indicating this is a null session to AAA Server (step 11a) which is stored in Accounting DB (step 11b).
- the accounting database always reflects Accounting Start and Stop messages for all session wherein the AAA Server has sent an Access Accept message as in step 6. It should be appreciated that the order of steps 10b and 11a may be reversed depending on how fast the AAA Server processes accounting messages.
- the AAA Sever may identify that for a particular device 3 a time-based subscription for which higher prices can be charged in certain time periods is enabled. Then, either the AAA Proxy or the Access Point will determine that at the current local time and the given subscription type the end-user is only allowed access at a higher price. It will allow the device 3 to access the infrastructure and will optionally inform the device 3 of the higher price. The user (or an automated procedure at the device 3) can optionally disconnect immediately if it does not want to accept the higher price.
- the Access Point If the user does not disconnect, the Access Point starts sending Accounting Start/Intermediate/Stop messages as it would in the regular case and these are forwarded to the AAA Server that stores it in the WISP accounting database.
- the Access Point or AAA Proxy will add pricing information to these accounting messages so the WISP will know that the end-user accessed the network at a higher price and can bill the end-user accordingly.
- Pricing information can either be a fixed tariff but can also be an indication of a tariff class.
- the time-based subscription of device 3 may be of such a type that the device 3 is allowed to use the network outside the applicable access grant time interval (except for the forbidden time interval but that during specific time periods it will be provided with a lower quality of service. For instance the bandwidth generated by the device 3 may be limited or its traffic will be labelled with a low priority. Implementing this scenario may be completely up to the discretion of either the Access Point or the AAA Proxy. It could optionally inform the device 3 that a lower quality of service is available and the user (or automated procedure at the device 3) may decide to disconnect from the network.
- the device 3 may be given a choice in steps 8/9 (e.g. either accept the higher price, the lower quality of service or disconnect and wait for a regular time slot).
- FIG. 8 is a schematic illustration of a second network node 30, such as an SGSN/MME or an AAA proxy.
- the second network node 30 comprises an access control system 31.
- the access control system has an input or interface 32 for receiving information (such as the information indicated in FIGS. 5 and 7 received by the new SGSN and the AAA Proxy respectively).
- the access control system 31 also contains a processor 33 for applying the second access grant time interval, possibly by adapting the first access grant time interval.
- time interval could also be used in such a way that access is granted but at other conditions (e.g. lower QoS, higher price).
- One embodiment of the invention may be implemented as a program product for use with a computer system.
- the program(s) of the program product define functions of the embodiments (including the methods described herein) and can be contained on a variety of computer-readable storage media.
- Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive, ROM chips or any type of solid-state non-volatile semiconductor memory) on which information is permanently stored; and (ii) writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive or any type of solid-state random-access semiconductor memory, flash memory) on which alterable information is stored.
- non-writable storage media e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive, ROM chips or any
Description
- The invention relates to the field of telecommunications. More specifically, the invention relates to the field of controlling access for a device to a telecommunications infrastructure.
- Telecommunications networks that provide wireless access (e.g. GSM, UMTS, WiMax, LTE, WLAN) have developed tremendously over the past years. In such networks, voice and data services can be provided to communication devices having a high mobility, i.e. the communication devices are not bound to a particular location and are freely movable through the area covered by the network or the networks of roaming partner operators. A gateway node of the telecommunications network enables connection to a further network, for example a network based on IP, such as the internet.
- The availability of such a telecommunications network connected to the further network has resulted in demands for further services, including services that relate to so-called machine-to-machine (M2M) communications, also referred to as machine-type communications (MTC). M2M is currently being standardized in 3GPP (see e.g. TS 22.368). MTC applications typically involve hundreds, thousands or millions of communication devices which each act as a communication device to the telecommunication network. Such communication devices may be stationary or non-stationary. An example involves the electronic reading of e.g. 'smart' electricity meters at the homes of a large customer base over the telecommunications network from a server connected to the further network. Other examples include sensors, meters, vending or coffee machines, car meters for route pricing applications, navigation equipment, etc. that can be equipped with communication modules that allow exchanging in- formation with other equipment such as a data processing centre over the telecommunications network. Such devices may also be monitored by the server. The data processing centre may e.g. store the data and/or provide a schedule for maintenance people to repair or refill a machine, meter or sensor or may update information in the device. Also, the data processing centre may be configured for processing data received from mobile communications devices, e.g. for road pricing applications.
- Many M2M applications are not time critical. A device may need to send/receive data regularly to/from a server, for instance every 24 hours, but has no further requirements about a specific time. In such cases a network operator may decide to schedule network access for these devices in a non-busy time period, as was e.g. disclosed in
EP 2 096 884 - However, the group time interval may not be a suitable period in all parts of a telecommunications network or for visited networks in case of moving devices, such as navigation systems or road pricing devices in vehicles. As an example, the non-busy period of the home operator is not necessarily a non-busy period for the visited operator, wherein the telecommunications network of the home operator and the telecommunications network of the visited operator form a telecommunications infrastructure. This could be because the visited and home operators are in different time zones, or because the visited operator has already scheduled devices for other M2M applications in the group time interval assigned by the home operator.
- On the other hand, the devices may still need to send information to or retrieve information from the server, e.g. map updates for a navigation device.
- Similar considerations may also apply outside the context of M2M applications.
-
US 6 230 017 B1 discloses that a mobile station is permitted to operate only in cells identified in the subscriber's record in the HLR. The information for geographically restricting operation includes a first list of allowed cells and a second list of allowed cells. The first list is utilized for determining in what cells the mobile station can operate during a first time period, while the second list is utilized for determining in what cells the mobile station can operate during a second time period. - A method is disclosed for controlling wireless access to a telecommunications infrastructure for a device. A first access grant time interval applicable for granting access for the device to the telecommunications infrastructure is stored in a device register system. The device register system may e.g. register information about the subscription of the device and/or information on the device itself. The first access grant time interval is applied when the device requests access to the telecommunications infrastructure via a first network node of the telecommunications infrastructure. However, a second access grant time interval is applied in a second network node of the telecommunications infrastructure when the device requests access via the second network node. The second access grant time interval is applicable for granting access for the device to the telecommunications infrastructure and is different from the first access grant time interval.
- Furthermore, a telecommunications infrastructure comprising a device register system, a first network node and a second network node is disclosed. The device register system is configured for storing a first access grant time interval applicable for granting access for the device to the telecommunications infrastructure. The device register system may e.g. register information about the subscription of the device and/or information on the device itself. The first network node is configured for granting access during the first access grant time interval when the device requests access via the first network node. The second network node comprises or is configured to exchange information with an access controlling system configured for applying a second access grant time interval to control access to the telecommunications infrastructure when the device requests access via the second network node. The second access grant time interval is applicable for granting access for the device to the telecommunications infrastructure and is different from the first access grant time interval.
- Moreover, a visiting network for the device comprising the second network node of the telecommunications infrastructure is disclosed.
- Finally, an access controlling system provided in one or more network nodes of the telecommunications network is disclosed.
- The disclosed method and system enable the (first) access grant time interval that is applicable for the device to (temporarily) be adapted to a different (second) access grant time interval for that same device in a different part of the telecommunications infrastructure. In other words, the method and system provide flexibility in the access grant time interval in different parts of the network. Accordingly, local circumstances in the different parts of the telecommunications infrastructure may be taken into account when deciding on the access of the device to the telecommunications infrastructure.
- Examples of such local circumstances include a telecommunication network covering multiple time zones, wherein the time zone for the first network node differs from the time zone for the second network node. It also enables operators of visited networks employing a second network node to adapt the access grant time interval of the first network node of the home network of the device according to the needs or requirements of the visited network, as defined in
claims - The adaptation of the first access grant time interval may comprise shifting the entire time interval, or modifying at least one of the start time and the end time of the first access grant time interval or to split the time interval into multiple intervals.
- The access grant time interval may be the time interval assigned to a single device or to a group of devices.
- It should be appreciated that, except for special circumstances such as the application of a forbidden time interval described below, access to the telecommunications infrastructure via the second network node may be granted outside the first and/or second access grant time interval. Whereas, apart from the different access time intervals, access to the telecommunications network is obtainable under the same conditions, access outside the first and/or second access grant time interval may be granted under different conditions, such as higher prices, lower quality of service etc. The conditions may depend on one or more network parameters at the second network node, e.g. the traffic load. The conditions may be communicated to the device with either an accept message or a reject access message. If an accept message is used, the device is responsible for not establishing the connection if it does not want to accept the conditions. If a reject message is used, the device may repeat a request for the connection setup in the case that it wants to accept the conditions, the second network, being aware that this is a re-request can immediately grant access. The device may also beforehand communicate acceptable conditions to the second network node with the request for access to the telecommunications infrastructure. A device configured for performing this functionality is also disclosed in the present application.
- It should be appreciated that the term "telecommunications infrastructure" may either include a single telecommunications network (e.g. covering multiple time zones) or multiple telecommunications networks (e.g. located in two or more operator domains between which the device may roam).
- Examples of the device register system include a Home Location Register (HLR) of a 2G/3G network, a Home Subscriber Server (HSS) of an LTE network or an AAA database of a WLAN network. Examples of first and second network nodes include SGSNs of a telecommunications infrastructure comprising a 2G/3G network, MMEs of a telecommunications infrastructure comprising an LTE network or AAA proxies or Wireless Access Points of a telecommunications infrastructure comprising a WLAN network.
- The second network node is informed of the first access grant time interval, e.g. by transferring information regarding this time interval to the second network node. Accordingly, the second network node is informed about the preference and/or contractual obligations for the device when accessing the telecommunications infrastructure via the first network node and can adapt the first access grant time interval to the second access grant time interval as far as necessary.
- As defined in the embodiments of
claims - The reverse situation applies as well. A request to the device register system occurring outside the first access grant time interval and inside the second access grant time interval would normally be denied, but should now be allowed.
- In order to inform the device register system of this deviant behaviour, the second network node may send an information message to the device register system informing it that the an acceptable access request of the device was nevertheless rejected. In WLAN networks, accounting messages may be used for this purpose, informing the device register system (or other accounting system in the home network) of a "null session". Also, the second network node preferably informs the device register system of the fact that it wants to locally apply the second access grant time interval such that the device register system refrains from applying the first access grant time interval.
- It should be appreciated that the device may be informed about the applicable second access grant time interval, e.g. with the reject access message.
- The device register system may also be informed about the applicable second access grant time interval as defined in
claims - In an embodiment of the invention, a forbidden time interval may apply during which the home network of the device will not accept access by the device to the telecommunications infrastructure. The device register system may store the first access grant time interval and the forbidden time interval. The forbidden time interval is taken into account by the second network node when applying or selecting the second access grant time interval. The forbidden time interval, e.g. stored in the HLR or HSS of the home network, should be obeyed and cannot be adapted by further nodes or visited network operators. In an embodiment of the invention, the forbidden time interval is determined based on the expected and/or observed load in the home network, service windows and agreements with M2M application owners. The forbidden time interval can be adapted based on the information received from one or more of the second network nodes.
- The second network node (e.g. the SGSN or MME of the visited network) may, in an embodiment of the invention, retrieve at least the access grant time interval and possibly also the forbidden time interval from the device register system storing the first access grant time interval and/or the forbidden time interval (e.g. from the HLR (in the home network)).
- The second network node may then, in an embodiment of the invention, adapt the access grant time interval to a time interval that is more suitable. The adaptation of the time interval may be a shift of the time interval. The adaptation can be determined by the second network node itself, e.g. based on expected and/or observed load for this network node or on information from a time register. The time register may contain service windows, agreements with other M2M application customers and expected and/or observed network load.
- Hereinafter, embodiments of the invention will be described in further detail. It should be appreciated, however, that these embodiments may not be construed as limiting the scope of protection for the present invention.
- In the drawings:
-
FIG. 1 is a schematic illustration of a telecommunications network connecting communication devices to an application server; -
FIG. 2 is a schematic illustration of a telecommunications infrastructure according to a first embodiment of the invention; -
FIG. 3 is a schematic illustration of a telecommunications infrastructure according to a second embodiment of the invention; -
FIGS. 4A and4B are schematic illustrations of various options of applicable time intervals; -
FIG. 5 provides a diagram showing an implementation example of applying a local access grant time interval in the telecommunications infrastructure ofFIG. 2 or3 ; -
FIG. 6 is a schematic illustration of a telecommunications infrastructure according to a third embodiment of the invention; -
FIG. 7 provides a diagram showing an implementation example of applying a local access grant time interval in the telecommunications infrastructure ofFIG. 6 ; and -
FIG. 8 is a schematic illustration of a second network node containing an access control system. -
FIG. 1 shows a schematic illustration of atelecommunications network 1. Thetelecommunications network 1 enables data sessions between anapplication server 2 and acommunication device 3 over adata network 4, wherein access of thecommunication device 3 to thetelecommunications network 1 is wireless. - In the telecommunications network of
FIG. 1 , three generations of telecommunications networks are schematically depicted together for purposes of brevity. A more detailed description of the architecture and overview can be found in 3GPP TS 23.002 which is included in the present application by reference in its entirety. - The lower branch of
FIG. 1 represents a GPRS or UMTS telecommunications network comprising a Gateway GPRS Support Node (GGSN), a Serving GPRS Support Node (SGSN) and a Radio Access Network (GERAN or UTRAN). For a GSM/EDGE radio access network (GERAN), the access network comprises a Base Station Controller (BSC) connected to a plurality of Base Station Transceivers (BTSs), both not shown. For a UMTS radio access network (UTRAN), the access network comprises a Radio Network Controller (RNC) connected to a plurality of NodeBs), also not shown. The GGSN and the SGSN are conventionally connected to a Home Location Register (HLR) that contains subscription information of thecommunication devices 3. In the figure, the HLR is combined with an authentication centre (AuC) for authenticatingcommunication devices 3 in the network. - The upper branch in
FIG. 1 represents a next generation telecommunications network, commonly indicated as Long Term Evolution (LTE) or Evolved Packet System (EPS). Such a network comprises a PDN Gateway (P-GW) and a Serving Gateway (S-GW). The E-UTRAN of the EPS comprises evolved NodeBs (eNodeBs or eNBs), not shown, providing wireless access for acommunication device 3 that is connected to the S-GW via a packet network. The S-GW is connected to a Home Subscriber Server HSS and a Mobility Management Entity MME for signalling purposes. The HSS includes a subscription profile repository and an authentication centre (AuC). - Further information of the general architecture of an EPS network can be found in 3GPP TS 23.401.
- The operator of
application server 2 may have access to the HLR/HSS of the telecommunications network. -
FIG. 2 is atelecommunications infrastructure 10 having two operator domains according to an embodiment of the invention.FIG. 2 also shows twomobile communications devices Device 3A is within coverage of the home operator,device 3B is within coverage of a visited network of a visited operator. Bothdevices devices - When
device 3A accesses theinfrastructure 10, the SGSN (in case of UMTS) or MME (in case of LTE) within the domain of the home operator, will request information about the device's subscription from the HLR. Part of this information is an access grant time interval (marked 'granted 04:00-05:30' in the figure) as well as a forbidden time interval (however, that last piece of information is not used). If thedevice 3A accesses the network within the access grant time interval (and all other conditions are met, such as properly passing authentication) the SGSN/MME will allowdevice 3A to access the network. When the current time is outside the access grant time interval the SGSN/MME will normally denydevice 3A to access the network. Optionally the SGSN/MME may informdevice 1 about the applicable access grant time interval, sodevice 3A will know the earliest possible time that it can attempt to successfully access the network. Optionally,device 3A may still access the network, albeit under amended conditions e.g. at a higher charge and/or at a lower quality of service. - When
device 3B accesses thetelecommunications infrastructure 10, its request for access is received by the SGSN/MME in the domain of the visited network operator. This SGSN/MME will also request information from the HLR (located with the home operator) and may indicate that it intends to apply a local time interval for controlling access. The information from the HLR may again include the access grant time interval and may also include the forbidden time interval from the HLR. The SGSN/MME checks whether this access grant time interval is a suitable time interval for the visited network. The visited network may have a "time register" that contains conditions and time intervals, which register the SGSN/MME can consult to decide on a proper access grant time interval (this time register may be located in the foreign HLR or elsewhere). - If the visited SGSN/MME decides to adapt the time interval (marked 'granted 02:00-04:00' in the figure) it will have to ensure that the adapted time interval is not within the forbidden time interval that is specified by the home operator. A further adjustment may be needed to resolve a conflict with the forbidden time interval. In the example of
FIG. 2 , the SGSN/MME decides to adapt it to 02:00-04:00, which does not conflict with 'forbidden 07:00-12:00' specified by the home operator. The SGSN/MME will then allowdevice 3B to access theinfrastructure 10 if the time is within the adapted time interval (and provided that all other conditions are met). When the current time is outside the adapted time interval, the SGSN/MME will denydevice 3B to access the infrastructure. Optionally the SGSN/MME may informdevice 3B about the adapted time interval, sodevice 3B will know the earliest possible time that it can attempt to successfully access the network. - When the visited SGSN/MME has adapted the time interval, the
M2M device 3B may optionally store this adapted time interval for later use. - When the visited SGSN/MME has decided to adapt the time interval, it may optionally inform the home operator, e.g. the HLR, about this adaptation.
- The forbidden time interval stored in the home HLR is defined by the home operator. It can be based on parameters such as: expected and/or observed network load, agreements with other M2M applications, service windows, and agreements with the owner of the M2M server for the specific applications (e.g. the M2M server has a specific service window, or has other reasons for not being able to serve the M2M devices during the forbidden period).
- It should be appreciated that the invention is not limited to a single time interval and that adapting a time interval may also comprise splitting a time interval into multiple time intervals or joining multiple time intervals.
- The information with regard to time intervals can be formulated absolute, e.g. "between 16.00 and 17.00" or relative, e.g. "between one and two hours from now", "within 3 hours".
- It should be appreciated that, preferably, all information regarding time intervals is exchanged in a uniform time code (e.g. UTC) to cope with regional time differences.
-
FIG. 3 depicts another embodiment of the invention applicable in a single operator domain, wherein the SGSN can adapt the time interval on a local or regional basis. That would distribute the burden on the centralized GGSN/PDN-GW and HLR. This is especially advantageous when a dedicated HLR and GGSN/PDN-GW are used to handle M2M traffic or when a single operator network spans multiple time zones. - It should be appreciated that, typically, the (first) access grant time interval and the forbidden time interval as well as the adapted (second) access grant time interval and the forbidden time intervals are not complementary to each other, i.e. that these do not cover an entire reference period (e.g. a 24-hour period). This is indicated in
FIGS. 4A and4B . InFIG. 4B , the adapted time interval is smaller than the group time interval (marked 'access grant time') interval and partly overlaps that interval. The reference period may e.g. be one day, one week or one month. -
FIG. 5 provides a flow chart showing an implementation example of applying a local access grant time interval in thetelecommunications infrastructure 10 ofFIG. 2 or3 . The flow chart depicts a packet switched (PS) attach request bydevice 3A formerly connected to an old SGSN and now connected to a new SGSN (e.g. resulting from a hand-over involving switching SGSN areas) for which a locally defined access grant time interval applies. InFIG. 5 , the old SGSN functions as a first network node and the new SGSN functions as a second network node. The HLR is the device register system. - In
step 1,device 3A initiates a PS Attach procedure by generating an Attach Request message to the new SGSN. The message contains the IMSI ofdevice 3A and possibly indicates an Access Condition. It should be noted that for security reasons 3GPP has specified that after the initial exchange of the IMSI the device's subscription may further be identified by the (Packet-Temporary Mobile Subscriber Identity) P-TMSI, which is a temporary identifier associated with the IMSI for a short time. In this embodiment only IMSI is mentioned but P-TMSI would be applicable as well. The parameter(s) reflecting the Access Condition may contain information about the ability of thedevice 3A to access theinfrastructure 10 outside the applicable access grant time interval, e.g. the price or acceptable quality of service. - In
step 2, since the actual serving network node has changed from an old SGSN to a new SGSN and if thedevice 3A has identified itself by IMSI, the new SGSN performs an Identity Check to the old SGSN. If thedevice 3A is unknown in both the old and the new SGSN, the new SGSN performs an Identity Check with thedevice 3A whereindevice 3A responds with the IMSI (step 3).Step 4 involves authentication. IMEI checking may also be performed (not shown). - Since the SGSN is new (this may also result from a very first attach request by the
device 3A), the new SGSN informs the HLR by sending an Update Location message instep 5. The Update Location message contains the IMSI of thedevice 3A and the address of the new SGSN. The Update Location message also contains an indicating field LTI indicating that the new SGSN applies a local access grant time interval. The LTI indication may be used by the HLR to ignore the access grant time interval defined in the HLR and applicable when requesting access via the old SGSN. Instep 6, the HLR sends a Cancel Location message to the old SGSN, which message is acknowledged by the old SGSN. - In
step 7, the HLR sends an Insert Subscriber Data message to the new SGSN. The parameters contained in this message may include the IMSI ofdevice 3A, the access grant time interval as stored in the HLR, the forbidden time interval and, possibly, the access conditions. Upon receipt of the Insert Subscriber Data message, the new SGSN validates whether thedevice 3A is still within reach of the SGSN and may adapt the access grant time interval according to local requirements or needs. The forbidden time interval may not be adjusted and the adaptation of the access grant time interval should be such that an overlap with the specified forbidden time interval is avoided. - In
step 9, if all checks are successful, the new SGSN returns an Insert Subscriber Data Acknowledgement message to the HLR. The message includes the locally adapted access grant time interval that is temporarily stored in the HLR. - In
step 10, the HLR acknowledges the Update Location message ofstep 5 by sending an Update Location Acknowledgement message to the new SGSN. - In
step 11, the new SGSN now checks if the Attach Request from thedevice 3A falls within the adapted access grant time interval as explained previously with reference toFIG. 2 . When outside the adapted access grant time interval and the forbidden time interval, access may still be granted when the Access Conditions received fromdevice 3A instep 1 match the Access Conditions received from the HLR/HSS instep 7. - If the Attach Request of
step 1 falls within the adapted access grant time.interval or if the Access Conditions are fulfilled an Attach Accept is sent to thedevice 3A as illustrated bystep 12a. This Attach Accept message contains the IMSI, the applicable access time interval and, possibly, the forbidden time interval. Thedevice 3A is now aware when it is allowed to send Attach Requests, at least until handover to a further new SGSN. - If the Attach Request does not fall within the Local Access Grant Time interval or the Access Conditions are not fulfilled, an Attach Reject is sent to the
device 3A as illustrate by step 12b. This Attach Reject message contains the IMSI, the applicable access time interval and, possibly, the forbidden time interval. Thedevice 3A is now aware when it is allowed to send Attach Requests, at least until handover to a further new SGSN. - When not attached,
device 3A may repeat an Attach Request to the new SGSN at a later time within the communicated access grant time interval or when it meets the Access Conditions when outside the local access grant time interval and forbidden time interval. -
FIG. 6 provides a schematic illustration of atelecommunications infrastructure 20 according to a third embodiment of the invention. Thetelecommunications infrastructure 20 involves a WLAN network comprising a user database DB in a combination with an AAA server of a wireless internet provider WISP as a device register system and a AAAn proxy as a second network node. For access to public WiFi hotspots a roaming mechanism is implemented based on RADIUS roaming using the RADIUS AAA protocol. RADIUS AAA is defined in RFC 2138 and RFC 2139. The end-user has a subscription with the WISP. The WISP hands out credentials (e.g. username/password) to the end-user. Whenever a user is within reach of a public WiFi hotspot, the user can login with hisdevice 3 and use the hotspot if the hotspot owner and WISP belong to the same "alliance" (i.e. having roaming agreements in place, either direct or via an intermediate party). To provide the end-user access to a hotspot, several specifications exist that are all based on the same RADIUS mechanism as shown inFIG. 6 . In ETSI TS 183.019 the relevant network elements are AAA Proxy, AAA Server and Access Controller and Access Point. InFIG. 6 , the Access Controller and Access Point are combined into the Public WiFi Access Point. In 3GPP TS 23.234, the AAA Proxy is referred to as 3GPP AAA Proxy, the AAA Server is called 3GPP AAA Server. The Access Controller is called Wireless Access Gateway, which inFIG. 6 is combined into the Public WiFi Access Point. - It should be noted that more AAA proxies may be present in the
infrastructure 20. - In the
infrastructure 20 ofFIG. 6 , the WISP can control whenever adevice 3 is allowed access to theinfrastructure 20 by defining a (first) access grant time interval in the user database. AAA server receives incoming access requests, checks the user credentials and, possibly, applies the first access grant time interval, to decide whether or not aparticular device 3 may access the infrastructure. -
FIG. 7 provides a diagram showing an implementation example of applying a local access grant time interval in the telecommunications infrastructure ofFIG. 6 . In this case, adevice 3 connects to a WiFi hotspot outside its access grant time interval as defined by the global WISP. The local hotspot provider decides to adapt the access grant time interval. - In
step 1, thedevice 3 requests access to the public WiFi Access Point (AP) providing user credentials. The WiFi AP forwards a RADIUS Access Request to the AAA Proxy instep 2 that forwards the RADIUS AAA Request to the AAA Server instep 3. In forwarding the request ofstep 3, the AAA Proxy includes a RADIUS parameter, e.g. an indicating field LTI indicating that the AAA Proxy applies a local access grant time interval, in the forwarded message. The LTI indication may be used by the AAA Server to ignore the access grant time interval defined in the user database. The LTI indication may also be provided by the WiFi AP. - In
step 4, the AAA Sever verifies the user credentials and profile. In this step, it will appear if a time-based subscription applies fordevice 3A - In
step 5, if the AAA Server has positively verified the credentials, it is observed that the access request is received outside the first access grant time interval and outside a forbidden time interval. The LTI indicator may be used to disregard application of the first access grant time interval stored in the user database. - In
step 6, the AAA Server sends an Access Accept message as the credentials are positively verified and the first access grant time interval is disregarded. The Access Accept message includes the first access grant time interval and the forbidden time interval. - In
step 7, the AAA Proxy adapts the access grant time interval received from the AAA Server. As the Access Request fromstep 1 is outside this adapted time interval, the AAA Proxy changes the Access Accept message fromstep 6 in an Access Reject message insteps step 1 was received within the first access grant time interval.Steps - The Access Reject message of
step 8 contains the adapted access grant time interval and, optionally, the forbidden time interval, to informdevice 3 when it may access. As RADIUS AAA is a stateless protocol, the AAA server and user database is preferably informed of the Access Reject message. This is advantageously performed by making use of the existing Accounting messages as indicated inFIG. 7 . - In
steps step 10a) which is stored in Accounting DB (step 10b). In order to indicate that the Access Request has been rejected, these steps are immediately succeeded by the AAA Proxy sending Accounting Stop message indicating this is a null session to AAA Server (step 11a) which is stored in Accounting DB (step 11b). In this manner, the accounting database always reflects Accounting Start and Stop messages for all session wherein the AAA Server has sent an Access Accept message as instep 6. It should be appreciated that the order ofsteps - It should be appreciated that various modifications have been envisaged for the above-described methods.
- Hitherto, it was assumed that only two classes of end-user subscriptions exist, either with the possibility of time-based access control or without. However, in practice, several classes of time-based subscriptions exist. As an example, the most expensive subscription always gets access and there is a range of other subscriptions that each match to several classes of timeslots or situations of traffic load.
- Furthermore, as previously mentioned, there may be a possibility that for a certain time-based subscriptions, access is still granted outside the adapted access grant time interval but at a higher price. To implement this in the process of
FIG. 7 , the AAA Sever may identify that for a particular device 3 a time-based subscription for which higher prices can be charged in certain time periods is enabled. Then, either the AAA Proxy or the Access Point will determine that at the current local time and the given subscription type the end-user is only allowed access at a higher price. It will allow thedevice 3 to access the infrastructure and will optionally inform thedevice 3 of the higher price. The user (or an automated procedure at the device 3) can optionally disconnect immediately if it does not want to accept the higher price. If the user does not disconnect, the Access Point starts sending Accounting Start/Intermediate/Stop messages as it would in the regular case and these are forwarded to the AAA Server that stores it in the WISP accounting database. However, either the Access Point or AAA Proxy will add pricing information to these accounting messages so the WISP will know that the end-user accessed the network at a higher price and can bill the end-user accordingly. Pricing information can either be a fixed tariff but can also be an indication of a tariff class. - Furthermore, the time-based subscription of
device 3 may be of such a type that thedevice 3 is allowed to use the network outside the applicable access grant time interval (except for the forbidden time interval but that during specific time periods it will be provided with a lower quality of service. For instance the bandwidth generated by thedevice 3 may be limited or its traffic will be labelled with a low priority. Implementing this scenario may be completely up to the discretion of either the Access Point or the AAA Proxy. It could optionally inform thedevice 3 that a lower quality of service is available and the user (or automated procedure at the device 3) may decide to disconnect from the network. - Combinations of the above modifications have been envisaged. For instance the
device 3 may be given a choice insteps 8/9 (e.g. either accept the higher price, the lower quality of service or disconnect and wait for a regular time slot). - Finally,
FIG. 8 is a schematic illustration of a second network node 30, such as an SGSN/MME or an AAA proxy. The second network node 30 comprises anaccess control system 31. The access control system has an input orinterface 32 for receiving information (such as the information indicated inFIGS. 5 and7 received by the new SGSN and the AAA Proxy respectively). Theaccess control system 31 also contains aprocessor 33 for applying the second access grant time interval, possibly by adapting the first access grant time interval. - Furthermore, the time interval could also be used in such a way that access is granted but at other conditions (e.g. lower QoS, higher price).
- One embodiment of the invention may be implemented as a program product for use with a computer system. The program(s) of the program product define functions of the embodiments (including the methods described herein) and can be contained on a variety of computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive, ROM chips or any type of solid-state non-volatile semiconductor memory) on which information is permanently stored; and (ii) writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive or any type of solid-state random-access semiconductor memory, flash memory) on which alterable information is stored.
Claims (13)
- A method for controlling wireless access to a telecommunications infrastructure (10) for a device (3), the method comprising the steps of:- storing a first access grant time interval applicable for granting access for the device to the telecommunications infrastructure in a device register system (HLR/HSS);- applying the first access grant time interval when the device requests access to the telecommunications infrastructure via a first network node (SGSN/MME) of the telecommunications infrastructure;- transferring the first access grant time interval from the device register system to a second network node (SGSN/MME) of the telecommunications infrastructure; and- applying a second access grant time interval in the second network node when the device requests access via the second network node, the second access grant time interval being applicable for granting access for the device to the telecommunications infrastructure and being different from the first access grant time interval;characterised in that the method further comprises, prior to the step of applying the second access grant time interval, the step of:- obtaining the second access grant time interval in the second network node by adapting the first access grant time interval, wherein the adapting of the first access grant time interval comprises modifying at least one of a start time and an end time of the first access grant time interval, shifting the time interval, or splitting the first access grant time interval in multiple intervals.
- The method according to claim 1, wherein the first network node and the device register system are located in a home network of the device and the second network node is located in a visiting network of the device.
- The method according to one or more of the preceding claims, comprising the steps of:- receiving an access request from the device at the second network node during the first access grant time interval and outside the second access grant time interval;- forwarding the access request from the second network node to the device register system ;- receiving an access grant message from the device register system at the second network node;- rejecting the access request from the device by applying the second access grant time interval at the second network node, and- optionally, transmitting a reject information message from the second network node to the device register system.
- The method according to one or more of the preceding claims, further comprising the step of transmitting to the device register system an information message regarding the second access grant time interval applied by the second network node.
- The method according to one or more of the preceding claims, further comprising the steps of:- storing a forbidden time interval in the device register system;- selecting the applicable second access grant time interval for the second network node such as to avoid an overlap with the forbidden time interval in the device register system.
- The method according to claim 5, further comprising the step of transferring the forbidden time interval to the second network node.
- A telecommunications infrastructure (10) comprising a device register system (HLR/HSS), a first network node (SGSN/MME) and a second network node (SGSN/MME), wherein- the device register system is configured for storing a first access grant time interval applicable for granting access for a device (3) to the telecommunications infrastructure;- the first network node is configured for granting access during the first access grant time interval when the device requests access via the first network node; and- the second network node comprises an access controlling system configured for applying a second access grant time interval to control access to the telecommunications infrastructure when the device requests access via the second network node, the second access grant time interval being applicable for granting access for the device to the telecommunications infrastructure and being different from the first access grant time interval, wherein the access controlling system comprises an interface configured for receiving the first access grant time interval from the device register system;characterised in that the access controlling system comprises a processor configured for obtaining the second access grant time interval in the second network node by adapting the first access grant time interval prior to applying the second access grant time interval, wherein the adapting of the first access grant time interval comprises modifying at least one of a start time and an end time of the first access grant time interval, shifting the time interval, or splitting the first access grant time interval in multiple intervals.
- The telecommunications infrastructure according to claim 7, wherein the device register system and first network node are located in a home network of the device and the second network node is located in a visiting network of the device.
- The telecommunications infrastructure according to one or more of the claims 7-8, wherein the access controlling system is configured for:- receiving an access request from the device during the first access grant time interval and outside the second access grant time interval;- forwarding the access request to the device register system;- receiving an access grant message from the device register system;- rejecting the access request from the device by applying the second access grant time interval at the second network node; and- optionally, transmitting a reject information message to the device register system.
- The telecommunications infrastructure according to one or more of the claims 7-9, wherein the access controlling system is further configured for transmitting to the device register system an information message regarding the second access grant time interval applied by the second network node.
- The telecommunications infrastructure according to one or more of the claims 7-10, wherein the access controlling system is further configured for selecting the second access grant time interval such as to avoid an overlap with a forbidden time interval defined in the device register system, optionally including receiving the forbidden time interval from the device register system.
- A visiting network for a device (3B) comprising a second network node (SGSN/MME) of a telecommunications infrastructure (10), the telecommunications infrastructure (10) comprising a device register system (HLR/HSS), a first network node (SGSN/MME) and said second network node (SGSN/MME), wherein- the device register system is configured for storing a first access grant time interval applicable for granting access for the device to the telecommunications infrastructure;- the first network node is configured for granting access during the first access grant time interval when the device requests access via the first network node; and- the second network node, being part of the visiting network, comprises an access controlling system configured for applying a second access grant time interval to control access to the telecommunications infrastructure when the device requests access via the second network node, the second access grant time interval being applicable for granting access for the device to the telecommunications infrastructure and being different from the first access grant time interval, wherein the access controlling system comprises an interface configured for receiving the first access grant time interval from the device register system;characterised in that the access controlling system, being part of the second network node in the visiting network, comprises a processor configured for obtaining the second access grant time interval in the second network node by adapting the first access grant time interval prior to applying the second access grant time interval, wherein the adapting of the first access grant time interval comprises modifying at least one of a start time and an end time of the first access grant time interval, shifting the time interval, or splitting the first access grant time interval in multiple intervals.
- An access controlling system provided in a second network node (SGSN/MME) of a telecommunications infrastructure (10), the telecommunications infrastructure comprising a device register system (HLR/HSS), a first network node (SGSN/MME) and said second network node (SGSN/MME), wherein- the device register system is configured for storing a first access grant time interval applicable for granting access for a device (3) to the telecommunications infrastructure;- the first network node is configured for granting access during the first access grant time interval when the device requests access via the first network node;- the second network node comprises said access controlling system;- the access controlling system comprises an interface configured for receiving the first access grant time interval from the device register system; and- the access controlling system is configured for applying a second access grant time interval to control access to the telecommunications infrastructure when the device requests access via the second network node, the second access grant time interval being applicable for granting access for the device to the telecommunications infrastructure and being different from the first access grant time interval;characterised in that the access controlling system comprises a processor configured for obtaining the second access grant time interval in the second network node by adapting the first access grant time interval prior to applying the second access grant time interval, wherein the adapting of the first access grant time interval comprises modifying at least one of a start time and an end time of the first access grant time interval, shifting the time interval, or splitting the first access grant time interval in multiple intervals.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11702985.0A EP2534884B1 (en) | 2010-02-08 | 2011-02-07 | Method and telecommunications infrastructure enabling localized time controlled access for a device |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP10152891 | 2010-02-08 | ||
EP10165825 | 2010-06-14 | ||
PCT/EP2011/051713 WO2011095618A1 (en) | 2010-02-08 | 2011-02-07 | Method and telecommunications infrastructure enabling localized time controlled access for a device |
EP11702985.0A EP2534884B1 (en) | 2010-02-08 | 2011-02-07 | Method and telecommunications infrastructure enabling localized time controlled access for a device |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2534884A1 EP2534884A1 (en) | 2012-12-19 |
EP2534884B1 true EP2534884B1 (en) | 2016-01-20 |
Family
ID=43707751
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11702985.0A Active EP2534884B1 (en) | 2010-02-08 | 2011-02-07 | Method and telecommunications infrastructure enabling localized time controlled access for a device |
Country Status (3)
Country | Link |
---|---|
US (2) | US9125131B2 (en) |
EP (1) | EP2534884B1 (en) |
WO (1) | WO2011095618A1 (en) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009036058A1 (en) | 2007-09-10 | 2009-03-19 | Rappaport Theodore R | Clearinghouse system for determining available network equipment |
WO2011095618A1 (en) * | 2010-02-08 | 2011-08-11 | Koninklijke Kpn N.V. | Method and telecommunications infrastructure enabling localized time controlled access for a device |
EP2624598A1 (en) * | 2012-02-03 | 2013-08-07 | Cinterion Wireless Modules GmbH | Distributed initialization of m2m access to radio access network |
US9015395B2 (en) * | 2012-05-10 | 2015-04-21 | Alcatel Lucent | Methods and apparatuses for multiple priority access in a wireless network system |
US9125076B2 (en) | 2012-08-02 | 2015-09-01 | Openet Telecom Ltd. | System and method for providing detection of signaling-only engagements in a telecommunication network |
JP6029755B2 (en) * | 2012-08-08 | 2016-11-24 | ノキア テクノロジーズ オーユー | Method and apparatus for network-assisted data transfer scheduling |
EP3111611B1 (en) * | 2014-02-24 | 2020-01-01 | Telefonaktiebolaget LM Ericsson (publ) | A node and a method for enabling network access authorization |
US9654338B2 (en) * | 2015-03-23 | 2017-05-16 | Verizon Digital Media Services Inc. | CPE device installation and operation |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6230017B1 (en) | 1997-07-31 | 2001-05-08 | Telefonaktiebolaget Lm Ericsson | Geographical restriction in cellular telecommunications network |
US6275695B1 (en) | 1998-10-08 | 2001-08-14 | Nortel Networks Limited | Spectrum yield management in a wireless communication system |
SG141225A1 (en) * | 2003-03-24 | 2008-04-28 | Starhome Gmbh | Preferred network selection |
ATE482580T1 (en) | 2008-02-29 | 2010-10-15 | Research In Motion Ltd | DEVICE AND METHOD FOR LINE SELECTION IN A COMMUNICATIONS DEVICE |
EP2096884A1 (en) | 2008-02-29 | 2009-09-02 | Koninklijke KPN N.V. | Telecommunications network and method for time-based network access |
WO2011095618A1 (en) * | 2010-02-08 | 2011-08-11 | Koninklijke Kpn N.V. | Method and telecommunications infrastructure enabling localized time controlled access for a device |
-
2011
- 2011-02-07 WO PCT/EP2011/051713 patent/WO2011095618A1/en active Application Filing
- 2011-02-07 US US13/577,531 patent/US9125131B2/en active Active
- 2011-02-07 EP EP11702985.0A patent/EP2534884B1/en active Active
-
2015
- 2015-07-22 US US14/806,216 patent/US9491687B2/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
US20150373621A1 (en) | 2015-12-24 |
US20120329455A1 (en) | 2012-12-27 |
WO2011095618A1 (en) | 2011-08-11 |
US9125131B2 (en) | 2015-09-01 |
EP2534884A1 (en) | 2012-12-19 |
US9491687B2 (en) | 2016-11-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9491687B2 (en) | Method and telecommunications infrastructure enabling localized time controlled access for a device | |
AU2015290086B2 (en) | Associating a device with another device's network subscription | |
US9369863B2 (en) | Method and corresponding apparatus, computer program product to validate an eUICC subscription change | |
KR101884348B1 (en) | server for control plane at mobile communication network and for providing local CSG and access control method | |
JP6214770B2 (en) | Method for dynamically switching mobile networks, subscription managers, and user equipment | |
EP2870799A1 (en) | Hierarchical access network discovery and selection function and offload wi-fi network | |
AU2014274399A1 (en) | Cell selection in dynamic spectrum arbitrage system | |
US20230164726A1 (en) | User equipment (ue) and communication method for ue | |
EP2656600B1 (en) | Method and system for handling service requests in a telecommunications network | |
CN102656923B (en) | In mobile or wireless communication system, prevent that wireless access is congested | |
WO2011157189A2 (en) | Method, device and system for reporting location | |
US8948750B1 (en) | LTE roaming APN adaptation | |
CN101568092A (en) | Position managing method of shared network, information-change reporting method, system and equipment | |
EP2717546B1 (en) | Method and device for acquiring destination ip address | |
US9344873B1 (en) | Limiting data service for a home terminal roaming near home coverage | |
WO2015088411A1 (en) | Methods and apparatuses for communicating in a communication system comprising a home communication network and visiting communication networks | |
US11956750B2 (en) | Communication method for controlling packet data unit session | |
US20230247542A1 (en) | User equipment (ue) and communication control method for ue | |
US20170150344A1 (en) | Subscription Fall-Back in a Radio Communication Network | |
WO2018205145A1 (en) | Method and apparatus for allocating registration area | |
EP2840862A1 (en) | Network selection method and user device configured for performing such a method | |
WO2022027300A1 (en) | Method of slice support for vehicle-to-everything service | |
JP6669960B2 (en) | Terminal device, communication program, and communication method | |
EP3038393A1 (en) | Method for connecting to a visited cellular network based on a second subscriber identity and mobile station for executing said method | |
US20230247543A1 (en) | User equipment (ue) and communication control method for ue |
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: 20120910 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20130909 |
|
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 4/00 20090101ALN20150520BHEP Ipc: H04W 48/02 20090101AFI20150520BHEP |
|
INTG | Intention to grant announced |
Effective date: 20150610 |
|
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 48/02 20090101AFI20150824BHEP Ipc: H04W 4/00 20090101ALN20150824BHEP |
|
INTG | Intention to grant announced |
Effective date: 20150910 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 4/00 20090101ALN20151008BHEP Ipc: H04W 48/02 20090101AFI20151008BHEP |
|
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 |
|
INTG | Intention to grant announced |
Effective date: 20151117 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM 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: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 772211 Country of ref document: AT Kind code of ref document: T Effective date: 20160215 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602011022792 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 6 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20160229 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 772211 Country of ref document: AT Kind code of ref document: T Effective date: 20160120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR 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: 20160120 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: 20160421 Ref country code: IT 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: 20160120 Ref country code: ES 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: 20160120 Ref country code: NO 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: 20160420 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20160520 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: 20160520 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: 20160120 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: 20160120 Ref country code: LV 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: 20160120 Ref country code: RS 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: 20160120 Ref country code: LT 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: 20160120 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602011022792 Country of ref document: DE |
|
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: 20160229 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: 20160120 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160229 Ref country code: EE 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: 20160120 Ref country code: MC 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: 20160120 |
|
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: SM 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: 20160120 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: 20160120 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: 20160120 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: 20160120 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
26N | No opposition filed |
Effective date: 20161021 |
|
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: 20160120 |
|
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: 20160207 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 7 |
|
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: 20160120 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: 20160420 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT 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: 20160120 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 8 |
|
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: 20160120 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; INVALID AB INITIO Effective date: 20110207 |
|
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: 20160207 Ref country code: MK 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: 20160120 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: 20160120 Ref country code: MT 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: 20160229 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AL 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: 20160120 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20230221 Year of fee payment: 13 Ref country code: FI Payment date: 20230224 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: SE Payment date: 20230216 Year of fee payment: 13 Ref country code: GB Payment date: 20230220 Year of fee payment: 13 Ref country code: DE Payment date: 20220620 Year of fee payment: 13 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230517 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20240219 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FI Payment date: 20240219 Year of fee payment: 14 Ref country code: DE Payment date: 20240219 Year of fee payment: 14 Ref country code: GB Payment date: 20240219 Year of fee payment: 14 |