EP1892879A1 - System and method for transferring a device between mobile carriers - Google Patents

System and method for transferring a device between mobile carriers Download PDF

Info

Publication number
EP1892879A1
EP1892879A1 EP06119594A EP06119594A EP1892879A1 EP 1892879 A1 EP1892879 A1 EP 1892879A1 EP 06119594 A EP06119594 A EP 06119594A EP 06119594 A EP06119594 A EP 06119594A EP 1892879 A1 EP1892879 A1 EP 1892879A1
Authority
EP
European Patent Office
Prior art keywords
mobile carrier
wireless network
unique
database
esn
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.)
Granted
Application number
EP06119594A
Other languages
German (de)
French (fr)
Other versions
EP1892879B1 (en
Inventor
Piotr c/o Research in Motion Limited Madej
Jia-Lin c/o Research in Motion Limited Chin
Diana G. c/o Research in Motion Limited Vitorino
Levente c/o Research in Motion Limited Janosi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Original Assignee
Research in Motion Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Research in Motion Ltd filed Critical Research in Motion Ltd
Priority to AT06119594T priority Critical patent/ATE518399T1/en
Priority to EP06119594A priority patent/EP1892879B1/en
Priority to CA2598151A priority patent/CA2598151C/en
Publication of EP1892879A1 publication Critical patent/EP1892879A1/en
Application granted granted Critical
Publication of EP1892879B1 publication Critical patent/EP1892879B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/66Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/41Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/50Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for cross-charging network operators
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/51Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for resellers, retailers or service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0164Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20Technology dependant metering
    • H04M2215/2026Wireless network, e.g. GSM, PCS, TACS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/52Interconnection, inter-exchange, reseller billing, billing agreements between different operators, e.g. billing identifier added on the CDR in order to cross charge the other operator, inter-operator accounting, reconciliation, bill directly resellers customers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/54Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06De-registration or detaching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/12Mobility data transfer between location registers or mobility servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/06Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates generally to systems and methods for transferring a device between mobile carriers.
  • Suppliers of mobile communication services may offer handheld devices that may be used on the networks of multiple mobile carriers. Where there are two mobile carriers A and B with compatible network standards and protocols, the handheld device may be capable of operating on the wireless networks of both mobile carriers A and B. If mobile carrier A and mobile carrier B are related companies, they may allow the handheld devices to be transferred between their networks.
  • a user purchases and registers a handheld device and becomes a subscriber on mobile carrier A's wireless network.
  • a handheld device may be returned and made available to another user who may become a subscriber on mobile carrier B's wireless network. This may result in the supplier billing both mobile carriers A and B for the same device. What is needed is an improved system and method for transferring devices between mobile carriers that may avoid this problem.
  • the present invention relates generally to a system and method for transferring devices between mobile carriers.
  • FIG. 1 Shown in FIG. 1 is a schematic block diagram of an illustrative mobile handheld device 100.
  • the handheld device 100 may comprise a number of components, including a main processor 102 which controls the overall operation of device 100.
  • Communication functions, including data and voice communications, may be performed through a communication subsystem 104.
  • the communication subsystem 104 may receive messages from and sends messages to a wireless network 200.
  • the main processor 102 may also interact with additional subsystems such as a random access memory (RAM) 106, a flash memory 108, a display 110, an auxiliary input/output (I/O) subsystem 112, a data port 114, a keyboard 116, a speaker 118, a microphone 120, short-range communications 122 and other device subsystems 124.
  • the device 100 may be a battery-powered device and may include a battery interface 132 for receiving one or more rechargeable batteries 130 and for powering the various subsystems described above.
  • Operating system software used by the main processor 102 is typically stored in a persistent store such as flash memory 108.
  • a persistent store such as flash memory 108.
  • the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as the RAM 106.
  • Handheld device 100 may also include a read-only memory (ROM) 107 that may store a non-alterable electronic serial number or ESN which may be burned into ROM 107 at the time of manufacture of device 100.
  • ROM read-only memory
  • ESN electronic serial number
  • handheld device 100 may have a unique product identification number (PIN) stored in the ROM 107, or in another memory store in device 100.
  • PIN unique product identification number
  • the main processor 102 in addition to its operating system functions, enables execution of software applications 134 on the device 100.
  • the subset of software applications 134 that control basic device operations, including data and voice communication applications, will normally be installed on the device 100 during its manufacture.
  • the software applications 134 may include, for example, a messaging application 136, and a password approval module 138.
  • the software applications 134 may also include a device registration module 137 for registering the device 100 on a carrier network. As will be described further below, the registration of device 100 may be performed such that the double-billing problem as described above may be avoided.
  • the handheld device 100 may further include a device state module 140, an address book 142, a personal information manager (PIM) 144, and various other modules 146. Additional applications may also be loaded onto the device 100 through one of the wireless network 200, the auxiliary I/O subsystem 112, the data port 114, the short-range communications subsystem 122, or another subsystem 124.
  • PIM personal information manager
  • the communication subsystem 104 may comprise a receiver 210 and a transmitter 212, as well as associated components such as one or more embedded or internal antenna elements 214, 216, Local Oscillators (LOs) 218, and a processing module such as a Digital Signal Processor (DSP) 220.
  • LOs Local Oscillators
  • DSP Digital Signal Processor
  • Signals received by the antenna 214 through the wireless network 200 are input to the receiver 210, which can perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and analog-to-digital (A/D) conversion.
  • A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in the DSP 220.
  • signals to be transmitted are processed, including modulation and encoding, by the DSP 220.
  • These DSP-processed signals are input to the transmitter 212 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over the wireless network 200 via the antenna 216.
  • D/A digital-to-analog
  • FIG. 3 shown is an illustrative schematic block diagram of wireless networks 200A, 200B of mobile carrier A 310 and mobile carrier B 320, respectively.
  • device 100 may be configured to access wireless networks 200A and 200B.
  • each of the wireless networks 200A, 200B may have subsystems 314, 324 for requesting registration of devices 100 onto their respective wireless networks 310, 320.
  • a supplier 330 of wireless communication services may offer, for example, wireless email services to subscribers on both wireless networks 200A, 200B via network connections to the supplier 330's own network 332.
  • the supplier 330's network 332 may connect to a provisioning system 334 maintained by the supplier 330 and which may be appropriately configured to interact with subsystems 314, 324 provided on each of the wireless networks 200A, 200B.
  • Provisioning system 334 may maintain a database 336 of devices 100 that have been provisioned on the wireless networks 200A, 200B of mobile carrier A 310, and mobile carrier B 320.
  • each of the devices 100 may be uniquely identified, for example, by the unique ESN burned into the ROM 107 of each device 100.
  • each device 100 may be uniquely identified by the unique PIN identifier stored in ROM 107, or in another memory store in device 100. Records in database 336 may contain the unique ESN or PIN retrieved from ROM 107 or another memory store on each device 100. Each device 100 may thus be uniquely recognized by the supplier's provisioning system 334. Records in database 336 may also store information for the owning mobile carrier (e.g. mobile carrier A 310, or mobile carrier B 320), and this information may be linked to the unique ESN or PIN of device 100.
  • the owning mobile carrier e.g. mobile carrier A 310, or mobile carrier B 320
  • each of the devices 100 may also have a unique billing identification (BID) based on the ESN or PIN. This information may also be stored in the database 336 of provisioning system 334.
  • the database 336 of provisioning system 334 may also store for each device 100 information on various wireless communication services that have been provisioned for that device (e.g. voice, data, picture, text messaging, Internet access, music downloading, etc.). Use of the various services can be monitored by a subscriber's unique BID, and billed appropriately to the subscriber.
  • registration module 137 of device 100 may be configured such that, when the device 100 is first powered up by a new user, the device 100 seeks a wireless network connection to access the supplier's provisioning system 334.
  • Subsystems 314, 324 on the wireless networks 200A, 200B may facilitate this connection between device 100 and provisioning system 334.
  • a double-billing problem may occur if device 100 is still activated on mobile carrier A 310's wireless network 200A. Even if carrier A 310 subsequently detects that device 100 has been registered on carrier B 320's wireless network 200B, carrier A 310 may be prevented by regulatory and security restrictions from attempting to deactivate device 100, as the device is now being used by carrier B 320's subscriber. In order to avoid this above problem, the following is proposed.
  • the request to provision the device 100 is received by provisioning system 334 (via subsystems 314, 324) only when the device 100 is turned on and at least temporarily makes a connection to the wireless network of the requesting mobile carrier. This is so that the ESN or PIN of the device 100 from which the request is made may be retrieved.
  • provisioning system 334 may be configured to first query its database 336 to determine whether the device 100 has been previously registered.
  • the unique ESN or PIN stored in ROM 107, or in another memory store in device 100 may be used to uniquely identify the device 100 for the purposes of this query.
  • mobile carrier B 320 in order to maintain security, is prevented from conducting a status request on device 100 directly from mobile carrier A 310, and vice versa. Rather, the supplier 330 handles any transfer of the device 100 between mobile carrier A 310 and mobile carrier B 320 on their behalf.
  • provisioning system 334 may determine if there is a record of device 100 in its provisioning system 334. As noted, the ESN or PIN may be used to uniquely identify device 100. If device 100 has not been previously registered, then provisioning system 334 may proceed to allow registration of device 100 on mobile carrier B 320's wireless network 200B, and provision mobile communication services for the device 100.
  • provisioning system 334 may be configured to determine whether the previous mobile carrier (i.e. mobile carrier A 310) uses a device based BID (e.g. BID based on ESN or PIN) and the device 100 is still activated on wireless network 200A. If the provisioning system 100 determines that device 100 is still activated on the wireless network 200A of mobile carrier A 310, then provisioning system 334 may proceed to deactivate device 100 on wireless network 200A. A notice may be sent to mobile carrier A 310 to advise that device 100 has been deactivate on its network. If there are any billing contracts set up for device 100 on wireless network 200A, such billing contracts may also be cancelled by the provisioning system 334.
  • the previous mobile carrier i.e. mobile carrier A 310
  • BID e.g. BID based on ESN or PIN
  • mobile carrier B 320 in order to allow the supplier 330 to verify deactivation of device 100 before allowing registration, mobile carrier B 320 will not be able to pre-activate a service for the device 100.
  • mobile carrier B 320 uses a non-device specific billing ID (e.g. Mobile Station International Subscriber Directory Number also known as MSISDN)
  • MSISDN Mobile Station International Subscriber Directory Number also known as MSISDN
  • mobile carrier B 320 may pre-activate a subscriber with some services but still will not be able to register a device 100 that is currently active for A until that device 100 completes registration with mobile carrier B 320.
  • provisioning system 334 may proceed to register device 100 on wireless network 200B, and also provision the requested wireless communication services.
  • a new billing contract based on a new BID may also be set up for device 100 on wireless network 200B.
  • Method 400 begins and, at block 402, receives a request (e.g. from mobile carrier B 320) for a device (e.g. handheld device 100) to be registered (e.g. on mobile carrier B 320's wireless network 200B) and provisioned with mobile communications services.
  • a request e.g. from mobile carrier B 320
  • a device e.g. handheld device 100
  • method 400 may proceed to make an enquiry (e.g. to provisioning system 334 and its database 336) to see whether device 100 has been previously registered and provisioned.
  • method 400 determines if the device 100 may have been previously registered. If no, method 400 proceeds to block 412 where method 400 proceeds with registration of device 100. Method 400 then proceeds to block 414 where method 400 provisions the requested wireless communication services on the wireless network (i.e. wireless network 200B) of the requesting mobile carrier B 320. If yes, module 400 proceeds to block 407.
  • wireless network i.e. wireless network 200B
  • method 400 determines if the BID of the previous mobile carrier (i.e. mobile carrier A 310) is device based (e.g. based on the unique ESN or unique PIN of the device 100). If no, method 400 proceeds to block 412 and proceeds with registration of device 100. If yes, method 400 proceeds to block 408.
  • method 400 deactivates the device 100 on the wireless network of the previous mobile carrier (i.e. mobile carrier A 310). Any billing contract for device 100 with the previous wireless carrier may also be cancelled.
  • method 400 determines if deactivation of the device on the previous mobile carrier has been confirmed. If no, method 400 loops. If yes, method 400 proceeds to block 412 where method 400 proceeds to allow registration of device 100.
  • a new billing contract may also be set up for device 100 on the wireless network of the requesting mobile carrier (i.e. wireless network 200B of mobile carrier B 320).
  • Method 400 then proceeds to block 414, where method 400 may provision mobile communication services for the device on the requesting mobile carrier's wireless network (i.e. wireless network 200B). Method 400 then ends.
  • a method of transferring a handheld device between mobile carriers comprising: receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network; uniquely identifying the device and querying a database to determine if the device has been previously registered; if the device has been previously registered to a previous mobile carrier, deactivating the device from the previous mobile carrier's wireless network; and upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network, registering the device on the requesting mobile carrier's wireless network.
  • the method further comprises, upon registration of the device on the requesting mobile carrier's wireless network, provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network.
  • the method further comprises uniquely identifying the device by one of a unique electronic serial number (ESN) and a unique product identification number (PIN).
  • ESN electronic serial number
  • PIN product identification number
  • the method further comprises maintaining in the database a list of previously registered devices based on one of the unique ESN and the unique PIN.
  • the method further comprises maintaining in the database a unique billing identification (BID) based on one of the unique ESN and the unique PIN.
  • BID unique billing identification
  • the method further comprises receiving the request to register the device only if the device is currently connected via the requesting mobile carrier's wireless network and can be identified by one of the unique ESN and the unique PIN.
  • the method further comprises, upon registration of the device on the requesting mobile carrier's wireless network, updating the database with the new registration information for the device.
  • the method further comprises deactivating the device from the previous mobile carrier's wireless network only if the previous mobile carrier uses a device based billing identification (BID).
  • BID device based billing identification
  • a system for transferring a handheld device between mobile carriers comprising: a provisioning system for receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network; a database uniquely identifying the device to determine if the device has been previously registered; deactivation means for deactivating the device from the previous mobile carrier's wireless network if the device has been previously registered to a previous mobile carrier; and registration means for registering the device on the requesting mobile carrier's wireless network upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network.
  • system further comprises provisioning means for provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network upon registration of the device on the requesting mobile carrier's wireless network.
  • system further comprises identification means for uniquely identifying the device by one of a unique electronic serial number (ESN) and a unique product identification number (PIN).
  • ESN electronic serial number
  • PIN product identification number
  • the provisioning system maintains in the database a list of previously registered devices based on one of the unique ESN and the unique PIN.
  • the provisioning system maintains in the database a unique billing identification (BID) based on one of the unique ESN and the unique PIN.
  • BID unique billing identification
  • the provisioning system is configured to receive the request to register the device only if the device is currently connected via the requesting mobile carrier's wireless network and can be identified by one of the unique ESN and the unique PIN.
  • the database stores the new registration information for the device upon registration of the device on the requesting mobile carrier's wireless network.
  • a computer readable medium storing computer code that when loaded into a provisioning system adapts the provisioning system to transfer a handheld device between mobile carriers, the computer readable medium comprising: code for receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network; code for uniquely identifying the device and querying a database to determine if the device has been previously registered; code for deactivating the device from the previous mobile carrier's wireless network if the device has been previously registered to a previous mobile carrier; and code for registering the device on the requesting mobile carrier's wireless network upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network.
  • the computer readable medium further comprises code for provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network upon registration of the device on the requesting mobile carrier's wireless network.
  • the computer readable medium further comprises code for uniquely identifying the device by one of a unique electronic serial number (ESN) and a unique product identification number (PIN).
  • ESN electronic serial number
  • PIN product identification number
  • the computer readable medium further comprises code for maintaining in the database a list of previously registered devices based on one of the unique ESN and the unique PIN.
  • the computer readable medium further comprises code for maintaining in the database a unique billing identification (BID) based on one of the unique ESN and the unique PIN.
  • BID unique billing identification
  • the computer readable medium further comprises code for receiving the request to register the device only if the device is currently connected via the requesting mobile carrier's wireless network and can be identified by one of the unique ESN and the unique PIN.
  • the computer readable medium further comprises code for updating the database with the new registration information for the device upon registration of the device on the requesting mobile carrier's wireless network.
  • the computer readable medium further comprises code for deactivating the device from the previous mobile carrier's wireless network only if the previous mobile carrier uses a device based billing identification (BID).
  • BID device based billing identification

Abstract

There is disclosed a system and method for transferring a mobile handheld device between mobile carriers. In an embodiment, a system for transferring a handheld device between mobile carriers comprises a provisioning system for receiving from a first mobile carrier a request to register the device on the first mobile carrier's wireless network; a database uniquely identifying the device to determine if the device has been previously registered; deactivation means for deactivating the device from the second mobile carrier's wireless network if the device has been previously registered to a second mobile carrier; and registration means for registering the device on the first mobile carrier's wireless network upon confirmation that the device has been deactivated from the second mobile carrier's wireless network. The device may be uniquely identified by a unique electronic serial number (ESN) or a unique product identification number (PIN)

Description

  • The present invention relates generally to systems and methods for transferring a device between mobile carriers.
  • Suppliers of mobile communication services, such as wireless email, may offer handheld devices that may be used on the networks of multiple mobile carriers. Where there are two mobile carriers A and B with compatible network standards and protocols, the handheld device may be capable of operating on the wireless networks of both mobile carriers A and B. If mobile carrier A and mobile carrier B are related companies, they may allow the handheld devices to be transferred between their networks.
  • Suppose that a user purchases and registers a handheld device and becomes a subscriber on mobile carrier A's wireless network. In some cases, a handheld device may be returned and made available to another user who may become a subscriber on mobile carrier B's wireless network. This may result in the supplier billing both mobile carriers A and B for the same device. What is needed is an improved system and method for transferring devices between mobile carriers that may avoid this problem.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • In the figures which illustrate exemplary embodiments of the invention:
    • FIGS. 1 is an illustration of a device in accordance with an embodiment;
    • FIG. 2 is a schematic block diagram of a communication subsystem component in the device of FIG. 1;
    • FIG. 3 is a schematic block diagram of a system in accordance with an embodiment;
    • FIG. 4 is a flowchart of a method in accordance with an embodiment.
    DESCRIPTION OF PREFERRED EMBODIMENTS
  • As noted above, the present invention relates generally to a system and method for transferring devices between mobile carriers.
  • Shown in FIG. 1 is a schematic block diagram of an illustrative mobile handheld device 100. The handheld device 100 may comprise a number of components, including a main processor 102 which controls the overall operation of device 100. Communication functions, including data and voice communications, may be performed through a communication subsystem 104. The communication subsystem 104 may receive messages from and sends messages to a wireless network 200.
  • The main processor 102 may also interact with additional subsystems such as a random access memory (RAM) 106, a flash memory 108, a display 110, an auxiliary input/output (I/O) subsystem 112, a data port 114, a keyboard 116, a speaker 118, a microphone 120, short-range communications 122 and other device subsystems 124. The device 100 may be a battery-powered device and may include a battery interface 132 for receiving one or more rechargeable batteries 130 and for powering the various subsystems described above.
  • Operating system software used by the main processor 102 is typically stored in a persistent store such as flash memory 108. Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as the RAM 106.
  • Handheld device 100 may also include a read-only memory (ROM) 107 that may store a non-alterable electronic serial number or ESN which may be burned into ROM 107 at the time of manufacture of device 100. In addition, handheld device 100 may have a unique product identification number (PIN) stored in the ROM 107, or in another memory store in device 100.
  • The main processor 102, in addition to its operating system functions, enables execution of software applications 134 on the device 100. The subset of software applications 134 that control basic device operations, including data and voice communication applications, will normally be installed on the device 100 during its manufacture.
  • The software applications 134 may include, for example, a messaging application 136, and a password approval module 138. The software applications 134 may also include a device registration module 137 for registering the device 100 on a carrier network. As will be described further below, the registration of device 100 may be performed such that the double-billing problem as described above may be avoided.
  • The handheld device 100 may further include a device state module 140, an address book 142, a personal information manager (PIM) 144, and various other modules 146. Additional applications may also be loaded onto the device 100 through one of the wireless network 200, the auxiliary I/O subsystem 112, the data port 114, the short-range communications subsystem 122, or another subsystem 124.
  • Referring now to FIG. 2, a block diagram of the communication subsystem component 104 of FIG. 1 is shown. The communication subsystem 104 may comprise a receiver 210 and a transmitter 212, as well as associated components such as one or more embedded or internal antenna elements 214, 216, Local Oscillators (LOs) 218, and a processing module such as a Digital Signal Processor (DSP) 220.
  • Signals received by the antenna 214 through the wireless network 200 are input to the receiver 210, which can perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and analog-to-digital (A/D) conversion. A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in the DSP 220. In a similar manner, signals to be transmitted are processed, including modulation and encoding, by the DSP 220. These DSP-processed signals are input to the transmitter 212 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over the wireless network 200 via the antenna 216.
  • Now referring to FIG. 3, shown is an illustrative schematic block diagram of wireless networks 200A, 200B of mobile carrier A 310 and mobile carrier B 320, respectively. With the various components and subsystems described above, device 100 may be configured to access wireless networks 200A and 200B. As shown, each of the wireless networks 200A, 200B may have subsystems 314, 324 for requesting registration of devices 100 onto their respective wireless networks 310, 320.
  • Still referring to FIG. 3, a supplier 330 of wireless communication services may offer, for example, wireless email services to subscribers on both wireless networks 200A, 200B via network connections to the supplier 330's own network 332. The supplier 330's network 332 may connect to a provisioning system 334 maintained by the supplier 330 and which may be appropriately configured to interact with subsystems 314, 324 provided on each of the wireless networks 200A, 200B. Provisioning system 334 may maintain a database 336 of devices 100 that have been provisioned on the wireless networks 200A, 200B of mobile carrier A 310, and mobile carrier B 320.
  • In the database 336 of provisioning system 334, each of the devices 100 may be uniquely identified, for example, by the unique ESN burned into the ROM 107 of each device 100. Alternatively, each device 100 may be uniquely identified by the unique PIN identifier stored in ROM 107, or in another memory store in device 100. Records in database 336 may contain the unique ESN or PIN retrieved from ROM 107 or another memory store on each device 100. Each device 100 may thus be uniquely recognized by the supplier's provisioning system 334. Records in database 336 may also store information for the owning mobile carrier (e.g. mobile carrier A 310, or mobile carrier B 320), and this information may be linked to the unique ESN or PIN of device 100.
  • In an embodiment, each of the devices 100 may also have a unique billing identification (BID) based on the ESN or PIN. This information may also be stored in the database 336 of provisioning system 334. The database 336 of provisioning system 334 may also store for each device 100 information on various wireless communication services that have been provisioned for that device (e.g. voice, data, picture, text messaging, Internet access, music downloading, etc.). Use of the various services can be monitored by a subscriber's unique BID, and billed appropriately to the subscriber.
  • In an embodiment, registration module 137 of device 100 may be configured such that, when the device 100 is first powered up by a new user, the device 100 seeks a wireless network connection to access the supplier's provisioning system 334.
    Subsystems 314, 324 on the wireless networks 200A, 200B may facilitate this connection between device 100 and provisioning system 334.
  • In the scenario described earlier, where a device 100 is originally registered to carrier A 310's wireless network 200A, then is transferred to carrier B 320's wireless network 320, a double-billing problem may occur if device 100 is still activated on mobile carrier A 310's wireless network 200A. Even if carrier A 310 subsequently detects that device 100 has been registered on carrier B 320's wireless network 200B, carrier A 310 may be prevented by regulatory and security restrictions from attempting to deactivate device 100, as the device is now being used by carrier B 320's subscriber. In order to avoid this above problem, the following is proposed.
  • In an embodiment, the request to provision the device 100 is received by provisioning system 334 (via subsystems 314, 324) only when the device 100 is turned on and at least temporarily makes a connection to the wireless network of the requesting mobile carrier. This is so that the ESN or PIN of the device 100 from which the request is made may be retrieved.
  • In the current example, suppose the request to provision the services is received from mobile carrier B 320. Rather than fulfilling the request to provision services for device 100 immediately, provisioning system 334 may be configured to first query its database 336 to determine whether the device 100 has been previously registered. As noted above, the unique ESN or PIN stored in ROM 107, or in another memory store in device 100, may be used to uniquely identify the device 100 for the purposes of this query.
  • In an embodiment, in order to maintain security, mobile carrier B 320 is prevented from conducting a status request on device 100 directly from mobile carrier A 310, and vice versa. Rather, the supplier 330 handles any transfer of the device 100 between mobile carrier A 310 and mobile carrier B 320 on their behalf.
  • In the current example, upon receiving the registration request from mobile carrier B, provisioning system 334 may determine if there is a record of device 100 in its provisioning system 334. As noted, the ESN or PIN may be used to uniquely identify device 100. If device 100 has not been previously registered, then provisioning system 334 may proceed to allow registration of device 100 on mobile carrier B 320's wireless network 200B, and provision mobile communication services for the device 100.
  • On the other hand, if provisioning system 334 determines that device 100 has been previously registered (e.g. there is a record in database 336 of device 100 being registered on wireless network 200A of mobile carrier A 310), provisioning system 334 may be configured to determine whether the previous mobile carrier (i.e. mobile carrier A 310) uses a device based BID (e.g. BID based on ESN or PIN) and the device 100 is still activated on wireless network 200A. If the provisioning system 100 determines that device 100 is still activated on the wireless network 200A of mobile carrier A 310, then provisioning system 334 may proceed to deactivate device 100 on wireless network 200A. A notice may be sent to mobile carrier A 310 to advise that device 100 has been deactivate on its network. If there are any billing contracts set up for device 100 on wireless network 200A, such billing contracts may also be cancelled by the provisioning system 334.
  • In an embodiment, in order to allow the supplier 330 to verify deactivation of device 100 before allowing registration, mobile carrier B 320 will not be able to pre-activate a service for the device 100. On the other hand, if mobile carrier B 320 uses a non-device specific billing ID (e.g. Mobile Station International Subscriber Directory Number also known as MSISDN), then mobile carrier B 320 may pre-activate a subscriber with some services but still will not be able to register a device 100 that is currently active for A until that device 100 completes registration with mobile carrier B 320.
  • Upon confirming deactivation of device 100 on wireless network 200A, provisioning system 334 may proceed to register device 100 on wireless network 200B, and also provision the requested wireless communication services. A new billing contract based on a new BID may also be set up for device 100 on wireless network 200B.
  • Now referring to FIG. 4, shown is an illustrative method 400 corresponding to the above described system. Method 400 begins and, at block 402, receives a request (e.g. from mobile carrier B 320) for a device (e.g. handheld device 100) to be registered (e.g. on mobile carrier B 320's wireless network 200B) and provisioned with mobile communications services. Upon receiving this request, at block 404, method 400 may proceed to make an enquiry (e.g. to provisioning system 334 and its database 336) to see whether device 100 has been previously registered and provisioned.
  • At decision block 406, method 400 determines if the device 100 may have been previously registered. If no, method 400 proceeds to block 412 where method 400 proceeds with registration of device 100. Method 400 then proceeds to block 414 where method 400 provisions the requested wireless communication services on the wireless network (i.e. wireless network 200B) of the requesting mobile carrier B 320. If yes, module 400 proceeds to block 407.
  • At block 407, method 400 determines if the BID of the previous mobile carrier (i.e. mobile carrier A 310) is device based (e.g. based on the unique ESN or unique PIN of the device 100). If no, method 400 proceeds to block 412 and proceeds with registration of device 100. If yes, method 400 proceeds to block 408.
  • At block 408, method 400 deactivates the device 100 on the wireless network of the previous mobile carrier (i.e. mobile carrier A 310). Any billing contract for device 100 with the previous wireless carrier may also be cancelled.
  • At decision block 410, method 400 determines if deactivation of the device on the previous mobile carrier has been confirmed. If no, method 400 loops. If yes, method 400 proceeds to block 412 where method 400 proceeds to allow registration of device 100. A new billing contract may also be set up for device 100 on the wireless network of the requesting mobile carrier (i.e. wireless network 200B of mobile carrier B 320).
  • Method 400 then proceeds to block 414, where method 400 may provision mobile communication services for the device on the requesting mobile carrier's wireless network (i.e. wireless network 200B). Method 400 then ends.
  • As will be appreciated, with the above system and method, the double-billing problem between mobile carriers A and B may be avoided.
  • Thus, in accordance with an embodiment of the invention, there is provided a method of transferring a handheld device between mobile carriers, comprising: receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network; uniquely identifying the device and querying a database to determine if the device has been previously registered; if the device has been previously registered to a previous mobile carrier, deactivating the device from the previous mobile carrier's wireless network; and upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network, registering the device on the requesting mobile carrier's wireless network.
  • In an embodiment, the method further comprises, upon registration of the device on the requesting mobile carrier's wireless network, provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network.
  • In another embodiment, the method further comprises uniquely identifying the device by one of a unique electronic serial number (ESN) and a unique product identification number (PIN).
  • In another embodiment, the method further comprises maintaining in the database a list of previously registered devices based on one of the unique ESN and the unique PIN.
  • In another embodiment, the method further comprises maintaining in the database a unique billing identification (BID) based on one of the unique ESN and the unique PIN.
  • In another embodiment, the method further comprises receiving the request to register the device only if the device is currently connected via the requesting mobile carrier's wireless network and can be identified by one of the unique ESN and the unique PIN.
  • In another embodiment, the method further comprises, upon registration of the device on the requesting mobile carrier's wireless network, updating the database with the new registration information for the device.
  • In another embodiment, the method further comprises deactivating the device from the previous mobile carrier's wireless network only if the previous mobile carrier uses a device based billing identification (BID).
  • In another aspect of the invention, there is provided a system for transferring a handheld device between mobile carriers, comprising: a provisioning system for receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network; a database uniquely identifying the device to determine if the device has been previously registered; deactivation means for deactivating the device from the previous mobile carrier's wireless network if the device has been previously registered to a previous mobile carrier; and registration means for registering the device on the requesting mobile carrier's wireless network upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network.
  • In an embodiment, the system further comprises provisioning means for provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network upon registration of the device on the requesting mobile carrier's wireless network.
  • In another embodiment, the system further comprises identification means for uniquely identifying the device by one of a unique electronic serial number (ESN) and a unique product identification number (PIN).
  • In another embodiment, the provisioning system maintains in the database a list of previously registered devices based on one of the unique ESN and the unique PIN.
  • In another embodiment, the provisioning system maintains in the database a unique billing identification (BID) based on one of the unique ESN and the unique PIN.
  • In another embodiment, the provisioning system is configured to receive the request to register the device only if the device is currently connected via the requesting mobile carrier's wireless network and can be identified by one of the unique ESN and the unique PIN.
  • In another embodiment, the database stores the new registration information for the device upon registration of the device on the requesting mobile carrier's wireless network.
  • In another aspect of the invention, there is provided a computer readable medium storing computer code that when loaded into a provisioning system adapts the provisioning system to transfer a handheld device between mobile carriers, the computer readable medium comprising: code for receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network; code for uniquely identifying the device and querying a database to determine if the device has been previously registered; code for deactivating the device from the previous mobile carrier's wireless network if the device has been previously registered to a previous mobile carrier; and code for registering the device on the requesting mobile carrier's wireless network upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network.
  • In an embodiment, the computer readable medium further comprises code for provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network upon registration of the device on the requesting mobile carrier's wireless network.
  • In another embodiment, the computer readable medium further comprises code for uniquely identifying the device by one of a unique electronic serial number (ESN) and a unique product identification number (PIN).
  • In another embodiment, the computer readable medium further comprises code for maintaining in the database a list of previously registered devices based on one of the unique ESN and the unique PIN.
  • In another embodiment, the computer readable medium further comprises code for maintaining in the database a unique billing identification (BID) based on one of the unique ESN and the unique PIN.
  • In another embodiment, the computer readable medium further comprises code for receiving the request to register the device only if the device is currently connected via the requesting mobile carrier's wireless network and can be identified by one of the unique ESN and the unique PIN.
  • In another embodiment, the computer readable medium further comprises code for updating the database with the new registration information for the device upon registration of the device on the requesting mobile carrier's wireless network.
  • In another embodiment, the computer readable medium further comprises code for deactivating the device from the previous mobile carrier's wireless network only if the previous mobile carrier uses a device based billing identification (BID).
  • While illustrative embodiments have been described above, it will be appreciated that various changes and modifications may be made. More generally, the scope of the invention is defined by the following claims.

Claims (17)

  1. A method of transferring a handheld device between mobile carriers, comprising:
    receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network;
    uniquely identifying the device and querying a database to determine if the device has been previously registered;
    if the device has been previously registered to a previous mobile carrier, deactivating the device from the previous mobile carrier's wireless network; and
    upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network, registering the device on the requesting mobile carrier's wireless network.
  2. The method of claim 1, further comprising, upon registration of the device on the requesting mobile carrier's wireless network, provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network.
  3. The method of claim 1 or claim 2, further comprising uniquely identifying the device by a unique electronic serial number (ESN) or a unique product identification number (PIN)
  4. The method of claim 3, further comprising maintaining in the database a list of previously registered devices based on the unique ESN or the unique PIN.
  5. The method of claim 3 or claim 4, further comprising maintaining in the database a unique billing identification (BID) based on the unique ESN or the unique PIN.
  6. The method of any one of claims 3 to 5, further comprising receiving the request to register the device only if the device is connected wirelessly via the requesting mobile carrier's wireless network and can be identified by the unique ESN or the unique PIN.
  7. The method of any one of claims 1 to 6, further comprising, upon registration of the device on the requesting mobile carrier's wireless network, updating the database with the new registration information for the device.
  8. The method of any one of claims 1 to 7, further comprising deactivating the device from the previous mobile carrier's wireless network only if the previous mobile carrier uses a device based billing identification (BID).
  9. A system for transferring a handheld device between mobile carriers, comprising:
    a provisioning system for receiving from a requesting mobile carrier a request to register the device on the requesting mobile carrier's wireless network;
    a database for uniquely identifying the device to determine if the device has been previously registered;
    deactivation means for deactivating the device from the previous mobile carrier's wireless network if the device has been previously registered to a previous mobile carrier; and
    registration means for registering the device on the requesting mobile carrier's wireless network upon confirmation that the device has been deactivated from the previous mobile carrier's wireless network.
  10. The system of claim 9, further comprising provisioning means for provisioning requested mobile communication services for the device on the requesting mobile carrier's wireless network upon registration of the device on the requesting mobile carrier's wireless network.
  11. The system of claim 9 or claim 10, further comprising identification means for uniquely identifying the device by a unique electronic serial number (ESN) or a unique product identification number (PIN).
  12. The system of claim 11, wherein the provisioning system is arranged to maintain in the database a list of previously registered devices based on the unique ESN or the unique PIN.
  13. The system of claim 11 or claim 12, wherein the provisioning system is arranged to maintain in the database a unique billing identification (BID) based on the unique ESN or the unique PIN.
  14. The system of any one of claims 11 to 13, wherein the provisioning system is configured to receive the request to register the device only if the device is connected wirelessly via the requesting mobile carrier's wireless network and can be identified by the unique ESN or the unique PIN.
  15. The system of any one of claims 9 to 14, wherein the database is arranged to store the new registration information for the device upon registration of the device on the requesting mobile carrier's wireless network.
  16. A computer readable medium storing computer code that when loaded into a provisioning system adapts the provisioning system to perform the method of any one of claims 1 to 8
  17. A communication network comprising two mobile carriers, a handheld device and the provision system of any one of claims 9 to 15 for transferring the handheld device between the mobile carriers.
EP06119594A 2006-08-25 2006-08-25 System and method for transferring a device between mobile carriers Active EP1892879B1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AT06119594T ATE518399T1 (en) 2006-08-25 2006-08-25 SYSTEM AND METHOD FOR TRANSMISSION FROM A TERMINAL BETWEEN MOBILE CARRIERS
EP06119594A EP1892879B1 (en) 2006-08-25 2006-08-25 System and method for transferring a device between mobile carriers
CA2598151A CA2598151C (en) 2006-08-25 2007-08-21 System and method for transferring a device between mobile carriers

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP06119594A EP1892879B1 (en) 2006-08-25 2006-08-25 System and method for transferring a device between mobile carriers

Publications (2)

Publication Number Publication Date
EP1892879A1 true EP1892879A1 (en) 2008-02-27
EP1892879B1 EP1892879B1 (en) 2011-07-27

Family

ID=37814054

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06119594A Active EP1892879B1 (en) 2006-08-25 2006-08-25 System and method for transferring a device between mobile carriers

Country Status (3)

Country Link
EP (1) EP1892879B1 (en)
AT (1) ATE518399T1 (en)
CA (1) CA2598151C (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997038522A1 (en) * 1996-04-04 1997-10-16 At & T Corp. Method and apparatus for automated provisioning and billing of communication services
WO1998046002A1 (en) 1997-04-09 1998-10-15 Telefonaktiebolaget Lm Ericsson (Publ) Cellular system having programmable subscription capabilities
US6381456B1 (en) 1997-12-31 2002-04-30 Lg Information & Communications, Ltd. Method for managing subscriber location information in mobile communications system
WO2003092317A1 (en) * 2002-04-25 2003-11-06 Nokia Corporation Method and network system for charging a roaming network subscriber
US20040139204A1 (en) * 2001-04-23 2004-07-15 Siegried Ergezinger Architecture for providing services in the internet
WO2006034284A1 (en) * 2004-09-20 2006-03-30 Claude Charles Buchert System and method for control of air time of communication devices

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997038522A1 (en) * 1996-04-04 1997-10-16 At & T Corp. Method and apparatus for automated provisioning and billing of communication services
WO1998046002A1 (en) 1997-04-09 1998-10-15 Telefonaktiebolaget Lm Ericsson (Publ) Cellular system having programmable subscription capabilities
US6381456B1 (en) 1997-12-31 2002-04-30 Lg Information & Communications, Ltd. Method for managing subscriber location information in mobile communications system
US20040139204A1 (en) * 2001-04-23 2004-07-15 Siegried Ergezinger Architecture for providing services in the internet
WO2003092317A1 (en) * 2002-04-25 2003-11-06 Nokia Corporation Method and network system for charging a roaming network subscriber
WO2006034284A1 (en) * 2004-09-20 2006-03-30 Claude Charles Buchert System and method for control of air time of communication devices

Also Published As

Publication number Publication date
CA2598151C (en) 2014-05-06
EP1892879B1 (en) 2011-07-27
ATE518399T1 (en) 2011-08-15
CA2598151A1 (en) 2008-02-25

Similar Documents

Publication Publication Date Title
CN102027764B (en) Method, system, and apparatus for access of network services using subscriber identities
CN100502551C (en) Network and method for registration of mobile devices and management of the mobile devices
US8812597B2 (en) Method and system for instant messaging traffic routing
CN101521875B (en) Terminal function management server, communication system and communication method
CN101031102B (en) System, device and method for processing SMS
WO2004017591A2 (en) System and method for triggering a provisioning event
CN101026795A (en) Apparatus, and associated method, for facilitating delivery and processing of push content
CN102341782A (en) Method for transmitting an nfc application and computer device
US8457630B2 (en) System and method for transferring a device between mobile carriers
CN102421089B (en) Service request processing method, platform thereof and system thereof
CN1926892B (en) Method and apparatus for sending message to mobile station by addressing the hardware part
CN101453694B (en) Method and system for value increasing service invoking Internet service capability
US8886170B2 (en) Systems and methods for managing services for carrier subscribers and migrating them to service bundles
CN105357650A (en) Intelligent mobile digital intercom method, server and system
US8155585B2 (en) System and method for blocking devices from a carrier network
CN102239671B (en) E-mail operation system, e-mail operation device, and e-mail operation method
CN101588567A (en) System and method for conditionally attempting an emergency call setup
CA2598151C (en) System and method for transferring a device between mobile carriers
CN102300198B (en) Realize method and system and the mobile phone remote service centre of mobile phone remote service
JP6320718B2 (en) Mobile terminal device, numbering server, and mobile terminal program
CN100428761C (en) Software updating method for mobile terminal
CN104869561A (en) Contacts updating method, client and contacts management platform
KR100826660B1 (en) Method and device for managing and using information of number portability
JP4769317B2 (en) Exchange, message transmission system, and message transmission method
KR20060017245A (en) Value added service subscriber information management system and method for mobile communication service system

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

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

17Q First examination report despatched

Effective date: 20080229

AKX Designation fees paid

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

AXX Extension fees paid

Extension state: RS

Payment date: 20060825

Extension state: AL

Payment date: 20060825

Extension state: MK

Payment date: 20060825

Extension state: HR

Payment date: 20060825

Extension state: BA

Payment date: 20060825

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 60/00 20090101AFI20110114BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

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

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

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

Ref legal event code: R096

Ref document number: 602006023269

Country of ref document: DE

Effective date: 20110929

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20110727

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 518399

Country of ref document: AT

Kind code of ref document: T

Effective date: 20110727

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

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

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

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

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

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

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

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

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

Ref country code: LV

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

Effective date: 20110727

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

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

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

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

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

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

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

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

Ref country code: CH

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

Effective date: 20110831

Ref country code: LI

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

Effective date: 20110831

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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

Ref country code: 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: 20110727

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

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

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

26N No opposition filed

Effective date: 20120502

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006023269

Country of ref document: DE

Effective date: 20120502

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

Ref country code: ES

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

Effective date: 20111107

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

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

Ref country code: BG

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

Effective date: 20111027

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

Ref country code: TR

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

Effective date: 20110727

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

Ref country code: HU

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

Effective date: 20110727

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006023269

Country of ref document: DE

Representative=s name: MATIAS ERNY REICHL HOFFMANN PATENTANWAELTE, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006023269

Country of ref document: DE

Representative=s name: MATIAS ERNY REICHL HOFFMANN PATENTANWAELTE, DE

Effective date: 20140925

Ref country code: DE

Ref legal event code: R081

Ref document number: 602006023269

Country of ref document: DE

Owner name: BLACKBERRY LIMITED, WATERLOO, CA

Free format text: FORMER OWNER: RESEARCH IN MOTION LIMITED, WATERLOO, ONTARIO, CA

Effective date: 20140925

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

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

Ref country code: GB

Payment date: 20230828

Year of fee payment: 18

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

Ref country code: FR

Payment date: 20230825

Year of fee payment: 18

Ref country code: DE

Payment date: 20230829

Year of fee payment: 18