EP2341660B1 - Handling of M2M services in a communication system - Google Patents
Handling of M2M services in a communication system Download PDFInfo
- Publication number
- EP2341660B1 EP2341660B1 EP10305012A EP10305012A EP2341660B1 EP 2341660 B1 EP2341660 B1 EP 2341660B1 EP 10305012 A EP10305012 A EP 10305012A EP 10305012 A EP10305012 A EP 10305012A EP 2341660 B1 EP2341660 B1 EP 2341660B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- service
- entity
- charging information
- communication system
- terminals
- 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
- 238000004891 communication Methods 0.000 title claims description 54
- 238000000034 method Methods 0.000 claims description 27
- 230000011664 signaling Effects 0.000 claims description 7
- 241000282414 Homo sapiens Species 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 230000005611 electricity Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000015654 memory Effects 0.000 description 1
- 238000012876 topography Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
- H04M15/765—Linked or grouped accounts, e.g. of users or devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
Definitions
- the present invention generally relates to communication networks and systems, such as for example wireless or mobile communication networks and systems.
- a terminal such as for example Mobile Station MS or User Equipment UE
- has access to communication services via an Access Network enabling various user services and applications.
- An example of Access Network is the lP Connectivity Access Network (IP-CAN) providing lP connectivity, enabling various lP-based user services and applications.
- IP-CAN lP Connectivity Access Network
- Examples of lP-CAN include GPRS (as specified in particular in 3GPP TS 23.060) and Evolved Packet Core (EPC) (as specified in particular in 3GPP TS 23.401).
- lP-CAN includes network nodes such as for example Serving GPRS Support Nodes (SGSN), Serving Gateway (S-GW), Gateway GPRS Support Node (GGSN) and PDN Gateway (P-GW).
- SGSN Serving GPRS Support Nodes
- S-GW Serving Gateway
- GGSN Gateway GPRS Support Node
- PDN Gateway PDN Gateway
- IP-CAN bearer services including in particular establishing and maintaining lP-CAN connections are subject to charging.
- charging is a function whereby information related to chargeable events is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed.
- lP-CAN bearer charging is specified in particular in 3GPP TS 32.251.
- charging information related to chargeable events is formatted into Charging Data Records CDR S , including in particular S-CDR, G-CDR, SGW-CDR and PGW-CDR used to collect charging information related to the lP-CAN bearer for a MS/UE respectively in the SGSN, in the GGSN, the S-GW and the P-GW.
- M2M Machine-to-Machine communication
- M2M Machine to Machine
- an issue is that there will likely be huge numbers of M2M terminals that typically send only a very limited amount of data per day but spread over time (e g a few hundred of bytes per 1 ⁇ 4 pour, or even less than that, once per hour) If a CDR is to be bult for each of these M2M mobile terminal access (as recalled above), the mobile system will have to handle a huge amount of charging related data that may even correspond to a greater amount of data than what the M2M mobile terminal did actually exchange over the mobile network
- the present invention in particular enables to solve such problems and/or avoid such drawbacks More generally, it is an oblect of the present invention to improve handling of M2M services in communication systems.
- a method for handling Machine to Machine M2M services in a communication system comprising a step of, for charging for IP Connectivity Access Network IP-CAN bearer, services in said communication system:
- a method for handling Machine to Machine M2M services in a communication system comprising a step of:
- entities for carrying out such methods including in particular: entity storing subscriber data (such as HSS/HLR), entity controlling lP-CAN bearer services (such as SGSN/MME), entity creating charging information such as CDR S (such as GGSN/P-GW), and entity in charge of managing communications of M2M terminals via a communication system.
- entity storing subscriber data such as HSS/HLR
- entity controlling lP-CAN bearer services such as SGSN/MME
- entity creating charging information such as CDR S (such as GGSN/P-GW)
- entity in charge of managing communications of M2M terminals via a communication system such as GGSN/P-GW
- a M2M system can generally be represented as illustrated in figure 1 .
- the Back Office systems contains the Applications that manage the M2M Devices and the data handled by them.
- the M2M Information System is in charge to manage the communications with the M2M Devices via a specific Communication Network.
- the Communication Network allows to transport data from/to Applications to/from M2M Devices or M2M Gateways.
- This network can be a public network (e.g. 3GPP, TISPAN, CDMA, ...) or any other kind of network (Ethernet, PLC (PowerLine Communication), ).
- a M2M Gateway is a specific M2M network element that is in charge to manage some M2M Devices via a M2M capillary network.
- a lot of types of capillary network (wired or wireless) are currently existing depending on the kind of handled data, the kind of topology, topography, range, ...
- One of the main goals of a M2M Gateway is for example the aggregation of the data collected from the M2M Devices before sending them in a more concentrated way to the central Application.
- a Back Office system can exchange messages with M2M Devices by using some specific protocols.
- Some M2M Systems can handle a huge number of M2M Devices (for example in Smart Metering in which the M2M Application remotely collect the value of each M2M Device that are the electricity counters).
- M2M Mobile Terminal may be
- the current approach in terms of billing in the Mobile Networks is to gather information in order to send a bill to the end-user that owns the terminal.
- the entity to be charged is likely not the individual M2M mobile terminal but the M2M service user (e.g. the M2M application)
- the frequency to build CDR / send charging information may be reduced to e.g. once per day instead of a classical 1 / 4 hour.
- the M2M mobile terminals may be allocated 2 identifiers by the mobile network
- M2M mobile terminals for a given service would have different M2M mobile terminal identifiers (e.g. IMSI) but the same service related identifier (e.g. MSISDN)
- an interface may be provided by the mobile network operator to the M2M Information System (in charge to manage the communications with the M2M Devices via a specific Communication Network) in order for the M2M Information system to be able to set the mapping between
- the interface between the M2M Information System and the (Mobile) communication operator is terminated on the HSS/HLR of this operator and allows to associate an identifier of the device such as the IMSI (International Mobile Subscriber Identity) of the device with an identifier of the M2M service e.g. the MSISDN (Mobile Station International ISDN Number).
- IMSI International Mobile Subscriber Identity
- MSISDN Mobile Station International ISDN Number
- the present invention provides a method for handling M2M services in a communication system, said method comprising a step of, for charging for lP-CAN bearer services in said communication system:
- said method comprises a step of:
- a single M2M service identifier is provided for said plurality of terminals using a same M2M service.
- said method comprises a step of:
- said indication is provided in the signalling associated with the creation of said lP-CAN bearer.
- said method comprises a step of:
- charging information is periodically created, and the period for creating charging information is depending of whether a terminal is supporting a M2M service and of the M2M service identifier.
- a M2M service identifier corresponds to Mobile Station International ISDN Number MSISDN.
- the present invention provides a method for handling M2M services in a communication system, said method comprising a step of:
- said method comprises a step of:
- a M2M service identifier corresponds to Mobile Station International ISDN Number MSISDN.
- the present invention provides entities comprising means for carrying out such methods, said entities including in particular: entity storing subscriber data, entity controlling lP-CAN services, entity creating charging information such as in particular CDR S , and entity in charge of managing communications of M2M terminals via a communication system.
- the present invention provides an entity storing subscriber data in a communication system, comprising, for charging for lP-CAN bearer services in said communication system:
- the present invention provides an entity controlling lP-CAN services in a communication system, comprising, for charging for lP-CAN bearer services in said communication system:
- the present invention provides an entity creating charging information for lP-CAN bearer services in a communication system, comprising:
- the present invention provides an entity in charge of managing communications of M2M terminals in a communication system, said entity comprising:
- program storage devices e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods.
- the program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.
- the embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Mobile Radio Communication Systems (AREA)
- Meter Arrangements (AREA)
Description
- The present invention generally relates to communication networks and systems, such as for example wireless or mobile communication networks and systems.
- Descriptions of such networks and systems can be found in the litterature such as in particular in Technical Specifications published by standardisation bodies. Examples of standardisation bodies include 3GPP (3rd Generation Partnership Project) ...etc.
- In such systems, a terminal (such as for example Mobile Station MS or User Equipment UE) has access to communication services via an Access Network, enabling various user services and applications.
- An example of Access Network is the lP Connectivity Access Network (IP-CAN) providing lP connectivity, enabling various lP-based user services and applications. Examples of lP-CAN include GPRS (as specified in particular in 3GPP TS 23.060) and Evolved Packet Core (EPC) (as specified in particular in 3GPP TS 23.401). lP-CAN includes network nodes such as for example Serving GPRS Support Nodes (SGSN), Serving Gateway (S-GW), Gateway GPRS Support Node (GGSN) and PDN Gateway (P-GW).
- Services provided by lP-CAN, or IP-CAN bearer services (including in particular establishing and maintaining lP-CAN connections) are subject to charging.
- Generally, charging is a function whereby information related to chargeable events is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed.
- lP-CAN bearer charging is specified in particular in 3GPP TS 32.251. In particular, charging information related to chargeable events is formatted into Charging Data Records CDRS, including in particular S-CDR, G-CDR, SGW-CDR and PGW-CDR used to collect charging information related to the lP-CAN bearer for a MS/UE respectively in the SGSN, in the GGSN, the S-GW and the P-GW.
- Historically mobile networks were mainly designed for enabling voice communication between human beings. Then some additional services were added, e.g. data service, SMS, ...
- Currently, a new kind of communications is emerging : the Machine-to-Machine communication (M2M). In M2M, the communication is not between human beings but between two machines that doesn't need necessarily human interaction
- With the development of Machine to Machine (M2M) communications (e.g. captors, sensors, .) huge amounts of new automatic M2M Mobile Terminals are going to be deployed. A large part of these new automatic M2M terminals will use Mobile Networks for exchanging messages with the M2M information system and the M2M Backoffice systems. Those M2M mobile terminals will request IP-CAN connections that are subject to charging
- As recognized by the inventors, an issue is that there will likely be huge numbers of M2M terminals that typically send only a very limited amount of data per day but spread over time (e g a few hundred of bytes per ¼ pour, or even less than that, once per hour) If a CDR is to be bult for each of these M2M mobile terminal access (as recalled above), the mobile system will have to handle a huge amount of charging related data that may even correspond to a greater amount of data than what the M2M mobile terminal did actually exchange over the mobile network
- Currently this issue is not solved whereas the M2M market is emerging The number of M2M devices that are managed via a mobile network is currently not huge, but it is foreseen that in the next future some applications (e g Smart Metering) could have to manage several millions of new M2M devices
- Document "3rd Generation Parthershipproject Technical Specification Group Services and System Aspects, Study on Facilitating Mashine to Machine Communication in 3GPP Systems; (Release 8) "3GPP STANDARD; 3GPP TR 22 868, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE, 650, ROUTE DES LUCIOLES, F-06921 SOPHIA-ANTIPOLIS CEDEX, FRANCE, n° V8 0.0, 1 March 2007 (2007-03-01), pages 1-15, XP050361381, and document
US 2007/036312 A1 provide technological background. - The present invention in particular enables to solve such problems and/or avoid such drawbacks More generally, it is an oblect of the present invention to improve handling of M2M services in communication systems.
- These and other objects are achieved, in one aspect of the present invention, by a method for handling Machine to Machine M2M services in a communication system, said method comprising a step of, for charging for IP Connectivity Access Network IP-CAN bearer, services in said communication system:
- providing global charging information for a plurality of terminals using a same M2M service.
- These and other objects are achieved, in another aspect of the present invention, by a method for handling Machine to Machine M2M services in a communication system, said method comprising a step of:
- controlling an association between a M2M service identifier and the M2M terminals supporting this M2M service.
- These and other objects are achieved in other aspects of the present invention, by entities for carrying out such methods, said entities including in particular: entity storing subscriber data (such as HSS/HLR), entity controlling lP-CAN bearer services (such as SGSN/MME), entity creating charging information such as CDRS (such as GGSN/P-GW), and entity in charge of managing communications of M2M terminals via a communication system.
- These and other objects of the present invention will become more apparent from the following description taken in conjunction with the accompanying drawings:
-
figure 1 is intended to illustrate a high level view of a M2M mobile communication system, -
figure 2 is intended to illustrate charging for lP-CAN bearer services according to an embodiment of the present invention, -
figure 3 is intended to illustrate controlling of M2M services according to an embodiment of the present invention. - From a high level point of view, a M2M system can generally be represented as illustrated in
figure 1 . - The Back Office systems contains the Applications that manage the M2M Devices and the data handled by them.
- The M2M Information System is in charge to manage the communications with the M2M Devices via a specific Communication Network.
- The Communication Network allows to transport data from/to Applications to/from M2M Devices or M2M Gateways. This network can be a public network (e.g. 3GPP, TISPAN, CDMA, ...) or any other kind of network (Ethernet, PLC (PowerLine Communication), ...).
- A M2M Gateway is a specific M2M network element that is in charge to manage some M2M Devices via a M2M capillary network. A lot of types of capillary network (wired or wireless) are currently existing depending on the kind of handled data, the kind of topology, topography, range, ... One of the main goals of a M2M Gateway is for example the aggregation of the data collected from the M2M Devices before sending them in a more concentrated way to the central Application.
- A Back Office system can exchange messages with M2M Devices by using some specific protocols.
- Some M2M Systems can handle a huge number of M2M Devices (for example in Smart Metering in which the M2M Application remotely collect the value of each M2M Device that are the electricity counters).
- In the following a M2M Mobile Terminal may be
- o A M2M device accessing directly to the mobile network
- o A M2M Gateway that is in charge to manage some M2M Devices via a M2M capillary network and to support access to a mobile network on behalf of these M2M devices.
- As recognized by the inventors, the current approach in terms of billing in the Mobile Networks is to gather information in order to send a bill to the end-user that owns the terminal. Now, considering that the entity to be charged is likely not the individual M2M mobile terminal but the M2M service user (e.g. the M2M application), it is proposed, in an embodiment, to have a global CDR for all the M2M mobile terminals supporting the same M2M service. Even when there are 100K(s) of M2M mobile terminals for some utility metering service (on behalf of an electricity distribution company), then there will be only one CDR built by the mobile network.
- Furthermore for this (M2M) type of mobile user, the frequency to build CDR / send charging information may be reduced to e.g. once per day instead of a classical 1/4 hour.
- In an embodiment, the M2M mobile terminals may be allocated 2 identifiers by the mobile network
- ■ One to identify the M2M mobile terminal itself e.g. the IMSI (International Mobile Subscriber Identity)
- ■One to identify the M2M service e.g. the MSISDN (Mobile Station International ISDN Number)
- All M2M mobile terminals for a given service would have different M2M mobile terminal identifiers (e.g. IMSI) but the same service related identifier (e.g. MSISDN)
- When an entity creating charging related data and signaling (e.g. PGW/GGSN) for the lP-CAN (lP Connectivity Access Network) service is being told that a mobile end-user actually corresponds to a M2M service, it does not create CDR or charging related messages dedicated to this mobile end-user (M2M mobile terminal) but agglomerates the associated charging information with the one associated with all other mobile end-user (M2M mobile terminal) for the same M2M service. The result is that only one CDR / charging related signaling message is to be created for all mobile end-user actually that corresponds to the same M2M service.
- In an embodiment, following steps may be provided as illustrated in
figure 2 : - ■In step 1, an entity storing subscriber data (such as HSS/HLR) provides to an entity controlling the lP-CAN service (such as SGSN/MME) an indication that a mobile user is actually a M2M mobile terminal together with an indication of the M2M service of that M2M mobile terminal. This indication is provided within the subscriber data of a mobile user that has just attached to the network (This includes the provisioning of a single MSISDN for all M2M mobile users corresponding to the same M2M service (as negotiated between the Mobile Network Operator and the M2M application) )
- ■ In
step 2, the entity controlling the lP-CAN service (such as SGSN/MME), provides this information to entities creating charging related data and signaling (e.g. GGSN/P-GW) for the lP-CAN service. This is provided in the signaling (e.g. in GTP PDP context activation / Create Session Request ) associated with the creation of an lP-CAN bearer (e.g. PDP context / PDN connection) - ■ In
step 3, an entity creating charging related data and signaling (e.g. P-GW/GGSN) for the lP-CAN service,- o Does not create individual CDR or charging related messages dedicated to a mobile identified as being actually a M2M mobile terminal. This entity agglomerates the associated charging information with the one associated with all other M2M mobile terminal for the same M2M service.
- o Considers a specific charging data generation scheme i.e. agglomerates charging related information for a longer period than for the case of a classical user.
- Other aspects of the present invention will be described in the following.
- In an embodiment, an interface may be provided by the mobile network operator to the M2M Information System (in charge to manage the communications with the M2M Devices via a specific Communication Network) in order for the M2M Information system to be able to set the mapping between
- ■ A M2M mobile terminal
- ■ M2M service negotiated between the M2M Information System and the Communication Network
- ln an embodiment, the interface between the M2M Information System and the (Mobile) communication operator, is terminated on the HSS/HLR of this operator and allows to associate an identifier of the device such as the IMSI (International Mobile Subscriber Identity) of the device with an identifier of the M2M service e.g. the MSISDN (Mobile Station International ISDN Number).
- In an embodiment, following steps may be provided as illustrated in
figure 3 : - in
step 4, an entity (such as a M2M Information System entity) in charge of managing communications of M2M terminals, controls in an entity storing subscriber data in said communication system (such as HSS/HLR) an association between a M2M service identifier and the M2M terminals supporting this M2M service. - In one aspect, in an embodiment, the present invention provides a method for handling M2M services in a communication system, said method comprising a step of, for charging for lP-CAN bearer services in said communication system:
- providing global charging information for a plurality of terminals using a same M2M service.
- In an embodiment, said method comprises a step of:
- an entity storing subscriber data providing to an entity controlling said lP-CAN bearer services an indication that a terminal supports a M2M service.
- ln an embodiment, a single M2M service identifier is provided for said plurality of terminals using a same M2M service.
- In an embodiment, said method comprises a step of:
- an entity controlling said lP-CAN bearer services providing to an entity creating charging information for said lP-CAN bearer services an indication that a terminal supports a M2M service.
- In an embodiment, said indication is provided in the signalling associated with the creation of said lP-CAN bearer.
- ln an embodiment, said method comprises a step of:
- an entity creating charging information for said lP-CAN bearer services agglomerating charging information associated with a terminal supporting a M2M service with charging information associated with other terminals supporting said M2M service.
- ln an embodiment, charging information is periodically created, and the period for creating charging information is depending of whether a terminal is supporting a M2M service and of the M2M service identifier.
- ln an embodiment, a M2M service identifier corresponds to Mobile Station International ISDN Number MSISDN.
- In another aspect, in an embodiment, the present invention provides a method for handling M2M services in a communication system, said method comprising a step of:
- an entity in charge of managing communications of M2M terminals controlling in an entity storing subscriber data in said communication system an association between a M2M service identifier and the M2M terminals supporting this M2M service.
- ln an embodiment, said method comprises a step of:
- an entity in charge of managing communications of M2M terminals controlling in an entity storing subscriber data in said communication system an association between a M2M service identifier and the M2M terminals supporting this M2M service.
- In an embodiment, a M2M service identifier corresponds to Mobile Station International ISDN Number MSISDN.
- In other aspects, the present invention provides entities comprising means for carrying out such methods, said entities including in particular: entity storing subscriber data, entity controlling lP-CAN services, entity creating charging information such as in particular CDRS, and entity in charge of managing communications of M2M terminals via a communication system.
- In an embodiment, the present invention provides an entity storing subscriber data in a communication system, comprising, for charging for lP-CAN bearer services in said communication system:
- means for providing to an entity controlling said lP-CAN bearer services an indication that a terminal supports a M2M service.
- In an embodiment, the present invention provides an entity controlling lP-CAN services in a communication system, comprising, for charging for lP-CAN bearer services in said communication system:
- means for providing to an entity creating charging information for said IP-CAN bearer services an indication that a terminal supports a M2M service.
- In an embodiment, the present invention provides an entity creating charging information for lP-CAN bearer services in a communication system, comprising:
- means for agglomerating charging information associated with a terminal supporting a M2M service with charging information associated with other terminals supporting said M2M service.
- ln an embodiment, the present invention provides an entity in charge of managing communications of M2M terminals in a communication system, said entity comprising:
- means for controlling, in an entity storing subscriber data in said communication system, an association between a M2M service identifier and the M2M terminals supporting this M2M service.
- The detailed implementation of the above-mentioned means does not raise any special problem for a person skilled in the art, and therefore such means do not need to be more fully disclosed than has been made above, by their function, for a person skilled in the art.
- A person of skill in the art would readily recognize that steps of various above-described methods can be performed by programmed computers. Herein, some embodiments are also intended to cover program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods. The program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. The embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.
Claims (12)
- A method for handling Machine to Machine, M2M, services in a communication system, said method comprising a step of- providing global charging information for a plurality of terminals (M2M device, M2M Gateway) supporting a same M2M service for charging IP Connectivity Access Network IP-GAN bearer services in said communication system :- wherein said global charging information is periodically created, and the period for creating said global charging information is depending of whether a terminal of said plurality of terminals M2M service and of said same M2M service identifier identifying the M2M service.
- A method according to claim 1, comprising a step of:- an entity (HSS/HLR) storing subscriber data providing to an entity (SGSN/MME) controlling said IP-CAN bearer services an indication that the terminal supports said same M2M service
- A method according to claim 2, wherein a single M2M service identifier is provided for said plurality of terminals supporting said same M2M service
- A method according to any of claims 1 to 3, comprising a step of:- an entity (SGSN/MME) controlling said IP-CAN bearer services providing to an entity (GGSN/P-GW) creating charging information for said IP-CAN bearer services an indication that the terminal supports said same M2M service.
- A method according to claim 4, wherein said indication is provided in the signaling associated with the creation of said IP-CAN bearer.
- A method according to any of claims 1 to 5, comprising a step of :an entity (GGSN/P-GW) creating charging information for said IP-CAN bearer services agglomerating charging information associated with the terminal supporting said same M2M service with charging information associated with other terminals supporting said same M2M service
- A method for handling M2M services in a communication system, said method comprising a step of.
controlling by an entity (M2M Information System) in charge of managing communications of M2M terminals (M2M device, M2M Gateway) in said communication system in an entity (HSS/HLR) storing subscriber data in said communication system an association between α M2M service identifier and a plurality of M2M terminals a M2M service identified by said M2M service identifier. - A method according to any of claims 1 to 7, wherein the M2M service identifier corresponds to a Mobile Station International ISDN Number, MSISDN.
- An entity (GGSN/P-GW) creating global charging information for IP-CAN bearer services in a communication system, comprising:- means for agglomerating charging information associated with α terminal (M2M device, M2M Gateway) supporting a M2M service with charging information associated with other terminals supporting said M2M service,- wherein said global charging information is periodically created, and the period for creating said global charging information is depending of whether the terminal is supporting a M2M service and of the M2M service identifier identifying the M2M service.
- An entity (M2M Information System) in charge of managing communications of M2M terminals (M2M device, M2M Gateway) in a communication system, said entity comprising.- means for controlling, in an entity (HSS/HLR) storing subscriber data in said communication system, an association between a M2M service identifier and a plurality of M2M terminals supporting a M2M service identified by said M2M service identifier.
- An entity according to claim 10, said entity having an interface with a communication operator, said interface terminated on an entity (HSS/HLR) of said operator storing subscriber data in said communication system.
- An entity according to claim 10 or 11, wherein the M2M service identifier corresponds to a Mobile Station International ISDN Number, MSISDN.
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP12187971.2A EP2547039B1 (en) | 2010-01-05 | 2010-01-05 | Handling of M2M services in a communication system |
EP10305012A EP2341660B1 (en) | 2010-01-05 | 2010-01-05 | Handling of M2M services in a communication system |
CN201080060748.0A CN102714598B (en) | 2010-01-05 | 2010-12-29 | Process method and the entity of M2M business in a communications system |
US13/520,450 US9344830B2 (en) | 2010-01-05 | 2010-12-29 | Handling of M2M services in a communication system |
KR1020127020359A KR101465465B1 (en) | 2010-01-05 | 2010-12-29 | Handling of m2m services in a communication system |
JP2012547488A JP5921443B2 (en) | 2010-01-05 | 2010-12-29 | Handling of M2M services in communication systems |
PCT/EP2010/070845 WO2011083065A1 (en) | 2010-01-05 | 2010-12-29 | Handling of m2m services in a communication system |
JP2014251576A JP6077518B2 (en) | 2010-01-05 | 2014-12-12 | Handling of M2M services in communication systems |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP10305012A EP2341660B1 (en) | 2010-01-05 | 2010-01-05 | Handling of M2M services in a communication system |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12187971.2A Division EP2547039B1 (en) | 2010-01-05 | 2010-01-05 | Handling of M2M services in a communication system |
EP12187971.2 Division-Into | 2012-10-10 |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2341660A1 EP2341660A1 (en) | 2011-07-06 |
EP2341660B1 true EP2341660B1 (en) | 2012-11-21 |
Family
ID=42085013
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12187971.2A Active EP2547039B1 (en) | 2010-01-05 | 2010-01-05 | Handling of M2M services in a communication system |
EP10305012A Active EP2341660B1 (en) | 2010-01-05 | 2010-01-05 | Handling of M2M services in a communication system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12187971.2A Active EP2547039B1 (en) | 2010-01-05 | 2010-01-05 | Handling of M2M services in a communication system |
Country Status (6)
Country | Link |
---|---|
US (1) | US9344830B2 (en) |
EP (2) | EP2547039B1 (en) |
JP (2) | JP5921443B2 (en) |
KR (1) | KR101465465B1 (en) |
CN (1) | CN102714598B (en) |
WO (1) | WO2011083065A1 (en) |
Families Citing this family (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2547039B1 (en) * | 2010-01-05 | 2014-11-26 | Alcatel Lucent | Handling of M2M services in a communication system |
EP2543175B1 (en) * | 2010-03-01 | 2018-05-02 | InterDigital Patent Holdings, Inc. | Machine-to-machine gateway architecture and functionality |
KR20110121977A (en) * | 2010-05-03 | 2011-11-09 | 삼성전자주식회사 | Mobile communication and method for managing signaling message thereof |
JP5743206B2 (en) * | 2011-06-23 | 2015-07-01 | 日本電気株式会社 | Service control apparatus, relay apparatus, femtocell base station, communication system, control method, and program |
EP2568765A1 (en) | 2011-09-09 | 2013-03-13 | Buzzinbees Sas | A module MLR for managing machine-to-machine type (M2M) mobile devices |
WO2013060387A1 (en) * | 2011-10-28 | 2013-05-02 | Telefonaktiebolaget L M Ericsson (Publ) | Processing usage information for machine-to-machine communication |
US20130176907A1 (en) * | 2012-01-06 | 2013-07-11 | George Foti | Offline charging of m2m interactions |
CN103327464B (en) * | 2012-03-22 | 2018-08-24 | 中兴通讯股份有限公司 | A kind of charging method and system, information processing entity of MTC communication |
CN103686769A (en) * | 2012-09-12 | 2014-03-26 | 中兴通讯股份有限公司 | Service control method and device for terminal equipment |
CN103781056A (en) * | 2012-10-26 | 2014-05-07 | 中兴通讯股份有限公司 | Terminal peripheral data management method and M2M gateway |
CN103888924A (en) * | 2012-12-19 | 2014-06-25 | 中国移动通信集团公司 | WLAN-based billing method and device |
CN103997724B (en) | 2013-02-17 | 2017-12-15 | 阿尔卡特朗讯 | A kind of methods, devices and systems for being used to polymerize charge information |
US12039544B2 (en) | 2013-03-14 | 2024-07-16 | Aeris Communications, Inc. | Adaptive M2M billing |
US9083823B2 (en) | 2013-03-14 | 2015-07-14 | Aeris Communications, Inc. | Context oriented billing |
US11039017B2 (en) | 2013-03-14 | 2021-06-15 | Aeris Communications, Inc. | Adaptive M2M billing |
US9787853B1 (en) * | 2013-03-14 | 2017-10-10 | Aeris Communications, Inc. | M2M billing reconciliation for the internet of things |
US10389887B2 (en) | 2013-03-14 | 2019-08-20 | Aeris Communications, Inc. | Application specific M2M billing reconciliation |
US9609144B2 (en) * | 2013-05-03 | 2017-03-28 | Qualcomm Incorporated | Method for policy control and charging for D2D services |
CN105378770A (en) | 2013-07-23 | 2016-03-02 | 诺基亚技术有限公司 | Method and apparatus of secure charging for device-to-device service |
CN103684802A (en) * | 2013-12-05 | 2014-03-26 | 大唐移动通信设备有限公司 | Offline charging method and device |
JP6523313B2 (en) | 2014-02-10 | 2019-05-29 | 中興通訊股▲ふん▼有限公司Zte Corporation | Connectivity Enhancement in Machine-to-Machine Communication Systems |
JP6377754B2 (en) * | 2014-02-10 | 2018-08-22 | ゼットティーイー コーポレーションZte Corporation | Technology for mapping machine-to-machine communication to different infrastructure networks |
CN106165374A (en) | 2014-02-10 | 2016-11-23 | 中兴通讯股份有限公司 | In terms of enabling the different equipment triggering in machine-to-machine communication system |
US20170332322A1 (en) * | 2015-03-31 | 2017-11-16 | Ntt Docomo, Inc. | Gateway apparatus and communication method |
KR102271290B1 (en) * | 2015-04-24 | 2021-06-30 | 삼성전자 주식회사 | Method for generating and acquiring of changing information between devices in a wireless communication system |
CN106304008B (en) * | 2015-05-26 | 2020-11-10 | 电信科学技术研究院 | Charging method and device |
US10740080B2 (en) * | 2016-04-22 | 2020-08-11 | Kony, Inc. | Preview and publishing of mobile applications |
US10127420B2 (en) | 2016-08-04 | 2018-11-13 | Industrial Technology Research Institute | Location based situation awareness system and method thereof |
US10643039B2 (en) | 2016-08-04 | 2020-05-05 | Industrial Technology Research Institute | Location based situation awareness system and method thereof |
EP3520321B1 (en) * | 2016-09-30 | 2021-01-13 | Telefonaktiebolaget LM Ericsson (PUBL) | Method, computer program, apparatus and system for charging of a service session of m2m devices in a communication network |
WO2019039987A1 (en) * | 2017-08-21 | 2019-02-28 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for device counting |
CN108260034B (en) * | 2018-02-13 | 2020-11-17 | 中国联合网络通信集团有限公司 | Method and device for acquiring service bearing capacity of access network |
EP4133759A4 (en) * | 2020-04-09 | 2023-05-31 | Telefonaktiebolaget LM ERICSSON (PUBL) | Method and apparatus for service charging in a communication network |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002318899A (en) * | 2001-04-19 | 2002-10-31 | Nippon Telegr & Teleph Corp <Ntt> | Household account book agent system |
CN1885780B (en) * | 2005-06-24 | 2012-03-28 | 朗迅科技公司 | Centralized off-line charge and on-line charge method and system |
EP2056570A1 (en) * | 2007-10-29 | 2009-05-06 | Nokia Siemens Networks Oy | Session and media binding to common control |
JP2009200991A (en) * | 2008-02-25 | 2009-09-03 | Softbank Mobile Corp | Usage fee information processing system, usage fee information processing program, and usage fee information processing method |
US8116728B2 (en) * | 2008-04-22 | 2012-02-14 | Alcatel Lucent | Charging in LTE/EPC communication networks |
US8813168B2 (en) * | 2008-06-05 | 2014-08-19 | Tekelec, Inc. | Methods, systems, and computer readable media for providing nested policy configuration in a communications network |
DE102008037725A1 (en) * | 2008-08-14 | 2010-02-18 | Deutsche Telekom Ag | Method for the multiple physical use of a single identification in TK networks |
US8737989B2 (en) * | 2008-08-29 | 2014-05-27 | Apple Inc. | Methods and apparatus for machine-to-machine based communication service classes |
US8688551B2 (en) * | 2008-11-03 | 2014-04-01 | Nokia Siemens Networks Oy | Charging control providing correction of charging control information |
US7957314B2 (en) * | 2008-12-12 | 2011-06-07 | Cisco Technology, Inc. | System and method for provisioning charging and policy control in a network environment |
WO2010112080A1 (en) * | 2009-04-02 | 2010-10-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Control of a communication session |
WO2011025876A1 (en) * | 2009-08-27 | 2011-03-03 | Interdigital Patent Holdings, Inc. | Method and apparatus for solving limited addressing space in machine-to-machine (m2m) environments |
US8750145B2 (en) * | 2009-11-23 | 2014-06-10 | Interdigital Patent Holdings, Inc. | Method and apparatus for machine-to-machine communication registration |
MY156150A (en) * | 2009-12-22 | 2016-01-15 | Interdigital Patent Holdings | Group-based machine to machine communication |
EP2547039B1 (en) * | 2010-01-05 | 2014-11-26 | Alcatel Lucent | Handling of M2M services in a communication system |
-
2010
- 2010-01-05 EP EP12187971.2A patent/EP2547039B1/en active Active
- 2010-01-05 EP EP10305012A patent/EP2341660B1/en active Active
- 2010-12-29 CN CN201080060748.0A patent/CN102714598B/en active Active
- 2010-12-29 WO PCT/EP2010/070845 patent/WO2011083065A1/en active Application Filing
- 2010-12-29 KR KR1020127020359A patent/KR101465465B1/en active IP Right Grant
- 2010-12-29 JP JP2012547488A patent/JP5921443B2/en active Active
- 2010-12-29 US US13/520,450 patent/US9344830B2/en active Active
-
2014
- 2014-12-12 JP JP2014251576A patent/JP6077518B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
WO2011083065A1 (en) | 2011-07-14 |
JP5921443B2 (en) | 2016-05-24 |
CN102714598A (en) | 2012-10-03 |
EP2547039B1 (en) | 2014-11-26 |
US20130003609A1 (en) | 2013-01-03 |
CN102714598B (en) | 2015-09-16 |
EP2341660A1 (en) | 2011-07-06 |
KR20120120277A (en) | 2012-11-01 |
JP2015097395A (en) | 2015-05-21 |
JP6077518B2 (en) | 2017-02-08 |
JP2013516877A (en) | 2013-05-13 |
EP2547039A1 (en) | 2013-01-16 |
KR101465465B1 (en) | 2014-11-26 |
US9344830B2 (en) | 2016-05-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2341660B1 (en) | Handling of M2M services in a communication system | |
EP3827552B1 (en) | Process-efficient generation of data records for data communications involving groups or aggregates of iot devices | |
CN101374055B (en) | Method for processing charging and network system, packet data network gateway and charging system | |
EP2456122B1 (en) | Method and equipment for charging count | |
CN102647700B (en) | A kind of method and device obtaining also use location information | |
CN103891346A (en) | Diameter session audits | |
CN103517245B (en) | A kind of charging method and system of D2D communications | |
EP2801218A1 (en) | Offline charging of m2m interactions | |
WO2019128709A1 (en) | Traffic charging control method, device and system, and computer readable storage medium | |
JPWO2015022764A1 (en) | Wireless communication system and method for charging control | |
CN102868988A (en) | Policy charging control-based business processing method and system in wireless network | |
CN102378304A (en) | Policy information obtaining method, policy information providing method and communication system | |
CN103907313A (en) | Supported feature override | |
US20200008031A1 (en) | Machine-to-machine network optimization and online charging | |
US9980172B2 (en) | MTC-IWF entity, SCS entity, PCRF entity, and communication method | |
CN105307141B (en) | The method, device and equipment of policy control and charging | |
CN103891328A (en) | Visited PCRF S9 session ID generation | |
JP6484941B2 (en) | Network node and method for billing management |
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 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA RS |
|
17P | Request for examination filed |
Effective date: 20120109 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: ALCATEL LUCENT |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602010003725 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0012140000 Ipc: H04W0004000000 |
|
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: H04L 29/08 20060101ALI20120514BHEP Ipc: H04W 4/00 20090101AFI20120514BHEP Ipc: H04L 12/14 20060101ALI20120514BHEP |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: THIEBAUT, LAURENT Inventor name: BALLOT, JEAN-MARC |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO 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: AT Ref legal event code: REF Ref document number: 585597 Country of ref document: AT Kind code of ref document: T Effective date: 20121215 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602010003725 Country of ref document: DE Effective date: 20130117 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20121121 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 585597 Country of ref document: AT Kind code of ref document: T Effective date: 20121121 |
|
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: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20121121 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: 20130221 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: 20130304 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: 20121121 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20121121 |
|
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: 20121121 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: 20121121 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: 20130222 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: 20121121 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: 20130321 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: 20121121 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20121121 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20121121 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: 20121121 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: 20130221 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: 20121121 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: 20121121 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130131 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: 20121121 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: 20121121 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20121121 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: 732E Free format text: REGISTERED BETWEEN 20130829 AND 20130904 |
|
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 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
26N | No opposition filed |
Effective date: 20130822 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: GC Effective date: 20131018 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602010003725 Country of ref document: DE Effective date: 20130822 |
|
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: 20130731 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130105 |
|
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: 20121121 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PCOW Free format text: NEW ADDRESS: 148/152 ROUTE DE LA REINE, 92100 BOULOGNE-BILLANCOURT (FR) |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140131 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140131 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: RG Effective date: 20141016 |
|
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: 20121121 |
|
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: 20121121 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: 20121121 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20100105 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130105 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: 20121121 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 602010003725 Country of ref document: DE Representative=s name: PATENTANWAELTE U. KNECHT UND KOLLEGEN, DE Ref country code: DE Ref legal event code: R081 Ref document number: 602010003725 Country of ref document: DE Owner name: GEMALTO SA, FR Free format text: FORMER OWNER: ALCATEL LUCENT, PARIS, FR Ref country code: DE Ref legal event code: R082 Ref document number: 602010003725 Country of ref document: DE Representative=s name: PRINZ & PARTNER MBB PATENTANWAELTE RECHTSANWAE, DE |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 7 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: CA Effective date: 20160125 Ref country code: FR Ref legal event code: TP Owner name: GEMALTO SA, FR Effective date: 20160125 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 602010003725 Country of ref document: DE Representative=s name: PRINZ & PARTNER MBB PATENTANWAELTE RECHTSANWAE, DE |
|
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: 20121121 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 8 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: 732E Free format text: REGISTERED BETWEEN 20161208 AND 20161214 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 9 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231219 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20231219 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20231219 Year of fee payment: 15 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 602010003725 Country of ref document: DE |