WO2013023323A1

WO2013023323A1 - Method and system for communicating a subscriber identifier

Info

Publication number: WO2013023323A1
Application number: PCT/CN2011/001361
Authority: WO
Inventors: Zheng NAN
Original assignee: Gemalto Technologies (Shanghai) Co., Ltd. Beijing Branch
Priority date: 2011-08-16
Filing date: 2011-08-16
Publication date: 2013-02-21

Abstract

The invention relates to a method (20) for communicating a subscriber identifier. According to the invention, a mother token (14) being coupled to a terminal (12), a son token (18) storing an identifier relating to the son token, as son token identifier, the method comprises the following steps. The mother token sends to a remote server (112) the son token identifier (22). The server storing a first list of at least one son token identifier and a second list of at least one subscriber identifier, the server sends to the mother token an allocated subscriber identifier (24). The terminal or another terminal (16) is coupled to the son token. The terminal or another terminal sends to the son token the allocated subscriber identifier (26). And the son token stores the allocated subscriber identifier. The invention also pertains to a corresponding system for communicating a subscriber identifier.

Description

METHOD AND SYSTEM FOR COMMUNICATING A SUBSCRIBER

IDENTIFIER

Field of the invention:

The invention relates, in a general manner, to a method for communicating a subscriber identifier.

Moreover, the invention also pertains to a system for communicating a subscriber identifier.

State of the art:

As known per se, a mobile (tele)phone is identified to a wireless network thanks to a token, as a smart object, coupled to the phone. The token, such as a Subscriber Identity Module (or SIM) type card, stores an International Mobile Subscriber Identity (or IMSI). The token sends to the network the IMSI. The IMSI is used for identifying a subscriber to one or several services offered by a wireless network operator. Thus, each subscriber to a wireless network is issued a token that uniquely identifies a user account to the wireless network. Prior to being issued to a user, as subscriber to a wireless network, the token has to be personalized by storing into the token an IMSI.

There is therefore a need to personalize, in a cheap and efficient manner, a token, such as a SIM type card.

Summary of the invention:

The invention proposes a solution for satisfying the just hereinabove specified need by providing a method for communicating a subscriber identifier.

According to the invention, a mother token being coupled to a terminal, a son token storing an identifier relating to the son token, as son token identifier, the method comprises the following steps. The mother token sends to a remote server the son token identifier. The server stores a first list of at least one son token identifier and a second list of at least one subscriber identifier. The server sends to the mother token an allocated subscriber identifier. The terminal or another terminal is coupled to the son token. The terminal or another terminal sends to the son token the allocated subscriber identifier. And the son token stores the allocated subscriber identifier.

The principle of the invention consists in delivering a subscriber identifier to one token, as son token, after having been identified by its identifier supplied to a server by another token, as mother token, while using one or two terminals.

It is to be noted that one or two ordinary terminals may be used to provide a son token with a subscriber identifier.

A token, as mother token, allows retrieving a subscriber identifier allocated to a son token whose identifier is transmitted to a server by the mother token.

Contrary to the herein above described known solution, a mere use of one or two terminals and another token allows personalizing, in an easy, cheap and simple manner, a token.

According to a further aspect, the invention is a system for communicating a subscriber identifier.

According to the invention, the system comprises at least one terminal, a mother token, at least one son token and a remote server. The mother token is coupled to a terminal. The son token comprises means for storing an identifier relating to the son token, as son token identifier. The mother token is adapted to send to the server the son token identifier. The server comprises means for storing a first list of at least one son token identifier and a second list of at least one subscriber identifier. The server is adapted to send to the mother token an allocated subscriber identifier. The terminal or another terminal is coupled to the son token. The terminal or another terminal is adapted to send to the son token the allocated subscriber identifier. And the son token is adapted to store the allocated subscriber identifier.

As token, it may be a fixed object, like an embedded chip, i.e. a chip soldered to a Printed Circuit Board (or PCB) of a terminal, or a removable object, like a SIM type card or a dongle, such as a Universal Serial Bus (or USB) type drive. Brief description of the drawings:

Additional features and advantages of the invention will be more clearly understandable after reading a detailed description of one preferred embodiment of the invention, given as an indicative and non-limitative example, in conjunction with the following drawings:

- Figure 1 illustrates a simplified diagram of one exemplary embodiment of a system comprising two mobile phones, as terminals, two cards, as one mother token and one son token, and a distant server, the system being adapted so that the son token receives a subscriber identifier assigned by the server, according to the invention; and

- Figure 2 represents a simplified flow chart of one exemplary embodiment of a method implemented by the mother token, the son token and the server of figure 1 , so that the mother token collects from the server a subscriber identifier that the terminal coupled to the son token transmits to the son token, according to the invention.

Detailed description:

Herein under is considered an invention embodiment in which two tokens, such as cards, each card being coupled to a mobile phone.

However, the invention method for communicating a subscriber identifier may be implemented, among others, by only one mobile phone, as one terminal. According to such an embodiment, a mother token and a son token are successively coupled to the terminal.

Instead of being a mobile phone, each terminal may be, a Personal Computer (or PC), a Personal Digital Assistant (or PDA), a palm-top computer, a laptop computer, a desktop computer, a netbook, a tablet computer, a game console, a digital audio player, a video player, a multimedia player, a camera or a set-top box.

Instead of being a card, the son token and/or the mother token may be, for instance, a dongle of the USB type, any other electronic medium that may have different form factors, a chip fixed, possibly in a removable manner, to a host device, as terminal, or an embedded Secure Element (or SE), as a chip to be soldered to a PCB of a host device.

Naturally, the herein below described embodiment is only for exemplifying purposes and is not considered to reduce the scope of the present invention. Figure 1 shows schematically a system 10 for communicating a subscriber identifier.

A first mobile equipment 102 and a second mobile equipment 104 are, each, to be connected, through one mobile radio-communication network(s) 1 10, to a remote (Web) server 1 12.

Alternately, instead of a mobile radio-communication network(s) 1 10, the user terminals are connected, via a wire communication network, to the remote server 1 12.

The mobile radio-communication network(s) 1 10 may be a GSM (acronym for "Global System for Mobile Communications"), UTRAN (for "Universal mobile telecommunications system Terrestrial Radio Access Network"), EDGE (for "Enhanced Data Rates for GSM Evolution"), GPRS (for "General Packet Radio System"), WLAN (for "Wide Local Area Network"), CDMA (for "Code Division Multiple Access") and/or LTE (for "Long Term Evolution") network(s).

The mobile radio-communication network list is not exhaustive but only for exemplifying purposes and is not considered to reduce the scope of the present invention.

The first mobile equipment 102 includes a first mobile phone 12, as hand-held appliance and first terminal, and a Universal Integrated Circuit Card (or UICC) type smart card 14, as a first and mother token.

The second mobile equipment 104 includes a second mobile phone 16, as hand-held appliance and second terminal, and a UICC type smart card 18, as a second and son token.

For a sake of clarity and conciseness, the mobile phones 12 and 16 and the UICC type smart cards 14 and 18 are termed hereinafter the first and second phones 12 and 16 and the first and second cards 14 and 18 respectively.

The first and second mobile equipments 102 and 104 are, each, connected, through a wireless bidirectional link 15 and 19 respectively, to the mobile radio- communication network 1 10.

The mobile radio-communication network 1 10 is linked, via a bi-directional wired line 1 1 1 , to the server 1 12.

The server 1 12 may be operated or managed by a Mobile Network Operator (or MNO), a Mobile Virtual Network Operator (or MVNO), a banking Operator, a wire communication network operator, any service Operator or on behalf of a service Operator, as a service provider.

The server 1 12 has preferably a phone number to be used for being accessed. The server 1 12 may (possibly also) have a Uniform Resource Locator (or URL) to be used for being accessed.

The server 1 12 is used for:

- registering a first list of at least one identifier, such as an Integrated Circuit Card IDentifier (or ICCID), relating to a (son) card;

- registering a second list of at least one subscriber identifier, such as an IMSI;

- registering, preferably, a third list of at least one terminal address identifier, such as a Session Initiation Protocol (or SIP) address or a mobile phone number, such as a Mobile Station international Integrated Services Digital Network number (or MSISDN) or the like;

- registering, preferably, a fourth list of at least one key Ki relating to a card;

- uploading from the first card 14 a (son) card identifier relating to the second card 18;

- associating a (son) card identifier relating to the second card 18 with a subscriber identifier; and

- downloading to the first card 14 a subscriber identifier that is associated with the card identifier and allocated by the server 1 12 to the second card 18.

The key Ki relating to a (son) card is to be used by the second card 18 notably to authenticate the second card 18 to the server 1 12.

For each card, as second card 18, the server 1 12 manages a database in which a (son) card identifier, a subscriber identifier, a terminal address identifier, a card key are preferably associated with each other.

According to one important feature of the invention, the server 1 12 has to be accessed via an initiation from the first card 14 while identifying at least the second card 18 to be personalized.

As further explained infra with respect to the figure 2, for the described embodiment, the server 1 12 is used as a necessary entity for allocating or assigning to the second card 1 12 a subscriber identifier.

Optionally, the server 1 12 executes one or several security functions. The security functions include preferentially an authentication of a user of the first mobile equipment 102. During a configuration phase, the user of the first mobile equipment 102 enters data to be used as reference data for authenticating the user of the first mobile equipment 102. For example, the user gives either a Personal Identification Number (or PIN), such as four digits, or a biometric reference, such as a fingerprint or an iris image, as a code to be recognized and used for accessing an application for allocating a subscriber identifier to the second card 18 to be executed by the server 112. The PIN or the biometric reference to be matched may be stored at the server 112 side.

The security functions may comprise a decryption/encryption process to be used for exchanging data with the first card 14 and/or the second card 18, so as to protect access to the data exchanged between the server 112 and the first card 14 and/or the second card 18.

Each of the first phone 12 and the second phone 16 includes at least one microprocessor (not represented), at least one memory (not represented) and at least one Input/Output (or I/O) interface (not represented).

The phone memory stores data, an Operating System (or OS) and at least one application.

As to application(s) supported by each phone 12 or 16, there is, among others, an application for setting a phone call, so as to initiate an outgoing phone call. There is preferably at least an application for receiving a phone call, so as to take an incoming phone call. There may be an application for exchanging, through a Short Message Service type message, so as to send and receive a SMS type message. There may be an application for exchanging, through a Multimedia Messaging Service (or MMS) type message, so as to send and receive a MMS type message. There may be a (Web) browser, so as to access either, through the mobile radio- communication network 110 and an Internet network a remote (Web) server or a local server incorporated within the card coupled to the concerned phone, in order to interact with the application(s) supported by the concerned coupled card 14 or 18 and offered to the concerned phone user.

The phone microprocessor processes data originating from the phone memory or the phone I/O interface.

The phone microprocessor executes the application stored within the phone memory requested directly or indirectly by the phone user. The first phone 12 is arranged to connect, through the mobile radio- communication network 1 10, to the server 1 12, thanks to data provided by the first card 14, for example, a phone number or a URL of the server 1 12 to be accessed.

The second phone 16 is arranged to connect to at least the second card 18, so as to supply the second card 18 with data, like personalizing data, such as the subscriber identifier, to be stored into the second card 18.

The phone I/O interface of the first phone 12 and the second phone 16 includes an interface(s), so as to exchange data with the coupled first card 14 and second card 18 respectively. The interface between the first phone 12 and the first card 14 and/or the second phone 16 and the second card 18 may be an International Standard Organisation (or ISO) 7816 interface, as a contact interface when the card(s) 14 and/or 18 is(are) inserted into the concerned phone(s) 12 and/or 16.

The phone I/O interface of the first phone 12 includes a first display screen 122, a first keyboard 124, and one first antenna 126 (or several antennas). The phone I/O interface of the second phone 16 includes a second display screen 162, a second keyboard 164, and one second antenna 166 (or several antennas).

The first or second display screen 122 or 162 and the first or second keyboard 124 or 164, as Man Machine Interface (or MMI), may be used for exchanging information between a phone user and the concerned phone 12 or 16 or another entity(ies) to which the concerned phone 12 or 16 is connected, like the first card 14 or the second card 18, and/or the server 1 12 to be accessed.

The first 126 or second 166 antenna is arranged to let communicate, through a long range radio-frequency link 15 or 19, notably the first card 14 or the second card 18, through the concerned phone 12 or 16, and the server 1 12.

The first card 14 carries a first chip. The first card 14 chip is connected, via a first bi-directional link 13, to the first phone 12.

The first (card 14) chip comprises, at least one microprocessor(s) 142, as means for processing data, at least one memory 144, as means for storing data, and at least one I/O interface 146 for communicating with a host device which are all linked together through a control and data bus 143.

The first chip is intended to interact with the first phone 12, in order to connect, via the mobile radio-communication network 1 10, to the server 1 12. The first card 14 is preferably able to initiate an action(s) by itself, in order to interact directly with the outside world, in an independent manner of the first phone 12 and the mobile radio-communication network 1 10. Such a capability of interaction at the initiative of the first card 14 is also known as proactive capability.

The first card I/O interface 146 includes preferably an ISO 7816 interface, so as to let communicate the first card 14 and the first phone 12.

According to one particular embodiment, the first card I/O interface 146 comprises at least one Application Protocol Data Unit (or APDU) communication channel.

The first card I/O interface 146 may comprise another or other communication channel(s), such as an Internet Protocol (or IP) communication channel, a Mass Storage communication channel, and/or a USB communication channel.

The first card I/O interface 146 is used for receiving data from or sending data to outside, namely at least the first phone 12, through the corresponding first phone I/O interface, via the bi-directional communication link 13.

The communication between the first card 14 and the first phone 12 is used in particular to benefit from the MMI of the first phone 12 and/or an access to the mobile radio-communication network 1 10 to which the first phone 12 may be connected.

The first card memory 144 can be constituted by one or several EEPROM (acronym for "Electrically Erasable Programmable Read-Only Memory"), one or several ROM (for "Read Only Memory"), one or several Flash memories, and/or any other memories of different types, like one or several RAM (for "Random Access Memory").

The first card memory 144 stores, besides a card OS, an application algorithm relating to an invention process for communicating a subscriber identifier to be assigned to the second card 18, as another token.

The first card memory 144 stores preferably security functions.

The security functions include preferably a user authentication process to be used for accessing the server 1 12. To authenticate the user, the first card memory 144 may store an application for verifying a PIN or biometric data. The first card memory 144 stores securely the expected PIN or biometric data to be input by the first card 14 user. The first card 14 chip compares the input data with the stored PIN or biometric data and, only when the input data matches the stored PIN or biometric data, the first card 14 authorizes a running of the application algorithm.

The security functions include preferentially an encryption/decryption process. The encryption/decryption process uses an algorithm for encrypting data and an algorithm for decrypting data with at least one key shared between the first card 14 and the server 1 12. The algorithms for encrypting/decrypting data are shared between the first card 14 and the server 1 12. The encryption/decryption process is to be used before sending, through the first phone 12, to the server 112, data and after receiving, through the first phone 12, from the server 1 12 data. The encryption/decryption process allows protecting access to the data exchanged between the first card 14 and the server 1 12.

The first card memory 144 stores preferably a phone number or a URL relating to the server 1 12 to be accessed.

The first card memory 144 stores, as subscriber identifier, a first IMSI, as unique mobile phone user number associated with all GSM, UMTS, CDMA and/or LTE type network(s).

The first card memory 144 stores preferably a first key Ki that is used for authenticating the first card 14 to the server 1 12. The first key Ki is associated with the first IMSI.

The first card memory 144 stores, for example, a SIM application for a GSM network, a Universal Subscriber Identity Module (or USIM) for a UMTS network, a CDMA Subscriber Identity module (or CSIM) for a CDMA network, a Removable User Identity Module (or RUIM) for GSM, UMTS and CDMA networks and/or an Internet protocol multimedia Services Identity Module (or ISIM) for IP Multimedia Subsystem (or IMS).

The first card microprocessor 142 controls and communicates with all the components of the first card chip, such as its memory 144 to read it and possibly write into it. The first card microprocessor 142 controls a data exchange, through the I/O interface 146, with outside, notably the first phone 12.

The second card 18 is connected, via a second bi-directional link 17, to the second phone 16. Instead of a UICC type card, as portable smart object, the second token 18 may be a memory token, like a memory card, such as a (micro) Secure Digital (or SD) type card or a Multi-Media type Card (or MMC).

The second card 18 is intended to interact with the second phone 16, in order to receive data, such as personalization data, like a subscriber identifier originating from the server 1 12.

The second card 18 is preferably able to initiate an action(s) by itself, in order to interact directly with the outside world, in an independent manner of the second phone 16 and the mobile radio-communication network 1 10.

The second card 18 comprises, at least one microprocessor(s) 182, as means for processing data at least one memory 184, as means for storing data, and at least one I/O interface 186 for communicating with a host device which are all linked together through a control and data bus 183.

The second card I/O interface 186 includes preferably an ISO 7816 interface, so as to let communicate the second card 18 and the second phone 16.

According to one particular embodiment, the second card I/O interface 186 comprises at least one APDU communication channel.

The second card I/O interface 186 may comprise another or other communication channel(s), such as an IP communication channel, a MS communication channel and/or a USB communication channel.

The second card I/O interface 186 is used for receiving data from or sending data to outside, namely with at least the second phone 16, through the corresponding second phone I/O interface, via the second bi-directional communication link 17.

The second card memory 184 may be constituted by one or several EEPROMs, one or several ROMs, one or several Flash memories, and/or any other memories of different types, like one or several RAMs.

The second card memory 184 stores either no IMSI or a second dummy (or fake) IMSI, as a unique number associated with a mobile phone user. A second real IMSI is to be assigned by the server 1 12.

The second card memory 184 may have to store a mobile phone number associated with the second real IMSI and to be assigned by the server 1 12. The second card memory 184 stores preferably a second key Ki that is used for authenticating the second card 18 to the server 1 12. The second key Ki is associated with the second real IMSI (to be assigned).

The second card memory 184 may store, for example, a SIM application for a GSM network, a USIM for a UMTS network, a CSIM for a CDMA network, a RUIM for GSM, UMTS and CDMA networks, and/or an ISIM for IMS.

The second card memory 184 stores, besides a card OS, an application algorithm relating to an invention process for communicating a subscriber identifier to be assigned to the second card 18, as another token.

The second card microprocessor 182 controls a data exchange, through the I/O interface 186, with outside, notably the second phone 16.

The second card microprocessor 182 controls and communicates with all the components of the second card chip, such as its memory 184. In particular, the second card microprocessor 182 controls the second card memory 184 to write into it. Once received from the second phone 16, the second card microprocessor 182 writes the assigned second real IMSI into the second card memory 184 by possibly overwriting the previously stored second dummy IMSI.

Figure 2 depicts an example of a message flow 20 that involves the first card 14, as mother card, the server 1 12, the second phone 16 and the second card 18, as son card.

For the sake of simplicity, the first phone 12 is not represented. However, the first card 14 and the server 1 12 exchange data through the first phone 12 that is connected to the mobile radio-communication network 1 10 that is linked to the server 1 12.

It is assumed that the first and second cards 14 and 18 exchange data with outside through their respective first and second phones 12 and 16. It is also assumed that the second card 18 has an ICCID relating to the second card 18, as son card identifier. The ICCID is written on a surface of the second card 18. It is further assumed that the second phone 16 is coupled to the second card 18 that is not completely personalized, i.e. the second card memory 184 does not store any second real IMSI.

Firstly, a first card 14 user, like an operator, on its behalf or a retailer (who sells the second card 18 to an end-user), desires to configure or personalize the second card 18. The first card 14 user selects, preferably, through the MMI of the first phone 12, an application that is supported by the first card 14. Such an application selection may be carried out by selecting an application displayed by the first display screen 122, for example, within a HyperText Markup Language (or HTML) type page originating from a local server embedded within the first card 14 or a menu of applications, like a Sim ToolKit (or STK) menu, originating from the first card 14.

Preferably, the first card 14 user, as a controller of the personalization of the second card 18, is successfully authenticated by their first card 14.

The first card 14 user types with the first keyboard 124 a value of the ICCID relating to the second card 18.

The first card 14 sends, through the first phone 12, to the server 1 12 a message 22, like an SMS type message, including a request for retrieving a subscriber identifier relating to the second card 18 to be personalized and an ICCID. Such a request for retrieving a subscriber identifier of the second card 18 to be personalized constitutes a request for personalizing the second card 18.

The server 1 12 executes an application for communicating a subscriber identifier. Based upon the received ICCID, the server 1 12 retrieves a subscriber identifier that is associated with the received son card identifier.

The server 1 12 may also retrieve one or several available mobile phone numbers, as terminal address identifier(s) that is(are) associated with the received son card identifier.

The server 1 12 sends to the first card 14 a message 24, like an SMS type message, including an allocated (real) IMSI, as subscriber identifier relating to the second card 18.

This message 24 (or another message (not represented)) may further include one or several available mobile phone numbers, among which the first card user has to select one mobile phone number.

The first card user may have to select, thanks to the first phone 12 MMI, one mobile phone number amongst several displayed available mobile phone numbers.

The first card 14 sends to the first phone 12 a message including an allocated

IMSI to be displayed by the first display screen 122. This message (or another message (not represented)) may also include a corresponding possibly selected mobile phone number. The first display screen 122 displays at once one or two strings, one relating to the allocated IMSI and possibly another relating to the associated mobile phone number.

Since only an ICCID, the allocated IMSI and the associated mobile phone number are exchanged between the server 1 12 and the first card 14, the invention solution is safe.

The first card 14 user (or another user under the first card user control) selects, preferably, through the MMI of the second phone 16, an application that is supported by the second card 18. Such an application selection may be carried out by selecting an application displayed by the second display screen 162, for example, within a HTML type page originating from a local server embedded within the second card 18 or a menu of applications, like a STK menu, originating from the second card 18.

Then, the second card 18 requests, through the second display screen 162, the first card 14 user (or another user under the first card user control) to input the allocated subscriber identifier and possibly the allocated mobile phone number. The allocated mobile phone number may have been selected by the first card 14 user.

The first card 14 user (or another user under the first card user control) types with the second keyboard 164 the string value read on the first display screen 122 corresponding to the allocated second (real) IMSI. The first card 14 user (or another user under the first card user control) may also type with the second keyboard 164 another string value read on the first display screen 122 corresponding to the allocated mobile phone number.

The second card 18 personalizes the second card memory 184 by writing or registering into it the allocated second (real) IMSI and possibly the allocated mobile phone number.

The second card memory 184 stores the subscriber identifier and possibly the terminal address identifier that has(have) been allocated by the server 1 12.

The first card 14 user (or another user under the first card user control) is informed through the MMI of the second phone 16 once the subscriber identifier and possibly the terminal address identifier are stored within the second card memory 184.

Once the second card memory 184 has been updated, the first card 14 user (or another user under the first card user control) may re-boot the second phone 16. Then, the second card 18 sends to the server 112 a message that informs about a saving (or registration) of the allocated subscriber identifier and possibly the allocated terminal address identifier within the second card memory 184.

Alternatively, the first card 14 sends to the server 112 a message for informing about a saving of the allocated subscriber identifier and possibly the allocated terminal address identifier within the second card memory 184.

Only two mere phones 12 and 16 are used, there is thus no need of a specific equipment dedicated to personalizing a card. The invention solution is therefore easy, cheap, and efficient to implement.

A lot of amendments of the embodiment described supra may be brought without departing from the spirit of the invention. For example, instead of using two phones 12 and 16, a mere phone, as a single terminal, may be used. For example, instead of a transmission of the subscriber identifier (and other possible personalization data) from the second phone 16 to the second card 18, the first card 14 sends directly the subscriber identifier to the second card 18 through a short range radiofrequency link (not represented) thanks to contactless communication means included within the first card 14 and the second card 18.

Claims

15 CLAIMS

1. A method (20) for communicating a subscriber identifier,

characterized in that, a mother token (14) being coupled to a terminal (12), a son token (18) storing an identifier relating to the son token, as son token identifier, the method comprises the following steps:

- the mother token sends to a remote server (112) the son token identifier (22); the server storing a first list of at least one son token identifier and a second list of at least one subscriber identifier;

- the server sends to the mother token an allocated subscriber identifier (24);

- the terminal or another terminal (16) is coupled to the son token;

- the terminal or another terminal sends to the son token the allocated subscriber identifier (26); and

- the son token stores the allocated subscriber identifier.

2. Method according to claim 1, wherein, the server storing a third list of at least one terminal address identifier associated with the subscriber identifier, besides an allocated subscriber identifier, the server sends to the mother token at least one terminal address identifier.

3. Method according to claim 2, wherein the method further includes a selection step in which at least one terminal address identifier is selected.

4. Method according to claim 2 or 3, wherein the method further includes the following steps:

- the terminal or another terminal sends to the son token an allocated terminal address identifier; and

- the son token stores the allocated terminal address identifier.

5. Method according to any of claims 2 to 4, wherein the terminal address identifier includes a mobile phone Number.

Method according to any of claims 1 to 5, wherein the terminal includes telephone, a Personal Digital Assistant, a Personal Computer (or PC), a rayCN 2011/ 001 36 !

WO 2013/023323 PCT/CN2011/001361

16 tablet computer, a portable computer, a digital audio player, a video player, a multimedia player, a camera, a game console and a set-top box.

7. Method according to any of claims 1 to 6, wherein the allocated subscriber identifier is included within a Short Message Service type message.

8. Method according to any of claims 1 to 7, wherein the son token identifier includes an Integrated Circuit Card IDentifier.

9. Method according to any of claims 1 to 8, wherein the subscriber identifier includes an International Mobile Subscriber Identity.

10. A system (10) for communicating a subscriber identifier,

characterized in that the system comprises at least one terminal (12, 16), a mother token (14), at least one son token (18) and a remote server (112), the mother token being coupled to a terminal, the son token comprising means (184) for storing an identifier relating to the son token, as son token identifier;

in that the mother token is adapted to send to the server the son token identifier

(22);

in that, the server comprising means for storing a first list of at least one son token identifier and a second list of at least one subscriber identifier, the server is adapted to send to the mother token an allocated subscriber identifier (24);

in that, the terminal or another terminal (16) being coupled to the son token, the terminal or another terminal is adapted to send to the son token the allocated subscriber identifier (26); and

in that the son token is adapted to store the allocated subscriber identifier.